Your message dated Thu, 02 Jan 2025 21:39:51 +0000
with message-id
<ceaca7743894c65b56e64dcc6070f9f6581a4137.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1077958: nmu: rust-async-broadcast_0.7.1-1
has caused the Debian Bug report #1077958,
regarding nmu: rust-async-broadcast_0.7.1-1
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.)
--
1077958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-async-broadc...@packages.debian.org,
debian-r...@lists.debian.org
Control: affects -1 + src:rust-async-broadcast
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu rust-async-broadcast_0.7.1-1 . riscv64 . unstable . -m "Rebuild to fix
previous broken build"
https://packages.debian.org/sid/riscv64/librust-async-broadcast-dev/filelist
looks really weird, and this is not seen on other architectures.
I suspect this broken binray package is the reason why the package fails on
debci and is holding up the rust-zbus transition
--- End Message ---
--- Begin Message ---
On Tue, 2024-08-06 at 07:15 +0200, Paul Gevers wrote:
> Hi,
>
> On 06-08-2024 06:39, Paul Gevers wrote:
> > On 06-08-2024 04:21, Reinhard Tartler wrote:
> > > So I think I managed to find the right combination of packages.
> > > Basically, we need all of
> > > - rust-async-channel
> > > - rust-async-process
> > > - rust-event-listener
> > > - rust-async-broadcast
> > >
> > > to migrate together.
> >
> > Because they break each other, or merely because the test fail?
>
> Wait, I think I now understand what you tried to say earlier (sorry,
> it's very exciting at $dayjob and I'm not always as sharp at home as
> I normally am). Apparently librust-async-io stopped providing
> librust-async-io-2+default-dev (and others), or something along those
> lines. I think we're running into limitations of britney2 here where
> it isn't aware of how to deal with situations where only one package
> Provides something else during the excuses phase. It's already for a
> long time on my todo list, but alas.
>
> Under the assumption that the above assessment above is correct, the
> packages will migrate together because otherwise they become
> not-installable and the second phase of britney2 protects against
> that.
And they did, not long afterwards; closing the bug.
Regards,
Adam
--- End Message ---
