Bug#1068221: comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures.
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 time64 transition (armel, armhf and some debian-ports archictures).
Bug#1068219: chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.
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 (armel, armhf and some debian-ports archictures).
Bug#1066248: librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=implicit-function-declaration]
tags 1066248 +patch thanks The functions in question are defined in src/librnd/plugins/hid_lesstif/dialogs.c and used in src/librnd/plugins/hid_lesstif/main.c My first attempt at fixing the issue was to declare the functions in dialogs.h and include dialogs.h in main.c, however doing so caused errors with conflicting type definitions, so I just defined them directly in main.c instead. while working on this issue I discovered that the clean target was not cleaning up properly, so I fixed that too. A debdiff is attatched. Review and upload would be appreciated since this blocks the time_t transition diff -Nru librnd-4.1.1/debian/changelog librnd-4.1.1/debian/changelog --- librnd-4.1.1/debian/changelog 2024-02-28 17:20:34.0 + +++ librnd-4.1.1/debian/changelog 2024-04-02 04:43:46.0 + @@ -1,3 +1,11 @@ +librnd (4.1.1-1.2) UNRELEASED; urgency=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-declaration.patch librnd-4.1.1/debian/patches/add-missing-function-declaration.patch --- librnd-4.1.1/debian/patches/add-missing-function-declaration.patch 1970-01-01 00:00:00.0 + +++ librnd-4.1.1/debian/patches/add-missing-function-declaration.patch 2024-04-02 04:42:54.0 + @@ -0,0 +1,14 @@ +Index: librnd-4.1.1/src/librnd/plugins/hid_lesstif/main.c +=== +--- librnd-4.1.1.orig/src/librnd/plugins/hid_lesstif/main.c librnd-4.1.1/src/librnd/plugins/hid_lesstif/main.c +@@ -51,6 +51,9 @@ + + #include + ++void lesstif_attr_dlg_free_all(void); ++void lesstif_attr_sub_update_hidlib(void *hid_ctx, rnd_design_t *new_dsg); ++ + const char *lesstif_cookie = "lesstif HID"; + + rnd_design_t *ltf_hidlib; diff -Nru librnd-4.1.1/debian/patches/series librnd-4.1.1/debian/patches/series --- librnd-4.1.1/debian/patches/series 2024-01-13 09:12:54.0 + +++ librnd-4.1.1/debian/patches/series 2024-04-02 04:21:58.0 + @@ -0,0 +1 @@ +add-missing-function-declaration.patch diff -Nru librnd-4.1.1/debian/rules librnd-4.1.1/debian/rules --- librnd-4.1.1/debian/rules 2024-01-13 09:12:54.0 + +++ librnd-4.1.1/debian/rules 2024-04-02 04:43:46.0 + @@ -21,6 +21,10 @@ override_dh_auto_clean: # only try to run dh_auto_clean if configure has been run test -f Makefile.conf && dh_auto_clean || true + find . -name *.o -delete + find . -name *.so.* -delete + rm -f scconfig/aru + rm -f doc/conf/tree/editor_global_grid.html doc/conf/tree/editor_local_grid.html src/librnd/plugins/lib_hid_gl/draw_INIT.h src/librnd/poly/polyconf.h src/librnd/polybool/polyconf.h override_dh_auto_configure: ./configure \
Bug#1068217: atomes, dependencies unsatisfiable on 32-bit non-i386 architectures.
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 transition (armel, armhf and some debian-ports archictures). This applies to both versions 1.1.12+repack-2 and 1.1.14-1
Bug#1066392: gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error: implicit declaration of function ‘murrine_widget_is_ltr’; did you mean ‘murrine_widget_is_rgba’? [-Werror=implicit-functi
tags 1066392 +patch thanks I've whipped up a patch that adds the missing function declarations to the headers. Review and upload would be appreciated as this is needed for the time64 transition (and is a key package, so can't simply be autoremoved). diff -Nru gtk2-engines-murrine-0.98.2/debian/changelog gtk2-engines-murrine-0.98.2/debian/changelog --- gtk2-engines-murrine-0.98.2/debian/changelog2019-11-18 08:32:18.0 + +++ gtk2-engines-murrine-0.98.2/debian/changelog2024-04-02 02:51:30.0 + @@ -1,3 +1,11 @@ +gtk2-engines-murrine (0.98.2-3.1) 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-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch --- gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch 1970-01-01 00:00:00.0 + +++ gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch 2024-04-02 02:51:30.0 + @@ -0,0 +1,31 @@ +Description: Add declarations for functions to fix implicit function declaration errors. +Author: Peter Michael Green + +--- gtk2-engines-murrine-0.98.2.orig/src/murrine_rc_style.h gtk2-engines-murrine-0.98.2/src/murrine_rc_style.h +@@ -155,4 +155,6 @@ struct _MurrineRcStyleClass + + GType murrine_rc_style_get_type (void); + ++void murrine_rc_style_register_types (GTypeModule *module); ++ + #endif /* MURRINE_RC_STYLE_H */ +--- gtk2-engines-murrine-0.98.2.orig/src/murrine_style.h gtk2-engines-murrine-0.98.2/src/murrine_style.h +@@ -102,5 +102,6 @@ struct _MurrineStyleClass + }; + + GType murrine_style_get_type (void); ++void murrine_style_register_types (GTypeModule *module); + + #endif /* MURRINE_STYLE_H */ +--- gtk2-engines-murrine-0.98.2.orig/src/support.h gtk2-engines-murrine-0.98.2/src/support.h +@@ -149,4 +149,7 @@ G_GNUC_INTERNAL void murrine_get_noteboo + gboolean *start, + gboolean *end); + ++gboolean murrine_object_is_a (const GObject * object, const gchar * type_name); ++gboolean murrine_widget_is_ltr (GtkWidget *widget); ++ + #endif /* SUPPORT_H */ diff -Nru gtk2-engines-murrine-0.98.2/debian/patches/series gtk2-engines-murrine-0.98.2/debian/patches/series --- gtk2-engines-murrine-0.98.2/debian/patches/series 2019-11-12 09:31:57.0 + +++ gtk2-engines-murrine-0.98.2/debian/patches/series 2024-04-02 02:51:30.0 + @@ -1,2 +1,3 @@ 02_fix-linking-lm.patch pango_cairo_update_layout.patch +add-missing-function-declarations.patch
Bug#1068216: aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.
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 debian-ports archictures).
Bug#1068178: aegean, dependencies unsatisfiable on 32-bit non-i386 architectures.
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 transition (armel, armhf and some debian-ports archictures).
Bug#1068047: marked as pending in libarchive
Control: tag -1 pending Hello, Bug #1068047 in libarchive 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/debian/libarchive/-/commit/31fcf28c3be82824c34dd115c7465748adb2b787 Add the robust-error-reporting upstream patch Closes: #1068047 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068047
Bug#1067906: qtwebengine-opensource-src - FTBFS on armhf.
Package: qtwebengine-opensource-src Version: 5.15.15+dfsg-2 Severity: serious qtwebengine-opensource-src failed to build on armhf when binnmu'd for the time_t transition due to symbol changes. (qtwebengine does not support any of the other architectures affected by the time64 transition. grep MISSING qtwebengine-opensource-src.log | grep -v optional +#MISSING: 5.15.15+dfsg-2+b3# _ZN15QtWebEngineCore14ProfileAdapter21determineDownloadPathERK7QStringS3_RKl@Qt_5 5.14.1 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox18localtime_overrideEPKl@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime64_overrideEPKl@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime_r_overrideEPKlP2tm@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox22localtime64_r_overrideEPKlP2tm@Qt_5 5.12.2
Bug#1067898: atril, dependencies unsatisfiable on 32-bit non-i386 architectures.
Package: atril Version: 1.26.2-2 Severity: serious The latest version of atril depends on both libatrildocument3 and libatrildocument3t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports archictures).
Bug#1067897: rust-coreutils - FTBFS with new rust-uutils-term-grid.
Package: rust-coreutils
Version: 0.0.24-2
Severity: serious
rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.
After bumping the cargo dependency, the code fails to build with a
bunch of errors.
error[E0432]: unresolved import `term_grid::Cell`
--> src/uu/ls/src/ls.rs:37:17
|
37 | use term_grid::{Cell, Direction, Filling, Grid, GridOptions};
| no `Cell` in the root
|
= help: consider importing one of these items instead:
std::cell::Cell
core::cell::Cell
error[E0063]: missing field `width` in initializer of `GridOptions`
--> src/uu/ls/src/ls.rs:2598:34
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
| ^^^ missing `width`
error[E0061]: this function takes 2 arguments but 1 argument was supplied
--> src/uu/ls/src/ls.rs:2598:24
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
|^ -- an
argument of type `Vec<_>` is missing
error[E0599]: no method named `add` found for struct `Grid` in the current scope
--> src/uu/ls/src/ls.rs:2609:18
|
2609 | grid.add(formatted_name);
| ^^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_width` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2612:20
|
2612 | match grid.fit_into_width(width as usize) {
|^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_columns` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2618:40
|
2618 | write!(out, "{}", grid.fit_into_columns(1))?;
| method not found in
`Grid<_>`
Bug#1066794: consider retrying git binnmus.
git failed to build when binnmu'd for the time64 transition and also in lucas's test build a few days earlier. This was filed as bug 1066794. Andrey Rakhmatullin responded to the bug report saying he was unable to reproduce the failure. Michael Hudson replied with a post suggesting that the failure may be related to libcgi-pm-perl, though he did not make it clear which version of libcgi-pm-perl he was testing with. Andrey noted that the version of libcgi-pm-perl in his local tests was newer than the version used in the failed builds. Ubuntu temporally disabled tests in git, but have since re-enabled them, and the package built successfully on all Ubuntu architectures. I would suggest therefore that it makes sense to retry the binnmus as there is a good chance that whatever caused the issue has since been fixed.
Bug#1067709: FTBFS in armel/armhf: some symbols disappeared
Control: tag -1 + confirmed On Tue, Mar 26, 2024 at 01:29:08AM +0500, Andrey Rakhmatullin wrote: > Source: dante > Version: 1.4.3+dfsg-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=dante&arch=armhf&ver=1.4.3%2Bdfsg-1&stamp=1710761774&raw=0 Thanks for reporting this. I noticed it as soon as I uploaded this version of dante, and I started looking into it; it is, at least partly, fallout from the new "implicit function declarations are errors" GCC option setting. FTR, I believe this is a good idea, no complaints here. However, it turns out to be a bit more complicated than sprinkling a couple of #include directives here and there; I will hopefully be able to upload a fixed version within the next couple of days. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1067027: python-cryptography build-dependencies unsatisfiable.
On 17/03/2024 13:01, Jérémy Lal wrote: The last missing piece seems to be version >= 3 of https://tracker.debian.org/pkg/rust-pem I've uploaded this to experimental, please tell me when you are ready for it to be uploaded to unstable.
Bug#1067027: python-cryptography build-dependencies unsatisfiable.
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 me what they are and I will see what I can do. This is blocking the time64 transition for python-cryptography.
Bug#1067010: libsquashfuse-dev: Incompatible pointer types on 32-bit architectures
Package: libsquashfuse-dev
Version: 0.5.0-2
Severity: serious
Tags: ftbfs fixed-upstream
Affects: src:charliecloud
Dear Maintainer,
squashfuse suffers from an incompatible pointer type issue on 32-bit
architectures. Checking the latest build logs for armel, armhf and
i386 ([0], [1], [2]) one finds the following warning:
ll_main.c: In function ‘main’:
ll_main.c:164:41: warning: assignment to ‘void (*)(struct fuse_req *,
fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned
int, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct
fuse_req *, fuse_ino_t, long unsigned int)’ {aka ‘void (*)(struct fuse_req *,
long long unsigned int, long unsigned int)’} [-Wincompatible-pointer-types]
164 | sqfs_ll_ops.forget = sqfs_ll_op_forget;
| ^
This incompatibility leads to an FTBFS issue for the charliecloud
package on 32-bit architectures (see e. g. [3]) since it is built
using the -Werror option.
It seems that this issue was fixed in upstream release 0.5.1 [4].
More background information on this issue can be obtained from the
corresponding Charliecloud upstream issue and PR ([5], [6]).
Best regards,
Peter
[0]
https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=armel&ver=0.5.0-2%2Bb1&stamp=1707534165&raw=0
[1]
https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=armhf&ver=0.5.0-2%2Bb1&stamp=1707538322&raw=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=i386&ver=0.5.0-2%2Bb1&stamp=1707537260&raw=0
[3]
https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armel&ver=0.37-2&stamp=1710594551&file=log
[4]
https://github.com/vasi/squashfuse/commit/cb148fc1477ed676049b7891ebb6efc90b2c00ec
[5] https://github.com/hpc/charliecloud/issues/1858
[6] https://github.com/hpc/charliecloud/pull/1859
Bug#1065793: charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int,
Control: reopen -1 It seems that the patch uploaded with 0.37-2 does not fix this issue. See https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armel&ver=0.37-2&stamp=1710594551&file=log and https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armhf&ver=0.37-2&stamp=1710594414&file=log Therefore I reopen this bug. Best regards, Peter
Bug#1066972: [Pkg-rust-maintainers] Bug#1066972: rust-python-pkginfo: FTBFS on mips64el: missing librust-rfc2047-decoder-0.2+default-dev
severity 1066972 important thanks Indeed, there is no librust-rfc2047-decoder-0.2+default-dev package. librust-rfc2047-decoder-0.2+default-dev is a virtual package provided by librust-rfc2047-decoder-dev which is built from the rust-rfc2047-decoder source package. Following the dependency chain, it looks like the root cause (or at least one of the root causes) is that the testsuite for rust-stacker is segfaulting on mips64el.
Bug#1065793: marked as pending in charliecloud
Control: tag -1 pending
Hello,
Bug #1065793 in charliecloud 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/hpc-team/charliecloud/-/commit/5b9e616161bc9b2651081434b5fa5b017fdbc885
Add patch from upstream PR 1859 to fix FTBFS issue on arm{el,hf}
Closes: #1065793
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1065793
Bug#1066866: railway-gtk: FTBFS on i386 "type annotations needed"
Package: railway-gtk
Version: 2.4.0-1
Severity: serious
railway-gtk FTBFS on i386 (and will probablly FTBFS on other
32-bit architectures but builds on those architectures are
currently blocked by the time64 transition).
error[E0283]: type annotations needed for `std::option::Option`
--> src/backend/journeys_result.rs:207:17
|
207 | let index = list
| ^
...
215 | if position <= index && index < position + n_items {
| -- type must be known at this point
|
= note: multiple `impl`s satisfying `u32: PartialOrd<_>` found in the
following crates: `core`, `glib`:
- impl PartialOrd for u32;
- impl PartialOrd for u32;
help: consider giving `index` an explicit type, where the placeholders `_` are
specified
|
207 | let index: std::option::Option = list
|
Looking at the code, I'm pretty confident that the intended type was
Option. The attached debdiff adds the annotation. I have tested
that railway-gtk builds succesfully with this patch on both i386
and amd64.diff -Nru railway-gtk-2.4.0/debian/changelog railway-gtk-2.4.0/debian/changelog
--- railway-gtk-2.4.0/debian/changelog 2024-03-04 13:13:51.0 +
+++ railway-gtk-2.4.0/debian/changelog 2024-03-14 16:10:58.0 +
@@ -1,3 +1,10 @@
+railway-gtk (2.4.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with "type annotation needed" error on i386.
+
+ -- Peter Michael Green Thu, 14 Mar 2024 16:10:58 +
+
railway-gtk (2.4.0-1) unstable; urgency=medium
* New upstream release
diff -Nru railway-gtk-2.4.0/debian/patches/add-type-annotation.patch
railway-gtk-2.4.0/debian/patches/add-type-annotation.patch
--- railway-gtk-2.4.0/debian/patches/add-type-annotation.patch 1970-01-01
00:00:00.0 +
+++ railway-gtk-2.4.0/debian/patches/add-type-annotation.patch 2024-03-14
16:10:58.0 +
@@ -0,0 +1,13 @@
+Index: railway-gtk-2.4.0/src/backend/journeys_result.rs
+===
+--- railway-gtk-2.4.0.orig/src/backend/journeys_result.rs
railway-gtk-2.4.0/src/backend/journeys_result.rs
+@@ -204,7 +204,7 @@ mod imp {
+ let list = self.journeys.borrow();
+ let selection = self.selected.borrow();
+
+-let index = list
++let index: Option = list
+ .iter()
+ .position(|j| {
+ j.refresh_token() == selection.as_ref().and_then(|j|
j.refresh_token())
diff -Nru railway-gtk-2.4.0/debian/patches/series
railway-gtk-2.4.0/debian/patches/series
--- railway-gtk-2.4.0/debian/patches/series 2024-03-04 13:13:51.0
+
+++ railway-gtk-2.4.0/debian/patches/series 2024-03-14 16:10:14.0
+
@@ -1,3 +1,4 @@
relax-deps.diff
disable-cargo-home-meson-build.diff
build-set-project-name-to-railway-gtk.patch
+add-type-annotation.patch
Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
On 07/03/2024 19:43, Peter Green wrote: In raspbian, I removed the reference from misfortune.cabel, removed the build-dependencies on libghc-regex-pcre* and also (for unrelated reasons) removed the build-dependency on ghc-doc. After doing so I was able to successfully build the package. Scratch that, I thought the build had finished, but it hadn't. It did in fact fail. The reference in the code to PCRE was in all caps which is why my grep did not find it.
Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
Can you please investigate the situation and figure out how to resolve it? I'm no haskell expert, but to me the dependency looks vestigal. Grepping the source tree for "pcre" finds a mention in the misfortune.cabal file but no mentions in the actual code, and there are no corresponding binary dependencies. In raspbian, I removed the reference from misfortune.cabel, removed the build-dependencies on libghc-regex-pcre* and also (for unrelated reasons) removed the build-dependency on ghc-doc. After doing so I was able to successfully build the package.
Bug#1063601: tailspin: FTBFS: error[E0407]: method `backtrace` is not a member of trait `Error`
reassign 1063601 tailspin 3.0.0+dfsg-1
retitle 1063601 tailspin FTBFS error: environment variable `CARGO_CHANNEL` not
defined at compile time
thanks
>> [eyre 0.6.8] error[E0407]: method `backtrace` is not a member of trait
`Error`
>> [eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:19:9
The above seems like a failure not in tailspin but in librust-eyre-dev.
I don't think the errors Sebastian quoted are the cause of the build failure
at all. I think they are just noise from a test compilation performed to
determine what the compiler supports. Those same errors are present
in the successful build log for tailspin 2.0.0
The actual error seems to be.
error: environment variable `CARGO_CHANNEL` not defined at compile time
--> tests/utils.rs:11:48
|
11 | PathBuf::from(format!("./target/{}/tspin", env!("CARGO_CHANNEL")))
|^
|
= help: Cargo sets build script variables at run time. Use
`std::env::var("CARGO_CHANNEL")` instead
= note: this error originates in the macro `env` (in Nightly builds, run
with -Z macro-backtrace for more info)
I also notice the following earlier in the build log.
"debian cargo wrapper: WARNING: falling back to simply calling upstream cargo,
because CARGO_HOME does not end with debian/cargo_home:"
This message appears in the failed logs for 3.0.0 but not in the succesful logs
for 2.0.0.
After serching for CARGO_CHANNEL I think may be the actual cause of the failure.
All the results on codesearch.debian.net for CARGO_CHANNEL seem to relate to
dh_cargo
or your fork thereof. So I think these are probablly related.
Bug#1063879: linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18
-5 ii firmware-intel-sound 20230210-5 pn firmware-intelwimax ii firmware-ipw2x00 20230210-5 ii firmware-ivtv 20230210-5 ii firmware-iwlwifi 20230210-5 ii firmware-libertas 20230210-5 ii firmware-linux-nonfree 20230210-5 ii firmware-misc-nonfree 20230210-5 ii firmware-myricom 20230210-5 ii firmware-netxen 20230210-5 ii firmware-qlogic 20230210-5 ii firmware-realtek 20230210-5 ii firmware-samsung 20230210-5 ii firmware-siano 20230210-5 ii firmware-ti-connectivity 20230210-5 pn xen-hypervisor -- no debconf information -- Peter Hyman
Bug#1061034: Re Bug#1061034
While Lazarus release (3.0+dfsg1-6) fixed the immediate problem of ideconfig.lpk missing, lazbuilds still all fail, now with "Note: (lazarus) Invalid Package Link: file "/usr/lib/lazarus/3.0/ide/packages/idedebugger/idedebugger.lpk" does not exist." Builds fail on the firts missing (lazarus) package. Providing idedebugger.lpk alone may not be sufficient to fix builds lazarus packages fail to build unless lazarus_src is included in build depends. Affects c-evo-dh, ddrescueview, view3dscene, winff, doublecmd
Bug#1024830: ERROR: Unable to connect to servers to test latency.
Hi, speedtest-cli 2.1.3-2 works for me on Bookworm. Best regards, Peter
Bug#1061120: rust-ahash-0.7 autopkgtest failure
Package: rust-ahash-0.7
Version: 0.7.7-1
Severity: serious
The autopkgtests for rust-ahash-0.7 are failing, this is blocking the
migration of rust-ahash-0.7 to testing which is in turn blocking the
migration of at least one rc bug fix to testing.
There are two issues, the first is that the autopkgtests are trying
to test a "runtime-rng" feature, but no such feature exists. My guess
is that there was some confusion between versions of ahash. I removed
the tests and the corresponding provides.
The second issue is more subtle. The "atomic-polyfill" feature
enables the dependency on the atomic-polyfill crate. However the
dependency on the atomic-polyfill crate is disabled on linux
(among many other targets). Disabling of a dependency on a target
overrides enabling the dependency in a feature. However the code
is not aware of this. The result is that building on Linux with
the atomic-polyfill feature enabled fails.
I see three possible routes for dealing with this.
1. Add target guards to the imports in the code, matching those
in Cargo.toml
2. Remove the target restrictions from the atomic-polyfill dependency
3. Simply accept that the atomic-polyfill feature is broken on linux
and stop testing it (this would also mean not having an "all features"
test.
My patch implements the first option but I don't have a strong
preference for any of them.
diff -Nru rust-ahash-0.7-0.7.7/debian/changelog
rust-ahash-0.7-0.7.7/debian/changelog
--- rust-ahash-0.7-0.7.7/debian/changelog 2023-12-30 10:22:55.0
+
+++ rust-ahash-0.7-0.7.7/debian/changelog 2024-01-18 17:11:34.0
+
@@ -1,3 +1,13 @@
+rust-ahash-0.7 (0.7.7-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtests
++ Remove provides and autopkgtests for feature runtime-rng which does not
+ exist.
++ Only import atomic-polyfill on platforms where the dependency is enabled
+
+ -- Peter Michael Green Thu, 18 Jan 2024 17:11:34 +
+
rust-ahash-0.7 (0.7.7-1) unstable; urgency=medium
[ upstream ]
diff -Nru rust-ahash-0.7-0.7.7/debian/control
rust-ahash-0.7-0.7.7/debian/control
--- rust-ahash-0.7-0.7.7/debian/control 2023-12-30 10:18:50.0 +
+++ rust-ahash-0.7-0.7.7/debian/control 2024-01-18 17:11:27.0 +
@@ -40,7 +40,6 @@
librust-ahash-0.7+atomic-polyfill-dev (= ${binary:Version}),
librust-ahash-0.7+compile-time-rng-dev (= ${binary:Version}),
librust-ahash-0.7+default-dev (= ${binary:Version}),
- librust-ahash-0.7+runtime-rng-dev (= ${binary:Version}),
librust-ahash-0.7+serde-dev (= ${binary:Version}),
librust-ahash-0.7+std-dev (= ${binary:Version}),
librust-ahash-0.7.7-dev (= ${binary:Version}),
diff -Nru rust-ahash-0.7-0.7.7/debian/patches/1002_atomic_polyfill.patch
rust-ahash-0.7-0.7.7/debian/patches/1002_atomic_polyfill.patch
--- rust-ahash-0.7-0.7.7/debian/patches/1002_atomic_polyfill.patch
1970-01-01 00:00:00.0 +
+++ rust-ahash-0.7-0.7.7/debian/patches/1002_atomic_polyfill.patch
2024-01-18 17:11:34.0 +
@@ -0,0 +1,23 @@
+Description: limit atomic-polyfill import architectures
+ The atomic-polyfill dependency is target limited, but the import
+ is not. This leads to import errors when building with the
+ atomic-polyfill feature enabled (or building with --all-features).
+
+ This patch makes the imports reflect the dependency
+Author: Peter Michael Green
+Last-Update: 2024-01-18
+
+--- rust-ahash-0.7-0.7.7.orig/src/random_state.rs
rust-ahash-0.7-0.7.7/src/random_state.rs
+@@ -29,9 +29,9 @@ extern crate alloc;
+ #[cfg(feature = "std")]
+ extern crate std as alloc;
+
+-#[cfg(feature = "atomic-polyfill")]
++#[cfg(all(feature = "atomic-polyfill",not(any(target_os = "linux", target_os
= "android", target_os = "windows", target_os = "macos", target_os = "ios",
target_os = "freebsd", target_os = "openbsd", target_os = "netbsd", target_os =
"dragonfly", target_os = "solaris", target_os = "illumos", target_os =
"fuchsia", target_os = "redox", target_os = "cloudabi", target_os = "haiku",
target_os = "vxworks", target_os = "emscripten", target_os = "wasi"]
+ use atomic_polyfill as atomic;
+-#[cfg(not(feature = "atomic-polyfill"))]
++#[cfg(not(all(feature = "atomic-polyfill",not(any(target_os = "linux",
target_os = "android", target_os = "windows", target_os = "macos", target_os =
"ios", target_os = "freebsd", target_os = "openbsd", target_os = "netbsd",
target_os = "dragonfly", target_os = "solaris", target_os = "illumos",
target_os = "fuchsia", target_os = "redox", target_os = "cloudabi", targe
Bug#1058286: marked as pending in ncrack
Control: tag -1 pending Hello, Bug #1058286 in ncrack 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/pkg-security-team/ncrack/-/commit/f4d07967032a4c9142532857b2d7b09f2ef7dc49 Allow zlib versions with two-part version number (Closes: #1058286) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058286
Bug#1059812: elan - dependency updates.
Package: elan Version: 3.0.0-1 Severity: serious I just updated the rust-term package, from 0.5 to 0.7 as a result elan needs to stop patching it's cargo dependency on term and update it's Debian build-dependency. While doing test builds I noticed a couple of other dependency issues. The Debian build-dependency for the toml crate was not strict enough, debian currently ships two versions of the toml crate and only the wrong one was installed in my test environment resulting in a build failure. So I tightened the dependency to only allow the correct one. The package has a cargo dependency on the "dirs" crate, but there was no corresponding Debian build-dependency. I presume it was missed because it was previously pulled in indirectly but this was no longer the case in my tests. So I added a Debian build-dependency. A debdiff is attached. If I get no response I'll probablly NMU this in a week or so.diff -Nru elan-3.0.0/debian/changelog elan-3.0.0/debian/changelog --- elan-3.0.0/debian/changelog 2023-09-26 19:22:31.0 + +++ elan-3.0.0/debian/changelog 2024-01-01 18:34:48.0 + @@ -1,3 +1,17 @@ +elan (3.0.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Dependency updates/fixes: ++ Stop patching Cargo dependency on "term" crate and update Debian + dependency accordingly. Debian has now updated to term 0.7 ++ Be more specific in Debian dependency for "toml" crate, Debian currently + 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) unstable; urgency=medium * Fix "FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build diff -Nru elan-3.0.0/debian/control elan-3.0.0/debian/control --- elan-3.0.0/debian/control 2023-09-26 19:19:14.0 + +++ elan-3.0.0/debian/control 2024-01-01 18:34:48.0 + @@ -19,9 +19,9 @@ librust-sha2-dev, librust-tar-dev, librust-tempfile-dev, - librust-term-dev, + librust-term-0.7+default-dev, librust-time-dev, - librust-toml-dev, + librust-toml-0.7+default-dev (>= 0.7.6), librust-url-dev, librust-wait-timeout-dev, librust-zip-dev, @@ -30,6 +30,7 @@ librust-clap-2+vec-map-dev (>= 2.33.3), librust-clap-2+ansi-term-dev (>= 2.33.3), librust-curl-dev, + librust-dirs-5+default-dev, librust-walkdir-dev, librust-openssl-dev, librust-semver-0.9-dev, diff -Nru elan-3.0.0/debian/patches/0002-dependencies.patch elan-3.0.0/debian/patches/0002-dependencies.patch --- elan-3.0.0/debian/patches/0002-dependencies.patch 2023-09-26 19:19:14.0 + +++ elan-3.0.0/debian/patches/0002-dependencies.patch 2024-01-01 18:33:54.0 + @@ -27,8 +27,7 @@ -sha2 = "0.9.2" +sha2 = "0.10.5" tempfile = "3.2.0" --term = "0.7.0" -+term = "0.5.2" + term = "0.7.0" time = "0.3.4" -toml = "0.5.8" +toml = "0.7.6"
Bug#1059675: rust-ahash - autopkgtest failure on s390x.
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 at 'assertion
failed: `(left == right)`
290s left: `18446744073709551614`,
290s right: `18446744073709551615`', src/operations.rs:373:9
290s stack backtrace:
290s 0: rust_begin_unwind
290s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
290s 1: core::panicking::panic_fmt
290s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
290s 2: core::panicking::assert_failed_inner
290s 3: core::panicking::assert_failed
290s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
290s 4: ahash::operations::test::test_add_length
290s at ./src/operations.rs:373:9
290s 5: ahash::operations::test::test_add_length::{{closure}}
290s at ./src/operations.rs:370:26
290s 6: core::ops::function::FnOnce::call_once
290s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
290s 7: core::ops::function::FnOnce::call_once
290s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
290s note: Some details are omitted, run with `RUST_BACKTRACE=full`
for a verbose backtrace.
This smells like an endian issue to me, but I don't know how serious
it is, so I've filed an upstream issue.
Bug#1057451: rust-ahash: autopkgtests failing
tags 1057451 +patch
thanks
I just looked at the remaining autopkgtest failures in rust-ahash, I found and
fixed two issues and after doing so the autopkgtests passed.
The first issue was some arithmetic overflows in summations in tests/bench.rs
these cause panics if built/run in Debug mode (as "cargo test --all-targets"
does by default). The results of the summations were not used for anything.
I'm not sure what the original intent of the summations was, perhaps it was
just to shut compiler warnings up, perhaps it was an attempt to stop the
compiler optimizing stuff away. I just commented out the summations, another
possibility would be to replace them with calls to std::hint::black_box
The second issue was some tests that failed to build when the std feature
was enabled but none of the rng features (runtime-rng, compile-time-rng
or no-rng) were enabled. I added/adjusted feature gaurds to fix this
issue.
Debdiff attached, if I get no response I will likely NMU this in a week
or so.diff -Nru rust-ahash-0.8.5/debian/changelog rust-ahash-0.8.5/debian/changelog
--- rust-ahash-0.8.5/debian/changelog 2023-12-10 23:06:48.0 +
+++ rust-ahash-0.8.5/debian/changelog 2023-12-26 10:08:52.0 +
@@ -1,3 +1,13 @@
+rust-ahash (0.8.5-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtest. (Closes: #1057451)
++ Disable overflowing additions whose results are not used in
tests/bench.rs
++ Add/Adjust feature gaurds to fix build of tests when the std feature is
+ enabled but no rng feature is enabled.
+
+ -- Peter Michael Green Tue, 26 Dec 2023 10:08:52 +
+
rust-ahash (0.8.5-3) unstable; urgency=medium
* update patch;
diff -Nru rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch
rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch
--- rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch 1970-01-01
00:00:00.0 +
+++ rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch 2023-12-26
10:08:52.0 +
@@ -0,0 +1,84 @@
+Description: Disable overflowing additions whose results are not used in
tests/bench.rs
+Author: Peter Michael Green
+Bug-Debian: https://bugs.debian.org/1057451
+
+--- rust-ahash-0.8.5.orig/tests/bench.rs
rust-ahash-0.8.5/tests/bench.rs
+@@ -118,10 +118,10 @@ fn bench_map(c: &mut Criterion) {
+ group.bench_function("aHash-alias", |b| {
+ b.iter(|| {
+ let hm: ahash::HashMap = (0..1_000_000).map(|i| (i,
i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get(&i) {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -129,10 +129,10 @@ fn bench_map(c: &mut Criterion) {
+ group.bench_function("aHash-hashBrown", |b| {
+ b.iter(|| {
+ let hm: hashbrown::HashMap = (0..1_000_000).map(|i|
(i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get(&i) {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -140,10 +140,10 @@ fn bench_map(c: &mut Criterion) {
+ group.bench_function("aHash-hashBrown-explicit", |b| {
+ b.iter(|| {
+ let hm: hashbrown::HashMap =
(0..1_000_000).map(|i| (i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get(&i) {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -151,10 +151,10 @@ fn bench_map(c: &mut Criterion) {
+ group.bench_function("aHash-wrapper", |b| {
+ b.iter(|| {
+ let hm: ahash::AHashMap = (0..1_000_000).map(|i|
(i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get(&i) {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -162,10 +162,10 @@ fn bench_map(c: &mut Criterion) {
+ group.bench_function("aHash-rand", |b| {
+ b.iter(|| {
+ let hm: std::collections::HashMap =
(0..1_000_000).map(|i| (i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get(&i) {
+-sum += x;
++//sum += x;
Bug#1059034: Impossible to install: Depends on missing package,librust-ego-tree-0.6+default-dev
Impossible to install: Depends on missing package librust-ego-tree-0.6+default-dev rust-ego-tree was uploaded but rejected. https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2023-December/037170.html
Bug#1051521: rust-palette: autopkgtest failures
tags 105121 +patch thanks rust-palette is unable to migrate to Testing because its autopkgtests are failing. I prepared a fix for the autopkgtest issues. While I was at it I also bumped the clap dev-dependency and the associated build and test dependencies to version 4 as we would like to phase out clap version 3. I discussed the clap upgrade with upstream, they said it was only used for examples but they did not want to bump it upstream at this time due to msrv. https://github.com/Ogeon/palette/issues/364 If I get no response I will likely NMU this in a week or so.
Bug#1059009: hime: build-depends on dropped package.
Package: hime Version: 0.9.11+dfsg-2 Severity: serious Tags: trixie, sid Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable Hime build-depends on libayatana-indicator-dev which is no longer built by the libayatana-indicator source package. It is still present in unstable as a cruft package but is gone from testing on most architectures meaning your package cannot be built on most architectures in testing.
Bug#1058074: rust-hyper-rustls - autopkgtest failure
Package: rust-hyper-rustls
Version: 0.24.2-1
Severity: serious
Tags: patch
The autopkgtest for rust-hyper-rustls is failing, because the code in
test_alpn_http2 requires a runtime, but the feature requirements for
the test do not specify one.
A debdiff fixing this is attatched.diff -Nru rust-hyper-rustls-0.24.2/debian/changelog
rust-hyper-rustls-0.24.2/debian/changelog
--- rust-hyper-rustls-0.24.2/debian/changelog 2023-12-02 20:25:28.0
+
+++ rust-hyper-rustls-0.24.2/debian/changelog 2023-12-12 01:18:39.0
+
@@ -1,3 +1,11 @@
+rust-hyper-rustls (0.24.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix feature requirements for test_alpn_http to prevent autopkgtest
+failure.
+
+ -- Peter Michael Green Tue, 12 Dec 2023 01:18:39 +
+
rust-hyper-rustls (0.24.2-1) unstable; urgency=medium
* unfuzz patches
diff -Nru
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
--- rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
1970-01-01 00:00:00.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
2023-12-12 01:18:17.0 +
@@ -0,0 +1,20 @@
+Description: tests_alpn_http2 fails to build if no runtime is enabled
+ Add feature guards so it doesn't cause autopkgtest failure.
+Author: Peter Michael Green
+Last-Update: 2023-12-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+Index: rust-hyper-rustls-0.24.2/src/connector/builder.rs
+===
+--- rust-hyper-rustls-0.24.2.orig/src/connector/builder.rs
rust-hyper-rustls-0.24.2/src/connector/builder.rs
+@@ -353,7 +353,7 @@ mod tests {
+ }
+
+ #[test]
+-#[cfg(all(not(feature = "http1"), feature = "http2"))]
++#[cfg(all(not(feature = "http1"), feature = "http2", any(feature =
"native-tokio", feature = "tokio-runtime")))]
+ fn test_alpn_http2() {
+ let roots = rustls::RootCertStore::empty();
+ let tls_config = rustls::ClientConfig::builder()
diff -Nru rust-hyper-rustls-0.24.2/debian/patches/series
rust-hyper-rustls-0.24.2/debian/patches/series
--- rust-hyper-rustls-0.24.2/debian/patches/series 2022-12-06
11:57:28.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/series 2023-12-12
01:16:36.0 +
@@ -1,3 +1,4 @@
1001_http1.patch
+1002_test-requires-runtime.patch
2001_webpki-roots.patch
2004_tests_broken.patch
Bug#1054156: librust-env-logger-0.7+default-dev shouldn't provide librust-env-logger+default-dev
On the one hand I'm not at all convinced this bug is rc, on the other hand I don't think shipping a four year old version of env-logger in the next release of Debian is a great idea. So I decided to look at the reverse dependencies, I found three safe-vdash - this is a Jonas package, the dependency on rust-env-logger-0.7 seems bogus, I filed a bug. rust-tracing-log - the new version no longer depends on env-logger, I updated it along with it's reverse dependency tracing-subscriber. rspotify - this package is long term broken, noctis expressed an interest in fixing it back in January but I don't know what if-any progress he has made since then.
Bug#1057198: rust-wasmtime: FTBFS error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope
Package: rust-wasmtime Version: 15.0.0+dfsg-3 Severity: serious Control: block 1055090 by -1 https://buildd.debian.org/status/fetch.php?pkg=rust-wasmtime&arch=all&ver=15.0.0%2Bdfsg-3&stamp=1701097543&raw=0 error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope --> cranelift/codegen/src/isa/mod.rs:118:12 | 118 | lookup(triple!(name)) |^ function or associated item not found in `Triple` | = help: items from traits can only be used if the trait is in scope = note: this error originates in the macro `triple` (in Nightly builds, run with -Z macro-backtrace for more info) help: the following trait is implemented but not in scope; perhaps add a `use` for it: | 46 + use core::str::FromStr; | For more information about this error, try `rustc --explain E0599`. The following warnings were emitted during compilation:
Bug#1055099: rust-async-task: Failing autopkgtests
On 21/11/2023 11:41, Jonas Smedegaard wrote: Quoting Peter Green (2023-11-21 09:16:21) Tags 1055099 +patch thanks The autopkgtests for rust-async-task began failing after the upgrade to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing. I have prepared a patch which adds a feature guard to the example in question and hence fixes the autopkgtest. A debdiff is attatched, if I get no response I intend to NMU this soon. Thanks. Seems the intended attachment is missing, however. Sorry, attatched now. diff -Nru rust-async-task-4.5.0/debian/changelog rust-async-task-4.5.0/debian/changelog --- rust-async-task-4.5.0/debian/changelog 2023-10-19 12:46:47.0 + +++ rust-async-task-4.5.0/debian/changelog 2023-11-21 08:05:37.0 + @@ -1,3 +1,10 @@ +rust-async-task (4.5.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch 1001 to add feature requirement to example (Closes: #1055099) + + -- Peter Micheal Green Tue, 21 Nov 2023 08:05:37 + + rust-async-task (4.5.0-1) unstable; urgency=medium [ upstream ] diff -Nru rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch --- rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch 1970-01-01 00:00:00.0 + +++ rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch 2023-11-21 08:05:31.0 + @@ -0,0 +1,16 @@ +Description: add feature requirement for example + Avoids build failure in autopkgtest. +Author: Peter Micahel Green +Forwarded: no +Last-Update: 2023-11-21 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +Index: rust-async-task-4.5.0/examples/spawn-local.rs +=== +--- rust-async-task-4.5.0.orig/examples/spawn-local.rs rust-async-task-4.5.0/examples/spawn-local.rs +@@ -1,3 +1,4 @@ ++#![cfg(feature = "std")] + //! A simple single-threaded executor that can spawn non-`Send` futures. + + use std::cell::Cell; diff -Nru rust-async-task-4.5.0/debian/patches/series rust-async-task-4.5.0/debian/patches/series --- rust-async-task-4.5.0/debian/patches/series 2023-10-10 17:25:47.0 + +++ rust-async-task-4.5.0/debian/patches/series 2023-11-21 08:05:37.0 + @@ -1 +1,2 @@ +1001_example_feature_requirements.patch 2001_flaky-test.patch
Bug#1055099: rust-async-task: Failing autopkgtests
Tags 1055099 +patch thanks The autopkgtests for rust-async-task began failing after the upgrade to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing. I have prepared a patch which adds a feature guard to the example in question and hence fixes the autopkgtest. A debdiff is attatched, if I get no response I intend to NMU this soon.
Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4
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://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/rust-ripasso-cursive.html error[E0425]: cannot find function `push` in module `pass` --> src/main.rs:941:29 | 941 | let push_result = pass::push(&store.lock().unwrap().lock().unwrap()); | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::push; | help: if you import `push`, refer to it directly | 941 - let push_result = pass::push(&store.lock().unwrap().lock().unwrap()); 941 + let push_result = push(&store.lock().unwrap().lock().unwrap()); | error[E0425]: cannot find function `pull` in module `pass` --> src/main.rs:953:19 | 953 | let _ = pass::pull(&store.lock().unwrap().lock().unwrap()) | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::pull; | help: if you import `pull`, refer to it directly | 953 - let _ = pass::pull(&store.lock().unwrap().lock().unwrap()) 953 + let _ = pull(&store.lock().unwrap().lock().unwrap()) | error[E0603]: function `init_git_repo` is private --> src/wizard.rs:32:26 | 32 | let init_res = pass::init_git_repo(&pass::password_dir(password_store_dir, home).unwrap()); | ^ private function | note: the function `init_git_repo` is defined here --> /usr/share/cargo/registry/ripasso-0.6.4/src/pass.rs:34:60 | 34 | add_and_commit_internal, commit, find_last_commit, init_git_repo, match_with_parent, |^ I tried to update ripasso-cursive to 0.6.4 to match ripasso but I got. Applying patch unbreak-new-user-wizard.patch patching file src/main.rs Hunk #1 succeeded at with fuzz 1 (offset -58 lines). Hunk #2 FAILED at 1189. Hunk #3 succeeded at 1324 with fuzz 1 (offset 109 lines). Hunk #4 FAILED at 1773. Hunk #5 FAILED at 1789. Hunk #6 FAILED at 1798. Hunk #7 succeeded at 1849 with fuzz 2 (offset 43 lines). 4 out of 7 hunks FAILED -- rejects in file src/main.rs Patch unbreak-new-user-wizard.patch does not apply (enforce with -f) Can someone confirm whether this patch is still needed, and if-so update it for the new upstream version? For what it's worth I was able to get a succesful build by. 1. Upgrading ripasso-cursive to 0.6.3 (0.6.4 has a new dependency that is not in Debian) 2. Disabling unbreak-new-user-wizard.patch and translation-locations.patch I would still like feedback from Alexander on whether those patches are still relavent.
Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4
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://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/rust-ripasso-cursive.html error[E0425]: cannot find function `push` in module `pass` --> src/main.rs:941:29 | 941 | let push_result = pass::push(&store.lock().unwrap().lock().unwrap()); | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::push; | help: if you import `push`, refer to it directly | 941 - let push_result = pass::push(&store.lock().unwrap().lock().unwrap()); 941 + let push_result = push(&store.lock().unwrap().lock().unwrap()); | error[E0425]: cannot find function `pull` in module `pass` --> src/main.rs:953:19 | 953 | let _ = pass::pull(&store.lock().unwrap().lock().unwrap()) | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::pull; | help: if you import `pull`, refer to it directly | 953 - let _ = pass::pull(&store.lock().unwrap().lock().unwrap()) 953 + let _ = pull(&store.lock().unwrap().lock().unwrap()) | error[E0603]: function `init_git_repo` is private --> src/wizard.rs:32:26 | 32 | let init_res = pass::init_git_repo(&pass::password_dir(password_store_dir, home).unwrap()); | ^ private function | note: the function `init_git_repo` is defined here --> /usr/share/cargo/registry/ripasso-0.6.4/src/pass.rs:34:60 | 34 | add_and_commit_internal, commit, find_last_commit, init_git_repo, match_with_parent, |^ I tried to update ripasso-cursive to 0.6.4 to match ripasso but I got. Applying patch unbreak-new-user-wizard.patch patching file src/main.rs Hunk #1 succeeded at with fuzz 1 (offset -58 lines). Hunk #2 FAILED at 1189. Hunk #3 succeeded at 1324 with fuzz 1 (offset 109 lines). Hunk #4 FAILED at 1773. Hunk #5 FAILED at 1789. Hunk #6 FAILED at 1798. Hunk #7 succeeded at 1849 with fuzz 2 (offset 43 lines). 4 out of 7 hunks FAILED -- rejects in file src/main.rs Patch unbreak-new-user-wizard.patch does not apply (enforce with -f) Can someone confirm whether this patch is still needed, and if-so update it for the new upstream version?
Bug#1055895: [Pkg-rust-maintainers] Bug#1055895: rust-self-cell: RUSTSEC-2023-0070
Please see https://rustsec.org/advisories/RUSTSEC-2023-0070.html I have read the upstream advisory and the linked bug report and while I don't fully understand the nitty gritty details my understanding of the issue is. * It was discovered that code (which was not marked as unsafe) could mis-use self-cell in a way that invoked undefined behaviour. * This was fixed by adding an additional compile time check which will cause the build to fail in such cases. Based on this understanding I have * Uploaded the new version of rust-self-cell * Performed a rebuild test of the only reverse dependency rust-coreutils, it built successfully, so presumably it is not impacted by this issue.
Bug#1055833: marked as pending in charliecloud
Control: tag -1 pending Hello, Bug #1055833 in charliecloud 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/hpc-team/charliecloud/-/commit/80969006f62d9d5450bdfb8237512baba4d891d9 d/t/control: Skip autopkgtest on s390x (Closes: #1055833) This is a workaround for upstream issue https://github.com/hpc/charliecloud/issues/1773 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055833
Bug#1055319: rust-rustls-webpki autopkgtest failure.
Package: rust-rustls-webpki Version: 0.101.6-1 Severity: serious The autopkgtest for rust-rustls-webpki fails with 238s error[E0583]: file not found for module `test_utils` 238s --> src/lib.rs:65:1 238s| 238s 65 | pub(crate) mod test_utils; 238s| ^^ 238s| 238s= help: to create the module `test_utils`, create file "src/test_utils.rs" or "src/test_utils/mod.rs" This bug affects both the versions in unstable and experimental. It does not affect the version currently in testing. It appears that the file src/test_utils.rs is included in the source package but is not making it into the binary package for some reason.
Bug#1054713: libsquashfuse-dev: needed headers (e.g. config.h) are not shipped
Control: affects -1 + src:charliecloud thanks Hi, this bug also affects charliecloud: - configure:6729: checking for squashfuse/ll.h configure:6729: gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -std=c99 -Wall -I/usr/include -L/usr/lib -Wno-unused-command-line-argument -Werror -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 In file included from /usr/include/squashfuse/dir.h:28, from /usr/include/squashfuse/squashfuse.h:28, from /usr/include/squashfuse/ll.h:28, from conftest.c:17: /usr/include/squashfuse/common.h:28:10: fatal error: config.h: No such file or directory 28 | #include "config.h" | ^~ compilation terminated. - Charliecloud users notice this as: - $ ch-run myimage.sqfs -- /bin/bash ch-run[7126]: error: this ch-run does not support internal SquashFS mounts (ch-run.c:202) ----- Best regards, Peter
Bug#1054568: breezy - broken rust regex build-dependency
Package: breezy Version: 3.3.4-1 Severity: serious Tags: patch Breezy build-depends on librust-regex+aho-corasick-dev which is no longer provided (in either physical or virtual form) by rust-regex. Looking at the Cargo.toml files I belive the correct build-dependency is librust-regex-1+default-dev (>= 1.5.4), after changing the build-dependency I was able to get a succesful build. If there are no objections I will likely NMU this in the not too distant future.diff -Nru breezy-3.3.4/debian/changelog breezy-3.3.4/debian/changelog --- breezy-3.3.4/debian/changelog 2023-09-04 17:39:38.0 + +++ breezy-3.3.4/debian/changelog 2023-10-26 02:55:52.0 + @@ -1,3 +1,12 @@ +breezy (3.3.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Replace broken build-dependency on "librust-regex+aho-corasick-dev" +with build-dependency on "librust-regex-1+default-dev (>= 1.5.4)" +based on the contents of Cargo.toml. + + -- Peter Michael Green Thu, 26 Oct 2023 02:55:52 + + breezy (3.3.4-1) unstable; urgency=low * New upstream release. diff -Nru breezy-3.3.4/debian/control breezy-3.3.4/debian/control --- breezy-3.3.4/debian/control 2023-09-04 17:39:38.0 + +++ breezy-3.3.4/debian/control 2023-10-26 02:55:40.0 + @@ -31,7 +31,7 @@ debhelper-compat (= 13), librust-pkg-version-dev, librust-pyo3-dev, - librust-regex+aho-corasick-dev, + librust-regex-1+default-dev (>= 1.5.4), rustc Standards-Version: 4.6.2 Rules-Requires-Root: no
Bug#1052732: notus-scanner: FTBFS: ModuleNotFoundError: No module named 'tomli'
Control: tags -1 + patch See https://salsa.debian.org/pkg-security-team/notus-scanner/-/merge_requests/1
Bug#1054141: fd - incompatible with clap 4.4.6
Package: rust-fd-find Version: 8.7.0-3 Severity: serious This bug affects both 8.7.0-3 in testing and 8.7.0-4 in unstable. I recently uploaded clap 4.4.6, since this was not a semver bump I was not expecting any breakage. Unfortunately it turns out it broke fd. There are (at least) two issues, the first is that the "unstable-grouped" feature was removed in clap 4.2.0 by the commit https://github.com/clap-rs/clap/commit/d5089b267235db72a6ea146ac4f1cb7f79a170a6 "fix!: Remove stablized unstable-grouped feature". By removing the reference to the "unstable-grouped" feature I was able to successfully build fd and run it's tests against clap versions 4.2.0 through 4.2.4. The second issue arises starting with clap version 4.2.5, a bunch of tests fail with errors like. test_custom_ignore_files stdout thread 'test_custom_ignore_files' panicked at '`fd --ignore-file custom.ignore foo` did not exit successfully. stdout: --- --- stderr: --- thread 'main' panicked at 'Command fd: Argument group 'execs' conflicts with non-existent 'has_results' id', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/clap_builder-4.2.5/src/builder/debug_asserts.rs:317:13 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---', tests/testenv/mod.rs:238:13 I'm not sure what should be done about this second issue. I've filed a bug upstream at https://github.com/sharkdp/fd/issues/1397
Bug#1053638: [Pkg-rust-maintainers] Bug#1053638: rust-pbr: Remove from Debian?
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.
Bug#1053632: [Pkg-rust-maintainers] Bug#1053632: rust-libslirp: Remove from Debian?
rust-libslirp has no reverse dependencies in Debian. https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-libslirp&perpkg=1 It is also one of the blockers for removing the old rust-zbus-1 from Debian. See https://bugs.debian.org/1053631 Can we remove rust-libslirp and rust-libslirp-sys from Debian? We discussed this on irc a while back, and apparently the package is important to debos. Though the package relationship is only a "suggests". rust-libslirp depends on the obsolete rust-zbus-1 (instead of the current rust-zbus-3) and rust-zvariant-2 (instead of rust-zvariant-3). I looked at porting this, but came to the conclusion that is beyond what I could reasonablly do. IIRC zbus moved from sync rust to async rust and there was no porting guide.
Bug#1053630: flask-dance: build-depends on package that is not in testing.
Package: flask-dance Version: 6.2.0.2-1 Severity: serious Justification: rc policy - "packages must be buildable within the same release". Tags: trixie, sid flask-dance build-depends on python3-sphinxcontrib.seqdiag which is not in testing, it was removed because it FTBFS and was badly broken, but for some reason flask-dance was not removed at the same time (dependency handling in auto-removals is far from perfect). This issue affects both versions 6:2.0.2-1 in testing and 7.0.0-1 which is trying to migrate to testing but failing to do so due to the aforementioned build-dependency.
Bug#1053536: squeekboard FTBFS with version 0.18 of rust gtk stack.
Package: squeekboard Version: 1.22.0-4 Severity: serious Tags: patch The rust gtk stack was recently updated, and squeekboard needs a few tweaks to build with the new version. I have whipped up a patch and tested that squeekboard builds with it, I have not tested it beyond that.diff -Nru squeekboard-1.22.0/debian/changelog squeekboard-1.22.0/debian/changelog --- squeekboard-1.22.0/debian/changelog 2023-08-23 08:47:31.0 + +++ squeekboard-1.22.0/debian/changelog 2023-10-05 19:31:30.0 + @@ -1,3 +1,10 @@ +squeekboard (1.22.0-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * update patches for gtk-rs 0.18 + + -- Peter Michael Green Thu, 05 Oct 2023 19:31:30 + + squeekboard (1.22.0-4) unstable; urgency=medium [ Peter Michael Green ] diff -Nru squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.17.patch squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.17.patch --- squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.17.patch 2023-08-23 08:47:31.0 + +++ squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.17.patch 1970-01-01 00:00:00.0 + @@ -1,53 +0,0 @@ -From: Arnaud Ferraris -Date: Tue, 27 Jun 2023 12:31:30 +0200 -Subject: Cargo.deps.newer: update for gtk-rs 0.17 - - Cargo.deps.newer | 20 ++-- - 1 file changed, 10 insertions(+), 10 deletions(-) - -diff --git a/Cargo.deps.newer b/Cargo.deps.newer -index 197dfa3..c236cc5 100644 a/Cargo.deps.newer -+++ b/Cargo.deps.newer -@@ -9,30 +9,30 @@ zvariant = "2.10.*" - zvariant_derive = "2.10.*" - - [dependencies.cairo-rs] --version = "0.14.*" -+version = "0.17.*" - - [dependencies.cairo-sys-rs] --version = "0.14.*" -+version = "0.17.*" - - [dependencies.gdk] --version = "0.14.*" -+version = "0.17.*" - - [dependencies.gio] --version = "0.14.*" -+version = "0.17.*" - features = ["v2_58"] - - [dependencies.glib] --version = "0.14.*" -+version = "0.17.*" - features = ["v2_58"] - - [dependencies.glib-sys] --version = "0.14.*" -+version = "0.17.*" - features = ["v2_58"] - - [dependencies.gtk] --version = "0.14.*" --features = ["v3_22"] -+version = "0.17.*" -+features = ["v3_24"] - - [dependencies.gtk-sys] --version = "0.14.*" --features = ["v3_22"] -+version = "0.17.*" -+features = ["v3_24"] diff -Nru squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.18.patch squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.18.patch --- squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.18.patch 1970-01-01 00:00:00.0 + +++ squeekboard-1.22.0/debian/patches/0001-Cargo.deps.newer-update-for-gtk-rs-0.18.patch 2023-10-05 19:31:30.0 + @@ -0,0 +1,55 @@ +Modified by Peter Michael Green for version 0.18 of rust gtk stack. + +From: Arnaud Ferraris +Date: Tue, 27 Jun 2023 12:31:30 +0200 +Subject: Cargo.deps.newer: update for gtk-rs 0.17 + +--- + Cargo.deps.newer | 20 ++-- + 1 file changed, 10 insertions(+), 10 deletions(-) + +diff --git a/Cargo.deps.newer b/Cargo.deps.newer +index 197dfa3..c236cc5 100644 +--- a/Cargo.deps.newer b/Cargo.deps.newer +@@ -9,30 +9,30 @@ zvariant = "2.10.*" + zvariant_derive = "2.10.*" + + [dependencies.cairo-rs] +-version = "0.14.*" ++version = "0.18.*" + + [dependencies.cairo-sys-rs] +-version = "0.14.*" ++version = "0.18.*" + + [dependencies.gdk] +-version = "0.14.*" ++version = "0.18.*" + + [dependencies.gio] +-version = "0.14.*" ++version = "0.18.*" + features = ["v2_58"] + + [dependencies.glib] +-version = "0.14.*" ++version = "0.18.*" + features = ["v2_58"] + + [dependencies.glib-sys] +-version = "0.14.*" ++version = "0.18.*" + features = ["v2_58"] + + [dependencies.gtk] +-version = "0.14.*" +-features = ["v3_22"] ++version = "0.18.*" ++features = ["v3_24"] + + [dependencies.gtk-sys] +-version = "0.14.*" +-features = ["v3_22"] ++version = "0.18.*" ++features = ["v3_24"] diff -Nru squeekboard-1.22.0/debian/patches/0004-Cargo.-use-xkbcommon-v0.5.patch squeekboard-1.22.0/debian/patches/0004-Cargo.-use-xkbcommon-v0.5.patch --- squeekboard-1.22.0/debian/patches/0004-Cargo.-use-xkbcommon-v0.5.patch 2023-08-23 08:47:31.0 + +++ squeekboard-1.22.0/debian/patches/0004-Cargo.-use-xkbcommon-v0.5.patch 2023-10-05 19:31:30.0 + @@ -26,14 +26,10 @@ index c236cc5..b36e616 100
Bug#1053440: rust-sequoia-openpgp - incompatible with new regex-syntax.
Package: rust-sequoia-openpgp Version: 1.16.0-3 Severity: serious rust-sequoia-openpgp depends on an old version of regex-syntax, I tried bumping the dependency but the build failed. I have filed an issue about this upstream at https://gitlab.com/sequoia-pgp/sequoia/-/issues/1056
Bug#1053431: rust-grep-regex - depends/build-depends on old version of regex-syntax
Package: rust-grep-regex Version: 0.1.11-1 Severity: serious rust-grep-regex depends on an old version of rust-regex-syntax, this is fixed in upstream git, but looking at the commit messages it's not something I feel comfortable cherry-picking. I have opened an upstream issue enquiring about the possibility of a new release at https://github.com/BurntSushi/ripgrep/issues/2619
Bug#1053420: rust-matchers - incompatible with mew regex-automata
Package: rust-matchers Version: 0.1.0-1 Severity: serious tas: trixie, sid rust-regex-automata was recently updated to 0.3, rendering the dependencies and build-dependencies of rust-matchers uninstallable. The changes seem to be fairly major, there is an upstream pull request but details are still being discussed, so I don't think we should pull it into Debian at this time.
Bug#1052490: rust-async-task, build-depends on old version of rust-flume.
Package: rust-async-task
Version: 4.4.0-3
Severity: serious
Tags: patch
rust-async-task's build-dependencies are unsatisfiable in testing/unstable
due to a recent update to rust-flume.
upstream bumped the dependency with no code changes, and after adding the
patch to the Debian package and adjusting the rest of the packaging
accordingly I was able to get a succesfull build and autopkgtest run.
debdiff attached.diff -Nru rust-async-task-4.4.0/debian/changelog
rust-async-task-4.4.0/debian/changelog
--- rust-async-task-4.4.0/debian/changelog 2023-09-10 13:43:24.0
+
+++ rust-async-task-4.4.0/debian/changelog 2023-09-23 05:20:54.0
+
@@ -1,3 +1,14 @@
+rust-async-task (4.4.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch 0001_update_flume.patch
++ Trivial upstream patch to bump flume depdency to 0.11
+ * Reduce context in 2001_flaky-test.patch so it will apply on top of
+0001_update_flume.patch
+ * Update build and autopkgtest dependencies for flume 0.11.
+
+ -- Peter Michael Green Sat, 23 Sep 2023 05:20:54 +
+
rust-async-task (4.4.0-3) unstable; urgency=medium
* omit testing examples for autopkgtest without feature std;
diff -Nru rust-async-task-4.4.0/debian/control
rust-async-task-4.4.0/debian/control
--- rust-async-task-4.4.0/debian/control2023-07-16 09:24:09.0
+
+++ rust-async-task-4.4.0/debian/control2023-09-23 05:20:54.0
+
@@ -7,7 +7,7 @@
librust-async-task-4+default-dev ,
librust-atomic-waker-1+default-dev ,
librust-easy-parallel-3+default-dev ,
- librust-flume-0.10-dev ,
+ librust-flume-0.11-dev ,
librust-once-cell-1+default-dev ,
librust-smol-1+default-dev ,
libstring-shellquote-perl,
diff -Nru rust-async-task-4.4.0/debian/patches/0001_update_flume.patch
rust-async-task-4.4.0/debian/patches/0001_update_flume.patch
--- rust-async-task-4.4.0/debian/patches/0001_update_flume.patch
1970-01-01 00:00:00.0 +
+++ rust-async-task-4.4.0/debian/patches/0001_update_flume.patch
2023-09-23 05:17:33.0 +
@@ -0,0 +1,29 @@
+commit c42a143176fbf5201411f97f27247ba52e054135
+Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
+Date: Mon Aug 21 00:25:27 2023 +
+
+Update flume requirement from 0.10 to 0.11
+
+Updates the requirements on [flume](https://github.com/zesterer/flume) to
permit the latest version.
+- [Changelog](https://github.com/zesterer/flume/blob/master/CHANGELOG.md)
+- [Commits](https://github.com/zesterer/flume/commits)
+
+---
+updated-dependencies:
+- dependency-name: flume
+ dependency-type: direct:production
+...
+
+Signed-off-by: dependabot[bot]
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 4345762..fb239ba 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -23,5 +23,5 @@ std = []
+ easy-parallel = "3"
+ flaky_test = "0.1"
+-flume = { version = "0.10", default-features = false }
++flume = { version = "0.11", default-features = false }
+ futures-lite = "1.12.0"
+ once_cell = "1"
diff -Nru rust-async-task-4.4.0/debian/patches/2001_flaky-test.patch
rust-async-task-4.4.0/debian/patches/2001_flaky-test.patch
--- rust-async-task-4.4.0/debian/patches/2001_flaky-test.patch 2023-08-14
09:47:35.0 +
+++ rust-async-task-4.4.0/debian/patches/2001_flaky-test.patch 2023-09-23
05:19:12.0 +
@@ -7,14 +7,8 @@
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Cargo.toml
+++ b/Cargo.toml
-@@ -21,7 +21,6 @@
- [dev-dependencies]
- atomic-waker = "1"
- easy-parallel = "3"
+@@ -24,1 +24,0 @@
-flaky_test = "0.1"
- flume = { version = "0.10", default-features = false }
- futures-lite = "1.12.0"
- once_cell = "1"
--- a/tests/waker_panic.rs
+++ b/tests/waker_panic.rs
@@ -238,60 +238,6 @@
diff -Nru rust-async-task-4.4.0/debian/patches/series
rust-async-task-4.4.0/debian/patches/series
--- rust-async-task-4.4.0/debian/patches/series 2023-02-03 11:05:22.0
+
+++ rust-async-task-4.4.0/debian/patches/series 2023-09-23 05:16:50.0
+
@@ -1 +1,2 @@
+0001_update_flume.patch
2001_flaky-test.patch
diff -Nru rust-async-task-4.4.0/debian/tests/control
rust-async-task-4.4.0/debian/tests/control
--- rust-async-task-4.4.0/debian/tests/control 2023-09-10 13:40:58.0
+
+++ rust-async-task-4.4.0/debian/tests/control 2023-09-23 05:20:54.0
+
@@ -6,7 +6,7 @@
librust-async-task-4-dev,
librust-atomic-waker-1+default-dev,
librust-easy-parallel-3+default-dev,
- librust-flume-0.10-dev,
+ librust-flume-0.11-dev,
librust-once-cell-1+default-dev,
librust-smol-1+default-dev,
Restrictions: allow-stderr
@@ -19,7 +19,7 @@
librust-async-task-4+default-dev,
librust-atomic-waker-1+default-dev,
librust-easy-parallel-3+default-dev,
- librust-flu
Bug#1052334: rust-leptonica-sys - Debian and Cargo dependencies inconsistent.
Package: rust-leptonica-sys Version: 0.4.6-3 Severity: serious The Debian dependencies for rust-leptonica-sys allow versions of rust-bindgen from 0.60.x to 0.66.x, however the Cargo dependencies only allow versions from 0.64.x to 0.66.x. This is causing autopkgtest failures and blocking rust-leptonica-sys and hence rust-bindgen from migrating to testing. Please make the dependencies consistent, either by changing the Debian depndencies to match the Cargo ones or by changing the Cargo dependency to match the Debian ones.
Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
On 12/09/2023 23:30, Faidon Liambotis wrote: Control: reassign -1 rustc 1.68.2+dfsg1-1 Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression) On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote: The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. Thanks for the report. Actually, I think the WasmEdge autopkgtests are catching a rustc 1.68 regression, whereas rustc compiles wasm32 binaries that do not work with neither WasmEdge, nor Wasmtime (the latter is not in Debian). And it seems the issue persists with rustc 1.69 :( https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37797497/log.gz Very simple test case: $ podman run --rm -it debian:sid # or bookworm to test with rustc 1.67 root@ad697f1c195f:~# apt install rustc libstd-rust-dev-wasm32 [...] root@ad697f1c195f:~# rustc -V rustc 1.68.2 root@ad697f1c195f:~# cat > hello.rs <https://github.com/bytecodealliance/wasmtime/releases/download/v12.0.1/wasmtime-v12.0.1-x86_64-linux.tar.xz | tar --wildcards --strip-components=1 -xJ '*/wasmtime' root@ad697f1c195f:~# ./wasmtime hello.wasm Error: failed to run main module `hello.wasm` Caused by: 0: failed to invoke command default 1: error while executing at wasm backtrace: 0: 0x9cd6 - !__stack_chk_fail 1: 0x9d3c - !__wasilibc_init_ssp 2: 0x320 - !__wasm_call_ctors 3: 0x342 - !_start note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information 2: wasm trap: wasm `unreachable` instruction executed Thanks, Faidon
Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
Package: wasmedge Version: 0.13.3+dfsg-1 Severity:serious The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37793933/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37778163/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/37770138/log.gz 93s autopkgtest [14:54:23]: test capi-wasi-env: [--- 93s 1..2 94s ok 1 build wasi_get_env.wasm with cargo/rustc 94s not ok 2 build set_wasm_env with gcc 94s # (in test file debian/tests/capi-wasi-env, line 24) 94s # `assert_output --partial "ENV1: VAL1"' failed 94s # 94s # -- output does not contain substring -- 94s # substring (1 lines): 94s # ENV1: VAL1 94s # output (4 lines): 94s # [2023-09-12 14:54:24.910] [error] execution failed: unreachable, Code: 0x89 94s # [2023-09-12 14:54:24.910] [error] In instruction: unreachable (0x00) , Bytecode offset: 0x9efb 94s # [2023-09-12 14:54:24.910] [error] When executing function name: "print_env" 94s # Execution Failed. Error message: unreachable 94s # -- 94s # 95s autopkgtest [14:54:25]: test capi-wasi-env: ---] 95s autopkgtest [14:54:25]: test capi-wasi-env: - - - - - - - - - - results - - - - - - - - - - 95s capi-wasi-envFAIL non-zero exit status 1
Bug#1050299: [Pkg-rust-maintainers] Bug#1050299: rust-webpki: RUSTSEC-2023-0052
I think this indicates that it can indeed be safely removed from Debian? I'm CC'ing developers that have made uploads to this packages in the past for additiponal opinions as I suspect the issue is more subtle than that. dak rm does not take account of virtual packages. So for rust packages it is generally useless. In terms of reverse dependencies, a number have already moved to the fork rustls-webpki. However there are still a few left. Specifically rust-async-tls, rust-trust-dns-proto and rust-trust-dns-client. async-tls has not switched upstream. On the other hand I don't see any packages in Debian using it yet. ccing mjt to see what the reason for packaging it was. trust-dns-proto and trust-dns-server have switched upstream, however updating the trust-dns-packages has proved a bit more involved than I would have liked. I pushed my current efforts to the branch trust-dns-0.23 in the debcargo-conf repo. The main thing left to deal with regarding the trust-dns is aardvark-dns, the code changes needed were beyond my skills, so I reported an issue upstream. Upstream has come up with a patch but has not merged it yet. https://github.com/containers/aardvark-dns/pull/381
Bug#1051408: Acknowledgement (flameshot: uploads potentially sensitive screenshots to the internet)
Thank you for the quick response to my message. My message is wrong in one place: I tested the old version from Debian Bullseye. In Bookworm it behaves as follows: There is an "Imgur Application Client Id" configured in the installation. So it is possible to use the upload without any further configuration. But before uploading there is a security prompt. In German: "Möchest du diese Aufnahme hochladen?"/"Do you want to upload this image?". You may set "Upload without confirmation". For privacy reasons I would prefer the image upload function to be disabled by default and no Imgur Application Id configured. Best regards. Peter
Bug#1051408: flameshot: uploads potentially sensitive screenshots to the internet
Package: flameshot Version: 0.9.0+ds1-2 Severity: critical Tags: upstream Justification: causes serious data loss X-Debbugs-Cc: pe...@ostwall195.de Dear Maintainer, * What led up to the situation? I have installed the package for taking screenshots on recommendation * What exactly did you do (or not do) that was effective (or ineffective)? Installed the package on debian bookworm * What was the outcome of this action? Default configuration uploaded my screenshots to imgur, I found a Imgur-link in my clipboard * What outcome did you expect instead? Default configuration should save the screenshot in a local directory -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-25-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flameshot depends on: ii hicolor-icon-theme0.17-2 ii libc6 2.31-13+deb11u6 ii libfmt7 7.1.3+ds1-5 ii libgcc-s1 10.2.1-6 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus5 5.15.2+dfsg-9 ii libqt5gui55.15.2+dfsg-9 ii libqt5network55.15.2+dfsg-9 ii libqt5svg55.15.2-3 ii libqt5widgets55.15.2+dfsg-9 ii libspdlog1 [libspdlog1-fmt7] 1:1.8.1+ds-2.1 ii libstdc++610.2.1-6 flameshot recommends no packages. Versions of packages flameshot suggests: ii ca-certificates 20210119 ii openssl 1.1.1n-0+deb11u5
Bug#1050891: sccache - update for new addr2line.
On 31/08/2023 08:50, Jonas Smedegaard wrote: , but it is a risky game, Letting stuff fall ever more out of date is also a risky game as it tends to mean stuff gets even more intertwined when we do finally try to update it and if the version of rust-cargo used by debcargo gets too far out of date then things can get *really* painful. We do have the option of using semver-suffix packages, but we try to use those sparingly for several reasons. * Debian in general discourages multiple copies of what is essentially the same codebase. * It's more packages to maintain (or fail to maintain) * The packages need to pass NEW, which introduces unpredictable delay to the whole process. It's worth noting that most languages in Debian don't normally put any upper limits on dependencies used at build time, despite having far less ability to detect problems at compile time than rust does. I'm not at all convinced that these dependency bumps are any riskier than many uploads for packages in other languages that happen, unnoticed, all the time. Allow those responsible for maintaining packages to actually do that. Please in future coordinate *before* doing breaking changes (unless it happens accidentally, of course). How exactly do you want this coordination to work? how long do you think it is reasonable for us to give you to respond? how should the actual uploads be handled given that ideally for minimum breakage the packages would be uploaded at the same time?
Bug#1050891: sccache - update for new addr2line.
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
--- sccache-0.5.4/debian/changelog 2023-08-24 08:23:51.0 +
+++ sccache-0.5.4/debian/changelog 2023-08-28 13:25:35.0 +
@@ -1,3 +1,10 @@
+sccache (0.5.4-11.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump dependency on object crate to 0.31.
+
+ -- nobody Mon, 28 Aug 2023 13:25:35 +
+
sccache (0.5.4-11) unstable; urgency=medium
* drop patch 2018, obsoleted by Debian package changes
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-08-13 09:04:02.0 +
+++ sccache-0.5.4/debian/control2023-08-28 13:15:03.0 +
@@ -44,7 +44,7 @@
librust-mime-0.3+default-dev,
librust-num-cpus-1+default-dev,
librust-number-prefix-0.4+default-dev,
- librust-object-0.30+default-dev,
+ librust-object-0.31+default-dev,
librust-once-cell-1+default-dev (>= 1.17),
librust-predicates-2+default-dev ,
librust-rand-0.8+default-dev,
diff -Nru sccache-0.5.4/debian/patches/1007_update_object.patch
sccache-0.5.4/debian/patches/1007_update_object.patch
--- sccache-0.5.4/debian/patches/1007_update_object.patch 1970-01-01
00:00:00.0 +
+++ sccache-0.5.4/debian/patches/1007_update_object.patch 2023-08-28
13:17:51.0 +
@@ -0,0 +1,7 @@
+Index: sccache-0.5.4/Cargo.toml
+===
+--- sccache-0.5.4.orig/Cargo.toml
sccache-0.5.4/Cargo.toml
+@@ -92,1 +92,1 @@ zip = { version = "0.6", default-feature
+-object = "0.30"
++object = "0.31"
diff -Nru sccache-0.5.4/debian/patches/2001_no_dist-server.patch
sccache-0.5.4/debian/patches/2001_no_dist-server.patch
--- sccache-0.5.4/debian/patches/2001_no_dist-server.patch 2023-08-24
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2001_no_dist-server.patch 2023-08-28
13:18:19.0 +
@@ -30,7 +30,7 @@
-# dist-server only
memmap2 = "0.6.2"
-nix = { version = "0.26.2", optional = true }
- object = "0.30"
+ object = "0.31"
-rouille = { version = "3.5", optional = true, default-features = false,
features = [
- "ssl",
-] }
diff -Nru sccache-0.5.4/debian/patches/2008_assert_cmd.patch
sccache-0.5.4/debian/patches/2008_assert_cmd.patch
--- sccache-0.5.4/debian/patches/2008_assert_cmd.patch 2023-08-24
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2008_assert_cmd.patch 2023-08-28
13:18:39.0 +
@@ -8,7 +8,7 @@
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -100,7 +100,7 @@
- object = "0.30"
+ object = "0.31"
[dev-dependencies]
-assert_cmd = "2.0.10"
diff -Nru sccache-0.5.4/debian/patches/2017_memmap2.patch
sccache-0.5.4/debian/patches/2017_memmap2.patch
--- sccache-0.5.4/debian/patches/2017_memmap2.patch 2023-08-24
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2017_memmap2.patch 2023-08-28
13:19:01.0 +
@@ -13,6 +13,6 @@
-memmap2 = "0.6.2"
+memmap2 = ">= 0.5.10, < 0.7"
- object = "0.30"
+ object = "0.31"
[dev-dependencies]
diff -Nru sccache-0.5.4/debian/patches/series
sccache-0.5.4/debian/patches/series
--- sccache-0.5.4/debian/patches/series 2023-08-18 15:13:19.0 +
+++ sccache-0.5.4/debian/patches/series 2023-08-28 13:16:36.0 +
@@ -1,5 +1,6 @@
1001_optional_tests.patch
1006_tests_network.patch
+1007_update_object.patch
2001_no_dist-server.patch
2002_no_opendal_backends.patch
2003_no_windows.patch
Bug#1050535: rust-rustls-webpki FTBFS, tests require rcgen.
Package: rust-rustls-webpki
Version: 0.101.4-1
Severity: serious
Tags: patch
It seems that in addition to the security fix, the new version of
rustls-webpki added some new tests, these depend on "rcgen" which is
currently patched away by 2001_bencher.patch.
After reinstating the dependency (but NOT the "patch.crates-io" section)
and adding corresponding build and test dependencies I was able to
successfully build the package and run it's autopkgtests.
Debdiff attatched, I may NMU this later (but I'd appreciate a prompt
maintainer upload).
diff -Nru rust-rustls-webpki-0.101.4/debian/changelog
rust-rustls-webpki-0.101.4/debian/changelog
--- rust-rustls-webpki-0.101.4/debian/changelog 2023-08-24 08:06:53.0
+
+++ rust-rustls-webpki-0.101.4/debian/changelog 2023-08-25 18:57:05.0
+
@@ -1,3 +1,13 @@
+rust-rustls-webpki (0.101.4-1.1) UNRELEASED; urgency=high
+
+ * Non-maintainer upload.
+ * Adjust patch 2001, reinstate rcgen dependency, some newly added tests need
+it. Do not reinstate the "patch.crates-io" section since we want to build
+against debian packaged crates, not stuff from github.
+ * Add build and 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/debian/control
rust-rustls-webpki-0.101.4/debian/control
--- rust-rustls-webpki-0.101.4/debian/control 2023-08-24 08:05:29.0
+
+++ rust-rustls-webpki-0.101.4/debian/control 2023-08-25 18:57:05.0
+
@@ -6,6 +6,7 @@
dh-cargo,
librust-base64-0.21+default-dev ,
librust-ring-0.16+default-dev ,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2) ,
librust-serde-1+default-dev ,
librust-serde-1+derive-dev ,
librust-serde-json-1+default-dev ,
diff -Nru rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
--- rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-24 08:06:28.0 +
+++ rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-25 18:56:43.0 +
@@ -15,16 +15,15 @@
include = [
"Cargo.toml",
-@@ -72,9 +73,6 @@
+@@ -72,8 +73,6 @@
[dev-dependencies]
base64 = "0.21"
-bencher = "0.1.5"
-once_cell = "1.17.2"
--rcgen = { version = "0.11.1", default-features = false }
+ rcgen = { version = "0.11.1", default-features = false }
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
-
@@ -93,12 +91,3 @@
lto = true
debug-assertions = false
diff -Nru rust-rustls-webpki-0.101.4/debian/tests/control
rust-rustls-webpki-0.101.4/debian/tests/control
--- rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-24
08:05:35.0 +
+++ rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-25
18:57:05.0 +
@@ -8,6 +8,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -20,6 +21,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -32,6 +34,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -44,6 +47,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -56,4 +60,5 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Bug#1040837: rust-log situation update.
On 22/08/2023 04:47, Peter Green wrote: Fabian: is sval-serde ready for sponsorship? if so can you add the RFS file? I couldn't see anything wrong with the sval-serde package, so I decided to go ahead and upload it, it is now in NEW.
Bug#1040837: rust-log situation update.
A bunch of packages just cleared new, and I made a bunch of follow up uploads. The result is that the situation surrounding the log package has improved a bit, but it still less than ideal. The "kv_unstable" and "kv_unstable_sval" features are now enabled, the "kv_unstable_serde" feature is currently disabled because it requires the serde feature in the value-bag package, which in turn requires the serde1 feature in the value-bag-serde1 crate, which in turn requires the sval_serde crate which is not currently in debian. I belive the net result of this is that * kv-log-macro's binary dependencies are satisfiable but it's build-dependencies are not. * femme's dependencies and build-dependencies are still unsatisfiable. Looking in the debcargo-conf repository it seems that Fabian Grünbichler has made a start on packaging sval_serde. Fabian: is sval-serde ready for sponsorship? if so can you add the RFS file?
Bug#1050185: rust-derive-builder-core - depends on old version of darling.
Package: rust-derive-builder-core Version: 0.12.0-1 Severity: serious Recently a new version of the darling crates was uploaded, (Alexander Kajil prepared the uploads, Sylvestre uploaded darling-core and I uploaded the rest of the darling crates). Most of the reverse dependencies either already had uploads prepared, or I was able to prepare uploads. Unfortunately things were not so fortunate with derive-builder-core. Bumping darling generally also implies bumping syn, otherwise one runs into issues. We currently have both versions 1.x and 2.x of syn in Debian, so this is not an issue in itself but it means more API changes. I tried to patch derive-builder-core for the new syn, but I failed. Looking upstream it seems they are also currently stuck. https://github.com/colin-kiegel/rust-derive-builder/issues/292
Bug#1050138: rust-wasmer-enumset-derive should not be in trixie
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 them around creating more busywork for the rust team to prevent them blocking semver transitions.
Bug#1050134: rust-leptonica-plumbing - autopkgtest depends on non-existent virtual package.
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 but it is not installable 118s E: Unable to correct problems, you have held broken packages. 118s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs librust-leptonica-plumbing-dev provides |librust-leptonica-plumbing-1+default-dev and|| librust-leptonica-plumbing-1.0-dev but not |librust-leptonica-plumbing-1.0+default-dev
Bug#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls
Package: rust-hyper-rustls Version: 0.23.2-4 Severity: serious I just updated tokio-rustls to 0.24.1, hyper-rustls needs updating to 0.24.1 to match.
Bug#1049447: minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps.
Package: minexpert2 Version: 8.6.3-1 Severity: serious Tags: trixie, sid Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable x-debbugs-cc: lopi...@debian.org daps 3.3.2+cleaned1-5 moved calibre from suggests to depends. This means that daps can no longer be installed on architectures where calibre is not available. This in turn means that minexpert2 cannot be built on those architectures. This applies to both the version of minexpert2 in testing and the version in unstable.
Bug#1049445: massxpert build-dependencies unsatisfiable on many architectures due to change in daps.
Package: massxpert Version: 7.0.0-2 Severity: serious Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable x-debbugs-cc: lopi...@debian.org daps 3.3.2+cleaned1-4 moved calibre from suggests to depends. This means that daps can no longer be installed on architectures where calibre is not available. This in turn means that massxpert cannot be built on those architectures.
Bug#1049440: calculix-cgx - build-depends on dropped transitional package.
Package: calculix-cgx Version: 2.17+dfsg-2 Severity: serious Tags: trixie, sid calculix-cgx build-depends on libgl1-mesa-glx which is no longer built by the mesa source package. It is still present in unstable and on a couple of architectures in testing as a cruft package, but it is completely gone from most architectures in testing. Please update your build-dependencies as appropriate.
Bug#1043418: rust-rustls-webpki - autopkgtest failure, file not found errors.
tags 1043418 +patch
thanks
The autopkgtest for rust-rustls-webpki is failing with a bunch of file not
found errors.
Investigating a bit more, the issue is that the data files in question are
included in the source package, but not in the binary package. I'm not sure if
this is
a result of your debcargo fork. In any case, I wrote a patch to allow the
autpkgtest
to use the test data from the source package.
I also ran into a second issue, there is a patch that removes the
dev-dependencies
needed for the benches and also removes the bench declaration in Cargo.toml, but
cargo has a feature for auto-detecting tests/benches/examples, so it was still
trying to build the benches. I added autobenches=false to disable this.
With the attatched debdiff, the autopkgtest passes. I'd like to see this fixed
fairly quickly, as fixes blocked by the stalled rustls transition are
threatening
a bunch of packages with auto-removal. If I get no response I'll likely NMU it
next weekend.
diff -Nru rust-rustls-webpki-0.101.3/debian/changelog
rust-rustls-webpki-0.101.3/debian/changelog
--- rust-rustls-webpki-0.101.3/debian/changelog 2023-08-13 11:24:24.0
+
+++ rust-rustls-webpki-0.101.3/debian/changelog 2023-08-15 16:01:55.0
+
@@ -1,3 +1,14 @@
+rust-rustls-webpki (0.101.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch 2004 and alter debian/tests/control to use test data from the
source
+package during autopkgtest as the test data is not included in the binary
+package (Closes: #1043418)
+ * Extend patch 2001 to add autobenches=false so that the benches
+are really disabled
+
+ -- Peter Michael Green Tue, 15 Aug 2023 16:01:55 +
+
rust-rustls-webpki (0.101.3-1) unstable; urgency=medium
[ upstream ]
diff -Nru rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
--- rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
2023-08-13 11:24:24.0 +
+++ rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
2023-08-15 15:56:54.0 +
@@ -1,11 +1,22 @@
-Description: drop bench-only build-dependencies
+Description: drop bench-only build-dependencies and disable benches
Author: Jonas Smedegaard
-Last-Update: 2023-07-29
+Author: Peter Michael Green
+Last-Update: 2023-08-15
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
a/Cargo.toml
-+++ b/Cargo.toml
-@@ -72,9 +72,6 @@
+Index: rust-rustls-webpki-0.101.3/Cargo.toml
+===
+--- rust-rustls-webpki-0.101.3.orig/Cargo.toml
rust-rustls-webpki-0.101.3/Cargo.toml
+@@ -22,6 +22,7 @@ name = "rustls-webpki"
+ readme = "README.md"
+ repository = "https://github.com/rustls/webpki";
+ version = "0.101.3"
++autobenches = false
+
+ include = [
+ "Cargo.toml",
+@@ -72,9 +73,6 @@ untrusted = "0.7.1"
[dev-dependencies]
base64 = "0.21"
@@ -15,7 +26,7 @@
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
-@@ -94,11 +91,6 @@
+@@ -94,11 +92,6 @@ lto = true
debug-assertions = false
codegen-units = 1
diff -Nru
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
---
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
1970-01-01 00:00:00.0 +
+++
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
2023-08-15 16:01:55.0 +
@@ -0,0 +1,43 @@
+Description: allow using an environment variable to specify where to find
test-data
+ This allows the test data, which is included in the source package, but not
in the
+ binary package to be used during the autopkgtest.
+Author: Peter Michael Green
+Last-Update: 2023-08-15
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+diff -urN rustls-webpki-0.101.3/build.rs rustls-webpki-0.101.3/build.rs
+--- rustls-webpki-0.101.3/build.rs 1970-01-01 00:00:00.0 +
rustls-webpki-0.101.3/build.rs 2023-08-15 17:04:24.774078929 +
+@@ -0,0 +1,7 @@
++use std::env::VarError::NotPresent;
++fn main() {
++println!("cargo:rerun-if-env-changed=SOURCEPACKAGEDIR");
++if std::env::var("SOURCEPACKAGEDIR") == Err(NotPresent) {
++
println!("cargo:rustc-env=SOURCEPACKAGEDIR={}",std::env::current_dir().unwrap().to_str().unwrap());
++}
++}
+diff -urN rustls-webpki-0.101.3/src/signed_data.rs
rustls-webpki-0.101.3/src/signed_data.rs
+--- rustls-webpki-0.101.3/src/signed_data.rs 2006-07-24 01:21:28.0
+
rustls-webpki-0.101.
Bug#1042194: netavark: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~)
tags 1042194 +patch
thanks
During a rebuild of all packages in sid, your package failed to build
on amd64.
The attached patch makes netavark build again (note: some of the packages
it depends on have only just been accepted, so it may be a little time
before binaries are available in sid).diff -Nru netavark-1.4.0/debian/changelog netavark-1.4.0/debian/changelog
--- netavark-1.4.0/debian/changelog 2023-02-03 11:31:00.0 +
+++ netavark-1.4.0/debian/changelog 2023-08-10 22:42:37.0 +
@@ -1,3 +1,13 @@
+netavark (1.4.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream patches for new netlink crates. (Closes: #1042194)
+ * Bump env-logger dependency.
+ * Stop patching zbus cargo dependency and update debian dependency, Debian
+now has zbus 3.x
+
+ -- Peter Michael Green Thu, 10 Aug 2023 22:42:37 +
+
netavark (1.4.0-3) unstable; urgency=medium
* Install aardvark-dns by default with netavark
diff -Nru netavark-1.4.0/debian/control netavark-1.4.0/debian/control
--- netavark-1.4.0/debian/control 2023-02-03 11:31:00.0 +
+++ netavark-1.4.0/debian/control 2023-08-10 22:42:37.0 +
@@ -9,7 +9,7 @@
librust-atty-dev,
librust-chrono-dev,
librust-clap-3+derive-dev (>= 3.2.23),
- librust-env-logger-dev (>> 0.9),
+ librust-env-logger-0.10-dev,
librust-futures-dev,
librust-fs2-dev,
librust-humantime-dev,
@@ -17,7 +17,7 @@
librust-iptables-dev,
librust-libc-dev,
librust-log-dev,
- librust-netlink-packet-route-dev,
+ librust-netlink-packet-route-0.17-dev,
librust-nix-dev,
librust-rand-dev,
librust-rtnetlink-dev,
@@ -31,7 +31,7 @@
librust-termcolor-dev,
librust-tokio+full-dev,
librust-url-dev,
- librust-zbus-dev (>= 1.9.2-4),
+ librust-zbus-3-dev (>= 3.6.1),
librust-zvariant-dev,
libstd-rust-dev,
rustc:native ,
diff -Nru netavark-1.4.0/debian/patches/netlink-0.5.patch
netavark-1.4.0/debian/patches/netlink-0.5.patch
--- netavark-1.4.0/debian/patches/netlink-0.5.patch 1970-01-01
00:00:00.0 +
+++ netavark-1.4.0/debian/patches/netlink-0.5.patch 2023-08-10
22:42:37.0 +
@@ -0,0 +1,65 @@
+This patch is based on the upstream commit described below, adapted for
+use in the Debian package by Peter Michael Green.
+
+commit 88a2a7a5a896d9b64d48b95f12e78cf91ee2b05f
+Author: Paul Holzinger
+Date: Fri Feb 17 15:03:19 2023 +0100
+
+update netlink-packet-{route,core} to 0.15 and 0.5
+
+They contain breaking changes but nothing major, just moved same type
+definitions.
+
+Signed-off-by: Paul Holzinger
+
+diff --git a/Cargo.toml b/Cargo.toml
+index de0b465..2620f80 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -44,2 +44,2 @@ zbus = { version = "3.10.0" }
+-netlink-packet-route = "0.13"
+-netlink-packet-core = "0.4.2"
++netlink-packet-route = "0.15"
++netlink-packet-core = "0.5"
+diff --git a/src/network/netlink.rs b/src/network/netlink.rs
+index 4b11a28..dcf165a 100644
+--- a/src/network/netlink.rs
b/src/network/netlink.rs
+@@ -9,11 +9,14 @@ use crate::{
+ wrap,
+ };
+ use log::{info, trace};
++use netlink_packet_core::{
++NetlinkHeader, NetlinkMessage, NetlinkPayload, NLM_F_ACK, NLM_F_CREATE,
NLM_F_DUMP, NLM_F_EXCL,
++NLM_F_REQUEST,
++};
+ use netlink_packet_route::{
+ nlas::link::{Info, InfoData, InfoKind, Nla},
+-AddressMessage, LinkMessage, NetlinkHeader, NetlinkMessage,
NetlinkPayload, RouteMessage,
+-RtnlMessage, AF_INET, AF_INET6, IFF_UP, NLM_F_ACK, NLM_F_CREATE,
NLM_F_DUMP, NLM_F_EXCL,
+-NLM_F_REQUEST, RTN_UNICAST, RTPROT_STATIC, RTPROT_UNSPEC,
RT_SCOPE_UNIVERSE, RT_TABLE_MAIN,
++AddressMessage, LinkMessage, RouteMessage, RtnlMessage, AF_INET,
AF_INET6, IFF_UP, RTN_UNICAST,
++RTPROT_STATIC, RTPROT_UNSPEC, RT_SCOPE_UNIVERSE, RT_TABLE_MAIN,
+ };
+ use netlink_sys::{protocols::NETLINK_ROUTE, SocketAddr};
+
+@@ -369,10 +372,7 @@ impl Socket {
+ }
+
+ fn send(&mut self, msg: RtnlMessage, flags: u16) -> NetavarkResult<()> {
+-let mut packet = NetlinkMessage {
+-header: NetlinkHeader::default(),
+-payload: NetlinkPayload::from(msg),
+-};
++let mut packet = NetlinkMessage::new(NetlinkHeader::default(),
NetlinkPayload::from(msg));
+ packet.header.flags = NLM_F_REQUEST | flags;
+ packet.header.sequence_number = {
+ self.sequence_number += 1;
+@@ -440,6 +440,7 @@ impl Socket {
+ return Ok(result);
+ }
+ }
++_ => {}
+ };
+
+ offset += rx_packet.header.length as usize;
diff -Nru netavark-1.4.0/debian/patches/netlink-0.7.patch
netavark-1.4.0/debian/patches/netlink-0.7.patch
--- netavark-1.4.0/debian/patches/netlink-0.7.patch 1970-01-01
00:00:00.0 +
+++ netavark-1.4.0/debian/patches/netlin
Bug#1043421: rust-rustls FTBFS: file not found error.
Package: rust-rustls Version: 0.21.6-1 Severity: serious rust-rustls fails to build from source. error: couldn't read rustls/build.rs: No such file or directory (os error 2) error: could not compile `rustls` due to previous error
Bug#1043418: rust-rustls-webpki - autopkgtest failure, file not found errors.
Package: rust-rustls-webpki Version: 0.101.2-2 Severity: serious The autopkgtest for rust-rustls-webpki is failing with a bunch of file not found errors. the first of which is pasted below. 199s error: couldn't read src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-spki-params-null.pem: No such file or directory (os error 2) 199s--> src/signed_data.rs:443:13 199s | 199s 443 | / include_bytes!(concat!( 199s 444 | | "../third-party/chromium/data/verify_signed_data/", 199s 445 | | $file_name 199s 446 | | )) 199s | |__^ 199s ... 199s 573 | / test_verify_signed_data!( 199s 574 | | test_ecdsa_prime256v1_sha512_spki_params_null, 199s 575 | | "ecdsa-prime256v1-sha512-spki-params-null.pem", 199s 576 | | Err(Error::UnsupportedSignatureAlgorithm) 199s 577 | | ); 199s | |_- in this macro invocation 199s | 199s = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
Bug#1043279: musicbrainzngs build-depends on dropped package
Package: musicbrainzngs Version: 0.7.1-4 Severity: serious Tags: trixie, sid Justification: rc policy - "Packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable musicbrainzngs build-depends on python-libdiscid-doc which is no longer built by the python-libdiscid source package. It is still present in unstable as a cruft package, but is completely gone from testing.
Bug#1043176: sccache - update for new serial-test
Package: sccache Severity: serious Tags: trixie, sid I just updated the serial-test crate to version 2.0. sccache needs a small update to the Debian dependency to match. (the Cargo dependency already allows both versions). Debdiff attatched. diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog --- sccache-0.5.4/debian/changelog 2023-07-30 16:13:02.0 + +++ sccache-0.5.4/debian/changelog 2023-08-06 13:14:32.0 + @@ -1,3 +1,11 @@ +sccache (0.5.4-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update Debian dependency on serial-test to version 2 +(Cargo dependencies already allow it). + + -- root Sun, 06 Aug 2023 13:14:32 + + sccache (0.5.4-7) unstable; urgency=medium * fix yet again: reduce lto further on mipsel diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control --- sccache-0.5.4/debian/control2023-07-27 16:54:09.0 + +++ sccache-0.5.4/debian/control2023-08-06 13:13:12.0 + @@ -58,7 +58,7 @@ librust-serde-1+default-dev, librust-serde-1+derive-dev, librust-serde-json-1+default-dev, - librust-serial-test-0.9+default-dev , + librust-serial-test-2+default-dev , librust-sha2-0.10+default-dev, librust-strip-ansi-escapes-0.1+default-dev, librust-tar-0.4+default-dev,
Bug#1043175: rust-rustls-native-certs - update for new serial-test
Package: rust-rustls-native-certs Severity: serious Tags: trixie, sid I just updated the serial-test crate to version 2.0. rust-rustls-native-certs needs a small update to the Debian dependency to match. (the Cargo dependency already allows both versions). Debdiff attatched. diff -Nru rust-rustls-native-certs-0.6.3/debian/changelog rust-rustls-native-certs-0.6.3/debian/changelog --- rust-rustls-native-certs-0.6.3/debian/changelog 2023-07-29 21:03:41.0 + +++ rust-rustls-native-certs-0.6.3/debian/changelog 2023-08-06 13:08:55.0 + @@ -1,3 +1,11 @@ +rust-rustls-native-certs (0.6.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update debian dependencies for rust-serial-test 2 +(Cargo dependencies already allow that version). + + -- Peter Michael Green Sun, 06 Aug 2023 13:08:55 + + rust-rustls-native-certs (0.6.3-1) unstable; urgency=medium [ upstream ] diff -Nru rust-rustls-native-certs-0.6.3/debian/control rust-rustls-native-certs-0.6.3/debian/control --- rust-rustls-native-certs-0.6.3/debian/control 2023-07-29 21:03:41.0 + +++ rust-rustls-native-certs-0.6.3/debian/control 2023-08-06 13:07:44.0 + @@ -9,7 +9,7 @@ librust-rustls-0.21+default-dev , librust-rustls-pemfile-1+default-dev , librust-rustls-webpki-0.101+default-dev , - librust-serial-test-0.9+default-dev , + librust-serial-test-2+default-dev , librust-untrusted-0.7+default-dev , libstring-shellquote-perl, Maintainer: Jonas Smedegaard diff -Nru rust-rustls-native-certs-0.6.3/debian/tests/control rust-rustls-native-certs-0.6.3/debian/tests/control --- rust-rustls-native-certs-0.6.3/debian/tests/control 2023-07-29 21:03:41.0 + +++ rust-rustls-native-certs-0.6.3/debian/tests/control 2023-08-06 13:08:50.0 + @@ -8,7 +8,7 @@ librust-rustls-0.21+default-dev, librust-rustls-native-certs-0.6-dev, librust-rustls-webpki-0.101+default-dev, - librust-serial-test-0.9+default-dev, + librust-serial-test-2+default-dev, librust-untrusted-0.7+default-dev, Restrictions: allow-stderr, flaky @@ -22,7 +22,7 @@ librust-rustls-0.21+default-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-webpki-0.101+default-dev, - librust-serial-test-0.9+default-dev, + librust-serial-test-2+default-dev, librust-untrusted-0.7+default-dev, Restrictions: allow-stderr, flaky @@ -36,6 +36,6 @@ librust-rustls-0.21+default-dev, librust-rustls-native-certs-0.6-dev, librust-rustls-webpki-0.101+default-dev, - librust-serial-test-0.9+default-dev, + librust-serial-test-2+default-dev, librust-untrusted-0.7+default-dev, Restrictions: allow-stderr, flaky
Bug#1043174: precious - update for new serial-test
Package: precious Severity: serious Tags: trixie, sid I just updated the serial-test crate to version 2.0. Precious needs a small update to the Debian dependency to match. (the Cargo dependency already allows both versions). Debdiff attatched.diff -Nru precious-0.5.1+20230704/debian/changelog precious-0.5.1+20230704/debian/changelog --- precious-0.5.1+20230704/debian/changelog2023-07-11 21:20:29.0 + +++ precious-0.5.1+20230704/debian/changelog2023-08-06 12:48:08.0 + @@ -1,3 +1,11 @@ +precious (0.5.1+20230704-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update Debian dependency on serial-test to 2.0. +(cargo dependency already allows the new version) + + -- Peter Michael Green Sun, 06 Aug 2023 12:48:08 + + precious (0.5.1+20230704-1) unstable; urgency=medium [ upstream ] diff -Nru precious-0.5.1+20230704/debian/control precious-0.5.1+20230704/debian/control --- precious-0.5.1+20230704/debian/control 2023-07-11 21:20:29.0 + +++ precious-0.5.1+20230704/debian/control 2023-08-06 12:47:55.0 + @@ -33,7 +33,7 @@ librust-regex-1+default-dev (>= 1.7), librust-serde-1+default-dev (>= 1.0.147), librust-serde-1+derive-dev (>= 1.0.147), - librust-serial-test-0.9+default-dev , + librust-serial-test-2.0+default-dev , librust-tempfile-3+default-dev (>= 3.3) , librust-test-case-2+default-dev , librust-thiserror-1+default-dev (>= 1.0.37),
Bug#1042983: squeekboard - rust gtk stack update.
Package: squeekboard
Version: 1.22.0-3
Severity: serious
The rust gtk stack is currently being updated in Debian,
squeekboard needs a small patch
Please test that squeekboard works with this patch and
if-so apply it.diff -Nru squeekboard-1.22.0/debian/changelog
squeekboard-1.22.0/debian/changelog
--- squeekboard-1.22.0/debian/changelog 2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/changelog 2023-08-03 16:41:53.0 +
@@ -1,3 +1,10 @@
+squeekboard (1.22.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Update for gtk-rs 0.17.
+
+ -- Peter Michael Green Thu, 03 Aug 2023 16:41:53 +
+
squeekboard (1.22.0-3) unstable; urgency=medium
* debian: update build dependencies.
diff -Nru squeekboard-1.22.0/debian/control squeekboard-1.22.0/debian/control
--- squeekboard-1.22.0/debian/control 2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/control 2023-08-03 16:39:01.0 +
@@ -17,11 +17,11 @@
librust-aho-corasick-dev,
librust-bitflags-1-dev (>= 1.0),
librust-clap-4+std-dev (>= 4.0),
- librust-gio+v2-58-dev (>= 0.16),
- librust-glib+v2-58-dev (>= 0.16),
- librust-glib-sys-dev (>= 0.16),
- librust-gtk+v3-24-dev (>= 0.16),
- librust-gtk-sys-dev (>= 0.16),
+ librust-gio+v2-58-dev (>= 0.17),
+ librust-glib+v2-58-dev (>= 0.17),
+ librust-glib-sys-dev (>= 0.17),
+ librust-gtk+v3-24-dev (>= 0.17),
+ librust-gtk-sys-dev (>= 0.17),
librust-maplit-1-dev (>= 1.0),
librust-serde-derive-1-dev (>= 1.0),
librust-serde-yaml-0.8-dev (>= 0.8),
diff -Nru squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch
squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch
--- squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch1970-01-01
00:00:00.0 +
+++ squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch2023-08-03
16:41:53.0 +
@@ -0,0 +1,56 @@
+Index: squeekboard-1.22.0/Cargo.deps.newer
+===
+--- squeekboard-1.22.0.orig/Cargo.deps.newer
squeekboard-1.22.0/Cargo.deps.newer
+@@ -10,30 +10,30 @@ zvariant_derive = "2.10.*"
+ xkbcommon = { version = "0.5.*", features = ["wayland"] }
+
+ [dependencies.cairo-rs]
+-version = "0.16.*"
++version = "0.17.*"
+
+ [dependencies.cairo-sys-rs]
+-version = "0.16.*"
++version = "0.17.*"
+
+ [dependencies.gdk]
+-version = "0.16.*"
++version = "0.17.*"
+
+ [dependencies.gio]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+
+ [dependencies.glib]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+
+ [dependencies.glib-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+
+ [dependencies.gtk]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+
+ [dependencies.gtk-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+Index: squeekboard-1.22.0/src/popover.rs
+===
+--- squeekboard-1.22.0.orig/src/popover.rs
squeekboard-1.22.0/src/popover.rs
+@@ -326,7 +326,7 @@ pub fn show(
+ let layout_action = gio::SimpleAction::new_stateful(
+ "layout",
+ Some(current_layout_name.to_variant().type_()),
+-¤t_layout_name.to_variant()
++current_layout_name.to_variant()
+ );
+
+ let menu_inner = menu.clone();
diff -Nru squeekboard-1.22.0/debian/patches/series
squeekboard-1.22.0/debian/patches/series
--- squeekboard-1.22.0/debian/patches/series2023-07-01 15:14:45.0
+
+++ squeekboard-1.22.0/debian/patches/series2023-08-03 16:40:41.0
+
@@ -2,3 +2,4 @@
0002-src-popover-fix-build-with-newer-gtk-rs.patch
0003-src-style-fix-build-with-newer-gtk-rs.patch
0004-Cargo.-use-xkbcommon-v0.5.patch
+0005-gtk-rs-0.17.patch
Bug#1042885: / Bug# 1042886 Acknowledgement (initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1)
Bug#1042885 / Bug# 1042886 Hello, as of Bullseye -rt-23 kernel part : it seems CONFIG_AS_VERSION=23502 was absent in the kernel config. this and or 5.10 dev fixed the rt-23 bullseye kernel boot but not the bookworm issue with initrams. #keypoint verify if this trigger can be the cause of dysfunct mkinitramfs initramfs-tools . i suspect dysfunct zstd 1.54 andor 0.142 initramfstools are the issue n o t 1.48 +0.140 bullseye greetings Original Message From: CHRISTIAN PETER KISS Sent: Wednesday, 2 August 2023 14:49 To: car...@deian.org Subject: Salvatore this Bug#1042885 isforyou : Acknowledgement (initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1) Original Message From: Debian Bug Tracking System Sent: Wednesday, 2 August 2023 13:54 To: Christian Kiss Subject: Bug#1042885: Acknowledgement (initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1) Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1042885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042885. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to christianpeterk...@yahoo.com (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian kernel team If you wish to submit further information on this problem, please send it to 1042...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1042885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042315: wfuzz: FTBFS: make: *** [debian/rules:8: clean] Error 25
Control: tags -1 + patch See https://salsa.debian.org/pkg-security-team/wfuzz/-/merge_requests/1
Bug#1042419: rust-ureq - update for new cookie-store
On 28/07/2023 08:07, Jonas Smedegaard wrote: Control: block -1 by 1042427 Quoting Peter Green (2023-07-28 05:20:53) I just updated rust-cookie-store. Ureq needs it's debian dependencies adjusting to account for this (the cargo dependencies already allow the new version. Thanks for the update, and the notice. Your package update is however blocked by bug#1042427 :-( Looks like this is now fixed. https://tracker.debian.org/news/1448563/accepted-rust-digest-0107-2-source-into-unstable/ * Enable oid feature and const-oid optional dependency
Bug#1042419: rust-ureq - update for new cookie-store
Package: rust-ureq Tags: trixie, sid Severity: serious I just updated rust-cookie-store. Ureq needs it's debian dependencies adjusting to account for this (the cargo dependencies already allow the new version. Debdiff attatched, I may or may not NMU this later.diff -Nru rust-ureq-2.7.1/debian/changelog rust-ureq-2.7.1/debian/changelog --- rust-ureq-2.7.1/debian/changelog2023-07-16 22:38:59.0 + +++ rust-ureq-2.7.1/debian/changelog2023-07-28 02:54:32.0 + @@ -1,3 +1,11 @@ +rust-ureq (2.7.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump debian dependency on cookie_store to 0.19 +(cargo dependency already allows this version) + + -- Peter Michael Green Fri, 28 Jul 2023 02:54:32 + + rust-ureq (2.7.1-1) unstable; urgency=medium [ upstream ] diff -Nru rust-ureq-2.7.1/debian/control rust-ureq-2.7.1/debian/control --- rust-ureq-2.7.1/debian/control 2023-07-16 10:47:12.0 + +++ rust-ureq-2.7.1/debian/control 2023-07-28 02:54:27.0 + @@ -8,7 +8,7 @@ librust-brotli-decompressor-2+default-dev , librust-chunked-transfer-1+default-dev , librust-cookie-0.16-dev , - librust-cookie-store-0.16+preserve-order-dev , + librust-cookie-store-0.19+preserve-order-dev , librust-encoding-rs-0.8+default-dev , librust-env-logger-0.9+default-dev , librust-flate2-1+default-dev (>= 1.0.22) , @@ -42,7 +42,7 @@ librust-brotli-decompressor-2+default-dev, librust-chunked-transfer-1+default-dev, librust-cookie-0.16-dev, - librust-cookie-store-0.16+preserve-order-dev, + librust-cookie-store-0.19+preserve-order-dev, librust-encoding-rs-0.8+default-dev, librust-flate2-1+default-dev (>= 1.0.22), librust-http-0.2+default-dev,
Bug#1042413: rust-rustls-webpki - autopkgtest failure building with only the alloc feature is broken.
Package: rust-rustls-webpki Version: 0.101.1 Severity: serious building the rustls-webpki crate with only the alloc feature (and not the std feature) is broken. I took a look at fixing it but came to the conclusion that doing so was beyond what was reasonable to do in a distribution patch. Since the only reverse dependency is rust-rustls which unconditionally enables the std and alloc features, I think it probably makes sense to just remove/disable the "alloc feature only" autopkgtest for now. diff -Nru rust-rustls-webpki-0.101.1/debian/changelog rust-rustls-webpki-0.101.1/debian/changelog --- rust-rustls-webpki-0.101.1/debian/changelog 2023-07-20 14:22:18.0 + +++ rust-rustls-webpki-0.101.1/debian/changelog 2023-07-27 21:08:16.0 + @@ -1,3 +1,12 @@ +rust-rustls-webpki (0.101.1-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove "--no-default-features --features alloc" autopkgtest, the +upstream code fails to build when built with only the alloc +feature. + + -- Peter Michael Green Thu, 27 Jul 2023 21:08:16 + + rust-rustls-webpki (0.101.1-2) unstable; urgency=medium * no-changes source-only upload to enable testing migration diff -Nru rust-rustls-webpki-0.101.1/debian/tests/control rust-rustls-webpki-0.101.1/debian/tests/control --- rust-rustls-webpki-0.101.1/debian/tests/control 2023-07-16 16:52:39.0 + +++ rust-rustls-webpki-0.101.1/debian/tests/control 2023-07-27 21:08:04.0 + @@ -17,15 +17,6 @@ Restrictions: allow-stderr Test-Command: /usr/share/cargo/bin/cargo-auto-test rustls-webpki 0.101.1 - --all-targets --no-default-features --features alloc -Features: test-name=rust-rustls-webpki-0.101:alloc -Depends: - dh-cargo, - librust-base64-0.21+default-dev, - librust-rustls-webpki-0.101+alloc-dev, -Restrictions: allow-stderr - -Test-Command: /usr/share/cargo/bin/cargo-auto-test rustls-webpki 0.101.1 --all-targets Features: test-name=rust-rustls-webpki-0.101:default Depends:
Bug#1042401: sccache FTBFS multiple issues
Package: sccache
Version: 0.5.4
Severity: serious
sccache has a couple of FTBFS issues.
The first is that a couple of dependencies have been updated, dealing
with this is a simple matter of dropping patches and updating
dependencies.
The second is that the build runs out of address space on mipsel.
The workaround seems to be to use "thin" lto rather than full
lto. Unfortunately i'm not aware of a good way to do this other
than editing Cargo.toml. I did so with sed in debian/rules,
conditioned behind architecture conditionals.
Debdiff attatched, I may or may not NMU this later.diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog 2023-07-05 18:31:19.0 +
+++ sccache-0.5.4/debian/changelog 2023-07-25 23:06:38.0 +
@@ -1,3 +1,14 @@
+sccache (0.5.4-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop patch 2023 and update debian dependency, directories 5.x is now in
+Debian.
+ * Drop patch 2016 and update debian dependency, daemonise 0.5 is now in
+Debian.
+ * Use thin lto on mipsel to avoid running out of address space.
+
+ -- Peter Michael Green Tue, 25 Jul 2023 23:06:38 +
+
sccache (0.5.4-2) unstable; urgency=medium
* drop patch 2019, obsoleted by Debian package updates
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-06-27 13:20:11.0 +
+++ sccache-0.5.4/debian/control2023-07-25 23:06:38.0 +
@@ -22,8 +22,8 @@
librust-chrono-0.4+default-dev,
librust-clap-4+default-dev,
librust-counted-array-0.1+default-dev,
- librust-daemonize-0.4+default-dev,
- librust-directories-4+default-dev,
+ librust-daemonize-0.5+default-dev,
+ librust-directories-5+default-dev,
librust-env-logger-0.9+default-dev,
librust-encoding-0.2+default-dev,
librust-filetime-0.2+default-dev,
diff -Nru sccache-0.5.4/debian/patches/2016_daemonize.patch
sccache-0.5.4/debian/patches/2016_daemonize.patch
--- sccache-0.5.4/debian/patches/2016_daemonize.patch 2023-06-27
13:26:13.0 +
+++ sccache-0.5.4/debian/patches/2016_daemonize.patch 1970-01-01
00:00:00.0 +
@@ -1,17 +0,0 @@
-Description: relax dependency on crate daemonize
- Needed to match Debian-packaged daemonize v0.4.1.
-Author: Jonas Smedegaard
-Last-Update: 2023-05-21
-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
a/Cargo.toml
-+++ b/Cargo.toml
-@@ -108,7 +108,7 @@
- serial_test = ">= 0.9, < 3"
-
- [target.'cfg(unix)'.dependencies]
--daemonize = "0.5"
-+daemonize = ">= 0.4, < 0.6"
-
- [features]
- all = [
diff -Nru sccache-0.5.4/debian/patches/2023_directories.patch
sccache-0.5.4/debian/patches/2023_directories.patch
--- sccache-0.5.4/debian/patches/2023_directories.patch 2023-07-05
18:31:19.0 +
+++ sccache-0.5.4/debian/patches/2023_directories.patch 1970-01-01
00:00:00.0 +
@@ -1,17 +0,0 @@
-Description: relax dependency on crate directories
- Needed to match Debian-packaged directories v4.0.1.
-Author: Jonas Smedegaard
-Last-Update: 2023-05-21
-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
a/Cargo.toml
-+++ b/Cargo.toml
-@@ -33,7 +33,7 @@
- byteorder = "1.0"
- bytes = "1"
- clap = { version = "4.1.11", features = ["derive", "env", "wrap_help"] }
--directories = "5.0.0"
-+directories = ">= 4, < 6"
- encoding = "0.2"
- env_logger = ">= 0.9, < 0.11"
- filetime = "0.2"
diff -Nru sccache-0.5.4/debian/patches/series
sccache-0.5.4/debian/patches/series
--- sccache-0.5.4/debian/patches/series 2023-07-04 08:18:27.0 +
+++ sccache-0.5.4/debian/patches/series 2023-07-25 23:06:38.0 +
@@ -15,9 +15,7 @@
2013_is-terminal.patch
2014_hyper.patch
2015_uuid.patch
-2016_daemonize.patch
2017_memmap2.patch
2018_regex.patch
2021_chrono.patch
2022_reqwest_trust-dns.patch
-2023_directories.patch
diff -Nru sccache-0.5.4/debian/rules sccache-0.5.4/debian/rules
--- sccache-0.5.4/debian/rules 2023-07-05 18:31:19.0 +
+++ sccache-0.5.4/debian/rules 2023-07-25 23:06:38.0 +
@@ -26,6 +26,10 @@
dh $@ --buildsystem cargo
override_dh_auto_build:
+ #use thin rather than full lto on mipsel to avoid running out of
address space.
+ifeq ($(DEB_HOST_ARCH),mipsel)
+ sed -i 's/lto = true/lto = "thin"/' Cargo.toml
+endif
dh_auto_build --buildsystem cargo -- $(CARGO_BUILD_ARGS)
# ensure ccache is not in use during tests
@@ -43,3 +47,8 @@
--name "a fast C/C++/Rust compiler cache" \
--output $@ $< \
|| { $< --help; false; }
+
+ifeq ($(DEB_HOST_ARCH),mipsel)
+execute_after_dh_auto_clean:
+ sed -i 's/lto = "thin"/lto = true/' Cargo.toml
+endif
Bug#1042156: rust-droid-juicer- call for testing of goblin update.
I've just patched rust-droid-juicer to use the new version of goblin. It built fine, but given the lack of any meaningful tests in the package I don't feel comfortable uploading it to unstable until someone more familiar with the software has tested it. I have uploaded the patched version to experimental to make it easier for people to test.
Bug#1042064: rust-rustls-0.20, autopkgtest failure, missing test ca
Package: rust-rustls-0.20 Version: 0.20.8-8 Severity: serious The autopkgtests for rust-rustls-0.20 fail due to a missing test CA. I missed this when filing my previous bug due to not testing in a clean environment. I can think of several potential solutions for this. 1. Have the tests for the 0.20 package depend on the 0.21 package to get the test CA. 2. Include a copy of the test CA in the 0.20 package, presumably this would have to be in a different path to avoid file conflicts 3. Skip the tests that involve the test CA. I will leave it to your judgement as maintainer to decide what solution to implement.
Bug#1042063: rust-rustls- autopkgtest failure due to error in test dependency
Package: rust-rustls Version: 0.21.5-4 Severity: serious The autopkgtest for rust-bencher depends on librust-bencher-0.4+default-dev, however version 0.4 of bencher does not exist, so I presume this was a typo. After fixing the dependency the autopkgtest passed in my local testing. A debdiff is attatched, I may or may not NMU this later.diff -Nru rust-rustls-0.21.5/debian/changelog rust-rustls-0.21.5/debian/changelog --- rust-rustls-0.21.5/debian/changelog 2023-07-22 09:04:42.0 + +++ rust-rustls-0.21.5/debian/changelog 2023-07-25 23:24:10.0 + @@ -1,3 +1,10 @@ +rust-rustls (0.21.5-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix bencher test dependency. + + -- Peter Michael Green Tue, 25 Jul 2023 23:24:10 + + rust-rustls (0.21.5-4) unstable; urgency=medium * fix: depend on package for crate rustls-webpki (not webpki) diff -Nru rust-rustls-0.21.5/debian/tests/control rust-rustls-0.21.5/debian/tests/control --- rust-rustls-0.21.5/debian/tests/control 2023-07-22 09:02:51.0 + +++ rust-rustls-0.21.5/debian/tests/control 2023-07-25 23:24:10.0 + @@ -5,7 +5,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-log-0.4+default-dev, @@ -28,7 +28,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -49,7 +49,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -70,7 +70,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -91,7 +91,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -112,7 +112,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -134,7 +134,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -155,7 +155,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-mio-0.8+default-dev, @@ -176,7 +176,7 @@ Depends: dh-cargo (>= 18), librust-base64-0.21+default-dev, - librust-bencher-0.4+default-dev, + librust-bencher-0.1+default-dev (>= 0.1.5), librust-docopt-1+default-dev, librust-env-logger-0.9+default-dev, librust-log-0.4+default-dev,
Bug#1041908: rust-rustls-0.20: broken test dependencies.
Package: rust-rustls-0.20 Version: 0.20.8-7 Severity: serious Tags: patch rust-rustls-0.20 has test-dependencies that contain "0.20-0.20", these are unsatisfiable and I assume are the result of a search and replace gone wrong. After replacing "0.20-0.20" with just "0.20" the autopkgtest passes successfully. Debdiff attatched, I may or may not NMU this later.diff -Nru rust-rustls-0.20-0.20.8/debian/changelog rust-rustls-0.20-0.20.8/debian/changelog --- rust-rustls-0.20-0.20.8/debian/changelog2023-07-20 14:31:37.0 + +++ rust-rustls-0.20-0.20.8/debian/changelog2023-07-25 08:07:49.0 + @@ -1,3 +1,10 @@ +rust-rustls-0.20 (0.20.8-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix autopkgtest dependencies. + + -- Peter Michael Green Tue, 25 Jul 2023 08:07:49 + + rust-rustls-0.20 (0.20.8-7) unstable; urgency=medium * no-changes source-only upload to enable testing migration diff -Nru rust-rustls-0.20-0.20.8/debian/tests/control rust-rustls-0.20-0.20.8/debian/tests/control --- rust-rustls-0.20-0.20.8/debian/tests/control2023-07-20 14:30:29.0 + +++ rust-rustls-0.20-0.20.8/debian/tests/control2023-07-25 08:07:38.0 + @@ -13,7 +13,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20-dev, + librust-rustls-0.20-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-rustversion-1-dev, @@ -35,7 +35,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+dangerous-configuration-dev, + librust-rustls-0.20+dangerous-configuration-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-serde-1+default-dev, @@ -56,7 +56,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+quic-dev, + librust-rustls-0.20+quic-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-serde-1+default-dev, @@ -77,7 +77,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+secret-extraction-dev, + librust-rustls-0.20+secret-extraction-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-dev, librust-serde-1+default-dev, @@ -98,7 +98,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+tls12-dev, + librust-rustls-0.20+tls12-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-dev, librust-serde-1+default-dev, @@ -119,7 +119,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+read-buf-dev, + librust-rustls-0.20+read-buf-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-dev, librust-rustversion-1-dev, @@ -141,7 +141,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20-dev, + librust-rustls-0.20-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-serde-1+default-dev, @@ -162,7 +162,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+default-dev, + librust-rustls-0.20+default-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-serde-1+default-dev, @@ -184,7 +184,7 @@ librust-mio-0.8+net-dev, librust-mio-0.8+os-poll-dev, librust-regex-1+default-dev, - librust-rustls-0.20-0.20+logging-dev, + librust-rustls-0.20+logging-dev, librust-rustls-native-certs-0.6+default-dev, librust-rustls-pemfile-1+default-dev, librust-serde-1+default-dev,
Bug#1041384: librust-derive-builder-dev: impossible to install
Version: 0.12.0-1 rust-derive-builder has now been updated to match rust-derive-builder-core.
Bug#1037790: nix: ftbfs with GCC-13
control: tag -1 + pending
On Wed, Jun 14, 2023 at 09:29:02AM +, Matthias Klose wrote:
> Package: src:nix
> Version: 2.8.0-1.1
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13
>
> [This bug is targeted to the upcoming trixie release]
[snip]
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> severity of this report will be raised before the trixie release.
>
> The full build log can be found at:
> http://qa-logs.debian.net/2023/05/22/logs/nix_2.8.0-1.1_unstable_gccexp.log
> The last lines of the build log are at the end of this report.
[snip]
> src/libutil/json.cc: In function ‘void nix::toJSON(std::ostream&, const
> char*, const char*)’:
> src/libutil/json.cc:33:22: error: ‘uint16_t’ was not declared in this scope
>33 | put(hex[(uint16_t(*i) >> 12) & 0xf]);
> | ^~~~
> src/libutil/json.cc:5:1: note: ‘uint16_t’ is defined in header ‘’;
> did you forget to ‘#include ’?
> 4 | #include
> +++ |+#include
> 5 |
> make[1]: *** [mk/patterns.mk:3: src/libutil/json.o] Error 1
> make[1]: *** Waiting for unfinished jobs
> make[1]: Leaving directory '/<>'
> dh_auto_build: error: make -j8 returned exit code 2
> make: *** [debian/rules:31: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
I am attaching the debdiff of the NMU that I uploaded to DELAYED/5 yesterday.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
diff -Nru nix-2.8.0/debian/changelog nix-2.8.0/debian/changelog
--- nix-2.8.0/debian/changelog 2022-10-15 13:28:28.0 +0300
+++ nix-2.8.0/debian/changelog 2023-07-22 19:16:28.0 +0300
@@ -1,3 +1,11 @@
+nix (2.8.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add the gcc13 patch to fix the build with GCC 13.
+Closes: #1037790
+
+ -- Peter Pentchev Sat, 22 Jul 2023 19:16:28 +0300
+
nix (2.8.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru nix-2.8.0/debian/patches/gcc13.patch
nix-2.8.0/debian/patches/gcc13.patch
--- nix-2.8.0/debian/patches/gcc13.patch1970-01-01 02:00:00.0
+0200
+++ nix-2.8.0/debian/patches/gcc13.patch2023-07-22 19:13:41.0
+0300
@@ -0,0 +1,17 @@
+Description: Fix the build with GCC 13
+ Include the header for the definition of the uint16_t type.
+Bug-Debian: https://bugs.debian.org/1037790
+Forwarded: no
+Author: Peter Pentchev
+Last-Update: 2023-07-22
+
+--- a/src/libutil/json.cc
b/src/libutil/json.cc
+@@ -1,6 +1,7 @@
+ #include "json.hh"
+
+ #include
++#include
+ #include
+
+ namespace nix {
diff -Nru nix-2.8.0/debian/patches/series nix-2.8.0/debian/patches/series
--- nix-2.8.0/debian/patches/series 2022-05-02 21:55:23.0 +0300
+++ nix-2.8.0/debian/patches/series 2023-07-22 19:16:28.0 +0300
@@ -4,3 +4,4 @@
fix_nix_DIR_in_doc_local_mk.patch
lowdown_does_not_declare_bsd_dep.patch
+gcc13.patch
signature.asc
Description: PGP signature
Bug#1040628: marked as pending in Dnstwist
Control: tag -1 pending Hello, Bug #1040628 in Dnstwist 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/pkg-security-team/dnstwist/-/commit/761047d3414f7a98bb436ba2986bdf0844f9ba22 Add patch to adapt to changes in pillow 10.0.0 See https://github.com/elceef/dnstwist/issues/194 Closes: #1040628, LP: #2027963 (this message was generated automatically) -- Greetings https://bugs.debian.org/1040628
Bug#1041284: rust-ureq - please update to support new serde-json
Package: rust-ureq Version: 2.7.0-1 Severity: serious Hi. A change to error reporting in serde_json 1.0.94, intended to prevent duplicate error messages broke an error-handling code-path in ureq. ureq's initial fix was to impose an upper limit on the version of serde_json. Later a proper fix was made by adding a new method to serde_json::error and changing ureq to use it. I've just updated serde_json, please update ureq to match.
Bug#1041233: [Pkg-rust-maintainers] Bug#1041233: librust-heapless-dev: impossible to install: depends on missing package librust-heapless-0.7-dev
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 Alexander Kjäll is working on it.
Bug#1040815: golang-gitlab-gitlab-org-labkit build-depends unsatisfiable due to version restriction.
Package: golang-gitlab-gitlab-org-labkit Version: 1.17.0-2 Tags: trixie, sid Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable golang-gitlab-gitlab-org-labkit build-depends on golang-google-grpc-dev:amd64 (< 1.38~) however the version of golang-google-grpc-dev in testing/unstable is now 1.38.0+really1.33.3-1
Bug#1040814: coq-quickchick build-depends on dropped transitional package.
Package: coq-quickchick Version: 2.0-1 Tags: trixie, sid Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable coq-quickchick build-depends on dune, in bullseye this was a transitional package built by the ocaml-dune source package and depending on the ocaml-dune binary package. However in ocaml-dune 3.8.2-1 the transitional package was dropped. It is still present in unstable as a cruft package but is completely gone from testing. Presumablly you need to update your build-dependency to build-depend on dune instead of ocaml-dune.
