Bug#1049872: FTBFS on multiple release architectures

[Andrius Merkys]

Hi Emanuele,

On 2023-09-05 16:58, Emanuele Rocca wrote:

On 2023-08-28 07:42, Andrius Merkys wrote:

On Wed, 16 Aug 2023 14:29:10 +0200 Emanuele Rocca  wrote:

asmjit does not build correctly on the following architectures:
armel, armhf, mips64el, mipsel, s390x.


Does this constitute an RC bug? If not, severity should be lowered.


It does, on armel and armhf the package did build successfully in the
past. See:

https://buildd.debian.org/status/logs.php?pkg=asmjit=armhf
https://buildd.debian.org/status/logs.php?pkg=asmjit=armel


This is news to me. Could you please point out where in Debian Policy I 
can read more about such requirement? I thought I saw packages dropping 
support for one or another release architecture without being removed 
from testing.



Bug retitled given that meanwhile the issue has been fixed on mips64el,
mipsel, and s390x.


This is correct, thanks.

Best wishes,
Andrius

Processed: set forward URL for 1049872

[Debian Bug Tracking System]

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

> forwarded 1049872 https://github.com/asmjit/asmjit/issues/74
Bug #1049872 [src:asmjit] asmjit: FTBFS on armel and armhf
Set Bug forwarded-to-address to 'https://github.com/asmjit/asmjit/issues/74'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1051510: searx: SearX upstream is no longer maintained

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1051510 [src:searx] searx: SearX upstream is no longer maintained
Severity set to 'serious' from 'normal'

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

Bug#1035366: marked as done (pytorch-ignite: FTBFS: py3versions: empty set of versions)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2023 01:49:45 +
with message-id 
and subject line Bug#1035366: fixed in pytorch-ignite 0.4.12-1
has caused the Debian Bug report #1035366,
regarding pytorch-ignite: FTBFS: py3versions: empty set of versions
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.)


-- 
1035366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch-ignite
Version: 0.4.3-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-torch-ignite


pytorch-ignite FTBFS in sid (it builds fine in bullseye):

 fakeroot debian/rules clean
dh clean -Spybuild --with python3
   dh_auto_clean -O-Spybuild
py3versions: empty set of versions
E: py3versions failed at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 53.
make: *** [debian/rules:5: clean] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: pytorch-ignite
Source-Version: 0.4.12-1
Done: Mo Zhou 

