debian/lib/python/debian_linux/debian.py,
debian/lib/python/debian_linux/patches.py,
- Support Python 3.
- Use six if necessary.
* debian/templates/control.main.in, debian/templates/control.source.in:
Depend on python-six.
svn path=/dists/trunk/linux/; revision=20946
At this point, Debian users should know that they may need to install
firmware from non-free. People using e.g. the r8169 driver may quite
reasonably choose not to install the associated firmware, either
because the driver doesn't actually request it for their chip or
because the driver can still work without it.
One thing we lose by doing this is a reminder that a firmware package
might also need to be upgraded, as a driver requires a newer version
of the firmware that has a different name. As an alternative, we
could compare the firmware file lists for old and new modules and only
warn about newly listed files that are missing. However, that would
also result in incorrect warnings for e.g. r8169 users, as that driver
may request a different file for each of the many chips it supports.
svn path=/dists/trunk/linux/; revision=20511
We warned about removal of the 'ramdisk' configuration variable
on upgrade to wheezy, and don't need to warn about it again - at
least not this prominently.
svn path=/dists/trunk/linux/; revision=20510
Refresh with: debconf-updatepo --podir=debian/templates/po
This resulted in some fuzzy matches between "Boot loader configuration
must be updated" and "Ramdisk configuration must be updated". These
obviously should not use the same translation so I removed the fuzzy
translations.
svn path=/dists/trunk/linux/; revision=20509
Use the same template syntax and implementation for maintainer
scripts, translations, etc. as we do for the control files. Define
the image-stem and initramfs variables to replace the old K and I
variables.
After this, debian/linux-* and debian/po/*.po are generated files (at
source preparation time) and should be ignored in svn.
Use debhelper to install the generated files at build time. This also
results in a redundant dependency on debconf (which we already have in
Pre-Depends), but this seems harmless.
svn path=/dists/trunk/linux/; revision=20508
Maintainer scripts generated by kernel-package pass an environment
variable $KERNEL_ARCH to hook scripts. This is undocumented but seems
to be the architecture string that the kernel will report
(e.g. through 'uname -m').
However, for the past few years our maintainer scripts have set it to
the source architecture name instead. Since no-one reported this bug,
I don't think anyone depends on it. codesearch didn't find any users
either. So remove it.
svn path=/dists/trunk/linux/; revision=20507
Drop most patches as they're already upstream in 3.8 or early.
Refresh some others for 3.8. In particular, remove use of __devinit from
debian/radeon-firmware-is-required-for-drm-and-kms-on-r600-onward.patch
as this macro is no longer defined or needed.
svn path=/dists/trunk/linux/; revision=19856
Exclude RT changes and ABI fudges.
Refresh firmware-remove-redundant-log-messages-from-drivers.patch
against 3.6, but don't attempt to cover anything new yet.
svn path=/dists/trunk/linux/; revision=19603
This allows us to list modules as required even if they are built-in
in some configurations. (Which I already did by mistake with 'hid' in
3.2.19-1.)
svn path=/dists/sid/linux/; revision=19088
Change patch.apply.in to apply a single patch series without
filtering. Move series/base to series-all and series/base-extra to
series-rt and series-none (the latter empty).
Remove the redundant status file support from patch.apply.in, and
convert it into a static file rather than a template.
Remove the redundant patch series list support from patches.py.
svn path=/dists/sid/linux/; revision=19071
We have not used per-architecture patches for many years. This is a
step toward using a more standard patch system.
svn path=/dists/sid/linux/; revision=19070
Ben Hutchings
Bastian Blank