Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Hug <philipp@hug.cx>
To: Helmut Wollmersdorfer <helmut@wollmersdorfer.at>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: 0.7.6 release tomorrow...
Date: Wed, 24 Nov 2004 14:46:07 +0100	[thread overview]
Message-ID: <41A4909F.4070806@hug.cx> (raw)
In-Reply-To: <41A48BB0.4080707@wollmersdorfer.at>


> The convenient way is to do "make tarball" before "dpkg-buildpackage 
> ..." and "make-kpkg ...". And I never really understood the 
> module-assistant, even after nearly a day of studying the docs. Same 
> is true for the newer packaging stuff.

You can still do make-kpkg even with the new packaging: If it doesn't
work, it's a bug.

> So, what's easier:
>
> 1) change and test the drbd/make plus writing a new "HOWTO build 
> debian packages from SVN/tarball", and test the HOWTO under different 
> conditions.

well actually I could change the debian scripts to work directly within
the svn directory. that's probably easier than doing "make tarball" first.

> OR
>
> 2) rm debian/  by debian maintainers

sounds easier than it is: according to debian policy the upstream source
tgz must not be modified when uploaded to debian, instead a diff.gz is
upload that contains the diffs between upstream and debian release + it
normally contains the debian directory.
its not possible for the debian packager to remove files from the
original tgz not even in the diffs. you could call this a bug in the
dpkg-buildpackage tool but that's the way it is now.

2nd: if an upstream package already contains a debian directory is
called a "native-debian" package and the version number should be e.g.
0.7.6 (without -debianversion). but the problem here would be, that the
drbd release must be the version that goes into debian.org and that's
not the case here...

so I think that removing ./debian at least from the release tarball
would be a good idea... maybe we could add a "make releasetarball" target...

philipp


  reply	other threads:[~2004-11-24 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 21:59 [Drbd-dev] 0.7.6 release tomorrow Philipp Reisner
2004-11-16 13:22 ` Philipp Hug
2004-11-16 14:12 ` Philipp Reisner
2004-11-17 19:32 ` Philipp Reisner
2004-11-18  7:16   ` Lars Ellenberg
2004-11-19 12:52 ` [Drbd-dev] " Cyril Bouthors
2004-11-19 14:12   ` Philipp Reisner
2004-11-22  7:59     ` Cyril Bouthors
2004-11-24 13:25       ` Helmut Wollmersdorfer
2004-11-24 13:46         ` Philipp Hug [this message]
2004-11-24 14:18           ` Philipp Reisner
2004-11-24 15:04             ` Philipp Hug
2004-11-24 22:21               ` Lars Ellenberg
2004-11-24 23:40                 ` Philipp Hug
2004-11-25  0:57                   ` Lars Ellenberg
2004-11-25  7:46                     ` Cyril Bouthors
2004-11-19 15:39   ` Helmut Wollmersdorfer

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=41A4909F.4070806@hug.cx \
    --to=philipp@hug.cx \
    --cc=drbd-dev@lists.linbit.com \
    --cc=helmut@wollmersdorfer.at \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox