Only, if I try and upgrade just the linstaller packages, it pulls in a new kernel as well, as linstaller-modules-base has a heap of dependencies, which eventually equal the new kernel being pulled down as well, which in turn causes the ext4 issues mentioned above:
You didn’t set a mount point. Thus it won’t be written in /etc/fstab, which in effect, is the same as not having a swap partition at all.
Also, just for the information, not having a swap won’t prevent the installation from continuing! You just neeed to press “Forward” button twice.
Yep, same issue as the last time.
ext4 module from the new kernel being loaded on the older ( running ) one.
You didn’t mention which ISO you were using ( I guess it’s RC1 )…?
Anyway, installer shouldn’t pull a new kernel.
Tested on RC1:
[[email protected]][~]$ sudo apt-get install linstaller linstaller-config-trios linstaller-frontend-cli linstaller-frontend-glade linstaller-modules-base linstaller-session live-config-linstaller
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
cgmanager libcgmanager0 libnih-dbus1 libnih1
Use ‘apt-get autoremove’ to remove them.
The following packages will be upgraded: linstaller linstaller-config-trios linstaller-frontend-cli
linstaller-frontend-glade linstaller-modules-base linstaller-session
live-config-linstaller 7 upgraded, 0 newly installed, 0 to remove and 536 not upgraded.
Need to get 401 kB of archives.
[[email protected]][~]$ apt-cache policy linstaller linux-image-3.16.0-4-amd64 linstaller:
*** 7.0.6~mia3 0
1001 Index of /trios/mia/ mia/main amd64 Packages
100 /var/lib/dpkg/status linux-image-3.16.0-4-amd64:
500 Debian – Security Information jessie/updates/main amd64 Packages
500 Index of /debian jessie/main amd64 Packages
*** 3.16.7-ckt2-1 0
So, please, update the installer by using the command I’ve listed here and there shoudn’t be any problems.
Otherwise if you spot that a new kernel is going to be installed, stop there and post the used apt command and it’s output here, so that we can find out why is it happening.
@ no mount point:
Yup, thats correct, I didn’t set a mount point, as its a swap volume…
Ended up hitting forward twice, and as I said, that worked, but then I hit the ext4 error again.
I’m using the RC1 iso, as bandwidth is not great here. Once I’ve booted off the RC1 iso, I’m updating the apt keys/repos etc and performing the install
Ok, I can see what’s going on here now. Sorry for wasting your time. Didn’t realise that apt-get upgrade grabbed all available updates, not just those specified, unlike apt-get install… Guess I needed to RTFM a little better.