Bug#1069064: marked as done (util-linux-extra: insufficient Replaces for util-linux due to /usr-move)
Your message dated Fri, 26 Apr 2024 10:44:03 +
with message-id
and subject line Bug#1069064: fixed in util-linux 2.40-7
has caused the Debian Bug report #1069064,
regarding util-linux-extra: insufficient Replaces for util-linux due to
/usr-move
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.)
--
1069064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux-extra
Version: 2.40-6
Severity: serious
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + util-linux
Hi Chris,
I think I mentioned this on IRC already and you intended to revert, but
nothing happened, so lets turn this into a bug for tracking purposes at
least.
util-linux-extra gained the utils ctrlaltdel, fsck.cramfs, fsck.minix,
mkfs.bfs, mkfs.cramfs, and mkfs.minix. In util-linux-extra, these now
reside below /usr/sbin while they used to reside in /sbin in util-linux
in bookworm and earlier. Hence upgrading from bookworm to sid can cause
these files to be lost.
I think we have three ways to address this:
1. Revert the move and retry after trixie. I think you favoured this?
2. Upgrade Breaks to Conflicts and issue a temporary protective
diversion from u-l-e.preinst to u-l-e.postinst. In theory, apt can
first unpack u-l, then unpack u-l-e and then configure both, so
there is a safe solution. However, there is a risk that apt could
decide to temporarily remove u-l and that would be really bad.
3. Keep Breaks and issue temporary diversions to be removed in forky's
u-l-e.postinst.
Please let me know your choice and I can do a patch.
Helmut
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.40-7
Done: Chris Hofstaedtler
We believe that the bug you reported is fixed in the latest version of
util-linux, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Hofstaedtler (supplier of updated util-linux 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: Fri, 26 Apr 2024 11:41:02 +0200
Source: util-linux
Architecture: source
Version: 2.40-7
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers
Changed-By: Chris Hofstaedtler
Closes: 1069064 1069634
Changes:
util-linux (2.40-7) unstable; urgency=medium
.
[ Chris Hofstaedtler ]
* Import upstream stable/v2.40 up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
* lsns: fix netns use
* libmount: fix comment typo for mnt_fs_get_comment()
* libmount: Fix access check for utab in context
* lsblk: simplify SOURCES code
* findmnt: always zero-terminate SOURCES data
* agetty: Don't override TERM passed by the user
* libsmartcols: reset wrap after calculation
* lslocks: remove a unused local variable
* lslocks: don't abort gathering per-process information even if
opening a /proc/[0-9]* fails
* lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing with ENOSYS
* lsns: report with warnx if a namespace related ioctl fails with ENOSYS
* Fix misplaced else in mnt_update_already_done
* findmnt: revise the code for -I and -D option (Closes: #1069634)
* libblkid: topology/ioctl: simplify ioctl handling
* libblkid: topology/ioctl: correctly handle kernel types
* pam_lastlog2: link against liblastlog
* libblkid: Fix segfault when blkid.conf doesn't exist (Closes: #1069634)
.
[ Helmut Grohne ]
* Fix /usr-move mitigation (Closes: #1069064).
Thanks!
Checksums-Sha1:
033ee23eb0abc00aa70357509d8acecc55aac653 4643 util-linux_2.40-7.dsc
732696cfce190b5f507a9c26cc8a0db919153e1c 08 util-linux_2.40-7.debian.tar.xz
b709e3e2a6f447e08ba8804bdb41999d8ce4f799 19579
util-linux_2.40-7_arm64.buildinfo
Checksums-Sha256:
c1a8aac385de4e93e2f71ec641652bdf89ff2c898e9cc7799eaf5076c2078220 4643
util-linux_2.40-7.dsc
fe7a854ac6659c5a668d4afad5e72ab87d3aeb0f0c313b3c07b8087294215291 08
util-linux_2.40-7.debian.tar.xz
90bd27ee0991db95b358726e96f215c143d19d8f70175298648fc4248afb2b54 19579
Bug#1069634: marked as done (/usr/bin/findmnt: util-linux: findmnt -D produces incorrect output)
Your message dated Fri, 26 Apr 2024 10:44:03 +
with message-id
and subject line Bug#1069634: fixed in util-linux 2.40-7
has caused the Debian Bug report #1069634,
regarding /usr/bin/findmnt: util-linux: findmnt -D produces incorrect output
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.)
--
1069634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux
Version: 2.40-6
Severity: normal
File: /usr/bin/findmnt
X-Debbugs-Cc: l...@lane-fu.com
Dear Maintainer,
Known Bug resolved in upstream package.
findmnt -D returns inode output instead of human-readable byte output.
Upstream commit aa0c45e8686df509c169121473d2cfb4fe18c3ea should resolve
issue.
See https://github.com/util-linux/util-linux/pull/2915
Thank you!
lane
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.8.7-edge-rockchip-rk3588 (SMP w/8 CPU threads; PREEMPT)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages util-linux depends on:
ii libblkid1 2.40-6
ii libc6 2.37-18
ii libcap-ng0 0.8.5-1
ii libcrypt1 1:4.4.36-4
ii libmount1 2.40-6
ii libpam0g 1.5.3-7
ii libselinux13.5-2+b2
ii libsmartcols1 2.40-6
ii libsystemd0255.4-1+b1
ii libtinfo6 6.4+20240414-1
ii libudev1 255.4-1+b1
ii libuuid1 2.40-6
Versions of packages util-linux recommends:
ii sensible-utils 0.0.22
Versions of packages util-linux suggests:
ii dosfstools 4.2-1.1
ii kbd 2.6.4-2
pn util-linux-extra
pn util-linux-locales
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.40-7
Done: Chris Hofstaedtler
We believe that the bug you reported is fixed in the latest version of
util-linux, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Hofstaedtler (supplier of updated util-linux 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: Fri, 26 Apr 2024 11:41:02 +0200
Source: util-linux
Architecture: source
Version: 2.40-7
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers
Changed-By: Chris Hofstaedtler
Closes: 1069064 1069634
Changes:
util-linux (2.40-7) unstable; urgency=medium
.
[ Chris Hofstaedtler ]
* Import upstream stable/v2.40 up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
* lsns: fix netns use
* libmount: fix comment typo for mnt_fs_get_comment()
* libmount: Fix access check for utab in context
* lsblk: simplify SOURCES code
* findmnt: always zero-terminate SOURCES data
* agetty: Don't override TERM passed by the user
* libsmartcols: reset wrap after calculation
* lslocks: remove a unused local variable
* lslocks: don't abort gathering per-process information even if
opening a /proc/[0-9]* fails
* lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing with ENOSYS
* lsns: report with warnx if a namespace related ioctl fails with ENOSYS
* Fix misplaced else in mnt_update_already_done
* findmnt: revise the code for -I and -D option (Closes: #1069634)
* libblkid: topology/ioctl: simplify ioctl handling
* libblkid: topology/ioctl: correctly handle kernel types
* pam_lastlog2: link against liblastlog
* libblkid: Fix segfault when blkid.conf doesn't exist (Closes: #1069634)
.
[ Helmut Grohne ]
* Fix /usr-move mitigation (Closes: #1069064).
Thanks!
Checksums-Sha1:
033ee23eb0abc00aa70357509d8acecc55aac653 4643 util-linux_2.40-7.dsc
732696cfce190b5f507a9c26cc8a0db919153e1c 08 util-linux_2.40-7.debian.tar.xz
b709e3e2a6f447e08ba8804bdb41999d8ce4f799 19579
util-linux_2.40-7_arm64.buildinfo
Checksums-Sha256:
c1a8aac385de4e93e2f71ec641652bdf89ff2c898e9cc7799eaf5076c2078220
Bug#1064715: marked as done (zabbix: FTBFS: make[4]: *** [Makefile:623: zabbix.com/cmd/zabbix_agent2] Error 1)
Your message dated Fri, 26 Apr 2024 10:45:13 + with message-id and subject line Bug#1064715: fixed in zabbix 1:6.0.29+dfsg-1 has caused the Debian Bug report #1064715, regarding zabbix: FTBFS: make[4]: *** [Makefile:623: zabbix.com/cmd/zabbix_agent2] Error 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.) -- 1064715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zabbix Version: 1:6.0.25+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/debian/tmp-build-AGENT2/src/go' > CGO_CFLAGS="-I/usr/include " CGO_LDFLAGS="-L/usr/lib -Wl,--start-group > > /<>/debian/tmp-build-AGENT2/src/zabbix_agent/logfiles/libzbxlogfiles.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxcomms/libzbxcomms.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxcommon/libzbxcommon.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxcrypto/libzbxcrypto.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsys/libzbxsys.a > /<>/debian/tmp-build-AGENT2/src/libs/zbxprof/libzbxprof.a > /<>/debian/tmp-build-AGENT2/src/libs/zbxnix/libzbxnix.a > /<>/debian/tmp-build-AGENT2/src/libs/zbxconf/libzbxconf.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxhttp/libzbxhttp.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxcompress/libzbxcompress.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxregexp/libzbxregexp.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/libzbxagent2sysinfo.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/common/libcommonsysinfo.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/simple/libsimplesysinfo.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/linux/libspechostnamesysinfo.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/linux/libspecsysinfo.a > > /<>/debian/tmp-build-AGENT2/src/libs/zbxexec/libzbxexec.a > /<>/debian/tmp-build-AGENT2/src/libs/zbxalgo/libzbxalgo.a > /<>/debian/tmp-build-AGENT2/src/libs/zbxjson/libzbxjson.a > -lm -lmodbus -lpcre2-8-lz -lpthread -lssl -lcrypto > -Wl,--end-group" go build -v -tags="pcre2" -ldflags="-X > 'zabbix.com/pkg/version.compileDate=`date +"%b %_d %Y"`' -X > zabbix.com/pkg/version.compileTime=`date +%H:%M:%S` -X > zabbix.com/pkg/version.compileOs=`go env GOOS` -X > zabbix.com/pkg/version.compileArch=`go env GOARCH` -X > main.confDefault=/etc/zabbix/zabbix_agent2.conf -X > main.applicationName=zabbix_agent2" -o bin zabbix.com/cmd/zabbix_agent2 > go build -v -ldflags="-X 'zabbix.com/pkg/version.compileDate=`date +"%b %_d > %Y"`' -X zabbix.com/pkg/version.compileTime=`date +%H:%M:%S` -X > zabbix.com/pkg/version.compileOs=`go env GOOS` -X > zabbix.com/pkg/version.compileArch=`go env GOARCH` -X > main.applicationName=zabbix_web_service" -o bin > zabbix.com/cmd/zabbix_web_service > internal/goarch > internal/coverage/rtcov > internal/godebugs > internal/goexperiment > internal/unsafeheader > internal/goos > runtime/internal/atomic > runtime/internal/syscall > internal/abi > internal/cpu > runtime/internal/math > runtime/internal/sys > internal/race > sync/atomic > internal/itoa > unicode/utf8 > container/list > unicode > runtime/internal/syscall > encoding > math/bits > unicode/utf8 > runtime/internal/atomic > sync/atomic > math/bits > crypto/internal/alias > unicode > internal/abi > internal/cpu > crypto/subtle > internal/bytealg > crypto/internal/boring/sig > log/internal > internal/nettrace > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > unicode/utf16 > internal/nettrace > crypto/subtle > crypto/internal/boring/sig > vendor/golang.org/x/crypto/internal/alias > github.com/chromedp/chromedp/device > math > github.com/gobwas/pool/internal/pmath > golang.org/x/net/internal/iana > golang.org/x/net/html/atom > golang.org/x/text/encoding/internal/identifier > golang.org/x/text/internal/utf8internal > golang.org/x/xerrors/internal > internal/bytealg > math > runtime > runtime > sync > internal/reflectlite > internal/reflectlite > sync > internal/singleflight > internal/bisect > zabbix.com/internal/monitor > internal/testlog > internal/bisect > internal/singleflight > github.com/josharian/intern >
Bug#739853: marked as done (bash: "hash -l" output not always reusable for input)
Your message dated Fri, 26 Apr 2024 12:23:22 +0200 with message-id <2491a6b0-b0d9-4dee-9b8c-78ea3d374...@svario.it> and subject line Re: Bug#739853: bash: "hash -l" output not always reusable for input has caused the Debian Bug report #739853, regarding bash: "hash -l" output not always reusable for input 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.) -- 739853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bash Version: 4.2+dfsg-0.1 Severity: minor Output from hash -l is not properly quoted, and might lead to surprises when a file name contains whitespace characters: $ add2path=`mktemp -d /tmp/XX` $ export PATH=$PATH:$add2path $ cp -p /bin/true "$add2path/t rue" $ "t rue" $ hash -l | tee $add2path/script builtin hash -p /tmp/PukY3C/t rue t rue builtin hash -p /bin/cp cp $ . $add2path/script $ hash -l builtin hash -p /tmp/C3TzlZ/t rue builtin hash -p /tmp/C3TzlZ/t rue t rue builtin hash -p /bin/cp cp builtin hash -p /tmp/C3TzlZ/t t Best regards, g -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.1wheezy4 ii dash 0.5.7-3 ii debianutils 4.3.2 ii libc62.13-38+deb7u1 ii libtinfo55.9-10 Versions of packages bash recommends: pn bash-completion Versions of packages bash suggests: pn bash-doc -- no debconf information --- End Message --- --- Begin Message --- Version: 5.0-6 On Sun, 23 Feb 2014 10:58:32 +0100 g1 wrote: Output from hash -l is not properly quoted, and might lead to surprises when a file name contains whitespace characters: $ add2path=`mktemp -d /tmp/XX` $ export PATH=$PATH:$add2path $ cp -p /bin/true "$add2path/t rue" $ "t rue" $ hash -l | tee $add2path/script builtin hash -p /tmp/PukY3C/t rue t rue builtin hash -p /bin/cp cp Hi, this issue does not seem to affect version 5.0-6 and later of bash. $ add2path=`mktemp -d /tmp/XX` $ export PATH=$PATH:$add2path $ cp -p /bin/true "$add2path/t rue" $ "t rue" $ hash -l builtin hash -p /usr/bin/cp cp builtin hash -p '/tmp/1Veh4C/t rue' 't rue' Please reopen this bug if you can still reproduce this issue. Regards, -- Gioele Barabucci--- End Message ---
Bug#1068490: marked as done (netperf: Netserver remove /dev/null in some cases, breaking many things)
Your message dated Fri, 26 Apr 2024 09:24:46 +
with message-id
and subject line Bug#1068490: fixed in netperf 2.7.0-0.3
has caused the Debian Bug report #1068490,
regarding netperf: Netserver remove /dev/null in some cases, breaking many
things
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.)
--
1068490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netperf
Version: 2.7.0-0.2
Severity: critical
Tags: patch upstream
Justification: breaks unrelated software
X-Debbugs-Cc: tourrilhes@gmail.com
This bug is hard to reproduce, as the condition that lead to
Netserver deleting /dev/null are quite mysterious. I was getting my
/dev/null removed over the years at very rare occurences, until
I managed to track it down to Netserver.
The issue is not present in the tarball for version 2.7.0. It
was introduced in patch :
02018-02-07T17:21:57-08:00~5380b1f.patch
In particular, this line :
+FileName = NETPERF_NULL;
This patch is part of the Netperf GitHub, which is why I added
the upstream tag.
I will report this bug upstream, unfortunately I don't expect
much action :-(
A quick look at the source code show that the code is wrong in
very obvious way. The fix is quite simple and obvious, and I provide
a patch (included below).
Note that my patch replace
11_no_change_perms_on_dev-null.patch, so please remove that patch
before applying mine.
Thanks in advance !
Jean
-- System Information:
Debian Release: 11.9
APT prefers oldstable-security
APT policy: (500, 'oldstable-security'), (500, 'oldstable-proposed-updates'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-28-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
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 /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages netperf depends on:
ii libc6 2.31-13+deb11u8
netperf recommends no packages.
netperf suggests no packages.
-- no debconf information
diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
#if !defined(WIN32)
struct stat buf;
- if (stat(FileName,)== 0) {
+ if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
if (buf.st_size == 0)
unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
if (where != NULL) fflush(where);
if (suppress_debug) {
strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
where = fopen(FileName, "w");
} else {
int fd;
@@ -260,7 +261,8 @@ open_debug_file()
#if !defined(WIN32)
- chmod(FileName,0644);
+ if (! suppress_debug)
+chmod(FileName,0644);
/* redirect stdin to "/dev/null" */
rd_null_fp = fopen(NETPERF_NULL,"r");
diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
#if !defined(WIN32)
struct stat buf;
- if (stat(FileName,)== 0) {
+ if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
if (buf.st_size == 0)
unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
if (where != NULL) fflush(where);
if (suppress_debug) {
strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
where = fopen(FileName, "w");
} else {
int fd;
@@ -260,7 +261,8 @@ open_debug_file()
#if !defined(WIN32)
- chmod(FileName,0644);
+ if (! suppress_debug)
+chmod(FileName,0644);
/* redirect stdin to "/dev/null" */
rd_null_fp = fopen(NETPERF_NULL,"r");
diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
#if !defined(WIN32)
struct stat buf;
- if (stat(FileName,)== 0) {
+ if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
if (buf.st_size == 0)
unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
if (where != NULL) fflush(where);
if (suppress_debug) {
strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
where = fopen(FileName, "w");
} else {
int fd;
@@ -260,7
Bug#732056: marked as done (netperf: incorrect check against NETSERVER_ENABLE in /etc/init.d/netperf)
Your message dated Fri, 26 Apr 2024 09:24:46 + with message-id and subject line Bug#732056: fixed in netperf 2.7.0-0.3 has caused the Debian Bug report #732056, regarding netperf: incorrect check against NETSERVER_ENABLE in /etc/init.d/netperf 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.) -- 732056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netperf Version: 2.6.0-2 Severity: normal Tags: patch Dear Maintainer, In the init.d script, the '$' character is missing in front of the NETSERVER_ENABLE variable. As a consequence, this variable is not expanded and the check is never performed. Please, apply the attached patch. Regards, Simon -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (1001, 'unstable'), (600, 'experimental'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages netperf depends on: ii libc6 2.17-97 netperf recommends no packages. netperf suggests no packages. -- Configuration Files: /etc/default/netperf changed [not included] /etc/init.d/netperf changed [not included] -- no debconf information >From 4f58328e01e2766d3411acc3f7ed7ac4ac4963cd Mon Sep 17 00:00:00 2001 From: Simon Guinot Date: Fri, 13 Dec 2013 11:31:02 +0100 Subject: [PATCH] Fix NETSERVER_ENABLE check in init.d script This patch fixes the NETSERVER_ENABLE variable expansion by adding the missing leading character '$'. Signed-off-by: Simon Guinot --- debian/init.d | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/init.d b/debian/init.d index 4744a73..bd80b05 100644 --- a/debian/init.d +++ b/debian/init.d @@ -31,7 +31,7 @@ test -f $DAEMON || exit 0 case "$1" in start) - if [ x"NETSERVER_ENABLE" = xno ] + if [ x"$NETSERVER_ENABLE" = xno ] then log_warning_msg "netperf daemon not enabled in /etc/default/netperf, not starting..." return 0 -- 1.8.5.1 >From 4f58328e01e2766d3411acc3f7ed7ac4ac4963cd Mon Sep 17 00:00:00 2001 From: Simon Guinot Date: Fri, 13 Dec 2013 11:31:02 +0100 Subject: [PATCH] Fix NETSERVER_ENABLE check in init.d script This patch fixes the NETSERVER_ENABLE variable expansion by adding the missing leading character '$'. Signed-off-by: Simon Guinot --- debian/init.d | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/init.d b/debian/init.d index 4744a73..bd80b05 100644 --- a/debian/init.d +++ b/debian/init.d @@ -31,7 +31,7 @@ test -f $DAEMON || exit 0 case "$1" in start) - if [ x"NETSERVER_ENABLE" = xno ] + if [ x"$NETSERVER_ENABLE" = xno ] then log_warning_msg "netperf daemon not enabled in /etc/default/netperf, not starting..." return 0 -- 1.8.5.1 --- End Message --- --- Begin Message --- Source: netperf Source-Version: 2.7.0-0.3 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of netperf, 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 732...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated netperf 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: Fri, 26 Apr 2024 11:05:37 +0200 Source: netperf Architecture: source Version: 2.7.0-0.3 Distribution: unstable Urgency: medium Maintainer: Erik Wenzel Changed-By: Andreas Beckmann Closes: 732056 1068490 Changes: netperf (2.7.0-0.3) unstable; urgency=medium . [ Andreas Beckmann ] * Non-maintainer upload. * Declare Rules-Requires-Root: no. . [ Simon Guinot ] * Fix NETSERVER_ENABLE check in init.d script. (Closes: #732056) . [ Jean Tourrilhes ] * Fix netserver removing /dev/null in some cases. (Closes: #1068490) Checksums-Sha1: 1528ebd93d42ca3b7e608f2b31ae6b24b62c57db 1904 netperf_2.7.0-0.3.dsc a1d34443dafb00ab2e1e75663822e2ac8235d32c 19508 netperf_2.7.0-0.3.debian.tar.xz a49ee558d0038e2ad4edebd67d81125fcaa26767 7343 netperf_2.7.0-0.3_source.buildinfo
Processed: Re: reassign 1067188 to src:gcc-mingw-w64, found 1067188 in 25.2, fixed 1067188 in 26.1, affects 1067188
Processing commands for cont...@bugs.debian.org: > close 1067188 Bug #1067188 [src:gcc-mingw-w64] gdb-mingw-w64: FTBFS in trixie Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065454: marked as done (libcanberra: Correct dpkg-dev build dependency)
Your message dated Fri, 26 Apr 2024 09:10:11 + with message-id and subject line Bug#1065454: fixed in libcanberra 0.30-13 has caused the Debian Bug report #1065454, regarding libcanberra: Correct dpkg-dev build dependency 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.) -- 1065454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcanberra Version: 0.30-10ubuntu4 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libcanberra-0.30/debian/changelog libcanberra-0.30/debian/changelog --- libcanberra-0.30/debian/changelog 2024-03-04 23:41:54.0 +1300 +++ libcanberra-0.30/debian/changelog 2024-03-05 10:55:23.0 +1300 @@ -1,3 +1,10 @@ +libcanberra (0.30-12.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:55:23 +1300 + libcanberra (0.30-12.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libcanberra-0.30/debian/control libcanberra-0.30/debian/control --- libcanberra-0.30/debian/control 2024-03-04 23:41:54.0 +1300 +++ libcanberra-0.30/debian/control 2024-03-05 10:55:23.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Josselin Mouette , Laurent Bigonville , Marco Trevisan (Treviño) , Sjoerd Simons -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), libltdl-dev | libltdl7-dev (>= 2.2.6), libasound2-dev [linux-any], --- End Message --- --- Begin Message --- Source: libcanberra Source-Version: 0.30-13 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of libcanberra, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated libcanberra package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2024 21:18:44 +0200 Source: libcanberra Binary: gnome-session-canberra gnome-session-canberra-dbgsym libcanberra-dev libcanberra-doc libcanberra-gstreamer libcanberra-gstreamer-dbgsym libcanberra-gtk-common-dev libcanberra-gtk3-0 libcanberra-gtk3-0-dbgsym libcanberra-gtk3-dev libcanberra-gtk3-module libcanberra-gtk3-module-dbgsym libcanberra-pulse libcanberra-pulse-dbgsym libcanberra0 libcanberra0-dbgsym Architecture: source amd64 all Version: 0.30-13 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Michael Biebl Description: gnome-session-canberra - GNOME session log in and log out sound events libcanberra-dev - simple interface for playing event sounds (development files) libcanberra-doc - simple abstract interface for playing event sounds - doc libcanberra-gstreamer - GStreamer backend for libcanberra libcanberra-gtk-common-dev - simple interface for playing event sounds (GTK+ shared developmen libcanberra-gtk3-0 - GTK+ 3.0 helper for playing widget event sounds with libcanberra libcanberra-gtk3-dev - simple interface for playing event sounds (GTK+ 3 development fil
Bug#1068936: marked as done (libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0)
Your message dated Fri, 26 Apr 2024 09:10:11 + with message-id and subject line Bug#1068936: fixed in libcanberra 0.30-13 has caused the Debian Bug report #1068936, regarding libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0 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.) -- 1068936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcanberra-gtk3-module Version: 0.30-12 Severity: serious X-Debbugs-Cc: sramac...@debian.org This package has a hard-coded dependency on libgtk-3-0. Since libgtk-3-0 was renamed for the time_t transition, the dependency needs to be updated or simply removed. Even oldstable has a recent enough version of GTK 3. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libcanberra Source-Version: 0.30-13 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of libcanberra, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated libcanberra package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2024 21:18:44 +0200 Source: libcanberra Binary: gnome-session-canberra gnome-session-canberra-dbgsym libcanberra-dev libcanberra-doc libcanberra-gstreamer libcanberra-gstreamer-dbgsym libcanberra-gtk-common-dev libcanberra-gtk3-0 libcanberra-gtk3-0-dbgsym libcanberra-gtk3-dev libcanberra-gtk3-module libcanberra-gtk3-module-dbgsym libcanberra-pulse libcanberra-pulse-dbgsym libcanberra0 libcanberra0-dbgsym Architecture: source amd64 all Version: 0.30-13 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Michael Biebl Description: gnome-session-canberra - GNOME session log in and log out sound events libcanberra-dev - simple interface for playing event sounds (development files) libcanberra-doc - simple abstract interface for playing event sounds - doc libcanberra-gstreamer - GStreamer backend for libcanberra libcanberra-gtk-common-dev - simple interface for playing event sounds (GTK+ shared developmen libcanberra-gtk3-0 - GTK+ 3.0 helper for playing widget event sounds with libcanberra libcanberra-gtk3-dev - simple interface for playing event sounds (GTK+ 3 development fil libcanberra-gtk3-module - translates GTK3 widgets signals to event sounds libcanberra-pulse - PulseAudio backend for libcanberra libcanberra0 - simple abstract interface for playing event sounds Closes: 1065454 1068936 Changes: libcanberra (0.30-13) unstable; urgency=medium . * Team upload * Revert time_t related changes. Those changes appear to not be necessary. time_t is not exposed in the API/ABI and a-c-c did not detect any issues. This reverts commit 04a6b5de59db6a0832b1d31f287bf7afa76e11c3. (Closes: #1065454) * Drop hard-coded dependency on libgtk-3-0 (>= 3.2.2-3) (Closes: #1068936) * Add versioned Provides for libcanberra0t64 and libcanberra-gtk3-0t64. This simplifies compatibility with Ubuntu 24.04. Thanks to Jeremy Bicha * Bump Standards-Version to 4.7.0 Checksums-Sha1: 21fecf599971d299f4a7f867ec4561ec625d2f30 2970 libcanberra_0.30-13.dsc b6402d7337f7d3e25cf45e33a3c151f03494fe09 14616 libcanberra_0.30-13.debian.tar.xz 96ecc3d5a904a034bec77fd9d21a2f524147e63a 8252 gnome-session-canberra-dbgsym_0.30-13_amd64.deb b897e4438c8936f88c6aa6d6d947c4a190b609ab 8208 gnome-session-canberra_0.30-13_amd64.deb 6f55851ca1808350e227e99dcd4d555fa5e4bc27 8488 libcanberra-dev_0.30-13_amd64.deb 9bcbac09b1cf8ae7f7af897316c2c26b86bb83aa 21056 libcanberra-doc_0.30-13_all.deb 64ff7efe2ded964d2a6287c2e88a3730b5cfaa64 24956 libcanberra-gstreamer-dbgsym_0.30-13_amd64.deb b888a11e306fb4a546241722911eab5b1d569907 9696 libcanberra-gstreamer_0.30-13_amd64.deb 302a4ef5b4cb203386cddfdb78cdb6e69599513d 4388 libcanberra-gtk-common-dev_0.30-13_all.deb f0f7b1304a288dd65b96d4607b444ab7c3544086 20508 libcanberra-gtk3-0-dbgsym_0.30-13_amd64.deb 6b175e1635fb1711b5d8953e42cd6b8cd56d4b38 9456
Processed: closing 591321
Processing commands for cont...@bugs.debian.org: > close 591321 Bug #591321 [bash] error: "value too great for base" while comparing numbers more than 7 with leading zeros Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 591321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 535009
Processing commands for cont...@bugs.debian.org: > close 535009 Bug #535009 [bash] bash: inconsistent calculation of remainders when dividend begins with 0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 535009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#506104: marked as done (bash: Problem with Parameter Expansion ${param//patt/str} if str contains a single quote ('))
Your message dated Fri, 26 Apr 2024 12:10:30 +0200
with message-id <11d46d97-7742-40d1-aaa5-85a724aaf...@svario.it>
and subject line Re: Bug#506104: bash: Problem with Parameter Expansion
${param//patt/str} if str contains a single quote (')
has caused the Debian Bug report #506104,
regarding bash: Problem with Parameter Expansion ${param//patt/str} if str
contains a single quote (')
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.)
--
506104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 2.05b-26
Severity: normal
Hi,
while trying to escape single quotes in a string, I discovered the following
behavior:
$ x="a'b'c"; echo "${x//\'/\'}"
a\'b\'c
When I leave off the last escaping backslash, the command line parser thinks
the line isn't complete:
$ x="a'b'c"; echo "${x//\'/'}"
>
Entering '}" there gives:
a'}"
'b'}"
'c
So, trying two quotes instead:
$ x="a'b'c"; echo "${x//\'/''}"
a''b''c
I haven't found a method to substitute a pattern with a single quote (not
using external commands of course).
I get the identical behavior if I do ${param/patt/str} instead of
${param//patt/str} and also with Etch's version of batch (reportbug's
info snippet added below the Sarge version's).
The behavior I *expected* is the following:
$ x="a'b'c"; echo "${x//\'/\'\\\'\'}"
a'\''b'\''c
Greetings,
Mike Dornberger
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.26-wolfden.2
Locale: LANG=C, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Versions of packages bash depends on:
ii base-files3.1.2 Debian base system miscellaneous f
ii libc6 2.3.2.ds1-22sarge6 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii passwd1:4.0.3-31sarge9 change and administer password and
-- no debconf information
Package: bash
Version: 3.1dfsg-8
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages bash depends on:
ii base-files 4 Debian base system miscellaneous f
ii debianutils2.17 Miscellaneous utilities specific t
ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries
ii libncurses55.5-5 Shared libraries for terminal hand
bash recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.0-6
On Tue, 18 Nov 2008 13:28:37 +0100 Mike Dornberger
wrote:
while trying to escape single quotes in a string, I discovered the following
behavior:
$ x="a'b'c"; echo "${x//\'/\'}"
a\'b\'c
[...]
I haven't found a method to substitute a pattern with a single quote (not
using external commands of course).
Hi,
this issue does not seem to affect version 5.0-6 and later of bash.
$ x="a'b'c"; echo "${x//\'/\'}"
a'b'c
Please reopen this bug if you can still reproduce this issue.
Regards,
--
Gioele Barabucci--- End Message ---
Bug#1068111: marked as done (wireshark: CVE-2024-2955)
Your message dated Fri, 26 Apr 2024 16:27:35 + with message-id and subject line Bug#1068111: fixed in wireshark 4.2.4-1 has caused the Debian Bug report #1068111, regarding wireshark: CVE-2024-2955 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.) -- 1068111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wireshark Version: 4.2.2-1 Severity: important Tags: security upstream Forwarded: https://gitlab.com/wireshark/wireshark/-/issues/19695 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for wireshark. CVE-2024-2955[0]: | T.38 dissector crash in Wireshark 4.2.0 to 4.0.3 and 4.0.0 to 4.0.13 | allows denial of service via packet injection or crafted capture | file 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-2024-2955 https://www.cve.org/CVERecord?id=CVE-2024-2955 [1] https://www.wireshark.org/security/wnpa-sec-2024-06.html [2] https://gitlab.com/wireshark/wireshark/-/issues/19695 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: wireshark Source-Version: 4.2.4-1 Done: Balint Reczey We believe that the bug you reported is fixed in the latest version of wireshark, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated wireshark package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 11:30:27 +0200 Source: wireshark Built-For-Profiles: noudeb Architecture: source Version: 4.2.4-1 Distribution: unstable Urgency: medium Maintainer: Balint Reczey Changed-By: Balint Reczey Closes: 1060670 1068111 1068410 Changes: wireshark (4.2.4-1) unstable; urgency=medium . [ Martin Bagge ] * Update Swedish debconf translation (Closes: #1060670) . [ Balint Reczey ] * debian/control: Drop comment about libgnutls28-dev's version's GPL compatibility. All supported releases already have the GPL2+ compatible libgnutls28-dev version. * Generate debian/control from control.in based on the target release * ACK NMU * Drop t64-related changes for backports * debian/watch: Update handling GitLab's page to make uscan work again * New upstream version 4.2.4: - security fixes (Closes: #1068111): - T.38 dissector crash (CVE-2024-2955) * Update symbols for libwireshark17t64 * libwireshark-dev: Ship missing dfilter-loc.h. Also check if dfilter.h is usable, too, in debian/headers-check.c. (Closes: #1068410) * Cherry-pick upstream patch to fix Lua 5.2 integration on 32 bit systems Checksums-Sha1: feed70ac622fa039472356daa96916fd80b366c3 3462 wireshark_4.2.4-1.dsc df769582e794c46b3d445a01083c6ba1990e9566 48477151 wireshark_4.2.4.orig.tar.bz2 3574e559f5db752407a39054329b9508a23f78b7 87676 wireshark_4.2.4-1.debian.tar.xz 05dcbfbd24d1c50e52a89027bc45b44f7792397b 20764 wireshark_4.2.4-1_source.buildinfo Checksums-Sha256: 26ae62d8086b10778fd61ff0b1f3a6fea1982baa505c01de8dd1a05f9763d482 3462 wireshark_4.2.4-1.dsc 71fef592077d09d52ece21543c3fecb162b6701fdcddcdcb37a7f146f1dab9c6 48477151 wireshark_4.2.4.orig.tar.bz2 bb87346e6a88d42b6f5e7e9e8b5143f82f6ce7abbe6a12f9a4a5df3551b13bf5 87676 wireshark_4.2.4-1.debian.tar.xz 6dd6bb52f92ac9d19084b2af448dff85e1484cde913dcf13c2e4c735326f841c 20764 wireshark_4.2.4-1_source.buildinfo Files: fd6d95a2936b2be0fb3c49debf94af15 3462 net optional wireshark_4.2.4-1.dsc 5aa2f58a617b7045dfd64102be541f11 48477151 net optional wireshark_4.2.4.orig.tar.bz2 6206be4d6ad6f0c54cb9510299139018 87676 net optional wireshark_4.2.4-1.debian.tar.xz b915154f2b6a30dd49788b5a77104483 20764 net optional wireshark_4.2.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAmYrpZMACgkQg6KBkWsl
Bug#1068410: marked as done (libwireshark-dev: Package is missing mandatory "dfilter-loc.h")
Your message dated Fri, 26 Apr 2024 16:27:35 + with message-id and subject line Bug#1068410: fixed in wireshark 4.2.4-1 has caused the Debian Bug report #1068410, regarding libwireshark-dev: Package is missing mandatory "dfilter-loc.h" 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.) -- 1068410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwireshark-dev Version: 4.2.2-1.1+b1 Severity: important X-Debbugs-Cc: contact.thors...@gmail.com Dear Maintainer, * What led up to the situation? Trying to build an external package dissector. * What exactly did you do (or not do) that was effective (or ineffective)? Including /usr/include/wireshark/epan/plugin_if.h in the source to build a dissector. * What was the outcome of this action? In file included from /usr/include/wireshark/cfile.h:17, from /usr/include/wireshark/epan/plugin_if.h:26, from packet-trdp_spy.c:52: /usr/include/wireshark/epan/dfilter/dfilter.h:15:10: fatal error: dfilter-loc.h: file missing * What outcome did you expect instead? successful build -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwireshark-dev depends on: ii libwireshark17t64 4.2.2-1.1+b1 ii libwiretap-dev 4.2.2-1.1+b1 ii libwsutil-dev 4.2.2-1.1+b1 libwireshark-dev recommends no packages. libwireshark-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: wireshark Source-Version: 4.2.4-1 Done: Balint Reczey We believe that the bug you reported is fixed in the latest version of wireshark, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated wireshark package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 11:30:27 +0200 Source: wireshark Built-For-Profiles: noudeb Architecture: source Version: 4.2.4-1 Distribution: unstable Urgency: medium Maintainer: Balint Reczey Changed-By: Balint Reczey Closes: 1060670 1068111 1068410 Changes: wireshark (4.2.4-1) unstable; urgency=medium . [ Martin Bagge ] * Update Swedish debconf translation (Closes: #1060670) . [ Balint Reczey ] * debian/control: Drop comment about libgnutls28-dev's version's GPL compatibility. All supported releases already have the GPL2+ compatible libgnutls28-dev version. * Generate debian/control from control.in based on the target release * ACK NMU * Drop t64-related changes for backports * debian/watch: Update handling GitLab's page to make uscan work again * New upstream version 4.2.4: - security fixes (Closes: #1068111): - T.38 dissector crash (CVE-2024-2955) * Update symbols for libwireshark17t64 * libwireshark-dev: Ship missing dfilter-loc.h. Also check if dfilter.h is usable, too, in debian/headers-check.c. (Closes: #1068410) * Cherry-pick upstream patch to fix Lua 5.2 integration on 32 bit systems Checksums-Sha1: feed70ac622fa039472356daa96916fd80b366c3 3462 wireshark_4.2.4-1.dsc df769582e794c46b3d445a01083c6ba1990e9566 48477151 wireshark_4.2.4.orig.tar.bz2 3574e559f5db752407a39054329b9508a23f78b7 87676 wireshark_4.2.4-1.debian.tar.xz 05dcbfbd24d1c50e52a89027bc45b44f7792397b 20764 wireshark_4.2.4-1_source.buildinfo Checksums-Sha256: 26ae62d8086b10778fd61ff0b1f3a6fea1982baa505c01de8dd1a05f9763d482 3462 wireshark_4.2.4-1.dsc 71fef592077d09d52ece21543c3fecb162b6701fdcddcdcb37a7f146f1dab9c6 48477151 wireshark_4.2.4.orig.tar.bz2
Bug#1060670: marked as done ([INTL:sv] Swedish strings for wireshark debconf)
Your message dated Fri, 26 Apr 2024 16:27:35 + with message-id and subject line Bug#1060670: fixed in wireshark 4.2.4-1 has caused the Debian Bug report #1060670, regarding [INTL:sv] Swedish strings for wireshark debconf 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.) -- 1060670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: wireshark severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother# Translation of wireshark debconf template to Swedish # Copyright (C) 2024 Martin Bagge # This file is distributed under the same license as the wireshark package. # # Martin Ågren , 2009, 2010. # Martin Bagge , 2024 msgid "" msgstr "" "Project-Id-Version: wireshark_sv\n" "Report-Msgid-Bugs-To: wiresh...@packages.debian.org\n" "POT-Creation-Date: 2019-09-13 00:04+0200\n" "PO-Revision-Date: 2024-01-12 13:57+0100\n" "Last-Translator: Martin Bagge \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.4\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Should non-superusers be able to capture packets?" msgstr "Ska icke-superanvändare kunna fånga paket?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "Dumpcap can be installed in a way that allows members of the \"wireshark\" " "system group to capture packets. This is recommended over the alternative of " "running Wireshark/Tshark directly as root, because less of the code will run " "with elevated privileges." msgstr "" "Dumpcap kan installeras på ett sätt som tillåter medlemmar i systemgruppen " "\"wireshark\" att fånga paket. Detta rekommenderas framför alternativet, att " "köra Wireshark/Tshark direkt som root, eftersom en mindre del av koden " "kommer köras med utökade rättigheter." #. Type: boolean #. Description #: ../templates:2001 msgid "" "For more detailed information please see /usr/share/doc/wireshark-common/" "README.Debian.gz once the package is installed." msgstr "" "Se /usr/share/doc/wireshark-common/README.Debian.gz för mer detaljerad " "information." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Enabling this feature may be a security risk, so it is disabled by default. " "If in doubt, it is suggested to leave it disabled." msgstr "" "Att aktivera denna funktion kan vara en säkerhetsrisk, så den är avaktiverad " "som standard. Vid tvivel rekommenderas att den lämnas avaktiverad." #. Type: error #. Description #: ../templates:3001 msgid "Creating the wireshark system group failed" msgstr "Kunde inte skapa systemgruppen wireshark" #. Type: error #. Description #: ../templates:3001 msgid "" "The wireshark group does not exist, and creating it failed, so Wireshark " "cannot be configured to capture traffic as an unprivileged user." msgstr "" "Gruppen wireshark finns inte och det gick inte att skapa den. Detta leder " "till att Wireshark inte kan ställas in för att fånga trafik för vanliga " "användare." #. Type: error #. Description #: ../templates:3001 msgid "" "Please create the wireshark system group and try configuring wireshark-" "common again." msgstr "" "Skapa systemgruppen wireshark och försök göra inställningar för wireshark-" "common igen." #. Type: error #. Description #: ../templates:4001 msgid "The wireshark group is a system group" msgstr "Gruppen wireshark är en systemgrupp" #. Type: error #. Description #: ../templates:4001 msgid "" "The wireshark group exists as a user group, but the preferred configuration " "is for it to be created as a system group." msgstr "" "Gruppen wireshark finns redan men är en användargrupp. Att ha gruppen som en " "systemgrupp är att föredra." #. Type: error #. Description #: ../templates:4001 msgid "" "As a result, purging wireshark-common will not remove the wireshark group, " "but everything else should work properly." msgstr "" "Om wireshark-common raderas helt och hållet så kommer gruppen wireshark inte " "tas bort, allt annat fungerar dock som vanligt." #. Type: error #. Description #: ../templates:5001 msgid "Setting capabilities for dumpcap failed" msgstr "Kunde inte aktivera rätt inställningar för dumpcap" #. Type: error #. Description #: ../templates:5001 msgid "" "The attempt to use Linux capabilities to grant packet-capturing privileges " "to the dumpcap binary failed. Instead, it has had the set-user-id bit set." msgstr "" "Försökte
Bug#979617: marked as done (tcplay: new upstream version 3.3 (includes VeraCrypt support))
Your message dated Fri, 26 Apr 2024 17:23:04 + with message-id and subject line Bug#979617: fixed in tcplay 3.3-1 has caused the Debian Bug report #979617, regarding tcplay: new upstream version 3.3 (includes VeraCrypt support) 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.) -- 979617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tcplay Version: 1.1-6 Severity: normal Dear Maintainer, It seems that VeraCrypt is supported in 3.0 in the upstream of tcplay. https://github.com/bwalex/tc-play/blob/master/CHANGELOG#L15 I hope it will be updated so that VeraCrypt can be used. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, arm64 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tcplay depends on: ii libc6 2.31-9 ii libdevmapper1.02.1 2:1.02.173-1 ii libgcrypt20 1.8.7-2 ii libgpg-error0 1.38-2 ii libuuid12.36.1-4 tcplay recommends no packages. tcplay suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tcplay Source-Version: 3.3-1 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of tcplay, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated tcplay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Apr 2024 18:51:43 +0200 Source: tcplay Architecture: source Version: 3.3-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 979617 Changes: tcplay (3.3-1) unstable; urgency=medium . [ Daniel Kahn Gillmor ] * Cleaning up packaging, track with revision control on Salsa * New upstream release, includes VeraCrypt support (closes: #979617) * Track debian packaging on salsa * wrap-and-sort -ast * d/watch: modernize, use mode=git * move to debhelper 13 * Rules-Requires-Root: no * Build-Depend on pkgconf instead of pkg-config * Ship all manpages * debian/rules: simplify * d/patches: refresh, drop those already upstream, clear out cruft, use gbp-pq formatting * clean up manpages, forwarding upstream * Update and differentiate package descriptions * Standards-Version: bump to 4.7.0 (no changes needed) . [ Laszlo Boszormenyi (GCS) ] * Multiarchify the library package. Checksums-Sha1: 643c0b76ae60295c14156b92d5e5b8aa49cd8f62 2004 tcplay_3.3-1.dsc 0ebad8c87b44c8bf4a73344d786d27e6ee0f3499 2556732 tcplay_3.3.orig.tar.xz 1d17737e8051ddbf2b7e5cca094e3daa37b9886d 6536 tcplay_3.3-1.debian.tar.xz Checksums-Sha256: 7b61e11cd99d8ef38660baad30e367e9c9302ac7d71fa9d2fb2294eaff33c306 2004 tcplay_3.3-1.dsc 49e83f62b953ea6844d7aba33e796ba030ad24db204613e79682348a1414cfce 2556732 tcplay_3.3.orig.tar.xz 62405e2794f0a73480ee41520d9a476bf806b48024aef6f090a355840183 6536 tcplay_3.3-1.debian.tar.xz Files: 39d690db84d09c74b697d528d8f27b3d 2004 admin optional tcplay_3.3-1.dsc 1160226f1c57340cbf20699d213cc21b 2556732 admin optional tcplay_3.3.orig.tar.xz caae1eafc5e3a1f13e4f27ae88b65f7c 6536 admin optional tcplay_3.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmYqkPcACgkQ3OMQ54ZM yL/dOA/7BlmNXKuCD+gcTsPk+9+0sNHN1+BFVatE8DxV+/SwJzUbnKJ3/7+DaenS kSSbHgZKoUEKCiE6tAtSLLT4O8wfCzzzZ7F5IaGlA8ekTHow6pi8mYhu9yb7MlyJ tSf2a2gaLMt5By8Un63X/2FOU9i9y1JjmC8ZmFQQYirm9XoLc6O/rxfzld14mER+ NXAZZ6bjfAx+L4VJttUmjuc5JaV5RybbsDuRVD/MoBi3xKnWahy7Kf+SsPwwCS3P
Bug#1069756: marked as done (readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean)
Your message dated Fri, 26 Apr 2024 16:25:48 + with message-id and subject line Bug#1069756: fixed in readability 0.8.1+dfsg1-4 has caused the Debian Bug report #1069756, regarding readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean 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.) -- 1069756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: readability Version: 0.8.1+dfsg1-3 Severity: serious Tags: ftbfs Justification: ftbfs Dear Maintainer, Attempt to run readability tests at build time results in the following error: == ERROR: readability (unittest.loader._FailedTest.readability) -- ImportError: Failed to import test module: readability Traceback (most recent call last): File "/usr/lib/python3.11/unittest/loader.py", line 452, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.11/unittest/loader.py", line 362, in _get_module_from_name __import__(name) File "/<>/.pybuild/cpython3_3.11/build/readability/__init__.py", line 3, in from .readability import Document File "/<>/.pybuild/cpython3_3.11/build/readability/readability.py", line 11, in from .cleaners import clean_attributes File "/<>/.pybuild/cpython3_3.11/build/readability/cleaners.py", line 3, in from lxml.html.clean import Cleaner File "/usr/lib/python3/dist-packages/lxml/html/clean.py", line 18, in raise ImportError( ImportError: lxml.html.clean module is now a separate project lxml_html_clean. Install lxml[html_clean] or lxml_html_clean directly. As far as I could witness, replacing the python3-lxml build dependency by python3-lxml-html-clean resolved the issue at least for the bulid time test. The package is subject to autodep8 python3 test, which raises that the binary package will also need it dependencies adjusted; this suggests the setup.py would probably need patching so this is addressed appropriately at a larger scale than Debian's. The missing dependency on python3-lxml-html-clean is also causing a regression in offpunk autopkgtest[1], although that could be easily worked around by pulling the missing dependency there. [1]: https://ci.debian.net/packages/o/offpunk/unstable/amd64/44684161/ Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/4, please excuse my verbosity `-on air: Mike Oldfield - Lion signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: readability Source-Version: 0.8.1+dfsg1-4 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of readability, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated readability 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: Fri, 26 Apr 2024 16:39:16 +0100 Source: readability Architecture: source Version: 0.8.1+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1069756 Changes: readability (0.8.1+dfsg1-4) unstable; urgency=medium . * Team upload. * Add (build-)dependency on python3-lxml-html-clean (closes: #1069756). Checksums-Sha1: 049a8bee60f5060f890863a598a85c7c8c695a20 2171 readability_0.8.1+dfsg1-4.dsc 529099c836815b069c5dd5e9b1945c23a91d0720 3640 readability_0.8.1+dfsg1-4.debian.tar.xz d4ed330a0e25aac01fb73894fa62715642c7234d 6805 readability_0.8.1+dfsg1-4_source.buildinfo Checksums-Sha256: b03cd45477452068afb0e51a5becc9c8f6989b42c75a5367963aa977ae784b5c 2171 readability_0.8.1+dfsg1-4.dsc
Processed: fish: loss of rendering (color) difference between valid and broken symbolic links
Processing control commands: > close 1064528 Bug #1064528 [fish] fish: loss of rendering (color) difference between valid and broken symbolic links Marked Bug as done -- 1064528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069842: marked as done (rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory)
Your message dated Fri, 26 Apr 2024 16:52:48 + with message-id and subject line Bug#1069842: fixed in r-base 4.4.0-2 has caused the Debian Bug report #1069842, regarding rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory 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.) -- 1069842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rjava Version: 1.0-11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem R dh_update_autotools_config -O--buildsystem=R cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary --buildsystem R dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-rjava/ -O--buildsystem=R I: R Package: rJava Version: 1.0-11 I: Building using R version 4.4.0-1 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Fri, 26 Jan 2024 11:10:09 -0600 mkdir -p /<>/debian/r-cran-rjava/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-cran-rjava/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 26 Jan 2024 11:10:09 -0600'" * installing *source* package ‘rJava’ ... files ‘configure’, ‘jri/tools/config.guess’, ‘jri/tools/config.sub’, ‘src/config.h.in’ have the wrong MD5 checksums ** using staged installation checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for sys/wait.h that is POSIX.1 compatible... yes checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for string.h... (cached) yes checking for sys/time.h... yes checking for unistd.h... (cached) yes checking for an ANSI C-conforming const... yes configure: checking whether gcc supports static inline... yes checking whether setjmp.h is POSIX.1 compatible... yes checking for gcc options needed to detect all undeclared functions... none needed checking whether sigsetjmp is declared... yes checking whether siglongjmp is declared... yes checking Java support in R... present: interpreter : '/usr/lib/jvm/default-java/bin/java' archiver: '/usr/lib/jvm/default-java/bin/jar' compiler: '/usr/lib/jvm/default-java/bin/javac' header prep.: '' cpp flags : '-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux' java libs : '-L/usr/lib/jvm/default-java/lib/server -ljvm' checking whether Java run-time works... yes checking whether -Xrs is supported... yes checking whether -Xrs will be used... yes checking whether JVM will be loaded dynamically... no checking whether JNI programs can be compiled... yes checking whether JNI programs run... yes checking JNI data types... ok checking whether JRI should be compiled (autodetect)... yes checking whether debugging output should be enabled... no checking whether memory profiling is desired... no checking whether threads support is requested... no checking whether callbacks support is requested... no checking whether JNI cache support is requested... no checking whether headless init is enabled... no checking whether JRI is requested... yes configure: creating ./config.status config.status: creating src/Makevars config.status: creating R/zzz.R config.status: creating src/config.h === configuring in jri (/<>/jri) configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local' 'CC=gcc' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat
Bug#1065777: marked as done (clblas: FTBFS on arm{el,hf}: /<>/src/library/blas/gens/symv.c:955:29: error: implicit declaration of function ‘abs’; did you mean ‘fabs’? [-Werror=implicit-fu
Your message dated Fri, 26 Apr 2024 17:19:20 +
with message-id
and subject line Bug#1065777: fixed in clblas 2.12-5
has caused the Debian Bug report #1065777,
regarding clblas: FTBFS on arm{el,hf}:
/<>/src/library/blas/gens/symv.c:955:29: error: implicit
declaration of function ‘abs’; did you mean ‘fabs’?
[-Werror=implicit-function-declaration]
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.)
--
1065777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clblas
Version: 2.12-4.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=clblas=armel=2.12-4.1=1709170039=0
cd /<>/obj-arm-linux-gnueabi/library/tools/tune && /usr/bin/cc
-DCLBLAS_BONAIRE_DYNAMIC_KERNEL -DCLBLAS_HAWAII_DYNAMIC_KERNEL
-DCLBLAS_TAHITI_DYNAMIC_KERNEL -DCL_USE_DEPRECATED_OPENCL_1_1_APIS
-DCL_USE_DEPRECATED_OPENCL_2_0_APIS -D_POSIX_C_SOURCE=199309L
-D_XOPEN_SOURCE=500 -I/<>/src -I/<>/src/include
-I/<>/src/library/blas/include
-I/<>/src/library/blas/gens
-I/<>/obj-arm-linux-gnueabi/include
-I/<>/src/library/tools/tune -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99
-Wstrict-prototypes -fno-builtin -MD -MT
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o -MF
CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o.d -o
CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o -c
/<>/src/library/blas/gens/symv.c
[ 14%] Building C object
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o
cd /<>/obj-arm-linux-gnueabi/library/tools/tune && /usr/bin/cc
-DCLBLAS_BONAIRE_DYNAMIC_KERNEL -DCLBLAS_HAWAII_DYNAMIC_KERNEL
-DCLBLAS_TAHITI_DYNAMIC_KERNEL -DCL_USE_DEPRECATED_OPENCL_1_1_APIS
-DCL_USE_DEPRECATED_OPENCL_2_0_APIS -D_POSIX_C_SOURCE=199309L
-D_XOPEN_SOURCE=500 -I/<>/src -I/<>/src/include
-I/<>/src/library/blas/include
-I/<>/src/library/blas/gens
-I/<>/obj-arm-linux-gnueabi/include
-I/<>/src/library/tools/tune -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99
-Wstrict-prototypes -fno-builtin -MD -MT
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o -MF
CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o.d -o
CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o -c
/<>/src/library/blas/gens/gemm.c
In file included from /usr/include/CL/cl.h:20,
from /<>/src/clBLAS.h:35,
from /<>/src/library/blas/gens/symv.c:27:
/usr/include/CL/cl_version.h:22:9: note: ‘#pragma message: cl_version.h:
CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined.
Defaulting to 300 (OpenCL 3.0)")
| ^~~
In file included from /usr/include/CL/cl.h:20,
from /<>/src/clBLAS.h:35,
from /<>/src/library/blas/gens/gemm.c:28:
/usr/include/CL/cl_version.h:22:9: note: ‘#pragma message: cl_version.h:
CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined.
Defaulting to 300 (OpenCL 3.0)")
| ^~~
/<>/src/library/blas/gens/symv.c: In function ‘fixupArgs’:
/<>/src/library/blas/gens/symv.c:955:29: error: implicit
declaration of function ‘abs’; did you mean ‘fabs’?
[-Werror=implicit-function-declaration]
955 | abs(kargs->ldc.Vector);
| ^~~
| fabs
cc1: some warnings being treated as errors
make[3]: *** [library/tools/tune/CMakeFiles/tune.dir/build.make:443:
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemv.c.o] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: clblas
Source-Version: 2.12-5
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
clblas, 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
Bug#1041565: marked as done (ITP: lib60870 -- library for IEC 60870-5 based protocols in C)
Your message dated Fri, 26 Apr 2024 18:00:13 + with message-id and subject line Bug#1041565: fixed in lib60870 2.3.2-1 has caused the Debian Bug report #1041565, regarding ITP: lib60870 -- library for IEC 60870-5 based protocols in C 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.) -- 1041565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: lib60870 Version : v2.3.2 Upstream Author : Michael Zillgith * URL or Web page : https://github.com/mz-automation/lib60870 * License : GPL-3 Description : lib60870 library for IEC 60870-5 based protocols in C The current implementation contains code for the IEC 60870-5-101 (application layer and serial link layer) and IEC 60870-5-104 (protocool over TCP/IP) specifications. Features: - support for all application layer message types - master and slave - balanced and unbalanced link layers (for CS 101 serial communication) - client/server for CS 104 TCP/IP communication - CS 104 redundancy group support - CS101 slave/CS104 server: file service support - Supports most TLS features required by IEC 62351-3 (third party code mbedtls required) - portable C99 code --- End Message --- --- Begin Message --- Source: lib60870 Source-Version: 2.3.2-1 Done: Yangfl We believe that the bug you reported is fixed in the latest version of lib60870, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yangfl (supplier of updated lib60870 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, 14 Feb 2024 15:50:12 +0800 Source: lib60870 Binary: liblib60870-2 liblib60870-2-dbgsym liblib60870-dev Architecture: source amd64 Version: 2.3.2-1 Distribution: unstable Urgency: medium Maintainer: Yangfl Changed-By: Yangfl Description: liblib60870-2 - library for IEC 60870-5 based protocols in C liblib60870-dev - library for IEC 60870-5 based protocols in C (development files) Closes: 1041565 Changes: lib60870 (2.3.2-1) unstable; urgency=medium . * Initial release (Closes: #1041565) Checksums-Sha1: 74977632388cb0fe78e6211eff19adaa72a95b7e 1961 lib60870_2.3.2-1.dsc 723434324c4a16239e436ebfa9b7ecbd2a1a2a43 272877 lib60870_2.3.2.orig.tar.gz ceadbfce29fcd42bfd2a63dbe136a3fcb31f695b 8228 lib60870_2.3.2-1.debian.tar.xz 08c3d367e79d31ce9e2a1b79b5ac7f9883c02a1d 7724 lib60870_2.3.2-1_amd64.buildinfo 00075e30f453de7989f89ad26528c32e28a8d660 248504 liblib60870-2-dbgsym_2.3.2-1_amd64.deb 1bc331f2212ead1c27430f708384eac600156590 77644 liblib60870-2_2.3.2-1_amd64.deb 518af37c2cbf886f62ca5a063ac300de52f058cf 110808 liblib60870-dev_2.3.2-1_amd64.deb Checksums-Sha256: c28dde9a7d99cea91a45e61f2d214abfc74bb88b06c77e7a078de248d9fd171b 1961 lib60870_2.3.2-1.dsc c63f170dc2dd25f7ec85d873be522f23d46838a84b072c8afda4118dfd5fc94d 272877 lib60870_2.3.2.orig.tar.gz 3baf1fa1838fb116d22e9fd85f2fc21fa767037bb056c4b97a9cd8a94ec33c0c 8228 lib60870_2.3.2-1.debian.tar.xz 459038f2d05057ac634a7033e3630b5684bffac73ae2f6ec1d3ecc6cee4e219f 7724 lib60870_2.3.2-1_amd64.buildinfo 43d6b8651dc6b12f7520766424e74499ba769121b67382a29d06b76340588e0f 248504 liblib60870-2-dbgsym_2.3.2-1_amd64.deb 071264c173c7be8b5e6cf77a82477f41003d7ac3255aa2d24f791866e4c3956e 77644 liblib60870-2_2.3.2-1_amd64.deb fdc82686bcb7912bf16444baf3850d21f5787d465c932abf544a3afc24f6c40f 110808 liblib60870-dev_2.3.2-1_amd64.deb Files: deeb71e9e7a29c6e4172c45c8a41103a 1961 libs optional lib60870_2.3.2-1.dsc 980f0ef86717e239f962796940f8dfac 272877 libs optional lib60870_2.3.2.orig.tar.gz 53ba6e26b141d7bca81b43f99e8a8e9f 8228 libs optional lib60870_2.3.2-1.debian.tar.xz cea93e8099da9885b8d0b860777d24cd 7724 libs optional lib60870_2.3.2-1_amd64.buildinfo 67072b3a130cc2f8708c19910e00bba8 248504 debug optional liblib60870-2-dbgsym_2.3.2-1_amd64.deb 28fe18070f755eddbf1f06e9df11f2a9 77644 libs optional liblib60870-2_2.3.2-1_amd64.deb 3d2da1f6b0f9473e86d6dfea8954665d 110808 libdevel optional liblib60870-dev_2.3.2-1_amd64.deb
Bug#1063388: marked as done (ITP: chuffed -- lazy clause generation CP solver)
Your message dated Fri, 26 Apr 2024 18:00:11 + with message-id and subject line Bug#1063388: fixed in chuffed 0.13.1-1 has caused the Debian Bug report #1063388, regarding ITP: chuffed -- lazy clause generation CP solver 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.) -- 1063388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Kari Pahula X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org * Package name: chuffed Version : 0.13.1 * URL : https://github.com/chuffed/chuffed * License : MIT/X Programming Lang: C++ Description : lazy clause generation CP solver Chuffed is a state of the art lazy clause solver designed from the ground up with lazy clause generation in mind. Lazy clause generation is a hybrid approach to constraint solving that combines features of finite domain propagation and Boolean satisfiability. It combines some of the advantages of finite domain constraint programming (high level model and programmable search) with some of the advantages of SAT solvers (reduced search by nogood creation, and effective autonomous search using variable activities). Chuffed only supports 3 different propagator priorities. Chuffed implements a number of global propagators (alldiff, inverse, minimum, table, regular, mdd, cumulative, disjunctive, circuit, difference). It also only supports two kinds of integer variables. Small integer variables for which the domain is represented by a byte string. And large integer variables for which the domain is represented only by its upper and lower bound (no holes allowed). All boolean variables and boolean constraints are handled by the builtin SAT solver. The solver, when run with lazy clause generation disabled, is somewhat comparable in speed with older versions of Gecode. The overhead from lazy clause generation ranges from negligible to perhaps around 100%. The search reduction, however, can reach orders of magnitude on appropriate problems. Thus lazy clause generation is an extremely important and useful technology. The easiest way to use Chuffed is as a backend to the MiniZinc constraint modelling language. Chuffed can also be used as a C++ library. The description is edited from upstream's description, it went into more detail than this about the implementation. For certain types of CP problems it works better than the alternatives. Chuffed is both a library and it provides a binary (fzn-chuffed). The library can be used as a dependency for both minizinc and minizinc-ide (which I maintain) and it provides an alternative flatzinc implementation for minizinc. I plan to maintain this under the Debian Science team. As of now upstream is building chuffed as a static library only but I'll try to convince them to provide a shared library before packaging it. --- End Message --- --- Begin Message --- Source: chuffed Source-Version: 0.13.1-1 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of chuffed, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated chuffed 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: Sat, 10 Feb 2024 14:02:14 +0200 Source: chuffed Binary: chuffed-flatzinc chuffed-flatzinc-dbgsym Architecture: source amd64 Version: 0.13.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kari Pahula Description: chuffed-flatzinc - lazy clause generation FlatZinc implememntation Closes: 1063388 Changes: chuffed (0.13.1-1) unstable; urgency=medium . * Initial release. (Closes: #1063388) * Use libmurmurhash instead of included implementation Checksums-Sha1: c92701d2317f2cf4b1418e1d6045f9c58acee51b 1999 chuffed_0.13.1-1.dsc e8f87d7928252f31204731236bb4b88e80e93619 2144212 chuffed_0.13.1.orig.tar.xz 04bec9e341200588207eeb30f22c8a3039c6c22d 5008 chuffed_0.13.1-1.debian.tar.xz
Bug#1063912: marked as done (ITP: pass-extension-update -- pass extension that provides an easy flow for updating passwords)
Your message dated Fri, 26 Apr 2024 18:00:15 + with message-id and subject line Bug#1063912: fixed in pass-update 2.1-1 has caused the Debian Bug report #1063912, regarding ITP: pass-extension-update -- pass extension that provides an easy flow for updating passwords 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.) -- 1063912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Antoine Beaupre X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: pass-extension-update Version : 2.1 Upstream Contact: Alex roddhjav * URL : https://github.com/roddhjav/pass-update * License : GPL-3 Programming Lang: Shell Description : pass extension that provides an easy flow for updating passwords pass update extends the pass utility with an update command providing an easy flow for updating passwords. It supports path, directory and wildcard update. Moreover, you can select how to update your passwords by automatically generating new passwords or manually setting your own. pass update assumes that the first line of the password file is the password and so only ever updates the first line unless the --multiline option is specified. By default, pass update prints the old password and waits for the user before generating a new one. This behaviour can be changed using the provided options. I need something like this for work so I'll take a look at how reasonable this is. There's already a Debian package in the upstream source too.$ --- End Message --- --- Begin Message --- Source: pass-update Source-Version: 2.1-1 Done: Antoine Beaupré We believe that the bug you reported is fixed in the latest version of pass-update, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antoine Beaupré (supplier of updated pass-update 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, 14 Feb 2024 14:21:40 -0500 Source: pass-update Binary: pass-extension-update Architecture: source all Version: 2.1-1 Distribution: experimental Urgency: medium Maintainer: Antoine Beaupré Changed-By: Antoine Beaupré Description: pass-extension-update - pass extension providing an easy flow for updating passwords Closes: 1063912 Changes: pass-update (2.1-1) experimental; urgency=medium . * Initial release (Closes: #1063912) Checksums-Sha1: 5a3a436f8f0321f1b9c821113e2d995a0d2d708c 1282 pass-update_2.1-1.dsc c7d599272ac5b66ac0fb719f2375edacbc256515 46199 pass-update_2.1.orig.tar.gz f16981ba16b4a047ef707354413c0a5df565bbc5 1840 pass-update_2.1-1.debian.tar.xz c8d76760d46730b6ce92a1e46a0479ec6edfe7bd 8328 pass-extension-update_2.1-1_all.deb 551f14755c04e88afaee6363bc83e1d33be05587 5610 pass-update_2.1-1_amd64.buildinfo Checksums-Sha256: db46bc448a113a0a6e46b26be40d82235ae121f850e06c275c16de988575b901 1282 pass-update_2.1-1.dsc d6b48671e7c38fd75bcc4c3f765f5bf35910981177e4f11659d092d120c8efe6 46199 pass-update_2.1.orig.tar.gz 95494665f8d3ad427f4d7ccee130e03a29165fb63b25b0bd1426873fc45223ac 1840 pass-update_2.1-1.debian.tar.xz 4802ecfda6c53b06a3ed09a8b38d33780832439b0743401fb3789ea8abe99671 8328 pass-extension-update_2.1-1_all.deb 42603f8e26e0d118b54a780b02ac12cbd9f8999da67a17468da0d2246b91af54 5610 pass-update_2.1-1_amd64.buildinfo Files: f9a25908cd65e38f6fdd75917f0cc0fd 1282 admin optional pass-update_2.1-1.dsc f50f8b10f8d6931c6497913e9d8536dd 46199 admin optional pass-update_2.1.orig.tar.gz 4d34c77c3d063ac7196354841ccb32f2 1840 admin optional pass-update_2.1-1.debian.tar.xz 31a3e559d9c4fa0812361d80a16249eb 8328 admin optional pass-extension-update_2.1-1_all.deb 74b6009741678f6f1fedda87b626594d 5610 admin optional pass-update_2.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQS7ts1MmNdOE1inUqYCKTpvpOU0cwUCZc0Z/AAKCRACKTpvpOU0 cxjvAP0fxu1Kz8cILxOkNcS/w1P2AZBIymc4/gmnCd9XWWGWWAEAtTLyTGr0WrVD WgIYVH8R/xf+pFllS8NKQtXHTNWVdAw= =3sRm -END PGP SIGNATURE- pgp_fGliT3ULB.pgp Description: PGP
Bug#1065727: marked as done (ITP: nwg-hello -- GTK3-based greeter for the greetd daemon)
Your message dated Fri, 26 Apr 2024 18:00:15 + with message-id and subject line Bug#1065727: fixed in nwg-hello 0.1.8-1 has caused the Debian Bug report #1065727, regarding ITP: nwg-hello -- GTK3-based greeter for the greetd daemon 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.) -- 1065727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Maytham Alsudany X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: nwg-hello Version : 0.1.7 Upstream Contact: https://github.com/nwg-piotr/nwg-hello/issues * URL : https://github.com/nwg-piotr/nwg-hello * License : Expat Programming Lang: Python Description : GTK3-based greeter for the greetd daemon This program is a part of the nwg-shell project. . Nwg-hello is a GTK3-based greeter for the greetd daemon, written in Python. It is meant to work under a Wayland compositor, like sway or Hyprland. . Features: - Multi-monitor support with gtk-layer-shell; - multi-language support; - background & style customization with css; - automatic selection of the last used session and user; - support for setting environment variables. Another option for greetd, and a great addition to Debian to encourage users to switch to Wayland compositors like sway. -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmXsVy0YHG1heXRoYTh0 aGVkZXZAZ21haWwuY29tAAoJENWXiXIGxfB/x1AQAK/zpikqDXl5m94O5IHUJBJf yuD3S588Ezwk26f/6n5Ole6nSZYkphtYV5VuGFAe2rAE5K+yMz1ivxoAxTk4vL0t ZZYufhz8kQrz2AsfgyENrERgkixmRKvSaY8qJeHgFDJE2Y9VSovIxE7o1XELJJsq vUYYvzAkn414rMrDLSR3tzey/KD9jVsknS97XmsoCjQy50+on95h4WNQsz0hQjrG LkUwU2Q61X8MGO6Zrr09QC5qDEc7yI9fDyyazNR/eD5IER0iH9Zw1xkGFv1Z39HS xmUTn83f8Ztz5s7jLvGerWqiZEvkN8yQTo51dGMv5sjkVliSmXy7WwfdE/P0aU8N HjvFOTD3+PQC9X3VU9z0Vx1mKxAWFRjjzOIvgyzetm3Hd3j0EfHQFyOJhAkyRphY U9oVoTKTKMn9UDykjrkRcMYo7H/3wvr9k597pA+QF8Sy3kby5LEQVpOu1ChkBuG5 m0RDGdTm30eRjf4Zf7J8sLbZnBZK13rPH/1h4ntzIUKFuRYKePCPkXRhzXCvlnyE iZBx1ERLU136rE3HprBcLgstJJ5TmpQxJ3Q9VsIwb9OUK46CQCNH4f9VUS9cLg4q 7OfgJ0Ub7ojZUZzoVB54sv4yqgdwW6TtAtNTgaaN/2/IuOm3efC9yr99AQ/MV4kZ zq/i588Hv4uiFeqFA1GU =5tIY -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: nwg-hello Source-Version: 0.1.8-1 Done: Maytham Alsudany We believe that the bug you reported is fixed in the latest version of nwg-hello, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maytham Alsudany (supplier of updated nwg-hello 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: Mon, 22 Apr 2024 12:33:10 +0300 Source: nwg-hello Binary: nwg-hello Architecture: source amd64 Version: 0.1.8-1 Distribution: unstable Urgency: medium Maintainer: Maytham Alsudany Changed-By: Maytham Alsudany Description: nwg-hello - GTK3-based greeter for the greetd daemon Closes: 1065727 Changes: nwg-hello (0.1.8-1) unstable; urgency=medium . * Initial release. (Closes: #1065727) Checksums-Sha1: 28074735b8cb208ebefc601f421a61fb20ffe1d8 1901 nwg-hello_0.1.8-1.dsc 1305e3752bf45e7ffa440a2ec3db50f9fd15384e 1460940 nwg-hello_0.1.8.orig.tar.gz 8ff83e680ecde02b9658c22bc3dfd3bd6f13eab1 2800 nwg-hello_0.1.8-1.debian.tar.xz 738be2e33fae3d78220466b2409d00b8d94cb636 8216 nwg-hello_0.1.8-1_amd64.buildinfo 235948bafd2e903b821a2d7246b1b982404380b8 1446444 nwg-hello_0.1.8-1_amd64.deb Checksums-Sha256: 12fe5062f0a3a1d9ed4ce5d21682ffec03ef52534f0b3514bf783f207eca15c3 1901 nwg-hello_0.1.8-1.dsc 755bfb17c2b65eb5782202a7c2d7fb594204c980deefa03b10128811fed610ac 1460940 nwg-hello_0.1.8.orig.tar.gz f79f52cff3b153055bedf1c355b331383baee93be2565d87d423c96b28183195 2800 nwg-hello_0.1.8-1.debian.tar.xz a5721cb899fc3498ca90353ffb7ca13f26ab2feee4ddef5900b45a9e628c 8216 nwg-hello_0.1.8-1_amd64.buildinfo 6ce3db69d5bce6a96047f0c5efe6292689f02258459d6c73186a93ed68597785 1446444 nwg-hello_0.1.8-1_amd64.deb Files: 5d640ab8e6f7febc95f430a5f1724878 1901 misc optional
Bug#1069568: marked as done (ITP: python-hatch-mypyc -- Hatch build hook plugin for Mypyc)
Your message dated Fri, 26 Apr 2024 18:00:16 + with message-id and subject line Bug#1069568: fixed in python-hatch-mypyc 0.16.0-1 has caused the Debian Bug report #1069568, regarding ITP: python-hatch-mypyc -- Hatch build hook plugin for Mypyc 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.) -- 1069568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Owner: Michael R. Crusoe Severity: wishlist * Package name : python-hatch-mypyc Version : 0.16.0 Upstream Author : Ofek Lev * URL : https://github.com/ofek/hatch-mypyc * License : Expat Programming Lang: Python Description : Hatch build hook plugin for Mypyc Provides a build hook plugin for Hatch build system for Python that compiles code with Mypyc. Remark: This package is Team Maintained by Michael R. Crusoe and the Debian Python Team at https://salsa.debian.org/python-team/packages/python-hatch-mypyc OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-hatch-mypyc Source-Version: 0.16.0-1 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of python-hatch-mypyc, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated python-hatch-mypyc 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: Sat, 20 Apr 2024 17:57:56 +0200 Source: python-hatch-mypyc Binary: python3-hatch-mypyc Architecture: source all Version: 0.16.0-1 Distribution: unstable Urgency: low Maintainer: Michael R. Crusoe Changed-By: Michael R. Crusoe Description: python3-hatch-mypyc - Hatch build hook plugin for Mypyc Closes: 1069568 Changes: python-hatch-mypyc (0.16.0-1) unstable; urgency=low . * Initial release; Closes: #1069568 Checksums-Sha1: 7e596edce6eb41119bfcf54479e42c7a4a9e0ecd 2205 python-hatch-mypyc_0.16.0-1.dsc 60cdbc1e5887cdf373eb08d5012c84e04de5 11720 python-hatch-mypyc_0.16.0.orig.tar.xz a49a50e74117ac9d662e5efc8779e68890576e9f 2312 python-hatch-mypyc_0.16.0-1.debian.tar.xz 97abefbc266b46ba17dee4e2e9f6257ffdf3e418 8131 python-hatch-mypyc_0.16.0-1_amd64.buildinfo 46aec8cd66f447addec9dc1d8e4222878b6df5e8 python3-hatch-mypyc_0.16.0-1_all.deb Checksums-Sha256: 5df7a5c4421fe7e088fca8e63caef3f61f82ad963effd9a78284c1861ffb64f2 2205 python-hatch-mypyc_0.16.0-1.dsc 28907b1de709d303f36aff76182d821dd2dfcfb4f2cb209a9f60b9adeced92c8 11720 python-hatch-mypyc_0.16.0.orig.tar.xz 5c0a33e0f3338c5974c6fab73214ca1be753dc0a27f611158587da341cf6b263 2312 python-hatch-mypyc_0.16.0-1.debian.tar.xz ab18576fd4b30df3170bc4bc0fd160d032c01644420f1e6b1bdf0c8637bce196 8131 python-hatch-mypyc_0.16.0-1_amd64.buildinfo 9a32feb83129ae8630ea679e233a209bf1016287c6b2fa4bc2db3f676a58831b python3-hatch-mypyc_0.16.0-1_all.deb Files: 304fe372be19e213d7c6f7db6437614b 2205 python optional python-hatch-mypyc_0.16.0-1.dsc 270229788cb8aba8e29fbcb1c40d8835 11720 python optional python-hatch-mypyc_0.16.0.orig.tar.xz fb5a07c55ef267b7581ae2ff929842bb 2312 python optional python-hatch-mypyc_0.16.0-1.debian.tar.xz e4cc38c3350d6dcab3557224031b2879 8131 python optional python-hatch-mypyc_0.16.0-1_amd64.buildinfo fd5db12bdc04da1cc66e4186e1a6af25 python optional python3-hatch-mypyc_0.16.0-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmYj5xwACgkQPCZ2P2xn 5uKvsRAAvHMgHYTE68SnrYFhLlAt7GvDIpN0VZRYBlj0ZgdkXnQz1v/mQcNYOegi R+OJYLhylVfUloYInto6KRSrI7IEh7HW0sMpGtf0i6lKN78Cl1ZKFJJwK1s9R/6W uNxbFtZsIgYmBa8yfICpCY3+vnKzHAXvR+Ig1C8JfP/7AfG4QFfafqTTnhnnEZXb mo7jEvWaCGoWuc4Wxh0pfv4+Ode1yPZH7HMZa7eyxedWYJyUPHeKs5RKBPNX7k5Z OwDmyhQfta2afI7ZslaHVuSf5v/k4eL1JKTxQ3N1gln2DZxgt4FgsD4sTqYLu9ty ncqZ4GxkfzivV8Ck9rMlt4Gv6x/71ruQfqdz0ZJJP5u3tLgAqr04dusW29WQ1HHm 9QLHReZGzxbYsm9Swak/WAWBvSqFhdORllH1RPJeUx9vmyPTJge1puLBi+930oYm eiUdGs55eIe6dxMNzZctimlqlEQwKCc/wRE8lccaFqPxBvt27ocF22u5t+ThU+dx eN8/KKzY/nnRAkz3e3+nSvbI+XQGLBDZc9yqeFm/ewfjln9vlKVCwt5h6subuBOf
Bug#763887: marked as done (ITP: libest -- Enrollment over Secure Transport reference)
Your message dated Fri, 26 Apr 2024 18:00:14 + with message-id and subject line Bug#763887: fixed in libest 3.2.0+ds-1 has caused the Debian Bug report #763887, regarding ITP: libest -- Enrollment over Secure Transport reference 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.) -- 763887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: John Foley * Package name: libest Version : 1.1.0p Upstream Author : John Foley * URL : https://github.com/cisco/libest * License : BSD Programming Lang: C Description : Enrollment over Secure Transport reference implementation (RFC 7030) RFC 7030 defines Enrollment over Secure Transport (EST). EST is used to securely provision X.509 certificates. libest provides both a client-side and server-side implementation of EST. There are currently no upstream packages dependent on libest. However, libest provides both a library and a command line utility. The CLI utility can be used as a stand-alone application to provision certificates on a Linux host. EST is a new protocol. It is expected that upstream projects will integrate libest in the future. I am not aware of any existing Debian packages that provide support for EST. I plan to be the package maintainer and am currently looking for a sponsor. Thank you. --- End Message --- --- Begin Message --- Source: libest Source-Version: 3.2.0+ds-1 Done: Andreas Schärtl We believe that the bug you reported is fixed in the latest version of libest, 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 763...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Schärtl (supplier of updated libest 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: Tue, 13 Feb 2024 19:32:58 +0100 Source: libest Binary: libest-dev libest-doc libest-utils libest-utils-dbgsym libest3 libest3-dbgsym Architecture: source armel all Version: 3.2.0+ds-1 Distribution: unstable Urgency: medium Maintainer: Andreas Schärtl Changed-By: Andreas Schärtl Description: libest-dev - Enrollment over Secure Transport (EST), development files libest-doc - Enrollment over Secure Transport (EST), documentation libest-utils - Utils that make use of the EST protocol libest3- Enrollment over Secure Transport (EST), library Closes: 763887 Changes: libest (3.2.0+ds-1) unstable; urgency=medium . * Initial packaging. Closes: #763887 Checksums-Sha1: 6d9122c274cf81b699940d5b8e91d495c07f56f9 2048 libest_3.2.0+ds-1.dsc 8b3c4482e4b105c5fa10d94b6d65c6ddc4d3bfbc 931012 libest_3.2.0+ds.orig.tar.xz d93020db97fedad9963fa627ab6c4090a2045ed9 12720 libest_3.2.0+ds-1.debian.tar.xz 38bad7baad22429f93917dbd39bb3e0afb694230 13212 libest-dev_3.2.0+ds-1_armel.deb 9d6af7997b49fe82b67c87b6d38da60df2e0d0b4 313012 libest-doc_3.2.0+ds-1_all.deb 0e437ba4433efc8971d0037a685b330bb0d69afd 150336 libest-utils-dbgsym_3.2.0+ds-1_armel.deb a113ab78fc18295242a3b599f97e980261542075 53572 libest-utils_3.2.0+ds-1_armel.deb 58bf1cc3d68d299857b04b50f1afbbbc3cecb719 209036 libest3-dbgsym_3.2.0+ds-1_armel.deb ff23d4af532872d5c3a5bea2e2a51081051bcc9a 80204 libest3_3.2.0+ds-1_armel.deb 0ad62513dacdf40470f772e80fe0d3be8bb48f56 9959 libest_3.2.0+ds-1_armel.buildinfo Checksums-Sha256: 73dd463d4219ecd1dd09fd85117b78209bd0b0539724af66a68ca21bcc714721 2048 libest_3.2.0+ds-1.dsc 46d1150ff6f1ace3ccd9a9ab962cfafd275b7c52edb0fd4e868280672aa7cf0d 931012 libest_3.2.0+ds.orig.tar.xz c82030bd8f66252d2413d08386373e1592f58d7a92f0928e9ada114a6afd921f 12720 libest_3.2.0+ds-1.debian.tar.xz 7409e650f1480a3f0580341f49ba6689efb6009fd49652ceb5c0f4c82db27a12 13212 libest-dev_3.2.0+ds-1_armel.deb 4fa9f73d6caf5d038284b686be088c681245248f60c259596d2aac469eea4c80 313012 libest-doc_3.2.0+ds-1_all.deb cd0670fc6f257026a43794c728f47609f6529254889ee81610dcb9764f288e21 150336 libest-utils-dbgsym_3.2.0+ds-1_armel.deb 6ed606ce6801b292ae78f8f017cce4e7f9efa93933fde8914c712b557c56c049 53572 libest-utils_3.2.0+ds-1_armel.deb
Bug#906850: marked as done (ITP: futhark -- a data-parallel functional language)
Your message dated Fri, 26 Apr 2024 18:00:12 + with message-id and subject line Bug#906850: fixed in haskell-futhark 0.25.15-1 has caused the Debian Bug report #906850, regarding ITP: futhark -- a data-parallel functional language 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.) -- 906850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist I'm the maintainer of Futhark, a data-parallel functional programming language whose compiler is implemented in Haskell: https://futhark-lang.org Futhark is already available on macOS via Homebrew and Arch Linux via AUR, and it would be a shame if Debian had to go without. Debian already has other packages written in Haskell, and the Futhark compiler does not require anything unusual to build, so I think whatever procedure is usual should be sufficient here. However, I do not know what that procedure might be. Also, I am ready to make changes upstream in order to make the packaging more convenient. -- \ Troels /\ Henriksen --- End Message --- --- Begin Message --- Source: haskell-futhark Source-Version: 0.25.15-1 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of haskell-futhark, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated haskell-futhark 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: Fri, 26 Apr 2024 14:38:16 +0300 Source: haskell-futhark Binary: futhark futhark-doc libghc-futhark-dev libghc-futhark-doc libghc-futhark-prof Architecture: source all amd64 Version: 0.25.15-1 Distribution: unstable Urgency: low Maintainer: Debian Haskell Group Changed-By: Kari Pahula Description: futhark- optimising compiler for Futhark programming language futhark-doc - Futhark User's Guide libghc-futhark-dev - libghc-futhark-doc - libghc-futhark-prof - Closes: 906850 Changes: haskell-futhark (0.25.15-1) unstable; urgency=low . * Initial release (Closes: #906850) Checksums-Sha1: 77ccf427b04cadd92e39023a5837775a0c7bb6e4 5512 haskell-futhark_0.25.15-1.dsc 71cbe77238f1fb42f214321785009b11d182263f 1757419 haskell-futhark_0.25.15.orig.tar.gz 6efa08711b4b9a2a4189896eb8871c64c6528a8f 5016 haskell-futhark_0.25.15-1.debian.tar.xz 0706860c4570a7f3a56a473b8bbf6193a0c1d8d1 233264 futhark-doc_0.25.15-1_all.deb 15905b748a5c634d6aa6467bdacc397148006d66 12203860 futhark_0.25.15-1_amd64.deb bf8d24919ca491d78d5119e6cb313112f54d66d9 23724 haskell-futhark_0.25.15-1_amd64.buildinfo 8141d5eebf9389b95c3ffe0086fcbf57254376df 17369184 libghc-futhark-dev_0.25.15-1_amd64.deb 04f0cd54209528e8b875a5a38a31ccdb2dcc16ad 4540628 libghc-futhark-doc_0.25.15-1_all.deb 7cef437ba03716bb3874974c88731f0919fccedc 16279128 libghc-futhark-prof_0.25.15-1_amd64.deb Checksums-Sha256: f8a0bdf81c3e979a5cc617af96faa72592bcdc2db12f34df5c3c4f61fbf11bb5 5512 haskell-futhark_0.25.15-1.dsc 5820a034e54fc4f511c15c5b16a5fa70bba739a10243a4f75f3cdd195c0e775c 1757419 haskell-futhark_0.25.15.orig.tar.gz 0996f540db2132ab53cd3c50061dd8afa4c53f86012adaa664352075c8c5f749 5016 haskell-futhark_0.25.15-1.debian.tar.xz e518bc77da32cb0122964d33ba4278cc6c64a9ae9f1884b8d38685f75ded518b 233264 futhark-doc_0.25.15-1_all.deb b904939964036309994876b79a2a9ac7f825c5e64f5ad87a4ea3cd19adad3165 12203860 futhark_0.25.15-1_amd64.deb f72ae64434e6f80a2559959e70c04ee5f2df877cd62164d68713416771fa11fa 23724 haskell-futhark_0.25.15-1_amd64.buildinfo cc482324ac65136b3b98b305cddfd5748883da4a8b3ce32de285c6a4835402cc 17369184 libghc-futhark-dev_0.25.15-1_amd64.deb fc2d51fbba1c2b4380500cc437c817a77755d9177a18d4753842102550d12f8c 4540628 libghc-futhark-doc_0.25.15-1_all.deb 7b3f11da6b077129fc5dc1e7f6100aeead3ec94fa4f713e56e2db11ae2d00fe0 16279128 libghc-futhark-prof_0.25.15-1_amd64.deb Files: d7877f2212ec341683fdfd4804765a44 5512 haskell optional haskell-futhark_0.25.15-1.dsc 017c6d6be7bb1d116467da08b832f9ae 1757419 haskell optional haskell-futhark_0.25.15.orig.tar.gz
Bug#1000232: marked as done (pywavelets: Call dh_numpy3 to get proper versioned dependency on python3-numpy)
Your message dated Fri, 26 Apr 2024 15:50:21 +
with message-id
and subject line Bug#1000232: fixed in pywavelets 1.4.1-1
has caused the Debian Bug report #1000232,
regarding pywavelets: Call dh_numpy3 to get proper versioned dependency on
python3-numpy
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.)
--
1000232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pywavelets
Version: 1.1.1-1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi Daniele,
In Ubuntu, a rebuild of pywavelets to pick up support for the new python3.10
is causing skimage's autopkgtests to fail, because it has also been built
against a newer numpy and pywavelets correctly notices that some object
sizes have changed:
$ python3 -m pywt
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 188, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib/python3.9/runpy.py", line 147, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib/python3.9/runpy.py", line 111, in _get_module_details
__import__(pkg_name)
File "/usr/lib/python3/dist-packages/pywt/__init__.py", line 16, in
from ._extensions._pywt import *
File "pywt/_extensions/_pywt.pyx", line 1, in init pywt._extensions._pywt
ValueError: numpy.ndarray size changed, may indicate binary incompatibility.
Expected 88 from C header, got 80 from PyObject
$
python3-pywt needs to depend on python3-numpy >= 1:1.20.0. This dependency
is autogenerated by calling dh_numpy3. The attached patch fixes the
pywavelet debian/rules to call this command and get the right dependency.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pywavelets-1.1.1/debian/rules pywavelets-1.1.1/debian/rules
--- pywavelets-1.1.1/debian/rules 2020-06-16 02:19:53.0 -0700
+++ pywavelets-1.1.1/debian/rules 2021-11-19 15:20:50.0 -0800
@@ -39,3 +39,7 @@
override_dh_fixperms_arch:
# Remove execution flag set by upstream also on examples.
find debian/python-pywt-doc -type f -exec chmod -x {} \;
+
+override_dh_python3:
+ dh_numpy3
+ dh_python3
--- End Message ---
--- Begin Message ---
Source: pywavelets
Source-Version: 1.4.1-1
Done: Colin Watson
We believe that the bug you reported is fixed in the latest version of
pywavelets, 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 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson (supplier of updated pywavelets 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: Fri, 26 Apr 2024 16:12:54 +0100
Source: pywavelets
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Colin Watson
Closes: 1000232 1068805
Changes:
pywavelets (1.4.1-1) unstable; urgency=medium
.
* Team upload.
* New upstream release:
- Remove distutils dependency (closes: #1068805).
* Remove misspelled override_dh_fixperms_indep and
override_dh_fixperms_arch targets from debian/rules; they're no longer
needed anyway.
* Build-depend on dh-sequence-numpy3 (closes: #1000232).
* Fix handling of SOURCE_DATE_EPOCH in debian/rules.
Checksums-Sha1:
7488b13c9529f53e7a91ccbc6605c473a4b468a1 2300 pywavelets_1.4.1-1.dsc
952c8f17a899f91642c2a4c9a212a30ab952135a 4589677 pywavelets_1.4.1.orig.tar.gz
68675d2782024b573cd6fd75543b69d1352ead28 8632 pywavelets_1.4.1-1.debian.tar.xz
Checksums-Sha256:
6320f99d98b5ca744a61a120d39eb1c1b62fbfa03aa82f65c99058df82c94bce 2300
pywavelets_1.4.1-1.dsc
6437af3ddf083118c26d8f97ab43b0724b956c9f958e9ea788659f6a2834ba93 4589677
pywavelets_1.4.1.orig.tar.gz
Bug#1068805: marked as done (python3-pywt: distutils not available in Python 3.12)
Your message dated Fri, 26 Apr 2024 15:50:21 + with message-id and subject line Bug#1068805: fixed in pywavelets 1.4.1-1 has caused the Debian Bug report #1068805, regarding python3-pywt: distutils not available in Python 3.12 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.) -- 1068805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pywt Version: 1.1.1-3 Severity: serious Dear maintainer, pywt directly depends on distutils, which is no longer available on Python 3.12. in pywt/__init__.py: ---8<-- from __future__ import division, print_function, absolute_import from distutils.version import LooseVersion ---8<-- This makes the current version of pywt unusable on Python 3.12. Best Ole --- End Message --- --- Begin Message --- Source: pywavelets Source-Version: 1.4.1-1 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of pywavelets, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated pywavelets 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: Fri, 26 Apr 2024 16:12:54 +0100 Source: pywavelets Architecture: source Version: 1.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1000232 1068805 Changes: pywavelets (1.4.1-1) unstable; urgency=medium . * Team upload. * New upstream release: - Remove distutils dependency (closes: #1068805). * Remove misspelled override_dh_fixperms_indep and override_dh_fixperms_arch targets from debian/rules; they're no longer needed anyway. * Build-depend on dh-sequence-numpy3 (closes: #1000232). * Fix handling of SOURCE_DATE_EPOCH in debian/rules. Checksums-Sha1: 7488b13c9529f53e7a91ccbc6605c473a4b468a1 2300 pywavelets_1.4.1-1.dsc 952c8f17a899f91642c2a4c9a212a30ab952135a 4589677 pywavelets_1.4.1.orig.tar.gz 68675d2782024b573cd6fd75543b69d1352ead28 8632 pywavelets_1.4.1-1.debian.tar.xz Checksums-Sha256: 6320f99d98b5ca744a61a120d39eb1c1b62fbfa03aa82f65c99058df82c94bce 2300 pywavelets_1.4.1-1.dsc 6437af3ddf083118c26d8f97ab43b0724b956c9f958e9ea788659f6a2834ba93 4589677 pywavelets_1.4.1.orig.tar.gz a4926079db63626cc5bbfeb6a0ccc680093e444dccdea7e6eb8963fb5cb72785 8632 pywavelets_1.4.1-1.debian.tar.xz Files: 82c3e2d0603008f3b1a9eb6b8048135b 2300 python optional pywavelets_1.4.1-1.dsc 6e487b2c3418fc0a1acf3be53bfbb0c3 4589677 python optional pywavelets_1.4.1.orig.tar.gz 407b2ae49defcbf4d44957c27033fdeb 8632 python optional pywavelets_1.4.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrxLkACgkQOTWH2X2G UAt98BAAjN7VkB7Bs2miVjOuRW8XDxP7paGxeRX5jMCe17Eqjyot3nRgGBg4qBLp Df7IMqCkwOcfYqHCd2zQQPfqMUcUx1SPM9oDuFizd7M627RSvXis3MFiUU3piJRJ BBOZ9cJrr3KxS5tYggweGVMVCojC8XBrs92rAN8ygKq3TDLI+KYxGSqU3XV7iAvY vyVH853n+mBS3HPvJOMM1PfwQx9r3kXg+IK+ACH/UN2Y5+BM1Fe6TzGzF3BlRqVq wjrrgmd49Y7gCnNyqJSbMfqudcoaN7n3oA+92pumCYYBwDsE8yfdplzxvPXViA80 pKPIEtTdHcWXgbgroJAOVFPPwbR6g4b2ZvYVCTDDxVd8TC8nT0u/yYUJcUYkkBKH FcOlH3VZkAXHVhGuewaKZ6mlGuGQ/R6pK8VK76o4SCqZHYWimAZEqpFH3RXny1uV SN0nM4p51B61BPgke1BOmMJ0PCVqxtT6JY2a4GTSHveDHCgqrCG2ZlTgdtxayOKf UJc1ABII1E8hmCafqrnKxSv0APGoPFuGsyiIw4KIPi2Qkz1XbBQIYrstIxUQMZHO 5nprmpOqsAYi9cWcopkuJ4voijIbb+74GfcEoDtw7zzFqlT98FRbCup4FfaHZ32b Mxa2lF3l6AXERJCZ16FIhLZLbG4HpumfJvmnn4SHINAZ4V3b+0I= =L08w -END PGP SIGNATURE- pgpBdCUu__pgZ.pgp Description: PGP signature --- End Message ---
Bug#1066357: marked as done (ldapvi: FTBFS: diff.c:218:9: error: implicit declaration of function ‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? [-Werror=implicit-function-declaration])
Your message dated Fri, 26 Apr 2024 15:47:46 + with message-id and subject line Bug#1066357: fixed in ldapvi 1.7-11 has caused the Debian Bug report #1066357, regarding ldapvi: FTBFS: diff.c:218:9: error: implicit declaration of function ‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? [-Werror=implicit-function-declaration] 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.) -- 1066357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldapvi Version: 1.7-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -o diff.o diff.c > diff.c: In function ‘safe_str2dn’: > diff.c:218:9: error: implicit declaration of function ‘ldap_bv2dn_x’; did you > mean ‘ldap_bv2dn’? [-Werror=implicit-function-declaration] > 218 | ldap_bv2dn_x(, out, flags); > | ^~~~ > | ldap_bv2dn > cc1: some warnings being treated as errors > make[1]: *** [GNUmakefile:16: diff.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/ldapvi_1.7-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ldapvi Source-Version: 1.7-11 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of ldapvi, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated ldapvi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 11:15:30 -0400 Source: ldapvi Architecture: source Version: 1.7-11 Distribution: unstable Urgency: medium Maintainer: Rhonda D'Vine Changed-By: Boyuan Yang Closes: 1066357 Changes: ldapvi (1.7-11) unstable; urgency=medium . * Non-maintainer upload. * debian/control: Avoid using transitional package names. * debian/control: Add missing dependency sensible-utils (lintian). * debian/patches/07,08: Add patch to fix FTBFS caused by Werror=implicit-function-declaration. (Closes: #1066357) Checksums-Sha1: ad00b7931db71fd5f8a91518475626e1ba621021 1777 ldapvi_1.7-11.dsc d1cde4cbb618180f9ae0e77c56a1520b8ad61c9a 119503 ldapvi_1.7.orig.tar.gz 707c8d4bd18f8dc8f0a93dd641a3b6c2a4fdd377 9592 ldapvi_1.7-11.debian.tar.xz 99fb0011f9d98d283e87820a6819cb2bb4330454 7756 ldapvi_1.7-11_amd64.buildinfo Checksums-Sha256: da7985a246d9274b0b68f6145e07dd5489f6c081346f06d5e88201bcf4b49e1f 1777 ldapvi_1.7-11.dsc 6f62e92d20ff2ac0d06125024a914b8622e5b8a0a0c2d390bf3e7990cbd2e153 119503 ldapvi_1.7.orig.tar.gz bba97940aa50f74e72a67a6b710e0847f018064a5f053c69033cb46890786b17 9592 ldapvi_1.7-11.debian.tar.xz
Bug#1057581: marked as done (node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type declarations.)
Your message dated Fri, 26 Apr 2024 15:49:10 + with message-id and subject line Bug#1057581: fixed in node-get-stream 8.0.1-11 has caused the Debian Bug report #1057581, regarding node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type declarations. 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.) -- 1057581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-clipanion Version: 3.2.1+dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with nodejs dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs /!\ website/package.json not found Unable to load website workspaces field found in package.json Found debian/nodejs/additional_components Link ./node_modules/tslib -> /usr/share/nodejs/tslib Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha Link ./node_modules/typescript -> /usr/share/nodejs/typescript Link ./node_modules/@rollup/plugin-typescript -> /usr/share/nodejs/@rollup/plugin-typescript Link ./node_modules/@types/chai -> /usr/share/nodejs/@types/chai Link ./node_modules/ts-node -> /usr/share/nodejs/ts-node Link ./node_modules/@types/chai-as-promised -> /usr/share/nodejs/@types/chai-as-promised Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node Link ./node_modules/get-stream -> /usr/share/nodejs/get-stream /!\ website/package.json not found Unable to load website Link ./node_modules/typanion -> /usr/share/nodejs/typanion Found debian/nodejs/additional_components dh_auto_build --buildsystem=nodejs /!\ website/package.json not found Unable to load website workspaces field found in package.json Found debian/nodejs/additional_components Found debian/nodejs/./build cd ./. && sh -ex debian/nodejs/./build + rollup -c --bundleConfigAsCjs [36m [1m/<>/sources/advanced/builtins/definitions.ts, /<>/sources/advanced/builtins/help.ts, /<>/sources/advanced/builtins/index.ts, /<>/sources/advanced/builtins/version.ts, /<>/sources/advanced/Cli.ts, /<>/sources/advanced/Command.ts, /<>/sources/advanced/HelpCommand.ts, /<>/sources/advanced/index.ts, /<>/sources/advanced/options/Array.ts, /<>/sources/advanced/options/Boolean.ts, /<>/sources/advanced/options/Counter.ts, /<>/sources/advanced/options/index.ts, /<>/sources/advanced/options/Proxy.ts, /<>/sources/advanced/options/Rest.ts, /<>/sources/advanced/options/String.ts, /<>/sources/advanced/options/utils.ts, /<>/sources/constants.ts, /<>/sources/core.ts, /<>/sources/errors.ts, /<>/sources/format.ts, /<>/sources/platform/browser.ts, /<>/sources/platform/node.ts[22m → [1mlib, lib[22m...[39m [1m[33m(!) The "preserveModules" option is deprecated. Use the "output.preserveModules" option instead.[39m[22m [90mhttps://rollupjs.org/https://rollupjs.org/configuration-options/#output-preservemodules[39m [32mcreated [1mlib, lib[22m in [1m3.7s[22m[39m + cp -a sources/platform/package.json lib/platform/ + debian/apply-publish-config ./package.json dh_auto_test --buildsystem=nodejs /!\ website/package.json not found Unable to load website workspaces field found in package.json Found debian/nodejs/additional_components ln -s ../. node_modules/clipanion /bin/sh -ex debian/tests/pkg-js/test + FORCE_COLOR=1 mocha --require ts-node/register --extension ts tests/specs --exclude tests/specs/browser.test.ts --exclude tests/specs/treeshake.test.ts TSError: ⨯ Unable to compile TypeScript: tests/tools.ts(1,54): error TS2307: Cannot find module 'get-stream' or its corresponding type declarations. at createTSError (/usr/share/nodejs/ts-node/src/index.ts:865:12) at reportTSError (/usr/share/nodejs/ts-node/src/index.ts:869:19) at getOutput (/usr/share/nodejs/ts-node/src/index.ts:1083:36) at Object.compile (/usr/share/nodejs/ts-node/src/index.ts:1439:41) at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1623:30) at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) at Object.require.extensions. [as .ts] (/usr/share/nodejs/ts-node/src/index.ts:1627:12) at Module.load (node:internal/modules/cjs/loader:1197:32) at Function.Module._load (node:internal/modules/cjs/loader:1013:12) at Module.require (node:internal/modules/cjs/loader:1225:19) at require
Bug#1056196: marked as done (python3-onelogin-saml2: Please package new version 1.16.0, as current version will FTBFS soon)
Your message dated Fri, 26 Apr 2024 18:20:41 + with message-id and subject line Bug#1056196: fixed in python3-onelogin-saml2 1.16.0-1 has caused the Debian Bug report #1056196, regarding python3-onelogin-saml2: Please package new version 1.16.0, as current version will FTBFS soon 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.) -- 1056196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python3-onelogin-saml2 Version: 1.12.0-3 Severity: important I've recently fixed a build error related to expired certificates used in the tests. However, I see that the current package in unstable will FTBFS in the future: https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/python3-onelogin-saml2_1.12.0-3.rbuild.log.gz This is from the build log: Current time: Fri Dec 20 10:52:08 -12 2024 and I can reproduce the error by using the "libfaketime" package in this way: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 FAKETIME="+1y" dpkg-buildpackage -uc -us -b So, before bothering upstream and telling them that the tests still fail, I'd like to see a more recent version in unstable, then I will be able to see if there are more things to backport for stable or not. Thanks. --- End Message --- --- Begin Message --- Source: python3-onelogin-saml2 Source-Version: 1.16.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python3-onelogin-saml2, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python3-onelogin-saml2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 19:56:00 +0200 Source: python3-onelogin-saml2 Architecture: source Version: 1.16.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexandre Detiste Closes: 1056196 Changes: python3-onelogin-saml2 (1.16.0-1) unstable; urgency=medium . * Team upload. * New upstream version 1.16.0 (Closes: #1056196) * remove old extraneous dependencies on python3-mock & python3-six * use new dh-sequence-python3 * run test with pytest like upstream does * set Rules-Requires-Root: no . [ Colin Watson ] * Apply patch from https://github.com/SAML-Toolkits/python3-saml/pull/399 to fix failing testValidateTimestamps. Checksums-Sha1: 5b8e965f0684a261043c0756e573f839f35010c2 2338 python3-onelogin-saml2_1.16.0-1.dsc 6641e973546be3df3db89254b74fbac56bb3ddda 3578998 python3-onelogin-saml2_1.16.0.orig.tar.gz f3aa9c2995df74e2e87479ff46f698532b915971 5504 python3-onelogin-saml2_1.16.0-1.debian.tar.xz ca423bd69362e10f1c1905a5309f606567f6d2dc 7311 python3-onelogin-saml2_1.16.0-1_source.buildinfo Checksums-Sha256: 69cf796ff0f07253b01a8ab7dfec8e0f77cb9e0643b9e955c2c942a6a494fb01 2338 python3-onelogin-saml2_1.16.0-1.dsc 41c41d986b0ef66635aa53abe51dfe0e09b1fb07a8803cbbdc861c3f82b6d15a 3578998 python3-onelogin-saml2_1.16.0.orig.tar.gz 1c25a269e97e9a7b46fb744a7356d5c66214e9715bfb2fa0a2266aa45e0717e3 5504 python3-onelogin-saml2_1.16.0-1.debian.tar.xz e76c2c8c4499e3a144857a26683bdf8f73e92745d56d30d7ada10a73fb76237b 7311 python3-onelogin-saml2_1.16.0-1_source.buildinfo Files: 2f2b24ebbc91e2ec7cf239c4cbe98e61 2338 python optional python3-onelogin-saml2_1.16.0-1.dsc 9857f093e6b860e51138010aa01ca31a 3578998 python optional python3-onelogin-saml2_1.16.0.orig.tar.gz 57f15537ffba670433aa9f47255ff813 5504 python optional python3-onelogin-saml2_1.16.0-1.debian.tar.xz b272396163c1c99f4060a62a9434d531 7311 python optional python3-onelogin-saml2_1.16.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYr63IRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpNIA/+Jn6CdR4dwnRmtGlrx1kSn/WcF2DGeV91 Ji72bKq2prAosjSflZMTetFl5Cmua+W3+tgSNU4KzUnedh3AV58CINjfK1Nex7tP FHI89yENRcSCAQ0nOn2xig+JJTOsPkCrFjm/45IVHeyID0tBmJE8GCoEYXq6mTE5 hMHyDgWQl0yhf+7hqE00hCt3F4/35F+LR/8mSjuc9Fy9GssLSdSM/4Vz6W0j+frU
Bug#1069385: marked as done (FTBFS: dh_installdocs: error: Requested unknown package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...)
Your message dated Fri, 26 Apr 2024 18:49:41 + with message-id and subject line Bug#1069385: fixed in clanlib 1.0~svn3827-11.2 has caused the Debian Bug report #1069385, regarding FTBFS: dh_installdocs: error: Requested unknown package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ... 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.) -- 1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clanlib Version: 1.0~svn3827-11.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > make[3]: Nothing to be done for 'install-exec-am'. > make[3]: Nothing to be done for 'install-data-am'. > make[3]: Leaving directory '/<>' > make[2]: Leaving directory '/<>' > make[1]: Leaving directory '/<>' >dh_install >debian/rules override_dh_installdocs-arch > make[1]: Entering directory '/<>' > dh_installdocs --link-doc=libclanapp-1.0v5 > dh_installdocs: error: Requested unknown package libclanapp-1.0v5 via > --link-doc, expected one of: libclanapp-1.0t64 libclanlib-dev clanlib-doc > make[1]: *** [debian/rules:49: override_dh_installdocs-arch] Error 25 The full build log is available from: http://qa-logs.debian.net/2024/04/20/clanlib_1.0~svn3827-11.1_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: clanlib Source-Version: 1.0~svn3827-11.2 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of clanlib, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated clanlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Apr 2024 21:29:44 + Source: clanlib Architecture: source Version: 1.0~svn3827-11.2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Steve Langasek Closes: 1067616 1069385 Changes: clanlib (1.0~svn3827-11.2) unstable; urgency=medium . * Non-maintainer upload. * Fix dep from -dev package to point to current runtime lib name. Closes: #1069385. * debian/patches/64-bit-time-t-compat.patch: compatibility with 64-bit time_t. Closes: #1067616. Checksums-Sha1: 73c4490a8aa6952bfe1e8db507a338fc53dcdb93 2395 clanlib_1.0~svn3827-11.2.dsc fd7ba9b0c52627f8932553e6ec12d02b6f89463f 130488 clanlib_1.0~svn3827-11.2.debian.tar.xz 393aed6f50eb343579e4bf19388955e1e6fd9221 5268 clanlib_1.0~svn3827-11.2_source.buildinfo Checksums-Sha256: 314060999cb0ad3a0bd6a50ef8f73c1a4c1211cdee2cd05da596b88b03109f6e 2395 clanlib_1.0~svn3827-11.2.dsc feebb45876f330995ef1e632e666346af0a0b1cda00338cff2b1144728308cf1 130488 clanlib_1.0~svn3827-11.2.debian.tar.xz 430b8e03ca2ebc350bc21e66e993bc7fd7c773de62322f3cfaed23a1160b3130 5268 clanlib_1.0~svn3827-11.2_source.buildinfo Files: 5ace6f4667a97d0162b072531d99fc91 2395 libs optional clanlib_1.0~svn3827-11.2.dsc d692cde148c56a9ba119144ffe72714d 130488 libs optional clanlib_1.0~svn3827-11.2.debian.tar.xz eab5787ab0a4aef8f744caa56ceeac4f 5268 libs optional clanlib_1.0~svn3827-11.2_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#1067616: marked as done (FTBFS: error: ‘struct input_event’ has no member named ‘time’)
Your message dated Fri, 26 Apr 2024 18:49:41 + with message-id and subject line Bug#1067616: fixed in clanlib 1.0~svn3827-11.2 has caused the Debian Bug report #1067616, regarding FTBFS: error: ‘struct input_event’ has no member named ‘time’ 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.) -- 1067616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clanlib Version: 1.0~svn3827-11.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=clanlib=armel=1.0%7Esvn3827-11.1=1711185366=0 GLX/input_device_linuxevent.cpp: In member function ‘virtual void CL_InputDevice_LinuxEvent::keep_alive()’: GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no member named ‘time’ 269 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report Sync" ); | ^~~~ GLX/input_device_linuxevent.cpp:269:91: error: ‘struct input_event’ has no member named ‘time’ 269 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report Sync" ); | ^~~~ GLX/input_device_linuxevent.cpp:274:72: error: ‘struct input_event’ has no member named ‘time’ 274 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, | ^~~~ GLX/input_device_linuxevent.cpp:274:91: error: ‘struct input_event’ has no member named ‘time’ 274 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, | ^~~~ GLX/input_device_linuxevent.cpp:283:72: error: ‘struct input_event’ has no member named ‘time’ 283 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, | ^~~~ GLX/input_device_linuxevent.cpp:283:91: error: ‘struct input_event’ has no member named ‘time’ 283 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: clanlib Source-Version: 1.0~svn3827-11.2 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of clanlib, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated clanlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Apr 2024 21:29:44 + Source: clanlib Architecture: source Version: 1.0~svn3827-11.2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Steve Langasek Closes: 1067616 1069385 Changes: clanlib (1.0~svn3827-11.2) unstable; urgency=medium . * Non-maintainer upload. * Fix dep from -dev package to point to current runtime lib name. Closes: #1069385. * debian/patches/64-bit-time-t-compat.patch: compatibility with 64-bit time_t. Closes: #1067616. Checksums-Sha1: 73c4490a8aa6952bfe1e8db507a338fc53dcdb93 2395 clanlib_1.0~svn3827-11.2.dsc fd7ba9b0c52627f8932553e6ec12d02b6f89463f 130488 clanlib_1.0~svn3827-11.2.debian.tar.xz 393aed6f50eb343579e4bf19388955e1e6fd9221 5268 clanlib_1.0~svn3827-11.2_source.buildinfo Checksums-Sha256: 314060999cb0ad3a0bd6a50ef8f73c1a4c1211cdee2cd05da596b88b03109f6e 2395 clanlib_1.0~svn3827-11.2.dsc feebb45876f330995ef1e632e666346af0a0b1cda00338cff2b1144728308cf1 130488 clanlib_1.0~svn3827-11.2.debian.tar.xz 430b8e03ca2ebc350bc21e66e993bc7fd7c773de62322f3cfaed23a1160b3130 5268 clanlib_1.0~svn3827-11.2_source.buildinfo Files: 5ace6f4667a97d0162b072531d99fc91 2395 libs optional clanlib_1.0~svn3827-11.2.dsc d692cde148c56a9ba119144ffe72714d 130488 libs optional clanlib_1.0~svn3827-11.2.debian.tar.xz eab5787ab0a4aef8f744caa56ceeac4f
Bug#1069818: marked as done (FTBFS: tests failed)
Your message dated Fri, 26 Apr 2024 12:05:31 + with message-id and subject line Bug#1069818: fixed in toolz 0.12.1-1 has caused the Debian Bug report #1069818, regarding FTBFS: tests failed 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.) -- 1069818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: toolz Version: 0.12.0-2 Severity: serious Tags: ftbfs === FAILURES === test_inspect_wrapped_property _ def test_inspect_wrapped_property(): class Wrapped(object): def __init__(self, func): self.func = func def __call__(self, *args, **kwargs): return self.func(*args, **kwargs) @property def __wrapped__(self): return self.func func = lambda x: x wrapped = Wrapped(func) assert inspect.signature(func) == inspect.signature(wrapped) > assert num_required_args(Wrapped) is None E AssertionError: assert 1 is None E+ where 1 = num_required_args(.Wrapped'>) toolz/tests/test_inspect_args.py:485: AssertionError -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: toolz Source-Version: 0.12.1-1 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of toolz, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated toolz 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: Fri, 26 Apr 2024 12:47:29 +0100 Source: toolz Architecture: source Version: 0.12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1069818 Changes: toolz (0.12.1-1) unstable; urgency=medium . * Team upload. * New upstream release: - Minimal maintenance to support Python 3.12. * Fix test failure on Python 3.11.9/3.12.3/main (closes: #1069818). Checksums-Sha1: 157cef3c60b2e193053cdf5d8f13d87b710ed967 2234 toolz_0.12.1-1.dsc 63a52090028bf5c16f7087f5ccaeb3fdea0014d9 94974 toolz_0.12.1.orig.tar.gz eb85426482979be65373159a663b84de16dbfb62 4500 toolz_0.12.1-1.debian.tar.xz Checksums-Sha256: f2e979a9834380b9b6a84f933c29ce2e4830f69de49894a8cd04552bd63c6f99 2234 toolz_0.12.1-1.dsc c2207d17a773209c50ae4038f2523ce9435b2fc43c5a8d69a0d96dd1967426c0 94974 toolz_0.12.1.orig.tar.gz 2e2e43535db1ce630adc3f2a0c0ad258e323aed288640507515a830102efadfc 4500 toolz_0.12.1-1.debian.tar.xz Files: ad9c5d7732b8c83fa39bac5512f2eadf 2234 python optional toolz_0.12.1-1.dsc 79dff938a0cb1cac59c2f67591d0c86a 94974 python optional toolz_0.12.1.orig.tar.gz c83402c5a142b85c831dadcc3c4ef579 4500 python optional toolz_0.12.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrlQYACgkQOTWH2X2G UAuB9hAAsgAr+F7oT0r6XEEJ0yn3awOfG9GczvZy50iDMMn26KAtGNkAN2zM+UWL jihekL9I9NmZagmqAVdaz4q+jmKapnehRRfGri/U6xxgrp9hDlyQR07Kdqgfk7M9 nAPjAZAjzh5acjP1UI/L2tUI2BsLVI3kou9NvtVd125WSfCXlPHmbxQsbwJdNhta jyjSBcsXPuJ2VmSQhNYdz3eT/Kf3LPmfsAmVwf9vyIgQAQuNE8eDqo7gYNUS1VCB 4Ovgjyk5se1WyC39ye7AprUlQO0QMfW4JSuLiXYjUo/PEqLV7ywy2pQl8OeLb2NP XObL/1B2OQQ6nSgQOL9rqbiJNtkmD0Qz9BvWiAtBSXfUdmzPK/xY4ALTmvE8Yg5r 47PXmZAoB6vK/g+8v4nCTW9VYsHpillJNCCUhzMPFDNlHVthM9z0W9H4W12LbJEg 0ybwESkLjVRgDIDfvqh8dsbm81b7/Vd8Yb0OffXBTVVz6kQxCrF7MnHQyo7/HczB
Bug#1069360: marked as done (python-cytoolz: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 26 Apr 2024 15:03:18 +
with message-id
and subject line Bug#1069360: fixed in python-cytoolz 0.12.2-2
has caused the Debian Bug report #1069360,
regarding python-cytoolz: FTBFS on arm64: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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.)
--
1069360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cytoolz
Version: 0.12.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config
> [1/5] Cythonizing cytoolz/dicttoolz.pyx
> [2/5] Cythonizing cytoolz/functoolz.pyx
> [3/5] Cythonizing cytoolz/itertoolz.pyx
> [4/5] Cythonizing cytoolz/recipes.pyx
> [5/5] Cythonizing cytoolz/utils.pyx
> running config
> I: pybuild base:311: python3.11 setup.py config
> [1/5] Cythonizing cytoolz/utils.pyx
> [2/5] Cythonizing cytoolz/dicttoolz.pyx
> [3/5] Cythonizing cytoolz/functoolz.pyx
> [4/5] Cythonizing cytoolz/itertoolz.pyx
> [5/5] Cythonizing cytoolz/recipes.pyx
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build
> [1/5] Cythonizing cytoolz/utils.pyx
> [2/5] Cythonizing cytoolz/dicttoolz.pyx
> [3/5] Cythonizing cytoolz/functoolz.pyx
> [4/5] Cythonizing cytoolz/itertoolz.pyx
> [5/5] Cythonizing cytoolz/recipes.pyx
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/_signatures.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/_version.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/compatibility.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/__init__.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/operator.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/exceptions.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/__init__.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/itertoolz.pyx ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/recipes.pyx ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/utils.pyx ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/dicttoolz.pyx ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/functoolz.pyx ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/itertoolz.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/cpython.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/__init__.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/dicttoolz.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/utils.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/functoolz.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/recipes.pxd ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_functoolz.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_serialization.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_doctests.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_embedded_sigs.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_tlz.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_dev_skip_test.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_dicttoolz.py ->
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_none_safe.py ->
>
Bug#1069816: marked as done (Autopkgtests fail)
Your message dated Fri, 26 Apr 2024 12:52:07 +
with message-id
and subject line Bug#1069816: fixed in python-argcomplete 3.3.0-1
has caused the Debian Bug report #1069816,
regarding Autopkgtests fail
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.)
--
1069816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-argcomplete
Version: 3.1.4-1
Severity: serious
https://ci.debian.net/packages/p/python-argcomplete/unstable/amd64/45886560/
102s ==
102s ERROR: test_repl_parse_after_complete
(__main__.TestArgcompleteREPL.test_repl_parse_after_complete)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 925, in
test_repl_parse_after_complete
102s args = p.parse_args(["--foo", "spam", "bar"])
102s^^
102s File "/usr/lib/python3.12/argparse.py", line 1908, in parse_args
102s args, argv = self.parse_known_args(args, namespace)
102s ^^
102s File "/usr/lib/python3.12/argparse.py", line 1941, in parse_known_args
102s namespace, args = self._parse_known_args(args, namespace)
102s ^^^
102s File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 299, in _parse_known_args
102s start_index = consume_optional(start_index)
102s ^
102s File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 165, in consume_optional
102s action, option_string, explicit_arg = option_tuple
102s ^^^
102s ValueError: too many values to unpack (expected 3)
102s
102s ==
102s FAIL: test_choices (__main__.TestArgcomplete.test_choices)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 170, in test_choices
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '-h'
102s '--help'
102s '--ship'
102s Items in the second set but not the first:
102s 'speedboat'
102s 'submarine'
102s
102s ==
102s FAIL: test_completers (__main__.TestArgcomplete.test_completers)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 291, in
test_completers
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--url'
102s '--email'
102s '-h'
102s '--help'
102s Items in the second set but not the first:
102s 'http://url1'
102s 'http://url2'
102s
102s ==
102s FAIL: test_default_completer
(__main__.TestArgcomplete.test_default_completer)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 415, in
test_default_completer
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--one'
102s '--many'
102s Items in the second set but not the first:
102s 'test/'
102s
102s ==
102s FAIL: test_escape_special_chars
(__main__.TestArgcomplete.test_escape_special_chars)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 823, in
test_escape_special_chars
102s self.assertEqual(set(self.run_completer(make_parser(), "prog -1 ")),
{r"bar\<\$\>baz "})
102s AssertionError: Items in the first set but not the second:
102s '-1'
102s '-2'
102s '-3'
102s Items in the second set but not the first:
102s 'bar\\<\\$\\>baz '
102s
102s
Bug#1061780: marked as done (python3-argcomplete: zsh support not in description)
Your message dated Fri, 26 Apr 2024 12:52:07 + with message-id and subject line Bug#1061780: fixed in python-argcomplete 3.3.0-1 has caused the Debian Bug report #1061780, regarding python3-argcomplete: zsh support not in description 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.) -- 1061780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-argcomplete Version: 3.1.4-1 The package description mentions only bash, but zsh is supported too since v3.0. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: python-argcomplete Source-Version: 3.3.0-1 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of python-argcomplete, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated python-argcomplete 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: Fri, 26 Apr 2024 13:28:45 +0100 Source: python-argcomplete Architecture: source Version: 3.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1061780 1069816 Changes: python-argcomplete (3.3.0-1) unstable; urgency=medium . * Team upload. * New upstream release: - Preserve compatibility with argparse option tuples of length 4. This update is required to use argcomplete on Python 3.11.9+ or 3.12.3+ (closes: #1069816, LP: #2063129). * Mention zsh in package description (closes: #1061780). Checksums-Sha1: cc493dcb3fd57128a7d5b3bf82cc502712b41ec3 2518 python-argcomplete_3.3.0-1.dsc 64c233a0c7bb6214d128d8f9c6c0d3cd16d77235 81832 python-argcomplete_3.3.0.orig.tar.gz ed8dd369dc74a352c267856f7dc101c7a8ccacda 7164 python-argcomplete_3.3.0-1.debian.tar.xz Checksums-Sha256: 82902ca327e547a5bf6d634f10c4f473ecd6ecb17a252351b45ff818e83ce88d 2518 python-argcomplete_3.3.0-1.dsc fd03ff4a5b9e6580569d34b273f741e85cd9e072f3fe3eba4891c70eda62 81832 python-argcomplete_3.3.0.orig.tar.gz 87942aaf7d337c5c1ac3a9017632b81cea0d2607f52cf6b75baa6c8f8b37b23e 7164 python-argcomplete_3.3.0-1.debian.tar.xz Files: f67a90cd0dacaab107f622c08eb1 2518 python optional python-argcomplete_3.3.0-1.dsc 255e2c9f2cdb18f88d1dc8de9b78a072 81832 python optional python-argcomplete_3.3.0.orig.tar.gz 3862993c02bf26c23fac68955fef7528 7164 python optional python-argcomplete_3.3.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrnj4ACgkQOTWH2X2G UAtdGw/+KmCmICIQHSLX91fUU6pV5wIIT/ccwTmZ8PY1BnR8D9Ndfwh/4i8EewrO 6bMRKLp7F7aS2QfjBC4K7ZOd0Wa/ALEvZD/5/1FKNba2EmGXGDhmVdGolfW/+x7Y wO7UPYY5jwe0fT0BV07J1yLu4LcEFsGRYuQspRN6H0xUQXi2xjIgdUXbOFK+k+dT ywKB85K/SxE1fSgyl8V20YbBnHpkk7Dfccmv7Gfiddjj570lk7PRywwDH22VAJNf wH29T2Z6TQROrQsIXXaJFFMM0ycZsvqP700lPNFpYsMSNzvWrVKpsNEMTLncD2zl rFBaViIWyFbEmkqNWz4sX8WTbp4cX3RGqYnWAlAMgfe/qUzoTe6X+FNtHU9VoGBD zMsT990LpTPXrEpBdgH/ySGhpZ7gwIAGaLdM5YZNPX/3IDUokpdALX7gAKvKleeK GmzQTNnjElbE/i8baeOnMWanEE8HDja3ztCyHgoxLZM9uY8ir55Bxa74Yep7rZI/ 28+f9MwZmAmQHruk/Klqej2rvMJ3H8vhNU9rstrnVni6u6SG9Y5dqTGKuBb30Y8w kJc4gToxI8odWrnBIeBtaQo9ghN+Ia4FqPu24dBoZKyFCqSNF0oXqkEiDztdamLJ AmsZb4hsZdPDqTZrjsQx1qKo7ZX4mZek2iUVhiQcYscs2ISufoA= =vG1e -END PGP SIGNATURE- pgpTSMVYEIjp1.pgp Description: PGP signature --- End Message ---
Bug#1069817: marked as done (Autopkgtests fail)
Your message dated Fri, 26 Apr 2024 13:12:20 + with message-id and subject line Bug#1069817: fixed in python-exceptiongroup 1.2.1-1 has caused the Debian Bug report #1069817, regarding Autopkgtests fail 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.) -- 1069817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-exceptiongroup Version: 1.2.0-1 Severity: serious https://ci.debian.net/packages/p/python-exceptiongroup/unstable/amd64/45886580/ 47s === FAILURES === 47s ___ DeepRecursionInSplitAndSubgroup.test_deep_split 47s tests/test_exceptions.py:375: in test_deep_split 47s with self.assertRaises(RecursionError): 47s E AssertionError: RecursionError not raised 47s __ DeepRecursionInSplitAndSubgroup.test_deep_subgroup __ 47s tests/test_exceptions.py:380: in test_deep_subgroup 47s with self.assertRaises(RecursionError): 47s E AssertionError: RecursionError not raised -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-exceptiongroup depends on: ii python3 3.11.8-1 python3-exceptiongroup recommends no packages. python3-exceptiongroup suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: python-exceptiongroup Source-Version: 1.2.1-1 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of python-exceptiongroup, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated python-exceptiongroup 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: Fri, 26 Apr 2024 13:42:11 +0100 Source: python-exceptiongroup Architecture: source Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1069817 Changes: python-exceptiongroup (1.2.1-1) unstable; urgency=medium . * Team upload. * New upstream release: - Fix test failure on Python 3.12.3 (closes: #1069817). Checksums-Sha1: 5152d02cfc98caef06db8e6a7a9fbb17fb938f4f 2220 python-exceptiongroup_1.2.1-1.dsc 6a82af27b1b1b0b4a2159d7f91f852543a04573f 28203 python-exceptiongroup_1.2.1.orig.tar.gz 10fb12a032882f81a4356368cf1a17f909590717 3856 python-exceptiongroup_1.2.1-1.debian.tar.xz 2cb8b006a87eb4306f830999c44ea2cbfa3d6e0a 6970 python-exceptiongroup_1.2.1-1_source.buildinfo Checksums-Sha256: bcbce2a4d0078a7edf7d7114f73ee773786887e68642de52e7588221a43af4db 2220 python-exceptiongroup_1.2.1-1.dsc b59b2c0cee4423a01ca6dba773efac4dd6390e3908e36ed222d683ce827c8f3b 28203 python-exceptiongroup_1.2.1.orig.tar.gz 682be05f009cb8bf4031e616beab4eb6c21ff06bab4beb9187ed406a8fc02f03 3856 python-exceptiongroup_1.2.1-1.debian.tar.xz c0aeda428a06f398b5d01cae9a979745024fed4a0d2626c7e6e25accedde68da 6970 python-exceptiongroup_1.2.1-1_source.buildinfo Files: 9723f3bda1dff420cf016405235d7dd7 2220 python optional python-exceptiongroup_1.2.1-1.dsc 7c9f0f77ee6cbe4c5cb33662b4d59889 28203 python optional python-exceptiongroup_1.2.1.orig.tar.gz 0744e3d73104ca225f480cbf07b00d89 3856 python optional python-exceptiongroup_1.2.1-1.debian.tar.xz 4c74c0cd636cef63185335778d2cb69f 6970 python optional python-exceptiongroup_1.2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrohoACgkQOTWH2X2G
Bug#1067366: marked as done (mirrorbits: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25)
Your message dated Fri, 26 Apr 2024 15:01:29 + with message-id and subject line Bug#1067366: fixed in mirrorbits 0.5.1+git20240203.4e34d9b+ds1-2 has caused the Debian Bug report #1067366, regarding mirrorbits: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25 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.) -- 1067366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mirrorbits Version: 0.5.1+git20240203.4e34d9b+ds1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- -buildmode=pie -ldflags '-X > github.com/etix/mirrorbits/core.VERSION=v0.5.1+git20240203.4e34d9b+ds1 -X > github.com/etix/mirrorbits/core.BUILD=0.5.1+git20240203.4e34d9b+ds1-1 -X > github.com/etix/mirrorbits/config.TEMPLATES_PATH=/usr/share/mirrorbits/templates/' > cd _build && go install -trimpath -v -p 8 -buildmode=pie -ldflags "-X > github.com/etix/mirrorbits/core.VERSION=v0.5.1+git20240203.4e34d9b+ds1 -X > github.com/etix/mirrorbits/core.BUILD=0.5.1+git20240203.4e34d9b+ds1-1 -X > github.com/etix/mirrorbits/config.TEMPLATES_PATH=/usr/share/mirrorbits/templates/" > github.com/etix/mirrorbits github.com/etix/mirrorbits/cli > github.com/etix/mirrorbits/config github.com/etix/mirrorbits/core > github.com/etix/mirrorbits/daemon github.com/etix/mirrorbits/database > github.com/etix/mirrorbits/database/interfaces > github.com/etix/mirrorbits/database/upgrader > github.com/etix/mirrorbits/database/v1 github.com/etix/mirrorbits/filesystem > github.com/etix/mirrorbits/http github.com/etix/mirrorbits/logs > github.com/etix/mirrorbits/mirrors github.com/etix/mirrorbits/network > github.com/etix/mirrorbits/process github.com/etix/mirrorbits/rpc > github.com/etix/mirrorbits/scan github.com/etix/mirrorbits/testing > github.com/etix/mirrorbits/utils > internal/goexperiment > internal/coverage/rtcov > internal/unsafeheader > internal/godebugs > internal/goos > internal/cpu > internal/goarch > internal/itoa > runtime/internal/atomic > runtime/internal/syscall > math/bits > unicode/utf8 > internal/race > internal/abi > internal/chacha8rand > runtime/internal/math > runtime/internal/sys > sync/atomic > unicode > cmp > encoding > crypto/internal/alias > slices > crypto/subtle > internal/bytealg > math > crypto/internal/boring/sig > log/internal > internal/nettrace > container/list > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > vendor/golang.org/x/crypto/internal/alias > google.golang.org/grpc/serviceconfig > runtime > internal/reflectlite > sync > internal/testlog > google.golang.org/grpc/internal/buffer > google.golang.org/grpc/internal/grpcsync > internal/bisect > internal/singleflight > runtime/cgo > errors > internal/godebug > sort > strconv > path > io > internal/oserror > internal/safefilepath > vendor/golang.org/x/net/dns/dnsmessage > internal/intern > syscall > math/rand > crypto/internal/nistec/fiat > bytes > strings > hash > reflect > crypto > net/netip > crypto/internal/randutil > bufio > regexp/syntax > crypto/rc4 > hash/crc32 > vendor/golang.org/x/text/transform > net/http/internal/ascii > html > text/tabwriter > google.golang.org/grpc/encoding > golang.org/x/text/transform > time > internal/syscall/execenv > internal/syscall/unix > regexp > internal/fmtsort > encoding/binary > google.golang.org/grpc/backoff > google.golang.org/grpc/internal/grpcrand > context > io/fs > internal/poll > google.golang.org/grpc/keepalive > google.golang.org/grpc/internal/backoff > golang.org/x/net/context > google.golang.org/grpc/tap > embed > crypto/md5 > crypto/cipher > crypto/internal/edwards25519/field > encoding/base64 > vendor/golang.org/x/crypto/internal/poly1305 > crypto/internal/nistec > os > crypto/internal/edwards25519 > golang.org/x/sys/unix > crypto/internal/boring > crypto/des > encoding/pem > crypto/sha1 > crypto/sha256 > crypto/aes > crypto/sha512 > crypto/hmac > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/hkdf > crypto/ecdh > fmt > path/filepath > io/ioutil > net > vendor/golang.org/x/sys/cpu > google.golang.org/grpc/internal/envconfig > os/signal > vendor/golang.org/x/crypto/chacha20poly1305 > os/exec > encoding/hex > log > flag > encoding/json > gopkg.in/yaml.v3 > math/big > net/url > github.com/pkg/errors > github.com/etix/mirrorbits/core >
Bug#1031387: marked as done (supertuxkart: Fails to compile due to inescaped +, bug in shaderc)
Your message dated Fri, 26 Apr 2024 15:52:05 + with message-id and subject line Bug#1031387: fixed in supertuxkart 1.4+dfsg-4 has caused the Debian Bug report #1031387, regarding supertuxkart: Fails to compile due to inescaped +, bug in shaderc 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.) -- 1031387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: supertuxkart Version: testing Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: rishincutc...@gmail.com Dear Maintainer, * What led up to the situation? Attempting to backport supertuxkart, necessary to backport glslang aswell. * What exactly did you do (or not do) that was effective (or ineffective)? Compiled with fakeroot debian/rules binary * What was the outcome of this action? Failed to build due to cd /home/rishi/build/supertuxkart/supertuxkart-1.4+dfsg/obj-x86_64-linux-gnu/lib/shaderc/libshaderc && /usr/bin/ar -M < shaderc_combined.ar +Syntax error in archive script, line 1 Appears to be an issue with cmake and shadercc not properly escaping '+' character: https://github.com/google/shaderc/issues/473 * What outcome did you expect instead? Successful (test) compile -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: supertuxkart Source-Version: 1.4+dfsg-4 Done: Vincent Cheng We believe that the bug you reported is fixed in the latest version of supertuxkart, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Cheng (supplier of updated supertuxkart package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 07:04:48 -0700 Source: supertuxkart Built-For-Profiles: noudeb Architecture: source Version: 1.4+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Vincent Cheng Closes: 995771 1031386 1031387 1057463 Changes: supertuxkart (1.4+dfsg-4) unstable; urgency=medium . [ Reiner Herrmann ] * Use system shaderc instead of embedded copy. (Closes: #1057463, #1031387) * Use system angelscript instead of embedded copy. (Closes: #995771) . [ Vincent Cheng ] * Declare versioned build-dep on glslang-dev. (Closes: #1031386) * Bump Standards version to 4.7.0, no changes required. Checksums-Sha1: 9b9647df6ac4e308bbf7b8fb675ec75dc6b0aaef 2512 supertuxkart_1.4+dfsg-4.dsc e43c7cbbfadfbc4f60df957fec09ec49ce9e8c2f 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Checksums-Sha256: 00185ac4844a3d1d07afce7d471baba6ee9a598d26f537dfca1bbeba0baf3a3f 2512 supertuxkart_1.4+dfsg-4.dsc 1902e786bf6d0d3c1d97bd1f1ff2e5fc35ddd4fcae5ef43be8ebbceee3e6642c 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Files: 25e3fab2533034c245750e6c3c6b479c 2512 games optional supertuxkart_1.4+dfsg-4.dsc 7b97db9de2168a513ac94356a6262aa1 2287220 games optional supertuxkart_1.4+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmYrvJMACgkQju3MG6of Mv+fiBAA30lbYcDCIosN4jIkt6EBV+hFGJdm97q60QIfQjnlr/lX5urdOjjw7OfC dbcHC00+IrIXVdi4cJ0nYylgkWDFIWn66LJkP3vOaxEE55rKTK1/j9j7Yn0hxeOe doFsGtkg9/vevyfxqQ+8QWHMD0oUc9oQos12fFy14yDcYC2AWaTWLCLv9FKoaoaB AaZr9JfCRQdWdu+4vZaanBVuOVYdxWPSjvHUC20zTA1A84rvojriFG04vEhr4wii tuiC/PU1Kis9b/0cv2JKwpFmBpjIVUFACl5tqKXl/4XBu6k5sHzTHczPIP5kMiXa DV3Fvo2EkyxbzrhazYdTko9XpIkv17vpFPl5gWFCmI5RkUOFF7NkWLil+vxCQ2HP cTe+ietHjoCwGcc62/GqAxHvGcW9ExNlO5LjI4RsuhsGgg1kw5c3cCeOy7W7sbPI hZ/Uml3pdlgm86rh4/UCK1nRzxx+CYFT4+XTF7/VM55AW+DDT+kNofgDBuOzObff
Bug#1058322: marked as done (supertuxkart: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in namespace ‘std’ does not name a template type)
Your message dated Fri, 26 Apr 2024 15:52:05 +
with message-id
and subject line Bug#1057463: fixed in supertuxkart 1.4+dfsg-4
has caused the Debian Bug report #1057463,
regarding supertuxkart: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in
namespace ‘std’ does not name a template type
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.)
--
1057463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supertuxkart
Version: 1.4+dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/lib/tinygettext && /usr/bin/c++
> -DDISABLE_ICONV -DENABLE_IPV6 -DSUPERTUXKART_VERSION=\"1.4\" -DVERSION=0.1.0
> -I/<>/lib/graphics_utils
> -I/<>/lib/graphics_engine/include
> -I/<>/lib/shaderc/libshaderc/include
> -I/<>/lib/enet/include -I/<>/lib/bullet/src
> -I/<>/lib/tinygettext/include -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++0x -O2 -DNDEBUG -MD -MT
> lib/tinygettext/CMakeFiles/tinygettext.dir/src/dictionary.o -MF
> CMakeFiles/tinygettext.dir/src/dictionary.o.d -o
> CMakeFiles/tinygettext.dir/src/dictionary.o -c
> /<>/lib/tinygettext/src/dictionary.cpp
> In file included from /usr/include/glslang/Include/Types.h:47,
> from /usr/include/glslang/Include/intermediate.h:57,
> from
> /usr/include/glslang/MachineIndependent/localintermediate.h:42,
> from /usr/include/glslang/SPIRV/SpvTools.h:50,
> from /usr/include/glslang/SPIRV/GlslangToSpv.h:42,
> from
> /<>/lib/shaderc/libshaderc_util/src/compiler.cc:23:
> /usr/include/glslang/Include/SpirvIntrinsics.h:120:10: error: ‘variant’ in
> namespace ‘std’ does not name a template type
> 120 | std::variant value;
> | ^~~
> /usr/include/glslang/Include/SpirvIntrinsics.h:120:5: note: ‘std::variant’ is
> only available from C++17 onwards
> 120 | std::variant value;
> | ^~~
> /usr/include/glslang/Include/SpirvIntrinsics.h: In constructor
> ‘glslang::TSpirvTypeParameter::TSpirvTypeParameter(const
> glslang::TIntermConstantUnion*)’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:100:60: error: ‘value’ was not
> declared in this scope
> 100 | TSpirvTypeParameter(const TIntermConstantUnion* arg) { value =
> arg; }
> |^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In constructor
> ‘glslang::TSpirvTypeParameter::TSpirvTypeParameter(const glslang::TType*)’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:101:45: error: ‘value’ was not
> declared in this scope
> 101 | TSpirvTypeParameter(const TType* arg) { value = arg; }
> | ^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In member function ‘const
> glslang::TIntermConstantUnion* glslang::TSpirvTypeParameter::getAsConstant()
> const’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:105:13: error: ‘value’ was not
> declared in this scope
> 105 | if (value.index() == 0)
> | ^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In member function ‘const
> glslang::TType* glslang::TSpirvTypeParameter::getAsType() const’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:111:13: error: ‘value’ was not
> declared in this scope
> 111 | if (value.index() == 1)
> | ^
> [ 2%] Building CXX object
> lib/bullet/CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
> cd /<>/obj-x86_64-linux-gnu/lib/bullet && /usr/bin/c++
> -DSUPERTUXKART_VERSION=\"1.4\" -I/<>/lib/bullet/src -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -DNDEBUG -MD -MT
> lib/bullet/CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
> -MF
> CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o.d
> -o
> CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
> -c
>
Bug#995771: marked as done (supertuxkart: Please depends on angelscript-dev)
Your message dated Fri, 26 Apr 2024 15:52:05 + with message-id and subject line Bug#995771: fixed in supertuxkart 1.4+dfsg-4 has caused the Debian Bug report #995771, regarding supertuxkart: Please depends on angelscript-dev 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.) -- 995771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: supertuxkart Version: 1.3+dfsg1-1 Severity: normal Dear Maintainer, supertuxkart fails to build on armhf on Ubuntu impish: https://github.com/supertuxkart/stk-code/issues/4638 As said in that issue supertuxkart could use angelscript-dev if available, and that would also avoid the build issue in the embedded angelscript. So, please add angelscript-dev as a build dependency. Thanks. --- End Message --- --- Begin Message --- Source: supertuxkart Source-Version: 1.4+dfsg-4 Done: Vincent Cheng We believe that the bug you reported is fixed in the latest version of supertuxkart, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Cheng (supplier of updated supertuxkart package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 07:04:48 -0700 Source: supertuxkart Built-For-Profiles: noudeb Architecture: source Version: 1.4+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Vincent Cheng Closes: 995771 1031386 1031387 1057463 Changes: supertuxkart (1.4+dfsg-4) unstable; urgency=medium . [ Reiner Herrmann ] * Use system shaderc instead of embedded copy. (Closes: #1057463, #1031387) * Use system angelscript instead of embedded copy. (Closes: #995771) . [ Vincent Cheng ] * Declare versioned build-dep on glslang-dev. (Closes: #1031386) * Bump Standards version to 4.7.0, no changes required. Checksums-Sha1: 9b9647df6ac4e308bbf7b8fb675ec75dc6b0aaef 2512 supertuxkart_1.4+dfsg-4.dsc e43c7cbbfadfbc4f60df957fec09ec49ce9e8c2f 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Checksums-Sha256: 00185ac4844a3d1d07afce7d471baba6ee9a598d26f537dfca1bbeba0baf3a3f 2512 supertuxkart_1.4+dfsg-4.dsc 1902e786bf6d0d3c1d97bd1f1ff2e5fc35ddd4fcae5ef43be8ebbceee3e6642c 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Files: 25e3fab2533034c245750e6c3c6b479c 2512 games optional supertuxkart_1.4+dfsg-4.dsc 7b97db9de2168a513ac94356a6262aa1 2287220 games optional supertuxkart_1.4+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmYrvJMACgkQju3MG6of Mv+fiBAA30lbYcDCIosN4jIkt6EBV+hFGJdm97q60QIfQjnlr/lX5urdOjjw7OfC dbcHC00+IrIXVdi4cJ0nYylgkWDFIWn66LJkP3vOaxEE55rKTK1/j9j7Yn0hxeOe doFsGtkg9/vevyfxqQ+8QWHMD0oUc9oQos12fFy14yDcYC2AWaTWLCLv9FKoaoaB AaZr9JfCRQdWdu+4vZaanBVuOVYdxWPSjvHUC20zTA1A84rvojriFG04vEhr4wii tuiC/PU1Kis9b/0cv2JKwpFmBpjIVUFACl5tqKXl/4XBu6k5sHzTHczPIP5kMiXa DV3Fvo2EkyxbzrhazYdTko9XpIkv17vpFPl5gWFCmI5RkUOFF7NkWLil+vxCQ2HP cTe+ietHjoCwGcc62/GqAxHvGcW9ExNlO5LjI4RsuhsGgg1kw5c3cCeOy7W7sbPI hZ/Uml3pdlgm86rh4/UCK1nRzxx+CYFT4+XTF7/VM55AW+DDT+kNofgDBuOzObff XxJrvQ5G75mevHpMjmS7n5jUdlXd9VlgSYd+tmxhLPr8EjFMCwnP7k7y8USaFbZ+ aM4687bfhpJtAPS88XORPooi8xyilWirWDhgvbEmzdPyVgDkBmFUXGwDmzVegcH9 sOrr9yOzzSAinManttLZnU5zsecqz/0gUlEoeWAhJ4CV1wfvMQ0= =4Ewm -END PGP SIGNATURE- pgpIlG5Q7MDGM.pgp Description: PGP signature --- End Message ---
Bug#1031386: marked as done (supertuxkart: Depends on newer version of glslang)
Your message dated Fri, 26 Apr 2024 15:52:05 + with message-id and subject line Bug#1031386: fixed in supertuxkart 1.4+dfsg-4 has caused the Debian Bug report #1031386, regarding supertuxkart: Depends on newer version of glslang 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.) -- 1031386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: supertuxkart Version: testing Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: rishincutc...@gmail.com Dear Maintainer, * What led up to the situation? Attempted to backport package to stable. Installed build-dependencies with mk-build-deps --install --remove * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to build with fakeroot debian/rules binary. * What was the outcome of this action? Recieved error relating to glslang::EShTargetSpv_1_6, and compilation failed. Was able to continue compilation after backporting glslang and it's dependencies * What outcome did you expect instead? Build-dependency should require newer version so that mk-build-deps errors to force new version. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: supertuxkart Source-Version: 1.4+dfsg-4 Done: Vincent Cheng We believe that the bug you reported is fixed in the latest version of supertuxkart, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Cheng (supplier of updated supertuxkart package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 07:04:48 -0700 Source: supertuxkart Built-For-Profiles: noudeb Architecture: source Version: 1.4+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Vincent Cheng Closes: 995771 1031386 1031387 1057463 Changes: supertuxkart (1.4+dfsg-4) unstable; urgency=medium . [ Reiner Herrmann ] * Use system shaderc instead of embedded copy. (Closes: #1057463, #1031387) * Use system angelscript instead of embedded copy. (Closes: #995771) . [ Vincent Cheng ] * Declare versioned build-dep on glslang-dev. (Closes: #1031386) * Bump Standards version to 4.7.0, no changes required. Checksums-Sha1: 9b9647df6ac4e308bbf7b8fb675ec75dc6b0aaef 2512 supertuxkart_1.4+dfsg-4.dsc e43c7cbbfadfbc4f60df957fec09ec49ce9e8c2f 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Checksums-Sha256: 00185ac4844a3d1d07afce7d471baba6ee9a598d26f537dfca1bbeba0baf3a3f 2512 supertuxkart_1.4+dfsg-4.dsc 1902e786bf6d0d3c1d97bd1f1ff2e5fc35ddd4fcae5ef43be8ebbceee3e6642c 2287220 supertuxkart_1.4+dfsg-4.debian.tar.xz Files: 25e3fab2533034c245750e6c3c6b479c 2512 games optional supertuxkart_1.4+dfsg-4.dsc 7b97db9de2168a513ac94356a6262aa1 2287220 games optional supertuxkart_1.4+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmYrvJMACgkQju3MG6of Mv+fiBAA30lbYcDCIosN4jIkt6EBV+hFGJdm97q60QIfQjnlr/lX5urdOjjw7OfC dbcHC00+IrIXVdi4cJ0nYylgkWDFIWn66LJkP3vOaxEE55rKTK1/j9j7Yn0hxeOe doFsGtkg9/vevyfxqQ+8QWHMD0oUc9oQos12fFy14yDcYC2AWaTWLCLv9FKoaoaB AaZr9JfCRQdWdu+4vZaanBVuOVYdxWPSjvHUC20zTA1A84rvojriFG04vEhr4wii tuiC/PU1Kis9b/0cv2JKwpFmBpjIVUFACl5tqKXl/4XBu6k5sHzTHczPIP5kMiXa DV3Fvo2EkyxbzrhazYdTko9XpIkv17vpFPl5gWFCmI5RkUOFF7NkWLil+vxCQ2HP cTe+ietHjoCwGcc62/GqAxHvGcW9ExNlO5LjI4RsuhsGgg1kw5c3cCeOy7W7sbPI hZ/Uml3pdlgm86rh4/UCK1nRzxx+CYFT4+XTF7/VM55AW+DDT+kNofgDBuOzObff XxJrvQ5G75mevHpMjmS7n5jUdlXd9VlgSYd+tmxhLPr8EjFMCwnP7k7y8USaFbZ+ aM4687bfhpJtAPS88XORPooi8xyilWirWDhgvbEmzdPyVgDkBmFUXGwDmzVegcH9
Bug#1069815: marked as done (wesnoth-1.8-server: new package installs systemd unit in aliased location)
Your message dated Fri, 26 Apr 2024 13:57:54 + with message-id and subject line Bug#1069815: fixed in wesnoth-1.18 1:1.18.0-2 has caused the Debian Bug report #1069815, regarding wesnoth-1.8-server: new package installs systemd unit in aliased location 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.) -- 1069815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wesnoth-1.18-server Version: 1:1.17.26-1 Severity: serious Justification: do not introduce aliased files into Debian Hi, I noticed that wesnoth-1.18-server is a new package and installs a file below /lib, which is an aliased location that we try to empty to complete the /usr-move transition via DEP17. I am filing this bug at RC-severity to stop it from migrating to trixie and hope you agree with this. Please downgrade if you disagree though note that this kind of issue will become an RC-bug for all packages later in the trixie cycle. The simplest fix to this problem is changing SYSTEMD_SERVICE = debian/wesnoth-$(BRANCH_VERSION)-server/lib/systemd/system/wesnoth-$(BRANCH_VERSION)-server.service in debian/rules and move the file to /usr/lib. This is mostly safe for backports, except that bookworm's debhelper will fail to generate necessary maintainer scripts. Please bump your debhelper dependency to 13.11.6 (available in bookworm-backports). Alternatively, adding dh-sequence-movetousr to Build-Depends should also resolve the matter, but for a new package I'd prefer to fix this right from the start. Both solutions are likely applicable to other wesnoth versions as well, though we don't consider those RC-bugs yet. Helmut --- End Message --- --- Begin Message --- Source: wesnoth-1.18 Source-Version: 1:1.18.0-2 Done: Vincent Cheng We believe that the bug you reported is fixed in the latest version of wesnoth-1.18, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Cheng (supplier of updated wesnoth-1.18 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 06:07:52 -0700 Source: wesnoth-1.18 Built-For-Profiles: noudeb Architecture: source Version: 1:1.18.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Vincent Cheng Closes: 1069815 Changes: wesnoth-1.18 (1:1.18.0-2) unstable; urgency=medium . * Install systemd unit file in UsrMerge-allowed location. (Closes: #1069815) - Declare build-dep on debhelper (>= 13.11.6~). Checksums-Sha1: d7373f7bff0ff3cd8e5e1881c2202b71b439ab03 4333 wesnoth-1.18_1.18.0-2.dsc 3219fa87680fc6b77e553ddee6e78766e7891943 179812 wesnoth-1.18_1.18.0-2.debian.tar.xz Checksums-Sha256: 0d1688a326a09b611c39779e20bad7fec0f0306603e768272515a5fd22db7d68 4333 wesnoth-1.18_1.18.0-2.dsc a433444dc008c18f9e8a6104fe243d764c79309678ebef8cb846d9a71bf0c0f4 179812 wesnoth-1.18_1.18.0-2.debian.tar.xz Files: e090205140738c026e374b7513308e7e 4333 games optional wesnoth-1.18_1.18.0-2.dsc 9b2d390259ad51de5834e2fd82e14e32 179812 games optional wesnoth-1.18_1.18.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmYrqwoACgkQju3MG6of Mv8d2Q//VCB812zD+EcTVz/dCEZV5kRpQofg+r2g08CxkLuNXu/K8Wt0qwdySPJc 4a2SlGTQxKn6T/HcXZ4y7rR5JeadPpUAGFN2gCo98CnoGFtwfOLL5LyJuzUaihwX KkCPJlMuS+BTJ8XfcAOP1SsAvLGfM2XT9X0L0eEz3SqKwUEgWTdimaETz6tX5k+a Xdt+ihGSiGErbH+w3DdfwykYMWfU62iuoGfLyRrDPaUF9DlNyealGfPJSHQSYiYT fWVFmtyMSwIHXFZ/xc6D9ANOY3Uj8Iqqz7Xz6HVqtOLYMqhSA9Qm45OSkeQ2hOzv CpZhY8n3GgaD3D2rRbEKdMwSpkqlPHfjg4iksJcKFV3HlQIQ2HPSwPwaPXFjcPDK 6Q6sqLQZnD8VzlWTbtPyracSjL60G9IbENq+KL5gZyCrU9ZgsDtLJQNcXT1u9fXr p4izRD1QMknmI2l5pQ17oMaEVdvYSrKS1ZIEP7PnvBMGYJDAC7Y+/xwGmySXaC89 AAfiP+A02IUQmDy7tDyv0mN8s7Lv49JQqxAhPW/0f1p9FTTAATk6eblZH4fbkm8H pREZ5yUGLeau/B407m7YsrDon+CRN3PM3IHffgGDP16SScfhBFDk+XUaHv8k+bBH qgWOc4T8y/9s5IUAmktZSxKOBeKzDnkQiQOmPrNtL9LbuqixFoM= =NiDI -END PGP SIGNATURE- pgp7FoZzHaKeb.pgp Description: PGP signature --- End Message ---
Bug#1067316: marked as done (gnucash-docs: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open sha
Your message dated Fri, 26 Apr 2024 12:35:18 + with message-id and subject line Bug#1067316: fixed in gnucash-docs 5.6-1 has caused the Debian Bug report #1067316, regarding gnucash-docs: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared object file: No such file or directory 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.) -- 1067316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnucash-docs Version: 5.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > [ 0%] Generating gnucash-guide.fo > cd /<>/build/zh/guide && /usr/bin/cmake -E make_directory > /<>/build/share/doc//zh > cd /<>/build/zh/guide && /usr/bin/xsltproc --path > /<>/docbook --xinclude --nonet -o > /<>/build/zh/guide/gnucash-guide.fo --stringparam > fop1.extensions 1 --stringparam variablelist.as.blocks 1 --stringparam > glosslist.as.blocks 1 /<>/zh/guide/../xsl/zh-fo.xsl > /<>/zh/guide/index.docbook > Making portrait pages on USletter paper (8.5inx11in) > [ 3%] Generating ../../share/doc/zh/gnucash-guide.pdf > cd /<>/build/zh/guide && /usr/bin/fop -l zh -c > /<>/build/zh/guide/fop.xconf -fo > /<>/build/zh/guide/gnucash-guide.fo -pdf > /<>/build/share/doc//zh/gnucash-guide.pdf > [warning] /usr/bin/fop: JVM flavor 'sun' not understood > [warning] /usr/bin/fop: Unable to locate serializer in /usr/share/java > [warning] /usr/bin/fop: Unable to locate xalan2 in /usr/share/java > [warning] /usr/bin/fop: Unable to locate xercesImpl in /usr/share/java > [WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting with > "Symbol,normal,400". > [WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. Substituting > with "ZapfDingbats,normal,400". > [WARN] FOUserAgent - Hyphenation pattern not found. URI: zh. > [INFO] FOUserAgent - Rendered page #1. > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 14384 millipoints. (See position > 18:448) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 15080 millipoints. (See position > 28:235) > [INFO] TTFFile - This is a TrueType collection file with 4 fonts > [INFO] TTFFile - Containing the following fonts: > [INFO] TTFFile - AR PL UKai CN <-- selected > [INFO] TTFFile - AR PL UKai HK > [INFO] TTFFile - AR PL UKai TW > [INFO] TTFFile - AR PL UKai TW MBE > [INFO] FOUserAgent - Rendered page #2. > [INFO] FOUserAgent - Rendered page #3. > [INFO] FOUserAgent - Rendered page #4. > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 98:462) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 100:237) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 102:237) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 104:299) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 105:241) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 106:241) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 107:303) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 108:237) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position > 109:237) > [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available > area in the inline-progression direction by 2000 millipoints. (See position >
Processed: closing 1067047
Processing commands for cont...@bugs.debian.org: > close 1067047 Bug #1067047 [src:gnucash] Buildng the package removes debian/.gitlab-ci.yml Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069608: marked as done (topplot: missing test-depends on python3-all)
Your message dated Fri, 26 Apr 2024 15:05:23 + with message-id and subject line Bug#1069608: fixed in topplot 0.2.2+repack-2 has caused the Debian Bug report #1069608, regarding topplot: missing test-depends on python3-all 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.) -- 1069608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: topplot Version: 0.2.2+repack-1 Tags: patch Severity: serious Justification: blocks testing migration of other packages topplot tries to run its autopkgtest in all versions of Python (which is good), but does not test-depend on all those versions of Python. This previously worked because numpy depended on them. However, this has now been removed (see #945824), causing topplot's autopkgtests to fail. Adding python3-all to the Depends in debian/*tests*/control should fix this bug, but I have not actually tested this. --- End Message --- --- Begin Message --- Source: topplot Source-Version: 0.2.2+repack-2 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of topplot, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated topplot 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: Fri, 26 Apr 2024 15:08:01 +0100 Source: topplot Architecture: source Version: 0.2.2+repack-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1069608 Changes: topplot (0.2.2+repack-2) unstable; urgency=medium . * Team upload. * Add python3-all to autopkgtest Depends (closes: #1069608). Checksums-Sha1: cdbe6d4f0279b6dad30b863bbfb71de70a17f9d7 2402 topplot_0.2.2+repack-2.dsc 3d82f6b2eff6e1edea62939b8e4655bb1bcb00f4 3472 topplot_0.2.2+repack-2.debian.tar.xz Checksums-Sha256: 103efd5cfaf1f3310beaae8ce60061303e1b50078a41043756d9d741af2dcf90 2402 topplot_0.2.2+repack-2.dsc 9833f2101df35241e326f912d61ab19fac29a81c0f5c45106ca9cc663ffe8975 3472 topplot_0.2.2+repack-2.debian.tar.xz Files: c7cd2265112964282d785f24b1382389 2402 utils optional topplot_0.2.2+repack-2.dsc 732739539cf9a29b67753e6b9dda5c82 3472 utils optional topplot_0.2.2+repack-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrtY0ACgkQOTWH2X2G UAumnBAAiY90VUC3I+Mmafxv7qFyaMTaFtW0dtR2FO/TfKKM4TC7cDqR73Qrln0o g2OgzYTeFpK6X31nSGg59wic7vDAIF1knPxNiBrildMLFVgKaJpWxFc90KvD5+N/ KajTBq2WnemMBB7ZUuTxjNNKzDLeftGaZlNvLuS+G4xyaU02iLElFBVMRKx4MMvi jfw7qgi7xiFRXXkVgPPnIlFDQcMQVhX9ww5fJNeJgkLADTxFM9nsjITIJkBrK2T4 bwYeobe2VUIEkEQbWEIspw/4zMuCuOJjyzrHnZ+PJeioWGSDXg0TIPYVVliS+RH9 gupMpgwmK+ETjHJ5YqFGe/ghuCjTgzNLSGjzZU8WKWo4jcDIJMMcMGFSFWpnpKiz JMsEYAGpjlIBT0hoPIMNoPwrQ5pgY6vtsHif9tSfRuJ0GdaECJVCx/mV79/b0cGS PByWnxucNLTlkEK5N7tk9DbZYQY8tmGY3Ig/lK0zInM4Qtj2Gqh8YvpoEfZZttBK XIUFbP4FRczqYdIGdFBK5YlU7yeaag1h5KyRJBkk48rila3ZNrb900iNZLM8dTs+ jwOWYaclvXQq4hzjd+z9fgeVQH8CyncORgGm6g+K9IofQ3q6ehRh7BnJmRQjvbek 0ta+KIhdcxc8kq6eNRFXBGfHTnKCpJlBuaWmH45+cgKe++cR8zA= =h6OC -END PGP SIGNATURE- pgpEh64HRbnCO.pgp Description: PGP signature --- End Message ---
Bug#1069703: marked as done (dynamips: requires rebuild for t64 transition)
Your message dated Sat, 27 Apr 2024 00:03:29 +0200 with message-id and subject line Re: dynamips: requires rebuild for t64 transition has caused the Debian Bug report #1069703, regarding dynamips: requires rebuild for t64 transition 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.) -- 1069703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dynamips Version: 0.2.14-1 Severity: serious Tags: sid trixie X-Debbugs-Cc: sramac...@debian.org dynamips is in non-free without auto build support. Please rebuild the package against the t64 packages in unstable. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- On Tue, 23 Apr 2024 08:29:23 +0200 Sebastian Ramacher wrote: dynamips is in non-free without auto build support. Please rebuild the package against the t64 packages in unstable. Uploaded manually built binNMUs for amd64 and i386. In case there are more packages in non-free or contrib in need of a manual binNMU, please let me know. Andreas--- End Message ---
Bug#1044294: marked as done (goldendict-ng: Fails to build source after successful build)
Your message dated Fri, 26 Apr 2024 20:43:11 + with message-id and subject line Bug#1044294: fixed in goldendict-ng 24.02.16-2 has caused the Debian Bug report #1044294, regarding goldendict-ng: Fails to build source after successful build 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.) -- 1044294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: goldendict-ng Version: 23.07.25-1 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > > > dpkg-buildpackage: info: source package goldendict-ng > dpkg-buildpackage: info: source version 23.07.25-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Boyuan Yang > dpkg-source --before-build . > debian/rules clean > dh clean --buildsystem=cmake >dh_auto_clean -O--buildsystem=cmake >dh_autoreconf_clean -O--buildsystem=cmake >dh_clean -O--buildsystem=cmake > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building goldendict-ng using existing > ./goldendict-ng_23.07.25.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: error: cannot represent change to > src/scripts/jquery-3.6.0.slim.min.js: > dpkg-source: error: new version is symlink to > /usr/share/javascript/jquery/jquery.min.js > dpkg-source: error: old version is nonexistent > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/goldendict-ng_23.07.25-1_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: goldendict-ng Source-Version: 24.02.16-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of goldendict-ng, 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 1044...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated goldendict-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 14:58:09 -0400 Source: goldendict-ng Architecture: source Version: 24.02.16-2 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 1044294 1068176 Changes: goldendict-ng (24.02.16-2) unstable; urgency=medium . * d/p/e62dded0f62c143406df775b604e86cb933d92ee.patch: Fix reproducible-builds issue, patch from upstream. (Closes: #1068176) * d/rules: Clean src/scripts/jquery-3.6.0.slim.min.js in dh_clean. (Closes: #1044294) Checksums-Sha1: 505522afde154655fa00e2d0cfc2f979f31ad0ae 2360 goldendict-ng_24.02.16-2.dsc 7de6da3201832fdf0b1f9727820391e117562bbf 5134268
Bug#1068176: marked as done (goldendict-ng: please make the build reproducible)
Your message dated Fri, 26 Apr 2024 20:43:11 +
with message-id
and subject line Bug#1068176: fixed in goldendict-ng 24.02.16-2
has caused the Debian Bug report #1068176,
regarding goldendict-ng: please make the build reproducible
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.)
--
1068176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: goldendict-ng
Version: 23.12.26-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timezone
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
goldendict-ng could not be built reproducibly.
This is because it does not specify the "UTC" argument to CMake's
TIMESTAMP macro function, so the build time embedded in the final
binary, whilst based on SOURCE_DATE_EPOCH, varies by the build
timezone.
Patch attached.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0002-Reproducible-build.patch 1970-01-01
01:00:00.0 +0100
--- b/debian/patches/0002-Reproducible-build.patch 2024-04-01
11:02:36.411764040 +0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2024-04-01
+
+--- goldendict-ng-23.12.26.orig/CMakeLists.txt
goldendict-ng-23.12.26/CMakeLists.txt
+@@ -54,7 +54,7 @@ set(CMAKE_AUTORCC ON) # not included in
+ Things required during configuration
+
+ block() # generate version.txt
+-string(TIMESTAMP build_time)
++string(TIMESTAMP build_time UTC)
+ find_package(Git)
+ if (EXISTS "${CMAKE_SOURCE_DIR}/.git" AND GIT_FOUND)
+ execute_process(
--- a/debian/patches/series 2024-04-01 09:53:57.209332464 +0100
--- b/debian/patches/series 2024-04-01 11:02:35.515760642 +0100
@@ -1 +1,2 @@
0001-Disable-checkUpdate-by-default.patch
+0002-Reproducible-build.patch
--- End Message ---
--- Begin Message ---
Source: goldendict-ng
Source-Version: 24.02.16-2
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
goldendict-ng, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated goldendict-ng package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 26 Apr 2024 14:58:09 -0400
Source: goldendict-ng
Architecture: source
Version: 24.02.16-2
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang
Changed-By: Boyuan Yang
Closes: 1044294 1068176
Changes:
goldendict-ng (24.02.16-2) unstable; urgency=medium
.
* d/p/e62dded0f62c143406df775b604e86cb933d92ee.patch:
Fix reproducible-builds issue, patch from upstream. (Closes: #1068176)
* d/rules: Clean src/scripts/jquery-3.6.0.slim.min.js in dh_clean.
(Closes: #1044294)
Checksums-Sha1:
505522afde154655fa00e2d0cfc2f979f31ad0ae 2360 goldendict-ng_24.02.16-2.dsc
7de6da3201832fdf0b1f9727820391e117562bbf 5134268
goldendict-ng_24.02.16.orig.tar.xz
404b6740d2b23d9921b9b16a492125d7583e2b21 23452
goldendict-ng_24.02.16-2.debian.tar.xz
fb8c9c63c10abaeaba47b7be37718472e9a0af57 19033
goldendict-ng_24.02.16-2_amd64.buildinfo
Checksums-Sha256:
d1ac04168c6278b781d6159bc4e1bdceff5437f00a04b4a673654e510a624a50 2360
goldendict-ng_24.02.16-2.dsc
e626ca361f4e8607df4cbbf11b7441fc6563527da23b8d21d65c7458f1808cc8 5134268
goldendict-ng_24.02.16.orig.tar.xz
3336d6d601a5a8f3ae5d85ab6a6199721e1307b030ea6f2e4913241de870b1aa 23452
goldendict-ng_24.02.16-2.debian.tar.xz
0d66b1801ef7e383f748bf3db387fbdbee2d7547136410b8f70f7349635ddbb2 19033
goldendict-ng_24.02.16-2_amd64.buildinfo
Files:
0bca52a02c48cce77595c123d1ce4aa2 2360 utils optional
goldendict-ng_24.02.16-2.dsc
8d5767e0127d1e3fe8f6a3aa7dc51560 5134268 utils optional
goldendict-ng_24.02.16.orig.tar.xz
dace362793c728d5e5a9cc721e00 23452 utils optional
goldendict-ng_24.02.16-2.debian.tar.xz
f85f4de3e962df1db550ff578b906ad5 19033 utils
Bug#1064088: marked as done (gutenprint: FTBFS in unstable)
Your message dated Sat, 27 Apr 2024 00:19:32 + with message-id and subject line Bug#1064088: fixed in gutenprint 5.3.4.20220624T01008808d602-2 has caused the Debian Bug report #1064088, regarding gutenprint: FTBFS in unstable 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.) -- 1064088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gutenprint Version: 5.3.4.20220624T01008808d602-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble Dear maintainers, gutenprint now fails to build from source in unstable. Initially, it fails to build because debian/libgutenprintui2-2.symbols expects symbols to be present that are not part of this library's API but only a result of using yacc internally. Marking these symbols optional gets past this issue: (optional)yy_create_buffer@Base 5.3.0~pre1 (optional)yy_delete_buffer@Base 5.3.0~pre1 (optional)yy_flex_debug@Base 5.3.0~pre1 (optional)yy_flush_buffer@Base 5.3.0~pre1 (optional)yy_scan_buffer@Base 5.3.0~pre1 (optional)yy_scan_bytes@Base 5.3.0~pre1 (optional)yy_scan_string@Base 5.3.0~pre1 (optional)yy_switch_to_buffer@Base 5.3.0~pre1 (optional)yyalloc@Base 5.3.0~pre1 (optional)yychar@Base 5.3.0~pre1 (optional)yydebug@Base 5.3.1 [...] But then the package fails because dh_missing complains about files installed into debian/tmp not being included in any package: [...] make[1]: Leaving directory '/tmp/time-t/gutenprint-5.3.4.20220624T01008808d602' dh_missing dh_missing: warning: usr/share/gutenprint/doc/reference-html/a2128.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/a2128.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1723.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c1723.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c193.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c193.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1974.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c1974.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c199.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c199.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c38.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c38.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c463.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c463.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c47.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c47.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/f14.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/f14.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/index.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/index.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1675.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x1675.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1740.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x1740.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x2159.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x2159.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x270.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x270.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x66.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x66.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x78.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x78.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x961.html exists in
Bug#1064089: marked as done (gutenprint: NMU diff for 64-bit time_t transition)
Your message dated Sat, 27 Apr 2024 00:19:32 + with message-id and subject line Bug#1064089: fixed in gutenprint 5.3.4.20220624T01008808d602-2 has caused the Debian Bug report #1064089, regarding gutenprint: NMU diff for 64-bit time_t transition 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.) -- 1064089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gutenprint Version: 5.3.4.20220624T01008808d602-1 Severity: important Tags: patch User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified gutenprint as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for gutenprint. Please find the patch for this NMU attached. Unfortunately, due to unrelated bugs (bug #1064088), your package fails to build in unstable and therefore we will not be uploading an NMU for this. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gutenprint Source-Version: 5.3.4.20220624T01008808d602-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of gutenprint, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated gutenprint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 23:10:00 +0200 Source: gutenprint Architecture: source Version: 5.3.4.20220624T01008808d602-2 Distribution: unstable Urgency: medium Maintainer: Debian Printing Group Changed-By: Thorsten Alteholz Closes: 1064088 1064089 Changes: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium . * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. Checksums-Sha1: 263f3b632560f12513538b513e696e0db53eb8da 3210 gutenprint_5.3.4.20220624T01008808d602-2.dsc f070be098b05810df047571faa521c7cec690b54 95036 gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz a8e143047c6f88a82d89d031ccff7acd64497c0a 20798 gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo Checksums-Sha256: 6661d2a2c7a9c6615c188217c93ddb7db4635d24474cd61e2f7ac144e8fd7174 3210 gutenprint_5.3.4.20220624T01008808d602-2.dsc 858c4091f2d9418f9e35cb37b0d2bfe181a819ddd4a08c00eedfae8a1816bf68 95036 gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz 4e06c6331a979761b6d018a5cd9862099f92da2c2146ec6fb49de6501b07c7ca 20798 gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo Files: ea7ac1f5ff28e39aeaeb7108783a112a 3210 graphics optional gutenprint_5.3.4.20220624T01008808d602-2.dsc 51151ed4e4d37c3ee58d2a49eb1bf9ff 95036 graphics optional
Bug#1069374: marked as done (python-grpc-tools: FTBFS: aborting due to unexpected upstream changes in grpc_tools/_protoc_compiler.cpp (generated by cython))
Your message dated Sat, 27 Apr 2024 00:49:36 + with message-id and subject line Bug#1069374: fixed in python-grpc-tools 1.14.1-7 has caused the Debian Bug report #1069374, regarding python-grpc-tools: FTBFS: aborting due to unexpected upstream changes in grpc_tools/_protoc_compiler.cpp (generated by cython) 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.) -- 1069374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-grpc-tools Version: 1.14.1-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:311: python3.12 setup.py clean > /<>/setup.py:18: DeprecationWarning: pkg_resources is deprecated > as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > import pkg_resources > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:381: FutureWarning: > Cython directive 'language_level' not set, using '3str' for now (Py3). This > has changed from earlier releases! File: > /<>/grpc_tools/_protoc_compiler.pyx > tree = Parsing.p_module(s, pxd, full_module_name) > Compiling grpc_tools/_protoc_compiler.pyx because it changed. > [1/1] Cythonizing grpc_tools/_protoc_compiler.pyx > running clean > removing '/<>/.pybuild/cpython3_3.12_grpcio-tools/build' (and > everything under it) > 'build/bdist.linux-aarch64' does not exist -- can't clean it > 'build/scripts-3.12' does not exist -- can't clean it > I: pybuild base:311: python3.11 setup.py clean > /<>/setup.py:18: DeprecationWarning: pkg_resources is deprecated > as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > import pkg_resources > running clean > removing '/<>/.pybuild/cpython3_3.11_grpcio-tools/build' (and > everything under it) > 'build/bdist.linux-aarch64' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-grpc-tools using existing > ./python-grpc-tools_1.14.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory grpcio_tools.egg-info > dpkg-source: warning: ignoring deletion of file > grpcio_tools.egg-info/SOURCES.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > grpcio_tools.egg-info/PKG-INFO, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > grpcio_tools.egg-info/top_level.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > grpcio_tools.egg-info/requires.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > grpcio_tools.egg-info/dependency_links.txt, use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > python-grpc-tools-1.14.1/grpc_tools/_protoc_compiler.cpp > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-grpc-tools_1.14.1-6.diff.silkQD > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2024-04-20T03:15:38Z The full build log is available from: http://qa-logs.debian.net/2024/04/20/python-grpc-tools_1.14.1-6_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a
Bug#1056955: marked as done ([INTL:sv] Swedish strings for openldap debconf)
Your message dated Sat, 27 Apr 2024 00:49:23 + with message-id and subject line Bug#1056955: fixed in openldap 2.5.17+dfsg-1 has caused the Debian Bug report #1056955, regarding [INTL:sv] Swedish strings for openldap debconf 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.) -- 1056955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: openldap severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother# Translation of openldap debconf template to Swedish # Copyright (C) 2023 Martin Bagge # This file is distributed under the same license as the openldap package. # # Martin Ågren , 2008. # Martin Bagge , 2010, 2017, 2023 msgid "" msgstr "" "Project-Id-Version: openldap_2.4.10-2_sv\n" "Report-Msgid-Bugs-To: openl...@packages.debian.org\n" "POT-Creation-Date: 2021-08-16 01:12+\n" "PO-Revision-Date: 2023-11-27 09:37+0100\n" "Last-Translator: Martin Bagge / brother \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Type: boolean #. Description #: ../slapd.templates:1001 msgid "Omit OpenLDAP server configuration?" msgstr "Utelämna konfiguration av OpenLDAP-servern?" #. Type: boolean #. Description #: ../slapd.templates:1001 msgid "" "If you enable this option, no initial configuration or database will be " "created for you." msgstr "" "Om du aktiverar det här alternativet kommer ingen initial konfiguration " "eller databas att skapas åt dig." #. Type: select #. Choices #: ../slapd.templates:2001 msgid "always" msgstr "alltid " #. Type: select #. Choices #: ../slapd.templates:2001 msgid "when needed" msgstr "vid behov" #. Type: select #. Choices #: ../slapd.templates:2001 msgid "never" msgstr "aldrig" #. Type: select #. Description #: ../slapd.templates:2002 msgid "Dump databases to file on upgrade:" msgstr "Dumpa databaser till fil vid uppgradering:" #. Type: select #. Description #: ../slapd.templates:2002 msgid "" "Before upgrading to a new version of the OpenLDAP server, the data from your " "LDAP directories can be dumped into plain text files in the standard LDAP " "Data Interchange Format." msgstr "" "Innan du uppgraderar till en ny version av OpenLDAP-servern, kan datat från " "dina LDAP-kataloger dumpas till klartextfiler i standardformatet LDAP Data " "Interchange Format." #. Type: select #. Description #: ../slapd.templates:2002 msgid "" "Selecting \"always\" will cause the databases to be dumped unconditionally " "before an upgrade. Selecting \"when needed\" will only dump the database if " "the new version is incompatible with the old database format and it needs to " "be reimported. If you select \"never\", no dump will be done." msgstr "" "Väljer du \"alltid\" kommer databaserna alltid att dumpas före en " "uppgradering. Väljer du \"vid behov\" kommer databasen bara dumpas om den " "nya versionen är inkompatibel med det gamla databasformatet och måste " "återimporteras. Om du väljer \"aldrig\", kommer ingen dump göras." #. Type: string #. Description #: ../slapd.templates:3001 msgid "Directory to use for dumped databases:" msgstr "Katalog att dumpa databaser i:" #. Type: string #. Description #: ../slapd.templates:3001 msgid "" "Please specify the directory where the LDAP databases will be exported. In " "this directory, several LDIF files will be created which correspond to the " "search bases located on the server. Make sure you have enough free space on " "the partition where the directory is located. The first occurrence of the " "string \"VERSION\" is replaced with the server version you are upgrading " "from." msgstr "" "Ange den katalog dit LDAP-databaser ska exporteras. I denna katalog kommer " "flera LDIF-filer att skapas som svarar mot sökbaserna på servern. Se till " "att du har tillräckligt med ledigt utrymme på den partition där katalogen " "finns. Den första förekomsten av strängen \"VERSION\" ersätts med den " "serverversion du uppgraderar från." #. Type: boolean #. Description #: ../slapd.templates:4001 msgid "Move old database?" msgstr "Flytta gammal databas?" #. Type: boolean #. Description #: ../slapd.templates:4001 msgid "" "There are still files in /var/lib/ldap which will probably break the " "configuration process. If you enable this option, the maintainer scripts " "will move the old database files out of the way before creating a new " "database." msgstr "" "Det finns
Bug#1040382: marked as done (slapd: debian12 ships with slapd-2.5.13+dfsg-5 which crashes (segfault in dynlist.la).)
Your message dated Sat, 27 Apr 2024 00:49:23 + with message-id and subject line Bug#1040382: fixed in openldap 2.5.17+dfsg-1 has caused the Debian Bug report #1040382, regarding slapd: debian12 ships with slapd-2.5.13+dfsg-5 which crashes (segfault in dynlist.la). 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.) -- 1040382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slapd Version: 2.5.13+dfsg-5 Severity: important Dear Maintainer, openldap-2.5.14 (slapd-2.5.14) does not have this problem (i have compiled from source, installed and tested). please consider to replace slapd-2.5.13 by slpad-2.5.14 in debian12. thanks in advance, gustav -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages slapd depends on: ii adduser3.134 ii coreutils 9.1-1 ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers1.65.2 ii libargon2-10~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167 ii libc6 2.36-9 ii libcrypt1 1:4.4.33-2 ii libldap-2.5-0 2.5.13+dfsg-5 ii libltdl7 2.4.7-5 ii libodbc2 2.3.11-2 ii libperl5.365.36.0-7 ii libsasl2-2 2.1.28+dfsg-10 ii libwrap0 7.6.q-32 ii lsb-base 11.6 ii perl [libmime-base64-perl 5.36.0-7 ] ii psmisc 23.6-1 ii sysvinit-utils [lsb-base] 3.06-4 Versions of packages slapd recommends: ii ldap-utils 2.5.13+dfsg-5 Versions of packages slapd suggests: ii libsasl2-modules 2.1.28+dfsg-10 pn libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimd al -- Configuration Files: /etc/init.d/slapd changed [not included] -- debconf information: slapd/invalid_config: true slapd/dump_database_destdir: /var/backups/slapd-VERSION slapd/move_old_database: true slapd/dump_database: when needed slapd/upgrade_slapcat_failure: slapd/postinst_error: slapd/no_configuration: false shared/organization: softing.com slapd/purge_database: false slapd/password_mismatch: slapd/domain: softing.com --- End Message --- --- Begin Message --- Source: openldap Source-Version: 2.5.17+dfsg-1 Done: Ryan Tandy We believe that the bug you reported is fixed in the latest version of openldap, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Tandy (supplier of updated openldap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 16:09:29 -0700 Source: openldap Architecture: source Version: 2.5.17+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenLDAP Maintainers Changed-By: Ryan Tandy Closes: 1040382 1056955 Changes: openldap (2.5.17+dfsg-1) unstable; urgency=medium . * New upstream release. - fixed slapo-dynlist so it can't be global (ITS#10091) (Closes: #1040382) * debian/copyright: Exclude doc/guide/admin/guide.html from the upstream source, because the tool required to build it from source is not packaged in Debian. Fixes a Lintian error (source-is-missing). * Update Swedish debconf translation. (Closes: #1056955) Thanks to Martin Bagge and Anders Jonsson. * debian/salsa-ci.yml: Enable Salsa CI pipeline. Checksums-Sha1: c45b57d916229c5fc468bf0cad5a3993a5e7643e 3325 openldap_2.5.17+dfsg-1.dsc a66044ecf02b340eba9cdd6b7be72f18a8672aa5 3683156 openldap_2.5.17+dfsg.orig.tar.xz 409a250e297f6b5f1f686bcde4295c9434e9b2c9 169736
Bug#1066348: marked as done (hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration of function ‘orblite_init’ [-Werror=implicit-function-declaration])
Your message dated Fri, 26 Apr 2024 23:35:05 +
with message-id
and subject line Bug#1066348: fixed in hplip 3.22.10+dfsg0-5
has caused the Debian Bug report #1066348,
regarding hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration
of function ‘orblite_init’ [-Werror=implicit-function-declaration]
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.)
--
1066348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hplip
Version: 3.22.10+dfsg0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"HP\
> Linux\ Imaging\ and\ Printing\" -DPACKAGE_TARNAME=\"hplip\"
> -DPACKAGE_VERSION=\"3.22.10\" -DPACKAGE_STRING=\"HP\ Linux\ Imaging\ and\
> Printing\ 3.22.10\" -DPACKAGE_BUGREPORT=\"3.22.10\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"hplip\" -DVERSION=\"3.22.10\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 -DHAVE_PTHREAD_H=1
> -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBHPIP=1
> -DDISABLE_IMAGEPROCESSOR=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1
> -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBAVAHI=1
> -DHAVE_LIBAVAHI_CLIENT=1 -DHAVE_LIBAVAHI_COMMON=1
> -DHAVE_AVAHI_CLIENT_CLIENT_H=1 -DHAVE_AVAHI_COMMON_MALLOC_H=1
> -DHAVE_CUPS_CUPS_H=1 -DHAVE_CUPS_PPD_H=1 -DHAVE_LIBUSB_1_0_LIBUSB_H=1
> -DHAVE_PYTHON_H=1 -DHAVE_DBUS=1 -I. -Iip -Iio/hpmud -Iscan/sane -Iprnt/hpijs
> -Icommon/ -Iprotocol -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/dbus-1.0
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -Iprotocol -Iprotocol/discovery
> -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -I/usr/include/python3.11 -I/usr/include/python3.11 -DCONFDIR=\"/etc/hp\" -c
> -o libsane_hpaio_la-pml.lo `test -f 'scan/sane/pml.c' || echo
> './'`scan/sane/pml.c
> In file included from scan/sane/mfpdtf.c:28:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on
> non-class types [-Wattributes]
> 191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char*
> str, int radix);
> | ^~~~
> scan/sane/mfpdtf.c: In function ‘MfpdtfReadInnerBlock’:
> scan/sane/mfpdtf.c:476:13: warning: ignoring return value of ‘write’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
> 476 | write( mfpdtf->fdLog, buffer, r ); /* log raw rgb data,
> use imagemagick to display */
> | ^
> In file included from scan/sane/hpaio.h:32,
> from scan/sane/hpaio.c:48:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on
> non-class types [-Wattributes]
> 191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char*
> str, int radix);
> | ^~~~
> In file included from scan/sane/hpaio.c:57:
> scan/sane/sanei_debug.h:167: warning: "DBG" redefined
> 167 | # define DBGDBG_LOCAL
> |
> In file included from scan/sane/hpaio.c:41:
> protocol/discovery/avahiDiscovery.h:79: note: this is the location of the
> previous definition
>79 |#define DBG(args...)
> |
> scan/sane/hpaio.c: In function ‘GetCupsPrinters’:
> scan/sane/hpaio.c:202:4: warning: ‘httpConnectEncrypt’ is deprecated: Use
> httpConnect2 instead. [-Wdeprecated-declarations]
> 202 |if ((http = httpConnectEncrypt(cupsServer(), ippPort(),
> cupsEncryption())) == NULL)
> |^~
> In file included from /usr/include/cups/ipp.h:18,
> from /usr/include/cups/cups.h:28,
> from scan/sane/hpaio.c:37:
> /usr/include/cups/http.h:477:26: note: declared here
> 477 | extern http_t *httpConnectEncrypt(const char *host, int
> port, http_encryption_t encryption) _CUPS_DEPRECATED_1_7_MSG("Use
> httpConnect2 instead.");
> |
Bug#1069805: marked as done (scikit-build tries pip install during build)
Your message dated Sat, 27 Apr 2024 01:49:47 +
with message-id
and subject line Bug#1069805: fixed in scikit-build 0.17.6-2
has caused the Debian Bug report #1069805,
regarding scikit-build tries pip install during build
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.)
--
1069805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-build
Version: 0.17.6-1
Severity: serious
Tags: trixie sid ftbfs
scikit-build accesses network resources during the build:
process =
stdout = None, stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them,
or pass capture_output=True to capture both.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except: # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
> raise CalledProcessError(retcode, process.args,
output=stdout, stderr=stderr)
E subprocess.CalledProcessError: Command '['/usr/bin/python3.12',
'-m', 'pip', 'wheel', '--wheel-dir',
'/tmp/pytest-of-jspricke/pytest-21/wheelhouse0', '/build/package/package']'
returned non-zero exit status 1.
--- End Message ---
--- Begin Message ---
Source: scikit-build
Source-Version: 0.17.6-2
Done: Emmanuel Arias
We believe that the bug you reported is fixed in the latest version of
scikit-build, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
Bug#1065976: marked as done (python-levenshtein: FTBFS on arm{el,hf}: Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’
Your message dated Sat, 27 Apr 2024 02:36:45 +
with message-id
and subject line Bug#1065976: fixed in python-levenshtein 0.25.1-3
has caused the Debian Bug report #1065976,
regarding python-levenshtein: FTBFS on arm{el,hf}:
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’?
[-Werror=implicit-function-declaration]
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.)
--
1065976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-levenshtein
Version: 0.12.2-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=python-levenshtein=armel=0.12.2-3=1709900271=0
arm-linux-gnueabi-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall
-g -Werror=implicit-function-declaration -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12
-c Levenshtein/_levenshtein.c -o
build/temp.linux-armv8l-cpython-312/Levenshtein/_levenshtein.o
Levenshtein/_levenshtein.c: In function ‘levenshtein_common’:
Levenshtein/_levenshtein.c:731:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
731 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:732:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
732 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:746:12: error: implicit declaration of function
‘PyUnicode_GET_SIZE’; did you mean ‘PyDict_GET_SIZE’?
[-Werror=implicit-function-declaration]
746 | len1 = PyUnicode_GET_SIZE(arg1);
|^~
|PyDict_GET_SIZE
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’?
[-Werror=implicit-function-declaration]
749 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^~~~
| PyUnicode_AsUCS4
Levenshtein/_levenshtein.c:749:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
749 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^
Levenshtein/_levenshtein.c:750:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
750 | string2 = PyUnicode_AS_UNICODE(arg2);
| ^
Levenshtein/_levenshtein.c: In function ‘hamming_py’:
Levenshtein/_levenshtein.c:816:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
816 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:817:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
817 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:832:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
832 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^
Levenshtein/_levenshtein.c:833:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
833 | string2 = PyUnicode_AS_UNICODE(arg2);
| ^
Levenshtein/_levenshtein.c: In function ‘jaro_py’:
Levenshtein/_levenshtein.c:860:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
860 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:861:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
861 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:870:13: warning: assignment
Bug#1069518: marked as done (projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing conversion of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ {aka ‘short u
Your message dated Sat, 27 Apr 2024 02:36:37 +
with message-id
and subject line Bug#1069518: fixed in projecteur 0.10-3
has caused the Debian Bug report #1069518,
regarding projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing
conversion of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’}
to ‘__u16’ {aka ‘short unsigned int’} [-Werror=narrowing]
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.)
--
1069518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: projecteur
Version: 0.10-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include
> -I/<>/src
> -I/<>/obj-arm-linux-gnueabihf/version/projecteur -isystem
> /usr/include/arm-linux-gnueabihf/qt5 -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem
> /usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtQuick -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtQmlModels -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtQml -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtX11Extras -isystem
> /usr/include/arm-linux-gnueabihf/qt5/QtDBus -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
> -std=gnu++14 -Wall -Wextra -Werror -fPIC -MD -MT
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -MF
> CMakeFiles/projecteur.dir/src/devicescan.cc.o.d -o
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -c
> /<>/src/devicescan.cc
> /<>/src/deviceinput.cc: In member function ‘void
> InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
> /<>/src/deviceinput.cc:697:64: error: narrowing conversion of
> ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
> {aka ‘short unsigned int’} [-Werror=narrowing]
> 697 | events.emplace_back(input_event{{}, ie.type, ie.code,
> ie.value});
> | ~~~^
> /<>/src/deviceinput.cc:697:69: error: missing initializer for
> member ‘input_event::value’ [-Werror=missing-field-initializers]
> 697 | events.emplace_back(input_event{{}, ie.type, ie.code,
> ie.value});
> | ^
> /<>/src/deviceinput.cc: In lambda function:
> /<>/src/deviceinput.cc:893:55: error: narrowing conversion of
> ‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
> {aka ‘short unsigned int’} [-Werror=narrowing]
> 893 | struct input_event ie = {{}, de.type, de.code, de.value};
> |~~~^
> /<>/src/deviceinput.cc:893:60: error: missing initializer for
> member ‘input_event::value’ [-Werror=missing-field-initializers]
> 893 | struct input_event ie = {{}, de.type, de.code, de.value};
> |^
> /<>/src/deviceinput.cc: In member function ‘void
> InputMapper::addEvents(const KeyEvent&)’:
> /<>/src/deviceinput.cc:906:79: error: missing initializer for
> member ‘input_event::value’ [-Werror=missing-field-initializers]
> 906 | if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN,
> SYN_REPORT, 0}); }
> |
> ^
> [ 44%] Building CXX object CMakeFiles/projecteur.dir/src/deviceswidget.cc.o
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include
Bug#1061434: marked as done (python 3.12 extension not working)
Your message dated Sat, 27 Apr 2024 02:36:45 + with message-id and subject line Bug#1061434: fixed in python-levenshtein 0.25.1-3 has caused the Debian Bug report #1061434, regarding python 3.12 extension not working 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.) -- 1061434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-levenshtein Version: 0.12.2-2+b5 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 the python 3.12 extension is not working: $ python3.12 -c 'import Levenshtein' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/Levenshtein/__init__.py", line 1, in from Levenshtein import _levenshtein ImportError: /usr/lib/python3/dist-packages/Levenshtein/_levenshtein.cpython-312-x86_64-linux-gnu.so: undefined symbol: PyUnicode_AS_UNICODE --- End Message --- --- Begin Message --- Source: python-levenshtein Source-Version: 0.25.1-3 Done: Stuart Prescott We believe that the bug you reported is fixed in the latest version of python-levenshtein, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott (supplier of updated python-levenshtein 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: Sat, 27 Apr 2024 11:45:48 +1000 Source: python-levenshtein Architecture: source Version: 0.25.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team , Changed-By: Stuart Prescott Closes: 1061434 1065976 Changes: python-levenshtein (0.25.1-3) unstable; urgency=medium . * Team upload. * Upload to unstable. * Fix compilation with Python 3.12 (Closes: #1061434, #1065976) Checksums-Sha1: e4fc2dfede970145e68d3a9eb060f6ced925a43a 2297 python-levenshtein_0.25.1-3.dsc eb0466b2b7d7cd2cc323d49dbcfe53f07be25a9c 3940 python-levenshtein_0.25.1-3.debian.tar.xz 26a5c8845fff0dc2d43bb185658831706833ee96 10326 python-levenshtein_0.25.1-3_amd64.buildinfo Checksums-Sha256: 7efb1ca2ea32973030dd607c920c6237884bb5469d4d71570daa0b8c895015cf 2297 python-levenshtein_0.25.1-3.dsc 215302622d09516d909a53a7e1627a783b7a955318230c0b40714a20e948de2f 3940 python-levenshtein_0.25.1-3.debian.tar.xz e810f71d1cf9ad8678a0816d6b1d5c02189989b42e02d7984e3f2943f2aa5cc0 10326 python-levenshtein_0.25.1-3_amd64.buildinfo Files: 2f6a87198286d4515f529dc505f5bb9b 2297 python optional python-levenshtein_0.25.1-3.dsc 635cc5a73ce1afa3491159d6214a8675 3940 python optional python-levenshtein_0.25.1-3.debian.tar.xz 7281f80fd73a123655cb4b5039c3aa4a 10326 python optional python-levenshtein_0.25.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmYsWmAACgkQu8F+uxOW 8vfa4w//fyKawiyXV18HhuPT87QS9U3IPgMXPF7Fe+z0QDm85dYsgYZqDNbivNYD 5PocU97Fyg27rNsBzSvXujlCcXFClJrBhrIOyT6cF3C3b2sfrqCUv3CRJ3344mwc +uB+aDwl9a66jDUT9WjWSswqAG40Abag6YqVaMskrL88tI4hhxAMwXpCef16YO6C CKGRUQoohjgAQ1GoJ+mrWg8Qec9SzuTkLE7KxmX0aYoa7Lg0OV5y7Yyv64Ruk7WA +RG1ucvDPS90TQLBa6QxVADly64l4tM5Fl6VH5guSHl1Hp9HOVCRFElPCJViYXU6 03/3TsXWinf/RbzjNWYJ8Ev6hcApuNhc5rEzCvyTKMB+4OvB3Hlt1LLIjYlNkR6m u8ilm0loDFwoYs+5677Mtkwu+hWunleZ7pR/5X8AEnkWB2++X9KgJjsggbU4K4Sf f3HK1EHutCDazug3Cl1yMtcxog3AyJQU91U/ErgYwbXU9yLOze1q7lvZoopcD+RJ LYH6AmpgpOeqnUHNEw1s+6STP3CrEzn0E4rqI8uZ7iuqcRO2uik4bh3bs2D7RZ/k DPgmPfT94aZrTP8n6dUNRhW9qyMlvZy3Zzo6/kqQAw47mZih0SRkWaQhnAxu2Tlh 2YkjPs84zQ1+La55dN0DN6Oyh+cf4FiQvdmyrvPuklbuvYIHbaA= =XJXQ -END PGP SIGNATURE- pgpIlCEGSB_cR.pgp Description: PGP signature --- End Message ---
Bug#1067622: marked as done (FTBFS: error: missing initializer for member ‘input_event::value’)
Your message dated Sat, 27 Apr 2024 02:36:36 +
with message-id
and subject line Bug#1067622: fixed in projecteur 0.10-3
has caused the Debian Bug report #1067622,
regarding FTBFS: error: missing initializer for member ‘input_event::value’
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.)
--
1067622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: projecteur
Version: 0.10-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=projecteur=armel=0.10-2%2Bb2=1711185228=0
/<>/src/deviceinput.cc: In member function ‘void
InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
/<>/src/deviceinput.cc:697:64: error: narrowing conversion of
‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
697 | events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
| ~~~^
/<>/src/deviceinput.cc:697:69: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
697 | events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
| ^
/<>/src/deviceinput.cc: In lambda function:
/<>/src/deviceinput.cc:893:55: error: narrowing conversion of
‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
893 | struct input_event ie = {{}, de.type, de.code, de.value};
|~~~^
/<>/src/deviceinput.cc:893:60: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
893 | struct input_event ie = {{}, de.type, de.code, de.value};
|^
/<>/src/deviceinput.cc: In member function ‘void
InputMapper::addEvents(const KeyEvent&)’:
/<>/src/deviceinput.cc:906:79: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
906 | if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN,
SYN_REPORT, 0}); }
|
^
Note that this package enables -Werror.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: projecteur
Source-Version: 0.10-3
Done: Stuart Prescott
We believe that the bug you reported is fixed in the latest version of
projecteur, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated projecteur 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: Sat, 27 Apr 2024 11:43:27 +1000
Source: projecteur
Architecture: source
Version: 0.10-3
Distribution: experimental
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Stuart Prescott
Closes: 1067622 1069518
Changes:
projecteur (0.10-3) experimental; urgency=medium
.
* Fix FTBFS caused by t64 transition with local patch to change the
input_event struct at compile time (Closes: #1067622, #1069518)
* Update Standards-Version to 4.7.0 (no changes required).
Checksums-Sha1:
65862ffb69d7ec01bc97edece06a371fc0568124 2143 projecteur_0.10-3.dsc
089ff391137b3ea9ff37f0209ccd15a265f183a6 4188 projecteur_0.10-3.debian.tar.xz
3488530d3f449432bb246c254f9febf80d8cd6f3 12258
projecteur_0.10-3_amd64.buildinfo
Checksums-Sha256:
Bug#1069896: marked as done (python3-tqdm: internal version is wrongly reported as 0.0.0)
Your message dated Sat, 27 Apr 2024 03:24:10 + with message-id and subject line Bug#1069896: fixed in tqdm 4.66.2-3 has caused the Debian Bug report #1069896, regarding python3-tqdm: internal version is wrongly reported as 0.0.0 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.) -- 1069896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-tqdm Version: 4.66.2-1 Severity: normal Tags: patch X-Debbugs-Cc: cru...@debian.org Dear Maintainer, I noticed that your package doesn't know its own version number, due to upstream using setuptools-scm: > /usr/lib/python3.12/dist-packages/tqdm-0.0.0.dist-info/INSTALLER > /usr/lib/python3.12/dist-packages/tqdm-0.0.0.dist-info/top_level.txt https://packages.debian.org/trixie/all/python3-tqdm/filelist Attached is a patch to fix this. commit 57f42a5693cb8fd1c0f80a0f605396d18ae24a0c Author: Michael R. Crusoe Date: Fri Apr 26 17:35:10 2024 +0200 d/watch: switch to PyPI to grab the _version file. Fixes "0.0.0" version reporting. diff --git a/debian/control b/debian/control index 8738979..24c5b98 100644 --- a/debian/control +++ b/debian/control @@ -14,6 +14,7 @@ Build-Depends: python3-pytest-timeout , python3-rich , python3-setuptools, + python3-setuptools-scm, python3-tk , Rules-Requires-Root: no Standards-Version: 4.7.0 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: tqdm Source-Version: 4.66.2-3 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of tqdm, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated tqdm 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: Sat, 27 Apr 2024 04:54:43 +0200 Source: tqdm Architecture: source Version: 4.66.2-3 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1069896 Changes: tqdm (4.66.2-3) sid; urgency=medium . * Uploading to sid. * Updating to standards-version 4.7.0. * Adding python3-setuptools-scm to build-depends so tqdm outputs its version properly, thanks to Michael R. Crusoe (Closes: #1069896). Checksums-Sha1: d7b5483bdc92742e87af8f75d6bf85e274b4b658 2171 tqdm_4.66.2-3.dsc 38778e68427e808a82eb14a87129493c160ab27d 4232 tqdm_4.66.2-3.debian.tar.xz 224d52d58dc2b0d656baeac32bc5d8f6e6c2f3c5 8600 tqdm_4.66.2-3_amd64.buildinfo Checksums-Sha256: 12296900b7dd676054a2733ccf3e84c1beca6e1f62ebbb9eaed6cb26a96da86d 2171 tqdm_4.66.2-3.dsc bced6e98ef4517ac34f40ab20a7e541d5eade483b27ca7a6195fdd64515b5f7b 4232 tqdm_4.66.2-3.debian.tar.xz 13d8a39e1be71de80c7e0f6e7a481cceeab2fbfe3b5ca19dbe2d11da18a28390 8600 tqdm_4.66.2-3_amd64.buildinfo Files: e8519c11c977b684279b2720d20459a1 2171 python optional tqdm_4.66.2-3.dsc b8bd2087fdbf49b40f3eb1888e01c460 4232 python optional tqdm_4.66.2-3.debian.tar.xz 492ac2c51afc03caa94c480ba188b4c8 8600 python optional tqdm_4.66.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmYsbE4ACgkQVc8b+Yar ucchvBAAvYHKoPyj2r5JszeTWNMeRi/gddSGaym3hS0RKRtEi4T5oVsZdvr2ifjJ 8ZxndS6H/Cg354F5XlXWcXb0CLexcbJ7LMNAx4ptv1YyzaFKm1nHdfp3X23FgBkP Ea1YEqKdhdXU0uuBVcqSsqhQ5rgsHq4vpWiS7ePOY8UF+7Sf39hklWVyv55pxTcK IGbo8sU4vKj2QPHxwgsHbXIIJgyGnDgAXpHbHdEXVjGMPZShdtYsJXIXIgGu1Ymx mg7TTz/LHY/HRAYXsMnjm4zWBdKBS3zsx/2Vu67lCFaRZwnLa5DRoziNieN9IAXp SxKNfytkuF9MEsB3L6JWrnO0ugnAnmeKqt103TJs5qFsB6nm7BWeetm0rv/MkorG Q7j1p0KLmA8WjX89UtKkMvywDxt1bKYz/uMy0j2IJujygrFWMVLbtf2K8jQJh6up LT3epFc0gVCUnKnjdbB7oMBwxJ4U7X8UNI1ST/vctMro/tuNKFBwU2959hWffU6v qzz9Zv1gYeMPZIRXmhu57Su+Px2G5JK9qeoh9nL7Rtv18maNf5DamnsAB5w8isa1 uMJ8I0GpGceKad58Qut61GQnSN0sYyn+CUHNfycMvxFp8jXj/bTgYGj691r7ea63 EdgtjpxdtjocLOVMtvNY4f8oC4HUBXWWqojJqsXDxvViRSazq8o= =hc9o -END PGP SIGNATURE- pgpdlqPJMR387.pgp Description: PGP signature --- End Message ---
Processed: bts
Processing commands for cont...@bugs.debian.org: > close 994840 0.23.93-1 Bug #994840 [zbarcam-gtk] [PATCH] zbarcam-gtk fails on wayland Marked as fixed in versions zbar/0.23.93-1. Bug #994840 [zbarcam-gtk] [PATCH] zbarcam-gtk fails on wayland Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 994840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069888: marked as done (node-bunyan: FTBFS: failing tests)
Your message dated Sat, 27 Apr 2024 05:36:27 + with message-id and subject line Bug#1069888: fixed in node-bunyan 2.0.5+~cs4.4.3-3 has caused the Debian Bug report #1069888, regarding node-bunyan: FTBFS: failing tests 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.) -- 1069888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-bunyan Version: 2.0.5+~cs4.4.3-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs Link node_modules/exeunt -> ../exeunt Link node_modules/mv -> ../mv Link node_modules/safe-json-stringify -> ../safejsonstringify dh_auto_build --buildsystem=nodejs No build command found, searching known files No build command found, searching known files No build command found, searching known files No build command found, searching known files dh_auto_test --buildsystem=nodejs ln -s ../. node_modules/bunyan /bin/sh -ex debian/tests/pkg-js/test + tap -R tap -J --no-cov test/add-stream.test.js test/buffer.test.js test/child-behaviour.test.js test/cli-client-req.test.js test/cli-res.test.js test/cli.test.js test/ctor.test.js test/cycles.test.js test/error-event.test.js test/level.test.js test/log.test.js test/other-api.test.js test/process-exit.test.js test/raw-stream.test.js test/ringbuffer.test.js test/safe-json-stringify.test.js test/serializers.test.js test/src.test.js test/stream-levels.test.js TAP version 13 # Subtest: test/add-stream.test.js # Subtest: non-writables passed as stream ok 1 - "stream" stream is not writable ok 2 - "stream" stream is not writable 1..2 ok 1 - non-writables passed as stream # time=18.713ms # Subtest: proper stream ok 1 - expect truthy value 1..1 ok 2 - proper stream # time=4.908ms 1..2 # time=46.964ms ok 1 - test/add-stream.test.js # time=46.964ms # Subtest: test/buffer.test.js # Subtest: log.info(BUFFER) ok 1 - log.trace msg is inspect(BUFFER) ok 2 - no "0" array index key in record: undefined ok 3 - no "parent" array index key in record: undefined ok 4 - log.trace(BUFFER, "bar") msg is inspect(BUFFER) + " bar" ok 5 - log.debug msg is inspect(BUFFER) ok 6 - no "0" array index key in record: undefined ok 7 - no "parent" array index key in record: undefined ok 8 - log.debug(BUFFER, "bar") msg is inspect(BUFFER) + " bar" ok 9 - log.info msg is inspect(BUFFER) ok 10 - no "0" array index key in record: undefined ok 11 - no "parent" array index key in record: undefined ok 12 - log.info(BUFFER, "bar") msg is inspect(BUFFER) + " bar" ok 13 - log.warn msg is inspect(BUFFER) ok 14 - no "0" array index key in record: undefined ok 15 - no "parent" array index key in record: undefined ok 16 - log.warn(BUFFER, "bar") msg is inspect(BUFFER) + " bar" ok 17 - log.error msg is inspect(BUFFER) ok 18 - no "0" array index key in record: undefined ok 19 - no "parent" array index key in record: undefined ok 20 - log.error(BUFFER, "bar") msg is inspect(BUFFER) + " bar" ok 21 - log.fatal msg is inspect(BUFFER) ok 22 - no "0" array index key in record: undefined ok 23 - no "parent" array index key in record: undefined ok 24 - log.fatal(BUFFER, "bar") msg is inspect(BUFFER) + " bar" 1..24 ok 1 - log.info(BUFFER) # time=15.595ms 1..1 # time=36.998ms ok 2 - test/buffer.test.js # time=36.998ms # Subtest: test/child-behaviour.test.js # Subtest: child can add stream ok 1 - should be equal ok 2 - should be equal ok 3 - should be equal ok 4 - should be equal 1..4 ok 1 - child can add stream # time=8.798ms # Subtest: child can set level of inherited streams ok 1 - should be equal ok 2 - should be equal ok 3 - should be equal 1..3 ok 2 - child can set level of inherited streams # time=2.496ms # Subtest: child can set level of inherited streams and add streams ok 1 - should be equal ok 2 - should be equal ok 3 - should be equal ok 4 - should be equal ok 5 - should be
Bug#1069918: marked as done (npm: depedency issue prevent to install npm while neovim is installed)
Your message dated Sat, 27 Apr 2024 07:29:32 +0400 with message-id <85b4f44e-4730-4d04-8fa2-bad47353f...@debian.org> and subject line Re: [Pkg-javascript-devel] Bug#1069918: npm: depedency issue prevent to install npm while neovim is installed has caused the Debian Bug report #1069918, regarding npm: depedency issue prevent to install npm while neovim is installed 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.) -- 1069918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: npm Version: 9.2.0~ds1-2 Severity: normal X-Debbugs-Cc: report...@ecl.400iso.net When trying to install npm on testing, it tries to pull libuv1t64, that appear to be incompatible with libuv1, on wich neovim depends: Unsatisfied dependencies: libuv1t64 : Breaks: libuv1 (< 1.48.0-1.1) -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'stable-security'), (450, 'unstable'), (400, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages npm depends on: ii ca-certificates20240203 pn node-abbrev pn node-agent-base pn node-aproba pn node-archy pn node-base64-js pn node-binary-extensions pn node-cacache pn node-chalk pn node-chownr pn node-ci-info pn node-cli-table3 pn node-colors pn node-columnify pn node-cssesc pn node-debug pn node-depd pn node-diff pn node-emoji-regex pn node-encoding pn node-events pn node-glob pn node-got pn node-graceful-fs pn node-gyp pn node-hosted-git-info pn node-http-proxy-agent pn node-https-proxy-agent pn node-ieee754 pn node-ini pn node-ip pn node-ip-regex pn node-json-parse-better-errors pn node-jsonparse pn node-lru-cache pn node-minimatch pn node-minipass pn node-mkdirp pn node-ms pn node-negotiator pn node-nopt pn node-normalize-package-data pn node-npm-bundled pn node-npm-normalize-package-bin pn node-npm-package-arg pn node-npmlog pn node-once pn node-p-map pn node-postcss-selector-parser pn node-promise-retry pn node-promzard pn node-read pn node-read-package-json pn node-rimraf pn node-semver pn node-ssri pn node-string-width pn node-strip-ansi pn node-tar pn node-text-table pn node-validate-npm-package-license pn node-validate-npm-package-name pn node-which pn node-wrappy pn node-write-file-atomic pn node-yallist ii nodejs 18.19.1+dfsg-3 Versions of packages npm recommends: ii git 1:2.43.0-1+b1 pn node-tap Versions of packages npm suggests: pn node-opener --- End Message --- --- Begin Message --- On 4/27/24 06:23, Mathieu R. wrote: Package: npm Version: 9.2.0~ds1-2 Severity: normal X-Debbugs-Cc: report...@ecl.400iso.net When trying to install npm on testing, it tries to pull libuv1t64, that appear to be incompatible with libuv1, on wich neovim depends:
Bug#1034154: marked as done (libyang2: CVE-2023-26916)
Your message dated Sat, 27 Apr 2024 04:34:24 + with message-id and subject line Bug#1034154: fixed in libyang2 2.1.148-0.1 has caused the Debian Bug report #1034154, regarding libyang2: CVE-2023-26916 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.) -- 1034154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libyang2 Version: 2.1.30-2 Severity: important Tags: security upstream Forwarded: https://github.com/CESNET/libyang/issues/1979 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libyang2. CVE-2023-26916[0]: | libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL | pointer dereference via the function lys_parse_mem at lys_parse_mem.c. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-26916 https://www.cve.org/CVERecord?id=CVE-2023-26916 [1] https://github.com/CESNET/libyang/issues/1979 Regards, Salvatore --- End Message --- --- Begin Message --- Source: libyang2 Source-Version: 2.1.148-0.1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of libyang2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated libyang2 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: Sat, 27 Apr 2024 05:52:11 +0200 Source: libyang2 Architecture: source Version: 2.1.148-0.1 Distribution: unstable Urgency: medium Maintainer: Ondřej Surý Changed-By: Daniel Baumann Closes: 1034154 1034724 1068952 Changes: libyang2 (2.1.148-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #1068952): - fixes a NULL pointer dereference in lys_parse_mem() [CVE-2023-26916] (Closes: #1034154). - fixes a NULL pointer dereference in lysp_stmt_validate_value() [CVE-2023-26917] (Closes: #1034724). * Updating libyang2t64.symbols for new upstream version. Checksums-Sha1: 7acb4949f97d211034bd3a5b90029a2dfe33a6d9 2193 libyang2_2.1.148-0.1.dsc 1b5a2b5397c53d16eb3a1c4174cd2bf5b61a7df0 852880 libyang2_2.1.148.orig.tar.xz 1474695156cb7a2b1753e9e962cadfe24fd1cb09 12648 libyang2_2.1.148-0.1.debian.tar.xz 17bfe4bad7fe0bc45b4fea488f77319b175ce0ee 8690 libyang2_2.1.148-0.1_amd64.buildinfo Checksums-Sha256: 3dae4a3c8c0b87e8df4faf7512837fd416a60e019f75e4a177939c3d4ec47c12 2193 libyang2_2.1.148-0.1.dsc 9813ae052e14312e34965b9d294a0529f392c4e21611c47c0c5732011296f2b8 852880 libyang2_2.1.148.orig.tar.xz 6197b33e0103b8a33995ce388729933827e6e8c258d5659cd2811f1eb247 12648 libyang2_2.1.148-0.1.debian.tar.xz 90372452df263ba06cf518d8d59687c8e95e73640b5f93c786fe310ee2c45e45 8690 libyang2_2.1.148-0.1_amd64.buildinfo Files: afd09c5af50a2a210101568cf83ee7d2 2193 libs optional libyang2_2.1.148-0.1.dsc ca6915c2c2e02525630777a626224ec7 852880 libs optional libyang2_2.1.148.orig.tar.xz c4873d50e28c0370928f9c3feffb53bb 12648 libs optional libyang2_2.1.148-0.1.debian.tar.xz 25275ebb03618452299cfb276ae705de 8690 libs optional libyang2_2.1.148-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmYsfGMACgkQVc8b+Yar uceVxQ/+PyR6KSetRF45ZwXd5uglI37AlSm/OYs/dPAxctPJ+il2eWpMKrzP8F+f o0MNuZ7871Ykkzfx6pMOfpNUKZj5PjhEnTxBkgbICsCNylh4D/oaSQf+IfSUq7r7 aOvIzCo6vuLzxdj5ygMg0FcnEEUR/9wH+rQdvRzvm1r1Y7s63FwASXo8wOLO7nnU hk0I9NU21zl0qDE7xc8o0A3y8TRswnsl/fWI691+luHRe8UoFvI/rFHjdemewi80 4nsqja9SYh3N/lLCABJkXnYObnNNfNEzbrZLpZE2Cxf2ROpFEcFNWG6Pqh+ai16d dzticNdGoemqKq0GxrkyR0eUHpahlHn1D402AiHxxOksG8HoOLVcVa6NKoOzFSNz YQaP9yIt0ozKvqxmgKm2aZd9vJ95j7aRnVXlj48cGs63PZdB5RhRCxtmcchO03BQ xL/it3Z4fK/5QOFhD1t4VN5Jz1glwbUUUiWM7kt+LQAT4Q+TATnYZ6wL2AVqSbkG NIZfYXmpikh2l+ANEHQ5bieY1cmhh5WvZ0cz8PgfB+k/ijy5YbG+uJ7J1HTsdmxk NXeXAyzNAsiJD/4lLg/pSz7rw0oligXlZKhe/sr1fcClOPuavUKUqRloZnBW2iTS
Bug#1034724: marked as done (libyang2: CVE-2023-26917)
Your message dated Sat, 27 Apr 2024 04:34:24 + with message-id and subject line Bug#1034724: fixed in libyang2 2.1.148-0.1 has caused the Debian Bug report #1034724, regarding libyang2: CVE-2023-26917 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.) -- 1034724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libyang2 X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for libyang2. CVE-2023-26917[0]: | libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL | pointer dereference via the function lysp_stmt_validate_value at | lys_parse_mem.c. https://github.com/CESNET/libyang/issues/1987 https://github.com/CESNET/libyang/commit/cfa1a965a429e4bfc5ae1539a8e87a9cf71c3090 (v2.1.55) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-26917 https://www.cve.org/CVERecord?id=CVE-2023-26917 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: libyang2 Source-Version: 2.1.148-0.1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of libyang2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated libyang2 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: Sat, 27 Apr 2024 05:52:11 +0200 Source: libyang2 Architecture: source Version: 2.1.148-0.1 Distribution: unstable Urgency: medium Maintainer: Ondřej Surý Changed-By: Daniel Baumann Closes: 1034154 1034724 1068952 Changes: libyang2 (2.1.148-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #1068952): - fixes a NULL pointer dereference in lys_parse_mem() [CVE-2023-26916] (Closes: #1034154). - fixes a NULL pointer dereference in lysp_stmt_validate_value() [CVE-2023-26917] (Closes: #1034724). * Updating libyang2t64.symbols for new upstream version. Checksums-Sha1: 7acb4949f97d211034bd3a5b90029a2dfe33a6d9 2193 libyang2_2.1.148-0.1.dsc 1b5a2b5397c53d16eb3a1c4174cd2bf5b61a7df0 852880 libyang2_2.1.148.orig.tar.xz 1474695156cb7a2b1753e9e962cadfe24fd1cb09 12648 libyang2_2.1.148-0.1.debian.tar.xz 17bfe4bad7fe0bc45b4fea488f77319b175ce0ee 8690 libyang2_2.1.148-0.1_amd64.buildinfo Checksums-Sha256: 3dae4a3c8c0b87e8df4faf7512837fd416a60e019f75e4a177939c3d4ec47c12 2193 libyang2_2.1.148-0.1.dsc 9813ae052e14312e34965b9d294a0529f392c4e21611c47c0c5732011296f2b8 852880 libyang2_2.1.148.orig.tar.xz 6197b33e0103b8a33995ce388729933827e6e8c258d5659cd2811f1eb247 12648 libyang2_2.1.148-0.1.debian.tar.xz 90372452df263ba06cf518d8d59687c8e95e73640b5f93c786fe310ee2c45e45 8690 libyang2_2.1.148-0.1_amd64.buildinfo Files: afd09c5af50a2a210101568cf83ee7d2 2193 libs optional libyang2_2.1.148-0.1.dsc ca6915c2c2e02525630777a626224ec7 852880 libs optional libyang2_2.1.148.orig.tar.xz c4873d50e28c0370928f9c3feffb53bb 12648 libs optional libyang2_2.1.148-0.1.debian.tar.xz 25275ebb03618452299cfb276ae705de 8690 libs optional libyang2_2.1.148-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmYsfGMACgkQVc8b+Yar uceVxQ/+PyR6KSetRF45ZwXd5uglI37AlSm/OYs/dPAxctPJ+il2eWpMKrzP8F+f o0MNuZ7871Ykkzfx6pMOfpNUKZj5PjhEnTxBkgbICsCNylh4D/oaSQf+IfSUq7r7 aOvIzCo6vuLzxdj5ygMg0FcnEEUR/9wH+rQdvRzvm1r1Y7s63FwASXo8wOLO7nnU hk0I9NU21zl0qDE7xc8o0A3y8TRswnsl/fWI691+luHRe8UoFvI/rFHjdemewi80 4nsqja9SYh3N/lLCABJkXnYObnNNfNEzbrZLpZE2Cxf2ROpFEcFNWG6Pqh+ai16d dzticNdGoemqKq0GxrkyR0eUHpahlHn1D402AiHxxOksG8HoOLVcVa6NKoOzFSNz YQaP9yIt0ozKvqxmgKm2aZd9vJ95j7aRnVXlj48cGs63PZdB5RhRCxtmcchO03BQ xL/it3Z4fK/5QOFhD1t4VN5Jz1glwbUUUiWM7kt+LQAT4Q+TATnYZ6wL2AVqSbkG NIZfYXmpikh2l+ANEHQ5bieY1cmhh5WvZ0cz8PgfB+k/ijy5YbG+uJ7J1HTsdmxk NXeXAyzNAsiJD/4lLg/pSz7rw0oligXlZKhe/sr1fcClOPuavUKUqRloZnBW2iTS
Bug#1068952: marked as done (new upstream required for frr)
Your message dated Sat, 27 Apr 2024 04:34:24 + with message-id and subject line Bug#1068952: fixed in libyang2 2.1.148-0.1 has caused the Debian Bug report #1068952, regarding new upstream required for frr 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.) -- 1068952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libyang2 Severity: wishlist Hi Ondrej, it would be nice if you could upload libyang2 >= 2.1.128 as the new frr release requires that. If you need/want help, I'm happy to do so, just let me know. Regards, Daniel --- End Message --- --- Begin Message --- Source: libyang2 Source-Version: 2.1.148-0.1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of libyang2, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated libyang2 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: Sat, 27 Apr 2024 05:52:11 +0200 Source: libyang2 Architecture: source Version: 2.1.148-0.1 Distribution: unstable Urgency: medium Maintainer: Ondřej Surý Changed-By: Daniel Baumann Closes: 1034154 1034724 1068952 Changes: libyang2 (2.1.148-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #1068952): - fixes a NULL pointer dereference in lys_parse_mem() [CVE-2023-26916] (Closes: #1034154). - fixes a NULL pointer dereference in lysp_stmt_validate_value() [CVE-2023-26917] (Closes: #1034724). * Updating libyang2t64.symbols for new upstream version. Checksums-Sha1: 7acb4949f97d211034bd3a5b90029a2dfe33a6d9 2193 libyang2_2.1.148-0.1.dsc 1b5a2b5397c53d16eb3a1c4174cd2bf5b61a7df0 852880 libyang2_2.1.148.orig.tar.xz 1474695156cb7a2b1753e9e962cadfe24fd1cb09 12648 libyang2_2.1.148-0.1.debian.tar.xz 17bfe4bad7fe0bc45b4fea488f77319b175ce0ee 8690 libyang2_2.1.148-0.1_amd64.buildinfo Checksums-Sha256: 3dae4a3c8c0b87e8df4faf7512837fd416a60e019f75e4a177939c3d4ec47c12 2193 libyang2_2.1.148-0.1.dsc 9813ae052e14312e34965b9d294a0529f392c4e21611c47c0c5732011296f2b8 852880 libyang2_2.1.148.orig.tar.xz 6197b33e0103b8a33995ce388729933827e6e8c258d5659cd2811f1eb247 12648 libyang2_2.1.148-0.1.debian.tar.xz 90372452df263ba06cf518d8d59687c8e95e73640b5f93c786fe310ee2c45e45 8690 libyang2_2.1.148-0.1_amd64.buildinfo Files: afd09c5af50a2a210101568cf83ee7d2 2193 libs optional libyang2_2.1.148-0.1.dsc ca6915c2c2e02525630777a626224ec7 852880 libs optional libyang2_2.1.148.orig.tar.xz c4873d50e28c0370928f9c3feffb53bb 12648 libs optional libyang2_2.1.148-0.1.debian.tar.xz 25275ebb03618452299cfb276ae705de 8690 libs optional libyang2_2.1.148-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmYsfGMACgkQVc8b+Yar uceVxQ/+PyR6KSetRF45ZwXd5uglI37AlSm/OYs/dPAxctPJ+il2eWpMKrzP8F+f o0MNuZ7871Ykkzfx6pMOfpNUKZj5PjhEnTxBkgbICsCNylh4D/oaSQf+IfSUq7r7 aOvIzCo6vuLzxdj5ygMg0FcnEEUR/9wH+rQdvRzvm1r1Y7s63FwASXo8wOLO7nnU hk0I9NU21zl0qDE7xc8o0A3y8TRswnsl/fWI691+luHRe8UoFvI/rFHjdemewi80 4nsqja9SYh3N/lLCABJkXnYObnNNfNEzbrZLpZE2Cxf2ROpFEcFNWG6Pqh+ai16d dzticNdGoemqKq0GxrkyR0eUHpahlHn1D402AiHxxOksG8HoOLVcVa6NKoOzFSNz YQaP9yIt0ozKvqxmgKm2aZd9vJ95j7aRnVXlj48cGs63PZdB5RhRCxtmcchO03BQ xL/it3Z4fK/5QOFhD1t4VN5Jz1glwbUUUiWM7kt+LQAT4Q+TATnYZ6wL2AVqSbkG NIZfYXmpikh2l+ANEHQ5bieY1cmhh5WvZ0cz8PgfB+k/ijy5YbG+uJ7J1HTsdmxk NXeXAyzNAsiJD/4lLg/pSz7rw0oligXlZKhe/sr1fcClOPuavUKUqRloZnBW2iTS ntvH5h7drxDwlOxqEpFMkgNIO5XEtgBxQakvqmcY60rHTtSbw0M= =eETj -END PGP SIGNATURE- pgpMGhKwDyKEV.pgp Description: PGP signature --- End Message ---
Bug#1068035: marked as done (FTBFS: wrong --link-doc target)
Your message dated Sat, 27 Apr 2024 05:50:29 + with message-id and subject line Bug#1068035: fixed in mdbtools 1.0.0+dfsg-1.3 has caused the Debian Bug report #1068035, regarding FTBFS: wrong --link-doc target 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.) -- 1068035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mdbtools Version: 1.0.0+dfsg-1.2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mdbtools=arm64=1.0.0%2Bdfsg-1.2%2Bb2=1711715505=0 dh_installdocs --no-package=mdbtools-doc --link-doc=libmdb3 dh_installdocs: error: Requested unknown package libmdb3 via --link-doc, expected one of: mdbtools mdbtools-dev libmdb3t64 libmdbsql3t64 odbc-mdbtools mdbtools-doc It should be changed to libmdb3t64. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: mdbtools Source-Version: 1.0.0+dfsg-1.3 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of mdbtools, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated mdbtools 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: Sat, 27 Apr 2024 05:11:37 + Source: mdbtools Architecture: source Version: 1.0.0+dfsg-1.3 Distribution: unstable Urgency: medium Maintainer: Jean-Michel Vourgère Changed-By: Steve Langasek Closes: 1068035 Changes: mdbtools (1.0.0+dfsg-1.3) unstable; urgency=medium . * Non-maintainer upload. * Use correct package for doc target. Closes: #1068035. Checksums-Sha1: c28355eb9bcb795abe129bc575484bedc66c6ca6 2393 mdbtools_1.0.0+dfsg-1.3.dsc f13693086712c9c566ed8a24ad3a0923269fee4b 15516 mdbtools_1.0.0+dfsg-1.3.debian.tar.xz 468bbd728b36904c0f1085d78a89a1fb80cb0ed1 7043 mdbtools_1.0.0+dfsg-1.3_source.buildinfo Checksums-Sha256: f333ff256e20a373f65baa1ca639ff33950f384e4bda60af81aa5f260b8e6bf3 2393 mdbtools_1.0.0+dfsg-1.3.dsc c59c9dc40b30e89f193e51ce76daddf9a55881e14019f57a321221dafb13392a 15516 mdbtools_1.0.0+dfsg-1.3.debian.tar.xz 9869fa47be5676661973cf9b990e306c11b8eb1579f41675bff5da2f8e2e0588 7043 mdbtools_1.0.0+dfsg-1.3_source.buildinfo Files: 116f58b4591787b8b67affd0f57313da 2393 database optional mdbtools_1.0.0+dfsg-1.3.dsc 013af2d96dc151173e882f2c5740ed56 15516 database optional mdbtools_1.0.0+dfsg-1.3.debian.tar.xz 58e70298b59652776b59279383f7a8af 7043 database optional mdbtools_1.0.0+dfsg-1.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmYsi3sSHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM9oWwP/i2Y3Lyd4RICDfDZ+QaNo1vCkjpgkKrU iAlKEOV+VjDdzB8m6gK343xyaOE0C3BPrWqINL92A2o8YkFmDfjzcNIcXVtsVv13 3lsfwijGBhaK2euNZMxzz15v/ru+CLmOBKPcxWJ/2sATGay7m8Nn7JIUlphtn0f4 JvDh1qTBVFvkmXz67WAXEwkBSaa5E+0AXaLmc8nxfAhSrVDCQOqtkldRk04cAbxh nOdJES+h9hDsjxGTKn1Q+q+qqFJy3E+ZFeHQ2F8YvPDRbHxenTwHONepstr0xa+H SoViiLZat5P66/LK6TDQvFlvpwTesnzIVEkpJ/tw3DJ8NLFiJURQx4IIFdotrojd 8L5KMlPOp75XLGEVKqT8DoHl40MBGTIiKzyz9tev94Hh6hcxtSEjudGeEPxZLaOX 8wkkOb9ujAxdSaDRiUAYGMn2W6UeGRkoL/Jx8CQKgESAwZVi9xleBfZXiGoypBtp DhYE/RbNOv4cnweLTKEnd7NHNSDK8sJf/wED8/UsfSmHLT6ta30BKT0ukmAU2r+x ST6tK8IxIUEtvNylNztEy5EDq+t21vvInfrDY2hKllwHU4RhfnfFjHVCommmr7ul LYUk3BwhcZ+fJ4a/snrituL5RIcPN0SaElmBrs5tjLIT6e4ilNplx/TtujSRqxpA TXltnku8oXqM =Evgx -END PGP SIGNATURE- pgpVVNgyC3mtd.pgp Description: PGP signature --- End Message ---
