Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 16:59, Mart Frauenlob wrote:
On 01.03.2010 12:06, Mart Frauenlob wrote:
On 28.02.2010 09:29, Mart Frauenlob wrote:
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Trimming it down more:
var[0]=\foo bar\ is valid on a line for itself.
But:
if true; then
echo \foo\
var=\foo bar\
var[0]=\foo bar\
fi
the 'echo' and the 'var=' escape well, but the 'var[0]=' array member
assignment fails.
Hello,
though I'm mainly talking to myself here, I got some updates.
I manually compiled/installed the vim versions 6.4, 7.0, 7.1 and 7.2.
Running version 6.4 and 7.0 with a slightly modified vimrc from the etch
version (vimrc.dpkg-old) (leaving out some debian specific things), I
get back the bash script syntax highlighting I was used to in sarge and
etch.
However vim versions 7.1 and 7.2 seem to have changed. I get different
results with both. I don't know if this is caused by the sh.vim or the
actual vim code, but however it does not seem to be a debian specific
problem, as far as I can tell.
Guess I need to find the time to talk to the people in the vim mailing list.
Good day
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8d5790.6070...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 28.02.2010 09:29, Mart Frauenlob wrote:
Hello,
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
Thanks a lot
Mart
Hello again,
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Best regards
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8b9fc4.8060...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
Check `update-alternatives --list vim` to ensure your not running vim-tiny. -- Jordan Metzmeier -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50e5edd51003010556p15a51dc7x475c5951dac84...@mail.gmail.com
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 14:56, Jordan Metzmeier wrote: Check `update-alternatives --list vim` to ensure your not running vim-tiny. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.basic /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 Current `best' version is /usr/bin/vim.basic. there are no other vim.X versions, right? Best regards Mart -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b8bde1d.1090...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 12:06, Mart Frauenlob wrote:
On 28.02.2010 09:29, Mart Frauenlob wrote:
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Trimming it down more:
var[0]=\foo bar\ is valid on a line for itself.
But:
if true; then
echo \foo\
var=\foo bar\
var[0]=\foo bar\
fi
the 'echo' and the 'var=' escape well, but the 'var[0]=' array member
assignment fails.
Regards
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8be45a.6030...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 16:32, Mart Frauenlob wrote: On 01.03.2010 14:56, Jordan Metzmeier wrote: Check `update-alternatives --list vim` to ensure your not running vim-tiny. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.basic /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 Current `best' version is /usr/bin/vim.basic. there are no other vim.X versions, right? Sorry, don't want to spam, just installed the vim.nox (as no gui here), but that didn't change anything. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.nox /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 /usr/bin/vim.nox - priority 40 Current `best' version is /usr/bin/vim.nox. Best regards Mart -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b8be685.9080...@chello.at
after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
Hello,
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
Thanks a lot
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8a296f.6080...@chello.at
a couple remaining issues after dist-upgrade, etch - lenny
i finally pulled the trigger on this, almost 300 packages upgraded, rebooted and here are some of the (apparently non-fatal) issues i ran across: 1) my /etc/aliases.db file was deleted. no problem, i just recreated it with # postalias hash:/etc/aliases easy enough to fix but should i have expected that? couldn't something that obvious be part of the automatic upgrade process? 2) log error that there was no permission to read /etc/ldap/slapd.conf, not surprising since the perms on that file were: root root -rw--- changed perms to 644, that seems to have solved that problem. should i have expected that as well? or was there a better way to solve that access problem? 3) in fact, running aptitude upgrade tells me that slapd is still only partially configured, but trying to finish the configuration gives me: = Setting up slapd (2.4.11-1) ... Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.3.30-5+etch2... done. Upgrading BDB 'checkpoint' options... . Moving old database directories to /var/backups: Loading from /var/backups/slapd-2.3.30-5+etch2: - directory dc=XX,dc=com... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: /etc/ldap/slapd.conf: line 50: unknown directive defaultaccess outside backend info and database definitions. slapadd: bad configuration file! dpkg: error processing slapd (--configure): subprocess post-installation script returned error exit status 1 = i'm not an LDAP expert -- can i just comment out the offending line? defaultaccess write i'm guessing there's been a change in the syntax of that config file and i just have to read up on it. off to check if there are any more issues, but if that's the extent of them, i'm in good shape. rday -- Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: a couple remaining issues after dist-upgrade, etch - lenny
Robert P. J. Day 写道: i finally pulled the trigger on this, almost 300 packages upgraded, rebooted and here are some of the (apparently non-fatal) issues i ran across: 1) my /etc/aliases.db file was deleted. no problem, i just recreated it with # postalias hash:/etc/aliases easy enough to fix but should i have expected that? couldn't something that obvious be part of the automatic upgrade process? 2) log error that there was no permission to read /etc/ldap/slapd.conf, not surprising since the perms on that file were: root root -rw--- changed perms to 644, that seems to have solved that problem. should i have expected that as well? or was there a better way to solve that access problem? 3) in fact, running aptitude upgrade tells me that slapd is still only partially configured, but trying to finish the configuration gives me: = Setting up slapd (2.4.11-1) ... Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.3.30-5+etch2... done. Upgrading BDB 'checkpoint' options... . Moving old database directories to /var/backups: Loading from /var/backups/slapd-2.3.30-5+etch2: - directory dc=XX,dc=com... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: /etc/ldap/slapd.conf: line 50: unknown directive defaultaccess outside backend info and database definitions. slapadd: bad configuration file! dpkg: error processing slapd (--configure): subprocess post-installation script returned error exit status 1 = i'm not an LDAP expert -- can i just comment out the offending line? defaultaccess write Don't know if defaultaccess is set to write is good enough for your application. You can try comment it out or add the following line to your config file: access to * by * write As far as I know, it's really dangerous and should be fully tested in advance. Hope this helps. i'm guessing there's been a change in the syntax of that config file and i just have to read up on it. off to check if there are any more issues, but if that's the extent of them, i'm in good shape. rday -- Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: a couple remaining issues after dist-upgrade, etch - lenny
On Tue, 25 Aug 2009, Niu Kun wrote: Robert P. J. Day 写道: i finally pulled the trigger on this, almost 300 packages upgraded, rebooted and here are some of the (apparently non-fatal) issues i ran across: ... snip ... 3) in fact, running aptitude upgrade tells me that slapd is still only partially configured, but trying to finish the configuration gives me: = Setting up slapd (2.4.11-1) ... Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.3.30-5+etch2... done. Upgrading BDB 'checkpoint' options... . Moving old database directories to /var/backups: Loading from /var/backups/slapd-2.3.30-5+etch2: - directory dc=XX,dc=com... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: /etc/ldap/slapd.conf: line 50: unknown directive defaultaccess outside backend info and database definitions. slapadd: bad configuration file! dpkg: error processing slapd (--configure): subprocess post-installation script returned error exit status 1 = i'm not an LDAP expert -- can i just comment out the offending line? defaultaccess write Don't know if defaultaccess is set to write is good enough for your application. You can try comment it out or add the following line to your config file: access to * by * write As far as I know, it's really dangerous and should be fully tested in advance. Hope this helps. for now, just to finish getting slapd configured, i commented out the defaultaccess line, at which point i got the error: error while running slapadd: /etc/ldap/slapd.conf: line 64: lastmod extra cruft after on|off that line originally read: lastmod on replogfile /var/lib/ldap/replog so i just obeyed the diagnostic and changed it to: lastmod on and the slapd configuration completed. i'll go over the docs later but, as long as slapd seems to be running for the moment, i'm hoping those changes are adequate. rday -- Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday
Upgrade etch vers lenny
Bonjour à tous, Tous les serveurs debian sous etch non pas encore migrés sous lenny. Même s'il n'y a pas d'urgence, je voudrais finir cette tâche. Mais j'ai un serveur sensible et j'avoue que je voudrais prendre toutes les précautions possibles. Au niveau matériel ce serveur repose sur un raid matériel 3ware biern géré par le kernel en cours à savoir 2.6.18-6-686. Dois je prendre une précaution particulière concernant l'upgrade ou je peux me dire que le kernel en cours sous lenny gérera aussi bien de matériel ? J'envisage de faire des images de chaque partition avec partimage pour restauration si nécessaire. Est ce une précaution inutile ou y a t il mieux ? merci de votre aide fabrice
Re: Upgrade etch vers lenny
Le 25/05/2009 à 16:33, fabrice test a écrit : Bonjour à tous, Tous les serveurs debian sous etch non pas encore migrés sous lenny. Même s'il n'y a pas d'urgence, je voudrais finir cette tâche. Mais j'ai un serveur sensible et j'avoue que je voudrais prendre toutes les précautions possibles. Au niveau matériel ce serveur repose sur un raid matériel 3ware biern géré par le kernel en cours à savoir 2.6.18-6-686. Dois je prendre une précaution particulière concernant l'upgrade ou je peux me dire que le kernel en cours sous lenny gérera aussi bien de matériel ? J'envisage de faire des images de chaque partition avec partimage pour restauration si nécessaire. Est ce une précaution inutile ou y a t il mieux ? Faire une copie complète du système est sage (ou plutôt ne pas faire de copie est complètement déraisonnable) Imprimer la table des partition peut aussi s'avérer utile (très rarement, mais le jour ou on en a besoin on est content :) ) Le mieux c'est de ne pas toucher au système en place et d'installer lenny dans une autre partition (et/ou disque). Eventuellement dupliquer l'existant dans la nouvelle partition et faire l'upgrade. Ainsi avec grub il y a le choix entre l'ancien système et le nouveau. Alain -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
[Solved]Re: Unable to boot into encrypted file system after upgrade etch -- lenny
On 26 Mrz., 16:10, Michael Lange klappn...@web.de wrote: On Thu, 26 Mar 2009 10:41:26 +0200 snip Ok, there seems to be a bug in debian's initramfs-tools that resembles a lot the one described at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507721 . In the last few days I learned how to unpack, edit and re-package the initrd.img file manually. I found there is a file conf/conf.d/ cryptroot missing from the initrd.img 's contents. Just add it manually and re-package the initrd.img and the machine boots fine. Reading the discussions from the link above, I thought that there might be a bug in initramfs-tools that stopped them from working with the disk partition labels in /etc/fstab. So change /etc/fstab back to use /dev/mapper/root again instead of LABEL=CRYPTOROOT for the root partition, call update-initramfs ... _et voila_ . Too bad that the debian docs for upgrading etch to lenny recommend the disk partition labels to avoid /dev/hda - /dev/sda confusions with a new kernel where it is not necessary at all with lenny's 2.6.26-1 . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Unable to boot into encrypted file system after upgrade etch -- lenny
klappnase wrote: Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is an encrypted root partition on /dev/hda1 and a separate /boot partition on /dev/hda4. When booting the new kernel I get Waiting for root file system and a while later I am being dropped to a busy box shell. I have seen, the docs suggest that the problem might be a /dev/hda - / dev/sda confusion with a new kernel, however before the boot hangs there is a bunch of messages that addresses the hard disk as /dev/ hda. Furthermore I followed the docs' suggestion to add label descriptors to the hard disk partitions to avoid these confusions. Did you run a 'update-initramfs' ? Normally you wouldn't have to, but try it... G. smime.p7s Description: S/MIME Cryptographic Signature
Re: Unable to boot into encrypted file system after upgrade etch -- lenny
On Thu, 26 Mar 2009 10:41:26 +0200 Γιώργος Πάλλας gp...@ccf.auth.gr wrote: klappnase wrote: Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is an encrypted root partition on /dev/hda1 and a separate /boot partition on /dev/hda4. When booting the new kernel I get Waiting for root file system and a while later I am being dropped to a busy box shell. I have seen, the docs suggest that the problem might be a /dev/hda - / dev/sda confusion with a new kernel, however before the boot hangs there is a bunch of messages that addresses the hard disk as /dev/ hda. Furthermore I followed the docs' suggestion to add label descriptors to the hard disk partitions to avoid these confusions. Did you run a 'update-initramfs' ? Normally you wouldn't have to, but try it... G. Yes I did. Even worse, in my first post I hoped that all that is wrong is that some necessary kernel modules are missing from /etc/initramfs-tools/modules . Now I found that I can run the debian-rescue live-cd which uses the very same kernel (2.6.26-1-686) and I am able to mount the encrypted partition from there; so I tried adding everything lsmod returns there to /etc/initramfs-tools/modules and re-run update-initramfs, yet without success. I also tried adding rootdelay=9 to the kernel line in grub/menu.lst as it has been suggested somewhere, but it did not change anything, except that I had to wait 9 seconds for Waiting for root file system :( Does anyone have another idea? Michael -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Unable to boot into encrypted file system after upgrade etch -- lenny
Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is an encrypted root partition on /dev/hda1 and a separate /boot partition on /dev/hda4. When booting the new kernel I get Waiting for root file system and a while later I am being dropped to a busy box shell. I have seen, the docs suggest that the problem might be a /dev/hda - / dev/sda confusion with a new kernel, however before the boot hangs there is a bunch of messages that addresses the hard disk as /dev/ hda. Furthermore I followed the docs' suggestion to add label descriptors to the hard disk partitions to avoid these confusions. Now my /etc/crypttab looks like: root LABEL=CRYPTOROOT root.key luks,keyscript=/root/crypto-usb-key.sh swap /dev/hda3 /dev/randomswap And /etc/fstab: proc /proc proc defaults0 0 /dev/mapper/swap none swap sw 0 0 LABEL=CRYPTOROOT / ext3 defaults,errors=remount-ro 0 1 LABEL=BOOT /boot ext3 defaults0 1 The entries in grub/menu.lst are: title Debian Etch old kernel root(hd0,3) kernel /vmlinuz-2.6.22-2-k7 root=LABEL=CRYPTOROOT ro vga=773 initrd /initrd.img-2.6.22-2-k7 savedefault title Debian GNU/Linux, kernel 2.6.26-1-686 root(hd0,3) kernel /vmlinuz-2.6.26-1-686 root=LABEL=CRYPTOROOT ro vga=773 initrd /initrd.img-2.6.26-1-686 savedefault where the first entry (old kernel) boots fine. Both initrd.img files were created after the upgrade. I suspect that there is some module missing from /etc/initramfs-tools/modules that is required for the new kernel, but I have no idea which it might be. I tried adding some modules by try-and-error, but to no avail. Currently it looks like: # Syntax: module_name [args ...] loop ide-disk # for usb drive: ehci_hcd sd_mod usb_storage fat vfat nls_cp850 nls_cp437 nls_iso8859_1 nls_iso8859_15 nls_utf8 # crypto: dm_mod dm_crypt cbc aes-i586 #sha256 #blkcipher # renamed in the new kernel: sha256_generic crypto_blkcipher aes_generic Any ideas? Thanks in advance! Michael -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
LUKS/lvm : pb de boot après upgrade etch- lenny [powerpc]
Bonjour à tous, Après une mise à jour Etch / powerpc sur un iBook avec LVM et LUKS (en préparation d'une upgrade vers Lenny), ma machine ne boote plus. Voici l'affichage console : [snip] Setting up cryptographic volume hda4_crypt (based o /dev/hda4) Enter LUKS passphrase: key 0 slot unlocked Command successful. cryptsetup : Waiting for root system attend longtemps done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= -did the system wait long enough?)* - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) FATAL : error inserting i8042... ALERT! /dev/mapper/tournemire-root does not exist. Dropping to a shell! Busybox... (initramfs) J'ai pas mal cherché sur internet, j'ai trouvé entre autres ça : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506634 Apparement LUKS est OK et me crée /dev/mapper/hda4_crypt, mais ensuite lvm n'arrive pas à monter le volume. Mais impossible d'appliquer la résolution de pb indiquée par Tobias sur la même page parce que le boot échoue et je me retrouve avec initramfs de monté avec busybox comme shell. J'aimerais pouvoir monter les volumes lvm pour arriver à relancer un aptitude, pour cela j'ai accès à des sauvegardes de cette machine d'avant la tentative d'upgrade via un nfs. Bref, est-ce que les experts dans la salle pourraient m'indiquer comment résoudre ce problème pour m'éviter de tout réinstaller? Merci d'avance Damien -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Upgrade etch to lenny on virtual server (Virtuozzo) with 2.6.18 kernel
Hello Debian users, I have a virtual private server (VPS) that is running a minimal install of etch (image used for installation provided by the hosting company). I believe they use Virtuozzo for virtualisation. Since the virtual servers are not run using Xen, this means I am bound by the kernel provided by the hoster since all virtual machines are sharing the kernel. The kernel is: servername:~# uname -a Linux servername.provider.tld 2.6.18-028stab060.2 #1 SMP Tue Jan 13 10:24:09 MSK 2009 i686 GNU/Linux Now my question is: Is it possible (or wise) to try to upgrade to lenny? Is it good practice to combine a lenny system with an etch kernel? Are there security risks? Maybe it's better to stick with etch and keep the system updated with security updates as long as they are available? The main purpose of the machine is being resposible for e-mails (exim, dovecot), hosting a tiny website. But on the other hand, I am playing around with it a lot and experimenting with running other services, so sometimes I'd welcome newer package versions. If you don't see reasons against this update: Would you recommend an installation using debootstrap, or is it fine to do the following? 1) /etc/apt/sources.list : Change occurences of etch to lenny 2) aptitude update 3) apt-get install aptitude 4) aptitude dist-upgrade I have simulated the above, and realised that there are some dependency problems, but they seem to result from the fact that it is a minimal install without X server etc. and thus there are unmet dependencies (depends) even now in the current installation. Thanks for your input! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade etch to lenny on virtual server (Virtuozzo) with 2.6.18 kernel
On Mon, Mar 09, 2009 at 06:56:25PM +0100, hh...@gmx.de wrote: Hello Debian users, I have a virtual private server (VPS) that is running a minimal install of etch (image used for installation provided by the hosting company). I believe they use Virtuozzo for virtualisation. Since the virtual servers are not run using Xen, this means I am bound by the kernel provided by the hoster since all virtual machines are sharing the kernel. The kernel is: servername:~# uname -a Linux servername.provider.tld 2.6.18-028stab060.2 #1 SMP Tue Jan 13 10:24:09 MSK 2009 i686 GNU/Linux Now my question is: Is it possible (or wise) to try to upgrade to lenny? Possible: sure. Each Debian distribution supports running on kernel of previous version. Wise? You generally have less than a year to migrate. It would probably be a good idea to ask them when will they provide you with a newer kernel to make a more informed decision. If you don't see reasons against this update: Would you recommend an installation using debootstrap, or is it fine to do the following? 1) /etc/apt/sources.list : Change occurences of etch to lenny 2) aptitude update 3) apt-get install aptitude 4) aptitude dist-upgrade This looks fine. Naturally it would help if you can test the upgrade on a similar server. I have simulated the above, and realised that there are some dependency problems, but they seem to result from the fact that it is a minimal install without X server etc. and thus there are unmet dependencies (depends) even now in the current installation. What are those? -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade etch to lenny on virtual server (Virtuozzo) with 2.6.18 kernel
On Monday 09 March 2009 12:56:25 hh...@gmx.de wrote: Hello Debian users, I have a virtual private server (VPS) that is running a minimal install of etch (image used for installation provided by the hosting company). I believe they use Virtuozzo for virtualisation. Since the virtual servers are not run using Xen, this means I am bound by the kernel provided by the hoster since all virtual machines are sharing the kernel. My VPS provider is running Xen, but I still have no control over my kernel. (I know Xen can be configured so that /boot [or similar] is available to both the host and the guest, but they are not doing so.) Anyway, I upgraded to Lenny without issue on an image that was originally Etch, so I'm using: Linux rei 2.6.24-19-xen #1 SMP Sat Jul 12 00:15:59 UTC 2008 x86_64 GNU/Linux with Lenny. They now support Lenny, but AFAIK the only way to get a Lenny VPS would requires starting from a fresh Lenny install by them. I may look into that in the future, but right now I don't feel like trying a data/settings migration and the kernel is working fine right now. The kernel is: servername:~# uname -a Linux servername.provider.tld 2.6.18-028stab060.2 #1 SMP Tue Jan 13 10:24:09 MSK 2009 i686 GNU/Linux Now my question is: Is it possible (or wise) to try to upgrade to lenny? I *think* that kernel should work for Lenny, but I'm not sure if 2.6.18 will be supported for Squeeze. Is it good practice to combine a lenny system with an etch kernel? No, but Lenny packages do have to support running on Etch and Etch-n-half kernels, since the reboot into the Lenny kernel can't happen until after a number of Lenny packages are running. So, you'll probably be safe running Lenny on an Etch kernel, but no guarantees. Are there security risks? I wouldn't think so. Etch still has security support, and your hosting provider should be responsible for that since they don't allow you to install your own kernel. Maybe it's better to stick with etch and keep the system updated with security updates as long as they are available? Probably, at least until your hosting provider provides Lenny images and you can migrate to one of those. I decided not to wait and didn't get bit. Still, I don't feel comfortable recommending it to just anyone. If you don't see reasons against this update: Would you recommend an installation using debootstrap, or is it fine to do the following? 1) /etc/apt/sources.list : Change occurences of etch to lenny 2) aptitude update 3) apt-get install aptitude 4) aptitude dist-upgrade I recommend following the steps given in the release notes for Lenny. Each Debian release provides instructions for upgrading from the previous release. I have simulated the above, and realised that there are some dependency problems, but they seem to result from the fact that it is a minimal install without X server etc. and thus there are unmet dependencies (depends) even now in the current installation. aptitude shouldn't let you get into a state like that, and will try and fix it for you if your system is in that state. I suggest getting your package management system in a consistent state (i.e. all Depends satisfied, among other things) before doing any installation or upgrade of packages. Now, aptitude likes having Recommends relationships satisfied by default as well, and will try and pull in packages that are not strictly necessary. If you are trying to keep your system minimal or simply trying to avoid something like X, it may be good to instruct it to not attempt to keep Recommends satisfied. Setting Aptitude::Recommends-Important to false in your apt.conf (or apt.conf.d) should do that. (I also use Aptitude::Keep-Recommends true and Aptitude::Keep-Suggests true, but that is so I can keep more packages marked as automatically installed.) -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Upgrade etch to lenny on virtual server (Virtuozzo) with 2.6.18 kernel
On Mon, Mar 9, 2009 at 12:18 PM, Tzafrir Cohen tzaf...@cohens.org.ilwrote: On Mon, Mar 09, 2009 at 06:56:25PM +0100, hh...@gmx.de wrote: Hello Debian users, I have a virtual private server (VPS) that is running a minimal install of etch (image used for installation provided by the hosting company). I believe they use Virtuozzo for virtualisation. Since the virtual servers are not run using Xen, this means I am bound by the kernel provided by the hoster since all virtual machines are sharing the kernel. The kernel is: servername:~# uname -a Linux servername.provider.tld 2.6.18-028stab060.2 #1 SMP Tue Jan 13 10:24:09 MSK 2009 i686 GNU/Linux Now my question is: Is it possible (or wise) to try to upgrade to lenny? Possible: sure. Each Debian distribution supports running on kernel of previous version. Wise? You generally have less than a year to migrate. It would probably be a good idea to ask them when will they provide you with a newer kernel to make a more informed decision. If you don't see reasons against this update: Would you recommend an installation using debootstrap, or is it fine to do the following? 1) /etc/apt/sources.list : Change occurences of etch to lenny 2) aptitude update 3) apt-get install aptitude 4) aptitude dist-upgrade This looks fine. Naturally it would help if you can test the upgrade on a similar server. I have simulated the above, and realised that there are some dependency problems, but they seem to result from the fact that it is a minimal install without X server etc. and thus there are unmet dependencies (depends) even now in the current installation. What are those? -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org I think the best thing to do is to ask your VPS provider if they support this upgrade, perhaps they will invite you to reimage your VPS using Lenny(not an option for all the services already running on your VPS). I have already use Lenny under OpenVZ(is the opensource option for Virtuozzo) without any issue, although I haven't upgraded Etch to Lenny under OpenVZ. -- It is human nature to think wisely and act in an absurd fashion. Todo el desorden del mundo proviene de las profesiones mal o mediocremente servidas
Upgrade etch - lenny
Witam, Ktoś juz upgradował etch do lennego na serwerze produkcyjnym gdzie może korzystac z postgresql,vserver i mógłby się podzielić wrażeniami ogólnie z przebiegu upgradu. pozdrawiam Albert -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
Salut, Bernard a écrit : | Souhaitant être en version testing/Lenny comment je fais ? Personnellement j'ai fait le saut de etch à lenny/sid il y a quelques jours en suivant à la lettre cet excellent tuto, conseillé d'ailleurs ici-même sur cette liste : http://ubunteros.tuxfamily.org/spip.php?article177 J'ai juste dû faire plusieurs fois aptitude dist-upgrade car les premières fois, aptitude installait plusieurs paquets, puis s'arrêtait pour trop d'erreurs. J'ai donc répété la commande 4 ou 5 fois, et j'ai désormais une magnifique Lenny/Sid. -- Franck Delage Création et hébergements de sites web www.web82.net -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny [resolu]
Le Thursday 08 January 2009 22:26:14 Stephane Bortzmeyer, vous avez écrit : On Thu, Jan 08, 2009 at 07:56:23PM +0100, anto...@starinux.org anto...@starinux.org wrote a message of 39 lines which said: Je remarque que les Upgrade ne fonctionnent pas toujours et pire, ils cassent la version avant upgrade ! Jamais eu de problème similaire mais, de toute façon, lenny n'est pas sortie encore. C'est une version de test. Donc, mettez à jour si vous voulez mais soyez prévenu ! J'aimerai connaître le moyen pour faire un upgrade sans trop de déboires. 0) SAUVEGARDES SAUVEGARDES SAUVEGARDES AI-JE DIT QU'IL FALLAIT FAIRE DES SAUVEGARDES ? 1) Éditer /etc/apt/sources.list 2) aptitude update 3) aptitude install aptitude (car la mise à jour doit se faire avec un aptitude récent) 4) aptitude dist-upgrade (en quatrième surtout pas en premier) Et j'en ai mis des machines à jour comme ça. Avant toutes choses, merci pour vos nombreuses réponses. Effectivement, il faut d'abord effectuer la mise à jours de aptitude version testing. La mise à jour EtchLenny se passe ensuite sans problemes majeurs. Il me reste à me documenter pour l'installation de logiciels en version récentes en adaptant le sources.list avec un fichier preferences. Merci encore à la liste pour le coup de main. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Upgrade Etch/Lenny
Messieurs bonsoir, Suite à l'utilisation de la commande apt-get -u dist-upgrade, je me retrouve avec la liste des erreurs suivantes : 1030 mis à jour, 306 nouvellement installés, 15 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0o/1073Mo dans les archives. Après dépaquetage, 743Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer [O/n] ? o Lecture des champs des paquets... Fait Lecture de l'état des paquets... Fait Récupération des rapports de bogue... Fait Analyse des informations Trouvé/Corrigé... 65%dpkg : mauvaise syntaxe de la version « 2007-10-01T00:00:00Z » : l'époque (epoch) dans la version n'est pas un nombre Analyse des informations Trouvé/Corrigé... Fait Bogues de gravité grave sur openoffice.org-writer (2.0.4.dfsg.2-7etch6 - 1:2.4.1-15) forwarded #507865 - openoffice.org-writer: OOo 2.4.x openinig OOo 3 files doesn't show text (2.x implements standard wrong) Bogues de gravité grave sur nautilus (2.14.3-11+b1 - 2.20.0-7) forwarded #510564 - nautilus: smb file deletion gvfs Bogues de gravité grave sur procps (1:3.2.7-3 - 1:3.2.7-9) done #511082 - procps: sysctl Display all values function contain bogus debug printf() (Corrigé : procps/1:3.2.7-9.1) Bogues de gravité grave sur texlive-common (- 2007.dfsg.1-4) done #429753 - texlive-commong post-install action fails, blocking tex/latex install (Corrigé : 2007-10-01T00:00:00Z) Bogues de gravité grave sur python2.5 (- 2.5.2-14) done #509697 - python2.5 misses dependency on binutils (Corrigé : 2.5.2-15) Réuni avec : 509821 Bogues de gravité grave sur libpam-modules (0.79-5 - 1.0.1-4) done #502140 - cannot unlock screen during etch - lenny transition (Corrigé : pam/1.0.1-5) Bogues de gravité grave sur initramfs-tools (0.85i - 0.92n) done #511085 - 60 seconds timeout for ipconfig is not enough (Corrigé : initramfs-tools/0.92o) Bogues de gravité serious sur epiphany-browser (2.14.3-8 - 2.22.3-8) done #510764 - epiphany-webkit: Epiphany should not provide webkit in a stable release (Corrigé : epiphany-browser/2.22.3-9) Bogues de gravité serious sur hal (0.5.8.1-9etch1 - 0.5.11-6) done #510639 - hal.conf.in needs augmenting for new D-Bus (Corrigé : hal/0.5.11-7) Bogues de gravité serious sur ghostscript (- 8.62.dfsg.1-3.1) done #503712 - etch-lenny upgrade left the system in broken state (Corrigé : ghostscript/8.62.dfsg.1-3.2 ghostscript/8.63.dfsg.1-1 ghostscript/8.62.dfsg.1-3.2lenny0) Bogues de gravité serious sur policycoreutils (1.32-3 - 2.0.49-6) done #506727 - policycoreutils: fail with error: list index out of range (Corrigé : policycoreutils/2.0.49-8) Bogues de gravité serious sur libsemanage1 (1.8-1 - 2.0.25-2) done #510134 - genhomedircon.c: login.defs:MAX_UID have no effect on generating list of valid users, but MIN_UID does have. (Corrigé : libsemanage/2.0.25-3) Bogues de gravité critical sur libaudiofile0 (0.2.6-6 - 0.2.6-7) pending #510205 - buffer overflow in libaudiofile Bogues de gravité critical sur iceweasel (2.0.0.18-0etch1 - 3.0.4-1) pending #510902 - Missing security updates - version 2.0.0.20 available from upstream Bogues de gravité grave sur xserver-xorg (1:7.1.0-19 - 1:7.3+18) pending #511216 - Xorg crash (i810 ) Bogues de gravité grave sur util-linux (2.12r-19etch1 - 2.13.1.1-1) pending #510130 - Error calculing volhdr partition boundaries on SGI disklabel Bogues de gravité grave sur libqt3-mt (3:3.3.7-4etch2 - 3:3.3.8b-5) pending #490999 - libqt3-mt: QTime::addMSecs(int) is compiled wrongly on sparc Bogues de gravité grave sur grub (0.97-27etch1 - 0.97-47lenny1) pending #243835 - grub-install hangs with xfs root/boot Réuni avec : 239111 246111 309218 425367 Bogues de gravité grave sur cupsys (1.2.7-4etch6 - 1.3.8-1lenny4) pending #510857 - cupsys: cups print jobs hang since upgrade to Etch Bogues de gravité serious sur perl (5.8.8-7etch6 - 5.10.0-18) pending #477694 - FTBFS: ext/threads/t/stress_re.t fails sporadically on sparc Bogues de gravité serious sur xserver-xorg-video-nv (1:2.0.3-1 - 1:2.1.10-1) pending #383465 - Contains obfuscated source code, DFSG violation? Bogues de gravité serious sur liferea (1.0.27-2 - 1.4.18-1+b1) pending #510765 - liferea-webkit: Liferea should not provide webkit in a stable release Bogues de gravité serious sur portmap (5-26 - 6.0-9) pending #424957 - portmap includes non-DFSG-compliant code Bogues de gravité serious sur python (2.4.4-2 - 2.5.2-3) pending #418462 - mailman: Fails to upgrade from Sarge to Etch Bogues de gravité serious sur system-tools-backends (1.4.2-3 - 2.6.0-2) pending #510744 - system-tools-backends: /etc/dbus-1/system.d file needs alterations for fd.o #18961 Bogues de gravité serious sur texlive-base (- 2007.dfsg.1-4) pending #477060 - texlive-base: license of amslatex is unclear Bogues de gravité serious sur libsnmp-base (5.2.3-7etch4 - 5.4.1~dfsg-12) pending #498475 - libsnmp-base ships MIB files licensed under a restrictive license Résumé : xserver-xorg(1 bogue), util-linux(1
Re: Upgrade Etch/Lenny
Le jeudi 8 janvier 2009 19:15, Bernard a écrit : Messieurs bonsoir, Suite à l'utilisation de la commande apt-get -u dist-upgrade, je me retrouve avec la liste des erreurs suivantes : J'avoue être trés découragé sur ce coup. C'est ou que ça colle pas ? Souhaitant être en version testing/Lenny comment je fais ? Merci de vos réponses suremment pertinentes. Désolé, je ne peux t'aider mais je compatis. Je remarque que les Upgrade ne fonctionnent pas toujours et pire, ils cassent la version avant upgrade ! Je voulais le faire et j'ai bien fait, étant encore sous Etch. J'ai eu le même déboire lorsque j'ai voulu upgrader de Sarge vers Etch. Du coup, j'ai dû tout réinstaller directement avec un DVD etch. (mais quel boulot pour tout configurer : son, vidéo, compte emails ... etc ... !!) As tu fait une sauvegarde de ta précédente version ? J'aimerai connaître le moyen pour faire un upgrade sans trop de déboires. antoine -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
Bernard a écrit : Messieurs bonsoir, Suite à l'utilisation de la commande apt-get -u dist-upgrade, je me retrouve avec la liste des erreurs suivantes : 1030 mis à jour, 306 nouvellement installés, 15 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0o/1073Mo dans les archives. Après dépaquetage, 743Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer [O/n] ? o Lecture des champs des paquets... Fait Lecture de l'état des paquets... Fait Récupération des rapports de bogue... Fait Analyse des informations Trouvé/Corrigé... 65%dpkg : mauvaise syntaxe de la version « 2007-10-01T00:00:00Z » : l'époque (epoch) dans la version n'est pas un nombre Analyse des informations Trouvé/Corrigé... Fait Bogues de gravité grave sur openoffice.org-writer (2.0.4.dfsg.2-7etch6 - 1:2.4.1-15) forwarded #507865 - openoffice.org-writer: OOo 2.4.x openinig OOo 3 files doesn't show text (2.x implements standard wrong) Bogues de gravité grave sur nautilus (2.14.3-11+b1 - 2.20.0-7) forwarded #510564 - nautilus: smb file deletion gvfs Bogues de gravité grave sur procps (1:3.2.7-3 - 1:3.2.7-9) done #511082 - procps: sysctl Display all values function contain bogus debug printf() (Corrigé : procps/1:3.2.7-9.1) Bogues de gravité grave sur texlive-common (- 2007.dfsg.1-4) done #429753 - texlive-commong post-install action fails, blocking tex/latex install (Corrigé : 2007-10-01T00:00:00Z) Bogues de gravité grave sur python2.5 (- 2.5.2-14) done #509697 - python2.5 misses dependency on binutils (Corrigé : 2.5.2-15) Réuni avec : 509821 Bogues de gravité grave sur libpam-modules (0.79-5 - 1.0.1-4) done #502140 - cannot unlock screen during etch - lenny transition (Corrigé : pam/1.0.1-5) Bogues de gravité grave sur initramfs-tools (0.85i - 0.92n) done #511085 - 60 seconds timeout for ipconfig is not enough (Corrigé : initramfs-tools/0.92o) Bogues de gravité serious sur epiphany-browser (2.14.3-8 - 2.22.3-8) done #510764 - epiphany-webkit: Epiphany should not provide webkit in a stable release (Corrigé : epiphany-browser/2.22.3-9) Bogues de gravité serious sur hal (0.5.8.1-9etch1 - 0.5.11-6) done #510639 - hal.conf.in needs augmenting for new D-Bus (Corrigé : hal/0.5.11-7) Bogues de gravité serious sur ghostscript (- 8.62.dfsg.1-3.1) done #503712 - etch-lenny upgrade left the system in broken state (Corrigé : ghostscript/8.62.dfsg.1-3.2 ghostscript/8.63.dfsg.1-1 ghostscript/8.62.dfsg.1-3.2lenny0) Bogues de gravité serious sur policycoreutils (1.32-3 - 2.0.49-6) done #506727 - policycoreutils: fail with error: list index out of range (Corrigé : policycoreutils/2.0.49-8) Bogues de gravité serious sur libsemanage1 (1.8-1 - 2.0.25-2) done #510134 - genhomedircon.c: login.defs:MAX_UID have no effect on generating list of valid users, but MIN_UID does have. (Corrigé : libsemanage/2.0.25-3) Bogues de gravité critical sur libaudiofile0 (0.2.6-6 - 0.2.6-7) pending #510205 - buffer overflow in libaudiofile Bogues de gravité critical sur iceweasel (2.0.0.18-0etch1 - 3.0.4-1) pending #510902 - Missing security updates - version 2.0.0.20 available from upstream Bogues de gravité grave sur xserver-xorg (1:7.1.0-19 - 1:7.3+18) pending #511216 - Xorg crash (i810 ) Bogues de gravité grave sur util-linux (2.12r-19etch1 - 2.13.1.1-1) pending #510130 - Error calculing volhdr partition boundaries on SGI disklabel Bogues de gravité grave sur libqt3-mt (3:3.3.7-4etch2 - 3:3.3.8b-5) pending #490999 - libqt3-mt: QTime::addMSecs(int) is compiled wrongly on sparc Bogues de gravité grave sur grub (0.97-27etch1 - 0.97-47lenny1) pending #243835 - grub-install hangs with xfs root/boot Réuni avec : 239111 246111 309218 425367 Bogues de gravité grave sur cupsys (1.2.7-4etch6 - 1.3.8-1lenny4) pending #510857 - cupsys: cups print jobs hang since upgrade to Etch Bogues de gravité serious sur perl (5.8.8-7etch6 - 5.10.0-18) pending #477694 - FTBFS: ext/threads/t/stress_re.t fails sporadically on sparc Bogues de gravité serious sur xserver-xorg-video-nv (1:2.0.3-1 - 1:2.1.10-1) pending #383465 - Contains obfuscated source code, DFSG violation? Bogues de gravité serious sur liferea (1.0.27-2 - 1.4.18-1+b1) pending #510765 - liferea-webkit: Liferea should not provide webkit in a stable release Bogues de gravité serious sur portmap (5-26 - 6.0-9) pending #424957 - portmap includes non-DFSG-compliant code Bogues de gravité serious sur python (2.4.4-2 - 2.5.2-3) pending #418462 - mailman: Fails to upgrade from Sarge to Etch Bogues de gravité serious sur system-tools-backends (1.4.2-3 - 2.6.0-2) pending #510744 - system-tools-backends: /etc/dbus-1/system.d file needs alterations for fd.o #18961 Bogues de gravité serious sur texlive-base (- 2007.dfsg.1-4) pending #477060 - texlive-base: license of amslatex is unclear Bogues de gravité serious sur libsnmp-base (5.2.3-7etch4 - 5.4.1~dfsg-12) pending #498475 - libsnmp-base ships MIB files licensed under a restrictive license Résumé :
Re: Upgrade Etch/Lenny
Mon sources.list sans fichier preferences : # lenny deb http://ftp.fr.debian.org/debian/ testing main contrib non-free deb-src http://ftp.fr.debian.org/debian/ testing main contrib non-free # security deb http://security.debian.org/ testing/updates main contrib non-free deb-src http://security.debian.org/ testing/updates main contrib non-free Si je lance la mise à jour, il m'affiche tout un tas de warning concernant perl apparemment, et je me retrouve avec une distro cassée ! J'ai essayé le fichier sources.list et le fichier préférences LennyEtchSidExperimental du forum : http://forum.debian-fr.org/viewtopic.php?f=8t=5659 mais sans succés. J'avoue être trés découragé sur ce coup. C'est ou que ça colle pas ? Souhaitant être en version testing/Lenny comment je fais ? Merci de vos réponses suremment pertinentes. Avant de faire l'upgrade être sûr d'avoir un etch correct avec toutes les mises à jour faites. J'ai l'impression qu'il y a encore des références à sarge !!! Donc remplacer les testing par etch dans sources.list et faire un aptitude update; aptitude dist-upgrade. Vérifier que tous les paquets sont bien mis à jour (qu'il n'ya pas de paquets bloqués ...) Ensuite remplacer etch par lenny dans sources.list et faire : aptitude update aptitude install aptitude aptitude dist-upgrade J'ai déjà fait 3 ou 4 upgrades sans trop de problèmes avec cette méthode. L'essentiel des soucis que j'ai rencontré gravitent autour du xorg.conf -- Guy -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
J'ai déjà fait 3 ou 4 upgrades sans trop de problèmes avec cette méthode. L'essentiel des soucis que j'ai rencontré gravitent autour du xorg.conf - Merci de ces bons conseils et précisions. Quel soucis as tu eu avec xorg.conf ? : Il n'y avait plus de mode graphique ? Comment les as tu résolus ? car je compte faire un upgrade et avant je m'informe, je suis vacciné d'échecs ... :-) antoine -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
Bonsoir, Pourquoi cette ligne : aptitude install aptitude ? Bonne soire tous, Guy Roussin a crit: Mon sources.list sans fichier preferences : # lenny deb http://ftp.fr.debian.org/debian/ testing main contrib non-free deb-src http://ftp.fr.debian.org/debian/ testing main contrib non-free # security deb http://security.debian.org/ testing/updates main contrib non-free deb-src http://security.debian.org/ testing/updates main contrib non-free Si je lance la mise jour, il m'affiche tout un tas de warning concernant perl apparemment, et je me retrouve avec une distro casse ! J'ai essay le fichier sources.list et le fichier prfrences LennyEtchSidExperimental du forum : http://forum.debian-fr.org/viewtopic.php?f=8t=5659 mais sans succs. J'avoue tre trs dcourag sur ce coup. C'est ou que a colle pas ? Souhaitant tre en version testing/Lenny comment je fais ? Merci de vos rponses suremment pertinentes. Avant de faire l'upgrade tre sr d'avoir un etch correct avec toutes les mises jour faites. J'ai l'impression qu'il y a encore des rfrences sarge !!! Donc remplacer les "testing" par "etch" dans sources.list et faire un aptitude update; aptitude dist-upgrade. Vrifier que tous les paquets sont bien mis jour (qu'il n'ya pas de paquets bloqus ...) Ensuite remplacer "etch" par "lenny" dans sources.list et faire : aptitude update aptitude install aptitude aptitude dist-upgrade J'ai dj fait 3 ou 4 upgrades sans trop de problmes avec cette mthode. L'essentiel des soucis que j'ai rencontr gravitent autour du xorg.conf -- Guy -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs "From" et "Reply-To:" To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
On Thu, Jan 08, 2009 at 07:56:23PM +0100, anto...@starinux.org anto...@starinux.org wrote a message of 39 lines which said: Je remarque que les Upgrade ne fonctionnent pas toujours et pire, ils cassent la version avant upgrade ! Jamais eu de problème similaire mais, de toute façon, lenny n'est pas sortie encore. C'est une version de test. Donc, mettez à jour si vous voulez mais soyez prévenu ! J'aimerai connaître le moyen pour faire un upgrade sans trop de déboires. 0) SAUVEGARDES SAUVEGARDES SAUVEGARDES AI-JE DIT QU'IL FALLAIT FAIRE DES SAUVEGARDES ? 1) Éditer /etc/apt/sources.list 2) aptitude update 3) aptitude install aptitude (car la mise à jour doit se faire avec un aptitude récent) 4) aptitude dist-upgrade (en quatrième surtout pas en premier) Et j'en ai mis des machines à jour comme ça. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
Bonsoir, Pourquoi cette ligne : aptitude install aptitude ? Pour utiliser la version lenny de aptitude à la ligne suivante ... (dist-upgrade) Guy -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
anto...@starinux.org a écrit : J'ai déjà fait 3 ou 4 upgrades sans trop de problèmes avec cette méthode. L'essentiel des soucis que j'ai rencontré gravitent autour du xorg.conf - Merci de ces bons conseils et précisions. Quel soucis as tu eu avec xorg.conf ? : Un probleme avec la souris, j'ai remis les paramètres de la version etch du xorg.conf de la section InputDevice correspondante. Un probleme avec openchrome qui est maintenant pris en charge par lenny et que je m'évertuais à recompiler alors qu'il suffisait d'indiquer driver openchrome Donc pas de graphique et petit passage en console ... La mise à jour peut te prendre 1 heure dans le meilleur des cas. Je constate que la présence de logiciels proprio (drivers, ...) ou compilés à la main rendent plus difficile la mise à jour. Et puis pas d'inquiétude ... on est là ;-) Depuis le temps que je fais des install et des mises à jours avec debian je n'ai jamais eu besoin de réinstaller (sauf lors de pannes disques) : merci la liste :-) Guy -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade Etch/Lenny
Bernard a écrit : Messieurs bonsoir, Suite à l'utilisation de la commande apt-get -u dist-upgrade, je me retrouve avec la liste des erreurs suivantes : 1030 mis à jour, 306 nouvellement installés, 15 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0o/1073Mo dans les archives. Après dépaquetage, 743Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer [O/n] ? o Lecture des champs des paquets... Fait Lecture de l'état des paquets... Fait Récupération des rapports de bogue... Fait Analyse des informations Trouvé/Corrigé... 65%dpkg : mauvaise syntaxe de la version « 2007-10-01T00:00:00Z » : l'époque (epoch) dans la version n'est pas un nombre Analyse des informations Trouvé/Corrigé... Fait Bogues de gravité grave sur openoffice.org-writer (2.0.4.dfsg.2-7etch6 - 1:2.4.1-15) forwarded #507865 - openoffice.org-writer: OOo 2.4.x openinig OOo 3 files doesn't show text (2.x implements standard wrong) Bogues de gravité grave sur nautilus (2.14.3-11+b1 - 2.20.0-7) forwarded #510564 - nautilus: smb file deletion gvfs Bogues de gravité grave sur procps (1:3.2.7-3 - 1:3.2.7-9) done #511082 - procps: sysctl Display all values function contain bogus debug printf() (Corrigé : procps/1:3.2.7-9.1) Bogues de gravité grave sur texlive-common (- 2007.dfsg.1-4) done #429753 - texlive-commong post-install action fails, blocking tex/latex install (Corrigé : 2007-10-01T00:00:00Z) Bogues de gravité grave sur python2.5 (- 2.5.2-14) done #509697 - python2.5 misses dependency on binutils (Corrigé : 2.5.2-15) Réuni avec : 509821 Bogues de gravité grave sur libpam-modules (0.79-5 - 1.0.1-4) done #502140 - cannot unlock screen during etch - lenny transition (Corrigé : pam/1.0.1-5) Bogues de gravité grave sur initramfs-tools (0.85i - 0.92n) done #511085 - 60 seconds timeout for ipconfig is not enough (Corrigé : initramfs-tools/0.92o) Bogues de gravité serious sur epiphany-browser (2.14.3-8 - 2.22.3-8) done #510764 - epiphany-webkit: Epiphany should not provide webkit in a stable release (Corrigé : epiphany-browser/2.22.3-9) Bogues de gravité serious sur hal (0.5.8.1-9etch1 - 0.5.11-6) done #510639 - hal.conf.in needs augmenting for new D-Bus (Corrigé : hal/0.5.11-7) Bogues de gravité serious sur ghostscript (- 8.62.dfsg.1-3.1) done #503712 - etch-lenny upgrade left the system in broken state (Corrigé : ghostscript/8.62.dfsg.1-3.2 ghostscript/8.63.dfsg.1-1 ghostscript/8.62.dfsg.1-3.2lenny0) Bogues de gravité serious sur policycoreutils (1.32-3 - 2.0.49-6) done #506727 - policycoreutils: fail with error: list index out of range (Corrigé : policycoreutils/2.0.49-8) Bogues de gravité serious sur libsemanage1 (1.8-1 - 2.0.25-2) done #510134 - genhomedircon.c: login.defs:MAX_UID have no effect on generating list of valid users, but MIN_UID does have. (Corrigé : libsemanage/2.0.25-3) Bogues de gravité critical sur libaudiofile0 (0.2.6-6 - 0.2.6-7) pending #510205 - buffer overflow in libaudiofile Bogues de gravité critical sur iceweasel (2.0.0.18-0etch1 - 3.0.4-1) pending #510902 - Missing security updates - version 2.0.0.20 available from upstream Bogues de gravité grave sur xserver-xorg (1:7.1.0-19 - 1:7.3+18) pending #511216 - Xorg crash (i810 ) Bogues de gravité grave sur util-linux (2.12r-19etch1 - 2.13.1.1-1) pending #510130 - Error calculing volhdr partition boundaries on SGI disklabel Bogues de gravité grave sur libqt3-mt (3:3.3.7-4etch2 - 3:3.3.8b-5) pending #490999 - libqt3-mt: QTime::addMSecs(int) is compiled wrongly on sparc Bogues de gravité grave sur grub (0.97-27etch1 - 0.97-47lenny1) pending #243835 - grub-install hangs with xfs root/boot Réuni avec : 239111 246111 309218 425367 Bogues de gravité grave sur cupsys (1.2.7-4etch6 - 1.3.8-1lenny4) pending #510857 - cupsys: cups print jobs hang since upgrade to Etch Bogues de gravité serious sur perl (5.8.8-7etch6 - 5.10.0-18) pending #477694 - FTBFS: ext/threads/t/stress_re.t fails sporadically on sparc Bogues de gravité serious sur xserver-xorg-video-nv (1:2.0.3-1 - 1:2.1.10-1) pending #383465 - Contains obfuscated source code, DFSG violation? Bogues de gravité serious sur liferea (1.0.27-2 - 1.4.18-1+b1) pending #510765 - liferea-webkit: Liferea should not provide webkit in a stable release Bogues de gravité serious sur portmap (5-26 - 6.0-9) pending #424957 - portmap includes non-DFSG-compliant code Bogues de gravité serious sur python (2.4.4-2 - 2.5.2-3) pending #418462 - mailman: Fails to upgrade from Sarge to Etch Bogues de gravité serious sur system-tools-backends (1.4.2-3 - 2.6.0-2) pending #510744 - system-tools-backends: /etc/dbus-1/system.d file needs alterations for fd.o #18961 Bogues de gravité serious sur texlive-base (- 2007.dfsg.1-4) pending #477060 - texlive-base: license of amslatex is unclear Bogues de gravité serious sur libsnmp-base (5.2.3-7etch4 - 5.4.1~dfsg-12) pending #498475 - libsnmp-base ships MIB files licensed under a restrictive license Résumé :
Problemes upgrade etch vers lenny
Bonsoir, Ce week end j'ai upgradé 2 PC de etch en lenny. Pour le premier pas de problemes, l'affaire a été réglé en une heure. Par contre pour le second je rencontre plusieurs difficultés. La plus importante provient du support de la souris dont le simple clic droit, centre ou gauche ne fonctionne pas correctement. C'est un peu comme si les simples clics se transformaient en double clic pour gnome. Le clic maintenu enfoncé fonctionne toujours. (tout cela quelquesoit l'utilisateur). J'ai même créé un nouvel utilisateur pour tester ... L'utilisation du PC est devenue très difficile. Plus moyen de cliquer dans le tableau de bord de gnome ou dans le menu des applications. Le copier/coller linux (selection/clic central) amène 2 copies du texte ... Toute idée sera la bienvenue ... Merci. Guy -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problemes upgrade etch vers lenny
Compléments d'infos sur ce probleme de souris : Sur le panneau de conf preferences de la souris le test du double clic marche à chaque coup avec un simple clic ! J'avais un message d'erreur mousetweaks nécessite l'activation des outils d'accessibilité lorsque j'essayais de cliquer une option sur le second onglet (accessibilité). La desinstallation de mousetweaks ne change pas les problèmes ... je ne sais si mon probleme de souris est lié à ce mousetweaks ? Guy PS: Au passage, j'ai réglé les autres problèmes que j'avais eu lors de cette mise à jour. Notamment j'avais pas remarqué la presence dans lenny d'un pilote X openchrome qui évite la compil à la mano d'openchrome comme avec etch ... merci lenny ! La plus importante provient du support de la souris dont le simple clic droit, centre ou gauche ne fonctionne pas correctement. C'est un peu comme si les simples clics se transformaient en double clic pour gnome. Le clic maintenu enfoncé fonctionne toujours. (tout cela quelquesoit l'utilisateur). J'ai même créé un nouvel utilisateur pour tester ... L'utilisation du PC est devenue très difficile. Plus moyen de cliquer dans le tableau de bord de gnome ou dans le menu des applications. Le copier/coller linux (selection/clic central) amène 2 copies du texte ... -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RESOLU] Probleme souris : upgrade etch vers lenny
Re-bonsoir, Pour mémoire, j'ai resolu mon problème de la façon suivante : La section InputDevice de la souris dans le fichier xorg.conf fraichement généré avait cette tête là : Section InputDevice IdentifierConfigured Mouse Drivermouse EndSection J'ai rajouté les 3 lignes suivantes (comme c'était en etch) Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 et maintenant la souris fonctionne correctement ... Mon problème est résolu mais ça me parait être un problème un peu génant lors de mises à jours vers lenny ... Guy Par contre pour le second je rencontre plusieurs difficultés. La plus importante provient du support de la souris dont le simple clic droit, centre ou gauche ne fonctionne pas correctement. C'est un peu comme si les simples clics se transformaient en double clic pour gnome. Le clic maintenu enfoncé fonctionne toujours. (tout cela quelquesoit l'utilisateur). J'ai même créé un nouvel utilisateur pour tester ... L'utilisation du PC est devenue très difficile. Plus moyen de cliquer dans le tableau de bord de gnome ou dans le menu des applications. Le copier/coller linux (selection/clic central) amène 2 copies du texte ... -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problemes upgrade etch vers lenny[pour info]
En ce qui me concerne, j'ai eu les soucis suivants (Dell inspiron 1525): * Paquet uswusp complètement non opérationnel sous lenny, il a fallu réinstaller celui de etch pour régler le problème. * keytouch a à reconfigurer complètement pour l'utilisateur. * xscreensaver qui passe mal avec la carte Intel, il a fallu réinstaller celui de etch. * Toujours le même souci d'hdparm et toujours le même souci lors d'un réveil. guessnet a changé son affichage mais semble fonctionner. Par contre, googleearth fonctionne enfin correctement en 64 bits sur xserver-xorg-intel. François Boisson -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ratowanie systemu po apt-get upgrade - etch
05-12-07, Marcin Bieniaszewski [EMAIL PROTECTED] napisał(a):
witam ponownie,
udalo mi sie poprosic aby zrobili manualny fsck - do wyskoczyla
konsola z prosba o haslo root. Po przejechaniu dysku fsck system
wstal.
tylko dlaczego po zwyklym upgradzie byly bledy na dysku
hmmm
wiem ze to wrozenie z kart ale co sadzicie o tej sytuacji ?
mysle ze miales po prostu bledy systmu plików .
--
Wojciech Ziniewicz
Unix SEX :{look;gawk;find;sed;talk;grep;touch;finger;find;fl
ex;unzip;head;tail; mount;workbone;fsck;yes;gasp;fsck;more;yes;yes;eje
ct;umount;makeclean; zip;split;done;exit:xargs!!;)}
Re: ratowanie systemu po apt-get upgrade - etch
witam ponownie, udalo mi sie poprosic aby zrobili manualny fsck - do wyskoczyla konsola z prosba o haslo root. Po przejechaniu dysku fsck system wstal. tylko dlaczego po zwyklym upgradzie byly bledy na dysku hmmm wiem ze to wrozenie z kart ale co sadzicie o tej sytuacji ? pozdrawiam Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ratowanie systemu po apt-get upgrade - etch
Witam, nie rozumiem co sie moglo stac, Debian stable etch pakiety pobierane z ftp.debian.org stable + security jadro debianowe z paczki dla amd64: 2.6.18 apt-get update pozniej apt-get upgrade wszystko przeszlo, kernel nie znalazl w /usr/modules/ jakims cudem tych od kernela 2.6.18 ... ale pozniej widze buduje sobie depmode skonczylo upgradowac, dalem update-grub, daje shutdown -r now i system nie wstaje czyli kernel zwariowal ? nie mam dostepu fizycznie w tym momencie do serwera. Co mozna wywrozyc z tej sytuacji ? dodam ze nie instalowalem pakietow z BUG-ami, zPinowalem te ktore mialy bugi i nie instalowalem ich. co radzicie ? czy starsza wersja kernela sprzed upgradu zostaje ? czy zostala zastapiona ? pozdrawiam Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ratowanie systemu po apt-get upgrade - etch
witaj, tez tak sadze, ale czy to takie normalne ze system dziala 60 dni poczym robie procedure upgradu bardzo ostroznie i po reboocie sa bledy systemu plikow ? moze cos sie nie zdazylo zamknac podczas shutdown ? pozdrawiam Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ratowanie systemu po apt-get upgrade - etch
05-12-07, Marcin Bieniaszewski [EMAIL PROTECTED] napisał(a):
witaj,
tez tak sadze, ale czy to takie normalne ze system dziala 60 dni
poczym robie procedure upgradu bardzo ostroznie i po reboocie sa bledy
systemu plikow ? moze cos sie nie zdazylo zamknac podczas shutdown ?
no dokladnie tak ;)
nie bedac na miejscu nie mozesz tego sprawdzic , ale szczerze mowiac
to prawie na pewno o to chodziło...
nie jestem oczywiscie wrózbitą ;)
--
Wojciech Ziniewicz
Unix SEX :{look;gawk;find;sed;talk;grep;touch;finger;find;fl
ex;unzip;head;tail; mount;workbone;fsck;yes;gasp;fsck;more;yes;yes;eje
ct;umount;makeclean; zip;split;done;exit:xargs!!;)}
Re: ratowanie systemu po apt-get upgrade - etch
On Wed, Dec 05, 2007 at 09:28:18PM +0100, Marcin Bieniaszewski wrote: tez tak sadze, ale czy to takie normalne ze system dziala 60 dni poczym robie procedure upgradu bardzo ostroznie i po reboocie sa bledy systemu plikow ? moze cos sie nie zdazylo zamknac podczas shutdown ? Normalnie, jak się ma zepsuty dysk -- niektóre błędy długo nie dają znać, a przy jakichś większych operacjach dyskowych (tu ściąganie i instalowanie większej liczby pakietów, jak sądzę) nagle się coś sypie... pzdr, jmb PS. Oczywiście powody mogą być inne, ale ten wydaje mi się najbardziej oczywistą możliwością... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade etch
Francesco, in order to move to 4.0 you just have to make sure your /etc/apt/sources.list points to stable or etch which is current stable release (a symbolic link to). This is a line of mine deb http://debian.fastweb.it/debian/ stable main contrib You can also run netselect-apt stable it will fetch and test the nearest mirrors for the stable release, and write a sources.list for you in current directory. You can safely replace your /etc/apt/sources.list with it, so you will be on stable/etch. running apt-get update apt-get -y upgrade, no new package will be installed from scratch exept for meeting dependencies, so GNOME won't be replaced by KDE and so on.. You can also run apt-get dist-upgrade. cheers raffaele 2007/4/25, Francesco Pietra [EMAIL PROTECTED]: Hope those who know will not be hurt by these naive questions in face of the extensive instructions on Debian website. I'm using i386 and amd64 etch. Now want to move to 4.0 etch, though I can't do that immediately because the amd64 machine is computing, while the i386 machine is ssh linked to the amd64 machine, collecting and analyzing data. That will last for at least three weeks more from now. Once ready, what should I do (besides backing up what is already indicated), in particular as to the repositories? Unfortunately I have to administer a complex system without having the formation of an administrator. Thanks for guidelines that, may be, will also serve for other naive guys. francesco pietra __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upgrade etch
Hope those who know will not be hurt by these naive questions in face of the extensive instructions on Debian website. I'm using i386 and amd64 etch. Now want to move to 4.0 etch, though I can't do that immediately because the amd64 machine is computing, while the i386 machine is ssh linked to the amd64 machine, collecting and analyzing data. That will last for at least three weeks more from now. Once ready, what should I do (besides backing up what is already indicated), in particular as to the repositories? Unfortunately I have to administer a complex system without having the formation of an administrator. Thanks for guidelines that, may be, will also serve for other naive guys. francesco pietra __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade etch
On Wed, 25 Apr 2007 02:50:18 -0700 (PDT) Francesco Pietra [EMAIL PROTECTED] wrote: Hope those who know will not be hurt by these naive questions in face of the extensive instructions on Debian website. I'm sure they won't be :-) I'm using i386 and amd64 etch. Now want to move to 4.0 etch, Please be aware that etch *is* version 4.0. Could you please verify what version you are running at the moment? The contents of /etc/debian_version will tell you. -- Liam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: upgrade etch
I forgot to ask how to prevent that during upgrading: ---X (and KDE/GNOME) are added to amd64? ---GNOME in i386 is replaced by KDE? ---iceweasel in i386 is replaced by GNOME's browser (which lacks remote control, thus not serving my needs) Thanks francesco --- Francesco Pietra [EMAIL PROTECTED] wrote: Date: Wed, 25 Apr 2007 02:50:18 -0700 (PDT) From: Francesco Pietra [EMAIL PROTECTED] Subject: upgrade etch To: debian-users debian-user@lists.debian.org Hope those who know will not be hurt by these naive questions in face of the extensive instructions on Debian website. I'm using i386 and amd64 etch. Now want to move to 4.0 etch, though I can't do that immediately because the amd64 machine is computing, while the i386 machine is ssh linked to the amd64 machine, collecting and analyzing data. That will last for at least three weeks more from now. Once ready, what should I do (besides backing up what is already indicated), in particular as to the repositories? Unfortunately I have to administer a complex system without having the formation of an administrator. Thanks for guidelines that, may be, will also serve for other naive guys. francesco pietra __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade etch
On Wed, Apr 25, 2007 at 12:00:16PM +0100, Liam O'Toole wrote: On Wed, 25 Apr 2007 02:50:18 -0700 (PDT) Francesco Pietra [EMAIL PROTECTED] wrote: I'm using i386 and amd64 etch. Now want to move to 4.0 etch, Please be aware that etch *is* version 4.0. Could you please verify what version you are running at the moment? The contents of /etc/debian_version will tell you. You could also send us the contents of the /etc/apt/sources.list files from both computers. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
