Am Freitag, den 06.11.2020, 18:05 +0100 schrieb Klaumi Klingsporn: > Am / On Fri, 06 Nov 2020 15:16:51 +0100 > schrieb / wrote Daniel Leidert <dleidert@debian.org>: > > > Praveen already gave you the advice. We use > > git-buildpackage (gbp) to build packages from the source. > > ... > > There is plenty of "learning by doing" here. Don't > > hesitate to ask whenever you stumble upon an issue. > > O.k., gbp (I had to install it first) opens a wide range of > new possibilities ;-) > > But meanwhile I followed Praveens advice, created the > missing branches manually with 'git checkout', downloaded > the latest upstream version with uscan and imported it with > gbp. It now has the tag upstream/3.0.6. > > Then I created a new changelog-entry with 'gbp dch -a', > made all my changes in the debian directory and documented > them in the changelog. Then I had to make git aware of a > new file: > git add ./debian/README.Debian > and committed all my changes to my local repo with > git commit -a. > > Now the questions: > > 1. > Do I set the tag 'debian/3.0.6' now? Or is it done when > releasing the package? It is done after finalizing debian/changelog and preparing the upload. gbp can do this automatically. Please don't add it just yet. Let us first check the result. > 2. > When exactly do I pull my changes to salsa.debian.org? Now? You packaged a major upstream version change (2.0 in Debian vs. 3.0 you packaged). Please don't push your changes to the main repository in such a case. Either (a) fork the repository on salsa into your own namespace (just push the fork button at https://salsa.debian.org/ruby-team/ruby-cmdparse and then choose your namespace) and then work on the fork or (b) create new branches. In either case you can then create merge requests with your changes. > Or should I build and test the package first (with this > meta-kit)? Definitely. At least build it. This won't affect the git repository. > Lucky for me according to reverse-depends there > doesn't seem to exist any reverse (build) dependency to > ruby-cmdparse. Luckily this is the case here. So feel free to push your changes to all three branches. I don't think you can do much harm here. > 3. > The maybe too late question: To get my personal package > built I had to remove the file .rb. I think > it's because there is no test suite in the upstream source > any more. I did the same here. Is this ok or is this file > somehow essential for the package? We want to have the tests. That's why we changed to using the github sources instead of the gem in many cases (debian/watch needs to be adjusted). For cmdparse the debian/watch file could look like this: version=4 opts=uversionmangle=s/[_.+-]?(rc|pre|dev|beta|alpha|b|a)/~$1/i,\ filenamemangle=s%(?:.+/)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2% \ https://github.com/gettalong/cmdparse/releases .*/v?@ANY_VERSION@@ARCHIVE_EXT@ Maybe you want to try this one out and re-import the upstream sources so we have the tests. > And more general: > 4. > I have no ~/.gbp.conf at all. Is there there something > usefull I should set there besides > > [pq] > > drop = true That really depends on your setup and the tools you need. If you want to have the tags signed you can add sign-tags = true keyid = <..key-ID...> into the [DEFAULT] section. You probably also want to define export-dir. Everything else really depends on your setup. For example I run gbp with pbuilder and autopkgtest by default: builder = pdebuild # builder = sbuild --arch-all --source --source-only-changes --verbose -d unstable # for sbuild postbuild = autopkgtest --user debci --apt-upgrade -s --output-dir="$GBP_BUILD_DIR/autopkgtest/u/" "$GBP_CHANGES_FILE" -- lxc --sudo autopkgtest-unstable-amd64 If you use the `build` script from the team repository you don't have to configure gbp much. The script is especially useful if you need to make sure that your upload won't break packages. > Thanks for your patience! It really seams to be "learning > by doing". Don't worry. Regards, Daniel -- Regards, Daniel Leidert <dleidert@debian.org> | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert
Attachment:
signature.asc
Description: This is a digitally signed message part