[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
Thanks for the review Andreas. Since it sounds like the test case is
invalid, this SRU attempt will have to be abandoned. I'll return this
to the backlog for the reporter to re-clarify reproduction steps, for
re-assessment in triage.
@Rene please see Andreas' feedback.
** Changed in: cyrus-sasl2 (Ubuntu Noble)
Status: Fix Committed => New
** Changed in: cyrus-sasl2 (Ubuntu Noble)
Assignee: Bryce Harrington (bryce) => (unassigned)
** Tags removed: server-todo
** Tags removed: bite-size
** Changed in: cyrus-sasl2 (Ubuntu Noble)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078851
Title:
saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928493] Re: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: (exceeded timeout to shutdown for restart?)
*** This bug is a duplicate of bug 1957013 *** https://bugs.launchpad.net/bugs/1957013 ** This bug has been marked a duplicate of bug 1957013 package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to install/upgrade: (exceeded timeout to shutdown for restart?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928493 Title: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: (exceeded timeout to shutdown for restart?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078319] Re: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2019003 *** https://bugs.launchpad.net/bugs/2019003 ** This bug has been marked a duplicate of bug 2019003 package mysql-server-8.0 8.0.33-0ubuntu0.22.04.1 failed to install/upgrade: Can't start server: Bind on TCP/IP port: Address already in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078319 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2078319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077725] Re: CIFS client reports 100% disk usage when rpc-quotad is started
Hi Stefan, thank you for providing the steps to reproduce, and taking the time to write them up to this level of detail. This will be super helpful in moving forward with the bug. The next step, as Athos mentioned in comment #8 is to isolate the upstream fix needed. Hopefully now that you've outlined a test case, there's a path to doing that. (Possibly this will require a git bisection search, which can be very effective though time consuming). I've added this to my team's list of items to discuss at our bug review meeting next Wednesday. I should set expectations though, with the caveat that our team's schedule is pretty full through at least to the end of October. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077725 Title: CIFS client reports 100% disk usage when rpc-quotad is started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2077725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077725] Re: CIFS client reports 100% disk usage when rpc-quotad is started
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077725 Title: CIFS client reports 100% disk usage when rpc-quotad is started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2077725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079015] Re: Redundant systemd unit smartd.service
lrwxrwxrwx 1 bryce bryce17 Nov 8 2022 smartmontools.service -> ../smartd.service Looks like the service files are intended to be symlinks, so it does not appear intended that both should be installed by the user. I assume the intent was to rename upstream's service rather than to provide two, so something does feel like it's not quite right here. I suspect this is related to this debian bug regarding a dangling symlink: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959917 So they appear to be aware of a problem but there hasn't been an update in a while. Would you mind inquiring on the Debian bug about the problem? Since we currently auto-sync the package from Debian, if the cleanup is done in Debian we'll pick up the fix in our next release automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079015 Title: Redundant systemd unit smartd.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/2079015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079015] Re: Redundant systemd unit smartd.service
** Bug watch added: Debian Bug tracker #959917 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959917 ** Also affects: smartmontools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959917 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079015 Title: Redundant systemd unit smartd.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/2079015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077893] Re: Current exim version have crashes inside PCRE2 lib
Excellent Dmitry, thanks for verifying that. I'm not sure whether we should proceed at this point with all 6 patches or try to whittle them down to a more minimal fix. I'm leaning towards the former since from the Gentoo bug it sounds like they came up as part of the stabilization process for this repair. Typically for Stable Release Updates (SRUs), we like to have detailed steps to reproduce the bug, but in this case it doesn't look like we're able to generate the right workloads synthetically to trigger it (per Andreas' attempt above). However in cases like these if someone that is able to reproduce it reliably can volunteer to handle verifying the fix, we can proceed with the SRU. Would you be willing to help us with this? Meanwhile, the next action to start the SRU process is to prepare the SRU document using the standard template. This process is documented at https://canonical-sru-docs.readthedocs- hosted.com/en/latest/howto/standard/, specifically step #4. If you'd like to take a shot at completing step #4 it would help move things along. Otherwise, someone from my team should be able to tackle that by next week, and then do steps 5-7. Step #8 is the verifying the fix (mentioned in previous paragraph) that we'd need you to do. Let us know if this plan will work for you. ** Changed in: exim4 (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077893 Title: Current exim version have crashes inside PCRE2 lib To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/2077893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Description changed: [Impact] - Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) + Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) saslauthd itself will appear to start successfully, but e.g. postfix will be unable to authenticate, effectively preventing outgoing mail submitted via smtp. This worked properly on prior LTS releases, but breaks outgoing mail service on upgrade to 24.04. [Workaround] # systemctl edit saslauthd.service Then, put the following lines inside the file: [Service] Group=sasl Save the file, and restart the service. You should now see the right permissions/owner/group under /run/saslauthd. [Test Case] $ sudo apt-get install postfix sasl2-bin $ sudo systemctl enable saslauthd $ ls -ld /run/saslauthd/ drwx--x--- 2 root sasl 40 Sep 24 23:07 /run/saslauthd/ $ sudo systemctl start saslauthd $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root root 140 Sep 24 23:09 /run/saslauthd [Where Problems Could Occur] - Since the fix is only in packaging and deals only with permissions, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) + Since the fix is only in packaging and deals only with group ownership, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) - Notably, the fix corrects permissions on the *directory* itself, but not - on its contents. Since the problem is that root ownership of the - directory prevents non-root users from adding non-root owned files - there, it is unlikely this situation would crop up in practice, and if - it did should be reviewed and analyzed by the user. (We would not want - to auto-fix unknown root-owned file permissions to non-root.) + Notably, the fix corrects group ownership permissions on the *directory* + itself, but not on its contents. The service itself continues to run as + the same user, so it should not cause any read/write problems, but if + there are any issues pertaining to *group* ownership, those may be + relate to this change. [Original Report] Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: Incomplete => New ** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: New => In Progress ** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077893] Re: Current exim version have crashes inside PCRE2 lib
I've created a second PPA that has a variation of the earlier package, that contains only the first patch in the set. Testing this would help verify whether the full set should be SRU'd or just the specific fix. https://launchpad.net/~bryce/+archive/ubuntu/exim4-sru-lp2077893-single- patch @Dmitry, after you've sufficiently tested the exim4-sru-lp2077893 PPA, can you please also test this exim4-sru-lp2077893-single-patch as well, using the same test e-mail? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077893 Title: Current exim version have crashes inside PCRE2 lib To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/2077893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083478] Re: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory
Hi docBrian, Unfortunately the collected log files don't reveal what caused this installation failure, however it looks like it may have been due to local modifications of config files in /etc/postfix/. Does that sound familiar? Or is it possible there was an earlier attempt to purge or remove postfix that may have left things in an inconsistent state? ** Changed in: postfix (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083478 Title: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2083478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081996] Re: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
Thanks for the additional logs. Looking at your attached pg_upgradecluster.OUT I see what you mean that it looks like it succeeded in porting the 'postgres' and 'template1' databases, but presumably you expected another database(s) to upgrade? Are those databases included in the 'main' cluster? If they're in a different cluster try running pg_upgradecluster on that one? I don't think it is going to be necessary to run it as the 'postgres' user; it looks like from this script's output that it's changing user ok. However, it does take an optional 'newdatadir' argument that you may find useful for troubleshooting purposes. Btw, you probably already know this but pg_upgradecluster is a debian/ubuntu-specific proxy script to simplify the database upgrade process, and certainly we'd like to make it work properly. But if you're looking for a quicker fix you may want to look into upstream's (more manual) steps for upgrading databases. ** Changed in: postgresql-16 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081996 Title: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081996] Re: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
** Changed in: postgresql-16 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081996 Title: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820870] Re: package postfix 2.8.1-1~lucid1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 75
[Ubuntu 10.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820870 Title: package postfix 2.8.1-1~lucid1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/820870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897632] Re: package postfix 2.8.5-2~build0.11.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 75
[Ubuntu 11.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897632 Title: package postfix 2.8.5-2~build0.11.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/897632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306710] Re: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
[Ubuntu 12.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306710 Title: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1306710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031795] Re: package postfix 2.9.3-2~12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Ubuntu 12.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031795 Title: package postfix 2.9.3-2~12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1031795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367823] Re: package postfix (not installed) failed to install/upgrade: új pre-installation szkript alfolyamat 5 hibakóddal kilépett
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367823 Title: package postfix (not installed) failed to install/upgrade: új pre- installation szkript alfolyamat 5 hibakóddal kilépett To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1367823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409371] Re: package postfix 2.11.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409371 Title: package postfix 2.11.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1409371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418428] Re: package postfix (not installed) failed to install/upgrade: podproces nowy skrypt pre-installation zwrócił kod błędu 1
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418428 Title: package postfix (not installed) failed to install/upgrade: podproces nowy skrypt pre-installation zwrócił kod błędu 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1418428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448085] Re: package postfix-mysql 2.11.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448085 Title: package postfix-mysql 2.11.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1448085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558348] Re: package postfix 2.11.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558348 Title: package postfix 2.11.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1558348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575266] Re: package postfix 2.11.0-1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
[Ubuntu 14.04 is no longer actively supported] ** Changed in: postfix (Ubuntu) Status: New => Invalid ** Changed in: postfix (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575266 Title: package postfix 2.11.0-1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1575266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083478] Re: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory
** Summary changed: - package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade: new postfix package pre-installation script subprocess returned error exit status 127 + package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083478 Title: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2083478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081947] Re: postfix-pgsql 3.8.6-1build2 failed to install/upgrade with exit status 1: no 'map create' support for this type: pgsql
** Summary changed: - package postfix-pgsql 3.8.6-1build2 failed to install/upgrade: installed postfix-pgsql package post-installation script subprocess returned error exit status 1 + postfix-pgsql 3.8.6-1build2 failed to install/upgrade with exit status 1: no 'map create' support for this type: pgsql -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081947 Title: postfix-pgsql 3.8.6-1build2 failed to install/upgrade with exit status 1: no 'map create' support for this type: pgsql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2081947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083478] Re: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade: new postfix package pre-installation script subprocess returned error exit status 127
** Description changed: - Unknown... + During installation there are errors about a missing master.cf file: + + Preparing to unpack .../postfix_3.6.4-1ubuntu1.3_amd64.deb ... + /etc/postfix/main.cf.proto modified, not updating. + /etc/postfix/master.cf.proto modified, not updating. + grep: /etc/postfix/master.cf: No such file or directory + grep: /etc/postfix/master.cf: No such file or directory + /var/lib/dpkg/tmp.ci/preinst: 175: retry_warning: not found + dpkg: error processing archive /var/cache/apt/archives/postfix_3.6.4-1ubuntu1.3_amd64.deb (--unpack): + new postfix package pre-installation script subprocess returned error exit status 127 + ProblemType: Package DistroRelease: Ubuntu 22.04 Package: postfix 3.6.4-1ubuntu1.3 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.6 AptOrdering: - postfix:amd64: Install - xxd:amd64: Install - vim-tiny:amd64: Install - vim-common:amd64: Install - NULL: ConfigurePending + postfix:amd64: Install + xxd:amd64: Install + vim-tiny:amd64: Install + vim-common:amd64: Install + NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 1 14:19:50 2024 Dependencies: - + DpkgHistoryLog: - Start-Date: 2024-10-01 14:19:49 - Commandline: apt-get -y install vim-common vim-tiny xxd - Upgrade: xxd:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), vim-common:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), vim-tiny:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), postfix:amd64 (3.6.4-1ubuntu1.3, 3.6.4-1ubuntu1.3) + Start-Date: 2024-10-01 14:19:49 + Commandline: apt-get -y install vim-common vim-tiny xxd + Upgrade: xxd:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), vim-common:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), vim-tiny:amd64 (2:8.2.3995-1ubuntu2.18, 2:8.2.3995-1ubuntu2.19), postfix:amd64 (3.6.4-1ubuntu1.3, 3.6.4-1ubuntu1.3) ErrorMessage: new postfix package pre-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2024-08-25 (38 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04.1 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.21.1ubuntu2.3 - apt 2.4.13 + dpkg 1.21.1ubuntu2.3 + apt 2.4.13 SourcePackage: postfix Title: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade: new postfix package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083478 Title: package postfix 3.6.4-1ubuntu1.3 failed to install/upgrade with exit status 127: /etc/postfix/master.cf: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2083478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077893] Re: Current exim version have crashes inside PCRE2 lib
I've backported the aforementioned commits to noble and set up a PPA for testing purposes: https://launchpad.net/~bryce/+archive/ubuntu/exim4-sru-lp2077893/+packages The first patch sounds like it's the fix for this specific issue by adding store_reset() calls as appropriate, and the second patch fixes a related issue with regex functionality with store_reset() calls as well. The other four are smaller fixups to other parts of the regex code where similar problems occur. It is possible only the first patch is strictly required for fixing this specific bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077893 Title: Current exim version have crashes inside PCRE2 lib To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/2077893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
My takeaway from the above is that the daemon service itself still runs as root, just the group name changes, so for the specific scenario raised in question #2 it looks like the daemon's read access to root only files like shadow would be unaffected. Similarly, the issue I raised in "Where Problems May Occur" due to root ownership of files in /var/run/saslauthd would not be exhibited by read (or write) errors by the daemon itself. Indeed, it appears the contents of /var/run/saslauthd are cleared when the daemon stops, or is restarted, so if there *was* an issue with files in the run directory it should present immediately at service stop/start/restart: $ sudo systemctl stop saslauthd $ sudo ls /var/run/saslauthd/ -l ls: cannot access '/var/run/saslauthd/': No such file or directory $ sudo systemctl start saslauthd $ sudo ls /var/run/saslauthd/ -l total 968 -rw--- 1 root sasl 0 Oct 3 16:38 cache.flock -rw--- 1 root sasl 986112 Oct 3 16:38 cache.mmap srwxrwxrwx 1 root sasl 0 Oct 3 16:38 mux -rw--- 1 root sasl 0 Oct 3 16:38 mux.accept -rw--- 1 root sasl 6 Oct 3 16:38 saslauthd.pid $ sudo systemctl restart saslauthd $ sudo ls /var/run/saslauthd/ -l total 968 -rw--- 1 root sasl 0 Oct 3 16:38 cache.flock -rw--- 1 root sasl 986112 Oct 3 16:38 cache.mmap srwxrwxrwx 1 root sasl 0 Oct 3 16:38 mux -rw--- 1 root sasl 0 Oct 3 16:38 mux.accept -rw--- 1 root sasl 6 Oct 3 16:38 saslauthd.pid $ sleep 60 $ sudo systemctl restart saslauthd $ sudo ls /var/run/saslauthd/ -l total 968 -rw--- 1 root sasl 0 Oct 3 16:39 cache.flock -rw--- 1 root sasl 986112 Oct 3 16:39 cache.mmap srwxrwxrwx 1 root sasl 0 Oct 3 16:39 mux -rw--- 1 root sasl 0 Oct 3 16:39 mux.accept -rw--- 1 root sasl 6 Oct 3 16:39 saslauthd.pid $ sleep 120 $ sudo ls /var/run/saslauthd/ -l total 968 -rw--- 1 root sasl 0 Oct 3 16:39 cache.flock -rw--- 1 root sasl 986112 Oct 3 16:39 cache.mmap srwxrwxrwx 1 root sasl 0 Oct 3 16:39 mux -rw--- 1 root sasl 0 Oct 3 16:39 mux.accept -rw--- 1 root sasl 6 Oct 3 16:39 saslauthd.pid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
A. sasl2 not installed: $ apt-cache policy sasl2-bin sasl2-bin: Installed: (none) Candidate: 2.1.28+dfsg1-5ubuntu3.2~oracular1 Version table: 2.1.28+dfsg1-5ubuntu3.2~oracular1 500 500 https://ppa.launchpadcontent.net/bryce/cyrus-sasl2-sru-lp2078851/ubuntu noble/main amd64 Packages 2.1.28+dfsg1-5ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 2.1.28+dfsg1-5ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages $ ls -ld /run/saslauthd ls: cannot access '/run/saslauthd': No such file or directory $ ps aux | grep sasl2 | grep -v grep $ B. Installing from noble-updates $ apt-cache policy sasl2-bin | grep Installed: Installed: 2.1.28+dfsg1-5ubuntu3.1 $ ls -ld /run/saslauthd drwx--x--- 2 root sasl 40 Oct 3 16:14 /run/saslauthd/ $ ps aux | grep sasl2 | grep -v grep $ sudo systemctl enable saslauthd Synchronizing state of saslauthd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable saslauthd Created symlink /etc/systemd/system/multi-user.target.wants/saslauthd.service → /usr/lib/systemd/system/saslauthd.service. $ ls -ld /run/saslauthd drwx--x--- 2 root sasl 40 Oct 3 16:14 /run/saslauthd/ $ sudo ls /var/run/saslauthd/ -l total 0 $ ls -l /usr/lib/systemd/system/saslauthd.service -rw-r--r-- 1 root root 326 Apr 5 19:59 /usr/lib/systemd/system/saslauthd.service $ sudo systemctl status saslauthd ○ saslauthd.service - SASL Authentication Daemon Loaded: loaded (/usr/lib/systemd/system/saslauthd.service; enabled; preset: enabled) Active: inactive (dead) Docs: man:saslauthd(8) Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble systemd[1]: saslauthd.service: Deactivated successfully. Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Stopped saslauthd.service - SASL Authentication Daemon. Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Starting saslauthd.service - SASL Authentication Daemon... Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble saslauthd[9743]: : master pid is: 9743 Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble saslauthd[9743]: : listening on socket: /var/run/saslauthd/mux Sep 24 23:35:06 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Started saslauthd.service - SASL Authentication Daemon. Oct 03 16:11:13 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Stopping saslauthd.service - SASL Authentication Daemon... Oct 03 16:11:13 cyrus-sasl2-sru-lp2078851-noble saslauthd[9743]: : master exited: 9743 Oct 03 16:11:13 cyrus-sasl2-sru-lp2078851-noble systemd[1]: saslauthd.service: Deactivated successfully. Oct 03 16:11:13 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Stopped saslauthd.service - SASL Authentication Daemon. $ sudo systemctl start saslauthd $ ps aux | grep sasl | grep -v grep root 34437 0.0 0.0 19732 1104 ?Ss 16:19 0:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 34438 0.0 0.0 19732 1104 ?S16:19 0:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 34439 0.0 0.0 19732 1104 ?S16:19 0:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 34440 0.0 0.0 19732 1104 ?S16:19 0:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 34441 0.0 0.0 19732 1104 ?S16:19 0:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 $ sudo systemctl status saslauthd ● saslauthd.service - SASL Authentication Daemon Loaded: loaded (/usr/lib/systemd/system/saslauthd.service; enabled; preset: enabled) Active: active (running) since Thu 2024-10-03 16:19:49 UTC; 1min 15s ago Docs: man:saslauthd(8) Process: 34436 ExecStart=/usr/sbin/saslauthd -a $MECHANISMS $MECH_OPTIONS $OPTIONS -n $THREADS (code=exited, status=0/SUCCESS) Main PID: 34437 (saslauthd) Tasks: 5 (limit: 76969) Memory: 2.9M () CPU: 8ms CGroup: /system.slice/saslauthd.service ├─34437 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 ├─34438 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 ├─34439 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 ├─34440 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 └─34441 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 Oct 03 16:19:49 cyrus-sasl2-sru-lp2078851-noble systemd[1]: Starting saslauthd.service - SASL Authentication Daemon... Oct 03 16:19:49 cyrus-sasl2-sru-lp2078851-noble saslauthd[34437]: : master pid is: 34437 Oct 03 16:19:49 cyrus-sasl2-sru-lp2078851-noble saslauthd[34437]: : listening on socket: /var/run/saslauthd/mux Oct 03 16:19:49 cyrus-sasl2-sru-lp2078851-noble
[Bug 2077893] Re: Current exim version have crashes inside PCRE2 lib
** Also affects: exim via http://bugs.exim.org/show_bug.cgi?id=3047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077893 Title: Current exim version have crashes inside PCRE2 lib To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/2077893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
> 1. Is this bug that saslauthd doesn't work in Noble at all because the permissions are wrong? Or only in certain circumstances, and in which case, which ones? The reporter did not indicate what their specific failure mode was, but some examples of where this has been a problem in the past have related to authentication or service restart. > 2. Is it possible that somebody is successfully using saslauthd running as root, and changing the group of the service to sasl would break them? For example, what if they have saslauthd configured to read something else that is only readable by root? What about shadow? I mentioned in the "Where Problems Might Occur" section that if files are created in the /run directory with root permissions, that could potentially cause issues. Similarly, I suppose if they had a configuration that was making use of the service root permissions, I suppose that could potentially be an issue as well. Do you feel either of those would be disqualifying for SRU? > 3. Seems like this could do with verifying that saslauthd is working > end-to-end in at least one scenario. See: "The Test Plan verifies a technical > change but not the user story" as well as "Test Plan only covers the fix, and > not general use of the package to make sure that it still works after the > update" from > https://canonical-sru-docs.readthedocs-hosted.com/en/latest/howto/common-issues/#test-plan > 4. Can we add a dep8 test for saslauthd to both do the verification and also > prevent regressions in the future? As Andreas mentions, there is a saslauthd DEP8 test. This issue crops up only after the service is restarted, and while the test cause does do a service restart, the subsequent checks may not be thorough enough to trigger the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080891] Re: pcsd complains: WebUI is not a part of pcs repository but it has its own repository.
Thomas, Ubuntu 24.04 is downstream of Debian's pcs 0.11.7-1 package, which appears to be included both in Debian trixie and sid (unstable). There is not a pcs-web-ui package but presumably that is what would need to be created, and what should be requested. In looking at the source for 20.04 and 22.04 compared with current, I see that indeed the package used to include the javascript code, but it was removed by upstream in the 0.11.1 release. Debian followed suit and removed the relevant packaging in 0.11.1-1: https://salsa.debian.org/ha- team/pcs/-/commit/285b5d72df2e31ad1516ff507062e7d7a3dc0ca2 I also notice RedHat's changes regarding this component: https://issues.redhat.com/browse/RHEL-29739 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080891 Title: pcsd complains: WebUI is not a part of pcs repository but it has its own repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/2080891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082086] Re: Expect build failure on non-amd64 architectures
** Tags added: ftbfs ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082086 Title: Expect build failure on non-amd64 architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2082086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679392] Re: Missing dep8 tests
** Changed in: sg3-utils (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679392 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sg3-utils/+bug/1679392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077893] Re: Current exim version have crashes inside PCRE2 lib
The bug mentions several additional comments: https://git.exim.org/exim.git/patch/b4e7527561f1 https://git.exim.org/exim.git/patch/35aacb69f5c8 https://git.exim.org/exim.git/patch/84add256b346 https://git.exim.org/exim.git/patch/6fcb3173d64e https://git.exim.org/exim.git/patch/a173a4376d16 https://git.exim.org/exim.git/patch/44b3172e3694 @Athos, for the test were you looking at what's in Comment #23? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077893 Title: Current exim version have crashes inside PCRE2 lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2077893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080891] Re: pcsd complains: WebUI is not a part of pcs repository but it has its own repository.
Hi Thomas, Yes, I can confirm the WebUI component is separate from the pcs source package. This is actually fairly typical - many open source software packages have 2nd or 3rd party add-ons or other associated tools and packages. In this particular case, WebUI appears to require installation via npm, which suggests there may be other web dependencies. I've not looked into what those are, but often they need to be kept to much newer versions than are typically tracked in Apt. Possibly the upstream wishes you to manually install so you can get latest versions of everything. I'll leave this as a wishlist against pcs in our backlog, however I don't expect Ubuntu will take action on this. If you feel strongly this should be included in Apt, I'd recommend forwarding this request to Debian, as they'd be in a better position to determine how best to package it. ** Tags removed: server-triage-discuss ** Changed in: corosync (Ubuntu) Status: New => Invalid ** Changed in: pacemaker (Ubuntu) Status: New => Invalid ** Changed in: pcs (Ubuntu) Importance: Undecided => Wishlist ** Changed in: pcs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080891 Title: pcsd complains: WebUI is not a part of pcs repository but it has its own repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/2080891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679392] Re: Missing dep8 tests
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/472834 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679392 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sg3-utils/+bug/1679392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082011] Re: htop memory leak
The video does not play properly, and in any case a video is generally not a good way to report bugs, especially memory leaks. There are many tools for diagnosing memory leaks, including htop itself. Valgrind, gdb, strace, and similar can be effective for doing this. ** Changed in: htop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082011 Title: htop memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/2082011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081994] Re: squid 5.9 crash during ipv6 requests
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081994 Title: squid 5.9 crash during ipv6 requests To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/2081994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081978] Re: boto3 completely unusable: ImportError: cannot import name 'JSONDecodeError' from 'simplejson' (unknown location)
I get an error about missing region when I run it:
triage-oracular+24.10: ~$ apt-cache policy python3-boto3
python3-boto3:
Installed: 1.34.46+dfsg-1ubuntu1
Candidate: 1.34.46+dfsg-1ubuntu1
Version table:
*** 1.34.46+dfsg-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages
100 /var/lib/dpkg/status
triage-oracular+24.10: ~$ python3 -c 'import boto3; client=boto3.client("ec2")'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/boto3/__init__.py", line 92, in client
return _get_default_session().client(*args, **kwargs)
^^
File "/usr/lib/python3/dist-packages/boto3/session.py", line 299, in client
return self._session.create_client(
File "/usr/lib/python3/dist-packages/botocore/session.py", line 997, in
create_client
client = client_creator.create_client(
^
File "/usr/lib/python3/dist-packages/botocore/client.py", line 161, in
create_client
client_args = self._get_client_args(
^^
File "/usr/lib/python3/dist-packages/botocore/client.py", line 508, in
_get_client_args
return args_creator.get_client_args(
^
File "/usr/lib/python3/dist-packages/botocore/args.py", line 100, in
get_client_args
final_args = self.compute_client_args(
^
File "/usr/lib/python3/dist-packages/botocore/args.py", line 219, in
compute_client_args
endpoint_config = self._compute_endpoint_config(
^^
File "/usr/lib/python3/dist-packages/botocore/args.py", line 369, in
_compute_endpoint_config
return self._resolve_endpoint(**resolve_endpoint_kwargs)
^
File "/usr/lib/python3/dist-packages/botocore/args.py", line 474, in
_resolve_endpoint
return endpoint_bridge.resolve(
File "/usr/lib/python3/dist-packages/botocore/client.py", line 613, in resolve
resolved = self.endpoint_resolver.construct_endpoint(
^^
File "/usr/lib/python3/dist-packages/botocore/regions.py", line 229, in
construct_endpoint
result = self._endpoint_for_partition(
^
File "/usr/lib/python3/dist-packages/botocore/regions.py", line 277, in
_endpoint_for_partition
raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.
When I specify the region, it runs fine:
triage-oracular+24.10: ~$ python3 -c 'import boto3; client=boto3.client("ec2",
region_name="us-west-2")'
triage-oracular+24.10: ~$ echo $?
0
However, the "cannot import name 'JSONDecodeError' from 'simplejson'"
suggests a package installation issue of some sort. Can you try running
this?
triage-oracular+24.10: ~$ python3
Python 3.12.6 (main, Sep 7 2024, 14:20:15) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from simplejson import JSONDecodeError
>>>
>>>
Also, do you have python3-simplejson installed on your system? If not,
does the issue go away if you manually install it?
** Changed in: python-boto3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081978
Title:
boto3 completely unusable: ImportError: cannot import name
'JSONDecodeError' from 'simplejson' (unknown location)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2081978/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081996] Re: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
pg_upgradecluster.OUT doesn't appear to be included in the APPORT.info file you attached; that doesn't appear to include log data at all. I'm not sure what data would help Athos the most, so hopefully he can follow up, but I would suggest maybe attaching these: /var/log/apt/term.log* /var/log/apt/history.log* Make sure to get the ones from the day of your upgrade. They will show the upgrade process and results, and if there were any errors. The postgres log files may also be pertinent, they should be at /var/log/postgresql or collected from journalctl. ** Changed in: postgresql-16 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081996 Title: After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081947] Re: package postfix-pgsql 3.8.6-1build2 failed to install/upgrade: installed postfix-pgsql package post-installation script subprocess returned error exit status 1
It looks like from your upgrade log, that the upgrader noticed several config file issues, but was told to overwrite the configs, which indeed could leave your system potentially in a bad state: https://launchpadlibrarian.net/751262355/DpkgTerminalLog.txt You should probably re-review the before / after versions of each of those config files to see was lost and how to correct your system. Otherwise, I think a reinstallation of the VM may be your best option. If you wish to explain the upgrade process you followed, we may be able to make some suggestions. If your process involved use of tools or documentation provided by DigitalOcean, you may need to work through their support channels. ** Changed in: postfix (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081947 Title: package postfix-pgsql 3.8.6-1build2 failed to install/upgrade: installed postfix-pgsql package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2081947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081994] Re: squid 5.9 crash during ipv6 requests
Thanks for reporting this issue and flagging the upstream bug+patch. I took a quick look at the code changes and they look worth backporting. The second crash you saw after disabling ipv6 may be a side effect and/or secondary bug. I'd be curious if there had been anything in your journalctl relating to squid prior to the first crash, if you still have the logs? Is there anything relevant in /var/log/apport.log? You mentioned you started seeing this after upgrading to 22.04.5. Were you upgrading from 22.04.4, or 20.04? Do you recall what version of squid you were successfully running previously? Your /var/log/apt/history.log* and term.log* can be useful in examining version changes. I am not (yet) spotting other mentions of this misbehavior by other squid users, which makes me wonder if there is something unique in your case that may assist in figuring out how to reproduce it. Can you see if there are particular URLs or usage behaviors that trigger the process exits? Can you attach your /etc/squid/squid.conf as well? If it is not possible to determine steps to reproduce the crash, we may need to have you try to gather a crash dump yourself. Squid provides a guideline for how to do this: https://wiki.squid- cache.org/SquidFaq/BugReporting ** Changed in: squid (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081994 Title: squid 5.9 crash during ipv6 requests To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/2081994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081994] Re: squid 5.9 crash during ipv6 requests
** Bug watch added: Squid Bugzilla #5154 http://bugs.squid-cache.org/show_bug.cgi?id=5154 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=5154 Importance: Unknown Status: Unknown ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081994 Title: squid 5.9 crash during ipv6 requests To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/2081994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
A PPA with the fix for noble is here: https://launchpad.net/~bryce/+archive/ubuntu/cyrus-sasl2-sru-lp2078851 $ sudo add-apt-repository ppa:bryce/cyrus-sasl2-sru-lp2078851 ... $ apt-cache policy sasl2-bin sasl2-bin: Installed: 2.1.28+dfsg1-5ubuntu3.1 Candidate: 2.1.28+dfsg1-5ubuntu3.2~oracular1 Version table: 2.1.28+dfsg1-5ubuntu3.2~oracular1 500 500 https://ppa.launchpadcontent.net/bryce/cyrus-sasl2-sru-lp2078851/ubuntu noble/main amd64 Packages *** 2.1.28+dfsg1-5ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.1.28+dfsg1-5ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages $ sudo apt-get upgrade ... $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root sasl 140 Sep 24 23:35 /run/saslauthd// $ sudo systemctl start saslauthd $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root sasl 140 Sep 24 23:35 /run/saslauthd// -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Description changed: - Folder group permission of /var/spool/postfix/var/run/saslauthd gets - reset to "root" (should be "sasl") every time saslauthd gets restarted. + [Impact] + Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) + + [Workaround] + # systemctl edit saslauthd.service + + Then, put the following lines inside the file: + + [Service] + Group=sasl + + Save the file, and restart the service. You should now see the right + permissions/owner/group under /run/saslauthd. + + + [Test Case] + $ sudo apt-get install postfix sasl2-bin + $ sudo systemctl enable saslauthd + $ ls -ld /run/saslauthd/ + drwx--x--- 2 root sasl 40 Sep 24 23:07 /run/saslauthd/ + + $ sudo systemctl start saslauthd + drwxr-xr-x 2 root root 140 Sep 24 23:09 /run/saslauthd + + + [Where Problems Could Occur] + Since the fix is only in packaging and deals only with permissions, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) + + Notably, the fix corrects permissions on the *directory* itself, but not + on its contents. Since the problem is that root ownership of the + directory prevents non-root users from adding non-root owned files + there, it is unlikely this situation would crop up in practice, and if + it did should be reviewed and analyzed by the user. (We would not want + to auto-fix unknown root-owned file permissions to non-root.) + + + [Original Report] + Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Changed in: cyrus-sasl2 (Ubuntu Noble) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080891] Re: pcsd complains: WebUI is not a part of pcs repository but it has its own repository.
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080891 Title: pcsd complains: WebUI is not a part of pcs repository but it has its own repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/2080891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081241] [NEW] Nginx apport hook should include /etc/nginx/nginx.conf
Public bug reported: Per LP: #2080915, automatically filed install/upgrade bugs should include the config file. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081241 Title: Nginx apport hook should include /etc/nginx/nginx.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081090] Re: gutenprint FTBFS due to 64-bit restriction
The binaries supplied by this package are: Package-List: escputil deb utils optional arch=any gimp-gutenprint deb graphics optional arch=any gutenprint-doc deb doc optional arch=all gutenprint-locales deb libs optional arch=all libgutenprint-common deb libs optional arch=all libgutenprint-dev deb libdevel optional arch=any libgutenprint-doc deb doc optional arch=all libgutenprint9 deb libs optional arch=any libgutenprintui2-2 deb libs optional arch=any libgutenprintui2-dev deb libdevel optional arch=any printer-driver-gutenprint deb graphics optional arch=any Of those, only the driver itself appears to have rdepends beyond gutenprint: printer-driver-gutenprint Reverse Depends: gutenprint-doc ubuntu-mate-desktop ubuntu-mate-core ubuntu-budgie-desktop printer-driver-all-enforce printer-driver-all lubuntu-desktop cups-backend-bjnp Unfortunately, simply removing gutenprint's binaries on armhf looks like it would have broad repercussions. Someone involved in the desktop and/or printing stack maintenance will need to evaluate how to handle this issue. ** Description changed: The FTBFS[0] report shows an issue for gutenprint: - The following packages have unmet dependencies: -sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable - E: Unable to correct problems, you have held broken packages. - apt-get failed. - E: Package installation failed + The following packages have unmet dependencies: + sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable + E: Unable to correct problems, you have held broken packages. + apt-get failed. + E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: - gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium + gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium - * do not build this package on 32bit architectures anymore - Closes: #1064088 - Closes: #1064089 - There was no patch attached to #1064089, so I can not reproduce the - problems mentioned in #1064088. I am fed up with this poorly done - transition, so I won't spend more time with this. Sorry 32bit people. + * do not build this package on 32bit architectures anymore + Closes: #1064088 + Closes: #1064089 + There was no patch attached to #1064089, so I can not reproduce the + problems mentioned in #1064088. I am fed up with this poorly done + transition, so I won't spend more time with this. Sorry 32bit people. --- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 + -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in - Ubuntu would merely exchange this FTBFS for a different one. + Ubuntu would merely exchange this FTBFS for a different one. (Perhaps + one avenue of solution would be to create the requested time_t patch for + #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? - 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081090] [NEW] gutenprint FTBFS due to 64-bit restriction
Public bug reported: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 ** Affects: gutenprint (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592660] Re: python-tooz fails to build in xenial
This particular build failure seems to have long since been resolved, as newer packages are built and shipping: ### Ubuntu ### python-tooz | 2.0.0-0ubuntu1 | focal python-tooz | 2.10.0-0ubuntu1 | jammy python-tooz | 6.0.1-0ubuntu1 | noble python-tooz | 6.0.1-0ubuntu1 | oracular There is currently a b-d issue with python-tooz 6.0.1 but that's unrelated to this report. ** Changed in: python-tooz (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592660 Title: python-tooz fails to build in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tooz/+bug/1592660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080494] Re: Hang in Unbound 1.13.1
Firxiao, we've discussed this issue in our team call. Unfortunately, while unbound's library binaries (libunbound8 and libunbound-dev) are in main, the rest of its binaries (including the unbound binary itself) are in universe. This doesn't appear to be a strong candidate for pursuing MRE, so are going to hold off on that for now. (It's also unclear if 1.13.2 has been confirmed to resolve the issue for you - did you test it (or Ubuntu 24.04) already and verify it does fix the problem?) However, the severity of the issue does suggest this potentially be a suitable candidate for SRU. An SRU would provide the discrete fix and be deployed to all Ubuntu 22.04 users. Before action could be taken towards SRU, however, it'd need either the patch pinpointed or steps to reproduce identified (ideally both). If you want to pursue that, I'd suggest first posting relevant logs and (sanitized) traces/dumps to this bug report, so we can follow your analysis work. Maybe we will have some suggestions. Null pointer bugs can be caused by a variety of code errors, so if your stack trace differs from the one(s) mentioned upstream, it's also possible you've discovered an entirely new bug... Alternatively, as I mentioned in the previous comment, we could prepare a PPA for you with the 1.13.2 build; this would not fix the issue for all users, but would enable you to resolve the problem in your local environment. ** Tags removed: server-triage-discuss ** Also affects: unbound (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080494 Title: Hang in Unbound 1.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2080494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080494] Re: Hang in Unbound 1.13.1
I doubt we would bump to 1.13.2 in 22.04, however we could look into putting it into a PPA, would that work for your needs? Like Mitchell mentioned, for SRUs it's generally required that a single distinct patch is backported, and that there are steps identified to reproduce it. Sounds like that might be tough in this case, though. But a PPA with the full backport should be pretty straightforward to provide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080494 Title: Hang in Unbound 1.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2080494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/debhelper/+git/debhelper/+merge/473311 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077407 Title: /etc/logrotate.d/exim4-paniclog has wrong content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2077407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
The issue was indeed the change to debhelper. In a PPA, I modified it
to allow --name for dh_installlogrotate, and then rebuilt exim4 against
that. Upgrading exim4 to the rebuilt version then correctly installed
the rotate config:
/var/log/exim4/paniclog {
size 10M
missingok
rotate 10
compress
delaycompress
notifempty
nocreate
}
So, for fixing this it looks like the fixed logrotate will need to be
posted to the archive, and then once it's built in -proposed, update
exim4 to require that version as a built depends and upload that as
well.
No SRU will be necessary since the debhelper change was only introduced
to oracular. However, any other packages besides exim4 that also rely
on installing logrotate with --name will also need rebuilt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077407
Title:
/etc/logrotate.d/exim4-paniclog has wrong content
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2077407/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
Other packages that may be affected include (but not limited to): ipmitool nginx syslogng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077407 Title: /etc/logrotate.d/exim4-paniclog has wrong content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2077407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073317] Re: Backport of open-vm-tools 12.4.5 to noble
Thanks Yan Jin. Timing wise I think there's a 7-day delay on verified SRUs before they go out, which if true means this should be released tomorrow or Saturday. If it's not out by Monday I'll follow up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073317 Title: Backport of open-vm-tools 12.4.5 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2073317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720638] Re: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2)
** Also affects: net-snmp (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: net-snmp (Ubuntu Jammy) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) ** Changed in: net-snmp (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: net-snmp (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/720638 Title: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/720638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal
Thanks! ** Changed in: libvirt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058278 Title: [Backport] libvirt-daemon-system won't install on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2058278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
** Also affects: debhelper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077407 Title: /etc/logrotate.d/exim4-paniclog has wrong content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2077407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073317] Re: Backport of open-vm-tools 12.4.5 to noble
** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073317 Title: Backport of open-vm-tools 12.4.5 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2073317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064450] Re: Merge qemu from Debian unstable for oracular
** Changed in: qemu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064450 Title: Merge qemu from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2064450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064396] Re: Merge containerd from Debian unstable for oracular
** Changed in: containerd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064396 Title: Merge containerd from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2064396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073316] Re: Backport of openldap for Jammy
** Changed in: openldap (Ubuntu) Status: New => Invalid ** Changed in: openldap (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073316 Title: Backport of openldap for Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2073316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078860] Re: DEP8 test case 3 fails, preventing migration in oracular
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/resource-agents/+git/resource-agents/+merge/472256 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078860 Title: DEP8 test case 3 fails, preventing migration in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2078860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078860] Re: DEP8 test case 3 fails, preventing migration in oracular
The test code for the hanging case is:
CASE "check base env: set non-existing OCF_RESKEY_statusurl"
Include prepare
Env OCF_RESKEY_statusurl="yoyoyoyo"
AgentRun start OCF_ERR_GENERIC
It looks like the env variable $OCF_RESKEY_statusurl gets used in the script in
the apache_monitor_basic() routine, where it's used as $STATUSURL:
https://github.com/ClusterLabs/resource-
agents/blob/main/heartbeat/apache
I'm not certain how it is causing a hang in this case, but it's used
only by this line:
if ${ourhttpclient}_func "$STATUSURL" | grep -Ei "$TESTREGEX" >
/dev/null # <---
I'm guessing that `ourhttpclient` resolves to wget or curl or something.
Locally, both will error immediately:
stirling: ~/pkg/ResourceAgents/resource-agents-gu$ curl yoyoyoyo
curl: (6) Could not resolve host: yoyoyoyo
stirling: ~/pkg/ResourceAgents/resource-agents-gu$ wget yoyoyoyo
--2024-09-03 13:00:48-- http://yoyoyoyo/
Resolving yoyoyoyo (yoyoyoyo)... failed: Name or service not known.
wget: unable to resolve host address ‘yoyoyoyo’
Is it possible instead of erroring it is hanging, like on a domain
lookup? I could imagine Launchpad's proxy blocking could do that.
It might be informative to do some instrumenting of the routine to see
where exactly it's failing, e.g.:
apache_monitor_basic() {
echo "Attempting to run ${ourhttpclient}_func '$STATUSURL'..."
apache_monitor_basic() {
if ${ourhttpclient}_func "$STATUSURL" | grep -Ei "$TESTREGEX" >
/dev/null # <---
then
echo " ...unexpected success 1 (?!?)"
return $OCF_SUCCESS
fi
attempt_index_monitor_request
if [ $? -eq 0 ]; then
echo " ...unexpected success 2 (?!?)"
return $OCF_SUCCESS
fi
if ! ocf_is_probe; then
echo " ...failed to probe httpd status page"
ocf_exit_reason "Failed to access httpd status page."
fi
echo "...expected error situation"
return $OCF_ERR_GENERIC
}
Honestly, I'm unclear if this test case is not super crucial for us to
run in Ubuntu's Autopkgtest; it is *supposed* to fail, just differently
than how it's failing for us. :-P It might be worth it to simply
disable the test case so the migration can complete, and maybe let
Debian and/or upstream know about the failure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078860
Title:
DEP8 test case 3 fails, preventing migration in oracular
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2078860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078860] Re: DEP8 test case 3 fails, preventing migration in oracular
** Description changed: https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/amd64/r/resource-agents/20240827_123605_85a06@/log.gz summary 1946s IPaddr2 PASS 1946s command1 PASS 1946s command2 PASS 1946s command3 FAIL non-zero exit status 1 1946s command4 PASS 1946s command5 PASS 1946s command6 PASS 1946s command7 PASS 1946s command8 PASS 1946s command9 PASS 1946s command10PASS 1946s command11PASS 1946s command12PASS 1946s command13PASS Command 3 is the apache command subtest, and the failure only happens in one of the 10 use cases being tested: 518s Starting '[33mapache[0m' case 1 '[33mcheck base env: set non-existing OCF_RESKEY_statusurl[0m': 519s Running agent:./apache stop 522s Setting agent environment:export OCF_RESKEY_statusurl="yoyoyoyo" 522s Running agent:./apache start 545s ERROR: The agent was hanging, killed it, maybe you damaged the agent or system's environment, see details below: 545s Aug 27 12:12:04 INFO: apache not running 545s Aug 27 12:12:04 INFO: waiting for apache /etc/apache2/apache2.conf to come up + + The test code is here: + + https://git.launchpad.net/ubuntu/+source/resource- + agents/tree/tools/ocft/apache -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078860 Title: DEP8 test case 3 fails, preventing migration in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2078860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078860] [NEW] DEP8 test case 3 fails, preventing migration in oracular
Public bug reported: https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/amd64/r/resource-agents/20240827_123605_85a06@/log.gz summary 1946s IPaddr2 PASS 1946s command1 PASS 1946s command2 PASS 1946s command3 FAIL non-zero exit status 1 1946s command4 PASS 1946s command5 PASS 1946s command6 PASS 1946s command7 PASS 1946s command8 PASS 1946s command9 PASS 1946s command10PASS 1946s command11PASS 1946s command12PASS 1946s command13PASS Command 3 is the apache command subtest, and the failure only happens in one of the 10 use cases being tested: 518s Starting '[33mapache[0m' case 1 '[33mcheck base env: set non-existing OCF_RESKEY_statusurl[0m': 519s Running agent:./apache stop 522s Setting agent environment:export OCF_RESKEY_statusurl="yoyoyoyo" 522s Running agent:./apache start 545s ERROR: The agent was hanging, killed it, maybe you damaged the agent or system's environment, see details below: 545s Aug 27 12:12:04 INFO: apache not running 545s Aug 27 12:12:04 INFO: waiting for apache /etc/apache2/apache2.conf to come up ** Affects: resource-agents (Ubuntu) Importance: High Assignee: Athos Ribeiro (athos-ribeiro) Status: In Progress ** Tags: server-todo update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078860 Title: DEP8 test case 3 fails, preventing migration in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2078860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078255] Re: autopkgtest error: rm: cannot remove '/tmp/tmp.OoiXjLc9ID/root': Permission denied
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078255 Title: autopkgtest error: rm: cannot remove '/tmp/tmp.OoiXjLc9ID/root': Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2078255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078301] Re: _autotst.c:1:1: error: return type defaults to ‘int’ in main()
** Changed in: procmail (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078301 Title: _autotst.c:1:1: error: return type defaults to ‘int’ in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procmail/+bug/2078301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078301] Re: _autotst.c:1:1: error: return type defaults to ‘int’ in main()
Debdiff between Debian 3.24+really3.22-2 and 3.24+really3.22-3, which carries 33.patch that has the code fixes for this issue. ** Patch added: "fix-gcc-14-build.debdiff" https://bugs.launchpad.net/debian/+source/procmail/+bug/2078301/+attachment/5811213/+files/fix-gcc-14-build.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078301 Title: _autotst.c:1:1: error: return type defaults to ‘int’ in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procmail/+bug/2078301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078478] Re: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0"
These seem to be matches to this issue: https://github.com/Cisco-Talos/clamav/issues/1300 https://github.com/NixOS/nixpkgs/issues/334852 https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1984784.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078274 This is pointed to as the fix: https://github.com/Cisco-Talos/clamav/commit/d11590f7a443b19da04211c13a57395f33ed7b11 This fix is included in Debian's clamav 1.3.1+dfsg-5 release, which landed a couple days ago. This bugfix was the only change included in that release. ** Bug watch added: github.com/Cisco-Talos/clamav/issues #1300 https://github.com/Cisco-Talos/clamav/issues/1300 ** Bug watch added: github.com/NixOS/nixpkgs/issues #334852 https://github.com/NixOS/nixpkgs/issues/334852 ** Bug watch added: Debian Bug tracker #1078274 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078274 ** Tags added: needs-merge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078478 Title: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2078478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078478] Re: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0"
** Description changed:
* amd64:
https://launchpadlibrarian.net/745207258/buildlog_ubuntu-oracular-amd64.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
* ppc64el:
https://launchpadlibrarian.net/745207148/buildlog_ubuntu-oracular-ppc64el.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
* s390x:
https://launchpadlibrarian.net/745217520/buildlog_ubuntu-oracular-s390x.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
"FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust
assert output.ec == 0"
"Exit code trying to run valgrind
'Test that clam can trust an EXE based on an authenticode certificate check.'"
+
+
+ 3: self =
+ 3:
+ 3: def test_pe_cert_trust(self):
+ 3: self.step_name('Test that clam can trust an EXE based on an
authenticode certificate check.')
+ 3:
+ 3: test_path = TC.path_source / 'unit_tests' / 'input' / 'pe_allmatch'
+ 3: test_exe = test_path / 'test.exe'
+ 3:
+ 3: command = '{valgrind} {valgrind_args} {clamscan} \
+ 3: -d {alerting_dbs} \
+ 3: -d {weak_dbs} \
+ 3: -d {broken_dbs} \
+ 3: -d {trust_dbs} \
+ 3: --allmatch --bytecode-unsigned {testfiles}'.format(
+ 3: valgrind=TC.valgrind, valgrind_args=TC.valgrind_args,
clamscan=TC.clamscan,
+ 3: alerting_dbs=test_path / 'alert-sigs',
+ 3: weak_dbs=test_path / 'weak-sigs',
+ 3: broken_dbs=test_path / 'broken-sigs',
+ 3: trust_dbs=test_path / 'trust-sigs',
+ 3: testfiles=test_exe,
+ 3: )
+ 3: output = self.execute_command(command)
+
+ 3: > assert output.ec == 0
+ 3: E AssertionError: assert 1 == 0
+ 3: E+ where 1 = CmdResult(ec=1,
out='/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_13of22_PE_S1_EXACT_testexe_0.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_11of22_PE_EP_testexe_0.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_14of22_PE_S1_BROAD_testexe_0.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_12of22_PE_EP_testexe_0.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_10of22_PE_testexe_0.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_17of22_PE_testexe_1.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_18of22_PE_EP_testexe_1.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.NDB_20of22_PE_S1_EXACT_testexe_1.UNOFFICIAL
FOUND\n/<>/unit_tests/input/pe_allmatch/test.exe:
Test.Ge...v-bRzyrL/clamav-1.3.1+dfsg/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.IMP_2of6_MD5_STAR.UNOFFICIAL FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.IMP_3of6_SHA1_FIXED.UNOFFICIAL FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.IMP_4of6_SHA1_STAR.UNOFFICIAL FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.IMP_5of6_SHA256_FIXED.UNOFFICIAL FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.IMP_6of6_SHA256_STAR.UNOFFICIAL FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.BC_6of6_PE_UNPCKR_testexe_1.matched FOUND
+ /<>/unit_tests/input/pe_allmatch/test.exe:
Test.GenSig.BC_5of6_PE_UNPCKR_testexe_0.matched FOUND
+
+ --- SCAN SUMMARY ---
+ Known viruses: 90
+ Engine version: 1.3.1
+ Scanned directories: 0
+ Scanned files: 1
+ Infected files: 1
+ Data scanned: 10.85 MB
+ Data read: 1.38 MB (ratio 7.87:1)\nTime: 0.278 sec (0 m 0 s)
+ Start Date: 2024:08:20 22:32:34
+ End Date: 2024:08:20 22:32:35\n', err='').ec
** Description changed:
* amd64:
https://launchpadlibrarian.net/745207258/buildlog_ubuntu-oracular-amd64.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
* ppc64el:
https://launchpadlibrarian.net/745207148/buildlog_ubuntu-oracular-ppc64el.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
* s390x:
https://launchpadlibrarian.net/745217520/buildlog_ubuntu-oracular-s390x.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz
"FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust
assert output.ec == 0"
"Exit code trying to run valgrind
'Test that clam can trust an EXE based on an authenticode certificate check.'"
-
3: self =
- 3:
+ 3:
3: def test_pe_cert_trust(self):
3: self.step_name('Test that clam can trust an EXE based on an
authenticode certificate check.')
- 3:
+ 3:
3: test_path = TC.path_source / 'unit_tests' / 'input' / 'pe_allmatch'
3: test_exe = test_path / 'test.exe'
- 3:
+ 3:
3: command = '{valgrind} {valgrind_args} {clamscan} \
3: -d {alerting_dbs} \
3: -d {weak_dbs} \
3: -d {broken_dbs} \
3: -d {trust_dbs} \
3: --allmatch --bytecode-unsigned {testfiles}'.format(
3: valgrind=TC.valgrind, valgrind_args=TC.valgrind_args,
clamscan=TC.clamscan,
3:
[Bug 2078301] Re: _autotst.c:1:1: error: return type defaults to ‘int’ in main()
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078301 Title: _autotst.c:1:1: error: return type defaults to ‘int’ in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procmail/+bug/2078301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078301] Re: _autotst.c:1:1: error: return type defaults to ‘int’ in main()
** Description changed: * amd64: https://launchpadlibrarian.net/745205379/buildlog_ubuntu-oracular-amd64.procmail_3.24-1ubuntu2_BUILDING.txt.gz * ppc64el: https://launchpadlibrarian.net/745205388/buildlog_ubuntu-oracular-ppc64el.procmail_3.24-1ubuntu2_BUILDING.txt.gz * s390x: https://launchpadlibrarian.net/745205943/buildlog_ubuntu-oracular-s390x.procmail_3.24-1ubuntu2_BUILDING.txt.gz * riscv64: https://launchpadlibrarian.net/743677026/buildlog_ubuntu-oracular-riscv64.procmail_3.24-1ubuntu2_BUILDING.txt.gz cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ gcc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ + + Probably needs fix from 3.24+really3.22-3 (Debb #1075398) ** Bug watch added: Debian Bug tracker #1075398 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075398 ** Also affects: procmail (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078301 Title: _autotst.c:1:1: error: return type defaults to ‘int’ in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procmail/+bug/2078301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078478] Re: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0"
** Description changed: * amd64: https://launchpadlibrarian.net/745207258/buildlog_ubuntu-oracular-amd64.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz * ppc64el: https://launchpadlibrarian.net/745207148/buildlog_ubuntu-oracular-ppc64el.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz * s390x: https://launchpadlibrarian.net/745217520/buildlog_ubuntu-oracular-s390x.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0" + + "Exit code trying to run valgrind + 'Test that clam can trust an EXE based on an authenticode certificate check.'" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078478 Title: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2078478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078478] [NEW] "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0"
Public bug reported: * amd64: https://launchpadlibrarian.net/745207258/buildlog_ubuntu-oracular-amd64.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz * ppc64el: https://launchpadlibrarian.net/745207148/buildlog_ubuntu-oracular-ppc64el.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz * s390x: https://launchpadlibrarian.net/745217520/buildlog_ubuntu-oracular-s390x.clamav_1.3.1+dfsg-4ubuntu1_BUILDING.txt.gz "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0" ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078478 Title: "FAILED clamscan/assorted_test.py::TC::test_pe_cert_trust assert output.ec == 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2078478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078301] [NEW] _autotst.c:1:1: error: return type defaults to ‘int’ in main()
Public bug reported: * amd64: https://launchpadlibrarian.net/745205379/buildlog_ubuntu-oracular-amd64.procmail_3.24-1ubuntu2_BUILDING.txt.gz * ppc64el: https://launchpadlibrarian.net/745205388/buildlog_ubuntu-oracular-ppc64el.procmail_3.24-1ubuntu2_BUILDING.txt.gz * s390x: https://launchpadlibrarian.net/745205943/buildlog_ubuntu-oracular-s390x.procmail_3.24-1ubuntu2_BUILDING.txt.gz * riscv64: https://launchpadlibrarian.net/743677026/buildlog_ubuntu-oracular-riscv64.procmail_3.24-1ubuntu2_BUILDING.txt.gz cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ gcc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] 1 | main() | ^~~~ ** Affects: procmail (Ubuntu) Importance: Undecided Status: New ** Description changed: * amd64: https://launchpadlibrarian.net/745205379/buildlog_ubuntu-oracular-amd64.procmail_3.24-1ubuntu2_BUILDING.txt.gz * ppc64el: https://launchpadlibrarian.net/745205388/buildlog_ubuntu-oracular-ppc64el.procmail_3.24-1ubuntu2_BUILDING.txt.gz - s390x: https://launchpadlibrarian.net/745205943/buildlog_ubuntu-oracular-s390x.procmail_3.24-1ubuntu2_BUILDING.txt.gz + * s390x: https://launchpadlibrarian.net/745205943/buildlog_ubuntu-oracular-s390x.procmail_3.24-1ubuntu2_BUILDING.txt.gz * riscv64: https://launchpadlibrarian.net/743677026/buildlog_ubuntu-oracular-riscv64.procmail_3.24-1ubuntu2_BUILDING.txt.gz - cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] - 1 | main() - | ^~~~ + 1 | main() + | ^~~~ cc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] - 1 | main() - | ^~~~ + 1 | main() + | ^~~~ gcc -O _autotst.c -o _autotst _autotst.c:1:1: error: return type defaults to ‘int’ [-Wimplicit-int] - 1 | main() - | ^~~~ + 1 | main() + | ^~~~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078301 Title: _autotst.c:1:1: error: return type defaults to ‘int’ in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procmail/+bug/2078301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073317] Re: Backport of open-vm-tools 12.4.5 to noble
Hi John, Yan Jin, and Haiying Ding, open-vm-tools version 12.4.5 has been uploaded to -proposed for noble, for your QA team to validate when you're ready. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073317 Title: Backport of open-vm-tools 12.4.5 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2073317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067501] Re: Ubuntu noble is missing libaio.so.1 compat symlink
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067501 Title: Ubuntu noble is missing libaio.so.1 compat symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/2067501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067480] Re: MRE updates of dpdk 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)
** Changed in: dpdk (Ubuntu Jammy) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Mantic) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Noble) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067480 Title: MRE updates of dpdk 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073313] Re: Backport of dpdk for focal, jammy and noble
** Changed in: dpdk (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Focal) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Jammy) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Noble) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073313 Title: Backport of dpdk for focal, jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2073313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073314] Re: Backport of dpdk for focal, jammy and noble
** Changed in: dpdk (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Focal) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Jammy) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dpdk (Ubuntu Noble) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073314 Title: Backport of dpdk for focal, jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2073314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073316] Re: Backport of openldap for Jammy
** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073316 Title: Backport of openldap for Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2073316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073311] Re: Backport of container-stack for focal, jammy and noble
** No longer affects: containerd-app (Ubuntu) ** No longer affects: containerd-app (Ubuntu Focal) ** No longer affects: containerd-app (Ubuntu Jammy) ** No longer affects: containerd-app (Ubuntu Noble) ** No longer affects: docker.io-app (Ubuntu Focal) ** No longer affects: docker.io-app (Ubuntu) ** No longer affects: docker.io-app (Ubuntu Jammy) ** No longer affects: docker.io-app (Ubuntu Noble) ** No longer affects: runc (Ubuntu) ** No longer affects: runc (Ubuntu Focal) ** No longer affects: runc (Ubuntu Jammy) ** Changed in: runc (Ubuntu Noble) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073311 Title: Backport of container-stack for focal, jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/noble/+source/runc/+bug/2073311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077327] Re: dig 9.20.0 from oracular-proposed is segfaulting
Confirm with the PPA package there is no crash. There are a couple migration issues: bind9 (1:9.18.28-0ubuntu1 to 1:9.20.0-2ubuntu2) Migration status for bind9 (1:9.18.28-0ubuntu1 to 1:9.20.0-2ubuntu2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: autopkgtest for bind-dyndb-ldap/11.10-6ubuntu12: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻ autopkgtest for bind9/1:9.20.0-2ubuntu2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻ autopkgtest for freedombox/24.17: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass However it looks like maybe there was a bit of a race condition with the package publication. I've retriggered all these tests in case that's all it was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077327 Title: dig 9.20.0 from oracular-proposed is segfaulting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2077327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
** Changed in: exim4 (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077407 Title: /etc/logrotate.d/exim4-paniclog has wrong content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2077407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064452] Re: Sync radvd from Debian unstable for oracular
This bug was fixed in the package radvd - 1:2.19-2.1 --- radvd (1:2.19-2.1) unstable; urgency=medium * Non-maintainer upload. * Install systemd units into /usr. (Closes: #1073691) -- Chris Hofstaedtler Mon, 05 Aug 2024 00:22:24 +0200 radvd (1:2.19-2) unstable; urgency=medium [Miriam España Acebal] * Fix a FTBFS at Trixie Closes: #1066224 -- Geert Stappers Sun, 21 Apr 2024 11:16:14 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064452 Title: Sync radvd from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/2064452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064452] Re: Merge radvd from Debian unstable for oracular
The Ubuntu delta was taken by Debian. The only other change is a /usr shift, which should land in -devel and can be sync'd in. radvd (1:2.19-2.1) unstable; urgency=medium * Non-maintainer upload. * Install systemd units into /usr. (Closes: #1073691) -- Chris Hofstaedtler Mon, 05 Aug 2024 00:22:24 +0200 radvd (1:2.19-2) unstable; urgency=medium [Miriam España Acebal] * Fix a FTBFS at Trixie Closes: #1066224 -- Geert Stappers Sun, 21 Apr 2024 11:16:14 +0200 ** Tags removed: needs-merge ** Tags added: needs-sync ** Summary changed: - Merge radvd from Debian unstable for oracular + Sync radvd from Debian unstable for oracular ** Changed in: radvd (Ubuntu) Status: New => Fix Released ** Changed in: radvd (Ubuntu) Status: Fix Released => In Progress ** Changed in: radvd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064452 Title: Sync radvd from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/2064452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064418] Re: Merge libpcap from Debian unstable for oracular
Merge was done by Gianfranco ### Debian ### libpcap | 1.10.3-1 | bookworm libpcap | 1.10.4-5 | trixie libpcap | 1.10.4-5 | sid ### Ubuntu ### libpcap | 1.9.1-3 | focal libpcap | 1.10.1-4build1| jammy libpcap | 1.10.4-4.1ubuntu3 | noble libpcap | 1.10.4-5ubuntu1 | oracular libpcap (1.10.4-5ubuntu1) oracular; urgency=low * Merge from Debian unstable. Remaining changes: - Add Build-Depends on libibverbs-dev to enable RDMA support. LP #2006557. - Have -dev package depend on libibverbs-dev per pkgconfig - Don't require ibverbs on i386 -- Gianfranco Costamagna Tue, 09 Jul 2024 09:45:02 +0200 ** Changed in: libpcap (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064418 Title: Merge libpcap from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2064418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064416] Re: Merge libesmtp from Debian unstable for oracular
No merge was available this cycle: ### Debian ### libesmtp | 1.1.0-3.1~deb12u1 | bookworm libesmtp | 1.1.0-3.1 | sid ### Ubuntu ### libesmtp | 1.0.6-4.3build1 | focal/universe libesmtp | 1.1.0-3build1 | jammy/universe libesmtp | 1.1.0-3.1ubuntu1 | noble/universe libesmtp | 1.1.0-3.1ubuntu1 | oracular/universe ** Changed in: libesmtp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064416 Title: Merge libesmtp from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libesmtp/+bug/2064416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064414] Re: Merge libdumbnet from Debian unstable for oracular
This was sync'd: ### Debian ### libdumbnet | 1.16.3-1| bookworm libdumbnet | 1.18.0-1.1 | trixie libdumbnet | 1.18.0-1.1 | sid ### Ubuntu ### libdumbnet | 1.12-9build1| focal/universe libdumbnet | 1.12-10 | jammy/universe libdumbnet | 1.17.0-1ubuntu2 | noble/universe libdumbnet | 1.18.0-1.1 | oracular/universe ** Changed in: libdumbnet (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064414 Title: Merge libdumbnet from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/2064414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
I'm not spotting anything in the Ubuntu delta that could cause this
behavior change. I do confirm it, though:
noble: (Installed: 4.97-4ubuntu4.1)
triage-noble+24.04: /etc/logrotate.d$ grep log exim4-*
exim4-base:/var/log/exim4/mainlog /var/log/exim4/rejectlog {
exim4-paniclog:/var/log/exim4/paniclog {
oracular: (Installed: 4.98-1ubuntu1)
triage-oracular+24.10: /etc/logrotate.d$ grep log exim4-*
exim4-base:/var/log/exim4/mainlog /var/log/exim4/rejectlog {
exim4-paniclog:/var/log/exim4/mainlog /var/log/exim4/rejectlog {
However, looking through the Debian exim4 delta from 4.97-5 to 4.98-1,
nothing obvious is popping out. Indeed, the same dh_installlogrotate
overrides are being done, and the /usr/bin/dh_installlogrotate script
has not changed. However it looks pretty evident that it is copying the
exim4-base's logrotate config instead of the one for exim4-paniclog. It
really looks like perhaps debhelper has changed behavior for the way
the --name option is handled by dh_installlogrotate.
Digging through debhelper's changelog, I spotted this change:
https://salsa.debian.org/debian/debhelper/-/commit/a16a181f2f141c8ae6b8101ee530fff7a67cfc78
It sounds like that is disabling some behavior for the --name option for
tools generally, and added overrides for specific tools that need it.
However, dh_installlogrotate is not one of the updated tools in that
changeset. Perhaps it should be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077407
Title:
/etc/logrotate.d/exim4-paniclog has wrong content
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2077407/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077407] Re: /etc/logrotate.d/exim4-paniclog has wrong content
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077407 Title: /etc/logrotate.d/exim4-paniclog has wrong content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2077407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal
Hi Guilherme, thanks for flagging this. I've corrected the regression and triggered a successful rebuild for the backports PPA; the build is currently being published to mirrors. Once it's available, please re- test and verify that it's working properly once again. ** Changed in: libvirt (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058278 Title: [Backport] libvirt-daemon-system won't install on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2058278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
