Processed: Bug#1057815 marked as pending in debian-edu-artwork

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1057815 [debian-edu-artwork-emerald] debian-edu-artwork-emerald: modifies 
conffile: /etc/plymouth/plymouthd.conf
Added tag(s) pending.

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



Bug#1057815: marked as pending in debian-edu-artwork

2023-12-08 Thread Mike Gabriel
Control: tag -1 pending

Hello,

Bug #1057815 in debian-edu-artwork 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/debian-edu/debian-edu-artwork/-/commit/ebf6b657e45f5f14aca2517569a9ee14f251f1c6


Revert "debian/update-debian-edu-artwork: Stop checking if this is a Debian Edu 
system."

Closes: #1057815
See also: #856789

This reverts commit 65703345dd7a400c3f4d548ae037f63253a4f1a2.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057815



Bug#1057815: debian-edu-artwork-emerald: modifies conffile: /etc/plymouth/plymouthd.conf

2023-12-08 Thread Mike Gabriel

On  Fr 08 Dez 2023 22:52:45 CET, Andreas Beckmann wrote:


Followup-For: Bug #1057815

Hi,

this actually causes prompting for modified conffiles on upgrades from
bullseye to bookworm+pu:

  Setting up plymouth (22.02.122-3) ...

  Configuration file '/etc/plymouth/plymouthd.conf'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** plymouthd.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error  
processing package plymouth (--configure):

   end of file on stdin at conffile prompt


Oh damn, we already have been here: #856789.

At that time I manipulated the update script so that plymouthd.conf  
only gets modified on Debian Edu installations. This was sufficient  
for Debian policy. I will revert this now to the previous state.


This is the commit that introduced this regression (neglecting history  
of the package):

https://salsa.debian.org/debian-edu/debian-edu-artwork/-/commit/65703345dd7a400c3f4d548ae037f63253a4f1a2

(My revert will then also contain a comment to never undo this again).

Sorry, for the noise!!!

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpur6a0PfnS0.pgp
Description: Digitale PGP-Signatur


Bug#1054193: marked as done (arpwatch: installs arpwatch@.service twice once dh_installsystemd installs to /usr)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Dec 2023 06:48:54 +
with message-id 
and subject line Bug#1054193: fixed in arpwatch 2.1a15-8.1
has caused the Debian Bug report #1054193,
regarding arpwatch: installs arpwatch@.service twice once dh_installsystemd 
installs to /usr
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.)


-- 
1054193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arpwatch
Version: 2.1a15-8
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to change dh_installsystemd to install to /usr to finalize the
/usr-merge transition via DEP17. Once doing so, arpwatch will contain
/usr/lib/systemd/system/arpwatch@.service (via dh_installsystemd) and
/lib/systemd/system/arpwatch@.service (via dh_install). This is a policy
violation. I'm attaching a patch for your convenience. Once I upload
debhelper, this bug will become release critical.

Helmut
diff -Nru arpwatch-2.1a15/debian/arpwatch.install 
arpwatch-2.1a15/debian/arpwatch.install
--- arpwatch-2.1a15/debian/arpwatch.install 2021-01-31 17:44:03.0 
+0100
+++ arpwatch-2.1a15/debian/arpwatch.install 2023-10-18 13:28:51.0 
+0200
@@ -1,7 +1,6 @@
 arp2ethers   usr/sbin/
 arpfetch usr/sbin/
 *.awkusr/lib/arpwatch/
