Skip to content

Conversation

mcjaeger
Copy link
Member

@mcjaeger mcjaeger commented Feb 26, 2017

updating the debian packaging scripts from [email protected] to
support recent changes (agents) of the fossology code base. updated
readme text still missing, the existing one is still from 2008.

Usage (one possibility):

  • go into project root dir
  • vagrant up (will use a trusty64 box by default)
  • vagrant ssh
  • cd /vagrant
  • sudo dpkg-buildpackage -I
  • see that some dependencies are missing
  • sudo apt-get install debhelper postgresql-server-dev-all libjson0-dev
  • sudo dpkg-buildpackage -I
    collect the packages (unfortunately at root dir) and test with a trusty64 installation

…logy

updating the debian packaging scripts from [email protected] to
support  recent changes (agents) of the fossology code base. proper
readme text still missing.
@maxhbr
Copy link
Member

maxhbr commented Feb 28, 2017

I have tried this but have still problems The problem was caused by #701 and is not related to this PR. It will be fixed by something like #738

@mcjaeger
Copy link
Member Author

super strange, the vagrant environments should be the same for every one, but the error must be in the differences between the locally shared (project) folders. I will try to do this with clean checkout on a vanilla virtual machine and then report.

@maxhbr
Copy link
Member

maxhbr commented Feb 28, 2017

I will also have a look. Maybe merge #738 first?

@mcjaeger
Copy link
Member Author

mcjaeger commented Feb 28, 2017

I retested it with a clean checkout (=no clutter from potentially uncommitted files) and it works as expected for me.

I was also wondering: how did executing the vagrant machine script actually work and installing the fossology from (the shared vagrant folder containing the) source, if the composer is not installed, or if the composer installation does not work? - that should fail in your case, regardless if you want to trigger the package build?

May it be that you were trying the vagrant file from pbconf (which is currently centos7 based) while I was just working on the plain vagrant file we have in the project root folder?

Actually the vagrant file in pbconf is for project builder (see the script in side) while the vagrant file in project root is just a plain way to install fossology from source, which was all I needed to execute the debhelper based backage build.

attached the complete dump of this run, to see where I am doing what, switching to the virtual machine in line 23282.

fossology-debian-package-build-log.txt

@maxhbr
Copy link
Member

maxhbr commented Mar 1, 2017

I have also retested. The problem was caused by #701 and does not appear if one do not restart.

Installation also works well.

@mcjaeger mcjaeger merged commit 84f686c into master Mar 2, 2017
@mcjaeger mcjaeger deleted the dev/debianpackages branch April 18, 2017 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants