Processed: Re: Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1024493 [src:bs1770gain] Proposed-RM: bs1770gain -- RoQA; inappropriate 
content
Severity set to 'wishlist' from 'serious'

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

Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content

[Petter Reinholdtsen]

Control: severity -1 wishlist

It is clear that there is no concensus on this issue.  It is not a
technical problem with the code, but a question of opinions.  Because of
this, I set severity to wishlist.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1025310: marked as done (libsamplerate: FTBFS with fftw3 (3.3.10-1))

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2022 06:49:17 +
with message-id 
and subject line Bug#1025310: fixed in libsamplerate 0.2.2-3
has caused the Debian Bug report #1025310,
regarding libsamplerate: FTBFS with fftw3 (3.3.10-1)
to be marked as done.

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

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


-- 
1025310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsamplerate
Version: 0.2.2-2
Severity: serious
Tags: ftbfs patch

Dear Maintainer,

Your package FTBFS with fftw3 (3.3.10-1) because it not longer provides 
fftw3-dev.

The attached patch resolves the issue by changing the dependency to 
libfftw3-dev.

Kind Regards,

Bas
diff -Nru libsamplerate-0.2.2/debian/changelog 
libsamplerate-0.2.2/debian/changelog
--- libsamplerate-0.2.2/debian/changelog2022-09-29 10:23:59.0 
+0200
+++ libsamplerate-0.2.2/debian/changelog2022-12-02 13:03:36.0 
+0100
@@ -1,3 +1,10 @@
+libsamplerate (0.2.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libfftw3-dev, fftw3-dev no longer provided.
+
+ -- Bas Couwenberg   Fri, 02 Dec 2022 13:03:36 +0100
+
 libsamplerate (0.2.2-2) unstable; urgency=medium
 
   [ Jenkins ]
diff -Nru libsamplerate-0.2.2/debian/control libsamplerate-0.2.2/debian/control
--- libsamplerate-0.2.2/debian/control  2022-09-29 10:23:59.0 +0200
+++ libsamplerate-0.2.2/debian/control  2022-12-02 13:03:34.0 +0100
@@ -6,7 +6,7 @@
  IOhannes m zmölnig (Debian/GNU) ,
 Build-Depends:
  debhelper-compat (= 13),
- fftw3-dev,
+ libfftw3-dev,
  libsndfile1-dev,
  pkg-config,
 Standards-Version: 4.6.1
--- End Message ---
--- Begin Message ---
Source: libsamplerate
Source-Version: 0.2.2-3
Done: Dennis Braun 

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

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

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

Debian distribution maintenance software
pp.
Dennis Braun  (supplier of updated libsamplerate 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, 03 Dec 2022 22:47:47 +0100
Source: libsamplerate
Architecture: source
Version: 0.2.2-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 1025310
Changes:
 libsamplerate (0.2.2-3) unstable; urgency=high
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
 .
   [ Dennis Braun ]
   * Fix FTBFS with fftw3. Thanks to Bas Couwenberg (Closes: #1025310)
   * Do not install extra license file
Checksums-Sha1:
 e4470dd421a64f034abdb6271c7189fb24a6b521 2206 libsamplerate_0.2.2-3.dsc
 dfae07d470634cd7b2e49f0fdc383bab419e03b0 7504 
libsamplerate_0.2.2-3.debian.tar.xz
 06b417b93d99b01498ae05f9f9acb1e59dbbd4e6 6201 
libsamplerate_0.2.2-3_source.buildinfo
Checksums-Sha256:
 364aee9f8033c795cecbb3cbc1659f795487f535d3523bc4ec6f3790ba66c74f 2206 
libsamplerate_0.2.2-3.dsc
 000ad52f38082f5a954595de96ee54c09d7af2995df28b03fe54183302ecfcb8 7504 
libsamplerate_0.2.2-3.debian.tar.xz
 4034d3e0b7337eaf504872a5b687601c20b036e547f466b674bbea8e9cb50737 6201 
libsamplerate_0.2.2-3_source.buildinfo
Files:
 0442f730614da5afa33088d578a8ecbe 2206 sound optional libsamplerate_0.2.2-3.dsc
 9eb5dad5c520cc86f702a93e53bd2953 7504 sound optional 
libsamplerate_0.2.2-3.debian.tar.xz
 e4d7e3188901e03994c1401e6699beff 6201 sound optional 
libsamplerate_0.2.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmOMPUgPHHNuZEBkZWJp
YW4ub3JnAAoJEGNOpV2QK5g2Km4P/1MGRWQcN/tuVxd4Naw0JE7U6Golx7QbVwee
r35UmV6YZiR4DAePdL6Zzdg13ff9A0Lb56T6zbPDXfVIcbM5692K9HSxQpz8WLBJ
MebeN/Ryoss4ZXD9DR4m5cF8EJweYt5GXCFTJxntHq0oh/LHFXey98Ut4P3Jm2+x
CzXgAnFqMjkGwBxZ93Tq20BApi0YSXbLoCOM4zzcGcr4+pDNeHoxvXUwRN4HyFGT
FIPtp6JGfEgo+0N0s/fwUY7sH8stE67+fN1CQpDjP1ILZqesL12aqIbPkWluCt4k
GjEb/hVEKmwCFF0+gjn1UAwR+9kdOCzJBE58mf8CNd4rUl4zmfO8bqCOm98hKCBl
+6m6oRJhwXkcReFvvRe5Sqp0xa+TUpzb9WgtJEf32EJ3Kzqn9dEmWR7nHj803jkU
Ey4oD+HTnkx2EefrNUTP4mbEx1jUc22

Bug#1022469: python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Stuart Prescott]

Hi Michael


On 04/12/2022 03:50, Michael Banck wrote:
[...]

Looks like they got a work-around here in (since closed) PR #1401:
https://github.com/hgrecco/pint/commit/eb4e13428a3ede09148b76c71bc5b8cddb169176.patch


I was somewhat concerned that upstream abandoned that work rather than 
merging it. I have a feeling all it does is fix the test failure without 
actually fixing the underlying problems.



If I stick this (also attached) patch in, the testsuite passes fine.


I don't think it's enough for users of pint like superqt, however. The 
superqt test suite's failures seem to need a newer pin to pick up other 
compatibility changes with babel.


 8<  8< 

_ ERROR collecting 
.pybuild/cpython3_3.11_superqt/build/tests/test_quantity.py _

/usr/lib/python3/dist-packages/pint/registry.py:575: in load_definitions
rbytes = importlib.resources.read_binary(__package__, file)
/usr/lib/python3.11/importlib/resources/_legacy.py:18: in wrapper
warnings.warn(
E   DeprecationWarning: read_binary is deprecated. Use files() instead. 
Refer to https://importlib-resource
s.readthedocs.io/en/latest/using.html#migrating-from-legacy for 
migration advice.


During handling of the above exception, another exception occurred:
tests/test_quantity.py:3: in 
from superqt import QQuantity
:1231: in _handle_fromlist
???
superqt/__init__.py:51: in __getattr__
from .spinbox._quantity import QQuantity
superqt/spinbox/_quantity.py:21: in 
UREG = UnitRegistry()
/usr/lib/python3/dist-packages/pint/registry.py:143: in __call__
obj._after_init()
/usr/lib/python3/dist-packages/pint/registry.py:1976: in _after_init
super()._after_init()
/usr/lib/python3/dist-packages/pint/registry.py:305: in _after_init
self.load_definitions("default_en.txt", True)
/usr/lib/python3/dist-packages/pint/registry.py:588: in load_definitions
raise ValueError("While opening {}\n{}".format(file, msg))
E   ValueError: While opening default_en.txt
E   read_binary is deprecated. Use files() instead. Refer to 
https://importlib-resources.readthedocs.io/en/

latest/using.html#migrating-from-legacy for migration advice.

 8<  8< 

cheers
Stuart

--
Stuart Prescott   http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer  http://www.debian.org/   stu...@debian.org
GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#1025213:

[wh]

I was able to build a copy of the libgl1-mesa-dri with the Gallium i915
driver enabled, and that fixed the flickering problem on my netbook from
that era.

Here's a copy if anyone would like to try
https://github.com/wh0/debian-mesa-i915g/releases/tag/22.3.0-1-1

I saw that Fedora had enabled it too:
https://bugzilla.redhat.com/show_bug.cgi?id=2100212

Processed: Re: [Pkg-zfsonlinux-devel] Bug#1024326: bullseye to bookworm upgrade failure: Could not locate dkms.conf file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1024326 [zfs-dkms] bullseye to bookworm upgrade failure: Could not locate 
dkms.conf file
Severity set to 'important' from 'serious'
> tags -1 +moreinfo
Bug #1024326 [zfs-dkms] bullseye to bookworm upgrade failure: Could not locate 
dkms.conf file
Added tag(s) moreinfo.

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

Bug#1024326: [Pkg-zfsonlinux-devel] Bug#1024326: bullseye to bookworm upgrade failure: Could not locate dkms.conf file

[M. Zhou]

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

I'm still not sure about why the upgrade failed, and I could not
reproduce the problem in a clean chroot using the following script:

https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/tests/sbuild-shell-bullseye-to-bookworm.sh

So I'm downgrading the bug's severity to unblock migration.

On Thu, 2022-11-17 at 10:31 -0500, Antoine Beaupre wrote:
> Package: zfs-dkms
> Version: 2.1.6-3
> Severity: serious
> 
> I have tried to upgrade to bookworm today and kernel builds fail on
> zfs-dkms. It fails with:
> 
> dkms: running auto installation service for kernel 6.0.0-4-
> amd64:Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/zfs/2.0.3/source/dkms.conf does not exist.
> 
> It's odd because zfs 2.0.3 is gone now... The package has been
> upgraded at this point... Yet the /var/lib/dkms/zfs/2.0.3 directory
> was still around. Removing it fixes the problem:
> 
>     rm -rf /var/lib/dkms/zfs/2.0.3
> 
> Note that I am doing batch upgrades with a special procedure, with
> this command:
> 
>     env DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none
> APT_LISTBUGS_FRONTEND=none UCF_FORCE_CONFFOLD=y \
>     apt full-upgrade -y -o Dpkg::Options::='--force-confdef' -o
> Dpkg::Options::='--force-confold' &&
> 
> ... which might have cause the old directory to not be removed.
> 
> See this for my upgrade procedure:
> 
> https://anarc.at/services/upgrades/bookworm/
> 
> More of the error log:
> 
> Setting up linux-image-6.0.0-4-amd64 (6.0.8-1) ...
> /etc/kernel/postinst.d/dkms:
> dkms: running auto installation service for kernel 6.0.0-4-
> amd64:Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/zfs/2.0.3/source/dkms.conf does not exist.
>  failed!
> run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
> dpkg: error processing package linux-image-6.0.0-4-amd64 (--
> configure):
>  installed linux-image-6.0.0-4-amd64 package post-installation script
> subprocess returned error exit status 1
> dpkg: dependency problems prevent configuration of linux-image-amd64:
>  linux-image-amd64 depends on linux-image-6.0.0-4-amd64 (= 6.0.8-1);
> however:
>   Package linux-image-6.0.0-4-amd64 is not configured yet.
> 
> dpkg: error processing package linux-image-amd64 (--configure):
>  dependency problems - leaving unconfigured
> Setting up linux-headers-6.0.0-4-amd64 (6.0.8-1) ...
> /etc/kernel/header_postinst.d/dkms:
> dkms: running auto installation service for kernel 6.0.0-4-
> amd64:Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/zfs/2.0.3/source/dkms.conf does not exist.
>  failed!
> run-parts: /etc/kernel/header_postinst.d/dkms exited with return code
> 4
> Failed to process /etc/kernel/header_postinst.d at
> /var/lib/dpkg/info/linux-headers-6.0.0-4-amd64.postinst line 11.
> dpkg: error processing package linux-headers-6.0.0-4-amd64 (--
> configure):
>  installed linux-headers-6.0.0-4-amd64 package post-installation
> script subprocess returned error exit status 1
> dpkg: dependency problems prevent configuration of linux-headers-
> amd64:
>  linux-headers-amd64 depends on linux-headers-6.0.0-4-amd64 (= 6.0.8-
> 1); however:
>   Package linux-headers-6.0.0-4-amd64 is not configured yet.
> 
> dpkg: error processing package linux-headers-amd64 (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  linux-image-6.0.0-4-amd64
>  linux-image-amd64
>  linux-headers-6.0.0-4-amd64
>  linux-headers-amd64

Bug#1025025: marked as done (ImportError: cannot import name 'Application' from 'cleo')

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2022 01:34:56 +
with message-id 
and subject line Bug#1025025: fixed in poetry 1.2.2+dfsg-1
has caused the Debian Bug report #1025025,
regarding ImportError: cannot import name 'Application' from 'cleo'
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.)


-- 
1025025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-poetry
Version: 1.1.14+dfsg-1
Severity: serious
X-Debbugs-Cc: deb...@microjoe.org

Dear Maintainer,

When invoking poetry locally, I get the following error:

Traceback (most recent call last):
  File "/usr/bin/poetry", line 5, in 
from poetry.console import main
  File "/usr/lib/python3/dist-packages/poetry/console/__init__.py", line 1, 
in 
from .application import Application
  File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 
3, in 
from cleo import Application as BaseApplication
ImportError: cannot import name 'Application' from 'cleo' 
(/usr/lib/python3/dist-packages/cleo/__init__.py)

Indeed, the installed python3-cleo package does not seem to have the
'Application' item directly available into its namespace:

Python 3.10.8 (main, Nov  4 2022, 09:21:25) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cleo
>>> dir(cleo)
['__builtins__', '__cached__', '__doc__', '__file__', '__loader__',
'__name__', '__package__', '__path__', '__spec__', '__version__',
'annotations']
>>>

The latest upstream poetry source code [1] seems to correctly use the
`cleo.application` namespace.

[1] 
https://github.com/python-poetry/poetry/blob/master/src/poetry/console/application.py

Thanks,

Agathe.

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

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

Versions of packages python3-poetry depends on:
ii  python3 3.10.6-3
ii  python3-cachecontrol0.12.12-2
ii  python3-cachy   0.3.0-4
ii  python3-cleo1.0.0a5-1
ii  python3-clikit  0.6.2-3
ii  python3-html5lib1.1-3
ii  python3-importlib-metadata  4.12.0-1
ii  python3-lockfile1:0.12.2-2.2
ii  python3-packaging   21.3-1.1
ii  python3-pexpect 4.8.0-3
ii  python3-pkginfo 1.8.2-1
ii  python3-poetry-core 1.3.2-1
ii  python3-requests2.28.1+dfsg-1
ii  python3-requests-toolbelt   0.9.1-3
ii  python3-shellingham 1.5.0-1
ii  python3-tomlkit 0.11.6-1
ii  python3-virtualenv  20.16.6+ds-1

python3-poetry recommends no packages.

python3-poetry suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: poetry
Source-Version: 1.2.2+dfsg-1
Done: Emmanuel Arias 

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Arias  (supplier of updated poetry package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Nov 2022 10:32:39 -0300
Source: poetry
Architecture: source
Version: 1.2.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emmanuel Arias 
Closes: 1023612 1025025
Changes:
 poetry (1.2.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #1023612, #1025025).
   * d/control: Add new packages as Build Depends: python3-deepdiff,
 python3-dulwich, python3-pip, python3-pytest-xdist, python3-venv,
 python3.11-venv.
   * d/rules: Skip tests, they need more work before active them:
 test_package_partial_yank, test_run_installs_with_same_vers

Processed: severity

[Debian Bug Tracking System]

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

> severity 951902 normal
Bug #951902 [src:duktape] duktape: python2 is required to regenerate some 
source files
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#972230: marked as done (CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 CVE-2019-16255 CVE-2020-25613)

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2022 19:06:07 -0500
with message-id <1c01cf43-fb13-94b1-8644-4ad55b0d4...@riseup.net>
and subject line Re: CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 
CVE-2019-16255 CVE-2020-25613
has caused the Debian Bug report #972230,
regarding CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 CVE-2019-16255 
CVE-2020-25613
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.)


-- 
972230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jruby
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

jruby bundles various modules from the Ruby stdlib, which have been affected by
security issues:

CVE-2017-17742:
https://www.ruby-lang.org/en/news/2018/03/28/http-response-splitting-in-webrick-cve-2017-17742/
https://github.com/ruby/ruby/commit/d9d4a28f1cdd05a0e8dabb36d747d40bbcc30f16

CVE-2019-16201
https://github.com/ruby/ruby/commit/36e057e26ef2104bc2349799d6c52d22bb1c7d03
https://hackerone.com/reports/661722
https://www.ruby-lang.org/en/news/2019/10/01/webrick-regexp-digestauth-dos-cve-2019-16201/

CVE-2019-16254
https://github.com/ruby/ruby/commit/3ce238b5f9795581eb84114dcfbdf4aa086bfecc
https://hackerone.com/reports/331984
https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254/

CVE-2019-16255
https://www.ruby-lang.org/en/news/2019/10/01/code-injection-shell-test-cve-2019-16255/
https://github.com/ruby/ruby/commit/3af01ae1101e0b8815ae5a106be64b0e82a58640

CVE-2020-25613
https://www.ruby-lang.org/en/news/2020/09/29/http-request-smuggling-cve-2020-25613/
https://github.com/ruby/webrick/commit/8946bb38b4d87549f0d99ed73c62c41933f97cc7


The root cause for all of this is #926280

Cheers,
Moritz

--- End Message ---
--- Begin Message ---

Hello,

These CVE IDs are been fixed with the upload of jruby 9.3.9.0+ds-1 in 
Debian:


CVE-2017-17742
CVE-2019-16201
CVE-2019-16254
CVE-2019-16255
CVE-2020-25613

These were marked as fixed in a previous changelog entry but I 
mistakenly made the upload without including it.


Thanks,

-- Jerome--- End Message ---

Processed: fixed 972230 in 9.3.9.0+ds-1

[Debian Bug Tracking System]

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

> fixed 972230 9.3.9.0+ds-1
Bug #972230 [jruby] CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 CVE-2019-16255 
CVE-2020-25613
Marked as fixed in versions jruby/9.3.9.0+ds-1.
> thanks
Stopping processing here.

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

Bug#977979: marked as done (jruby fails to run without declaring the DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable)

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2022 18:59:29 -0500
with message-id <13a56f02-e0fc-39e2-9d7b-353cc02e2...@riseup.net>
and subject line Re: jruby fails to run without declaring the 
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable
has caused the Debian Bug report #977979,
regarding jruby fails to run without declaring the 
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable
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.)


-- 
977979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jruby
Version: 9.1.17.0-3
Severity: grave

Dear maintainers,

It seems jruby fails to run without declaring the
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable:

jruby -e "puts 'Hello World'"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by jnr.posix.JavaLibCHelper$ReflectiveAccess 
to method sun.nio.ch.SelChImpl.getFD()
WARNING: Please consider reporting this to the maintainers of 
jnr.posix.JavaLibCHelper$ReflectiveAccess
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
NameError: undefined method `default_specifications_dir' for class 
`#'
  singleton class at 
/usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:84
at 
/usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:58
  require at org/jruby/RubyKernel.java:956
at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1
  require at org/jruby/RubyKernel.java:956
at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1347
 load at org/jruby/RubyKernel.java:974
at uri:classloader:/jruby/kernel/gem_prelude.rb:1

Any value for DEBIAN_DISABLE_RUBYGEMS_INTEGRATION makes it work again:

DEBIAN_DISABLE_RUBYGEMS_INTEGRATION=hamburger jruby -e "puts 'Hello World'"
Hello World

Talking with Antonio Terceiro, it seems the underlying problem comes
from the current jruby version in Debian bundling an old version of
rubygems, that isn't compatible with the code in
/usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb.

Setting DEBIAN_DISABLE_RUBYGEMS_INTEGRATION seems like a cheap
trick, as ruby gems in debian are 2.7 compatible, and our
jruby is 2.3 compatible.

Really, jruby shouldn't load gems from /usr/lib/ruby/vendor_ruby
(but I'll open another bug about this).

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄





OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
This bug is now fixed with of upload of jruby_9.3.9.0+ds-1. The new 
version of jruby in Debian does not attempt to load any ruby code from 
the shared system libraries/gems.


Thanks,

-- Jerome--- End Message ---

Processed: fixed 976477 in 9.3.9.0+ds-1

[Debian Bug Tracking System]

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

> fixed 976477 9.3.9.0+ds-1
Bug #976477 {Done: Jérôme Charaoui } [src:jruby] jruby: 
FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or 
directory
Marked as fixed in versions jruby/9.3.9.0+ds-1.
> thanks
Stopping processing here.

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

Processed: Re: duktape: python2 is required to regenerate some source files

[Debian Bug Tracking System]

Processing control commands:

> unblock 937695 by -1
Bug #937695 [src:python-defaults] python-defaults: Python2 removal in 
sid/bookworm
937695 was blocked by: 936661 937331 936845 943133 938528 883161 943268 936483 
943064 937021 937318 943070 937675 938295 932542 936939 938654 937246 943016 
936720 938212 966785 935767 936704 938604 936537 937181 936946 942112 942994 
936444 945735 942944 937038 936996 942999 936449 965288 938748 937682 937234 
936812 938518 938458 942987 936934 943007 936759 943241 937011 936385 937328 
936776 937296 938663 938676 936709 943057 938408 936767 943140 938610 943026 
936710 938222 943003 942983 943069 936895 936162 966772 943027 937293 938666 
936433 936729 938428 937230 943183 936993 942940 936997 966762 936172 936437 
943079 942986 966735 937891 937118 943006 936599 943056 938252 936714 938614 
936544 938677 937297 936777 943144 937665 943194 943017 937247 936335 943060 
937051 937001 937841 938581 938418 936984 938431 938558 936852 936362 943136 
936536 937088 938771 936802 936440 942990 936943 936185 938600 936700 942933 
937243 938650 936724 937617 936887 938294 937660 938178 938098 938249 938236 
936844 943032 967200 936899 936208 936146 966743 942912 966747 942995 936445 
945734 937568 938605 936180 966784 938061 936883 938655 947301 937627 966789 
937262 936935 945746 938391 938283 935208 942945 936962 936495 966797 945678 
937711 937541 936196 939260 966793 936343 936894 943102 938299 938808 937679 
966730 937606 938244 938858 937738 945668 936972 937931 945743 938692 936189 
936792 937491 937657 938141 938615 943122 936522 938828 943145 938378 936833 
936339 945747 937468 966734 936890 946929 936346 966796 966746 936228 938233 
936840 936985 938168 938290 937670 966739 943195 936595 937664 943302 943075 
936725 938625 943112 938818 937788 936742 938642 937616 936886 937441 966780 
937701 937578 886617 938237 936147 937751 938831 943142 938008 938848 938220 
936712 943125 938612 937588 936525 937411 947294 938204 937998 945727 938058 
938081 936876 936863 936298 936809 937501 937778 936326 937639 937551 936859 
936303 966764 936261 936307 936975 936113 942955 936867 936810 937680 945723 
953219 938695 937275 945706 937961 938645 936745 938301 943115 938622 938210 
937421 945717 938861 938351 938388 936316 936455 936127 966757 936804 966753 
936123 936370 966769 936854 937634 936179 936820 947299 936982 945713 938259 
939181 937696 938276 938263 943192 938209 938111 942992 936442 966727 937511 
936819 936425 937488 936313 936107 936702 938871 937538 937451 936752 937697 
938277 943062 938273 945688 938229 945716 936169 936850 936317 966779 945651 
943035 936103 936126 936153 942915 966756 936800 936170 936829 937521 936164 
937768 936323 936873 936866 938311 943105 936505 953220 938224 945707 937643 
937647 937971 937265 936932 945726 938219 938101 936814 937684 937232 936877 
942925 942942 936271 938188 937791 936467 936913 966732 943100 937213 943043 
936524 943124 938921 936550 937161 937217 943047 912491 937260 938694 937274 
936794 943201 943119 938781 937811 936681 937198 938649 936749 938448 937078 
939478 936736 936658 938758 936459 937838 943288 936974 936608 938708 942954 
936917 936463 936454 942976 942963 936420 942909 936923 936956 936787 942959 
936979 936799 938699 938498 937148 937256 936577 936744 938644 936514 943114 
943173 936332 943166 936573 936566 938461 936529 936783 938683 937635 936855 
936805 936927 942910 943167 937398 938640 937253 936740 937203 966782 937269 
936969 936400 942929 936926 945732 942966 936450 942973 936424 942914 936957 
932197 942977 936825 937888 938718 936786 943034 936842 938686 937361 936559 
937851 943159 936631 938731 937041 938471 943096 936509 937672 937257 943163 
943176 936520 937171 943120 937091 943046 936132 943104 938598 936892 936737 
935450 938637 936916 939491 943039 936477 936165 966775 942950 936473 942924 
936815 936628 936733 937068 937264 936790 938690 937270 936912 938239 939111 
936149 939259 938181 936340 966733 937654 936834 943042 938108 937212 937620 
938675 937295 936775 945744 966737 938280 936585 936995 936462 938331 945736 
936945 942962 945658 946927 942935 966786 936183 937667 937245 936337 936880 
937610 937222 938011 938328 937663 936572 937609 937408 943172 937458 936839 
936187 937748 938234 938682 937252 937614 936884 937677 937941 966783 937202 
936847 936902 938131 936241 942972 945733 938289 936952 938381 938230 943135 
936535 936843 938308 936485 937428 936336 936562 937673 938358 937666 938293 
938243 936830 966736 943005 937968 937600 936268 936344 966749 936893 966794 
936190 937771 937508 936472 938632 937431 937558 936897 938001 938841 936889 
945740 937619 937581 937418 938665 936765 938051 937061 943024 938613 943050 
936543 943143 937605 943000 942980 936862 938568 938591 936994 936496 936949 
937236 936584 947501 943184 945745 936434 936936 937249 938617 942939 936717 
936774 938674 938660 936760 943014 937244 943197 936756 938623 938656 936723 
938738 966800 936638 938

Bug#951902: duktape: python2 is required to regenerate some source files

[Bastian Germann]

Control: unblock 937695 by -1

On Sat, 22 Feb 2020 13:19:04 -0700 Sean Whitton  
wrote:

Thus, I believe that conversion of these scripts to python3 blocks
python2 removal in Debian.  I'm attempting to file this bug with the
right metadata; please excuse me if I didn't get it right, as I'm not
really involved in the python2 removal efforts.


I do not think that python2 removal should be blocked by a package that has never depended on it but would have to do 
that to conform with the Policy. Upstream has partly converted the scripts to python3 and apparently some of them to nodejs.

Processed: fixed 977979 in 9.3.9.0+ds-1

[Debian Bug Tracking System]

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

> fixed 977979 9.3.9.0+ds-1
Bug #977979 [jruby] jruby fails to run without declaring the 
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable
Marked as fixed in versions jruby/9.3.9.0+ds-1.
> thanks
Stopping processing here.

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

Processed: closing 959600

[Debian Bug Tracking System]

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

> close 959600
Bug #959600 [src:jruby] jruby: FTBFS:  [exec] Failure/Error: return 
gem_original_require(path)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: fixed 959600 in 9.3.9.0+ds-1

[Debian Bug Tracking System]

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

> fixed 959600 9.3.9.0+ds-1
Bug #959600 [src:jruby] jruby: FTBFS:  [exec] Failure/Error: return 
gem_original_require(path)
Marked as fixed in versions jruby/9.3.9.0+ds-1.
> thanks
Stopping processing here.

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

Bug#938322: fixed in qtwebengine-opensource-src 5.15.11+dfsg-1

[Bastian Germann]

On Sun, 27 Nov 2022 10:00:56 + Debian FTP Masters 
 wrote:

   * Use Python 3 instead of Python 2 for building (closes: #938322).
 - Update build-dependency.
 - Add python3.patch, inspired by Arch Linux but using versioned python3.
 - Add chromium-python3.patch, copied from Arch Linux.


This is now literally the last package that has build depends on python2 in 
bookworm.
Is there a chance to move the experimental package to sid soon?

Bug#1024312: marked as done (rust-test-case build-deends on old version of rust-once-cell)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 23:07:37 +
with message-id 
and subject line Bug#1024312: fixed in rust-test-case 2.2.2-5
has caused the Debian Bug report #1024312,
regarding rust-test-case build-deends on old version of rust-once-cell
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.)


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

Package: rust-test-case
Version: 2.2.2-2
Severity: serious

rust-test-case depends on librust-once-cell-1.14+default-dev but Debian
now has version 1.16.

Generally, in line with semver, you shouldn't be depending on specific minor
versions once a crate is at version 1.0 or higher.
--- End Message ---
--- Begin Message ---
Source: rust-test-case
Source-Version: 2.2.2-5
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-test-case 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, 03 Dec 2022 22:21:09 +0100
Source: rust-test-case
Architecture: source
Version: 2.2.2-5
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1024312
Changes:
 rust-test-case (2.2.2-5) unstable; urgency=medium
 .
   * update patch 2001 to relax dependency on crate once-cell;
 relax build-dependency and autopkgtest dependencies
 on librust-once-cell-dev;
 closes: bug#1024312
   * update dh-cargo fork;
 build-depend on libstring-shellquote-perl
   * simplify build routines
Checksums-Sha1:
 dfe243b4a750f4ac49e4d6a2b5d3f748965e3c7b 2963 rust-test-case_2.2.2-5.dsc
 5f9357a9577f12a482aa989ecea0f98040b41bf2 12364 
rust-test-case_2.2.2-5.debian.tar.xz
 fca8b5f63cfa8691f986119d7d1a921c13cc6842 13297 
rust-test-case_2.2.2-5_amd64.buildinfo
Checksums-Sha256:
 5dc3b19a9a847d619b9511dfaba855668074a9d25a102efc051c4d63f21ea6e8 2963 
rust-test-case_2.2.2-5.dsc
 3f65e0924a2482a7a10e9afcb540d4e93d11797e6d73ab8fc4f88ae97450ce93 12364 
rust-test-case_2.2.2-5.debian.tar.xz
 d3ba0653cd367a1b95101090ec89140ba8278cf7f7d686e0a01c24178228fb00 13297 
rust-test-case_2.2.2-5_amd64.buildinfo
Files:
 6fc125b616e72a1584535f13fda5f53a 2963 rust optional rust-test-case_2.2.2-5.dsc
 1726314c8843e9cb3b621948cd5209cd 12364 rust optional 
rust-test-case_2.2.2-5.debian.tar.xz
 0eebd1883f16549a2be650325b0e22ba 13297 rust optional 
rust-test-case_2.2.2-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOL0DIACgkQLHwxRsGg
ASH50w/+PvEJCAOMOoQz7dStJgr6gh7Cdeb33RIGMjtkhNrmG7DpNbBt8U9Y/nvI
WkSOIsK9B5/V3y+zvWXk0/xUAeSco4oVQIkWszhfv+ovQYN9WyFtxZuVi4B4pqvd
dUefCdFAE0BS7kLQb0fZV8vl2ZRWkk1YwyWw3Xp0nRRSzurxAiaMyW5oI5RzFFQx
6ZMwEaUggA5I39VcDqZNrd7WwHagfnaP8ooiqo9DqktJfYsI16CCwnTB7L3MLm7t
m7G2h6GzOdk5VD1viJ2jsVQpbS2ppnEftvjztnVZvtAJ306sGNYwpTbUImKcbio3
j1KNR76pOC1u2Mz1zhlnIWSzzTDkWoJf48OuQNb28S/aZtolf58ka5YRyqr65zlq
TaFKNP7zptxUEvS+OKCQFEBQi7vOtjFBzi9kE54sUqbfMGJdQs5EUmVQKQQ6wE1W
aOKc5YglJaK8nCaNNnYLDkiuSYn1blwhP106WlXjIYNZPbHvxpQst+3R4NomLeuH
XUgCtGEPWwmCi/CvgH1SAXzH2WgxXilzp3RU+Cx9NHqH5Al4vGJf6Le3BGH5Py+A
uoBqP/V4yEAFlL/Tp8SErhgFTaGQvdkwgsUylJcdtj2Xe5zHtCxNCCRuKfxlgFAs
+qFMK/3dKlkgkXN5/bzcCAh4TqfYTR9lXAVyIcyS7idgXcpWbn4=
=WKFP
-END PGP SIGNATURE End Message ---

Bug#945665: marked as done (dump1090-mutability: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 23:04:32 +
with message-id 
and subject line Bug#945665: fixed in dump1090-mutability 
1.15~20180310.4a16df3+dfsg-8.1
has caused the Debian Bug report #945665,
regarding dump1090-mutability: Python2 removal in sid/bullseye
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.)


-- 
945665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dump1090-mutability
Version: 1.15~20180310.4a16df3+dfsg-6
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: dump1090-mutability
Source-Version: 1.15~20180310.4a16df3+dfsg-8.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated dump1090-mutability 
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, 03 Dec 2022 23:38:23 +0100
Source: dump1090-mutability
Architecture: source
Version: 1.15~20180310.4a16df3+dfsg-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Bastian Germann 
Closes: 945665
Changes:
 dump1090-mutability (1.15~20180310.4a16df3+dfsg-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop Recommends: python (Closes: #945665).
Checksums-Sha1:
 54cebcc0a36a42baf08e2ddfb45394e3c60c1681 2138 
dump1090-mutability_1.15~20180310.4a16df3+dfsg-8.1.dsc
 dc8b03045ce969b23045fd09400f797cd3a59f07 33312 
dump1090-mutability_1.15~20180310.4a16df3+dfsg-8.1.debian.tar.xz
 d5e0bab7256313fec928f4e57d76b5a4bba998a7 7170 
dump1090-mutability_1.15~20180310.4a16df3+dfsg-8.1_source.buildinfo
Checksums-Sha256:
 e655b8ec1c5fb22e345b7d5fb1b7df8b405cd7db2e56222ee8df574cca6423e5 2138 
dump1090-mutability_1.15~20180310.4a16df3+dfsg-8.1.dsc
 acc58ab7b6ccd76c0aa997dcfb50c047b84653db0ca2c14300c294f42def7608 33312 
d

Bug#945665: dump1090-mutability: Python2 removal in sid/bullseye

[Bastian Germann]

Uploading a NMU to fix this. debdiff attached.diff -Nru dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/changelog 
dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/changelog
--- dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/changelog 
2021-01-27 05:16:35.0 +0100
+++ dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/changelog 
2022-12-03 23:38:23.0 +0100
@@ -1,3 +1,10 @@
+dump1090-mutability (1.15~20180310.4a16df3+dfsg-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Recommends: python (Closes: #945665).
+
+ -- Bastian Germann   Sat, 03 Dec 2022 23:38:23 +0100
+
 dump1090-mutability (1.15~20180310.4a16df3+dfsg-8) unstable; urgency=medium
 
   * Team upload.
diff -Nru dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/control 
dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/control
--- dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/control   
2021-01-27 05:16:35.0 +0100
+++ dump1090-mutability-1.15~20180310.4a16df3+dfsg/debian/control   
2022-12-03 23:38:23.0 +0100
@@ -29,7 +29,6 @@
  ${shlibs:Depends}
 Recommends:
  lighttpd,
- python (>= 2.5)
 Provides:
  fatsv-data-source
 Description: ADS-B Ground Station System for RTL-SDR

Bug#1025281: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 22:08:58 +
with message-id 
and subject line Bug#1025281: fixed in nvidia-graphics-drivers-legacy-390xx 
390.157-1
has caused the Debian Bug report #1025281,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, 
CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259
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.)


-- 
1025281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5415

CVE-2022-34670  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an unprivileged
regular user can cause truncation errors when casting a primitive to a
primitive of smaller size causes data to be lost in the conversion,
which may lead to denial of service or information disclosure.

CVE-2022-42263  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an Integer
overflow may lead to denial of service or informa

Processed: Re: urjtag: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - bookworm bullseye sid
Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye
Removed tag(s) sid, bookworm, and bullseye.
> unblock 937569 by -1
Bug #937569 [src:python2.7] python2.7: Python2 removal in sid/bullseye
937569 was blocked by: 937903 936516 936931 937931 938791 938766 938381 966751 
936309 966783 936660 936920 936814 938670 937519 936825 966784 938637 937136 
938705 936674 936444 938114 938841 936778 936852 936344 937622 938792 937262 
936962 938795 943085 935767 936877 936721 936818 936462 937027 938691 938666 
936777 938423 938510 938096 936819 937420 937304 936361 936909 937102 937320 
938745 938130 936268 936938 936628 937628 936941 936681 936858 936557 938252 
937103 936611 966800 938647 936161 936885 937611 936859 943016 938803 938095 
938386 936581 936936 937266 937291 938665 938124 937333 937511 936942 967143 
937339 936624 937150 936853 938451 936366 936658 937135 937234 936828 942941 
936854 938532 936627 938743 936937 936270 938507 938036 936902 937025 936829 
938921 936890 936515 936558 936659 936805 936570 937094 936183 938686 938852 
936900 966738 936915 937841 936958 937009 942981 936810 886617 936595 936602 
937411 938660 938618 936736 945863 936869 936839 943223 937695 936271 945641 
938393 937118 936928 936863 966801 943212 936864 936834 938167 945742 936569 
938403 936536 953377 937062 966733 936240 937701 942972 938774 936371 935209 
936538 947232 936895 937290 938346 936541 937912 936119 936669 937423 966737 
936912 936358 937174 937691 936957 1020928 938462 937099 937400 936982 936282 
936802 942977 937115 936635 936796 937731 936185 942988 936720 936489 938859 
937697 936983 936951 936251 936279 938723 936832 936862 937898 937171 936978 
936318 937039 936897 936844 936921 939594 938380 937696 938790 937960 938572 
938076 936850 938237 936274 938711 937548 936503 936314 936483 938615 936561 
936794 966793 937273 936809 937038 937483 937068 942987 883157 936893 936632 
936919 936219
937569 was blocking: 938198
Removed blocking bug(s) of 937569: 945742
> unblock 937695 by -1
Bug #937695 [src:python-defaults] python-defaults: Python2 removal in 
sid/bookworm
937695 was blocked by: 938421 937785 936120 937823 936628 938762 937238 936337 
938063 938156 942963 936529 938278 937758 936437 936872 966724 936196 936859 
936464 938489 937269 936581 936132 937553 938644 936266 943104 938389 945728 
936942 937491 936728 938129 936556 938383 936245 936442 938520 934870 937658 
942938 937391 936853 938483 938596 943193 937263 937559 937078 938181 938532 
936480 936937 883194 938850 937572 938744 936890 938921 937193 936147 938069 
966775 936523 942969 937903 937090 936776 938259 945719 937394 937296 937884 
943166 966783 943232 936630 936299 938866 937494 937779 937026 938705 937166 
936787 937616 937053 937673 943090 938924 938375 946929 938272 943026 937435 
945676 936560 938047 938184 937232 936169 938710 936619 938020 937101 943247 
937860 935767 943303 938226 938290 938639 937059 936730 937578 937145 942996 
937679 938096 938605 966789 938845 945630 936687 937072 937247 936293 937773 
938032 936361 936584 938801 938641 937403 936448 943145 938610 945713 938160 
938668 936276 936158 933775 938759 937914 936704 937796 938626 938239 938690 
937720 936185 938198 938107 936474 936799 939181 943033 937388 945699 937455 
936693 937647 937898 936862 939483 938402 937252 937355 937033 938772 937488 
938016 943279 937544 938241 938653 938073 938210 966746 938268 942973 939112 
937039 943068 943273 936844 936604 943041 938558 937696 942979 937620 938790 
966797 936699 937562 936507 938585 943005 937314 936974 938233 936325 937041 
936793 938828 937273 937068 943039 937005 936425 938672 937414 945650 938753 
945704 938052 936222 936219 936457 938262 938308 947297 936645 936805 967200 
937738 936570 945666 938887 936179 938465 939641 937482 947027 936601 936841 
943044 938408 937176 938497 937258 937663 937892 936868 938365 936810 945701 
937440 937927 937769 937411 938192 943285 937836 945745 937187 938573 943113 
936839 937533 937044 936152 943258 938516 943176 938579 943119 936228 938058 
937327 943122 936745 942958 936833 937638 937539 953377 936536 937940 936701 
937062 937427 938819 937911 936371 937510 937568 938346 937119 938244 937541 
937122 938830 945645 936957 936173 937870 937505 939259 943062 936268 945726 
936241 937495 937681 936772 937019 937022 937467 938693 937885 938862 938799 
943292 936690 936107 937162 938070 937334 938704 937236 942970 966771 937030 
936759 945672 938374 938276 938650 938222 937144 938219 945626 936753 938425 
937781 936672 937087 938092 942992 938793 945690 936828 937270 937013 938507 
938598 936902 936585 938036 937712 946849 938699 938230 936790 943144 937076 
936726 953220 938604 938844 936558 936659 966757 945653 938750 938152 945678 
938839 966725 937931 937105 938766 936573 943298 937660 943207 937168 937784 
937618 936813 937141 937519 936876 943105 938810 938601 938841 937443 937028 
938357 93646

Bug#945742: urjtag: Python2 removal in sid/bullseye

[Bastian Germann]

Control: tags -1 - bookworm bullseye sid
Control: unblock 937569 by -1
Control: unblock 937695 by -1

This affects only experimental.

Processed: found

[Debian Bug Tracking System]

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

> notfound 945742 urjtag/0.10+r2007-1.2
Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye
No longer marked as found in versions urjtag/0.10+r2007-1.2.
>
End of message, stopping processing here.

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

Bug#1025310: marked as pending in libsamplerate

[Dennis Braun]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/libsamplerate/-/commit/d33a01f5d2922bc6156086ab5d77c2229af520f7


Fix FTBFS with fftw3. Thanks to Bas Couwenberg (Closes: #1025310)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025310

Processed: Bug#1025310 marked as pending in libsamplerate

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025310 [src:libsamplerate] libsamplerate: FTBFS with fftw3 (3.3.10-1)
Added tag(s) pending.

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

Bug#1024906: apparently fixed Re: dask autopkgtest fail with python 3.11

[Rebecca N. Palmer]

This combination stopped failing on 2022-11-22/23 (without a dask 
upload, suggesting it was fixed somewhere other than dask itself).


Hence, I suggest closing this bug.

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1025394 normal
Bug #1025394 [src:llvm-toolchain-14] clang-14: undefined symbol errors on 
chromium with basic_string
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: found

[Debian Bug Tracking System]

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

> found 945742 0.10+r2007-1.2
Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye
Marked as found in versions urjtag/0.10+r2007-1.2.
>
End of message, stopping processing here.

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

Bug#1025394: clang-14: undefined symbol errors on chromium with basic_string

[Andres Salomon]

Source: llvm-toolchain-14
Version: 1:14.0.6-8
Severity: serious
Tags: ftbfs fixed-upstream patch sid
Justification: fails to build from source

When building chromium, I hit the following:

ld.lld: error: undefined symbol: void 
std::__cxx11::basic_string, 
std::allocator >::_M_construct(char16_t 
const*, char16_t const*, std::forward_iterator_tag)

   >>> referenced by http_handler.cc
   >>>   
obj/chrome/test/chromedriver/lib/http_handler.o:(internal::MatchesCommand(std::__cxx11::basic_stringstd::char_traits, std::allocator > const&, 
std::__cxx11::basic_string, 
std::allocator > const&, CommandMapping const&, 
std::__cxx11::basic_string, 
std::allocator >*, base::DictionaryValue*))



Even fixing that one implicit cast from std::u16string to 
base::StringPiece16, there's many more of those types of errors. The 
errors were trigged by chromium upstream switching from --std=c++17 to 
--std=c++20, so I figured I could work around it with this patch:




Unfortunately, even with that it still happens on some architectures:



Upstream claimed to have fixed this bug in clang 14.0.5, however it 
then popped up again in 14.0.6:




There's now a fix from 2 days ago:



It would be great to get this fixed in sid, and it's also an issue in 
bullseye with clang-13. It's probably also in clang-15, I'm guessing, 
although I haven't tested it and will likely get fixed automatically in 
the next clang point release.


Thanks,
Andres

Bug#1025341: marked as done (rust-lalrpop: flaky autopkgtest on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 21:00:47 +
with message-id 
and subject line Bug#1025341: fixed in rust-lalrpop 0.19.8-4
has caused the Debian Bug report #1025341,
regarding rust-lalrpop: flaky autopkgtest on s390x
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.)


-- 
1025341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-lalrpop
Version: 0.19.8-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of rust-lalrpop as it was
blocking glibc. I noticed that it sometimes fails on s390x with the
following error:

thread 'lr1::build::test::expr_grammar1' has overflowed its stack
fatal runtime error: stack overflow
error: test failed, to rerun pass '--lib'

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.ylFj0b7NXt/target/s390x-unknown-linux-gnu/debug/deps/lalrpop-d02d6930d272c3cf`
 (signal: 6, SIGABRT: process abort signal)
autopkgtest [23:12:06]: test librust-lalrpop-dev:lexer: ---]
autopkgtest [23:12:06]: test librust-lalrpop-dev:lexer:  - - - - - - - - - - 
results - - - - - - - - - -
librust-lalrpop-dev:lexer FAIL non-zero exit status 101

See the logs of failed and successful runs:
https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-lalrpop/28902703/log.gz
https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-lalrpop/28902705/log.gz

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: rust-lalrpop
Source-Version: 0.19.8-4
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-lalrpop 
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, 03 Dec 2022 19:37:02 +
Source: rust-lalrpop
Architecture: source
Version: 0.19.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1025341
Changes:
 rust-lalrpop (0.19.8-4) unstable; urgency=medium
 .
   * Team upload.
   * Package lalrpop 0.19.8 from crates.io using debcargo 2.6.0
   * Attempt to fix sporadic stack overflow in expr_grammar1 test (Closes: 
#1025341)
 + Increase stack size for test to 10 MiB
 + Replace random number generator with one that has a fixed seed.
Checksums-Sha1:
 8f5debb8e53ecba0a2106bf4fbda8252ddf127a9 2804 rust-lalrpop_0.19.8-4.dsc
 1c6cddfef9ba008b6e97b8e9b8f9810e92f02ad7 5920 
rust-lalrpop_0.19.8-4.debian.tar.xz
 6aefda0b198f28f9d756d8f425670c9adeba6345 11373 
rust-lalrpop_0.19.8-4_source.buildinfo
Checksums-Sha256:
 4e52709a8e7db4cfaba587eef21735787d161e7598c7d66c56c8c1c05a9530f5 2804 
rust-lalrpop_0.19.8-4.dsc
 9985db3a78ce040c171d4f7f828fd5f6b0517694b81c6f86ab8082bb93f70c87 5920 
rust-lalrpop_0.19.8-4.debian.tar.xz
 ed540088f655b46ca47ef183018531b5c879d70ebac60fb1c4bf3dcc80c690de 11373 
rust-lalrpop_0.19.8-4_source.buildinfo
Files:
 481b0f3660f41d34fdff79e991c0ad5c 2804 rust optional rust-lalrpop_0.19.8-4.dsc
 ce4bb5af6c16bfa9e82ee0d1b7096fd5 5920 rust optional 
rust-lalrpop_0.19.8-4.debian.tar.xz
 6074de5cb022035e9be7426863b7b15b 11373 rust optional 
rust-lalrpop_0.19.8-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmOLqqIUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsmBw//WA6oCGuE93HNyXpaxwsAdHGQ9++P
Jj+i/uMrsWNfFpOwnYgnpQKmSUVuYsm6Cb3Wp60ciFwkUimVch3XauR8P8S7p0fr
zdIj3X1+f2llz7CYrsSBTDc29TlU1yotVBrRU1sX9qCzk/hoIpHXn8VhunFNFGzl
Pt0kmYKhJcqGULLMkGc8rJHFDY7S0hWbCmeo/odHpOub6yCzCq9p3XOnCsvNQg/T
PRlaMOimwf2no5rBLnFkcAjlTH3iWWlDOtaKudoNvZM1fVdc57/B4K7zF1wcQJjw
Xw1LgBEwGe1IuhaFfp30fChZtjLqNesRATMvLLBEjz8MKmnz4iVl84TRW

Bug#1025391: hdf5-filter-plugin: missing Breaks+Replaces: bitshuffle

[Andreas Beckmann]

Package: hdf5-filter-plugin
Version: 0.0~git2022.49e3b65-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack 
.../hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb ...
  Unpacking hdf5-filter-plugin (0.0~git2022.49e3b65-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5bshuf.so', which is also in 
package bitshuffle 0.3.5-4+b1
  Errors were encountered while processing:
   
/var/cache/apt/archives/hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb


Is my understanding right that src:hdf5-filter-plugin supersedes src:bitshuffle?
Then please RM the obsolete bitshuffle package.

If bitshuffle is to be removed, the B+R against it can be unversioned (unless
you have a virtual bitshuffle package provided somewhere).


cheers,

Andreas


bitshuffle=0.3.5-4+b1_hdf5-filter-plugin=0.0~git2022.49e3b65-2.log.gz
Description: application/gzip

Bug#1025390: python3-prody-tests: missing Breaks+Replaces: python3-prody (<< 2.3.1)

[Andreas Beckmann]

Package: python3-prody-tests
Version: 2.3.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python3-prody-tests_2.3.1+dfsg-1_all.deb ...
  Unpacking python3-prody-tests (2.3.1+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-prody-tests_2.3.1+dfsg-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/prody/tests/__init__.py', which is also in 
package python3-prody 2.2.0+dfsg-3+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-prody-tests_2.3.1+dfsg-1_all.deb


cheers,

Andreas


python3-prody=2.2.0+dfsg-3+b1_python3-prody-tests=2.3.1+dfsg-1.log.gz
Description: application/gzip

Bug#1019645: marked as done (ruby-otr-activerecord: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 19:27:17 +
with message-id 
and subject line Bug#1019645: fixed in ruby-otr-activerecord 2.1.1-0.1
has caused the Debian Bug report #1019645,
regarding ruby-otr-activerecord: FTBFS with ruby3.1: ERROR: Test "ruby3.1" 
failed:  ArgumentError:
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.)


-- 
1019645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-otr-activerecord
Version: 2.0.3-3
Severity: important
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 ruby-otr-activerecord with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>  ArgumentError:
>    wrong number of arguments (given 4, expected 1)
>  # ./lib/otr-activerecord/activerecord.rb:61:in 
> `configure_from_file!'
>  # ./spec/otr-activerecord/activerecord_spec.rb:21:in `block (4 
> levels) in '
> 
> Finished in 0.00541 seconds (files took 0.43504 seconds to load)
> 2 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/otr-activerecord/activerecord_spec.rb:8 # 
> OTR::ActiveRecord.configure_from_file! when simple configuration file is 
> given configures active record
> rspec ./spec/otr-activerecord/activerecord_spec.rb:20 # 
> OTR::ActiveRecord.configure_from_file! when configuration file with multiple 
> roles given configures active record
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> mv examples/grape-activerecord4/.gem2deb.Gemfile.lock 
> examples/grape-activerecord4/Gemfile.lock
> mv examples/grape-activerecord5/.gem2deb.Gemfile.lock 
> examples/grape-activerecord5/Gemfile.lock
> mv examples/rakefile-activerecord5/.gem2deb.Gemfile.lock 
> examples/rakefile-activerecord5/Gemfile.lock
> mv examples/rakefile-activerecord5.2/.gem2deb.Gemfile.lock 
> examples/rakefile-activerecord5.2/Gemfile.lock
> mv examples/rakefile-activerecord6.0/.gem2deb.Gemfile.lock 
> examples/rakefile-activerecord6.0/Gemfile.lock
> mv examples/rakefile-activerecord7.0/.gem2deb.Gemfile.lock 
> examples/rakefile-activerecord7.0/Gemfile.lock
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-otr-activerecord/ruby-otr-activerecord_2.0.3-3+rebuild1663007937_amd64-2022-09-12T18:38:58Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-otr-activerecord
Source-Version: 2.1.1-0.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ruby-otr-activerecord 
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, 20 Nov 2022 10:21:15 +0200
Source: ruby-otr-activerecord
Architecture: source
Version: 2.1.1-0.1
Distribution: unstable
Urgency: low
Maintainer:

Bug#1017319: marked as done (gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 19:20:41 +
with message-id 
and subject line Bug#1017161: fixed in gringo 5.4.1-3.1
has caused the Debian Bug report #1017161,
regarding gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an 
integer constant before ‘]’ token
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.)


-- 
1017161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gringo
Version: 5.4.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build.dir/hardening_mt'
> [  8%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/main.cpp.o
> [  8%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o
> [  9%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_value.cpp.o
> [  9%] Building CXX object 
> clasp/libpotassco/app/CMakeFiles/lpconvert.dir/lpconvert.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o
>  -MF CMakeFiles/test_potassco_opts.dir/test_application.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/test_application.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_application.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/main.cpp.o -MF 
> CMakeFiles/test_potassco_opts.dir/main.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/main.cpp.o -c 
> /<>/clasp/libpotassco/tests/main.cpp
> [  9%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_value.cpp.o 
> -MF CMakeFiles/test_potassco_opts.dir/test_value.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/test_value.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_value.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/app && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/app/CMakeFiles/lpconvert.dir/lpconvert.cpp.o -MF 
> CMakeFiles/lpconvert.dir/lpconvert.cpp.o.d -o 
> CMakeFiles/lpconvert.dir/lpconvert.cpp.o -c 
> /<>/clasp/libpotassco/app/lpconvert.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=c++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -MF 
> CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o.d -o 
> CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_aspif.cpp
> [ 10%] Building CXX object 
> clasp/src/CMakeFiles/libclasp.dir/asp_preprocessor.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/src && /usr/bin/g++-10  
> -I/<>/clasp -I/<>/build.dir/hardening_mt/clasp 
> -I/<>/clasp/libpo

Bug#1023682: marked as done (gringo build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 19:20:41 +
with message-id 
and subject line Bug#1023682: fixed in gringo 5.4.1-3.1
has caused the Debian Bug report #1023682,
regarding gringo build depends on gcc-10 that should not be in bookworm
to be marked as done.

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

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


-- 
1023682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gringo
Version: 5.4.1-3
Severity: serious
Tags: bookworm sid
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.4.1-3.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gringo 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, 19 Nov 2022 12:33:48 +0200
Source: gringo
Architecture: source
Version: 5.4.1-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 963054 1015422 1017161 1023682
Changes:
 gringo (5.4.1-3.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Build using the default gcc. (Closes: #1023682)
   * Add patch from Lukas Märdian to use the system catch/catch2.
 (Closes: #1017161)
   * Fix the testsuite for Python no longer supporting 'rU' in open().
   * Remove the symbols file. (Closes: #963054, #1015422)
Checksums-Sha1:
 49406d3c1ad4265de14d9c97297d8b5b8dc9da6d 2131 gringo_5.4.1-3.1.dsc
 798850eb7f4ef4045682c6ba7fb6dbb88b0677f1 21592 gringo_5.4.1-3.1.debian.tar.xz
Checksums-Sha256:
 0597322ea1414ee31e101d7b1a9617166519991a7ab11a06a34855ab77895a84 2131 
gringo_5.4.1-3.1.dsc
 3b40f14945cd7d7e614200da06c501372680c7b555032c6fe601f654f50d23e9 21592 
gringo_5.4.1-3.1.debian.tar.xz
Files:
 6d1a4dc6648aef0403a13bff094b2e90 2131 interpreters optional 
gringo_5.4.1-3.1.dsc
 28fbdde6e24ae0e1e9b7e9d7d67af433 21592 interpreters optional 
gringo_5.4.1-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN4ut4ACgkQiNJCh6LY
mLHlCxAAxYXfT9ia66Jr1oKkZ7vwJhOAWSdrWGAz8HLRt27qUR5f3EjYss3SKBUz
5+nEPTBrDaGwpTDqEDSz5nU+yeMhg3cFwSVRM6HNgz94wUYeVxwoG6BOU7hAbIud
mklYoF+sRT59ljMtidjnV4lho7NbMSMnLM/6vjKfbV2AvFmx4I/LxutP23uDfgF5
/FQS0j3zSYwY0JoKFLSPphIbcs3qLAqMxplCy/2xGvVWB4ED+hvbBuEbMz8qsMQT
SViMlMeJNoNY2NXot/x7yx7vA0ByZzspDCrMqVlV175NQamsQtJP6sL1hd3wcxOq
q1y25wgS6jzs502IpOTKvFwUqZ5VkooKVTuPpTGka60j94RLApDkCGcCrmNoEVsi
UkVC5to4OPSrJEePFCetUnmmVAXHyUJuunyEjOm6fZ5Htpmu49K1OThneJTMhMrn
2WSlvMLZC40gByGQpiaC5x0auiW9nO4lIq8HIk7ZWrPlS3ObeHmlhYPDp2SSJxaH
bmDEJwxrANUK2VeRs6Y752bPvN7tHL8PjyK7Qfdj1JcDyrq31TRSmjDL2G3QiYI1
Ni5dC5O4kJWZNI1ujO6ul7MO1XKKOxJW1WdRplQ5kLRrsTrTr4eYU4ne/AFwSPlT
Lgl76yXLK/M7O1A9KPXIOcme/sgxIDMijku8NI0i7dKvcIQhw+E=
=A1MU
-END PGP SIGNATURE End Message ---

Bug#1017161: marked as done (gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 19:20:41 +
with message-id 
and subject line Bug#1017161: fixed in gringo 5.4.1-3.1
has caused the Debian Bug report #1017161,
regarding gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an 
integer constant before ‘]’ token
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.)


-- 
1017161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gringo
Version: 5.4.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build.dir/hardening_mt'
> [  8%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/main.cpp.o
> [  8%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o
> [  9%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_value.cpp.o
> [  9%] Building CXX object 
> clasp/libpotassco/app/CMakeFiles/lpconvert.dir/lpconvert.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o
>  -MF CMakeFiles/test_potassco_opts.dir/test_application.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/test_application.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_application.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/main.cpp.o -MF 
> CMakeFiles/test_potassco_opts.dir/main.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/main.cpp.o -c 
> /<>/clasp/libpotassco/tests/main.cpp
> [  9%] Building CXX object 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_value.cpp.o 
> -MF CMakeFiles/test_potassco_opts.dir/test_value.cpp.o.d -o 
> CMakeFiles/test_potassco_opts.dir/test_value.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_value.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/app && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=gnu++11 -MD -MT 
> clasp/libpotassco/app/CMakeFiles/lpconvert.dir/lpconvert.cpp.o -MF 
> CMakeFiles/lpconvert.dir/lpconvert.cpp.o.d -o 
> CMakeFiles/lpconvert.dir/lpconvert.cpp.o -c 
> /<>/clasp/libpotassco/app/lpconvert.cpp
> cd /<>/build.dir/hardening_mt/clasp/libpotassco/tests && 
> /usr/bin/g++-10  -I/<>/clasp/libpotassco/tests 
> -I/<>/clasp/libpotassco -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -DNDEBUG -fvisibility=hidden 
> -std=c++11 -MD -MT 
> clasp/libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -MF 
> CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o.d -o 
> CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -c 
> /<>/clasp/libpotassco/tests/test_aspif.cpp
> [ 10%] Building CXX object 
> clasp/src/CMakeFiles/libclasp.dir/asp_preprocessor.cpp.o
> cd /<>/build.dir/hardening_mt/clasp/src && /usr/bin/g++-10  
> -I/<>/clasp -I/<>/build.dir/hardening_mt/clasp 
> -I/<>/clasp/libpo

Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)

[Ricardo Mones]

On Sat, 3 Dec 2022 18:38:20 +0100
Francesco Poli  wrote:

> Control: fixed -1 claws-mail-themes/20221017+dfsg.1-1
> 
> 
> [it seems to me that control directives in messages sent to -done
> addresses are not processed... I am repeating the directive for this
> reason]

Umm, how inconvenient, but thanks anyway! :)

> 
> On Sat, 3 Dec 2022 18:08:55 +0100 Ricardo Mones wrote:
> 
> > control: fixed -1 claws-mail-themes/20221017+dfsg.1-1
> > 
> > On Sun, 27 Feb 2022 17:55:23 +0100
> > Francesco Poli  wrote:
> > […]  
> > > > Yeah, agreed, but given I doubt that can be possible at this
> > > > point to make upstream release a new tarball just to fix those
> > > > bits, specially without a contact address. Will try to ask
> > > > upstream if somebody has his contact, otherwise I'm afraid the
> > > > only solution will be the removal.
> > > 
> > > Thanks for willing to attempt this.
> > > Let's see how it goes...  
> > 
> > Despite the time passed, efforts were worth it and it went well :-)
> >  
> [...]
> 
> This is great news, indeed!
> Thanks for your efforts.
> 
> 
> Now, if only the licensing status of Fugue/* were also ironed out...
> See the original bug report!  ;-)

Oh, the joys of reporting two problems on one bug… had lost track of
this one! The original web from where the theme icons are being reused
(http://www.pinvoke.com/) still works and points to the licence so I
tend to agree this is CC-BY-3.0, furthermore the theme includes the full
text in the LICENSE.txt, so I've updated the copyright file¹.

Presumably this can be improved if #884224 is fixed at some point ;-)

Regarding persuading authors to switch licenses, well, my feeling is
that you have the same power than me to do that. As you rightly said,
the license is accepted by Debian currently, and that, very likely,
outweighs any other argument you can give to them.

best regards, 

¹ 
https://salsa.debian.org/claws-mail-team/claws-mail-themes/-/commit/84ce4ff4d7141d5a95c57fec67556d8350f9ad81
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Alimony and bribes will engage a large share of your wealth.»

Bug#1023678: marked as done (clasp build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 19:19:23 +
with message-id 
and subject line Bug#1023678: fixed in clasp 3.3.5-4.2
has caused the Debian Bug report #1023678,
regarding clasp build depends on gcc-10 that should not be in bookworm
to be marked as done.

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

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


-- 
1023678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clasp
Version: 3.3.5-4.1
Severity: serious
Control: block 1023666 by -1

Please use the default gcc if possible,
or switch to gcc-12 that is default in bookworm.
--- End Message ---
--- Begin Message ---
Source: clasp
Source-Version: 3.3.5-4.2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated clasp 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, 19 Nov 2022 12:10:37 +0200
Source: clasp
Architecture: source
Version: 3.3.5-4.2
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 1023678
Changes:
 clasp (3.3.5-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Build using the default gcc. (Closes: #1023678)
Checksums-Sha1:
 a8802501cb6c50d0e0fb843eda0b7d3ed8865a71 2015 clasp_3.3.5-4.2.dsc
 304f6697ff52c54bdbe31d1085ed0a2c66c383c0 10356 clasp_3.3.5-4.2.debian.tar.xz
Checksums-Sha256:
 3f7779249406ba72560a20fef48dad036f88691ad2a69d31a8502f6644156080 2015 
clasp_3.3.5-4.2.dsc
 076b8691a0f5dd773d2880632d308b90e98f925ee4bbe347da1eda1fcfc73a45 10356 
clasp_3.3.5-4.2.debian.tar.xz
Files:
 7013dad61b610dfb34a2d940b1c790e0 2015 interpreters optional clasp_3.3.5-4.2.dsc
 8f747c7997d9752c223fad57ce340150 10356 interpreters optional 
clasp_3.3.5-4.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN4rEoACgkQiNJCh6LY
mLFqvBAAzczk+bAavHfWOqVhsF3fL263oRyFNVI+phEqd/Gn7mBuLWlQAzP3j4xA
ztYKM/oewJnX/Kfx2WXo0yVdPPpRoK6B2AqsLdtCvo1xdGhu+colFLzxbaw1lsVw
MuIJ5MauVIhuxo3BQcfTCQVkWFqfXid0ukfMnHoMAUUXYUz3kMZxbuemei1uS78n
XH9Tfov8sLHPv6g2MmEA2wJjMElwBc1I4HFQOqY9sjEstsU2BAM7mb7qNhTAbDtm
lRq6Y9MEoV3E4+Cfj6FisXXGsqh0ClWhMkzrcQA6xK1NpXsG5LamPIgI93iBY3ml
r5Hk6XmPjoVTr+UZmkVCmPvBaEjLLHw4erjKM8VmwB6N3xG+/FIYy1CyhD+e1JFI
3S1rlUFjdrSbRhxvPrEccs3p7gLhwHj0217O3bAKsNkL/+Xdy5U/wQV1EmqGyNAn
vySxGrHcv9UxQWv30OxGYEmsHVtum4imLPjSSpnyuwavdusPbQhsoV+bp7ca1GKO
iHOotvTc4FvJ2cO9UF8/XmJ66Cmb2+RQcPJ1wnV24vk5yHpSszp/1ZLV9KtKr03r
PVhtRutOHiTgdUA3WYbsfGZ3dG2zztXE4oiU/4LD1Au/9GnzQXqfhgDXxfF7lMMq
W8mb69e2hbJYBTIESaxsGcJDjf59rdBMiZMY6uMB609nUOnBNfQ=
=kJC6
-END PGP SIGNATURE End Message ---

Bug#1025374: firefox: reproducible crashes on various websites

[Vincent Lefevre]

On 2022-12-03 12:49:39 +0100, Vincent Lefevre wrote:
> Since FF 107, I've noticed crashes on several websites, including
> Facebook (even just after a restart).

It seems that it got worse in the last few days, though FF 107 got
last upgraded on 2022-11-16.

Note: Nightly also crashes on Facebook (with a new profile).

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

Bug#1024431: gcc-12: diff for NMU version 12.2.0-9.1

[Sean Whitton]

Control: tags 1024431 + patch
Control: tags 1024431 + pending


Dear maintainer,

I've prepared an NMU for gcc-12 (versioned as 12.2.0-9.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
Sean Whitton
diff -Nru gcc-12-12.2.0/debian/changelog gcc-12-12.2.0/debian/changelog
--- gcc-12-12.2.0/debian/changelog  2022-11-03 01:40:42.0 -0700
+++ gcc-12-12.2.0/debian/changelog  2022-12-02 18:28:07.0 -0700
@@ -1,3 +1,10 @@
+gcc-12 (12.2.0-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * libgccjit0: Depend on libc6-dev (Closes: #1024431).
+
+ -- Sean Whitton   Fri, 02 Dec 2022 18:28:07 -0700
+
 gcc-12 (12.2.0-9) unstable; urgency=medium
 
   * Update to git 20221103 from the gcc-12 branch.
diff -Nru gcc-12-12.2.0/debian/control gcc-12-12.2.0/debian/control
--- gcc-12-12.2.0/debian/control2022-11-02 09:19:52.0 -0700
+++ gcc-12-12.2.0/debian/control2022-12-02 18:28:07.0 -0700
@@ -783,7 +783,7 @@
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Priority: optional
-Depends: gcc-12-base (= ${gcc:Version}), libgcc-12-dev, binutils, 
${shlibs:Depends}, ${misc:Depends}
+Depends: gcc-12-base (= ${gcc:Version}), libgcc-12-dev, binutils, 
${dep:libcdev}, ${shlibs:Depends}, ${misc:Depends}
 Breaks: python-gccjit (<< 0.4-4), python3-gccjit (<< 0.4-4)
 Description: GCC just-in-time compilation (shared library)
  libgccjit provides an embeddable shared library with an API for adding
diff -Nru gcc-12-12.2.0/debian/control.m4 gcc-12-12.2.0/debian/control.m4
--- gcc-12-12.2.0/debian/control.m4 2022-11-02 09:19:37.0 -0700
+++ gcc-12-12.2.0/debian/control.m4 2022-12-02 18:28:07.0 -0700
@@ -3263,7 +3263,7 @@
 Pre-Depends: ${misc:Pre-Depends}
 ')`'dnl
 Priority: optional
-Depends: BASEDEP, libgcc`'PV-dev, binutils, ${shlibs:Depends}, ${misc:Depends}
+Depends: BASEDEP, libgcc`'PV-dev, binutils, ${dep:libcdev}, ${shlibs:Depends}, 
${misc:Depends}
 Breaks: python-gccjit (<< 0.4-4), python3-gccjit (<< 0.4-4)
 BUILT_USING`'dnl
 Description: GCC just-in-time compilation (shared library)


signature.asc
Description: PGP signature

Processed: gcc-12: diff for NMU version 12.2.0-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1024431 + patch
Bug #1024431 [libgccjit0] libgccjit0: missing Depends: libc6-dev
Added tag(s) patch.
> tags 1024431 + pending
Bug #1024431 [libgccjit0] libgccjit0: missing Depends: libc6-dev
Added tag(s) pending.

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

Processed: Bumping severity of sphinx 5 FTBFS bugs

[Debian Bug Tracking System]

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

> # I am going to upload Sphinx 5.3 to unstable soon
> severity 1013381 serious
Bug #1013381 [src:buildbot] buildbot: FTBFS with Sphinx 5.0, docutils 0.18: 
make[2]: *** [Makefile:67: singlehtml] Error 2
Severity set to 'serious' from 'important'
> severity 1013384 serious
Bug #1013384 [src:petsc4py] petsc4py: FTBFS with Sphinx 5.0, docutils 0.18: 
make[1]: *** [debian/rules:77: override_dh_sphinxdoc-indep] Error 255
Severity set to 'serious' from 'important'
> severity 1013385 serious
Bug #1013385 [src:recommonmark] recommonmark: FTBFS with Sphinx 5.0, docutils 
0.18: AssertionError:
Severity set to 'serious' from 'important'
> severity 1013391 serious
Bug #1013391 [src:sphinx-tabs] sphinx-tabs: FTBFS with Sphinx 5.0, docutils 
0.18: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.9 3.10" returned exit code 13
Severity set to 'serious' from 'important'
> severity 1013395 serious
Bug #1013395 [src:mpdecimal] mpdecimal: FTBFS with Sphinx 5.0, docutils 0.18: 
make[1]: *** [debian/rules:60: override_dh_sphinxdoc] Error 255
Severity set to 'serious' from 'important'
> severity 1013398 serious
Bug #1013398 [src:petsc] petsc: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: 
*** [debian/rules:591: override_dh_sphinxdoc-indep] Error 255
Severity set to 'serious' from 'important'
> severity 1013399 serious
Bug #1013399 [src:sagemath] sagemath: FTBFS with Sphinx 5.0, docutils 0.18: ln: 
failed to create symbolic link '*/_static': No such file or directory
Severity set to 'serious' from 'important'
> severity 1013406 serious
Bug #1013406 [src:python-os-api-ref] python-os-api-ref: FTBFS with Sphinx 5.0, 
docutils 0.18: FAIL: 
os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_response
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013381
1013384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013384
1013385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013385
1013391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013391
1013395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013395
1013398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013398
1013399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013399
1013406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]

[Steve McIntyre]

Hi Daniel!

On Sat, Dec 03, 2022 at 01:41:51AM +1100, Daniel Axtens wrote:
>Steve McIntyre  writes:
>>
>> программист некто (in CC) reported this bug a few weeks back in
>> Debian. Since I applied the bundle of filesystem bounds-checking fixes
>> a few months back, he can't run grub-install. He's done the work to
>> determine that the patch that breaks things for him is
>>
>> 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end 
>> of nat journal entries
>>
>> The full thread of our discussion is at https://bugs.debian.org/1021846
>>
>> I don't have any knowledge of f2fs to go any further here. Help please! :-)
>
>Ergh, apologies for the regression.
>
>[somewhat off-topic: The fix came from a crash derived from fuzzing. I
>am not really knowledgeable about f2fs either - I was just trying to do
>my best based on what we could derive from the existing driver. In
>general, filesystems are a nightmare for fuzzing fixes because testing
>beyond the (quite decent!) tests that the grub test-suite runs is very
>challenging. There is usually no-one who is both involved in grub
>security and an expert on any given file system either. We do the best
>we can. Sadly our regression rate has been climbing, so we may need to
>come up with some other way to secure file systems or get access to
>sufficient expertise in the future.]

ACK. I used to develop amd maintain filesystems as a day job, I
understand the issue! Writing good and comprehensive tests is hard,
and therefore quite rare!

>I had a massive, massive work-in-progress spiel where I looked at this
>code and compared the linux code and counted sizes and so on and so
>forth. I was getting nowhere. But eventually I realised I had just made
>an off-by-one error in the test. You're allowed to have up to n =
>NAT_JOURNAL_ENTRIES entries _inclusive_, because the loop below uses i <
>n, not i <= n. D'oh.

Doh indeed! :-)

>Please try the following:
>
>diff --git a/grub-core/fs/f2fs.c b/grub-core/fs/f2fs.c
>index df6beb544cbd..855e24618c2b 100644
>--- a/grub-core/fs/f2fs.c
>+++ b/grub-core/fs/f2fs.c
>@@ -650,7 +650,7 @@ get_blkaddr_from_nat_journal (struct grub_f2fs_data *data, 
>grub_uint32_t nid,
>   grub_uint16_t n = grub_le_to_cpu16 (data->nat_j.n_nats);
>   grub_uint16_t i;
> 
>-  if (n >= NAT_JOURNAL_ENTRIES)
>+  if (n > NAT_JOURNAL_ENTRIES)
> return grub_error (GRUB_ERR_BAD_FS,
>"invalid number of nat journal entries");
>
>
>If for some reason that doesn't work, please add the following debug
>code and report the results:
>
>diff --git a/grub-core/fs/f2fs.c b/grub-core/fs/f2fs.c
>index 855e24618c2b..6e49a6d17b7a 100644
>--- a/grub-core/fs/f2fs.c
>+++ b/grub-core/fs/f2fs.c
>@@ -643,6 +643,10 @@ get_nat_journal (struct grub_f2fs_data *data)
>   return err;
> }
> 
>+#ifdef GRUB_UTIL
>+#include 
>+#endif
>+
> static grub_err_t
> get_blkaddr_from_nat_journal (struct grub_f2fs_data *data, grub_uint32_t nid,
>   grub_uint32_t *blkaddr)
>@@ -650,6 +654,10 @@ get_blkaddr_from_nat_journal (struct grub_f2fs_data 
>*data, grub_uint32_t nid,
>   grub_uint16_t n = grub_le_to_cpu16 (data->nat_j.n_nats);
>   grub_uint16_t i;
> 
>+#ifdef GRUB_UTIL
>+  fprintf(stderr, "%s: n = %hu\n", __func__, n);
>+#endif
>+
>   if (n > NAT_JOURNAL_ENTRIES)
> return grub_error (GRUB_ERR_BAD_FS,
>"invalid number of nat journal entries");
>

программист некто: could you please try these changes and report back?

>Amusingly the debug code shows that the grub-fs-tester tests always have
>n = 0, which makes sense for a test that doesn't really stress the
>file-system, and also explains why we didn't catch the bug when it was
>introduced.

Right.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#1024626: Blender removal for 32-bit architectures

[John Scott]

Hi,

I see from previous mails that Blender upstream has decided not to support 
32-bit architectures anymore. This is a friendly ping that the maintainer will 
request its removal so it may migrate into Bookworm.

Thanks,
John


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

Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)

[Francesco Poli]

Control: fixed -1 claws-mail-themes/20221017+dfsg.1-1


[it seems to me that control directives in messages sent to -done
addresses are not processed... I am repeating the directive for this
reason]


On Sat, 3 Dec 2022 18:08:55 +0100 Ricardo Mones wrote:

> control: fixed -1 claws-mail-themes/20221017+dfsg.1-1
> 
> On Sun, 27 Feb 2022 17:55:23 +0100
> Francesco Poli  wrote:
> […]
> > > Yeah, agreed, but given I doubt that can be possible at this point
> > > to make upstream release a new tarball just to fix those bits,
> > > specially without a contact address. Will try to ask upstream if
> > > somebody has his contact, otherwise I'm afraid the only solution
> > > will be the removal.  
> > 
> > Thanks for willing to attempt this.
> > Let's see how it goes...
> 
> Despite the time passed, efforts were worth it and it went well :-)
[...]

This is great news, indeed!
Thanks for your efforts.


Now, if only the licensing status of Fugue/* were also ironed out...
See the original bug report!  ;-)


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpSJ06kGGKeO.pgp
Description: PGP signature

Processed: Re: Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 claws-mail-themes/20221017+dfsg.1-1
Bug #1005840 {Done: Ricardo Mones } [claws-mail-themes] 
claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)
Marked as fixed in versions claws-mail-themes/20221017+dfsg.1-1.

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

Bug#1005840: marked as done (claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0))

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2022 18:08:55 +0100
with message-id <20221203180855.67e9d43e@curuxu>
and subject line Re: Bug#1005840: claws-mail-themes: includes non-free content 
(CC-by-nc-sa-v3.0)
has caused the Debian Bug report #1005840,
regarding claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.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.)


-- 
1005840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: claws-mail-themes
Version: 20140629+dfsg2-1
Severity: serious
Justification: Policy 2.2.1

Hello and thanks for maintaining claws-mail.

I noticed that one of the themes shipped in package 'claws-mail-themes'
is non-free and should not be included in a package in Debian main:

  Files: UltimateClawsMail0.5.1/*
  Copyright:
   Daniel LaGesse
  License: CC-BY-NC-SA-3.0
  Comment:
   http://creativecommons.org/licenses/by-nc-sa/3.0/

This is non-free, since it's non-commercial.
Please persuade its upstream copyright holder to re-license it
under DFSG-free terms (such as the GNU GPL) or drop the theme
from the package.


Another part of the package is apparently licensed under a
Creative Commons license, which is however identified with
a non-standard short name:

  Files: Fugue/*
  Copyright:
   Yusuke Kamiyamane (http://www.pinvoke.com/)
   Ciprian Popovici 
  License: CCA-3.0
  Comment:
   http://xlife.zuavra.net/index.php/tag/claws-mail/
   The package contains icons that vaguely resemble logos of Adobe
   products. They are a loose imitation of the originals, created from
   scratch. It is neither mine nor Kamiyamane-san's intention to infringe
   upon trademarks owned by Adobe nor to create any confusion regarding
   their products, but simply to provide means of loosely identifying
   certain types of mail attachments.

This license appears to be CC-BY-3.0, but the license text is not
explicitly identified as Creative Commons Attribution version 3.0
and the URL provided in the comment is now a dead link (the
domain no longer exists).
I would strongly recommend to persuade the upstream copyright
holders of these icons to re-license or dual-license them
under more clearly DFSG-free terms (such as the GNU GPL).
Although CC-BY-3.0 is accepted by Debian ftp masters, I respectfully
disagree with this decision: CC licenses (even the ones accepted
in Debian main) are highly controversial and considered non-free
by a number of people. It would be way better, if those icons were
more clearly DFSG-free.


Thanks for your time and patience!
Bye.
--- End Message ---
--- Begin Message ---
control: fixed -1 claws-mail-themes/20221017+dfsg.1-1

On Sun, 27 Feb 2022 17:55:23 +0100
Francesco Poli  wrote:
[…]
> > Yeah, agreed, but given I doubt that can be possible at this point
> > to make upstream release a new tarball just to fix those bits,
> > specially without a contact address. Will try to ask upstream if
> > somebody has his contact, otherwise I'm afraid the only solution
> > will be the removal.  
> 
> Thanks for willing to attempt this.
> Let's see how it goes...

Despite the time passed, efforts were worth it and it went well :-)
Unfortunately my typing mistake on the changelog¹ has prevented the
report from being closed properly with the last upload. Hence I'm doing
it by hand now, apologies for the inconvenience.

best regards,

¹
https://tracker.debian.org/news/1377421/accepted-claws-mail-themes-20221017dfsg1-1-source-into-unstable/
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «You will win success in whatever calling you adopt.»


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

Processed: Re: Bug#1022469: python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Debian Bug Tracking System]

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

> tags 1022469 +patch
Bug #1022469 [src:python-pint] python-pint: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.10 returned exit code 13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1022469: python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Michael Banck]

tags 1022469 +patch
thanks

Hi,

On Wed, Nov 23, 2022 at 07:48:47PM +1100, Stuart Prescott wrote:
> pint is incompatible with babel > 2.8; unfortunately, Debian now has babel
> 2.10.
> 
> So far, upstream has only noted the compatibility with version pinning.
> 
> https://github.com/hgrecco/pint/issues/1219
> 
> Upstream tests for newer releases of pint also now fail due to this same
> reason.

Looks like they got a work-around here in (since closed) PR #1401:
https://github.com/hgrecco/pint/commit/eb4e13428a3ede09148b76c71bc5b8cddb169176.patch
 
If I stick this (also attached) patch in, the testsuite passes fine.

> (and we should enable autopkgtest tests for pint and then this would have
> been caught as soon as babel > 2.8 was uploaded)

Yeah.


Michael
>From eb4e13428a3ede09148b76c71bc5b8cddb169176 Mon Sep 17 00:00:00 2001
From: Hernan 
Date: Wed, 27 Oct 2021 20:36:40 -0300
Subject: [PATCH] Support for babel > 2.8

Close #1400, #1219 and #1296.
---
 pint/formatting.py| 11 ---
 pint/testsuite/test_issues.py |  8 
 2 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/pint/formatting.py b/pint/formatting.py
index a04205dd9..528f4e03e 100644
--- a/pint/formatting.py
+++ b/pint/formatting.py
@@ -333,9 +333,14 @@ def formatter(
 # Don't remove this positional! This is the format used in Babel
 key = pat.replace("{0}", "").strip()
 break
-division_fmt = compound_unit_patterns.get("per", {}).get(
-babel_length, division_fmt
-)
+
+tmp = compound_unit_patterns.get("per", {}).get(babel_length, division_fmt)
+
+try:
+division_fmt = tmp.get("compound", division_fmt)
+except AttributeError:
+division_fmt = tmp
+
 power_fmt = "{}{}"
 exp_call = _pretty_fmt_exponent
 if value == 1:
diff --git a/pint/testsuite/test_issues.py b/pint/testsuite/test_issues.py
index ed781b72f..9d4167c02 100644
--- a/pint/testsuite/test_issues.py
+++ b/pint/testsuite/test_issues.py
@@ -824,6 +824,14 @@ def test_issue_1300(self):
 m = ureg.Measurement(1, 0.1, "meter")
 assert m.default_format == "~P"
 
+def test_issue_1400(self, sess_registry):
+q1 = 3 * sess_registry.W
+q2 = 3 * sess_registry.W / sess_registry.cm
+assert q1.format_babel("~", locale="es_Ar") == "3 W"
+assert q1.format_babel("", locale="es_Ar") == "3 vatios"
+assert q2.format_babel("~", locale="es_Ar") == "3.0 W / cm"
+assert q2.format_babel("", locale="es_Ar") == "3.0 vatios por centímetros"
+
 
 if np is not None:
 

Processed: Re: Bug#1024395: grub-efi-amd64-signed: after upgrade to 1+2.06+5 I get errors when booting (although I manage to boot)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1024395 [grub-efi-amd64-bin] grub-efi-amd64-signed: after upgrade to 
1+2.06+5 I get errors when booting (although I manage to boot)
Severity set to 'important' from 'grave'

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

Bug#1024395: grub-efi-amd64-signed: after upgrade to 1+2.06+5 I get errors when booting (although I manage to boot)

[Steve McIntyre]

Control: severity -1 important

Hi Eric,

On Fri, Nov 18, 2022 at 07:24:32PM +0100, Eric Valette wrote:
>Package: grub-efi-amd64-bin
>Version: 1+2.06+5
>Severity: grave
>Tags: security
>Justification: user security hole
>X-Debbugs-Cc: Debian Security Team 
>
>After upgrade to 2.06-5, I get an error message "prohibited by secure boot 
>policy" and it boot
>with a strange look with \xe7caracaters instead of lines.

Right. Those are both part of the security fixes that went into the
latest grub upload. It's trying to load fonts from /usr, but that's
now blocked when doing Secure Boot. It's basically cosmetic, but
obviously we don't want to leave it like this. We're talking upstream
about the best way to fix this up now.

>I build my own kernel and enrolled my owns keys, sign the linux
>kernel binarry and the mdoules with the keys. Everythong was working
>fine with 2.06-3.
>
>I also noticed that my enrolled keys is no more listed via "mokutil
>--list-enrolled". Although no key were cleared.

OK. I believe that is more likely an unrelated issue.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone

Bug#1025380: python3-fissix: SyntaxError: Missing parentheses in call to 'print'

[Jakub Wilk]

Package: python3-fissix
Version: 21.6.6-2
Severity: serious

python3-fissix fails to install:

   Setting up python3-fissix (21.6.6-2) ...
 File "/usr/lib/python3/dist-packages/fissix/fissix/tests/data/bom.py", 
line 2
   print "BOM BOOM!"
   ^
   SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
   dpkg: error processing package python3-fissix (--configure):
installed python3-fissix package post-installation script subprocess 
returned error exit status 1
   Processing triggers for libc-bin (2.36-6) ...
   Errors were encountered while processing:
python3-fissix
   E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Architecture: i386

Versions of packages python3-fissix depends on:
ii  python3-appdirs  1.4.4-3
ii  python3  3.10.6-3

--
Jakub Wilk

Bug#1022024: marked as done (python-gitlab FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 15:40:49 +
with message-id 
and subject line Bug#1022024: fixed in python-gitlab 1:3.12.0-1
has caused the Debian Bug report #1022024,
regarding python-gitlab FTBFS: test failures
to be marked as done.

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

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


-- 
1022024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gitlab
Version: 1:3.10.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-gitlab&arch=all&ver=1%3A3.10.0-1&stamp=1666104723&raw=0

...
=== FAILURES ===
 test_from_helper_subprocess_error_raises_error 

m_open = 
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f57355c8b50>

@mock.patch("builtins.open")
@pytest.mark.skipif(sys.platform.startswith("win"), reason="Not supported 
on Windows")
def test_from_helper_subprocess_error_raises_error(m_open, monkeypatch):
# using /usr/bin/false here to force a non-zero return code
fd = io.StringIO(
dedent(
"""\
[global]
default = helper

[helper]
url = https://helper.url
oauth_token = helper: /usr/bin/false
"""
)
)

fd.close = mock.Mock(return_value=None)
m_open.return_value = fd
with monkeypatch.context() as m:
m.setattr(Path, "resolve", _mock_existent_file)
with pytest.raises(config.GitlabConfigHelperError) as e:
>   config.GitlabConfigParser(gitlab_id="helper")

tests/unit/test_config.py:327: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
gitlab/config.py:114: in __init__
self._parse_config()
gitlab/config.py:198: in _parse_config
self._get_values_from_helper()
gitlab/config.py:266: in _get_values_from_helper
subprocess.check_output(commmand, stderr=subprocess.PIPE)
/usr/lib/python3.10/subprocess.py:420: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
/usr/lib/python3.10/subprocess.py:501: in run
with Popen(*popenargs, **kwargs) as process:
/usr/lib/python3.10/subprocess.py:969: in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
args = ['/usr/bin/false'], executable = b'/usr/bin/false', preexec_fn = None
close_fds = True, pass_fds = (), cwd = None, env = None, startupinfo = None
creationflags = 0, shell = False, p2cread = -1, p2cwrite = -1, c2pread = 11
c2pwrite = 12, errread = 13, errwrite = 14, restore_signals = True, gid = None
gids = None, uid = None, umask = -1, start_new_session = False

def _execute_child(self, args, executable, preexec_fn, close_fds,
   pass_fds, cwd, env,
   startupinfo, creationflags, shell,
   p2cread, p2cwrite,
   c2pread, c2pwrite,
   errread, errwrite,
   restore_signals,
   gid, gids, uid, umask,
   start_new_session):
"""Execute program (POSIX version)"""

if isinstance(args, (str, bytes)):
args = [args]
elif isinstance(args, os.PathLike):
if shell:
raise TypeError('path-like args is not allowed when '
'shell is true')
args = [args]
else:
args = list(args)

if shell:
# On Android the default shell is at '/system/bin/sh'.
unix_shell = ('/system/bin/sh' if
  hasattr(sys, 'getandroidapilevel') else '/bin/sh')
args = [unix_shell, "-c"] + args
if executable:
args[0] = executable

if executable is None:
executable = args[0]

sys.audit("subprocess.Popen", executable, args, cwd, env)

if (_USE_POSIX_SPAWN
and os.path.dirname(executable)
and preexec_fn is None
and not close_fds
and not pass_fds
and cwd is None
and (p2cread == -1 or p2cread > 2)
and (c2pwrite == -1 or c2pwrite > 2)
and (errwrite == -1 or errwrite > 2)
and not start_new_session
and gid is None
  

Bug#1012633: marked as done (imgvtopgm: FTBFS with netpbm11)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 15:38:46 +
with message-id 
and subject line Bug#1012633: fixed in imgvtopgm 2.1-1
has caused the Debian Bug report #1012633,
regarding imgvtopgm: FTBFS with netpbm11
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.)


-- 
1012633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imgvtopgm
Version: 2.0-9.1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi Erik,

imgvtopgm build-depends on libnetpbm9-dev, which has been obsoleted in favor
of libnetpbm11-dev (related: https://bugs.debian.org/1007984).  After
updating the build-dependency, the package still fails to build from source:

[...]
checking for X... no
checking for netpbm... libraries (none), headers /usr/include/netpbm
checking for pbm_init in -lpbm... no
configure: error: The PBM library '-lpbm' could not be found.
Please use the configure options '--with-pnm-includes=DIR'
and '--with-pnm-libraries=DIR' to specify the netpbm location.
See the 'config.log' file for further diagnostics.
make: *** [debian/rules:26: build-stamp] Error 1
[...]

Please update your package to work with the current netpbm-free.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: imgvtopgm
Source-Version: 2.1-1
Done: Erik Schanze 

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

Debian distribution maintenance software
pp.
Erik Schanze  (supplier of updated imgvtopgm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Dec 2022 00:17:28 +0100
Source: imgvtopgm
Architecture: source
Version: 2.1-1
Distribution: unstable
Urgency: low
Maintainer: Erik Schanze 
Changed-By: Erik Schanze 
Closes: 989953 999003 1007585 1012633
Changes:
 imgvtopgm (2.1-1) unstable; urgency=low
 .
   * New upstream version, make it compile for netpbm11 (Closes: #1012633)
   * Thanks Adrian for the NMU (Closes: #999003)
   * removed Recommends, the packages were removed
   * Switch to dpkg-source 3.0 (quilt) format (Closes: #1007585)
   * Fix FTCBFS: Export cross tools for configure. Thanks Helmut (Closes: 
#989953)
   * debian/control:
 + Bumped Standards-Version to 4.5.1, no changes needed
   * Increased debhelper version to 13
   * Fixed lintian warning about national-encoding in debian/man/*.de.1
Checksums-Sha1:
 7ae5ef86e8a45d9d09df9632922d6483f443f775 1729 imgvtopgm_2.1-1.dsc
 7ea54363e8330ab62a2d5e45f21c0454d142bd28 310604 imgvtopgm_2.1.orig.tar.gz
 003942817dad21553816eba33acf11dec9f814b3 6748 imgvtopgm_2.1-1.debian.tar.xz
Checksums-Sha256:
 113348cc49ae9170b799cb98c53c10c50bdb11c1a5df0973f09ae16ffb0d5fd7 1729 
imgvtopgm_2.1-1.dsc
 f5d2c3936af9d8d77cc8c756c500f8475ef12d6acd8bd569d89bba7d8fed4e48 310604 
imgvtopgm_2.1.orig.tar.gz
 e298242562622e8bb367e87044db8f62108667ec52f1eb4c7322b919a4fd5b70 6748 
imgvtopgm_2.1-1.debian.tar.xz
Files:
 36ef91abe2c18d275863ec2c364f5b12 1729 otherosfs optional imgvtopgm_2.1-1.dsc
 00fc1f44573aca68b1d5e9de9f16cd27 310604 otherosfs optional 
imgvtopgm_2.1.orig.tar.gz
 274e6be72c02dbd3b61aa4f21349c4de 6748 otherosfs optional 
imgvtopgm_2.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEulscPO2CY43D3w3scmdG4PC8g2UFAmOLZTsACgkQcmdG4PC8
g2UA+w/8CFHXBd9OGZK01d2yfFmwCZ0MQVEpB3gEs+lSpqCVfujs+oJ5ag6WFL0x
chE+X532uNkcrfCNR6EQpYj5qFQT5m9m4W9WDd5WAH96ywngXvzxZIznWQ8NsYcy
5FOk+F+OJ5G6xxO8BDtKU5sDIVVoH4Ez+0Fy+WDrK2x+By5s7VCKaH40J5v7N2vb
DTYIcB7VWLV0n6+pF57urd0TVljPbaNv4uqPEGXUL71MFMya/9JEDVF1zsmlxuY6
jrdTEU5o3KhxXG9nqfEazFiC3ab28NHdl6J2siKIEq949SScD5GnM8poIOCaNxqr
CpKB9xK5bg666K8uKkGM3cfGFS+ye7fpzY2WijAJdrNRM6/z2JhWgw

Bug#1025377: texstudio: Switch to libqtermwidget5-1-dev

[Sebastian Ramacher]

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

Unfortunately, qtermwidget bumpbed SONAME and also changed the name of
the -dev package. The new -dev package is called libqtermwidget5-1-dev.
Please adopt the package accordingly.

Cheers
-- 
Sebastian Ramacher

Processed: Re: pulsemixer: FTBFS: error: Multiple top-level packages discovered in a flat-layout: ['snap', 'debian'].

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream patch
Bug #1022496 [src:pulsemixer] pulsemixer: FTBFS: error: Multiple top-level 
packages discovered in a flat-layout: ['snap', 'debian'].
Added tag(s) upstream and patch.
> forwarded -1 https://github.com/GeorgeFilipkin/pulsemixer/pull/71
Bug #1022496 [src:pulsemixer] pulsemixer: FTBFS: error: Multiple top-level 
packages discovered in a flat-layout: ['snap', 'debian'].
Set Bug forwarded-to-address to 
'https://github.com/GeorgeFilipkin/pulsemixer/pull/71'.

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

Bug#1022496: pulsemixer: FTBFS: error: Multiple top-level packages discovered in a flat-layout: ['snap', 'debian'].

[Diederik de Haas]

Control: tag -1 upstream patch
Control: forwarded -1 https://github.com/GeorgeFilipkin/pulsemixer/pull/71

On Sun, 23 Oct 2022 15:41:02 +0200 Lucas Nussbaum  wrote:
> Source: pulsemixer
> Version: 1.5.1-1
> Severity: serious
> Justification: FTBFS

I submitted a patch upstream, but upstream seems kind of dead.

So I also created a MR on salsa with the same fix:
https://salsa.debian.org/debian/pulsemixer/-/merge_requests/1

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

Processed: block 1025363 with 1025312

[Debian Bug Tracking System]

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

> block 1025363 with 1025312
Bug #1025363 [src:libplacebo] libplacebo: FTBFS in sid (at least arm64 armhf 
riscv64 s390x)
1025363 was not blocked by any bugs.
1025363 was not blocking any bugs.
Added blocking bug(s) of 1025363: 1025312 and 1025324
> thanks
Stopping processing here.

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

Bug#1025363: marked as pending in libplacebo

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/libplacebo/-/commit/8354dc5458d149f156526bf49ace55fdbb02c97e


Apply upstream fix for FTBFS with latest glslang

Closes: #1025363


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025363

Processed: Bug#1025363 marked as pending in libplacebo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025363 [src:libplacebo] libplacebo: FTBFS in sid (at least arm64 armhf 
riscv64 s390x)
Added tag(s) pending.

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

Bug#1025374: firefox: reproducible crashes on various websites

[Vincent Lefevre]

Package: firefox
Version: 107.0-1
Severity: grave
Justification: renders package unusable
Tags: upstream
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1803899

Since FF 107, I've noticed crashes on several websites, including
Facebook (even just after a restart).

In particular, I can reproduce the crash on http://www.sylvainshunt.com
(where I don't expect the contents to change, so this should be a good
testcase) with a new profile. Upstream's Firefox Nightly is also
affected.

I don't know whether all these crashes are due to the same bug, though.
But I had never had any such crash with FF in the previous months, and
even years, IIRC.

-- Package-specific info:


-- Addons package information

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

Kernel: Linux 6.0.0-5-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

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.13.1-4.5
ii  libasound2   1.2.8-1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-6
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.4-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.2-1
ii  libgtk-3-0   3.24.35-1
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.85-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libstdc++6   12.2.0-9
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:3.3.17-7.1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec59  7:5.1.2-1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
ii  pulseaudio 16.1+dfsg1-2+b1

-- no debconf information

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

Processed: tagging 1025363

[Debian Bug Tracking System]

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

> tags 1025363 + fixed-upstream ftbfs
Bug #1025363 [src:libplacebo] libplacebo: FTBFS in sid (at least arm64 armhf 
riscv64 s390x)
Added tag(s) ftbfs and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1013651: marked as done (nbsphinx: FTBFS: KeyError in code-cells.ipynb: 'state')

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 11:21:17 +
with message-id 
and subject line Bug#1007847: fixed in nbsphinx 0.8.10+ds-1
has caused the Debian Bug report #1007847,
regarding nbsphinx: FTBFS: KeyError in code-cells.ipynb: 'state'
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.)


-- 
1007847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbsphinx
Version: 0.8.7+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 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 '/<>'
> PYTHONPATH=/<>/src python3 -m sphinx -b html doc 
> /<>/debian/python-nbsphinx-doc/usr/share/doc/python-nbsphinx/html
> Running Sphinx v4.5.0
> making output directory... done
> checking bibtex cache... out of date
> parsing bibtex file /<>/doc/references.bib... parsed 2 entries
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 31 source files that are out of date
> updating environment: [new config] 31 added, 0 changed, 0 removed
> reading sources... [  3%] a-normal-rst-file
> reading sources... [  6%] allow-errors
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> [IPKernelApp] WARNING | debugpy_stream undefined, debugging will not be 
> enabled
> reading sources... [  9%] allow-errors-per-cell
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> [IPKernelApp] WARNING | debugpy_stream undefined, debugging will not be 
> enabled
> reading sources... [ 12%] code-cells
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> /usr/lib/python3/dist-packages/IPython/paths.py:66: UserWarning: IPython 
> parent '/sbuild-nonexistent' is not a writable location, using a temp 
> directory.
>   warn("IPython parent '{0}' is not a writable location,"
> [IPKernelApp] WARNING | debugpy_stream undefined, debugging will not be 
> enabled
> [IPKernelApp] WARNING | Widget Javascript not detected.  It may not be 
> installed or enabled properly. Reconnecting the current kernel may help.
> 
> Notebook error:
> KeyError in code-cells.ipynb:
> 'state'
> Task was destroyed but it is pending!
> task:  coro= /usr/lib/python3/dist-packages/nbclient/client.py:816> wait_for= pending cb=[Task.task_wakeup()]>>
> make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/nbsphinx_0.8.7+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

If you reassign this bug to another package, please 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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nbsphinx
Source-Version: 0.8.10+ds-1
Done: Dmitry Shachnev 

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

A summary of the changes 

Bug#1025324: libc6: Xserver with nouveau not workiing.

[Santiago José López Borrazás]

El 3/12/22 a las 12:07, Aurelien Jarno escribió:

control: reassign -1 libgl1-mesa-dri
control: forcemerge 1025312 -1
control: affects 1025312 src:glibc

Hi,

On 2022-12-03 07:25, Agustin Martin wrote:

Hi all,

Also hit by this problem (intel i5 box).

Noticed that Xorg log showing the error is very similar to what is seen in

#1025312 [libgl1-mesa-dri: multiple packages FTBFS and have
autopkgtest regressions running test programs under Xvfb]

Thanks for the pointer, it indeed looks the real issue. Basically mesa
calls dlclose(NULL), that's why libc6 appears in the backtrace.

I am therefore reassigning the bug.

Regards
Aurelien


Yes. Is correct. Thanks.

--
Enviando desde Mozilla Thunderbird.



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1025324: libc6: Xserver with nouveau not workiing.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgl1-mesa-dri
Bug #1025324 [libc6] libc6: Xserver with nouveau not workiing.
Bug reassigned from package 'libc6' to 'libgl1-mesa-dri'.
No longer marked as found in versions glibc/2.36-6.
Ignoring request to alter fixed versions of bug #1025324 to the same values 
previously set
> forcemerge 1025312 -1
Bug #1025312 [libgl1-mesa-dri] libgl1-mesa-dri: multiple packages FTBFS and 
have autopkgtest regressions running test programs under Xvfb
Bug #1025324 [libgl1-mesa-dri] libc6: Xserver with nouveau not workiing.
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819'.
Severity set to 'grave' from 'normal'
1025332 was blocked by: 1025312
1025332 was not blocking any bugs.
Added blocking bug(s) of 1025332: 1025324
1025308 was blocked by: 1025312
1025308 was not blocking any bugs.
Added blocking bug(s) of 1025308: 1025324
Added indication that 1025324 affects 
src:muffin,xvfb,src:njplot,src:cogl,src:openscad,src:gsequencer,src:gtk4,src:clutter-1.0,src:gnome-builder,src:mutter,src:juce,src:gtk+3.0,src:pyopengl,src:kodi
Marked as found in versions mesa/22.3.0-1 and mesa/22.3.0~rc4-1.
Merged 1025312 1025324
> affects 1025312 src:glibc
Bug #1025312 [libgl1-mesa-dri] libgl1-mesa-dri: multiple packages FTBFS and 
have autopkgtest regressions running test programs under Xvfb
Bug #1025324 [libgl1-mesa-dri] libc6: Xserver with nouveau not workiing.
Added indication that 1025312 affects src:glibc
Added indication that 1025324 affects src:glibc

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

Bug#1025183: silx: (autopkgtest) needs update for python3.11: Segmentation fault

[Stuart Prescott]

It appears that src:silx FTBFS at present too. The failure is during 
building the docs with python3.10, meaning that this failure predates 
python3.11.


The failing line is:

# build the documentation
pybuild --build -s custom -p 3.10 --build-args="cd doc && env 
PYTHONPATH={build_dir} http_proxy='127.0.0.1:9' xvfb-run -a 
--server-args=\"-screen 0 1024x768x24\" {interpreter} -m sphinx -N 
-bhtml source build/html"
I: pybuild base:240: cd doc && env 
PYTHONPATH=/build/silx-pvssnu/silx-1.1.0+dfsg/.pybuild/cpython3_3.10_silx/build 
http_proxy='127.0.0.1:9' xvfb-run -a --server-args="-screen 0 
1024x768x24" python3.10 -m sphinx -N -bhtml source build/html

Running Sphinx v4.5.0
[...snip...]
reading sources... [ 92%] modules/sx
qt.qpa.xcb: could not connect to display :109
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even 
though it was found.
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.


Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, 
offscreen, vnc, xcb.


Aborted (core dumped)



--
Stuart Prescott   http://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer  http://www.debian.org/ stu...@debian.org
GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#1025371: fio-examples: missing Breaks+Replaces: fio (<< 3.32-2)

[Andreas Beckmann]

Package: fio-examples
Version: 3.32-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../fio-examples_3.33-2_all.deb ...
  Unpacking fio-examples (3.33-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fio-examples_3.33-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/fio/examples/1mbs_clients.fio', which is 
also in package fio 3.32-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/fio-examples_3.33-2_all.deb


cheers,

Andreas


fio=3.32-1_fio-examples=3.33-2.log.gz
Description: application/gzip

Bug#1025370: ntcard: ftbfs with nthash 2.3.0

[Étienne Mollier]

Source: ntcard
Version: 1.2.2+dfsg-4
Severity: serious
Tags: ftbfs upstream
Justification: ftbfs

Hi,

It seems that since introduction of nthash 2.3.0, ntcard is
failing to build from source.  Relevant part of the log:

g++ -DHAVE_CONFIG_H -I.  -I./Common -I/usr/include -I/<> 
-fopenmp -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o Common/nthll-Fcontrol.o `test -f 
'Common/Fcontrol.cpp' || echo './'`Common/Fcontrol.cpp
ntcard.cpp:2:10: fatal error: nthash/ntHashIterator.hpp: No such file 
or directory
2 | #include "nthash/ntHashIterator.hpp"
  |  ^~~
compilation terminated.
make[3]: *** [Makefile:632: ntcard-ntcard.o] Error 1
make[3]: *** Waiting for unfinished jobs
nthll.cpp:11:10: fatal error: nthash/ntHashIterator.hpp: No such file 
or directory
   11 | #include "nthash/ntHashIterator.hpp"
  |  ^~~
compilation terminated.

I tried a few things to get the package back on track, but
changes seem more involved than just changing headers.  I
suppose this would be fixed in an upcoming upstream version, but
such newer release does not seem to exist so far.

For information,
Étienne.

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

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


signature.asc
Description: PGP signature

Processed: Re: python-pam: Debian differences not clearly separated from upstream source

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #562702 [python-pam] python-pam: Debian differences not clearly separated 
from upstream source
Severity set to 'serious' from 'normal'

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

Processed: reassign 1025269 to wnpp, tagging 1025315, tagging 1025309, found 1025021 in 1.3.7-8

[Debian Bug Tracking System]

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

> reassign 1025269 wnpp
Bug #1025269 [dotnet-sdk-6.0] ITP dotnet in debian archive
Warning: Unknown package 'dotnet-sdk-6.0'
Bug reassigned from package 'dotnet-sdk-6.0' to 'wnpp'.
No longer marked as found in versions 6.0.403-1.
Ignoring request to alter fixed versions of bug #1025269 to the same values 
previously set
> tags 1025315 + sid bookworm
Bug #1025315 [src:pyxplot] pyxplot: FTBFS with fftw3 (3.3.10-1)
Added tag(s) bookworm and sid.
> tags 1025309 + sid bookworm
Bug #1025309 [src:jamin] jamin: FTBFS with fftw3 (3.3.10-1)
Added tag(s) bookworm and sid.
> found 1025021 1.3.7-8
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Marked as found in versions nose/1.3.7-8.
> thanks
Stopping processing here.

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

Bug#1025366: virtualbox-dkms does not compile with gcc-12

[Eric Valette]

Package: virtualbox-dkms
Version: 7.0.4-dfsg-4
Severity: grave
Tags: upstream
Justification: renders package unusable

dkms autoinstall
Sign command: /usr/lib/linux-kbuild-5.10/scripts/sign-file
Binary /usr/lib/linux-kbuild-5.10/scripts/sign-file not found, modules won't be 
signed

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=5.10.156 -C /lib/modules/5.10.156/build 
M=/var/lib/dkms/virtualbox/7.0.4/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.156 (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.4/build/make.log for more information.
root@tri-yann4:~# more /var/lib/dkms/virtualbox/7.0.4/build/make.log
DKMS make.log for virtualbox-7.0.4 for kernel 5.10.156 (x86_64)
Sat Dec  3 10:39:35 AM CET 2022
make: Entering directory '/usr/src/linux-i7-asus'
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPLibAll.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/combined-agnostic1.o
In file included from 
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/iprt/assert.h:45,
 from 
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/VBox/sup.h:44,
 from 
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvInternal.h:49,
 from /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrv.c:43:
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/VBox/vmm/hm_vmx.h:532:29: 
error: â\x80\x98VMX_BF_EPT_PT_0_MASKâ\x80\x99 undeclared here (not in a 
function); did you mean â\x80\x98VMX_BF_EPT_PT_RE
AD_MASKâ\x80\x99?
  532 | RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,
  | ^~
/var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/iprt/assertcompile.h:107:101:
 note: in definition of macro â\x80\x98AssertCompileNSâ\x80\x99
  107 | # define AssertCompileNS(expr)  extern int RTASSERTVAR[1

RT_BF_ASSERT_COMPILE_CHECKS macros does not what is expected. Using alternate 
definition makes it work

here is a  simple patch:

--- cdefs.h.orig2022-12-03 10:46:44.540262521 +0100
+++ cdefs.h 2022-12-03 10:57:10.289734851 +0100
@@ -2659,19 +2659,7 @@
  *
  * This requires variadic macros because its too much to type otherwise.
  */
-#if defined(RT_COMPILER_SUPPORTS_VA_ARGS) || defined(DOXYGEN_RUNNING)
-# define RT_BF_ASSERT_COMPILE_CHECKS(a_Prefix, a_uZero, a_uCovered, a_Fields) \
-AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_OR_MASK, a_uZero, 
a_Prefix, RT_UNPACK_ARGS a_Fields ) == a_uCovered); \
-AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_XOR_MASK, a_uCovered, 
a_Prefix, RT_UNPACK_ARGS a_Fields ) == 0); \
-AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_1ST_MASK_BIT,   true, 
a_Prefix, RT_UNPACK_ARGS a_Fields ) == true); \
-AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_MASK_START, true, 
a_Prefix, RT_UNPACK_ARGS a_Fields ) == true)
-/** Bit field compile time check helper
- * @internal */
-# define RT_BF_CHECK_DO_N(a_DoThis, a_uLeft, a_RightPrefix, ...) \
-RT_UNPACK_CALL(RT_CONCAT(RT_BF_CHECK_DO_, 
RT_EXPAND(RT_COUNT_VA_ARGS(__VA_ARGS__))), (a_DoThis, a_uLeft, a_RightPrefix, 
__VA_ARGS__))
-#else
 # define RT_BF_ASSERT_COMPILE_CHECKS(a_Prefix, a_uZero, a_uCovered, a_Fields) 
