On a new desktop install apt complains about ubuntu.sources.curtin.old

Bug #2058741 reported by Sebastien Bacher
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
curtin
Fix Released
High
Olivier Gayot

Bug Description

Installing Ubuntu Desktop Noble daily with the default options (no encryption, using the only available disk in the VM), on the installed system apt displays those warnings

> N: Ignoring file 'ubuntu.sources.curtin.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

Tags: iso-testing

Related branches

Dan Bungert (dbungert)
Changed in curtin:
importance: Undecided → High
tags: added: foundations-todo
Revision history for this message
Olivier Gayot (ogayot) wrote :

Hello Seb. Thank you for your bug report,

Indeed, during installation, curtin apt-config backs up the original ubuntu.sources file before making modifications:

https://github.com/canonical/curtin/blob/master/curtin/commands/apt_config.py#L650

I suggest we either remove it completely or use a different extension. By default on noble, the following extensions should be ignored without warning:

$ apt-config dump | grep -F Dir::Ignore-Files-Silently
Dir::Ignore-Files-Silently "";
Dir::Ignore-Files-Silently:: "~$";
Dir::Ignore-Files-Silently:: "\.disabled$";
Dir::Ignore-Files-Silently:: "\.bak$";
Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$";
Dir::Ignore-Files-Silently:: "\.ucf-[a-z]+$";
Dir::Ignore-Files-Silently:: "\.save$";
Dir::Ignore-Files-Silently:: "\.orig$";
Dir::Ignore-Files-Silently:: "\.distUpgrade$";

Changed in curtin:
status: New → Triaged
importance: High → Medium
Olivier Gayot (ogayot)
Changed in curtin:
importance: Medium → High
Olivier Gayot (ogayot)
Changed in curtin:
assignee: nobody → Olivier Gayot (ogayot)
status: Triaged → In Progress
Revision history for this message
Server Team CI bot (server-team-bot) wrote :

This bug is fixed with commit a02daee2 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=a02daee2

Changed in curtin:
status: In Progress → Fix Committed
Olivier Gayot (ogayot)
tags: removed: foundations-todo
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2058741

tags: added: iso-testing
Revision history for this message
ajgreeny (ajg-charlbury) wrote :

I have seen the same problem on my KVM/QEMU installs of Xubuntu for the past few days (can't remember when it first appeared) though the system still appears to update packages as it should.
I changes the name of that ubuntu.sources.curtin.old to ubuntu.sources and the error did not appear.

Is the problem simply a misnaming of that file or does it go deeper than that?

Revision history for this message
corrado venturini (corradoventu) wrote :

In /etc/apt/sources.list.d they are 2 files:
corrado@corrado-n8-nn-0322:~$ ls /etc/apt/sources.list.d -l
total 8
-rw-r--r-- 1 root root 386 Mar 22 15:08 ubuntu.sources
-rw-r--r-- 1 root root 2580 Mar 22 06:32 ubuntu.sources.curtin.old
corrado@corrado-n8-nn-0322:~$

file ubuntu.sources already exist, how could you rename ubuntu.sources.curtin.old to ubuntu.sources?

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

the fix which has been merged renames the file to be .orig isn't of .old

Revision history for this message
ajgreeny (ajg-charlbury) wrote :

Just as a test I have just renamed ubuntu.sources.curtin.old as ubuntu.sources.curtin.orig and no warning or error appeared when running sudo apt update.

Whether or not this is a complete fix remains to be seen but it's a start.
Can I assume that with that new name the file really is being parsed as it should be?

Revision history for this message
corrado venturini (corradoventu) wrote :

Same renaming to ubuntu.sources.curtin.save

Changed in curtin:
status: Fix Committed → Fix Released
Revision history for this message
Bozkurt (maksimuswindbroken) wrote :

Looks like a fix is released but I'm not sure if it's included in the stable version since I'm still having the same issue. 24.04 LTS Stable. Can I simply remove it?

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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