#2653 closed defect (worksforme)
xpra upgrade :0 looks like a bad idea
Reported by: | stdedos | Owned by: | stdedos |
---|---|---|---|
Priority: | minor | Milestone: | 4.0 |
Component: | server | Version: | 3.0.x |
Keywords: | Cc: |
Description
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?
Change History (7)
comment:1 Changed 10 months ago by
Owner: | changed from Antoine Martin to stdedos |
---|
comment:3 Changed 10 months ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:4 Changed 10 months ago by
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
comment:5 follow-up: 6 Changed 10 months ago by
There are no new xpra builds to test against.
There are Xenial and win32 builds fresh from today.
comment:6 Changed 10 months ago by
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)
comment:7 Changed 10 months ago by
Somehow you broke the xpra repo. These files give:
/etc/apt/bak-sources# bat * ───────┬──────────────────────────────────────── │ File: xpra.list ───────┼──────────────────────────────────────── 1 │ deb https://xpra.org/ xenial main 2 │ deb https://xpra.org/beta/ xenial main ───────┴──────────────────────────────────────── ───────┬──────────────────────────────────────── │ File: xpra.list.save ───────┼──────────────────────────────────────── 1 │ deb https://xpra.org/ xenial main 2 │ deb https://xpra.org/beta/ xenial main ───────┴────────────────────────────────────────
# aug Hit:1 http://fi.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://fi.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://fi.archive.ubuntu.com/ubuntu xenial-backports InRelease Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease Hit:5 http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu xenial InRelease Get:6 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB] Hit:7 http://dl.google.com/linux/chrome/deb stable Release Hit:8 http://archive.canonical.com/ubuntu xenial InRelease Get:9 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB] Hit:10 http://ppa.launchpad.net/beineri/opt-qt-5.14.1-xenial/ubuntu xenial InRelease Ign:11 https://dl.bintray.com/getinsomnia/Insomnia InRelease Hit:12 http://ppa.launchpad.net/csaba-kertesz/random/ubuntu xenial InRelease Get:13 https://dl.bintray.com/getinsomnia/Insomnia Release [815 B] Hit:13 https://dl.bintray.com/getinsomnia/Insomnia Release Hit:14 https://private-ppa.launchpad.net/awyr/ffmpeg-4/ubuntu xenial InRelease Hit:15 http://ppa.launchpad.net/dawidd0811/neofetch/ubuntu xenial InRelease Hit:16 https://xpra.org xenial InRelease Hit:19 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu xenial InRelease Get:18 https://xpra.org/beta xenial InRelease [4197 B] Hit:20 http://pub.freerdp.com/repositories/deb/xenial freerdp-nightly InRelease Hit:21 http://ppa.launchpad.net/dlech/keepass2-plugins/ubuntu xenial InRelease Hit:22 http://ppa.launchpad.net/fkrull/speedcrunch-daily/ubuntu xenial InRelease Hit:23 http://ppa.launchpad.net/git-core/ppa/ubuntu xenial InRelease Hit:24 http://ppa.launchpad.net/jonathonf/meson/ubuntu xenial InRelease Hit:26 http://ppa.launchpad.net/jonathonf/vlc-3/ubuntu xenial InRelease Hit:27 http://ppa.launchpad.net/jtaylor/keepass/ubuntu xenial InRelease Hit:28 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease Reading package lists... Done E: Unable to parse package file (1)
This E: Unable to parse package file (1)
has two spaces intentionally: between file (1)
there should be the filename that's unparseable (Google it for example "full" messages).
Do you want a new issue with these, or can you look into it now?
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 asupgrade-desktop
), or even better: a genericupgrade
command which would figure out what it is upgrading automatically. (but it's not as easy as it sounds)