Re: Bad release in install documentation
-----BEGIN PGP SIGNED MESSAGE-----
El 08/03/16 a las 12:18, Rhonda D'Vine escribió:
> * Laura Arjona Reina <email@example.com> [2016-03-07 20:25:12
>> El 23/02/16 a las 20:27, Holger Wansing escribió:
>>> Holger Wansing <firstname.lastname@example.org> wrote:
>>>> For the time being:
>>>> Looking at
it seems, we have the same situation again now:
>>>> The latest upload of installation-guide was for Stretch
>>>> (Changelog does not mention that explicitly, but there are
>>>> several changings effecting Stretch), so that script has to
>>>> be adapted around that:
>>>> all occurences of 'jessie' have to be changed into 'stretch'
>>>> and all 'wheezy' be changed into 'jessie'.
>>>> Am I correct? If yes, could someone commit that, please !!!
>>> I have tried to apply this, but I'm lacking proper
>> I've committed the suggested change. I suppose now the install
>> guide for stretch will appear in its place, but I'm not sure if
>> this will automatically retrieve the install guide for
>> jessie/stable in its place too...
>> I'll have a look at the log and the install guides in the website
>> after the next lessoften build.
> From what I read in the VCS link above I guess it would need
> manually fetching the thing and run it manually for jessie again.
Thanks Rhonda for the hint.
I've tried to (manually) run the build of the installation manual for
jessie, and I think it went ok.
This is what I did, based on the lessoften script :
ls -t1 /srv/www.debian.org/cron/ftpfiles/pool/installation-guide_*.dsc
| head -1
sudo -u debwww dpkg-source -sn -x
cd installation-guide-20150423+deb8u2/build && sudo -u debwww
destination=/srv/www.debian.org/installmanual/jessie/ ./buildweb.sh >
sudo -u debwww cp -a /srv/www.debian.org/installmanual/jessie/*
Let's see what happens in the next lessoften build. I think stretch
manual is not built yet, but maybe it's build after this is fixed. If
tomorrow after lessoften I see the jessie manual fixed, and the
stretch manual not appearing, I would try to build it manually too.
> In the long run maybe the package version should be compared to
> the release information through something like rmadison or similar
> (though, rmadison gives stable and not jessie, so at least some
> mapping still would be needed somewhere).
I cannot help in this part, I'm afraid.
Laura Arjona Reina
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----