[ CCed maintainers for delicate rev-depends ]
Hi,
Some weeks ago I uploaded directfb 1.0.1-2 to experimental. I've
successfully built the following packages, which are the only ones
really Build-Depending on libdirectfb-dev:
In unstable
---
directvnc_0.7.5-8
freesci_0.3.5-5
gst
Hello,
Our company is producing some high class leather products, Jackets Wallets and
all kind of stuff, i wanted to know if anyone is interested in
really cheap leather prodcuts please.
Nudge me back at
[EMAIL PROTECTED]
Regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi RMs,
Please unblock ttf-cjk-compact 1.11.
This package has CJK fonts are needed for newer d-i.
I believe it's safe to unfreeze this package usually because
this udeb package is related with only CJK fonts of GUI d-i.
Thanks,
- --
Kenshi Muto
[EM
Package: debian-installer
Version: 20070308
Severity: wishlist
Please add Release.gpg files to the official releases on CDROMs and
DVDs, and anything else needed for aptitude to verify the authenticity
of the disks.
I just went through a lot of trouble trying to get aptitude to quit
warning me th
Package: installation-reports
Boot method: Network install using serial console
boot: install console=ttyS0,17200
Image version:
ftp://ftp.uk.debian.org/debian/dists/etch/main/installer-i386/20070308etch1/images/netboot/mini.iso
or:
ftp://ftp.uk.debian.org/debian/dis
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Otavio Salvador]
>> Isn't it 1011:a511?
>
> Nope, it isn't. That surprised me too, as I looked in the
> modules.pcimap file. The machine I test on do not have the 1011:a511,
> but the 1011:a501 device.
hum ... no idea _why_ it's being loaded th
Processing commands for [EMAIL PROTECTED]:
> severity 445148 serious
Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck
Severity set to `serious' from `important'
> reassign 445148 debian-installer 20070308
Bug#445148: S390: Build w/ /boot partition succeeds, but re-bo
severity 445148 serious
reassign 445148 debian-installer 20070308
thanks
On Monday 08 October 2007, Frans Pop wrote:
> This does not seem to be an installation problem. Instead it looks like
> either the boot loader or the kernel is not releasing the partition
> holding /boot after the kernel and/
[Otavio Salvador]
> It was tested using 2.6.22 right?
I tested using the 2.6.18 kernel in etch.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Otavio Salvador]
>> Isn't it 1011:a511?
>
> Nope, it isn't. That surprised me too, as I looked in the
> modules.pcimap file. The machine I test on do not have the 1011:a511,
> but the 1011:a501 device.
hum ... no idea _why_ it's being loaded th
Processing commands for [EMAIL PROTECTED]:
> reopen 442891
Bug#442891: installation-report: setting up the clock + configuring package
manager
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
Bug reopened, originator no
On 10/6/07, Thomas Jeunet <[EMAIL PROTECTED]> wrote:
>
> I get the error in the win32 part of the install. When in expert mode,
> choosing the proxy here (tried name an IP of proxy) doesn't change
> anything.
>
I tried to leave this field blank and it worked... I have no idea why,
I'm not using a
[Otavio Salvador]
> Isn't it 1011:a511?
Nope, it isn't. That surprised me too, as I looked in the
modules.pcimap file. The machine I test on do not have the 1011:a511,
but the 1011:a501 device.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Petter Reinholdtsen]
>> A quick look in /lib/modules/2.6.18-5-686/modules.pcimap tell me that
>> the conflicting kernel module issue only affect one PCI id. These are
>> the devices supported by the two modules:
>>
>> 1044:a511 dpt_i2o i2o_cor
tags 445148 confirmed
reassign 445148 s390-tools
thanks
> Install boot went as expected, up until the first re-boot. After
> rebooting, system fails in fsck because one of the partitions is
> "already mounted".
>
> Configuration is a 125 cylinder /dev/dasda1, which is to be mounted
> as /boot, and
Processing commands for [EMAIL PROTECTED]:
> tags 445148 confirmed
Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck
There were no tags set.
Tags added: confirmed
> reassign 445148 s390-tools
Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fs
[Petter Reinholdtsen]
> A quick look in /lib/modules/2.6.18-5-686/modules.pcimap tell me that
> the conflicting kernel module issue only affect one PCI id. These are
> the devices supported by the two modules:
>
> 1044:a511 dpt_i2o i2o_core
> 1044:a501 dpt_i2o
> 8086:1962 i2o_core
This pro
17 matches
Mail list logo
