Re: Upgrade problems from LTS -> LTS+1
- To: Ola Lundqvist <ola@inguza.com>
- Cc: Raphael Hertzog <hertzog@debian.org>, Utkarsh Gupta <utkarsh@debian.org>, Debian LTS <debian-lts@lists.debian.org>, Abhijith PA <abhijith@debian.org>, Holger Levsen <holger@layer-acht.org>
- Subject: Re: Upgrade problems from LTS -> LTS+1
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Thu, 20 May 2021 08:23:26 +0200
- Message-id: <[🔎] 20210520062326.GA24019@lorien.valinor.li>
- Mail-followup-to: Ola Lundqvist <ola@inguza.com>, Raphael Hertzog <hertzog@debian.org>, Utkarsh Gupta <utkarsh@debian.org>, Debian LTS <debian-lts@lists.debian.org>, Abhijith PA <abhijith@debian.org>, Holger Levsen <holger@layer-acht.org>
- In-reply-to: <[🔎] CABY6=0k48kOpvhw=NqUnF7_x47wuUZPN9HvJKbh7JOX-7RrkTA@mail.gmail.com>
- References: <[🔎] CABY6=0mg6mzLe92mMfUabSn6fw7peft0b9K2Ns6QcSUJqo=C7A@mail.gmail.com> <[🔎] CAPP0f94+Pxr0kR9R6LEu0HYzt6+3gB6wTnu66eLupesPC43Y8g@mail.gmail.com> <[🔎] 20210517080513.GD30043@layer-acht.org> <[🔎] CABY6=0mYjjfmJXkdU4RPtTxm488M2z1s7DsxqOzaDYmf41WLGg@mail.gmail.com> <[🔎] CAPP0f97GfizhbYWa6cLvTp7OB7sauexD-iNPhCY7JhDuWxjfHw@mail.gmail.com> <[🔎] CABY6=0=kDqe3vsSAp9xz=hCL6gzYHXifqofb9je8b3THvc9+3w@mail.gmail.com> <[🔎] CABY6=0=yGArQE4jjJMCcRDFnZRDsgrAyP+y_=PgHw8ipbVeu_Q@mail.gmail.com> <[🔎] CAPP0f970v6hza_oEFmVAJhpvhRPAOrochbhhAah8Y-oLcqFeSA@mail.gmail.com> <[🔎] YKUy2DpDa5XpFrkJ@t14-buxy.home.ouaza.com> <[🔎] CABY6=0k48kOpvhw=NqUnF7_x47wuUZPN9HvJKbh7JOX-7RrkTA@mail.gmail.com>
Hi,
On Thu, May 20, 2021 at 08:14:12AM +0200, Ola Lundqvist wrote:
> Hi
>
> I was thinking more on placing it in the security tracker bin folder for
> easy access. Or do you think we should consider it as a separate tool with
> its own repo?
Given (if) it is specific to things fixed in previous LTS (now ELTS)
to LTS, please keep it outside the security-tracker and use it instead
in a (E)LTS specific repository.
Alternatively if it's parametrised as such that by can cover the
regular supported suites by default (not from "external" ELTS -> LTS)
and report problems from (currently stretch -> buster), and e.g. by an
--lts parameter and a URI from jessie -> stretch -- then I guess we
can discuss indeed having it in the security-tracker bin. But in
general the rule would be not ELTS dependencies in the
security-tracker itself.
Regards,
Salvatore
Reply to: