#13574 closed bug (duplicate)
[package_daemon] activate packages after replace
| Reported by: | diver | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Servers/package_daemon | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | #15068 | Blocking: | |
| Platform: | All |
Description
Patch from #10038 fixed the issue however now replacing a package (with the same name) doesn't activate the new one.
Change History (7)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Yes, that's what diver wrote. This new behavior does not strike me as intuitive.
comment:3 by , 7 years ago
i'm trying to fix it by adding reactivating possibility to package_daemon. Packagefs already supports it.
Version 0, edited 7 years ago by (next)
comment:4 by , 7 years ago
What is the point of doing that? Just to repeatedly test a package you build yourself? What am I missing here? :-)
comment:5 by , 7 years ago
The original point is exactly that :-) But there might be other use cases, who knows?
comment:6 by , 5 years ago
| Blocked By: | 15068 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Now that the causes are better understood, #15068 is a dupe of this, but that one has more details.
comment:7 by , 4 years ago
| Milestone: | Unscheduled |
|---|
Remove milestone for tickets with status = closed and resolution != fixed
Note:
See TracTickets
for help on using tickets.
Huh? Unless I missed something, that should only happen if you replace a package with the *exact* same name, i.e. the version+revision is the same. If the package has a newer revision, it should get activated.