packagegroup-core-tools-debug: Drop MACHINE_ARCH as PACKAGE_ARCH

There is nothing machine specific about this recipe.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake.conf: Set PACKAGE_ARCH with ??=

Currently its near impossible for other classes to sanely override
this value with their own default. By setting a weak default we can
allow other classes to change the default and allow end recipes to
again override this.

As far as I can tell, there shouldn't be any regressions from this
change.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake.conf/debian.bbclass: Move AUTO_LIBNAME_PKGS definition to class file

Might as well move this default to the class which uses it allowing
for easier reading/understanding of the class.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
packagegroup: Make allarch inherit conditional

Make the allarch inherit conditional on PACKAGE_ARCH being left as
all. The one downside to this approach is that recipes need to set
PACKAGE_ARCH *before* inheriting the class in order to avoid the inherit.

The advantage is that we could start to detect the use of the
allarch inherit in the sstatesig code for improved task checksums.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
allarch: Add warning about packagegroup

Since we want to start including this class conditionally, detect cases
where packagegroup files use the old ordering and inform the user they
need to update this.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
packagegroup: Move inherit packagegroup to after PACKAGE_ARCH

This means these classes now avoid the allarch inherit entirely.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
sstatesig: Only squash dependencies for allarch packagegroups

The idea of squashing packagegroup dependencies was to avoid allarch
packages rebuilding upon tune/arch changes. Now that the allarch class
inclusion is conditional, we can narrow down the packagegroup squashing
to be specifically applied to allarch recipes.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
debian: Set RPROVIDES to include the original packagename when renaming

Currently its hard for a packagegroup recipe to depend on something who's name
can change unpredictably. We therefore add in RPROVIDES for the original
package name so that these are also available to use as dependencies.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
package: Don't remap names in packagegroup recipes

For package groups, use the original package names and don't use the
remapped (e.g. debian) naming.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
package: Disable runtime mapping of RPROVIDES/RCONFLICTS/RREPLACES

It doesn't really make sense to run the remapping code on these
variables. If specific renaming is needed, it should be applied
manually. This means that the debian RPROVIDES of the original package
name can be preserved. There was also a bug report about this on the
OE-Core mailing list recently where someone else ran into this problem
too.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
cups: Upgrade to 1.7.5

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libbsd: Upgrade to 0.7.0

COPYING file changed in year, but no license changes

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
boost: Upgrade to 1.56.0

Rebase boostconfig to handle moved user-config file

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
glew: Upgrade to 1.11.0

Rebase patch and move patches from too generic files to glew

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libidn: Upgrade to 1.29

The COPYING and other files updated the year to 2014 so the Checksums
needed to be updated also.

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gnupg: Upgrade to 2.0.26

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
sqlite3: Upgrade to 2.8.6.0

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes/autotools: avoid error if recipe is first in task dependency tree

If the recipe being built is listed first in BB_TASKDEPDATA (i.e. item
0) this is still valid and should not trigger an error.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
e2fsprogs: Backport fixes for building with musl

Both of these fixes have been applied upstream and improve general code
correctness.  They are needed when building with TCLIBC=musl but shouldn't cause
any harm with other libc implementations.

Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wic: do not steal sectors from the first partition

In order to make up for space loss due to overhead located before the
first partition, same amount of bytes was extracted from the first
partition's size. This leads to unexpected change of first partition's
size, and is not matched by similar adjustment at the time the partition
image is generated. Thus it is possible that the first partition may
partially overwrite contents of the following partition, as the
partition image is larger than the allocated space.

This is also problematic on certain platforms such as OMAP, where the
first partition is required for have an even number of
sectors (typically already expressed by --size in kickstart
file). Subtracting an odd number of sectors lost for overhead, leads to
an odd number of sectors assigned for partition, preventing the board,
such as beaglebone, from booting correctly.

Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>