Re: Upgrade problems from LTS -> LTS+1

[Ola Lundqvist <ola@inguza.com>]

Hi Salvatore

It is parameterized to check any release update. So it can be used to check any previous version to any later version.

It has the parameters --old, --old-sec, --new and --new-sec to point to any relevant packages files.

It can be improved to add other things like proposed updates as well with few modifications.

Also it can be improved by making --old-sec and --new-sec optional, right now they are mandatory.

So I think it can be used by the regular security team too.

Cheers

// Ola

On Thu, 20 May 2021 at 08:23, Salvatore Bonaccorso <carnil@debian.org> wrote:

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

--

 --- Inguza Technology AB --- MSc in Information Technology ----

|  ola@inguza.com                    opal@debian.org            |

|  http://inguza.com/                Mobile: +46 (0)70-332 1551 |

 ---------------------------------------------------------------