Re: Move from /media to /run/media/$USER

2012-04-14 Thread Jonathan Kamens
It is absurdly unpredictable that if I stick a DVD in my drive after 
logging in, it is mounted underneath /run/media/$USER, but if my 
computer than crashes, or I reboot it by hand, and I log in immediately 
after the reboot, that DVD is no longer mounted.


Independent of whether the move from /media to /run/media/$USER is a 
good idea, and I'm reserving judgment on that, clearly the behavior I 
just described above is entirely unexpected by the user and therefore wrong.


  Jonathan Kamens

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

Fedora 15 updates-testing report

2012-04-14 Thread updates
The following Fedora 15 Security updates need testing:


https://admin.fedoraproject.org/updates/FEDORA-2012-5256/wireshark-1.4.12-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5631/phpMyAdmin-3.5.0-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5805/samba-3.5.14-73.fc15.1

https://admin.fedoraproject.org/updates/FEDORA-2012-5822/gallery3-3.0.3-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5814/gallery2-2.3.2-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5436/quagga-0.99.20.1-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5915/python-2.7.3-1.fc15,python-docs-2.7.3-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5916/python3-3.2.3-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-5923/wicd-1.7.0-12.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-5420/rpm-4.9.1.3-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5422/freetype-2.4.4-8.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5406/libtiff-3.9.5-3.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5515/libpng-1.2.49-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2011-17233/tor-0.2.1.32-1500.fc15


The following Fedora 15 Critical Path updates have yet to be approved:


https://admin.fedoraproject.org/updates/FEDORA-2012-5915/python-2.7.3-1.fc15,python-docs-2.7.3-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5905/kernel-2.6.43.2-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5805/samba-3.5.14-73.fc15.1

https://admin.fedoraproject.org/updates/FEDORA-2012-5745/nss-util-3.13.4-2.fc15,nss-3.13.4-2.fc15,nss-softokn-3.13.4-1.fc15,nspr-4.9-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5515/libpng-1.2.49-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5406/libtiff-3.9.5-3.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-5422/freetype-2.4.4-8.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-5420/rpm-4.9.1.3-1.fc15
https://admin.fedoraproject.org/updates/dracut-009-15.fc15
https://admin.fedoraproject.org/updates/lm_sensors-3.3.2-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2011-13190/phonon-backend-gstreamer-4.5.90-2.fc15,phonon-4.5.57-1.20110914.fc15


The following builds have been pushed to Fedora 15 updates-testing

drupal6-views-2.16-2.fc15
kernel-2.6.43.2-2.fc15
oxygen-gtk3-1.0.3-1.fc15
perl-Net-GitHub-0.44-1.fc15
python-2.7.3-1.fc15
python-docs-2.7.3-1.fc15
python3-3.2.3-1.fc15
sugar-maze-17-1.fc15
wicd-1.7.0-12.fc15

Details about builds:



 drupal6-views-2.16-2.fc15 (FEDORA-2012-5908)
 Provides a method for site designers to control content presentation

Update Information:

Latest upstream.

ChangeLog:

* Fri Jan 13 2012 Fedora Release Engineering  
- 2.16-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
* Tue Nov 15 2011 Jon Ciesla  - 2.16-1
- Update to 2.16, BZ 754076.
* Fri Nov  4 2011 Jon Ciesla  - 2.14-1
- Update to 2.14, BZ 751044.




 kernel-2.6.43.2-2.fc15 (FEDORA-2012-5905)
 The Linux kernel

Update Information:

Linux 3.3.2


There was a regression at the DVB core, affecting applications that require the 
DVB status before having a lock. In order to allow a broader test (including my 
environment).

All new patches from the upstream media tree up to Apr, 10 got backported plus 
the fix patches, in order to have, among other things, the az6007 and af9035 
drivers backported.

Various bugfixes.

ChangeLog:

* Fri Apr 13 2012 Josh Boyer 
- Reapply rebased drivers-media-update.patch
* Fri Apr 13 2012 Dave Jones  2.6.43.2-1
- Linux 3.3.2
* Thu Apr 12 2012 Dennis Gilmore 
- KALLSYMS_EXTRA_PASS=1 has to be passed in on the command line so do so only 
for arm
* Tue Apr 10 2012 Mauro Carvalho Chehab 
- Backport dvb-core and a few driver fixes from media tree (rhbz808871)
* Tue Apr 10 2012 Josh Boyer 
- Apply upstream patch to add USB device 13d3:3375 (rhbz 811087)
- Backport fixes for correct register constraints in cmpxchg.h (rhbz 809014)
* Thu Apr  5 2012 Dave Jones 
- Better watermark the number of pages used by hibernation I/O (Bojan Smojver) 
(rhbz 785384)
* Wed Apr  4 2012 Josh Boyer 
- Disable runtime PM for hotpluggable ATA ports (rhbz 806676 807632)
- Fix NULL pointer dereference in i2400m (rhbz 808603)
* Tue Apr  3 2012 Josh Boye

Fedora 16 updates-testing report

2012-04-14 Thread updates
The following Fedora 16 Security updates need testing:


https://admin.fedoraproject.org/updates/FEDORA-2012-5624/phpMyAdmin-3.5.0-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-4946/freetype-2.4.6-5.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-5058/expat-2.1.0-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5155/perl-Pod-Plainer-1.03-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5833/python3-3.2.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5832/gallery3-3.0.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5806/gallery2-2.3.2-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5919/kde-partitionmanager-1.0.3-7.20120205svn.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5411/quagga-0.99.20.1-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5924/python-2.7.3-1.fc16,python-docs-2.7.3-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-5909/wicd-1.7.0-13.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5243/wireshark-1.6.6-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5434/tremulous-1.2.0-0.5.beta1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5410/libtiff-3.9.5-3.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-5421/rpm-4.9.1.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2011-14691/tomcat6-6.0.32-19.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5518/libpng-1.2.49-1.fc16


The following Fedora 16 Critical Path updates have yet to be approved:


https://admin.fedoraproject.org/updates/FEDORA-2012-5924/python-2.7.3-1.fc16,python-docs-2.7.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5906/rsyslog-5.8.10-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5750/PackageKit-0.6.22-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5669/v4l-utils-0.8.7-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5518/libpng-1.2.49-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5410/libtiff-3.9.5-3.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5396/gdb-7.3.50.20110722-14.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-5421/rpm-4.9.1.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5400/NetworkManager-0.9.4-2.git20120403.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5274/gnome-settings-daemon-3.2.3-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5236/virtuoso-opensource-6.1.5-2.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5227/akonadi-1.7.2-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-5148/flac-1.2.1-8.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5086/nss-util-3.13.4-2.fc16,nss-3.13.4-2.fc16,nss-softokn-3.13.4-1.fc16,nspr-4.9-2.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-5022/xorg-x11-server-1.11.4-3.fc16


The following builds have been pushed to Fedora 16 updates-testing

drupal6-views-2.16-2.fc16
kde-partitionmanager-1.0.3-7.20120205svn.fc16
oxygen-gtk2-1.2.3-1.fc16
oxygen-gtk3-1.0.3-1.fc16
perl-HTTP-Exception-0.04001-1.fc16
perl-Net-GitHub-0.44-1.fc16
python-2.7.3-1.fc16
python-docs-2.7.3-1.fc16
rsyslog-5.8.10-1.fc16
rubygem-dynect_rest-0.4.3-1.fc16
sugar-maze-17-1.fc16
sugar-turtleart-138-1.fc16
wicd-1.7.0-13.fc16

Details about builds:



 drupal6-views-2.16-2.fc16 (FEDORA-2012-5911)
 Provides a method for site designers to control content presentation

Update Information:

Latest upstream.

ChangeLog:

* Fri Jan 13 2012 Fedora Release Engineering  
- 2.16-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
* Tue Nov 15 2011 Jon Ciesla  - 2.16-1
- Update to 2.16, BZ 754076.
* Fri Nov  4 2011 Jon Ciesla  - 2.14-1
- Update to 2.14, BZ 751044.




 kde-partitionmanager-1.0.3-7.20120205svn.fc16 (FEDORA-2012-5919)
 KDE Partition Manager

Update Information:

Enabled PIE as requested by change in Packaging Guidelines.

ChangeLog:

* Fri Apr 13 2012 Mattia Verga  - 1.0.3-7.20120205svn
- Enable PIE following change in Pakaging Guidelines
* Wed Mar 14 2012 Mattia Verga  - 1.0.3-6.20120205svn
- Rebuilt for parted-3.1



=

Re: Move from /media to /run/media/$USER

2012-04-14 Thread Stijn Hoop
On Sat, 14 Apr 2012 12:49:20 +0530
Ankur Sinha  wrote:

> On Fri, 2012-04-13 at 14:05 -0500, Steven Stern wrote:
> > This behavior messes up a bunch of scripts I've written that assume
> > the
> > external USB drive "MyBackupDrive" will be hooked up as
> > "/media/MyBackupDrive" no matter who's logged in when it's plugged
> > in. Phooey. 
> 
> I have the same issue. Would anyone know where we can get specific
> details on the subject? I.e., what is going to get mounted where, in
> what condition? This move, while may be documented in the release
> notes as Bill pointed out, is going to confuse a plethora of users. 
> 
> I also think that this being mentioned in the release notes is not
> sufficient. It's a major change and deserves more visibility really. 

I agree. Some of our scripts will be bitten by this as well. I see
the reasons why it has moved and I accept them, it's just that I failed
to see any communication about it upfront. I think more people will be
surprised at this change...

Regards,

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

Re: F17 vs. Pentium 4

2012-04-14 Thread Michael Hennebry

On Sat, 14 Apr 2012, mwesten wrote:


On 04/14/2012 04:29 AM, Michael Hennebry wrote:



The next time, I made /boot sda2 and picked sda for the bootloader.
This time I got an install, but I'm not sure how to boot to it.
I'd rather not have to play with the BIOS
every time I want to boot a different install.
Is there a way to chainload to sda?
I'd have tried configfile,
but I don't think that works from old grub to grub2.


This is not quite clear to me.  It sounds like you can now boot F16 or 
whatever you had before by changing the BIOS boot drive.  Is that where 
we are?


GRUB Legacy can chainload the bootsector of the second drive with the 
chainloader command.


chainloader (hd1)+1


Thanks.
Chainloading worked, Grub 2 didn't.
GRUB Loading stage1.5
GRUB loading please wait...
Error 18

Huh?
I thought that Grub 2 was supposed to be smarter than old decrepit Grub.
1023 cylinders or not, sda2 was my /boot from the first time I installed
fedoralinux to some considerable time after I put in the second drive.
Old decrepit Grub handled it.
Why not wave of the future Grub?

Also note that sda2 does not cross the 1023 cylinder boundary.
root@localhost ~]# fdisk /dev/sda

Command (m for help): p

Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xece6ece6

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *  632867602414337981c  W95 FAT32 (LBA)
/dev/sda22867602528871576   97776   83  Linux
/dev/sda3288715774566 8398656   83  Linux
/dev/sda4456688897816535916248235+   5  Extended
/dev/sda54566895249574888 1952968+  82  Linux swap / Solaris
/dev/sda64957495262856296 6640672+  83  Linux
/dev/sda76285636078165359 7654500   83  Linux

1023*78165360/4865=16436415< 28676025

