Upgrade Woody vers Sarge[pour info]

2005-11-06 Thread François Boisson
Première fois que j'ai un souci danbs une mise à jour. Une mise à jour
d'un serveur de woody vers Sarge (en fait une mise à jour d'un
réplique, j'aime savoir où je vais). Un apt-get avec un source.list
vers sarge renvoyait systématiquement des erreurs (Conflits en
pagaille), même une suppression d'un eptit paquet mettait la pagaille.
Je ne m'en suis sorti qu'en récupérant les paquets d'un debootstart
sarge et en les installant via dpkg (5 ou 6 fois de suite dpkg -i
*.deb). A l'issue de cela, désinstallation et réinstallation de apt,
suppression via dpkg de tasksel et enfin 2 ou 3 apt-get upgrade suivi
de apt-get -f install ont fini de remettre la machine (ou du moins son
clone) sur pied.

Je n'ai pas à me plaindre, ce serveur comporte une série de backports
(clamav essentiellement, mais aussi dosemu) ce qui fait que c'était
plutôt un mixte woody/sarge mais tout de même, comportement étonnant.

François Boisson


-- 
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Upgrade Woody vers Sarge[pour info]

2005-11-06 Thread Jerome Guery
Bonsoir,

J'avais aussi rencontré quelques petits problèmes lors d'un passage de
woody+backports vers sarge par simple modification du source.list
suivi d'un apt-get dist-upgrade.

J'étais très vite tombé sur
http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-upgrading_other
et la commande, magique pour mon cas:

aptitude -f --with-recommends dist-upgrade

qui avait solutionné tous mes problèmes (heureusement pour moi, je
n'avais pas eu la sagesse de tester sur une réplique :o).

Mais peut-être votre cas est-il différent.

Jerome Guery

Le Sun, Nov 06, 2005 at 05:23:20PM +0100, François Boisson écrivait:
 Première fois que j'ai un souci danbs une mise à jour. Une mise à jour
 d'un serveur de woody vers Sarge (en fait une mise à jour d'un
 réplique, j'aime savoir où je vais). Un apt-get avec un source.list
 vers sarge renvoyait systématiquement des erreurs (Conflits en
 pagaille), même une suppression d'un eptit paquet mettait la pagaille.
 Je ne m'en suis sorti qu'en récupérant les paquets d'un debootstart
 sarge et en les installant via dpkg (5 ou 6 fois de suite dpkg -i
 *.deb). A l'issue de cela, désinstallation et réinstallation de apt,
 suppression via dpkg de tasksel et enfin 2 ou 3 apt-get upgrade suivi
 de apt-get -f install ont fini de remettre la machine (ou du moins son
 clone) sur pied.
 
 Je n'ai pas à me plaindre, ce serveur comporte une série de backports
 (clamav essentiellement, mais aussi dosemu) ce qui fait que c'était
 plutôt un mixte woody/sarge mais tout de même, comportement étonnant.
 
 François Boisson
 
 
 -- 
 Pensez à lire la FAQ de la liste avant de poser une question :
 http://wiki.debian.net/?DebianFrench
 
 Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To:
 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 


-- 
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



upgrade woody vers sarge (dpkg: parse error, in file `/var/lib/dpkg/available)

2005-07-26 Thread Jean-Jacques
Bonjour à tous !

Je viens d'essayer de faire l'upgrade de woody vers Sarge.
mon sources.list est composé des élèments suivants:

deb ftp://sunsite.cnlab-switch.ch/mirror/debian/ stable main non-free
contrib
deb-src ftp://sunsite.cnlab-switch.ch/mirror/debian/ stable main
non-free contrib
deb http://non-us.debian.org/debian-non-US stable/non-US main contrib
non-free
deb-src http://non-us.debian.org/debian-non-US stable/non-US main
contrib non-free
deb http://security.debian.org/ stable/updates main contrib non-free

je commence par faire un apt-get update (jusqu'ici aucuns problèmes)
puis je tente le apt-get dist-upgrade et voici le message d'erreur que
j'obtiens:


The following packages will be REMOVED:
  abiword abiword-common abiword-gtk analog apache apache-common
apache-dev ark autoconf autoconf2.13 automake
  awstats blt bonobo console-tools-libs defoma docbook-xml dpkg-dev gdm
gimp-python gmc gnome-applets
  gnome-control-center gnome-core gnome-help gnome-panel
gnome-panel-data gnome-session gnome-terminal
  gnome-users-guide gnome-utils gs gs-common gsfonts gsfonts-x11 idle
idle-python2.1 kab karm kate kcalc
  kcharselect kchart kcoloredit kcron kde kdebase kdebase-audiolibs
kdebase-libs kdelibs3 kdelibs3-bin kdepasswd
  kdepim-libs kdf kdict kdm kedit kfind kformula kfract kghostview
khexedit kiconedit kit kivio kjots kmail
  knewsticker knode knotes koffice koffice-libs konqueror konsole
kontour korganizer korn koshell kpackage kpaint
  kpm kpresenter kruler kscreensaver ksirc ksnapshot kspread ksysv
ktimer kugar kuser kview kword language-env
  libapache-configfile-perl libapache-dbilogconfig-perl
libapache-mod-auth-shadow libapache-mod-dav
  libapache-mod-proxy-add-forward libapache-mod-python
libapache-mod-ruby libapache-mod-speedycgi
  libapache-mod-witch libapache-session-perl libapache-stage-perl
libarts libauthen-pam-perl libauthen-smb-perl
  libconvert-asn1-perl libdb2-dev libdbd-mysql-perl libdbi-perl
libdevel-symdump-perl libdigest-md5-perl libfam0
  libgnomeprint-data libgnomeprint15 libgtkhtml20 libhtml-parser-perl
libhtml-simpleparse-perl
  libhtml-tagset-perl libhtml-tree-perl libkdenetwork1 libkmid libkonq3
liblcms libmime-base64-perl libmimelib1
  libmldbm-perl libmldbm-sync-perl libnet-ldap-perl libnet-perl
libnet-ssleay-perl libsafe-hole-perl
  libsql-statement-perl libstorable-perl libtimedate-perl liburi-perl
libvorbis0 libwww-perl mailx mc-common
  mozilla mozilla-browser mozilla-mailnews mozilla-psm mysql-client
mysql-server nethack nethack-common
  nethack-x11 perl perl-modules php4 php4-gd php4-mysql proftpd
proftpd-common psfontmgr python-bobo
  python-bobopos python-gdk-imlib python-glade python-gnome python-gtk
python-imaging-tk python-pmw python-tk
  python2.1-imaging-tk python2.1-tk rpm sawfish-gnome scrollkeeper
secpolicy sendmail sgml-base sgml-data
  spamassassin speedy-cgi-perl webmin webmin-mysql x-window-system
x-window-system-core xbase-clients xdm xtel
The following NEW packages will be installed:
  apache2-utils coreutils cpp-3.3 cvs debconf-i18n debconf-utils
desktop-base desktop-file-utils dirmngr
  dosfstools dselect e2fslibs edict enscript g++-3.3 gcc-3.3
gcc-3.3-base gettext gnome-desktop-data
  gnome-icon-theme gnupg-agent gnupg2 gpgsm gstreamer0.8-oss
hicolor-icon-theme html2text imagemagick imlib11
  initscripts kanjidic kdeartwork-misc kdeartwork-theme-icon
kdebase-data kdeedu-data kdegames-card-data
  kdelibs-data kivio-data klettres-data kstars-data ksysguardd libacl1
libapache-ruby1.8 libapm1 libapr0
  libart-2.0-2 libartsc0 libasound2 libatk1.0-0 libattr1 libblkid1
libbonobo2-0 libbonobo2-common
  libbonoboui2-common libboost-python1.32.0 libc-client2002edebian
libcomerr2 libconsole libcroco3
  libcupsys2-gnutls10 libcurl3 libdb1-compat libdb4.1 libdb4.2 libdb4.2
++ libdb4.2-dev libdevmapper1.01 libdns16
  libeel2-data libexif10 libfam0c102 libflac6 libfribidi0 libgadu3
libgcrypt11 libgd1-noxpm libgdbm3 libgle3
  libglib2.0-0 libgnomecanvas2-common libgnomecups1.0-1
libgnomeprint2.2-data libgnomeprintui2.2-common
  libgnomeui-common libgnutls11 libgpg-error0 libgpgme11 libgphoto2-2
libgphoto2-port0 libgsf-1
  libgstreamer-plugins0.8-0 libgstreamer0.8-0 libgtksourceview-common
libgtop2-2 libidl0 libidn11 libieee1284-3
  libisc7 libiw27 libjack0.80.0-0 libjasper-1.701-1 libjpeg-progs
libksba8 liblcms1 liblocale-gettext-perl
  liblzo1 libmad0 libmagic1 libmagick6 libmal1 libmimelib1a libmodplug0
libmusicbrainz4 libmyspell3
  libmysqlclient12 libncursesw5 libnetpbm10 libnewt0.51 liboggflac1
libopencdk8 libopenct1 libopenexr2 libopensc1
  liborbit2 libosp4 libostyle1 libpaper-utils libpaper1 libpcap0.7
libpcap0.8 libpcsclite1 libperl5.8 libpils0
  libpisock8 libpng10-0 libpng12-0 libpq3 libpth2 libraw1394-5
libreadline5 libruby1.8 libsamplerate0 libsasl2
  libsdl1.2debian libsdl1.2debian-oss libselinux1 libsensors3 libsigc
++-1.2-5c102 libslp1 libsmbclient libsnmp5
  libspeex1 libss2 libssl0.9.7 libstartup-notification0 libstdc++5

Re: upgrade woody vers sarge (dpkg: parse error, in file `/var/lib/dpkg/available)

2005-07-26 Thread Yves Perraudin

Jean-Jacques a écrit :

Bonjour à tous !


Bonjour,


Je viens d'essayer de faire l'upgrade de woody vers Sarge.


[...]


333 packages upgraded, 228 newly installed, 186 to remove and 21  not
upgraded.
Need to get 0B/265MB of archives. After unpacking 131MB will be used.
Do you want to continue? [Y/n] y


Moi, je n'aurais pas appuyer sur 'y' après avoir lu cela...


Est ce que quelqu'un pourrait m'indiquer comment faire pour aller
jusqu'à la fin du processus d'upgrade ?


Il faut de préférence utiliser aptitude pour la mise à jour.

Les notes de publications :
http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.fr.html

Yves Perraudin


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Dist-upgrade woody auf sarge per ssh

2005-06-27 Thread Ralf Ebeling
Thomas Amm wrote:
 hat jemand $SUBJECT erfolgreich bewältigt? Ich habe einen root-Server
 mit allerhand Projektchen, auf den ich normalerweise nur per ssh
 zugreifen kann. Darauf läuft noch Woody, aber ich möchte das Upgrade
 nun endlich mal in Angriff nehmen. Hat evtl. jemand Schwierigkeiten, was
 die Netconfig, bzw den Restart von sshd angeht beobachtet?
 Das Archiv schweigt sich diesbezgl. erfreulich aus (No message - good
 message), aber ich will lieber auf Nummer Sicher gehen.

Ja, mit ein wenig Nacharbeit. Ich hatte mich bei einigen angezeigten
Paketen (dhcp, MySQL, logcheck, chrony, cupsd, apache) dafür entschieden
die neuen Konfigurationen der Maintaner zu übernehmen - diese musste ich
dann hinterher nochmal nacharbeiten.

Ralf


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Dist-upgrade woody auf sarge per ssh

2005-06-25 Thread Thomas Amm
Hallo Liste,

hat jemand $SUBJECT erfolgreich bewältigt? Ich habe einen root-Server
mit allerhand Projektchen, auf den ich normalerweise nur per ssh
zugreifen kann. Darauf läuft noch Woody, aber ich möchte das Upgrade
nun endlich mal in Angriff nehmen. Hat evtl. jemand Schwierigkeiten, was
die Netconfig, bzw den Restart von sshd angeht beobachtet?
Das Archiv schweigt sich diesbezgl. erfreulich aus (No message - good
message), aber ich will lieber auf Nummer Sicher gehen.

Danke im Vorraus,

Thomas Amm

 



Re: Dist-upgrade woody auf sarge per ssh

2005-06-25 Thread Daniel Leidert
Am Samstag, den 25.06.2005, 19:43 +0200 schrieb Thomas Amm:

 hat jemand $SUBJECT erfolgreich bewältigt?

Ja, ging problemlos. War aber schon länger vor dem offiziellen
Sarge-Release.

 Ich habe einen root-Server
 mit allerhand Projektchen, auf den ich normalerweise nur per ssh
 zugreifen kann. Darauf läuft noch Woody, aber ich möchte das Upgrade
 nun endlich mal in Angriff nehmen. Hat evtl. jemand Schwierigkeiten, was
 die Netconfig,

Ich weiß jetzt nicht genau, was du unter Netconfig verstehst, aber ...

 bzw den Restart von sshd angeht beobachtet?

... das sollte unproblematisch sein, da davon die aktuelle SSH-Sitzung
nicht betroffen ist bzw. sein sollte. Wenn du sicher gehen willst,
versuche nach dem Upgrade erst einen parallelen SSH-Login, bevor du die
SSH-Sitzung beendest, dann weißt du es genau.

 Das Archiv schweigt sich diesbezgl. erfreulich aus (No message - good
 message), aber ich will lieber auf Nummer Sicher gehen.

Garantien gibt es allerdings keine ;)
Ernsthaft, mach ein Vollbackup wenn möglich und dann wäre auch der GAU
zu verkraften.

MfG Daniel



Re: Dist-upgrade woody auf sarge per ssh

2005-06-25 Thread Evgeni Golov
On Sat, 25 Jun 2005 19:43:14 +0200
Thomas Amm [EMAIL PROTECTED] wrote:

 Hallo Liste,

Hallo Thomas,

 
 hat jemand $SUBJECT erfolgreich bewältigt? Ich habe einen root-Server

Ja, ich.

 mit allerhand Projektchen, auf den ich normalerweise nur per ssh
 zugreifen kann. Darauf läuft noch Woody, aber ich möchte das Upgrade
 nun endlich mal in Angriff nehmen. Hat evtl. jemand Schwierigkeiten,
 was die Netconfig, bzw den Restart von sshd angeht beobachtet?

Nein eigentlich nicht, sources.list geändert, apt, dpkg upgedated, dann
den Rest, dann die Backports remved und die Sarge-Pakete genommen -
läuft einwandfrei unter Sarge nu der Server.

 Das Archiv schweigt sich diesbezgl. erfreulich aus (No message - good
 message), aber ich will lieber auf Nummer Sicher gehen.

Aufpassen bei Backports und Fremdquellen, aber sonst hatte die Kiste
größeren Probs gemacht.

 Danke im Vorraus,
 
 Thomas Amm

Evgeni

-- 
   ^^^| Evgeni -SargentD- Golov ([EMAIL PROTECTED])
 d(O_o)b  | PGP-Key-ID: 0xAC15B50C
  -|-   | WWW: www.die-welt.net   ICQ: 54116744
   / \| IRC: #sod @ irc.german-freakz.net


pgptjPoXwyB06.pgp
Description: PGP signature


Re: Dist-upgrade woody auf sarge per ssh

2005-06-25 Thread Thomas Amm
On Sat, 25 Jun 2005 19:59:17 +0200
Daniel Leidert [EMAIL PROTECTED] wrote:

 Am Samstag, den 25.06.2005, 19:43 +0200 schrieb Thomas Amm:
 
  hat jemand $SUBJECT erfolgreich bewältigt?
 
 Ja, ging problemlos. War aber schon länger vor dem offiziellen
 Sarge-Release.
 
  Ich habe einen root-Server
  mit allerhand Projektchen, auf den ich normalerweise nur per ssh
  zugreifen kann. Darauf läuft noch Woody, aber ich möchte das
  Upgrade nun endlich mal in Angriff nehmen. Hat evtl. jemand
  Schwierigkeiten, was die Netconfig,
 
 Ich weiß jetzt nicht genau, was du unter Netconfig verstehst, aber ...

Wenn ich's nochmal nachlese, eigentlich gar nix, nur das Interface an
dem sshd haengt, sollte nach einem evtl. Reboot wieder hochkommen

  bzw den Restart von sshd angeht beobachtet?
 
 ... das sollte unproblematisch sein, da davon die aktuelle SSH-Sitzung
 nicht betroffen ist bzw. sein sollte. Wenn du sicher gehen willst,
 versuche nach dem Upgrade erst einen parallelen SSH-Login, bevor du
 die SSH-Sitzung beendest, dann weißt du es genau.

Gute Idee, ich denke, ich werde ausnahmsweise auch noch telnetd
laufen lassen. Lieber logt einer einer zuviel ein, den ich in flagranti
erwische, als gar niemand mehr ;)

 
 Garantien gibt es allerdings keine ;)
 Ernsthaft, mach ein Vollbackup wenn möglich und dann wäre auch der GAU
 zu verkraften.

Sowieso. Die Kiste wird taeglich mit rsync gespiegelt.

Danke, Gruss und dann werd' ich mal...



Re: Dist-upgrade woody auf sarge per ssh

2005-06-25 Thread Thomas Amm
On Sat, 25 Jun 2005 20:00:20 +0200
Evgeni Golov [EMAIL PROTECTED] wrote:

 On Sat, 25 Jun 2005 19:43:14 +0200
 Thomas Amm [EMAIL PROTECTED] wrote:
 
  Hallo Liste,
 
 Hallo Thomas,
 
  
  hat jemand $SUBJECT erfolgreich bewältigt? Ich habe einen root-
  Server
 
 Ja, ich.
 
Congrats :)

  mit allerhand Projektchen, auf den ich normalerweise nur per ssh
  zugreifen kann. Darauf läuft noch Woody, aber ich möchte das
  Upgrade nun endlich mal in Angriff nehmen. Hat evtl. jemand
  Schwierigkeiten, was die Netconfig, bzw den Restart von sshd angeht
  beobachtet?
 
 Nein eigentlich nicht, sources.list geändert, apt, dpkg upgedated,
 dann den Rest, dann die Backports remved und die Sarge-Pakete
 genommen - läuft einwandfrei unter Sarge nu der Server.
 
 
 Aufpassen bei Backports und Fremdquellen, aber sonst hatte die Kiste
 größeren Probs gemacht.
 
OK. Wesentlich ist ohnehin nur, dass ich wieder hineinkomme, der Rest
ist das taeglich' FreudLeid des Admin.

Danke und Gruss aus Berlin,

Thomas



Re: easiest way to upgrade woody to sarge?

2005-06-09 Thread David Roguin
If you have something in there like a Primary Domain Controller or
something like a server that it could break if you change the version
of it; the upgrade is done changing the 'woody' word in the
/etc/apt/sources.list to 'sarge' and then run apt-get update 
apt-get dist-upgrade.

If instead of woody you have stabe, then is apt-get update  apt-get
dist-upgrade the only thing to upgrade your system.

have luck ;)

On 6/7/05, Sean Davis [EMAIL PROTECTED] wrote:
 I've got a Debian Woody system that's been running decently for over a month
 now, and would like to update it to Sarge. I know it's been covered before,
 but is there an authoritative document on updating? I can only access the
 box remotely - it's hosted at the datacenter at which I work, and I don't
 typically have time to mess with it at work, although I could hook up a
 monitor/keyboard if I hosed it badly enough - so I'm wondering if there is
 a procedure known to work on remote servers without much trouble.
 
 The hardware is nothing exotic; Athlon XP2200+, 1GB ram, 80GB ATA100 HD.
 
 TIA,
 -Sean
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 




Re: easiest way to upgrade woody to sarge?

2005-06-09 Thread Jon Dowland

Sean Davis wrote:

I've got a Debian Woody system that's been running decently for over a 
month
now, and would like to update it to Sarge. I know it's been covered 
before,

but is there an authoritative document on updating?


Yes, the sarge release notes. http://www.debian.org/releases/stable/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




easiest way to upgrade woody to sarge?

2005-06-06 Thread Sean Davis
I've got a Debian Woody system that's been running decently for over a month
now, and would like to update it to Sarge. I know it's been covered before,
but is there an authoritative document on updating? I can only access the
box remotely - it's hosted at the datacenter at which I work, and I don't
typically have time to mess with it at work, although I could hook up a
monitor/keyboard if I hosed it badly enough - so I'm wondering if there is
a procedure known to work on remote servers without much trouble.

The hardware is nothing exotic; Athlon XP2200+, 1GB ram, 80GB ATA100 HD.

TIA,
-Sean


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: easiest way to upgrade woody to sarge?

2005-06-06 Thread Roberto C. Sanchez
On Mon, Jun 06, 2005 at 11:40:41PM -0400, Sean Davis wrote:
 I've got a Debian Woody system that's been running decently for over a month
 now, and would like to update it to Sarge. I know it's been covered before,
 but is there an authoritative document on updating? I can only access the
 box remotely - it's hosted at the datacenter at which I work, and I don't
 typically have time to mess with it at work, although I could hook up a
 monitor/keyboard if I hosed it badly enough - so I'm wondering if there is
 a procedure known to work on remote servers without much trouble.
 
 The hardware is nothing exotic; Athlon XP2200+, 1GB ram, 80GB ATA100 HD.
 

Remote upgrades are a piece of cake.  If you intend to upgrade the
kernel, I recommend you do it seperately *after* upgrading everything
else.  Read the release notes in their entirety before jumping in.

-Roberto

-- 
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr


pgpNKhZuh97J2.pgp
Description: PGP signature


Re: easiest way to upgrade woody to sarge?

2005-06-06 Thread Paul E Condon
On Mon, Jun 06, 2005 at 11:40:41PM -0400, Sean Davis wrote:
 I've got a Debian Woody system that's been running decently for over a month
 now, and would like to update it to Sarge. I know it's been covered before,
 but is there an authoritative document on updating? I can only access the
 box remotely - it's hosted at the datacenter at which I work, and I don't
 typically have time to mess with it at work, although I could hook up a
 monitor/keyboard if I hosed it badly enough - so I'm wondering if there is
 a procedure known to work on remote servers without much trouble.
 

Yes. The standard procedure is known to work on remote servers, except
you should have a plan B, if there is a problem. Maybe wait a few
hours/days to be let others who aren't doing it remotely discover
whatever bugs are still there.  The dist-upgrade does NOT mess with
the kernel, so you should be OK.

The standard is (I like aptitude):
1) edit sources.list to point to sarge rather than woody.
2) aptitude update
3) aptitude dist-upgrade
4) wait for a time that depends on the size of your pipe
5) answer config messages 

HTH

-- 
Paul E Condon   
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Is it possible to upgrade Woody to Sarge?

2004-11-22 Thread Robert Cates
Hi all,
is it possible with apt-get to upgrade a Woody installation to Sarge?
If so, would that be with:
apt-get dist-upgrade
or is that just to completely upgrade the Woody installation.?
Thanks, and please CC me directly since I'm not currently subscribed to this 
list.
Robert


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Is it possible to upgrade Woody to Sarge?

2004-11-22 Thread Maurits van Rees
On Mon, Nov 22, 2004 at 09:33:33AM +0100, Robert Cates wrote:
 Hi all,
 
 is it possible with apt-get to upgrade a Woody installation to Sarge?
 If so, would that be with:
 
 apt-get dist-upgrade

Yes. But first change sources.list: all occurances of woody or stable
should be changed to sarge or testing. I would say pick sarge in both
cases.

Then:

apt-get update

apt-get dist-upgrade.

Of course it never hurts (read: is highly recommended) to make a
complete backup first...

By all means first take a look at the docs in
/usr/share/doc/Debian/apt-howto/ 

 or is that just to completely upgrade the Woody installation.?

