From: Philipp Hug <philipp@hug.cx>
To: drbd-dev@lists.linbit.com
Cc: David Krovich <dkrovich@csee.wvu.edu>, 244291@bugs.debian.org
Subject: Re: [Drbd-dev] 0.7.5 debian stuff
Date: Tue, 5 Oct 2004 22:37:50 +0200 [thread overview]
Message-ID: <200410052237.50672.philipp@hug.cx> (raw)
In-Reply-To: <41615E9A.5070203@csee.wvu.edu>
On Monday 04 October 2004 16.30, David Krovich wrote:
> Have the drbd source package create 2 binary packages, one named
> drbd-utils and one named drbd-modules-source. I think those would be
> much cleaner names for the binary packages.
>
agreed... I'll change them
> I like the fact that drbd0.7 conflicts drbd << 0.7, but do we think
> 0.6.x is no longer being used? If we upload this package into debian,
> how would we ever be able to upload a newer version of the 0.6.x series?
actually, I thought we'd put drbd0.6 into sarge and drbd0.7 into unstable/sid.
but if you want to have both in sid, you'd need two different source packages.
does it really make sense to keep 0.6 in unstable as upstream isn't working on
it anymore and has already started the 0.8 branch...?
(or am I wrong here?)
in my opinion, the only reason for having 0.6 packages is to make sure that
existing 0.6 users don't get automatically upgraded to 0.7.
so, what we have to do is: rename the current packages to drbd0.6 and put them
into sarge...
then we can start uploading the drbd0.7 version to unstable...
philipp
next prev parent reply other threads:[~2004-10-05 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 14:30 [Drbd-dev] 0.7.5 debian stuff David Krovich
2004-10-05 20:37 ` Philipp Hug [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 22:36 Alexander Opitz
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=200410052237.50672.philipp@hug.cx \
--to=philipp@hug.cx \
--cc=244291@bugs.debian.org \
--cc=dkrovich@csee.wvu.edu \
--cc=drbd-dev@lists.linbit.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.