Re: [Reproducible-builds] dpkg_1.18.1.0~reproducible5 ftbfs

2015-08-05 Thread Holger Levsen
Hi Guillem,

On Mittwoch, 5. August 2015, Guillem Jover wrote:
 Ah, the problem is that the releases are being made directly from
 git with dpkg-buildpackage. 

indeed, that's how I've built.

 The correct way to release dpkg is to
 «make dist» and then build Debian packages from that tarball.

that didnt work, but...

 The detailed instructions on releasing can be found on the “How to
 release“ section here:
   https://wiki.debian.org/Teams/Dpkg/GitUsage

these were helpful indeed, thanks a lot, but this happened:

- I kept UNRELEASED as distro in debian/changelog
- I didnt create a tag for the release… (also because we have the illegal (for 
git tags) character ~ in our version...)
- then I ran git clean -Xdf 
- then I ran autoreconf -f -i; ./configure; DPKG_DEVEL_MODE=1 make distcheck 
which created dpkg-1.18.1-11-g1c825.tar.xz - which is not what I expected as 
1.18.2.0~reproducible1 is the version in debian/changelog...

What now? debian/changelog inside dpkg-1.18.1-11-g1c825.tar.xz has the correct 
version, but I assume there's another location I need to change this...

If you want to look yourself, our repo is at 
git.debian.org/git/reproducible/dpkg.git and the branch is 
pu/reproducibe_builds

Thanks again for your support, much appreciated!


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] dpkg_1.18.1.0~reproducible5 ftbfs

2015-08-04 Thread Vagrant Cascadian
On 2015-07-31, Guillem Jover wrote:
 On Fri, 2015-07-31 at 16:49:13 +0200, Holger Levsen wrote:
 so yesterday I tried to build 
 http://reproducible.alioth.debian.org/debian/dpkg_1.18.1.0~reproducible5.dsc 
 with pbuilder on sid/armhf and that failed _exactly_ like 
 https://reproducible.debian.net/rbuild/unstable/amd64/dpkg_1.18.1.0~reproducible5.rbuild.log
 
 I then tried to build dpkg_1.18.1.dsc from sid proper and that built 
 flawlessly on sid/armhf.
 
 Thus I conclude our reproducible patches cause this, whatever this is. Yet I 
 lack time atm to debug this, so this mail is merely a note to Guillem and a 
 call for help to the reproducible folks.

 Right, I noticed this quite some time ago, but forgot to bring it up.
 W/o having checked anything, it might be that whoever prepared the
 release perhaps forgot to «autoreconf -f -i» the sources and prepared
 it from a previous .dsc instead of a git tree?

I *think* what's happening is the reproducible builds git tree doesn't
include tags for the version, and .dist-version isn't present, so
./get-version is returning an empty string (it can't get it from git or
From .dist-version), so autoreconf -f -i fails... running:

  echo 1.18.1.0~reproducible5  .dist-version
  autoreconf -f -i
  debuild -us -uc # or your build of choice

Seems to fix/workaround the issue.


live well,
  vagrant


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] dpkg_1.18.1.0~reproducible5 ftbfs

2015-08-04 Thread Guillem Jover
On Tue, 2015-08-04 at 08:42:48 -0700, Vagrant Cascadian wrote:
 On 2015-07-31, Guillem Jover wrote:
  Right, I noticed this quite some time ago, but forgot to bring it up.
  W/o having checked anything, it might be that whoever prepared the
  release perhaps forgot to «autoreconf -f -i» the sources and prepared
  it from a previous .dsc instead of a git tree?
 
 I *think* what's happening is the reproducible builds git tree doesn't
 include tags for the version, and .dist-version isn't present, so
 ./get-version is returning an empty string (it can't get it from git or
 From .dist-version), so autoreconf -f -i fails... running:
 
   echo 1.18.1.0~reproducible5  .dist-version
   autoreconf -f -i
   debuild -us -uc # or your build of choice
 
 Seems to fix/workaround the issue.

Ah, the problem is that the releases are being made directly from
git with dpkg-buildpackage. The correct way to release dpkg is to
«make dist» and then build Debian packages from that tarball.

The detailed instructions on releasing can be found on the “How to
release“ section here:

  https://wiki.debian.org/Teams/Dpkg/GitUsage

although several points might not be relevant here.

Thanks,
Guillem

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] dpkg_1.18.1.0~reproducible5 ftbfs

2015-07-31 Thread Guillem Jover
Hi!

On Fri, 2015-07-31 at 16:49:13 +0200, Holger Levsen wrote:
 so yesterday I tried to build 
 http://reproducible.alioth.debian.org/debian/dpkg_1.18.1.0~reproducible5.dsc 
 with pbuilder on sid/armhf and that failed _exactly_ like 
 https://reproducible.debian.net/rbuild/unstable/amd64/dpkg_1.18.1.0~reproducible5.rbuild.log
 
 I then tried to build dpkg_1.18.1.dsc from sid proper and that built 
 flawlessly on sid/armhf.
 
 Thus I conclude our reproducible patches cause this, whatever this is. Yet I 
 lack time atm to debug this, so this mail is merely a note to Guillem and a 
 call for help to the reproducible folks.

Right, I noticed this quite some time ago, but forgot to bring it up.
W/o having checked anything, it might be that whoever prepared the
release perhaps forgot to «autoreconf -f -i» the sources and prepared
it from a previous .dsc instead of a git tree?

 I've now also added dpkg to the 
 https://reproducible.debian.net/issues/unstable/ftbfs_in_jenkins_setup_issue.html
  
 issues, which will make sure the ftbfs issue will soon (tomorrow, I think) 
 not 
 show up on https://tracker.debian.org/pkg/dpkg anymore.

Appreciated.

Thanks,
Guillem

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds