Source: sagemath
Version: 9.4-3
Severity: serious
Control: close -1 9.5-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004872
Control: block -1 by 920147
Control: block -1 by 1009241
Dear maintainer(s),
The Release Team considers pac
Processing control commands:
> close -1 9.5-3
Bug #1009674 [src:sagemath] src:sagemath: fails to migrate to testing for too
long: FTBFS on armhf and mips64el
Marked as fixed in versions sagemath/9.5-3.
Bug #1009674 [src:sagemath] src:sagemath: fails to migrate to testing for too
long: FTBFS on a
Processing control commands:
> retitle -1 molmodel: FTBFS with tao-pegtl v3
Bug #1009402 [src:molmodel] molmodel: FTBFS: demangle.hpp:23:33: error:
‘string_view’ in namespace ‘std’ does not name a type
Changed Bug title to 'molmodel: FTBFS with tao-pegtl v3' from 'molmodel: FTBFS:
demangle.hpp:2
Control: retitle -1 molmodel: FTBFS with tao-pegtl v3
Control: tags -1 + confirmed
Control: block -1 by 1009415
Hello,
On 2022-04-12 20:47, Lucas Nussbaum wrote:
> /usr/include/tao/pegtl/match.hpp:139:15: error: use of deleted function
> ‘tao::pegtl::internal::marker M>::marker(tao::pegtl::inter
Your message dated Thu, 14 Apr 2022 04:33:52 +
with message-id
and subject line Bug#1009532: fixed in node-string-decoder 1.3.0-6
has caused the Debian Bug report #1009532,
regarding node-string-decoder: FTBFS: ERROR: Coverage for statements (93.29%)
does not meet global threshold (100%)
to b
Control: tag -1 pending
Hello,
Bug #1009532 in node-string-decoder 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-string-decoder/-/commit/44507f87
Processing control commands:
> tag -1 pending
Bug #1009532 [src:node-string-decoder] node-string-decoder: FTBFS: ERROR:
Coverage for statements (93.29%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009532
Debian Bug T
Your message dated Thu, 14 Apr 2022 04:03:50 +
with message-id
and subject line Bug#1009512: fixed in node-tacks 1.3.0-3
has caused the Debian Bug report #1009512,
regarding node-tacks: FTBFS: ERROR: Coverage for statements (94.04%) does not
meet global threshold (100%)
to be marked as done.
Processing control commands:
> tag -1 pending
Bug #1009512 [src:node-tacks] node-tacks: FTBFS: ERROR: Coverage for statements
(94.04%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009512
Debian Bug Tracking System
Con
Control: tag -1 pending
Hello,
Bug #1009512 in node-tacks 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-tacks/-/commit/06530e7c688a5b2c88b178ded4
Your message dated Thu, 14 Apr 2022 02:37:59 +
with message-id
and subject line Bug#1005147: fixed in golang-github-sylabs-sif 2.3.1-3
has caused the Debian Bug report #1005147,
regarding siftool: ships /usr/bin/test
to be marked as done.
This means that you claim that the problem has been de
Control: tags 1009240 + patch
Control: tags 1009240 + pending
Dear maintainer,
I've prepared an NMU for esys-particle (versioned as 2.3.5+dfsg2-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
SR
diff -Nru esys-particle-2.3.5+dfsg2/debian/chan
Processing control commands:
> tags 1009240 + patch
Bug #1009240 [src:esys-particle] esys-particle: autopkgtest regression since
rebuild for python3.10 as default
Added tag(s) patch.
> tags 1009240 + pending
Bug #1009240 [src:esys-particle] esys-particle: autopkgtest regression since
rebuild for
Package: foliate
Version: 2.6.4-1+dfsg1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: bgvaug...@gmail.com
After selecting a file, EPUB or MOBI, there's a spinner displayed, but the file
is never displayed. After closing foliate and reopening it, it shows the
Processing control commands:
> tag -1 pending
Bug #1005147 [siftool] siftool: ships /usr/bin/test
Added tag(s) pending.
--
1005147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1005147 in golang-github-sylabs-sif 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-github-sylabs-si
Your message dated Wed, 13 Apr 2022 22:19:11 +
with message-id
and subject line Bug#1009399: fixed in fonts-monoid 0.61-4
has caused the Debian Bug report #1009399,
regarding fonts-monoid: FTBFS: TypeError: 'float' object cannot be interpreted
as an integer
to be marked as done.
This means t
Hi there,
For what it's worth, upstream puppet does not yet suppport ruby 3.0.
see: https://puppet.com/docs/puppet/7/release_notes_puppet.html
puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there
upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only.
Processing commands for cont...@bugs.debian.org:
> block 900928 with 981822
Bug #900928 [wnpp] ITP: fractal -- Matrix.org messaging app for GNOME written
in Rust
Bug #959100 [wnpp] ITP: fractal -- Matrix.org messaging app for GNOME written
in Rust
Bug #963588 [wnpp] ITP: fractal -- Matrix.org me
Your message dated Wed, 13 Apr 2022 21:08:55 +
with message-id
and subject line Bug#1009470: fixed in lifeograph 2.0.2-2
has caused the Debian Bug report #1009470,
regarding lifeograph: FTBFS: ../src/ui_login.cpp:352:5: error: ‘utimes’ was not
declared in this scope; did you mean ‘utime’?
to
I did some digging:
The issue here is that sys.path is not being correctly configured
It is being initialized to:
['', '/tmp/cpython/lib/python310.zip', '/tmp/cpython/lib/python3.10',
'/tmp/cpython/lib/python3.10/lib-dynload']
not:
['', '/tmp/cpython/lib/python310.zip', '/tmp/cpython/lib/python
Package: dd-opentracing-cpp
Version: 1.3.1-1
Severity: serious
Tags: patch experimental
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi Stephen,
dd-opentracing-cpp fails to build from source against glibc 2.34 or later
because MINSIGSTKSZ is
[Resending whole thing. I think it is is important to have it publicly
available and to reach you, so adding it to the bugreport too.
Apparently team+dns@tracker.d.o isn't working and there's no archives]
I want to follow up on the todays ldns incident.
I think it was quite interesting.
The whol
Hi Anton,
* Anton Gladky [220412 19:18]:
> thanks a lot for NMU! Feel free to upload immediately,
> but please commit your changes into the git. Thanks!
okay, can/will do. Could you push the tag tags/upstream/2.2.5+dfsg2 into
git?
I have cancelled the NMU in the meantime.
Thanks,
Chris
Note that this will consistently fail alignment checks on architectures
which require alignment, because the initial buffer is allocated with
reasonable alignment (32bit) but the ethernet header is 14 bytes long, so
the TCP header fields will always be unaligned within the buffer.
On Wed, Apr 13,
Hi,
Sorry for my mistake, in the previous email sent by me the delay was 2
days and not 22. I had a problem with my keyboard.
Control: tag -1 pending
Hello,
Bug #1009609 in node-tar 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-tar/-/commit/1415a49cdac24bcb4e5c9edc3415e8
Processing control commands:
> tag -1 pending
Bug #1009609 [src:node-tar] node-tar: FTBFS: ERROR: Coverage for statements
(43.87%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009609
Debian Bug Tracking System
Contact
Here is a backtrace of the armhf SIGBUS.
Note that not all ARM implementations return SIGBUS which is probably why
this was not reproducible on the porter machine.
# gdb --args pktanon -c /usr/share/doc/pktanon/examples/profiles/profile.xml
./profiles/sample.pcap ./out.pcap
[...]
Reading symbols
Package: ucarp
Version: 1.5.2-2.2
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for ucarp (versioned as 1.5.2-2.3) and
uploaded it to DELAYED/22. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u ucarp-1.5.2/debian/changelog ucarp-1.5.2/debia
BTW, Daniel, please re-tag 1.7.1-3 - this is what's at the tip of master now.
I hope anyway :)
Thanks,
/mjt
Fixed my branch on the ldns repo, rebasing it on top of now-okay master.
If we ever need one more 1.7 release it will be easier to rebase now with
the conflicts resolved.
I have to review my branch again, I think something might not be right
there after the rebase on top of dkg's changes. I will
Hi Hervé,
Am Wed, Apr 13, 2022 at 09:46:59AM -0700 schrieb Hervé Pagès:
> @tillea And most importantly, it seems that Debian is building the wrong
> version of Bioconductor. The `S.h` file was removed from R 4.2 and they are
> reporting a bug for **Biostrings** 2.62.0, which belongs to Bioconduc
Processing control commands:
> affects -1 src:evolution-ews
Bug #1009660 [src:gnome-contacts] gnome-contacts: 42 is incompatible with
evolution-ews
Added indication that 1009660 affects src:evolution-ews
> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/222
Bug #1009660 [src:g
Source: gnome-contacts
Version: 42.0-1
Severity: serious
Control: affects -1 src:evolution-ews
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/222
gnome-contacts 42 won't start if evolution-ews is installed.
Thank you,
Jeremy Bicha
Okay guys.
I thought about this a bit more.
One wrong action by one developer does not make the environment
unhealthy.
I fixed the mess done to the master branch.
I think - provided this wont happen again - it's okay to work
on this to fix the rest of the mess done.
I'm doing this right now.
Patrick Matthäi dixit:
> But how did it happened, that .rpmdb is owned by root in your own user
> directory?
rpm is installed, I run sudo apt-get something.
> Same in my test, if I use $ sudo needrestart => .rpmdb of ~root/ is used
Hmm.
Maybe !env_reset in sudoers would do this…
bye,
//mirabi
13.04.2022 21:19, Daniel Kahn Gillmor wrote:
..
reviewed and i'll push that to salsa as a "debian/experimental" branch
later today, if either of you want to take a look at what i'm
considering for release.
The whole thing was ready, polished, everything addressed.
If you wanted another 1.7.1 up
13.04.2022 21:29, Michael Tokarev wrote:
The only prob is that the master branch on the ldns repository is
seriously messed up.
Also you've made similar commits as I did, but in an incomplete way
(like the watch file update).
Thanks,
/mjt
13.04.2022 21:19, Daniel Kahn Gillmor wrote:
Hi Michael and Santiago--
I've now uploaded ldns 1.7.1-3 with the associated fix for 1009385. I'm
reviewing Michael's changes for 1.8.1, and they're looking good to me.
Thank you for all that work, Michael! I think we should consider
uploading 1.8.1
Package: mysql-workbench
Version: 8.0.26+dfsg-1+b1
Severity: serious
Attempting to install mysql-workbench under sid fails with the following
output:
sicelo@tpt440p:~$ sudo apt install mysql-workbench
Reading package lists... Done
Building dependency tree... Done
Reading state information... D
Hi Michael and Santiago--
I've now uploaded ldns 1.7.1-3 with the associated fix for 1009385. I'm
reviewing Michael's changes for 1.8.1, and they're looking good to me.
Thank you for all that work, Michael! I think we should consider
uploading 1.8.1 into experimental while we wait for 1.7.1-3 to
Your message dated Wed, 13 Apr 2022 18:04:17 +
with message-id
and subject line Bug#1009385: fixed in ldns 1.7.1-3
has caused the Debian Bug report #1009385,
regarding libldns3 1.7.1-2.1 changes output of ldns-key2ds, causing FTBFS on
dns-root-data
to be marked as done.
This means that you c
Thanks both Michael and Santiago for sorting this out!
I agree that backporting
https://github.com/NLnetLabs/ldns/commit/4d2057f0b5220487882be1b19c302833b84cffe3
to 1.7.1 is the most reasonable/conservative fix. We want that to
propagate into testing as soon as possible without risking being bloc
On 4/13/22 12:11, Anthony Callegaro wrote:
Me again,
I tried debugging further. If I remove the Preferences file I am then able to
start chromium and if I try to restore pages from the window that makes it
crashes manually I manage to restore some tabs but some will make it crash
consistently
This issue is related to https://bugs.debian.org/1009097
Thank you,
Jeremy Bicha
Processing commands for cont...@bugs.debian.org:
> affects 1009448 + src:libpdf-builder-perl
Bug #1009448 [src:libpdf-builder-perl] libpdf-builder-perl: FTBFS:
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added indication that 1009448 affects src:libpdf-builder-perl
> th
Processing control commands:
> tag -1 + confirmed
Bug #1009448 [src:libpdf-builder-perl] libpdf-builder-perl: FTBFS:
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) confirmed.
> forwarded -1 https://github.com/PhilterPaper/Perl-PDF-Builder/issues/177
Bug #10094
Control: tag -1 + confirmed
Control: forwarded -1
https://github.com/PhilterPaper/Perl-PDF-Builder/issues/177
Control: block -1 with 1007752
On Tue, 12 Apr 2022 20:39:41 +0200, Lucas Nussbaum wrote:
> Source: libpdf-builder-perl
> Version: 3.023-1
> Severity: serious
> Justification: FTBFS
> Tag
Your message dated Wed, 13 Apr 2022 16:20:32 +
with message-id
and subject line Bug#1009439: fixed in fontparts 0.10.4-1
has caused the Debian Bug report #1009439,
regarding fontparts: FTBFS: AttributeError: module 'collections' has no
attribute 'Hashable'
to be marked as done.
This means th
Processing commands for cont...@bugs.debian.org:
> tags 1009406 + confirmed
Bug #1009406 [src:libzonemaster-perl] libzonemaster-perl: FTBFS: dh_auto_test:
error: make -j1 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you
Your message dated Wed, 13 Apr 2022 16:21:12 +
with message-id
and subject line Bug#1008395: fixed in golang-github-bmatsuo-lmdb-go
1.8.0+git20170215.a14b5a3-3
has caused the Debian Bug report #1008395,
regarding golang-github-bmatsuo-lmdb-go: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-
Processing commands for cont...@bugs.debian.org:
> tags 1009412 + confirmed
Bug #1009412 [src:libsendmail-milter-perl] libsendmail-milter-perl: FTBFS:
perl.h:736:25: error: expected expression before ‘do’
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need as
Processing control commands:
> tag -1 pending
Bug #1008395 [src:golang-github-bmatsuo-lmdb-go] golang-github-bmatsuo-lmdb-go:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8
github.com/bmatsuo/lmdb-go/cmd/lmdb_copy
github.com/bmatsuo/lmdb-go/cmd/lmdb_stat
github
Control: tag -1 pending
Hello,
Bug #1008395 in golang-github-bmatsuo-lmdb-go 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-github-bma
Processing commands for cont...@bugs.debian.org:
> forwarded 1008395 https://github.com/bmatsuo/lmdb-go/issues/143
Bug #1008395 [src:golang-github-bmatsuo-lmdb-go] golang-github-bmatsuo-lmdb-go:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8
github.com/bmatsuo/lm
Just a quick update:
The problem of this particular one is:
in puppet/file_system.rb
def self.symlink(path, dest, options = {})
@impl.symlink(assert_path(path), dest, options)
end
Changing this to:
def self.symlink(path, dest, **options)
@impl.symlink(assert_path(path), dest, **o
Your message dated Wed, 13 Apr 2022 15:11:52 +
with message-id
and subject line Bug#1009595: fixed in node-buffer-shims 1.0.0-5
has caused the Debian Bug report #1009595,
regarding node-buffer-shims: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be m
Your message dated Wed, 13 Apr 2022 15:10:51 +
with message-id
and subject line Bug#1009400: fixed in mathcomp-analysis 0.5.0-3
has caused the Debian Bug report #1009400,
regarding mathcomp-analysis: FTBFS: Error: Cannot find library elpi.elpi in
loadpath
to be marked as done.
This means tha
Your message dated Wed, 13 Apr 2022 15:11:58 +
with message-id
and subject line Bug#1009586: fixed in node-trysound-sax 0.2.0-3
has caused the Debian Bug report #1009586,
regarding node-trysound-sax: FTBFS: ERROR: Coverage for statements (79.38%)
does not meet global threshold (100%)
to be ma
Processing control commands:
> tag -1 pending
Bug #1009595 [src:node-buffer-shims] node-buffer-shims: FTBFS: dh_auto_test:
error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.
--
1009595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009595
Debian Bug Trac
Control: tag -1 pending
Hello,
Bug #1009595 in node-buffer-shims 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-buffer-shims/-/commit/0ae461874a0c
Your message dated Wed, 13 Apr 2022 14:51:40 +
with message-id
and subject line Bug#1009509: fixed in node-vasync 2.2.1-2
has caused the Debian Bug report #1009509,
regarding node-vasync: FTBFS: ERROR: Coverage for statements (71.91%) does not
meet global threshold (100%)
to be marked as done
Your message dated Wed, 13 Apr 2022 14:51:34 +
with message-id
and subject line Bug#1009485: fixed in node-typedarray 0.0.6-3
has caused the Debian Bug report #1009485,
regarding node-typedarray: FTBFS: ERROR: Coverage for statements (41.62%) does
not meet global threshold (100%)
to be marked
Your message dated Wed, 13 Apr 2022 14:51:45 +
with message-id
and subject line Bug#1009495: fixed in node-wrappy 1.0.2-3
has caused the Debian Bug report #1009495,
regarding node-wrappy: FTBFS: ERROR: Coverage for statements (88.88%) does not
meet global threshold (100%)
to be marked as done
Control: tag -1 pending
Hello,
Bug #1009586 in node-trysound-sax 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-trysound-sax/-/commit/f349d5a62ec9
Processing control commands:
> tag -1 pending
Bug #1009586 [src:node-trysound-sax] node-trysound-sax: FTBFS: ERROR: Coverage
for statements (79.38%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009586
Debian Bug Track
Processing commands for cont...@bugs.debian.org:
> fixed 1009587 5.5.3+~cs8.20.16-1
Bug #1009587 [src:node-tape] node-tape: FTBFS: ERROR: Coverage for statements
(48.12%) does not meet global threshold (100%)
Marked as fixed in versions node-tape/5.5.3+~cs8.20.16-1.
> close 1009587
Bug #1009587 [
Processing commands for cont...@bugs.debian.org:
> fixed 1005912 hydrogen/1.1.1+819.g676dbf8c-1~exp1
Bug #1005912 {Done: Nicholas D Steeves } [src:hydrogen]
hydrogen: autopkgtest regression on arm64 and ppc64el:
H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.
Marked as fixed in v
Control: tag -1 pending
Hello,
Bug #1009509 in node-vasync 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-vasync/-/commit/8426fbbd7279c058ff6e7271
Processing control commands:
> tag -1 pending
Bug #1009509 [src:node-vasync] node-vasync: FTBFS: ERROR: Coverage for
statements (71.91%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009509
Debian Bug Tracking System
C
Your message dated Wed, 13 Apr 2022 14:36:59 +
with message-id
and subject line Bug#1009563: fixed in node-mkdirp 1.0.4+~1.0.2-2
has caused the Debian Bug report #1009563,
regarding node-mkdirp: FTBFS: ERROR: Coverage for statements (83.92%) does not
meet global threshold (100%)
to be marked
Processing control commands:
> tag -1 pending
Bug #1009485 [src:node-typedarray] node-typedarray: FTBFS: ERROR: Coverage for
statements (41.62%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009485
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1009485 in node-typedarray 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-typedarray/-/commit/a9fa2425563cb57f
Control: tag -1 pending
Hello,
Bug #1009495 in node-wrappy 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-wrappy/-/commit/cc6e5de04500a7ce1fab54d3
Processing control commands:
> tag -1 pending
Bug #1009495 [src:node-wrappy] node-wrappy: FTBFS: ERROR: Coverage for
statements (88.88%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009495
Debian Bug Tracking System
C
Package: puppet
Version: 5.5.22-4
Severity: serious
Justification: Fails at core functions
Since testing switched /usr/bin/ruby to use ruby3.0, a previously working
Puppet manifest fails:
s...@larsa.muc:/tmp$ ruby3.0 /usr/bin/puppet apply t.pp
Notice: Compiled catalog for larsa.muc.corp.google.co
Processing control commands:
> tag -1 pending
Bug #1009563 [src:node-mkdirp] node-mkdirp: FTBFS: ERROR: Coverage for
statements (83.92%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009563
Debian Bug Tracking System
C
Control: tag -1 pending
Hello,
Bug #1009563 in node-mkdirp 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-mkdirp/-/commit/bf8601424e2070dfd0792f8c
Control: tags -1 upstream
Control: forwarded -1 https://github.com/Bioconductor/Biostrings/issues/66
Processing control commands:
> tags -1 upstream
Bug #1009467 [src:r-bioc-biostrings] r-bioc-biostrings: FTBFS:
BitMatrix.c:9:10: fatal error: S.h: No such file or directory
Added tag(s) upstream.
> forwarded -1 https://github.com/Bioconductor/Biostrings/issues/66
Bug #1009467 [src:r-bioc-biostrin
Your message dated Wed, 13 Apr 2022 13:51:20 +
with message-id
and subject line Bug#984606: fixed in sword-comm-scofield 2.0-1
has caused the Debian Bug report #984606,
regarding sword-comm-scofield: Missing source
to be marked as done.
This means that you claim that the problem has been deal
On 13.04.2022 16:44, Santiago Ruano Rincón wrote:
..
So what do we do now? I think the best is to include
this fix as 1.7.1-3 (provided it actually fixes the
issue) for now, instead of uploading 1.8.
Why just don't uploading 1.8.1?
Well, we know 1.7 (sort of) works while 1.8 might cause
surp
El 13/04/22 a las 16:25, Michael Tokarev escribió:
> [Just a quick follow-up]
>
> On 13.04.2022 15:52, Santiago Ruano Rincón wrote:
> [...]
> > It seems it was fixed on 1.8.0.
> > https://github.com/NLnetLabs/ldns/commit/4d2057f0b5220487882be1b19c302833b84cffe3
>
> Wonderful.. :) Thank you Santi
I prepared a PR that fix this:
https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/13
OpenPGP_signature
Description: OpenPGP digital signature
Your message dated Wed, 13 Apr 2022 13:35:18 +
with message-id
and subject line Bug#1009393: fixed in schleuder-gitlab-ticketing 1.0.0-3
has caused the Debian Bug report #1009393,
regarding schleuder-gitlab-ticketing: FTBFS: ERROR: Test "ruby3.0" failed:
/usr/lib/ruby/vendor_ruby/rubygems/spe
Processing control commands:
> forwarded -1 https://github.com/NLnetLabs/ldns/issues/142
Bug #1009385 [libldns3] libldns3 1.7.1-2.1 changes output of ldns-key2ds,
causing FTBFS on dns-root-data
Set Bug forwarded-to-address to 'https://github.com/NLnetLabs/ldns/issues/142'.
> tags -1 + pending
Bug
Control: forwarded -1 https://github.com/NLnetLabs/ldns/issues/142
Control: tags -1 + pending
On Wed, 13 Apr 2022 14:52:58 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?=
wrote:
> Control: tags -1 + upstream
> Control: tags -1 + forwarded https://github.com/NLnetLabs/ldns/issues/142
🙈
> El 13/0
Your message dated Wed, 13 Apr 2022 13:35:05 +
with message-id
and subject line Bug#1009567: fixed in node-aproba 2.0.0-3
has caused the Debian Bug report #1009567,
regarding node-aproba: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as don
Your message dated Wed, 13 Apr 2022 13:35:11 +
with message-id
and subject line Bug#1009552: fixed in node-asn1 0.2.6+~0.2.0-2
has caused the Debian Bug report #1009552,
regarding node-asn1: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as
[Just a quick follow-up]
On 13.04.2022 15:52, Santiago Ruano Rincón wrote:
[...]
It seems it was fixed on 1.8.0.
https://github.com/NLnetLabs/ldns/commit/4d2057f0b5220487882be1b19c302833b84cffe3
Wonderful.. :) Thank you Santiago!
So, the prob should've be there after just any
recompile of ldn
Processing commands for cont...@bugs.debian.org:
> tags 1009383 + experimental
Bug #1009383 [src:gromacs] gromacs: FTBFS: AttributeError: module 'collections'
has no attribute 'Iterable'
Added tag(s) experimental.
> tags 1009439 + experimental
Bug #1009439 [src:fontparts] fontparts: FTBFS: Attrib
Control: tag -1 pending
Hello,
Bug #1009567 in node-aproba 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-aproba/-/commit/5df01e2b084b0eb8134814ab
Processing control commands:
> tag -1 pending
Bug #1009552 [src:node-asn1] node-asn1: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.
--
1009552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009552
Debian Bug Tracking System
Cont
Processing control commands:
> tag -1 pending
Bug #1009567 [src:node-aproba] node-aproba: FTBFS: dh_auto_test: error: /bin/sh
-ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.
--
1009567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009567
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1009552 in node-asn1 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-asn1/-/commit/3b6738e8e70275112b9a6d5f6d66
Your message dated Wed, 13 Apr 2022 13:03:56 +
with message-id
and subject line Bug#1009449: fixed in coq-hierarchy-builder 1.2.1-4
has caused the Debian Bug report #1009449,
regarding coq-hierarchy-builder: FTBFS: make[2]: coq_makefile: No such file or
directory
to be marked as done.
This m
Processing control commands:
> tags -1 + upstream
Bug #1009385 [libldns3] libldns3 1.7.1-2.1 changes output of ldns-key2ds,
causing FTBFS on dns-root-data
Added tag(s) upstream.
> tags -1 + forwarded https://github.com/NLnetLabs/ldns/issues/142
Unknown tag/s: forwarded, https://github.com/NLnetLa
Control: tags -1 + upstream
Control: tags -1 + forwarded https://github.com/NLnetLabs/ldns/issues/142
El 13/04/22 a las 10:37, Michael Tokarev escribió:
> 13.04.2022 10:09, Michael Tokarev wrote:
> ..
> > But let's try.
> >
> > How this utility is used in building of dns-root-data? Lemme take a
Your message dated Wed, 13 Apr 2022 12:05:01 +
with message-id
and subject line Bug#1009588: fixed in node-config-chain 1.1.12-3
has caused the Debian Bug report #1009588,
regarding node-config-chain: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be
1 - 100 of 157 matches
Mail list logo
