What version of the product are you using? On what operating system? latest 0.2.x Please provide any additional information below. Sometimes I find two section for the same package in the /usr/lib/opkg/info file. The two sections describe the package in different versions. The newer Version has as status a "unknown user installed", the older package a "install user not-installed" This double sections results in some Warnings on a opkg upgrade like: "Not selecting kernel 3.16.1.86 as installing it would break existing dependencies." The double section is not the kernel section, but the section of a package that depends the kernel. What is the reason for this double section and how can I prevent this? Originally reported by muusclaus, Aug 22, 2014 ----------------------------------------------------------------------------- #1 paul.betafive (Aug 25, 2014) The older package probably shouldn't be marked as "install" as that indicates that state_want = SW_INSTALL and that opkg wants to install that pacakge. I think it should be "unknown" or possibly "deinstall". I'll look into how state_want is set during a package upgrade after the v0.2.3 release unless this is a regression against previous behaviour in the v0.2.x series.
from andreas.schultz@gmail.com on 11/03/2015 I can confirm that this problem still occurs with opkg 0.3. There seems to be no way to resolve it (except for manual editing the status file). Here is an example from an affected installation: # opkg list-upgradable Not selecting shadow-securetty 4.2.1 as installing it would break existing dependencies. # opkg -V4 upgrade shadow-securetty | grep shadow-securetty ... pkg_breaks_reverse_dep: Installing shadow-securetty 4.2.1 would break reverse dependency from shadow-securetty-dev. Not selecting shadow-securetty 4.2.1 as installing it would break existing dependencies. ... # opkg status shadow-securetty-dev Package: shadow-securetty-dev Version: 4.2.1-r3.5 Depends: shadow-securetty (= 4.2.1-r3.5) Status: install user installed Architecture: lanner_fw8758 Installed-Time: 1446482508 # opkg status shadow-securetty Package: shadow-securetty Version: 4.2.1-r3.5 Status: install ok installed Architecture: lanner_fw8758 Installed-Time: 1446481775 # grep -A5 "Package: shadow-securetty" /var/lib/opkg/status Package: shadow-securetty Version: 4.2.1-r3.5 Status: install ok installed Architecture: lanner_fw8758 Installed-Time: 1446481775 Auto-Installed: yes -- Package: shadow-securetty Version: 4.2.1-r3.2 Status: install ok not-installed Architecture: lanner_fw8758 Installed-Time: 1438343802 Auto-Installed: yes -- Package: shadow-securetty-dev Version: 4.2.1-r3.5 Depends: shadow-securetty (= 4.2.1-r3.5) Status: install user installed Architecture: lanner_fw8758 Installed-Time: 1446482508
Wasn't able to reproduce on 0.3.2. Will take another look at this during the 0.3.3 timeframe.
Hi Is the problem resolved..? I am facing the same problem and i am in big trouble. can anyone put some light into this..? Thanks and Regards Jatin
I have this issue, too. I was able to resolve it manually by deleting the duplicated entry to the myapp-dev package in /var/lib/opkg/status.
Christian, Jaitin: it would help me a whole lot if you could come up with a reproducible case with the latest opkg. I haven't seen this problem, so its pretty hard for me to figure out what's going....
fixed on 6ace897319009bdc367f06b645c465daa9f998c9