I am building a full image for the OPiPC. For the most part everything works. I do get one error while running compile.sh The error I see during build is:

"W: Failed to fetch http://apt.armbian.com/dists/jessie/InRelease  Unable to find expected entry 'jessie-utils/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

 

I am building on a VMware vm running Linux armbian 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I did the clone from the git repository and ran compile.sh as root.

I selected:

Full OS image for flashing

Do not change the kernel configuration

orangepipc

next Mainline (@kernel.org) (4.x)

jessie Debian 8 Jessie

Image with console interface (server)

The image does create and boot when burned to a SD

I get deb http://apt.armbian.com jessie main jessie-utils jessie-desktop in /etc/apt/sources.list.d/armbian.list which generates a error on apt-get update.

 

Did I miss something during the build?

Are there any logs I need to post.

 

Thanks, Steve

Change jessie-utils to jessie and it should work. This problem will be addressed at next major update. 

BTW. Perhaps you could try building Stretch.

I should have added that I did make the change in the resulting image. 

Thanks, for the info.

 

Steve

It's a known issue. Package repository management is a bit clumsy and that's why I rather wait for a major upgrade, where I have to deal with this in any case. I hope you are aware that you are building image with unfinished 4.13.x kernel - this one does not have thermal protection yet. You should not be using it for real yet.

18 minutes ago, Igor said:

Change jessie-utils to jessie and it should work. This problem will be addressed at next major update. 

BTW. Perhaps you could try building Stretch.

I would be happy to build Stretch. I did not see the option. Please point me to the info.

Use build switch EXPERT="yes"

Nice!

Building now. I am just testing for now so I will be aware of the thermal issue with the kernel. Can the EXPERT switch be added to the config-default.conf?

Just now, N4IRS said:

Building now. I am just testing for now so I will be aware of the thermal issue with the kernel.

 

 

o.k. We expect those features within 1-2 month so you will be able to upgrade.

 

1 minute ago, N4IRS said:

Can the EXPERT switch be added to the config-default.conf?

 

 

yes. 

I'm still building, I am seeing this in the console:

Setting up python3 (3.5.3-1) ...
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 384
Setting up python3-gi (3.22.0-2) ...
 

Just a example I think ever qemu error is 384.

 

 

AFAIK those qemu glitches are harmless. After the building is done, check output/debug/*.log files for a sign of troubles. 

Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-spi-spl-fit-support.patch
patch unexpectedly ends in middle of line

Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-sunxi-gpio-driver.patch
patch unexpectedly ends in middle of line
 

In patching.log

13 minutes ago, N4IRS said:

Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-spi-spl-fit-support.patch
patch unexpectedly ends in middle of line

Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-sunxi-gpio-driver.patch
patch unexpectedly ends in middle of line

This is not error, safe to ignore. Pay attention to "failed" and "error" ...

Just to be clear, I'm just getting used to the environment I'm not trying to put anything into production. If I break it, I get to keep both pieces.

I am a BIG fan of Armbian and I hope I can at least feedback information.

 

Thanks, Steve