Bug#1025771: marked as done (python3-matplotlib: package delivers jquery-1.7.1 whith XSS Vulnerability known from CVE-2012-6708)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 22:10:00 -0500
with message-id 

and subject line Re: Bug#1025771: python3-matplotlib: package delivers 
jquery-1.7.1 whith XSS Vulnerability known from CVE-2012-6708
has caused the Debian Bug report #1025771,
regarding python3-matplotlib: package delivers jquery-1.7.1 whith XSS 
Vulnerability known from CVE-2012-6708
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.)


-- 
1025771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-matplotlib Version: 3.3.4-1 Severity: normal Dear 
Maintainer,


is there a specific reason for 
matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js 
CVE-2012-6708 XSS Vulnerability jQuery < 1.9.0 XSS Vulnerability 



found vulnerable jquery version

Expected jquery version >1.9.0

python3-matplotlib_3.5.2-4 also affected

-- System Information: Debian Release: 11.5  APT prefers stable-updates 
 APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.74-1-pve (SMP 
w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: 
LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via 
/run/systemd/system) LSM: AppArmor: enabled Versions of packages 
python3-matplotlib depends on: ii  libc6 
  2.31-13+deb11u5 ii  libfreetype6 
   2.10.4+dfsg-1+deb11u1 ii  libgcc-s1 
  10.2.1-6 ii  libjs-jquery 
   3.5.1+dfsg+~3.5.5-7 ii  libjs-jquery-ui 
1.12.1+dfsg-8+deb11u1 ii  libstdc++6 
 10.2.1-6 ii  python-matplotlib-data 
 3.3.4-1 ii  python3 3.9.2-3 ii 
 python3-cycler  0.10.0-3 ii  python3-dateutil 
   2.8.1-6 ii  python3-kiwisolver 
 1.3.1-1+b1 ii  python3-numpy [python3-numpy-abi9] 
 1:1.19.5-1 ii  python3-pil 
8.1.2+dfsg-0.3+deb11u1 ii  python3-pyparsing 
  2.4.7-1 ii  python3-six 
1.16.0-2 Versions of packages 
python3-matplotlib recommends: ii  python3-tk  3.9.2-1 Versions of 
packages python3-matplotlib suggests: pn  dvipng  
pn  ffmpeg  pn  ghostscript     pn 
 gir1.2-gtk-3.0  pn  inkscape    pn 
 ipython3    ii  librsvg2-common    2.50.3+dfsg-1 
pn  python-matplotlib-doc   pn  python3-cairocffi   pn 
 python3-gi  pn  python3-gi-cairo    pn 
 python3-gobject     pn  python3-nose    pn 
 python3-pyqt5   pn  python3-scipy   pn 
 python3-sip     pn  python3-tornado     pn 
 texlive-extra-utils     pn  texlive-latex-extra     pn 
 ttf-staypuft    -- no debconf information
--- End Message ---
--- Begin Message ---
first of all, please format your bug reports appropriately, it is
really hard to read.

On Thu, Dec 8, 2022 at 3:33 PM  wrote:
>
> Package: python3-matplotlib Version: 3.3.4-1 Severity: normal Dear Maintainer,
>
> is there a specific reason for 
> matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js CVE-2012-6708 
> XSS Vulnerability jQuery < 1.9.0 XSS Vulnerability

did you look at the file? that's actually a symlink to what
libjs-jquery provides.

$ ls -l 
/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js
lrwxrwxrwx 1 root root 61 Jan  1  2022
/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js
-> ../../../../../../../../share/javascript/jquery/jquery.min.js

> ii  libjs-jquery3.5.1+dfsg+~3.5.5-7

this is the libjs-query you have installed so that's also the version mpl uses.

not a bug, closing.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Processed: merge 1020018 1025733

[Debian Bug Tracking System]

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

> forcemerge 1020018 1025733
Bug #1020018 {Done: Nicolas Boulenguez } [src:libxmlada] 
libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but 
15.0.0-1 is to be installed
Bug #1025733 [src:libxmlada] libxmlada: unsatisfiable buil-dependency on 
unicode-data
Marked Bug as done
Marked as fixed in versions libxmlada/23.0.0-1.
Added tag(s) bookworm, sid, experimental, and ftbfs.
Merged 1020018 1025733
> thanks
Stopping processing here.

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

Bug#1026289: marked as done (surf: The app opens, only displays a blank page)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 23:18:25 +0100
with message-id 
and subject line Re: Bug#1026289: surf: The app opens, only displays a blank 
page
has caused the Debian Bug report #1026289,
regarding surf: The app opens, only displays a blank page
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.)


-- 
1026289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: surf
Version: 2.1+git20221016-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: marathon.duran...@gmail.com 

Dear Maintainer,

On startup no content is displayed, simply a white blank window. The
window doesn't accept any mouse input. Error message when launching from
the console:

** (surf:6798): WARNING **: 14:38:03.031: Could not open 
/sys/class/dmi/id/chassis_type: Failed to open file 
“/sys/class/dmi/id/chassis_type”: Permission denied

** (surf:6798): WARNING **: 14:38:03.031: Could not open 
/sys/firmware/acpi/pm_profile: Failed to open file 
“/sys/firmware/acpi/pm_profile”: Permission denied

I'm running it as the regular logged in user. Thanks for looking at
this.

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

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

Versions of packages surf depends on:
ii  libc6   2.36-6
ii  libgcr-base-3-1 3.41.1-1+b1
ii  libgcr-ui-3-1   3.41.1-1+b1
ii  libglib2.0-02.74.2-1
ii  libgtk-3-0  3.24.35-3
ii  libjavascriptcoregtk-4.1-0  2.38.2-1+b1
ii  libwebkit2gtk-4.1-0 2.38.2-1+b1
ii  libx11-62:1.8.1-2

Versions of packages surf recommends:
ii  curl7.86.0-2
ii  lxterminal [x-terminal-emulator]0.4.0-2
ii  rxvt-unicode [x-terminal-emulator]  9.30-2+b3
ii  suckless-tools  46-2
ii  x11-utils   7.7+5

Versions of packages surf suggests:
ii  apparmor  3.0.8-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Steve,

On Sat, Dec 17, 2022 at 02:44:27PM -0500, Steve wrote:
> On startup no content is displayed, simply a white blank window. The
> window doesn't accept any mouse input. Error message when launching from
> the console:
> 
> ** (surf:6798): WARNING **: 14:38:03.031: Could not open 
> /sys/class/dmi/id/chassis_type: Failed to open file 
> “/sys/class/dmi/id/chassis_type”: Permission denied
> 
> ** (surf:6798): WARNING **: 14:38:03.031: Could not open 
> /sys/firmware/acpi/pm_profile: Failed to open file 
> “/sys/firmware/acpi/pm_profile”: Permission denied
> 
> I'm running it as the regular logged in user. Thanks for looking at
> this.

These two messages are not really errors. It's just a warning that it
can't access some files due to AppArmor restrictions, but they are not
needed for operation.

Having a blank window when starting surf without any arguments is
normal behavior. Please have a look at the manpage [0] to read how
to use it. For example you can call it directly with a URL:
 $ surf debian.org
Or when it is already running, you can press CTRL+g to open a URL.

Kind regards,
  Reiner


[0] https://manpages.debian.org/bullseye/surf/surf.1.en.html--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1025326 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of 
libgl1-mesa-dri to 22.3.0 breaks Xvnc
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819'.
> affects 1025326 = src:njplot src:juce src:clutter-1.0 src:ibus-cangjie 
> src:cogl src:pyopengl src:gnome-builder src:muffin src:gtk+3.0 src:glibc 
> src:openscad src:gtk4 src:keyman src:kodi src:gsequencer src:mutter xvfb
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of 
libgl1-mesa-dri to 22.3.0 breaks Xvnc
Added indication that 1025326 affects src:gsequencer, src:gtk4, src:muffin, 
src:clutter-1.0, src:glibc, src:ibus-cangjie, xvfb, src:openscad, src:njplot, 
src:keyman, src:gtk+3.0, src:gnome-builder, src:juce, src:pyopengl, src:mutter, 
src:cogl, and src:kodi
> forcemerge 1025312 1025326
Bug #1025312 {Done: Timo Aaltonen } [libgl1-mesa-dri] 
libgl1-mesa-dri: multiple packages FTBFS and have autopkgtest regressions 
running test programs under Xvfb
Bug #1025324 {Done: Timo Aaltonen } [libgl1-mesa-dri] 
libc6: Xserver with nouveau not workiing.
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of 
libgl1-mesa-dri to 22.3.0 breaks Xvnc
1025839 was blocked by: 1025312 1025324
1025839 was not blocking any bugs.
Added blocking bug(s) of 1025839: 1025326
1025308 was blocked by: 1025312 1025324
1025308 was not blocking any bugs.
Added blocking bug(s) of 1025308: 1025326
1025363 was blocked by: 1025312 1025324
1025363 was not blocking any bugs.
Added blocking bug(s) of 1025363: 1025326
1025308 was blocked by: 1025324 1025326 1025312
1025308 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1025308 to the same blocks 
previously set
1025839 was blocked by: 1025324 1025326 1025312
1025839 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1025839 to the same blocks 
previously set
1025332 was blocked by: 1025312 1025324
1025332 was not blocking any bugs.
Added blocking bug(s) of 1025332: 1025326
Marked Bug as done
Removed indication that 1025326 affects src:gtk+3.0, src:keyman, 
src:gnome-builder, src:openscad, src:njplot, src:kodi, src:juce, src:pyopengl, 
src:cogl, src:mutter, src:muffin, src:gtk4, src:clutter-1.0, src:glibc, 
src:gsequencer, xvfb, and src:ibus-cangjie
Added indication that 1025326 affects 
src:glibc,src:keyman,src:mutter,src:gtk+3.0,src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:kodi,src:openscad,src:gtk4,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot
Marked as found in versions mesa/22.3.0~rc4-1.
Bug #1025324 {Done: Timo Aaltonen } [libgl1-mesa-dri] 
libc6: Xserver with nouveau not workiing.
Removed indication that 1025324 affects src:cogl, src:mutter, src:pyopengl, 
src:juce, src:kodi, src:njplot, src:openscad, src:gnome-builder, src:keyman, 
src:gtk+3.0, xvfb, src:ibus-cangjie, src:gsequencer, src:glibc, 
src:clutter-1.0, src:gtk4, and src:muffin
Added indication that 1025324 affects 
src:glibc,src:keyman,src:mutter,src:gtk+3.0,src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:kodi,src:openscad,src:gtk4,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot
Removed indication that 1025312 affects xvfb, src:ibus-cangjie, src:gsequencer, 
src:muffin, src:gtk4, src:clutter-1.0, src:glibc, src:juce, src:pyopengl, 
src:cogl, src:mutter, src:kodi, src:openscad, src:njplot, src:gtk+3.0, 
src:keyman, and src:gnome-builder
Added indication that 1025312 affects 
src:glibc,src:keyman,src:mutter,src:gtk+3.0,src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:kodi,src:openscad,src:gtk4,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot
Merged 1025312 1025324 1025326
>
End of message, stopping processing here.

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

Bug#1026240: marked as done ([deluge] crashes on load)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 20:10:52 +
with message-id <7aa6ad5ad06a51bf99c646cea95a9009fb677df2.ca...@gmail.com>
and subject line Re: [deluge] crashes on load
has caused the Debian Bug report #1026240,
regarding [deluge] crashes on load
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.)


-- 
1026240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: deluge
Version: 2.0.3-3.2
Severity: grave

Worked yesterday, now won't start.

Loading in a terminal reveals the following output:

Traceback (most recent call last):
  File "/usr/bin/deluge", line 33, in 
sys.exit(load_entry_point('deluge==2.0.3', 'gui_scripts', 'deluge')())
  File "/usr/lib/python3/dist-packages/deluge/ui/ui_entry.py", line 143, in 
start_ui
ui.start()
  File "/usr/lib/python3/dist-packages/deluge/ui/gtk3/__init__.py", line 43, in 
start
from .gtkui import GtkUI
  File "/usr/lib/python3/dist-packages/deluge/ui/gtk3/gtkui.py", line 27, in 

from twisted.internet import defer, gtk3reactor
  File "/usr/lib/python3/dist-packages/twisted/internet/gtk3reactor.py", line 
22, in 
from twisted.internet import gireactor
  File "/usr/lib/python3/dist-packages/twisted/internet/gireactor.py", line 27, 
in 
from twisted.internet import _glibbase
  File "/usr/lib/python3/dist-packages/twisted/internet/_glibbase.py", line 19, 
in 
from twisted.internet import base, posixbase, selectreactor
  File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 19, 
in 
from twisted.internet import error, tcp, udp
  File "/usr/lib/python3/dist-packages/twisted/internet/tcp.py", line 38, in 

from twisted.internet._newtls import (
  File "/usr/lib/python3/dist-packages/twisted/internet/_newtls.py", line 18, 
in 
from twisted.protocols.tls import TLSMemoryBIOFactory, TLSMemoryBIOProtocol
  File "/usr/lib/python3/dist-packages/twisted/protocols/tls.py", line 50, in 

Connection(Context(TLSv1_METHOD), None)
  File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 674, in __init__
res = _lib.SSL_CTX_set_ecdh_auto(context, 1)
AttributeError: module 'lib' has no attribute 'SSL_CTX_set_ecdh_auto'
--- End Message ---
--- Begin Message ---
Turns out the cause was #1026215 which has now been fixed, so this can
be closed.--- End Message ---

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reassign 1025326 mesa 22.3.0-1
Bug #1025326 [tigervnc-standalone-server] tigervnc-standalone-server: Upgrade 
of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Bug reassigned from package 'tigervnc-standalone-server' to 'mesa'.
No longer marked as found in versions tigervnc/1.12.0+dfsg-5.
Ignoring request to alter fixed versions of bug #1025326 to the same values 
previously set
Bug #1025326 [mesa] tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 
22.3.0 breaks Xvnc
There is no source info for the package 'mesa' at version '22.3.0-1' with 
architecture ''
Unable to make a source version for version '22.3.0-1'
Marked as found in versions 22.3.0-1.
> severity 1025326 grave
Bug #1025326 [mesa] tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 
22.3.0 breaks Xvnc
Severity set to 'grave' from 'normal'
> close 1025326 22.3.0-2
Bug #1025326 [mesa] tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 
22.3.0 breaks Xvnc
There is no source info for the package 'mesa' at version '22.3.0-2' with 
architecture ''
Unable to make a source version for version '22.3.0-2'
Marked as fixed in versions 22.3.0-2.
Bug #1025326 [mesa] tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 
22.3.0 breaks Xvnc
Marked Bug as done
> merge 1025312 1025326
Bug #1025312 {Done: Timo Aaltonen } [libgl1-mesa-dri] 
libgl1-mesa-dri: multiple packages FTBFS and have autopkgtest regressions 
running test programs under Xvfb
Bug #1025324 {Done: Timo Aaltonen } [libgl1-mesa-dri] 
libc6: Xserver with nouveau not workiing.
Unable to merge bugs because:
forwarded of #1025326 is '' not 
'https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819'
blocks of #1025326 is '' not '1025308 1025332 1025363 1025839'
affects of #1025326 is '' not 
'src:glibc,src:keyman,src:mutter,src:gtk+3.0,src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:kodi,src:openscad,src:gtk4,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot'
package of #1025326 is 'mesa' not 'libgl1-mesa-dri'
affects of #1025324 is 
'src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:glibc,src:keyman,src:mutter,src:gtk+3.0,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot,src:kodi,src:openscad,src:gtk4'
 not 
'src:glibc,src:keyman,src:mutter,src:gtk+3.0,src:muffin,src:juce,src:cogl,src:pyopengl,src:gnome-builder,src:kodi,src:openscad,src:gtk4,xvfb,src:gsequencer,src:clutter-1.0,src:ibus-cangjie,src:njplot'
Failed to merge 1025312: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Processed: closing 975596

[Debian Bug Tracking System]

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

> close 975596
Bug #975596 [python3-paramiko] dput-ng: traceback with ssh-upload when 
python3-gssapi is installed
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#896056: marked as done (python-paramiko: SSH key login fails since 2.0.0)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:00:37 -0500
with message-id 

and subject line Re: Further information
has caused the Debian Bug report #896056,
regarding python-paramiko: SSH key login fails since 2.0.0
to be marked as done.

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

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


-- 
896056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-paramiko
Version: 2.4.0-1
Severity: important

Dear Maintainer,

I use SSH keys on a PKCS#11 smart card (via OpenSC) to authenticate to various 
machines via SSH.
I also use Fabric to automate certain tasks on some remote machines and have 
been doing so since Jessie. It worked fine then.
Ever since upgrading to Stretch, Fabric can no longer authenticate to remote 
machines, either with my SSH key or my correct password, while normal direct 
ssh continues to work correctly with keys (and passwords if I remove keys from 
the agent.)
(Fabric uses the Paramiko library to make its SSH connections.)

Running ssh-agent in debug mode shows the error "process_sign_request2: 
sshkey_sign: error in libcrypto" when paramiko attempts to authenticate to the 
remote host, itself saying "SSHException: key cannot be used for signing".

It does this on the second key on my card while the fourth one is the correct 
one for a particular remote machine. It lists that it is trying the other keys 
but gives no further debug information about them.

Running ssh -vvv  does not show any such error about signing 
when it tries that same key. (The server just rejects it so the client moves on 
to the next key.)

My ssh-agent is linked against libssl 1.0.2.

#paramiko on Freenode mentioned that Paramiko v2.0.0 changed their dependency 
from PyCrypto to cryptography.io which may be related.


-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-paramiko depends on:
ii  python   2.7.13-2
ii  python-bcrypt3.1.2-1
ii  python-cryptography  1.7.1-3
ii  python-nacl  1.0.1-2
ii  python-pyasn10.1.9-2

python-paramiko recommends no packages.

Versions of packages python-paramiko suggests:
pn  python-gssapi  

-- no debconf information
--- End Message ---
--- Begin Message ---
> For further testing, I did the following:
>
> sudo dpkg -r python-paramiko
> pip install paramiko==1.18.5
>
> And the problem still appears just the same as with a newer Paramiko.
> (Does that mean this problem is not related to Paramiko then?)

very likely, also this bug report is 4 years old and in the meantime
there has been no updates to it and paramiko was updated several
times. Please retry on an up-to-date debian machine and reopen if the
problem still happens and it is indeed related to paramiko. closting--- End Message ---

Bug#1025531: marked as done (transition: elpi 1.16.8-1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 19:26:16 +0100
with message-id 
and subject line Re: Bug#1025531: transition: elpi 1.16.8-1
has caused the Debian Bug report #1025531,
regarding transition: elpi 1.16.8-1
to be marked as done.

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

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


-- 
1025531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: jpu...@debian.org
X-Debbugs-Cc: Debian OCaml Maintainers


A new upstream version of elpi is out ; it requires rebuilding all
depending packages:

 nmu coq-elpi_1.16.0-1+b2 . ANY . -m 'Rebuild because of upload of
elpi=1.16.8-1'
 dw coq-elpi_1.16.0-1+b2 . ANY . -m 'elpi >= 1.16.8-1'
 nmu coq-hierarchy-builder_1.4.0-2+b4 . ANY . -m 'Rebuild because of
upload of coq-elpi=1.16.0-1+b2'
 dw coq-hierarchy-builder_1.4.0-2+b4 . ANY . -m 'coq-elpi >= 1.16.0-
1+b2'
 nmu mathcomp-algebra-tactics_1.0.0-8+b4 . ANY . -m 'Rebuild because of
upload of coq-elpi=1.16.0-1+b2'
 dw mathcomp-algebra-tactics_1.0.0-8+b4 . ANY . -m 'coq-elpi >= 1.16.0-
1+b2'
 nmu mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'Rebuild because of upload
of coq-hierarchy-builder=1.4.0-2+b4 coq-elpi=1.16.0-1+b2'
 dw mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'coq-hierarchy-builder >=
1.4.0-2+b4'
 dw mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'coq-elpi >= 1.16.0-1+b2'


I'm waiting for the "go!" signal to upload elpi 1.16.8-1.

Cheers,

J.Puydt
--- End Message ---
--- Begin Message ---
On 2022-12-06 23:55:57 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2022-12-06 10:42:46 +0100, julien.pu...@gmail.com wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: jpu...@debian.org
> > X-Debbugs-Cc: Debian OCaml Maintainers
> > 
> > 
> > A new upstream version of elpi is out ; it requires rebuilding all
> > depending packages:
> > 
> >  nmu coq-elpi_1.16.0-1+b2 . ANY . -m 'Rebuild because of upload of
> > elpi=1.16.8-1'
> >  dw coq-elpi_1.16.0-1+b2 . ANY . -m 'elpi >= 1.16.8-1'
> >  nmu coq-hierarchy-builder_1.4.0-2+b4 . ANY . -m 'Rebuild because of
> > upload of coq-elpi=1.16.0-1+b2'
> >  dw coq-hierarchy-builder_1.4.0-2+b4 . ANY . -m 'coq-elpi >= 1.16.0-
> > 1+b2'
> >  nmu mathcomp-algebra-tactics_1.0.0-8+b4 . ANY . -m 'Rebuild because of
> > upload of coq-elpi=1.16.0-1+b2'
> >  dw mathcomp-algebra-tactics_1.0.0-8+b4 . ANY . -m 'coq-elpi >= 1.16.0-
> > 1+b2'
> >  nmu mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'Rebuild because of upload
> > of coq-hierarchy-builder=1.4.0-2+b4 coq-elpi=1.16.0-1+b2'
> >  dw mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'coq-hierarchy-builder >=
> > 1.4.0-2+b4'
> >  dw mathcomp-analysis_0.5.4-3+b4 . ANY . -m 'coq-elpi >= 1.16.0-1+b2'
> > 
> > 
> > I'm waiting for the "go!" signal to upload elpi 1.16.8-1.
> 
> Please go ahead

It seems that this upload didn't need rebuilds after all.

Cheers
-- 
Sebastian Ramacher--- End Message ---

Processed: src:ruby-nokogiri: fails to migrate to testing for too long: FTBFS on some arch

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.13.8+dfsg-1
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to testing 
for too long: FTBFS on some arch
Marked as fixed in versions ruby-nokogiri/1.13.8+dfsg-1.
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to testing 
for too long: FTBFS on some arch
Marked Bug as done

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

Bug#964882: marked as done (ITP: templating-maven-plugin -- Copying files to an output directory)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 18:52:11 +0100
with message-id <7fa5687d-42dc-7ec4-d8dc-3d91cef39...@debian.org>
and subject line Close Bug #964882
has caused the Debian Bug report #964882,
regarding ITP: templating-maven-plugin -- Copying files to an output directory
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.)


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

* Package name : libtemplating-maven-plugin
  Version : 1.0.0
  Upstream Author : Name 
* URL : http://www.example.org/
* License : (GPL, LGPL, BSD, MIT/X, etc.)
  Programming Lang: (C, C++, C#, Perl, Python, etc.)
  Description :  Copying files to an output directory

The templating maven plugin handles copying files from a source to a
given output directory, while filtering them. This plugin is useful to
filter Java Source Code if you need for example to have things in that
code replaced with some properties values.



* Why is this package useful/relevant?
* Is it a dependency for another package?

This is a dependency of jcabi-aspects which is a dependency of jlawyer.

* Do you use it yourself?
* If there are other packages providing similar functionality,
  how does it compare?
* How do you plan to maintain it? Do you plan to maintain it
  inside a packaging team?
  (check list at https://wiki.debian.org/Teams)

I want to maintain it in the java-team
* Are you looking for co-maintainers? Do you need a sponsor?

Kind regards

...--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Package: templating-maven-plugin
Version: 1.0.0-1

Comment: It is already published
--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F--- End Message ---

Processed: src:mutter: fails to migrate to testing for too long: autopkgtest regression and FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 43.2-1
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long: 
autopkgtest regression and FTBFS on armhf
Marked as fixed in versions mutter/43.2-1.
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long: 
autopkgtest regression and FTBFS on armhf
Marked Bug as done
> block -1 by 1024438
Bug #1026279 {Done: Paul Gevers } [src:mutter] src:mutter: 
fails to migrate to testing for too long: autopkgtest regression and FTBFS on 
armhf
1026279 was not blocked by any bugs.
1026279 was not blocking any bugs.
Added blocking bug(s) of 1026279: 1024438

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

Bug#1025706: marked as done (squashfuse: link against fuse3)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 16:48:25 +
with message-id 
and subject line Bug#1025706: fixed in squashfuse 0.1.105-1
has caused the Debian Bug report #1025706,
regarding squashfuse: link against fuse3
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.)


-- 
1025706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squashfuse
Version: 0.1.103-3
Severity: normal

Dear Maintainer,

squashfuse should be built against libfuse3 rather than libfuse2.
The current/supported version of libfuse is 3 and squashfuse supports
linking and running with libfuse3.

There are some existing issues that are fixed by using libfuse3 [1] and
it is surely a better upstream support path.

[1] https://github.com/vasi/squashfuse/issues/80


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

Kernel: Linux 5.15.0-53-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_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 squashfuse depends on:
ii  libc6   2.35-0ubuntu3.1
ii  libfuse22.9.9-5ubuntu3.1
ii  libsquashfuse0  0.1.103-3

squashfuse recommends no packages.

squashfuse suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: squashfuse
Source-Version: 0.1.105-1
Done: Scarlett Moore 

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

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

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

Debian distribution maintenance software
pp.
Scarlett Moore  (supplier of updated squashfuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 08:28:46 -0700
Source: squashfuse
Architecture: source
Version: 0.1.105-1
Distribution: unstable
Urgency: medium
Maintainer: Scarlett Moore 
Changed-By: Scarlett Moore 
Closes: 1025706
Changes:
 squashfuse (0.1.105-1) unstable; urgency=medium
 .
   [ Scott Moser ]
   * New upstream release.
   * Link against libfuse3 rather than libfuse2 (Closes: #1025706).
   * debian/patches/* - drop patches.
 .
   [ Scarlett Moore ]
   * Update my email address.
   * Bump standards to 4.6.1, No changes needed.
   * Release to unstable.
Checksums-Sha1:
 532fff4a8a54b266f6f88907c57a7177a850df7c 2134 squashfuse_0.1.105-1.dsc
 34533764f783f06db46b90e30b51c54545896ea7 65644 squashfuse_0.1.105.orig.tar.gz
 6aeb4e7cf0146bbeebc07f683ae6b4941dbf8295 4692 
squashfuse_0.1.105-1.debian.tar.xz
 cda95ed61dae6a17b0afb77cb8abe7a2b17f2048 7963 
squashfuse_0.1.105-1_amd64.buildinfo
Checksums-Sha256:
 5eb2d9b709884d3782cc369b719ddc29205656e1c2151ff13344cf2e781a3b2e 2134 
squashfuse_0.1.105-1.dsc
 3f776892ab2044ecca417be348e482fee2839db75e35d165b53737cb8153ab1e 65644 
squashfuse_0.1.105.orig.tar.gz
 9ae5bd6e0c2bab1f6d6d5ca50f854a7adab68e5087269785532fb41a180b069e 4692 
squashfuse_0.1.105-1.debian.tar.xz
 9a9c3616141490618dec84950278b49c91f5816b42c5ab3ce21ca3dd1074800b 7963 
squashfuse_0.1.105-1_amd64.buildinfo
Files:
 54badf41e6bb5228a93634b201017580 2134 utils optional squashfuse_0.1.105-1.dsc
 5bd5ff30d416aba1e2de0c2761d4cea2 65644 utils optional 
squashfuse_0.1.105.orig.tar.gz
 5e89f5c3be95fd6d63b52dbce6c4a705 4692 utils optional 
squashfuse_0.1.105-1.debian.tar.xz
 2d144630ddca7d1aa79c8dfb901a49ac 7963 utils optional 
squashfuse_0.1.105-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfDWSDxziiZ6OqarQLnwDZ7m/oIkFAmOd44EACgkQLnwDZ7m/
oIkC+g/+NwUYQnq4hYGzH87kPw0PLh+g1SMN9hUcvAw4JZX4XqXREQnePnGVNIR6
14K8tlrXs3njpVvMAtHWa07uhbsebfSFtFlcKNqww6LNdONmA/WflIleVpIIv4/M
Vfexoz/e6O+BnsFbmFQFjF3EnVyE6r0zDBBcP6AuF4DqA95iTn3EbptMtqRr5QNb
cYTSZM7jXp5gnuKciivu22mHF4wNmklr4CHP68QqtFj4CeUWhBCG/pWG5gtTQc+y
sbBRpNyNkGbuTcihMm4/+PU3CssDNHBTSnlWs7S2z0wwC+UHcheIEvFoL/kONJ6v
ITP3dfBhzEfjOQuyTAiJTlkSTeCpBrAiMBh9zZYHONQrdw

Bug#1026257: marked as done (FTBFS: more network tests in node-zx)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:51:28 +
with message-id 
and subject line Bug#1026257: fixed in node-zx 7.1.1+~cs6.7.23-2
has caused the Debian Bug report #1026257,
regarding FTBFS: more network tests in node-zx
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.)


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

Source: node-zx
Version: 7.1.1+~cs6.7.23-1
Severity: serious
Tag: ftbfs patch

Dear Maintainer,

node-zx currently fails to build with the following error messages:
   FAIL  deps  "installDeps() loader works via JS API"
Cannot find package 'cpy' imported from 
/build/node-zx-7.1.1+~cs6.7.23/test/deps.test.js


   FAIL  deps  "installDeps() loader works via CLI"
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'lodash' imported from 
/build/node-zx-7.1.1+~cs6.7.23/zx-kdsc9wx1fn.mjs

Did you mean to import lodash/lodash.js?
at new NodeError (node:internal/errors:393:5)
at packageResolve (node:internal/modules/esm/resolve:860:9)
at moduleResolve (node:internal/modules/esm/resolve:909:20)
at defaultResolve (node:internal/modules/esm/resolve:1124:11)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ModuleWrap. 
(node:internal/modules/esm/module_job:76:40)

at link (node:internal/modules/esm/module_job:75:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}
at Object.handler 
(file:///build/node-zx-7.1.1+~cs6.7.23/test/deps.test.js:35:12)

exit code: 1

(See 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-zx.html 
for more details)


I was able to reproduce the same error message when building in pbuilder 
on my local Sid system. Turns out there's a couple of tests which call 
`npm install` and verify the results which breaks when the network is 
not available.


After expanding and applying the patch to disable network tests, the 
package builds successfully.



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

Kernel: Linux 6.0.0-5-amd64 (SMP w/3 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/patches/drop-network-test.patch b/debian/patches/drop-network-test.patch
index cf5cd17..905f6a8 100644
--- a/debian/patches/drop-network-test.patch
+++ b/debian/patches/drop-network-test.patch
@@ -1,7 +1,7 @@
 Description: drop network test
 Author: Yadd 
 Forwarded: not-needed
-Last-Update: 2022-11-07
+Last-Update: 2022-12-17
 
 --- a/test/cli.test.js
 +++ b/test/cli.test.js
@@ -37,3 +37,24 @@ Last-Update: 2022-11-07
  test('echo() works', async () => {
let stdout = ''
let log = console.log
+--- a/test/deps.test.js
 b/test/deps.test.js
+@@ -21,7 +21,7 @@ const test = suite('deps')
+ 
+ $.verbose = false
+ 
+-test('installDeps() loader works via JS API', async () => {
++test.skip('installDeps() loader works via JS API', async () => {
+   await installDeps({
+ cpy: '9.0.1',
+ 'lodash-es': '4.17.21',
+@@ -30,7 +30,7 @@ test('installDeps() loader works via JS
+   assert.instance((await import('lodash-es')).pick, Function)
+ })
+ 
+-test('installDeps() loader works via CLI', async () => {
++test.skip('installDeps() loader works via CLI', async () => {
+   let out =
+ await $`node build/cli.js --install <<< 'import _ from "lodash" /* @4.17.15 */; console.log(_.VERSION)'`
+   assert.match(out.stdout, '4.17.15')
+
--- End Message ---
--- Begin Message ---
Source: node-zx
Source-Version: 7.1.1+~cs6.7.23-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-zx 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..

Bug#1026252: marked as done (lintian-brush: Do not "fix" "uses-debhelper-compat-file" for non-stable debhelper compat levels)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:51:10 +
with message-id 
and subject line Bug#1026252: fixed in lintian-brush 0.145
has caused the Debian Bug report #1026252,
regarding lintian-brush: Do not "fix" "uses-debhelper-compat-file" for 
non-stable debhelper compat levels
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.)


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

Package: lintian-brush
Severity: normal
X-Debbugs-Cc: ni...@thykier.net


I noted that the janitor failed to do lintian-fixes for debhelper. 
Looking into the logs I found:



Lintian tags fixed: {'uses-debhelper-compat-file', 
'no-versioned-debhelper-prerequisite'}


plus:


  unsat-dependency: debhelper-compat:amd64 (= 15) | debhelper-compat:amd64 
(= 15)


Which means lintian-brush concluded that it made sense to replace a 
debian/compat file for an experimental compat level into a 
"debhelper-compat" build dependency.


I think lintian-brush should limit itself to fixing this tag if the 
compat level in question is defined as a stable compat level.


The lintian-brush tool can determine the highest stable compat level by 
using "dh_assistant supported-compat-levels" and then reading the 
"HIGHEST_STABLE_COMPAT_LEVEL" key from the output.


Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: lintian-brush
Source-Version: 0.145
Done: Jelmer Vernooij 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated lintian-brush package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 15:02:52 +
Source: lintian-brush
Architecture: source
Version: 0.145
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Closes: 1026052 1026252
Changes:
 lintian-brush (0.145) unstable; urgency=medium
 .
   * unused-build-dependency-on-cdbs: Cope with missing Build-Depends.
 Closes: #1026052
   * uses-debhelper-compat-file: Only migrate to debhelper-compat for
 stable compat levels. Closes: #1026252
Checksums-Sha1:
 a33e5f28363cafde80188520f30c99ec6aba8a68 2104 lintian-brush_0.145.dsc
 bb858279699037ab99a0efef7ce1bd53867acb70 948832 lintian-brush_0.145.tar.xz
 981a6d1c63606c1ea539c270009861b9e753b56a 20975 
lintian-brush_0.145_source.buildinfo
Checksums-Sha256:
 42a1f492b3d1335b69a564b66bb60c75ff7bfa5cb0e2de5cd5471cde19c5f6f4 2104 
lintian-brush_0.145.dsc
 5798becbe9fea1042cd5066453b88d2d68738fc84e47a93bf95c340f9da9dca5 948832 
lintian-brush_0.145.tar.xz
 154371b7243ccd352557b6b051ad20d6cd741c5edcd5f7e178dc9ceffe22bac8 20975 
lintian-brush_0.145_source.buildinfo
Files:
 d4bccdd543a0930caec81e8ca2e4a280 2104 devel optional lintian-brush_0.145.dsc
 98b1d66008977fa09f784e9ef976e4b9 948832 devel optional 
lintian-brush_0.145.tar.xz
 60c4110b42cec9f274041eac18cf253d 20975 devel optional 
lintian-brush_0.145_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmOd3AAACgkQMG8hYYBC
UGYe9Af8DvQYYP+/rJZ/Niwg+ghIawhQmjS92N62efsmK7GsTK88Te6XcGpAstEp
BizItWjgfjkkb60GsCKbckMNR+h2LElQbGl6UpH8wyjvwAS1dB0jWoGqulpZT+jr
jCKyli9rF3ckPeLGGJ7gsET6E9KfcnuifU+1OspMG4uC82Y+9OWzkiq5ifgh3n7n
1LvPOhIMJShUpY+lDmEupz/ve14S9wip8YW2U821dYMQLcD/K/qgRuwG1p30dTBQ
jw+fRewxUZhR5xc6c3Tqcw+vtGnSFTaxGbzNu6KR9oNSY0pouF+QbTim/FvjfMsR
P2RddEDpgbFYiksokf+fy5gLTDOxcw==
=Q+gj
-END PGP SIGNATURE End Message ---

Bug#1026052: marked as done (lintian-brush: fixer unused-build-dependency-on-cdbs fails if there is no Build-Depends)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:51:10 +
with message-id 
and subject line Bug#1026052: fixed in lintian-brush 0.145
has caused the Debian Bug report #1026052,
regarding lintian-brush: fixer unused-build-dependency-on-cdbs fails if there 
is no Build-Depends
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.)


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

Package: lintian-brush
Version: 0.144

Dear maintainer:

Running lintian-brush on a package not having any Build-Depends at all 
results in a KeyError:


Fixer 'unused-build-dependency-on-cdbs' failed to run.
Script 
/usr/share/lintian-brush/fixers/unused-build-dependency-on-cdbs.py 
failed with exit code: 1

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lintian_brush/__init__.py", line 
419, in run

exec(code, global_vars)
  File 
"/usr/share/lintian-brush/fixers/unused-build-dependency-on-cdbs.py", 
line 23, in 

if new_depends != updater.source['Build-Depends']:
  File 
"/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line 
1348, in __getitem__

v = self._paragraph.get_kvpair_element((item, 0))
  File 
"/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line 
2215, in get_kvpair_element

return self._kvpair_elements[item]
KeyError: 'Build-Depends'


(BTW: The package is "hello-traditional", an example aimed to show the 
sort of things one would have to do if debhelper did not exist, so 
switching to debhelper is not an option).


Thanks.
--- End Message ---
--- Begin Message ---
Source: lintian-brush
Source-Version: 0.145
Done: Jelmer Vernooij 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated lintian-brush package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 15:02:52 +
Source: lintian-brush
Architecture: source
Version: 0.145
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Closes: 1026052 1026252
Changes:
 lintian-brush (0.145) unstable; urgency=medium
 .
   * unused-build-dependency-on-cdbs: Cope with missing Build-Depends.
 Closes: #1026052
   * uses-debhelper-compat-file: Only migrate to debhelper-compat for
 stable compat levels. Closes: #1026252
Checksums-Sha1:
 a33e5f28363cafde80188520f30c99ec6aba8a68 2104 lintian-brush_0.145.dsc
 bb858279699037ab99a0efef7ce1bd53867acb70 948832 lintian-brush_0.145.tar.xz
 981a6d1c63606c1ea539c270009861b9e753b56a 20975 
lintian-brush_0.145_source.buildinfo
Checksums-Sha256:
 42a1f492b3d1335b69a564b66bb60c75ff7bfa5cb0e2de5cd5471cde19c5f6f4 2104 
lintian-brush_0.145.dsc
 5798becbe9fea1042cd5066453b88d2d68738fc84e47a93bf95c340f9da9dca5 948832 
lintian-brush_0.145.tar.xz
 154371b7243ccd352557b6b051ad20d6cd741c5edcd5f7e178dc9ceffe22bac8 20975 
lintian-brush_0.145_source.buildinfo
Files:
 d4bccdd543a0930caec81e8ca2e4a280 2104 devel optional lintian-brush_0.145.dsc
 98b1d66008977fa09f784e9ef976e4b9 948832 devel optional 
lintian-brush_0.145.tar.xz
 60c4110b42cec9f274041eac18cf253d 20975 devel optional 
lintian-brush_0.145_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmOd3AAACgkQMG8hYYBC
UGYe9Af8DvQYYP+/rJZ/Niwg+ghIawhQmjS92N62efsmK7GsTK88Te6XcGpAstEp
BizItWjgfjkkb60GsCKbckMNR+h2LElQbGl6UpH8wyjvwAS1dB0jWoGqulpZT+jr
jCKyli9rF3ckPeLGGJ7gsET6E9KfcnuifU+1OspMG4uC82Y+9OWzkiq5ifgh3n7n
1LvPOhIMJShUpY+lDmEupz/ve14S9wip8YW2U821dYMQLcD/K/qgRuwG1p30dTBQ
jw+fRewxUZhR5xc6c3Tqcw+vtGnSFTaxGbzNu6KR9oNSY0pouF+QbTim/FvjfMsR
P2RddEDpgbFYiksokf+fy5gLTDOxcw==
=Q+gj
-END PGP SIGNATURE End Message ---

Bug#999713: marked as done (ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_d

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:26:39 +
with message-id 
and subject line Bug#1026202: Removed package(s) from unstable
has caused the Debian Bug report #999713,
regarding ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test 
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in 
`rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.2) 
among 77 total gem(s) (Gem::MissingSpecError)
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.)


-- 
999713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-cas3
Version: 1.1.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-cas3 was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.2) among 77 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all/specifications/omniauth-cas3-1.1.4.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.2) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> addressable (2.8.0)
> awesome_print (1.8.0)
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> crack (0.4.4)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashdiff (1.0.1)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> net-telnet (0.1.1)
> nokogiri (1.11.7)
> observer (default: 0.1.0)
> omniauth (2.0.4)
>

Bug#1026202: marked as done (RM: ruby-omniauth-cas3 -- ROM; upstream inactive)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:26:35 +
with message-id 
and subject line Bug#1026202: Removed package(s) from unstable
has caused the Debian Bug report #1026202,
regarding RM: ruby-omniauth-cas3 -- ROM; upstream inactive
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.)


-- 
1026202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mdbi...@disroot.org

Hello,

The upstream for ruby-omniauth-cas3 has archived the project[1] and is no 
longer maintained.Moreover the only reverse-dependency gitlab uses their own 
fork[2] of the gem. So I think we can remove this package from the archive

[1] - https://github.com/tduehr/omniauth-cas3
[2] - 
https://gitlab.com/gitlab-org/gitlab/-/tree/master/vendor/gems/omniauth-cas3

Thanks,
Mohd Bilal
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ruby-omniauth-cas3 |1.1.4-2 | source, all

--- Reason ---
ROM; upstream inactive
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026202

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#999712: marked as done (ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in ac

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:25:38 +
with message-id 
and subject line Bug#1026203: Removed package(s) from unstable
has caused the Debian Bug report #999712,
regarding ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: 
Test "ruby2.7" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in 
activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total 
gem(s) (Gem::MissingSpecError)
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.)


-- 
999712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-azure-oauth2
Version: 0.0.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-azure-oauth2 was found to fail to build in that 
situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all/specifications/omniauth-azure-oauth2-0.0.10.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> faraday (1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> jwt (2.2.2)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> multi_json (1.14.1)
> multi_xml (0.6.0)
> multipart-post (2.0.0)
> mustermann (1.1.1)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (defaul

Bug#1026203: marked as done (RM: ruby-omniauth-azure-oauth2 -- ROM; upstream inactive)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:25:35 +
with message-id 
and subject line Bug#1026203: Removed package(s) from unstable
has caused the Debian Bug report #1026203,
regarding RM: ruby-omniauth-azure-oauth2 -- ROM; upstream inactive
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.)


-- 
1026203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mdbi...@disroot.org

Hello,

The upstream for ruby-omniauth-azure-oauth2 is no longer maintained[1] and the 
only reverse-dep gitlab uses its own fork of the gem. So I think we can remove 
this gem from the archive.

[1] - 
https://github.com/marknadig/omniauth-azure-oauth2/commit/58ccf0f26e74325c70f2257615023e2b5a7ace20
[2] - 
https://gitlab.com/gitlab-org/gitlab/-/tree/master/vendor/gems/omniauth-azure-oauth2

Thanks,
Mohd Bilal
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ruby-omniauth-azure-oauth2 |   0.0.10-1 | source, all

--- Reason ---
ROM; upstream inactive
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026203

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#999723: marked as done (ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in act

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id 
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #999723,
regarding ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR: 
Test "ruby2.7" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in 
activate_dependencies': Could not find 'omniauth' (~> 1.0) among 68 total 
gem(s) (Gem::MissingSpecError)
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.)


-- 
999723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-remote-user
Version: 0.1.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-remote-user was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot. I would expect a new upstream version to
work against the latest ruby-omniauth just fine.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 68 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all/specifications/omniauth-remote-user-0.1.3.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> net-telnet (0.1.1)
> observe

Bug#959557: marked as done (ruby-omniauth-remote-user: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `strip' for nil:NilClass)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id 
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #959557,
regarding ruby-omniauth-remote-user: FTBFS: ERROR: Test "ruby2.7" failed: 
NoMethodError: undefined method `strip' for nil:NilClass
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.)


-- 
959557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-remote-user
Version: 0.1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  NoMethodError:
>undefined method `strip' for nil:NilClass
>  # ./spec/omniauth/strategies/remote_user_spec.rb:68:in `block (3 levels) 
> in '
> 
> Finished in 0.11039 seconds (files took 0.17888 seconds to load)
> 10 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/omniauth/strategies/remote_user_spec.rb:30 # Test Strategy 
> Remote_User Without HTTP_REMOTE_USER and logged in Logout curreent user
> rspec ./spec/omniauth/strategies/remote_user_spec.rb:43 # Test Strategy 
> Remote_User With HTTP_REMOTE_USER and not logged in logs HTTP_REMOTE_USER in
> rspec ./spec/omniauth/strategies/remote_user_spec.rb:71 # Test Strategy 
> Remote_User With HTTP_REMOTE_USER, logged in and current user not equals 
> HTTP_REMOTE_USER Logout current user and login HTTP_REMOTE_USER
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/ruby-omniauth-remote-user_0.1.3-1_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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.1.3-1+rm

Dear submitter,

as the package ruby-omniauth-remote-user 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/1026135

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026135: marked as done (RM: ruby-omniauth-remote-user -- ROM; upstream inactive)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:23:32 +
with message-id 
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #1026135,
regarding RM: ruby-omniauth-remote-user -- ROM; upstream inactive
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.)


-- 
1026135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mdbi...@disroot.org

Hello,

The upstream[1] for ruby-omniauth-remote-user is not active anymore and the 
last release was 7 years ago. 

[1] - https://softwarepublico.gov.br/gitlab/softwarepublico/omniauth-remote-user

Thanks,
Mohammed Bilal
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ruby-omniauth-remote-user |0.1.3-1 | source, all

--- Reason ---
ROM; upstream inactive
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026135

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#982774: marked as done (haskell-uri: Wrong homepage + new version)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id 
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #982774,
regarding haskell-uri: Wrong homepage + new version
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.)


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

Source: haskell-uri
Version: 0.1.6.4-4
Severity: normal

I have see that the project homepage do not respond anymore:
http://gitorious.org/uri

I think that the homepage is now:
https://gitlab.com/Voker57/uri
https://hackage.haskell.org/package/uri

I think here there is a new version: 0.1.6.5

Ciao
Davide

Note: this is a simplified bug report that I use to report homepage 
problems found at https://repology.org/repository/debian_testing/problems
--- End Message ---
--- Begin Message ---
Version: 0.1.6.5-1+rm

Dear submitter,

as the package haskell-uri 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/1026157

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026157: marked as done (RM: haskell-uri -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:22:02 +
with message-id 
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1026157,
regarding RM: haskell-uri -- ROM; obsolete
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.)


-- 
1026157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-uri
Version: 0.1.6.4-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last commit more than 6 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-uri |  0.1.6.4-4 | source
haskell-uri |  0.1.6.5-1 | source
libghc-uri-dev | 0.1.6.4-4+b2 | mipsel
libghc-uri-dev | 0.1.6.4-4+b3 | mips64el
libghc-uri-dev | 0.1.6.4-4+b4 | amd64, arm64, armel, armhf, i386, ppc64el
libghc-uri-dev | 0.1.6.4-4+b5 | s390x
libghc-uri-doc |  0.1.6.4-4 | all
libghc-uri-prof | 0.1.6.4-4+b2 | mipsel
libghc-uri-prof | 0.1.6.4-4+b3 | mips64el
libghc-uri-prof | 0.1.6.4-4+b4 | amd64, arm64, armel, armhf, i386, ppc64el
libghc-uri-prof | 0.1.6.4-4+b5 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026157

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026156: marked as done (RM: haskell-thyme -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:45 +
with message-id 
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1026156,
regarding RM: haskell-thyme -- ROM; obsolete
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.)


-- 
1026156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-thyme
Version: 0.3.5.5-5
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-thyme |  0.3.5.5-5 | source
libghc-thyme-dev | 0.3.5.5-5+b2 | armel, armhf, i386, mips64el, mipsel
libghc-thyme-dev | 0.3.5.5-5+b3 | amd64, arm64, ppc64el, s390x
libghc-thyme-doc |  0.3.5.5-5 | all
libghc-thyme-prof | 0.3.5.5-5+b2 | armel, armhf, i386, mips64el, mipsel
libghc-thyme-prof | 0.3.5.5-5+b3 | amd64, arm64, ppc64el, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026156

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1018030: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id 
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1018030,
regarding Removal notice: obsolete
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.)


-- 
1018030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-uri
Version: 0.1.6.4-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last commit more than 6 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.1.6.5-1+rm

Dear submitter,

as the package haskell-uri 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/1026157

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026154: marked as done (RM: haskell-text-format -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:10 +
with message-id 
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1026154,
regarding RM: haskell-text-format -- ROM; obsolete
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.)


-- 
1026154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-text-format
Version: 0.3.2-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-text-format |0.3.2-4 | source
libghc-text-format-dev | 0.3.2-4+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el
libghc-text-format-dev | 0.3.2-4+b2 | s390x
libghc-text-format-doc |0.3.2-4 | all
libghc-text-format-prof | 0.3.2-4+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el
libghc-text-format-prof | 0.3.2-4+b2 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026154

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022920: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id 
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1022920,
regarding Removal notice: obsolete
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.)


-- 
1022920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-thyme
Version: 0.3.5.5-5
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.3.5.5-5+rm

Dear submitter,

as the package haskell-thyme 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/1026156

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1021574: marked as done (haskell-thyme FTBFS: Couldn't match type)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id 
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1021574,
regarding haskell-thyme FTBFS: Couldn't match type
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.)


-- 
1021574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-thyme
Version: 0.3.5.5-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=haskell-thyme&arch=amd64&ver=0.3.5.5-5%2Bb4&stamp=1658619154&raw=0

...
src/Data/Thyme/Time/Core.hs:287:23: error:
• Couldn't match type: forall (p :: * -> * -> *) (f :: * -> *).
   (Data.Profunctor.Unsafe.Profunctor p, Functor f) =>
   Control.Lens.Overloaded
 p f UTCTime UTCTime AbsoluteTime AbsoluteTime
 with: (AbsoluteTime
-> Data.Functor.Const.Const AbsoluteTime 
AbsoluteTime)
   -> UTCTime -> Data.Functor.Const.Const AbsoluteTime 
UTCTime
  Expected: LeapSecondTable
-> Control.Lens.Getting AbsoluteTime UTCTime AbsoluteTime
Actual: LeapSecondTable -> Iso' UTCTime AbsoluteTime
• In the second argument of ‘(.)’, namely ‘absoluteTime’
  In the expression: view . absoluteTime
  In an equation for ‘utcToTAITime’:
  utcToTAITime = view . absoluteTime
|
287 | utcToTAITime = view . absoluteTime
|   

src/Data/Thyme/Time/Core.hs:291:25: error:
• Couldn't match type: forall (p :: * -> * -> *) (f :: * -> *).
   (Data.Profunctor.Unsafe.Profunctor p, Functor f) =>
   Control.Lens.Overloaded
 p f UTCTime UTCTime AbsoluteTime AbsoluteTime
 with: Control.Lens.Reviewed
 a2 (Data.Functor.Identity.Identity AbsoluteTime)
   -> Control.Lens.Reviewed
s2 (Data.Functor.Identity.Identity UTCTime)
  Expected: LeapSecondTable
-> Control.Lens.AReview s2 UTCTime a2 AbsoluteTime
Actual: LeapSecondTable -> Iso' UTCTime AbsoluteTime
• In the second argument of ‘(.)’, namely ‘absoluteTime’
  In the expression: review . absoluteTime
  In an equation for ‘taiToUTCTime’:
  taiToUTCTime = review . absoluteTime
|
291 | taiToUTCTime = review . absoluteTime
| 

src/Data/Thyme/Time/Core.hs:322:25: error:
• Couldn't match type: forall (p :: * -> * -> *) (f :: * -> *).
   (Data.Profunctor.Unsafe.Profunctor p, Functor f) =>
   Control.Lens.Overloaded p f UTCTime UTCTime 
LocalTime LocalTime
 with: (LocalTime -> Data.Functor.Const.Const LocalTime 
LocalTime)
   -> UTCTime -> Data.Functor.Const.Const LocalTime 
UTCTime
  Expected: TimeZone
-> Control.Lens.Getting LocalTime UTCTime LocalTime
Actual: TimeZone -> Iso' UTCTime LocalTime
• In the second argument of ‘(.)’, namely ‘utcLocalTime’
  In the expression: view . utcLocalTime
  In an equation for ‘utcToLocalTime’:
  utcToLocalTime = view . utcLocalTime
|
322 | utcToLocalTime = view . utcLocalTime
| 

src/Data/Thyme/Time/Core.hs:326:27: error:
• Couldn't match type: forall (p :: * -> * -> *) (f :: * -> *).
   (Data.Profunctor.Unsafe.Profunctor p, Functor f) =>
   Control.Lens.Overloaded p f UTCTime UTCTime 
LocalTime LocalTime
 with: Control.Lens.Reviewed
 a1 (Data.Functor.Identity.Identity LocalTime)
   -> Control.Lens.Reviewed
s1 (Data.Functor.Identity.Identity UTCTime)
  Expected: TimeZone -> Control.Lens.AReview s1 UTCTime a1 LocalTime
Actual: TimeZone -> Iso' UTCTime LocalTime
• In the second argument of ‘(.)’, namely ‘utcLocalTime’
  In the expression: review . utcLocalTime
  In an equation for ‘localTimeToUTC’:
  localTimeToUTC = review . utcLocalTime
|
326 | localTimeToUTC = review . utcLocalTime
|   

src/Data/Thyme/Time/Core.hs:330:25: error:
• Couldn't match type: forall (p :: * -> * -> *) (f :: * -> *).
   (Data.Profunc

Bug#1022918: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id 
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1022918,
regarding Removal notice: obsolete
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.)


-- 
1022918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-text-format
Version: 0.3.2-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.3.2-4+rm

Dear submitter,

as the package haskell-text-format 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/1026154

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1017253: marked as done (haskell-uri: FTBFS: hlibrary.setup: Encountered missing or private dependencies: parsec >=3.0 && <=3.1.11)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id 
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1017253,
regarding haskell-uri: FTBFS: hlibrary.setup: Encountered missing or private 
dependencies: parsec >=3.0 && <=3.1.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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-uri-doc.substvars
> dh_installdirs -plibghc-uri-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/GarRuejGGZ -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-uri-dev
> libghc-uri-prof
> libghc-uri-doc
> Running dh_listpackages
> libghc-uri-dev
> libghc-uri-prof
> libghc-uri-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/uri-0.1.6.5/ --datasubdir=uri 
> --htmldir=/usr/share/doc/libghc-uri-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring uri-0.1.6.5...
> Warning: uri.cabal:21:29: version operators used. To use version operators the
> package needs to specify at least 'cabal-version: >= 1.8'.
> Warning: uri.cabal:21:51: version operators used. To use version operators the
> package needs to specify at least 'cabal-version: >= 1.8'.
> 
> hlibrary.setup: Encountered missing or private dependencies:
> parsec >=3.0 && <=3.1.11
> 
>  at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 631
>   Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:155: configure-ghc-stamp] 
> Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/haskell-uri_0.1.6.5-1_unstable.log

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

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

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

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

Dear submitter,

as the package haskell-uri has j

Bug#1014001: marked as done (haskell-text-format FTBFS: hlibrary.setup: Encountered missing or private dependencies: base >=4.3 && <4.15)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id 
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1014001,
regarding haskell-text-format FTBFS: hlibrary.setup: Encountered missing or 
private dependencies: base >=4.3 && <4.15
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.)


-- 
1014001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-text-format
Version: 0.3.2-4
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-text-format&suite=sid

...
hlibrary.setup: Encountered missing or private dependencies:
base >=4.3 && <4.15

 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
"--libexecdir=/usr/lib", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
"--libexecdir=/usr/lib", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 620
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.3.2-4+rm

Dear submitter,

as the package haskell-text-format 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/1026154

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#837766: marked as done (wrapped list in long description)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:10 +
with message-id 
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #837766,
regarding wrapped list in long description
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.)


-- 
837766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-schemas
Version: 0.1.3.1-1
Severity: minor
Tags: patch

The list in the long description comes out garbled due to wrapping. The attached
patch /should/ fix this, but is untested.
diff -ru haskell-relational-schemas-0.1.3.1/debian/control haskell-relational-schemas-0.1.3.1+/debian/control
--- haskell-relational-schemas-0.1.3.1/debian/control	2016-09-08 20:18:07.0 +0200
+++ haskell-relational-schemas-0.1.3.1+/debian/control	2016-09-14 13:26:42.426715063 +0200
@@ -22,12 +22,12 @@
 X-Description: RDBMSs' schema templates for relational-query
  This package contains some RDBMSs' schema structure definitions.
  Supported RDBMS schemas are below:
- + IBM DB2
- + PostgreSQL
- + Microsoft SQLServer
- + SQLite3
- + Oracle
- + MySQL
+  + IBM DB2
+  + PostgreSQL
+  + Microsoft SQLServer
+  + SQLite3
+  + Oracle
+  + MySQL
 
 Package: libghc-relational-schemas-dev
 Architecture: any
--- End Message ---
--- Begin Message ---
Version: 0.1.8.0-1+rm

Dear submitter,

as the package haskell-relational-schemas 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/1026152

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026153: marked as done (RM: haskell-test-framework-th-prime -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:45 +
with message-id 
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1026153,
regarding RM: haskell-test-framework-th-prime -- ROM; obsolete
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.)


-- 
1026153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-test-framework-th-prime
Version: 0.0.10-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-test-framework-th-prime |   0.0.10-4 | source
libghc-test-framework-th-prime-dev | 0.0.10-4+b1 | mips64el, mipsel
libghc-test-framework-th-prime-dev | 0.0.10-4+b2 | amd64, arm64, armel, i386, 
ppc64el
libghc-test-framework-th-prime-dev | 0.0.10-4+b3 | armhf, s390x
libghc-test-framework-th-prime-doc |   0.0.10-4 | all
libghc-test-framework-th-prime-prof | 0.0.10-4+b1 | mips64el, mipsel
libghc-test-framework-th-prime-prof | 0.0.10-4+b2 | amd64, arm64, armel, i386, 
ppc64el
libghc-test-framework-th-prime-prof | 0.0.10-4+b3 | armhf, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026153

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026152: marked as done (RM: haskell-relational-schemas -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:06 +
with message-id 
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #1026152,
regarding RM: haskell-relational-schemas -- ROM; obsolete
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.)


-- 
1026152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-schemas
Version: 0.1.8.0-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-relational-schemas |  0.1.8.0-1 | source
libghc-relational-schemas-dev | 0.1.8.0-1+b2 | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el
libghc-relational-schemas-dev | 0.1.8.0-1+b3 | s390x
libghc-relational-schemas-doc |  0.1.8.0-1 | all
libghc-relational-schemas-prof | 0.1.8.0-1+b2 | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el
libghc-relational-schemas-prof | 0.1.8.0-1+b3 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026152

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022913: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id 
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1022913,
regarding Removal notice: obsolete
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.)


-- 
1022913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-test-framework-th-prime
Version: 0.0.10-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.0.10-4+rm

Dear submitter,

as the package haskell-test-framework-th-prime 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/1026153

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022196: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:10 +
with message-id 
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #1022196,
regarding Removal notice: obsolete
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.)


-- 
1022196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-schemas
Version: 0.1.8.0-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.1.8.0-1+rm

Dear submitter,

as the package haskell-relational-schemas 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/1026152

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1015288: marked as done (haskell-test-framework-th-prime FTBFS: Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id 
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1015288,
regarding haskell-test-framework-th-prime FTBFS: Couldn't match expected type 
‘Maybe Exp’ with actual type ‘Exp’
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.)


-- 
1015288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-test-framework-th-prime
Version: 0.0.10-4
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-test-framework-th-prime&suite=sid

...
Test/Framework/TH/Prime/Parser.hs:41:20: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: ListE (map toCase cases)
  In the first argument of ‘TupE’, namely
‘[ListE (map toCase cases), ListE (map toProp props)]’
  In the second argument of ‘($)’, namely
‘TupE [ListE (map toCase cases), ListE (map toProp props)]’
   |
41 | return $ TupE [ListE (map toCase cases), ListE (map toProp props)]
   |

Test/Framework/TH/Prime/Parser.hs:41:46: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: ListE (map toProp props)
  In the first argument of ‘TupE’, namely
‘[ListE (map toCase cases), ListE (map toProp props)]’
  In the second argument of ‘($)’, namely
‘TupE [ListE (map toCase cases), ListE (map toProp props)]’
   |
41 | return $ TupE [ListE (map toCase cases), ListE (map toProp props)]
   |  
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.0.10-4+rm

Dear submitter,

as the package haskell-test-framework-th-prime 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/1026153

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026151: marked as done (RM: haskell-relational-query-hdbc -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:16:05 +
with message-id 
and subject line Bug#1026151: Removed package(s) from unstable
has caused the Debian Bug report #1026151,
regarding RM: haskell-relational-query-hdbc -- ROM; obsolete
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.)


-- 
1026151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-query-hdbc
Version: 0.7.2.0-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-relational-query-hdbc |  0.7.2.0-2 | source
libghc-relational-query-hdbc-dev | 0.7.2.0-2+b2 | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el
libghc-relational-query-hdbc-dev | 0.7.2.0-2+b3 | s390x
libghc-relational-query-hdbc-doc |  0.7.2.0-2 | all
libghc-relational-query-hdbc-prof | 0.7.2.0-2+b2 | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el
libghc-relational-query-hdbc-prof | 0.7.2.0-2+b3 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026151

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026149: marked as done (RM: haskell-relational-record -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:15:10 +
with message-id 
and subject line Bug#1026149: Removed package(s) from unstable
has caused the Debian Bug report #1026149,
regarding RM: haskell-relational-record -- ROM; obsolete
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.)


-- 
1026149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-record
Version: 0.2.2.0-5
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-relational-record |  0.2.2.0-5 | source
libghc-relational-record-dev |  0.2.2.0-5 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libghc-relational-record-doc |  0.2.2.0-5 | all
libghc-relational-record-prof |  0.2.2.0-5 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026149

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022191: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:15:42 +
with message-id 
and subject line Bug#1026150: Removed package(s) from unstable
has caused the Debian Bug report #1022191,
regarding Removal notice: obsolete
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.)


