[Tails-dev] Tor Monitor build fails
Hi, Sascha Steinbiss wrote: > Long story short, there’s a first version of a tor-monitor package in: > https://github.com/satta/tor-monitor > I just tried to build the package and failed: $ git-buildpackage --git-debian-branch=debian dh clean --with python3 --buildsystem=pybuild dh_testdir -O--buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory `/home/amnesia/Persistent/dev/tor-monitor' rm -f po/tormonitor.pot rm -rf build make[1]: Leaving directory `/home/amnesia/Persistent/dev/tor-monitor' dh_clean -O--buildsystem=pybuild gbp:error: Couldn't checkout "tor-monitor_0.1.orig.tar.gz": Execution failed: [Errno 2] No such file or directory What am I doing wrong? I'm doing exactly what works for our other python packages. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Hi, Alan: > Hi, > > Sascha Steinbiss wrote: >> > Long story short, there’s a first version of a tor-monitor package in: >> > https://github.com/satta/tor-monitor >> > > I just tried to build the package and failed: > > $ git-buildpackage --git-debian-branch=debian > dh clean --with python3 --buildsystem=pybuild >dh_testdir -O--buildsystem=pybuild >debian/rules override_dh_auto_clean > make[1]: Entering directory `/home/amnesia/Persistent/dev/tor-monitor' > rm -f po/tormonitor.pot > rm -rf build > make[1]: Leaving directory `/home/amnesia/Persistent/dev/tor-monitor' >dh_clean -O--buildsystem=pybuild > gbp:error: Couldn't checkout "tor-monitor_0.1.orig.tar.gz": Execution > failed: [Errno 2] No such file or directory > > What am I doing wrong? I'm doing exactly what works for our other python > packages. I could build the package successfully. Please make sure to fetch all the branches, namely pristine-tar and build from debian/sid. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Hi, u wrote: > Alan: > > I just tried to build the package and failed: > > > > $ git-buildpackage --git-debian-branch=debian > > gbp:error: Couldn't checkout "tor-monitor_0.1.orig.tar.gz": Execution > > failed: [Errno 2] No such file or directory > > > > What am I doing wrong? I'm doing exactly what works for our other python > > packages. > > I could build the package successfully. Please make sure to fetch all > the branches, namely pristine-tar I do have pristine-tar following satta/pristine-tar > and build from debian/sid. > debian/sid is a tag. When I try to build from it, I get: gbp.git.repository.GitRepositoryError: Currently not on a branch I also tried to clone https://github.com/satta/tor-monitor.git to a new empty repo, create the branches, and got the same result. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Hi Alan, > I just tried to build the package and failed: > >$ git-buildpackage --git-debian-branch=debian >dh clean --with python3 --buildsystem=pybuild > dh_testdir -O--buildsystem=pybuild > debian/rules override_dh_auto_clean >make[1]: Entering directory `/home/amnesia/Persistent/dev/tor-monitor' >rm -f po/tormonitor.pot >rm -rf build >make[1]: Leaving directory `/home/amnesia/Persistent/dev/tor-monitor' > dh_clean -O--buildsystem=pybuild >gbp:error: Couldn't checkout "tor-monitor_0.1.orig.tar.gz": Execution > failed: [Errno 2] No such file or directory > > What am I doing wrong? I'm doing exactly what works for our other python > packages. Hmm, I don’t get why you are using —git-debian-branch. There is no ‘debian’ branch…? What branch are you on when you try to build as shown above? I can build everything perfectly directly after cloning: [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git Cloning into 'tor-monitor'... remote: Counting objects: 153, done. remote: Compressing objects: 100% (74/74), done. remote: Total 153 (delta 78), reused 145 (delta 70), pack-reused 0 Receiving objects: 100% (153/153), 32.71 KiB | 0 bytes/s, done. Resolving deltas: 100% (78/78), done. Checking connectivity... done. [vagrant@debian-8:~] $ cd tor-monitor [vagrant@debian-8:~/tor-monitor] $ gbp buildpackage --git-pbuilder -uc -us gbp:info: tor-monitor_0.1.orig.tar.gz does not exist, creating from 'upstream/0.1' Building with cowbuilder for distribution sid I: using cowbuilder as pbuilder […] As you can see, the tarball is created if it does not exist. Does this work for you? Cheers Sascha ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
On Mon, 24 Aug 2015 12:59:35 + (UTC) Alan wrote: > What am I doing wrong? I'm doing exactly what works for our other > python packages. There's no branch called `debian`. ❯ git branch -r origin/HEAD -> origin/master origin/master origin/pristine-tar origin/upstream I suggest cloning all of the branches with `gbp clone https://github.com/satta/tor-monitor.git`. This command will ensure that you get the pristine-tar branch. The package built fine for me with sbuild and git-buildpackage. pgpMFqlZKVphx.pgp Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Hi, Sascha Steinbiss wrote: > I can build everything perfectly directly after cloning: > > [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git > Cloning into 'tor-monitor'... > remote: Counting objects: 153, done. > remote: Compressing objects: 100% (74/74), done. > remote: Total 153 (delta 78), reused 145 (delta 70), pack-reused 0 > Receiving objects: 100% (153/153), 32.71 KiB | 0 bytes/s, done. > Resolving deltas: 100% (78/78), done. > Checking connectivity... done. > [vagrant@debian-8:~] $ cd tor-monitor > [vagrant@debian-8:~/tor-monitor] $ gbp buildpackage --git-pbuilder -uc -us > gbp:info: tor-monitor_0.1.orig.tar.gz does not exist, creating from > 'upstream/0.1' > Building with cowbuilder for distribution sid > I: using cowbuilder as pbuilder > […] > > As you can see, the tarball is created if it does not exist. Does this work > for you? > No, it doesn't work under Tails (based on wheezy), but I tried under jessie and the build starts... but then I hit: $ gbp buildpackage --git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us gbp:info: Building with pbuilder for jessie Building with pbuilder for distribution jessie, architecture i386 I: using pbuilder as pbuilder dpkg-buildpackage: source package tor-monitor dpkg-buildpackage: source version 0.1-1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Sascha Steinbiss dpkg-source --before-build tor-monitor-packaging fakeroot debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_testdir -O--buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory 'XXX/tor-monitor-packaging' rm -f po/tormonitor.pot rm -rf build make[1]: Leaving directory 'XXX/tor-monitor-packaging' dh_clean -O--buildsystem=pybuild dpkg-source -b tor-monitor-packaging dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building tor-monitor using existing ./tor-monitor_0.1.orig.tar.gz dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no final newline (either original or modified version) dpkg-source: info: local changes detected, the modified files are: tor-monitor-packaging/tormonitor.desktop dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/tor-monitor_0.1-1.diff.3aQP6Q dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-buildpackage: error: dpkg-source -b tor-monitor-packaging gave error exit status 2 gbp:error: 'git-pbuilder -uc -us' failed: it exited with 2 Thanks for your support, Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Alan: Hi Alan, > Sascha Steinbiss wrote: >> I can build everything perfectly directly after cloning: >> >> [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git >> Cloning into 'tor-monitor'... >> remote: Counting objects: 153, done. >> remote: Compressing objects: 100% (74/74), done. >> remote: Total 153 (delta 78), reused 145 (delta 70), pack-reused 0 >> Receiving objects: 100% (153/153), 32.71 KiB | 0 bytes/s, done. >> Resolving deltas: 100% (78/78), done. >> Checking connectivity... done. >> [vagrant@debian-8:~] $ cd tor-monitor >> [vagrant@debian-8:~/tor-monitor] $ gbp buildpackage --git-pbuilder -uc -us >> gbp:info: tor-monitor_0.1.orig.tar.gz does not exist, creating from >> 'upstream/0.1' >> Building with cowbuilder for distribution sid >> I: using cowbuilder as pbuilder >> […] >> >> As you can see, the tarball is created if it does not exist. Does this work >> for you? >> > No, it doesn't work under Tails (based on wheezy), but I tried under > jessie and the build starts... but then I hit: > > $ gbp buildpackage --git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us > gbp:info: Building with pbuilder for jessie > Building with pbuilder for distribution jessie, architecture i386 > I: using pbuilder as pbuilder > dpkg-buildpackage: source package tor-monitor > dpkg-buildpackage: source version 0.1-1 > dpkg-buildpackage: source distribution unstable > dpkg-buildpackage: source changed by Sascha Steinbiss > dpkg-source --before-build tor-monitor-packaging > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_testdir -O--buildsystem=pybuild >debian/rules override_dh_auto_clean > make[1]: Entering directory 'XXX/tor-monitor-packaging' > rm -f po/tormonitor.pot > rm -rf build > make[1]: Leaving directory 'XXX/tor-monitor-packaging' >dh_clean -O--buildsystem=pybuild > dpkg-source -b tor-monitor-packaging > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building tor-monitor using existing > ./tor-monitor_0.1.orig.tar.gz > dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no > final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > tor-monitor-packaging/tormonitor.desktop > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/tor-monitor_0.1-1.diff.3aQP6Q > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b tor-monitor-packaging gave error > exit status 2 > gbp:error: 'git-pbuilder -uc -us' failed: it exited with 2 > What's in the diff /tmp/tor-monitor_0.1-1.diff.3aQP6Q? Only this? > dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > tor-monitor-packaging/tormonitor.desktop ? Is this something which could have happened due to some editor configuration on your machine? Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Monitor build fails
Hi all, >> As you can see, the tarball is created if it does not exist. Does this work >> for you? >> > No, it doesn't work under Tails (based on wheezy), but I tried under > jessie and the build starts... but then I hit: > > $ gbp buildpackage --git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us > gbp:info: Building with pbuilder for jessie > Building with pbuilder for distribution jessie, architecture i386 […] > dpkg-source: info: local changes detected, the modified files are: > tor-monitor-packaging/tormonitor.desktop > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/tor-monitor_0.1-1.diff.3aQP6Q > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b tor-monitor-packaging gave error > exit status 2 > gbp:error: 'git-pbuilder -uc -us' failed: it exited with 2 I tried immediately cloning and then building with your exact settings (--git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us) on a newly created jessie-i386 cowbuilder base and it finished fine for me. Indeed it would be really useful to know what the differences are. Did you try the above directly after cloning or did you start a different build before which then was aborted or failed? Could it be that, for example, there are still patches from a previous build applied to the source? Try ‘quilt pop -a’ before rebuilding to make sure all patches are removed. Cheers Sascha ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
