Bug#1040584: marked as done (seek-bzip: broken symlinks: /usr/bin/seek-bunzip, /usr/bin/seek-table)

[Debian Bug Tracking System]

Your message dated Sun, 09 Jul 2023 05:49:09 +
with message-id 
and subject line Bug#1040584: fixed in node-openpgp-seek-bzip 1.0.5-3
has caused the Debian Bug report #1040584,
regarding seek-bzip: broken symlinks: /usr/bin/seek-bunzip, /usr/bin/seek-table
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.)


-- 
1040584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seek-bzip
Version: 1.0.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
broken symlinks:

0m22.5s ERROR: FAIL: Broken symlinks:
  /usr/bin/seek-bunzip -> ../share/nodejs/@openpgp/seek-bzip/bin/seek-bunzip 
(seek-bzip)
  /usr/bin/seek-table -> ../share/nodejs/@openpgp/seek-bzip/bin/seek-bzip-table 
(seek-bzip)


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: node-openpgp-seek-bzip
Source-Version: 1.0.5-3
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-openpgp-seek-bzip, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-openpgp-seek-bzip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Jul 2023 09:26:42 +0400
Source: node-openpgp-seek-bzip
Architecture: source
Version: 1.0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1040584
Changes:
 node-openpgp-seek-bzip (1.0.5-3) unstable; urgency=medium
 .
   * Team upload
   * Apply multi-arch hints (foreign)
   * Fix seek-bzip install (Closes: #1040584)
Checksums-Sha1: 
 217999f282768959bcee5f13e3ba054b6d98f07e 2210 
node-openpgp-seek-bzip_1.0.5-3.dsc
 e9461c7a2de4c4857b0ebe984d6b2f0dc44aa17d 3568 
node-openpgp-seek-bzip_1.0.5-3.debian.tar.xz
Checksums-Sha256: 
 312ad19e1e6a42e939f30a65a0364ec5247f6b99e6e50fd5f2731d4f1105fc92 2210 
node-openpgp-seek-bzip_1.0.5-3.dsc
 33f58e4da238ff71c499cd28e3de96418176f54215aa0a03cff231aaf61ccdfe 3568 
node-openpgp-seek-bzip_1.0.5-3.debian.tar.xz
Files: 
 9157113095540cf55651d5810b99f196 2210 javascript optional 
node-openpgp-seek-bzip_1.0.5-3.dsc
 a7633a3fc6bf64e8a2d963ed514b6e22 3568 javascript optional 
node-openpgp-seek-bzip_1.0.5-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmSqRWIACgkQ9tdMp8mZ
7ukPew/+LYPPvtfKuJ85AA4DHH1OGrQsCyvybE05BqkPns6KMaS6fFc4vF9NGi56
+duy7OA/mQ9xNBOLpY8hQ9nsdg8eKe6tzmDFkggmYFktTa4Tco0QcwOBLCdIcNNA
iL4mfb9iATosD2Ehf2XGe10bzbweh/I67Gfz7yp0e1Rh492XFlEY8dt+rgCZ9jl3
VVizGR/4QchYMR4TimRPC0AOH46fx1RWP6IUUDdv5BdHU0TYhtU1F908ooVXyRCA
9OgVy3moMbzZEDq90EMG0pkDXVP5yCen9H6ypkB43iXsPVy8qzamnN3i2wrbOS1b
jvLR7WWG8uIWfOCxql1NQ9o0xH4zqkDvV9AwZSIbD5TA4Elw85pv1iNNWY/NHHFi
s7YDqgsbapQBk4QsGXEVegXiiJPQOdM49XXjFArD2i1QTCvtECzn7c8ehowwqvPn
PjahqBt09QAP6vLvrnpinTym5yzZ7WY5x0sY1Rhe+0fpCNV3T78yQbHFlydWPcMD
Yj8ZH9DTp1yfKSikpHt1wPU0g6IMMPc4UeUTFLW5uXB2h1i7FZL+bDD1HHU+OoQL
stusLBJ9hUEZjgVJTist26xoDmyNhl1GCHD150Y5bEISy6MvPsIvytoV82i+sKG/
RjaHEsvUTvG4uOA2Gqs5xssvQfzcun3NOJWAUhy+SxIucDs2ToE=
=7Qe/
-END PGP SIGNATURE End Message ---

Bug#1040682: FTBFS in colord with meson 1.2.0 rc2

[Eli Schwartz]

Source: colord
Version: 1.4.6-2.2
Severity: serious
Tags: ftbfs

colord successfully passes dh_auto_configure, but fails to build
immediately after:

```
dh override_dh_auto_configure-arch
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure-indep
make[1]: Entering directory '/<>'
meson configure  -Dsession_example=false -Ddaemon_user=colord
-Dvapi=true -Ddocs=false -Dinstalled_tests=true -Dargyllcms_sensor=true
 -Dsane=true -Dprint_profiles=true

ERROR: No valid build directory found, cannot modify options.
make[1]: *** [debian/rules:38: override_dh_auto_configure-indep] Error 1
```

The cause of this is that setup options are passed to meson's "print the
values of all options" subcommand.

Previous versions of meson would print the following warning:

The source directory instead of the build directory was specified.
Only the default values for the project are printed, and all command
line parameters are ignored.


The release candidate makes this an error instead. If you want to print
the values of available options, simply avoid passing arguments; this
works both in a source directory and a build directory.

-- 
Eli Schwartz

Bug#1040675: ca-certificates-java: incorrect "Breaks:" versions about ubuntu

[Vincent Lefevre]

Package: ca-certificates-java
Severity: serious

ca-certificates-java 20230707 has

Breaks: openjdk-11-jre-headless (<< 11.0.19+7~1~), openjdk-17-jre-headless (<< 
17.0.8~6-3~), openjdk-18-jre-headless (<< 18.0.2+9-2ubuntu1~), 
openjdk-19-jre-headless (<< 19.0.2+7-0ubuntu4~), openjdk-20-jre-headless (<< 
20.0.1+9~1~), openjdk-21-jre-headless (<< 21~9ea-1~), openjdk-8-jre-headless 
(<< 8u382~b04-2~)

with versions concerning ubuntu. This is Debian here! This prevents
its installation in Debian when openjdk-18-jre-headless from unstable
is installed.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Ted]

Thank you for pointing this out. I have removed python3-setuptools and
successfully built gpgme1.0.
For fun I will see if I can figure out how to add this to Conflicts.

On Wed, Jul 5, 2023 at 12:30 PM Andreas Metzler  wrote:

> On 2023-07-04 Ted  wrote:
> > The only software which has ever run here is from a bookworm or vscodim
> > repo so i will just wait for bookworm to stabilize and hope i can abandon
> > the workarounds in the future.
>
> Hello,
>
> You were right all the time. python3-setuptools is the culprit,
> installing it breaks the build.
>
> cu Andreas
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>


-- 

-Theodoric

Bug#1040297: marked as done (gnome-shell: fails to start on login: failed to allocate 51540049304 bytes)

[Debian Bug Tracking System]

Your message dated Sat, 8 Jul 2023 23:02:59 +0100
with message-id 
and subject line Re: Bug#1040297: gnome-shell: fails to start on login: failed 
to allocate 51540049304 bytes
has caused the Debian Bug report #1040297,
regarding gnome-shell: fails to start on login: failed to allocate 51540049304 
bytes
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.)


-- 
1040297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome
Version: 1:43+1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vent...@debian.org

Dear Maintainer,

since yesterday, Gnome fails to start and falls back to GDM3 when I try to
login. I cannot start gnome on wayland nor xorg anymore. Gnome classic fails as
well. Falling back to the terminal and trying `startx` does also not start
gnome either. Installing something else (MATE) helps.

Since there was no upgrade in Gnome recently, I suspect that one of the
dependencies got an upgrade. I do vaguely remember evolution, systemd and libc6
being the biggest updates today.

Here's some output of journalctl that looks suspicious. Maybe it helps you:

Jul 03 16:48:14 fiona dbus-daemon[1894]: [session uid=1000 pid=1894] Activating 
service name='org.gnome.ScreenSaver' requested by ':1.63' (uid=1000 pid=2485 
comm="/usr/libexec/gsd-usb-pr>
Jul 03 16:48:14 fiona dbus-daemon[1894]: [session uid=1000 pid=1894] 
Successfully activated service 'org.freedesktop.portal.IBus'
Jul 03 16:48:14 fiona gnome-software-service.desktop[2490]: Unable to acquire 
bus name 'org.gnome.Software'
Jul 03 16:48:14 fiona gnome-shell[2112]: ../../../glib/gmem.c:136: failed to 
allocate 51540049304 bytes
Jul 03 16:48:14 fiona gnome-shell[2112]: == Stack trace for context 
0x557fe8d747b0 ==
Jul 03 16:48:14 fiona gnome-shell[2112]: #0   557fe9756f10 i   
resource:///org/gnome/shell/ui/appDisplay.js:2124 (20b9b5e92b50 @ 110)
Jul 03 16:48:14 fiona gnome-shell[2112]: #1   7ffd1218ef90 I   self-hosted:164 
(3bea9db8c380 @ 272)
Jul 03 16:48:14 fiona gnome-shell[2112]: #2   557fe9756e78 i   
resource:///org/gnome/shell/ui/appDisplay.js:2138 (20b9b5e92b00 @ 147)
Jul 03 16:48:14 fiona gnome-shell[2112]: #3   557fe9756de8 i   
resource:///org/gnome/shell/ui/appDisplay.js:2229 (20b9b5e92dd0 @ 21)
Jul 03 16:48:14 fiona gnome-shell[2112]: #4   557fe9756d38 i   
resource:///org/gnome/shell/ui/appDisplay.js:2106 (20b9b5e92a60 @ 325)
Jul 03 16:48:14 fiona gnome-shell[2112]: #5   557fe9756c98 i   
resource:///org/gnome/shell/ui/appDisplay.js:490 (20b9b5e90ba0 @ 27)
Jul 03 16:48:14 fiona gnome-shell[2112]: #6   557fe9756bf8 i   
resource:///org/gnome/shell/ui/appDisplay.js:2081 (20b9b5e92fb0 @ 27)
Jul 03 16:48:14 fiona gnome-shell[2112]: #7   557fe9756b40 i   
resource:///org/gnome/shell/ui/appDisplay.js:2329 (20b9b5e93060 @ 336)
Jul 03 16:48:14 fiona gnome-shell[2112]: #8   557fe9756aa0 i   
resource:///org/gnome/shell/ui/appDisplay.js:1844 (20b9b5e92970 @ 27)
Jul 03 16:48:14 fiona gnome-shell[2112]: #9   557fe9756a00 i   
resource:///org/gnome/shell/ui/appDisplay.js:2305 (20b9b5e93600 @ 27)
Jul 03 16:48:14 fiona gnome-shell[2112]: #10   557fe9756958 i   
resource:///org/gnome/shell/ui/appDisplay.js:1504 (20b9b5e915b0 @ 115)
Jul 03 16:48:14 fiona gnome-shell[2112]: #11   7ffd12191b10 I   self-hosted:164 
(3bea9db8c380 @ 272)
Jul 03 16:48:14 fiona gnome-shell[2112]: #12   557fe97568b8 i   
resource:///org/gnome/shell/ui/appDisplay.js:1500 (20b9b5e914c0 @ 226)
Jul 03 16:48:14 fiona gnome-shell[2112]: #13   557fe9756808 i   
resource:///org/gnome/shell/ui/appDisplay.js:1067 (20b9b5e904c0 @ 88)
Jul 03 16:48:14 fiona gnome-shell[2112]: #14   557fe9756778 i   
resource:///org/gnome/shell/ui/appDisplay.js:1374 (20b9b5e91100 @ 44)
Jul 03 16:48:14 fiona gnome-shell[2112]: #15   557fe97566f8 i   
resource:///org/gnome/shell/ui/appDisplay.js:638 (20b9b5e8f920 @ 12)
Jul 03 16:48:14 fiona gnome-shell[2112]: #16   7ffd12192880 b   
resource:///org/gnome/gjs/modules/core/_signals.js:114 (3bea9dba0790 @ 433)
Jul 03 16:48:14 fiona gnome-shell[2112]: #17   557fe9756670 i   
resource:///org/gnome/shell/ui/appFavorites.js:75 (20b9b5e94d80 @ 35)
Jul 03 16:48:14 fiona gnome-shell[2112]: #18   557fe97565c0 i   
resource:///org/gnome/shell/misc/parentalControlsManager.js:95 (20b9b5e95510 @ 
590)
Jul 03 16:48:14 fiona gnome-shell[2112]: #19   557fe9756528 i   
self-hosted:1429 (1caa8ee391f0 @ 30)
Jul 03 16:48:14 fiona gnome-shell[2112]: #20   7ffd12193f70 b   self-hosted:632 
(1caa8eeb2e70 @ 15)
Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: 

Bug#1040049: gnome-terminal: assert hit on mouseover, all open terminal windows are lost

[Egmont Koblinger]

Hi,

FYI: upstream issue https://gitlab.gnome.org/GNOME/vte/-/issues/2577 is
related, but did not fix this very problem.

The current problem is tracked upstream at
https://gitlab.gnome.org/GNOME/vte/-/issues/2636.

e.

Processed: Re: Bug#1040297: gnome-shell: fails to start on login: failed to allocate 51540049304 bytes

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libc6 2.37-3
Bug #1040297 [gnome-shell] gnome-shell: fails to start on login: failed to 
allocate 51540049304 bytes
Bug reassigned from package 'gnome-shell' to 'libc6'.
No longer marked as found in versions gnome-shell/43.6-1.
Ignoring request to alter fixed versions of bug #1040297 to the same values 
previously set
Bug #1040297 [libc6] gnome-shell: fails to start on login: failed to allocate 
51540049304 bytes
Marked as found in versions glibc/2.37-3.
> fixed -1 2.37-5
Bug #1040297 [libc6] gnome-shell: fails to start on login: failed to allocate 
51540049304 bytes
Marked as fixed in versions glibc/2.37-5.
> tags -1 - moreinfo
Bug #1040297 [libc6] gnome-shell: fails to start on login: failed to allocate 
51540049304 bytes
Removed tag(s) moreinfo.

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

Bug#1040297: gnome-shell: fails to start on login: failed to allocate 51540049304 bytes

[Simon McVittie]

Control: reassign -1 libc6 2.37-3
Control: fixed -1 2.37-5
Control: tags -1 - moreinfo

On Sat, 08 Jul 2023 at 16:08:14 +0200, Bastian Venthur wrote:
> I've just updated all packages from unstable, including glibc and the
> problem is solved.

Let's assume this was the glibc bug with corrupted locale archives unless
someone finds evidence to the contrary, then. I'll close the bug after the
reassign command is processed.

smcv

Bug#1034939: [Pkg-rust-maintainers] Bug#1040477: Bug#1040477: librust-syn-1-dev fails to coinstall

[Fabian Grünbichler]

On Thu, Jul 06, 2023 at 04:39:08PM +0100, Peter Green wrote:
> > I'd be very interested in knowing what this self-conflict is supposed to
> > achieve.
> 
> It is common upstream for there to be multiple semver-incompatible versions
> of each rust crate in use at a given time. Incompatibilities can range from
> minor corner cases that are easily patched away to complete redesigns
> 
> We try to only package one version of each crate at a time, but sometimes
> that isn't practical. When it becomes impractical we crate semver-suffix
> packages. The convention in the rust team is that the un-suffixed packages
> are used for the latest version and suffixed versions are used for any
> older versions.
> 
> When packaged crates are installed on a Debian system. They are installed
> in a path that depends on the upstream version of a crate.
> 
> This creates a problem though, if the same version is packaged as both
> a non-suffixed and suffixed version. Something that happens fairly
> frequently when a new version is introduced e.g.
> 
> Before:
> 
> librust-foo-dev version 1.23-1
> 
> After:
> 
> librust-foo-1-dev version 1.23-2
> librust-foo-dev version 2.34-1
> 
> This doesn't always happen, indeed it didn't happen in the case of syn,
> because a new upstream release of syn 1.x at the same time at the same
> time the semver suffix was introduced. However debcargo works on one
> crate at a time. so it doesn't know if this has happened or not.
> 
> When this happens, it leads to a file conflict. In an attempt to fix
> this breaks+replaces were added. Unfortunately these proved to be
> insufficient because while breaks against virtual packages work,
> replaces apparently don't. We are in the process of considering
> several options to fix this, but overall switching to conflicts+replaces
> seems the least likely to be problematic.
> 
> Do you encounter the same problem if you replace the breaks with
> conflicts? if so we would need to do something about it. I think
> the easiest would probablly be to put a version constraint on the
> conflicts/replaces. It would mean we would have to take care that
> semver-suffixed packages had a higher Debian revision than their
> un-suffixed counterparts, but I think that is managable.

and, with a bit of unexpected delay (sorry), the result of a discussion
Helmut and me had in parallel on IRC:

the issue with Conflicts arises in combination with M-A:same, since dpkg
and apt don't agree on which one of those two "angles" has higher
priority. to sort that out would require a release cycle or two.

it seems like this leaves the other alternative from #1034939 [0,
CC-ed], namely, switching the breaks and replaces to point at the real
package (version guarded), so that upgrading from "old" non suffixed
package (for which a newer version should exist by definition if a
suffixed package of the same version exists) while installing the
suffixed package of the same "old" version at the same time works. the
main downside (and reason why we preferred the Conflicts-based variant)
is that this means that two suffixed packages with different versions
are no longer co-installable (since the one with the higher version
would break the older one). thankfully, such issues should seldomly
matter in practice. or we could investigate just switching the replaces,
and keeping the breaks as is.

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

Bug#1040573: marked as done (python-screed: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2023 19:49:58 +
with message-id 
and subject line Bug#1040573: fixed in python-screed 1.1.2-1
has caused the Debian Bug report #1040573,
regarding python-screed: implicitly depends on python3-pkg-resources
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.)


-- 
1040573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-screed
Version: 1.0.5-4
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-screed/35451522/log.gz


 24s  ERRORS 

 24s __ ERROR collecting screed/tests/test_attriberror.py 
___
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_attriberror.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s screed/__init__.py:39: in 
 24s from pkg_resources import get_distribution, DistributionNotFound
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s  ERROR collecting screed/tests/test_convert.py 
_
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_convert.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s screed/__init__.py:39: in 
 24s from pkg_resources import get_distribution, DistributionNotFound
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s ___ ERROR collecting screed/tests/test_db.py 
___
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_db.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s screed/__init__.py:39: in 
 24s from pkg_resources import get_distribution, DistributionNotFound
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s ___ ERROR collecting screed/tests/test_dictionary.py 
___
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_dictionary.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s screed/__init__.py:39: in 
 24s from pkg_resources import get_distribution, DistributionNotFound
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s __ ERROR collecting screed/tests/test_dna.py 
___
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_dna.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s screed/__init__.py:39: in 
 24s from pkg_resources import get_distribution, DistributionNotFound
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s _ ERROR collecting screed/tests/test_fasta.py 
__
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ocsondrc/downtmp/autopkgtest_tmp/screed/tests/test_fasta.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s 

Bug#1040634: marked as done (pycoast autopkg tests fail with pillow 10.0.0)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2023 17:20:25 +
with message-id 
and subject line Bug#1040634: fixed in pycoast 1.6.1+dfsg-3
has caused the Debian Bug report #1040634,
regarding pycoast autopkg tests fail with pillow 10.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.)


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

Package: src:pycoast
Version: 1.6.1+dfsg-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycoast/35498778/log.gz

[...]
101s self = 
101s draw = 
101s position = (8.56126709559166, 4), txt = '50W'
101s font = , align = 'CT'
101s kwargs = {'fill': 'white', 'lat_placement': 'lr', 'lon_placement': 'tb', 
'minor_is_tick': True, ...}

101s
101s def _draw_text(self, draw, position, txt, font, align="cc", **kwargs):
101s """Draw text with agg module."""
101s >   txt_width, txt_height = draw.textsize(txt, font)
101s E   AttributeError: 'ImageDraw' object has no attribute 'textsize'
101s
101s ../build.wr6/src/pycoast/cw_base.py:170: AttributeError
101s === short test summary info 

101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestContourWriterPIL::test_grid_germ
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestContourWriterPIL::test_add_points_coordinate_conversion
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestFromConfig::test_cache
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestFromConfig::test_caching_with_param_changes
101s === 4 failed, 35 passed, 2 skipped, 16 deselected in 30.31s 

--- End Message ---
--- Begin Message ---
Source: pycoast
Source-Version: 1.6.1+dfsg-3
Done: Antonio Valentino 

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

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

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated pycoast 
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, 08 Jul 2023 16:32:00 +
Source: pycoast
Architecture: source
Version: 1.6.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Closes: 1040634
Changes:
 pycoast (1.6.1+dfsg-3) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Bump Standards-Version to 4.6.2, no changes.
   * Bump debhelper compat to 13.
 .
   [ Antonio Valentino ]
   * debian/control:
 - fix lintian warnings (break/replaces too old versions).
   * debian/patches:
 - new 0006-Compatibility-with-Pillow-10.patch (Closes: #1040634).
Checksums-Sha1:
 dd3f01478bb28fbd7d25c4bbb0cec1db07e62995 2446 pycoast_1.6.1+dfsg-3.dsc
 9f95dcb0d83082e6ebd4ad86bf8ec229407fbb6a 9008 
pycoast_1.6.1+dfsg-3.debian.tar.xz
 fa7833b9ed55c3f324524c242874ceb363fd85fd 11800 
pycoast_1.6.1+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 74e8d902e44c313bb78fd1c9b8d831af0e1c2b9431f78e4bc609264e00f8b860 2446 
pycoast_1.6.1+dfsg-3.dsc
 51754a8ea21b4eedf1cdc8602966747c51b28b1a98c5bd1f77a4155e0672696b 9008 
pycoast_1.6.1+dfsg-3.debian.tar.xz
 58cb2f56884bf575ed491357bd85426d304309990ab560a57ff1ad6098c53a1e 11800 
pycoast_1.6.1+dfsg-3_amd64.buildinfo
Files:
 ae52afe5f34e9062746b3286256ee1c5 2446 python optional pycoast_1.6.1+dfsg-3.dsc
 c7b939714c83191d98299f90e15f7a95 9008 python optional 
pycoast_1.6.1+dfsg-3.debian.tar.xz
 bc79148850279bf1e50c49d8b8693084 11800 python optional 
pycoast_1.6.1+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEEO3DyCaX/1okDxHLF6/SKslePmBIFAmSpk9MdHGFudG9uaW8u
dmFsZW50aW5vQHRpc2NhbGkuaXQACgkQ6/SKslePmBLAdRAA0hT4z+XfNVZ53oAr
fsdGlIAMz+He+kOSNZw/Aoc6UYXuD4TKxvZrVPohK2x6LdxynKVEvuwHgh3O8WEZ
qQ2MVKOcxvdn11e21qCeL4G6l3JE+bY5VqMvHaP1+mfCMWVtPOTLWhbuN9qxbVTQ
HhziRkhkZWYOenMa67v9o2Bhxv741wS8Fpcn8WlMLjaYSmLS6+pGcAcYPHHFv2Zs
jjkyQoRLUTnZ6o8fB2YwxFntf62+QNYaTWNTL7LuA3j4NEbKd7Qt4NqHDOxsVYNG
w5CGmR5QsrMeqGt5SRWQQcr8Blmn1ciwW8wUoHFvxXdY2zKlxVZ0f43DxaQlYr+D

Processed: Bumping severity of Qt 5.15.10 FTBFS bugs

[Debian Bug Tracking System]

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

> # Qt 5.15.10 is in unstable now
> severity 1038402 serious
Bug #1038402 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with 
Qt ≥ 5.15.9: QPainterTest failures
Severity set to 'serious' from 'important'
> severity 1038737 serious
Bug #1038737 [src:photoqt] photoqt: FTBFS on mips64el: Unable to import 
PyChromecast
Ignoring request to change severity of Bug 1038737 to the same value.
> thanks
Stopping processing here.

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

Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults

[Lisandro Damian Nicanor Perez Meyer]

On sábado, 8 de julio de 2023 12:27:34 -03 Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi,
> 
> On Thu, 6 Jul 2023 at 14:30, Helmut Grohne  wrote:
> > Source: qt6-virtualkeyboard
> > Version: 6.4.2+dfsg-2
> > Severity: serious
> > Tags: ftbfs
> > 
> > qt6-virtualkeyboard fails to build from source in unstable when passing
> 
> > DEB_BUILD_OPTIONS=parallel=1. A build ends as follows:
> Interestingly enough I could only reproduce the issue by using sbuild.
> If I hand compile it using dpkg-buildpackage directly on a clean
> machine things just work.

More info: I did a build of qt6-virtualkeyboard on 6.5.1 with parallel=1 with 
no issues... but at the same time not the fully proper environment, because it 
was an sbuild build using Ubuntu focal and some special Qt build I have at 
hand. But maybe the answer is there.

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

Bug#1040652: librust-system-deps-dev: Depends: librust-cfg-expr-0.10+default-dev that is no longer provided by librust-cfg-expr-dev

[Adrian Bunk]

Package: librust-system-deps-dev
Version: 6.0.2-2
Severity: serious
Tags: trixie sid

The following packages have unmet dependencies:
 librust-system-deps-dev : Depends: librust-cfg-expr-0.10+default-dev

Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults

[Lisandro Damián Nicanor Pérez Meyer]

Hi,


On Thu, 6 Jul 2023 at 14:30, Helmut Grohne  wrote:
>
> Source: qt6-virtualkeyboard
> Version: 6.4.2+dfsg-2
> Severity: serious
> Tags: ftbfs
>
> qt6-virtualkeyboard fails to build from source in unstable when passing
> DEB_BUILD_OPTIONS=parallel=1. A build ends as follows:

Interestingly enough I could only reproduce the issue by using sbuild.
If I hand compile it using dpkg-buildpackage directly on a clean
machine things just work.

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/

Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3

[Bastian Venthur]

I've just updated all packages from unstable, including glibc and the 
problem is solved. So, it might have been the one you've described. 
Thanks for your help and your work!



Cheers,

Bastian

Am 08.07.23 um 11:32 schrieb Simon McVittie:

On Thu, 06 Jul 2023 at 09:50:57 +0100, Simon McVittie wrote:

On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote:

 #5  0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0
+ 0x8a7ce)
 #6  0x7f134ccee180 e_source_set_display_name
