1. 01 Mar, 2018 2 commits
  2. 26 Feb, 2018 3 commits
  3. 29 Jan, 2018 3 commits
    • Guido Günther's avatar
      Turn on several threads when creating xz/lzma tarballs · fd81e454
      Guido Günther authored
      and not using pristine-tar.
      
      Gives a 50% speedup on my machine:
      
      $ time gbp export-orig --no-pristine-tar --force-create
      gbp:info: Creating thunderbird_52.6.0.orig.tar.xz from 'upstream/52.6.0'
      gbp:info: Creating additional tarball 'thunderbird_52.6.0.orig-thunderbird-l10n.tar.xz' from 'dea43c2b49f11d68f05edac2bd9d6c5d1e1f4bcb'
      gbp:info: Creating additional tarball 'thunderbird_52.6.0.orig-lightning-l10n.tar.xz' from '9adcd261726ccb160c4fd6947f7cbfe9df2e581b'
      
      real	8m27,153s
      user	7m23,717s
      sys	0m3,015s
      
      0|agx@bogon:/var/scratch/debian/icedove/icedove (debian/wheezy)$ time gbp-from-sourcetree export-orig --no-pristine-tar --force-create
      gbp:info: Creating thunderbird_52.6.0.orig.tar.xz from 'upstream/52.6.0'
      gbp:info: Creating additional tarball 'thunderbird_52.6.0.orig-thunderbird-l10n.tar.xz' from 'dea43c2b49f11d68f05edac2bd9d6c5d1e1f4bcb'
      gbp:info: Creating additional tarball 'thunderbird_52.6.0.orig-lightning-l10n.tar.xz' from '9adcd261726ccb160c4fd6947f7cbfe9df2e581b'
      
      real	4m3,080s
      user	11m18,733s
      sys	0m3,499s
      
      Thanks: Carsten Schönert for the suggestion
      Closes: #888572
      fd81e454
    • Guido Günther's avatar
      gbplogtaster: capture INFO and DEBUG log levels too · 5f2120b3
      Guido Günther authored
      This allows to test for certain features more easily and to
      use it not only in the error case.
      
      Using two different streams allows us to test that messages still
      end up on stderr or stdout correctly.
      5f2120b3
    • Markus Lehtonen's avatar
      buildpackage-rpm: support setting the 'VCS:' tag in spec · 393edba3
      Markus Lehtonen authored
      Now gbp buildpackage-rpm is able to update the 'VCS:' tag in the exported
      spec file. A new config option 'spec-vcs-tag' controls the format:
      - if empty, no 'VCS' tag is inserted and possible old 'VCS' tag is
        removed
      - otherwise, a 'VCS' tag is inserted or the old 'VCS' tag is updated
      
      The spec-vcs-tag is a format string which supports the following
      keywords:
      - '%(commit)' expands to the full commit sha1
      - '%(commitish)' expands to the sha1 of the exported object (commit or
         tag)
      - '%(tagname)s' expands to the long tag name (from git-describe)
      Signed-off-by: 's avatarMarkus Lehtonen <markus.lehtonen@linux.intel.com>
      393edba3
  4. 23 Jan, 2018 2 commits
  5. 22 Jan, 2018 3 commits
  6. 20 Jan, 2018 1 commit
  7. 19 Jan, 2018 1 commit
  8. 18 Jan, 2018 1 commit
  9. 17 Jan, 2018 1 commit
  10. 12 Jan, 2018 2 commits
  11. 31 Dec, 2017 1 commit
  12. 24 Dec, 2017 1 commit
    • Maximiliano Curia's avatar
      pq: Parse DEP3 headers · 17a471d1
      Maximiliano Curia authored
      Currently the patch headers in DEP3 format are partially
      supported, as git's mailinfo only reads the From and Subject fields from
      the first paragraph. But the default in dep3 patches is Description and
      Author, that are ignored by git. Even worse, when this fields are in the
      first paragraph (again the default) git mailinfo drops all the contained
      information.
      
      This patch parses the dep3 headers if git's mailinfo couldn't obtain any
      useful information, any header other than Subject|Description and
      Author|From is appended to the patch message.
      
      The description field is splitted in first line for the short
      description and the rest is prepended to the patch message.
      
      Closes: #785274
      17a471d1
  13. 16 Dec, 2017 1 commit
  14. 28 Nov, 2017 1 commit
  15. 27 Nov, 2017 5 commits
  16. 23 Nov, 2017 1 commit
  17. 16 Nov, 2017 2 commits
  18. 13 Nov, 2017 1 commit
  19. 12 Nov, 2017 6 commits
  20. 10 Nov, 2017 1 commit
  21. 09 Nov, 2017 1 commit