[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#935540: debian-installer: Errors on sources.list security repositories



[ Please don't drop submitters; quoting in full accordingly. ]

Philip Hands <phil@hands.com> (2019-08-24):
> Cyril Brulebois <kibi@debian.org> writes:
> 
> > Control: tag -1 - d-i
> >
> > Hi Gustavo,
> >
> > Gustavo Romero Vazquez <gustavorv86@gmail.com> (2019-08-23):
> >> See the Wiki Debian (https://wiki.debian.org/Status/Testing), the
> >> security repositories for bullseye are the next (and they working):
> >>
> >> deb http://security.debian.org testing-security main contrib non-free
> >> deb-src http://security.debian.org testing-security main contrib non-free
> >>
> >> Regards and good luck!!
> >
> > You're absolutely right. I had stashed a branch a while ago, but it was
> > suggested to handle things slightly differently:
> >
> >    “do it other way around and hardcode the old releases rather than
> >     hardcode the new one?”
> >
> > I've just rebased it on top of master, and it'd be great if someone
> > could rework it to take the above comment in consideration:
> >
> >   https://salsa.debian.org/installer-team/apt-setup/tree/pu/security-naming-scheme
> 
> Hopefully something like this what you were wanting done:
> 
>   https://salsa.debian.org/installer-team/apt-setup/commit/78078caff231de7bb5a161fa19210b4ac6eb2cb5

Yes, that looks sane enough.

I meant to check how this could affect Ubuntu. But from what I can see
in apt-setup/0.141ubuntu2, there are a bunch of changes already anyway,
so except for a possible merge conflict, that shouldn't be much of an
issue.

Feel free to release that to master/the archive if you like.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


Reply to: