Le ven. 29 mars 2019 à 10:11, Matus UHLAR - fantomas <uh...@fantomas.sk> a écrit : > > >>On 27.03.19 11:20, Bernie Elbourn wrote: > >>>If it is possible to wiz up a blank jessie-updates this will save me > >>>visiting a bunch of systems throwing apt errors in next few days. > > >On 2019-03-27 11:50, Matus UHLAR - fantomas wrote: > >>I wonder if it wasn't blank already. All of its contents was > >>supposed to be > >>moved to jessie main archive with last point release and no content > >>should > >>be there after that. > > On 27.03.19 13:52, Adam D. Barratt wrote: > >Packages aren't moved from -updates to (old)stable, they're moved from > >p-u. Packages only get removed from -updates following manual action > >from a Release Team member. > > so, as I understand it, packages like clamav, spamassassin and others that > are in -updates may not get to main archive with a point release? > > Is there anything other needed to get them in? > > iirc, the -updates (formerly called volatile) was created to contain > packages that really need updates during distribution lifecycle, just like > antiviruses, spam filters and alike. > > They should not be lost. >
The way I understand it, but I asked for clarification and confirmation in my previous message [1], is that all « updates » goes into -proposed-updates/, but the one who need to be quickly applied into the distribution (but aren't security updates) are duplicated from -proposed-updates/ into -updates/. Theses are the updates who can't wait and must be applied between the point releases. Then, when point releases occurs, all packages in -proposed-updates/ moves into the stable repository of the distribution. They are automatically removed from -proposed-updates/. This isn't true for the -updates/ repository as it requires manual pruning. Nonetheless, all packages in -updates/ went into the stable repository (from the -proposed-updates they originated from) when the point-release occurred. So nothing is lost. But is that right ? Pierre. [1] https://lists.debian.org/debian-lts/2019/03/msg00142.html