Summary: | package move over a installed package shows as an update in ~arch | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Petteri Räty (RETIRED)
2006-12-27 15:47:17 UTC
As I said on irc: [15:55] <zmedico> Betelgeuse: so, the move put 2 packages in the same slot? [15:56] <zmedico> I think the ~arch version is behaving correcly. [15:57] <zmedico> if 2 packages are in the same slot, it ignores (and cleans) the one that was installed first [16:00] <zmedico> Betelgeuse: apparently 2.0.1 was installed after 2.0.2-r1. Since they're both in the same slot, 2.0.2-r1 is effectively overwritten by 2.0.1. [16:01] <zmedico> so it appears as an upgrade, since 2.0.2-r1 has been overwritten. [16:02] <zmedico> it uses the COUNTER file to determine the order of installation. |