Great--I got to my desktop about an hour ago and fired off a test build with the change. It looks good so far so I'm presuming it'll resolve the issue. I've sent an email off to the Debian people I'm working with to hopefully re-upload with the fix.NormandC wrote: ↑Sat Mar 31, 2018 7:22 pm Thanks Kurt.
Edit: pushed change to https://code.launchpad.net/~freecad-mai ... ef/occt7.2
FYI I installed the opencascade-7.2.0 packages from my PPA. As expected, they automatically removed the old libopencascade-7.1.0 packages as well as freecad-daily so conflicting packages are not an issue. So I think with your fix, we should be good to go. Unless there is still an issue building on bionic (18.04).
OpenCASCADE Packaging
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
- kkremitzki
- Veteran
- Posts: 2515
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: OpenCASCADE Packaging
Re: OpenCASCADE Packaging
I launched a trusty (14.04) build on my own PPA with an updated recipe (version bumped to 7.2.0-0ppa2): https://code.launchpad.net/~gemnoc/+rec ... aging-test
We'll know if it works in an hour; if it does, I'll copy the packages to the OCCT Releases PPA.
I would still like to understand why using {debversion} in the recipe does not work.
We'll know if it works in an hour; if it does, I'll copy the packages to the OCCT Releases PPA.
I would still like to understand why using {debversion} in the recipe does not work.
Re: OpenCASCADE Packaging
WTF... the trusty 32-Bit build succeeded, but not the 64-Bit one!
https://code.launchpad.net/~gemnoc/+rec ... aging-test
Now what?
https://code.launchpad.net/~gemnoc/+rec ... aging-test
Now what?
- kkremitzki
- Veteran
- Posts: 2515
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: OpenCASCADE Packaging
Ah, it's for a different reason now (dh_doxygen being missing) which should be included with the doxygen package... loading up a 14.04 VM now to take a look.NormandC wrote: ↑Sat Mar 31, 2018 10:43 pm WTF... the trusty 32-Bit build succeeded, but not the 64-Bit one!
https://code.launchpad.net/~gemnoc/+rec ... aging-test
Now what?
Re: OpenCASCADE Packaging
It's supposed to be there in the amd64 package.
https://packages.ubuntu.com/trusty/amd6 ... n/filelist
https://packages.ubuntu.com/trusty/amd6 ... n/filelist
- kkremitzki
- Veteran
- Posts: 2515
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: OpenCASCADE Packaging
Ah, it looks like https://git.launchpad.net/~freecad-main ... an/control needs to be updated. Here's the one from Debian: https://salsa.debian.org/kkremitzki-gue ... an/controlNormandC wrote: ↑Sat Mar 31, 2018 10:55 pm It's supposed to be there in the amd64 package.
https://packages.ubuntu.com/trusty/amd6 ... n/filelist
In particular you need the Build-Depends-Indep: doxygen,
graphviz
Re: OpenCASCADE Packaging
You're not looking at the right branch. This is the new one:
https://git.launchpad.net/~freecad-main ... ?h=occt7.2
But it worked for i386, why didn't it for amd64?!?
https://git.launchpad.net/~freecad-main ... ?h=occt7.2
But it worked for i386, why didn't it for amd64?!?
Re: OpenCASCADE Packaging
I see you made quite a few changes in your repo... I'll have to review them and port them to the OCCT7-packaging branch...
- kkremitzki
- Veteran
- Posts: 2515
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: OpenCASCADE Packaging
Ah, I see.. hmm.. not sure then. My gut reaction is to figure that it may be a bug which could be resolved by moving graphviz up to Build-Depends from Build-Depends-Indep, but that's just a guess. Hopefully it's resolved just by you pulling in my latest updates, but if not, I'll have a fresh 14.04 VM to test in.NormandC wrote: ↑Sat Mar 31, 2018 11:04 pm You're not looking at the right branch. This is the new one:
https://git.launchpad.net/~freecad-main ... ?h=occt7.2
But it worked for i386, why didn't it for amd64?!?
- kkremitzki
- Veteran
- Posts: 2515
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: OpenCASCADE Packaging
Well, the build in my 14.04 VM succeeded, so it's still quite strange...