This is a late fall-out of the priority changes done by
Henning. This recipe is not using autotools and doesn't
support src != build dir builds. So let's not use the
autotools class but simply invoke install ourselves. Let's
lower the default preference so the recipe from yocto master
is picked as well.
ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890)
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'common-linux', 'common-glibc', 'allarch-linux', 'common']
| DEBUG: Executing shell function do_install
| NOTE: make -j 2 DESTDIR=/home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/image install
| make: *** No rule to make target `install'. Stop.
| ERROR: oe_runmake failed
| WARNING: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/run.do_install.16890:1 exit 1 from
| exit 1
| ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890)
NOTE: recipe ca-certificates-20120623-r0: task do_install: Failed
ERROR: Task 3639 (/home/builder/jenkins/workspace/Yocto-Master/label/OE/meta-sysmocom-bsp/recipes-extra/ca-certificates/ca-certificates_20120623.bb, do_install) failed with exit code '1'
The current 1:0.1+git1+019d2535b6-r9.2 is considered to be older
than the new gpsdate_0.1+git0+2326eee789-r10 file. Change the
PE to benefit from an upgrade.
The ODU has the GPSD for GNSS/GPS listening on a different
port. In hindsight this was a stupid decision but one we can
only fix once we move to generating the config of the system
at boot time.
Fixes: SYS#906
In case the port is not in a forwarding state.. don't just
give up but background and move on. This appears to be needed
for the odu to acquire a lease when STP is used.
networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Active: failed (Result: exit-code) since Fri 2015-02-13 17:59:17 UTC; 43s ago
Process: 54 ExecStart=/etc/init.d/networking start (code=exited, status=1/FAILURE)
Feb 13 18:04:47 sysmocom-idu networking[54]: ifup: failed to open lockfile /run
/network/.ifstate.lock: No such file or directory
The creation of /run/network occurs way too late. So we need
to look for another solution.
This reverts commit 86dda7481f.
* DHCP range for 'vlan6' onboard network 172.16.2.0/23
* DHCP range for 'native' onboard network 172.16.4.0/23
* DHCP range for 'admin' port eth1 172.16.6.0/24
* domain name vessel.sob.sysmocom.de
* listen on all interfaces, not just one
* allow admin to specify static leases (ODU) in /etc/dnsmasq.dhcp-hosts
$ ifup br0.6
would go throup _none_up of links.defn and never call the
set_environ for any of the files. Check for environ being
null and then call the set_environ function to initialize
the PATH. This is changing the semantic to allow the iface,
mode and phase to be NULL. I tried to add proper null checks
--exit-on-error is not supported by the busybox run-parts
and the easiest way is to make the ignore-errors option
the default.
I didn't test the change on the device but is looks sound.
This way we can manage bridges and vlans without additional
hacks. This package shouldn't clash with busybox so I need
to install all files with a ${BPN} suffix and then use the
update-alternatives to create the symlinks. The last two parts
were not tested/verified yet.
* the license in README has a new checksum, it now clarifies
to GPLv2
* bump the layer priority otherwise we could not use the latest version,
because the yocto layers have a higher priority
Related: SYS#732
This means that currently only Yocto Dora and Yocto Master are
being targeted. The amount of maintenance to get it to work on
Edison again is too high and it is better to focus on a systemd
only world. Remove the symlinks for yocto-edison.
A quick look and some notes from henning pointed me to wget
which is in the default layers, the sysmobts-2050 which is now
handle dby sysmobts and some older notes that are unlikely
to be addressed.
[hfreyther: We assume that the user might install OpenVPN with
a different priority but that it will always be available in the
runlevel two (e.g. even if the user changed the default runlevel)]
Related: SYS#517
I have no idea who creates the /run/openvpn directory on Debian.
The path is not in a tmpfiles.d and I don't see the generator
creating it or the service file indicating that it needs to be
created. Place the file with openvpn.NAME.status into the /run
directory which appears to work on the device.
We want to use systemd for managing the lifetime of OpenVPN. Take
the debian generator (which should work with busybox ash) and the
openvpn.service (to inhibit the sysvinit script) and the target
file and install it.
On systems that have ran "update-rc.d openvpn defaults" one need
to manually execute a systemctl enable openvpn.service. This is
not done through a post-inst script and I am not sure if we should
do it. This means there is a danger of ending with a unit that
doesn't start OpenVPN automatically after upgrade!
The scripts/packages have not been tested on a device yet.
We should use a more recent version of the OpenVPN client. Import
it from the meta-networking layer like we did before. The sysvinit
script has just minor whitespace differences and wasn't imported.
We need to test opkg upgrades of OpenVPN through the VPN. We don't
want to kill the tunnel on such upgrade.
In dora there is no autotools-brokensep bbclass. So let's just
set the build directory to the source directory ourselves. I have
not built the package for dora though/
Poky dizzy is more strict with -I/usr/include and the old
tcpdump could pick-up "/usr/bin/pcap-config" from the host
and fail. Just upgrade to a newer version of tcpdump and be
done with it.
Holger Hans Peter Freyther
Henning Heinold
Harald Welte