search

leosac / access-control

Leosac Access Control - Open Source Physical Access Control System
https://leosac.com
GNU Affero General Public License v3.0
242 stars 40 forks source link

Update Debian Packaging to build develop #103

Closed knight-of-ni closed 6 years ago

knight-of-ni commented 6 years ago

These changes allow the deb.sh script to build the latest develop branch, or another leosac branch or fork.

Documentation is included, but I do not know how to preview my additions. I expect further changes to be required, once I can see the page rendered to html.

TO-DO: Add custom built odb packages to the Leosac bin-resources repo. I'll have a separate pr for that once I've got the packages ready.

xaqq commented 6 years ago

Hey, thank you for the pr.

It tested it but for now it still fails, probably because I haven't updated the changelog debian file, so it tries to find a leosac_0.6.3.orig.tar.gz file instead of 0.7.0

If you want to generate the doc you can use leosaccli dev doc build the output is in doc/output/html.

knight-of-ni commented 6 years ago

Yeah, you're right. I neglected to bump the package revision. I'll take a look at it and send another pr.

xaqq commented 6 years ago

I updated changelog and with non-debian repo odb package it went a long way but did not finish.

knight-of-ni commented 6 years ago

I ran into linker issues in one case when I used a custom built odb package, combined with the other libodb packages from the Debian repo. To resolve that, I rebuilt all the odb packeges (11 in total) and then ran the build again. It succeeded after I did that.

In addition, the odb packages depend on major version of gcc they are built against. Found out the hard way that you can't use gcc 7 and an odb that was built against gcc 6.

What I'm working on right now are four complete sets of odb packages: 1) amd64 w/ gcc6 2) amd64 w/ gcc7 3) armhf w/ gcc6 4) armhf w/ gcc7

The first three are done, and I'm watching my pi build #4 right now. Once that completes, I'll push these to the bin-resources repo.

I'm not sure what failed in your build, but if it is a linker problem then perhaps the above will help.

In any case, I will return to testing the deb.sh script and fix anything that isn't working once I'm done building all these deb packages. Should be in the next day or two.

knight-of-ni commented 6 years ago

Ok, the deb.sh script builds now after I merge #106 to my fork. Let me know if that works for you as well.