Fw: Errors on upgrading from etch to lenny
in [Debian]
|
From: Francesco Pietra on 6 May 2008 10:20 Hi: The full error message is: deb32:/home/francesco# apt-get install -f Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded. 5 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up exim4-daemon-light (4.69-2+b1) ... Starting MTA:exim: incompatible command-line options or arguments invoke-rc.d: initscript exim4, action "start" failed. dpkg: error processing exim4-daemon-light (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of at: at depends on mail-transport-agent; however: Package mail-transport-agent is not installed. Package exim4-daemon-light which provides mail-transport-agent is not configured yet. dpkg: error processing at (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of exim4: exim4 depends on exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-custom; however: Package exim4-daemon-light is not configured yet. Package exim4-daemon-heavy is not installed. Package exim4-daemon-custom is not installed. dpkg: error processing exim4 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of bsd-mailx: bsd-mailx depends on exim4 | mail-transport-agent; however: Package exim4 is not configured yet. Package mail-transport-agent is not installed. Package exim4-daemon-light which provides mail-transport-agent is not configured yet. dpkg: error processing bsd-mailx (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of mailx: mailx depends on bsd-mailx; however: Package bsd-mailx is not configured yet. dpkg: error processing mailx (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: exim4-daemon-light at exim4 bsd-mailx mailx E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks francesco pietra --- On Tue, 5/6/08, Florian Kulzer <florian.kulzer+debian(a)icfo.es> wrote: > From: Florian Kulzer <florian.kulzer+debian(a)icfo.es> > Subject: Re: Fw: Errors on upgrading from etch to lenny > To: debian-user(a)lists.debian.org > Cc: chiendarret(a)yahoo.com > Date: Tuesday, May 6, 2008, 1:13 AM > On Tue, May 06, 2008 at 00:08:35 -0700, Francesco Pietra > wrote: > > Hi: > > I wonder whether the debian-user list is still active. > When posting > > for help at the amd64 list, even from inexperienced > users, the amd64 > > list usually provides help overnight. > > > > See please my request for help below to the > debian-users list. > > Unanswered. > > Your original message (17:28:33 UTC): > http://lists.debian.org/debian-user/2008/05/msg00201.html > > An answer (18:07:33 UTC): > http://lists.debian.org/debian-user/2008/05/msg00204.html > > Maybe you missed the answer because you expected to get a > CC to your own > email address and therefore you did not follow the list > closely enough. > The fact that your messages have a Reply-To header pointing > to your own > email address does not mean that you will automatically be > CC'd if > somebody replies to the list. You have to explicitly ask to > be CC'd or > you have to include an appropriate Mail-Followup-To header. > > I am CC'ing you now to make sure that you get this > message, even though > this is technically a violation of the list policy. I > assume this is > what you wanted, since I cannot otherwise see the point of > generating a > Reply-To header that is identical to the From address. > > > Notice, please, that no such errors came out when > > upgrading from etch to lenny with amd64. > > > > Of course I understand that a general list such as > debian-users may be > > very crowded. Therefore, this is just a respectfully > remind. Must add > > that I tried all obvious resources to resolve the > issue, such as > > "apt-get -f install" and others, without > success. > > It seems be bug #477258, which has been fixed in Sid since > April 25, > exim4 version 4.69-3. The bug report describes how to > repair the init > script yourself. (So far the fix did not propagate to Lenny > because > there have been further updates in Sid, restarting the 10 > days waiting > period.) > > -- > Regards, | http://users.icfo.es/Florian.Kulzer > Florian | ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Paul Cartwright on 7 May 2008 08:10 On Wed May 7 2008, Teodor wrote: > This bug #476987 is fixed in the exim4-base from sid. I fixed this > yesterday like this: > # apt-get -t sid install exim4-base > > The transition to lenny is mainly blocked by the perl5.10 transition. I am running Lenny, and I tried that: #apt-get update <SNIP> # apt-get -t sid install exim4-base Reading package lists... Done Building dependency tree Reading state information... Done exim4-base is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. 2 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up exim4-daemon-light (4.69-2+b1) ... Starting MTA:exim: incompatible command-line options or arguments invoke-rc.d: initscript exim4, action "start" failed. dpkg: error processing exim4-daemon-light (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of exim4: exim4 depends on exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-custom; however: Package exim4-daemon-light is not configured yet. Package exim4-daemon-heavy is not installed. Package exim4-daemon-custom is not installed. dpkg: error processing exim4 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: exim4-daemon-light exim4 E: Sub-process /usr/bin/dpkg returned an error code (1) -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Florian Kulzer on 7 May 2008 08:40 On Wed, May 07, 2008 at 07:04:46 -0400, Paul Cartwright wrote: > On Wed May 7 2008, Teodor wrote: > > This bug #476987 is fixed in the exim4-base from sid. I fixed this > > yesterday like this: > > # apt-get -t sid install exim4-base > > > > The transition to lenny is mainly blocked by the perl5.10 transition. > > I am running Lenny, and I tried that: > #apt-get update > <SNIP> > # apt-get -t sid install exim4-base > Reading package lists... Done > Building dependency tree > Reading state information... Done > exim4-base is already the newest version. My guess is that you do not have "sid" in your sources.list, therefore apt-get ignores the "-t sid" part and tells you that the newest version it knows about (i.e. the one from Lenny) is already installed. > 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. > 2 not fully installed or removed. > After this operation, 0B of additional disk space will be used. > Setting up exim4-daemon-light (4.69-2+b1) ... > Starting MTA:exim: incompatible command-line options or arguments > invoke-rc.d: initscript exim4, action "start" failed. > dpkg: error processing exim4-daemon-light (--configure): > subprocess post-installation script returned error exit status 1 > dpkg: dependency problems prevent configuration of exim4: > exim4 depends on exim4-daemon-light | exim4-daemon-heavy | > exim4-daemon-custom; however: > Package exim4-daemon-light is not configured yet. > Package exim4-daemon-heavy is not installed. > Package exim4-daemon-custom is not installed. > dpkg: error processing exim4 (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > exim4-daemon-light > exim4 > E: Sub-process /usr/bin/dpkg returned an error code (1) -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Paul Cartwright on 7 May 2008 09:00 On Wed May 7 2008, Florian Kulzer wrote: > > # apt-get -t sid install exim4-base > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > exim4-base is already the newest version. > > My guess is that you do not have "sid" in your sources.list, therefore > apt-get ignores the "-t sid" part and tells you that the newest version > it knows about (i.e. the one from Lenny) is already installed. correct. I guess I didn't read the MAN on apt-get -t to understand.. I thought that would look for sid sources. So.. I have to add sid sources to souirces.list, do an apt-get update, then run that command.. then take sid sources back out. Is there one specific source I can add/change to sid to get the exim package? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrei Popescu on 7 May 2008 13:10
On Wed, May 07, 2008 at 08:57:38AM -0400, Paul Cartwright wrote: > correct. I guess I didn't read the MAN on apt-get -t to understand.. I thought > that would look for sid sources. So.. I have to add sid sources to > souirces.list, do an apt-get update, then run that command.. then take > sid sources back out. Safer would be to echo 'APT::Default-Release "testing";' > /etc/apt/apt.conf.d/default-release assuming that file does *not* exist. Beware, you *must not* use code names here. >Is there one specific source I can add/change to sid to get the exim >package? Just copy your lenny line and change lenny to sid. After you do that run 'apt-cache policy'. It should show lenny with a priority of 990 and sid with 500 (if you do the trick suggested above). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) |