Bug#1066397: lgeneral: FTBFS: ../config.h:566:12: fatal error: direct.h: No such file or directory

on the system + . + We currently need to only change the generated configure because the + package disables the autoreconf sequence, due to the upstream build system + being out-of-date and failing to autoreconf cleanly. To fix this properly + the build system should get updated, then the sequence re-ena

Bug#1066466: rlinetd: FTBFS: ../../src/cleanups.c:27:49: error: implicit declaration of function ‘pmap_unset’ [-Werror=implicit-function-declaration]

Control: tag -1 patch Hi! On Wed, 2024-03-13 at 12:56:21 +0100, Lucas Nussbaum wrote: > Source: rlinetd > Version: 0.9.3-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef > This is most likely

Bug#1066470: kxl: FTBFS: KXLsound.c:75:9: error: implicit declaration of function 'read'; did you mean 'fread'? [-Werror=implicit-function-declaration]

Control: tag -1 patch Hi! On Wed, 2024-03-13 at 12:52:04 +0100, Lucas Nussbaum wrote: > Source: kxl > Version: 1.1.7-17 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef > This is most likely

Bug#1066671: geki3: FTBFS: boss.c:205:11: error: implicit declaration of function ‘CreateEnemyBomb’; did you mean ‘CreateEnemyShot’? [-Werror=implicit-function-declaration]

Hi! On Fri, 2024-05-03 at 12:57:21 +0200, Guillem Jover wrote: > The attached patch should fix this FTBFS Sorry, please use the attached patch instead which fixes some typos in the patch description. Thanks, Guillem diff --git c/debian/patches/020_headers.diff i/debian/patches/020_headers.d

Bug#1066549: geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration]

Hi! On Fri, 2024-05-03 at 13:06:21 +0200, Guillem Jover wrote: > Actually, the attached debdiff should be better (properly split > patches). Hrmmf, sorry, please use the attached patch, which fixes some typos in the patch description. :) Thanks, Guillem diff -Nru geki2-2.0.3/debian/p

Bug#1066390: gravitywars: FTBFS: misc.c:6:9: error: implicit declaration of function ‘keyboard_update’ [-Werror=implicit-function-declaration]

y to rework the patch. Thanks, Guillem diff -Nru gravitywars-1.102/debian/patches/implicit-decls.patch gravitywars-1.102/debian/patches/implicit-decls.patch --- gravitywars-1.102/debian/patches/implicit-decls.patch 1970-01-01 01:00:00.0 +0100 +++ gravitywars-1.102/debian/patches/implicit-dec

Bug#1066549: geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration]

Hi! On Fri, 2024-05-03 at 12:42:19 +0200, Guillem Jover wrote: > Control: tag -1 patch > On Wed, 2024-03-13 at 12:50:29 +0100, Lucas Nussbaum wrote: > > Source: geki2 > > Version: 2.0.3-10 > > Severity: serious > > Justification: FTBFS > > Tags: trixie

Bug#1066671: geki3: FTBFS: boss.c:205:11: error: implicit declaration of function ‘CreateEnemyBomb’; did you mean ‘CreateEnemyShot’? [-Werror=implicit-function-declaration]

nclude #include ++#include #include #include "KXL.h" + diff --git c/debian/patches/020_implicit-decl.patch i/debian/patches/020_implicit-decl.patch new file mode 100644 index 000..ba22660 --- /dev/null +++ i/debian/patches/020_implicit-decl.patch @@ -0,0 +1,59 @@ +Description:

Bug#1066549: geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration]

Control: tag -1 patch Hi! On Wed, 2024-03-13 at 12:50:29 +0100, Lucas Nussbaum wrote: > Source: geki2 > Version: 2.0.3-10 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef > During a rebuild of

Bug#1070027: fdisk: dependency problems prevent configuration of fdisk

Control: severity -1 normal Hi! On Mon, 2024-04-29 at 00:01:02 +0200, Chris Hofstaedtler wrote: > Control: reassign -1 dpkg > > * Vincent Lefevre [240428 22:33]: > > Package: fdisk > > Version: 2.40-8 > > Severity: serious > ... > > Setting up util-linux (2.40-8) ... > > fstrim.service is a

Bug#1066507: closed by Debian FTP Masters (reply to Guillem Jover ) (Bug#1066507: fixed in kannel 1.4.5-14)

SL or configure with --disable-ssl > > It has been closed by Debian FTP Masters > (reply to Guillem Jover ). Just sending keep-alive mail to avoid the auto-removal, as the bug is already fixed in sid, but not migrating due to the time64 transition. Thanks, Guillem

Bug#1066952: Defaulting to -Werror=implicit-function-declaration might not be a good idea

Hi! On Sat, 2024-03-16 at 02:18:22 +0200, Adrian Bunk wrote: > Package: dpkg-dev > Version: 1.22.6 > Severity: serious > X-Debbugs-Cc: Steve Langasek > 3. Code that does still compile with -Werror=implicit-function-declaration >but behaves differently, e.g. due to failing autoconf tests

Bug#1065371: in package dpkg marked as pending

Control: tag 1065371 pending Hi! Bug #1065371 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=4993fe783 --- Dpkg::Vendor::Debian:

Bug#1065486: sbd: FTBFS due to hardcoded libaio SONAME used in dlopen()

the current SONAME at this point in time, simply use libaio.so. Author: Guillem Jover Last-Update: 2024-03-05 --- tests/sbd-testbed.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/tests/sbd-testbed.c +++ b/tests/sbd-testbed.c @@ -154,9 +154,9 @@ init (void) orig_fopen

Bug#1062218: in package libaio marked as pending

--- commit 8d2d6c2930be1e34cb357ab4f1b8d42471a16f77 Author: Guillem Jover Date: Tue Mar 5 11:33:36 2024 +0100 Add time64 support - Remove dead code for syscall handling. - Refactor code to use an internal implementation for public functions that handle timespec, by switching

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

Hi! On Mon, 2024-03-04 at 13:51:19 +0100, Guillem Jover wrote: > I've got all the upstream changes now ready, except that there's still > one test case failing, something wrong with the sigset_t type. I've run > out of time trying to track this down, but I've pushed what I have on > t

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

Hi! On Sun, 2024-03-03 at 23:00:00 +0100, Guillem Jover wrote: > On Thu, 2024-02-29 at 02:35:16 +0100, Guillem Jover wrote: > > Control: tags -1 - pending > > > On Wed, 2024-01-31 at 19:36:09 +, Steve Langasek wrote: > > > Source: libaio > > > Versio

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

Hi! On Thu, 2024-02-29 at 02:35:16 +0100, Guillem Jover wrote: > Control: tags -1 - pending > On Wed, 2024-01-31 at 19:36:09 +, Steve Langasek wrote: > > Source: libaio > > Version: 0.3.113-5 > > Severity: serious > > Tags: patch pending > > Justif

Bug#1065371: unable to disable bug-implicit-func for time64

Hi! On Sun, 2024-03-03 at 16:46:33 +0100, Guillem Jover wrote: > On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote: > > - please provide an opt-out option. > > This is a bug, which I should fix. The first attached patch is what I'd use to fix this. > >

Bug#1065371: unable to disable bug-implicit-func for time64

On Sun, 2024-03-03 at 16:57:28 +0100, Matthias Klose wrote: > On 03.03.24 16:46, Guillem Jover wrote: > > On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote: > > > I just filed another bug report for bc, together with the one for heimdal. > > > > > > Pl

Bug#1065371: unable to disable bug-implicit-func for time64

Hi! On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote: > Control: severity -1 serious > I just filed another bug report for bc, together with the one for heimdal. > > Please turn this off for a while, it's really harmful for the time64 > bootstrap. This was added on request by Steve,

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

Control: tags -1 - pending Hi! On Wed, 2024-01-31 at 19:36:09 +, Steve Langasek wrote: > Source: libaio > Version: 0.3.113-5 > Severity: serious > Tags: patch pending > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t > Please find the patch

Bug#1064909: in package libbsd marked as pending

--- commit 864f359fe0eae118b73726c26591a0447c299359 Author: Guillem Jover Date: Wed Feb 28 05:15:20 2024 +0100 New libbsd upstream release 0.12.1 - Fix missing installation of err.h. Closes: #1064909 diff --git a/debian/changelog b/debian/changelog index 39f7b9e..0afdbbe 100644

Bug#1064909: libbsd-dev: Many functions (possibly all?) aren't available

Hi! On Tue, 2024-02-27 at 17:33:16 +0100, Alejandro Colomar wrote: > Package: libbsd-dev > Version: 0.12.0-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > X-Debbugs-Cc: a...@kernel.org > After upgrading to libbsd 0.12 today, several build systems that I use >

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

Hi! On Thu, 2024-02-15 at 16:48:43 -0800, Steve Langasek wrote: > Control: forwarded -1 seli...@vger.kernel.org > > Patch now forwarded upstream for review. > > https://lore.kernel.org/selinux/zc6tzkpsyzric...@homer.dodds.net/T/#t > On Wed, Feb 14, 2024 at 11:25:26PM -0800, Steve Langasek

Bug#1063646: tix: missing required debian/rules targets build-arch and/or build-indep

Source: tix Version: 8.4.3-11 Severity: serious Justification: Debian Policy section 4.9 Tags: sid trixie User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by

Bug#1063647: sysconfig: missing required debian/rules targets build-arch and/or build-indep

Source: sysconfig Version: 0.0.14 Severity: serious Justification: Debian Policy section 4.9 Tags: sid trixie User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required

Bug#1063644: atitvout: missing required debian/rules targets build-arch and/or build-indep

Source: atitvout Version: 0.4-13.2 Severity: serious Justification: Debian Policy section 4.9 Tags: sid trixie User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is

Bug#1063645: markdown: missing required debian/rules targets build-arch and/or build-indep

Source: markdown Version: 1.0.1-12 Severity: serious Justification: Debian Policy section 4.9 Tags: sid trixie User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

Hi! On Tue, 2024-02-06 at 15:42:33 +0100, Helmut Grohne wrote: > On Tue, Feb 06, 2024 at 11:34:07AM +0100, Adrien Nader wrote: > > Providing two APIs makes me quite uneasy due to having core components > > that would behave differently from the rest of the distribution. It > > sounds like

Bug#1059266: in package dupload marked as pending

Control: tag 1059266 pending Hi! Bug #1059266 in package dupload reported by you has been fixed in the dpkg/dupload.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dupload.git/diff/?id=62a1cb0 --- Revert "hooks:

Bug#1059266: error: cannot verify inline signature

'/usr/share/dupload/openpgp-check %1' failed > > for emmax_0~beta.20100307-4_riscv64-buildd.changes Ouch, ok. > > On 2023-12-22 12:16, Guillem Jover wrote: > > > Just to understand what is going wrong, I assume you don't have the > > >

Bug#1059266: error: cannot verify inline signature

Hi! On Fri, 2023-12-22 at 10:53:18 +0100, Christian Marillat wrote: > Package: dupload > Version: 2.10.4 > Severity: grave > This version fail to check a signature. Work fine with 2.10.3 > > , > | $ debrelease > | dupload note: no announcement will be sent. > | Checking OpenPGP signatures

Bug#1055580: dlt-daemon: Runs daemon as user nobody with owned files on fsys

Package: dlt-daemon Version: 2.18.0-1 Severity: serious Tags: security Hi! This daemon runs as user nobody, while creating multiple files on the filesystem owned by the same user, which are used as part of its security protection. This is a security issue, given that other daemons on the system

Bug#1054999: dlt-daemon: FTBFS: 5: /bin/sh: 1: killall: not found

(I'm filing another report for the /tmp stuff.) Attached a series of patches that "fix" this (and some of other cleanups. The only ones needed to workaround this problem are patch 2 and 3. Although ideally the test suite would be made parallel safe by using different files for each test case

Bug#1041731: groff-base: "-" mapped as HYPHEN

Hi! [ CCed Russ for the pod2man side of this. ] On Mon, 2023-08-14 at 14:18:51 +0200, Samuel Thibault wrote: > I'm marking this important, and am tempted to raise it to serious... > > The problem at stake is that we have already a hard time making > newcomers read manpages. If they can't even

Bug#1051189: intel-opencl-icd: Uninstallable since intel-graphics-compiler 1.0.14896.8-1 upload

Package: intel-opencl-icd Version: 22.43.24595.41-1 Severity: serious Hi! This package has become uninstallable since the upload of the source package intel-graphics-compiler 1.0.14896.8-1: ,--- $ apt install intel-opencl-icd Reading package lists... Done Building dependency tree...

Bug#1043118: victoriametrics: FTBFS: test failure

Hi! On Tue, 2023-08-08 at 14:59:45 +0300, Denys Holius wrote: > The latest version of VictoriaMetrics v1.92.0 > should be marked as > LTS but it has some backwards-incompatible changes. Meanwhile v1.87.6 >

Bug#1033671: MD5File() goes into an unconditional infinite loop on bullseye

Hi! On Fri, 2023-03-31 at 13:43:03 +0200, Guillem Jover wrote: > Control: fixed -1 0.11.4-1 > Control: severity -1 serious > > On Wed, 2023-03-29 at 20:51:07 +0200, Guillaume Morin wrote: > > Package: libbsd0 > > Version: 0.11.3-1 > > Tags: patch,upstream,fixed-up

Bug#1039621: libngs-jni: Installs shared object in wrong directory

Package: libngs-jni Version: 3.0.3+dfsg-5 Severity: serious Hi This package installs the shared object in the following _literal_ pathname: /usr/lib/$(DEB_HOST_MULTIARCH)/jni/libncbi-ngs.so Where the variable has not been expanded and appears as is. So the shared object will not be found.

Bug#1034120: sensible-utils: Broken shell invocation handling

Package: sensible-utils Version: 0.0.18 Severity: serious Hi! I installed this some time ago, and started seeing issues, but was still wondering why no one had reported this already and whether this was a local issue of mine, until I realized now this is an experimental only upload. In any case,

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

Hi! On Wed, 2023-03-08 at 14:26:13 +0100, Guilhem Moulin wrote: > On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote: > > On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote: > >> No please don't, #-1 is RC so that would block transitioning into > >> Bookworm which only

Bug#1032381: aide: Broken aideinit due to _aide user handling

On Sun, 2023-03-05 at 17:18:00 +0100, Marc Haber wrote: > On Sun, Mar 05, 2023 at 04:00:26PM +0100, Guillem Jover wrote: > > Package: aide > > Version: 0.18-2 > > Severity: serious > > Justification? After upgrade, something that used to work stopped working, whi

Bug#1032381: aide: Broken aideinit due to _aide user handling

Package: aide Version: 0.18-2 Severity: serious Hi! Just upgraded a server to Debian bookworm, and noticed that aideinit was not working anymore, giving the following error: ,--- # aideinit --yes --force Running aide --init... User [_aide] not known AIDE --init return code 1 `---

Bug#1013876: Please close this bug report for keepassxc-browser to migrate to testing

Hi! On Mon, 2023-02-06 at 19:57:02 +0100, Bruno Kleinert wrote: > neither revision gets properly loaded by Chromium as of today. > > As the freeze approaches, I will remove the Chromium package relation > and the symbolic link to the Web Extension >

Bug#1013876: Please close this bug report for keepassxc-browser to migrate to testing

Control: found -1 1.8.4+repack1-1 Control: found -1 1.8.4+repack1-2 Hi! On Mon, 2023-02-06 at 14:34:36 +0200, Adrian Bunk wrote: > On Fri, Nov 18, 2022 at 07:43:48PM +0100, Bruno Kleinert wrote: > > I do not have time to investigate and fix the issue in the mid-term. > > I'd appreciate if

Bug#1028961: dpkg: reverts to using insecure cryptographic algorithms by default

On Wed, 2023-01-25 at 21:44:27 +, James Addison wrote: > Package: dpkg > Version: 1.21.18 > Followup-For: Bug #1028961 > > Are SHA224 and SHA384 used widely by dpkg and/or Debian? I'd expect all (?) signatures for packaging artifacts in Debian to be SHA512. This change sets an explicit

Bug#1028961: in package dpkg marked as pending

Control: tag 1028961 pending Hi! Bug #1028961 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=3c42b0ed7 ---

Bug#1028961: dpkg: reverts to using insecure cryptographic algorithms by default

On Sun, 2023-01-15 at 11:45:20 +0100, Ansgar wrote: > Package: dpkg > Version: 1.21.13 > Severity: serious > Tags: security > X-Debbugs-Cc: Debian Security Team > dpkg 1.21.13 introduced passing "--openpgp" to GnuPG by default […]. This > causes GnuPG to use insecure cryptographic algorithms

Bug#1027476: closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1027476: fixed in cron 3.0pl1-155)

Control: reopen -1 Hi! Although I've not tested nor checked the affected code, the fix done to close this cannot possibly be correct, see below. :) On Mon, 2023-01-09 at 21:27:06 +, Debian Bug Tracking System wrote: > Date: Sun, 01 Jan 2023 07:12:58 -0500 > From: "Kevin P. Fleming" > To:

Bug#1027966: in package dpkg marked as pending

Control: tag 1027966 pending Hi! Bug #1027966 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=4c03965ef --- dpkg-genbuildinfo: Do

Bug#1027759: pylint: Missing dependency on python3-tomli for python3 < 3.11

Control: reopen -1 Control: reassign -1 devscripts Control: retitle -1 devscripts: Wrong usage of pylint as a module breaks Hi! On Thu, 2023-01-05 at 00:18:13 -0500, Sandro Tosi wrote: > > Package: pylint > > Version: 2.15.9-1 > > Severity: serious > > It looks like the recent release is

Bug#1027966: building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo

Control: found -1 1.21.10 On Thu, 2023-01-05 at 11:23:30 +0100, Matthias Klose wrote: > Package: dpkg-dev > Version: 1.21.16 > Severity: serious > Tags: sid bookworm > see > https://buildd.debian.org/status/fetch.php?pkg=cross-toolchain-base-ports=all=60=1672912429=0 > > touch

Bug#1027759: pylint: Missing dependency on python3-tomli for python3 < 3.11

Package: pylint Version: 2.15.9-1 Severity: serious Hi! It looks like the recent release is missing a dependency on python3-tomli when the python used is not at least 3.11. Seen on test suite failures locally and on the devscripts CI pipelines:

Bug#1026227: vagrant: Uninstallable in sid with VirtualBox 7.0.x

Hi! On Sun, 2022-12-18 at 18:10:16 -0300, Antonio Terceiro wrote: > On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote: > > Package: vagrant > > Version: 2.2.19+dfsg-2 > > Severity: serious > > Since virtualbox 7.0.4 got uploaded, vagrant is no longer insta

Bug#1026227: vagrant: Uninstallable in sid with VirtualBox 7.0.x

Package: vagrant Version: 2.2.19+dfsg-2 Severity: serious Hi! Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable in Debian sid. I assume this will require packaging a new upstream release to support the new virtualbox version 7.0.x series. Thanks, Guillem

Bug#1025261: vagrant: Broken with ruby3.1

Package: vagrant Version: 2.2.19+dfsg-1 Severity: serious Hi! After the upgrade of ruby to the 3.1 version vagrant has stopped working completely, I'm getting the following errors repeated multiple times: ,--- /usr/lib/ruby/vendor_ruby/rubygems/resolver/conflict.rb:47:in

Bug#1013876: Please close this bug report for keepassxc-browser to migrate to testing

On Thu, 2022-11-17 at 13:52:38 +, Amr Ibrahim wrote: > On Sat, 24 Sep 2022 21:37:45 +0200 Guillem Jover wrote: > > I've kept the package on hold since, but try to upgrade from time to > > time to see whether its fixed. Last time I did with the latest version > > curren

Bug#1023654: in package liburing marked as pending

=b80de0d --- commit b80de0dca45a2c0006d0cc2c4059d56f56898f57 Author: Guillem Jover Date: Mon Nov 14 00:13:19 2022 +0100 Artificially bump some symbol versions to 2.3 Do this for functions involved in a forward compatibility ABI break, for objects built against the new library and run

Bug#1023654: liburing 2.3 breaks binary compatibility

Hi! I've forwarded this upstream now. On Tue, 2022-11-08 at 14:44:25 +0100, Guillem Jover wrote: > On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote: > > On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev wrote: > > > In liburing.h in 2.3, structures io_uring_

Bug#1023654: liburing 2.3 breaks binary compatibility

Hi! On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote: > On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev wrote: > > Source: liburing > > Version: 2.3-1 > > Severity: grave > > > > liburing 2.3 broke binary compatibility without bumping the soname. Indeed. :/ Should make a habit of

Bug#1020898: Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6

Package: perl6-readline,raku-file-which,raku-librarycheck,raku-readline Severity: serious Hi! [ Filing against all affected packages because it's not clear to me which one needs to be fixed. ] These packages all contain (at least) these same filenames: ,--- perl6-readline:

Bug#1013876: Please close if fixed to migrate to testing

Hi! On Fri, 2022-09-23 at 13:27:31 +, Amr Ibrahim wrote: > On Mon, 27 Jun 2022 07:21:33 +0200 Bruno Kleinert > wrote: > > thanks for the report. Something else in 1.8.0 is bugging me that may > > be related to upstream's jQuery removal. I'm expecting upstream may > > release 1.8.1 soonish.

Bug#1019724: warning: stray \ before - causes autopkgtest failure

On Wed, 2022-09-14 at 17:31:16 +0200, Santiago Ruano Rincón wrote: > Yeah, sorry. I lately realised not all the packages would autoreconf > during building time. > > So silencing these warnings would make sense. Please consider implementing a way to be able to conditionally re-enable locally

Bug#995387: in package dpkg marked as pending

Control: tag 995387 pending Hi! Bug #995387 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=741d474aa --- dpkg: Fix conffile

Bug#1008478: in package dpkg marked as pending

Control: tag 1008478 pending Hi! Bug #1008478 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=699c417f5 --- dpkg-fsys-usrunmess:

Bug#1008316: in package dpkg marked as pending

Control: tag 1008316 pending Hi! Bug #1008316 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=7086b1b62 --- dpkg-fsys-usrunmess:

Bug#1000421: in package dpkg marked as pending

Control: tag 1000421 pending Hi! Bug #1000421 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=5a9f336dc --- Dpkg::Shlibs::Objdump:

Bug#919697: arcanist: file conflict with arc

Control: reassign -1 arcanist Hi! On Fri, 2022-09-02 at 07:46:43 +0200, Sylvestre Ledru wrote: > Le 02/09/2022 à 01:10, Guillem Jover a écrit : > > So we have reached the point at which arc is getting autoremoved from > > testing as the RC is still filed against it too. :( >

Bug#919697: arcanist: file conflict with arc

Hi! On Wed, 2022-08-10 at 01:29:27 +0200, Guillem Jover wrote: > [ The bug has been (correctly) bumped back to serious. Sorry that I > have not engaged about this bug in the past, but the reply to simply > ignore policy looked rather off-putting, I just noticed the reply >

Bug#1017440: pahole: Several tools just segfault

Package: pahole Version: 1.23-2 Severity: serious Hi! Many of the tools simply segfault when executed. On a shared library with debugging symbols: $ codiff libsysfs.so.2.0.1 libsysfs.so.2.0.1 Segmentation fault (core dumped) $ dtagnames libsysfs.so.2.0.1 Segmentation fault (core dumped)

Bug#919697: arcanist: file conflict with arc

Hi! [ The bug has been (correctly) bumped back to serious. Sorry that I have not engaged about this bug in the past, but the reply to simply ignore policy looked rather off-putting, I just noticed the reply below, which seemed encouraging! :) ] On Sat, 2019-01-26 at 11:20:13 +0100,

Bug#1013876: webext-keepassxc-browser: Version 1.8.0+repack1-2 fail to load in chromium

Package: webext-keepassxc-browser Version: 1.8.0+repack1-2 Severity: serious Hi! This version seems to fail load on chromium 103.0.5060.53-1, with the following warnings and errors shown on the extensions settings page: (W) Unrecognized manifest key 'applications'. (W) Manifest version 2 is

Bug#1012544: libworkflow1: Broken shared library packaging

Package: libworkflow1 Version: 0.9.10-1 Severity: serious Hi! This package has several problems: - It contains a shared library without a SOVERSION ,--- $ objdump -p /usr/lib/x86_64-linux-gnu/libworkflow.so | grep SONAME SONAME libworkflow.so `--- This means any

Bug#1008443: golang-github-smartystreets-assertions: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/smartystreets/assertions github.com/smartystreets/assert

Hi! On Sat, 2022-04-16 at 23:06:39 +0200, Drew Parsons wrote: > I don't understand the version scheme for this package. > > The Debian version is 1.10.1, which was released 1 Apr 2019. > > After that, many more versions were released, but with "older" version > numbers. The most recent was

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

Control: severity -1 normal Hi! On Fri, 2022-04-01 at 07:27:26 +0900, Norbert Preining wrote: > Package: dpkg > Version: 1.21.6 > Severity: critical > Justification: breaks the whole system The script does not break the whole system, it fails quite early during preparations before doing any

Bug#1008316: in package dpkg marked as pending

Control: tag 1008316 pending Hi! Bug #1008316 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=48e33c406 --- dpkg-fsys-usrunmess:

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

On Mon, 2022-03-28 at 09:34:35 +, Éric Valette wrote: > On 3/28/22 01:29, Guillem Jover wrote: > >> Invoquing the dkms postinstall script fails because it does not find > >> /lib/modules/x.y.z > >> > >> directories and rebooting without graphic dri

Bug#1008478: in package dpkg marked as pending

Control: tag 1008478 pending Hi! Bug #1008478 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=77756084e --- dpkg-fsys-usrunmess:

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

Control: retitle -1 dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Hi! On Sat, 2022-03-26 at 19:21:44 +0100, Eric Valette wrote: > Package: dpkg > Version: 1.21.4 > Severity: critical > Justification: breaks the whole system > Gobally the scripts does a very good job but it

Bug#1005141: linux-perf: Removes diversions on upgrade breaking it

Package: linux-perf Version: 5.16.3-1~exp1 Severity: serious Hi! This package has code in its postrm maintscript, which unconditionally removes the diversion, which breaks as the rename cannot be performed due to linux-base owning the file, and dpkg-divert refusing to overwrite it. This is the

Bug#1003814: in package dpkg-repack marked as pending

Control: tag 1003814 pending Hi! Bug #1003814 in package dpkg-repack reported by you has been fixed in the dpkg/dpkg-repack.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg-repack.git/diff/?id=55a6cc7 ---

Bug#1003664: fwupd: Too loose dependency on libfwupdN

Package: fwupd Version: 1.5.7-5 Severity: serious Hi! This package seems to use a too loose dependency on at least libfwupdN, but I suspect the same applies to libfwupdpluginM (or even libfwupdN from libfwupdpluginM). These are encoded as >=, which causes them to be upgradable on new upstream

Bug#1002258: marked as pending in golang-github-go-openapi-analysis

Control: tag -1 pending Hello, Bug #1002258 in golang-github-go-openapi-analysis 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:

Bug#995387: in package dpkg marked as pending

Control: tag 995387 pending Hi! Bug #995387 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=20e181fc2 --- dpkg: Fix conffile

Bug#1000421: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

Hi! On Sat, 2021-12-04 at 23:09:19 +, Ian Jackson wrote: > Joachim: > > I'm aware of that. And "shortly" definitely means "before the > > autoremoval" (which is currently scheduled for 2022-01-01). > > The real deadline is when I ought to take action myself, as someone > adversely affected

Bug#1000776: marked as pending in golang-github-go-openapi-validate

Control: tag -1 pending Hello, Bug #1000776 in golang-github-go-openapi-validate 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:

Bug#1000775: marked as pending in golang-github-go-openapi-validate

Control: tag -1 pending Hello, Bug #1000775 in golang-github-go-openapi-validate 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:

Bug#1000421: in package dpkg marked as pending

Control: tag 1000421 pending Hi! Bug #1000421 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=ecbd9f1b1 --- Dpkg::Shlibs::Objdump:

Bug#1000421: dpkg-shlibdeps: Wrong minimum version requirement on libc6

her arches and if they use the same symbol format. But at least it should improve things and not cause regressions as it will try both formats. Thanks, Guillem From a9c4f1806f1927a2da42712658f4cfdd37f73e50 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Tue, 23 Nov 2021 02:26:50 +0100 Subject:

Bug#999768: lintian: false report: adopted-extended-field XS-Autobuild

On Tue, 2021-11-16 at 13:11:26 +0100, Andreas Beckmann wrote: > Package: lintian > Version: 2.112.0 > Severity: serious > > Lintian now reports > > I: nvidia-graphics-drivers source: adopted-extended-field XS-Autobuild (in > section for source) [debian/control:26] > > but that field is not

Bug#997566: marked as pending in golang-github-prometheus-exporter-toolkit

Control: tag -1 pending Hello, Bug #997566 in golang-github-prometheus-exporter-toolkit 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:

Bug#995999: marked as pending in prometheus

Control: tag -1 pending Hello, Bug #995999 in prometheus 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:

Bug#995387: dpkg: remove-on-upgrade deletes symlink targets owned by another package

Hi! On Thu, 2021-09-30 at 16:21:21 +0200, Andreas Beckmann wrote: > Package: dpkg > Version: 1.20.6 > Severity: grave > Justification: breaks unrelated packages by removing their conffiles > > attached is a small package demonstrating the misbehavior of > remove-on-upgrade which may delete

Bug#995492: lintian: Broken --fails-on=none as default never got reverted

Package: lintian Version: 2.77.0 Severity: serious Sigh, So the problematic --fail-on default change never got actually reverted as the patch applied in commit 3758bfafd5dd742c327f2312dac8e3a71b1f036e omitted the relevant part that would make it work. :( None of the previous arguments against

Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

Control: reassign -1 glx-diversions 1.2.0 On Tue, 2021-09-14 at 11:19:43 +0200, Sébastien Villemot wrote: > Control: reassign -1 dpkg 1.20.9 > Le dimanche 12 septembre 2021 à 15:24 +, Witold Baryluk a écrit : > > Package: octave > > Version: 6.2.0-1 > > Followup-For: Bug #993338 > >

Bug#993135: in package inetutils marked as pending

=a7fcfbf --- commit a7fcfbf633594801e2c3d1c1ac1b9e994bb8bf7b Author: Guillem Jover Date: Sat Aug 28 01:15:04 2021 +0200 Stop using obsolete autoconf macros This will make the build stop emitting warnings that break the autopkgtest. Closes: #993135 diff --git a/debian

Bug#992602: libtinyxml2-9: Bogus Provides/Conflicts on libtinyxml2-8

Package: libtinyxml2-9 Version: 9.0.0+dfsg-2 Severity: serious Hi! This package contains bogus Provides/Conflicts against libtinyxml2-8 from when the package was named libtinyxml2-8a. These need to be removed as they are leftovers, incorrect (as they might make package depending on libtinyxml2-8

Bug#991399: mariadb: Daemon hangs on stop with replication and parallel slaves

Source: mariadb-10.5 Source-Version: 1:10.5.10-2 Severity: serious Forwarded: https://jira.mariadb.org/browse/MDEV-20821 Control: fixed -1 1:10.5.11-1~exp1 Hi! When replication is enabled with the slave running in parallel mode, the daemon completely hangs and will not terminate, which means

Bug#991334: monit: Race condition on reboot timestamp checks

dc50d6cca9a69922f75f98fe73d95bb2f1067cfa Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Tue, 20 Jul 2021 20:40:54 +0200 Subject: [PATCH] Use an epsilon when doing the reboot boot timestamp comparisons At least on Linux, the current method to retrieve the boot timestamp is racy, as we first

  1   2   3   4   5   6   7   8   >