Your message dated Tue, 19 Apr 2022 06:33:55 +
with message-id
and subject line Bug#1009580: fixed in node-inline-source-map 0.6.2~git-7
has caused the Debian Bug report #1009580,
regarding node-inline-source-map: FTBFS: ERROR: Coverage for statements
(98.18%) does not meet global threshold (
Your message dated Tue, 19 Apr 2022 06:34:00 +
with message-id
and subject line Bug#1009565: fixed in node-module-deps 6.2.3-3
has caused the Debian Bug report #1009565,
regarding node-module-deps: FTBFS: ERROR: Coverage for statements (86.71%) does
not meet global threshold (100%)
to be mark
Your message dated Tue, 19 Apr 2022 06:33:50 +
with message-id
and subject line Bug#1009538: fixed in node-detective 5.2.0-5
has caused the Debian Bug report #1009538,
regarding node-detective: FTBFS: ERROR: Coverage for statements (92.15%) does
not meet global threshold (100%)
to be marked a
Your message dated Tue, 19 Apr 2022 06:34:05 +
with message-id
and subject line Bug#1009513: fixed in node-object-inspect 1.11.0+~cs1.8.1-3
has caused the Debian Bug report #1009513,
regarding node-object-inspect: FTBFS: ERROR: Coverage for statements (60.76%)
does not meet global threshold (
Your message dated Tue, 19 Apr 2022 06:33:45 +
with message-id
and subject line Bug#1009507: fixed in node-deps-sort 2.0.1-3
has caused the Debian Bug report #1009507,
regarding node-deps-sort: FTBFS: ERROR: Coverage for statements (95.23%) does
not meet global threshold (100%)
to be marked a
Processing control commands:
> tag -1 pending
Bug #1009565 [src:node-module-deps] node-module-deps: FTBFS: ERROR: Coverage
for statements (86.71%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009565
Debian Bug Trackin
Control: tag -1 pending
Hello,
Bug #1009565 in node-module-deps 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-module-deps/-/commit/a082d2d74a0c6e
Processing control commands:
> tag -1 pending
Bug #1009513 [src:node-object-inspect] node-object-inspect: FTBFS: ERROR:
Coverage for statements (60.76%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009513
Debian Bug T
Processing control commands:
> tag -1 pending
Bug #1009580 [src:node-inline-source-map] node-inline-source-map: FTBFS: ERROR:
Coverage for statements (98.18%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009580
Debian
Control: tag -1 pending
Hello,
Bug #1009513 in node-object-inspect 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-object-inspect/-/commit/7e55227d
Control: tag -1 pending
Hello,
Bug #1009580 in node-inline-source-map 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-inline-source-map/-/commit/5f
Your message dated Tue, 19 Apr 2022 06:19:36 +
with message-id
and subject line Bug#1009592: fixed in node-process-nextick-args 2.0.1-3
has caused the Debian Bug report #1009592,
regarding node-process-nextick-args: FTBFS: ERROR: Coverage for statements
(10%) does not meet global threshold (1
Your message dated Tue, 19 Apr 2022 06:19:19 +
with message-id
and subject line Bug#1009556: fixed in node-invariant 2.2.4-2
has caused the Debian Bug report #1009556,
regarding node-invariant: FTBFS: ERROR: Coverage for statements (81.25%) does
not meet global threshold (100%)
to be marked a
Your message dated Tue, 19 Apr 2022 06:19:13 +
with message-id
and subject line Bug#1009559: fixed in node-falafel 2.2.4-4
has caused the Debian Bug report #1009559,
regarding node-falafel: FTBFS: ERROR: Coverage for statements (98.11%) does not
meet global threshold (100%)
to be marked as do
Your message dated Tue, 19 Apr 2022 06:19:07 +
with message-id
and subject line Bug#1009544: fixed in node-combine-source-map 0.8.0+ds-8
has caused the Debian Bug report #1009544,
regarding node-combine-source-map: FTBFS: ERROR: Coverage for statements
(93.44%) does not meet global threshold
Your message dated Tue, 19 Apr 2022 06:19:00 +
with message-id
and subject line Bug#1009502: fixed in node-block-stream 0.0.9-4
has caused the Debian Bug report #1009502,
regarding node-block-stream: FTBFS: ERROR: Coverage for statements (98.24%)
does not meet global threshold (100%)
to be ma
Your message dated Tue, 19 Apr 2022 06:18:53 +
with message-id
and subject line Bug#1009503: fixed in node-archy 1.0.0-5
has caused the Debian Bug report #1009503,
regarding node-archy: FTBFS: ERROR: Coverage for branches (95.45%) does not
meet global threshold (100%)
to be marked as done.
T
Your message dated Tue, 19 Apr 2022 06:19:24 +
with message-id
and subject line Bug#1009486: fixed in node-isarray 2.0.5-4
has caused the Debian Bug report #1009486,
regarding node-isarray: FTBFS: ERROR: Coverage for statements (66.66%) does not
meet global threshold (100%)
to be marked as do
Control: tag -1 pending
Hello,
Bug #1009507 in node-deps-sort 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-deps-sort/-/commit/fe57298767ca87b0af
Processing control commands:
> tag -1 pending
Bug #1009507 [src:node-deps-sort] node-deps-sort: FTBFS: ERROR: Coverage for
statements (95.23%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009507
Debian Bug Tracking Sy
Processing control commands:
> tag -1 pending
Bug #1009538 [src:node-detective] node-detective: FTBFS: ERROR: Coverage for
statements (92.15%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009538
Debian Bug Tracking Sy
Control: tag -1 pending
Hello,
Bug #1009538 in node-detective 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-detective/-/commit/0dab2546c8846ab97d
Processing control commands:
> tag -1 pending
Bug #1009486 [src:node-isarray] node-isarray: FTBFS: ERROR: Coverage for
statements (66.66%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009486
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1009486 in node-isarray 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-isarray/-/commit/1b1d59384ac2e11ec57f27
Control: tag -1 pending
Hello,
Bug #1009511 in node-once 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-once/-/commit/4d52f986ecc7cc8e36a97b2b9781
Processing control commands:
> tag -1 pending
Bug #1009511 [src:node-once] node-once: FTBFS: ERROR: Coverage for statements
(83.33%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009511
Debian Bug Tracking System
Conta
Processing control commands:
> tag -1 pending
Bug #1009559 [src:node-falafel] node-falafel: FTBFS: ERROR: Coverage for
statements (98.11%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009559
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1009559 in node-falafel 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-falafel/-/commit/61681a883eee23f14ae012
Processing control commands:
> tag -1 pending
Bug #1009502 [src:node-block-stream] node-block-stream: FTBFS: ERROR: Coverage
for statements (98.24%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009502
Debian Bug Track
Control: tag -1 pending
Hello,
Bug #1009502 in node-block-stream 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-block-stream/-/commit/56871c27f0d8
Control: tag -1 pending
Hello,
Bug #1009544 in node-combine-source-map 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-combine-source-map/-/commit/
Your message dated Tue, 19 Apr 2022 06:03:50 +
with message-id
and subject line Bug#1009571: fixed in node-call-limit 1.1.1-3
has caused the Debian Bug report #1009571,
regarding node-call-limit: FTBFS: ERROR: Coverage for statements (83.58%) does
not meet global threshold (100%)
to be marked
Processing control commands:
> tag -1 pending
Bug #1009544 [src:node-combine-source-map] node-combine-source-map: FTBFS:
ERROR: Coverage for statements (93.44%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009544
Debi
Your message dated Tue, 19 Apr 2022 06:03:45 +
with message-id
and subject line Bug#1009530: fixed in node-arrify 2.0.1-3
has caused the Debian Bug report #1009530,
regarding node-arrify: FTBFS: ERROR: Coverage for statements (90.9%) does not
meet global threshold (100%)
to be marked as done.
Your message dated Tue, 19 Apr 2022 06:03:55 +
with message-id
and subject line Bug#1009545: fixed in node-jsonstream 1.3.5-2
has caused the Debian Bug report #1009545,
regarding node-jsonstream: FTBFS: ERROR: Coverage for statements (50.89%) does
not meet global threshold (100%)
to be marked
Control: tag -1 pending
Hello,
Bug #1009556 in node-invariant 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-invariant/-/commit/038e421d8c0e2c8a6b
Processing control commands:
> tag -1 pending
Bug #1009556 [src:node-invariant] node-invariant: FTBFS: ERROR: Coverage for
statements (81.25%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009556
Debian Bug Tracking Sy
Control: tag -1 pending
Hello,
Bug #1009592 in node-process-nextick-args 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-process-nextick-args/-/com
Processing control commands:
> tag -1 pending
Bug #1009592 [src:node-process-nextick-args] node-process-nextick-args: FTBFS:
ERROR: Coverage for statements (10%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009592
Deb
Processing control commands:
> tag -1 pending
Bug #1009503 [src:node-archy] node-archy: FTBFS: ERROR: Coverage for branches
(95.45%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009503
Debian Bug Tracking System
Conta
Control: tag -1 pending
Hello,
Bug #1009503 in node-archy 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-archy/-/commit/df6d66db38594ced593a4e6002
Processing control commands:
> tag -1 pending
Bug #1009530 [src:node-arrify] node-arrify: FTBFS: ERROR: Coverage for
statements (90.9%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009530
Debian Bug Tracking System
Co
Control: tag -1 pending
Hello,
Bug #1009530 in node-arrify 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-arrify/-/commit/549c9701aa858c86516022fa
Processing control commands:
> tag -1 pending
Bug #1009571 [src:node-call-limit] node-call-limit: FTBFS: ERROR: Coverage for
statements (83.58%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009571
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1009571 in node-call-limit 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-call-limit/-/commit/465211ef07ee26d5
Control: tag -1 pending
Hello,
Bug #1009545 in node-jsonstream 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-jsonstream/-/commit/c7a267bdddc7ce1b
Processing control commands:
> tag -1 pending
Bug #1009545 [src:node-jsonstream] node-jsonstream: FTBFS: ERROR: Coverage for
statements (50.89%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009545
Debian Bug Tracking
> I've prepared an NMU for vdirsyncer (versioned as 0.18.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
As a team member, feel free to reschedule this to 0-day.
I've merged your git tree.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 4
Your message dated Tue, 19 Apr 2022 03:33:51 +
with message-id
and subject line Bug#1009240: fixed in esys-particle 2.3.5+dfsg2-4.1
has caused the Debian Bug report #1009240,
regarding esys-particle: autopkgtest regression since rebuild for python3.10 as
default
to be marked as done.
This me
Your message dated Tue, 19 Apr 2022 03:19:34 +
with message-id
and subject line Bug#981822: fixed in rust-bytemuck 1.9.1-1
has caused the Debian Bug report #981822,
regarding librust-bytemuck-dev: Depends: librust-bytemuck-derive-1+default-dev
but it is not installable
to be marked as done.
Your message dated Tue, 19 Apr 2022 03:19:54 +
with message-id
and subject line Bug#974117: fixed in rust-image 0.23.14-1
has caused the Debian Bug report #974117,
regarding rust-image: FTBFS build-depends on librust-tiff-0.3+default-dev
to be marked as done.
This means that you claim that th
Control: tags 999034 + patch
Control: tags 999034 + pending
Dear maintainer,
I've prepared an NMU for squidtaild (versioned as 2.1a6-6.2) and
uploaded it to DELAYED/22. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru squidtaild-2.1a6/debian/changelog squidtaild-2.1a6
Processing control commands:
> tags 999034 + patch
Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets
build-arch and/or build-indep
Added tag(s) patch.
> tags 999034 + pending
Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets
build-arch an
He Andreas, thanks for the feedback!
Le 2022-04-17 à 10 h 42, Andreas Metzler a écrit :
Yes, a rebuild will get a binary which works against the new
library, however (partial) upgrades from bookworm won't work.
BTW, the symbol file seems to be wrong:
| h_execute_query_sqlite@Base 1.4.15
the sy
Your message dated Tue, 19 Apr 2022 01:18:47 +
with message-id
and subject line Bug#999095: fixed in clif 0.93-9.2
has caused the Debian Bug report #999095,
regarding clif: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim tha
Your message dated Tue, 19 Apr 2022 01:18:47 +
with message-id
and subject line Bug#965462: fixed in clif 0.93-9.2
has caused the Debian Bug report #965462,
regarding clif: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the proble
Processing control commands:
> tags 999018 + patch
Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch
and/or build-indep
Added tag(s) patch.
> tags 999018 + pending
Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch
and/or build-indep
Add
Processing control commands:
> tags 965595 + patch
Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and
6 in bookworm
Added tag(s) patch.
> tags 965595 + pending
Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and
6 in bookworm
Added tag(s)
Control: tags 999018 + patch
Control: tags 999018 + pending
Dear maintainer,
I've prepared an NMU for xvier (versioned as 1.0-7.7) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u xvier-1.0/debian/changelog xvier-1.0/debian/changelog
--- xv
Control: tags 965595 + patch
Control: tags 965595 + pending
Dear maintainer,
I've prepared an NMU for info2www (versioned as 1.2.2.9-24.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u info2www-1.2.2.9/debian/changelog info2www-1.2.2.9/d
Your message dated Mon, 18 Apr 2022 23:18:46 +
with message-id
and subject line Bug#999015: fixed in clamassassin 1.2.4-1.2
has caused the Debian Bug report #999015,
regarding clamassassin: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means t
Your message dated Mon, 18 Apr 2022 23:18:46 +
with message-id
and subject line Bug#965468: fixed in clamassassin 1.2.4-1.2
has caused the Debian Bug report #965468,
regarding clamassassin: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you clai
} > Upstream changed paths for the framework manifest files in recent
} > releases and did not maintain backward compatibility links resulting
} > in 4.3.4 no longer being able to install the frameworks.
}
} Had a quick look, and it's worse than that. Not just a change in paths,
} but an entire ne
Your message dated Mon, 18 Apr 2022 20:52:29 +
with message-id
and subject line Bug#1009054: fixed in openshot-qt 2.6.1+dfsg1-2
has caused the Debian Bug report #1009054,
regarding Just crashes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Mon, 18 Apr 2022 20:48:48 +
with message-id
and subject line Bug#965457: fixed in choosewm 0.1.6-3.1
has caused the Debian Bug report #965457,
regarding choosewm: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that t
Control: tag -1 pending
Hello,
Bug #1009054 in openshot-qt 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/multimedia-team/openshot-qt/-/commit/415288424c643ce0
Processing control commands:
> tag -1 pending
Bug #1009054 [openshot-qt] Just crashes
Added tag(s) pending.
--
1009054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
This bug is blocking openimageio, which blocks blender. Can this be
fixed, is it still not reproducible?
Best Regards,
Jonathan Rubenstein
la...@debian.org dixit:
>On my bullseye machine sudo rpm -qa creates the subdirectory in
>/root/.rpmdb as root. So IMO this works correct.
Not with !env_reset in sudoers, though :( as I wrote in the last mail.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht d
Package: python3-pylsp-flake8
Version: 0.4.0-2
Severity: serious
The debian/copyright file for this package currently does not state
the location of the upstream sources. (Marked "serious" because this
is a violation of Policy section 12.5.)
I'm happy to fix this myself if you would like me to.
Processing commands for cont...@bugs.debian.org:
> found 1009415 0.5.3+ds-1
Bug #1009415 [src:gemmi] gemmi: FTBFS with tao-pegtl v3
Marked as found in versions gemmi/0.5.3+ds-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009415: https://bugs.debian.org/cgi-b
Processing control commands:
> close -1 1.3.1-1
Bug #1009833 [src:connectagram] src:connectagram: fails to migrate to testing
for too long: new build dependency not available on s390x
Marked as fixed in versions connectagram/1.3.1-1.
Bug #1009833 [src:connectagram] src:connectagram: fails to migr
Source: connectagram
Version: 1.2.11-2
Severity: serious
Control: close -1 1.3.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 day
Processing control commands:
> close -1 1.6.1.1-1
Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for too
long: new build dependency not available on s390x
Marked as fixed in versions tanglet/1.6.1.1-1.
Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for to
Source: tanglet
Version: 1.5.6-1
Severity: serious
Control: close -1 1.6.1.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as
Hi,
The FTBFS is reproducable `debuild -uc -us`.
Below is a screenshot of my repair attempt.
8<--8<--8<--8<--
stappers@myhost:~/src/lirc
$ cd python-pkg/tests/
stappers@myhost:~/src/lirc/python-pkg/tests
$ python3 -m unittest discover && rm backend.log
E
==
Processing control commands:
> close -1 2.2.0-1
Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long:
new build dependency not available on s390x
Marked as fixed in versions tetzle/2.2.0-1.
Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long:
Source: tetzle
Version: 2.1.6-1
Severity: serious
Control: close -1 2.2.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as ha
Processing control commands:
> close -1 2.2+ds1-1
Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too
long: new build-dependency doesn't migrate
Marked as fixed in versions uncalled/2.2+ds1-1.
Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too
Source: uncalled
Version: 2.2+ds-3
Severity: serious
Control: close -1 2.2+ds1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days
Processing commands for cont...@bugs.debian.org:
> affects 1008189 src:ghex
Bug #1008189 [src:meson] meson: gnome module incorrectly requires
gtk4-update-icon-cache
Added indication that 1008189 affects src:ghex
>
End of message, stopping processing here.
Please contact me if you need assistance
Package: hfst
Version: 3.16.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
hfst is currently not able to migrate due to dependency issues on armel
and mipsel:
Issues preventing migration:
∙ ∙ Impossible Depends: hfst -> libfst8/1.6.3-2/armel
∙ ∙ Impossible Depends: hfst -> libfst8/1.6.3
On Mon, Apr 18, 2022 at 07:46:34PM +0200, Sascha Steinbiss wrote:
> Hi,
> > > Do you think we should wait for this to be fixed? As I said before I (just
> > > from my practical point of view) would be in favor of just removing the
> > > problematic architectures.
> > I have no opinion on this. B
On Mon, Apr 18, 2022 at 06:32:07PM +0200, Thomas Lange wrote:
> > On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev
> > said:
>
>
> > If you run sudo without the "set_home" option, thus making it preserve
> > the HOME environment variable, rpm run as root with HOME set to
>
Hm, good question. What I'd start doing is looking at the
~/.cache/chromium and ~/.config/chromium snapshots, making copies, and
then trying to run chromium with random stuff deleted.
For example, on my system I have ~/.cache/chromium/Profile
1/old_Cache_000 and ~/.cache/chromium/System Profi
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package lxqt-build-tools
> # 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.or
Hi,
Do you think we should wait for this to be fixed? As I said before I (just
from my practical point of view) would be in favor of just removing the
problematic architectures.
I have no opinion on this. But if you want the package to be releasable,
you will need to change it so that it is n
Source: halide
Version: 14.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
halide FTBFS on arm64:
317/569 Test #317: correctness_strided_load ...
Passed1.12 sec
Start 318: correctness
Source: gnss-sdr
Version: 0.0.16-1
Severity: serious
Tags: sid bookworm
gnss-sdr's autopkgtest fail with gr-osmosdr 0.2.3-6
autopkgtest [14:10:33]: test testgnsssdr: [---
terminate called after throwing an instance of 'std::runtime_error'
what(): rpcmanager: Aggregator not
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:r-bioc-biostrings
> # 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.debi
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:libpdf-builder-perl
> # 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.de
Package: snort
Version: 2.9.15.1-5
Severity: critical
Tags: security upstream
Justification: root security hole
X-Debbugs-Cc: sec-advis...@ait.ac.at
Dear Maintainer,
The path of the logdirectory of snort can be manipulated by user
Snort in Debian Bullseye:
# ls -ld /var/log/snort/
drwxr-s--- 3
Processing commands for cont...@bugs.debian.org:
> severity 981680 important
Bug #981680 [src:golang-github-canonical-go-dqlite]
golang-github-canonical-go-dqlite FTBFS: test failures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assi
Control: severtiy -1 important
On Fri, 26 Nov 2021 14:43:09 +0200 Adrian Bunk wrote:
> Control: reopen -1
>
> On Fri, Nov 26, 2021 at 12:21:09PM +, Debian Bug Tracking System wrote:
> >...
> > golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium
> >...
> >* Add patches
Control: tags -1 patch
On 2022-04-02 Adrian Bunk wrote:
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1
> Severity: serious
> Forwarded: https://github.com/FreeRADIUS/freeradius-server/issues/4441
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1+b1
> Depends: freeradius (= 3.0.25+df
Processing control commands:
> tags -1 patch
Bug #1008832 [freeradius-python3] freeradius-python3: Module not linked with
libpython when built with Python 3.10
Added tag(s) patch.
--
1008832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008832
Debian Bug Tracking System
Contact ow...@bugs
Processing control commands:
> tags 965480 + patch
Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) patch.
> tags 965480 + pending
Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) pending.
--
965480
Control: tags 965480 + patch
Control: tags 965480 + pending
Dear maintainer,
I've prepared an NMU for d52 (versioned as 3.4.1-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u d52-3.4.1/debian/changelog d52-3.4.1/debian/changelog
--- d5
> On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev
> said:
> If you run sudo without the "set_home" option, thus making it preserve
> the HOME environment variable, rpm run as root with HOME set to
> /home/something will indeed do the wrong thing.
I have no set_home entry
Processing control commands:
> notforwarded -1
Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS:
patching fails
Unset Bug forwarded-to-address
> tags -1 - pending
Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS:
patching fails
Removed tag(s) pendi
1 - 100 of 111 matches
Mail list logo
