On 25/05/2023 14.42, Andreas Tille wrote:
Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
Installation of kleborate from sid and testing shown no issues.
Installation of kleborate from bullseye on bullseye is okay too.
Good. Maybe we should reflect in BTS that this bug is
I had difficulties reproducing the issue with piuparts, but I
manage to reproduce the problem as I suspected, with the
following upgrade path, most likely because of the inconsistent
makeblastdb version between the one used for building kleborate
in bookworm and the one "refreshed" during postinst
Hi Andreas Tille,
Andreas Tille, on 2023-05-25:
> Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
> >
> > Installation of kleborate from sid and testing shown no issues.
> > Installation of kleborate from bullseye on bullseye is okay too.
>
> Good. Maybe we should reflect in
Hi Étienne,
Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
>
> Installation of kleborate from sid and testing shown no issues.
> Installation of kleborate from bullseye on bullseye is okay too.
Good. Maybe we should reflect in BTS that this bug is not relevant for
bookworm?
Hi all,
Andreas Beckmann, on 2023-05-25:
> during a test with piuparts I noticed debsums reporting modified files
> after a 2-stage upgrade from bullseye to bookworm:
> apt-get upgrade
> apt-get dist-upgrade
> (It does not happen if only a single-stage apt-get dist-upgrade is used)
>
>
5 matches
Mail list logo
