[Touch-packages] [Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
Ubuntu 20.04 is also affected by this bug in the same way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: The python version of the gpgme version contains "unknown" and is therefore not PEP440 order compatible. See this example: # pip3 freeze | grep gpg gpg===1.16.0-unknown # pip3 install pstore ... Successfully installed gpg-1.10.0 Successfully installed pstore-2.0.0 # pip3 freeze | grep gpg gpg==1.10.0 Key takeways from that example: - pstore depends on gpg>=1.10 - 1.16 SHOULD be higher than 1.10 - pip installs 1.10 even though 1.16 exists - the triple-= (gpg===1.16.0-unknown) means that the version exists, but cannot be version compared: https://peps.python.org/pep-0440/#arbitrary-equality Suggested fix: - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a '+'; that will compare as expected; - fix so "-unknown" isn't appended. Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch I've attached a FIXED version, which should fix things. Before: $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown. After: $ quilt push Applying patch 0001-avoid-identifying-as-beta-FIXED.patch $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0. Versions: $ lsb_release -a 2>/dev/null| grep Codename Codename: jammy $ apt-cache policy python3-gpg | grep Installed Installed: 1.16.0-1.2ubuntu4 Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367214] Re: Newly installed openssh-server and upstart: status: Unknown job: ssh
Here are some external descriptions of this problem: https://askubuntu.com/questions/403279/sshd-wont-stop-start-properly https://askubuntu.com/questions/406265/ssh-server-does-not-start-on-lubuntu-live-image https://superuser.com/questions/931329/unable-to-setup-openssh-server-on-ubuntu https://serverfault.com/questions/333943/cant-start-ssh-after-upgrade-ubuntu http://aplawrence.com/Linux/ubuntu_start_bug.html http://ubuntuforums.org/showthread.php?t=2260006 http://xbian.org/forum/thread-2473-post-24475.html https://stackoverflow.com/questions/30568905/ubuntu-when-upstart-service-is-run-with-user-root-it-returns-unknown-job -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1367214 Title: Newly installed openssh-server and upstart: status: Unknown job: ssh Status in upstart package in Ubuntu: Confirmed Bug description: Just after installing openssh-server, there is no ssh service in the initctl's list. Consequently, the SSH server cannot be started: # initctl start ssh initctl: Unknown job: ssh # dpkg -l | grep ssh ii openssh-client 1:6.6p1-2ubuntu2 i386 secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:6.6p1-2ubuntu2 i386 secure shell (SSH) server, for secure access from remote machines # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" # initctl reload-configuration # initctl list | grep ssh ssh-agent start/running # ps axuw | grep ssh ivoras1578 0.0 0.0 4216 200 ?Ss Sep08 0:00 ssh-agent -s root 11810 0.0 0.0 6168 852 pts/2S+ 11:26 0:00 grep ssh # initctl start ssh initctl: Unknown job: ssh Running "/etc/init.d/ssh" does not do anything since the script exits, AFAIK in the upstart check. Running "service ssh restart" results in: # service ssh restart stop: Unknown job: ssh start: Unknown job: ssh After rebooting the machine, sshd is started (!), but still not visible in "initctl list" (!!) and running /etc/init.d/ssh still doesn't do anything (!!!), as well as the "service" command returning the same "Unknown job: ssh" error. Exactly the same problem happens with the php5-fpm service. I've also installed nginx and while it can be controlled by using /etc/init.d/nginx , it is not visible in "initctl list". The question is - how do I control the services in Ubuntu 14.04? This is a fresh install, the ssh service was the first service installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1367214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367214] Re: Newly installed openssh-server and upstart: status: Unknown job: ssh
I also have this problem on a client's machine. This leads to failing chef-scripts, that's very annoying. Does anyone have a solution or workaround, except the --system flag? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1367214 Title: Newly installed openssh-server and upstart: status: Unknown job: ssh Status in upstart package in Ubuntu: Confirmed Bug description: Just after installing openssh-server, there is no ssh service in the initctl's list. Consequently, the SSH server cannot be started: # initctl start ssh initctl: Unknown job: ssh # dpkg -l | grep ssh ii openssh-client 1:6.6p1-2ubuntu2 i386 secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:6.6p1-2ubuntu2 i386 secure shell (SSH) server, for secure access from remote machines # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" # initctl reload-configuration # initctl list | grep ssh ssh-agent start/running # ps axuw | grep ssh ivoras1578 0.0 0.0 4216 200 ?Ss Sep08 0:00 ssh-agent -s root 11810 0.0 0.0 6168 852 pts/2S+ 11:26 0:00 grep ssh # initctl start ssh initctl: Unknown job: ssh Running "/etc/init.d/ssh" does not do anything since the script exits, AFAIK in the upstart check. Running "service ssh restart" results in: # service ssh restart stop: Unknown job: ssh start: Unknown job: ssh After rebooting the machine, sshd is started (!), but still not visible in "initctl list" (!!) and running /etc/init.d/ssh still doesn't do anything (!!!), as well as the "service" command returning the same "Unknown job: ssh" error. Exactly the same problem happens with the php5-fpm service. I've also installed nginx and while it can be controlled by using /etc/init.d/nginx , it is not visible in "initctl list". The question is - how do I control the services in Ubuntu 14.04? This is a fresh install, the ssh service was the first service installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1367214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp