NormandC wrote: ↑Fri Oct 28, 2022 3:36 am
In the past few days I had a look around the Launchpad and Salsa infrastructure, and my feeling is that the situation isn't as dire as everybody seems to think. I may be overly optimistic, but the whole thing may not require much effort to put it back on track.
I was going to list what I perceived were the next steps, but I just noticed that Kurt actually produced builds on the freecad-stable PPA 10 hours ago, including for Ubuntu 22.04.
Indeed, hopefully not. Quick summary of what I did:
- The Launchpad recipe for the stable builds currently targets the `ppa/py3only` branch, so I had to `git merge master` into that branch and fix a few merge conflicts
- Once that was done, next step was to test those builds on the targeted Ubuntu versions. I used LXD containers, but e.g. Docker would work fine here too. The general process is to push the packaging repo over, `apt install devscripts equivs`, `mk-build-deps && sudo apt install ./*.deb` to get dependencies, then `dpkg-buildpackage -us -uc` to attempt a build.
- After testing, I noticed that for Ubuntu 18.04/20.04, the build dependency on libvtk9-dev had to be reverted to libvtk7-dev, and for some reason, the PYTHON_INCLUDE_DIR had to be specified. Those quirks are now handled in a separate `ppa/py3only-vtk7` branch, with a new `freecad-stable-vtk7` Launchpad recipe to handle it.
- With those changes tested, I pushed the branches to Salsa. In the Launchpad recipes, you can see there's a repo `lp:freecad`, which mirrors the repo on Salsa every 4 hours. There's also a button for triggering an import immediately, so I did that and then started the builds
Next steps:
- Updating the Daily PPA (another process of merging master into a branch and fixing the merge commits)
- Updating the PPA's version of OpenCASCADE
- Updating other packaged dependencies in the PPAs
- Backporting VTK9 to the PPA to get rid of the quirk for Ubuntu 18.04/20.04