| krytarik | Eickmeyer: In context of today's LP bug 1962304, it would seem grub2-themes-ubuntustudio should depend on grub2-common rather than grub-common, doesn't it? | 16:59 |
|---|---|---|
| ubottu | Launchpad bug 1962304 in ubuntustudio-look (Ubuntu) "package ubuntustudio-branding-common 20.04.1 failed to install/upgrade: installed ubuntustudio-branding-common package post-installation script subprocess returned error exit status 127" [Undecided, Invalid] https://launchpad.net/bugs/1962304 | 16:59 |
| Eickmeyer[m] | krytarik: Yes, but it seems weird that we're seeing this happen now, over two years later. | 17:00 |
| Eickmeyer | Part of me can't be bothered to SRU something this close to Jammy's release, which I guess is still 2 months out. | 17:01 |
| krytarik | Well, I think LP bug 1928019 reported earlier might be related to this too though. | 17:01 |
| ubottu | Launchpad bug 1928019 in ubuntustudio-look (Ubuntu) "package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade: installed plymouth-theme-ubuntustudio package post-removal script subprocess returned error exit status 1" [Undecided, Invalid] https://launchpad.net/bugs/1928019 | 17:01 |
| krytarik | I mean 20.04 is supposed to be supported for about another year regardless though. | 17:03 |
| Eickmeyer | Yeah, as a grace period for upgrade. | 17:03 |
| krytarik | But yeah, given the few reports about this so far, I'm not sure it's worth the effort of doing an SRU either. | 17:05 |
| Eickmeyer | I am, however, seeing the grub-common package as a dependency of the grub theme, not the old branding-common package (since removed). | 17:11 |
| Eickmeyer | And I'm trying to figure out why it's not grub2-common. I might, for Jammy, make it grub-common | grub2-common. | 17:12 |
| krytarik | grub2-common depends on grub-common itself. And the latter wouldn't help in the case the bug report is about. | 17:14 |
| Eickmeyer | It seems as though, in the case of the branding-common package, it ran update-grub on postinst, but that only works if the system already has grub installed. | 17:16 |
| Eickmeyer | In the case of this raspberry pi situation, that means it didn't have grub installed, which brought an impossible situation, which means my comment/closure still stands. Seems to be a support issue more than anything. | 17:17 |
| krytarik | I think we are just lucky that usually grub2-common is already installed by way of the bootloader itself. | 17:20 |
| Eickmeyer | Additionally, I recall 3 years ago when I made the change to the plymouth postrm (as is the case in the latter bug), that it needed to always assume grub was there. Pretty sure that was an AA that told me that, and I just followed. | 17:20 |
| Eickmeyer | Either way, I will proably fix for jammy, but I'm not 100% convinced SRU-ing this is worth the effort. | 17:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!