-- 
1022191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-persistable-types-hdbc-pg
Version: 0.0.3.5-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.0.3.5-2+rm

Dear submitter,

as the package haskell-persistable-types-hdbc-pg 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/1026150

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026150: marked as done (RM: haskell-persistable-types-hdbc-pg -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:15:38 +
with message-id 
and subject line Bug#1026150: Removed package(s) from unstable
has caused the Debian Bug report #1026150,
regarding RM: haskell-persistable-types-hdbc-pg -- ROM; obsolete
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.)


-- 
1026150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-persistable-types-hdbc-pg
Version: 0.0.3.5-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-persistable-types-hdbc-pg |  0.0.3.5-2 | source
libghc-persistable-types-hdbc-pg-dev | 0.0.3.5-2+b2 | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el
libghc-persistable-types-hdbc-pg-dev | 0.0.3.5-2+b3 | s390x
libghc-persistable-types-hdbc-pg-doc |  0.0.3.5-2 | all
libghc-persistable-types-hdbc-pg-prof | 0.0.3.5-2+b2 | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el
libghc-persistable-types-hdbc-pg-prof | 0.0.3.5-2+b3 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026150

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022195: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:15:14 +
with message-id 
and subject line Bug#1026149: Removed package(s) from unstable
has caused the Debian Bug report #1022195,
regarding Removal notice: obsolete
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.)


-- 
1022195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-record
Version: 0.2.2.0-5
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.2.0-5+rm

Dear submitter,

as the package haskell-relational-record 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/1026149

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022194: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:16:09 +
with message-id 
and subject line Bug#1026151: Removed package(s) from unstable
has caused the Debian Bug report #1022194,
regarding Removal notice: obsolete
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.)


-- 
1022194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-query-hdbc
Version: 0.7.2.0-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.7.2.0-2+rm

Dear submitter,

as the package haskell-relational-query-hdbc 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/1026151

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026148: marked as done (RM: haskell-pipes-zlib -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:14:11 +
with message-id 
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #1026148,
regarding RM: haskell-pipes-zlib -- ROM; obsolete
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.)


-- 
1026148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-pipes-zlib
Version: 0.4.4.2-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS (see #1015280)
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-pipes-zlib |  0.4.4.2-3 | source
libghc-pipes-zlib-dev | 0.4.4.2-3+b2 | mips64el
libghc-pipes-zlib-dev | 0.4.4.2-3+b3 | mipsel
libghc-pipes-zlib-dev | 0.4.4.2-3+b4 | amd64, arm64, armel, armhf, i386, ppc64el
libghc-pipes-zlib-dev | 0.4.4.2-3+b5 | s390x
libghc-pipes-zlib-doc |  0.4.4.2-3 | all
libghc-pipes-zlib-prof | 0.4.4.2-3+b2 | mips64el
libghc-pipes-zlib-prof | 0.4.4.2-3+b3 | mipsel
libghc-pipes-zlib-prof | 0.4.4.2-3+b4 | amd64, arm64, armel, armhf, i386, 
ppc64el
libghc-pipes-zlib-prof | 0.4.4.2-3+b5 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026148

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026147: marked as done (RM: haskell-monad-unlift -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:12:54 +
with message-id 
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1026147,
regarding RM: haskell-monad-unlift -- ROM; obsolete
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.)


-- 
1026147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-monad-unlift
Version: 0.2.0-6
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of unliftio-core, unliftio, rio

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-monad-unlift |0.2.0-6 | source
libghc-monad-unlift-dev | 0.2.0-6+b1 | mips64el, mipsel
libghc-monad-unlift-dev | 0.2.0-6+b2 | amd64, arm64, armel, armhf, i386, ppc64el
libghc-monad-unlift-dev | 0.2.0-6+b3 | s390x
libghc-monad-unlift-doc |0.2.0-6 | all
libghc-monad-unlift-prof | 0.2.0-6+b1 | mips64el, mipsel
libghc-monad-unlift-prof | 0.2.0-6+b2 | amd64, arm64, armel, armhf, i386, 
ppc64el
libghc-monad-unlift-prof | 0.2.0-6+b3 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026147

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022906: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id 
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1022906,
regarding Removal notice: obsolete
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.)


-- 
1022906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-monad-unlift
Version: 0.2.0-6
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of unliftio-core, unliftio, rio

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.0-6+rm

Dear submitter,

as the package haskell-monad-unlift 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/1026147

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022223: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id 
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #103,
regarding Removal notice: obsolete
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.)


-- 
103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-pipes-zlib
Version: 0.4.4.2-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS (see #1015280)
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.4.4.2-3+rm

Dear submitter,

as the package haskell-pipes-zlib 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/1026148

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1015280: marked as done (haskell-pipes-zlib FTBFS: error: Couldn't match type)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id 
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #1015280,
regarding haskell-pipes-zlib FTBFS: error: Couldn't match type
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.)


-- 
1015280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-pipes-zlib
Version: 0.4.4.2-3
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-pipes-zlib&suite=sid

...
src/Pipes/Zlib.hs:81:13: error:
• Couldn't match type: forall x'1 x1.
   Proxy x'1 x1 () B.ByteString m0 ()
 with: Proxy x' x () B.ByteString m1 a0
  Expected: Popper -> Proxy x' x () B.ByteString m1 a0
Actual: Popper -> Producer' B.ByteString m0 ()
• In the first argument of ‘(=<<)’, namely ‘fromPopper’
  In a stmt of a 'do' block:
fromPopper =<< liftIO (feedInflate inf bs)
  In the expression:
do fromPopper =<< liftIO (feedInflate inf bs)
   flush inf
   leftover <- liftIO $ getUnusedInflate inf
   if B.null leftover then
   go p' inf
   else
   return $ Left (yield leftover >> p')
• Relevant bindings include
p' :: Producer B.ByteString m1 b (bound at src/Pipes/Zlib.hs:80:21)
res :: Either b (B.ByteString, Producer B.ByteString m1 b)
  (bound at src/Pipes/Zlib.hs:77:7)
p :: Producer B.ByteString m1 b (bound at src/Pipes/Zlib.hs:76:8)
go :: Producer B.ByteString m1 b
  -> Inflate
  -> Proxy
   x'
   x
   ()
   B.ByteString
   m1
   (Either (Proxy X () () B.ByteString m1 b) b)
  (bound at src/Pipes/Zlib.hs:76:5)
   |
81 | fromPopper =<< liftIO (Z.feedInflate inf bs)
   | ^^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.4.4.2-3+rm

Dear submitter,

as the package haskell-pipes-zlib 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/1026148

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1013996: marked as done (haskell-monad-unlift FTBFS: error: Couldn't match type)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id 
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1013996,
regarding haskell-monad-unlift FTBFS: error: Couldn't match type
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.)


-- 
1013996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-monad-unlift
Version: 0.2.0-6
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=haskell-monad-unlift&ver=0.2.0-6%2Bb3

...
Control/Monad/Trans/Unlift.hs:78:16: error:
• Couldn't match type: forall a1 (n :: * -> *).
   Monad n =>
   t n a1 -> n a1
 with: t m a -> m a
  Expected: Unlift t -> t m a -> m a
Actual: Unlift t
-> forall a (n :: * -> *). Monad n => t n a -> n a
• In the first argument of ‘liftM’, namely ‘unlift’
  In the expression: liftM unlift askUnlift
  In an equation for ‘askRun’: askRun = liftM unlift askUnlift
• Relevant bindings include
askRun :: t m (t m a -> m a)
  (bound at Control/Monad/Trans/Unlift.hs:78:1)
   |
78 | askRun = liftM unlift askUnlift
   |^^

Control/Monad/Trans/Unlift.hs:115:20: error:
• Couldn't match type: forall a1. m a1 -> b a1
 with: m a -> b a
  Expected: UnliftBase b m -> m a -> b a
Actual: UnliftBase b m -> forall a. m a -> b a
• In the first argument of ‘liftM’, namely ‘unliftBase’
  In the expression: liftM unliftBase askUnliftBase
  In an equation for ‘askRunBase’:
  askRunBase = liftM unliftBase askUnliftBase
• Relevant bindings include
askRunBase :: m (m a -> b a)
  (bound at Control/Monad/Trans/Unlift.hs:115:1)
|
115 | askRunBase = liftM unliftBase askUnliftBase
|^^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.2.0-6+rm

Dear submitter,

as the package haskell-monad-unlift 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/1026147

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026146: marked as done (RM: haskell-maths -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:52 +
with message-id 
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1026146,
regarding RM: haskell-maths -- ROM; obsolete
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.)


-- 
1026146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-maths
Version: 0.4.9-2
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 4 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-maths |0.4.9-2 | source
libghc-maths-dev | 0.4.9-2+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libghc-maths-dev | 0.4.9-2+b2 | s390x
libghc-maths-doc |0.4.9-2 | all
libghc-maths-prof | 0.4.9-2+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libghc-maths-prof | 0.4.9-2+b2 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026146

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022905: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id 
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1022905,
regarding Removal notice: obsolete
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.)


-- 
1022905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-maths
Version: 0.4.9-2
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 4 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.4.9-2+rm

Dear submitter,

as the package haskell-maths 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/1026146

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1013795: marked as done (haskell-maths FTBFS: error: Bang pattern in expression context: !j)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id 
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1013795,
regarding haskell-maths FTBFS: error: Bang pattern in expression context: !j
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.)


-- 
1013795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-maths
Version: 0.4.9-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-maths&suite=sid

...
Math/Algebra/LinearAlgebra.hs:222:60: error:
Bang pattern in expression context: !j
Did you mean to add a space after the '!'?
|
222 |in zip is $ L.transpose [map (negate . (!j)) m' | j <- 
js]

|^^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.4.9-2+rm

Dear submitter,

as the package haskell-maths 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/1026146

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#982490: marked as done (haskell-hsh: Wrong homepage)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:10:34 +
with message-id 
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #982490,
regarding haskell-hsh: Wrong homepage
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.)


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

Source: haskell-hsh
Version: 2.1.3-4
Severity: normal

I have see that the project homepage do not respond anymore:
https://wiki.github.com/jgoerzen/hsh

I think that the homepage is now:
https://github.com/jgoerzen/hsh
https://hackage.haskell.org/package/HSH

Ciao
Davide

Note: this is a simplified bug report that I use to report homepage 
problems found at https://repology.org/repository/debian_testing/problems
--- End Message ---
--- Begin Message ---
Version: 2.1.3-4+rm

Dear submitter,

as the package haskell-hsh 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/1026144

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#982489: marked as done (haskell-hashmap: Wrong homepage)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id 
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #982489,
regarding haskell-hashmap: Wrong homepage
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.)


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

Source: haskell-hashmap
Version: 1.3.3-3
Severity: normal

I have see that the project homepage do not respond anymore:
http://git.auryn.cz/haskell/hashmap/

I think that the homepage is now:
https://hackage.haskell.org/package/hashmap
https://github.com/foxik/hashmap

note that on github it say: "Deprecated in favor of unordered-containers"

Ciao
Davide

Note: this is a simplified bug report that I use to report homepage 
problems found at https://repology.org/repository/debian_testing/problems
--- End Message ---
--- Begin Message ---
Version: 1.3.3-3+rm

Dear submitter,

as the package haskell-hashmap 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/1026145

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026145: marked as done (RM: haskell-hashmap -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:24 +
with message-id 
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1026145,
regarding RM: haskell-hashmap -- ROM; obsolete
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.)


-- 
1026145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hashmap
Version: 1.3.3-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Deprecated in favor of unordered-containers

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-hashmap |1.3.3-3 | source
libghc-hashmap-dev | 1.3.3-3+b3 | arm64, i386, mips64el, mipsel
libghc-hashmap-dev | 1.3.3-3+b4 | amd64, armel, armhf, ppc64el, s390x
libghc-hashmap-doc |1.3.3-3 | all
libghc-hashmap-prof | 1.3.3-3+b3 | arm64, i386, mips64el, mipsel
libghc-hashmap-prof | 1.3.3-3+b4 | amd64, armel, armhf, ppc64el, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026145

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026144: marked as done (RM: haskell-hsh -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:10:30 +
with message-id 
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #1026144,
regarding RM: haskell-hsh -- ROM; obsolete
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.)


-- 
1026144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hsh
Version: 2.1.3-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-hsh |2.1.3-4 | source
libghc-hsh-dev | 2.1.3-4+b3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libghc-hsh-dev | 2.1.3-4+b4 | s390x
libghc-hsh-doc |2.1.3-4 | all
libghc-hsh-prof | 2.1.3-4+b3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libghc-hsh-prof | 2.1.3-4+b4 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026144

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1017242: marked as done (haskell-descriptive: FTBFS: • Couldn't match expected type ‘Key’ with actual type ‘Text’ • In the second argument of ‘(.:)’, namely ‘k’ In the first argument of ‘const’, n

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id 
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1017242,
regarding haskell-descriptive: FTBFS: • Couldn't match expected type ‘Key’ with 
actual type ‘Text’ • In the second argument of ‘(.:)’, namely ‘k’ In the first 
argument of ‘const’, namely ‘(s .: k)’ In the first argument of ‘parseMaybe’, 
namely ‘(const (s .: k))’
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-descriptive-doc.substvars
> dh_installdirs -plibghc-descriptive-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/OeJFQdNWqO -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-descriptive-dev
> libghc-descriptive-prof
> libghc-descriptive-doc
> Running dh_listpackages
> libghc-descriptive-dev
> libghc-descriptive-prof
> libghc-descriptive-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/descriptive-0.9.5/ 
> --datasubdir=descriptive 
> --htmldir=/usr/share/doc/libghc-descriptive-doc/html/ 
> --enable-library-profiling --enable-tests
> Using Parsec parser
> Configuring descriptive-0.9.5...
> Dependency aeson >=0.7.0.5: using aeson-2.0.3.0
> Dependency base >=4.4 && <5: using base-4.15.1.0
> Dependency bifunctors: using bifunctors-5.5.12
> Dependency containers >=0.5: using containers-0.6.4.1
> Dependency mtl: using mtl-2.2.2
> Dependency scientific >=0.3.2: using scientific-0.3.7.0
> Dependency text: using text-1.2.5.0
> Dependency transformers: using transformers-0.5.6.2
> Dependency vector: using vector-0.12.3.1
> Dependency HUnit: using HUnit-1.6.2.0
> Dependency aeson: using aeson-2.0.3.0
> Dependency base: using base-4.15.1.0
> Dependency bifunctors: using bifunctors-5.5.12
> Dependency containers: using containers-0.6.4.1
> Dependency descriptive: using descriptive-0.9.5
> Dependency hspec: using hspec-2.8.5
> Dependency mtl: using mtl-2.2.2
> Dependency text: using text-1.2.5.0
> Dependency transformers: using transformers-0.5.6.2
> Source component graph:
> component lib
> component test:test dependency lib
> Configured component graph:
> component descriptive-0.9.5-5P2vCz4KhPqJCdag67L8cD
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include base-4.15.1.0
> include bifunctors-5.5.12-EkHRFXmt5NvB4N6g2Q7ooc
> include containers-0.6.4.1
> include mtl-2.2.2
> include scientific-0.3.7.0-7BCpthzRrIo63GoBWzRPfh
> include text-1.2.5.0
> include transformers-0.5.6.2
> include vector-0.12.3.1-TXkE6leK98EdYcmdk29JF
> component descriptive-0.9.5-2wpA94z6qKhAUiIfaZuloy-test
> include HUnit-1.6.2.0-6A7GkX10OfW69odZH6xHBm
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include base-4.15.1.0
> include bifunctors-5.5.12-EkHRFXmt5NvB4N6g2Q7ooc
> include containers-0.6.4.1
> include descriptive-0.9.5-5P2vCz4KhPqJCdag67L8cD
> include hspec-2.8.5-ztFhIZtg6636xJR5cbSTr
> include mtl-2.2.2
> include text-1.2.5.0
> include transformers-0.5.6.2
> Linked component graph:
> unit descriptive-0.9.5-5P2vCz4KhPqJCdag67L8cD
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include base-4.15.1.0
> include bifunctors-5

Bug#1026143: marked as done (RM: haskell-ghc-mtl -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:09:59 +
with message-id 
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1026143,
regarding RM: haskell-ghc-mtl -- ROM; obsolete
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.)


-- 
1026143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-ghc-mtl
Version: 1.2.1.0-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-ghc-mtl | 1.2.1.0-10 | source
libghc-ghc-mtl-dev | 1.2.1.0-10+b3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libghc-ghc-mtl-doc | 1.2.1.0-10 | all
libghc-ghc-mtl-prof | 1.2.1.0-10+b3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026143

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026142: marked as done (RM: haskell-djinn-ghc -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:09:29 +
with message-id 
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1026142,
regarding RM: haskell-djinn-ghc -- ROM; obsolete
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.)


-- 
1026142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-djinn-ghc
Version: 0.0.2.3-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-djinn-ghc | 0.0.2.3-10 | source
libghc-djinn-ghc-dev | 0.0.2.3-10+b3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libghc-djinn-ghc-doc | 0.0.2.3-10 | all
libghc-djinn-ghc-prof | 0.0.2.3-10+b3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026142

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1026141: marked as done (RM: haskell-descriptive -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:08:34 +
with message-id 
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1026141,
regarding RM: haskell-descriptive -- ROM; obsolete
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.)


-- 
1026141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-descriptive
Version: 0.9.5-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It is unmaintained
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-descriptive |0.9.5-3 | source
libghc-descriptive-dev | 0.9.5-3+b1 | armel, armhf, i386
libghc-descriptive-dev | 0.9.5-3+b2 | amd64, arm64, mips64el, mipsel, ppc64el, 
s390x
libghc-descriptive-doc |0.9.5-3 | all
libghc-descriptive-prof | 0.9.5-3+b1 | armel, armhf, i386
libghc-descriptive-prof | 0.9.5-3+b2 | amd64, arm64, mips64el, mipsel, ppc64el, 
s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026141

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022901: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id 
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1022901,
regarding Removal notice: obsolete
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.)


-- 
1022901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-ghc-mtl
Version: 1.2.1.0-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 1.2.1.0-10+rm

Dear submitter,

as the package haskell-ghc-mtl 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/1026143

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1021070: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id 
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1021070,
regarding Removal notice: obsolete
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.)


-- 
1021070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-descriptive
Version: 0.9.5-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It is unmaintained
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.9.5-3+rm

Dear submitter,

as the package haskell-descriptive 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/1026141

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1022053: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id 
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1022053,
regarding Removal notice: obsolete
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.)


-- 
1022053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-djinn-ghc
Version: 0.0.2.3-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.0.2.3-10+rm

Dear submitter,

as the package haskell-djinn-ghc 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/1026142

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1020252: marked as done (libghc-hashmap-doc: Depends: haddock-interface-35 but it is not installable)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id 
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020252,
regarding libghc-hashmap-doc: Depends: haddock-interface-35 but it is not 
installable
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.)


-- 
1020252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-hashmap-doc
Version: 1.3.3-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

$ apt install libghc-hashmap-doc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libghc-hashmap-doc : Depends: haddock-interface-35 but it is not installable
  Recommends: libghc-hashable-doc but it is not going to be 
installed
  Recommends: libjs-mathjax but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.3.3-3+rm

Dear submitter,

as the package haskell-hashmap 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/1026145

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1020782: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id 
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020782,
regarding Removal notice: obsolete
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.)


-- 
1020782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hashmap
Version: 1.3.3-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Deprecated in favor of unordered-containers

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 1.3.3-3+rm

Dear submitter,

as the package haskell-hashmap 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/1026145

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1018051: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:10:34 +
with message-id 
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #1018051,
regarding Removal notice: obsolete
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.)


-- 
1018051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hsh
Version: 2.1.3-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 2.1.3-4+rm

Dear submitter,

as the package haskell-hsh 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/1026144

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1014021: marked as done (haskell-ghc-mtl FTBFS: error: Could not find module)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id 
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1014021,
regarding haskell-ghc-mtl FTBFS: error: Could not find module
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.)


-- 
1014021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-ghc-mtl
Version: 1.2.1.0-10
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-ghc-mtl&suite=sid

...
Control/Monad/Ghc.hs:22:1: error:
Could not find module ‘MonadUtils’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
22 | import qualified MonadUtils as GHC
   | ^^

Control/Monad/Ghc.hs:23:1: error:
Could not find module ‘Exception’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
23 | import qualified Exception  as GHC
   | ^^

Control/Monad/Ghc.hs:25:1: error:
Could not find module ‘GhcMonad’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
25 | import qualified GhcMonad   as GHC
   | ^^

Control/Monad/Ghc.hs:31:1: error:
Could not find module ‘DynFlags’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
31 | import qualified DynFlags as GHC
   | 
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 1.2.1.0-10+rm

Dear submitter,

as the package haskell-ghc-mtl 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/1026143

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1014002: marked as done (haskell-djinn-ghc FTBFS: error: Could not find module)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id 
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1014002,
regarding haskell-djinn-ghc FTBFS: error: Could not find module
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.)


-- 
1014002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-djinn-ghc
Version: 0.0.2.3-10
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-djinn-ghc&suite=sid

...
src/Djinn/GHC.hs:13:1: error:
Could not find module ‘MonadUtils’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
13 | import MonadUtils
   | ^

src/Djinn/GHC.hs:14:1: error:
Could not find module ‘DataCon’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
14 | import qualified DataCon as G
   | ^

src/Djinn/GHC.hs:16:1: error:
Could not find module ‘Name’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
16 | import qualified Name as G
   | ^^

src/Djinn/GHC.hs:17:1: error:
Could not find module ‘TyCon’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
17 | import qualified TyCon as G
   | ^^^

src/Djinn/GHC.hs:18:1: error:
Could not find module ‘Type’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
   |
18 | import qualified Type as G
   | ^^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.0.2.3-10+rm

Dear submitter,

as the package haskell-djinn-ghc 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/1026142

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1017011: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id 
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017011,
regarding Removal notice: obsolete
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.)


-- 
1017011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-binary-tagged
Version: 0.2-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Newer versions depend on libraries not available in Debian

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2-1+rm

Dear submitter,

as the package haskell-binary-tagged 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/1026140

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1017207: marked as done (haskell-binary-tagged: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 1.5), libghc-base16-bytestring-dev (< 0.2))

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id 
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017207,
regarding haskell-binary-tagged: FTBFS: unsatisfiable build-dependencies: 
libghc-aeson-dev (< 1.5), libghc-base16-bytestring-dev (< 0.2)
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.)


-- 
1017207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-binary-tagged
Version: 0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.8), libghc-aeson-dev (<< 
> 1.5), libghc-aeson-prof, libghc-base16-bytestring-dev (>= 0.1.1.6), 
> libghc-base16-bytestring-dev (<< 0.2), libghc-base16-bytestring-prof, 
> libghc-cryptohash-sha1-dev (>= 0.11.100.1), libghc-cryptohash-sha1-dev (<< 
> 0.12), libghc-cryptohash-sha1-prof, libghc-generics-sop-dev (>= 0.3.2.0), 
> libghc-generics-sop-dev (<< 0.6), libghc-generics-sop-prof, 
> libghc-hashable-dev (>= 1.2), libghc-hashable-dev (<< 1.4), 
> libghc-hashable-prof, libghc-scientific-dev (>= 0.3), libghc-scientific-dev 
> (<< 0.4), libghc-scientific-prof, libghc-tagged-dev (>= 0.7), 
> libghc-tagged-dev (<< 0.9), libghc-tagged-prof, 
> libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-dev (>= 
> 0.2), libghc-unordered-containers-prof, libghc-vector-dev (>= 0.10), 
> libghc-vector-dev (<< 0.13), libghc-vector-prof, build-essential, fakeroot, 
> ghc-doc, libghc-aeson-doc, libghc-base16-bytestring-doc, 
> libghc-cryptohash-sha1-doc, libghc-generics-sop-doc, libghc-hashable-doc, 
> libghc-scientific-doc, libghc-tagged-doc, libghc-unordered-containers-doc, 
> libghc-vector-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.8), libghc-aeson-dev (<< 
> 1.5), libghc-aeson-prof, libghc-base16-bytestring-dev (>= 0.1.1.6), 
> libghc-base16-bytestring-dev (<< 0.2), libghc-base16-bytestring-prof, 
> libghc-cryptohash-sha1-dev (>= 0.11.100.1), libghc-cryptohash-sha1-dev (<< 
> 0.12), libghc-cryptohash-sha1-prof, libghc-generics-sop-dev (>= 0.3.2.0), 
> libghc-generics-sop-dev (<< 0.6), libghc-generics-sop-prof, 
> libghc-hashable-dev (>= 1.2), libghc-hashable-dev (<< 1.4), 
> libghc-hashable-prof, libghc-scientific-dev (>= 0.3), libghc-scientific-dev 
> (<< 0.4), libghc-scientific-prof, libghc-tagged-dev (>= 0.7), 
> libghc-tagged-dev (<< 0.9), libghc-tagged-prof, 
> libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-dev (>= 
> 0.2), libghc-unordered-containers-prof, libghc-vector-dev (>= 0.10), 
> libghc-vector-dev (<< 0.13), libghc-vector-prof, build-essential, fakeroot, 
> ghc-doc, libghc-aeson-doc, libghc-base16-bytestring-doc, 
> libghc-cryptohash-sha1-doc, libghc-generics-sop-doc, libghc-hashable-doc, 
> libghc-scientific-doc, libghc-tagged-doc, libghc-unordered-containers-doc, 
> libghc-vector-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [650 B]
> Get:5 copy:/<>/apt_archive ./ Packages [734 B]
> Fetched 2347 B in 0s (191 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-buil

Bug#1026208: marked as done (RM: recipe-scrapers -- ROM; Upstream switched to scrape-schema-recipe)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 16:05:43 +0100
with message-id <875yea5auw@43-1.org>
and subject line Re: RM: recipe-scrapers -- ROM; Upstream switched to 
scrape-schema-recipe
has caused the Debian Bug report #1026208,
regarding RM: recipe-scrapers -- ROM; Upstream switched to scrape-schema-recipe
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.)


-- 
1026208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Hi,

I did an ITP for recipe-scrapers module #1001313 (package already in
NEWS) but upstream (gourmand package) changed to the
scrape-schema-recip python module.

So I no longer need this package.

Christian
--- End Message ---
--- Begin Message ---
Hi,

I marked the package to be rejected from NEW.

Ansgar--- End Message ---

Bug#1026140: marked as done (RM: haskell-binary-tagged -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 15:07:51 +
with message-id 
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1026140,
regarding RM: haskell-binary-tagged -- ROM; obsolete
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.)


-- 
1026140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-binary-tagged
Version: 0.2-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Newer versions depend on libraries not available in Debian

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

haskell-binary-tagged |  0.2-1 | source
libghc-binary-tagged-dev |   0.2-1+b1 | mips64el, mipsel
libghc-binary-tagged-dev |   0.2-1+b2 | amd64, arm64, armel, armhf, i386, 
ppc64el
libghc-binary-tagged-dev |   0.2-1+b3 | s390x
libghc-binary-tagged-doc |  0.2-1 | all
libghc-binary-tagged-prof |   0.2-1+b1 | mips64el, mipsel
libghc-binary-tagged-prof |   0.2-1+b2 | amd64, arm64, armel, armhf, i386, 
ppc64el
libghc-binary-tagged-prof |   0.2-1+b3 | s390x

--- Reason ---
ROM; obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1026140

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.
Ansgar (the ftpmaster behind the curtain)--- End Message ---

Bug#1025588: marked as done (osmnx: FTBFS with Shapely 2.0)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:42:29 +
with message-id 
and subject line Bug#1025588: fixed in osmnx 1.2.3+ds-1
has caused the Debian Bug report #1025588,
regarding osmnx: FTBFS with Shapely 2.0
to be marked as done.

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

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


-- 
1025588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmnx
Version: 1.2.2+ds-2
Severity: important
Tags: upstream ftbfs
User: debian-...@lists.debian.org
Usertags: shapely-2.0
Control: forwarded -1 https://github.com/gboeing/osmnx/pull/891

Dear Maintainer,

Your package FTBFS with python3-shapely from experimental:

 = test session starts 
==
 platform linux -- Python 3.10.8, pytest-7.1.2, pluggy-1.0.0+repack -- 
/usr/bin/python3
 cachedir: .pytest_cache
 rootdir: /build/osmnx-1.2.2+ds
 collecting ... collected 0 items / 1 error
 
  ERRORS 

 _ ERROR collecting debian/tests/test_osmnx_offline.py 
__
 ImportError while importing test module 
'/build/osmnx-1.2.2+ds/debian/tests/test_osmnx_offline.py'.
 Hint: make sure your test modules/packages have valid Python names.
 Traceback:
 /usr/lib/python3.10/importlib/__init__.py:126: in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
 debian/tests/test_osmnx_offline.py:35: in 
 import osmnx as ox
 osmnx/__init__.py:3: in 
 from ._api import *
 osmnx/_api.py:17: in 
 from .geometries import geometries_from_address
 osmnx/geometries.py:21: in 
 from shapely.geos import TopologicalError
 E   ImportError: cannot import name 'TopologicalError' from 'shapely.geos' 
(/usr/lib/python3/dist-packages/shapely/geos.py)
 === short test summary info 

 ERROR debian/tests/test_osmnx_offline.py
  Interrupted: 1 error during collection 

 === 1 error in 7.73s 
===

The attached patch fixes the issue.

Kind Regards,

Bas
diff -Nru osmnx-1.2.2+ds/debian/changelog osmnx-1.2.2+ds/debian/changelog
--- osmnx-1.2.2+ds/debian/changelog 2022-12-03 12:02:14.0 +0100
+++ osmnx-1.2.2+ds/debian/changelog 2022-12-06 14:51:41.0 +0100
@@ -1,3 +1,10 @@
+osmnx (1.2.2+ds-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix FTBFS with Shapely 2.0.
+
+ -- Bas Couwenberg   Tue, 06 Dec 2022 14:51:41 +0100
+
 osmnx (1.2.2+ds-2) unstable; urgency=medium
 
   * Debianization:
diff -Nru osmnx-1.2.2+ds/debian/patches/series 
osmnx-1.2.2+ds/debian/patches/series
--- osmnx-1.2.2+ds/debian/patches/series2021-11-04 16:28:16.0 
+0100
+++ osmnx-1.2.2+ds/debian/patches/series2022-12-06 14:51:41.0 
+0100
@@ -1,3 +1,4 @@
 adhoc-fix-elevation-multiprocessing.patch
 debianization.patch
 debianization-tests-extra.patch
+shapely.patch
diff -Nru osmnx-1.2.2+ds/debian/patches/shapely.patch 
osmnx-1.2.2+ds/debian/patches/shapely.patch
--- osmnx-1.2.2+ds/debian/patches/shapely.patch 1970-01-01 01:00:00.0 
+0100
+++ osmnx-1.2.2+ds/debian/patches/shapely.patch 2022-12-06 14:51:41.0 
+0100
@@ -0,0 +1,15 @@
+Description: Fix ImportError with Shapely 2.0.
+Author: Bas Couwenberg 
+Forwarded: https://github.com/gboeing/osmnx/pull/891
+
+--- a/osmnx/geometries.py
 b/osmnx/geometries.py
+@@ -18,7 +18,7 @@ from shapely.geometry import LineString
+ from shapely.geometry import MultiPolygon
+ from shapely.geometry import Point
+ from shapely.geometry import Polygon
+-from shapely.geos import TopologicalError
++from shapely.errors import TopologicalError
+ from shapely.ops import linemerge
+ from shapely.ops import polygonize
+ 
--- End Message ---
--- Begin Message ---
Source: osmnx
Source-Version: 1.2.3+ds-1
Done: Jerome Benoit 

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated osmnx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please conta

Bug#1025526: marked as done (rust-nix: please upgrade to v0.26.1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:43:18 +
with message-id 
and subject line Bug#1025526: fixed in rust-nix 0.26.1-2
has caused the Debian Bug report #1025526,
regarding rust-nix: please upgrade to v0.26.1
to be marked as done.

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

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


-- 
1025526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-nix
Version: 0.25.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to newer upstram version v0.26.1.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOPDAgACgkQLHwxRsGg
ASGLjA//fq0UpOlfdmiFUyWef3HEdMrSLGTDq/89qpgoULC986AriryjV/ddodjG
aW5gVbcjM7cUfyO9xYAxmVMCAiNm5QSkHSNWzfLA+IGBhnxfQ97saZ26yE9m+zYM
NsT0mxAZVqz6V+XIdGrn3BWuPCDcsZOlrfSo7VswefPtNgaFhdI0O0Wm6a6tqZFS
e+RpqTZcqtgGM8mY8Y+HEGDZE68wP/ijJP7rshGgGMpZwI9dIoNdmLLBvBa5iZ0S
1vzRV+yOVWfRzvoCUBNQuBwZs/zfwdk2Usk8ln7KbUHJeqZFLpIRoCIPfeYCLoWK
FUZvIZ/3YbeUPpM0bKA4G65YmMqlTSlhXVkAET5wvjPuB+Tiv8IZj7JE87T7Oj+c
VpZcBaYNTrQzO4DgoSiMxibm5aCWHM+TIoJSj4pbjvTEcpRvQ25gYNbYzcNxcnhU
QmRsU6hO0HPGyRzfS3P7iUOE0EkXpznmysPoSexLMkdSMT17OFS+BXiAX464jo44
gb1iivQOjj9+i/TCEIblhVLgP0chrPVVJN8iwhzTDXKgj70Sn4SMF2UbWDLD3jBI
sQiw8pNLwCMnfrsxBFIomTzwD5lXeKJSJPYkdHLNshNcLI2QbcjpZbOwuPoc7F30
QQcLw6tb6/h7o8j3K2kKo/bHF9JHgBdVAo/+mgjxjruMsT08rtg=
=W46g
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-nix
Source-Version: 0.26.1-2
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-nix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Dec 2022 13:56:52 +
Source: rust-nix
Architecture: source
Version: 0.26.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1025526
Changes:
 rust-nix (0.26.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Package nix 0.26.1 from crates.io using debcargo 2.6.0
   * Fix tests with --no-default-features --features term,process
   * Upload to unstable (Closes: #1025526).
Checksums-Sha1:
 6795da736908dc5d0c20deb38759fd81767756c5 2806 rust-nix_0.26.1-2.dsc
 3c1e1e77f889ed3bf5fc0728620b4c93b72f2f24 14428 rust-nix_0.26.1-2.debian.tar.xz
 21786cef7760371e14fba8c4f9cfc5d3fcefec07 7760 
rust-nix_0.26.1-2_source.buildinfo
Checksums-Sha256:
 2793906a174bdc6d9ffe1ebb6ddc6ac2b13047e52a76f0678c2b807dff213235 2806 
rust-nix_0.26.1-2.dsc
 42127c5a696aad212c5bbedd1ca908cce63139d44592de29ca533ffd1f1be520 14428 
rust-nix_0.26.1-2.debian.tar.xz
 387b92e5329f73d2ec290a5af1de5479f123359addec289e95c50187ed36f7b8 7760 
rust-nix_0.26.1-2_source.buildinfo
Files:
 5639002a3d4d670d1ad3276cbd0279a1 2806 rust optional rust-nix_0.26.1-2.dsc
 378ed8e5c02e5a50d8736905edd33bc8 14428 rust optional 
rust-nix_0.26.1-2.debian.tar.xz
 d400ab1835094d7d09b5d56c16559af2 7760 rust optional 
rust-nix_0.26.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmOdyswUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvczBAAgzVuPfgrYNfhXzg5tk5TJgAXhlY2
Xa4gmW0F1ZAvQiApZhFu7bP7yPjuph/RFBfNLL0UtWycEqBTvE/r90T8S1rpGeuo
B8BI9nUfeIHgKPf+XRV4FkYzXETWallzFglmLXSXEf72giGE77gbiS030EitmiHw
tG6GrB/2QrZIREzvK9weQTMV8AQQct3ak5V7ptUkWrCf38tzMUNVrGfsyDKuHKt8
jMVguf0T60HxW8XxRNMwNyMrkrSlW8odJp64uZ0NW0oIGDH+yoyuil0gd9d5a3fR
4qFvEL24ds1oAXOMhdBOekg/gfaq8tw5tuKP8uHh6weAR2F3YHDH/6hP7apPsYGZ
qvmXLUPihCO4oP5Mp5L4ppNH3dVFvSTMIRhT+lH3MGQxCq+Q9lX6XZRE9g5ifGrx
qdoStdOMbiDc2gofjuGSR9eBX/QTjlC8QDFs9A5gPpWp3NQA2elMgsYhLCSiHwF7
RU4usQYqjBBAwBpYa6DTpgqR0zPDVJbEgOYZTxcSdZ7oiH40MMuiA3X6+hXt5iXs
CdRKUrfn8nKXgytIx4QP5ItuOnKoiGQ27+RVNcHMxJgB2K64eVIa0ECQyXjVy396
XazEer1047PcCzRWd7IjrqAXMwetLHTfWgoiJR/TCMYc7fBNJ9+ACdMUShderp/I
H7ROOzFFVoTxOQY=
=Wbhx
-END PGP SIGNATURE End Message ---

Bug#1025832: marked as done (transition: libkeduvocdocument)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:54:14 +0100
with message-id 
and subject line Re: Bug#1025832: transition: libkeduvocdocument
has caused the Debian Bug report #1025832,
regarding transition: libkeduvocdocument
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.)


-- 
1025832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: libkeduvocdocum...@packages.debian.org, Debian Qt/KDE Maintainers 

Control: affects -1 + src:libkeduvocdocument

Dear Release Team,

I’d like to request a transition slot for libkeduvocdocument.

It has 4 reverse dependencies:
- kanagram
- khangman
- kwordquiz
- parley

All 4 rebuild successfully with the new version of the library.

I’ve uploaded libktorrent 4:22.11.90-2 with the new ABI to experimental
and it builds successfully on all release architectures. [0]


Ben file:

title = "libkeduvocdocument";
is_affected = .depends ~ "libkeduvocdocument5" | .depends ~ 
"libkeduvocdocument5abi1";
is_good = .depends ~ "libkeduvocdocument5abi1";
is_bad = .depends ~ "libkeduvocdocument5";

[0] 
https://buildd.debian.org/status/package.php?p=libkeduvocdocument&suite=experimental
--- End Message ---
--- Begin Message ---
On 2022-12-10 20:37:36 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> Hi Aurélien
> 
> On 2022-12-10 08:16:31 +0100, Aurélien COUDERC wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: libkeduvocdocum...@packages.debian.org, Debian Qt/KDE 
> > Maintainers 
> > Control: affects -1 + src:libkeduvocdocument
> > 
> > Dear Release Team,
> > 
> > I’d like to request a transition slot for libkeduvocdocument.
> > 
> > It has 4 reverse dependencies:
> > - kanagram
> > - khangman
> > - kwordquiz
> > - parley
> > 
> > All 4 rebuild successfully with the new version of the library.
> > 
> > I’ve uploaded libktorrent 4:22.11.90-2 with the new ABI to experimental
> > and it builds successfully on all release architectures. [0]
> 
> Please go ahead.

The old packages got removed. Closing.

Cheers
-- 
Sebastian Ramacher--- End Message ---

Bug#1025944: marked as done (rust-castaway: please upgrasde to v0.2)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:44:40 +0100 (CET)
with message-id 
and subject line 
has caused the Debian Bug report #1025944,
regarding rust-castaway: please upgrasde to v0.2
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.)


-- 
1025944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-castaway
Version: 0.2.2-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to newer upstream branch v0.2.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOXCO4ACgkQLHwxRsGg
ASEldQ/+PkOpuWcvgc6Rp9KJtaBz5j8rWgkpmYaeG9JjPGwshLgU5FJwyuKHfSum
trbxV7bYOS/4l/vtwC+Bh2iLo2XlnwydV64EL/b7ei4SCOvytlQF0xOUBfTy/DLU
DL07xDtbCSoVXXP6IohXVW50KYEWFovTeiKuia86FaJuB7vHFdXYM2x8zUyF1jjm
q6JgqVdXuOFYGddm9vC2J54Fmk2BEudCYEDjkZ/Y9mtel973h5bDJPl1dK4HhH5U
cQ3RBwykDpzekhtzz57dwERmuATyKDCgiPrwm8GahbXybwSJiaxlvEQw096ROysO
77osifbXsleewQoUDbjYtZCzJumq+b/h5wsye8ZAVjSI8G3z6C7ubUBthk5wa4dd
qQ154yB6Y2yEZl7gKPwk6yV0KGyYlpJwISQofOKJCdZmeIewKbcY8gm4Wn17x/1H
+5mMwX3/LwIc4eXYGLxHPineyrPfeA8Pl91XKdkPop4VQxn+hu48PL1x6bnITi2N
kknqe9MlcjE3BVu8Yn4ZnNoLDnpFNEs09hauZP2ZJE/t/grH+3WPgGqClVnHJT99
zz9BHyg17GhfB6n0F3/lyy8tYwMb69DWiG0219OmhZxZjMido7ziYjw9MOTr2Zih
g9TZkk1g+VZVVx+dM5gE0Kt7BgwCqPWC6NuQfeh+sZW0YsY03OE=
=6uD3
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.2.2
It's already the newest version. Closing.
--- End Message ---

Bug#1025768: marked as done (transition: snapd-glib 1.63)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 14:44:43 +0100
with message-id 
and subject line Re: Bug#1025768: transition: snapd-glib 1.63
has caused the Debian Bug report #1025768,
regarding transition: snapd-glib 1.63
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.)


-- 
1025768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: snapd-g...@packages.debian.org

I am ready to do the snapd-glib transition now. You can use the auto tracker:
https://release.debian.org/transitions/html/auto-snapd-glib.html

