From: Alexander Opitz <opitz@primacom.net>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] 0.7.5 debian stuff
Date: Thu, 7 Oct 2004 00:36:06 +0200 [thread overview]
Message-ID: <200410070036.06736.opitz@primacom.net> (raw)
Hi,
> 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?
The conflict is correct.
If you update the drbd package to a newer 0.6.x version, the drbd package is
updated and still conflicts with drbd0.7 ... but if you do not have drbd0.7
installed, then you see the newer drbd package from the 0.6 series.
You also can update the drbd0.7 package to a newer version with this conflict
to drbd, the conflict doesn't stop the debian upload process, it only helps
the user to do not make stupid installations.
My first thought was: "And for note, a debian package can't named drbd0.7
(with point) ... the normal way for such transitions is to add the next
higher number to the end of package name ... so you have then drbd (old name)
and drbd1 (new name)."
but as you can see for the libswig package a point in name is possible:
http://packages.debian.org/cgi-bin/search_packages.pl?version=all&subword=1&exact=&arch=any&releases=all&case=insensitive&keywords=libswig&searchon=names
It have likely same conflict/update setup.
Greetings Alex//
next reply other threads:[~2004-10-06 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 22:36 Alexander Opitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-04 14:30 [Drbd-dev] 0.7.5 debian stuff David Krovich
2004-10-05 20:37 ` Philipp Hug
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=200410070036.06736.opitz@primacom.net \
--to=opitz@primacom.net \
--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.