Le 13 novembre 2020 00:26:16 GMT+01:00, Norbert Preining
a écrit :
>Hi Scarlett, hi all,
Hi !
>> However, it seems that because of the ABI break in libkscreenlocker5
>> there may need to be more specific dependency requirements (like
>
>I suggest the following change in kscreenlocker debian/
Source: rust-zoxide
Version: 0.4.3-1
Severity: serious
rust-zoxide contains an invalid Section for the Source package:
| Source: rust-zoxide
| Section: FIXME-(source.section)
| Priority: optional
| Build-Depends: debhelper (>= 11),
| dh-cargo (>= 18),
| cargo:native,
| rustc:native,
| libstd-
Source: biosig4c++
Version: 1.9.5-1
Severity: serious
- Forwarded message from Debian FTP Masters
-
From: Debian FTP Masters
To: mipsel Build Daemon
Date: Fri, 13 Nov 2020 07:18:34 +
Subject: biosig4c++_1.9.5-1+b2_mipsel-buildd.changes REJECTED
Message-Id:
Version check failed:
Processing commands for cont...@bugs.debian.org:
> reassign 956336 src:bkchem
Bug #956336 [bkchem] depends on python-pil which is being removed in bullseye
(testing)
Bug reassigned from package 'bkchem' to 'src:bkchem'.
No longer marked as found in versions bkchem/0.13.0-6.
Ignoring request to al
Your message dated Fri, 13 Nov 2020 06:49:06 +
with message-id
and subject line Bug#973151: fixed in termshark 2.1.1-1
has caused the Debian Bug report #973151,
regarding termshark: FTBFS: src/github.com/gcla/termshark/tty/tty.go:31:42:
cannot use &t.tiosp (type *syscall.Termios) as type *uni
Your message dated Fri, 13 Nov 2020 05:21:15 +
with message-id
and subject line re: libjogl2-java, build-depends no longer satisfiable on
32-bit architectures.
has caused the Debian Bug report #972478,
regarding libjogl2-java, build-depends no longer satisfiable on 32-bit
architectures.
to b
Source: systemd
Version: 247~rc2-1
Severity: serious
User: debian-m...@lists.debian.org
Usertags: mipsel
X-Debbugs-Cc: debian-m...@lists.debian.org
Hi mips porters,
systemd in experimental FTBFS on mipsel and mips64el
https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=mips64el&ver=247%7E
Your message dated Fri, 13 Nov 2020 01:18:25 +
with message-id
and subject line Bug#974589: fixed in pam-python 1.0.9-1
has caused the Debian Bug report #974589,
regarding pam-python: broken autopkgtest.
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 2020-11-12 23:20, Matthias Klumpp wrote:
You want this patch for AppStream:
https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
But only comments are changed there!?
Still... I built AppStream with that commit applied:
https://launchpad.net/~gunnarhj/+archiv
Hi,
Am Donnerstag, den 12.11.2020, 18:21 +0100 schrieb Pallai Roland:
> Hi Markus,
>
> The problem is still the same here:
Thanks for your debug log. I have looked at every line of code again and
compared the original upstream patch from here
https://bugzilla.redhat.com/attachment.cgi?id=17227
Processing commands for cont...@bugs.debian.org:
> tags 974143 + sid bullseye
Bug #974143 {Done: Dominic Hargreaves } [libencode-arabic-perl]
libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d
modifier in transliteration operator
Added tag(s) sid and bullseye.
> tags
Hi Scarlett, hi all,
> However, it seems that because of the ABI break in libkscreenlocker5
> there may need to be more specific dependency requirements (like
I suggest the following change in kscreenlocker debian/control, Scarlett, wdyt?
diff --git a/debian/control b/debian/control
index b961e0d
[Matthias Klumpp]
> Oh, btw: Thank you all for the last messages, knowing which commands
> to run to reproduce this easily helped quite a bit with finding the
> culprit quite quickly (and I also looked in the code for other
> instances of this, but found only the ones in AsPool).
Well, thank you f
retitle 971879 "charset=Ascii" appears before the comment of the image
severity 971879 normal
thanks
In data giovedì 12 novembre 2020 23:33:17 CET, Vincent Lefevre ha scritto:
> On 2020-11-12 22:48:32 +0100, Pino Toscano wrote:
> > This is not how SONAME works, especially in a binary distro like D
Processing commands for cont...@bugs.debian.org:
> retitle 971879 "charset=Ascii" appears before the comment of the image
Bug #971879 [libexiv2-27] libexiv2-27: change in both the API and the ABI
Changed Bug title to '"charset=Ascii" appears before the comment of the image'
from 'libexiv2-27: cha
Your message dated Thu, 12 Nov 2020 22:45:51 +
with message-id
and subject line Bug#973543: fixed in nvidia-cuda-toolkit 11.1.1-1
has caused the Debian Bug report #973543,
regarding nvidia-cuda-toolkit: CVE-2020-5991
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> fixed 974563 1.1.16-1
Bug #974563 [pacemaker] corosync unable to communicate with pacemaker
1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654
Marked as fixed in versions pacemaker/1.1.16-1.
> thanks
Stopping processing here.
Please conta
On 2020-11-12 22:48:32 +0100, Pino Toscano wrote:
> This is not how SONAME works, especially in a binary distro like Debian.
> Even assuming an SONAME bump is due (which IMHO is not), the consequence
> will be:
> 1) the SONAME of the library is bumped, either by upstream or in Debian
> 2) the Debia
Am Do., 12. Nov. 2020 um 23:20 Uhr schrieb Matthias Klumpp :
> [...]
> You want this patch for AppStream:
> https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
> Basically, Python thought it could free more objects than it should
> actually have freed - not sure why
Am Do., 12. Nov. 2020 um 22:21 Uhr schrieb Gunnar Hjalmarsson
:
>
> On 2020-11-12 21:28, Petter Reinholdtsen wrote:
> > [Gunnar Hjalmarsson]
> >> Additional observations:
> >>
> >> * The testing failure in Ubuntu started around October 31.
> >>
> >> * The test-command-line script fails on amd64 and
In data giovedì 12 novembre 2020 22:25:31 CET, Vincent Lefevre ha scritto:
> Control: retitle -1 libexiv2-27: change in both the API and the ABI
> Control: severity -1 serious
>
> On 2020-10-09 03:11:19 +0200, Vincent Lefevre wrote:
> > I think that this is
> >
> > https://github.com/Exiv2/exiv
Control: clone -1 -2
Control: reassign -2 gthumb 3:3.8.0-2.1
Control: found -2 3:3.8.3-0.1
Control: retitle -2 gthumb: "charset=Ascii" appears before the comment of the
image
Control: severity -2 normal
Control: tags -2 upstream
As a summary, libexiv2-27 changed its API and ABI. So gthumb needs t
Processing control commands:
> clone -1 -2
Bug #971879 [libexiv2-27] libexiv2-27: change in both the API and the ABI
Bug 971879 cloned as bug 974608
> reassign -2 gthumb 3:3.8.0-2.1
Bug #974608 [libexiv2-27] libexiv2-27: change in both the API and the ABI
Bug reassigned from package 'libexiv2-27'
Your message dated Thu, 12 Nov 2020 21:33:25 +
with message-id
and subject line Bug#974595: fixed in node-snapdragon 0.12.0+repack-4
has caused the Debian Bug report #974595,
regarding node-snapdragon-util: missing Breaks+Replaces: node-snapdragon (<=
0.12.0+repack-2)
to be marked as done.
T
Processing control commands:
> retitle -1 libexiv2-27: change in both the API and the ABI
Bug #971879 [libexiv2-27] libexiv2-27: "charset=Ascii" appears before the
comment of the image
Changed Bug title to 'libexiv2-27: change in both the API and the ABI' from
'libexiv2-27: "charset=Ascii" appea
On 2020-11-12 21:28, Petter Reinholdtsen wrote:
[Gunnar Hjalmarsson]
Additional observations:
* The testing failure in Ubuntu started around October 31.
* The test-command-line script fails on amd64 and i386 but succeeds on
other architectures.
Is it possible to 'diff' the logs from a su
Your message dated Thu, 12 Nov 2020 21:19:00 +
with message-id
and subject line Bug#973636: fixed in golang-github-nicksnyder-go-i18n.v2
2.1.1-2
has caused the Debian Bug report #973636,
regarding
golang-github-nicksnyder-go-i18n.v2-dev,golang-github-nicksnyder-go-i18n-dev:
duplicate packag
Your message dated Thu, 12 Nov 2020 21:19:23 +
with message-id
and subject line Bug#957464: fixed in libpam-ssh 2.3+ds-2
has caused the Debian Bug report #957464,
regarding libpam-ssh: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Thu, 12 Nov 2020 21:19:43 +
with message-id
and subject line Bug#974594: fixed in node-snapdragon 0.12.0+repack-3
has caused the Debian Bug report #974594,
regarding node-snapdragon-node: missing Breaks+Replaces: node-snapdragon (<=
0.12.0+repack-2)
to be marked as done.
T
Control: tag -1 pending
Hello,
Bug #974595 in node-snapdragon 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:
https://salsa.debian.org/js-team/node-snapdragon/-/commit/df2920230dfb21142
Processing control commands:
> tag -1 pending
Bug #974595 [node-snapdragon] node-snapdragon-util: missing Breaks+Replaces:
node-snapdragon (<= 0.12.0+repack-2)
Added tag(s) pending.
--
974595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974595
Debian Bug Tracking System
Contact ow...@bugs
Processing control commands:
> reassign -1 node-snapdragon
Bug #974595 [node-snapdragon-util] node-snapdragon-util: missing
Breaks+Replaces: node-snapdragon (<= 0.12.0+repack-2)
Bug reassigned from package 'node-snapdragon-util' to 'node-snapdragon'.
No longer marked as found in versions node-sna
Control: reassign -1 node-snapdragon
Control: affects -1 node-snapdragon
Le 12/11/2020 à 20:49, Andreas Beckmann a écrit :
> Package: node-snapdragon-util
> Version: 5.0.1-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noti
Processing control commands:
> reassign -1 node-snapdragon
Bug #974594 [node-snapdragon-node] node-snapdragon-node: missing
Breaks+Replaces: node-snapdragon (<= 0.12.0+repack-2)
Bug reassigned from package 'node-snapdragon-node' to 'node-snapdragon'.
No longer marked as found in versions node-sna
control: reassign -1 node-snapdragon
control: affects -1 node-snapdragon-node
Le 12/11/2020 à 20:47, Andreas Beckmann a écrit :
> Package: node-snapdragon-node
> Version: 3.0.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I
Control: tag -1 pending
Hello,
Bug #974594 in node-snapdragon 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:
https://salsa.debian.org/js-team/node-snapdragon/-/commit/6c42261e8dbab45ba
Processing control commands:
> tag -1 pending
Bug #974594 [node-snapdragon-node] node-snapdragon-node: missing
Breaks+Replaces: node-snapdragon (<= 0.12.0+repack-2)
Added tag(s) pending.
--
974594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974594
Debian Bug Tracking System
Contact ow...
Source: rust-tokio-process
Version: 0.2.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Hi,
rust-tokio-process build-depends on librust-crossbeam-queue-0.1+default-dev.
This package does not exist in sid or in the NEW queue.
-Ralf.
Source: rust-sloppy-rfc4880
Version: 0.1.5-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Hi,
rust-sloppy-rfc4880 build-depends on
librust-base64-0.11+default-dev | librust-base64-0.10+default-dev.
However none of these exists in sid.
-Ralf.
[Gunnar Hjalmarsson]
> Additional observations:
>
> * The testing failure in Ubuntu started around October 31.
>
> * The test-command-line script fails on amd64 and i386 but succeeds on
>other architectures.
Is it possible to 'diff' the logs from a successful and a failing test,
to see what ch
Control: tag -1 pending
Hello,
Bug #973636 in golang-github-nicksnyder-go-i18n.v2 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:
https://salsa.debian.org/go-team/packages/golang-githu
Processing control commands:
> tag -1 pending
Bug #973636
[golang-github-nicksnyder-go-i18n.v2-dev,golang-github-nicksnyder-go-i18n-dev]
golang-github-nicksnyder-go-i18n.v2-dev,golang-github-nicksnyder-go-i18n-dev:
duplicate packages?
Added tag(s) pending.
--
973636: https://bugs.debian.org/c
Package: node-snapdragon
Version: 0.12.0+repack-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package has file conflicts
with some newly introduced packages in sid, which seem to package
some components currently in node-sna
Package: node-snapdragon-node
Version: 3.0.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 overwrit
Package: node-snapdragon-util
Version: 5.0.1-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 overwrit
Package: libavif8-gdk-pixbuf
Version: 0.8.3-1
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
Processing commands for cont...@bugs.debian.org:
> forwarded 974580 https://github.com/rerrahkr/BambooTracker/issues/263
Bug #974580 [src:bambootracker] bambootracker FTBFS on 32bit
Set Bug forwarded-to-address to
'https://github.com/rerrahkr/BambooTracker/issues/263'.
> thanks
Stopping processin
$ which kwin
/usr/bin/kwin
$ dpkg -S usr/bin/kwin
kwin-x11: /usr/bin/kwin
kwin-x11: /usr/bin/kwin_x11
$ ls -l /usr/bin/kwin
/usr/bin/kwin -> kwin_x11
$ dpkg --list kwin-x11
ii kwin-11 4:5.17.5-4 amd64 KDE window manager, X11 version
$ kwin --version
kwin: symbol lookup error: /lib/x86_64-linux-
Hi !
Just tested v1.1 and the issue persists. The problem is quiet local connection
when using with corosync
Thanks,
Alejandro
> On 12 Nov 2020, at 14:21, Pallai Roland wrote:
>
> Hi Markus,
>
> The problem is still the same here:
> Nov 12 18:14:46 srv1 lrmd[990]: warning: Rejecting IPC req
Hi,
On Thu, Nov 12, 2020 at 07:08:26PM +0100, wf...@niif.hu wrote:
> Moritz Mühlenhoff writes:
>
> > On Sat, Nov 07, 2020 at 08:56:38PM +0100, wf...@niif.hu wrote:
> >
> >> I propose a security upload with the debdiff below. The patch series
> >> posted by upstream against 2.0.3 applies cleanl
Moritz Mühlenhoff writes:
> On Sat, Nov 07, 2020 at 08:56:38PM +0100, wf...@niif.hu wrote:
>
>> I propose a security upload with the debdiff below. The patch series
>> posted by upstream against 2.0.3 applies cleanly to the buster source,
>> and is hereby included. I'll try to do some testing
Hi Markus,
The problem is still the same here:
Nov 12 18:14:46 srv1 lrmd[990]: warning: Rejecting IPC request
'lrmd_rsc_info' from unprivileged client crmd
Nov 12 18:14:46 srv1 lrmd[990]: warning: Rejecting IPC request
'lrmd_rsc_register' from unprivileged client crmd
Nov 12 18:14:46 srv1 crm
Your message dated Thu, 12 Nov 2020 17:18:47 +
with message-id
and subject line Bug#974162: fixed in plast 2.3.2+dfsg-3
has caused the Debian Bug report #974162,
regarding plast: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:libproxy
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Se
Thanks for reporting. This is a permission problem. I assume your clients are
local and not remote and you don't use the tls_backend. I have prepared another
update that should grant the local hacluser clients the necessary privileges.
You can download the source and binary files from
https://peop
Source: pam-python
Version: 1.0.8-1
Severity: serious
The autopkgtest for pam-python is broken, it tries to install a binary package
that does not exist.
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU mK Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on python-pam:amd64 < none @un H >
Re
Control: found -1 2021~beta2-1
On 11/12/20 3:42 AM, Debian Bug Tracking System wrote:
> gromacs (2021~beta2-1) experimental; urgency=medium
> .
>* New upstream beta release.
> - Remove versioning-for-nblib.patch, incorporated in this release.
> - libnblib SONAME corrected to 0.2.0.
Processing control commands:
> found -1 2021~beta2-1
Bug #973639 {Done: Nicholas Breen } [libgromacs6]
libgromacs6: missing Breaks+Replaces: libgromacs5
Marked as found in versions gromacs/2021~beta2-1; no longer marked as fixed in
versions gromacs/2021~beta2-1 and reopened.
--
973639: https:/
Your message dated Thu, 12 Nov 2020 18:24:28 +0200
with message-id
and subject line insighttoolkit4 ftbfs with python3.9
has caused the Debian Bug report #972909,
regarding insighttoolkit4 ftbfs with python3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 12 Nov 2020 16:59:26 +0100
with message-id <20201112155926.GD587120@pisa>
and subject line msxpertsuite: FTBFS: MassSpectrum.cpp:50:10: fatal error:
pwiz/data/msdata/MSDataFile.hpp: No such file or directory
has caused the Debian Bug report #924843,
regarding msxpertsuite:
On Thu, 12 Nov 2020 12:00:16 -0300 Alejandro Taboada
wrote:
> Here we have the same error after a security update.
> We tried to configure different user/role without success.
>
>
>
>
> On Thu, 12 Nov 2020 14:57:45 +0100 Emmanuel Lacour
> wrote:
> > I can confirm that we had the same problem he
Here we have the same error after a security update.
We tried to configure different user/role without success.
On Thu, 12 Nov 2020 14:57:45 +0100 Emmanuel Lacour wrote:
> I can confirm that we had the same problem here. I downgraded everything
> until fixed:
>
>
>
> apt install libcib4=1.
Your message dated Thu, 12 Nov 2020 15:04:06 +
with message-id
and subject line Bug#971966: fixed in boinc 7.16.15+dfsg.is.7.16.11+dfsg-2
has caused the Debian Bug report #971966,
regarding boinc-manager: Mismatch between the program and library build
versions (C++ ABI 1014 vs. 1013)
to be ma
Package: courier-mta
Version: 1.0.6-1
Severity: critical
Justification: hide real errors
as of 0015-Disable-imapscanfail-maildirwatch-error-reporting.patch
only hide the error message and seems real solution are by install FAM
please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578937#
Source: inspectrum
Version: 0.2.2-1
Severity: serious
Tags: ftbfs
inspectrum fails to build from source in unstable on amd64:
| [ 84%] Building CXX object CMakeFiles/inspectrum.dir/traceplot.cpp.o
| /usr/bin/c++ -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -I/<>/
Source: jerry
Version: 3.2.0-1
Severity: serious
Tags: ftbfs
jerry fails to build from source in unstable on amd64:
| g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++1y -Wall -Wextra -D_REENTRANT -f
I can confirm that we had the same problem here. I downgraded everything until
fixed:
apt install libcib4=1.1.16-1 libcrmcluster4=1.1.16-1 libcrmcommon3=1.1.16-1
libcrmservice3=1.1.16-1 liblrmd1=1.1.16-1 libpe-rules2=1.1.16-1
libpe-status10=1.1.16-1 libpengine10=1.1.16-1 libstonithd2=1.1.16-1
Source: bambootracker
Version: 0.4.5-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=bambootracker&suite=sid
...
midi/RtMidi/RtMidi.cpp: In function ‘void* alsaMidiHandler(void*)’:
midi/RtMidi/RtMidi.cpp:1664:26: error: comparison of integer expressions of
differen
Source: mailsync
Version: 5.2.7-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=mailsync&suite=sid
...
debian/rules build
dh_testdir
automake -a
configure.ac:2: error: version mismatch. This is Automake 1.16.2,
configure.ac:2: but the definition used by this AM_IN
Seems this issue is solved with the patch
0012-Define-and-use-PEMFILE-in-mkesmtpdcert.patch
please confirm and close
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Hello, feel free to push your way to fix it!
I tested with dpkg-buildpackage -A and dpkg-buildpackage -B and it was fine,
and also was fine my Ubuntu upload
https://launchpad.net/ubuntu/+source/ismrmrd/1.4.2.1-5~build1
So, I hope everything is fine now
(my biggest concern was to avoid accident
> It's quite interesting to submit a bug report without a working window
> manager, but I think this may be related to the commit
> https://salsa.debian.org/qt-kde-team/kde/kscreenlocker/-/commit/
2320b40c8d6f3ba316c83a31bdba79dc8db6d208
> not listing the symbol
> _ZN12ScreenLocker7KSldApp30greeter
Your message dated Thu, 12 Nov 2020 13:18:24 +
with message-id
and subject line Bug#973939: fixed in ismrmrd 1.4.2.1-5
has caused the Debian Bug report #973939,
regarding ismrmrd: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 12 Nov 2020 13:18:24 +
with message-id
and subject line Bug#974570: fixed in ismrmrd 1.4.2.1-5
has caused the Debian Bug report #974570,
regarding ismrmrd: missing libpugi-dev runtime dependency
to be marked as done.
This means that you claim that the problem has been
Hi Gianfranco,
thanks a lot for the fix (I had some race condition with another
way to fix it but your's is fine as well) and specifically to also
fix #974570.
I'll upload once my local build has finished.
Kind regards
Andreas.
On Thu, Nov 12, 2020 at 01:23:51PM +0100, Gianfranco Costam
Processing commands for cont...@bugs.debian.org:
> block 968912 with 974574
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 974134 974061 972274 974063 972275 964902 974021 961208
974143 961152 974055 961157 960863 974170 974058 973010 961154 961155 968913
968912 was
Processing commands for cont...@bugs.debian.org:
> block 968912 with 973010
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 974143 961152 968913 974021 960863 972275 974063 972274
961157 974055 974061 974058 964902 974170 961208 974134 961154 961155
968912 was not bl
package: nbdkit
severity: serious
version: 1.22.3-1
Hi,
The latest version of nbdkit build-depends on libtorrent-rasterbar-dev. As
libtorrent-rasterbar is no longer in testing, this prevents migration to
testing.
Cheers,
Ivo
Hello,
I fixed and pushed on git the arch:all/arch:any builds and autopkgtests
commit d2d320434f30ecefc1ed8b88c0dc89c74b92b64d (HEAD -> master, origin/master,
origin/HEAD)
Author: Gianfranco Costamagna
Date: Thu Nov 12 13:22:27 2020 +0100
Update changelog
:100644 100644 b617ae1 824ae5c
control: reopen -1
control: notfixed -1 1.4.2.1-4
thanks
On Thu, 12 Nov 2020 09:03:47 + Debian FTP Masters
wrote:
> Source: ismrmrd
> Source-Version: 1.4.2.1-4
> Done: Andreas Tille
>
> We believe that the bug you reported is fixed in the latest version of
> ismrmrd, which is due to be ins
Processing control commands:
> tag -1 pending
Bug #974570 [src:ismrmrd] ismrmrd: missing libpugi-dev runtime dependency
Added tag(s) pending.
--
974570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #974570 in ismrmrd 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:
https://salsa.debian.org/med-team/ismrmrd/-/commit/662b5b1fdc1b1b098149fed3a227d9d5
Processing control commands:
> reopen -1
Bug #973939 {Done: Andreas Tille } [src:ismrmrd] ismrmrd:
binary-all FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed
Package: libx11-6
Version: 2:1.6.12-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: fake...@ammd.net
Dear Maintainer,
After upgrading to 2:1.6.12-1, the following warning appears when launching
rxvt-unicode:
urxvt: the locale is not supported by Xlib, continuing without
Source: ismrmrd
Version: 1.4.2.1-4
Severity: serious
tags: patch
Hello, autopkgtests fails because of:
cmake ../../ismrmrd-1.4.2.1/examples/c/
-- Could NOT find PugiXML (missing: PugiXML_DIR)
CMake Error at /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47
(find_package):
By not p
Hi Matthias,
shouldn't the severity be "important" if the FTBFS is really related to
python 3.9 until this version becomes the default python version?
AFAICS 3.8 is still the default, here [1] it is not yet listed for
bullseye, and ITK is build only against the default python version
(everythin
Processing commands for cont...@bugs.debian.org:
> retitle 974061 postgresql-12 should not be part of the next release, remove
> from testing
Bug #974061 [src:postgresql-12] postgresql-12: FTBFS: timetz test failure
Changed Bug title to 'postgresql-12 should not be part of the next release,
remo
Your message dated Thu, 12 Nov 2020 10:50:15 +
with message-id
and subject line Bug#971048: fixed in samba 2:4.13.2+dfsg-1
has caused the Debian Bug report #971048,
regarding samba: CVE-2020-1472
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Affected by this bug too! It gave us a good headache today!
https://askubuntu.com/questions/1291685/apache-file-on-mounted-folder-corrupted-file/1291690
Your message dated Thu, 12 Nov 2020 10:20:09 +
with message-id
and subject line Bug#973768: fixed in rust-num-traits 0.2.11-3
has caused the Debian Bug report #973768,
regarding rust-num-traits FTBFS: missing comma in Depends
to be marked as done.
This means that you claim that the problem ha
Your message dated Thu, 12 Nov 2020 10:20:04 +
with message-id
and subject line Bug#959549: fixed in qwertone 0.3.0-1
has caused the Debian Bug report #959549,
regarding qwertone: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
to be marked as done.
This m
Your message dated Thu, 12 Nov 2020 10:18:52 +
with message-id
and subject line Bug#972220: fixed in cgreen 1.3.0-2
has caused the Debian Bug report #972220,
regarding src:cgreen: fails to migrate to testing for too long: FTBFS on s390x
to be marked as done.
This means that you claim that the
Processing control commands:
> merge -1 974560
Bug #974564 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and
ppc64el: Segmentation fault
Bug #974560 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and
ppc64el: Segmentation fault
Merged 974560 974564
--
974560: https:/
Control: merge -1 974560
Oops, sorry for the noise.
Paul
signature.asc
Description: OpenPGP digital signature
Source: mpi4py
Version: 3.0.3-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of mpi4py started to
fail in testing when that autopkgtest is run on amd64, arm64 an
Processing commands for cont...@bugs.debian.org:
> severity 931345 serious
Bug #931345 [src:nvchecker] nvchecker: autopkgtest regression in June 2019
Severity set to 'serious' from 'important'
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> u
Package: pacemaker
Version: 1.1.16-1+deb9u1
Severity: grave
X-Debbugs-CC: a...@debian.org
Hi,
I am running corosync 2.4.2-3+deb9u1 with pacemaker and the last run of
unattended-upgrades broke the cluster (downgrading pacemaker to 1.1.16-1
fixed it immediately).
The logs contain a lot of warnings t
Source: mpi4py
Version: 3.0.3-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of mpi4py started to
fail in testing when that autopkgtest is run on amd64, arm64 an
Source: fades
Version: 9.0.1-1
Severity: serious
Justification: ftp-master autoreject ruling
Hi Iñaki,
Your package has an autopkgtest, awesome. However, I noticed that it
installs Python code using pip. Running downloaded code from internet is
not allowed in the Debian archive; see the ftp-maste
Your message dated Thu, 12 Nov 2020 09:03:20 +
with message-id
and subject line Bug#974544: fixed in charls 2.1.0+dfsg-8
has caused the Debian Bug report #974544,
regarding libcharls-dev needs Breaks: libdcmtk-dev (<< 3.6.5-1~)
to be marked as done.
This means that you claim that the problem
1 - 100 of 109 matches
Mail list logo
