Bug#1019655: remmina: should support WM_DELETE_WINDOW like other programs

Package: remmina Version: 1.4.11+dfsg-3 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A host connection ended and remmina displayed its "lost connection [close]" or something similar banner

Bug#1019507: ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6)

Hi, Am Mon, Sep 12, 2022 at 08:08:40PM +0200 schrieb Filippo Rusconi: > > Thank you for the offer, but the package was just sponsored yesterday by > > Adam Borowski (kilobyte) and is in the NEW queue. If you're interested > > in QuaZip for Qt5, I could package that for you to review. > > Well,

Bug#1019654: cfengine3: Package latest LTS/non-LTS version

Package: cfengine3 Version: 3.15.2-3.1 Severity: wishlist Dear Maintainer, Upstream support for the current version of CFEngine in Debian, 3.15 LTS, will end on 31 December 2022. Shortly after, the next Debian freeze will begin. To ensure users of Debian Bookworm can install a more recent

Bug#1019653: RFP simple-netaid - a minimal connection manager with curses and gtk interfaces

Package: wnpp Severity: wishlist This program is being actively developed. The packaging is bookworm-compatible but more work is needed for a Debian release. > From: aitor > Date: Mon, 18 Jul 2022 02:17:56 +0200 > This weekend I uploaded the packages for daedalus [bookworm] > The newest

Bug#1019651: "Control: fixed ..." not working

On Mon, 2022-09-12 at 23:17 -0300, Joao Eriberto Mota Filho wrote: > I noticed in several opportunities that any "Control: fixed" inside > email > messages won't work. See an example here[1]. I needed to send an > extra command > via bts ($ bts fixed 336959 spell/1.0-16) to work. > > [1]

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

On Mon, Sep 12, 2022 at 10:09:40AM +0200, Mathias Behrle wrote: > running lintian-brush --allow-reformatting > introduced the following change: > > -opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ > -https://pypi.debian.net/zeep/zeep-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) >

Bug#1019652: ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result[1]).to eq token

Source: ruby-regexp-parser Version: 2.1.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-regexp-parser with ruby3.1 enabled, the

Bug#1019651: "Control: fixed ..." not working

Package: bugs.debian.org Severity: normal Dear maintainers, I noticed in several opportunities that any "Control: fixed" inside email messages won't work. See an example here[1]. I needed to send an extra command via bts ($ bts fixed 336959 spell/1.0-16) to work. [1]

Bug#1019649: ruby-rabl: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: rm: cannot remove 'Gemfile.lock': No such file or directory

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

Bug#1019650: ruby-rantly: 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 measurement is already s

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

Bug#1019648: ruby-premailer-rails: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-premailer-rails Version: 1.10.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-premailer-rails with ruby3.1 enabled,

Bug#1019647: ruby-power-assert: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-power-assert Version: 1.1.7-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-power-assert with ruby3.1 enabled, the

Bug#1019646: ruby-parallel: FTBFS: fails randomly

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

Bug#1019645: ruby-otr-activerecord: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

Source: ruby-otr-activerecord Version: 2.0.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-otr-activerecord with ruby3.1 enabled,

Bug#1019644: ruby-omniauth-openid-connect: 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 measure

Source: ruby-omniauth-openid-connect Version: 0.10.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-omniauth-openid-connect with

Bug#1019642: ruby-omniauth-kerberos: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: NoMethodError:

Source: ruby-omniauth-kerberos Version: 0.3.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-omniauth-kerberos with ruby3.1

Bug#1019640: ruby-mono-logger: 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 measurement is alre

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

Bug#1019643: ruby-omniauth-oauth2-generic: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.headers["Location"]).to match(%r{redirect_uri=https%3A%2F%2Fmy_ser

Source: ruby-omniauth-oauth2-generic Version: 0.2.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-omniauth-oauth2-generic with

Bug#1007152: RFP: virtiofsd -- vhost-user virtio-fs device backend written in Rust

