Bug#984529: marked as done (rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1))
Your message dated Thu, 11 Mar 2021 03:33:34 + with message-id and subject line Bug#984529: fixed in rheolef 7.1-4 has caused the Debian Bug report #984529, regarding rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1) 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.) -- 984529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rheolef Version: 7.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../51-rheolef_7.1-3_amd64.deb ... Unpacking rheolef (7.1-3) over (7.0-2+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-qDgNC1/51-rheolef_7.1-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/rheolef-config', which is also in package librheolef-dev 7.0-2+b1 Preparing to unpack .../52-librheolef-dev_7.1-3_amd64.deb ... Unpacking librheolef-dev (7.1-3) over (7.0-2+b1) ... cheers, Andreas rheolef_7.1-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: rheolef Source-Version: 7.1-4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of rheolef, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated rheolef 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: Wed, 10 Mar 2021 21:45:18 -0500 Source: rheolef Architecture: source Version: 7.1-4 Distribution: unstable Urgency: high Maintainer: Debian Science Maintainers Changed-By: Boyuan Yang Closes: 984529 Changes: rheolef (7.1-4) unstable; urgency=high . * Team upload. * debian/control: Bump Breaks+Replaces relationship between package rheolef and librheolef-dev from (<< 6.1) to (<< 7.1-4~). (Closes: #984529) * debian/changelog: Remove trailing spaces. Checksums-Sha1: e3b6c3aa09c477b9803eb250f104e41f98e8c129 2579 rheolef_7.1-4.dsc 8904839c211d2a2809061f71dc7f3d456fe18d8b 35928350 rheolef_7.1.orig.tar.gz de3bca026fb1d456303414b505e110d92d55cf12 11376 rheolef_7.1-4.debian.tar.xz c9ad573e850a39ea8e437721a519bd7d20f39b97 20146 rheolef_7.1-4_amd64.buildinfo Checksums-Sha256: e6479a4dd1680d300ef0e2b4507429b1abc77ce6c08dac4859e602071f751faf 2579 rheolef_7.1-4.dsc c9a069b9dcda583d9577a545fba3c413723cb9bd76dfafd585237795ddb1737e 35928350 rheolef_7.1.orig.tar.gz e444b1a9f2b77852d6ac1b1784346514665e9f22bc70c7c4bfb0d7175f61e1cd 11376 rheolef_7.1-4.debian.tar.xz 1ba0ec40b3c763899d8cc745a45e60b735c14b3e43af8b29fc7c46e57400643d 20146 rheolef_7.1-4_amd64.buildinfo Files: d1302a284c2b72aacfba34e0e9cf81a5 2579 math optional rheolef_7.1-4.dsc da1cc82910d98ffd73a04d189af4383d 35928350 math optional rheolef_7.1.orig.tar.gz 26aa4cca0d3ec97618cff4b6f62a7230 11376 math optional rheolef_7.1-4.debian.tar.xz 0c6092f2da7ebe1a9230bfa144b9bfb4 20146 math optional rheolef_7.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmBJipUACgkQwpPntGGC Ws7gpBAAvsPDqNutqQuwOej2FAO7bPWqgOBn/Thv/FNobAIVtkKa2aUYtkLVHIPO FFukAKFLvxkMFfuZ4KrL6S9PYKdrln75u7FqrFGHK7kDtfYBfq/hFAIRxK91W+j3 xAAKdlPkQ2UrX/UdlBvBzDW+GParBwXC2wA+K/HoT2vNKkTHrCHzkSyOkZHn/vmO VVLnDrljXL46SvMV5I8noj3C1+qhRVt3Kb2aYfsPz/lMLpKMjjDcMKGE/Ea8rTwa fGQ7Pksml4V50VXLXODEqKdyI2npfFzrercMD+wQHABctb8tG1oDVFZ9VhHxegea m9WZqd+80uOebxPqtPUb+Bqm19vyri7xfPPKMgtrSU1iQoDHbwOGENBB/6Z4JKLO XXJIMkNb7bDgbdEPFpZUeqNkXIpgWMjQBZxFAWNa5QlNYmeDFMKj+xDlG6iFzhOj HDF7lxO0jHywJK9dghaUNs9HcU5LzUeooM8yI8LKQIftZlBVxSAMUmHH7TDkWhxl 4sILVcBJ1a5HSbVNz6qQBZ3ROyo3PfIUEPaQ6qo3H3Xl3d8vmbhLcC9NdAC1K50S
Bug#984529: rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1)
X-Debbugs-CC: pierre.saram...@imag.fr debian-scie...@lists.debian.org 在 2021-03-08星期一的 10:10 -0500，Boyuan Yang写道： > X-Debbugs-CC: pierre.saram...@imag.fr debian-scie...@lists.debian.org > > On Thu, 04 Mar 2021 18:31:28 +0100 Andreas Beckmann > wrote: > > Package: rheolef > > Version: 7.1-3 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > > > during a test with piuparts I noticed your package fails to upgrade > from > > 'buster'. > > It installed fine in 'buster', then the upgrade to 'bullseye' fails > > because it tries to overwrite other packages files without > > declaring > a > > Breaks+Replaces relation. > > > > See policy 7.6 at > > > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > > > From the attached log (scroll to the bottom...): > > > > Preparing to unpack .../51-rheolef_7.1-3_amd64.deb ... > > Unpacking rheolef (7.1-3) over (7.0-2+b1) ... > > dpkg: error processing archive /tmp/apt-dpkg-install-qDgNC1/51- > rheolef_7.1-3_amd64.deb (--unpack): > > trying to overwrite '/usr/bin/rheolef-config', which is also in > package librheolef-dev 7.0-2+b1 > > Preparing to unpack .../52-librheolef-dev_7.1-3_amd64.deb ... > > Unpacking librheolef-dev (7.1-3) over (7.0-2+b1) ... > > I believe the problem is more than just that. Actually > /usr/bin/rheolef-config is intended for library build config. As a > result, it is supposed to be installed in librheolef-dev instead of > package rheolef. > > The move of /usr/bin/rheolef-config took place in 7.1-1. Pierre, can > you confirm this change? That being said, I will make a team upload with minimal changes first and request an unblock. Probably the placement of /usr/bin/rheolef- config can be settled in a separate bug report. Thanks, Boyuan Yang
Processed: user debian...@lists.debian.org, affects 982332, found 984931 in 1:2.30.2-1, usertagging 973885
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > affects 982332 + dahdi dahdi-linux Bug #982332 [dahdi-dkms] dahdi-dkms: fails to build module for Linux 5.10 Added indication that 982332 affects dahdi and dahdi-linux > found 984931 1:2.30.2-1 Bug #984931 [git-el,elpa-magit] git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7. There is no source info for the package 'elpa-magit' at version '1:2.30.2-1' with architecture '' Marked as found in versions git/1:2.30.2-1. > usertags 973885 piuparts Usertags were: broken-symlink adequate. Usertags are now: broken-symlink piuparts adequate. > thanks Stopping processing here. Please contact me if you need assistance. -- 973885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973885 982332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982332 984931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984962: openmpi-bin: broken symlink: /usr/bin/mpijavac -> mpijavac.pl
Package: openmpi-bin Version: 4.1.0-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m17.9s ERROR: FAIL: Broken symlinks: /usr/bin/mpijavac -> mpijavac.pl (openmpi-bin) cheers, Andreas openmpi-bin_4.1.0-7.log.gz Description: application/gzip
Bug#945506: Processed: dkms: export CC pointing to the kernels compiler
On 10/03/2021 14.14, Benjamin Kaduk wrote: Thanks for filing 984929. Do you have a sense for what the cutoff should be for trying to get 984929 resolved vs. just uploading a workaround in the dkms-consuming packages (e.g., openafs)? I do not have a good workarounnd for the affected packages. The "add Depends: gcc" suggestion is a rather bad hack (that does the right thing only in some cases), especially after I found this rather easy (but Debian specific) solution in dkms. The patch is probably not suitable for upstream inclusion, as the .kernelvariables file seems to be Debian specific. But a more general solution getting the CC value from Kbuild might be a useful upstream addition. Andreas
Bug#984730: marked as done (rust-sequoia-autocrypt: autopkgtest needs update for new version of rust-sequoia-openpgp: output changed)
Your message dated Wed, 10 Mar 2021 23:17:02 +
with message-id <11a93d7a-3209-08a5-f443-58dc980cf...@p10link.net>
and subject line re: rust-sequoia-autocrypt: autopkgtest needs update for new
version of rust-sequoia-openpgp: output changed
has caused the Debian Bug report #984730,
regarding rust-sequoia-autocrypt: autopkgtest needs update for new version of
rust-sequoia-openpgp: output changed
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.)
--
984730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sequoia-autocrypt
Version: 0.23.0-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:rust-sequoia-openpgp
[X-Debbugs-CC: debian...@lists.debian.org,
rust-sequoia-open...@packages.debian.org]
Dear maintainer(s),
With a recent upload of rust-sequoia-openpgp the autopkgtest of
rust-sequoia-autocrypt fails in testing when that autopkgtest is run
with the binary packages of rust-sequoia-openpgp from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
rust-sequoia-openpgp from testing1.1.0-1
rust-sequoia-autocrypt from testing0.23.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of
rust-sequoia-openpgp to testing [1]. Of course, rust-sequoia-openpgp
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in rust-sequoia-openpgp was intended and
your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from rust-sequoia-openpgp
should really add a versioned Breaks on the unfixed version of (one of
your) package(s). Note: the Breaks is nice even if the issue is only in
the autopkgtest as it helps the migration software to figure out the
right versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=rust-sequoia-openpgp
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-sequoia-autocrypt/10911145/log.gz
failures:
test::autocrypt_header_new stdout
thread 'test::autocrypt_header_new' panicked at 'assertion failed:
`(left == right)`
left: `"3E8877C877274692975189F5D03F6F865226FE8B"`,
right: `"3E88 77C8 7727 4692 9751 89F5 D03F 6F86 5226 FE8B"`',
src/lib.rs:1058:9
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.48.0/library/std/src/panicking.rs:483
1: std::panicking::begin_panic_fmt
at /usr/src/rustc-1.48.0/library/std/src/panicking.rs:437
2: sequoia_autocrypt::test::autocrypt_header_new
at ./src/lib.rs:1058
3: sequoia_autocrypt::test::autocrypt_header_new::{{closure}}
at ./src/lib.rs:1034
4: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.48.0/library/core/src/ops/function.rs:227
5: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.48.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
failures:
test::autocrypt_header_new
test result: FAILED. 6 passed; 1 failed; 0 ignored; 0 measured; 0
filtered out
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.23.1-1
Tests for the new version of rust-sequoia-autocrypt pass with both the new and
old versions of
rust-sequoia-openpgp.--- End Message ---
Bug#984953: libgtkmm-3.0-1v5: GParted crashes on Gdk::Pixbuf::get_width() const ()
Package: libgtkmm-3.0-1v5 Version: 3.24.2-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: moonwal...@syrius.us Dear Maintainer, I attempted to launch GParted and saw it crash immediately after initially showing its window I attempted to delete all /root/.gtkrc*, /root/.config/gtkrc*, and /root/.config/gtk-3.0/settings.ini files, as I had configured Breeze as GTK theme and I thought maybe that has something to do with the crash since console does spam theme-related warning messages. That did visibly reset the GTK theme for GParted, but the crash was still there. I'm also attaching the core dump from the run before my attempt to reset GTK theme. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Foreign Architectures: i386 Kernel: Linux 5.8.5-0.40-1-pinebookpro-hwaccel (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgtkmm-3.0-1v5 depends on: ii libatkmm-1.6-1v5 2.28.0-3 ii libc62.31-9 ii libcairomm-1.0-1v5 1.12.2-4 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.7-1 ii libglibmm-2.4-1v52.64.2-2 ii libgtk-3-0 3.24.24-3 ii libpangomm-1.4-1v5 2.42.1-1 ii libsigc++-2.0-0v52.10.4-2 ii libstdc++6 10.2.1-6 libgtkmm-3.0-1v5 recommends no packages. libgtkmm-3.0-1v5 suggests no packages. -- no debconf information
Bug#983365: (no subject)
Hi Dennis, I did respond to your email on the 7th. Maybe it wound up in your spam folder? At any rate, apologies for the delay - things have been a bit busy the past several days. I'm currently building/testing the data type patch, and hope to upload it to unstable today. I'll file the unblock request once that's done. Since we're in the freeze, I'm going to hold off on applying the test regen patch for now, but I'll add it eventually. Best regards, Bill
Processed: wrong binary package
Processing commands for cont...@bugs.debian.org: > reassign 982857 imagemagick-6-doc Bug #982857 [imagemagick-6-common] All pages cut off due to IFRAME closing tag bungle Bug reassigned from package 'imagemagick-6-common' to 'imagemagick-6-doc'. No longer marked as found in versions imagemagick/8:6.9.11.60+dfsg-1. Ignoring request to alter fixed versions of bug #982857 to the same values previously set > retitle 982857 imagemagick-6-doc mostly useless when pages are viewed in > browser due to invalid closure of iframe Bug #982857 [imagemagick-6-doc] All pages cut off due to IFRAME closing tag bungle Changed Bug title to 'imagemagick-6-doc mostly useless when pages are viewed in browser due to invalid closure of iframe' from 'All pages cut off due to IFRAME closing tag bungle'. > severity 982857 important Bug #982857 [imagemagick-6-doc] imagemagick-6-doc mostly useless when pages are viewed in browser due to invalid closure of iframe Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 982857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984534: marked as done ([PATCH] Missing type conversion hints in libsoci_sqlite3-4.0 lead to std::bad_cast exceptions in Linphone)
Your message dated Wed, 10 Mar 2021 19:23:57 + with message-id and subject line Bug#984534: fixed in soci 4.0.1-5 has caused the Debian Bug report #984534, regarding [PATCH] Missing type conversion hints in libsoci_sqlite3-4.0 lead to std::bad_cast exceptions in Linphone 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.) -- 984534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: soci Architecture: amd64 Version: 4.0.1-4 Severity: grave Justification: Breaks linphone Affects: linphone Tags: patch upstream sid bullseye The sqlite3 backend uses a hard-coded map of column data type names in src/backends/sqlite3/statement.cpp as hints to convert any results sqlite3 dynamically retyped to text to whatever the caller asked for. Linphone uses a database schema with MySQL-specific type names that are not in this map and thus suffers random std::bad_cast exceptions which are at the heart of #983365 (see badcast.cpp for a reproducer). The first attached patch adds the missing entries to the map which fixes the issue. The optional second patch disables the regeneration of an unneeded config file to satisfy dpkg-source during repeated builds. Regards, Dennis. badcast.cpp.gz Description: application/gzip 02-add-mysql-ddl-types.patch.gz Description: application/gzip 03-disable-test-access-regen.patch.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: soci Source-Version: 4.0.1-5 Done: William Blough We believe that the bug you reported is fixed in the latest version of soci, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Blough (supplier of updated soci 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: Wed, 10 Mar 2021 12:46:31 -0500 Source: soci Architecture: source Version: 4.0.1-5 Distribution: unstable Urgency: medium Maintainer: William Blough Changed-By: William Blough Closes: 984534 Changes: soci (4.0.1-5) unstable; urgency=medium . * Add unsigned type hints to sqlite backend. Closes: 984534 Checksums-Sha1: 350fd41da004baa7a241ed6219f0cbca096c2ff6 2638 soci_4.0.1-5.dsc 56595f0aaa37ac09bcf7154ccdba95b80ba52b10 85484 soci_4.0.1-5.debian.tar.xz f4d7fef1479261d7dca571b471963ba0d067520a 11398 soci_4.0.1-5_amd64.buildinfo Checksums-Sha256: 11076f5d4ef1f549c4731d3b318ec043419b0ebb56451b66fce1c3d2251374bb 2638 soci_4.0.1-5.dsc 0a05c94b4595daf47eff316e1373648fd577fa8174f022d1a527932700c82946 85484 soci_4.0.1-5.debian.tar.xz adf294043f554b61acbb2cc522081bf8dff6e33541b39d752f8a9b320516a798 11398 soci_4.0.1-5_amd64.buildinfo Files: 8827512d8dd94c796c99ebae96afd897 2638 libs optional soci_4.0.1-5.dsc c42a4e962e4d8df6e556d7d9567397b8 85484 libs optional soci_4.0.1-5.debian.tar.xz 50c25c6a5a1419b1222c6037681c2c50 11398 libs optional soci_4.0.1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCACRFiEEJXjSPd76bZ5rVv2gNeEe5JHS9UwFAmBJFrBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDI1 NzhEMjNEREVGQTZEOUU2QjU2RkRBMDM1RTExRUU0OTFEMkY1NEMTHGJibG91Z2hA ZGViaWFuLm9yZwAKCRA14R7kkdL1TPHVD/9pFF+Ct5Oyyq0B99yGWoOi55nBaZ24 aMzHnimf1T2/ITHyKNITEEnquvL4h7iW5DyrSux3lLczD5nZwYRXVgwyptXzdmTf czhGVSta3rSzsLlhHtaZ0Z1/q2GjydW5itOYErOnXV/8bGKA82yEfJ7aqQUZl8AC jfHMpEA2PcpjxMZy3b3bphEQuliSZT1MhfvfpxzpEgCRiwaZM3czClaDR97H9EQ3 6+3rBo+svv0xZyzpzRry+OKXraWzMToVHV/1vxEem35i5+yBazTXlYgdyCUbIDtr t2dk7OnqCiWjjLYHE26ijFhW+fURFusWXoGtRMSn6IZgwx2Rzo4FMjKscXoR44J9 q0iSU9aZ9+VBeZ1TGILN2yicFtFUJ/VRa+HG0XXrqfitU2auUjTWZej2rdR9xLKQ e3dzJ9mH6soY5wPWwtdR+jwoAUXVOKZ5kXdiVUb+7kGydxWoZb22zULEzeyvN2zI LCPe8wHysvOIINc97o/FeNe2/ojOQ7VN2dCApPEGsCJhkVOIjnwu1gJgDAI2qwKf EU1abQFcTEt7aNRm03m//N/0wCf6bBdFOtWRRCfjwcQtvo34Kg7IN4Pe/NRJiBxL YKi3Z2sWPu8dCP+s3+X86tRRl5m5/gRbFlHi2qbxsw1yeLHYeNjEn9ZhhfhUgA1P JZMLtRAijJOq3w== =ZRLR -END PGP SIGNATURE End Message ---
Bug#984939: marked as done (python-netaddr-docs: Many topics are empty)
Your message dated Wed, 10 Mar 2021 18:48:32 + with message-id and subject line Bug#984939: fixed in python-netaddr 0.7.19-5 has caused the Debian Bug report #984939, regarding python-netaddr-docs: Many topics are empty 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.) -- 984939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-netaddr-docs Version: 0.7.19-4 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I wanted to read the documentation for the python-netaddr and python3-netaddr packages. * What exactly did you do (or not do) that was effective (or ineffective)? I opened the HTML files in /usr/share/doc/python-netaddr-docs, expecting to read the documentation for the python-netaddr package. * What was the outcome of this action? The HTML files are there, but the following chapters/topics are empty of text, and therefore unusable as documentation: * Installing netaddr * Tutorial 1: IP Addresses, Subnets and Ranges * Tutorial 2: MAC addresses * Tutorial 3: Working with IP sets * Contributors Only the "API Reference" topic/chapter has useful documentation, but a dry reference is not always very helpful. * What outcome did you expect instead? I expected the above-mentioned files to contain equivalent documentation as seen on these corresponding web pages: https://netaddr.readthedocs.io/en/latest/installation.html https://netaddr.readthedocs.io/en/latest/tutorial_01.html https://netaddr.readthedocs.io/en/latest/tutorial_02.html https://netaddr.readthedocs.io/en/latest/tutorial_03.html https://netaddr.readthedocs.io/en/latest/contributors.html *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:C:en:en_GB:sv_SE:sv_FI (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-netaddr-docs depends on: ii libjs-sphinxdoc 1.8.4-1 python-netaddr-docs recommends no packages. python-netaddr-docs suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-netaddr Source-Version: 0.7.19-5 Done: Vincent Bernat We believe that the bug you reported is fixed in the latest version of python-netaddr, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Bernat (supplier of updated python-netaddr 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: Wed, 10 Mar 2021 19:35:08 +0100 Source: python-netaddr Architecture: source Version: 0.7.19-5 Distribution: unstable Urgency: medium Maintainer: Vincent Bernat Changed-By: Vincent Bernat Closes: 984939 Changes: python-netaddr (0.7.19-5) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address . [ Vincent Bernat ] * d/rules: do not build documentation (Closes: #984939) Checksums-Sha1: b60c1de25de254c8e5309d74e136ccbb93d58775 2111 python-netaddr_0.7.19-5.dsc 00e0ce7d7ebc1d6e7943e884aa51ccb7becdc9ea 1622835 python-netaddr_0.7.19.orig.tar.gz 6aa0c865739a1eb9ba41a85f13ebd74b5443f1b6 6168 python-netaddr_0.7.19-5.debian.tar.xz 52054a1165db9da9e41fbb70306e818b8f6e9c2d 7552 python-netaddr_0.7.19-5_amd64.buildinfo Checksums-Sha256: 6e351b9a6aef9986aa315045383d9e600e49a72905cb0d5a48bf20c3cf36e23e 2111 python-netaddr_0.7.19-5.dsc 38aeec7cdd035081d3a4c306394b19d677623bf76fa0913f6695127c7753aefd 1622835
Bug#984939: marked as pending in python-netaddr
Control: tag -1 pending Hello, Bug #984939 in python-netaddr 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/python-netaddr/-/commit/49d864914fc7f3796cfff07dc21beabd0b391dbd d/rules: do not build documentation The package downloaded from Pypi does not contain all the files to generate the documentation. Let's just not build it. Closes: #984939 (this message was generated automatically) -- Greetings https://bugs.debian.org/984939
Processed: Bug#984939 marked as pending in python-netaddr
Processing control commands: > tag -1 pending Bug #984939 [python-netaddr-docs] python-netaddr-docs: Many topics are empty Added tag(s) pending. -- 984939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ruby-rails-html-sanitizer: FTBFS: ERROR: Test "ruby2.7" failed.
Processing control commands: > tags -1 bullseye-ignore Bug #982723 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: FTBFS: ERROR: Test "ruby2.7" failed. Added tag(s) bullseye-ignore. -- 982723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982723: ruby-rails-html-sanitizer: FTBFS: ERROR: Test "ruby2.7" failed.
Control: tags -1 bullseye-ignore Hi, On Sat, 13 Feb 2021 18:10:03 +0100 Lucas Nussbaum > During a rebuild of all packages in sid, your package failed to build > on amd64. This is due to a new version of ruby-loofah which isn't migrating because it breaks the autopkgtest. So, this bug can be ignored for bullseye assuming no other issues pop up with ruby-rails-html-sanitizer. ruby-rails-html-sanitizer and ruby-loofah are key packages so can't be easily removed. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: sks: autopkgtest failure since git snapshot update
Processing control commands: > severity -1 serious Bug #975711 [sks] The autopkgtests since the git snapshot update Severity set to 'serious' from 'normal' > retitle -1 sks: autopkgtest failure since git snapshot update Bug #975711 [sks] The autopkgtests since the git snapshot update Changed Bug title to 'sks: autopkgtest failure since git snapshot update' from 'The autopkgtests since the git snapshot update'. -- 975711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969938: debirf: bullseye: switch from /updates to -security
user debian-rele...@lists.debian.org
usertags -1 + bsp-2021-03-latinoamerica
tags -1 + pending,patch
thank you
I have included the following patch and pushed to the Git repository
(but not made an upload):
diff --git a/debian/changelog b/debian/changelog
index 25f22f6..9872f94 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,11 @@
debirf (0.39) UNRELEASED; urgency=medium
+ [ Ondřej Nový ]
* d/copyright: Use https protocol in Format field
+ [ Gunnar Wolf ]
+ * switch from /updates to -security (Closes: #969938)
+
-- Ondřej Nový Mon, 01 Oct 2018 10:36:19 +0200
debirf (0.38) unstable; urgency=medium
diff --git a/src/modules/a0_add_security_repos
b/src/modules/a0_add_security_repos
index a4ab2be..7c0341d 100755
--- a/src/modules/a0_add_security_repos
+++ b/src/modules/a0_add_security_repos
@@ -22,7 +22,7 @@ case "${DEBIRF_DISTRO}" in
;;
*)
cat <
"${DEBIRF_ROOT}/etc/apt/sources.list.d/security_repos.list"
-deb http://security.debian.org/ ${DEBIRF_SUITE}/updates main contrib non-free
+deb http://security.debian.org/ ${DEBIRF_SUITE}-security main contrib non-free
EOF
;;
esac
This package has currently three RC bugs. I'll see if I can make
progress on any other of them, and if so, will upload to a delayed
queue (otherwise, I'm just tagging as patch+pending).
signature.asc
Description: PGP signature
Bug#904627: (no subject)
user debian-rele...@lists.debian.org usertags -1 + bsp-2021-03-latinoamerica thank you
Bug#983917: marked as done (gnome-weather: Fails to get forecast data)
Your message dated Wed, 10 Mar 2021 17:48:27 + with message-id and subject line Bug#983917: fixed in libgweather 3.36.1-2 has caused the Debian Bug report #983917, regarding gnome-weather: Fails to get forecast data 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.) -- 983917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-weather Version: 3.36.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, Gnome Weather fails to get forecast data. After entering a location the app shows the message: "Forecast data not available" This happens with every location tried: New York, New York, United States of America; London, Greater London, United Kingdom; and others. This is the terminal output: ``` $ gnome-weather GWeather-Message: 11:51:16.849: Failed to get Yr.no forecast data: 404 Not Found GWeather-Message: 11:51:16.862: Failed to get Yr.no forecast data: 404 Not Found ``` -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-weather depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii geoclue-2.0 2.5.7-2 ii gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 ii gir1.2-geoclue-2.0 2.5.7-2 ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gnomedesktop-3.0 3.38.4-1 ii gir1.2-gtk-3.0 3.24.24-3 ii gir1.2-gweather-3.0 3.36.1-1 ii gjs 1.66.2-1 ii libglib2.0-bin 2.66.7-1 gnome-weather recommends no packages. gnome-weather suggests no packages. --- End Message --- --- Begin Message --- Source: libgweather Source-Version: 3.36.1-2 Done: Iain Lane We believe that the bug you reported is fixed in the latest version of libgweather, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iain Lane (supplier of updated libgweather 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: Wed, 10 Mar 2021 17:26:48 + Source: libgweather Architecture: source Version: 3.36.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Iain Lane Closes: 983917 Changes: libgweather (3.36.1-2) unstable; urgency=medium . [ Andreas Henriksson ] * Add patches from upstream for yr.no->met.no API. These patches has been cherry-picked from upstream and modified to apply directly to the yrno backend (without renaming it to metno and breaking the API). (Closes: #983917) . [ Laurent Bigonville ] * Only use 4 significant decimals for locations when sending the query. Patch from upstream. More precision is not needed and this helps to improve caching on the provider side and reduce their load. Checksums-Sha1: ad5473787128445d4d5e452a48d0925b8ae8ab43 2682 libgweather_3.36.1-2.dsc 0393d559ee95e25dce9a34ebd2a7c7ccb0e4e341 13340 libgweather_3.36.1-2.debian.tar.xz 79ce92dd287fd83234aca9ed40b21c28995c1663 21307 libgweather_3.36.1-2_source.buildinfo Checksums-Sha256: a3fb06e4739ca90ceeea36f0155e1f05607b3aa6b6ae8b0e498e230cb22f66f3 2682 libgweather_3.36.1-2.dsc 84afb861a05461de7d6bdc9fb8a2d42a37ad29297dd05644de1da3d0e15fb897 13340 libgweather_3.36.1-2.debian.tar.xz f9125bfd23fc0c049f81630908667b032c9a82c5fc906126df959de54cbe0351 21307 libgweather_3.36.1-2_source.buildinfo Files: 767e8fa96d272de35c21efa9186760cc 2682 libs optional libgweather_3.36.1-2.dsc 6067f9b47b9004128a2f8c7bbba381b8 13340 libs optional
Bug#956083: autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups
user debian-rele...@lists.debian.org usertags -1 + bsp-2021-03-latinoamerica thank you
Bug#956083: autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups
tags 956083 + patch,pending
thanks
Hello Tina!
I have prepared a _very_ simple patch for this issue that lacks
elegance, but I think solves the problem: As it is invoked before the
data rotation, it will notify via stderr and exit before destroying
past data:
diff --git a/autopostgresqlbackup b/autopostgresqlbackup
index 19f2264..2b9eb14 100755
--- a/autopostgresqlbackup
+++ b/autopostgresqlbackup
@@ -367,6 +367,14 @@ dbdump () {
pg_dump --username=$USERNAME $PGHOST $OPT $db >> $2
fi
fi
+ # Was the dump successful? We can only guess based on the
+ # return status of the command.
+ if [ $? != 0 ]
+ then
+ echo "Errors reported by dump process! (return code: $?)" >&2
+ echo $@ >&2
+ exit 1
+ fi
done
return 0
}
I will now proceed to build the package and upload to the 5-day
delayed queue.
FWIW, this is part of the LatinAmerica 2021.03 BSP ;-)
https://wiki.debian.org/BSP/2021/03/LatinAmerica
signature.asc
Description: PGP signature
Processed: Re: autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups
Processing commands for cont...@bugs.debian.org: > tags 956083 + patch,pending Bug #956083 [autopostgresqlbackup] autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups Added tag(s) patch and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984939: python-netaddr-docs: Many topics are empty
Package: python-netaddr-docs Version: 0.7.19-4 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I wanted to read the documentation for the python-netaddr and python3-netaddr packages. * What exactly did you do (or not do) that was effective (or ineffective)? I opened the HTML files in /usr/share/doc/python-netaddr-docs, expecting to read the documentation for the python-netaddr package. * What was the outcome of this action? The HTML files are there, but the following chapters/topics are empty of text, and therefore unusable as documentation: * Installing netaddr * Tutorial 1: IP Addresses, Subnets and Ranges * Tutorial 2: MAC addresses * Tutorial 3: Working with IP sets * Contributors Only the "API Reference" topic/chapter has useful documentation, but a dry reference is not always very helpful. * What outcome did you expect instead? I expected the above-mentioned files to contain equivalent documentation as seen on these corresponding web pages: https://netaddr.readthedocs.io/en/latest/installation.html https://netaddr.readthedocs.io/en/latest/tutorial_01.html https://netaddr.readthedocs.io/en/latest/tutorial_02.html https://netaddr.readthedocs.io/en/latest/tutorial_03.html https://netaddr.readthedocs.io/en/latest/contributors.html *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:C:en:en_GB:sv_SE:sv_FI (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-netaddr-docs depends on: ii libjs-sphinxdoc 1.8.4-1 python-netaddr-docs recommends no packages. python-netaddr-docs suggests no packages. -- no debconf information
Processed: severity of 983395 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 983395 wishlist Bug #983395 [src:libpod] Please print nicer error message if newuidmap is not Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 983395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983395: podman lacks a runtime dependency on rootlesskit
Control: retitle -1 Please print nicer error message if newuidmap is not installed Control: severity -1 wishlist Control: tag -1 upstream Andrey, please stop this bug ping-pong. Feel free to escalate this to the TC, but I don't think you are being reasonable here. -- regards, Reinhard
Processed: Re: Bug#983395: podman lacks a runtime dependency on rootlesskit
Processing control commands: > retitle -1 Please print nicer error message if newuidmap is not Bug #983395 [src:libpod] podman requires uidmap, promote from Recommends to Depends Changed Bug title to 'Please print nicer error message if newuidmap is not' from 'podman requires uidmap, promote from Recommends to Depends'. -- 983395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#983395: podman lacks a runtime dependency on rootlesskit
Processing control commands: > severity -1 serious Bug #983395 [src:libpod] Please print nicer error message if newuidmap is not Severity set to 'serious' from 'important' > retitle -1 podman requires uidmap, promote from Recommends to Depends Bug #983395 [src:libpod] Please print nicer error message if newuidmap is not Changed Bug title to 'podman requires uidmap, promote from Recommends to Depends' from 'Please print nicer error message if newuidmap is not'. -- 983395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959022: cgroup-tools: does not work in cgroup2 / unified hierarchy
On Tue, 28 Apr 2020 15:22:35 +0900 Ryutaroh Matsumoto wrote: > Package: cgroup-tools > Version: 0.41-10 > Severity: normal > Tags: wontfix > User: pkg-systemd-maintain...@lists.alioth.debian.org > Usertags: cgroupv2 > > Dear Maintainer, > > It does not work in the cgroup2 / unified hierarchy. It gives > > # lssubsys > # lscgroup > cgroups can't be listed: Cgroup is not mounted > > Best regards, Ryutaroh Matsumoto Hi there, In this other upstream repo, there is some progress relating cgroupv2-support: https://github.com/libcgroup/libcgroup i.e.: https://github.com/libcgroup/libcgroup/issues/12 On my Debian sid machine, I can run these simple tests from compile source (commit 6f387cbc5f4fb8d43371a317356648d1c561efda): sudo ./src/tools/cgcreate -g io:a/b/c/d sudo ./src/tools/cgget -g io:a/b/c/d a/b/c/d: io.pressure: some avg10=0.00 avg60=0.00 avg300=0.00 total=0 full avg10=0.00 avg60=0.00 avg300=0.00 total=0 io.max: io.weight: default 100 io.stat: sudo ./src/tools/lscgroup cpuset,cpu,io,memory,hugetlb,pids,rdma:/ cpuset,cpu,io,memory,hugetlb,pids,rdma:/sys-fs-fuse-connections.mount cpuset,cpu,io,memory,hugetlb,pids,rdma:/sys-kernel-config.mount cpuset,cpu,io,memory,hugetlb,pids,rdma:/sys-kernel-debug.mount cpuset,cpu,io,memory,hugetlb,pids,rdma:/a ... As of today, there are 9 of 12 applications supporting cgroup2. I'll take a look if I could package it. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#983686: libcaca: CVE-2021-3410
Control: tags -1 + patch
Hi,
On Sun, Feb 28, 2021 at 01:54:37PM +0100, Salvatore Bonaccorso wrote:
> Source: libcaca
> Version: 0.99.beta19-2.1
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/cacalabs/libcaca/issues/52
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The following vulnerability was published for libcaca.
>
> CVE-2021-3410[0]:
> | A flaw was found in libcaca v0.99.beta19. A buffer overflow issue in
> | caca_resize function in libcaca/caca/canvas.c may lead to local
> | execution of arbitrary code in the user context.
>
>
> 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-2021-3410
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3410
> [1] https://github.com/cacalabs/libcaca/issues/52
Attached is debdiff prepared (not yet uploaded).
Regards,
Salvatore
diff -Nru libcaca-0.99.beta19/debian/changelog
libcaca-0.99.beta19/debian/changelog
--- libcaca-0.99.beta19/debian/changelog2019-04-06 22:18:41.0
+0200
+++ libcaca-0.99.beta19/debian/changelog2021-03-10 14:59:27.0
+0100
@@ -1,3 +1,14 @@
+libcaca (0.99.beta19-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Illegal write memory access in caca_resize function (CVE-2021-3410)
+- canvas: fix an integer overflow in caca_resize().
+- Fix a problem in the caca_resize() overflow detection and add
+ several unit tests
+(Closes: #983686)
+
+ -- Salvatore Bonaccorso Wed, 10 Mar 2021 14:59:27 +0100
+
libcaca (0.99.beta19-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru
libcaca-0.99.beta19/debian/patches/Fix-a-problem-in-the-caca_resize-overflow-detection-.patch
libcaca-0.99.beta19/debian/patches/Fix-a-problem-in-the-caca_resize-overflow-detection-.patch
---
libcaca-0.99.beta19/debian/patches/Fix-a-problem-in-the-caca_resize-overflow-detection-.patch
1970-01-01 01:00:00.0 +0100
+++
libcaca-0.99.beta19/debian/patches/Fix-a-problem-in-the-caca_resize-overflow-detection-.patch
2021-03-10 14:59:27.0 +0100
@@ -0,0 +1,135 @@
+From: Sam Hocevar
+Date: Fri, 26 Feb 2021 12:40:06 +0100
+Subject: [2/2] Fix a problem in the caca_resize() overflow detection and add
+ several unit tests.
+Origin:
https://github.com/cacalabs/libcaca/commit/e4968ba6e93e9fd35429eb16895c785c51072015
+Bug: https://github.com/cacalabs/libcaca/issues/52
+Bug-Debian: https://bugs.debian.org/983686
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2021-3410
+
+---
+ caca/canvas.c | 16
+ test/canvas.cpp | 18 +++---
+ tools/makefont.c | 22 +++---
+ 3 files changed, 42 insertions(+), 14 deletions(-)
+
+--- a/caca/canvas.c
b/caca/canvas.c
+@@ -367,6 +367,14 @@ int caca_resize(caca_canvas_t *cv, int w
+ {
+ int x, y, f, old_width, old_height, old_size;
+
++/* Check for overflow */
++int new_size = width * height;
++if (new_size < 0 || (width > 0 && new_size / width != height))
++{
++seterrno(EOVERFLOW);
++return -1;
++}
++
+ old_width = cv->width;
+ old_height = cv->height;
+ old_size = old_width * old_height;
+@@ -377,14 +385,6 @@ int caca_resize(caca_canvas_t *cv, int w
+ * dirty rectangle handling */
+ cv->width = width;
+ cv->height = height;
+-int new_size = width * height;
+-
+-/* Check for overflow */
+-if (new_size / width != height)
+-{
+-seterrno(EOVERFLOW);
+-return -1;
+-}
+
+ /* If width or height is smaller (or both), we have the opportunity to
+ * reduce or even remove dirty rectangles */
+--- a/test/canvas.cpp
b/test/canvas.cpp
+@@ -16,6 +16,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include "caca.h"
+
+@@ -53,18 +54,29 @@ public:
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_width(cv), 0);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_height(cv), 0);
+
+-caca_set_canvas_size(cv, 1, 1);
++int ret = caca_set_canvas_size(cv, 1, 1);
++CPPUNIT_ASSERT_EQUAL(ret, 0);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_width(cv), 1);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_height(cv), 1);
+
+-caca_set_canvas_size(cv, 1234, 1001);
++ret = caca_set_canvas_size(cv, 1234, 1001);
++CPPUNIT_ASSERT_EQUAL(ret, 0);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_width(cv), 1234);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_height(cv), 1001);
+
+-caca_set_canvas_size(cv, 0, 0);
++ret = caca_set_canvas_size(cv, 0, 0);
++CPPUNIT_ASSERT_EQUAL(ret, 0);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_width(cv), 0);
+ CPPUNIT_ASSERT_EQUAL(caca_get_canvas_height(cv), 0);
+
++CPPUNIT_ASSERT_EQUAL(-1, caca_set_canvas_size(cv, -1,
Processed: Re: Bug#983686: libcaca: CVE-2021-3410
Processing control commands: > tags -1 + patch Bug #983686 [src:libcaca] libcaca: CVE-2021-3410 Added tag(s) patch. -- 983686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977068: marked as done (indexed-gzip FTBFS with pytest 6)
Your message dated Wed, 10 Mar 2021 15:18:25 +
with message-id
and subject line Bug#977068: fixed in indexed-gzip 0.8.6-1.2
has caused the Debian Bug report #977068,
regarding indexed-gzip FTBFS with pytest 6
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.)
--
977068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: indexed-gzip
Version: 0.8.6-1.1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
indexed-gzip FTBFS with pytest 6 in experimental.
The error log below has more details.
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> python3 setup.py test --addopts '--niter 1'
> running pytest
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> creating indexed_gzip.egg-info
> writing indexed_gzip.egg-info/PKG-INFO
> writing dependency_links to indexed_gzip.egg-info/dependency_links.txt
> writing top-level names to indexed_gzip.egg-info/top_level.txt
> writing manifest file 'indexed_gzip.egg-info/SOURCES.txt'
> reading manifest file 'indexed_gzip.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'indexed_gzip.egg-info/SOURCES.txt'
> running build_ext
> building 'indexed_gzip.indexed_gzip' extension
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I./indexed_gzip -Iindexed_gzip
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.9
> -c indexed_gzip/indexed_gzip.c -o
> build/temp.linux-x86_64-3.9/indexed_gzip/indexed_gzip.o -Wall -pedantic
> -Wno-unused-function
> indexed_gzip/indexed_gzip.c:5002:119: warning: ISO C forbids conversion of
> function pointer to object pointer type [-Wpedantic]
> 5002 | static PyMethodDef
> __pyx_mdef_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_23__exit__ =
> {"__exit__",
> (PyCFunction)(void*)(PyCFunctionWithKeywords)__pyx_pw_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_23__exit__,
> METH_VARARGS|METH_KEYWORDS,
> __pyx_doc_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_22__exit__};
> |
> ^
> indexed_gzip/indexed_gzip.c:5002:106: warning: ISO C forbids conversion of
> object pointer to function pointer type [-Wpedantic]
> 5002 | static PyMethodDef
> __pyx_mdef_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_23__exit__ =
> {"__exit__",
> (PyCFunction)(void*)(PyCFunctionWithKeywords)__pyx_pw_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_23__exit__,
> METH_VARARGS|METH_KEYWORDS,
> __pyx_doc_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_22__exit__};
> |
>^
> indexed_gzip/indexed_gzip.c:5470:111: warning: ISO C forbids conversion of
> function pointer to object pointer type [-Wpedantic]
> 5470 | static PyMethodDef
> __pyx_mdef_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_29seek = {"seek",
> (PyCFunction)(void*)(PyCFunctionWithKeywords)__pyx_pw_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_29seek,
> METH_VARARGS|METH_KEYWORDS,
> __pyx_doc_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_28seek};
> |
> ^
> indexed_gzip/indexed_gzip.c:5470:98: warning: ISO C forbids conversion of
> object pointer to function pointer type [-Wpedantic]
> 5470 | static PyMethodDef
> __pyx_mdef_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_29seek = {"seek",
> (PyCFunction)(void*)(PyCFunctionWithKeywords)__pyx_pw_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_29seek,
> METH_VARARGS|METH_KEYWORDS,
> __pyx_doc_12indexed_gzip_12indexed_gzip_16_IndexedGzipFile_28seek};
> |
>^
> indexed_gzip/indexed_gzip.c:6133:111: warning: ISO C forbids conversion of
> function pointer to object pointer type [-Wpedantic]
> 6133 | static PyMethodDef
>
Bug#983775: libgrokj2k: Baseline violation on amd64/i386
Hello, I have created a patch for this bug: https://mentors.debian.net/package/libgrokj2k/ Thanks, Aaron On Mon, Mar 1, 2021 at 12:21 PM Adrian Bunk wrote: > Source: libgrokj2k > Version: 7.6.6-1 > Severity: serious > Tags: patch > > > https://buildd.debian.org/status/fetch.php?pkg=libgrokj2k=amd64=7.6.6-1=1612309672=0 > > ... > cd /<>/obj-x86_64-linux-gnu/src/lib/jp2 && /usr/bin/c++ > -DSPDLOG_COMPILED_LIB -Dgrokj2k_EXPORTS > -I/<>/obj-x86_64-linux-gnu/src/lib/jp2 > -I/<>/src/bin/common -I/<>/src/bin/jp2 > -I/<>/src/include -I/<>/src/lib/jp2 > -I/<>/src/lib/jp2/plugin > -I/<>/src/lib/jp2/transform -I/<>/src/lib/jp2/t1 > -I/<>/src/lib/jp2/t1/t1_part1 > -I/<>/src/lib/jp2/t1/t1_ht > -I/<>/src/lib/jp2/t1/t1_ht/coding > -I/<>/src/lib/jp2/t1/t1_ht/common > -I/<>/src/lib/jp2/t1/t1_ht/others > -I/<>/src/lib/jp2/util > -I/<>/src/lib/jp2/codestream > -I/<>/src/lib/jp2/codestream/markers > -I/<>/src/lib/jp2/point_transform > -I/<>/src/lib/jp2/t2 -I/<>/src/lib/jp2/tile > -I/<>/src/lib/jp2/filters -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2 > -fvisibility=hidden -mavx2 -mbmi2 -fPIC -Wall -Wextra -Wconversion > -Wsign-conversion -Wunused-parameter -std=c++2a -o > CMakeFiles/grokj2k.dir/util/GrkMappedFile.cpp.o -c > /<>/src/lib/jp2/util/GrkMappedFile.cpp > ... > > > "-mavx2 -mbmi2" is a violation of tha amd64 and i386 port baselines. > > Fix: > > --- debian/rules.old2021-03-01 17:09:49.253529618 + > +++ debian/rules2021-03-01 17:10:55.989543343 + > @@ -18,6 +18,7 @@ >-DBUILD_TESTING:BOOL=OFF \ >-DBUILD_DOC:BOOL=ON \ >-DBUILD_THIRDPARTY:BOOL=OFF \ > + -DAVX2_FOUND:BOOL=OFF \ >-DGRK_USE_LIBJPEG:BOOL=ON > > override_dh_auto_configure: >
Bug#983775: Patch
Hello, I have a patch for this bug on the mentors site: https://mentors.debian.net/package/libgrokj2k/ Thanks, Aaron
Bug#957070: marked as done (cde: ftbfs with GCC-10)
Your message dated Wed, 10 Mar 2021 14:20:34 +
with message-id
and subject line Bug#957070: fixed in cde 0.1+git9-g551e54d-1.2
has caused the Debian Bug report #957070,
regarding cde: ftbfs with GCC-10
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.)
--
957070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cde
Version: 0.1+git9-g551e54d-1.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/cde_0.1+git9-g551e54d-1.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
In function ‘CDE_load_environment_vars’,
inlined from ‘CDE_init’ at cde.c:3144:5:
cde.c:3648:9: warning: ‘%s’ directive argument is null [-Wformat-overflow=]
3648 | printf("ignored envvar '%s' => '%s'\n", name, val);
| ^~
mv -f .deps/cde.Tpo .deps/cde.Po
gcc -DHAVE_CONFIG_H -I. -I./linux/x86_64 -I./linux -I./linux -Wall
-Wwrite-strings -Wl,--hash-style=both -g -O2 -fno-stack-protector
-U_FORTIFY_SOURCE -D_GNU_SOURCE -MT okapi.o -MD -MP -MF .deps/okapi.Tpo -c -o
okapi.o okapi.c
mv -f .deps/okapi.Tpo .deps/okapi.Po
gcc -Wall -Wwrite-strings -Wl,--hash-style=both -g -O2 -fno-stack-protector
-U_FORTIFY_SOURCE -D_GNU_SOURCE-o strace strace.o syscall.o count.o util.o
desc.o file.o ipc.o io.o ioctl.o mem.o net.o process.o bjm.o quota.o resource.o
signal.o sock.o system.o term.o time.o proc.o scsi.o stream.o block.o cde.o
okapi.o ../readelf-mini/libreadelf-mini.a
/usr/bin/ld: syscall.o:/<>/strace-4.6/defs.h:38: multiple
definition of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38:
first defined here
/usr/bin/ld: syscall.o:/<>/strace-4.6/defs.h:37: multiple
definition of `CDE_PACKAGE_DIR';
strace.o:/<>/strace-4.6/defs.h:37: first defined here
/usr/bin/ld: count.o:/<>/strace-4.6/defs.h:38: multiple definition
of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first
defined here
/usr/bin/ld: count.o:/<>/strace-4.6/defs.h:37: multiple definition
of `CDE_PACKAGE_DIR'; strace.o:/<>/strace-4.6/defs.h:37: first
defined here
/usr/bin/ld: util.o:/<>/strace-4.6/defs.h:38: multiple definition
of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first
defined here
/usr/bin/ld: util.o:/<>/strace-4.6/defs.h:37: multiple definition
of `CDE_PACKAGE_DIR'; strace.o:/<>/strace-4.6/defs.h:37: first
defined here
/usr/bin/ld: desc.o:/<>/strace-4.6/defs.h:38: multiple definition
of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first
defined here
/usr/bin/ld: desc.o:/<>/strace-4.6/defs.h:37: multiple definition
of `CDE_PACKAGE_DIR'; strace.o:/<>/strace-4.6/defs.h:37: first
defined here
/usr/bin/ld: file.o:/<>/strace-4.6/defs.h:38: multiple definition
of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first
defined here
/usr/bin/ld: file.o:/<>/strace-4.6/defs.h:37: multiple definition
of `CDE_PACKAGE_DIR'; strace.o:/<>/strace-4.6/defs.h:37: first
defined here
/usr/bin/ld: ipc.o:/<>/strace-4.6/defs.h:38: multiple definition
of `CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first
defined here
/usr/bin/ld: ipc.o:/<>/strace-4.6/defs.h:37: multiple definition
of `CDE_PACKAGE_DIR'; strace.o:/<>/strace-4.6/defs.h:37: first
defined here
/usr/bin/ld: io.o:/<>/strace-4.6/defs.h:38: multiple definition of
`CDE_ROOT_DIR'; strace.o:/<>/strace-4.6/defs.h:38: first defined
here
/usr/bin/ld: io.o:/<>/strace-4.6/defs.h:37: multiple definition of
Bug#945506: Processed: dkms: export CC pointing to the kernels compiler
Hi Andreas, Thanks for filing 984929. Do you have a sense for what the cutoff should be for trying to get 984929 resolved vs. just uploading a workaround in the dkms-consuming packages (e.g., openafs)? Thanks, Ben On Wed, Mar 10, 2021 at 01:09:06PM +, Debian Bug Tracking System wrote: > Processing control commands: > > > block 984862 with -1 > Bug #984862 [iptables-netflow-dkms] iptables-netflow-dkms: module wants to > build with gcc instead of kernel's compiler > 984862 was not blocked by any bugs. > 984862 was not blocking any bugs. > Added blocking bug(s) of 984862: 984929 > > block 945506 with -1 > Bug #945506 [openafs-modules-dkms] openafs-modules-dkms: module wants to > build with gcc instead of kernel's compiler > 945506 was not blocked by any bugs. > 945506 was not blocking any bugs. > Added blocking bug(s) of 945506: 984929 > > block 946497 with -1 > Bug #946497 [zfs-dkms] zfs-dkms: module wants to build with gcc instead of > kernel's compiler > 946497 was not blocked by any bugs. > 946497 was not blocking any bugs. > Added blocking bug(s) of 946497: 984929 > > -- > 945506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945506 > 946497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946497 > 984862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984862 > 984929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984929 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#984931: git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7.
Package: git-el,elpa-magit Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.99.0.git0957.ge8c7bd03-1 Control: found -1 1:2.30.1-1 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. The error was observed by testing git-el with --install-recommends enabled. The error occurred in elpa-magit, which could be tested fine on its own. >From the attached log (scroll to the bottom...): Setting up elpa-magit (2.99.0.git0957.ge8c7bd03-1) ... tsort: -: input contains a loop: tsort: elpa-dash tsort: emacsen-common tsort: -: input contains a loop: tsort: elpa-git-commit tsort: emacsen-common tsort: elpa-transient tsort: -: input contains a loop: tsort: elpa-git-commit tsort: emacsen-common tsort: elpa-with-editor tsort: -: input contains a loop: tsort: elpa-git-commit tsort: emacsen-common tsort: -: input contains a loop: tsort: emacsen-common tsort: elpa-transient tsort: -: input contains a loop: tsort: elpa-with-editor tsort: emacsen-common Install git for emacs install/git: Handling install of emacsen flavor emacs install/git: Byte-compiling for emacs + emacs -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el /usr/lib/emacsen-common/packages/install/git: 26: emacs: not found /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7. dpkg: error processing package elpa-magit (--configure): installed elpa-magit package post-installation script subprocess returned error exit status 2 Setting up libm17n-0:i386 (1.8.0-2) ... Setting up librsvg2-2:i386 (2.50.3+dfsg-1) ... Setting up librsvg2-common:i386 (2.50.3+dfsg-1) ... Setting up glib-networking:i386 (2.66.0-2) ... Setting up libsoup2.4-1:i386 (2.72.0-2) ... Setting up libsoup-gnome2.4-1:i386 (2.72.0-2) ... Setting up librest-0.7-0:i386 (0.8.1-1.1) ... Setting up libgtk-3-0:i386 (3.24.24-3) ... Setting up libgtk-3-bin (3.24.24-3) ... Setting up emacs-gtk (1:27.1+1-3) ... update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs) in auto mode update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) in auto mode Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install git for emacs install/git: Handling install of emacsen flavor emacs install/git: Byte-compiling for emacs + emacs -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el Install elpa-transient for emacs install/transient-0.2.0.30: Handling install of emacsen flavor emacs install/transient-0.2.0.30: byte-compiling for emacs Install elpa-with-editor for emacs install/with-editor-3.0.2: Handling install of emacsen flavor emacs install/with-editor-3.0.2: byte-compiling for emacs Install elpa-dash for emacs install/dash-2.17.0: Handling install of emacsen flavor emacs install/dash-2.17.0: byte-compiling for emacs Install elpa-git-commit for emacs install/git-commit-2.99.0: Handling install of emacsen flavor emacs install/git-commit-2.99.0: byte-compiling for emacs Install elpa-magit for emacs install/magit-2.99.0: Handling install of emacsen flavor emacs install/magit-2.99.0: byte-compiling for emacs Setting up git-el (1:2.30.1-1) ... Install git for emacs install/git: Handling install of emacsen flavor emacs install/git: Byte-compiling for emacs + emacs -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el Install git for emacs install/git: Handling install of emacsen flavor emacs install/git: Byte-compiling for emacs + emacs -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el Setting up emacs (1:27.1+1-3) ... Processing triggers for install-info (6.7.0.dfsg.2-6) ... Processing triggers for libc-bin (2.31-9) ... Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.2+dfsg-1) ... Errors were encountered while processing: elpa-magit cheers, Andreas git-el_1:2.30.1-1.log.gz Description: application/gzip
Processed: git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7.
Processing control commands: > found -1 2.99.0.git0957.ge8c7bd03-1 Bug #984931 [git-el,elpa-magit] git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7. There is no source info for the package 'git-el' at version '2.99.0.git0957.ge8c7bd03-1' with architecture '' Marked as found in versions magit/2.99.0.git0957.ge8c7bd03-1. > found -1 1:2.30.1-1 Bug #984931 [git-el,elpa-magit] git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7. There is no source info for the package 'elpa-magit' at version '1:2.30.1-1' with architecture '' Marked as found in versions git/1:2.30.1-1. -- 984931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dkms: export CC pointing to the kernels compiler
Processing control commands: > block 984862 with -1 Bug #984862 [iptables-netflow-dkms] iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler 984862 was not blocked by any bugs. 984862 was not blocking any bugs. Added blocking bug(s) of 984862: 984929 > block 945506 with -1 Bug #945506 [openafs-modules-dkms] openafs-modules-dkms: module wants to build with gcc instead of kernel's compiler 945506 was not blocked by any bugs. 945506 was not blocking any bugs. Added blocking bug(s) of 945506: 984929 > block 946497 with -1 Bug #946497 [zfs-dkms] zfs-dkms: module wants to build with gcc instead of kernel's compiler 946497 was not blocked by any bugs. 946497 was not blocking any bugs. Added blocking bug(s) of 946497: 984929 -- 945506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945506 946497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946497 984862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984862 984929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984854: marked as done (seqsero: Seqsero invokes python2.7 during execution)
Your message dated Wed, 10 Mar 2021 12:48:37 + with message-id and subject line Bug#984854: fixed in seqsero 1.0.1+dfsg-3 has caused the Debian Bug report #984854, regarding seqsero: Seqsero invokes python2.7 during execution 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.) -- 984854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: seqsero Version: 1.0.1+dfsg-2 Severity: serious X-Debbugs-Cc: nil...@debian.org Dear Maintainer, Seqsero seems to invoke python2.7 during execution, for example here[1] Similar invocation statements have _not_ been patched out yet in the d/patches/2to3.patch, probably affecting the functionality serverly. [1]: https://sources.debian.org/src/seqsero/1.0.1+dfsg-2/SeqSero.py/#L35 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages seqsero depends on: ii bwa0.7.17-5 ii python33.9.1-1 ii python3-biopython 1.78+dfsg-3 ii samtools 1.10-4 ii sra-toolkit2.10.7+dfsg-1 seqsero recommends no packages. Versions of packages seqsero suggests: pn ispcr -- no debconf information --- End Message --- --- Begin Message --- Source: seqsero Source-Version: 1.0.1+dfsg-3 Done: Shruti Sridhar We believe that the bug you reported is fixed in the latest version of seqsero, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shruti Sridhar (supplier of updated seqsero 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 Mar 2021 23:47:46 +0530 Source: seqsero Architecture: source Version: 1.0.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Shruti Sridhar Closes: 970598 984854 Changes: seqsero (1.0.1+dfsg-3) unstable; urgency=medium . * Team Upload. [ Nilesh Patra ] * Add test depends on current package, cleanup test debug statements . [ Shruti Sridhar ] * Update 2to3 patch (Closes: #984854) * Add autopkgtest. (Closes: #970598) * Both the above changes are meant as targeted fixes Checksums-Sha1: e636e1005434e15206c831e6cab9fa622e49c347 2028 seqsero_1.0.1+dfsg-3.dsc 4666fbae58ae4a4509a769230c6d369a6260e8e8 42760 seqsero_1.0.1+dfsg-3.debian.tar.xz 54e25bc951a9637ab328905e7cb2228c2bd0b2e5 6322 seqsero_1.0.1+dfsg-3_amd64.buildinfo Checksums-Sha256: bf5e43b9dd9f3fd2051907f004027d15b914b95a2a1c83b697514730bc68838e 2028 seqsero_1.0.1+dfsg-3.dsc 7c80e010529451f905ae7f3edcc31f4a6c658e157b8ad3e272732bb40ab3e085 42760 seqsero_1.0.1+dfsg-3.debian.tar.xz 283ff3915f622d5683145fd49bfd9eef68e749f0fded0341417facd56a0f589b 6322 seqsero_1.0.1+dfsg-3_amd64.buildinfo Files: ee50a5de6a0fba48ca57c8abb382290c 2028 science optional seqsero_1.0.1+dfsg-3.dsc b72e1f7befe19b509267a0731e71b777 42760 science optional seqsero_1.0.1+dfsg-3.debian.tar.xz f9625d83cffea72b92980f143d67fa04 6322 science optional seqsero_1.0.1+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmBIvAoUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafGkhg//TYbYH+MepbP9YnGCJMWcvpPrer4Q PvmptViYJiYZjHqFBFl8ZIlbs963WpwZ1S+VUBsLh4lrGIAdtBp3yinVQJOHh5rj 1EkDVWyGYHfEIu6SmwCuZQQeKd0IyBfHGAW2r2kCmnMpKa6XQPFHnQP4c8OKYkUy sOoTEzKy5L33ePT00VfL5uQD9bQ2Z4O9mzU6g3//a7Go/WjPOsyPrmLX0NU4JHGh 9nVPQRqVgzI4w4e/Y3v20uJbXLPDWj+9kVBiZm43RgpjB/JWUTG4PVXm6SoHPhQj CViwPJfgLHDr6bjBIcK5J3EfIumkV2AIGh5nWcyfeyX3w96fPkhMjsNFHVloUROX DcI7DIQFB15kdQRUbP2eJ/7UY7nmP6N4eUELvIxt4x7HRwIX23HhcorXtcgUz5bX 0Bniljx7zbrSuXcKx84JZw7al1YYZdFJjimXGOagHpyMb1ezDwELII7Yo4OL/rQh ux4NG7KEAVsQQ0EDgqsIHUlGG3CDz6s5w3Se8vItSe54P8irXydBgKhr13vr/gWI
Processed: Can't reproduce
Processing commands for cont...@bugs.debian.org: > tags 983618 +moreinfo +unreproducible Bug #983618 [python3-zaqar-ui] python3-zaqar-ui: causes openstack-dashboard to fail upon installation Added tag(s) moreinfo. Bug #983618 [python3-zaqar-ui] python3-zaqar-ui: causes openstack-dashboard to fail upon installation Added tag(s) unreproducible. > severity 983618 important Bug #983618 [python3-zaqar-ui] python3-zaqar-ui: causes openstack-dashboard to fail upon installation Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 983618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 984859 in 0.8.7-2
Processing commands for cont...@bugs.debian.org:
> notfound 984859 0.8.7-2
Bug #984859 {Done: Simon McVittie } [flatpak] flatpak: sandbox
escape via special tokens in .desktop file (flatpak#4146)
Ignoring request to alter found versions of bug #984859 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984613: marked as done (glance-store-common: prompting due to modified conffiles which were not modified by the user: /etc/glance/rootwrap.conf)
Your message dated Wed, 10 Mar 2021 10:18:28 + with message-id and subject line Bug#984613: fixed in python-glance-store 2.3.0-4 has caused the Debian Bug report #984613, regarding glance-store-common: prompting due to modified conffiles which were not modified by the user: /etc/glance/rootwrap.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.) -- 984613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glance-store-common Version: 2.3.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + glance-common Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#behavior, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." https://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In https://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. This was observed during a buster -> bullseye upgrade. >From the attached log (scroll to the bottom...): Setting up glance-store-common (2.3.0-3) ... Configuration file '/etc/glance/rootwrap.conf' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** rootwrap.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package glance-store-common (--configure): end of file on stdin at conffile prompt cheers, Andreas glance-common_2:21.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-glance-store Source-Version: 2.3.0-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-glance-store, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-glance-store 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: Wed, 10 Mar 2021 10:58:01 +0100 Source: python-glance-store Architecture: source Version: 2.3.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 984613 Changes: python-glance-store (2.3.0-4) unstable; urgency=medium . * glance-store-common.preinst: remove /etc/glance/rootwrap.conf, if it was an unmodified filed by the glance-common postinst, to avoid dpkg interactive prompting. (Closes: #984613) Checksums-Sha1: 670ceaea8f695b9ce33a726966492328f04b1147 3115 python-glance-store_2.3.0-4.dsc 0af99b3035253c3c66e546af638931183a9bba8b 5784 python-glance-store_2.3.0-4.debian.tar.xz c8d19ecd01972ca4c2d09b8708e5019815f8aea3 13097 python-glance-store_2.3.0-4_amd64.buildinfo Checksums-Sha256: d2a6be1fd321f52008d1c7a13ce92738baf246fab5197e726c8c9cdbcda31723 3115 python-glance-store_2.3.0-4.dsc 4e171a2814255ab9d950dbf539c1726e39e6fa4f82a2e656b2afd9984f74c66c 5784 python-glance-store_2.3.0-4.debian.tar.xz 07f84e59dafc60b94c2f24242426cf32005b753d8d134ed75b69580243c6f013 13097 python-glance-store_2.3.0-4_amd64.buildinfo Files: 7673ba4ed88ed013247ddd1a96473a54 3115 python optional
Processed: Downgrading 977311 severity
Processing commands for cont...@bugs.debian.org: > severity 977311 important Bug #977311 [node-uglifyjs-webpack-plugin] node-uglifyjs-webpack-plugin: dead upstream since July 2019 Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 977311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977311: Triaging
Since Praveen says he wants to replace the package *after* bullseye, it's probably fine to downgrade this bug to "Important" and not have it as an RC bug before the release. Therefore, downgrading it. Cheers, Thomas Goirand (zigo)
Processed: Bug#984613 marked as pending in python-glance-store
Processing control commands: > tag -1 pending Bug #984613 [glance-store-common] glance-store-common: prompting due to modified conffiles which were not modified by the user: /etc/glance/rootwrap.conf Added tag(s) pending. -- 984613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984613: marked as pending in python-glance-store
Control: tag -1 pending Hello, Bug #984613 in python-glance-store 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-glance-store/-/commit/b3cac5fe74f35234259273751e9024a0d1eab236 * glance-store-common.preinst: remove /etc/glance/rootwrap.conf, if it was an unmodified filed by the glance-common postinst, to avoid dpkg interactive prompting. (Closes: #984613) (this message was generated automatically) -- Greetings https://bugs.debian.org/984613
Bug#984923: matlab-iso2mesh: move to contrib
Package: matlab-iso2mesh Version: 1.9.6+ds-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts matlab-iso2mesh depends on several packages in contrib, therefore it needs to be moved to contrib as well. The following packages have unmet dependencies: matlab-iso2mesh : Depends: matlab-zmat but it is not installable Depends: matlab-jsonlab but it is not installable Depends: matlab-jnifti but it is not installable You can build a single binary package in contrib from a source package in main by just setting Section: contrib/science Andreas
Processed: user debian...@lists.debian.org, usertagging 969609, affects 984866, affects 969609 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 969609 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 984866 + librust-diesel+network-address-dev
Bug #984866 [src:rust-diesel] rust-diesel: depends on multiple unavailable
packages
Added indication that 984866 affects librust-diesel+network-address-dev
> affects 969609 + librust-zstd-dev librust-zstd+bindgen-dev
> librust-zstd+legacy-dev librust-zstd+wasm-dev
Bug #969609 [src:rust-zstd] rust-zstd: unbuildable, uninstallable, depends on
non-existent rust-zstd-safe
Added indication that 969609 affects librust-zstd-dev,
librust-zstd+bindgen-dev, librust-zstd+legacy-dev, and librust-zstd+wasm-dev
> usertags 964842 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 964842 + libghc-yesod-auth-oauth2-dev libghc-yesod-auth-oauth2-doc
> libghc-yesod-auth-oauth2-prof
Bug #964842 [src:haskell-yesod-auth-oauth2] haskell-yesod-auth-oauth2:
BD-Uninstallable
Added indication that 964842 affects libghc-yesod-auth-oauth2-dev,
libghc-yesod-auth-oauth2-doc, and libghc-yesod-auth-oauth2-prof
> usertags 885677 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 885677 2.18.8+dfsg-1
Bug #885677 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[src:lablgtk2] liblablgtksourceview2-ocaml: Depends on unmaintained
gtksourceview2
Marked as found in versions lablgtk2/2.18.8+dfsg-1.
> affects 885677 + liblablgtksourceview2-ocaml
Bug #885677 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[src:lablgtk2] liblablgtksourceview2-ocaml: Depends on unmaintained
gtksourceview2
Added indication that 885677 affects liblablgtksourceview2-ocaml
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677
964842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964842
969609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969609
984866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#983853: marked as pending in horizon
Control: tag -1 pending Hello, Bug #983853 in horizon 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/services/horizon/-/commit/c841eedc22bfd099cb1bafbe814f847dd050ff60 * Fix upgrade from Buster to Bullseye by manually copying the font-awesome scss files in Horizon static folder (Closes: #983853). (this message was generated automatically) -- Greetings https://bugs.debian.org/983853
Processed: Bug#983853 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #983853 [openstack-dashboard] openstack-dashboard: fails to upgrade from 'buster': Couldn't find anything to import: /horizon/lib/font_awesome/scss/font-awesome.scss Ignoring request to alter tags of bug #983853 to the same tags previously set -- 983853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: rust-libsqlite3-sys: depends on multiple unavailable packages
Processing control commands: > affects -1 + librust-libsqlite3-sys+bindgen-dev > librust-libsqlite3-sys+buildtime-bindgen-dev Bug #984921 [src:rust-libsqlite3-sys] rust-libsqlite3-sys: depends on multiple unavailable packages Added indication that 984921 affects librust-libsqlite3-sys+bindgen-dev and librust-libsqlite3-sys+buildtime-bindgen-dev -- 984921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984921: rust-libsqlite3-sys: depends on multiple unavailable packages
Source: rust-libsqlite3-sys Version: 0.15.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + librust-libsqlite3-sys+bindgen-dev librust-libsqlite3-sys+buildtime-bindgen-dev Hi, the binary packages built from src:rust-libsqlite3-sys depend on several no longer available packages, e.g. The following packages have unmet dependencies: librust-libsqlite3-sys+bindgen-dev : Depends: librust-bindgen-0.50+default-dev but it is not installable Andreas
Bug#983853: marked as pending in horizon
Control: tag -1 pending Hello, Bug #983853 in horizon 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/services/horizon/-/commit/c841eedc22bfd099cb1bafbe814f847dd050ff60 * Fix upgrade from Buster to Bullseye by manually copying the font-awesome scss files in Horizon static folder (Closes: #983853). (this message was generated automatically) -- Greetings https://bugs.debian.org/983853
Processed: Bug#983853 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #983853 [openstack-dashboard] openstack-dashboard: fails to upgrade from 'buster': Couldn't find anything to import: /horizon/lib/font_awesome/scss/font-awesome.scss Added tag(s) pending. -- 983853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: rust-cookie: depends on multiple unavailable packages
Processing control commands: > affects -1 + librust-cookie+ring-dev librust-cookie+base64-dev > librust-cookie+secure-dev Bug #984919 [src:rust-cookie] rust-cookie: depends on multiple unavailable packages Added indication that 984919 affects librust-cookie+ring-dev, librust-cookie+base64-dev, and librust-cookie+secure-dev -- 984919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984919: rust-cookie: depends on multiple unavailable packages
Source: rust-cookie Version: 0.12.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + librust-cookie+ring-dev librust-cookie+base64-dev librust-cookie+secure-dev Hi, the binary packages built from src:rust-cookie depend on several no longer available packages, e.g. The following packages have unmet dependencies: librust-cookie+ring-dev : Depends: librust-ring-0.14+default-dev but it is not installable Andreas
Processed: rust-combine: depends on multiple unavailable packages
Processing control commands: > affects -1 + librust-combine+combine-regex-1-dev librust-combine+doc-dev > librust-combine+regex-dev Bug #984914 [src:rust-combine] rust-combine: depends on multiple unavailable packages Added indication that 984914 affects librust-combine+combine-regex-1-dev, librust-combine+doc-dev, and librust-combine+regex-dev -- 984914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984914: rust-combine: depends on multiple unavailable packages
Source: rust-combine Version: 3.8.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + librust-combine+combine-regex-1-dev librust-combine+doc-dev librust-combine+regex-dev Hi, the binary packages built from src:rust-combine depend on several no longer available packages, e.g. The following packages have unmet dependencies: librust-combine+combine-regex-1-dev : Depends: librust-combine-regex-1-1+default-dev but it is not installable Andreas
Bug#984862: iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler
On 10/03/2021 03.25, Axel Beckert wrote: Correct. But how do I determine that kernel-specific compiler without tracking down package dependencies? linux-compiler-gcc-10-x86 seems not to provide a symlink or similar. Or is tracking down package dependencies the way to go? If you are inside Kbuild, CC is set to the correct value. But you are calling a configure script outside of Kbuild ... Actually I would have expected that DKMS already takes care of this. That is actually a good idea. dkms knows which headers to use, so it should try to find the correct CC and set this. That should help all of these packages, unless they hardcode CC=gcc somewhere. Andreas
Bug#982704: marked as done (ofxstatement-plugins: FTBFS: TypeError: expected str, bytes or os.PathLike object, not NoneType)
Your message dated Wed, 10 Mar 2021 08:33:23 + with message-id and subject line Bug#982704: fixed in ofxstatement-plugins 20210310 has caused the Debian Bug report #982704, regarding ofxstatement-plugins: FTBFS: TypeError: expected str, bytes or os.PathLike object, not NoneType 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.) -- 982704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ofxstatement-plugins Version: 20210108 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210213 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd ofxstatement-1822direkt && python3 setup.py test > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > writing src/ofxstatement_germany_1822direkt.egg-info/PKG-INFO > writing dependency_links to > src/ofxstatement_germany_1822direkt.egg-info/dependency_links.txt > writing entry points to > src/ofxstatement_germany_1822direkt.egg-info/entry_points.txt > writing namespace_packages to > src/ofxstatement_germany_1822direkt.egg-info/namespace_packages.txt > writing requirements to > src/ofxstatement_germany_1822direkt.egg-info/requires.txt > writing top-level names to > src/ofxstatement_germany_1822direkt.egg-info/top_level.txt > reading manifest file > 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt' > writing manifest file > 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt' > running build_ext > > -- > Ran 0 tests in 0.000s > > OK > # run pytest with doctest and ignore exit code 5 (no tests found) > cd ofxstatement-1822direkt && PYTEST_ADDOPTS=--doctest-modules python3 > setup.py pytest; \ > PYTEST_RESULT=$?; \ > test $PYTEST_RESULT -eq 5 && exit 0; \ > exit $PYTEST_RESULT > running pytest > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > writing src/ofxstatement_germany_1822direkt.egg-info/PKG-INFO > writing dependency_links to > src/ofxstatement_germany_1822direkt.egg-info/dependency_links.txt > writing entry points to > src/ofxstatement_germany_1822direkt.egg-info/entry_points.txt > writing namespace_packages to > src/ofxstatement_germany_1822direkt.egg-info/namespace_packages.txt > writing requirements to > src/ofxstatement_germany_1822direkt.egg-info/requires.txt > writing top-level names to > src/ofxstatement_germany_1822direkt.egg-info/top_level.txt > reading manifest file > 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt' > writing manifest file > 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt' > running build_ext > = test session starts > == > platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 > rootdir: /<>/_ofxstatement-germany/germany_1822direkt > collected 0 items > > no tests ran in 0.01s > = > cd ofxstatement-airbankcz && python3 setup.py test > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > writing src/ofxstatement_airbankcz.egg-info/PKG-INFO > writing dependency_links to > src/ofxstatement_airbankcz.egg-info/dependency_links.txt > writing entry points to src/ofxstatement_airbankcz.egg-info/entry_points.txt > writing namespace_packages to > src/ofxstatement_airbankcz.egg-info/namespace_packages.txt > writing requirements to src/ofxstatement_airbankcz.egg-info/requires.txt > writing top-level names to src/ofxstatement_airbankcz.egg-info/top_level.txt > reading manifest file 'src/ofxstatement_airbankcz.egg-info/SOURCES.txt' > reading manifest template '
Bug#984913: librust-backtrace+rustc-dep-of-std-dev: depends on unavailable librust-cfg-if-0.1+rustc-dep-of-std-dev
Package: librust-backtrace+rustc-dep-of-std-dev Version: 0.3.46-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts The following packages have unmet dependencies: librust-backtrace+rustc-dep-of-std-dev : Depends: librust-cfg-if-0.1+rustc-dep-of-std-dev (>= 0.1.10-~~) but it is not installable Andreas