I need to do source uploads for gnome-control-center and
gnome-software for the transition but I am a team maintainer for
those. The other 2 packages can be binNMU'd.

Ubuntu completed this transition months ago and I verified today that
the 4 affected packages build successfully against the new library.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
On 2022-12-08 20:48:06 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> Hi Jeremy
> 
> On 2022-12-08 14:31:53 -0500, Jeremy Bicha wrote:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: snapd-g...@packages.debian.org
> > 
> > I am ready to do the snapd-glib transition now. You can use the auto 
> > tracker:
> > https://release.debian.org/transitions/html/auto-snapd-glib.html
> > 
> > I need to do source uploads for gnome-control-center and
> > gnome-software for the transition but I am a team maintainer for
> > those. The other 2 packages can be binNMU'd.
> > 
> > Ubuntu completed this transition months ago and I verified today that
> > the 4 affected packages build successfully against the new library.
> 
> Please go ahead

The old packages got removed from testing. Closing.

Cheers
-- 
Sebastian Ramacher--- End Message ---

Processed: reassign 1023911 to swig, forcibly merging 1024555 1023911, affects 1023911

[Debian Bug Tracking System]

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

> reassign 1023911 swig
Bug #1023911 [src:xdmf] xdmf FTBFS with SWIG 4.1.0
Bug reassigned from package 'src:xdmf' to 'swig'.
No longer marked as found in versions xdmf/3.0+git20190531-11.
Ignoring request to alter fixed versions of bug #1023911 to the same values 
previously set
> forcemerge 1024555 1023911
Bug #1024555 {Done: Jochen Sprickerhof } [swig] xdmf FTBFS 
with SWIG 4.1.0
Bug #1023911 [swig] xdmf FTBFS with SWIG 4.1.0
Marked Bug as done
Added indication that 1023911 affects src:xdmf
Marked as fixed in versions swig/4.1.0-0.2.
Marked as found in versions swig/4.1.0-0.1.
Merged 1023911 1024555
> affects 1023911 xdmf
Bug #1023911 {Done: Jochen Sprickerhof } [swig] xdmf FTBFS 
with SWIG 4.1.0
Bug #1024555 {Done: Jochen Sprickerhof } [swig] xdmf FTBFS 
with SWIG 4.1.0
Added indication that 1023911 affects xdmf
Added indication that 1024555 affects xdmf
> thanks
Stopping processing here.

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

Processed: closing 1023353

[Debian Bug Tracking System]

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

> close 1023353
Bug #1023353 [php-faker] [php-faker] Failing tests with PHP 8.2
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1022546: marked as done (rust-siphasher: please update to v0.3.9)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 13:16:51 +
with message-id 
and subject line re: rust-siphasher: please update to v0.3.9
has caused the Debian Bug report #1022546,
regarding rust-siphasher: please update to v0.3.9
to be marked as done.

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

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


-- 
1022546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-siphasher
Version: 0.3.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer upstream release v0.3.9, needed by projects I am
preparing for Debian.

  - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNVd8gACgkQLHwxRsGg
ASEHFw/9GSsaSwWLViAUadyHSmc1uxWd/fRTPl978atVXdEm369+9ymVC1K3cDMJ
ImjeUDdR1+kmnvS8s+BvReEzIH/CEYXCGuLnMua6mI69WNYoJ/XRZ6WQgWBVbLpn
IkYtdQVf7Gq5HfP7MPN6WIwvZNXvxKbaZeeNc69wQ3Z0HTnW21TLqsht0l8HO03m
DNhRNl+wnFt1DZNhjOeCjLjT15BI3ImHlwt3hq5f7X6tpYhjR+b4M6RufjT7dMcY
y1Vz9wm60lTc2Ov1a0oyrGVNbQSXRx6hGibhVRdvLuFYzsky9BhDxhjvdkw5uRVG
XR6bkOLZk7xPlqkJETRcfkjS13sbSuRM2MUiSWMbJYTCF4m+xUTSsyzEd2dCEnv+
HnPcCSDJEtUHO9LUqC7Y6YeZ1GQ/77pcLC1tC7MD3nclOrqa80O1vUaY7M3bA8vV
uVU68bMiWbdVRsaUi0JyY+SRxSBvXpgWljRkcThZfMB0FR5RSaEzL350w/gKgVQl
B0jWSj7KipQADL0WAkbm+o+BNIWCVBJrdvypkc4TvRxuFkeIgIeDTl29OQtt05mq
Zn+wc5HUEWczoZo6e5y/WdqzIN2AvvznXQTyKqPTf8vCZUHhWFSbhO0OKJMq5ioz
UMca/ctQNh5A4CsIVrB3YdS5JW3CHi3FkaW1eHd9DkKNTbWbna4=
=JKB1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

Version: 0.3.10-1

Forgot to close this one in the changelog.--- End Message ---

Bug#1022198: marked as done (rust-rustyline: please upgrade to v9)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 13:13:09 +
with message-id <9dbac8b0-0617-2d30-409f-0e3569d77...@p10link.net>
and subject line re: rust-rustyline: please upgrade to v9
has caused the Debian Bug report #1022198,
regarding rust-rustyline: please upgrade to v9
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.)


-- 
1022198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rustyline
Version: 6.3.0-5
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to newer upstream release v9, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNS81gACgkQLHwxRsGg
ASHVhQ//elkE5vVU9/MEVi8qQDZqUcFEyrpIvtA0J77BFL5ZjaO4yjsM/kRQsEjN
kAhz9Ai02S/+MBkPhipqFUcF+5XlA3JCrniIQBAxSV2D3tDHBsNd2+B2j8gDpljb
5AdiI3+aaYFaPpHc1X12rUfYN/en4kfYTVjiSa6MFzme0ctBk/DDyZvH4TDsCPw+
hcNeD5DAjZPTV+U0vuWjarkFDZY50RG3yd0vCJkenPmLLjEeUdDIO3PPVim8kpMW
y+KT/CDPbBmZaZ2ONrAy4B0j3j9LEIpTF3SxHHUorbZ87WZiokzHpxsnrH/1ptjS
MaZYL4W3+fNURkW+c5L9tYUlPbHx1ICq/r4A800YXK8fiUdfOmcapee48keIvjCI
uPgaI0/7cIEFxFBNZGZMj9rMJEl8haeXbGKSTdjrJS9sZ17PuUa4139AbOItLxS7
FMGfxTdEj610jSe4x6gnqK1e+d1TOaIGIC4bzMvDk+oXk+osUs9lGn64ogh6z6YV
lzmyR1YTBOR/YVY2alziwpuCregGDUwR8sU+avxv68HB09u+rJz9e7SOoMHH7ese
GOYa9rRw4lsgGIKiSSK66Ic2qCCaeuR2n2k4iPOO/3egvMoFG/sCsEdUviB8Bwd+
CFZ8w7v+yySC7+kaJhyWJFIZ201TCeT3SSfD61yfl3pTQ0+A7bo=
=STr3
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

Version: 9.1.2-1

Forgot to close this one in the changelog.--- End Message ---

Bug#1026155: marked as done (python3-trio: MultiError implementation conflicts with BaseExceptionGroup backport in Python 3.10)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 12:22:32 +
with message-id 
and subject line Bug#1026155: fixed in python-trio 0.22.0-0.1
has caused the Debian Bug report #1026155,
regarding python3-trio: MultiError implementation conflicts with 
BaseExceptionGroup backport in Python 3.10
to be marked as done.

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

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


-- 
1026155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-trio
Version: 0.21.0-1
Severity: serious
Tags: fixed-upstream
Control: affects -1 src:ipykernel

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package conflicts with the BaseExceptionGroup backport from
python3-exceptiongroup, which will cause ipykernel to FTBFS.

Apparently, this has been addressed in the new upstream release 0.22.0.

Relevant build log excerpt from ipykernel:

if not monkeypatched_or_warned:
>   warnings.warn(
"You seem to already have a custom sys.excepthook handler "
"installed. I'll skip installing Trio's custom handler, but this "
"means MultiErrors will not show full tracebacks.",
category=RuntimeWarning,
)
E   RuntimeWarning: You seem to already have a custom sys.excepthook 
handler installed. I'll skip installing Trio's custom handler, but this means 
MultiErrors will not show full tracebacks.

/usr/lib/python3/dist-packages/trio/_core/_multierror.py:511: RuntimeWarning

FAILED ipykernel/tests/test_async.py::test_async_interrupt[trio] - 
RuntimeWarning: You seem to already have a custom sys.excepthook handler 
installed. I'll skip installing Trio's custom handler, but this means 
MultiErrors will not show full tracebacks.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmObEGgACgkQ+C8H+466
LVm+vQwAnzg7/F631S3n2sShpH1IgA+GHN4vwpgyn9LHab0a6I5WH3GtV6pDuT7Q
NSkMahKJieGZi+Mfmhbw5QWfDMTMyGTOCtkjJpp/U+d+/srtBARCdaQcNERmY+El
M4ySgro1HFrmP7xu2S705g+UslRJWt9Lzg2EbZPfRhUAb9/AlOShSc0bxqzfMk59
7UVTJEUcZNM7cnZi+lAnDNz7ftXTE8UpquZjwDbHtuN8lL8OdSRTm1KdsTXrMKF5
QNIOepmawjxshEAomi10iKyQmLk76fwgaMS9BDoomUfzCJFwSZSgZB53sgAwsHzD
04O3Au1tZua8XOhk/0qa+sonCXcD3yKQ4nqJnMKg9WkRXNLFAYds/zl8jKD/AdSy
9mFB7CNI/tTJN05ixpHO9iokvdJHtIWDwOeF8x+xmVl9wTbiI46kmMrjCzDmHi4k
EfMPqSG8t76pkBVmwiV0oiKWSyjzb3bdeWX3NQVNFCZYDOPpEeWdxfJjBS/+Nmwg
DlV3IZvA
=s0A+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-trio
Source-Version: 0.22.0-0.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-trio 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2022 13:14:37 +0100
Source: python-trio
Architecture: source
Version: 0.22.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Robie Basak 
Changed-By: Jochen Sprickerhof 
Closes: 1026155
Changes:
 python-trio (0.22.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 0.22.0 (Closes: #1026155)
Checksums-Sha1:
 4833470ffe7e011f10d1aa386835b17eadef 2037 python-trio_0.22.0-0.1.dsc
 91c03ca9294bade2008edb09901e7caaa53d8613 472205 python-trio_0.22.0.orig.tar.gz
 8400656642fb17fd5ba3754a6392a32b06b9a6b0 2872 
python-trio_0.22.0-0.1.debian.tar.xz
 18ba31c73a69a1fd3f5bce989cd80f982a97d93f 7882 
python-trio_0.22.0-0.1_source.buildinfo
Checksums-Sha256:
 1c6ded384b298896b4cc5ddf30ce37fa12c6f2082298ae6aba46f8ebf751a8f9 2037 
python-trio_0.22.0-0.1.dsc
 ce68f1c5400a47b137c5a4de72c7c901bd4e7a24fbdebfe9b41de8c6c04eaacf 472205 
python-trio_0.22.0.orig.tar.gz
 ec1d4aaa61a060895625e24da876485e294697bf58d2ac67d70cd590ed2ff5bb 2872 
python-trio_0.22.0-0.1.debian.tar.xz
 dd0540a3b0fd9d4ae92f1d57a46dca0e385013bbbeb19fd8346b2843c5fa113b 7882 
python-trio_0.22.0-0.1_source.buildinfo
Files:
 c619663bd1dd174059c9a3386616c9c2 2037 python optional 
python-trio_0.22.0-0.1.dsc
 f7dbfa6a8722065f09da188641d8ed93 472205

Bug#1024555: marked as done (xdmf FTBFS with SWIG 4.1.0)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 11:20:46 +
with message-id 
and subject line Bug#1024555: fixed in swig 4.1.0-0.2
has caused the Debian Bug report #1024555,
regarding xdmf FTBFS with SWIG 4.1.0
to be marked as done.

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

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


-- 
1024555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdmf
Version: 3.0+git20190531-11
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xdmf&ver=3.0%2Bgit20190531-11%2Bb1

...
[ 81%] Building CXX object CMakeFiles/XdmfPython.dir/XdmfPYTHON_wrap.cxx.o
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5606:248: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5606 | SWIGINTERN std::vector< boost::shared_ptr< XdmfAttribute 
>,std::allocator< boost::shared_ptr< XdmfAttribute > > > 
*std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SggetitemSWIG_0(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT *slice){
  | 


   ^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘std::vector >* 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SggetitemSWIG_0(std::vector
 >*, int*)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5612:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5612 |   PySlice_GetIndices(slice, (Py_ssize_t)self->size(), &i, &j, 
&step);
  |  ^
  |  |
  |  int*
In file included from /usr/include/python3.10/Python.h:106,
 from 
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:168:
/usr/include/python3.10/sliceobject.h:41:46: note:   initializing argument 1 of 
‘int PySlice_GetIndices(PyObject*, Py_ssize_t, Py_ssize_t*, Py_ssize_t*, 
Py_ssize_t*)’
   41 | PyAPI_FUNC(int) PySlice_GetIndices(PyObject *r, Py_ssize_t length,
  |~~^
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: At global 
scope:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5617:149: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5617 | SWIGINTERN void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_0(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT 
*slice,std::vector< boost::shared_ptr< XdmfAttribute >,std::allocator< 
boost::shared_ptr< XdmfAttribute > > > const &v){
  | 

^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_0(std::vector
 >*, int*, const std::vector >&)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5623:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5623 |   PySlice_GetIndices(slice, (Py_ssize_t)self->size(), &i, &j, 
&step);
  |  ^
  |  |
  |  int*
/usr/include/python3.10/sliceobject.h:41:46: note:   initializing argument 1 of 
‘int PySlice_GetIndices(PyObject*, Py_ssize_t, Py_ssize_t*, Py_ssize_t*, 
Py_ssize_t*)’
   41 | PyAPI_FUNC(int) PySlice_GetIndices(PyObject *r, Py_ssize_t length,
  |~~^
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: At global 
scope:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5628:149: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5628 | SWIGINTERN void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_1(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT *slice){
  | 

^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_1(std::vector
 >*, int*)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5634:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5634 |   PySlice_GetIndices(slic

Bug#1024304: marked as done (rust-cargo-outdated - build-depends on obsolete version of rust-cargo.)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 11:18:56 +
with message-id 
and subject line Bug#1024304: fixed in rust-cargo-outdated 0.11.1-1
has caused the Debian Bug report #1024304,
regarding rust-cargo-outdated - build-depends on obsolete version of rust-cargo.
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.)


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

Package: rust-cargo-outdated
Version: 0.10.2-3
Severity: serious

Rust-cargo-outdated depends on version 0.57 of rust-cargo, debian has 0.62.
There is a new upstream version, but it still only depends on version 0.60
of the cargo crate.

I tried patching the new upstream version to use version 0.62 of the cargo
crate but it failed with.


error[E0599]: no method named `update` found for struct `Box` in 
the current scope
   --> src/cargo_ops/temp_project.rs:386:24
|
386 | source.update()?;
|^^ method not found in `Box`

error[E0599]: no method named `sort_by` found for enum `Poll` in the current 
scope
   --> src/cargo_ops/temp_project.rs:390:26
|
390 | query_result.sort_by(|a, b| b.version().cmp(a.version()));
|  ^^^ method not found in 
`Poll>`

error[E0599]: no method named `iter` found for enum `Poll` in the current scope
   --> src/cargo_ops/temp_project.rs:397:42
|
397 | let latest_result = query_result.iter().find(|summary| {
|   method not found in 
`Poll>`

error[E0608]: cannot index into a value of type 
`Poll>`
   --> src/cargo_ops/temp_project.rs:430:21
|
430 | query_result[0].version()
| ^^^

error[E0608]: cannot index into a value of type 
`Poll>`
   --> src/cargo_ops/temp_project.rs:434:18
|
434 | &query_result[0]
|  ^^^

Some errors have detailed explanations: E0599, E0608.
For more information about an error, try `rustc --explain E0599`.
error: could not compile `cargo-outdated` due to 5 previous errors


I will commit the work so far to debcargo-conf so that others can build on it.
--- End Message ---
--- Begin Message ---
Source: rust-cargo-outdated
Source-Version: 0.11.1-1
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-cargo-outdated package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Dec 2022 10:43:29 +
Source: rust-cargo-outdated
Architecture: source
Version: 0.11.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1024304
Changes:
 rust-cargo-outdated (0.11.1-1) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * Team upload.
   * Package cargo-outdated 0.11.1 from crates.io using debcargo 2.6.0
   * Update relax.dep.diff for new upstream and current situation in Debian.
 .
   [ Fabian Gruenbichler ]
   * Fix patch for cargo 0.63 compat (Closes: #1024304)
Checksums-Sha1:
 071e7c42ce321ebaaef6f268bec4ad5fd1b8d478 2626 rust-cargo-outdated_0.11.1-1.dsc
 9a3587eb2ce7d18c98cb07c73e546957df3340a6 37310 
rust-cargo-outdated_0.11.1.orig.tar.gz
 dc506fc1fd7f486d935b0010406f30d18b5ad87a 3796 
rust-cargo-outdated_0.11.1-1.debian.tar.xz
 577eaf63c00bdc656cd6341e912d6148153b0e5d 10072 
rust-cargo-outdated_0.11.1-1_source.buildinfo
Checksums-Sha256:
 d44223bbbf565834fc76fc4832eba0ad67c7320bdcddab0d43621d15c08a8655 2626 
rust-cargo-outdated_0.11.1-1.dsc
 c017ec7c7fda169c802e2374ae1c74078696eb07d12a1fbf04801c4e70acb78d 37310 
rust-cargo-outdated_0.11.1.orig.tar.gz
 d467a915b227c9362019891bcc593881da1c2632e8efd0a8fe68b1de2a559e4e 3796 
rust-cargo-outdated_0.11.1-1.debian.tar.xz
 aa35a015c71aa6fa1506eb9fe6634a01ca79d8ea826b236dbfd85efe1eb4bd0a 10072 
rust-cargo-outdated_0.11.1-1_source.buildinfo
File

Bug#1025840: marked as done (deepin-log-viewer: build-depends on dropped virtual package)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 11:06:27 +
with message-id 
and subject line Bug#1025840: fixed in deepin-log-viewer 5.9.7+ds1-2
has caused the Debian Bug report #1025840,
regarding deepin-log-viewer: build-depends on dropped virtual package
to be marked as done.

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

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


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

Source: deepin-log-viewer
Version: 5.9.7+ds1-1
Severity: serious
Tags: bookworm, sid
Justification: rc policy - "Packages must be buildable within the same release"
User:debian...@lists.debian.org
Usertags: edos-uninstallable

deepin-log-viewer build-depends on libfftw3-3, this was previously a 
transitional
package, depending on the single, double and (where available) long double 
versions
of fftw3, but has since been dropped. Please investigate which version(s) of 
fftw3
your package needs and update your build-dependencies accodingly.
--- End Message ---
--- Begin Message ---
Source: deepin-log-viewer
Source-Version: 5.9.7+ds1-2
Done: Arun Kumar Pariyar 

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

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

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

Debian distribution maintenance software
pp.
Arun Kumar Pariyar  (supplier of updated deepin-log-viewer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 15:34:08 +0545
Source: deepin-log-viewer
Architecture: source
Version: 5.9.7+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Arun Kumar Pariyar 
Changed-By: Arun Kumar Pariyar 
Closes: 1025840
Changes:
 deepin-log-viewer (5.9.7+ds1-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control:
 + Drop libfftw3-3 from B-D (Closes: #1025840).
 + Drop qtchooser from B-D.
   * d/watch: Update with dversionmangle.
   * d/copyright: Drop unused license.
Checksums-Sha1:
 fa2f0f1e178c83944bef7a4acdc4e931830bc236 2423 deepin-log-viewer_5.9.7+ds1-2.dsc
 63f8f0a0ee420e807bd07f02a189f6b4a5a49a16 5336 
deepin-log-viewer_5.9.7+ds1-2.debian.tar.xz
 693a15cdbba62acf01d6aae27229b84004f8393a 14922 
deepin-log-viewer_5.9.7+ds1-2_amd64.buildinfo
Checksums-Sha256:
 e449dca5ff8daa6fc3d0a2a96cfb31d3022ba8aa6bf3486f6ed688c4104298f0 2423 
deepin-log-viewer_5.9.7+ds1-2.dsc
 111a74725d5d932f4d4025dde6e03bd9fe7a2850b9025fa3c018bb76127d82be 5336 
deepin-log-viewer_5.9.7+ds1-2.debian.tar.xz
 7c4ac9c730dcdc0b41b03cfddb8605f20eed765911d64aa430c243109acd4d24 14922 
deepin-log-viewer_5.9.7+ds1-2_amd64.buildinfo
Files:
 951a74e93d5ab2914b035ecb7fba264b 2423 misc optional 
deepin-log-viewer_5.9.7+ds1-2.dsc
 321b15ae2ec5b286e56412b2f0d6297c 5336 misc optional 
deepin-log-viewer_5.9.7+ds1-2.debian.tar.xz
 75bb0e419a5629f0838e13afb0b8d2cb 14922 misc optional 
deepin-log-viewer_5.9.7+ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmOdkfYACgkQS1Qq9wT3
RRajLQ//T88GtjwunjuPIJuqTx4NKarlnzTj5Y9aKbRYZWwggJyesJlxmrH8Kfli
dZyxbQRnJrTYKpGrVNpob86YWO5HnV1nPZ9AitJEO1CLM08BiEN3g2aVJ0iz1BN7
DdXAVToL4FYXpR/XqhiwUPm4Qdo0bQSDJvwjrWjApwbITtAcQsjTNgdyKjzMqut+
4cdrt0N8QwiD28y9xCE4xv4DzX/2poOb2ElGJjMtNoCF4NVpaBNrr5BRsBnclDWH
14DOXtf1M7pzS0r+rC7DzQwjqYugPPHINuLdEbGRvDuU8Zp71rvawagGjiPBNX1q
gerHG9Bdx3WKnbbOwiugdlvbclvA0/zeS0pcDga5go3kROMbHM36C5MIsHkAsy5V
pVknOi96B9AJ8uPwACXkRa5ACMtvfvJ7paxlE3KgTjQvWtw2yh7DOPtmnNf/JLKi
hMcfnN53+O6AmiRb3pfXiQvhUlJCR4B3oD8EuWj6WCZ/iCpLuFuHS43jtqFKvb3K
wJ/xRU4i+y+pD2ghNsZWGKyzeN6huvz3LKVw1nmulvYlaybIr+lvYyTUJhicdIbd
b+QdC13Lt1nwiZ21x53avzzWe+roYkuOstp14wlYFX/mo8UyIdI21EPr+KpG9axZ
YPgJ/Ki8X6jo5zy7EtJJDGcVl4CtjNH3kDuWGLU1x2hlevEjq+U=
=V6Np
-END PGP SIGNATURE End Message ---

Bug#1025774: marked as done (bullseye-pu: package evolution/3.38.3-1+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025774,
regarding bullseye-pu: package evolution/3.38.3-1+deb11u1
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.)


-- 
1025774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bullseye
X-Debbugs-CC:evolut...@packages.debian.org

[ Reason ]
Adapt to Google Contacts API change

[ Impact ]
Google Contacts integration in Evolution won't work without this fix.

[ Tests ]
I manually tested this fix and the corresponding evolution-data-server
fix on Debian 11 to ensure that the fix fixes the bug.

This fix was delayed several months because the original attempts to
fix this bug were missing one of the necessary patches. This was
noticed because the manual test failed to demonstrate that the bug was
fixed.

[ Risks ]
The required patch was cherry-picked from a newer evolution series.
The upstream evolution project no longer maintains the 3.38.x branch
that Debian 11 uses.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
1 patch cherry-picked from a newer evolution series

[ Other info ]
This bug fix requires evolution-data-server to be updated too. See
https://bugs.debian.org/1025773

Thank you,
Jeremy Bicha


evolution_3.38.3-1+deb11u1.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025766: marked as done (bullseye-pu: package golang-github-go-chef-chef/0.0.1+git20161023.60.deb8c38-1.2~deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025766,
regarding bullseye-pu: package 
golang-github-go-chef-chef/0.0.1+git20161023.60.deb8c38-1.2~deb11u1
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.)


-- 
1025766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Go Packaging Team 


  * Add upstream fix for intermittent test failures. (Closes: #848055)

Test-only change to fix flaky build:
https://tests.reproducible-builds.org/debian/history/golang-github-go-chef-chef.html
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025764: marked as done (bullseye-pu: package isoquery/3.2.4-1+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025764,
regarding bullseye-pu: package isoquery/3.2.4-1+deb11u1
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.)


-- 
1025764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Dr. Tobias Quathamer 

  * Add upstream fix for test to match French translation change
in iso-codes. (Closes: #991653)

Test-only change to fix FTBFS.
diff -Nru isoquery-3.2.4/debian/changelog isoquery-3.2.4/debian/changelog
--- isoquery-3.2.4/debian/changelog 2020-12-28 18:24:11.0 +0200
+++ isoquery-3.2.4/debian/changelog 2022-12-08 20:33:56.0 +0200
@@ -1,3 +1,11 @@
+isoquery (3.2.4-1+deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for test to match French translation change
+in iso-codes. (Closes: #991653)
+
+ -- Adrian Bunk   Thu, 08 Dec 2022 20:33:56 +0200
+
 isoquery (3.2.4-1) unstable; urgency=medium
 
   * New upstream version 3.2.4
diff -Nru 
isoquery-3.2.4/debian/patches/0001-Update-test-to-match-French-translation-change-in-is.patch
 
isoquery-3.2.4/debian/patches/0001-Update-test-to-match-French-translation-change-in-is.patch
--- 
isoquery-3.2.4/debian/patches/0001-Update-test-to-match-French-translation-change-in-is.patch
   1970-01-01 02:00:00.0 +0200
+++ 
isoquery-3.2.4/debian/patches/0001-Update-test-to-match-French-translation-change-in-is.patch
   2022-12-08 20:33:56.0 +0200
@@ -0,0 +1,22 @@
+From 643d70e3472eabc55ff5186ea3e3b52efefd3cf1 Mon Sep 17 00:00:00 2001
+From: "Dr. Tobias Quathamer" 
+Date: Thu, 26 Aug 2021 20:27:19 +0200
+Subject: Update test to match French translation change in iso-codes
+
+---
+ tests/expected/iso_15924/all_localized_test_stdout.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/tests/expected/iso_15924/all_localized_test_stdout.txt 
b/tests/expected/iso_15924/all_localized_test_stdout.txt
+index 4867094..af74c26 100644
+--- a/tests/expected/iso_15924/all_localized_test_stdout.txt
 b/tests/expected/iso_15924/all_localized_test_stdout.txt
+@@ -1,4 +1,4 @@
+-Beng  325 Bengali
++Beng  325 bengali
+ Cyrl  220 cyrillique
+ Grek  200 grec
+ Latn  215 latin
+-- 
+2.30.2
+
diff -Nru isoquery-3.2.4/debian/patches/series 
isoquery-3.2.4/debian/patches/series
--- isoquery-3.2.4/debian/patches/series1970-01-01 02:00:00.0 
+0200
+++ isoquery-3.2.4/debian/patches/series2022-12-08 20:33:56.0 
+0200
@@ -0,0 +1 @@
+0001-Update-test-to-match-French-translation-change-in-is.patch
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025758: marked as done (bullseye-pu: package efitools/1.9.2-2~deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025758,
regarding bullseye-pu: package efitools/1.9.2-2~deb11u1
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.)


-- 
1025758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian UEFI Maintainers 

  * Fix occasional FTBFS due to incorrect dependency.
Closes: #1010996.

1.9.2-1 parallel build was flaky:
https://tests.reproducible-builds.org/debian/history/arm64/efitools.html
diff -Nru efitools-1.9.2/debian/changelog efitools-1.9.2/debian/changelog
--- efitools-1.9.2/debian/changelog 2019-12-23 20:39:27.0 +0200
+++ efitools-1.9.2/debian/changelog 2022-12-08 19:01:40.0 +0200
@@ -1,3 +1,20 @@
+efitools (1.9.2-2~deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for bullseye.
+
+ -- Adrian Bunk   Thu, 08 Dec 2022 19:01:40 +0200
+
+efitools (1.9.2-2) unstable; urgency=medium
+
+  [ Steve McIntyre ]
+  * Fix occasional FTBFS due to incorrect dependency.
+Closes: #1010996. Thanks to Adrian Bunk for the patch!
+
+  * Team upload
+
+ -- Steve McIntyre <93...@debian.org>  Tue, 24 May 2022 18:44:35 +
+
 efitools (1.9.2-1) unstable; urgency=medium
 
   [ Luca Boccassi ]
diff -Nru efitools-1.9.2/debian/patches/fix-deps.patch 
efitools-1.9.2/debian/patches/fix-deps.patch
--- efitools-1.9.2/debian/patches/fix-deps.patch1970-01-01 
02:00:00.0 +0200
+++ efitools-1.9.2/debian/patches/fix-deps.patch2022-05-24 
20:48:58.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix a typo in the %-blacklist.esl rule
+ This sometimes resulted in FTBFS.
+Author: Adrian Bunk 
+
+--- efitools-1.9.2.orig/Make.rules
 efitools-1.9.2/Make.rules
+@@ -71,7 +71,7 @@ endif
+ %.hash: %.efi hash-to-efi-sig-list
+   ./hash-to-efi-sig-list $< $@
+ 
+-%-blacklist.esl: %.crt cert-to-efi-hash-list
++%-blacklist.esl: %.crt cert-to-efi-sig-list
+   ./cert-to-efi-sig-list $< $@
+ 
+ %-hash-blacklist.esl: %.crt cert-to-efi-hash-list
diff -Nru efitools-1.9.2/debian/patches/series 
efitools-1.9.2/debian/patches/series
--- efitools-1.9.2/debian/patches/series2019-12-23 20:39:27.0 
+0200
+++ efitools-1.9.2/debian/patches/series2022-05-24 20:48:58.0 
+0300
@@ -1 +1,2 @@
 makefile-enable-harden-local-files.patch
+fix-deps.patch
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025756: marked as done (bullseye-pu: package nvidia-graphics-drivers/470.161.03-1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025756,
regarding bullseye-pu: package nvidia-graphics-drivers/470.161.03-1
to be marked as done.

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

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


-- 
1025756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

A huge bunch of CVEs has been fixed upstream in the supported branches
of the proprietary nvidia driver. This is probably related to the
release of an open source variant of the kernel module (with the
proprietary bits being restricted to a firmware blob).

So let's upload a new upstream release to stable.
This is not a backport from sid (which has already a 510 driver which is
not suitable for stable since it drops support for certain cards), but
an equivalent package to the already -pu'ed tesla-470 driver of the same
version.

Packaging changes include the addition some new substitutions that are
needed for the packaging of above mentioned open source kernel module
(and are included here in order to mimimize the diff between different
driver series maintained in different releases).
The (tesla-)470 driver also includes the removal of make-kpkg support
and the simplification of the -source package to only support
module-assistant. This change was only backported to 470 but not older
series since only the 470 tesla driver has sufficient upstream support
life left to be included in bookworm.

The changelog diff looks huge due to rewrapping of long lines, but
the relevant changelog entries are only

+nvidia-graphics-drivers (470.161.03-1) bullseye; urgency=medium
+
+  * New upstream production branch release 470.161.03 (2022-11-22).
+* Fixed CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677,
+  CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254,
+  CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258,
+  CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262,
+  CVE-2022-42263, CVE-2022-42264.  (Closes: #1025279)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5415
+- Fixed a bug that caused the Xorg server to crash if an NvFBC capture
+  session is started while video memory is full.
+* Improved compatibility with recent Linux kernels.  (Closes: #1024852)
+  * New upstream Tesla release (amd64 only) 470.141.10 (2022-10-19).
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+  * Add missing #includes to fix kernel module build for ppc64el.
+  * Rename the internally used ARCH variable which might clash on externally
+set values.
+  * Use substitutions for ${nvidia-kernel} and friends (510.108.03-1).
+  * Try to compile a kernel module at package build time (510.108.03-1).
+  * Upload to bullseye.
+
+ -- Andreas Beckmann   Thu, 08 Dec 2022 17:30:11 +0100
+
+nvidia-graphics-drivers (470.141.03-3) UNRELEASED; urgency=medium
+
+  * Backport get_task_ioprio changes from 510.85.02, acpi changes from
+510.85.02 and 515.65.01, drm_frambuffer.h changes from 515.76 to fix
+kernel module build for Linux 6.0.  (Closes: #1021974, #1022738)
+
+ -- Andreas Beckmann   Mon, 24 Oct 2022 18:00:40 +0200
+
+nvidia-graphics-drivers (470.141.03-2) unstable; urgency=medium
+
+  * Add support for unversioned Tesla packages (tesla 510.85.02-1).
+(Closes: #1020697)
+  * Switch *-source to a modern module-assistant based template.
+  * Drop support for kernel-package and make-kpkg, gone since stretch.
+
+ -- Andreas Beckmann   Tue, 27 Sep 2022 14:18:14 +0200

 debian/README.source   
   |  49 +--
 debian/bug-control.mk  
   |   8 +-
 debian/build-module-packages.sh.in 
   |   2 +-
 debian/changelog   
   | 741 
 debian/control 
   |  30 +-
 debian/control.in  
   |  34 +-
 debian/control.kmod
   |   6 +-
 debian/control.md5sum  
   |   8 +-
 debia

Bug#1025755: marked as done (bullseye-pu: package dovecot-fts-xapian/1.4.9a-1+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025755,
regarding bullseye-pu: package dovecot-fts-xapian/1.4.9a-1+deb11u1
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.)


-- 
1025755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Joseph Nahmias 

  * Generate dependency on dovecot ABI in use during build.
Technique stolen from dovecot-antispam packaging.
Thanks to Ron Lee  (Closes: #1009794)

debdiff of the change in the dependencies:
Depends: libc6 (>= 2.14), libgcc-s1 (>= 3.0), libicu67 (>= 67.1-1~), libstdc++6 
(>= 5.2), libxapian30 (>= [-1.4.17~)-] {+1.4.17~), dovecot-abi-2.3.abiv13+}

This ensures that on bullseye -> bookworm upgrades dovecot-fts-xapian
will be upgraded at the same time as dovecot-core.

It also fixes the less severe issue that dovecot-fts-xapian is
a plugin that was not previously depending on what it is a plugin for.
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025750: marked as done (bullseye-pu: package nvidia-graphics-drivers-tesla-470/470.161.03-1~deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025750,
regarding bullseye-pu: package 
nvidia-graphics-drivers-tesla-470/470.161.03-1~deb11u1
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.)


-- 
1025750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

A huge bunch of CVEs has been fixed upstream in the supported branches
of the proprietary nvidia driver. This is probably related to the
release of an open source variant of the kernel module (with the
proprietary bits being restricted to a firmware blob).

So let's upload a new upstream release to stable.
This is a rebuild of the package from sid with no further changes.

Packaging changes include the addition some new substitutions that are
needed for the packaging of above mentioned open source kernel module
(and are included here in order to mimimize the diff between different
driver series maintained in different releases).
The (tesla-)470 driver also includes the removal of make-kpkg support
and the simplification of the -source package to only support
module-assistant. This change was only backported to 470 but not older
series since only the 470 tesla driver has sufficient upstream support
life left to be included in bookworm.

The changelog diff looks huge due to rewrapping of long lines, but
the relevant changelog entries are only

+nvidia-graphics-drivers-tesla-470 (470.161.03-1~deb11u1) bullseye; 
urgency=medium
+
+  * Rebuild for bullseye.
+
+ -- Andreas Beckmann   Thu, 08 Dec 2022 15:30:30 +0100
+
+nvidia-graphics-drivers-tesla-470 (470.161.03-1) unstable; urgency=medium
+
+  * New upstream production branch release 470.161.03 (2022-11-22).
+* Fixed CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677,
+  CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254,
+  CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258,
+  CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262,
+  CVE-2022-42263, CVE-2022-42264.  (Closes: #1025285)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5415
+- Fixed a bug that caused the Xorg server to crash if an NvFBC capture
+  session is started while video memory is full.
+* Improved compatibility with recent Linux kernels.
+  * New upstream Tesla release (amd64 only) 470.141.10 (2022-10-19).
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+  * Add missing #includes to fix kernel module build for ppc64el.
+  * Rename the internally used ARCH variable which might clash on externally
+set values.
+  * Use substitutions for ${nvidia-kernel} and friends (510.108.03-1).
+  * Try to compile a kernel module at package build time (510.108.03-1).
+
+ -- Andreas Beckmann   Thu, 08 Dec 2022 15:18:42 +0100
+
+nvidia-graphics-drivers-tesla-470 (470.141.03-3) unstable; urgency=medium
+
+  * Backport get_task_ioprio changes from 510.85.02, acpi changes from
+510.85.02 and 515.65.01, drm_frambuffer.h changes from 515.76 to fix
+kernel module build for Linux 6.0.  (Closes: #1021974, #1022738)
+
+ -- Andreas Beckmann   Mon, 24 Oct 2022 18:00:40 +0200
+
+nvidia-graphics-drivers-tesla-470 (470.141.03-2) unstable; urgency=medium
+
+  * Rebuild as Tesla 470 driver.
+
+ -- Andreas Beckmann   Tue, 27 Sep 2022 16:37:25 +0200
+
+nvidia-graphics-drivers (470.141.03-2) unstable; urgency=medium
+
+  * Add support for unversioned Tesla packages (tesla 510.85.02-1).
+(Closes: #1020697)
+  * Switch *-source to a modern module-assistant based template.
+  * Drop support for kernel-package and make-kpkg, gone since stretch.
+
+ -- Andreas Beckmann   Tue, 27 Sep 2022 14:18:14 +0200

 debian/README.source   
   |  49 +--
 debian/bug-control.mk  
   |   8 +-
 debian/build-module-packages.sh.in 
   |   2 +-
 debian/changelog   
   | 761 +---
 debian/control 
   |  27 +-
 debian/control.in  
   |  34 +-
 debian/control

Bug#1025754: marked as done (bullseye-pu: package containerd/1.4.13~ds1-1~deb11u3)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025754,
regarding bullseye-pu: package containerd/1.4.13~ds1-1~deb11u3
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.)


-- 
1025754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: contain...@packages.debian.org, z...@debian.org
Control: affects -1 + src:containerd

[ Reason ]

Backport patch for CVE-2022-23471.

https://github.com/containerd/containerd/security/advisories/GHSA-2qjp-425j-52j9

> A bug was found in containerd's CRI implementation where a user can exhaust
> memory on the host.

[ Impact ]


[ Tests ]

No new test is added, but the patch is simple and easy to review.
It is taken from upstream 1.5 release branch without modification.

[ Risks ]

Code is trivial.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]

See attachment

[ Other info ]

No
diff -Nru containerd-1.4.13~ds1/debian/changelog 
containerd-1.4.13~ds1/debian/changelog
--- containerd-1.4.13~ds1/debian/changelog  2022-06-07 03:07:20.0 
+0800
+++ containerd-1.4.13~ds1/debian/changelog  2022-12-08 10:24:34.0 
+0800
@@ -1,3 +1,9 @@
+containerd (1.4.13~ds1-1~deb11u3) bullseye; urgency=medium
+
+  * CVE-2022-23471: CRI plugin: Fix goroutine leak during Exec
+
+ -- Shengjing Zhu   Thu, 08 Dec 2022 10:24:34 +0800
+
 containerd (1.4.13~ds1-1~deb11u2) bullseye-security; urgency=high
 
   * CVE-2022-31030: CRI plugin: Host memory exhaustion through ExecSync
diff -Nru containerd-1.4.13~ds1/debian/patches/0011-CVE-2022-23471.patch 
containerd-1.4.13~ds1/debian/patches/0011-CVE-2022-23471.patch
--- containerd-1.4.13~ds1/debian/patches/0011-CVE-2022-23471.patch  
1970-01-01 08:00:00.0 +0800
+++ containerd-1.4.13~ds1/debian/patches/0011-CVE-2022-23471.patch  
2022-12-08 10:24:34.0 +0800
@@ -0,0 +1,56 @@
+From: Danny Canter 
+Date: Mon, 28 Nov 2022 14:45:34 -0800
+Subject: CVE-2022-23471
+
+Origin: backport, https://github.com/containerd/containerd/commit/6cd11527
+---
+ .../cri/pkg/streaming/remotecommand/httpstream.go | 15 ---
+ 1 file changed, 12 insertions(+), 3 deletions(-)
+
+diff --git 
a/vendor/github.com/containerd/cri/pkg/streaming/remotecommand/httpstream.go 
b/vendor/github.com/containerd/cri/pkg/streaming/remotecommand/httpstream.go
+index 0417a1a..9177fa7 100644
+--- 
a/vendor/github.com/containerd/cri/pkg/streaming/remotecommand/httpstream.go
 
b/vendor/github.com/containerd/cri/pkg/streaming/remotecommand/httpstream.go
+@@ -33,6 +33,7 @@ limitations under the License.
+ package remotecommand
+ 
+ import (
++  gocontext "context"
+   "encoding/json"
+   "errors"
+   "fmt"
+@@ -132,7 +133,7 @@ func createStreams(req *http.Request, w 
http.ResponseWriter, opts *Options, supp
+ 
+   if ctx.resizeStream != nil {
+   ctx.resizeChan = make(chan remotecommand.TerminalSize)
+-  go handleResizeEvents(ctx.resizeStream, ctx.resizeChan)
++  go handleResizeEvents(req.Context(), ctx.resizeStream, 
ctx.resizeChan)
+   }
+ 
+   return ctx, true
+@@ -425,7 +426,7 @@ WaitForStreams:
+ // supportsTerminalResizing returns false because v1ProtocolHandler doesn't 
support it.
+ func (*v1ProtocolHandler) supportsTerminalResizing() bool { return false }
+ 
+-func handleResizeEvents(stream io.Reader, channel chan<- 
remotecommand.TerminalSize) {
++func handleResizeEvents(ctx gocontext.Context, stream io.Reader, channel 
chan<- remotecommand.TerminalSize) {
+   defer runtime.HandleCrash()
+   defer close(channel)
+ 
+@@ -435,7 +436,15 @@ func handleResizeEvents(stream io.Reader, channel chan<- 
remotecommand.TerminalS
+   if err := decoder.Decode(&size); err != nil {
+   break
+   }
+-  channel <- size
++
++  select {
++  case channel <- size:
++  case <-ctx.Done():
++  // To avoid leaking this routine, exit if the http 
request finishes. This path
++  // would generall

Bug#1025716: marked as done (bullseye-pu: package mutt/2.0.5-4.1+deb11u2)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025716,
regarding bullseye-pu: package mutt/2.0.5-4.1+deb11u2
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.)


-- 
1025716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: m...@packages.debian.org, Marc Haber 
, "Kevin J. McCarthy" , Antonio 
Radici , car...@debian.org
Control: affects -1 + src:mutt

Hi Stable release managers,

[ Reason ]
mutt in bullseye (fixed in unstable already) is affected by #1024427,
mutt segfaults in pgp_gpgme_extract_keys(). The bug #1024427 attaches
a test mailbox (originally from debian-mentors list) to verify the
fix.

[ Impact ]
mutt crash if user opens problemac mail triggering the issue.

[ Tests ]
Explicitly tested agains the testcase attached in #bug1024427.

[ Risks ]
Patches are taken from upstream, with upstream indicating to them in
https://bugs.debian.org/1024427#10

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Adds the three patches from upstream. Quoting upstream: The first is
just a cleaned up version of the patch you tested. The second fixes a
bug in the same function when used with older versions of gpgme. The
last fixes a similar potential key->uid dereference bug elsewhere in
the gpgme code.

[ Other info ]
None.

Regards,
Salvatore
diff -Nru mutt-2.0.5/debian/changelog mutt-2.0.5/debian/changelog
--- mutt-2.0.5/debian/changelog 2022-04-23 14:44:09.0 +0200
+++ mutt-2.0.5/debian/changelog 2022-12-07 22:39:58.0 +0100
@@ -1,3 +1,12 @@
+mutt (2.0.5-4.1+deb11u2) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix gpgme crash when listing keys in a public key block (Closes: #1024427)
+  * Fix public key block listing for old versions of gpgme
+  * Add a check for key->uids in create_recipient_set
+
+ -- Salvatore Bonaccorso   Wed, 07 Dec 2022 22:39:58 +0100
+
 mutt (2.0.5-4.1+deb11u1) bullseye; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mutt-2.0.5/debian/patches/series mutt-2.0.5/debian/patches/series
--- mutt-2.0.5/debian/patches/series2022-04-23 14:44:09.0 +0200
+++ mutt-2.0.5/debian/patches/series2022-12-07 22:39:58.0 +0100
@@ -15,3 +15,6 @@
 upstream/985152-body-color-slowness.patch
 upstream/Fix-seqset-iterator-when-it-ends-in-a-comma.patch
 upstream/Fix-uudecode-buffer-overflow.patch
+upstream/Fix-gpgme-crash-when-listing-keys-in-a-public-key-bl.patch
+upstream/Fix-public-key-block-listing-for-old-versions-of-gpg.patch
+upstream/Add-a-check-for-key-uids-in-create_recipient_set.patch
diff -Nru 
mutt-2.0.5/debian/patches/upstream/Add-a-check-for-key-uids-in-create_recipient_set.patch
 
mutt-2.0.5/debian/patches/upstream/Add-a-check-for-key-uids-in-create_recipient_set.patch
--- 
mutt-2.0.5/debian/patches/upstream/Add-a-check-for-key-uids-in-create_recipient_set.patch
   1970-01-01 01:00:00.0 +0100
+++ 
mutt-2.0.5/debian/patches/upstream/Add-a-check-for-key-uids-in-create_recipient_set.patch
   2022-12-07 22:39:58.0 +0100
@@ -0,0 +1,30 @@
+From b254f2fb44f994c48e2491adaf03d97d3c628283 Mon Sep 17 00:00:00 2001
+From: Kevin McCarthy 
+Date: Tue, 1 Nov 2022 20:22:06 -0700
+Subject: [PATCH] Add a check for key->uids in create_recipient_set.
+
+For gpgme < 1.11.0, it used this function to create the encryption key
+list.  The '!' was interpreted differently back then, and it
+apparently didn't check if the returned key had any uids before
+referencing it.  Add a check to prevent a segv as in the public key
+block fix.
+---
+ crypt-gpgme.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/crypt-gpgme.c b/crypt-gpgme.c
+index bf120ab50fc2..fdf44af4fe3d 100644
+--- a/crypt-gpgme.c
 b/crypt-gpgme.c
+@@ -915,7 +915,7 @@ static gpgme_key_t *create_recipient_set (const char 
*keylist, int use_smime)
+ buf[i-1] = 0;
+ 
+ err = gpgme_get_key (context, buf, &key, 0);
+-if (! err)
++if (! err && key->uids)
+   key->uids->validity = GPGME_VALIDITY_FULL;
+ buf[i-1] = '!';
+   }
+

Bug#1025710: marked as done (bullseye-pu: package awstats/7.8-2+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025710,
regarding bullseye-pu: package awstats/7.8-2+deb11u1
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.)


-- 
1025710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: awst...@packages.debian.org, car...@debian.org
Control: affects -1 + src:awstats

Hi Stable release managers,

awstats is prone to a XSS vulnerability, but it does not warrant a
DSA. Following the QA upload to unstable (which should migrate in two
days), I would like to propose the change as well for stable and have
it included in the next point release.

CVE-2022-46391 is assigned to the issue (Cf. #1025410)
https://github.com/eldy/AWStats/pull/226

[ Impact ]
Issue remains open, but might be cherry-picked as well for furture
upload via security or in the next point release.

[ Tests ]
None specific

[ Risks ]
It is a targetted fix for the reporte XSS vulnerability.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]

   * fix cross site scripting (CVE-2022-46391) (Closes: #1025410)

[ Other info ]
Nothing I'm aware of.

Regards,
Salvatore
diff -Nru awstats-7.8/debian/changelog awstats-7.8/debian/changelog
--- awstats-7.8/debian/changelog2021-02-02 08:56:57.0 +0100
+++ awstats-7.8/debian/changelog2022-12-07 21:47:25.0 +0100
@@ -1,3 +1,10 @@
+awstats (7.8-2+deb11u1) bullseye; urgency=medium
+
+  * QA upload.
+  * fix cross site scripting (CVE-2022-46391) (Closes: #1025410)
+
+ -- Salvatore Bonaccorso   Wed, 07 Dec 2022 21:47:25 +0100
+
 awstats (7.8-2) unstable; urgency=high
 
   * QA upload.
diff -Nru awstats-7.8/debian/patches/fix-cross-site-scripting.patch 
awstats-7.8/debian/patches/fix-cross-site-scripting.patch
--- awstats-7.8/debian/patches/fix-cross-site-scripting.patch   1970-01-01 
01:00:00.0 +0100
+++ awstats-7.8/debian/patches/fix-cross-site-scripting.patch   2022-12-07 
21:47:25.0 +0100
@@ -0,0 +1,29 @@
+From: rekter0 <58881147+rekt...@users.noreply.github.com>
+Date: Mon, 7 Nov 2022 15:12:03 +0100
+Subject: fix cross site scripting
+Origin: 
https://github.com/eldy/AWStats/commit/38682330e1ec3f3af95f9436640358b2d9e4a965
+Bug: https://github.com/eldy/AWStats/pull/226
+Bug-Debian: https://bugs.debian.org/1025410
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2022-46391
+
+xss due to printing response from Net::XWhois without proper checks
+---
+ wwwroot/cgi-bin/plugins/hostinfo.pm | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/wwwroot/cgi-bin/plugins/hostinfo.pm 
b/wwwroot/cgi-bin/plugins/hostinfo.pm
+index 95b2c20b7b91..1f0ac699459d 100644
+--- a/wwwroot/cgi-bin/plugins/hostinfo.pm
 b/wwwroot/cgi-bin/plugins/hostinfo.pm
+@@ -181,7 +181,7 @@ sub BuildFullHTMLOutput_hostinfo {
+ 
+   &tab_head("Full Whois Field",0,0,'whois');
+   if ($w && $w->response()) {
+-  print "".($w->response())."\n";
++  print "".CleanXSS($w->response())."\n";
+   }
+   else {
+   print "The Whois command failed.Did the 
server running AWStats is allowed to send WhoIs queries (If a firewall is 
running, port 43 should be opened from inside to outside) ?\n";
+-- 
+2.38.1
+
diff -Nru awstats-7.8/debian/patches/series awstats-7.8/debian/patches/series
--- awstats-7.8/debian/patches/series   2021-02-02 08:56:57.0 +0100
+++ awstats-7.8/debian/patches/series   2022-12-07 21:47:25.0 +0100
@@ -11,3 +11,4 @@
 2008_twitter.patch
 2009_googlesearch.patch
 0013-Only-look-for-configuration-in-dedicated-awstats-dir.patch
+fix-cross-site-scripting.patch
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025700: marked as done (bullseye-pu: package virglrenderer/0.8.2-5+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025700,
regarding bullseye-pu: package virglrenderer/0.8.2-5+deb11u1
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.)


-- 
1025700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Gert Wollny 

(CC'ing Gert Wollny  as maintainer of virglrenderer so he is 
aware)

[ Reason ]

I'm currently preparing a security update for virglrenderer for LTS
and figured out that there is one of the fixed CVEs is not adressed in bullseye
yet.

The CVE fixed is CVE-2022-0135: (#1009073)

To have this CVE also fixed in bullseye, I'm asking for permission to upload a
targeted fix for the next stable point release.

The changes are on this branch:
https://salsa.debian.org/debian/virglrenderer/-/tree/debian/bullseye
namely adding this patch:
https://salsa.debian.org/debian/virglrenderer/-/blob/debian/bullseye/debian/patches/CVE-2022-0135.patch


[ Impact ]
The description of CVE-2022-0135 is:
 An out-of-bounds write issue was found in the VirGL virtual OpenGL renderer
 (virglrenderer). This flaw allows a malicious guest to create a specially
 crafted virgil resource and then issue a VIRTGPU_EXECBUFFER ioctl, leading to a
 denial of service or possible code execution.

[ Tests ]

Upstream provides a unit-text which covers this CVE.

[ Risks ]

The patch is taken from upstream:
https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/95e581fd181b213c2ed7cdc63f2abc03eaaa77ec

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

-- 
tobi
diff -Nru virglrenderer-0.8.2/debian/changelog 
virglrenderer-0.8.2/debian/changelog
--- virglrenderer-0.8.2/debian/changelog2020-12-07 13:38:41.0 
+0100
+++ virglrenderer-0.8.2/debian/changelog2022-12-07 17:24:59.0 
+0100
@@ -1,3 +1,10 @@
+virglrenderer (0.8.2-5+deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload by the LTS Security Team.
+  * Cherry-pick upstream fix for CVE-2022-0135. (Closes: #1009073)
+
+ -- Tobias Frost   Wed, 07 Dec 2022 17:24:59 +0100
+
 virglrenderer (0.8.2-5) unstable; urgency=medium
 
   [ Christian Ehrhardt ]
diff -Nru virglrenderer-0.8.2/debian/patches/CVE-2022-0135.patch 
virglrenderer-0.8.2/debian/patches/CVE-2022-0135.patch
--- virglrenderer-0.8.2/debian/patches/CVE-2022-0135.patch  1970-01-01 
01:00:00.0 +0100
+++ virglrenderer-0.8.2/debian/patches/CVE-2022-0135.patch  2022-12-07 
17:24:59.0 +0100
@@ -0,0 +1,83 @@
+Description: CVE-2022-0135
+ An out-of-bounds write issue was found in the VirGL virtual OpenGL
+ renderer (virglrenderer). This flaw allows a malicious guest to create a
+ specially crafted virgil resource and then issue a VIRTGPU_EXECBUFFER ioctl,
+ leading to a denial of service or possible code execution.  
+Origin: 
https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/95e581fd181b213c2ed7cdc63f2abc03eaaa77ec
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009073
+Last-Update: 2022-12-05 
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/vrend_renderer.c
 b/src/vrend_renderer.c
+@@ -7097,8 +7097,11 @@
+   info->box->height) * elsize;
+   if (res->target == GL_TEXTURE_3D ||
+   res->target == GL_TEXTURE_2D_ARRAY ||
++  res->target == GL_TEXTURE_2D_MULTISAMPLE_ARRAY ||
+   res->target == GL_TEXTURE_CUBE_MAP_ARRAY)
+   send_size *= info->box->depth;
++  else if (need_temp && info->box->depth != 1)
++ return EINVAL;
+ 
+   if (need_temp) {
+  data = malloc(send_size);
+--- a/tests/test_fuzzer_formats.c
 b/tests/test_fuzzer_formats.c
+@@ -958,6 +958,48 @@
+ virgl_renderer_submit_cmd((void *) cmd, ctx_id, 0xde);
+ }
+ 
++/* Test adapted from yaojun8558...@gmail.com:
++ * https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/250
++*/
++static void test_vrend_3d_resource_overflow() {
++
++struct virgl_renderer_resource_create_args resource;
++resource.handle = 0x4c474572;
++resource.target = PIPE_TEXTURE_2D_A

Bug#1025646: marked as done (bullseye-pu: package libapache2-mod-auth-mellon/0.17.0-1+deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025646,
regarding bullseye-pu: package libapache2-mod-auth-mellon/0.17.0-1+deb11u1
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.)


-- 
1025646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I propose this upload to bullseye to fix a relatively minor security issue
(open redirect) in libapache2-mod-auth-mellon.

The changes are already in sid and bookworm for a longer time.


Cheers,
Thijs
diff -Nru libapache2-mod-auth-mellon-0.17.0/debian/changelog 
libapache2-mod-auth-mellon-0.17.0/debian/changelog
--- libapache2-mod-auth-mellon-0.17.0/debian/changelog  2020-09-08 
12:56:41.0 +0200
+++ libapache2-mod-auth-mellon-0.17.0/debian/changelog  2022-12-06 
20:12:37.0 +0100
@@ -1,3 +1,10 @@
+libapache2-mod-auth-mellon (0.17.0-1+deb11u1) bullseye; urgency=medium
+
+  * Upload to fix security issue:
+- Open redirect in logout endpoint (CVE-2021-3639)
+
+ -- Thijs Kinkhorst   Tue, 06 Dec 2022 20:12:37 +0100
+
 libapache2-mod-auth-mellon (0.17.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru libapache2-mod-auth-mellon-0.17.0/debian/patches/CVE-2021-3639.patch 
libapache2-mod-auth-mellon-0.17.0/debian/patches/CVE-2021-3639.patch
--- libapache2-mod-auth-mellon-0.17.0/debian/patches/CVE-2021-3639.patch
1970-01-01 01:00:00.0 +0100
+++ libapache2-mod-auth-mellon-0.17.0/debian/patches/CVE-2021-3639.patch
2022-12-06 20:12:37.0 +0100
@@ -0,0 +1,44 @@
+From 42a11261b9dad2e48d70bdff7c53dd57a12db6f5 Mon Sep 17 00:00:00 2001
+From: AIMOTO Norihito 
+Date: Tue, 6 Jul 2021 22:57:24 +0200
+Subject: [PATCH] Prevent redirect to URLs that begin with '///'
+
+Visiting a logout URL like this:
+
https://rp.example.co.jp/mellon/logout?ReturnTo=///fishing-site.example.com/logout.html
+would have redirected the user to fishing-site.example.com
+
+With the patch, this URL would be rejected.
+
+Fixes: CVE-2021-3639
+---
+ auth_mellon_util.c | 10 ++
+ 1 file changed, 10 insertions(+)
+
+diff --git a/auth_mellon_util.c b/auth_mellon_util.c
+index 2f8c9c3..6a686db 100644
+--- a/auth_mellon_util.c
 b/auth_mellon_util.c
+@@ -927,6 +927,10 @@ int am_check_url(request_rec *r, const char *url)
+ {
+ const char *i;
+ 
++if (url == NULL) {
++return HTTP_BAD_REQUEST;
++}
++
+ for (i = url; *i; i++) {
+ if (*i >= 0 && *i < ' ') {
+ /* Deny all control-characters. */
+@@ -943,6 +947,12 @@ int am_check_url(request_rec *r, const char *url)
+ }
+ }
+ 
++if (strstr(url, "///") == url) {
++AM_LOG_RERROR(APLOG_MARK, APLOG_ERR, HTTP_BAD_REQUEST, r,
++  "URL starts with '///'");
++return HTTP_BAD_REQUEST;
++}
++
+ return OK;
+ }
+ 
diff -Nru libapache2-mod-auth-mellon-0.17.0/debian/patches/series 
libapache2-mod-auth-mellon-0.17.0/debian/patches/series
--- libapache2-mod-auth-mellon-0.17.0/debian/patches/series 2020-01-27 
14:32:39.0 +0100
+++ libapache2-mod-auth-mellon-0.17.0/debian/patches/series 2022-12-06 
20:12:37.0 +0100
@@ -0,0 +1 @@
+CVE-2021-3639.patch
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.6

Hi,

Each of the updates referred to in these requests was included in this
morning's 11.6 point release.

Regards,

Adam--- End Message ---

Bug#1025652: marked as done (bullseye-pu: package nvidia-graphics-drivers-legacy-390xx/390.157-1~deb11u1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id 
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025652,
regarding bullseye-pu: package 
nvidia-graphics-drivers-legacy-390xx/390.157-1~deb11u1
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.)


-- 
1025652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

A huge bunch of CVEs has been fixed upstream in the supported branches
of the proprietary nvidia driver. This is probably related to the
release of an open source variant of the kernel module (with the
proprietary bits being restricted to a firmware blob).

So let's upload a new upstream release to stable.
This is a rebuild of the package from sid with no further changes.

Packaging changes include the addition some new substitutions that are
needed for the packaging of above mentioned open source kernel module
(and are included here in order to mimimize the diff between different
driver series maintained in different releases).

The changelog diff looks huge due to rewrapping of long lines, but
the relevant changelog entries are only

+nvidia-graphics-drivers-legacy-390xx (390.157-1~deb11u1) bullseye; 
urgency=medium
+
+  * Rebuild for bullseye.
+
+ -- Andreas Beckmann   Tue, 06 Dec 2022 23:15:45 +0100
+
+nvidia-graphics-drivers-legacy-390xx (390.157-1) unstable; urgency=medium
+
+  * New upstream legacy branch release 390.157 (2022-11-22).
+* Fixed CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677,
+  CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259.
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5415
+  (Closes: #1025281)
+* Improved compatibility with recent Linux kernels.
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+  * Rename the internally used ARCH variable which might clash on externally
+set values.
+  * Use substitutions for ${nvidia-kernel} and friends (510.108.03-1).
+  * Try to compile a kernel module at package build time (510.108.03-1).
+
+ -- Andreas Beckmann   Sat, 03 Dec 2022 22:17:01 +0100
+
+nvidia-graphics-drivers-legacy-390xx (390.154-2) unstable; urgency=medium
+
+  * Backport nv_install_notifier changes from 418.30, acpi changes from
+430.09, 510.85.02 and 515.65.01, drm_frambuffer.h changes from 515.76 to
+fix kernel module build for Linux 6.0.
+
+ -- Andreas Beckmann   Thu, 20 Oct 2022 11:57:16 +0200

 debian/README.source   
  |  49 ++---
 debian/bug-control.mk  
  |   8 +-
 debian/build-module-packages.sh.in 
  |   2 +-
 debian/changelog   
  | 478 +++--
 debian/control 
  |  21 ++-
 debian/control.in  
  |  25 +--
 debian/control.kmod
  |   6 +-
 debian/control.md5sum  
  |   8 +-
 debian/gbp.conf
  |   2 +-
 debian/module/debian/control.modules.in.binary.in  
  |  21 +++
 debian/module/debian/control.template.binary.in
  |  21 ---
 debian/module/debian/patches/0001-backport-error-on-unknown-conftests.patch
  |  17 +-
 
debian/module/debian/patches/0002-backport-error-on-unknown-conftests-uvm-part.patch
 |   2 +-
 
debian/module/debian/patches/0003-backport-set_-memory-pages-_array-_uc-changes-from-5.patch
 |  10 +-
 debian/module/debian/patches/0004-fix-conftest-includes.patch  
  |  10 +-
 debian/module/debian/patches/arm-outer-sync.patch  
  |   4 +-
 debian/module/debian/patches/armhf-on-arm64-kernel.patch   
  |   4 +-
 debian/module/debian/patches/bashisms.patch
  |   2