On Sat, 19 Dec 2015, Ansgar Burchardt wrote:
> The changes to the subdirectories below pool/ might also affect people
> maintaining (partial) private mirrors of the security archive. They
> would need to update what they mirror for the next release.
We should also make the canonical root of the
On 14160 March 1977, Thijs Kinkhorst wrote:
> Seems like a good plan. I'm assuming that people using the old style
> configuration on the new release would get an error message (and not a
> silent lack of updates); or even better: that they are automatically
> redirected to the new locations.
Dep
On Sat, December 19, 2015 15:08, Ansgar Burchardt wrote:
> I would like to propose two changes for the security archive:
>
> * Rename */updates to *-security, starting with the next stable release.
> This gets rid of the confusion of */updates vs. *-updates.
>
> * Rename the components updates/{m
Hi Ansgar
On Sat, Dec 19, 2015 at 03:08:09PM +0100, Ansgar Burchardt wrote:
> * Rename */updates to *-security, starting with the next stable release.
> This gets rid of the confusion of */updates vs. *-updates.
Please do.
> * Rename the components updates/{main,contrib,non-free} to just
> {
Hi,
[ Please send followups to -devel@ ]
I would like to propose two changes for the security archive:
* Rename */updates to *-security, starting with the next stable release.
This gets rid of the confusion of */updates vs. *-updates.
* Rename the components updates/{main,contrib,non-free} to
5 matches
Mail list logo