Bug#1019680: ruby-zeitwerk: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: LoadError: cannot load such file -- /<>/test/tmp/foo.rb

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

Bug#1019679: ruby-yaml-db: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

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

Bug#1019678: ruby-websocket: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(handshake.to_s).to eql(client_request)

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

Bug#1019677: ruby-webpacker: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

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

Bug#1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #

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

Bug#1019675: ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-versionomy Version: 0.5.0-2.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-versionomy with ruby3.1 enabled, the build

Bug#1019672: ruby-uglifier: FTBFS with ruby3.1: make[1]: *** [debian/rules:15: override_dh_auto_install] Error 25

Source: ruby-uglifier Version: 4.2.0+dfsg-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-uglifier with ruby3.1 enabled, the build

Bug#1019674: ruby-vcr: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: test failures

Source: ruby-vcr Version: 6.0.0+really5.0.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-vcr with ruby3.1 enabled, the build

Bug#1019673: ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require 'ruby-growl'

Source: ruby-uniform-notifier Version: 1.13.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-uniform-notifier with ruby3.1 enabled,

Bug#1019671: ruby-test-spec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-test-spec Version: 0.10.0-3.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-test-spec with ruby3.1 enabled, the build

Bug#1019668: ruby-sixarm-ruby-unaccent: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage measuremen

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

Bug#1019669: ruby-slim: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:130:in `block (3 levels) in define': Command failed with status

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

Bug#1019670: ruby-sprite-factory: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: no image files found

Source: ruby-sprite-factory Version: 1.7.1-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-sprite-factory with ruby3.1 enabled, the

Bug#1019667: ruby-sinatra: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- wlang: skipping wlang tests

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

Bug#1019553: FTBFS: ts_file_io

Hello Adam, Thanks for your report. I've unable to reproduce the build failure as of now, using both a docker image and sbuild on my laptop (amd64 only). The failing test simply tries to open /etc/hosts (which should be present inside chroot), read it and look for the string localhost

Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

Source: ruby-safe-yaml Version: 1.0.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-safe-yaml with ruby3.1 enabled, the build

Bug#1019666: ruby-simplecov: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(@stderr).to be_empty

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

Bug#1019664: ruby-rspec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure }

Source: ruby-rspec Version: 3.10.0c1e1m2s3-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-rspec with ruby3.1 enabled, the build

Bug#1019662: ruby-riddle: FTBFS: mysql server fails to start

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

Bug#1019663: ruby-ronn: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

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

Bug#1019445: shotcut: Shotcut crashes on startup with error: File already exists in database: opencv-caffe.proto

Hi Matteo, [Debug ] begin [libprotobuf ERROR google/protobuf/descriptor_database.cc:120] File already exists in database: opencv-caffe.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1382] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): terminate called after

Bug#949086: Bug#945623: cfengine3: diff for NMU version 3.15.2-3.2

Hi all, I'll have a look at it. First I will include the changes from NMU -3.1 into the salsa repository. Christoph Am 09.09.22 um 09:33 schrieb Hugh McMaster: Control: tags 945623 + patch Control: tags 949086 + patch Control: tags 998014 + patch Dear maintainer, I've prepared an NMU for

Bug#1019661: Breaks monin and maybe other packages

Klaus, On Tue, Sep 13, 2022 at 12:16:33PM +0100, Klaus Ethgen wrote: > Package: lsb-base > Version: 11.3 > Severity: critical > > The new package breaks monin as it does not provide > /lib/lsb/init-functions anymore. This file has been moved to sysvinit-utils. Which version of that do you have

Bug#1019661: Breaks monin and maybe other packages

Package: lsb-base Version: 11.3 Severity: critical The new package breaks monin as it does not provide /lib/lsb/init-functions anymore. As this is used in many other packages, I suspect more breaks. -- System Information: Debian Release: bookworm/sid APT prefers experimental APT policy: (1,

Bug#1019577: hokey lint: "Non-exhaustive patterns in function getSecretKey" when sending a secret key instead of certificate

On Tue, Sep 13, 2022 at 03:02:14AM -0400, Daniel Kahn Gillmor wrote: > I was "hokey lint"ing the attached binary-formatted secret key, which > was provided by Justus Winter for use with the notmuch test suite: Looks like parsing of Ed25519 secret keys hasn't been implemented in hOpenPGP yet and

Bug#1019660: console-setup: grep: warning: stray \ before #

Package: console-setup Version: 1.210 Severity: minor Control: affects -1 + initramfs-tools With grep (>= 3.8), I'm getting this warning: # setupcon grep: warning: stray \ before # -- System Information: Architecture: i386 Versions of packages console-setup depends on: ii debconf

Bug#1018063: [debian-mysql] Bug#1018063: Regression: mariadb client default charset changed breaks compatibility

Hi Georg! Georg Richter , 08/09/2022 – 17:40:21 (+0200): > default character set changed here: > https://github.com/mariadb-corporation/mariadb-connector-c/commit/d7461f7c4f6e36b4916f3dda2b64ac0cae88868c OK > Issues: CONC-547, MDEV-25485. > Github discussion: >

Bug#1019568: lintian-brush: Fixer lintian debian-watch-does-not-check-gpg-signature reformats wrongly

* Jelmer Vernooij: " Re: Bug#1019568: lintian-brush: Fixer lintian debian-watch-does-not-check-gpg-signature reformats wrongly" (Tue, 13 Sep 2022 05:02:50 +0100): Hi Jelmer, > On Mon, Sep 12, 2022 at 10:09:40AM +0200, Mathias Behrle wrote: > > running lintian-brush --allow-reformatting > >

Bug#978621: pipewire: Drag and drop a file in Dolphin makes pipewire crash KDE Plasma Wayland

Control: tag 978621 moreinfo Hi Silvério, Is this crash still reproducible with latest pipewire and KDE versions? I have seen several issues between pipewire and KDE solved, thus I am temped to close this bug if it is no longer reproducible. Best, Dylan

Bug#1019587: qflipper: Missing dependency on qml-module-qt-labs-platform

Control: tag -1 + pending On Mon, 12 Sep 2022 10:56:40 -0700 Francois Marier wrote: > After installing the qml-module-qt-labs-platform package, everything starts > up fine. > > Please add the missing dependency (or at the very least a Recommends). Thanks for the report. Will fix this in

Bug#977813: Bug#980974: apparmor blocks cups backend outgoing network connections

Christian Boltz schrieb am Wed 17. Aug, 20:47 (+0200): > Hello, > > denials for capabilty net_admin are often a sign that a service uses > systemd libraries on startup, and these systemd libraries do funny[tm] > things. In these cases the net_admin capability is not really needed. Hi, yes,

Bug#959930: update does not need gradle

control: unblock -1 by 933264 926714 I have successfully built v0.39 locally without gradle (using javahelper instead). Maven coordinates have disappeared as a result, but at least one of the reverse dependencies, beast-mcmc, builds successfully. Other reverse dependencies (deepboof, ddogleg and

Bug#1019659: ITP: golang-github-maruel-natural -- Natural sorting (natsort) in Go

Package: wnpp Severity: wishlist Owner: Daniel Milde * Package name : golang-github-maruel-natural Version : 1.1.0-1 Upstream Author : M-A * URL : https://github.com/maruel/natural * License : Apache-2.0 Programming Lang: Go Description : Natural sorting (natsort) in Go natural . Yet another

Bug#1019325: Patch

Here's the patch I applied locally to my /etc to fix these warnings. Francois -- https://fmarier.org/ diff --git a/logcheck/ignore.d.server/anon-proxy b/logcheck/ignore.d.server/anon-proxy index 6b111708..31a442fd 100644 --- a/logcheck/ignore.d.server/anon-proxy +++

Bug#1019577: hokey lint: "Non-exhaustive patterns in function getSecretKey" when sending a secret key instead of certificate

On Mon 2022-09-12 13:52:50 +, Clint Adams wrote: > On Sun, Sep 11, 2022 at 01:02:33PM -0400, Daniel Kahn Gillmor wrote: >> I think what it's trying to say is "hokey lint only works on OpenPGP >> certificates, not secret keys". But this is a pretty awkward way to say >> it. > > That is not

Bug#1019575: usr-is-merged false-negative on arm64

On Sep 12, Boris Kolpackov wrote: > Indeed. A bit more digging revealed that this is systemd-nspawn's > "helpful" hand. Specifically, there is no /lib64 before I run > systemd-nspawn, it is present during, and it disappears again after > systemd-nspawn exits. This is caused by

Bug#975597: libxft2: fonts-noto-color-emoji causes protocol error in libxft

Hi, this has been fixed upstream in version 2.3.5: | Add support for BGRA glyphs display and scaling https://gitlab.freedesktop.org/xorg/lib/libxft/-/blob/libXft-2.3.5/NEWS I've merged the latest 2.3.6 locally and it seems to work fine. Would be great to get that into unstable. Cheers Jochen

Bug#1019656: dwww: cannot set custom title containing spaces with configuration parameter DWWW_TITLE

Package: dwww Version: 1.14 Severity: wishlist The dwww configuration file "/etc/dwww/dwww.conf" statess "The file is in Bourne shell script format, thus no spaces may be used in variables assignments." which gives a false impression since the configuration file is in fact read using the Perl

Bug#1017623: nautilus-filename-repairer: Fails to build with Nautilus 43

I reviewed the code for a while but it needs a significant change to migrate. Adopting new APIs was relatively easy, but this repairer extension works by launching several modal synchronous dialogs, which are obsolete in GTK4, in sequence. This impacts the whole flow of this program in GTK4

Bug#1004308: smokeping: New upstream version 2.8.2 needs to be packaged

Hi Gabriel, * Gabriel Filion [Mon Jan 24, 2022 at 10:53:27AM -0500]: > Upstream has released a new version of smokeping, 2.8.2 and it would be > helpful > to upgrade the debian package to this version since it contains a number of > fixes, some of which would remove patches in the package. > >

<    1   2