Hi Guillem,
thanks for the quick answer.
> I think this is just git being missing in that chroot. And I see the
No, even with git it breaks the same way. But what I did is
# in the git repo
gbp buildpackage -us -uc -rfakeroot -S
# then
cowbuilder --build --buildre
On Mon, 2020-06-29 at 10:27:51 +0900, Norbert Preining wrote:
> > I assume you have the key found in the upstream/signing-key.asc in
> > your keyring,
>
> No, I don't have it. Is this a (new?) requirement?
No, was just a wild guess in case gpg was getting confused by seeing a
missing private key
Hi Guillem,
> I think this might have been fixed in git already (with the changes to
Sounds great!
> I assume you have the key found in the upstream/signing-key.asc in
> your keyring,
No, I don't have it. Is this a (new?) requirement?
> perhaps that's even your private key?
No, it is upstream
Hi!
On Mon, 2020-06-29 at 09:19:18 +0900, Norbert Preining wrote:
> Package: libdpkg-perl
> Version: 1.20.2
> Severity: serious
> Justification: breaks unrelated packages
> it seems that the bump to 1.20 changed the behaviour of building
> packages, i.e., dpkg-source -b . doesn't work anymore, ou
Package: libdpkg-perl
Version: 1.20.2
Severity: serious
Justification: breaks unrelated packages
Hi,
it seems that the bump to 1.20 changed the behaviour of building
packages, i.e., dpkg-source -b . doesn't work anymore, out of the blue,
due to signature/key import errors:
$ dpkg-source -b .
dpk
5 matches
Mail list logo
