Bug#1000336: numba: FTBFS with Python 3.10

[Graham Inggs]

Hi Diane

On Mon, 21 Feb 2022 at 05:39, Diane Trout  wrote:
> It would... except numpy 1.22 just hit experimental on the 18th. and
> numba isn't compatible with numpy 1.22. I tried adding this to
> d/control,
>
> python3-numpy (<< 1.22),
>
> but my sbuild resolver still picked up numpy from experimental and
> refused to build.

That doesn't sound right.  You should be targeting experimental, but
still building against packages in unstable.  Something like this:

sbuild -d experimental -c unstable-amd64-sbuild ...

Regards
Graham

Bug#1005962: marked as done (dask: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Mon, 21 Feb 2022 07:33:44 +
with message-id 
and subject line Bug#1005962: fixed in dask 2022.01.0+dfsg-1
has caused the Debian Bug report #1005962,
regarding dask: FTBFS in testing
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.)


-- 
1005962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dask
Version: 2021.09.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:python-sparse

Hi Maintainer

Python-sparse was removed from testing in order to advance the Python
3.10 transition (#996584).  Dask has a  build-dependency on
python3-sparse, so currently FTBFS in testing.

Please consider (temporarily) dropping this dependency.

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2022.01.0+dfsg-1
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated dask 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 Feb 2022 17:11:53 -0800
Source: dask
Architecture: source
Version: 2022.01.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Diane Trout 
Closes: 1005962
Changes:
 dask (2022.01.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * split tests/control Tests-Command: into a separate shell script
   * Add sphinx-remove-toctree and sphinx-tabs to build-depends
   * add 32-bit compatibility patch for pandas 1.3
 See https://github.com/dask/dask/issues/8169
   * Copy conftest.py into test directory for autopkgtests
   * Add python3-ipython as a build-dependency.
 - it provides a sphinx formatting extension.
   * Add patch pytest-futurewarning.patch for compatibility with our pytest
   * Disable python3-sparse for tests since numba is broken (Closes: #1005962)
Checksums-Sha1:
 b3580bbd7d09c69c74cc786c58beaf402419a4c8 3035 dask_2022.01.0+dfsg-1.dsc
 25d1c26bcb5734db6d1fdc5f3818201275caf466 4293312 
dask_2022.01.0+dfsg.orig.tar.xz
 6c0f263157ac2a442446ab888d62c5d0a9960bf8 23196 
dask_2022.01.0+dfsg-1.debian.tar.xz
 2339e1779bad9b23f64e26b1dc7bc7ee6890e71e 9792 
dask_2022.01.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 2fd7db2e7e1d74b6b086d6f8199e58cec107cf8057e8c8531f02a66304c954a6 3035 
dask_2022.01.0+dfsg-1.dsc
 77f81416b9e618cb33bd038679fec36371bf7c5796c9234d7de1f605ffe56bd9 4293312 
dask_2022.01.0+dfsg.orig.tar.xz
 592aa9a388583925a637b999fd6892ea1fe46f9d0f263c19642e7310846dd530 23196 
dask_2022.01.0+dfsg-1.debian.tar.xz
 3c6c76a3dfbf711af73a27a4e7e067d411514993beead84482714f4847033e35 9792 
dask_2022.01.0+dfsg-1_amd64.buildinfo
Files:
 5a86097e9f5ef567a375d8005f65eb21 3035 python optional dask_2022.01.0+dfsg-1.dsc
 0a5d2b5586b156df2e522f066bb64bd0 4293312 python optional 
dask_2022.01.0+dfsg.orig.tar.xz
 719a09437f49571ae1cc96fc93396c00 23196 python optional 
dask_2022.01.0+dfsg-1.debian.tar.xz
 ec55607466dfc5e725c8c4f3de113134 9792 python optional 
dask_2022.01.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAmITPL8ACgkQmQ04NnM0
13Dk+xAApKbiomlfBZW6ijEXYgjNAPzS1R0LoizKgtBsKCshDo6XwLKGsy/Be9DF
cGm3oDVPrTM8OfOTOckWo33qQxR19uoFH9Uerrn7AqcPd4rCpFbKH0Vu/YR5Ulim
S26Zp3CY9lfSkMTYvHGKuCVDIpjoJd/Oxxn8utUmUvG/YBtlp0dIAUmyP6w3teBr
OTevQ9Vl0kU/Y6etyrbo/6uno/7rkRPjvwZfGC6JO73kUECpfxLqiweneOSq/9V5
oVswj7+zmrIavKmndU5r9CNF487V7QFaIuVmEo9QUOGKClb8ILFiq2MKfMvzhyGs
YliT1fN40elzOBRNXaK0NLdBUQ5XO288Af6Kd05NW3r+fHaJ2Sv6y0udgoiA4Yr2
0DGfNqyhrtmmkWff7K6DOpPZwDQmojgTz7Wbi3+vVQ03jk+Uhoig8Ai/ILTtBJtN
Y9LU059xyZ1/XPF8Fx+OlvXESVtUtvctz5ihHr2TsrjTn5aWUo7bGZkcPGSqf3VJ
MCaKvDLGjG6SIEYul6WBQYI/WRQRiuuj7VwTLz8brx5YDkvJrk/1+an5dmH7IWf7
ltpM8BE/YIoAMg0b3ASrD+w6vTP9E1PFK4xhcXOOshLHFh/ncTGXp7JiKxns6STf
Z49sKjzYQyL0MZeEjowBllF+K0eSp+kqy9RRLfRkAw4IEUFGcZI=
=VcSo
-END PGP SIGNATURE End Message ---

Bug#1005230: Does chromium REALLY need fuse now?

[Trent W. Buck]

Trent W. Buck wrote:
> The error report for #1005230 only specifically mentioned GTK3.
> Are these other "portal" dependencies *really* needed now?

As at chromium 98.0.4758.102-1~deb11u1,
chromium works with xdg-desktop-portal, fuse, flatpak removed.

A minimal test script is attached.
it builds & boots a Debian 11 Live VM without chromium.
You can then launch chromium,
browse to https://example.com, Ctrl+S save and Ctrl+O open.

I'm not sure what other tests are needed.
Can I do anything else to help with this ticket?
#!/usr/bin/python3
import subprocess
import tempfile

__doc__ = """ test chrome w/o fuse

log in as "x", run chromium, browse to https://example.museum/, Ctrl+S Enter to save.
See that saving works even with xdg-desktop-portal/flatpak/fuse removed.

NOTE: kvm's default geometry is 800x600 or something.
  GTK3's default save dialog does not fit.
  Try resizing the KVM window before lightdm starts.
"""

with tempfile.TemporaryDirectory() as td:
subprocess.check_call(
['mmdebstrap',
 '--include=linux-image-generic,live-boot,chromium,task-xfce-desktop,sudo',
 # f'--aptopt=Acquire::http::Proxy "http://localhost:3142;',
 '--customize-hook=chroot $1 adduser x --gecos x --disabled-password --quiet',
 '--customize-hook=chroot $1 adduser x sudo',
 '--customize-hook=echo x: | chroot $1 chpasswd --crypt-method=NONE',
 '--customize-hook=download vmlinuz vmlinuz',
 '--customize-hook=download initrd.img initrd.img',

 # Remove things that chromium claims it needs but does not actually need.
 '--customize-hook=chroot $1 dpkg --force-depends --purge xdg-desktop-portal xdg-desktop-portal-backend xdg-desktop-portal-gtk fuse libfuse2 fuse3 libfuse3-3 bubblewrap flatpak libgnome-desktop-3-19',

 # Report which version of chromium we are running.
 '--customize-hook=chroot $1 dpkg-query -W chromium',
 'bullseye',
 'filesystem.squashfs'],
cwd=td)
subprocess.check_call(
['kvm',
 '-m', '2G',
 '--device', 'virtio-vga',
 '--kernel', 'vmlinuz',
 '--initrd', 'initrd.img',
 '--append', 'boot=live plainroot root=/dev/vda quiet',
 '--drive', f'file=filesystem.squashfs,format=raw,media=disk,if=virtio,readonly=on'],
cwd=td)
bash5$ python3 POC-chromium-without-fuse.py
I: automatically chosen mode: unshare
I: chroot architecture amd64 is equal to the host's architecture
I: automatically chosen format: squashfs
I: using /tmp/mmdebstrap.YvkchFlb0y as tempdir
W: tar2sqfs does not support extended attributes from the 'system' namespace
I: running apt-get update...
done
I: downloading packages with apt...
done
I: extracting archives...
done
I: installing essential packages...
done
I: downloading apt...
done
I: installing apt...
done
I: installing remaining packages inside the chroot...
done
done
done
done
done
I: running --customize-hook in shell: sh -c 'chroot $1 adduser x --gecos x 
--disabled-password --quiet' exec /tmp/mmdebstrap.YvkchFlb0y
I: running --customize-hook in shell: sh -c 'chroot $1 adduser x sudo' exec 
/tmp/mmdebstrap.YvkchFlb0y
Adding user `x' to group `sudo' ...
Adding user x to group sudo
Done.
I: running --customize-hook in shell: sh -c 'echo x: | chroot $1 chpasswd 
--crypt-method=NONE' exec /tmp/mmdebstrap.YvkchFlb0y
I: running special hook: download vmlinuz vmlinuz
I: running special hook: download initrd.img initrd.img
I: running --customize-hook in shell: sh -c 'chroot $1 dpkg --force-depends 
--purge xdg-desktop-portal xdg-desktop-portal-backend xdg-desktop-portal-gtk 
fuse libfuse2 fuse3 libfuse3-3 bubblewrap flatpak libgnome-desktop-3-19' exec 
/tmp/mmdebstrap.YvkchFlb0y
dpkg: warning: ignoring request to remove xdg-desktop-portal-backend which 
isn't installed
dpkg: warning: ignoring request to remove fuse3 which isn't installed
dpkg: warning: ignoring request to remove libfuse3-3 which isn't installed
dpkg: warning: ignoring request to remove flatpak which isn't installed
dpkg: libgnome-desktop-3-19:amd64: dependency problems, but removing anyway as 
you requested:
 xdg-desktop-portal-gtk depends on libgnome-desktop-3-19 (>= 3.17.92).

(Reading database ... 31385 files and directories currently installed.)
Removing libgnome-desktop-3-19:amd64 (3.38.5-3) ...
dpkg: xdg-desktop-portal: dependency problems, but removing anyway as you 
requested:
 xdg-desktop-portal-gtk depends on xdg-desktop-portal (>= 1.7.1).

Removing xdg-desktop-portal (1.8.1-1) ...
dpkg: xdg-desktop-portal-gtk: dependency problems, but removing anyway as you 
requested:
 chromium depends on xdg-desktop-portal-gtk | xdg-desktop-portal-backend; 
however:
  Package xdg-desktop-portal-gtk is to be removed.
  Package xdg-desktop-portal-backend is not installed.
  Package xdg-desktop-portal-gtk which provides xdg-desktop-portal-backend is 
to be removed.
 chromium depends on xdg-desktop-portal-gtk | xdg-desktop-portal-backend; 
however:
  

Bug#1005230: Does chromium REALLY need fuse now?

[Trent W. Buck]

Package: chromium
Followup-For: Bug #1005230

Hi, I ship chromium in prisons, where we extremely do not want
unprivileged users to be able to add new drivers (fuse) and
applications (flatpak/bubblewrap/xdg-desktop-portal). [*]

The fix for #1005230 added indirect dependencies on fuse and bubblewrap.

The error report for #1005230 only specifically mentioned GTK3.
Are these other "portal" dependencies *really* needed now?

If they are needed, I can deal with it.
If they aren't needed, is it feasible to define the hard dependencies more 
precisely?
Or downgrade xdg-desktop-portal to a Recommends?

(I repackage a few things in-house like linux and vlc, but
I'm frankly too scared to try that with chromium.)


As a sanity-check, I see that libwebkit2gtk-4.0-37 needs bubblewrap (but not 
fuse), and
firefox-esr needs neither.



[*] I have a bunch of other layers to block these, but
"libfuse* isn't even installed" is really nice layer to have.
e.g. detainee kernels have CONFIG_FUSE_FS disabled
(though CONFIG_USER_NS is enabled due to systemd).


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

Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 chromium-common depends on:
ii  libc6   2.31-13+deb11u2
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.2-1
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
pn  chromium-sandbox   
ii  fonts-liberation   1:1.07.4-11
ii  gnome-shell [notification-daemon]  3.38.6-1~deb11u1
ii  libgl1-mesa-dri20.3.5-1
ii  libu2f-udev1.1.10-3
ii  notification-daemon3.20.0-4
ii  system-config-printer  1.5.14-1
ii  upower 0.99.11-2

Processed: tagging 1006038 ...

[Debian Bug Tracking System]

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

> tags 1006038 + fixed-upstream patch
Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: 
make -j8 test returned exit code 2
Added tag(s) fixed-upstream and patch.
> forwarded 1006038 
> https://github.com/mnauw/git-remote-hg/commit/949345fb115bcead02194f84287d54941fa2b0d9
>  https://github.com/mnauw/git-remote-hg/issues/48
Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: 
make -j8 test returned exit code 2
Changed Bug forwarded-to-address to 
'https://github.com/mnauw/git-remote-hg/commit/949345fb115bcead02194f84287d54941fa2b0d9
 https://github.com/mnauw/git-remote-hg/issues/48' from 
'https://github.com/mnauw/git-remote-hg/issues/48'.
> thanks
Stopping processing here.

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

Bug#1006141: supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'

[Peter Michael Green]

Tags 1006141 +patch
thanks

This was fixed in ubuntu a few months ago by adding ".fpu vfp" to the 
assembler file in question.
(within the block of code that is only used on systems with the hard 
float ABI).


https://patches.ubuntu.com/s/supertuxkart/supertuxkart_1.3+dfsg1-2ubuntu1.patch

I have just built the same fix successfully in raspbian bookworm-staging 
and uploaded it
to raspbian. I haven't tested it in Debian myself but I'd be extremely 
surprised if it doesn't work.

Processed: re: supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'

[Debian Bug Tracking System]

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

> Tags 1006141 +patch
Bug #1006141 [src:supertuxkart] supertuxkart: FTBFS on armhf: Error: selected 
FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1006172: [Pkg-electronics-devel] Bug#1006172: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

[Bdale Garbee]

Paul Gevers  writes:

> Your package fails to build on s390x where it build successfully in
> the past. I've X-Debbugs-CC-ed the s390x porters to help you
> understand why only this architecture is affected.

It's hard to imagine anyone actually trying to use lepton-eda on s390x.
If the porting team for that architecture wants to figure this out,
that's great, but I'd personally be completely comfortable having the
s390x binaries removed from the archive to allow fresher lepton-eda to
migrate to testing.

Bdale


signature.asc
Description: PGP signature

Bug#1000336: numba: FTBFS with Python 3.10

[Diane Trout]

On Sat, 2022-02-19 at 11:02 +0100, Drew Parsons wrote:
> Source: numba
> Followup-For: Bug #1000336
> 
> onetbb is now building (in experimental) for all arches except
> armel and armhf.
> 
> Is it worth at this point to make an upload of numba 0.55 to
> experimental to check that it's building and passing tests for the
> other arches?

It would... except numpy 1.22 just hit experimental on the 18th. and
numba isn't compatible with numpy 1.22. I tried adding this to
d/control, 

python3-numpy (<< 1.22),

but my sbuild resolver still picked up numpy from experimental and
refused to build.

Upstream has a meta bug with the numpy 1.22 issues.
https://github.com/numba/numba/issues/7754

Bug#1002402: python-sparse: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Diane Trout]

On Mon, 2022-02-21 at 02:24 +, Peter Michael Green wrote:
> > During a rebuild of all packages in sid, your package failed to
> > build
> > on amd64.
>  
>  I'm no expert on this particular package, but this looks to me like
> it is not actually caused by a problem in python-sparse, but is
> instead a symptom of python3-numba not being built against python
> 3.10 due to 
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000336
>  

Yep that was my interpretation as well.

Numba 0.55.1 needs libtbb-dev > 2021.04, and 2021.05 is in experimental
getting some weird architectures tested. However libtbb is going to
need a transition.

Unfortunately numpy 0.55.1 breaks with numpy 1.22 which is also in
experimental

Diane

Bug#1003470: openimageio FTBFS: invalid preprocessing directive #errorDCMTK

[Jeremy Bicha]

In Ubuntu, we fixed this issue by building with C++17.

You can find a diff of the rules file at
https://launchpad.net/ubuntu/+source/openimageio/2.2.18.0+dfsg-1ubuntu1

This is needed to complete the libwebp transition:
https://release.debian.org/transitions/html/auto-libwebp.html

Thank you,
Jeremy Bicha

Bug#1002402: python-sparse: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Peter Michael Green]

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


I'm no expert on this particular package, but this looks to me like it 
is not actually caused by a problem in python-sparse, but is instead a 
symptom of python3-numba not being built against python 3.10 due to

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

Processed: closing 886145

[Debian Bug Tracking System]

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

> close 886145 0.99.2-2
Bug #886145 [src:shutter] shutter: Don't recommend libgoo-canvas-perl
Marked as fixed in versions shutter/0.99.2-2.
Bug #886145 [src:shutter] shutter: Don't recommend libgoo-canvas-perl
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 870418

[Debian Bug Tracking System]

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

> close 870418 0.99.2-2
Bug #870418 [shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will 
go away during the Buster cycle
Marked as fixed in versions shutter/0.99.2-2.
Bug #870418 [shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will 
go away during the Buster cycle
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1006196: mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory

[Simon McVittie]

On Sun, 20 Feb 2022 at 23:59:14 +, Simon McVittie wrote:
> I tried building mozjs on the mips(64)el porterbox 'eller' to test my
> earlier commit that resolved a build failure, and it now fails on eller
> with a test failure instead:
...
>  FAILED!  integer overflow in js : Expected value 'InternalError: allocation 
> size overflow', Actual value 'out of memory'

I'm testing a possible patch.

smcv

Processed: Re: Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1755531
Bug #1006152 [src:mozjs91] mozjs91: FTBFS on i386: 
test262/built-ins/Date/UTC/fp-evaluation-order.js
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1755531'.

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

Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

[Simon McVittie]

Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1755531

On Sat, 19 Feb 2022 at 22:38:34 +, Simon McVittie wrote:
> After applying patches to fix compilation on i386 and mipsel (see commits
> 3f0f229d, 585dadd4) there is a test failure unresolved on i386:
> 
> ## test262/built-ins/Date/UTC/fp-evaluation-order.js: rc = 3, run time = 
> 0.022397
> /home/smcv/mozjs/js/src/tests/test262/shell.js:415:9 uncaught exception: 
> Test262Error: order of operations / precision in MakeTime Expected 
> SameValue(«29256», «29312») to be true
> Stack:
>   Test262Error.thrower@/home/smcv/mozjs/js/src/tests/test262/shell.js:415:9
>   assert.sameValue@/home/smcv/mozjs/js/src/tests/test262/shell.js:51:9
>   
> @/home/smcv/mozjs/js/src/tests/test262/built-ins/Date/UTC/fp-evaluation-order.js:19:8
> TEST-UNEXPECTED-FAIL | test262/built-ins/Date/UTC/fp-evaluation-order.js | 
> (args: "") [0.0 s]

I think this is the same thing Marco reported in
.

I'm testing a patch (basically just extending Marco's workaround to
apply to i386 too). If successful, I'll downgrade the severity of this bug
but leave it open.

smcv

Processed: closing 973059

[Debian Bug Tracking System]

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

> close 973059 1.9-1
Bug #973059 [src:logging-tree] logging-tree: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Marked as fixed in versions logging-tree/1.9-1.
Bug #973059 [src:logging-tree] logging-tree: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unarchiving 870418, reopening 870418, unarchiving 886145, reopening 886145, unarchiving 724871 ...

[Debian Bug Tracking System]

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

> # src:shutter was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 870418
Bug #870418 {Done: Debian FTP Masters } 
[shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will go away 
during the Buster cycle
Unarchived Bug 870418
> reopen 870418
Bug #870418 {Done: Debian FTP Masters } 
[shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will go away 
during the Buster cycle
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 886145
Bug #886145 {Done: Debian FTP Masters } 
[src:shutter] shutter: Don't recommend libgoo-canvas-perl
Unarchived Bug 886145
> reopen 886145
Bug #886145 {Done: Debian FTP Masters } 
[src:shutter] shutter: Don't recommend libgoo-canvas-perl
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 724871
Bug #724871 {Done: Debian FTP Masters } 
[shutter] shutter: Will be removed with todays update within Debian/testing
Unarchived Bug 724871
> reopen 724871
Bug #724871 {Done: Debian FTP Masters } 
[shutter] shutter: Will be removed with todays update within Debian/testing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 755278
Bug #755278 {Done: Debian FTP Masters } 
[shutter] shutter: Ram usage
Unarchived Bug 755278
> reopen 755278
Bug #755278 {Done: Debian FTP Masters } 
[shutter] shutter: Ram usage
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 872855
Bug #872855 {Done: Debian FTP Masters } 
[shutter] shutter: Shutter hangs gnome desktop environment when capture
Unarchived Bug 872855
> reopen 872855
Bug #872855 {Done: Debian FTP Masters } 
[shutter] shutter: Shutter hangs gnome desktop environment when capture
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 551891
Bug #551891 {Done: Debian FTP Masters } 
[shutter] shutter: Cannot capture from multi-monitor
Unarchived Bug 551891
> reopen 551891
Bug #551891 {Done: Debian FTP Masters } 
[shutter] shutter: Cannot capture from multi-monitor
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 588277
Bug #588277 {Done: Debian FTP Masters } 
[shutter] shutter is placed in utilities menu instead of graphics
Unarchived Bug 588277
> reopen 588277
Bug #588277 {Done: Debian FTP Masters } 
[shutter] shutter is placed in utilities menu instead of graphics
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 717220
Bug #717220 {Done: Debian FTP Masters } 
[shutter] shutter: Text is readable under Pixelizer (has less than 100% opacity)
Unarchived Bug 717220
> reopen 717220
Bug #717220 {Done: Debian FTP Masters } 
[shutter] shutter: Text is readable under Pixelizer (has less than 100% opacity)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 761058
Bug #761058 {Done: Debian FTP Masters } 
[shutter] shutter: GLib-CRITICAL **: Source ID 29 was not found when attempting 
to remove it at /usr/bin/shutter line 7247
Unarchived Bug 761058
> reopen 761058
Bug #761058 {Done: Debian FTP Masters } 
[shutter] shutter: GLib-CRITICAL **: Source ID 29 was not found when attempting 
to remove it at /usr/bin/shutter line 7247
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.94-1+rm.
> unarchive 764011
Bug #764011 {Done: Debian FTP Masters } 
[shutter] fails to capture with Unexpected short read from authority file
Unarchived Bug 764011
> reopen 764011
Bug #764011 {Done: Debian FTP Masters } 
[shutter] fails to capture with Unexpected short read from authority file
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may 

Processed: unarchiving 973059, reopening 973059

[Debian Bug Tracking System]

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

> # src:logging-tree was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 973059
Bug #973059 {Done: Debian FTP Masters } 
[src:logging-tree] logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.8" returned exit code 13
Unarchived Bug 973059
> reopen 973059
Bug #973059 {Done: Debian FTP Masters } 
[src:logging-tree] logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.8" returned exit code 13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.8.1-0.1+rm.
> thanks
Stopping processing here.

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

Bug#1006196: mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory

[Simon McVittie]

Source: mozjs91
Version: 91.6.0-1
Severity: serious
Tags: ftbfs

I tried building mozjs on the mips(64)el porterbox 'eller' to test my
earlier commit that resolved a build failure, and it now fails on eller
with a test failure instead:

## non262/regress/regress-303213.js: rc = 0, run time = 0.147349
BUGNUMBER: 303213
STATUS: integer overflow in js
STATUS: This bug passes if no crash occurs
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 0 ---
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 5 ---
STATUS: done generating
 FAILED!  integer overflow in js : Expected value 'InternalError: allocation 
size overflow', Actual value 'out of memory'
TEST-UNEXPECTED-FAIL | non262/regress/regress-303213.js | (args: "") [0.1 s]

I think some other tests have already been adjusted to accept either of
these messages as being OK?

smcv

Processed: reassign 996706 to mariadb-server-core-10.6, reassign 993219 to mariadb-server-core-10.6 ...

[Debian Bug Tracking System]

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

> reassign 996706 mariadb-server-core-10.6 1:10.6.5-1
Bug #996706 [mariadb-server-core] mariadb-server-10.5: run directory is not 
created in multi-instance mode
Warning: Unknown package 'mariadb-server-core'
Bug reassigned from package 'mariadb-server-core' to 'mariadb-server-core-10.6'.
No longer marked as found in versions 1.10.6.5-1.
Ignoring request to alter fixed versions of bug #996706 to the same values 
previously set
Bug #996706 [mariadb-server-core-10.6] mariadb-server-10.5: run directory is 
not created in multi-instance mode
Marked as found in versions mariadb-10.6/1:10.6.5-1.
> reassign 993219 mariadb-server-core-10.6 1:10.6.5-1
Bug #993219 [mariadb-server-core] mariadb-server-core: Akonadi database - 
mysql_upgrade fails always with "FATAL ERROR: Can't execute 'mysqlcheck'"
Warning: Unknown package 'mariadb-server-core'
Bug reassigned from package 'mariadb-server-core' to 'mariadb-server-core-10.6'.
No longer marked as found in versions 1.10.6.5-1.
Ignoring request to alter fixed versions of bug #993219 to the same values 
previously set
Bug #993219 [mariadb-server-core-10.6] mariadb-server-core: Akonadi database - 
mysql_upgrade fails always with "FATAL ERROR: Can't execute 'mysqlcheck'"
Marked as found in versions mariadb-10.6/1:10.6.5-1.
> reassign 1005898 src:java-common
Bug #1005898 [java] java: The package "java" should exist, and it should 
install default-jre.
Warning: Unknown package 'java'
Bug reassigned from package 'java' to 'src:java-common'.
Ignoring request to alter found versions of bug #1005898 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1005898 to the same values 
previously set
> tags 1005898 - newcomer
Bug #1005898 [src:java-common] java: The package "java" should exist, and it 
should install default-jre.
Removed tag(s) newcomer.
> found 1006170 1.3.5+dfsg-2
Bug #1006170 [python3-pandas,python3-fsspec] pandas tests fail with new fsspec
There is no source info for the package 'python3-fsspec' at version 
'1.3.5+dfsg-2' with architecture ''
Marked as found in versions pandas/1.3.5+dfsg-2.
> tags 1006170 + sid bookworm
Bug #1006170 [python3-pandas,python3-fsspec] pandas tests fail with new fsspec
Added tag(s) bookworm and sid.
> found 1006170 2022.01.0-1
Bug #1006170 [python3-pandas,python3-fsspec] pandas tests fail with new fsspec
There is no source info for the package 'python3-pandas' at version 
'2022.01.0-1' with architecture ''
Marked as found in versions fsspec/2022.01.0-1.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1005977 normal
Bug #1005977 [fwupd] fwupd: Cannot update anymore, fwupdx64.efi... cannot be 
found
Severity set to 'normal' from 'grave'
>
End of message, stopping processing here.

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

Bug#1000928: marked as done (codelite: Please upgrade to llvm-toolchain-12 or 13)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 23:03:39 +
with message-id 
and subject line Bug#997219: fixed in codelite 14.0+dfsg-2
has caused the Debian Bug report #997219,
regarding codelite: Please upgrade to llvm-toolchain-12 or 13
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.)


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -13 (or -12).

Bookworm won't ship with llvm-toolchain-11

llvm-defaults is now pointing to -13.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: codelite
Source-Version: 14.0+dfsg-2
Done: Håvard F. Aasen 

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated codelite 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 Feb 2022 22:09:27 +0100
Source: codelite
Architecture: source
Version: 14.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard F. Aasen 
Closes: 997219 1000928
Changes:
 codelite (14.0+dfsg-2) unstable; urgency=medium
 .
   * QA upload.
   * Refresh patches using quilt.
   * Add patch from upstream to fix FTBFS with Hunspell and GCC-11.
 Closes: #997219
   * Rebuild for llvm. Closes: #1000928
   * d/rules:
 - Remove CMake options regarding clang, the options are
   no longer recognised.
 - Remove '--as-needed' flag, used by default.
 - No longer needed to specify include and library path for LLVM.
   * Update architectures to build with liblldb-dev.
   * Remove renamed and unused lintian tag for codelit.
   * d/watch: Bump to version 4.
   * Remove duplicated debhelper dependency.
   * Add upstream metadata:: Bug-Database, Bug-Submit, Repository
 and Repository-Browse.
   * Update architectures for llvm and libclang-dev.
   * Remove unused lintian override for package codelite-plugins.
Checksums-Sha1:
 d28bc8dab1b416b68084402c06021f5fb868ca55 2323 codelite_14.0+dfsg-2.dsc
 cc757add6adea1dfe74f0afaa451b7102b769e03 23576 
codelite_14.0+dfsg-2.debian.tar.xz
 7c748e9d39153bdd8d23cba4fe6092e18452645d 15291 
codelite_14.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 059e2762fb8e126590c96920d6ad309e7ee693911dce3687739b6d834c7fa63c 2323 
codelite_14.0+dfsg-2.dsc
 cb79ed3a449d049ed075d3a1271812bae6557c188e2da080dd7d2f4f5ea8507e 23576 
codelite_14.0+dfsg-2.debian.tar.xz
 366e67995d56b176594564565796196e21722103f2e92d5cca2bf916565664b1 15291 
codelite_14.0+dfsg-2_source.buildinfo
Files:
 80648bf253597c13ff4c3105283e93b7 2323 devel optional codelite_14.0+dfsg-2.dsc
 6c50044ce2408b02ab8b9a97e524750c 23576 devel optional 
codelite_14.0+dfsg-2.debian.tar.xz
 6ba4859d253ba556bb73c1832652ba98 15291 devel optional 
codelite_14.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmISxZYACgkQweDZLphv
fH6tHBAAjGR6cde7fQZIxSvGnl1n8sM2ReGV0BbbBdliKYQaLVz+AuG0YoUWOjcS
5j/upQcrJ9PTfJZPiXo1BimYwWsjz8tA22hg9yJIcINPa3umP/p6YAvwoIHUxW5F
1Fa8gyxqGQ8cj5AtG6c45u+KBX3I3lTPkE2afRoF3XJhU4dFFKzG0QTXv6WdrsnM
WKqo2BudK3+pCuFrvvMclB4tPsad52LGJgQDehr9YjCAQUOpuk523J+XVVwRKkmD
J4j/bpSkz/8z8ya2py3YkNtll0DMSZYPFJeLfYEgioZqyQ57X/HdvsIBQA6sm0YF
FnYOmbR1UbPp7hwWMJxdJz48DdqDW2GYHwKDM7Ivavh96cNsCFRKUufh9zShbcDm
LrkQe8z+zXFalzfSNtJsdkzjXV73BWgxavF1U+ZKzhCClSMO7ilWw1Sj9xYsuzNW
mW4GN48IiYDF5OzwiJBLAhM+OMNubLwAq4F81VStLWi3fE3BwCQxgCdnU77pwOrJ
uQOUT3p0YRZ49WzyX5nkQSkFZJTrUoiWC8FUlOxiZr3uvZUQFJt/EBqfqd5GILou
ZFbHLbiRG4t7C6uQckUkeN2Fx8yFJ0XzjGAuFSiMORdMPvDnehM3C1WjTlvDoKPo
OZVAcbIVkZPvXql8y9rFDJnQFpeIlYykHkLhk+99j9ErHh2RoHo=
=UOZA
-END PGP SIGNATURE End Message ---

Bug#997219: marked as done (codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value = wxString; _Hash = IHu

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 23:03:39 +
with message-id 
and subject line Bug#997219: fixed in codelite 14.0+dfsg-2
has caused the Debian Bug report #997219,
regarding codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function 
‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value 
= wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’
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.)


-- 
997219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codelite
Version: 14.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/ZoomNavigator && /usr/bin/c++ 
> -DINSTALL_DIR=\"/usr/share/codelite\" -DNDEBUG 
> -DPLUGINS_DIR=\"/usr/lib/codelite\" -DUSE_AUI_NOTEBOOK=0 -DUSE_SFTP=1 
> -DWXUSINGDLL -DWXUSINGDLL_CL -DWXUSINGDLL_SDK -DWXUSINGDLL_WXSQLITE3 
> -DYY_NEVER_INTERACTIVE=1 -DZoomNavigator_EXPORTS -D_FILE_OFFSET_BITS=64 
> -D__WXGTK__ -DwxUSE_GUI=1 -I/usr/include/gtk-3.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 
> -I/<>/Plugin -I/<>/sdk/wxsqlite3/include 
> -I/<>/CodeLite -I/<>/PCH 
> -I/<>/Interfaces -isystem 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem 
> /usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-deprecated-declarations -isystem 
> /usr/include/harfbuzz -std=c++11 -O2 -pthread -fPIC -fPIC -MD -MT 
> ZoomNavigator/CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o
>  -MF 
> CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o.d -o 
> CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o -c 
> /<>/ZoomNavigator/zoom_navigator_zoomnavigator_bitmaps.cpp
> /<>/SpellChecker/IHunSpell.cpp: In constructor 
> ‘IHunSpell::IHunSpell()’:
> /<>/SpellChecker/IHunSpell.cpp:67:17: error: use of deleted 
> function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() 
> [with _Value = wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
> IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’
>67 | m_scanners(0)
>   | ^
> In file included from /usr/include/c++/11/unordered_set:47,
>  from /<>/CodeLite/wxStringHash.h:4,
>  from /<>/CodeLite/file_logger.h:34,
>  from /<>/SpellChecker/IHunSpell.cpp:39:
> /usr/include/c++/11/bits/unordered_set.h:135:7: note: 
> ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with 
> _Value = wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
> IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’ is 
> implicitly deleted because the default definition would be ill-formed:
>   135 |   unordered_set() = default;
>   |   ^
> /usr/include/c++/11/bits/unordered_set.h:135:7: error: use of deleted 
> function ‘std::_Hashtable<_Key, _Value, _Alloc, _ExtractKey, _Equal, _Hash, 
> _RangeHash, _Unused, _RehashPolicy, _Traits>::_Hashtable() [with _Key = 
> wxString; _Value = wxString; _Alloc = std::allocator; _ExtractKey = 
> std::__detail::_Identity; _Equal = IHunSpell::StringCompareOptionalCase; 
> _Hash = IHunSpell::StringHashOptionalCase; _RangeHash = 
> std::__detail::_Mod_range_hashing; _Unused = 
> std::__detail::_Default_ranged_hash; _RehashPolicy = 
> std::__detail::_Prime_rehash_policy; _Traits = 
> std::__detail::_Hashtable_traits]’
> In file included from /usr/include/c++/11/unordered_set:46,
>  from /<>/CodeLite/wxStringHash.h:4,
>  from /<>/CodeLite/file_logger.h:34,
>  from /<>/SpellChecker/IHunSpell.cpp:39:
> /usr/include/c++/11/bits/hashtable.h:527:7: note: ‘std::_Hashtable<_Key, 
> _Value, _Alloc, _ExtractKey, _Equal, _Hash, _RangeHash, _Unused, 
> _RehashPolicy, _Traits>::_Hashtable() [with _Key = wxString; _Value = 
> wxString; _Alloc = std::allocator; _ExtractKey = 
> std::__detail::_Identity; _Equal = IHunSpell::StringCompareOptionalCase; 
> _Hash = IHunSpell::StringHashOptionalCase; _RangeHash = 
> std::__detail::_Mod_range_hashing; _Unused = 
> std::__detail::_Default_ranged_hash; _RehashPolicy = 

Bug#984159: marked as done (gnubiff: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 23:03:52 +
with message-id 
and subject line Bug#984159: fixed in gnubiff 2.2.17-4
has caused the Debian Bug report #984159,
regarding gnubiff: ftbfs with GCC-11
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.)


-- 
984159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnubiff
Version: 2.2.17-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gnubiff_2.2.17-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  273 | GMutex *g_mutex_new (void);
  | ^~~
mailbox.cc:64:39: warning: ‘GMutex* g_mutex_new()’ is deprecated 
[-Wdeprecated-declarations]
   64 | monitor_mutex_ = g_mutex_new ();
  |   ^
In file included from /usr/include/glib-2.0/glib.h:111,
 from support.h:39,
 from mailbox.cc:33:
/usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here
  273 | GMutex *g_mutex_new (void);
  | ^~~
mailbox.cc: In copy constructor ‘Mailbox::Mailbox(const Mailbox&)’:
mailbox.cc:83:31: warning: ‘GMutex* g_mutex_new()’ is deprecated 
[-Wdeprecated-declarations]
   83 | mutex_ = g_mutex_new ();
  |   ^
In file included from /usr/include/glib-2.0/glib.h:111,
 from support.h:39,
 from mailbox.cc:33:
/usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here
  273 | GMutex *g_mutex_new (void);
  | ^~~
mailbox.cc:84:39: warning: ‘GMutex* g_mutex_new()’ is deprecated 
[-Wdeprecated-declarations]
   84 | monitor_mutex_ = g_mutex_new ();
  |   ^
In file included from /usr/include/glib-2.0/glib.h:111,
 from support.h:39,
 from mailbox.cc:33:
/usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here
  273 | GMutex *g_mutex_new (void);
  | ^~~
mailbox.cc: In destructor ‘virtual Mailbox::~Mailbox()’:
mailbox.cc:107:29: warning: ‘void g_mutex_free(GMutex*)’ is deprecated 
[-Wdeprecated-declarations]
  107 | g_mutex_free (mutex_);
  | ^
In file included from /usr/include/glib-2.0/glib.h:111,
 from support.h:39,
 from mailbox.cc:33:
/usr/include/glib-2.0/glib/deprecated/gthread.h:275:17: note: declared here
  275 | voidg_mutex_free(GMutex *mutex);
  | ^~~~
mailbox.cc:110:37: warning: ‘void g_mutex_free(GMutex*)’ is deprecated 
[-Wdeprecated-declarations]
  110 | g_mutex_free (monitor_mutex_);
  | ^
In file included from /usr/include/glib-2.0/glib.h:111,
 from support.h:39,
 from mailbox.cc:33:
/usr/include/glib-2.0/glib/deprecated/gthread.h:275:17: note: declared here
  275 | voidg_mutex_free

Bug#997219: marked as done (codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value = wxString; _Hash = IHu

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 23:03:39 +
with message-id 
and subject line Bug#1000928: fixed in codelite 14.0+dfsg-2
has caused the Debian Bug report #1000928,
regarding codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function 
‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value 
= wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’
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.)


-- 
1000928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codelite
Version: 14.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/ZoomNavigator && /usr/bin/c++ 
> -DINSTALL_DIR=\"/usr/share/codelite\" -DNDEBUG 
> -DPLUGINS_DIR=\"/usr/lib/codelite\" -DUSE_AUI_NOTEBOOK=0 -DUSE_SFTP=1 
> -DWXUSINGDLL -DWXUSINGDLL_CL -DWXUSINGDLL_SDK -DWXUSINGDLL_WXSQLITE3 
> -DYY_NEVER_INTERACTIVE=1 -DZoomNavigator_EXPORTS -D_FILE_OFFSET_BITS=64 
> -D__WXGTK__ -DwxUSE_GUI=1 -I/usr/include/gtk-3.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 
> -I/<>/Plugin -I/<>/sdk/wxsqlite3/include 
> -I/<>/CodeLite -I/<>/PCH 
> -I/<>/Interfaces -isystem 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem 
> /usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-deprecated-declarations -isystem 
> /usr/include/harfbuzz -std=c++11 -O2 -pthread -fPIC -fPIC -MD -MT 
> ZoomNavigator/CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o
>  -MF 
> CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o.d -o 
> CMakeFiles/ZoomNavigator.dir/zoom_navigator_zoomnavigator_bitmaps.cpp.o -c 
> /<>/ZoomNavigator/zoom_navigator_zoomnavigator_bitmaps.cpp
> /<>/SpellChecker/IHunSpell.cpp: In constructor 
> ‘IHunSpell::IHunSpell()’:
> /<>/SpellChecker/IHunSpell.cpp:67:17: error: use of deleted 
> function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() 
> [with _Value = wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
> IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’
>67 | m_scanners(0)
>   | ^
> In file included from /usr/include/c++/11/unordered_set:47,
>  from /<>/CodeLite/wxStringHash.h:4,
>  from /<>/CodeLite/file_logger.h:34,
>  from /<>/SpellChecker/IHunSpell.cpp:39:
> /usr/include/c++/11/bits/unordered_set.h:135:7: note: 
> ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with 
> _Value = wxString; _Hash = IHunSpell::StringHashOptionalCase; _Pred = 
> IHunSpell::StringCompareOptionalCase; _Alloc = std::allocator]’ is 
> implicitly deleted because the default definition would be ill-formed:
>   135 |   unordered_set() = default;
>   |   ^
> /usr/include/c++/11/bits/unordered_set.h:135:7: error: use of deleted 
> function ‘std::_Hashtable<_Key, _Value, _Alloc, _ExtractKey, _Equal, _Hash, 
> _RangeHash, _Unused, _RehashPolicy, _Traits>::_Hashtable() [with _Key = 
> wxString; _Value = wxString; _Alloc = std::allocator; _ExtractKey = 
> std::__detail::_Identity; _Equal = IHunSpell::StringCompareOptionalCase; 
> _Hash = IHunSpell::StringHashOptionalCase; _RangeHash = 
> std::__detail::_Mod_range_hashing; _Unused = 
> std::__detail::_Default_ranged_hash; _RehashPolicy = 
> std::__detail::_Prime_rehash_policy; _Traits = 
> std::__detail::_Hashtable_traits]’
> In file included from /usr/include/c++/11/unordered_set:46,
>  from /<>/CodeLite/wxStringHash.h:4,
>  from /<>/CodeLite/file_logger.h:34,
>  from /<>/SpellChecker/IHunSpell.cpp:39:
> /usr/include/c++/11/bits/hashtable.h:527:7: note: ‘std::_Hashtable<_Key, 
> _Value, _Alloc, _ExtractKey, _Equal, _Hash, _RangeHash, _Unused, 
> _RehashPolicy, _Traits>::_Hashtable() [with _Key = wxString; _Value = 
> wxString; _Alloc = std::allocator; _ExtractKey = 
> std::__detail::_Identity; _Equal = IHunSpell::StringCompareOptionalCase; 
> _Hash = IHunSpell::StringHashOptionalCase; _RangeHash = 
> std::__detail::_Mod_range_hashing; _Unused = 
> std::__detail::_Default_ranged_hash; _RehashPolicy 

Bug#1000928: marked as done (codelite: Please upgrade to llvm-toolchain-12 or 13)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 23:03:39 +
with message-id 
and subject line Bug#1000928: fixed in codelite 14.0+dfsg-2
has caused the Debian Bug report #1000928,
regarding codelite: Please upgrade to llvm-toolchain-12 or 13
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.)


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -13 (or -12).

Bookworm won't ship with llvm-toolchain-11

llvm-defaults is now pointing to -13.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: codelite
Source-Version: 14.0+dfsg-2
Done: Håvard F. Aasen 

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated codelite 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 Feb 2022 22:09:27 +0100
Source: codelite
Architecture: source
Version: 14.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard F. Aasen 
Closes: 997219 1000928
Changes:
 codelite (14.0+dfsg-2) unstable; urgency=medium
 .
   * QA upload.
   * Refresh patches using quilt.
   * Add patch from upstream to fix FTBFS with Hunspell and GCC-11.
 Closes: #997219
   * Rebuild for llvm. Closes: #1000928
   * d/rules:
 - Remove CMake options regarding clang, the options are
   no longer recognised.
 - Remove '--as-needed' flag, used by default.
 - No longer needed to specify include and library path for LLVM.
   * Update architectures to build with liblldb-dev.
   * Remove renamed and unused lintian tag for codelit.
   * d/watch: Bump to version 4.
   * Remove duplicated debhelper dependency.
   * Add upstream metadata:: Bug-Database, Bug-Submit, Repository
 and Repository-Browse.
   * Update architectures for llvm and libclang-dev.
   * Remove unused lintian override for package codelite-plugins.
Checksums-Sha1:
 d28bc8dab1b416b68084402c06021f5fb868ca55 2323 codelite_14.0+dfsg-2.dsc
 cc757add6adea1dfe74f0afaa451b7102b769e03 23576 
codelite_14.0+dfsg-2.debian.tar.xz
 7c748e9d39153bdd8d23cba4fe6092e18452645d 15291 
codelite_14.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 059e2762fb8e126590c96920d6ad309e7ee693911dce3687739b6d834c7fa63c 2323 
codelite_14.0+dfsg-2.dsc
 cb79ed3a449d049ed075d3a1271812bae6557c188e2da080dd7d2f4f5ea8507e 23576 
codelite_14.0+dfsg-2.debian.tar.xz
 366e67995d56b176594564565796196e21722103f2e92d5cca2bf916565664b1 15291 
codelite_14.0+dfsg-2_source.buildinfo
Files:
 80648bf253597c13ff4c3105283e93b7 2323 devel optional codelite_14.0+dfsg-2.dsc
 6c50044ce2408b02ab8b9a97e524750c 23576 devel optional 
codelite_14.0+dfsg-2.debian.tar.xz
 6ba4859d253ba556bb73c1832652ba98 15291 devel optional 
codelite_14.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmISxZYACgkQweDZLphv
fH6tHBAAjGR6cde7fQZIxSvGnl1n8sM2ReGV0BbbBdliKYQaLVz+AuG0YoUWOjcS
5j/upQcrJ9PTfJZPiXo1BimYwWsjz8tA22hg9yJIcINPa3umP/p6YAvwoIHUxW5F
1Fa8gyxqGQ8cj5AtG6c45u+KBX3I3lTPkE2afRoF3XJhU4dFFKzG0QTXv6WdrsnM
WKqo2BudK3+pCuFrvvMclB4tPsad52LGJgQDehr9YjCAQUOpuk523J+XVVwRKkmD
J4j/bpSkz/8z8ya2py3YkNtll0DMSZYPFJeLfYEgioZqyQ57X/HdvsIBQA6sm0YF
FnYOmbR1UbPp7hwWMJxdJz48DdqDW2GYHwKDM7Ivavh96cNsCFRKUufh9zShbcDm
LrkQe8z+zXFalzfSNtJsdkzjXV73BWgxavF1U+ZKzhCClSMO7ilWw1Sj9xYsuzNW
mW4GN48IiYDF5OzwiJBLAhM+OMNubLwAq4F81VStLWi3fE3BwCQxgCdnU77pwOrJ
uQOUT3p0YRZ49WzyX5nkQSkFZJTrUoiWC8FUlOxiZr3uvZUQFJt/EBqfqd5GILou
ZFbHLbiRG4t7C6uQckUkeN2Fx8yFJ0XzjGAuFSiMORdMPvDnehM3C1WjTlvDoKPo
OZVAcbIVkZPvXql8y9rFDJnQFpeIlYykHkLhk+99j9ErHh2RoHo=
=UOZA
-END PGP SIGNATURE End Message ---

Bug#1005448: marked as done (ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 22:50:47 +
with message-id 
and subject line Bug#1005448: fixed in ruby-certificate-authority 1.0.0-1
has caused the Debian Bug report #1005448,
regarding ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: 
NoMethodError:
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.)


-- 
1005448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-certificate-authority
Version: 0.2.0~434c15cd-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>   NoMethodError:
> undefined method `[]=' for #
> Did you mean?  []
>   # ./lib/certificate_authority/certificate.rb:229:in `block in 
> merge_options'
>   # ./lib/certificate_authority/certificate.rb:228:in `each'
>   # ./lib/certificate_authority/certificate.rb:228:in `merge_options'
>   # ./lib/certificate_authority/certificate.rb:95:in `block in sign!'
>   # ./lib/certificate_authority/certificate.rb:93:in `each'
>   # ./lib/certificate_authority/certificate.rb:93:in `sign!'
>   # ./spec/units/certificate_spec.rb:366:in `block (3 levels) in  (required)>'
> 
> Finished in 0.56569 seconds (files took 0.20536 seconds to load)
> 196 examples, 17 failures, 3 pending
> 
> Failed examples:
> 
> rspec ./spec/units/certificate_spec.rb:295 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should support BasicConstraints
> rspec ./spec/units/certificate_spec.rb:300 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should support subjectKeyIdentifier
> rspec ./spec/units/certificate_spec.rb:305 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should support authorityKeyIdentifier
> rspec ./spec/units/certificate_spec.rb:310 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should order subjectKeyIdentifier before authorityKeyIdentifier
> rspec ./spec/units/certificate_spec.rb:317 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should support keyUsage
> rspec ./spec/units/certificate_spec.rb:322 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> should support extendedKeyUsage
> rspec ./spec/units/certificate_spec.rb:182 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> SubjectAltName should have a subjectAltName if specified
> rspec ./spec/units/certificate_spec.rb:188 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> SubjectAltName should NOT have a subjectAltName if one was not specified
> rspec ./spec/units/certificate_spec.rb:194 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> SubjectAltName should replace email:copy with email address
> rspec ./spec/units/certificate_spec.rb:213 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> AuthorityInfoAccess should have an authority info access if specified
> rspec ./spec/units/certificate_spec.rb:228 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> CrlDistributionPoints should have a crlDistributionPoint if specified
> rspec ./spec/units/certificate_spec.rb:234 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> CrlDistributionPoints should NOT have a crlDistributionPoint if one was not 
> specified
> rspec ./spec/units/certificate_spec.rb:250 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> CertificatePolicies should have a certificatePolicy if specified
> rspec ./spec/units/certificate_spec.rb:287 # 
> CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates 
> CertificatePolicies should NOT include a certificatePolicy if not specified
> rspec ./spec/units/certificate_spec.rb:354 # 
> CertificateAuthority::Certificate Signing profile should be able to sign with 
> an optional policy hash
> rspec ./spec/units/certificate_spec.rb:358 # 
> CertificateAuthority::Certificate Signing profile should support a default 
> signing digest of SHA512
> rspec ./spec/units/certificate_spec.rb:364 # 
> CertificateAuthority::Certificate Signing profile should support a 
> configurable digest algorithm
> 
> 

Bug#1005448: marked as pending in ruby-certificate-authority

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #1005448 in ruby-certificate-authority 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/ruby-team/ruby-certificate-authority/-/commit/45717e0b6b3deb8efdc8526b2602af63f0043441


add fix for Ruby openssl 3.0.0

Closes: #1005448


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005448

Processed: Bug#1005448 marked as pending in ruby-certificate-authority

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005448 [src:ruby-certificate-authority] ruby-certificate-authority: 
FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:
Added tag(s) pending.

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

Processed: Re: Bug#1005920 closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1005920: fixed in coq-doc 8.15.0-2)

[Debian Bug Tracking System]

Processing control commands:

> found -1 8.15.0-2
Bug #1005920 {Done: Julien Puydt } [src:coq-doc] coq-doc: 
FTBFS: Error: Library "zarith" not found.
Marked as found in versions coq-doc/8.15.0-2; no longer marked as fixed in 
versions coq-doc/8.15.0-2 and reopened.

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

Bug#1005920: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1005920: fixed in coq-doc 8.15.0-2)

[Andreas Beckmann]

Control: found -1 8.15.0-2

This looks like more missing Build-Depends(-Indep):

[...]
Running[3870]: (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b 
html sphinx refman-html)
Running[3871]: (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b 
latex sphinx refman-pdf)
Command [3870] exited with code 2:
$ (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b html sphinx 
refman-html)

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 329, in 
eval_config_file
exec(code, namespace)
  File "/build/coq-doc-8.15.0/_build/default/doc/sphinx/conf.py", line 245, in 

import sphinx_rtd_theme
ModuleNotFoundError: No module named 'sphinx_rtd_theme'

Command [3871] exited with code 2:
$ (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b latex sphinx 
refman-pdf)

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 329, in 
eval_config_file
exec(code, namespace)
  File "/build/coq-doc-8.15.0/_build/default/doc/sphinx/conf.py", line 245, in 

import sphinx_rtd_theme
ModuleNotFoundError: No module named 'sphinx_rtd_theme'

make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1


Andreas

Bug#1005448: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:

[Antonio Terceiro]

Control: forwarded -1 
https://github.com/cchandler/certificate_authority/issues/61

I tried updating to the latest upstream release, and this issue is still
there. It's caused by the fact that ruby3.0 now carries version 3.0.0 of
the openssl ruby extension, and this packages is not compatible with it
yet.


signature.asc
Description: PGP signature

Processed: Re: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/cchandler/certificate_authority/issues/61
Bug #1005448 [src:ruby-certificate-authority] ruby-certificate-authority: 
FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:
Set Bug forwarded-to-address to 
'https://github.com/cchandler/certificate_authority/issues/61'.

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

Bug#1004037: marked as done (src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 21:04:03 +
with message-id 
and subject line Bug#1004037: fixed in plink2 2.00~a3-220218+dfsg-1
has caused the Debian Bug report #1004037,
regarding src:plink2: fails to migrate to testing for too long: autopkgtest 
regression
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.)


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

Source: plink2
Version: 2.00~a3-210816+dfsg-1
Severity: serious
Control: close -1 2.00~a3-211011+dfsg-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1000782

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=plink2



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: plink2
Source-Version: 2.00~a3-220218+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated plink2 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 Feb 2022 21:36:16 +0100
Source: plink2
Architecture: source
Version: 2.00~a3-220218+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1000782 1004037
Changes:
 plink2 (2.00~a3-220218+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #1000782, #1004037
   * Standards-Version: 4.6.0 (routine-update)
Checksums-Sha1:
 e6ff076eef14c851a162d8dd460ed88f1877c3a1 2153 plink2_2.00~a3-220218+dfsg-1.dsc
 09268f7f3b97f18f0d9673de0096dde412bd685d 914416 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 b506e2ab12a9f4fb1be18793e00437f0d8212e83 49820 
plink2_2.00~a3-220218+dfsg-1.debian.tar.xz
 84148889d28b8fca2b6e456f2f0632e0b6901997 6559 
plink2_2.00~a3-220218+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 0ccd27cd3c265ddfabd0c717bfc3fe9642bd676ae66d2b0a97747143fd951e8e 2153 
plink2_2.00~a3-220218+dfsg-1.dsc
 b21c9753377dc97822dcbba3ee4f82946c94fd0f3f67aa4e0a2efc82587b13c1 914416 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 ace36fe35ffdf654c35113ec970af7304cfcec9c03ff84e133e44c3daeff39db 49820 
plink2_2.00~a3-220218+dfsg-1.debian.tar.xz
 52132c361f33a9c7595d9b75d18b1da830eff74bd240ccd1b57b3ff0df15b97f 6559 
plink2_2.00~a3-220218+dfsg-1_amd64.buildinfo
Files:
 f48804cf2ed590373ab87a1cc7583847 2153 science optional 
plink2_2.00~a3-220218+dfsg-1.dsc
 f1917a6fddb4839ec61bd81335acd345 914416 science optional 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 fefd57da810620611028f557babc3509 49820 science optional 

Bug#1000782: marked as done (plink2: autopkgtest regression: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 21:04:03 +
with message-id 
and subject line Bug#1000782: fixed in plink2 2.00~a3-220218+dfsg-1
has caused the Debian Bug report #1000782,
regarding plink2: autopkgtest regression: Segmentation fault
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.)


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

Source: plink2
Version: 2.00~a3-211011+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
plink2 from testing2.00~a3-211011+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=plink2

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plink2/17088127/log.gz

PLINK v2.00a3 SSE4.2 (11 Oct 2021) 
www.cog-genomics.org/plink/2.0/
(C) 2005-2021 Shaun Purcell, Christopher Chang   GNU General Public 
License v3

Logging to tmp_data.log.
Options in effect:
  --dummy 33 65537 0.1 dosage-freq=0.1
  --out tmp_data

Start time: Sun Nov 28 11:11:17 2021
257840 MiB RAM detected; reserving 128920 MiB for main workspace.
Using up to 48 threads (change this with --threads).

--dummy: 65k variants written.
Dummy data (33 samples, 65537 SNPs) written to tmp_data.pgen + 
tmp_data.pvar +

tmp_data.psam .
End time: Sun Nov 28 11:11:17 2021
/usr/bin/plink2: line 8:  1566 Segmentation fault  "${cmd}" "$@"
autopkgtest [11:11:17]: test run-sample-analysis




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: plink2
Source-Version: 2.00~a3-220218+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated plink2 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 Feb 2022 21:36:16 +0100
Source: plink2
Architecture: source
Version: 2.00~a3-220218+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1000782 1004037
Changes:
 plink2 (2.00~a3-220218+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #1000782, #1004037
   * Standards-Version: 4.6.0 (routine-update)
Checksums-Sha1:
 e6ff076eef14c851a162d8dd460ed88f1877c3a1 2153 plink2_2.00~a3-220218+dfsg-1.dsc
 09268f7f3b97f18f0d9673de0096dde412bd685d 914416 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 b506e2ab12a9f4fb1be18793e00437f0d8212e83 49820 
plink2_2.00~a3-220218+dfsg-1.debian.tar.xz
 84148889d28b8fca2b6e456f2f0632e0b6901997 6559 
plink2_2.00~a3-220218+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 0ccd27cd3c265ddfabd0c717bfc3fe9642bd676ae66d2b0a97747143fd951e8e 2153 
plink2_2.00~a3-220218+dfsg-1.dsc
 b21c9753377dc97822dcbba3ee4f82946c94fd0f3f67aa4e0a2efc82587b13c1 914416 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 ace36fe35ffdf654c35113ec970af7304cfcec9c03ff84e133e44c3daeff39db 49820 
plink2_2.00~a3-220218+dfsg-1.debian.tar.xz
 52132c361f33a9c7595d9b75d18b1da830eff74bd240ccd1b57b3ff0df15b97f 6559 
plink2_2.00~a3-220218+dfsg-1_amd64.buildinfo
Files:
 f48804cf2ed590373ab87a1cc7583847 2153 science optional 
plink2_2.00~a3-220218+dfsg-1.dsc
 f1917a6fddb4839ec61bd81335acd345 914416 science optional 
plink2_2.00~a3-220218+dfsg.orig.tar.xz
 

Processed: severity of 1004392 is normal

[Debian Bug Tracking System]

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

> severity 1004392 normal
Bug #1004392 {Done: Ansgar } [systemd] systemd: Incorrect 
location of configuration files
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Andreas Tille]

Cool!  This finally works.  Thanks a lot for your patience, Andreas.

Am Sun, Feb 20, 2022 at 09:43:10AM -0800 schrieb Chris Chang:
> Hmm.  Ordinarily, that download link would be fine.  I had not updated it
> this time because the issue only affects gcc 11+, so it did not affect any
> of the precompiled binaries and I wanted to keep the posted source
> identical to that used to compile those binaries.
> 
> On the other hand, the only difference (in the non-gcc-11+ case) between
> the binaries and the updated source is the version date.  I guess this is
> insignificant enough that a temporary discordance is less disruptive than
> making you change your packing process, so I've updated the website source
> link to point to the newer code; let me know if you still run into any
> problems.
> 
> On Sat, Feb 19, 2022 at 11:53 PM Andreas Tille  wrote:
> 
> > Hi Chris,
> >
> > Am Sat, Feb 19, 2022 at 11:37:34PM -0800 schrieb Chris Chang:
> > > To elaborate: when I look at
> > > https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that
> > > plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have
> > the
> > > same contents as the v2.00a3-20220218 GitHub tag/release.  So I don't
> > know
> > > where you grabbed the code from this time, but it does not appear to be
> > > from GitHub.
> >
> > That's true since on Github the source code of plink1.9 and plink2 is not
> > separated.  Thus I download the tarball from
> >
> >https://www.cog-genomics.org/plink/2.0/
> >
> > which points to
> >
> >https://www.cog-genomics.org/static/bin/plink2_src_220217.zip
> >
> > I confirm that the tag on Github says v2.00a3-20220218 which seems to be
> > later than 220217.  In principle I could point the packaging metadata to
> > Github and exclude everything that I do not need for plink2 packaging (so
> > remove 1.9 directory and code copies of libdeflate, simde and zstd in 2.0)
> >
> > In case you consider this the safer way to download plink2 code I'll do so.
> >
> > Kind regards and thanks a lot for comparing the code base
> >
> >  Andreas.
> >
> > > On Sat, Feb 19, 2022 at 7:54 AM Chris Chang 
> > wrote:
> > >
> > > > If you build off the current head, the version string should say "18
> > Feb
> > > > 2022", not "17 Feb 2022".
> > > >
> > > > On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille 
> > wrote:
> > > >
> > > >> Hi again,
> > > >>
> > > >> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> > > >> > Ok, new release/tag created.
> > > >>
> > > >> I've built the new version now.  The bad news is that it keeps on
> > > >> SEGFAULTing for me:
> > > >>
> > > >> ...
> > > >> (gdb) run
> > > >> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data
> > > >> --export vcf vcf-dosage=DS --out tmp_data2
> > > >> [Thread debugging using libthread_db enabled]
> > > >> Using host libthread_db library
> > "/lib/x86_64-linux-gnu/libthread_db.so.1".
> > > >> [New Thread 0x74cc7640 (LWP 985019)]
> > > >> [New Thread 0x744c6640 (LWP 985020)]
> > > >> [New Thread 0x7fffebcc5640 (LWP 985021)]
> > > >> PLINK v2.00a3 64-bit (17 Feb 2022)
> > > >> www.cog-genomics.org/plink/2.0/
> > > >> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public
> > > >> License v3
> > > >> Logging to tmp_data2.log.
> > > >> Options in effect:
> > > >>   --debug
> > > >>   --export vcf vcf-dosage=DS
> > > >>   --out tmp_data2
> > > >>   --pfile tmp_data
> > > >>
> > > >> Start time: Sat Feb 19 16:00:00 2022
> > > >> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
> > > >> Using up to 4 compute threads.
> > > >> [New Thread 0x77fc5640 (LWP 985022)]
> > > >>
> > > >> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
> > > >> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60
> > > >> "tmp_data.psam", pheno_range_list_ptr=, fam_cols=...,
> > > >> pheno_ct_max=,
> > > >> missing_pheno=, affection_01=0, max_thread_ct=4,
> > > >> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
> > > >> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
> > > >> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
> > > >> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
> > > >> pheno_ct_ptr=0x7fff8720,
> > > >> max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
> > > >> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
> > > >>
> > > >>
> > > >> Please let me know if I can do further checks.
> > > >>
> > > >> Kind regards
> > > >>
> > > >>   Andreas.
> > > >>
> > > >> --
> > > >> http://fam-tille.de
> > > >>
> > > >
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Bug#1001341: marked as done (genetic: autopkgtest needs update for python3.10: 'Sequence' from 'collections' is removed)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 19:49:18 +
with message-id 
and subject line Bug#1001341: fixed in genetic 0.1.1b+git20170527.98255cb-3
has caused the Debian Bug report #1001341,
regarding genetic: autopkgtest needs update for python3.10: 'Sequence' from 
'collections' is removed
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.)


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

