Package: gtk4
Version: 4.12.5+dfsg-6
Severity: serious
According to britney, gtk4's udebs are uninstallable.
* ∙ ∙ libgtk-4-1-udeb/amd64 has unsatisfiable dependency
* ∙ ∙ libgtk-4-1-udeb/arm64 has unsatisfiable dependency
* ∙ ∙ libgtk-4-1-udeb/i386 has unsatisfiable dependency
* ∙ ∙
Package: tfortune
Version: 1.0.1-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, tfortune
depends on both liblopsub1 and liblopsub1t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: swtpm-libs
Version: 0.7.1-1.3
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, swtpm-libs still depends
on libglib2.0-0 rather than libglib2.0-0t64. As a result swtpm-tools
is uninstallable on
Package: ruby-xapian
Version: 1.4.22-1
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, ruby-xapian
still depends on libruby3.1 rather than libruby3.1t64.
As a result it is uninstallable on architectures that are
Package: spice-client-gtk
Version: 0.42-2
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
spice-client-gtk still depends on libusbredirhost1 and libusbredirparser1,
rather than the t64 versions of those libraries.
Package: libtrantor1
Version: 1.5.12+ds-1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
libtrantor1 was recently binnmu'd for the time_t transition,
however, despite the binnmu, it still depends on the old libssl3
because said dependency is hardcoded in the source package.
Package: deepin-movie
Version: 5.10.8-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, deepin-movie
still depends on libqt5concurrent5. As a
result it is uninstallable on architectures that are undergoing
the time64 transition
Package: cyrus-imapd
Version: 3.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
cyrus-imapd is failing to build on the architectures affected by the
time_t transition (armel, armhf, several debian-ports architectures)
with the following error.
unit: fatal(Internal
Package: libappmenu-gtk3-parser0
Version: 0.7.6-2.1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libappmenu-gtk3-parser0
depends on both libgtk3-0 and libgtk3-0t64. As a
result it is uninstallable on architectures that are
Package: comet-ms
Version: 2019015+cleaned1-4
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, comet-ms depends
on both libmstoolkit82 and libmstoolkit82t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: chatty
Version: 0.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, chatty depends
on both libpurple0 and libpurple0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition
=medium
+
+ * Non-maintainer upload.
+ * Add missing function declarations.
+ * Fix clean target.
+
+ -- Peter Michael Green Tue, 02 Apr 2024 04:43:46 +
+
librnd (4.1.1-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru librnd-4.1.1/debian/patches/add-missing-function
severity 1067391 serious
thanks
After rebuilding for the time64 transition, bitlbee-facebook depends on
both libglib2.0-0 and libglib2.0-0t64. As a result it is uninstallable on
architectures affected by the time64 transition (armel, armhf and
several unofficial ports).
Package: atomes
Version: 1.1.12+repack-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, atomes depends
on both libgtk-3-0t64 and .libgtk-3-0t64 As a
result it is uninstallable on architectures that are undergoing
the time64
) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add declarations for functions to fix implicit function declaration
+errors.
+
+ -- Peter Michael Green Tue, 02 Apr 2024 02:51:30 +
+
gtk2-engines-murrine (0.98.2-3) unstable; urgency=medium
[ Mike Gabriel ]
diff -Nru
gtk2
Package: aqemu
Version: 0.9.2-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, aqemu still
depends on libqt5dbus5. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some
severity 966249 serious
thanks
That's actually an issue with GDC, it only supports a really old
standard library version currently (will be resolved with GDC 11,
apparently), and supporting multiple standard library versions is a
massive pain. I lowered the issue priority to wishlist, since GDC
severity 1064708 important
Can you explain why you downgraded this bug? it looks rc to me
and is blocking the time_t transition.
It looks like there are two separate issues here.
arm64, ppc64el, riscv64, s390x and ppc64el are failing because
the c type char is unsigned on those platforms, which means the
rust type c_char is an alias for u8 instead of i8. Probably just
needs some casts adjusting.
armel, armhf, i386 and
Package: aegean
Version: 0.16.0+dfsg-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, aegen depends
on both libgenometools0t64 and libgenometools0. As a
result it is uninstallable on architectures that are undergoing
the time64
Package: python-cryptography
Version: 41.0.7-5
Severity: serious
x-debbugs-cc: eam...@debian.org, kapo...@melix.org
python-cryptography build-depends on python3-cryptography-vectors (<<
41.0.8~)
but unstable has version 42.0.5-1
If you need rust package updates to fix this issue, please tell
I partially started to patch gtk3-rs to use the newer glib from
experimental. However, this is not really supported and I'd rather
remove it now that it's EOL. For qwertone we can employ partial
vendoring; this will also need to be done for squeekboard (in progress).
I'd appreciate if you agree
The armhf build complains about Extra-Depends: dpkg-dev (>= 1.22.5),
gcc-13 (>= 13.2.0-16.1), libssl-dev (>= 3.1.5-1.1), but I checked and
all of these exists in armhf, so not sure what is going on.
There is a little more information further down the page.
cargo build-depends on:
- cargo:armel
-maturin (1.3.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax cargo dependency on indexmap.
+
+ -- Peter Michael Green Sun, 11 Feb 2024 03:59:53 +
+
python-maturin (1.3.2-1) unstable; urgency=medium
[ Andreas Tille ]
diff -Nru python-maturin-1.3.2/debian/patches
reopen 1063685
thanks
On 11/02/2024 18:27, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the precious package:
#1063685: precious - upcoming rust-indexmap update.
It has been closed by Debian FTP Masters (reply to
Jonas
/changelog 2024-02-11 01:24:39.0 +
@@ -1,3 +1,10 @@
+precious (0.6.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop 2001_indexnap.patch and update build-depends for indexmap 2.
+
+ -- Peter Michael Green Sun, 11 Feb 2024 01:24:39 +
+
precious (0.6.0-3) unstable
:45.0 +
@@ -1,3 +1,10 @@
+loupe (45.3-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Stop patching indexmap dependency and update build-depends accordingly.
+
+ -- Peter Michael Green Sat, 10 Feb 2024 22:30:45 +
+
loupe (45.3-2) unstable; urgency=medium
* Enable
:21.0 +
@@ -1,3 +1,10 @@
+rust-ahash (0.8.7-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump hasbrown dev-dependency to 0.14.
+
+ -- Peter Michael Green Sat, 10 Feb 2024 21:45:21 +
+
rust-ahash (0.8.7-4) unstable; urgency=medium
* relax to declare most package
Package: settle
Version: 0.40-1-2
I'm currently looking at updating rust-dialoguer, settle is one of
the reverse dependencies.
Looking at the upstream changelog, I don't see anything too
scary and I've done a test build with the dependency bumped
and it built successfully.
I've uploaded the
a more recent version of librust-asn1-dev (>= 0.15) is needed
to be able to update to python3-cryptography (>= 0.41) which
in turn is required by some other package.
I've uploaded the new versions of rust-asn1 and rust-asn1-derive
to experimental, python-cryptography seems to be the only
has multiple versions of toml and the previous dependency could be
+ satisfied by the wrong one.
++ Add a Debian dependency on "dirs" crate (which appeard to simply be
+ missing before.
+
+ -- Peter Michael Green Mon, 01 Jan 2024 18:34:48 +
+
elan (3.0.0-1) un
Package: sccache
Version: 0.7.4-3
I have been working on an update of rust-backtrace and it's
dependencies, backtrace itself is not semver breaking, but
several of it's dependencies are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 ->
Package: rust-ahash
Version: 0.8.5-4
Severity: serious
Thanks for uploading my autopkgtest fixes, the tests now pass on most
architectures.
Unfortunately they still fail on s390x.
290s operations::test::test_add_length stdout
290s thread 'operations::test::test_add_length' panicked
Version 3.4.0-1
Please update to at least v3.4.0.
Done
to 0.18 and bat to 0.24.
+
+ -- Peter Michael Green Sun, 03 Dec 2023 13:41:55 +
+
git-delta (0.16.5-3) unstable; urgency=medium
* mention unrelated but similarly named package and binary executable
diff -Nru git-delta-0.16.5/debian/control git-delta-0.16.5/debian/control
--- git-delta
> Please update to (at least) newer upstream release v0.3.69.
Backtrace itself is not semver breaking, but some of it's dependencies
are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 -> 0.28.1
object 0.31.1 -> 0.32.1
I've uploaded these to
Package: rust-wasmtime
Version: 10.0.1+dfsg-7
I currently working on an update of rust-backtrace and it's
dependencies, backtrace itself is not semver breaking, but
several of it's dependencies are.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli
Package: dgit
(this bug report is a result of a question discussion in IANs tag2upload
talk at the cambridge miniconf 2023)
In the talk Ian made the following points
* the current Salsa approach leads to users accidentlly receiving
patches unapplied git trees
* In a later slide
Package: dwarf2sources
Version: 0.2.1-1
Tags: trixie, sid
I am currently preparing an update of rust-backtrace and related crates.
they have been uploaded to experimental and I hope to upload them
to unstable in the not too distant future.
backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
Package: safe-vdash
I'm currently in the process of preparing updates for crossterm
to 0.27 and ratatui to 0.23.
save-vdash's cargo dependencies already allow the new
versions (indeed the new versions will allow patches to be
dropped) but the Debian dependencies currently do not.
After bumping
Package: btm
I'm currently in the process of preparing updates for crossterm
to 0.27 and ratatui to 0.23.
Btm's dependencies (both cargo and Debian) already allow the
new version of crossterm, but they don't allow the new version
of ratatui. I don't see anything too scary in the upstream
On 19/11/2023 12:14, Peter Michael Green wrote:
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
https
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
It would be nice to remove rust-arrayvec-0.5 to only have one version of
rust-arrayvec in Debian.
We can patch out the arrayvec feature in zvariant-derive-2 to unblock this.
It has no reverse dependencies and is one of the last things keeping
rust-time-0.1 in Debian.
Not speaking for or against removal, but updating it to the latest
version would get rid of the dependency on time 0.1.
-sys (0.4.6-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax dependeny to allow bindgen 0.66.
+
+ -- Peter Michael Green Sun, 03 Sep 2023 14:19:09 +
+
rust-leptonica-sys (0.4.6-2) unstable; urgency=medium
* update DEP-3 patch headers
diff -Nru rust-leptonica-sys
On 03/09/2023 14:58, Peter Michael Green wrote:
The attatched debdiff,
Sorry, really attached nowdiff -Nru rust-laurel-0.5.3/debian/changelog rust-laurel-0.5.3/debian/changelog
--- rust-laurel-0.5.3/debian/changelog 2023-07-18 14:26:32.0 +
+++ rust-laurel-0.5.3/debian/changelog
Package: rust-laurel
Version: 0.5.3-1
In the rust team we are working on upgrading rust-bindgen from 0.60 to
0.66, there are a few reasons for this. Firstly it's part of the
dependency stack
for the new version of rust-cargo. Secondly the version currently in sid
has a
compatibility issue with
Reopen 1050113
thanks
Bumped the hint to 0.101.3-2.
Testing migration was unfortunately interrupted by a security bug.
then some follow-up issues with the new upstream version uploaded
to fix the security bug.
Can you update the hint to 0.101.4-4?
Package: sccache
Version: 0.5.4-11
Severity: serious
Tags: patch
I just updated addr2line to version 0.20.0, sccache builds succesfully
with the new version after bumping the dependency.
Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
---
dependency.
+
+ -- Peter Michael Green Sun, 27 Aug 2023 19:54:23 +
+
rust-async-process (1.7.0-2) unstable; urgency=medium
* update dh-cargo fork;
diff -Nru rust-async-process-1.7.0/debian/control
rust-async-process-1.7.0/debian/control
--- rust-async-process-1.7.0/debian/control 2023
Package: rust-rustls-webpki
Version: 0.101.4-2
Severity serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rustls-webpki/37179484/log.gz
92s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose',
d test dependencies on librust-rcgen-0.11+default-dev (>=
0.11.1-2)
+
+ -- Peter Michael Green Fri, 25 Aug 2023 18:57:05 +
+
rust-rustls-webpki (0.101.4-1) unstable; urgency=high
* bump project version in virtual packages and autopkgtests;
diff -Nru rust-rustls-webpki-0.101.4/d
Package: rust-wasmer-enumset-derive
Version: 0.5.0-2
Severity: serious
Tags: trixie, sid
rust-wasmer-enumset-derive and it's reverse dependency
rust-wasmer-enumset are an abandoned fork of rust-enumset-dervive and
rust-enumset, no applications use them anymore so there is no reason to
keep
Package: rust-leptonica-plumbing
Version: 1.0.1-4
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-leptonica-plumbing/36970458/log.gz
118s The following packages have unmet dependencies:
118s autopkgtest-satdep : Depends: librust-leptonica-plumbing-1.0+default-dev
Package: rust-hyper-rustls
Version: 0.24.1-2
Severity: minor
debian/tests/control in rust-hyper-rustls still refers to rustls 0.20,
even though
the package itself is now using rustls 0.21.
Version: 0.12.0-1
rust-derive-builder has now been updated to match rust-derive-builder-core.
As subject says, this package depends on librust-heapless-0.7-dev which
is missing, rendering the package impossible to install.
I don't see any such dependency, was this a typo.
It does however seem to depend on librust-defmt-0.3+default-dev,
rust-defmt hasn't been uploaded yet, but it seems
will break builds with older versions of the rust gtk stack.
+
+ -- Peter Michael Green Wed, 28 Jun 2023 18:54:50 +
+
squeekboard (1.22.0-2) unstable; urgency=medium
* Release to unstable
diff -Nru squeekboard-1.22.0/debian/control squeekboard-1.22.0/debian/control
--- squeekboard-1.22.0
Package: php-doctrine-cache
Version: 2.2.0-1
Severity: serious
Tags: trixie, sid
php-doctrine-cache build-depends on php-nrk-predis which
was a transitional dummy package in bookworm and no
longer exists in trixie or sid.
Presumablly the build-dependency should be changed to
php-predis.
of librust-pyo3-dev.
+ * Apply adjusted upstream patch for py03 0.19 and bump
+dependencies accordingly.
+
+ -- Peter Michael Green Sun, 25 Jun 2023 00:58:26 +
+
python-cryptography (38.0.4-3) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff -Nru python-cryptography-38.0.4/de
/changelog 2023-02-03 13:57:58.0 +
+++ rust-rustls-0.20.8/debian/changelog 2023-06-18 01:01:18.0 +
@@ -1,3 +1,10 @@
+rust-rustls (0.20.8-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump base64 dev-dependency to 0.21.
+
+ -- Peter Michael Green Sun, 18 Jun 2023
On 23/04/2023 21:07, Paul Gevers wrote:
Can you point to a discussion where we might draw the conclusion that
this is common practice or consensus? I *personally* [no hats on] find
that distinction a bit weird although I can see how we would come to
it and also why.
No, I can't point to a
On 23/04/2023 19:19, Paul Gevers wrote:
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual updating. Instead of
hard-coding the list, it's better to ensure the build doesn't happen
or fails on architectures where python3-sage is not
reassign 1034723 rust-h2
thanks
The following vulnerability was published for rust-hyper.
CVE-2023-26964[0]:
|/An issue was discovered in hyper v0.13.7. h2-0.2.4 Stream stacking /|/occurs
when the H2 component processes HTTP2 RST_STREAM frames. As a /|/result, the
memory and CPU usage are
Package: dgit
dget -d http://deb.debian.org/debian/pool/main/g/git/git_2.39.2-1.1.dsc
mkdir dgittest
cd dgittest
git init
dgit import-dsc ../git_2.39.2-1.1.dsc +workingbranch
results in.
Dgit metadata in .dsc: specified git info (debian)
dgit: import-dsc of .dsc with Dgit field, using git hash
.
+
+ [ Jochen Sprickerhof ]
+ * Add patch to fix FTBFS on i386.
+Thanks to Adrian Bunk (Closes: 1004869)
+ * Use execute_after_ in d/rules
+ * Set R³ in d/control
+
+ -- Peter Michael Green Sun, 19 Feb 2023 00:50:57 +
+
python-xarray (2023.01.0-1) unstable; urgency=medium
* Mew
On 09/02/2023 23:43, Michele Martone wrote:
On 20230209@17:50, Peter Green wrote:
Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags:
Please consider enabling feature socks now: Package rust-socks is now in Debian.
The socks feature of rust-reqwest depends on the tokio-socks crate, not the
socks
crate.
Package: pushpin
Version: 1.36.0-1
Severity: serious
The new version of pushpin added a dependency on jsonwebtoken,
unfortunately jsonwebtoken depends in ring, which is only available
on x86* and arm*. There is work upstream to make ring more
portable but it seems unlikely to feature in a stable
Package: rust-debcargo
I've attached a patch which makes debcargo build with clap 4, debcargo
builds and it's cargo tests run succesfully, but I haven't actually done any
testing of the command line interface with this patch.
Fabian and I have agreed on irc that it probablly doesn't make sense
Package: cctbx
Version: 2022.9+ds2+~3.11.2+ds1-5
Severity: serious
Despite the fix uploaded for bug 1024859 the cctbx autopkgtest is still
failing
and preventing the package from migrating to testing.
Testing cctbx with python3.10:
Sorry: Please run this program in an empty directory.
Source: commons-vfs
Version: 2.1-2
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
commons-vfs build-depends on libcommons-net-java-doc which
is no longer built
-maintainer upload.
+ * Depend on librust-zip-0.6-dev instead of rust-zip-0.5-dev
+
+ -- Peter Michael Green Wed, 28 Dec 2022 16:57:19 +
+
sccache (0.4.0~~pre1-1) unstable; urgency=medium
[ upstream ]
diff -Nru sccache-0.4.0~~pre1/debian/control sccache-0.4.0~~pre1/debian/control
--- sccache
> Please upgrade to newer upstream release v7.3.2.
dkg - do you have an opinion on this? I see you updated this package
to 6.x a few months ago and added yourself as an uploader,
presumably in support of some packaging effort, but without
knowing what you were packaging, I can't tell if the
Package: ruby-aruba
Version: 2.1.0-1
Severity: serious
Justification: rc policy - "Packages must be buildable within the same release"
User:debian...@lists.debian.org
Usertags: edos-uninstallable
ruby-aruba build-depends on rubocop (<< 1.0) but bookworm and sid have version
1.39.0+dfsg-1
On 15/11/2022 20:52, Peter Green wrote:
Please upgrade to v0.6, needed by projects I am preparing for Debian.
Unfortunately upstream do not seem to provide a changelog.
There seem to be three reverse dependencies, elan, rust-grcov and
rust-coreutils.
And since this message was written,
Package: obantoo
Version: 2.1.12+ds1-3
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
obantoo build-depends on libitext5-java-doc which is no longer built
by the libitext5-java
I've prepared an upload of verion 0.17 of pyo3 and built/tested breezy
with it. It built successfully the autopkgtest passed. Any objections if
I go ahead and update to this version?
Package: ntcard
Version: 1.2.2+dfsg-4
Severity: serious
ntcard build-depends on libnthash-dev which is no longer available on
32-bit architectures.
There are in general 3 potential soloutions for this (in roughly
descending order of preference)
1. Fix your build-dependencies so they are
Package: pplacer
version: 1.1~alpha19-6
Severity: serious
Justification: rc policy: "packages must be buildable within the same
release"
pplacer build-depends on libmcl-ocaml-dev which is no longer built by the
mcl source package. It is still present in unstable as a cruft package, but
is
Please upgrade to newer upstream branch v0.11.
The new version depends on rust-derive-builder-macro which is not
currently in Debian.
Package: rust-wasmer-enumset
rust-wasmer-enumset and it's support crate rust-wasmer-enumset-derive
are a fork of the enumset/enumset-derive crates to fix a specific issue.
The issue has now been fixed in the enumset crates and the
wasmer-enumset crates are unmaintained
The only
Package: rust-coreutils
Version: 0.0.15-1
Severity: serious
cargo build --features "arch base32 base64 basename basenc cat chcon
chgrp chmod chown chroot cksum comm cp csplit cut date dd df dir
dircolors dirname du echo env expand expr factor false fmt fold groups
hashsum head hostid
Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1
Serverity: serious
Tags: bookworm, sid
tt-rss build-depends on libjs-prototype (= 1.7.1-3.1) but
testing/unstable has version 1.7.3-1
Package: rust-smol
Version: 1.2.5-2
Severity: serious
rust-smol build-depends on librust-nix-0.24+default-dev but the nix
crate in debian testing/unstable is now at 0.25
There is a new upstream version of petgraph that uses the new version of
fixedbitset, I suspect the most sensible way to fix this bug is
uploading it and it has been prepared in debcargo-conf (initially
byBlair Noctis with some further tweaking by myself)
However before I upload it, I wanted
Package: rust-ahash
Version: 0.7.6-4
Severity: serious
The autopkgtest of rust-ahash is failing
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ahash/25673987/log.gz
Testing aeshash/u8
thread 'main' panicked at 'aes must be enabled', tests/bench.rs:20:5
stack backtrace:
0:
I have written a merge request [1] to fix FTBFS on all platforms. Tested on my
dev machine on amd64 and riscv64. If more helps are needed, please let me know.
Thanks for the patch,
Was this patch just a result of general QA activity or is there some
program you are trying to package?
We can
severity 998306 serious
thanks
I have uploaded rust-backtrace and related packages to experimental for now.
rust-backtrace and related packages have now been uploaded to unstable,
bumping to serious.
Package: debcargo
Version: 2.5.0-3
Alexander Kjäll was working on packaging wl-clipboard-rs when he ran
into an autopkgtest failure.
debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
Package: orthanc-dicomweb
Version: 1.7+dfsg-5
The build-dependencies of orthanc-dicomweb are not satisfiable on armel
package: orthanc-dicomweb
version: 1.7+dfsg-5
architecture: any
type: src
status: broken
reasons:
-
missing:
pkg:
package: node-ms
version:
dependencies on gettext-sys, gettext-rs and proptest crates.
+(Closes: #1011620, #1013539)
+
+ -- Peter Michael Green Sat, 16 Jul 2022 19:13:03 +
+
newsboat (2.21-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru newsboat-2.21/debian/control newsboat-2.21/debian/control
reassign 1014663 vkd3d 1.2-13
thanks
vk3d's build-dependencies are unsatisfible on most architectures,
because debian/control was not updated to reflect the new version number.
Sorry messed up the package name, it's vkd3d not vk3d
Package: vk3d
version: 1.2-13
vk3d's build-dependencies are unsatisfible on most architectures,
because debian/control was not updated to reflect the new version number.
There seems to be a group of 4 closely related packages, zbus,
zbus-macros, zvariant and zvariant-derive which
should probably be upgraded in lockstep.
2.x (3.x for zvariant) is a semver break, so reverse dependencies need
to be investigated.
rust-ashpd - fixed upstream, upstream fix
The rust-zstd package has both a dependency and a build-dependency on
librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in
Debian. Presumably it would be built by a rust-zstd-safe package, but no
such package exists, including in the Debian NEW queue.
Specifically looking
Package: deepin-movie
Version: 5.7.15-3
Severity: serious
The deepin-movie-reborn source package was recently binnmu'd for the
ffmpeg transtion,
unfortunately though the resulting binary packages still depend on the
old libav* packages.
I just uploaded new package rust-common-failures now sitting in NEW, but
then realized that rust-failure which it depends on is removed from
Debian (see bug#973298).
Please drop rust-common-failures from NEW queue - it is useless.
This is not entirely correct, rust-failure was indeed removed
Package: rust-hdrhistogram
Version: 7.5.0-1
Severity: serious
I recently updated the hdrhistogram package and as part of that I
resolved the issues that were blocking the tests from running on as
autopkgtests.
Unfortunately when running the autopkgtests on i386 two tests failed, I
can also
1 - 100 of 184 matches
Mail list logo
