Why is cedet-common and cedet-contrib removed from natty

Asked by Philipp Lies

Package got deinstalled during update from 10.10 to 11.04 beta 3. Reinstalling via "apt-get install cedet-common" leads to "Package 'cedet-common' has no installation candidate"

Tried to file a bug report but ubuntu-bug crashes with ValueError package cedet-common does not exist. Same for cedet-contrib. What's going on?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu cedet Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Are you using 32bit or 64bit Ubuntu?

Revision history for this message
Philipp Lies (philipp-lies) said :
#2

64bit, started update-manager last night, all updates installed

Revision history for this message
Philipp Lies (philipp-lies) said :
#3

64bit, started update-manager last night, all updates installed

Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#4
Revision history for this message
Philipp Lies (philipp-lies) said :
#5

Thanks for the info. For the sake of completeness, I also installed cedet-contrib which needed some more packages (in the order of installation dependencies, links to deps are on the pages):

https://launchpad.net/ubuntu/natty/amd64/eieio/1:1.0pre4-3.1
https://launchpad.net/ubuntu/natty/amd64/ede/1:1.0pre4-3.1
https://launchpad.net/ubuntu/natty/amd64/speedbar/1:1.0pre4-3.1
https://launchpad.net/ubuntu/natty/amd64/semantic/1:1.0pre4-3.1
https://launchpad.net/ubuntu/natty/amd64/cedet-contrib/1:1.0pre4-3.1

Will this problem be fixed in the final version or will this manual installation still be required?

Revision history for this message
Philipp Lies (philipp-lies) said :
#6

Thanks actionparsnip, that solved my question.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

Great share, hopefully this will help others seeking the same package and they can then fix it just the way you did. Can you also log a bug with your fix to inform the devs

Glad you got the gold
:D

Revision history for this message
Philipp Lies (philipp-lies) said :
#8
Revision history for this message
Eliah Kagan (degeneracypressure) said :
#9

@Philipp
When you tried to report a bug, did ubuntu-bug *crash*, or did it simply give the error message "Package cedet-common does not exist" (with the title bar text "Invalid problem report")? If it crashed--and it sounds like you're saying it did, since you said it reported ValueError--then did another instance of Apport get launched to enable you to report *that* crash? *That* crash certainly is a bug...

Revision history for this message
Philipp Lies (philipp-lies) said :
#10

I started ubuntu-bug from console.
python threw a ValueError exception with "Package cedet-common does not exist" as message text and the backtrace of the thrown exception.
An Apport window did not pop up afterwards.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#11
Revision history for this message
Eliah Kagan (degeneracypressure) said :
#12

If you're interested to help get this bug examined and fixed, then please:

(1) Update your system fully and see if you can still reproduce this problem. (You should also see if you can reproduce the problem by running ubuntu-bug with the name of a different package that is not present in Natty, preferably one not present in any Ubuntu release, such as the fictitious package called nonexistent-package. When you report the bug or comment on an existing report, you can report whether or not that also produced it, and if there were any differences.)

(2) If so, and you have not done so already, read https://help.ubuntu.com/community/ReportingBugs carefully.

(3) Search for previous reports of the bug on Launchpad; if you find one, you can indicate it affects you using the green "This bug affects" near the top of the bug page, post any missing information in it with a comment (for example, if you experience the bug with a different Ubuntu release, different architecture, different version of the package apport, or any other significant differences including any differences, however small, in the backtrace--if your backtrace is different or there is no backtrace in the existing bug report, you can post or attach yours in full).

(4) If you didn't find this bug already reported, then report it by running "ubuntu-bug apport". (Normally it is preferable to report crashes by configuring apport to launch automatically, and preferable to report non-crashes by running ubuntu-bug with the PID of the relevant process, but in this case, reporting it against the apport package and then manually including the backtrace and other relevant information seems like the best that can be done.) Include a full description of what you did and what happened, including all the text from the Terminal. It is especially important that the backtrace be included in full. After reporting your bug, it's a good idea to link it to this question using the "Link existing bug" link on this question page under "Related bugs" (you can keep bug 767301 linked too--no need to remove it). However, your bug report should be complete and self-contained--it should not be necessary for the Ubuntu developers to refer to this question in order to fully understand

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#13

@actionparsnip
In this case, it is substantially preferable to report the bug with "ubuntu-bug apport" because that will include version, dependency, and configuration information regarding apport on this user's system. This does not appear to be an easily reproducible crash in apport. For example, I am unable to reproduce it on my Natty system. Therefore, this information, much of which would likely be left out of the bug report or presented less clearly, will likely be very important.

Revision history for this message
Ramkumar R. Aiyengar (andyetitmoves) said :
#14

I was able to track it down to this:
https://bugs.launchpad.net/ubuntu/+source/cedet/+bug/733527
which leads to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617267
Looks like Emacs has now pulled in the package. Hope that helps!