[Group.of.nepali.translators] [Bug 1946137] Re: distro-info-data update needed for 14.04/16.04 ESM being extended to five years
This was fixed in all releases (including trusty and xenial ESM) except impish, leaving that task open. ** Changed in: distro-info-data (Ubuntu) Status: Fix Released => Triaged ** Also affects: distro-info-data (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: distro-info-data (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: distro-info-data (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: distro-info-data (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: distro-info-data (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: distro-info-data (Ubuntu Trusty) Status: New => Fix Released ** Changed in: distro-info-data (Ubuntu Xenial) Status: New => Fix Released ** Changed in: distro-info-data (Ubuntu Bionic) Status: New => Fix Released ** Changed in: distro-info-data (Ubuntu Focal) Status: New => Fix Released ** Changed in: distro-info-data (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1946137 Title: distro-info-data update needed for 14.04/16.04 ESM being extended to five years Status in distro-info-data package in Ubuntu: Triaged Status in distro-info-data source package in Trusty: Fix Released Status in distro-info-data source package in Xenial: Fix Released Status in distro-info-data source package in Bionic: Fix Released Status in distro-info-data source package in Focal: Fix Released Status in distro-info-data source package in Hirsute: Fix Released Bug description: It was recently announced the the 14.04 and 16.04 ESM releases would be receive a total of five years ESM support status each, and the distro-info-data for ubuntu should be updated to reflect that: $ dpkg -l distro-info-data | grep ^ii ii distro-info-data 0.51 all information about the distributions' releases (data files) $ grep -E '(Trusty|Xenial)' /usr/share/distro-info/ubuntu.csv 14.04 LTS,Trusty Tahr,trusty,2013-10-17,2014-04-17,2019-04-25,2019-04-25,2022-04-25 16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21,2021-04-21,2024-04-23 The last entries should be updated to 2024 and 2026 respectively, to match the information at https://ubuntu.com/security/esm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1946137/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"
[Xenial has reached its end of standard support.] ** Changed in: bind9 (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630025 Title: Fails running In chroot with "ENGINE_by_id failed (crypto failure)" Status in BIND: New Status in bind9 package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Won't Fix Status in bind9 package in Debian: Fix Released Bug description: Running inside an OpenVZ guest, it is not possible to use the AppArmor as discussed, so I am trying to configure BIND9 to run in chroot. Then I got the following in the log: named[3398]: ENGINE_by_id failed (crypto failure) named[3398]: error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: named[3398]: error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:467: named[3398]: error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:390:id=gost named[3398]: initializing DST: crypto failure named[3398]: exiting (due to fatal error) systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE This seems to be a bug that is found in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820974 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1645002] Re: ssh sessions are not cleanly terminated on shutdown/restart with systemd
Xenial is now in Extended Security Maintenance and this bug doesn't qualify for it, so the bugfix won't be SRUed there. ** Changed in: openssh (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1645002 Title: ssh sessions are not cleanly terminated on shutdown/restart with systemd Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Won't Fix Status in openssh source package in Yakkety: Fix Released Status in openssh package in Debian: Fix Released Bug description: In Ubuntu 16.04, a "reboot" command does not terminate the ssh session. This results in clients hanging, until timing out (sometimes as much as 120 seconds). This also introduces bugs to all orchestration / automation tools which work over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 hosts. For example, have a look at this issue for Fabric: https://github.com/fabric/fabric/issues/1488 The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. There is a very detailed discussion in their bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1645002/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1608965] Re: ssh GSSAPI rekey failure
Yakkety reached EOL, while Xenial is now in Extended Security Maintenance, and this bug doesn't qualify for it, so this bug won't be fixed in those releases. ** Changed in: openssh (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: openssh (Ubuntu Yakkety) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1608965 Title: ssh GSSAPI rekey failure Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Won't Fix Status in openssh source package in Yakkety: Won't Fix Bug description: If I have ssh set up using GSSAPI with rekeying enabled, then the connection fails on rekey, and tries to do host-based verification 'mid-session'. Steps to reproduce: $ ssh -vvv server.example.com debug1: Authenticating to ssh.example.com:22 as 'user' debug2: local client KEXINIT proposal debug2: KEX algorithms: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: peer server KEXINIT proposal debug2: KEX algorithms: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 Last login: Tue Aug 02 10:47:20 2016 from foo # Then do 'kinit' on the client to get a new ticket... debug1: need rekeying debug1: SSH2_MSG_KEXINIT sent debug1: rekeying in progress debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1 debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,null [...] debug2: peer server KEXINIT proposal debug2: KEX algorithms: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 [...] debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: rekeying in progress debug1: rekeying in progress debug1: Server host key: ecdsa-sha2-nistp256 SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E The authenticity of host 'server.example.com (10.0.0.1)' can't be established. ECDSA key fingerprint is SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E. Are you sure you want to continue connecting (yes/no)? Host key verification failed. It looks like the list of KEX algorithms differs between the initial connection, and the rekeying. This behaviour seems to occur with a client running 16.04 (openssh- client 1:7.2p2-4ubuntu1) but not on 15.10 (openssh-client 1:6.9p1-2ubuntu0.2). ssh_config is as follows: HashKnownHosts no GSSAPIAuthentication yes GSSAPIDelegateCredentials yes GSSAPIRenewalForcesRekey yes GSSAPITrustDNS yes GSSAPIKeyExchange yes ForwardX11 yes ForwardX11Trusted yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1608965/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1618719] Re: scp1 reports ssh1 is not supported
Xenial is now in Extended Security Maintenance and this bug doesn't qualify for it, so this bug won't be fixed in that release. ** Changed in: openssh (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1618719 Title: scp1 reports ssh1 is not supported Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Won't Fix Bug description: For getting ssh protocol 1 support I installed the package openssh-client-ssh1. This works with .ssh/config host entries, when omitting any "Protocol 1" lines, but calling "ssh1 -1 host". This package also has the command scp1 included, but this command doesn't have ssh protocol 1 support: > corben@ubuntu:~$ scp1 -1 host:/path/to/file . > ssh1 is not supported Is the ssh protocol 1 support not included for scp1 during compile time? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1618719/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
This bug was fixed in the package apache2 - 2.4.29-1ubuntu4.19 --- apache2 (2.4.29-1ubuntu4.19) bionic; urgency=medium * d/apache2ctl: Also use systemd for graceful if it is in use. (LP: #1832182) - This extends an earlier fix for the start command to behave similarly for restart / graceful. Fixes service failures on unattended upgrade. -- Bryce Harrington Tue, 28 Sep 2021 22:27:27 + ** Changed in: apache2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Xenial: Won't Fix Status in apache2 source package in Bionic: Fix Released Status in apache2 source package in Focal: Fix Released Status in apache2 source package in Groovy: Won't Fix Status in apache2 source package in Hirsute: Fix Released Status in apache2 package in Debian: New Bug description: [Impact] Unattended upgrade will attempt to gracefully reload the Apache2 httpd service, but it reloads apache directly, not via systemd, so systemctl will mis-report the true status. This can cause unexpected and unnecessary server outages when e.g. upgrading from one LTS to another. [Test Case] root@server:/usr/local/sbin# apache2ctl stop root@server:/usr/local/sbin# apache2ctl graceful httpd not running, trying to start root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: inactive (dead) since Mon 2019-06-10 01:04:13 MDT; 17s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Main PID: 1849 (code=exited, status=0/SUCCESS) Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server systemd[1]: Started The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloading The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloaded The Apache HTTP Server. Jun 10 01:04:13 server apachectl[27370]: httpd (no pid file) not running Output after customizing the apache2ctl script and restarting it: root@server:/usr/local/sbin# apache2ctl_custom graceful Invoking 'systemctl start apache2'. Use 'systemctl status apache2' for more info. root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: active (running) since Mon 2019-06-10 01:04:50 MDT; 4s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Process: 27432 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 27444 (apache2) Tasks: 6 (limit: 2318) CGroup: /system.slice/apache2.service +-27444 /usr/sbin/apache2 -k start +-27448 /usr/sbin/apache2 -k start +-27449 /usr/sbin/apache2 -k start +-27451 /usr/sbin/apache2 -k start +-27454 /usr/sbin/apache2 -k start +-27455 /usr/sbin/apache2 -k start Jun 10 01:04:50 server systemd[1]: Starting The Apache HTTP Server... Jun 10 01:04:50 server systemd[1]: Started The Apache HTTP Server. [Fix] The fix is made somewhat obvious due to the fact that the issue was fixed for "apache2ctl start" in 18.04 LTS by replacing the regular call (which resolves to "/usr/sbin/apache2 -k start") with a check for presence of systemd, followed by an invocation of "systemctl start apache2.service" if that check is affirmative, or falling back to the old start command if that check is negative. Attached to this bug report is a diff of the file before and after I copied the fixed in
[Group.of.nepali.translators] [Bug 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
This bug was fixed in the package apache2 - 2.4.41-4ubuntu3.7 --- apache2 (2.4.41-4ubuntu3.7) focal; urgency=medium * d/apache2ctl: Also use systemd for graceful if it is in use. (LP: #1832182) - This extends an earlier fix for the start command to behave similarly for restart / graceful. Fixes service failures on unattended upgrade. -- Bryce Harrington Tue, 28 Sep 2021 22:28:10 + ** Changed in: apache2 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Xenial: Won't Fix Status in apache2 source package in Bionic: Fix Released Status in apache2 source package in Focal: Fix Released Status in apache2 source package in Groovy: Won't Fix Status in apache2 source package in Hirsute: Fix Released Status in apache2 package in Debian: New Bug description: [Impact] Unattended upgrade will attempt to gracefully reload the Apache2 httpd service, but it reloads apache directly, not via systemd, so systemctl will mis-report the true status. This can cause unexpected and unnecessary server outages when e.g. upgrading from one LTS to another. [Test Case] root@server:/usr/local/sbin# apache2ctl stop root@server:/usr/local/sbin# apache2ctl graceful httpd not running, trying to start root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: inactive (dead) since Mon 2019-06-10 01:04:13 MDT; 17s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Main PID: 1849 (code=exited, status=0/SUCCESS) Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server systemd[1]: Started The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloading The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloaded The Apache HTTP Server. Jun 10 01:04:13 server apachectl[27370]: httpd (no pid file) not running Output after customizing the apache2ctl script and restarting it: root@server:/usr/local/sbin# apache2ctl_custom graceful Invoking 'systemctl start apache2'. Use 'systemctl status apache2' for more info. root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: active (running) since Mon 2019-06-10 01:04:50 MDT; 4s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Process: 27432 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 27444 (apache2) Tasks: 6 (limit: 2318) CGroup: /system.slice/apache2.service +-27444 /usr/sbin/apache2 -k start +-27448 /usr/sbin/apache2 -k start +-27449 /usr/sbin/apache2 -k start +-27451 /usr/sbin/apache2 -k start +-27454 /usr/sbin/apache2 -k start +-27455 /usr/sbin/apache2 -k start Jun 10 01:04:50 server systemd[1]: Starting The Apache HTTP Server... Jun 10 01:04:50 server systemd[1]: Started The Apache HTTP Server. [Fix] The fix is made somewhat obvious due to the fact that the issue was fixed for "apache2ctl start" in 18.04 LTS by replacing the regular call (which resolves to "/usr/sbin/apache2 -k start") with a check for presence of systemd, followed by an invocation of "systemctl start apache2.service" if that check is affirmative, or falling back to the old start command if that check is negative. Attached to this bug report is a diff of the file before and after I copied the fixed invoca
[Group.of.nepali.translators] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
Setting series as wontfix due to end of standard support. This should be fixed from bionic and on. ** Changed in: openssh (Ubuntu Precise) Status: New => Won't Fix ** Changed in: openssh (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1859013 Title: openssh tests use "not valid yet" certificate from 2020, which is now valid Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Precise: Won't Fix Status in openssh source package in Trusty: Won't Fix Status in openssh source package in Xenial: Fix Released Status in openssh source package in Bionic: Fix Released Status in openssh source package in Disco: Won't Fix Status in openssh source package in Eoan: Fix Released Status in openssh source package in Focal: Fix Released Bug description: [Impact] * regression testsuite uses 1st of January 2020 as the date in the future, however that is now in the past making autpkgtests fail. [Test Case] * Autopkgtest must pass [Regression Potential] * Testsuite assertion update only [Other Info] This is a staged update to be rolled up with any other openssh update in the future. fixed in debian https://tracker.debian.org/news/1092767/accepted- openssh-181p1-4-source-into-unstable/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1944926] Re: xenial/linux-oracle: 4.15.0-1082.90~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - main - signed sru-review: - main - meta - signed kernel-stable-master-bug: 1944927 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Wednesday, 06. October 2021 12:51 UTC reason: - promote-to-proposed: Pending -- packages copying to Signing - (signed:P) + promote-to-proposed: Pending -- packages copying to Proposed (main:P + meta:P signed:P) synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-1082.90~16.04.1 meta: 4.15.0.1082.70 signed: 4.15.0-1082.90~16.04.1 source: 4.15.0-1082.90~16.04.1 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Triaged ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - main - signed sru-review: - main - meta - signed kernel-stable-master-bug: 1944927 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Wednesday, 06. October 2021 12:51 UTC + phase: Testing + phase-changed: Wednesday, 06. October 2021 13:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Pending -- packages copying to Proposed (main:P - meta:P signed:P) + regression-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-1082.90~16.04.1 meta: 4.15.0.1082.70 signed: 4.15.0-1082.90~16.04.1 source: 4.15.0-1082.90~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1944926 Title: xenial/linux-oracle: 4.15.0-1082.90~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Triaged Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - main - signed sru-review: - main - meta - signed kernel-stable-master-bug: 1944927 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 06. October 2021 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-1082.90~16.04.1 meta
[Group.of.nepali.translators] [Bug 1944926] Re: xenial/linux-oracle: 4.15.0-1082.90~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - main - signed sru-review: - main - meta - signed kernel-stable-master-bug: 1944927 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Tuesday, 05. October 2021 19:52 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 06. October 2021 12:51 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-1082.90~16.04.1 meta: 4.15.0.1082.70 signed: 4.15.0-1082.90~16.04.1 source: 4.15.0-1082.90~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1944926 Title: xenial/linux-oracle: 4.15.0-1082.90~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - main - signed sru-review: - main - meta - signed kernel-stable-master-bug: 1944927 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Wednesday, 06. October 2021 12:51 UTC reason: promote-to-proposed: Stalled -- packages copying to Signing (signed:B) synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-1082.90~16.04.1 meta: 4.15.0.1082.70 signed: 4.15.0-1082.90~16.04.1 source: 4.15.0-1082.90~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1944926/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1945527] Re: Update tzdata to version 2021a-2
This bug was fixed in the package tzdata - 2021a-2ubuntu0.20.04
---
tzdata (2021a-2ubuntu0.20.04) focal; urgency=medium
* Merge from Debian unstable (LP: #1945527). Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them
to 2021a1.
-- Brian Murray Wed, 29 Sep 2021 12:14:22 -0700
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 27'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1945527] Re: Update tzdata to version 2021a-2
This bug was fixed in the package tzdata - 2021a-2ubuntu0.21.04
---
tzdata (2021a-2ubuntu0.21.04) hirsute; urgency=medium
* Merge from Debian unstable (LP: #1945527). Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them
to 2021a1.
-- Brian Murray Wed, 29 Sep 2021 12:14:22 -0700
** Changed in: tzdata (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 27'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
