kernel headers

2013-01-12 Thread Lawrence Graves
Everyone is blaming the inability of vmware workstation to compile on 
vmware/ nvidia people, when theerror message received says it can't find 
where the C file is located to compile. That seems to be a kernel error 
not a vmware or nvidia error. Please look into this minor problem.

--
All things are workable but don't all things work. Prov. 3:5  6
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Frank Murphy
On Sat, 12 Jan 2013 04:57:49 -0700
Lawrence Graves lgrave...@gmail.com wrote:

 Everyone is blaming the inability of vmware workstation to compile
 on vmware/ nvidia people, when theerror message received says it
 can't find where the C file is located to compile. 

What c file?
can you cp the error to fpaste.com?

-- 
Regards,
Frank

Still trying to learn, both old and new tricks
--me .
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Frank Murphy

Anyone else having problems getting
their network cards to play ball this morning?

-- 
Regards,
Frank

Still trying to learn, both old and new tricks
--me .
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

kernel headers

2013-01-12 Thread Lawrence Graves
what the error message says is that it could not find the kernel headers 
for kernel 3.7.1-5. I know that they were installed. So where are the 
kernel header file if in fact it was installed.

--
All things are workable but don't all things work. Prov. 3:5  6
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Frank Murphy
On Sat, 12 Jan 2013 05:09:41 -0700
Lawrence Graves lgrave...@gmail.com wrote:

 what the error message says is that it could not find the kernel
 headers for kernel 3.7.1-5. I know that they were installed. So
 where are the kernel header file if in fact it was installed.

Can you not copy the whole error? camera?
Oherwise it's a game of charades.

Can you keep the reples in the current thread please,
your coming in as new threads.

-- 
Regards,
Frank

Still trying to learn, both old and new tricks
--me .
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Frank Murphy
On Sat, 12 Jan 2013 05:09:41 -0700
Lawrence Graves lgrave...@gmail.com wrote:

 what the error message says is that it could not find the kernel
 headers for kernel 3.7.1-5. I know that they were installed. So
 where are the kernel header file if in fact it was installed.

This is where the headers should go: 32bit
http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612780

64 bit:
http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612758

if you have those files,
then the kernel is most likely not your problem.


-- 
Regards,
Frank

Still trying to learn, both old and new tricks
--me .
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Gary Gatling
On Sat, Jan 12, 2013 at 7:16 AM, Frank Murphy frankl...@gmail.com wrote:

 On Sat, 12 Jan 2013 05:09:41 -0700
 Lawrence Graves lgrave...@gmail.com wrote:

  what the error message says is that it could not find the kernel
  headers for kernel 3.7.1-5. I know that they were installed. So
  where are the kernel header file if in fact it was installed.

 This is where the headers should go: 32bit
 http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612780

 64 bit:
 http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612758

 if you have those files,
 then the kernel is most likely not your problem.


I've not tried with the latest f18 kernel, but I think the kernel-devel rpm
package is required to compile third party kernel modules with shims and
whatnot.

http://forums.fedoraforum.org/showthread.php?t=149704

Maybe you need to install the correct kernel-devel rpm to match the kernel
rpm and that will fix the problems?

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

Re: kernel headers

2013-01-12 Thread Scott Robbins
On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote:
 what the error message says is that it could not find the kernel headers for
 kernel 3.7.1-5. I know that they were installed. So where are the kernel 
 header
 file if in fact it was installed.

Usually, if VMware can't find kernel-headers, you need the kernel-devel
package. 

The kernel-devel package number has to match the result of uname -r.  What
I frequently see on the forums is that someone updated, got a newer package
of kernel-devel, but hasn't rebooted, so there will be a version mismatch.  

Also, if running a PAE kernel, one has to specify kernel-PAE-devel.  (Which
doesn't seem relevant in your case). 


-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Xander: Isn't that what they called The Slayer? 
Willow: Buffy, ohh scary. 
Xander: Someone has to talk to her people. That name is striking 
fear in nobody's hearts. 
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20130112 changes

2013-01-12 Thread Fedora Rawhide Report
Compose started at Sat Jan 12 08:15:09 UTC 2013

Broken deps for x86_64
--
[bootconf]
bootconf-1.4-6.fc18.noarch requires grub
[clementine]
clementine-1.0.1-12.fc18.x86_64 requires libcdio.so.13(CDIO_13)(64bit)
clementine-1.0.1-12.fc18.x86_64 requires libcdio.so.13()(64bit)
[ebview]
ebview-0.3.6.2-7.fc18.x86_64 requires VLGothic-fonts
[ember]
ember-0.6.3-3.fc19.x86_64 requires libOgreMain.so.1.7.4()(64bit)
[epiphany-extensions]
epiphany-extensions-3.6.0-1.fc19.x86_64 requires epiphany(abi) = 0:3.6
[evolution-rss]
1:evolution-rss-0.3.92-3.fc19.x86_64 requires 
libevolution-utils.so()(64bit)
1:evolution-rss-0.3.92-3.fc19.x86_64 requires 
libemiscwidgets.so()(64bit)
1:evolution-rss-0.3.92-3.fc19.x86_64 requires libemail-utils.so()(64bit)
1:evolution-rss-0.3.92-3.fc19.x86_64 requires 
libedataserverui-3.0.so.5()(64bit)
1:evolution-rss-0.3.92-3.fc19.x86_64 requires 
libcamel-1.2.so.42()(64bit)
[freeipa]
freeipa-server-strict-3.1.0-1.fc19.x86_64 requires 389-ds-base = 0:1.3.0
[freewrl]
freewrl-1.22.13.1-3.fc18.i686 requires libGLEW.so.1.7
freewrl-1.22.13.1-3.fc18.x86_64 requires libGLEW.so.1.7()(64bit)
libEAI-1.22.13.1-3.fc18.i686 requires libGLEW.so.1.7
libEAI-1.22.13.1-3.fc18.x86_64 requires libGLEW.so.1.7()(64bit)
[gcc-python-plugin]
gcc-python2-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 
0:4.7.2-8.fc19
gcc-python2-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19
gcc-python3-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 
0:4.7.2-8.fc19
gcc-python3-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19
[gdb-heap]
gdb-heap-0.5-11.fc19.x86_64 requires glibc(x86-64) = 0:2.16.90
[gfal]
gfal-1.13.0-0.fc18.i686 requires libgsoap.so.2
gfal-1.13.0-0.fc18.x86_64 requires libgsoap.so.2()(64bit)
gfal-doc-1.13.0-0.fc18.x86_64 requires libgsoap.so.2()(64bit)
gfal-python-1.13.0-0.fc18.x86_64 requires libgsoap.so.2()(64bit)
[ghc-wai-extra]
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSzlib-conduit-0.4.0.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSzlib-bindings-0.1.0.1-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSzlib-0.5.3.3-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSwai-1.2.0.3-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSvoid-0.5.6-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSvault-0.2.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSunordered-containers-0.2.1.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSunix-2.5.1.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHStransformers-base-0.4.1-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHStransformers-0.3.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHStime-1.4-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHStext-0.11.2.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSsemigroups-0.8.3.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSresourcet-0.3.2.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSparsec-3.1.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSold-time-1.1.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSold-locale-1.0.0.4-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSnetwork-2.3.0.13-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSmtl-2.1.1-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSmonad-control-0.3.1.3-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSlifted-base-0.1.1-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSinteger-gmp-0.4.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHShttp-types-0.6.11-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHShashable-1.1.2.3-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSghc-prim-0.2.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSfilepath-1.3.0.0-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSfast-logger-0.0.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSdlist-0.5-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 
libHSdirectory-1.1.0.2-ghc7.4.1.so()(64bit)
ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires 

Re: test Digest, Vol 107, Issue 43

2013-01-12 Thread Lawrence Graves


On 01/12/2013 07:03 AM, test-requ...@lists.fedoraproject.org wrote:

Send test mailing list submissions to
test@lists.fedoraproject.org

To subscribe or unsubscribe via the World Wide Web, visit
https://admin.fedoraproject.org/mailman/listinfo/test
or, via email, send a message with subject or body 'help' to
test-requ...@lists.fedoraproject.org

You can reach the person managing the list at
test-ow...@lists.fedoraproject.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of test digest...


Today's Topics:

1. [Rawhide] dhclient seg. out this morning? (Frank Murphy)
2. kernel headers (Lawrence Graves)
3. Re: kernel headers (Frank Murphy)
4. Re: kernel headers (Frank Murphy)
5. Re: kernel headers (Gary Gatling)
6. Re: kernel headers (Scott Robbins)
7. rawhide report: 20130112 changes (Fedora Rawhide Report)

gphoto2://[usb:002,006]/DCIM/Camera/2012-10-29_06-25-13_137.jpg

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


--
All things are workable but don't all things work. Prov. 3:5  6
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Christopher A. Williams
On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote:
 On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote:
  what the error message says is that it could not find the kernel headers for
  kernel 3.7.1-5. I know that they were installed. So where are the kernel 
  header
  file if in fact it was installed.
 
 Usually, if VMware can't find kernel-headers, you need the kernel-devel
 package. 
 
 The kernel-devel package number has to match the result of uname -r.  What
 I frequently see on the forums is that someone updated, got a newer package
 of kernel-devel, but hasn't rebooted, so there will be a version mismatch.  
 
 Also, if running a PAE kernel, one has to specify kernel-PAE-devel.  (Which
 doesn't seem relevant in your case). 

Actually, in this case, the kernel-headers and kernel-devel packages are
installed. Further, this appears to only happen with the 3.7 series of
the kernel.

I know this because I was having the same problem and, because I need
VMware Workstation for my work (some things needed for my job require
Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I
can confirm that VMware Workstation 9.0.1 is working with kernel version
3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no
patches from VMware needed).

Now, I don't recall the exact error message with kernel 3.7 because I
reverted back to the 3.6 series (via yum distro-sync), but VMware
Workstation 9.0.1 clearly is having trouble finding the kernel headers
and other associated components with the 3.7 series of the kernel that
is in the updates-testing repository.

So, what that means is that something with respect to where the header
files are placed and located between these two series of kernels has
been changed to the point that applications like VMware Workstaion can
no longer find them. I would need to go back to the 3.7 series kernel to
get the exact error message. I may have it in an old VMware log file, so
I'll check that too next chance.

In my case, I'm running the 64-bit kernel, so there's no PAE stuff to
worry about.

I know that's not all of the information people are asking for, but
hopefully it does shed some additional light on the situation...

Cheers,

Chris

-- 
Christopher A. Williams chriswfed...@cawllc.com

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

Re: kernel headers

2013-01-12 Thread Matthew Miller
On Sat, Jan 12, 2013 at 04:57:49AM -0700, Lawrence Graves wrote:
 Everyone is blaming the inability of vmware workstation to compile
 on vmware/ nvidia people, when theerror message received says it
 can't find where the C file is located to compile. That seems to be
 a kernel error not a vmware or nvidia error. Please look into this
 minor problem.

Probably a file they are looking for changed. They'll need to update
their build tools to look in the right place.

The kernel makes a guarantee to not cause problems for userspace programs
with new versions. It makes no such guarantee for kernel modules. This is
one of the reasons the Linux kernel has been able to adapt and grow so well,
and also one of the reasons out-of-tree kernel modules (whether commercial
or open source) are problematic.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Matthew Miller
On Sat, Jan 12, 2013 at 07:56:40AM -0700, Christopher A. Williams wrote:
 On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote:
 VMware Workstation for my work (some things needed for my job require
 Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I

Any particular reason not to use KVM? Save you some headache.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel headers

2013-01-12 Thread Jóhann B. Guðmundsson

On 01/12/2013 02:56 PM, Christopher A. Williams wrote:

On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote:

On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote:


snip../snip


Actually, in this case, the kernel-headers and kernel-devel packages are
installed. Further, this appears to only happen with the 3.7 series of
the kernel.

I know this because I was having the same problem and, because I need
VMware Workstation for my work (some things needed for my job require
Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I
can confirm that VMware Workstation 9.0.1 is working with kernel version
3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no
patches from VMware needed).

Now, I don't recall the exact error message with kernel 3.7 because I
reverted back to the 3.6 series (via yum distro-sync), but VMware
Workstation 9.0.1 clearly is having trouble finding the kernel headers
and other associated components with the 3.7 series of the kernel that
is in the updates-testing repository.


Aren't you just experiencing that broken vmware scripts which cant find 
the relocated version.h in the 3.7 series kernels ?


And that's simply solved by running ln -s 
/usr/src/linux-3.7-X/include/generated/uapi/linux/version.h 
/usr/src/linux-3.7-X/include/linux/version.h


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

Fedora 18 updates-testing report

2013-01-12 Thread updates
The following Fedora 18 Security updates need testing:
 Age  URL
   3  
https://admin.fedoraproject.org/updates/FEDORA-2013-0437/proftpd-1.3.4b-4.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0125/drupal6-context-3.1-1.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0124/xorg-x11-apps-7.7-1.fc18
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-0170/drupal7-context-3.0-0.3.beta6.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0145/asterisk-11.1.2-1.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-0568/rubygem-actionpack-3.2.8-2.fc18,rubygem-activerecord-3.2.8-3.fc18,rubygem-activesupport-3.2.8-2.fc18
   0  https://admin.fedoraproject.org/updates/FEDORA-2013-0627/xen-4.2.1-3.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-0589/thunderbird-17.0.2-1.fc18
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-0182/kexec-tools-2.0.3-64.fc18
   7  https://admin.fedoraproject.org/updates/FEDORA-2013-0178/pl-6.0.2-5.fc18
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-0185/rubygem-activerecord-3.2.8-2.fc18
  64  
https://admin.fedoraproject.org/updates/FEDORA-2012-17834/cumin-0.1.5522-4.fc18
   0  https://admin.fedoraproject.org/updates/FEDORA-2013-0600/moin-1.9.6-1.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0659/perl-5.16.2-237.fc18
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-0306/ca-certificates-2012.87-1.fc18
   3  
https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-0320/sleuthkit-4.0.1-1.fc18
   9  
https://admin.fedoraproject.org/updates/FEDORA-2013-0063/php-ZendFramework-1.12.1-1.fc18
   4  https://admin.fedoraproject.org/updates/FEDORA-2013-0199/qt-4.8.4-6.fc18


The following Fedora 18 Critical Path updates have yet to be approved:
 Age URL
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0655/systemd-197-1.fc18.1
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0630/gnome-settings-daemon-3.6.4-1.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0659/perl-5.16.2-237.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0610/shadow-utils-4.1.5.1-2.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-0609/util-linux-2.22.2-2.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-0589/thunderbird-17.0.2-1.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-0559/bluez-4.101-6.fc18
   1  https://admin.fedoraproject.org/updates/FEDORA-2013-0572/dhcp-4.2.5-1.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-0531/parted-3.1-10.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-0528/linux-firmware-20121218-0.1.gitbda53ca.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-0541/mdadm-3.2.6-11.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-0524/gnutls-2.12.22-1.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-0543/empathy-3.6.3-1.fc18,gstreamer1-plugins-bad-free-1.0.5-1.fc18,gstreamer1-plugins-good-1.0.5-1.fc18,gstreamer1-plugins-base-1.0.5-1.fc18,gstreamer1-1.0.5-1.fc18
   3  https://admin.fedoraproject.org/updates/FEDORA-2013-0439/lzo-2.06-4.fc18
   3  
https://admin.fedoraproject.org/updates/FEDORA-2013-0409/xorg-x11-drv-evdev-2.7.3-3.fc18
   3  
https://admin.fedoraproject.org/updates/FEDORA-2013-0441/xorg-x11-drv-nouveau-1.0.6-1.fc18
   3  
https://admin.fedoraproject.org/updates/FEDORA-2013-0443/libdrm-2.4.40-2.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-0384/python-urlgrabber-3.9.1-24.fc18
   4  https://admin.fedoraproject.org/updates/FEDORA-2013-0364/pcre-8.31-4.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-0359/cogl-1.12.2-1.fc18
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-0306/ca-certificates-2012.87-1.fc18
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-0309/xorg-x11-drv-intel-2.20.17-1.fc18
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-0196/grubby-8.22-1.fc18
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-0165/qtwebkit-2.2.2-5.fc18
   4  https://admin.fedoraproject.org/updates/FEDORA-2013-0199/qt-4.8.4-6.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0149/python-bugzilla-0.7.0-3.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0162/bash-4.2.42-1.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-0143/wayland-1.0.3-1.fc18
   9  
https://admin.fedoraproject.org/updates/FEDORA-2013-0066/nautilus-3.6.3-4.fc18
   8  

Re: kernel headers

2013-01-12 Thread Christopher A. Williams
On Sat, 2013-01-12 at 15:26 +, Frank Murphy wrote:
 On Sat, 12 Jan 2013 07:56:40 -0700
 Christopher A. Williams chriswfed...@cawllc.com wrote:
 
 
 http://slackblogs.blogspot.ie/2012/12/linux-kernel-37-vmware-workstation-and.html
 thank the great God Google,
 now why didn't I think of that ;)

Now why didn't I try _that_ search string...

Ask Google the right question and you get amazing results. ;-)

Chris

-- 
Christopher A. Williams chriswfed...@cawllc.com

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

Some bash help needed

2013-01-12 Thread Gene Czarcinski
I have located and submitted a patch to correct a problem with grub2's 
handling of a three-device (actually, anything more than two) btrfs 
volume.  Here is the bugzilla report: 
https://bugzilla.redhat.com/show_bug.cgi?id=890955


And here is the patch:
---
From 4770be177085a17837687d2d858acfc9696092e1 Mon Sep 17 00:00:00 2001
From: Fedora Ninjas grub2-ow...@fedoraproject.org
Date: Fri, 11 Jan 2013 10:52:01 -0500
Subject: [PATCH] support for multi-device btrfs volume

The current code produces error messages if passed a device
list with multiple devices for a btrfs volume.  It worked OK
for single device btrfs volume.

This has been regression tested with root/boot on a regular
partition, single device VG logical volume,
and single device btrfs volume.
---
 util/grub-mkconfig_lib.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/util/grub-mkconfig_lib.in b/util/grub-mkconfig_lib.in
index 76133b4..8e2ff66 100644
--- a/util/grub-mkconfig_lib.in
+++ b/util/grub-mkconfig_lib.in
@@ -279,7 +279,7 @@ gettext_printf () {
 uses_abstraction () {
   device=$1

-  abstraction=`${grub_probe} --device ${device} --target=abstraction`
+  abstraction=`${grub_probe} --device ${device} --target=abstraction`
   for module in ${abstraction}; do
 if test x${module} = x$2; then
   return 0
--
1.8.1
---
with
device=/dev/vda2
/dev/vdb2
/dev/vdc3

Can someone more knowledgeable explain?

Gene


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

Re: Some bash help needed

2013-01-12 Thread Michal Jaegermann
On Sat, Jan 12, 2013 at 11:26:23AM -0500, Gene Czarcinski wrote:
 
 And here is the patch:
...
 -  abstraction=`${grub_probe} --device ${device} --target=abstraction`
 +  abstraction=`${grub_probe} --device ${device} --target=abstraction`
...
 with
 device=/dev/vda2
 /dev/vdb2
 /dev/vdc3
 
 Can someone more knowledgeable explain?

Dropping those quotes around ${device} replaces one parameter, which has
spaces inside and so it is not likely be a valid device name, with three
separate ones.  Does not make any difference with a single device but
means something else with multiple ones.  If you would like to visualise
what is going on here try to run the following script:

device=/dev/vda2
/dev/vdb2
/dev/vdc3

show_args () {
echo $#
while [ $1 ] ; do
echo $1; shift
done
}
grub_probe=show_args
abstraction=`${grub_probe} --device ${device} --target=abstraction`
echo $abstraction

and similar with other variants for 'abstraction'.

I have no idea if

... --device /dev/vda2 /dev/vdb2 /dev/vdc3 ...

is indeed a valid syntax for the real ${grub_probe}.  Possibly.

AFAICT outside double quotes for 'abstraction', i.e. `...` are not
doing here anything useful beyond making this more confusing and harder
to understand. abstraction=`...` would be just fine.

   Michal



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

[Fedora QA] #328: create boot.fedoraproject.org optional test case

2013-01-12 Thread Fedora QA
#328: create boot.fedoraproject.org optional test case
+--
 Reporter:  kevin   |   Owner:
 Type:  task|  Status:  new
 Priority:  minor   |   Milestone:
Component:  Test cases  | Version:
 Keywords:  |  Blocked By:
 Blocking:  |
+--
 test case would be something like:

 - download each of the images available from boot.fedoraproject.org

 - check sha256sum on each

 - transfer to indicated media

 - boot each and confirm that an install starts.

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/328
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #328: create boot.fedoraproject.org optional test case

2013-01-12 Thread Chris Murphy

On Jan 12, 2013, at 12:28 PM, Fedora QA t...@fedorahosted.org wrote:

 #328: create boot.fedoraproject.org optional test case
 +--
 Reporter:  kevin   |   Owner:
 Type:  task|  Status:  new
 Priority:  minor   |   Milestone:
 Component:  Test cases  | Version:
 Keywords:  |  Blocked By:
 Blocking:  |
 +--
 test case would be something like:
 
 - download each of the images available from boot.fedoraproject.org
 
 - check sha256sum on each
 
 - transfer to indicated media
 
 - boot each and confirm that an install starts.

At the risk of (very slowly) going down a long rabbit hole: if it's worth doing 
the above, I think it's worth finding out if there are any persistent problems 
resulting in installation failure. Transient problems can probably be ignored. 
Example, the first time I used BFO, it (I think anaconda) hung up for 2-3 hours 
because a mirror it had decided to use wasn't available, and there was no fall 
back. That's since been fixed, I think, but that's been years.

Do an installation, note any non-transient errors?


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

Re: [Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Kevin Fenzi
On Sat, 12 Jan 2013 12:02:06 +
Frank Murphy frankl...@gmail.com wrote:

 
 Anyone else having problems getting
 their network cards to play ball this morning?

Working fine here... 

dhclient-4.2.5-1.fc19.x86_64

selinux issues perhaps?

kevin


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

Re: [Fedora QA] #328: create boot.fedoraproject.org optional test case

2013-01-12 Thread Jóhann B. Guðmundsson

On 01/12/2013 07:43 PM, Chris Murphy wrote:

On Jan 12, 2013, at 12:28 PM, Fedora QA t...@fedorahosted.org wrote:


#328: create boot.fedoraproject.org optional test case
+--
Reporter:  kevin   |   Owner:
 Type:  task|  Status:  new
Priority:  minor   |   Milestone:
Component:  Test cases  | Version:
Keywords:  |  Blocked By:
Blocking:  |
+--
test case would be something like:

- download each of the images available from boot.fedoraproject.org

- check sha256sum on each

- transfer to indicated media

- boot each and confirm that an install starts.

At the risk of (very slowly) going down a long rabbit hole: if it's worth doing 
the above, I think it's worth finding out if there are any persistent problems 
resulting in installation failure. Transient problems can probably be ignored. 
Example, the first time I used BFO, it (I think anaconda) hung up for 2-3 hours 
because a mirror it had decided to use wasn't available, and there was no fall 
back. That's since been fixed, I think, but that's been years.

Do an installation, note any non-transient errors?


Optional test cases are fine for anything. That just means it can be 
tested not necessary it will be tested.


Adding this to the criteria however is not.

JBG

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

Re: [Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Bruno Wolff III

On Sat, Jan 12, 2013 at 12:59:51 -0700,
  Kevin Fenzi ke...@scrye.com wrote:

On Sat, 12 Jan 2013 12:02:06 +
Frank Murphy frankl...@gmail.com wrote:



Anyone else having problems getting
their network cards to play ball this morning?


Working fine here...

dhclient-4.2.5-1.fc19.x86_64

selinux issues perhaps?

kevin


My network devices seem OK.
I am having selinux problems. The systemd journal program gets blocked and it continuously tries to restart it. 
I am also having some sort of X/gdm/kernel issue. If I try to start X something hangs. I see a few flickers 
and then they stop. After that I can't switch to a VT. Briefly holding down the power button does do a 
controlled shutdown, so the system isn't dead.


Something in the last few days did this. With the combination of issues and lack of time, I haven't been 
able to narrow this down to what is causing the X related issue.

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

Re: test Digest, Vol 107, Issue 44

2013-01-12 Thread Marty Felker

On 01/12/2013 10:36 AM, test-requ...@lists.fedoraproject.org wrote:

Actually, in this case, the kernel-headers and kernel-devel packages are
installed. Further, this appears to only happen with the 3.7 series of
the kernel.

I know this because I was having the same problem and, because I need
VMware Workstation for my work (some things needed for my job require
Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I
can confirm that VMware Workstation 9.0.1 is working with kernel version
3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no
patches from VMware needed).

Now, I don't recall the exact error message with kernel 3.7 because I
reverted back to the 3.6 series (via yum distro-sync), but VMware
Workstation 9.0.1 clearly is having trouble finding the kernel headers
and other associated components with the 3.7 series of the kernel that
is in the updates-testing repository.

So, what that means is that something with respect to where the header
files are placed and located between these two series of kernels has
been changed to the point that applications like VMware Workstaion can
no longer find them. I would need to go back to the 3.7 series kernel to
get the exact error message. I may have it in an old VMware log file, so
I'll check that too next chance.
I've also had to back away from kernel 3.7 because even a symbolic link 
fix floating around WS 9.0.1 won't compile (as usual Virtualbox works 
fine!). Thke kernel dev seem to have moved the location of the heaader 
files (VMwareecan't find but I can - their search has always been weak).

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

Re: test Digest, Vol 107, Issue 44

2013-01-12 Thread Patrick O'Callaghan
On Sat, 2013-01-12 at 21:04 -0500, Marty Felker wrote:
 On 01/12/2013 10:36 AM, test-requ...@lists.fedoraproject.org wrote:
  Actually, in this case, the kernel-headers and kernel-devel packages are
  installed. Further, this appears to only happen with the 3.7 series of
  the kernel.
 
  I know this because I was having the same problem and, because I need
  VMware Workstation for my work (some things needed for my job require
  Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I
  can confirm that VMware Workstation 9.0.1 is working with kernel version
  3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no
  patches from VMware needed).
 
  Now, I don't recall the exact error message with kernel 3.7 because I
  reverted back to the 3.6 series (via yum distro-sync), but VMware
  Workstation 9.0.1 clearly is having trouble finding the kernel headers
  and other associated components with the 3.7 series of the kernel that
  is in the updates-testing repository.
 
  So, what that means is that something with respect to where the header
  files are placed and located between these two series of kernels has
  been changed to the point that applications like VMware Workstaion can
  no longer find them. I would need to go back to the 3.7 series kernel to
  get the exact error message. I may have it in an old VMware log file, so
  I'll check that too next chance.
 I've also had to back away from kernel 3.7 because even a symbolic link 
 fix floating around WS 9.0.1 won't compile (as usual Virtualbox works 
 fine!). Thke kernel dev seem to have moved the location of the heaader 
 files (VMwareecan't find but I can - their search has always been weak).

Please refrain from replying to digests
(https://fedoraproject.org/wiki/Mailing_list_guidelines#Replying_to_Digests)

poc

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

Re: kernel headers

2013-01-12 Thread Christopher A. Williams
On Sat, 2013-01-12 at 09:23 -0700, Christopher A. Williams wrote:
 On Sat, 2013-01-12 at 15:26 +, Frank Murphy wrote:
  On Sat, 12 Jan 2013 07:56:40 -0700
  Christopher A. Williams chriswfed...@cawllc.com wrote:
  
  
  http://slackblogs.blogspot.ie/2012/12/linux-kernel-37-vmware-workstation-and.html
  thank the great God Google,
  now why didn't I think of that ;)
 
 Now why didn't I try _that_ search string...
 
 Ask Google the right question and you get amazing results. ;-)

...Looked again at this. It's actually not quite what's needed. It says
to make a symbolic link from:

/usr/src/linux-3.7/include/generated/uapi/linux/version.h

to

/usr/src/linux-3.7/include/linux/version.h

only problem is that this first directory doesn't exist in Fedora from
what I can see. the file is actually located in:

/usr/src/kernels/kernel-version/include/linux/version.h

Is this a departure in Fedora from the stock kernel 3.7 series? I'll bet
this is really messing with VMware's scripts if it is. Since I am not
running Kernel 3.7 at the moment and don't have time to do so now, we'll
need someone else to have a look at this. I'm sure it's probably an easy
fix.

Chris

-- 
Christopher A. Williams chriswfed...@cawllc.com

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

Re: [Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Kevin Fenzi
On Sat, 12 Jan 2013 18:27:29 -0600
Bruno Wolff III br...@wolff.to wrote:

 My network devices seem OK.
 I am having selinux problems. The systemd journal program gets
 blocked and it continuously tries to restart it. I am also having
 some sort of X/gdm/kernel issue. If I try to start X something hangs.
 I see a few flickers and then they stop. After that I can't switch to
 a VT. Briefly holding down the power button does do a controlled
 shutdown, so the system isn't dead.
 
 Something in the last few days did this. With the combination of
 issues and lack of time, I haven't been able to narrow this down to
 what is causing the X related issue.

This is the libselinux update most likely. 

See: 

Subject: [rawhide] Warning: libselinux-2.1.12-12.fc19 breaks X/udev

Update to -13 and it should be happy again. 

kevin


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

Re: [Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Bruno Wolff III

On Sat, Jan 12, 2013 at 20:35:01 -0700,
  Kevin Fenzi ke...@scrye.com wrote:


Update to -13 and it should be happy again.


I got that, and a relabel fixed the systemd logger issue, so things are 
working OK again.

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

Re: [Rawhide] dhclient seg. out this morning?

2013-01-12 Thread Frank Murphy
On Sat, 12 Jan 2013 12:59:51 -0700
Kevin Fenzi ke...@scrye.com wrote:

 On Sat, 12 Jan 2013 12:02:06 +
 Frank Murphy frankl...@gmail.com wrote:
 
  
  Anyone else having problems getting
  their network cards to play ball this morning?
 
 Working fine here... 
 
 dhclient-4.2.5-1.fc19.x86_64
 
 selinux issues perhaps?
 
 kevin

found the culprit.

snip
:Jan 11 09:43:58 test07 yum-updateonboot[994]: Cleanup:
12:dhclient-4.2.5-0.3.rc1.fc19.i686   87/149 :Jan
11 09:47:35 test07 yum-updateonboot[994]: Verifying  :
12:dhclient-4.2.5-1.fc19.i686 62/149 :Jan
11 09:47:37 test07 yum-updateonboot[994]: Verifying  :
12:dhclient-4.2.5-0.3.rc1.fc19.i686  142/149 :Jan
11 09:47:40 test07 yum-updateonboot[994]: dhclient.i686
12:4.2.5-1.fc19 :Jan 12 07:49:22 test07 kernel: [   30.948525]
dhclient[775]: segfault at 8654c22a ip b76b6607 sp bfbe4240 error 6
in ld-2.17.so[b76ab000+1f000]

-- 
Regards,
Frank

Still trying to learn, both old and new tricks
--me .
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test