It seems 4.2 image was published, it seems file of kernel and dtb for cubietruck is not prepared, I think there is a reason?

Best regards.

I produce some bug in the middle of the publishing process ... now I need to rebuild most images which are going to be rebuild / updated during the night. The rest (packages and repository) when everything is done and when I got some sleep

 

I'll publish some text about changes and than it's officially online 

OK

It is waiting to be updated.

By the way, does this will be able to update from the apt command?

Best regards.

Yes, now everything will be updated via apt-get. That's also the reason why there is no new .tar package and why I have a lot of extra manual work with this release. Not only the kernel and OS but also "the big picture" - build script was rewritten totally.

Next kernel update will be done fully auto on Jessie and half on Wheezy - you'll only need to issue apt-get upgrade command. If you don't want this, you will need to disable it. If you are running old kernel you will stay there and vice versa. Updating will be done within kernel family.

 

I also reduce / combine kernels down to minimum. There are 6 different kernels for all boards now, 4 x legacy: sunxi for majority, special for banana, lamobo and orange, cubox, udoo and 2 x mainline: sunxi and udoo

 

P.S.

Building process is half done.

Upgrade for advanced users is ready:

 

Repository: apt.armbian.com

Key: http://apt.armbian.com/armbian.key

 

Add to sources if not there:

deb http://apt.armbian.com $(lsb_release -cs) main

Packages naming logic:

Kernel 3.4:

linux-u-boot-DEVICE_NAME (cubieboard, cubietruck, lime, ...)
linux-image-sunxi (all) or linux-image-banana (for boards bananapi, orange, lamobo r1)
linux-headers-sunxi or linux-headers-banana (for boards bananapi, orange, lamobo r1)
linux-firmware-image-sunxi or linux-firmware-image-banana (for boards bananapi, orange, lamobo r1)
linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...)

Mainline stable kernel:

linux-u-boot-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...)
linux-image-next-sunxi 
linux-headers-next-sunxi
linux-firmware-image-next-sunxi
linux-dtb-next-sunxi
linux-$(lsb_release -cs)-root-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...)

Mainline latest kernel:

linux-image-dev-sunxi (not implemented yet)

If you don't understand what's written above wait for official release together with update script which will fix this for you. Currently under testing.

Hi,

 

I was about to try this on my cubietruck :

nsteinmetz@or-azur:~$ sudo apt install linux-dtb-next-sunxi  linux-image-next-sunxi  linux-firmware-image-next-sunxi linux-headers-next-sunxi  linux-image-next-sunxi  linux-jessie-root-next-cubietruck linux-u-boot-cubietruck-next

But I have as result :

Selecting previously unselected package linux-dtb-next-sunxi.
(Reading database ... 48345 files and directories currently installed.)
Preparing to unpack .../linux-dtb-next-sunxi_4.2_armhf.deb ...
Unpacking linux-dtb-next-sunxi (4.2) ...
dpkg: error processing archive /var/cache/apt/archives/linux-dtb-next-sunxi_4.2_armhf.deb (--unpack):
 trying to overwrite '/boot/dtb/sun5i-a10s-r7-tv-dongle.dtb', which is also in package linux-dtb-4.1.2-cubietruck 4.0
Selecting previously unselected package linux-firmware-image-next-sunxi.
Preparing to unpack .../linux-firmware-image-next-sunxi_4.2_armhf.deb ...
Unpacking linux-firmware-image-next-sunxi (4.2) ...
Selecting previously unselected package linux-headers-next-sunxi.
Preparing to unpack .../linux-headers-next-sunxi_4.2_armhf.deb ...
Unpacking linux-headers-next-sunxi (4.2) ...
Selecting previously unselected package linux-jessie-root-next-cubietruck.
Preparing to unpack .../linux-jessie-root-next-cubietruck_4.2_armhf.deb ...
Unpacking linux-jessie-root-next-cubietruck (4.2) ...
dpkg: error processing archive /var/cache/apt/archives/linux-jessie-root-next-cubietruck_4.2_armhf.deb (--unpack):
 trying to overwrite '/etc/bash.bashrc.custom', which is also in package linux-jessie-root-cubietruck 4.2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
E: Sub-process /usr/bin/dpkg returned an error code (1)

So what's the best way to use mainline kernel (if adapted) ?

 

Thanks,

Nicolas

Only remove old conflicting packages, repeat install and you are done.

 

Wrote on mobile phone

Ok, thanks.

 

For the record, it leads to removing also :

Removing apt-transport-https (1.0.9.8) ...
Removing cmake (3.0.2-1) ...
Removing curl (7.38.0-4+deb8u2) ...
Removing mailutils (1:2.99.98-2) ...
Removing git (1:2.1.4-2.1) ...
Removing libcurl3:armhf (7.38.0-4+deb8u2) ...
Removing libcurl3-gnutls:armhf (7.38.0-4+deb8u2) ...
Removing libldap-2.4-2:armhf (2.4.40+dfsg-1) ...
Removing linux-dtb-4.1.2-cubietruck (4.0) ...
Removing linux-jessie-root-cubietruck (4.2) ...

Which I reinstalled later as they are not installed with new packages.

 

A reboot later and it seems it works as expected and seems some error I had on boot time are also fixed

uname -a
Linux or-azur 4.1.6-sunxi #22 SMP Tue Aug 25 17:54:51 CEST 2015 armv7l GNU/Linux

Have a nice day.