(libedataserver-1.2.so.27 + 0x57180)


Well, this is messed up - something is setting the display name of an
ESource (a calendar or address book or something similar) to a value that
is, apparently, so long that allocating memory for its collation key (a
version that has been modified to sort in the correct locale-sensitive
order) will fail.


I wonder whether this is the same root cause as #1040452: glibc (>= 2.37-2)
sometimes generating corrupted locale archives? That might explain why
g_utf8_collate_key() would get nonsense results.

Please try with glibc (>= 2.37-5) which fixes that bug, and maybe this
one too.

 smcv



--
Dr. Bastian Venthur https://venthur.de
Debian Developer venthur at debian org

Bug#1040252: [3dprinter-general] Bug#1040252: cura-engine FTBFS on some 32bit architectures

[Gregor Riepl]

Hi myon,

I've tested the patch both on amd64 and i686 (in a chroot) and pushed it 
to Salsa.


Could you upload cura-engine 5.0.0-4 when you have time?
Thank you very much!

Regards,
Gregor

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1040252 https://github.com/Ultimaker/CuraEngine/issues/1897
Bug #1040252 [src:cura-engine] cura-engine FTBFS on some 32bit architectures
Set Bug forwarded-to-address to 
'https://github.com/Ultimaker/CuraEngine/issues/1897'.
> tags 1040252 patch
Bug #1040252 [src:cura-engine] cura-engine FTBFS on some 32bit architectures
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1034028: marked as done (ruby-rails-assets-jquery: autopkgtest regression: Don't know how to build task 'assets:precompile')

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2023 12:54:30 +
with message-id 
and subject line Bug#1034028: fixed in ruby-rails-assets-jquery 3.5.1+dfsg-2
has caused the Debian Bug report #1034028,
regarding ruby-rails-assets-jquery: autopkgtest regression: Don't know how to 
build task 'assets:precompile'
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.)


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

Source: ruby-rails-assets-jquery
Version: 3.5.1+dfsg-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since November 
2021. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rails-assets-jquery/32420365/log.gz

Use `bundle info [gemname]` to see where a bundled gem is installed.
+ cat
+ cat
+ cat
+ cat
+ bundle exec rake assets:precompile
rake aborted!
Don't know how to build task 'assets:precompile' (See the list of 
available tasks with `rake --tasks`)


(See full trace by running task with --trace)


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-rails-assets-jquery
Source-Version: 3.5.1+dfsg-2
Done: Pirate Praveen 

We believe that the bug you reported is fixed in the latest version of
ruby-rails-assets-jquery, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-rails-assets-jquery 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, 08 Jul 2023 17:40:49 +0530
Source: ruby-rails-assets-jquery
Architecture: source
Version: 3.5.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Pirate Praveen 
Closes: 1034028
Changes:
 ruby-rails-assets-jquery (3.5.1+dfsg-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Pirate Praveen ]
   * Fix autopkgtest regression by switching to ruby-sprockets-rails
 (Closes: #1034028)
   * Bump Standards-Version to 4.6.2 (no changes needed)
   * Drop obsolete X{S,B}-Ruby-Versions fields
   * Switch to ${ruby:Depends} for ruby dependencies
Checksums-Sha1:
 57e06fc40739fce78355f3340ce14381f027d528 2290 
ruby-rails-assets-jquery_3.5.1+dfsg-2.dsc
 64091a2905f3f729f7896dafd36169ecad4a8c5d 4180 
ruby-rails-assets-jquery_3.5.1+dfsg-2.debian.tar.xz
 7a4cd1d3a10fabfc4d785eabc7313242a4b06a2a 9407 
ruby-rails-assets-jquery_3.5.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 d0fdc687b553ba0b071a4d04b4fca864cd49d234b205e7a4f7ed416c22a87354 2290 
ruby-rails-assets-jquery_3.5.1+dfsg-2.dsc
 7b30d0704fc99ad41ea803340de3adba8e7d27566b0b931ddbc800038390a1ca 4180 
ruby-rails-assets-jquery_3.5.1+dfsg-2.debian.tar.xz
 526a2861df48da4d635ae8c41b9101df18ed00041177c9c774f349318dad72f7 9407 
ruby-rails-assets-jquery_3.5.1+dfsg-2_amd64.buildinfo
Files:
 ca07a6f90591498268bcd763d11138f8 2290 ruby optional 
ruby-rails-assets-jquery_3.5.1+dfsg-2.dsc
 89244caf63f5bb24c7525f81fb818c29 4180 ruby optional 
ruby-rails-assets-jquery_3.5.1+dfsg-2.debian.tar.xz
 0174580da316702d6bdf702584ee57dc 9407 ruby optional 
ruby-rails-assets-jquery_3.5.1+dfsg-2_amd64.buildinfo

-BEGIN PGP 

Bug#1037352: marked as done (pushpin: ftbfs with rust-base64 0.21)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2023 12:21:19 +
with message-id 
and subject line Bug#1037352: fixed in pushpin 1.36.0-3
has caused the Debian Bug report #1037352,
regarding pushpin: ftbfs with rust-base64 0.21
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.)


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

Package: pushpin
Version: 1.36.0-2
Severity: serious
Tags: trixie, sid, ftbfs, patch

pushpin FTBFS with the new version of rust-base64 due to an upper limit
on the dependency in Cargo.toml. If I remove the upper limit then the code
builds fine.

