Package: btlib
Version: 1.7.5+dfsg-2
According to tracker.debian.org the new version of btlib is
causing an autopkgtest regression in nthash, this is
preventing the new versions of btlib from migrating to
testing.
The new version of btlib is needed to fix a build-dependency
uninstallability issu
(43.0.0-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix overly strict build-dependency for cc crate.
+
+ -- Peter Michael Green Thu, 24 Apr 2025 21:13:03 +
+
python-cryptography (43.0.0-2) unstable; urgency=medium
* Restore B-D: python3-setuptools (Closes: #1100262
If preferred, a variant of the proposed changes with a default of "no" would
also be possible
I think the default (for bin packages) should be not to generate a multi-arch:
field at all.
This is behaviorally equivalent to multi-arch: no, but it IMO has different
implications, it implies "noone
Most of the issues appear to be some pointer definition mismatch for
dirent...
Rust does not have a core type that is directly equivalent to the
c type char, instead it has a type alias core:ffi::c_char (also
rexported as std::ffi::c_char) which, depending on the target
platform, is an alias for
On 21/04/2025 12:47, Moritz Mühlenhoff wrote:
Am Tue, Apr 15, 2025 at 07:52:49PM +0200 schrieb Alexander Kjäll:
pprof was at some point needed for the gix stack, if they have moved
away from using it then I agree that it's not needed in trixie.
Will this bug be enought to block it, or do we n
Package: storm
Version: 1.0-1
Severity: serious
storm has binaries on 32-bit architectures (i386, armel, and armhf),
however it's build-dependencies cannot be satisified there
package: storm
version: 1.0-1
architecture: any
type: src
status: broken
reasons:
-
missing:
pk
The debdiff patch
is in the attachment.I have tested that locally,and it works well.Please
let me know whether this solution can be accepted.
You seem to have totally ignored the existing built-using.patch and added
a new patch, furthermore your new patch hardcodes the version number of
ring, so
On 15/04/2025 16:07, Jing Luo wrote:
X-Debbugs-Cc: debian-am...@lists.debian.org, debian-...@lists.debian.org,
debian-powe...@lists.debian.org, debian-ri...@lists.debian.org
I understand CC'ing the porters when you have an issue that is specific to the
port, but
if it's failing on every damn
Tags 1068418 +wontfix
After a bunch of back and forth the upstream maintainer of this crate has
stated.
The goal of this crate is to implement direct, memory safe bindings to OpenSSL
APIs. Some of those APIs are poorly designed, but that is frankly OpenSSL's
problem, not my problem.
Package: rust-pprof
Version: 0.13.0-5
Severity: serious
X-debbugs-cc: alexander.kj...@gmail.com
A soundness issue was reported in rust-prost 0.13,
https://rustsec.org/advisories/RUSTSEC-2024-0408.html
which is reported as causing real-world failures in
downstream applications.
I looked at updati
Package: pydantic
Version: 2.10.6-1
Severity: serious
After the update of pydantic-core to build against the new rust-url,
pydantic's autopkgtests are failing.
https://ci.debian.net/packages/p/pydantic/testing/amd64/59623497/
63s E Differing items:
63s E {'msg': 'Input should
severity 1101417 serious
thanks
On 27/03/2025 11:06, Colin Watson wrote:
This was fixed upstream in
https://github.com/pydantic/pydantic-core/pull/1585. Since the new
tests won't work with the old rust-url, unless you object, I think it
would be simplest for us to just cherry-pick that at t
On 19/03/2025 11:03, Adrian Bunk wrote:
It's easy to reproduce even with the binary package when you remove
openssl (see #1099669).
I've now reproduced the bug.
It seems the package will build successfully as long as /etc/ssl/certs
exits, but will fail if that directory does not exist. Install
Is there something I can improve on this front? In other words, how can
the design become smarter?
It's hard to answer this because I don't really understand exactly
how the scheduler works, but what I frequently see is.
1. The set of pins that britney chooses don't work.
2. The fallback depend
> ∙ ∙ Built-Using: rust-rebuildctl rust-rustls-native-certs (not considered)
rust-rustls-pemfile and friends have been trying to migrate to testing for
nearly a month, but a combination of a few real issues, a number of
well-intentioned
but poorly timed uploads, britney's autopkgtest scheduler b
Package: rust-skeptic
Version: 0.13.7-4
Severity: serious
rust-skeptic's dependencies are no longer satisfiable in unstable
after the upload of rust-cargo-metadata 0.15
(a removal request for this package has already been filed)
Package: rust-unzip
Version: 0.1.0-1
severity: serious
rust-unzip is no longer installable in unstable after the upload
of rust-zip 2.0
(a removal request for this package has been filed already)
-tz.
+
+ -- Peter Michael Green Fri, 28 Mar 2025 08:03:18 +
+
railway-gtk (2.7.3-1) unstable; urgency=medium
* New upstream release (Closes: #1098620)
diff -Nru railway-gtk-2.7.3/debian/control railway-gtk-2.7.3/debian/control
--- railway-gtk-2.7.3/debian/control2025-02-23 15:08
Package: pydantic-core
version: 2.27.2-1
I hope to update rust-idna soon to version 1.0.3 to fix CVE-2024-12224,
the Debian build-dependencies for your package allow the new version
but the Cargo dependency does not.
After relaxing the cargo dependency, I ran into some test failures,
I think the
0.6,
+The current package produces many errors with version 0.7.
+
+ -- Peter Michael Green Sat, 22 Mar 2025 23:27:07 +
+
rust-ureq (2.12.1-4) unstable; urgency=medium
* reduce patch 2001_rustls to not involve crate rustls-pemfile;
diff -Nru rust-ureq-2.12.1/debian/control rust-ureq-2
Package: rust-railway-core
Version: 0.1.2-3
Since we don't want to carry around the old versions of rustls, http
and friends forever, I started looking through the reverse-dependencies
of the old version of hyper-rustls. Two that popped up were railway-core
and hafas-rs. The vcs link for both too
Package: rust-hafas-rs
hafas-rs seems to have been renamed to railway-backend,
and split into multiple crates, which have been packaged
in Debian. There do not appear to be any remaining reverse
dependencies.
Should rust-hafas-rs be removed?
+
@@ -1,3 +1,11 @@
+rust-hyper-rustls (0.27.5-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove autopkgtest for feature "acceptor" which no longer
+ exists.
+
+ -- Peter Michael Green Sat, 22 Mar 2025 09:25:12 +
+
rust-hyper-rustls (0.27.5-1) unstable;
On 18/03/2025 20:22, Jonas Smedegaard wrote:
Looks like it is best to wait until the current wave of changes related
rustls-pemfile has entered testing before stirring the dependency chain
more. As I understand it, that chain of dependencies currently awaits
axum til mature, and possibly other
On 15/03/2025 14:38, Jonas Smedegaard wrote:
Quoting Peter Green (2025-02-21 05:02:41)
Hi.
I've been looking at the various aspects of the rustls stack update, and I think
we probably want to semver-suffix tokio-rustls and hyper-rustls so reqwest 0.11.
can remain on the old rustls,
+
@@ -1,3 +1,11 @@
+rust-tonic (0.12.3+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix tests with rustls-native-certs 0.6
+ * Fix typos in control files.
+
+ -- Peter Michel Green Sun, 16 Mar 2025 12:28:58 +
+
rust-tonic (0.12.3+dfsg-1) unstable; urgency=m
In addition to the new version of zbus, there is also now a new version of
tonic, which will
need to be dealt with if this package is to remain in trixie. I had a quick
poke in the
upstream git history and there seems to be a commit doing the update.
https://github.com/containers/netavark/commi
severity 1099728 important
retitle 1099728 unmaintained upstream since 2021
thanks
The crate yaml-rust have seen no upstream activity since 2001, and have
been flagged as unmaintained in RUSTSEC since 2004:
These dates are off by 20 years, rust didn't even exist in 2001.
I'm downgrading this
member of said team.
On 10/03/2025 07:08, Andreas Tille wrote:
Source: pgzero
Version: 1.2.post4+dfsg-2
Severity: important
X-Debbugs-Cc: Debian Python Team , Peter Michael Green
, Serge Schneider , 1060...@bugs.debian.org,
1083...@bugs.debian.org, Package Salvaging Team
Hi,
I'm int
I've prepared a version of reqwest with a vendored copy
of hyper-rustls to get the package fixed while we wait for
a suitable version to be packaged seperately.
It's in debcargo-conf, can you test it before I upload it to
sid?
On 08/03/2025 18:05, Peter Green wrote:
Unfortunatel
Unfortunately we can't remove this patch yet (along with
downgrade-rustls.patch) until the following packages become available:
- librust-hyper-rustls-0.27+http1-dev
- librust-rustls-pemfile-2+default-dev
Opening this bug so it's documented.
I've just updated rustls-pemfile in sid.
The quest
On 22/02/2025 18:31, Jonas Smedegaard wrote:
Quoting Peter Green (2025-02-22 18:23:00)
Package: rust-rustls-native-certs
Version: 0.6.3-4
I hope to update rust-rustls-pemfile to version 2 soon, you expressed
in bug 1098278 that you would prefer the rustls-pemfile and
rustls-native-certs
urgency=medium
+
+ * Non-maintainer upload.
+ * Add patches to support new versions of rtnetlink, netlink-packet-route
+if-addrs crates, update Debian build-dependencies accordingly.
+(Closes: #1099780)
+
+ -- Peter Michael Green Sat, 08 Mar 2025 03:59:15 +
+
rust-if-watch (3.
match
+Cargo dependency.
+
+ -- Peter Michael Green Fri, 07 Mar 2025 00:10:27 +
+
mdevctl (1.4.0-1) unstable; urgency=medium
* New upstream version 1.4.0
diff -Nru mdevctl-1.4.0/debian/control mdevctl-1.4.0/debian/control
--- mdevctl-1.4.0/debian/control2025-02-19 17:27
/2001_rustls.patch
+ * Update debian build-dependencies for rustls version change.
+ * Update 2001_rustls-native-certs.patch for new rustls.
+ * Update other debian patches to avoid fuzz issues.
+
+ -- Peter Michael Green Tue, 25 Feb 2025 04:23:32 +
+
rust-ureq (2.12.1-3) unstable; urgency
02-25 03:13:13.0
+
@@ -1,3 +1,10 @@
+rust-tonic (0.10.2+dfsg-12.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch for rustls-pemfile 2.
+
+ -- Peter Michael Green Tue, 25 Feb 2025 03:13:13 +
+
rust-tonic (0.10.2+dfsg-12) unstable; urgency=medium
*
:05:33.0
+
+++ rust-hyper-rustls-0.24.2/debian/changelog 2025-02-25 00:49:17.0
+
@@ -1,3 +1,10 @@
+rust-hyper-rustls (0.24.2-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to support rustls-pemfile 2.
+
+ -- Peter Michael Green Tue, 25 Feb
Package: rust-imap-client
Version: 0.1.5
Severity: serious
I recently introduced a semver-suffix package rust-tokio-rustls-0.24, and
updated the
main rust-tokio-rustls package to 0.26.
Unfortunately rust-imap-client's debian dependency is inconsistent with it's
cargo
dependency. The Debian dep
:02:14.0 +
@@ -1,3 +1,10 @@
+rust-rustls-native-certs (0.6.3-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to support rustls-pemfile 2.
+
+ -- Peter Michael Green Sat, 22 Feb 2025 17:02:14 +
+
rust-rustls-native-certs (0.6.3-4) unstable; urgency=medium
It seems to me that you are lumping together two issues that can be
tackled independently. It makes me nervous to do too many changes at
once, especially when they require tight coordination like here: the
patch to support rustls-pemfile 2 removes support for rustls-pemfile 1,
which means the mi
Hi.
I've been looking at the various aspects of the rustls stack update, and I think
we probably want to semver-suffix tokio-rustls and hyper-rustls so reqwest 0.11.
can remain on the old rustls, while reqwest 0.12 moves to the new rustls.
tokio-rustls is a rust team package, so I can deal with
On 19/02/2025 05:49, Jonas Smedegaard wrote:
I would love to get rustls-native-certs upgraded, and am happy for help
doing it, but think that it will require fixing each reverse dependency
first - which was possibly also the exact thing you were doing here.
Yup, working through the reverse depen
I fixed the dependency installability issues with librust-ntp-proto-dev but
rust-ntp-os-clock seems to be incompatible with the new version of
ntp-proto and also seems to be abandoned upstream and has no rdeps
in Debian.
sylvestre, should we remove it?
On 18/02/2025 21:58, Jonas Smedegaard wrote:
Quoting Peter Green (2025-02-18 22:15:14)
Package: rust-mail-send
I hope to update rustls-native-certs to 0.8 soon.
I see that the version in experimental already uses rustls-native-certs 0.8
but it also uses a newer version of tokio-rustls, which
gelog 2025-02-18 21:09:38.0
+
@@ -1,3 +1,10 @@
+rust-mail-send (0.5.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Update for rustls-native-certs 0.8
+
+ -- Peter Michael Green Tue, 18 Feb 2025 21:09:38 +
+
rust-mail-send (0.5.0-1) unstable; urgency=m
++ Adjust dependency in Debian packaging.
++ Drop 2001
+
+ -- Peter Michael Green Tue, 18 Feb 2025 20:26:23 +
+
rust-imap-client (0.1.5-2) unstable; urgency=medium
* declare rust-related build-dependencies unconditionally,
diff -Nru rust-imap-client-0.1.5/debian/control
rust-imap
Package: rust-rustls
I hope to update rust-rustls-native-certs to version 0.8 soon
(after the new rust-rustls is in testing), I think it probablly
makes sense to update rust-hyper-rustls at the same time.
I looked though the upstream git history and it seems that the
changes for 0.7-0.8 are in a
annotation to str derived from arraystring.
+ * Relax cargo dependency on base64.
+ * Fix build to support rustls-native-certs 0.8 and update
+dependencies.
+
+ -- Peter Michael Green Tue, 18 Feb 2025 18:58:45 +
+
pushpin (1.39.1-3) unstable; urgency=medium
* Upgrade base64 dependency to
gency=medium
+
+ * Non-maintainer upload.
+ * Add patch for rustls-pemfile 2.
+ * Add patch for rustls-native-certs 0.8
+
+ -- Peter Michael Green Tue, 18 Feb 2025 04:46:26 +
+
rust-rustls-0.21 (0.21.12-13) unstable; urgency=medium
* install tests to versioned directory;
diff -Nru
Package: librust-rustls-0.21-dev
Version: 0.21.12-12
Severity: serious
While attempting to update one of my development chroots I ran into the
following error.
> Unpacking librust-rustls-0.21-dev (0.21.12-12) ...
> dpkg: error processing archive
/var/cache/apt/archives/librust-rustls-0.21-dev_
ython-libcst-1.4.0/debian/changelog2025-02-13 12:47:33.0
+
@@ -1,3 +1,9 @@
+python-libcst (1.4.0-1.1+rpi1) trixie-staging; urgency=medium
+
+ * Fix build-dependency for thiserror crate.
+
+ -- Peter Michael Green Thu, 13 Feb 2025 12:47:33
+
+
python-libcst (1.4.0-1.1)
14:04:30.0 +
@@ -1,3 +1,10 @@
+sourmash (4.8.14-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove upper limit from cargo dependency on rkyv (Closes: #1095393).
+
+ -- Peter Michal Green Tue, 11 Feb 2025 14:04:30 +
+
sourmash (4.8.14-2) unstable; urgency
Looking at the version number, the offending package seems not to be
from debian/raspbian per-se, but from the packages raspberry pi add on
top of Debian/Raspbian to make "raspberry Pi OS".
On 06/02/2025 10:39, Andrew Maier wrote:
Hello,
Thanks for all these pointers.
For my Raspis, I usually
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
rust-sqlx-core and rust-sqlx seem to be blocked by some autopkgtest snarlups,
particularly 3 autopkgtests seem to be stuck in "test in progress".
The test for rust-ognibuild with the new r
Package: rust-idna
Severity: important
It seems like it would be a good idea to upgrade the idna crate to version 1,
version 0.5 has a "security" issue and the new version of rust-url, which has
been requested by jonas needs version 1.
rust-idna 1 supports multiple backends with the backend bein
Package: rust-serde-yml
Severity: serious
(I will be cloning this bug against rust-libyml once I have a bug number)
rust-serde-yml is a fork of rust-serde-yaml and rust-libyml is
a fork of rust-unsafe-libyaml.
Serious concerns have been raised about the quality of code in
rust-serde-yml.
https
I tried to get this building with idna 0.4 but it seems like
a pain, so probablly better to do this as part of an idna 1
update.
Will look into what that entails, but not right now.
rust-serial-test version 3 depends on the scc crate which is
not currently in Debian.
Looking at the package descriptions I think html5ever, xml5ever and markup5ever
should probablly be updated as a group.
So either
html5ever 0.27, markup5ever 0.12, xml5ever 0.18
html5ever 0.28, markup5ever 0.13, xml5ever 0.19
html5ever 0.29, markup5ever 0.14, xml5ever 0.20
Looking at the
Package: rust-condure
x-debbugs-cc: j...@debian.org
rust-condure has not seen either a maintainer upload, or a new upstream
release in two years.
Furthermore, upstream recently archived the git repository with the
following message.
> UPDATE: This project has been merged into Pushpin and the re
I see that in addition to updating to 0.22, jamessan has restructured
the tree-sitter packaging in experimental to take it out of the rust
team and move to a single source package (tree-sitter) for all the
tree-sitter-* packages.
Looking through the reverse dependencies I see
sdml - maintained b
tags 1091017 +patch
thanks
A merge request addressing this issue can be found at
https://salsa.debian.org/debian/elan/-/merge_requests/1
-maintainer upload.
+ * Bump gimli and object dependencies (Closes: #1090390, #1091602).
+
+ -- Peter Michael Green Thu, 02 Jan 2025 19:56:39 +
+
rust-wasmtime (21.0.2+dfsg-1) unstable; urgency=medium
[ upstream ]
diff -Nru rust-wasmtime-21.0.2+dfsg/debian/control
rust-wasmtime-21.0.2
> Please upgrade or separately provide newer branch v0.15.
Preliminary analysis
Quite a few removals listed in the upstream changelog, not clear how widely
used the removed APIs were though.
In terms of the upstream state of the rdeps, 0.14 still seems
significantly more
prevalent than 0.15.
reopen 1090075
thanks
On 28/12/2024 03:28, Paul R. Tagliamonte wrote:
Heyya Peter,
There's a subtle syntax in the bug title; so I took the liberty of
fixing it by hand. I think the auto-decrufter already resolved this
situation
I don't think the auto-decrufter removes binaries when a packag
severity 1090390 serious
severity 1090396 serious
thanks
the updated backtrace stack is now in unstable, raising the severity of
bugs.
embed and
+i18n-embed-impl.
+ * Add patch to support i18n-embed 0.15 with i18n-embed-fl 0.9 and bump
+dependencies accordgingly.
+
+ -- Peter Michael Green Thu, 26 Dec 2024 00:17:34 +
+
tuigreet (0.9.1-4) unstable; urgency=medium
[ Peter Michael Green ]
diff -Nru tuigreet-0.9.1/debia
@@
+sccache (0.9.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump object to 0.36
+
+ -- Peter Michael Green Tue, 17 Dec 2024 23:12:49 +
+
sccache (0.9.0-1) unstable; urgency=medium
[ upstream ]
diff -Nru sccache-0.9.0/debian/control sccache-0.9.0/debian/control
--- sccache
Package: rust-version-sync
Version: 0.9.5-5
Your Debian dependency on the pulldown-cmark crate allows the
version in testing, but your cargo dependency does not, this is
leading to autopkgtest failures on some architectures.
Please can you either relax the cargo dependecy to allow the
version in
Package: sccache
Version: 0.9.0-1
I am currently looking at updating rust-backtrace and related packages
to the latest version, backtrace itself is not semver-breaking but
a number of it's dependencies are.
backtrace 0.3.69 -> 0.3.74
addr2line 0.21.4 -> 0.24.2
object 0.32.3 -> 0.36.5
gimli 0.28.
/changelog 2024-11-16 22:20:06.0
+
+++ rust-wasmtime-21.0.2+dfsg/debian/changelog 2024-12-17 22:19:16.0
+
@@ -1,3 +1,10 @@
+rust-wasmtime (21.0.2+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump gimli and object dependencies.
+
+ -- Peter Michael
As the PTS page shows, rust-ognibuild has long failed to migrate to testing due
to broken depedencies. This, in turn, affects the migration of other packages.
Could you please look into this? Thanks!
Update, I have uploaded the latest version of rust-ognibuild, currently it's
testing migratio
Package: ftp.debian.org
Please remove rust-vm-memory and it's reverse dependencies rust-vhost,
rust-vhost-user-backend
and rust-virtio-queue on 32-bit architectures. The new version of
rust-vm-memory has a
build-dependeny on "architecture-is-64-bit" and the other packages in the list
all
build
gency=medium
+
+ * Non-maintainer upload.
+ * Fix test feature gates.
+
+ -- Peter Michael Green Sat, 14 Dec 2024 14:24:34 +
+
rust-lazy-regex (3.3.0+20241210-1) unstable; urgency=medium
[ upstream ]
diff -Nru
rust-lazy-regex-3.3.0+20241210/debian/patches/1001_fence_features.patch
rust
Package: dgit
mkdir test
dget -d http://ftp.debian.org/debian/pool/main/g/glib2.0/glib2.0_2.82.3-2.dsc
cd test
git init
dgit import-dsc ../glib2.0_2.82.3-2.dsc +workingbranch
results in
gpgv: Signature made Tue 10 Dec 2024 23:42:20 GMT
gpgv:using RSA key 7A073AD1AE694FA25BFF62E5
Package: rust-lazy-regex
Version: 3.1.0-6
Severity: serious
The no features autopkgtest for rust-lazy-regex is failing.
78s error[E0432]: unresolved import `regex`
78s--> src/lib.rs:203:9
78s |
78s 203 | self,
78s | no external crate `regex`
Doing some di
(3.0.1-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix build-dependency for regex crate.
+
+ -- Peter Michael Green Thu, 12 Dec 2024 04:56:42 +
+
fragments (3.0.1-3) unstable; urgency=medium
* Update d/control and d/p/relax-deps for nix 0.29 (Closes: #1085436
ilures and is not used by leptonica.
+
+ -- Peter Michael Green Tue, 26 Nov 2024 02:40:08 +
+
rust-leptonica-sys (0.4.8-3) unstable; urgency=medium
* autopkgtest-depend on dh-rust (not dh-cargo)
diff -Nru
rust-leptonica-sys-0.4.8/debian/patches/1002_blocklist_max_align_t.patch
rust-lep
00
+
@@ -1,3 +1,11 @@
+rust-leptess (0.14.0-6.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Replace ImageOutputFormat::Tiff with ImageFormat::Tiff in test and
+example to fix autopkgtest with rust-image 0.25.
+
+ -- Peter Michael Green Mon, 11 Nov 2024 07:11:29
Package: jameica-datasource
Version: 2.8.1+dfsg-4
Severity: serious
Justification: rc-policy - packages must be buildable within the same release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
jameica-datasource build-depends on libmckoisqldb-java-doc which is
no longer built by t
Package: rust-tealdeer
Version: 1.7.0-1
Severity: serious
Justification: rc-policy - packages must be buildable within the same release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
tealdeer build-depends on versoin 0.5 of rust-yansi, but trixie/sid
now has version 1, so it is no
Package: libpdb-redo3
Version: 3.1.5-3
Severity: serious
libpdb-redo3 has a hard coded dependency on libcifpp5, so after
building aginst the new version it ends up with dependencies
on both libcifpp5 and libcifpp7
Please remove or update the dependency.
This bug affects both 3.1.5-3 in testing
Please upgrade to, or separately provide, branch v0.29.
I think I've pretty much worked through all the rdeps now.
Currently waiting for rust-findutils (hopefully my latest uploaded fixed it)
and rustc to get into testing before I go ahead and do the big block of
uploads to unstable.
aardvark-
.
+ * Fix Debian dependency for "half" crate.
+
+ -- Peter Michael Green Thu, 25 Jan 2024 08:27:35 +
+
rust-coreutils (0.0.23-2) unstable; urgency=medium
* Team upload.
diff -Nru rust-coreutils-0.0.23/debian/control
rust-coreutils-0.0.23/debian/control
--- rust-coreutils-0.0
-dependency accordingly.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 22:46:25 +
+
wlgreet (0.5.0-2) unstable; urgency=medium
* Rebuild with smithay 0.16, kindly provided by James McCoy
diff -Nru wlgreet-0.5.0/debian/control wlgreet-0.5.0/debian/control
--- wlgreet-0.5.0/debian/control2024
+
@@ -1,3 +1,10 @@
+tuigreet (0.9.1-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove upper limit from Cargo dependency on nix.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 16:27:34 +
+
tuigreet (0.9.1-3) unstable; urgency=medium
* Backport upstream commit to
+
+ * Non-maintainer upload.
+ * Drop downgrade-nix-0.27.patch
+ * Stop patching nix dependency in relax-deps.patch
+ * Update Debian build-dependency for nix crate to match Cargo dependency.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 16:11:36 +
+
trippy (0.11.0+dfsg-2) unstable; urgency=medium
2001_sealed_test.patch and 2002_system-shared_libs.patch
+so they don't conflict with 2001_nix.patch.
+ * Update debian build-dependency for nix crate from 0.27 to 0.29.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 14:57:22 +
+
meli (0.8.7+20241007+dfsg-1) unstable; urgency=m
+
@@ -1,3 +1,10 @@
+greetd (0.10.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch for rust-nix 0.29.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 14:33:13 +
+
greetd (0.10.3-1) unstable; urgency=medium
* NUR.
diff -Nru greetd-0.10.3/debian/control greetd
-maintainer upload.
+ * Relax nix dependency.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 14:11:23 +
+
fragments (3.0.1-2) unstable; urgency=medium
* Cherry-pick upstream patch for gtk-rs 0.9
diff -Nru fragments-3.0.1/debian/control fragments-3.0.1/debian/control
--- fragments-3.0.1/debian
+++ bpftop-0.5.2.9.ga1b99d7/debian/changelog2024-10-19 01:40:22.0
+
@@ -1,3 +1,10 @@
+bpftop (0.5.2.9.ga1b99d7-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax cargo dependency on nix.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 01:40:22 +
+
bpftop
intainer upload.
+ * Add patch for nix 0.29.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 01:11:38 +
+
aardvark-dns (1.12.2-1) unstable; urgency=medium
* New upstream relase.
diff -Nru aardvark-dns-1.12.2/debian/control aardvark-dns-1.12.2/debian/control
--- aardvark-dns-1.12.2/debian/con
Reading the upstream changelog it seems that a load of
"breaking changes" came in 0.10 with those since then
being relatively minor. I've taken a priliminary look
through the rdeps and most of the important ones seem
to have updated to at least 0.10 upstream.
So my gut feeling is to start prepari
Version: 0.7.0~beta.2-2
During a rebuild of all packages in unstable, your package failed to build:
This was fixed just before the bug was filed.
Package: rust-fips203-ffi
Version: 0.2.1-4
Severity: serious
rust-fips203-ffi build-depends on an old version of rust-fips203
and it's build-dependencies are no longer
There seem to be updates in upstream git but they don't
seem to be being published on crates.io. Maybe this
package should move
Package: cafeobj
Version: 1.6.0-2
Severity: serious
Justification: rc-policy - packages must be buildable within the same
release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
cafeobj build-depends on sbcl which no longer built on armel and
armhf. Either the package needs to be
Package: nwchem
Version: 7.2.2-2
Severity: serious
Justification: rc-policy - packages must be buildable within the same
release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
nwchem build-depends on libscalapack-openmpi-dev which is no
longer built on 32-bit architectures.
lib
Package: openscad
Version: 2021.01-7
Severity: serious
Justification: rc-policy - packages must be buildable within the same
release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
openscad build-depends on libcgal-qt5-dev which is no longer built by the
cgal source package. It i
Package: gudhi
Version: 3.10.1+dfsg-1
Severity: serious
Justification: rc-policy - packages must be buildable within the same
release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
gudhi build-depends on libcgal-qt5-dev which is no longer built by the
cgal source package. It is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
I am trying to get the new versions of rust-sqlx and
related packages into testing, this is a prerequisite for
getting the new version of rust-base64 into testing.
It's currently blocked b
1 - 100 of 1558 matches
Mail list logo