I'm pretty sure it is Grub 2.
Not only do I have a brand new grub2 directory with nearly 200 files in it,
[root@localhost ~]# file - < /dev/sda
/dev/stdin: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot 
drive 0x80, stage2 address 0x2000, stage2 segment 0x200; partition 1: ID=0xc, 
active, starthead 1, startsector 63, 28675962 sectors; partition 2: ID=0x83, 
starthead 7, startsector 28676025, 195552 sectors; partition 3: ID=0x83, 
starthead 7, startsector 28871577, 16797312 sectors; partition 4: ID=0x5, 
starthead 7, startsector 45668889, 32496471 sectors, code offset 0x63
[root@localhost ~]# file - < /dev/sdb
/dev/stdin: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, 
stage2 address 0x2000, stage2 segment 0x200, GRUB version 0.97; partition 1: 
ID=0x83, starthead 1, startsector 63, 78140097 sectors; partition 2: ID=0x83, 
active, starthead 254, startsector 78140160, 192780 sectors; partition 3: 
ID=0x83, starthead 254, startsector 78332940, 31262490 sectors; partition 4: 
ID=0x5, starthead 254, startsector 109595430, 671822235 sectors, code offset 
0x48
[root@localhost ~]#


--
Michael   henne...@web.cs.ndsu.nodak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword."  --  Lily
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Fedora 17 updates-testing report

2012-04-14 Thread updates
The following Fedora 17 Security updates need testing:


https://admin.fedoraproject.org/updates/FEDORA-2012-5599/phpMyAdmin-3.5.0-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5135/perl-Pod-Plainer-1.03-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5793/samba-3.6.4-82.fc17.1

https://admin.fedoraproject.org/updates/FEDORA-2012-5785/python3-3.2.3-2.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5787/gallery3-3.0.3-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5777/gallery2-2.3.2-2.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5854/samba4-4.0.0-40alpha18.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-5858/wicd-1.7.2.1-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5873/kde-partitionmanager-1.0.3-7.20120205svn.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5352/quagga-0.99.20.1-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5892/python-2.7.3-1.fc17,python-docs-2.7.3-1.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-5371/tremulous-1.2.0-0.5.beta1.fc17


The following builds have been pushed to Fedora 17 updates-testing

bip-0.8.8-5.fc17
emacs-magit-1.1.1-1.fc17
glib2-2.32.1-1.fc17
gtk3-3.4.1-1.fc17
mingw-glib2-2.32.1-1.fc17
mingw-glibmm24-2.32.0-1.fc17
mingw-gtk3-3.4.1-1.fc17
mingw-gtkmm30-3.4.0-1.fc17
ocsinventory-agent-2.0.5-1.fc17
ocsinventory-ipdiscover-2.0.5-1.fc17
oxygen-gtk2-1.2.3-1.fc17
oxygen-gtk3-1.0.3-1.fc17
spectrum-1.4.8-7.fc17
udisks-1.0.4-6.fc17

Details about builds:



 bip-0.8.8-5.fc17 (FEDORA-2012-5900)
 IRC Bouncer

Update Information:

This update fixes upstream https://projects.duckcorp.org/issues/252 - a bug 
which caused the messages from the two parties to a private chat to be written 
to different log files, rendering it difficult to read the logs.

ChangeLog:

* Fri Apr 13 2012 Adam Williamson  - 0.8.8-5
- upstream patch to fix privmsg logs being split up (upstream #252)




 emacs-magit-1.1.1-1.fc17 (FEDORA-2012-5898)
 Emacs interface to the most common Git operations

Update Information:

Update to upstream version 1.1.1.

ChangeLog:

* Wed Jan 25 2012 Tom Moertel  - 1.1.1-1
- Update to upstream 1.1.1




 glib2-2.32.1-1.fc17 (FEDORA-2012-5896)
 A library of handy utility functions

Update Information:

This bug-fix release fixes a number of bugs, most importantly:

673612 Fails to decode dictionaries wrapped in two layers of array

It also includes a number of translation updates.


ChangeLog:

* Fri Apr 13 2012 Matthias Clasen  2.32.1-1
- Update to 2.32.1




 gtk3-3.4.1-1.fc17 (FEDORA-2012-5899)
 The GIMP ToolKit (GTK+), a library for creating GUIs for X

Update Information:

This bug-fix release fixes a number of problems related to input handling and 
XI2.2 support, and also includes translation updates.

ChangeLog:

* Fri Apr 13 2012 Matthias Clasen  - 3.4.1-1
- Update to 3.4.1
* Mon Apr  2 2012 Matthias Clasen  - 3.4.0-2
- Bump up glib dependency (#806042)

References:

  [ 1 ] Bug #810614 - GdkEventButton contains wrong buttons in modifier mask 
for button releases
https://bugzilla.redhat.com/show_bug.cgi?id=810614
  [ 2 ] Bug #809486 - Mouse button lock after click onto inactive part of 
toolbar
https://bugzilla.redhat.com/show_bug.cgi?id=809486
  [ 3 ] Bug #807881 - Doesn't handle lots of wheel scroll events very well
https://bugzilla.redhat.com/show_bug.cgi?id=807881
  [ 4 ] Bug #806042 - symbol lookup error: /lib/libgtk-3.so.0: undefined 
symbol: g_signal_set_va_marshaller
https://bugzilla.redhat.com/show_bug.cgi?id=806042
--

Re: rpmbuild --target=i686 on x86_64 fails in configure

2012-04-14 Thread John5342
On Sat, Apr 14, 2012 at 17:27, Zoltan Boszormenyi  wrote:
> 2012-04-14 17:20 keltezéssel, John Reiser írta:
>
>>> What should I do to make rpmbuild work for --target=i686?
>>
>> Does this work:
>>    export CC="gcc -m32"
>>    rpmbuild -ba --target=i686 ...
>>
>
> Yes, it does. Although I still get signs that rpmbuild wants to build
> x86_64 binaries:
>
> + ./configure --host=x86_64-unknown-linux-gnu
> --build=x86_64-unknown-linux-gnu ...
>
> and
>
> checking for x86_64-unknown-linux-gnu-gcc... gcc -m32
>
> but the resulting binary rpm is suffixed as i686.rpm and
> the shard libs are 32-bit.

I always used to use setarch as well: "setarch i386 rpmbuild -ba
--target=i686 foo.spec"

That should fool the configure script into 32bit.

-- 
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: rpmbuild --target=i686 on x86_64 fails in configure

2012-04-14 Thread Dan Horák
Zoltan Boszormenyi píše v So 14. 04. 2012 v 18:27 +0200: 
> 2012-04-14 17:20 keltezéssel, John Reiser írta:
> >> What should I do to make rpmbuild work for --target=i686?
> > Does this work:
> > export CC="gcc -m32"
> > rpmbuild -ba --target=i686 ...
> >
> 
> Yes, it does. Although I still get signs that rpmbuild wants to build
> x86_64 binaries:
> 
> + ./configure --host=x86_64-unknown-linux-gnu 
> --build=x86_64-unknown-linux-gnu ...
> 
> and
> 
> checking for x86_64-unknown-linux-gnu-gcc... gcc -m32
> 
> but the resulting binary rpm is suffixed as i686.rpm and
> the shard libs are 32-bit.

rpmbuild doesn't support cross-compiles, it may or may not work, the
recommended way is to use mock, then you will get clean packages


Dan


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

Re: rpmbuild --target=i686 on x86_64 fails in configure

2012-04-14 Thread Zoltan Boszormenyi

2012-04-14 17:20 keltezéssel, John Reiser írta:

What should I do to make rpmbuild work for --target=i686?

Does this work:
export CC="gcc -m32"
rpmbuild -ba --target=i686 ...



Yes, it does. Although I still get signs that rpmbuild wants to build
x86_64 binaries:

+ ./configure --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu 
...

and

checking for x86_64-unknown-linux-gnu-gcc... gcc -m32

but the resulting binary rpm is suffixed as i686.rpm and
the shard libs are 32-bit.

Thanks.

Best regards,
Zoltán Böszörményi

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

Re: rpmbuild --target=i686 on x86_64 fails in configure

2012-04-14 Thread John Reiser
> What should I do to make rpmbuild work for --target=i686?

Does this work:
   export CC="gcc -m32"
   rpmbuild -ba --target=i686 ...

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

rpmbuild --target=i686 on x86_64 fails in configure

2012-04-14 Thread Zoltan Boszormenyi

Hi,

yesterday I installed Fedora 17 Beta RC4/x86_64 on my laptop and
wanted to compile newer than Mesa 8.0 to see the future of Linux
gaming. ;-) Since a lot of -devel packages can live happily in both
32- and 64-bit forms, I wanted to compile both versions of Mesa GIT.
To do that, I also needed a new libdrm from GIT.

"rpmbuild -ba libdrm.spec" succeeded, using the current src.rpm
and switching out the source tree under it. The patches listed in
libdrm.spec still apply correctly.

However, "rpmbuilt -ba --target=i686 libdrm.spec" fails:

[zozo@localhost SPECS]$ rpmbuild -ba --target=i686 libdrm.spec
...
autoreconf: Leaving directory `.'
+ CFLAGS='-O2 -g -march=i686'
+ export CFLAGS
+ CXXFLAGS='-O2 -g -march=i686'
+ export CXXFLAGS
+ FFLAGS='-O2 -g -march=i686'
+ export FFLAGS
+ ./configure --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu 
--program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
--sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib 
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib 
--mandir=/usr/share/man --infodir=/usr/share/info --enable-udev 
--enable-nouveau-experimental-api --enable-libkms

configure: WARNING: unrecognized options: --enable-nouveau-experimental-api
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for x86_64-unknown-linux-gnu-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/zozo/rpmbuild/BUILD/libdrm-2.4.33':
configure: error: C compiler cannot create executables
See `config.log' for more details
error: Bad exit status from /var/tmp/rpm-tmp.RGnIK6 (%build)


RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.RGnIK6 (%build)

config.log tells me this:

configure:3263: checking whether the C compiler works
configure:3285: gcc -O2 -g -march=i686   conftest.c >&5
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set

The problem is obvious: "rpmbuild --target=i686" only adds "-march=i686"
without "-m32". Compiling a minimal C source like the one below with
"gcc -m32 -o a a.c" succeeds and properly produces a 32-bit binary.

8<8<8<=
int main(void) { return 0; }
8<8<8<=

$ rpm -q rpm rpm-build
rpm-4.9.1.3-1.fc17.x86_64
rpm-build-4.9.1.3-1.fc17.x86_64

What should I do to make rpmbuild work for --target=i686?
I don't remember needing anything special under Fedora 16?

Best regards,
Zoltán Böszörményi

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

Re: F17 vs. Pentium 4

2012-04-14 Thread mwesten

On 04/14/2012 04:29 AM, Michael Hennebry wrote:

So I tried again.
I use grub's setup to put the bootloader on sdb and point it at sdb1.
I updated BIOS settings to use sdb.
Again anaconda labeled sdb partitons storage and sda partitions install.
It had sda marked for the bootloader.
It offered me the choice of sda or sdb19 for the bootloader.
I picked sdb19.

It choked the same way again.

The next time, I made /boot sda2 and picked sda for the bootloader.
This time I got an install, but I'm not sure how to boot to it.
I'd rather not have to play with the BIOS
every time I want to boot a different install.
Is there a way to chainload to sda?
I'd have tried configfile,
but I don't think that works from old grub to grub2.


This is not quite clear to me.  It sounds like you can now boot F16 or 
whatever you had before by changing the BIOS boot drive.  Is that where 
we are?


GRUB Legacy can chainload the bootsector of the second drive with the 
chainloader command.


chainloader (hd1)+1

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

NO EFI boot USB for MacBook Pro i7 with RC4.1 lives?

2012-04-14 Thread Thomas C Gilliard
possible problem: ./tools_livecd-iso-to-disk.sh --format --efi 
--overlay-size-mb 300 --home-size-mb 175 --delete-home 
--unencrypted-home Fedora-17-Beta-RC4-x86_64-Live-Desktop.iso /dev/sdb1  
fails on 4.1 live with  "invalid token legacy boot"


Works on RC4  Fedora-17-Beta-RC4-x86_64-Live-Desktop.iso

Result NO EFI boot USB for MacBook Pro i7 with RC4.1 lives?

Do we need both?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

It must be said: the photo import app in F17 is the most intrusive annoying piece of sw I've seen

2012-04-14 Thread Fernando Cassia
I find the photo import app in Fedora 17 the most intrusive, annoying
piece of software I've seen in a long, long time.

I plug a removable USB drive into the system and the transparent
window pops up telling me if I want to:

1. Import the pictures into this software
2. Eject.

There's no escape. What if I want to öpen a folder view" of the
drive?. You cant.
And if I click on Eject, well, the drive is gone.

Who in his right mind thought these only two options were the only
possible options?

If anything, there should be at the very least three options:

1.Import pictures into (piece of cr(p software I've now uninstalled)
2.Open a folder view
[ ] Do this automatically in the future
3. Eject

FC



-- 
During times of Universal Deceit, telling the truth becomes a revolutionary act
Durante épocas de Engaño Universal, decir la verdad se convierte en un
Acto Revolucionario
- George Orwell
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F-17 Branched report: 20120414 changes

2012-04-14 Thread Fedora Branched Report
Compose started at Sat Apr 14 08:15:03 UTC 2012

Broken deps for x86_64
--
[aeolus-conductor]
aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8
[aeolus-configserver]
aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri
[ale]
ale-0.9.0.3-6.fc17.x86_64 requires libMagickCore.so.4()(64bit)
[alexandria]
alexandria-0.6.8-2.fc17.1.noarch requires ruby(abi) = 0:1.8
[cuneiform]
cuneiform-1.1.0-6.fc17.i686 requires libMagick++.so.4
cuneiform-1.1.0-6.fc17.x86_64 requires libMagick++.so.4()(64bit)
[dh-make]
dh-make-0.55-4.fc17.noarch requires debhelper
[dmapd]
dmapd-0.0.47-2.fc17.i686 requires libMagickWand.so.4
dmapd-0.0.47-2.fc17.i686 requires libMagickCore.so.4
dmapd-0.0.47-2.fc17.x86_64 requires libMagickWand.so.4()(64bit)
dmapd-0.0.47-2.fc17.x86_64 requires libMagickCore.so.4()(64bit)
[dogtag-pki]
dogtag-pki-9.0.0-10.fc17.noarch requires pki-util-javadoc >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-util >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-tks >= 0:9.0.9
dogtag-pki-9.0.0-10.fc17.noarch requires pki-symkey >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-silent >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-setup >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-selinux >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-ocsp >= 0:9.0.9
dogtag-pki-9.0.0-10.fc17.noarch requires pki-native-tools >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-kra >= 0:9.0.10
dogtag-pki-9.0.0-10.fc17.noarch requires pki-java-tools-javadoc >= 
0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-java-tools >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-common-javadoc >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-common >= 0:9.0.18
dogtag-pki-9.0.0-10.fc17.noarch requires pki-ca >= 0:9.0.18
[drawtiming]
drawtiming-0.7.1-5.fc17.x86_64 requires libMagickCore.so.4()(64bit)
drawtiming-0.7.1-5.fc17.x86_64 requires libMagick++.so.4()(64bit)
[dustmite]
dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires 
libphobos2-ldc.so()(64bit)
[dx]
dx-4.4.4-21.fc17.x86_64 requires libMagickCore.so.4()(64bit)
dx-libs-4.4.4-21.fc17.i686 requires libMagickCore.so.4
dx-libs-4.4.4-21.fc17.x86_64 requires libMagickCore.so.4()(64bit)
[egoboo]
egoboo-2.7.5-11.fc17.x86_64 requires libenet-1.2.1.so()(64bit)
[entangle]
entangle-0.3.2-1.fc17.x86_64 requires libgexiv2.so.0()(64bit)
[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
[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)
[i3]
i3-4.0.1-2.fc17.x86_64 requires libxcb-property.so.1()(64bit)
i3-4.0.1-2.fc17.x86_64 requires libxcb-icccm.so.1()(64bit)
i3-4.0.1-2.fc17.x86_64 requires libxcb-event.so.1()(64bit)
i3-4.0.1-2.fc17.x86_64 requires libxcb-aux.so.0()(64bit)
i3-4.0.1-2.fc17.x86_64 requires libxcb-atom.so.1()(64bit)
[ibus-gucharmap]
ibus-gucharmap-1.4.0-4.fc17.x86_64 requires libibus-1.0.so.0()(64bit)
[ibus-panel-extensions]
ibus-panel-extensions-1.4.99.20111207-2.fc17.i686 requires 
libibus-1.0.so.0
ibus-panel-extensions-1.4.99.20111207-2.fc17.x86_64 requires 
libibus-1.0.so.0()(64bit)
[imageinfo]
imageinfo-0.05-14.fc17.x86_64 requires libMagickCore.so.4()(64bit)
[inkscape]
inkscape-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit)
inkscape-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit)
inkscape-view-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit)
inkscape-view-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit)
[jboss-as]
jboss-as-7.1.0-2.fc17.noarch requires slf4j-jboss-logmanager
[k3d]
k3d-0.8.0.2-6.fc17.i686 requires libMagickCore.so.4
k3d-0.8.0.2-6.fc17.i686 requires libMagick++.so.4
k3d-0.8.0.2-6.fc17.x86_64 requires libMagickCore.so.4()(64bit)
k3d-0.8.0.2-6.fc17.x86_64 requires libMagick++.so.4()(64bit)
[kxstitch]
kxstitch-0.8.4.1-8.fc17.x86_64 requires libMagickCore.so.4()(64bi

Re: F17 vs. Pentium 4

2012-04-14 Thread Michael Hennebry

On Fri, 13 Apr 2012, mwesten wrote:

Alright, I looked at the pics you posted and it appears that you have 
reproduced this anaconda crash during the bootloader installation:


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

I was looking at the included exception report and it seems this person 
was installing F16 on the second of two drives with the bootloader going 
on the first.


Is that what you were doing as well?


Yes.
So I tried again.
I use grub's setup to put the bootloader on sdb and point it at sdb1.
I updated BIOS settings to use sdb.
Again anaconda labeled sdb partitons storage and sda partitions install.
It had sda marked for the bootloader.
It offered me the choice of sda or sdb19 for the bootloader.
I picked sdb19.

It choked the same way again.

The next time, I made /boot sda2 and picked sda for the bootloader.
This time I got an install, but I'm not sure how to boot to it.
I'd rather not have to play with the BIOS
every time I want to boot a different install.
Is there a way to chainload to sda?
I'd have tried configfile,
but I don't think that works from old grub to grub2.
The grub2 directory has nearly 200 files in it.
Wow.



Also, I truly hate UUIDs.
For desktop systems, they are large, unintelligible overkill.
Labels are quite sufficient.


--
Michael   henne...@web.cs.ndsu.nodak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword."  --  Lily
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Move from /media to /run/media/$USER

2012-04-14 Thread Ankur Sinha
On Fri, 2012-04-13 at 14:05 -0500, Steven Stern wrote:
> This behavior messes up a bunch of scripts I've written that assume
> the
> external USB drive "MyBackupDrive" will be hooked up as
> "/media/MyBackupDrive" no matter who's logged in when it's plugged in.
> Phooey. 

I have the same issue. Would anyone know where we can get specific
details on the subject? I.e., what is going to get mounted where, in
what condition? This move, while may be documented in the release notes
as Bill pointed out, is going to confuse a plethora of users. 

I also think that this being mentioned in the release notes is not
sufficient. It's a major change and deserves more visibility really. 
-- 
Thanks, 
Regards,
Ankur: "FranciscoD"

http://fedoraproject.org/wiki/User:Ankursinha
http://dodoincfedora.wordpress.com/



signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test