(I prepared a debdiff, but it ended up with a bunch of noise left behind
from the build process, so I haven't bothered including it).
--- End Message ---
--- Begin Message ---
Source: pushpin
Source-Version: 1.36.0-3
Done: Jan Niehusmann 

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

Debian distribution maintenance software
pp.
Jan Niehusmann  (supplier of updated pushpin 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, 08 Jul 2023 13:27:37 +0200
Source: pushpin
Architecture: source
Version: 1.36.0-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann 
Changed-By: Jan Niehusmann 
Closes: 1037352
Changes:
 pushpin (1.36.0-3) unstable; urgency=medium
 .
   * Relaxed upper limit from base64 dependency. (Closes: #1037352)
Checksums-Sha1:
 e617bcc8298ababf5c794944b410f7aa6b097fb2 1934 pushpin_1.36.0-3.dsc
 ba001e141934c829697deefe5822366c4a1922b5 22944 pushpin_1.36.0-3.debian.tar.xz
 d3011ba7d67b7f18d43d3cb52fe6126018590c7a 17117 pushpin_1.36.0-3_amd64.buildinfo
Checksums-Sha256:
 1473d151b88a83f66b275ce07ff519d261b6cdd6ffe963166e7b7d3fe51cc30c 1934 
pushpin_1.36.0-3.dsc
 809237ac5180ce54a8f9173c29c19047517bdbec62334e53457ab6ac0412c891 22944 
pushpin_1.36.0-3.debian.tar.xz
 373b9027fc77715bca3ff73132a35f4021f781ec304769482b0cec85d9a8734b 17117 
pushpin_1.36.0-3_amd64.buildinfo
Files:
 99f81f771209b06cffce3b9709e95566 1934 net optional pushpin_1.36.0-3.dsc
 df75ab1e588c740dc30399d9f7920b39 22944 net optional 
pushpin_1.36.0-3.debian.tar.xz
 972a2d52314565341af3e294040f74f7 17117 net optional 
pushpin_1.36.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAmSpSoMPHGphbkBkZWJp
YW4ub3JnAAoJEMJAzpldAmsRwdUL/3bpjHOrQpo7AGwJAwwyGQWsjJLllkR8Iusx
6T0BCSPFcfHwFcSwLVgsVu+CkF8ksOd2WhIgOTDHmmqZdDXS2XE56Ms4MYbb8pGJ
sA75Oc8jO6DM0jWz6YH1bD7DznZ8mUWV5sAll0Lsli5oS5lKp5BGD6vhwZgS9O4l
iReYGkpwdhvfmGXo7Ptixm1rAI97YPAHVXTsWWCZeEWEXxr7Ih1Prjve6vfUr4l4
xOQbPPiKF+ndPyPe1mS2rBGLcZhyO6Gsmag8Ll/sXiB5SkQPrCeqDZmW4cdGOfjT
9GevWJfMpKtGo0ljJ0PIjvBXyY+BAruU0EbT04JammN4LQc+QHoHBcR1TmDvjoVt
hJYP8lX2nQFUMkR+FhRBqFvrbik+oO+N1MebUfiC3ldyZ+Uib2Oxk555KwvlnvXS
v7yawIAAb1A8NN34IJM7FXCGZiM5uiO5QHMpt7rfJ4tR8901TgXKRryLJQB1GBie
JK7KHPnlbUebudG0oYhTx3IUl7Vzeg==
=RQEL
-END PGP SIGNATURE End Message ---

Bug#1040252: cura-engine FTBFS on some 32bit architectures

[Gregor Riepl]

This is actually a bug in the test and not CuraEngine.

In tests/InfillTest.cpp:104, they format a size_t as %lld instead of 
%zu. %llu works as well, but it's not 100% correct with a 32-bit size_t.


Current upstream HEAD still has the bug, so I'm going to report it there 
as well: 
https://github.com/Ultimaker/CuraEngine/blob/main/tests/InfillTest.cpp#L103


Patch:

diff --git a/tests/InfillTest.cpp b/tests/InfillTest.cpp
index 23b083f5..6f39b708 100644
--- a/tests/InfillTest.cpp
+++ b/tests/InfillTest.cpp
@@ -100,7 +100,7 @@ namespace cura
 result_lines(result_lines),
 result_polygons(result_polygons)
 {
-name = 
makeName("InfillTestParameters_P%d_Z%d_C%d_L%lld__%lld", 
(int)params.pattern, (int)params.zig_zagify, 
(int)params.connect_polygons, params.line_distance, test_polygon_id);
+name = 
makeName("InfillTestParameters_P%d_Z%d_C%d_L%lld__%zu", 
(int)params.pattern, (int)params.zig_zagify, 
(int)params.connect_polygons, params.line_distance, test_polygon_id);

 }

 friend std::ostream& operator<<(std::ostream& os, const 
InfillTestParameters& params)

Processed: fixed 997182 in 2.3.1-5

[Debian Bug Tracking System]

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

> fixed 997182 2.3.1-5
Bug #997182 [src:tiptop] tiptop: FTBFS: helpwin.c:64:3: error: format not a 
string literal and no format arguments [-Werror=format-security]
Ignoring request to alter fixed versions of bug #997182 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1040642: upower/experimental must build depend on libgudev-1.0-dev (>= 238)

[Adrian Bunk]

Source: upower
Version: 1.90.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=upower=1.90.2-1

...
Dependency gudev-1.0 found: NO found 237 but need: '>= 238'
Dependency lookup for gudev-1.0 with method 'pkgconfig' failed: Invalid 
version, need 'gudev-1.0' ['>= 238'] found '237'.
CMake binary for 1 is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
Dependency lookup for gudev-1.0 with method 'cmake' failed: CMake binary for 
machine 1 not found. Giving up.
Run-time dependency gudev-1.0 found: NO 

../meson.build:72:14: ERROR: Dependency lookup for gudev-1.0 with method 
'pkgconfig' failed: Invalid version, need 'gudev-1.0' ['>= 238'] found '237'.
dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup 
.. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dman=true -Dgtk-doc=true 
-Dintrospection=enabled -Dsystemdsystemunitdir=/lib/systemd/system returned 
exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25

Bug#1034565: ftbfs tests fail on ppc64el and mips64el

[Pirate Praveen]

On Tue, 18 Apr 2023 17:08:34 +0530 Pirate Praveen  
wrote:

> Failures:
>
>1) Prometheus::Client::Helper::MmapedFile file does not exist 
creates

> a file with minimum initial size
>   Failure/Error: expect(File.size(subject.filepath)).to
> eq(subject.send(:initial_mmap_file_size))
>
> expected: 4096
>  got: 16384
>
> (compared using ==)
>   # ./spec/prometheus/client/helpers/mmaped_file_spec.rb:30:in
> `block (3 levels) in '

Fixed upstream in 0.20 and 0.23 is being uploaded to experimental. We 
can close this once we confirm the failures are fixed.

Bug#1039916: ruby-derailed-benchmarks: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0)

[Pirate Praveen]

On Thu, 29 Jun 2023 16:03:13 +0200 Paul Gevers  
wrote:


> 
┌──┐

>   19s │ Checking Rubygems dependency resolution on ruby3.1
>  │
>   19s
> 
└──┘

>   19s  19s GEM_PATH= ruby3.1 -e gem\ \"derailed_benchmarks\"
>   19s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
> `rescue in block in activate_dependencies': Could not find
> 'memory_profiler' (~> 0) among 102 total gem(s) 
(Gem::MissingSpecError)

>   19s Checked in

This is fixed upstream but the new upstream version adds a new 
dependency dead_end gem. Also gitlab has moved this dependency from 
production to test group in Gemfile, so we can remove this once the 
dependency is dropped from gitlab.

Bug#1033705: golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist

[Pirate Praveen]

On Thu, 30 Mar 2023 19:19:44 +0200 Paul Gevers  
wrote:

> autopkgtest [15:18:15]: test command1: preparing testbed
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Correcting dependencies...Starting pkgProblemResolver with broken 
count: 1

> Starting 2 pkgProblemResolver with broken count: 1
> Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
> Broken autopkgtest-satdep:amd64 Depends on ruby-gitaly-proto:amd64 <
> none @un H >
>Removing autopkgtest-satdep:amd64 because I can't find
> ruby-gitaly-proto:amd64

ruby-gitaly-proto used to be provided by ruby-gitaly binary package 
built from this source package. But ruby-gitaly binary package is now 
built from gitaly source package which does not provide 
ruby-gitaly-proto.


This was originally packaged as a dependency of gitlab-shell, which no 
longer need golang-gitaly-proto-dev build dependency.


So we can remove this package. I will file an rm request once the build 
dependency is removed from gitlab-shell in unstable.

Processed: user debian...@lists.debian.org, usertagging 1040205, found 988811 in 2.5.1-2 ..., tagging 1040624 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1040205 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 988811 2.5.1-2
Bug #988811 [libmpdec-doc] libmpdec-doc: broken symlinks: 
/usr/share/doc/libmpdec-doc/libmpdec/_static/*.js
Marked as found in versions mpdecimal/2.5.1-2.
> found 924216 1.7.0-1.1
Bug #924216 [ruby-database-cleaner] ruby-database-cleaner: broken symlinks: 
/usr/share/doc/ruby-database-cleaner/examples/Gemfile{,.lock} -> 
../Gemfile{,.lock}
Marked as found in versions ruby-database-cleaner/1.7.0-1.1.
> usertags 1032894 piuparts
There were no usertags set.
Usertags are now: piuparts.
> retitle 1032894 psad: broken symlink: /usr/share/doc/psad/README -> README.md
Bug #1032894 [psad] psad: Broken symbolic link in documentation
Changed Bug title to 'psad: broken symlink: /usr/share/doc/psad/README -> 
README.md' from 'psad: Broken symbolic link in documentation'.
> found 990655 0.37.0-2
Bug #990655 [python-qpid-proton-doc] python-qpid-proton-doc: roken symlinks: 
/usr/share/doc/python-qpid-proton-doc/html/_static/*.js -> 
../../../../javascript/sphinxdoc/1.0/*.js
Marked as found in versions qpid-proton/0.37.0-2.
> found 990657 4.14.0-4
Bug #990657 [python3-dnf-doc] python3-dnf-doc: broken symlinks: 
/usr/share/doc/python3-dnf-doc/html/_static/{jquery,underscore}.js
Marked as found in versions dnf/4.14.0-4.
> tags 1040624 + sid trixie
Bug #1040624 [src:gcc-10-cross-mipsen] gcc-10-cross-mipsen ftbfs in unstable
Added tag(s) trixie and sid.
> tags 1040257 + sid trixie bookworm
Bug #1040257 [schleuder-cli] schleuder-cli does not work with Ruby >= 3.0.0
Added tag(s) trixie, bookworm, and sid.
> found 1040485 1.20220830+ds-1
Bug #1040485 [raspi-firmware] raspi-firmware breaks kernel upgrade
Marked as found in versions raspi-firmware/1.20220830+ds-1.
> tags 1040485 + sid trixie
Bug #1040485 [raspi-firmware] raspi-firmware breaks kernel upgrade
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032894
1040257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040257
1040485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040485
1040624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040624
924216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924216
988811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988811
990655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990655
990657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1039915: marked as done (ruby-benchmark-memory: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9))

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2023 15:54:24 +0530
with message-id 
and subject line Re: ruby-benchmark-memory: autopkgtest needs update for new 
version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)
has caused the Debian Bug report #1039915,
regarding ruby-benchmark-memory: autopkgtest needs update for new version of 
ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)
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.)


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

Source: ruby-benchmark-memory
Version: 0.1.2-3
Severity: serious
X-Debbugs-CC: ruby-memory-profi...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-memory-profiler

Dear maintainer(s),

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


   passfail
ruby-memory-profiler   from testing1.0.1-2
ruby-benchmark-memory  from testing0.1.2-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of 
ruby-memory-profiler to testing [1]. Of course, ruby-memory-profiler 
shouldn't just break your autopkgtest (or even worse, your package), but 
it seems to me that the change in ruby-memory-profiler 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-memory-profiler 
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-memory-profiler

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-benchmark-memory/34928924/log.gz

 16s  16s 
┌──┐
 16s │ Checking Rubygems dependency resolution on ruby3.1 
│
 16s 
└──┘

 16s  16s GEM_PATH= ruby3.1 -e gem\ \"benchmark-memory\"
 17s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 
'memory_profiler' (~> 0.9) among 101 total gem(s) (Gem::MissingSpecError)
 17s Checked in 
'GEM_PATH=/home/debci/.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' 
at: 
/usr/share/rubygems-integration/all/specifications/benchmark-memory-0.1.2.gemspec, 
execute `gem env` for more information
 17s 	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in 
`block in activate_dependencies'
 17s 	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`each'
 17s 	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`activate_dependencies'
 17s 	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
`activate'
 17s 	from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
 17s 	from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
 17s 	from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem'

 17sfrom -e:1:in `'
 17s /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in 
`to_specs': Could not find 'memory_profiler' (~> 0.9) - did find: 
[memory_profiler-1.0.1] (Gem::MissingSpecVersionError)
 17s Checked in 
'GEM_PATH=/home/debci/.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' 
, execute `gem env` for more information
 17s 	from 

Bug#1039915: ruby-benchmark-memory: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)

[Pirate Praveen]

Control: fixed -1 0.2.0-1

On Thu, 29 Jun 2023 16:01:57 +0200 Paul Gevers  
wrote:

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

> your package needs to update to the new situation.

ruby-benchmark-memory 0.2.0-1 was ready in experimental, but missed a 
reupload to unstable. I'm reuploading it to unstable now.

Processed: Re: ruby-benchmark-memory: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.2.0-1
Bug #1039915 [src:ruby-benchmark-memory] ruby-benchmark-memory: autopkgtest 
needs update for new version of ruby-memory-profiler: Could not find 
'memory_profiler' (~> 0.9)
Marked as fixed in versions ruby-benchmark-memory/0.2.0-1.

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

Bug#1037192: sd: version is lower than in squeeze

[Blair Noctis]

On 2023-07-08 17:31, Andreas Beckmann wrote:
> On Thu, 6 Jul 2023 01:58:50 +0800 Blair Noctis  wrote:
>> On Wed, 07 Jun 2023 14:12:08 +0200 Andreas Beckmann  wrote:
>> > Package: sd
>> > Version: 0.7.6-1
> 
>> > squeeze had a sd binary package built from (unrelated) src:sd at
>> > version 0.74-1 while bookworm has one built from src:rust-sd at
>> > version 0.7.6-1 which is lower, violating the archive property of
>> > monotonically increasing version numbers.
> 
>> TIL about that. Do you think I can use epoch here? Or should I change its 
>> name?
> 
> IMO that is one of the correct uses for an epoch, similar to git which also
> reused an old package name (probably predating the git version control).
> 
> Note that the upload needs to be done as 1:0.7.6-2, i.e. with increment of the
> Debian revision to avoid clashes in the .deb file name (in some cases the 
> epoch
> is not part of the file name for historic reasons).

Thanks, I'll go for that.

> 
>> (Sorry about the late reply, the email didn't reach me.)
> 
> And if you don't Cc the submitter, I don't see your reply ;-)

Ha, I'm sending To both the submitter and bug@bugs.d.o so it will _definitely_
be seen ;)

-- 
Sdrager,
Blair Noctis

Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3

[Simon McVittie]

On Thu, 06 Jul 2023 at 09:50:57 +0100, Simon McVittie wrote:
> On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote:
> > #5  0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0
> > + 0x8a7ce)
> > #6  0x7f134ccee180 e_source_set_display_name
> > (libedataserver-1.2.so.27 + 0x57180)
> 
> Well, this is messed up - something is setting the display name of an
> ESource (a calendar or address book or something similar) to a value that
> is, apparently, so long that allocating memory for its collation key (a
> version that has been modified to sort in the correct locale-sensitive
> order) will fail.

I wonder whether this is the same root cause as #1040452: glibc (>= 2.37-2)
sometimes generating corrupted locale archives? That might explain why
g_utf8_collate_key() would get nonsense results.

Please try with glibc (>= 2.37-5) which fixes that bug, and maybe this
one too.

smcv

Bug#1037192: sd: version is lower than in squeeze

[Andreas Beckmann]

On Thu, 6 Jul 2023 01:58:50 +0800 Blair Noctis  wrote:

On Wed, 07 Jun 2023 14:12:08 +0200 Andreas Beckmann  wrote:
> Package: sd
> Version: 0.7.6-1



> squeeze had a sd binary package built from (unrelated) src:sd at
> version 0.74-1 while bookworm has one built from src:rust-sd at
> version 0.7.6-1 which is lower, violating the archive property of
> monotonically increasing version numbers.



TIL about that. Do you think I can use epoch here? Or should I change its name?


IMO that is one of the correct uses for an epoch, similar to git which 
also reused an old package name (probably predating the git version 
control).


Note that the upload needs to be done as 1:0.7.6-2, i.e. with increment 
of the Debian revision to avoid clashes in the .deb file name (in some 
cases the epoch is not part of the file name for historic reasons).



(Sorry about the late reply, the email didn't reach me.)


And if you don't Cc the submitter, I don't see your reply ;-)

Please try to get this fixed over the next week including a rebuild for 
bookworm s.t. it can be included in the first point release.



Andreas

Bug#1040634: pycoast autopkg tests fail with pillow 10.0.0

[Sebastiaan Couwenberg]

On 7/8/23 09:31, Matthias Klose wrote:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycoast/35498778/log.gz

[...]
101s self = 
101s draw = 
101s position = (8.56126709559166, 4), txt = '50W'
101s font = , align 
= 'CT'
101s kwargs = {'fill': 'white', 'lat_placement': 'lr', 'lon_placement': 
'tb', 'minor_is_tick': True, ...}

101s
101s def _draw_text(self, draw, position, txt, font, align="cc", 
**kwargs):

101s """Draw text with agg module."""
101s >   txt_width, txt_height = draw.textsize(txt, font)
101s E   AttributeError: 'ImageDraw' object has no attribute 'textsize'
101s
101s ../build.wr6/src/pycoast/cw_base.py:170: AttributeError


From the upstream changelog:

 Removed

  ImageDraw.textsize() and
  ImageDraw.multiline_textsize()

 Use instead

  ImageDraw.textbbox(),
  ImageDraw.textlength() and
  ImageDraw.multiline_textbbox()

https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#font-size-and-offset-methods

Kind Regards,

Bas

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

Bug#1040635: python-wordcloud autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:python-wordcloud
Version: 1.8.2.2+dfsg-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-wordcloud/35498779/log.gz

[...]
101s autopkgtest [17:25:06]: test run-unit-test: [---
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-lxc.0c3pi9b6/downtmp/autopkgtest_tmp/foo.py", line 
14, in 

102s wc.generate(text)
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 639, 
in generate

102s return self.generate_from_text(text)
102s^
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 621, 
in generate_from_text

102s self.generate_from_frequencies(words)
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 508, 
in generate_from_frequencies

102s box_size = draw.textsize(word, font=transposed_font)
102s^
102s AttributeError: 'ImageDraw' object has no attribute 'textsize'
103s autopkgtest [17:25:08]: test run-unit-test: ---]

Bug#1040634: pycoast autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:pycoast
Version: 1.6.1+dfsg-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycoast/35498778/log.gz

[...]
101s self = 
101s draw = 
101s position = (8.56126709559166, 4), txt = '50W'
101s font = , align = 'CT'
101s kwargs = {'fill': 'white', 'lat_placement': 'lr', 'lon_placement': 'tb', 
'minor_is_tick': True, ...}

101s
101s def _draw_text(self, draw, position, txt, font, align="cc", **kwargs):
101s """Draw text with agg module."""
101s >   txt_width, txt_height = draw.textsize(txt, font)
101s E   AttributeError: 'ImageDraw' object has no attribute 'textsize'
101s
101s ../build.wr6/src/pycoast/cw_base.py:170: AttributeError
101s === short test summary info 

101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestContourWriterPIL::test_grid_germ
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestContourWriterPIL::test_add_points_coordinate_conversion
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestFromConfig::test_cache
101s FAILED 
../build.wr6/src/pycoast/tests/test_pycoast.py::TestFromConfig::test_caching_with_param_changes
101s === 4 failed, 35 passed, 2 skipped, 16 deselected in 30.31s 

Bug#1040633: pilkit autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:pilkit
Version: 2.0-4
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pilkit/35498777/log.gz

 41s ==
 41s ERROR: Test that the upscale argument works as expected.
 41s --
 41s Traceback (most recent call last):
 41s   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
 41s self.test(*self.arg)
 41s   File 
"/tmp/autopkgtest-lxc.6edwevyp/downtmp/autopkgtest_tmp/tests/test_processors.py", 
line 97, in test_upscale

 41s img2 = P(500, 500, upscale=True).process(img)
 41s^^
 41s   File "/usr/lib/python3/dist-packages/pilkit/processors/resize.py", line 
24, in process

 41s img = img.resize((self.width, self.height), Image.ANTIALIAS)
 41s ^^^
 41s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 41s
 41s --
 41s Ran 26 tests in 0.048s
 41s
 41s FAILED (errors=6)

Bug#1040630: gavodachs autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:gavodachs
Version: 2.8+dfsg-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/35498774/log.gz

107s autopkgtest [17:24:20]: test integration-test: [---
108s Making data it/q#import_t5
108s Shipped 5/5
108s Create index t5_spoint_t5
108s Rows affected: 5
108s Making data it/q#import_t25
108s Shipped 25/30
108s Create index t25_spoint_t25
108s Rows affected: 25
110s EE
110s 2 of 2 bad.  avg 0.01, min 0.01, max 0.01. 178.7/s, par 1.3
110s From it/q:
110sERROR SCS has a valid response
110sERROR TAP query with pgsphere yields plausible result
110s
110s
111s autopkgtest [17:24:24]: test integration-test: ---]
111s integration-test FAIL non-zero exit status 1
111s autopkgtest [17:24:24]: test integration-test:  - - - - - - - - - - results 
- - - - - - - - - -

111s autopkgtest [17:24:24]:  summary
111s integration-test FAIL non-zero exit status 1

Bug#1040632: lazygal autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:lazygal
Version: 0.10.6-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/l/lazygal/35498776/log.gz

 57s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 57s autopkgtest [17:24:04]: test smoke: ---]
 57s smokeFAIL non-zero exit status 1
 57s autopkgtest [17:24:04]: test smoke:  - - - - - - - - - - results - - - - - 
- - - - -
 57s autopkgtest [17:24:04]: test smoke:  - - - - - - - - - - stderr - - - - - 
- - - - -

 57s Traceback (most recent call last):
 57s   File "/usr/bin/lazygal", line 33, in 
 57s sys.exit(load_entry_point('lazygal==0.10.6', 'console_scripts', 
'lazygal')())
 57s 
^^^

 57s   File "/usr/lib/python3/dist-packages/lazygal/cmdline.py", line 292, in 
main
 57s album.generate(progress=progress)
 57s   File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 943, 
in generate

 57s destgal.make()
 57s   File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 667, 
in make

 57s super().make(force)
 57s   File "/usr/lib/python3/dist-packages/lazygal/make.py", line 123, in make
 57s d.make()  # dependency building not forced
 57s 
 57s   File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 250, 
in make

 57s super().make()
 57s   File "/usr/lib/python3/dist-packages/lazygal/make.py", line 123, in make
 57s d.make()  # dependency building not forced
 57s 
 57s   File "/usr/lib/python3/dist-packages/lazygal/make.py", line 124, in make
 57s self.call_build()
 57s   File "/usr/lib/python3/dist-packages/lazygal/make.py", line 133, in 
call_build

 57s self.build()
 57s   File "/usr/lib/python3/dist-packages/lazygal/genmedia.py", line 71, in 
build
 57s self.do_build()
 57s   File "/usr/lib/python3/dist-packages/lazygal/genmedia.py", line 211, in 
do_build

 57s im = self.resize(self.get_image())
 57s  ^
 57s   File "/usr/lib/python3/dist-packages/lazygal/genmedia.py", line 162, in 
resize

 57s im = im.resize(self.unrotated_size, PILImage.ANTIALIAS)
 57s ^^
 57s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'

Bug#1040631: imgp autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:imgp
Version: 2.8-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/i/imgp/35498775/log.gz

 27s autopkgtest [17:23:03]: test test: [---
 27s Traceback (most recent call last):
 27s   File "/usr/bin/imgp", line 54, in 
 27s png_ip = PIL.Image.ANTIALIAS  # default interpolation for PNG
 27s  ^^^
 27s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 28s autopkgtest [17:23:04]: test test: ---]

Bug#1040629: fdroidserver autopkg tests fail

[Matthias Klose]

Package: src:fdroidserver
Version: 2.2.1-1
Severity: serious
Tags: sid trixie

seen, when triggered by pillow 10.0.0, although I don't see how this is related 
to pillow:


https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/35498773/log.gz

[...]
185s
185s sent 413 bytes  received 199 bytes  1,224.00 bytes/sec
185s total size is 263  speedup is 0.43
185s sending incremental file list
185s created directory 
/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/.testfiles/test_gitlab_ci_27et6ow31688750714.0798733/fdroid/git-mirror/fdroid/stats

185s ./
185s known_apks.txt
185s
185s sent 207 bytes  received 196 bytes  806.00 bytes/sec
185s total size is 73  speedup is 0.18
185s 
.ERROR:root:/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/.testfiles/test_main_empty_dot_android_7j0unv181688750725.1382802/home/.android/debug.keystore 
does not exist!  Create it by running:
185s keytool -genkey -v -keystore 
/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/.testfiles/test_main_empty_dot_android_7j0unv181688750725.1382802/home/.android/debug.keystore 
-storepass android \
185s  -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 
-validity 1 \

185s  -dname "CN=Android Debug,O=Android,C=US"
185s .Importing keystore 
/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/.testfiles/test_main_empty_dot_ssh_2vw_pu0j1688750725.1395078/home/.android/debug.keystore 
to /tmp/.7smgnil0/.keystore.p12...

185s
185s Warning:
185s  uses the SHA1withRSA signature algorithm which is 
considered a security risk. This algorithm will be disabled in a future update.

185s writing RSA key
186s .Importing keystore 
/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/.testfiles/test_main_on_user_machine_5ftzm0191688750725.8284636/home/.android/debug.keystore 
to /tmp/.km112q4u/.keystore.p12...

186s
186s Warning:
186s  uses the SHA1withRSA signature algorithm which is 
considered a security risk. This algorithm will be disabled in a future update.

186s writing RSA key
187s ..Importing keystore 
/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/tests/aosp_testkey_debug.keystore 
to /tmp/.kt4fn4c9/.keystore.p12...

187s
187s Warning:
187s  uses the SHA1withRSA signature algorithm which is 
considered a security risk. This algorithm will be disabled in a future update.

187s writing RSA key
187s .
187s ==
187s FAIL: test_get_repo_base_url (__main__.NightlyTest.test_get_repo_base_url)
187s --
187s Traceback (most recent call last):
187s   File 
"/tmp/autopkgtest-lxc.1h987dr1/downtmp/build.ia0/src/tests/nightly.TestCase", 
line 105, in test_get_repo_base_url

187s self.assertTrue(r.status_code in (200, 403), 'should not be a 
redirect')
187s AssertionError: False is not true : should not be a redirect
187s
187s --
187s Ran 9 tests in 24.624s
187s
187s FAILED (failures=1)

Bug#1040628: dnstwist autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:dnstwist
Version: 0~20221213-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dnstwist/35498772/log.gz

 61s autopkgtest [17:23:09]: test testdebiandomain: [---
 65s Traceback (most recent call last):
 65s   File "/usr/bin/dnstwist", line 33, in 
 65s sys.exit(load_entry_point('dnstwist==20221213', 'console_scripts', 
'dnstwist')())
 65s 
^^^

 65s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 933, in wrapper
 65s result = func(*args, **kwargs)
 65s  ^
 65s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 1190, in run
 65s phash = pHash(BytesIO(screenshot))
 65s ^^
 65s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 298, in __init__
 65s img = Image.open(image).convert('L').resize((hsize, hsize), 
Image.ANTIALIAS)
 65s 
^^^

 65s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 65s dnstwist execution failed
 66s autopkgtest [17:23:14]: test testdebiandomain: ---]
 66s testdebiandomain FAIL non-zero exit status 1
 66s autopkgtest [17:23:14]: test testdebiandomain:  - - - - - - - - - - 
results - - - - - - - - - -
 66s autopkgtest [17:23:14]: test testdebiandomain:  - - - - - - - - - - stderr 
- - - - - - - - - -

 66s Traceback (most recent call last):
 66s   File "/usr/bin/dnstwist", line 33, in 
 66s sys.exit(load_entry_point('dnstwist==20221213', 'console_scripts', 
'dnstwist')())
 66s 
^^^

 66s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 933, in wrapper
 66s result = func(*args, **kwargs)
 66s  ^
 66s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 1190, in run
 66s phash = pHash(BytesIO(screenshot))
 66s ^^
 66s   File "/usr/lib/python3/dist-packages/dnstwist.py", line 298, in __init__
 66s img = Image.open(image).convert('L').resize((hsize, hsize), 
Image.ANTIALIAS)
 66s 
^^^

 66s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 66s dnstwist execution failed

Bug#1040627: django-simple-captcha autopkg tests fail with pillow 10.0.0

[Matthias Klose]

Package: src:django-simple-captcha
Version: 0.5.17-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-simple-captcha/35498771/log.gz

ImageFont.getsize was deprecated in 9.2.0

 32s ==
 32s ERROR: test_transparent_background 
(captcha.tests.tests.CaptchaCase.test_transparent_background)

 32s --
 32s Traceback (most recent call last):
 32s   File "/usr/lib/python3/dist-packages/captcha/tests/tests.py", line 459, 
in test_transparent_background

 32s response = self.client.get(reverse("captcha-image", 
kwargs=dict(key=key)))
 32s
^^^
 32s   File "/usr/lib/python3/dist-packages/django/test/client.py", line 742, 
in get

 32s response = super().get(path, data=data, secure=secure, **extra)
 32s
 32s   File "/usr/lib/python3/dist-packages/django/test/client.py", line 396, 
in get

 32s return self.generic('GET', path, secure=secure, **{
 32s
 32s   File "/usr/lib/python3/dist-packages/django/test/client.py", line 473, 
in generic

 32s return self.request(**r)
 32s^
 32s   File "/usr/lib/python3/dist-packages/django/test/client.py", line 719, 
in request

 32s self.check_exception(response)
 32s   File "/usr/lib/python3/dist-packages/django/test/client.py", line 580, 
in check_exception

 32s raise exc_value
 32s   File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", 
line 47, in inner

 32s response = get_response(request)
 32s^
 32s   File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 
181, in _get_response

 32s response = wrapped_callback(request, *callback_args, **callback_kwargs)
 32s
 32s   File "/usr/lib/python3/dist-packages/captcha/views.py", line 88, in 
captcha_image

 32s charimage = Image.new("L", getsize(font, " %s " % char), "#00")
 32s
 32s   File "/usr/lib/python3/dist-packages/captcha/views.py", line 33, in 
getsize
 32s return font.getsize(text)
 32s
 32s AttributeError: 'FreeTypeFont' object has no attribute 'getsize'
 32s
 32s --
 32s Ran 33 tests in 0.266s
 32s
 32s FAILED (errors=6, skipped=1)

Bug#1040626: gcc-13-cross-mipsen ftbfs in unstable

[Matthias Klose]

Package: src:gcc-13-cross-mipsen
Version: 1+c1
Severity: serious
Tags: sid trixie

[...]
checking linker soname option... yes
checking linker --demangle support... no
checking linker plugin support... 0
checking assembler for explicit relocation support... no
checking assembler for -mno-shared support... no
checking assembler for .gnu_attribute support... no
checking assembler for .module support... no
configure: error: Requesting --with-fp-32= requires assembler support for 
.module.
make[4]: *** [Makefile:4569: configure-gcc] Error 1
make[4]: Leaving directory '/<>/gcc/build'
make[3]: *** [Makefile:1042: all] Error 2
make[3]: Leaving directory '/<>/gcc/build'

Bug#1040624: gcc-10-cross-mipsen ftbfs in unstable

[Matthias Klose]

Package: src:gcc-10-cross-mipsen
Version: 3+c5
Severity: serious

[...]
checking linker soname option... yes
checking linker --demangle support... no
checking linker plugin support... 0
checking assembler for explicit relocation support... no
checking assembler for -mno-shared support... no
checking assembler for .gnu_attribute support... no
checking assembler for .module support... no
configure: error: Requesting --with-fp-32= requires assembler support for 
.module.
make[4]: *** [Makefile:4401: configure-gcc] Error 1
make[4]: Leaving directory 
'/home/packages/cross/10/m/gcc-10-cross-mipsen-3+c5/gcc/build'

make[3]: *** [Makefile:990: all] Error 2