This bug was fixed in the package systemd - 256.5-2ubuntu3.1
---
systemd (256.5-2ubuntu3.1) oracular; urgency=medium
* Make sure systemd-cryptsetup is pulled in by systemd on install/upgrade
(LP: #2084251)
- d/control: make systemd-cryptsetup Priority: important
- d/cont
Priorities are handled entirely via the archive overrides. It doesn't
matter if this is changed in the SRU or not, we should accept it either
way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
This bug was fixed in the package systemd - 256.5-2ubuntu4
---
systemd (256.5-2ubuntu4) plucky; urgency=medium
* Make sure systemd-cryptsetup is pulled in by systemd on install/upgrade
(LP: #2084251)
- d/control: make systemd-cryptsetup Priority: important
- d/control: m
> ### Edit: The deboostrap test is not applicable, because I wrongly assumed we
> would adjust the priorities
> in SRU, but after consulting an AA, it is not worth doing for oracular.
I don't understand this, because the diff shows that the priority was
adjusted in the proposed package:
--- a/d
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/oracular/update_excuses.html#systemd also shows a linux-
lowlatency test on arm64 running, I suppose for days. I didn't locate it
in the autopkgtest /running page, nor in the history of completed tests,
so I triggered a new run.
--
You re
I think it's best to remove the priority change then, because:
a) that seems to have been the agreement with an AA before;
b) making it priority important could have other implications we haven't
thought through
But then DEP8 hell will happen, it will be days before this can be
released...
Perh
The linux-lowlatency test has passed now
(https://autopkgtest.ubuntu.com/packages/l/linux-
lowlatency/oracular/arm64)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
LUKS not detected o
> I don't understand this, because the diff shows that the priority was
adjusted in the proposed package:
Yes, sorry for the confusion.
I originally wrote both the SRU patch, and the test plan, under the
impression that we *would* adjust the priority for oracular. Once the
SRU was accepted into -
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2084251
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Oh, changing `Pin-Priority` to 500 did it:
| [hloeung@dharkan etc]$ sudo apt install systemd/oracular-proposed
systemd-sysv/oracular-proposed
| Selected version '256.5-2ubuntu3.1' (Ubuntu:24.10/oracular-proposed [amd64])
for 'systemd'
| Selected version '256.5-2ubuntu3.1' (Ubuntu:24.10/oracular-
I've tried even with `-APT::Install-Recommends "true";`. My pinning is
left over from prior SRU testing:
| [hloeung@dharkan etc]$ cat apt/preferences.d/proposed-updates
| # Configure apt to allow selective installs of packages from proposed
| Package: *
| Pin: release a=oracular-proposed
| Pin-Pri
I have confirmed the fix using systemd/systemd-cryptsetup
256.5-2ubuntu3.1 from oracular-proposed. I used a LXD container to test
an upgrade from noble to oracular:
nr@six:~$ lxc launch ubuntu:noble noble
Launching noble
^R
nr@six:~$ lxc exec noble bash
root@noble:~# cat > /etc/apt/sources.list.d/
Or, maybe because you don't have the apt pinning configured for
oracular-proposed, apt silently ignores the Recommends.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
LUKS not detected
Haw, do you have a configuration in place to prevent Recommends: being
installed by default?
This works fine for me:
root@oracular:~# apt policy systemd systemd-cryptsetup
systemd:
Installed: 256.5-2ubuntu3
Candidate: 256.5-2ubuntu3
Version table:
*** 256.5-2ubuntu3 500
500 http://
This doesn't seem to work for me?
Removal of `systemd-cryptsetup` first:
| [hloeung@dharkan apt]$ sudo apt-get purge systemd-cryptsetup
| [sudo] password for hloeung:
| Sorry, try again.
| [sudo] password for hloeung:
| Reading package lists... Done
| Building dependency tree... Done
| Reading st
Hello Haw, or anyone else affected,
Accepted systemd into oracular-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/256.5-2ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
I've marked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084802
as duplicate of this issue because it is solved the same way and I also
edited the title here to make it more generic (don't hesitate to change
it further).
The issue in that other bug report has a different setup however.
Qu
17 matches
Mail list logo
