hi folks, I'm new to: koha, this community and the debian-build process I'm familiar with: linux (archlinux), software development I'm struggling while building the koha package. And get the following errors (here are the last few lines the build-script throws): make[1]: Leaving directory '/tmp/buildd/koha-19.05.09+20200110003754.96ab4982' fakeroot debian/rules binary dh binary --fail-missing --with bash-completion dh_testroot -O--fail-missing dh_prep -O--fail-missing dh_installdirs -O--fail-missing /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 1: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: etc/koha/sites: not found /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 2: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: var/cache/koha: not found /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 3: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: var/lib/koha: not found /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 4: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: var/log/koha: not found /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 5: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: var/lock/koha: not found /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: 6: /tmp/buildd/koha-19.05.09+20200110003754.96ab4982/debian/koha-common.dirs: var/spool/koha: not found dh_installdirs: problem reading debian/koha-common.dirs: debian/rules:9: recipe for target 'binary' failed make: *** [binary] Error 127 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 E: Failed autobuilding of package I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build//1505 and its subdirectories Don't know if it's problematic but following the build output there are a lot fail-missings: dh_auto_build dh_auto_clean dh_auto_configure dh_auto_test dh_binary dh_build dh_clean dh_installdirs dh_prep dh_testdir dh_testroot dh_update_autotools_config changing the compatability-level of pbuilder wasn't helpful. My VirtualBox looks like this: 4GB Ram, variable filesystem size (max 32GB). Debian 8 (Jessie) is used (but Stretch has the exact same issues). Used the default installation from Debian, but XFCE as desktop environment. These packages where installed by myself: git, libmodern-perl-perl, pbuilder, dh-make, gnupg2, devscripts, dput, build-essential, module-assistant As root: m-a prepare; mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso sh /media/cdrom/VBoxLinuxAdditions.run adduser marco vboxsfsu mounting host partition under /media/sf_Share as root: pbuilder create --distribution jessie ...and as root (like in the tutorial for building packages the easy way): pbuilder --login --save-after-login echo "deb http://debian.koha-community.org/koha stable main" > /etc/apt/sources.list.d/koha.list apt-get install wget gnupg2 wget -O- http://debian.koha-community.org/koha/gpg.asc | apt-key add - apt-get update exit checkout koha: cd /media/sf_Share (mounted host-partition) git clone git://git.koha-community.org/koha.git git checkout -b 19.05.x origin/19.05.x cd /media/sf_Share cp -rf koha koha-build cd /media/sf_Share/koha-build as root: /media/sf_Share/koha-build/debian/build-git-snapshot -v 19.05.09 -d Thats all i did. What am i doing wrong? Any ideas or more information needed? Best wishes Marco
Hehe, silly me! i used a mounted directory from the host system within the virtualbox guest. May be some write permission issues occured. The mounted directory lays on an ext4 partition. Using ~/.debian as directory (as described in the tutorial) was the solution. Now i have problems with some tests. connection to memcached server failed. 'would sugest some package is missing. Stay tuned... best wishes Marco
I recommend you try the koha-dpkg docker image. El dom., 12 de enero de 2020 13:08, M.Wahls <marco.wahls@gmx.de> escribió:
Hehe, silly me! i used a mounted directory from the host system within the virtualbox guest. May be some write permission issues occured. The mounted directory lays on an ext4 partition.
Using ~/.debian as directory (as described in the tutorial) was the solution.
Now i have problems with some tests. connection to memcached server failed.
'would sugest some package is missing. Stay tuned...
best wishes Marco _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Probably a good idea to use koha-dpkg, as I think that’s fairly widely used now. However, if you’re feeling adventurous, you can try https://gitlab.com/minusdavid/koha-deb-builder-docker. It probably won’t work the first time, as I’m having issues where some dependencies (libcache-perl libconvert-basen-perl libcrypt-gcrypt-perl liblocale-maketext-lexicon-perl) aren’t being automagically detected. But if you install those manually in the Docker container and then run the build script, it should work a treat. (One of these days I’ll investigate that dependency issue. They’re missing from the Debian control file but in theory koha-dpkg doesn’t have this problem.) Personally, I use koha-deb-builder-docker (which I wrote), because I use Windows as my host, and I recall having issues running older versions of koha-dpkg on it. I haven’t had much luck mounting Windows based Git repositories into Docker containers. In this case, you can do your dev work anywhere, export a Koha tarball, and then provide that to koha-deb-builder-docker. Anyway, I’m use koha-dpkg will meet your needs. (Also, I imagine warnings about “connection to Memcached server failed” will just be warnings and not errors. I think they can safely be ignored, since you shouldn’t need a real Memcached server running when doing a build/running unit tests…) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Tomas Cohen Arazi Sent: Monday, 13 January 2020 5:40 AM To: M.Wahls <marco.wahls@gmx.de> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Build the easy way throws error I recommend you try the koha-dpkg docker image. El dom., 12 de enero de 2020 13:08, M.Wahls <marco.wahls@gmx.de <mailto:marco.wahls@gmx.de> > escribió: Hehe, silly me! i used a mounted directory from the host system within the virtualbox guest. May be some write permission issues occured. The mounted directory lays on an ext4 partition. Using ~/.debian as directory (as described in the tutorial) was the solution. Now i have problems with some tests. connection to memcached server failed. 'would sugest some package is missing. Stay tuned... best wishes Marco _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Thank you. You helped me a lot! I analysed the docker image and used the description on the webside of the docker image. And was able to get things working using the debian installation on VirtualBox. Here are my steps. There are some litte changes compared to the tutorial in the koha-wiki. May be it helps someone somehow. Debian virtualbox setup min 2GB Ram, 20GB variable Filesystem Downloaded installation media is Debian netinstall (setup includes SSH Server und standard systemtools during package selection). after reboot install the following software: apt-get install devscripts pbuilder dh-make fakeroot debian-archive-keyring libmodern-perl-perl create build image: pbuilder create --distribution stretch pbuilder login --save-after-login export VERSION=19.11 echo "deb http://debian.koha-community.org/koha $VERSION main" > /etc/apt/sources.list.d/koha.list
To build a package from master, you need the following steps instead of the two mentioned above: echo "deb http://debian.koha-community.org/koha unstable main" > /etc/apt/sources.list.d/koha.list echo "deb [trusted=yes] http://apt.abunchofthings.net/koha-nightly unstable main" >> /etc/apt/sources.list.d/koha.list the rest of the procedure is the same for master and 19.11, except checkout after cloning the koha repository.
apt install wget gnupg wget -O- http://debian.koha-community.org/koha/gpg.asc | apt-key add - apt update apt install koha-perldeps exit apt-get update apt-get upgrade checkout koha and prepare build: mkdir ~/debian cd ~/debian git clone git://git.koha-community.org/koha.git koha cd koha git checkout -b 19.11.x origin/19.11.x git pull cd .. cp -r koha koha-build mkdir build-result cd koha-build su -c "./debian/build-git-snapshot -r /home/user/debian/build-result -v 19.11.02git -d" cd ../build-result
check if *.deb-files exist: ls -al
Not all steps are importent for the first build, but are usefull later on. best wishes Marco
Hello koha-devel, i'm facing a general problem on debugging. The remote debugger (on koha-testing-docker instance) seams to ignore my breakpoints. If the debugger connects my Komodo-11.1 it stops on the first executable (starman file) and thats it. In my example i used Ubuntu. Koha-testing-docker and Komodo-11.1 are up and running. the debugger connects to komodo. Here are my steps on koha-testing-docker: wget https://downloads.activestate.com/Komodo/releases/11.1.1/remotedebugging/Kom... tar xzf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64.tar.gz mkdir dbgp mkdir dbgp/perllib mv Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64/* dbgp/perllib/ rm -rf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64 ip a sudo koha-plack --stop kohadev start_plack_debug the mapping on the komodo project is configured like this: URI: file://dd1090d5f944/kohadevbox/koha Maps to: /home/user/git/koha it's really a strange problem. And because of a lack of documentation i'm not sure if i just misconfigured something tiny - albeit reading a lot of tutorials and documentation on remote debugging Perl in general. i would sugest the best way is to take a look on a machine i put online. Because it's more handy than writing mails. Feel free to send me an email: marco.wahls@gmx.de best wishes Marco
Hi Marco, Did you see those 3 lines on the wiki (https://wiki.koha-community.org/wiki/Debugging_in_VIM)? """ Remote Debugging won't work under plack; you'll also have to disable plack in the virtualhost as well. Disable Plack Restart Apache """ Regards, Jonathan Le lun. 6 avr. 2020 à 17:30, M.Wahls <marco.wahls@gmx.de> a écrit :
Hello koha-devel,
i'm facing a general problem on debugging. The remote debugger (on koha-testing-docker instance) seams to ignore my breakpoints. If the debugger connects my Komodo-11.1 it stops on the first executable (starman file) and thats it.
In my example i used Ubuntu. Koha-testing-docker and Komodo-11.1 are up and running. the debugger connects to komodo.
Here are my steps on koha-testing-docker: wget https://downloads.activestate.com/Komodo/releases/11.1.1/remotedebugging/Kom... tar xzf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64.tar.gz mkdir dbgp mkdir dbgp/perllib mv Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64/* dbgp/perllib/ rm -rf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64 ip a sudo koha-plack --stop kohadev start_plack_debug
the mapping on the komodo project is configured like this: URI: file://dd1090d5f944/kohadevbox/koha Maps to: /home/user/git/koha
it's really a strange problem. And because of a lack of documentation i'm not sure if i just misconfigured something tiny - albeit reading a lot of tutorials and documentation on remote debugging Perl in general. i would sugest the best way is to take a look on a machine i put online. Because it's more handy than writing mails. Feel free to send me an email: marco.wahls@gmx.de
best wishes Marco _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
I will add the debugger into koha-testing-docker for simplicity. When breakpoints don't work, it is because of the mappings. In KohaDevBox the hostname for the VM was 'kohadevbox' and the URI mapping was set to //kohadevbox/home/vagrant/kohaclone <- that still works In koha-testing-docker the last time I tried the problem was the hostname was resolved into something a bit random like koha_koha_11236287361287. Maybe that's where things don't work. El lun., 6 abr. 2020 a las 12:30, M.Wahls (<marco.wahls@gmx.de>) escribió:
Hello koha-devel,
i'm facing a general problem on debugging. The remote debugger (on koha-testing-docker instance) seams to ignore my breakpoints. If the debugger connects my Komodo-11.1 it stops on the first executable (starman file) and thats it.
In my example i used Ubuntu. Koha-testing-docker and Komodo-11.1 are up and running. the debugger connects to komodo.
Here are my steps on koha-testing-docker: wget
https://downloads.activestate.com/Komodo/releases/11.1.1/remotedebugging/Kom... tar xzf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64.tar.gz mkdir dbgp mkdir dbgp/perllib mv Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64/* dbgp/perllib/ rm -rf Komodo-PerlRemoteDebugging-11.1.1-91089-linux-x86_64 ip a sudo koha-plack --stop kohadev start_plack_debug
the mapping on the komodo project is configured like this: URI: file://dd1090d5f944/kohadevbox/koha Maps to: /home/user/git/koha
it's really a strange problem. And because of a lack of documentation i'm not sure if i just misconfigured something tiny - albeit reading a lot of tutorials and documentation on remote debugging Perl in general. i would sugest the best way is to take a look on a machine i put online. Because it's more handy than writing mails. Feel free to send me an email: marco.wahls@gmx.de
best wishes Marco _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
participants (4)
-
dcook＠prosentient.com.au -
Jonathan Druart -
M.Wahls -
Tomas Cohen Arazi