On Sat, Oct 22, 2005 at 12:41:32AM +0200, Marco Amadori wrote:
The situation right now is that a user cannot chose initramfs-tools, which
is
not what i had planed, expecting initramfs-tools to follow the proposal
shortly, which is partly a good thing since jonas proposed an even cleverer
Hello, ...
I have upgraded SVN to 2.6.14-rc5, and did a powerpc build. The only
difference was CONFIG_AIRO, and the build completed fine, and i saw that
CONFIG_AIRO was enabled in other arches, so i suppose powerpc was added or
something such, not sure, but in general things will work out fine so
Hello,
Apparently the initramfs-tools guys are refusing to implement the
--supported-* policy, and as such, the current packages will not allow to use
initramfs-tools, even though i designed it so that there should be no problem.
Well, after it almost came to blow and bad blood with maks about
Male sexual enhancement formula
http://www.sulige.com/pt/
America is a mistake, a giant mistake.
All a man can betray is his conscience.
Self-respect permeates every aspect of your life.
BRUTE, n. See HUSBAND.
The strongest principle of growth lies in human choice.
On Sat, Oct 22, 2005 at 08:22:59AM +0200, Sven Luther wrote:
But apparently this caused build problems in the arch-indep part, which was
fixed one time by Simon Horman, and then refixed another way by Bastian Blank.
No. The arch-indep part was something else: kernel-package decided that
it
On Sat, Oct 22, 2005 at 10:24:35AM +0200, Bastian Blank wrote:
On Sat, Oct 22, 2005 at 08:22:59AM +0200, Sven Luther wrote:
But apparently this caused build problems in the arch-indep part, which was
fixed one time by Simon Horman, and then refixed another way by Bastian
Blank.
No. The
On Sat, Oct 22, 2005 at 08:36:50AM +0200, Sven Luther wrote:
Apparently the initramfs-tools guys are refusing to implement the
--supported-* policy, and as such, the current packages will not allow to use
initramfs-tools, even though i designed it so that there should be no problem.
Well,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 13:41:32 +0200
Erik van Konijnenburg [EMAIL PROTECTED] wrote:
Perhaps we can simplify this further:
* have list of alteratives built into the kernel installer,
* allow ramdisk= in an /etc file to override this,
* run them all,
On Sat, Oct 22, 2005 at 01:41:32PM +0200, Erik van Konijnenburg wrote:
On Sat, Oct 22, 2005 at 08:36:50AM +0200, Sven Luther wrote:
In any case, i think the best idea would no more be to make a hard choice,
but
maybe use some kind of heuristic, or even make it configurable at package
On Sat, Oct 22, 2005 at 04:16:00PM +0200, Sven Luther wrote:
On Sat, Oct 22, 2005 at 01:41:32PM +0200, Erik van Konijnenburg wrote:
On Sat, Oct 22, 2005 at 08:36:50AM +0200, Sven Luther wrote:
In any case, i think the best idea would no more be to make a hard
choice, but
maybe use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 08:36:50 +0200
Sven Luther [EMAIL PROTECTED] wrote:
We now allow the ramdisk to contain either of :
1) undefined
2) a single field
3) a space separated list of fields.
I will go at this in reverse. In case 3), we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 16:55:39 +0200
Erik van Konijnenburg [EMAIL PROTECTED] wrote:
Also the postinsts are in perl, and my perl is not all that good,
so i dislike complex modifications of this kind.
Strong argument: you're the one doing the
On Sat, Oct 22, 2005 at 05:43:02PM +0200, Jonas Smedegaard wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 16:55:39 +0200
Erik van Konijnenburg [EMAIL PROTECTED] wrote:
Also the postinsts are in perl, and my perl is not all that good,
so i dislike complex
tag 258043 + fixed-in-experimental
tag 333842 + fixed-in-experimental
quit
This message was generated automatically in response to an
upload to the experimental distribution. The .changes file follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 21 Oct 2005 12:17:47
On Sat, Oct 22, 2005 at 04:40:37PM +0200, Jonas Smedegaard wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 08:36:50 +0200
Sven Luther [EMAIL PROTECTED] wrote:
We now allow the ramdisk to contain either of :
1) undefined
2) a single field
3) a
Processing commands for [EMAIL PROTECTED]:
tag 258043 + fixed-in-experimental
Bug#258043: kernel-patch-debian-2.6.7: doesn't list which patches are
incorporated: kernel-patch-debian-2.6.7, kernel-image-2.6.7: doesn't list which
patches are incorporated
Tags were: pending
Tags added:
On Sat, Oct 22, 2005 at 04:55:39PM +0200, Erik van Konijnenburg wrote:
On Sat, Oct 22, 2005 at 04:16:00PM +0200, Sven Luther wrote:
[...]
Also the postinsts are in perl, and my perl is not all that good, so i
dislike
complex modifications of this kind.
Strong argument: you're the one
Accepted:
kernel-image-2.6-power3-smp_2.6.13+2.6.14-rc4-0experimental.1_powerpc.deb
to
pool/main/l/linux-2.6/kernel-image-2.6-power3-smp_2.6.13+2.6.14-rc4-0experimental.1_powerpc.deb
kernel-image-2.6-power3_2.6.13+2.6.14-rc4-0experimental.1_powerpc.deb
to
On Sat, Oct 22, 2005 at 08:10:09PM +0200, Mattia Dongili wrote:
On Sat, Oct 22, 2005 at 04:55:39PM +0200, Erik van Konijnenburg wrote:
On Sat, Oct 22, 2005 at 04:16:00PM +0200, Sven Luther wrote:
[...]
Also the postinsts are in perl, and my perl is not all that good, so i
dislike
Package: yaird
Version: 0.0.11-6
Severity: critical
Yaird needs the effort to support booting from a root device on a EVMS volume.
This bug should tracks the efforts to enable yaird understand EVMS volumes.
This is needed since the next release, etch, will surely provide a linux
kernel =
On Fri, Oct 21, 2005 at 04:31:01PM +0200, Norbert Tretkowski wrote:
* Horms wrote:
I've put the packages in
http://packages.vergenet.net/testing/linux-2.6-2.6.13+2.6.14-rc4/
incase they dissapear from other sources.
The ABI revision in the version number is missing in those packages.
reassign 335229 linux-2.6
thanks
On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm having problems hotplugging my firewire CDR.
I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new
kernel version.
The error log is:
ieee1394: Error parsing configrom for node
Just thought I'd take my EVMS maintainer hat on and try to add some
constructive input to this:
EVMS support in yaird should not be difficult to add for someone who already
knows yaird. Basically, what you need to do is:
- If root= is not /dev/evms/*, _do not do anything in the initrd_. If you
Processing commands for [EMAIL PROTECTED]:
reassign 335229 linux-2.6
Bug#335229: udev: problems with firewire CDR hotplug
Bug reassigned from package `udev' to `linux-2.6'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On Sat, Oct 22, 2005 at 08:52:45PM +0200, Marco d'Itri wrote:
reassign 335229 linux-2.6
thanks
On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm having problems hotplugging my firewire CDR.
I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new
kernel version.
On Sat, Oct 22, 2005 at 09:18:44PM +0200, Steinar H. Gunderson wrote:
Just thought I'd take my EVMS maintainer hat on and try to add some
constructive input to this:
EVMS support in yaird should not be difficult to add for someone who already
knows yaird. Basically, what you need to do is:
Alle 21:18, sabato 22 ottobre 2005, Steinar H. Gunderson ha scritto:
EVMS support in yaird should not be difficult to add for someone who
already knows yaird. Basically, what you need to do is:
We need a perl hacker.
Code speaking, I'm not a perl hacker, too bad, but I understood that,
On Sat, Oct 22, 2005 at 09:47:12PM +0200, Marco Amadori wrote:
- Make sure /dev/ is writable, and mkdir /dev/evms.
Translate this in perl plz :-)
Well, the make sure part depends on how yaird works. You may have to mount
a tmpfs over /dev/evms if the initrd is read-only. (This is during _boot_
On Sat, Oct 22, 2005 at 09:54:54PM +0200, Steinar H. Gunderson wrote:
On Sat, Oct 22, 2005 at 09:47:12PM +0200, Marco Amadori wrote:
- Make sure /dev/ is writable, and mkdir /dev/evms.
Translate this in perl plz :-)
Well, the make sure part depends on how yaird works. You may have to
On Sat, Oct 22, 2005 at 09:47:12PM +0200, Marco Amadori wrote:
Alle 21:18, sabato 22 ottobre 2005, Steinar H. Gunderson ha scritto:
EVMS support in yaird should not be difficult to add for someone who
already knows yaird. Basically, what you need to do is:
We need a perl hacker.
Mattia,
On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm having problems hotplugging my firewire CDR.
I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new
kernel version.
The error log is:
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 08:36:50 +0200
Sven Luther [EMAIL PROTECTED] wrote:
[regarding kernel-package becoming smarter at picking ramdisk-tool]
In any case, i think the best idea would no more be to make a hard
choice, but maybe use some kind of
On Sat, Oct 22, 2005 at 08:10:09PM +0200, Mattia Dongili wrote:
On Sat, Oct 22, 2005 at 04:55:39PM +0200, Erik van Konijnenburg wrote:
On Sat, Oct 22, 2005 at 04:16:00PM +0200, Sven Luther wrote:
[...]
Also the postinsts are in perl, and my perl is not all that good, so i
dislike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 335230 important
thanks
On Sat, 22 Oct 2005 20:37:21 +0200
Marco Amadori [EMAIL PROTECTED] wrote:
Release is set to critical because no EVMS support and kernels
=2.6.13 will broke any EVMS systems running safe since now with old
Processing commands for [EMAIL PROTECTED]:
severity 335230 important
Bug#335230: Yaird should support booting from an EVMS (local, at least) volume
Severity set to `important'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On 10/21/05, maximilian attems [EMAIL PROTECTED] wrote:
On Fri, 21 Oct 2005, Thibaut VARENE wrote:
On 10/16/05, Maximilian Attems [EMAIL PROTECTED] wrote:
there will be soon a 2.6.14 in exeperimental, would be cool to check
that too before bugging alsa upstream.
I highly doubt this
[EMAIL PROTECTED] wrote:
On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm having problems hotplugging my firewire CDR.
I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new
kernel version.
The error log is:
ieee1394: Error parsing configrom for node
Package: yaird
Version: 0.0.11-6
Severity: normal
Tags: patch
Hi, ...
On my titanium powerbook, yaird fails with :
yaird error: unrecognised device:
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io
yaird error: unrecognised device:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
First of all: I am in no way mad at you. :-)
I see nothing secret in your mail, and want to share our discussion
with the world - maybe others can learn from it (or maybe they find my
arguments stupid and can then point fingers at me). So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Oct 2005 23:50:10 +0200
Sven Luther [EMAIL PROTECTED] wrote:
BTW, my new plan makes me consider two things :
1) how can i check if there is only one entry in the ramdisk=
line ? Reading the length of the list, or doing a shift and
yaird_0.0.11-7_powerpc.changes uploaded successfully to localhost
along with the files:
yaird_0.0.11-7.dsc
yaird_0.0.11-7.diff.gz
yaird_0.0.11-7_powerpc.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Your message dated Sat, 22 Oct 2005 18:17:24 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#335264: fixed in yaird 0.0.11-7
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
Accepted:
yaird_0.0.11-7.diff.gz
to pool/main/y/yaird/yaird_0.0.11-7.diff.gz
yaird_0.0.11-7.dsc
to pool/main/y/yaird/yaird_0.0.11-7.dsc
yaird_0.0.11-7_powerpc.deb
to pool/main/y/yaird/yaird_0.0.11-7_powerpc.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 335264
Your message dated Sat, 22 Oct 2005 22:18:08 -0700 (PDT)
with message-id [EMAIL PROTECTED]
and subject line No further details, closing
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
44 matches
Mail list logo