-debian/arpwatch@.service lib/systemd/system
 debian/etc/READMEetc/arpwatch/
 debian/ieee-data-update/arpwatch var/lib/ieee-data/update.d/
 debian/sbin/*usr/sbin/
diff -Nru arpwatch-2.1a15/debian/changelog arpwatch-2.1a15/debian/changelog
--- arpwatch-2.1a15/debian/changelog2021-01-31 17:44:03.0 +0100
+++ arpwatch-2.1a15/debian/changelog2023-10-18 13:30:20.0 +0200
@@ -1,3 +1,10 @@
+arpwatch (2.1a15-8.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install arpwatch@.service only once. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 18 Oct 2023 13:30:20 +0200
+
 arpwatch (2.1a15-8) unstable; urgency=medium
 
   * Team Upload
--- End Message ---
--- Begin Message ---
Source: arpwatch
Source-Version: 2.1a15-8.1
Done: Salvatore Bonaccorso 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2023 07:12:41 +0100
Source: arpwatch
Architecture: source
Version: 2.1a15-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Salvatore Bonaccorso 
Closes: 1054193
Changes:
 arpwatch (2.1a15-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Install arpwatch@.service only once. (Closes: #1054193)
Checksums-Sha1: 
 3dc51c994bebb540c8e9b34b518e1bf28e3341ca 2100 arpwatch_2.1a15-8.1.dsc
 d43bc159250efbc5586a9f2d5042068fde47b604 33004 
arpwatch_2.1a15-8.1.debian.tar.xz
Checksums-Sha256: 
 fc1037a6f3fad6cdd0dd32deab9c6e6c1a05a09813a3062b9604cdd9a19ea480 2100 
arpwatch_2.1a15-8.1.dsc
 dfcdd0fa3c8b319901531a08ecfed75b4abb83933d60137291813d02908b5d0e 33004 
arpwatch_2.1a15-8.1.debian.tar.xz
Files: 
 c606fdee73b10e09e657a94c98acbd98 2100 admin optional arpwatch_2.1a15-8.1.dsc
 84e1097cd6345dfa700a79c235f843bf 33004 admin optional 
arpwatch_2.1a15-8.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmVxYrxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EDSYP/j0IcsCagt10tGnPuB1y6dqW3TFUyutp
7KmGfpyc7q8cAQx0ecqstfg8wmffviR0f6jrzrVfJ7B5vax8CSDwaoUBraXbvza3
OQvGHSs5bmv8x87VPD2bmvyYTe1He2bqad0BQgGr+kGUXA9u6IV63/hV8Hb9oJA0
M5S6mHsVFvac12vkG2Zed1VAhN8tkk81+73ksGdTjUI8Y+V/6QrjJlhG6YXz3Iyf
T/KqLlTXEcThR3Knd4SbNcpdu1YFwKrWJQOsumPV6Xrd5WOqGz6x59RL4WO2JMy1
GM/hCdijGPu5CNy/wmFyC0hfx1jfjrI88M7TXH6cP71UtRJ0ooc0hMjoMZe/QT9V

Bug#1057799: systemd: fails to configure

2023-12-08 Thread Michael Biebl

Am 09.12.23 um 00:53 schrieb JP Pozzi:

Hello,

Here the result :

grep users /etc/group /etc/gshadow
/etc/group:users:x:100:
/etc/gshadow:users:*::suricata


You appear to have a mismatch between /etc/group and /etc/gshadow.
Either your user "suricata" is listed in both or none.

Not sure how you ended up in this situation, but this looks like a local 
misconfiguration.


Michael



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, 

Here the result : 

grep users /etc/group /etc/gshadow 
/etc/group:users:x:100: 
/etc/gshadow:users:*::suricata 

To circumvent the problem ; 
1) I save /etc/gshadow, drop the "offending" line 
and restart systemd --configure 
with success 
2) Restore the saved gshadow file. 

Regards 

JP P 

- Mail original - 
De: "Michael Biebl"  
À: 1057...@bugs.debian.org, "JPPO"  
Envoyé: Vendredi 8 Décembre 2023 18:48:18 
Objet: Re: systemd: fails to configure 

On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote: 
> Package: systemd 
> Version: 252.19-1~deb12u1 
> Severity: serious 
> Tags: d-i 
> Justification: normal 
> 
> Dear Maintainer, 
> 
> I get a problem upgrading the system, systemd fails to configure : 
> 
> sudo dpkg --configure systemd 
> Setting up systemd (252.19-1~deb12u1) ... 
> Creating group 'users' with GID 100. 
> /etc/gshadow: Group "users" already exists. 

Can you attach the output of 

sudo grep users /etc/group /etc/gshadow 


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, 

Sorry I didn't see the second part, here is it : 
1) SYSTEMD_LOG_LEVEL=debug 
# systemd-sysusers /usr/lib/sysusers.d/basic.conf 
result : nothing 
2) cat /usr/lib/sysusers.d/basic.conf 
# generated from /usr/share/base-passwd/{passwd,group}.master 
g adm 4 - 
g tty 5 - 
g disk 6 - 
g man 12 - 
g kmem 15 - 
g dialout 20 - 
g fax 21 - 
g voice 22 - 
g cdrom 24 - 
g floppy 25 - 
g tape 26 - 
g sudo 27 - 
g audio 29 - 
g dip 30 - 
g operator 37 - 
g src 40 - 
g shadow 42 - 
g utmp 43 - 
g video 44 - 
g sasl 45 - 
g plugdev 46 - 
g staff 50 - 
g games 60 - 
g users 100 - 
g nogroup 65534 - 

u root 0 - /root /bin/bash 
u daemon 1 - /usr/sbin /usr/sbin/nologin 
u bin 2 - /bin /usr/sbin/nologin 
u sys 3 - /dev /usr/sbin/nologin 
u sync 4:65534 - /bin /bin/sync 
u games 5:60 - /usr/games /usr/sbin/nologin 
u man 6:12 - /var/cache/man /usr/sbin/nologin 
u lp 7 - /var/spool/lpd /usr/sbin/nologin 
u mail 8 - /var/mail /usr/sbin/nologin 
u news 9 - /var/spool/news /usr/sbin/nologin 
u uucp 10 - /var/spool/uucp /usr/sbin/nologin 
u proxy 13 - /bin /usr/sbin/nologin 
u www-data 33 - /var/www /usr/sbin/nologin 
u backup 34 - /var/backups /usr/sbin/nologin 
u list 38 - /var/list /usr/sbin/nologin 
u irc 39 - /run/ircd /usr/sbin/nologin 
u _apt 42:65534 - /nonexistent /usr/sbin/nologin 
u nobody 65534:65534 - /nonexistent /usr/sbin/nologin 


I hope this will help. 

Regards 

JP P 


- Mail original - 
De: "Michael Biebl"  
À: "1057799" <1057...@bugs.debian.org>, "JPPO"  
Envoyé: Vendredi 8 Décembre 2023 18:51:17 
Objet: Re: systemd: fails to configure 

Am 08.12.23 um 18:48 schrieb Michael Biebl: 
> On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote: 
>> Package: systemd 
>> Version: 252.19-1~deb12u1 
>> Severity: serious 
>> Tags: d-i 
>> Justification: normal 
>> 
>> Dear Maintainer, 
>> 
>> I get a problem upgrading the system, systemd fails to configure : 
>> 
>> sudo dpkg --configure systemd 
>> Setting up systemd (252.19-1~deb12u1) ... 
>> Creating group 'users' with GID 100. 
>> /etc/gshadow: Group "users" already exists. 
> 
> Can you attach the output of 
> 
> sudo grep users /etc/group /etc/gshadow 
> 

The output of 

sudo SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/basic.conf 

as well, please 


Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello,

Here the result :

grep users /etc/group /etc/gshadow
/etc/group:users:x:100:
/etc/gshadow:users:*::suricata

To circumvent the problem ;
1) I save /etc/gshadow, drop the "offending" line 
and restart systemd --configure
with success
2) Restore the saved gshadow file.

Regards 

JP P

- Mail original -
De: "Michael Biebl" 
À: 1057...@bugs.debian.org, "JPPO" 
Envoyé: Vendredi 8 Décembre 2023 18:48:18
Objet: Re: systemd: fails to configure

On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote:
> Package: systemd
> Version: 252.19-1~deb12u1
> Severity: serious
> Tags: d-i
> Justification: normal
> 
> Dear Maintainer,
> 
> I get a problem upgrading the system, systemd fails to configure :
> 
> sudo dpkg --configure systemd
> Setting up systemd (252.19-1~deb12u1) ...
> Creating group 'users' with GID 100.
> /etc/gshadow: Group "users" already exists.

Can you attach the output of

sudo grep users /etc/group /etc/gshadow

OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello,

Sorry I didn't see the second part, here is it :
1) SYSTEMD_LOG_LEVEL=debug
# systemd-sysusers /usr/lib/sysusers.d/basic.conf
result : nothing
2) cat /usr/lib/sysusers.d/basic.conf
# generated from /usr/share/base-passwd/{passwd,group}.master
g adm4 -
g tty5 -
g disk   6 -
g man12-
g kmem   15-
g dialout20-
g fax21-
g voice  22-
g cdrom  24-
g floppy 25-
g tape   26-
g sudo   27-
g audio  29-
g dip30-
g operator   37-
g src40-
g shadow 42-
g utmp   43-
g video  44-
g sasl   45-
g plugdev46-
g staff  50-
g games  60-
g users  100   -
g nogroup65534 -

u root   0   - /root/bin/bash
u daemon 1   - /usr/sbin/usr/sbin/nologin
u bin2   - /bin /usr/sbin/nologin
u sys3   - /dev /usr/sbin/nologin
u sync   4:65534 - /bin /bin/sync
u games  5:60- /usr/games   /usr/sbin/nologin
u man6:12- /var/cache/man   /usr/sbin/nologin
u lp 7   - /var/spool/lpd   /usr/sbin/nologin
u mail   8   - /var/mail/usr/sbin/nologin
u news   9   - /var/spool/news  /usr/sbin/nologin
u uucp   10  - /var/spool/uucp  /usr/sbin/nologin
u proxy  13  - /bin /usr/sbin/nologin
u www-data   33  - /var/www /usr/sbin/nologin
u backup 34  - /var/backups /usr/sbin/nologin
u list   38  - /var/list/usr/sbin/nologin
u irc39  - /run/ircd/usr/sbin/nologin
u _apt   42:65534 - /nonexistent /usr/sbin/nologin
u nobody 65534:65534 - /nonexistent /usr/sbin/nologin


I hope this will help.

Regards

JP P


- Mail original -
De: "Michael Biebl" 
À: "1057799" <1057...@bugs.debian.org>, "JPPO" 
Envoyé: Vendredi 8 Décembre 2023 18:51:17
Objet: Re: systemd: fails to configure

Am 08.12.23 um 18:48 schrieb Michael Biebl:
> On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote:
>> Package: systemd
>> Version: 252.19-1~deb12u1
>> Severity: serious
>> Tags: d-i
>> Justification: normal
>>
>> Dear Maintainer,
>>
>> I get a problem upgrading the system, systemd fails to configure :
>>
>> sudo dpkg --configure systemd
>> Setting up systemd (252.19-1~deb12u1) ...
>> Creating group 'users' with GID 100.
>> /etc/gshadow: Group "users" already exists.
> 
> Can you attach the output of
> 
> sudo grep users /etc/group /etc/gshadow
> 

The output of

sudo SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/basic.conf

as well, please



Bug#1057805: marked as done (pandas ftbfs on at least armhf)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 23:20:07 +
with message-id 
and subject line Bug#1057805: fixed in pandas 1.5.3+dfsg-9
has caused the Debian Bug report #1057805,
regarding pandas ftbfs on at least armhf
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.)


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

Package: src:pandas
Version: 1.5.3+dfsg-7
Severity: serious
Tags: sid trixie

these fail on armhf (but succeeding on armel), and on some ports 
architectures.  If I'm reading correctly, these fail with Python 3.11, 
but not Python 3.12.


[...]
=== short test summary info 

FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data1-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data5-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data5-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data6-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data6-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data7-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data7-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data11-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data15-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data15-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data16-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data16-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data17-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data17-2-sum]
= 14 failed, 469 passed, 834 skipped, 550 deselected in 45.94s 
=
--- End Message ---
--- Begin Message ---
Source: pandas
Source-Version: 1.5.3+dfsg-9
Done: Rebecca N. Palmer 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Dec 2023 19:15:36 +
Source: pandas
Architecture: source
Version: 1.5.3+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Rebecca N. Palmer 
Closes: 1057805
Changes:
 pandas (1.5.3+dfsg-9) unstable; urgency=medium
 .
   * Tests: avoid xfail ordering issue.  (Closes: #1057805)
Checksums-Sha1:
 7342abf9d381b9192b2caa1200f064a49a503b90 4866 pandas_1.5.3+dfsg-9.dsc
 731d0231a2dc2479eea16864d8fc340a7ca2d691 76796 
pandas_1.5.3+dfsg-9.debian.tar.xz
 675c5d10c0e49926eb885e6d225351883ad45abc 6587 
pandas_1.5.3+dfsg-9_source.buildinfo
Checksums-Sha256:
 d76aef56fc7a241627134f8db362ec86af37dd2846b042b49ddf2a03fd24879e 4866 
pandas_1.5.3+dfsg-9.dsc
 eb2f41060f1db29ec34dd72ad278cddce24679507e64ec8151d2a0c6b62f 76796 
pandas_1.5.3+dfsg-9.debian.tar.xz
 38b0af802e401dd2caeb96b63300fdd697cd7305c94bf446b38fce982d942a5b 6587 
pandas_1.5.3+dfsg-9_source.buildinfo
Files:
 6de25b0b506721c29ac7e42c1844202e 4866 python optional pandas_1.5.3+dfsg-9.dsc
 

Processed: Re: Bug#1056980: [devuan-dev] bug#813: Reopen 1056980

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1056980 serious
Bug #1056980 {Done: Helmut Grohne } [netcat-traditional] 
netcat-traditional: upgrade to 1.10-48 fails (postinst script)
Ignoring request to change severity of Bug 1056980 to the same value.
> reopen 1056980
Bug #1056980 {Done: Helmut Grohne } [netcat-traditional] 
netcat-traditional: upgrade to 1.10-48 fails (postinst script)
Bug reopened
Ignoring request to alter fixed versions of bug #1056980 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed (with 1 error): Re: Bug#1056980: [devuan-dev] bug#813: Reopen 1056980

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1056980 {Done: Helmut Grohne } [netcat-traditional] 
netcat-traditional: upgrade to 1.10-48 fails (postinst script)
Severity set to 'serious' from 'normal'
> tags -1 reopen
Unknown tag/s: reopen.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.


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



Bug#1057782: marked as done (gtk4: FTBFS on big-endian: memorytexture test fails)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 22:21:28 +
with message-id 
and subject line Bug#1057782: fixed in gtk4 4.12.4+ds-2
has caused the Debian Bug report #1057782,
regarding gtk4: FTBFS on big-endian: memorytexture test fails
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.)


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

>From 
>https://buildd.debian.org/status/fetch.php?pkg=gtk4=s390x=4.12.4%2Bds-1=1701103591=0
> test: gtk:gdk / memorytexture
> start time:   16:40:53
> duration: 0.64s
> result:   killed by signal 6 SIGABRT
> ...
> 1..2072
> # Start of memorytexture tests
> # Start of download_1x1 tests
> # Start of b8g8r8a8-premultiplied tests
> ok 1 /memorytexture/download_1x1/b8g8r8a8-premultiplied/local
> not ok /memorytexture/download_1x1/b8g8r8a8-premultiplied/gl - 
> ERROR:../../../testsuite/gdk/memorytexture.c:819:compare_textures: 
> 'gdk_memory_format_pixel_equal (format, accurate_compare, data1 + bpp * x, 
> data2 + bpp * x)' should be TRUE

The same test fails on ppc64, which makes me think this is an endianness
bug, probably introduced in the new upstream release 4.12.4. I'm looking
into it.

cc debian-s390 since it is our only big-endian release architecture.

smcv
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.12.4+ds-2
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Dec 2023 17:36:22 +
Source: gtk4
Architecture: source
Version: 4.12.4+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1057782
Changes:
 gtk4 (4.12.4+ds-2) unstable; urgency=medium
 .
   [ Jeremy Bícha ]
   * Reinstate Build-Depends on dh-sequence-gnome.
 This is used by Ubuntu to pull in dh_translations.
 .
   [ Simon McVittie ]
   * d/p/gsk-Always-use-RGBA-on-big-endian-architectures.patch:
 Add proposed patch to fix test failure on big-endian CPUs
 (Closes: #1057782)
Checksums-Sha1:
 9a479f1335f4b9d1120284ecc48be809df700af2 5406 gtk4_4.12.4+ds-2.dsc
 fc32932353e951384e1abc47a13b01f9767c1fa6 3105964 gtk4_4.12.4+ds-2.debian.tar.xz
 0ed35e7d4327ade432c80e68e54bede3d3b3db2e 20441 
gtk4_4.12.4+ds-2_source.buildinfo
Checksums-Sha256:
 a63afbb7936b23dbe17cf5a438bd7ad713ecfcaab6de10fa5070f373a9459958 5406 
gtk4_4.12.4+ds-2.dsc
 58d33e8a98eea84f3e8d16b5b015b13050e31261a19f30fa33dc8353d47cfc6a 3105964 
gtk4_4.12.4+ds-2.debian.tar.xz
 7b0e59a1d9bbba90105dcc52e77ff7cbf7d79e3817b85b909e06b56b7b1380db 20441 
gtk4_4.12.4+ds-2_source.buildinfo
Files:
 533d798bdb8ac740f97df2f3e8ed4405 5406 libs optional gtk4_4.12.4+ds-2.dsc
 efa1e983634751c54ef04c15a258f1a8 3105964 libs optional 
gtk4_4.12.4+ds-2.debian.tar.xz
 448d0fbe2d2de363a5dc3fa8a4300a9d 20441 libs optional 
gtk4_4.12.4+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmVzkdwACgkQ4FrhR4+B
TE8cVw//S2tinkKwzEhcEfMx8cWjPru6xf4E4uWXr72P9ANwm9WNv/9kHkwwlUg+
E2tvouzKt/BLzHE60mIocwDx430Y7MMGcdiB+tc8ujHJkGpu23hzW/sosTOMRpXu
gbFKJwI0ScDQngfahpTQtf0k266g7FObrncXoUp7Cdf/J80MNLfscgBRKlakekTf
vh2Hcek6WgqAELyoCuGAC9O5fvWbq+p53SRlWvsnrO5bplKSnzVKjQD02EjwcbDA
cot0VHBHQiytKYRUVaKBPLAFwOtVE2CNTWPt80HUUxAnTqVIymKn96Nb8Du3uy/n
8mZsGF/GcuedMkRzjy4+RwsaG5xLBMhk8ucnSaoO9biUQENv2WgbxYL1ECoKJkSO
kOkLsIR1bk/sZb1KrdP/P641ndIo2vQu5hTfWkmlBL+GyL2o9aVZMy2ytyTam6JR
Nm/QWDtvInGDhiZdVIdY736IWx28aOW2uSceZB8t/w9NDOl2ccCihU1aeUgf4F67
15pGntnnYi38jIHTWMBQB6mxdJFfsI42TSJ3yYNgvRGNnVkE0lO5i4eZvrYqUtvN
EHXjFzl2XqAEqHA0UppoKU613YCvQawegxDuoTNhWBr2pQbc6qYlHpH3Xx0y0Nfp
HDkC6onHDiYR5PRN4D+iGpdtOu4SAAMkUKq82twnIwzv0OXhXlE=
=75in
-END 

Bug#1057671: closed by Sylvain Beucler (Re: Bug#1057671: cytadela: game include non free graphical assets)

2023-12-08 Thread Alexandre Detiste
I understand your arguments.

There was no real emergency to close this bugs.
I was letting some time for other to voice some opinion.

Some non modifiable Scummvm game blob
have ended up in main but it's another fight
I won't take either.

Anyways I think that this package would
greatly benefit from a machine-readable
d/copyright and a more general refresh.

Greetings



Processed: severity of 1055735 is serious

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1055735 serious
Bug #1055735 [src:geventhttpclient] geventhttpclient ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Processed: Bug#1057782 marked as pending in gtk4

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1057782 [src:gtk4] gtk4: FTBFS on big-endian: memorytexture test fails
Ignoring request to alter tags of bug #1057782 to the same tags previously set

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



Bug#1057782: marked as pending in gtk4

2023-12-08 Thread Simon McVittie
Control: tag -1 pending

Hello,

Bug #1057782 in gtk4 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/gnome-team/gtk4/-/commit/668402a1181744dce17488b35ac20b8f56a6a698


Add proposed patch to fix test failure on big-endian CPUs

Closes: #1057782


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057782



Bug#1057671: marked as done (cytadela: game include non free graphical assets)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Dec 2023 18:00:13 +0100
with message-id <8f54c6ea-8072-4e0c-be48-a5ecd6c15...@beuc.net>
and subject line Re: Bug#1057671: cytadela: game include non free graphical 
assets
has caused the Debian Bug report #1057671,
regarding cytadela: game include non free graphical 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.)


-- 
1057671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cytadela
Version: 1.1.0-4+b1
Severity: serious
Justification: Policy 2.2.2.

Hi,

I'm currently reviewing all the games in contrib & non-free to see
wether game-data-packager can help to make them easier to install.


I'm surprised that cytadela is in contrib but doesn't try
to download anything and works from the go.

It should be either in "main" or in "non-free",
that just does not makes sense.


After digging out, I see that the graphical sprites
included upstream are a rip of from the original Amiga rom.

https://www.myabandonware.com/game/citadel-7ki
https://sourceforge.net/projects/cytadela/
https://sources.debian.org/src/cytadela/1.1.0-4/data/obj/

If this data-extraction were scriptable,
this engine would have to be stripped of the files
in data/obj/ and would then indeed perfectly fit in "contrib".

The game being mostly unmaintained I have little hope.

In the current state I think this package is
unfit for inclusion in Debian and should be removed.


Greetings,


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cytadela depends on:
ii  cytadela-data   1.1.0-4
ii  libc6   2.37-12
ii  libgcc-s1   13.2.0-7
ii  libgl1  1.7.0-1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libsdl-mixer1.2 1.2.12-17+b3
ii  libsdl1.2debian 1.2.68-1
ii  libstdc++6  13.2.0-7
ii  libvlc5 3.0.20-1+b1
ii  vlc-plugin-base 3.0.20-1+b1

cytadela recommends no packages.

cytadela suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Hi,

As explained yesterday, I believe the graphical assets are free as 
explained in upstream's website and in the copyright file.


Since the severity is serious and hence the package will be marked for 
unwarranted removal, I'm closing this bug without waiting further.


Cheers!
Sylvain--- End Message ---


Bug#1057815: debian-edu-artwork-emerald: modifies conffile: /etc/plymouth/plymouthd.conf

2023-12-08 Thread Andreas Beckmann
Package: debian-edu-artwork-emerald
Version: 2.12.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.12.3-2~deb12u1

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

/etc/plymouth/plymouthd.conf


Note that this bug is only easily reproducible in piuparts tests
with --install-recomends enabled. (It requires a certain combination of
packages (that are only linked via Recommends) to be installed
concurrently.)

This bug wasn't present in bookworm initially, but is now being
introduced via -pu.

This bug did not exist with pre-bookworm releases.

Since all other theme configuration is handled via alternatives, why
can't the same be done with plymouth? (It may require some packaging
changes on the plymouth side, though).


cheers,

Andreas


debian-edu-artwork-emerald_2.12.3-2.log.gz
Description: application/gzip


Processed: debian-edu-artwork-emerald: modifies conffile: /etc/plymouth/plymouthd.conf

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> found -1 2.12.3-2~deb12u1
Bug #1057815 [debian-edu-artwork-emerald] debian-edu-artwork-emerald: modifies 
conffile: /etc/plymouth/plymouthd.conf
Marked as found in versions debian-edu-artwork/2.12.3-2~deb12u1.

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



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

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 21:19:07 +
with message-id 
and subject line Bug#1042694: fixed in deap 1.3.1-5
has caused the Debian Bug report #1042694,
regarding deap: 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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> PYTHONPATH=/<>/../ sphinx-build -b html -d _build/doctrees   . 
> _build/html   
> Running Sphinx v7.1.1
> Matplotlib created a temporary config/cache directory at 
> /tmp/matplotlib-c6de1z4n because the default path 
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
> highly recommended to set the MPLCONFIGDIR environment variable to a writable 
> directory, in particular to speed up the import of Matplotlib and to better 
> support multiprocessing.
> making output directory... done
> WARNING: favicon file 'deap_orange_icon_32.ico' does not exist
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> loading intersphinx inventory from 
> http://docs.scipy.org/doc/numpy/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due 
> to : 
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
> http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
> proxy.', NewConnectionError(' 0x7f14fa232590>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.scipy.org/doc/numpy/objects.inv' not 
> fetchable due to : 
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
> http://docs.scipy.org/doc/numpy/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f14f9c11f10>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 43 source files that are out of date
> updating environment: [new config] 43 added, 0 changed, 0 removed
> reading sources... [  2%] about
> reading sources... [  5%] api/algo
> reading sources... [  7%] api/base
> reading sources... [  9%] api/benchmarks
> reading sources... [ 12%] api/creator
> reading sources... [ 14%] api/gp
> reading sources... [ 16%] api/index
> reading sources... [ 19%] api/tools
> reading sources... [ 21%] contributing
> reading sources... [ 23%] examples/bipop_cmaes
> WARNING: autodoc: failed to import module 'algorithms' from module 'deap'; 
> the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.eaSimple' from module 
> 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.eaMuPlusLambda' from 
> module 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.eaMuCommaLambda' from 
> module 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.eaGenerateUpdate' 
> from module 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.varAnd' from module 
> 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.varOr' from module 
> 'deap'; the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import module 'cma' from module 'deap'; the 
> following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import class 'cma.Strategy' from module 'deap'; 
> the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import class 'cma.StrategyOnePlusLambda' from 
> module 'deap'; the following exception was 

Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-08 Thread Fabio Fantoni

I tried to look on recent gobject-introspection changes

About muffin I tried to add "Provides: ${gir:Provides}" to -dev package 
but it didn't added anything, I tried after saw 
https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/d3611aaf3d8d98ca910b5f1e96f68a579538507f


I not understand what I should do about muffin as have only one packages 
with private gir, maintain one gir package will remain ok? I should add 
only a manual Provides in -dev package?


About cinnamon I saw that add this fixed the build:


override_dh_girepository:
dh_girepository --verbose /usr/lib/$(DEB_HOST_MULTIARCH)/muffin


from the build the output was:


dh_girepository --verbose /usr/lib/x86_64-linux-gnu/muffin
|
Package: cinnamon
||
Public GIR XML directory: debian/cinnamon/usr/share/gir-1.0
||
GIR XML: St-1.0.gir
||
Dependency: Clutter-0.gir
||
Dependency: ClutterX11-0.gir
||
Dependency: Gtk-3.0.gir
||
Dependency: Meta-0.gir
||
GIR XML: Cinnamon-0.1.gir
||
Dependency: CMenu-3.0.gir
||
Dependency: Clutter-0.gir
||
Dependency: ClutterX11-0.gir
||
Dependency: Cogl-0.gir
||
Dependency: CoglPango-0.gir
||
Dependency: Meta-0.gir
||
Dependency: St-1.0.gir
||
rm -f
||
cinnamon Provides gir1.2-st-1.0-dev (= 5.8.4-4~+salsaci+20231208+166)
||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
cinnamon Provides gir1.2-cinnamon-0.1-dev (= 
5.8.4-4~+salsaci+20231208+166)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Clutter-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Clutter-0.gir (version 
taken from libmuffin-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: ClutterX11-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for ClutterX11-0.gir (version 
taken from libmuffin-dev in B-D)

||
Dependency: Gtk-3.0.gir
||
Dependency: Gtk-3.0.gir
||
dh_girepository: warning: libgtk-3-dev should have Provides: 
gir1.2-gtk-3.0-dev (= ${binary:Version})

||
cinnamon Depends libgtk-3-dev (>= 3.9.12) for Gtk-3.0.gir (version 
taken from libgtk-3-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Meta-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Meta-0.gir (version taken 
from libmuffin-dev in B-D)

||
Dependency: CMenu-3.0.gir
||
Dependency: CMenu-3.0.gir
||
dh_girepository: warning: libcinnamon-menu-3-dev should have Provides: 
gir1.2-cmenu-3.0-dev (= ${binary:Version})

||
cinnamon Depends libcinnamon-menu-3-dev (>= 5.4~) for CMenu-3.0.gir 
(version taken from libcinnamon-menu-3-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Cogl-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Cogl-0.gir (version taken 
from libmuffin-dev in B-D)

||
Dependency: CoglPango-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for CoglPango-0.gir (version 
taken from libmuffin-dev in B-D)

||
Dependency: St-1.0.gir
||
found in the same package
||
Package: cinnamon-common
||
rm -f
||
Package: cinnamon-doc
||rm -f|
and seems it should add some -dev packages as cinnamon deps that I think 
not good, I suppose I should create a new package instead like 
gir1.2-cinnamon-0.1-dev, or I'm wrong?


on cinnamon full -dev package is not needed but only gir files for few 
cases (only developer I think) can be useful so was added in cinnamon 
package


anyway when I tried to look artifact 
(https://salsa.debian.org/cinnamon-team/cinnamon/-/commit/c74a32e74374e5c61e7546c2f28a6a858e2f6999/pipelines?ref=master) 
cinnamon packages don't have -dev deps wrote by dh_girepository, is it 
correct?


thanks for any reply



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057471: marked as done (new upstream version required for Python 3.11/3.12)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 20:27:16 +
with message-id 
and subject line Bug#1057471: fixed in zope.event 5.0-0.1
has caused the Debian Bug report #1057471,
regarding new upstream version required for Python 3.11/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.)


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

Package: src:zope.event
Version: 4.4-3
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

A new upstream version required for Python 3.11/3.12


==
 ``zope.event`` Changelog
==

5.0 (2023-06-23)


- Drop support for Python 2.7, 3.5, 3.6.


4.6 (2022-12-15)


- Port documentation to Python 3.

- Add support for Python 3.10, 3.11.
--- End Message ---
--- Begin Message ---
Source: zope.event
Source-Version: 5.0-0.1
Done: Matthias Klose 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Dec 2023 20:42:21 +0100
Source: zope.event
Architecture: source
Version: 5.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lenharo de Souza 
Changed-By: Matthias Klose 
Closes: 1057471
Changes:
 zope.event (5.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #1057471.
   * Test package with zope.testrunner.
   * Bump standards version.
Checksums-Sha1:
 795d5782f65e6d0faa4b2f2dad036ddc4febcb0e 1995 zope.event_5.0-0.1.dsc
 e63bf059a157f6edd8ff8beb58c20508799148ac 17350 zope.event_5.0.orig.tar.gz
 6cf3dfebfaae60d7934b96b991ba758aebd479f5 4416 zope.event_5.0-0.1.debian.tar.xz
 ad35571a6d26906f44052b0b29668dfa8e245d75 6847 
zope.event_5.0-0.1_source.buildinfo
Checksums-Sha256:
 6ae81a3665b0263ba38e835de6029222e3b2999d0624bb613e43ee79e24637e1 1995 
zope.event_5.0-0.1.dsc
 bac440d8d9891b4068e2b5a2c5e2c9765a9df762944bda6955f96bb9b91e67cd 17350 
zope.event_5.0.orig.tar.gz
 220294df038c73dc47d4d48680fe54210ba473f1d456b77a9d3b7b03020993a3 4416 
zope.event_5.0-0.1.debian.tar.xz
 3c46312a47adfd16108272fa516fdaffd7132e4c0afa96c1d0fcf130993508d6 6847 
zope.event_5.0-0.1_source.buildinfo
Files:
 1453e51b3c3f644dc169dfacef0d0eaa 1995 python optional zope.event_5.0-0.1.dsc
 8639012f7c6a762d245f9229a6e900af 17350 python optional 
zope.event_5.0.orig.tar.gz
 fbdeec49b77a5f1324cf00b4016102a7 4416 python optional 
zope.event_5.0-0.1.debian.tar.xz
 bb249c8495ac9b6a53d1af37f26b6ae0 6847 python optional 
zope.event_5.0-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmVzcuQQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9X2CD/4sq2IBKZhTA/ria70RA4s55NUNTWkn70os
5ze47W0TXDcx2d4qUKJ75J2uTyNfu+Fn8XdtcPtN40NNpLamwUz5asdvRtu5nGwE
Di0/uR62ZdCgfnFpjA0QUnkEHoRWDx2KqQV60h+GUMLHm9g2NoTtQq15s4AV+1i+
k+2lslOyiH0uSXIGSpmmMw2zgK5eKyP9SvDq7fN6x8yVVaM2QXzsW5DVOOEHmLxE
62Tpr0H4snApIpG+4xuIQEjGNt0KPec0KleLC/VrgeeNQVIuaDPmO5Y1eTt9IA8S
n6n/nJT6LGcSiv4mnthBVwjL/R5iFwtAzqjhV3bMxhHLGd7dd8PVeCYoFQ/Hk8vA
IZiVPcbFWLbv73yod27aJHMslzVg24EgI8WrOOeKV2GSrY4RTuejOwBQLNU5uSp8
ZAmhU8ZMQUlKwcMRvBAnbSNKUVJCeTkfK2VK2pq9w5yUZmebwCWccrZJToDzQW5V
MisfiBqbQztmMz2OKexI6sp9J4P8GYDKmF8QoBduOhnB7u1XIZjX7TfVALE5bVS+
uRB+ksFpvhClOPxKndNXHgNre0w4xhZ7kOsE1ARLWifiqKoe699azBbwJdG1zei7
JD7YPqVTt46Dnlp/431bXFCkBeqwnLfZOgQi7WNBndIKAzAXKwqVKwNpv9epeTNF
YXAurdVXKw==
=PWSs
-END PGP SIGNATURE End Message ---


Bug#1050580: ruby-roxml: broken by ruby-nokogiri 1.15.4

2023-12-08 Thread Lucas Kanashiro
Upstream is not active for some years (last commit from more than 2 
years ago), I do not expect them to fix this. I was checking the reverse 
dependencies and it seems there isn't any, I believe we should remove 
this package also from unstable (it was already removed from testing).


--
Lucas Kanashiro



Bug#1042290: closing 1042290

2023-12-08 Thread Roland Mas
close 1042290 0.12.3-2
thanks



Processed: close 1057436

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1057436 23.09.0-2
Bug #1057436 [src:ovn] ovn: FTBFS: tar (child): 
/usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such file or directory
The source 'ovn' and version '23.09.0-2' do not appear to match any binary 
packages
Marked as fixed in versions ovn/23.09.0-2.
Bug #1057436 [src:ovn] ovn: FTBFS: tar (child): 
/usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such file or directory
Marked Bug as done
>
End of message, stopping processing here.

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



Processed: Re: Bug#1056980: [devuan-dev] bug#813: Reopen 1056980

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #1056980 [netcat-traditional] netcat-traditional: upgrade to 1.10-48 fails 
(postinst script)
Severity set to 'normal' from 'serious'
> tags -1 = wontfix
Bug #1056980 [netcat-traditional] netcat-traditional: upgrade to 1.10-48 fails 
(postinst script)
Removed tag(s) patch.

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



Bug#1056980: [devuan-dev] bug#813: Reopen 1056980

2023-12-08 Thread Chris Hofstaedtler
Control: severity -1 normal
Control: tags -1 = wontfix

* Svante Signell  [231208 19:38]:
> On Fri, 2023-12-08 at 16:15 +0100, Svante Signell wrote:
> > reopen 1056980
> > severity 1056980 serious
> > tags 1056980 patch
> > thanks
> 
> Sorry, forgot the patch!
> 

> --- a/debian/netcat-traditional.postinst  2023-11-27 03:20:27.0 
> +0100
> +++ b/debian/netcat-traditional.postinst  2023-12-04 15:11:31.0 
> +0100
> @@ -4,8 +4,8 @@
>  
>  if [ "$1" = "configure" ]; then
>  update-alternatives \
> ---install /bin/nc nc /bin/nc.traditional 10 \
> ---slave /bin/netcat netcat /bin/nc.traditional \
> +--install /usr/bin/nc nc /usr/bin/nc.traditional 10 \
> +--slave /usr/bin/netcat netcat /usr/bin/nc.traditional \
>  --slave /usr/share/man/man1/nc.1.gz nc.1.gz \
>  /usr/share/man/man1/nc.traditional.1.gz \
>  --slave /usr/share/man/man1/netcat.1.gz netcat.1.gz \

This is absolutely wrong on Debian, and must not be uploaded to
Debian.

If you want to keep it as a Devuan delta, go ahead.

Chris



Processed: fixed 1042290 in 0.12.3-2

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 1042290 0.12.3-2
Bug #1042290 [src:jupyter-packaging] jupyter-packaging: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit 
code 13
Ignoring request to alter fixed versions of bug #1042290 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: closing 1042290

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1042290 0.12.3-2
Bug #1042290 [src:jupyter-packaging] jupyter-packaging: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit 
code 13
Ignoring request to alter fixed versions of bug #1042290 to the same values 
previously set
Bug #1042290 [src:jupyter-packaging] jupyter-packaging: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit 
code 13
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1057660: marked as done (fastdtw: autopkgtest failure)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 19:34:05 +
with message-id 
and subject line Bug#1057660: fixed in fastdtw 0.3.4-3
has caused the Debian Bug report #1057660,
regarding fastdtw: autopkgtest failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fastdtw
Version: 0.3.4-2
Severity: serious

https://tracker.debian.org/pkg/fastdtw

Issues preventing migration:
∙ ∙ autopkgtest for fastdtw/0.3.4-2: amd64: Regression ♻ , arm64: Regression ♻ 
, armel: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: 
Regression ♻ , s390x: Regression ♻

...
48s autopkgtest [15:11:13]: test pybuild-autopkgtest: pybuild-autopkgtest
 48s autopkgtest [15:11:13]: test pybuild-autopkgtest: [---
 48s pybuild-autopkgtest
 49s I: pybuild base:310: python3.11 setup.py test 
 49s /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
Cython directive 'language_level' not set, using 2 for now (Py2). This will 
change in a later release! File: 
/tmp/autopkgtest-lxc.nv65t9ym/downtmp/build.LqL/src/fastdtw/_fastdtw.pyx
 49s   tree = Parsing.p_module(s, pxd, full_module_name)
 49s Compiling fastdtw/_fastdtw.pyx because it depends on 
/usr/lib/python3/dist-packages/Cython/Includes/numpy/math.pxd.
 49s [1/1] Cythonizing fastdtw/_fastdtw.pyx
 49s /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
_DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
 49s !!
 49s 
 49s 

 49s Requirements should be satisfied by a PEP 517 installer.
 49s If you are using pip, you can try `pip install --use-pep517`.
 49s 

 49s 
 49s !!
 49s   dist.fetch_build_eggs(dist.setup_requires)
 50s WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 50s WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 51s WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 53s WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 57s WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 57s ERROR: Could not find a version that satisfies the requirement 
pytest-runner (from versions: none)
 57s ERROR: No matching distribution found for pytest-runner
 57s Traceback (most recent call last):
 57s   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 101, 
in _fetch_build_egg_no_warn
 57s subprocess.check_call(cmd)
 57s   File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
 57s raise CalledProcessError(retcode, cmd)
 57s subprocess.CalledProcessError: Command '['/usr/bin/python3.11', '-m', 
'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
'/tmp/tmpx6wpjq2f', '--quiet', 'pytest-runner']' returned non-zero exit status 
1.
 57s 
 57s The above exception was the direct cause of the following exception:
 57s 
 57s Traceback (most recent call last):
 57s   File "/tmp/autopkgtest-lxc.nv65t9ym/downtmp/build.LqL/src/setup.py", 
line 81, in 
 57s setup(**kwargs)
 57s   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 106, 
in setup
 57s _install_setup_requires(attrs)
 57s   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 79, 
in _install_setup_requires
 57s 

Processed: Re: Bug#1055801: pandas: test failures with Python 3.12

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #1055801 [python3-pandas] pandas: test failures with Python 3.12
Severity set to 'normal' from 'serious'
> retitle -1 pandas/pytables: ignored test fails with Python 3.12
Bug #1055801 [python3-pandas] pandas: test failures with Python 3.12
Changed Bug title to 'pandas/pytables: ignored test fails with Python 3.12' 
from 'pandas: test failures with Python 3.12'.
> found -1 2.1.3+dfsg-1
Bug #1055801 [python3-pandas] pandas/pytables: ignored test fails with Python 
3.12
Marked as found in versions pandas/2.1.3+dfsg-1.
> tags 1057805 pending
Bug #1057805 [src:pandas] pandas ftbfs on at least armhf
Added tag(s) pending.

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



Bug#1055801: pandas: test failures with Python 3.12

2023-12-08 Thread Rebecca N. Palmer

Control: severity -1 normal
Control: retitle -1 pandas/pytables: ignored test fails with Python 3.12
Control: found -1 2.1.3+dfsg-1
Control: tags 1057805 pending

In 1.5.3+dfsg-8, these are ignored, so are no longer an FTBFS but are 
still a bug.  I don't know whether they're a pandas bug or a pytables 
bug; they don't appear to be known to either upstream.


(The build failure on armhf, #1057805, was because this xfail took 
precedence over the existing run=False xfail and hence exposed a 
long-known crash, #790925.  This should be fixed in -9.)


If the 'affects' is because you were trying to test those reverse 
dependencies in Python 3.12, this should now be possible.




Bug#1057436: ovn: FTBFS: tar (child): /usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such file or directory

2023-12-08 Thread Frode Nordahl
Hello, Chris,

Thank you for reporting this bug.

To resolve a reproducible build issue with the openvswitch package we
had to change the layout of the openvswitch-source package [0].

The necessary changes were proposed to the ovn package simultaneously [1].

Unfortunately these two package changes were uploaded at a different
point in time, allowing for this window of FTBFS for the ovn package.

The ovn change has just been uploaded and should be available as soon
as the build farms have completed building it.

0: 
https://salsa.debian.org/openstack-team/third-party/openvswitch/-/commit/b7c390f39fcc35b05365f021812b3aaba76b7210
1: 
https://salsa.debian.org/openstack-team/third-party/ovn/-/commit/1d71b47c7f4c94f63ac944df0c097e17bb0cc565

-- 
Frode Nordahl



Bug#1057809: python-pysam ftbfs with Python 3.12

2023-12-08 Thread Andreas Tille
Control: tags -1 upstream
Control: forwarded -1 https://github.com/biopython/biopython/issues/4532

-- 
http://fam-tille.de



Processed: Re: Bug#1057809: python-pysam ftbfs with Python 3.12

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 upstream
Bug #1057809 [src:python-pysam] python-pysam ftbfs with Python 3.12
Added tag(s) upstream.
> forwarded -1 https://github.com/biopython/biopython/issues/4532
Bug #1057809 [src:python-pysam] python-pysam ftbfs with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/biopython/biopython/issues/4532'.

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



Bug#1042595: marked as done (python-gevent: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 19:19:35 +
with message-id 
and subject line Bug#1042595: fixed in python-gevent 23.9.1-0.2
has caused the Debian Bug report #1042595,
regarding python-gevent: 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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> /usr/share/sphinx/scripts/python3/sphinx-build -b html -d _build/doctrees   . 
> _build/html
> Running Sphinx v7.1.1
> making output directory... done
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('http://docs.python.org/', 
> '../debian/python.inv')}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://greenlet.readthedocs.io/en/latest/', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://zopeevent.readthedocs.io/en/latest/', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://zopecomponent.readthedocs.io/en/latest/', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> loading intersphinx inventory from ../debian/python.inv...
> loading intersphinx inventory from 
> https://greenlet.readthedocs.io/en/latest/objects.inv...
> loading intersphinx inventory from 
> https://zopeevent.readthedocs.io/en/latest/objects.inv...
> loading intersphinx inventory from 
> https://zopecomponent.readthedocs.io/en/latest/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 95 source files that are out of date
> updating environment: [new config] 95 added, 0 changed, 0 removed
> reading sources... [  1%] _about
> reading sources... [  2%] api/gevent
> reading sources... [  3%] api/gevent._socket2
> reading sources... [  4%] api/gevent._socket3
> reading sources... [  5%] api/gevent._ssl2
> reading sources... [  6%] api/gevent._ssl3
> reading sources... [  7%] api/gevent._sslgte279
> reading sources... [  8%] api/gevent.ares
> reading sources... [  9%] api/gevent.backdoor
> reading sources... [ 11%] api/gevent.baseserver
> reading sources... [ 12%] api/gevent.builtins
> reading sources... [ 13%] api/gevent.contextvars
> reading sources... [ 14%] api/gevent.core
> reading sources... [ 15%] api/gevent.event
> /usr/lib/python3.11/ssl.py:docstring of ssl.SSLCertVerificationError:1: 
> WARNING: duplicate object description of ssl.SSLCertVerificationError, other 
> instance in api/gevent._ssl2, use :noindex: for one of them
> /usr/lib/python3.11/ssl.py:docstring of ssl.SSLEOFError:1: WARNING: duplicate 
> object description of ssl.SSLEOFError, other instance in api/gevent._ssl2, 
> use :noindex: for one of them
> /usr/lib/python3.11/ssl.py:docstring of ssl.SSLError:1: WARNING: duplicate 
> object description of ssl.SSLError, other instance in api/gevent._ssl2, use 
> :noindex: for one of them
> /usr/lib/python3.11/ssl.py:docstring of ssl.SSLSyscallError:1: WARNING: 
> duplicate object description of ssl.SSLSyscallError, other instance in 
> api/gevent._ssl2, use :noindex: for one of them
> /usr/lib/python3.11/ssl.py:docstring of 

Bug#1057809: python-pysam ftbfs with Python 3.12

2023-12-08 Thread Matthias Klose

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

python-pysam ftbfs with Python 3.12, didn't check for any follow-up errors:

[...]
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/pysam -I/usr/include -I/<>/samtools 
-I/<>/samtools/lz4 -I/<>/bcftools 
-I/<> -I/usr/include/python3.12 -c pysam/libchtslib.c -o 
build/temp.linux-x86_64-cpython-312/pysam/libchtslib.o -Wno-unused 
-Wno-strict-prototypes -Wno-sign-compare 
-Wno-error=declaration-after-statement

pysam/libchtslib.c: In function ‘__pyx_f_5pysam_10libchtslib_set_verbosity’:
pysam/libchtslib.c:1387:32: error: ‘_PyCFrame’ has no member named 
‘use_tracing’

 1387 |  (unlikely((tstate)->cframe->use_tracing) &&\
  |^~
pysam/libchtslib.c:958:43: note: in definition of macro ‘unlikely’
  958 |   #define unlikely(x) __builtin_expect(!!(x), 0)
  |   ^
pysam/libchtslib.c:1426:15: note: in expansion of macro ‘__Pyx_IsTracing’
 1426 |   if (__Pyx_IsTracing(tstate, 1, 1)) {\
  |   ^~~



Processed: Bug#1042595 marked as pending in python-gevent

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1042595 [src:python-gevent] python-gevent: FTBFS with Sphinx 7.1, docutils 
0.20: TypeError: not all arguments converted during string formatting
Added tag(s) pending.

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



Bug#1042595: marked as pending in python-gevent

2023-12-08 Thread Matthias Klose
Control: tag -1 pending

Hello,

Bug #1042595 in python-gevent 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-gevent/-/commit/ab0a3b88102407029bd7ffb579c23e9bf3fd9089


* Non-maintainer upload.
  * New upstream version.
- Fixes build with recent sphinx version. Closes: #1042595.
  * Build-depend on furo.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042595



Bug#1054860: marked as done (haskell-tree-monad: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 18:36:34 +
with message-id 
and subject line Bug#1057723: Removed package(s) from unstable
has caused the Debian Bug report #1054860,
regarding haskell-tree-monad: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tree-monad
Version: 0.3.2-1
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):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-tree-monad-doc.substvars
> dh_installdirs -plibghc-tree-monad-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/I_ZmLcz5xc -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-tree-monad-dev
> libghc-tree-monad-prof
> libghc-tree-monad-doc
> Running dh_listpackages
> libghc-tree-monad-dev
> libghc-tree-monad-prof
> libghc-tree-monad-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/tree-monad-0.3.2/ 
> --datasubdir=tree-monad --htmldir=/usr/share/doc/libghc-tree-monad-doc/html/ 
> --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring tree-monad-0.3.2...
> CallStack (from HasCallStack):
>   withMetadata, called at 
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in 
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Encountered missing or private dependencies:
> base >=4.13 && <4.16.3
> 
>  at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
>   Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] 
> Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-tree-monad_0.3.2-1_unstable.log

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

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.3.2-1+rm

Dear submitter,

as the package haskell-tree-monad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry

Bug#1054353: marked as done (Removal notice: obsolete)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 18:36:34 +
with message-id 
and subject line Bug#1057723: Removed package(s) from unstable
has caused the Debian Bug report #1054353,
regarding Removal notice: obsolete
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.)


-- 
1054353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tree-monad
Version: 0.3.2-1
Severity: serious

I intend to remove this package:

  * The current version FTBFS
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.3.2-1+rm

Dear submitter,

as the package haskell-tree-monad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1057723

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---


Processed: user debian...@lists.debian.org, usertagging 1054944, affects 1054944, usertagging 1054863 ...

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1054944 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054944 + libghc-gitit-dev libghc-gitit-doc
Bug #1054944 [src:gitit] 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), libghc-pandoc-dev (< 
2.18), libghc-pandoc-prof, libghc-pandoc-types-dev (< 1.23), 
libghc-skylighting-dev (< 0.13), libghc-pandoc-doc
Added indication that 1054944 affects libghc-gitit-dev and libghc-gitit-doc
> usertags 1054863 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054863 + libghc-hsyaml-dev
Bug #1054863 [src:haskell-hsyaml] haskell-hsyaml: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
Added indication that 1054863 affects libghc-hsyaml-dev
> usertags 1054947 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054947 + libghc-ircbot-dev
Bug #1054947 [src:haskell-ircbot] haskell-ircbot: FTBFS: unsatisfiable 
build-dependency: libghc-optparse-applicative-dev (< 0.17) but 0.17.1.0-1+b1 is 
to be installed
Added indication that 1054947 affects libghc-ircbot-dev
> usertags 1054865 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054865 + libghc-reform-hsp-dev
Bug #1054865 [src:haskell-reform-hsp] haskell-reform-hsp: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
Added indication that 1054865 affects libghc-reform-hsp-dev
> usertags 1054865 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 1054865 + libghc-tidal-dev
Bug #1054865 [src:haskell-reform-hsp] haskell-reform-hsp: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
Added indication that 1054865 affects libghc-tidal-dev
> usertags 1054860 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054860 + libghc-tree-monad-dev
Bug #1054860 [src:haskell-tree-monad] haskell-tree-monad: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
Added indication that 1054860 affects libghc-tree-monad-dev
> usertags 1054977 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054977 + libghc-userid-dev
Bug #1054977 [src:haskell-userid] haskell-userid: FTBFS: unsatisfiable 
build-dependency: libghc-aeson-dev (< 2.1) but 2.1.2.1-5 is to be installed
Added indication that 1054977 affects libghc-userid-dev
> usertags 1057056 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1057056 + librust-comrak-dev
Bug #1057056 [src:rust-comrak] rust-comrak: Unsatisfiable dependency on 
rust-emojis
Added indication that 1057056 affects librust-comrak-dev
> usertags 1054722 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054722 + librust-matchers-dev
Bug #1054722 [src:rust-matchers] rust-matchers: FTBFS: build-dependency not 
installable: librust-regex-automata-0.1+default-dev
Added indication that 1054722 affects librust-matchers-dev
> usertags 1051615 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1051615 + librust-minijinja-dev
Bug #1051615 [src:rust-minijinja] rust-minijinja: Uninstallable dependencies
Added indication that 1051615 affects librust-minijinja-dev
> usertags 1056177 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051615
1054722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054722
1054860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054860
1054863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054863
1054865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054865
1054944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054944
1054947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054947
1054977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054977
1056177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056177
1057056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1057805: pandas ftbfs on at least armhf

2023-12-08 Thread Matthias Klose

Package: src:pandas
Version: 1.5.3+dfsg-7
Severity: serious
Tags: sid trixie

these fail on armhf (but succeeding on armel), and on some ports 
architectures.  If I'm reading correctly, these fail with Python 3.11, 
but not Python 3.12.


[...]
=== short test summary info 

FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data1-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data5-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data5-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data6-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data6-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data7-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data7-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data11-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data15-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data15-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data16-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data16-2-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data17-0-sum]
FAILED 
pandas/tests/window/moments/test_moments_consistency_expanding.py::test_expanding_apply_consistency_sum_nans[all_data17-2-sum]
= 14 failed, 469 passed, 834 skipped, 550 deselected in 45.94s 
=




Bug#1057799: systemd: fails to configure

2023-12-08 Thread Michael Biebl

Am 08.12.23 um 18:48 schrieb Michael Biebl:

On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote:

Package: systemd
Version: 252.19-1~deb12u1
Severity: serious
Tags: d-i
Justification: normal

Dear Maintainer,

I get a problem upgrading the system, systemd fails to configure :

sudo dpkg --configure systemd
Setting up systemd (252.19-1~deb12u1) ...
Creating group 'users' with GID 100.
/etc/gshadow: Group "users" already exists.


Can you attach the output of

sudo grep users /etc/group /etc/gshadow



The output of

sudo SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/basic.conf

as well, please


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057799: systemd: fails to configure

2023-12-08 Thread Michael Biebl

On Fri, 08 Dec 2023 17:30:23 +0100 JPP  wrote:

Package: systemd
Version: 252.19-1~deb12u1
Severity: serious
Tags: d-i
Justification: normal

Dear Maintainer,

I get a problem upgrading the system, systemd fails to configure :

sudo dpkg --configure systemd
Setting up systemd (252.19-1~deb12u1) ...
Creating group 'users' with GID 100.
/etc/gshadow: Group "users" already exists.


Can you attach the output of

sudo grep users /etc/group /etc/gshadow



OpenPGP_signature.asc
Description: OpenPGP digital signature


Processed: bug 1057782 is forwarded to https://gitlab.gnome.org/GNOME/gtk/-/issues/6260, tagging 1057782

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1057782 https://gitlab.gnome.org/GNOME/gtk/-/issues/6260
Bug #1057782 [src:gtk4] gtk4: FTBFS on big-endian: memorytexture test fails
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gtk/-/issues/6260'.
> tags 1057782 + upstream patch pending
Bug #1057782 [src:gtk4] gtk4: FTBFS on big-endian: memorytexture test fails
Added tag(s) upstream, pending, and patch.
> thanks
Stopping processing here.

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



Bug#1057802: libgetdata ftbfs when building binary-indep packages only

2023-12-08 Thread Matthias Klose

Package: src:libgetdata
Version: 0.11.0-8
Severity: serious
Tags: sid trixie

libgetdata ftbfs when building binary-indep packages only:

[...]
   dh_missing -i
dh_missing: warning: 
usr/local/lib/python3.11/dist-packages/pygetdata.cpython-311-x86_64-linux-gnu.so 
exists in debian/tmp but is not installed to anywhere
dh_missing: warning: 
usr/local/lib/python3.12/dist-packages/pygetdata.cpython-312-x86_64-linux-gnu.so 
exists in debian/tmp but is not installed to anywhere

dh_missing: error: missing files, aborting



Bug#984100: libdjconsole: diff for NMU version 0.1.3-3.1

2023-12-08 Thread Chris Hofstaedtler
Control: tags 984100 + patch
Control: tags 984100 + pending

Dear maintainer,

I've prepared an NMU for libdjconsole (versioned as 0.1.3-3.1) and
uploaded it to DELAYED/7.
Feel free to upload a fix in the meantime or cancel the NMU.

Best,
Chris
diff -Nru libdjconsole-0.1.3/debian/changelog libdjconsole-0.1.3/debian/changelog
--- libdjconsole-0.1.3/debian/changelog	2015-12-16 17:14:43.0 +0100
+++ libdjconsole-0.1.3/debian/changelog	2023-12-08 17:37:04.0 +0100
@@ -1,3 +1,13 @@
+libdjconsole (0.1.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use pkg-config to place udev rules file.
+  * Fix FTBFS by correcting usb_open retval check (Closes: #984100)
+  * Bump to dh compat level 13, away from obsolete level 9.
+Record not installed files in debian/not-installed.
+
+ -- Chris Hofstaedtler   Fri, 08 Dec 2023 17:37:04 +0100
+
 libdjconsole (0.1.3-3) unstable; urgency=medium
 
   * Don't use /usr/share/doc/ symlinks anymore to keep things simple and
diff -Nru libdjconsole-0.1.3/debian/compat libdjconsole-0.1.3/debian/compat
--- libdjconsole-0.1.3/debian/compat	2015-08-28 16:32:22.0 +0200
+++ libdjconsole-0.1.3/debian/compat	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-9
diff -Nru libdjconsole-0.1.3/debian/control libdjconsole-0.1.3/debian/control
--- libdjconsole-0.1.3/debian/control	2015-08-28 16:32:22.0 +0200
+++ libdjconsole-0.1.3/debian/control	2023-12-08 17:37:04.0 +0100
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Adrien Cunin 
-Build-Depends: debhelper (>= 9), dh-autoreconf, pkg-config, libusb-dev
+Build-Depends: debhelper-compat (= 13), pkgconf, libusb-dev, systemd-dev
 Standards-Version: 3.9.6
 Homepage: http://djplay.sourceforge.net/
 
diff -Nru libdjconsole-0.1.3/debian/libdjconsole-data.install libdjconsole-0.1.3/debian/libdjconsole-data.install
--- libdjconsole-0.1.3/debian/libdjconsole-data.install	2015-08-28 16:32:22.0 +0200
+++ libdjconsole-0.1.3/debian/libdjconsole-data.install	2023-12-08 17:37:04.0 +0100
@@ -1,2 +1,2 @@
 debian/tmp/usr/share/
-debian/tmp/lib/udev/rules.d/
+debian/tmp/${env:deb_udevdir}
diff -Nru libdjconsole-0.1.3/debian/not-installed libdjconsole-0.1.3/debian/not-installed
--- libdjconsole-0.1.3/debian/not-installed	1970-01-01 01:00:00.0 +0100
+++ libdjconsole-0.1.3/debian/not-installed	2023-12-08 17:37:04.0 +0100
@@ -0,0 +1 @@
+usr/lib/*/libdjconsole.la
diff -Nru libdjconsole-0.1.3/debian/patches/01_install_udev_rules_lib.patch libdjconsole-0.1.3/debian/patches/01_install_udev_rules_lib.patch
--- libdjconsole-0.1.3/debian/patches/01_install_udev_rules_lib.patch	2015-08-28 16:32:22.0 +0200
+++ libdjconsole-0.1.3/debian/patches/01_install_udev_rules_lib.patch	2023-12-08 17:37:04.0 +0100
@@ -7,7 +7,7 @@
  AUTOMAKE_OPTIONS = gnu
  pkgconfigdir=$(libdir)/pkgconfig
 -rulesdir=$(sysconfdir)/udev/rules.d
