Re: [Test-Announce] livecd-tools testing request

2012-02-27 Thread Samuel Sieb 

Adam Williamson wrote:

Also the bug where, if you write a DVD ISO to USB stick with l-i-t-d,
only the anaconda stuff gets written, not the packages - so the stick is
effectively just a boot.iso, you need another source of packages. That
one I didn't file yet, but it should be fixed.

That's interesting.  I guess I've always avoided it by copying the .iso image to 
the USB drive as well so it just finds it there.  That's also handy because then 
you have the full .iso image to share with others or create new USB installers. 
 I wonder if this new change will now take up twice the space if I use this method.

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Kamil Paral 
> > I copied a squashfs.img to the the tftpd directory along with
> > vmlinuz
> > and initrd.img.
> > Pxeboot fails claiming it can't handle root=squashfs.img.
> > 
> > "V'ger does not know."
> > 
> > 
> > prompt 1
> > default linux
> > timeout 100
> > 
> > label linux
> > kernel vmlinuz
> > append initrd=initrd.img ramdisk_size=9216 root=squashfs.img
> > askmethod
> 
> I'm not sure, but from the bug report it reads like it actually can't
> pull the root image over all protocols ATM. I might be
> misunderstanding,
> though.


That is correct. Currently supported are http and ftp AFAIK. nfs support will 
come in future.

Also the 'root' argument should not be required in the future, hopefully.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #283: USB 3.0

2012-02-27 Thread Fedora QA 
#283: USB 3.0
---+---
  Reporter:  ccui  |  Owner:  hongqing
  Type:  task  | Status:  assigned
  Priority:  major |  Milestone:  Fedora 17
 Component:  Test Day  |Version:
Resolution:|   Keywords:  USB 3.0
Blocked By:|   Blocking:
---+---

Comment (by hongqing):

 I will work together with the kernel team to create test cases later.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #283: USB 3.0

2012-02-27 Thread Fedora QA 
#283: USB 3.0
---+---
  Reporter:  ccui  |  Owner:  hongqing
  Type:  task  | Status:  assigned
  Priority:  major |  Milestone:  Fedora 17
 Component:  Test Day  |Version:
Resolution:|   Keywords:  USB 3.0
Blocked By:|   Blocking:
---+---
Changes (by hongqing):

 * owner:   => hongqing
 * status:  new => assigned


-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #282: Test Day proposal - ABRT & deduplication service

2012-02-27 Thread Fedora QA 
#282: Test Day proposal - ABRT & deduplication service
---+---
  Reporter:  rmarko|  Owner:
  Type:  task  | Status:  new
  Priority:  major |  Milestone:  Fedora 17
 Component:  Test Day  |Version:
Resolution:|   Keywords:
Blocked By:|   Blocking:
---+---
Changes (by mnowak):

 * cc: mnowak (added)


-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Adam Williamson 
On Mon, 2012-02-27 at 21:23 -0800, Chuck Forsberg WA7KGX N2469R wrote:
> On 02/27/2012 04:40 PM, Adam Williamson wrote:
> > On Mon, 2012-02-27 at 14:16 -0800, Chuck Forsberg WA7KGX N2469R wrote:
> >
> >> I have looked at the document and have no idea of what to include in a 
> >> root=
> >> phrase.  Apparently no one else does or they would mention a universal 
> >> root=
> >> that just works as well as Fedora 16 pxeboot did without a root= phrase.
> > I'm not sure why you didn't look at the *other* reply to your question,
> > which directed you to the appropriate bug report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=785815
> >
> > Where you find the appropriate parameter - it seems to be approximately
> > "root=live:(path_to_squashfs.img_from_build_to_install)"
> >
> >> Between a broken pxeboot and an anaconda that flips out when it sees the
> >> wrong
> >> version of Linux on the hard drive, I would think folks would wish to get a
> >> robust install experience before proclaiming a public beta.
> > The beta doesn't go out for another month or so. This is the alpha.
> I copied a squashfs.img to the the tftpd directory along with vmlinuz 
> and initrd.img.
> Pxeboot fails claiming it can't handle root=squashfs.img.
> 
> "V'ger does not know."
> 
> 
> prompt 1
> default linux
> timeout 100
> 
> label linux
> kernel vmlinuz
> append initrd=initrd.img ramdisk_size=9216 root=squashfs.img askmethod

I'm not sure, but from the bug report it reads like it actually can't
pull the root image over all protocols ATM. I might be misunderstanding,
though.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Chuck Forsberg WA7KGX N2469R 

On 02/27/2012 04:40 PM, Adam Williamson wrote:

On Mon, 2012-02-27 at 14:16 -0800, Chuck Forsberg WA7KGX N2469R wrote:


I have looked at the document and have no idea of what to include in a root=
phrase.  Apparently no one else does or they would mention a universal root=
that just works as well as Fedora 16 pxeboot did without a root= phrase.

I'm not sure why you didn't look at the *other* reply to your question,
which directed you to the appropriate bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=785815

Where you find the appropriate parameter - it seems to be approximately
"root=live:(path_to_squashfs.img_from_build_to_install)"


Between a broken pxeboot and an anaconda that flips out when it sees the
wrong
version of Linux on the hard drive, I would think folks would wish to get a
robust install experience before proclaiming a public beta.

The beta doesn't go out for another month or so. This is the alpha.
I copied a squashfs.img to the the tftpd directory along with vmlinuz 
and initrd.img.

Pxeboot fails claiming it can't handle root=squashfs.img.

"V'ger does not know."


prompt 1
default linux
timeout 100

label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=9216 root=squashfs.img askmethod

--
Chuck Forsberg WA7KGX N2469R c...@omen.com   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
  Omen Technology Inc  "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Test-Announce] livecd-tools testing request

2012-02-27 Thread Adam Williamson 
Hey, folks. There's a new livecd-tools build which needs testing:

https://admin.fedoraproject.org/updates/FEDORA-2012-2313/livecd-tools-17.6-1.fc17

It should fix two bugs I came across in Alpha testing:

https://bugzilla.redhat.com/show_bug.cgi?id=796419 - "F17 Alpha RC4 DVD
written to USB with livecd-iso-to-disk --efi does not boot"

Also the bug where, if you write a DVD ISO to USB stick with l-i-t-d,
only the anaconda stuff gets written, not the packages - so the stick is
effectively just a boot.iso, you need another source of packages. That
one I didn't file yet, but it should be fixed.

bcl says it's a fairly big change, so he wants it to get some testing
before applying the change to f15 and f16. please test whatever you
usually use livecd-iso-to-disk for and make sure it didn't break
anything. Ideally we should re-run all the USB validation tests that use
anything from livecd-tools - the 'USB Stick' section on the installation
matrix - and make sure nothing got worse, at least. If it all goes well,
file positive karma. thanks! it'd be great to get this approved and
f15/f16 builds done ASAP so as to help people get Alpha written.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #284: Create advisory installation validation test cases for VirtualBox

2012-02-27 Thread Fedora QA 
#284: Create advisory installation validation test cases for VirtualBox
---+-
  Reporter:  adamwill  |  Owner:
  Type:  task  | Status:  new
  Priority:  minor |  Milestone:
 Component:  Wiki  |Version:
Resolution:|   Keywords:
Blocked By:|   Blocking:
---+-
Changes (by robatino):

 * cc: robatino@… (added)


-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Fedora QA] #284: Create advisory installation validation test cases for VirtualBox

2012-02-27 Thread Fedora QA 
#284: Create advisory installation validation test cases for VirtualBox
--+--
 Reporter:  adamwill  |   Owner:
 Type:  task  |  Status:  new
 Priority:  minor |   Milestone:
Component:  Wiki  | Version:
 Keywords:|  Blocked By:
 Blocking:|
