[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
Hello Jeremy, or anyone else affected, Accepted glib2.0 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.80.0-6ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Noble) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Fix Committed Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by removing the transitional package and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 We have landed the removal in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. The removal was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. (Although that particular detail was fixed by the removal that already happened.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
The updates look good, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Confirmed Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by removing the transitional package and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 We have landed the removal in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. The removal was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. (Although that particular detail was fixed by the removal that already happened.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Description changed: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. + Technically, Steve Langasek already removed libglib2.0-0 from noble + release just before release. This upload is necessary to ensure that we + don't accidentally bring it back. + Test Case - - Is libglib2.0-0 built? + 1. Is libglib2.0-0 built? + + 2. Run rmadison libglib2.0-0 + There should be 0 results for noble, noble-proposed, or noble-updates + + 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu + 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is + currently set to disallow upgrades to 24.04 LTS. If this is still the + case when it is time to verify this SRU, you can manually substitute + jammy → noble in /etc/apt/sources.list for purposes of testing this + upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. - Hmm, we can't actually drop libglib2.0-0 after release, can we? - Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 ** Description changed: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- - We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. - - This SRU was recommended by Julian Klode, the apt maintainer for Debian - and Ubuntu. - - The original transitional package was added by Simon McVittie in hopes - that it would help apt be able to calculate the upgrade easier. At least - in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was - the opposite. + Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by - this update and some other workarounds in other packages, like in the - transitional thunderbird package. + removing the transitional package and some other workarounds in other + packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 + + We have landed the removal in Debian Unstable and it successfully + migrated to Debian Testing on April 27 as one of the first t64 packages + to migrate there. + + The removal was recommended by Julian Klode, the apt maintainer for + Debian and Ubuntu. + + The original transitional package was added by Simon McVittie in hopes + that it would help apt be able to calculate the upgrade
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Description changed: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? + Where Problems Could Occur + -- + We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. + + This SRU was recommended by Julian Klode, the apt maintainer for Debian + and Ubuntu. + + The original transitional package was added by Simon McVittie in hopes + that it would help apt be able to calculate the upgrade easier. At least + in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was + the opposite. + + Hmm, we can't actually drop libglib2.0-0 after release, can we? + Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Incomplete Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. Hmm, we can't actually drop libglib2.0-0 after release, can we? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
Hi Jeremy, This looks mostly good, AFAICT. Could you please complete the SRU bug template by adding the section 'Where problems could occur' / 'Regression potential'? [1] And although the 'Test Case' is feasible to understand, based on the 'Impact' section, it would be nice to have a 'functional' test, if at all possible/reasonably doable. For example, I tried to reproduce the thunderbird deb2snap issue, but it didn't. I realize there might be a more complex package setup/install list to trigger it, but maybe there's something simpler that you are aware of. (Or if it's too complex / not worth it, just clarifying that and mentioning what shouldn't change / how to check for no regressions, would be OK too; I tried to convey that in comment #1). Thanks! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: glib2.0 (Ubuntu Noble) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Incomplete Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. Hmm, we can't actually drop libglib2.0-0 after release, can we? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as expected;
libglib2.0-0 is removed in favor of libglib2.0-0t64 in all cases.
Test 1)
Just Noble:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu1 Ubuntu:24.04/noble
[amd64]) []
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu1
Ubuntu:24.04/noble [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu1 Ubuntu:24.04/noble [all])
Noble and local build/repo:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu3
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu3 localhost [amd64])
[]
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu3 localhost [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu3 localhost [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu3 localhost [all])
Test 2)
Just Noble:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu1
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu1
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu1
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
Noble and local build/repo:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu3
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu3
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu3
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Also affects: glib2.0 (Ubuntu Noble) Importance: High Status: In Progress ** Changed in: glib2.0 (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Changed in: glib2.0 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
