[Coordination] Ubuntu freecad-stable PPA update to 0.18

[NormandC]

Guys, now that the Releases/FreeCAD-0-18 branch has been created, let's talk about packaging it.

I think it should be packaged the same was as the work Kurt did for Debian, with separate python2 and python3 packages. What do you guys think? I tried it briefly when Kurt made it for his own PPA back in January and it seemed to work without issue.

There's also the matter of documentation in other languages.

In the meanwhile maybe we should ease off on freecad-daily builds... Maybe wait for master to switch to 0.19?

I'll try to help if I can.

[sgrogan]

Guys, now that the Releases/FreeCAD-0-18 branch has been created, let's talk about packaging it.

I think it should be packaged the same was as the work Kurt did for Debian, with separate python2 and python3 packages. What do you guys think? I tried it briefly when Kurt made it for his own PPA back in January and it seemed to work without issue.

14.04 and 16.04 are still QT4/PY2, so I can work on releasing these once we decide what to do about the docs.

In the meanwhile maybe we should ease off on freecad-daily builds... Maybe wait for master to switch to 0.19?

master is already 1 commit ahead of 0.18, but hasn't switched to 0.19 yet. If this commit was backported, I would build the daily against master and the latest daily would = 0.18 release. This would buy time for the rest of the work.

I'll try to help if I can.

We will need it, Thanks

[NormandC]

14.04 and 16.04 are still QT4/PY2, so I can work on releasing these once we decide what to do about the docs.

I forgot, yeah, I guess 14.04 and 16.04 will have to remain Qt4/Py2 (14.04 reaches EOL next month anyway, as you wrote in another topic).

I think we should look at removing the freecad-doc package from the freecad packaging and use Kurt's work on Debian, if that's not too much work. Knowing we'll almost certainly have to make a few iterations of the package (we always do), this will save a lot of bandwidth. I wonder if that would mean duplicating the work Yorik just did to extract the wiki into html (probably, since he didn't generate the fr/it pages). We should have a discussion about making this method the "official" one starting with 0.19... If not on salsa.debian.org, then on Github under the FreeCAD project.

master is already 1 commit ahead of 0.18, but hasn't switched to 0.19 yet. If this commit was backported, I would build the daily against master and the latest daily would = 0.18 release. This would buy time for the rest of the work.

Unless Kurt says there are big hurdles preventing this, how about this:

1. Build a last freecad-daily-018 package - maybe change the beta label to RC (release candidate)?
2. Build freecad-doc-en/fr/it packages separately (Kurt's Debian method)
3. Build Ubuntu 14.04/16.04 freecad-stable Qt4/Py2 packages without doc
4. Build Ubuntu 18.04/18.10 freecad-stable Qt5/Py2-Py3 packages using Kurt's Debian method

[kkremitzki]

One limitation to keep in mind with my doc packages is that the total size for the source package and 3 language packs is about 1.2 GB (300 MB x4). So if we have a copy for 14.04/16.04/18.04/18.10 that'll be 4.8 GB. The daily and stable PPAs have 5.0 and 6.1 GB left respectively.

Edit: Though, we'll be at -300 MB for each of the 4 versions when we drop the freecad-doc and freecad-daily-doc packages from freecad and freecad-daily proper. So only +3.6 GB, which should be fine.

[NormandC]

I guess there's no way to make a single package available to all Ubuntu versions?

[Jee-Bee]

can somebody explain about "16.04 is still py2/Qt4" py3 is in there just in apt.

https://packages.ubuntu.com/xenial/python/python3

[kkremitzki]

can somebody explain about "16.04 is still py2/Qt4" py3 is in there just in apt.

https://packages.ubuntu.com/xenial/python/python3

The problem is that https://packages.ubuntu.com/xenial/python/qt5-default is too old a version of Qt5 to get PySide2 to work, so without PySide2 we won't have Python 3 support.

[sgrogan]

Build a last freecad-daily-018 package - maybe change the beta label to RC (release candidate)?

So I just update the changelog https://git.launchpad.net/~freecad-main ... build-occt
Then trigger builds using the releases/FreeCAD-0-18 in the recipe?

[NormandC]

Yes, that's what I meant.

[sgrogan]

Yes, that's what I meant.

RC < beta, rc > beta

ping

I can't edit the qt5 recipe for the 18.04 and 18.10 builds?