Bug#693956: Acknowledgement (Wheezy d-i fails to set german keymap when set on command line)

2012-11-22 Thread Bernhard Schmidt

It looks like I need to set both debian-installer/keymap=de and keymap=de

keymap=de prevents getting the keyboard layout selection displayed, but 
does not seem to do anything regarding the actual layout being set


debian-installer/keymap=de sets the keyboard layout to German but the 
selection still gets displayed


Both settings together have the desired effect.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50addb65.2030...@birkenwald.de



Re: Proposal to add patches to netcfg (#682737)

2012-11-22 Thread Philipp Kern
On Tue, Nov 20, 2012 at 03:12:33PM +0100, Michael Biebl wrote:
> This is a bit weird. The UUID is only required really on Linux
> plattforms, since NM is Linux-only. I would expect the NM specific code
> is ifdeffed on those plattforms so a libuuid dependency is not needed.
> Is this not the case?

It is now. I didn't realize that there is no network-manager at all on
non-Linux.

Also the changes have been uploaded now.

Kind regards
Philipp Kern


signature.asc
Description: Digital signature


Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7

2012-11-22 Thread Brian Potkin
On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote:

> Thanks for your reply -- for some reason it didn't arrive here as email,
> but I found it tonight while looking in the debian-boot list archives.

Strange. mail.msen.com accepted the mail from my server.

> On Mon, 19 Nov 2012 11:00:49 +, Brian Potkin wrote:
>
> : : Did you get that advice from section 6.3.6.1? I'd agree it is
> less
> : helpful than intended.
>
> Yes, exactly.  The mention of black arts also makes me hesitant to interfere
> when the automatic process gets it wrong.  The GRUB ecosystem seems more
> complicated, the more I try to understand it, with the various scripts
> which probe and update and install, but aren't really discussed in the
> mainline grub documentation sources, such as they are.  Perhaps in section
> 6.3.6.2 where it says "See the grub manual for complete information."
> there could be some hyperlink[s].

I am not sure that would really help in general. In this case it would
not have because the bug lay with d-i and not any of the GRUB scripts.

> : : It's a pity you declined to install GRUB. At least you should
> have got a
> : bootable system from which to attempt to get the missing entry into the
> : GRUB menu.
>
> It's too bad the ISO doesn't provide a way to boot into the completed
> installation, without overwriting the disk's MBR.  I would be more
> confident to experiment with GRUB configurations and probing if I could
> see what it was trying to install before I commit to it.  I don't want
> to lose the ability to boot the existing Win7 system on my wife's computer.

It does. You decline the offer to install GRUB to /dev/sda by answering
'No' and specifying where GRUB should go.

> I see that the beta-4 version is available today.  I'll grab that, and try
> it out to see if it will work automatically.

It works for me.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121122141052.GA8215@desktop



Experience and problems in installing wheezy b-4

2012-11-22 Thread L V Gandhi
I downloaded kde version of wheezy b-4.
Problems are listed below.
1) I used netbootin and prepared USB stick from iso. Though it booted from
USB, it was looking for CD for further installation.
Hence I have to burn a CD.
2) While installing from CD, I tried to use wifi. But  wifi could not be
configured. Though same wifi works in kubuntu, mint and also previously in
b-3.
I think it needs more time to get connected. If there is some time
configuration to allow it to connect in stead of standard, it could have
saved the trouble.
3)Both in b-3 and b-4, i have downloaded KDE cd. But when I select desktop
in task during installation, it downloads and installs GNOME, not the KDE
in CD.
I hope Installer team will look into the above problems.
If I failed to notice something and above problems occurred, kindly let me
know to avoid above problems.
-- 
L V Gandhi


Re: Experience and problems in installing wheezy b-4

2012-11-22 Thread Julien Cristau
On Thu, Nov 22, 2012 at 22:25:39 +0530, L V Gandhi wrote:

> I downloaded kde version of wheezy b-4.
> Problems are listed below.
> 1) I used netbootin and prepared USB stick from iso. Though it booted from
> USB, it was looking for CD for further installation.
> Hence I have to burn a CD.

What's netbootin?  Copying the iso to a usb device should just work,
without any other preparation...

> 2) While installing from CD, I tried to use wifi. But  wifi could not be
> configured. Though same wifi works in kubuntu, mint and also previously in
> b-3.
> I think it needs more time to get connected. If there is some time
> configuration to allow it to connect in stead of standard, it could have
> saved the trouble.

Most likely it needs firmware.

> 3)Both in b-3 and b-4, i have downloaded KDE cd. But when I select desktop
> in task during installation, it downloads and installs GNOME, not the KDE
> in CD.
> I hope Installer team will look into the above problems.
> If I failed to notice something and above problems occurred, kindly let me
> know to avoid above problems.

Please provide the d-i log.  It's in /var/log/installer/
post-installation.

Cheers,
Julien


signature.asc
Description: Digital signature


Re: Experience and problems in installing wheezy b-4

2012-11-22 Thread Brian Potkin
On Thu 22 Nov 2012 at 22:25:39 +0530, L V Gandhi wrote:

> I downloaded kde version of wheezy b-4.

The URL you used was

   http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/ ?

But maybe amd64 instead of i386.

> Problems are listed below.
> 1) I used netbootin and prepared USB stick from iso. Though it booted from
> USB, it was looking for CD for further installation.

UNetbootin? Last time I used it it didn't even display a Debian splash
screen and some of the menus did not function. It did boot but I doubt
anyone (not me, anyway) is going to debug the operation of this software,
especially as the CD FAQ at

   http://www.debian.org/CD/

and the install manual describe a reliable method for writing an ISO on
a USB device. Is there any reason why you cannot use it?

I think d-i says it is detecting and mounting a CD-ROM. Somewhat
confusing if you have a USB stick. In expert mode there should be a
message which says CD-ROM autodetection has been successful.

> Hence I have to burn a CD.

Please see above.

> 2) While installing from CD, I tried to use wifi. But  wifi could not be
> configured. Though same wifi works in kubuntu, mint and also previously in
> b-3.

In what way could it not be configured? Firmware? WPA passphrase? A
problem with the access point?

> I think it needs more time to get connected. If there is some time
> configuration to allow it to connect in stead of standard, it could have
> saved the trouble.
> 3)Both in b-3 and b-4, i have downloaded KDE cd. But when I select desktop
> in task during installation, it downloads and installs GNOME, not the KDE
> in CD.

The CD contains everything you need to get KDE. Try it without any network
connection. My beta-3 KDE ISO gave me KDE with the network operative.



> I hope Installer team will look into the above problems.
> If I failed to notice something and above problems occurred, kindly let me
> know to avoid above problems.
> -- 
> L V Gandhi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121122190934.GN6794@desktop



Re: Debian Installer 7.0 Beta4 release

2012-11-22 Thread Holger Wansing
Hi,

Cyril Brulebois  wrote:
> Known issues in this release
> 
> 
>  * Network issues when installing a desktop over a wireless connection
>(#682608). A bug fix is expected for the next installer release.
> 
> See the errata[2] for details and a full list of known issues.

Maybe it would be worse to add the following to the errata:
if /boot is on a btrfs filesystem (for example when creating only one
partition formatted as btrfs for / ), lilo fails to install, and
grub is relative slow on reading its configuration from the btrfs
filesystem, which leads to a longer delay until the grub menu appears
(see https://lists.debian.org/debian-boot/2012/11/msg00084.html ).


Holger

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121122201139.c28828b2.li...@wansing-online.de



Re: d-i manual (Re: building and testing d-i with jenkins)

2012-11-22 Thread Holger Levsen
Hi,

On Samstag, 17. November 2012, Holger Wansing wrote:
> As documented in manual/doc/translations_po.txt:
>   Use the following commands:
> 1. ./scripts/merge_xml en
> 2. ./scripts/update_pot
> 3. ./scripts/update_po 
> 4. ./scripts/revert_pot
> 5. ./scripts/create_xml 

I've created these jobs now, 
see http://jenkins.debian.net/view/d-i_manual/

Those have quite a lot more failures and warnings...

I'm not sure whether I should ignore these warnings: "Warning: no PO file 
found for ..." - If I did that,
http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed_console/?
would show a lot less warnings, but still some. 

And the status of the actual translations is tracked elsewhere already, so I
believe I should do this. What do you think?


cheers,
Holger


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201211222031.41581.hol...@layer-acht.org



Re: d-i manual (Re: building and testing d-i with jenkins)

2012-11-22 Thread Holger Wansing
Hello Holger,

Holger Levsen  wrote:
> Those have quite a lot more failures and warnings...
> 
> I'm not sure whether I should ignore these warnings: "Warning: no PO file 
> found for ..." - If I did that,
> http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed_console/?
> would show a lot less warnings, but still some. 

At that url I see only warnings like "Warning: no PO file found for ...", no 
others.

> And the status of the actual translations is tracked elsewhere already, so I
> believe I should do this. What do you think?

We could change the workflow for the po based translations, so that all po files
are existing, even if the are completely untranslated.

Christian, what do you think?

If we don't change the workflow, ignoring that warnings would be the only way 
to go IMHO.
Would it be possible, to ignore ONLY that warnings with THAT TEXT, but no 
others? 


Holger W.

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121122205637.a8289b89.li...@wansing-online.de



Bug#694002: installation-report: wheezy beta4 success on lenovo thinkpad

2012-11-22 Thread Simon Josefsson
Package: installation-reports
Version: 2.47
Severity: normal

tl;dr: Success.

The only problem during installation was that it said
"ftp.se.debian.org" didn't have the requested distribution, so I
selected "cdn.debian.net" instead and that worked.  Presumably, this
problem is because wheezy isn't released yet.

-- Package-specific info:

Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso
Date: 2012 November 22

Machine: Lenovo Thinkpad X201
Partitions: See below.


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20121114"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux latte 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor
DRAM Controller [8086:0044] (rev 02)
lspci -knn: Subsystem: Lenovo Device [17aa:2193]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation
Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
lspci -knn: Subsystem: Lenovo Device [17aa:215a]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 5
Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:215f]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 5
Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2162]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation
82577LM Gigabit Network Connection [8086:10ea] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2153]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5
Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c]
(rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2163]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400
Series Chipset High Definition Audio [8086:3b56] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:215e]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400
Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 5 Series/3400
Series Chipset PCI Express Root Port 4 [8086:3b48] (rev 06)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400
Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 5
Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34]
(rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2163]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile
PCI Bridge [8086:2448] (rev a6)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series
Chipset LPC Interface Controller [8086:3b07] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2166]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 5
Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev
06)
lspci -knn: Subsystem: Lenovo Device [17aa:2168]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series
Chipset SMBus Controller [8086:3b30] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2167]
lspci -knn: 00:1f.6 Signal processing controller [1180]: Intel
Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32]
(rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:2190]
lspci -knn: 02:00.0 Network controller [0280]: Intel Corporation
Centrino Ultimate-N 6300 [

Re: Debian Installer 7.0 Beta4 release

2012-11-22 Thread Cyril Brulebois
Hi,

Holger Wansing  (22/11/2012):
> Maybe it would be worse to add the following to the errata:
> if /boot is on a btrfs filesystem (for example when creating only one
> partition formatted as btrfs for / ), lilo fails to install, and
> grub is relative slow on reading its configuration from the btrfs
> filesystem, which leads to a longer delay until the grub menu appears
> (see https://lists.debian.org/debian-boot/2012/11/msg00084.html ).

not sure it's worth it. How common is people wanting to install lilo,
let alone together with btrfs?

But if somebody wants to get that added to webwml's cvs, feel free.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: d-i manual (Re: building and testing d-i with jenkins)

2012-11-22 Thread Christian PERRIER
Quoting Holger Wansing (li...@wansing-online.de):

> We could change the workflow for the po based translations, so that all po 
> files
> are existing, even if the are completely untranslated.
> 
> Christian, what do you think?

That could help having better stats, as a side effect, so I would be
in favor of this.





signature.asc
Description: Digital signature


Bug#692118: marked as done ([d-i beta3] installation report: installing from i386-CD1 without a mirror results in no X)

2012-11-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Nov 2012 22:22:39 +0100
with message-id <2012112239.3f00fa1f.li...@wansing-online.de>
and subject line Bug#692118: [d-i beta3] installation report: installing from 
i386-CD1 without a mirror results in no X
has caused the Debian Bug report #692118,
regarding [d-i beta3] installation report: installing from i386-CD1 without a 
mirror results in no X
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
692118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: booting virtual machine from CD
http://cdimage.debian.org/cdimage/wheezy_di_beta3/i386/iso-cd/debian-wheezy-DI-b3-i386-CD-1.iso

Date: 01. Nov 2012

Machine: Virtualbox VM
Partitions: guided partitioning, using the whole disk, all files in one 
partition


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

A known problem coming up once again:
Offline-installation itself (without a mirror!) went fine.
Selected tasks during installation: Desktop environment + Standard system.
But the result is an console-only system.
No X!
Installation should have resulted in a GNOME system.

Holger

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--- End Message ---
--- Begin Message ---
I tried this with a beta4 image
http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-CD-1.iso
and it works fine now!
I got a working GNOME from the CD1, without a network connection.

So closing this bug.

Thanks
Holger

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =--- End Message ---


Re: Experience and problems in installing wheezy b-4

2012-11-22 Thread L V Gandhi
On Thu, Nov 22, 2012 at 11:05 PM, Julien Cristau wrote:

> On Thu, Nov 22, 2012 at 22:25:39 +0530, L V Gandhi wrote:
>
> > I downloaded kde version of wheezy b-4.
> > Problems are listed below.
> > 1) I used netbootin and prepared USB stick from iso. Though it booted
> from
> > USB, it was looking for CD for further installation.
> > Hence I have to burn a CD.
>
> What's netbootin?  Copying the iso to a usb device should just work,
> without any other preparation...
>

I meant unetbootin, used for creating bootable flash using ISO. Any how cp
and sync has solved that problem.

>
> > 2) While installing from CD, I tried to use wifi. But  wifi could not be
> > configured. Though same wifi works in kubuntu, mint and also previously
> in
> > b-3.
> > I think it needs more time to get connected. If there is some time
> > configuration to allow it to connect in stead of standard, it could have
> > saved the trouble.
>
> Most likely it needs firmware.
>

I dont think it is firmware. When I took the laptop near router, it
connected easily. That means when away, it needs more time for connecting.

>
> > 3)Both in b-3 and b-4, i have downloaded KDE cd. But when I select
> desktop
> > in task during installation, it downloads and installs GNOME, not the KDE
> > in CD.
> > I hope Installer team will look into the above problems.
> > If I failed to notice something and above problems occurred, kindly let
> me
> > know to avoid above problems.
>
> Please provide the d-i log.  It's in /var/log/installer/
> post-installation.
>
> There is no specific d-i log in installer folder. There is a folder
cdebconf with two files in it named questions.dat and templates.dat and
sixmore files namely hardware-summary, lsb-release, partman, status, syslog
and Xorg.0.log.
Which one should I post?



-- 
L V Gandhi


Bug#694002: installation-report: wheezy beta4 success on lenovo thinkpad

2012-11-22 Thread Simon Paillard
Control: tag -1 unreproducible

Hi,

On Thu, Nov 22, 2012 at 09:13:06PM +0100, Simon Josefsson wrote:
> Package: installation-reports
> Version: 2.47
> Severity: normal
> 
> The only problem during installation was that it said
> "ftp.se.debian.org" didn't have the requested distribution,

Do you remember the exact error message ?

Grepping di_log from choose-mirror, it may be:
di_log(DI_LOG_LEVEL_WARNING, "broken mirror: invalid %s in Release file 
for %s", field, name);
di_log(DI_LOG_LEVEL_ERROR, "no default release specified");
di_log(DI_LOG_LEVEL_ERROR, "array overflow: more releases than allowed 
by MAXRELEASES");
di_log(DI_LOG_LEVEL_INFO, "mirror does not have any suite symlinks");
di_log(DI_LOG_LEVEL_WARNING, "mirror does not support the specified 
release (%s)", default_suite);
di_log(DI_LOG_LEVEL_ERROR, "array overflow: more releases than allowed 
by MAXRELEASES");
di_log(DI_LOG_LEVEL_DEBUG, "architecture not supported by selected 
mirror");
di_log(DI_LOG_LEVEL_WARNING, "broken mirror: invalid %s in Release file 
for %s", field, name);
di_log(DI_LOG_LEVEL_WARNING, "mirror does not support the specified 
release (%s)",

> so I selected "cdn.debian.net" instead and that worked.  Presumably, this
> problem is because wheezy isn't released yet.
> 
> Image version:
> http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso

With same ISO and same mirror (and the fact ftp.se.d.o DNS entry didn't change
between the initial report and this mail), I cannot reproduce this report.

-- 
Simon Paillard


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2012112353.ga...@glenfiddich.mraw.org



Processed: Re: Bug#694002: installation-report: wheezy beta4 success on lenovo thinkpad

2012-11-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 unreproducible
Bug #694002 [installation-reports] installation-report: wheezy beta4 success on 
lenovo thinkpad
Added tag(s) unreproducible.

-- 
694002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.b694002.135362889412184.transcr...@bugs.debian.org



Bug#685159: os-prober does not detect Fedora

2012-11-22 Thread Andreas Bombe
Package: os-prober
Version: 1.56
Followup-For: Bug #685159

The bug is caused by using GRUB's internal filesystems through FUSE
which doesn't support symlinks (at least not on ext4). This filesystem
is only used when the volume is not already mounted, therefore this bug
does not appear when the volume is previously mounted using a real
filesystem that properly supports symlinks.

The specific problem is in 90linux-distro, which checks for lib*/ld*.so*
in the target filesystem as a heuristic to recognize Linux root
filesystems. With broken symlinks this fails for distributions that
moved lib* to /usr and only left symlinks in place.

Attached patch fixes this by also checking for usr/lib*/ld*.so*.
Index: os-prober-1.56/os-probes/mounted/common/90linux-distro
===
--- os-prober-1.56.orig/os-probes/mounted/common/90linux-distro	2011-07-23 10:19:40.0 +0200
+++ os-prober-1.56/os-probes/mounted/common/90linux-distro	2012-11-23 02:15:50.800011728 +0100
@@ -12,8 +12,12 @@
 # fact that only some architectures have ld-linux.so, I can't see anything
 # better. Make sure this test has a high number so that more accurate tests
 # can come first.
+# Unless volumes to checked are already mounted, they will be mounted using
+# GRUB's own filesystems through FUSE. Since these ATM doesn't support
+# symlinks we need to also check in $dir/usr/lib* for distributions that
+# moved /lib* to /usr and only left symlinks behind.
 # TODO: look for ld-linux.so on arches that have it
-if ls "$dir"/lib*/ld*.so* >/dev/null 2>/dev/null; then
+if (ls "$dir"/lib*/ld*.so* || ls "$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then
 	if [ -e "$dir/etc/debian_version" ]; then
 		short="Debian"
 		long="$(printf "Debian GNU/Linux (%s)\n" "$(cat "$dir/etc/debian_version")")"


Processed: tagging 685159

2012-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 685159 + patch
Bug #685159 [os-prober] os-prober does not detect Fedora
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
685159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135363725132249.transcr...@bugs.debian.org