Any hope for the Yakkety cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/502454
Title:
add-apt-repository should allow version specification or offer next
highest repo version if repo for
Any hope for the Oneiric cycle.
I know a fair amount of Python, but don't want to do this myself.
D:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/502454
Title:
add-apt-repository should allow
With Maverick repos open, this bug once again rears its ugly head.
--
add-apt-repository should allow version specification or offer next highest
repo version if repo for running version is not found
https://bugs.launchpad.net/bugs/502454
You received this bug notification because you are a
** Changed in: software-properties (Ubuntu)
Status: New = Confirmed
** Changed in: software-properties (Ubuntu)
Importance: Undecided = Wishlist
--
add-apt-repository should allow version specification or offer next highest
repo version if repo for running version is not found
Sorry about the duplicate labeling, some guy in #ubuntu-desktop had told
me to.
--
add-apt-repository should allow version specification or offer next highest
repo version if repo for running version is not found
https://bugs.launchpad.net/bugs/502454
You received this bug notification because
That would be me :-)
I'm pretty new in this community, and have been working on bugfixing in
the software-properties package. As I have been told when I raised the
question myself, it's not the date that matters when marking an issue as
duplicate, but the amount of information, clarity, or
** Summary changed:
- add-apt-repository should offer next highest repo version if repo for running
version is not found
+ add-apt-repository should allow version specification or offer next highest
repo version if repo for running version is not found
--
add-apt-repository should allow
How is it possible that a bug reported 2 months ago is marked a
duplicate of the same bug reported 3 hours ago?
Does anyone know how to unmark the original bug as a duplicate and mark this as
it should be?
By the way, this application does not look at uname for it's
information. Uname is used
