Your message dated Mon, 25 May 2015 18:40:14 +0200 with message-id <[email protected]> and subject line Re: Bug#786793: option to totally ignore upstream source has caused the Debian Bug report #786793, regarding option to totally ignore upstream source to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 786793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786793 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: git-buildpackage Version: 0.6.28 Severity: wishlist Hello, imagine the following usecase: you are developing an upstream version for multiple distros in an upstream branch, and you have a debian specific branch. From time to time, you checkout debian/sid, merge upstream into it and then you would like to quickly check whether the Debian package still builds. This is a pure test build, not intended to be released ever. However, this is not so easy and quick if the upstream source branch is some work in progress version, i.e. there is no tag. Depending on the pristine-tar config option, you end up in sth. like the following (more logs below). gbp:error: upstream/0.8.4 is not a valid treeish or in gbp:error: Pristine-tar couldn't checkout "apt-cacher-ng_0.8.4.orig.tar.xz": fatal: Path 'apt-cacher-ng_0.8.4.orig.tar.xz.delta' does not exist in 'refs/heads/pristine-tar' ^^ That's obviously true but how can I convince it to continue? I studied the manpage and cannot see anything, no -B or --binary-only option or similar things. debuild itself is happy to do what I want when -b is in place. BTW: I also use a separate build directory. It would be nice to have a command line option to do something like "git diff --cached | (cd $build_directory && patch -p1)". Meaning: please take over what I hacked locally (like a totally new configure option in debian/rules) to the build space for a quick test, I want to test it right now and then probably throw the change away, so I don't want to make an extra commit just because it's the only method to deal with gbp. Ok, I probably could use a hook but it should be easier than that.) $ gbp buildpackage --git-ignore-new --git-no-pristine-tar --git-verbose -b gbp:debug: ['git', 'rev-parse', '--show-cdup'] gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] gbp:debug: fakeroot debian/rules clean [] [] dh clean --parallel --with systemd dh_testdir -O--parallel dh_auto_clean -O--parallel ... gbp:debug: ['git', 'symbolic-ref', 'HEAD'] gbp:debug: ['git', 'show-ref', 'refs/heads/debian/sid'] gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'HEAD'] gbp:debug: ['git', 'ls-tree', 'HEAD'] gbp:debug: ['git', 'show', '--pretty=medium', 'HEAD:debian/source/format'] gbp:debug: ['git', 'show', '--pretty=medium', 'HEAD:debian/changelog'] gbp:debug: Looking for orig tarball 'apt-cacher-ng_0.8.4.orig.tar.xz' at '../tarballs/' gbp:info: Orig tarball 'apt-cacher-ng_0.8.4.orig.tar.xz' not found at '../tarballs/' gbp:debug: ['git', 'ls-tree', 'upstream/0.8.4'] gbp:error: upstream/0.8.4 is not a valid treeish -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-rc3.111cputssfix+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages git-buildpackage depends on: ii devscripts 2.15.4 ii git 1:2.1.4-2.1 ii man-db 2.7.0.2-5 ii python 2.7.9-1 ii python-dateutil 2.2-2 ii python-pkg-resources 16.0-2 ii python-six 1.9.0-3 Versions of packages git-buildpackage recommends: ii cowbuilder 0.73 ii pristine-tar 1.33 ii python-requests 2.4.3-6 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii unzip 6.0-17 -- Configuration Files: /etc/git-buildpackage/gbp.conf changed: [DEFAULT] cleaner = debuild clean pristine-tar = True [buildpackage] [import-orig] postimport = git-dch -N%(version)s -S -a --debian-branch=$GBP_BRANCH [import-dsc] [dch] [pq] [clone] [pull] [create-remote-repo] [remote-config pkg-libvirt] remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s template-dir = /srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-template -- no debconf information -- [ Nach einem Vorstellungsgespraech ] <alphascorpii> naja, und ich hatte die Debconf in den Lebenslauf geschrieben, das hat sie 100% überzeugt ;) <Myon> "I moderated krooger postings and survived" <weasel> Myon: "and I didn't even get a fscking t-shirt"
--- End Message ---
--- Begin Message ---On Mon, May 25, 2015 at 05:22:10PM +0200, Eduard Bloch wrote: > Package: git-buildpackage > Version: 0.6.28 > Severity: wishlist > > Hello, > > imagine the following usecase: you are developing an upstream version > for multiple distros in an upstream branch, and you have a debian > specific branch. From time to time, you checkout debian/sid, merge > upstream into it and then you would like to quickly check whether the > Debian package still builds. This is a pure test build, not intended > to be released ever. > > However, this is not so easy and quick if the upstream source branch is > some work in progress version, i.e. there is no tag. Depending on the > pristine-tar config option, you end up in sth. like the following (more > logs below). > > gbp:error: upstream/0.8.4 is not a valid treeish > or in > gbp:error: Pristine-tar couldn't checkout "apt-cacher-ng_0.8.4.orig.tar.xz": > fatal: Path 'apt-cacher-ng_0.8.4.orig.tar.xz.delta' does not exist in > 'refs/heads/pristine-tar' This only happens if you enable pristine tar by default. To not use this for your "scratch builds" just pass --git-no-pristine-tar. If you want the tarball. It will then try to create the tarball from what is referenced in the changelog. If you don't want this either user --git-upstream-tree=<yourbranch>. Cheers, -- Guido
--- End Message ---
