date:20230128

Processed: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-28 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #1029593 {Done: Étienne Mollier } [src:nibabel] 
nibabel: (armel autopkgtest) needs update for NumPy 1.24
'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 nibabel/5.0.0-1.

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

Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-28 Thread Graham Inggs

Control: reopen -1

autopkgtests of nibabel/5.0.0-1 still fail in the same way on armel.

https://ci.debian.net/packages/n/nibabel/testing/armel/

Bug#1028994: [Pkg-mailman-hackers] Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11

2023-01-28 Thread Petter Reinholdtsen



[Sebastiaan Couwenberg]
> How is that going?
> 
> mailman3 is the last major blocker for testing migration of
> python3-defaults.

No idea what is going on, but thought it best to mention that mailman3
has been removed from testing because of this issue.
-- 
Happy hacking
Petter Reinholdtsen

Bug#978228: marked as done (vagrant-librarian-puppet: FTBFS: ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 14:27:29 +0900
with message-id 
and subject line Re: vagrant-librarian-puppet: FTBFS: ruby-faraday : Breaks: 
ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed
has caused the Debian Bug report #978228,
regarding vagrant-librarian-puppet: FTBFS: ruby-faraday : Breaks: 
ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed
to be marked as done.

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

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


-- 
978228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vagrant-librarian-puppet
Version: 0.9.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), gem2deb, librarian-puppet (>= 
> 2.2.1), puppet (>= 4.3.2), vagrant (>= 2.2.3), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), gem2deb, librarian-puppet 
> (>= 2.2.1), puppet (>= 4.3.2), vagrant (>= 2.2.3), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [407 B]
> Get:5 copy:/<>/apt_archive ./ Packages [494 B]
> Fetched 1858 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/vagrant-librarian-puppet_0.9.2-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
vagrant-librarian-puppet 0.9.2-2 can build successfully now
with ruby-faraday 1.1.0-7 and ruby-puppet-forge 3.0.0-1.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature
--- End Message ---

Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.

2023-01-28 Thread Peter Michael Green


Package: pushpin
Version: 1.36.0-1
Severity: serious

The new version of pushpin added a dependency on jsonwebtoken,
unfortunately jsonwebtoken depends in ring, which is only available
on x86* and arm*. There is work upstream to make ring more
portable but it seems unlikely to feature in a stable release before
the bookworm freeze.

Not sure what can be done about this, I tried reverting the
upstream commit in question using a Debian patch, but it did not
seem to revert cleanly.

Bug#1027305: marked as done (python3-pyglossary: crashes with ModuleNotFoundError)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 03:50:51 +
with message-id 
and subject line Bug#1027305: fixed in pyglossary 4.5.0-1
has caused the Debian Bug report #1027305,
regarding python3-pyglossary: crashes with ModuleNotFoundError
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.)


-- 
1027305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyglossary
Version: 3.2.1-1.1
Severity: grave
Justification: renders package unusable

Hi,

pyglossary is crashing with a simple invocation:

$ pyglossary

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/pyglossary/plugins/babylon_bgl/bgl_reader.py", 
line 30, in 
GzipFile = __import__(
ModuleNotFoundError: No module named 'pyglossary.plugin_lib.py310'
If things didn't work well with BGL files, install Python 3.5 to 3.7 and try 
again
Traceback (most recent call last):
  File "/usr/share/pyglossary/pyglossary.pyw", line 215, in 
log.setVerbosity(args.verbosity)
AttributeError: 'RootLogger' object has no attribute 'setVerbosity'

- exit 1

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

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

Versions of packages python3-pyglossary depends on:
ii  python3  3.10.6-3+b1

Versions of packages python3-pyglossary recommends:
ii  gir1.2-gtk-3.03.24.35-3
ii  python3-gi3.42.2-3
ii  python3-gi-cairo  3.42.2-3
ii  python3-html5lib  1.1-3
ii  python3-icu   2.10.2-1+b2
ii  python3-jinja23.0.3-2
ii  python3-lxml  4.9.1-1+b2
ii  python3-lzo   1.14-1+b2

python3-pyglossary suggests no packages.

Regards,
--
Raul Benencia
--- End Message ---
--- Begin Message ---
Source: pyglossary
Source-Version: 4.5.0-1
Done: Emfox Zhou 

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

Debian distribution maintenance software
pp.
Emfox Zhou  (supplier of updated pyglossary package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 29 Jan 2023 09:03:30 +0800
Source: pyglossary
Architecture: source
Version: 4.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Emfox Zhou 
Changed-By: Emfox Zhou 
Closes: 1027305
Changes:
 pyglossary (4.5.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Working on newer python3 (Closes: #1027305).
   * Bump policy and compat version.
Checksums-Sha1:
 499542f6e69ff6085a20fc24b80107dd1aaace12 1810 pyglossary_4.5.0-1.dsc
 01fc74dfc4a206c115f249e4a3c6f2a3951650fa 402743 pyglossary_4.5.0.orig.tar.gz
 d8dca4a5504f173fdc1390e5705eac0e1adab836 4304 pyglossary_4.5.0-1.debian.tar.xz
 b8ba0c9185f3b7cbcda67b7e41642e58f4eb574f 6602 
pyglossary_4.5.0-1_source.buildinfo
Checksums-Sha256:
 512c94200d14c3a19eaacafa0ef0268e48002da4594ed07f71b0ef9fbcec28a7 1810 
pyglossary_4.5.0-1.dsc
 cc8eeaf9fd7e0b913b82a70f6e1a855a6d1f06f85f0873422318fdbee27d9e39 402743 
pyglossary_4.5.0.orig.tar.gz
 c9c2521465c90a20a0a6c9946f367ac2dcf9193db47cb743f7cd2497311e5817 4304 
pyglossary_4.5.0-1.debian.tar.xz
 5d47456f79bdc91f654cee5c54d8e991aebd6e3428aae4dd2b972da3dae72bd1 6602 
pyglossary_4.5.0-1_source.buildinfo
Files:
 56bd2cd3dfcd428fb84298959aae9bee 1810 python optional pyglossary_4.5.0-1.dsc
 d58447e7113ac3586ac9c53181bcebda 402743 python optional 
pyglossary_4.5.0.orig.tar.gz
 83b4509dcc9cd61f951d3d8bc394608c 4304 python optional 
pyglossary_4.5.0-1.debian.tar.xz
 95f01c931bd7fb95680cf323016c3ec7 6602 python optional 
pyglossary_4.5.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEGSauJtItZVqOiaNpgImbv9t7vZQFAmPV57MRHGVtZm94QGRl
Ymlhbi5vcmcACgkQgImbv9t7vZQDIhAAqh8S5c4fISE9dbh7s+uWrE33KU1KzEaO
312TRfWEGGxLmJLjQt4b0gWF11DIxRG6UwQgoBiO6QkNLWLRAEbiU2q6zAeDhznO

Bug#1029906: marked as done (mdevctl: Build depends on cruft package about to be removed: librust-log+serde-dev)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 03:42:44 +
with message-id <86d898f7-ed1e-d032-166c-62c0f30cf...@p10link.net>
and subject line re: mdevctl: Build depends on cruft package about to be 
removed: librust-log+serde-dev
has caused the Debian Bug report #1029906,
regarding mdevctl: Build depends on cruft package about to be removed: 
librust-log+serde-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.)


-- 
1029906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdevctl
Version: 1.2.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

librust-log+serde-dev is NBS cruft that is about to be removed, which
will cause the package to FTBFS.

Scott K
--- End Message ---
--- Begin Message ---

librust-log+serde-dev is NBS cruft that is about to be removed,

It's also a virtual package provided by librust-log-dev

  which
will cause the package to FTBFS.

the cruft physical package has been uninstallable for ages,
the package has been building just fine using the virtual
package.
--- End Message ---

Bug#1027851: pytorch FTBFS with Python 3.11 as default version

2023-01-28 Thread M. Zhou

For reference, a 8 core + 16GB RAM configuration should be able to finish the
pytorch compilation timely. The build takes roughly an hour. My observation
is based on power9 -- on amd64 it should be something similar.


On Sun, 2023-01-29 at 11:09 +0800, Aron Xu wrote:
> On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille  wrote:
> > 
> > Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu:
> > > On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille  wrote:
> > > >   make: *** [debian/rules:83: binary] Terminated
> > > >   ninja: build stopped: interrupted by user.
> > > > 
> > > > could be a sign for this.  Was I to naive to assume Salsa CI could
> > > > manage a pytorch build and should we possibly switch this off again?
> > > > 
> > > 
> > > Not sure but by wild guess it could be caused by running for too long?
> > 
> > I do not think so.  Since I was aware that it will take long I have
> > adjusted the timeout from 1h (default) to 4h.  The log stops a bit after
> > 3h.  To my experience if timeout is the reason the log ends with this
> > information.
> > 
> 
> Then I guess it could be out-of-memory, the build process is hungry
> for RAM and a single cc1plus process can take at least up to 2GB
> memory during my quick observation.
> 
> Regards,
> Aron
>

Processed: Move where the bug was

2023-01-28 Thread Debian Bug Tracking System

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

> reassign 1029911 librust-rustls-dev 0.20.8-1
Bug #1029911 [src:rust-ureq] rust-ureq FTBFS: error: unable to load build 
system class 'cargo': Can't locate String/ShellQuote.pm
Bug reassigned from package 'src:rust-ureq' to 'librust-rustls-dev'.
No longer marked as found in versions rust-ureq/2.6.2-1.
Ignoring request to alter fixed versions of bug #1029911 to the same values 
previously set
Bug #1029911 [librust-rustls-dev] rust-ureq FTBFS: error: unable to load build 
system class 'cargo': Can't locate String/ShellQuote.pm
Marked as found in versions rust-rustls/0.20.8-1.
> affects 1029911 src:rust-ureq
Bug #1029911 [librust-rustls-dev] rust-ureq FTBFS: error: unable to load build 
system class 'cargo': Can't locate String/ShellQuote.pm
Added indication that 1029911 affects src:rust-ureq
> close 1029911 0.20.8-2
Bug #1029911 [librust-rustls-dev] rust-ureq FTBFS: error: unable to load build 
system class 'cargo': Can't locate String/ShellQuote.pm
Marked as fixed in versions rust-rustls/0.20.8-2.
Bug #1029911 [librust-rustls-dev] rust-ureq FTBFS: error: unable to load build 
system class 'cargo': Can't locate String/ShellQuote.pm
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-28 Thread Otto Kekäläinen

Hi!

I managed now to reproduce this. The purge step is not relevant, but
simply the upgrade itself.


In clean Docker container with Debian unstable:

$ apt install -y mariadb-server-10.6
-> install successful

$ apt full-upgrade -y
-> does nothing

$ service mariadb restart
Stopping MariaDB database server: mariadbd.
Starting MariaDB database server: mariadbd.

$ apt install mariadb-server -y
The following packages will be REMOVED:
  mariadb-client-10.6 mariadb-client-core-10.6 mariadb-server-10.6
mariadb-server-core-10.6
The following NEW packages will be installed:
  mariadb-client mariadb-client-core mariadb-server mariadb-server-core pv

$ service mariadb restart
mariadb: unrecognized service

-> upgrade successful, but service stopped working - the service file
has no executable bit anymore.

$ dpkg -l | grep -iE 'maria|mysql|galera'
ii  galera-4  26.4.11-1+b2   amd64
Replication framework for transactional applications
ii  libdbd-mariadb-perl   1.22-1+b1  amd64Perl5
database interface to the MariaDB/MySQL databases
ii  libmariadb3:amd64 1:10.11.1-1amd64MariaDB
database client library
ii  mariadb-client1:10.11.1-1amd64MariaDB
database client binaries
rc  mariadb-client-10.6   1:10.6.11-2amd64MariaDB
database client binaries
ii  mariadb-client-core   1:10.11.1-1amd64MariaDB
database core client binaries
ii  mariadb-common1:10.11.1-1all  MariaDB
common configuration files
ii  mariadb-server1:10.11.1-1amd64MariaDB
database server binaries
rc  mariadb-server-10.6   1:10.6.11-2amd64MariaDB
database server binaries
ii  mariadb-server-core   1:10.11.1-1amd64MariaDB
database core server files
ii  mysql-common  5.8+1.1.0  all  MySQL
database common files, e.g. /etc/mysql/my.cnf

$ find /etc -name '*mariadb*' -type f -ls
-rw-r--r--   1 root root 6387 Jan 15 22:45 /etc/init.d/mariadb
-rw-r--r--   1 root root 1859 Jan 15 22:45 /etc/logrotate.d/mariadb
-rw-r--r--   1 root root 1126 Jan  8 01:45 /etc/mysql/mariadb.cnf
-rw-r--r--   1 root root  730 Jan  3 06:42
/etc/apparmor.d/usr.sbin.mariadbd
-rw-r--r--   1 root root  716 Jan  3 06:42
/etc/logcheck/ignore.d.paranoid/mariadb-server-10_6
-rw-r--r--   1 root root  716 Jan 15 22:45
/etc/logcheck/ignore.d.paranoid/mariadb-server
-rw-r--r--   1 root root 2153 Jan  3 06:42
/etc/logcheck/ignore.d.server/mariadb-server-10_6
-rw-r--r--   1 root root 2153 Jan 15 22:45
/etc/logcheck/ignore.d.server/mariadb-server
-rw-r--r--   1 root root 2153 Jan  3 06:42
/etc/logcheck/ignore.d.workstation/mariadb-server-10_6
-rw-r--r--   1 root root 2153 Jan 15 22:45
/etc/logcheck/ignore.d.workstation/mariadb-server

$ apt purge 'mariadb-*-10.6' -y
The following packages will be REMOVED:
  mariadb-client-10.6* mariadb-server-10.6*

$ find /etc -name '*mariadb*' -type f -ls
-rw-r--r--   1 root root 6387 Jan 15 22:45 /etc/init.d/mariadb
-rw-r--r--   1 root root 1859 Jan 15 22:45 /etc/logrotate.d/mariadb
-rw-r--r--   1 root root 1126 Jan  8 01:45 /etc/mysql/mariadb.cnf
-rw-r--r--   1 root root  730 Jan  3 06:42
/etc/apparmor.d/usr.sbin.mariadbd
-rw-r--r--   1 root root  716 Jan 15 22:45
/etc/logcheck/ignore.d.paranoid/mariadb-server
-rw-r--r--   1 root root 2153 Jan 15 22:45
/etc/logcheck/ignore.d.server/mariadb-server
-rw-r--r--   1 root root 2153 Jan 15 22:45
/etc/logcheck/ignore.d.workstation/mariadb-server

-> purge works as expected

Bug#1027851: pytorch FTBFS with Python 3.11 as default version

2023-01-28 Thread Aron Xu

On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille  wrote:
>
> Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu:
> > On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille  wrote:
> > >   make: *** [debian/rules:83: binary] Terminated
> > >   ninja: build stopped: interrupted by user.
> > >
> > > could be a sign for this.  Was I to naive to assume Salsa CI could
> > > manage a pytorch build and should we possibly switch this off again?
> > >
> >
> > Not sure but by wild guess it could be caused by running for too long?
>
> I do not think so.  Since I was aware that it will take long I have
> adjusted the timeout from 1h (default) to 4h.  The log stops a bit after
> 3h.  To my experience if timeout is the reason the log ends with this
> information.
>

Then I guess it could be out-of-memory, the build process is hungry
for RAM and a single cc1plus process can take at least up to 2GB
memory during my quick observation.

Regards,
Aron

Bug#1029929: msmtp-mta fails to purge when adduser is not installed

2023-01-28 Thread Adrian Bunk

Package: msmtp-mta
Version: 1.8.22-1
Severity: serious

https://piuparts.debian.org/sid/fail/msmtp-mta_1.8.22-3.log

...
  Purging configuration files for msmtp-mta (1.8.22-3) ...
  /var/lib/dpkg/info/msmtp-mta.postrm: 8: deluser: not found
  dpkg: error processing package msmtp-mta (--purge):
   installed msmtp-mta package post-removal script subprocess returned error 
exit status 127
  Errors were encountered while processing:
   msmtp-mta



Similar to #1029799, but for the other binary package.

Bug#1019604: marked as done (bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 03:26:12 +0100
with message-id 
and subject line FTBFS was caused by ruby-qdbm not being built with Ruby 3.1
has caused the Debian Bug report #1019604,
regarding bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.

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

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


-- 
1019604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsfilter
Version: 1:1.0.19-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild bsfilter with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 test.rb --verbose
> cd test
> Loaded suite test
> Started
> TestBase64: 
>   test_base64:.: (0.012286)
>   test_delimiter_bug: .: (0.002738)
> TestDBM: 
>   test_default_dbm:   .: (0.008320)
>   test_gdbm:  F
> ===
> Failure: test_gdbm(TestDBM):
>   Warning: ignore this test if GDBM is NOT installed.
>   Exception raised:
>   LoadError()
>   
> :85:in
>  `require'
>   
> :85:in
>  `require'
>   /<>/bsfilter/bsfilter:3108:in `get_options'
>   /<>/bsfilter/bsfilter:3262:in `setup'
>   test.rb:408:in `block in test_gdbm'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/assertions.rb:693:in
>  `block in assert_nothing_raised'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/assertions.rb:1826:in
>  `_wrap_assertion'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/assertions.rb:684:in
>  `assert_nothing_raised'
>   test.rb:407:in `test_gdbm'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testcase.rb:871:in
>  `run_test'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testcase.rb:566:in
>  `block (2 levels) in run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/fixture.rb:276:in 
> `block in create_fixtures_runner'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/fixture.rb:276:in 
> `block in create_fixtures_runner'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/fixture.rb:257:in 
> `run_fixture'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/fixture.rb:292:in 
> `run_setup'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testcase.rb:564:in
>  `block in run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testcase.rb:563:in
>  `catch'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testcase.rb:563:in
>  `run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testsuite.rb:124:in
>  `run_test'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testsuite.rb:53:in
>  `run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testsuite.rb:124:in
>  `run_test'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/testsuite.rb:53:in
>  `run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/ui/testrunnermediator.rb:67:in
>  `run_suite'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/ui/testrunnermediator.rb:45:in
>  `block (2 levels) in run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/ui/testrunnermediator.rb:102:in
>  `with_listener'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/ui/testrunnermediator.rb:41:in
>  `block in run'
>   
> /usr/lib/ruby/gems/3.1.0/gems/test-unit-3.5.3/lib/test/unit/ui/testrunnermediator.rb:39:in
>  `catch'
>   
>

Bug#1029928: dials: autopkgtest failure on arm64/ppc64el

2023-01-28 Thread Adrian Bunk

Source: dials
Version: 3.12.1+dfsg3-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/arm64/d/dials/30737888/log.gz
https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dials/30737889/log.gz

...
== FAILURES ===
___ test_versus_brute_force 

def test_versus_brute_force():
"""Perform a regression test by comparing to indices generated by the 
brute
force method"""

# cubic, 50A cell, 1A radiation, 1 deg osciillation, everything ideal
a = 50.0
ub_beg = matrix.sqr((1.0 / a, 0.0, 0.0, 0.0, 1.0 / a, 0.0, 0.0, 0.0, 
1.0 / a))
axis = matrix.col((0, 1, 0))
r_osc = matrix.sqr(
r3_rotation_axis_and_angle_as_matrix(axis=axis, angle=1.0, deg=True)
)
ub_end = r_osc * ub_beg
uc = unit_cell((a, a, a, 90, 90, 90))
sg = space_group(space_group_symbols("P23").hall())
s0 = matrix.col((0, 0, 1))
wavelength = 1.0
dmin = 1.5

# get the full set of indices
indices = full_sphere_indices(unit_cell=uc, resolution_limit=dmin, 
space_group=sg)

# find the observed indices
ra = rotation_angles(dmin, ub_beg, wavelength, axis)
obs_indices, obs_angles = 
ra.observed_indices_and_angles_from_angle_range(
phi_start_rad=0.0 * math.pi / 180.0,
phi_end_rad=1.0 * math.pi / 180.0,
indices=indices,
)

# r = reeke_model(ub_beg, ub_end, axis, s0, dmin, 1.0)
# reeke_indices = r.generate_indices()

# now try the Reeke method to generate indices
r = ReekeIndexGenerator(ub_beg, ub_end, sg.type(), axis, s0, dmin, 
margin=1)
reeke_indices = r.to_array()

for oi in obs_indices:
>   assert tuple(map(int, oi)) in reeke_indices
E   assert (-30, 0, -10) in 
E+  where (-30, 0, -10) = tuple()
E+where  = map(int, (-30.0, 0.0, 
-10.0))

tests/algorithms/spot_prediction/test_reeke_index_generator.py:134: 
AssertionError
...
=== short test summary info 
FAILED 
tests/algorithms/spot_prediction/test_reeke_index_generator.py::test_versus_brute_force
= 1 failed, 820 passed, 531 skipped, 1 xfailed, 43 warnings in 1466.82s 
(0:24:26) =
autopkgtest [23:44:38]: test command1: ---]
autopkgtest [23:44:38]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1

Bug#1029915: marked as done (mikutter: Depends: ruby-gtk3 (>= 3.4.9) but it is not going to be installed)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 03:32:28 +0100
with message-id <763d54b8be69240e04d817c07df9c81007507c4a.ca...@gmx.net>
and subject line Bug#1029915: fixed in mikutter 5.0.4+dfsg1-2
has caused the Debian Bug report #1029915,
regarding mikutter: Depends: ruby-gtk3 (>= 3.4.9) but it is not going to be 
installed
to be marked as done.

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

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


-- 
1029915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mikutter
Version: 5.0.4+dfsg1-1
Severity: serious

The following packages have unmet dependencies:
 mikutter : Depends: ruby-gtk3 (>= 3.4.9) but it is not going to be installed
--- End Message ---
--- Begin Message ---
Source: mikutter
Source-Version: 5.0.4+dfsg1-2
Done: Daniel Leidert 

Hi,

I had already spotted this issue and uploaded a new version relaxing the
dependencies. Closing this report.

Regards, Daniel--- End Message ---

Bug#1029926: nagios-plugins-contrib: autopkgtest regression

2023-01-28 Thread Adrian Bunk

Source: nagios-plugins-contrib
Version: 38.20230124
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/30770474/log.gz

...
autopkgtest [00:15:02]: test command7: /usr/lib/nagios/plugins/check_ssl_cert 
-H www.debian.org
autopkgtest [00:15:02]: test command7: [---
SSL_CERT UNKNOWN www.debian.org: cannot find program: bc
autopkgtest [00:15:03]: test command7: ---]
autopkgtest [00:15:03]: test command7:  - - - - - - - - - - results - - - - - - 
- - - -
command7 FAIL non-zero exit status 3
...
autopkgtest [00:15:56]:  summary
command1 PASS
command2 PASS
command3 PASS
command4 PASS
command5 PASS
command6 PASS
command7 FAIL non-zero exit status 3
command8 PASS
command9 PASS

Processed: closing 1029328

2023-01-28 Thread Debian Bug Tracking System

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

> close 1029328 0.11.0-1
Bug #1029328 [src:rust-imagesize] rust-imagesize: autopkgtest failure
Marked as fixed in versions rust-imagesize/0.11.0-1.
Bug #1029328 [src:rust-imagesize] rust-imagesize: autopkgtest failure
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#995359: marked as done (ruby-gitlab-labkit: autopkgtest needs update for new version of ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10))

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 04:18:28 +0200
with message-id 
and subject line Fixed since 0.25.0-1
has caused the Debian Bug report #995359,
regarding ruby-gitlab-labkit: autopkgtest needs update for new version of 
ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10)
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.)


-- 
995359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gitlab-labkit
Version: 0.12.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, ruby-jaeger-cli...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-jaeger-client

Dear maintainer(s),

With a recent upload of ruby-jaeger-client the autopkgtest of
ruby-gitlab-labkit fails in testing when that autopkgtest is run with
the binary packages of ruby-jaeger-client from unstable. It passes when
run with only packages from testing. In tabular form:

   passfail
ruby-jaeger-client from testing1.1.0-2
ruby-gitlab-labkit from testing0.12.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It looks to me
that you have to make your package compatible with the next version of
ruby-jaeger-client.

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

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-jaeger-client

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-gitlab-labkit/15624242/log.gz


┌──┐
│ Checking Rubygems dependency resolution on ruby2.7
   │
└──┘

GEM_PATH= ruby2.7 -e gem\ \"gitlab-labkit\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in
block in activate_dependencies': Could not find 'jaeger-client' (~>
0.10) among 98 total gem(s) (Gem::MissingSpecError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
at:
/usr/share/rubygems-integration/all/specifications/gitlab-labkit-0.12.2.gemspec,
execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs':
Could not find 'jaeger-client' (~> 0.10) - did find:
[jaeger-client-1.1.0] (Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
, execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block
in activate_dependencies'
from

Processed: Workarounds in affected packages do not fix a bug

2023-01-28 Thread Debian Bug Tracking System

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

> reopen 1016936
Bug #1016936 {Done: David Prévot } [dwz] dwz: Unknown 
debugging section .debug_addr causes some builds to fail
Bug reopened
Ignoring request to alter fixed versions of bug #1016936 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1029917: marked as done (r-cran-pbkrtest: Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be installed)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 01:08:28 +
with message-id 
and subject line Bug#1029917: fixed in r-cran-pbkrtest 0.5.2-2
has caused the Debian Bug report #1029917,
regarding r-cran-pbkrtest: Depends: r-cran-lme4 (>= 1.1.31) but it is not going 
to be installed
to be marked as done.

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

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


-- 
1029917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-pbkrtest
Version: 0.5.2-1
Severity: serious

The following packages have unmet dependencies:
 r-cran-pbkrtest : Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be 
installed


You might want to reconsider

   * debian/patches/series: Disable no longer required lme4 version patch
--- End Message ---
--- Begin Message ---
Source: r-cran-pbkrtest
Source-Version: 0.5.2-2
Done: Dirk Eddelbuettel 

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated r-cran-pbkrtest 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Jan 2023 18:35:04 -0600
Source: r-cran-pbkrtest
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 1029917
Changes:
 r-cran-pbkrtest (0.5.2-2) unstable; urgency=medium
 .
   * debian/patches/series: Reenable lme4 version patch (Closes: #1029917)
   * debian/patches/hyphenated_version: Updated to current version
Checksums-Sha1:
 e7cbacb85c1d48eef941ab8dac4d06f1860c0e86 2021 r-cran-pbkrtest_0.5.2-2.dsc
 017190ca1389bb82cffcd03e1ad7375a27bac0c3 2904 
r-cran-pbkrtest_0.5.2-2.debian.tar.xz
 58074c3cfe34c3dbf9712b8b4c6a9b3524cf 12756 
r-cran-pbkrtest_0.5.2-2_amd64.buildinfo
Checksums-Sha256:
 5cf6da24a60cfc42b8a563028aba97eb296f4b0ee6a5ddb524d6eef28040490f 2021 
r-cran-pbkrtest_0.5.2-2.dsc
 10d278398cd80aca58f31c46140bf08b1319a71aadf0c4d84e6a178cf84af9af 2904 
r-cran-pbkrtest_0.5.2-2.debian.tar.xz
 1bc8977694a00ae688621b304721ae76f811d2d6322e7bec6b200d2b865d3dfd 12756 
r-cran-pbkrtest_0.5.2-2_amd64.buildinfo
Files:
 01d833e7c64d350cd0941a151e4a51d9 2021 gnu-r optional 
r-cran-pbkrtest_0.5.2-2.dsc
 3fb12fd5fc27aefb26dbd5c861ec5811 2904 gnu-r optional 
r-cran-pbkrtest_0.5.2-2.debian.tar.xz
 c9250f5aaf60001a75be87bcb5580e77 12756 gnu-r optional 
r-cran-pbkrtest_0.5.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBY9W/nKFIn+KrmaIaAQhMTw//ZG8a/oMSDXKqlQP3Mu/ec8wQzktxzKEX
s3UAtMC493KqIHuEVypUdTPebeITAP2ER/0Cmi4fBNpLZYJJousuPOltAb+WIbCt
ukt+SIwndG9mCb2WPrK1Sr/IaK2VXLyKKNp/fFM0vu2p7DyNM1qvZNUDi/di49/O
pb4sdJ5bmyCpdEA7g14x9sAdM5oqCkRKGKnEm+2sk5A9crYUCxtNOVezsMW4EMFh
12mlwvQyUmjhQD+ONCGkRRJZzcR9GiWM2/ykJwYmmr7wLv8+/ESn3nKHym3dV54g
lZ3mxUJoMO5aEmLOFYf0KJ92tGWdPgtASeRh9skjULb13p+rGThdA07I5KARSlnv
5JMuBPKNeP83QBAJPcKSX44U9CzXbpz9MVFgg5yq7AlfkV7fqclJU+ipLteKUKIJ
h//O660T7nmg7JMldqPQEDbdUr2ZIM807DexWWTfXMeKZt5+vnTtA4HRLdhfDM5P
cUTCY7yA80vUOBNr6VVklUkuPNpR6Yfp+b0HdEWc/0fV06rhyeNnEKDgZJpc/1P9
CU1gk/KPah1fb1LdqwuUYouvecXQy0DfPtZuXal5zK7Qg/vf0m50XRUk6gaQq/eO
yrqn+ogHaBGZw8K6SufXsiAxB5QzcLtH/6FgimmNPCB04s/hWMpG9qjhGa9RvDTT
C4I7XZpBCDQ=
=D/Uz
-END PGP SIGNATURE End Message ---

Processed: Re: gopacket: FTBFS with libpcap >= 1.10.2

2023-01-28 Thread Debian Bug Tracking System

Processing control commands:

> retitle -1 gopacket: FTBFS with libpcap >= 1.10.2
Bug #1028841 [src:gopacket] gopacket: FTBFS: pcap_test.go:26: Error 
returned for nonexistent file: /path/to/nonexistent/file: No such file or 
directory
Changed Bug title to 'gopacket: FTBFS with libpcap >= 1.10.2' from 'gopacket: 
FTBFS: pcap_test.go:26: Error returned for nonexistent file: 
/path/to/nonexistent/file: No such file or directory'.
> tags -1 + confirmed
Bug #1028841 [src:gopacket] gopacket: FTBFS with libpcap >= 1.10.2
Added tag(s) confirmed.
> forwarded -1 https://github.com/google/gopacket/issues/1088
Bug #1028841 [src:gopacket] gopacket: FTBFS with libpcap >= 1.10.2
Set Bug forwarded-to-address to 
'https://github.com/google/gopacket/issues/1088'.

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

Bug#1028841: gopacket: FTBFS with libpcap >= 1.10.2

2023-01-28 Thread Mathias Gibbens

Control: retitle -1 gopacket: FTBFS with libpcap >= 1.10.2
Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/google/gopacket/issues/1088

  It appears that libpcap 1.10.2 introduced some change that is causing
the test failure. Manually downgrading to libpcap 1.10.1-4 from
snapshot.d.o allows the build to succeed. I've opened an issue with the
upstream project, as I don't possess the knowledge to properly fix
this.

Mathias


signature.asc
Description: This is a digitally signed message part

Processed: reopening 1029919, forcibly merging 1004356 1029919

2023-01-28 Thread Debian Bug Tracking System

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

> reopen 1029919
Bug #1029919 {Done: Daniel Leidert } 
[ruby-gitlab-license-finder] ruby-gitlab-license-finder,ruby-license-finder: 
error when trying to install together
Bug reopened
Ignoring request to alter fixed versions of bug #1029919 to the same values 
previously set
> forcemerge 1004356 1029919
Bug #1004356 [ruby-gitlab-license-finder] ruby-gitlab-license-finder: missing 
Breaks+Replaces: ruby-license-finder (<< 6)
Bug #1029919 [ruby-gitlab-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Marked as found in versions ruby-gitlab-license-finder/6.14.2.1-1.
Bug #1004356 [ruby-gitlab-license-finder] ruby-gitlab-license-finder: missing 
Breaks+Replaces: ruby-license-finder (<< 6)
Marked as found in versions ruby-gitlab-license-finder/6.14.2.1-2.
Merged 1004356 1029919
> thanks
Stopping processing here.

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

Bug#1029923: gstreamer1.0-plugins-good: trying to overwrite libgstxingmux.so, which is also in package gstreamer1.0-plugins-ugly

2023-01-28 Thread Simon McVittie

Package: gstreamer1.0-plugins-good
Version: 1.22.0-3
Severity: serious
Justification: Policy 7.6.1

> Unpacking gstreamer1.0-plugins-good:amd64 (1.22.0-3) over (1.20.5-2) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-qofiMB/43-gstreamer1.0-plugins-good_1.22.0-3_amd64.deb 
> (--unpack):
>  trying to overwrite 
> '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstxingmux.so', which is also in 
> package gstreamer1.0-plugins-ugly:amd64 1.20.5-1

Presumably gstreamer1.0-plugins-good needs a versioned Breaks/Replaces
on gstreamer1.0-plugins-ugly (<< 1.22~) or similar?

smcv

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gstreamer1.0-plugins-good depends on:
ii  gstreamer1.0-plugins-base 1.22.0-2
ii  libaa11.4p5-50
ii  libavc1394-0  0.5.4-5
ii  libbz2-1.01.0.8-5+b1
ii  libc6 2.36-8
ii  libcaca0  0.99.beta20-3
ii  libcairo-gobject2 1.16.0-7
ii  libcairo2 1.16.0-7
ii  libdv41.0.0-15
ii  libflac12 1.4.2+ds-2
ii  libgcc-s1 12.2.0-14
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.74.5-1
ii  libgstreamer-plugins-base1.0-01.22.0-2
ii  libgstreamer1.0-0 1.22.0-2
ii  libgudev-1.0-0237-2
ii  libiec61883-0 1.2.0-6
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-2
ii  libjpeg62-turbo   1:2.1.2-1+b1
ii  libmp3lame0   3.100-6
ii  libmpg123-0   1.31.2-1
ii  liborc-0.4-0  1:0.4.33-2
ii  libpng16-16   1.6.39-2
ii  libpulse0 16.1+dfsg1-2+b1
ii  libraw1394-11 2.1.2-2
ii  libshout3 2.4.6-1+b1
ii  libsoup-3.0-0 3.2.2-1
ii  libsoup2.4-1  2.74.3-1
ii  libspeex1 1.2.1-1
ii  libstdc++612.2.0-14
ii  libtag1v5 1.13-1
ii  libtwolame0   0.4.0-2
ii  libv4l-0  1.22.1-5+b1
ii  libvpx7   1.12.0-1
ii  libwavpack1   5.6.0-1
ii  libx11-6  2:1.8.3-3
ii  libxdamage1   1:1.1.6-1
ii  libxext6  2:1.3.4-1+b1
ii  libxfixes31:6.0.0-2
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages gstreamer1.0-plugins-good recommends:
ii  gstreamer1.0-x  1.22.0-2

gstreamer1.0-plugins-good suggests no packages.

-- no debconf information

Bug#1029908: marked as done (libjna-java: JNA HelloWorld fails on armhf)

2023-01-28 Thread Debian Bug Tracking System

Your message dated Sun, 29 Jan 2023 00:34:59 +
with message-id 
and subject line Bug#1029908: fixed in libjna-java 5.13.0-2
has caused the Debian Bug report #1029908,
regarding libjna-java: JNA HelloWorld fails on armhf
to be marked as done.

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

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


-- 
1029908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjna-java
Version: 5.13.0-1
Severity: normal
Tags: patch

Dear Maintainer,

When trying the JNA tutorial Helloworld on aarch64, it fails with the following
error message:

autopkgtest [12:34:07]: test helloworld: [---
Jan 28, 2023 12:34:09 PM com.sun.jna.Native loadNativeDispatchLibrary
INFO: Looking in /usr/lib/jni/libjnidispatch.system.so
Jan 28, 2023 12:34:09 PM com.sun.jna.Native loadNativeDispatchLibrary
INFO: Looking in /usr/lib/arm-linux-gnueabi/jni/libjnidispatch.system.so
Jan 28, 2023 12:34:09 PM com.sun.jna.Native extractFromResourcePath
INFO: Looking in classpath from 
jdk.internal.loader.ClassLoaders$AppClassLoader@19e0bfd for 
/com/sun/jna/linux-arm/libjnidispatch.so
Exception in thread "main" java.lang.UnsatisfiedLinkError: Native library 
(com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path 
(debian/tests:/usr/share/java/jna.jar)
at 
com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1062)
at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:1018)
at com.sun.jna.Native.(Native.java:221)
at HelloWorld$CLibrary.(HelloWorld.java:8)
at HelloWorld.main(HelloWorld.java:14)
autopkgtest [12:34:09]: test helloworld: ---]

I succesfully tested a fix.

https://salsa.debian.org/niol/libjna-java/-/commit/c69675faa352652e95439f528d6a3e1fda0d90ed

Feel free to come back to me for a ready to upload package.

Cheers,

Alex

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

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

Versions of packages libjna-java depends on:
ii  libjna-jni  5.13.0-1

libjna-java recommends no packages.

libjna-java suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libjna-java
Source-Version: 5.13.0-2
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libjna-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Jan 2023 15:25:15 -0800
Source: libjna-java
Architecture: source
Version: 5.13.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java maintainers 

Changed-By: tony mancill 
Closes: 1029908
Changes:
 libjna-java (5.13.0-2) unstable; urgency=medium
 .
   [ tony mancill ]
   * Team upload.
 .
   [ Alexandre Rossi ]
   * Fix JNA Hello World on armhf (Closes: #1029908)
Checksums-Sha1:
 b685cdfbeda0c73ac279b1ec49cf4c042aff30d4 2388 libjna-java_5.13.0-2.dsc
 ea8b63c562d707f79274fc0509a4f39af2761670 11216 
libjna-java_5.13.0-2.debian.tar.xz
 38e48ff7c461ede487aee8aaa4e2244dac7d19ac 13424 
libjna-java_5.13.0-2_amd64.buildinfo
Checksums-Sha256:
 8514e8399afbe34f0027ad9788e4fe699cac1f891cbc9f86e886e14d03ad8005 2388 
libjna-java_5.13.0-2.dsc
 4b33c018a49d2c7aed6238d2c80f8e66104b9307579880faeea84471ff55a12f 11216 
libjna-java_5.13.0-2.debian.tar.xz
 1965925604f2e02de83979933119ebe6cf449858c32a48adfe09a20b04ba15b3 13424 
libjna-java_5.13.0-2_amd64.buildinfo
Files:
 2f851ab5ca72f85debc729e17f4cd35a 2388 java optional libjna-java_5.13.0-2.dsc
 3e94df251ced04c7fae4f1aa84c341a9 11216 java optional 
libjna-java_5.13.0-2.debian.tar.xz
 b8cf6b4eb2ce9aa6ddca8c702a8b2f5b 13424 java optional 
libjna-java_5.13.0-2_amd64.buildinfo

-BEGIN PGP

Processed: cloning 1011445, reassign 1011445 to ruby-license-finder, reassign -1 to ruby-gitlab-license-finder

2023-01-28 Thread Debian Bug Tracking System

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

> clone 1011445 -1
Bug #1011445 {Done: Daniel Leidert } 
[ruby-gitlab-license-finder,ruby-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Bug 1011445 cloned as bug 1029919
> reassign 1011445 ruby-license-finder 7.0.1-1
Bug #1011445 {Done: Daniel Leidert } 
[ruby-gitlab-license-finder,ruby-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Bug reassigned from package 'ruby-gitlab-license-finder,ruby-license-finder' to 
'ruby-license-finder'.
No longer marked as found in versions ruby-license-finder/7.0.1-1 and 
ruby-gitlab-license-finder/6.14.2.1-2.
No longer marked as fixed in versions ruby-license-finder/7.0.1-2.
Bug #1011445 {Done: Daniel Leidert } [ruby-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Marked as found in versions ruby-license-finder/7.0.1-1.
> reassign -1 ruby-gitlab-license-finder 6.14.2.1-2
Bug #1029919 {Done: Daniel Leidert } 
[ruby-gitlab-license-finder,ruby-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Bug reassigned from package 'ruby-gitlab-license-finder,ruby-license-finder' to 
'ruby-gitlab-license-finder'.
No longer marked as found in versions ruby-license-finder/7.0.1-1 and 
ruby-gitlab-license-finder/6.14.2.1-2.
No longer marked as fixed in versions ruby-license-finder/7.0.1-2.
Bug #1029919 {Done: Daniel Leidert } 
[ruby-gitlab-license-finder] ruby-gitlab-license-finder,ruby-license-finder: 
error when trying to install together
Marked as found in versions ruby-gitlab-license-finder/6.14.2.1-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1028081: argus-server: Produces corrupted argus.out file

2023-01-28 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 grave
Bug #1028081 [argus-server] argus-server: Produces corrupted argus.out file
Severity set to 'grave' from 'important'

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

Bug#1029917: r-cran-pbkrtest: Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be installed

2023-01-28 Thread Dirk Eddelbuettel



On 29 January 2023 at 01:58, Adrian Bunk wrote:
| Package: r-cran-pbkrtest
| Version: 0.5.2-1
| Severity: serious
| 
| The following packages have unmet dependencies:
|  r-cran-pbkrtest : Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be 
installed
|
| You might want to reconsider
| 
|* debian/patches/series: Disable no longer required lme4 version patch

Indeed. I read the upstream DESCRIPTION file the wrong way, the issue is
*still* not fixed upstream.  Sighs.

Will fix. Thanks for the heads up!

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1029917: r-cran-pbkrtest: Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be installed

2023-01-28 Thread Adrian Bunk

Package: r-cran-pbkrtest
Version: 0.5.2-1
Severity: serious

The following packages have unmet dependencies:
 r-cran-pbkrtest : Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be 
installed


You might want to reconsider

   * debian/patches/series: Disable no longer required lme4 version patch

Bug#1029916: q2-phylogeny/i386: Depends: python3-skbio but it is not installable

2023-01-28 Thread Adrian Bunk

Package: q2-phylogeny
Version: 2022.11.1-2
Severity: serious

The following packages have unmet dependencies:
 q2-phylogeny : Depends: python3-skbio but it is not installable


python-skbio does FTBFS on 32bit.

Bug#1021739: nekohtml: CVE-2022-24839

2023-01-28 Thread tony mancill

On Sat, Jan 28, 2023 at 11:35:30PM +0100, David Prévot wrote:
> Hi,
> 
> Le Thu, Oct 13, 2022 at 09:17:02PM +0200, Moritz Mühlenhoff a écrit :
> > Source: nekohtml
> […]
> > The following vulnerability was published for nekohtml.
> > 
> > CVE-2022-24839[0]:
> 
> I prepared an upload (new upstream release) of this package in order to
> fix this RC-bug as part of the BSP currently happening in St-Cergue,
> Switzerland. A merge request has been submitted.
> 
> https://salsa.debian.org/java-team/nekohtml/-/merge_requests/1
> 
> Unless advised otherwise, I intend to upload the updated package
> tomorrow.

Please go ahead with the upload.

Thank you!


signature.asc
Description: PGP signature

Bug#1029915: mikutter: Depends: ruby-gtk3 (>= 3.4.9) but it is not going to be installed

2023-01-28 Thread Adrian Bunk

Package: mikutter
Version: 5.0.4+dfsg1-1
Severity: serious

The following packages have unmet dependencies:
 mikutter : Depends: ruby-gtk3 (>= 3.4.9) but it is not going to be installed

Bug#1029914: libmail-dmarc-perl FTBFS due to missing build (and runtime?) dependencies

2023-01-28 Thread Adrian Bunk

Source: libmail-dmarc-perl
Version: 1.20211209-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libmail-dmarc-perl=all=1.20211209-2=1674928751=0

...
   dh_auto_test -i
/usr/bin/perl Build test --verbose 1
Can't locate Config/Tiny.pm in @INC (you may need to install the Config::Tiny 
module) (@INC contains: lib /tmp/3SPCAxt2ay /<>/blib/lib 
/<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl .) at lib/Mail/DMARC/Base.pm line 
8.
BEGIN failed--compilation aborted at lib/Mail/DMARC/Base.pm line 8.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl-base/parent.pm 
line 16.
BEGIN failed--compilation aborted at lib/Mail/DMARC.pm line 10.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl-base/parent.pm 
line 16.
BEGIN failed--compilation aborted at t/00.Dmarc.t line 343.
t/00.Dmarc.t . 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 

#   Failed test 'use Mail::DMARC::Policy;'
#   at t/01.Policy.t line 10.
# Tried to use 'Mail::DMARC::Policy'.
# Error:  Can't locate URI.pm in @INC (you may need to install the URI 
module) (@INC contains: lib /<>/blib/lib 
/<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl .) at 
lib/Mail/DMARC/Report/URI.pm line 8.
# BEGIN failed--compilation aborted at lib/Mail/DMARC/Report/URI.pm line 8.
# Compilation failed in require at lib/Mail/DMARC/Policy.pm line 9.
# BEGIN failed--compilation aborted at lib/Mail/DMARC/Policy.pm line 9.
# Compilation failed in require at t/01.Policy.t line 10.
# BEGIN failed--compilation aborted at t/01.Policy.t line 10.
Can't locate object method "new" via package "Mail::DMARC::Policy" at 
t/01.Policy.t line 12.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 1.
t/01.Policy.t  
not ok 1 - use Mail::DMARC::Policy;
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/1 subtests
...
Test Summary Report
---
t/00.Dmarc.t   (Wstat: 512 (exited 2) Tests: 0 
Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/01.Policy.t  (Wstat: 512 (exited 2) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/03.Base.t(Wstat: 65280 (exited 255) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/04.PurePerl.t(Wstat: 512 (exited 2) Tests: 0 
Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/06.Result.t  (Wstat: 65280 (exited 255) Tests: 2 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/10.Report.t  (Wstat: 512 (exited 2) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/11.Report.Store.t(Wstat: 512 (exited 2) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/12.Report.Store.SQL.t(Wstat: 512 (exited 2) Tests: 0 
Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/13.Report.Aggregate.t(Wstat: 512 (exited 2) Tests: 0 
Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/14.Report.Aggregate.Metadata.t   (Wstat: 512 (exited 2) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/15.Report.Aggregate.Record.t (Wstat: 65280 (exited 255) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/16.Report.Aggregate.Record.Auth_Results.t (Wstat: 65280 (exited 255) Tests: 3 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/17.Report.Aggregate.Schema.t (Wstat: 512 (exited 2) Tests: 0 
Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/20.Report.URI.t  (Wstat: 65280 (exited 255) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/21.Report.Send.t (Wstat: 65280 (exited 255) Tests: 1 
Failed: 1)
  Failed test:  1
  Non-zero exit status: 255

Bug#1029913: texlive-pictures: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu: /tmp write vulnerability

2023-01-28 Thread Frank Heckenbach

Package: texlive-pictures
Version: 2020.20210202-3
Severity: grave
File: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu

Classic /tmp write vulnerability: function dir_writable writes to
"/tmp/1" (and if this fails, "/tmp/2" etc.) without sufficient
checks.

Harmless demonstration:

% mkfifo /tmp/1
% epspdf /etc/hostname /dev/null # any non-empty input file will do

hangs indefinitely trying to write to the pipe (as can be seen using
strace).

That's already a bug (and incidentally the one that actually
happened to me), but it seems it can be turned into an exploit using
a symlink. Though on my system this seems to be mitigated due to
this kernel patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=30aba6656f61ed44cba445a3c0d38b296fa9e8f5

But on systems where the patch is not installed or not active, it
would be possible to get any other user, possibly root, that runs
this program to write "test" to a new file of the attacker's choice.
I don't know how to turn this into a more serious privilege
escalation, but that's just my lack of fanatsy and knowledge of e.g.
every possible file and subdirectory under /etc. In any case,
writing such a file is already transgressing privileges.

To avoid this, as usual for this kind of exploit, files written
under publicly writable directories such as /tmp must be opened with
O_CREAT|O_EXCL (whatever the equivalent in texlua is, if any), or a
subdirectory must be created since mkdir will fail if the target
exists already, even as a dangling symlink.

Bug#1029912: kati: Depends: golang-glog (= 0.0~git20160126.23def4e-5) but it is not installable

2023-01-28 Thread Adrian Bunk

Package: kati
Version: 10.0.0+r32+git20220314.09dfa26c4e59-6
Severity: serious

The following packages have unmet dependencies:
 kati : Depends: golang-glog (= 0.0~git20160126.23def4e-5) but it is not 
installable


Depends is the wrong place for ${misc:Built-Using}.

Bug#1029911: rust-ureq FTBFS: error: unable to load build system class 'cargo': Can't locate String/ShellQuote.pm

2023-01-28 Thread Adrian Bunk

Source: rust-ureq
Version: 2.6.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=rust-ureq=all=2.6.2-1=1674929287=0

...
dh clean --buildsystem cargo
   dh_auto_clean -O--buildsystem=cargo
dh_auto_clean: error: unable to load build system class 'cargo': Can't locate 
String/ShellQuote.pm in @INC (you may need to install the String::ShellQuote 
module) (@INC contains: /<>/debian/dh-cargo/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl) at 
/<>/debian/dh-cargo/lib/Debian/Debhelper/Buildsystem/cargo.pm line 
37.
BEGIN failed--compilation aborted at 
/<>/debian/dh-cargo/lib/Debian/Debhelper/Buildsystem/cargo.pm line 
37.
Compilation failed in require at (eval 3) line 1.
BEGIN failed--compilation aborted at (eval 3) line 1.

make: *** [debian/rules:15: clean] Error 25

Processed: retitle 1026568 to python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files

2023-01-28 Thread Debian Bug Tracking System

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

> retitle 1026568 python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info 
> as directory, not files
Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: 
AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Changed Bug title to 'python-distutils-extra: FTBFS: setuptools 54+ ships 
.egg-info as directory, not files' from 'python-distutils-extra: FTBFS: 
AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != 
'''.
> thanks
Stopping processing here.

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

Processed: user debian-rele...@lists.debian.org, usertagging 1016936, closing 1016936

2023-01-28 Thread Debian Bug Tracking System

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was taf...@debian.org).
> usertags 1016936 + bsp-2023-01-ch-stcergue
There were no usertags set.
Usertags are now: bsp-2023-01-ch-stcergue.
> # Both affected packages have been successfully uploaded and built on Debian 
> infrastructure since.
> close 1016936
Bug #1016936 [dwz] dwz: Unknown debugging section .debug_addr causes some 
builds to fail
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''

2023-01-28 Thread Didier 'OdyX' Raboud

Control: tags -1 +confirmed +help

Hello there from the St-Cergue BSP where I've taken a look at this RC bug.

I can confirm this still FTBFS, and doesn't in stable, so let's check why.

The crux of the issue is that python3-setuptools from 54.0.0
(https://setuptools.pypa.io/en/latest/history.html#v54-0-0) does _not_ build 
the .egg-info as single file, but _only_ as directory [0].

This has the direct consequence that all tests fail for either of these 
reasons:
* the .egg-info is not a file, and cannot be compared with the expected 
version
* the .egg-info directory is not cleaned in clean() , hence the snapshot-vs-
result directory comparison is always going to flag the .egg-info directory as 
resulting cruft.

I've trimmed down the report below with an example result, which clearly shows 
the above two things.

Btw, from the FTBFS build directory, the fastest way to reproduce this is to 
run:

 LC_ALL=C LANGUAGE= LANG=C PYTHONPATH=. python3.10 test/auto.py -v -k empty -f


So. python-distutils-extra is broken by src:setuptools which is not going to 
revert this. python3-distutils-extra has 34 reverse Build-Depends, including 
python-apt, which makes it a "key package". Even if the B-D from python-apt 
can be amended, I also identify unattended-upgrades, software-properties and 
command-not-found. It looks like this won't be easy to remove from testing; we 
need to fix it.

Suggestions on the angle to use to tackle this welcome!

Best,

OdyX


[0] Also, distutils is deprecated "soon", so all this should get nuked post-
bookworm, but that's a discussion for another time.

Le mardi, 20 décembre 2022, 18.23:15 h CET Lucas Nussbaum a écrit :
> Source: python-distutils-extra
> Version: 2.47
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > # run tests with all supported python 2 and 3 versions
> > set -e; for python in `py3versions -s`; do \
> > 
> >   echo "-- Running tests with $python "; \
> >   LC_ALL=C LANGUAGE= LANG=C PYTHONPATH=. $python test/auto.py -v; \
> > 
> > done
> > -- Running tests with python3.11 
> > (...)
> > test_empty (__main__.T.test_empty)
> > empty source tree (just setup.py) ... FAIL
> > test_empty (__main__.T.test_empty)
> > empty source tree (just setup.py) ... FAIL

(...)

> > ==
> > FAIL: test_empty (__main__.T.test_empty)
> > empty source tree (just setup.py)
> > --
> > 
> > Traceback (most recent call last):
> >   File "/<>/test/auto.py", line 68, in test_empty
> >   
> > self.assertEqual(len(f), 1)
> > 
> > AssertionError: 4 != 1
> > 
> > ==
> > FAIL: test_empty (__main__.T.test_empty)
> > empty source tree (just setup.py)
> > --
> > 
> > Traceback (most recent call last):
> >   File "/<>/test/auto.py", line 43, in tearDown
> >   
> > self.assertEqual(cruft, '', 'no cruft after cleaning:\n' + cruft)
> > 
> > AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n"
> > != '' - diff -x foo.pot -x '*.pyc' -Nur
> > /tmp/tmp56zs21t4/s/foo.egg-info/PKG-INFO
> > /tmp/tmp15hh51oe/foo.egg-info/PKG-INFO - ---
> > /tmp/tmp56zs21t4/s/foo.egg-info/PKG-INFO1970-01-01 
00:00:00.0
> > + - +++ /tmp/tmp15hh51oe/foo.egg-info/PKG-INFO  2022-12-20
> > 09:38:33.086490908 + - @@ -0,0 +1,8 @@
> > - +Metadata-Version: 2.1
> > - +Name: foo
> > - +Version: 0.1
> > - +Summary: Test suite package
> > - +Home-page: https://foo.example.com
> > - +Author: Martin Pitt
> > - +Author-email: martin.p...@example.com
> > - +License: GPL v2 or later
> > - diff -x foo.pot -x '*.pyc' -Nur
> > /tmp/tmp56zs21t4/s/foo.egg-info/SOURCES.txt
> > /tmp/tmp15hh51oe/foo.egg-info/SOURCES.txt - ---
> > /tmp/tmp56zs21t4/s/foo.egg-info/SOURCES.txt 1970-01-01 
00:00:00.0
> > + - +++ /tmp/tmp15hh51oe/foo.egg-info/SOURCES.txt   2022-12-20
> > 09:38:33.090490943 + - @@ -0,0 +1,5 @@
> > - +setup.py
> > - +foo.egg-info/PKG-INFO
> > - +foo.egg-info/SOURCES.txt
> > - +foo.egg-info/dependency_links.txt
> > - +foo.egg-info/top_level.txt
> > - \ No newline at end of file
> > - diff -x foo.pot -x '*.pyc' -Nur
> > /tmp/tmp56zs21t4/s/foo.egg-info/dependency_links.txt
> > /tmp/tmp15hh51oe/foo.egg-info/dependency_links.txt - ---
> > /tmp/tmp56zs21t4/s/foo.egg-info/dependency_links.txt1970-01-01
> > 00:00:00.0 + - +++
> > /tmp/tmp15hh51oe/foo.egg-info/dependency_links.txt  2022-12-20
> > 09:38:33.086490908 + - @@ -0,0 +1 @@
> > - +
> > - diff -x foo.pot -x '*.pyc' -Nur
> >

Processed: Re: Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''

2023-01-28 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +confirmed +help
Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: 
AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Added tag(s) confirmed.
Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: 
AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Added tag(s) help.

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

1 2 3 >

1 - 100 of 242 matches

Mail list logo