--+--
 Although kernel team (and the rest of the development team) specifically
 don't want to commit to supporting VirtualBox, the practical fact is that
 a lot of people like to run Fedora in VirtualBox, and we don't at present
 have formal testing in place to find out if it's actually working during
 release validation.

 In practice, we usually find out about any bugs via people trying it and
 then posting their results to test@ or the forums, but this is pretty
 rough and ready and it's easy to lose the information. If we add formal
 VBox testing to the release validation process we'll probably find out
 about VBox fails sooner and do a better job of tracking them for possible
 fixes or at least documentation at release time.

 So, ideally, we should write test cases for deploying Fedora as a VBox
 guest (and possibly using it as a VBox host), and add these to the
 installation validation matrix as 'advisory' tests (tests not associated
 with Alpha, Beta or Final release phases, and without a corresponding
 release criterion).

 Dan Mashal, who I hope I've added to CC, is interested in this topic and
 may choose to be an awesome rock star and contribute the test cases :)

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: missing url...

2012-02-27 Thread John5342 
On Tue, Feb 28, 2012 at 01:04, Rob Healey  wrote:
> Greetings:
>
> In the most recent past, I have used:
> http://download.fedora.redhat.com/pub/fedora/linux/development/17/x86_64/os
> as my baseurl in /etc/yum.repos.d/fedora.repo
>
> Today, I can't  find the server...
>
> Did the url disappear or is it just temporarily down???

This was already announced on the announce mailing list:
http://lists.fedoraproject.org/pipermail/announce/2012-February/003040.html

-- 
There are 10 kinds of people in the world: Those who understand binary
and those who don't...
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: missing url...

2012-02-27 Thread Kevin Fenzi 
On Mon, 27 Feb 2012 17:04:02 -0800
Rob Healey  wrote:

> Greetings:
> 
> In the most recent past, I have used:
> http://download.fedora.redhat.com/pub/fedora/linux/development/17/x86_64/osas
> my baseurl in /etc/yum.repos.d/fedora.repo
> 
> Today, I can't  find the server...
> 
> Did the url disappear or is it just temporarily down???
> 

http://lists.fedoraproject.org/pipermail/announce/2012-February/003040.html

You must have a really old fedora.repo file. ;) 

kevin


signature.asc
Description: PGP signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

missing url...

2012-02-27 Thread Rob Healey 
Greetings:

In the most recent past, I have used:
http://download.fedora.redhat.com/pub/fedora/linux/development/17/x86_64/osas
my baseurl in /etc/yum.repos.d/fedora.repo

Today, I can't  find the server...

Did the url disappear or is it just temporarily down???

-- 
Sincerely yours,
Rob G. Healey
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Adam Williamson 
On Mon, 2012-02-27 at 14:16 -0800, Chuck Forsberg WA7KGX N2469R wrote:

> I have looked at the document and have no idea of what to include in a root=
> phrase.  Apparently no one else does or they would mention a universal root=
> that just works as well as Fedora 16 pxeboot did without a root= phrase.

I'm not sure why you didn't look at the *other* reply to your question,
which directed you to the appropriate bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=785815

Where you find the appropriate parameter - it seems to be approximately
"root=live:(path_to_squashfs.img_from_build_to_install)"

> Between a broken pxeboot and an anaconda that flips out when it sees the 
> wrong
> version of Linux on the hard drive, I would think folks would wish to get a
> robust install experience before proclaiming a public beta.

The beta doesn't go out for another month or so. This is the alpha.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Chuck Forsberg WA7KGX N2469R 

On 02/27/2012 11:04 AM, Pete Travis wrote:



On Feb 26, 2012 11:00 AM, "Chuck Forsberg WA7KGX N2469R" > wrote:

>
> I have been using the following for the "default" file in tftpd.
> It has worked until Fedora 17, which needs a root= phrase.
> However I can find no information on what that phrase should be.
> What should it be changed to?
>
> prompt 1
> default linux
> timeout 100
>
> label linux
> kernel vmlinuz
> append initrd=initrd.img ramdisk_size=9216 askmethod noselinux
>
> --
> Chuck Forsberg WA7KGX N2469R c...@omen.com  
www.omen.com 

> Developer of Industrial ZMODEM(Tm) for Embedded Applications
>  Omen Technology Inc  "The High Reliability Software"
> 10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430
>
> --
> test mailing list
> test@lists.fedoraproject.org 
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test

Does 
http://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt help?


--pete




I have looked at the document and have no idea of what to include in a root=
phrase.  Apparently no one else does or they would mention a universal root=
that just works as well as Fedora 16 pxeboot did without a root= phrase.

