State of PPA's after a distribution upgradeDistribution upgrade ErrorCan't add any PPA's after reinstalling Ubuntu 13.10Re-enable working PPA's after ubuntu upgradeapt-get loop for ppa'sDistribution upgrade stuck on postgresql confirmation window
Who inspired the character Geordi La Forge?
If we should encrypt the message rather than the method of transfer, why do we care about wifi security? Is this just security theatre?
Why it is a big deal whether or not Adam Schiff talked to the whistleblower?
Largest number order in string
How much does freezing grapes longer sweeten them more?
Multiple holes in exterior wall studs for electrical wiring
I wanna get a result of i/j . Like 1/3, 1/5, 1/7, 3/5, 3, 5/3... Something like that. But none of my code works
Prisoner's dilemma formulation for children
How do I get my boyfriend to remove pictures of his ex girlfriend hanging in his apartment?
I need an automatic way of making a lot of numbered folders
Does any politician - honestly - want a No Deal Brexit?
TV mount on wooden studs - what screws to use
How to deal with people whose priority is to not get blamed?
Charges from Dollar General have never shown up on my debit card. How can I resolve this?
Sum of all digits in a string
2000's spooky show with a group of teens telling spooky stories in the woods
What is the difference between experimental and amateur built aircraft in the US?
Are dead worlds a good galactic barrier?
Problem with NSolve with Logarithm
I run daily 5kms but I cant seem to improve stamina when playing soccer
Car as a good investment
Digit Date Range
Can Microsoft employees see my data?
On notice period - coworker I need to train is giving me the silent treatment
State of PPA's after a distribution upgrade
Distribution upgrade ErrorCan't add any PPA's after reinstalling Ubuntu 13.10Re-enable working PPA's after ubuntu upgradeapt-get loop for ppa'sDistribution upgrade stuck on postgresql confirmation window
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Suppose a hypothetical situation where I am upgrading from one version of Ubuntu to the next (e.g. 18.10 to 19.04, but can be any pair of adjacent versions), and I've got a lot of third-party repositories from which I download packages. Upon upgrading to the next distribution version, what happens to said repositories? Do they get updated, too, if available, or do they just stay on the previous version?
For example, suppose I have this repository in my sources.list or sources.list.d
deb https://something.org/stuff/foo/ cosmic main
and one for Disco Dingo exists (but is not [yet] added because it's in the next version)
deb https://something.org/stuff/foo/ disco main
Would I have to update my PPA's manually like this, or is this automatic?
apt package-management upgrade ppa
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
add a comment
|
Suppose a hypothetical situation where I am upgrading from one version of Ubuntu to the next (e.g. 18.10 to 19.04, but can be any pair of adjacent versions), and I've got a lot of third-party repositories from which I download packages. Upon upgrading to the next distribution version, what happens to said repositories? Do they get updated, too, if available, or do they just stay on the previous version?
For example, suppose I have this repository in my sources.list or sources.list.d
deb https://something.org/stuff/foo/ cosmic main
and one for Disco Dingo exists (but is not [yet] added because it's in the next version)
deb https://something.org/stuff/foo/ disco main
Would I have to update my PPA's manually like this, or is this automatic?
apt package-management upgrade ppa
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
add a comment
|
Suppose a hypothetical situation where I am upgrading from one version of Ubuntu to the next (e.g. 18.10 to 19.04, but can be any pair of adjacent versions), and I've got a lot of third-party repositories from which I download packages. Upon upgrading to the next distribution version, what happens to said repositories? Do they get updated, too, if available, or do they just stay on the previous version?
For example, suppose I have this repository in my sources.list or sources.list.d
deb https://something.org/stuff/foo/ cosmic main
and one for Disco Dingo exists (but is not [yet] added because it's in the next version)
deb https://something.org/stuff/foo/ disco main
Would I have to update my PPA's manually like this, or is this automatic?
apt package-management upgrade ppa
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
Suppose a hypothetical situation where I am upgrading from one version of Ubuntu to the next (e.g. 18.10 to 19.04, but can be any pair of adjacent versions), and I've got a lot of third-party repositories from which I download packages. Upon upgrading to the next distribution version, what happens to said repositories? Do they get updated, too, if available, or do they just stay on the previous version?
For example, suppose I have this repository in my sources.list or sources.list.d
deb https://something.org/stuff/foo/ cosmic main
and one for Disco Dingo exists (but is not [yet] added because it's in the next version)
deb https://something.org/stuff/foo/ disco main
Would I have to update my PPA's manually like this, or is this automatic?
apt package-management upgrade ppa
apt package-management upgrade ppa
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
asked May 19 at 17:45
Mona the MonadMona the Monad
1215 bronze badges
1215 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
First, recall that PPAs are NOT official, supported sources for Ubuntu software. Some projects (mis)use PPAs to distribute unofficial packages - your support for those packages comes from that project, not us. Ubuntu conducts no quality assurance or checking of any kind on most PPA packages. We have no idea if they are laden with malware or not. Use entirely at your own risk.
Second, recall that lots of terrible or ancient instructions on the internet tell folks to install PPAs quite needlessly. In many cases, the software is in the Ubuntu repositories already, or in Ubuntu's Snap Store.
Since PPAs are published by random folks across the internet, Ubuntu cannot compel them to adhere to the release schedule. Packages for a new release may appear on time, or many months later, or never. This is one reason that PPAs are automatically disabled during a release-upgrade.
You must update PPAs manually after a release upgrade.
Best practice for a trouble-free release-upgrade with PPAs:
1) Prepare: Uninstall all PPA packages and disable all PPA sources. Return your system to as close to stock condition as possible. The ppa-purge tool makes this step very easy.
2) Preparation: Update/upgrade your system to ensure your old release is up-to-date.
3) Do the release-upgrade
4) Check your list of PPAs and other Non-Ubuntu software to determine which are no longer needed. (e.g.: Don't use it anymore, the feature is now in Ubuntu, use the new Snap instead, etc.) Delete these PPAs from your list.
5) Check your list of PPAs to determine which don't have packages compatible with your new release of Ubuntu. Generally, it is a Very Bad Idea to try to install wrong-release packages. Doing so can break your system quite horribly. Revisit these PPAs in a few months to see if the new release is supported.
6) Edit and re-add the PPAs that you want to keep, and that have compatible packages for your new release. Re-add each PPA one at a time, including separate update/upgrades for each PPA. Watch your apt output carefully for errors and warnings.
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1144561%2fstate-of-ppas-after-a-distribution-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
First, recall that PPAs are NOT official, supported sources for Ubuntu software. Some projects (mis)use PPAs to distribute unofficial packages - your support for those packages comes from that project, not us. Ubuntu conducts no quality assurance or checking of any kind on most PPA packages. We have no idea if they are laden with malware or not. Use entirely at your own risk.
Second, recall that lots of terrible or ancient instructions on the internet tell folks to install PPAs quite needlessly. In many cases, the software is in the Ubuntu repositories already, or in Ubuntu's Snap Store.
Since PPAs are published by random folks across the internet, Ubuntu cannot compel them to adhere to the release schedule. Packages for a new release may appear on time, or many months later, or never. This is one reason that PPAs are automatically disabled during a release-upgrade.
You must update PPAs manually after a release upgrade.
Best practice for a trouble-free release-upgrade with PPAs:
1) Prepare: Uninstall all PPA packages and disable all PPA sources. Return your system to as close to stock condition as possible. The ppa-purge tool makes this step very easy.
2) Preparation: Update/upgrade your system to ensure your old release is up-to-date.
3) Do the release-upgrade
4) Check your list of PPAs and other Non-Ubuntu software to determine which are no longer needed. (e.g.: Don't use it anymore, the feature is now in Ubuntu, use the new Snap instead, etc.) Delete these PPAs from your list.
5) Check your list of PPAs to determine which don't have packages compatible with your new release of Ubuntu. Generally, it is a Very Bad Idea to try to install wrong-release packages. Doing so can break your system quite horribly. Revisit these PPAs in a few months to see if the new release is supported.
6) Edit and re-add the PPAs that you want to keep, and that have compatible packages for your new release. Re-add each PPA one at a time, including separate update/upgrades for each PPA. Watch your apt output carefully for errors and warnings.
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
add a comment
|
First, recall that PPAs are NOT official, supported sources for Ubuntu software. Some projects (mis)use PPAs to distribute unofficial packages - your support for those packages comes from that project, not us. Ubuntu conducts no quality assurance or checking of any kind on most PPA packages. We have no idea if they are laden with malware or not. Use entirely at your own risk.
Second, recall that lots of terrible or ancient instructions on the internet tell folks to install PPAs quite needlessly. In many cases, the software is in the Ubuntu repositories already, or in Ubuntu's Snap Store.
Since PPAs are published by random folks across the internet, Ubuntu cannot compel them to adhere to the release schedule. Packages for a new release may appear on time, or many months later, or never. This is one reason that PPAs are automatically disabled during a release-upgrade.
You must update PPAs manually after a release upgrade.
Best practice for a trouble-free release-upgrade with PPAs:
1) Prepare: Uninstall all PPA packages and disable all PPA sources. Return your system to as close to stock condition as possible. The ppa-purge tool makes this step very easy.
2) Preparation: Update/upgrade your system to ensure your old release is up-to-date.
3) Do the release-upgrade
4) Check your list of PPAs and other Non-Ubuntu software to determine which are no longer needed. (e.g.: Don't use it anymore, the feature is now in Ubuntu, use the new Snap instead, etc.) Delete these PPAs from your list.
5) Check your list of PPAs to determine which don't have packages compatible with your new release of Ubuntu. Generally, it is a Very Bad Idea to try to install wrong-release packages. Doing so can break your system quite horribly. Revisit these PPAs in a few months to see if the new release is supported.
6) Edit and re-add the PPAs that you want to keep, and that have compatible packages for your new release. Re-add each PPA one at a time, including separate update/upgrades for each PPA. Watch your apt output carefully for errors and warnings.
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
add a comment
|
First, recall that PPAs are NOT official, supported sources for Ubuntu software. Some projects (mis)use PPAs to distribute unofficial packages - your support for those packages comes from that project, not us. Ubuntu conducts no quality assurance or checking of any kind on most PPA packages. We have no idea if they are laden with malware or not. Use entirely at your own risk.
Second, recall that lots of terrible or ancient instructions on the internet tell folks to install PPAs quite needlessly. In many cases, the software is in the Ubuntu repositories already, or in Ubuntu's Snap Store.
Since PPAs are published by random folks across the internet, Ubuntu cannot compel them to adhere to the release schedule. Packages for a new release may appear on time, or many months later, or never. This is one reason that PPAs are automatically disabled during a release-upgrade.
You must update PPAs manually after a release upgrade.
Best practice for a trouble-free release-upgrade with PPAs:
1) Prepare: Uninstall all PPA packages and disable all PPA sources. Return your system to as close to stock condition as possible. The ppa-purge tool makes this step very easy.
2) Preparation: Update/upgrade your system to ensure your old release is up-to-date.
3) Do the release-upgrade
4) Check your list of PPAs and other Non-Ubuntu software to determine which are no longer needed. (e.g.: Don't use it anymore, the feature is now in Ubuntu, use the new Snap instead, etc.) Delete these PPAs from your list.
5) Check your list of PPAs to determine which don't have packages compatible with your new release of Ubuntu. Generally, it is a Very Bad Idea to try to install wrong-release packages. Doing so can break your system quite horribly. Revisit these PPAs in a few months to see if the new release is supported.
6) Edit and re-add the PPAs that you want to keep, and that have compatible packages for your new release. Re-add each PPA one at a time, including separate update/upgrades for each PPA. Watch your apt output carefully for errors and warnings.
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
First, recall that PPAs are NOT official, supported sources for Ubuntu software. Some projects (mis)use PPAs to distribute unofficial packages - your support for those packages comes from that project, not us. Ubuntu conducts no quality assurance or checking of any kind on most PPA packages. We have no idea if they are laden with malware or not. Use entirely at your own risk.
Second, recall that lots of terrible or ancient instructions on the internet tell folks to install PPAs quite needlessly. In many cases, the software is in the Ubuntu repositories already, or in Ubuntu's Snap Store.
Since PPAs are published by random folks across the internet, Ubuntu cannot compel them to adhere to the release schedule. Packages for a new release may appear on time, or many months later, or never. This is one reason that PPAs are automatically disabled during a release-upgrade.
You must update PPAs manually after a release upgrade.
Best practice for a trouble-free release-upgrade with PPAs:
1) Prepare: Uninstall all PPA packages and disable all PPA sources. Return your system to as close to stock condition as possible. The ppa-purge tool makes this step very easy.
2) Preparation: Update/upgrade your system to ensure your old release is up-to-date.
3) Do the release-upgrade
4) Check your list of PPAs and other Non-Ubuntu software to determine which are no longer needed. (e.g.: Don't use it anymore, the feature is now in Ubuntu, use the new Snap instead, etc.) Delete these PPAs from your list.
5) Check your list of PPAs to determine which don't have packages compatible with your new release of Ubuntu. Generally, it is a Very Bad Idea to try to install wrong-release packages. Doing so can break your system quite horribly. Revisit these PPAs in a few months to see if the new release is supported.
6) Edit and re-add the PPAs that you want to keep, and that have compatible packages for your new release. Re-add each PPA one at a time, including separate update/upgrades for each PPA. Watch your apt output carefully for errors and warnings.
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
edited May 20 at 14:28
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
answered May 19 at 18:32
user535733user535733
11.3k3 gold badges33 silver badges49 bronze badges
11.3k3 gold badges33 silver badges49 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1144561%2fstate-of-ppas-after-a-distribution-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
