date:20231210

Your message dated Mon, 11 Dec 2023 05:19:03 +
with message-id 
and subject line Bug#1052664: fixed in ntpsec 1.2.2+dfsg1-3
has caused the Debian Bug report #1052664,
regarding ntpsec FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ntpsec
Version: 1.2.2+dfsg1-2
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. ntpsec's upstream build system consumes this variable,
but the packaging hard codes the current value. Consequently, ntpsec
FTBFS when it changes. Consider applying the attached patch to avoid
this failure.

Helmut
diff -Nru ntpsec-1.2.2+dfsg1/debian/changelog 
ntpsec-1.2.2+dfsg1/debian/changelog
--- ntpsec-1.2.2+dfsg1/debian/changelog 2023-07-30 21:04:02.0 +0200
+++ ntpsec-1.2.2+dfsg1/debian/changelog 2023-09-25 22:51:13.0 +0200
@@ -1,3 +1,10 @@
+ntpsec (1.2.2+dfsg1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Sep 2023 22:51:13 +0200
+
 ntpsec (1.2.2+dfsg1-2) unstable; urgency=high
 
   * copyright: Update libjsmn comment
diff -Nru ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpviz.install 
ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpviz.install
--- ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpviz.install 2023-01-17 
00:31:00.0 +0100
+++ ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpviz.install 2023-09-25 
22:50:52.0 +0200
@@ -1,9 +1,9 @@
-debian/tmp/lib/systemd/system/ntplogtemp.service
-debian/tmp/lib/systemd/system/ntplogtemp.timer
-debian/tmp/lib/systemd/system/ntpviz-daily.service
-debian/tmp/lib/systemd/system/ntpviz-daily.timer
-debian/tmp/lib/systemd/system/ntpviz-weekly.service
-debian/tmp/lib/systemd/system/ntpviz-weekly.timer
+debian/tmp/${env:systemdsystemunitdir}/ntplogtemp.service
+debian/tmp/${env:systemdsystemunitdir}/ntplogtemp.timer
+debian/tmp/${env:systemdsystemunitdir}/ntpviz-daily.service
+debian/tmp/${env:systemdsystemunitdir}/ntpviz-daily.timer
+debian/tmp/${env:systemdsystemunitdir}/ntpviz-weekly.service
+debian/tmp/${env:systemdsystemunitdir}/ntpviz-weekly.timer
 debian/tmp/usr/bin/ntpviz
 debian/tmp/usr/sbin/ntploggps
 debian/tmp/usr/sbin/ntplogtemp
diff -Nru ntpsec-1.2.2+dfsg1/debian/ntpsec.install 
ntpsec-1.2.2+dfsg1/debian/ntpsec.install
--- ntpsec-1.2.2+dfsg1/debian/ntpsec.install2023-01-17 00:31:00.0 
+0100
+++ ntpsec-1.2.2+dfsg1/debian/ntpsec.install2023-09-25 22:51:03.0 
+0200
@@ -1,7 +1,7 @@
 debian/ntp-systemd-wrapper usr/libexec/ntpsec
 debian/rotate-stats usr/libexec/ntpsec
-debian/tmp/lib/systemd/system/ntpsec-wait.service
-debian/tmp/lib/systemd/system/ntpsec.service
+debian/tmp/${env:systemdsystemunitdir}/ntpsec-wait.service
+debian/tmp/${env:systemdsystemunitdir}/ntpsec.service
 debian/tmp/usr/bin/ntpleapfetch usr/sbin
 debian/tmp/usr/bin/ntpmon
 debian/tmp/usr/bin/ntpq
diff -Nru ntpsec-1.2.2+dfsg1/debian/rules ntpsec-1.2.2+dfsg1/debian/rules
--- ntpsec-1.2.2+dfsg1/debian/rules 2023-01-17 00:31:00.0 +0100
+++ ntpsec-1.2.2+dfsg1/debian/rules 2023-09-25 22:50:13.0 +0200
@@ -6,6 +6,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow,+pie
 export DEB_CFLAGS_MAINT_APPEND = -fno-strict-aliasing
+export systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd)
 
 %:
dh $@ --with apache2,python3
@@ -78,11 +79,11 @@
 override_dh_install:
python3 waf install --destdir=$(CURDIR)/debian/tmp
mv \
-   debian/tmp/lib/systemd/system/ntpd.service \
-   debian/tmp/lib/systemd/system/ntpsec.service
+   debian/tmp/$(systemdsystemunitdir)/ntpd.service \
+   debian/tmp/$(systemdsystemunitdir)/ntpsec.service
mv \
-   debian/tmp/lib/systemd/system/ntp-wait.service \
-   debian/tmp/lib/systemd/system/ntpsec-wait.service
+   debian/tmp/$(systemdsystemunitdir)/ntp-wait.service \
+   debian/tmp/$(systemdsystemunitdir)/ntpsec-wait.service
rm -rf debian/tmp/usr/lib/python3/dist-packages/ntp/__pycache__
# ntpfrob probes internal, mostly undocumented settings.  It is
# extremely unlikely that anyone needs this.
@@ -129,19 +130,19 @@
debian/ntpsec.certbot \

Bug#1057171: marked as pending in libitext5-java

2023-12-10 Thread Tony Mancill

Control: tag -1 pending

Hello,

Bug #1057171 in libitext5-java reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/libitext5-java/-/commit/76a0d51dda07cd09211479918b0bd71184209936


Add patch to compile against BouncyCastle 1.77 (Closes: #1057171)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057171

Processed: Bug#1057171 marked as pending in libitext5-java

Processing control commands:

> tag -1 pending
Bug #1057171 [src:libitext5-java] libitext5-java: FTBFS with bouncycastle 1.77
Added tag(s) pending.

-- 
1057171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

Processing commands for cont...@bugs.debian.org:

> notfound 1057967 6.1.64-1
Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my 
physical bookworm/gnome computer largely unusable
There is no source info for the package 'linux-image-6.1.0-15-amd64' at version 
'6.1.64-1' with architecture ''
Unable to make a source version for version '6.1.64-1'
Ignoring request to alter found versions of bug #1057967 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1057967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-10 Thread Kevin Price

Package: linux-image-6.1.0-15-amd64
Version: 6.1.66-1
Severity: critical
Control: -1 notfound 6.1.64-1

When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
misbehaves in many ways, rendering it largely unusable. With kernels up
to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
this seemed fine.

Misbehavior includes, not limited to:

1. Most actions take considerably longer than usual.

2. The GDM greeter has an English keyboard layout, which otherwise is
German. (Login works.)

3. There seems to be no network connectivity. No WiFi icon. "ping
8.8.8.8" returns IIRC network unreachable.

4. Launching Firefox does apparently nothing.

5. Launching gnome-terminal does work, but some basic commands just
freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".

6. Shutting down takes ages, with systemd waiting for a bunch of
processes (sudo) and services to terminate, most of the latter seem to
be somehow network-related, but you tell me which aren't.

After more that 10 min I used hard power-off, leaving my ext4 dirty, but
being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
-13 working properly, and -15 showing the exact same misbehavior
reproducibly.

I'll attach all I could get out of reportbug running under 6.1.0-15, and
please let me know what further testing I may perform IOT help you.
Please also specify whether you'd like me to do that testing under
6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
will do anything fine.

Thanks a lot in advance, and HTH!
-- 
Kevin PriceContent-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kevin Price 
To: Debian Bug Tracking System 
Subject: linux-image-6.1.0-15-amd64 makes my physical bookworm/gnome system 
vastly unusable
Bcc: Kevin Price 

Package: src:linux
Version: 6.1.66-1
Severity: critical



-- Package-specific info:
** Version:
Linux version 6.1.0-15-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-15-amd64 
root=UUID=b1e4af52-2d43-40ab-a468-ca11bf2a3122 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 1068FQG
product_version: Lenovo B570
chassis_vendor: LENOVO
chassis_version: 0.1
bios_vendor: LENOVO
bios_version: 44CN41WW
board_vendor: LENOVO
board_name: Emerald Lake
board_version: FAB1

** Loaded modules:
cts
uinput
rfcomm
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
xt_CHECKSUM
xt_MASQUERADE
bridge
stp
llc
cmac
algif_hash
algif_skcipher
af_alg
bnep
ip6t_rt
ip6t_REJECT
nf_reject_ipv6
nft_chain_nat
nf_nat
xt_set
ipt_REJECT
nf_reject_ipv4
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
nf_tables
binfmt_misc
ip_set_hash_ipport
pktcdvd
ip_set
nfnetlink
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
nls_ascii
nls_cp437
btusb
kvm_intel
btrtl
btbcm
vfat
btintel
btmtk
fat
kvm
bluetooth
irqbypass
crc32_pclmul
crypto_simd
xts
ecb
jitterentropy_rng
dm_crypt
ghash_clmulni_intel
cryptd
snd_hda_codec_hdmi
sha512_ssse3
sha512_generic
isofs
sha256_ssse3
rtsx_usb_sdmmc
sha1_ssse3
snd_hda_codec_realtek
wl(POE)
snd_hda_codec_generic
mmc_core
ledtrig_audio
ctr
rtsx_usb_ms
memstick
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
drbg
snd_hda_codec
iTCO_wdt
intel_pmc_bxt
uvcvideo
iTCO_vendor_support
mei_hdcp
at24
watchdog
videobuf2_vmalloc
snd_hda_core
videobuf2_memops
rtsx_usb
rapl
videobuf2_v4l2
ansi_cprng
videobuf2_common
snd_hwdep
intel_cstate
ecdh_generic
intel_uncore
wmi_bmof
ecc
snd_pcm
videodev
sr_mod
cdrom
r8169
cfg80211
realtek
i2c_i801
snd_timer
mc
pcspkr
i2c_smbus
mei_me
ideapad_laptop
mdio_devres
platform_profile
snd
libphy
mei
lpc_ich
soundcore
sparse_keymap
rfkill
ac
battery
button
joydev
sg
coretemp
parport_pc
ppdev
lp
parport
loop
fuse
efi_pstore
dm_mod
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
efivarfs
raid10
raid456
libcrc32c
crc32c_generic
async_raid6_recov
async_memcpy
async_pq
async_xor
xor
async_tx
raid6_pq
raid1
raid0
multipath
linear
md_mod
sd_mod
t10_pi
crc64_rocksoft
crc64
crc_t10dif
crct10dif_generic
hid_generic
usbhid
hid
i915
i2c_algo_bit
drm_buddy
drm_display_helper
ahci
libahci
drm_kms_helper
libata
cec
rc_core
ehci_pci
ehci_hcd
ttm
scsi_mod
usbcore
crct10dif_pclmul
crct10dif_common
drm
psmouse
evdev
crc32c_intel
scsi_common
serio_raw
usb_common
video
wmi

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Lenovo 2nd Generation Core Processor Family DRAM

Bug#832116: marked as done (edgar: Source missing for some GPL licensed assets)

Your message dated Mon, 11 Dec 2023 01:49:43 +
with message-id 
and subject line Bug#832116: fixed in edgar 1.36-1
has caused the Debian Bug report #832116,
regarding edgar: Source missing for some GPL licensed assets
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.)


-- 
832116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: edgar
Severity: serious
Justification: source missing for GPL licensed assets

According to debian/copyright, the edgar-data package contains a number
of songs which are licensed under the GPL-3+. However, only the final
rendered music is present in the form of a .ogg file.

> Files:
>   music/Battle?in?the?winter.ogg
>   music/Devilish?design.ogg
>   music/A?wintertale_0.ogg
>   music/Medicine.ogg
> Copyright: Copyright (c) Johan Brodd
> Comment: http://opengameart.org/users/jobromedia
> License: GPL-3+

Upon checking OpenGameArt, I found out that "Battle in the winter" and "A
winter tale" are dual-licensed, and available under the CC-BY 3.0 and
CC-BY-SA 3.0 licenses respectively, so it should be a simple matter of
updating the copyright notice here. However, "Devilish design" is only
available under GPL 3.0. As such, I believe that unless the source can
be found or Johan Brodd can be contacted and asked if the license could
be changed, this song should be removed from the source package.

Also, Medicine.ogg is, according to OpenGameArt.org, created by
Alexander Zhelanov, and is licensed only under CC-BY 3.0.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: edgar
Source-Version: 1.36-1
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
edgar, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated edgar 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: Mon, 11 Dec 2023 02:23:35 +0100
Source: edgar
Architecture: source
Version: 1.36-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Alexandre Detiste 
Closes: 818326 832116 985185 998116 1013412 1038193
Changes:
 edgar (1.36-1) unstable; urgency=medium
 .
   * Team upload.
   * Upstream has dutifully tracked origin of all music/*.ogg
 files (Closes: #832116)
   * build with SDL2 (Closes: #985185, #1038193)
   * remove duplicate dependency on debhelper
   * add debian/.gitignore
   * Import v1.36 that fix Polish translation (Closes: #818326)
   * use upstream-provided manpage, drop Debian stub
   * d/copyright: add license details for appdata.xml
 .
   [ Matt Barry ]
   * New upstream release (1.35).
   * New maintainer.  Closes: #998116.
   * URL updates.  Closes: #1013412.
   * Various Lintian updates.
   * Update and drop patches.
Checksums-Sha1:
 1c89c522e7cee6084c13db60f8be6e45c550eb41 2157 edgar_1.36-1.dsc
 4a88cb78233c1c064102baa93d5b4aa7bc807d6a 136993357 edgar_1.36.orig.tar.gz
 b73caebf766e1fc3abf6fd924537b5aa8a30e22e 3276 edgar_1.36-1.debian.tar.xz
 f0a60d0bde47f695f1f110b9967f16ae7c83a2ba 13528 edgar_1.36-1_source.buildinfo
Checksums-Sha256:
 ff52498536dd4dcb1983fc61940edaf9f42938c8c7b64e9b2404e852b998fd70 2157 
edgar_1.36-1.dsc
 478184e4b59e0d1ed7db995d913f6187b47b240d01561d8a581a990d5515240c 136993357 
edgar_1.36.orig.tar.gz
 d0c975aabf95116a2f7e15d106823730fb893672296862eb2c000853b5f0f3de 3276 
edgar_1.36-1.debian.tar.xz
 26eaddfed687f29de603a2cf0e5f5149d5c7a521fa9a43d6a861475dde36183c 13528 
edgar_1.36-1_source.buildinfo
Files:
 9a4302551ca50af136e0c716d3bb0d30 2157 games optional edgar_1.36-1.dsc
 758bca5ef7333e6b55cf884a6272a284 136993357 games optional 
edgar_1.36.orig.tar.gz

Bug#1056780: marked as done (openmsx: Source-less Windows binary in source package (and other packaging issues))

Your message dated Sun, 10 Dec 2023 23:34:13 +
with message-id 
and subject line Bug#1056780: fixed in openmsx 19.1+dfsg-1
has caused the Debian Bug report #1056780,
regarding openmsx: Source-less Windows binary in source package (and other 
packaging issues)
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.)


-- 
1056780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmsx
Version: 19.1-1
Severity: serious
Justification: Policy 2.2.1
X-Debbugs-Cc: arraybo...@ubuntu.com

Packages in the Debian `main` archive area *must* comply with the DFSG, of
which section 2 states "The program must include source code, and must allow
distribution in source code as well as compiled form." The openMSX package
currently ships a Windows library (Contrib/codec/Win32/zmbv.dll) allegedly
built from code that is part of DOSBox. The source code of the library is not
included, and the library is fairly useless in Debian for obvious reasons.

On top of this, there are a number of packaging issues that could be improved
but that aren't so serious - the most problematic of these is an autopkgtest
failure caused by catch2 (Debian currently ships catch2 v3, but openMSX's
tests are only designed for catch2 v2 - thankfully there's a vendored version
of catch2 in openMSX that builds successfully on Debian Sid now). As there
does not appear to be a VCS link to the openMSX packaging in
tracker.debian.org, I'm assuming openMSX isn't in Debian Salsa yet, and will
provide a debdiff in this bug report.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 openmsx depends on:
ii  cbios  0.29a-1
ii  libasound2 1.2.10-1
ii  libc6  2.37-12
ii  libgcc-s1  13.2.0-7
ii  libgl1 1.7.0-1
ii  libglew2.2 2.2.0-4+b1
ii  libogg01.3.5-3
ii  libpng16-161.6.40-2
ii  libsdl2-2.0-0  2.28.5+dfsg-2
ii  libsdl2-ttf-2.0-0  2.20.2+dfsg-1
ii  libstdc++6 13.2.0-7
ii  libtcl8.6  8.6.13+dfsg-2
ii  libtheora0 1.1.1+dfsg.1-16.1+b1
ii  libvorbis0a1.3.7-1
ii  openmsx-data   19.1-1
ii  zlib1g 1:1.3.dfsg-3

openmsx recommends no packages.

Versions of packages openmsx suggests:
pn  dmktools  
pn  openmsx-catapult  
pn  openmsx-debugger  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openmsx
Source-Version: 19.1+dfsg-1
Done: Bas Wijnen 

We believe that the bug you reported is fixed in the latest version of
openmsx, 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.
Bas Wijnen  (supplier of updated openmsx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 19:47:57 +0100
Source: openmsx
Architecture: source
Version: 19.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Bas Wijnen 
Changed-By: Bas Wijnen 
Closes: 1056780
Changes:
 openmsx (19.1+dfsg-1) unstable; urgency=medium
 .
   [ Aaron Rainbolt ]
   * Override spurious source-is-missing Lintian errors.
   * Don't build-depend on dpkg-dev, it's guaranteed to be installed in a
 Debian build environment.
   * Repack the upstream tarball to remove prebuilt binaries lacking source
 code. (Closes: #1056780)
   * Set 'DEB_BUILD_MAINT_OPTIONS = hardening=+all' in debian/rules.
   * Remove debian/source/include-binaries, every file listed in it doesn't
 exist.
   * Set 'Rules-Requires-Root: no' in debian/control.
   * Use debhelper 13 rather than debhelper 10.
 - Changed "debhelper (>= 10)" to "debhelper-compat (= 13)" in
   debian/control.
 - Deleted debian/compat.
   * Override spurious package-contains-documentation-outside-usr-share-doc
 Lintian

Processed: Bug#832116 marked as pending in edgar

Processing control commands:

> tag -1 pending
Bug #832116 [src:edgar] edgar: Source missing for some GPL licensed assets
Added tag(s) pending.

-- 
832116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832116: marked as pending in edgar

2023-12-10 Thread Alexandre Detiste

Control: tag -1 pending

Hello,

Bug #832116 in edgar reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/edgar/-/commit/ee497fc3455b86b6ef986f72281b31e0cca0f49f


copyright assesment of *.ogg files (Closes: #832116)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/832116

Bug#1057952: marked as done (pandoc: FTBFS on ppc64el: This version of pandoc has been compiled without Lua support.)

Your message dated Sun, 10 Dec 2023 22:34:36 +
with message-id 
and subject line Bug#1057952: fixed in pandoc 3.0.1+ds-2
has caused the Debian Bug report #1057952,
regarding pandoc: FTBFS on ppc64el: This version of pandoc has been compiled 
without Lua 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.)


-- 
1057952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc
Version: 2.17.1.1+~git20230125+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

Thanks for working on the pandoc update. Unfortunately, it fails to
build on ppc64el due to the missing lua support:

https://buildd.debian.org/status/fetch.php?pkg=pandoc=ppc64el=2.17.1.1%2B%7Egit20230125%2Bds-1=1702140012=0

dist-ghc/build/pandoc/pandoc MANUAL.txt -f markdown -t man -s \
--lua-filter man/manfilter.lua \
--include-before-body man/pandoc.1.before \
--include-after-body man/pandoc.1.after \
--metadata author="" \
--variable footer="pandoc 3.0.1+2.17.1.1+~git20230125+ds-1" \
-o man/pandoc.1
This version of pandoc has been compiled without Lua support.
make: *** [debian/rules:95: man/pandoc.1] Error 89

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pandoc
Source-Version: 3.0.1+ds-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
pandoc, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated pandoc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 23:14:13 +0100
Source: pandoc
Architecture: source
Version: 3.0.1+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 
Changed-By: Jonas Smedegaard 
Closes: 1057952
Changes:
 pandoc (3.0.1+ds-2) unstable; urgency=medium
 .
   * stop prefix library version
   * avoid generating man page
 on architectures where the executable is built with Lua support;
 closes: bug#1057952, thanks to Sebastian Ramacher
Checksums-Sha1:
 4de34c417a5c61ab746d7b226e57813b6bc4d3c7 2474 pandoc_3.0.1+ds-2.dsc
 d211034f142a2dda0e3efc42c014e39f17efc99b 40080 pandoc_3.0.1+ds-2.debian.tar.xz
 b56acd1c87809830d9167016de506e7178625597 21718 
pandoc_3.0.1+ds-2_amd64.buildinfo
Checksums-Sha256:
 24096e6ceba72716235112f90a337e3a5da31a613a4364916f24ee1b3fd551f1 2474 
pandoc_3.0.1+ds-2.dsc
 9f3c90722895c621f79269d114ed69f0efde1f975d2f5dff273eae852d713ee7 40080 
pandoc_3.0.1+ds-2.debian.tar.xz
 bcfef300b4df5d5da832c36bbd6beafc2c2b0888bd0befa6bcef78905aaccedb 21718 
pandoc_3.0.1+ds-2_amd64.buildinfo
Files:
 7b0aa92144c194acbe97297d85aa6bb3 2474 text optional pandoc_3.0.1+ds-2.dsc
 be9e258212319789fa2032ab3afed0b5 40080 text optional 
pandoc_3.0.1+ds-2.debian.tar.xz
 6047f4c155f16f12c2ef20a5872e3c41 21718 text optional 
pandoc_3.0.1+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmV2Oa0ACgkQLHwxRsGg
ASGv7g//frMX3nR5Qxnn36/jE4RZZ/o25Uut4jdq0UC3QhE7lc9BMtsna7a18jYR
vESOIbDSRHMkR1ptazlmgH6wvLrX6pm/PcT7TLXsZ1/2E7k7tlJRmpOLBaMBuasn
3iLySZ6g6RGVDmBOEStNppcP9THQRL+mAmwF1EV45sCF+4scg8ybC+Xb1Qpgv6r6
RGOSGfBb+3uH/RRw3vV6auyFLW274efmwZcQNytbPME1EkXnQQm0aquAM1vG8kU0
d6JlvqkLNOXhNnAzNLazTUmAYsOtduYClAWi5X64hvognvDwb6aDIsZsMiMLFQNJ
5c1hivb9NU4MOir4OGJE4m25flkckDA/IRrU7QCufax5DLTfqRYJBZa9t2xZrWOJ
gJNRLo1nXBqx7iiKB0tjHT/3Dv071IeeA9TmeJya/xmyF5tYf4IkM2zD5shK9eZn
93lHPGvEBDc6by/gPyygjB3XFznAzyySKcKWV/QOcHHoQLpiegDg0aVyTcmYcI/e
biODK/LURjQuO3uDX6uoyQw/Y2CJnylRNbCWVOaUCAYFhTuPFsriKV9IF5PlcX1x
sOdauyMWjQWXH78yj2ocjXSrCzGBbDlqp4WwDFKvCnS+dBcP0P014kuhC67snAah
IeD8olcJd4taP5SE390KIyC1IXYweFcxNFhaCaJPjUaacOkJUfY=
=sDJk
-END PGP SIGNATURE End Message ---

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

2023-12-10 Thread tony mancill

On Sun, Dec 10, 2023 at 08:18:03PM +0100, Santiago Vila wrote:
> Package: src:libjose4j-java
> Version: 0.7.12-2
> Severity: serious
> Tags: ftbfs
> 
> [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.063 
> s <<< FAILURE! - in org.jose4j.jwk.EllipticCurveJsonWebKeyTest
> [ERROR] 
> testParseExampleWithPrivate256(org.jose4j.jwk.EllipticCurveJsonWebKeyTest)  
> Time elapsed: 0.031 s  <<< FAILURE!
> java.lang.AssertionError:
> expected: [8b:e2:14:0f:3a:17:e9:25:d1:ae:df:18:a3:b2:9a:fd:63:04:41:11]
> X: 
> 7fcdce2770f6c45d4183cbee6fdb4b7b580733357be9ef13bacf6e3c7bd15445
> Y: 
> c7f144cd1bbd9b7e872cdfedb9eeb9f4b3695d6ea90b24ad8a4623288588e5ad
> > but was:
>   at 
> org.jose4j.jwk.EllipticCurveJsonWebKeyTest.testParseExampleWithPrivate256(EllipticCurveJsonWebKeyTest.java:53)
> ...
>
> If required, the full build log is available here:
> 
> https://people.debian.org/~sanvila/build-logs/202312/

Thank you for making this available.

> About the archive rebuild: The build was made using virtual machines
> from AWS, with enough memory, enough disk, and either one or two
> CPUs, using a reduced chroot with only build-essential packages.

I'm not able to reproduce this locally, and the only potentially
relevant difference I see between the AWS testbed and my local
environment is that I am running Intel and the AWS system is AMD.

> If you could not reproduce the bug please contact me privately, as I
> am willing to provide ssh access to a virtual machine where the bug is
> fully reproducible.

Will do, as time permits.

This package has a low popcon, and is a build-dependency of
libcallstats-java, which also has a low popcon, and has no reverse
dependencies.  I believe both are part of an effort to get Jitsi back
into Debian.  If that's not likely to happen, an alternative is to file
RM bugs for both of them.  (I am adding the Uploaders to the cc:)

Thanks,
tony

signature.asc
Description: PGP signature

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}


El 10/12/23 a las 22:09, Markus Uhlin escribió:

My guess is that Ncurses is built with '--enable-opaque-curses' and defines 
NCURSES_OPAQUE=1.
I'm currently running stable so I'm not able to reproduce the problem but if 
you can give me access to a computer where the problem occurs I can investigate 
it.


Hmm, please note that when I say "if you can't reproduce it" it should
be understood as "if you can't reproduce it using an unstable chroot".

So, you should really use an unstable chroot in your own computer
first (you can create it with debootstrap and then use it with schroot).

Regarding the bug itself: Here is a very similar one which maybe gives
you an idea about how to fix it, as it contains a fix at the end:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057553

Thanks.

Bug#1055049: libtakari-polyglot-groovy-java: missing Breaks+Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)

2023-12-10 Thread Andreas Beckmann

Ok what I think I'll do is to add: "Breaks: 
libtakari-polyglot-maven-java (<< 0.4.11-2)" to 
libtakari-polyglot-groovy-java. I think that's more explicit than a 
versioned depends, and should prevent any instances of users 
accidentally having wrong versions of the two packages.


You'll need both
  Breaks:   libtakari-polyglot-maven-java (<< 0.4.11-2)
  Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)
s.t. dkms handles the takeover of the files correctly in all poassible 
unpacking orderings.




Andreas

Bug#1057946: pypandoc: autopkgtest needs update for new version of pandoc

2023-12-10 Thread Jonas Smedegaard

Quoting Paul Gevers (2023-12-10 21:40:34)
> Source: pypandoc
> Version: 1.7.4+ds0-2
> Severity: serious
> X-Debbugs-CC: pan...@packages.debian.org
> Tags: sid trixie
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:pandoc
> 
> Dear maintainer(s),
> 
> With a recent upload of pandoc the autopkgtest of pypandoc fails in 
> testing when that autopkgtest is run with the binary packages of pandoc 
> from unstable. It passes when run with only packages from testing. In 
> tabular form:
> 
> passfail
> pandoc from testing2.17.1.1+~git20230125+ds-1
> pypandoc   from testing1.7.4+ds0-2
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report. The failing 
> tests checks that the version of pandoc is lower than the current version.
> 
> Currently this regression is blocking the migration of pandoc to testing 
> [1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
> worse, your package), but it seems to me that the change in pandoc was 
> intended and your package needs to update to the new situation.
> 
> If this is a real problem in your package (and not only in your 
> autopkgtest), the right binary package(s) from pandoc should really add 
> a versioned Breaks on the unfixed version of (one of your) package(s). 
> Note: the Breaks is nice even if the issue is only in the autopkgtest as 
> it helps the migration software to figure out the right versions to 
> combine in the tests.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=pandoc
> 
> https://ci.debian.net/packages/p/pypandoc/testing/amd64/40824353/
> 
> 
>   69s ==
>   69s FAIL: test_get_pandoc_version 
> (tests.TestPypandoc.test_get_pandoc_version)
>   69s --
>   69s Traceback (most recent call last):
>   69s   File 
> "/tmp/autopkgtest-lxc._ozpb6jh/downtmp/build.wmM/src/tests.py", line 
> 159, in test_get_pandoc_version
>   69s self.assertTrue(major in [0, 1, 2])
>   69s AssertionError: False is not true

Pandoc is a library and an executable binary.  The package pandoc
version 2.17.1.1+~git20230125+ds-1 links against ghc-pandoc-dev version
3.0.1-3.

Yesterday, upstream agreed to change the versioning of the executable
binary to be in sync with the library - as was the case with 1.x and 2.x
releases.  I have just now released pandoc version 3.0.1-1.

Hope that helps.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1057949: nbconvert: needs update for new version of pandoc: PDF creating failed

2023-12-10 Thread Jonas Smedegaard

Quoting Paul Gevers (2023-12-10 21:45:50)
> With a recent upload of pandoc the autopkgtest of nbconvert fails in 
> testing when that autopkgtest is run with the binary packages of pandoc 
> from unstable. It passes when run with only packages from testing. In 
> tabular form:
> 
> passfail
> pandoc from testing2.17.1.1+~git20230125+ds-1
> nbconvert  from testing6.5.3-4
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
[...]
> 378s [1m[31mE 
> /usr/lib/python3/dist-packages/nbconvert/utils/pandoc.py:51: 
> RuntimeWarning: You are using an unsupported version of pandoc (3.0.1).[0m

Pandoc is a library and an executable binary.  The package pandoc
version 2.17.1.1+~git20230125+ds-1 links against ghc-pandoc-dev version
3.0.1-3.

Yesterday, upstream agreed to change the versioning of the executable
binary to be in sync with the library - as was the case with 1.x and 2.x
releases.  I have just now released pandoc version 3.0.1-1.

Hope that helps.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-10 Thread Markus Uhlin

My guess is that Ncurses is built with '--enable-opaque-curses' and 
defines NCURSES_OPAQUE=1.
I'm currently running stable so I'm not able to reproduce the problem 
but if you can give me access to a computer where the problem occurs I 
can investigate it.


Den 2023-12-10 kl. 20:18, skrev Santiago Vila:
invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

Bug#1056512: marked as done (python-vdf's autopkg tests fail with Python 3.12)

Your message dated Sun, 10 Dec 2023 21:34:30 +
with message-id 
and subject line Bug#1056512: fixed in python-vdf 3.4-3
has caused the Debian Bug report #1056512,
regarding python-vdf's autopkg tests fail with 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.)


-- 
1056512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-vdf
Version: 3.4-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-vdf's autopkg tests fail with Python 3.12:

[...]
332s autopkgtest [18:56:37]: test python3: [---
332s + export RUN_SLOW_TESTS=1
332s + mkdir /tmp/autopkgtest.eEXwxK/autopkgtest_tmp/tests/
332s + install tests/__init__.py tests/test_binary_vdf.py 
tests/test_vdf.py tests/test_vdf_dict.py 
/tmp/autopkgtest.eEXwxK/autopkgtest_tmp/tests/

332s + cd /tmp/autopkgtest.eEXwxK/autopkgtest_tmp
332s + failed=0
332s + py3versions -s
332s + python3.12 -u -m unittest -v tests
332s
332s --
332s Ran 0 tests in 0.000s
332s
332s NO TESTS RAN
332s + failed=1
332s + python3.11 -u -m unittest -v tests
332s
332s --
332s Ran 0 tests in 0.000s
332s
332s OK
332s + python3 -u -m unittest -v tests
332s
332s --
332s Ran 0 tests in 0.000s
332s
332s OK
332s + exit 1
332s autopkgtest [18:56:37]: test python3: ---]
332s autopkgtest [18:56:37]: test python3:  - - - - - - - - - - results 
- - - - - - - - - -

332s python3  FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: python-vdf
Source-Version: 3.4-3
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
python-vdf, 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.
Simon McVittie  (supplier of updated python-vdf 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: Sun, 10 Dec 2023 21:04:05 +
Source: python-vdf
Architecture: source
Version: 3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Simon McVittie 
Closes: 1056512
Changes:
 python-vdf (3.4-3) unstable; urgency=medium
 .
   * d/tests: Really run unit tests (Closes: #1056512)
   * Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
 9db249743e3a430619c33fb680846a3f9011ae83  python-vdf_3.4-3.dsc
 4251aed5f8a8d47264c6c5043f9df6d00ca50f80 2684 python-vdf_3.4-3.debian.tar.xz
 8a21cc8fb80ad1afb8edf889c41e54ef0a30806f 6492 python-vdf_3.4-3_source.buildinfo
Checksums-Sha256:
 6dfbbc144d8ba459eafa0c5c08beb9ca59fb021e6b4137d7242a9c67ba5f635c  
python-vdf_3.4-3.dsc
 be00b6d74a99218eedafc52ffc2d64fe0d2ca168244bd2898ca4bdde0d6e4486 2684 
python-vdf_3.4-3.debian.tar.xz
 9678eab56ef0884b931cd7c6be4cdf7b7449fc372aef6ba64bc2e792d7b788f1 6492 
python-vdf_3.4-3_source.buildinfo
Files:
 7b492c72f0c6557a5a2b8e33d6b25677  python optional python-vdf_3.4-3.dsc
 b80c47a52aa5fc00920f0498a7f2a3ff 2684 python optional 
python-vdf_3.4-3.debian.tar.xz
 5736516a9592fa745475f6fccbc0c52d 6492 python optional 
python-vdf_3.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmV2LAsACgkQ4FrhR4+B
TE97vw//TfMp9DeLVokd/d9m+PBpJRS7gyBMTH/Kn3tQvVjx1e9GxUuN9mRLbRBj
XGlFsSoU80oTKy6EfbOU2M1FfOHv1N6dsDcjJiJaoafNTgk1KdgZwfufXYeXJUw/
o87wzFZxLDWkENh3wpUvjZForJrTb3aWO+jr7eCrTwleZKrsODmh7Qkw22o3zkjH
ahanj8YzIJIrJqqGYF+1WQhpM9/XITIu8NJI84rWolMZ3XxTTYgwNWKAXS//uvuQ
mlQDKAFufK2rdn7mRQ7FvKKPnvw4T8HbA8IdxInOJhfRfgQynJ0niitGp1+1XrPA
MsOPzUNrjY1h5jY1ClgWkIG6QxjcEJRjMpDrmiEF+SnFVOF32cXwKqO9MOtm6aei
uYHBmztPU8UjLGSvFzLI/CK20maevVwdGdUriHJtavjMLrI+NJ9kyCGUds8KZi5c
qh4X7Fpy3gYEpvdFFy8no+qjjNLyw0jV12xU0cloJDzp8ZSV07C22zkW3nMbSsxZ
OXZrfhvy1LXcroHUqbIebVHj59RnrJX0i3E/9feHXEDbRT7eFkDz8O26pHR/Roy7
6zxSgn+JavKz4Z4pVrCamYAUWjd1jwhyOSq9n2W/6U4qTJ3UF5qOkU/RK9z00s32

Bug#1057952: pandoc: FTBFS on ppc64el: This version of pandoc has been compiled without Lua support.

2023-12-10 Thread Sebastian Ramacher

Source: pandoc
Version: 2.17.1.1+~git20230125+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

Thanks for working on the pandoc update. Unfortunately, it fails to
build on ppc64el due to the missing lua support:

https://buildd.debian.org/status/fetch.php?pkg=pandoc=ppc64el=2.17.1.1%2B%7Egit20230125%2Bds-1=1702140012=0

dist-ghc/build/pandoc/pandoc MANUAL.txt -f markdown -t man -s \
--lua-filter man/manfilter.lua \
--include-before-body man/pandoc.1.before \
--include-after-body man/pandoc.1.after \
--metadata author="" \
--variable footer="pandoc 3.0.1+2.17.1.1+~git20230125+ds-1" \
-o man/pandoc.1
This version of pandoc has been compiled without Lua support.
make: *** [debian/rules:95: man/pandoc.1] Error 89

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1056485: python-mpd's autopkg tests fail with Python 3.12

Processing control commands:

> forwarded -1 https://github.com/Mic92/python-mpd2/issues/214
Bug #1056485 [src:python-mpd] python-mpd's autopkg tests fail with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/Mic92/python-mpd2/issues/214'.
> tags -1 + upstream help
Bug #1056485 [src:python-mpd] python-mpd's autopkg tests fail with Python 3.12
Added tag(s) upstream and help.

-- 
1056485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056485: python-mpd's autopkg tests fail with Python 3.12

2023-12-10 Thread Simon McVittie

Control: forwarded -1 https://github.com/Mic92/python-mpd2/issues/214
Control: tags -1 + upstream help

On Wed, 22 Nov 2023 at 15:18:06 +0100, Matthias Klose wrote:
> python-mpd's autopkg tests fail with Python 3.12:
> [...]
> 248s mpd.base.ConnectionError: Can not send command to disconnected client

Fedora opened an equivalent bug upstream. No fix is currently known -
patches would be very much appreciated.

Thanks,
smcv

Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'


Package: src:promod3
Version: 3.3.1+ds-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 python3
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON -DOST_ROOT=/usr 
-DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON 
-DOST_ROOT=/usr -DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib ..
-- The CXX compiler identification is GNU 13.2.0
-- The C compiler identification is GNU 13.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped

[... snipped ...]

make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f loop/pymod/CMakeFiles/loop_pymod.dir/build.make 
loop/pymod/CMakeFiles/loop_pymod.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/loop/pymod && /usr/bin/cmake -E copy_if_different 
/<>/loop/pymod/__init__.py 
/<>/obj-x86_64-linux-gnu/stage/lib64/python3.11/site-packages//promod3/loop/__init__.py
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./backbone.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./backbone.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  0%] Built target loop_pymod
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/scoring/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/scoring/src 
/<>/obj-x86_64-linux-gnu/scoring/src/CMakeFiles/promod3_scoring_headers.dir/DependInfo.cmake "--color="
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./bb_trace_param.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./bb_trace_param.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/build
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./data_bag.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./data_bag.hh
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_score_base.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_score_base.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_overall_scorer.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_overall_scorer.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_hash_table.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_hash_table.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./scoring_object_loader.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./scoring_object_loader.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_map.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_map.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_map.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_map.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./density_creator.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./density_creator.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./forcefield_lookup.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./forcefield_lookup.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./frag_db.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./frag_db.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./cbeta_env_listener.hh

Bug#1057950: dask.distributed: FTBFS: TypeError: not all arguments converted during string formatting


Package: src:dask.distributed
Version: 2023.8.0+ds.1-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 python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f distributed/comm/tests/__init__.py
set -e; \
for p in distributed/http/static/js/anime.js 
distributed/http/static/js/reconnecting-websocket.js; do \
uglifyjs -o $p debian/missing-sources/$p ; \
done
chmod a-x distributed/tests/test_utils_test.py
dh_auto_build

[... snipped ...]

copying build/lib/distributed/cli/tests/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_tls_cli.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/active_memory_manager.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/versions.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/lock.py -> 
build/bdist.linux-x86_64/wheel/distributed
creating build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
creating build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive_core.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_spec_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_slow_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_deploy_utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_subprocess.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_old_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/adaptive_core.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/old_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/subprocess.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
creating build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_merge.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_disk.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_worker_plugin.py ->

Bug#1057949: nbconvert: needs update for new version of pandoc: PDF creating failed

2023-12-10 Thread Paul Gevers


Source: nbconvert
Version: 6.5.3-4
Severity: serious
X-Debbugs-CC: pan...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pandoc

Dear maintainer(s),

With a recent upload of pandoc the autopkgtest of nbconvert fails in 
testing when that autopkgtest is run with the binary packages of pandoc 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
pandoc from testing2.17.1.1+~git20230125+ds-1
nbconvert  from testing6.5.3-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pandoc to testing 
[1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in pandoc was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pandoc should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pandoc

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbconvert/40824350/log.gz

378s [1m[31mE 
/usr/lib/python3/dist-packages/nbconvert/utils/pandoc.py:51: 
RuntimeWarning: You are using an unsupported version of pandoc (3.0.1).[0m
378s [1m[31mE   Your version must be at least (1.12.1) but 
less than (3.0.0).[0m

378s [1m[31mE   Refer to https://pandoc.org/installing.html.[0m
378s [1m[31mE   Continuing with doubts...[0m
378s [1m[31mE check_pandoc_version()[0m
378s [1m[31mE   [NbConvertApp] Support files will be in 
notebook2_files/[0m
378s [1m[31mE   [NbConvertApp] Making directory 
./notebook2_files[0m
378s [1m[31mE   [NbConvertApp] Writing 2889 bytes to support 
file ./notebook2_files/notebook2_13_1.png[0m
378s [1m[31mE   [NbConvertApp] Making directory 
./notebook2_files[0m
378s [1m[31mE   [NbConvertApp] Writing 74369 bytes to support 
file ./notebook2_files/notebook2_13_1.pdf[0m
378s [1m[31mE   [NbConvertApp] Writing 25528 bytes to 
notebook.tex[0m

378s [1m[31mE   [NbConvertApp] Building PDF[0m
378s [1m[31mE   [NbConvertApp] Running xelatex 1 time: 
['xelatex', 'notebook.tex', '-quiet'][0m
378s [1m[31mE   [NbConvertApp] CRITICAL | xelatex failed: 
['xelatex', 'notebook.tex', '-quiet'][0m

378s [1m[31mE   [0m
378s [1m[31mE   Traceback (most recent call last):[0m
378s [1m[31mE File "", line 198, in 
_run_module_as_main[0m

378s [1m[31mE File "", line 88, in _run_code[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/__main__.py", line 3, in 
[0m

378s [1m[31mE   main()[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/jupyter_core/application.py", line 282, 
in launch_instance[0m
378s [1m[31mE   super().launch_instance(argv=argv, 
**kwargs)[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
982, in launch_instance[0m

378s [1m[31mE   app.start()[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 423, in 
start[0m

378s [1m[31mE   self.convert_notebooks()[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 597, in 
convert_notebooks[0m
378s [1m[31mE 
self.convert_single_notebook(notebook_filename)[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 560, in 
convert_single_notebook[0m
378s [1m[31mE   output, resources = 
self.export_single_notebook([0m
378s [1m[31mE 
[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 488, in 
export_single_notebook[0m
378s [1m[31mE   output, resources = 
self.exporter.from_filename([0m
378s [1m[31mE 
[0m
378s [1m[31mE File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
189, in from_filename[0m
378s [1m[31mE   return self.from_file(f, 
resources=resources, **kw)[0m
378s [1m[31mE 
[0m
378s [1m[31mE File

Processed: nbconvert: needs update for new version of pandoc: PDF creating failed

Processing control commands:

> affects -1 src:pandoc
Bug #1057949 [src:nbconvert] nbconvert: needs update for new version of pandoc: 
PDF creating failed
Added indication that 1057949 affects src:pandoc

-- 
1057949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057932: kgb-bot: FTBFS: Failed test 'Changes contains all valid release dates'

2023-12-10 Thread gregor herrmann

COntrol: tag -1 + confirmed

On Sun, 10 Dec 2023 20:17:56 +0100, Santiago Vila wrote:

> During a rebuild of all packages in unstable, your package failed to build:

> #   Failed test 'Changes contains all valid release dates'
> #   at t/changes.t line 6.
> #   ERR: No date for version 1.59 (line 1)
> # Looks like you failed 1 test of 6.
> t/changes.t ...
> ok 1 - Changes is loadable
> ok 2 - Changes contains at least one release
> not ok 3 - Changes contains all valid release dates
> ok 4 - Changes contains all valid release versions
> ok 5 - Changes has an entry for version 1.59
> ok 6 - Changes version 1.59 has content
> 1..6
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/6 subtests

t/changes.t uses Test::CPAN::Changes in libcpan-changes-perl, which
was recently updated.

I guess, writing the "headers" in ./Changes as "1.59 2023-10-30" or
"1.59 - 2023-10-30" instead of "1.59 (2023-10-30)" could work.

(Maybe also guarding a few tests in t/ with RELEASE_TESTING …)

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Re: Bug#1057932: kgb-bot: FTBFS: Failed test 'Changes contains all valid release dates'

Processing control commands:

> tag -1 + confirmed
Bug #1057932 [src:kgb-bot] kgb-bot: FTBFS: Failed test 'Changes contains all 
valid release dates'
Added tag(s) confirmed.

-- 
1057932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057946: pypandoc: autopkgtest needs update for new version of pandoc

2023-12-10 Thread Paul Gevers


Source: pypandoc
Version: 1.7.4+ds0-2
Severity: serious
X-Debbugs-CC: pan...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pandoc

Dear maintainer(s),

With a recent upload of pandoc the autopkgtest of pypandoc fails in 
testing when that autopkgtest is run with the binary packages of pandoc 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
pandoc from testing2.17.1.1+~git20230125+ds-1
pypandoc   from testing1.7.4+ds0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. The failing 
tests checks that the version of pandoc is lower than the current version.


Currently this regression is blocking the migration of pandoc to testing 
[1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in pandoc was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pandoc should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pandoc

https://ci.debian.net/packages/p/pypandoc/testing/amd64/40824353/


 69s ==
 69s FAIL: test_get_pandoc_version 
(tests.TestPypandoc.test_get_pandoc_version)

 69s --
 69s Traceback (most recent call last):
 69s   File 
"/tmp/autopkgtest-lxc._ozpb6jh/downtmp/build.wmM/src/tests.py", line 
159, in test_get_pandoc_version

 69s self.assertTrue(major in [0, 1, 2])
 69s AssertionError: False is not true


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: pypandoc: autopkgtest needs update for new version of pandoc

Processing control commands:

> affects -1 src:pandoc
Bug #1057946 [src:pypandoc] pypandoc: autopkgtest needs update for new version 
of pandoc
Added indication that 1057946 affects src:pandoc

-- 
1057946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057947: hp48cc: missing error trapping in Makefile

2023-12-10 Thread Helmut Grohne

Source: hp48cc
Version: 1.0-3
Severity: serious
Justification: policy section 4.6

Debian policy section 4.6 requires that failures from a build step are
propagated rather than continuing and possibly misbuilding. hp48cc
violates this in the upstream build system. The toplevel Makefile.in
says:

| all install clean realclean mostyclean:
|   @for f in $(subdirs); do \
|   (cd $$f && $(MAKE) $@) \
|   done

If any of these fails, no failure is raised and the build continues. I
suggest adding "set -e" before the loop to fix this.

Helmut

Bug#1041430: marked as done (ruby-sanitize: CVE-2023-36823)

Your message dated Sun, 10 Dec 2023 19:54:11 +
with message-id 
and subject line Bug#1041430: fixed in ruby-sanitize 6.0.2-1
has caused the Debian Bug report #1041430,
regarding ruby-sanitize: CVE-2023-36823
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.)


-- 
1041430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sanitize
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ruby-sanitize.

CVE-2023-36823[0]:
| Sanitize is an allowlist-based HTML and CSS sanitizer. Using
| carefully crafted input, an attacker may be able to sneak arbitrary
| HTML and CSS through Sanitize starting with version 3.0.0 and prior
| to version 6.0.2 when Sanitize is configured to use the built-in
| "relaxed" config or when using a custom config that allows `style`
| elements and one or more CSS at-rules. This could result in cross-
| site scripting or other undesired behavior when the malicious HTML
| and CSS are rendered in a browser. Sanitize 6.0.2 performs
| additional escaping of CSS in `style` element content, which fixes
| this issue. Users who are unable to upgrade can prevent this issue
| by using a Sanitize config that doesn't allow `style` elements,
| using a Sanitize config that doesn't allow CSS at-rules, or by
| manually escaping the character sequence `https://github.com/rgrove/sanitize/commit/76ed46e6dc70820f38efe27de8dabd54dddb5220
 (v6.0.2)
https://github.com/rgrove/sanitize/security/advisories/GHSA-f5ww-cq3m-q3g7
  

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-36823
https://www.cve.org/CVERecord?id=CVE-2023-36823

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ruby-sanitize
Source-Version: 6.0.2-1
Done: Abhijith PA 

We believe that the bug you reported is fixed in the latest version of
ruby-sanitize, 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.
Abhijith PA  (supplier of updated ruby-sanitize package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 22:52:54 +0530
Source: ruby-sanitize
Binary: ruby-sanitize
Architecture: source all
Version: 6.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Abhijith PA 
Description:
 ruby-sanitize - whitelist-based HTML sanitizer
Closes: 1041430
Changes:
 ruby-sanitize (6.0.2-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
 .
   [Abhijith PA]
   * New upstream release
 Fix CVE-2023-36823 (Closes: #1041430)
   * Remove X*-Ruby fields
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 cadd3d8ceb0dadd8bccb987bf88314d4cc7fdec4 2101 ruby-sanitize_6.0.2-1.dsc
 cdfb890da8c02ca127d775162c34bdc5d44904a2 45157 ruby-sanitize_6.0.2.orig.tar.gz
 a30ad69229068dbd5fb822e9804242c448c52233 3820 
ruby-sanitize_6.0.2-1.debian.tar.xz
 452243a286f851e4c3e8799d6824cd3f96768ed2 34688 ruby-sanitize_6.0.2-1_all.deb
 1cd3832a86ac9f6fe44cdd305ea2bdc1416cf861 9688 
ruby-sanitize_6.0.2-1_amd64.buildinfo
Checksums-Sha256:
 aaef94ca95f63bdfe52768f730fbc09a7e104f43ea322ac3c331ceb4aeb2183b 2101 
ruby-sanitize_6.0.2-1.dsc
 17ab5fbf9a69027904ee866b263050808aa3c732b7984b5cb6c9bcc1d43b4684 45157 
ruby-sanitize_6.0.2.orig.tar.gz
 a42229ecc2de95f50ab35a2521dbf8852f2f6ee240da03edeca03f8b87c7a832 3820 
ruby-sanitize_6.0.2-1.debian.tar.xz
 7d7f2fee48919a695c2a2de232ab4e30eb47c00382fba63538ea127fa7850a4a 34688 
ruby-sanitize_6.0.2-1_all.deb
 980b1adb711b183a661610e8aae7725068c31ea5eb821248d6e05ad8bf3c1e84 9688 
ruby-sanitize_6.0.2-1_amd64.buildinfo
Files:
 dc1bc705b07f52a14ac5dc9194fc7e37 2101 ruby optional ruby-sanitize_6.0.2-1.dsc
 b2deed2915f7b02f30217080774acc90 45157 ruby optional 
ruby-sanitize_6.0.2.orig.tar.gz

Bug#1057941: ycm-cmake-modules: FTBFS: TypeError: not all arguments converted during string formatting


Package: src:ycm-cmake-modules
Version: 0.13.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --without build-stamp --with linktree
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
 -DSPHINX_HTML=ON \
 -DSPHINX_MAN=ON \
 -DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules \
 -DCMAKE_INSTALL_LIBDIR=share \
 -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DSPHINX_HTML=ON -DSPHINX_MAN=ON 
-DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules -DCMAKE_INSTALL_LIBDIR=share 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF ..
-- YCM Version: 0.13.0 (0.13.0)
CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message):
  A "FindGSL.cmake" module already exists in CMAKE_ROOT.  Please remove it,
  or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message):
  A "FindOpenGL.cmake" module already exists in CMAKE_ROOT.  Please remove
  it, or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at deprecated/CMakeLists.txt:19 (message):
  A "FindGLUT.cmake" module already exists in CMAKE_ROOT.  Please remove it,
  or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done (0.5s)
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_FIND_USE_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_prep
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
cd obj-x86_64-linux-gnu && make -j2 install 
DESTDIR=/<>/debian/ycm-cmake-modules AM_UPDATE_INFO_DIR=no "INSTALL=install 
--strip-program=true"
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f modules/CMakeFiles/modules.dir/build.make 
modules/CMakeFiles/modules.dir/depend
make  -f find-modules/CMakeFiles/find-modules.dir/build.make 
find-modules/CMakeFiles/find-modules.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/modules 
/<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/DependInfo.cmake "--color="
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/find-modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/find-modules 
/<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/DependInfo.cmake "--color="
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f find-modules/CMakeFiles/find-modules.dir/build.make 
find-modules/CMakeFiles/find-modules.dir/build
make  -f modules/CMakeFiles/modules.dir/build.make 
modules/CMakeFiles/modules.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E 
echo_append
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E 
echo_append
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E touch 
/<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/ycm_download-complete
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E touch 
/<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/ycm_download-complete
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E 
echo_append
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E 
echo_append
cd

Bug#1057942: ydpdict: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}


Package: src:ydpdict
Version: 1.0.4-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
   dh_update_autotools_config
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
Copying file ABOUT-NLS
Copying file config.rpath
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:9: installing './compile'
configure.ac:12: installing './config.guess'
configure.ac:12: installing './config.sub'
configure.ac:5: installing './install-sh'
configure.ac:5: installing './missing'
src/Makefile.am: installing './depcomp'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --with-dictdir=/usr/local/share/ydpdict
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-dictdir=/usr/local/share/ydpdict
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
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 whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
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 dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC

Bug#1057939: recommonmark: FTBFS: FAIL: test_headings (tests.test_sphinx.GenericTests.test_headings)


Package: src:recommonmark
Version: 0.7.1+ds-5
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 python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
running config
I: pybuild base:310: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:310: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12/build/recommonmark

[... snipped ...]

/<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
UserWarning: Container node skipped: type=document
  warn("Container node skipped: type={0}".format(mdnode.t))

[91m/<>/.pybuild/cpython3_3.11/build/tests/sphinx_generic/index.md::
 WARNING: image file not readable: image.png[39;49;00m
[01mlooking for now-outdated files... [39;49;00mnone found
[01mpickling environment... [39;49;00mdone
[01mchecking consistency... [39;49;00mdone
[01mpreparing documents... [39;49;00mdone
[01mcopying assets... [39;49;00m[01mcopying static files... [39;49;00mdone
[01mcopying extra files... [39;49;00mdone
done
[01mwriting output... [39;49;00m[100%] [32mindex[39;49;00m

[91m/<>/.pybuild/cpython3_3.11/build/tests/sphinx_generic/index.md:13:
 WARNING: None:any reference target not found: /example[39;49;00m
[01mgenerating indices... [39;49;00mgenindex done
[01mwriting additional pages... [39;49;00msearch done
[01mdumping search index in English (code: en)... [39;49;00mdone
[01mdumping object inventory... [39;49;00mdone
[01mbuild succeeded, 56 warnings.[39;49;00m

The HTML pages are in tests/sphinx_generic/_build/text.
ok
test_lists (tests.test_sphinx.GenericTests.test_lists) ... [01mRunning Sphinx 
v7.2.6[39;49;00m
[91mWARNING: Invalid configuration value found: 'language = None'. Update your 
configuration to a valid language code. Falling back to 'en' 
(English).[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 'toctree' 
is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 'desc' is 
already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_signature' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_signature_line' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_content' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_inline' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_name' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_addname' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_type' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_returns' is already registered, its visitors will be overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_parameterlist' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_type_parameter_list' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_parameter' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_type_parameter' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_optional' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_annotation' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_sig_keyword_type' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING: while setting up extension sphinx.addnodes: node class 
'desc_sig_punctuation' is already registered, its visitors will be 
overridden[39;49;00m
[91mWARNING:

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}


Package: src:swirc
Version: 3.4.6-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 --without autoreconf
   dh_update_autotools_config
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --with-libnotify
creating temp file...ok
checking whether the etext segment is usable...yes
cleaning...
creating temp file...ok
checking for strcasestr()...yes
cleaning...
creating temp file...ok
checking whether to define 'USE_LIBNOTIFY=1'...yes
cleaning...
creating temp file...ok
checking for gnu libiconv...yes
cleaning...
creating temp file...ok
checking for gnu libidn...yes
cleaning...
creating temp file...ok
checking for 'libintl.h'...yes
cleaning...
creating temp file...ok
checking for libintl_setlocale()...no
cleaning...
make[2]: Entering directory '/<>/po'
msgfmt --output-file=de/swirc.mo de/swirc.po
msgfmt --output-file=fi/swirc.mo fi/swirc.po
msgfmt --output-file=fr/swirc.mo fr/swirc.po
msgfmt --output-file=sv/swirc.mo sv/swirc.po
make[2]: Leaving directory '/<>/po'
creating temp file...ok
checking for hunspell...yes
cleaning...
configure: options.mk successfully created!
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j2
make[1]: Entering directory '/<>'
  CXX  src/commands/admin.o
  CC   src/commands/ban.o
  CXX  src/commands/cap.o
  CXX  src/commands/cleartoasts.o
  CXX  src/commands/colormap.o
  CC   src/commands/connect.o
In file included from src/commands/../terminal.h:5,
 from src/commands/connect.c:49:
src/commands/../term-unix.h: In function ‘term_set_attr’:
src/commands/../term-unix.h:38:20: error: invalid use of incomplete typedef 
‘WINDOW’ {aka ‘struct _win_st’}
   38 | win->_attrs = at;
  |^~
make[1]: *** [Makefile:17: src/commands/connect.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j2 returned exit code 2
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057937: pkcs11-provider: FTBFS: failing tests


Package: src:pkcs11-provider
Version: 0.2+g20231107-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
   dh_update_autotools_config
   dh_autoreconf
aclocal: warning: couldn't open directory 'm4': No such file or directory
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:13: installing './ar-lib'
configure.ac:12: installing './compile'
configure.ac:14: installing './config.guess'
configure.ac:14: installing './config.sub'
configure.ac:8: installing './install-sh'
configure.ac:8: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
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 whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
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 dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes

Bug#1057938: python-duniterpy: FTBFS: RuntimeError: The Poetry configuration is invalid


Package: src:python-duniterpy
Version: 1.1.1-2
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=pybuild --with=sphinxdoc
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11
* Building wheel...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 353, in 
main()
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
 
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 251, in build_wheel
return _build_backend().build_wheel(wheel_directory, config_settings,
   ^^
  File "/usr/lib/python3/dist-packages/poetry/core/masonry/api.py", line 55, in 
build_wheel
poetry = Factory().create_poetry(Path(".").resolve(), with_groups=False)
 ^^^
  File "/usr/lib/python3/dist-packages/poetry/core/factory.py", line 58, in 
create_poetry
raise RuntimeError("The Poetry configuration is invalid:\n" + message)
RuntimeError: The Poetry configuration is invalid:
  - data.homepage must be uri


ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: python3.11 -m 
build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057936: odpic: FTBFS: UndefinedError("'style' is undefined")


Package: src:odpic
Version: 4.6.0-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
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
mkdir -p build
mkdir -p lib
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiConn.c -o build/dpiConn.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiContext.c -o build/dpiContext.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiData.c -o build/dpiData.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiEnv.c -o build/dpiEnv.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiError.c -o build/dpiError.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiGen.c -o build/dpiGen.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiGlobal.c -o build/dpiGlobal.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiLob.c -o build/dpiLob.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObject.c -o build/dpiObject.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObjectAttr.c -o build/dpiObjectAttr.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObjectType.c -o build/dpiObjectType.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiPool.c -o build/dpiPool.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiStmt.c -o build/dpiStmt.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiUtils.c -o build/dpiUtils.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiVar.c -o build/dpiVar.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiOracleType.c -o build/dpiOracleType.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiSubscr.c -o build/dpiSubscr.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiDeqOptions.c -o build/dpiDeqOptions.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong

Bug#1057935: ncurses-hexedit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}


Package: src:ncurses-hexedit
Version: 0.9.7+orig-7.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
   debian/rules override_dh_update_autotools_config
make[1]: Entering directory '/<>'
dh_update_autotools_config
test -f debian/backup.tar || \
tar cpf debian/backup.tar -T debian/mutable
make[1]: Leaving directory '/<>'
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
configure.ac:11: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.ac:11: You should use the 'AC_CONFIG_HEADERS' macro instead.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:745: AM_CONFIG_HEADER is expanded from...
configure.ac:11: the top level
configure.ac:22: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:22: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:22: the top level
configure.ac:109: warning: AC_OUTPUT should be used without arguments.
configure.ac:109: You should run autoupdate.
configure.ac:13: installing './compile'
src/Makefile.am: installing './depcomp'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
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 whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
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 grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for ncurses.h... yes
checking for fcntl.h... yes
checking for getopt.h... yes
checking for limits.h... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for an ANSI C-conforming const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for snprintf... yes
checking for isprint... yes
checking for getopt_long... yes
checking for TIOCGWINSZ... yes, found in termio.h
checking for newwin in -lncurses... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating gnu/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
rm -f debian/ncurses-hexedit.debhelper.log
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- \

make -j2
make[2]: Entering directory '/<>'
make  all-recursive
make[3]: Entering directory '/<>'
Making all in docs
make[4]: Entering directory '/<>/docs'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash '/<>/missing' makeinfo --version) >/dev/null 2>&1; 
then \
  for f in hexeditor.info hexeditor.info-[0-9]

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported


Package: src:libjose4j-java
Version: 0.7.12-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
mh_patchpoms -plibjose4j-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
-Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
deprecated in JDK 13 and will likely be removed in a future release.
[0m[0m[INFO] Scanning for projects...
[INFO]
[INFO] --< org.bitbucket.b_c:jose4j >--
[INFO] Building jose4j 0.7.12
[INFO] [ jar ]-

[... snipped ...]

at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:61)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
14:19:37.806 DEBUG org.jose4j.jwk.JsonWebKeySet - Ignoring an individual JWK in a JWKS due to a problem processing it. JWK params: {kty=null, x=riwTtQeRjmlDsR4PUQELhejpPkZkQstb0_Lf08qeBzM, y=izN8y6z-8j8bB_Lj10gX9mnaE_E0ZK5fl0hJVyLWMKA, crv=P-256} and the full JWKS content:

Bug#1057932: kgb-bot: FTBFS: Failed test 'Changes contains all valid release dates'


Package: src:kgb-bot
Version: 1.59-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
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
[ "1.59" = "1.59" ] \
|| ( echo "Package version (1.59) doesn't match module version (1.59)"; 
exit 1 )
dh_auto_configure
/usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wl,-z,relro"
Checking prerequisites...
  test_requires:
!  Test::Perl::Critic is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'App-KGB' version '1.59'
make[1]: Leaving directory '/<>'
   dh_auto_build
/usr/bin/perl Build
Building App-KGB
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LANG=bg_BG.utf8 LC_ALL=bg_BG.utf8 dh_auto_test
/usr/bin/perl Build test --verbose 1
t/00-compile.t 
ok 1 - blib/lib/App/KGB.pm compiles
ok 2 - blib/lib/App/KGB/API.pm compiles
ok 3 - blib/lib/App/KGB/Change.pm compiles
ok 4 - blib/lib/App/KGB/Client.pm compiles
ok 5 - blib/lib/App/KGB/Client/Fake.pm compiles
ok 6 - blib/lib/App/KGB/Client/Git.pm compiles
ok 7 - blib/lib/App/KGB/Client/RelayMsg.pm compiles
ok 8 - blib/lib/App/KGB/Client/ServerRef.pm compiles
ok 9 - blib/lib/App/KGB/Client/Subversion.pm compiles
ok 10 - blib/lib/App/KGB/Commit.pm compiles
ok 11 - blib/lib/App/KGB/Commit/Tag.pm compiles
ok 12 - blib/lib/App/KGB/Painter.pm compiles
ok 13 - blib/lib/JSON/RPC/Client/Any.pm compiles
ok 14 - blib/lib/WWW/Shorten/Debli.pm compiles
1..14
ok
t/00-compile_scripts.t 
1..2
ok 1 - blib/script/kgb-ci-report compiles
ok 2 - blib/script/kgb-client compiles
ok
t/00-compile_shell_scripts.t ..
ok 1
1..1
ok
t/30-bot-changes.t 
ok 1
ok 2
ok 3
1..3
ok
# trying port 5392
# port 5392 is available
# test bot listening on 127.0.0.1:5392, pid: 629908  at t/TestBot.pm line 133.
# Test bot started on 127.0.0.1:5392
# $>=924 $<=924 $ENV{USER}=buildd getpwuid($>)=buildd
# stopping test bot, pid 629908
# Removing directory /<>/t/bot
t/50-client.t .
Checked out revision 0.
A file
Adding file
Transmitting file data .done
Committing transaction...
Committed revision 1.
Sendingfile
Transmitting file data .done
Committing transaction...
Committed revision 2.
D file
A file
Replacing  file
Transmitting file data .done
Committing transaction...
Committed revision 3.
ok 1 - Test repository prepared
ok 2 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 25 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 26 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 27 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 28 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 29 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 30 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 31
1..31
ok
t/51-client_branch_module.t ...
ok 1 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 2 - branch detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 3 - module detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 4 - file list for [module and branch]
ok 5 - branch detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 6 - module detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 7 - file list for [branch and module]
ok 8 - branch detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 9 - module detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 10 - file list for [branch only]
ok 11 - branch detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 12 - module detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 13 - file list for [module only]
ok 14 - branch detection in [real example]

Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1


Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-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
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js

Tracing dependencies for: jstree

/<>/dist/jstree.js

/<>/src/jstree.js
/<>/src/jstree.changed.js
/<>/src/jstree.checkbox.js
/<>/src/jstree.conditionalselect.js
/<>/src/jstree.contextmenu.js
/<>/src/jstree.dnd.js
/<>/src/jstree.massload.js
/<>/src/jstree.search.js
/<>/src/jstree.sort.js
/<>/src/jstree.state.js
/<>/src/jstree.types.js
/<>/src/jstree.unique.js
/<>/src/jstree.wholerow.js
/<>/src/vakata-jstree.js

sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/libjs-jquery-jstree/
   dh_debputy
Internal error in debputy
  - 8<  BEGIN STACK TRACE  8< -
Traceback (most recent call last):
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 2082, in 
main
command.handler(cmd_context)
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 1133, in 
_dh_integration_generate_debs
intermediate_manifest = manifest.finalize_data_tar_contents(

  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 1177, in 
finalize_data_tar_contents
intermediate_manifest = list(
^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180, in 
_generate_intermediate_manifest
tar_member = _path_to_tar_member(path, clamp_mtime_to)
 ^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159, in 
_path_to_tar_member
return TarMember.from_file(
   
  File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line 147, in 
from_file
"debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
  - 8<  END STACK TRACE  8< -
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs -p 
libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057931: greetd: FTBFS: failed to select a version for the requirement `rpassword = "^6.0"`


Package: src:greetd
Version: 0.9.0-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --buildsystem=cargo
   dh_update_autotools_config -O--buildsystem=cargo
   dh_autoreconf -O--buildsystem=cargo
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po '^\S+') 
> debian/cargo-checksum.json;
make[1]: Leaving directory '/<>'
   dh_auto_configure -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] [] 
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# actually does the build
DEB_BUILD_OPTIONS= dh_auto_test -- --release
debian cargo wrapper: options, profiles, parallel, lto: [] [] [] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
error: failed to select a version for the requirement `rpassword = "^6.0"`
candidate versions found which didn't match: 7.2.0
location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `agreety v0.9.0 (/<>/agreety)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_test: error: /usr/share/cargo/bin/cargo build --release returned exit 
code 101
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057930: cunit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}


Package: src:cunit
Version: 2.1-3-dfsg-2.6
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 autoreconf
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
cp -an --reflink=auto config.guess 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669.tmp
mv 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669.tmp
 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669
cp -f /usr/share/misc/config.guess ./config.guess
cp -an --reflink=auto config.sub 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
mv 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39
cp -f /usr/share/misc/config.sub ./config.sub
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.in

[... snipped ...]

  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:29: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |   ~~^~
  | |
  | int
  505 |   width[0], _("#"),
  506 |   width[1], _("Suite Name"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:32: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 7 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |   ~^~
  ||
  |int
..
  507 |   width[2], _("Init?"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:35: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 9 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |  ~^~
  |   |
  |   int
..
  508 |   width[3], _("Cleanup?"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:38: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 11 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  | ~^~
  |  |
  |  int
..
  509 |   width[4], _("#Tests"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:41: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 13 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |~^~
  | |
  | int
..
  510 |   width[5], _("Active?"));
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:514:25: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 3 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  514 | fprintf(stdout, "\n%*d. %-*.*s%*s%*s%*u%*s",
  |~^~
  | |
  | int
  515 | width[0], i,
  | 
  |  |
  |  size_t {aka long unsigned int}
Console.c:514:31: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]

Bug#1057929: buildbot: FTBFS: locale.Error: unsupported locale setting


Package: src:buildbot
Version: 3.9.2-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 --with python3,bash-completion,sphinxdoc
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --configure -i python{version} -p 3.11 --dir master
I: pybuild base:310: python3.11 setup.py config
/<>/master/setup.py:27: 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/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running config
dh_auto_configure --buildsystem=pybuild --sourcedirectory=worker \
--package=buildbot-worker
pybuild --configure -i python{version} -p 3.11 --dir worker
I: pybuild base:310: python3.11 setup.py config
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running config
make[1]: Leaving directory '/<>'
rm -f debian/buildbot-worker.debhelper.log debian/buildbot.debhelper.log
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --build -i python{version} -p 3.11 --dir master
I: pybuild base:310: /usr/bin/python3 setup.py build
/<>/master/setup.py:27: 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/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/pbutil.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/asyncio.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/scheduler.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/warnings.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/errors.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildbot_net_usage_data.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/locks.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/revlinks.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildrequest.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/manhole.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/interfaces.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/master.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
creating /<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/janitor.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
creating /<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/local.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/docker.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/latent.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/marathon.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/kubernetes.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/base.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/openstack.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/libvirt.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/ec2.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/manager.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/upcloud.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
creating /<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/msgpack.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/null.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying

Bug#1057928: boinctui: FTBFS: invalid use of incomplete type ‘ITEM’ {aka ‘struct tagITEM’}


Package: src:boinctui
Version: 2.7.0-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
   dh_update_autotools_config
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.in
autoreconf -f -i
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoconf
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
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 special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for main in -lncursesw... yes
checking for main in -lformw... yes
checking for main in -lpanelw... yes
checking for main in -lmenuw... yes
checking for main in -lexpat... yes
checking for main in -lpthread... yes
checking for MD5_Init in -lgnutls-openssl ... 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 pthread.h... yes
checking for string.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for stdio.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdarg.h... yes
checking for sys/ioctl.h... yes
checking for arpa/inet.h... yes
checking for locale.h... yes
checking for malloc.h... yes
checking for sys/socket.h... yes
checking for netdb.h... yes
checking for signal.h... yes
checking for ctype.h... yes
checking for algorithm... yes
checking for string... yes
checking for list... yes
checking for vector... yes
checking for queue... yes
checking for stack... yes
checking for sstream... yes
checking for expat.h... yes
checking for gnutls/openssl.h... yes
checking for ncursesw/curses.h... yes
checking for ncursesw/form.h... yes
checking for ncursesw/panel.h... yes
checking for ncursesw/menu.h... yes
checking for _Bool... yes
checking for stdbool.h that conforms to C99... yes
checking for size_t... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether lstat correctly handles trailing slash... yes
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for mblen... yes
checking for memset... yes
checking for setlocale... yes
checking for socket... yes
checking for strdup... yes
checking for strstr... yes
configure: creating ./config.status
config.status: creating Makefile
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j2
make[1]: Entering directory '/<>'
create .obj
 
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -DENABLEMOUSE -DVERSION=2.7.0 -DPACKAGE_NAME=\"boinctui\" -DPACKAGE_TARNAME=\"boinctui\" -DPACKAGE_VERSION=\"VERSION\" -DPACKAGE_STRING=\"boinctui\ VERSION\" -DPACKAGE_BUGREPORT=\"BUG-REPORT-ADDRESS\" -DPACKAGE_URL=\"\" -DHAVE_LIBNCURSESW=1 -DHAVE_LIBFORMW=1 -DHAVE_LIBPANELW=1 -DHAVE_LIBMENUW=1 -DHAVE_LIBEXPAT=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBGNUTLS_OPENSSL_=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1

Bug#965489: marked as done (dictdlib: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sun, 10 Dec 2023 19:54:43 +0100
with message-id 

and subject line closing open bugs of Python2 package removed in 2020
has caused the Debian Bug report #965489,
regarding dictdlib: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dictdlib
Version: 2.0.4.1+nmu1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package dictdlib uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
done--- End Message ---

Bug#1057766: marked as done (Osk button missing after startup)

Your message dated Sun, 10 Dec 2023 18:51:57 +
with message-id 
and subject line Bug#1057766: fixed in phosh 0.34.0-2
has caused the Debian Bug report #1057766,
regarding Osk button missing after startup
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.)


-- 
1057766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phosh
Version: 0.34.0-1
Severity: grave

There's a regression in phosh 0.34.0 that prevents the button to
manually unfold the OSK after startup. Let's block testing migration
as this makes many apps unusable for some people.

Likely fixed via 
https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1332

 -- Guido



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  fonts-lato   2.015-1
ii  gnome-shell-common   44.5-2
ii  gsettings-desktop-schemas45.0-2
ii  libc62.37-12
ii  libcairo21.18.0-1
ii  libcallaudio-0-1 0.1.9-1
ii  libecal-2.0-23.50.1-1
ii  libedataserver-1.2-273.50.1-1
ii  libfeedback-0.0-00.2.1-1
ii  libfribidi0  1.0.13-3
ii  libgcr-base-3-1  3.41.1-3
ii  libgcr-ui-3-13.41.1-3
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
ii  libglib2.0-0 2.78.1-4
ii  libgnome-desktop-3-2044.0-2
ii  libgtk-3-0   3.24.38-6
ii  libgudev-1.0-0   238-3
ii  libhandy-1-0 1.8.2-3
ii  libical3 3.0.17-1
ii  libjson-glib-1.0-0   1.8.0-2
ii  libnm0   1.44.2-3
ii  libpam0g 1.5.2-9.1
ii  libpango-1.0-0   1.51.0+ds-3
ii  libpolkit-agent-1-0  123-3
ii  libpolkit-gobject-1-0123-3
ii  libpulse-mainloop-glib0  16.1+dfsg1-2+b1
ii  libpulse016.1+dfsg1-2+b1
ii  libsecret-1-00.21.1-1
ii  libsystemd0  254.5-1
ii  libupower-glib3  1.90.2-6
ii  libwayland-client0   1.22.0-2.1
ii  phoc 0.34.0~beta1+ds-2~exp1

Versions of packages phosh recommends:
ii  feedbackd  0.2.1-1
ii  gnome-session-bin  45.0-2
ii  gnome-session-common   45.0-2
ii  gnome-settings-daemon  45.0-1
ii  iio-sensor-proxy   3.5-1
ii  phosh-mobile-tweaks0.33.0-1
ii  phosh-osk-stub 0.34.0-1
ii  phosh-plugins  0.34.0-1
ii  slurp  1.4.0-1
ii  squeekboard1.22.0-5

phosh suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: phosh
Source-Version: 0.34.0-2
Done: Guido Günther 

We believe that the bug you reported is fixed in the latest version of
phosh, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated phosh 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

Bug#1055848: cfgrib failing to find eccodes


Control: retitle -1 cfgrib: test failure - can't find eccodes

Because we now enforce that build-depends of testing must be in testing, 
this bug is blocking python-xarray and hence pandas from testing, so is 
more important than this package's popcon would suggest.


I consider it likely that the real bug is in ecmwflibs, specifically 
this function, but haven't actually tested that:

https://sources.debian.org/src/ecmwflibs/2%3A0.5.7-1/ecmwflibs/__init__.py/#L118

Processed: Re: cfgrib failing to find eccodes

Processing control commands:

> retitle -1 cfgrib: test failure - can't find eccodes
Bug #1055848 [src:cfgrib] cfgrib: autopkgtest regression
Changed Bug title to 'cfgrib: test failure - can't find eccodes' from 'cfgrib: 
autopkgtest regression'.

-- 
1055848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

2023-12-10 Thread Aaron Rainbolt


On 12/10/23 12:08, Bas Wijnen wrote:

On Sun, Dec 03, 2023 at 02:18:38AM -0600, Aaron Rainbolt wrote:

[Catch 2]

While it is definitely possible to port the
openMSX tests to use catch2 v3, we will be departing from what
upstream supports, and that seems like it could lead to way more work
than necessary (for instance, what if the next major release of
openMSX still uses catch2 v2 and uses it in a way that's incompatible
with catch2 v3? Then we have to maintain that delta from upstream
ourselves, possibly for an extended period of time).

You are misunderstanding me. First of all, I was expecting the changes to be
minor. So I was thinking we can write a patch and let upstream use it. They are
very responsive, so I would expect them to include our patch immediately.

However, if it is a lot of work, it might be better to just file a bug report
upstream. I would expect them to respond to that as well, by doing it
themselves. Although it might take some time.

So because we are in a bit of a hurry with openMSX dropping from testing, I
think the approach for now is to use the bundled catch2-v2, and either port it
for them, or let them know it needs to be ported.


One possible solution might be for Debian to ship multiple major
versions of catch2.

I don't know enough about catch2 to know if that is a good idea. It might be,
but it's certainly out of the scope of this problem.


Maybe this is something we can bring up to whoever maintains catch2 in
Debian.

Yes, that sounds like a good idea. They will probably have an intelligent
opinion about it.


I'm not so sure it's a Lintian bug since HTML files oftentimes *are*
compiled from other source code.

They are, but Lintian is now very forceful in saying that files like these are
definitely compiled, which is just false. So if there is no better way to
detect this, at the very least the certainty of the problem should be decreased
(from error to warning, for example). It is quite common for hand-written text
files (including html files) to contain long lines and it is not reasonable for
all those files to either be required to be line-wrapped, nor for all those
packages to contain overrides.

I think that due to the urgency, I'll make a new package based on your work and
upload it. We can figure out how to handle the remaining issues after that.


Sounds good, and I'll see about a catch2 v3 port. (Part of the reason I 
was against that idea was because I actually tried to do it and it 
failed miserably. I didn't understand enough about how exactly the 
openMSX build system worked to do it "right" and the quick-and-dirty way 
of doing it was discouraged in the catch2 documentation.) I'll probably 
have to learn Perl before I can look into Lintian, but I've wanted to 
learn it before anyway, so may as well do so now.


Thanks you for all your help with this!


Thanks again,
Bas


--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

2023-12-10 Thread Bas Wijnen

On Sun, Dec 03, 2023 at 02:18:38AM -0600, Aaron Rainbolt wrote:
> > [Catch 2]
> While it is definitely possible to port the
> openMSX tests to use catch2 v3, we will be departing from what
> upstream supports, and that seems like it could lead to way more work
> than necessary (for instance, what if the next major release of
> openMSX still uses catch2 v2 and uses it in a way that's incompatible
> with catch2 v3? Then we have to maintain that delta from upstream
> ourselves, possibly for an extended period of time).

You are misunderstanding me. First of all, I was expecting the changes to be
minor. So I was thinking we can write a patch and let upstream use it. They are
very responsive, so I would expect them to include our patch immediately.

However, if it is a lot of work, it might be better to just file a bug report
upstream. I would expect them to respond to that as well, by doing it
themselves. Although it might take some time.

So because we are in a bit of a hurry with openMSX dropping from testing, I
think the approach for now is to use the bundled catch2-v2, and either port it
for them, or let them know it needs to be ported.

> One possible solution might be for Debian to ship multiple major
> versions of catch2.

I don't know enough about catch2 to know if that is a good idea. It might be,
but it's certainly out of the scope of this problem.

> Maybe this is something we can bring up to whoever maintains catch2 in
> Debian.

Yes, that sounds like a good idea. They will probably have an intelligent
opinion about it.

> I'm not so sure it's a Lintian bug since HTML files oftentimes *are*
> compiled from other source code.

They are, but Lintian is now very forceful in saying that files like these are
definitely compiled, which is just false. So if there is no better way to
detect this, at the very least the certainty of the problem should be decreased
(from error to warning, for example). It is quite common for hand-written text
files (including html files) to contain long lines and it is not reasonable for
all those files to either be required to be line-wrapped, nor for all those
packages to contain overrides.

I think that due to the urgency, I'll make a new package based on your work and
upload it. We can figure out how to handle the remaining issues after that.

Thanks again,
Bas

signature.asc
Description: PGP signature

Processed: Bug#1057766 marked as pending in phosh

Processing control commands:

> tag -1 pending
Bug #1057766 [phosh] Osk button missing after startup
Ignoring request to alter tags of bug #1057766 to the same tags previously set

-- 
1057766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057766: marked as pending in phosh

2023-12-10 Thread Guido Günther

Control: tag -1 pending

Hello,

Bug #1057766 in phosh reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/DebianOnMobile-team/phosh/-/commit/de6aa7ac1e26b9eea7e779f1b43ff76de0ccdcac


osk-manager: Sync initial state

Closes: #1057766
Thanks: Jarrah Gosbell for testing


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057766

Bug#1057921: offlineimap: NameError: name 'fcntl' is not defined

2023-12-10 Thread Sebastian Ramacher

Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20231201.77e70ed+dfsg-1
Severity: grave
X-Debbugs-Cc: sramac...@debian.org

offlineimap no longer works after the last upgrade due to a missing
import.

$ offlineimap -a mailhost
OfflineIMAP 8.0.0
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v3.05, Python v3.11.7, OpenSSL 3.1.4 24 Oct 2023
*** Processing account mailhost
Establishing connection to tunnel:ssh -i /home/sebastian/.ssh/offlineimap -C -q 
mailhost -S none '/usr/bin/imapd ./Maildir' (mailhost_imap)
ERROR: While attempting to sync account 'mailhost'
  name 'fcntl' is not defined
*** Finished account 'mailhost' in 0:00
ERROR: Exceptions occurred during the run!
ERROR: While attempting to sync account 'mailhost'
  NameError: name 'fcntl' is not defined


Traceback:
  File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in 
syncrunner
self.__sync()
  File "/usr/share/offlineimap3/offlineimap/accounts.py", line 375, in __sync
remoterepos.getfolders()
  File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 698, in 
getfolders
imapobj = self.imapserver.acquireconnection()
  ^^^
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 552, in 
acquireconnection
imapobj = imaplibutil.IMAP4_Tunnel(
  ^
  File "/usr/share/offlineimap3/offlineimap/imaplibutil.py", line 133, in 
__init__
IMAP4.__init__(self, tunnelcmd, **kwargs)
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 336, in __init__
self.open(host, port)
  File "/usr/share/offlineimap3/offlineimap/imaplibutil.py", line 145, in open
self.set_nonblocking(self.read_fd)
  File "/usr/share/offlineimap3/offlineimap/imaplibutil.py", line 151, in 
set_nonblocking
fl = fcntl.fcntl(fd, fcntl.F_GETFL)
 ^

Cheers

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), 
(600, 'experimental-debug'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages offlineimap depends on:
ii  offlineimap3  0.0~git20231201.77e70ed+dfsg-1

offlineimap recommends no packages.

offlineimap suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher

Bug#1054739: marked as done (cbflib: FTBFS: chmod: cannot access '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfcb.so': No such file or directory)

Your message dated Sun, 10 Dec 2023 19:34:31 +0200
with message-id 
and subject line cbflib: FTBFS: chmod: cannot access '/<>...
has caused the Debian Bug report #1054739,
regarding cbflib: FTBFS: chmod: cannot access 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfcb.so': 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.)


-- 
1054739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cbflib
Version: 0.9.7+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p /<>/bin
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -Wall -D_USE_XOPEN_EXTENDED 
> -fno-strict-aliasing   -Wl,-z,relro -Wl,-z,now   -DCBF_REGEXLIB_REGEX 
> -I/<>/include -I/<>/src -I/usr/include/hdf5/serial  
>  \
> /<>/examples/cif2c.c -L/<>/lib \
> -lcbf   -lm -L/usr/lib/x86_64-linux-gnu/hdf5/serial -lhdf5  -o 
> /<>/bin/cif2c
> mkdir -p /<>/bin
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -Wall -D_USE_XOPEN_EXTENDED 
> -fno-strict-aliasing   -Wl,-z,relro -Wl,-z,now   -DCBF_REGEXLIB_REGEX 
> -I/<>/include -I/<>/src -I/usr/include/hdf5/serial  
>  \
> /<>/examples/testcell.C -L/<>/lib \
> -lcbf   -lm -L/usr/lib/x86_64-linux-gnu/hdf5/serial -lhdf5  -o 
> /<>/bin/testcell
> mkdir -p /<>/debian/tmp/usr
> mkdir -p /<>/debian/tmp/usr/lib/x86_64-linux-gnu
> mkdir -p /<>/debian/tmp/usr/bin
> mkdir -p /<>/debian/tmp/usr/include
> mkdir -p /<>/debian/tmp/usr/include/cbflib
> chmod 755 /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.a
> chmod: cannot access 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.a': No such file 
> or directory
> make[2]: [Makefile:1235: baseinstall] Error 1 (ignored)
> cp /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.a 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf_old.a
> cp: cannot stat 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.a': No such file 
> or directory
> make[2]: [Makefile:1236: baseinstall] Error 1 (ignored)
> cp /<>/lib/libcbf.a 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.a
> cp /<>/solib/libcbf.so 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.so.1.0.0
> ln -s -f -r 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.so.1.0.0 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.so.1
> ln -s -f -r 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.so.1.0.0 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcbf.so
> cp /<>/debian/tmp/usr/bin/cbflib.ini 
> /<>/debian/tmp/usr/bin/cbflib.ini_old
> cp: cannot stat '/<>/debian/tmp/usr/bin/cbflib.ini': No such 
> file or directory
> make[2]: [Makefile:1241: baseinstall] Error 1 (ignored)
> echo  
> "LD_LIBRARY_PATH=/<>/debian/tmp/usr/LIB:/<>/lib:$LD_LIBRARY_PATH;export
>  LD_LIBRARY_PATH;" > /<>/debian/tmp/usr/bin/cbflib.ini
> echo  
> "HDF5_PLUGIN_PATH=/<>/debian/tmp/usr/lib:$HDF5_PLUGIN_PATH" >> 
> /<>/debian/tmp/usr/bin/cbflib.ini
> echo  "export HDF5_PLUGIN_PATH" >> 
> /<>/debian/tmp/usr/bin/cbflib.ini
> cp /<>/debian/tmp/usr/bin/adscimg2cbf 
> /<>/debian/tmp/usr/bin/adscimg2cbf_old
> cp: cannot stat '/<>/debian/tmp/usr/bin/adscimg2cbf': No such 
> file or directory
> make[2]: [Makefile:1245: baseinstall] Error 1 (ignored)
> cp /<>/bin/adscimg2cbf 
> /<>/debian/tmp/usr/bin/adscimg2cbf
> cp /<>/debian/tmp/usr/bin/cbf2adscimg 
> /<>/debian/tmp/usr/bin/cbf2adscimg_old
> cp: cannot stat '/<>/debian/tmp/usr/bin/cbf2adscimg': No such 
> file or directory
> make[2]: [Makefile:1247: baseinstall] Error 1 (ignored)
> cp /<>/bin/cbf2adscimg 
> /<>/debian/tmp/usr/bin/cbf2adscimg
> cp /<>/debian/tmp/usr/bin/cbf_standardize_numbers \
>   /<>/debian/tmp/usr/bin/cbf_standardize_numbers_old
> cp: cannot stat 
> '/<>/debian/tmp/usr/bin/cbf_standardize_numbers': No such file 
> or directory
> make[2]: [Makefile:1249: baseinstall] Error 1 (ignored)
> cp /<>/bin/cbf_standardize_numbers 
> /<>/debian/tmp/usr/bin/cbf_standardize_numbers
> cp /<>/debian/tmp/usr/bin/convert_image 
> /<>/debian/tmp/usr/bin/convert_image_old
> cp: cannot stat '/<>/debian/tmp/usr/bin/convert_image': No such 
> file or directory
> make[2]: [Makefile:1251: baseinstall] Error 1 (ignored)
> cp

Processed: 1056431

Processing commands for cont...@bugs.debian.org:

> forwarded 1056431 https://github.com/numpy/numpydoc/issues/512
Bug #1056431 [src:numpydoc] numpydoc's autopkg tests fail with Python 3.12
Set Bug forwarded-to-address to 'https://github.com/numpy/numpydoc/issues/512'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1056431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055847: python-sparse crash on arm64 (and possibly other non-x86)

At least on arm64, this appears to be a crash in a @numba.jit function. 
Given numba's known issues on non-x86 (e.g. #1033907), this suggests 
that actually fixing it _may_ not be reasonable.


In pandas I don't recommend/build/test-depend on numba on the problem 
architectures, but python-sparse has a hard Depends on numba so that 
doesn't appear to be an option here.


A potential option is to disable the tests on these architectures and 
display a warning on import (for an example, see 
https://salsa.debian.org/science-team/statsmodels/-/commit/a64430166b1e48135c58ec41330e3ce9b2206b46 
).

Processed: Re: python-sparse in Python 3.12

Processing control commands:

> tags -1 fixed-upstream
Bug #1056504 [src:python-sparse] python-sparse's autopkg tests fail with Python 
3.12
Added tag(s) fixed-upstream.

-- 
1056504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056504: python-sparse in Python 3.12


Control: tags -1 fixed-upstream

This was fixed upstream by 
https://github.com/pydata/sparse/commit/266af7307b5232a37daa1d7659f02faf6a42e46e 
.  It still exists here because 
debian/patches/fix-test-fails-on-i386.patch effectively reverses that 
fix, possibly by accident.

Bug#1057843: linux-image-6.1.0-13-amd64: Workaround

2023-12-10 Thread Sebastian Niehaus

Package: src:linux
Followup-For: Bug #1057843




FYI: there is a nice workaround to avoid upgrading to the affected kernel:
https://octodon.social/@alienghic/111554146479489358

===[ snip ]

This should block just the buggy kernel. Which might help with unattended 
upgrades problem or just being forgetful. It might even uninstall the 
buggy kernel, though I didn't test that. And it shouldn't impact upgrading 
to 6.1.66 when it's available.

create a file:

/etc/apt/preferences.d/buggy-kernel

with the contents:
# avoid kernel with ext4 bug 
# 1057843
Package: linux-image-*
Pin: version 6.1.64-1
Pin-Priority: -1

(the comment isn't required but is helpful for remembering why this file 
is around in 6 months.)

===[ snip ]

Processed: found 1057914 in 5.55-3.1, found 1057914 in 5.66-1

Processing commands for cont...@bugs.debian.org:

> found 1057914 5.55-3.1
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Marked as found in versions bluez/5.55-3.1.
> found 1057914 5.66-1
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Marked as found in versions bluez/5.66-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057914: bluez: CVE-2023-45866

2023-12-10 Thread Salvatore Bonaccorso

Source: bluez
Version: 5.70-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for bluez.

CVE-2023-45866[0]:
| Bluetooth HID Hosts in BlueZ may permit an unauthenticated
| Peripheral role HID Device to initiate and establish an encrypted
| connection, and accept HID keyboard reports, potentially permitting
| injection of HID messages when no user interaction has occurred in
| the Central role to authorize such access. An example affected
| package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some
| cases, a CVE-2020-0556 mitigation would have already addressed this
| Bluetooth HID Hosts issue.


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-45866
https://www.cve.org/CVERecord?id=CVE-2023-45866
[1] 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=25a471a83e02e1effb15d5a488b3f0085eaeb675

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1042605: marked as done (terminaltables: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

Your message dated Sun, 10 Dec 2023 16:01:09 +
with message-id 
and subject line Bug#1042605: fixed in terminaltables 3.1.10-3
has caused the Debian Bug report #1042605,
regarding terminaltables: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not 
all arguments converted during string formatting
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.)


-- 
1042605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terminaltables
Version: 3.1.10-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

terminaltables fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. /usr/share/sphinx/scripts/python3/sphinx-build -N -q -E -b html 
> docs/ 
> debian/python-terminaltables-doc/usr/share/doc/python-terminaltables-doc/html/
> /<>/docs/changelog.rst:3: CRITICAL: Problems with "include" 
> directive path:
> InputError: [Errno 2] No such file or directory: 'README.rst'.
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-ofs01ccr.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/terminaltables_3.1.10-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: terminaltables
Source-Version: 3.1.10-3
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
terminaltables, 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 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
terminaltables package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 16:18:44 +0100
Source: terminaltables
Architecture: source
Version: 3.1.10-3
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1042605
Changes:
 terminaltables (3.1.10-3) sid; urgency=medium
 .
   * Uploading to sid.
   * Building documentation for the time being without sphinx extlinks
 extensions to fix

Bug#1000015: mp4h: depends on obsolete pcre3 library

2023-12-10 Thread Yavor Doganov

Control: tags -1 + patch

Please find attached a patch.
>From 4ead19b22c1564097192c50e2ec42c07351ef8de Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Sun, 10 Dec 2023 17:12:31 +0200
Subject: [PATCH] Port to PCRE2 (#115)

---
 debian/changelog   |   7 +
 debian/control |   2 +-
 debian/patches/pcre2.patch | 449 +
 debian/patches/series  |   1 +
 4 files changed, 458 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/pcre2.patch

diff --git a/debian/changelog b/debian/changelog
index b8143c6..018 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mp4h (1.3.1-18) UNRELEASED; urgency=medium
+
+  * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #115).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov   Sun, 10 Dec 2023 17:11:18 +0200
+
 mp4h (1.3.1-17) unstable; urgency=medium
 
   [ Axel Beckert ]
diff --git a/debian/control b/debian/control
index 4ee9a51..4630c13 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Build-Depends: autoconf (>= 2.57~),
fakeroot,
gettext,
libltdl-dev,
-   libpcre3-dev,
+   libpcre2-dev,
libtool,
tidy
 Build-Conflicts: autoconf2.13,
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..15a5857
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,449 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/115
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-10
+---
+
+--- mp4h.orig/src/Makefile.am
 mp4h/src/Makefile.am
+@@ -17,7 +17,7 @@
+ if LOADABLE_MODULES
+ mp4h_LDFLAGS = -export-dynamic
+ endif
+-mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a -lpcre @LIBINTL@ 
$(MODULE_LDADD)
++mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a -lpcre2-8 @LIBINTL@ 
$(MODULE_LDADD)
+ 
+ include_HEADERS = mp4h.h
+ noinst_HEADERS  = builtin.h
+--- mp4h.orig/src/builtin.c
 mp4h/src/builtin.c
+@@ -373,7 +373,7 @@
+ static char * utf8char_skip __P ((char *, int));
+ static int utf8char_strlen __P ((char *));
+ static int encoding_strlen __P ((char *));
+-static void substitute __P ((struct obstack *, const char *, const char *, 
int *));
++static void substitute __P ((struct obstack *, const char *, const char *, 
size_t *));
+ static void string_regexp __P ((struct obstack *, int, token_data **, int, 
const char *));
+ static void subst_in_string __P ((struct obstack *, int, token_data **, int));
+ static void generic_variable_lookup __P ((MP4H_BUILTIN_PROTO, boolean));
+@@ -382,6 +382,8 @@
+ static int array_member __P ((const char *, symbol *, boolean));
+ static int sort_function __P ((const void *, const void *));
+ static void logical_to_physical_paths __P ((char **));
++static void * pcre_malloc (size_t, void *);
++static void pcre_free (void *, void *);
+ 
+ /*  This symbol controls breakings of flow statements.  */
+ static symbol varbreak;
+@@ -398,7 +400,12 @@
+ struct lconv *my_locale;
+ 
+ /*  Table of characters used by PCRE with non-C locales  */
+-static const unsigned char *re_tableptr = NULL;
++static const uint8_t *re_tableptr = NULL;
++
++/*  PCRE contexts needed for custom memory management and adding
++non-builtin character tables.  */
++static pcre2_general_context *gen_ctxt;
++static pcre2_compile_context *comp_ctxt;
+ 
+ /*  Timer  */
+ static struct tms elapsed_time;
+@@ -662,12 +669,22 @@
+ | Initialise all builtin and predefined macros.  |
+ `---*/
+ 
++static void *
++pcre_malloc (size_t size, void *ptr)
++{
++  return xmalloc (size);
++}
++
++static void
++pcre_free (void *ptr, void *tag)
++{
++  xfree (ptr);
++}
++
+ void
+ builtin_init (void)
+ {
+   install_builtin_table (builtin_tab);
+-  pcre_malloc = xmalloc;
+-  pcre_free   = xfree;
+ }
+ 
+ /*---.
+@@ -688,18 +705,22 @@
+   varstack_check ();
+ }
+ 
+-static pcre *
++static pcre2_code *
+ xre_compile (const char *pattern, int cflags)
+ {
+-  pcre *patcomp;
+-  const char *errbuf;
+-  int erroffset;
++  pcre2_code *patcomp;
++  PCRE2_UCHAR errbuf[120];
++  int errcode;
++  size_t erroffset;
+ 
+   if (document_encoding == ENCODING_UTF8)
+-  cflags |= PCRE_UTF8;
+-  patcomp = pcre_compile (pattern, cflags, , , re_tableptr);
++  cflags |= PCRE2_UTF;
++  pcre2_set_character_tables (comp_ctxt, re_tableptr);
++  patcomp = pcre2_compile ((PCRE2_SPTR) pattern, PCRE2_ZERO_TERMINATED,
++   cflags, , , comp_ctxt);
+   if (patcomp == 0)
+ {
++  pcre2_get_error_message (errcode, errbuf, sizeof (errbuf));
+   MP4HERROR ((warning_status, 0,
+ _("Warning:%s:%d: Bad regular expression `%s' at position %d: %s"),
+  CURRENT_FILE_LINE, pattern, erroffset, errbuf));
+@@ -822,11 +843,10 @@
+   register char

