This bug was fixed in the package snapd - 2.65.3+20.04
---
snapd (2.65.3+20.04) focal; urgency=medium
* New upstream release, LP: #2077473
- Fix missing aux info from store on snap setup
snapd (2.65.2) xenial; urgency=medium
* New upstream release, LP: #2077473
- Bump sq
This bug was fixed in the package snapd - 2.65.3+22.04
---
snapd (2.65.3+22.04) jammy; urgency=medium
* New upstream release, LP: #2077473
- Fix missing aux info from store on snap setup
snapd (2.65.2) xenial; urgency=medium
* New upstream release, LP: #2077473
- Bump sq
This bug was fixed in the package snapd - 2.65.3+24.04
---
snapd (2.65.3+24.04) noble; urgency=medium
* New upstream release, LP: #2077473
- Fix missing aux info from store on snap setup
snapd (2.65.2) xenial; urgency=medium
* New upstream release, LP: #2077473
- Bump sq
Andreas has a fair point, we probably need to re-investigate the
SnapdUpdates wiki. I never required the upgrade test from one series to
another in the last few snapd SRUs at least - I think we need to sit
down and reiterate if it still makes sense to perform this check.
In the meantime I'll check
> About "The upgrade test from previous distribution to the current one.", this
> was not tested since at
> least 6 years and I think has to be redefined because it is not included in
> the SRU validation process we
> have in snapd project.
Sounds like that exception needs updating then, or it
Hi Andreas,
About question 1, I re-executed the failing tests to have a green
execution. The only error is related to a nvidia package dependency not
available in the test (not a regression).
About question 2, Those tests failed because a known issue in the
testing infrastructure and those errors
This contains the GH action results for 2.65.3. It's red:
https://github.com/canonical/snapd/actions/runs/10832763415
Looks like several tests are failing there, are these the same that you
mentioned in
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2077473/comments/17
?
And why is this ok
Was this question from comment #5 answered somewhere?
> For the SRUs: I see that the usr/bin/ubuntu-core-launcher wrapper has been
> removed. Are we certain no
> snaps use this? We should not regress users of stable series if they use some
> snaps that depend on this
> wrapper.
--
You receiv
snapd 2.65.3 validated in focal, jammy and noble
Logs:
https://warthogs.atlassian.net/jira/core/projects/ST/board?selectedIssue=ST-2056
Some tests failed, after review I see all of them are caused by the
change that forces snapd snap to be installed which breaks some tests
when using snapd from t
** Tags removed: block-proposed block-proposed-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077473
Title:
[SRU] 2.65.3
To manage notifications about this bug go to:
https://bugs.launchpa
Validation done.
Manual tests executed. All good in Oracular
Automated tests executed. See log https://paste.ubuntu.com/p/VPtHFmymVN/. Just
1 error related to a test issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Tags added: block-proposed block-proposed-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077473
Title:
[SRU] 2.65.3
To manage notifications about this bug go to:
https://bugs.launchpad.
Upload requests for Snapd 2.65.3 to Oracular proposed
-
Please note snapd 2.65.3 was created to address a small bug (can removed
by accident). Risk of this change is considered low (it was previously
there).
https://launchpad.net/~snappy-
dev/+a
13 matches
Mail list logo