I think with `completely upgrading' you mean updating all your woody
packages to their latest versions in the woody districution? No,
that's what you get with `apt-get update' and then `apt-get upgrade'.

-- 
Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands]
Let your advance worrying become advance thinking and planning.
 - Winston Churchill


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Is it possible to upgrade Woody to Sarge?

2004-11-22 Thread Ron Johnson
On Mon, 2004-11-22 at 09:33 +0100, Robert Cates wrote:
[snip]
 Thanks, and please CC me directly since I'm not currently subscribed
 to this list.

So, subscribe to the list like the rest of us schmucks...

-- 
-
Ron Johnson, Jr.
Jefferson, LA USA
PGP Key ID 8834C06B I prefer encrypted mail.

He that would live in peace and at ease must not speak all he
knows or all he sees.
Benjamin Franklin



signature.asc
Description: This is a digitally signed message part


Re: Is it possible to upgrade Woody to Sarge?

2004-11-22 Thread Brian Nelson
Robert Cates [EMAIL PROTECTED] writes:

 is it possible with apt-get to upgrade a Woody installation to Sarge?
 If so, would that be with:

 apt-get dist-upgrade

 or is that just to completely upgrade the Woody installation.?

Read the release notes, available at:

  http://www.debian.org/doc/user-manuals#relnotes

Sarge of course hasn't been released yet, and I don't think the release
notes for it have been prepared, but they will likely be similar to the
notes for woody.

-- 
For every sprinkle I find, I shall kill you!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



upgrade Woody to Sarge

2004-01-25 Thread john gennard
On a new hard drive, I've installed a basic Woody (ex the 7 CD set) to 
use to
upgrade to Sarge.

In /etc/apt/sources.list I put:-
   'deb http://http.us.debian.org/debian testing main contrib non-free'
and ran:-'apt-get update'
Things seemed to go fine initially, but I finished with the following 
error:-

--
[snip]
Fetched 2827kB in 38s ...
Reading Package Lists ... Error!
E.  Dynamic MMap ran out of room
E.  Error occured while processing vrwave (NewVersion2)
E.  Problem with MergeList /var/lib/apt/lists/
  http.us.debian.org_debian_dists_testing_non-free_binary-i386_Packages
E.  The package lists or status file could not be parsed or opened
--
I haven't yet configured this Woody for email yet, so this is being sent 
from
another OS.

I'd be grateful for an explanation, and any suggestions to get over this 
problem.
(Is the problem only with the 'non-free'?)

Regards,John.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: upgrade Woody to Sarge

2004-01-25 Thread Alan Chandler
On Sunday 25 January 2004 10:10 am, john gennard wrote:
 On a new hard drive, I've installed a basic Woody (ex the 7 CD set) to
 use to
 upgrade to Sarge.

 In /etc/apt/sources.list I put:-
 'deb http://http.us.debian.org/debian testing main contrib
 non-free' and ran:-'apt-get update'

 Things seemed to go fine initially, but I finished with the following
 error:-

 --
 [snip]
 Fetched 2827kB in 38s ...
 Reading Package Lists ... Error!
 E.  Dynamic MMap ran out of room
 E.  Error occured while processing vrwave (NewVersion2)
 E.  Problem with MergeList /var/lib/apt/lists/

Have you run out of disk space in /var ?  - or alternatively perhaps in /tmp 
or swap


-- 
Alan Chandler
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: upgrade Woody to Sarge

2004-01-25 Thread john gennard






Alan Chandler wrote:

  On Sunday 25 January 2004 10:10 am, john gennard wrote:
  
  
On a new hard drive, I've installed a basic Woody (ex the 7 CD set) to
use to
upgrade to Sarge.

In /etc/apt/sources.list I put:-
'deb http://http.us.debian.org/debian testing main contrib
non-free' and ran:-'apt-get update'

Things seemed to go fine initially, but I finished with the following
error:-

--
[snip]
Fetched 2827kB in 38s ...
Reading Package Lists ... Error!
E.  Dynamic MMap ran out of room
E.  Error occured while processing vrwave (NewVersion2)
E.  Problem with MergeList /var/lib/apt/lists/

  
  
Have you run out of disk space in /var ?  - or alternatively perhaps in /tmp 
or swap


  

No, I've used only 500mb out of 6.5 Gig, and am using only one partition.
Swap
is 500mb and Ram over 650mb and very little is used.




Re: upgrade Woody to Sarge

2004-01-25 Thread Colin Watson
On Sun, Jan 25, 2004 at 10:31:05AM +, Alan Chandler wrote:
 On Sunday 25 January 2004 10:10 am, john gennard wrote:
  On a new hard drive, I've installed a basic Woody (ex the 7 CD set)
  to use to upgrade to Sarge.
 
  In /etc/apt/sources.list I put:-
  'deb http://http.us.debian.org/debian testing main contrib
  non-free' and ran:-'apt-get update'
 
  Things seemed to go fine initially, but I finished with the following
  error:-
 
  --
  [snip]
  Fetched 2827kB in 38s ...
  Reading Package Lists ... Error!
  E.  Dynamic MMap ran out of room
  E.  Error occured while processing vrwave (NewVersion2)
  E.  Problem with MergeList /var/lib/apt/lists/
 
 Have you run out of disk space in /var ?  - or alternatively perhaps in /tmp 
 or swap

No, he hasn't. Or at least, that's not the problem.

John, if you just added that sources.list line and didn't remove the
corresponding one for stable, then do so now. If that doesn't help, then
try putting 'APT::Cache-Limit 16777216;' in /etc/apt/apt.conf (create
it if it doesn't exist) and trying again.

If you need to do the second step, then please report that together with
the complete contents of your /etc/apt/sources.list. We'll need to know
this for the sarge release notes.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: upgrade Woody to Sarge

2004-01-25 Thread john gennard


Colin Watson wrote:

On Sun, Jan 25, 2004 at 10:31:05AM +, Alan Chandler wrote:
 

On Sunday 25 January 2004 10:10 am, john gennard wrote:
   

On a new hard drive, I've installed a basic Woody (ex the 7 CD set)
to use to upgrade to Sarge.
In /etc/apt/sources.list I put:-
   'deb http://http.us.debian.org/debian testing main contrib
non-free' and ran:-'apt-get update'
Things seemed to go fine initially, but I finished with the following
error:-
--
[snip]
Fetched 2827kB in 38s ...
Reading Package Lists ... Error!
E.  Dynamic MMap ran out of room
E.  Error occured while processing vrwave (NewVersion2)
E.  Problem with MergeList /var/lib/apt/lists/
 

Have you run out of disk space in /var ?  - or alternatively perhaps in /tmp 
or swap
   

No, he hasn't. Or at least, that's not the problem.

John, if you just added that sources.list line and didn't remove the
corresponding one for stable, then do so now. 

I'm ok there, Colin, as I only had entries for cdrom access plus the 
security update http
entry which I commented out.

If that doesn't help, then
try putting 'APT::Cache-Limit 16777216;' in /etc/apt/apt.conf (create
it if it doesn't exist) and trying again.
 

Haven't tried this. After posting, I tried a number of things (brute 
force and ignorance) and
eventually got 'update' to work by using:-
'deb http://ftp.us.debian.org/debian testing main contrib'
   (ie changing 'http' to 'ftp' and deleting 'non-free')

However, I had to run 'apt-get dist-upgrade' five times before it 
stopped complaining,
and by that time it had removed almost all kde pkgs and installed over 
500mb of packages
I didn't ask for. Mind you, I think I learned a lot about what was 
involved in the way of
changed approaches.

In my ignorance, I assumed that only those packages I had installed (I 
deliberately made
only a minimal install) would be upgraded. Does this always happen, I 
wonder?

If you need to do the second step, then please report that together with
the complete contents of your /etc/apt/sources.list. We'll need to know
this for the sarge release notes.
The sources.list contained only the entries made during the install from 
the official 7 CD set,
and the http security entry also created by the install program, plus 
the single line I inserted
and then amended.
Let me know if you think more information would be useful to you.

Thanks for the reply,

John.

Cheers,

 



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]