Processing control commands:
> affects -1 src:git
Bug #980574 [src:gitbrute] gitbrute: autopkgtest needs update for new version
of git
Added indication that 980574 affects src:git
--
980574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980574
Debian Bug Tracking System
Contact
Source: gitbrute
Version: 0~12-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git
Dear maintainer(s),
With a recent upload of git the autopkgtest of gitbrute
Package: golang-github-cznic-lldb
Version: 1.0.1-1
Severity: serious
Dear Maintainer,
golang-github-cznic-lldb ftbfs in current sid:
I: Building the package
I: Running cd /build/golang-github-cznic-lldb-1.0.1/ && env
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent"
Your message dated Wed, 20 Jan 2021 19:19:23 +
with message-id
and subject line Bug#977065: fixed in html5lib 1.1-3
has caused the Debian Bug report #977065,
regarding html5lib FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: golang-github-cznic-ql
Version: 1.0.6-1
Severity: serious
Dear Maintainer,
golang-github-cznic-ql ftbfs in current sid:
I: Building the package
I: Running cd /build/golang-github-cznic-ql-1.0.6/ && env
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent"
Processing commands for cont...@bugs.debian.org:
> severity 919917 serious
Bug #919917 [yui-compressor] yui-compressor: insufficient java dependency in
jessie
Severity set to 'serious' from 'normal'
> found 919917 2.4.8-2.1
Bug #919917 [yui-compressor] yui-compressor: insufficient java
Processing commands for cont...@bugs.debian.org:
> reopen 978251
Bug #978251 {Done: Lucas Nussbaum } [src:ruby-mysql2]
ruby-mysql2: FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
Bug reopened
Ignoring request to alter fixed versions of bug #978251 to the same values
hi Gregor,
On Thu, Dec 31, 2020 at 02:13:53AM +0100, gregor herrmann wrote:
> I've uploaded -2 in order to
> - see what the buildds say
> - get more diagnostics
> - get a .buildinfo file
>
> And the result is:
> - it built on my laptop and on the buildd
> - we should have a .buildinfo file :)
I am pretty knowledgable in C and dynamic linking.
In theory, I would also be very happy to contribute to maintaining this
package. However, time is an ongoing issue and I would need to learn to
make packages for Debian.
I noticed how old was this patch. It doesn't feel very healthy to keep
some
Your message dated Wed, 20 Jan 2021 18:34:23 +
with message-id
and subject line Bug#980448: fixed in ucx 1.10.0~rc1-6
has caused the Debian Bug report #980448,
regarding ucx: breaks openmpi autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 20 Jan 2021 18:34:01 +
with message-id
and subject line Bug#979480: fixed in openmpi 4.1.0-7
has caused the Debian Bug report #979480,
regarding mpi4py: autopkgtest failure on arm64, armhf and ppc64el
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 20 Jan 2021 18:34:01 +
with message-id
and subject line Bug#979041: fixed in openmpi 4.1.0-7
has caused the Debian Bug report #979041,
regarding libopempi3: aborts python code due to libfabric fork() issues
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jan 2021 18:34:07 +
with message-id
and subject line Bug#978066: fixed in pmix 4.0.0-4
has caused the Debian Bug report #978066,
regarding pmix: breaks openmpi autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> tags #976305 unreproducible moreinfo
Bug #976305 [src:atop] atop: FTBFS twice in a row
Added tag(s) unreproducible and moreinfo.
> severity #976305 important
Bug #976305 [src:atop] atop: FTBFS twice in a row
Severity set to 'important' from
tags #976305 unreproducible moreinfo
severity #976305 important
thanks
On Thu, Dec 03, 2020 at 03:54:50AM +0100, Andreas Beckmann wrote:
> atop FTBFS twice in a row because 'make clean' does not remove the
> generated 'atopsar':
I cannot reproduce this with two debuilds in a row and two fakeroot
Your message dated Wed, 20 Jan 2021 18:03:57 +
with message-id
and subject line Bug#692311: fixed in libxml-stream-perl 1.24-4
has caused the Debian Bug report #692311,
regarding FTBFS if non-local network communication is forbidden
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jan 2021 18:03:57 +
with message-id
and subject line Bug#692311: fixed in libxml-stream-perl 1.24-4
has caused the Debian Bug report #692311,
regarding libxml-stream-perl FTBFS on IPV6-only buildds
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tag -1 pending
Bug #692311 [src:libxml-stream-perl] FTBFS if non-local network communication
is forbidden
Bug #980481 [src:libxml-stream-perl] libxml-stream-perl FTBFS on IPV6-only
buildds
Added tag(s) pending.
Added tag(s) pending.
--
692311:
Control: tag -1 pending
Hello,
Bug #692311 in libxml-stream-perl 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:
On Wed, 20 Jan 2021 13:06:56 -0300, Thadeu Lima de Souza Cascardo wrote:
> Here is a suggested patch. Can someone forward that upstream? I would
> like to get this fixed as soon as possible, so would rather upload an
> NMU with this patch in the next couple of days anyway. But I would
>
Processing control commands:
> tag -1 pending
Bug #978288 [src:pytest-mock] pytest-mock: FTBFS: dpkg-buildpackage: error:
dpkg-source -b . subprocess returned exit status 2
Added tag(s) pending.
--
978288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978288
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #978288 in pytest-mock 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:
With 06-fix-m-option.patch you add these two lines in
src/osdsh/controlsh.c:load_plugin():
mod_mixerdev = dlsym(module, "mixerdevice");
*mod_mixerdev = mixerdevice;
I presume what you intended to accomplish here is to tell the module
which user-specified mixer device to use since
Hi,
On Mon, Jan 11, 2021 at 05:23:50PM +0100, Michel Le Bihan wrote:
[...]
> The window for getting in Bullseye will close soon and this issue is
> blocking. Will you be able to maintain Chromium in Bullseye? I can help
> with it if needed.
Thanks for you both which were involved in the last two
Your message dated Wed, 20 Jan 2021 17:33:08 +0100
with message-id <2bbd01af-be6c-ac08-7f08-6927d1727...@offensive-security.com>
and subject line no autopkgtest failure with version 20.8.0-1
has caused the Debian Bug report #978522,
regarding ospd-openvas' autopkg tests fail
to be marked as done.
Source: libxml-stream-perl
Followup-For: Bug #692311
Here is a suggested patch. Can someone forward that upstream? I would
like to get this fixed as soon as possible, so would rather upload an
NMU with this patch in the next couple of days anyway. But I would
appreciate this being forwarded on my
Processing commands for cont...@bugs.debian.org:
> found 980564 87.0.4280.141-0.1~deb10u1
Bug #980564 [src:chromium] chromium: 88.0.4324.96 stable release
Marked as found in versions chromium/87.0.4280.141-0.1~deb10u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Package: php-enum
Version: 4.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
php-enum/experimental recently started to FTBFS:
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-enum-4.2.0'
php --define zend.assertions=1 /usr/bin/phpunit
Source: chromium
Version: 87.0.4280.141-0.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi
For Details please see
https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop_19.html
covering
Your message dated Wed, 20 Jan 2021 16:04:05 +
with message-id
and subject line Bug#979297: fixed in python-llfuse 1.3.8+dfsg-1
has caused the Debian Bug report #979297,
regarding python-llfuse FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 20 Jan 2021 15:49:50 +
with message-id
and subject line Bug#944505: fixed in fonts-beteckna 0.5-3
has caused the Debian Bug report #944505,
regarding FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
to be marked as done.
This means that you
Your message dated Wed, 20 Jan 2021 15:36:35 +
with message-id
and subject line Bug#952336: fixed in photocollage 1.4.3-2.2
has caused the Debian Bug report #952336,
regarding photocollage: FTBFS: dh: error: unable to load addon python3: Can't
locate Debian/Debhelper/Sequence/python3.pm in
Your message dated Wed, 20 Jan 2021 15:18:51 +
with message-id
and subject line Bug#980281: fixed in q2-dada2 2020.11.1-3
has caused the Debian Bug report #980281,
regarding q2-dada2: autopkgtest failure: missing depends python3-biom-format
to be marked as done.
This means that you claim
Hi Alastair
On Wed, 20 Jan 2021 at 16:44, Alastair McKinstry
wrote:
> Can these bugs be closed ?
Not until they are fixed.
> pmix tests are failing because of an openmpi bug , but its no longer due
> to pmix.
>
> Ditto, ucx errors that caused the failure are fixed in openmpi-4.1.0-6.
ucx
Hi Graham
Can these bugs be closed ?
pmix tests are failing because of an openmpi bug , but its no longer due
to pmix.
Ditto, ucx errors that caused the failure are fixed in openmpi-4.1.0-6.
openmpi 4.1.0-6 fails on libfabric:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979041
I'm
Package: kgames
Version: 1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
On Tue, 19 Jan 2021 17:12:17 +0100 Roland Rosenfeld
wrote:
Package: chromium
Version: 87.0.4280.141-0.1~deb10u1
Severity: serious
Tags: buster
Dear Maintainer,
I upgraded chromium on Debian stable (buster) from
83.0.4103.116-1~deb10u3 to 87.0.4280.141-0.1~deb10u1.
After this upgrade chromium
Package: lutris
Version: 0.5.8.2-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: witold.bary...@gmail.com
$ lutris
Traceback (most recent call last):
File "/usr/games/lutris", line 54, in
from lutris.gui.application import Application # pylint:
Your message dated Wed, 20 Jan 2021 13:13:26 +0100
with message-id
and subject line Re: Bug#980038: marked as pending in kodi
has caused the Debian Bug report #980038,
regarding kodi-pvr-hts: kodi crashes when switching to TV with pvr hts plugin
activated and configured
to be marked as done.
Your message dated Wed, 20 Jan 2021 10:34:12 +
with message-id
and subject line Bug#958619: fixed in memlockd 1.2.1
has caused the Debian Bug report #958619,
regarding memlockd: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Your message dated Wed, 20 Jan 2021 09:48:28 +
with message-id
and subject line Bug#962203: fixed in debdelta 0.66
has caused the Debian Bug report #962203,
regarding DeprecationWarning: isAlive() is deprecated, use is_alive() instead
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jan 2021 09:48:28 +
with message-id
and subject line Bug#962203: fixed in debdelta 0.66
has caused the Debian Bug report #962203,
regarding Python deprecation warning
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 20 Jan 2021 09:48:28 +
with message-id
and subject line Bug#954420: fixed in debdelta 0.66
has caused the Debian Bug report #954420,
regarding DeprecationWarning: isAlive() is deprecated, use is_alive() instead
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jan 2021 09:48:28 +
with message-id
and subject line Bug#954420: fixed in debdelta 0.66
has caused the Debian Bug report #954420,
regarding Python deprecation warning
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> severity -1 normal
Bug #974778 [src:llvmlite] llvmlite: stop using llvm-toolchain-10
Bug #974824 [src:llvmlite] llvmlite: stop using llvm-toolchain-10
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
--
974778:
Control: severity -1 normal
Llvmlite has switched back to using LLVM 9 in 0.35.0-2.
Lowering severity, but leaving this bug open for switching to LLVM 11.
201 - 246 of 246 matches
Mail list logo
