Skip to content
This repository has been archived by the owner on Feb 12, 2023. It is now read-only.

qTox version number #4112

Closed
nweyand opened this issue Jan 31, 2017 · 12 comments
Closed

qTox version number #4112

nweyand opened this issue Jan 31, 2017 · 12 comments
Labels
M-packaging Affected Module: Packaging OS-osx OS-windows

Comments

@nweyand
Copy link
Contributor

nweyand commented Jan 31, 2017

When downloading qTox from the website, the file should be named something like setup-qtox-v1.7.0 instead of only setup-qtox, as this would allow to download new versions to the same folder without overwriting the previous installer.

Also, it would allow to determine the version number of an installer at first glance, which is quite nice to have. ;)

@pascalberger
Copy link

This would also help to maintain the Chocolatey Package.

@sudden6 sudden6 added the M-packaging Affected Module: Packaging label Feb 3, 2017
@sudden6
Copy link
Member

sudden6 commented Feb 3, 2017

@tux3 do you think you can implement this? Maybe replace setup-qtox-latest with a link to the current version.

@ghost
Copy link

ghost commented Feb 6, 2017

Ditto for macOS release qTox-1.8.1.dmg with qTox-1.8.1.dmg.sig file as well.

@sudden6 sudden6 added the OS-osx label Feb 6, 2017
@Hasshu
Copy link

Hasshu commented Feb 11, 2017

By the way, how up-to-date are the recent non-Linux builds, actually?

At least under Windows, the toxcore version number seems to get updated every now and then, while qTox itself is stuck at "v1.7.0".

@DjDiabolik
Copy link

By the way because here on github it's present 1.8.1 and latest for windows it's 1.7.0 from site.....

@DjDiabolik
Copy link

Now it's setup-qtox-1.8.1.exe....... but on version inside "Info about qtox" i continue to read 1.7.0... it's normal ?

Add a feature to check upgrade directly from app........... i thinks it's a good.

@Hasshu
Copy link

Hasshu commented Feb 21, 2017

Looks like it just appends the version number of the latest release, instead of the build's actual one.

@tux3 Is that the expected behavior?

@tux3
Copy link
Member

tux3 commented Feb 21, 2017

@Hasshu Yes, and those should match. What were you expecting instead?

@Hasshu
Copy link

Hasshu commented Feb 22, 2017

@tux3 Hmm... They do match now. You see, I downloaded the "v1.8.1" installer soon after #4177 was merged, but it actually contained an older version, for some reason (see also what @DjDiabolik said above).

@tux3
Copy link
Member

tux3 commented Feb 22, 2017

@Hasshu It might have been still building on the server when you downloaded it, my apologies for announcing it a bit too soon then!

@Hasshu
Copy link

Hasshu commented Feb 23, 2017

@tux3 Ah, no worries. The proper build is up now, so it's fine.

@DjDiabolik
Copy link

I can confirm i have upgrade to 1.8.1 about one or two days ago.....

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M-packaging Affected Module: Packaging OS-osx OS-windows
Projects
None yet
Development

No branches or pull requests

7 participants