Source: genetic
Version: 0.1.1b+git20170527.98255cb-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.9.8-1
geneticfrom testing0.1.1b+git20170527.98255cb-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. 
https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

Currently this regression is blocking the migration of python3-defaults 
to testing [1].


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

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/g/genetic/17376868/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/genetic/__init__.py", line 2, in 


import genetic.populations
  File 
"/usr/lib/python3/dist-packages/genetic/populations/__init__.py", line 
1, in 

from ._populations import *
  File 
"/usr/lib/python3/dist-packages/genetic/populations/_populations.py", 
line 10, in 

from genetic.util import Workers, filter_duplicates
  File "/usr/lib/python3/dist-packages/genetic/util/__init__.py", line 
1, in 

from ._util import *
  File "/usr/lib/python3/dist-packages/genetic/util/_util.py", line 1, 
in 

from collections import Sequence
ImportError: cannot import name 'Sequence' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

autopkgtest [21:40:01]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: genetic
Source-Version: 0.1.1b+git20170527.98255cb-3
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated genetic 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 Feb 2022 20:27:49 +0100
Source: genetic
Architecture: source
Version: 0.1.1b+git20170527.98255cb-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Timo Röhling 
Closes: 1001341
Changes:
 genetic (0.1.1b+git20170527.98255cb-3) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.6.0
   * Import Sequence from collections.abc (Closes: #1001341)
   * Fix unit tests
Checksums-Sha1:
 233175a93aa4311a4847780f5e037f8c4ec7c7a5 2058 
genetic_0.1.1b+git20170527.98255cb-3.dsc
 fec65d43ce109e8cdb2e40229fac2312d22194d3 4060 
genetic_0.1.1b+git20170527.98255cb-3.debian.tar.xz
 a14734cc87bd60b05e3346f10e22d0f80d249042 7043 
genetic_0.1.1b+git20170527.98255cb-3_amd64.buildinfo
Checksums-Sha256:
 e1514cbd73c07af392c3a7f402ef67c1fe1d0f9fcbd9a7dccb4cfd2fb7a761bd 2058 

Bug#1001489: marked as done (twodict: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'KeysView')

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 19:34:39 +
with message-id 
and subject line Bug#1001489: fixed in twodict 1.2-3
has caused the Debian Bug report #1001489,
regarding twodict: (autopkgtest) needs update for python3.10: 'collections' has 
no attribute 'KeysView'
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.)


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

Source: twodict
Version: 1.2-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of twodict fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
twodictfrom testing1.2-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/t/twodict/17446747/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/twodict.py", line 25, in 
class DictKeysView(collections.KeysView):
AttributeError: module 'collections' has no attribute 'KeysView'
autopkgtest [14:18:28]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: twodict
Source-Version: 1.2-3
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated twodict 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 Feb 2022 20:13:51 +0100
Source: twodict
Architecture: source
Version: 1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1001489
Changes:
 twodict (1.2-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Timo Röhling ]
   * Import abstract base classes from collections.abc (Closes: #1001489)
   * Bump Standards-Version to 4.6.0
   * Bump debhelper compat to 13
   * Upgrade d/watch to version 4 format
Checksums-Sha1:
 4082b399b97518c31db74b32f4cfec08a653edd8 1837 twodict_1.2-3.dsc
 1f775a28f571c506d43c9139064242fd0bd1c6a9 3048 twodict_1.2-3.debian.tar.xz
 8bfd9850a1851d4f96a1b7e66a86b3e31013973f 6683 twodict_1.2-3_amd64.buildinfo
Checksums-Sha256:
 0b30401f0649b0425d0a4e2311d05db556b42132a1cb6c04365e49fdea60f992 1837 
twodict_1.2-3.dsc
 9d7bd62495009e492a19d9fdba7ab03bc679a2305125c309a32c13984d0fd9ca 3048 
twodict_1.2-3.debian.tar.xz
 

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

[Nilesh Patra]

Hi Salvatore,

On Sun, Feb 20, 2022 at 08:01:34PM +0100, Salvatore Bonaccorso wrote:
> >[ Andreas Tille ]
> >* Team upload.
> >* Version > 3.6.x are closing CVE-2021-33622
> >  Closes: #990201
> 
> Can you help isolate on that?
> https://support.sylabs.io/support/solutions/articles/4287130-3-5-8-security-release-cve-2021-33622-
> refers the 3.6.x as beeing affected and so there is the statement that
> the issue is not going to be patched in those version:
> 
> > This issue affects open-source Singularity 3.5.x and 3.6.x. These
> > versions are no longer supported and will not be patched.

Yes, but in the same bug link, this is written as well:

| Affected Versions
| Singularity 3.5.x - 3.6.x, SingularityPRO <3.5-8.

And so I thought it has been fixed in later versions.

> https://bugs.debian.org/990201#10 is as well relevant in the context.

Since Andreas added this entry, I suppose he somehow forgot
about his own findings about the problem; and I did not scrutinize much
before upload (as this was not building and that was my primary focus)

> So where has this issue bin fixed?

But yes, you are right, even at Mitre metadata, I do not find any information
about any patch for the bug; i.e. I do not see the "code" that fixes it, and 
hence
I too am skeptical whether or not it is really gone.

For the sake of completeness, I have opened a issue upstream[1]

[1]: https://github.com/sylabs/singularity/issues/586
 
Regards,
Nilesh


signature.asc
Description: PGP signature

Bug#1001295: marked as done (dominate: needs update for python3.10: 'Callable' from 'collections' is removed)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 19:18:42 +
with message-id 
and subject line Bug#1001295: fixed in dominate 2.6.0-1
has caused the Debian Bug report #1001295,
regarding dominate: needs update for python3.10: 'Callable' from 'collections' 
is removed
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.)


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

Source: dominate
Version: 2.3.1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.9.8-1
dominate   from testing2.3.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. 
https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

Currently this regression is blocking the migration of python3-defaults 
to testing [1].


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

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dominate/17344293/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/dominate/__init__.py", line 4, 
in 

from .document import document
  File "/usr/lib/python3/dist-packages/dominate/document.py", line 19, 
in 

from . import tags
  File "/usr/lib/python3/dist-packages/dominate/tags.py", line 21, in 


from .dom_tag  import dom_tag, attr
  File "/usr/lib/python3/dist-packages/dominate/dom_tag.py", line 23, 
in 

from collections import defaultdict, namedtuple, Callable
ImportError: cannot import name 'Callable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

autopkgtest [20:14:07]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dominate
Source-Version: 2.6.0-1
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated dominate 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 Feb 2022 19:58:55 +0100
Source: dominate
Architecture: source
Version: 2.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1001295
Changes:
 dominate (2.6.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * debian/control: Remove empty control field Uploaders.
   * Bump debhelper from deprecated 9 to 12.
   * Remove obsolete field Name from debian/upstream/metadata (already present 
in
 machine-readable debian/copyright).
   * Bump debhelper from old 12 to 13.
 .
   [ Timo Röhling ]
   * Fix d/watch
   * New upstream version 2.6.0
 - Fix import of collections.abc.Callable (Closes: #1001295)
   * Bump Standards-Version to 4.6.0
Checksums-Sha1:
 711c1feb14a72c35c1dd3856cdc3475803b7a446 1828 dominate_2.6.0-1.dsc
 149fa64f7838198882d6f35aed29278e03ca59da 

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

[Salvatore Bonaccorso]

Hi Nilesh, hi Andreas,

On Sun, Feb 20, 2022 at 02:37:12PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Sun, 20 Feb 2022 19:27:46 +0530
> Source: singularity-container
> Architecture: source
> Version: 3.9.5+ds1-1
> Distribution: experimental
> Urgency: medium
> Maintainer: Debian HPC Team 
> Changed-By: Nilesh Patra 
> Closes: 990201
> Changes:
>  singularity-container (3.9.5+ds1-1) experimental; urgency=medium
>  .
>[ Andreas Tille ]
>* Team upload.
>* Version > 3.6.x are closing CVE-2021-33622
>  Closes: #990201

Can you help isolate on that?
https://support.sylabs.io/support/solutions/articles/4287130-3-5-8-security-release-cve-2021-33622-
refers the 3.6.x as beeing affected and so there is the statement that
the issue is not going to be patched in those version:

> This issue affects open-source Singularity 3.5.x and 3.6.x. These
> versions are no longer supported and will not be patched.

https://bugs.debian.org/990201#10 is as well relevant in the context.

So where has this issue bin fixed?

Regards,
Salvatore

Bug#996737: marked as done (ksysguard: apt dist-upgrade wants to remove ksysguard due to broken dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:51:23 +
with message-id 
and subject line Bug#1005973: Removed package(s) from unstable
has caused the Debian Bug report #996737,
regarding ksysguard: apt dist-upgrade wants to remove ksysguard due to broken 
dependencies
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.)


-- 
996737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ksysguard
Version: 4:5.21.5-2
Severity: normal

Dear Maintainer,


apt dist-upgrade wants to remove ksysguard due to libkf5sysguard-bin breaks and 
replaces ksysguard (<< 4:5.21.80), but no later version is available in the sid 
repo.

Also see this 
https://qa.debian.org/dose/debcheck/unstable_main/latest/packages/ksysguard.html#dadaa0da5452e7f3ebf4066d6b7206dc

I believe this also related to ksysguard bug #996736

Thanks,
manul


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ksysguard depends on:
ii  kio  5.86.0-1
ii  ksysguard-data   4:5.21.5-2
ii  ksysguardd   4:5.21.5-2
ii  libc62.32-4
ii  libgcc-s111.2.0-8
ii  libkf5completion55.86.0-1
ii  libkf5configcore55.86.0-1
ii  libkf5configwidgets5 5.86.0-1
ii  libkf5coreaddons55.86.0-1
ii  libkf5dbusaddons55.86.0-1
ii  libkf5i18n5  5.86.0-1
ii  libkf5iconthemes55.86.0-1
ii  libkf5kiocore5   5.86.0-1
ii  libkf5kiowidgets55.86.0-1
ii  libkf5networkmanagerqt6  5.86.0-1
ii  libkf5newstuff5  5.86.0-3
ii  libkf5newstuffcore5  5.86.0-3
ii  libkf5notifications5 5.86.0-1
ii  libkf5solid5 5.86.0-1
ii  libkf5widgetsaddons5 5.86.0-1
ii  libkf5windowsystem5  5.86.0-1
ii  libkf5xmlgui55.86.0-1
ii  libksgrd94:5.21.5-3
ii  libksignalplotter9   4:5.21.5-3
ii  libksysguardformatter1   4:5.21.5-3
ii  libnl-3-200  3.4.0-1+b1
ii  libnl-route-3-2003.4.0-1+b1
ii  libpcap0.8   1.10.1-4
ii  libprocesscore9  4:5.21.5-3
ii  libprocessui94:5.21.5-3
ii  libqt5core5a 5.15.2+dfsg-12
ii  libqt5dbus5  5.15.2+dfsg-12
ii  libqt5gui5   5.15.2+dfsg-12
ii  libqt5network5   5.15.2+dfsg-12
ii  libqt5widgets5   5.15.2+dfsg-12
ii  libqt5xml5   5.15.2+dfsg-12
ii  libsensors5  1:3.6.0-7
ii  libstdc++6   11.2.0-8
ii  libudev1 247.9-4

ksysguard recommends no packages.

ksysguard suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:5.21.5-2+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#984337: marked as done (slowmovideo: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:50:50 +
with message-id 
and subject line Bug#1005926: Removed package(s) from unstable
has caused the Debian Bug report #984337,
regarding slowmovideo: ftbfs with GCC-11
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.)


