xpra icon
Bug tracker and wiki

Opened 5 weeks ago

Closed 5 weeks ago

Last modified 5 weeks ago

#2389 closed defect (fixed)

beta repository: updates fail because of wrong versioning

Reported by: mviereck Owned by: Antoine Martin
Priority: major Milestone: 3.0
Component: packaging Version: 3.0.x
Keywords: Cc:

Description

In the winswitch beta repository for debian xpra versions r23061 and r23066 have a different name scheme than the other version packages.
This prevents apt from installing the real latest version.

I've been stuck with r23066 since weeks because apt/debian believes it to be the latest version.

I was wondering why I did not get an xpra update for a long time until I had a look at http://winswitch.org/beta/buster/main/binary-amd64/ today.
Manually choosing and installing r23522 worked. However, my next system update will install r23066 again.

Change History (9)

comment:1 Changed 5 weeks ago by Antoine Martin

Resolution: fixed
Status: newclosed

Ah, right, those were built as release versions but landed on the beta channel by mistake.
I've just deleted them and re-created the repo data, this should do it.
Though you may have to remove the version you have installed and then apt-get update

comment:2 Changed 5 weeks ago by mviereck

I've just deleted them and re-created the repo data, this should do it.

Thanks! xpra-python2 and xpra-python3 packages are fixed now.
Still wrong:
xpra-html5
xpra_3.0 (at end of http://winswitch.org/beta/buster/main/binary-amd64/)

comment:3 Changed 5 weeks ago by Antoine Martin

Still wrong:

Oops, sorry for the sloppy job, did that in a rush.
Should be OK now.

comment:4 Changed 5 weeks ago by mviereck

Still a bit left:
python2-xpra-dbgsym
python3-xpra-dbgsym
:-)

comment:5 Changed 5 weeks ago by Antoine Martin

Whoops, forgot about those. Done. Thanks!

comment:6 Changed 5 weeks ago by Mark Harkin

Can I hijack this ticket and request a similar fix for CentOS on the beta repo...

Resolving Dependencies
--> Running transaction check
---> Package xpra.x86_64 0:3.0-0.20190706r23103.el7_6 will be installed
--> Processing Dependency: xpra-common = 3.0-0.20190706r23103.el7_6 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
--> Processing Dependency: python3-xpra-server = 3.0-0.20190706r23103.el7_6 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
--> Processing Dependency: python3-xpra-client = 3.0-0.20190706r23103.el7_6 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
--> Processing Dependency: xpra-html5 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
--> Running transaction check
---> Package xpra.x86_64 0:3.0-0.20190706r23103.el7_6 will be installed
--> Processing Dependency: python3-xpra-server = 3.0-0.20190706r23103.el7_6 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
--> Processing Dependency: python3-xpra-client = 3.0-0.20190706r23103.el7_6 for package: xpra-3.0-0.20190706r23103.el7_6.x86_64
---> Package xpra-common.noarch 0:3.0-0.20190706r23103.el7_6 will be installed
---> Package xpra-html5.noarch 0:3.0-0.20190706r23103.el7_6 will be installed
--> Finished Dependency Resolution
Error: Package: xpra-3.0-0.20190706r23103.el7_6.x86_64 (winswitch-beta)
           Requires: python3-xpra-client = 3.0-0.20190706r23103.el7_6
Error: Package: xpra-3.0-0.20190706r23103.el7_6.x86_64 (winswitch-beta)
           Requires: python3-xpra-server = 3.0-0.20190706r23103.el7_6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

comment:7 Changed 5 weeks ago by Antoine Martin

Can I hijack this ticket and request a similar fix for CentOS on the beta repo...

That's odd, the packages are there. Maybe createrepo failed or something.
I've uploaded some new packages and I will try CentOS 7.x soon.

comment:8 Changed 5 weeks ago by Antoine Martin

Damn, that had been broken for a while too. Thanks for reporting that.
Fixed in r23547. There are new beta packages for centos7.

comment:9 in reply to:  8 Changed 5 weeks ago by Mark Harkin

Great, thanks, it's working now.

Damn, that had been broken for a while too. Thanks for reporting that.

I'm working mainly with a custom build so not using the beta repo so often.

Note: See TracTickets for help on using tickets.