I just forgot to mention that I was using
debian-Lenny-DI-rc2-sparc-netinst.iso
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
signature.asc
Description: PGP signature
Package: debian-installer
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I just wanted to test something on sparc and tried to install Lenny in
Qemu and it fails, it looks like silo configuration is somehow broken,
but I don't know the platform at all. 4.0r6 installation start
Package: console-setup
Version: 1.29
Severity: normal
Tags: patch
Hello,
While upgrading from console-data's keymaps to console-setup, my caps
lock became a shift lock, and the caps lock led doesn't work any more.
This is due to these few lines:
# A hack to work around a bug in the kernel/load
On Thursday 05 February 2009, Michal Čihař wrote:
> I just wanted to test something on sparc and tried to install Lenny in
> Qemu and it fails, it looks like silo configuration is somehow broken,
> but I don't know the platform at all. 4.0r6 installation starts fine,
> so it looks like a regression
Hi
Dne Thu, 5 Feb 2009 10:41:41 +0100
Frans Pop napsal(a):
> On Thursday 05 February 2009, Michal Čihař wrote:
> > I just wanted to test something on sparc and tried to install Lenny in
> > Qemu and it fails, it looks like silo configuration is somehow broken,
> > but I don't know the platform a
Your message dated Thu, 5 Feb 2009 10:55:04 +0100
with message-id <200902051055.05091.elen...@planet.nl>
and subject line Re: Bug#514211: lenny not installable on sparc (Qemu)
has caused the Debian Bug report #514211,
regarding lenny not installable on sparc (Qemu)
to be marked as done.
This mean
On Thu, Feb 05, 2009 at 10:34:09AM +0100, Samuel Thibault wrote:
>
> If the reason has been lost in history (the code dates back from at
> least 2005) then we should probably apply the patch to fix the common
> case, and let the real bug reappear and get fixed the proper way.
The reason is known
Anton Zinoviev, le Thu 05 Feb 2009 13:04:42 +0200, a écrit :
> On Thu, Feb 05, 2009 at 10:34:09AM +0100, Samuel Thibault wrote:
> >
> > If the reason has been lost in history (the code dates back from at
> > least 2005) then we should probably apply the patch to fix the common
> > case, and let th
Michal Čihař writes:
> I just wanted to test something on sparc and tried to install Lenny in
> Qemu and it fails, it looks like silo configuration is somehow broken,
> but I don't know the platform at all.
Do you try to boot the Lenny installer with a sparc32 qemu system? That
won't work. Len
I found the patch that needs to be applied and it is relatively simple.
http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Anton Zinoviev, le Thu 05 Feb 2009 13:28:07 +0200, a écrit :
> I found the patch that needs to be applied and it is relatively simple.
>
> http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html
Thanks, that's mine :)
I don't have the time to develop right now, but the idea would then be
Samuel Thibault, le Thu 05 Feb 2009 12:39:08 +0100, a écrit :
> Anton Zinoviev, le Thu 05 Feb 2009 13:28:07 +0200, a écrit :
> > I found the patch that needs to be applied and it is relatively simple.
> >
> > http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html
>
> Thanks, that's mine :
Samuel Thibault, le Thu 05 Feb 2009 10:34:09 +0100, a écrit :
> Why is this hack needed?
Oh, that's probably due to
http://bugzilla.kernel.org/show_bug.cgi?id=7746
Bummer, that's not an easy one.
Samuel
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsu
Package: debian-installer
Version: 20090123
Severity: important
The installation guide says that we support sun4v systems, but our
silo.conf file for netboot and CDs only lists sun4u. Note that this
should also be changed in debian-cd when it is added for D-I.
--
To UNSUBSCRIBE, email to deb
>On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote:
>>Hi folks,
>>
>>Apologies for the massive cross-posting, but I'm trying to arrange
>>some discussions between the various teams, or at least those members
>>who will be at FOSDEM. Topics I'd like us to talk about include:
>>
>> 1. ho
Hi,
On Donnerstag, 5. Februar 2009, Steve McIntyre wrote:
> >>Then: when and where would be a good time to meet up?
> Hello? Anyone?
Looking at http://wiki.debian.org/FosdemVideo2009 I'd suggest either Saturday
from 17:30-18:15 (right before your talk, Steve) or sunday between 10 and 13.
Or sat
On Thu, Feb 05, 2009 at 12:39:08PM +0100, Samuel Thibault wrote:
>
> I don't have the time to develop right now, but the idea would then be
> to double the number of keymaps to 128, to have "capsed" versions of
> each of the current keycode translations.
A good idea. :)
Idealy some future versi
On Thu, 05, Feb, 2009 at 12:30:46PM +, Steve McIntyre spoke thus..
> >>Apologies for the massive cross-posting, but I'm trying to arrange
> >>some discussions between the various teams, or at least those members
> >>who will be at FOSDEM. Topics I'd like us to talk about include:
> >>
> >> 1. h
On Thursday 05 February 2009, Steve McIntyre wrote:
> >On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote:
> >>Hi folks,
> >>
> >>Apologies for the massive cross-posting, but I'm trying to arrange
> >>some discussions between the various teams, or at least those members
> >>who will be
On Thu, 2009-02-05 at 12:30 +, Steve McIntyre wrote:
> >>Then: when and where would be a good time to meet up?
Given we all tend to arrive in dribs-and-drabs on Friday night, I'd
suggest Saturday some time. Perhaps either have a "working lunch" or, if
the group is likely to be too large, perha
Quoting Filipus Klutiero (chea...@gmail.com):
> This is an install on the same target as #497318. Everything went as
> expected,
> which means that the 3 issues mentioned there were fixed. Additionally, I
> used amd64 instead of i386. The test
> image I downloaded is supposed to be the same a
On Thu, Feb 05, 2009 at 12:30:46PM +, Steve McIntyre wrote:
> >On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote:
> >>Hi folks,
> >>
> >>Apologies for the massive cross-posting, but I'm trying to arrange
> >>some discussions between the various teams, or at least those members
> >>
Dne Thu, 5 Feb 2009 10:55:04 +0100
Frans Pop napsal(a):
> On Thursday 05 February 2009, Michal Čihař wrote:
> > I just wanted to test something on sparc and tried to install Lenny in
> > Qemu and it fails, it looks like silo configuration is somehow broken,
> > but I don't know the platform at al
On Fri, Jan 30, 2009 at 07:39:54PM -0200, Otavio Salvador wrote:
> Guido Günther writes:
>
> > Frans Pop schrieb:
> >> On Friday 30 January 2009, Guido Günther wrote:
> >>> The i386 businesscard iso lacks the libaio1-udeb so "multipath -l"
> >>> won't work due to lack of libaio.so.1 and the syste
On Thu, Jan 29, 2009 at 04:27:54PM +0100, Guido Günther wrote:
> Hi,
> Attached is an updated version of the multipath support patch for
> grub-legacy. It applies cleanly to 0.97-47lenny2. It's the only
> missing piece for getting multipath support to work in lenny's d-i:
> http://wiki.debian.org/
Package: installation-reports
Severity: normal
Just passing along a report of a smooth and successful installation of
lenny RC2 for PPC.
The only snag was when I tried to install onto an existing partition
without re-creating the filesystem. I haven't managed to find any
details in the logs rega
FYI: The status of the debootstrap source package
in Debian's testing distribution has changed.
Previous version: 1.0.10
Current version: 1.0.10lenny1
--
This email is automatically generated; the Debian Release Team
is responsible.
See http://release.debian.org/testing-watch/ for more inf
Hi,
just as an exercise what might be done to fix this:
It would seem that the options are
- not fix it (for now),
- find something in current tar that works (I didn't),
- switch off tar,
- try to do something with tar
(new upstream - vs. release: ugh - has a "apply to symlink target"
--trans
On Thu, 2009-02-05 at 18:20 +0100, Thomas Viehmann wrote:
> just as an exercise what might be done to fix this:
> It would seem that the options are
> - not fix it (for now),
> - find something in current tar that works (I didn't),
> - switch off tar,
> - try to do something with tar
> (new upst
On Thu, Feb 05, 2009 at 06:20:24PM +0100, Thomas Viehmann wrote:
> just as an exercise what might be done to fix this:
> It would seem that the options are
> - find something in current tar that works (I didn't),
There is nothing.
> - switch off tar,
I intend to replace tar with a custom unpack
On Thu, Feb 05, 2009 at 10:44:25AM -0700, Bdale Garbee wrote:
> How about just fixing the offending package to use a relative symlink,
> like /lib64 -> lib?
This would only affect one part of the problem. But this bug is about
the problem that it will write outside of the new root if it encounters
Steve McIntyre writes:
>>>Then: when and where would be a good time to meet up?
>
> Hello? Anyone?
I won't be at FOSDEM :(
--
O T A V I OS A L V A D O R
-
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49
Hi,
On Thu Feb 05, 2009 at 12:30:46 +, Steve McIntyre wrote:
> >On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote:
> >>Hi folks,
> >>
> >>Apologies for the massive cross-posting, but I'm trying to arrange
> >>some discussions between the various teams, or at least those members
>
This one time, at band camp, Mark Hymers said:
> On Thu, 05, Feb, 2009 at 12:30:46PM +, Steve McIntyre spoke thus..
> > >>Apologies for the massive cross-posting, but I'm trying to arrange
> > >>some discussions between the various teams, or at least those members
> > >>who will be at FOSDEM. T
Following my recent call for testers, I've had 7 positive and
0 negative reports, so I've uploaded mdadm 2.6.7.2-1 to unstable,
which should hopefully take care of those RC bugs once and for all.
The new version should not have any effect on the operation within
D-I at all.
Please unblock.
--
Hi,
thanks for your replies. Again, this is mostly because I needed some
idle occupation and am not into sudoku. Apologies for presenting it a
way that looked like a proposal.
Bdale Garbee wrote:
> How about just fixing the offending package to use a relative symlink,
> like /lib64 -> lib? This
36 matches
Mail list logo
