Bug#1021678: [Pkg-rust-maintainers] Bug#1021678: Bug#1021678: rust-object: autopkgtest failure on s390x

2022-10-12 Thread Wolfgang Silbermayr
Am 13.10.22 um 01:23 schrieb Peter Green: 3. Apply the upstream fix as Debian packages, hope any resulting API breakage    is manageable. I did a quick regex search on https://codesearch.debian.not/ for "\bshndx\b package:^rust*", and that only revealed two source packages, namely

Bug#1011717: Patch

2022-05-27 Thread Wolfgang Silbermayr
/pixz/issues/103 Submitted MR: https://github.com/vasi/pixz/pull/104 Attached the patch exported such that it can be added to the package with quilt. Wolfgang. >From 2f4db115586bd3d98c1f05eb64c125495bf0331a Mon Sep 17 00:00:00 2001 From: Wolfgang Silbermayr Date: Fri, 27 May 2022 09:19:02 +0

Bug#975191: [Pkg-rust-maintainers] Bug#975191: re: rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2021-08-31 Thread Wolfgang Silbermayr
On 8/31/21 4:25 PM, Bastian Germann wrote: > On Wed, 2 Dec 2020 02:46:36 + peter green wrote: >>  > This will impact quite some other modules. >> >> I agree that the current autoremoval list looks pretty scary, so I decided >> to do some >> dependency analysis. It seems there are 5 source

Bug#985087: [Pkg-rust-maintainers] Bug#985087: CVE-2021-27378

2021-03-12 Thread Wolfgang Silbermayr
On 3/12/21 7:54 PM, Moritz Muehlenhoff wrote: > Source: rust-rand-core > Severity: grave > Tags: security > X-Debbugs-Cc: Debian Security Team > > Please see: > https://rustsec.org/advisories/RUSTSEC-2021-0023.html Thank you for your report. The commit [0] fixed the issue upstream in the

Bug#954613: rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev

2020-11-14 Thread Wolfgang Silbermayr
On Sun, 8 Nov 2020 09:55:38 +0100 Sylvestre Ledru wrote: > Hello Wofgang, > > Do you have the intention to fix process-viewer? > > We have a RC bug from March on it. Hi Sylvestre, I updated the patch in the debcargo-conf repo on Salsa in a way that fixes the problem. My previous gpg subkey

Bug#947709: (no subject)

2020-01-27 Thread Wolfgang Silbermayr
A quick investigation reveals: * We have the "@" test (currently called command1 in the quoted log) which enables all crate features. The clang-sys crate does not permit enabling both the "runtime" and the "static" features at the same time, so the build script intentionally aborts with a

Bug#946734: [Pkg-rust-maintainers] Bug#946734: rust-addr2line Build-Depends on librust-fallible-iterator-0.1+default-dev which isn't available

2019-12-15 Thread Wolfgang Silbermayr
On 12/14/19 10:49 PM, Paul Gevers wrote: > Source: rust-addr2line > Version: 0.7.0-1 > Severity: serious > Tags: ftbfs > > Dear maintainers, > > Your package was never build on a buildd, and was rescheduled 117 days > ago. Since then, the status is BD-Uninstallable. Can you please make sure that

Bug#946465: [Pkg-rust-maintainers] Bug#946465: librust-rand+alloc-dev: does not find upgrade path from buster to bullseye

2019-12-12 Thread Wolfgang Silbermayr
On 12/9/19 3:38 PM, Andreas Beckmann wrote: > Package: librust-rand+alloc-dev > Version: 0.6.4-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'buster'. > It installed fine in

Bug#945796: [Pkg-rust-maintainers] Bug#945796: rust-url-serde: (build-)depends on obsolete virtual package.

2019-11-28 Thread Wolfgang Silbermayr
On 11/28/19 9:04 PM, peter green wrote: > Package: rust-url-serde > Version: 0.2.0-1 > Severity: serious > Tags: bullseye, sid > > librust-url-serde-dev depends on and rust-url-serde build-depends on > librust-url-1+default-dev which is no longer provided by rust-url. It > seems to have been

Bug#927314: Reported upstream

2019-04-27 Thread Wolfgang Silbermayr
Thanks for your report. Forwarded to upstream: https://github.com/tomprogrammer/rust-ascii/issues/61

Bug#901148: Some analysis

2019-04-07 Thread Wolfgang Silbermayr
Having been hit by this on Buseter Testing before, I did some investigation. Here are my findings: Conditions for this bug to appear are: * timidity-daemon is installed * timidity service (from the timidity-daemon package) is enabled or timidity gets started by hand * No midi