On Tuesday, November 26, 2024 3:42:39 PM MST Preuße, Hilmar wrote: > Am 19.11.2024 um 23:39 schrieb Hilmar Preuße: > > Hi, > > > > How do I have to name the additional tar balls? Putting the needed > > directory into the tar balls does not seem to do the trick. Currently my > > only idea is to merge the two tar balls into one and name it > > asy....orig-acextlibs.tar.xz . > > > > Hopefully(?) last question. I use gbp and master/upstream/pristine-tar > branch The source package now consists of three different orig.tar.xz > files. Where should I put the files into the repo? putting the two new > files into the existing pristine-tar branch probably doesn't make sense. > Should I simply two new branches and put them there? The file > d/README.source exists anyway. The following example with fonts-adobe-sourcesans3 might be helpful, even if it is a little different than your situation. I created the following MUT repository using `gbp import-dsc`: https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3 It put both tarballs in pristine-tar. Building a package with MUT from pristine-tar requires some extra info with the --git-component argument (which I believe can be specified multiple times). https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3/-/blob/master/ debian/README.Source?ref_type=heads#L49-75 I should note that I haven’t actually tried the `gbp import-orig` code path for importing a new release, as this font package hasn’t had a new release since I created it. It is based simply on reading the documentation (which I might have misunderstood). -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.