> this is business as usual, and the reason why we import tarballs into > pristine-tar. in addition, gbp even requires a dedicated tarball import > commit for some reason.
Good to know, thanks. > master is now up2date with the 12.2.1 release (tarball). it seems to > build, but not on all machines. (i only have random systems, no proper > buildbot yet). Sandia has quite a particular range of machines they support. For example, 32-bit-builds (x86) are _not_ supported. Perhaps that explains your failures. --Nico On Sat, Sep 19, 2015 at 8:13 PM Felix Salfelder <[email protected]> wrote: > On Sat, Sep 19, 2015 at 06:00:33PM +0000, Nico Schlömer wrote: > > As I said, however, the git-archive of that commit dow _not_ coincide > with > > what Sandia distributes as their 12.2.1 tarball. > > this is business as usual, and the reason why we import tarballs into > pristine-tar. in addition, gbp even requires a dedicated tarball import > commit for some reason. > > > For example, the > > git-archive [1] is 212 MB large, the official tarball [2] only 110 MB. > This > > is because some testing files are removed from the tarball. Possibly > there > > are other changes as well. > > master is now up2date with the 12.2.1 release (tarball). it seems to > build, but not on all machines. (i only have random systems, no proper > buildbot yet). > > cheers > felix >
