[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

dpkg-preconfigure : pb de compilation ???



Bonjour à tous,

juste une question, je viens de réaliser le passage de Sarge en Sid, et, en 
grand maladroit, j'ai simplement fait un "apt-get upgrade" au lieu du 
recommandé "apt-get dist-upgrade".
J'ai lancé immédiatement après un "apt-get dist-upgrade" (au cas où) mais 
depuis, à chaque installation de package, j'obtiens le message suivant :

--------------
String found where operator expected at /usr/sbin/dpkg-preconfigure line 96, 
near "die sprintf(gettext(""
  (Might be a runaway multi-line "" string starting on line 94)
        (Missing semicolon on previous line?)
Bareword found where operator expected at /usr/sbin/dpkg-preconfigure line 96, 
near "die sprintf(gettext("debconf"
        (Do you need to predeclare die?)
Unquoted string "debconf" may clash with future reserved word 
at /usr/sbin/dpkg-preconfigure line 96.
String found where operator expected at /usr/sbin/dpkg-preconfigure line 103, 
near "gettext(""
  (Might be a runaway multi-line "" string starting on line 96)
        (Missing semicolon on previous line?)
Bareword found where operator expected at /usr/sbin/dpkg-preconfigure line 
104,near "$package, $confmodule"
  (Might be a runaway multi-line ff string starting on line 103)
        (Missing operator before dule?)
Unquoted string "dule" may clash with future reserved word 
at /usr/sbin/dpkg-preconfigure line 104.
syntax error at /usr/sbin/dpkg-preconfigure line 96, near "die 
sprintf(gettext(""
Unmatched right curly bracket at /usr/sbin/dpkg-preconfigure line 108, at end 
of line
syntax error at /usr/sbin/dpkg-preconfigure line 108, near "}"
Execution of /usr/sbin/dpkg-preconfigure aborted due to compilation errors.
-----------------

Question : est-ce un bug de dpkg dans la sid, ou est-ce du à ma mauvaise manip 
lors du passage de sarge à sid.
Bonus : comment réparer ça, parce que, du coup, je n'ai plus accès à la 
pré-configuration des packages avant installation ...



Reply to: