Xpra: Ticket #2246: missing packages from the beta repository

I was trying to fetch the updates from the beta repository today (02.04), and, to my surprise, everything was wiped clean (xenial and windows).

After (manually!) going through r22000 --> r22260, I figured out that the case is (probably) that 2.5.x was released.

Since I've read somewhere that mixing release and beta repository shouldn't really be mixed. Is it unreasonable to have the "last release" as "the first package" in the beta repository, in all possible ways?

Can you please please build the zips for the released version also?



Tue, 02 Apr 2019 13:00:27 GMT - Antoine Martin: status changed; resolution set

2.5 was released 2 weeks ago: https://xpra.org/trac/wiki/News You should subscribe to the mailing list to get the email notifications.

Since I've read somewhere that mixing release and beta repository shouldn't really be mixed.

That's not the case. The beta one is supplemental, you must have both enabled to use it.

Is it unreasonable to have the "last release" as "the first package" in the beta repository, in all possible ways?

The beta channel is for pre-releases. Use stable to get proper releases.

Can you please please build the zips for the released version also?

The ZIP builds are there in the stable repo. For the beta repo, they may be posted occasionally, it does take extra time / bandwidth.


Wed, 03 Apr 2019 12:46:54 GMT - stdedos:

Replying to Antoine Martin:

Since I've read somewhere that mixing release and beta repository is ill-advised.

That's not the case. The beta one is supplemental, you must have both enabled to use it.

So far, I've always used:

/etc/apt$ grep -TrinP 'xpra|winswitch'
sources.list.d/xpra.list.save:   1     :deb https://xpra.org/beta/ xenial main
sources.list.d/xpra.list:   1  :deb https://xpra.org/beta/ xenial main
$ sudo apt-get update && sudo apt-get upgrade
[sudo] password for user:
Hit:1 http://archive.canonical.com/ubuntu xenial InRelease
Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Hit:4 https://deb.nodesource.com/node_8.x xenial InRelease
Hit:5 http://download.virtualbox.org/virtualbox/debian xenial InRelease
Hit:6 http://ppa.launchpad.net/csaba-kertesz/random/ubuntu xenial InRelease
Get:7 https://xpra.org/beta xenial InRelease [4086 B]
Hit:8 http://ppa.launchpad.net/dawidd0811/neofetch/ubuntu xenial InRelease
Ign:9 https://dl.bintray.com/getinsomnia/Insomnia  InRelease
Get:10 https://dl.bintray.com/getinsomnia/Insomnia  Release [815 B]
Hit:10 https://dl.bintray.com/getinsomnia/Insomnia  Release
Hit:11 http://ppa.launchpad.net/dlech/keepass2-plugins/ubuntu xenial InRelease
Hit:12 https://download.sublimetext.com apt/stable/ InRelease
Get:13 https://xpra.org/beta xenial/main amd64 Packages [2151 B]
Get:14 https://xpra.org/beta xenial/main i386 Packages [2149 B]
Hit:15 http://ppa.launchpad.net/fkrull/speedcrunch-daily/ubuntu xenial InRelease
Hit:17 http://fi.archive.ubuntu.com/ubuntu xenial InRelease
Hit:18 http://linux.teamviewer.com/deb stable InRelease
Hit:19 http://ppa.launchpad.net/git-core/ppa/ubuntu xenial InRelease
Get:20 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [637 kB]
Ign:21 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:22 http://ppa.launchpad.net/jonathonf/ffmpeg-3/ubuntu xenial InRelease
Hit:23 http://ppa.launchpad.net/jonathonf/ffmpeg-4/ubuntu xenial InRelease
Hit:24 http://ppa.launchpad.net/jonathonf/meson/ubuntu xenial InRelease
Get:25 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [530 kB]
Hit:26 http://ppa.launchpad.net/jonathonf/vlc-3/ubuntu xenial InRelease
Hit:27 http://ppa.launchpad.net/jtaylor/keepass/ubuntu xenial InRelease
Get:28 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [261 kB]
Hit:29 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease
Get:30 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [433 kB]
Hit:31 http://fi.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:32 http://dl.google.com/linux/chrome/deb stable Release
Get:34 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [377 kB]
Get:35 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [175 kB]
Hit:36 http://ppa.launchpad.net/phoerious/keepassxc/ubuntu xenial InRelease
Hit:37 http://ppa.launchpad.net/slgobinath/safeeyes/ubuntu xenial InRelease
Hit:38 http://fi.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:39 http://ppa.launchpad.net/sylvain-pineau/kazam/ubuntu xenial InRelease
Ign:40 http://repo.vivaldi.com/stable/deb stable InRelease
Hit:41 http://ppa.launchpad.net/vlijm/nonotifs/ubuntu xenial InRelease
Hit:42 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Hit:43 http://ppa.launchpad.net/webupd8team/nemo3/ubuntu xenial InRelease
Hit:44 http://ppa.launchpad.net/wireshark-dev/stable/ubuntu xenial InRelease
Hit:45 http://repo.vivaldi.com/stable/deb stable Release
Fetched 2637 kB in 3s (702 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  busybox-initramfs busybox-static libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 policykit-1
9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 5408 kB of archives.
After this operation, 91,1 kB of additional disk space will be used.
Do you want to continue? [Y/n]

you must have both enabled to use it

So, I don't understand this

Is it unreasonable to have the "last release" as "the first package" in the beta repository, in all possible ways?

The beta channel is for pre-releases. Use stable to get proper releases.

What if I want to always be on the bleeding edge, be it "beta" or "stable"? I understand they are "beta"s, but, a lot developers/maintainers are building "mature betas" in some sense (I am not sure what to call them? Release Candidates? -- probably too much. Something worse than "stable", but "better enough" than a beta/alpha/canary/dev release). I've seen here so far that this is the case too, so, I feel comfortable with basically whatever you upload.

Can you please please build the zips for the released version also?

The ZIP builds are there in the stable repo. For the beta repo, they may be posted occasionally, it does take extra time / bandwidth.

Apologies for pushing :/. I have only recently discovered how easy it is to switch between versions using the zip-files, so, now I am in love with them :-D.


Wed, 03 Apr 2019 13:44:52 GMT - Antoine Martin:

you must have both enabled to use it

So, I don't understand this

You need to have both deb https://xpra.org/ xenial main and deb https://xpra.org/beta/ xenial main enabled. As per wiki/Download: the beta repositories are supplemental ones so you must also configure the stable repository to use them

a lot developers/maintainers are building "mature betas" in some sense

That's what the beta channel is meant to be. It is not a daily build, the buildbot is only scheduled whenever there are enough new features and hopefully not too much breakage.

I have only recently discovered how easy it is to switch between versions using the zip-files, so, now I am in love with them

I'll try to remember to post more of them.


Sat, 23 Jan 2021 05:46:05 GMT - migration script:

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