Thomas Koch wrote: > Hash: SHA256 > > * Package name: virtiofsd > Version : 1.1.0 > Upstream Author : multiple, Chromium OS, Intel Corp, Red Hat > * URL : https://gitlab.com/virtio-fs/virtiofsd > * License : BSD and Apache > Programming Lang: Rust >

Bug#1019641: ruby-omniauth-auth0: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.status).to eq(302)

Source: ruby-omniauth-auth0 Version: 2.0.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-omniauth-auth0 with ruby3.1 enabled, the

Bug#1019639: ruby-minitest-hooks: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-minitest-hooks Version: 1.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-minitest-hooks with ruby3.1 enabled, the

Bug#1019636: ruby-mechanize: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

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

Bug#1019638: ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-memory-profiler Version: 0.9.14-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-memory-profiler with ruby3.1 enabled,

Bug#1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is memoized')

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

Bug#1019635: ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Can not decode an entire message, try calling #decoded on the various fields and body or p

Source: ruby-mail Version: 2.7.1+dfsg1-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-mail with ruby3.1 enabled, the build

Bug#1019634: ruby-jekyll-remote-theme: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'liqu

Source: ruby-jekyll-remote-theme Version: 0.4.3-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-jekyll-remote-theme with ruby3.1

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#1019335: Shellcheck is a great tool

Looks like WAY more people need to learn the wonderful tool when it comes to scripts: shellcheck (also packaged for Debian) Maybe make it a release goal for Trixie to make that a requirement? Run your scripts through shellcheck and you'd have been warned years ago too:

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#741278: ITA: java2html -- Highlight Java and C++ sources for WWW presentation

I intend to adopt (ITA) this package. -- Regards, Adrian Gallo

Bug#1019625: No debug packages for Sid.

Package: evolution Version: 3.45.3-2 Severity: normal There are no debug packaes in the Sid repositories for any of the evolution packages. I have run into an issue in the last couple of weeks and would like to be able to run some debugging so I can provide extra information -- System

Bug#1019624: UPSONIC IRT-3K 2U broken by length checking in blazer_usb/nutdrv_qx

Package: nut-server Version: 2.7.4-13 Severity: normal Tags: patch Short version: 1. UPSONIC IRT-3K 2U speaks a variant of Q1 which omits final \r. 2. nut 2.4 doesn't check for final \r, so it Just Works. 3. nut 2.7 checks for final \r, cannot talk to my UPS. 4. I fixed #3 but it's not

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#1019335: fixed in grep 3.8-2

Hi, On Mon, Sep 12, 2022 at 03:21:01PM +, Debian FTP Masters wrote: >* Add 01-disable-egrep-fgrep-warnings.patch (Closes: #1019335) >* Add 02-man_egrep_fgrep_rgrep.patch >* Reintroduce and updated 05-grep-wrapper-sh.patch >* Add test to check availability of egrep and fgrep >

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#1017739: emacs-lucid cannot start after upgrade

Stefan Monnier writes: > > Of course, another way to fix this is to actually fix the original > problem where the wrong directory (i.e. `~$USER/.emacs.d` instead of > `$HOME/.emacs.d`) is chosen. This original problem affects other > circumstances where Emacs will write to the `.emacs.d`

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#1018799: gcc-12: Workround for fixing -latomic issue on riscv64 after glibc2.34

Hi, On 2022-09-06 09:56, Bo YU wrote: > Hi, > On Wed, Aug 31, 2022 at 07:04:53PM +0200, Aurelien Jarno wrote: > ... > > reason for limiting the link with -latomic to pthread, but that has been > > discussed internally before the patch submission to GCC, and has been > > lost. > > > > Anyway this

Bug#1019602: texlive-bin: CVE-2022-35486 CVE-2022-35485 CVE-2022-35484 CVE-2022-35483 CVE-2022-35482 CVE-2022-35481 CVE-2022-35479 CVE-2022-35478 CVE-2022-35477 CVE-2022-35476 CVE-2022-35475 CVE-2022-

Source: texlive-bin X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for OFTCC, which starting with some texlive release after Bullseye gets included in texlive (web2c/mfluadir):

Bug#1019600: swfmill: CVE-2022-36139 CVE-2022-36144

Source: swfmill X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for swfmill. CVE-2022-36139[0]: | SWFMill commit 53d7690 was discovered to contain a heap-buffer | overflow via SWF::Writer::writeByte(unsigned char).

Bug#1019601: docker.io: CVE-2022-36109

Source: docker.io X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for docker.io. CVE-2022-36109[0]: | Moby is an open-source project created by Docker to enable software | containerization. A bug was found in Moby (Docker

Bug#1019596: libconfuse: CVE-2022-40320

Source: libconfuse X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for libconfuse. CVE-2022-40320[0]: | cfg_tilde_expand in confuse.c in libConfuse 3.3 has a heap-based | buffer over-read.

Bug#1019595: gpac: CVE-2022-38530 CVE-2022-36186 CVE-2022-36190 CVE-2022-36191

Source: gpac X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for gpac. CVE-2022-38530[0]: | GPAC v2.1-DEV-rev232-gfcaa01ebb-master was discovered to contain a | stack overflow when processing ISOM_IOD.

Bug#1019599: w3m: CVE-2022-38223

Source: w3m X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for w3m. CVE-2022-38223[0]: | There is an out-of-bounds write in checkType located in etc.c in w3m | 0.5.3. It can be triggered by sending a crafted HTML file to

Bug#1019598: pspp: CVE-2022-39832

Source: pspp X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for pspp. CVE-2022-39832[0]: | An issue was discovered in PSPP 1.6.2. There is a heap-based buffer | overflow at the function read_string in

Bug#1019597: pspp: CVE-2022-39831

Source: pspp X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for pspp. CVE-2022-39831[0]: | An issue was discovered in PSPP 1.6.2. There is a heap-based buffer | overflow at the function read_bytes_internal in

Bug#1019594: deluge: CVE-2021-3427

Source: deluge X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for deluge. CVE-2021-3427[0]: | The Deluge Web-UI is vulnerable to XSS through a crafted torrent file. | The the data from torrent files is not properly

Bug#1019593: hp-plugin: Failure to download plugin

Package: hplip Version: 3.22.6+dfsg0-1 Severity: normal File: /usr/bin/hp-plugin Trying to get a M479fdn to work, I found that `hp-setup` fails to download the plugin. It seems to contact an Akamai host using `HEAD` and that results in a "503 Service Unavailable". It then tries to get a

Bug#1019425: dkms 3.0.6-2 not signing modules

Package: dkms Version: 3.0.6-2 Followup-For: Bug #1019425 Control: tags -1 patch The dkms script has several flaw that forbid module signing: - Debian, contrary to ubuntu, does not have kmodsign sign-file from the kernel should be directly used - the script logic was wrong (if [[ -x

Bug#1014932: python3-jellyfish: DeprecationWarning: getargs: The 'u' format is deprecated. Use 'U' instead

tag 1014932 + fixed-upstream thanks On Thu, Jul 14, 2022 at 07:42:12PM +0200, Jakub Wilk wrote: > Package: python3-jellyfish > Version: 0.8.9-1+b1 > > I'm getting this deprecation warning: This has been fixed in version 0.9.0 upstream, so the Debian package needs updating to fix this. Best

Bug#1019592: advancecomp: CVE-2022-35020 CVE-2022-35019 CVE-2022-35018 CVE-2022-35017 CVE-2022-35016 CVE-2022-35015 CVE-2022-35014

Source: advancecomp X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for advancecomp. Multiple issues in advancement, I suppose none of these have actually been forwarded upstream by the reporter: CVE-2022-35020[0]: |

Bug#1019513: node-jquery breaks r-cran-pkgdown autopkgtest: replacement has 11 rows, data has 10

Control: reassign -1 r-cran-jquerylib 0.1.4+dfsg-3 Control: reassign 1019514 r-cran-jquerylib 0.1.4+dfsg-3 Control: close -1 Control: close 1019514 Both this and #1019514 are due to jquerylib build pointing to old symlinks of jquery. I have re-uploaded a new changelog revision with this updated

Bug#1019591: libpod: CVE-2022-2989

Source: libpod X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for libpod. CVE-2022-2989[0]: https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/

Bug#1018940: devhelp: Scrolling does not immediately update the view

I don't experience this bug, but I'm using Intel graphics and webkit2gtk 2.37.91 (found in Experimental). webkitgtk 2.38 should be released soon and available in Debian Unstable and Testing shortly after that. Thank you, Jeremy Bicha

Bug#959972: Obsolete binaries?

On Bullseye (11.5), needrestart seems to think that nextcloud-desktop is using (or trying to use) an obsolete binary. One solution would be to provide a backport. With nextcloud-desktop running, needrestart reports that my user is running an outdated binary. Shut it down, and needrestart no

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#1019590: vim: CVE-2022-2946 CVE-2022-2982 CVE-2022-3037 CVE-2022-3099 CVE-2022-3134

Source: vim X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for vim. CVE-2022-2946[0]: | Use After Free in GitHub repository vim/vim prior to 9.0.0246. https://huntr.dev/bounties/5d389a18-5026-47df-a5d0-1548a9b555d5

Bug#1019589: dpdk: CVE-2022-28199 CVE-2022-2132

Source: dpdk X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities are fixed in DSA 5222, but filing a bug to track the fix in unstable: CVE-2022-28199[0]: | NVIDIA#8217;s distribution of the Data Plane Development Kit | (MLNX_DPDK) contains a

Bug#1019550: cryptmount: [INTL:de] updated German po file translation

Thanks, Helge - that's very helpful. I'll roll this into the next release of cryptmount. Your changes should also be visible in the (new) GitHub repository at https://github.com/rwpenney/cryptmount/commit/e631e0d98238618c455f409292618f624ab80c3a

Bug#1019507: ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6)

Greetings, Ben, On Mon, Sep 12, 2022 at 05:48:15PM +, Ben Westover wrote: Hello Filippo, On 9/12/22 10:08 AM, Filippo Rusconi wrote:> We do depend on Quazip and I very muuch would like to see a package for Qt6. Tell me how I can help and were to find the packaging repos. I'd be eager to

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#1019588: jdupes: BTRFS deduplication broken by new update

Package: jdupes Version: 1.21.0-1 Severity: normal Dear Maintainer, When running jdupes -rB ./ in a folder on a BTRFS filesystem, I got errors for every file: eg,   [SRC] ./.git/logs/HEAD   -XX-> ./.git/logs/refs/heads/master error: Inappropriate ioctl for device (25) I have been running jdupes

Bug#1000927: fixed in unstable

On Thu, 8 Sep 2022 15:20:23 +0200 Matthias Klose wrote: > fixed in unstable, now built using LLVM 13. When this bug was closed, it was titled "creduce: Please upgrade to llvm-toolchain-14", so i don't believe this is fixed, which is suboptimal because creduce is the only blocker for me to be

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

Package: qflipper Version: 1.1.1-2 Severity: important I installed qflipper and was unable to run it: $ qFlipper 34 [default] QQmlApplicationEngine failed to load component 35 [default] qrc:/main.qml:29:5: Type MainWindow unavailable 35 [default] qrc:/components/MainWindow.qml:7:1:

Bug#1019542: reverse dependencies

Control: tags -1 + moreinfo Hi Roland, there are reverse dependencies that needs to be taken care of: Checking reverse dependencies... # Broken Depends: inventor: libinventor1 pokerth: pokerth-data # Broken Build-Depends: gcc-3.3: gsfonts-x11 In case they matter, this needs to be addressed

Bug#934608: license of the book

The book is available in french and english also for bullseye https://lescahiersdudebutant.arpinux.org/bullseye-en/ This is the license: the beginner's handbook is published under Free License WTFPLv2 --- WTFPL DO WHAT THE FUCK YOU

Bug#1019343: Remove Date::Manip entirely? PATCH [1/1]

On Mon, 12 Sep 2022 10:07:54 -0700, Nye Liu wrote: > > > munin-graph does not seem to use Date::Manip at all, unless there is a > > > hidden dependency that isn't obvious. > > This also causes munin's autopkgtests to fail which blocks > > libdate-manip-perl from migrating to testing. >

Bug#1019586: gnome-shell-extension-weather: Extension not compatible with libsoup3

Package: gnome-shell-extension-weather Version: 0.0~git20210509.d714eb1-4 Severity: important Tags: upstream Hello, The extension broke after building gnome-shell 42.4-2 with libsoup3 in Debian testing. It cannot fetch the weather data any more. 18:49:37 gnome-shell: Unhandled promise

Bug#1019585: Syntax error: expected expression, got keyword 'const' @ extension.js:13:4

Package: gnome-shell-extension-gsconnect Version: 50-5 Severity: important Hello, There is a JS error / syntax error in the extension.js file after the recent 50-5 upload. JS ERROR: Extension gsconn...@andyholmes.github.io: SyntaxError: expected expression, got keyword 'const' @

Bug#1019343: Remove Date::Manip entirely? PATCH [1/1]

On Wed, 07 Sep 2022 16:59:17 -0700, Nye Liu wrote: > munin-graph does not seem to use Date::Manip at all, unless there is a > hidden dependency that isn't obvious. This also causes munin's autopkgtests to fail which blocks libdate-manip-perl from migrating to testing. Now it can be argued that

Bug#1019554: Stamp files are not updated

Hello, $ ls -tlr /var/spool/anacron/ insgesamt 12 -rw--- 1 root root 9 16. Aug 17:03 cron.monthly -rw--- 1 root root 9 3. Sep 09:31 cron.weekly -rw--- 1 root root 9 5. Sep 13:02 cron.daily So cron.weekly is now overdue and cron.daily did not get touched since the 5th, consistent

Bug#1019448: ITP: golang-github-gonvenience-wrap -- golang package to wrap things into a bit of context

control: merge -1 1019467 -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org http://czchen.info/ Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature

Bug#1019584: python3-jsonschema - unused dependencies

Package: python3-jsonschema Version: 4.6.0-3 Severity: normal python3-jsonschema got several hard-coded dependencies, which don't seem to be used at all by the code. python3-attr: shouldn't this be found by the normal stuff? python3-pkg-resources: the jsonschema tool does not entrypoints, so no

Bug#1019582: LLVM 15 ftbfs on riscv64

Package: src:llvm-toolchain-15 Version: 1:15.0.0-1~exp1 Severity: important Tags: sid bookworm I assume these GPU targets are not be built on riscv64? [...] dh_install --fail-missing dh_install: warning: Please use dh_missing --list-missing/--fail-missing instead dh_install: warning: This

Bug#1019573: libreoffice-calc: Fake warning : The master password is stored in an outdated format, you should refresh it.

Le 12/09/2022 à 13:17, Rene Engelhard a écrit : tag - moreinfo reassign 1019573 libreoffice-core retitle 1019573 warning : The master password is stored in an outdated format, you should refresh it. found 1019573 1:7.0.4-4+deb11u2 found 1019573 1:7.3.3~rc1-1 severity 1019573 minor thanks

Bug#877414: systemd: please include a /var/log/README like Fedora has

Am 12.09.22 um 11:59 schrieb Holger Levsen: On Mon, Sep 12, 2022 at 11:07:06AM +0200, Michael Biebl wrote: We could either ship this symlink directly in the package as well (so dpkg will remove it if the package is uninstalled), or add an explicit cleanup to systemd.postrm. sounds like

Bug#1019573: libreoffice-calc: Fake warning : The master password is stored in an outdated format, you should refresh it.

Hi, Am 12.09.22 um 16:53 schrieb Rpnpif: Now, I understand the objective. What is confusing is that this message is untranslated Well, I didn't collect (all) the translations, and didn't try to get the 7.3.x/7.4x translations then into 7.0.4, indeed. I think a security fix shouldn't wait

  1   2   >