xpra upgrade :0 looks like a bad idea

[stdedos]

I updated /etc/xpra/conf.d/80_lock.conf configuration file, and I was thinking how could I quickly update the server without stop/shadow.

Without much thinking I did xpra upgrade :0.

Now theming is different, fonts are different and applications have duplicated "File" menus (one in the normal Unity toolbar, one just when their drawing area starts).

Maybe I shouldn't be able to do that? Or you do it internally like a stop/shadow instead?

[Antoine Martin]

Maybe I shouldn't be able to do that?

Correct, that's a bug, fixed in r25673. (backport in r25674)

For upgrading shadow servers, you are meant to stop it and start a new one, shadow servers aren't meant to linger around, they are usually started with --exit-with-client=yes.

Ideally, we would have an upgrade-shadow subcommand (same as upgrade-desktop), or even better: a generic upgrade command which would figure out what it is upgrading automatically. (but it's not as easy as it sounds)

[Antoine Martin]

This caused a regression, details in r25677.

[stdedos]

There are no new xpra builds to test against.

I understand you are going in release and you are cleaning up the tracker, but at least for some tickets there could be some grace period

[Antoine Martin]

There are no new xpra builds to test against.

There are Xenial and win32 builds fresh from today.

[stdedos]

Replying to Antoine Martin:

There are no new xpra builds to test against.

There are Xenial and win32 builds fresh from today.

I trust you, and I've seen the changeset, but apt-get does not want to pick them up for some reason (apt-cache madison also agrees)

[stdedos]

Somehow you broke the xpra repo...
Edit: moved to #2663.

[migration script]

this ticket has been moved to: ​https://github.com/Xpra-org/xpra/issues/2653