Your message dated Mon, 24 Jun 2024 17:42:54 +0200
with message-id <171924377436.255930.4424760604575176...@auryn.jones.dk>
and subject line Re: Bug#1069575: FTBFS in experimental
has caused the Debian Bug report #1069575,
regarding FTBFS in experimental
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1069575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 `&Mutex<SignalsInfo>`, but
its trait bounds were not satisfied
--> src/lib.rs:313:33
|
313 | (&self.signals).next().await;
| ^^^^ method cannot be called on
`&Mutex<SignalsInfo>` 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<SignalsInfo>: StreamExt`
|
= note: the following trait bounds were not satisfied:
`&std::sync::Mutex<SignalsInfo>: futures_lite::Stream`
which is required by `&std::sync::Mutex<SignalsInfo>: StreamExt`
`std::sync::Mutex<SignalsInfo>: futures_lite::Stream`
which is required by `std::sync::Mutex<SignalsInfo>: 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<Result<SignalsInfo,
std::io::Error>>`
|
= help: the trait `Try` is not implemented for
`std::sync::Mutex<Result<SignalsInfo, std::io::Error>>`
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=
/<<PKGBUILDDIR>>/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-----
--- End Message ---
--- Begin Message ---
Version: 2.2.3-1
Quoting Matthias Geiger (2024-06-24 14:21:14)
> On Wed, 19 Jun 2024 20:04:26 +0200 Jonas Smedegaard <j...@debian.org> wrote:
> > > >
> > > I packaged async-signal; it's awaiting a NEW trip.
> >
> > Great!
> >
> async-signal migrated to testing; I'd appreciate it if you could test if
> re-enabling async-signal fixes this bug.
This was fixed with release 2.2.3-1.
If for some *different* reason the same package fails to build, then
please report as a separate issue (not reopening this issue).
Kind regards,
- 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
--- End Message ---
