Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Issue to create a binary package .deb #144

Open
ghost opened this Issue · 5 comments

4 participants

HughWilliams OpenLink Software Nolan Nichols Patrick van Kleef
Deleted user

Hi,

I tried to create a ".deb" binary package of the develop/7 git branch and I have these errors :

parsechangelog/debian: avertissement: debian/changelog(l5): début d'une entrée trouvé, more change data or trailer attendu
LINE: virtuoso-opensource (6.1.7) unstable; urgency=low
parsechangelog/debian: avertissement: debian/changelog(l5): fin de fichier trouvée, more change data or trailer attendu
dpkg-buildpackage: paquet source virtuoso-opensource
dpkg-buildpackage: version source 7.0.1
dpkg-buildpackage: erreur: impossible de déterminer source changé par

The package creation process is up to date for the last 7.1 version ? I'm on Ubuntu 13.10.

Thanks in advance.

HughWilliams
Collaborator

Development are checking this, Have you tried building against the Ubtuntu 12.04 LTS version as that is the last version we have successfully built against ?

Deleted user

There is an issue on 12.04, the libreadline5 is not found Still for ".deb" creation step. And the package libreadline5-dev doesn't exists anymore in 12.04 repositories.

OpenLink Software
Owner

i put some patches into develop/7 that should resolve this issue.

Patrick van Kleef pkleef was assigned by openlink
Deleted user

I have another error with the new bugfix :

$ dpkg-buildpackage -us -uc
dpkg-buildpackage: paquet source virtuoso-opensource
dpkg-buildpackage: version source 7.1
dpkg-buildpackage: source changé par OpenLink Virtuoso Maintainer <vos.admin@openlinksw.com>
dpkg-buildpackage: architecture hôte amd64
 dpkg-source --before-build virtuoso-perso
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
# Add here commands to clean up after the build process.
[ ! -f Makefile ] || /usr/bin/make distclean
make[1]: entrant dans le répertoire « /home/julien-plu/virtuoso-perso »
Making distclean in .
make[2]: entrant dans le répertoire « /home/julien-plu/virtuoso-perso »
rm -rf .libs _libs
rm -f *.lo
test -z "" || rm -f
test . = "." || test -z "" || rm -f
rm -f libtool config.lt
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -f cscope.out cscope.in.out cscope.po.out cscope.files
make[2]: quittant le répertoire « /home/julien-plu/virtuoso-perso »
Making distclean in docsrc
make[2]: entrant dans le répertoire « /home/julien-plu/virtuoso-perso/docsrc »
make[2]: *** Pas de règle pour fabriquer la cible « distclean ». Arrêt.
make[2]: quittant le répertoire « /home/julien-plu/virtuoso-perso/docsrc »
make[1]: *** [distclean-recursive] Erreur 1
make[1]: quittant le répertoire « /home/julien-plu/virtuoso-perso »
make: *** [clean] Erreur 2
dpkg-buildpackage: erreur: fakeroot debian/rules clean a produit une erreur de sortie de type 2

The error says "No rule to create distclean target" inside the "docsrc" folder.

Nolan Nichols

FYI... Gave this a shot on a vanilla precise64 vagrant box and seems to work fine.

vagrant@precise64:~/virtuoso$ sudo apt-get install git
vagrant@precise64:~/virtuoso$ git clone https://github.com/openlink/virtuoso-opensource.git
vagrant@precise64:~/virtuoso$ cd virtuoso-opensource/
vagrant@precise64:~/virtuoso$ sudo apt-get install build-essential
vagrant@precise64:~/virtuoso$ sudo apt-get install debhelper autotools-dev autoconf automake libtool flex bison gperf gawk m4
vagrant@precise64:~/virtuoso$ dpkg-buildpackage -us -uc
vagrant@precise64:~/virtuoso$ cd ..
vagrant@precise64:~/virtuoso$ sudo dpkg -i virtuoso-opensource_7.1_amd64.deb
vagrant@precise64:~/virtuoso$ ps aux | grep virtuoso
root     10868  3.0 80.4 1505972 301096 ?      Ssl  22:27   0:08 /usr/bin/virtuoso-t -c virtuoso +wait

@yarikoptic, not sure if this helps the situation of getting virtuoso-opensource-7.1 into the next debian release re: https://lists.debian.org/debian-qt-kde/2014/06/msg00199.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.