Processed: ruby-spamcheck: cannot use ruby-grpc package

2021-06-12 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 966653 Bug #989786 [ruby-spamcheck] ruby-spamcheck: cannot use ruby-grpc package 989786 was not blocked by any bugs. 989786 was not blocking any bugs. Added blocking bug(s) of 989786: 966653 -- 989786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9

Bug#989786: ruby-spamcheck: cannot use ruby-grpc package

2021-06-12 Thread Pirate Praveen
Package: ruby-spamcheck Version: 0.1.0+git20210519.2084b44-2 Severity: grave Control: block -1 by 966653 Since the only reverse dependency of ruby-spamcheck is gitlab and gitlab does not work with debian's ruby-grpc package (see #966653), dependency on ruby-grpc is removed. It will be added bac

Bug#989767: marked as done (libesmtp: Not built on buildd: arch arm64 binaries: needs a source only upload)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jun 2021 01:48:29 + with message-id and subject line Bug#989767: fixed in libesmtp 1.1.0-2 has caused the Debian Bug report #989767, regarding libesmtp: Not built on buildd: arch arm64 binaries: needs a source only upload to be marked as done. This means that you c

Bug#987388: Crash of amdgpu on Debian 11 Bullseye

2021-06-12 Thread Maxime G.
Hello. The linux-image-5.10.0-7 update fell in testing (bullseye) and it includes some patches for amdgpu. I do many tasks with amdgpu (games, vaapi decoding, vaapi encoding, gpu computations), I will report if any problem resurfaces. Thanks ! Max.

Bug#989700: marked as done (bluez: CVE-2021-3588)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jun 2021 20:18:24 + with message-id and subject line Bug#989700: fixed in bluez 5.55-3.1 has caused the Debian Bug report #989700, regarding bluez: CVE-2021-3588 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#989614: marked as done (bluez: CVE-2021-0129 CVE-2020-26558)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jun 2021 20:18:24 + with message-id and subject line Bug#989614: fixed in bluez 5.55-3.1 has caused the Debian Bug report #989614, regarding bluez: CVE-2021-0129 CVE-2020-26558 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#989344: ogre-1.12: diff for NMU version 1.12.10+dfsg2-1.1

2021-06-12 Thread s . schmeisser
I'm sorry for messing this up, this is my first official debian package. Your patch looks good. Could you please also open a MR on salsa for it? Or commit it right away if you have the permissions. I'm currently on vacation but can do further cleanup if required and an update to 1.12.12 starting

Bug#989776: auto-apt-proxy: autopkgtest regression since June 2021

2021-06-12 Thread Paul Gevers
Source: auto-apt-proxy Version: 13.2 Severity: serious Tags: bullseye-ignore User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org Dear Antonio, Your package has an autopkgtest, great! However, since somewhere in May or June it started to fail [1]. Looking

Bug#989662: marked as done (connman: CVE-2021-33833: dnsproxy: Check the length of buffers before memcpy)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jun 2021 18:32:07 + with message-id and subject line Bug#989662: fixed in connman 1.36-2.1~deb10u2 has caused the Debian Bug report #989662, regarding connman: CVE-2021-33833: dnsproxy: Check the length of buffers before memcpy to be marked as done. This means that

Bug#983684: marked as done (mupdf: CVE-2021-3407)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jun 2021 18:32:08 + with message-id and subject line Bug#983684: fixed in mupdf 1.14.0+ds1-4+deb10u3 has caused the Debian Bug report #983684, regarding mupdf: CVE-2021-3407 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#989344: ogre-1.12: diff for NMU version 1.12.10+dfsg2-1.1

2021-06-12 Thread Jochen Sprickerhof
* Jochen Sprickerhof [2021-06-12 17:50]: I've prepared an NMU for ogre-1.12 (versioned as 1.12.10+dfsg2-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I've chosen a short delay as this needs to pass the NEW queue, hope that is fine. The release team

Processed: ogre-1.12: diff for NMU version 1.12.10+dfsg2-1.1

2021-06-12 Thread Debian Bug Tracking System
Processing control commands: > tags 989344 + patch Bug #989344 [libogre-1.12] libogre-1.12: package name does not match soname Added tag(s) patch. > tags 989344 + pending Bug #989344 [libogre-1.12] libogre-1.12: package name does not match soname Added tag(s) pending. -- 989344: https://bugs.deb

Bug#989344: ogre-1.12: diff for NMU version 1.12.10+dfsg2-1.1

2021-06-12 Thread Jochen Sprickerhof
Control: tags 989344 + patch Control: tags 989344 + pending Dear maintainer, I've prepared an NMU for ogre-1.12 (versioned as 1.12.10+dfsg2-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I've chosen a short delay as this needs to pass the NEW queue,

Processed: re: dh-cargo: please refresh json timestamps

2021-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Found 932172 17 Bug #932172 {Done: Sylvestre Ledru } [dh-cargo] dh-cargo: please refresh json timestamps Marked as found in versions dh-cargo/17. > Thanks Stopping processing here. Please contact me if you need assistance. -- 932172: https://bu

Bug#932172: dh-cargo: please refresh json timestamps

2021-06-12 Thread peter green
Found 932172 17 Thanks While preparing a stable update for a rust package to fix a FTBFS I discovered that this bug also affects buster, meaning that attempts to update rust packages in buster (e.g. to fix FTBFS introduced by rustc updates) result in rejections. The fix applies cleanly to the

Processed: tag as needing help

2021-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 989774 help Bug #989774 [ruby-pg-query] ruby-pg-query: no longer works with ruby-google-protobuf Added tag(s) help. > End of message, stopping processing here. Please contact me if you need assistance. -- 989774: https://bugs.debian.org/cg

Processed: Re: Bug#989357: nmu: ros-rviz_1.14.4+dfsg-3

2021-06-12 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 989344 Bug #989357 [release.debian.org] nmu: ros-rviz_1.14.4+dfsg-3 989357 was not blocked by any bugs. 989357 was not blocking any bugs. Added blocking bug(s) of 989357: 989344 -- 989357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989357 Debian

Bug#989774: ruby-pg-query: no longer works with ruby-google-protobuf

2021-06-12 Thread Pirate Praveen
Package: ruby-pg-query Version: 2.0.3-1 Severity: grave Control: affects -1 gitlab gitaly ruby-gitlab-labkit gitlab-sidekiq service fails to start when ruby-google-protobuf package is used, works with gem install -v 3.17.1 google-protobuf and removing ruby-google-protobuf Possibly the debian

Processed: ruby-pg-query: no longer works with ruby-google-protobuf

2021-06-12 Thread Debian Bug Tracking System
Processing control commands: > affects -1 gitlab gitaly ruby-gitlab-labkit Bug #989774 [ruby-pg-query] ruby-pg-query: no longer works with ruby-google-protobuf Added indication that 989774 affects gitlab, gitaly, and ruby-gitlab-labkit -- 989774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#988603: marked as done (libxml2: CVE-2021-3541: Exponential entity expansion attack bypasses all existing protection mechanisms)

2021-06-12 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jun 2021 10:47:08 + with message-id and subject line Bug#988603: fixed in libxml2 2.9.4+dfsg1-7+deb10u2 has caused the Debian Bug report #988603, regarding libxml2: CVE-2021-3541: Exponential entity expansion attack bypasses all existing protection mechanisms to be