SRU the current 0.20.4 stable update

Bug #1925795 reported by Sebastien Bacher
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libsecret (Ubuntu)
Fix Released
Low
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

* Impact

That's the current GNOME stable update, including some bugfixes and translation updates
https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares
- evince (try to open a a password protected pdf, it should store and remember the password)
- evolution
- epiphany-browser
- vinagre
- balsa
- deja-dup

* Regression potential

Nothing specific to try in those changes, just ensure the library still access the passwords as expected

Changed in libsecret (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Sebastien, or anyone else affected,

Accepted libsecret into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsecret/0.20.4-0ubuntu1 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 libsecret (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed verification-needed-focal
Revision history for this message
Brian Murray (brian-murray) wrote :

I missed that Groovy will have a lower version number than Focal. Could you also SRU this for Groovy?

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (libsecret/0.20.4-0ubuntu1)

All autopkgtests for the newly accepted libsecret (0.20.4-0ubuntu1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

pinentry/1.1.0-3build1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#libsecret

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Sebastien Bacher (seb128) wrote :

The pinenty test was successful after a retry

Revision history for this message
Sebastien Bacher (seb128) wrote :

The 0.20.4-0ubuntu1 update works as expected, accessing the keyring is working. Trying to open a protected pdf in evince the password is correctly stored and re-used after trying to open the document again.

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Revision history for this message
Chris Halse Rogers (raof) wrote :

Hey Seb! This is a candidate for release into -updates, but I don't think we can do that while it supersedes any package in Groovy.

I understand that the Desktop team has constrained resources. The SRU team intends to propose a policy change to help, but for now could you please do a Groovy upload too?

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Chris, would you need the SRU in proposed or to migrate to updates? If that's the later I don't think we want to waste verification resources on that at the moment, in which case we would rather delay copying until we stop doing SRUs for 20.10, sorry for the LTS users waiting for the update

Revision history for this message
Brian Murray (brian-murray) wrote :

Part of the argument for requiring the package being SRU'ed to be available in the release to which you'd upgrade is that we don't want to regress users when they upgrade to the next release or prevent their ability to upgrade by creating a scenario for which an upgrade cannot be calculated. Having said that I installed the libsecret binary packages from -proposed for Focal and then attempted an upgrade from Focal to Groovy, this was successfully calculated and the libsecret binary packages were kept at the same version. Subsequently, I think it is okay to release libsecret for Focal.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libsecret - 0.20.4-0ubuntu1

---------------
libsecret (0.20.4-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1925795)

 -- Sebastien Bacher <email address hidden> Fri, 23 Apr 2021 15:03:10 +0200

Changed in libsecret (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for libsecret has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.