Re: [DNG] Creating .deb packages with jenkins-debian-glue
Hi KatolaZ, KatolaZ writes: > On Thu, May 31, 2018 at 03:29:30PM +0200, KatolaZ wrote: >> On Thu, May 31, 2018 at 09:16:27PM +0900, Olaf Meeuwissen wrote: >> > >> > The "n/a" sounds like you've also been hit by >> > >> > http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 >> > >> > Try using packages.devuan.org. >> >> Please hold on on that. We are working to solve it. Thanks! > Thanks to parazyd who has just fixed it. If you are using > pkgmaster.devuan.org, please `apt-get update` and then lsb_release > will work correctly: > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Devuan > Description:Devuan GNU/Linux 2.0 (ascii) > Release:2.0 > Codename: ascii > $ Works for me, closed the bug report mentioned above. > If you are on deb.devuan.org it might take up to one hour to > propagate. Please report any undesired behaviour. I'm using deb.devuan.org, so things appear to have propagated just fine. My ascii InRelease files were timestamped 2018-06-02 01:02 JST when I tested. That works out to 2018-06-01 16:02 UTC, if I got my arithmetic right ;-) Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
On Thu, 31 May 2018 16:33:06 +0200, KatolaZ wrote in message <20180531143306.fmu656thmuzgx...@katolaz.homeunix.net>: > On Thu, May 31, 2018 at 03:29:30PM +0200, KatolaZ wrote: > > On Thu, May 31, 2018 at 09:16:27PM +0900, Olaf Meeuwissen wrote: > > > Hi Tom, > > > > > > Tom writes: > > > > > > > Hi, > > > > > > > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to > > > > package a python app into a .deb using jenkins. > > > > > > > > I followed all the instructions on > > > > https://jenkins-debian-glue.org, updating the steps where > > > > required for differences in the latest Jenkins release, but I > > > > see errors when running the jenkins-debian-glue-binaries job. > > > > > > > > It looked like it was failing due to the output of 'lsb_release > > > > --short --codename' returning "n/a" on Devuan Ascii, so I > > > > created /etc/lsb-release with the relevant details. It's now > > > > showing a different error. > > > > > > The "n/a" sounds like you've also been hit by > > > > > > http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 > > > > > > Try using packages.devuan.org. > > > > Please hold on on that. We are working to solve it. > > > > > Thanks to parazyd who has just fixed it. If you are using > pkgmaster.devuan.org, please `apt-get update` and then lsb_release > will work correctly: > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Devuan > Description:Devuan GNU/Linux 2.0 (ascii) > Release:2.0 > Codename: ascii > $ > > If you are on deb.devuan.org it might take up to one hour to > propagate. Please report any undesired behaviour. > > HTH > > KatolaZ > ..this means OP (Tom) can go back to his plan A (using dh_virtualenv, jenkins-debian-glue and jenkins) because parazyd fixed the bugs there so Tom's plan A will now work? ..I also got the impression "Tom's plan A" is the easier and better way when joining devuan.org as a packager and package maintainer, while dpkg-buildpackage is a better and easier way for people who just rarely needs custom built packages on his own home boxes. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
On Thu, May 31, 2018 at 03:29:30PM +0200, KatolaZ wrote: > On Thu, May 31, 2018 at 09:16:27PM +0900, Olaf Meeuwissen wrote: > > Hi Tom, > > > > Tom writes: > > > > > Hi, > > > > > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to package > > > a python app into a .deb using jenkins. > > > > > > I followed all the instructions on https://jenkins-debian-glue.org, > > > updating the steps where required for differences in the latest > > > Jenkins release, but I see errors when running the > > > jenkins-debian-glue-binaries job. > > > > > > It looked like it was failing due to the output of 'lsb_release > > > --short --codename' returning "n/a" on Devuan Ascii, so I created > > > /etc/lsb-release with the relevant details. It's now showing a > > > different error. > > > > The "n/a" sounds like you've also been hit by > > > > http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 > > > > Try using packages.devuan.org. > > Please hold on on that. We are working to solve it. > Thanks to parazyd who has just fixed it. If you are using pkgmaster.devuan.org, please `apt-get update` and then lsb_release will work correctly: $ lsb_release -a No LSB modules are available. Distributor ID: Devuan Description:Devuan GNU/Linux 2.0 (ascii) Release:2.0 Codename: ascii $ If you are on deb.devuan.org it might take up to one hour to propagate. Please report any undesired behaviour. HTH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
On Thu, May 31, 2018 at 09:16:27PM +0900, Olaf Meeuwissen wrote: > Hi Tom, > > Tom writes: > > > Hi, > > > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to package > > a python app into a .deb using jenkins. > > > > I followed all the instructions on https://jenkins-debian-glue.org, > > updating the steps where required for differences in the latest > > Jenkins release, but I see errors when running the > > jenkins-debian-glue-binaries job. > > > > It looked like it was failing due to the output of 'lsb_release > > --short --codename' returning "n/a" on Devuan Ascii, so I created > > /etc/lsb-release with the relevant details. It's now showing a > > different error. > > The "n/a" sounds like you've also been hit by > > http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 > > Try using packages.devuan.org. Please hold on on that. We are working to solve it. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
Hi Tom, Tom writes: > Hi, > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to package > a python app into a .deb using jenkins. > > I followed all the instructions on https://jenkins-debian-glue.org, > updating the steps where required for differences in the latest > Jenkins release, but I see errors when running the > jenkins-debian-glue-binaries job. > > It looked like it was failing due to the output of 'lsb_release > --short --codename' returning "n/a" on Devuan Ascii, so I created > /etc/lsb-release with the relevant details. It's now showing a > different error. The "n/a" sounds like you've also been hit by http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 Try using packages.devuan.org. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
> On 31 May 2018, at 18:51, KatolaZ wrote: > >> On Thu, May 31, 2018 at 05:42:21PM +1000, Tom wrote: >> Hi, >> >> I'm trying to use dh_virtualenv and and jenkins-debian-glue to package >> a python app into a .deb using jenkins. >> >> I followed all the instructions on https://jenkins-debian-glue.org, >> updating the steps where required for differences in the latest >> Jenkins release, but I see errors when running the >> jenkins-debian-glue-binaries job. > > > Tom, if you just need the package locally, a better and easier way > could be to just use dpkg-buildpackage. You need to satisfy the build > deps locally, but apart from the that the process is quite > straightforward. > > jenkins-debian-glue is a bit too convoluted and requires some extra > stuff that you really don't need to build the occasional package. > > HTH > > KatolaZ Thanks, I’ll definitely take a look at that. Are there any good tutorials out there on using dpkg-buildpackage and how to correctly manage the version, changelog, and other files used for the deb packaging? Most of the stuff I’ve seen is aimed towards providing deb packages for the official Debian package archive. I noticed that jenkins-debian-glue goes and stores the built packages in something called reprepro that looks like a local apt repository? Is this easy to use outside of jenkins-debian-glue? What’s the generally recommended way to store and deploy release artifacts, in this case deb files, from Jenkins? Do I store them in something like this reprepro tool? Do I use a commercial tool like artifactory? Thanks —Tom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Creating .deb packages with jenkins-debian-glue
On Thu, May 31, 2018 at 05:42:21PM +1000, Tom wrote: > Hi, > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to package > a python app into a .deb using jenkins. > > I followed all the instructions on https://jenkins-debian-glue.org, > updating the steps where required for differences in the latest > Jenkins release, but I see errors when running the > jenkins-debian-glue-binaries job. Tom, if you just need the package locally, a better and easier way could be to just use dpkg-buildpackage. You need to satisfy the build deps locally, but apart from the that the process is quite straightforward. jenkins-debian-glue is a bit too convoluted and requires some extra stuff that you really don't need to build the occasional package. HTH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Creating .deb packages with jenkins-debian-glue
Hi,
I'm trying to use dh_virtualenv and and jenkins-debian-glue to package
a python app into a .deb using jenkins.
I followed all the instructions on https://jenkins-debian-glue.org,
updating the steps where required for differences in the latest
Jenkins release, but I see errors when running the
jenkins-debian-glue-binaries job.
It looked like it was failing due to the output of 'lsb_release
--short --codename' returning "n/a" on Devuan Ascii, so I created
/etc/lsb-release with the relevant details. It's now showing a
different error.
I have the "jenkins-debian-glue-buildenv-devuan" package installed, if
that matters.
Are there any configuration files I need to change from default for
any packages associated with this? eg. /etc/git-buildpackage/gbp.conf
Are there any easier alternatives to create .deb packages? I have no
prior experience with this, so I used this as the jenkins-debian-glue
project was the first thing I discovered on google. I am not creating
packages to go into Devuan archive, just for private usage on a local
network.
--- ERROR LOG ---
Started by upstream project "deb-test/jenkins-debian-glue-binaries"
build number 6
originally caused by:
Started by upstream project "deb-test/jenkins-debian-glue-source"
build number 11
originally caused by:
Started by user Admin (admin)
Building on master in workspace
/var/lib/jenkins/workspace/deb-test/jenkins-debian-glue-binaries/architecture/amd64
[WS-CLEANUP] Deleting project workspace...
Copied 5 artifacts from "deb-test » jenkins-debian-glue-source" build number 11
[amd64] $ /bin/sh -xe /tmp/jenkins6420083586795712532.sh
+ /usr/bin/build-and-provide-package
+ set -u
+ umask 022
+ PATH=/bin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin
+ export QEMU_RESERVED_VA=0x0
+ QEMU_RESERVED_VA=0x0
++ date
+ echo '*** Starting /usr/bin/build-and-provide-package at Thu 31 May
17:24:30 AEST 2018 ***'
*** Starting /usr/bin/build-and-provide-package at Thu 31 May 17:24:30
AEST 2018 ***
++ sed -e 's/^\([0-9]*\).*/\1/'
+ start_seconds=1233774
++ dpkg --list jenkins-debian-glue
++ awk '/^ii/ {print $3}'
+ JENKINS_DEBIAN_GLUE_VERSION=0.18.4
+ '[' -n 0.18.4 ']'
+ echo '*** Running jenkins-debian-glue version 0.18.4 ***'
*** Running jenkins-debian-glue version 0.18.4 ***
++ dpkg --print-architecture
+ HOST_ARCH=amd64
+ '[' -n amd64 ']'
+ echo '*** Identified host architecture amd64 ***'
*** Identified host architecture amd64 ***
+ trap bailout SIGHUP SIGINT SIGQUIT SIGABRT SIGALRM SIGTERM
+ checks_and_defaults
+ '[' -z '' ']'
+ local repository_is_missing_in_env=true
+ '[' -r /etc/jenkins/debian_glue ']'
+ . /etc/jenkins/debian_glue
+ '[' -n '' ']'
+ '[' -n '' ']'
+ '[' -z deb-test/jenkins-debian-glue-binaries/architecture=amd64 ']'
+ '[' -z amd64 ']'
+ set_debootstrap
+ '[' -n '' ']'
+ '[' amd64 = amd64 ']'
+ DEBOOTSTRAP=debootstrap
+ return 0
+ '[' -z '' ']'
+ REPREPRO_OPTS='-v --waitforlock 1000'
+ echo '*** REPREPRO_OPTS is unset, using default: -v --waitforlock 1000 ***'
*** REPREPRO_OPTS is unset, using default: -v --waitforlock 1000 ***
+ REPREPRO_CMD=reprepro
+ '[' -z '' ']'
+ DEFAULT_REPOSITORY=/srv/repository
+ '[' -z '' ']'
+ REPOSITORY=/srv/repository
+ '[' -z '' ']'
+ PBUILDER_HOOKDIR=/usr/share/jenkins-debian-glue/pbuilder-hookdir/
+ '[' -z '' ']'
+ '[' -z '' ']'
+ FREIGHT_VARLIB=/var/lib/freight
+ FREIGHT_VARCACHE=/var/cache/freight
+ FREIGHT_CONF=/etc/freight.conf
+ clean_workspace
++ pwd
+ echo '*** The following files have been noticed in the workspace
[/var/lib/jenkins/workspace/deb-test/jenkins-debian-glue-binaries/architecture/amd64]:
***'
*** The following files have been noticed in the workspace
[/var/lib/jenkins/workspace/deb-test/jenkins-debian-glue-binaries/architecture/amd64]:
***
+ ls -la ./
total 56
drwxr-xr-x 2 jenkins jenkins 4096 May 31 17:24 .
drwxr-xr-x 3 jenkins jenkins 4096 May 31 17:24 ..
-rw-r--r-- 1 jenkins jenkins 15573 May 31 17:24
deb-test_0.1.0-local+0~20180531072409.11~1.gbpf2793c.diff.gz
-rw-r--r-- 1 jenkins jenkins 992 May 31 17:24
deb-test_0.1.0-local+0~20180531072409.11~1.gbpf2793c.dsc
-rw-r--r-- 1 jenkins jenkins 5543 May 31 17:24
deb-test_0.1.0-local+0~20180531072409.11~1.gbpf2793c_source.buildinfo
-rw-r--r-- 1 jenkins jenkins 13031 May 31 17:24 deb-test_0.1.0.orig.tar.gz
-rw-r--r-- 1 jenkins jenkins 661 May 31 17:24 lintian.txt
+ identify_package_name
+ PACKAGE=deb-test/jenkins-debian-glue-binaries/architecture=amd64
+ PACKAGE=deb-test/jenkins-debian-glue
+ '[' -n deb-test/jenkins-debian-glue ']'
+ echo '*** Identified Debian package name deb-test/jenkins-debian-glue ***'
*** Identified Debian package name deb-test/jenkins-debian-glue ***
+ set_base_path
+ '[' -n '' ']'
+
BASE_PATH=/var/lib/jenkins/workspace/deb-test/jenkins-debian-glue-binaries/architecture/amd64
+ echo '*** Using $WORKSPACE
[/var/lib/jenkins/workspace/deb-test/jenkins-debian-glue-binaries/architecture/amd64]
as default for BASE_PATH ***'
*** Using $WORKSPACE
