Archived thread 1479468 from Maverick Meerkat Testing and Discussion (CLOSED). Markdown source: Maverick_Meerkat_Testing_and_Discussion_(CLOSED)/thread_1479468_Adding_PPAs_without_manually_adding_keys_is_such_a.md
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/502454
This bug needs more attention.
Basically, until Maverick PPA repos start popping up, we either have to use the deb/deb-src and manually add the key or use the ppa:blah/blah method and change the maverick to lucid in Software Souces for that PPA.
Well, it's my bug report. I can frame it however I wish. Besides, I forgot a single digit in the URL.
Ok I see. You link to 50245 but it should be 502454. The text is ok, but the link is wrong.
As far as the title to the thread, YES :)
Link should be fine now.
Starks said: Adding PPAs without manually adding keys is such a pain right now.
Er, what?
sudo add-apt-repository ppa:<user>/<ppa>What a pain...
You totally missed the point.
Doing that will add the repo as maverick and not function at all until you change the source to lucid.
99% of PPA repos are still lucid or older.
How many PPAs do you add per day? :D apt-add-repository takes care of the key and changing the distribution field in "Software Sources" is a non-issue to me. The proposed change would be nice, though.
There’s no guarantee that packages pulled from other releases will work. There can be changes to ABI and in libc, glib, and all sorts of other libraries.
That isn't a problem for most PPAs. If a PPA only has a repo for an older release, chances are that the Ubuntu main repo already supersedes the PPA's packages.
Secondly, people on Maverick who want to use PPAs like ubuntu-mozilla-daily or xorg-edgers have been told by the respective PPA maintainers to use the Lucid repo.
Starks said:
Secondly, people on Maverick who want to use PPAs like ubuntu-mozilla-daily or xorg-edgers have been told by the respective PPA maintainers to use the Lucid repo.
..., use the lucid repos or help them in building packages for maverick.
There’s no guarantee that packages pulled from other releases will work.
There is not guarantee that any package in a ppa will work!
Most of those libraries are designed to be backwards compatible. And besides many of us have been doing this type of naughty stuff for years. And at this point in development (e.g. pre-alpha) I would hope we would have permission to completely fry out installs!
nanog said: There is not guarantee that any package in a ppa will work!
Most of those libraries are designed to be backwards compatible. And besides many of us have been doing this type of naughty stuff for years. And at this point in development (e.g. pre-alpha) I would hope we would have permission to completely fry out installs! I certainly haven't been doing this "naughty stuff" for years but I do have a lot of installs and I do have permission to fry as many as I want.
I know I do. I have it on a sticky note on my tower.
Starks said: Basically, until Maverick PPA repos start popping up, we either have to use the deb/deb-src and manually add the key or use the ppa:blah/blah method and change the maverick to lucid in Software Souces for that PPA.
Maybe the command line script should be fixed for those adding PPAs that way, but I can't really say I feel your pain.
If I go to 'System --> Administration --> Software Sources'.....
Or my preference, since if I am adding a PPA I will probably want to be installing something right away....
Open Synaptic and go to 'Settings --> Respositories --> Other Sofware --> Add'......
Type in the line to add the PPA, I used... ``` ppa:ubuntu-mozilla-daily/ppa
The key seemed to be handled, at least I never saw any complaints any where.
If you need to change the distribution, scroll down the list, select the newly added entry, click on 'Edit', do it.
Where's the pain in that? :P
Later, SeekerThere's no real pain there, but I agree it's annoying. Mvo has acknowledged the bug so he plans to implement it sometime... To increase the priority a bit everyone that agrees with this should set the bug as affecting him. Thanks!