Bug#1069391: marked as pending in nmap
Control: tag -1 pending Hello, Bug #1069391 in nmap 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/pkg-security-team/nmap/-/commit/06ff1ac3296fd639ae1e9840b2c78b48dfd45196 debian/rules: filter out build flag not supported by i686-w64-mingw32-gcc We are using the native build flags against the Windows cross compiler, there is no guarantee that that compiler will support the same flags as the native, official Debian gcc. Ideally That should be changed to a hardcoded known-good list of options support by i686-w64-mingw32-gcc. Closes: #1069391 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069391
Bug#1069348: closing 1069348
close 1069348 0.16.0-2 thanks
Bug#1068537: marked as pending in ruby-ethon
Control: tag -1 pending Hello, Bug #1068537 in ruby-ethon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-ethon/-/commit/c66b1a1db60d982a2648f44977ed104a42d93293 Don't hardcode a dependency on libcurl4 Closes: #1068537 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068537
Bug#1066854: marked as pending in ruby-magic
Control: tag -1 pending Hello, Bug #1066854 in ruby-magic reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-magic/-/commit/3a95d42fa6ea9355487927f2c663a73bbad603ea Use libmagic-dev in Build-Depends/Depends instead of libmagic1 Closes: #1066854 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066854
Bug#1068589: marked as pending in gem2deb
Control: tag -1 pending Hello, Bug #1068589 in gem2deb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/gem2deb/-/commit/31ab3f4026d0365e9300a521d2a75931626d209b dh_ruby_fixdepends: workaround presence of libruby3.1t64 Closes: #1068589 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068589
Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2
On Tue, Mar 12, 2024 at 09:13:09PM +0100, Sebastian Andrzej Siewior wrote: > tried with 1.50+nmu2 which is in deferred for the next 11h. So tomorrow > it should be all good. Please make sure to commit the patch to the pristine-tar git repository as well. signature.asc Description: PGP signature
Bug#1065091: marked as pending in gtg
Control: tag -1 pending Hello, Bug #1065091 in gtg 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/python-team/packages/gtg/-/commit/89f6c4814684b99f82fbf6be1b43c2da1667da5e Revert patch switching from imp to importlib; use zombie-imp instead Closes: #1065091 (this message was generated automatically) -- Greetings https://bugs.debian.org/1065091
Bug#1065091: gtg: crashes on startup
Package: gtg Version: 0.6-6 Severity: grave Justification: renders package unusable Dear Maintainer, $ gtg 2024-02-29 14:44:05,373 - ERROR - application:do_activate:153 - Exception during activation Traceback (most recent call last): File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 148, in do_activate self.init_shared() File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 229, in init_shared self.init_plugin_engine() File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 255, in init_plugin_engine self.plugin_engine.activate_plugins() File "/usr/lib/python3/dist-packages/GTG/core/plugins/engine.py", line 199, in activate_plugins plugin.active = True ^ File "/usr/lib/python3/dist-packages/GTG/core/plugins/engine.py", line 78, in _set_active self.instance = self.plugin_class() ^ AttributeError: 'Plugin' object has no attribute 'plugin_class' 2024-02-29 14:44:06,815 - INFO - errorhandler:handle_response:163 - Going to exit because either of fatal error or user choice Aborted Downgrading to 0.6-5 from snapshots makes it work again, so some change in 0.6-6 broke it entirely. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.6.15-arm64 (SMP w/32 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.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 gtg depends on: ii gir1.2-gtk-3.0 [gir1.2-gdk-3.0] 3.24.41-1 ii gir1.2-gtksource-4 4.8.4-5+b1 ii gir1.2-pango-1.0 1.51.0+ds-4 ii gir1.2-secret-1 0.21.2-1 ii pdftk-java 3.3.3-2 ii python3 3.11.6-1 ii python3-caldav 0.11.0-2 ii python3-cheetah 3.3.3-1 ii python3-gi 3.47.0-3 ii python3-gi-cairo 3.47.0-3 ii python3-liblarch 3.2.0-3 ii python3-lxml 5.1.0-1 ii texlive-extra-utils 2023.20240207-1 ii texlive-latex-base 2023.20240207-1 gtg recommends no packages. gtg suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1058111: marked as pending in cmdtest
Control: tag -1 pending Hello, Bug #1058111 in cmdtest 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/python-team/packages/cmdtest/-/commit/dcf5b1bda3cb1ae41b23c23324f88023a993379f Pull `imp` from python3-zombie-imp Closes: #1058111 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058111
Bug#1058937: /usr-move: Do we support upgrades without apt?
On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > ## Upgrading using dpkg directly? > > We already have quite a number of packages that use Conflicts to prevent > file loss in upgrades in a very similar way to #1058937 (Ben's > libnfsidmap1 bug) even in released versions of Debian. For instance, > dhcpcd-base's Replaces were upgraded to Conflicts, see #1053657. If you > employ dpkg, you can still experience the problem there. > > Is it ok to call upgrade scenarios failures that cannot be reproduced > using apt unsupported until we no longer deal with aliasing? I think so, yes. I don't think it's likely that there are people doing upgrades on running systems not using apt. If there are, they already need to deal with doing the dpkg calls in the right order anyway -- basically doing the apt dependency resolution by hand -- that this is just another corner case that they need to handle; there could be already Conflicts in there for other reasons than /usr-merge. signature.asc Description: PGP signature
Bug#1054727: rails: FTBFS: build-dependency not installable: ruby-thin (>= 1.6.0)
Control: forcemerge 1054256 -1 Control affects 1054256 + src:rails On Fri, Oct 27, 2023 at 09:27:35PM +0200, Lucas Nussbaum wrote: > Source: rails > Version: 2:6.1.7.3+dfsg-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > 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 > > - [...] > > 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: > > ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. This is caused by an issue with ruby-blade (already reported) signature.asc Description: PGP signature
Bug#1054256: ruby-blade: uninstallable in unstable (ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable)
Package: ruby-blade Version: 0.7.1-4 Severity: serious Justification: uninstallable After the last upload, ruby-blade ended up with a dependency on ruby-thin, which does not exist. 8<8<8<- $ LANG=C sudo apt install ruby-blade/unstable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '0.7.1-4' (Debian:unstable [all]) for 'ruby-blade' 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: ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable E: Unable to correct problems, you have held broken packages. 8<8<8<- The correct dependency would be on `thin`. This is actually caused by a bug in gem2deb (unreported), which was not finding the correct mapping between gem names and Debian package names for architecture dependent packages. In any case, ruby-blade will need a no changes upload to be rebuilt once gem2deb 2.2, just uploaded, is available. See https://salsa.debian.org/ruby-team/gem2deb/-/commit/827cb954c941872e24bb8f489d1a54cba416694b for more details. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.5.0-1-arm64 (SMP w/32 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 ruby-blade depends on: ii ruby 1:3.1 ii ruby-activesupport2:6.1.7.3+dfsg-2 ii ruby-blade-qunit-adapter 2.0.1-2 ii ruby-curses 1.4.4-1+b2 ii ruby-eventmachine 1.3~pre20220315-df4ab006-3+b1 ii ruby-faye 1.4.0-1 ii ruby-sprockets3.7.2-4 pn ruby-thin ii ruby-thor 1.2.2-1 ii ruby-useragent0.16.8-1.1 ii thin 1.8.1-2 ruby-blade recommends no packages. ruby-blade suggests no packages. signature.asc Description: PGP signature
Bug#1051900: ohcount: aborts with segfaul or bus error 90% of the time on arm64
Package: ohcount Version: 4.0.0-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, ohcount segfaults (and sometimes aborts with a Bus error) on arm64, almost 90% of the time. I tried this on an up to date arm64 Debian testing against the hexchat source code, but it's also reproducible on the ohcount source code itself. The same test, when performced on an up to date amd64 Debian testing, finishes successfully 100% of the time. For example this is a sample session with 10 runs against the source of ohcount itself: $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.4.0-3-arm64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 ohcount depends on: ii file 1:5.45-2 ii libc6 2.37-7 ii libmagic1 1:5.45-2 ii libpcre3 2:8.39-15 ii ruby 1:3.1 ii ruby-diff-lcs 1.5.0-1 ohcount recommends no packages. Versions of packages ohcount suggests: pn ohcount-doc -- no debconf information signature.asc Description: PGP signature
Bug#1050462: gtg: crashes on startup often
On Fri, Aug 25, 2023 at 08:52:49PM +0200, François Mazen wrote: > Dear Antonio, > > thanks for the crash report! I can reproduce it easily with unstable > distribution and the call stack points to pango_font_description_to_string > method. > > The issues seems to have been already reported upstream [1] and the suggested > worj around is to add "font_name = Sans 11" in the [browser] section of the > ~/.config/gtg/gtg.conf config file. Thanks, this indeed seem to work around the issue. > I've checked the fix and no more crash occurs, so it could be integrated as a > quilt patch for the Debian package. We probably want to fix the code to *not* segfault when the workaround is not in place. I'm not sure whether this is a bug in gtg itself, or in pango. signature.asc Description: PGP signature
Bug#1050462: gtg: crashes on startup often
Package: gtg
Version: 0.6-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gtg crashes on startup very often.
~$ gtg
2023-08-24 14:38:12,928 - WARNING - adaptive_button:do_forall:279 - Got error
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget'
object has no attribute '_children'")
~$ gtg
2023-08-24 14:38:17,288 - WARNING - adaptive_button:do_forall:279 - Got error
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget'
object has no attribute '_children'")
~$ gtg
Segmentation fault
~[139]$ gtg
2023-08-24 14:38:25,240 - WARNING - adaptive_button:do_forall:279 - Got error
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget'
object has no attribute '_children'")
~$ gtg
Segmentation fault
~[139]$ gtg
Segmentation fault
~[139]$ gtg
2023-08-24 14:38:40,377 - WARNING - adaptive_button:do_forall:279 - Got error
in for but it should've stay valid: AttributeError("'AdaptiveFittingWidget'
object has no attribute '_children'")
I can reproduce this issue:
- on both arm64 and amd64 systems, running testing;
- with or without wiping out ~/.local/share/gtg/ before each attempt at
starting it.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Kernel: Linux 6.5.0-0-arm64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 gtg depends on:
ii gir1.2-gtk-3.0 [gir1.2-gdk-3.0] 3.24.38-2
ii gir1.2-gtksource-4 4.8.4-4
ii gir1.2-pango-1.0 1.51.0+ds-2
ii gir1.2-secret-1 0.21.0-1
ii pdftk-java 3.3.3-1
ii python3 3.11.4-5+b1
ii python3-caldav 0.11.0-1
ii python3-cheetah 3.3.2-1
ii python3-gi 3.44.1-2
ii python3-gi-cairo 3.44.1-2
ii python3-liblarch 3.2.0-3
ii python3-lxml 4.9.3-1
ii texlive-extra-utils 2022.20230122-4
ii texlive-latex-base 2022.20230122-3
gtg recommends no packages.
gtg suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
Bug#1038139: debci-worker: Process leaks authentication data via amqp-tools
On Thu, Jun 15, 2023 at 10:48:57PM +0200, Christian Kastner wrote: > > Package: debci > Version: 3.6 > Severity: serious > Tags: security > X-Debbugs-Cc: Debian Security Team > > Hi, > > When using authentication in AMQP connections, the username and password > supplied in the --url option to amqp-consume resp. amqp-publish are > exposed in the proces list, see #1037322: > > $ pgrep -a ampq-consume > 62287 amqp-consume --url amqp://user:pass@192.168.0.1 --queue=myqueue > > A patch has been accepted upstream to read the username and password > from a file. I assume this will make its way into ampq-tools soon. > > Unless I'm mistaken, debci will need to be updated for this, e.g. by > adding a debci_amqp_pwfile config option + NEWS entry suggesting that > people migrate to this new option. I'd be happy to file an MR for this, > once ampq-tools has been fixed. Note that the variable where you inserted a username and password is calle debci_amqp_server, and was never supposed to be used for putting a password in plain text. For the c.d.n deployment we use SSL client certificates for authentication, and that's why the variables debci_amqp_cacert, debci_amqp_cert, debci_amqp_key are there. IMO that is no different from any other program that takes a url as a command line parameter: you can pass a URL containing a username and password, but then that's on you. signature.asc Description: PGP signature
Bug#1035568: dnsmasq is broken on new bookworm installations
Control: severity -1 normal On Fri, 05 May 2023 15:17:37 + =?utf-8?q?Jens_Mei=C3=9Fner?= wrote: > Package: dnsmasq > Version: 2.89-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: heptal...@gmx.de > > Hello, > > dnsmasq on bookworm fails to start after installation because the dns port 53 > is already is use by systemd-resolved. > After stopping systemd-resolved dnsmasq will start but refuses all dns > queries with the Extended DNS Error Code 14 "Not Ready". > This error is reproducible on new installation. > > Setting severity to grave because it affects clean installs. This is a bug that needs fixing, for sure. But systemd-resolved is installed by default only on the cloud images, and not on all Debian installs. Therefore this does not really affect all users, and grave severity does not apply. Enabling (uncommenting) the `bind-interfaces` in /etc/dnsmasq.conf fixes the issue on my tests, and maybe that should be set by default. signature.asc Description: PGP signature
Bug#1017218: marked as pending in ruby-parallel
Control: tag -1 pending Hello, Bug #1017218 in ruby-parallel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-parallel/-/commit/2e9dc6867d9541a89b4f10cd7c71edcb36f51cf1 Disable running upstream test suite Closes: #905648, #1019646, #1017218 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017218
Bug#1031238: marked as pending in debci
Control: tag -1 pending Hello, Bug #1031238 in debci 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/ci-team/debci/-/commit/917430ee7492279993eef2fa5599944866ce6793 debci generate-apt-sources: add support for non-free-firmware Closes: #1031238 (this message was generated automatically) -- Greetings https://bugs.debian.org/1031238
Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases
Control: severity -1 normal Failing on some inputs is not a justification for a `serious` severity. Thus, I am downgrading this bug to normal. signature.asc Description: PGP signature
Bug#1025125: closing 1025125
close 1025125 thanks
Bug#1004068: marked as pending in origami-pdf
Control: tag -1 pending Hello, Bug #1004068 in origami-pdf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/origami-pdf/-/commit/265003d4bfe95c77983856f6481104db872ca733 Add patch from an upstream fork with fix for Ruby 3+ Closes: #1004068 (this message was generated automatically) -- Greetings https://bugs.debian.org/1004068
Bug#1028871: marked as pending in djangorestframework
Control: tag -1 pending Hello, Bug #1028871 in djangorestframework 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/python-team/packages/djangorestframework/-/commit/fd193d9b87d1220836426e15510ea1bcf3085707 Add patch to fix tests against the environment on bookworm Closes: #1028871 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028871
Bug#1026499: rows: diff for NMU version 0.4.1-5.1
On Wed, Jan 18, 2023 at 06:27:59PM +0200, Adrian Bunk wrote: > Control: tags 1026499 + patch > Control: tags 1026499 + pending > > Dear maintainer, > > I've prepared an NMU for rows (versioned as 0.4.1-5.1) and uploaded > it to DELAYED/14. Please feel free to tell me if I should cancel it. I'm about to upload a new upstream snapshot that will close this bug, so I think you can cancel it. Thanks for looking into the package, though. signature.asc Description: PGP signature
Bug#1028890: marked as pending in ruby
Control: tag -1 pending Hello, Bug #1028890 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby/-/commit/ff807c1310d34221957c9c29713cfe7360eab19b Apply upstream patch to fix TZ tests Closes: #1028890 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028890
Bug#1026779: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1026779: fixed in binutils 2.39.50.20221224-1)
Control: reopen -1
On Sat, Dec 24, 2022 at 02:45:07PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:binutils package:
>
> #1026779: binutils: cross binutils and foreign libbinutils not coinstallable,
> breaking upgrades
>
> It has been closed by Debian FTP Masters
> (reply to Matthias Klose ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters
> (reply to Matthias Klose )
> by
> replying to this email.
>
>
> --
> 1026779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026779
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> Date: Sat, 24 Dec 2022 14:40:11 +
> From: Debian FTP Masters
> To: 1026779-cl...@bugs.debian.org
> Subject: Bug#1026779: fixed in binutils 2.39.50.20221224-1
> Reply-To: Matthias Klose
> Message-Id:
>
> Date: Tue, 20 Dec 2022 21:04:46 -0300
> From: Antonio Terceiro
> To: Debian Bug Tracking System
> Subject: binutils: cross binutils and foreign libbinutils not
> coinstallable, breaking upgrades
> Message-ID:
>
> Source: binutils
> Version: 2.39.50.20221208-5
> Severity: serious
>
> Dear Maintainer,
>
> Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
> libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
> where both are installed (e.g. binutils-aarch64-linux-gnu and
> libbinutils:arm64) fails like this:
>
> 8<8<8<-
> Unpacking libbinutils:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack
> .../3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb ...
> Unpacking binutils-aarch64-linux-gnu (2.39.50.20221208-5) over (2.39-8) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
> (--unpack):
> trying to overwrite '/usr/lib/aarch64-linux-gnu/libsframe.so.0.0.0', which
> is also in package libbinutils:arm64 2.39.50.20221208-5
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Preparing to unpack .../4-binutils-common_2.39.50.20221208-5_amd64.deb ...
> De-configuring binutils-common:arm64 (2.39-8), to allow configuration of
> binutils-common:amd64 (2.39.50.20221208-5) ...
> Unpacking binutils-common:amd64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack .../5-binutils-common_2.39.50.20221208-5_arm64.deb ...
> Unpacking binutils-common:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Selecting previously unselected package libbinutils:amd64.
> Preparing to unpack .../6-libbinutils_2.39.50.20221208-5_amd64.deb ...
> Unpacking libbinutils:amd64 (2.39.50.20221208-5) ...
> Selecting previously unselected package libjansson4:amd64.
> Preparing to unpack .../7-libjansson4_2.14-2_amd64.deb ...
> Unpacking libjansson4:amd64 (2.14-2) ...
> Errors were encountered while processing:
>
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 8<8<8<-
i386 is still affected by this on 2.39.50.20221224-1 (testing):
Unpacking binutils-i686-linux-gnu (2.39.50.20221224-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is
also in package libbinutils:i386 2.39.50.20221224-1
Errors were encountered while processing:
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
and also on 2.39.90.20221231-1 (unstable)
Unpacking binutils-i686-linux-gnu (2.39.90.20221231-1) ...
dpkg: error processing archive
/var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is
also in package libbinutils:i386 2.39.90.20221231-1
Errors were encountered while processing:
/var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
signature.asc
Description: PGP signature
Bug#1027342: itamae: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'net-telnet' (= 0.1.1)
Control: reassign -1 src:ruby-specinfra Control: forcemerge #1027347 -1 Control: affects #1027347 src:itamae On Fri, Dec 30, 2022 at 05:20:58PM +0100, Lucas Nussbaum wrote: > Source: itamae > Version: 1.14.1-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221230 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. This is caused by ruby-specinfra. signature.asc Description: PGP signature
Bug#1027449: marked as pending in ruby-dbm
Control: tag -1 pending Hello, Bug #1027449 in ruby-dbm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-dbm/-/commit/10bf8229a52d3f53ed90004bc3c9f27e7141f80a debian/copyright: drop notes about licensing of resulting binaries Closes: #1027449 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027449
Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp
Control: tag -1 + pending On Fri, Dec 30, 2022 at 08:08:50PM -0300, Antonio Terceiro wrote: > Control: reassign -1 dhelp > Control: severity -1 serious > Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm) > > On Fri, Dec 30, 2022 at 06:09:03PM +0100, Drew Parsons wrote: > > Package: ruby-rubygems > > Version: 3.3.15-1 > > Severity: important > > > > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb from > > ruby-rubygems causes a LoadError which prevents dhelp from updating > > succcessfully (when packages register a doc-base entry). > > > > This affects all other packages (unrelated to ruby) registering with > > doc-base, hence marking Severity: important > > > > The error message (when installing any packing using doc-base, in this > > case python-lmfit-doc) is > > > > Setting up python-lmfit-doc (1.1.0-1) ... > > Processing triggers for doc-base (0.11.1) ... > > Processing 1 added doc-base file... > > Registering documents with dhelp... > > :85:in > > `require': cannot load such file -- dbm (LoadError) > > from > > :85:in > > `require' > > from /usr/lib/ruby/vendor_ruby/dhelp.rb:21:in `' > > from > > :85:in > > `require' > > from > > :85:in > > `require' > > from /usr/sbin/dhelp_parse:32:in `' > > The issue is that dhelp depends on a module that has been removed from > the Ruby standard library (dbm). I imagine the dhelp database is just a > cache and can be rebuilt from scratch on upgrades, so one way to fix > this would be to migrate to a similar module that is available and > probably has a similar enough API, like sdbm (ruby-sdbm). Actually this would invalidate existing databases, creating extra complications. I have just uploaded a ruby-dbm package to NEW, and made the necessary adjustments to the dhelp git repository to use it. I will make an upload when the new package is accepted. signature.asc Description: PGP signature
Bug#1027087: ruby-rubocop-performance: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: subject(:config) { RuboCop::ConfigLoader.load_file('config/default.yml') }
Source: ruby-rubocop-performance
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rubocop-performance failed to build. I retried with the version in
the archive, and obtained the same failure so this is not related to
ruby-rspec.
Relevant part of the build log (hopefully):
> Failure/Error: subject(:config) {
> RuboCop::ConfigLoader.load_file('config/default.yml') }
>
> RuboCop::ValidationError:
>`Performance` cops have been extracted to the `rubocop-performance`
> gem.
>(obsolete configuration found in config/default.yml, please update it)
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_obsoletion.rb:43:in
> `reject_obsolete!'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:78:in
> `check_obsoletions'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:44:in
> `validate'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:49:in
> `check'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:38:in
> `create'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_loader.rb:57:in
> `load_file'
> # ./spec/project_spec.rb:5:in `block (3 levels) in '
> # ./spec/project_spec.rb:34:in `block (4 levels) in '
> # ./spec/project_spec.rb:33:in `each'
> # ./spec/project_spec.rb:33:in `block (3 levels) in '
>
> Finished in 24.75 seconds (files took 2.65 seconds to load)
> 7975 examples, 5 failures
>
> Failed examples:
>
> rspec ./spec/project_spec.rb:40 # RuboCop Performance Project default
> configuration file sorts configuration keys alphabetically
> rspec ./spec/project_spec.rb:22 # RuboCop Performance Project default
> configuration file requires a nicely formatted `VersionAdded` metadata for
> all cops
> rspec ./spec/project_spec.rb:14 # RuboCop Performance Project default
> configuration file has a nicely formatted description for all cops
> rspec ./spec/project_spec.rb:47 # RuboCop Performance Project default
> configuration file has a SupportedStyles for all EnforcedStyle and
> EnforcedStyle is valid
> rspec ./spec/project_spec.rb:32 # RuboCop Performance Project default
> configuration file has a period at EOL of description
>
> Randomized with seed 20775
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-rubocop-performance.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
Bug#1027082: ruby-mysql2: FTBFS: ERROR: Test "ruby3.1" failed: mysqld crashes at startup
-11 libreadline8_8.2-1.2 > libregexp-ipv6-perl_0.03-3 librole-tiny-perl_2.002004-1 libruby_1:3.1 > libruby3.1_3.1.2-3 libsasl2-2_2.1.28+dfsg-10 > libsasl2-modules-db_2.1.28+dfsg-10 libseccomp2_2.5.4-1+b2 > libselinux1_3.4-1+b4 libsemanage-common_3.4-1 libsemanage2_3.4-1+b4 > libsepol2_3.4-2 libsigsegv2_2.14-1 libsmartcols1_2.38.1-4 > libsnappy1v5_1.1.9-2 libsqlite3-0_3.40.0-2 libss2_1.46.6~rc1-1+b1 > libssl-dev_3.0.7-1 libssl1.1_1.1.1o-1 libssl3_3.0.7-1 > libstdc++-11-dev_11.3.0-8 libstdc++-12-dev_12.2.0-11 libstdc++6_12.2.0-11 > libsub-override-perl_0.09-4 libsub-quote-perl_2.006006-3 libsystemd0_252.4-1 > libtasn1-6_4.19.0-2 libtext-glob-perl_0.11-3 libtimedate-perl_2.3300-2 > libtinfo6_6.3+20220423-2 libtirpc-common_1.3.3+ds-1 libtirpc-dev_1.3.3+ds-1 > libtirpc3_1.3.3+ds-1 libtool_2.4.7-5 libtry-tiny-perl_0.31-2 > libtsan0_11.3.0-8 libtsan2_12.2.0-11 libubsan1_12.2.0-11 libuchardet0_0.0.7-1 > libudev1_252.4-1 libunistring2_1.0-2 liburi-perl_5.17-1 liburing2_2.3-2 > libuuid1_2.38.1-4 libwrap0_7.6.q-31 libwww-perl_6.67-1 > libwww-robotrules-perl_6.02-1 libxml2_2.9.14+dfsg-1.1+b2 libxtables12_1.8.8-1 > libxxhash0_0.8.1-1 libyaml-0-2_0.2.5-1 libzstd1_1.5.2+dfsg-1 > linux-libc-dev_6.0.12-1 login_1:4.13+dfsg1-1 logsave_1.46.6~rc1-1+b1 > lsof_4.95.0-1 m4_1.4.19-1 make_4.3-4.1 man-db_2.11.1-1 > mariadb-client-10.6_1:10.6.11-1 mariadb-client-core-10.6_1:10.6.11-1 > mariadb-common_1:10.6.11-1 mariadb-server-10.6_1:10.6.11-1 > mariadb-server-core-10.6_1:10.6.11-1 mawk_1.3.4.20200120-3.1 > media-types_8.0.0 mount_2.38.1-4 mysql-common_5.8+1.0.8 > ncurses-base_6.3+20220423-2 ncurses-bin_6.3+20220423-2 netbase_6.4 newpid_13 > openssl_3.0.7-1 passwd_1:4.13+dfsg1-1 patch_2.7.6-7 patchutils_0.4.2-1 > perl_5.36.0-6 perl-base_5.36.0-6 perl-modules-5.32_5.32.1-6 > perl-modules-5.36_5.36.0-6 perl-openssl-defaults_7+b1 pinentry-curses_1.2.1-1 > po-debconf_1.0.21+nmu1 procps_2:4.0.2-3 psmisc_23.6-1 python3_3.10.6-3+b1 > python3-minimal_3.10.6-3+b1 python3.10_3.10.9-1 python3.10-minimal_3.10.9-1 > rake_13.0.6-3 readline-common_8.2-1.2 rpcsvc-proto_1.4.3-1 rsync_3.2.7-1 > ruby_1:3.1 ruby-all-dev_1:3.1 ruby-diff-lcs_1.5.0-1 ruby-net-telnet_0.1.1-2.1 > ruby-rspec_3.12.0c0e1m1s0-1 ruby-rspec-core_3.12.0c0e1m1s0-1 > ruby-rspec-expectations_3.12.0c0e1m1s0-1 ruby-rspec-mocks_3.12.0c0e1m1s0-1 > ruby-rspec-support_3.12.0c0e1m1s0-1 ruby-rubygems_3.3.15-1 > ruby-sdbm_1.0.0-5+b1 ruby-webrick_1.7.0-4 ruby-xmlrpc_0.3.2-2 ruby3.1_3.1.2-3 > ruby3.1-dev_3.1.2-3 rubygems-integration_1.18 > sbuild-build-depends-main-dummy_0.invalid.0 sed_4.8-1 sensible-utils_0.0.17 > socat_1.7.4.4-2 sysvinit-utils_3.06-2 tar_1.34+dfsg-1.1 tzdata_2022f-1 > usrmerge_35 util-linux_2.38.1-4 util-linux-extra_2.38.1-4 wdiff_1.2.2-4 > xz-utils_5.4.0-0.1 zlib1g_1:1.2.13.dfsg-1 zlib1g-dev_1:1.2.13.dfsg-1 > > +--+ > | Build > | > +--+ > > > Unpack source > - > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 3.0 (quilt) > Source: ruby-mysql2 > Binary: ruby-mysql2 > Architecture: any > Version: 0.5.3-4 > Maintainer: Debian Ruby Team > > Uploaders: Michael Franzl , Cédric Boutillier > , Utkarsh Gupta > Homepage: https://github.com/brianmario/mysql2 > Standards-Version: 4.6.1 > Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-mysql2 > Vcs-Git: https://salsa.debian.org/ruby-team/ruby-mysql2.git > Testsuite: autopkgtest-pkg-ruby > Build-Depends: debhelper-compat (= 13), default-libmysqlclient-dev, > default-mysql-server | virtual-mysql-server, gem2deb, rake, ruby-rspec > Package-List: > ruby-mysql2 deb ruby optional arch=any > Checksums-Sha1: > afdd1dfe2f7424d03eddd059a8b0227ef46ff607 107917 ruby-mysql2_0.5.3.orig.tar.gz > 9e3d8e99728374fdc1fd450983cb8b75b59da73f 9060 > ruby-mysql2_0.5.3-4.debian.tar.xz > Checksums-Sha256: > a11d72f79c43e5ffe9bbaa3ab6bc10ea6f777fcedfbf101c88b96e1fec950790 107917 > ruby-mysql2_0.5.3.orig.tar.gz > 7323015934799fa67eb816a048aba87de9482704780d92a81858a283d1aafd6b 9060 > ruby-mysql2_0.5.3-4.debian.tar.xz > Files: > 0c714fc0e5871836ab5e37f8135d78b7 107917 ruby-mysql2_0.5.3.orig.tar.gz > 57e1e380bad5e84890eb34417f0f876f 9060 ruby-mysql2_0.5.3-4.debian.tar.xz > Ruby-Versions: all > > -BEGIN PGP SIGNATURE- > > iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmNWgt8VHGthbmFzaGly > b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8G4gP/A8IvOg9T/29AMt08kLAb1D5A6jF > DSFNt6QFKgif6/4rHgPvUouARiDLlhacGIb16jxn8Nt2jPx06NP0ruRkjhEwVh4i > Q4jrSXcRUNGRlalvUvv3rJIPMaV4UdRt5Z/yMbznrf9VZnKl7EP7iq8eLM55D
Bug#1027080: ruby-localhost: FTBFS: tests fail randomly
Source: ruby-localhost Version: 1.1.9-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-localhost failed to build. I retried it with ruby-rspec 3.10 from the archive, and I got one successfull build, and one failure exactly like the one below. So this means the test suite fails randomly, and that is a problem. Relevant part of the build log (hopefully): > 2.2) Failure/Error: expect(status).to be_success > expected `#.success?` to be > truthy, got false > # ./spec/localhost/protocol_spec.rb:42:in `block (2 levels) in (required)>' > # > /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:93:in > `block (4 levels) in ' > # > /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:57:in > `block in run_in_reactor' > # > /usr/share/rubygems-integration/all/gems/async-1.30.3/lib/async/task.rb:261:in > `block in make_fiber' > > Finished in 2.71 seconds (files took 0.22921 seconds to load) > 10 examples, 2 failures > > Failed examples: > > rspec './spec/localhost/protocol_spec.rb[1:1:2]' # Localhost::Authority > behaves like valid protocol can connect using HTTP over TLSv1.2 > rspec './spec/localhost/protocol_spec.rb[1:2:2]' # Localhost::Authority > behaves like valid protocol can connect using HTTP over default > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is attached. 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 ruby-localhost.log.gz Description: application/gzip signature.asc Description: PGP signature
Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #
Control: reassign -1 ruby-rspec-expectations Control: retitle -1 ruby-rspec-expectations: raise_error() matcher does not work with ruby3.1 Control: forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338 Control: affects -1 src:ruby-hashie On Sat, Nov 19, 2022 at 03:29:31PM +0200, Adrian Bunk wrote: > Control: tags -1 fixed-upstream [...] > This seems to be fixed in 5.0.0. It turns out this is a problem rspec-expectations on ruby3.1. The latest upstream should fix this. signature.asc Description: PGP signature
Bug#1026897: marked as pending in ruby-tilt
Control: tag -1 pending Hello, Bug #1026897 in ruby-tilt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-tilt/-/commit/4990458cf7b824ae7bc0cb7b9562a7f27ff78017 Add patch to remove warnings with ruby-haml >= 6 Closes: #1026897 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026897
Bug#1026178: marked as pending in ruby-tzinfo
Control: tag -1 pending Hello, Bug #1026178 in ruby-tzinfo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-tzinfo/-/commit/f05c11f0a73409edf49bd1f3555198701561f232 Add dependency on tzdata Closes: #1026178 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026178
Bug#1026897: ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.
Source: ruby-tilt Version: 2.0.11-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test failure. Relevant part (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.1 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -e gem\ \"tilt\" > > ┌──┐ > │ Run tests for ruby3.1 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.1 -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/tilt_asciidoctor_test.rb" "test/tilt_blueclothtemplate_test.rb" > "test/tilt_buildertemplate_test.rb" "test/tilt_cache_test.rb" > "test/tilt_coffeescripttemplate_test.rb" > "test/tilt_commonmarkertemplate_test.rb" "test/tilt_compilesite_test.rb" > "test/tilt_creoletemplate_test.rb" "test/tilt_csv_test.rb" > "test/tilt_erbtemplate_test.rb" "test/tilt_erubistemplate_test.rb" > "test/tilt_erubitemplate_test.rb" "test/tilt_etannitemplate_test.rb" > "test/tilt_hamltemplate_test.rb" "test/tilt_kramdown_test.rb" > "test/tilt_lesstemplate_test.rb" "test/tilt_liquidtemplate_test.rb" > "test/tilt_livescripttemplate_test.rb" "test/tilt_mapping_test.rb" > "test/tilt_markaby_test.rb" "test/tilt_markdown_test.rb" > "test/tilt_marukutemplate_test.rb" "test/tilt_metadata_test.rb" > "test/tilt_nokogiritemplate_test.rb" "test/tilt_pandoctemplate_test.rb" > "test/tilt_prawntemplate_test.rb" "test/tilt_radiustemplate_test.rb" > "test/tilt_rdiscounttemplate_test.rb" "test/tilt_rdoctemplate_test.rb" > "test/tilt_redcarpettemplate_test.rb" "test/tilt_redclothtemplate_test.rb" > "test/tilt_rstpandoctemplate_test.rb" "test/tilt_sasstemplate_test.rb" > "test/tilt_sigil_test.rb" "test/tilt_stringtemplate_test.rb" > "test/tilt_template_test.rb" "test/tilt_test.rb" > "test/tilt_typescript_test.rb" "test/tilt_wikiclothtemplate_test.rb" > "test/tilt_yajltemplate_test.rb" -v > Tilt::AsciidoctorTemplate (disabled) > Tilt::BlueClothTemplate (disabled) > Tilt::BuilderTemplate (disabled) > Tilt::CoffeeScriptTemplate (disabled) > Tilt::CommonMarkerTemplate (disabled) > /<>/test/tilt_compilesite_test.rb:40: warning: assigned but > unused variable - res > /usr/share/rubygems-integration/all/gems/creole-0.5.0/lib/creole/parser.rb:255: > warning: character class has duplicated range: /\A([:alpha:]|[:digit:])+/ > Tilt::ErubiTemplate (disabled) > Tilt::KramdownTemplate (disabled) > Tilt::LessTemplate (disabled) > Tilt::LiquidTemplate (disabled) > Tilt::LiveScriptTemplate (disabled) > /<>/test/tilt_markaby_test.rb:51: warning: assigned but unused > variable - eval_scope > Tilt::MarkabyTemplate (disabled) > /<>/test/tilt_markdown_test.rb:85: warning: assigned but unused > variable - boom > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85: > warning: possibly useless use of a variable in void context > Tilt::MarukuTemplate (disabled) > Tilt::PandocTemplate (disabled) > Tilt::PrawnTemplate (disabled) > Tilt::RadiusTemplate (disabled) > Tilt::RDiscountTemplate (disabled) > Tilt::RedcarpetTemplate (disabled) > Tilt::RedClothTemplate (disabled) > Tilt::RstPandocTemplate (disabled) [cannot load such file -- pandoc] > Tilt::SassTemplate (disabled) > Tilt::SigilTemplate (disabled) > /<>/test/tilt_template_test.rb:3: warning: setting > Encoding.default_external > /<>/test/test_helper.rb:39: warning: method redefined; > discarding old test_template_source_with_locals_of_strings > /<>/test/tilt_template_test.rb:132: warning: previous definition > of test_template_source_with_locals_of_strings was here > Tilt::TypeScriptTemplate (disabled) > Tilt::WikiClothTemplate (disabled) > Run options: -v --seed 27460 > > #
Bug#1026895: ruby-html2haml: FTBFS with ruby-haml 6.1.1: ERROR: Test "ruby3.1" failed: Could not find 'haml' (>= 4.0, < 6) among 102 total gem(s) (Gem::MissingSpecError)
Source: ruby-html2haml Version: 2.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block > in activate_dependencies': Could not find 'haml' (>= 4.0, < 6) among 102 > total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /<>/debian/ruby-html2haml/usr/share/rubygems-integration/all/specifications/html2haml-2.2.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381: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 'haml' (>= 4.0, < 6) - did find: [haml-6.1.1] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381: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 `' > abbrev (default: 0.1.0) > base64 (default: 0.1.1) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (default: 2.3.7) > cgi (default: 0.3.1) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > did_you_mean (default: 1.6.1) > digest (default: 3.1.0) > drb (default: 2.1.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > erubis (2.7.0) > etc (default: 1.3.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > haml (6.1.1) > io-console (default: 0.5.11) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.1) > ipaddr (default: 1.2.4) > irb (default: 1.4.1) > json (default: 2.6.1) > logger (default: 1.5.0) > matrix (0.4.2) > mini_portile2 (2.8.0) > minitest (5.15.0) > mutex_m (default: 0.1.1) > net-ftp (0.1.3) > net-http (default: 0.2.0) > net-imap (0.2.3) > net-pop (0.1.1) > net-protocol (default: 0.1.2) > net-smtp (0.3.1) > net-telnet (0.1.1) > nkf (default: 0.1.1) > nokogiri (1.13.10) > observer (default: 0.1.1) > open-uri (default: 0.2.0) > open3 (default: 0.1.1) > openssl (default: 3.0.0) > optparse (default: 0.2.0) > ostruct (default: 0.5.2) > pathname (default: 0.2.0) > pkg-config (1.4.6) > power_assert (2.0.1) > pp (default: 0.3.0) > prettyprint (default: 0.1.1) > prime (0.1.2) > pstore (default: 0.1.1) > psych (default: 4.0.3) > racc (default: 1.6.0, 1.4.14) > rake (13.0.6) > rbs (2.1.0) > rdoc (default: 6.4.0) > readline (default: 0.0.3) > readline-ext (default: 0.1.4) > reline (default: 0.3.0) > resolv (default: 0.2.1) > resolv-replace (default: 0.1.0) > rexml (3.2.5) > rinda (default: 0.1.1) > rss (0.2.9) > ruby2_keywords (default: 0.0.5) > ruby_parser (3.15.1) > rubygems-update (3.3.15) > sdbm (1.0.0) > securerandom (default: 0.1.1) > set (default: 1.0.2) > sexp_processor (4.15.2) > shellwords (default: 0.1.0) > singleton (default: 0.1.1) > stringio (default: 3.0.1) > strscan (default: 3.0.1) > syslog (default: 0.1.0) > tempfile (default: 0.1.2) > temple (0.8.2) > test-unit (3.5.3) > thor (1.2.1) > tilt (2.0.11) > time (default: 0.2.0) >
Bug#1026894: ruby-haml-rails: FTBFS: unsatisfiable build-dependency: ruby-haml (< 6.0) but 6.1.1-1 is to be installed
Source: ruby-haml-rails Version: 2.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable build dependencies. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, > ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= > 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, > ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= > 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, > build-essential, fakeroot > 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 [580 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [776 B] > Get:5 copy:/<>/apt_archive ./ Packages [808 B] > Fetched 2164 B in 0s (0 B/s) > Reading package lists... > Get:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease > Ign:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease > Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B] > Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B] > Get:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg > Ign:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: ruby-haml (< 6.0) but 6.1.1-1 is > to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. signature.asc Description: PGP signature
Bug#1026893: ruby-haml-contrib: FTBFS: ERROR: Test "ruby3.1" failed: /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in `': Filters is not a modul
Source: ruby-haml-contrib Version: 1.0.0.1-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with a test failure. Relevant part (hopefully): > /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in > `': Filters is not a module (TypeError) > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/haml-6.1.1/lib/haml/filters/base.rb:5: > previous definition of Filters was here > from > /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:7:in > `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/php_filter_test.rb:2:in `' > from > :85:in > `require' > from > :85:in > `require' > from debian/ruby-tests.rb:2:in `block in ' > from debian/ruby-tests.rb:2:in `each' > from debian/ruby-tests.rb:2:in `' > ERROR: Test "ruby3.1" failed: Attached is the full build log. ruby-haml-contrib.log.gz Description: application/gzip signature.asc Description: PGP signature
Bug#1026892: asciidoctor: FTBFS with haml 6.1.1: ERROR: Test "ruby3.1" failed.
Source: asciidoctor Version: 2.0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, I'm working on updating ruby-haml to the new upstream versinon 6.1.1, and when trying asciidoctor against that the tests fail. Relevant part (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.1 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -e gem\ \"asciidoctor\" > > ┌──┐ > │ Run tests for ruby3.1 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-asciidoctor/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.1 -w -I"lib:test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/api_test.rb" "test/attribute_list_test.rb" "test/attributes_test.rb" > "test/blocks_test.rb" "test/converter_test.rb" "test/document_test.rb" > "test/extensions_test.rb" "test/helpers_test.rb" "test/invoker_test.rb" > "test/links_test.rb" "test/lists_test.rb" "test/logger_test.rb" > "test/manpage_test.rb" "test/options_test.rb" "test/paragraphs_test.rb" > "test/parser_test.rb" "test/paths_test.rb" "test/preamble_test.rb" > "test/reader_test.rb" "test/sections_test.rb" "test/substitutions_test.rb" > "test/syntax_highlighter_test.rb" "test/tables_test.rb" "test/text_test.rb" > RUBY_GC_HEAP_FREE_SLOTS=75 (default value: 4096) > RUBY_GC_HEAP_INIT_SLOTS=75 (default value: 1) > RUBY_GC_HEAP_GROWTH_FACTOR=2.00 (default value: 1.80) > RUBY_GC_HEAP_GROWTH_MAX_SLOTS=5 (default value: 0) > RUBY_GC_MALLOC_LIMIT=12800 (default value: 16777216) > RUBY_GC_OLDMALLOC_LIMIT=12800 (default value: 16777216) > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85: > warning: possibly useless use of a variable in void context > Run options: --seed 60429 > > # Running: > > ...Haml::Engine: > Option :attr_wrapper is invalid > Haml::Engine: Option :attr_wrapper is invalid > FHaml::Engine: Option :attr_wrapper is invalid >
Bug#1026779: binutils: cross binutils and foreign libbinutils not coinstallable, breaking upgrades
Source: binutils
Version: 2.39.50.20221208-5
Severity: serious
Dear Maintainer,
Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
where both are installed (e.g. binutils-aarch64-linux-gnu and
libbinutils:arm64) fails like this:
8<8<8<-
Unpacking libbinutils:arm64 (2.39.50.20221208-5) over (2.39-8) ...
Preparing to unpack
.../3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb ...
Unpacking binutils-aarch64-linux-gnu (2.39.50.20221208-5) over (2.39-8) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/aarch64-linux-gnu/libsframe.so.0.0.0', which is
also in package libbinutils:arm64 2.39.50.20221208-5
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../4-binutils-common_2.39.50.20221208-5_amd64.deb ...
De-configuring binutils-common:arm64 (2.39-8), to allow configuration of
binutils-common:amd64 (2.39.50.20221208-5) ...
Unpacking binutils-common:amd64 (2.39.50.20221208-5) over (2.39-8) ...
Preparing to unpack .../5-binutils-common_2.39.50.20221208-5_arm64.deb ...
Unpacking binutils-common:arm64 (2.39.50.20221208-5) over (2.39-8) ...
Selecting previously unselected package libbinutils:amd64.
Preparing to unpack .../6-libbinutils_2.39.50.20221208-5_amd64.deb ...
Unpacking libbinutils:amd64 (2.39.50.20221208-5) ...
Selecting previously unselected package libjansson4:amd64.
Preparing to unpack .../7-libjansson4_2.14-2_amd64.deb ...
Unpacking libjansson4:amd64 (2.14-2) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
8<8<8<-
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (500,
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
signature.asc
Description: PGP signature
Bug#1026427: jekyll: depends on deprecated and broken ruby-safe-yaml
Package: jekyll Version: 3.9.0+dfsg-5 Severity: serious Tags: upstream Dear Maintainer, Working to get ruby3.1 as the default Ruby version it was noticed that ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most upstreams have dropped their dependencies on it; I checked and jekyll is not there yet. There is this pull request upstream, but that didn't get into a release yet: https://github.com/jekyll/jekyll/pull/8772 ruby-safe-yaml will soon be removed from testing due to this (maybe even before the autoremoval), jekyll needs to drop its dependency on it. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#1026227: vagrant: Uninstallable in sid with VirtualBox 7.0.x
On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote: > Package: vagrant > Version: 2.2.19+dfsg-2 > Severity: serious > > Hi! > > Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable > in Debian sid. I assume this will require packaging a new upstream > release to support the new virtualbox version 7.0.x series. I cherry picked a patch from upstream that should solve the issue. The Breaks: restriction will now make the package installable with virtualbox 7.0, but I don't use virtualbox so I can't really test that it actually works. Can you please try the package from git master? signature.asc Description: PGP signature
Bug#1026107: ruby-asciidoctor-pdf: depends on deprecated ruby-safe-yaml
Package: ruby-asciidoctor-pdf Version: 1.6.2-1 Severity: serious Tags: upstream User: debian-r...@lists.debian.org Usertags: ruby3.1 Dear Maintainer, Working to get ruby3.1 as the default Ruby version it was noticed that ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most upstreams have dropped their dependencies on it; I checked and that is also the case for asciidoctor-pdf: v2.3.4 no longer depends on safe_yaml. ruby-safe-yaml will soon be removed from testing due to this, ruby-asciidoctor-pdf needs to drop its dependency on it. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-asciidoctor-pdf depends on: ii ruby 1:3.1~1 ii ruby-asciidoctor 2.0.17-1 ii ruby-concurrent 1.1.6+dfsg-5 pn ruby-prawn pn ruby-prawn-icon pn ruby-prawn-svg pn ruby-prawn-table ii ruby-safe-yaml1.0.5-2 pn ruby-treetop ruby-asciidoctor-pdf recommends no packages. Versions of packages ruby-asciidoctor-pdf suggests: ii ruby-rouge 3.30.0-2 signature.asc Description: PGP signature
Bug#1019635: marked as pending in ruby-mail
Control: tag -1 pending Hello, Bug #1019635 in ruby-mail reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-mail/-/commit/2460a6e62ef16ff6d73456ca7fb2550523726783 Add patches to fix tests with ruby3.1 Closes: #1019635 (this message was generated automatically) -- Greetings https://bugs.debian.org/1019635
Bug#1025261: marked as pending in vagrant
Control: tag -1 pending Hello, Bug #1025261 in vagrant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/vagrant/-/commit/f89c5d4283f370fda5c2564221812ac1ef058317 Don't force an upper bound on Ruby versions Closes: #1025261 (this message was generated automatically) -- Greetings https://bugs.debian.org/1025261
Bug#1024174: closing 1024175, closing 1024174
close 1024175 4.1.0-1 close 1024174 1.0.1-1 thanks These bugs have been closed in the last uploads of ruby-omniauth-gitlab and ruby-omniauth-dingtalk-oauth2, respectively, but I missed the bugs already reported.
Bug#1006022: marked as pending in puma
Control: tag -1 pending Hello, Bug #1006022 in puma reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/puma/-/commit/e6961fbc2125bcaccb759b4c7fb05576ed37545e debian/ruby-tests.rake: skip test that fails often I tried rebuilding 10 times, and that one test failed in 2 of those builds. Closes: #1006022 (this message was generated automatically) -- Greetings https://bugs.debian.org/1006022
Bug#1021737: lava: CVE-2022-42902
On Wed, Oct 19, 2022 at 09:57:34PM +0200, Moritz Muehlenhoff wrote: > On Tue, Oct 18, 2022 at 06:09:42PM -0300, Antonio Terceiro wrote: > > Hi, > > > > On Thu, Oct 13, 2022 at 09:13:18PM +0200, Moritz Mühlenhoff wrote: > > > Source: lava > > > X-Debbugs-CC: t...@security.debian.org > > > Severity: grave > > > Tags: security > > > > > > Hi, > > > > > > The following vulnerability was published for lava. > > > > > > CVE-2022-42902[0]: > > > | In Linaro Automated Validation Architecture (LAVA) before 2022.10, > > > | there is dynamic code execution in lava_server/lavatable.py. Due to > > > | improper input sanitization, an anonymous user can force the lava- > > > | server-gunicorn service to execute user-provided code on the server. > > > > > > https://git.lavasoftware.org/lava/lava/-/merge_requests/1834 > > > https://git.lavasoftware.org/lava/lava/-/commit/e66b74cd6c175ff8826b8f3431740963be228b52?merge_request_iid=1834 > > > > > > If you fix the vulnerability please also make sure to include the > > > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > > > > > For further information see: > > > > > > [0] https://security-tracker.debian.org/tracker/CVE-2022-42902 > > > https://www.cve.org/CVERecord?id=CVE-2022-42902 > > > > > > Please adjust the affected versions in the BTS as needed. > > > > I have uploaded a fix version to unstable (latest upstream), and I would > > like to upload the attached debdiff to -security. That package builds > > cleanly and passes its autopkgtest on bullseye. Let me know. > > Ack, we can fix this via a DSA. The debdiff looks fine content-wise, > but the deb111u1 version is slightly off by 100 Debian releases ;-) > > So please change to +deb11u1 and upload to security-master. Heh, my mistake. Just uploaded. signature.asc Description: PGP signature
Bug#1021737: lava: CVE-2022-42902
On Tue, Oct 18, 2022 at 06:09:45PM -0300, Antonio Terceiro wrote: > Hi, > > On Thu, Oct 13, 2022 at 09:13:18PM +0200, Moritz Mühlenhoff wrote: > > Source: lava > > X-Debbugs-CC: t...@security.debian.org > > Severity: grave > > Tags: security > > > > Hi, > > > > The following vulnerability was published for lava. > > > > CVE-2022-42902[0]: > > | In Linaro Automated Validation Architecture (LAVA) before 2022.10, > > | there is dynamic code execution in lava_server/lavatable.py. Due to > > | improper input sanitization, an anonymous user can force the lava- > > | server-gunicorn service to execute user-provided code on the server. > > > > https://git.lavasoftware.org/lava/lava/-/merge_requests/1834 > > https://git.lavasoftware.org/lava/lava/-/commit/e66b74cd6c175ff8826b8f3431740963be228b52?merge_request_iid=1834 > > > > If you fix the vulnerability please also make sure to include the > > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > > > For further information see: > > > > [0] https://security-tracker.debian.org/tracker/CVE-2022-42902 > > https://www.cve.org/CVERecord?id=CVE-2022-42902 > > > > Please adjust the affected versions in the BTS as needed. > > I have uploaded a fix version to unstable (latest upstream), and I would > like to upload the attached debdiff to -security. That package builds > cleanly and passes its autopkgtest on bullseye. Let me know. Correction: it fails the autopkgtest, but it fails in the exact same way as the package already in bullseye fails. signature.asc Description: PGP signature
Bug#1021737: lava: CVE-2022-42902
tinue # just skip this term - results in a query matching All.
+q &= Q(**{f"{key}__contains": val})
+
if (
hasattr(self.table_class.Meta, "queries")
and key in self.table_class.Meta.queries.keys()
):
-# note that this calls the function 'key' with the argument from the search
-args = 'q = q.__and__(self.{0}("{1}"))'.format(key, val)
-try:
-exec(args, globals(), local_namespace)
-except SyntaxError:
-# should log exception somewhere...
-continue
+# note that this calls
+# the function 'key' with the argument from the search
+q &= getattr(self, key)(val)
+
# general OR searches
if self.request.GET.get(table_search):
self.terms["search"] = escape(self.request.GET.get(table_search))
if hasattr(self.table_class.Meta, "searches") and "search" in self.terms:
for key, val in self.table_class.Meta.searches.items():
-# this is a little bit of magic - creates an OR clause in the query based
-# on the iterable search hash passed in via the table_class
+# this is a little bit of magic - creates an OR clause
+# in the query based on the iterable search hash
+# passed in via the table_class
# e.g. self.searches = {'id', 'contains'}
-# so every simple search column in the table is queried at the same time with OR
-args = 'q = q.__or__(Q({0}__{1}=self.terms["search"]))'.format(key, val)
-try:
-exec(args, globals(), local_namespace) # sets the value of q
-except SyntaxError:
-# should log exception somewhere...
-continue # just skip this term - results in a query matching All.
+# so every simple search column in the table
+# is queried at the same time with OR
+q |= Q(**{f"{key}__{val}": self.terms["search"]})
+
# call explicit handlers as simple text searches of relational fields.
if hasattr(self.table_class.Meta, "queries"):
for key in self.table_class.Meta.queries:
-# note that this calls the function 'key' with the argument from the search
-args = 'q = q.__or__(self.{0}("{1}"))'.format(
-key, self.terms["search"].encode("utf-8")
-)
-try:
-exec(args, globals(), local_namespace)
-except SyntaxError:
-# should log exception somewhere...
-continue
+# note that this calls the function 'key'
+# with the argument from the search
+q |= getattr(self, key)(self.terms["search"])
+
# now add "class specials" - from an iterable hash
# datetime uses (start_time__lte=timezone.now()-timedelta(days=3)
-data = data.filter(self._time_filter(local_namespace["q"]))
-return data
+return data.filter(self._time_filter(q))
class LavaTable(tables.Table):
From e1f934df702a1db386e301fbe2d51ab4154ee21c Mon Sep 17 00:00:00 2001
From: Antonio Terceiro
Date: Tue, 18 Oct 2022 17:57:46 -0300
Subject: [PATCH] share/requires.py: fix building for debian -backports and
-security suites
---
share/requires.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/share/requires.py b/share/requires.py
index 2599028d8..00aadc3a4 100755
--- a/share/requires.py
+++ b/share/requires.py
@@ -123,6 +123,8 @@ def main():
help="Distribution package names for unittest support - requires --names",
)
args = parser.parse_args()
+args.suite = args.suite.replace("-backports", "")
+args.suite = args.suite.replace("-security", "")
if args.unittests and not args.names:
raise RuntimeError("--unittests option requires --names")
try:
--
2.35.1
diff -Nru lava-2020.12/debian/changelog lava-2020.12/debian/changelog
--- lava-2020.12/debian/changelog 2021-05-24 09:05:18.0 -0300
+++ lava-2020.12/debian/changelog 2022-10-18 17:24:50.0 -0300
@@ -1,3 +1,10 @@
+lava (2020.12-5+deb111u1) bullseye-security; urgency=high
+
+ * Fix remote code execution [CVE-2022-42902] (Closes: #1021737)
+ * Add patch to fix building the package for -security
+
+ -- Antonio Terceiro Tue, 18 Oct 2022 17:24:50 -0300
+
lava (2020.12-5) unstable; urgency=medium
* Fix PyYAML usage after backwards-incompatible se
Bug#979887: closing 979887
close 979887 2022.01.3-3 thanks This has actually been fixed before 2022.01. Closing.
Bug#1020776: closing 1020776
close 1020776 thanks
Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
Hi, On Fri, Oct 07, 2022 at 01:50:56AM +0300, Adrian Bunk wrote: > On Mon, Sep 12, 2022 at 08:24:43PM -0300, Antonio Terceiro wrote: > > Source: ruby-ahoy-email > > Version: 1.1.1-2 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs > > User: debian-r...@lists.debian.org > > Usertags: ruby3.1 > > > > Hi, > > > > We are about to start the ruby3.1 transition in unstable. While trying to > > rebuild ruby-ahoy-email with ruby3.1 enabled, the build failed. > > > > Relevant part of the build log (hopefully): > > > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > > > `require': cannot load such file -- net/smtp (LoadError) > > Do you have any ides where this dependency is required and why it isn't found? $ dpkg -S net/smtp.rb libruby3.0:amd64: /usr/lib/ruby/3.0.0/net/smtp.rb libruby3.1:amd64: /usr/lib/ruby/gems/3.1.0/gems/net-smtp-0.3.1/lib/net/smtp.rb In ruby3.0, net/smtp was part of the standard library, and in ruby3.1, it's now a "default gem", which is more or less a third-party library that happens to be shipped together with the standard library. And it seems that the test suite for this package loads bundler. bundler prevents any library that is not part of the standard library and is not explicitly declared the Gemfile from being loaded, therefore it looks like the library is not installed. But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so this is a bit weird. Our version is also quite outated wrt upstream, so my first attempt would be to just update the latest upstream (there are no reverse dependencies in the archive). signature.asc Description: PGP signature
Bug#1020435: ruby-prof: FTBFS on ppc64el
Control: tag -1 + unreproducible Control: severity -1 important Hi, On Wed, Sep 21, 2022 at 07:20:31PM +0200, Sebastian Ramacher wrote: > Source: ruby-prof > Version: 1.4.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=ruby-prof=ppc64el=1.4.3-1%2Bb1=1663720013=0 > > 1) Failure: > PrinterGraphTest#test_graph_results_sorting > [/<>/test/printer_graph_test.rb:37]: > Array [0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, > 0.0, 0.0, 0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0] is not sorted. > --- expected > +++ actual > @@ -1 +1 @@ > -[0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, > 0.0, 0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0] > +[0.171, 0.171, 0.17, 0.17, 0.169, 0.169, 0.167, 0.167, 0.166, 0.164, 0.004, > 0.004, 0.002, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0] > > > 51 runs, 687 assertions, 1 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/abstract_printer_test.rb" "test/alias_test.rb" "test/basic_test.rb" > "test/call_tree_visitor_test.rb" "test/call_trees_test.rb" > "test/duplicate_names_test.rb" "test/enumerable_test.rb" > "test/exceptions_test.rb" "test/exclude_methods_test.rb" > "test/exclude_threads_test.rb" "test/fiber_test.rb" "test/gc_test.rb" > "test/line_number_test.rb" "test/marshal_test.rb" > "test/multi_printer_test.rb" "test/no_method_class_test.rb" > "test/printer_call_stack_test.rb" "test/printer_call_tree_test.rb" > "test/printer_flat_test.rb" "test/printer_graph_html_test.rb" > "test/printer_graph_test.rb" "test/printing_recursive_graph_test.rb" > "test/profile_test.rb" "test/rack_test.rb" "test/singleton_test.rb" -v] > /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in ` (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Exiting. Unfortunately I could not reproduce this on the ppc64el porterbox, even trying the same random seed as the original build failure. I was suspecting an random test failure, but I didn't see this after trying 50 builds in a row. In fact, just giving back the build on the buildd made it succeed. I'm not saying there is no issue, so I am keeping this open and maybe we will be able to figure it out at some point. I hope you don't mind me downgrading this to important. signature.asc Description: PGP signature
Bug#1020536: unicorn-engine: FTBFS on s390x: several test failures
Source: unicorn-engine Version: 2.0.0-3 Severity: serious Tags: ftbfs Justification: fails to build from source Dear Maintainer, unicorn-engine fails to build on s390x, with several test failures. It seems to pass on all other release architectures. 8<8<8<- FAILED: 26 of 33 unit tests have failed. 25% tests passed, 9 tests failed out of 12 Total Test time (real) = 0.31 sec The following tests FAILED: 1 - test_x86 (Failed) 2 - test_arm (Failed) 3 - test_arm64 (Failed) 4 - test_m68k (Failed) 5 - test_mips (Failed) 7 - test_ppc (Failed) 8 - test_riscv (Failed) 11 - test_mem (Failed) 12 - test_ctl (Failed) Errors while running CTest 8<8<8<- The full build log is available at https://buildd.debian.org/status/fetch.php?pkg=unicorn-engine=s390x=2.0.0-3=1663852538=0 signature.asc Description: PGP signature
Bug#1019623: ruby-fog-core: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
hould create a getter to save the > association model = 0.00 s = . > Fog::Attributes::.has_one#test_0001_should create an instance_variable to > save the association object = 0.00 s = . > Fog::Attributes::.has_one#test_0003_should create a setter that accept an > object as param = 0.00 s = . > Fog::Attributes::.has_one#test_0004_should create an alias to single = 0.00 s > = . > Fog::Attributes::.has_many_identities::should create a setter that accept an > array of#test_0001_ids as param = 0.00 s = . > Fog::Attributes::.has_many_identities::should create a setter that accept an > array of#test_0002_models as param = 0.00 s = . > Fog::Compute::Server::#sshable?::when the server is not ready#test_0001_is > false = 0.00 s = . > Fog::Identity::#new#test_0001_instantiates an instance of > Fog::Identity:: from the :provider keyword arg = 0.00 s = . > Fog::Identity::#new#test_0002_instantiates an instance of > FogIdentity from the :provider keyword arg = 0.00 s = . > Fog::Identity::#new#test_0003_passes the supplied keyword args less :provider > to Fog::Identity::#new = 0.00 s = . > Fog::Identity::#new#test_0004_raises ArgumentError when given a :provider > where a Fog::Identity::Provider that does not exist = 0.00 s = . > > Finished in 7.056015s, 33.5884 runs/s, 42.6586 assertions/s. > > 1) Failure: > Fog::Cache#test_0004_load bad cache data - empty file, from disk > [/<>/spec/core/cache_spec.rb:90]: > Expected: false > Actual: nil > > 237 runs, 301 assertions, 1 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"spec" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "./spec/compute/models/server_spec.rb" "./spec/compute_spec.rb" > "./spec/connection_spec.rb" "./spec/core/cache_spec.rb" > "./spec/core/model_spec.rb" "./spec/core/stringify_keys_spec.rb" > "./spec/core/whitelist_keys_spec.rb" "./spec/credentials_spec.rb" > "./spec/current_machine_spec.rb" "./spec/fog_attribute_spec.rb" > "./spec/formatador_spec.rb" "./spec/identity_spec.rb" > "./spec/mocking_spec.rb" "./spec/service_spec.rb" "./spec/storage_spec.rb" > "./spec/test_helpers/formats_helper_spec.rb" > "./spec/test_helpers/schema_validator_spec.rb" "./spec/timeout_spec.rb" > "./spec/utils_spec.rb" "./spec/uuid_spec.rb" "./spec/wait_for_spec.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed. The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-fog-core/ruby-fog-core_2.1.0-3.1+rebuild1663007614_amd64-2022-09-12T18:33:35Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019620: ruby-enumerize: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
Source: ruby-enumerize Version: 2.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-enumerize with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.1 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-enumerize/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -e gem\ \"enumerize\" > > ┌──┐ > │ Run tests for ruby3.1 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-enumerize/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.1 -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/activemodel_test.rb" "test/activerecord_test.rb" > "test/attribute_map_test.rb" "test/attribute_test.rb" "test/base_test.rb" > "test/module_attributes_test.rb" "test/mongo_mapper_test.rb" > "test/mongoid_test.rb" "test/multiple_test.rb" "test/predicates_test.rb" > "test/rails_admin_test.rb" "test/sequel_test.rb" "test/set_test.rb" > "test/value_test.rb" -v > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/core_ext/class/subclasses.rb:30: > warning: method redefined; discarding old subclasses > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.7/lib/nokogiri/version/info.rb:85: > warning: possibly useless use of a variable in void context > /<>/test/activerecord_test.rb:411: warning: assigned but unused > variable - document_2 > /<>/test/sequel_test.rb:302: warning: assigned but unused > variable - document_2 > DEPRECATED: global use of must_equal from test/activerecord_test.rb:232. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of wont_be from test/activerecord_test.rb:233. Use > _(obj).wont_be instead. This will fail in Minitest 6. > DEPRECATED: global use of must_include from test/activerecord_test.rb:234. > Use _(obj).must_include instead. This will fail in Minitest 6. > DEPRECATED: global use of must_be_nil from test/activerecord_test.rb:594. Use > _(obj).must_be_nil instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:542. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of wont_be from test/activerecord_test.rb:217. Use > _(obj).wont_be instead. This will fail in Minitest 6. > DEPRECATED: global use of must_include from test/activerecord_test.rb:218. > Use _(obj).must_include instead. This will fail in Minitest 6. > DEPRECATED: global use of must_be from test/activerecord_test.rb:290. Use > _(obj).must_be instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:468. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:469. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:642. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:643. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from test/activerecord_test.rb:644. Use > _(obj).must_equal instead. This will fail in Minitest 6. > Run options: -v --seed 3512 > > # Running: > > Enumerize::ActiveRecordSupport#test_0014_validates inclusion when using > write_attribute with string attribute = 0.01 s = . > Enumerize::ActiveRecordSupport#test_0048_sets attribute to nil if given one > is not valid = 0.01 s = . > Enumerize::ActiveRecordSupport#test_0043_allows using update_all with values > = 0.00 s = . >
Bug#1019619: ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
rrections_include_top_level_class_name = 0.00 s = . > ClassNameCheckTest#test_corrections_should_work_from_within_instance_method = > 0.00 s = . > ClassNameCheckTest#test_corrections_should_work_from_within_instance_method_on_nested_class > = 0.00 s = . > VariableNameCheckTest#test_corrections_include_private_method = (none):61: > warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_struct_name_error = (none):61: warning: assigned > but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_corrections_include_method_from_module = > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_corrections_include_instance_method = (none):61: > warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_exclude_typical_incorrect_suggestions = (none):61: > warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_corrections_include_local_variable_name = > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_corrections_include_ruby_predefined_objects = > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.01 s = . > VariableNameCheckTest#test_corrections_include_class_variable_name = > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > VariableNameCheckTest#test_corrections_include_instance_variable_name = > (none):61: warning: assigned but unused variable - some_var > (none):61: warning: assigned but unused variable - some_var > 0.00 s = . > JaroWinklerTest#test_jaro_winkler_distance = 0.00 s = . > JaroWinklerTest#test_jarowinkler_distance_with_utf8_strings = 0.00 s = . > DeprecatedIgnoreCallersTest#test_ignore = 0.00 s = . > > Finished in 0.055686s, 754.2342 runs/s, 3070.8105 assertions/s. > > 1) Failure: > UncorrectableNameCheckTest#test_message > [/<>/test/spell_checking/uncorrectable_name_check_test.rb:13]: > --- expected > +++ actual > @@ -1 +1,4 @@ > -"Other name error" > +"Other name error > + > + raise FirstNameError, \"Other name error\" > + ^" > > > 2) Skipped: > NameErrorExtensionTest#test_message > [/<>/test/core_ext/name_error_extension_test.rb:22]: > Skipped, no message given > > 42 runs, 171 assertions, 1 failures, 0 errors, 1 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/core_ext/name_error_extension_test.rb" > "test/deprecated_formatter_test.rb" "test/edit_distance/jaro_winkler_test.rb" > "test/spell_checker_test.rb" "test/spell_checking/class_name_check_test.rb" > "test/spell_checking/key_name_check_test.rb" > "test/spell_checking/method_name_check_test.rb" > "test/spell_checking/uncorrectable_name_check_test.rb" > "test/spell_checking/variable_name_check_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed. The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-did-you-mean/ruby-did-you-mean_1.2.1-1+rebuild1663007513_amd64-2022-09-12T18:31:53Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019622: ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "undefined method 'static_attributes_are_gone' in 'broken' factory\nDid you mean? 's
Source: ruby-factory-bot
Version: 6.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-factory-bot with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
>expected NoMethodError with "undefined method
> 'static_attributes_are_gone' in 'broken' factory\nDid you mean?
> 'static_attributes_are_gone { \"true\" }'\n", got # method 'static_attributes_are_gone' in 'broken' factory
>Did you mean? 'static_attributes_are_gone { "true" }'
>
>
>raise NoMethodError.new(<<~MSG)
>^> with backtrace:
> # ./lib/factory_bot/definition_proxy.rb:99:in `method_missing'
> # ./spec/factory_bot/definition_proxy_spec.rb:69:in `block (3
> levels) in '
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2
> levels) in '
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2 levels) in
> '
>
> Finished in 0.429 seconds (files took 0.32709 seconds to load)
> 290 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/factory_bot/definition_proxy_spec.rb:66 #
> FactoryBot::DefinitionProxy#method_missing raises a NoMethodError when called
> with a static-attribute-like argument
>
> Randomized with seed 11142
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern spec/\{\*_spec.rb,factory_bot/\*\*/\*_spec.rb\} --format
> documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-factory-bot/ruby-factory-bot_6.2.0-2+rebuild1663007590_amd64-2022-09-12T18:33:11Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
Bug#1019621: ruby-excon: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:
Source: ruby-excon Version: 0.88.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-excon with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > RuntimeError: > Shared Example Group: "a excon test server" called from > ./spec/excon/test/server_spec.rb:22 > # ./lib/excon/test/plugin/server/puma.rb:12:in `start' > # > ./spec/support/shared_examples/shared_example_for_test_servers.rb:10:in > `block (2 levels) in ' > > Finished in 1.38 seconds (files took 0.2012 seconds to load) > 143 examples, 1 failure > > Failed examples: > > rspec './spec/excon/test/server_spec.rb[1:3:1:2]' # Excon::Test::Server when > the web server is puma it should behave like a excon test server starts the > server > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern spec/\*\*/\*_spec.rb -c -f doc -r ./spec/spec_helper.rb failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-excon/ruby-excon_0.88.0-1+rebuild1663007570_amd64-2022-09-12T18:32:50Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019616: ruby-dalli: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Source: ruby-dalli Version: 3.0.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-dalli with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > adduser: Warning: The home dir /nonexistent you specified can't be accessed: > No such file or directory > invoke-rc.d: could not determine current runlevel > All runlevel operations denied by policy > invoke-rc.d: policy-rc.d denied execution of start. > Setting up libldap-2.5-0:amd64 (2.5.12+dfsg-2+b1) ... > Setting up intltool-debian (0.35.0+20060710.5) ... > Setting up libpython3.10-stdlib:amd64 (3.10.7-1) ... > Setting up dh-autoreconf (20) ... > Setting up patchutils (0.4.2-1) ... > Setting up ruby-mail (2.7.1+dfsg1-1.1) ... > Setting up libjs-jquery-ui (1.13.2+dfsg-1) ... > Setting up ruby-activemodel (2:6.1.6.1+dfsg-4) ... > Setting up dh-strip-nondeterminism (1.13.0-1) ... > Setting up libwww-robotrules-perl (6.02-1) ... > Setting up dwz (0.14-1) ... > Setting up groff-base (1.22.4-8) ... > Setting up libhtml-parser-perl:amd64 (3.78-1) ... > Setting up libxslt1.1:amd64 (1.1.35-1) ... > Setting up gpgconf (2.2.39-1) ... > Setting up libio-socket-ssl-perl (2.075-1) ... > Setting up gpg (2.2.39-1) ... > Setting up libpython3-stdlib:amd64 (3.10.6-1) ... > Setting up gnupg-utils (2.2.39-1) ... > Setting up libhttp-message-perl (6.37-1) ... > Setting up ruby-rails-deprecated-sanitizer (1.0.3-3.1+rebuild1658565853) ... > Setting up libhttp-negotiate-perl (6.01-1) ... > Setting up gpg-agent (2.2.39-1) ... > Setting up ruby-globalid (0.6.0-1+rebuild1658566084) ... > Setting up python3.10 (3.10.7-1) ... > Setting up ruby-activerecord (2:6.1.6.1+dfsg-4) ... > Setting up ruby-nokogiri (1.13.7+dfsg-2+rebuild1662922586) ... > Setting up libhttp-cookies-perl (6.10-1) ... > Setting up ruby-simplecov-html (0.12.3-2) ... > Setting up po-debconf (1.0.21+nmu1) ... > Setting up libhtml-tree-perl (5.07-2) ... > Setting up libparams-classify-perl:amd64 (0.015-2) ... > Setting up gpgsm (2.2.39-1) ... > Setting up python3 (3.10.6-1) ... > Setting up man-db (2.10.2-3) ... > Not building database; man-db/auto-update is not 'true'. > Setting up dirmngr (2.2.39-1) ... > Setting up libmodule-runtime-perl (0.016-2) ... > Setting up ruby-simplecov (0.21.2-1.1) ... > Setting up ruby-loofah (2.18.0-1) ... > Setting up gpg-wks-server (2.2.39-1) ... > Setting up ruby-rails-dom-testing (2.0.3-4+rebuild1659020114) ... > Setting up ruby-activejob (2:6.1.6.1+dfsg-4) ... > Setting up gpg-wks-client (2.2.39-1) ... > Setting up libimport-into-perl (1.002005-2) ... > Setting up libmoo-perl (2.005004-3) ... > Setting up debhelper (13.9.1) ... > Setting up ruby-rails-html-sanitizer (1.4.2-2) ... > Setting up ruby-actionview (2:6.1.6.1+dfsg-4) ... > Setting up gnupg (2.2.39-1) ... > Setting up ruby-actionpack (2:6.1.6.1+dfsg-4) ... > Setting up ruby-sprockets-rails (3.4.1-2+rebuild1659020268) ... > Setting up ruby-actioncable (2:6.1.6.1+dfsg-4) ... > Setting up ruby-actionmailer (2:6.1.6.1+dfsg-4) ... > Setting up ruby-activestorage (2:6.1.6.1+dfsg-4) ... > Setting up ruby-actiontext (2:6.1.6.1+dfsg-4) ... > Setting up ruby-actionmailbox (2:6.1.6.1+dfsg-4) ... > Setting up ruby-railties (2:6.1.6.1+dfsg-4) ... > Setting up ruby-rails (2:6.1.6.1+dfsg-4) ... > Setting up libwww-perl (6.67-1) ... > Setting up devscripts (2.22.2) ... > Setting up gem2deb (2.0.3) ... > Setting up liblwp-protocol-https-perl (6.10-1) ... > Setting up sbuild-build-depends-main-dummy (0.invalid.0) ... > Processing triggers for libc-bin (2.34-8) ... > > +--+ > | Check architectures > | > +--+ > > Arch check ok (amd64 included in all) > > +--+ > | Build environment > | > +--+ > > Kernel: Linux 5.10.0-16-cloud-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) > amd64 (x86_64) > Toolchain package versions: binutils_2.38.90.20220713-2 dpkg-dev_1.21.9 > g++-11_11.3.0-6 g++-12_12.2.0-2 gcc-11_11.3.0-6 gcc-12_12.2.0-2 > libc6-dev_2.34-8 libstdc++-11-dev_11.3.0-6 libstdc++-12-dev_12.2.0-2 > libstdc++6_12.2.0-2 linux-libc-dev_5.19.6-1 > Package versions: adduser_3.129 apt_2.5.2 auto-apt-proxy_14 autoconf_2.71-2 > automake_1:1.16.5-1.3 autopoint_0.21-9 autotools-dev_20220109.1 > base-files_12.2 base-passwd_3.6.0 bash_5.2~rc2-2 binutils_2.38.90.20220713-2 > binutils-common_2.38.90.20220713-2 > binutils-x86-64-linux-gnu_2.38.90.20220713-2 bsdextrautils_2.38.1-1 > bsdutils_1:2.38.1-1 build-essential_12.9 bzip2_1.0.8-5 >
Bug#1019618: ruby-delayed-job: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:
Source: ruby-delayed-job Version: 4.1.9-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-delayed-job with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > Failure/Error: >expect do > yaml = "--- !ruby/struct\nn: 1\n" > object = YAML.load(yaml) > expect(object).to be_kind_of(Struct) > expect(object.n).to eq(1) >end.not_to raise_error > >expected no Exception, got # unspecified class: Struct> with backtrace: > # (eval):2:in `struct' > # ./spec/yaml_ext_spec.rb:28:in `block (3 levels) in (required)>' > # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in (required)>' > # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in ' > > Finished in 1.46 seconds (files took 0.9459 seconds to load) > 177 examples, 1 failure > > Failed examples: > > rspec ./spec/yaml_ext_spec.rb:25 # YAML autoloads the class of an anonymous > struct > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-delayed-job/ruby-delayed-job_4.1.9-1+rebuild1663007476_amd64-2022-09-12T18:31:17Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019617: ruby-delayed-job-active-record: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:
Source: ruby-delayed-job-active-record Version: 4.1.6-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-delayed-job-active-record with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > Failure/Error: >expect do > YAML.load(Story.create.to_yaml) >end.not_to raise_error > >expected no Exception, got # unspecified class: Story> with backtrace: > # ./spec/delayed/serialization/active_record_spec.rb:8:in `block (3 > levels) in ' > # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 > levels) in ' > # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 > levels) in ' > > Finished in 1.4 seconds (files took 0.51816 seconds to load) > 101 examples, 1 failure > > Failed examples: > > rspec ./spec/delayed/serialization/active_record_spec.rb:6 # ActiveRecord > loads classes with non-default primary key > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-delayed-job-active-record/ruby-delayed-job-active-record_4.1.6-3+rebuild1663007492_amd64-2022-09-12T18:31:33Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019615: ruby-crack: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
Error:
> JSON Parsing#test_0028_decode json (false):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 18) Error:
> JSON Parsing#test_0035_decode json ({"foo":"bar\x00baz"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 19) Error:
> JSON Parsing#test_0005_decode json ({"return\"To\":":{"\/categories":"\/"}}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 20) Error:
> JSON Parsing#test_0011_decode json ({"a": "2007-01-01"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 21) Error:
> JSON Parsing#test_0026_decode json (null):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 22) Error:
> JSON Parsing#test_0032_decode json (bar\u):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 23) Error:
> JSON Parsing#test_0001_decode json ({"data": "G\u00fcnter"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 24) Error:
> JSON Parsing#test_0029_decode json ("http:\/\/test.host\/posts\/1"):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 25) Error:
> JSON Parsing#test_0034_decode json ({"foo":"bar\x00"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 26) Error:
> JSON Parsing#test_0027_decode json (true):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 27) Error:
> JSON Parsing#test_0009_decode json ({"a": "'", "b": "5,000"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 28) Error:
> JSON Parsing#test_0030_decode json ({"foo":"bar\u"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 29) Error:
> JSON Parsing#test_0040_does not raise SystemStackError when parsing large
> JSON files:
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:89:in `block (2 levels) in (required)>'
>
> 30) Error:
> JSON Parsing#test_0003_decode json ({"returnTo":{"\/categories":"\/"}}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/lib/crack/json.rb:14:in `parse'
> /<>/test/json_test.rb:50:in `block (3 levels) in (required)>'
>
> 31) Error:
> JSON Parsing#test_0017_decode json ({"bio": "1985-01-29: birthdate"}):
> Crack::ParseError: Invalid JSON string
> /<>/lib/crack/json.rb:18:in `rescue in parse'
> /<>/li
Bug#1019613: ruby-capybara: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: raise LoadError, 'Capybara is unable to load `puma` for its server, please add `puma` to your project or sp
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:8]' # > Capybara::Session RackTest #current_url, #current_path, #current_host is > affected by following a redirect > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:9]' # > Capybara::Session RackTest #current_url, #current_path, #current_host > maintains fragment > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:10]' # > Capybara::Session RackTest #current_url, #current_path, #current_host > redirects to a fragment > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:13]' # > Capybara::Session RackTest #current_url, #current_path, #current_host doesn't > raise exception on a nil current_url > rspec /<>/spec/server_spec.rb:6 # Capybara::Server should spool > up a rack server > rspec /<>/spec/server_spec.rb:15 # Capybara::Server should do > nothing when no server given > rspec /<>/spec/server_spec.rb:21 # Capybara::Server should bind > to the specified host > rspec /<>/spec/server_spec.rb:42 # Capybara::Server should use > specified port > rspec /<>/spec/server_spec.rb:54 # Capybara::Server should use > given port > rspec /<>/spec/server_spec.rb:64 # Capybara::Server should find > an available port > rspec /<>/spec/server_spec.rb:95 # Capybara::Server should > return its #base_url > rspec /<>/spec/server_spec.rb:102 # Capybara::Server should call > #clamp on the puma configuration to ensure that environment is a string > rspec /<>/spec/server_spec.rb:253 # Capybara::Server should > raise an error when there are pending requests > rspec /<>/spec/server_spec.rb:156 # Capybara::Server When > Capybara.reuse_server is true should use the existing server if it already > running > rspec /<>/spec/server_spec.rb:169 # Capybara::Server When > Capybara.reuse_server is true detects and waits for all reused server > sessions pending requests > rspec /<>/spec/server_spec.rb:201 # Capybara::Server When > Capybara.reuse_server is false should not reuse an already running server > rspec /<>/spec/server_spec.rb:214 # Capybara::Server When > Capybara.reuse_server is false detects and waits for only one sessions > pending requests > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-capybara/ruby-capybara_3.36.0+ds-2+rebuild1663007416_amd64-2022-09-12T18:30:17Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019614: ruby-celluloid: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected Timeout::Error, got #
Source: ruby-celluloid Version: 0.17.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-celluloid with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): >expected Timeout::Error, got # `timeout' for Kernel:Module > >Kernel.send(:timeout, timeout_interval) do > ^> with backtrace: > # ./spec/celluloid/mailbox/evented_spec.rb:19:in `block (3 levels) > in ' > # ./spec/celluloid/mailbox/evented_spec.rb:18:in `block (2 levels) > in ' > # ./spec/support/configure_rspec.rb:37:in `block (4 levels) in (required)>' > # ./spec/support/configure_rspec.rb:37:in `block (3 levels) in (required)>' > # ./spec/support/reset_class_variables.rb:9:in > `reset_class_variables' > # ./spec/support/configure_rspec.rb:36:in `block (2 levels) in (required)>' > # ./spec/celluloid/mailbox/evented_spec.rb:18:in `block (2 levels) in > ' > # ./spec/support/configure_rspec.rb:37:in `block (4 levels) in (required)>' > # ./spec/support/configure_rspec.rb:37:in `block (3 levels) in (required)>' > # ./spec/support/reset_class_variables.rb:9:in `reset_class_variables' > # ./spec/support/configure_rspec.rb:36:in `block (2 levels) in (required)>' > > Top 3 slowest examples (8.17 seconds, 46.4% of total time): > Celluloid::Actor timers run every(t) task several times > 5.51 seconds ./spec/celluloid/timer_spec.rb:29 > Celluloid behaves like a Celluloid Actor timers schedules recurring timers > which fire in the future > 1.66 seconds ./spec/shared/actor_examples.rb:964 > Celluloid::Condition times out inside Tasks > 1.01 seconds ./spec/celluloid/condition_spec.rb:80 > > Top 3 slowest example groups: > Celluloid::Actor timers > 5.51 seconds average (5.51 seconds / 1 example) > ./spec/celluloid/timer_spec.rb:28 > Celluloid::Condition > 0.29208 seconds average (2.04 seconds / 7 examples) > ./spec/celluloid/condition_spec.rb:1 > Deprecated Celluloid::Future > 0.26575 seconds average (1.33 seconds / 5 examples) > ./spec/deprecate/future_spec.rb:1 > > Finished in 17.63 seconds (files took 0.23316 seconds to load) > 201 examples, 1 failure, 7 pending > > Failed examples: > > rspec ./spec/celluloid/mailbox/evented_spec.rb:15 # > Celluloid::Mailbox::Evented recovers from timeout exceeded to process mailbox > message > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-celluloid/ruby-celluloid_0.17.3-1+rebuild1663007422_amd64-2022-09-12T18:30:22Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019611: ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
Source: ruby-asset-sync
Version: 2.11.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-asset-sync with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: @yml ||=
> ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
>
> Psych::BadAlias:
> Unknown alias: defaults
> # ./lib/asset_sync/config.rb:165:in `yml'
> # ./lib/asset_sync/config.rb:195:in `load_yml!'
> # ./lib/asset_sync/config.rb:95:in `initialize'
> # ./spec/unit/rackspace_spec.rb:63:in `new'
> # ./spec/unit/rackspace_spec.rb:63:in `block (3 levels) in (required)>'
>
> Finished in 1 second (files took 0.56587 seconds to load)
> 133 examples, 27 failures, 3 pending
>
> Failed examples:
>
> rspec ./spec/unit/asset_sync_spec.rb:105 # AssetSync from yml should default
> AssetSync to enabled
> rspec ./spec/unit/asset_sync_spec.rb:110 # AssetSync from yml should
> configure run_on_precompile
> rspec ./spec/unit/asset_sync_spec.rb:114 # AssetSync from yml should
> configure aws_access_key_id
> rspec ./spec/unit/asset_sync_spec.rb:118 # AssetSync from yml should
> configure aws_secret_access_key
> rspec ./spec/unit/asset_sync_spec.rb:122 # AssetSync from yml should
> configure fog_directory
> rspec ./spec/unit/asset_sync_spec.rb:126 # AssetSync from yml should
> configure fog_region
> rspec ./spec/unit/asset_sync_spec.rb:130 # AssetSync from yml should
> configure path_style
> rspec ./spec/unit/asset_sync_spec.rb:134 # AssetSync from yml should
> configure existing_remote_files
> rspec ./spec/unit/asset_sync_spec.rb:138 # AssetSync from yml should default
> gzip_compression to false
> rspec ./spec/unit/asset_sync_spec.rb:142 # AssetSync from yml should default
> manifest to false
> rspec ./spec/unit/asset_sync_spec.rb:146 # AssetSync from yml should default
> asset_regexps to match regexps
> rspec ./spec/unit/asset_sync_spec.rb:158 # AssetSync from yml, exporting to a
> mobile hybrid development directory should be disabled
> rspec ./spec/unit/google_spec.rb:111 # AssetSync from yml when using S3
> interop API should configure google_storage_access_key_id
> rspec ./spec/unit/google_spec.rb:115 # AssetSync from yml when using S3
> interop API should configure google_storage_secret_access_key
> rspec ./spec/unit/google_spec.rb:119 # AssetSync from yml when using S3
> interop API should not configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:123 # AssetSync from yml when using S3
> interop API should configure fog_directory
> rspec ./spec/unit/google_spec.rb:127 # AssetSync from yml when using S3
> interop API should configure existing_remote_files
> rspec ./spec/unit/google_spec.rb:131 # AssetSync from yml when using S3
> interop API should default gzip_compression to false
> rspec ./spec/unit/google_spec.rb:135 # AssetSync from yml when using S3
> interop API should default manifest to false
> rspec ./spec/unit/google_spec.rb:146 # AssetSync from yml when using service
> account API should configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:150 # AssetSync from yml when using service
> account API should not configure google_storage_secret_access_key
> rspec ./spec/unit/rackspace_spec.rb:66 # AssetSync using Rackspace from yml
> should keep existing remote files
> rspec ./spec/unit/rackspace_spec.rb:70 # AssetSync using Rackspace from yml
> should configure rackspace_username
> rspec ./spec/unit/rackspace_spec.rb:74 # AssetSync using Rackspace from yml
> should configure rackspace_api_key
> rspec ./spec/unit/rackspace_spec.rb:78 # AssetSync using Rackspace from yml
> should configure fog_directory
> rspec ./spec/unit/rackspace_spec.rb:82 # AssetSync using Rackspace from yml
> should configure fog_region
> rspec ./spec/unit/rackspace_spec.rb:86 # AssetSync using Rackspace from yml
> should configure existing_remote_files
>
> Coverage report generated for RSpec to /<>/coverage. 359 / 474
> LOC (75.74%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has
> been detected
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> ./spec/integration/aws_integration_spec.rb ./spec/unit/asset_sync_spec.rb
> ./spec/unit/google_spec.rb ./spec/unit/multi_mime_spec.rb
> ./spec/unit/rackspace_spec.rb ./spec/unit/railsless_spec.rb
> ./spec/unit/storage_spec.rb failed
>
Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
Source: ruby-ahoy-email Version: 1.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-ahoy-email with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require': cannot load such file -- net/smtp (LoadError) > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `block in require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in > `load_dependency' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from /usr/lib/ruby/vendor_ruby/mail.rb:9:in `' > from /usr/lib/ruby/vendor_ruby/mail.rb:3:in `' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `block in require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in > `load_dependency' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from > /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/mail_with_error_handling.rb:4:in > `' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `block in require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in > `load_dependency' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from > /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/base.rb:3:in > `' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `block in require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in > `load_dependency' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in > `require' > from /<>/test/test_helper.rb:21:in `' > from /<>/test/click_test.rb:1:in `require_relative' > from /<>/test/click_test.rb:1:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-ahoy-email/ruby-ahoy-email_1.1.1-2+rebuild1663007340_amd64-2022-09-12T18:29:01Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019609: ruby-activerecord-import: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
m > :85:in > `require' > from /<>/test/import_test.rb:1:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test:sqlite3 > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed. The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-activerecord-import/ruby-activerecord-import_1.2.0-1+rebuild1663007333_amd64-2022-09-12T18:28:54Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019607: redmine: FTBFS with ruby3.1: Could not find gem 'rails (~> 6.1.4.6)' in cached gems or installed locally.
Source: redmine Version: 5.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild redmine with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > debian/rules binary > dh binary --with ruby >dh_update_autotools_config >dh_autoreconf >debian/rules override_dh_auto_configure > make[1]: Entering directory '/<>' > ./debian/check-locales > bundle --local --quiet > `/sbuild-nonexistent` is not a directory. > Bundler will use `/tmp/bundler20220912-3391316-u0d4lg3391316' as your home > directory temporarily. > Could not find gem 'rails (~> 6.1.4.6)' in cached gems or installed locally. > > The source contains the following gems matching 'rails': > * rails-6.1.6.1 > make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 7 The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/redmine/redmine_5.0.0-1+rebuild1663007309_amd64-2022-09-12T18:28:31Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019608: rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq('')
k_alignment_spec.rb:223 # > RuboCop::Cop::Layout::BlockAlignment when variables of a mass assignment > spans several lines accepts end aligned with the variables > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:610 # > RuboCop::Cop::Layout::BlockAlignment when the block is terminated by } > mentions } (not end) in the message > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:78 # > RuboCop::Cop::Layout::BlockAlignment when there is an assignment chain > accepts end aligned with the first variable > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:65 # > RuboCop::Cop::Layout::BlockAlignment when there is an assignment chain > registers an offense for an end aligned with the 2nd variable > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:638 # > RuboCop::Cop::Layout::BlockAlignment when configured to align with > start_of_line errors when do aligned > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:629 # > RuboCop::Cop::Layout::BlockAlignment when configured to align with > start_of_line allows when start_of_line aligned > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:670 # > RuboCop::Cop::Layout::BlockAlignment when configured to align with do errors > when start_of_line aligned > rspec /<>/spec/rubocop/cop/layout/block_alignment_spec.rb:661 # > RuboCop::Cop::Layout::BlockAlignment when configured to align with do allows > when do aligned > rspec /<>/spec/rubocop/cli/cli_autocorrect_spec.rb:885 # > RuboCop::CLI corrects SymbolProc and SpaceBeforeBlockBraces offenses > rspec /<>/spec/rubocop/cli/cli_autocorrect_spec.rb:1029 # > RuboCop::CLI can correct two problems with blocks > rspec /<>/spec/rubocop/cli/cli_autocorrect_spec.rb:1485 # > RuboCop::CLI corrects Style/BlockDelimiters offenses when > specifingLayout/SpaceInsideBlockBraces together > > Randomized with seed 39902 > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --exclude-pattern > spec/rubocop/config_loader_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/rubocop/rubocop_0.89.1+dfsg-3+rebuild1663007326_amd64-2022-09-12T18:28:47Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019606: roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: YAML.load_file config_file
Source: roodi
Version: 5.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild roodi with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: YAML.load_file config_file
>
> Psych::DisallowedClass:
>Tried to load unspecified class: Regexp
> # (eval):2:in `regexp'
> # ./lib/roodi/core/runner.rb:135:in `load_config'
> # ./lib/roodi/core/runner.rb:126:in `load_checks'
> # ./lib/roodi/core/runner.rb:72:in `check'
> # ./lib/roodi/core/runner.rb:81:in `check_content'
> # ./spec/roodi/core/runner_spec.rb:52:in `block (4 levels) in (required)>'
>
> Deprecation Warnings:
>
> Using `should_not` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/roodi/checks/abc_metric_method_check_spec.rb:12:in
> `verify_content_score'.
>
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly
> enable `:should` instead. Called from
> /<>/spec/roodi/core/runner_spec.rb:58:in `block (3 levels) in
> '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 2 deprecation warnings total
>
> Finished in 0.09081 seconds (files took 0.39761 seconds to load)
> 115 examples, 5 failures
>
> Failed examples:
>
> rspec ./spec/roodi/core/runner_spec.rb:7 # Roodi::Core::Runner running
> against a file adds an error if file is not valid ruby
> rspec ./spec/roodi/core/runner_spec.rb:17 # Roodi::Core::Runner running
> against a file checks that one file
> rspec ./spec/roodi/core/runner_spec.rb:24 # Roodi::Core::Runner running
> against a directory checks all files in that directory recursively
> rspec ./spec/roodi/core/runner_spec.rb:31 # Roodi::Core::Runner running
> without specifying files or directory checks all files in that directory
> recursively
> rspec ./spec/roodi/core/runner_spec.rb:43 # Roodi::Core::Runner configuration
> given a custom config file uses check from it
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> spec/roodi/checks/abc_metric_method_check_spec.rb
> spec/roodi/checks/assignment_in_conditional_check_spec.rb
> spec/roodi/checks/case_missing_else_check_spec.rb
> spec/roodi/checks/class_line_count_check_spec.rb
> spec/roodi/checks/class_name_check_spec.rb
> spec/roodi/checks/class_variable_check_spec.rb
> spec/roodi/checks/control_coupling_check_spec.rb
> spec/roodi/checks/core_method_override_check_spec.rb
> spec/roodi/checks/cyclomatic_complexity_block_check_spec.rb
> spec/roodi/checks/cyclomatic_complexity_method_check_spec.rb
> spec/roodi/checks/empty_rescue_body_check_spec.rb
> spec/roodi/checks/for_loop_check_spec.rb
> spec/roodi/checks/method_line_count_check_spec.rb
> spec/roodi/checks/method_name_check_spec.rb
> spec/roodi/checks/module_line_count_check_spec.rb
> spec/roodi/checks/module_name_check_spec.rb
> spec/roodi/checks/npath_complexity_method_check_spec.rb
> spec/roodi/checks/parameter_number_check_spec.rb
> spec/roodi/core/runner_spec.rb spec/roodi_task_spec.rb failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/roodi/roodi_5.0.0-4+rebuild1663007308_amd64-2022-09-12T18:28:29Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
Bug#1019605: feed2imap: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
/test/tc_config.rb:109:in `new' > /<>/test/tc_config.rb:109:in `test_integer_as_name' > 106: > 107: def test_integer_as_name > 108: sio = StringIO.new CONFINTNAME > => 109: conf = F2IConfig.new(sio) > 110: assert_equal "10", conf.feeds.first.name > 111: end > 112: > === > .E > === > Error: test_url_array(ConfigTest): Psych::BadAlias: Unknown alias: target > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:430:in `visit_Psych_Nodes_Alias' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `block in register_empty' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `each' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `register_empty' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:146:in > `visit_Psych_Nodes_Sequence' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:345:in `block in revive_hash' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each_slice' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `revive_hash' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:167:in > `visit_Psych_Nodes_Mapping' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `block in register_empty' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `each' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `register_empty' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:146:in > `visit_Psych_Nodes_Sequence' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:345:in `block in revive_hash' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each_slice' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `revive_hash' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:167:in > `visit_Psych_Nodes_Mapping' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:318:in > `visit_Psych_Nodes_Document' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit' > /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept' > /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept' > /usr/lib/ruby/3.1.0/psych.rb:335:in `safe_load' > /usr/lib/ruby/3.1.0/psych.rb:370:in `load' > /<>/lib/feed2imap/config.rb:43:in `initialize' > /<>/test/tc_config.rb:103:in `new' > /<>/test/tc_config.rb:103:in `test_url_array' > 100: > 101: def test_url_array > 102: sio = StringIO::new CONFARRAYTARGET > => 103: conf = F2IConfig::new(sio) > 104: assert_equal "/tmp/Maildir/feed1", conf.feeds.first.folder > 105: end > 106: > === > > Finished in 0.016493688 seconds. > --- > 14 tests, 32 assertions, 0 failures, 2 errors, 0 pendings, 0 omissions, 0 > notifications > 85.7143% passed > --- > 848.81 tests/s, 1940.14 assertions/s > ERROR: Test "ruby3.1" failed. The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/feed2imap/feed2imap_1.3.1-1+rebuild1663007227_amd64-2022-09-12T18:27:07Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019604: bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
.: (0.001951) > TestJtokenizer: > test_bigram:.: (0.003743) > TestMarkSpamSubject: > test_multi_subject: .: (0.006381) > test_no_body: .: (0.014042) > test_no_boundary: .: (0.006012) > TestMbox: > test_with_mbox: .: (0.002450) > test_without_mbox: .: (0.002033) > TestMultipleInstances: > test_by_jtokenizer: .: (0.004416) > test_by_mbox: .: (0.008279) > TestPlainTextParser: > test_folding: .: (0.003153) > test_iso_8895_1:.: (0.001718) > TestTokenizerOptionCombination: > test_all: .: (3.166783) > > Finished in 3.394784289 seconds. > --- > 47 tests, 116 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 > notifications > 97.8723% passed > --- > 13.84 tests/s, 34.17 assertions/s > rake aborted! > Command failed with status (1): [/usr/bin/ruby3.1 test.rb --verbose...] > /<>/debian/ruby-tests.rake:7:in `block (2 levels) in (required)>' > /<>/debian/ruby-tests.rake:6:in `block in ' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed. The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/bsfilter/bsfilter_1.0.19-3+rebuild1663007202_amd64-2022-09-12T18:26:43Z.build To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or ir the transition has alraedy started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1019603: asciidoctor: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
F...
>
> Finished in 3.096380s, 844.8576 runs/s, 3008.0289 assertions/s.
>
> 1) Failure:
> Minitest::Test::TestHelpers::TestTypeResolution#test_should_not_resolve_class_if_not_in_scope
> [/<>/test/helpers_test.rb:127]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: Asciidoctor::Extensions::String"
> +"Could not resolve class for name: Asciidoctor::Extensions::String
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 2) Failure:
> Minitest::Test::TestHelpers::TestTypeResolution#test_should_raise_exception_if_cannot_find_class_for_name
> [/<>/test/helpers_test.rb:79]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: InvalidModule::InvalidClass"
> +"Could not resolve class for name: InvalidModule::InvalidClass
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 3) Failure:
> Minitest::Test::TestHelpers::TestTypeResolution#test_should_raise_exception_if_class_not_found_in_scope
> [/<>/test/helpers_test.rb:97]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: Asciidoctor::Extensions::String"
> +"Could not resolve class for name: Asciidoctor::Extensions::String
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 4) Failure:
> Minitest::Test::TestHelpers::TestTypeResolution#test_should_raise_exception_if_name_resolves_to_module
> [/<>/test/helpers_test.rb:106]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: Asciidoctor::Extensions"
> +"Could not resolve class for name: Asciidoctor::Extensions
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 5) Failure:
> Minitest::Test::TestHelpers::TestTypeResolution#test_should_raise_exception_if_constant_name_is_invalid
> [/<>/test/helpers_test.rb:88]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: foobar"
> +"Could not resolve class for name: foobar
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 6) Failure:
> Minitest::Test::TestExtensions::TestRegister#test_should_raise_NameError_if_extension_class_cannot_be_resolved_from_string
> [/<>/test/extensions_test.rb:355]:
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -"Could not resolve class for name: foobar"
> +"Could not resolve class for name: foobar
> +
> +raise ::NameError, %(Could not resolve class for name:
> \#{qualified_name})
> +^"
>
>
> 2616 runs, 9314 assertions, 6 failures, 0 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w -I"lib:test"
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
> "test/api_test.rb" "test/attribute_list_test.rb" "test/attributes_test.rb"
> "test/blocks_test.rb" "test/converter_test.rb" "test/document_test.rb"
> "test/extensions_test.rb" "test/helpers_test.rb" "test/invoker_test.rb"
> "test/links_test.rb" "test/lists_test.rb" "test/logger_test.rb"
> "test/manpage_test.rb" "test/options_test.rb" "test/paragraphs_test.rb"
> &qu
Bug#1015327: Starting ruby3.1 transition: important bugs now marked as serious
severity 1015305 serious severity 1015309 serious severity 1015310 serious severity 1015322 serious severity 1015327 serious severity 1015328 serious severity 1015329 serious severity 1015334 serious thanks Hi, We are about to start the ruby3.1 transition. I will coordinate this with the release team, and ruby3.1 should be enabled in unstable soon. Before that, you can test things by installing ruby-all-dev from experimental. The following bugs are the current blockers, so the most important ones to be fixed. If you can, please help by fixing them: #1015305 puma: FTBFS: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1015305 #1015309 ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: actual = YAML.load(regexp.to_yaml) https://bugs.debian.org/1015309 #1015310 ruby-dataobjects-mysql: FTBFS: chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': Permission denied https://bugs.debian.org/1015310 #1015322 ruby-kyotocabinet: FTBFS: kccommon.h:19:8: error: expected identifier or ‘(’ before string constant https://bugs.debian.org/1015322 #1015327 ruby-mysql2: FTBFS: ERROR: Test "ruby3.0" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory https://bugs.debian.org/1015327 #1015328 ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1015328 #1015329 ruby-prof: FTBFS: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1015329 #1015334 ruby-stackprof: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1015334 signature.asc Description: PGP signature
Bug#1005442: marked as pending in ruby-em-http-request
Control: tag -1 pending Hello, Bug #1005442 in ruby-em-http-request reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-em-http-request/-/commit/7a00580eb46b9fa5be957b509451b9cc54ae4efd debian/ruby-tests.rake: exclude broken tests Closes: #1005442, #1006985 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005442
Bug#1006026: marked as pending in ruby-axiom-types
Control: tag -1 pending Hello, Bug #1006026 in ruby-axiom-types reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-axiom-types/-/commit/796f33353513fe46e7b04af6536182910111b086 debian/ruby-tests.rake: test class finalizer separately If this gets run together with the rest of the tests, it will fail randomly at approximately 60% of the time (I assume based on the test ordering). Closes: #1006026 Gbp-Dch: full (this message was generated automatically) -- Greetings https://bugs.debian.org/1006026
Bug#1006026: ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations.
Control: retitle -1 ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations. I tried this locally and couldn't reproduce twice in row, first on my main system, then with sbuild. I then tried 10 times in a row, and got a 60% failure rate. Tried again 20 times, then 55% failure rate. I tried debugging this with the upstream sources from git and ruby-standalone + bundler, but the upstream tree has broken dependencies and I lost my patience. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#1017017: regression: lxc virt backend cannot attach to container
Package: autopkgtest Version: 5.23 Severity: grave Justification: renders package unusable This was first noticed by a salsa-ci user: https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/270#note_328972 I then tested locally, and reproduced the same issue with the snapshot I was running from git: 8<8<8<- autopkgtest [08:53:39]: starting date: 2022-08-11 autopkgtest [08:53:39]: version 5.23~terceiro0 autopkgtest [08:53:39]: host lemur; command line: /usr/bin/autopkgtest --output-dir=/tmp/autopkgtest-HicmTIAeQ --no-built-binaries --apt-upgrade /home/terceiro/src/debian/ruby-team/build-area/chake_0.82-1_all.deb . -- lxc --sudo autopkgtest-unstable-amd64 : failure: timed out waiting for testbed to start: lxc-attach: autopkgtest-lxc-jdtdzt: ../src/lxc/attach.c: get_attach_context: 405 Connection refused - Failed to get init pid lxc-attach: autopkgtest-lxc-jdtdzt: ../src/lxc/attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context autopkgtest [08:55:45]: ERROR: testbed failure: unexpected eof from the testbed 8<8<8<- I get the same with 5.23 from unstable. Reverting back to 5.22 fixed things. I bisected locally and found out that 6ca1a0a5350026fe32b67c0ef4a64481ede83ea0 is the first bad commit commit 6ca1a0a5350026fe32b67c0ef4a64481ede83ea0 Author: Simon McVittie Date: Mon Aug 8 10:19:20 2022 +0100 virt-lxc, virt-lxd: Factor out code to wait for container to boot This is duplicated between the two, and soon we'll want it for podman as well. Signed-off-by: Simon McVittie Makefile | 2 + lib/VirtSubproc.py| 99 ++- lib/await-sysv-boot | 30 ++ lib/detect-init-system| 15 +++ tests/shellcheck | 2 + virt/autopkgtest-virt-lxc | 27 + virt/autopkgtest-virt-lxd | 26 + 7 files changed, 149 insertions(+), 52 deletions(-) create mode 100755 lib/await-sysv-boot create mode 100755 lib/detect-init-system which makes sense. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.5.2 ii libdpkg-perl1.21.9 ii procps 2:3.3.17-7+b1 ii python3 3.10.5-3 ii python3-debian 0.1.46 Versions of packages autopkgtest recommends: ii autodep8 0.26 ii fakeroot 1.29-1 Versions of packages autopkgtest suggests: ii docker.io20.10.14+dfsg1-1+b1 ii fakemachine 0.0~git20210901.fc48786-1+b1 ii lxc 1:5.0.1-1 pn lxd ii ovmf 2022.05-2 pn ovmf-ia32 ii podman 4.0.3+ds1-1 pn python3-distro-info ii qemu-efi-aarch64 2022.05-2 ii qemu-efi-arm 2022.05-2 ii qemu-system 1:7.0+dfsg-7 ii qemu-utils 1:7.0+dfsg-7 ii schroot 1.6.12-1 ii util-linux 2.38.1-1 ii vmdb20.26-1 -- no debconf information signature.asc Description: PGP signature
Bug#1006471: marked as pending in ruby
Control: tag -1 pending Hello, Bug #1006471 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby/-/commit/5dbe7a8f795d2427379cb76c6fd64de69f963cfb debian/rules: ensure rbconfig.rb is reproducible regardless of usr-merge Closes: #1006471 Signed-off-by: Vagrant Cascadian Signed-off-by: Antonio Terceiro (this message was generated automatically) -- Greetings https://bugs.debian.org/1006471
Bug#1006471: ruby3.0: reproducible builds: embeds path to various binaries
Control: tag -1 + pending On Wed, Jul 27, 2022 at 02:52:47PM +0100, Simon McVittie wrote: > Is the Ruby build intentionally putting EGREP into rbconfig.rb for use by > some other component, or is it just populating that file with everything > that Autoconf happens to have discovered, on the off chance that it > might become necessary at some point? If the latter, then that seems > like it will cause unpredictable action-at-a-distance if Autoconf stops > needing to discover some particular thing (for instance if Autoconf's > maintainers decide that they are only going to support systems where > the first grep in PATH is POSIX.1-2001 compliant, and stop checking for a > possibly-better-quality grep elsewhere). The later. Thanks for the explanation. This has already been fixed for ruby3.1, and is fixed in git for ruby3.0. signature.asc Description: PGP signature
Bug#1006471: ruby3.0: reproducible builds: embeds path to various binaries
Control: clone -1 -2 Control: reassign -2 src:ruby3.1 Control: retitle -2 ruby3.1: reproducible builds: embeds path to various binaries Hi, On Sun, Jul 17, 2022 at 12:04:45PM +0100, Simon McVittie wrote: > Control: severity -1 serious > > On Fri, 25 Feb 2022 at 15:26:51 -0800, Vagrant Cascadian wrote: > > The paths to various binaries, which differs on a usrmerge > > vs. non-usrmerge system, are embedded in rbconfig.rb: > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/ruby3.0.html > > > > /usr/lib/x86_64-linux-gnu/ruby/3.0.0/rbconfig.rb > > > > CONFIG["EGREP"]·=·"/bin/grep·-E" > > vs. > > CONFIG["EGREP"]·=·"/usr/bin/grep·-E" > > If these CONFIG variables are used for something at runtime, then this > will become a practical problem as soon as Debian starts using merged-/usr > buildds. The problem scenario is: > > - ruby3.0 is built on a merged-/usr buildd > - /usr/bin/grep is recorded in rbconfig.rb > - this build of ruby3.0 is installed on a non-merged-/usr system during > the upgrade from Debian 11 to Debian 12 > - whatever feature uses CONFIG["EGREP"] will not work, because > non-merged-/usr systems only have /bin/grep > > Technical Committee resolution > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110 recommends > that this class of bug is treated as release-critical, so I'm raising the > severity of this bug report. > > If none of the affected CONFIG variables are actually used for anything > on installed systems, then the severity of this bug can be downgraded > to non-RC (but it would be better to fix it anyway, because reproducible > builds are a useful goal for other reasons). Those variables are read from config.status during the builds. Maybe this should be fixed centrally in autoconf instead? > > Patch attached which passes variables to configure to use the > > non-usrmerge locations, as usrmerge installations typically have > > compatibility symlinks, but not vice-versa. > > To clarify: in Debian, merged-/usr installations are *guaranteed* to > have these compatibility symlinks. The patch looks appropriate to me, > although I have not tested it. Sure. signature.asc Description: PGP signature
Bug#1015340: xapian-bindings: FTBFS: dh_install: error: missing files, aborting
Source: xapian-bindings Version: 1.4.20-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild xapian-bindings with ruby3.1 enabled, the build failed. The failure has no relation to ruby, and I can also reproduce this on a clean sbuild build with unstable only. Relevant part of the build log (hopefully): > make[7]: Entering directory '/<>/debian/build/java/java' > rm -f > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/jni/libxapian_jni.la > make[7]: Leaving directory '/<>/debian/build/java/java' > make[6]: Leaving directory '/<>/debian/build/java/java' > make[5]: Leaving directory '/<>/debian/build/java/java' > make[4]: Leaving directory '/<>/debian/build/java/java' > make[3]: Leaving directory '/<>/debian/build/java' > make[2]: Leaving directory '/<>/debian/build/java' > # Reads the '*.install' files to decide where to install everything. > dh_install --sourcedir=debian/tmp > dh_install: warning: Cannot find (any matches for) > "usr/lib/python3*/*-packages/xapian/*.so" (tried in debian/tmp, debian/tmp) > > dh_install: warning: python3-xapian missing files: > usr/lib/python3*/*-packages/xapian/*.so > dh_install: warning: Cannot find (any matches for) > "usr/lib/python3*/*-packages/xapian/*.py" (tried in debian/tmp, debian/tmp) > > dh_install: warning: python3-xapian missing files: > usr/lib/python3*/*-packages/xapian/*.py > dh_install: error: missing files, aborting > make[1]: *** [debian/rules:363: override_dh_auto_install] Error 25 The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/xapian-bindings_1.4.20-1+rebuild1658134795_amd64.log To reproduce this, you need to install ruby-all-dev >= 1:3.0+2 (in experimental). If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1015327: ruby-mysql2: FTBFS: ERROR: Test "ruby3.0" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
> > shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf > > You can also try to start the mysqld daemon with: > > shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & > > and use the command line tool /usr/bin/mariadb > to connect to the mysql database and look at the grant tables: > > shell> /usr/bin/mysql -u root mysql > mysql> show tables; > > Try 'mysqld --help' if you have problems with paths. Using > --general-log gives you a log in /tmp/tmp.YafTwmGWe1 that may be helpful. > > The latest information about mysql_install_db is available at > https://mariadb.com/kb/en/installing-system-tables-mysql_install_db > You can find the latest source at https://downloads.mariadb.org and > the maria-discuss email list at https://launchpad.net/~maria-discuss > > Please check all of the above before submitting a bug report > at https://mariadb.org/jira > > rake aborted! > Command failed with status (1): [./debian/start_mysqld_and_run.sh ruby3.0 > -...] > /<>/debian/ruby-tests.rake:6:in `block in ' > /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in ` (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/ruby-mysql2_0.5.3-3.1+rebuild1658134272_amd64.log To reproduce this, you need to install ruby-all-dev >= 1:3.0+2 (in experimental). If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature
Bug#1011443: faker,ruby-faker: error when trying to install together
On Tue, Jul 05, 2022 at 06:44:15PM +0200, Timo Röhling wrote: > On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann wrote: > > Package: faker,ruby-faker > > Severity: serious > > Tags: sid bookworm > > User: trei...@debian.org > > Usertags: edos-file-overwrite > > Control: found -1 0.9.3-0.1 > > Control: found -1 2.20.0-1 > > > > [...] > > Here is a list of files that are known to be shared by both packages > > (according to the Contents file for sid/amd64, which may be > > slightly out of sync): > > > > /usr/bin/faker > > > > This bug is assigned to both packages. If you, the maintainers of > > the two packages in question, have agreed on which of the packages will > > resolve the problem please reassign the bug to that package. > I'm posting to d-devel because I failed to make contact with the > Ruby Team directly: > > ruby-faker primarily ships a Ruby module while faker's sole purpose > is the faker executable, so I believe ruby-faker should yield. > There are two reverse dependencies: > > - ruby-devise-two-factor builds fine without /usr/bin/faker in > ruby-faker > > - ruby-omniauth-openid-connect FTBFS for unrelated reasons with and > wihout /usr/bin/faker > > If the Ruby Team agrees with my analysis, I'd appreciate it if > someone could upload a fixed version (I am not a team member). I just did that. Remember that you need to add Breaks:/Replaces: on your package for upgrades to work. signature.asc Description: PGP signature
Bug#1005472: marked as pending in typeshed
Control: tag -1 pending Hello, Bug #1005472 in typeshed 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/python-team/packages/typeshed/-/commit/a675b1c0cd5cfdef67fcc9c6ac3d95f0ce3f3903 debian/install_stubs.py: remove --system option Closes: #1005472 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005472
Bug#992786: passenger uses many vendored libraries
Control: severity -1 important Hi, On Mon, Aug 23, 2021 at 03:00:16PM +0300, Adrian Bunk wrote: > Source: passenger > Severity: serious > > passenger-5.0.30/src/cxx_supportlib/vendor-copy: > adhoc_lve.h libcurl libuv nghttp2 utf8 utf8.h > > passenger-5.0.30/src/cxx_supportlib/vendor-modified: > SmallVector.h jsoncpp modp_b64.cpp modp_b64_data.h > boost libevmodp_b64.hpsg_sysqueue.h > > passenger-6.0.10/src/cxx_supportlib/vendor-copy: > adhoc_lve.h libuv utf8 utf8.h websocketpp > > passenger-6.0.10/src/cxx_supportlib/vendor-modified: > boostlibev modp_b64.h modp_b64_strict_aliasing.cpp > jsoncpp modp_b64.cpp modp_b64_data.h psg_sysqueue.h > > > The problem is that these vendored copies seem to actually be used. > > Does for example CVE-2021-22918 in libuv1 need fixing in passenger? 6.0.13+ds-1 drops the embedded copies of both libuv and libev, who seem to be the most high-profile libraries; and it's now actually possible to build passenger against system-provided copies of those. There is still an embeded copy of boost, but that's modified from upstream boost in a way that the code does not build about system boost. Ideally we would want to drop all of the other embeded copies, but realistically that would involve a amount of work that is not available at the moment. Because this is still a relevant issue, but IMO not worth removing passenger because of it, I am downgrading this bug to important. signature.asc Description: PGP signature
Bug#1010740: ruby-bootsnap: FTBFS on ppc64el: test suite hangs
Source: ruby-bootsnap Version: 1.9.3-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source Forwarded: https://github.com/Shopify/bootsnap/issues/415 The ruby-bootsnap test suite hangs forever on ppc64el. This has been reported upstream at the link above, and happens on both the version in testing and the one in unstable. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#1010061: [git-buildpackage/master] tests: fix input data to create-remote-repo tests
tag 1010061 pending thanks Date: Sat Apr 23 10:08:16 2022 -0300 Author: Antonio Terceiro Commit ID: 6733ab9603773281016812c34604aa3358fbdc34 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=6733ab9603773281016812c34604aa3358fbdc34 Patch URL: https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=6733ab9603773281016812c34604aa3358fbdc34 tests: fix input data to create-remote-repo tests Closes: #1010061
Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues
Source: git-buildpackage Version: 0.9.25 Severity: serious Tags: patch ftbfs Justification: fails to build from source Dear Maintainer, git-buildpackage currently fails to build due to a few issues. I tried both the source currently in testing/unstable, and the master branch from the git repository. There are a few different issues: - pydoctor changed its configuration file format, and there is needed porting. - The tests make assumptions about the global git configuration (and fail for me on my system). - A few parts of the Debian packaging assume the current python3 version ends with single digit (python3.?), what breaks now that python 3.10 is the default. - the tests for create-remote-repo seem to be using slightly broken input data. I'm not sure how this worked before. I'm including patches for all of the above issues, in that order. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled From d77682bf92b2c486ef1a35e5af13411129583fb1 Mon Sep 17 00:00:00 2001 From: Antonio Terceiro Date: Sat, 23 Apr 2022 09:23:43 -0300 Subject: [PATCH 1/3] docs: port build system to newer pydoctor According to https://pydoctor.readthedocs.io/en/latest/help.html, the command line and configuration parsing has changed in an incompatible way. These changes fix the documentation build for me, but are probably backwards-incompatible with older versions of pydoctor. --- .pydoctor.cfg | 4 Makefile | 2 +- pydoctor.ini | 4 3 files changed, 5 insertions(+), 5 deletions(-) delete mode 100644 .pydoctor.cfg create mode 100644 pydoctor.ini diff --git a/.pydoctor.cfg b/.pydoctor.cfg deleted file mode 100644 index ede8e513.. --- a/.pydoctor.cfg +++ /dev/null @@ -1,4 +0,0 @@ -projectname: git-buildpackage -projecturl: https://honk.sigxcpu.org/piki/projects/git-buildpackage/ -htmloutput: build/apidocs -packages: gbp,tests/doctests/ diff --git a/Makefile b/Makefile index c94fa6c2..618f1a18 100644 --- a/Makefile +++ b/Makefile @@ -27,6 +27,6 @@ docs: apidocs: mkdir -p build - pydoctor -v --config=.pydoctor.cfg + pydoctor -v gbp tests/doctests/ .PHONY: docs diff --git a/pydoctor.ini b/pydoctor.ini new file mode 100644 index ..a9bd0215 --- /dev/null +++ b/pydoctor.ini @@ -0,0 +1,4 @@ +[pydoctor] +project-name = git-buildpackage +project-url = https://honk.sigxcpu.org/piki/projects/git-buildpackage/ +html-output = build/apidocs -- 2.35.1 From a627139e5ac73a65f99a970981063bc0e709f4df Mon Sep 17 00:00:00 2001 From: Antonio Terceiro Date: Sat, 23 Apr 2022 09:37:41 -0300 Subject: [PATCH 2/3] tests: set HOME to an unexisting directory The test suite contains several assumptions about the global git configuration, including but not limited to the default branch name being `master`. By running the tests against a unexisting HOME, git will not load the user configuration and instead use all the git defaults. --- Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile b/Makefile index 618f1a18..db5ad88e 100644 --- a/Makefile +++ b/Makefile @@ -9,6 +9,7 @@ all+net: $(MAKE) GBP_NETWORK_TESTS=1 all test: + export HOME=/nonexisting; \ export GIT_AUTHOR_NAME="Gbp Tests"; \ export GIT_AUTHOR_EMAIL=te...@example.com; \ export GIT_COMMITTER_NAME=$$GIT_AUTHOR_NAME; \ -- 2.35.1 From 2fae160d990992a1273b713778ee6928646a Mon Sep 17 00:00:00 2001 From: Antonio Terceiro Date: Sat, 23 Apr 2022 09:42:14 -0300 Subject: [PATCH 3/3] debian/rules: fix build with python3.10 as default --- debian/git-buildpackage-rpm.install | 10 ++-- debian/git-buildpackage.install | 72 ++--- debian/not-installed| 14 +++--- debian/rules| 2 +- 4 files changed, 49 insertions(+), 49 deletions(-) diff --git a/debian/git-buildpackage-rpm.install b/debian/git-buildpackage-rpm.install index 503e495a..f79d4f17 100644 --- a/debian/git-buildpackage-rpm.install +++ b/debian/git-buildpackage-rpm.install @@ -1,6 +1,6 @@ usr/bin/gbp-builder-mock /usr/share/git-buildpackage/ -usr/lib/python3.?/dist-packages/gbp/rpm usr/lib/python3/dist-packages/gbp/ -usr/lib/python3.?//dist-packages/gbp/scripts/import_srpm.py usr/lib/python3/dist-packages/gbp/scripts/ -usr/lib/python3.?/dist-packages/gbp/scripts/pq_rpm.py usr/lib/python3/dist-packages/gbp/scripts/ -usr/lib/python3.?/dist-packages/gbp/scripts/buildpackage_rpm.py usr/lib/python3/dist-packages/gbp/scripts/ -usr/lib/python3.?/dist-packages/gbp/scripts/rpm_ch.py usr/lib/python3/dist-packages/gbp/scripts
Bug#1009374: podman: fails to install: unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory
On Tue, Apr 12, 2022 at 02:33:50PM -0300, Antonio Terceiro wrote: > Package: podman > Version: 4.0.1+ds1-3 > Severity: serious > Justification: fails to install > > I wanted to try podman 4.0 from experimental, but I can't install it: > This is on a testing machine, with unstable and experimental available, > but with testing at a higher priority: > > 8<8<8<- > $ sudo LANG=C apt install -t experimental -qy podman > Reading package lists... > Building dependency tree... > Reading state information... > Suggested packages: > containers-storage > The following packages will be upgraded: > podman > 1 upgraded, 0 newly installed, 0 to remove and 306 not upgraded. > Need to get 0 B/10.5 MB of archives. > After this operation, 3781 kB of additional disk space will be used. > (Reading database ... 774204 files and directories currently installed.) > Preparing to unpack .../podman_4.0.1+ds1-3_amd64.deb ... > Unpacking podman (4.0.1+ds1-3) over (3.4.4+ds1-1) ... > dpkg: error processing archive > /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack): > unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file > or directory > /usr/bin/deb-systemd-helper: error: unable to read podman.socket > Errors were encountered while processing: > /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > 8<8<8<- This is because podman is shipping both /lib/systemd/user/podman.socket and /usr/lib/systemd/user/podman.socket: $ dpkg --contents podman_4.0.1+ds1-3_amd64.deb | grep socket -rw-r--r-- root/root 176 2022-02-23 23:41 ./lib/systemd/system/podman.socket -rw-r--r-- root/root 176 2022-03-06 19:16 ./lib/systemd/user/podman.socket -rw-r--r-- root/root 176 2022-02-23 23:41 ./usr/lib/systemd/user/podman.socket You can either ship one of the other, because if /lib is a symlink to /usr/lib, one will overwrite the other. Indeed, If I revert the test VM to unmerged-usr filesystem, then podman installs just fine. I'm pushing a change (commit 699e6f68cd) that fixes this, I hope the maintainers don't mind. signature.asc Description: PGP signature
Bug#1009374: marked as pending in libpod
Control: tag -1 pending Hello, Bug #1009374 in libpod 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/libpod/-/commit/699e6f68cd633dd6f19c0e04e037608856b7b159 Stop installing systemd socket units under /usr/lib debian/rules already installs the system support files in override_dh_auto_install using the upstream build system (make install.systemd), there is no need to also keep this ones here (they get installed automatically by debhelper, but get under /usr/lib which is Wrong™ for now). Closes: #1009374 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009374
Bug#1009374: podman: fails to install: unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory
Package: podman Version: 4.0.1+ds1-3 Severity: serious Justification: fails to install I wanted to try podman 4.0 from experimental, but I can't install it: This is on a testing machine, with unstable and experimental available, but with testing at a higher priority: 8<8<8<- $ sudo LANG=C apt install -t experimental -qy podman Reading package lists... Building dependency tree... Reading state information... Suggested packages: containers-storage The following packages will be upgraded: podman 1 upgraded, 0 newly installed, 0 to remove and 306 not upgraded. Need to get 0 B/10.5 MB of archives. After this operation, 3781 kB of additional disk space will be used. (Reading database ... 774204 files and directories currently installed.) Preparing to unpack .../podman_4.0.1+ds1-3_amd64.deb ... Unpacking podman (4.0.1+ds1-3) over (3.4.4+ds1-1) ... dpkg: error processing archive /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack): unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory /usr/bin/deb-systemd-helper: error: unable to read podman.socket Errors were encountered while processing: /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) 8<8<8<- I can reproduce the same exact issue when installing podman from experimental on a clean testing VM. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman depends on: ii conmon 2.0.25+ds1-1.1 ii containernetworking-plugins 1.1.0+ds1-1 ii crun 0.17+dfsg-1.1 ii golang-github-containers-common 0.47.2+ds1-1 ii init-system-helpers 1.62 ii libc62.33-7 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.16.0-1.2 ii libseccomp2 2.5.3-2 ii runc 1.1.1+ds1-1 Versions of packages podman recommends: ii buildah 1.24.1+ds1-1 ii catatonit 0.1.7-1 ii fuse-overlayfs1.8.2-1 ii golang-github-containernetworking-plugin-dnsname 1.3.1+ds1-2 ii slirp4netns 1.0.1-2 ii tini 0.19.0-1 ii uidmap1:4.11.1+dfsg1-2 Versions of packages podman suggests: pn containers-storage ii docker-compose 1.29.2-1 ii iptables1.8.7-1 -- no debconf information -- debsums errors found: debsums: missing file /usr/lib/systemd/user/podman.socket (from podman package) signature.asc Description: PGP signature
Bug#994456: now also FTBFS
On Fri, 11 Mar 2022 19:17:43 +0100 Paul Gevers wrote: > severity 994456 serious > tags 994456 ftbfs > thanks > > Now also causing FTBFS during the ruby2.7 removal transition. Testing this locally, the tests fail randomly aproximately 10% of the times like this: 8<8<8<- Failure: StackProfTest#test_cputime [/tmp/autopkgtest.t74Yoq/build.KKC/real-tree/test/test_stackprof.rb:83]: Expected # encoding: ASCII-8BIT #valid: true "Integer#times" to include "StackProfTest#math". 8<8<8<- signature.asc Description: PGP signature
Bug#1006352: marked as pending in bsfilter
Control: tag -1 pending Hello, Bug #1006352 in bsfilter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/bsfilter/-/commit/eaac70e378ef4d16867d71e7dcdaf60076277be8 Add dependency on ruby-sdbm Closes: #1006352 (this message was generated automatically) -- Greetings https://bugs.debian.org/1006352
Bug#1006352: bsfiltger: "Cannot load such file -- sdbm (LoadError)"
On Thu, Feb 24, 2022 at 10:51:16AM +0900, YABUKI Yukiharu wrote: > Package: bsfilter > Version: 1:1.0.19-2.1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Due to ruby transition, ruby could not load sdbm module. > > I use bsfilter which classifies spam mail. > > ``` > $ bsfilter > :85:in > `require': cannot load such file -- sdbm (LoadError) > Did you mean? dbm > from > :85:in > `require' > from /usr/bin/bsfilter:3106:in `get_options' > from /usr/bin/bsfilter:3262:in `setup' > from /usr/bin/bsfilter:3413:in `' > ``` Yes, `sdbm` has been removed from the standard library. Thanks for the bug report, since bsfilter has no automated tests (otherwise we would have caught this earlier). I just uploaded a standalone ruby-sdbm package to NEW now, and will upload a bsfilter update with the right dependency as soon as that's in the archive. signature.asc Description: PGP signature
Bug#1006547: diaspora-installer: incompatible with ruby3.0
Source: diaspora-installer Version: 0.7.15.0+debian1 Severity: serious Tags: upstream Justification: makes the package unsuitable After ruby-defaults switched to ruby3.0 as default, diaspora-installer started failing its autopkgtest. The failure looks like this: 8<8<8<- Installing gems with rubygems ... [DEPRECATED] The `--frozen` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local frozen 'true'`, and stop using this flag [DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local path 'vendor/bundle'`, and stop using this flag [DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'development test'`, and stop using this flag [DEPRECATED] The `--with` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local with 'postgresql'`, and stop using this flag [DEPRECATED] Your lockfile contains a single rubygems source section with multiple remotes, which is insecure. Make sure you run `bundle install` in non frozen mode and commit the result to make your lockfile secure. Fetching gem metadata from https://gems.diasporafoundation.org/.. Fetching gem metadata from https://rubygems.org/... Your bundle is locked to diaspora_federation-rails (0.2.6) from rubygems repository https://gems.diasporafoundation.org/, https://rubygems.org/ or installed locally, but that version can no longer be found in that source. That means the author of diaspora_federation-rails (0.2.6) has removed it. You'll need to update your bundle to a version other than diaspora_federation-rails (0.2.6) that hasn't been removed in order to install. dpkg: error processing package diaspora-installer (--configure): installed diaspora-installer package post-installation script subprocess returned error exit status 7 dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on diaspora-installer; however: Package diaspora-installer is not configured yet. 8<8<8<- I went to investigate inside a testbed, by copy the diaspora source that was downloaded into /tmp, and running `bundle` by hand from there. Then I get this: 8<8<8<- diaspora@autopkgtest-lxc-kiettk:/$ cp -r /var/cache/diaspora-installer/diaspora-0.7.15.0 /tmp/d diaspora@autopkgtest-lxc-kiettk:/$ cd /tmp/d diaspora@autopkgtest-lxc-kiettk:/tmp/d$ bundle Bundler 2.3.5 is running, but your lockfile was generated with 1.17.3. Installing Bundler 1.17.3 and restarting using that version. Fetching gem metadata from https://rubygems.org/. Fetching bundler 1.17.3 Installing bundler 1.17.3 /tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:29: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. [ this warning repeated *a lot* of times ] Fetching gem metadata from https://gems.diasporafoundation.org/.. Fetching gem metadata from https://rubygems.org/./tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:118: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. /tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:118: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. [ this warning repeated *a lot* of times ] Fetching gem metadata from https://gems.diasporafoundation.org/.. diaspora_federation-0.2.6 requires ruby version ~> 2.1, which is incompatible with the current version, ruby 3.0.2p107 8<8<8<- I went looking into github, and saw that there were a new release of diaspora, 0.7.16.0, that pulled diaspora_federation 0.2.7. I though that could resolve the issue, and tried to update like this: 8<8<8<- commit 051a42d95d25087e32f225e0ed4c264ccd4d4923 Author: Antonio Terceiro Date: Sun Feb 27 09:20:04 2022 -0300 Update diaspora to 0.7.16.0 for compatibility with ruby3.0+ diff --git a/debian/changelog b/debian/changelog index 06a7254..f652f44 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +diaspora-installer (0.7.16.0+debian1) experimental; urgency=medium + + * Team upload. + * Update diaspora to 0.7.16.0 for compatibility wit
Bug#1006119: uwsgi: FTBFS with ruby3.0 as default
On Sun, Feb 20, 2022 at 03:26:42PM -0300, Antonio Terceiro wrote:
> Control: tag -1 + patch
>
> On Sat, 19 Feb 2022 14:19:46 +0100 Paul Gevers wrote:
> > Source: uwsgi
> > Version: 2.0.20-2
> > Severity: serious
> > Tags: ftbfs
> > Justification: FTBFS
> > Control: block -1 by 1004915
> >
> > Dear maintainer,
> >
> > I tried to binNMU your package for the ongoing ruby3.0 as default ruby
> > transition. It failed:
> > https://buildd.debian.org/status/package.php?p=uwsgi
> >
> > Paul
>
> The attached patch converts the rack plugin to ruby3.0. Please let me
> know if I should just upload it (requires going through NEW due to the
> new bianry package).
Sorry, the patch I attached originall is obviously bogus, I typed
"echo" instead of "debdiff" when creating applied it. I'm attaching the
correct patch now (which I just uploaded, since this is blocking the
ruby3.0 transition).
diff -Nru uwsgi-2.0.20/debian/changelog uwsgi-2.0.20/debian/changelog
--- uwsgi-2.0.20/debian/changelog 2021-10-20 11:15:28.0 -0300
+++ uwsgi-2.0.20/debian/changelog 2022-02-26 12:42:07.0 -0300
@@ -1,3 +1,11 @@
+uwsgi (2.0.20-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Replace uwsgi-plugin-rack-ruby2.7 with uwsgi-plugin-rack-ruby3.0
+(Closes: #1006119)
+
+ -- Antonio Terceiro Sat, 26 Feb 2022 12:42:07 -0300
+
uwsgi (2.0.20-2) unstable; urgency=medium
* link againt libyajl
diff -Nru uwsgi-2.0.20/debian/control uwsgi-2.0.20/debian/control
--- uwsgi-2.0.20/debian/control 2021-10-20 11:05:25.0 -0300
+++ uwsgi-2.0.20/debian/control 2022-02-26 12:40:26.0 -0300
@@ -736,7 +736,7 @@
This package provides Python 3 WSGI plugin for uWSGI
(linked with Python 3 runtime).
-Package: uwsgi-plugin-rack-ruby2.7
+Package: uwsgi-plugin-rack-ruby3.0
Architecture: any
Depends:
uwsgi-core (= ${binary:Version}),
signature.asc
Description: PGP signature
