Bug#1034558: rnp: CVE-2023-29479 VE-2023-29480
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: car...@debian.org, Debian Security Team > > > > Thanks for tracking this in the BTS, Salvatore. > > I aim to have 0.16.3 (which is a targeted upstream release with a very > narrow set of changes) uploaded to unstable in the next day or two. Thanks! Note the deadline for unblock requests will be on 28th. So the unblock needs to be granted by then so we have the fixes in bookworm. Thanks for your work! Salvatore
Processed: retitle 1034558 to rnp: CVE-2023-29479 CVE-2023-29480
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 processing here. Please contact me if you need assistance. -- 1034558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036639: marked as done (libost-base2.3: please add Breaks: libost-base2.2 for smoother upgrades from bullseye)
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 means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1036639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 virtual package provided by
libboost-regex1.74.0 in bullseye only, while the bookworm version
provides libboost-regex1.74.0-icu72. This is hard for apt to figure out
correctly and on some upgrade paths apt prefers to keep the obsolete
library stack installed instead of replacng it with the new one.
Adding a Breaks to the base package which is at the top of the
dependency tree helps apt making the right choice: removing the old
library stack s.t. it can upgrade libboost-regex1.74.0.
Please consider applying the attached patch.
Andreas
>From 69fc50fdf3bdc26ed5152a7d6ec3c264e279c143 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue, 23 May 2023 18:38:19 +0200
Subject: [PATCH] libost-base2.3: add Breaks: libost-base2.2 for smoother
upgrades from bullseye
---
debian/changelog | 7 +++
debian/control | 2 ++
2 files changed, 9 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index eda78fd..e6970ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openstructure (2.3.1-9) UNRELEASED; urgency=medium
+
+ * libost-base2.3: Add Breaks: libost-base2.2 for smoother upgrades from
+bullseye. (Closes: #)
+
+ -- Andreas Beckmann Tue, 23 May 2023 18:37:03 +0200
+
openstructure (2.3.1-8) unstable; urgency=medium
* Install shlibs into multiarch locations using debian/rules.
diff --git a/debian/control b/debian/control
index f7340ea..310d73b 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,8 @@ Section: libs
Depends:
${misc:Depends},
${shlibs:Depends},
+Breaks:
+ libost-base2.2,
Description: Open-Source Computational Structural Biology Framework
OpenStructure aims to provide an open-source, modular, flexible, molecular
modelling and visualization environment. It is targeted at interested method
--
2.20.1
--- End Message ---
--- Begin Message ---
Source: openstructure
Source-Version: 2.3.1-9
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
openstructure, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrius Merkys (supplier of updated openstructure package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 May 2023 00:56:53 -0400
Source: openstructure
Architecture: source
Version: 2.3.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team
Changed-By: Andrius Merkys
Closes: 1036639
Changes:
openstructure (2.3.1-9) unstable; urgency=medium
.
* libost-base2.3: Add Breaks: libost-base2.2 for smoother upgrades from
bullseye. (Closes: #1036639)
Checksums-Sha1:
56ea064655ffee58ee35d56619d519e5a713859e 4617 openstructure_2.3.1-9.dsc
21a29136bba759745d17a40f1553d46227a9d652 84062732
openstructure_2.3.1-9.debian.tar.xz
bcb39ffaf8b2c367fced6210e4990b711172a483 14404
openstructure_2.3.1-9_source.buildinfo
Checksums-Sha256:
29da90df6746dae26bd183ffdf4c92e277eadb39fd1df84465bd8612d9a5239b 4617
openstructure_2.3.1-9.dsc
833f305194c546155c25da8f9502e36e01e64ee0c61a2c7bb0cdc5e7e1b36214 84062732
openstructure_2.3.1-9.debian.tar.xz
3f3b2b2d9cb3b1987de183b4c870fa2f5c3959f5aa84eeede4f1591900940c61 14404
openstructure_2.3.1-9_source.buildinfo
Files:
2ec27d178a4ee1c3c31ac73285650577 4617 science optional
openstructure_2.3.1-9.dsc
084250628c50ea532edca3fee43f148a 84062732 science optional
Bug#1036591: reaver: segmentation fault
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 change will be approved for bookworm, especially at this > > point in the freeze? > > I don't see any other better alternative. > I don't think it's worthy to cherry-pick a single possible fix since > the package might be broken in other ways as well. > > The correct action here is to update to 1.6.6, which has been released > years ago and is being shipped by a lot of other distros. > > To be clear, I haven't tried to reproduce the issue myself, but it > looks general enough and easy to do so, I'll do it in the next few > days, but wanted to make sure we keep moving on fixing this. > > Cheers, > > -- > Samuel Henrique There was a user who reported that the problem also occurs in Debian 11 (Bullseye). But I can't confirm because I don't use stable. Samuel, I know you use testing. Andrey Rakhmatullin, do you use stable or do you have machines with stable? See https://github.com/t6x/reaver-wps-fork-t6x/issues/365 -- Cheers, Leandro Cunha
Bug#1034558: rnp: CVE-2023-29479 VE-2023-29480
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 have 0.16.3 (which is a targeted upstream release with a very narrow set of changes) uploaded to unstable in the next day or two. --dkg signature.asc Description: PGP signature
Bug#1036591: reaver: segmentation fault
> 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? I don't see any other better alternative. I don't think it's worthy to cherry-pick a single possible fix since the package might be broken in other ways as well. The correct action here is to update to 1.6.6, which has been released years ago and is being shipped by a lot of other distros. To be clear, I haven't tried to reproduce the issue myself, but it looks general enough and easy to do so, I'll do it in the next few days, but wanted to make sure we keep moving on fixing this. Cheers, -- Samuel Henrique
Bug#1036591: reaver: segmentation fault
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?
Bug#1036591: reaver: segmentation fault
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 filling an unblock request so we can ship this package > for bookworm. I'm going to make these changes, since he is still the package maintainer. > Please let me know if you disagree, we will have to act quickly due to > the freeze. > > Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his > fix: > https://salsa.debian.org/leandrocunha/reaver Thank you, I apologize because I always confuse the tags use. Even looking in the documentation about debbugs BTS I was a little confused about this. -- Cheers, Leandro Cunha
Processed: your mail
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 Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
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. -- 1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036591: reaver: segmentation fault
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 know if you disagree, we will have to act quickly due to the freeze. Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his fix: https://salsa.debian.org/leandrocunha/reaver Cheers, -- Samuel Henrique
Processed: reaver: segmentation fault
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
Processed: user debian...@lists.debian.org, affects 1031346, affects 984331, affects 1035545
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 indication that 1031346 affects gr-dab-dev > affects 984331 + libsipxtapi-dev Bug #984331 [src:sipxtapi] sipxtapi: ftbfs with GCC-11 Added indication that 984331 affects libsipxtapi-dev > affects 1035545 + src:vdr-plugin-live Bug #1035545 [src:tntnet] tntnet: FTBFS with cxxtools 3: fatal error: cxxtools/atomicity.h: No such file or directory Added indication that 1035545 affects src:vdr-plugin-live > thanks Stopping processing here. Please contact me if you need assistance. -- 1031346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031346 1035545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035545 984331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036591: reaver: segmentation fault
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 NMU of see link for more > > information.[1] > > > > [1] https://wiki.debian.org/PackageSalvaging > Not sure what do you mean and how is that related to this bug, sorry. Because of this here: The last upload was an NMU and there was no maintainer upload within one year. But due to the condition of the package, I believe it is really heading towards salvaging. -- Cheers, Leandro Cunha
Bug#1036591: reaver: segmentation fault
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 related to this bug, sorry.
Processed: your mail
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
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 versions of bug #1036646 to the same values previously set > forwarded 1036646 https://github.com/rspamd/rspamd/issues/4409 Bug #1036646 [rspamd] libhyperscan5: prevents rspamd from starting Set Bug forwarded-to-address to 'https://github.com/rspamd/rspamd/issues/4409'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1036646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036646: libhyperscan5: prevents rspamd from starting
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
Bug#1036646: libhyperscan5: prevents rspamd from starting
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
Processed: your mail
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 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036591: reaver: segmentation fault
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] https://wiki.debian.org/PackageSalvaging -- Cheers, Leandro Cunha
Bug#1036647: bitcoin: CVE-2023-33297
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 denial of service (CPU consumption) because | draining the inventory-to-send queue is inefficient, as exploited in | the wild in May 2023. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-33297 https://www.cve.org/CVERecord?id=CVE-2023-33297 [1] https://github.com/bitcoin/bitcoin/issues/27586 [2] https://github.com/bitcoin/bitcoin/issues/27623 [3] https://github.com/bitcoin/bitcoin/pull/27610 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1035428: marked as done (r-cran-shiny: broken symlink: /usr/lib/R/site-library/shiny/www/shared/ionrangeslider/css/normalize.css -> ../../../../../../../nodejs/normalize.css/normalize.css)
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 -> ../../../../../../../nodejs/normalize.css/normalize.css to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-cran-shiny Version: 1.7.4+dfsg-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. 2m10.5s ERROR: FAIL: Broken symlinks: /usr/lib/R/site-library/shiny/www/shared/ionrangeslider/css/normalize.css -> ../../../../../../../nodejs/normalize.css/normalize.css (r-cran-shiny) The symlink targets the file in /usr/lib while it actually resides in /usr/share (since node-normalize.css 8.0.1-5). Since all (most?) of your .js, .css, ... dependencies are linked to /usr/share/javascript, I'd recommend doing the same for normalize.css, i.e. point your symlink to /usr/share/javascript/normalize.css/normalize.css which is a symlink provided by all versions of node-normalize.css, so you don't need a versioned dependency on that (or the virtual libjs-normalize.css package you depend on). cheers, Andreas --- End Message --- --- Begin Message --- Source: r-cran-shiny Source-Version: 1.7.4+dfsg-2+deb12u1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-shiny, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-shiny package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 May 2023 07:56:25 +0200 Source: r-cran-shiny Architecture: source Version: 1.7.4+dfsg-2+deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1035428 Changes: r-cran-shiny (1.7.4+dfsg-2+deb12u1) bookworm; urgency=medium . * Upload to testing-proposed-updates "bookworm" due to the fact that there was an accidental upload of a new version of r-base to unstable * Fix link for normalize.css Closes: #1035428 Checksums-Sha1: 14ad0f8759b482b600ee5b23885e78a4b9b57344 2781 r-cran-shiny_1.7.4+dfsg-2+deb12u1.dsc 189e6d52a78258a03c3c8d3bba23d2dfa9a6ba61 140092 r-cran-shiny_1.7.4+dfsg-2+deb12u1.debian.tar.xz 12a035d6ccdae947ad6b6fc2ee87ff886a48925e 4 r-cran-shiny_1.7.4+dfsg-2+deb12u1_source.buildinfo Checksums-Sha256: 885ad84430bac509de90da95adbcb74d5def48236411b909d2db701bd352d5ba 2781 r-cran-shiny_1.7.4+dfsg-2+deb12u1.dsc 6012589287e0dae2590c0efc8b1724053cec3e780b5e7654132f69e464d5b82b 140092 r-cran-shiny_1.7.4+dfsg-2+deb12u1.debian.tar.xz b712df698d2485b85f79791f284344efe2b65a74f81779e8f2d7bfef87c82010 4 r-cran-shiny_1.7.4+dfsg-2+deb12u1_source.buildinfo Files: 471aeb995369cac8cfd7a7090209d3ff 2781 gnu-r optional r-cran-shiny_1.7.4+dfsg-2+deb12u1.dsc c29c81027bc22ad613cf223bb9312a03 140092 gnu-r optional r-cran-shiny_1.7.4+dfsg-2+deb12u1.debian.tar.xz 86f4d5816013fc2b74d305ab30d846da 4 gnu-r optional r-cran-shiny_1.7.4+dfsg-2+deb12u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmRs+rkOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtHZzA/+OeLV4/aDQ4eQaATyFGTBRokExDJBlWjMnwZB xeDZoSbcF1PfJI/GG7dhxcexvLut52x89g42czJwKYSM5IgaaNs4KaSnPysIYZCt ngGpCDNrELScZ8kma+/mQXDDADLn6b6jZiC6By8n5RX0mDW9JGe+2ZiaZwJWPcun fMP9wXUDMR86u2uYCA4Bg7Sy+yJFY2NUO6/SXiVuVo+RTD0BK3z3kVu1XTAY+G5Q 0loqxDBH8KIdvWB8g4YKIJJsgIoqocm3U1u0xjtEPpFEaiitKOdtNBJINlhebr1f mNiMl9i/Wyt6lY9TiAGDqz0TMmgLsWqTrRKzN2fTkB6kkRfQOi3A/CLt7pvi/txj 2eRBBWYHkfWTNnFkjqWXovw15+NWOaUvCKFFir09RsIkDfvs3F9BYaUso71ZN5aL debkXeYhHB36el+0e6rcL1SlAUgAYAzjiO1G8M6cMxNttIXLGjwd9Rlav422Sexr lFB8G5CH2wROHjqEGPX351qv8h8otp4+wa66sDD0+dWTQ7lx8m39WhkstOj2qulK
Bug#1036591: reaver: segmentation fault
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 dependency is > causing this. I can confirm this, running `reaver -i wlan0 -b 00:90:4C:C1:AC:21 -vv` (the BSSID is from the -h example). Program received signal SIGSEGV, Segmentation fault. 0x77df1d19 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x77df1d19 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x77e85d3a in pcap_activate_linux (handle=0x55636e00) at ./pcap-linux.c:1016 #2 0x77e8d64d in pcap_activate (p=p@entry=0x55636e00) at ./pcap.c:2716 #3 0x55599e44 in capture_init (capture_source=) at init.c:148 #4 0x5559a93d in crack () at cracker.c:59 #5 0x5559e969 in reaver_main (argc=6, argv=) at wpscrack.c:106 #6 0x77cc318a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x77cc3245 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x555987fa in _start ()
Processed: Re: Bug#1036591: reaver: segmentation fault
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
Bug#1036576: marked as done (libscotch{,par}metis-dev: broken symlinks: /usr/lib//*metis-*/lib*metis.* -> ../scotch-*/lib*metis.*)
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.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1036576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libscotchmetis-dev,libscotchparmetis-dev
Version: 7.0.3-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:
0m34.0s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/metis-int32/libmetis.a ->
../scotch-int32/libscotchmetis.a (libscotchmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/metis-int32/libmetis.so ->
../scotch-int32/libscotchmetis.so (libscotchmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/metis-int64/libmetis.a ->
../scotch-int64/libscotchmetis.a (libscotchmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/metis-int64/libmetis.so ->
../scotch-int64/libscotchmetis.so (libscotchmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/metis-long/libmetis.a ->
../scotch-long/libscotchmetis.a (libscotchmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/metis-long/libmetis.so ->
../scotch-long/libscotchmetis.so (libscotchmetis-dev:amd64)
0m33.4s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/parmetis-int32/libparmetis.a ->
../scotch-int32/libptscotchparmetis.a (libscotchparmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/parmetis-int32/libparmetis.so ->
../scotch-int32/libptscotchparmetis.so (libscotchparmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/parmetis-int64/libparmetis.a ->
../scotch-int64/libptscotchparmetis.a (libscotchparmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/parmetis-int64/libparmetis.so ->
../scotch-int64/libptscotchparmetis.so (libscotchparmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/parmetis-long/libparmetis.a ->
../scotch-long/libptscotchparmetis.a (libscotchparmetis-dev:amd64)
/usr/lib/x86_64-linux-gnu/parmetis-long/libparmetis.so ->
../scotch-long/libptscotchparmetis.so (libscotchparmetis-dev:amd64)
libscotch-dev/libptscotch-dev no longer ship static libraries (*.a)
and instead of libscotchmetis.so there are now libscotchmetisv[35].so
and instead of libptscotchparmetis.so there is now
libptscotchparmetisv3.so.
cheers,
Andreas
--- End Message ---
--- Begin Message ---
Source: scotch
Source-Version: 7.0.3-2
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
scotch, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated scotch package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 23 May 2023 17:23:49 +0200
Source: scotch
Architecture: source
Version: 7.0.3-2
Distribution: unstable
Urgency: high
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 1036576
Changes:
scotch (7.0.3-2) unstable; urgency=high
.
* Team upload.
* update libscotchmetis-dev and libscotchparmetis-dev links to point
int-specific libmetis.so at the corresponding libscotchmetisv5.so
(v5 not v3, to match libmetis), and point libparmetis.so at the
corresponding int-build of libptscotchparmetisv3.so. Likewise for
static .a libraries. Closes: #1036576.
Checksums-Sha1:
a874718a35a27c293e50dce92d5f7f32e574c2ad 2575 scotch_7.0.3-2.dsc
5659a23f646495383c51ecc92c6a194cb812911d 20988 scotch_7.0.3-2.debian.tar.xz
Checksums-Sha256:
4bdac6bb7d3a7fbe840c37ae93923b94155930747354a21a080b6250445a10fe 2575
scotch_7.0.3-2.dsc
82cf9daac482b2548c73fc92fa8cd98cfe4ea587ffcda684c598ba9eca15a700 20988
scotch_7.0.3-2.debian.tar.xz
Files:
e9d3345caac7de93d99ad9d134885397 2575 math optional scotch_7.0.3-2.dsc
f812bf7d60cae89d0e85b4a69069fca1 20988 math optional
scotch_7.0.3-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmRs+6wACgkQVz7x5L1a
Bug#1036257: Debian package udm FTBFS
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, Thorsten Alteholz wrote:
>
> > Hi,
> >
> > can you please help me with a problem with udm?
> > For whatever reason the package started to FTBFS recently -> [1]
> > The log says:
> > > /<>/uplaysound.pas(35,22) Fatal: (10022) Can't find unit
> > > LResources used by uplaysound
> >
> > but why isn't LResources available anymore? Do you have any idea what went
> > wrong here? Could this be related to your latest uploads of lazarus?
> >
> > Best regards
> > Thorsten
> >
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036257
I've managed to compile this using the following patch and rules file.
--
Cheers,
Abou Al Montacir
Description: Fixd compilation with Lazarus 2.2.6
This patch fixes compilation with Lazarus 2.2.6 by adding required packages
that are used by the softare.
Author: Abou Al Montacir
---
Bug-Debian: https://bugs.debian.org/1036257
Forwarded: no
Last-Update: 2023-05-23
--- udm-1.0.0.322.orig/playwavepackage.lpk
+++ udm-1.0.0.322/playwavepackage.lpk
@@ -1,6 +1,6 @@
-
+
@@ -56,15 +56,22 @@
+
-
+
-
+
+
+
+
+
+
+
--- udm-1.0.0.322.orig/udm.lpi
+++ udm-1.0.0.322/udm.lpi
@@ -17,6 +17,9 @@
+
+
+
@@ -81,6 +84,9 @@
+
+
+
@@ -131,7 +137,7 @@
-
+
@@ -182,12 +188,12 @@
-
+
@@ -240,7 +246,7 @@
-
+
@@ -624,127 +630,158 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
--- udm-1.0.0.322.orig/udm.lpr
+++ udm-1.0.0.322/udm.lpr
@@ -21,7 +21,7 @@ startupoptions;
{$R *.res}
begin
- Application.Scaled:=True;
+ Application.Scaled := True;
{$IFDEF DEBUG}
// Assuming your build mode sets -dDEBUG in Project Options/Other when defining -gh
// This avoids interference when running a production/default build without -gh
--- udm-1.0.0.322.orig/udmc.lpi
+++ udm-1.0.0.322/udmc.lpi
@@ -1,13 +1,13 @@
-
+
+
-
@@ -19,9 +19,11 @@
-
-
+
+
+
+
@@ -30,15 +32,35 @@
-
+
+
+
+
+
+
+
+
+
-
+
-
+
+
Bug#1036257: marked as done (udm: FTBFS in testing: make[1]: *** [debian/rules:68: override_dh_auto_build] Error 2)
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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: udm Version: 1.0.0.322-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230517 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # this looks awfull and I hope there is a better solution > # but at the moment at least the package builds > mkdir /<>/tmphome > echo "#INCLUDE /etc/fpc.cfg" > /<>/tmphome/.fpc.cfg > echo "-dLCLGTK2" >> /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/components/lazutils/lib/x86_64-linux" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/packager/units/x86_64-linux" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/lcl/units/x86_64-linux" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/components/ideintf/units/x86_64-linux/gtk2/" > >> /<>/tmphome/.fpc.cfg > echo > "-Fu/usr/lib/lazarus/2.2.4/components/lazcontrols/lib/x86_64-linux/gtk2/" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/components/synedit/units/x86_64-linux/gtk2/" > >> /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/components/tachart/lib/x86_64-linux/gtk2/" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/components/printers/lib/x86_64-linux/gtk2/" > >> /<>/tmphome/.fpc.cfg > echo > "-Fu/usr/lib/lazarus/2.2.4/components/cairocanvas/lib/x86_64-linux/gtk2/" >> > /<>/tmphome/.fpc.cfg > echo "-Fu/usr/lib/lazarus/2.2.4/lcl/units/x86_64-linux/gtk2/" >> > /<>/tmphome/.fpc.cfg > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcalc4.inc > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttconfig.inc > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttraster_sweep.inc > ln -s /usr/lib/lazarus/2.2.4/components/opengl/openglcontext.res > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/ideoptionsintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/baseideintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/macrointf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/macrodefintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/compoptsintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/projectintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/newitemintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/projpackintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/buildstrconsts.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/ideexterntoolintf.pas > ln -s /usr/lib/lazarus/2.2.4/components/buildintf/lazmsgworker.pas > ln -s /usr/lib/lazarus/2.2.4/components/opengl/openglcontext.pas > ln -s /usr/lib/lazarus/2.2.4/components/opengl/glgtkglxcontext.pas > ln -s /usr/lib/lazarus/2.2.4/components/opengl/lazopenglcontext.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/easylazfreetype.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/lazfreetype.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/tttypes.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/tterror.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcalc4.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcalc.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttmemory.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/tttables.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcache.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttfile.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcmap.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttobjs.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttload.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttinterp.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttgload.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttkern.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttraster.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttprofile.pas > ln -s /usr/lib/lazarus/2.2.4/components/freetype/lazfreetypefontcollection.pas > lazbuild --widgetset=gtk2 -B udm.lpi > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> >
Bug#1036641: gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye
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
Bug#1036639: libost-base2.3: please add Breaks: libost-base2.2 for smoother upgrades from bullseye
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 virtual package provided by
libboost-regex1.74.0 in bullseye only, while the bookworm version
provides libboost-regex1.74.0-icu72. This is hard for apt to figure out
correctly and on some upgrade paths apt prefers to keep the obsolete
library stack installed instead of replacng it with the new one.
Adding a Breaks to the base package which is at the top of the
dependency tree helps apt making the right choice: removing the old
library stack s.t. it can upgrade libboost-regex1.74.0.
Please consider applying the attached patch.
Andreas
>From 69fc50fdf3bdc26ed5152a7d6ec3c264e279c143 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue, 23 May 2023 18:38:19 +0200
Subject: [PATCH] libost-base2.3: add Breaks: libost-base2.2 for smoother
upgrades from bullseye
---
debian/changelog | 7 +++
debian/control | 2 ++
2 files changed, 9 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index eda78fd..e6970ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openstructure (2.3.1-9) UNRELEASED; urgency=medium
+
+ * libost-base2.3: Add Breaks: libost-base2.2 for smoother upgrades from
+bullseye. (Closes: #)
+
+ -- Andreas Beckmann Tue, 23 May 2023 18:37:03 +0200
+
openstructure (2.3.1-8) unstable; urgency=medium
* Install shlibs into multiarch locations using debian/rules.
diff --git a/debian/control b/debian/control
index f7340ea..310d73b 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,8 @@ Section: libs
Depends:
${misc:Depends},
${shlibs:Depends},
+Breaks:
+ libost-base2.2,
Description: Open-Source Computational Structural Biology Framework
OpenStructure aims to provide an open-source, modular, flexible, molecular
modelling and visualization environment. It is targeted at interested method
--
2.20.1
Bug#1031046: asterisk gone from bookworm ?
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 power to maintain than I could muster alone :-( - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1035920: cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm
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, 23 May 2023 00:56:50 +0200 Subject: [PATCH] fix copy_exec /bin/udevadm /sbin --- debian/changelog| 6 ++ growroot/hooks/growroot | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index c1720fa..d4e2fd8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +cloud-initramfs-tools (0.18.debian13) UNRELEASED; urgency=medium + + * Fix copy_exec /bin/udevadm /sbin (Closes: #1035920). + + -- Andreas Beckmann Tue, 23 May 2023 00:54:39 +0200 + cloud-initramfs-tools (0.18.debian12) unstable; urgency=medium [ Martin Pitt ] diff --git a/growroot/hooks/growroot b/growroot/hooks/growroot index 5d06aa8..a8ee1ab 100644 --- a/growroot/hooks/growroot +++ b/growroot/hooks/growroot @@ -11,7 +11,7 @@ esac ## copy_exec /sbin/sfdisk /sbin copy_exec /usr/bin/growpart /sbin -copy_exec /usr/bin/udevadm /sbin +copy_exec /bin/udevadm /sbin copy_exec /usr/bin/flock /bin # vi: ts=4 noexpandtab -- 2.20.1
Processed: Re: cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033432: marked as done (pyramid-jinja2: FTBFS in testing: ImportError: cannot import name 'contextfilter' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/__init__.py))
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' (/usr/lib/python3/dist-packages/jinja2/__init__.py) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyramid-jinja2 Version: 2.7+dfsg-1.2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230323 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_update_autotools_config -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > dh_auto_configure: warning: Compatibility levels before 10 are deprecated > (level 9 in use) > I: pybuild base:240: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > copying pyramid_jinja2/i18n.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > copying pyramid_jinja2/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > copying pyramid_jinja2/compat.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > copying pyramid_jinja2/settings.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > copying pyramid_jinja2/filters.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2 > creating > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/scaffolds > copying pyramid_jinja2/scaffolds/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/scaffolds > creating > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo > copying pyramid_jinja2/demo/tests.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo > copying pyramid_jinja2/demo/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo > creating > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/base.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/extensions.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/test_filters.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/test_settings.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/test_ext.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > copying pyramid_jinja2/tests/test_it.py -> > /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests > running egg_info > writing pyramid_jinja2.egg-info/PKG-INFO > writing dependency_links to pyramid_jinja2.egg-info/dependency_links.txt > writing entry points to pyramid_jinja2.egg-info/entry_points.txt > writing requirements to pyramid_jinja2.egg-info/requires.txt > writing top-level names to pyramid_jinja2.egg-info/top_level.txt > reading manifest file 'pyramid_jinja2.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '*.pyc' found under directory > 'docs' > warning: no previously-included files matching '*.pyc' found under directory > 'pyramid_jinja2' > adding license file 'LICENSE.txt' > writing manifest file 'pyramid_jinja2.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: > SetuptoolsDeprecationWarning: Installing 'pyramid_jinja2.demo.locale' as > data is deprecated, please list it in `packages`. > !! > > > > # Package would be ignored # > > Python recognizes
Bug#1031489: NVIDIA 340.108 driver gives Segmentation fault at launch all Qt software
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 0x in ?? () No symbol table info available. #1 0x7f95fda01252 in ?? () from /lib/x86_64-linux-gnu/libnvidia- tls.so.340.108 No symbol table info available. #2 0x7f95ffacb81d in QThread::start(QThread::Priority) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 0x7f95ffacb81d is a call to pthread_create What likely happens is that the library needs to be loaded first LD_PRELOAD=libpthread.so.0 wireshark -> voila, no crash anymore What needs to happen is that libnvidia-tls.so.340.108 should depend on libpthread.so.0. I fixed up my version with the patchelf tool: patchelf --add-needed libpthread.so.0 /lib/x86_64-linux-gnu/libnvidia- tls.so.340.108 This took care of the issue for me. This should be feasible to fix in debian. -- Package-specific info: uname -a: Linux lano-work 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT218 [NVS 300] [10de:0862] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 May 23 14:58 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 May 23 14:58 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 May 23 14:58 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 May 23 14:58 pci-:01:00.0-card -> ../card0 video:x:44:lano Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia_drv.so is /usr/lib/nvidia/nvidia_drv.so /usr/lib/nvidia/legacy-340xx - priority 340 slave nvidia--20-nvidia-legacy-340xx.conf: /etc/nvidia/legacy-340xx/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1 slave nvidia--libglx.so: /usr/lib/nvidia/legacy-340xx/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf: /usr/lib/nvidia/legacy-340xx/monitoring.conf slave nvidia--nvidia-blacklists-nouveau.conf: /etc/nvidia/nvidia-legacy-340xx-340.108/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh: /usr/lib/nvidia/legacy-340xx/nvidia-bug-report.sh slave nvidia--nvidia-debugdump: /usr/lib/nvidia/legacy-340xx/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf: /etc/nvidia/legacy-340xx/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf:
Bug#1031046: asterisk gone from bookworm ?
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
Processed: user debian...@lists.debian.org, found 985882 in 0.6.91-4, found 990653 in 202209.3-1 ...
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 versions cwiid/0.6.91-4.
> found 990653 202209.3-1
Bug #990653 [rdkit-doc] rdkit-doc: broken symlinks:
/usr/share/doc/rdkit/html/_static/{jquery,underscore}.js
Marked as found in versions rdkit/202209.3-1.
> found 989331 1.14.5-3
Bug #989331 [librepo-doc] librepo-doc: broken symlink:
/usr/share/doc/librepo-doc/html/jquery.js ->
../../../javascript/jquery/jquery.js
Marked as found in versions librepo/1.14.5-3.
> found 988770 0.69.0-2
Bug #988770 [python3-hawkey-doc] python3-hawkey-doc: broken symlinks:
/usr/share/doc/python3-hawkey-doc/html/_static/{jquery,underscore}.js
Marked as found in versions libdnf/0.69.0-2.
> found 990657 4.14.0-3
Bug #990657 [python3-dnf-doc] python3-dnf-doc: broken symlinks:
/usr/share/doc/python3-dnf-doc/html/_static/{jquery,underscore}.js
Marked as found in versions dnf/4.14.0-3.
> found 988773 22.2.0-0.1
Bug #988773 [python-treq-doc] python-treq-doc: broken symlinks:
/usr/share/doc/python-treq-doc/html/_static/*.js
Marked as found in versions python-treq/22.2.0-0.1.
> found 988855 0.10.1-3
Bug #988855 [python-sphinx-gallery-doc] python-sphinx-gallery-doc: broken
symlinks under /usr/share/doc/python-sphinx-gallery-doc/html/_static/
Marked as found in versions sphinx-gallery/0.10.1-3.
> found 858485 1.10.6-3
Bug #858485 [python-pg8000-doc] python-pg8000-doc: broken symlink:
/usr/share/doc/python-pg8000-doc/changelog -> html/_sources/release_notes.rst
Marked as found in versions pg8000/1.10.6-3.
> found 972611 1.46.0-1
Bug #972611 [python-mutagen-doc] /usr/share/doc/python-mutagen/rst is a broken
symlink
Marked as found in versions mutagen/1.46.0-1.
> unarchive 988675
Bug #988675 {Done: Adrian Bunk } [python-distributed-doc]
python-distributed-doc: broken symlink:
/usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js ->
/sphinx_rtd_theme/static/js/html5shiv.min.js
Unarchived Bug 988675
> found 988675 2022.12.1+ds.1-3
Bug #988675 {Done: Adrian Bunk } [python-distributed-doc]
python-distributed-doc: broken symlink:
/usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js ->
/sphinx_rtd_theme/static/js/html5shiv.min.js
Marked as found in versions dask.distributed/2022.12.1+ds.1-3 and reopened.
> found 988766 5.1.0-2
Bug #988766 [python-apptools-doc] python-apptools-doc: broken symlink:
/usr/share/doc/python-apptools/html/_sources/README.rst.txt -> ../../README.rst
Marked as found in versions python-apptools/5.1.0-2.
> found 924202 1.7.7-1
Bug #924202 [pmacct] pmacct: broken symlink: /usr/share/pmacct/examples ->
../../lib/pmacct/examples
Marked as found in versions pmacct/1.7.7-1.
> found 988859 0.3.1+dfsg+~0.3.29-2
Bug #988859 [node-expect.js] node-expect.js: broken symlink:
/usr/share/nodejs/expect.js/support/mocha.js -> ../../mocha/mocha.js
Marked as found in versions node-expect.js/0.3.1+dfsg+~0.3.29-2.
> found 988653 2.0.5+~cs4.4.3-2
Bug #988653 [node-bunyan] node-bunyan: broken symlink:
/usr/share/doc/node-exeunt -> ../node-bunyan
Marked as found in versions node-bunyan/2.0.5+~cs4.4.3-2.
> unarchive 858958
Bug #858958 {Done: Bo YU } [morse-simulator-doc]
morse-simulator-doc: broken symlink:
/usr/share/doc/morse/html/_static/underscore.js ->
../../../../javascript/jquery/underscore.js
Unarchived Bug 858958
> reopen 858958
Bug #858958 {Done: Bo YU } [morse-simulator-doc]
morse-simulator-doc: broken symlink:
/usr/share/doc/morse/html/_static/underscore.js ->
../../../../javascript/jquery/underscore.js
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions morse-simulator/1.4-7.
> found 858958 1.4-8
Bug #858958 [morse-simulator-doc] morse-simulator-doc: broken symlink:
/usr/share/doc/morse/html/_static/underscore.js ->
../../../../javascript/jquery/underscore.js
Marked as found in versions morse-simulator/1.4-8.
> found 988867 4.5.0-1
Bug #988867 [libtyxml-ocaml-doc] libtyxml-ocaml-doc: broken symlink:
/usr/share/doc/libtyxml-ocaml-doc/api -> ../libtyxml-ocaml-dev/api
Marked as found in versions tyxml/4.5.0-1.
> found 989331 1.14.5-3
Bug #989331 [librepo-doc] librepo-doc: broken symlink:
/usr/share/doc/librepo-doc/html/jquery.js ->
../../../javascript/jquery/jquery.js
Ignoring request to alter found versions of bug #989331 to the same values
previously set
> found 988845 3.0.0-1
Bug #988845 [libcalendar-ocaml-doc] libcalendar-ocaml-doc: broken symlink:
/usr/share/doc/libcalendar-ocaml-doc/html/api -> ../doc
Marked as found in versions calendar/3.0.0-1.
> found 988741 3.3.1.1+dfsg-1
Bug #988741 [glances-doc] glances-doc: broken symlinks:
Bug#1036610: marked as done (node-isomorphic-fetch: broken symlink: /usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js -> ../../javascript/fetch/fetch.js)
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 -> ../../javascript/fetch/fetch.js to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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: /usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js -> ../../javascript/fetch/fetch.js (node-isomorphic-fetch) Since the dependency on libjs-fetch was replaced with node-whatwg-fetch, the symlink target should probably be updated to /usr/share/nodejs/whatwg-fetch/fetch.js, too. cheers, Andreas --- End Message --- --- Begin Message --- Source: node-isomorphic-fetch Source-Version: 3.0.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-isomorphic-fetch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-isomorphic-fetch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 May 2023 13:18:55 +0400 Source: node-isomorphic-fetch Built-For-Profiles: nocheck Architecture: source Version: 3.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1036610 Changes: node-isomorphic-fetch (3.0.0-3) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Apply multi-arch hints. + node-isomorphic-fetch: Add Multi-Arch: foreign. . [ Yadd ] * Declare compliance with policy 4.6.2 * Update fetch-npm-browserify.js link (Closes: #1036610) Checksums-Sha1: 6f151d2f5933a07391a9aa31ca22e73221870735 2157 node-isomorphic-fetch_3.0.0-3.dsc 5a742feab8bf2165b0b96976b041b3c2fd08e3a6 2792 node-isomorphic-fetch_3.0.0-3.debian.tar.xz Checksums-Sha256: 353acaf45abfb00066445414a116a5c23c53b79c3776b0541175bbf641820966 2157 node-isomorphic-fetch_3.0.0-3.dsc 9a8f767fb531c760e277011e139c9907d6833bc49103c6a1eb1296d83ec8ddfc 2792 node-isomorphic-fetch_3.0.0-3.debian.tar.xz Files: 3dacb6bad17568c44d2015bb304e1bae 2157 javascript optional node-isomorphic-fetch_3.0.0-3.dsc 72555d2d051e83052069f1789a6d4e5d 2792 javascript optional node-isomorphic-fetch_3.0.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRshZcACgkQ9tdMp8mZ 7ul7vQ/3Wr3EzhKh+YCZf1WNPmaWKcEnSY20zsQR7ChRHg5z4IyIy5d+8jhf88f/ +ixfn0h7V3IcKdkYXC5wwkv88oZYeVMbsw3VfmhA/7NaW94Xy+aeJkcZPaQ6xDi3 9sPwXBCGdCpCJNL7qMl7ZiTIZ43EuupxuMPRG2TlNmHKxMydveyl0kvA2tvE8dzz AiCSgpS1PnY4vcJ93b0LHb/RmI+kLmCzE/v1uKWzIkFPvZoJmH9nx6PE+pH2UmSu 02FQQU2Xsicu7BPYtqSoVxMklimMxsaI183bJmgPy34POrGIe1tzrgano6bgyYjg Vd6WZ7ZhflOBJAnqETMtBix5XSXG94dNrRK1vGLOLGqj8HLcxte61tgUVdJefuOS nJFBJM/MkKxgOcylvIfcO9FUX8vo/0RdTSXS2OkGSe4jPd6zBWrEFPjcXbjhzpB7 sziFcFGT2KclRhLyJ7IK3EenrarfqpEu+GPw0JGNq08zDyEqpfzeIU6NvwivWJvR QIyirfc9bJ7bCJECo+Api4JGyTMBeqpzObetzOGf1XYvOZrk2GnfcIOjuIOHzOOL shacybRu4H9EAgXFVLEkbaycEKS8qsOY+/Y2HkoPD04masJgsQPdUMJI+z+aDoPH P3ZXMxe5Vk+8StYEZgSxNDQDjr+/vut79MHp7pYPVKWLasELfQ== =3T3G -END PGP SIGNATURE End Message ---
Processed: Bug#1036610 marked as pending in node-isomorphic-fetch
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036610: marked as pending in node-isomorphic-fetch
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: https://salsa.debian.org/js-team/node-isomorphic-fetch/-/commit/a7a89da794133ec648e8d14cfe1d5e63b92d8026 Update fetch-npm-browserify.js link Closes: #1036610 (this message was generated automatically) -- Greetings https://bugs.debian.org/1036610
Bug#1036609: marked as done (node-jschardet: missing Depends/Recommends/Suggests: node-buffer ?)
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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 -> ../buffer (node-jschardet) Is node-jschardet missing some dependency/... on node-buffer? cheers, Andreas --- End Message --- --- Begin Message --- Source: node-jschardet Source-Version: 3.0.0+dfsg+~1.4.0-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-jschardet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-jschardet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 May 2023 13:03:58 +0400 Source: node-jschardet Architecture: source Version: 3.0.0+dfsg+~1.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1036609 Changes: node-jschardet (3.0.0+dfsg+~1.4.0-2) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.2 * Drop useless symlink to buffer (Closes: #1036609) Checksums-Sha1: 4d10e7212dd636fb0fe6306706e4c4c3c64a3115 2607 node-jschardet_3.0.0+dfsg+~1.4.0-2.dsc bbd6c2303bf2515f397fc39b180eec0f52399407 5736 node-jschardet_3.0.0+dfsg+~1.4.0-2.debian.tar.xz Checksums-Sha256: 95be44808a6e858dbba50d9134b612f5bdd627f79c0b519efe55a53d22035e60 2607 node-jschardet_3.0.0+dfsg+~1.4.0-2.dsc a4094bddfb04f555f2c7b4cfcb26526551c1eb9a62d1b1b9f2a1784eef38ed2e 5736 node-jschardet_3.0.0+dfsg+~1.4.0-2.debian.tar.xz Files: 2bab905c8ed1dbc0eabe67fb05bde3a7 2607 javascript optional node-jschardet_3.0.0+dfsg+~1.4.0-2.dsc b85caab9d87921049775b672194ccd74 5736 javascript optional node-jschardet_3.0.0+dfsg+~1.4.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRsgjMACgkQ9tdMp8mZ 7ukYKA//V5cLJtH0hsQbVkJeM3rUweNZEMXulh7BAswiM/M19IT3gy0VfA/8Gpem hbzE1iT+kRafNcsODz7feg8og+A833POLdw5PXbYCZaL743InaOLBDuwNlGGwhZg 3UT9j+5usTfcIIVg9iVRncWghNhynrQQVuv/nsf78/KCOQijCRqr68qbMnCNWM/8 QTJejNGA9MyVL/0MoDpYrLhashoqBTNXkzWxAT6yYdqhpLbMAXtK5UKiyjJZ3xW/ oD/g34kfZrvn5PNFbf/WrLQyVKBqB44NFCveCKsCGOcnC8ffF4qPuh0q4yEg6pno P9f3LxDIdfuBSsni4WV3tu6J5o8D8PJ+1xnTxOI3ra0tjnf/bSSB4iGwCKIzrTHy f2cEbCdY0zbNVJ4j5BgdDNAEDaNJxhtZcUAK+ax79BxWO6LK4i1HaFf4TiCX1boi Nt2DK3d2nVVZGRiMJ+/k1d1/umnk73TDdzEM/e0FiWb3H/LiMSRXviqy/hgyxeYR ZF4bieOxHJC/oag46WeTpLtrmjU+a28PdqGXOHDpk8HTv0aSTXRgY8F6h52Lad0e e3T/bNNNPxPIb+qfXNCCnCtO5kgK4aGPvYqrgLAhs+mHROkmd2rsJFJB2qFQEkQk 053GJnq3VBdiBnH8DRuzUOE+t1QT9Oj6dVy/zKXIe1M0jg2GKsA= =iIQT -END PGP SIGNATURE End Message ---
Bug#1036614: python3-lldb-15: broken symlinks: /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so, /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.so.1
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: /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so -> ../../../../../lib/liblldb.so (python3-lldb-15) /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/lldb-argdumper -> ../../../../../bin/lldb-argdumper (python3-lldb-15) /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.0.6.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-15.0.6.so.1 (python3-lldb-15) /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-15.0.6.so.1 (python3-lldb-15) lldb-argdumper has one level of '..' too much, otherwise it could be found. The correct target for libLLVM-15.0.6.so.1 would be /usr/lib//libLLVM-15.so.1 and _lldb.cpython-311-.so should be linked to /usr/lib/llvm-15/lib/python3/dist-packages/lldb/_lldb.so or /usr/lib//liblldb-15.so.1 cheers, Andreas
Bug#1036611: python3-lldb-13: broken symlinks: /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13*.so.1 -> ../../../../..//libLLVM-13.0.1.so.1
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: /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.0.1.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13) /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13) The correct target would be /usr/lib//libLLVM-13.so.1 cheers, Andreas
Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar
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 > Java_JAVAC_EXECUTABLE Java_JAR_EXECUTABLE Java_JAVADOC_EXECUTABLE > Java_JAVAH_EXECUTABLE Development) (Required is at least version > "1.8") > CMake Warning at src/bin/jpip/CMakeLists.txt:160 (message): > No java compiler found. Won't be able to build java viewer default-jdk is defined in B-D-I which looks wrong IMHO: * https://salsa.debian.org/debian-phototools-team/openjpeg2/-/blob/master/debian/control#L16 [...] Build-Depends-Indep: default-jdk, [...]
Processed: Re: Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar
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 problems
Bug#1036610: node-isomorphic-fetch: broken symlink: /usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js -> ../../javascript/fetch/fetch.js
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: /usr/share/nodejs/isomorphic-fetch/fetch-npm-browserify.js -> ../../javascript/fetch/fetch.js (node-isomorphic-fetch) Since the dependency on libjs-fetch was replaced with node-whatwg-fetch, the symlink target should probably be updated to /usr/share/nodejs/whatwg-fetch/fetch.js, too. cheers, Andreas
Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar
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 at least version "1.8") CMake Warning at src/bin/jpip/CMakeLists.txt:160 (message): No java compiler found. Won't be able to build java viewer ref: * https://buildd.debian.org/status/fetch.php?pkg=openjpeg2=amd64=2.5.0-1%2Bb1=1673540495=0
Processed: Re: Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar
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 be able to build java viewer' from 'libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar'. -- 1036584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036581: marked as done (occt-draw: broken symlink: /usr/bin/occt-draw -> occt-draw-7.5)
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 that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: occt-draw Version: 7.6.3+dfsg1-6 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: 0m27.2s ERROR: WARN: Broken symlinks: /usr/bin/occt-draw -> occt-draw-7.5 (occt-draw) Looks like a hardcoded obsolete version in the target. cheers, Andreas --- End Message --- --- Begin Message --- Source: opencascade Source-Version: 7.6.3+dfsg1-7 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of opencascade, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated opencascade package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 May 2023 09:45:56 +0200 Source: opencascade Architecture: source Version: 7.6.3+dfsg1-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Tobias Frost Closes: 1036581 Changes: opencascade (7.6.3+dfsg1-7) unstable; urgency=medium . * Update broken symlink /usr/bin/occt-draw to new version occt-draw-7.6" (Closes: #1036581) Checksums-Sha1: da506befbc8b8802a4fb0bc46f57a7838cd5c519 3484 opencascade_7.6.3+dfsg1-7.dsc 4ed9141c66a4abd260521a7ad23d1672a6a7cf72 70624 opencascade_7.6.3+dfsg1-7.debian.tar.xz 49b8299387cb01ee9299858a01746a2000c908a2 19465 opencascade_7.6.3+dfsg1-7_amd64.buildinfo Checksums-Sha256: 8c9bff13462bad40fdc809efa28777c795ddd45950cc574778e1285ea1baaea9 3484 opencascade_7.6.3+dfsg1-7.dsc 466dfe605d68d83c6c43aaf816c68bc462857b6d5f82be592efa8c3b8905a496 70624 opencascade_7.6.3+dfsg1-7.debian.tar.xz f5b4da605e1732b71922b8d90ecd1ba2dd24b6bf911327d22a7bb30238bd826a 19465 opencascade_7.6.3+dfsg1-7_amd64.buildinfo Files: 226971eb8fd59622e9e886de93fafc73 3484 science optional opencascade_7.6.3+dfsg1-7.dsc cc5bd87ef55427d0c6b1b8886b8b76d2 70624 science optional opencascade_7.6.3+dfsg1-7.debian.tar.xz 4c0604037a099a6ef9ae24b9b0d5 19465 science optional opencascade_7.6.3+dfsg1-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmRscbIACgkQkWT6HRe9 XTZuRxAAxm1GgrkLRWS+RueaXPn/W6N9Zx6wjzNr1yrEWbPtqpvEXG2qqyIPw2Kb P4IHWZrL13Xy+UV3pMxAumjvoisEjJUth6fJ+sFMAImDaDYF7yavEothRc3M+j6p aec7YyZVT74m08d2gU2bDaz6lRzlnakMsy2CZ+j/ywI5B5SFC41bYDoOiyYKYlqy /klYS1w2ACmFpy0XPg7uLMMhzlRQxZkRLcSGk/mUncAHL42k4+4OUPvqIjfxzJpi V3ZCrm6dx+LtVQ8d7cxDl5C+97z6LUIikaxewYKhXopZjgu1qGuVDpIhcYE9C1jK ZWE/nffs3q+sZU3c4E0/QJMisRNLSP+cVebB95pkt4aVWdMuUDTPKNb9kJgGcgX+ I9BnItVXy1mJddskuwAbncnKXHyInkiU4UwI7n8X+7h3+Ct8fVkkWLaSzlfQ1wQm tyqt5Se6Np2wwRuoelHxobN/T22J7fFKKDopZfBNrPpzjBy7WJjyFfSgbM+yqkzN yMX/RpL2fIdKtys//UVp7gzIZzKKrbqgNFB7EzBddjFJrlBHkXuivjFx5DjmjmcM 2NnyA3vF5AFT8yKm5d3G0+pbxkFpLv9mG+4C+1k4FwONXvRxTUSMssh4Qnk/CLVa llER5ny8t3F7IRgpFT+DVmVgiy8SNowxzt1wCWfAB+t6Rk4oYjE= =Lx6/ -END PGP SIGNATURE End Message ---
Bug#1036609: node-jschardet: missing Depends/Recommends/Suggests: node-buffer ?
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 -> ../buffer (node-jschardet) Is node-jschardet missing some dependency/... on node-buffer? cheers, Andreas
Bug#1036582: marked as done (node-shelljs: broken symlink: /usr/bin/shjs -> ../lib/nodejs/shelljs/bin/shjs)
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 means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-shelljs Version: 0.8.5+~cs0.8.10-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: 0m22.0s ERROR: WARN: Broken symlinks: /usr/bin/shjs -> ../lib/nodejs/shelljs/bin/shjs (node-shelljs) The target seems to reside in /usr/share/nodejs instead of /usr/lib/nodejs. cheers, Andreas --- End Message --- --- Begin Message --- Source: node-shelljs Source-Version: 0.8.5+~cs0.8.10-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-shelljs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-shelljs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 May 2023 06:39:48 +0400 Source: node-shelljs Built-For-Profiles: nocheck Architecture: source Version: 0.8.5+~cs0.8.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1036582 Changes: node-shelljs (0.8.5+~cs0.8.10-2) unstable; urgency=medium . * Team upload * Fix /usr/bin/shjs link (Closes: #1036582) Checksums-Sha1: 67ac9edd8939dee8b26a016344ed7d037b712cb3 2530 node-shelljs_0.8.5+~cs0.8.10-2.dsc be8bf0e890c4da12c5ae8320d8d3edcf7f1900b8 8896 node-shelljs_0.8.5+~cs0.8.10-2.debian.tar.xz Checksums-Sha256: 25bf37d496248b97a15235ae04060275d13e16aad8590b3842723dcb6e95a68e 2530 node-shelljs_0.8.5+~cs0.8.10-2.dsc fc9d6f01b8d3f3ffa4aecee40c0efa37df8d05b45b69cf1c3e747e8e5479e96a 8896 node-shelljs_0.8.5+~cs0.8.10-2.debian.tar.xz Files: 7716b4fa0b341cec5ce01f55432e4d6e 2530 javascript optional node-shelljs_0.8.5+~cs0.8.10-2.dsc 8eef7b6efb7497920d2c7801e3c3713e 8896 javascript optional node-shelljs_0.8.5+~cs0.8.10-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRsddwACgkQ9tdMp8mZ 7ukchw/+OfDO+/D0qwRyJT59hM0ySXBPNmtA4OGanBn7EttdxKsxQBNfoOdgPLcY j9eCMkNgKuvsgkazslrQ7z8XLyvEakghNzChytBRJ5uZFEat70vM+XEbyRBpbCpL MTsuHj80Qpx+kpkdOjzs3CvG2DH94ADiIFHT64USkGfEth//hc+plfzmZEBPOm0v 1TG0gJqrbQ01cGgKyVUmByU50djU7eGPGoQKFLPG9E5iwE3Ubgn+54j50ghf7I0R 4SQSShxAxA/aaNXMgk/ThYArGQWAaDbQVM58w9BzT5YYVgV+2lh0EFo+cZaGFaVy urYkFuTolubMgImnxgHA262++ykJ0IFz3aoenIRJTidYXyWigmuy95LBXB6QAUx7 GAVCD32lV744JjZCA12nIXUAWmmR2qyO965vpHvTeyUmp4H2eWw5CxNN1RAy+Vc+ UOXDkaTXiofK2w06LucOv44GLpWDVMpfX4HDQA8VO9L+lU0y+C/OyqDSiAe0OuzM FxurzOB0MG89VzXXxLUtkeQ1mqNpFFSCFVYNubhq1Um68Xmw/BOT3EXsKOTqEaZb XQ91goRkVuyWU6QHXaBdmW7wUIPeLInTvSnwe2reRB/e4IcKYEaWQa7PvDp7SzR8 cqurSe/E/WjQshvlN2ecHCAU2h6E5TiH0ggK9GEFB/aOWoYIj7k= =xMyg -END PGP SIGNATURE End Message ---
Bug#1036579: marked as done (node-is-docker: broken symlink: /usr/bin/is-docker -> ../lib/nodejs/is-docker/cli.js)
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 means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-is-docker Version: 3.0.0-4 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.6s ERROR: FAIL: Broken symlinks: /usr/bin/is-docker -> ../lib/nodejs/is-docker/cli.js (node-is-docker) The target should probably be /usr/share/nodejs/is-docker/cli.js ^ cheers, Andreas --- End Message --- --- Begin Message --- Source: node-is-docker Source-Version: 3.0.0-5 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-is-docker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-is-docker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 May 2023 12:15:54 +0400 Source: node-is-docker Built-For-Profiles: nocheck Architecture: source Version: 3.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1036579 Changes: node-is-docker (3.0.0-5) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.2 * Fix /usr/bin/is-docker link (Closes: #1036579) Checksums-Sha1: 1933d971bc253e6f555c9142d22e79c2671b1c50 2065 node-is-docker_3.0.0-5.dsc 7917f3656ad0fd4b0d1a3adbc30ee557c2116b40 2868 node-is-docker_3.0.0-5.debian.tar.xz Checksums-Sha256: 08e05f44a95166a05d8ae91740de4ccfa78dd61e4a327b4e0112a56ea4c10fbb 2065 node-is-docker_3.0.0-5.dsc b513b6e811b0dad66abf0aa2fcd517240231baa866b250a4f1b8973b2a32d2cc 2868 node-is-docker_3.0.0-5.debian.tar.xz Files: 3a302a270cde3bfaab229137e0c45a4d 2065 javascript optional node-is-docker_3.0.0-5.dsc 37260047c04ae3cd0ca4b6453a470882 2868 javascript optional node-is-docker_3.0.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRsdowACgkQ9tdMp8mZ 7ulqVw//bWRlgumIdIvgeYAXPQfnmu8q/BfFmh33uOW7k/W2kE+KL6eSXGV4NVXd zxFtXtadCSBoGNHKJ8SdaPp58DU40PowUQRMs1iZjcR+nBbFAYRZ6p+jlRb/deyK H2616lHPW2/qmV7Cog8fATSzMN0X/UUyMPklgyYnOzjovUMO0NjmWpqubbDEJ1B1 CTFqHw63V09HZ+ENDoj0s7v2/D70r61DeYAJpGgLYFpCL414JG8F8e3bLEFqGDO5 I2st+CItRtuYdO1nZSWTdZlziMNdYK/6QQ0MZZJGR1aHle3yaeYK31RG90krzRVU azgPZqrmUB7MJwGEyfeQId3jokzZc7yqak30nq0sypuSjOKdknkIjQkaCOF0OHx1 it3oQQy5msicGRW2uX2MgrvUMPrv2JPDNudGvPSOZQiXqLUKd41KisPbCI5Vplo4 os8wI+wemkG+g9naY8a4dFNjFfzQfcu0nC5haN0Yo/vQzpVYu3/WFjU6IwoMuahU 1usRaSCEgr4kzUu/3wdyGaWR4Btad3zzTBzCQRMoW72dn07QRWyY/jf7Ne3UoI00 9pynvFFrEjumOM+T+UYKOhQ0cVswBtsF48/LDSVQ/cS5HKi1PUl/Xn75hgCXO9+d 1Kp16UpBs0nB38nT1F42Vnso/3fPXhlsUrrX1uzWMsyrE/yE59o= =nAUK -END PGP SIGNATURE End Message ---
Bug#1036603: libinventor1: broken symlinks: /usr/share/inventor/fonts/Century-Schoolbook-* -> /usr/share/fonts/X11/Type1/c0590*l.pfb
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 symlinks: /usr/share/inventor/fonts/Century-Schoolbook-Bold -> /usr/share/fonts/X11/Type1/c059016l.pfb /usr/share/inventor/fonts/Century-Schoolbook-BoldItalic -> /usr/share/fonts/X11/Type1/c059036l.pfb /usr/share/inventor/fonts/Century-Schoolbook-Italic -> /usr/share/fonts/X11/Type1/c059033l.pfb /usr/share/inventor/fonts/Century-Schoolbook-Roman -> /usr/share/fonts/X11/Type1/c059013l.pfb /usr/share/inventor/fonts/Utopia-Regular -> Century-Schoolbook-Roman fonts-urw-base35 does not provide the old "numeric" font names gsfonts-x11 had. (gsfonts-x11 is now an empty transitional package, so you could drop that alternative dependency.) Feel free to downgrade the severity if the missing fonts are harmless. cheers, Andreas
Processed: Bug#1036579 marked as pending in node-is-docker
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 ow...@bugs.debian.org with problems
Bug#1036579: marked as pending in node-is-docker
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: https://salsa.debian.org/js-team/node-is-docker/-/commit/3e122f4eca062235bdab9f8209656971ecc28673 Fix /usr/bin/is-docker link Closes: #1036579 (this message was generated automatically) -- Greetings https://bugs.debian.org/1036579
Bug#1036601: xenstore-utils: missing Depends: xen-utils-common
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 -> ../lib/xen-common/bin/xen-utils-wrapper (xenstore-utils) cheers, Andreas
Bug#1036596: python3-lldb-14: broken symlinks: /usr/lib/llvm-14/lib/python3/dist-packages/lldb/libLLVM-14.so.1 etc.
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: /usr/lib/llvm-14/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so -> ../../../../../lib/liblldb.so (python3-lldb-14) /usr/lib/llvm-14/lib/python3.11/dist-packages/lldb/lldb-argdumper -> ../../../../../bin/lldb-argdumper (python3-lldb-14) /usr/lib/llvm-14/lib/python3/dist-packages/lldb/libLLVM-14.0.6.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-14.0.6.so.1 (python3-lldb-14) /usr/lib/llvm-14/lib/python3/dist-packages/lldb/libLLVM-14.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-14.0.6.so.1 (python3-lldb-14) Possible target replacements are liblldb.so: /usr/lib/llvm-14/lib/python3/dist-packages/lldb/_lldb.so libLLVM-14.0.6.so.1: /usr/lib//libLLVM-14.so.1 lldb-argdumper: /usr/lib/llvm-14/bin/lldb-argdumper (there is currently one level of '..' too much) cheers, Andreas
Processed: Bug#1036581 marked as pending in opencascade
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 problems
Bug#1036581: marked as pending in opencascade
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: https://salsa.debian.org/science-team/opencascade/-/commit/2bd09f5508e56d66263d2b4e9b89b38ef97fd3e8 Fix #1036581 (broken symlink) Closes: #1036581 (this message was generated automatically) -- Greetings https://bugs.debian.org/1036581
Bug#1036576: libscotch{,par}metis-dev: broken symlinks: /usr/lib//*metis-*/lib*metis.* -> ../scotch-*/lib*metis.*
Package: libscotchmetis-dev Version: 7.0.3-1 Followup-For: Bug #1036576 Awkward. Thanks for catching it.
Bug#1036591: reaver: segmentation fault
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 up-to-date dependency is causing this. * What exactly did you do (or not do) that was effective (or ineffective)? Executing multiple commands. * What was the outcome of this action? Every command executed returns segmentation fault. * What outcome did you expect instead? The correct thing is that all commands were executed correctly. I tried compiling a newer version 1.6.6 and it worked fine with no segmentation fault. Plus several improvements upstream. Remembering that this packaging is unusable in the face of tests carried out. Short description of what the segmentation fault is about in your description. In the context of segmentation fault, segment refers to the program memory address space. Only the program's memory space is readable. Of this space, only the stack and part of the data segment are writable. Other parts of the data segment and text segment are not writable. The data segment is where global or static variables reside. The text segment, also called the code segment, is where program instructions are stored. Segments have size and permissions, such as write, read, and execute. Segmentation fault occurs when a program tries to access restricted memory, such as trying to write to the text segment or read from a non-existent memory address. The failure is reported by the memory protection system of the Memory Management Unit or MMU. The MMU is the hardware responsible for translating the virtual memory address to physical addresses. As soon as the MMU notices a memory access violation, it informs the Kernel of the problem. In the case of Linux, the Kernel sends a signal to the program, the SEGV. Upon receiving the signal, the program is usually terminated. -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reaver depends on: ii libc6 2.36-9 ii libpcap0.8 1.10.3-1 Versions of packages reaver recommends: ii pixiewps 1.4.2-5 Versions of packages reaver suggests: ii aircrack-ng 1:1.7-5 -- no debconf information
