Hi Daniel,
On Tue, May 23, 2023 at 06:29:43PM -0400, Daniel Kahn Gillmor wrote:
> In https://bugs.debian.org/1034558, Salvatore Bonaccorso wrote:
>
> > Source: rnp
> > Version: 0.16.2-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > X-Debbugs-Cc:
Processing commands for cont...@bugs.debian.org:
> # fix subject
> retitle 1034558 rnp: CVE-2023-29479 CVE-2023-29480
Bug #1034558 [src:rnp] rnp: CVE-2023-29479 VE-2023-29480
Changed Bug title to 'rnp: CVE-2023-29479 CVE-2023-29480' from 'rnp:
CVE-2023-29479 VE-2023-29480'.
> thanks
Stopping
Your message dated Wed, 24 May 2023 05:19:17 +
with message-id
and subject line Bug#1036639: fixed in openstructure 2.3.1-9
has caused the Debian Bug report #1036639,
regarding libost-base2.3: please add Breaks: libost-base2.2 for smoother
upgrades from bullseye
to be marked as done.
This
Hi,
On Tue, May 23, 2023 at 7:33 PM Samuel Henrique wrote:
>
> > On Tue, May 23, 2023 at 10:21:35PM +0100, Samuel Henrique wrote:
> > > Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's
> > > his fix:
> > > https://salsa.debian.org/leandrocunha/reaver
> > Do you think this
In https://bugs.debian.org/1034558, Salvatore Bonaccorso wrote:
> Source: rnp
> Version: 0.16.2-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
Thanks for tracking this in the BTS, Salvatore.
I aim to
> On Tue, May 23, 2023 at 10:21:35PM +0100, Samuel Henrique wrote:
> > Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his
> > fix:
> > https://salsa.debian.org/leandrocunha/reaver
> Do you think this change will be approved for bookworm, especially at this
> point in the
On Tue, May 23, 2023 at 10:21:35PM +0100, Samuel Henrique wrote:
> Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his
> fix:
> https://salsa.debian.org/leandrocunha/reaver
Do you think this change will be approved for bookworm, especially at this
point in the freeze?
Hi Samuel,
On Tue, May 23, 2023 at 6:22 PM Samuel Henrique wrote:
>
> Control: tags -1 patch fixed-upstream
>
> Hello Bartosz,
>
> We are planning to perform an NMU, changing the package's maintership
> to the Security Tools team (while keeping you as an Uploader), fixing
> this RC bug and
Processing commands for cont...@bugs.debian.org:
> tags 1036591 - fixed
Bug #1036591 [reaver] reaver: segmentation fault
Removed tag(s) fixed.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591
Debian
Processing commands for cont...@bugs.debian.org:
> tags 1036591 patch fixed-upstream
Bug #1036591 [reaver] reaver: segmentation fault
Ignoring request to alter tags of bug #1036591 to the same tags previously set
> --
Stopping processing here.
Please contact me if you need assistance.
--
Control: tags -1 patch fixed-upstream
Hello Bartosz,
We are planning to perform an NMU, changing the package's maintership
to the Security Tools team (while keeping you as an Uploader), fixing
this RC bug and filling an unblock request so we can ship this package
for bookworm.
Please let me
Processing control commands:
> tags -1 patch fixed-upstream
Bug #1036591 [reaver] reaver: segmentation fault
Added tag(s) patch and fixed-upstream.
--
1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> affects 1031346 + gr-dab-dev
Bug #1031346 [gr-dab] gr-dab not installable due to dependency on outdated
gnuradio 3.8 (current is 3.10)
Added
Hi,
On Tue, May 23, 2023 at 5:27 PM Andrey Rakhmatullin wrote:
>
> On Tue, May 23, 2023 at 04:38:26PM -0300, Leandro Cunha wrote:
> > Control: tags +1 fixed
> Please don't tag this "fixed".
The problem itself has been fixed, it's just pending upload.
> > However, the package is at risk with an
On Tue, May 23, 2023 at 04:38:26PM -0300, Leandro Cunha wrote:
> Control: tags +1 fixed
Please don't tag this "fixed".
> However, the package is at risk with an NMU of see link for more
> information.[1]
>
> [1] https://wiki.debian.org/PackageSalvaging
Not sure what do you mean and how is that
Processing commands for cont...@bugs.debian.org:
> tags 1036646 fixed-upstream
Bug #1036646 [rspamd] libhyperscan5: prevents rspamd from starting
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1036646:
Processing commands for cont...@bugs.debian.org:
> reassign 1036646 rspamd
Bug #1036646 [libhyperscan5] libhyperscan5: prevents rspamd from starting
Bug reassigned from package 'libhyperscan5' to 'rspamd'.
No longer marked as found in versions hyperscan/5.4.2-1.
Ignoring request to alter fixed
I bumped the bug severity to prevent the automatic migration to Bookworm, but
feel free to lower it if you think it is not warranted.
OpenPGP_signature
Description: OpenPGP digital signature
It looks like an update of rspamd should fix this:
https://github.com/rspamd/rspamd/issues/4409
I am reassigning this bug report to rspamd since it seems that a fix is
available from their upstream.
OpenPGP_signature
Description: OpenPGP digital signature
Processing commands for cont...@bugs.debian.org:
> tag #1036591 fixed
Bug #1036591 [reaver] reaver: segmentation fault
Added tag(s) fixed.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591
Processing commands for cont...@bugs.debian.org:
> severity 1036646 serious
Bug #1036646 [libhyperscan5] libhyperscan5: prevents rspamd from starting
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1036646:
Control: tags +1 fixed
Hi Andrey Rakhmatullin,
I already fixed the problem and just need to upload.
I'll have a member of the security team upload it for me. Thank you
for your confirmation.
However, the package is at risk with an NMU of see link for more information.[1]
[1]
Source: bitcoin
Version: 22.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for bitcoin.
CVE-2023-33297[0]:
| Bitcoin Core before 24.1, when debug mode is not used, allows
| attackers to cause a
Your message dated Tue, 23 May 2023 19:07:10 +
with message-id
and subject line Bug#1035428: fixed in r-cran-shiny 1.7.4+dfsg-2+deb12u1
has caused the Debian Bug report #1035428,
regarding r-cran-shiny: broken symlink:
/usr/lib/R/site-library/shiny/www/shared/ionrangeslider/css/normalize.css
Control: tags -1 - fixed
On Tue, May 23, 2023 at 03:39:24AM -0300, Leandro Cunha wrote:
>* What led up to the situation? The package has a segmentation
> fault on any command I tried to run, but I've used this package in the
> past and it was working and I think some more up-to-date
Processing control commands:
> tags -1 - fixed
Bug #1036591 [reaver] reaver: segmentation fault
Removed tag(s) fixed.
--
1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 23 May 2023 18:21:24 +
with message-id
and subject line Bug#1036576: fixed in scotch 7.0.3-2
has caused the Debian Bug report #1036576,
regarding libscotch{,par}metis-dev: broken symlinks:
/usr/lib//*metis-*/lib*metis.* -> ../scotch-*/lib*metis.*
to be marked as done.
On Tue, 2023-05-23 at 16:55 +0200, Thorsten Alteholz wrote:
> Oh my! I seem to be doing something totally stupid here with creating all
> these links in debian/rules, but back then it worked at least.
> Do you have a recommendation on how to do it better?
>
> Thorsten
>
> On 23.05.23 11:18,
Your message dated Tue, 23 May 2023 17:53:07 +
with message-id
and subject line Bug#1036257: fixed in udm 1.0.0.322-4
has caused the Debian Bug report #1036257,
regarding udm: FTBFS in testing: make[1]: *** [debian/rules:68:
override_dh_auto_build] Error 2
to be marked as done.
This means
Package: gcc-12-base
Version: 12.2.0-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
As usual, it is helpful to bump the Breaks against gnat (which is not
co-installable) for smoother upgrades from bullseye to ensure the
obsolete gnat-10 stack gets removed.
Andreas
Package: libost-base2.3
Version: 2.3.1-8
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
the openstructure library stacks from bullseye and bookworm are not
co-installable due to a transitive dependency conflict on
libboost-regex1.74.0-icu67 which is a
Quoting Bogdan Veringioiu (2023-05-23 14:59:48)
> Is there any news from the asterisk maintainers regarding this?
> what are the chances that asterisk 20 will be included in bookworm ?
No chance: It was removed during freeze which means it will not be part
of Bookworm.
Sorry, requires more man
Followup-For: Bug #1035920
Control: tag -1 patch
The attached patch seems to fix this issue.
The canonical path for udevadm in the udev package has been /bin/udevadm
since jessie.
Andreas
>From b7839503f56aee1252b268401421fb90a69d5456 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue,
Processing control commands:
> tag -1 patch
Bug #1035920 [cloud-initramfs-growroot] cloud-initramfs-growroot:
/usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment:
expects /usr/bin/udevadm
Added tag(s) patch.
--
1035920:
Your message dated Tue, 23 May 2023 13:48:45 +
with message-id
and subject line Bug#1033432: fixed in pyramid-jinja2 2.7+dfsg-1.3
has caused the Debian Bug report #1033432,
regarding pyramid-jinja2: FTBFS in testing: ImportError: cannot import name
'contextfilter' from 'jinja2'
Package: libnvidia-legacy-340xx-glcore
Version: 340.108-18
Followup-For: Bug #1031489
X-Debbugs-Cc: nolang...@gmail.com
I can confirm this is still an issue, but debian might be at fault here. I will
use wireshark as an example:
# wireshark
This will segfault with this stacktrace:
#0
Hi all,
Is there any news from the asterisk maintainers regarding this?
what are the chances that asterisk 20 will be included in bookworm ?
Thanks,
Bogdan Veringioiu
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> found 985882 0.6.91-4
Bug #985882 [wminput] wminput: broken symlink: /usr/share/wminput/plugins ->
../../lib/wminput/plugins
Marked as found in
Your message dated Tue, 23 May 2023 09:33:51 +
with message-id
and subject line Bug#1036610: fixed in node-isomorphic-fetch 3.0.0-3
has caused the Debian Bug report #1036610,
regarding node-isomorphic-fetch: broken symlink:
/usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js ->
Processing control commands:
> tag -1 pending
Bug #1036610 [node-isomorphic-fetch] node-isomorphic-fetch: broken symlink:
/usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js ->
../../javascript/fetch/fetch.js
Added tag(s) pending.
--
1036610:
Control: tag -1 pending
Hello,
Bug #1036610 in node-isomorphic-fetch 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:
Your message dated Tue, 23 May 2023 09:19:01 +
with message-id
and subject line Bug#1036609: fixed in node-jschardet 3.0.0+dfsg+~1.4.0-2
has caused the Debian Bug report #1036609,
regarding node-jschardet: missing Depends/Recommends/Suggests: node-buffer ?
to be marked as done.
This means
Package: python3-lldb-15
Version: 1:15.0.6-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m35.3s ERROR: FAIL: Broken symlinks:
Package: python3-lldb-13
Version: 1:13.0.1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m38.1s ERROR: FAIL: Broken symlinks:
Control: tags -1 patch
On Tue, May 23, 2023 at 10:46 AM Mathieu Malaterre wrote:
>
> Control: retitle -1 No java compiler found. Won't be able to build java viewer
>
> openjpeg2/java compilation appears to be broken:
>
> -- Could NOT find Java (missing: Java_JAVA_EXECUTABLE
>
Processing control commands:
> tags -1 patch
Bug #1036584 [libopenjpip-viewer] No java compiler found. Won't be able to
build java viewer
Added tag(s) patch.
--
1036584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: node-isomorphic-fetch
Version: 3.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.8s ERROR: FAIL: Broken symlinks:
Control: retitle -1 No java compiler found. Won't be able to build java viewer
openjpeg2/java compilation appears to be broken:
-- Could NOT find Java (missing: Java_JAVA_EXECUTABLE
Java_JAVAC_EXECUTABLE Java_JAR_EXECUTABLE Java_JAVADOC_EXECUTABLE
Java_JAVAH_EXECUTABLE Development) (Required is
Processing control commands:
> retitle -1 No java compiler found. Won't be able to build java viewer
Bug #1036584 [libopenjpip-viewer] libopenjpip-viewer: broken symlink:
/usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar
Changed Bug title to 'No java compiler found. Won't
Your message dated Tue, 23 May 2023 08:36:37 +
with message-id
and subject line Bug#1036581: fixed in opencascade 7.6.3+dfsg1-7
has caused the Debian Bug report #1036581,
regarding occt-draw: broken symlink: /usr/bin/occt-draw -> occt-draw-7.5
to be marked as done.
This means that you claim
Package: node-jschardet
Version: 3.0.0+dfsg+~1.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.4s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/jschardet/buffer ->
Your message dated Tue, 23 May 2023 08:33:53 +
with message-id
and subject line Bug#1036582: fixed in node-shelljs 0.8.5+~cs0.8.10-2
has caused the Debian Bug report #1036582,
regarding node-shelljs: broken symlink: /usr/bin/shjs ->
../lib/nodejs/shelljs/bin/shjs
to be marked as done.
This
Your message dated Tue, 23 May 2023 08:33:44 +
with message-id
and subject line Bug#1036579: fixed in node-is-docker 3.0.0-5
has caused the Debian Bug report #1036579,
regarding node-is-docker: broken symlink: /usr/bin/is-docker ->
../lib/nodejs/is-docker/cli.js
to be marked as done.
This
Package: libinventor1
Version: 2.1.5-10+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
>From the attached log (scroll to the bottom...):
0m36.0s ERROR: FAIL: Broken
Processing control commands:
> tag -1 pending
Bug #1036579 [node-is-docker] node-is-docker: broken symlink:
/usr/bin/is-docker -> ../lib/nodejs/is-docker/cli.js
Added tag(s) pending.
--
1036579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036579
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1036579 in node-is-docker 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:
Package: xenstore-utils
Version: 4.17.0+74-g3eac216e6e-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.9s ERROR: FAIL: Broken symlinks:
/usr/bin/xenstore-control ->
Package: python3-lldb-14
Version: 1:14.0.6-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m35.0s ERROR: FAIL: Broken symlinks:
Processing control commands:
> tag -1 pending
Bug #1036581 [occt-draw] occt-draw: broken symlink: /usr/bin/occt-draw ->
occt-draw-7.5
Added tag(s) pending.
--
1036581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1036581 in opencascade 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:
Package: libscotchmetis-dev
Version: 7.0.3-1
Followup-For: Bug #1036576
Awkward. Thanks for catching it.
Package: reaver
Version: 1.6.5-1+b1
Severity: grave
Justification: package unusable
Tags: fixed
Dear Maintainer,
* What led up to the situation? The package has a segmentation
fault on any command I tried to run, but I've used this package in the
past and it was working and I think some more
62 matches
Mail list logo
