| micdud | trying to figure out proper packaging with gbp but get stuck in 2 places , 1: upstream does not use any tags ( can i just tag the upstream branch myself , or will that screw up later updates from upstream?) 2: how do i get gbp to make orig.tar.gz by itself ( so far i have been using one made by dh_make ) | 11:23 |
|---|---|---|
| LeePen | micdud: yes, tag yourself. Once the tag is there gbp will build the orig tarball. | 11:25 |
| micdud | and later pull/merge remote/upstream branch will not erase them ? | 11:26 |
| LeePen | Not unless you specifically ask. | 11:27 |
| micdud | thanx | 11:27 |
| micdud | this is missing in docs everywhere , they all assume upstream always tags | 11:27 |
| LeePen | See --prune and --pruen-tags in git-pull(1). | 11:28 |
| micdud | still get same errors after tagging upstream . 1:(gbp:info: Tarballs 'package_00.01.01.orig.tar.gz' not found at '../') 2:(gbp:error: upstream/00.01.01 is not a valid treeish) | 12:44 |
| LeePen | Have you created the tag upstream/00.01.01? | 13:16 |
| micdud | just figured it out i was just tagging 00.01.01 | 13:20 |
| micdud | thanx | 13:21 |
| micdud | can i call gbp to make orig.tar.gz and deb-source without building the first incomplete package so i can commit extra changes and then build a full package | 16:18 |
| LeePen | Call gbp with '--git-builder=true' | 16:20 |
| micdud | last question(today) with gbp worklow i should not touch dpkg-source --commit , and do everything with gbp pq and keep it on patch-queue branch? | 16:55 |
| LeePen | This is personal choice. I have never used gbp pq. I usually just use quilt import on the patch file created with git-format-patch. | 17:26 |
| LeePen | But there are lots of ways to do it. | 17:26 |
| bgstack15 | Devuan meet tomorrow May 12, at 20:30 UTC. Pad is here: https://pad.dyne.org/code/#/2/code/edit/naDR+yY4PkHBWkLvCXBOBdDp/ | 17:32 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!