Bug#985840: gitlab-shell: should not ship /usr/bin/check
On 18/12/22 03:06 AM, Abhijith PA wrote: > Praveen, mdbilal > > On 24/03/21 07:11 PM, Julien Cristau wrote: > > ... > > > /usr/bin/check seems like an awfully generic program name to be shipped > > in something like gitlab-shell. Please don't. > > I have reported this upstream. > https://gitlab.com/gitlab-org/gitlab-shell/-/issues/603 Hey, I didn't know you reported upstream long time before. https://gitlab.com/gitlab-org/gitlab-shell/-/issues/197 I will close my issue opened upstream. --abhijith
Processed: tagging 1026256
Processing commands for cont...@bugs.debian.org: > tags 1026256 + pending Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1026256, bug 1026256 is forwarded to https://github.com/backuppc/backuppc/issues/466
Processing commands for cont...@bugs.debian.org: > tags 1026256 + fixed-upstream Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Added tag(s) fixed-upstream. > forwarded 1026256 https://github.com/backuppc/backuppc/issues/466 Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Set Bug forwarded-to-address to 'https://github.com/backuppc/backuppc/issues/466'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024078: pytango FTBFS with Python 3.11 as supported version
Source: pytango Followup-For: Bug #1024078 As a maintenance note: it looks like upstream pytango v9.4.0 should resolve this; it includes compatibility[1] with Python 3.11. That release is currently planned[2] for the end of January, 2023. [1] - https://gitlab.com/tango-controls/pytango/-/merge_requests/498 [2] - https://gitlab.com/tango-controls/pytango/-/issues/491#note_1193929461
Processed: merge 1020018 1025733
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#1025733: merge 1020018 1025733
forcemerge 1020018 1025733 thanks This is a duplicate. 1020018 is closed by libxmlada/23.0.0-1 in experimental.
Bug#1026304: obantoo build-depends on dropped package.
Package: obantoo Version: 2.1.12+ds1-3 Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable obantoo build-depends on libitext5-java-doc which is no longer built by the libitext5-java source package. It is still present in unstable as a cruft package, but is completely gone from testing.
Bug#1026298: datalad: FTBFS without network access
Source: datalad Version: 0.17.10-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen on reproducible builds [1], datalad 0.17.10-1 FTBFS without network access. I've copied what I hope is the relevant part of a successful build below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/datalad.html Installed /<> Processing dependencies for datalad==0.17.10 Searching for chardet<5.0.0,>=3.0.4 Reading https://pypi.org/simple/chardet/ /usr/lib/python3/dist-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: is an invalid version and will not be supported in a future release warnings.warn( Downloading https://files.pythonhosted.org/packages/19/c7/fa589626997dd07bd87d9269342ccb74b1720384a4d739a1872bd84fbe68/chardet-4.0.0-py2.py3-none-any.whl#sha256=f864054d66fd9118f2e67044ac8981a54775ec5b67aed0441892edb553d21da5 Best match: chardet 4.0.0 Processing chardet-4.0.0-py2.py3-none-any.whl Installing chardet-4.0.0-py2.py3-none-any.whl to /<>/bin Adding chardet 4.0.0 to easy-install.pth file Installing chardetect script to bin
Bug#1025869: marked as pending in tigervnc
Hi Joachim, Thank you! I installed the patched .pm files and retested. *One error is fixed:* Can't locate object method "cleanup" via package "File::Temp::Dir" at /usr/share/perl5/TigerVNC/Wrapper.pm line 1347, line 100.) *The other error still remains:* $ x0vncserver -display :0 -SecurityTypes None *result:* [usage is printed] then x0vncserver: /usr/bin/X0tigervnc exited with status 1, please look into '/home/mark/.vnc/[redacted]:5900.log' to determine the reason! -2 /home/mark/.vnc/[redacted]:5900.log contains only the same information as above under result: *Note that the following does not return an error.* * * *X0tigervnc* -display :0 -SecurityTypes None I hope that helps. Thank you! Mark On Sat, Dec 17, 2022, at 11:15 AM, Joachim Falk wrote: > Control: tag -1 pending > > Hello, > > Bug #1025869 in tigervnc reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/debian-remote-team/tigervnc/-/commit/b0e4724c81f7dc9198c4685839ff38b35e5a1543 > > > Fixed some undef warnings and a tempdir cleanup error (closes: #1025869) > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/1025869 >
Processed: unifrac-tools: Frequent parallel FTBFS
Processing control commands:
> block 1021542 by -1
Bug #1021542 {Done: Andreas Tille } [src:unifrac] unifrac:
partially taken over by src:unifrac-tools
1021542 was blocked by: 1021378
1021542 was not blocking any bugs.
Added blocking bug(s) of 1021542: 1026297
--
1021542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021542
1026297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026297: unifrac-tools: Frequent parallel FTBFS
Source: unifrac-tools Version: 1.1.3-1 Severity: serious Tags: ftbfs patch Control: block 1021542 by -1 https://tests.reproducible-builds.org/debian/history/unifrac-tools.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/unifrac-tools.html https://buildd.debian.org/status/logs.php?pkg=unifrac-tools=arm64 ... make[3]: Entering directory '/<>/src' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[3]: Entering directory '/<>/src' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[3]: Entering directory '/<>/src' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. ... h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -Wextra -Wno-unused-parameter -Wall -std=c++14 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib faithpd.cpp -o faithpd tree.o biom.o unifrac_internal.o unifrac_cmp_cpu.o unifrac.o cmd.o skbio_alt.o api.o -lhdf5_cpp -llz4 -llapacke -lblas -lpthread h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -Wextra -Wno-unused-parameter -Wall -std=c++14 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib faithpd.cpp -o faithpd tree.o biom.o unifrac_internal.o unifrac_cmp_cpu.o unifrac.o cmd.o skbio_alt.o api.o -lhdf5_cpp -llz4 -llapacke -lblas -lpthread /usr/bin/ld: /usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu/Scrt1.o: in function `_start': (.text+0x1c): undefined reference to `main' /usr/bin/ld: (.text+0x20): undefined reference to `main' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:108: faithpd] Error 1 The problem is the toplevel Makefile calling make in src/ up to three times in parallel during the build. The easiest workaround is: --- debian/rules.old2022-12-17 22:53:06.643268060 + +++ debian/rules2022-12-17 22:53:11.403264194 + @@ -7,7 +7,7 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all %: - dh $@ + dh $@ --no-parallel override_dh_auto_build: mkdir -p $(CURDIR)/debian/tmp/usr/bin
Bug#1026289: marked as done (surf: The app opens, only displays a blank page)
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 ---
Bug#1026294: vip-manager: FTBFS: cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to arp.NewPacket
Source: vip-manager Version: 1.0.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs vip-manager is failing to build in a clean sid schroot: > github.com/cybertec-postgresql/vip-manager/ipmanager > # github.com/cybertec-postgresql/vip-manager/ipmanager > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:101:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:103:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:125:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:127:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket signature.asc Description: This is a digitally signed message part
Bug#985840: gitlab-shell: should not ship /usr/bin/check
Praveen, mdbilal On 24/03/21 07:11 PM, Julien Cristau wrote: ... > /usr/bin/check seems like an awfully generic program name to be shipped > in something like gitlab-shell. Please don't. I have reported this upstream. https://gitlab.com/gitlab-org/gitlab-shell/-/issues/603 For now, this will work. https://salsa.debian.org/go-team/packages/gitlab-shell/-/commit/0a36733fd8bc2ba10f9a7afd3ab306c96114d5a9 --abhijith signature.asc Description: PGP signature
Bug#1023688: incorrect syntax in patch
The modification to fcgiwrap.socket doesn’t appear to use values recognised by systemd. I believe the configuration: Mode=0660 SocketUser=www-data SockerGroup=www-data Should actually be: SocketMode=0660 SocketUser=www-data SocketGroup=www-data
Processed: your mail
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
Processed: fixed 1023239 in 057+157-2
Processing commands for cont...@bugs.debian.org:
> fixed 1023239 057+157-2
Bug #1023239 {Done: Thomas Lange } [dracut] dracut:
[regression] missing grep
Marked as fixed in versions dracut/057+157-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026240: marked as done ([deluge] crashes on load)
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 ---
Bug#1026172: mono: FTBFS on mipsel
Hi Jo, On Thu, Dec 15, 2022 at 03:04:35PM -0500, Jo Shields wrote: > What hardware is in the mipsel-osuosl-* machines? Mono has a history of > triggering hardware bugs in imperfect MIPS implementations, e.g. Loongson 2 They are listed in https://db.debian.org/machines.cgi?host=mipsel-osuosl-01 https://db.debian.org/machines.cgi?host=mipsel-osuosl-02 https://db.debian.org/machines.cgi?host=mipsel-osuosl-03 https://db.debian.org/machines.cgi?host=mipsel-osuosl-04 https://db.debian.org/machines.cgi?host=mipsel-osuosl-05 So where it failed it was a Quad Core Loongson 3A3000. It suceeded on mipsel-osuosl-01 which is different. Maybe we can treat that not as RC, but I wanted to be on safe side. Regards, Salvatore
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 1025326 22.3.0-1
Bug #1025326 {Done: Joachim Falk } [libgl1-mesa-dri]
tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Marked as found in versions mesa/22.3.0-1 and reopened.
> fixed 1025326 22.3.0-2
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of
libgl1-mesa-dri to 22.3.0 breaks Xvnc
Marked as fixed in versions mesa/22.3.0-2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1025326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 1025326 libgl1-mesa-dri
Bug #1025326 {Done: Joachim Falk } [mesa]
tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Bug reassigned from package 'mesa' to 'libgl1-mesa-dri'.
No longer marked as found in versions 22.3.0-1.
No longer marked as fixed in versions 22.3.0-2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1025326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026289: surf: The app opens, only displays a blank page
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
Processed (with 1 error): your mail
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
Bug#1005272: libxt6: out-of-date copyright file -
Package: libxt6 Followup-For: Bug #1005272 X-Debbugs-Cc: mechti...@debian.org I tried to fix this RC bug. but I can't do it in my build environment. It isn't buildable with gbp buildpackage. I miss pristine-tar and upstream branch. Regards Mechtilde -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libxt6 depends on: ii libc6 2.36-6 ii libice6 2:1.0.10-1 ii libsm62:1.2.3-1 ii libx11-6 2:1.8.1-2 libxt6 recommends no packages. libxt6 suggests no packages. -- no debconf information
Bug#1026286: Unsatisfiable versioned dependency on python3-numpy
Package: python3-numba Version: 0.56.2+dfsg-2 Severity: serious Hello, thank you for maintaining python3-numba! Unfortunately the package is currently uninstallable in sid. It depends on `python3-numpy (<< 1:1.22), python3-numpy (>= 1:1.20.0)`, but the version of python3-numpy in sid is 1:1.23.5-2. Thanks, Enrico -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1025869: marked as pending in tigervnc
Control: tag -1 pending Hello, Bug #1025869 in tigervnc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-remote-team/tigervnc/-/commit/b0e4724c81f7dc9198c4685839ff38b35e5a1543 Fixed some undef warnings and a tempdir cleanup error (closes: #1025869) (this message was generated automatically) -- Greetings https://bugs.debian.org/1025869
Processed: Bug#1025869 marked as pending in tigervnc
Processing control commands: > tag -1 pending Bug #1025869 [tigervnc-scraping-server] tigervnc-scraping-server: Under bookworm server fails to start. Gives error in Wrapper.pm Added tag(s) pending. -- 1025869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026285: src:ruby-nokogiri: fails to migrate to testing for too long: FTBFS on some arch
Source: ruby-nokogiri Version: 1.13.7+dfsg-2 Severity: serious Control: close -1 1.13.8+dfsg-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:ruby-nokogiri has been trying to migrate for 62 days [2]. Hence, I am filing this bug. Your package was reported to FTBFS on s390x (still building), but the upload of today FTBFS on ppc64el already. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=ruby-nokogiri OpenPGP_signature Description: OpenPGP digital signature
Processed: src:ruby-nokogiri: fails to migrate to testing for too long: FTBFS on some arch
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
Processed: src:mutter: fails to migrate to testing for too long: autopkgtest regression and FTBFS on armhf
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#1026279: src:mutter: fails to migrate to testing for too long: autopkgtest regression and FTBFS on armhf
Source: mutter Version: 43.0-2 Severity: serious Control: close -1 43.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1024438 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:mutter has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on armhf (testsuite issue), where it built successfully in the past. The autopkgtest also regressed, which I reported in bug 1024438. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=mutter OpenPGP_signature Description: OpenPGP digital signature
Processed: found 1013526 in 0.12-1
Processing commands for cont...@bugs.debian.org: > found 1013526 0.12-1 Bug #1013526 [src:libtickit-widget-scrollbox-perl] libtickit-widget-scrollbox-perl: intermittent memory corruption in t/02input-key.t and t/03input-mouse.t The source 'libtickit-widget-scrollbox-perl' and version '0.12-1' do not appear to match any binary packages Marked as found in versions libtickit-widget-scrollbox-perl/0.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 1023688
Processing commands for cont...@bugs.debian.org:
> reopen 1023688
Bug #1023688 {Done: Jordi Mallach } [fcgiwrap] improper
permissions on fcgiwrap systemd socket lead to privilege escalation to www-data
under default config
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fcgiwrap/1.1.0-13.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1026256: backuppc: BackupPC destroys its configuration when you "Save" in the admin web console
Processing control commands: > clone -1 -2 Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Bug 1026256 cloned as bug 1026270 > severity -1 grave Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Severity set to 'grave' from 'important' > severity -2 wishlist Bug #1026270 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Severity set to 'wishlist' from 'important' > reassign -2 perl Bug #1026270 [backuppc] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Bug reassigned from package 'backuppc' to 'perl'. No longer marked as found in versions backuppc/4.4.0-6. Ignoring request to alter fixed versions of bug #1026270 to the same values previously set > retitle -2 perl: Please add a versioned Conflicts with backuppc Bug #1026270 [perl] backuppc: BackupPC destroys its configuration when you "Save" in the admin web console Changed Bug title to 'perl: Please add a versioned Conflicts with backuppc' from 'backuppc: BackupPC destroys its configuration when you "Save" in the admin web console'. -- 1026256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026256 1026270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026257: marked as done (FTBFS: more network tests in node-zx)
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
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
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#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
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
Bug#1018030: marked as done (Removal notice: obsolete)
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#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
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) >
Bug#959557: marked as done (ruby-omniauth-remote-user: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `strip' for nil:NilClass)
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#1022918: marked as done (Removal notice: obsolete)
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#1022920: marked as done (Removal notice: obsolete)
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)
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=amd64=0.3.5.5-5%2Bb4=1658619154=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 :: * -> *).
Bug#1017253: marked as done (haskell-uri: FTBFS: hlibrary.setup: Encountered missing or private dependencies: parsec >=3.0 && <=3.1.11)
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=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=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 just been removed from the Debian archive
unstable we hereby close the associated bug reports.
Bug#1014001: marked as done (haskell-text-format FTBFS: hlibrary.setup: Encountered missing or private dependencies: base >=4.3 && <4.15)
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=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#1022913: marked as done (Removal notice: obsolete)
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)
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’)
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=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#1022194: marked as done (Removal notice: obsolete)
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#1022195: marked as done (Removal notice: obsolete)
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#1022191: marked as done (Removal notice: obsolete)
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#1022906: marked as done (Removal notice: obsolete)
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)
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)
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=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)
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=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#1022905: marked as done (Removal notice: obsolete)
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)
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=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#1022901: marked as done (Removal notice: obsolete)
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)
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)
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#1020782: marked as done (Removal notice: obsolete)
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#1020252: marked as done (libghc-hashmap-doc: Depends: haddock-interface-35 but it is not installable)
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#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
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
Bug#1018051: marked as done (Removal notice: obsolete)
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)
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=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)
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=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)
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))
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: >
Bug#1026258: FTBFS: missing build dependency and failing tests
Source: ormar
Version: 0.12.0-1
Severity: serious
Tag: ftbfs
Dear Maintainer,
ormar currently fails to build from source for two reasons. The first is
several error message like these when running the test suite:
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_fastapi/test_skip_reverse_models.py:8: in
from starlette.testclient import TestClient
/usr/lib/python3/dist-packages/starlette/testclient.py:16: in
import httpx
E ModuleNotFoundError: No module named 'httpx'
_ ERROR collecting tests/test_fastapi/test_wekref_exclusion.py
_
(Taken from the build log when the package got synced to Ubuntu, but
I've also reproduced this on Sid
https://launchpadlibrarian.net/638906557/buildlog_ubuntu-lunar-amd64.ormar_0.12.0-1_BUILDING.txt.gz)
These errors are the easy part, it simply needs
python3-httpx
added as a build dependency. With this in place, the build result
changes from 19 errors to 2 failing tests. I don't know why they are
failing though, whether it is due to api changes in the test client
used, or the functionality of the package.
=== FAILURES
===
__ test_all_endpoints
__
def test_all_endpoints():
client = TestClient(app)
with client as client:
item = {
"name": "test",
"categories": [{"name": "test cat"}, {"name": "test
cat2"}],
}
response = client.post("/items/", json=item)
item_check = Item(**response.json())
assert item_check.id is not None
assert item_check.categories[0].id is not None
no_pk_item = client.get(f"/items/{item_check.id}",
json=item).json()
E TypeError: TestClient.get() got an unexpected keyword
argument 'json'
tests/test_fastapi/test_excluding_fields.py:118: TypeError
__ test_all_endpoints
__
def test_all_endpoints():
client = TestClient(app)
with client as client:
response = client.post("/categories/", json={"name": "test
cat"})
category = response.json()
response = client.post(
"/items/", json={"name": "test", "id": 1, "category":
category}
)
item = Item(**response.json())
assert item.pk is not None
response = client.get("/items/")
items = [Item(**item) for item in response.json()]
assert items[0] == item
item.name = "New name"
response = client.put(f"/items/{item.pk}", json=item.dict())
assert response.json() == item.dict()
response = client.get("/items/")
items = [Item(**item) for item in response.json()]
assert items[0].name == "New name"
response = client.get("/items/raw/")
items = [Item(**item) for item in response.json()]
assert items[0].name == "New name"
assert items[0].category.name is None
response = client.get(f"/items/{item.pk}")
new_item = Item(**response.json())
assert new_item == item
response = client.delete(f"/items/{item.pk}")
assert response.json().get("deleted_rows", "__UNDEFINED__")
!= "__UNDEFINED__"
response = client.get("/items/")
items = response.json()
assert len(items) == 0
client.post("/items/", json={"name": "test_2", "id": 2,
"category": category})
response = client.get("/items/")
items = response.json()
assert len(items) == 1
item = Item(**items[0])
response = client.delete(f"/items/{item.pk}",
json=item.dict())
E TypeError: TestClient.delete() got an unexpected keyword
argument 'json'
tests/test_fastapi/test_more_reallife_fastapi.py:150: TypeError
-- 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.org
Processed: Re: Bug#1025744: greetd - FTBFS with new version of rust-nix.
Processing control commands: > severity -1 serious Bug #1025744 [greetd] greetd - FTBFS with new version of rust-nix. Severity set to 'serious' from 'important' -- 1025744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026257: FTBFS: more network tests in node-zx
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')
+
Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:
On 13 Sep 2022 09:00:07 -0300 Antonio Terceiro wrote: > Source: ruby-safe-yaml > Version: 1.0.5-2 > Justification: FTBFS > Usertags: ruby3.1 > > We are about to start the ruby3.1 transition in unstable. While trying to > rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed. > > Relevant part of the build log (hopefully): > > ArgumentError: > > wrong number of arguments (given 2, expected 1) > > # ./lib/safe_yaml/load.rb:149:in `load' > > # ./lib/safe_yaml.rb:29:in `safe_load' > > # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip' > > # ./spec/safe_yaml_spec.rb:745:in `block (4 levels) in > (required)>' > > > > Finished in 0.08109 seconds (files took 0.12613 seconds to load) > > 134 examples, 20 failures > > > > Failed examples: > > > > rspec ./spec/safe_yaml_spec.rb:29 # Psych unsafe_load allows exploits > > through objects defined in YAML w/ !ruby/hash via custom :[]= methods There is an upstream PR: https://github.com/dtao/safe_yaml/pull/101 which tried to address this, but someone who tried it still got errors. Last upstream commit was from 2019-02-22 and there are several PRs open and it looks like the maintainer hasn't responded to any of them for > 5 YEARS signature.asc Description: This is a digitally signed message part.
Processed: reassign 1023911 to swig, forcibly merging 1024555 1023911, affects 1023911
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
Bug#1026255: FTBFS: error: invalid flag: -html4
Source: junit5-system-exit
Version: 1.1.2-3
Severity: serious
Tags: ftbfs patch
Dear Maintainer,
junit5-system-exit currently fails to build from source with the
following error message:
Starting process 'command
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''. Working directory:
/build/1st/junit5-system-exit-1.1.2 Command:
/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc
@/build/1st/junit5-system-exit-1.1.2/build/tmp/javadoc/javadoc.options
Successfully started process 'command
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''
error: invalid flag: -html4
1 error
(for details see
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/junit5-system-exit.html)
I was able to reproduce this on my Sid system, and the package built
successfully when replacing the flag, see the attached patch.
Based on the output from javadoc, this option now seems to be the
default
-html5Generate HTML 5 output. This option is no longer
required.
so alternatively the javadoc section can be trimmed down. Another thing
is that I haven't checked when the html5 option was introduced or when
it replaced html4. It builds successfully with the current JDK, but it
might introduced problems when backporting the package in the future. I
don't know if this is a concern.
Regardless, the attached patch should fix the build issue or serve as
the base for a better fix :)
-- 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.orgDescription: Replace html4 option with html5
The html4 option has been removed/replaced in newer JDKs, causing a build
failure.
---
Forwarded: no
--- junit5-system-exit-1.1.2.orig/build.gradle
+++ junit5-system-exit-1.1.2/build.gradle
@@ -74,6 +74,6 @@ publishing {
javadoc {
if(JavaVersion.current().isJava9Compatible()) {
-options.addBooleanOption('html4', true)
+options.addBooleanOption('html5', true)
}
}
Bug#1026155: marked as done (python3-trio: MultiError implementation conflicts with BaseExceptionGroup backport in Python 3.10)
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
Processed: RC bug #1013381 was fixed upstream. Forwarded to upstream PR
Processing commands for cont...@bugs.debian.org: > forwarded 1013381 https://github.com/buildbot/buildbot/pull/6616 Bug #1013381 [src:buildbot] buildbot: FTBFS with Sphinx 5.0, docutils 0.18: make[2]: *** [Makefile:67: singlehtml] Error 2 Set Bug forwarded-to-address to 'https://github.com/buildbot/buildbot/pull/6616'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1024555
Processing commands for cont...@bugs.debian.org:
> affects 1024555 src:xdmf
Bug #1024555 {Done: Jochen Sprickerhof } [swig] xdmf FTBFS
with SWIG 4.1.0
Added indication that 1024555 affects src:xdmf
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026155: python-trio: diff for NMU version 0.22.0-0.1
On Sat, Dec 17, 2022 at 07:28:24AM +0100, Jochen Sprickerhof wrote: > I've prepared an NMU for python-trio (versioned as 0.22.0-0.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Thank you for working on this! Assuming it builds and passes tests OK, +1 for immediate upload if you wish. signature.asc Description: PGP signature
Bug#1024555: marked as done (xdmf FTBFS with SWIG 4.1.0)
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=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(), , ,
);
| ^
| |
| 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 ){
|
^~
/<>/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(), , ,
);
| ^
| |
| 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(slice,
Bug#1024304: marked as done (rust-cargo-outdated - build-depends on obsolete version of rust-cargo.)
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 | _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
Files:
Bug#1025840: marked as done (deepin-log-viewer: build-depends on dropped virtual package)
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#1017835: elpa-evil: emacs 28.1 upgrade fails with byte compiling elpa-evil
On Sun, Aug 21, 2022 at 12:29:21PM +0200, Gregory Mounie wrote: > Upgrading to emacs-gtk 28.1 fails with byte co[m]piling elpa-evil* [...] > In toplevel form: > evil.el:133:1: Error: Wrong number of arguments: (3 . 4), 2 > ERROR: install script from elpa-evil package failed Confirmed, I'm seeing this as well and it's breaking the overall installation of emacs-28 (if you've elpa-evil installed). As a workaround, the following works: remove the "elpa-evil" Debian package, install the same package via "M-x package-install" and then "evil". That will give you evil version 1.15.0, which is compatible with Emacs 28. (But also get you out of the comfort zone of Debian packages, you've been warned!) Hope this helps, Cheers
Processed: Re: Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available
Processing control commands: > reassign -1 src:mesa 22.2.4-1 Bug #1025213 [gnome-shell] gnome-shell: Flickering and mangled screens on wayland if dri driver not available Bug reassigned from package 'gnome-shell' to 'src:mesa'. No longer marked as found in versions gnome-shell/43.1-2. Ignoring request to alter fixed versions of bug #1025213 to the same values previously set Bug #1025213 [src:mesa] gnome-shell: Flickering and mangled screens on wayland if dri driver not available Marked as found in versions mesa/22.2.4-1. > severity -1 normal Bug #1025213 [src:mesa] gnome-shell: Flickering and mangled screens on wayland if dri driver not available Severity set to 'normal' from 'serious' -- 1025213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available
Control: reassign -1 src:mesa 22.2.4-1 Control: severity -1 normal >From what you've said about the various different drivers in use in different modes, this looks like a Mesa issue more than a gnome-shell issue, so I'm reassigning this. It also seems to be hardware-specific and has a straightforward workaround (using gnome-shell in Xorg mode), so I'm setting the severity accordingly (Mesa maintainers: this is a guess, please increase or decrease as you wish). This is certainly not a Debian Policy section 3.8 violation, because Policy §3.8 refers to a specific technical feature, the "Essential: yes" field, and gnome-shell is not an "Essential: yes" package. On Thu, 01 Dec 2022 at 15:46:07 +0100, Gert van de Kraats wrote: > my 32-bit Dell-laptop There are many 32-bit Dell laptops in the world. Which model is this and which CPU and GPU does it have? Please try running reportbug --template libgl1-mesa-dri and send the result to the bug address 1025...@bugs.debian.org so that the Mesa maintainers have the necessary context. smcv
Bug#1025213: DRM platform with kms_swrast
On Fri, 16 Dec 2022 at 22:40:28 +0100, Gert van de Kraats wrote: > If the i915 dri driver is present gnome-shell is using the DRM platform > (not the Wayland platform?) with this driver. This is expected. gnome-shell acts as the Wayland compositor (the X11 equivalent would be Xorg, window manager and compositing manager all in one process), so it can't use Wayland itself, for the same reasons that Xorg can't output via X11. It has to use something lower-level to talk directly to the kernel, and the DRM platform is exactly that lower-level thing. Ordinary applications running under GNOME (when it's in Wayland mode) will use the Wayland platform as you'd expect, it's only gnome-shell itself that can't. Similarly, if there is no suitable hardware-specific DRI driver available for your hardware, it's normal and expected that gnome-shell will use the DRM platform with some sort of software-rendering driver. smcv
Bug#1022149: Link to upstream bug
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460701
Processed: Link to upstream bug
Processing control commands: > forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460701 Bug #1022149 [ktimetracker] ktimetracker total data loss Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=460701'. -- 1022149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
