Ubuntu 25.04 "Modernize sources

Pre-Release Discussion
1

Testing Ubuntu 25.04 Gnome. When updating I get a message to modernize, so what the heck I tried it. It seems to work OK except with to of my sources. This is the output:

Notice: Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘https://packages.microsoft.com/repos/edge stable InRelease’ doesn’t support architecture ‘i386’
Notice: Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘https://packages.teejeetech.com/aptik/0/uaxmSG4xNy/ubuntu/jammy/amd64 stable InRelease’ doesn’t support architecture ‘i386’

Sorry for the way it displayed, could not fing code tags.

Gort

2

Ubuntu hasn’t supported 32bit systems for over 5 years (i386). Did you upgrade from 22.04 as I see you have ‘jammy’ in your 2nd package?

3

Please post the output of inxi -r

If the package is not installed you can install with this sudo apt install inxi

To add code tags, either from the ribbon

Screenshot
Screenshot906×270 20.4 KB

Or use backticks from the keyboard some output here

On my keyboard the backtick is found under the esc button top left. ```

1 Like
4 
inxi -r
Repos:
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.sources
    1: deb https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/teejeetech-aptik.sources
    1: deb https://packages.teejeetech.com/aptik/0/uaxmSG4xNy/ubuntu/jammy/amd64/ stable main
  Active apt repos in: /etc/apt/sources.list.d/ubuntu.sources
    1: deb http://us.archive.ubuntu.com/ubuntu/ plucky plucky-updates plucky-backports main restricted universe multiverse
    2: deb http://security.ubuntu.com/ubuntu/ plucky-security main restricted universe multiverse
5

I did a fresh install. I guess teejeetech has not update to Plucky yet, but it works. Would installing i386 packages make a difference?

Gort

6

The issue isn’t necessarily that you have i386 packages installed but those two third-party repos you have (which are, of course, unsupported by Ubuntu) provide (or did provide maybe) them.

7

Just an aside, it is usually prudent to check your sources lists before a major upgrade and disable 3rd party repos to avoid conflicts and issues similar to what you experienced.

Glad you resolved it in the end.

1 Like
8

Point taken, I should have disabled 3rd party repos…must be losing my marbles :joy:

Gort

9

You should definitely not need to do this, update-manager (or do-release-upgrade if you used the cmdline version of it) has a ton of code to make sure they automatically get disabled, if this did not work opening a bug and attaching all logs (best done via ubuntu-bug update-manager, that will collect relevant logs automatically) should be the first thing you do, so the issue can be researched and fixed for others …

1 Like
10

@ogra I guess my suggestion was based on what we used to do in the old days.

Now I know better.

Is this disabling of repos documented, can you please point me to it?

11

There should be plenty of docs mentioning it (and indeed there is the source code to look at), here is one:

https://documentation.ubuntu.com/server/how-to/software/upgrade-your-release/index.html

Third-party software repositories and personal 
package archives (PPAs) are disabled during the 
upgrade. However, any software installed from these 
repositories is not removed or downgraded. Software
 installed from these repositories is the most 
common cause of upgrade issues.
1 Like
12

Thanks, appreciated as usual :slight_smile:

After a successful upgrade, I assume the user has to manually re-enable the disabled 3rd party sources and PPAs?

1 Like
13

Actually I went to software and remove Edge and Aptik, until Ubuntu 25.04 goes stable. Then I will make a bug report. In the meantime Edge and Aptik won’t update till then.

Gort

14

Opening a bug after release will not fix the release, you should do it while there is still development being possible…

15

Hey,

this is likely a result of APT dropping various options when modernizing sources, see

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094709

for more details.

Going to need some more work to actually get access to the options to parse them and translate them.

That said, this is really just a bad workaround 3rd party sources use, where they specify [arch=amd64] in their sources.list rather than include i386 in the Architectures: field in their Release file.

1 Like
16

Everybody’s responses are truly amazing. Your support is what makes Ubuntu great. I will follow up with all your replies. Thank you so much for your support.

Gort

1 Like
17

Is there a way to disabled this “Modernize Sources” message?

Gort

18

Yes. Only use deb822 compliant sources.

19

How can I determine if the source is deb822 compliant? I am not familiar with that standard.

Gort

20

Ubuntu switched to deb822 only somewhere between 24.04 and 25.04, since this move is a one time switch (we won’t be going back to old sources.list files) the message will not occur anymore once the transition of your install is complete (so that it will not break once the old style sources.list handling gets removed completely one day)…

Just make sure you have completely transitioned and the message will not return