working properly. Since bookworm-backports is already providing
pipewire 1.2, I would like to ask you to backport wireplumber 0.5 to stable in
the hope that this will fix the issue.
Thank you,
NoisyCoil
-- System Information:
Debian Release: 12.6
APT prefers stable-updates
APT policy: (500
Package: wnpp
Severity: wishlist
Owner: NoisyCoil
X-Debbugs-Cc: debian-de...@lists.debian.org, noisyc...@tutanota.com
* Package name: dysk
Version : 2.9.0
Upstream Contact: Denys Séguret
* URL : https://github.com/Canop/dysk
* License : MIT
Programming Lang
t; I've actually already completed the packaging (>
> https://salsa.debian.org/NoisyCoil/debcargo-conf/-/commits/package-dysk> ),
> didn't open the MR yet though. I'll be quite busy during the next few days,
> so I don't know if I'll be able to submit it before
Hi Dylan,
Thank you for your answer. No, I do believe the issue comes from the pairing,
although I acknowledge that pw 1.2 + wp 0.4 does work at least in a general
setting. In this respect, I apologize if I didn't make clear enough in my
initial report that when I said wp 0.4 is broken with pip
> P.S.: I just tried backporting wp 0.5 to bookworm myself, that is, rebuilding
>unstable's source package within bookworm-backports, and I can confirm
>pipewire 1.2 + wireplumber 0.5 + asahi-audio 2.2 (needed for the config format
>change) + alsa-ucm-conf-asahi 5 + linux-asahi 6.9.8 works in un
Source: wayland
Followup-For: Bug #1076729
X-Debbugs-Cc: noisyc...@tutanota.com
I can confirm this bug report, except for the fact that the cursor isn't shown
in my case (the session gets stuck on a plain black screen). Tested on a M1 Pro
MacBookPro running Asahi Linux (v6.9.9 and v6.9.10) and t
,
NoisyCoil
P.S.: I checked that llvm-16 still builds with gcc-14.
alling
the *-dev packages listed above does fix the issue in unstable, if all pkgconf
is supposed to return is the system include directory (at least as far as the
headers are concerned) there might be simpler ways to fix this (e.g. dropping
the
new dependencies in the .pc file?)
Thank you,
NoisyCoil
Package: dysk
Followup-For: Bug #1077511
X-Debbugs-Cc: noisyc...@tutanota.com
Hi Jonas,
I am having a bit of trouble understanding if your concerns are limited
to the description alone, or extend to the package itself, so I'll try
to cover both.
> I have difficulty understanding the purpose of
no change.
The section change in d/control was already accepted into unstable.
Thank you,
NoisyCoil
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: rust-bindgen-...@packages.debian.org, noisyc...@tutanota.com
Control: affects -1 + src:rust-bindgen-cli
Hello,
In order to fully fix bug #1069047, 'rust-bindgen-cli' needs to b
n
attachment.
Thank you,
NoisyCoil
*** /home/noisycoil/bindgen.patch
--- a/codegen/mod.rs
+++ b/codegen/mod.rs
@@ -714,18 +714,18 @@ impl CodeGenerator for Var {
let len = proc_macro2::Literal::usize_unsuffixed(
Package: rustc
Followup-For: Bug #1068008
X-Debbugs-Cc: noisyc...@tutanota.com
Hi,
I join the others in offering my help. If there is anything we can do please
let us know!
Best,
NoisyCoil
Hi Jonas,
Thanks for the fix. On a second thought yes, given that you're building the
package as "Architecture: all" your build.rs patch probably is the right thing
to do.
> I think that patch is generally usable, not only for Debian but also sensible
> for upstream to adopt.
I agree. They ar
> Also, would be neat if the patch was improved to not fail but lower
> optimization level and emit a warning.
I liked the idea so I started playing around a bit. While I haven't found a way
to achieve that yet (simply setting environment variables doesn't seem to work
and there doesn't seem to
I think you have MRs disabled in the rust-wide repo. You can cherry-pick this
commit from my fork:
https://salsa.debian.org/NoisyCoil/rust-wide/-/commit/c68a2e54b6bd231206a85a290b4da4e01ca72fbe.
Confusingly, while the `cfg` target checks run on the build machine, the
`CARGO_CFG_TARGET_
Yes, I think you misunderstood. Your patch, as it is, will *always* build code
for i386 when cross compiling, because the `cfg` check in build.rs applies to
the build machine and the empty main function (via #[cfg(not(target_arch =
"x86"))]) will always be compiled instead of the top one. CI suc
> Sorry, I still don't understand: If my patch effectively does nothing, then
> why do the tests now succeed when they failed without the patch applied?
What "fixed" the tests is the changes in d/tests/control, not the patch. Tests
passing is the expected behavior if the patch does nothing, beca
Package: xserver-xorg-core
Version: 2:21.1.12-2
Severity: wishlist
Tags: patch upstream
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
In order to work properly on Apple Silicon machines, the Xorg server needs
a quirk which was merged to upstream's master branch [1] but was never
backporte
Package: asahi-btsync
Followup-For: Bug #1071216
X-Debbugs-Cc: noisyc...@tutanota.com, cybae...@web.de
Hi all,
The reported bug seems to point to a missing variable in NVRAM, which is a bit
weird. I cannot reproduce it on my machine (M1 Mac Mini).
cy8aer, do you confirm the bug is still there an
So the bug is not specifically with asahi-btsync, but rather generically with
reading that variable from NVRAM. We could even reassign it to
librust-apple-nvram-dev since that's where the reading happens, but let's not
rush things (also, the variable specifically is a bluetooth variable). Does
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: rust-d...@packages.debian.org, noisyc...@tutanota.com
Control: affects -1 + src:rust-dysk
User: ftp.debian@packages.debian.org
Usertags: override
Hello,
Given that src:rust-dysk builds a single binary package, which
installs a binary appl
Package: wnpp
Followup-For: Bug #948483
X-Debbugs-Cc: noisyc...@tutanota.com, eam...@yaerobi.com
Hi eamanu,
Do you mind if I claim ownership of this ITP?
Cheers,
NC
not affect building images based on bookworm (nor
presumably on unstable, but I didn't check this explicitly).
Best,
NoisyCoil
>From 4d11835d376899258946d52b54cfe32f6d94 Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sat, 10 Aug 2024 15:07:43 +0200
Subject: [PATCH] Compile with -W
Hello,
The compile flag I used in the patch, -Wno-error=incompatible-pointer-types,
has been used since presumably forever to build zsync. Note that the code of
zsync has not changed since at least old-old stable: the zsync builds still in
Debian unstable and <= 12 were made using it. The issue
Thank you, I think this is a good compromise.
only one I'm aware of being rust-tiny-dfr).
Best,
NoisyCoil
Some data points:
1. I was able to reproduce the failures on an amd64 build machine running and
compiling i386 code as early as v0.7.11-2 (see logs at [1]). To reproduce, on
Debian Testing, within said version's source code:
```
sbuild-createchroot --include=eatmydata --arch=i386 testing
/srv/
In the light of the recent discussion upstream, it looks quite clear that the
test failures are due to the lack of SSE2 in Debian's i686 rust target (and
resulting unsound floating point behavior). The failures themselves were
triggered by your switch from dh-cargo to dh-rust, which caused autop
Package: ftp.debian.org
Followup-For: Bug #1080965
X-Debbugs-Cc: noisyc...@tutanota.com
Control: reopen -1
Hello,
I see the override file was updated for src:rust-dysk, but not for the binary
package dysk, while I had requested changing from 'rust' to 'utils' that one
too. If this happened becaus
Package: wnpp
Followup-For: Bug #1056068
X-Debbugs-Cc: noisyc...@tutanota.com, eam...@yaerobi.com,
debian-r...@lists.debian.org, n...@debian.org
Hi all,
While working on ITP #948483 I repackaged usvg and resvg v0.42 as dependencies
of broot, without knowing they were already being built by src:r
Package: wnpp
Followup-For: Bug #1056068
X-Debbugs-Cc: noisyc...@tutanota.com, eam...@yaerobi.com,
debian-r...@lists.debian.org, n...@debian.org
For the record, `cargo debstatus` now lists both usvg and resvg as being in
NEW, but were it not for NEW they would be listed as absent. In fact, readin
Package: gnome-core
Version: 1:47+1
Severity: important
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
Since September 30, gnome-core fails to install in newly debootstrapped testing
and
unstable chroots due to conflicting CUPS dependencies:
```
root@debian:~# deboostrap testing testing
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-bindgen-...@packages.debian.org, noisyc...@tutanota.com,
pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rust-bindgen-cli
User: release.debian@packages.debian.org
Usertags: binnmu
nmu rust-bindgen-cli_0.66.
Package: xserver-xorg-core
Version: 2:21.1.13-2
Followup-For: Bug #1080099
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
Has there been progress on this bug? Tobias Heider has recently rebased
[1], so the patch is ready to merge.
Best.
[1] https://salsa.debian.org/xorg-team/xserver/xor
Package: cpdb-backend-cups,cups-filters
Followup-For: Bug #1084195
X-Debbugs-Cc: noisyc...@tutanota.com, lewa...@gmail.com,
rolf.o1.heinri...@gmx.net
Hi Daniel,
Yes, I confirm this is fixed now.
Thank you!
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-bindgen-...@packages.debian.org, noisyc...@tutanota.com
Control: affects -1 + src:rust-bindgen-cli
User: release.debian@packages.debian.org
Usertags: binnmu
nmu rust-bindgen-cli_0.66.1-7+b2 . ANY . unstable . -m "Rebuild with
lib
Package: librust-bindgen-dev
Followup-For: Bug #1086510
X-Debbugs-Cc: noisyc...@tutanota.com, oj...@kernel.org
Control: tag -1 pending
Hi Miguel,
An updated version of librust-bindgen-dev with the patch backported was uploaded
to unstable. Please be aware that bindgen now needs to be rebuilt with
Package: librust-bindgen-dev
Followup-For: Bug #1086510
X-Debbugs-Cc: noisyc...@tutanota.com
Hi Miguel.
Correction: the fixed version will be bindgen 0.66.1-7+b3. The corresponding
binNMU bug is #1086616.
Have a good weekend!
pass in unstable using the updated version, as suggested by its Cargo.toml.
Bumping the dependency is trivial, but I'm attaching a patch anyway.
Best,
NoisyCoil
>From 89cee530c0560a18bb81a1feaa75cdc5d20b8b7c Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Mon, 11 Nov 2024 23:12:00 +0100
a4204cd1bdebae Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Wed, 23 Oct 2024 00:32:14 +0200
Subject: [PATCH] also provide the librust-lazy-regex+$feature-dev packages
---
debian/control | 16
1 file changed, 16 insertions(+)
diff --git a/debian/control b/debian/control
i
Thanks for the clarification Jonas. I still struggle to see the logic in it (at
least as it would apply to the default feature, I could make sense out of it
for other features), but there's no point in arguing. As a Debian developer you
have, of course, absolute freedom over how you decide to ma
> SemVer explicitly do not support stability across major releases, which
> implies that no stability is promised about a feature having same API across
> major releases.
Are you talking about the availability/unavailability of certain features? If
yes, all of debcargo-conf's packages involved
and its
autopkgtests pass in unstable using the updated version and leptonica as in
bug #1087401. Bumping the dependency is trivial, but I'm attaching a patch
anyway.
Best,
NC
>From 6047da829ed76cbbbce51d205183b4d03588a03d Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Mon, 11 Nov 2024
y. I tested them both, of course, although they are functionally
equivalent.
Best,
NC
[1] https://github.com/rust-lang/rust-bindgen/blob/main/CHANGELOG.md#changed-6
>From 8c2a5e022ce9afef26c2429f000b33f78faf9511 Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Mon, 11 Nov 2024 01:03:33 +0100
S
Control: reassign -1 librust-bindgen-dev
Control: affects -1 + bindgen
Hi Miguel,
Thanks for the very detailed bug report. I'm reassigning it to
librust-bindgen-dev as that's where the patch goes. In reference to your
previous statement [1] on when the bug could start to affect unstable,
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: noisyc...@tutanota.com
User: ftp.debian@packages.debian.org
Usertags: remove
Hello,
Please remove rust-libnotcurses-sys from unstable, as it has not seen an
upload in 3.5+ years, has an open RC bug (#985813), only exists for one
architect
take over all of it, not only the library parts.
I pushed the changes to debcargo-conf's current packaging of usvg/resvg needed
to build the binaries to my personal repo:
https://salsa.debian.org/NoisyCoil/debcargo-conf/-/commits/usvg-resvg. As far
as the binaries are concerned, packagin
Jonas, you must have missed one piece of my first email, which I report below:
> Jonas, I apologize for the duplicated work. Since you've been working on this
> for a long time I am more than willing to step down from {u,re}svg once the
> sources are rejected. I am no user of resvg and I am not in
> If you never offered to maintain resvg then how did this conversation
> emerge? Did I try to bend your words, when all you initially said was
> "whoops" and informing me that it was a bleep on the radar soon gone?
> If that's the case then I apologize for the confusion I have caused:
> Please sim
Hi Alex,
> I'm not sure that is really our policy? We package multiple binaries
> for packages that have them.
>From the "Packaging binaries" section in debcargo-conf's `rust_hacks.md`:
> If a package ships a binary but you only want to use it as library add this
> stanza in debcargo.toml:
>
>
Package: wnpp
Followup-For: Bug #1018258
X-Debbugs-Cc: noisyc...@tutanota.com
Control: retitle -1 ITP: procs -- modern replacement for ps
Control: owner -1 noisyc...@tutanota.com
Hello,
I would like to work on this.
Best.
ipten-core/emscripten/discussions/22656
[2] https://salsa.debian.org/NoisyCoil/emscripten/-/commits/3.1.66-3
[3] https://salsa.debian.org/NoisyCoil/binaryen/-/commits/119-1
Source: rust-leptonica-sys
Followup-For: Bug #1088237
X-Debbugs-Cc: noisyc...@tutanota.com
Control: forwarded -1 https://github.com/ccouzens/leptonica-sys/issues/29
Having spent some more time debugging this issue, I now see I looked at the
wrong autopkgtest run for leptonica-sys. The one I linked
Source: rust-comrak
Followup-For: Bug #1087914
X-Debbugs-Cc: noisyc...@tutanota.com
Control: tag -1 pending
Hi,
I pushed v0.29 to the debcargo-conf repo (v0.30 and higher have a new
dependency which is not packaged in Debian yet). It's waiting for
review and upload, in the meantime I'm tagging th
Package: tracker.debian.org
Followup-For: Bug #1088254
X-Debbugs-Cc: noisyc...@tutanota.com
Hi,
I had a similar experience to Julian's. bindgen 0.70.1-2 was uploaded on
November 22 together with a large number of rdeps. Most tests were run by
November 24 at the latest (I checked them manually on
Source: rust-comrak
Followup-For: Bug #1087914
X-Debbugs-Cc: noisyc...@tutanota.com
Control: tags -1 pending
Hi Samuel,
Although I am not the maintainer of this package, from what I can see
librust-version-ranges-dev is an actual dependency of pep440-rs [1],
which has been stuck in the NEW queue for more than two weeks now [2].
Cheers
[1] https://github.com/konstin/pep440-rs/blob/main/Cargo.toml
[
Source: rust-leptonica-sys
Severity: serious
Tags: upstream
Justification: RT
X-Debbugs-Cc: noisyc...@tutanota.com
Control: affects -1 + src:rust-tesseract-sys
Hi,
The recent bindgen update uncovered an i386 bug which was already present in
leptonica-sys, namely, the one described in [1]. It mani
Source: rust-leptonica-sys
Followup-For: Bug #1088237
X-Debbugs-Cc: noisyc...@tutanota.com
Hi,
The bug should be fixed in v0.4.9.
Cheers.
Source: rust-leptonica-sys
Followup-For: Bug #1088263
X-Debbugs-Cc: noisyc...@tutanota.com
Hi plugwash,
This is a duplicate of #1088237. Also, your bindgen bug is a duplicate of
[1], which was already closed approx. as "won't fix" in 2020. Not merging
the bugs nor taking further action so the res
Source: rust-lazy-regex
Version: 3.1.0-4
Severity: wishlist
X-Debbugs-Cc: noisyc...@tutanota.com, debian-r...@lists.debian.org
Hi Jonas,
Please upload rust-lazy-regex 3.1.0-4 to unstable. We are ready for the
transition.
Thanks.
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: rust-env-logger-...@packages.debian.org, noisyc...@tutanota.com
Control: affects -1 + src:rust-env-logger-0.7
User: ftp.debian@packages.debian.org
Usertags: remove
Hello,
On behalf of the Rust Team, please remove src:rust-env-logger-0.7 f
Control: tags -1 + pending
Hi Holger,
I've already fixed this in Salsa together with a number of related bugs,
will ask someone from the Rust Team for sponsorship soon (a large
migration is expected in the next few hours, so I'm trying to avoid
interferences).
Cheers!
FWIW, just to add half a data point, I recently tried backporting
rustc-1.83 to bookworm (that is, using the source from unstable), and
this bug didn't show up neither on amd64 nor on arm64. My logs look
exactly the same as Fabian's.
Cheers!
Package: broot
Version: 1.44.3-1
Severity: normal
X-Debbugs-Cc: noisyc...@tutanota.com
(Opening this bug report as the maintainer of the package to inform users this
is a known issue)
When the `open_preview` verb is executed on an image, a hexdump is displayed
instead of the image preview.
This
Package: dh-rust
Version: 0.0.10
Followup-For: Bug #1094199
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@jones.dk
Hi Jonas,
Has there been any progress on this bug? It is currently blocking the bindgen
transition (via oxigraph) and may possibly block other updates to come (some
evidence of this in
Control: reassign -1 dh-rust
Control: retitle -1 dh-rust: fails to build packages with profile
`nocheck` and B-Ds
Control: severity -1 important
Control: affects -1 + src:rust-async-std
This is a dh-rust bug. When the build is done with the `nocheck`
profile, `cargo package` is still called i
Control: retitle -1 dh-rust: fails to build packages with profile
"nocheck" and B-Ds
Control: severity -1 important
Control: affects -1 + src:rust-async-std
BTS control server was apparently unhappy with the retitling format,
trying again.
Source: rust-wasmtime
Followup-For: Bug #1095429
X-Debbugs-Cc: noisyc...@tutanota.com
Control: tags -1 + patch
Promised patch in attachment.
Cheers!
>From 43b05fba5278c55db6b83fe76b12bf57f7ce19dc Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sat, 8 Feb 2025 00:13:03 +0100
Subject: [PATCH]
v0.13 using the patch in attachment.
Cheers!
>From 6d1744c798de93d45ae2e6b7606d0ab8893946e5 Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sun, 9 Feb 2025 10:34:12 +0100
Subject: [PATCH] Bump capstone dependency to v0.13
---
debian/control | 4 ++--
debian/patc
with async-std),
showing that the underlying issue is in fact the same as Bug #1094483.
>From 475f2bf42e577d93ed524848d7862d6afd857a6f Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Fri, 7 Feb 2025 19:59:52 +0100
Subject: [PATCH] Add a `no-lock` option to `cargo package`
---
src/bin/cargo/
Package: dh-rust
Version: 0.0.10
Followup-For: Bug #1094199
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@jones.dk, ben...@debian.org
Hi Jonas,
Just putting some ideas out there, not sure they will actually help but at
least I tried.
Why should dependencies be installed in the correct order in th
Source: rust-wasmtime
Version: 21.0.2+dfsg-1.1
Severity: normal
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
src:rust-wasmtime's after_dh_auto_clean target,
```
# re-lock dependencies
execute_after_dh_auto_clean:
[ ! -f Cargo.lock.orig ] || mv -f Cargo.lock.lock Cargo.lock
```
> As I also wrote at #1094199, this is a bug against dh-rust, and since
> your arguments seem to be targeted at making changes to cargo, they are
> likely better suited at a separate bugreport.
Here I described cargo's behavior to explain how it affects dh-rust and how it
got worse starting with
Control: retitle -1 dh-rust: fails to build packages with profile `nocheck` and
B-Ds
Control: severity -1 important
Control: affects -1 + src:rust-async-std
Third time's the charm, they say.
there are no tests in the package,
I didn't do checks other than a test build.
Cheers!
>From d541c8f2f83b5f1a0a995d9a9110f6db5f03f106 Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sat, 18 Jan 2025 21:18:17 +0100
Subject: [PATCH] bump build-dependency for crate procfs
---
debian
No problem, thanks a lot!
Package: alsa-ucm-conf
Version: 1.2.13-1
Followup-For: Bug #1092257
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@debian.org
Hi Jordi,
Should we NMU this?
Thanks
Source: rustc-web
Followup-For: Bug #1084926
X-Debbugs-Cc: noisyc...@tutanota.com
Control: retitle -1 please Provide rustc from rustc-web and cargo from cargo-web
For similar reasons src:rustc-web should also Provide rustc from rustc-web.
Source: oxigraph
Version: 0.4.7-2
Severity: serious
Tags: ftbfs
Justification: RT
X-Debbugs-Cc: noisyc...@tutanota.com
Hi,
rust-bindgen v0.71 was just accepted in unstable. At this time src:oxigraph
(both v0.4.5-1 in unstable and v0.4.7-2 in experimental) depends on v0.70. Due
to the current FTBF
stall due to bug #1094737. And of
course, FTBFS means I could not *actually* test the package with the new
bindgen.
>From 3f599130570d95583a429665ee861920eb60c60c Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sat, 25 Jan 2025 21:11:00 +0100
Subject: [PATCH] Update to bindgen v0.71
---
debia
Package: m1n1
Version: 1.4.19-1
Severity: critical
Tags: upstream sid
Justification: breaks the whole system
X-Debbugs-Cc: noisyc...@tutanota.com
Version 1.4.19 [1] of m1n1 makes M2 Pro/Max Macbook Pros unbootable [2].
[1] Actually, >= 1.4.18, <= 1.4.20, but testing currently has 1.4.17 and
, I'm attaching a patch to decouple
rust-rust-ini from it. The patch is to be imported with quilt.
Cheers!
>From 19548da2f8b520d5b8177e801503aac18d9204c4 Mon Sep 17 00:00:00 2001
From: NoisyCoil
Date: Sun, 15 Dec 2024 12:46:33 +0100
Subject: [PATCH] Temporarily patch-out trim_in_place
Avoid
Source: rust-cargo
Followup-For: Bug #1090298
X-Debbugs-Cc: noisyc...@tutanota.com
Control: merge -1 1090296 1090297 1090299 1090301
Hi,
These are all the same bug, fixed by yesterday's upload of
librust-gix-credentials-dev 0.24.3-2. I'll wait for the latter to migrate to
testing and then I'll cl
Package: libvirt-daemon-driver-network
Version: 10.10.0-3
Followup-For: Bug #1090355
X-Debbugs-Cc: noisyc...@tutanota.com
I see the same behavior by simply having ufw installed and enabled, no special
rules, no docker installed. Disabling ufw or manually adding blanket INPUT and
FORWARD rules to e
Source: rust-coreutils
Severity: serious
Justification: RT
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
As agreed with you in [1], I'm about to file a removal request for rust-users
(see security Bug#1051808). rust-coreutils is the only package in the archive
that still depends on rust-u
Source: rust-ognibuild
Followup-For: Bug #1089894
X-Debbugs-Cc: noisyc...@tutanota.com, d...@jones.dk, jel...@debian.org
Hi Martin-Éric,
TL;DR: one issue is fixed in VCS and waiting for upload, I plan to work on
another issue if lazy-regex's maintainer doesn't beat me on timing, a third
issue is
Package: ftp.debian.org
Severity: normal
Tags: security
X-Debbugs-Cc: rust-us...@packages.debian.org, noisyc...@tutanota.com, Debian
Security Team
Control: affects -1 + src:rust-users
User: ftp.debian@packages.debian.org
Usertags: remove
Hello,
On behalf of the Rust Team, please remove src:
> Indeed I totally missed it. And your proposed patch (if working, which
> I am testing right now, restructered to instead extend existing feature
> fencing patch) is more elegant than giving up and skipping the test.
>
Thanks and I agree, it could be worth it not to disable the test. This is t
Package: librust-lazy-regex-dev
Followup-For: Bug #1089204
X-Debbugs-Cc: noisyc...@tutanota.com, d...@jones.dk
Hi Jonas,
I think you missed this bug, which was filed before plugwash's #1089813. This
is RC too, so it will prevent migration. Feel free to close it.
Best.
Thanks for the heads-up Jonas. However, that wasn't the right call. I cc'ed you
just to let you know that you were being mentioned in this discussion (and to
let you know that I would be working on a patch for a bug that I hadn't opened
yet!), but this bug was not blocked by any other bug presen
Package: librust-lazy-regex-dev
Followup-For: Bug #1089204
X-Debbugs-Cc: noisyc...@tutanota.com
Jonas,
Are you sure you are not mixing up bugs? This one is for an autopkgtest failure
that existed in v3.1, but currently (v3.3) there are other autopkgtest failures
which were just introduced upstrea
Source: rust-ognibuild
Followup-For: Bug #1089894
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@jones.dk
Control: unblock -1 by 1089204
Control: block -1 by 1089917
> Unfortunately, even with the (equivalent, I believe, of) your patch
> applied, a build with autopkgtest checking enabled still fails
> Apparently none of us tests autopkgtests: Turns out your patch was
> correct after all, albeit incomplete.
Not entirely sure I follow. I sent the patch one week ago, when it would
have fixed lazy-regex 3.1.0-6 and made all its autopkgtests pass, which
I had tested :-) Upload of 3.3 then intro
Thanks Andrea!
Package: libvirt-daemon-driver-network
Version: 10.10.0-3
Followup-For: Bug #1090355
X-Debbugs-Cc: noisyc...@tutanota.com
> This too is a known issue:
>
> https://fedoraproject.org/wiki/Changes/LibvirtVirtualNetworkNFTables#Known_issue:_non-firewalld_firewall_mgmt_tools
Confirmed. DHCP not workin
Source: oxigraph
Followup-For: Bug #1087350
X-Debbugs-Cc: noisyc...@tutanota.com
Control: severity -1 serious
bindgen v0.70.1 is now in unstable, raising severity to serious.
Source: rust-tesseract-sys
Followup-For: Bug #1087403
X-Debbugs-Cc: noisyc...@tutanota.com
Control: severity -1 serious
bindgen v0.70.1 is now in unstable, raising severity to serious.
Source: librust-lazy-regex-dev
Version: 3.1.0-6
Severity: serious
Tags: patch upstream
Justification: RT
X-Debbugs-Cc: noisyc...@tutanota.com
Hi,
Even after the changes in your last upload, lazy-regex failed the test with all
features disabled. I'm attaching a patch to be imported with quilt that
1 - 100 of 148 matches
Mail list logo
