Bug 8348 - opkg removes package provider on upgrade (old issue #121)
Summary: opkg removes package provider on upgrade (old issue #121)
Status: RESOLVED FIXED
Alias: None
Product: opkg
Classification: Yocto Project Subprojects
Component: opkg (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 0.4.0
Assignee: Alejandro del Castillo
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-09-21 00:56 UTC by Alejandro del Castillo
Modified: 2016-05-05 16:17 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 Alejandro del Castillo 2015-09-21 00:56:26 UTC
What steps will reproduce the problem?
1. Install package "A" version 2.0 that also provides "B".
2. Create package "B" v1.0 in repository.
3. Create package "A" to v2.1 in repository that no longer provides "B".
4. Do upgrade.

What is the expected output?
Packages "A" v2.1 and "B" v1.0 are installed.

What do you see instead?
Only package "A" v2.1 is installed. Thus provider of "B" is missing.

Originally reported by KirGeNe, Feb 6, 2014
-----------------------------------------------------------------------------

#1 paul.betafive (Feb 6, 2014)
I don't see how opkg can know when you install A that you need a provider of B. Does any other package manager (eg. rpm, dpkg) do what you're saying?

#2 KirGeNe (Feb 7, 2014)
Oh, I forgot to mention that other packages depends on "B".

#3 paul.betafive (Feb 7, 2014)
So is A being explicitly installed or is it being brought in just to provide B? Do any other packages have a direct dependency on A?

I'm trying to get this clear enough that we can write a minimal test case.

#4 KirGeNe (Feb 7, 2014)
OK, so there are many packages that depends on A and B from start.
Package A v2.0 is installed from start to provide A and B.

Later separate package B v1.0 is created.
Also updated package A v2.1 is created to provide only A (without B). Also for package A new dependency on B is created.

After that update process is started.
After upgrade package A will be upgraded but B won't be installed.
During this process I see following messages:
"Multiple replacers for B, using first one (A)."

#5 paul.betafive (Feb 16, 2014)
So, there are 2 problems which lead to this:

1) The function pkg_installed_and_constraint_satisfied() doesn't check pkg->state_want. When pkg->state_want == SW_DEINSTALL, the package is scheduled for uninstall and so shouldn't be treated as installed. This is easy to fix.

2) For an abstract_pkg, provided_by is a list of abstract packages, not a list of real packages. An abstract package is just a name with no version number. So if A 1.0 provides B, A is added to B->provided_by. There is no current mechanism to say that a particular version of A provides B but a different version of A doesn't provide B. This may be more difficult to fix.

I've added "tests/regress/issue121.py" to master which checks this behaviour. It is currently expected to fail on the last check. If you could take a quick look at that and ensure it checks what you expect it to that'd be helpful.

I've listed this as Milestone-0.4 as it may be a complicated fix and it seems like a rare corner case. I may be wrong though so if you disagree please say so.

The only thing I can't reproduce is the message "Multiple replacers for B, using first one (A).". Are any of your packages listed as
Comment 1 Alejandro del Castillo 2016-05-05 16:17:20 UTC
Test passes since v0.3.0.