[SRU] command-not-found metadata support

Bug #1906541 reported by Valters Jansons
This bug report is a duplicate of:  Bug #1821251: please add cnf support to debmirror. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debmirror (Ubuntu)
Confirmed
Undecided
Unassigned
Focal
In Progress
Undecided
Brian Murray
Groovy
In Progress
Undecided
Brian Murray

Bug Description

[Impact]

 * Starting with Ubuntu Focal (20.04), the APT client expects APT sources to provide command-not-found (cnf) metadata files.

 * This package provides package mirrors, however does not support mirroring this cnf metadata up until upstream version 1:2.32, which is later than the version in Focal (20.04) and Groovy (20.10).

 * This upload cherry-picks upstream commits 292e9e9c, 39055366 and 9606535d, in order to add the cnf metadata support.

[Test Case]

 * Create a mirror of e.g. `bionic main` and `focal main`: debmirror -d bionic,focal -s main --passive --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror

 * Serve the root directory of /opt/debmirror as webroot.

 * Point APT `sources.list` at this webroot: deb http://mirror.example.com/ubuntu/ focal main

 * Attempt to run `apt update` on Focal (20.04) client to see that it fails to obtain the cnf metadata.

 * Optionally run `apt update` on Bionic (18.04) client to see that it works fine without the cnf metadata.

[Where problems could occur]

 * New cnf files are expected to be created and maintained by the debmirror package. The regression risk for incorrectly downloading these files does not serve more harm than not downloading the files whatsoever (current state of 20.04 release), as the APT client does not use the mirror in either case.

 * The change as uploaded was released in upstream as part of 1:2.32, tagged 23 Mar 2019, and is part of Debian stable. This serves as evidence of it having had testing carried out over time.

[Other Info]

Revision history for this message
Valters Jansons (sigv) wrote :
Changed in debmirror (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Valters Jansons (sigv) wrote :
Revision history for this message
Valters Jansons (sigv) wrote :

This SRU further applies to Groovy (20.10) in addition to Focal (20.04).

Hirsute (21.04) already has been pushed an upstream merge and is not a concern.

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

Thanks for working on this, the debdiff looks good to me but we'll need two debdiffs one for focal and one for groovy as they are both released. Additionally, the packages will have need to have a different number scheme which you can find guidance for here:

https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging

I'll do that when sponsoring the package.

Changed in debmirror (Ubuntu Focal):
assignee: nobody → Brian Murray (brian-murray)
Changed in debmirror (Ubuntu Groovy):
assignee: nobody → Brian Murray (brian-murray)
Changed in debmirror (Ubuntu Focal):
status: New → In Progress
Changed in debmirror (Ubuntu Groovy):
status: New → In Progress
summary: - [SRU] [focal] command-not-found metadata support
+ [SRU] command-not-found metadata support
Revision history for this message
Valters Jansons (sigv) wrote :

Thank you for the information, as well as the SecurityTeam/UpdatePreparation link. I will for sure keep that in mind for potential future SRU requests.

And thank you for the handling the correction during sponsoring.

Let me know if there is anything else I can provide to assist in the process!

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.