We believe that the bug you reported is fixed in the latest version of
pytorch-ignite, 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.
Mo Zhou  (supplier of updated pytorch-ignite 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 Sep 2023 21:18:54 -0400
Source: pytorch-ignite
Architecture: source
Version: 0.4.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team 

Changed-By: Mo Zhou 
Closes: 1035366
Changes:
 pytorch-ignite (0.4.12-1) unstable; urgency=medium
 .
   * New upstream version 0.4.12
   * Bump X-Python3-Version to 3.11. (Closes: #1035366)
Checksums-Sha1:
 13b3843002e2530d485dedb18d696f35b8978dbf 2239 pytorch-ignite_0.4.12-1.dsc
 d0e22b676c72ad24dd4bca971566ded0a7a79fc2 7338331 
pytorch-ignite_0.4.12.orig.tar.gz
 582bca9b7c38455d206acc493f38856d5b0b3cb1 2232 
pytorch-ignite_0.4.12-1.debian.tar.xz
 71c131882ebe4577be23527013d4ac403e977939 9801 
pytorch-ignite_0.4.12-1_source.buildinfo
Checksums-Sha256:
 a6911cb67dea5b254b75df92962ef17489ada6ff9d2c5c47103eb51d0da59179 2239 
pytorch-ignite_0.4.12-1.dsc
 7d10fd40edc568bbda687151bb5b53b0d59a980cd6c25ec2b061e7f234aeab76 7338331 
pytorch-ignite_0.4.12.orig.tar.gz
 b602527b0ebfd7d381fcada899d308628f2d66a0cc5da09716647906e0de9a6a 2232 
pytorch-ignite_0.4.12-1.debian.tar.xz
 9cc34929eaaeb55e1810cd1d764df5b8542896c72439e835812eeac09090b132 9801 
pytorch-ignite_0.4.12-1_source.buildinfo
Files:
 087f2ad9bc3192cd8b31938b9f54f3be 2239 science optional 
pytorch-ignite_0.4.12-1.dsc
 e86b4ca029b05a4e313074e8b19047b6 7338331 science optional 
pytorch-ignite_0.4.12.orig.tar.gz
 da065fdb1005b523f9e4de44dea7644a 2232 science optional 
pytorch-ignite_0.4.12-1.debian.tar.xz
 2df3464b87eb0494e2ab225315b1cce4 9801 science optional 
pytorch-ignite_0.4.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmT7yDgRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaoojtw/9HY6bdMFSVk5erlQpLLeuSexZEY+gz5IC
HjAwV93k8OJ5/gmg/Llfn0uhjKtdNUsKau4TQxc97+w5I3lrGHFs7Q4O310Z1oIY
RA/sbp911w+pl/dCYXBsWpO1gzpjNN3EnCQeLOiNxNjxEGmkR7TjstgExjqK8ZaN
CFp+jqebE+EAs3LEYVsnLlJ2u5UCN5vvE43UntLWqxSfUYz3tdRxe+92b6Q3c6LX
mviiWZoc3qLC63t8LD3P5xtT9o5d+9mfIPRV93ymbcoHZAiGlBcDPCPxSG9MUyQ5
VGpLBlrqJcCEbdXTrTPIuyauwULhz4OO0jL9bkX+2mrxXWdI8TSZNUSc6SYFXOWy
MAk145y//DedHyKBMB1gCsVWbIaqIfhqJAae1ubfilUCwHCkS5PQTjalPU82FqBm
LlfcMky/hNzPi7clYQyll6J7o4xchzQTyF5LtDuqdMIJWpb5i+ZGaAjbA05Kupsf
lLqcCJzMuV4k5d5wXeVHXgu4Md6bS9KuwLhUZErM4mH5wYp6GfQ4/iigJmY0PWJb
jH0MeUJmkCRPR929rN2x1UzW88u6rI/tdyvV+t+YP63M2j2BVgrFKyBE3ZGYrCUe
sPz48LbNeeLl5EBCXTy+xysVLos5Nd7s/q9WutkR3YJR7ojAEFoeH1aHXpCjjthf
QYyXvEyXFBg=
=+mvW
-END PGP SIGNATURE End Message ---

Bug#1051496: mailgraph: does not support the new syslog format

[Vincent Lefevre]

Control: tags -1 patch upstream

On 2023-09-08 19:30:29 +0200, Vincent Lefevre wrote:
> mailgraph no longer works after the upgrade to bookworm, and
> this is probably due to the fact that it does not support the
> new syslog format: /usr/sbin/mailgraph contains
[...]
> and this format is no longer correct.
> 
> There's a git repository where this bug seems to have been fixed
> 5 years ago:
> 
>   https://gist.github.com/mdklapwijk/4f8d2fc39f09f4aa615cbf8ffae0379a

I've attached a patch based on these modifications.
I've made 2 changes:
  * This patch does not add a new type "rsyslog" for this new format;
so both formats are supported at the same time.
  * Fixed a variable name ($mon → $montxt) for the old format.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: support the rsyslog high-precision timestamp format.
 Patch based on M.D. Klapwijk's modifications for this support:
   https://gist.github.com/mdklapwijk/4f8d2fc39f09f4aa615cbf8ffae0379a
 (with some changes).
Author: Vincent Lefevre 
Bug-Debian: https://bugs.debian.org/1051496
Last-Update: 2023-09-09

--- mailgraph.pl.bak
+++ mailgraph.pl
@@ -202,27 +202,41 @@
 }
 my $file = $self->{file};
 line: while(defined (my $str = $self->_next_line)) {
-# date, time and host 
-$str =~ /^
-(\S{3})\s+(\d+)  # date  -- 1, 2
-\s
-(\d+):(\d+):(\d+)# time  -- 3, 4, 5
-(?:\s<\w+\.\w+>)?# FreeBSD's verbose-mode
-\s
-([-\w\.\@:]+)# host  -- 6
-\s+
-(?:\[LOG_[A-Z]+\]\s+)?  # FreeBSD
-(.*) # text  -- 7
-$/x or do
-{
-warn "WARNING: line not in syslog format: $str";
-next line;
-};
-my $mon = $months_map{$1};
-defined $mon or croak "unknown month $1\n";
-$self->_year_increment($mon);
+# date, time and host
+my ($year, $mon, $day, $hour, $min, $sec, $host, $text);
+if(($year, $mon, $day, $hour, $min, $sec, $host, $text) = $str =~ /^
+(\d+)-(\d+)-(\d+)T(\d+):(\d+):(\d+)\S+  # datetime
+\s+
+(\S+)   # host
+\s+
+(.*)# text
+$/x) {
+$mon--;
+$self->{year} = $year;
+}
+else {
+my $montxt;
+($montxt, $day, $hour, $min, $sec, $host, $text) = $str =~ /^
+(\S{3})\s+(\d+)  # date
+\s
+(\d+):(\d+):(\d+)# time
+(?:\s<\w+\.\w+>)?# FreeBSD's verbose-mode
+\s
+([-\w\.\@:]+)# host
+\s+
+(?:\[LOG_[A-Z]+\]\s+)?  # FreeBSD
+(.*) # text
+$/x or do
+{
+warn "WARNING: line not in syslog format: $str";
+next line;
+};
+$mon = $months_map{$montxt};
+defined $mon or croak "unknown month $montxt\n";
+$self->_year_increment($mon);
+}
 # convert to unix time
-my $time = $self->str2time($5,$4,$3,$2,$mon,$self->{year}-1900,$self->{GMT});
+my $time = $self->str2time($sec,$min,$hour,$day,$mon,$self->{year}-1900,$self->{GMT});
 if(not $self->{allow_future}) {
 # accept maximum one day in the present future
 if($time - time > 86400) {
@@ -230,7 +244,6 @@
 next line;
 }
 }
-my ($host, $text) = ($6, $7);
 # last message repeated ... times
 if($text =~ /^(?:last message repeated|above message repeats) (\d+) time/) {
 next line if defined $self->{repeat} and not $self->{repeat};

Processed: Re: mailgraph: does not support the new syslog format

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch upstream
Bug #1051496 [mailgraph] mailgraph: does not support the new syslog format
Added tag(s) upstream and patch.

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

Bug#1051521: rust-palette: autopkgtest failures

[Jeremy Bícha]

Source: rust-palette
Version: 0.7.3+dfsg-1
Severity: serious

rust-palette is unable to migrate to Testing because its
autopkgtests are failing.

https://qa.debian.org/excuses.php?package=rust-palette

Thank you,
Jeremy Bícha

Bug#1051519: rust-async-task: autopkgtest failures

[Jeremy Bícha]

Source: rust-async-task
Version: 4.4.0-2
Severity: serious

rust-async-task is unable to migrate to Testing because its
autopkgtests are failing.

https://qa.debian.org/excuses.php?package=rust-async-task

Thank you,
Jeremy Bícha

Bug#1050299: [Pkg-rust-maintainers] Bug#1050299: rust-webpki: RUSTSEC-2023-0052

[Peter Green]

I think this indicates that it can indeed be safely removed from Debian? I'm
CC'ing developers that have made uploads to this packages in the past for
additiponal opinions as I suspect the issue is more subtle than that.


dak rm does not take account of virtual packages. So for rust packages
it is generally useless.

In terms of reverse dependencies, a number have already moved to the fork
rustls-webpki. However there are still a few left. Specifically
rust-async-tls, rust-trust-dns-proto and rust-trust-dns-client.

async-tls has not switched upstream. On the other hand I don't
see any packages in Debian using it yet. ccing mjt to see what
the reason for packaging it was.

trust-dns-proto and trust-dns-server have switched upstream, however
updating the trust-dns-packages has proved a bit more involved than
I would have liked. I pushed my current efforts to the branch
trust-dns-0.23 in the debcargo-conf repo.

The main thing left to deal with regarding the trust-dns is
aardvark-dns, the code changes needed were beyond my skills,
so I reported an issue upstream. Upstream has come up with
a patch but has not merged it yet.

https://github.com/containers/aardvark-dns/pull/381

Bug#1051031: marked as done (libvmime: build-depends on old libgsasl7-dev)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 22:35:12 +
with message-id 
and subject line Bug#1051031: fixed in libvmime 0.9.2-8.1
has caused the Debian Bug report #1051031,
regarding libvmime: build-depends on old libgsasl7-dev
to be marked as done.

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

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


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

Source: libvmime
Version: 0.9.8-8
Severity: Serious
tags: patch

Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev
$ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control

Should be enough to fix the issue.

G.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libvmime
Source-Version: 0.9.2-8.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated libvmime 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Sep 2023 00:08:37 +0200
Source: libvmime
Built-For-Profiles: noudeb
Architecture: source
Version: 0.9.2-8.1
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Gianfranco Costamagna 
Closes: 1051031
Changes:
 libvmime (0.9.2-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change libgsasl7-dev into libgsasl-dev following Debian
 package renaming (Closes: #1051031)
Checksums-Sha1:
 a9cd2a5b284531f743bccdd26ed3227d18e7254a 2170 libvmime_0.9.2-8.1.dsc
 0493f58cb846b8f2eb997d4576e01615ca6701ed 13680 libvmime_0.9.2-8.1.debian.tar.xz
 fb02f055ab5e226a94c9cde7c75f263875d09f7f 18115 
libvmime_0.9.2-8.1_source.buildinfo
Checksums-Sha256:
 1f9ff74efa1d18b66df55443c0638eaaf5ee5827c8335c6655cf4af75004beca 2170 
libvmime_0.9.2-8.1.dsc
 5d53336ebc436a5fae4adc2e030da01058ed3c594c8f2984e509d33068267081 13680 
libvmime_0.9.2-8.1.debian.tar.xz
 3570304ea4d5cff6d2b24e0d0a1cb14c6f18fb66a32bd522ed86503e5d73e7f7 18115 
libvmime_0.9.2-8.1_source.buildinfo
Files:
 151b0c1883c503e46bdabe08227dbc88 2170 libs optional libvmime_0.9.2-8.1.dsc
 a84f5f5582fcbdec608930b09430dab1 13680 libs optional 
libvmime_0.9.2-8.1.debian.tar.xz
 1e861cbd3401872417213d2913036e54 18115 libs optional 
libvmime_0.9.2-8.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmT4+I4ACgkQ808JdE6f
XdlJNA//cRNBf5GJyzELy3PD+buIdbeHm2hwWKELeDL1i+Q/1ElqMBJrXkVNcceT
ztEGik5vqf7hfp1IrFesko9uQ7cUZUuwIRrXmRut811KpaMzcnUDud3pltCGxVtW
47AtzXjP5yjZCwj5Joe7wFjeZvxLa0GAoDSl3x0F0HjguP4Sx18sZOaHvkJr3tgM
4ucK6cXXWrlBMSg5RtJla5ISt9n0jqk9qlX9VuRfLfr+vaTDfwh004w8dBnC8jlf
PjqkatES96/hzpqugvM7KXtFSAXxZ7PC9Xh9c0JcnqdSPXbI8OzhqeGU+yjfxkL0
TZPN4uyyOkAWbfRFQK6qgWkCl/meNmWNjVGn/AUCd93XEqpmlmNz/m9QgN9NQiup
zEke9TbVHwbF6gpNrSi8u2F6KrqYFcWTeSzehNwBuZUEGl/ZZj84I+aTun2M87FO
QLMW1Air4xeitiGSh795R7Pw3UkFlKIuYmQkKhrcnELxaJf384f28+HlCz6kNyTj
AIULpTBd3y9lRNaV+0KxpqVtWjgY/JoH9+oeqMjGGyRdwlHFeDLeeDbzy4NPyRXV
FOaIXZ3aZ96ERqCcjwfPw7l9ZssG4BlS7dsiOqIjm2CVLg8FGJSUdksq0kgQzecj
IXt4wxlMMO+tU1IxCFzXhdpLFNASQl/v5/agvqcS0a3hVJMekmw=
=sJCE
-END PGP SIGNATURE End Message ---

Bug#1051392: marked as done (Crash on unaligned reads on 32-bit arm architectures)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 22:21:18 +
with message-id 
and subject line Bug#1051392: fixed in victoriametrics 1.79.14+ds1-1
has caused the Debian Bug report #1051392,
regarding Crash on unaligned reads on 32-bit arm architectures
to be marked as done.

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

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


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

Package: victoria-metrics
Version: 1.79.5+ds1-2+b5
Severity: grave

victoria-metrics v1.79.5 randomly crashes on aligned reads file reads, 
rendering it more or less unusable.
 
Sep  7 08:46:31 localhost victoria-metrics[17179]: unexpected fault address 0x0

Sep  7 08:46:31 localhost kernel: [233869.646841] Alignment trap: not handling 
instruction ed9c0b00 at [<005af9bc>]
Sep  7 08:46:31 localhost kernel: [233869.646882] 8<--- cut here ---
Sep  7 08:46:31 localhost kernel: [233869.646887] Unhandled fault: alignment 
exception (0x001) at 0x02153612
Sep  7 08:46:31 localhost kernel: [233869.646898] [02153612] *pgd=3ea5d831
Sep  7 08:46:31 localhost victoria-metrics[17179]: fatal error: fault
Sep  7 08:46:31 localhost victoria-metrics[17179]: [signal SIGBUS: bus error 
code=0x1 addr=0x0 pc=0x5af9c0]
Sep  7 08:46:31 localhost victoria-metrics[17179]: goroutine 28 [running]:
Sep  7 08:46:31 localhost victoria-metrics[17179]: runtime.throw({0x6abcef, 
0x5})
Sep  7 08:46:31 localhost victoria-metrics[17179]: #011runtime/panic.go:1047 
+0x4c fp=0x24993b4 sp=0x24993a0 pc=0x50424
Sep  7 08:46:31 localhost victoria-metrics[17179]: runtime.sigpanic()
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
#011runtime/signal_unix.go:832 +0xac fp=0x24993cc sp=0x24993b4 pc=0x69fc8
Sep  7 08:46:31 localhost victoria-metrics[17179]: math.IsNaN(...)
Sep  7 08:46:31 localhost victoria-metrics[17179]: #011math/bits.go:39
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql.removeEmptySeries(...)
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
#011github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql/exec.go:157
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql.timeseriesToResult({0x21fe3b0,
 0x1, 0x2}, 0x1)
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
#011github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql/exec.go:99 
+0x610 fp=0x24994ac sp=0x24993d0 pc=0x5af9c0
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql.Exec(0x0, 
0x28c6540, {0x201f325, 0x1a}, 0x0)
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
#011github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/promql/exec.go:58 
+0x2ec fp=0x2499584 sp=0x24994ac pc=0x5aebbc
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/prometheus.queryRangeHandler(0x0,
 {0xc1368159f7200fc8, 0x299f41302, 0xb5cc08}, {0x81ffbc, 0x292a320}, 
{0x201f325, 0x1a}, 0x18a6b9c9ae0, 0x18a6bb93718, ...)
Sep  7 08:46:31 localhost victoria-metrics[17179]: 
#011github.com/VictoriaMetrics/VictoriaMetrics/app/vmselect/prometheus/prometheus.go:840
 +0x5f4 fp=0x2499748 sp=0x2499584 pc=0x5ea4cc
[...]

Seehttps://github.com/VictoriaMetrics/VictoriaMetrics/pull/3927  for more 
details on the issue.

The bug has already been patched upstream and an LTS release (v1.79.11) has 
been made in March, along with other important 
fixes:https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.11  
.

This is on an armhf box (hardkernel odroid-c1) running Debian 12.1, kernel 
6.1.0-11-armmp, fully up to date.

Steps to reproduce:
- run victoria-metrics on a 32-bit arm system,
- ingest a small amount of data (my data directory is less than 10MB),
- query the data with e.g. grafana, by zooming in and moving the observed time 
window.
Querying with some automated script should also work as all that needs to be 
done is to cause an unaligned read on disk, which is a naturally occurring 
condition due to how datapoints are stored and compressed.


Would it be possible to upgrade to that LTS release?

Thanks in advance,
-Simon

--
Simon Vetter
--- End Message ---
--- Begin Message ---
Source: victoriametrics
Source-Version: 1.79.14+ds1-1
Done: Guillem Jover 

We believe that the bug you reported is fixed in the latest version of
victoriametrics, 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, 

Bug#1050299: rust-webpki: RUSTSEC-2023-0052

[Reinhard Tartler]

Hi Salvatore,

thanks for filing this bug.

> Please see https://rustsec.org/advisories/RUSTSEC-2023-0052.html .

This page is giving a very general description of the problem:

>> When this crate is given a pathological certificate chain to validate, it
>> will spend CPU time exponential with the number of candidate certificates at
>> each step of path building.

>>Both TLS clients and TLS servers that accept client certificate are affected.


The page is also indicating that the issue was fixed in version 0.22.1, hence,
I've packaged that version and closed this bug. While this might not address
all concerns, (at least https://github.com/briansmith/webpki/issues/69
indicates that there is more work to do),
https://github.com/briansmith/webpki/issues/69#issuecomment-1699894848
indicates:


>> There is a webpki 0.22.1 release that implements the signature count 
>> mitigation.


Additional, you are asking:

> Should rust-webpki be removed from Debian testing and unstable?

```
siretart@coccia:~$ dak rm -nR  rust-webpki
Will remove the following packages from unstable:

librust-webpki-dev |   0.22.0-2 | amd64, arm64, armel, armhf, i386
rust-webpki |   0.22.0-2 | source

Maintainer: Debian Rust Maintainers 


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.
```

I think this indicates that it can indeed be safely removed from Debian? I'm
CC'ing developers that have made uploads to this packages in the past for
additiponal opinions as I suspect the issue is more subtle than that.

-rt

Bug#1050592: marked as done (perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 20:50:10 +
with message-id 
and subject line Bug#1050592: fixed in glibc 2.37-8
has caused the Debian Bug report #1050592,
regarding perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking 
libfile-fcntllock-perl
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.)


-- 
1050592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.36.0-8
Severity: serious
X-Debbugs-Cc: debian-powe...@lists.debian.org
Control: affects -1 libfile-fcntllock-perl

Hi,

debugging an unexpected autopkgtest failure of
libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found
it's because the old perl binary (5.36.0-7) was built with the fcntl(2)
constant F_GETLK == 12, but the new one with F_GETLK == 5 [2].

There are no source or build system changes in perl that would have caused
this change. The failure is currently blocking perl testing migration,
so filing at 'serious'.

Perl is built with -D_FILE_OFFSET_BITS=64, and I see that on bullseye
this causes F_GETLK == F_GETLK64 == 12, but on bookworm and later
F_GETLK == 5 while F_GETLK64 == 12 [3]. I didn't find the exact
change that caused this yet.

As can be expected from the above, building libfile-fcntllock-perl on
bookworm against perl_5.36.0-7 makes it fail its test suite in a similar
way. And rebuilding it on sid against perl_5.36.0-8 makes it pass.

On amd64 the constants have stayed equal (== 5) from bullseye to sid,
and _FILE_OFFSET_BITS=64 doesn't affect them. What's the deal on ppc64el?

Copying the powerpc porters list. Could you please look into this?

[1] 
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/libf/libfile-fcntllock-perl/34669085/log.gz
[2] perl -MPOSIX -E 'say F_GETLK'
[3] printf '#include \nF_GETLK\nF_GETLK64\n' | cpp 
-D_FILE_OFFSET_BITS=64 | tail -2

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.37-8
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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 Sep 2023 20:39:29 +0200
Source: glibc
Architecture: source
Version: 2.37-8
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 874160 1050592
Changes:
 glibc (2.37-8) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/libc0.3.symbols.hurd-i386: Update symbols.
   * debian/patches/hurd-i386/git-jemalloc.diff: Add support for static TSD
 data.
   * debian/patches/hurd-i386/git-jemalloc2.diff: Initialize ___pthread_self
 early.
   * debian/patches/hurd-i386/git-error_t.diff: Make error_t an int on C++.
   * debian/patches/hurd-i386/git-tls_dtors.diff: Fix TLS destructors.
   * debian/patches/hurd-i386/git-main_stack.diff: Fix stack information for 
main
 thread.
 .
   [ Aurelien Jarno ]
   * debian/patches/local-disable-tst-bz29951.diff: removed, obsolete.
   * debian/patches/any/git-c-utf-8-language.diff: backport support from
 upstream to treat C. locale like C locale.  Closes: #874160.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix the value of F_GETLK/F_SETLK/F_SETLKW with __USE_FILE_OFFSET64 on
   ppc64el.  Closes: #1050592.
 - debian/patches/hurd-i386/git-exception-long.diff: upstreamed.
Checksums-Sha1:
 281c5bcc99ab244917948931b1fcea2542cc713c 8959 glibc_2.37-8.dsc
 b6974d62862ea092732c0ff897265d2a5f6944bb 399620 glibc_2.37-8.debian.tar.xz
 91fdbff276dc463895ac7a2f1f579a0df384e412 9641 glibc_2.37-8_source.buildinfo
Checksums-Sha256:
 f5dcb3ed9d8a6a1bc207c5c1f5f4c64b0550fc5f5c5e0eac947e3c3eaea7b6e9 8959 
glibc_2.37-8.dsc
 107e483c57ab96d13f2b705d10daf86efca8fd9585737af5413babbfa9a2e258 399620 
glibc_2.37-8.debian.tar.xz
 950a0889d30edd24f7f1b4443c239af95ab4fe5d648d1740dafbc2e38a1f3b37 9641 
glibc_2.37-8_source.buildinfo

Bug#1051287: marked as done (pike8.0-core: undeclared file conflict with former pike8.0-pcre)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 20:42:42 +
with message-id 
and subject line Bug#1051287: fixed in pike8.0 8.0.1738-1.2
has caused the Debian Bug report #1051287,
regarding pike8.0-core: undeclared file conflict with former pike8.0-pcre
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.)


-- 
1051287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike8.0-core
Version: 8.0.1738-1.1
Severity: serious
Control: affects -1 + pike8.0-pcre
User: debian...@lists.debian.org
Usertags: fileconflict

pike8.0-core now installs /usr/lib/pike8.0/modules/_Regexp_PCRE.pmo and
/usr/lib/pike8.0/modules/Regexp_PCRE.so. These files happen to also
be installed into former versions of pike8.0-pcre. Thus upgrades can
cause an unpack error if the new pike8.0-core is unpacked before
pike8.0-pcre is removed. There are no Replaces, Conflicts or diversions
averting this scenario.

Helmut
--- End Message ---
--- Begin Message ---
Source: pike8.0
Source-Version: 8.0.1738-1.2
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated pike8.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Sep 2023 22:00:09 +
Source: pike8.0
Architecture: source
Version: 8.0.1738-1.2
Distribution: unstable
Urgency: medium
Maintainer: Magnus Holmgren 
Changed-By: Bastian Germann 
Closes: 1051287
Changes:
 pike8.0 (8.0.1738-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Do not install former pike8.0-pcre files into -core (Closes: #1051287).
Checksums-Sha1:
 152ff503b2c6cabeff0ce4bd79a3e9ff722937d3 3396 pike8.0_8.0.1738-1.2.dsc
 2d1c4dbef2712871e2b64b1820fc9bc9b19251e3 37768 
pike8.0_8.0.1738-1.2.debian.tar.xz
 ababd523ca8a78af5680ddf4693d0b4c522e1f3c 15905 
pike8.0_8.0.1738-1.2_source.buildinfo
Checksums-Sha256:
 1478b90ee3df92d32fd90db0fb48dad12c9abab267bad082129ffb20560d1ece 3396 
pike8.0_8.0.1738-1.2.dsc
 0990fe7aa5f22ae1b183f50823c26035e2577c87c6c33b48698d1dbe71f30db9 37768 
pike8.0_8.0.1738-1.2.debian.tar.xz
 ecf2e2898808ddb9b78e39dea74c8844f289be5eaa4b2c0a1f14cdfc80bf6fec 15905 
pike8.0_8.0.1738-1.2_source.buildinfo
Files:
 113f9498b4d7a22689d652ae49ba5855 3396 interpreters optional 
pike8.0_8.0.1738-1.2.dsc
 d7f5e303c214be94672418711a037c52 37768 interpreters optional 
pike8.0_8.0.1738-1.2.debian.tar.xz
 d699dfdeea437d68d6c6697806534b12 15905 interpreters optional 
pike8.0_8.0.1738-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmT7fEYQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFI4PDACKq1RyRpOHPhbIiOJg4EIk6HlE9zLnPII6
IErtL5FFDEyJINCDaUncc1/6wITcEKj7xGhovE1Gr1bKek8KvkiMjzHM0jZmkVH1
ug9DKqdrUNMz+irA6b5sMRRl/gkAmLOUJm+GvbO9fBM926wEVQ8Akr2W1cdmF+L0
y92MMThI/S7fTcGtQ4pZLLp8IlY4Bdh3zWFAh6L5Q61jyPKNSbCxdXmEKYrvFKoD
l1Ubr1vSNaHpZAktsbc9mCErDib5ylzy7FhXrlq0uOn+StImB4CPfJg5j0QB+2hV
t9BgtFIlFGfwBMI2KhHmRX87DaUOTxPKbYOYwM9gjPlfqFmUF1oLeixwkHRTUOMF
P+y9SU1lbSEca0jNAuwQlzcgJBm8kH++hxbqBJAXvtI0wVD2oNe7hLnqr+kRMOE4
FWzM52OaTOAcuiqhdEItU9sISi2RLLeQ4ukLTTOGcOexcNmRc1e+G+nV5fLyNo6Z
JvOKXEvM28tcW9YVofGZCAUBB+2P6+o=
=ROTf
-END PGP SIGNATURE End Message ---

Bug#1050592: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1050592 in glibc 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/glibc-team/glibc/-/commit/8a21102fffcf626f090aed44604b04809a8aa808


debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - Fix the value of F_GETLK/F_SETLK/F_SETLKW with __USE_FILE_OFFSET64 on
ppc64el.  Closes: #1050592.
  - debian/patches/hurd-i386/git-exception-long.diff: upstreamed.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050592

Processed: Bug#1050592 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050592 [libc6-dev] perl: F_GETLK / F_GETLK64 confusion on ppc64el 
breaking libfile-fcntllock-perl
Added tag(s) pending.

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

Bug#1051355: Processed: your mail

[Leandro Cunha]

Hi,

On Fri, Sep 8, 2023 at 4:39 PM Andres Salomon  wrote:
>
>
>
> On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha 
>  wrote:
>
> Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System 
>  wrote:
>
> Processing commands for cont...@bugs.debian.org: > affects 1051355 phpsysinfo 
> phpldapadmin jquery-timepicker Bug #1051355 [chromium] chromium: Segmentation 
> fault Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
> jquery-timepicker > stop Stopping processing here. Please contact me if you 
> need assistance. -- 1051355: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355 Debian Bug Tracking 
> System Contact ow...@bugs.debian.org with problems
>
> Apparently this should have been fixed in version 117.0.5938.48-1, if you 
> want to release this version in beta stage as a distro they are making which 
> is Arch and we can test it on Debian. 
> https://archlinux.org/packages/extra/x86_64/chromium/ 
> https://repology.org/project/chromium/versions
> --
> Cheers, Leandro Cunha
>
>
>
> Do you have a crbug or commit or something that fixes it? I haven't started 
> on 117 yet, and I also haven't really had time to debug this sid-specific 116 
> crash (other than building with downgraded packages from 9/1 and still 
> getting the crash). This was a bad week for finding free time.
>
> Tim, I don't suppose you've looked at 117 yet? There's an early release out.
>
>

This version is expected to be released on September 12th and we can
wait. I believe it must have also been compiled for Linux with the
current changes.
https://chromiumdash.appspot.com/schedule

-- 
Cheers,
Leandro Cunha

Bug#1051287: NMU 8.0.1738-1.2

[Bastian Germann]

I am uploading a NMU to fix this.diff -Nru pike8.0-8.0.1738/debian/changelog pike8.0-8.0.1738/debian/changelog
--- pike8.0-8.0.1738/debian/changelog   2023-08-22 11:50:42.0 +
+++ pike8.0-8.0.1738/debian/changelog   2023-09-06 22:00:09.0 +
@@ -1,3 +1,10 @@
+pike8.0 (8.0.1738-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not install former pike8.0-pcre files into -core (Closes: #1051287).
+
+ -- Bastian Germann   Wed, 06 Sep 2023 22:00:09 +
+
 pike8.0 (8.0.1738-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pike8.0-8.0.1738/debian/rules pike8.0-8.0.1738/debian/rules
--- pike8.0-8.0.1738/debian/rules   2018-06-23 23:06:03.0 +
+++ pike8.0-8.0.1738/debian/rules   2023-09-06 22:00:09.0 +
@@ -117,6 +117,7 @@
--without-fftw \
--without-libpdf \
--without-libpanda \
+   --without-libpcre \
--without-GTK \
--without-GTK2 \
--without-bundles \
@@ -190,6 +191,7 @@
 
 #  Some cleaning
find "$(TMP)$(lib_prefix)" -name '.autodoc' -type f -exec rm -f '{}' ';'
+   find "$(TMP)$(lib_prefix)" -name '*Regexp_PCRE.*' -type f -delete
 
install -d -m755 $(TMP)/usr/share/pixmaps
install -m644 debian/pike.xpm $(TMP)/usr/share/pixmaps/$(PIKE).xpm

Bug#1051355: Processed: your mail

[Andres Salomon]

On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha 
 wrote:

Hi,

On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System
mailto:ow...@bugs.debian.org>> wrote:


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


 > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker
 Bug #1051355 [chromium] chromium: Segmentation fault
 Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
jquery-timepicker

 > stop
 Stopping processing here.

 Please contact me if you need assistance.
 --
 1051355: 
 Debian Bug Tracking System
 Contact ow...@bugs.debian.org  with 
problems


Apparently this should have been fixed in version 117.0.5938.48-1, if
you want to release this version in beta stage as a distro they are
making which is Arch and we can test it on Debian.



--
Cheers,
Leandro Cunha



Do you have a crbug or commit or something that fixes it?  I haven't 
started on 117 yet, and I also haven't really had time to debug this 
sid-specific 116 crash (other than building with downgraded packages 
from 9/1 and still getting the crash). This was a bad week for finding 
free time.


Tim, I don't suppose you've looked at 117 yet? There's an early release 
out.

Bug#1051504: salt: CVE-2023-20897 CVE-2023-20898

[Salvatore Bonaccorso]

Source: salt
Version: 3004.1+dfsg-2.2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for salt.

CVE-2023-20897[0]:
| Salt masters prior to 3005.2 or 3006.2 contain a DOS in minion
| return. After receiving several bad packets on the request server
| equal to the number of worker threads, the master will become
| unresponsive to return requests until restarted.


CVE-2023-20898[1]:
| Git Providers can read from the wrong environment because they get
| the same cache directory base name in Salt masters prior to 3005.2
| or 3006.2. Anything that uses Git Providers with different
| environments can get garbage data or the wrong data, which can lead
| to wrongful data disclosure, wrongful executions, data corruption
| and/or crash.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-20897
https://www.cve.org/CVERecord?id=CVE-2023-20897
[1] https://security-tracker.debian.org/tracker/CVE-2023-20898
https://www.cve.org/CVERecord?id=CVE-2023-20898
[2] https://saltproject.io/security-announcements/2023-08-10-advisory/

Regards,
Salvatore

Bug#1051355: Processed: your mail

[Leandro Cunha]

Hi,

On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System
 wrote:
>
> Processing commands for cont...@bugs.debian.org:
>
> > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker
> Bug #1051355 [chromium] chromium: Segmentation fault
> Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
> jquery-timepicker
> > stop
> Stopping processing here.
>
> Please contact me if you need assistance.
> --
> 1051355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Apparently this should have been fixed in version 117.0.5938.48-1, if
you want to release this version in beta stage as a distro they are
making which is Arch and we can test it on Debian.
https://archlinux.org/packages/extra/x86_64/chromium/
https://repology.org/project/chromium/versions

-- 
Cheers,
Leandro Cunha

Processed: severity of 1033316 is serious

[Debian Bug Tracking System]

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

> severity 1033316 serious
Bug #1033316 [src:ruby-moneta] Autopkgtest is flaky
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1042911: marked as done (Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 17:49:00 +
with message-id 
and subject line Bug#1042911: fixed in muse-el 3.20+dfsg-8
has caused the Debian Bug report #1042911,
regarding Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open 
load file: No such file or directory, assoc
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.)


-- 
1042911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-muse
Version: 3.20+dfsg-7
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since upgrading to Emacs 29.1, byte-(re-)compilation fails as follows:

[…]
Install elpa-muse for emacs
install/muse-3.20: Handling install of emacsen flavor emacs
install/muse-3.20: byte-compiling for emacs

In toplevel form:
cgi.el:71:2: Warning: Package cl is deprecated
cgi.el:87:13: Warning: Unknown defun property ‘character’

In cgi-decode-string:
cgi.el:94:4: Warning: ‘do’ is an obsolete alias (as of 27.1); use ‘cl-do’ 
instead.
cgi.el:101:15: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.
cgi.el:108:17: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.

In cgi-decode:
cgi.el:124:6: Warning: ‘flet’ is an obsolete macro (as of 24.3); use either 
‘cl-flet’ or ‘cl-letf’.

In cgi-arguments:
cgi.el:161:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use ‘cl-loop’ 
instead.

In end of data:
cgi.el:197:16: Warning: the function ‘calendar-current-date’ might not be 
defined at runtime.

In toplevel form:
htmlize-hack.el:12:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use 
‘cl-loop’ instead.
htmlize-hack.el:17:8: Warning: ‘reduce’ is an obsolete function (as of 27.1); 
use ‘cl-reduce’ instead.

In muse-backlink-insert-hook-func:
muse-backlink.el:264:12: Warning: ‘font-lock-fontify-buffer’ is for interactive 
use only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.

In end of data:
muse-backlink.el:313:33: Warning: the function ‘muse-make-link’ might not be 
defined at runtime.

In toplevel form:
muse-colors.el:60:2: Warning: custom-declare-variable 
`muse-colors-autogen-headings' docstring has wrong usage of unescaped single 
quotes (use \= or different
 quoting)
muse-colors.el:94:2: Warning: custom-declare-variable 
`muse-colors-inline-image-method' docstring has wrong usage of unescaped single 
quotes (use \= or differ
ent quoting)

In muse-colors-region:
muse-colors.el:577:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-unhighlight-region:
muse-colors.el:732:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-colors-lisp-tag:
muse-colors.el:775:30: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-docbook-markup-paragraph:
muse-docbook.el:233:41: Warning: ‘muse-looking-back’ called with 1 argument, 
but requires 2 or 3

In toplevel form:
muse-html.el:67:2: Warning: custom-declare-variable `muse-html-style-sheet' 
docstring wider than 80 characters
muse-html.el:96:2: Warning: custom-declare-variable `muse-xhtml-style-sheet' 
docstring wider than 80 characters
muse-html.el:399:2: Warning: custom-declare-variable 
`muse-html-meta-content-encoding' docstring has wrong usage of unescaped single 
quotes (use \= or differe
nt quoting)
muse-html.el:421:2: Warning: custom-declare-variable 
`muse-html-src-allowed-modes' docstring has wrong usage of unescaped single 
quotes (use \= or different q
uoting)

In muse-html-markup-paragraph:
muse-html.el:490:6: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-html-src-tag:
muse-html.el:670:16: Warning: ‘font-lock-fontify-buffer’ is for interactive use 
only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: Unknown defun property ‘character’
../../elpa-src/muse-3.20/cgi.el: Warning: ‘do’ is an obsolete alias (as of 
27.1); use ‘cl-do’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘flet’ is an obsolete macro (as of 
24.3); use either ‘cl-flet’ 

Bug#1051496: mailgraph: does not support the new syslog format

[Vincent Lefevre]

Package: mailgraph
Version: 1.14-20
Severity: grave
Justification: renders package unusable

mailgraph no longer works after the upgrade to bookworm, and
this is probably due to the fact that it does not support the
new syslog format: /usr/sbin/mailgraph contains

sub _next_syslog($)
{
[...]
line: while(defined (my $str = $self->_next_line)) {
# date, time and host 
$str =~ /^
(\S{3})\s+(\d+)  # date  -- 1, 2
\s
(\d+):(\d+):(\d+)# time  -- 3, 4, 5
(?:\s<\w+\.\w+>)?# FreeBSD's verbose-mode
\s
([-\w\.\@:]+)# host  -- 6
\s+
(?:\[LOG_[A-Z]+\]\s+)?  # FreeBSD
(.*) # text  -- 7
$/x or do
{
warn "WARNING: line not in syslog format: $str";
next line;
};

and this format is no longer correct.

There's a git repository where this bug seems to have been fixed
5 years ago:

  https://gist.github.com/mdklapwijk/4f8d2fc39f09f4aa615cbf8ffae0379a

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

Kernel: Linux 6.1.0-11-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailgraph depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  init-system-helpers1.65.2
ii  libfile-tail-perl  1.3-7
ii  librrds-perl   1.7.2-4+b8
ii  lsb-base   11.6
ii  perl   5.36.0-7
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1

Versions of packages mailgraph recommends:
ii  apache2 [httpd] 2.4.57-2
ii  postfix [mail-transport-agent]  3.7.6-0+deb12u2

mailgraph suggests no packages.

-- debconf information:
  mailgraph/start_on_boot: true
  mailgraph/ignore_localhost: false
  mailgraph/mail_log: /var/log/mail.log

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Error while importing Python "lensfun" module

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #1050998 [python3-lensfun] Error while importing Python "lensfun" module
Added tag(s) moreinfo and unreproducible.
> severity -1 important
Bug #1050998 [python3-lensfun] Error while importing Python "lensfun" module
Severity set to 'important' from 'serious'

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

Bug#1050998: Error while importing Python "lensfun" module

[Sebastiaan Couwenberg]

Control: tags -1 moreinfo unreproducible
Control: severity -1 important

On Fri, 1 Sep 2023 10:40:47 +0200 Thierry Florac wrote:

I just installed the package "python3-lensfun" on Debian testing.
When trying to import the module, an error occurs:

*> python3*
Python 3.9.15 (main, Nov 21 2022, 16:07:38)


Your python is old, 3.11 is the default in trixie & sid.


[GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import lensfun
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'lensfun'
>>>


Works just fine in a trixie chroot:

# python3
Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import lensfun
>>> print(lensfun)



The same error occurs when trying to launch the "lensfun-update-data"
command line tool.


That also just works:

# lensfun-update-data
Reading http://lensfun.sourceforge.net/db/versions.json …
Reading http://wilson.bronger.org/lensfun-db/versions.json …
Successfully updated the database in /var/lib/lensfun-updates/version_1.


/usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info
/usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/PKG-INFO
/usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/dependency_links.txt
/usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/top_level.txt


lensfun was built for python3.11 and you're using 3.9.15 which was never 
in Debian, 3.9.13 was the most recent python3.9.


Kind Regards,

Bas

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

Processed: Re: Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

[Debian Bug Tracking System]

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

> severity 1036737 normal
Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8 is not co-installable with 
libsoapysdr0.7
Severity set to 'normal' from 'serious'
> tags 1036737 - patch
Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8 is not co-installable with 
libsoapysdr0.7
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

[Andreas Bombe]

severity 1036737 normal
tags 1036737 - patch
thanks

[resend just to the bug because it was still archived before]

On Thu, May 25, 2023 at 03:08:22AM +0200, Andreas Beckmann wrote:
> The soapysdr library stacks from bullseye and bookworm are not
> co-installable, but the transitive conflict behind longer dependency
> chains is not always easy detectable by apt. Therefore several upgrade
> paths result in old libraries being kept installed and some upgradable
> packages being kept at an older version.

It is unfortunate that I neglected the package at that time and did not
look at the underlying issue. I reverted the Breaks added in the team
upload now, in any case.

The SoapySDR library and module packages are designed to be
co-installable across SONAME versions and if something prevents that it
is an issue that needs fixing. Could you tell me what the specific
issue was that prevented co-installation?

Bug#1051493: ghc: FTBFS with a GHC newer than 9.0.2

[Ilias Tsitsimpis]

Source: ghc
Version: 9.4.6-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

The current version of GHC in unstable (9.4.6-1) FTBFS when the
bootstrap compiler is newer than 9.0.2.

The error message is the following:

  ghc.mk:141: *** The make build system requires a boot compiler older
  than ghc-9.2. Your boot compiler is too new and cannot be used to
  build ghc-9.4 with make. Either boot with ghc 9.0.2 or build with
  hadrian. See
  https://www.haskell.org/ghc/blog/20220805-make-to-hadrian.html for
  advice on transitioning to hadrian..  Stop.

We need to switch to the newer hadrian build system in order to be able
to build ghc with a newer bootstrap compiler.

For more information about why the make build system fails, see the
upstream issue https://gitlab.haskell.org/ghc/ghc/-/issues/21188.

Thanks,

-- 
Ilias

Bug#1051484: marked as done (dose3 FTBFS with ocamlgraph 2.0.0)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 16:19:12 +
with message-id 
and subject line Bug#1051484: fixed in dose3 7.0.0-4
has caused the Debian Bug report #1051484,
regarding dose3 FTBFS with ocamlgraph 2.0.0
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=dose3=amd64=7.0.0-3%2Bb1=1694182045=0

...
==
FAIL: runTest (__main__.DoseTests.runTest)
Test : ceve_cone_dot
Group : ceve
Cmd : ./src/applications/ceve.exe -T dot -c 2to3 
deb://tests/DebianPackages/Packages_20201226T144309Z_amd64.xz
Expected file : tests/applications/dose-tests/ceve_cone_dot

--
Traceback (most recent call last):
  File "/<>/_build/default/src/applications/dose-tests.py", line 
238, in runTest
test_application(self, self.expected, self.cmd, self.difftype, 
self.exitcode)
  File "/<>/_build/default/src/applications/dose-tests.py", line 
195, in test_application
self.assertTrue(d)
AssertionError: False is not true

==
FAIL: runTest (__main__.DoseTests.runTest)
Test : ceve_cone_multiarch_dot
Group : ceve
Cmd : ./src/applications/ceve.exe -T dot -c 2to3:amd64 --deb-native-arch amd64 
-t deb tests/DebianPackages/Packages_20201226T144309Z_amd64.xz
Expected file : tests/applications/dose-tests/ceve_cone_multiarch_dot

--
Traceback (most recent call last):
  File "/<>/_build/default/src/applications/dose-tests.py", line 
238, in runTest
test_application(self, self.expected, self.cmd, self.difftype, 
self.exitcode)
  File "/<>/_build/default/src/applications/dose-tests.py", line 
195, in test_application
self.assertTrue(d)
AssertionError: False is not true

--
Ran 49 tests in 43.658s

FAILED (failures=2)
make[1]: *** [debian/rules:40: override_dh_auto_test-arch] Error 1
--- End Message ---
--- Begin Message ---
Source: dose3
Source-Version: 7.0.0-4
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated dose3 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 Sep 2023 17:55:57 +0200
Source: dose3
Architecture: source
Version: 7.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1051484
Changes:
 dose3 (7.0.0-4) unstable; urgency=medium
 .
   * Team upload
   * Fix tests with ocamlgraph 2.1.0 (Closes: #1051484)
Checksums-Sha1:
 90d551b4c85b61fc47867015c025134867831382 2636 dose3_7.0.0-4.dsc
 290ad2b4eb90e3c973e89fa83288cdd7ef5a251a 20256 dose3_7.0.0-4.debian.tar.xz
Checksums-Sha256:
 31008bce0ca1da03bca0a775273c8bc9e9a204e8c8c2505b01d64824749928dc 2636 
dose3_7.0.0-4.dsc
 491446825463580bc4eb6883d3d9e3ebc8af0e4018a59ce07926aa961f081f44 20256 
dose3_7.0.0-4.debian.tar.xz
Files:
 53de707d6fc8e7d167954f95535bc507 2636 ocaml optional dose3_7.0.0-4.dsc
 eaf375f51ecd61085c73d6b932a34134 20256 ocaml optional 
dose3_7.0.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmT7RbYSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBP18IAJxw28zqRV7QZqcDb/yDVKDcWzVu2RFp
ZUwdyqycPhRs8nQ6Gw1RF2mwixvWsq0sklbd3QWjywek9NNVO/sz1N7zgZuU+xB+
4v35Se3tymcsyWIJizZJf6H983O1sTj9i+ti1uZ2+v1N/m9UOMNcQNK/KhCKyLd/
n+nQsqPXiGj6Kpavb27yubiEcKlJhlma4O2vzuLJWwQYaG767rDFb/rGYtVrtMem
eNM8Vjg/m/UEwJcyLFZTBbVralrazyxgIivOA5WDgurnaGnRllVkLTCe0zeOERSy
2DdAQ1Awbj/1aftXAKtuoS99Lag95Qa6NO3wNGkssdLnIRU/MYfbSpI=
=nTy2
-END PGP SIGNATURE End Message ---

Bug#1050433: marked as done (src:sqlgrey: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 16:06:31 +
with message-id 
and subject line Bug#1050433: fixed in sqlgrey 1:1.8.0-5.1
has caused the Debian Bug report #1050433,
regarding src:sqlgrey: fails to migrate to testing for too long
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.)


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

Source: sqlgrey
Version: 1:1.8.0-4
Severity: serious
Control: close -1 1:1.8.0-5
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:sqlgrey has been trying to migrate for 35 
days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=sqlgrey



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sqlgrey
Source-Version: 1:1.8.0-5.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated sqlgrey package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2023 17:07:36 +0200
Source: sqlgrey
Architecture: source
Version: 1:1.8.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Antonin Kral 
Changed-By: Paul Gevers 
Closes: 1050433
Changes:
 sqlgrey (1:1.8.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1050433)
Checksums-Sha1:
 41fb801dfca251112baf9b75d16ee09f0358afd8 1622 sqlgrey_1.8.0-5.1.dsc
 1ffd888aaca5e3b6738ac8386c0334ec34a62b3b 6408 sqlgrey_1.8.0-5.1.debian.tar.xz
Checksums-Sha256:
 773a5a3f1c01c698fb1bdd744f2a8866594d7c96cb6940da69131efe1adbfdcc 1622 
sqlgrey_1.8.0-5.1.dsc
 33af04c48db7266de7093a3dad469e5999199985541e11df2befe67dbc3303af 6408 
sqlgrey_1.8.0-5.1.debian.tar.xz
Files:
 f18bb6a3e8df92fbfbe1eead005a9ba4 1622 mail optional sqlgrey_1.8.0-5.1.dsc
 45372ddf1ccc1533a52e6ae66e0d0401 6408 mail optional 
sqlgrey_1.8.0-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmTncmYACgkQnFyZ6wW9
dQq0gwgAtoN350ZlWF/jHhJo0zgceqNFkBfXcLfcbwGyvken4/XwCiBVoTXJhqYq
WOg1AV+n8mFOqOtvgS/Nko+66vAkMLaffBLaSKb2qCdGsuM0nLKHzDAaZPR6L5aQ
o2UqzRYP8KvFR6akkkBqsuy2YHQTZhxBvbCiozOiDumMmNrETAS5Dx7e1Ry5T1w3
kIog+4R3IvJVDpDPo+ejjAuPLI/s7ELzMkdSmXyKiwrOA9cAMqVBYLoPYHQ8tG+6
1NqeJMvImrQn/+/N7pzdjqHrFZMrsCxajEbXbZfqT7vnS+6MU6ncMwfS8gZ7XC52
7md2RrRDT57sLU3a15kXm3vzkcAGvA==
=ihuE
-END PGP SIGNATURE End Message ---

Bug#1050299: marked as done (rust-webpki: RUSTSEC-2023-0052)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 16:06:25 +
with message-id 
and subject line Bug#1050299: fixed in rust-webpki 0.22.1-1
has caused the Debian Bug report #1050299,
regarding rust-webpki: RUSTSEC-2023-0052
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.)


-- 
1050299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-webpki
Version: 0.22.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

Please see https://rustsec.org/advisories/RUSTSEC-2023-0052.html .

FWIW, there is a fix in the rustls-webpki is a fork, which is actively
maintained.

Should rust-webpki be removed from Debian testing and unstable?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: rust-webpki
Source-Version: 0.22.1-1
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated rust-webpki 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 Sep 2023 11:51:40 -0400
Source: rust-webpki
Architecture: source
Version: 0.22.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Reinhard Tartler 
Closes: 1050299
Changes:
 rust-webpki (0.22.1-1) unstable; urgency=medium
 .
   * Team upload.
   * Package webpki 0.22.1 from crates.io using debcargo 2.6.0
   * Fix for: RUSTSEC-2023-0052, Closes:  #1050299
Checksums-Sha1:
 ff3431acaa20e92b2a722788bce310d6afa2a465 2280 rust-webpki_0.22.1-1.dsc
 30ed5b47c57ad06dc6f9d8187419df0137ebcaca 59573 rust-webpki_0.22.1.orig.tar.gz
 508fdba2ace90ac69d6d2bc0ddd2bbc511f9149e 3760 
rust-webpki_0.22.1-1.debian.tar.xz
 d8ebbbaadf767ef6b602501d990eb8aa650e0522 7810 
rust-webpki_0.22.1-1_source.buildinfo
Checksums-Sha256:
 d9260da2fe75bf2e225ec4996682c6c24a8383e129db955771f14eb2860f05f7 2280 
rust-webpki_0.22.1-1.dsc
 f0e74f82d49d545ad128049b7e88f6576df2da6b02e9ce565c6f533be576957e 59573 
rust-webpki_0.22.1.orig.tar.gz
 64261abe95a38936b33897e5606e34d89787ceda64287ab799a57622483389c5 3760 
rust-webpki_0.22.1-1.debian.tar.xz
 ddca096b787e95c0c815c6556af9d7ce9ef80087c43c972ef0525903a1771327 7810 
rust-webpki_0.22.1-1_source.buildinfo
Files:
 0e19ebc8e6143e5118b0b1f8d22fb5bd 2280 rust optional rust-webpki_0.22.1-1.dsc
 000579b8d9651f1e28bb6f5a30bc8b7a 59573 rust optional 
rust-webpki_0.22.1.orig.tar.gz
 86dfa49f3e786d63021ed3313dd0ee0a 3760 rust optional 
rust-webpki_0.22.1-1.debian.tar.xz
 e37fc1ad5a31611d00cb00b326e77283 7810 rust optional 
rust-webpki_0.22.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmT7QxcUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsugExAAmuf509OiRE5sg3aOZY/Ime7fM80M
sjfwUdJNR+Fs2fHgYE99dtm8M7DPZFy5LAj1JZ3dTK1kMsDqZm0HxTe9rjAvhEn+
j3EcY+5Uoe/K7Iuk+1rqY8K7+7RhC4KBBNqVyFy6Xd5j61RC5jbWarayDyJVdXlo
9bcU0qFFKbyhwDLSlfLo6UssxSn84/HYZBSQdXVKcwTLw+DD+M6gpWpp6BgNusQZ
lHncsKb2kL4IdN09TaEhUXJcuPUddayVurj841pzPaZAmeZRzpJpGqlVq8sXnbhE
t5woIjKUg5dqv/3UKQVQBf8QztHNTcaNbXJRRPSDvpO3Rk7zYi//Wi719zga2RxC
dRX4Sczr6E7tWcv9JLcl8zNKvzOCdtbNix+W/8PWGUvqN3FGhOlogDWIGG/ZzJyd
fdoZTiCq2AbYivYs7ys+yj5VhqHiThb0+MUS4aJeIkFIQHYNIUx4VKg+VniiOVOP
05zXqKLgIIBqm38dcHE/l2/NYIn4L4v3XnP1ApGkf67A4HL8IeoWYFUvTAPA0P8O
OjVHisPyfEkEfh/RA2NvQfHIseaKE4lAPWQF1r0jxvSUVPThB2w4ySEOi5bAaqYh
Gya4GYeJ/3RV75dszUUb9a/jsKR5kGy0dp5u3MlkUdXErJKPJ41IVXbJF2uA5hQn
qUD5dMbx0Fl6Cv4=
=yxQE
-END PGP SIGNATURE End Message ---

Processed: Bug#1051484 marked as pending in dose3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051484 [src:dose3] dose3 FTBFS with ocamlgraph 2.0.0
Added tag(s) pending.

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

Bug#1051484: marked as pending in dose3

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #1051484 in dose3 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/ocaml-team/dose3/-/commit/33bd9726f19e3e163b79e6df6d4805d77bda47f1


Fix tests with ocamlgraph 2.1.0 (Closes: #1051484)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051484

Bug#1051475: marked as done (ledit: can't be built with arch:all+any)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 15:35:15 +
with message-id 
and subject line Bug#1051475: fixed in ledit 2.04-7
has caused the Debian Bug report #1051475,
regarding ledit: can't be built with arch:all+any
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.)


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

Source: ledit
Version: 2.04-6
Severity: serious

Hello, for some reasons, building ledit with arch:all + arch:any produces a 
ledit binary with an additional dependency
on libstdlib-ocaml-lqmb5
This makes the arch:all package not binNMU safe, and then RC buggy.

I think, for an arch:all package binary depending on shlibs:Depends and 
ocaml:Depends is a little bit strange

Package: ledit
Architecture: all
Depends:
 ${ocaml:Depends},
 ${misc:Depends},
 ${shlibs:Depends}


I don't honestly know if we have to convert ledit into an arch:all package, or 
to stop adding ocaml:Depends on it.

G.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ledit
Source-Version: 2.04-7
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ledit 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 Sep 2023 17:15:06 +0200
Source: ledit
Architecture: source
Version: 2.04-7
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1051475
Changes:
 ledit (2.04-7) unstable; urgency=medium
 .
   * Make ledit an arch:any package (Closes: #1051475)
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 c1a7ed9d7e53d64598c87c5af92d23749d0c8277 1841 ledit_2.04-7.dsc
 ea68899711cbb49740f21eb67734e90cde93247c 7092 ledit_2.04-7.debian.tar.xz
Checksums-Sha256:
 af24a8632c051eae44af816d98e9788145ac678cfb1e2883ea827fd354afcab9 1841 
ledit_2.04-7.dsc
 f82f1474882b7647dc981277d941529b4204697d08e2691653df8e5eae19eb26 7092 
ledit_2.04-7.debian.tar.xz
Files:
 84c73d89b0ae39f3e8a377a1d8772823 1841 editors optional ledit_2.04-7.dsc
 e535e8bfb950a58f7f20a7ffb09a5381 7092 editors optional 
ledit_2.04-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmT7O/0SHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBuQMH/3rz8p9/KU+Dg5vXKbIMI8Sphd/KTMkU
pfpPRkwLKZP3GDxn08T3V9mmvAUKvtmmDWY81SehvBjOeS5EDWEl6zh49o1bjESM
nSrs/EDgjD0xZ8eUfLVJ5sMgmLfeeVXTuuHEAr17yovyT5V8LE/h70qsQzxSp5VU
SXgaR1u601Uu03OcUQkfiGiSsHI/rumLw+PEu4qK1daPCjCFFRcRentD3V474bDb
8QvvOcoTHKUJDb/aEtxMpJzWZ4mo5QH9OgssxBQguLComgwIS7cSy9qJGmQnmc4r
Nwkx1GJ+kUlVd87vll1YMVv5zbo0t3fw1oulC/2uDV5uQilxx7u0JjQ=
=0r6Y
-END PGP SIGNATURE End Message ---

Processed (with 1 error): Re: Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

[Debian Bug Tracking System]

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

> unarchive 1036737
Bug #1036737 {Done: Andreas Beckmann } [libsoapysdr0.8] 
libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from 
bullseye
Unarchived Bug 1036737
> reopen 1036737
Bug #1036737 {Done: Andreas Beckmann } [libsoapysdr0.8] 
libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from 
bullseye
'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 soapysdr/0.8.1-3.
> retitle 1036737 libsoapysdr0.8 is not co-installable with libsoapysdr0.7
Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8: please add Breaks: libsoapysdr0.7 
for smoother upgrades from bullseye
Changed Bug title to 'libsoapysdr0.8 is not co-installable with libsoapysdr0.7' 
from 'libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades 
from bullseye'.
> severity normal
Unknown command or malformed arguments to command.
> tags 1036737 + moreinfo
Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8 is not co-installable with 
libsoapysdr0.7
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Bug#1051475 marked as pending in ledit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051475 [src:ledit] ledit: can't be built with arch:all+any
Added tag(s) pending.

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

Bug#1051475: marked as pending in ledit

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #1051475 in ledit 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/ocaml-team/ledit/-/commit/eaf1f8a1b07a097e3fc4a8d98d2f5065a583b05b


Make ledit an arch:any package (Closes: #1051475)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051475

Bug#1051485: frama-c FTBFS with why3 1.6.0

[Adrian Bunk]

Source: frama-c
Version: 20220511-manganese-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=frama-c=amd64=20220511-manganese-4%2Bb5=1694181938=0

...
File "src/plugins/wp/ProverWhy3.ml", line 1129, characters 12-36:
1129 |   let drv = Why3.Whyconf.load_driver (Why3.Whyconf.get_main config)
   
Error: Unbound value Why3.Whyconf.load_driver
make[1]: *** [share/Makefile.generic:77: src/plugins/wp/ProverWhy3.cmo] Error 2

Bug#1051484: dose3 FTBFS with ocamlgraph 2.0.0

[Adrian Bunk]

Source: dose3
Version: 7.0.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dose3=amd64=7.0.0-3%2Bb1=1694182045=0

...
==
FAIL: runTest (__main__.DoseTests.runTest)
Test : ceve_cone_dot
Group : ceve
Cmd : ./src/applications/ceve.exe -T dot -c 2to3 
deb://tests/DebianPackages/Packages_20201226T144309Z_amd64.xz
Expected file : tests/applications/dose-tests/ceve_cone_dot

--
Traceback (most recent call last):
  File "/<>/_build/default/src/applications/dose-tests.py", line 
238, in runTest
test_application(self, self.expected, self.cmd, self.difftype, 
self.exitcode)
  File "/<>/_build/default/src/applications/dose-tests.py", line 
195, in test_application
self.assertTrue(d)
AssertionError: False is not true

==
FAIL: runTest (__main__.DoseTests.runTest)
Test : ceve_cone_multiarch_dot
Group : ceve
Cmd : ./src/applications/ceve.exe -T dot -c 2to3:amd64 --deb-native-arch amd64 
-t deb tests/DebianPackages/Packages_20201226T144309Z_amd64.xz
Expected file : tests/applications/dose-tests/ceve_cone_multiarch_dot

--
Traceback (most recent call last):
  File "/<>/_build/default/src/applications/dose-tests.py", line 
238, in runTest
test_application(self, self.expected, self.cmd, self.difftype, 
self.exitcode)
  File "/<>/_build/default/src/applications/dose-tests.py", line 
195, in test_application
self.assertTrue(d)
AssertionError: False is not true

--
Ran 49 tests in 43.658s

FAILED (failures=2)
make[1]: *** [debian/rules:40: override_dh_auto_test-arch] Error 1

Bug#1051475: ledit: can't be built with arch:all+any

[Stéphane Glondu]

Le 08/09/2023 à 15:53, Gianfranco Costamagna a écrit :
Hello, for some reasons, building ledit with arch:all + arch:any 
produces a ledit binary with an additional dependency

on libstdlib-ocaml-lqmb5
This makes the arch:all package not binNMU safe, and then RC buggy.

I think, for an arch:all package binary depending on shlibs:Depends and 
ocaml:Depends is a little bit strange


Package: ledit
Architecture: all
Depends:
  ${ocaml:Depends},
  ${misc:Depends},
  ${shlibs:Depends}


I don't honestly know if we have to convert ledit into an arch:all 
package, or to stop adding ocaml:Depends on it.


dh_ocaml + arch:all has always been shaky, I think it's better to make 
ledit an arch:any package (I did it for ocamlwc recently).



Cheers,

--
Stéphane

Bug#1050688: marked as done (poetry: needs internet access during build?)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 14:41:39 +
with message-id 
and subject line Bug#1050688: fixed in poetry 1.6.1+dfsg-1
has caused the Debian Bug report #1050688,
regarding poetry: needs internet access during build?
to be marked as done.

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

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


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

Source: poetry:
Version: 1.5.1+dfsg-4
Severity: serious

Hello, this looks similar to #1031444 but with different test log, so I prefer 
to open a new defect.
The issue however might be linked, due to the fact that poetry looks doing some 
remote connections to github
during testsuite run.
If you disable internet access you might see that the package FTBFS

dpkg-buildpackage: info: source package poetry
dpkg-buildpackage: info: source version 1.5.1+dfsg-3
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from poetry-1.5.1+dfsg/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
 debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:291: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11_poetry
* Building wheel...
Successfully built poetry-1.5.1-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with 
"installer" module
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11_poetry/build; 
python3.11 -m pytest --ignore=tests/console/commands/env/test_list.py 
--ignore=tests/console/commands/env/test_remove.py 
--ignore=tests/console/commands/env/test_use.py --ignore=tests/utils/test_env.py 
--ignore=tests/config/test_config.py --ignore=tests/utils/test_helpers.py -k 'not 
test_self_update_should_install_all_necessary_elements and not 
test_add_file_constraint_sdist and not test_add_file_constraint_sdist_old_installer and not 
test_builder_setup_generation_runs_with_pip_editable and not test_publish_dry_run and not 
test_info_from_sdist and not test_installer_can_install_dependencies_from_forced_source and 
not test_search_for_file_sdist and not test_search_for_file_sdist_with_extras and not 
test_solver_can_resolve_sdist_dependencies and not 
test_solver_can_resolve_sdist_dependencies_with_extras and not 
test_solver_chooses_from_correct_repository_if_forced and not 
test_solver_chooses_from_correct_repository_if_forced_and_transitive_dependency and not 
test_solver_does_not_choose_from_secondary_repository_by_default and not 
test_solver_chooses_from_secondary_if_explicit and not 
test_get_package_information_fallback_read_setup and not 
test_get_package_information_skips_dependencies_with_invalid_constraints and not 
test_get_package_retrieves_packages_with_no_hashes and not 
test_fallback_can_read_setup_to_get_dependencies and not 
test_exporter_can_export_requirements_txt_with_file_packages and not 
test_exporter_can_export_requirements_txt_with_file_packages_and_markers and not 
test_lock_no_update and not test_locker_dumps_dependency_information_correctly and not 
test_package_partial_yank and not test_run_installs_with_same_version_url_files and not 
test_env_info_displays_complete_info and not test_skip_existing_output and not 
test_installer_should_use_the_locked_version_of_git_dependencies_with_extras and not 
test_installer_should_use_the_locked_version_of_git_dependencies_without_reference and not 
test_installer_uses_prereleases_if_they_are_compatible and not 
test_requirement_git_subdirectory and not test_check_valid and not test_check_invalid and 
not test_packages_property_returns_empty_list and not test_parse_dependency_specification 
and not test_info_setup_missing_mandatory_should_trigger_pep517 and not 
test_uninstall_git_package_nspkg_pth_cleanup and not 
test_executor_should_write_pep610_url_references_for_directories and not 
test_executor_should_write_pep610_url_references_for_git and not 

Bug#1050687: marked as done (poetry: needs internet access during build?)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 14:41:39 +
with message-id 
and subject line Bug#1050688: fixed in poetry 1.6.1+dfsg-1
has caused the Debian Bug report #1050688,
regarding poetry: needs internet access during build?
to be marked as done.

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

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


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

Source: poetry:
Version: 1.5.1+dfsg-4
Severity: serious

Hello, this looks similar to #1031444 but with different test log, so I prefer 
to open a new defect.
The issue however might be linked, due to the fact that poetry looks doing some 
remote connections to github
during testsuite run.
If you disable internet access you might see that the package FTBFS

dpkg-buildpackage: info: source package poetry
dpkg-buildpackage: info: source version 1.5.1+dfsg-3
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from poetry-1.5.1+dfsg/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
 debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:291: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11_poetry
* Building wheel...
Successfully built poetry-1.5.1-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with 
"installer" module
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11_poetry/build; 
python3.11 -m pytest --ignore=tests/console/commands/env/test_list.py 
--ignore=tests/console/commands/env/test_remove.py 
--ignore=tests/console/commands/env/test_use.py --ignore=tests/utils/test_env.py 
--ignore=tests/config/test_config.py --ignore=tests/utils/test_helpers.py -k 'not 
test_self_update_should_install_all_necessary_elements and not 
test_add_file_constraint_sdist and not test_add_file_constraint_sdist_old_installer and not 
test_builder_setup_generation_runs_with_pip_editable and not test_publish_dry_run and not 
test_info_from_sdist and not test_installer_can_install_dependencies_from_forced_source and 
not test_search_for_file_sdist and not test_search_for_file_sdist_with_extras and not 
test_solver_can_resolve_sdist_dependencies and not 
test_solver_can_resolve_sdist_dependencies_with_extras and not 
test_solver_chooses_from_correct_repository_if_forced and not 
test_solver_chooses_from_correct_repository_if_forced_and_transitive_dependency and not 
test_solver_does_not_choose_from_secondary_repository_by_default and not 
test_solver_chooses_from_secondary_if_explicit and not 
test_get_package_information_fallback_read_setup and not 
test_get_package_information_skips_dependencies_with_invalid_constraints and not 
test_get_package_retrieves_packages_with_no_hashes and not 
test_fallback_can_read_setup_to_get_dependencies and not 
test_exporter_can_export_requirements_txt_with_file_packages and not 
test_exporter_can_export_requirements_txt_with_file_packages_and_markers and not 
test_lock_no_update and not test_locker_dumps_dependency_information_correctly and not 
test_package_partial_yank and not test_run_installs_with_same_version_url_files and not 
test_env_info_displays_complete_info and not test_skip_existing_output and not 
test_installer_should_use_the_locked_version_of_git_dependencies_with_extras and not 
test_installer_should_use_the_locked_version_of_git_dependencies_without_reference and not 
test_installer_uses_prereleases_if_they_are_compatible and not 
test_requirement_git_subdirectory and not test_check_valid and not test_check_invalid and 
not test_packages_property_returns_empty_list and not test_parse_dependency_specification 
and not test_info_setup_missing_mandatory_should_trigger_pep517 and not 
test_uninstall_git_package_nspkg_pth_cleanup and not 
test_executor_should_write_pep610_url_references_for_directories and not 
test_executor_should_write_pep610_url_references_for_git and not 

Processed: Bug#1050688 marked as pending in poetry

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050688 [src:poetry] poetry: needs internet access during build?
Bug #1050687 [src:poetry] poetry: needs internet access during build?
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1050688: marked as pending in poetry

[Emmanuel Arias]

Control: tag -1 pending

Hello,

Bug #1050688 in poetry 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/poetry/-/commit/e51299f5cc6c02a94da3bef35649bfdbf80ce5d9


d/rules: override dh_auto_test to avoid remove egg-info folder. Some poetry 
tests use egg-info folders created for tests purpose as fixtures (Closes: 
#1050688).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050688

Bug#1051475: ledit: can't be built with arch:all+any

[Gianfranco Costamagna]

Source: ledit
Version: 2.04-6
Severity: serious

Hello, for some reasons, building ledit with arch:all + arch:any produces a 
ledit binary with an additional dependency
on libstdlib-ocaml-lqmb5
This makes the arch:all package not binNMU safe, and then RC buggy.

I think, for an arch:all package binary depending on shlibs:Depends and 
ocaml:Depends is a little bit strange

Package: ledit
Architecture: all
Depends:
 ${ocaml:Depends},
 ${misc:Depends},
 ${shlibs:Depends}


I don't honestly know if we have to convert ledit into an arch:all package, or 
to stop adding ocaml:Depends on it.

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051474: libreoffice: Please add embeded code copies to embeded-code-copies on security tracker debian.tar.xz/tarballs

[Bastien Roucariès]

Source: libreoffice
Severity: serious
Tags: security
Justification: Document embdeded code copy + copyright
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

Could you document that you embded a few tar ball under the security tracker ?
For oldstable/stable/unstable

Version should be documented.

Moreover you do not document where you downloaded these file a comment under
copyright will be helpful (README.source say how to retrieve it not the link to
get).

Thanks

Bastien


-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 6.4.0-3-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 1051355 phpsysinfo phpldapadmin jquery-timepicker
Bug #1051355 [chromium] chromium: Segmentation fault
Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
jquery-timepicker
> stop
Stopping processing here.

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

Processed: bug 1051454 is forwarded to https://code.videolan.org/rist/librist/-/issues/169

[Debian Bug Tracking System]

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

> # many thanks to Simon McVittie for collecting this report
> forwarded 1051454 https://code.videolan.org/rist/librist/-/issues/169
Bug #1051454 [src:librist] librist: FTBFS on 32-bit architectures: "Simple 
profile unicast packet loss" test segfaults
Set Bug forwarded-to-address to 
'https://code.videolan.org/rist/librist/-/issues/169'.
> thanks
Stopping processing here.

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

Bug#1025576: marked as done (libgsecuredelete: recommends transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 10:19:23 +
with message-id 
and subject line Bug#1025576: fixed in libgsecuredelete 0.3-3.1
has caused the Debian Bug report #1025576,
regarding libgsecuredelete: recommends transitional policykit-1 package
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.)


-- 
1025576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgsecuredelete
Version: 0.3-3
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1

This package has a Recommends on the transitional package policykit-1,
which has been separated into polkitd, pkexec and (deprecated)
polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: libgsecuredelete
Source-Version: 0.3-3.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libgsecuredelete 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 Sep 2023 23:37:52 +
Source: libgsecuredelete
Architecture: source
Version: 0.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Bastian Germann 
Closes: 1025576
Changes:
 libgsecuredelete (0.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Recommend pkexec instead of policykit-1 (Closes: #1025576)
Checksums-Sha1:
 4aa242be3673024ddc0272eccb8352b3eafe345d 2279 libgsecuredelete_0.3-3.1.dsc
 c7ccfd35a521f45b7b4d9c1d5e245afcf621814f 8592 
libgsecuredelete_0.3-3.1.debian.tar.xz
 103f8579283ed4c9d15e6766cdd55bc7c475f1ec 6478 
libgsecuredelete_0.3-3.1_source.buildinfo
Checksums-Sha256:
 5d92a028ffe5da5ea9cb38223887ab407efafc891ac91e7cc1ab069d88a2c7d4 2279 
libgsecuredelete_0.3-3.1.dsc
 a9ece9146bf010c0e0b29094a37ddd229dea9770dc9800f6a7a8adb5ab0e3e64 8592 
libgsecuredelete_0.3-3.1.debian.tar.xz
 e9ab8e2b813b3ffd807c5dbf6f4df3462be1f789a7ccea13de593a0e5bed1606 6478 
libgsecuredelete_0.3-3.1_source.buildinfo
Files:
 d2a586adc589620031b9438f0e915a8e 2279 gnome optional 
libgsecuredelete_0.3-3.1.dsc
 20006e8c29a7a16861beee085a0cd8ac 8592 gnome optional 
libgsecuredelete_0.3-3.1.debian.tar.xz
 5339dfe701f83dc4a48d119930d39721 6478 gnome optional 
libgsecuredelete_0.3-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmT68OUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDDPDACVfHm19RbkNyw2Y0qV5z1DQh5G4NnJ/C5r
safnEHcd5NkTksHfbT2crcm1wlrsXyhNT8hkFB+eIGICV/eX9VNnTslx2yZfSaQm
FmSIf7qTb99BB2GA8/skGG3DKFAltq4U/aoLhcZWtrin5llLiHkthHBylnmYb4vo
K+0p2iqB5aeH9dT8wIChcVwdM07ICl/2Ky4SVbx+T9wWjPULhHrz+HIQZHFxFtwi
5DPKdTV6aOM7c9FW9akzdQA45qbFreXx0edV/DH+Kangj3Bt46oj3X0F9/vjnjuq
KtjAI6edZuAVqln1OkAOYKyuoRSYnz/5YX+0h8KhBc/L69KXtUVahvqsTfhSz4+Z
o+ook1qGMknbzXe6Sqz5VjhoxB00KzWVSTDOMwZ6bp+GeppFnUjy1289QR0f3IOZ
l0ygGRxvBOdekjdRoqW04iboYB6e/FLbce5h/ANeyNMovMnXN1Jx0A1jrZldF10d
KncRqB2c8lYwTdJYQKTgI7Wjjv8v09A=
=sobH
-END PGP SIGNATURE End Message ---

Bug#1025576: libgsecuredelete: recommends transitional policykit-1 package

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru libgsecuredelete-0.3/debian/changelog 
libgsecuredelete-0.3/debian/changelog
--- libgsecuredelete-0.3/debian/changelog   2021-01-12 15:17:08.0 
+0100
+++ libgsecuredelete-0.3/debian/changelog   2023-09-08 01:37:52.0 
+0200
@@ -1,3 +1,10 @@
+libgsecuredelete (0.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Recommend pkexec instead of policykit-1 (Closes: #1025576)
+
+ -- Bastian Germann   Thu, 07 Sep 2023 23:37:52 +
+
 libgsecuredelete (0.3-3) unstable; urgency=medium
 
   * Patch gsecuredelete/Makefile.am to generate a proper valac call - Thanks
diff -Nru libgsecuredelete-0.3/debian/control 
libgsecuredelete-0.3/debian/control
--- libgsecuredelete-0.3/debian/control 2021-01-12 13:27:25.0 +0100
+++ libgsecuredelete-0.3/debian/control 2023-09-08 01:37:29.0 +0200
@@ -20,7 +20,7 @@
  ${shlibs:Depends},
  libglib2.0-0,
  secure-delete
-Recommends: policykit-1
+Recommends: pkexec
 Description: wrapper library for the secure-delete tools
  GSecureDelete is a GObject wrapper library for the secure-delete tools
  (srm, sfill, sswap and smem), aiming to ease use of these tool from programs

Bug#1042199: marked as done (python-colour: FTBFS: ImportError: cannot import name '_get_unpatched' from 'setuptools.dist' (/usr/lib/python3/dist-packages/setuptools/dist.py))

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2023 10:04:47 +
with message-id 
and subject line Bug#1042199: fixed in python-colour 0.1.5-4
has caused the Debian Bug report #1042199,
regarding python-colour: FTBFS: ImportError: cannot import name 
'_get_unpatched' from 'setuptools.dist' 
(/usr/lib/python3/dist-packages/setuptools/dist.py)
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.)


-- 
1042199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-colour
Version: 0.1.5-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'requires-dist' will not be supported in 
> future
> versions. Please use the underscore name 'requires_dist' instead.
> 
> By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> By 2023-Oct-30, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> Traceback (most recent call last):
>   File "/<>/setup.py", line 61, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 147, in setup
> _setup_distribution = dist = klass(attrs)
>  
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 486, in 
> __init__
> _Distribution.__init__(
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 283, in __init__
> self.finalize_options()
>   File 

Bug#1051454: librist: FTBFS on 32-bit architectures: "Simple profile unicast packet loss" test segfaults

[Simon McVittie]

Source: librist
Version: 0.2.8+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

The new version of librist in unstable is failing its build-time tests on
all 32-bit architectures (armel, armhf, i386 and several ports
architectures):

> Summary of Failures:
> 
> 3/21 libRIST:simple+unicast / Simple profile unicast packet loss 10%  
>  FAIL 
> 0.05s   killed by signal 11 SIGSEGV
> 4/21 libRIST:simple+unicast / Simple profile unicast packet loss 25%  
>  FAIL 
> 0.03s   killed by signal 11 SIGSEGV

It's likely to be easy to reproduce this on an amd64 machine by building
the i386 package (debuild -ai386), either cross-compiling or in an
i386 chroot, container or VM. This is a regression since 0.2.7+dfsg-1,
so I would suggest starting by reviewing the differences between those
versions.

This could be related to one of these compiler warnings, which indicate
assumptions in the source code that are not true on ILP32 architectures:

> ../tools/srp_shared.c: In function ‘user_verifier_lookup’:
> ../tools/srp_shared.c:176:43: warning: left shift count >= width of type 
> [-Wshift-count-overflow]
>   176 | *generation = (buf.st_mtim.tv_sec << 32) | 
> buf.st_mtim.tv_nsec;
>   |   ^~

> ../tools/ristreceiver.c: In function ‘cb_stats’:
> ../tools/ristreceiver.c:446:86: warning: cast from pointer to integer of 
> different size [-Wpointer-to-int-cast]
>   446 | rist_prometheus_parse_stats(prom_stats_ctx, 
> stats_container, (uint64_t)arg);
>   |   
>^

> ../tools/ristsender.c: In function ‘setup_rist_peer’:
> ../tools/ristsender.c:447:74: warning: cast to pointer from integer of 
> different size [-Wint-to-pointer-cast]
>   447 | if (rist_stats_callback_set(ctx, setup->statsinterval, 
> cb_stats, (void*)w->id) == -1) {
>   |   
>^

Or it could be something more subtle that gcc is unable to diagnose, like
type-size assumptions in a varargs function.

(It also failed to build on arm64, but that seems to be unrelated:
a different test failed there with an assertion failure, that test has
failed similarly in the past, and it doesn't fit the pattern of 64-bit
architectures succeeding but 32-bit failing. That's out of scope for this
particular bug report.)

librist4:i386 is pulled in by this dependency chain for users of Wine:

wine32 -> libwine -R-> gstreamer1.0-libav -> libavformat60 -> librist4

(where -R-> indicates a Recommends)

so having both amd64 and i386 versions installed is going to be a relatively
normal thing to do. Please could you take a look?

Thanks,
smcv

Processed: severity of 1051368 is normal

[Debian Bug Tracking System]

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

> severity 1051368 normal
Bug #1051368 [python3-selenium] python3-selenium: Selenium Python still can't 
find chromedriver
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: notfound 1030328 in 0.4.0-16

[Debian Bug Tracking System]

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

> notfound 1030328 0.4.0-16
Bug #1030328 {Done: Bastian Germann } [src:quelcom] quelcom: 
FTBFS with TeXInfo 7.0.x
No longer marked as found in versions quelcom/0.4.0-16.
> thanks
Stopping processing here.

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

Bug#1051096: marked as done (nfoview: recommends a non-existent package)

[Debian Bug Tracking System]

Your message dated Fri, 8 Sep 2023 09:16:33 +0200
with message-id <20230908091633.3bca9...@debian.org>
and subject line Re: Bug#1051096: nfoview: recommends a non-existent package
has caused the Debian Bug report #1051096,
regarding nfoview: recommends a non-existent package
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.)


-- 
1051096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfoview
Version: 1.29-2
Severity: serious
X-Debbugs-Cc: paula@cs.email

Dear Maintainer,

nfoview currently Recommends the package fonts-cascadia-code which is
not packaged in stable version of debian. This is a policy violation.

Please fix thank you.

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

Kernel: Linux 6.1.0-11-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfoview depends on:
ii  gir1.2-gtk-3.0  3.24.37-2
ii  python3 3.11.2-1+b1
ii  python3-gi  3.42.2-3+b1

Versions of packages nfoview recommends:
pn  fonts-cascadia-code  

nfoview suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: severity -1 normal


On Sat, 02 Sep 2023 16:44:57 +
paula@cs.email wrote:

> nfoview currently Recommends the package fonts-cascadia-code which
> is not packaged in stable version of debian.

Thanks for reporting!

Note that package fonts-cascadia-code does exist in the archive [1]
and is in main, but happens to have been removed from testing because
of a bug [2] and thus isn't available in stable/bookworm.

That should not prevent anyone from installing or using nfoview
though, given that the dependency is merely recommended. Updating the
package in bookworm to remove fonts-cascadia-code would therefore not
make any real life difference: users would end up with nfoview
installed and working and fonts-cascadia-code not installed, same as
today.

In unstable meanwhile, there's nothing to fix (as fonts-cascadia-code
is present) other than the font package itself. Work for that appears
to be ongoing in the Fonts Team, see [3][4].


[1] https://tracker.debian.org/pkg/fonts-cascadia-code
[2] https://bugs.debian.org/997317
[3] https://salsa.debian.org/fonts-team/fonts-cascadia-code
[4] https://bugs.debian.org/1013213


pgpvpBczBXR1P.pgp
Description: OpenPGP digital signature
--- End Message ---

Bug#1051368: python3-selenium: Selenium Python still can't find chromedriver

[Carsten Schoenert]

Control: tags -1 severity normal

Hello Jonathan,

Am Wed, Sep 06, 2023 at 04:37:28PM -0400 schrieb Jonathan Kamens:
 
> Opening a new ticket since bug 1050378 is resolved and I don't know
> how to reopen a resolved ticket (nor do I know if it is even possible
> for me to reopen a resolved ticket).

https://www.debian.org/Bugs/server-control#reopen

if you use 'bts' this would become the following CLI command:

$ bts 1050378 reopen

If you prefer to use a MTA ensure to include the following line at the
very beginning of the body.

reopen 1050378

> python3-selenium 4.12.0+dfsg-1 still doesn't work.
> 
> I get this when I try to create a selenium.webdriver.Chrome object:
> 
> selenium.common.exceptions.NoSuchDriverException: Message: Unable to obtain 
> driver for chrome using Selenium Manager.; For documentation on this error, 
> please visit: 
> https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location
> 
> The ChangeLog for this release claims:
> 
>   * [5b22b76] d/README.Debian: Add section about the Selenium Manager
>   * [25b0d5f] d/NEWS moved to d/python-selenium.NEWS
> (Closes: #1050378)
> 
> But neither of those files exists in the python3-selenium package. Was
> there an intention to add them to the package that wasn't followed
> through on?

This is indeed a issue, both file should be within the package
python3-selenium but are not in 4.12.0-1. This slipped somehow through.
The file are moved now into the correct binary package.

> Incidentally, I took a look at README.Debian in the source package and
> there are some issues with the text that may be worth fixing as well.
> In particular:
> 
> >While writing it's not packaged for Debian. In order to make python3-selenium
> 
> I suggest changing "While writing" (which is not really an idiom that
> is used in English) to "At this time".
> 
> >usable with this new circumstance you will need to adjust your source in a
> >way to choose the used driver directly and skip the calling of the manager
> >code in Selenium. Please have a look at the following example how to archive
> 
> I think you mean to say "achieve" here rather than "archive".

Correct, I'm not a native english speaking person and all spelling and
grammar tools do not not detect all common mistakes, I fixed the
relevant parts which will get included in a next upload.

> In any case I do not believe that documenting this deficiency in
> README.Debian, even if/when it is included in the package, is a
> sufficient fix for the issue. The issue IMO should remain unresolved
> until Selenium Manager is properly packaged for Debian.

And then? Who will package the required package? I'm not tend to do
this. And adding at minimum two lines of additional code to your
project/code/application that is intended to be running on a Debian
system isn't a big thing to me.

If you rely on Selenium Manager you should fill a RFP issue I suggest.

If you think the problem (and also the possible solutions) aren't well
enough explained and to less documentation is provided how to work
around the new requirement for Selenium Manager is now needed as a
middle layer we are happy to get suggestions and text snippets how this
can be improved.

To find out how to set the driver interface manually instead by the
Selenium Manager took me about 30min
on searching with my preferred search engine. I'm sure others will be
able to find quite the same in a similar time.

So no, I don't think your report is of severity grave nor is
python3-selenium within Debian not working currently.

Regards
Carsten