Processing commands for cont...@bugs.debian.org:
> tags 1012535 + pending
Bug #1012535 [src:cantor] cantor: fails to build from source
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012535:
Your message dated Thu, 09 Jun 2022 05:03:55 +
with message-id
and subject line Bug#1012513: fixed in apache2 2.4.54-1
has caused the Debian Bug report #1012513,
regarding apache2: CVE-2022-31813 CVE-2022-26377 CVE-2022-28614 CVE-2022-28615
CVE-2022-29404 CVE-2022-30522 CVE-2022-30556
to be
Dear Michael,
Thanks for the proposed patch. I will try to review and submit a new
package version is the coming days.
Saludos,
Javier
El mié, 8 jun 2022 20:45, M. Buecher escribió:
> I had a look at the package source and only the paths in the file
> debian/rules [1] have to be changed.
>
Control: tag -1 pending
Hello,
Bug #1011863 in guix reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #1011863 [src:guix] guix: FTBFS: tests fail
Added tag(s) pending.
--
1011863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 997264 + patch
Bug #997264 [src:seriousproton] seriousproton: FTBFS: collisionable.h:5:10:
fatal error: Box2D/Box2D.h: No such file or directory
Added tag(s) patch.
> --
Stopping processing here.
Please contact me if you need assistance.
Attached is a patch to fix Debian bug #997264.
--
Plasma
seriousproton_2020.01.15+dfsg-1.1.debdiff
Description: Binary data
The Debian packaged version is much older than the current version.
On Wednesday, June 8, 2022, Arnaldo Pirrone wrote:
> Package: chirp
> Version: 1:20200227+py3+20200213-3
> Severity: grave
> X-Debbugs-Cc: it9...@gmail.com
>
> Just tried using this software to program my radio and found out it
Package: libworkflow1
Version: 0.9.10-1
Severity: serious
Hi!
This package has several problems:
- It contains a shared library without a SOVERSION
,---
$ objdump -p /usr/lib/x86_64-linux-gnu/libworkflow.so | grep SONAME
SONAME libworkflow.so
`---
This means any
Your message dated Wed, 08 Jun 2022 22:49:53 +
with message-id
and subject line Bug#1011869: fixed in golang-github-containers-buildah
1.23.1+ds1-3
has caused the Debian Bug report #1011869,
regarding golang-github-containers-buildah: FTBFS: make[1]: ***
[debian/rules:26:
Control: tag -1 pending
Hello,
Bug #1011869 in golang-github-containers-buildah reported by you has been fixed
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #1011869 [src:golang-github-containers-buildah]
golang-github-containers-buildah: FTBFS: make[1]: *** [debian/rules:26:
override_dh_auto_build] Error 25
Added tag(s) pending.
--
1011869:
My hunch might have been correct, the fresh upload did build successfully
on buildds. yay!
On Sun, Jun 5, 2022 at 7:12 AM Reinhard Tartler wrote:
> Just a hunch, is it possible that your build environment did not have the
> package 'ca-certificates' present whereas mine does?
>
> I wonder
Your message dated Wed, 08 Jun 2022 21:35:13 +
with message-id
and subject line Bug#1011051: fixed in openssl 3.0.3-7
has caused the Debian Bug report #1011051,
regarding libssl3: upgrade to libssl3 broke my dovecot setup
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Jun 2022 21:20:59 +
with message-id
and subject line Bug#1011875: fixed in
golang-github-opencontainers-runtime-tools 0.9.0+git20220423.g0105384-2
has caused the Debian Bug report #1011875,
regarding golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test:
Processing control commands:
> forwarded 1011863 https://issues.guix.gnu.org/55506
Bug #1011863 [src:guix] guix: FTBFS: tests fail
Set Bug forwarded-to-address to 'https://issues.guix.gnu.org/55506'.
> tags 1011863 fixed-upstream
Bug #1011863 [src:guix] guix: FTBFS: tests fail
Added tag(s)
Control: forwarded 1011863 https://issues.guix.gnu.org/55506
Control: tags 1011863 fixed-upstream
On 2022-06-08, Vagrant Cascadian wrote:
> On 2022-05-26, Vagrant Cascadian wrote:
>> On 2022-05-26, Lucas Nussbaum wrote:
>>> During a rebuild of all packages in sid, your package failed to build
>>>
On 2022-05-26, Vagrant Cascadian wrote:
> On 2022-05-26, Lucas Nussbaum wrote:
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
...
>>> PASS: tests/channels.scm - latest-channel-instances, missing introduction
>>> for 'guix'
>>> FAIL: tests/channels.scm -
Package: chirp
Version: 1:20200227+py3+20200213-3
Severity: grave
X-Debbugs-Cc: it9...@gmail.com
Just tried using this software to program my radio and found out it stopped
working. I remember it was everything fine a few months ago. Probably this is
caused by changes in Python 3.10.5
-- System
Control: tag -1 pending
Hello,
Bug #1011875 in golang-github-opencontainers-runtime-tools reported by you has
been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #1011875 [src:golang-github-opencontainers-runtime-tools]
golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 8
github.com/opencontainers/runtime-tools/api/socket
Source: cantor
Version: 4:21.12.3-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
Hi,
As part of the pseudo libluajit transition [1] I scheduled a rebuild
of cantor. It failed to build everywhere [2]. As can be seen on the
reproducible build project page, the build already fails in
Your message dated Wed, 08 Jun 2022 19:19:36 +
with message-id
and subject line Bug#1009431: fixed in skimage 0.18.3-3
has caused the Debian Bug report #1009431,
regarding skimage: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.9 3.10" returned exit code 13
to be marked
Your message dated Wed, 08 Jun 2022 19:19:36 +
with message-id
and subject line Bug#1010430: fixed in skimage 0.18.3-3
has caused the Debian Bug report #1010430,
regarding tifffile breaks skimage autopkgtest: asarray() got an unexpected
keyword argument 'multifile'
to be marked as done.
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011306,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011309,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011303,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011301,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011300,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011299,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Your message dated Wed, 8 Jun 2022 21:14:30 +0200
with message-id
and subject line libluajit2 is replacing libluajit on ppc64el
has caused the Debian Bug report #1011296,
regarding please replace (build) dependency luajit with lua on ppc64el
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> tags 1012513 + upstream
Bug #1012513 [src:apache2] apache2: CVE-2022-31813 CVE-2022-26377
CVE-2022-28614 CVE-2022-28615 CVE-2022-29404 CVE-2022-30522 CVE-2022-30556
Added tag(s) upstream.
> found 1012513 2.4.53-2
Bug #1012513 [src:apache2]
Processing commands for cont...@bugs.debian.org:
> tags 1012512 + upstream
Bug #1012512 [src:libengine-gost-openssl1.1] libengine-gost-openssl1.1:
CVE-2022-29242
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012512:
Your message dated Wed, 08 Jun 2022 18:49:04 +
with message-id
and subject line Bug#1007225: fixed in ruby-image-processing 1.10.3-2
has caused the Debian Bug report #1007225,
regarding ruby-image-processing: CVE-2022-24720
to be marked as done.
This means that you claim that the problem has
On Wed, Jun 08, 2022 at 07:51:28PM +0200, Yadd wrote:
> Hi,
>
> those CVEs are tagged low/moderate by upstream, why did you tag this bug as
> grave ?
Anything moderate or above should get fixed by the next Debian release IOW RC
severity.
Cheers,
Moritz
I had a look at the package source and only the paths in the file
debian/rules [1] have to be changed.
Extend all `lib/$(DEB_HOST_MULTIARCH)` to
`lib/$(DEB_HOST_MULTIARCH)/security` (added suffix `/security`).
[1] https://sources.debian.org/src/libpam-chroot/0.9-5/debian/rules/
Here the
Hi,
those CVEs are tagged low/moderate by upstream, why did you tag this bug as
grave ?
Cheers,
Yadd
Le Mercredi, Juin 08, 2022 17:49 CEST, Moritz Mühlenhoff a
écrit:
> Source: apache2
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
>
> Hi,
>
> The following
Package: libpam-chroot
Version: 0.9-5
Followup-For: Bug #991113
X-Debbugs-Cc: maddes+deb...@maddes.net
Dear Maintainer,
the library pam_chroot.so is installed in the wrong location, therefore it
cannot be loaded.
This prevents anyone (incl. root) to log into systems that require that module.
Your message dated Wed, 08 Jun 2022 16:48:56 +
with message-id
and subject line Bug#1012510: fixed in firejail 0.9.68-4
has caused the Debian Bug report #1012510,
regarding firejail: CVE-2022-31214: local root exploit reachable via --join
logic
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> severity 1012361 wishlist
Bug #1012361 [electrum] New upstream version 4.2.2
Severity set to 'wishlist' from 'critical'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1012361:
Control: tags -1 + patch ftbfs
Control: unblock -1 by 1010595
The attached patch, based on an imageio upstream commit [1], fixes the
issue with Pillow 9.1 for me.
[1] https://github.com/imageio/imageio/pull/775
Description: handle PIL palettes with <256 colors
based on
Processing control commands:
> tags -1 + patch ftbfs
Bug #1009431 [src:skimage] skimage: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p "3.9 3.10" returned exit code 13
Added tag(s) patch.
> unblock -1 by 1010595
Bug #1009431 [src:skimage] skimage: FTBFS: dh_auto_test: error:
Control: tags -1 + fixed-upstream patch
On Wed, 08 Jun 2022 at 12:53:42 +0100, Simon McVittie wrote:
> I think the solution to this might be upstream commit acbf56d7 (trying it
> now on the ppc64el porterbox).
That seems to have been successful. MR available here:
Processing control commands:
> tags -1 + fixed-upstream patch
Bug #1012494 [gdb] gdb: FTBFS on ppc family: No rule to make target 'info' in
build/default/sim/ppc
Added tag(s) patch and fixed-upstream.
--
1012494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012494
Debian Bug Tracking
Your message dated Wed, 08 Jun 2022 16:04:19 +
with message-id
and subject line Bug#1012505: fixed in debmutate 0.53
has caused the Debian Bug report #1012505,
regarding debmutate: missing runtime python3-pcre dependency?
to be marked as done.
This means that you claim that the problem has
On Wed, Jun 08, 2022 at 05:41:00PM +0300, Timo Aaltonen wrote:
Did you have 2.7.0 at some point?
2.7.0-1 was installed 2022-05-27
2.7.0-1+b1 was installed 2022-05-29
no issues with either of those; I reverted to 2.6.3 just because it was
easier to grab from the mirrors.
Source: apache2
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for apache2.
CVE-2022-31813[0]:
| Apache HTTP Server 2.4.53 and earlier may not send the X-Forwarded-*
| headers to the origin server based on client side
Source: libengine-gost-openssl1.1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for libengine-gost-openssl1.1.
CVE-2022-29242[0]:
| GOST engine is a reference implementation of the Russian GOST crypto
| algorithms for
Processing commands for cont...@bugs.debian.org:
> found 1012510 0.9.64.4-2
Bug #1012510 [src:firejail] firejail: CVE-2022-31214: local root exploit
reachable via --join logic
Marked as found in versions firejail/0.9.64.4-2.
> thanks
Stopping processing here.
Please contact me if you need
Source: firejail
Version: 0.9.68-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for firejail.
CVE-2022-31214[0]:
| local root exploit reachable via --join logic
If
Michael Stone kirjoitti 8.6.2022 klo 15.44:
Package: sssd
Version: 2.7.1-1
Severity: critical
Justification: breaks the whole system
Installing sssd 2.7.1-1 causes IPA/krb5 authentication to fail with messages
such as the following in /var/log/sssd/sssd_DOMAIN.log
(2022-06-07 18:31:36):
Processing control commands:
> reassign -1 libsepol2 3.4-1
Bug #1012503 [selinux-policy-default] selinux-policy-default - Fails to
install: No such file or directory
Bug reassigned from package 'selinux-policy-default' to 'libsepol2'.
No longer marked as found in versions
Source: debmutate
Version: 0.52
Severity: serious
Hello, building lintian-brush now fails with something like:
fixer test: no-watch-file for debian-watch-file-old-format ... Traceback (most
recent call last):
File "/<>/fixers/debian-watch-file-old-format.py", line 5, in
from
Package: selinux-policy-default
Version: 2:2.20220520-1
Severity: serious
Moin
selinux-policy-default fails to install into a basic Debian unstable
system:
Setting up selinux-policy-default (2:2.20220520-1) ...
Updating selinux default policy (this step might take a
On Wed, May 18 2022, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the shiboken2 package:
>
> #1010747: Unusable with current python version
>
> It has been closed by Debian FTP Masters
> (reply to Georges Khaznadar
> ).
Package: sssd
Version: 2.7.1-1
Severity: critical
Justification: breaks the whole system
Installing sssd 2.7.1-1 causes IPA/krb5 authentication to fail with messages
such as the following in /var/log/sssd/sssd_DOMAIN.log
(2022-06-07 18:31:36): [be[DOMAIN]] [krb5_auth_done] (0x3f7c0): [RID#10]
Your message dated Wed, 08 Jun 2022 12:28:09 +
with message-id
and subject line Bug#1012497: fixed in rust-rustyline 6.3.0-4
has caused the Debian Bug report #1012497,
regarding librust-rustyline-dev: depends on missing package
librust-nix-0.23+default-dev
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> found 1012467 0.8.0-1
Bug #1012467 [src:davix] davix ships complete lyrics of "Never Gonna Give You
Up"
Marked as found in versions davix/0.8.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012467:
Source: finalcif
Version: 104+dfsg-1
Severity: serious
Tags: ftbfs
finalcif FTBFS with python3-gemmi 0.5.5+ds:
self =
@property
def is_centrosymm(self) -> bool:
"""
Whether a structuere is centro symmetric or not.
"""
if not self.symmops or self.symmops
Package: librust-rustyline-dev
Version: 6.3.0-3
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As sbject says, package is impossible to install.
-BEGIN PGP SIGNATURE-
On Wed, 08 Jun 2022 at 12:24:45 +0100, Simon McVittie wrote:
> > make[4]: Entering directory '/<>/build/default/sim/ppc'
> > make[4]: *** No rule to make target 'info'. Stop.
I think the solution to this might be upstream commit acbf56d7 (trying it
now on the ppc64el porterbox).
That commit is
Source: inkscape
Version: 1.2-1
Severity: serious
Tags: ftbfs
Forwarded: https://gitlab.com/inkscape/inkscape/-/issues/3554
https://buildd.debian.org/status/fetch.php?pkg=inkscape=arm64=1.2-1=1653329867=0
https://buildd.debian.org/status/fetch.php?pkg=inkscape=ppc64el=1.2-1=1653326620=0
Package: gdb
Version: 11.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-powe...@lists.debian.org
User: debian-powe...@lists.debian.org
Usertags: ppc64el powerpc ppc64
gdb 11 is not migrating to testing because
Your message dated Wed, 08 Jun 2022 09:35:40 +
with message-id
and subject line Bug#1012479: fixed in paramcoq 1.1.3-6
has caused the Debian Bug report #1012479,
regarding libcoq-paramcoq-ocaml: missing Breaks+Replaces: libcoq-paramcoq (<<
1.1.3-5)
to be marked as done.
This means that you
Your message dated Wed, 08 Jun 2022 09:03:51 +
with message-id
and subject line Bug#1011808: fixed in ffcall 2.4-2
has caused the Debian Bug report #1011808,
regarding ffcall: FTBFS: make[4]: *** [Makefile:1210: asyncsafe-spin.lo] Error
63
to be marked as done.
This means that you claim
A request for the removal of sysbench from ppc64el has been filed in
order to allow the recent upload to migrate to testing, see #1012484.
pgp0U1RcwU9fK.pgp
Description: OpenPGP digital signature
Processing control commands:
> retitle -1 grub2: CVE-2022-28735 grub2: shim_lock verifier allows non-kernel
> files to be loaded
Bug #1001057 [grub2] grub2: hold 2.06 in unstable for now
Changed Bug title to 'grub2: CVE-2022-28735 grub2: shim_lock verifier allows
non-kernel files to be loaded'
Control: retitle -1 grub2: CVE-2022-28735 grub2: shim_lock verifier allows
non-kernel files to be loaded
On Fri, Dec 03, 2021 at 11:17:26AM +, Colin Watson wrote:
> Package: grub2
> Version: 2.06-2
> Severity: serious
> Justification: maintainer says so
>
> GRUB 2.06 is a pretty big change
Source: rdflib
Version: 6.1.1
Severity: critical
Tags: security upstream
Forwarded: https://github.com/RDFLib/rdflib/issues/1844
Hello,
rdflib will attempt to resolve any URL in @context in POSTed JSON-LD
messages, leading to various probing and DDoS vectors, see the upstream
discussion [1].
69 matches
Mail list logo
