Bug#1035841: fixed in amavisd-new 1:2.13.0-3
Hi, On Thu, 11 May 2023 23:52:00 + Debian FTP Masters wrote: > Changes: > amavisd-new (1:2.13.0-3) unstable; urgency=medium > . >* Fix failure to purge without adduser. Closes: #1035841. thank you! Would you like me to take care of filing the unblock request with release.debian.org or would you like to take care of that yourself? Thanks! cheers, josch signature.asc Description: signature
Bug#1035841: marked as done (amavisd-new fails to purge without adduser - userdel: not found)
Your message dated Thu, 11 May 2023 23:52:00 + with message-id and subject line Bug#1035841: fixed in amavisd-new 1:2.13.0-3 has caused the Debian Bug report #1035841, regarding amavisd-new fails to purge without adduser - userdel: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: amavisd-new Version: 1:2.13.0-2 Severity: serious User: jo...@debian.org Usertags: adduserpurge Hi, the packages passwd and adduser are not part of the Essential:yes set. According to policy §7.2 maintainer scripts cannot assume them being installed when purging a package. If one tries to remove this package without adduser (which depends on passwd) installed, one gets: --%<- Purging configuration files for amavisd-new (1:2.13.0-2) ... /var/lib/dpkg/info/amavisd-new.postrm: 36: userdel: not found dpkg: error processing package amavisd-new (--purge): installed amavisd-new package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: amavisd-new -->%- There is ongoing discussion how to handle system users on package removal, see https://bugs.debian.org/621833 For a discussion about use of adduser during purge, see #1035654. To work around this problem, at least 125 source packages [codesearch] simply ignore failures of calling the passwd or adduser tools during purge. The following patch should fix this package by doing the same: --%<- diff -Nru amavisd-new-2.13.0/debian/amavisd-new.postrm amavisd-new-2.13.0/debian/amavisd-new.postrm --- amavisd-new-2.13.0/debian/amavisd-new.postrm2023-02-23 05:59:36.0 +0100 +++ amavisd-new-2.13.0/debian/amavisd-new.postrm2023-05-10 06:33:15.0 +0200 @@ -33,7 +33,7 @@ dpkg-statoverride --remove $i || true done -userdel amavis +userdel amavis || true echo "Removing amavis files and directories..." [ -d /var/lib/amavis ] && rm -fr /var/lib/amavis -->%- If you prefer I can fix this via an NMU. Thanks! cheers, josch [codesearch] https://codesearch.debian.net/search?q=del%28user%7Cgroup%29.*%5C%7C%5C%7C+true+path%3Adebian%2F.*%5C.%28pre%7Cpost%29rm%24=0 --- End Message --- --- Begin Message --- Source: amavisd-new Source-Version: 1:2.13.0-3 Done: Brian May We believe that the bug you reported is fixed in the latest version of amavisd-new, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated amavisd-new package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 May 2023 08:52:23 +1000 Source: amavisd-new Architecture: source Version: 1:2.13.0-3 Distribution: unstable Urgency: medium Maintainer: Brian May Changed-By: Brian May Closes: 1035841 Changes: amavisd-new (1:2.13.0-3) unstable; urgency=medium . * Fix failure to purge without adduser. Closes: #1035841. Checksums-Sha1: dd5c9bf77b25b896076011ac344adb367dd01085 2282 amavisd-new_2.13.0-3.dsc 158b72a0328b5654a2a50a7d036e8ce99fc3a473 890624 amavisd-new_2.13.0.orig.tar.bz2 6d9df44f4deff3cb2267ec4f2f51075f01440ecd 71952 amavisd-new_2.13.0-3.debian.tar.xz 686d01024b4d0dea40217e22b733fcf8a249ef48 12341 amavisd-new_2.13.0-3_source.buildinfo Checksums-Sha256: 966734b2ab6aad92e585160c039a01448f03d27fbad82a5752a510b950706173 2282 amavisd-new_2.13.0-3.dsc deb6e99182f0ee67c382eab454220106aa5d0fd18a564236710f59f07600069b 890624 amavisd-new_2.13.0.orig.tar.bz2 7ccbb226cf6e383a74a39cb93105dc18ad815f88279678c054ccca0764db88b4 71952 amavisd-new_2.13.0-3.debian.tar.xz c655a1809507653e7728b6a8523fbae648b77ffeabb0ff6879b59ac650035907 12341 amavisd-new_2.13.0-3_source.buildinfo Files:
Bug#1035289: marked as done (merecat: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf)
Your message dated Thu, 11 May 2023 23:25:40 + with message-id and subject line Bug#1035289: fixed in merecat 2.31+git20220513+ds-4.1 has caused the Debian Bug report #1035289, regarding merecat: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: merecat Version: 2.31+git20220513+ds-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: "Packages must not require the existence of any files in /usr/share/doc/ in order to function." https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. >From the attached log (scroll to the bottom...): Setting up merecat (2.31+git20220513+ds-4) ... Error: The new file usr/share/doc/merecat/examples/merecat.conf does not exist! dpkg: error processing package merecat (--configure): installed merecat package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: merecat Cheers, Andreas merecat_2.31+git20220513+ds-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: merecat Source-Version: 2.31+git20220513+ds-4.1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of merecat, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated merecat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 21:17:13 CEST Source: merecat Binary: Architecture: source Version: 2.31+git20220513+ds-4.1 Distribution: unstable Urgency: medium Maintainer: Joost van Baal-Ilić Changed-By: gregor herrmann Description: Closes: 1035289 Changes: merecat (2.31+git20220513+ds-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix "postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf": Install example config files to /usr/share/merecat, symlink them from /usr/share/doc/merecat/examples, and use the ones from /usr/share/merecat in the postinst. (Closes: #1035289) Checksums-Sha256: 818d32873c3b108ff5f5fc778001488391c9daa5120890d457205202ef64a4f7 2152 merecat_2.31+git20220513+ds-4.1.dsc 1a334599eb3a312c3667b046534f6e594d1cacf60ed4ae5454020de2be4f817c 3668 merecat_2.31+git20220513+ds-4.1.debian.tar.xz 65937544f028385d415470de6f2a4c24a6a2340a7ff63104ea887d021e1f40a3 6732 merecat_2.31+git20220513+ds-4.1_sourceonly.buildinfo Checksums-Sha1: 88711586bce674e8c70d0d31ff6770354fee85c1 2152 merecat_2.31+git20220513+ds-4.1.dsc 615acf59ab179a6466761a8e2c26d2af5492f5ad 3668 merecat_2.31+git20220513+ds-4.1.debian.tar.xz 7b7aee5aeff3a111bed3b8b5bbd2299a347edea4 6732 merecat_2.31+git20220513+ds-4.1_sourceonly.buildinfo Files: 4b5d1116e40db801c182a219d2765e65 2152 web optional merecat_2.31+git20220513+ds-4.1.dsc f044b571e92073b822d180120bd62ecd 3668 web optional merecat_2.31+git20220513+ds-4.1.debian.tar.xz d3620c7b0437c1bbe6ae03277f48 6732 - - merecat_2.31+git20220513+ds-4.1_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmRdPzpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbkexAAr8qLQtzac7KLV77/xA/hgYTRX9+h6U68mB6qJ9yE+BuxLfmm+ohwRtpW uKY+yo86k3Px+5KCjtBc8T20DcZ6Qn8awfdXln+c1fZNuJFGVWvDLIzDvEXTK4A2
Bug#1018730: More info
To add to the previous briefly, as I didn't explicitly mention this. Early initramfs should: * Activate the resume device (one of the swap) for resume handling. * Activate the rootfs. Once rootfs is there, remaining PVs etc will cascade activate through the setup from late-stage boot process onwards. Early initramfs should NOT call vgchange and activate things it doesn't need to activate, specific lvchange is better in my opinion. Thanks, -- Melvin Vermeeren Systems engineer signature.asc Description: This is a digitally signed message part.
Bug#1034824: tomcat9 should not be released with Bookworm
Hi Paul, Le 2023-05-11 21:44, Paul Gevers a écrit : From a quick look at the key packages: It seems you didn't follow up (86 days) on libcommons-dbcp-java which can't migrate to bookworm because it would make libbiojava-java-doc uninstallable (no fix there, no bug report filed). I have to apology for this one, I forgot to check the transition of libcommons-dbcp-java. Is it still possible to remove libbiojava-java-doc to fix this (very low popcon and unused like the other -java-doc package)? src:tiles also build-depends on libtomcat9-java, with no bug filed for the migration to tomcat10 *and* it having it's own FTBFS bug. (It's key because of src:libspring-java) I remember pulling my hair on src:tiles to make it build with OpenJDK 17, without success unfortunately (#1011597). The project is dead upstream, that doesn't help. Patching src:libspring-java and removing src:tiles is likely the next step. On IRC carnil and jmm_ suggested that src:tomcat9 could be left in bookworm but have it's server component stripped. Would that help the situation? I agree, this is a good compromise. Emmanuel Bourg
Bug#1018730: closed by Bastian Blank (Re: Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure)
Hi, My wording might be a bit over the top, apologies in advance. I do really mean the best, just a bit baffled at the wontfix reply and lack of acknowledgement of the problem. I'm not really understanding the "Half VG was never a real thing" approach and general dismissal of this bug, I think it should be reopened still and this use case handled properly or at least further discussion. I consider it to be a regression and quite a nasty one at that especially for servers without BMC. LVM officially support activation of any LV in a VG as long as specific PVs needed for this LV are present. Specifying --activationmode is something else entirely and should never be done (unless disaster recovery). >From lvchange(8) man page about this option: > Determines if LV activation is allowed when PVs are missing, e.g. because of > a device failure. ... Meaning that --activationmode decides whether LV with missing PVs may be activated or not. This is not the case in my setup and in many other server setups. To make sure: *only* the PVs for the *exact* LV in question need to be present, PVs for *other* LVs in the same VG may be missing. What LVM does not support, unless you force it, is actually changing a VG when PVs of this VG are missing, as to my knowledge VG metadata is stored on each and every PV independently. LV activation does not count as VG modification. The entire reason to have a single VG for many things is because of flexibility LVM provides within a VG. Almost all of the features *require* PVs within the same VG. Snapshots, thin LVM, cache, etc. Even basic feature like resizing require a nice PV - VG - LV structure. As a PV can only be in one VG, what refusal of this bug is suggesting is that one has to manually partition (GPT) drives for root-related stuff, with their own PVs and VGs and LVs, so it can boot. And then create other partitions with PVs on the same disk for the additional stuff. This literally defeats the entire purpose of LVM, easy volume management, and means you have to resize the physical disk partitions to extend things. Good luck with that! A few examples: root filesystem on some NVMe SSD and a bunch of HDDs connected for persistent storage. Now let's say I want to: * When running backups, copy-on-write snapshot on the SSD PV so the HDD array PVs performance remains in good condition instead of COW on the HDDs. * Implement LVM caching for this HDD array PVs on fast SSD PV. * Thin pool on HDDs and store the metadata on the SSD PV for performance. * Reminder: simply having a /etc/luks.key on rootfs used to open other PVs (HDD array) will result in boot failure if they're in the same VG! All totally reasonable use cases. But if you are requiring split VG for "root stuff needed during booting" this is all not supported, because HDDs are only activated later. Maybe these HDD PVs are actually on a networked file system (NBD, NFS) are only available later. LVM can do all of this safely no problem. (I have used many of the above in production environments with great results.) Anyway, the main problem is that the udev rules are currently coded to only do activation when LVM_VG_NAME_COMPLETE aka a VG has all the PVs used for all the LVs within the VG. This is not suitable for early stage boot processes and activation of LV for root, swap and other early required fs. It *is* suitable for auto-activation of LVs during late stage boot process or during runtime. On my workstation, opening mail of this issue, a typical boot is as follows: # The PV (SSD) containing root and swap is unlocked (LUKS, manual input pw). # Manual initramfs hack that "lvchange -aay -y root swap". lvm: WARNING: VG verm-r4e is missing PV HDD_ARRAY_1... lvm: WARNING: VG verm-r4e is missing PV HDD_ARRAY_2... # Rootfs get mounted, late-stage boot lvm cryptsetup etc run. # It notices verm-r4e VG is incomplete. lvm[1535]: PV /dev/dm-2 online, VG verm-r4e incomplete (need 2). # The /etc/luks.key is used to open HDD array PVs. lvm[2387]: PV /dev/dm-17 online, VG verm-r4e incomplete (need 1). lvm[2534]: PV /dev/dm-19 online, VG verm-r4e is complete. # Now the all PVs are there, the remainder LVs get auto-activated. lvm[2540]: 9 logical volume(s) in volume group "verm-r4e" now active # As a result, my HDD pool LV is on and gets fsck + mounted cleanly. This is working very well and is by design and very normal way of using LVM. Both startup and shutdown works perfectly with clean mount/unmount etc. Also, if system configuration somehow triggers raid rebuilds every boot then sysadmin will get mail from tooling (if properly configured at least). Pretty sure it also only syncs dirty pages in such a case anyway, which is very quick. In any case I'd rather have a system mail root with some issue than hard fail in initramfs for no good reason. This strongly feels like removing upstream supported use cases to "protect" sysadmin from wrongly configuring their system, at the
Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded
James Addison dixit: >On Thu, 11 May 2023 at 02:43, Andres Salomon wrote: >> For ARM64, he says that raising the stack limit is not safe for v8 >> *embedded inside WebView*, and therefore not appropriate for upstream >> v8. But then he says it could/should be safe for v8 *embedded inside >> NodeJS*. >> >> Based on that, I suggest patching Debian's NodeJS with the patch to >> adjust armhf/arm64 stack limit size That would be a good thing (huh, wasn’t armhf good?), but… >I have a question: if we apply the patch and begin using the same >constant stack size of 984kb on 32-bit ARM and 64-bit ARM as is >defined for other architectures, then does NodeJS on those platforms >begin supporting exactly the same stack frame capacity (maximum call >depth for any given recursive function, for example) as a build of the >same NodeJS source on x86 and amd64 respectively? … no, because both stack usage and other stuff on stack differ. Which is why I’d rather have the getrlimit-based one for nodejs. That would give us twice to four times the limit. >> (As chromium maintainer, which also embeds v8, I haven't heard of any >> issues and hadn't planned on touching stacks limits. It sure would be Yes, yes, definitely don’t change it outside of nodejs. >> javascript code that is triggering this bug should really be fixed to >> not be so stack-intensive, of course. Perhaps this bug cloned at a >> lower severity, filed against those packages that this bug is affecting? That’s got a dependency chain so long that don’t hold your breath for ALL those to be changed is true. Besides, how would the respective maintainers be aware of this in the first place? Short of failing with an arbitrary nesting limit on all arches, in upstream nodejs, I doubt you’d get half of the upstream code maintainers to care… if they even care about their code any more at all. I am not a friend of such limits either, in addition. bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Processed: fixed 1035732 in 5.27.2-1
Processing commands for cont...@bugs.debian.org: > fixed 1035732 5.27.2-1 Bug #1035732 [libkscreenlocker5] libkscreenlocker5: Endless loop when using PAM Marked as fixed in versions kscreenlocker/5.27.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1035732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035862: marked as done (libpopplerkit0: broken symlinks: /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/*.pfb -> ../../../../../fonts/type1/urw-base35/*.pfb)
Your message dated Thu, 11 May 2023 22:42:52 + with message-id and subject line Bug#1035862: fixed in popplerkit.framework 0.0.20051227svn-11 has caused the Debian Bug report #1035862, regarding libpopplerkit0: broken symlinks: /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/*.pfb -> ../../../../../fonts/type1/urw-base35/*.pfb to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpopplerkit0 Version: 0.0.20051227svn-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks. 0m57.5s ERROR: FAIL: Broken symlinks: /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/d05l.pfb -> ../../../../../fonts/type1/urw-base35/d05l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n019003l.pfb -> ../../../../../fonts/type1/urw-base35/n019003l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n019004l.pfb -> ../../../../../fonts/type1/urw-base35/n019004l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n019023l.pfb -> ../../../../../fonts/type1/urw-base35/n019023l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n019024l.pfb -> ../../../../../fonts/type1/urw-base35/n019024l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n021003l.pfb -> ../../../../../fonts/type1/urw-base35/n021003l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n021004l.pfb -> ../../../../../fonts/type1/urw-base35/n021004l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n021023l.pfb -> ../../../../../fonts/type1/urw-base35/n021023l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n021024l.pfb -> ../../../../../fonts/type1/urw-base35/n021024l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n022003l.pfb -> ../../../../../fonts/type1/urw-base35/n022003l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n022004l.pfb -> ../../../../../fonts/type1/urw-base35/n022004l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n022023l.pfb -> ../../../../../fonts/type1/urw-base35/n022023l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/n022024l.pfb -> ../../../../../fonts/type1/urw-base35/n022024l.pfb (libpopplerkit0) /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/s05l.pfb -> ../../../../../fonts/type1/urw-base35/s05l.pfb (libpopplerkit0) fonts-urw-base35 does no longer ship the fonts with the "numbered" names. cheers, Andreas --- End Message --- --- Begin Message --- Source: popplerkit.framework Source-Version: 0.0.20051227svn-11 Done: Yavor Doganov We believe that the bug you reported is fixed in the latest version of popplerkit.framework, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated popplerkit.framework package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 May 2023 19:49:38 +0300 Source: popplerkit.framework Architecture: source Version: 0.0.20051227svn-11 Distribution: unstable Urgency: medium Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Closes: 1035862 Changes: popplerkit.framework (0.0.20051227svn-11) unstable; urgency=medium . * debian/patches/debian-fonts.patch: New; use new font names from the fonts-urw-base35 package. * debian/libpopplerkit0.links: New file; create symlinks for the font files from fonts-urw-base35 (Closes: #1035862). * debian/rules (binary-post-install/libpopplerkit0): Remove; symlinks are now handled via .links.
Bug#1035289: merecat: diff for NMU version 2.31+git20220513+ds-4.1
On Thu, 11 May 2023 21:28:17 +0200, Joost van Baal-Ilić wrote: > Awesome, thanks a lot! (And no need to delay longer.) Thanks, rescheduled to 0-day. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1035857: texlive-fonts-extra: broken font symlinks for junicode
On 10.05.2023 11:18, Andreas Beckmann wrote: Hi again, during a test with piuparts I noticed your package ships (or creates) broken symlinks: OK, had a closer look: the "Debian Fonts Task Force" replaced the "Junicode 1" by "Junicode 2" although they may behave differently "Users of the various versions of Junicode 1 need to be aware that documents originally set in Junicode 1 may reflow when set in Junicode 2. Further, documents that use the OpenType features of Junicode 1 (aside from basics like kerning and standard ligatures) may not be displayed properly when changed over to Junicode 2." I guess it would have been better to create fonts-junicode2 and then slowly phase out fonts-junicode, when v2 left beta stage. I could simply fix the links and point them to the v2 OTF fonts. This could be even done now. This would give Debian users the v2 fonts but I don't know if they are compatible to the Junicode related files in texlive-fonts-extra. Junicode v2 wasn't even uploaded to CTAN yet. I guess it is a better idea to stay with Junicode 1 for now and re-integrate them into tfe after bookworm.. fonts-alegreya-sans will not be in bookworm (and hasn't been in bullseye), thus /usr/share/texlive/texmf-dist/fonts/opentype/huerta/alegreya also contains broken symlinks. Well, I tend to say "this is not my fault". I may revert my decision after bookworm. H. -- sigfault
Bug#1034824: tomcat9 should not be released with Bookworm
Hello Paul, Am Donnerstag, dem 11.05.2023 um 21:44 +0200 schrieb Paul Gevers: > Hi Markus, > > On Tue, 25 Apr 2023 16:04:09 +0200 Markus Koschany wrote: > > We can only support one major Tomcat version per release. Tomcat9 has > > been part of Buster and Bullseye already and is superseded by Tomcat > > 10 in Bookworm. I wanted to wait with the removal request until the > > issues in [resteasy3.0] and [tomcatjss] have been resolved but to make > > it more obvious I am filing this bug report now. > > Release Team member here. I'll note that I'm not impressed by the > communication and timing of this bug. We're in Full Freeze for bookworm. > This is no time for transitions, let alone for *uncoordinated* ones. This bug report was merely intended as a reminder. I assumed that tomcatjss (#1031816) and resteasy3.0 were the only two issues left to resolve. I agree that we should have filed the bug report earlier. I was under the impression that all affected packages are maintained by the Java team. IMHO it doesn't make much sense to maintain a Tomcat plugin outside of it, which is by definition tightly coupled with the web server. Still, there was plenty of time and I have pointed to several possible ways to resolve this problem but there was no response. [1] > > You should have raised the issue earlier and brought it to the release > team. tomcat9 and tomcat10 are both key packages so neither can easily > be removed. > > From a quick look at the key packages: > > It seems you didn't follow up (86 days) on libcommons-dbcp-java which > can't migrate to bookworm because it would make libbiojava-java-doc > uninstallable (no fix there, no bug report filed). I did not upload libcommons-dbcp-java and I was not aware of the problem. I will take care of it. > src:tiles also build-depends on libtomcat9-java, with no bug filed for > the migration to tomcat10 *and* it having it's own FTBFS bug. (It's key > because of src:libspring-java) Again I was not aware of src:tiles, probably because there was an RC bug already. This problem seems solvable too. > On IRC carnil and jmm_ suggested that src:tomcat9 could be left in > bookworm but have it's server component stripped. Would that help the > situation? Yes, that was one of my suggestions. > Everything in this transition would still need an unblock by the release > team, as we're now very close to the hard freeze (24 May) and nearly > ready to release. I suggest we just drop all tomcat9 binary packages except libtomcat9-java and I fix tiles and libcommons-dbcp-java. That seems to be the easiest solution right now. Regards, Markus [1] https://bugs.debian.org/1031816#37 signature.asc Description: This is a digitally signed message part
Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded
On Thu, 11 May 2023 at 02:43, Andres Salomon wrote: > > On Sat, 11 Mar 2023 11:04:15 + James Addison > wrote: > > Package: nodejs > > Followup-For: Bug #1030284 > > X-Debbugs-Cc: t...@debian.org > > > > Guidance received from the V8 project (a vendored dependency in the > upstream > > NodeJS codebase) on the v8-dev mailing list is, in > summary/interpretation: > > > > * It is not yet safe to increase the stack size limit on ARM64 > systems. > [...] > > Sidenotes: > > > > A patch for 32-bit architectures could apparently be acceptable, > although may > > be best offered to NodeJS rather than V8. For what it's worth: > NodeJS seems > > to have a policy of not accepting patches to their vendored > dependencies. > > > > In reading Jakob's response > (https://groups.google.com/g/v8-dev/c/7ZI3vxtabcU/m/c9qvHkOBBAAJ), I'm > interpreting it slightly differently- > > He says that raising the stack limit *is* safe for 32-bit ARM, even > inside of the V8 upstream source tree. > > For ARM64, he says that raising the stack limit is not safe for v8 > *embedded inside WebView*, and therefore not appropriate for upstream > v8. But then he says it could/should be safe for v8 *embedded inside > NodeJS*. > > Based on that, I suggest patching Debian's NodeJS with the patch to > adjust armhf/arm64 stack limit size to 984kb. With the caveat that the > javascript code that is triggering this bug should really be fixed to > not be so stack-intensive, of course. Perhaps this bug cloned at a > lower severity, filed against those packages that this bug is affecting? > > (As chromium maintainer, which also embeds v8, I haven't heard of any > issues and hadn't planned on touching stacks limits. It sure would be > nice to have just one copy of V8 in the archive, though..) I have a question: if we apply the patch and begin using the same constant stack size of 984kb on 32-bit ARM and 64-bit ARM as is defined for other architectures, then does NodeJS on those platforms begin supporting exactly the same stack frame capacity (maximum call depth for any given recursive function, for example) as a build of the same NodeJS source on x86 and amd64 respectively?
Processed: Re: Bug#1035947: fresh build from git fails with cannot access local variable 'new_file'
Processing commands for cont...@bugs.debian.org: > severity 1035947 normal Bug #1035947 [src:firefox] fresh build from git fails with cannot access local variable 'new_file' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1035947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035947: fresh build from git fails with cannot access local variable 'new_file'
severity 1035947 normal thanks This would be serious if it failed to build with the sources in the Debian archive, which is what counts. Note that using uscan doesn't get you all the sources. On Thu, May 11, 2023 at 10:32:40AM -0400, Antoine Beaupre wrote: > Source: firefox > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully in the past) > > I'm trying to build Firefox 113 from the git repository. I have pulled > the package with: > > debcheckout firefox > > Then tried to download the latest tarballs with: > > uscan --download-current > > This crashes with a Python exception: > > anarcat@angela:firefox$ uscan --download-current > Newest version of firefox on remote site is 113.0, specified download version > is 113.0 > uscan warn: Possible OpenPGP signature found at: > > https://archive.mozilla.org/pub/firefox/releases/113.0/source/firefox-113.0.source.tar.xz.asc > * Add opts=pgpsigurlmangle=s/$/.asc/ or opts=pgpmode=auto to debian/watch > * Add debian/upstream/signing-key.asc. > See uscan(1) for more details > Successfully symlinked ../firefox-113.0.source.tar.xz to > ../firefox_113.0.orig.tar.xz. > Traceback (most recent call last): > File "/home/anarcat/dist/firefox/debian/repack.py", line 217, in > main() > File "/home/anarcat/dist/firefox/debian/repack.py", line 205, in main > if not new_file: > > UnboundLocalError: cannot access local variable 'new_file' where it is not > associated with a value > uscan: error: python3 debian/repack.py --upstream-version 113.0 > ../firefox_113.0.orig.tar.xz subprocess returned exit status 1 > anarcat@angela:firefox[1]$ > > I believe the following patch fixes the issue somehow: > > diff --git i/debian/repack.py w/debian/repack.py > index 00d20928f6e..4f04ea200fb 100755 > --- i/debian/repack.py > +++ w/debian/repack.py > @@ -199,6 +199,8 @@ def main(): > > if options.new_file: > new_file = options.new_file > +else: > +new_file = None > > if os.path.islink(args[0]): > orig = os.path.realpath(args[0]) > > a. > > -- Package-specific info: > > > -- Addons package information > > -- System Information: > Debian Release: 12.0 > APT prefers testing-security > APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, > 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental'), > (1, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT) > Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > -- no debconf information >
Bug#1034824: tomcat9 should not be released with Bookworm
Hi Markus, On Tue, 25 Apr 2023 16:04:09 +0200 Markus Koschany wrote: We can only support one major Tomcat version per release. Tomcat9 has been part of Buster and Bullseye already and is superseded by Tomcat 10 in Bookworm. I wanted to wait with the removal request until the issues in [resteasy3.0] and [tomcatjss] have been resolved but to make it more obvious I am filing this bug report now. Release Team member here. I'll note that I'm not impressed by the communication and timing of this bug. We're in Full Freeze for bookworm. This is no time for transitions, let alone for *uncoordinated* ones. You should have raised the issue earlier and brought it to the release team. tomcat9 and tomcat10 are both key packages so neither can easily be removed. From a quick look at the key packages: It seems you didn't follow up (86 days) on libcommons-dbcp-java which can't migrate to bookworm because it would make libbiojava-java-doc uninstallable (no fix there, no bug report filed). src:tiles also build-depends on libtomcat9-java, with no bug filed for the migration to tomcat10 *and* it having it's own FTBFS bug. (It's key because of src:libspring-java) On IRC carnil and jmm_ suggested that src:tomcat9 could be left in bookworm but have it's server component stripped. Would that help the situation? Everything in this transition would still need an unblock by the release team, as we're now very close to the hard freeze (24 May) and nearly ready to release. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1035289: merecat: diff for NMU version 2.31+git20220513+ds-4.1
Hi gregor, Awesome, thanks a lot! (And no need to delay longer.) Bye, Joost On Thu, May 11, 2023 at 08:54:27PM +0200, gregor herrmann wrote: > Control: tags 1035289 + patch > Control: tags 1035289 + pending > > > Dear maintainer, > > I've prepared an NMU for merecat (versioned as 2.31+git20220513+ds-4.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. > > Regards. > > > -- > .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe >`- > diff -Nru merecat-2.31+git20220513+ds/debian/changelog > merecat-2.31+git20220513+ds/debian/changelog > --- merecat-2.31+git20220513+ds/debian/changelog 2023-02-23 > 07:09:58.0 +0100 > +++ merecat-2.31+git20220513+ds/debian/changelog 2023-05-11 > 20:47:24.0 +0200 > @@ -1,3 +1,13 @@ > +merecat (2.31+git20220513+ds-4.1) unstable; urgency=medium > + > + * Non-maintainer upload. > + * Fix "postinst uses /usr/share/doc content (Policy 12.3): > +/usr/share/doc/merecat/examples/merecat.conf": > +Install example config files to /usr/share/merecat and symlink them from > +/usr/share/doc/merecat/examples. (Closes: #1035289) > + > + -- gregor herrmann Thu, 11 May 2023 20:47:24 +0200 > + > merecat (2.31+git20220513+ds-4) unstable; urgency=medium > >* Upload to unstable. > diff -Nru merecat-2.31+git20220513+ds/debian/install > merecat-2.31+git20220513+ds/debian/install > --- merecat-2.31+git20220513+ds/debian/install2023-02-17 > 09:47:41.0 +0100 > +++ merecat-2.31+git20220513+ds/debian/install2023-05-11 > 20:47:24.0 +0200 > @@ -1 +1,3 @@ > merecat.service lib/systemd/system > +throttle.conf usr/share/merecat > +merecat.confusr/share/merecat > diff -Nru merecat-2.31+git20220513+ds/debian/merecat.examples > merecat-2.31+git20220513+ds/debian/merecat.examples > --- merecat-2.31+git20220513+ds/debian/merecat.examples 2022-05-05 > 09:52:36.0 +0200 > +++ merecat-2.31+git20220513+ds/debian/merecat.examples 1970-01-01 > 01:00:00.0 +0100 > @@ -1,2 +0,0 @@ > -throttle.conf > -merecat.conf > diff -Nru merecat-2.31+git20220513+ds/debian/merecat.links > merecat-2.31+git20220513+ds/debian/merecat.links > --- merecat-2.31+git20220513+ds/debian/merecat.links 1970-01-01 > 01:00:00.0 +0100 > +++ merecat-2.31+git20220513+ds/debian/merecat.links 2023-05-11 > 19:58:06.0 +0200 > @@ -0,0 +1,2 @@ > +usr/share/merecat/throttle.conf usr/share/doc/merecat/examples/throttle.conf > +usr/share/merecat/merecat.conf usr/share/doc/merecat/examples/merecat.conf
Bug#1035289: merecat: diff for NMU version 2.31+git20220513+ds-4.1
[2nd try, I forgot to adjust the postinst, sorry for the blunder.] Dear maintainer, I've prepared an NMU for merecat (versioned as 2.31+git20220513+ds-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru merecat-2.31+git20220513+ds/debian/changelog merecat-2.31+git20220513+ds/debian/changelog --- merecat-2.31+git20220513+ds/debian/changelog 2023-02-23 07:09:58.0 +0100 +++ merecat-2.31+git20220513+ds/debian/changelog 2023-05-11 20:47:24.0 +0200 @@ -1,3 +1,15 @@ +merecat (2.31+git20220513+ds-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "postinst uses /usr/share/doc content (Policy 12.3): +/usr/share/doc/merecat/examples/merecat.conf": +Install example config files to /usr/share/merecat, symlink them from +/usr/share/doc/merecat/examples, and use the ones from /usr/share/merecat +in the postinst. +(Closes: #1035289) + + -- gregor herrmann Thu, 11 May 2023 20:47:24 +0200 + merecat (2.31+git20220513+ds-4) unstable; urgency=medium * Upload to unstable. diff -Nru merecat-2.31+git20220513+ds/debian/install merecat-2.31+git20220513+ds/debian/install --- merecat-2.31+git20220513+ds/debian/install 2023-02-17 09:47:41.0 +0100 +++ merecat-2.31+git20220513+ds/debian/install 2023-05-11 20:47:24.0 +0200 @@ -1 +1,3 @@ merecat.service lib/systemd/system +throttle.conf usr/share/merecat +merecat.confusr/share/merecat diff -Nru merecat-2.31+git20220513+ds/debian/merecat.examples merecat-2.31+git20220513+ds/debian/merecat.examples --- merecat-2.31+git20220513+ds/debian/merecat.examples 2022-05-05 09:52:36.0 +0200 +++ merecat-2.31+git20220513+ds/debian/merecat.examples 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -throttle.conf -merecat.conf diff -Nru merecat-2.31+git20220513+ds/debian/merecat.links merecat-2.31+git20220513+ds/debian/merecat.links --- merecat-2.31+git20220513+ds/debian/merecat.links 1970-01-01 01:00:00.0 +0100 +++ merecat-2.31+git20220513+ds/debian/merecat.links 2023-05-11 19:58:06.0 +0200 @@ -0,0 +1,2 @@ +usr/share/merecat/throttle.conf usr/share/doc/merecat/examples/throttle.conf +usr/share/merecat/merecat.conf usr/share/doc/merecat/examples/merecat.conf diff -Nru merecat-2.31+git20220513+ds/debian/merecat.postinst merecat-2.31+git20220513+ds/debian/merecat.postinst --- merecat-2.31+git20220513+ds/debian/merecat.postinst 2023-02-17 09:56:29.0 +0100 +++ merecat-2.31+git20220513+ds/debian/merecat.postinst 2023-05-11 20:47:24.0 +0200 @@ -5,8 +5,8 @@ case "$1" in configure) -ucf usr/share/doc/merecat/examples/merecat.conf /etc/merecat.conf -ucf usr/share/doc/merecat/examples/throttle.conf /etc/throttle.conf +ucf usr/share/merecat/merecat.conf /etc/merecat.conf +ucf usr/share/merecat/throttle.conf /etc/throttle.conf ;; abort-upgrade|abort-remove|abort-deconfigure) ;; signature.asc Description: Digital Signature
Bug#1034914: marked as done (libdbusada8-dev: missing Breaks+Replaces for libdbusada6-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 19:03:50 + with message-id and subject line Bug#1034914: fixed in dbusada 0.6.2-4 has caused the Debian Bug report #1034914, regarding libdbusada8-dev: missing Breaks+Replaces for libdbusada6-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdbusada8-dev Version: 0.6.2-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libdbusada8-dev/0.6.2-3 from Debian bookworm on a minimal Debian bullseye with libdbusada6-dev/0.6.0-3 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/dbusada/d_bus-arguments-basic.ali being contained in both packages. | Selecting previously unselected package libdbusada8-dev. | (Reading database ... 15407 files and directories currently installed.) | Preparing to unpack .../libdbusada8-dev_0.6.2-3_amd64.deb ... | Unpacking libdbusada8-dev (0.6.2-3) ... | dpkg: error processing archive ./libdbusada8-dev_0.6.2-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/dbusada/d_bus-arguments-basic.ali', which is also in package libdbusada6-dev 0.6.0-3 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libdbusada8-dev_0.6.2-3_amd64.deb Please ensure that libdbusada8-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: dbusada Source-Version: 0.6.2-4 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of dbusada, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated dbusada package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 11:34:08 +0200 Source: dbusada Architecture: source Version: 0.6.2-4 Distribution: unstable Urgency: medium Maintainer: Reto Buerki Changed-By: Nicolas Boulenguez Closes: 1034914 Changes: dbusada (0.6.2-4) unstable; urgency=medium . * Break/Replace libdbusada*-dev since oldstable. Closes: #1034914. Checksums-Sha1: 4a4391b87110334fbb4140c0fb14213fbc7f83be 2444 dbusada_0.6.2-4.dsc c68b8927eba45dfb3cdb5a2ab68fe86fcf202dad 7112 dbusada_0.6.2-4.debian.tar.xz 070e306b6bd3d19ca0a188f4edc4b2b646acfcfd 5588 dbusada_0.6.2-4_source.buildinfo Checksums-Sha256: 027ff307239ba99d0cdd521a2dcd1b16c0cf7be241d1b154f06e02bffc15c607 2444 dbusada_0.6.2-4.dsc 19f9d7cf88b119a562cd07586c8f5628a256734da48cdaccd2ee09367233d472 7112 dbusada_0.6.2-4.debian.tar.xz 18a71da90f6c0d671a37ea5681777cc18bce1ccb7a7172d1f1941e76a03a18e5 5588 dbusada_0.6.2-4_source.buildinfo Files: 4bb431483bd030ff0a0e6067d5abeed9 2444 libs optional dbusada_0.6.2-4.dsc 2fddecf4675925fda11d889567d5818f 7112 libs optional dbusada_0.6.2-4.debian.tar.xz 774b8d6a5a030d079faea75d5ff2d37b 5588 libs optional dbusada_0.6.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmRdOGYTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0ml/D/4v56bQzjjubZdTClpkU3vqjZ3aTjTh gHAwx8/Z9GZRcIFoq+r6cA5LmTJE/rzCO3JMIIX/l300IxqEarLXPLtaFImVfpTy 8nrJBa4sndlbLYkK3B1i0NKMY/upwCdl8KYhXmstc4xY1hY5Vpr915Ohy2MtO5f5 CDYHyKNWZLKNaeXz3gqB3TW0Mds3ZHYFMvH3b3CBgAJ2Mb9vC0+vW3+BtrGPNLFZ b86EDbqA4XI9QkdJZcsGNrCPfLb7dWF8sICmbx9hOKE5632JvMYWgPhUcYVHKyzf KPN2hsVZTZAfmrHDkWqFknMVu891zEr9ieiuiF6YSs9wrHYlXWNm3T4aY8Y4oxfi 372InCWcefF5s9EJLrmPvvHafJZX6qoSRMiBapRGyLfyyvGrhbUNWFzXlzXLNZg5 hGgb3Y4fhWPOK+/1CDwNbtqCC26pXvolEKIC/jwKmnXgDkLUdgcKZI9ggkNzeOD2 Blvyff/URu7Wd0sHjjBQ+11mv0EejX7h6weTLT+eikinW9a358ia+4rE4a6ySdlI hZKo+888JdgBcaqOLsWI7o+JlxZsw70FXRSMGbazE0uROQlqvNUBg1YkIIc69JiR fzFIyMMyKjtBMdVewkKD+5SNWZ9sSZZIN/yh+yStkntrG0H6s+vSmO6ebOx634zq ZK60GnrtAj0LzQ== =5HzR -END PGP SIGNATURE End Message ---
Processed: tagging 1035932, found 1035932 in 6.1.0-2, cloning 1035932, reassign -1 to src:cinder ...
Processing commands for cont...@bugs.debian.org:
> tags 1035932 + security upstream fixed-upstream
Bug #1035932 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Added tag(s) fixed-upstream, upstream, and security.
> found 1035932 6.1.0-2
Bug #1035932 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Marked as found in versions python-os-brick/6.1.0-2.
> clone 1035932 -1 -2 -3
Bug #1035932 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Bug 1035932 cloned as bugs 1035961-1035963
> reassign -1 src:cinder 2:21.1.0-2
Bug #1035961 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Bug reassigned from package 'src:python-os-brick' to 'src:cinder'.
No longer marked as found in versions python-os-brick/6.1.0-2 and
python-os-brick/6.2.0-1.
No longer marked as fixed in versions python-os-brick/6.1.0-3 and
python-os-brick/6.2.2-1.
Bug #1035961 {Done: Thomas Goirand } [src:cinder]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Marked as found in versions cinder/2:21.1.0-2.
> reassign -2 src:python-glance-store 4.1.0-3
Bug #1035962 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Bug reassigned from package 'src:python-os-brick' to 'src:python-glance-store'.
No longer marked as found in versions python-os-brick/6.1.0-2 and
python-os-brick/6.2.0-1.
No longer marked as fixed in versions python-os-brick/6.2.2-1 and
python-os-brick/6.1.0-3.
Bug #1035962 {Done: Thomas Goirand } [src:python-glance-store]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Marked as found in versions python-glance-store/4.1.0-3.
> reassign -3 src:nova 2:26.1.0-2
Bug #1035963 {Done: Thomas Goirand } [src:python-os-brick]
CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted
volume attachments
Bug reassigned from package 'src:python-os-brick' to 'src:nova'.
No longer marked as found in versions python-os-brick/6.1.0-2 and
python-os-brick/6.2.0-1.
No longer marked as fixed in versions python-os-brick/6.1.0-3 and
python-os-brick/6.2.2-1.
Bug #1035963 {Done: Thomas Goirand } [src:nova] CVE-2023-2088
/ OSSA-2023-003: Unauthorized volume access through deleted volume attachments
Marked as found in versions nova/2:26.1.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932
1035961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035961
1035962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035962
1035963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: merecat: diff for NMU version 2.31+git20220513+ds-4.1
Processing control commands: > tags 1035289 + patch Bug #1035289 [merecat] merecat: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf Added tag(s) patch. > tags 1035289 + pending Bug #1035289 [merecat] merecat: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf Added tag(s) pending. -- 1035289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035289: merecat: diff for NMU version 2.31+git20220513+ds-4.1
Control: tags 1035289 + patch Control: tags 1035289 + pending Dear maintainer, I've prepared an NMU for merecat (versioned as 2.31+git20220513+ds-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru merecat-2.31+git20220513+ds/debian/changelog merecat-2.31+git20220513+ds/debian/changelog --- merecat-2.31+git20220513+ds/debian/changelog 2023-02-23 07:09:58.0 +0100 +++ merecat-2.31+git20220513+ds/debian/changelog 2023-05-11 20:47:24.0 +0200 @@ -1,3 +1,13 @@ +merecat (2.31+git20220513+ds-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "postinst uses /usr/share/doc content (Policy 12.3): +/usr/share/doc/merecat/examples/merecat.conf": +Install example config files to /usr/share/merecat and symlink them from +/usr/share/doc/merecat/examples. (Closes: #1035289) + + -- gregor herrmann Thu, 11 May 2023 20:47:24 +0200 + merecat (2.31+git20220513+ds-4) unstable; urgency=medium * Upload to unstable. diff -Nru merecat-2.31+git20220513+ds/debian/install merecat-2.31+git20220513+ds/debian/install --- merecat-2.31+git20220513+ds/debian/install 2023-02-17 09:47:41.0 +0100 +++ merecat-2.31+git20220513+ds/debian/install 2023-05-11 20:47:24.0 +0200 @@ -1 +1,3 @@ merecat.service lib/systemd/system +throttle.conf usr/share/merecat +merecat.confusr/share/merecat diff -Nru merecat-2.31+git20220513+ds/debian/merecat.examples merecat-2.31+git20220513+ds/debian/merecat.examples --- merecat-2.31+git20220513+ds/debian/merecat.examples 2022-05-05 09:52:36.0 +0200 +++ merecat-2.31+git20220513+ds/debian/merecat.examples 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -throttle.conf -merecat.conf diff -Nru merecat-2.31+git20220513+ds/debian/merecat.links merecat-2.31+git20220513+ds/debian/merecat.links --- merecat-2.31+git20220513+ds/debian/merecat.links 1970-01-01 01:00:00.0 +0100 +++ merecat-2.31+git20220513+ds/debian/merecat.links 2023-05-11 19:58:06.0 +0200 @@ -0,0 +1,2 @@ +usr/share/merecat/throttle.conf usr/share/doc/merecat/examples/throttle.conf +usr/share/merecat/merecat.conf usr/share/doc/merecat/examples/merecat.conf signature.asc Description: Digital Signature
Bug#1029201: openbox-menu: do not release with bookworm
On 9.05.2023 at 14:47 +0200, Bastian Germann wrote: On Thu, 19 Jan 2023 15:17:26 +0100 mat...@linuxmint.pl wrote: openbox-menu should not be shipped in bookworm. Will you also file a RM bug or are you going to update the package for later releases? I found new place of source https://github.com/fabriceT/openbox-menu but is also dead, so I will create RM bug after bookworm release. -- .''`. Mateusz Łukasik : :' : l0calh0st.pl `. `' Debian Member - mat...@linuxmint.pl `-GPG: D93B 0C12 C8D0 4D7A AFBC FA27 CCD9 1D61 11A0 6851
Processed: tagging 1035957, tagging 1035956, tagging 1035955, tagging 1035954, tagging 1035953, tagging 1035952 ...
Processing commands for cont...@bugs.debian.org: > tags 1035957 + upstream Bug #1035957 [src:openjdk-17] openjdk-17: CVE-2023-21930 CVE-2023-21937 CVE-2023-21938 CVE-2023-21939 CVE-2023-21954 CVE-2023-21967 CVE-2023-21968 Added tag(s) upstream. > tags 1035956 + upstream Bug #1035956 [src:docker-registry] docker-registry: CVE-2023-2253 Added tag(s) upstream. > tags 1035955 + upstream Bug #1035955 [src:vim] vim: CVE-2023-2610 Added tag(s) upstream. > tags 1035954 + upstream Bug #1035954 [src:opencv] opencv: CVE-2023-2617 CVE-2023-2618 Added tag(s) upstream. > tags 1035953 + upstream Bug #1035953 [src:odoo] odoo: CVE-2021-23166 CVE-2021-23176 CVE-2021-23178 CVE-2021-23186 CVE-2021-23203 CVE-2021-26263 CVE-2021-26947 CVE-2021-44476 CVE-2021-44775 CVE-2021-45071 CVE-2021-45111 Added tag(s) upstream. > tags 1035952 + upstream Bug #1035952 [src:apache-jena] apache-jena: CVE-2023-22665 Added tag(s) upstream. > tags 1035951 + upstream Bug #1035951 [src:yasm] yasm: CVE-2023-29579 Added tag(s) upstream. > forwarded 1035951 https://github.com/yasm/yasm/issues/214 Bug #1035951 [src:yasm] yasm: CVE-2023-29579 Set Bug forwarded-to-address to 'https://github.com/yasm/yasm/issues/214'. > tags 1035950 + upstream Bug #1035950 [src:dav1d] dav1d: CVE-2023-32570 Added tag(s) upstream. > tags 1035936 + upstream Bug #1035936 [src:maradns] maradns: CVE-2023-31137 Added tag(s) upstream. > tags 1035935 + upstream Bug #1035935 [src:libpodofo] libpodofo: CVE-2023-31555 CVE-2023-31556 CVE-2023-31568 Added tag(s) upstream. > tags 1035934 + upstream Bug #1035934 [src:in-toto] in-toto: CVE-2023-32076 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1035934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035934 1035935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035935 1035936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035936 1035950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035950 1035951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035951 1035952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035952 1035953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035953 1035954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035954 1035955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035955 1035956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035956 1035957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035286: dnssec-trigger: diff for NMU version 0.17+repack-5.1
Control: tags 1035286 + patch Control: tags 1035286 + pending Dear maintainer, I've prepared an NMU for dnssec-trigger (versioned as 0.17+repack-5.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru dnssec-trigger-0.17+repack/debian/changelog dnssec-trigger-0.17+repack/debian/changelog --- dnssec-trigger-0.17+repack/debian/changelog 2021-01-12 06:30:22.0 +0100 +++ dnssec-trigger-0.17+repack/debian/changelog 2023-05-11 19:40:04.0 +0200 @@ -1,3 +1,14 @@ +dnssec-trigger (0.17+repack-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "missing Depends: openssl": +Add runtime dependency on openssl. +/usr/sbin/dnssec-trigger-control-setup, which is also called from the +postinst, runs the openssl binary. +(Closes: #1035286) + + -- gregor herrmann Thu, 11 May 2023 19:40:04 +0200 + dnssec-trigger (0.17+repack-5) unstable; urgency=medium * Recommend e2fsprogs (Closes: #887231) dnssec-trigger tries to call diff -Nru dnssec-trigger-0.17+repack/debian/control dnssec-trigger-0.17+repack/debian/control --- dnssec-trigger-0.17+repack/debian/control 2021-01-12 06:30:22.0 +0100 +++ dnssec-trigger-0.17+repack/debian/control 2023-05-11 19:39:30.0 +0200 @@ -27,6 +27,7 @@ python3-gi, python3-lockfile, gir1.2-nm-1.0 (>= 1.2) [linux-any], + openssl, sensible-utils, unbound Recommends: e2fsprogs signature.asc Description: Digital Signature
Processed: dnssec-trigger: diff for NMU version 0.17+repack-5.1
Processing control commands: > tags 1035286 + patch Bug #1035286 [dnssec-trigger] dnssec-trigger: missing Depends: openssl Added tag(s) patch. > tags 1035286 + pending Bug #1035286 [dnssec-trigger] dnssec-trigger: missing Depends: openssl Added tag(s) pending. -- 1035286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to popplerkit.framework, tagging 1035862
Processing commands for cont...@bugs.debian.org: > limit source popplerkit.framework Limiting to bugs with field 'source' containing at least one of 'popplerkit.framework' Limit currently set to 'source':'popplerkit.framework' > tags 1035862 + pending Bug #1035862 [libpopplerkit0] libpopplerkit0: broken symlinks: /usr/share/GNUstep/Frameworks/PopplerKit.framework/Versions/1.0/*.pfb -> ../../../../../fonts/type1/urw-base35/*.pfb Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1035862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034998: marked as done (pcp-export-pcp2elasticsearch: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:44 + with message-id and subject line Bug#1034998: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034998, regarding pcp-export-pcp2elasticsearch: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-export-pcp2elasticsearch Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2elasticsearch/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2elasticsearch being contained in both packages. | Selecting previously unselected package pcp-export-pcp2elasticsearch. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2elasticsearch ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2elasticsearch) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2elasticsearch (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2elasticsearch', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2elasticsearch has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE-
Bug#1034983: marked as done (pcp-export-pcp2json: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:44 + with message-id and subject line Bug#1034983: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034983, regarding pcp-export-pcp2json: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-export-pcp2json Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2json/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2json being contained in both packages. | Selecting previously unselected package pcp-export-pcp2json. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2json ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2json) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2json_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2json (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2json_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2json', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2json_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2json has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC FISFYRAAgCmZZEiCfwnYCCF6IaKmUhMGz2z8XicweSqxuIDnB4pt5kQl5xJgff7z
Bug#1034973: marked as done (pcp-export-pcp2zabbix: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:44 + with message-id and subject line Bug#1034973: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034973, regarding pcp-export-pcp2zabbix: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-export-pcp2zabbix Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2zabbix/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2zabbix being contained in both packages. | Selecting previously unselected package pcp-export-pcp2zabbix. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2zabbix ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2zabbix) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2zabbix_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2zabbix (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2zabbix_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2zabbix', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2zabbix_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2zabbix has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC FISFYRAAgCmZZEiCfwnYCCF6IaKmUhMGz2z8XicweSqxuIDnB4pt5kQl5xJgff7z
Bug#1034966: marked as done (pcp-doc: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:44 + with message-id and subject line Bug#1034966: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034966, regarding pcp-doc: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-doc Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-doc/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/share/pcp/examples/pcp2spark/PCP2SparkStreamCollector.python being contained in both packages. | Selecting previously unselected package pcp-doc. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-doc ... | dpkg: yes, will deconfigure pcp (broken by pcp-doc) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack ./pcp-doc_6.0.3-1_all.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-doc (6.0.3-1) ... | dpkg: error processing archive ./pcp-doc_6.0.3-1_all.deb (--unpack): | trying to overwrite '/usr/share/pcp/examples/pcp2spark/PCP2SparkStreamCollector.python', which is also in package pcp 5.2.6-1 | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-doc_6.0.3-1_all.deb Please ensure that pcp-doc has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC FISFYRAAgCmZZEiCfwnYCCF6IaKmUhMGz2z8XicweSqxuIDnB4pt5kQl5xJgff7z 1yFk0+GuPY8E7yEqTDwwDZ6BO1B7nh+Yee304BVu7VVOfDkRrhB2ylk5f8xZS50s mqQe98AtByPevJVuc6TFkXYA7CpFbdvOzw2i/cV9Appzs4cxdKRysbbCbKjrIbbT
Bug#1034932: marked as done (pcp-export-pcp2spark: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:43 + with message-id and subject line Bug#1034932: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034932, regarding pcp-export-pcp2spark: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-export-pcp2spark Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2spark/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2spark being contained in both packages. | Selecting previously unselected package pcp-export-pcp2spark. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2spark ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2spark) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2spark_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2spark (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2spark_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2spark', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2spark_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2spark has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC FISFYRAAgCmZZEiCfwnYCCF6IaKmUhMGz2z8XicweSqxuIDnB4pt5kQl5xJgff7z
Bug#1034895: marked as done (pcp-zeroconf: missing Replaces: pcp (<< ?))
Your message dated Thu, 11 May 2023 17:20:43 + with message-id and subject line Bug#1034895: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034895, regarding pcp-zeroconf: missing Replaces: pcp (<< ?) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-zeroconf Version: 6.0.3-1 Severity: serious Unpacking pcp-zeroconf from bookworm on a stable system with pcp installed fails: | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-zeroconf ... | dpkg: yes, will deconfigure pcp (broken by pcp-zeroconf) | (Reading database ... 10139 files and directories currently installed.) | Preparing to unpack pcp-zeroconf_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-zeroconf (6.0.3-1) ... | dpkg: error processing archive pcp-zeroconf_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/etc/pcp/pmieconf/zeroconf/all_threads', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | All runlevel operations denied by policy | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | pcp-zeroconf_6.0.3-1_amd64.deb Due to shipping /etc/pcp/pmieconf/zeroconf/all_threads in both pcp-zeroconf/bookworm and pcp/bullseye, pcp-zeroconf must declare Replaces: pcp (<< someversion) in addition to the existing Breaks. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC
Bug#1034922: marked as done (pcp-export-pcp2xml: missing Breaks+Replaces for pcp when upgrading from bullseye)
Your message dated Thu, 11 May 2023 17:20:43 + with message-id and subject line Bug#1034922: fixed in pcp 6.0.3-1.1 has caused the Debian Bug report #1034922, regarding pcp-export-pcp2xml: missing Breaks+Replaces for pcp when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pcp-export-pcp2xml Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2xml/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2xml being contained in both packages. | Selecting previously unselected package pcp-export-pcp2xml. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2xml ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2xml) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2xml_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2xml (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2xml_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2xml', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2xml_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2xml has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcp Source-Version: 6.0.3-1.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of pcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated pcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2023 11:36:37 +0200 Source: pcp Architecture: source Version: 6.0.3-1.1 Distribution: unstable Urgency: medium Maintainer: PCP Development Team Changed-By: Andreas Metzler Closes: 1034895 1034922 1034932 1034966 1034973 1034983 1034998 Changes: pcp (6.0.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add missing replaces on pcp (<< 5.3.0): + pcp-export-pcp2elasticsearch Closes: #1034998 + pcp-export-pcp2json Closes: #1034983 + pcp-export-pcp2spark Closes: #1034932 + pcp-export-pcp2xml Closes: #1034922 + pcp-export-pcp2zabbix Closes: #1034973 + pcp-doc Closes: #1034966 + pcp-zeroconf Closes: #1034895 + pcp-export-pcp2xlsx (unfiled) Checksums-Sha1: 6450f77234df546485aecd5e9d73959e9213a213 5175 pcp_6.0.3-1.1.dsc 7fd817c7836b6be4918a1b6e1bd8d6002a4bc711 26280 pcp_6.0.3-1.1.debian.tar.xz Checksums-Sha256: f9aa388cf71c73caa99341044519d186f259ae76d1310466e729a24091ca78e7 5175 pcp_6.0.3-1.1.dsc 7d54284faf10004a6d0dff5b251f78e46847e8c1013c7ed9d15954e0765e433b 26280 pcp_6.0.3-1.1.debian.tar.xz Files: 16c7ab116f647824b9a9a000ee633986 5175 utils extra pcp_6.0.3-1.1.dsc c7672ee08090ad57aeac008ee7162b4d 26280 utils extra pcp_6.0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRXhx0ACgkQpU8BhUOC FISFYRAAgCmZZEiCfwnYCCF6IaKmUhMGz2z8XicweSqxuIDnB4pt5kQl5xJgff7z
Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure
On Thu, May 11, 2023 at 06:25:00PM +0200, Guilhem Moulin wrote: > On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote: > > Nope, not really. Half VG was never a real thing. It might work in > > some cases. > And these use-cases are unbootable since 2.03.15… Those still have access to an old kernel and initramfs, so can be fixed without special knowledge. The fix is then to use vgsplit to have complete VG available. Why it worked in the past: there was a block activation script that just looked into the "root" parameter and enabled exactly that LV. That was a fallback to the udev activation. Bastian -- You can't evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3
Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure
On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote: > Nope, not really. Half VG was never a real thing. It might work in > some cases. And these use-cases are unbootable since 2.03.15… > Then, degraded is the default activation mode, so overriding that would > not be appropriate. But forcefully enabling stuff like an incomplete > raid will trigger rebuilds every time. So no, this can't be the default > option. If that's a concern then ‘--activationmode complete’ can be used instead (although the boot scripts used the default mode from lvm.conf). That's enough to fix the systems rapported here, because the required LVs are actually complete. -- Guilhem. signature.asc Description: PGP signature
Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote: > There might be a better way to detect an initramfs-tools environment > than checking whether ‘/run/initramfs’ exists (and ‘/run/systemd/system’ > doesn't). The only acceptable way would be a different udev rules file for the initramfs. Then, degraded is the default activation mode, so overriding that would not be appropriate. But forcefully enabling stuff like an incomplete raid will trigger rebuilds every time. So no, this can't be the default option. Bastian -- Conquest is easy. Control is not. -- Kirk, "Mirror, Mirror", stardate unknown
Bug#1035957: openjdk-17: CVE-2023-21930 CVE-2023-21937 CVE-2023-21938 CVE-2023-21939 CVE-2023-21954 CVE-2023-21967 CVE-2023-21968
Source: openjdk-17 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for openjdk-17. CVE-2023-21930[0]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition | product of Oracle Java SE (component: JSSE). Supported versions that | are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18, 17.0.6, | 20; Oracle GraalVM Enterprise Edition: 20.3.9, 21.3.5 and 22.3.1. | Difficult to exploit vulnerability allows unauthenticated attacker | with network access via TLS to compromise Oracle Java SE, Oracle | GraalVM Enterprise Edition. Successful attacks of this vulnerability | can result in unauthorized creation, deletion or modification access | to critical data or all Oracle Java SE, Oracle GraalVM Enterprise | Edition accessible data as well as unauthorized access to critical | data or complete access to all Oracle Java SE, Oracle GraalVM | Enterprise Edition accessible data. Note: This vulnerability applies | to Java deployments, typically in clients running sandboxed Java Web | Start applications or sandboxed Java applets, that load and run | untrusted code (e.g., code that comes from the internet) and rely on | the Java sandbox for security. This vulnerability can also be | exploited by using APIs in the specified Component, e.g., through a | web service which supplies data to the APIs. CVSS 3.1 Base Score 7.4 | (Confidentiality and Integrity impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). CVE-2023-21937[1]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition | product of Oracle Java SE (component: Networking). Supported versions | that are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18, | 17.0.6, 20; Oracle GraalVM Enterprise Edition: 20.3.9, 21.3.5 and | 22.3.1. Difficult to exploit vulnerability allows unauthenticated | attacker with network access via multiple protocols to compromise | Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks | of this vulnerability can result in unauthorized update, insert or | delete access to some of Oracle Java SE, Oracle GraalVM Enterprise | Edition accessible data. Note: This vulnerability applies to Java | deployments, typically in clients running sandboxed Java Web Start | applications or sandboxed Java applets, that load and run untrusted | code (e.g., code that comes from the internet) and rely on the Java | sandbox for security. This vulnerability can also be exploited by | using APIs in the specified Component, e.g., through a web service | which supplies data to the APIs. CVSS 3.1 Base Score 3.7 (Integrity | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N). CVE-2023-21938[2]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition | product of Oracle Java SE (component: Libraries). Supported versions | that are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18, | 17.0.6, 20; Oracle GraalVM Enterprise Edition: 20.3.8, 21.3.4 and | 22.3.0. Difficult to exploit vulnerability allows unauthenticated | attacker with network access via multiple protocols to compromise | Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks | of this vulnerability can result in unauthorized update, insert or | delete access to some of Oracle Java SE, Oracle GraalVM Enterprise | Edition accessible data. Note: This vulnerability applies to Java | deployments, typically in clients running sandboxed Java Web Start | applications or sandboxed Java applets, that load and run untrusted | code (e.g., code that comes from the internet) and rely on the Java | sandbox for security. This vulnerability does not apply to Java | deployments, typically in servers, that load and run only trusted code | (e.g., code installed by an administrator). CVSS 3.1 Base Score 3.7 | (Integrity impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N). CVE-2023-21939[3]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition | product of Oracle Java SE (component: Swing). Supported versions that | are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18, 17.0.6, | 20; Oracle GraalVM Enterprise Edition: 20.3.9, 21.3.5 and 22.3.1. | Easily exploitable vulnerability allows unauthenticated attacker with | network access via HTTP to compromise Oracle Java SE, Oracle GraalVM | Enterprise Edition. Successful attacks of this vulnerability can | result in unauthorized update, insert or delete access to some of | Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. | Note: This vulnerability applies to Java deployments, typically in | clients running sandboxed Java Web Start applications or sandboxed | Java applets, that load and run untrusted code (e.g., code that comes | from the internet) and rely on the Java sandbox for security. This | vulnerability can also be exploited by using APIs in the specified | Component, e.g., through a web service which
Bug#1034836: marked as done (initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell)
Your message dated Thu, 11 May 2023 17:42:35 +0200 with message-id <20230511154235.x7ioftoblgf2p...@shell.thinkmo.de> and subject line Re: Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure has caused the Debian Bug report #1018730, regarding initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.142 Severity: critical Justification: breaks the whole system X-Debbugs-Cc:pasztor.ja...@it.ppke.hu Dear Maintainer * What led up to the situation? I have upgraded my desktop machine (which is an old install, started with stretch ) from bullseye to bookworm * What was the outcome of this action? The boot process halts in the initramfs shell and I have to issue 'vgchange -ay' manually in order to continue. After that it asks for the LUKS password again for the second disk in the machine (both disks are having the same LUKS pw) * What outcome did you expect instead? Machine boots properly and asks only once for the LUKS pw during boot (as it has done it during bullseye) * Workaround I have installed the following hook to the initramfs generator in order to have a proper boot (pw asked twice still) -88--- root@asgard ~ # more /etc/initramfs-tools/hooks/crypttab-fix.sh #!/bin/sh cp /etc/crypttab "${DESTDIR}/cryptroot/crypttab" exit 0 -8<--END--->8--- * disk setup (nvme0n1 and sda are relevant) -8 8--- root@asgard ~ # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:00 3.6T 0 disk └─sda18:10 3.6T 0 part └─4Tsolid 254:30 3.6T 0 crypt └─asgardfs-home 254:40 3.3T 0 lvm /home/pasja/solid sdb 8:16 0 931.5G 0 disk ├─sdb18:17 016M 0 part └─sdb28:18 0 904.2G 0 part sdc 8:32 0 119.2G 0 disk ├─sdc18:33 016M 0 part ├─sdc28:34 0 113.7G 0 part ├─sdc38:35 0 100M 0 part └─sdc48:36 0 1M 0 part nvme0n1 259:00 931.5G 0 disk ├─nvme0n1p1 259:10 550M 0 part /boot/efi ├─nvme0n1p2 259:20 2G 0 part /boot └─nvme0n1p3 259:30 829G 0 part └─1Tnvme 254:00 829G 0 crypt ├─asgardfs-root 254:10 504.7G 0 lvm /gnu/store │ / └─asgardfs-swap 254:20 952M 0 lvm [SWAP] -8<--END--->8--- * fstab -8 8--- root@asgard ~ # more /etc/fstab /dev/mapper/asgardfs-root / xfs defaults0 1 UUID=6b9e331f-9f78-42fa-99af-04e587e3bf6d /boot xfsdefaults 0 2 /dev/mapper/asgardfs-home /home/pasja/solid xfs defaults0 2 /dev/mapper/asgardfs-swap noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 UUID=FAA7-BDB0 /boot/efi vfat defaults 0 2 -8<--END--->8--- * logs and other remarks Please find attached an initramfs.debug log from my last boot attempt. I also have the output of 'journalctl -b'. Please let me know if that would help the investigation. I have diff-ed both systemd (bullseye backports) and initramfs-tools (bullseye) to bookworm, but I have not spotted anything relevant which could explain this regression. Will try to reproduce it in a vm in order to have an environment where I can investigate it easier. Any pointers / questions would be appreciated here. Regards, János Pásztor -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 75M Apr 25 18:55 /boot/initrd.img-6.1.0-7-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-6.1.0-7-amd64 root=/dev/mapper/asgardfs-root ro debug -- resume RESUME=/dev/mapper/asgardfs-swap -- /proc/filesystems xfs fuseblk vfat -- lsmod Module
Bug#1018730: marked as done (lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure)
Your message dated Thu, 11 May 2023 17:42:35 +0200 with message-id <20230511154235.x7ioftoblgf2p...@shell.thinkmo.de> and subject line Re: Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure has caused the Debian Bug report #1018730, regarding lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lvm2 Version: 2.03.16-1 Severity: important X-Debbugs-Cc: vermee...@vermwa.re -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Since LVM 2.03.15 or possibly 2.03.16 my system fails to boot during initramfs because the root LVM LV is not activated. I did some digging and confirmed this is caused by the new method of using udev rules, which have a big flaw. In /lib/udev/rules.d/69-lvm.rules a VG is only activated once the VG is fully complete. However in initramfs my HDD arrays are not yet activated because they need keyfile stored on root partition for automatic activation. This means the VG is never complete (missing PVs) so it is never activated, meaning the root LV is never activated at all, resulting in boot failure with initramfs shell. I have the following storage stack in use on this system: Disk partition -> integrity -> mdadm -> luks -> lvm -> ext4 Integrity is not part of Debian, I submitted patches a while ago at: https://salsa.debian.org/cryptsetup-team/cryptsetup/-/merge_requests/22 My LVM setup is the following. The fc520 contains root, swap LV and all integritysetup meta LVs. The nas4 and ex12 PVs are exclusively used by hdd LV. root@verm-r4e:~# pvs PV VG Fmt Attr PSize PFree /dev/mapper/md_ex12_0_crypt verm-r4e lvm2 a-- 10.91t 0 /dev/mapper/md_fc520_0_crypt verm-r4e lvm2 a-- 1.81t 256.77g /dev/mapper/md_nas4_0_crypt verm-r4e lvm2 a-- <3.64t <565.54g root@verm-r4e:~# vgs VG #PV #LV #SN Attr VSize VFree verm-r4e 3 9 0 wz--l- 16.36t 822.31g root@verm-r4e:~# lvs LV VG Attr LSize hddverm-r4e -wi-ao 14.00t is_boot_0_meta verm-r4e -wi-ao 8.00m is_boot_1_meta verm-r4e -wi-ao 8.00m is_ex12_0_meta verm-r4e -wi-ao 11.41g is_ex12_1_meta verm-r4e -wi-ao 11.41g is_nas4_0_meta verm-r4e -wi-ao 4.14g is_nas4_1_meta verm-r4e -wi-ao 4.14g root verm-r4e -wi-ao 1.50t swap verm-r4e -wi-ao 32.00g Although my integrity setup is not common it's very common for servers with many encrypted disks is to have something like this: hdd -> mdadm -> luks -> lvm With current version udev rules simply having all these disks in the same VG will result in boot failure, because udev rule will only activate the entire VG once all PVs are there. The fix is to use behaviour like in old version and similar to cryptsetup hooks. Actaully parse what is needed from kernel arg, fstab, etc and try to activate these LVs directly even if the VG is incomplete. Concretely in my case the hook should activate verm-r4e/swap (resume device) and verm-r4e/root (root). This is quite a key regression for servers, as I'm not sure you can access initramfs shell remotely when it drops into it. Maybe if you have dropbear-initramfs setup? In my case it's on a workstation. Could you share thoughts and/or investigate this problem? Perhaps upstream udev rules are not suited for initramfs and only for regular system operation once fully booted? Thanks, Melvin Vermeeren. - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2 depends on: ii dmeventd2:1.02.185-1 ii dmsetup 2:1.02.185-1 ii init-system-helpers 1.64 ii libaio1 0.3.113-2 ii libblkid1 2.38.1-1 ii libc6 2.34-4 ii libdevmapper-event1.02.12:1.02.185-1 ii libedit23.1-20210910-1 ii libselinux1
Processed: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
Processing control commands: > affects -1 + zoph Bug #1035949 [src:mariadb] mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Added indication that 1035949 affects zoph -- 1035949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
Source: mariadb Version: 1:10.11.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + zoph Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails. This failure is observable while testing the zoph package. Since timing is unfortunate and upgrading zoph causes db accesses while the db is temporarily down, I tried to first upgrade default-mysql-server (as I usually do in this case) by running apt-get install default-mysql-server immediately after switching sources.list to bookworm (and running apt-get update to refresh the lists.) >From the attached log (scroll to the bottom...): Upgrading early: default-mysql-server ... Starting 2 pkgProblemResolver with broken count: 0 Done The following packages were automatically installed and are no longer required: libaio1 libsnappy1v5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gcc-12-base libc-bin libc6 libdaxctl1 libkmod2 libndctl6 libpmem1 libssl3 libstdc++6 liburing2 libzstd1 mariadb-client mariadb-client-core mariadb-common mariadb-server mariadb-server-core Suggested packages: glibc-doc libc-l10n locales libnss-nis libnss-nisplus mailx mariadb-test netcat-openbsd Recommended packages: manpages libdbd-mariadb-perl | libdbd-mysql-perl libterm-readkey-perl libhtml-template-perl mariadb-plugin-provider-bzip2 mariadb-plugin-provider-lz4 mariadb-plugin-provider-lzma mariadb-plugin-provider-lzo mariadb-plugin-provider-snappy pv The following packages will be REMOVED: mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 The following NEW packages will be installed: gcc-12-base libdaxctl1 libkmod2 libndctl6 libpmem1 libssl3 liburing2 mariadb-client mariadb-client-core mariadb-server mariadb-server-core The following packages will be upgraded: default-mysql-server libc-bin libc6 libstdc++6 libzstd1 mariadb-common 6 upgraded, 11 newly installed, 4 to remove and 189 not upgraded. Need to get 21.1 MB of archives. ... Preparing to unpack .../libc6_2.36-9_amd64.deb ... Unpacking libc6:amd64 (2.36-9) over (2.31-13+deb11u6) ... Setting up libc6:amd64 (2.36-9) ... Preparing to unpack .../libc-bin_2.36-9_amd64.deb ... Unpacking libc-bin (2.36-9) over (2.31-13+deb11u6) ... Setting up libc-bin (2.36-9) ... Preparing to unpack .../mariadb-common_1%3a10.11.2-1_all.deb ... Unpacking mariadb-common (1:10.11.2-1) over (1:10.5.19-0+deb11u2) ... Preparing to unpack .../default-mysql-server_1.1.0_all.deb ... Unpacking default-mysql-server (1.1.0) over (1.0.7) ... dpkg: mariadb-client-10.5: dependency problems, but removing anyway as you requested: mariadb-server-10.5 depends on mariadb-client-10.5 (>= 1:10.5.19-0+deb11u2). dbconfig-mysql depends on default-mysql-client | virtual-mysql-client; however: Package default-mysql-client is not installed. Package virtual-mysql-client is not installed. Package mariadb-client-10.5 which provides virtual-mysql-client is to be removed. Removing mariadb-client-10.5 (1:10.5.19-0+deb11u2) ... Removing mariadb-client-core-10.5 (1:10.5.19-0+deb11u2) ... dpkg: mariadb-server-10.5: dependency problems, but removing anyway as you requested: zoph depends on default-mysql-server | virtual-mysql-server; however: Package default-mysql-server is not configured yet. Package virtual-mysql-server is not installed. Package mariadb-server-10.5 which provides virtual-mysql-server is to be removed. Removing mariadb-server-10.5 (1:10.5.19-0+deb11u2) ... invoke-rc.d: could not determine current runlevel Stopping MariaDB database server: mariadbd [ESC][31mfailed![ESC][39;49m invoke-rc.d: initscript mariadb, action "stop" failed. dpkg: error processing package mariadb-server-10.5 (--remove): installed mariadb-server-10.5 package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: mariadb-server-10.5 Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) Here apt choses a suboptimal removal order: mariadb-server-10.5 gets removed (and therefore stopped, but that fails) only after mariadb-client-10.5 and mariadb-client-core-10.5 are already gone. I have tried the early upgrade scenario only with one other package that needs it (icinga2-ido-mysql), and there it worked flawless. Some bits from the log: ... Preparing to unpack .../mariadb-common_1%3a10.11.2-1_all.deb ... Unpacking mariadb-common (1:10.11.2-1) over (1:10.5.19-0+deb11u2) ... Preparing to unpack .../default-mysql-server_1.1.0_all.deb ... Unpacking default-mysql-server (1.1.0) over (1.0.7) ... Removing mariadb-server-10.5 (1:10.5.19-0+deb11u2) ...
Bug#1035947: fresh build from git fails with cannot access local variable 'new_file'
Source: firefox Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) I'm trying to build Firefox 113 from the git repository. I have pulled the package with: debcheckout firefox Then tried to download the latest tarballs with: uscan --download-current This crashes with a Python exception: anarcat@angela:firefox$ uscan --download-current Newest version of firefox on remote site is 113.0, specified download version is 113.0 uscan warn: Possible OpenPGP signature found at: https://archive.mozilla.org/pub/firefox/releases/113.0/source/firefox-113.0.source.tar.xz.asc * Add opts=pgpsigurlmangle=s/$/.asc/ or opts=pgpmode=auto to debian/watch * Add debian/upstream/signing-key.asc. See uscan(1) for more details Successfully symlinked ../firefox-113.0.source.tar.xz to ../firefox_113.0.orig.tar.xz. Traceback (most recent call last): File "/home/anarcat/dist/firefox/debian/repack.py", line 217, in main() File "/home/anarcat/dist/firefox/debian/repack.py", line 205, in main if not new_file: UnboundLocalError: cannot access local variable 'new_file' where it is not associated with a value uscan: error: python3 debian/repack.py --upstream-version 113.0 ../firefox_113.0.orig.tar.xz subprocess returned exit status 1 anarcat@angela:firefox[1]$ I believe the following patch fixes the issue somehow: diff --git i/debian/repack.py w/debian/repack.py index 00d20928f6e..4f04ea200fb 100755 --- i/debian/repack.py +++ w/debian/repack.py @@ -199,6 +199,8 @@ def main(): if options.new_file: new_file = options.new_file +else: +new_file = None if os.path.islink(args[0]): orig = os.path.realpath(args[0]) a. -- Package-specific info: -- Addons package information -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Processed: Re: Bug#1035872: tuxmath-data: broken symlink: /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> ../../fonts/truetype/andika/Andika-R.ttf
Processing control commands: > tags -1 + moreinfo Bug #1035872 [tuxmath-data] tuxmath-data: broken symlink: /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> ../../fonts/truetype/andika/Andika-R.ttf Added tag(s) moreinfo. > severity -1 important Bug #1035872 [tuxmath-data] tuxmath-data: broken symlink: /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> ../../fonts/truetype/andika/Andika-R.ttf Severity set to 'important' from 'serious' -- 1035872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035872: tuxmath-data: broken symlink: /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> ../../fonts/truetype/andika/Andika-R.ttf
control: tags -1 + moreinfo
control: severity -1 important
thanks
Hi Andreas,
as usual: thanks for this bug report and all the other piuparts bug reports you
are filing! \o/
On Wed, May 10, 2023 at 02:03:17PM +0200, Andreas Beckmann wrote:
> Package: tuxmath-data
> Severity: serious
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
why are those suddenly serious?
> 0m19.3s ERROR: FAIL: Broken symlinks:
> /usr/share/tuxmath/fonts/AndikaDesRevG.ttf ->
> ../../fonts/truetype/andika/Andika-R.ttf (tuxmath-data)
>
> /usr/share/fonts/truetype/andika/Andika-Regular.ttf might be an
> alternative target. (May need a versioned fonts-sil-andika dependency.)
from debian/control:
Package: tuxmath-data
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends},
fonts-sil-andika
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"Climate change" is an euphenism. "Global warming" as well.
signature.asc
Description: PGP signature
Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common
On 11/05/2023 14.58, Otto Kekäläinen wrote: Thanks for reporting! Is this sporadic or does it reproduce every time? Just reran it with the same result, so seems deterministic. If you tell me what information to collect, I can easily enter the chroot and test things after the failure occurred. We have this upgrade scenario in CI without issues, thus asking about reproducibility. Do you use mariadb-plugin-gssapi-server? Andreas
Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common
Thanks for reporting! Is this sporadic or does it reproduce every time? We have this upgrade scenario in CI without issues, thus asking about reproducibility.
Bug#1034976: marked as done (gensio-bin: missing Breaks+Replaces for libgensio-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 12:48:49 + with message-id and subject line Bug#1034976: fixed in gensio 2.6.2-4 has caused the Debian Bug report #1034976, regarding gensio-bin: missing Breaks+Replaces for libgensio-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gensio-bin Version: 2.6.2-3 Severity: serious Justification: dpkg unpack error Attempting to unpack gensio-bin/2.6.2-3 from Debian bookworm on a minimal Debian bullseye with libgensio-dev/2.2.4-1 installed, causes an unpack error from dpkg due to /usr/share/man/man5/gensio.5.gz being contained in both packages. | Selecting previously unselected package gensio-bin. | dpkg: considering deconfiguration of libgensio0:amd64, which would be broken by installation of gensio-bin ... | dpkg: yes, will deconfigure libgensio0:amd64 (broken by gensio-bin) | (Reading database ... 4951 files and directories currently installed.) | Preparing to unpack ./gensio-bin_2.6.2-3_amd64.deb ... | De-configuring libgensio0:amd64 (2.2.4-1) ... | Unpacking gensio-bin (2.6.2-3) ... | dpkg: error processing archive ./gensio-bin_2.6.2-3_amd64.deb (--unpack): | trying to overwrite '/usr/share/man/man5/gensio.5.gz', which is also in package libgensio-dev:amd64 2.2.4-1 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./gensio-bin_2.6.2-3_amd64.deb Please ensure that gensio-bin has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: gensio Source-Version: 2.6.2-4 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of gensio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated gensio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 09 May 2023 21:27:59 +0200 Source: gensio Architecture: source Version: 2.6.2-4 Distribution: unstable Urgency: medium Maintainer: Marc Haber Changed-By: Marc Haber Closes: 1031204 1034976 Changes: gensio (2.6.2-4) unstable; urgency=medium . * Apply patch removing duplicate symbols and making symbols optional. Thanks to Graham Inggs (Closes: #1031204) * gensio-bin: add missing Breaks+Replaces for libgensio-dev. Thanks to Helmut Grohne (Closes: #1034976) Checksums-Sha1: e16689134a9ab1c9eb6c8222099314ded8193aa5 2137 gensio_2.6.2-4.dsc 2b0570c2a738fdd3b6e18e1bd433fc630c1b11ef 12244 gensio_2.6.2-4.debian.tar.xz c4dd53bfbdc3ca76560f0667486dc5e6076f1d79 7237 gensio_2.6.2-4_source.buildinfo Checksums-Sha256: 9d0cac6aa811b153af57ab149ffd4c2592be7fa4601aee552f245ed6b01de6d4 2137 gensio_2.6.2-4.dsc d7cfc671949ebcabf16b1abf3e1a756e11af4d7d830453d831be3ba4a6729229 12244 gensio_2.6.2-4.debian.tar.xz 1dc9739f98c89d847394cbc4e4157d96c949d5637cb51ec53063c0c6841732bc 7237 gensio_2.6.2-4_source.buildinfo Files: 539d7bdcfd6397bdd5fc30675c2d0aa8 2137 libs optional gensio_2.6.2-4.dsc 336dd2c0982688b7f282c223912122a9 12244 libs optional gensio_2.6.2-4.debian.tar.xz 07df9a2fc5e29151bd057cb22b69d5c6 7237 libs optional gensio_2.6.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmRc3K8ACgkQj3cgEwEy BEId0A//VDzsLBDUb05xdgr/+8/6uAsP9JVZkemaXJdfXnuxcpMNMP6dcd/Ntd27 tMJOr7z+mTtLo1l3QHa+CZ0aPyQqLNjSrh/RKIcP9IJrSxiOIUclQ/5EVw3vSYKW 96QUSHaZy+DdLluofCiuJCtx1SbWXMtOaSRr+GmZunVmP2qEpq8yXi8g+Gz3IbvV Kkhn5OaeNmCkFlBHFcZJuwAAiap4Tl5F37iBggscrf+STnFyN/KoqPFTMUmQx+v6 8ALA2CQ3PqVoz0lR6WfqM7OTMMrlFu6muL9amCzGLZ6M1VSM0bhjCgnUVo6XixHC xALio7Aiz6PMC3GI2sEOz6rZGtp7o4ej7do1VlPqQ/iJJy75BzZew/hHC5bhKQ86 6jIhDkOa1vpBSTE5w9RuFlJEgdUvl9TRlCZdmqQ3OQ83XDT1CLWFvqpt3PDTb9fg gxhkeTbhqk54VI1iT6AUfkTpmuDDNbz/15SP75/NwY5q6kPpn+AXFf/+SKNfZbVs JGNwz5cXQ1dsTfLwLgGJxyXUfsv8/GnsqQO94DC8O56ddeUdS3p+EQInxev+w6pU WKUoNHm377mOUffQfR5n1VWTQ21XId64998zE4wyukN3QJe6G2LCbpcOZgbvAQo2
Processed: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common
Processing control commands: > affects -1 + mariadb-plugin-gssapi-server Bug #1035944 [src:mariadb] mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common Added indication that 1035944 affects mariadb-plugin-gssapi-server -- 1035944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common
Source: mariadb Version: 1:10.11.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + mariadb-plugin-gssapi-server Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails. This test was planned to do a 2-stage upgrade: apt-get upgrade && apt-get distupgrade (the first part does not install any new packages, that will happen in the second part) but the first part already failed. I try to summarize what seems to happen: * In a bullseye chroot (which alles starting services) install mariadb-plugin-gssapi-server * switch sources.list to bookworm, run 'apt-get update' * run 'apt-get upgrade' - this only upgrades mysql-common and mariadb-common - this triggers a mariadb-server-10.5 restart which fails >From the attached log (scroll to the bottom...): ... Preparing to unpack .../24-mysql-common_5.8+1.1.0_all.deb ... Unpacking mysql-common (5.8+1.1.0) over (5.8+1.0.7) ... Preparing to unpack .../25-mariadb-common_1%3a10.11.2-1_all.deb ... Unpacking mariadb-common (1:10.11.2-1) over (1:10.5.19-0+deb11u2) ... ... Setting up mysql-common (5.8+1.1.0) ... ... Setting up mariadb-common (1:10.11.2-1) ... ... Processing triggers for mariadb-server-10.5 (1:10.5.19-0+deb11u2) ... invoke-rc.d: could not determine current runlevel Stopping MariaDB database server: mariadbd. Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ESC][31mfailed![ESC][0m invoke-rc.d: initscript mariadb, action "restart" failed. dpkg: error processing package mariadb-server-10.5 (--configure): installed mariadb-server-10.5 package post-installation script subprocess returned error exit status 1 Processing triggers for debianutils (5.7-0.4) ... Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: mariadb-server-10.5 This might indicate that mariadb-common needs a Breaks: mariadb-server-10.5 I cannot reproduce this by testing default-mariadb-server in the same way, so mariadb-plugin-gssapi-server seems to be needed to trigger that bug. cheers, Andreas mariadb-plugin-gssapi-server_1:10.11.2-1.log.gz Description: application/gzip
Processed: notfound 1031797 in 3.-1
Processing commands for cont...@bugs.debian.org: > notfound 1031797 3.-1 Bug #1031797 [src:libsemanage] libsemanage: Inaccurate copyright file The source 'libsemanage' and version '3.-1' do not appear to match any binary packages No longer marked as found in versions libsemanage/3.-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035932: marked as done (CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments)
Your message dated Thu, 11 May 2023 12:21:47 + with message-id and subject line Bug#1035932: fixed in python-os-brick 6.2.2-1 has caused the Debian Bug report #1035932, regarding CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-os-brick Version: 6.2.0-1 Severity: grave OSSA-2023-003: Unauthorized volume access through deleted volume attachments :Date: May 10, 2023 :CVE: CVE-2023-2088 Affects ~~~ - Cinder: <20.2.1, >=21.0.0 <21.2.1, ==22.0.0 - Glance_store: <3.0.1, >=4.0.0 <4.1.1, >=4.2.0 <4.3.1 - Nova: <25.1.2, >=26.0.0 <26.1.2, ==27.0.0 - Os-brick: <5.2.3, >=6.0.0 <6.1.1, >=6.2.0 <6.2.2 Description ~~~ An unauthorized access to a volume could occur when an iSCSI or FC connection from a host is severed due to a volume being unmapped on the storage system and the device is later reused for another volume on the same host. **Scope:** Only deployments with iSCSI or FC volumes are affected. However, the fix for this issue includes a configuration change in Nova and Cinder that may impact you on your next upgrade regardless of what backend storage technology you use. See the *Configuration change* section below, and item 4(B) in the *Patches and Associated Deployment Changes* for details. This data leak can be triggered by two different situations. **Accidental case:** If there is a problem with network connectivity during a normal detach operation, OpenStack may fail to clean the situation up properly. Instead of force-detaching the compute node device, Nova ignores the error, assuming the instance has already been deleted. Due to this incomplete operation OpenStack may end up selecting the wrong multipath device when connecting another volume to an instance. **Intentional case:** A regular user can create an instance with a volume, and then delete the volume attachment directly in Cinder, which neglects to notify Nova. The compute node SCSI plumbing (over iSCSI/FC) will continue trying to connect to the original host/port/LUN, not knowing the attachment has been deleted. If a subsequent volume attachment re-uses the host/port/LUN for a different instance and volume, the original instance will gain access to it once the SCSI plumbing reconnects. Configuration Change To prevent the intentional case, the Block Storage API provided by Cinder must only accept attachment delete requests from Nova for instance-attached volumes. A complicating factor is that Nova deletes an attachment by making a call to the Block Storage API on behalf of the user (that is, by passing the user's token), which makes the request indistinguishable from the user making this request directly. The solution is to have Nova include a service token along with the user's token so that Cinder can determine that the detach request is coming from Nova. The ability for Nova to pass a service token has been supported since Ocata, but has not been required until now. Thus, deployments that are not currently sending service user credentials from Nova will need to apply the relevant code changes and also make configuration changes to solve the problem. Patches and Associated Deployment Changes - Given the above analysis, a thorough fix must include the following elements: 1. The os-brick library must implement the ``force`` option for fibre channel, which which has only been available for iSCSI until now (covered by the linked patches). 2. Nova must call os-brick with the ``force`` option when disconnecting volumes from deleted instances (covered by the linked patches). 3. In deployments where Glance uses the cinder glance_store driver, glance must call os-brick with the ``force`` option when disconnecting volumes (covered by the linked patches). 4. Cinder must distinguish between safe and unsafe attachment delete requests and reject the unsafe ones. This part of the fix has two components: a. The Block Storage API will return a 409 (Conflict) for a request to delete an attachment if there is an instance currently using the attachment, **unless** the request is being made by a service (for example, Nova) on behalf of a
Bug#1035932: marked as done (CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments)
Your message dated Thu, 11 May 2023 12:21:36 + with message-id and subject line Bug#1035932: fixed in python-os-brick 6.1.0-3 has caused the Debian Bug report #1035932, regarding CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-os-brick Version: 6.2.0-1 Severity: grave OSSA-2023-003: Unauthorized volume access through deleted volume attachments :Date: May 10, 2023 :CVE: CVE-2023-2088 Affects ~~~ - Cinder: <20.2.1, >=21.0.0 <21.2.1, ==22.0.0 - Glance_store: <3.0.1, >=4.0.0 <4.1.1, >=4.2.0 <4.3.1 - Nova: <25.1.2, >=26.0.0 <26.1.2, ==27.0.0 - Os-brick: <5.2.3, >=6.0.0 <6.1.1, >=6.2.0 <6.2.2 Description ~~~ An unauthorized access to a volume could occur when an iSCSI or FC connection from a host is severed due to a volume being unmapped on the storage system and the device is later reused for another volume on the same host. **Scope:** Only deployments with iSCSI or FC volumes are affected. However, the fix for this issue includes a configuration change in Nova and Cinder that may impact you on your next upgrade regardless of what backend storage technology you use. See the *Configuration change* section below, and item 4(B) in the *Patches and Associated Deployment Changes* for details. This data leak can be triggered by two different situations. **Accidental case:** If there is a problem with network connectivity during a normal detach operation, OpenStack may fail to clean the situation up properly. Instead of force-detaching the compute node device, Nova ignores the error, assuming the instance has already been deleted. Due to this incomplete operation OpenStack may end up selecting the wrong multipath device when connecting another volume to an instance. **Intentional case:** A regular user can create an instance with a volume, and then delete the volume attachment directly in Cinder, which neglects to notify Nova. The compute node SCSI plumbing (over iSCSI/FC) will continue trying to connect to the original host/port/LUN, not knowing the attachment has been deleted. If a subsequent volume attachment re-uses the host/port/LUN for a different instance and volume, the original instance will gain access to it once the SCSI plumbing reconnects. Configuration Change To prevent the intentional case, the Block Storage API provided by Cinder must only accept attachment delete requests from Nova for instance-attached volumes. A complicating factor is that Nova deletes an attachment by making a call to the Block Storage API on behalf of the user (that is, by passing the user's token), which makes the request indistinguishable from the user making this request directly. The solution is to have Nova include a service token along with the user's token so that Cinder can determine that the detach request is coming from Nova. The ability for Nova to pass a service token has been supported since Ocata, but has not been required until now. Thus, deployments that are not currently sending service user credentials from Nova will need to apply the relevant code changes and also make configuration changes to solve the problem. Patches and Associated Deployment Changes - Given the above analysis, a thorough fix must include the following elements: 1. The os-brick library must implement the ``force`` option for fibre channel, which which has only been available for iSCSI until now (covered by the linked patches). 2. Nova must call os-brick with the ``force`` option when disconnecting volumes from deleted instances (covered by the linked patches). 3. In deployments where Glance uses the cinder glance_store driver, glance must call os-brick with the ``force`` option when disconnecting volumes (covered by the linked patches). 4. Cinder must distinguish between safe and unsafe attachment delete requests and reject the unsafe ones. This part of the fix has two components: a. The Block Storage API will return a 409 (Conflict) for a request to delete an attachment if there is an instance currently using the attachment, **unless** the request is being made by a service (for example, Nova) on behalf of a
Processed: found 1031798 in 3.1-1
Processing commands for cont...@bugs.debian.org: > found 1031798 3.1-1 Bug #1031798 [src:libsepol] libsepol: Inaccurate copyright file Marked as found in versions libsepol/3.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1031797 in 3.1-1
Processing commands for cont...@bugs.debian.org: > found 1031797 3.1-1 Bug #1031797 [src:libsemanage] libsemanage: Inaccurate copyright file Marked as found in versions libsemanage/3.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1031797 in 3.-1
Processing commands for cont...@bugs.debian.org: > found 1031797 3.-1 Bug #1031797 [src:libsemanage] libsemanage: Inaccurate copyright file The source 'libsemanage' and version '3.-1' do not appear to match any binary packages Marked as found in versions libsemanage/3.-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/dfeb4ee8526e8bddb4764c7d64f21b27e3de821d * CVE-2023-30861: Unauthorized volume access through deleted volume attachments. Added upstream patch: Support force disconnect for FC (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Ignoring request to alter tags of bug #1035932 to the same tags previously set -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Ignoring request to alter tags of bug #1035932 to the same tags previously set -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/6c9c154a057d9bbb6af916ad1a2f23e2987cfbea * CVE-2023-30861: Unauthorized volume access through deleted volume attachments. Added upstream patch: Support force disconnect for FC (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/6c0e61af9c3f22e7cd4c0083fd6bc35708cbff2a * CVE-2023-30861: Unauthorized volume access through deleted volume attachments. Added upstream patch: Support force disconnect for FC (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Ignoring request to alter tags of bug #1035932 to the same tags previously set -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031152: system-config-printer: unlock button in system-config-printer provides no elevated permissions dialog
This unlikely to be a bug in system-config-printer as its delegate authentication to polkit and cups-pk-helper. Could you tell if you have cups-pk-helper installed and if running "pkexec ls" from a graphical terminal works? Cheers, Alban To other participants, you have to include the submitter email address in the Cc of your email else the bug report only ends up on the web UI. On Thu, 20 Apr 2023 18:47:25 -0400 Kevin Otte wrote: > On my Debian 11 XFCE machine this works correctly. Make sure "PolicyKit > Authentication Agent" is checked under "Session and Startup" -> > "Application Autostart". > > In Debian 12 under Sway the GNOME Authentication Agent segfaults, but I > will take this up under separate cover. I was able to work around the > issue for the moment by using lxpolkit for the authentication agent instead. > >
Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)
Package: linux-image-6.1.0-8-amd64-unsigned Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: cla...@mathr.co.uk Dear Maintainer, * What led up to the situation? I wanted to patch the kernel source to see if it would help an issue I was having, so I followed my usual steps when changing a Debian package locally: sudo apt build-dep linux-image-6.1.0-8-amd64-unsigned mkdir linux cd linux apt source linux-image-6.1.0-8-amd64-unsigned cd linux-6.1.25 # make changes to the source code # specfically some warning prints in devices/usb/host/xhci-ring.c debuild -i -us -uc -b * What was the outcome of this action? The build failed after some time with: ... llvm-strip -g /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/profiler.bpf.o make[4]: llvm-strip: No such file or directory make[4]: *** [Makefile:187: /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/profiler.bpf.o] Error 127 make[4]: *** Waiting for unfinished jobs llvm-strip -g /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/pid_iter.bpf.o make[4]: llvm-strip: No such file or directory make[4]: *** [Makefile:187: /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/pid_iter.bpf.o] Error 127 make[4]: Leaving directory '/home/claude/linux/linux-6.1.25/tools/bpf/bpftool' make[3]: *** [/home/claude/linux/linux-6.1.25/debian/rules.d/tools/bpf/bpftool/Makefile:15: all] Error 2 make[3]: Leaving directory '/home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool' make[2]: *** [debian/rules.real:538: build_bpftool] Error 2 make[2]: Leaving directory '/home/claude/linux/linux-6.1.25' make[1]: *** [debian/rules.gen:1494: build-arch_amd64_real_bpftool] Error 2 make[1]: Leaving directory '/home/claude/linux/linux-6.1.25' make: *** [debian/rules:39: build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -i -b failed * What outcome did you expect instead? I expected apt to have fetched all the build-time dependencies of the package, and the build to have succeeded. * What exactly did you do (or not do) that was effective (or ineffective)? After sudo apt install llvm then debuild -i -us -uc -b worked as expected. Thanks for your work on this package, Claude -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-8-amd64-unsigned depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-8-amd64-unsigned recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-8-amd64-unsigned suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-12 pn linux-doc-6.1
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/96cca7de67c2e76ca91b09117d316699cb69879c * CVE-2023-30861: Unauthorized volume access through deleted volume attachments. Added upstream patch: Support force disconnect for FC (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Ignoring request to alter tags of bug #1035932 to the same tags previously set -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Ignoring request to alter tags of bug #1035932 to the same tags previously set -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/766b5e22b7f98ce01dbb1279460572ed887d324f * CVE-2023-30861: Unauthorized volume access through deleted volume attachments. Added upstream patch: Support force disconnect for FC (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Processed: Bug#1035932 marked as pending in python-os-brick
Processing control commands: > tag -1 pending Bug #1035932 [src:python-os-brick] CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments Added tag(s) pending. -- 1035932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035932: marked as pending in python-os-brick
Control: tag -1 pending Hello, Bug #1035932 in python-os-brick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-brick/-/commit/0a3dc82a70a202620c39043261614c6fbc636fa1 * New upstream point release: - Fixes CVE-2023-2088: Unauthorized volume access through deleted volume attachments. (Closes: #1035932). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035932
Bug#1035932: CVE-2023-2088 / OSSA-2023-003: Unauthorized volume access through deleted volume attachments
Source: python-os-brick Version: 6.2.0-1 Severity: grave OSSA-2023-003: Unauthorized volume access through deleted volume attachments :Date: May 10, 2023 :CVE: CVE-2023-2088 Affects ~~~ - Cinder: <20.2.1, >=21.0.0 <21.2.1, ==22.0.0 - Glance_store: <3.0.1, >=4.0.0 <4.1.1, >=4.2.0 <4.3.1 - Nova: <25.1.2, >=26.0.0 <26.1.2, ==27.0.0 - Os-brick: <5.2.3, >=6.0.0 <6.1.1, >=6.2.0 <6.2.2 Description ~~~ An unauthorized access to a volume could occur when an iSCSI or FC connection from a host is severed due to a volume being unmapped on the storage system and the device is later reused for another volume on the same host. **Scope:** Only deployments with iSCSI or FC volumes are affected. However, the fix for this issue includes a configuration change in Nova and Cinder that may impact you on your next upgrade regardless of what backend storage technology you use. See the *Configuration change* section below, and item 4(B) in the *Patches and Associated Deployment Changes* for details. This data leak can be triggered by two different situations. **Accidental case:** If there is a problem with network connectivity during a normal detach operation, OpenStack may fail to clean the situation up properly. Instead of force-detaching the compute node device, Nova ignores the error, assuming the instance has already been deleted. Due to this incomplete operation OpenStack may end up selecting the wrong multipath device when connecting another volume to an instance. **Intentional case:** A regular user can create an instance with a volume, and then delete the volume attachment directly in Cinder, which neglects to notify Nova. The compute node SCSI plumbing (over iSCSI/FC) will continue trying to connect to the original host/port/LUN, not knowing the attachment has been deleted. If a subsequent volume attachment re-uses the host/port/LUN for a different instance and volume, the original instance will gain access to it once the SCSI plumbing reconnects. Configuration Change To prevent the intentional case, the Block Storage API provided by Cinder must only accept attachment delete requests from Nova for instance-attached volumes. A complicating factor is that Nova deletes an attachment by making a call to the Block Storage API on behalf of the user (that is, by passing the user's token), which makes the request indistinguishable from the user making this request directly. The solution is to have Nova include a service token along with the user's token so that Cinder can determine that the detach request is coming from Nova. The ability for Nova to pass a service token has been supported since Ocata, but has not been required until now. Thus, deployments that are not currently sending service user credentials from Nova will need to apply the relevant code changes and also make configuration changes to solve the problem. Patches and Associated Deployment Changes - Given the above analysis, a thorough fix must include the following elements: 1. The os-brick library must implement the ``force`` option for fibre channel, which which has only been available for iSCSI until now (covered by the linked patches). 2. Nova must call os-brick with the ``force`` option when disconnecting volumes from deleted instances (covered by the linked patches). 3. In deployments where Glance uses the cinder glance_store driver, glance must call os-brick with the ``force`` option when disconnecting volumes (covered by the linked patches). 4. Cinder must distinguish between safe and unsafe attachment delete requests and reject the unsafe ones. This part of the fix has two components: a. The Block Storage API will return a 409 (Conflict) for a request to delete an attachment if there is an instance currently using the attachment, **unless** the request is being made by a service (for example, Nova) on behalf of a user (covered by the linked patches). b. In order to recognize that a request is being made by a service on behalf of a user, Nova must be configured to send a service token along with the user token. If this configuration change is not made, the cinder change will reject **any** request to delete an attachment associated with a volume that is attached to an instance. Nova must be configured to send a service token to Cinder, and Cinder must be configured to accept service tokens. This is described in the following document and **IS NOT AUTOMATICALLY APPLIED BY THE LINKED PATCHES:** (Using service tokens to prevent long-running job failures) https://docs.openstack.org/cinder/latest/configuration/block-storage/service-token.html The Nova patch mentioned in step 2 includes a
Bug#1035931: cjs: Please don't use mozjs78
Source: cjs Version: 5.6.0-1 Severity: serious Tags: security sid cjs uses mozjs78. mozjs78 is the SpiderMonkey JavaScript engine from Firefox 78 ESR. Firefox 78 ESR received monthly security updates until October 2021. Since mozjs78 is no longer supported, please switch to mozjs102. This was done upstream recently in the (still unreleased) 5.7. https://github.com/linuxmint/cjs/commits/master Thank you, Jeremy Bícha
Bug#1034694: closing 1034694
close 1034694 thanks
Processed: closing 1034694
Processing commands for cont...@bugs.debian.org: > close 1034694 Bug #1034694 [gnome-core] gnome-core: Cannot install due to pipewire-audio dependency Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1034694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035670: marked as done (flask: CVE-2023-30861: Possible disclosure of permanent session cookie due to missing Vary: Cookie header)
Your message dated Thu, 11 May 2023 11:04:07 + with message-id and subject line Bug#1035670: fixed in flask 2.2.2-3 has caused the Debian Bug report #1035670, regarding flask: CVE-2023-30861: Possible disclosure of permanent session cookie due to missing Vary: Cookie header to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flask Version: 2.2.2-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for flask. CVE-2023-30861[0]: | Flask is a lightweight WSGI web application framework. When all of the | following conditions are met, a response containing data intended for | one client may be cached and subsequently sent by the proxy to other | clients. If the proxy also caches `Set-Cookie` headers, it may send | one client's `session` cookie to other clients. The severity depends | on the application's use of the session and the proxy's behavior | regarding cookies. The risk depends on all these conditions being met. | 1. The application must be hosted behind a caching proxy that does not | strip cookies or ignore responses with cookies. 2. The application | sets `session.permanent = True` 3. The application does not access or | modify the session at any point during a request. 4. | `SESSION_REFRESH_EACH_REQUEST` enabled (the default). 5. The | application does not set a `Cache-Control` header to indicate that a | page is private or should not be cached. This happens because | vulnerable versions of Flask only set the `Vary: Cookie` header when | the session is accessed or modified, not when it is refreshed (re-sent | to update the expiration) without being accessed or modified. This | issue has been fixed in versions 2.3.2 and 2.2.5. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-30861 https://www.cve.org/CVERecord?id=CVE-2023-30861 [1] https://github.com/pallets/flask/security/advisories/GHSA-m2qf-hxjv-5gpq Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: flask Source-Version: 2.2.2-3 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of flask, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated flask package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 May 2023 12:39:19 +0200 Source: flask Architecture: source Version: 2.2.2-3 Distribution: unstable Urgency: high Maintainer: Debian Python Team Changed-By: Thomas Goirand Closes: 1035670 Changes: flask (2.2.2-3) unstable; urgency=high . * CVE-2023-30861: Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header. Applied upstream patch: set Vary: Cookie header consistently for session (Closes: #1035670). Checksums-Sha1: f6ea3261f449f168552d1ab0efc56c794a866389 2497 flask_2.2.2-3.dsc e96fb745aad15c475173f092b2e4dd57c2ecab2b 8372 flask_2.2.2-3.debian.tar.xz fde59a1b079c3466fc297d72cac08cadf225cd48 8511 flask_2.2.2-3_amd64.buildinfo Checksums-Sha256: c53168c98b85bd6b74b8ac6b810bad6bcdfc8be0ae8c6be98367a115ee7e9550 2497 flask_2.2.2-3.dsc e20c2c4d90eb02780fa2712a4fd7b2c192bd856c403c8f104ebdffa5078bac21 8372 flask_2.2.2-3.debian.tar.xz 3d07c8f839a50f67f841583c0010edb598b767a436a31d839bbe5f2637787e3f 8511 flask_2.2.2-3_amd64.buildinfo Files: 17139565f967b5b6698e2304f9def61b 2497 python optional flask_2.2.2-3.dsc 87128aed635fac063ace7b32cff22bb1 8372 python optional flask_2.2.2-3.debian.tar.xz 43bd28a9e49000a0f48fd4697689caa6 8511 python optional flask_2.2.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1035792: marked as done (qt6-charts-dev: Missing dependecy on qml6-module-qtcharts)
Your message dated Thu, 11 May 2023 10:50:35 + with message-id and subject line Bug#1035792: fixed in qt6-charts 6.4.2-3 has caused the Debian Bug report #1035792, regarding qt6-charts-dev: Missing dependecy on qml6-module-qtcharts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qt6-charts-dev Version: 6.4.2-2 Severity: serious Dear Maintainer, When trying to build pyside6 I see : , | CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6qtchartsqml2Targets.cmake:96 (message): | The imported target "Qt6::qtchartsqml2" references the file | | "/usr/lib/x86_64-linux-gnu/qt6/qml/QtCharts/libqtchartsqml2plugin.so" | | but this file does not exist. Possible reasons include: | | * The file was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and contained | | "/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6qtchartsqml2Targets.cmake" | | but not all the files it references ` Christian -- System Information: Debian Release: 12.0 APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.1-1-custom (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt6-charts-dev depends on: ii libqt6charts6 6.4.2-2 ii libqt6chartsqml6 6.4.2-2 ii qt6-base-dev 6.4.2+dfsg-7 qt6-charts-dev recommends no packages. qt6-charts-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qt6-charts Source-Version: 6.4.2-3 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of qt6-charts, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated qt6-charts package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 12:25:19 +0200 Source: qt6-charts Architecture: source Version: 6.4.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1035792 Changes: qt6-charts (6.4.2-3) unstable; urgency=medium . [ Patrick Franz ] * Do not install cmake-files for Qml plugins (Closes: #1035792). Checksums-Sha1: 1cf019a2050a170169ebd9c8b03267d7955ce71f 2532 qt6-charts_6.4.2-3.dsc a12dbc4e22ce76aab895d2a54770942589007b84 29452 qt6-charts_6.4.2-3.debian.tar.xz fbc14537106bd262e04756a99a94f1922084352d 12705 qt6-charts_6.4.2-3_source.buildinfo Checksums-Sha256: 42bef5f5510078ac347a63587ff3404482689cd65b9a0e19ed2e0374bfae9e77 2532 qt6-charts_6.4.2-3.dsc ec2d589bd63afc73f6bfaa9fe9ee24982d23d41eedd0f81f7531c5ee552deb77 29452 qt6-charts_6.4.2-3.debian.tar.xz cc223d59deeb30e416155a566e1dc70babb888e94633f5e35e22e637832608ce 12705 qt6-charts_6.4.2-3_source.buildinfo Files: b8f209295fddad5623b2f4f5cfb2d2d2 2532 libs optional qt6-charts_6.4.2-3.dsc 66bfc5607bbfe0c0cc930c42a6df15d2 29452 libs optional qt6-charts_6.4.2-3.debian.tar.xz 1c95f24c12b509648b64747426cd193b 12705 libs optional qt6-charts_6.4.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmRcwsAACgkQnp96YDB3 /la6gw/9GirytgWu6g4IpvORGruKzrx25U7vD/ENK8J++WOA7xraT2WD7dFnJe5A XP8GdXGdHH4A5iOTUAdJZ/xqY7TVR0d/ZPctbxlg7n1EzKLZKGP4L6jAJq5fn3+q 0UtyOrDIc6P04UFbTtZI/jbdNXc7yYQ+htnPJb3qwmmNSeL8JTt7Ce24VK/oc6kQ ox4gDcp/T4gVEa0vRbbUMvcM52KxlWsmRv05iBnZ34WOtYeXO37iWpvrr9btHLdz jLaM+GR4S0Ssfxp6qZy4xfvZ5zmKmom3K0EPAskojz1a13LwgAxM4+u5q/ESaq3C 02uVz12cetaGeGbL16x8fRKFX4n07Ca/Vc2R/ui+phnPOBhHTkZJFwBdv8gCKtmg ffO3jwmgNPNjqe/ULew1b1ad4/+8dce2bvMagjNCtm5b39mbNo34yqxXxIEGhOyY
Bug#1035791: marked as done (qt6-datavisualization-dev: Missing dependency on qml6-module-qtdatavisualization)
Your message dated Thu, 11 May 2023 10:50:48 + with message-id and subject line Bug#1035791: fixed in qt6-datavis3d 6.4.2-3 has caused the Debian Bug report #1035791, regarding qt6-datavisualization-dev: Missing dependency on qml6-module-qtdatavisualization to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qt6-datavisualization-dev Version: 6.4.2-2 Severity: serious Dear Maintainer, When trying toi build pyside6 I see : , | CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6DataVisualizationQmlpluginTargets.cmake:96 (message): | The imported target "Qt6::DataVisualizationQmlplugin" references the file | | "/usr/lib/x86_64-linux-gnu/qt6/qml/QtDataVisualization/libdatavisualizationqmlplugin.so" | | but this file does not exist. Possible reasons include: | | * The file was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and contained | | "/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6DataVisualizationQmlpluginTargets.cmake" | | but not all the files it references. ` Christian -- System Information: Debian Release: 12.0 APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.1-1-custom (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt6-datavisualization-dev depends on: ii libqt6datavisualization6 6.4.2-2 ii libqt6datavisualizationqml6 6.4.2-2 ii qt6-base-dev 6.4.2+dfsg-7 qt6-datavisualization-dev recommends no packages. qt6-datavisualization-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qt6-datavis3d Source-Version: 6.4.2-3 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of qt6-datavis3d, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated qt6-datavis3d package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 12:34:27 +0200 Source: qt6-datavis3d Architecture: source Version: 6.4.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1035791 Changes: qt6-datavis3d (6.4.2-3) unstable; urgency=medium . [ Patrick Franz ] * Do not install cmake-files for Qml plugins (Closes: #1035791). Checksums-Sha1: 100be4f9f3f34405140bfb011b611f4699effe8d 2693 qt6-datavis3d_6.4.2-3.dsc fb6730e3f4d110108c487c607d7037580e3c1703 17200 qt6-datavis3d_6.4.2-3.debian.tar.xz 4e163a68230f1a4b8e7e6b62012517728a4ec271 12717 qt6-datavis3d_6.4.2-3_source.buildinfo Checksums-Sha256: d5eaa00377afc1aad530964ef95e858c9143f31a2ed83840b2c4cc06342a68e9 2693 qt6-datavis3d_6.4.2-3.dsc 1cfa40f1667f3d8b3dfeefeea17ea94996b208395f79a2cf94025477fb7add20 17200 qt6-datavis3d_6.4.2-3.debian.tar.xz 60e31afabcb09fd883b32ae142069ef048d865135332d2d082c2609b28e06575 12717 qt6-datavis3d_6.4.2-3_source.buildinfo Files: cdf16eb8ba39a70ecb90cdf277c8aa40 2693 libs optional qt6-datavis3d_6.4.2-3.dsc a484c7f47f9d2468654b14bdaf335dd1 17200 libs optional qt6-datavis3d_6.4.2-3.debian.tar.xz ca6ce07ba8771d5f6d6377bdf3d0ac22 12717 libs optional qt6-datavis3d_6.4.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmRcxM4ACgkQnp96YDB3 /lY8GBAAvk0K8byaMHt4UKNmvEKZM34sk+SB9AdERqK8NzWmZBUpLCf/i//4/1xY /Q2ngCQ3m9yewp6ThYzwBi1TNMnWilffnug0gIZeTeOB8Qa+A593jsAvuieiUboi flveXByT4Q1RjNbBXNbnzS7dHOjEyoYkhmQLepx25hpeO7mQQ27aC41Alc5iIVHd
Processed: Bug#1035670 marked as pending in flask
Processing control commands: > tag -1 pending Bug #1035670 [src:flask] flask: CVE-2023-30861: Possible disclosure of permanent session cookie due to missing Vary: Cookie header Added tag(s) pending. -- 1035670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035670: marked as pending in flask
Control: tag -1 pending Hello, Bug #1035670 in flask reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/flask/-/commit/ed3291de88a14c3e4d1db52d552dc5f24459edb2 * CVE-2023-30861: Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header. Applied upstream patch: set Vary: Cookie header consistently for session (Closes: #1035670). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035670
Bug#1034927: marked as done (libpcscada11-dev: missing Breaks+Replaces for libpcscada8-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 10:24:48 + with message-id and subject line Bug#1034927: fixed in pcscada 0.7.7-4 has caused the Debian Bug report #1034927, regarding libpcscada11-dev: missing Breaks+Replaces for libpcscada8-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpcscada11-dev Version: 0.7.7-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libpcscada11-dev/0.7.7-3 from Debian bookworm on a minimal Debian bullseye with libpcscada8-dev/0.7.6-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/pcscada/pcsc-scard-conversion.ali being contained in both packages. | Selecting previously unselected package libpcscada11-dev. | (Reading database ... 9196 files and directories currently installed.) | Preparing to unpack .../libpcscada11-dev_0.7.7-3_amd64.deb ... | Unpacking libpcscada11-dev (0.7.7-3) ... | dpkg: error processing archive ./libpcscada11-dev_0.7.7-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/pcscada/pcsc-scard-conversion.ali', which is also in package libpcscada8-dev 0.7.6-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libpcscada11-dev_0.7.7-3_amd64.deb Please ensure that libpcscada11-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pcscada Source-Version: 0.7.7-4 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of pcscada, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated pcscada package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 11:40:45 +0200 Source: pcscada Architecture: source Version: 0.7.7-4 Distribution: unstable Urgency: medium Maintainer: Reto Buerki Changed-By: Nicolas Boulenguez Closes: 1034927 Changes: pcscada (0.7.7-4) unstable; urgency=medium . * Break/Replace libpcscada*-dev since oldstable. Closes: #1034927 . Checksums-Sha1: 3b8d9355344a6290604e042ce37214d633fce9ff 2158 pcscada_0.7.7-4.dsc 8e5bf57a5916e4982413abe570e481d7e268d690 6536 pcscada_0.7.7-4.debian.tar.xz d21d09a2860cd1b73b534ba8494e7a2e8a0c86d9 5588 pcscada_0.7.7-4_source.buildinfo Checksums-Sha256: 32d8428a6750e2a0f9f71e22a2625881701c107cbf2daaa41beb59b33f93c762 2158 pcscada_0.7.7-4.dsc 609ee442f13cba17089493d3122e9935ac182efcb64ae5eee353eb7ee65548c6 6536 pcscada_0.7.7-4.debian.tar.xz 61f7c1b4ef42ed157f7a9b6ab1ac8ec2cd4b4e554a2cda16284112e13f0e2e21 5588 pcscada_0.7.7-4_source.buildinfo Files: 1e3dd5dea454567aa6a153f263e7077d 2158 libs optional pcscada_0.7.7-4.dsc d0c337245f8941bdbba6c8a7a9495618 6536 libs optional pcscada_0.7.7-4.debian.tar.xz 0102811acc008ae2a2432e045d25af82 5588 libs optional pcscada_0.7.7-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmRcuCsTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0rF2D/9ZegGht7BYkpPyydsTpAGelt5aTndn c5ZZbhbAVDuEgs0I5dOzZgu6MlFcis/yWlD1L3Kt8blagkevgu11m983bbNTkL6s zqj/DLyKIcx+Ne3q086bpAZnoSq3e0jO2HmJZ3NGIkgm15EpleA3iBLfywJgLcLR IuD4qspLqzjSTauXXfcVLXlzxi3LX5hn4fPYOM79KJ6OSWIeqR3E1nzLWlnJhxOp 3FNbuPTe9UPMxwk+ASMcK88bqAm4Wsb5Jw3/WNl5FasKqWFtbCoHUqSaCubvMOG7 hEuEkIZ2i3VjINvtG3EPd8Mw4wdDFDQ457F/YX7AAIacgvHkSeFwyaB7JxU7xT4o G4tSKAeXNOLkGPaRq6Ed3RYkXoEVbfFgn49tlBjS+jKA+TqV7udVtIQODRmlG6Ih TT1kVTJWJs/gfV4M7R9yUiYp4w2f1sQ2kGgu/JQHyGEEvQB9poQmtx8LJoURQSqE boSoo5+BKcJvRP2h0m/6IkMUQoJDH4aXkv2TYBbtuIw0zWz1Bm5SBzu3hl39vDKw fp30C03S0zDPxoTrB+eqyb1NgYfC7+q3sxUL4Xdug9Ka6Km+HYH1aaxreMpqId4q NgQ8Fas7lak/lCuDR+2QOHbQ/dTAuU1QpGwFj2sLywvi7rOH3RraE6USdGLBke19 4UqLyo4Xmsll0Q== =4o7c -END PGP SIGNATURE End Message ---
Bug#1035013: marked as done (libanet7-dev: missing Breaks+Replaces for libanet5-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 09:49:33 + with message-id and subject line Bug#1035013: fixed in anet 0.4.3-3 has caused the Debian Bug report #1035013, regarding libanet7-dev: missing Breaks+Replaces for libanet5-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libanet7-dev Version: 0.4.3-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libanet7-dev/0.4.3-2 from Debian bookworm on a minimal Debian bullseye with libanet5-dev/0.4.2-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali being contained in both packages. | Selecting previously unselected package libanet7-dev. | (Reading database ... 9228 files and directories currently installed.) | Preparing to unpack .../libanet7-dev_0.4.3-2_amd64.deb ... | Unpacking libanet7-dev (0.4.3-2) ... | dpkg: error processing archive ./libanet7-dev_0.4.3-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali', which is also in package libanet5-dev 0.4.2-4 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libanet7-dev_0.4.3-2_amd64.deb Please ensure that libanet7-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: anet Source-Version: 0.4.3-3 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of anet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated anet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 11:26:53 +0200 Source: anet Architecture: source Version: 0.4.3-3 Distribution: unstable Urgency: medium Maintainer: Reto Buerki Changed-By: Nicolas Boulenguez Closes: 1035013 Changes: anet (0.4.3-3) unstable; urgency=medium . * Break/Replace libanet*-dev since oldstable. Closes: #1035013 . Checksums-Sha1: 47e28f4a56fa14c44503c185efd7c8457cac11c6 2377 anet_0.4.3-3.dsc ad7dfcee4bfc5500880721386eabc210ef090418 6664 anet_0.4.3-3.debian.tar.xz f685e8dbb9bb00192aa59f1b8aa6c3530bc75307 5576 anet_0.4.3-3_source.buildinfo Checksums-Sha256: 43dc1e12970daab3c704d50c493dd93b5035d24c6978d9887358ceaba4e418a4 2377 anet_0.4.3-3.dsc c65c922a3c411dbb03ede839bcf102653884372190fbab07c2a3c9c789bc570c 6664 anet_0.4.3-3.debian.tar.xz 65dc9211eaae588d2f0269e8066eb00bc9f5ce4ba2faa817f06b63bed36e1439 5576 anet_0.4.3-3_source.buildinfo Files: cbd002549a03cb24d615428e80972446 2377 libs optional anet_0.4.3-3.dsc e62fc3fe5e535a6aedbc0a76d9233b08 6664 libs optional anet_0.4.3-3.debian.tar.xz 62a2a6fb4151e79ac60141bed6943359 5576 libs optional anet_0.4.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmRctPQTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0gfQEACbj+K0bpI4+CUS6RoztOmKqCSlqz+a JMRjPxLxxpFHEXQYcYZtMztUu5IK7GRjNsguhBvIpY7YvbY+PbI9L7Ad1LDw3a4O v/ANq+Ve6129CVq86yH/hhcm60Cx8EQNCRWfXNjj1hhmIUqlSk4kw/DTUFhKVK7A KKNXA/NFex5yjk+DYvF8kOUKHPPDQJbnLN2cz5oZwO1o0pr1cw+B0YWAWXnn2S0j wJWXFV9On4jcIbI0MPgbXVplMMGD6vGZLUKrEGPXA+8Ygj4RuPkRYMr2fjuCRGKN PIJYoZvx3jn7OqncrHqUYKTCzAZvs8SETEuMwt/5ehdfTmDucxJlzuaVjL87HXev eLN2r3CKLVbCCBWEbv+gvoJnl0ed9HRRNwOH8h8bTaU29Zeup2/HHEfRw1I8wXV/ ju3X73FEQBo3areSMpP0gDw26b+bh2Iasapbz+HC8+e97aKTLEnDx2Q2Xv6I24nA sqAuR6AOJDXTJVQ8orryzlbKTtiss5R7O7iyUa+zHYMlyA3w9ln8AO4kgGMipyOv J/nMoRxTYuskSsEDXbKjD72iIdc4IIR62S7mbLq5LafTGDU45JZ/3w+esMxjx8pR 1g6xKiVbAol5/p3rqqgFGavE4M9PSnixYhDWkSGzcUgfee4EwKSR3ouZ9oyvAu5d ICtUiBPjrAzYFA== =0wZ5 -END PGP SIGNATURE End Message ---
Bug#1035004: marked as done (libalog8-dev: missing Breaks+Replaces for libalog6-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 09:35:33 + with message-id and subject line Bug#1035004: fixed in libalog 0.6.2-3 has caused the Debian Bug report #1035004, regarding libalog8-dev: missing Breaks+Replaces for libalog6-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libalog8-dev Version: 0.6.2-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libalog8-dev/0.6.2-2 from Debian bookworm on a minimal Debian bullseye with libalog6-dev/0.6.1-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali being contained in both packages. | Selecting previously unselected package libalog8-dev. | (Reading database ... 9183 files and directories currently installed.) | Preparing to unpack .../libalog8-dev_0.6.2-2_amd64.deb ... | Unpacking libalog8-dev (0.6.2-2) ... | dpkg: error processing archive ./libalog8-dev_0.6.2-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali', which is also in package libalog6-dev 0.6.1-4 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libalog8-dev_0.6.2-2_amd64.deb Please ensure that libalog8-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: libalog Source-Version: 0.6.2-3 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of libalog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated libalog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 11:14:21 +0200 Source: libalog Architecture: source Version: 0.6.2-3 Distribution: unstable Urgency: medium Maintainer: Adrian-Ken Rueegsegger Changed-By: Nicolas Boulenguez Closes: 1035004 Changes: libalog (0.6.2-3) unstable; urgency=medium . * Break/Replace libalog*-dev since oldstable. Closes: #1035004. Checksums-Sha1: 1abbdc193730a3a7576426553557388f2ee1b08d 2509 libalog_0.6.2-3.dsc e3f0e382c6db0f25b5baeb8aa62e68eb2c8579a6 7112 libalog_0.6.2-3.debian.tar.xz 38a1ebc9a1d4916279f31cb1059318f335d4e8a4 5588 libalog_0.6.2-3_source.buildinfo Checksums-Sha256: f1d3f13628206fcf3abdad82e06fbb00be8b3ff67f93867110f82b090323a6ca 2509 libalog_0.6.2-3.dsc 694689c6d027c708d9fef9b3e7f3da343e9c21ccad04bdbe41db2f99f05187b5 7112 libalog_0.6.2-3.debian.tar.xz 4fdb83164a0b243258b62b71905a8396fc2c3582aa4c9223c4b5583fc622bb9d 5588 libalog_0.6.2-3_source.buildinfo Files: f8b28925541ede5f78d246bc2e623024 2509 libs optional libalog_0.6.2-3.dsc 743e0e271b0ed6c2801a799c16a0f322 7112 libs optional libalog_0.6.2-3.debian.tar.xz 4098c1007af99914c7dfca8258a63ed1 5588 libs optional libalog_0.6.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmRcsnMTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0pT2EACt8uinTdsRaCE/cul1PWaR6992x3gX bAQA8xDM8eh50SPz/Emi51Whb15MHZUhCjHoMvSdIZwVzAVM3MEKYVzsS4bWo+lf bzvGzHNaN1DpGoxcqAKm7sHTj7LkLn9pkYUCjebdiExqVtPcjul83CIv9Al0i4n3 Nn+pEHXRz5OmsCVdsOP2FqGcjkNeWOnvOhDwvHWFZLjOA3Bp0FRFQmqAwCQqCWrH oEuUcJkw3LehGVZ3LnmviAX6cAUHGjqrLPCSkh3qTd1XjulGY9pRRKOCOuHpjLkN TzuE0uPjAtBWy/faIhQHerTigdk3PIPdGvr1QFt7rJtGlCvMLShrXbw0IczCEEPn GoAx04g1AzHNhowjCiCY3vopaDH1g7V5V+IMCjfy0r1oMf4PBFEMat0mL1nClwBt Ae4j6KSxBhgPiksgtOOh89hrhoXQQqw7QH0Np0EL2IRGf8gVClrSqLTqwdfvSwh/ eyQaPBNnFiOLvjx244Zob0arWjqtpOfn0SIJMoC4/0MqDZ9NaljpOplROSAC4fot xrvlDZkPNe/uh6y8FxnFGsA9Uwpd3VflSkvXBxOwgBTkdtbCx93sy6DZLd103bNK CSznFlKCIy5TqPli0c2qLWhVlnXt2HBDqGkKCP9ZcazgQ8leQ89m32BcQ+hVK9ki h/EXOs8uGvagsQ== =iWiQ -END PGP SIGNATURE End Message ---
Bug#1035011: marked as done (libahven11-dev: missing Breaks+Replaces for libahven9-dev when upgrading from bullseye)
Your message dated Thu, 11 May 2023 09:19:00 + with message-id and subject line Bug#1035011: fixed in ahven 2.8-7 has caused the Debian Bug report #1035011, regarding libahven11-dev: missing Breaks+Replaces for libahven9-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libahven11-dev Version: 2.8-6 Severity: serious Justification: dpkg unpack error Attempting to unpack libahven11-dev/2.8-6 from Debian bookworm on a minimal Debian bullseye with libahven9-dev/2.8-1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali being contained in both packages. | Selecting previously unselected package libahven11-dev. | (Reading database ... 9179 files and directories currently installed.) | Preparing to unpack .../libahven11-dev_2.8-6_amd64.deb ... | Unpacking libahven11-dev (2.8-6) ... | dpkg: error processing archive ./libahven11-dev_2.8-6_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali', which is also in package libahven9-dev 2.8-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libahven11-dev_2.8-6_amd64.deb Please ensure that libahven11-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: ahven Source-Version: 2.8-7 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of ahven, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated ahven package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 May 2023 10:43:00 +0200 Source: ahven Architecture: source Version: 2.8-7 Distribution: unstable Urgency: medium Maintainer: Reto Buerki Changed-By: Nicolas Boulenguez Closes: 1035011 Changes: ahven (2.8-7) unstable; urgency=medium . * Break/Replace libahven*-dev since oldstable. Closes: #1035011. Checksums-Sha1: 8288d760b57b453069222f34aca5f22c4d88749a 2255 ahven_2.8-7.dsc bf6633e23891ad0756ae147189644dd003aaa947 7992 ahven_2.8-7.debian.tar.xz 6c5dedd5426a4d41dbcd48a857ed715504de37dd 5572 ahven_2.8-7_source.buildinfo Checksums-Sha256: 4086e7da6d0aa1323740ebf5ca43aa5d7137347d3f6527627ede1856e04ef485 2255 ahven_2.8-7.dsc 49547fb495c18f41fee79a23cc242b5a39fe14a54dcb339c1209c52bf561b60d 7992 ahven_2.8-7.debian.tar.xz 71d77c3617a6d5efa25a83a99437da685e56cbd8dcd64a0308e5366775ff7411 5572 ahven_2.8-7_source.buildinfo Files: af3176d181fcc57691bba4f202ffa799 2255 libs optional ahven_2.8-7.dsc 5da827e9a3725ace671204dd3467028f 7992 libs optional ahven_2.8-7.debian.tar.xz 700bbc71d81363ea26faf97a4cbd464d 5572 libs optional ahven_2.8-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmRcrfETHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0lK/D/0Z1T8AoMFd51haQacJpHaxSipH+59N MD46n9eg1hETA5SQlDBrZhpFOwUr3dIjPbrKUv36h1mNJqpAL3+8I8nXEz/PVRRY njSfR/PvYaTMSwuDgi+cPdYqOcZb7RN/G3Uzp93/evnIZSiKMWhpJKbJJYbh36fX cZ+EAqp6sSl1v6ELEecw17ltkD396frVsNZ3BdnWh6fV5OkawW3TgVgRlWNYp/JP Yx7NWOUmWKl/4068PtCWGlpZ9aH3kgHE/B1G9YZczUvQnnNlUDvCqVCbaBUhieto jt+2TxLdlHUgE9TVj4/FkORf1Xvx5mx3Vf6SknNWxH4chfMoL64GasWPGErkcQSL dr5llNjlH1/xcEXf10Z+nekBPvkgJtmh8C6QPGLxUQ84yowAARwNyXbwWHvIyqVv 6apAIA4UsHnhgeUhHrWWFztPPIREHnwqtAuOjnyUITT425KwAuTBcipJRnMLHV9g RhPBNYzppZBOlQjOTbJnYBXw3OQTXKKEjnFTKMEF2OHX6vEqqdmN3tOqpmhhwadk r+i2hvlR1DAF6QFLBjdkYgT5YULSWXV3b57942JOXycXP2cMTeAGU+INsbDeX9cL S0389VnCf+3PSPD8AeU9gy4lP+jNJh0S6b+18mk7IJT64PYNVunNxEdGpibCd+dq vnvjzXNJiRYgNg== =d2ik -END PGP SIGNATURE End Message ---
Processed: user debian...@lists.debian.org, found 1035604 in 20221002-9
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > found 1035604 20221002-9 Bug #1035604 [progress-linux-container] progress-linux-container: fails to upgrade from 'bullseye': diversion conflict Marked as found in versions progress-linux-metapackages/20221002-9. > thanks Stopping processing here. Please contact me if you need assistance. -- 1035604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035870: marked as done (libgnunet-dev: missing Depends: gnunet (= ${binary:Version}))
Your message dated Thu, 11 May 2023 08:51:17 +
with message-id
and subject line Bug#1035870: fixed in gnunet 0.19.4-2
has caused the Debian Bug report #1035870,
regarding libgnunet-dev: missing Depends: gnunet (= ${binary:Version})
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1035870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnunet-dev
Version: 0.19.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m44.3s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/libgnunetats.so -> libgnunetats.so.4.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetblock.so -> libgnunetblock.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetblockgroup.so ->
libgnunetblockgroup.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetcadet.so -> libgnunetcadet.so.7.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetconsensus.so ->
libgnunetconsensus.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetconversation.so ->
libgnunetconversation.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetcore.so -> libgnunetcore.so.0.0.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdatacache.so ->
libgnunetdatacache.so.0.0.1 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdatastore.so ->
libgnunetdatastore.so.1.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdht.so -> libgnunetdht.so.4.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdid.so -> libgnunetdid.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdns.so -> libgnunetdns.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfragmentation.so ->
libgnunetfragmentation.so.2.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfriends.so -> libgnunetfriends.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfs.so -> libgnunetfs.so.2.1.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgns.so -> libgnunetgns.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgnsrecord.so ->
libgnunetgnsrecord.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgnsrecordjson.so ->
libgnunetgnsrecordjson.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunethello.so -> libgnunethello.so.0.1.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetidentity.so -> libgnunetidentity.so.1.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetmessenger.so ->
libgnunetmessenger.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetmicrophone.so ->
libgnunetmicrophone.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnamecache.so ->
libgnunetnamecache.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnamestore.so ->
libgnunetnamestore.so.0.0.1 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnatauto.so -> libgnunetnatauto.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnatnew.so -> libgnunetnatnew.so.2.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnse.so -> libgnunetnse.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnt.so -> libgnunetnt.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpeerinfo.so -> libgnunetpeerinfo.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpeerstore.so ->
libgnunetpeerstore.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpq.so -> libgnunetpq.so.3.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetreclaim.so -> libgnunetreclaim.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetregex.so -> libgnunetregex.so.3.0.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetregexblock.so ->
libgnunetregexblock.so.1.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetrest.so -> libgnunetrest.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetrevocation.so ->
libgnunetrevocation.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetscalarproduct.so ->
libgnunetscalarproduct.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetsecretsharing.so ->
libgnunetsecretsharing.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetset.so -> libgnunetset.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetseti.so -> libgnunetseti.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetsetu.so -> libgnunetsetu.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetspeaker.so -> libgnunetspeaker.so.0.0.0
Bug#1035870: marked as done (libgnunet-dev: missing Depends: gnunet (= ${binary:Version}))
Your message dated Thu, 11 May 2023 08:50:55 +
with message-id
and subject line Bug#1035870: fixed in gnunet 0.19.3-2
has caused the Debian Bug report #1035870,
regarding libgnunet-dev: missing Depends: gnunet (= ${binary:Version})
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1035870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnunet-dev
Version: 0.19.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m44.3s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/libgnunetats.so -> libgnunetats.so.4.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetblock.so -> libgnunetblock.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetblockgroup.so ->
libgnunetblockgroup.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetcadet.so -> libgnunetcadet.so.7.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetconsensus.so ->
libgnunetconsensus.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetconversation.so ->
libgnunetconversation.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetcore.so -> libgnunetcore.so.0.0.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdatacache.so ->
libgnunetdatacache.so.0.0.1 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdatastore.so ->
libgnunetdatastore.so.1.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdht.so -> libgnunetdht.so.4.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdid.so -> libgnunetdid.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetdns.so -> libgnunetdns.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfragmentation.so ->
libgnunetfragmentation.so.2.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfriends.so -> libgnunetfriends.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetfs.so -> libgnunetfs.so.2.1.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgns.so -> libgnunetgns.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgnsrecord.so ->
libgnunetgnsrecord.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetgnsrecordjson.so ->
libgnunetgnsrecordjson.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunethello.so -> libgnunethello.so.0.1.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetidentity.so -> libgnunetidentity.so.1.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetmessenger.so ->
libgnunetmessenger.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetmicrophone.so ->
libgnunetmicrophone.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnamecache.so ->
libgnunetnamecache.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnamestore.so ->
libgnunetnamestore.so.0.0.1 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnatauto.so -> libgnunetnatauto.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnatnew.so -> libgnunetnatnew.so.2.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnse.so -> libgnunetnse.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetnt.so -> libgnunetnt.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpeerinfo.so -> libgnunetpeerinfo.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpeerstore.so ->
libgnunetpeerstore.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetpq.so -> libgnunetpq.so.3.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetreclaim.so -> libgnunetreclaim.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetregex.so -> libgnunetregex.so.3.0.1
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetregexblock.so ->
libgnunetregexblock.so.1.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetrest.so -> libgnunetrest.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetrevocation.so ->
libgnunetrevocation.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetscalarproduct.so ->
libgnunetscalarproduct.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetsecretsharing.so ->
libgnunetsecretsharing.so.0.0.0 (libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetset.so -> libgnunetset.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetseti.so -> libgnunetseti.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetsetu.so -> libgnunetsetu.so.0.0.0
(libgnunet-dev)
/usr/lib/x86_64-linux-gnu/libgnunetspeaker.so -> libgnunetspeaker.so.0.0.0
Processed: cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm
Processing control commands: > affects -1 + debian-cloud-images-packages Bug #1035920 [cloud-initramfs-growroot] cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm Added indication that 1035920 affects debian-cloud-images-packages -- 1035920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035920: cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm
Package: cloud-initramfs-growroot
Version: 0.18.debian12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + debian-cloud-images-packages
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up linux-image-6.1.0-8-amd64 (6.1.25-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-8-cloud-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-8-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-8-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-8-amd64
W: No zstd in /usr/bin:/sbin:/bin, using gzip
E: /usr/share/initramfs-tools/hooks/growroot failed with return 1.
update-initramfs: failed for /boot/initrd.img-6.1.0-8-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-8-amd64 (--configure):
installed linux-image-6.1.0-8-amd64 package post-installation script
subprocess returned error exit status 1
After injecting set -x in the growroot hook:
# dpkg --configure --pending
Setting up linux-image-6.1.0-8-cloud-amd64 (6.1.25-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-8-cloud-amd64
W: No zstd in /usr/bin:/sbin:/bin, using gzip
+ set -e
+ PREREQS=
+ echo
+ exit 0
+ set -e
+ PREREQS=
+ . /usr/share/initramfs-tools/hook-functions
+ copy_exec /sbin/sfdisk /sbin
+ local src target x nonoptlib ret
+ src=/sbin/sfdisk
+ target=/sbin
+ copy_file binary /sbin/sfdisk /sbin
+ local type src target link_target
+ type=binary
+ src=/sbin/sfdisk
+ target=/sbin
+ [ -f /sbin/sfdisk ]
+ [ -d /var/tmp/mkinitramfs_eGzSvp//sbin ]
+ target=/sbin/sfdisk
+ target=/usr/sbin/sfdisk
+ [ -e /var/tmp/mkinitramfs_eGzSvp//usr/sbin/sfdisk ]
+ mkdir -p /var/tmp/mkinitramfs_eGzSvp//usr/sbin
+ [ -h /sbin/sfdisk ]
+ [ n = y ]
+ cp -pP /sbin/sfdisk /var/tmp/mkinitramfs_eGzSvp//usr/sbin/sfdisk
+ sed -e
/\//!d;
/linux-gate/d;
/=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/
+ env --unset=LD_PRELOAD ldd /sbin/sfdisk
+ sed -e
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ echo /usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ nonoptlib=/usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ echo /usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ nonoptlib=/usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ [ -e /usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ x=/usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ copy_file binary /usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ local type src target link_target
+ type=binary
+ src=/usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ target=/usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ [ -f /usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ [ -d /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ [ -e /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ mkdir -p /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu
+ [ -h /usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ readlink -f /usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ link_target=/usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
+ src=/usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
+ [ /usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0 !=
/usr/lib/x86_64-linux-gnu/libfdisk.so.1 ]
+ [ n = y ]
+ ln -rs
/var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
/var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1
+ target=/usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
+ [ -e /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0 ]
+ mkdir -p /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu
+ [ n = y ]
+ cp -pP /usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
/var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libfdisk.so.1.1.0
+ echo /usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ sed -e
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ nonoptlib=/usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ echo /usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ nonoptlib=/usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ [ -e /usr/lib/x86_64-linux-gnu/libsmartcols.so.1 ]
+ x=/usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ copy_file binary /usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ local type src target link_target
+ type=binary
+ src=/usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ target=/usr/lib/x86_64-linux-gnu/libsmartcols.so.1
+ [ -f /usr/lib/x86_64-linux-gnu/libsmartcols.so.1 ]
+ [ -d /var/tmp/mkinitramfs_eGzSvp//usr/lib/x86_64-linux-gnu/libsmartcols.so.1 ]
+ [ -e
