This bug was fixed in the package glib2.0 - 2.80.1-0ubuntu2
---
glib2.0 (2.80.1-0ubuntu2) oracular; urgency=medium
* Fix doc build
glib2.0 (2.80.1-0ubuntu1) oracular; urgency=medium
* New upstream release
* Drop patches applied in new release
glib2.0 (2.80.0-10ubuntu1) oracul
You have a typo in the description:
> the massive Y2028 time_t transition
I think you mean Y20*3*8.
Not a big deal, but just for clarity you should probably fix that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This bug was fixed in the package glib2.0 - 2.80.0-6ubuntu3
---
glib2.0 (2.80.0-6ubuntu3) noble; urgency=medium
[ Simon McVittie ]
* Revert addition of libglib2.0-0 transitional package. (LP: #2063221)
Because it didn't have a Pre-Depends on the replacement, it resulted
in
I changed it back for you. There is more documentation about what those
bug statuses mean for Stable Release Updates at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
** Changed in: glib2.0 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification becaus
Whoops, accidental status change that I can't change back. Was just
intending to find out more about the fix released status, didn't know it
would change it.
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
I'm marking the SRU verified based now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
https://bugs
I've tested 2.80.0-6ubuntu3 on a noble system, the upgrade went as
expected and the desktop is still working properly.
I still had libglib2.0-0 installed and it got removed when installing
the new version
rmadison also confirmed the libglib2.0-0 binary isn't published in
noble-proposed
** Tags r
the autopkgtests issues listed in the previous comments were transients
and got resolved on retry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notificatio
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://w
The updates look good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
https://bugs.launchp
** 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.
+ Technical
** 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
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 'functiona
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 expe
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
https://bugs.launch
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
https://bugs.launchpa
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications abo
19 matches
Mail list logo