[package_daemon] activate packages after replace

[diver]

Patch from #10038 fixed the issue however now replacing a package (with the same name) doesn't activate the new one.

[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.

[luroh]

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

[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.

[axeld]

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

[diver]

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

[waddlesplash]

Now that the causes are better understood, #15068 is a dupe of this, but that one has more details.

[nielx]

Remove milestone for tickets with status = closed and resolution != fixed