Bug 11033 - opkg does not treat symlink/directory conflicts as an error
Summary: opkg does not treat symlink/directory conflicts as an error
Status: RESOLVED FIXED
Alias: None
Product: opkg
Classification: Yocto Project Subprojects
Component: opkg (show other bugs)
Version: 0.3.4
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Alejandro del Castillo
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-02-08 21:32 UTC by Michael Hansen
Modified: 2017-02-24 21:02 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Hansen 2017-02-08 21:32:23 UTC
Given two packages:
- a, which provides a symlink at a given path (e.g. /ro/config -> ../rw/config)
- b, which installs files into the same path (e.g. /ro/config/b.conf)

opkg will allow both packages to be installed, but will not produce a "reasonable" result no matter which order they're installed in.

If a is installed before b:
- Opkg will print a warning that it can't create file /ro/config/b.conf, since /rw/config doesn't exist.  It will still proceed and return successful exit status nonetheless.

If b is installed before a:
- Opkg will silently ignore the creation of the symlink.


Expected behavior:
- Opkg should detect the conflict and disallow the two packages from being installed at the same time.
Comment 1 Alejandro del Castillo 2017-02-24 21:02:25 UTC
Fixed on f9ca21f1892d64a70c2756d28e29ef3f60a324eb