On 05/23/20 13:13 PM, Adrian Bunk wrote:
> On Thu, Mar 12, 2020 at 04:36:17PM +, Ivo De Decker wrote:
>> package: src:gambc
>> version: 4.9.3-1
>> severity: serious
>> tags: ftbfs
>>
>> Hi,
>>
>> The latest upload of gambc to unstable fails on s390x:
>>
>> https://buildd.debian.org/status/pa
Processing commands for cont...@bugs.debian.org:
> severity 981403 serious
Bug #981403 [src:pylev] pylev: Another source-only upload is needed
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981403: https://bugs.debian.or
Source: cadabra2
Version: 2.3.5-2
Severity: serious
https://buildd.debian.org/status/package.php?p=cadabra2
...
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing:
/<>/debian/cadabra2/usr/share/jupyter/kernels/cadabra2/kernel.json
-- Insta
Source: poetry-core
Version: 1.0.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/p/poetry-core/9884892/log.gz
...
=== FAILURES ===
__ test_build_wheel_extended __
Your message dated Mon, 01 Feb 2021 04:48:53 +
with message-id
and subject line Bug#955772: fixed in dask.distributed 2021.01.0+ds.1-1
has caused the Debian Bug report #955772,
regarding dask.distributed: flaky autopkgtest: timeout reached in
test_robust_to_bad_sizeof_estimates
to be marked a
On Sun, Jan 31, 2021 at 11:20 PM Tino Didriksen wrote:
> I did CC Kartik in the original mail. I assume it was lost in the crowd.
> https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and
> bundled and is the only thing that wanted apertium-ukr, so after
> apertium-rus-ukr is u
Hi Helmut (2018.04.20_14:01:36_-0600)
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib/python3/dist-packages/sphinxcontrib/rubydomain.py", line 23,
> in
> from sphinx.util.compat import Directive
> ImportError: cannot import name 'Directive'
Had a look at this
Your message dated Mon, 01 Feb 2021 02:28:48 +
with message-id
and subject line Bug#980608: fixed in renderdoc 1.11+dfsg-5
has caused the Debian Bug report #980608,
regarding renderdoc: FTBFS: glslang_compile.cpp:145:1: error: cannot convert
‘’ to ‘int’ in initialization
to be marked as done.
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305
On Sun, 31 Jan 2021 at 18:53:09 -0500, Charles Malaheenee wrote:
> In journalctl there are a lot messages from systemd or dbus-daemon, like
> "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service
> 'or
Processing control commands:
> forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/glib/-/issues/2305'.
--
981420: https://bugs.debia
Your message dated Mon, 01 Feb 2021 00:18:38 +
with message-id
and subject line Bug#979058: fixed in geronimo-j2ee-connector-1.5-spec 2.0.0-2
has caused the Debian Bug report #979058,
regarding src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address
to be marked as done.
This means t
Processing commands for cont...@bugs.debian.org:
> severity 534756 grave
Bug #534756 [fusesmb] fusesmb.cache fails on 64-bit
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
534756: https://bugs.debian.org/cgi-bin/bugreport.
Hello Simon,
Thank you for the attention to this bug!
Our DE is Mate. Probably, the problem is related to the mix of components ?
Here is the output (I do not remember to have to change the permissions of
gnome-keyring-daemon):
ls -l /usr/bin/gnome-keyring-daemon
-rwxr-xr-x 1 root root 1143712
Processing control commands:
> tag -1 pending
Bug #979058 [src:geronimo-j2ee-connector-1.5-spec]
src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address
Added tag(s) pending.
--
979058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979058
Debian Bug Tracking System
Contact ow...@bu
Control: tag -1 pending
Hello,
Bug #979058 in geronimo-j2ee-connector-1.5-spec 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/java-team/geronimo-j2ee-connecto
Package: minigalaxy
Version: 1.0.1-1
Severity: grave
Tags: security
Justification: introduces a security hole allowing access to the accounts of
users who use the package
Hi,
thanks for packaging minigalaxy. Unfortunately it's unusable as you
can't conscientiously login to GOG:
On startup it sh
> Re: Lucas Nussbaum
> > > 14/14 Test #1: code-style ...***Failed 61.38 sec
> > > cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module
> > > 'PyQt5.QtCore' has no attribute 'pyqtProperty'
>
> Fwiw cura still works fine here, so I'd claim this is a test-only
> p
* Helmut Grohne :
> On Fri, Aug 07, 2020 at 12:28:17PM +0200, Stefan Bühler wrote:
> > I think fixing libgamin0.shlibs and dropping fam from the archives is
> > the smoothest path to fixing this mess.
>
> Well, yeah. Removing fam removes the whole mess of compatibility.
#966273 has become RM: fa
Your message dated Sun, 31 Jan 2021 23:06:12 +
with message-id
and subject line Bug#979056: fixed in geronimo-jms-1.1-spec 1.1.1-1
has caused the Debian Bug report #979056,
regarding src:geronimo-jms-1.1-spec: invalid maintainer address
to be marked as done.
This means that you claim that the
On Sun, 2021-01-31 at 18:49 +0100, Andrea Bolognani wrote:
> I've added a few extra Depends to make sure everything is really
> updated in lockstep and tested with unattended-upgrades: the result
> was much better this time!
...
> I believe we can merge the MR and consider the issue resolved.
Loo
Processing commands for cont...@bugs.debian.org:
> forwarded 980603 https://github.com/Ultimaker/Cura/issues/9216
Bug #980603 [src:cura] cura: FTBFS:
cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module
'PyQt5.QtCore' has no attribute 'pyqtProperty'
Set Bug forwarded-to-address to '
Processing control commands:
> tag -1 pending
Bug #979056 [src:geronimo-jms-1.1-spec] src:geronimo-jms-1.1-spec: invalid
maintainer address
Added tag(s) pending.
--
979056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Control: tag -1 pending
Hello,
Bug #979056 in geronimo-jms-1.1-spec 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/java-team/geronimo-jms-1.1-spec/-/commit/65f
* Guido Günther [2021-01-31 13:19]:
Awesome. I had fixed the rpm parts here already
https://github.com/agx/git-buildpackage/tree/rpm but went for your
patches so your work is not lost. The reason i wrote 'tip of the
iceberg' is that the component tests need fixing as well - that's the bit
still
Processing control commands:
> severity 980923 serious
Bug #980923 [apt-cacher-ng] acngtools eats all the CPU and doesn’t finish daily
cron with merged pdiffs
Severity set to 'serious' from 'important'
--
980923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980923
Debian Bug Tracking Syste
Your message dated Sun, 31 Jan 2021 22:00:18 +
with message-id
and subject line Bug#966967: fixed in libunity 7.1.4+19.04.20190319-3
has caused the Debian Bug report #966967,
regarding libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1
returned exit code 2
to be marked as done.
T
package: mercurial
version: 5.6.1-1
severity: serious
Hi,
The mercurial autopkgtest fails with the latest git:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/10134722/log.gz
It seems the output of git changed in a way that the test didn't expect.
I suspect this will be fixed
Your message dated Sun, 31 Jan 2021 22:43:00 +0100
with message-id <20210131214259.ga25...@debian.org>
and subject line Re: git: FTBFS: test failed
has caused the Debian Bug report #975173,
regarding git: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been
Source: screenkey
Version: 1:1.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
| I: pybuild base:232: python3.9 setup.py clean
| WARNING: The pip package is not available, falling back to EasyInstall for
handling setup_requires/test_
Source: pyfai
Version: 0.20.0+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
| ==
| ERROR: setUpClass (pyFAI.test.test_histog
Processing control commands:
> tag -1 pending
Bug #954303 [src:tika] tika: CVE-2020-1950
Added tag(s) pending.
--
954303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #954303 in tika 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/java-team/tika/-/commit/1a8d36ebff54d00c2dda5d27671305ba16680
Control: tag -1 pending
Hello,
Bug #954302 in tika 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/java-team/tika/-/commit/1a8d36ebff54d00c2dda5d27671305ba16680
Processing control commands:
> tag -1 pending
Bug #954302 [src:tika] tika: CVE-2020-1951
Added tag(s) pending.
--
954302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 -pending
Bug #948739 [gparted] gparted should not mask .mount units
Removed tag(s) pending.
--
948739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 -pending
Hi,
On Fri, Jan 29, 2021 at 08:56:01AM -0500, Phillip Susi wrote:
> John Paul Adrian Glaubitz writes:
>
> > Hello!
> >
> > It looks like this particular issue has been fixed in gparted 1.2.0 which
> > was just released a few days ago [1]:
> >
> >> - Don't try to mask no
Processing commands for cont...@bugs.debian.org:
> severity 980338 serious
Bug #980338 [src:hotswap] hotswap: should ship with bullseye?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980338: https://bugs.debian.org/cgi-
Processing commands for cont...@bugs.debian.org:
> severity 980348 serious
Bug #980348 [src:ruby-wirble] ruby-wirble: ship with bullseye?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980348: https://bugs.debian.org/cgi
Your message dated Sun, 31 Jan 2021 21:09:39 +
with message-id
and subject line Bug#936880: fixed in libiptcdata 1.0.5-2.3
has caused the Debian Bug report #936880,
regarding libiptcdata: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> block 978710 with 976735
Bug #978710 [ftp.debian.org] RM: python3.8 -- ROM; superseded by python3.9
978710 was not blocked by any bugs.
978710 was not blocking any bugs.
Added blocking bug(s) of 978710: 976735 and 978648
> thanks
Stopping processi
Processing control commands:
> severity -1 important
Bug #980903 [debhelper] debhelper: doc-base doc-id deduplication does not work
as documented with multiple "dh_installdocs -p" calls; causes
/usr/share/doc-base/ to be installed multiple times
Severity set to 'important' from 'serious'
--
98
Control: severity -1 important
Hi Niels,
I've now added one paragraph to the POD of dh_installdocs:
Please be aware that this deduplication currently only works if
B is called only once during the package build as
deduplication is done in memory only. Especially calling
BI in combination
Dear maintainer,
I've prepared an NMU for libiptcdata (versioned as 1.0.5-2.3). The diff
is attached to this message.
Regards.
--
Sebastian Ramacher
diff -Nru libiptcdata-1.0.5/debian/bin/pydoc libiptcdata-1.0.5/debian/bin/pydoc
--- libiptcdata-1.0.5/debian/bin/pydoc 2020-08-08 22:18:23.
Your message dated Sun, 31 Jan 2021 21:18:44 +0100
with message-id
and subject line Re: Bug#978360: python-whoosh: FTBFS: AttributeError:
'NullMatcherClass' object has no attribute '__name__'
has caused the Debian Bug report #978360,
regarding python-whoosh: FTBFS: AttributeError: 'NullMatcherCla
Processing control commands:
> forwarded -1
> https://bitbucket.org/wooster/biplist/issues/12/python-39-compatibility
Bug #973082 [src:python-biplist] python-biplist: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13
Set Bug forwarded-to
Control: forwarded -1
https://bitbucket.org/wooster/biplist/issues/12/python-39-compatibility
Control: tag -1 + patch
Hi Hans-Christoph (2021.01.03_13:54:51_-0700)
> In Python 3.9, the plistlib was changed to no longer have the internal data
> structure plistlib.Data, which biplist relied on.
Fr
package: webext-exteditor
version: 2.0.4-1
severity: serious
Hi,
Thunderbird 1:78.7.0-1 has 'Breaks: webext-exteditor (<= 2.0.4-1)', which
means webext-exteditor doesn't work with it.
Cheers,
Ivo
package: python3-extractor
version: 1:0.6-8
severity: serious
Hi,
Piuparts detected an installation error in python3-extractor:
Setting up python3.9 (3.9.1-3) ...
Setting up python3 (3.9.1-1) ...
Setting up python3-extractor (1:0.6-8) ...
Sorry: TabError: inconsistent use of tabs and spa
Processing control commands:
> close -1 0~20200923.2-2
Bug #981482 [src:abseil] src:abseil: fails to migrate to testing for too long:
FTBFS everywhere
Marked as fixed in versions abseil/0~20200923.2-2.
Bug #981482 [src:abseil] src:abseil: fails to migrate to testing for too long:
FTBFS everywher
Source: abseil
Version: 0~20200923.2-1
Severity: serious
Control: close -1 0~20200923.2-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 976575
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
a
On 31 January 2021 at 20:09, Graham Inggs wrote:
| Hi Dirk
|
| On Sun, 31 Jan 2021 at 16:13, Dirk Eddelbuettel wrote:
| > This is a bug in glmmTMB.
|
| I don't see how you can be so sure.
Experience around R. glmmTMB is a huge package with many dependencies, there
will be a stale one in the p
Processing commands for cont...@bugs.debian.org:
> retitle 941714 bst-external: file conflict: installs .coverage file
Bug #941714 [src:bst-external] bst-external: please make the build reproducible
Changed Bug title to 'bst-external: file conflict: installs .coverage file'
from 'bst-external: pl
Your message dated Sun, 31 Jan 2021 19:06:49 +
with message-id
and subject line Bug#981474: fixed in node-rollup-plugin-terser 7.0.2-5
has caused the Debian Bug report #981474,
regarding node-rollup-plugin-terser: test randomly fails due to timeout problems
to be marked as done.
This means th
Your message dated Sun, 31 Jan 2021 18:54:45 +
with message-id
and subject line Bug#979012: fixed in minetest 5.3.0+repack-2
has caused the Debian Bug report #979012,
regarding minetest-data: debian/copyright needs updating
to be marked as done.
This means that you claim that the problem has
Package: ser2net
Version: 4.3.2-1
Severity: grave
When attempting to start ser2net I get the message:
/usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined
symbol: gensio_alloc_mdns
This happens when I start it in any way, such as just invoking the
executable with no parameters,
Processing control commands:
> tag -1 pending
Bug #981474 [node-rollup-plugin-terser] node-rollup-plugin-terser: test
randomly fails due to timeout problems
Added tag(s) pending.
--
981474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981474
Debian Bug Tracking System
Contact ow...@bugs.de
Control: tag -1 pending
Hello,
Bug #981474 in node-rollup-plugin-terser 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-rollup-plugin-terser/-/comm
Package: node-rollup-plugin-terser
Version: 7.0.2-4
Severity: serious
Tags: ftbfs
Justification: Policy 2.1
https://ci.debian.net/packages/n/node-rollup-plugin-terser/testing/amd64/
shows that node-rollup-plugin-terser test randomly fails
Hi Dirk
On Sun, 31 Jan 2021 at 16:13, Dirk Eddelbuettel wrote:
> This is a bug in glmmTMB.
I don't see how you can be so sure.
> All the 'gradient function must ...' errors are from its tests and
> points to me to a recent change in R (where boolean comparisons can now check
> if the compared v
I did CC Kartik in the original mail. I assume it was lost in the crowd.
https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and
bundled and is the only thing that wanted apertium-ukr, so after
apertium-rus-ukr is uploaded, apertium-ukr will be superfluous and should
be removed.
-
On Sun, Jan 31, 2021 at 04:36:21PM +0100, Andrea Bolognani wrote:
> I've opened
>
> https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/98
>
> with the proposed patch, and I'm going to use the information you
> provided above to give it some testing now.
I've added a few extra Depen
Processing commands for cont...@bugs.debian.org:
> severity #981461 important
Bug #981461 [ser2net] ser2net: unable to start, undefined symbol:
gensio_alloc_mdns
Severity set to 'important' from 'grave'
> # works for me
> tags 981461 unreproducible moreinfo
Bug #981461 [ser2net] ser2net: unable t
severity #981461 important
# works for me
tags 981461 unreproducible moreinfo
thanks
Hi,
On Sun, Jan 31, 2021 at 10:46:35PM +0800, Gedalya wrote:
> When attempting to start ser2net I get the message:
> /usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined symbol:
> gensio_alloc_mdn
Your message dated Sun, 31 Jan 2021 17:35:16 +
with message-id
and subject line Bug#975963: fixed in bmake 20200710-6
has caused the Debian Bug report #975963,
regarding bmake: /usr/share/mk is now a symlink, upgrades from non-symlinks are
broken
to be marked as done.
This means that you cla
Hi Tino,
On Tue, 5 Jan 2021 01:13:56 +0100 Tino Didriksen wrote:
> apertium-ukr should be removed from Debian. The pair that needed it has
> been upgraded to bundle the required version instead:
If you agree, can I retitle and reassign to file in a removal bug for
apertium-ukr, then?
Also, I do
Your message dated Sun, 31 Jan 2021 17:04:29 +
with message-id
and subject line Bug#979640: fixed in adv-17v35x 5.0.6.0-1
has caused the Debian Bug report #979640,
regarding src:adv-17v35x: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been de
Dear Maintainer,
after recent upload of rdflib/5.0.0-1, tests fail with
this message:
(Reading database ... 18244 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [12:41:57]: test python3: [---
/tmp/autopkgtest.vpiWsK/build.W6L/src/de
Processing commands for cont...@bugs.debian.org:
> tags 936593 - wontfix
Bug #936593 [src:geda-gaf] geda-gaf: Python2 removal in sid/bullseye
Bug #966736 [src:geda-gaf] geda-gaf: Unversioned Python removal in sid/bullseye
Removed tag(s) wontfix.
Removed tag(s) wontfix.
> user debian-pyt...@lists.d
On Thu, 14 Jan 2021 at 20:03:37 +, A Ozbay wrote:
> I looked through journalctl output and saw this which looked out of ordinary:
> Jan 13 22:59:29 snorlax gnome-shell[2475]: JS ERROR: Error getting systemd
> inhibitor: Gio.IOErrorEnum:
> GDBus.Error:org.freedesktop.login1.OperationInProgress
Control: tags -1 - wontfix
Control: user debian-pyt...@lists.debian.org , usertags -1 + py2keep
Hi,
since migrating gEDA/gaf to Python 3 is a non-trivial effort and the
package has many users (popcon > 1000), I'm adding the "py2keep" user tag
as requested.
I fixed the use of unversioned pyth
On Sun, Jan 31, 2021 at 11:04:13PM +0800, Paul Wise wrote:
> On Sun, 2021-01-31 at 15:34 +0100, Andrea Bolognani wrote:
> > As I've never used unattended-upgrades myself, I'm not familiar with
> > it. Is there any chance you could provide some quick tips on how to
> > set up a reproducer environmen
On Sun, 31 Jan 2021 at 11:45:08 +, Simon McVittie wrote:
> I suspect I know what change triggered this: it'll be the security hardening
> imported from the upstream glib-2-66 branch in 2.66.4-2. However, I couldn't
> reproduce this failure to unlock in a test VM.
I've prepared several sets of
Processing control commands:
> retitle -1 geda-gaf: please upload latest version which uses guile-2.2
Bug #885195 [src:geda-gaf] geda-gaf: please migrate to guile-2.2
Changed Bug title to 'geda-gaf: please upload latest version which uses
guile-2.2' from 'geda-gaf: please migrate to guile-2.2'.
>
Control: retitle -1 geda-gaf: please upload latest version which uses guile-2.2
Control: fixed -1 geda-gaf/1:1.10.2-0.1
Hi,
gEDA/gaf has migrated to Guile 2.2 in version 1.10.2. Since Bdale isn't
interested in packaging gEDA/gaf any more and Kai-Martin is currently
unavailable, I stepped in a
On Sun, 2021-01-31 at 15:34 +0100, Andrea Bolognani wrote:
> As I've never used unattended-upgrades myself, I'm not familiar with
> it. Is there any chance you could provide some quick tips on how to
> set up a reproducer environment? Specifically how to set up the same
> upgrade strategy you're u
Processing commands for cont...@bugs.debian.org:
> affects 981428 yubikey-manager
Bug #981428 [python3-fido2] python3-fido2: Version 0.9 breaks yubikey-manager
Added indication that 981428 affects yubikey-manager
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981
On Sun, Jan 31, 2021 at 05:43:43PM +0800, Paul Wise wrote:
> Source: libvirt
> Version: 7.0.0-1
> Severity: serious
>
> There is some sort of missing dependency that means that the daemon is
> stopped during certain kinds of upgrades. I use unattended-upgrades in
> the minimal-steps mode rather th
On 31 January 2021 at 09:20, Graham Inggs wrote:
| Control: reopen -1
|
| Hi Dirk
|
| Paul's test results showed that the run-unit-test autopkgtest still
| fails with the same errors (
| Error: gradient function must return a numeric vector of length...) as
| in my original report.
|
|
| The "
Your message dated Sun, 31 Jan 2021 13:18:50 +
with message-id
and subject line Bug#980609: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980609,
regarding gcc-10 in testing is broken, cannot build linux kernel
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding nheko: FTBFS: internal compiler error
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 31 Jan 2021 13:18:50 +
with message-id
and subject line Bug#980609: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980609,
regarding missing i386-cpuinfo.h
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
to be marked as done.
Th
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding nheko: FTBFS: internal compiler error
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
to be m
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
to be m
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
to be marked as done.
Th
Processing commands for cont...@bugs.debian.org:
> found 981439 2020.01.19-1
Bug #981439 [src:liblivemedia] liblivemedia: includes non-free code from RFC
3550
Marked as found in versions liblivemedia/2020.01.19-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
9
Processing control commands:
> severity -1 serious
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring
Severity set to 'serious' from 'important'
--
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.d
Your message dated Sun, 31 Jan 2021 12:49:28 +
with message-id
and subject line Bug#980630: fixed in libvigraimpex 1.11.1+dfsg-8
has caused the Debian Bug report #980630,
regarding libvigraimpex: FTBFS: UnicodeDecodeError: 'utf-8' codec can't decode
byte 0xb3 in position 138922: invalid start
Your message dated Sun, 31 Jan 2021 12:50:03 +
with message-id
and subject line Bug#980580: fixed in ruby-ruby2ruby 2.4.4-1
has caused the Debian Bug report #980580,
regarding ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError:
unknown arg type nil
to be marked as done.
This m
Dear Maintainer,
After applying this patch [1], I was able to
build your package in a sid chroot environment.
Kind Regards
[1] https://github.com/behave/behave/commit/66fcad
Processing commands for cont...@bugs.debian.org:
> found 914314 git-buildpackage/0.9.20
Bug #914314 [git-buildpackage] git-buildpackage: import-orig --uscan passes
--symlink unconditionally
Marked as found in versions git-buildpackage/0.9.20.
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> found 914314 git-buildpackage/0.9.14
Bug #914314 [git-buildpackage] git-buildpackage: import-orig --uscan passes
--symlink unconditionally
Marked as found in versions git-buildpackage/0.9.14.
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> tag 980256 pending
Bug #980256 [src:git-buildpackage] git-buildpackage: autopkgtest armhf
regression: /usr/bin/python: not found
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980256: https
Hi,
On Sat, Jan 30, 2021 at 09:13:07PM +0100, Jochen Sprickerhof wrote:
> Control: tags -1 + patch
>
> Hi Guido,
>
> * Guido Günther [2021-01-27 12:08]:
> > Hi,
> > On Wed, Jan 20, 2021 at 09:37:56PM +0100, Lucas Nussbaum wrote:
> > > Source: git-buildpackage
> > > Version: 0.9.21
> > > Severity
tag 980256 pending
thanks
Date: Sat Jan 30 20:38:05 2021 +0100
Author: Jochen Sprickerhof
Commit ID: 5949fbc41d0008efb1f06c42e227bdbcceb7e0ff
Commit URL:
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=5949fbc41d0008efb1f06c42e227bdbcceb7e0ff
Patch URL:
https://git.sigxcpu.org/cgit/
My two cents: if `dseupd_` gives random output for the same input then it is
most likely a bug in ARPACK, although it would be good to have an isolated test
case that does not involve igraph. @jgmbenoit have you managed to produce such
a test case, or do you need a hand with creating one? If you
package: src:trapperkeeper-scheduler-clojure
version: 1.1.3-3
severity: serious
tags: ftbfs
Hi,
The latest upload of trapperkeeper-scheduler-clojure to unstable fails on all:
https://buildd.debian.org/status/package.php?p=trapperkeeper-scheduler-clojure
Cheers,
Ivo
Processing control commands:
> forwarded 980602 https://gitlab.freedesktop.org/xorg/lib/libxcb/-/issues/49
Bug #980602 [src:libxcb] libxcb: FTBFS: ../../tests/check_public.c:40:24:
error: too many arguments for format [-Werror=format-extra-args]
Set Bug forwarded-to-address to
'https://gitlab.fr
Control: forwarded 980602
https://gitlab.freedesktop.org/xorg/lib/libxcb/-/issues/49
Control: tags 980602 + patch
Control: tags 980602 + pending
Dear maintainer,
I've prepared an NMU for libxcb (versioned as 1.14-2.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay
1 - 100 of 107 matches
Mail list logo
