On Mon, Sep 18, 2006 at 11:56:30PM +0200, Geert Stappers wrote:
> On Mon, Sep 18, 2006 at 11:24:17PM +0200, De Leeuw Guy wrote:
> > Another question : where I post this kind of report ?
> > If debian-boot is not the good place, ok, sorry for the disturb, but where ?
>
> I assume that the pointer t
On Mon, Sep 18, 2006 at 02:44:40PM +0100, David Goodenough wrote:
> On Monday 18 September 2006 14:13, Frans Pop wrote:
> > On Monday 18 September 2006 14:56, De Leeuw Guy wrote:
> > > I just finish a new net-install with the daily builds 20060918 of
> > > testing. I have a strange bug with the net
On Tue, Sep 19, 2006 at 12:19:57PM +0200, Amaya wrote:
> I feel my previous email could be taken as harsh on my side, which it
> was not menat to be at all. I apologize to the reporter if he feels this
> way.
:)
> Sven Luther wrote:
> > it was Frans who suggested this, and doing ping-pong of bug
Processing commands for [EMAIL PROTECTED]:
> severity 388159 wishlist
Bug#388159: installation-reports: Please depend on lspci
Severity set to `wishlist' from `wishlist'
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
I feel my previous email could be taken as harsh on my side, which it
was not menat to be at all. I apologize to the reporter if he feels this
way.
Sven Luther wrote:
> it was Frans who suggested this, and doing ping-pong of bug reporters
> is hardly user friendly
I am not doing ping pong of anyt
Processing commands for [EMAIL PROTECTED]:
> severity 388159 wishlist
Bug#388159: installation-reports: Please depend on lspci
Severity set to `wishlist' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
severity 388159 wishlist
stop
On Tue, Sep 19, 2006, Debian Bug Tracking System wrote:
> > severity wishlist
> Unknown command or malformed arguments to command.
--
Loïc Minier <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
On Tue, Sep 19, 2006 at 11:25:21AM +0200, Amaya wrote:
> reassign 388159 installation-reports
> retitle 388159 installation-reports: Please depend on lspci
> severity wishlist
> thanks
Hi Amaya, ...
> Rick Thomas wrote:
> > Package: base
>
> Please do not file bugs against the base pseudo-packa
Processing commands for [EMAIL PROTECTED]:
> reassign 388159 installation-reports
Bug#388159: missing lspci on a fresh install
Bug reassigned from package `base' to `installation-reports'.
> retitle 388159 installation-reports: Please depend on lspci
Bug#388159: missing lspci on
reassign 388159 installation-reports
retitle 388159 installation-reports: Please depend on lspci
severity wishlist
thanks
Rick Thomas wrote:
> Package: base
Please do not file bugs against the base pseudo-package.
It is there just as a catch-all-I-dunno-where-to-file-this-report for
users that c
On Mon, Sep 18, 2006 at 10:57:24PM +0200, Frans Pop wrote:
> On Monday 18 September 2006 21:49, Rick Thomas wrote:
> > On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
> > > Frans Pop a écrit :
> > >> The d-i team is not responsible for what is part of the base
> > >> system and what is not.
> >
>
On Mon, Sep 18, 2006 at 11:24:17PM +0200, De Leeuw Guy wrote:
> Rick Thomas a écrit :
> > On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
> >> Frans Pop a écrit :
> >>>
> >>> The d-i team is not responsible for what is part of the base system and
> >>> what is not.
> >
> > Then who is? Where sho
Package: base
On Sep 18, 2006, at 4:57 PM, Frans Pop wrote:
On Monday 18 September 2006 21:49, Rick Thomas wrote:
On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
Frans Pop a écrit :
The d-i team is not responsible for what is part of the base
system and what is not.
Then who is? Where s
On Monday 18 September 2006 23:26, De Leeuw Guy wrote:
> I not consider that is a bug, but an essential functionality that are
> missing just after a bad reboot.
No it is not as the installer has already saved the info
in /var/log/installer/.
And even after a bad reboot it is hardly "essential" (
Hello Frans
> Correct place to file a bug report would be the pseudo package "base", but
> I strongly suggest you do not file a bug for this.
>
I not consider that is a bug, but an essential functionality that are
missing just after a bad reboot.
Regards
Guy
--
To UNSUBSCRIBE, email to [EM
Hello Rick, Frans
Rick Thomas a écrit :
>
> On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
>
>> Frans Pop a écrit :
>>>
>>> The d-i team is not responsible for what is part of the base system and
>>> what is not.
>
> Then who is? Where should I send a bug report?
>
Yes, I'am surprising also ab
On Monday 18 September 2006 21:49, Rick Thomas wrote:
> On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
> > Frans Pop a écrit :
> >> The d-i team is not responsible for what is part of the base
> >> system and what is not.
>
> Then who is? Where should I send a bug report?
What is your rational
On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:
Frans Pop a écrit :
The d-i team is not responsible for what is part of the base
system and
what is not.
Then who is? Where should I send a bug report?
Thanks,
I follow the procedure from this link :
http://www.mail-archive.com/debian-boot@lists.debian.org/msg77135.html
and work now.
Guy
Frans Pop a écrit :
> On Monday 18 September 2006 15:39, De Leeuw Guy wrote:
>
>> Frans Pop a écrit :
>>
>>> Known issue. Upgrade to udev from unstable.
On Monday 18 September 2006 15:39, De Leeuw Guy wrote:
> Frans Pop a écrit :
> > Known issue. Upgrade to udev from unstable.
>
> How can I do that without network access ?
Use another machine to download the package and a USB stick to move it to
your machine the install using 'dpkg -i'?
> > Then
On Monday 18 September 2006 14:13, Frans Pop wrote:
> On Monday 18 September 2006 14:56, De Leeuw Guy wrote:
> > I just finish a new net-install with the daily builds 20060918 of
> > testing. I have a strange bug with the network after the first reboot.
> > lo become eth0
> > eth0 become eth1_temp
Frans Pop a écrit :
> Known issue. Upgrade to udev from unstable.
>
How can I do that without network access ?
> Then install pci-utils...
>
Ok, but why this tool are not on the base-system ?
> Cheers,
> FJP
>
Thanks for your respons
Guy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
On Monday 18 September 2006 14:56, De Leeuw Guy wrote:
> I just finish a new net-install with the daily builds 20060918 of
> testing. I have a strange bug with the network after the first reboot.
> lo become eth0
> eth0 become eth1_temp
> and I cannot access the network.
Known issue. Upgrade to ud
Hello all
I just finish a new net-install with the daily builds 20060918 of testing.
I have a strange bug with the network after the first reboot.
lo become eth0
eth0 become eth1_temp
and I cannot access the network.
I try to start lspci to identify my network card but this tools missing.
Regards
24 matches
Mail list logo
