search

dskvr / opkg

Automatically exported from code.google.com/p/opkg
0 stars 0 forks source link

Fixed in r625 #79

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Given three packages A, B, C
     A depends on B
     A failed postinst and is in unpacked state
     C depends on B
2. Upgrade to a new version of C which do not depends on B anymore, and use 
--autoremove

What is the expected output? What do you see instead?
1. B should not be removed, bot opkg uninstall it.

Original issue reported on code.google.com by pixdamix@gmail.com on 12 Jul 2011 at 7:26

GoogleCodeExporter commented 8 years ago 
Can anyone review this patch. I'm pretty sure it's ok, but better safe than 
sorry.

Original comment by pixdamix@gmail.com on 12 Jul 2011 at 7:35

Attachments:

GoogleCodeExporter commented 8 years ago 
This looks correct, feel free to commit it.

Interesting that opkg only uses SS_UNPACKED and SS_INSTALLED. It looks like an 
opportunity to remove some dead code (e.g. parsing of the other state_status 
fields).

Original comment by graham.g...@gmail.com on 13 Jul 2011 at 12:18

GoogleCodeExporter commented 8 years ago

Original comment by pixdamix@gmail.com on 13 Jul 2011 at 11:54