Peter Valdemar Morch wrote:
Hi there,
We have 100s of almost identical machines that need to be kept up-to-date with
apt-get dist-upgrade .
Having to run apt-get dist-upgrade manually on all of them is just not working
(taking too much man-power) due to having to answer the same Y/N debconf(?
On Sat, Apr 21, 2007 at 10:31:21AM +0200, "Peter Valdemar M?rch (vol)" wrote:
> Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote:
> >I use aptitude (this is not a troll, please), and I use it interactivly.
> >I have only those pacakges that I specifically _want_ installed marked
>
On Sat, Apr 21, 2007 at 10:31:21AM +0200, "Peter Valdemar Mørch (vol)" wrote:
> Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote:
> >I use aptitude (this is not a troll, please), and I use it interactivly.
> >I have only those pacakges that I specifically _want_ installed marked
>
On Sat, 21 Apr 2007 10:31:21 +0200
"Peter Valdemar Mørch (vol)" <[EMAIL PROTECTED]> wrote:
> Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote:
> > I use aptitude (this is not a troll, please), and I use it
> > interactivly. I have only those pacakges that I specifically _want_
>
Here goes this term "package breakage" again. Do you know what it is
and how it arises? Most of the time, dist-upgrade just decides to
install a couple of extra packages. But some other times... I just
never figured out what makes the difference and what the possible
problems and solutions
Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote:
I use aptitude (this is not a troll, please), and I use it interactivly.
I have only those pacakges that I specifically _want_ installed marked
as manual with everything else being automatic.
Aa! What is *THIS*? "manual" co
> """
> export aptopt=
> $ROOTCMD apt-get $aptopt -f -y dist-upgrade """
Sorry for the late reply.. been busy.
You know, you could always use apt-get -simulate dist-upgrade on your
machines. Check the output and leave a token somewhere that then allows the
machines to do the upgrade for real.
On Thu, Apr 19, 2007 at 03:55:06PM +0200, Peter Valdemar M?rch wrote:
> Ok, but what is the alternative? I find that without dist-upgrade, I end
> up with a constantly growing number of packages in the
> "The following packages have been kept back"
> category.
>
My 2 C worth. Preface: I've ne
On Thu, Apr 19, 2007 at 10:37:54AM -, Peter Valdemar Morch wrote:
> We have 100s of almost identical machines that need to be kept
> up-to-date with apt-get dist-upgrade .
>
> Having to run apt-get dist-upgrade manually on all of them is just not
> working (taking too much man-power) due to ha
Alex Samad wrote:
> If you have 100's of machines all in production or atleast all having to be
> kept to the same package setup.
>
> why not setup yor own repo (and extend it to your down release) could
> correspond to your SOE, when it comes time to update, go through the testing
> phase, once y
If you have 100's of machines all in production or atleast all having to be
kept to the same package setup.
why not setup yor own repo (and extend it to your down release) could
correspond to your SOE, when it comes time to update, go through the testing
phase, once your happy with all the new pac
Georgi Alexandrov wrote:
Too much is going on in testing, unstable and experimental but not in
the stable branch.
Mmm I'd say that having less package changes would be more reason to
monitor the process instead of just throwing it out there. :P From the
look of it there applications that wi
Daniel Palmer wrote:
> Peter Valdemar Mørch wrote:
>> Ok, but what is the alternative? I find that without dist-upgrade, I
>> end up with a constantly growing number of packages in the
>> "The following packages have been kept back"
>> category.
> Jamming dist-upgrade into a cron job will cause pro
Daniel Palmer daniel-at-cardboardbox.org.uk |volatile-lists| wrote:
Jamming dist-upgrade into a cron job will cause problems when a package
doesn't upgrade cleanly.. for example mysql is getting upgraded, the
server will stop and not come back up. Even worse if a kernel upgrade
doesn't create t
FAI works with standard debian kernels or require a special patched one ?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Peter Valdemar Mørch wrote:
Ok, but what is the alternative? I find that without dist-upgrade, I
end up with a constantly growing number of packages in the
"The following packages have been kept back"
category.
Jamming dist-upgrade into a cron job will cause problems when a package
doesn't upgr
Daniel Palmer daniel-at-cardboardbox.org.uk |volatile-lists| wrote:
Georgi Alexandrov wrote:
Or you can:
for i in `seq 10-150`; do ssh [EMAIL PROTECTED] apt-get update && apt-get
-y dist-upgrade &>/var/log/apt-upgrade.log; done
The automatic dist-upgrade is a bad idea in my opinion. Asking
Daniel Palmer wrote:
> Georgi Alexandrov wrote:
>> Or you can:
>> for i in `seq 10-150`; do ssh [EMAIL PROTECTED] apt-get update && apt-get
>> -y dist-upgrade &>/var/log/apt-upgrade.log; done
>>
>>
>
> The automatic dist-upgrade is a bad idea in my opinion. Asking for
> package breakage.
Depen
Georgi Alexandrov wrote:
Or you can:
for i in `seq 10-150`; do ssh [EMAIL PROTECTED] apt-get update && apt-get
-y dist-upgrade &>/var/log/apt-upgrade.log; done
The automatic dist-upgrade is a bad idea in my opinion. Asking for
package breakage.
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
cedric briner wrote:
> Peter Valdemar Morch wrote:
>> Hi there,
>>
>> We have 100s of almost identical machines that need to be kept
>> up-to-date with apt-get dist-upgrade .
> Okay, I'm not an expert but I'll go like this.
>>
>> Having to run apt-get dist-upgrade manually on all of them is just no
Peter Valdemar Morch wrote:
Hi there,
We have 100s of almost identical machines that need to be kept up-to-date with
apt-get dist-upgrade .
Okay, I'm not an expert but I'll go like this.
Having to run apt-get dist-upgrade manually on all of them is just not working
(taking too much man-powe
On Thu, Apr 19, 2007 at 10:37:54AM -, Peter Valdemar Morch wrote:
> Is there a smarter way? How does one manage many, many debian installations
> without having to give each one special manual treatment? Ideally I'd like
> this to be a fully automated operation and only be
> notified of any
Hi there,
We have 100s of almost identical machines that need to be kept up-to-date with
apt-get dist-upgrade .
Having to run apt-get dist-upgrade manually on all of them is just not working
(taking too much man-power) due to having to answer the same Y/N debconf(?)
questions over and over aga
23 matches
Mail list logo
