Bug#1019633: ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp

Source: ruby-invisible-captcha Version: 1.1.0-5 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-invisible-captcha with ruby3.1

Bug#1019632: ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(YAML.load(symbol_yaml)).to eq(YAML.load(string_yaml))

Source: ruby-ice-cube Version: 0.16.4-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-ice-cube with ruby3.1 enabled, the build

Bug#1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-httparty Version: 0.20.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-httparty with ruby3.1 enabled, the build

Bug#1019630: ruby-hoe: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-hoe Version: 3.22.1+dfsg1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-hoe with ruby3.1 enabled, the build failed.

Bug#1019629: ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-heapy Version: 0.2.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-heapy with ruby3.1 enabled, the build failed.

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 #

Source: ruby-hashie Version: 3.5.5-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-hashie with ruby3.1 enabled, the build failed.

Bug#1019627: ruby-graphviz: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-graphviz Version: 1.2.5-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-graphviz with ruby3.1 enabled, the build

Bug#1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-grape-entity Version: 0.10.1-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-grape-entity with ruby3.1 enabled, the

Bug#1019623: ruby-fog-core: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-fog-core Version: 2.1.0-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-fog-core with ruby3.1 enabled, the build

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

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

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.

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.

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

Bug#1019619: ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-did-you-mean Version: 1.2.1-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-did-you-mean with ruby3.1 enabled, the build

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

Bug#1019615: ruby-crack: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-crack Version: 0.4.4-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-crack with ruby3.1 enabled, the build failed.

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

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

Source: ruby-capybara Version: 3.36.0+ds-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-capybara with ruby3.1 enabled, the build

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

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

Bug#1019609: ruby-activerecord-import: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-activerecord-import Version: 1.2.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-activerecord-import with ruby3.1

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

Bug#1019608: rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq('')

Source: rubocop Version: 0.89.1+dfsg-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 rubocop with ruby3.1 enabled, the build failed.

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

Bug#1019605: feed2imap: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: feed2imap Version: 1.3.1-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 feed2imap with ruby3.1 enabled, the build failed.

Bug#1019604: bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: bsfilter Version: 1:1.0.19-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 bsfilter with ruby3.1 enabled, the build failed.

Bug#1019603: asciidoctor: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: asciidoctor Version: 2.0.16-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 asciidoctor with ruby3.1 enabled, the build failed.

Bug#1015207: transitions: ruby3.1-add

Hi, On Sun, Jul 17, 2022 at 02:08:14PM -0300, Lucas Kanashiro wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > Tags: moreinfo > > Hi, > > We would like to add support for ruby3.1 in ruby-defaults in unstable > soon.

Bug#1015305: 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

Bug#1019232: evince: annotation window in dark has a black cursor on a dark background (difficult to see)

Package: evince Version: 43~alpha-1+b1 Severity: normal Dear Maintainer, When using evince with GNOME in dark mode, the text cursor in the annotation window is very difficult to see, because it is black on a dark background. See the attached screenshot. I built evince from upstream git here,

Bug#1019101: resampy: autopkgtest regression on s390x

to be able to investigate. kind regards -- Antonio Valentino

Bug#1018983: gnucash-docs: No gnome help files

Package: gnucash-docs Version: 4.11-1 Severity: important X-Debbugs-Cc: acr...@gmail.com Dear Maintainer, Pressing F1 or selecting the menu option opens a gnome-help window with the message: El URI «ghelp:gnucash-help» no apunta a una página válida. In english The URI ‘ghelp:gnucash-help’ does

Bug#1010961: reverse dependency

Dear Thorsten, On Sat, 25 Jun 2022 11:30:47 +0200 Thorsten Alteholz wrote: Hi Antonio, there is a reverse dependency that needs to be taken care of: Checking reverse dependencies... # Broken Depends: pysph: pysph-viewer This needs to be addressed first. Please remove the moreinfo tag once

Bug#1018453: pysph: build-depends on python3-nose or uses it for autopkgtest

or waiting the closure of #1010961 and #1015009 and the migration to testing. Please let me know how to proceed. kind regards -- Antonio Valentino

Bug#1017808: ITP: zfp -- Fixed-Rate Compressed Floating-Point Arrays

Hi Gürkan, the package is now on mentros.d.net https://mentors.debian.net/package/zfp/ cheers antonio Il 22/08/22 13:00, Gürkan Myczko ha scritto: Hi Antonio, I have create a "working" git repo on my area in salsa. https://salsa.debian.org/antonio.valentino/zfp I hope you

Bug#1017808: ITP: zfp -- Fixed-Rate Compressed Floating-Point Arrays

Dear Gürkan, Il 21/08/22 20:44, Gürkan Myczko ha scritto: Hi Antonio, On 21 Aug 2022, at 20:34, Antonio Valentino wrote: [...] Il 21/08/22 11:45, Gürkan Myczko ha scritto: [...] On Sat, 20 Aug 2022 23:05:34 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= wrote: Package: wnpp Severity: wishlist

Bug#1017808: ITP: zfp -- Fixed-Rate Compressed Floating-Point Arrays

ry to include symbol files. Please let me know if you have any comments. kind regards -- Antonio Valentino

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

Bug#1017808: ITP: zfp -- Fixed-Rate Compressed Floating-Point Arrays

tool I'm very interested in having this library in Debian. If you need any help form me please let me know an I will be happy to support the packaging and maintenance of this library. kind regards -- Antonio Valentino

Bug#1017708: libodc-dev: installs objects over existing directory symlinks

Package: libodc-dev Version: 1.4.5-1 Severity: normal X-Debbugs-Cc: antonio.valent...@tiscali.it Dear Maintainer, the piuparts test for satpy [1] fails with the following message: 2m10.1s ERROR: installs objects over existing directory symlinks:

Bug#1017532: packagekit: please do the equivalent of "apt autoremove" after upgrades

Package: packagekit Version: 1.2.5-3 Severity: wishlist Dear Maintainer, I help a few friends whore are not into software run Debian on their machines. They do updates through gnome-software and PackageKit, and this works well. However, after a few stable updates, there are several kernels

Bug#1017447: pwgen: [PATCH] Add simple automated tests

: enabled From e18e9293ee39280f57a357cf0af1a4265afb4ee9 Mon Sep 17 00:00:00 2001 From: Antonio Terceiro Date: Tue, 16 Aug 2022 09:03:49 -0300 Subject: [PATCH] Add simple automated tests These tests are run as part of the test/check targets, and can help a limited set of catch implementation issues

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

Bug#1016835: pulseeffects: segfault

<48> 8b 5f 08 48 89 f7 e8 00 81 f5 ff 48 39 d8 48 89 da 48 89 c5 48 Thanks, Antonio

Bug#1016595: cuda: CUDA Error : system not yet initialized

/A N/A 6646 G ...181797667042908025,131072 32MiB | +-+ Before the system upgrade everything worked fine. Thanks Antonio -- System Information: Debian Release: bookworm/sid APT prefers testing APT

Bug#966524: "lvconvert --merge" does not remove the snapshot after completing

Hi Alexander, For now I understand that, unlike the previous time, I can eliminate the stall condition with:     vgchange -ay Perhaps an unavailable condition occurs, but not knowing how Lvconvert works can only hypothesize... I would like this bug to be closed, since it has been going on

Bug#1016541: ruby-aruba: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-aruba Version: 1.0.4-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-aruba with ruby3.1 enabled, the build failed.

Bug#966524: "lvconvert --merge" does not remove the snapshot after completing

Package: lvm2 Version:2.03.16-1 Dear Maintainer, I would like to remember that this problem is still present. Thanks, Antonio

Bug#1016530: Fwd: mesa-utils-bin: some applications do not start

: ../nptl/pthread_mutex_lock.c:424: __pthread_mutex_lock_full: Assertion `e != ESRCH || !robust' failed. Annullato Thanks, Antonio -- System Information: Debian Release: bookworm/sid   APT prefers unstable   APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500

Bug#1016371: transition: lerc

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition For the Debian GIS team I'd like to transition to LERC 4.0.0. The only reverse dependency is tiff and it rebuilds successfully with LERC 4.0.0 form experimental. Transition:

Bug#1016210: qtcreator: segmentation error

lled addOverrideAction /Switch to Welcome mode: Action /Switch to Welcome mode is already registered for context Global Context. Errore di segmentazione Thread 1 "qtcreator" received signal SIGSEGV, Segmentation fault. 0x763a5f34 in QObject::setProperty(char const*, QVariant cons

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

Bug#1016122: dh_strip: will not strip shared library under a debug/ directory

Package: debhelper Version: 13.8 Severity: normal File: /usr/bin/dh_strip Dear Maintainer, While running lintian against a ruby3.1 build, I was presented with an error tag from lintian: E: libruby3.1: unstripped-binary-or-object

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

Bug#982887: #982887: cross building Ruby extensions

Hi, After a long time, I was able to finish a first version of this. The solution has two parts: 1) Per Ruby version, per architecture rbconfig.rb provided by ruby-all-dev: $ dpkg -L ruby-all-dev:amd64 ruby-all-dev:arm64 | grep rbconfig

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

Bug#1015338: ruby-xmlhash: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-xmlhash Version: 1.3.6-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-xmlhash with ruby3.1 enabled, the build failed.

Bug#1015339: ruby-zoom: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-zoom Version: 0.5.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-zoom with ruby3.1 enabled, the build failed.

Bug#1015337: ruby-websocket-driver: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-websocket-driver Version: 0.6.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-websocket-driver with ruby3.1 enabled,

Bug#1015335: ruby-timfel-krb5-auth: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-timfel-krb5-auth Version: 0.8.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-timfel-krb5-auth with ruby3.1 enabled,

Bug#1015332: ruby-sdl: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-sdl Version: 2.2.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-sdl with ruby3.1 enabled, the build failed.

Bug#1015336: ruby-vmstat: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-vmstat Version: 2.3.0-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-vmstat with ruby3.1 enabled, the build failed.

Bug#1015334: ruby-stackprof: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-stackprof Version: 0.2.17-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-stackprof with ruby3.1 enabled, the build

Bug#1015333: ruby-sigar: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-sigar Version: 0.7.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-sigar with ruby3.1 enabled, the build failed.

Bug#1015331: ruby-rpam-ruby19: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-rpam-ruby19 Version: 1.2.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-rpam-ruby19 with ruby3.1 enabled, the build

Bug#1015330: ruby-rdiscount: FTBFS with ruby3.1: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-rdiscount Version: 2.1.8-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-rdiscount with ruby3.1 enabled, the build

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

Source: ruby-mysql2 Version: 0.5.3-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-mysql2 with ruby3.1 enabled, the build failed.

Bug#1015326: ruby-libxml: FTBFS: causes the ruby interpreter to crash (?)

Source: ruby-libxml Version: 3.2.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-libxml with ruby3.1 enabled, the build failed.

Bug#1015329: ruby-prof: FTBFS: ERROR: Test "ruby3.1" failed.

Source: ruby-prof Version: 1.3.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-prof with ruby3.1 enabled, the build failed.

Bug#1015328: ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed.

Source: ruby-netcdf Version: 0.8.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-netcdf with ruby3.1 enabled, the build failed.

Bug#1015323: ruby-levenshtein: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-levenshtein Version: 0.2.2-3+rebuild1658134203 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-levenshtein with ruby3.1

Bug#1015322: ruby-kyotocabinet: FTBFS: kccommon.h:19:8: error: expected identifier or ‘(’ before string constant

Source: ruby-kyotocabinet Version: 1.34-0.1+rebuild1658134192 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-kyotocabinet with

Bug#1015321: ruby-god: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-god Version: 0.13.7-3+rebuild1658134141 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-god with ruby3.1 enabled, the

Bug#1015320: ruby-github-markdown: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-github-markdown Version: 0.6.9-5+rebuild1658137820 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-github-markdown with

Bug#1015319: ruby-gd: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-gd Version: 0.8.0-8+rebuild1658134133 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-gd with ruby3.1 enabled, the build

Bug#1015315: ruby-fcgi: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-fcgi Version: 0.9.2.1-3+rebuild1658134097 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-fcgi with ruby3.1 enabled, the

Bug#1015316: ruby-fusefs: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-fusefs Version: 0.7.0-5+rebuild1658134133 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-fusefs with ruby3.1 enabled,

Bug#1015311: ruby-fast-stemmer: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-fast-stemmer Version: 1.0.2-3+rebuild1658134087 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-fast-stemmer with ruby3.1

Bug#1015312: ruby-fast-xs: FTBFS: Tried to load unspecified class: Gem::Specification (Psych::DisallowedClass)

Source: ruby-fast-xs Version: 0.8.0-3+rebuild1658134093 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-fast-xs with ruby3.1 enabled,

Bug#1015310: ruby-dataobjects-mysql: FTBFS: chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': Permission denied

Source: ruby-dataobjects-mysql Version: 0.10.17-3+rebuild1658134000 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-dataobjects-mysql

Bug#1015309: ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: actual = YAML.load(regexp.to_yaml)

Source: ruby-bson Version: 4.10.0-2+rebuild1658137615 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-bson with ruby3.1 enabled, the

Bug#1015308: ruby-bert: FTBFS: ERROR: Test "ruby3.1" failed.

Source: ruby-bert Version: 1.1.6-2+rebuild1658133846 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-bert with ruby3.1 enabled, the

Bug#1015307: ruby-atomic: FTBFS: make: *** [debian/rules:15: binary] Error 25

Source: ruby-atomic Version: 1.1.16-3+rebuild1658133756 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-atomic with ruby3.1 enabled,

Bug#1015306: raspell: FTBFS: make: *** [debian/rules:15: binary] Error 25

Source: raspell Version: 1.3-2+rebuild1658133666 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild raspell with ruby3.1 enabled, the build

Bug#1015305: puma: FTBFS: ERROR: Test "ruby3.1" failed.

Source: puma Version: 5.6.4-1+rebuild1658137576 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild puma with ruby3.1 enabled, the build

Bug#1015149: vim-addon-manager is no longer desirable for packaging Vim plugins

Hi, On Sat, Jul 16, 2022 at 10:15:02PM +0300, Nicholas Guriev wrote: > Package: vim-addon-manager > > This message states that deprecated vim-addon-manager(1) should not be used > within Debian codebase. > VAM was written in aughts to simplify installation of third-party scripts for > Vim

Bug#1015009: RM: pysph-viewer [ppc64 s390x] -- ROM; new build dependency not available on ppc64el and s390x

Package: ftp.debian.org Severity: normal src:pysph: fails to migrate to testing for too long: new build dependency not available on ppc64el and s390x See also #1010862 and #1010961. kind regards -- Antonio Valentino

Bug#1014452: pyresample: Test failures with rasterio 1.3.0

'/usr/lib/python3/dist-packages/rasterio/_loading.py'> I see > E ImportError: /usr/lib/python3/dist-packages/rasterio/_filepath.cpython-39-x86_64-linux-gnu.so: undefined symbol: VSIAllocFilesystemPluginCallbacksStruct could it be a problem related to a mismatch with the GDAL version? Any idea on how to proceed? kind regards -- Antonio Valentino

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 > >

Bug#1014380: vagrant: Unable to activate net-sftp-3.0.0, because net-ssh-7.0.1 conflicts with net-ssh (>= 5.0.0, < 7.0.0)

Control: reassign -1 ruby-net-ssh Control: notfound -1 1:7.0.0~beta1-2 Control: found -1 1:7.0.1-1 Control: retitle -1 ruby-net-ssh: breaks version expectations of ruby-net-sftp Control: affects -1 vagrant On Tue, Jul 05, 2022 at 10:31:09AM +0200, Kyle Robbertze wrote: > Package: vagrant >

Bug#1004459: bullseye-pu: package lxc/1:4.0.6-2+deb11u1

On Fri, Jul 01, 2022 at 07:13:24PM +0100, Adam D. Barratt wrote: > On Sun, 2022-02-20 at 19:38 -0300, Antonio Terceiro wrote: > > On Sat, Feb 19, 2022 at 06:53:52PM +, Adam D. Barratt wrote: > > > Control: tags -1 + confirmed > > > > > > On Thu, 2022-01

Bug#1004821: libam7xxx: FTBFS with ffmpeg 5.0

this week-end to push a new package compatible with FFmpeg 5.0. Take care, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?

Bug#1014078: RFS: librosa/0.9.2-1 [ITP] -- Python package for music and audio analysis

need to add it to your list of dependencies. P.S.: I will update the resampy package to the latest upstream version as soon as possible. regards -- Antonio Valentino

Bug#1013451: openssh-client: double free or corruption

GNU gdb (Debian 12.1-2) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show

Bug#1013451: openssh-client: double free or corruption

Package: openssh-client Version: 1:9.0p1-1 Severity: grave Dear Maintainer, after update to version 1:9.0p1-1+b1 a get this error: --- $ ssh xxx.xxx.xxx.xxx double free or corruption (!prev) Canceled --- and program crash. For now I downgrade to 1:9.0p1-1 version. Thanks, Antonio -- System

Bug#1012247: ruby3.1: Please build with --with-coroutine=ucontext on x32

On Thu, Jun 02, 2022 at 06:10:26PM +0200, John Paul Adrian Glaubitz wrote: > Hi Antonio! > > On 6/2/22 15:58, John Paul Adrian Glaubitz wrote: > > On 6/2/22 15:43, Antonio Terceiro wrote: > >> isn't this something that should be done in configure.ac instead (and > >

Bug#1012247: ruby3.1: Please build with --with-coroutine=ucontext on x32

On Thu, Jun 02, 2022 at 09:17:43AM +0200, John Paul Adrian Glaubitz wrote: > Source: ruby3.1 > Version: 3.1.2-1 > Severity: normal > Tags: patch > > Hello! > > ruby3.1 FTBFS on x32 because the configure misdetects x32 as amd64: > > checking stack growing direction on x86_64... -1 > checking

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 > >

Bug#1009363: bullseye-pu: package ruby-net-ssh/1:6.1.0-2+deb11u1

On Sat, May 28, 2022 at 08:47:53PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Tue, 2022-04-12 at 09:40 -0300, Antonio Terceiro wrote: > > OpenSSH 8.8 disables RSA signatures using the SHA-1 hash algorithm, > > and > > that breaks clients t

<    1   2   3   4   5   6   7   8   9   10   >