[buildd-tools-devel] Bug#477696: [Buildd-tools-devel] Bug#477696: Bug#477696: ability to not rebuild source but add it to the changes file

[Roger Leigh]

On Tue, Apr 29, 2008 at 02:16:46PM +0200, martin f krafft wrote:
> also sprach Roger Leigh <rleigh at whinlatter.ukfsn.org> [2008.04.27.1958 +0200]:
> > I'm not quite clear on exactly you want to do here.  Could you
> > perhaps provide an example to give me a bit more detail?
> 
> Well, I feed sbuild a source package and it then rebuilds the source
> package. This means I have to resign the source package. Instead, it
> could just not build the source package, but still create a changes
> file encompassing both, the generated binary packages as well as the
> source package used to build them.
> 
> Right now I am using [0] to achieve what I want.
> 
> 0. http://git.madduck.net/v/code/mbuild.git?a=blob;f=mbuild.sh

Hi Martin,

I'm sorry for the long delay in getting back to this (PhD taking up
my time).

I'm still not really sure about what you really want to do here, and
why.  A few questions:

- why do you need to *re*-sign the source package

  If it's not already been uploaded to Debian, why is the source
  package signed separately?

  Since you have to sign the changes for upload, I can't see the
  need to "pre-sign" the .dsc prior to building the sbuild.

- If the sources are already available in Debian, can't you just
  omit the "-s" option and do a binary-only upload?

- If you're building a .dsc directly, are there any options we
  can pass to dpkg-buildpackage to prevent rebuilding of the
  source package, but still include it in the .changes?

  Note that sbuild relies entirely upon dpkg-buildpackage to do all
  this, so any changes need to be in how we run it.

Note that the sbuild in unstable can now build directly from a source
tree, saving the need to build without sbuild, and then build with
sbuild.  It just packs up the source with dpkg-source and builds that.
If this was part of the problem, it might be of help.

I'm basically still stuck on the "big picture" of your overall
workflow which is requiring you to jump through these additional
hoops.  A complete description of the process, with rationale of
why you are doing things, would help a lot!


Many thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20101120/0b1e97da/attachment.pgp>