The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: software-properties (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: software-properties (Ubuntu Precise)
Assignee: Didier Roche (didrocks) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936186
Title:
add-apt-repository crashed with
** Changed in: software-properties (Ubuntu Precise)
Milestone: ubuntu-12.04.2 = ubuntu-12.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936186
Title:
add-apt-repository crashed with error
same problem here jus started this morning
cmcanulty@HPTech:~$ sudo add-apt-repository ppa:gnome3-team/gnome3
[sudo] password for cmcanulty:
Traceback (most recent call last):
File /usr/bin/add-apt-repository, line 125, in module
ppa_info = get_ppa_info_from_lp(user, ppa_name)
File
** Changed in: software-properties (Ubuntu Precise)
Milestone: ubuntu-12.04.1 = ubuntu-12.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936186
Title:
add-apt-repository crashed with error
Part of the reason there are two different tracebaks is that the
duplicate database doesn't consider enough of the Traceback for the
signatures to be unique:
936186 /usr/bin/add-apt-repository:error:module:get_ppa_info_from_lp
I suggest that we fix the issue that is being reported on
Additionally, based of data obtained from errors.ubuntu.com,
(https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fadd-apt-
repository%3Aerror%3A%3Cmodule%3E%3Aget_ppa_info_from_lp), and since
Quantal no longer uses curl but rather urllib2 this bug is fixed in
Quantal.
** Changed in:
The initial backtrace and the can't resolve backtrace seem to be quite
different.
The first looks like it would be triggered by some bad data coming over https
where the other one is simply because resolving fails.
Catching the DNS resolution problem should be trivial, the initial
traceback
Didier, is there any chance that you look at this one as well (or get mvo to
look at it by asking questions on how to fix it if needed ;-)
The bug scored 916 reports in 5 days on errors.ubuntu.com in July
** Changed in: software-properties (Ubuntu Precise)
Milestone: precise-updates =
** Changed in: software-properties (Ubuntu)
Status: Confirmed = New
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) = ByungGulRyu (baramryu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
file /usr/bin/add-apt-repository, line 125, in ,module ppa_info =
get_info_from_lp (user,ppa_name)
file usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 80, in
get_ppa_info_from_lp curl.perform () pycurl.error: 6, couldn't resolve host
'launchpad.net'
after fresh install
Thanx
There is a bug with a similar signature ranked 4rd on errors.ubuntu.com
(over 2100 reports yesterday), the error is sometime different though:
File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 80,
in get_ppa_info_from_lp
curl.perform()
error: (6, Couldn't resolve host
** Visibility changed to: Public
** Changed in: software-properties (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936186
Title:
add-apt-repository
13 matches
Mail list logo