AssertCompile(true)
-#endif
 
 
 /** @def RT_ALIGN


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

Kernel: Linux 5.10.156 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.0.8-3

Versions of packages virtualbox-dkms recommends:
iu  virtualbox  7.0.4-dfsg-4

virtualbox-dkms suggests no packages.

-- no debconf information

Processed: libplacebo build failure [PATCH]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1025363 [src:libplacebo] libplacebo: FTBFS in sid (at least arm64 armhf 
riscv64 s390x)
Added tag(s) patch.

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

Bug#1025363: libplacebo build failure [PATCH]

[Gianfranco Costamagna]

control: tags -1 patch
Hello, I crafted a patch after finding that the culprit was the newer glslang 
11.12.0-1 uploaded in sid.
I just copy-pasted the new values into the array (why aren't exported into a 
public header file?)


Following what I consider to be a patch (at least it makes the package compile 
now)

diff -Nru libplacebo-4.208.0/debian/changelog 
libplacebo-4.208.0/debian/changelog
--- libplacebo-4.208.0/debian/changelog 2022-09-19 22:50:00.0 +
+++ libplacebo-4.208.0/debian/changelog 2022-12-03 09:06:24.0 +
@@ -1,3 +1,9 @@
+libplacebo (4.208.0-3) unstable; urgency=medium
+
+  * Fix build with newer glslang 11.12.0-1 (Closes: #1025363)
+
+ -- Gianfranco Costamagna   Sat, 03 Dec 2022 
10:06:24 +0100
+
 libplacebo (4.208.0-2) unstable; urgency=medium
 
   * Upload to unstable

diff -Nru libplacebo-4.208.0/debian/patches/new-glslang-11.12.0-build-fix.patch 
libplacebo-4.208.0/debian/patches/new-glslang-11.12.0-build-fix.patch
--- libplacebo-4.208.0/debian/patches/new-glslang-11.12.0-build-fix.patch   
1970-01-01 00:00:00.0 +
+++ libplacebo-4.208.0/debian/patches/new-glslang-11.12.0-build-fix.patch   
2022-12-03 09:06:23.0 +
@@ -0,0 +1,24 @@
+Description: Adapt to new glslang 11.12.0-1 Standalone/ResourceLimits.cpp 
exported resources
+Author: Gianfranco Costamagna 
+
+Bug-Debian: https://bugs.debian.org/1025363
+Last-Update: 2022-12-03
+
+--- libplacebo-4.208.0.orig/src/glsl/glslang.cc
 libplacebo-4.208.0/src/glsl/glslang.cc
+@@ -208,6 +208,15 @@ const TBuiltInResource DefaultTBuiltInRe
+ /* .maxTaskWorkGroupSizeY_NV = */ 1,
+ /* .maxTaskWorkGroupSizeZ_NV = */ 1,
+ /* .maxMeshViewCountNV = */ 4,
++/* .maxMeshOutputVerticesEXT = */ 256,
++/* .maxMeshOutputPrimitivesEXT = */ 256,
++/* .maxMeshWorkGroupSizeX_EXT = */ 128,
++/* .maxMeshWorkGroupSizeY_EXT = */ 128,
++/* .maxMeshWorkGroupSizeZ_EXT = */ 128,
++/* .maxTaskWorkGroupSizeX_EXT = */ 128,
++/* .maxTaskWorkGroupSizeY_EXT = */ 128,
++/* .maxTaskWorkGroupSizeZ_EXT = */ 128,
++/* .maxMeshViewCountEXT = */ 4,
+ /* .maxDualSourceDrawBuffersEXT = */ 1,
+
+ /* .limits = */ {
diff -Nru libplacebo-4.208.0/debian/patches/series 
libplacebo-4.208.0/debian/patches/series
--- libplacebo-4.208.0/debian/patches/series1970-01-01 00:00:00.0 
+
+++ libplacebo-4.208.0/debian/patches/series2022-12-03 09:05:30.0 
+
@@ -0,0 +1 @@
+new-glslang-11.12.0-build-fix.patch


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002964: marked as done (netpanzer: FTBFS with SCons 4.2.0+)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 09:06:08 +
with message-id 
and subject line Bug#1002964: fixed in netpanzer 0.8.7+ds-4.1
has caused the Debian Bug report #1002964,
regarding netpanzer: FTBFS with SCons 4.2.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.)


-- 
1002964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netpanzer
Version: 0.8.7+ds-4
Severity: important
Tags: patch

Hi,

SCons 4.3.0 was released some time ago. I've packaged it and would
like to upload it in the next day or so. Your package FTBFS with that,
for which a patch is attached to fix it.

Regards,
Laszlo/GCS
Description: SCons 4.2.0 no longer has env.has_key()
 Check env as an array.
Author: Laszlo Boszormenyi (GCS) 
Forwarded: no
Last-Update: 2022-01-01

---

--- netpanzer-0.8.7+ds.orig/SConstruct
+++ netpanzer-0.8.7+ds/SConstruct
@@ -237,7 +237,7 @@ npdirs = """
 """
 
 env.Append( NPSOURCES = globSources(env, 'src/NetPanzer', npdirs, "*.cpp") )
-if env.has_key('WINICON'):
+if 'WINICON' in env:
 env.Append( NPSOURCES = env['WINICON'] )
 
 env.Prepend( LIBS = ['np2d','lua5.1','npnetwork','nplibs','physfs'] )
--- End Message ---
--- Begin Message ---
Source: netpanzer
Source-Version: 0.8.7+ds-4.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated netpanzer 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, 20 Nov 2022 00:32:24 +0200
Source: netpanzer
Architecture: source
Version: 0.8.7+ds-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Adrian Bunk 
Closes: 1002964
Changes:
 netpanzer (0.8.7+ds-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from László Böszörményi to fix FTBFS with SCons >= 4.2.0.
 (Closes: #1002964)
Checksums-Sha1:
 6daf996457f9c295ef916d659a128ea9ee80 2141 netpanzer_0.8.7+ds-4.1.dsc
 d38c4083300043bbec3afda78a303d9570565cdd 11932 
netpanzer_0.8.7+ds-4.1.debian.tar.xz
Checksums-Sha256:
 e470530e1f0b0f91eed05dc8c5452f2a1f2332714e2ec53d7d75abf0fae25ece 2141 
netpanzer_0.8.7+ds-4.1.dsc
 44fd637be93027ff7f336474905dc077c7f545abeadc30169672934a4656bb18 11932 
netpanzer_0.8.7+ds-4.1.debian.tar.xz
Files:
 bc05e4b7c89733674fe5c6dcef15771a 2141 games optional netpanzer_0.8.7+ds-4.1.dsc
 a57b8e6487153b7b1f4b6245707f0e42 11932 games optional 
netpanzer_0.8.7+ds-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN5Wn8ACgkQiNJCh6LY
mLG5GA/9HSz9N5R58V/h6cCrwEN28S9NL65b3M4GYt4+7ulBxzyteVBA8pQfmeCN
pKjy9IWWDbkKtfXSrV/ogStI5GDUcLGgytVgARCCSAZghotGaNwuV+SCv7i9cT3S
g37ZOGNBOVgKFiDcuV6QTnIiKiTdhnbYC8FzhBTMzjV9v6rw6lORB7ThcSw6Da09
P7CTIBOuNQtpS/yln/yiri9t+cAl7ssklFr6VMuIpheB3VYrMzLwyJDQ89ZZYqFD
pxW8/o7ZfDf76J4XdPoX2z9Ak/+RVz0RbzHtpzl+RjvWNIFaBStVCUAY9drDTU5f
2o69jBZD1AXMpYe6cicSNv/mytr3f9LSTyM906JndeEXoh9u++DWqpxoVgBcWG+/
q2Y22n3eV8AlajTwP7zBKHi2lrfdUtreIEwba8zJEff78exda4/LZDQLj4NeK/7u
/u55ixbfI3eGFrNEN9QUNlNnSvaAMeEY8G27vkLxnL6vRnVaHaqkeWZV8v7ce1A4
wCIDRKx1IGFKLnO65LeM04U5/QeF7h0tfTTIhTpdDrZzEwYf5uAAMXMBVcu1nCbk
r9f8sJoO3JeNIEJLQtezYmlSMpJC8KYoNSb2RMoB3Gt4bzYuXucDajDQG3jjPscx
1UhlKGkDyR360dIcV/JFDs1ovOb6tbUd+gF2V5v5UYXpkUPsPho=
=cVXv
-END PGP SIGNATURE End Message ---

Bug#1022356: marked as done (netpanzer: FTBFS: AttributeError: 'SConsEnvironment' object has no attribute 'has_key':)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 09:06:08 +
with message-id 
and subject line Bug#1002964: fixed in netpanzer 0.8.7+ds-4.1
has caused the Debian Bug report #1002964,
regarding netpanzer: FTBFS: AttributeError: 'SConsEnvironment' object has no 
attribute 'has_key':
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.)


-- 
1002964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netpanzer
Version: 0.8.7+ds-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> chmod a-x pics/flags/karmapa.bmp
> scons datadir=/usr/share/games/netpanzer
> scons: Reading SConscript files ...
> /bin/sh: 1: svnversion: not found
> NPVERSION = 0.8.7
> SVERSION = 
> Building version 0.8.7 in linux
> AttributeError: 'SConsEnvironment' object has no attribute 'has_key':
>   File "/<>/SConstruct", line 240:
> if env.has_key('WINICON'):
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/netpanzer_0.8.7+ds-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

If you reassign this bug to another package, please 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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: netpanzer
Source-Version: 0.8.7+ds-4.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated netpanzer 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, 20 Nov 2022 00:32:24 +0200
Source: netpanzer
Architecture: source
Version: 0.8.7+ds-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Adrian Bunk 
Closes: 1002964
Changes:
 netpanzer (0.8.7+ds-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from László Böszörményi to fix FTBFS with SCons >= 4.2.0.
 (Closes: #1002964)
Checksums-Sha1:
 6daf996457f9c295ef916d659a128ea9ee80 2141 netpanzer_0.8.7+ds-4.1.dsc
 d38c4083300043bbec3afda78a303d9570565cdd 11932 
netpanzer_0.8.7+ds-4.1.debian.tar.xz
Checksums-Sha256:
 e470530e1f0b0f91eed05dc8c5452f2a1f2332714e2ec53d7d75abf0fae25ece 2141 
netpanzer_0.8.7+ds-4.1.dsc
 44fd637be93027ff7f336474905dc077c7f545abeadc30169672934a4656bb18 11932 
netpanzer_0.8.7+ds-4.1.debian.tar.xz
Files:
 bc05e4b7c89733674fe5c6dcef15771a 2141 games optional netpanzer_0.8.7+ds-4.1.dsc
 a57b8e6487153b7b1f4b6245707f0e42 11932 games optional 
netpanzer_0.8.7+ds-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN5Wn8ACgkQiNJCh6LY
mLG5GA/9HSz9N5R58V/h6cCrwEN28S9NL65b3M4GYt4+7ulBxzyteVBA8pQfmeCN
pKjy9IWWDbkKtfXSrV/ogStI5GDUcLGgytVgARCCSAZghotGaNwuV+SCv7i9cT3S
g37ZOGNBOVgKFiDcuV6QTnIiKiTdhnbYC8FzhBTMzjV9v6rw6lORB7ThcSw6Da09
P7CTIBOuNQtpS/yln/yiri9t+cAl7ssklFr6VMuIpheB3VYrMzLwyJDQ89ZZYqFD
pxW8/o7ZfDf76J4XdPoX2z9Ak/+RVz0RbzHtpzl+RjvWNIFaBStVCUAY9drDTU5f
2o69jBZD1AXMpYe6cicSNv/mytr3f9LSTyM906JndeEXoh9u++DWqpxoVgBcWG+/
q2Y22n3eV8AlajTwP7zBKHi2lrfdUtreIEwba8zJEff78exda4/LZDQLj4NeK/7u
/u55ixbfI3eGFrNEN9QUNlNnSvaAMeEY8G27vkLxnL6vRnVaHaqkeWZV8v7ce1A

Bug#1022181: marked as done (pygccjit: non-standard gcc used for build (gcc-10))

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2022 09:06:14 +
with message-id 
and subject line Bug#1022181: fixed in pygccjit 0.4-12.1
has caused the Debian Bug report #1022181,
regarding pygccjit: non-standard gcc used for build (gcc-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.)


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

Source: pygccjit
Severity: important
Version: 0.4-12

This package depends on a non-standard compiler version; on amd64,
this package can be built with libgccjit-12-dev, gcc-12.  If the
package cannot be built on any architecture with gcc-12 because
of a compiler bug, please file a report for gcc-12. Else, please
switch to gcc-12.
--- End Message ---
--- Begin Message ---
Source: pygccjit
Source-Version: 0.4-12.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pygccjit 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, 20 Nov 2022 01:51:51 +0200
Source: pygccjit
Architecture: source
Version: 0.4-12.1
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose 
Changed-By: Adrian Bunk 
Closes: 1022181
Changes:
 pygccjit (0.4-12.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Build using gcc 12. (Closes: #1022181)
Checksums-Sha1:
 ea35f30a839df69da9f729e4ee468d725b09a666 1888 pygccjit_0.4-12.1.dsc
 6368e9fee83c25224d18e99371f0c73d8fe13491 2788 pygccjit_0.4-12.1.debian.tar.xz
Checksums-Sha256:
 beb66b622f5877ffbcdada8b574af6ec29bd9d0e12712a3902d64d3c78241a3a 1888 
pygccjit_0.4-12.1.dsc
 03088216362d2821bdc1358cf902143ed4446443d436f9482296b27e6033b9d9 2788 
pygccjit_0.4-12.1.debian.tar.xz
Files:
 f31375d785e075edf3711801b0879e2e 1888 python optional pygccjit_0.4-12.1.dsc
 5b69e17a496a712ffe418c28b7ecb901 2788 python optional 
pygccjit_0.4-12.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN5bPAACgkQiNJCh6LY
mLFXhBAAhNX9Di7eZo4dArfYH6NswyUPessdqo3Bi4LzZ+EUEPgVujxw6C9T7KCx
x9JFDjzmS97W8sg6UaU/eu+OoK98G3lxupNxhkyLf50hPD5aLMnBgNFcL81xrwAX
2U0To/alhP/ZtliIXJ5WvT8aXY3Qf0nzj4z0jwkw+J1GTMKry7gp3CKy0BtHi/JL
jnKXNiu1TPByTtdjhGfQ0OZOkHDDBrlUd7mNL/8u8xzWvt9p6p9OEMmnIuUMc2GL
Id1uxjburTurCoqN1NMeQwODr58kA6IoyqF2jXioZDiz2h8oFLszsSoTMLvpgW4d
/KkDN314r47OxLJVUSlzv8UfVcEyOJj7O3pLFKOKvlhwITGWwngnxKRX0N08X2+Z
+duoemmKI9ShfBxuayiI1WbBUAiIGIIbz3bWtBVxZTi6lTSmVm6+TI0bbBZIQvwa
s7g4y7R18e1VjN1IsIg4yTlemjHvifOEt6s59F1Za3caiBUe1+OXYZ2/Jq6dzqqM
EnwM4s2Hv2DtR0wISYyfanioDX/V0OYaspfIII0GL682RT9Lve822ZNojRbj6ziL
2gehfzhB/CG+E8ErU6GDi+HqrrrUamTkVhZmdT8IXo++Ui/DSqGIV3HUr7nNd6Qu
b8Tt2e7jf5Xb8wWKVz3TLhe+pOKPbm+0of4WtDbBX4eQBTIzlxM=
=lUWo
-END PGP SIGNATURE End Message ---

Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

[Roelof Berg]

I agree, it’s also unmaintained. Let’s take it out.

Roelof
(Author and original packager)

Von meinem Mobiltelefon gesendet.

> Am 02.12.2022 um 10:38 schrieb Andreas Tille :
> 
> Am Thu, Dec 01, 2022 at 11:39:47PM +0200 schrieb Adrian Bunk:
>> [1] contains a patch from a Debian porter, but considering the facts 
>> that limereg already missed the current Debian stable bullseye and the 
>> comment from upstream (who is also the original Debian packager) in [2], 
>> removal from Debian might be a better option?
>> 
>> I do not know how limereg compares to other tools like for example
>> elastix (based on ITK) or registrationx (part of CMTK) or other tools,
>> but neither the upstream bug tracker nor the Debian BTS indicate that
>> there would be an active userbase who report bugs or complained that
>> limereg is not in bullseye.
> 
> I'll immediately ask for removal of this package.
> 
> Kind regards
> 
>  Andreas.
> 
>> [1] https://github.com/RoelofBerg/limereg/issues/3
>> [2] https://github.com/RoelofBerg/limereg/issues/3#issuecomment-1296863979
> 
> -- 
> http://fam-tille.de
> 

Processed: qutemol: Please transition to wxwidgets3.2

[Debian Bug Tracking System]

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

> severity 1019819 important
Bug #1019819 [src:qutemol] qutemol: Please transition to wxwidgets3.2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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