When installing ktorrent-dbgsym, adept wants to install gnome packages

Bug #120824 reported by agrabah
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I don't really know if it's adepts fault, or if the ktorrent-dbgsym package is faulty.
Anyway: I wanted to install ktorrent-dbgsym from http://people.ubuntu.com/~pitti/ddebs repository, and adept says the commit would break packages. I wondered why, because package info states it requires only ktorrent, and indicated no conflicts. I then discovered adept wants to install a whole bunch of other packages (not required ones - see the appended picture), together 24 packages. I didn't even try to commit changes.

Steps to recreate:
1. start adept
2. add aforementioned repository
3. pick ktorrent-dbgsym
4. click install
5. see preview changes

This let it happen on my box, which is Kubuntu Feisty (up to date as per regular updates), KDE 3.5.7.

Cheers,
Tine

Revision history for this message
agrabah (agrabah) wrote :
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

emilio@kiko:~$ aptitude show ktorrent-dbgsym | grep Depends
Depends: ktorrent (= 2.2~rc1-0ubuntu1)

So it doesn't seem to be a dbgsym issue...
That's in Gutsy, if you're in Gutsy, please run that command, and put here the output.

Also, did you have ktorrent installed before installing the -dbgsym package?

Revision history for this message
agrabah (agrabah) wrote :

Yes, I did have ktorrent installed. And I'm not in Gutsy, I'm running Feisty. Anyway, I ran the command (just in case) and I did
get a similar, but not quite identical output:

tine@durumba:~$ aptitude show ktorrent-dbgsym | grep Depends
Depends: ktorrent (= 2.1-0ubuntu2)

Interlude... (I decided to check the behavior of adept when installing other stuff)

Uh-oh. Happens with other packages too.

When I tried to install adept-manager-dbgsym in apt-get, I told me the commit would break packages, too, because a newer version of adept-manager is required. I guess I understand what you meant by "That's in Gutsy" - those dbgsym packages are probably for Gutsy, Right?

Now I think it happens only with dbgsym packages which are meant for Gutsy (or require a newer version of its "mother package" than Feisty repositories provides). I could find only two - Adept-manager-dbgsym and ktorrent-dbgsym. It tells me the commit would break packages; and when I pick undo, 23 packages (on the picture-list) are automagically added to the instalation queue.

Anyway - This problem started today (maybe after I installed KDE 3.5.7; I'm not sure). It could be an issue on my machine, but I don't really know how to check. Oddly enough adept always starts with an empty instalation queue.

Tine

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

No, you have the Feisty debug symbol repository. That's ok.

Try to simply update the system, without installing any dbgsym package, and see if it tries to install those gnome libraries (to see if it's a dgbsym problem or not).

Revision history for this message
agrabah (agrabah) wrote :

There are no updates pending (the "full Upgrade" button is greyed out, too), so I tried apt-get upgrade. Confirmed previous results - no upgrades pending.
I fetched updates in adept, and there still aren't any upgrades pending.

Just for the heck of it I tried to recreate the problem one more time... and after the update the ktorrent-dbgsym and adept-manager-dbgsym packages still break other packages (though I've no idea which packages), adept does not try to install a bunch of gnome packages. I guess it was just a flux, mended by fetching the updates.

So I guess this is not a bug after all. Sorry for the unnecessary work I've caused.

Tine

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

In such case I'm closing this report. Please, don't hesitate to reopen it if you need to.

Regards

Changed in adept:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.