On 8/10/23 20:20, gene heskett wrote:
ping
On 8/10/23 13:33, gene heskett wrote:
On 8/10/23 12:09, Sebastian Kuzminsky wrote:
On 8/10/23 09:38, Marius wrote:
Just so I understand please. Did the RPi 4 code crash or are you using a RPi 4 to do some of the compilation?

The Pi is one of the workers in the buildbot, it checks out the linuxcnc source code, builds and tests it, and builds & uploads its Raspberry Pi OS Buster/armhf debs to our debian package archive.

The Pi crashes maybe once per month - the whole computer locks up so it has to be powercycled.


I just discovered that apt seems to be the problem here, Seb.
Its reporting the packages can be upgraded, but then doesn't do it..

My command line to update the pi:
sudo apt autoremove -y && sudo apt update && sudo apt list --upgradable && sudo apt upgrade -y

The output is:
pi@rpi4:~ $ sudo apt autoremove -y && sudo apt update && sudo apt list --upgradable && sudo apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Hit:1 http://buildbot.linuxcnc.org buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Listing... Done
linuxcnc-uspace-dbgsym/stable 1:2.10.0~pre0.1787.g93a0bc31f armhf [upgradable from: 1:2.10.0~pre0.1309.g10ef777f1] linuxcnc-uspace-dev/stable 1:2.10.0~pre0.1787.g93a0bc31f armhf [upgradable from: 1:2.10.0~pre0.1309.g10ef777f1] linuxcnc-uspace/stable 1:2.10.0~pre0.1787.g93a0bc31f armhf [upgradable from: 1:2.10.0~pre0.1309.g10ef777f1]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

What might be stopping apt?

sudo -E synaptic reports that the buildbot does not have a release file, so has disabled that repo.
That puts me back to building it myself, but:
#>:time ./buster-make-debs.sh
make[1]: Entering directory '/media/pi/workspace/buster-linuxcnc'
# The G-code quick reference html docs are built as
# `docs/html/en_US.UTF-8/gcode.html`.  We install them
# into `/usr/share/doc/linuxcnc-uspace/` in each
# linuxcnc-doc-en_US.UTF-8 package, then rename them there (except
# for the English one) to include the language in the filename,
# so they don't collide when we install all the doc debs.
#
# Rename the "main" doc directories from
# `usr/share/doc/linuxcnc-uspace` to `usr/share/doc/linuxcnc`,
# because that's where the `.desktop` files look for the docs.
dh_installdocs --doc-main-package=linuxcnc-uspace --package=linuxcnc-doc-de
         install -d debian/linuxcnc-doc-de/usr/share/doc/linuxcnc-doc-de
dh_installdocs: error: Cannot find (any matches for) "usr/share/doc/linuxcnc/LinuxCNC_Developer_de.pdf" (tried in ., debian/tmp)

make[1]: *** [debian/rules:108: override_dh_installdocs-indep] Error 255
make[1]: Leaving directory '/media/pi/workspace/buster-linuxcnc'
make: *** [debian/rules:38: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
mv: cannot stat '*.deb': No such file or directory

real    69m30.822s
user    60m38.884s
sys     11m2.849s
pi@rpi4:/media/pi/workspace $

So, can I pass an argument to make etc, so It only builds English pdf's?
The build script:
pi@rpi4:/media/pi/workspace $ cat buster-make-debs.sh
!#/bin/bash
# converted to relative cd-ing
cd buster-linuxcnc/debian
./configure uspace
cd ..
echo 5 `pwd`
dpkg-checkbuilddeps
echo 7 `pwd`
dpkg-buildpackage -b -uc
cd ..
mv *.deb buster-lcnc-debs/

Thanks.

Cheers, Gene Heskett.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to