Question

2

rated 0 times [ 2] [ 0] / answers: 1 / hits: 4464 / 2 Years ago, mon, august 1, 2022, 1:32:41

During the Saucy update it said that it would disable some packages, and it did.

In Software & Updates under Other Software a lot of my repositories are either "disabled on upgrade to saucy" or end in raring.
IE:

Http://ppa.launchpad.net/webupd8team/java/ubuntu

Distribution: raring

Componets: main

Comment: disabled on upgrade to saucy

Do I just change the distribution to saucy?
Do I have to do that to all of them?

Only authorized users can answer the question. Please sign in first, or register a free account.

Total Points: 63

Total Questions: 107

Total Answers: 104

Location: Morocco

Member since Fri, May 22, 2020

4 Years ago

brellked questions

Wed, Jul 20, 22, 23:30, 2 Years ago

Sun, Apr 10, 22, 19:26, 2 Years ago

Mon, Sep 6, 21, 05:31, 3 Years ago

Sat, Aug 20, 22, 02:03, 2 Years ago

Sun, Aug 21, 22, 07:11, 2 Years ago

answered 2 Years ago scusaper · Accepted Answer

I wrote a bash script that removes the leading hash character from all files in sources.list.d that were disabled during the upgrade. I also posted the same code in What's the best way to re-enable ppa's/repos after an upgrade?.

The following code is for upgrading raring sources to saucy.

If you want to keep the suffix # disabled on upgrade to ..., use

for f in /etc/apt/sources.list.d/*.list; do sudo sed -i 's/raring/saucy/g' $f; sudo sed -i 's/^# (.*disabled on upgrade to.*)/1/g' $f;done

if you want to delete the suffix # disabled on upgrade to ..., use

for f in /etc/apt/sources.list.d/*.list; do sudo sed -i 's/raring/saucy/g' $f; sudo sed -i 's/^# (.*) # disabled on upgrade to.*/1/g' $f;done