Sorry for such a late reply. I'll fix the commit log. The reason for the
order change is that I get:
rm: can't remove '/etc/resolv.conf': Read-only file system
ln: /etc/resolv.conf: File exists
every time on boot up. When switched, no error messages. It does still
'work', I just thought I'd clear
On Fri, Feb 6, 2015 at 8:56 PM, Nathan Lynch wrote:
> The testcases for lttng-tools use the "prove" command from perl-misc,
> which needs many modules not in the base perl package.
>
> Signed-off-by: Nathan Lynch
Wouldn't be better to specify the modules needed for the prove
command? This avoids
On 07/02/15 22:55, Paul Barker wrote:
> I didn't realise people were following oe-core master on deployments of a few
> thousand systems! This is definitely a use-case for the stable branches.
The deployed systems are currently on:
opkg mips32el 1:0.2.2-r0
opkg-collateral mips32el 1.0-r2
opkg-con
On Sat, Feb 07, 2015 at 09:47:32PM +1100, Peter Urbanec wrote:
> On 17/01/15 09:15, Paul Barker wrote:
> > All these changes work locally in qemuarm and the on-target upgrade
> > path is
> > mostly clean. opkg-collateral does get left behind on the target
> > filesystem
> > after a
On 17/01/15 09:15, Paul Barker wrote:
> All these changes work locally in qemuarm and the on-target upgrade path
> is
> mostly clean. opkg-collateral does get left behind on the target
> filesystem
> after an upgrade but it's effectively an empty package. I don't think
> this
>
