Your message dated Fri, 02 Dec 2005 15:18:19 -0600
with message-id <[EMAIL PROTECTED]>
and subject line These bugs are now fixed in the version in unstable
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Nov 2005 06:59:34 +0000
>From [EMAIL PROTECTED] Mon Oct 31 22:59:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from sorrow.cyrius.com [65.19.161.204]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EWq7K-0007PO-00; Mon, 31 Oct 2005 22:59:34 -0800
Received: by sorrow.cyrius.com (Postfix, from userid 10)
id 854E964D54; Tue, 1 Nov 2005 06:59:34 +0000 (UTC)
Received: by deprecation.cyrius.com (Postfix, from userid 1000)
id 0D4408118; Tue, 1 Nov 2005 06:59:25 +0000 (GMT)
Date: Tue, 1 Nov 2005 06:59:25 +0000
From: Martin Michlmayr <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: kernel-package tells me we're being reinstalled AND updated
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: kernel-package
Version: 9.008.4
Severity: minor
I had no kernel package installed at all, and when I installed one, I
was told that we're being reinstalled AND updated. Obviously, neither
is true.
| Not touching initrd symlinks since we are being reinstalled (2.6.12-10)
| Not updating image symbolic links since we are being updated (2.6.12-10)
(Yes, I was running the kernel that I was installing; basically, I
purged and then reinstalled the package.)
Full transcript:
[ purge kernel stuff ]
619:[EMAIL PROTECTED]: ~] ls -la /boot
total 19
drwxr-xr-x 5 root root 1024 2005-11-01 06:52 .
drwxr-xr-x 24 root root 4096 2005-11-01 05:58 ..
lrwxrwxrwx 1 root root 15 2005-05-25 19:35 debian.bmp -> /boot/sarge.bmp
drwxr-xr-x 2 root root 1024 2005-11-01 06:52 grub
drwx------ 2 root root 1024 2005-05-25 20:20 keys
drwx------ 2 root root 12288 2005-05-25 17:23 lost+found
620:[EMAIL PROTECTED]: ~] sudo apt-get install linux-image-2.6.12-1-686
Reading package lists... Done
Building dependency tree... Done
Suggested packages:
linux-doc-2.6.12 lilo
The following NEW packages will be installed:
linux-image-2.6.12-1-686
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/16.7MB of archives.
After unpacking 48.6MB of additional disk space will be used.
Selecting previously deselected package linux-image-2.6.12-1-686.
(Reading database ... 104500 files and directories currently installed.)
Unpacking linux-image-2.6.12-1-686 (from
.../linux-image-2.6.12-1-686_2.6.12-10_i386.deb) ...
You are attempting to install a kernel image (version 2.6.12-1-686)
However, the directory /lib/modules/2.6.12-1-686 still exists. If this
directory belongs to a previous linux-image-2.6.12-1-686 package, and if
you have deselected some modules, or installed standalone modules
packages, this could be bad. However, if this directory exists because
you are also installing some stand alone modules right now, and they
got unpacked before I did, then this is pretty benign. Unfortunately,
I can not tell the difference.
If /lib/modules/2.6.12-1-686 belongs to a old install of
linux-image-2.6.12-1-686, then this is your last chance to abort the
installation of this kernel image (nothing has been changed yet).
If this directory is because of stand alone modules being installed
right now, or if it does belong to an older linux-image-2.6.12-1-686
package but you know what you are doing, and if you feel that this
image should be installed despite this anomaly, Please answer n to the
question.
Otherwise, I suggest you move /lib/modules/2.6.12-1-686 out of the way,
perhaps to /lib/modules/2.6.12-1-686.old or something, and then try
re-installing this image.
Do you want to stop now? [Y/n]n
Setting up linux-image-2.6.12-1-686 (2.6.12-10) ...
You are attempting to install a kernel version that is the same as
the version you are currently running (version 2.6.12-1-686). The modules
list is quite likely to have been changed, and the modules dependency
file /lib/modules/2.6.12-1-686/modules.dep needs to be re-built. It can
not be built correctly right now, since the module list for the
running kernel are likely to be different from the kernel installed.
I am creating a new modules.dep file, but that may not be
correct. It shall be regenerated correctly at next reboot.
I repeat: you have to reboot in order for the modules file to be
created correctly. Until you reboot, it may be impossible to load
some modules. Reboot as soon as this install is finished (Do not
reboot right now, since you may not be able to boot back up until
installation is over, but boot immediately after). I can not stress
that too much. You need to reboot soon.
Please Hit return to continue.
Not touching initrd symlinks since we are being reinstalled (2.6.12-10)
Not updating image symbolic links since we are being updated (2.6.12-10)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /vmlinuz-2.6.12-1-686
Updating /boot/grub/menu.lst ... done
--
Martin Michlmayr
http://www.cyrius.com/
---------------------------------------
Received: (at 336733-done) by bugs.debian.org; 2 Dec 2005 21:21:55 +0000
>From [EMAIL PROTECTED] Fri Dec 02 13:21:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from host-12-107-230-171.dtccom.net ([12.107.230.171]
helo=glaurung.internal.golden-gryphon.com)
by spohr.debian.org with esmtp (Exim 4.50)
id 1EiILp-0000oK-1x; Fri, 02 Dec 2005 13:21:54 -0800
Received: from glaurung.internal.golden-gryphon.com ([EMAIL PROTECTED]
[127.0.0.1])
by glaurung.internal.golden-gryphon.com (8.13.5/8.13.5/Debian-3) with
ESMTP id jB2LIJTC000390
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 2 Dec 2005 15:18:20 -0600
Received: (from [EMAIL PROTECTED])
by glaurung.internal.golden-gryphon.com (8.13.5/8.13.5/Submit) id
jB2LIJ6S000389;
Fri, 2 Dec 2005 15:18:19 -0600
X-Authentication-Warning: glaurung.internal.golden-gryphon.com: srivasta set
sender to [EMAIL PROTECTED] using -f
From: Manoj Srivastava <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: These bugs are now fixed in the version in unstable
Organization: Manoj Srivastava's Home
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)
(i686-pc-linux-gnu)
Face: iVBORw0KGgoAAAANSUhEUgAAACYAAAAwCAMAAABKbPgaAAAAM1BMVEUAAADIjH/0rp1KPz79
0b+ic2nlpJc2Ly2AY17VlYb4uqi2gHQXFBN2WVXgno5iT02Xa2Nx+jaIAAACVElEQVQ4je
WU23bjIAxFLUAggQX6/6+dI9LGTpo+9mlYiXNhc3TnOP50naZE0tqvgEk+soutnNfQ8yPT
WMTENhNrjI+Y+N7POVt8tAzpn2vJlsmttbyfrdkP7hx5iezteGzsbOts7xT+tC1mcG+LtR
P2X/16bEQExuyx1uZWvscrAWUT8aE0aDBeBuw8nS5u4WgWyDCllOZUBeyWgbWbGrBsTDpT
x0qpphlcYPcgJLvBXFClPMg56WH2JidLIAaDF5aAed7uPTH4bjw0bZvfajp2tHc1F+cBm+
Vr9YomGSwNhbmcczYEWUu5MBpYvCLVF+ZIKwQfYB+CBXnIRQFvIRhK6l96PemsFLEPFxi+
MPxiTYH0Ave1InPsIYes3NJb42ytBSmmysyjlIQYHJm6Im1WbQ0kWMesKFRFPKTDzJ3GhW
Un2KWKEkWlKthoACLm2eWJQQh2qKbAUgQxa+8TVjn1aySm8656ookCfCc5TRzvnZ6YOu3N
pHg+uR5YuRkNF/b5IHq5Y7Ve6c2+sR4hqIZ3+5DCt3ukh8EovFIXVJxqfMdbkd/BF3YaQk
B/2RIUHPMS7RLVAHefrYzWZVQ/ei4peBsROFLi90ltQyvF5I05t4ZsL4C9DODJ2AZCUf8U
itGjCIdfx15QQkfZibTOGT3edxns5fY6F2rstKcTwiiaJnQwvYkdzTlaTqNHIkSmGdLrON
45tGsMNDoSYr4bxH5emHEFaoFjKBahHXFXfLx9cR9p6ejJXihuxPz57gWHZkWovbPl9gsU
8eImtBi++3D+f+sfT/Mg79fyEz8AAAAASUVORK5CYII=
X-URL: http://www.golden-gryphon.com/
Mail-Copies-To: nobody
X-Face: [EMAIL PROTECTED]/;Y^gTjR\T^"B'fbeuVGiyKrvbfKJl!^e|e:iu(kJ6c|QYB57LP*|t
&YlP~HF/=h:[EMAIL PROTECTED]:6Cj0kd#4]>*D,|0djf'CVlXkI,>aV4\}?d_KEqsN{Nnt7
78"OsbQ["56/!nisvyB/uA5Q.{)gm6?q.j71ww.>b9b]-sG8zNt%KkIa>xWg&1VcjZk[hBQ>]j~`Wq
Xl,y1a!(>6`UM{~'X[Y_,Bv+}=L\SS*mA8=s;!=O`ja|@PEzb&i0}Qp,`Z\:6:OmRi*
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::F60QUYLB+zmlJGc3:0000000000000000000000000000000000vh94
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::In7KFagmIZrg1zpL:00000000000000000000000000000000012QBY
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::4hYmma9FCRucJAIw:0000000000000000000000000000000002lVa7
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::uhXBmimPRUv25Icx:0000000000000000000000000000000006pXLa
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::zXEqydJq+/o6OtNv:0000000000000000000000000000000003EIBd
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::AOnf0CNyXC9/82As:0000000000000000000000000000000000RbIY
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::Ez8yubQ4OWcKW3QB:0000000000000000000000000000000000GWca
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::Jd+QeWzkc74EILIY:0000000000000000000000000000000000GfSy
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::oUyvvB86yCnEmEMk:0000000000000000000000000000000002WpKg
X-Hashcash: 1:25:051202:[EMAIL
PROTECTED]::UwrSuP8xqfvstiQe:0000000000000000000000000000000002tnrD
Date: Fri, 02 Dec 2005 15:18:19 -0600
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-CRM114-Score: -57.5082
X-CRM114-Status: Good ( pR: -57.5082 )
X-SA-Orig: -8.399, -57.5082
X-Spam-Value: -16.0383444444444
X-Grey: White
X-SA-Rep: -16.0383444444444 ALL_TRUSTED,BAYES_00,HASHCASH_25
X-Scanned-By: MIMEDefang version 2.53 (www . roaringpenguin . com / mimedefang)
on 192.168.1.10
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-4.5 required=4.0 tests=HAS_PACKAGE,SUSPICIOUS_RECIPS
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 3
Package: kernel-package
Version: 10.011
kernel-package (10.011) unstable; urgency=low
* Bug fix: "DEBIAN/ directory doesn't appear to exist at
image_clean_hook time", thanks to Don Armstrong. Moved the hooks for
image and headers later in the process. (Closes: #339659).
* Bug fix: "kernel-package: kernel-image-deb mentioned in README.gz but
removed in 10.x", thanks to Marc Haber. Well. The new name is
stamp-kernel-image. Changed docs, and added kernel-image-deb
temporarily as an alias. (Closes: #340978).
-- Manoj Srivastava <[EMAIL PROTECTED]> Thu, 1 Dec 2005 15:30:27 -0600
kernel-package (10.010) experimental; urgency=low
* Bug fix: "kernel-package: Fails to build ppc64 2.6.14 kernel", thanks
to Juergen Kreileder. Sven Luther provided the patch (Closes: #338449).
-- Manoj Srivastava <[EMAIL PROTECTED]> Thu, 10 Nov 2005 21:47:09 -0600
kernel-package (10.009) experimental; urgency=low
* The long obsolete --flavour option is now gone, and --apend-to-version
should be used. Also, --append-to-version may soon be superceded with
--abi, stay tuned.
* Speed up the stripping code in kernel header packages, by only looking
at the scripts directory (which was the only place with the elf
binaries).
-- Manoj Srivastava <[EMAIL PROTECTED]> Wed, 9 Nov 2005 22:55:55 -0600
kernel-package (10.008) experimental; urgency=low
* Well, it turns out that only on some architectures do we havea binary
using a dynamically loaded shared library, so the call to dpkg-shlibs
was failing on the others. Now, go throug a complex dance in which we
either call dpkg-shlibs, or edit the control file using Perl, so that
both cases can be catered to.
-- Manoj Srivastava <[EMAIL PROTECTED]> Tue, 8 Nov 2005 08:51:08 -0600
kernel-package (10.007) experimental; urgency=low
* Aaargh, typo in the kernel header rules.
* The generated packages should not have native version numbers by
default, since they are not really debain native packages. The problem
was that the default version generated did not have a -, so chnaged
that value. The files affected are kernel-pkg.conf, README,
kernel/ruleset/misc/version_vars.mk , kernel-pkg.conf.5,
kernel/docs/README, kernel/ruleset/misc/config.mk.
* While looking at Lintian errors, I noticed that apparently
kernel-headers package carries with it an elf binary, and thus should
depend on the shared libraries -- but did not. Fixed now by a search
and a call to dpkg-shlibs. Various minor nitpicks in the default
Control file also fixed.
* We also added a make snippet to find and strip the binaries we need to
run dpkg-shlibs upon, since that is the policy.
* kernel/ruleset/targets/image.mk: Export the variable IMAGE_TOP before
calling scripts in $(SRCTOP)/debian/image.d and debian/post-install,
since that is what they expected. Bad idea changing an exposed
interface.
* kernel/pkg/image/postrm: Call purge to remove the questions from
debconf database when the package is purged.
-- Manoj Srivastava <[EMAIL PROTECTED]> Tue, 8 Nov 2005 01:03:49 -0600
kernel-package (10.006) experimental; urgency=low
* Hmm. We need to 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 setr. In this case, the header postinst now
correctly installs the build symlink.
-- Manoj Srivastava <[EMAIL PROTECTED]> Mon, 7 Nov 2005 12:44:21 -0600
kernel-package (10.005) experimental; urgency=low
* Bug fix: "kernel/image.postinst should mention GRUB", thanks to
Martin Michlmayr. Well, I don't see why we should mention _any_ boot
loader at all, so we are no longer biased against grub. (Closes: #336927)
* Bug fix: "kernel-package: Using dpkg --remove followed by dpkg
--install does not restore the kernel package", thanks to Daniel
Jacobowitz. Also: "kernel-package tells me we're being reinstalled AND
updated". Actually, the installed/updated is just sematics; when you
reinstall a kernel image you are updating it, and vice versa. The
actual problem was that while the symbolic links were removed when the
package was removed, dpkg passed the last-version-configured to the
postinst, and we took that as evidence that the package had been
installed before -- which, while true, did not take into account that
the package was currently uninstalled. The fix is to always see if a
missing symlink needs to be installed, and not touch existing
symlinks. (Closes: #336733, #336517).
* Added kernel/pkg/headers/create_link as an example. The user can install
it in the postinst.d directory to set up the /lib/modules/foo/build
symlink to point to the kernel-headers. This is not needed, since the
kernel-image postinst already checks in the /usr/src/ directory for an
installed kernel headers package.
* Convert the image prerm scripts to debconf as well, the questions are
asked if we try to remove the running kernel image, or if we are
removing a kernel version mentioned in boot loader configuration.
* Have the minimal.mk not overwrite the control or the changelog file.
* Added a whole slew of config files, and updated older ones, to bring
the configurations offered up by default to be more in line with
official kernels.
* Fixed substitutions in the kernel image package, there was a duplicate
=B substitution.
* Ran lintian on all the generated packages. Fixed FSF address in all
the copyright notices, and fixed case in the templates file as
well. This shall be the last experimental release, barring major
problems.
-- Manoj Srivastava <[EMAIL PROTECTED]> Mon, 7 Nov 2005 10:44:39 -0600
kernel-package (10.004) experimental; urgency=low
* Bug fix: "using debconf", thanks to Robert Millan (Closes: #115884)
* Bug fix: "does not install non-interactively", thanks to Matt Kraai
(Closes: #247782)
* This fine tunes the dependencies between targets. All of the package
building targets are ones that insert themselves into the normal flow
of policy specified targets, so they must hook themselves into the
stream. That means, in essence, that they must depend on the configure
and corresponding build targets (with stamps) and ensure that the
prep work is all done before they are invoked. The advantage is that
nothing is going to be remade more often than it needs to. It also
means we do not need to produce as many stamp files. So, the only
dependencies on any of the intermediate targets are targets that have
not been registered into the ladder created in rulesets/common/targets.mk
* The kernel image maintainer scripts have been greatly
changed. Firstly, they now use debconf; and a number of questions
have been moved to the config file (create-kimage-link-$version,
old-initrd-link, old-dir-initrd-link, old-system-map-link) while
others are asked conditionally in the postinst (depmod-error,
depmod-error-initrd, bootloader-test-error, bootloader-error). The
postinst has also become far less verbose; the users are far better
educated a decade after this was written, and there are other sources
of information about booting than the postinst of a kernel image.
* The preinst also uses debconf. All the questions asked are still here
-- we just use debconf to ask the user. Also, the priority, and need
to break non-interactive installs was re-evaluated, and the preinst
breaks in far fewer cases than it did before.
* Second, 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 are
now control if the source tree is optionally cleaned after the kernel
image package is built.
-- Manoj Srivastava <[EMAIL PROTECTED]> Thu, 3 Nov 2005 23:26:29 -0600
kernel-package (10.003) experimental; urgency=low
* Bug fix: "can not clean up the kernel source tree", thanks to
Chun-Chung Chen. (Closes: #336409)
* Bug fix: "kernel-package creates packages depending on
linux-initramfs-tools, should use linux-initramfs-tool", thanks to
Thomas Luzat. (Closes: #336724)
* Bug fix: "/usr/share/doc/kernel-package seems to contain broken
symlinks", thanks to Thomas Luzat (Closes: #336744)
* This is a major reorganization of the rules file that helps
create kernel related packages. The crusty old mechanism has been
removed, the targets are now streamlined, and the policy mandated
dependencies are now called out into a separate file. This should allow
a future enhancement to allow end users to override the behavior of
kernel-package in a fine grained fashion. Also, separating out the
variable setting for each arch into a separate file should facilitate
the delegation of that file to the person responsible for kernel images
for that architecture. And, separating out the policy mandated targets
into fine grained double colon targets allows people to add in any
additional make targets for a particular architecture, something long
requested.
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.
Unfortunately, since Make reads all the commands at startup, it
was difficult to incorporate any customizations, but the modularization
of the rules file makes it possible to have two top level files, a
minimal make file whose sole responsibility is to populate ./debian (and
run clean even when ./debian does not exist), and which uses some of the
same variable setting make snippets that the final top level Make file
uses when it resides in ./debian. The task of deciding which top level
makefile to use has now been relegated to /usr/bin/make-kpkg -- which,
if there ./debian is empty or not present, first calls the minimal
Makefile to populate it, and _then_ calls the real ./debian/rules file
to perform the actual task that it was asked. This little intelligence
in make-kpkg allows the minimal makefile, and ./debian/rules, to be far
simpler, and allows them to conform to the standards my other Debian
packages adhere to.
The goal of this release was to handle the bugs in the previous
experimental release, but to create a set of packages indistinguishable
from the ones created before. Pointedly, non-of the minor lacunae in the
Debian kernel image postinst scripts have been addressed yet. Also, the
build process is a little more verbose at the moment than it needs to be.
-- Manoj Srivastava <[EMAIL PROTECTED]> Wed, 2 Nov 2005 14:16:19 -0600
kernel-package (10.002) experimental; urgency=low
* Bug fix: "kernel-package: Problem with kernel_version.mk causes build
fauilure", thanks to Horms (Closes: #335993).
* This is a fairly large reorganization of the directory and file layout
for the package. Instead of a mostly flat directory structure with a
giant monolithic rules files, we are moving towards a more organized
structure, with finer granularity of files, which may in the future
facilitate third party replacement and overriding of parts of the build
mechanism. Also, this reorganization may make the overall structure
easier to see (though it may also result in it being harder to get the
big picture, but I doubt that).
This time around, I am trying to keep substantive changes to a minimum,
so files have just been broken up, moved around, but the package should
still more or less behave the way that it always did (apart from changing
the stem).
* kernel/rules (DEBDIR): Test to see if we have
./debian/kernel_version.mk, since all kinds of other people create
./debian
* Makefile (install): Adjust for the reorganization of the files, since
the source files are no longer in their previous locations. Keep the
destination mostly the same.
* kernel/rules: This is the one file that has faced the brunt of the
changes. Large chunks of it have been moved out into separate chunks
included in this file. The major addition has been are mechanisms to
allow the file to be broken up. The parts removed are
o) dpkg-architecture variable are now moved out to
ruleset/common/archvars.mk
o) The variables set in the file have mostly been moved to
ruleset/local-vars.mk, which shall be further broken up into
smaller parts
o) For example, the per arch variable settings have already been moved
out of ruleset/local-vars.mk into ruleset/architecture.mk -- and
shall be further fragmented into files in ruleset/arches/, so that
it would be easier to delegate ownership to domain experts.
o) The action/rules part of the file have been broken out to
ruleset/local.mk -- and shall be broken out into
ruleset/common/targets.mk (which contain policy mandated targets,
and their dependencies, and ruleset/actual_rules.mk, where the
grunt work shall be done. It may make sense to further divide
ruleset/actual_rules.mk into separate files for images, headers,
doc, and manual packages. At a later stage, actually installing
files into ./debian/tmp-<something> shall be separated out from the
subsequent packaging into separate targets (probably in the same
file), to allow finer granularity for debugging.
-- Manoj Srivastava <[EMAIL PROTECTED]> Fri, 28 Oct 2005 09:03:41 -0500
kernel-package (10.001) experimental; urgency=low
* Bug fix: "doesn't install: Internal Error: Could not find image
(/boot/vmlinuz-2.4.27-xxs1500)", thanks to Martin Michlmayr. Well,
calling kimage vmlinux.srec was breaking the postinst. However, kimage
does not seem to be used anywhere except in determining the next
value, namely, kimagesrc -- so I just added .srec to kimagesrc, and
thus eliminated the need for hacking the postinst. So the fix was
earlier in the build process, and not deferred to the postinst.
(Closes: #333220).
* Acknowledge the changes made for initrd stuff in the NMU
series. Thanks to Sven Luther for the work. I have made some changes,
for example, instead of hard-coding the list of initrd tools one
considers in the installation phase, now one can set that list by
editing /etc/kernel-pkg.conf -- and this replaces the hard coded
list. Of course, the admin at the target location can still over-ride
that list by editing /etc/kernel-img.con (note, not the same as
/etc/kernel-pkg.conf above); this makes things slightly more
flexible. Also, the list of commands does not have to be the fully
qualified path, the postinst and preinst use the PATH variable to find
the commands.
* kernel-img.conf.5: Document the fact that the ramdisk variable 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. This is
the list tried at installation time.
* kernel-pkg.conf.5: Document the fact that one can provide the default
values for the list by setting INITRD_CMD, but this list can be
overridden by the one in kernel-img.conf.5. 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.
* kernel/image.postrm, kernel/image.prerm: Added new variable for the
initrd dependency, and also modified the variable ramdisk to be a
space separated list of commands, not just a single command.
* kernel/image.postinst, kernel/image.preinst: Added new variable for
the initrd dependency, and also modified the variable ramdisk to be a
space separated list of commands, not just a single
command. (find_inird_tool): Added function to determine the list of
viable initrd creation tools present on the target system, and use it
to select which tool to use for creating the ram fs.
* Bug fix: "'man make-kpkg' typo: 'thatthis'", thanks to A
Costa (Closes: #335316).
-- Manoj Srivastava <[EMAIL PROTECTED]> Tue, 25 Oct 2005 04:00:35 -0500
--
Administration: An ingenious abstraction in politics, designed to
receive the kicks and cuffs due to the premier or president. --
Ambrose Bierce
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