Between a broken pxeboot and an anaconda that flips out when it sees the 
wrong

version of Linux on the hard drive, I would think folks would wish to get a
robust install experience before proclaiming a public beta.

--
Chuck Forsberg WA7KGX N2469R c...@omen.com   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
  Omen Technology Inc  "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Pete Travis 
On Feb 26, 2012 11:00 AM, "Chuck Forsberg WA7KGX N2469R" 
wrote:
>
> I have been using the following for the "default" file in tftpd.
> It has worked until Fedora 17, which needs a root= phrase.
> However I can find no information on what that phrase should be.
> What should it be changed to?
>
> prompt 1
> default linux
> timeout 100
>
> label linux
> kernel vmlinuz
> append initrd=initrd.img ramdisk_size=9216 askmethod noselinux
>
> --
> Chuck Forsberg WA7KGX N2469R c...@omen.com   www.omen.com
> Developer of Industrial ZMODEM(Tm) for Embedded Applications
>  Omen Technology Inc  "The High Reliability Software"
> 10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test

Does http://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txthelp?

--pete
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: New testcase for installation without selinux

2012-02-27 Thread Petr Schindler 
I've removed the criterion from [1].

[1] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria 

On Mon, 2012-02-20 at 17:20 +0100, Petr Schindler wrote:
> It looks like better idea to drop criterion as this option is
> obsolete.
> So, I propose to remove criterion 
> 
> "The installed system must run normally if the user chooses to install
> without SELinux"
> 
> from final criteria [1]. If someone wants to switch the selinux off it
> can be easily done from the installed system. Some objections??
> 
> [1] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria 

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: New criterion for updates.img using

2012-02-27 Thread Petr Schindler 
I've added new criterion to beta release criteria. Tha alpha criterion
has already been there (I proposed it in another thread). You can find
changes here [1].

[1] https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria

On Mon, 2012-02-20 at 17:51 +0100, Petr Schindler wrote:
> So I propose alpha criterion:
> 
> "The installer must be able to use an [[Anaconda/Updates|installer
> update image]] retrieved from HTTP url"
> 
> And beta criterion:
> 
> "The installer must be able to use an [[Anaconda/Updates|installer
> update image]] retrieved from removable media, remote installation
> source and HTTP url"
> 
> I think, that this should be beta for testing purposes. It will be
> easier to test patches, so it would be better if it worked earlier
> than
> later. But that's only my opinion. If you have something against it,
> please, reply to this thread.
> 
> 

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F-17 Branched report: 20120227 changes

2012-02-27 Thread Branched Report 
Compose started at Mon Feb 27 08:15:07 UTC 2012

Broken deps for x86_64
--
[HippoDraw]
HippoDraw-devel-1.21.3-2.fc17.i686 requires python-numarray
HippoDraw-devel-1.21.3-2.fc17.x86_64 requires python-numarray
HippoDraw-python-1.21.3-2.fc17.x86_64 requires python-numarray
[Pound]
Pound-2.6-2.fc17.x86_64 requires libtcmalloc.so.0()(64bit)
[aeolus-conductor]
aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8
[aeolus-configserver]
aeolus-configserver-0.4.1-5.fc17.noarch requires ruby-nokogiri
[alexandria]
alexandria-0.6.8-2.fc17.1.noarch requires ruby(abi) = 0:1.8
[asterisk]
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires 
libSaEvt.so.3(OPENAIS_EVT_B.01.01)(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires libSaEvt.so.3()(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires 
libSaClm.so.3(OPENAIS_CLM_B.01.01)(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires libSaClm.so.3()(64bit)
[aunit]
aunit-2010-3.fc16.i686 requires libgnat-4.6.so
aunit-2010-3.fc16.x86_64 requires libgnat-4.6.so()(64bit)
[banshee]
banshee-meego-2.2.1-3.fc17.x86_64 requires mutter-meego
[catfish]
catfish-engines-0.3.2-4.fc17.1.noarch requires pinot
[comoonics-cdsl-py]
comoonics-cdsl-py-0.2-19.noarch requires comoonics-base-py
[comoonics-cluster-py]
comoonics-cluster-py-0.1-25.noarch requires comoonics-base-py
[contextkit]
contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1
contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit)
[couchdb]
couchdb-1.0.3-2.fc16.x86_64 requires libicuuc.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicui18n.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicudata.so.46()(64bit)
[curry]
curry-0.9.11-7.fc12.x86_64 requires libgmp.so.3()(64bit)
[dh-make]
dh-make-0.55-4.fc17.noarch requires debhelper
[dlm]
dlm-3.99.0-5.fc17.x86_64 requires libcfg.so.4(COROSYNC_CFG_0.82)(64bit)
dlm-3.99.0-5.fc17.x86_64 requires libcfg.so.4()(64bit)
[elice]
elice-0.323-6.fc17.x86_64 requires ruby(abi) = 0:1.8
[eruby]
eruby-1.0.5-17.fc17.x86_64 requires libruby.so.1.8()(64bit)
eruby-libs-1.0.5-17.fc17.i686 requires ruby(abi) = 0:1.8
eruby-libs-1.0.5-17.fc17.i686 requires libruby.so.1.8
eruby-libs-1.0.5-17.fc17.x86_64 requires ruby(abi) = 0:1.8
eruby-libs-1.0.5-17.fc17.x86_64 requires libruby.so.1.8()(64bit)
[fantasdic]
fantasdic-1.0-0.9.beta7.fc17.noarch requires ruby(gettext-package)
[gcc-python-plugin]
gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 
0:4.7.0-0.10.fc17
gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17
gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 
0:4.7.0-0.10.fc17
gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17
[gdal]
gdal-ruby-1.7.3-12.fc17.x86_64 requires libruby.so.1.8()(64bit)
[gearmand]
gearmand-0.23-2.fc17.x86_64 requires libtcmalloc.so.0()(64bit)
gearmand-0.23-2.fc17.x86_64 requires 
libboost_program_options-mt.so.1.47.0()(64bit)
[genius]
genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
gnome-genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
[geos]
geos-ruby-3.3.2-1.fc17.x86_64 requires libruby.so.1.8()(64bit)
[gnatcoll]
gnatcoll-2011-6.fc17.i686 requires libgnat-4.6.so
gnatcoll-2011-6.fc17.i686 requires libgnarl-4.6.so
gnatcoll-2011-6.fc17.x86_64 requires libgnat-4.6.so()(64bit)
gnatcoll-2011-6.fc17.x86_64 requires libgnarl-4.6.so()(64bit)
[gnome-phone-manager]
gnome-phone-manager-0.66-9.fc17.x86_64 requires 
libgnome-bluetooth.so.9()(64bit)
[gnome-user-share]
gnome-user-share-3.0.1-3.fc17.x86_64 requires 
libgnome-bluetooth.so.9()(64bit)
[gnucash]
gnucash-2.4.8-1.fc17.x86_64 requires libgoffice-0.8.so.8()(64bit)
[gorm]
gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit)
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires 
libgnustep-gui.so.0.20()(64bit)
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires 
libgnustep-base.so.1.23()(64bit)
[gphpedit]
gphpedit-0.9.95-0.2.20090209snap.fc15.x86_64 requires 
libgtkhtml-2.so.0()(64bit)
[gpsdrive]
gpsdrive-2.11-10.fc17.x86_64 requires libmapnik.so.0.7()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_thread-mt.so.1.47.0()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_system-mt.so.1.47.0()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_filesystem-mt.so.1.47.0()(64bit)
[grads]
grads-2.0.1-1.fc17.x86

Re: root= for Fedora 17 pxeboot?

2012-02-27 Thread Kamil Paral 
> I have been using the following for the "default" file in tftpd.
> It has worked until Fedora 17, which needs a root= phrase.
> However I can find no information on what that phrase should be.
> What should it be changed to?
> 
> prompt 1
> default linux
> timeout 100
> 
> label linux
> kernel vmlinuz
> append initrd=initrd.img ramdisk_size=9216 askmethod noselinux

https://bugzilla.redhat.com/show_bug.cgi?id=785815
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test