apt-get update Bad header line - apt-get

I'm hosting a reprepo debian package server with a bunch of arm packages for an embedded linux project. I have arm symbol files in the repo. On my host machine, Ubuntu 14.04 LTS, I want to -force-architecture install them. When I update my PPAs with my debian repo apt-get update is erroring with Bad header line. I've been searching for hours for a solution. Can't even find a way to turn on verbose for apt-get. dpkg has --debug= so I tried sudo apt-get -o Dpkg::Options::="--debug=3773" update with no success.
Checked /var/log/dpkg.log and /etc/apt/*.logs nothing in them... How do you debug apt-get?

Related

Installing MySQL and MySQLWorkbench In Offline Red Hat 7 Machine

I am trying to install mysql workbench on a system without network. I downloaded the mysql-workbench-community, mysql-community-{server, client, common, libs} which were noted in the "Installing RPM Packages" section of MySQL Install Manual. It states that these are the standard rpm packages needed for a basic functional install of mysql community. So with that I downloaded all the rpm packages and attempted to manually install each using:
sudo rpm -ivh mysql-community-package-name.rpm
Unfortunately I keep getting dependency errors. I found this link to obtain all the dependencies for a package. So on my second attempt I ran the following:
Repoquery -R --resolve --recursive mysql-community-server | xargs -r yumdownloader
Which gave me about 100 rpm packages. I transferred them onto my machine and unfortunately more dependencies like mysql-connectors-community and mysql-=tools-community came up which were never documented or mentioned as dependencies with the script.
What am i doing wrong? Is there a way to download all the rpms and bundle them together as a custom RPM in the future? I see ubuntu has a apt-offline command mentioned here. Is there a similar method I can apply for redhat?
Update1:
I have an idea to create a container rhel7 instance, mounting /root/tmpkg and running this example. But is there another way I should consider?

How can I get the keyring extension working for mercurial in Ubuntu 18.04?

I've tried dozens of guides on installing mercurial and keyring extensions on Ubuntu and have never been able to get the keyring extension to work. It was a snap under Windows.
I've installed mercurial many different ways. I'm not sure if the install method has anything to do with the keyring, but here are a few of the things I've tried:
sudo apt-get install mercurial
sudo apt install mercurial
pip install mercurial
... and so on.
I even used this method where it compiles mercurial.
All of these methods work for mercurial. It runs. I can do commits, etc. It's keyring and mercurial_keyring installations that are giving me trouble. I installed both of those using pip install. When I do a command like:
hg out http://somerepo
At the moment, I'm getting the following message:
No handlers could be found for logger "keyring.backend"
I feel like there is a concise set of steps to get keyring working, but it's just eluding me. I've made half a dozen attempts on fresh virtual machines and can never get this to work. :(
pip uninstall keyring
The reason is that python has already the library python-keyring installed which conflicts with the one installed with pip. Credits to Python library woes on Ubuntu 18.04 by Kai Koenig
Edit: the story actually did not end there because what it did was to get rid of that error but was not the actual solution. I had to continue with these commands
pip install keyrings.alt
pip install keyring
(yes, I installed it back)
python -c "import keyring.util.platform_; print(keyring.util.platform_.config_root())"
That was taken from keyring docummentation. It turned out that my config folder shown by this command was not created so I did:
mkdir ~/.local/share/python_keyring
vi ~/.local/share/python_keyring/keyringrc.cfg
I had to create the .cfg file as well and put this inside (on my MacOS Mojave!):
[backend]
default-keyring=keyring.backends.OS_X.Keyring
Now everything works fine, no password asked anymore

How do I update version of Fish Terminal? (Ubuntu)

I am currently on 2.1.0 and would like to go to latest (2.5.0 currently). Is there a command to do this? Or do I need to uninstall the current version and install a new one? Is this done through apt-get?
Could not find this anywhere in documentation or elsewhere on the internet...
I tried downloading the latest .deb file from the fish download page, but trying to open this in Ubuntu software centre yields "Breaks existing package 'fish'"
The best way is to use the package archive provided by the fish project to replace the packages that the Ubuntu project ship (which are very old and contain security problems).
The following commands subscribe your system to the Personal Package Archive run by the fish developers, update the package list and finally upgrade or install fish:
sudo add-apt-repository ppa:fish-shell/release-3
sudo apt-get update
sudo apt-get install fish
As an added bonus, running apt-get upgrade after these steps will always make sure you have the newest-available version of fish.
Add the PPA for release-3, update, and install
sudo add-apt-repository ppa:fish-shell/release-3
sudo apt-get update
sudo apt-get install fish

Why can't I uninstall mysql-5.5 & install mysql-5.6 on Amazon Linux machine?

I'm on a 64-bit Amazon Linux machine.
I had previously installed mysql-server 5.5. (using sudo yum install)
However, I soon found out that my application requires MySql-serve 5.6.
So I uninstalled mysql-server 5.5. (using sudo yum remove mysql-server) and now I'm following these instruction to install mysql-server 5.6.
But I'm running into a problem.
when I try to do the second install, I get the following 2 errors:
file /usr/lib64/mysql/libmysqlclient.so.18 from install of mysql-community-libs-5.6.14-3.el6.x86_64 conflicts with file from package mysql55-libs-5.5.46-1.10.amzn1.x86_64
file /etc/my.cnf from install of mysql-community-server-5.6.14-3.el6.x86_64 conflicts with file from package mysql-config-5.5.46-1.10.amzn1.x86_64
Why on earth am I getting these two errors? How do I fix them?
I removed mysql-server-5.5, so why is it conflicting with 5.6?
I did ls on /etc/my.cnf and /usr/lib64/mysql/libmysqlclient.so.18 and the files don't even exist!! If the files don't exist how can they be conflicting with other files?? Who can help explain this?
PS, I tried #msknapp's explanation here: Can't install MySQL 5.6 by RPM, however I don't know what to do after step #1 to install the rpm. I think that step is left unstated.
mysql-server (of whatever version) depends on other packages ( in your case mysql-community-libs mysql-community-server)
When it is installed in the first place with the old version this stuff is installed. When you "uninstall" mysql-server these dependencies are NOT removed.
When you try and install the new version these still existing packages will conflict with the new package. It does not matter if the actual files in the package are there, it is the package and it's listing of what to expect that conflicts.
To resolve your problem figure out what the dependencies of mysql-server were and uninstall them before attemping the install.
This answer https://superuser.com/questions/294662/how-to-get-list-of-dependencies-of-non-installed-rpm-package may be of interest for working out what mysql-server depends on

Installing libssl0.9.7 on Debian (Google Compute Engine)

I am quite new to this. Is there a certain repo I'm supposed to install? If so could you tell me it and what command I need to put in. Thanks.
libssl0.9.7 on Debian.
I don't think there are any repos that still have that version. Installing such an old version of OpenSSL is NOT recommended as it comes with way too many vulnerabilities to list. But if you still want that version, you can download it here: http://archive.debian.net/etch/amd64/libssl0.9.7-dbg/download
Here are the commands to install it:
wget -c http://archive.kernel.org/debian-archive/debian/pool/main/o/openssl097/libssl0.9.7-dbg_0.9.7k-3.1etch5_amd64.deb
sudo dpkg -i libssl0.9.7*.deb
sudo apt-get -f install
Since it's an old version, there's no guarantee that it'll be compatible with new systems. You may receive some errors after completing the installation.