Re: Rolling release prototype
On Sun, Jun 05, 2011 at 01:59:57PM +0200, Josselin Mouette wrote:
> Le dimanche 05 juin 2011 à 10:31 +0200, Raphael Hertzog a écrit :
> > Where are the sources ? :)
>
> I’m somehow ashamed to share such crappy code, but it’s on
> ries:/home/joss/rolling/make_rolling.py
>
> > > The APT lines you need are the following:
> > > deb http://your.favorite.mirror/ testing main contrib non-free
> > > deb http://rolling.debian.net/ rolling main contrib non-free
> > > You will also need the temporary archive key[2].
> >
> > I would like to see rolling a full suite and not an overlay of testing.
> >
> > For the experiment it's fine (in particular to not overload your server),
> > but we should be able to switch to a full suite when integrated on
> > ftp-master.debian.org.
>
> Yes, once we use the same dak instance as testing and unstable, it
> should be trivial. This is why I haven’t bothered with the cleanness of
> the archive generation code.
>
> > http://udd.debian.org/bugs.cgi?release=wheezy_not_sid&merged=ign&done=only&fnewerval=7&rc=1&sortby=popcon&sorto=desc
> >
> > Some interesting candidates could be:
> > - fuse: security issues fixed in unstable
> > - digikam: fix a crasher (might be blocked by dependencies)
> > - libvirt: security issues fixed in unstable
>
> I’m not sure the digikam bug really affects testing. And even if it did,
> this would mandate a t-p-u upload instead.
Or even a s-p-u upload. According to the date and version it also
affects Squeeze... Looks like the problem is deeper, and fixing it
through a rolling distribution is probably the wrong answer.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: