How to remove broken PPAs using Terminal at once? [on hold] Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to cleanly remove a badly installed .deb?How to use apt-get to install packages without one specify package?How to use sed to edit /var/log/apt/history.log in order to apt-get remove numerous installed packages?Automatically disable a ppa'apt-get update' fails when using proxyHow Do I fix my particular broken package system?Install multiple ppas at once via terminal without using scriptHow to purge Steam ppa completelyDpkg: error processing package linux-image-extra-3.13.0-93-genericCommand not found: apt-get
Seeking colloquialism for “just because”
Why light coming from distant stars is not discreet?
How come Sam didn't become Lord of Horn Hill?
Can I cast Passwall to drop an enemy into a 20-foot pit?
Okay to merge included columns on otherwise identical indexes?
How discoverable are IPv6 addresses and AAAA names by potential attackers?
What is Arya's weapon design?
When do you get frequent flier miles - when you buy, or when you fly?
ListPlot join points by nearest neighbor rather than order
51k Euros annually for a family of 4 in Berlin: Is it enough?
Compare a given version number in the form major.minor.build.patch and see if one is less than the other
Is it fair for a professor to grade us on the possession of past papers?
What is known about the Ubaid lizard-people figurines?
How to find all the available tools in mac terminal?
Extract all GPU name, model and GPU ram
How do I stop a creek from eroding my steep embankment?
How does debian/ubuntu knows a package has a updated version
When a candle burns, why does the top of wick glow if bottom of flame is hottest?
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
Fundamental Solution of the Pell Equation
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
How can I make names more distinctive without making them longer?
Can an alien society believe that their star system is the universe?
Error "illegal generic type for instanceof" when using local classes
How to remove broken PPAs using Terminal at once? [on hold]
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to cleanly remove a badly installed .deb?How to use apt-get to install packages without one specify package?How to use sed to edit /var/log/apt/history.log in order to apt-get remove numerous installed packages?Automatically disable a ppa'apt-get update' fails when using proxyHow Do I fix my particular broken package system?Install multiple ppas at once via terminal without using scriptHow to purge Steam ppa completelyDpkg: error processing package linux-image-extra-3.13.0-93-genericCommand not found: apt-get
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have lots of broken PPAs that I like to get rid of, but since I have lots of PPAs in general, deleting them by hand is not an option. I want to somehow delete all broken PPAs at once. Thank you for your help!
EDIT: This is the result of sudo apt-get update | grep Failed. I think this might be a good indicator whether a PPA is broken or not.
apt lubuntu ppa 19.04
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
put on hold as off-topic by Kulfy, fkraiem, karel, N0rbert, Eric Carvalho Apr 13 at 15:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Kulfy, fkraiem, karel, N0rbert, Eric Carvalho
|
show 3 more comments
I have lots of broken PPAs that I like to get rid of, but since I have lots of PPAs in general, deleting them by hand is not an option. I want to somehow delete all broken PPAs at once. Thank you for your help!
EDIT: This is the result of sudo apt-get update | grep Failed. I think this might be a good indicator whether a PPA is broken or not.
apt lubuntu ppa 19.04
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
put on hold as off-topic by Kulfy, fkraiem, karel, N0rbert, Eric Carvalho Apr 13 at 15:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Kulfy, fkraiem, karel, N0rbert, Eric Carvalho
1
I don't know any general method, that can tell the difference between good and broken PPAs. But you can trysudo add-apt-repository -r ppa:whatever-you-want-to-removefor each PPA that you want to get rid of.
– sudodus
Apr 12 at 18:53
@sudodus PPAs that fail when callingapt-get updateshall be a good indicator IMO.
– Farhood ET
Apr 12 at 18:56
In that case you can use that information in a shellscript file in order to decide which PPAs to treat withadd-apt-repository -r
– sudodus
Apr 12 at 18:58
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output ofsudo apt-get update | grep Failed. pastebin.com/MiiLHZYX
– Farhood ET
Apr 12 at 19:05
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15
|
show 3 more comments
I have lots of broken PPAs that I like to get rid of, but since I have lots of PPAs in general, deleting them by hand is not an option. I want to somehow delete all broken PPAs at once. Thank you for your help!
EDIT: This is the result of sudo apt-get update | grep Failed. I think this might be a good indicator whether a PPA is broken or not.
apt lubuntu ppa 19.04
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
I have lots of broken PPAs that I like to get rid of, but since I have lots of PPAs in general, deleting them by hand is not an option. I want to somehow delete all broken PPAs at once. Thank you for your help!
EDIT: This is the result of sudo apt-get update | grep Failed. I think this might be a good indicator whether a PPA is broken or not.
apt lubuntu ppa 19.04
apt lubuntu ppa 19.04
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
edited Apr 13 at 5:49
Farhood ET
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
asked Apr 12 at 18:35
Farhood ETFarhood ET
1217
1217
put on hold as off-topic by Kulfy, fkraiem, karel, N0rbert, Eric Carvalho Apr 13 at 15:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Kulfy, fkraiem, karel, N0rbert, Eric Carvalho
put on hold as off-topic by Kulfy, fkraiem, karel, N0rbert, Eric Carvalho Apr 13 at 15:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Kulfy, fkraiem, karel, N0rbert, Eric Carvalho
1
I don't know any general method, that can tell the difference between good and broken PPAs. But you can trysudo add-apt-repository -r ppa:whatever-you-want-to-removefor each PPA that you want to get rid of.
– sudodus
Apr 12 at 18:53
@sudodus PPAs that fail when callingapt-get updateshall be a good indicator IMO.
– Farhood ET
Apr 12 at 18:56
In that case you can use that information in a shellscript file in order to decide which PPAs to treat withadd-apt-repository -r
– sudodus
Apr 12 at 18:58
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output ofsudo apt-get update | grep Failed. pastebin.com/MiiLHZYX
– Farhood ET
Apr 12 at 19:05
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15
|
show 3 more comments
1
I don't know any general method, that can tell the difference between good and broken PPAs. But you can trysudo add-apt-repository -r ppa:whatever-you-want-to-removefor each PPA that you want to get rid of.
– sudodus
Apr 12 at 18:53
@sudodus PPAs that fail when callingapt-get updateshall be a good indicator IMO.
– Farhood ET
Apr 12 at 18:56
In that case you can use that information in a shellscript file in order to decide which PPAs to treat withadd-apt-repository -r
– sudodus
Apr 12 at 18:58
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output ofsudo apt-get update | grep Failed. pastebin.com/MiiLHZYX
– Farhood ET
Apr 12 at 19:05
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15
1
1
I don't know any general method, that can tell the difference between good and broken PPAs. But you can try
sudo add-apt-repository -r ppa:whatever-you-want-to-remove for each PPA that you want to get rid of.– sudodus
Apr 12 at 18:53
I don't know any general method, that can tell the difference between good and broken PPAs. But you can try
sudo add-apt-repository -r ppa:whatever-you-want-to-remove for each PPA that you want to get rid of.– sudodus
Apr 12 at 18:53
@sudodus PPAs that fail when calling
apt-get update shall be a good indicator IMO.– Farhood ET
Apr 12 at 18:56
@sudodus PPAs that fail when calling
apt-get update shall be a good indicator IMO.– Farhood ET
Apr 12 at 18:56
In that case you can use that information in a shellscript file in order to decide which PPAs to treat with
add-apt-repository -r– sudodus
Apr 12 at 18:58
In that case you can use that information in a shellscript file in order to decide which PPAs to treat with
add-apt-repository -r– sudodus
Apr 12 at 18:58
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output of
sudo apt-get update | grep Failed. pastebin.com/MiiLHZYX– Farhood ET
Apr 12 at 19:05
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output of
sudo apt-get update | grep Failed. pastebin.com/MiiLHZYX– Farhood ET
Apr 12 at 19:05
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15
|
show 3 more comments
1 Answer
1
active
oldest
votes
We really don't discuss 19.04 until later this month when it's formally released. You caused these problems mostly by prematurely upgrading to a as yet unreleased version of Ubuntu.
However, to solve your problem...
is configured multiple times in /etc/apt/sources.list:50 and /etc/apt/sources.list.d/vivaldi.list:3
It tells you right there where the problem is. You have the same repository entered twice, once in sources.list line 50, and vivaldi.list line 3. View vivadi.list, and then edit sources.list and remove the duplicate entry on line 50.
The repository 'http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu disco Release' does not have a Release file.
Because you upgraded to 19.04 prematurely, some PPA's got updated to the disco release prematurely, and those don't exist yet. Edit each of these and use cosmic, or some older Ubuntu release. Easiest to do this in Software & Updates application.
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
We really don't discuss 19.04 until later this month when it's formally released. You caused these problems mostly by prematurely upgrading to a as yet unreleased version of Ubuntu.
However, to solve your problem...
is configured multiple times in /etc/apt/sources.list:50 and /etc/apt/sources.list.d/vivaldi.list:3
It tells you right there where the problem is. You have the same repository entered twice, once in sources.list line 50, and vivaldi.list line 3. View vivadi.list, and then edit sources.list and remove the duplicate entry on line 50.
The repository 'http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu disco Release' does not have a Release file.
Because you upgraded to 19.04 prematurely, some PPA's got updated to the disco release prematurely, and those don't exist yet. Edit each of these and use cosmic, or some older Ubuntu release. Easiest to do this in Software & Updates application.
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
add a comment |
We really don't discuss 19.04 until later this month when it's formally released. You caused these problems mostly by prematurely upgrading to a as yet unreleased version of Ubuntu.
However, to solve your problem...
is configured multiple times in /etc/apt/sources.list:50 and /etc/apt/sources.list.d/vivaldi.list:3
It tells you right there where the problem is. You have the same repository entered twice, once in sources.list line 50, and vivaldi.list line 3. View vivadi.list, and then edit sources.list and remove the duplicate entry on line 50.
The repository 'http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu disco Release' does not have a Release file.
Because you upgraded to 19.04 prematurely, some PPA's got updated to the disco release prematurely, and those don't exist yet. Edit each of these and use cosmic, or some older Ubuntu release. Easiest to do this in Software & Updates application.
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
add a comment |
We really don't discuss 19.04 until later this month when it's formally released. You caused these problems mostly by prematurely upgrading to a as yet unreleased version of Ubuntu.
However, to solve your problem...
is configured multiple times in /etc/apt/sources.list:50 and /etc/apt/sources.list.d/vivaldi.list:3
It tells you right there where the problem is. You have the same repository entered twice, once in sources.list line 50, and vivaldi.list line 3. View vivadi.list, and then edit sources.list and remove the duplicate entry on line 50.
The repository 'http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu disco Release' does not have a Release file.
Because you upgraded to 19.04 prematurely, some PPA's got updated to the disco release prematurely, and those don't exist yet. Edit each of these and use cosmic, or some older Ubuntu release. Easiest to do this in Software & Updates application.
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
We really don't discuss 19.04 until later this month when it's formally released. You caused these problems mostly by prematurely upgrading to a as yet unreleased version of Ubuntu.
However, to solve your problem...
is configured multiple times in /etc/apt/sources.list:50 and /etc/apt/sources.list.d/vivaldi.list:3
It tells you right there where the problem is. You have the same repository entered twice, once in sources.list line 50, and vivaldi.list line 3. View vivadi.list, and then edit sources.list and remove the duplicate entry on line 50.
The repository 'http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu disco Release' does not have a Release file.
Because you upgraded to 19.04 prematurely, some PPA's got updated to the disco release prematurely, and those don't exist yet. Edit each of these and use cosmic, or some older Ubuntu release. Easiest to do this in Software & Updates application.
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
answered Apr 13 at 13:09
heynnemaheynnema
21.6k32361
21.6k32361
add a comment |
add a comment |
1
I don't know any general method, that can tell the difference between good and broken PPAs. But you can try
sudo add-apt-repository -r ppa:whatever-you-want-to-removefor each PPA that you want to get rid of.– sudodus
Apr 12 at 18:53
@sudodus PPAs that fail when calling
apt-get updateshall be a good indicator IMO.– Farhood ET
Apr 12 at 18:56
In that case you can use that information in a shellscript file in order to decide which PPAs to treat with
add-apt-repository -r– sudodus
Apr 12 at 18:58
@sudodus I'm not very good with shellscripts. Could you write me one? here's the output of
sudo apt-get update | grep Failed. pastebin.com/MiiLHZYX– Farhood ET
Apr 12 at 19:05
I don't say no, but I can't do it now. Let us hope that someone else has better time this weekend and can help you.
– sudodus
Apr 12 at 19:15