For example, now the gcc version in the bookworm is 11.2.0-2, now the
maintainer of the package upload a new version. I suppose it is 11.2.0-3.
Normally, it will be pushed into the bookworm after 5 days. Now we assume a
package relied on the package updated after one day. Normally it will be
Hi Bob, hi Jérôme,
On Fri, 05 Nov 2021, Jérôme Pouiller wrote:
> Is there a way to avoid this problem happen in the future?
Yes of course:
* take a VM
* for each package in the set of Plasma, that is about 150 or so, do
- upgrade the package and all necessary dependencies
- reboot the vm
-
Probably the best way is to do the rolling release. Another solution is
to make each package synced downstream at the same time, but it's too hard
to achieve.
Jérôme Pouiller 于2021年11月5日周五 下午6:11写道：
> On Friday 5 November 2021 03:02:13 CET Norbert Preining wrote:
> > > After 2 weeks, the
On Friday 5 November 2021 03:02:13 CET Norbert Preining wrote:
> > After 2 weeks, the bug has finally been fixed. But I wonder why the bug
> > wasn't tested out in the unstable branch and was pushed into the testing
>
> Because on unstable everything worked. The bug happens only due to
>
> After 2 weeks, the bug has finally been fixed. But I wonder why the bug
> wasn't tested out in the unstable branch and was pushed into the testing
Because on unstable everything worked. The bug happens only due to
different transition times from unstable to testing. This cannot be
tested in
After 2 weeks, the bug has finally been fixed. But I wonder why the bug
wasn't tested out in the unstable branch and was pushed into the testing
branch.
6 matches
Mail list logo
