On 20/02/2022 10.21, Sascha Steinbiss wrote:
Currently thrust and cub are out of sync. I got somewhat distracted ...
OK, got it. Just wanted to find out if there's anything I can do from
the relion packaging side. Will take a break from working on this then
until this is sorted out.
thrust a
Your message dated Thu, 10 Mar 2022 07:04:13 +
with message-id
and subject line Bug#993451: fixed in osslsigncode 2.3.0-1
has caused the Debian Bug report #993451,
regarding osslsigncode: timestamp-based tests fail on amd64 (sometimes)
to be marked as done.
This means that you claim that the
Your message dated Thu, 10 Mar 2022 07:04:13 +
with message-id
and subject line Bug#993452: fixed in osslsigncode 2.3.0-1
has caused the Debian Bug report #993452,
regarding osslsigncode: MSI tests fail on big-endian architectures
to be marked as done.
This means that you claim that the probl
Hi,
I forwarded the bug to
upstream: https://github.com/agronholm/anyio/issues/417
Here is the commit upstream would like feedback about:
https://github.com/agronholm/anyio/commit/184744ca291d426dd278f697c3637623eb9de0ed
Can you check?
Thanks!
J.Puydt
Source: nim
Version: 1.6.4-1
Severity: serious
Tags: experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy
Hi Federico,
The nim source package currently has a hard-coded build-dependency (and
runtime dependency) on libssl1.1. Attempting to switch to libssl3 results
in an
Processing control commands:
> tags -1 patch
Bug #1003904 [lsp-plugins] lsp-plugins 1.1.31-1 FTBFS on armhf
Added tag(s) patch.
--
1003904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: lsp-plugins
Version: 1.1.31-1
Followup-For: Bug #1003904
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Hi there,
Attached is a patch that we have applied in Ubuntu to fix this build
failure. It's not suitable as-is for application
Your message dated Wed, 09 Mar 2022 22:03:54 +
with message-id
and subject line Bug#1006733: fixed in php-nesbot-carbon 2.55.2-2
has caused the Debian Bug report #1006733,
regarding phpunit breaks php-nesbot-carbon autopkgtest: rounding differences
to be marked as done.
This means that you cl
Your message dated Wed, 09 Mar 2022 21:06:17 +
with message-id
and subject line Bug#1004035: fixed in rumur 2022.03.05-1
has caused the Debian Bug report #1004035,
regarding rumur FTBFS on 32bit: Bad system call
to be marked as done.
This means that you claim that the problem has been dealt w
Processing commands for cont...@bugs.debian.org:
> tags 1006733 + pending
Bug #1006733 [php-nesbot-carbon] phpunit breaks php-nesbot-carbon autopkgtest:
rounding differences
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006733: https://bu
Source: ruby-em-http-request
Version: 1.1.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression timesout
Dear maintainer(s),
Your package has an autopkgtest, great. However, recently it started
failing in testing (looking at the date, probably when ruby-defaults
migrated)
Source: ruby-clockwork
Version: 2.0.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of ruby-defaults. I noticed
that the test regularly
Source: rails
Version: 2:6.0.3.5+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on amd64 and
armhf because it was showing up as a regression for the upload of
ruby-defaults. I noticed that
Your message dated Wed, 09 Mar 2022 11:30:54 -0800
with message-id <3728c09aa2dae39f8c2bc9d915c85401e7f3979d.ca...@ghic.org>
and subject line sphinx-remove-toctrees - source-only upload required.
has caused the Debian Bug report #1006535,
regarding sphinx-remove-toctrees - source-only upload requir
Control: block -1 by 1005377
The new upstream version of r-cran-emayili needs r-cran-jinjar
which is waiting in new queue.
Kind regards
Andreas.
--
http://fam-tille.de
Processing control commands:
> block -1 by 1005377
Bug #1006380 [src:r-cran-tidyr, src:r-cran-emayili] r-cran-tidyr breaks
r-cran-emayili autopkgtest: Input must be a vector, not a object.
1006380 was not blocked by any bugs.
1006380 was not blocking any bugs.
Added blocking bug(s) of 1006380: 1
Hi,
* Santiago Garcia Mantinan [Mon Sep 06, 2021 at 11:04:58AM +0200]:
> I'm CCing Josué because this seems to be more on ifupdown's side than on
> bridge-utils.
[...]
> I know we are having quite some trouble with the random bridge mac address,
> but this doesn't seem to be one of those cases.
Processing commands for cont...@bugs.debian.org:
> severity 998516 important
Bug #998516 [bridge-utils] bridge-utils: Kernel assigns same MAC-address to the
bridge on 2 similar network devices
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> tags 998516 + moreinfo
Bug #998516 [bridge-utils] bridge-utils: Kernel assigns same MAC-address to the
bridge on 2 similar network devices
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
99
Hi,
* Alf [Thu Nov 04, 2021 at 08:24:35PM +0100]:
> Having 2 tiny servers (APU2.C4 and APU.2D4) in my local net each having
> 3 ethernet interfaces assigned to a bridge "br0" (configured in
> /etc/network/interfaces).
> Upgrading from Bustser to Bullseye worked fine for the first box, the bridge
Hi Mike,
Le 09/03/2022 13:41, Michał Trojnara a écrit :
Didn't you notice that these tests are *not* part of the osslsigncode
release tarball? Just because some random code can be found is in the
same GitHub repository doesn't meany it's suitable for production use.
Apologies, I did not noti
Your message dated Wed, 09 Mar 2022 13:06:12 +
with message-id
and subject line Bug#1005867: fixed in node-sanitize-html 2.7.0+~2.6.2-1
has caused the Debian Bug report #1005867,
regarding node-sanitize-html: Broken by node-htmlparser2 >=7
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #1005867 in node-sanitize-html 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-sanitize-html/-/commit/52a4e6233e
Hi Stephen,
Didn't you notice that these tests are *not* part of the osslsigncode
release tarball? Just because some random code can be found is in the
same GitHub repository doesn't meany it's suitable for production use.
There is a very good reason why "make check" doesn't work in
osslsigncode
Processing control commands:
> tag -1 pending
Bug #1005867 [node-sanitize-html] node-sanitize-html: Broken by
node-htmlparser2 >=7
Added tag(s) pending.
--
1005867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> block 1003037 with -1
Bug #1003037 [src:astra-toolbox] astra-toolbox: FTBFS: error: parameter packs
not expanded with '...'
1003037 was not blocked by any bugs.
1003037 was not blocking any bugs.
Added blocking bug(s) of 1003037: 1006962
--
1003037: https://bugs.d
Package: nvidia-cuda-toolkit
Version: 11.4.3-2
Severity: serious
Control: block 1003037 with -1
nvcc fails to compile bits/std_function.h from g++ 11.2:
$ echo '#include ' | nvcc -ccbin g++-11 -x cu -c -
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not
expanded with ‘.
Your message dated Wed, 09 Mar 2022 12:19:35 +
with message-id
and subject line Bug#1006465: fixed in python-dbusmock 0.26.1-2
has caused the Debian Bug report #1006465,
regarding python-dbusmock: Fails to build from source: README.rst is not
README.md
to be marked as done.
This means that y
Control: tag -1 pending
Hello,
Bug #1006465 in python-dbusmock 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/python-team/packages/python-dbusmock/-/commit/c19
Processing control commands:
> tag -1 pending
Bug #1006465 [src:python-dbusmock] python-dbusmock: Fails to build from source:
README.rst is not README.md
Added tag(s) pending.
--
1006465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006465
Debian Bug Tracking System
Contact ow...@bugs.deb
Your message dated Wed, 09 Mar 2022 11:05:10 +
with message-id
and subject line Bug#999761: fixed in fastjet 3.4.0+dfsg-1
has caused the Debian Bug report #999761,
regarding fastjet: ships a copy of siscone
to be marked as done.
This means that you claim that the problem has been dealt with.
On Tue, 08 Mar 2022 20:53:46 +0100 Paul Gevers wrote:
> Source: gcc-12
> Version: 12-20220222-1
> Severity: serious
> Tags: ftbfs
>
> Dear Matthias, GCC maintainers,
>
> gcc-12 fails to build from source on mips64el in unstable. Normally this
> isn't an issue, but it builds a Build-Depends of g
32 matches
Mail list logo