-+rulesdir=/lib/udev/rules.d
++rulesdir=$(shell pkg-config --variable=udevdir udev)/rules.d
  
  lib_LTLIBRARIES = libdjconsole.la
  
@@ -18,7 +18,7 @@
  AUTOMAKE_OPTIONS = gnu
  pkgconfigdir = $(libdir)/pkgconfig
 -rulesdir = $(sysconfdir)/udev/rules.d
-+rulesdir = /lib/udev/rules.d
++rulesdir=$(shell pkg-config --variable=udevdir udev)/rules.d
  
  lib_LTLIBRARIES = libdjconsole.la
  
diff -Nru libdjconsole-0.1.3/debian/patches/04_usb_open_retval.patch libdjconsole-0.1.3/debian/patches/04_usb_open_retval.patch
--- libdjconsole-0.1.3/debian/patches/04_usb_open_retval.patch	1970-01-01 01:00:00.0 +0100
+++ libdjconsole-0.1.3/debian/patches/04_usb_open_retval.patch	2023-12-08 17:37:04.0 +0100
@@ -0,0 +1,22 @@
+Index: libdjconsole-0.1.3/djconsole.cpp
+===
+--- libdjconsole-0.1.3.orig/djconsole.cpp
 libdjconsole-0.1.3/djconsole.cpp
+@@ -107,7 +107,7 @@ DJConsole::DJConsole(bool load_data)
+ 
+ 	hdev1=usb_open(dev);
+ 
+-	if(hdev1 < 0)
++	if(hdev1 == nullptr)
+ 	{
+ 		printf("Error opening DJ Console device, check permissions\n");
+ 		return;
+@@ -115,7 +115,7 @@ DJConsole::DJConsole(bool load_data)
+ 
+ 	hdev2=usb_open(dev);
+ 
+-	if(hdev2 < 0)
++	if(hdev2 == nullptr)
+ 	{
+ 		printf("Error opening DJ Console device, check permissions\n");
+ 		return;
diff -Nru libdjconsole-0.1.3/debian/patches/series libdjconsole-0.1.3/debian/patches/series
--- libdjconsole-0.1.3/debian/patches/series	2015-08-28 16:32:22.0 +0200
+++ libdjconsole-0.1.3/debian/patches/series	2023-12-08 17:37:04.0 +0100
@@ -1,3 +1,4 @@
 01_install_udev_rules_lib.patch
 02_udev_rules_sysfs_attr.patch
 03_update_pc_file.patch
+04_usb_open_retval.patch
diff -Nru libdjconsole-0.1.3/debian/rules libdjconsole-0.1.3/debian/rules
--- libdjconsole-0.1.3/debian/rules	2015-12-16 17:14:43.0 +0100
+++ libdjconsole-0.1.3/debian/rules	2023-12-08 17:37:04.0 +0100
@@ -1,3 +1,5 @@
 #!/usr/bin/make -f
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 %:
-	dh $@ 

Processed: libdjconsole: diff for NMU version 0.1.3-3.1

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tags 984100 + patch
Bug #984100 [src:libdjconsole] libdjconsole: ftbfs with GCC-11
Added tag(s) patch.
> tags 984100 + pending
Bug #984100 [src:libdjconsole] libdjconsole: ftbfs with GCC-11
Added tag(s) pending.

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



Processed: reopening 1054737

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 1054737
Bug #1054737 {Done: Alastair McKinstry } 
[src:ruby-pry-byebug] ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.1" failed: 
:86:in 
`require': cannot load such file -- pry-byebug (LoadError)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pmix/5.0.1-4.
> thanks
Stopping processing here.

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



Processed: affects 1057737

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 1057737 src:pyresample
Bug #1057737 [src:python-cartopy] python-cartopy: FTBFS with Python 3.12
Added indication that 1057737 affects src:pyresample
> 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#1057799: systemd: fails to configure

2023-12-08 Thread JPP
Package: systemd
Version: 252.19-1~deb12u1
Severity: serious
Tags: d-i
Justification: normal

Dear Maintainer,

I get a problem upgrading the system, systemd fails to configure :

sudo dpkg --configure systemd
Setting up systemd (252.19-1~deb12u1) ...
Creating group 'users' with GID 100.
/etc/gshadow: Group "users" already exists.
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 systemd


-- Package-specific info:

-- System Information:
Debian Release: 12.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9+deb12u3
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u1
ii  libfdisk1  2.38.1-5+b1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+b1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.19-1~deb12u1
ii  libsystemd0252.19-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+b1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  ntpsec [time-daemon]1.2.2+dfsg1-1+deb12u1

Versions of packages systemd suggests:
ii  libfido2-11.12.0-2+b1
ii  libqrencode4  4.1.1-1
ii  libtss2-esys-3.0.2-0  3.2.1-3
ii  libtss2-mu0   3.2.1-3
pn  libtss2-rc0   
ii  policykit-1   122-3
ii  polkitd   122-3
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-1~deb12u1
pn  dracut 
ii  initramfs-tools0.142
iu  libnss-systemd 252.19-1~deb12u1
iu  libpam-systemd 252.19-1~deb12u1
ii  udev   252.19-1~deb12u1

-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
DefaultTimeoutStopSec=30s
DefaultDeviceTimeoutSec=20s

/etc/systemd/user.conf changed:
[Manager]
DefaultTimeoutStopSec=30s
DefaultRestartSec=100ms


-- no debconf information



Processed: Bug#1057766 marked as pending in phosh

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1057766 [phosh] Osk button missing after startup
Added tag(s) pending.

-- 
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-08 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#1057437: marked as done (pmix: FTBFS: dh_missing: error: missing files, aborting)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Dec 2023 16:04:46 +
with message-id <8367f760-efe7-4b4a-9b72-4fcb96108...@mckinstry.ie>
and subject line Closing
has caused the Debian Bug report #1057437,
regarding pmix: FTBFS: dh_missing: error: missing files, aborting
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.)


-- 
1057437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmix
Version: 5.0.1-3
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in unstable, in my own test rebuild as well as on 
reproducible-builds.org.

Build log snippet, hopefully relevant:
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cygdb exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cython exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cythonize 
exists in debian/tmp but is not installed to anywhere 
   dh_missing: error: missing files, aborting
  The following debhelper tools have reported what they installed (with 
files per package)
  * dh_install: libpmix-bin (9), libpmix-dev (4), libpmix2 (35), 
python3-pmix (1)
  * dh_installdocs: libpmix-bin (0), libpmix-dev (3), libpmix2 (0), 
python3-pmix (0)
  * dh_installexamples: libpmix-bin (0), libpmix-dev (27), libpmix2 (0), 
python3-pmix (0)
  * dh_installman: libpmix-bin (0), libpmix-dev (5), libpmix2 (0), 
python3-pmix (0)
  If the missing files are installed by another tool, please file a bug 
against it.
  When filing the report, if the tool is not part of debhelper itself, 
please reference the
  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
  If the omission is intentional or no other helper can take care of this 
consider adding the
  paths to debian/not-installed.

  Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
  use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
  to ensure it works on all architectures (see #961104).
   make: *** [debian/rules:36: binary] Error 25
   dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Full build log attached.
rbo build log here:
   
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/pmix_5.0.1-3.rbuild.log.gz

Best,
Chris



pmix_5.0.1-3.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

close 1057437

thanks

Incorrect bug closed in changelog

--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie--- End Message ---


Bug#1055688: marked as done (libgetdata ftbfs with Python 3.12 as supported Python version)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 16:05:13 +
with message-id 
and subject line Bug#1055688: fixed in libgetdata 0.11.0-8
has caused the Debian Bug report #1055688,
regarding libgetdata ftbfs with Python 3.12 as supported Python version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: src:libgetdata
Version: 0.11.0-7
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libgetdata ftbfs with Python 3.12 as supported Python version, 
hard-coding specific versions in the install file.


$ cat debian/python3-pygetdata.install
# usr/lib/python3*/site-packages/pygetdata*so
usr/local/lib/python3.11/dist-packages/*  /usr/lib/python3.11/site-packages


please work around that in other ways, not having a concrete version 
hard-coded.
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.11.0-8
Done: Alastair McKinstry 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Dec 2023 15:37:55 +
Source: libgetdata
Architecture: source
Version: 0.11.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1035352 1055544 1055688
Changes:
 libgetdata (0.11.0-8) unstable; urgency=medium
 .
   * Fix install rules to iterate over all pythons.Closes: #1055544, #1055688
   * No longer need python3-pygetdata.install
   * Drop obsolete CVE-2021-20204 patch. Closes: #1035352
Checksums-Sha1:
 770172921fa859bfad564636f5e1882342312011 2786 libgetdata_0.11.0-8.dsc
 f9a4df5d2468d9b06bffa3ed2e0e729ad5187077 7304 libgetdata_0.11.0-8.debian.tar.xz
Checksums-Sha256:
 ce3787bf726c1cf3d6aab59f169c1591391ce12fcfd3f3e1168c56e27aaedee9 2786 
libgetdata_0.11.0-8.dsc
 29f00b1665c3ece4b2c3e4557923fb8ef3568a84543fba28c4a2b05439321e28 7304 
libgetdata_0.11.0-8.debian.tar.xz
Files:
 6ae826748d07af290ea0e2978b2579b9 2786 science optional libgetdata_0.11.0-8.dsc
 849763fcf7e7f7808e71d8419e479367 7304 science optional 
libgetdata_0.11.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmVzOvwACgkQy+a7Tl2a
06XkNw/+JRuQVvk35+kEsgBz0WTT3xToA+Qi3P2/G7JZT0rZpKIbadlrA1amiTCy
iHtgskOp0T/PQ8W2taxVqpzxy/G1SxIhHFR9PrmX893MCGC1zg5XG5E5iax3UQhQ
UD8OENQSki1bQnj+iyoa2TaacRcNfiYmShG5zL972ZkOGtgtIphFaH/MegGkxONP
l6p3ZyIpzbH1pHjI7KqDQtdVwajmdqdQkcecx8fJoQEPrjLg2FblPM1e1AfgzJ/J
VFtzOTK2opAk2jCAKH6ZI/Gi8qPGoiivbUckgUx8t3jvWwM/uzoa/K0VEWk/y0R1
9banPbZVdOAFMW16gI9phzNikDGk42kZzIGszypCt2Ml8fRud2ZKuJRbXPRbwsAw
7M3F9Bwvj+ZOlwui8gYHvorBSlPCsAdVUvvOrLfOqz+i4SjflCjsVzwgNnzu/aYk
mIdFl2OQOb/Gao5PTbGpfvtk63pSqNWsbpiI4h2rV7aHQYIiGWrsd/wA1+jjlr+f
sT5lT1OEGHuvna19DXiTRIeb/a22by3/1t109XoG8eV6tyWPWXkAMJTgif/1bJqW
MkUzjlh5zO710sknjbP8e+/pRsPFaJm0tCwHZ1MTe/vAsecskV5gREBHqFeeQHh1
PiNTaOaJFIAadp/iBodHZoeSe+/lr/vTBaiKwkfJ/S6kK9lLXhA=
=XBUl
-END PGP SIGNATURE End Message ---


Bug#1055544: marked as done (libgetdata hardcodes specific python versions in the packaging)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 16:05:13 +
with message-id 
and subject line Bug#1055688: fixed in libgetdata 0.11.0-8
has caused the Debian Bug report #1055688,
regarding libgetdata hardcodes specific python versions in the packaging
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.)


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

Package: src:libgetdata
Version: 0.11-0-7
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libgetdata hardcodes specific python versions in the packaging, which it 
should not (seen when building with both 3.11 and 3.12 as supported 
Python version)


https://launchpadlibrarian.net/696569970/buildlog_ubuntu-noble-amd64.libgetdata_0.11.0-7build1_BUILDING.txt.gz

dh_missing: warning: 
usr/local/lib/python3.12/dist-packages/pygetdata.cpython-312-x86_64-linux-gnu.so 
exists in debian/tmp but is not installed to anywhere

dh_missing: error: missing files, aborting

$ cat debian/python3-pygetdata.install # 
usr/lib/python3*/site-packages/pygetdata*so

usr/local/lib/python3.11/dist-packages/*  /usr/lib/python3.11/site-packages
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.11.0-8
Done: Alastair McKinstry 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Dec 2023 15:37:55 +
Source: libgetdata
Architecture: source
Version: 0.11.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1035352 1055544 1055688
Changes:
 libgetdata (0.11.0-8) unstable; urgency=medium
 .
   * Fix install rules to iterate over all pythons.Closes: #1055544, #1055688
   * No longer need python3-pygetdata.install
   * Drop obsolete CVE-2021-20204 patch. Closes: #1035352
Checksums-Sha1:
 770172921fa859bfad564636f5e1882342312011 2786 libgetdata_0.11.0-8.dsc
 f9a4df5d2468d9b06bffa3ed2e0e729ad5187077 7304 libgetdata_0.11.0-8.debian.tar.xz
Checksums-Sha256:
 ce3787bf726c1cf3d6aab59f169c1591391ce12fcfd3f3e1168c56e27aaedee9 2786 
libgetdata_0.11.0-8.dsc
 29f00b1665c3ece4b2c3e4557923fb8ef3568a84543fba28c4a2b05439321e28 7304 
libgetdata_0.11.0-8.debian.tar.xz
Files:
 6ae826748d07af290ea0e2978b2579b9 2786 science optional libgetdata_0.11.0-8.dsc
 849763fcf7e7f7808e71d8419e479367 7304 science optional 
libgetdata_0.11.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmVzOvwACgkQy+a7Tl2a
06XkNw/+JRuQVvk35+kEsgBz0WTT3xToA+Qi3P2/G7JZT0rZpKIbadlrA1amiTCy
iHtgskOp0T/PQ8W2taxVqpzxy/G1SxIhHFR9PrmX893MCGC1zg5XG5E5iax3UQhQ
UD8OENQSki1bQnj+iyoa2TaacRcNfiYmShG5zL972ZkOGtgtIphFaH/MegGkxONP
l6p3ZyIpzbH1pHjI7KqDQtdVwajmdqdQkcecx8fJoQEPrjLg2FblPM1e1AfgzJ/J
VFtzOTK2opAk2jCAKH6ZI/Gi8qPGoiivbUckgUx8t3jvWwM/uzoa/K0VEWk/y0R1
9banPbZVdOAFMW16gI9phzNikDGk42kZzIGszypCt2Ml8fRud2ZKuJRbXPRbwsAw
7M3F9Bwvj+ZOlwui8gYHvorBSlPCsAdVUvvOrLfOqz+i4SjflCjsVzwgNnzu/aYk
mIdFl2OQOb/Gao5PTbGpfvtk63pSqNWsbpiI4h2rV7aHQYIiGWrsd/wA1+jjlr+f
sT5lT1OEGHuvna19DXiTRIeb/a22by3/1t109XoG8eV6tyWPWXkAMJTgif/1bJqW
MkUzjlh5zO710sknjbP8e+/pRsPFaJm0tCwHZ1MTe/vAsecskV5gREBHqFeeQHh1
PiNTaOaJFIAadp/iBodHZoeSe+/lr/vTBaiKwkfJ/S6kK9lLXhA=
=XBUl
-END PGP SIGNATURE End Message ---


Bug#1055688: marked as done (libgetdata ftbfs with Python 3.12 as supported Python version)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 16:05:13 +
with message-id 
and subject line Bug#1055544: fixed in libgetdata 0.11.0-8
has caused the Debian Bug report #1055544,
regarding libgetdata ftbfs with Python 3.12 as supported Python version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: src:libgetdata
Version: 0.11.0-7
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libgetdata ftbfs with Python 3.12 as supported Python version, 
hard-coding specific versions in the install file.


$ cat debian/python3-pygetdata.install
# usr/lib/python3*/site-packages/pygetdata*so
usr/local/lib/python3.11/dist-packages/*  /usr/lib/python3.11/site-packages


please work around that in other ways, not having a concrete version 
hard-coded.
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.11.0-8
Done: Alastair McKinstry 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Dec 2023 15:37:55 +
Source: libgetdata
Architecture: source
Version: 0.11.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1035352 1055544 1055688
Changes:
 libgetdata (0.11.0-8) unstable; urgency=medium
 .
   * Fix install rules to iterate over all pythons.Closes: #1055544, #1055688
   * No longer need python3-pygetdata.install
   * Drop obsolete CVE-2021-20204 patch. Closes: #1035352
Checksums-Sha1:
 770172921fa859bfad564636f5e1882342312011 2786 libgetdata_0.11.0-8.dsc
 f9a4df5d2468d9b06bffa3ed2e0e729ad5187077 7304 libgetdata_0.11.0-8.debian.tar.xz
Checksums-Sha256:
 ce3787bf726c1cf3d6aab59f169c1591391ce12fcfd3f3e1168c56e27aaedee9 2786 
libgetdata_0.11.0-8.dsc
 29f00b1665c3ece4b2c3e4557923fb8ef3568a84543fba28c4a2b05439321e28 7304 
libgetdata_0.11.0-8.debian.tar.xz
Files:
 6ae826748d07af290ea0e2978b2579b9 2786 science optional libgetdata_0.11.0-8.dsc
 849763fcf7e7f7808e71d8419e479367 7304 science optional 
libgetdata_0.11.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmVzOvwACgkQy+a7Tl2a
06XkNw/+JRuQVvk35+kEsgBz0WTT3xToA+Qi3P2/G7JZT0rZpKIbadlrA1amiTCy
iHtgskOp0T/PQ8W2taxVqpzxy/G1SxIhHFR9PrmX893MCGC1zg5XG5E5iax3UQhQ
UD8OENQSki1bQnj+iyoa2TaacRcNfiYmShG5zL972ZkOGtgtIphFaH/MegGkxONP
l6p3ZyIpzbH1pHjI7KqDQtdVwajmdqdQkcecx8fJoQEPrjLg2FblPM1e1AfgzJ/J
VFtzOTK2opAk2jCAKH6ZI/Gi8qPGoiivbUckgUx8t3jvWwM/uzoa/K0VEWk/y0R1
9banPbZVdOAFMW16gI9phzNikDGk42kZzIGszypCt2Ml8fRud2ZKuJRbXPRbwsAw
7M3F9Bwvj+ZOlwui8gYHvorBSlPCsAdVUvvOrLfOqz+i4SjflCjsVzwgNnzu/aYk
mIdFl2OQOb/Gao5PTbGpfvtk63pSqNWsbpiI4h2rV7aHQYIiGWrsd/wA1+jjlr+f
sT5lT1OEGHuvna19DXiTRIeb/a22by3/1t109XoG8eV6tyWPWXkAMJTgif/1bJqW
MkUzjlh5zO710sknjbP8e+/pRsPFaJm0tCwHZ1MTe/vAsecskV5gREBHqFeeQHh1
PiNTaOaJFIAadp/iBodHZoeSe+/lr/vTBaiKwkfJ/S6kK9lLXhA=
=XBUl
-END PGP SIGNATURE End Message ---


Bug#1055544: marked as done (libgetdata hardcodes specific python versions in the packaging)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 16:05:13 +
with message-id 
and subject line Bug#1055544: fixed in libgetdata 0.11.0-8
has caused the Debian Bug report #1055544,
regarding libgetdata hardcodes specific python versions in the packaging
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.)


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

Package: src:libgetdata
Version: 0.11-0-7
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libgetdata hardcodes specific python versions in the packaging, which it 
should not (seen when building with both 3.11 and 3.12 as supported 
Python version)


https://launchpadlibrarian.net/696569970/buildlog_ubuntu-noble-amd64.libgetdata_0.11.0-7build1_BUILDING.txt.gz

dh_missing: warning: 
usr/local/lib/python3.12/dist-packages/pygetdata.cpython-312-x86_64-linux-gnu.so 
exists in debian/tmp but is not installed to anywhere

dh_missing: error: missing files, aborting

$ cat debian/python3-pygetdata.install # 
usr/lib/python3*/site-packages/pygetdata*so

usr/local/lib/python3.11/dist-packages/*  /usr/lib/python3.11/site-packages
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.11.0-8
Done: Alastair McKinstry 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Dec 2023 15:37:55 +
Source: libgetdata
Architecture: source
Version: 0.11.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1035352 1055544 1055688
Changes:
 libgetdata (0.11.0-8) unstable; urgency=medium
 .
   * Fix install rules to iterate over all pythons.Closes: #1055544, #1055688
   * No longer need python3-pygetdata.install
   * Drop obsolete CVE-2021-20204 patch. Closes: #1035352
Checksums-Sha1:
 770172921fa859bfad564636f5e1882342312011 2786 libgetdata_0.11.0-8.dsc
 f9a4df5d2468d9b06bffa3ed2e0e729ad5187077 7304 libgetdata_0.11.0-8.debian.tar.xz
Checksums-Sha256:
 ce3787bf726c1cf3d6aab59f169c1591391ce12fcfd3f3e1168c56e27aaedee9 2786 
libgetdata_0.11.0-8.dsc
 29f00b1665c3ece4b2c3e4557923fb8ef3568a84543fba28c4a2b05439321e28 7304 
libgetdata_0.11.0-8.debian.tar.xz
Files:
 6ae826748d07af290ea0e2978b2579b9 2786 science optional libgetdata_0.11.0-8.dsc
 849763fcf7e7f7808e71d8419e479367 7304 science optional 
libgetdata_0.11.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmVzOvwACgkQy+a7Tl2a
06XkNw/+JRuQVvk35+kEsgBz0WTT3xToA+Qi3P2/G7JZT0rZpKIbadlrA1amiTCy
iHtgskOp0T/PQ8W2taxVqpzxy/G1SxIhHFR9PrmX893MCGC1zg5XG5E5iax3UQhQ
UD8OENQSki1bQnj+iyoa2TaacRcNfiYmShG5zL972ZkOGtgtIphFaH/MegGkxONP
l6p3ZyIpzbH1pHjI7KqDQtdVwajmdqdQkcecx8fJoQEPrjLg2FblPM1e1AfgzJ/J
VFtzOTK2opAk2jCAKH6ZI/Gi8qPGoiivbUckgUx8t3jvWwM/uzoa/K0VEWk/y0R1
9banPbZVdOAFMW16gI9phzNikDGk42kZzIGszypCt2Ml8fRud2ZKuJRbXPRbwsAw
7M3F9Bwvj+ZOlwui8gYHvorBSlPCsAdVUvvOrLfOqz+i4SjflCjsVzwgNnzu/aYk
mIdFl2OQOb/Gao5PTbGpfvtk63pSqNWsbpiI4h2rV7aHQYIiGWrsd/wA1+jjlr+f
sT5lT1OEGHuvna19DXiTRIeb/a22by3/1t109XoG8eV6tyWPWXkAMJTgif/1bJqW
MkUzjlh5zO710sknjbP8e+/pRsPFaJm0tCwHZ1MTe/vAsecskV5gREBHqFeeQHh1
PiNTaOaJFIAadp/iBodHZoeSe+/lr/vTBaiKwkfJ/S6kK9lLXhA=
=XBUl
-END PGP SIGNATURE End Message ---


Bug#1057577: marked as done (mapsforge: FTBFS: Could not resolve :osmosis-core-0.48.3:.)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 15:51:31 +
with message-id 
and subject line Bug#1057577: fixed in mapsforge 0.17.0+dfsg.1-3
has caused the Debian Bug report #1057577,
regarding mapsforge: FTBFS: Could not resolve :osmosis-core-0.48.3:.
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.)


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

Package: src:mapsforge
Version: 0.17.0+dfsg.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=gradle --with maven_repo_helper
   dh_update_autotools_config -O--buildsystem=gradle
   dh_autoreconf -O--buildsystem=gradle
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# Set version string correctly
if [ ! -f build.gradle.debsave ]; then \
sed -i.debsave 's/master-SNAPSHOT/0.17.0/' build.gradle ;\
fi
dh_auto_configure
make[1]: Leaving directory '/<>'
   dh_auto_build -O--buildsystem=gradle
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=mapsforge -Dfile.encoding=UTF-8 --parallel 
--max-workers=2 jar
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-2)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-2, mixed mode, sharing)
Initialized native services in: /<>/.gradle/native
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
Starting process 'Gradle build daemon'. Working directory: 
/<>/.gradle/daemon/4.4.1 Command: 
/usr/lib/jvm/java-17-openjdk-amd64/bin/java --add-opens java.base/java.lang=ALL-UNNAMED 
-Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
 -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp 
/usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 0.726 secs.
The client will now receive all logging from the daemon (pid: 1250065). The daemon log 
file: /<>/.gradle/daemon/4.4.1/daemon-1250065.out.log
Daemon will be stopped at the end of the build stopping after processing
Closing daemon's stdin at end of input.
The daemon will no longer process any standard input.
Using 2 worker leases.
Creating new cache for fileHashes, path 
/<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@4921497
Creating new cache for resourceHashesCache, path 
/<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
access org.gradle.cache.internal.DefaultCacheAccess@4921497
Creating new cache for fileHashes, path 
/<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@4d4cfb5b
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Creating new cache for metadata-1.1/results, path 
/<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@13ab7d50
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Settings file found (/<>/settings.gradle), but 
rootProject.name isn't defined
Root project name not defined in settings.gradle, defaulting to 
'mapsforge' instead of the name of the root directory 'mapsforge-0.17.0+dfsg.1'
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'mapsforge', project ':mapsforge-core', 
project ':mapsforge-map', project ':mapsforge-map-awt', project 
':mapsforge-map-reader', project ':mapsforge-map-writer', project 
':mapsforge-poi', project ':mapsforge-samples-awt', project ':mapsforge-themes']
Keep-alive timer started
Adding Debian repository to project 'mapsforge'
Adding Debian repository to project 

Bug#1056980: [devuan-dev] bug#813: Reopen 1056980

2023-12-08 Thread Svante Signell
On Fri, 2023-12-08 at 16:15 +0100, Svante Signell wrote:
> reopen 1056980
> severity 1056980 serious
> tags 1056980 patch
> thanks

Sorry, forgot the patch!

--- a/debian/netcat-traditional.postinst	2023-11-27 03:20:27.0 +0100
+++ b/debian/netcat-traditional.postinst	2023-12-04 15:11:31.0 +0100
@@ -4,8 +4,8 @@
 
 if [ "$1" = "configure" ]; then
 update-alternatives \
---install /bin/nc nc /bin/nc.traditional 10 \
---slave /bin/netcat netcat /bin/nc.traditional \
+--install /usr/bin/nc nc /usr/bin/nc.traditional 10 \
+--slave /usr/bin/netcat netcat /usr/bin/nc.traditional \
 --slave /usr/share/man/man1/nc.1.gz nc.1.gz \
 /usr/share/man/man1/nc.traditional.1.gz \
 --slave /usr/share/man/man1/netcat.1.gz netcat.1.gz \


Bug#1057792: Removal notice: obsolete

2023-12-08 Thread Ilias Tsitsimpis
Source: darcs-monitor
Version: 0.4.2-14
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Last upload more than 10 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Processed: Reopen 1056980

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 1056980
Bug #1056980 {Done: Luca Boccassi } [netcat-traditional] 
netcat-traditional: upgrade to 1.10-48 fails (postinst script)
Bug reopened
Ignoring request to alter fixed versions of bug #1056980 to the same values 
previously set
> severity 1056980 serious
Bug #1056980 [netcat-traditional] netcat-traditional: upgrade to 1.10-48 fails 
(postinst script)
Severity set to 'serious' from 'normal'
> tags 1056980 patch
Bug #1056980 [netcat-traditional] netcat-traditional: upgrade to 1.10-48 fails 
(postinst script)
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#1057780: gdb-minimal provides gdb, without providing all the features in gdb

2023-12-08 Thread Matthias Klose

On 08.12.23 15:39, Héctor Orón Martínez wrote:

Hello Matthias,

El vie, 8 dic 2023, 13:27, Matthias Klose  escribió:


Package: src:gdb
Version: 13.2-1
Severity: serious
Tags: sid trixie

gdb-minimal provides gdb, without providing all the features in gdb.
Seen this in the python testsuite, trying to call

gdb '--eval-command=python3 import sys; print(sys.version_info)'

please drop the provides, or maybe it's time to stop building the
gdb-minimal package.



Looking at popcon there are similar installs for gdb as there are for gdb
minimal. This is useful for systems with limited storage. I do not think
dropping it is an option.

https://qa.debian.org/popcon.php?package=gdb

Having gdb-minimal replace gdb with minimal features I think it makes sense
to keep it. Why do you think this is a serious issue?


gdb-minimal announces features that it cannot fulfill.  If you want to 
keep it, please remove the provides.




Bug#1057780: gdb-minimal provides gdb, without providing all the features in gdb

2023-12-08 Thread Héctor Orón Martínez
Hello Matthias,

El vie, 8 dic 2023, 13:27, Matthias Klose  escribió:

> Package: src:gdb
> Version: 13.2-1
> Severity: serious
> Tags: sid trixie
>
> gdb-minimal provides gdb, without providing all the features in gdb.
> Seen this in the python testsuite, trying to call
>
>gdb '--eval-command=python3 import sys; print(sys.version_info)'
>
> please drop the provides, or maybe it's time to stop building the
> gdb-minimal package.
>

Looking at popcon there are similar installs for gdb as there are for gdb
minimal. This is useful for systems with limited storage. I do not think
dropping it is an option.

https://qa.debian.org/popcon.php?package=gdb

Having gdb-minimal replace gdb with minimal features I think it makes sense
to keep it. Why do you think this is a serious issue?

>


Bug#1055572: marked as done (cbflib ftbfs with Python 3.12)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 14:34:55 +
with message-id 
and subject line Bug#1055572: fixed in cbflib 0.9.7+dfsg1-3
has caused the Debian Bug report #1055572,
regarding cbflib 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.)


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

Package: src:cbflib
Version: 0.9.7+dfsg1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

cbflib ftbfs with Python 3.12.  Please also have a look at the full 
build log, I doubt that the package correctly builds for two supported 
Python versions.


[...]
make[2]: Leaving directory '/<>'
# install the python extension
dh_auto_install --buildsystem=pybuild --sourcedirectory=pycbf
I: pybuild base:310: /usr/bin/python3.12 setup.py install --root 
/<>/debian/python3-pycbf
/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
SetuptoolsDeprecationWarning: setup.py install is deprecated.

!!



Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.

See 
https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for 
details.




!!
  self.initialize_options()
error: Invalid distribution name or version syntax: -pycbf-0.0.0
E: pybuild pybuild:395: install: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py install --root 
/<>/debian/python3-pycbf
dh_auto_install: error: pybuild --install -i python{version} -p "3.12 
3.11" --dir pycbf --dest-dir 
/<>/cbflib-0.9.7\+dfsg1/debian/tmp returned exit code 13

make[1]: *** [debian/rules:56: override_dh_auto_install-arch] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:30: binary] Error 2



full build log:
https://launchpadlibrarian.net/696570331/buildlog_ubuntu-noble-amd64.cbflib_0.9.7+dfsg1-2build3_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
Source: cbflib
Source-Version: 0.9.7+dfsg1-3
Done: Picca Frédéric-Emmanuel 

We believe that the bug you reported is fixed in the latest version of
cbflib, 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.
Picca Frédéric-Emmanuel  (supplier of updated cbflib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Dec 2023 14:14:29 +0100
Source: cbflib
Architecture: source
Version: 0.9.7+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1055572
Changes:
 cbflib (0.9.7+dfsg1-3) unstable; urgency=medium
 .
   [ Teemu Ikonen ]
   * d/patches: setup_py.m4: Use setuptools, change to acceptable module name
   * d/rules: Remove pycbf/pycbf.egg-info on clean
   * Bug fix: "cbflib ftbfs with Python 3.12", thanks to Matthias Klose
 (Closes: #1055572).
Checksums-Sha1:
 5f47f219ea74a1b975b9dfe79ccd8d897ee2ec60 2562 cbflib_0.9.7+dfsg1-3.dsc
 8318ba344f41bee8f5e0eb7e7c7a179a42d5e0f1 25664 
cbflib_0.9.7+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 1eb341104f985b7e62fa9bbd9de3c4a3079a707472090929f68be6a11d1de6db 2562 
cbflib_0.9.7+dfsg1-3.dsc
 de0055c5bd10a83630691e07db43ddcfb621474db70446d55dcba874165be591 25664 
cbflib_0.9.7+dfsg1-3.debian.tar.xz
Files:
 e95a7d266915f420d45e65c126bd90ea 2562 science optional cbflib_0.9.7+dfsg1-3.dsc
 77aa60ee2791ff65648cc6dce939c537 25664 science optional 
cbflib_0.9.7+dfsg1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmVzHNERHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALtMBBAAgNELdAUAMIiq8lAs8HIpS8PvsJokv30V
8sjfzYbAC7wSA+lIW63969avTL0ioSEdeXKo7IqrO4ej7jRrKby4V/d1wqYO0Lu9
kFJ1M6+Gb5wVnxwsQgBKPbxnPzBXHDAw1JV/wokanmCU1nfl40HeRgrmwlzwtNq8
OkSeQMLAbwJ9pTZpr7cPx++JWtnQmfAdFmWGK+iHIa/275HQksihW5ZLqFpqn5oW
12BU4badh2nGJKh2/enYLTjeGb9C/NWDf+RgsKcJyNdZRlkE8ym0y6XxSR5hm9po

Processed: Re: transmission-gtk 3.00-1 : *** invalid %N$ use detected *** - Abandon

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1053988 important
Bug #1053988 [transmission-gtk] transmission-gtk 3.00-1 : *** invalid %N$ use 
detected *** - Abandon.
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#1053988: transmission-gtk 3.00-1 : *** invalid %N$ use detected *** - Abandon

2023-12-08 Thread Alexandre Rossi
severity 1053988 important
thanks

Hi,

Lowering severity as transmission-daemon works well.

Thanks,

Alex



Bug#1057782: gtk4: FTBFS on big-endian: memorytexture test fails

2023-12-08 Thread Simon McVittie
Source: gtk4
Version: 4.12.4+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-s...@lists.debian.org

>From 
>https://buildd.debian.org/status/fetch.php?pkg=gtk4=s390x=4.12.4%2Bds-1=1701103591=0
> test: gtk:gdk / memorytexture
> start time:   16:40:53
> duration: 0.64s
> result:   killed by signal 6 SIGABRT
> ...
> 1..2072
> # Start of memorytexture tests
> # Start of download_1x1 tests
> # Start of b8g8r8a8-premultiplied tests
> ok 1 /memorytexture/download_1x1/b8g8r8a8-premultiplied/local
> not ok /memorytexture/download_1x1/b8g8r8a8-premultiplied/gl - 
> ERROR:../../../testsuite/gdk/memorytexture.c:819:compare_textures: 
> 'gdk_memory_format_pixel_equal (format, accurate_compare, data1 + bpp * x, 
> data2 + bpp * x)' should be TRUE

The same test fails on ppc64, which makes me think this is an endianness
bug, probably introduced in the new upstream release 4.12.4. I'm looking
into it.

cc debian-s390 since it is our only big-endian release architecture.

smcv



Bug#1057780: gdb-minimal provides gdb, without providing all the features in gdb

2023-12-08 Thread Matthias Klose

Package: src:gdb
Version: 13.2-1
Severity: serious
Tags: sid trixie

gdb-minimal provides gdb, without providing all the features in gdb. 
Seen this in the python testsuite, trying to call


  gdb '--eval-command=python3 import sys; print(sys.version_info)'

please drop the provides, or maybe it's time to stop building the 
gdb-minimal package.




Bug#1054797: marked as done (dosage: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 11:34:32 +
with message-id 
and subject line Bug#1054797: fixed in dosage 3.0+dfsg-1
has caused the Debian Bug report #1054797,
regarding dosage: FTBFS: make[1]: *** [debian/rules:8: 
override_dh_auto_configure] Error 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dosage
Version: 2.15-4
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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> python3 setup.py sdist --manifest-only
> Warning: 'classifiers' should be a list, got type 'tuple'
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: option --manifest-only not recognized
> make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/dosage_2.15-4_unstable.log

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

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dosage
Source-Version: 3.0+dfsg-1
Done: Alexandre Detiste 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Dec 2023 11:59:45 +0100
Source: dosage
Architecture: source
Version: 3.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Detiste 
Changed-By: Alexandre Detiste 
Closes: 774995 102 1054797
Changes:
 dosage (3.0+dfsg-1) unstable; urgency=medium
 .
   * Adopt package (Closes: #774995)
   * New upstream version 3.0
   * redo d/rules, fix FTBFS (Closes: #1054797, #102)
   * repack to remove vendored example website with fonts and js
   * create Salsa repository
   * use newer dh-sequence-python3
   * Update standards version to 4.6.2, no more changes needed.
 .
   [ Janitor ]
   * Use correct machine-readable copyright file URI.
   * Use secure URI in Homepage field.
   * Bump debhelper from deprecated 9 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Add missing build-dependency on python3-setuptools.
Checksums-Sha1:
 7bb5336bd32923f268acf56a6f478b0ccfb74b11 1927 dosage_3.0+dfsg-1.dsc
 030eafda4b2949707eb723d16bfe49550bafbb2d 289072 dosage_3.0+dfsg.orig.tar.xz
 f3da11f4213541331c6dd6f166b920f349fd 6796 dosage_3.0+dfsg-1.debian.tar.xz
 2d5e2e4cf8169691a727806391fa33b698a33ec1 7209 
dosage_3.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 ab6d57621bab5aa682bd105fa779b993c7254b9bd657424dfe3deda63a4fdd34 1927 
dosage_3.0+dfsg-1.dsc
 7a54437dceee1eb0168b544e94710fdfa19161c3b26eee5b1d49112ed9e3b992 289072 
dosage_3.0+dfsg.orig.tar.xz
 9239517dad8021a234d50b155c21c1abcf2386acb54ceaccc588c590f8ababa1 6796 
dosage_3.0+dfsg-1.debian.tar.xz

Processed: affects 1055801

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 1055801 src:python-geotiepoints src:trollimage
Bug #1055801 [python3-pandas] pandas: test failures with Python 3.12
Added indication that 1055801 affects src:python-geotiepoints and src:trollimage
> thanks
Stopping processing here.

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



Bug#1057424: marked as done (libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Dec 2023 12:17:38 +0100
with message-id 
and subject line Re: Bug#1057424: libmodule-build-perl: Multi-Arch: foreign 
makes other packages FTBFS
has caused the Debian Bug report #1057424,
regarding libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS
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.)


-- 
1057424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmodule-build-perl
Version: 0.423400-2
Severity: serious
Tags: ftbfs
Control: affects -1 libnet-cidr-set-perl libparams-validate-perl
X-Debbugs-Cc: debian-cr...@lists.debian.org
Control: block 1055955 with -1

The libnet-cidr-set-perl and libparams-validate-perl packages
fail to build from source in current unstable.

>From a full build log at

 
http://perl.debian.net/rebuild-logs/sid/libparams-validate-perl_1.31-1/libparams-validate-perl_1.31-1.buildlog

  Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -Zxz
  dpkg-buildpackage: info: source package libparams-validate-perl
  dpkg-buildpackage: info: source version 1.31-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by gregor herrmann 
   dpkg-source -Zxz --before-build .
  dpkg-buildpackage: info: host architecture amd64
  dpkg-checkbuilddeps: error: Unmet build dependencies: 
libmodule-build-perl:native
  dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
  dpkg-buildpackage: warning: (Use -d flag to override.)
 
This is because libmodule-build-perl was recently marked
Multi-Arch:foreign, but dpkg-checkbuilddeps does not consider that as
satisfying :native build dependencies, see #1023438.

My understanding is that M-A:foreign is probably the right thing
to do here, but we need to remove the :native build dependency
in other packages first. Fortunately I see only two in the archive,
libnet-cidr-set-perl and libparams-validate-perl.

  grep-dctrl -sPackage,Build-Depends,Build-Depends-Indep 
-FBuild-Depends,Build-Depends-Indep -r 'libmodule-build-perl[^,]*:native' 
/var/lib/apt/lists/*_main_source_Sources

Filing against libmodule-build-perl for now to prevent it from entering
trixie before the other two are changed. Feel free to reassign or clone
or whatever if you like.

As libparams-validate-perl is an arch:any XS module, we need to fix it
one way or another before the Perl 5.38 transition. So marking this as
a blocker.

Copying the debian-cross list in case I got something wrong :)
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
On Wed, 06 Dec 2023 10:19:22 +0100, gregor herrmann wrote:

> On Wed, 06 Dec 2023 09:52:17 +0200, Niko Tyni wrote:
> > Maybe just wait a couple of days and close this when the two packages
> > have migrated?
> … of course this works as well :)

libnet-cidr-set-perl and libparams-validate-perl migrated, so closing
this bug now.


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
--- End Message ---


Bug#1035604: marked as done (progress-linux-container: fails to upgrade from 'bullseye': diversion conflict)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 10:22:16 +
with message-id 
and subject line Bug#1035604: fixed in progress-linux-metapackages 20221002-10
has caused the Debian Bug report #1035604,
regarding progress-linux-container: fails to upgrade from 'bullseye': diversion 
conflict
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.)


-- 
1035604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: progress-linux-container
Version: 20221002-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'bookworm' fails.

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

  Preparing to unpack .../112-progress-linux-container_20221002-8_all.deb ...
  dpkg-divert: error: 'diversion of /sbin/halt to 
/lib/container/divert/halt.orig by progress-linux-container' clashes with 
'diversion of /sbin/halt to /lib/open-infrastructure/container/divert/halt.orig 
by progress-linux-container'
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ujBXu1/112-progress-linux-container_20221002-8_all.deb 
(--unpack):
   new progress-linux-container package pre-installation script subprocess 
returned error exit status 2
  Preparing to unpack .../113-sysstat_12.6.1-1_amd64.deb ...
  Unpacking sysstat (12.6.1-1) over (12.5.2-2) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ujBXu1/112-progress-linux-container_20221002-8_all.deb


cheers,

Andreas


progress-linux-container_20221002-8.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: progress-linux-metapackages
Source-Version: 20221002-10
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
progress-linux-metapackages, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1035...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
progress-linux-metapackages package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Dec 2023 10:53:05 +0100
Source: progress-linux-metapackages
Architecture: source
Version: 20221002-10
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1035604
Changes:
 progress-linux-metapackages (20221002-10) sid; urgency=medium
 .
   * Uploading to sid.
   * Removing previous diversions when upgrading from bullseye in progress-
 linux-container (Closes: #1035604).
   * Adding console-setup to progress-linux-host depends.
   * Removing 32bit architectures from depends.
   * Moving from knot-resolver to systemd-resolved.
   * Moving gnome-shell-extensions-extra from progress-linux-gnome-desktop
 suggests to depends.
   * Removing old virtualbox-qt package in progress-linux-desktop suggests.
Checksums-Sha1:
 5eb4cab231ee6edcc60f46ad6046e1300a86c139 2772 
progress-linux-metapackages_20221002-10.dsc
 ec3b3a40bb070ffb371af56b57491cb6ae3fb677 7312 
progress-linux-metapackages_20221002-10.debian.tar.xz
 595540b101ff8d171895c314eb7c59291394e9f1 8859 
progress-linux-metapackages_20221002-10_amd64.buildinfo
Checksums-Sha256:
 bde666534077135087312bfbd1ade3aba316244410bdd9a9c6aab6f4feb7647d 2772 
progress-linux-metapackages_20221002-10.dsc
 f0332521fe615e0d4dd0934ec6da42f0ac95b8c107f054774ac2aef5f8afbaf3 7312 
progress-linux-metapackages_20221002-10.debian.tar.xz
 2ba7021b50da933582d2712c6ca7adbfe88049b6a8dca1e048bf728014af21e4 8859 
progress-linux-metapackages_20221002-10_amd64.buildinfo
Files:
 0aad0ef72206e1b96f4a4f968c9f10fd 2772 metapackages optional 
progress-linux-metapackages_20221002-10.dsc
 bfca6f1501a25a20b83896b2a13e1f34 7312 metapackages optional 
progress-linux-metapackages_20221002-10.debian.tar.xz
 fabd55f475c2fcf8c1f8766bf0deff32 8859 metapackages optional 
progress-linux-metapackages_20221002-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmVy5/kACgkQVc8b+Yar

Bug#1054156: [Pkg-rust-maintainers] Bug#1054156: librust-env-logger-0.7+default-dev shouldn't provide librust-env-logger+default-dev

2023-12-08 Thread Fabian Grünbichler
On Thu, Dec 07, 2023 at 01:02:58AM +, Peter Green wrote:
> On the one hand I'm not at all convinced this bug is rc, on the other
> hand I don't think shipping a four year old version of env-logger
> in the next release of Debian is a great idea.
> 
> So I decided to look at the reverse dependencies, I found three
> 
> safe-vdash - this is a Jonas package, the dependency on rust-env-logger-0.7 
> seems bogus, I filed a bug.
> rust-tracing-log - the new version no longer depends on env-logger, I updated 
> it along with it's reverse dependency tracing-subscriber.
> rspotify - this package is long term broken, noctis expressed an interest in 
> fixing it back in January but I don't know what if-any progress he has made 
> since then.

(as always!) thanks for the analysis above. I agree that reducing the
env_logger versions in testing is a good idea in any case.

the question is whether we want to drop the unversioned provides in
semver-suffixed packages altogether in debcargo - IIRC debcargo itself
would never generate an unversioned dependency in d/control except if
Cargo.toml itself has an unversioned dependency, which is not possible
for crates on crates.io. that would only leave manually generated
dependencies, or patched crates with very strong relaxation.

and even so, the normal flow for semver-suffix packages would work just fine:
- fork semver suffix package, upload to NEW/experimental
- wait for NEW processing
- bump regular package, upload both to unstable

and any package that uses an unversioned dependency would stay on the
non-suffixed package providing/containing the latest packaged version,
while anything depending on the old semantic version would switch to the
suffixed package.

the only thing that wouldn't work anymore is having a versioned dep on
the unversioned package where the version constraint would only be
satisfied by the suffixed package.

e.g., librust-env-logger-dev (<= 0.8)



Bug#1057674: marked as pending in pyqt6

2023-12-08 Thread Dmitry Shachnev
Control: tag -1 pending

Hello,

Bug #1057674 in pyqt6 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/pyqt6/-/commit/562b433605800d0943609ac58fbb87f7419a49d9


Do not use dh_python3 on examples.

Closes: #1057674.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057674



Processed: Bug#1057674 marked as pending in pyqt6

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1057674 [pyqt6-examples] pyqt6-examples: rtupdate hook uses /usr/share/doc 
content (Policy 12.3): 
/usr/share/doc/pyqt6-examples/examples/designer/calculatorform/calculatorform.py
Added tag(s) pending.

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



Bug#1055701: marked as done (pycifrw ftbfs with Python 3.12 (test failures))

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Dec 2023 09:36:16 +
with message-id 
and subject line Bug#1055701: fixed in pycifrw 4.4.6-2
has caused the Debian Bug report #1055701,
regarding pycifrw ftbfs with Python 3.12 (test failures)
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.)


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

Package: src:pycifrw
Version: 4.4.4-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12


=== short test summary info 

FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testAddIndent - 
AttributeError...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testCorrectEnding - 
AttributeE...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testFinalBackslash - 
Attribute...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testFoldingRemoval - 
Attribute...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testManyLineEndings - 
Attribut...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testOptionalBreak - 
AttributeE...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testPlainLineFolding - 
Attribu...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testPreWrappedFolding - 
Attrib...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testPrefixAndFold - 
AttributeE...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testRemoveIndent - 
AttributeEr...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testReverseIndent - 
AttributeE...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testStarList - 
AttributeError:...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testTrailingBackslash - 
Attrib...
FAILED TestPyCIFRW.py::BasicUtilitiesTestCase::testTrickyFoldingRemoval 
- Att...
FAILED TestPyCIFRW.py::BlockRWTestCase::testStringSet - AttributeError: 
'Bloc...
FAILED TestPyCIFRW.py::BlockRWTestCase::testTupleComplexSet - 
AttributeError:...
FAILED TestPyCIFRW.py::BlockRWTestCase::testTupleNumberSet - 
AttributeError: ...
FAILED TestPyCIFRW.py::BlockChangeTestCase::testAddToLoop - 
AttributeError: '...
FAILED TestPyCIFRW.py::BlockChangeTestCase::testFullLoopRemove - 
AttributeErr...
FAILED TestPyCIFRW.py::LoopBlockTestCase::testLoop - AttributeError: 
'LoopBlo...
FAILED TestPyCIFRW.py::LoopBlockTestCase::testLoopCharCase - 
AttributeError: ...
FAILED TestPyCIFRW.py::LoopBlockTestCase::testLoopOutputOrder - 
AttributeErro...
FAILED TestPyCIFRW.py::FileWriteTestCase::testApostropheInOut - 
AttributeErro...
FAILED TestPyCIFRW.py::FileWriteTestCase::testBadBeginning - 
AttributeError: ...
FAILED TestPyCIFRW.py::FileWriteTestCase::testCopySaveFrame - 
AttributeError:...
FAILED TestPyCIFRW.py::FileWriteTestCase::testEmptyDict - 
AttributeError: 'Fi...
FAILED TestPyCIFRW.py::FileWriteTestCase::testEmptyStringInOut - 
AttributeErr...
FAILED TestPyCIFRW.py::FileWriteTestCase::testFirstBlock - 
AttributeError: 'F...
FAILED TestPyCIFRW.py::FileWriteTestCase::testGetLoopData - 
AttributeError: '...
FAILED TestPyCIFRW.py::FileWriteTestCase::testItemChange - 
AttributeError: 'F...
FAILED TestPyCIFRW.py::FileWriteTestCase::testLongStringInOut - 
AttributeErro...
FAILED TestPyCIFRW.py::FileWriteTestCase::testLoopDataInOut - 
AttributeError:...
FAILED TestPyCIFRW.py::FileWriteTestCase::testLoopStringInOut - 
AttributeErro...
FAILED TestPyCIFRW.py::FileWriteTestCase::testNumberInOut - 
AttributeError: '...
FAILED TestPyCIFRW.py::FileWriteTestCase::testSemiWhiteSpace - 
AttributeError...
FAILED TestPyCIFRW.py::FileWriteTestCase::testStringInOut - 
AttributeError: '...
FAILED TestPyCIFRW.py::FileWriteTestCase::testWrongLoop - 
AttributeError: 'Fi...
FAILED TestPyCIFRW.py::SimpleWriteTestCase::testNDString - 
AttributeError: 'S...
FAILED TestPyCIFRW.py::SimpleWriteTestCase::testNumpyArray - 
AttributeError: ...
FAILED TestPyCIFRW.py::SimpleWriteTestCase::testNumpyLoop - 
AttributeError: '...
FAILED TestPyCIFRW.py::TemplateTestCase::testStringInput - 
AttributeError: 'T...
FAILED TestPyCIFRW.py::TemplateTestCase::testTemplateInput - 
AttributeError: ...
FAILED TestPyCIFRW.py::ParentChildTestCase::testChangeParent - 
AttributeError...
FAILED TestPyCIFRW.py::ParentChildTestCase::testGetChildren - 
AttributeError:...
FAILED TestPyCIFRW.py::ParentChildTestCase::testGetChildrenwithParent - 
Attri...
FAILED TestPyCIFRW.py::ParentChildTestCase::testGetParent - 
AttributeError: '...
FAILED TestPyCIFRW.py::ParentChildTestCase::testGoodRead - 
AttributeError: 'P...
FAILED TestPyCIFRW.py::ParentChildTestCase::testRename1 - 
AttributeError: 'Pa...
FAILED 

Processed (with 1 error): Re: Bug#1057589: octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + upstream confirmed
Bug #1057589 [octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Ignoring request to alter tags of bug #1057589 to the same tags previously set
> forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Bug #1057589 [octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Ignoring request to change the forwarded-to-address of bug#1057589 to the same 
value
> reassign -1 octave-netcdf
Bug #1057589 [octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Ignoring request to reassign bug #1057589 to the same package
> merge -1 1057590
Bug #1057589 [octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Unable to merge bugs because:
package of #1057590 is 'src:octave-netcdf' not 'octave-netcdf'
Failed to merge 1057589: Did not alter merged bugs.


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



Bug#1057766: Osk button missing after startup

2023-12-08 Thread Guido Günther
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



Processed (with 1 error): Re: Bug#1057589: octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + upstream confirmed
Bug #1057589 [src:octave-ncarray] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Added tag(s) upstream and confirmed.
> forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Bug #1057589 [src:octave-ncarray] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?64999'.
> reassign -1 octave-netcdf
Bug #1057589 [src:octave-ncarray] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Bug reassigned from package 'src:octave-ncarray' to 'octave-netcdf'.
No longer marked as found in versions octave-ncarray/1.0.5-3.
Ignoring request to alter fixed versions of bug #1057589 to the same values 
previously set
> merge -1 1057590
Bug #1057589 [octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Unable to merge bugs because:
package of #1057590 is 'src:octave-netcdf' not 'octave-netcdf'
Failed to merge 1057589: Did not alter merged bugs.


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



Bug#1057589: octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-08 Thread Rafael Laboissière

Control: tags -1 + upstream confirmed
Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Control: reassign -1 octave-netcdf
Control: merge -1 1057590

Thanks for the bug report.

I verified with gdb and I think that this bug is very certainly caused by 
the octave-netcdf package, on which octave-ncarray depends. I am hereby 
merging the present bug report with Bug#1057590


Best,

Rafael Laboissière

* Santiago Vila  [2023-12-05 23:08]:


Package: src:octave-ncarray
Version: 1.0.5-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 --buildsystem=octave
  dh_update_autotools_config -O--buildsystem=octave
  dh_autoreconf -O--buildsystem=octave
  dh_octave_version -O--buildsystem=octave
Checking the Octave version... ok
  dh_auto_configure -O--buildsystem=octave
  dh_auto_build -O--buildsystem=octave
  dh_auto_test -O--buildsystem=octave
  create-stamp debian/debhelper-build-stamp
  dh_testroot -O--buildsystem=octave
  dh_prep -O--buildsystem=octave
  dh_auto_install --destdir=debian/octave-ncarray/ -O--buildsystem=octave
octave --no-gui --no-history --silent --no-init-file --no-window-system 
/usr/share/dh-octave/install-pkg.m 
/<>/debian/octave-ncarray/usr/share/octave/packages 
/<>/debian/octave-ncarray/usr/lib/x86_64-linux-gnu/octave/packages
For information about changes from previous versions of the ncarray package, 
run 'news ncarray'.
  dh_octave_check -O--buildsystem=octave
Checking package...
Checking m files ...
warning: function /usr/share/octave/packages/statistics-1.6.0/shadow9/std.m 
shadows a core library function
warning: called from
   /usr/share/octave/packages/statistics-1.6.0/PKG_ADD at line 13 column 3
   load_packages_and_dependencies at line 56 column 5
   load_packages at line 53 column 3
   pkg at line 639 column 7
   /tmp/tmp.DHPTjFH6go at line 9 column 9

warning: function /usr/share/octave/packages/statistics-1.6.0/shadow9/var.m 
shadows a core library function
warning: called from
   /usr/share/octave/packages/statistics-1.6.0/PKG_ADD at line 13 column 3
   load_packages_and_dependencies at line 56 column 5
   load_packages at line 53 column 3
   pkg at line 639 column 7
   /tmp/tmp.DHPTjFH6go at line 9 column 9

warning: function /usr/share/octave/packages/statistics-1.6.0/shadow9/mean.m 
shadows a core library function
warning: called from
   /usr/share/octave/packages/statistics-1.6.0/PKG_ADD at line 13 column 3
   load_packages_and_dependencies at line 56 column 5
   load_packages at line 53 column 3
   pkg at line 639 column 7
   /tmp/tmp.DHPTjFH6go at line 9 column 9

warning: function /usr/share/octave/packages/statistics-1.6.0/shadow9/median.m 
shadows a core library function
warning: called from
   /usr/share/octave/packages/statistics-1.6.0/PKG_ADD at line 13 column 3
   load_packages_and_dependencies at line 56 column 5
   load_packages at line 53 column 3
   pkg at line 639 column 7
   /tmp/tmp.DHPTjFH6go at line 9 column 9

warning: function /usr/share/octave/packages/statistics-1.6.0/shadow9/mad.m 
shadows a core library function
warning: called from
   /usr/share/octave/packages/statistics-1.6.0/PKG_ADD at line 13 column 3
   load_packages_and_dependencies at line 56 column 5
   load_packages at line 53 column 3
   pkg at line 639 column 7
   /tmp/tmp.DHPTjFH6go at line 9 column 9

[inst/test_ncarray_nan.m]

/<>/inst/test_ncarray_nan.m

* test
test_ncarray_nan ()
warning: test: file /<>/inst/test_ncarray_nan.m leaked global 
variables: CACHED_DECOMPRESS_DIR CACHED_DECOMPRESS_LOG_FID CACHED_DECOMPRESS_MAX_SIZE
1 test, 1 passed, 0 known failure, 0 skipped
[inst/test_ncarray.m]

/<>/inst/test_ncarray.m

* test
test_ncarray()
creating directory /tmp/oct-n6O7Cg for temporary files.

All tests passed.
1 test, 1 passed, 0 known failure, 0 skipped
Checking C++ files ...
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault
make: *** [debian/rules:5: binary] Error 139
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.


Processed: Re: Bug#1057590: octave-netcdf: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + upstream confirmed
Bug #1057590 [src:octave-netcdf] octave-netcdf: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Added tag(s) upstream and confirmed.
> forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Bug #1057590 [src:octave-netcdf] octave-netcdf: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?64999'.

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



Bug#1057590: octave-netcdf: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-08 Thread Rafael Laboissière

Control: tags -1 + upstream confirmed
Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?64999

* Santiago Vila  [2023-12-05 23:08]:


Package: src:octave-netcdf
Version: 1.0.17-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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

[snip] 
fatal: caught signal Segmentation fault -- stopping myself... 
Segmentation fault


Thanks for the bug report. It seems to be an upstream problem. I have 
forwarded the bug to the upstream developers.


Best,

Rafael Laboissière



Bug#1032104: Fixed in 4.19.301, 5.10.203, 6.1.66

2023-12-08 Thread Salvatore Bonaccorso
So the fix landed as well in 5.10.203 and 6.1.66 in particular, will
add a respective closer for this bug with those rebases. This means
the update will be in the next upload rebasing at least to those
versions (it was too late for the next round of point release for
bookworm).



Processed: tagging 1057730

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1057730 + ftbfs
Bug #1057730 [src:python-jellyfish] python-jellyfish ftbfs in unstable 
(dpkg-buildpackage -B)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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



Processed: your mail

2023-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> owner 1055701 !
Bug #1055701 [src:pycifrw] pycifrw ftbfs with Python 3.12 (test failures)
Owner recorded as Andrius Merkys .
> forwarded 1055701 https://github.com/jamesrhester/pycifrw/pull/6
Bug #1055701 [src:pycifrw] pycifrw ftbfs with Python 3.12 (test failures)
Set Bug forwarded-to-address to 
'https://github.com/jamesrhester/pycifrw/pull/6'.
> tags 1055701 + patch
Bug #1055701 [src:pycifrw] pycifrw ftbfs with Python 3.12 (test failures)
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#1057265: marked as done (cron: Uncheck return values of set*id() family functions)

2023-12-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Dec 2023 09:18:05 +0100
with message-id 
and subject line Re: Bug#1057265: cron: Uncheck return values of set*id() 
family functions
has caused the Debian Bug report #1057265,
regarding cron: Uncheck return values of set*id() family functions
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.)


-- 
1057265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-149
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: georg...@debian.org

Hi,

Both setuid() and setgid() return values are not checked in cron's code used to 
execute user-provided commands:

do_command.c:
> 63 static void
> 64 child_process(entry *e, user *u) {
> ...
> 243 setgid(e->pwd->pw_gid);
> 244 initgroups(usernm, e->pwd->pw_gid);
> 245 #if (defined(BSD)) && (BSD >= 199103)
> 246 setlogin(usernm);
> 247 #endif /* BSD */
> 248 setuid(e->pwd->pw_uid); /* we aren't root after this... */
> 249
> 250 #endif /* LOGIN_CAP */

man 2 setuid() states the following:

> RETURN VALUE
>   On success, zero is returned.  On error, -1 is returned, and errno is 
> set to indicate the error.
>
>   Note: there are cases where setuid() can fail even when the caller is 
> UID 0; it is a grave security error to omit checking for a failure return 
> from setuid().

In the unlikely event where setuid() (or setgid()) fails, privileges of cron 
would not be dropped and commands would be run as root. 
This would lead to privilege escalation.

The attached patch fixes this by aborting execution when such an event occurs.

Regards,


-- Package-specific info:
--- EDITOR:


--- /usr/bin/editor:
/usr/bin/nano

--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 43648 Jul 25  2022 /usr/bin/crontab

--- /var/spool/cron:
drwxr-xr-x 5 root root 4096 Jun 27 17:17 /var/spool/cron

--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 4096 Jul 25  2022 /var/spool/cron/crontabs

--- /etc/cron.d:
drwxr-xr-x 2 root root 4096 Jun 29 15:08 /etc/cron.d

--- /etc/cron.daily:
drwxr-xr-x 2 root root 4096 Jun 16 17:34 /etc/cron.daily

--- /etc/cron.hourly:
drwxr-xr-x 2 root root 4096 Aug  8  2022 /etc/cron.hourly

--- /etc/cron.monthly:
drwxr-xr-x 2 root root 4096 Nov 30  2022 /etc/cron.monthly

--- /etc/cron.weekly:
drwxr-xr-x 2 root root 4096 Oct 30  2022 /etc/cron.weekly


-- System Information:
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
Release:2022.3
Codename:   kali-rolling
Architecture: x86_64

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

Versions of packages cron depends on:
ii  cron-daemon-common   3.0pl1-149
ii  init-system-helpers  1.64+kali2
ii  libc62.36-9
ii  libpam-runtime   1.5.2-6
ii  libpam0g 1.5.2-6
ii  libselinux1  3.4-1+b5
ii  lsb-base 11.2
ii  sensible-utils   0.0.17

Versions of packages cron recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.96-14

Versions of packages cron suggests:
pn  anacron
pn  checksecurity  
ii  logrotate  3.20.1-1

Versions of packages cron is related to:
pn  libnss-ldap   
pn  libnss-ldapd  
pn  libpam-ldap   
pn  libpam-mount  
pn  nis   
pn  nscd  

-- no debconf information
>From 42309c1fdcc192f356c84221954331b4e64be29e Mon Sep 17 00:00:00 2001
From: Jeffrey Bencteux 
Date: Fri, 1 Dec 2023 12:27:21 +0100
Subject: [PATCH] fix unchecked set*id() return values

In the unlikely event where setuid() (or setgid()) fails, privileges of cron 
would not be dropped and commands would be run as root.
This would lead to privilege escalation. The below patch fixes this by aborting 
execution when such an event occurs.

Signed-off-by: Jeffrey Bencteux 
---
 do_command.c | 18 +++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/do_command.c b/do_command.c
index 4083c32..db5227f 100644
--- a/do_command.c
+++ b/do_command.c
@@ -28,7 +28,7 @@ static char rcsid[] = "$Id: do_command.c,v 2.12 1994/01/15 
20:43:43 vixie Exp $"
 #if defined(SYSLOG)
 # include 
 #endif
-
+#include 
 
 static voidchild_process __P((entry *, user *)),
do_univ __P((user *));
@@ -206,11 +206,23 @@ child_process(e, u)
/* set