[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton updated JENKINS-54120 Jenkins / JENKINS-54120 Output directory or source file null. Change By: Robert Middleton Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton updated JENKINS-54120 Jenkins / JENKINS-54120 Output directory or source file null. Change By: Robert Middleton Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. My best guess is that it is a problem with the packaging; I've never encountered that error under normal circumstances. It almost seems like it's trying to install the pbuilder dependency package twice, since just before it fails it says "pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0)" Here's an example of a good build: https://jenkins.rm5248.com/view/CSerial/job/CSerial-debian/23/architecture=armhf/console Note that there could also be a problem with the buster build at the moment; try making sure it works with stretch first. Finally, closing this issue since it appears to be a packaging problem now; I did however add a new check for a bad source directory: https://github.com/jenkinsci/debian-pbuilder-plugin/commit/1ceda90ce782f73d0b0f67210d524fc01d7db7c6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. thanks for the explanation, so this issue can be closed i guess. just to be sure, this error "E: pbuilder-satisfydepends failed." which i get when building for mipsel arch, is also a packaging problem in source? so i need to dig into the source to fix this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. One of the reasons that I don't use 'Debian package builder' and I made my own(based off of jenkins-debian-glue) is because that particular Jenkins plugin doesn't use pbuilder in the correct way(it will run the pbuilder commands directly on your system, instead of actually making a chroot environment). So if something is working with debian-package-builder and not with debian-pbuilder, it is most likely a packaging problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title
Christoph Loesch edited a comment on JENKINS-54120
Re: Output directory or source file null.
thanks, you're right, i forgot this one. now it seems to run through, but stops later.. ([seems to be a packaging problem| [https://github.com/mika/jenkins-debian-glue/issues/200 #issuecomment-431609562]] in olsrd .then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with : plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") {code:java}make[2]: Entering directory '/build/olsrd-0.9.6.1'mkdir -p /build/olsrd-0.9.6.1/debian/olsrd/usr/sbininstall -m 755 olsrd /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin: /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/olsrdif [ -e /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh ]; then \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new; \ echo "Policy routing script was saved as /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new"; \ else \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh; \ fi= C O N F I G U R A T I O N - F I L E olsrd uses the configfile /etc/olsrd/olsrd.confa default configfile. A sample RFC-compliance aimedconfigfile can be found in olsrd.conf.default.rfc.However none of the larger OLSRD using networks use thatso install a configfile with activated link quality exstensionsper default.can be found at files/olsrd.conf.default.lq==mkdir -p /etc/olsrdmkdir: cannot create directory '/etc/olsrd': Permission deniedmake[2]: *** [Makefile:177: install_olsrd] Error 1make[2]: Leaving directory '/build/olsrd-0.9.6.1'make[1]: *** [debian/rules:27: override_dh_auto_install] Error 2make[1]: Leaving directory '/build/olsrd-0.9.6.1'make: *** [debian/rules:15: binary] Error 2dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2E: Failed autobuilding of packageI: unmounting dev/ptmx filesystemI: unmounting dev/pts filesystemI: unmounting dev/shm filesystemI: unmounting proc filesystemI: unmounting sys filesystemI: Cleaning COW directoryI: forking: rm -rf /var/cache/pbuilder/build/cow.35458Build step 'Debian Pbuilder' marked build as failureFinished: FAILURE{code} then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") interesting also, when i try with architecture mipsel, it stops at another point, see log:[https://gist.github.com/vchrizz/7cde387c0c1ebdfc5efd68eef2879e6e]why does it stop here when apt should install packages?{code:java}...0 packages upgraded, 221 newly installed, 0 to remove and 0 not upgraded.Need to get 70.9 MB/93.8 MB of archives. After unpacking 364 MB will be used.Writing extended state information...E: pbuilder-satisfydepends failed.I: Copying back the cached apt archive contentsI: unmounting dev/ptmx filesystemI: unmounting dev/pts filesystemI: unmounting dev/shm filesystemI: unmounting proc filesystemI: unmounting sys filesystemI: Cleaning COW directoryI: forking: rm -rf /var/cache/pbuilder/build/cow.31117Build step 'Debian Pbuilder' marked build as failure{code}
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. thanks, you're right, i forgot this one. now it seems to run through, but stops later.. (seems to be a packaging problem in olsrd. then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") make[2]: Entering directory '/build/olsrd-0.9.6.1' mkdir -p /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin install -m 755 olsrd /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin : /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/olsrd if [ -e /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh ]; then \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new; \ echo "Policy routing script was saved as /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new"; \ else \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh; \ fi = C O N F I G U R A T I O N - F I L E olsrd uses the configfile /etc/olsrd/olsrd.conf a default configfile. A sample RFC-compliance aimed configfile can be found in olsrd.conf.default.rfc. However none of the larger OLSRD using networks use that so install a configfile with activated link quality exstensions per default. can be found at files/olsrd.conf.default.lq == mkdir -p /etc/olsrd mkdir: cannot create directory '/etc/olsrd': Permission denied make[2]: *** [Makefile:177: install_olsrd] Error 1 make[2]: Leaving directory '/build/olsrd-0.9.6.1' make[1]: *** [debian/rules:27: override_dh_auto_install] Error 2 make[1]: Leaving directory '/build/olsrd-0.9.6.1' make: *** [debian/rules:15: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 E: Failed autobuilding of package I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: Cleaning COW directory I: forking: rm -rf /var/cache/pbuilder/build/cow.35458 Build step 'Debian Pbuilder' marked build as failure Finished: FAILURE Add Comment
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. Did you update the 'Location of debian/ folder' parameter? You will have to set that to 'source/'(or whatever your source directory is), if it's still set to '.' it won't work properly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title
Christoph Loesch commented on JENKINS-54120
Re: Output directory or source file null.
ok, added to Source-Code-Management: Additional Behaviours: Check out to a sub-directory: source to be sure i checked the wiki and noticed i did it exactly as described in Project Setup(Traditional) now it stops here:
...
Fetching upstream changes from https://salsa.debian.org/debian/olsrd.git
> git fetch --tags --progress https://salsa.debian.org/debian/olsrd.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision aa2a47024230b443052c5b07163ec2f76361c7e0 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f aa2a47024230b443052c5b07163ec2f76361c7e0
Commit message: "d/control: Remove trailing whitespaces"
> git rev-list --no-walk aa2a47024230b443052c5b07163ec2f76361c7e0 # timeout=10
$ dpkg-parsechangelog --version
[olsrd] $ dpkg-parsechangelog --count 1
We do not appear to have an actual package
Build step 'Debian Pbuilder' marked build as failure
Finished: FAILURE
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. Okay, first thing: make sure that you have your checkout in a sub-folder(e.g. source/). Because of how dpkg works, it will generate the files needed for the build in the parent directory, so that's probably why it's failing. Next, you also will need to clean your workspace before the new build; I generally nuke the entire workspace, but it should be possible to just delete *.tar.gz and *.dsc if the checkout would take too long. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. seems I'm able to only post one screenshot in a posting... 3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch updated an issue Jenkins / JENKINS-54120 Output directory or source file null. Change By: Christoph Loesch Attachment: jenkins-workspace-olsrd.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. first time - I have just set up jenkins and trying to automate my manual work. It works with Debian Package Builder plugin, but its not easy to crosscompile with that, so I'm trying Debian Pbuilder plugin and am stuck here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch updated an issue Jenkins / JENKINS-54120 Output directory or source file null. Change By: Christoph Loesch Attachment: debian-pbuilder-plugin-conf.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. A couple of questions here: Is this a recent thing - did it work before, or is this the first time? Can you post a screenshot of your debian pbuilder build configuration or the relevant part of your Jenkinsfile? Can you post a screenshot of what your workspace for this build looks like? It seems to be failing because either the 'binaries' directory was not created, or there is no .dsc file to build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch created an issue Jenkins / JENKINS-54120 Output directory or source file null. Issue Type: Bug Assignee: Robert Middleton Components: debian-pbuilder-plugin Created: 2018-10-17 09:29 Priority: Minor Reporter: Christoph Loesch using Jenkins ver. 2.138.2 with debian-pbuilder-plugin 1.4 when trying to build a debian package: ... I: new cache content 'libgpg-error0_1.26-2_mips.deb' added I: new cache content 'libxapian30_1.4.3-2+deb9u1_mips.deb' added I: new cache content 'libblkid1_2.29.2-1+deb9u1_mips.deb' added I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem Output directory or source file null. This is a programming problem, please file a bug report. Build step 'Debian Pbuilder' marked build as failure Add Comment
