-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010年06月29日 18:33, maximilian attems wrote:
>> FTR, I've attached the hook scripts template. The @...@ stuff is
>> substituted at package build time.
>
> hmm I don'T see at a quick look why it failed.
>
> but I don't get it'S purpose?
>
> why do y
On Tue, Jun 29, 2010 at 09:05:55AM +0900, Olaf Meeuwissen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thanks for the info. I've checked the dash and bash manual pages but
> running under errexit seems to be the same as using `set -e`. The hook
> provided by iscan has done a `set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010?06?29? 07:55, maximilian attems wrote:
> On Tue, Jun 29, 2010 at 08:02:03AM +0900, Olaf Meeuwissen wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 2010???06???28??? 17:31, maximilian attems wrote:
>>> On Mon, Jun 28, 2010 at
On Tue, Jun 29, 2010 at 08:02:03AM +0900, Olaf Meeuwissen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2010???06???28??? 17:31, maximilian attems wrote:
> > On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010年06月28日 17:31, maximilian attems wrote:
> On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Image Scan! for Linux upstream maintainer here.
>>
>> Care to point out why isca
On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Image Scan! for Linux upstream maintainer here.
>
> Care to point out why iscan is the culprit? I went through the logs but
> nothing ran a bell.
you are sending the message to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Image Scan! for Linux upstream maintainer here.
Care to point out why iscan is the culprit? I went through the logs but
nothing ran a bell.
If possible we'd like to get a fix out before squeeze goes stable ;-)
- --
Olaf Meeuwissen, LPIC-2
tags 586554 - moreinfo
tags 586554 + pending
thanks
* thebickhams [Tue Jun 22, 2010 at 12:03:29AM +0100]:
[...]
> find /usr/share/initramfs-tools -print0 | xargs -0 dpkg -S
> iscan, initramfs-tools, udev, dmsetup: /usr/share/initramfs-tools
> iscan: /usr/share/initramfs-tools/hooks/iscan
[...]
find /usr/share/initramfs-tools
/usr/share/initramfs-tools
/usr/share/initramfs-tools/modules
/usr/share/initramfs-tools/conf-hooks.d
/usr/share/initramfs-tools/hooks
/usr/share/initramfs-tools/hooks/klibc
/usr/share/initramfs-tools/hooks/iscan
/usr/share/initramfs-tools/hooks/busybox
/usr/share/i
hello,
On Mon, 21 Jun 2010, thebickhams wrote:
> log file as attachment
from a quick look at this looks like an older mkinitramfs,
we'd need belows output from the one that fails to install:
> sh -x /usr/sbin/mkinitramfs -o
> /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sid
* maximilian attems [Tue Jun 22, 2010 at 12:06:00AM +0200]:
> your first report shows clearly an mkinitramfs failure,
> currently we don't know where to trace it.
While discussing this with maks we also noticed that this could be
caused by a problem in a hook script shipped with sidux.
thebickh
* Michael Prokop [Mon Jun 21, 2010 at 01:22:01PM +0200]:
> * thebickhams [Mon Jun 21, 2010 at 12:11:12PM
> +0100]:
> > Still won't update. I note three other people have reported the issue in
> > the sidux forums; both 32bit and 64bit.
> Please provide output of:
> apt-get --download-only
Hi Michael,
Still won't update. I note three other people have reported the issue in
the sidux forums; both 32bit and 64bit.
Best regards,
Dai
The following packages will be upgraded:
initramfs-tools
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/84.9kB of ar
* thebickhams [Mon Jun 21, 2010 at 12:11:12PM +0100]:
> Still won't update. I note three other people have reported the issue in
> the sidux forums; both 32bit and 64bit.
Please provide output of:
apt-get --download-only --reinstall --print-uris install
2.6.34-0.slh.9-sidux-amd64
so I can
* thebickhams [Mon Jun 21, 2010 at 11:35:52AM +0100]:
> On 06/21/2010 11:17 AM, Michael Prokop wrote:
>> sh -x /usr/sbin/update-initramfs -u 1>/tmp/update-initramfs.log 2>&1
> Running as root (not sudo), log file attached.
> + STATEDIR=/var/lib/initramfs-tools
[...]
> + return 0
Seems to work
* thebickhams [Mon Jun 21, 2010 at 11:07:01AM +0100]:
> On 06/21/2010 09:43 AM, Michael Prokop wrote:
>> sh -x /usr/sbin/mkinitramfs -o
>> /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sidux-amd64
>> 1>/tmp/mkinitramfs.log 2>&1
> + umask 0022
[...]
> + exit 0
Ok, this works
* thebickhams [Mon Jun 21, 2010 at 08:51:00AM +0100]:
> The output is as follows :
> # sh -x /var/lib/dpkg/info/initramfs-tools.postinst
> + set -e
> + [ ! -e /etc/initramfs-tools/modules ]
> + [ x != xtriggered ]
> + dpkg --compare-versions ge 1.14.5ubuntu10~~
> + DPKG_MAINTSCRIPT_PACKAGE= upd
Processing commands for cont...@bugs.debian.org:
> tags 586554 + moreinfo
Bug #586554 [initramfs-tools] initramfs-tools fails to upgrade from 0.96.1 to
0.97
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
586554: http://bugs.debian.org/cgi-
tags 586554 + moreinfo
thanks
* drb [Sun Jun 20, 2010 at 03:42:34PM +0100]:
> Unpacking replacement initramfs-tools ...
> Processing triggers for man-db ...
> Setting up initramfs-tools (0.97) ...
> Installing new version of config file /etc/initramfs-tools/update-
> initramfs.conf ...
> Install
Package: initramfs-tools
Version: 0.94.4
Severity: important
Unpacking replacement initramfs-tools ...
Processing triggers for man-db ...
Setting up initramfs-tools (0.97) ...
Installing new version of config file /etc/initramfs-tools/update-
initramfs.conf ...
Installing new version of config fil
20 matches
Mail list logo
