libbabeltrace-ctf-dev was merged into libbabeltrace-dev, so the
build dependencies are unsatisfiable in unstable. For stretch-
backports we will still want both of them. So add a suitably
versioned dependency on libbabeltrace-dev as a preferred
alternative to libbabeltrace-ctf-dev.
It has a lintian error (non-empty-dependency_libs-in-la-file) and it
also seems to be missing a header (the newly added
usbip_host_common.h) since Linux 4.7. No-one seems to have noticed,
and it has nothing build-depending on it, so get rid of it.
The dpkg bugs affecting libssl-dev build deps were fixed in 1.18.8.
The various non-M-A packages for which we used :native qualification
were fixed before stretch release. So neither unstable nor
stretch-backports needs these.
This reverts commit 85b468262e "Remove unused liblockdep packaging"
and 87d08943da "liblockdep: Stop trying to build packages, as it
failed to build again", but doesn't restore the patches. All our
patches, and further build fixes, were applied upstream as of
v4.13-rc1.
It has finally been removed after all docs were converted to ReST format.
As there is no longer a way to build manpages, remove the linux-manual
package.
linux-headers-*-common* packages are arch-independent since version
4.9~rc7-1~exp1, so to allow for binNMUs we need to specify
${source:Version} in versioned dependencies on them.
Closes: #869511
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlkI0/kACgkQ57/I7JWG
EQkutQ/9EsYdnQXf4HaC1YTqQW0Nu5+swZzyosOcdtMfJrj+PWXQMgmY4WWav8I/
DipRGhfXXMnqlBg1vOR5cEdqPznRm/cwcuPqZpw7H0fA7LvyCibg/7yERJYv7i1U
BIy8s29NCpVVRhDhY9Nl5t0WLGQT4Rg9JW6iKNRDq2y91etahSxzOBxB2B3k04Ys
9vFPpuKq5QAskCBGEucinYYKTy7/ciIXsaSij2m/G7/ly/Qaqt0pIgjqi4QhuJs3
yWidIm1aBvE4MHXH8WQkg1aF20vfdGXz3CZNT6BWFn/6hNesS+tEQpF/nYLBqnfS
2GghqeWO1+xzxlXWNZU/SD0JhkB6gAeZ+4MP7eYz8BAtpUz7H/zZfZNsOBWb6YJY
Pc8AjqG6mBd/1B2O8yXUda/j/xazEtg0c7uxQjyOEqh2nPeHn9FVLuJsSP74wxdx
zjGmOjJzKUmhBGxLdJZAFL5N7YbLR+qNQfV2UGz4+zVIJge9R7HwWwR9+Um8AHq0
qrnjRf6iAla1phYlgHnPx4r6A9kactDuFsNMfUN8nsUrV+KX15k+dt02CpFSWw0B
lXGPf2MNXTEp+CsuAVBAWFP55JCOwD6yYoLfEfErXvchc7qqIKHgmIrLSyexro7O
F1+HBfu6t1M4tRz0xNu8sGL4uzsjockMW8RL1HFgboUluMgTFPQ=
=k/sj
-----END PGP SIGNATURE-----
Merge tag 'debian/4.9.25-1'
Drop the added patches, which are already in 4.11.
CONFIG_NFP_NETVF is replaced by CONFIG_NFP in 4.11.
dak currently allows a binary upload to include debug symbol packages
that don't appear in the overrides file or the Binary field of the
changes file, so long as they have the appropriate
'Auto-Built-Package' field and their name matches another binary
package in the upload plus the '-dbgsym' suffix.
For architectures with code signing enabled, our binary uploads never
match this condition as the corresponding binary package has the
'-unsigned' suffix and the debug symbols package does not. Since we
do list the debug symbol packages in the Binary field, they do get
added to the overrides file when accepted through the NEW queue, but
they are automatically pruned from there some time later. Later
uploads then have to go through NEW even though they are not
introducing new binary packages. This would be a big problem for
stable security updates.
For now, move debug symbols back to the main archive with the old
'-dbg' suffix. Keep them enabled for all architectures.
Listing usr/sbin in linux-cpupower.install caused FTBFS on !x86 as
cpupower itself doesn't install anything there. Do the architecture
filtering in the debhelper lists instead of complicating
debian/rules.real further.
This reverts commit 99d37f9b16, which
caused most binary uploads to be rejected. dak's allows upload of
debug symbol packages not listed in the Binary field only if there is
a corresponding binary package without the -dbgsym suffix, which is
not the case on architectures where we use a -unsigned suffix.
Any packages listed in debian/control that are not installed in the
main archive will always be seen as NEW. This might be fixable by
archive configuration changes, but for now we'll generate them in a
similar way to debhelper.
Include headers for all architectures that we build a kernel for.
This allows co-installation of per-flavour header packages for
multiple Debian architectures, and fixes the problem of arm64 headers
depending on arm headers that we did not include.
The new versions have Multi-Arch: allowed, and surprisingly dpkg doesn't
consider them to satisfy a dependency on openssl:native. Change the
build-dependency into an alternative satisfiable by both old and new
versions. (Closes: #839145)
(cherry picked from commit 8e552ff10c)
The new versions have Multi-Arch: allowed, and surprisingly dpkg doesn't
consider them to satisfy a dependency on openssl:native. Change the
build-dependency into an alternative satisfiable by both old and new
versions. (Closes: #839145)
If kernel.dmesg_restrict is enabled (which it now will be by default)
and sudo is installed, ask whether to use sudo. If this is denied or
fails then fall back to writing a placeholder in the bug report.
-----BEGIN PGP SIGNATURE-----
iQIcBAABCgAGBQJX4HvgAAoJEOe/yOyVhhEJq9cP/j1XO1dNpOXxq0JZod66K1sl
JIC4LPZ3i+kiAD0amMZiAexAuCpqCDjinjVr/pAhEoAa79983tFoY9yWjDCAW+9H
0j7Torb5wQ76BlyXCjSoaztcQmzQ1YiCvjIzk4hCJCcvqdTuA1MMr7+AbXAgi3xE
Es/G7ai+7SK5suEYgsbliM2ndFFMtIDqgpvDVDFNBDt61m2RXKxw7SQwyItIx+Hn
n7Aq/P+LP7BjMSP6nW6EafF/RidbAwq4x+FKqzGyZhVQV7c3YFbh0EA7lVcTDhC7
A1ZbdeUjiFhUKchRPa56qf+eAI8sBEeU3Ga1mhpkxL8RkFKwvWmmB2J0tBE7KHgw
WCy+8nPxnLAq3eVIkOcB3MuvNdM9DvvtQ7X5NjXnBIfq06OX4y+C+udMpafmegTG
5YB3FVppFQNGZcOxeF9hCQspHGvBsTGRYoK3hxzx4AY94E1cakl08oZte4dHYALz
GvP/tjbLH5i/g9djVNGtfZCHKMZbDq2QhD60GNwFoN/ssX4Q/L3q4N+eyJD9KoQM
Bu44v1ZY7M13F4t5JUomjU2e5mze3opxEB2C7vIoyJfaUvtAWX/mn8SysDGdT0OJ
zd8ow6IntzcL+mqxrarOPMenSt2yqoQ6WdkYkpF5aCTj2GJyAkU7dUWfWdKWtLM7
yjuIvqRAcVzMU9XuU8uf
=s0s4
-----END PGP SIGNATURE-----
Merge tag 'debian/4.7.4-2'
- Drop ABI references and ABI maintenance patches
- Fix Kconfig symbols for omapdss sub-drivers, which were renamed for 4.8
I don't know what the suffix is going to be next time we need to add
it, but it will sort lower than the '+deb' suffix added for stable
security updates.
- Add python-sphinx and python-sphinx-rtd-theme to Build-Depends-Indep
- Install files from both HTML output directories into the package
- Exclude RST sources from the package
Currently the linux-source-<version> package may or may not include
these files, depending on the order things are built in.
As autotools always modifies the source directory, copy (rsync) the
source to the build directory and build in-place there.
Currently we build-depend on the native python (via asciidoc), and on
the host python (via python-dev). As these are not coinstallable it
is impossible to perform a complete cross-build. Until that's resolved,
this will allow cross-building of most of the package with the
combination of the 'cross' and 'nopython' profiles.
(This also sidesteps the issue of perf wanting a multilib compiler.)
The current cross-compiler packages don't set the Multi-Arch field, so
specify that the cross-compiler package must be native, rather than any
architecture.
flex doesn't support multi-arch, and this would require splitting it
(#611230, #761449). Force use of the native package for now.
openssl doesn't support multi-arch but probably easily could (#827028).
Force use of the native package for now.
We need the native libssl-dev while building the kernel itself and the
host libssl-dev while building tools for linux-kbuild.
Document the state of cross-building in README.source.
linux-kernel-headers was removed from unstable in 2007, so presumably
was last released in etch.
libkxl0-dev still depends on it, so don't remove the Provides yet.
Currently the postinst script distinguishes installation vs upgrade by
checking whether its second argument is empty. However, it will only
be empty if the package was *never* installed before, or was purged.
If the package has been installed, then removed, and is now being
installed again, it's seen as an upgrade.
Unfortunately dpkg only tells the preinst script whether or not this
is an upgrade. So create a flag file there, consume it in postinst
and remove it in postrm.
Use the new linux-update-symlinks command for symlink updates.
Drop support for minimal_swap, no_symlinks, use_hard_links and *_hook
parameters in /etc/kernel-img.conf.
Thanks to Aurelien Jarno and Santiago Vila for pointing out the
ischroot command and that it's in an essential package (i.e. doesn't
add a dependency).
This seems to have been a transitional feature for the switch
from kernel-image to linux-image. mkvmlinuz still uses it but
no hook scripts appear to depend on it.
The list is getting hard to read as we add build profiles. It's also easier
to merge and cherry-pick changes when each dependency is on a separate line.
* Drop redundant gitignore.patch from linux-tools
* Rename linux-tools' debian/templates/control.main.in to
debian/templates/control.tools.in
* Combine changelogs, putting all entries for each upstream release
cycle in chronological order
* Combine rules and gencontrol.py code
Also add a helper executable that implements the check for Hyper-V
(like ConditionVirtualization=microsoft in the systemd units).
(cherry picked from commit 50747480c882dae7d3c8f7b4d0df5cf3276c4ee5)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIVAwUAVsT0Jue/yOyVhhEJAQo96w/+IZBasj9Vf3KovHNaOXaW1rZL6GRVNzpB
OSNqINfAEtvOR8RuwAcA/zgHy7NNDS9CkDQgjGdJKIhdXXem7mG7Oo3iEwb5osL7
HhUPmeTmXqsa5C6GWzNtERrtX6N8XtBV3inR8iSS46XOm+RHq5UnffqZB35DqUbq
G0h5hiZSXXIXbn0MYJWSPAekAmTXdcevGUoe8bIBD+wH/X4oPINmQLkH6PL5iK7B
KHbf7dJ+JnmbsKJdBpfZvPoa6B1a9FL3HLKkOQjmYF0YjIzZe14JHnvjZNULBmj9
eqmwpfPxAmR5XQgUBu1TPx37FB/nJdMUjZQNz01k0Ybv3l6lKocc7YwX3kViitqe
CiWqbq7LPwN1QNGI6Sf7UB/1XjWJPzWsYoZ0AjDH3ihIPrxmYCdjJstFXr0W3qEG
4e3pJv8gqHxP5SSmE5PQQcS8uiisHmADHZc7C02mxWGDLpqb3gmtgrGqQRFjkk55
tpn8jz2fGGt5VQkhpSBE8wWG4fHRFwiLaAsCVv9jE36pLNq5M9U9VnilCPeoTkti
JcDfPYBjma6RVADIU6tkNnjxJcHFXAqEb5Jn0Wq89GGaS1egAlch4K/XYS+OnIH9
m2Fg4P+TdMePDYxh40tNTIwwHcHLffNfe9K+Ien/DmffuQ87Jk4hfKPW/ZXDO3jO
qdrmLXK2BEg=
=syys
-----END PGP SIGNATURE-----
Merge tag 'debian/4.4.2-1'
Drop rt featureset changes.
Drop patches that are already in 4.5-rc4.
Keep the ABI version at 'trunk'.
Karsten did a test-build on armhf and found failures due to missing modules
and directories.
* The wireless drivers from staging need to be optional; this requires
support for wildcards in optional-inclusion lines
* The check for a containing directory must only be done for non-optional
inclusion lines
Bump the kernel-wedge version requirement and add the optional-include
suffixes.
It would be nice to include the Device Tree model in the reportbug
output. On DT based platforms, /proc/cpuinfo only includes quite
generic information.
Please note that the strange "echo ... $(cat ..)" construct is
intentional. 'cat /proc/device-tree/model' leads to a strange
character at the end because there's no newline and using echo
gets rid of it.
Ben Hutchings
Salvatore Bonaccorso
Uwe Kleine-König
Bastian Blank
Mattia Dongili
Martin Michlmayr