-- 
984337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:slowmovideo
Version: 0.5+git20190116-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/slowmovideo_0.5+git20190116-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:49,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QDebug:1,
 from /<>/src/slowmoVideo/lib/defs_sV.hpp:22,
 from /<>/src/slowmoVideo/lib/defs_sV.cpp:1:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:129:5: note: declared here
  129 | Q_OBJECT
  | ^~~~
/<>/src/slowmoVideo/lib/defs_sV.cpp: At global scope:
/<>/src/slowmoVideo/lib/defs_sV.cpp:128:34: error: ISO C++17 does 
not allow dynamic exception specifications
  128 | Fps_sV::Fps_sV(int num, int den) throw(Error_sV) :
  |  ^
/<>/src/slowmoVideo/lib/defs_sV.cpp:135:35: error: ISO C++17 does 
not allow dynamic exception specifications
  135 | Fps_sV::Fps_sV(QString fpsString) throw(Error_sV)
  |   ^
/<>/src/slowmoVideo/lib/defs_sV.cpp:148:27: error: ISO C++17 does 
not allow dynamic exception specifications
  148 | Fps_sV::Fps_sV(float fps) throw(Error_sV)
  |   ^
In file included from /<>/src/slowmoVideo/lib/videoInfo_sV.cpp:13:
/<>/src/slowmoVideo/lib/defs_sV.hpp:99:30: error: ISO C++17 does 
not allow dynamic exception specifications
   99 | Fps_sV(int num, int den) throw(Error_sV); ///< den must be > 0.
  |  ^
/<>/src/slowmoVideo/lib/defs_sV.hpp:101:23: error: ISO C++17 does 
not allow dynamic exception specifications
  101 | Fps_sV(float fps) throw(Error_sV); ///< Converts a float fps number 
to a fractional. 23.97 and 29.97 are detected.
  |   ^
/<>/src/slowmoVideo/lib/defs_sV.hpp:103:31: error: ISO C++17 does 
not allow dynamic exception specifications
  103 | Fps_sV(QString fpsString) throw(Error_sV); ///< Accepts fps strings 
like 24000/1001 for 23.97 fps.
  |   ^
make[3]: *** [slowmoVideo/lib/CMakeFiles/sV.dir/build.make:85: 
slowmoVideo/lib/CMakeFiles/sV.dir/defs_sV.cpp.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:402: slowmoVideo/lib/CMakeFiles/sV.dir/all] 
Error 2
[  5%] Building CXX object 
slowmoVideo/lib/CMakeFiles/sVencode.dir/moc_ffmpeg_writer.cpp.o
cd /<>/obj-x86_64-linux-gnu/slowmoVideo/lib && /usr/bin/c++ 
-DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-I/<>/obj-x86_64-linux-gnu -I/<>/src/slowmoVideo/tr 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 

Bug#996072: marked as done (gnome-shell-extension-tilix-dropdown: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:49:46 +
with message-id 
and subject line Bug#1005914: Removed package(s) from unstable
has caused the Debian Bug report #996072,
regarding gnome-shell-extension-tilix-dropdown: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
996072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tilix-dropdown
Version: 7-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 7-1+rm

Dear submitter,

as the package gnome-shell-extension-tilix-dropdown has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#994062: marked as done (gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in search path)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:49:46 +
with message-id 
and subject line Bug#1005914: Removed package(s) from unstable
has caused the Debian Bug report #994062,
regarding gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in 
search path
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.)


-- 
994062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tilix-dropdown
Version: 7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
installed gnome-shell-extension-tilix-dropdown
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
attempted to enable extension
   * What was the outcome of this action?
extension not enabled with the error given in the subject line.
   * What outcome did you expect instead?
extension enabled

*** End of the template - remove these template lines ***


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

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

Versions of packages gnome-shell-extension-tilix-dropdown depends on:
ii  gnome-shell  3.38.4-1
ii  tilix1.9.4-2

gnome-shell-extension-tilix-dropdown recommends no packages.

gnome-shell-extension-tilix-dropdown suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7-1+rm

Dear submitter,

as the package gnome-shell-extension-tilix-dropdown has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#993200: marked as done (gnome-shell-extension-tilix-shortcut: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:50:16 +
with message-id 
and subject line Bug#1005915: Removed package(s) from unstable
has caused the Debian Bug report #993200,
regarding gnome-shell-extension-tilix-shortcut: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
993200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tilix-shortcut
Version: 1.0.1-2
Severity: important

The metadata.json for this extension doesn't declare compatibility with
GNOME 40. I don't know whether the actual code will need changes.

In many versions of GNOME Shell, metadata.json didn't matter much, because
validation of extensions' metadata against the installed Shell version
was disabled by default; but in GNOME 40 the default has changed back
to enabling the version check by default, in an effort to avoid issues
caused by outdated extensions remaining enabled.

When we do the GNOME 40 transition, hopefully soon, we will have to
either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.0.1-2+rm

Dear submitter,

as the package gnome-shell-extension-tilix-shortcut has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#959741: marked as done (gnome-shell-extension-tilix-shortcut: it does not appear in Nautilus contextual menu)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 18:50:16 +
with message-id 
and subject line Bug#1005915: Removed package(s) from unstable
has caused the Debian Bug report #959741,
regarding gnome-shell-extension-tilix-shortcut: it does not appear in Nautilus 
contextual menu
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.)


-- 
959741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tilix-shortcut
Version: 1.0.1-2
Severity: grave
Justification: renders package unusable

Dear maintainer,

I open this bug to add more information to #913024.
(In fact, I think that bug should be moved here, as the bug affects
the extension, not tilix proper.)


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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell-extension-tilix-shortcut depends on:
ii  gnome-shell  3.36.2-1
ii  tilix1.9.3-4+b1

gnome-shell-extension-tilix-shortcut recommends no packages.

gnome-shell-extension-tilix-shortcut suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.1-2+rm

Dear submitter,

as the package gnome-shell-extension-tilix-shortcut has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Fixed in latest upload already

[Debian Bug Tracking System]

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

> fixed 1005621 1.2.1-2
Bug #1005621 [src:coq-hierarchy-builder] coq-hierarchy-builder: FTBFS: 
dh_install: error: missing files, aborting
Ignoring request to alter fixed versions of bug #1005621 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1006119: uwsgi: FTBFS with ruby3.0 as default

[Antonio Terceiro]

Control: tag -1 + patch

On Sat, 19 Feb 2022 14:19:46 +0100 Paul Gevers  wrote:
> Source: uwsgi
> Version: 2.0.20-2
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
> Control: block -1 by 1004915
> 
> Dear maintainer,
> 
> I tried to binNMU your package for the ongoing ruby3.0 as default ruby
> transition. It failed:
> https://buildd.debian.org/status/package.php?p=uwsgi
> 
> Paul

The attached patch converts the rack plugin to ruby3.0. Please let me
know if I should just upload it (requires going through NEW due to the
new bianry package).
uwsgi_2.0.20-2.1.dsc
uwsgi_2.0.20-2.dsc


signature.asc
Description: PGP signature

Processed: Re: uwsgi: FTBFS with ruby3.0 as default

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1006119 [src:uwsgi] uwsgi: FTBFS with ruby3.0 as default
Added tag(s) patch.

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

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Chris Chang]

Hmm.  Ordinarily, that download link would be fine.  I had not updated it
this time because the issue only affects gcc 11+, so it did not affect any
of the precompiled binaries and I wanted to keep the posted source
identical to that used to compile those binaries.

On the other hand, the only difference (in the non-gcc-11+ case) between
the binaries and the updated source is the version date.  I guess this is
insignificant enough that a temporary discordance is less disruptive than
making you change your packing process, so I've updated the website source
link to point to the newer code; let me know if you still run into any
problems.

On Sat, Feb 19, 2022 at 11:53 PM Andreas Tille  wrote:

