All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Nathan Scott <nathans@debian.org>
Cc: Andrew Dahl <adahl@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/4] Refactor release scripts to conform to using git archive
Date: Thu, 14 Feb 2013 16:37:31 -0600	[thread overview]
Message-ID: <20130214223731.GJ22182@sgi.com> (raw)
In-Reply-To: <322172909.3042470.1360880747978.JavaMail.root@redhat.com>

On Thu, Feb 14, 2013 at 05:25:47PM -0500, Nathan Scott wrote:
> ----- Original Message -----
> > ...
> > 'make deb' failed for me like this:
> > 
> > signfile xfsprogs_3.1.9.dsc
> > gpg: skipped "Nathan Scott <nathans@debian.org>": secret key not
> > available
> > gpg: [stdin]: clearsign failed: secret key not available
> > 
> > dpkg-genchanges  >../xfsprogs_3.1.9_amd64.changes
> > dpkg-genchanges: including full source code in upload
> > dpkg-buildpackage: full upload; Debian-native package (full source is
> > included)
> > dpkg-buildpackage: warning: Failed to sign .dsc and .changes file
> > make: *** [deb] Error 1
> > 
> > Secure-by-default is a great idea but it seems that in this case it
> > also
> > requires that anyone who wants to do a build for debian has to do it
> > on a
> > machine with a keyring containing your secret key. ;)
> > 
> 
> Awkward.  :)

Really I don't mind.  What was your passphrase again? 

> > I think it is also reasonable for devs to be able to build test debs
> 
> *nod* ... not sure what trickery Dave had used.

I tried setting DEB_BUILD_OPTIONS="-us -uc" but no luck.

> But, perhaps a better
> way to tackle this would be similar to the way the build allows extra
> configure options to be passed in.

> 
> include/builddefs: configure
>         ./configure $$LOCAL_CONFIGURE_OPTIONS
> 
> so, perhaps something like this...
> 
> # LOCAL_BUILDPACKAGE_OPTIONS="-us -uc" for unsigned debs
> deb: include/builddefs include/platform_defs.h
> ...
>         $(Q)cd $(SRCDIR) && dpkg-buildpackage $$LOCAL_BUILDPACKAGE_OPTIONS

Gotcha.  I'll take a look.  Thanks for the reviews!

-Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-02-14 22:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50F44B2E.9050408@sgi.com>
     [not found] ` <50F44B62.7060504@sgi.com>
2013-02-01  2:10   ` [PATCH 1/4] xfsprogs: Refactor release scripts to conform to using git archive Ben Myers
     [not found] ` <50F44B87.3040102@sgi.com>
2013-02-01  2:36   ` [PATCH 2/4] xfsdump: " Ben Myers
     [not found] ` <50F44BA5.9030509@sgi.com>
2013-02-01  2:55   ` [PATCH 3/4] xfstests: " Ben Myers
     [not found] ` <50F44BC0.80708@sgi.com>
2013-02-01 16:47   ` [PATCH 4/4] dmapi: " Ben Myers
2013-02-01 19:09 ` [PATCH 0/4] " Ben Myers
2013-02-06  1:15   ` Dave Chinner
2013-02-06  6:28     ` Nathan Scott
2013-02-06 19:31       ` [PATCH 0/4] Refactor release scripts to conform to using git?archive Ben Myers
2013-02-06 22:47       ` Dave Chinner
2013-02-14  1:08     ` [PATCH 0/4] Refactor release scripts to conform to using git archive Ben Myers
2013-02-14  2:14       ` Nathan Scott
2013-02-14 16:24         ` Ben Myers
2013-02-14 16:54           ` xfsprogs: update 'make deb' to use tarball Ben Myers
2013-02-14 22:26             ` Nathan Scott
2013-02-14 22:50             ` Dave Chinner
2013-02-14 17:31           ` xfsdump: update 'make deb' to use tarball archive Ben Myers
2013-02-14 22:27             ` Nathan Scott
2013-02-14 22:51             ` Dave Chinner
2013-02-14 22:25           ` [PATCH 0/4] Refactor release scripts to conform to using git archive Nathan Scott
2013-02-14 22:37             ` Ben Myers [this message]
2013-02-14 22:36           ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130214223731.GJ22182@sgi.com \
    --to=bpm@sgi.com \
    --cc=adahl@sgi.com \
    --cc=nathans@debian.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.