1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
kernel-package (10.051) unstable; urgency=low
* With this release of kernel package, changes have been made to the
specification and behaviour of hook scripts for the kernel image,
source, and header packages. Now relative paths can be used to specify
the names of scripts, as long as these scripts live in a "safe" path,
namely, /bin, /sbin, /usr/bin, /usr/sbin. Also, the sanity checking
has gotten more rigorous, failure to find a hook script or failure for
the script to execute correctly is now a fatal error.
-- Manoj Srivastava <srivasta@debian.org> Sat, 5 Aug 2006 13:26:35 -0500
kernel-package (10.025) unstable; urgency=low
* With this release, any scripts used in hooks which write to stdout
shall cause debconf to error out. In a majority of cases the error is
benign, and the package does install, but in some cases this causes
other hooks not to be run, and may result in an unbootable image. So,
please ensure that the scripts you use in the hooks do not write to
STDOUT, but use STDERR instead.
-- Manoj Srivastava <srivasta@debian.org> Sun, 25 Dec 2005 10:14:33 -0600
kernel-package (10.023) unstable; urgency=low
* Any hook scripts called from the kernel hooks should not write to
STDOUT. This is a consequence of using debconf, which commandeers
stdout. Even after db_stop is called, debconf does not restore stdout.
We used to redirect 1>&2 in the invocation of hook scripts, but we no
longer do so since some scripts may need to use debconf themselves, so
this change helps them (at the expense of other scripts that wrote to
stdout).
-- Manoj Srivastava <srivasta@debian.org> Thu, 22 Dec 2005 10:02:15 -0600
kernel-package (10.009) unstable; urgency=low
* The long obsolete --flavour option is now gone, and --append-to-version
should be used.
-- Manoj Srivastava <srivasta@debian.org> Tue, 8 Nov 2005 21:28:38 -0600
kernel-package (10.007) experimental; urgency=low
* We now take special care of the case in which the kernel-headers
are installed after the kernel-image has been; and the build
symlink is not set. In this case, the header postinst now
correctly installs the build symlink.
* Another fallout from the kernel-package generated packages being made
lintian clean is that it was noticed that the default versioning was
such that the packages appeared to be Debian native, obviously not the
case. It now generates a proper $version-$debian version, unless over
ridden.
-- Manoj Srivastava <srivasta@debian.org> Mon, 7 Nov 2005 20:11:04 -0600
kernel-package (10.004) experimental; urgency=low
* This version of kernel-package has been largely reorganized. The
crusty old mechanism has beenremoved, the targets are now
streamlined. One of the factors that made the build mechanism so
complex was that the rules file had a dual purpose: Initially, when
./debian was not present or not populated, it was responsible for
populating that, and then it was responsible for building the kernel
packages, incorporating any user customizations.
* Implement the new ramdisk generation tool finding plan. The ramdisk
variable in /etc/kernel-pkg.conf or /etc/kernel-img.conf can now be a
space separated list of init ram disk creation commands, which need to
also support the --supported-host-version and
--supported-target-version options, just like mkinitrd does. The list
in /etc/kernel-pkg.conf is used to set defaults (by setting
INITRD_CMD). However, the defaults are set to a subset of "mkinitrd
mkinitrd.yaird mkinitramfs", the subset being decided based on the
version of the kernel being built, so one should refrain from setting
this manually -- unless one knows what one is doing. The list in
/etc/kernel-img.conf is the list tried at installation time.
* The stem used for the kernel-related packages is now set to
$DEB_HOST_OS -- so we create kfreebsd-image-foo or linux-image-foo
packages, for instance.
* The kernel image maintainer scripts now use debconf; and a number of
questions have been moved to the config file while others are asked
conditionally in the postinst. The postinst has also become far less
verbose.
* The postinst gets rid of the code that generated boot floppies
and created lilo.conf (that latter was probably illegal under current
policy anyway). The do_boot_enable and do_boot_floppy configuration
variables in /etc/kernel-img.conf are now invalid.
* Also, the source tree is not automatically cleaned; the do_clean
configuration variable, and the environment variable CLEAN_SOURCE, now
control if the source tree is optionally cleaned after the kernel
image package is built.
-- Manoj Srivastava <srivasta@debian.org> Thu, 3 Nov 2005 23:38:14 -0600
|
