Opened 22 months ago

Last modified 22 months ago

#13574 new bug

[package_daemon] activate packages after replace

Reported by: diver Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Servers/package_daemon Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no 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 (5)

comment:1 Changed 22 months ago by waddlesplash

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.

comment:2 Changed 22 months ago by luroh

Yes, that's what diver wrote. This new behavior does not strike me as intuitive.

comment:3 Changed 22 months ago by throttle10

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.

Yes, name is the same. i'm trying to fix it by adding reactivating possibility to package_daemon. Packagefs already supports it.

Last edited 22 months ago by throttle10 (previous) (diff)

comment:4 Changed 22 months ago by axeld

What is the point of doing that? Just to repeatedly test a package you build yourself? What am I missing here? :-)

comment:5 Changed 22 months ago by diver

The original point is exactly that :-) But there might be other use cases, who knows?

Note: See TracTickets for help on using tickets.