zhengzkkai / opkg

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

Forced reinstallation of a package in the repository does not update file list #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a package containing file /foo
2. Create an identically named/versioned package containing file /foo and /bar
3. Install the first package.
4. Force reinstall the second package from a repository (passing the package on 
the command line will not show the bug).

What is the expected output? What do you see instead?
The package should show that it owns both /foo and /bar. It only shows 
ownership of the file(s) that were installed initially.
$ ./opkg-cl -o /tmp/opkg files a
Package a (1) is installed on root and has the following files:
/tmp/opkg/foo

If the package is now removed, /bar will be left on the system.

Original issue reported on code.google.com by graham.g...@gmail.com on 18 Jun 2010 at 1:21

Attachments:

GoogleCodeExporter commented 9 years ago
Also a problem, is when the --force-reinstall'd package contains fewer files. 
These files are not properly orphaned/deleted.

Perhaps --force-reinstall should do a --force-depends remove, then install?

Original comment by graham.g...@gmail.com on 18 Jun 2010 at 5:38

GoogleCodeExporter commented 9 years ago
Fixed with r538.

Original comment by graham.g...@gmail.com on 22 Jun 2010 at 12:22