FS#4060 - pacman: "something has gone horribly wrong"

Attached to Project: Pacman
Opened by Jan Willemson (janwill) - Saturday, 25 February 2006, 15:55 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 24 January 2007, 11:16 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

Today I tried to upgrade my system to XOrg7. I hadn't done upgrading for some time, so there were more than 500MB of downloads necessary. I started downloading from one mirror, but that was rather slow. So I interrupted the pacman -Syu upgrade by killing pacman and wget, changed pacman.conf to point to another mirror and continued. The downloads finished well and package integrity check was successful. But then I got the following error message:

error: something has gone horribly wrong

This looks like an error message that actually should never occur -- but it did. Later I cleaned the package cache and downloaded all the 500MB again, but the message was still the same. Then I tried updating XOrg first. This upgrade was successful, but pacman -Syu after that failed with the same error message.

Jan
This task depends upon

This task blocks these from closing
 FS#6316 - Pacman 3 release bugcatcher 
Closed by  Aaron Griffin (phrakture)
Wednesday, 21 February 2007, 16:48 GMT
Reason for closing:  Works for me
Additional comments about closing:  No longer a pacman3 bug.
Comment by Jan Willemson (janwill) - Saturday, 25 February 2006, 17:00 GMT
I located the suspect. Among packages to be upgraded there is avahi which conflicts with nss-mdns. I am prompted to remove nss-mdns and after saying "Y" I get the "something has gone horribly wrong" error. This was reproduced when doing

pacman -S avahi

only.

Jan
Comment by Jan Willemson (janwill) - Saturday, 25 February 2006, 17:08 GMT
Another comment -- it seems to be the case that on one hand nss-mdns conflicts with avahi, but on the other hand nss-mdns is required by avahi, as can be seen from the output of

pacman -R nss-mdns

I can understand that pacman gets confused, but the situation should be handled a bit better by him.

Jan
Comment by Glenn Matthys (RedShift) - Wednesday, 05 April 2006, 20:57 GMT
I had this error with the hotplug/udev conflict stuff. After removing hotplug manually the upgrade went fine.
Comment by Aaron Griffin (phrakture) - Wednesday, 03 January 2007, 08:30 GMT
Is this still an issue with pacman3? It looks almost like that would be an infinite dep cycle... but I don't really have a history on what the error message actually meant.... /me shrugs
Comment by Georg Grabler (STiAT) - Tuesday, 20 February 2007, 00:00 GMT
Well, i think the error can be tacked back to dependency calculation.

I've had a short look in the depend calculation, and as it seems it just builds up a list. Just iterating trough the whole depend list should figure out if the dependency actually is in the list in a prior place than the package to be installed.

I don't know if that's already in, but shouldn't be too much to figure out.

I think this happened or happens if cycles are in the depend list, or if the replaces array isn't set correctly...

It should be tested against trash packages built for this once, to just see the effect (like 2 packages depending on each other, 3 packages with a cycle etc). Maybe a common test case, which could be included in the pacman release tests (if it isn't already).
Comment by Aaron Griffin (phrakture) - Wednesday, 21 February 2007, 16:47 GMT
This error is still in the source for pacman3, however, it is no longer the same error. In fact, I don't even know the error case that it could happen in.

It appears that pacman3 can only output this error in an odd case that I don't even understand. This comment makes no sense:

/* If miss->depend.name depends on something that miss->target and a package in final both provide, then it's okay... */

For now, I'm going to close this bug. If we can get more specific data for pacman3, then I will reopen this, or open a more descriptive bug report.

Loading...