Le 10/09/2024 à 17:30, Colin Watson a écrit :
Peter fixed it in
https://tracker.debian.org/news/1562797/accepted-rust-merge-010-2-source-into-unstable/
(thanks!), so the situation is definitely less bad than it was for
Debian; though the apparent lack of upstream maintenance might still be
a pro
On Tue, Sep 10, 2024 at 05:21:30PM +0200, Arnaud Ferraris wrote:
> Le 04/09/2024 à 21:36, Colin Watson a écrit :
> > On Wed, Sep 04, 2024 at 08:04:21PM +0100, Colin Watson wrote:
> > > https://ci.debian.net/packages/r/rust-merge/testing/amd64/ appears to
> > > have always failed; it looks as though
Hi Colin,
Le 04/09/2024 à 21:36, Colin Watson a écrit :
On Wed, Sep 04, 2024 at 08:04:21PM +0100, Colin Watson wrote:
https://ci.debian.net/packages/r/rust-merge/testing/amd64/ appears to
have always failed; it looks as though rust-merge:@ and
librust-merge-dev:default succeed but everything el
On Wed, Sep 04, 2024 at 08:04:21PM +0100, Colin Watson wrote:
> https://ci.debian.net/packages/r/rust-merge/testing/amd64/ appears to
> have always failed; it looks as though rust-merge:@ and
> librust-merge-dev:default succeed but everything else fails.
>
> librust-merge-dev:derive fails with:
>
Source: rust-merge
Version: 0.1.0-1
Severity: serious
Justification: https://release.debian.org/testing/rc_policy.txt 6(a)
https://ci.debian.net/packages/r/rust-merge/testing/amd64/ appears to
have always failed; it looks as though rust-merge:@ and
librust-merge-dev:default succeed but everything
5 matches
Mail list logo
