Bug#1069575: FTBFS in experimental
Control: block -1 by 1071902 Quoting Matthias Geiger (2024-05-26 11:20:09) > I will look into updating concurrent-queue to 2.5.0 then. Please also see https://bugs.debian.org/1071902 - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1069575: FTBFS in experimental
On Sat, 25 May 2024 20:27:28 +0200 Jonas Smedegaard wrote: > Control: block -1 by 1071900 > > Quoting Jonas Smedegaard (2024-05-25 20:13:12) > > Ahh, you are talking about *async-channel* v2.3.0. Please consider in > > future to mention crate name, both in email subject and in content, to > > help disambiguate. > > > > I'll have a go at updating async-channel, and tighten dependency on that > > from async-process to see if that solves the FTBFS of async-process. > > > > Thanks for nudging, > > ...and now I remember what held me back last I had a look at this: > async-channel v2.3.0 is broken. Bugfix released with v2.3.1 was to > tighten dependency on concurrent-queue, to a version newer than what is > in Debian. > > > - Jonas > > -- Ack, I will look into updating concurrent-queue to 2.5.0 then. -- Matthias Geiger
Bug#1069575: FTBFS in experimental
Control: block -1 by 1071900 Quoting Jonas Smedegaard (2024-05-25 20:13:12) > Ahh, you are talking about *async-channel* v2.3.0. Please consider in > future to mention crate name, both in email subject and in content, to > help disambiguate. > > I'll have a go at updating async-channel, and tighten dependency on that > from async-process to see if that solves the FTBFS of async-process. > > Thanks for nudging, ...and now I remember what held me back last I had a look at this: async-channel v2.3.0 is broken. Bugfix released with v2.3.1 was to tighten dependency on concurrent-queue, to a version newer than what is in Debian. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1069575: FTBFS in experimental
Quoting Matthias Geiger (2024-05-25 17:29:45) > On Wed, 15 May 2024 22:18:38 +0200 Matthias Geiger > wrote: > > On Mon, 22 Apr 2024 19:45:07 +0200 Matthias Geiger > > wrote: > > > On Sat, 20 Apr 2024 20:36:11 +0200 Matthias Geiger > > > wrote: > > > > Source: rust-async-process > > > > Version: 1.7.0-4 > > > > Severity: important > > > > Tags: ftbfs > > > > X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net > > > > > > > > > > > > I didn't have time to investigate this yet. I'd appreciate it if you > > > > coud take a look at this as it is blocking the > > > > event-listener-transition. > > > > > > > > > > > > > 2.2.1 (the latest upstream release) should fix this. Please consider > > > uploading this version so we can proceed with the event-listener > > transition. > > > > > > > 2.3 depends on event-listener-strategy 0.5; this release should fix > > this. I will create a debdiff later and send it over. > > > Hi Jonas, > > is there anything blocking this ? Having 2.3 in exp would resolve the > FTBFS and pave the way to switch to event-listener 5 (and zbus 4.0 later > on). I am not quite sure what you are suggesting here. You write about "2.3", but "2.3" of what? As far as I am aware, the newest release of crate "async-process" is v2.1.1. [some time later] Ahh, you are talking about *async-channel* v2.3.0. Please consider in future to mention crate name, both in email subject and in content, to help disambiguate. I'll have a go at updating async-channel, and tighten dependency on that from async-process to see if that solves the FTBFS of async-process. Thanks for nudging, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1069575: FTBFS in experimental
On Wed, 15 May 2024 22:18:38 +0200 Matthias Geiger wrote: > On Mon, 22 Apr 2024 19:45:07 +0200 Matthias Geiger > wrote: > > On Sat, 20 Apr 2024 20:36:11 +0200 Matthias Geiger > > wrote: > > > Source: rust-async-process > > > Version: 1.7.0-4 > > > Severity: important > > > Tags: ftbfs > > > X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net > > > > > > > > > I didn't have time to investigate this yet. I'd appreciate it if you > > > coud take a look at this as it is blocking the > > > event-listener-transition. > > > > > > > > > 2.2.1 (the latest upstream release) should fix this. Please consider > > uploading this version so we can proceed with the event-listener > transition. > > > > 2.3 depends on event-listener-strategy 0.5; this release should fix > this. I will create a debdiff later and send it over. Hi Jonas, is there anything blocking this ? Having 2.3 in exp would resolve the FTBFS and pave the way to switch to event-listener 5 (and zbus 4.0 later on). thanks, -- Matthias Geiger Debian Maintainer
Bug#1069575: FTBFS in experimental
On Mon, 22 Apr 2024 19:45:07 +0200 Matthias Geiger wrote: > On Sat, 20 Apr 2024 20:36:11 +0200 Matthias Geiger > wrote: > > Source: rust-async-process > > Version: 1.7.0-4 > > Severity: important > > Tags: ftbfs > > X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net > > > > > > I didn't have time to investigate this yet. I'd appreciate it if you > > coud take a look at this as it is blocking the > > event-listener-transition. > > > > > 2.2.1 (the latest upstream release) should fix this. Please consider > uploading this version so we can proceed with the event-listener transition. > 2.3 depends on event-listener-strategy 0.5; this release should fix this. I will create a debdiff later and send it over. -- Matthias Geiger Debian Maintainer
Bug#1069575: FTBFS in experimental
On Sat, 20 Apr 2024 20:36:11 +0200 Matthias Geiger wrote: > Source: rust-async-process > Version: 1.7.0-4 > Severity: important > Tags: ftbfs > X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net > > > I didn't have time to investigate this yet. I'd appreciate it if you > coud take a look at this as it is blocking the > event-listener-transition. > 2.2.1 (the latest upstream release) should fix this. Please consider uploading this version so we can proceed with the event-listener transition. best, -- Matthias Geiger Debian Maintainer
Bug#1069575: FTBFS in experimental
Source: rust-async-process Version: 1.7.0-4 Severity: important Tags: ftbfs X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Jonas, asnyc-process currently fail to build in experimental: = error[E0599]: the method `next` exists for reference ``, but its trait bounds were not satisfied --> src/lib.rs:313:33 | 313 | ().next().await; | method cannot be called on `` due to unsatisfied trait bounds --> /usr/src/rustc-1.70.0/library/std/src/sync/mutex.rs:175:1 | = note: doesn't satisfy `_: Stream` | = note: doesn't satisfy `std::sync::Mutex: StreamExt` | = note: the following trait bounds were not satisfied: `::sync::Mutex: futures_lite::Stream` which is required by `::sync::Mutex: StreamExt` `std::sync::Mutex: futures_lite::Stream` which is required by `std::sync::Mutex: StreamExt` error[E0599]: no function or associated item named `new` found for struct `EventListener` in the current scope --> src/lib.rs:513:43 | 513 | let listener = EventListener::new(); | ^^^ function or associated item not found in `EventListener` error[E0277]: the `?` operator can only be applied to values that implement `Try` --> src/lib.rs:307:30 | 307 | signals: Mutex::new(Signals::new([SIGCHLD]))?, | the `?` operator cannot be applied to type `std::sync::Mutex>` | = help: the trait `Try` is not implemented for `std::sync::Mutex>` Some errors have detailed explanations: E0277, E0599. For more information about an error, try `rustc --explain E0277`. error: could not compile `async-process` due to 3 previous errors warning: build failed, waiting for other jobs to finish... dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test returned exit code 101 make: *** [debian/rules:9: binary-indep] Error 25 == I didn't have time to investigate this yet. I'd appreciate it if you coud take a look at this as it is blocking the event-listener-transition. best, werdahias - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: OpenRC (via /run/openrc), PID 1: init LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmYkCxcVHHdlcmRhaGlh c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1EhMQAKe69jDJ2+e+DEaWDfSgVhgXW8je WQ8U4WHhk38rIaKfZmxem3GfQZWj+WSeRCY07E2JHurgci82iCzKw3mp1hnAZeoV DsMsKQlNQmMnrNCk+vYgb0zjv65KN9iDjcZwuCOwm7Qy8v3N6yRru8yzHs7GsJEH tJgcUjo6lAi3MuDm0Znl35vrBvhU/oNLMUqVWb3I4Rv9/woeHllXvZtxx9Nfz7Rj ltzkLWTFbrWS1bWBCVLS3heJ980wuS9hVb+s9YYtkcy6FZDWUUZGQZ4nNKZBwAhf 5krwZMhsMTF3h22e+61wE4wIpbCVTBsWICROTXQeQLtwiWRqknFRdHOVfX8XfWSG VxGx60Zw076tRtzrZ3DvXJvztt3eKSK3pEv+ZtQjwDiQQDjpUUQyMafeMa6wHd8y Xm0AhQK4zCDHwntnHjnCUVDLp9JU1DxnUCx1CE98Iarhv5p1PUyXLRC3IXqmbvbe zbumMaKgiEkXabA1FaUJpgO5E871B1Dcod+EC8nQi5KlVGnhK8E85qY2Z/2W4wKz 1veTg1ZKKRsuaveZx6Dhn0sB0mwJVrLfgLc4kBcvtjkoFPOeA+vpPY+Rp0NAY4CJ K5as+DJyRHSNFkj23e/dvNKYQlHAfzfYIDRI5EI/gZ71c0hzrRZSJe+5Qg95I7SP EWU2XUhf6aFUO3Rc =vZWi -END PGP SIGNATURE-