Processed: Re: Bug#1000015: mp4h: depends on obsolete pcre3 library

Processing control commands:

> tags -1 + patch
Bug #115 [src:mp4h] mp4h: depends on obsolete pcre3 library
Added tag(s) patch.

-- 
115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1056460 is forwarded to https://github.com/MatthieuDartiailh/bytecode/issues/135

Processing commands for cont...@bugs.debian.org:

> forwarded 1056460 https://github.com/MatthieuDartiailh/bytecode/issues/135
Bug #1056460 [src:python-bytecode] python-bytecode's autopkg tests fail with 
Python 3.12 (armhf)
Set Bug forwarded-to-address to 
'https://github.com/MatthieuDartiailh/bytecode/issues/135'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1056460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031414: Proposed RM: libgpuarray - abandoned, RC-buggy

libgpuarray has been de facto abandoned upstream since 2018, and is 
currently unused in Debian.  (Its original user was theano, which was 
removed in #1042574.)


It currently has what may or may not be a wrong-answer bug (#1031414), 
and two broken-by-transition bugs.  (The latter two _might_ be easy to 
fix - I haven't tried because I've already mostly given up on it.)


Hence, I intend to request removal.

Bug#1057730: marked as done (python-jellyfish ftbfs in unstable (dpkg-buildpackage -B))

Your message dated Sun, 10 Dec 2023 14:41:00 +
with message-id 
and subject line Bug#1057730: fixed in python-jellyfish 0.10.0-3
has caused the Debian Bug report #1057730,
regarding python-jellyfish ftbfs in unstable (dpkg-buildpackage -B)
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.)


-- 
1057730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-jellyfish
Version: 0.10.0-2
Severity: serious
Tags: sid trixie

python-jellyfish ftbfs in unstable


[...]
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
dh_installdocs -ppython-jellyfish-doc --doc-main-package=python3-jellyfish
dh_installdocs: warning: All requested packages have been excluded (e.g. 
via a Build-Profile or due to architecture restrictions).

dh_installdocs --remaining-packages
mv debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/site 
debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/html
mv: cannot stat 
'debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/site': No 
such file or directory

make[1]: *** [debian/rules:28: override_dh_installdocs] Error 1
--- End Message ---
--- Begin Message ---
Source: python-jellyfish
Source-Version: 0.10.0-3
Done: Julian Gilbey 

We believe that the bug you reported is fixed in the latest version of
python-jellyfish, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated python-jellyfish 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: Sun, 10 Dec 2023 14:14:24 +
Source: python-jellyfish
Architecture: source
Version: 0.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1014932 1057730
Changes:
 python-jellyfish (0.10.0-3) unstable; urgency=medium
 .
   * Fix binary-only build (closes: #1057730)
   * The 0.10.0 version also fixes the deprecated 'u' format
 (closes: #1014932)
Checksums-Sha1:
 ff4b9dbd03279eb57b1f67c2f910215121140130 2327 python-jellyfish_0.10.0-3.dsc
 06b0d2ece60014341eac3cb480a5260ce854ab4a 4592 
python-jellyfish_0.10.0-3.debian.tar.xz
 f714517634704e3250ef872ff57fe9b36a32e846 9390 
python-jellyfish_0.10.0-3_amd64.buildinfo
Checksums-Sha256:
 768589c2862a4201ca5eaf86a8bb40f1a918b6d2d463895f2d1e1a19136db959 2327 
python-jellyfish_0.10.0-3.dsc
 a1beac294e0ef21a766cd0ae9b67bbc08373edcaf9758c817c9d8c93cdca 4592 
python-jellyfish_0.10.0-3.debian.tar.xz
 56cd6f1634cc16ec00301e32ff6a44eba860168707dcb42637d95720f877c4b5 9390 
python-jellyfish_0.10.0-3_amd64.buildinfo
Files:
 e8e3def49764787a2a64b4de04f299ca 2327 python optional 
python-jellyfish_0.10.0-3.dsc
 36009dad02c675ae2da648df65f995d5 4592 python optional 
python-jellyfish_0.10.0-3.debian.tar.xz
 413538298d603d2b87b527af8d542f7b 9390 python optional 
python-jellyfish_0.10.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmV1yGIPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+NaAQAKXZkLX4kNl1dzs/8PGaRF3pI04B6dfE0aCp
J8FKRZ0uDQ5cenrnqKBWb7oHWUpMJJiQke2gxaEj+/pka4zVcLbv6hto/p0xGn39
sJvjbQVTzWE5F/DriZaHaUioHX1C2U2dBhD/9iehBST74fRgk2OIgzzVtPj+xg7r
+kr8lAgMvVzK6xBf5urGrN+kt5lPHZwMY5FzFn+PUGU15My/4qvQtSFqeaX3hBRG
d0j6rYOZ8WKgQaaGgNA8HlWKAhIRkk1xyHL+bPFkCSZYincvqrAzL/zelxWq9Gtb
jY7KCxS3MUWdZ6/4dBAoZs16MwQdznJdcMJhBU2b/POjlR63Q0SsgAS2S7Yrd619
JSPKs9DFToPmMcAZTlRvKxUZy0Q45DwvkZFzuJoaskWgnIdF46Jh/aFVXtKNIwMn
UAykgyCg6uTWkbjLib7VVRR3qCJAiDX+b5O3gbwMNzYJxoqZFlW/j8h1b88llTrr
8YIZaOIFqyU3OR/OVAb0Wm+/XFYMj4S8qXZ1qQu3yWSBjdlMegLUsSH5gxvaVvGB
D93X6KefQTJyopWWsQtUYm0ronpUbYJqCgaD0QXX5OomhLaci7QECKZr9fiIlNce
CGfswTx912M9/5AGblchQzxYSXrLxRVCMkunCzHwKTBXK8VeQ5YNwzIqUvXoxOKq
bF1NCeDr
=Wf06
-END PGP SIGNATURE End Message ---

Processed: libc++abi-18-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a

Processing control commands:

> affects -1 + libc++-17-dev
Bug #1057899 [libc++abi-18-dev] libc++abi-18-dev has an undeclared file 
conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a
Added indication that 1057899 affects libc++-17-dev

-- 
1057899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057899: libc++abi-18-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a

2023-12-10 Thread Helmut Grohne

Package: libc++abi-18-dev
Version: 1:18~++20231203063627+9f78edbd20ed-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libc++-17-dev

libc++abi-18-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/libc++experimental.a is contained in
the packages
 * libc++-17-dev/1:17.0.6-2 as present in unstable
 * libc++abi-18-dev/1:18~++20231203063627+9f78edbd20ed-1~exp1 as present in 
experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1055049: libtakari-polyglot-groovy-java: missing Breaks+Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)

2023-12-10 Thread Jérôme Charaoui

Le 2023-12-09 à 17 h 29, tony mancill a écrit :

On Sat, Dec 09, 2023 at 04:39:35PM -0500, Jérôme Charaoui wrote:

On Mon, 30 Oct 2023 09:37:34 +0100 Andreas Beckmann wrote:

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

From the attached log (scroll to the bottom...):

Preparing to unpack .../libtakari-polyglot-groovy-java_0.4.11-2_all.deb ...
Unpacking libtakari-polyglot-groovy-java (0.4.11-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libtakari-polyglot-groovy-java_0.4.11-2_all.deb
(--unpack):
trying to overwrite '/usr/share/java/polyglot-groovy-0.4.11.jar', which is
also in package libtakari-polyglot-maven-java 0.4.11-1
Errors were encountered while processing:
/var/cache/apt/archives/libtakari-polyglot-groovy-java_0.4.11-2_all.deb

Thanks for the heads up.

I'm not sure what's happening here: polyglot-groovy-0.4.11.jar was indeed
split away from "libtakari-polyglot-maven-java" and into
"libtakari-polyglot-groovy-java", however the new version of
"libtakari-polyglot-maven-java" does *not* depend on/recommend
"libtakari-polyglot-groovy-java".

So I'm unsure why "libtakari-polyglot-groovy-java" is being installed in the
first place, during the piuparts upgrade. It's not present in testing, and
it has currently zero reverse-dependencies.

I did my own testing and on a bare system with
"libtakari-polyglot-maven-java" installed, upgrading to sid does not include
an installation of "libtakari-polyglot-groovy-java".

Any idea what's going on?

Hi Jérôme,

I believe you're correct that in the normal upgrade case, this is
unlikely to occur. Here's the test case I ran instead a clean trixie
chroot:

1. Install libtakari-polyglot-maven-java (0.4.11-1)
2. Update sources.list to unstable and then apt-get update
3. apt-get -y install libtakari-polyglot-groovy-java

Step (3) will upgrade libtakari-polyglot-maven-java to 0.4.11-2 *before*
installing libtakari-polyglot-groovy-java, so there's no problem.

However, the issue can occur when using dpkg directly, or some other
factor influences the ordering such that libtakari-polyglot-groovy-java
is installed *before* libtakari-polyglot-maven-java is upgraded.

For example:

1. Install libtakari-polyglot-maven-java (0.4.11-1)
2. wget
http://ftp.us.debian.org/debian/pool/main/t/takari-polyglot-maven/libtakari-polyglot-groovy-java_0.4.11-2_all.deb
3. dpkg -i libtakari-polyglot-groovy-java_0.4.11-2_all.deb

Preparing to unpack libtakari-polyglot-groovy-java_0.4.11-2_all.deb ...
Unpacking libtakari-polyglot-groovy-java (0.4.11-2) ...
dpkg: error processing archive libtakari-polyglot-groovy-java_0.4.11-2_all.deb
(--install):
trying to overwrite '/usr/share/java/polyglot-groovy-0.4.11.jar', which is
also in package libtakari-polyglot-maven-java 0.4.11-1
Errors were encountered while processing:
libtakari-polyglot-groovy-java_0.4.11-2_all.deb

This is the reason that the relationship needs to be explicit.

I'm not 100% certain, but perhaps we can get away with only adding a
versioned depends on libtakari-polyglot-maven-java (>= 0.4.11-2) to the
libtakari-polyglot-groovy-java package. The problem as I see it is that
the current unversioned Depends can be satisfied by any version of
libtakari-polyglot-maven-java, including older versions with the file
conflict. Requiring the newer libtakari-polyglot-maven-java would
prevent this.

Ok what I think I'll do is to add: "Breaks:
libtakari-polyglot-maven-java (<< 0.4.11-2)" to
libtakari-polyglot-groovy-java. I think that's more explicit than a
versioned depends, and should prevent any instances of users
accidentally having wrong versions of the two packages.

-- Jérôme

Processed: Bug#1057730 marked as pending in python-jellyfish

Processing control commands:

> tag -1 pending
Bug #1057730 [src:python-jellyfish] python-jellyfish ftbfs in unstable 
(dpkg-buildpackage -B)
Added tag(s) pending.

-- 
1057730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057730: marked as pending in python-jellyfish

2023-12-10 Thread Julian Gilbey

Control: tag -1 pending

Hello,

Bug #1057730 in python-jellyfish reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-jellyfish/-/commit/10d200089b11f984a1de60b5185e5d37f679d721


Fix binary-only build (closes: #1057730)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057730

Processed: closing 1055561

Processing commands for cont...@bugs.debian.org:

> close 1055561 5.0.1-1
Bug #1055561 [src:pyodbc] pyodbc ftbfs with Python 3.12
Marked as fixed in versions pyodbc/5.0.1-1.
Bug #1055561 [src:pyodbc] pyodbc ftbfs with Python 3.12
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057412: marked as done (pynormaliz: FTBFS in testing and unstable)

Your message dated Sun, 10 Dec 2023 21:56:51 +0800
with message-id 

and subject line close 1057405
has caused the Debian Bug report #1057405,
regarding pynormaliz: FTBFS in testing and 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.)


-- 
1057405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pynormaliz
Version: 2.18+ds-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds [1], pynormaliz currently FTBFS
in testing and unstable.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/pynormaliz.html


dh execute_after_dh_auto_build --buildsystem=pybuild
make[1]: Leaving directory '/build/reproducible-path/pynormaliz-2.18+ds'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:310: cd
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH=/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build
python3.11 tests/runtests.py
Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit
code=1: cd 
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH={build_dir} {interpreter} tests/runtests.py
dh_auto_test: error: pybuild --test -i python{version} -p 3.11
returned exit code 13
make: *** [debian/rules:9: binary] Error 25
--- End Message ---
--- Begin Message ---
Version: 2.18+ds-1
Tag: fixed

Rebuild it with a new upload of normaliz[0] which was rebuilt with
nauty 2.8.8 is okay.

[0]: 
https://tracker.debian.org/news/1484284/accepted-normaliz-3101ds-3-source-into-unstable/--- End Message ---

Bug#1057405: marked as done (pynormaliz ftbfs with Python 3.12)

Your message dated Sun, 10 Dec 2023 21:56:51 +0800
with message-id 

and subject line close 1057405
has caused the Debian Bug report #1057405,
regarding pynormaliz ftbfs with 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.)


-- 
1057405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pynormaliz
Version: 2.18+ds-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pynormaliz ftbfs with Python 3.12:


[...]
dh execute_after_dh_auto_build --buildsystem=pybuild
make[1]: Leaving directory '/<>'
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build; 
PYTHONPATH=/<>/.pybuild/cpython3_3.12/build python3.12 
tests/runtests.py

Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.12/build; PYTHONPATH={build_dir} 
{interpreter} tests/runtests.py
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11/build; 
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build python3.11 
tests/runtests.py

Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.11/build; PYTHONPATH={build_dir} 
{interpreter} tests/runtests.py
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
returned exit code 13

make: *** [debian/rules:9: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Version: 2.18+ds-1
Tag: fixed

Rebuild it with a new upload of normaliz[0] which was rebuilt with
nauty 2.8.8 is okay.

[0]: 
https://tracker.debian.org/news/1484284/accepted-normaliz-3101ds-3-source-into-unstable/--- End Message ---

Bug#1057889: marked as done (graphviz_10.0.0~git231209-1_riscv64-buildd.changes REJECTED)

Your message dated Sun, 10 Dec 2023 13:05:01 +
with message-id 
and subject line Bug#1057889: fixed in graphviz 10.0.0~git231210-1
has caused the Debian Bug report #1057889,
regarding graphviz_10.0.0~git231209-1_riscv64-buildd.changes REJECTED
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.)


-- 
1057889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphviz
Version: 10.0.0~git231209-1
Severity: serious

On 2023-12-10 07:05, Debian FTP Masters wrote:
> graphviz-tools_10.0.0~git231209-1_riscv64.deb: has 1 file(s) with a timestamp=
>  too far in the past:
>   usr/share/doc/graphviz-tools/copyright (Thu Jan  1 00:01:00 1970)
> 
> 
> 
> =3D=3D=3D
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
--- End Message ---
--- Begin Message ---
Source: graphviz
Source-Version: 10.0.0~git231210-1
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
graphviz, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated graphviz 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 13:10:49 +0100
Source: graphviz
Architecture: source
Version: 10.0.0~git231210-1
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1057889
Changes:
 graphviz (10.0.0~git231210-1) experimental; urgency=medium
 .
   * New major upstream release candidate version.
   * Re-set correct time on debian/* files (closes: #1057889).
Checksums-Sha1:
 b780fc4185f22fc8d9607e4717116ce2773a3ce6 5285 graphviz_10.0.0~git231210-1.dsc
 6912f0dac12fff54cb3c93129eb31ac44e44ad34 23754040 
graphviz_10.0.0~git231210.orig.tar.xz
 1da8ce4a281521590afe95d90dc6a40015d805be 40312 
graphviz_10.0.0~git231210-1.debian.tar.xz
Checksums-Sha256:
 15d7afa494053c05eda6d85f7056e105473fb888ba08028d456c1f50716fc0ec 5285 
graphviz_10.0.0~git231210-1.dsc
 8cb709b8c91523348a4c15846f8f82c2d0bd31a927020cd1b1c3303c233fa2aa 23754040 
graphviz_10.0.0~git231210.orig.tar.xz
 256c1c9a8e6b91518e79f35af20157f792a807b4a2ae77198f3168289ddd3577 40312 
graphviz_10.0.0~git231210-1.debian.tar.xz
Files:
 2ed42c4881e57ef86f6c249f367bbb32 5285 graphics optional 
graphviz_10.0.0~git231210-1.dsc
 2defa616bcfba9c6e4d8d60a641d1961 23754040 graphics optional 
graphviz_10.0.0~git231210.orig.tar.xz
 0f80cfcb0c793d01b22e7c22d30a9a79 40312 graphics optional 
graphviz_10.0.0~git231210-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmV1sj0ACgkQ3OMQ54ZM
yL+O4xAArPYCfnMdqUp0TKEuaU04vHMfPPGRyjy+r3XPsXjgenb/ow09PvOrsrF2
2kFneq56gh6XgZNlfKL0rKLXokElR/ekDObs6SVm1dcWbage+iwKaH/jZMYfqvqu
LbPir9clvBwVI4dapk8kAilmq8CEM8Y24PY3P4+1f0L1+YA68lLf6zASWGAtrD52
Oi1+KyVIgVyOOr8KW+1X0nqWdgo51/p/loY580Cuik8seuza5MGrtZS8Ze5AkGc/
dWuZudDCW96oyibEUop1wW6fO03tt7FLuDQrJ7g3anxKtjXjF065E+mQt4RnRpDN
ooV6tVZ/fVqIS+z9WtkK//pO+B0YE05d8MA6wvm625bkicPQsJkl8ptrDjnqZEtc
gfkn5LOAFScCt95c+OlEEvCcoKxcGSes0gFz7CNAaEQMhvmyhLfcfq2TWyWuTGgj
p36hxo4jeNkOMeVRAhm0XMLWuNC5MFhV0xRN7ECnTv8xMEIHx2JoYIBdGMHYOg1p
dg7QnGkjfA9Rw0vl4sF+6zdT1NCvxHegyPwmZ+UCiCJE3fY0s4vMybgrQLzK+zzy
qhmw7GwMOjXMhLYvvuAVuikrAlKkWiyl2e6UC61IOBXdbeU4Htqahr2BUWaJFe7d
2Q2W2TAeIy7VOoNFpN+sbDWBV+XoVNOdypSbhzhOTZYP6Z5sdGo=
=6hhe
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1057877: Acknowledgement (Package new tango upstream release: 9.5.0)

Processing control commands:

> block 1057862 by -1
Bug #1057862 [src:pytango] pytango ftbfs with Python 3.12
1057862 was not blocked by any bugs.
1057862 was not blocking any bugs.
Added blocking bug(s) of 1057862: 1057877
> block 1055733 by -1
Bug #1055733 [src:pytango] pytango ftbfs with Python 3.12 (test failures)
1055733 was not blocked by any bugs.
1055733 was not blocking any bugs.
Added blocking bug(s) of 1055733: 1057877

-- 
1055733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055733
1057862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057862
1057877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1057889: graphviz_10.0.0~git231209-1_riscv64-buildd.changes REJECTED

Processing control commands:

> tags -1 +confirmed pending
Bug #1057889 [src:graphviz] graphviz_10.0.0~git231209-1_riscv64-buildd.changes 
REJECTED
Added tag(s) confirmed and pending.

-- 
1057889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057889: graphviz_10.0.0~git231209-1_riscv64-buildd.changes REJECTED

2023-12-10 Thread GCS

Control: tags -1 +confirmed pending

On Sun, Dec 10, 2023 at 10:33 AM Aurelien Jarno  wrote:
> On 2023-12-10 07:05, Debian FTP Masters wrote:
> > graphviz-tools_10.0.0~git231209-1_riscv64.deb: has 1 file(s) with a 
> > timestamp=
> >  too far in the past:
> >   usr/share/doc/graphviz-tools/copyright (Thu Jan  1 00:01:00 1970)
 Seems I updated my Bookworm system too soon and hit the ext4
corruption bug in the kernel as noted in #1057843. Luckily an fsck
corrected my filesystem and package update is in progress.

Regards,
Laszlo/GCS

Processed: intake: can't handle newlines in error messages

Processing control commands:

> unblock 1043240 by 1044050
Bug #1043240 [python3-pandas] transition: pandas 1.5 -> 2.1
1043240 was blocked by: 1044054 1053942 1044067 1053940 1050144 1044078 1044053 
1044066 1044065 1044071 1053945 1053946 1044058 1044073 1053947 1044069 1044060 
1044074 1044063 1053948 1044055 1044056 1053941 1044064 1044072 1044057 1044079 
1044070 1044077 1044050 1044059 1044052 1053944 1053939 1043093 1044076 1044075 
1044061 1043968 1044068 1053943
1043240 was not blocking any bugs.
Removed blocking bug(s) of 1043240: 1044050
> severity 1044050 serious
Bug #1044050 [src:intake] intake: FTBFS with pandas 2.0
Severity set to 'serious' from 'normal'
> merge 1044050 1050623
Bug #1044050 [src:intake] intake: FTBFS with pandas 2.0
Bug #1044050 [src:intake] intake: FTBFS with pandas 2.0
Added tag(s) sid, ftbfs, and trixie.
Bug #1050623 [src:intake] intake: autopkgtest needs update for dask 2023.8.0
Merged 1044050 1050623
> retitle -1 intake: newlines in error messages
Bug #1044050 [src:intake] intake: FTBFS with pandas 2.0
Bug #1050623 [src:intake] intake: autopkgtest needs update for dask 2023.8.0
Changed Bug title to 'intake: newlines in error messages' from 'intake: FTBFS 
with pandas 2.0'.
Changed Bug title to 'intake: newlines in error messages' from 'intake: 
autopkgtest needs update for dask 2023.8.0'.
> tags -1 patch
Bug #1044050 [src:intake] intake: newlines in error messages
Bug #1050623 [src:intake] intake: newlines in error messages
Added tag(s) patch.
Added tag(s) patch.

-- 
1043240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043240
1044050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044050
1050623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057843: Guidelines for affected users

2023-12-10 Thread Tim Connors

Meanwhile, can the ftp admins pull this faulty version?

I just managed to download and install this, but fortunately didn't reboot
on all of my systems before coming across this bug via LWN via reddit.

If you're in such a pickle as myself, you're able to get around it for now
by:

apt install linux-image-amd64/bookworm-security
dpkg --get-selections | grep 6.1.0.14
apt purge linux-image-6.1.0-14-amd64
(probably want to mark that one as uninstallable too, but there's only one
of me, surely I'll remember not to install it at a later date??!)

and at worst you'll be left on the kernel you're currently running.

I am basing this off https://lwn.net/Articles/954285/

"- Stable kernels < 6.5 are affected if they have 91562895f803 (ext4
commit)
- Kernels >= 6.5 are not affected, as they will _also_ have 936e114a245b6
(iomap commit)"

91562895f803 is not in 6.1.55-1 that anyone who last updated 3 weeks ago
would have encountered, nor in the current bookworm-security version.


-- 
Tim Connors

Bug#1057593: marked as done (python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS_FOR_BUILD) in dpkg-buildflags)

Your message dated Sun, 10 Dec 2023 11:56:26 +
with message-id 
and subject line Bug#1057593: fixed in python-escript 5.6-6
has caused the Debian Bug report #1057593,
regarding python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS_FOR_BUILD) 
in dpkg-buildflags
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.)


-- 
1057593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-escript
Version: 5.6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build  -v
   dh_update_autotools_config -O-v
   dh_autoreconf -O-v
   dh_auto_configure -O-v
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Build steps for py3
mkdir -p /<>/debian/stage3
scons  -j2   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 verbose=on 
prefix=/<>/debian/stage3 options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.11.6 (main, Oct  8 2023, 05:06:43) [GCC 13.2.0]
RuntimeError: Unknown key (ASFLAGS_FOR_BUILD) in dpkg-buildflags:
  File "/<>/SConstruct", line 172:
env = Environment(tools = ['default'], options = vars,
  File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1231:
variables.Update(self)
  File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
exec(contents, {}, values)
  File "", line 84:

  File "/<>/site_scons/extractdebbuild.py", line 52:

raise RuntimeError("Unknown key ("+key+") in dpkg-buildflags")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:38: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-escript
Source-Version: 5.6-6
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
python-escript, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-escript 
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: Sun, 10 Dec 2023 10:53:54 +
Source: python-escript
Architecture: source
Version: 5.6-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1057593
Changes:
 python-escript (5.6-6) unstable; urgency=medium
 .
   * Update patch for new buildflags. Closes: #1057593
Checksums-Sha1:
 38b850e64a8ed3683a8f02e4b95663480a44b68d 2740 python-escript_5.6-6.dsc
 07c76ce965a83bc063fc806d3a19258c919bdcc4 19436 
python-escript_5.6-6.debian.tar.xz
Checksums-Sha256:
 52182e8a530a767a396e4f293bcf0603241b76d1f48efa13c6e08ceb1022bea4 2740 
python-escript_5.6-6.dsc
 57746d4811eb3b1de54626e4cbaea51a1bd1a7423075ea578f79ca8be890e021 19436 
python-escript_5.6-6.debian.tar.xz
Files:
 50f569507cc5de78833b09565185e2ff 2740 science optional python-escript_5.6-6.dsc
 a895e1dfe9af772d4326184cca90eab1 19436 science optional 
python-escript_5.6-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#1055563: marked as done (pycdio ftbfs with Python 3.12)

Your message dated Sun, 10 Dec 2023 11:55:55 +
with message-id 
and subject line Bug#1055563: fixed in pycdio 2.1.1-1.1
has caused the Debian Bug report #1055563,
regarding pycdio ftbfs with 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.)


-- 
1055563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pycdio
Version: 2.1.1-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12


[...]
   dh_auto_test -O--buildsystem=pybuild -O--builddirectory=build
dh_auto_test: warning: warning: pybuild does not support building out of 
source tree. In source building enforced.
I: pybuild base:310: cd 
/<>/.pybuild/cpython3_3.12_cdio/build; python3.12 -m nose 
-v test

Traceback (most recent call last):
  File "", line 189, in _run_module_as_main
  File "", line 148, in _get_module_details
  File "", line 112, in _get_module_details
  File "/usr/lib/python3/dist-packages/nose/__init__.py", line 1, in 


from nose.core import collector, main, run, run_exit, runmodule
  File "/usr/lib/python3/dist-packages/nose/core.py", line 12, in 
from nose.loader import defaultTestLoader
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 21, in 


from nose.importer import Importer, add_path, remove_path
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 12, in 


from imp import find_module, load_module, acquire_lock, release_lock
ModuleNotFoundError: No module named 'imp'
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.12_cdio/build; python3.12 -m 
nose -v test



and then later fails with:

[...]
   dh_auto_test -O--buildsystem=pybuild -O--builddirectory=build
dh_auto_test: warning: warning: pybuild does not support building out of 
source tree. In source building enforced.
I: pybuild base:310: cd 
/home/packages/12/pycdio-2.1.1/.pybuild/cpython3_3.12_cdio/build; 
python3.12 -m nose -v test

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/result.py", line 14, in 


from unittest.runner import _TextTestResult
ImportError: cannot import name '_TextTestResult' from 'unittest.runner' 
(/usr/lib/python3.12/unittest/runner.py). Did you mean: 'TextTestResult'?


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 189, in _run_module_as_main
  File "", line 148, in _get_module_details
  File "", line 112, in _get_module_details
  File "/usr/lib/python3/dist-packages/nose/__init__.py", line 1, in 


from nose.core import collector, main, run, run_exit, runmodule
  File "/usr/lib/python3/dist-packages/nose/core.py", line 15, in 
from nose.result import TextTestResult
  File "/usr/lib/python3/dist-packages/nose/result.py", line 16, in 


from unittest import _TextTestResult
ImportError: cannot import name '_TextTestResult' from 'unittest' 
(/usr/lib/python3.12/unittest/__init__.py). Did you mean: 'TextTestResult'?
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /home/packages/12/pycdio-2.1.1/.pybuild/cpython3_3.12_cdio/build; 
python3.12 -m nose -v test
--- End Message ---
--- Begin Message ---
Source: pycdio
Source-Version: 2.1.1-1.1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
pycdio, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated pycdio package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 12:06:13 +0100
Source: pycdio
Architecture: source
Version: 2.1.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Timo Aaltonen 
Changed-By: Sebastian Ramacher 
Closes: 1055563
Changes:
 pycdio (2.1.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches: Fix compatibility with Python 3.12 (Closes: #1055563)
Checksums-Sha1:
 8213a382451f43af14154b900f45bde82927 1345 pycdio_2.1.1-1.1.dsc

Bug#1054533: marked as done (nvme-stas: autopkgtest fails on all architectures)

Your message dated Sun, 10 Dec 2023 11:55:16 +
with message-id 
and subject line Bug#1054533: fixed in nvme-stas 2.3.1-1
has caused the Debian Bug report #1054533,
regarding nvme-stas: autopkgtest fails on all architectures
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.)


-- 
1054533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvme-stas
Version: 2.3-1
Severity: serious
Justification: autopkgtest fails, blocking reverse dependencies migrations

 36s autopkgtest [21:22:19]: test unittest: cp -r test "$AUTOPKGTEST_TMP" && cd 
"$AUTOPKGTEST_TMP/test" && rm test-avahi.py && python3 -m unittest -v test*.py
 36s autopkgtest [21:22:19]: test unittest: [---
 36s Error reading mandatory Host NQN (see stasadm --help): [Errno 2] No such 
file or directory: '/etc/nvme/hostnqn'

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvme-stas/39251054/log.gz

This is blocking iproute2's migration from unstable to testing, hence
filing at high severity.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nvme-stas
Source-Version: 2.3.1-1
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
nvme-stas, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
nvme-stas package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2023 11:42:55 +0100
Source: nvme-stas
Architecture: source
Version: 2.3.1-1
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1054533 1057031 1057530
Changes:
 nvme-stas (2.3.1-1) sid; urgency=medium
 .
   * Uploading to sid.
   * Merging upstream version 2.3.1: - properly handles big-endian data in
 `iputils.py` (Closes: #1057031).
   * Adding patch from upstream to fix udev tests with dummy interfaces,
 thanks to Olivier Gayot  (Closes:
 #1057530).
   * Adding patch from upstream to fix tests with esoteric interface names,
 thanks to Olivier Gayot  (Closes:
 #1057530).
   * Adding nvme-cli to autopkg depends, thanks to Olivier Gayot
  (Closes: #1054533).
Checksums-Sha1:
 7346116cfc61434119dc8740380e47c574646c68 2275 nvme-stas_2.3.1-1.dsc
 04190583049b555ffd0f0a090155e301553392d5 323696 nvme-stas_2.3.1.orig.tar.xz
 7b036ab95906aee855a7c0d481d629d21f1a603b 4744 nvme-stas_2.3.1-1.debian.tar.xz
 ac7b23208cd6c305a8a0d3ee2347ae9e1b107a0d 7800 nvme-stas_2.3.1-1_amd64.buildinfo
Checksums-Sha256:
 72e1241a446b50a655b82038ff8d8c9fd76d687662ab4e81d8892c7b8811991b 2275 
nvme-stas_2.3.1-1.dsc
 0f9664d1d1fc119ffcc3792582026ee3ccbab15b944d7d055b56979cb5ea6449 323696 
nvme-stas_2.3.1.orig.tar.xz
 157bf7dd144e8f8c160475576c05d4f4464713458d5162db7e7520b51cec9dcf 4744 
nvme-stas_2.3.1-1.debian.tar.xz
 74ec8d2b8a1a62705cd9a850204f9551239557c591613cf1580b057ef135006e 7800 
nvme-stas_2.3.1-1_amd64.buildinfo
Files:
 1508607c69a73b38e7177e1592176b2c 2275 net optional nvme-stas_2.3.1-1.dsc
 ca5e152780abed8945623af9daf23af2 323696 net optional 
nvme-stas_2.3.1.orig.tar.xz
 eadcde7d5c40d72903cf085ab48a0da0 4744 net optional 
nvme-stas_2.3.1-1.debian.tar.xz
 0e44d7b7e11c304a0b6ec33110df034f 7800 net optional 
nvme-stas_2.3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmV1lokACgkQVc8b+Yar
uccgZQ/7BADtF9o7EPf3WzZgPaAH72awqX7g8s2ZG2nlVOGsQINSVI/AfidV8Pll
E9yOdpJcsm8sgFGoXLxjN6uvvdL4RAIBY6Es5WIPW6yJeVVB74tKGp8LkAioXdO3
S422FhrQITQUQe2lkbxX8qBVJOAXTEnHXdgtxeR6rmVh9O6pG0fQt09wkJzqUw2b
BBDhzotQppCSnWNxJv9VuhoMzK8JmN5DgcnnX8fHuzxtbVRg4p117R770TV4YFin
GEbmOAst+SRnI2NRH+HC+hYm5lxdpueKMl9OxTy1fQ2IpKwT5A/nwJCpstQnQqXK
AUZ7HAvuC3ViV/TTo+/E+7OFGehPqhKi+7JSKSulYnobvtUNdhIWzr2iAFY+gd4k
vFCKqRUXuH97QmnMZUDIGnd5gaipTq7/cNhC9ndl7o9bZo6AoMAby3KJsPuNzG0Z
PHmSMjzmEoowTWwhSx8JW7aW+3a6joj29BKrM7S9Qo8WEtpNYnC5Vhmraikwg6hL
ltw3pN21Dwvn42mE3VPrQkjSMtQfRfOyj8K+1Uc8054Jrj9fBKE1WdL7yksUdTso

Bug#1052310: marked as done (plymouth FTBFS when systemdsystemunitdir changes in systemd.pc)

Your message dated Sun, 10 Dec 2023 11:55:48 +
with message-id 
and subject line Bug#1052310: fixed in plymouth 22.02.122-4
has caused the Debian Bug report #1052310,
regarding plymouth FTBFS when systemdsystemunitdir changes in systemd.pc
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.)


-- 
1052310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plymouth
Version: 22.02.122-3
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc. The
upstream build system of plymouth consumes this value, but the packaging
hard codes the current value. Once the value is changed, plymouth will
FTBFS. I'm attaching a patch that fixes this future build failure for
your convenience.

Helmut
diff -Nru plymouth-22.02.122/debian/changelog 
plymouth-22.02.122/debian/changelog
--- plymouth-22.02.122/debian/changelog 2023-02-01 18:20:20.0 +0100
+++ plymouth-22.02.122/debian/changelog 2023-09-20 11:08:04.0 +0200
@@ -1,3 +1,10 @@
+plymouth (22.02.122-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemdsystemunitdir changes in systemd.pc. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 20 Sep 2023 11:08:04 +0200
+
 plymouth (22.02.122-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru plymouth-22.02.122/debian/plymouth.install 
plymouth-22.02.122/debian/plymouth.install
--- plymouth-22.02.122/debian/plymouth.install  2023-02-01 18:20:20.0 
+0100
+++ plymouth-22.02.122/debian/plymouth.install  2023-09-20 11:07:57.0 
+0200
@@ -1,6 +1,6 @@
 etc/logrotate.d
 etc/plymouth
-lib/systemd
+${env:systemdsystemunitdir}
 usr/bin
 usr/lib/*/plymouth/details.so
 usr/lib/*/plymouth/renderers/drm.so
diff -Nru plymouth-22.02.122/debian/rules plymouth-22.02.122/debian/rules
--- plymouth-22.02.122/debian/rules 2023-02-01 18:20:20.0 +0100
+++ plymouth-22.02.122/debian/rules 2023-09-20 11:07:34.0 +0200
@@ -6,6 +6,8 @@
 # symbols, and speed up loading.
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,defs -Wl,-O1
 
+export systemdsystemunitdir=$(shell pkg-config --variable=systemdsystemunitdir 
systemd | sed s,^/,,)
+
 %:
dh ${@}
 
--- End Message ---
--- Begin Message ---
Source: plymouth
Source-Version: 22.02.122-4
Done: Laurent Bigonville 

We believe that the bug you reported is fixed in the latest version of
plymouth, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated plymouth 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: Sun, 10 Dec 2023 12:00:10 +0100
Source: plymouth
Architecture: source
Version: 22.02.122-4
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Laurent Bigonville 
Closes: 916792 1035076 1050545 1052310
Changes:
 plymouth (22.02.122-4) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemdsystemunitdir changes in systemd.pc. (Closes:
 #1052310)
 .
   [ Laurent Bigonville ]
   * debian/control: Add elogind as an alternative to systemd as elogind
 package ships the necessesary udev rules files (Closes: #1035076)
   * debian/local/plymouth.hook: Do not copy the security contexts when
 building the initramfs (Closes: #1050545)
   * Update initramfs for all kernel versions when installing or removing
 plymouth (Closes: #916792)
   * debian/control: Drop lsb-base, to please lintian
   * debian/plymouth.links: Fix .service symlink path after move to /usr
   * debian/rules: Move LSB init-functions file to /usr
Checksums-Sha1:
 f71f104559a3a9c1d0474544dd92017bf40ee29a 2042 plymouth_22.02.122-4.dsc
 1fff6b2d3c4c5a7045893fe7560acd0f1c484d62 29412 
plymouth_22.02.122-4.debian.tar.xz
 3ad37661955f7e9f1409dc529eb0a1964be9234f 14069 
plymouth_22.02.122-4_source.buildinfo
Checksums-Sha256:
 0fbede535aa54cbbd84cb0121e562fb9986e95acfbd6e181f42577f242bf3308 2042 
plymouth_22.02.122-4.dsc

Processed: pycdio: diff for NMU version 2.1.1-1.1

Processing control commands:

> tags 1055563 + patch
Bug #1055563 [src:pycdio] pycdio ftbfs with Python 3.12
Added tag(s) patch.

-- 
1055563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055563: pycdio: diff for NMU version 2.1.1-1.1

2023-12-10 Thread Sebastian Ramacher

Control: tags 1055563 + patch

Dear maintainer,

I've prepared an NMU for pycdio (versioned as 2.1.1-1.1). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru pycdio-2.1.1/debian/changelog pycdio-2.1.1/debian/changelog
--- pycdio-2.1.1/debian/changelog	2021-08-30 12:59:08.0 +0200
+++ pycdio-2.1.1/debian/changelog	2023-12-10 12:06:13.0 +0100
@@ -1,3 +1,10 @@
+pycdio (2.1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix compatibility with Python 3.12 (Closes: #1055563)
+
+ -- Sebastian Ramacher   Sun, 10 Dec 2023 12:06:13 +0100
+
 pycdio (2.1.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru pycdio-2.1.1/debian/patches/python3.12.patch pycdio-2.1.1/debian/patches/python3.12.patch
--- pycdio-2.1.1/debian/patches/python3.12.patch	1970-01-01 01:00:00.0 +0100
+++ pycdio-2.1.1/debian/patches/python3.12.patch	2023-12-10 12:05:43.0 +0100
@@ -0,0 +1,29 @@
+--- a/test/test-cdtext.py
 b/test/test-cdtext.py
+@@ -29,7 +29,7 @@
+ class CDTextTests(unittest.TestCase):
+ def test_keyword(self):
+ """Test keywords"""
+-self.assertEquals(
++self.assertEqual(
+ pycdio.cdtext_field2str(pycdio.CDTEXT_FIELD_PERFORMER), "PERFORMER"
+ )
+ 
+@@ -39,12 +39,12 @@
+ device = cdio.Device(tocpath, pycdio.DRIVER_CDRDAO)
+ 
+ text = device.get_cdtext()
+-self.assertEquals(text.get(pycdio.CDTEXT_FIELD_PERFORMER, 0), "Performer")
+-self.assertEquals(text.get(pycdio.CDTEXT_FIELD_TITLE, 0), "CD Title")
+-self.assertEquals(text.get(pycdio.CDTEXT_FIELD_DISCID, 0), "XY12345")
++self.assertEqual(text.get(pycdio.CDTEXT_FIELD_PERFORMER, 0), "Performer")
++self.assertEqual(text.get(pycdio.CDTEXT_FIELD_TITLE, 0), "CD Title")
++self.assertEqual(text.get(pycdio.CDTEXT_FIELD_DISCID, 0), "XY12345")
+ 
+-self.assertEquals(text.get(pycdio.CDTEXT_FIELD_PERFORMER, 1), "Performer")
+-self.assertEquals(text.get(pycdio.CDTEXT_FIELD_TITLE, 1), "Track Title")
++self.assertEqual(text.get(pycdio.CDTEXT_FIELD_PERFORMER, 1), "Performer")
++self.assertEqual(text.get(pycdio.CDTEXT_FIELD_TITLE, 1), "Track Title")
+ 
+ 
+ if __name__ == "__main__":
diff -Nru pycdio-2.1.1/debian/patches/series pycdio-2.1.1/debian/patches/series
--- pycdio-2.1.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ pycdio-2.1.1/debian/patches/series	2023-12-10 12:05:18.0 +0100
@@ -0,0 +1 @@
+python3.12.patch

Processed: Re: tombo: FTBFS with Python 3.12

Processing commands for cont...@bugs.debian.org:

> severity 1057847 important
Bug #1057847 [src:tombo] tombo: FTBFS with Python 3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dipy: FTBFS with Python 3.12

Processing commands for cont...@bugs.debian.org:

> severity 1057845 important
Bug #1057845 [src:dipy] dipy: FTBFS with Python 3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: libslow5lib: FTBFS with Python 3.12

Processing commands for cont...@bugs.debian.org:

> severity 1057839 important
Bug #1057839 [src:libslow5lib] libslow5lib: FTBFS with Python 3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: python-pysam ftbfs with Python 3.12

Processing control commands:

> unblock -1 by 1057762
Bug #1057809 [src:python-pysam] python-pysam ftbfs with Python 3.12
1057809 was blocked by: 1057762
1057809 was not blocking any bugs.
Removed blocking bug(s) of 1057809: 1057762

-- 
1057809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057809: python-pysam ftbfs with Python 3.12

2023-12-10 Thread Sebastiaan Couwenberg


Control: unblock -1 by 1057762

On Sat, 9 Dec 2023 14:03:35 +0100 Sebastiaan Couwenberg wrote:

The package builds successfully with cython 3.0 from experimental.


It also builds successfully with cython (0.29.36-3.1):

 https://buildd.debian.org/status/package.php?p=python-pysam

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Fix blocked by 1057762: cython: Move cython 3.0 from experimental to unstable

Processing control commands:

> unblock -1 by 1057762
Bug #1055692 [src:macs] macs ftbfs with Python 3.12
1055692 was blocked by: 1057762
1055692 was not blocking any bugs.
Removed blocking bug(s) of 1055692: 1057762

-- 
1055692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055692: Fix blocked by 1057762: cython: Move cython 3.0 from experimental to unstable

2023-12-10 Thread Sebastiaan Couwenberg


Control: unblock -1 by 1057762

The package builds successfully with cython (0.29.36-3.1):

 https://buildd.debian.org/status/package.php?p=macs

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#1057737: python-cartopy: FTBFS with Python 3.12

Processing commands for cont...@bugs.debian.org:

> severity 1057737 important
Bug #1057737 [src:python-cartopy] python-cartopy: FTBFS with Python 3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054944: marked as done (gitit: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 2.1), libghc-happstack-server-dev (< 7.8), libghc-hoauth2-dev (< 2.4), libghc-pandoc-dev (>= 2.9), libg