** Also affects: sbuild (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: sbuild (Ubuntu Trusty)
       Status: New => Triaged

** Changed in: sbuild (Ubuntu Trusty)
   Importance: Undecided => High

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  not possible to build yakkety packages because of gpg changes

Status in sbuild package in Ubuntu:
Status in sbuild source package in Trusty:
Status in sbuild source package in Xenial:
Status in sbuild package in Debian:
  Fix Released

Bug description:
  I was trying to build update-manager in a yakkety sbuild chroot from a
  xenial system and encountered the following error:

  Local sources

  update-manager_16.10.5.dsc exists in .; copying to chroot

  Check architectures

  Check dependencies

  Merged Build-Depends: build-essential, fakeroot
  Filtered Build-Depends: build-essential, fakeroot
  dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
  gpg: /<<BUILDDIR>>/resolver-9lYerC/gpg/trustdb.gpg: trustdb created
  gpg: Warning: not using 'Sbuild Signer' as default key: No secret key
  gpg: all values passed to '--default-key' ignored
  gpg: no default secret key: No secret key
  gpg: signing failed: No secret key
  Failed to sign dummy archive Release file.

  I worked around the issue by installing the yakkety version of sbuild
  on my xenial system, but the fix should be backported.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to