From: Lars Marowsky-Bree <lmb@suse.de>
To: Philipp Reisner <philipp.reisner@linbit.com>, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: [john.cagle@hp.com: FW: device number request for drbd]
Date: Thu, 19 Aug 2004 12:32:21 +0200 [thread overview]
Message-ID: <20040819103221.GM9601@marowsky-bree.de> (raw)
In-Reply-To: <200408191115.42139.philipp.reisner@linbit.com>
On 2004-08-19T11:15:41,
Philipp Reisner <philipp.reisner@linbit.com> said:
> I will look into it, probabely it is easy to do... [I can not remeber
> what we changed there...]
I'm also sweet-talking our maintenance crew because I really want to
avoid that ;-)
> BTW: I thought that RPMs have dependencies too. Why is it not possible
> to express something like
>
> km_drbd-0.7.1 requires >= drbd-0.7.1 (user-package)
>
> in the dependencies of the kernel module package...
Because YaST2 Online Update does not evaluate these dependencies.
("Updates are not allowed to change package dependencies in a stable
product.")
So, I'm not happy with either the change in drbd nor our online update
system - either one on it's own would be fine, but the combination
thereof is somewhat annoying ;-)
But, there's hope, I think. I'll try to weasle out of that policy. I can
be really good with weasel words. ;)
(I also don't think any drbd using customer would only update the
kernel, but not drbd, or update drbd user-space but not the kernel.
I claim that's a somewhat ridiculous policy in this case...)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ This space /
SUSE Labs, Research and Development | intentionally |
SUSE LINUX AG - A Novell company \ left blank /
prev parent reply other threads:[~2004-08-19 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040728080645.GB7918@tmathiasen>
2004-07-28 10:10 ` [Drbd-dev] Re: [john.cagle@hp.com: FW: device number request for drbd] Philipp Reisner
2004-07-28 10:58 ` Lars Ellenberg
2004-07-28 12:08 ` Philipp Reisner
2004-07-28 12:17 ` Lars Ellenberg
2004-07-28 12:40 ` Philipp Reisner
2004-07-28 14:12 ` Lars Marowsky-Bree
2004-07-28 14:55 ` Philipp Reisner
2004-07-28 15:33 ` Lars Marowsky-Bree
2004-07-28 15:46 ` Lars Ellenberg
2004-07-28 17:56 ` Philipp Reisner
2004-07-28 18:45 ` Lars Ellenberg
2004-07-29 22:32 ` Lars Marowsky-Bree
2004-07-30 9:56 ` Philipp Reisner
2004-07-30 11:32 ` Philipp Reisner
2004-07-30 12:14 ` Lars Ellenberg
2004-07-30 12:29 ` Philipp Reisner
2004-08-18 18:42 ` Lars Marowsky-Bree
2004-08-18 19:31 ` Philipp Reisner
2004-08-18 22:57 ` Lars Marowsky-Bree
2004-08-19 9:15 ` Philipp Reisner
2004-08-19 10:32 ` Lars Marowsky-Bree [this message]
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=20040819103221.GM9601@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.com \
--cc=philipp.reisner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox