Title: backboard
cadenza somerset centroid
Are you looking for Medicine? Obtain it now!
We have all tablets you could possibly need!
All your pills in one place!
Stop receiving promotional material
On Thu, Jan 20, 2005 at 05:46:39PM +0900, Horms wrote:
> On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> > On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:2
Tenho uma loja de porodutos de informatica e gostaria
de ser parceiro de voces...
Caso haja interesse da sua parte, mande-me um email
com uma lista detalhada de preços, colocando o modelo
do original e do compativel. Tenho certa urgencia,
estou a procura desses cartuchos compatíveis de
impressora
Package: debian-installer
Followup-For: Bug #288522
Ok, I did an lsmod just after "network hardware detection." 1394
devices were not listed. After some fiddling, I found that if i did
a "modprobe ohci1394" during the language selection that once I got to
the network hardware selection that the
Package: debian-installer
Followup-For: Bug #288522
Ok, I booted the installer with "linux26." After the "network hardware
detection" in stage 1, I am presented with the option to choose my main
network interface from only:
eth0: 3com card
eth1: wireless ethernet
Obviously, fire
Package: debian-installer
Followup-For: Bug #288522
> But what is eth0?
eth0 is my wired lan interface; a 3c59x built in to the motherboard. i
do not have a lan cable plugged in, and it appears that eth0 does not
get configured at boot (for either kernel).
> Right, the devices will in fact be d
I've analyzed this change for potential negative impacts on debian-installer
and find none. The existing d-i CD images all include debootstrap-udeb, so
cannot be broken by this change. The d-i netboot images would not include
debootstrap-udeb, but they also would be pulling all packages from the
* Joey Hess <[EMAIL PROTECTED]> [2005-01-20 16:13]:
> mips
> No abiname. Kernel updated and in testing; udebs updated.
> No initrd daily builds since Dec 31 so new udebs untested.
I made the daily build on Dec 31 with the new kernel so udebs are
tested. In any case, I asked Thiemo Seu
On Jan 20, 2005 at 08:31:55PM +0100, Christian Perrier wrote:
> The advantage for translators is obviousÂ: the interface is very
> simple and involved people can focus on the real workÂ: deal with PO
> files, and just forget about "nasty" stuff such as dealing with
> various Revision Control Syste
On Thu, Jan 20, 2005 at 11:11:14PM +0100, Christian T. Steigies wrote:
> > > I have no idea about the abichanges, m68k uses no abiname? Is that a
> > > problem?
> > The downside of not includeing an abiname in the package name is that
> > past d-i releases will break once the updated kernels and
On Thu, Jan 20, 2005 at 04:58:10PM -0500, Joey Hess wrote:
> Christian T. Steigies wrote:
> > I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make
> > it
> > urgent...: Too young, only 7 of 10 days old
> > For 2.4.27 I am waiting for the latest kernel-source to be released be
On Thu, Jan 20, 2005 at 10:25:47PM +0100, Christian T. Steigies wrote:
> On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
> >
> > Update for current status, 10 days after my first mail:
> >
> > m68k
> > No abiname; not updated. ?
> >
> > [This is another arch that I'd consider
Christian T. Steigies wrote:
> I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
> urgent...: Too young, only 7 of 10 days old
> For 2.4.27 I am waiting for the latest kernel-source to be released before I
> build new images. This is supposed to happen today/tomorrow? I
Accepted:
usb-discover_1.02.dsc
to pool/main/u/usb-discover/usb-discover_1.02.dsc
usb-discover_1.02.tar.gz
to pool/main/u/usb-discover/usb-discover_1.02.tar.gz
usb-discover_1.02_all.udeb
to pool/main/u/usb-discover/usb-discover_1.02_all.udeb
Announcing to debian-devel-changes@lists.debian.or
On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
>
> Update for current status, 10 days after my first mail:
>
> m68k
> No abiname; not updated. ?
>
> [This is another arch that I'd consider releasing d-i rc3 without
> it being updated for the kernel security fixes.]
usb-discover_1.02_hppa.changes uploaded successfully to localhost
along with the files:
usb-discover_1.02.dsc
usb-discover_1.02.tar.gz
usb-discover_1.02_all.udeb
Greetings,
Your Debian queue daemon
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.6
> severity 291006 serious
Bug#291006: Package: installation-reports
Severity set to `serious'.
> severity 291362 serious
Bug#291362: installation-reports: LVM install failed due to miss
Package: installation-reports
Debian-installer-version: d-i rc2 floppies (root.img + boot.img +
net-drivers.img)
uname -a: Linux pitr 2.4.27-2-586-tsc #1 Thu Dec 30 18:06:49 JST 2004 i586
GNU/Linux
Date: 20050119-20
Method: Floppy boot and network installation
Machine: Fuijutsu desktop PC
Process
Wesley W. Terpstra wrote:
> On Thu, Jan 20, 2005 at 02:59:00PM -0500, Joey Hess wrote:
> > initrd-tools 0.1.76 changed to abort on install to LVM if dmsetup was
> > not installed. I think this was a mistake. I'm ccing tbm, who made the
> > change.
>
> I made the change.
Right, tbm only committed
Joey Hess wrote:
> Before we can release d-i rc3 we need all the kernels updated with at
> least some security fixes, notably the ones that change the kernel
> module ABI, and we need to update things to reflect the new kernel
> "abiname". Here's my understanding of the current status of that:
Upd
severity 291006 serious
merge 291362 291006
thanks
Based on this response, the only bug in this installation report is the
same as #291362
- Forwarded message from Tiziano Müller <[EMAIL PROTECTED]> -
From: Tiziano Müller <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 21:13:25 +0100
To: Joey
On Thu, Jan 20, 2005 at 02:59:00PM -0500, Joey Hess wrote:
> initrd-tools 0.1.76 changed to abort on install to LVM if dmsetup was
> not installed. I think this was a mistake. I'm ccing tbm, who made the
> change.
I made the change.
> This was apparently added as part of a patch to support encryp
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.6
> severity 291362 serious
Bug#291362: installation-reports: LVM install failed due to missing dmsetup
Severity set to `serious'.
>
End of message, stopping processing here.
Please cont
Processing commands for [EMAIL PROTECTED]:
> severity 291006 serious
Bug#291006: Package: installation-reports
Severity set to `serious'.
> merge 291362 291006
Bug#291006: Package: installation-reports
Bug#291362: installation-reports: LVM install failed due to missing dmsetup
Mismatch - only Bug
Carlos Z.F. Liu wrote:
> After some discussions in debian-chinese-gb[1] and some debian related
> web forum in TW[2] and HK[3], I made many changes in chinese-s,
> chinese-s-desktop, chinese-t, and chinese-t-desktop tasks. See attached
> tarball. Thanks in advance for updating them.
Could you writ
severity 291362 serious
reassign 291362 initrd-tools
thanks
Lupe Christoph wrote:
> Kernel installation (2.4.27) failed because the initrd could not be
> generated. dmsetup is missing.
>
> Root is on a DM device, but dmsetup not installed
> Failed to create initrd image.
>
> Same happens with 2.
A. Raulino wrote:
> Install boot loader:[E] remark: lilo fails to be wrote at mbr... but
> grub instalation at mbr is ok!
Could you provide any more details on this problem? Error messages, log
files, whatever..
--
see shy jo
signature.asc
Description: Digital signature
Tiziano Müller wrote:
> - Installer should maybe warn someone who's trying to create the boot
> partition in an LVM-Volume (-> grub can't install in LVM-Volume)
The installer should detect that the boot partition is on lvm and use
lilo instead of grub. Didn't this work for you?
> - dmsetup shoul
Michael Gilbert wrote:
> As can be seen, it appears that the 1394 firewire interface is
> enumerated as eth1, and my wlan is enumerated as eth2.
But what is eth0?
> If I examine
> dmesg when booting the 2.4 kernel, I see that the 1394 firewire device
> is not enumerated as an interface and my wla
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.6
> reassign 291398 installation-reports
Bug#291398: Debian Sarge-Doesnt recognise SATA harddisk
Bug reassigned from package `installation-reports' to `installation-reports'.
> tags 2913
I'm crossposting this to -boot as I'm considering using the above for
D-I material, but indeed this is not restricted to D-I stuff.
The Ubuntu project recently announced the Rosetta project while the
Translate Toolkit team announced the Pootle project at about the same
moment.
Rosetta: https://la
Frans Pop wrote:
> In that case, wouldn't svn.d-i.debian.org be a lot nicer and future-proof?
At least during the recent move, wiggy was able to update independently the
svn.d-i.alioth.debian.org url but not the other one. I don't know why
though.
> Also, shouldn't the base README [1] reflect tha
On Mon, Jan 03, 2005 at 08:35:36PM +0100, Frans Pop wrote:
> It looks like you are one of those users for whom we invented expert and
> medium priority installs.
Actually, yes. After reading the docs I found that the installer does
exactly the right thing when invoked with the right priority.
Th
Package: Debian Sarge
Version: Weekly
I tried installing debian-sarge on HP machine dx6100M
which has SATA hard-disk. It doesn’t recognize the hard-disk. In case of
debian-woody it recognizes but after installing it searches for IDE HD.
Regards
Mangesh
Processing commands for [EMAIL PROTECTED]:
> reassign 291398 installation-reports
Bug#291398: Debian Sarge-Doesnt recognise SATA harddisk
Bug reassigned from package `installation-reports' to `installation-reports'.
> --
Stopping processing here.
Please contact me if you need assistance.
Debia
Processing commands for [EMAIL PROTECTED]:
> reassign 291398 installation-reports
Bug#291398: Debian Sarge-Doesnt recognise SATA harddisk
Warning: Unknown package 'debian'
Warning: Unknown package 'sarge'
Bug reassigned from package `debian sarge' to `installation-reports'.
>
End of message, sto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Colin Watson wrote:
| On Thu, Jan 20, 2005 at 01:38:20AM -0500, Daniel Dickinson wrote:
|
|>Am I missing a step, or doing something wrong, the process for
|>downloading udebs not up-to-date, or something else?
|
|
| If you're using the cdrom initrd, per
LAGOS OFFICE
22 ALLEN AVENUE IKEJA
LAGOS-NIGEGRIA
TEL: 234-1-7753961
FAX: 234-1-7596499
LONDON OFFICE:
DUCK ISLAND COTTAGE
LONDON W2 2UH
Fax:+44 8701332609
NOTIFICATION OF BEQUEST
This is sequel to your non response of our earlier letter to you on
be
On Thu, Jan 20, 2005 at 01:38:20AM -0500, Daniel Dickinson wrote:
> I've been trying to build d-i and get the associated udebs. I can
> successfully build now that I have reinstalled my system (which I
> screwed up by doing things wrong before), but the install process fails,
> and investigation r
Package: installation-reports
Severity: important
Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-netinst.iso
19-Jan-2005 23:05
uname -a: Install failed
Date: 2004-01-19 10:30
Method: CD-ROM based install
Machine: Homebrew
Proc
> Is Finnish planned to be included?
It will as soon as things will be more stable and I'll have some time
to experiment.
Here's the story which explains why Finnish is not supported (in case you
were interested):
When I first set up the spellchecking system, I did that on my Sarge
box and I ins
On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > > > As far as I know, no other arches except amd64 (not
Processing commands for [EMAIL PROTECTED]:
> severity 291347 important
Bug#291347: debian-installer: SiS5513 IDE Module doesn't work,, must use
ide-generic or ide based systems won't work
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Package: debian-installer
Severity: critical
Justification: breaks system unless you can boot another way and apply
workaround
This is also a kernel bug, but I don't know how to send the report to
both debian-installer (which needs to work around the problem or get
questions on why an affected syst
I have the great pleasure to announce that Siim Põder and other
Estonian translators have completed the work on Debian Installer
level1 translations for their language.
Now, Siim, you can go up for level2. This is a bit more complicated as
there are several packages involvedbut remember:
For base
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been trying to build d-i and get the associated udebs. I can
successfully build now that I have reinstalled my system (which I
screwed up by doing things wrong before), but the install process fails,
and investigation reveals that (at least) the p
On Tue, Jan 18, 2005 at 12:06:02AM +0200, Konstantinos Margaritis wrote:
> 1) It tries to read the debconf variable debian-installer/keymap.
> If it finds it, it uses this map[1] to preseed the XFree86 keyboard
> with the correct values. All these values have been collected by
> asking the correc
47 matches
Mail list logo
