public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sevo Stille <sevo@radiox.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Frozen Bacula??
Date: Wed, 23 Nov 2005 21:50:08 +0100	[thread overview]
Message-ID: <4384D600.6030904@radiox.de> (raw)
In-Reply-To: <43824772.4326f7ef.2661.3317@mx.gmail.com>

Chris Lee wrote:

> As for 1.38.[01], I will have it committed
> to portage when I have some time in the near future, but please be aware
> that it will spend some time in ~arch just like every other pacakge.

Better start out with a hard masked package at least for some time! The 
implications of the (IMHO horrible) upstream failure of maintaining 
downward compatibility on a distributed application will inevitably hit 
somebody hard, if we do not prevent emerge -u world from switching one 
Bacula client or server to 1.38 without taking care of the others...

Probably the only thing we could do about it (as slotting is as 
impracticable as a network-wide forced upgrade) would be to install 
1.38.x to a temporary path, and provide a script to switch it alive 
manually, to be sure the admins in question have at any rate noticed 
that they may just be cutting their clients off from the backup system. 
If you are willing to go that way, I'd lend a hand.

Sevo
-- 
gentoo-dev@gentoo.org mailing list



      parent reply	other threads:[~2005-11-23 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 13:22 [gentoo-dev] Frozen Bacula?? Herbert G. Fischer
2005-11-21 13:33 ` Jakub Moc
2005-11-21 22:17 ` Chris Lee
2005-11-22 11:50   ` Herbert G. Fischer
2005-11-23 20:50   ` Sevo Stille [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=4384D600.6030904@radiox.de \
    --to=sevo@radiox.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /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