On Wed, Nov 10, 2021 at 11:48:15PM +0000, Colin Watson wrote: > On Wed, Nov 10, 2021 at 10:39:04AM -0800, Brian Murray wrote: > > On Wed, Nov 10, 2021 at 08:11:19AM +0000, Colin Watson wrote: > > > On Tue, Nov 09, 2021 at 02:22:34PM -0800, Brian Murray wrote: > > > > I was looking at some Foundations bug reports[1] today and discovered > > > > that > > > > there is no command-not-found information for Jammy as of yet. Looking > > > > at the archive there is no cnf folder for any jammy components. Adding > > > > the new release to the list of releases for the cnf-extractor was > > > > done[2] (by me) so I'm at a loss for what is missing. Does anybody else > > > > have an idea? > > > > > > Is cnf-extractor.internal still the current prod-cnf-extractor machine? > > > It's not publishing any data for jammy either: > > > > I believe I've found the source of the problem and the system is > > currently working on producing updated data for impish and after that > > jammy will get done. > > Looks like it's in the archive now. Thanks for tracking that down. > Does anything need to be added to NewReleaseCycleProcess for this, or > was it a one-off bug?
It was a one-off bug because the prod-cnf-extractor machine was not up to date, but I've now enabled unattended-upgrades so this specific type of issue should not happen again. Having said that is there a mechanism we could use to ensure the Commands files on the archive were generated recently? -- Brian Murray -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel