[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2023-05-05 Thread Lenin
so if anyone else wants to opt out from it, you're welcome: https://github.com/alexmyczko/autoexec.bat/blob/master/config.sys/ubuntu- remove-phased-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-09-23 Thread Julian Andres Klode
** No longer affects: hobbit-plugins (Ubuntu) ** Changed in: aptitude (Ubuntu) Status: Invalid => Triaged ** Changed in: apt (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-09-23 Thread Lenin
hobbit-plugins client/apt check reports: Fri Sep 23 08:59:06 2022 - apt NOT ok Ubuntu 22.04.1 LTS yellow Packages not installed from apt repositories (4): libnss-systemd:amd64 (249.11-0ubuntu3.4) libudev1:amd64 (249.11-0ubuntu3.4) systemd-sysv (249.11-0ubuntu3.4) systemd-timesyncd

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-08-24 Thread Lenin
Hi Julian, Looks like APT::Get::Phase-Policy true; did what I wanted. Thank you. ** Changed in: apt (Ubuntu) Status: Triaged => Invalid ** Changed in: aptitude (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch

Re: [Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-08-03 Thread Axel Beckert
Hi Julian, Julian Andres Klode wrote: > Do note that aptitude is mostly unmaintained these days. I have to object here as well: There's no development currently, but it is _not_ unmaintained. (And the current RC bug in Debian will soon be addressed. I'm just back from holidays.)

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-08-03 Thread Julian Andres Klode
To make it clear, my suggestion for a workaround for jammy would be to have _config->CndSet("APT::Get::Phase-Policy", true); somewhere in the aptitude code. It is unclear to me if aptitude will break then as phased versions get their pin limited to 1, apt certainly does if there's a mismatch as

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-08-03 Thread Julian Andres Klode
I have added an aptitude task and set the tasks accordingly to indicate that this is a feature request for aptitude. The needed API will surface at some point in APT due to some refactoring, likely in the 23.04 cycle. aptitude could then consume that API in its resolver and make choices to keep