Now I want to import a new upstream version.<br></div><div>Upstream now provides a lz file and signs this lz.<br><br></div><div>When I try to import using:<br>gbp import-orig ../bruteforce-luks-1.4.0.tar.lz<br></div><div>or<br>gbp import-orig url-for-same-file<br><br></div><div>gbp is creating a tar.gz and I have a problem with the signature.<br><br></div><div>How is the right way to solve this problem?<br><br></div><div>Thanks.<br></div><div>[]'s</div><div>kretcheu</div><div>:x</div><div><br></
<div><br></div><div><br></div><div><br></div></div>
Hi,You can't have an orig.tar.lz in any case, this is not related to gbp or
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?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 61:41:39 |
Calls: | 6,654 |
Files: | 12,200 |
Messages: | 5,331,534 |