On Fri, Oct 22, 2021 at 08:14:34AM -0300, kretcheu wrote: > Hi, > > I`m working on one of my packages and I had problems. > > First I did run: > > gbp import-dscs --debsnap bruteforce-luks > > Everything works well. > > Now I want to import a new upstream version. > Upstream now provides a lz file and signs this lz. > > When I try to import using: > gbp import-orig ../bruteforce-luks-1.4.0.tar.lz > or > gbp import-orig url-for-same-file > > gbp is creating a tar.gz and I have a problem with the signature. > > How is the right way to solve this problem? You can't have an orig.tar.lz in any case, this is not related to gbp or sigs, the only think you should do is to ask the tools to repack it to .xz, not to .gz. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature