This should include all changes up to 2.6.31-2, except patches merged upstream.
Fix up ARM patches to apply to 2.6.32.
svn path=/dists/trunk/linux-2.6/; revision=14642
as we ship that code and already modified more then bits,
just take up responsibility. copyright is deducible from commits.
let's one jump directly to the code when opening relevant file.
svn path=/dists/trunk/linux-2.6/; revision=14596
maximilian suggested to grab an axe and rip the reverse symlinks handling out.
The man page for kernel-img.conf has no reference to it anymore.
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
svn path=/dists/trunk/linux-2.6/; revision=14593
There is no /etc/kernel-img.con on a fresh debootstrap sid. Installing a
kernel leads to:
|mikejones:/var/lib# dpkg --configure -a
|Setting up linux-image-2.6.31-1-amd64 (2.6.31-1) ...
|Running depmod.
|Running update-initramfs.
|update-initramfs: Generating /boot/initrd.img-2.6.31-1-amd64
|Error retreiving answer for linux-image-2.6.31-1-amd64/postinst/create-kimage-link-2.6.31-1-amd64:
| linux-image-2.6.31-1-amd64/postinst/create-kimage-link-2.6.31-1-amd64 doesn't exist at
| /var/lib/dpkg/info/linux-image-2.6.31-1-amd64.postinst line 522, <STDIN> line 3.
|dpkg: error processing linux-image-2.6.31-1-amd64 (--configure):
| subprocess installed post-installation script returned error exit status 9
As far as I understand debconf, there must be a template and input() for
${package_name}/postinst/create-kimage-link-$version in order to get a
value saved. Since I did not find it I guess that this can't work.
If the bootloader is palo than the answer is ignored anyway so the
question is not required there.
kernel-img.conf(5) says that do_symlinks defaults to yes.
This could also fix piuparts [0].
[0] http://piuparts.debian.org/sid/fail/linux-image-2.6.31-1-amd64_2.6.31-1.log
[ nuked that template in question and this is indeed the right fix
instead of reprompting user for useless questions.
Add a comment and keep current ordering. -maks ]
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Really fix making a debian kernel installable without kernel-img.conf.
boah the code below this with reverse links must die pretty soon.
thanks for good analysis and bug report.
svn path=/dists/trunk/linux-2.6/; revision=14589
- Clarify the differences between i386 flavours (Closes: #414690)
- Simplify wording of the description template
svn path=/dists/trunk/linux-2.6/; revision=14342
nuke the preinst check if their is an initramfs,
check makes no sense as anyway around thanks to dep by linux-image
svn path=/dists/trunk/linux-2.6/; revision=14293
used for development in unstable. There are other branches
used for experimental (trunk), oldstable and stable, but Vcs-*
doesn't yet provide the ability to distinguish branches in a
more fine-grained manner. (Closes: #471495)
svn path=/dists/trunk/linux-2.6/; revision=14159
no point in keeping code that allows to circumvent this.
cleans up preinst a lot, nuke related varialbes everywhere.
as bonus nukes in preinst an comment that seems misplaced now..
svn path=/dists/trunk/linux-2.6/; revision=14030
the template is quite aged and thus we don't need to check for that.
first step in cleaning up the symlink mess.
svn path=/dists/trunk/linux-2.6/; revision=14027
as we always ship an initramfs that code path,
was never executed and thus is useless for us, nuke it.
svn path=/dists/trunk/linux-2.6/; revision=14018
initramfs is the default and user shouldn't be prompted for it.
nukes thus some useless templates.
also nuke do_initrd and warn_initrd variables all over the places.
svn path=/dists/trunk/linux-2.6/; revision=14014
"The problem is that (a) the kernel's postinst uses debconf, which uses
stdin and stdout for communication and forbids other junk from appearing
there, and (b) the kernel's postinst calls update-initramfs, which
outputs status information to stdout which debconf thinks is a command
in its protocol and thus confuses any future real debconf commands.
Since the kernel's postinst is the thing with special requirements due
to using debconf, it should be the thing responsible for redirecting
file descriptors around as necessary." -cjwatson
svn path=/dists/sid/linux-2.6/; revision=13347
fixes:
rmdir: failed to remove `/lib/modules/2.6.29-rc8-amd64': Directory not empty
dpkg - warning: while removing linux-image-2.6.29-rc8-amd64, directory
`/lib/modules/2.6.29-rc8-amd64' not empty so not removed.
ls /lib/modules/2.6.29-rc8-amd64
modules.alias.bin modules.dep.bin modules.symbols.bin
should also land in sid branch.
svn path=/dists/trunk/linux-2.6/; revision=13314
/usr/include/drm/drm_mode.h is now also in linux-libc-dev,
so it's also in libdrm-dev 2.4.5.
Fixed for 2.4.5-2 without that file.
Reported-by: Julien Cristau <jcristau@debian.org>
svn path=/dists/sid/linux-2.6/; revision=13258
don't use mkinitramfs-kpkg vestiges.
preinst and postinst needed a bit of surge to not call
the old mkinitramfs-kpkg interfaces. just check which initramfs
binary is around and call them.
they support all relevant linux-2.6 versions.
svn path=/dists/trunk/linux-2.6/; revision=12828
user proably don't even cares about the symbolic link,
nuke 2 messages as they don't provide info.
nor is there any action for the admin.
svn path=/dists/trunk/linux-2.6/; revision=12163
currently is printed:
Running depmod.
Using mkinitramfs-kpkg to build the ramdisk.
just print:
Running depmod.
Running mkinitramfs-kpkg.
(which reminds me that this wrapper should be nuked).
svn path=/dists/trunk/linux-2.6/; revision=11743
-- relevant irc discussion:
00:43 <waldi> maks: sarge->lenny upgrades are not supported
00:44 <maks> waldi i know but people like to install latest linux-26 in etch
00:44 <waldi> not our problem
00:45 <waldi> this is not supported
00:45 <waldi> and even if, only on top of etch, where it is already moved in l-k-h
---
thus revert and close away.
This reverts commit 72cd97dcf534b764c137b62ff2b7fbc6fd362d2b.
svn path=/dists/trunk/linux-2.6/; revision=11442
> Both linux-kernel-headers in etch and amd64-libs-dev in sarge
> provide /usr/include/asm/bootsetup.h (among others), leading to a hiccup
> during sarge->etch upgrade if they are not upgraded in the right order.
a bit late not but better safe than sorry,
can be kicked after Lenny release.
svn path=/dists/trunk/linux-2.6/; revision=11441
later we might want to add amixer output,
but that is very verbose so kept out for now.
fix changelog for removed atl1 drivers too.
svn path=/dists/trunk/linux-2.6/; revision=11427