> Most of the times when I take a detailed look on why it doesn't migrate,
> it leads to one of the few packages that currently are in NEW. I don't
> have the time right now to include it in this mail, but if desired I
> will assemble the list of required packages that are currently in NEW as
>
On 2/3/20 2:57 PM, Carsten Schoenert wrote:
> Hi,
>
> Am 03.02.20 um 13:08 schrieb Sylvestre Ledru:
> ...
>> I have been told that the transition of one of the build-dep is blocked by
>> packages blocked in NEW...
>> Not sure which one.
>
> this is more or less what I mean, we should get
Hi,
Am 03.02.20 um 13:08 schrieb Sylvestre Ledru:
...
> I have been told that the transition of one of the build-dep is blocked by
> packages blocked in NEW...
> Not sure which one.
this is more or less what I mean, we should get clearance about the root
of problems.
> We already started a
Le 03/02/2020 à 10:47, Carsten Schoenert a écrit :
Hi Sylvestre,
Am 04.01.20 um 17:19 schrieb Sylvestre Ledru:
Honestly, (shame on me) I didn't pay much attention to the cbindgen
migration
or other migrations of rust binaries.
Mostly because when I look at the transition dashboard, I don't
Hi Sylvestre,
Am 04.01.20 um 17:19 schrieb Sylvestre Ledru:
> Honestly, (shame on me) I didn't pay much attention to the cbindgen
> migration
> or other migrations of rust binaries.
>
> Mostly because when I look at the transition dashboard, I don't
> understand why they are blocked. For
Hello,
Le 04/01/2020 à 17:02, Paul Gevers a écrit :
Dear rust maintainers,
I should have probably contacted you earlier, but better now than
latter. I think it is time to align between the rust maintainers and the
release team how we (ideally you without needing our assistance) can
manage the
6 matches
Mail list logo