> Hi Chris,
>
> Am Sat, Feb 19, 2022 at 11:37:34PM -0800 schrieb Chris Chang:
> > To elaborate: when I look at
> > https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that
> > plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have
> the
> > same contents as the v2.00a3-20220218 GitHub tag/release.  So I don't
> know
> > where you grabbed the code from this time, but it does not appear to be
> > from GitHub.
>
> That's true since on Github the source code of plink1.9 and plink2 is not
> separated.  Thus I download the tarball from
>
>https://www.cog-genomics.org/plink/2.0/
>
> which points to
>
>https://www.cog-genomics.org/static/bin/plink2_src_220217.zip
>
> I confirm that the tag on Github says v2.00a3-20220218 which seems to be
> later than 220217.  In principle I could point the packaging metadata to
> Github and exclude everything that I do not need for plink2 packaging (so
> remove 1.9 directory and code copies of libdeflate, simde and zstd in 2.0)
>
> In case you consider this the safer way to download plink2 code I'll do so.
>
> Kind regards and thanks a lot for comparing the code base
>
>  Andreas.
>
> > On Sat, Feb 19, 2022 at 7:54 AM Chris Chang 
> wrote:
> >
> > > If you build off the current head, the version string should say "18
> Feb
> > > 2022", not "17 Feb 2022".
> > >
> > > On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille 
> wrote:
> > >
> > >> Hi again,
> > >>
> > >> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> > >> > Ok, new release/tag created.
> > >>
> > >> I've built the new version now.  The bad news is that it keeps on
> > >> SEGFAULTing for me:
> > >>
> > >> ...
> > >> (gdb) run
> > >> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data
> > >> --export vcf vcf-dosage=DS --out tmp_data2
> > >> [Thread debugging using libthread_db enabled]
> > >> Using host libthread_db library
> "/lib/x86_64-linux-gnu/libthread_db.so.1".
> > >> [New Thread 0x74cc7640 (LWP 985019)]
> > >> [New Thread 0x744c6640 (LWP 985020)]
> > >> [New Thread 0x7fffebcc5640 (LWP 985021)]
> > >> PLINK v2.00a3 64-bit (17 Feb 2022)
> > >> www.cog-genomics.org/plink/2.0/
> > >> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public
> > >> License v3
> > >> Logging to tmp_data2.log.
> > >> Options in effect:
> > >>   --debug
> > >>   --export vcf vcf-dosage=DS
> > >>   --out tmp_data2
> > >>   --pfile tmp_data
> > >>
> > >> Start time: Sat Feb 19 16:00:00 2022
> > >> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
> > >> Using up to 4 compute threads.
> > >> [New Thread 0x77fc5640 (LWP 985022)]
> > >>
> > >> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
> > >> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60
> > >> "tmp_data.psam", pheno_range_list_ptr=, fam_cols=...,
> > >> pheno_ct_max=,
> > >> missing_pheno=, affection_01=0, max_thread_ct=4,
> > >> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
> > >> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
> > >> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
> > >> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
> > >> pheno_ct_ptr=0x7fff8720,
> > >> max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
> > >> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
> > >>
> > >>
> > >> Please let me know if I can do further checks.
> > >>
> > >> Kind regards
> > >>
> > >>   Andreas.
> > >>
> > >> --
> > >> http://fam-tille.de
> > >>
> > >
>
> --
> http://fam-tille.de
>

Bug#1004556: marked as done (libmpich-dev: The simplest MPI program compiled with mpich crashes)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 16:34:17 +
with message-id 
and subject line Bug#1004556: fixed in mpich 4.0-2
has caused the Debian Bug report #1004556,
regarding libmpich-dev: The simplest MPI program compiled with mpich crashes
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.)


-- 
1004556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 4.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jul...@julien-bigot.fr

Dear Maintainer,

When running the simplest MPI program,
```
#include 
int main(int argc, char* argv[])
{
MPI_Init(, );
MPI_Finalize();
return 0;
}
```

it crashes with output:
```
Abort(874106383): Fatal error in internal_Init: Other MPI error, error stack:
internal_Init(59): MPI_Init(argc=0x7ffc82ed999c, argv=0x7ffc82ed9990) failed
MPII_Init_thread(209): 
MPID_Init(359)...: 
MPIR_pmi_init(151)...: PMIX_Init returned -25
```

See attached reproduction log for full details

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmpich-dev depends on:
ii  g++4:11.2.0-2
ii  gfortran [gfortran-mod-15] 4:11.2.0-2
ii  gfortran-10 [gfortran-mod-15]  10.3.0-14
ii  gfortran-11 [gfortran-mod-15]  11.2.0-14
ii  gfortran-9 [gfortran-mod-15]   9.4.0-4+b1
ii  libmpich12 4.0-1
ii  mpich  4.0-1

libmpich-dev recommends no packages.

libmpich-dev suggests no packages.

-- no debconf information
docker run --rm -ti debian:sid  
   
[14:10]
Unable to find image 'debian:sid' locally
sid: Pulling from library/debian
48c02bc8c594: Pull complete 
Digest: sha256:0e6e082a988ec6f880c76864c68705f47e4af4a319e0a56d5a1817282767336c
Status: Downloaded newer image for debian:sid
root@23bd1ec5a8ce:/# apt update
Get:1 http://deb.debian.org/debian sid InRelease [165 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 Packages [8898 kB]
Fetched 9063 kB in 1s (8372 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@23bd1ec5a8ce:/# apt upgrade
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1 
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 bsdutils amd64 1:2.37.3-1+b1 
[149 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 util-linux amd64 2.37.3-1+b1 
[1200 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libc6 amd64 2.33-5 [2831 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libc-bin amd64 2.33-5 [834 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libsystemd0 amd64 250.3-2 
[404 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 mount amd64 2.37.3-1+b1 [191 
kB]
Get:7 http://deb.debian.org/debian sid/main amd64 libblkid1 amd64 2.37.3-1+b1 
[202 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 libgnutls30 amd64 3.7.3-4+b1 
[1377 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 libmount1 amd64 2.37.3-1+b1 
[220 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libsmartcols1 amd64 
2.37.3-1+b1 [162 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libudev1 amd64 250.3-2 [178 
kB]
Get:12 http://deb.debian.org/debian sid/main amd64 libuuid1 amd64 2.37.3-1+b1 
[85.4 kB]
Get:13 http://deb.debian.org/debian sid/main amd64 mawk amd64 
1.3.4.20200120-3+b1 [113 kB]
Fetched 7946 kB in 0s (73.9 MB/s)
debconf: delaying package configuration, since apt-utils is not 

Bug#978867: marked as done (mpich: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 16:34:17 +
with message-id 
and subject line Bug#978867: fixed in mpich 4.0-2
has caused the Debian Bug report #978867,
regarding mpich: ftbfs with autoconf 2.70
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.)


-- 
978867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpich
Version: 3.4~a2+really3.3.2-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/mpich_3.4~a2+really3.3.2-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
target_alias=''
target_cpu='x86_64'
target_os='linux-gnu'
target_vendor='pc'
ucxdir=''
ucxlib=''
use_embedded_hwloc_FALSE=''
use_embedded_hwloc_TRUE=''
with_libfabric='yes'
zmlib=''
zmlibdir=''
zmsrcdir=''

## --- ##
## File substitutions. ##
## --- ##

cc_shlib_conf=''
cxx_shlib_conf=''
f77_shlib_conf=''
fc_shlib_conf=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "MPICH"
#define PACKAGE_TARNAME "mpich"
#define PACKAGE_VERSION "3.3.2"
#define PACKAGE_STRING "MPICH 3.3.2"
#define PACKAGE_BUGREPORT "disc...@mpich.org"
#define PACKAGE_URL "http://www.mpich.org/;
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define __EXTENSIONS__ 1
#define _ALL_SOURCE 1
#define _DARWIN_C_SOURCE 1
#define _GNU_SOURCE 1
#define _POSIX_PTHREAD_SEMANTICS 1
#define __STDC_WANT_IEC_60559_ATTRIBS_EXT__ 1
#define __STDC_WANT_IEC_60559_BFP_EXT__ 1
#define __STDC_WANT_IEC_60559_DFP_EXT__ 1
#define __STDC_WANT_IEC_60559_FUNCS_EXT__ 1
#define __STDC_WANT_IEC_60559_TYPES_EXT__ 1
#define __STDC_WANT_LIB_EXT2__ 1
#define __STDC_WANT_MATH_SPEC_FUNCS__ 1
#define _TANDEM_SOURCE 1
#define PACKAGE "mpich"
#define VERSION "3.3.2"
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_ERROR_CHECKING MPID_ERROR_LEVEL_ALL
#define MPICH_ERROR_MSG_LEVEL MPICH_ERROR_MSG__ALL
#define HAVE_TAG_ERROR_BITS 1
#define USE_LOGGING MPICH_LOGGING__NONE

configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --with-libfabric 
--enable-shared --prefix=/usr --enable-fortran=all --disable-rpath 
--disable-wrapper-rpath --sysconfdir=/etc/mpich 
--libdir=/usr/lib/x86_64-linux-gnu 
--includedir=/usr/include/x86_64-linux-gnu/mpich --docdir=/usr/share/doc/mpich 
CPPFLAGS= CFLAGS= CXXFLAGS= "FFLAGS=-O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong  -fallow-invalid-boz -fallow-argument-mismatch" 
"FCFLAGS=-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong  
-fallow-invalid-boz -fallow-argument-mismatch" BASH_SHELL=/bin/bash returned 
exit code 1
make[1]: *** [debian/rules:83: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:70: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.0-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mpich package)

(This message was generated automatically at their 

Bug#1006162: marked as done (expat: autopkgtest regressions (from CVE-2022-25313 fix))

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 16:34:02 +
with message-id 
and subject line Bug#1006162: fixed in expat 2.4.5-2
has caused the Debian Bug report #1006162,
regarding expat: autopkgtest regressions (from CVE-2022-25313 fix)
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.)


-- 
1006162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: expat
Version: 2.4.5-1
Severity: serious
Justification: autopkgtest regression
X-Debbugs-Cc: car...@debian.org
Control: affects -1 
src:libxml-parser-perl,src:python2.7,src:python3.10,src;python3.9

Hi Laszlo,

There appears to be regressions from the CVE-2022-25313 fix in 2.4.5.
They are known already upstream, cf.
https://github.com/NixOS/nixpkgs/pull/160826#issuecomment-1046074523

I will hold of the planned expat security release until this is
addressed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: expat
Source-Version: 2.4.5-2
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated expat 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 Feb 2022 16:26:07 +0100
Source: expat
Architecture: source
Version: 2.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1006162
Changes:
 expat (2.4.5-2) unstable; urgency=medium
 .
   * Fix build_model regression (closes: #1006162).
Checksums-Sha1:
 750a1460795f60e88e4c9c08c2760b6d11cc69f2 1981 expat_2.4.5-2.dsc
 1bc9af10956db09870b1e959ecbede46d90af75b 16304 expat_2.4.5-2.debian.tar.xz
Checksums-Sha256:
 293a8909ba4fd7d55c23eef0e58193153632afde236ee804f7473175a33bcafb 1981 
expat_2.4.5-2.dsc
 1eb50e66fe814e7950e8d55214ac4373cb2caeac5ea3a983ab2fc1b2aa03c84b 16304 
expat_2.4.5-2.debian.tar.xz
Files:
 b0238efdc100a7c4dd30c317c83b3769 1981 text optional expat_2.4.5-2.dsc
 83ba4e45bcdd3ec8554d7eac6cdc222f 16304 text optional 
expat_2.4.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmISaRYACgkQ3OMQ54ZM
yL9djBAAqkRX0qbI5pE+r/NitvR1v7PsDzcQn3k31a3E3IroptmFz7LSKqqkq7br
jzy1NkstvtI62FyvWLm8rRLdkout1nsXisVOFl8mlbwe9USp7hEWZABTCYuNwCbx
urhy7vUDWg5dLQnlVem7NlF4beFmdwq/gsoYMJGvZuEl9QsTLeQPeWWKRc+KQMF8
U7ILz9pZW6moUtEslsi70dv2oOqDRW/7qB/HdK6pYhOv3pWbqAuKSoPK3lyPIyN5
doCQ9zPw9Q9v0C3TYhgO2Xc7N3/BbVx8E1BF+JjfUbB6kXYln+ZKXVjzjelphuAD
bb6ZbmeJHl/06XlQRzAr8zDalnAJkbi1nGpOoRMpHzQ1K3TUx7912mWB5V39szRl
nLAvI1n9NHKt6T+62N2xiB1Xx4K1s45tXWm/GL6Ra5z86SJx3giw3daimhIgXR5a
was8iLTLpI8D9AhcJnYDdxHT3KqJSveUDPQWvEoX2TKjjM0qqYj59UzXF0xWLv3C
Ow3Hc6BVbiWXs7GzDlwN0A8/H9lcJjS5rCnBZwF6W24ipSH9/9FfEDPluEKcyHFt
ldgDaOgckkq0zuYfKamhPJD7LO/WtuKqBzLMiSoc+Ew9P9FqRCs4QFXDUg0AKhmV
uaa35aniyEfncVYMF5E+TIoRwdgNF9Jvg6iUkRjHV+reMqrff6s=
=pZbQ
-END PGP SIGNATURE End Message ---

Processed: severity of 1006028 is important, tagging 1006028

[Debian Bug Tracking System]

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

> severity 1006028 important
Bug #1006028 [src:php-crypt-gpg] php-crypt-gpg: FTBFS: 
PHPUnit\Framework\Exception: PHP Fatal error: Uncaught 
Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect 
passphrase provided for keys: "First Keypair Test Key (do not encrypt important 
data with this key) ", 
"F27FB97E211A40BDD61FAD75E7493277280054C4", "First Keypair Test Key (do not 
encrypt important data with this key) ". in 
/<>/Crypt_GPG-1.6.7/Crypt/GPG/ProcessHandler.php on line 634
Severity set to 'important' from 'serious'
> tags 1006028 = pending
Bug #1006028 [src:php-crypt-gpg] php-crypt-gpg: FTBFS: 
PHPUnit\Framework\Exception: PHP Fatal error: Uncaught 
Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect 
passphrase provided for keys: "First Keypair Test Key (do not encrypt important 
data with this key) ", 
"F27FB97E211A40BDD61FAD75E7493277280054C4", "First Keypair Test Key (do not 
encrypt important data with this key) ". in 
/<>/Crypt_GPG-1.6.7/Crypt/GPG/ProcessHandler.php on line 634
Added tag(s) pending; removed tag(s) moreinfo, bookworm, sid, and ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1006149 is important

[Debian Bug Tracking System]

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

> severity 1006149 important
Bug #1006149 [src:linux] linux-image-5.16.0-1-686: Fails to boot on T41 
Thinkpads
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#1002428: marked as done (python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS) in dpkg-buildflags:)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 15:38:23 +
with message-id <4b1a809a-f560-4a93-8e5b-88303a8f7...@sceal.ie>
and subject line Fixed in last upload
has caused the Debian Bug report #1002428,
regarding python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS) in 
dpkg-buildflags:
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.)


-- 
1002428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-escript
Version: 5.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 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 '/<>'
> # Build steps for py3
> mkdir -p /<>/debian/stage3
> scons  -j4   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 
> verbose=on prefix=/<>/debian/stage3 
> options_file=debian/sid_options.py docs
> scons: Reading SConscript files ...
> 3.9.9 (main, Dec 16 2021, 23:13:29) 
> [GCC 11.2.0]
> RuntimeError: Unknown key (ASFLAGS) in dpkg-buildflags:
>   File "/<>/SConstruct", line 172:
> env = Environment(tools = ['default'], options = vars,
>   File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 982:
> variables.Update(self)
>   File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
> exec(contents, {}, values)
>   File "", line 84:
> 
>   File "/<>/site_scons/extractdebbuild.py", line 52:
> raise RuntimeError("Unknown key ("+key+") in dpkg-buildflags")
> make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/python-escript_5.6-3_unstable.log

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

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

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

 

Close 1002428

Thanks

 

--- End Message ---

Processed: Re: Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libwebp7 1.2.1-7
Bug #1006009 [src:qtimageformats-opensource-src] qtimageformats-opensource-src: 
FTBFS on mipsel: test failure
Bug reassigned from package 'src:qtimageformats-opensource-src' to 'libwebp7'.
No longer marked as found in versions qtimageformats-opensource-src/5.15.2-2.
Ignoring request to alter fixed versions of bug #1006009 to the same values 
previously set
Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test 
failure
Marked as found in versions libwebp/1.2.1-7.
> affects -1 src:qtimageformats-opensource-src
Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test 
failure
Added indication that 1006009 affects src:qtimageformats-opensource-src

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

Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure

[Dmitry Shachnev]

Control: reassign -1 libwebp7 1.2.1-7
Control: affects -1 src:qtimageformats-opensource-src

Hi Sebastian and libwebp maintainers!

On Fri, Feb 18, 2022 at 10:39:23PM +0100, Sebastian Ramacher wrote:
> Source: qtimageformats-opensource-src
> Version: 5.15.2-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
> qtimageformats-opensource-src FTBFS on mipsel:
>
> TIFFReadDirectory: Warning, Sum of Photometric type-related color channels 
> and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels 
> as ExtraSamples..
> TIFFReadDirectory: Warning, Sum of Photometric type-related color channels 
> and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels 
> as ExtraSamples..
> PASS   : tst_qtiff::tiffGrayscale()
> FAIL!  : tst_qwebp::writeImage(kollada_noalpha-100) '!reread.isNull()' 
> returned FALSE. ()
>Loc: [tst_qwebp.cpp(174)]
> PASS   : tst_qwebp::cleanupTestCase()
> Totals: 10 passed, 1 failed, 0 skipped, 0 blacklisted, 632ms
> * Finished testing of tst_qwebp *
>
> See
> https://buildd.debian.org/status/fetch.php?pkg=qtimageformats-opensource-src=mipsel=5.15.2-2%2Bb1=1645209225=0

It looks to me like a bug in new libwebp version: encoder generates broken
webp files on mipsel.

I can reproduce it without any Qt code by encoding the attached PNG file and
then trying to decode it back:

(sid_mipsel-dchroot)mitya57@eller:~$ cwebp kollada_noalpha.png -lossless -o 
kollada_noalpha.webp
Saving file 'kollada_noalpha.webp'
File:  kollada_noalpha.png
Dimension: 436 x 160
Output:37004 bytes (4.24 bpp)
Lossless-ARGB compressed size: 37004 bytes
  * Header size: 636 bytes, image data size: 36342
  * Precision Bits: histogram=3 transform=3 cache=1
(sid_mipsel-dchroot)mitya57@eller:~$ dwebp kollada_noalpha.webp
Decoding of kollada_noalpha.webp failed.
Status: 3(BITSTREAM_ERROR)

I am also attaching the generated broken WEBP file.

--
Dmitry Shachnev


kollada_noalpha.webp
Description: Binary data


signature.asc
Description: PGP signature

Bug#990201: marked as done (singularity-container: CVE-2021-33622)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 14:37:12 +
with message-id 
and subject line Bug#990201: fixed in singularity-container 3.9.5+ds1-1
has caused the Debian Bug report #990201,
regarding singularity-container: CVE-2021-33622
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.)


-- 
990201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for singularity-container.

CVE-2021-33622[0]:
| Sylabs Singularity 3.5.x and 3.6.x, and SingularityPRO before 3.5-8,
| has an Incorrect Check of a Function's Return Value.

Note that this differs from CVE-2021-32635.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-33622
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33622
[1] 
https://support.sylabs.io/support/solutions/articles/4287130-3-5-8-security-release-cve-2021-33622-

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 3.9.5+ds1-1
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated singularity-container 
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 Feb 2022 19:27:46 +0530
Source: singularity-container
Architecture: source
Version: 3.9.5+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Nilesh Patra 
Closes: 990201
Changes:
 singularity-container (3.9.5+ds1-1) experimental; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Version > 3.6.x are closing CVE-2021-33622
 Closes: #990201
   * Add debian/README.source with my findings about issues when trying
 to replace vendored code copies
   * Remove superfluous file patterns from d/copyright
   * Remove unneeded patches
   * Cleanup list of Files-Excluded
   * Drop Afif Elghraoui from Uploaders (thank you for your work Afif)
 .
   [ Nilesh Patra ]
   * d/copyright: Exclude more vendor copies
   * New upstream version 3.9.5+ds1
   * d/control: Add/update B-D for dropped vendor copies
   * Adapt patch to newer release
   * Drop d/README.source
Checksums-Sha1:
 7b1323b6a5f76a4cee1d5f26d88c7e509d55c266 4343 
singularity-container_3.9.5+ds1-1.dsc
 7cc7e465d90446cbd7cbe8eb32961253cb5b3fce 5717004 
singularity-container_3.9.5+ds1.orig.tar.xz
 fee90611e5b3d788276215e39290fe41f45faf8e 19512 
singularity-container_3.9.5+ds1-1.debian.tar.xz
 5ee0961e14ab231ea3ccaa44dd244010efae327f 24362 
singularity-container_3.9.5+ds1-1_amd64.buildinfo
Checksums-Sha256:
 1390c2126df9008620037d6e0fd567ff828646a0dfdce6531e09a29ba78e9f20 4343 
singularity-container_3.9.5+ds1-1.dsc
 929e38200b3d26d8f46200b9b8f57e91409fd07e26cb81ce5c27a41c4383e137 5717004 
singularity-container_3.9.5+ds1.orig.tar.xz
 d7cb55a4effed3ce0d97248e32b52b42d48435d58932d77ac2d325c27018893a 19512 
singularity-container_3.9.5+ds1-1.debian.tar.xz
 7a821cc16e161c6d94d0fe21e1a8b62434f525e86057d6ace27f8a15d5f48904 24362 
singularity-container_3.9.5+ds1-1_amd64.buildinfo
Files:
 ee4cb7986eb99b4242e4c64a5bcfc710 4343 admin optional 
singularity-container_3.9.5+ds1-1.dsc
 cd85c34e85a373d373db8b2242cd4847 5717004 admin optional 
singularity-container_3.9.5+ds1.orig.tar.xz
 471aa86b62b83e74df4539c2c6436f9d 19512 admin optional 
singularity-container_3.9.5+ds1-1.debian.tar.xz
 34f742a59371fb287d4834cc6ecc8f00 24362 admin optional 
singularity-container_3.9.5+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmISSzkSHG5pbGVzaEBk

Bug#997255: marked as done (qd: FTBFS: fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ declared void)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 14:49:10 +
with message-id 
and subject line Bug#997255: fixed in qd 2.3.23+dfsg.1-1
has caused the Debian Bug report #997255,
regarding qd: FTBFS: fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ 
declared void
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.)


-- 
997255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qd
Version: 2.3.22+dfsg.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile c++ -DHAVE_CONFIG_H   -I.. 
> -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3  -c -o fpu.lo fpu.cpp
> libtool: compile:  c++ -DHAVE_CONFIG_H -I.. -I../include -I../include 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O3 -c fpu.cpp  
> -fPIC -DPIC -o .libs/fpu.o
> fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ declared void
>   110 | #define f_fpu_fix_start FC_FUNC_(f_fpu_fix_start, F_FPU_FIX_START)
>   | ^~~~
> fpu.cpp:113:6: note: in expansion of macro ‘f_fpu_fix_start’
>   113 | void f_fpu_fix_start(unsigned int *old_cw) {
>   |  ^~~
> fpu.cpp:110:34: error: ‘f_fpu_fix_start’ was not declared in this scope
>   110 | #define f_fpu_fix_start FC_FUNC_(f_fpu_fix_start, F_FPU_FIX_START)
>   |  ^~~
> fpu.cpp:113:6: note: in expansion of macro ‘f_fpu_fix_start’
>   113 | void f_fpu_fix_start(unsigned int *old_cw) {
>   |  ^~~
> fpu.cpp:110:51: error: ‘F_FPU_FIX_START’ was not declared in this scope
>   110 | #define f_fpu_fix_start FC_FUNC_(f_fpu_fix_start, F_FPU_FIX_START)
>   |   ^~~
> fpu.cpp:113:6: note: in expansion of macro ‘f_fpu_fix_start’
>   113 | void f_fpu_fix_start(unsigned int *old_cw) {
>   |  ^~~
> fpu.cpp:111:25: error: variable or field ‘FC_FUNC_’ declared void
>   111 | #define f_fpu_fix_end   FC_FUNC_(f_fpu_fix_end,   F_FPU_FIX_END)
>   | ^~~~
> fpu.cpp:117:6: note: in expansion of macro ‘f_fpu_fix_end’
>   117 | void f_fpu_fix_end(unsigned int *old_cw) {
>   |  ^
> fpu.cpp:111:34: error: ‘f_fpu_fix_end’ was not declared in this scope
>   111 | #define f_fpu_fix_end   FC_FUNC_(f_fpu_fix_end,   F_FPU_FIX_END)
>   |  ^
> fpu.cpp:117:6: note: in expansion of macro ‘f_fpu_fix_end’
>   117 | void f_fpu_fix_end(unsigned int *old_cw) {
>   |  ^
> fpu.cpp:111:51: error: ‘F_FPU_FIX_END’ was not declared in this scope
>   111 | #define f_fpu_fix_end   FC_FUNC_(f_fpu_fix_end,   F_FPU_FIX_END)
>   |   ^
> fpu.cpp:117:6: note: in expansion of macro ‘f_fpu_fix_end’
>   117 | void f_fpu_fix_end(unsigned int *old_cw) {
>   |  ^
> make[3]: *** [Makefile:490: fpu.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/qd_2.3.22+dfsg.1-3_unstable.log

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

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated qd package)

(This message was generated automatically at their request; if you
believe that there is a 

Processed: bug 1006162 is forwarded to https://github.com/libexpat/libexpat/pull/566

[Debian Bug Tracking System]

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

> forwarded 1006162 https://github.com/libexpat/libexpat/pull/566
Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 
fix)
Set Bug forwarded-to-address to 'https://github.com/libexpat/libexpat/pull/566'.
> thanks
Stopping processing here.

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

Processed: src:opentsne: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6.1-2
Bug #1006177 [src:opentsne] src:opentsne: fails to migrate to testing for too 
long: FTBFS on i386
Marked as fixed in versions opentsne/0.6.1-2.
Bug #1006177 [src:opentsne] src:opentsne: fails to migrate to testing for too 
long: FTBFS on i386
Marked Bug as done
> block -1 by 1004706
Bug #1006177 {Done: Paul Gevers } [src:opentsne] 
src:opentsne: fails to migrate to testing for too long: FTBFS on i386
1006177 was not blocked by any bugs.
1006177 was not blocking any bugs.
Added blocking bug(s) of 1006177: 1004706

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

Bug#1006177: src:opentsne: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: opentsne
Version: 0.5.0-2
Severity: serious
Control: close -1 0.6.1-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004706

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=opentsne



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lua-system: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.2.1-5
Bug #1006176 [src:lua-system] src:lua-system: fails to migrate to testing for 
too long: autopkgtest regression
Marked as fixed in versions lua-system/0.2.1-5.
Bug #1006176 [src:lua-system] src:lua-system: fails to migrate to testing for 
too long: autopkgtest regression
Marked Bug as done
> block -1 by 1004099
Bug #1006176 {Done: Paul Gevers } [src:lua-system] 
src:lua-system: fails to migrate to testing for too long: autopkgtest regression
1006176 was not blocked by any bugs.
1006176 was not blocking any bugs.
Added blocking bug(s) of 1006176: 1004099

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

Bug#1006176: src:lua-system: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: lua-system
Version: 0.2.1-2
Severity: serious
Control: close -1 0.2.1-5
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004099

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lua-system



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lua-say: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3-1-7
Bug #1006175 [src:lua-say] src:lua-say: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions lua-say/1.3-1-7.
Bug #1006175 [src:lua-say] src:lua-say: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done
> block -1 by 1004098
Bug #1006175 {Done: Paul Gevers } [src:lua-say] src:lua-say: 
fails to migrate to testing for too long: autopkgtest regression
1006175 was not blocked by any bugs.
1006175 was not blocking any bugs.
Added blocking bug(s) of 1006175: 1004098

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

Bug#1006175: src:lua-say: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: lua-say
Version: 1.3-1-5
Severity: serious
Control: close -1 1.3-1-7
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004098

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lua-say



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lua-mediator: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.1.2-0-6
Bug #1006174 [src:lua-mediator] src:lua-mediator: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions lua-mediator/1.1.2-0-6.
Bug #1006174 [src:lua-mediator] src:lua-mediator: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1004097
Bug #1006174 {Done: Paul Gevers } [src:lua-mediator] 
src:lua-mediator: fails to migrate to testing for too long: autopkgtest 
regression
1006174 was not blocked by any bugs.
1006174 was not blocking any bugs.
Added blocking bug(s) of 1006174: 1004097

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

Bug#1006174: src:lua-mediator: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: lua-mediator
Version: 1.1.2-0-3
Severity: serious
Control: close -1 1.1.2-0-6
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004097

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lua-mediator



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006172: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: lepton-eda
Version: 1.9.16-3
Severity: serious
Control: close -1 1.9.17-2
X-Debbugs-CC: debian-s3...@lists.debian.org
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:lepton-eda has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package fails to build on 
s390x where it build successfully in the past. I've X-Debbugs-CC-ed the 
s390x porters to help you understand why only this architecture is affected.


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lepton-eda



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lua-cliargs: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0-2-4
Bug #1006173 [src:lua-cliargs] src:lua-cliargs: fails to migrate to testing for 
too long: autopkgtest regression
Marked as fixed in versions lua-cliargs/3.0-2-4.
Bug #1006173 [src:lua-cliargs] src:lua-cliargs: fails to migrate to testing for 
too long: autopkgtest regression
Marked Bug as done
> block -1 by 1004096
Bug #1006173 {Done: Paul Gevers } [src:lua-cliargs] 
src:lua-cliargs: fails to migrate to testing for too long: autopkgtest 
regression
1006173 was not blocked by any bugs.
1006173 was not blocking any bugs.
Added blocking bug(s) of 1006173: 1004096

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

Bug#1006173: src:lua-cliargs: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: lua-cliargs
Version: 3.0-2-1
Severity: serious
Control: close -1 3.0-2-4
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004096

Dear maintainer(s),

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


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lua-cliargs



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.9.17-2
Bug #1006172 [src:lepton-eda] src:lepton-eda: fails to migrate to testing for 
too long: FTBFS on s390x
Marked as fixed in versions lepton-eda/1.9.17-2.
Bug #1006172 [src:lepton-eda] src:lepton-eda: fails to migrate to testing for 
too long: FTBFS on s390x
Marked Bug as done

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

Processed: notfound 1005891 in 1.1.0+ds1-1

[Debian Bug Tracking System]

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

> notfound 1005891 1.1.0+ds1-1
Bug #1005891 {Done: Shengjing Zhu } [src:runc] runc: failing 
autopkgtest on one of ci.d.n amd64 workers
No longer marked as found in versions runc/1.1.0+ds1-1.
> thanks
Stopping processing here.

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

Bug#1005891: marked as done (runc: failing autopkgtest on one of ci.d.n amd64 workers)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 21:36:57 +0800
with message-id 

and subject line Re: Bug#1005891: runc: failing autopkgtest on one of ci.d.n 
amd64 workers
has caused the Debian Bug report #1005891,
regarding runc: failing autopkgtest on one of ci.d.n amd64 workers
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.)


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

Source: runc
Version: 1.1.0+ds1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on amd64
because with a recent upload of glibc the autopkgtest of runc
fails in testing. Recently (mid January) your packages started to fail 
regularly and it seems to me that the failures are related to the

worker that the test runs on. ci-worker13 fails, while the other workers
are OK. Obviously I'm not sure it's related, but this particular host is 
extremely powerful, 256 GB RAM and 48 cores.


Don't hesitate to contact us at debian...@lists.debian.org if you need
help debugging this issue.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/r/runc/18799590/log.gz

ok  github.com/opencontainers/runc/libcontainer/utils   0.005s
?   github.com/opencontainers/runc/types[no test files]
FAIL
dh_auto_test: error: cd _build && go test -vet=off -v -p 48 -tags 
seccomp github.com/opencontainers/runc 
github.com/opencontainers/runc/libcontainer 
github.com/opencontainers/runc/libcontainer/apparmor 
github.com/opencontainers/runc/libcontainer/capabilities 
github.com/opencontainers/runc/libcontainer/cgroups 
github.com/opencontainers/runc/libcontainer/cgroups/devices 
github.com/opencontainers/runc/libcontainer/cgroups/ebpf 
github.com/opencontainers/runc/libcontainer/cgroups/ebpf/devicefilter 
github.com/opencontainers/runc/libcontainer/cgroups/fs 
github.com/opencontainers/runc/libcontainer/cgroups/fs2 
github.com/opencontainers/runc/libcontainer/cgroups/fscommon 
github.com/opencontainers/runc/libcontainer/cgroups/systemd 
github.com/opencontainers/runc/libcontainer/configs 
github.com/opencontainers/runc/libcontainer/configs/validate 
github.com/opencontainers/runc/libcontainer/devices 
github.com/opencontainers/runc/libcontainer/intelrdt 
github.com/opencontainers/runc/libcontainer/keys 
github.com/opencontainers/runc/libcontainer/logs 
github.com/opencontainers/runc/libcontainer/nsenter 
github.com/opencontainers/runc/libcontainer/nsenter/test 
github.com/opencontainers/runc/libcontainer/seccomp 
github.com/opencontainers/runc/libcontainer/seccomp/patchbpf 
github.com/opencontainers/runc/libcontainer/specconv 
github.com/opencontainers/runc/libcontainer/stacktrace 
github.com/opencontainers/runc/libcontainer/system 
github.com/opencontainers/runc/libcontainer/user 
github.com/opencontainers/runc/libcontainer/userns 
github.com/opencontainers/runc/libcontainer/utils 
github.com/opencontainers/runc/types returned exit code 1
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.v97d589s/downtmp/autopkgtest_tmp'

make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25
make: *** [debian/rules:11: build] Error 2
autopkgtest [13:11:41]: test dh-golang-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: notfound -1 1.1.0+ds1-1

On Sun, Feb 20, 2022 at 8:47 PM Paul Gevers  wrote:
>
> Hi,
>
> On 20-02-2022 11:04, Shengjing Zhu wrote:
> > That's great to know. Could you retry runc's autopkgtest on
> > ci-worker13. If it succeeds, can we close this bug?
>
> I hit the retry button three times, two of those were executed on
> ci-worker13 and all three passed.
>

Thanks. I'm closing it now.

-- 
Shengjing Zhu--- End Message ---

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

[Paul Gevers]

Hi,

On 20-02-2022 11:04, Shengjing Zhu wrote:

That's great to know. Could you retry runc's autopkgtest on
ci-worker13. If it succeeds, can we close this bug?


I hit the retry button three times, two of those were executed on 
ci-worker13 and all three passed.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1001001 closed by Salvatore Bonaccorso (Re: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1001001 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/5.10.84-1.
> found -1 5.10.84-1
Bug #1001001 [src:linux] linux-image-5.10.0-9-arm64: kernel BUG at 
include/linux/swapops.h:204!
Marked as found in versions linux/5.10.84-1.

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

Bug#1001001: closed by Salvatore Bonaccorso (Re: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!)

[Paul Gevers]

Control: reopen -1
Control: found -1 5.10.84-1

Hi,

Sad to say, but this week we had two hangs again.

The one on ci-worker-arm64-06 had this:

Feb 15 08:51:12 ci-worker-arm64-06 kernel: kernel BUG at 
include/linux/swapops.h:204!
Feb 15 08:51:12 ci-worker-arm64-06 kernel: Internal error: Oops - BUG: 0 
[#1] SMP


root@ci-worker-arm64-06:~# uname -a
Linux ci-worker-arm64-06 5.10.0-10-arm64 #1 SMP Debian 5.10.84-1 
(2021-12-08) aarch64 GNU/Linux


I'm upgrading the workers to the latest kernel now.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bug 1005527 is forwarded to https://github.com/python-hyper/wsproto/issues/169, tagging 1005527

[Debian Bug Tracking System]

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

> forwarded 1005527 https://github.com/python-hyper/wsproto/issues/169
Bug #1005527 [src:python-wsproto] python-wsproto: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Set Bug forwarded-to-address to 
'https://github.com/python-hyper/wsproto/issues/169'.
> tags 1005527 + upstream fixed-upstream
Bug #1005527 [src:python-wsproto] python-wsproto: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#993241: marked as done (minidlna FTBFS: configure: error: Could not find libid3tag)

[Debian Bug Tracking System]

Your message dated Sun, 20 Feb 2022 10:50:27 +
with message-id 
and subject line Bug#993241: fixed in minidlna 1.3.0+dfsg-2.1
has caused the Debian Bug report #993241,
regarding minidlna FTBFS: configure: error: Could not find libid3tag
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.)


-- 
993241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minidlna
Version: 1.3.0+dfsg-2
Severity: serious
Tags: ftbfs

minidlna fails to build from source. The relevant parts of the build log
are:

| dh_auto_configure -- --with-os-version=Debian 
--with-log-path=/var/log/minidlna
|   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-os-version=Debian --with-log-path=/var/log/minidlna
| checking build system type... x86_64-pc-linux-gnu
| checking host system type... x86_64-pc-linux-gnu
| checking target system type... x86_64-pc-linux-gnu
| checking for a BSD-compatible install... /usr/bin/install -c
| checking whether build environment is sane... yes
| checking for a race-free mkdir -p... /bin/mkdir -p
| checking for gawk... no
| checking for mawk... mawk
| checking whether make sets $(MAKE)... yes
| checking whether make supports nested variables... yes
| checking whether make supports nested variables... (cached) yes
| checking whether make supports the include directive... yes (GNU style)
| checking for gcc... gcc
| checking whether the C compiler works... yes
| checking for C compiler default output file name... a.out
| checking for suffix of executables... 
| checking whether we are cross compiling... no
| checking for suffix of object files... o
| checking whether the compiler supports GNU C... yes
| checking whether gcc accepts -g... yes
| checking for gcc option to enable C11 features... none needed
| checking whether gcc understands -c and -o together... yes
| checking dependency style of gcc... none
| checking for stdio.h... yes
| checking for stdlib.h... yes
| checking for string.h... yes
| checking for inttypes.h... yes
| checking for stdint.h... yes
| checking for strings.h... yes
| checking for sys/stat.h... yes
| checking for sys/types.h... yes
| checking for unistd.h... yes
| checking for wchar.h... yes
| checking for minix/config.h... no
| checking for vfork.h... no
| checking whether it is safe to define __EXTENSIONS__... yes
| checking whether _XOPEN_SOURCE should be defined... no
| checking for ld used by GCC... /usr/bin/ld
| checking if the linker (/usr/bin/ld) is GNU ld... yes
| checking for shared library run path origin... done
| checking how to run the C preprocessor... gcc -E
| checking for grep that handles long lines and -e... /bin/grep
| checking for egrep... /bin/grep -E
| checking for iconv... yes
| checking for working iconv... yes
| checking for iconv declaration... 
|  extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, 
char * *outbuf, size_t *outbytesleft);
| checking whether NLS is requested... yes
| checking for msgfmt... /usr/bin/msgfmt
| checking for gmsgfmt... /usr/bin/msgfmt
| checking for xgettext... /usr/bin/xgettext
| checking for msgmerge... /usr/bin/msgmerge
| checking for CFPreferencesCopyAppValue... no
| checking for CFLocaleCopyCurrent... no
| checking for GNU gettext in libc... yes
| checking whether to use NLS... yes
| checking where the gettext function comes from... libc
| checking for gawk... (cached) mawk
| checking for gcc... (cached) gcc
| checking whether the compiler supports GNU C... (cached) yes
| checking whether gcc accepts -g... (cached) yes
| checking for gcc option to enable C11 features... (cached) none needed
| checking whether gcc understands -c and -o together... (cached) yes
| checking dependency style of gcc... (cached) none
| checking whether ln -s works... yes
| checking whether make sets $(MAKE)... (cached) yes
| checking for inline... inline
| checking for mode_t... yes
| checking for off_t... yes
| checking for pid_t... yes
| checking for size_t... yes
| checking for uint8_t... yes
| checking for int32_t... yes
| checking for uint32_t... yes
| checking for uint64_t... yes
| checking for ssize_t... yes
| checking for dirent.h that defines DIR... yes
| checking for library containing opendir... none required
| checking for struct 

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

[Shengjing Zhu]

On Sun, Feb 20, 2022 at 6:00 PM Paul Gevers  wrote:
>
> Hi,
>
> On 20-02-2022 09:20, Shengjing Zhu wrote:
> > It's because ci-worker13 still runs on the buster kernel.
> >
> > Any chance we can upgrade ci-worker13 to bullseye? So we can have a
> > consistent testbed. Otherwise I can work around that by disabling
> > relevant failed tests.
>
> That wasn't possible until a couple of days ago. Coincidentally I did
> this yesterday.
>

That's great to know. Could you retry runc's autopkgtest on
ci-worker13. If it succeeds, can we close this bug?

-- 
Shengjing Zhu

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

[Paul Gevers]

Hi,

On 20-02-2022 09:20, Shengjing Zhu wrote:

It's because ci-worker13 still runs on the buster kernel.

Any chance we can upgrade ci-worker13 to bullseye? So we can have a
consistent testbed. Otherwise I can work around that by disabling
relevant failed tests.


That wasn't possible until a couple of days ago. Coincidentally I did 
this yesterday.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: ruby3.0 defaults

[Debian Bug Tracking System]

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

> block 1004915 by 1005448
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1006119 1001217 1001022 998499 1005947
1004915 was not blocking any bugs.
Added blocking bug(s) of 1004915: 1005448
> block 1004915 by 1005426
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 998499 1001022 1006119 1005448 1001217 1005947
1004915 was not blocking any bugs.
Added blocking bug(s) of 1004915: 1005426
> thanks
Stopping processing here.

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

Processed: ruby3.0 defaults

[Debian Bug Tracking System]

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

> block 1004915 by 1001022
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1005947 1001217
1004915 was blocking: 1006119
Added blocking bug(s) of 1004915: 1001022
> block 1004915 by 998499
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1005947 1001022 1001217
1004915 was blocking: 1006119
Added blocking bug(s) of 1004915: 998499
> unblock 1006119 by 1004915
Bug #1006119 [src:uwsgi] uwsgi: FTBFS with ruby3.0 as default
1006119 was blocked by: 1004915
1006119 was not blocking any bugs.
Removed blocking bug(s) of 1006119: 1004915
> block 1004915 by 1006119
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1005947 998499 1001022 1001217
1004915 was not blocking any bugs.
Added blocking bug(s) of 1004915: 1006119
> thanks
Stopping processing here.

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

Bug#995224: [Debian-med-packaging] Bug#995224: relion-cuda: FTBFS with cub 1.14

[Sascha Steinbiss]

Hi Andreas,

thanks for your quick reply!

On 19.02.22 22:17, Andreas Beckmann wrote:
> On 19/02/2022 20.13, Sascha Steinbiss wrote:
>>     79 | #error The version of CUB in your include path is not compatible
>> with this release of Thrust. CUB is now included in the CUDA Toolkit, so
>> you no longer need to use your own checkout of CUB. Define
>> THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
>>    |  ^
> 
> Currently thrust and cub are out of sync. I got somewhat distracted ...
> trying to add some autopkg tests.
> But this bug points out that thrust should have a tighter dependency on
> cub (not only >= upstreamversion , but also << upstreamversion+1).
> 
> If you want to blame anything, it's thrust.

OK, got it. Just wanted to find out if there's anything I can do from
the relion packaging side. Will take a break from working on this then
until this is sorted out.

Thanks and best wishes
Sascha

Bug#1006149: linux-image-5.16.0-1-amd64: [RKL] hard lock during init with >1 connected displays & 0500 chipset

[Felix Miata]

Package: src:linux
Version: 5.16.7-2
Followup-For: Bug #1006149

Upstream fix is in 5.17rc4 per
https://gitlab.freedesktop.org/drm/intel/-/issues/4762
CPU, chipset and IGP were all released >5 months prior to Bullseye release, 
early 2021.

-- Package-specific info:
** Version:
Linux version 5.16.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-16) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37.90.20220130) #1 SMP 
PREEMPT Debian 5.16.7-2 (2022-02-09)

** Command line:
BOOT_IMAGE=/vmlinuz root=LABEL=tm8p10deb12 noresume ipv6.disable=1 
net.ifnames=0 mitigations=auto consoleblank=0 video=1440x900@60 5

** Not tainted

** Kernel log:
log ends [5.300511] e1000e :00:1f.6 eth0: NIC Link is Up 1000...

** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1203
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME B560M-A
board_version: Rev 1.xx

** Loaded modules:
nfsv3
rpcsec_gss_krb5
nfsv4
dns_resolver
nfs
fscache
netfs
hid_generic
usbhid
hid
intel_rapl_msr
intel_rapl_common
snd_hda_codec_hdmi
snd_hda_codec_realtek
eeepc_wmi
asus_wmi
platform_profile
ppdev
snd_hda_codec_generic
mei_hdcp
iTCO_wdt
intel_pmc_bxt
ee1004
iTCO_vendor_support
watchdog
battery
sparse_keymap
rfkill
wmi_bmof
snd_sof_pci_intel_tgl
snd_sof_intel_hda_common
soundwire_intel
soundwire_generic_allocation
soundwire_cadence
snd_sof_intel_hda
snd_sof_pci
snd_sof_xtensa_dsp
x86_pkg_temp_thermal
snd_sof
intel_powerclamp
i915
snd_soc_hdac_hda
snd_hda_ext_core
snd_soc_acpi_intel_match
snd_soc_acpi
snd_soc_core
snd_compress
soundwire_bus
coretemp
ledtrig_audio
crc32_pclmul
ghash_clmulni_intel
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
aesni_intel
ahci
snd_hda_core
crypto_simd
ttm
libahci
cryptd
xhci_pci
snd_hwdep
xhci_hcd
drm_kms_helper
libata
intel_cstate
snd_pcm
e1000e
usbcore
snd_timer
cec
intel_uncore
scsi_mod
mei_me
snd
rc_core
mei
intel_lpss_pci
i2c_i801
i2c_algo_bit
intel_lpss
ptp
soundcore
idma64
usb_common
efi_pstore
pps_core
pcspkr
i2c_smbus
scsi_common
wmi
parport_pc
parport
video
intel_pmc_core
acpi_pad
acpi_tad
button
nfsd
auth_rpcgss
nfs_acl
lockd
grace
drm
fuse
sunrpc
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
nvme
nvme_core
t10_pi
crc_t10dif
evdev
crct10dif_generic
crct10dif_pclmul
crc32c_intel
serio_raw
crct10dif_common
fan

00:02.0 VGA compatible controller [0300]: Intel Corporation RocketLake-S GT1 
[UHD Graphics 730] [8086:4c8b] (rev 04) (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. RocketLake-S GT1 [UHD Graphics 730] 
[1043:8694]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-H Shared SRAM 
[8086:43ef] (rev 11)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Tiger Lake-H Shared SRAM [1043:8694]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

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

Kernel: Linux 5.16.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-5.16.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod29-1
ii  linux-base  4.8

Versions of packages linux-image-5.16.0-1-amd64 recommends:
pn  apparmor 
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.16.0-1-amd64 suggests:
pn  debian-kernel-handbook   
pn  grub-pc | grub-efi-amd64 | extlinux  
pn  linux-doc-5.16   

Versions of packages linux-image-5.16.0-1-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
ii  firmware-intel-sound  20210818-1
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Petra R.-P.]

Hello Diederik,

Thanks for your quick reply:

Am Sa., 19. Feb. 2022, um 22:36 +0100 schrieb Diederik de Haas 
:
> On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote:
> > Package: src:linux
> > Version: 5.16.7-2
[...]
> > pn  firmware-iwlwifi  
> 
> I see you don't have firmware-iwlwifi installed, but there have been other 
> bug 
> reports which could be similar, so with the 5.15 kernel, do you have the 
> 'iwlwifi' kernel module loaded?

On one of the old Thinkpads in question, running the 5.15 kernel:

  ~ > lsmod | grep iwlwifi
  ~ > lsmod | grep wifi
  ~ >

So I suppose that module is _not_ loaded ...

> If so, could you blacklist that and try to 
> reboot into the 5.16 kernel and see whether it then works?

Nevertheless, I created /etc/modprobe.d/blacklist.conf as root, and:

  ~ > cat  /etc/modprobe.d/blacklist.conf
  blacklist iwlwifi
  ~ >

Sadly, this has no effect whatsoever on the 5.16.0-1 kernel.
When trying to boot it it 'hangs' exactly as before.

Thanks all the same, and best regards,
 
 Petra

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

[Shengjing Zhu]

On Thu, Feb 17, 2022 at 4:39 AM Paul Gevers  wrote:
>
> Source: runc
> Version: 1.1.0+ds1-1
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: flaky
>
> Dear maintainer(s),
>
> I looked at the results of the autopkgtest of you package on amd64
> because with a recent upload of glibc the autopkgtest of runc
> fails in testing. Recently (mid January) your packages started to fail
> regularly and it seems to me that the failures are related to the
> worker that the test runs on. ci-worker13 fails, while the other workers
> are OK. Obviously I'm not sure it's related, but this particular host is
> extremely powerful, 256 GB RAM and 48 cores.

It's because ci-worker13 still runs on the buster kernel.

Any chance we can upgrade ci-worker13 to bullseye? So we can have a
consistent testbed. Otherwise I can work around that by disabling
relevant failed tests.

-- 
Shengjing Zhu