beta2

[numanoids]

(18th Oct, 2013 02:45 AM)mk01 Wrote:  @numanoids

the initscripts issue was anticipated, wasn't it? And I posted the solution so again

Code:

rm -f /etc/init.d/mountall*
insserv -f
apt-get upgrade (again)

apt-get upgrade will continue where stopped before.

Terminal

Preconfiguring packages ...
Setting up initscripts (2.88dsf-41+deb7u1) ...
(Reading database ... 29603 files and directories currently installed.)
Preparing to replace tzdata 2013c-0wheezy1 (using .../tzdata_2013d-0wheezy1_all.deb) ...
Unpacking replacement tzdata ...
Setting up tzdata (2013d-0wheezy1) ...

Current default time zone: 'Etc/UTC'
Local time is now: Thu Oct 17 16:43:45 UTC 2013.
Universal Time is now: Thu Oct 17 16:43:45 UTC 2013.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(Reading database ... 29603 files and directories currently installed.)
Preparing to replace libbind9-80 1:9.8.4.dfsg.P1-6+nmu2 (using .../libbind9-80_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u1_armhf.deb) ...
Unpacking replacement libbind9-80 ...
Setting up libbind9-80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u1) ...
(Reading database ... 29603 files and directories currently installed.)
Preparing to replace libdns88 1:9.8.4.dfsg.P1-6+nmu2 (using .../libdns88_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u1_armhf.deb) ...
Unpacking replacement libdns88 ...
Setting up libdns88 (1:9.8.4.dfsg.P1-6+nmu2+deb7u1) ...
(Reading database ... 29603 files and directories currently installed.)
Preparing to replace libisccfg82 1:9.8.4.dfsg.P1-6+nmu2 (using .../libisccfg82_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u1_armhf.deb) ...
Unpacking replacement libisccfg82 ...
Setting up libisccfg82 (1:9.8.4.dfsg.P1-6+nmu2+deb7u1) ...
(Reading database ... 29603 files and directories currently installed.)
Preparing to replace liblwres80 1:9.8.4.dfsg.P1-6+nmu2 (using .../liblwres80_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u1_armhf.deb) ...
Unpacking replacement liblwres80 ...

Sorry, no, on another thread you said not to worry about it!

"For sure you will hit the issue if updating to Beta2 after the Debian packages were released - because the system is not Beta2 yet. In that case you can happily leave package unconfigured dpkg should be able to roll other packages. Once beta2 finishes install the initscripts package should be pass configuration step without problems. "

dpkg was NOT able to roll the other packages without something being done to deal with initscripts but now you say to deal with it so you can understand my frustration when there isn't a clear consistent response to what is clearly a regular problem for people who end up spending a lot of time trying to get it working!

Perhaps an update to Post 1 would be in order to deal with this is all sorted out.