Re: [Fedora QA] #271: L10N and i18n Test Day
#271: L10N and i18n Test Day ---+--- Reporter: aalam | Owner: jdulaney Type: task | Status: closed Priority: major | Milestone: Fedora 17 Component: Test Day |Version: Resolution: fixed | Keywords: Blocked By:| Blocking: ---+--- Changes (by aalam): * status: assigned = closed * resolution: = fixed Comment: Fedora 17 i18n/l10n Test Day Report: https://fedoraproject.org/wiki/FLTG/Fedora17_Report Task completed. Closing Ticket -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/271#comment:24 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: Hey! Hard disk install of DVD iso works!
I never had any issues with the DVD alpha or beta minus btrfs. Did you do any custom partitioning? Dan On Tue, Apr 17, 2012 at 5:02 PM, Adam Williamson awill...@redhat.comwrote: On Tue, 2012-04-17 at 18:13 -0400, Tom Horsley wrote: Unlike the Alpha DVD iso, I was able to install f17 Beta using the hard disk install technique, so at least one thing is definitely improved since the Alpha (but why is it *always* broken in Alphas? :-). The clue is in the name ;) -- 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 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options
Well that's an Anaconda bug isn't it? :) Still not a reason for a rolling release. I quite enjoy Fedora 14. Thanks, Dan On Wed, Apr 18, 2012 at 1:48 AM, Tom Horsley horsley1...@gmail.com wrote: On Wed, 18 Apr 2012 01:06:42 -0700 Dan Mashal wrote: You can install updates during the initial OS install. Just select updates and updates-testing repo. You will need network when you do this. You can do that, but then you find you can't restrict the install to packages only appearing on the DVD. The entire online inventory of packages shows up in the customise pages. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hey! Hard disk install of DVD iso works!
On Wed, 18 Apr 2012 01:46:54 -0700 Dan Mashal wrote: Just use whatever the default options are for upgrading or replace existing linux system with all default options for now, That should do it. I'm not upgrading. I'm installing from scratch in a different partition. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On 18.04.2012 07:46, Fernando Cassia wrote: Am I missing something obvious? Run program, right-click entry in sidebar, click Add to Favorites, perhaps? Jan -- Jan H Wildeboer| EMEA Open Source Affairs | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Technopark II, Haus C | Fax:+49 (0)89 205071-111 Werner-von-Siemens-Ring 11 -15 | 85630 Grasbrunn| _ Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15 85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243 Geschaeftsfuehrer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
RE: Hey! Hard disk install of DVD iso works!
Ok, will test tomorrow. Dan -Original Message- From: test-boun...@lists.fedoraproject.org [mailto:test-boun...@lists.fedoraproject.org] On Behalf Of Tom Horsley Sent: Wednesday, April 18, 2012 2:01 AM To: test@lists.fedoraproject.org Subject: Re: Hey! Hard disk install of DVD iso works! On Wed, 18 Apr 2012 01:46:54 -0700 Dan Mashal wrote: Just use whatever the default options are for upgrading or replace existing linux system with all default options for now, That should do it. I'm not upgrading. I'm installing from scratch in a different partition. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new Release Criterion proposal: kernel+initrd boot
On Tue, 2012-04-17 at 08:42 -0700, Brian C. Lane wrote: On Tue, Apr 17, 2012 at 12:08:04PM +0100, Adam Williamson wrote: On Mon, 2012-04-16 at 10:11 -0400, Kamil Paral wrote: [1] The installer must boot (if appropriate) and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media If there are no further objections I'll put it into Alpha criteria tomorrow. I'm okay with it, but I'm CCing bcl to give him a chance to object if anaconda team feels that supporting PXE in Alpha is unnecessarily ambitious... Yes, I think Alpha is too early to require PXE to work. I'm fine with Beta. In general I think we need to be fairly loose with Anaconda and Alpha -- as long as there is some way to boot the installer I'm happy. We currently don't see alot of installer testing in rawhide so the period before Alpha is too short to expect everything to be working. That sounds reasonable to me. Kamil, do you hate making it Beta? Sigh. Let's make it Beta. Currently there is some movement to make Fedora Branched and all its milestones available in Red Hat's automated testing suite. That uses PXE. Once that is done, I expect more pressure to make it work in Alpha. Another reason why I'm not thrilled is that I perform a lot of testing on a machine that doesn't support booting from USB. So I use PXE, because optical media are PITA. But if anaconda team says it's hard for them to make it in Alpha, let's make it Beta then. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-17 Branched report: 20120418 changes
Compose started at Wed Apr 18 08:15:05 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()(64bit)
Re: F17 Beta DVD install options
On Wed, Apr 18, 2012 at 4:49 AM, Dan Mashal dan.mas...@gmail.com wrote: Well that's an Anaconda bug isn't it? :) Still not a reason for a rolling release. I quite enjoy Fedora 14. Please, if you do nothing else, upgrade your kernel manually. josh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 10:23 +0200, Stijn Hoop wrote: 2. I have a plugged-in USB disk and I am at the physical console however I need to find the name of my USB disk in the folder list and click on it before I can use any files on it This is what I personally object to, and I suspect Jonathan does as well. It is a) inconsistent with other operating systems, at least Windows and Mac OS X. b) inconsistent with previous Fedora releases c) not by any means more secure for multi users since you need physical access to the machine to plug in a USB stick / insert a CD anyway So what are the real reasons for behavioural aspect #2, and was this design tested on users? Where is the rationale? Yeah, I'm honestly not a huge fan of this one either. It bugs me frequently. -- 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: Hey! Hard disk install of DVD iso works!
On Wed, 2012-04-18 at 04:44 -0400, Tom Horsley wrote: On Wed, 18 Apr 2012 00:56:04 -0700 Dan Mashal wrote: I never had any issues with the DVD alpha or beta minus btrfs. Did you do any custom partitioning? My problems came way before partitioning. It simply couldn't find the disk image given on the repo=hd:yadda-yadda kernel command line. With the Beta, things work fine. That was https://bugzilla.redhat.com/show_bug.cgi?id=806966 . Unfortunately, the next problem is (somewhat) related to partitioning - it can't properly install grub2 in the partition versus the MBR: https://bugzilla.redhat.com/show_bug.cgi?id=804835 I have somewhat worked around that by installing the grub2 from f16 in the f17 partition. That's still notabug, I think. See my comment. Even if it wasn't, the fault isn't anaconda's. It installs grub2 into the partition just fine. The code for doing so did not change in any way from F16 to F17, or from F17 Alpha to F17 Beta. It's in pyanaconda/bootloader.py if you want to look. -- 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: F17 Beta DVD install options
On Wed, 2012-04-18 at 01:49 -0700, Dan Mashal wrote: Well that's an Anaconda bug isn't it? :) Still not a reason for a rolling release. Why is it a bug at all? Why wouldn't you want that? -- 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: F17 Beta DVD install options
I know Fedora 14 is EOL. And sorry, I'm not that type. Try again. Dan On Wed, Apr 18, 2012 at 9:55 AM, Rick Stevens rstev...@corp.alldigital.comwrote: On 04/18/2012 09:22 AM, David wrote: On 4/18/2012 11:11 AM, Dan Mashal wrote: My system is secure. Thanks for your concern. Dan Fedora 14 is EOL since one month after Fedora 16. Fedora 15 will be EOL one month after Fedora 17. A long time with no security patches of any kind for any package for you. I know the type. 'I use Linux so I'm ten feet tall and bullet proof'. You forgot and invisible. --**--**-- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - grasshopotomus: A creature that can leap to tremendous heights... - -...once.- --**--**-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.**org/mailman/listinfo/testhttps://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options [OT]
On 2012/04/18 09:42 (GMT-0700) Tommy Pham composed: Tried a i386 F17 Beta on an old Dell Optiplex GX280 machine here at work and works fine. However my new upgraded home machine fails :( Hardware info: * Gigabyte GA-990FXA-UD5 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX * 3ware 9650SE-8LPML with 4x HDD on RAID5 * DVD-RW connected to a mobo SATA connection. All mobo SATAs (including eSATA) are set to AHCI, only the DVD-RW is connected to the mobo SATA. Presumably you mean all SATA on the new machine are set to AHCI? I can't find an AHCI setting in my GX280's BIOS, and would like to know where you did if you did. cf. https://bugzilla.novell.com/show_bug.cgi?id=757426#c23 -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options
On Wed, 2012-04-18 at 09:42 -0700, Tommy Pham wrote: On Tue, Apr 17, 2012 at 1:14 PM, Adam Williamson awill...@redhat.com wrote: On Tue, 2012-04-17 at 09:50 -0700, Tommy Pham wrote: Hi, Has anyone tried the recent beta released on DVD? Yes. Does it give various install options like F16? Yes. The alpha F17 only installed bare minimal. Um, no it didn't. It had a full set of install options and defaulted to a heavy graphical desktop install just like F16. That sounds like you wound up with text mode install, for some reason, which gives you a minimal package set and no choice about it. If that happens and you didn't explicitly request it, the important question becomes 'why did I wind up in text mode', and the answer is usually 'there's some kind of bug in the graphics driver for my video adapter'. Try Beta, and let us know what happens :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net Tried a i386 F17 Beta on an old Dell Optiplex GX280 machine here at work and works fine. However my new upgraded home machine fails :( What exactly do you mean by 'fails'? Going to need details to do any diagnosis. Thanks. -- 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: F17 Beta DVD install options
On Wed, 2012-04-18 at 12:22 -0400, David wrote: On 4/18/2012 11:11 AM, Dan Mashal wrote: My system is secure. Thanks for your concern. Fedora 14 is EOL since one month after Fedora 16. Fedora 15 will be EOL one month after Fedora 17. A long time with no security patches of any kind for any package for you. I know the type. 'I use Linux so I'm ten feet tall and bullet proof'. Maybe he is like me and has a machine that he can't upgrade. One of my machines has an HPT374 IDE RAID controller in it that hasn't worked for years. Last distro I cleanly loaded was RHEL4 (Whitebox4 actuallu) I managed to brutally hack the kernel in Fedora 10 with an old out of tree driver from Highpoint (GPL) to have something a little newer and did it again for F11 but a major kernel update along that line changed something I couldn't manage to fix. So that is where that machine stays until I finally toss the 4x200GB drives in it for a pair of larger ones connected to the onboard SATA plugs that should be supported. It is behind a NAT on a home network so I don't worry too much about it getting hacked. Firefox is almost certainly vulnerable but you rarely see active attacks in the wild against Linux browsers, especially if you don't hang out at dodgy sites. And if it happens, guess that will be the universe saying it is finally time to stop being a cheap bastard and buy some new drives. 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
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 12:15 -0400, Jonathan Kamens wrote: OK, so I took a look at the GNOME Disks utility, which I was finally able to get to run without crashing, and as far as I can tell, it doesn't resolve my main complaint with the new F17 behavior. Yes, I can use the Disks utility to configure removable devices, e.g., my DVD drive, to mount on startup. But then it isn't going to mount in /run/media/$USER, because there's no user logged in yet. My concern, which I've explained repeatedly and I believe is quite legitimate despite all of the flak I've taken for it here, is that the behavior of a removable device that is already inserted when I log in should be exactly the same as the behavior of a removable device that I insert after logging in. As far as I can tell the Disks utility can't achieve that. If I'm wrong, please explain to me exactly how I should configure, e.g., my DVD drive in the Disks utility so that if there's a DVD in the drive when I log in, it will be mounted under /run/media/$USER automatically. (And, while you're at it, explain to me why this shouldn't be the default behavior, which I've yet to see anyone here explain, as far as I recall.) If you set a specific mount location for a device in that tool - i.e. in fstab - it will be used even if the device is connected after login. -- 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: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On 04/18/2012 01:06 PM, Adam Williamson wrote: If you set a specific mount location for a device in that tool - i.e. in fstab - it will be used even if the device is connected after login. Yes, I'm aware of that, but that's not what I want. If it is the position of the Fedora developers that /run/media/$USER is the right place for stuff to be mounted, and I don't have a particular problem with that decision, then I want /that/ behavior, i.e., the behavior that the developers think is correct, /with/ the F16 behavior of the device being mounted automatically when I log in. Why /shouldn't/ it act that way? jik -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Draft SOP for requesting TCs/RCs
On Wed, 2012-03-14 at 18:03 -0700, Adam Williamson wrote: On Tue, 2012-03-13 at 06:04 -0400, Kamil Paral wrote: One remark to this paragraph: It is theoretically possible that the situation could arise where a release candidate is requested and built, and results in multiple blockers being reported and accepted, some of which are easy to fix and some of which are not; in this case a subsequent compose to test the easy fixes may be desirable, but could not be denoted a release candidate due to the presence of the other un-addressed blockers. In this case a new test compose could be requested. This is obviously somewhat confusing, however, so it is best to try and get all the blockers fixed and request a new release candidate instead. I don't believe this is a good idea. I would rather have QA team vote on exceptional circumstances and call it another RC. There's no point in calling it TC just to satisfy some criteria. TC and RC naming is confusing already. RC TC, but not alphabetically. Having e.g. TC1 RC1 RC2 TC2 RC3 is a complete mess, arcane knowledge that only QA team would have. Since we generally ask also other parties to perform testing, we should have the naming pattern as obvious and straightforward as possible. Let's call it RC and lets clearly state that this is an exceptional process that should happen just rarely. BTW, your line wrapping seems to be broken again :) Yeah, I'm not super happy with it either. I mainly just included it because we nearly actually *did* it once. The thing is, I'm not really happy with the alternative you suggest (calling it an RC) either. I really think it's a good thing to stick to a strict definition, and a release candidate, strictly, is a build you believe can be the release. A build which is known to include a blocker simply is not a release candidate. It could not possibly be released. So I'd love if we could come up with a third way. I'm wondering if we should simply leave this unaddressed in the SOP and deal with it on the fly if the situation ever arises. I think perhaps we should give any such build a label that's different from both TC and RC, if it ever happens. Any bright ideas, anyone? We did have a few different bright ideas, but they're all rather bigger changes that might be better off being discussed separately from this SOP. So how about this: what if we put the current draft into production but entirely leave out the paragraph about doing a TC release after an RC release, so the SOP just doesn't cover the case at all? That would at least document current practice reasonably well. Then I'll try and find some time to synthesize all the ideas that came later in this thread, about revising TC/RC naming and so on, and maybe go back in time as well because I recall some similar proposals being made on devel a year or so back. I'll try and come up with some kind of comprehensive proposal covering all those ideas, in terms of actually revising the process itself. This SOP proposal was really just intended to be a document _describing_ current practice, I didn't have changing the practice in mind when writing it. If that sounds okay to everyone, I'll put the SOP minus the controversial paragraph into 'production' tomorrow, and then work on the new 'change the process' proposal when I can. Thanks! -- 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: F17 Beta DVD install options
On Wed, 2012-04-18 at 12:05 -0500, John Morris wrote: It is behind a NAT on a home network so I don't worry too much about it getting hacked. Firefox is almost certainly vulnerable but you rarely see active attacks in the wild against Linux browsers, especially if you don't hang out at dodgy sites. And if it happens, guess that will be the universe saying it is finally time to stop being a cheap bastard and buy some new drives. How do you know it _hasn't_ happened? Not all hacks involve the attacker posting some kind of 'HAHA U HAZ BEEN HACKED' notice to let you know about it. Those are the _nice_ hackers. -- 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: F17 Beta DVD install options [OT]
On Wed, Apr 18, 2012 at 14:00, Felix Miata mrma...@earthlink.net wrote: Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- Another OS/2 user joins the Fedora Family. I remember you from the OS/2 lists Felix, welcome. :) FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 13:10 -0400, Jonathan Kamens wrote: Yes, I'm aware of that, but that's not what I want. If it is the position of the Fedora developers that /run/media/$USER is the right place for stuff to be mounted, and I don't have a particular problem with that decision, then I want that behavior, i.e., the behavior that the developers think is correct, with the F16 behavior of the device being mounted automatically when I log in. Why shouldn't it act that way? Oh, I see. I don't know about that. I don't know if there's a way to make GNOME mount devices on login rather than on access. I think that's a GNOME policy question rather than a udisks one. It may be worth asking on the desktop list. Matthias, are you reading this? -- 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: F17 Beta DVD install options
I can upgrade. I know how to. It's actually a Virtualbox VM running on a quad core AMD box with 16GB of RAM. Yes, it is natted. Yes SSH is open to the internet. Yes nginx is open to the internet. Yes other ports are open to the internet. No I've never gotten hacked. Any other questions? Thanks, Dan On Wed, Apr 18, 2012 at 10:05 AM, John Morris jmor...@beau.org wrote: On Wed, 2012-04-18 at 12:22 -0400, David wrote: On 4/18/2012 11:11 AM, Dan Mashal wrote: My system is secure. Thanks for your concern. Fedora 14 is EOL since one month after Fedora 16. Fedora 15 will be EOL one month after Fedora 17. A long time with no security patches of any kind for any package for you. I know the type. 'I use Linux so I'm ten feet tall and bullet proof'. Maybe he is like me and has a machine that he can't upgrade. One of my machines has an HPT374 IDE RAID controller in it that hasn't worked for years. Last distro I cleanly loaded was RHEL4 (Whitebox4 actuallu) I managed to brutally hack the kernel in Fedora 10 with an old out of tree driver from Highpoint (GPL) to have something a little newer and did it again for F11 but a major kernel update along that line changed something I couldn't manage to fix. So that is where that machine stays until I finally toss the 4x200GB drives in it for a pair of larger ones connected to the onboard SATA plugs that should be supported. It is behind a NAT on a home network so I don't worry too much about it getting hacked. Firefox is almost certainly vulnerable but you rarely see active attacks in the wild against Linux browsers, especially if you don't hang out at dodgy sites. And if it happens, guess that will be the universe saying it is finally time to stop being a cheap bastard and buy some new drives. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 'alacarte' crashes, and no apparent way to set Start-up apps, but yes, there is, and hidden (Gnome-session-properties)
On Wed, Apr 18, 2012 at 13:00, Adam Williamson awill...@redhat.com wrote: Should I file a bug fix about this? No, you'd be wasting your time. It's hidden intentionally because it's considered deprecated in GNOME 3. The GNOME devs don't like the whole session handling stuff and consider it fundamentally too fragile to be advertised to users. Okay, and the replacement is?. FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options [OT]
On Wed, Apr 18, 2012 at 10:00 AM, Felix Miata mrma...@earthlink.net wrote: On 2012/04/18 09:42 (GMT-0700) Tommy Pham composed: Tried a i386 F17 Beta on an old Dell Optiplex GX280 machine here at work and works fine. However my new upgraded home machine fails :( Hardware info: * Gigabyte GA-990FXA-UD5 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX * 3ware 9650SE-8LPML with 4x HDD on RAID5 * DVD-RW connected to a mobo SATA connection. All mobo SATAs (including eSATA) are set to AHCI, only the DVD-RW is connected to the mobo SATA. Presumably you mean all SATA on the new machine are set to AHCI? I can't find an AHCI setting in my GX280's BIOS, and would like to know where you did if you did. cf. https://bugzilla.novell.com/show_bug.cgi?id=757426#c23 -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- Yes, I'm sorry I wasn't explicit about the problems and the hardware info with related settings. The AHCI are set on my new Gigabyte mobo. (I only tested the F17 beta on GX280 just to make sure that the GUI install process should work.) Side note, I think there's like 3 SATA chip for that Gigabyte mobo: 1 AMD SB950 (4 SATA ports) and 2 x Marvell 88SE9172 chips (2 internal + 2 eSATA). I also remembering seeing that the kernel did detect that Marvell chip. I'll check on the messages later when I get home to get the details. Thanks, Tommy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Yum upgrade F16 - F17
Adam Williamson wrote: I did test upgrade with yum following info on https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum After doing succesfull usrmove i did upgrade with: yum --releasever=17 update rpm rm -f /var/lib/rpm/__* rpm --rebuilddb yum --releasever=17 distro-sync If i boot after that i see that kernel is not updated and shutdown doesnt work. If i run yum update after distro-sync, there is still packages updating: These results are both actually expected for a typical F16 config (though they surprised you :). The distro-sync operation will not have used the updates-testing repository, because this repo wouldn't have been enabled before the operation. The kernel in F17's current 'stable' repo is older than the newest F16 kernel, so it's normal that when you do this kind of upgrade - and, indeed, when you do a DVD upgrade using the Beta - you don't get a new kernel. It's also normal that a subsequent 'yum update' shows more updates available, because the 'distro-sync' installs a new fedora-release, with the updates-testing repository *enabled* by default - so on the next yum operation, all those packages in updates-testing show up. Bit surprising, sure, but actually, everything there works as it's intended to. If you want to do a one-step upgrade you could add '--enablerepo=updates-testing' to the 'distro-sync' operation. Ok this makes sense. So this is problem only exists when F17 is in beta, when released distro-upgrade would update all needed packages. Thanks for clarifying this. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
But no, right clicking on empty space doesn't do diddly squat in the Gnome 3 Applications screen. I do not think a click on nothing is persuasively intuative as a way to create an application launcher. Who wants diddly squats littering the screen, anyway? For programs that can be found through the Applications function (top left corner in the default desktop arrangement), a right click on the desired application and selection of Add to favorites seems rather intuitive. I suspect your concern may be for an easy way to add new programs to the Applications function, which is a more obscure matter. Something that creates a .desktop file in the right way, perhaps? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, Apr 18, 2012 at 05:55, Jan Wildeboer jwild...@redhat.com wrote: On 18.04.2012 07:46, Fernando Cassia wrote: Am I missing something obvious? Run program, right-click entry in sidebar, click Add to Favorites, perhaps? Jan who mentioned favorites?? Let me repeat: I download a Java app for instance. A single .jar. I put it into /usr/local/bin/myapp.jar I want to create a new program entry (so it shows in the list of installed apps) that does java -jar /usr/local/bin/myapp.jar and with a custom name and icon. How do I do that, from the GUI, without dropping to the shell?. FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hey! Hard disk install of DVD iso works!
That's still notabug, I think. See my comment. Even if it wasn't, the fault isn't anaconda's. Then the bug should be moved to grub2, because it sure is a bug. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On 04/18/2012 07:56 PM, Fernando Cassia wrote: On Wed, Apr 18, 2012 at 14:48, Richard Ryniker ryni...@alum.mit.edu wrote: I suspect your concern may be for an easy way to add new programs to the Applications function, which is a more obscure matter. Something that creates a .desktop file in the right way, perhaps? I think that should be done by alacarte, but it's broken actually. -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, Apr 18, 2012 at 14:59, Joachim Backes joachim.bac...@rhrk.uni-kl.de wrote: I think that should be done by alacarte, but it's broken actually. Joachim, I appreciate your reply, and don´t get me wrong, but anybody else understands how counter-intuititive this whole thing is?. Why need to call an external program to create a new program launcher? are Gnome devs nuts? It should be a function of the bloody desktop, sheesh!. Imagine in Windows or OSX if to create a new program launcher you were told to find program Cardmudgeon to do the operation... Again, User Experience, they have heard of it... And I´ve used a number of desktops from GEOS back in the Commodore 64 days to AmigaOS to the OS/2 Workplace Shell. None were as awkward and incomplete as Gnome 3.x is in some areas. I know this doesn´t solve my problem, but I´m outraged. FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, Apr 18, 2012 at 14:48, Richard Ryniker ryni...@alum.mit.edu wrote: I do not think a click on nothing is persuasively intuative as a way to create an application launcher. Right clicking over something to obtain a pop-up menu of actions to perform on it is an almost universal metaphor in the GUI world. If you click on empty space, it´s assumed you want to perform actions on the desktop. It has worked that way from the OS/2 Workplace Shell (whose paradigm was ´everything is an object´) to Windows, too... (and previous Gnome versions). FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act - George Orwell -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On 18/04/12 19:07, Fernando Cassia wrote: It has worked that way from the OS/2 Workplace Shell (whose paradigm was ´everything is an object´) to Windows, too... (and previous Gnome versions). Unfortunately CUA is going (gone) the way of the DoDo -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options
On Wed, 2012-04-18 at 12:22 -0400, David wrote: On 4/18/2012 11:11 AM, Dan Mashal wrote: My system is secure. Thanks for your concern. Fedora 14 is EOL since one month after Fedora 16. Fedora 15 will be EOL one month after Fedora 17. A long time with no security patches of any kind for any package for you. I know the type. 'I use Linux so I'm ten feet tall and bullet proof'. Maybe he is like me and has a machine that he can't upgrade. One of my machines has an HPT374 IDE RAID controller in it that hasn't worked for years. Last distro I cleanly loaded was RHEL4 (Whitebox4 actuallu) I managed to brutally hack the kernel in Fedora 10 with an old out of tree driver from Highpoint (GPL) to have something a little newer and did it again for F11 but a major kernel update along that line changed something I couldn't manage to fix. So that is where that machine stays until I finally toss the 4x200GB drives in it for a pair of larger ones connected to the onboard SATA plugs that should be supported. It is behind a NAT on a home network so I don't worry too much about it getting hacked. Firefox is almost certainly vulnerable but you rarely see active attacks in the wild against Linux browsers, especially if you don't hang out at dodgy sites. And if it happens, guess that will be the universe saying it is finally time to stop being a cheap bastard and buy some new drives. I can fully appreciate your situation, if aint broke Fedora, Ubuntu and Slackware user Linux counter #386175 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, Apr 18, 2012 at 15:10, Frank Murphy frankl...@gmail.com wrote: Unfortunately CUA is going (gone) the way of the DoDo Hi Frank, What, you read my rant? :) http://news.techeye.net/software/software-gui-design-going-to-hell-in-a-basket FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act - George Orwell -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On 18/04/12 19:15, Fernando Cassia wrote: On Wed, Apr 18, 2012 at 15:10, Frank Murphy frankl...@gmail.com mailto:frankl...@gmail.com wrote: Unfortunately CUA is going (gone) the way of the DoDo Hi Frank, What, you read my rant? :) http://news.techeye.net/software/software-gui-design-going-to-hell-in-a-basket No, just studied sw design for a bit. -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, Apr 18, 2012 at 15:17, Frank Murphy frankl...@gmail.com wrote: No, just studied sw design for a bit. :)) FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
Three use cases in which in my opinion the behavior is clearly incorrect: Case 1: 1. Put DVD in drive while logged in. DVD is mounted. 2. Reboot computer and log back in. DVD is not mounted. It should be. Case 2: 1. Put DVD in drive before logging in. DVD is not mounted. 2. Log in. DVD is not mounted. It should be. Case 3: 1. Put DVD in drive while logged in. DVD is mounted. 2. Log out. DVD stays mounted under /run/media/$USER. It should have been unmounted when you logged out. 3. Log back in as another user. DVD is still mounted under /run/media//previous-$USER/. It should have been remounted under your $USER. jik On 04/18/2012 02:40 PM, Bill Nottingham wrote: Adam Williamson (awill...@redhat.com) said: On Wed, 2012-04-18 at 13:10 -0400, Jonathan Kamens wrote: Yes, I'm aware of that, but that's not what I want. If it is the position of the Fedora developers that /run/media/$USER is the right place for stuff to be mounted, and I don't have a particular problem with that decision, then I want that behavior, i.e., the behavior that the developers think is correct, with the F16 behavior of the device being mounted automatically when I log in. Why shouldn't it act that way? Oh, I see. I don't know about that. I don't know if there's a way to make GNOME mount devices on login rather than on access. I think that's a GNOME policy question rather than a udisks one. It may be worth asking on the desktop list. Matthias, are you reading this? So, I'm a bit confused. I tried to reproduce this with a USB stick today. If I plug it in while I'm logged in, it shows up. I log out and log back in, and it still shows up. If I reboot, plug it in during GDM, and then log in... it shows up. Under what circumstance does it not show up for you? Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: started display manager = hang
On Wed, Apr 18, 2012 at 12:12, Fernando Cassia fcas...@gmail.com wrote: So, I´m running out of clues as to what to do. I´m curious if any of you running F17 with the testing repos experienced any hiccup wrt X not starting up?. If not, I´d really appreciate clues wrt how to get my system back to a working state. OK, I´m progressing but not at the speed I´d wish. I looked at the Xorg log files and the last thing it loaded before the hang were the vbox drivers. I remember the last thing I had installed before the reboot was the vbox ose plugins. So I went to the xorg libs dir and removed vbox*. I guess I was wrong to remove the files without removing the references to them, as now the system boots to a point where the monitors put themselves in power-saving mode (blinking power led) and I can´t even do ctrl-alt-f2 to get to a login prompt. So, I´d really appreciate if someone more knowledgeable about Xorg snafus would give me a generic recipe to get my system back to at least vesa mode. I guess booting from grub 2.0 in single user mode would be first right? 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
Fedora 15 updates-testing report
The following Fedora 15 Security updates need testing: 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-6055/puppet-2.6.16-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6001/gajim-0.15-2.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-6025/openssh-5.6p1-36.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-5905/kernel-2.6.43.2-2.fc15 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-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/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 Zim-0.56-1.fc15 gajim-0.15-2.fc15 gdesklets-0.36.3-6.1.fc15 gfal2-2.0.0-0.6.2012041515snap.fc15 imapsync-1.488-1.fc15 janino-parent-2.6.1-3.fc15 josm-0-0.29.5181svn.fc15 kde-plasma-networkmanagement-0.9.0.1-1.fc15 munin-1.4.7-2.fc15 openssh-5.6p1-36.fc15 perl-DBIx-Class-DynamicDefault-0.04-1.fc15 perl-Mail-IMAPClient-3.31-1.fc15 procServ-2.6.0-1.fc15 puppet-2.6.16-1.fc15 python-libcloud-0.9.1-1.fc15 qlandkartegt-1.4.0-2.fc15 rbldnsd-0.996b-6.fc15 rear-1.13.0-1.fc15 rubygem-mustache-0.99.4-4.fc15 sane-backends-1.0.22-10.fc15 sugar-maze-18-1.fc15 Details about builds: Zim-0.56-1.fc15 (FEDORA-2012-6036) Desktop wiki notekeeper Update Information: New upstream release. ChangeLog: * Wed Apr 4 2012 Robin Lee cheese...@fedoraproject.org - 0.56-1 - Update to 0.56 gajim-0.15-2.fc15 (FEDORA-2012-6001) Jabber client written in PyGTK Update Information: Fixes CVE-2012-2093 gajim (LaTeX module): Insecure creation of temporary file ChangeLog: * Tue Apr 17 2012 Michal Schmidt mschm...@redhat.com 0.15-2 - CVE-2012-2093 gajim (LaTeX module): Insecure creation of temporary file References: [ 1 ] Bug #811651 - CVE-2012-2093 gajim (LaTeX module): Insecure creation of temporary file https://bugzilla.redhat.com/show_bug.cgi?id=811651 gdesklets-0.36.3-6.1.fc15 (FEDORA-2012-6048) Architecture for desktop applets Update Information: Backport fix from F16 related memory leak bug ChangeLog: * Tue Mar 20 2012 Luya Tshimbalanga l...@fedoraproject.org - 0.36.3-6 - Adhered to Fedora guideline for desktop declaration - Ported patch from OpenSuse spec version - Patch addressing memory leak (rhbz #747420, launchpad #190894) - Drop patch for vfs * Fri Jan 13 2012
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
If I plug it in while I'm logged in, it shows up. I log out and log back in, and it still shows up. If I reboot, plug it in during GDM, and then log in... it shows up. Under what circumstance does it not show up for you? If your USB stick is plugged in before you boot your system, where does it show up? Nowhere. The device node is created (/dev/sd...) but it is not mounted. (Yes, I believe an entry in /etc/fstab will help in some cirsumstances.) Root can mount the device, but behavior then varies. Mount over /x is normal but mount over /home/desktop user/x causes the Gnome desktop to pop up a menu that offers: Open with files or Eject. Eject will only work after authentication (quite proper - the device was mounted by root) whereas automatic mount over /run/media/desktop user/label allows the user to Eject without authentication. None of this is intrinsically terrible, but there is a surfeit of different behaviors that will likely confuse many users at one time or another. This feels like a consensus issue: with no agreed strategy about what should happen, programmers wrote whatever seemed appropriate for the case they were coding. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
Richard Ryniker (ryni...@alum.mit.edu) said: If I plug it in while I'm logged in, it shows up. I log out and log back in, and it still shows up. If I reboot, plug it in during GDM, and then log in... it shows up. Under what circumstance does it not show up for you? Aha, for this last one it's a timing issue... if it scans slow enough that it 'appears' during the session, it will be mounted. If your USB stick is plugged in before you boot your system, where does it show up? Nowhere. The device node is created (/dev/sd...) but it is not mounted. (Yes, I believe an entry in /etc/fstab will help in some cirsumstances.) It shows up in the file manager; it's not mounted. Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On 04/18/2012 04:45 PM, Bill Nottingham wrote: It shows up in the file manager; it's not mounted. Why not? In F16, it was mounted. In Windows, it's mounted. In Mac OS, it's mounted. Why should F17 behave differently from F17 and from every other mainstream OS people are familiar with? What is the justification for this different, unexpected, non-intuitive behavior? jik -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: started display manager = hang
On Wed, Apr 18, 2012 at 16:13, Fernando Cassia fcas...@gmail.com wrote: So, I´d really appreciate if someone more knowledgeable about Xorg snafus would give me a generic recipe to get my system back to at least vesa mode. I guess booting from grub 2.0 in single user mode would be first right? Okay the silence was educative, for me, :) forced me to learn things on my own. Indeed, as I suspected, the problem was the Vbox add-ons (VirtualBox-OSE-Guest). I manually went to /etc/X11/xorg.conf.d/ and removed 00-vboxvideo.conf Rebooted and all is well. 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
Re: F17 vs. Pentium 4
On Wed, 18 Apr 2012, Adam Williamson wrote: On Tue, 2012-04-17 at 17:39 -0500, Michael Hennebry wrote: I've booted F16. My old-grub stanza: title chainload to sda kernel (hd1,1)/grub2/core.img As I didn't expect it to work, I only installed the minimal version. There are a few things that concern me. When I tried to login as hennebry, my password showed on the console. Probably a plymouth issue. I'd found these before your response: http://en.wikipedia.org/wiki/Plymouth_%28software%29 http://en.wikipedia.org/wiki/Talk:Plymouth_(software) Someone really doesn't like plymouth. Also, which of the following should concern me: [root@localhost root]# grep -v Installing install.log warning: setup-2.8.36-2.fc16.noarch: Header V3 RSA/SHA256 Signature, key ID a82ba4b7: NOKEY Need 'inst' function, try setting PLYMOUTH_POPULATE_SOURCE_FUNCTIONS to a file that defines it SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.26, searching for an older version. SELinux: Could not open policy file = /etc/selinux/targeted/policy/policy.26: No such file or directory load_policy: Can't load policy: No such file or directory grubby fatal error: unable to find a suitable template grubby: doing this would leave no kernel entries. Not writing out new config. *** FINISHED INSTALLING PACKAGES *** [root@localhost root]# I wouldn't be hugely worried about any of them. Try doing a full install and I suspect a lot of the above 'weirdness' would go away. Will do. Thanks. -- 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
8 GB USB with DVD: formatted as GPT with 4 GB partition fat /dev/sdb1 2nd 4 GB left,unformatted
I just did a sucessful install to an external USB HD using a USB of Fedora-17-Beta-x86_64-DVD.iso -It only used the Install Repo on the DVD(USB) ./tools_livecd-iso-to-disk.sh --format --reset-mbr Fedora-17-Beta-x86_64-DVD.iso /dev/sdb1 1-)needed an 8GB USB formatted GPT format with /dev/sdb1 formatted fat in disk-utility 2-)only 4GB was formatted label:LIVE and 4GB was left unformatted 3-)a second partition was created by anaconda labeled LIVE-REPO (with Fedora 17 Beta-x86-64-DVD.iso inside) https://bugzilla.redhat.com/show_bug.cgi?id=811412#c22 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, Apr 18, 2012 at 10:48 PM, Jonathan Kamens j...@kamens.us wrote: On 04/18/2012 04:45 PM, Bill Nottingham wrote: It shows up in the file manager; it's not mounted. Why not? In F16, it was mounted. In Windows, it's mounted. In Mac OS, it's mounted. Why should F17 behave differently from F17 and from every other mainstream OS people are familiar with? What is the justification for this different, unexpected, non-intuitive behavior? It got fixed / reverted: http://git.gnome.org/browse/gvfs/commit/?id=e30a67f3215 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 8 GB USB with DVD: formatted as GPT with 4 GB partition fat /dev/sdb1 2nd 4 GB left,unformatted
On 04/18/2012 03:51 PM, Thomas Gilliard wrote: I just did a sucessful install to an external USB HD using a USB of Fedora-17-Beta-x86_64-DVD.iso -It only used the Install Repo on the DVD(USB) ./tools_livecd-iso-to-disk.sh --format --reset-mbr Fedora-17-Beta-x86_64-DVD.iso /dev/sdb1 1-)needed an 8GB USB formatted GPT format with /dev/sdb1 formatted fat in disk-utility 2-)only 4GB was formatted label:LIVE and 4GB was left unformatted 3-)a second partition was created by anaconda labeled LIVE-REPO (with Fedora 17 Beta-x86-64-DVD.iso inside) https://bugzilla.redhat.com/show_bug.cgi?id=811412#c22 Another issue with 8GB USB sticks is that liveusb-creator won't let you use their full capacity: https://bugzilla.redhat.com/show_bug.cgi?id=798041 -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options [OT]
On Wed, 2012-04-18 at 14:17 -0300, Fernando Cassia wrote: On Wed, Apr 18, 2012 at 14:00, Felix Miata mrma...@earthlink.net wrote: Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- Another OS/2 user joins the Fedora Family. I remember you from the OS/2 lists Felix, welcome. :) Felix has been around here for years... -- 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: 'alacarte' crashes, and no apparent way to set Start-up apps, but yes, there is, and hidden (Gnome-session-properties)
On Wed, 2012-04-18 at 14:27 -0300, Fernando Cassia wrote: On Wed, Apr 18, 2012 at 13:00, Adam Williamson awill...@redhat.com wrote: Should I file a bug fix about this? No, you'd be wasting your time. It's hidden intentionally because it's considered deprecated in GNOME 3. The GNOME devs don't like the whole session handling stuff and consider it fundamentally too fragile to be advertised to users. Okay, and the replacement is?. Suspend and resume, apparently. If you always suspend rather than shutting down, your session never ends... -- 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: Yum upgrade F16 - F17
On Wed, 2012-04-18 at 20:34 +0300, Tomi Leppikangas wrote: If you want to do a one-step upgrade you could add '--enablerepo=updates-testing' to the 'distro-sync' operation. Ok this makes sense. So this is problem only exists when F17 is in beta, when released distro-upgrade would update all needed packages. It still wouldn't install packages from updates-testing; but the default configs for both 16 and 17 would have that repo disabled, so there would be no obvious inconsistency. -- 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: 8 GB USB with DVD: formatted as GPT with 4 GB partition fat /dev/sdb1 2nd 4 GB left,unformatted
I suppose since all that is installed on the /dev/sdb1 LIVE partition is LiveOS - 130.4 MB syslinux - 29.4 MB Properties: 159.9 MB used 5.2 GB free Filesystem type:msdos the /dev/sdb2 LIVE-REPO contains a 2.5 GB .iso file. Properties: 2.5 GB used 168.9 MB free Filesystem type:msdos It could be much smaller. Looks like a 4 GB USB should work well for this. I did not use the graphical liveusb-creator to build this installer DVD USB however. On 04/18/2012 03:24 PM, Eric Blake wrote: On 04/18/2012 03:51 PM, Thomas Gilliard wrote: I just did a sucessful install to an external USB HD using a USB of Fedora-17-Beta-x86_64-DVD.iso -It only used the Install Repo on the DVD(USB) ./tools_livecd-iso-to-disk.sh --format --reset-mbr Fedora-17-Beta-x86_64-DVD.iso /dev/sdb1 1-)needed an 8GB USB formatted GPT format with /dev/sdb1 formatted fat in disk-utility 2-)only 4GB was formatted label:LIVE and 4GB was left unformatted 3-)a second partition was created by anaconda labeled LIVE-REPO (with Fedora 17 Beta-x86-64-DVD.iso inside) https://bugzilla.redhat.com/show_bug.cgi?id=811412#c22 Another issue with 8GB USB sticks is that liveusb-creator won't let you use their full capacity: https://bugzilla.redhat.com/show_bug.cgi?id=798041 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hey! Hard disk install of DVD iso works!
On Wed, 2012-04-18 at 13:57 -0400, Tom Horsley wrote: That's still notabug, I think. See my comment. Even if it wasn't, the fault isn't anaconda's. Then the bug should be moved to grub2, because it sure is a bug. If grub2 isn't designed to be chainloaded in that way, it isn't. Like I said, I believe the answer is simply 'to chainload grub2 you load core.img, rather than using the chainloader command'. -- 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: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 14:40 -0400, Bill Nottingham wrote: Adam Williamson (awill...@redhat.com) said: On Wed, 2012-04-18 at 13:10 -0400, Jonathan Kamens wrote: Yes, I'm aware of that, but that's not what I want. If it is the position of the Fedora developers that /run/media/$USER is the right place for stuff to be mounted, and I don't have a particular problem with that decision, then I want that behavior, i.e., the behavior that the developers think is correct, with the F16 behavior of the device being mounted automatically when I log in. Why shouldn't it act that way? Oh, I see. I don't know about that. I don't know if there's a way to make GNOME mount devices on login rather than on access. I think that's a GNOME policy question rather than a udisks one. It may be worth asking on the desktop list. Matthias, are you reading this? So, I'm a bit confused. I tried to reproduce this with a USB stick today. If I plug it in while I'm logged in, it shows up. I log out and log back in, and it still shows up. If I reboot, plug it in during GDM, and then log in... it shows up. Under what circumstance does it not show up for you? The problem is with the definition of 'shows up'. GNOME will show such devices in Nautilus, file chooser etc, but it doesn't actually automount until you try to access it through such a graphical app. So you can't access it through the terminal unless you mount it manually or go click on it in Nautilus to get it mounted first. -- 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: F17 vs. Pentium 4
On Wed, 2012-04-18 at 16:39 -0500, Michael Hennebry wrote: On Wed, 18 Apr 2012, Adam Williamson wrote: On Tue, 2012-04-17 at 17:39 -0500, Michael Hennebry wrote: I've booted F16. My old-grub stanza: title chainload to sda kernel (hd1,1)/grub2/core.img As I didn't expect it to work, I only installed the minimal version. There are a few things that concern me. When I tried to login as hennebry, my password showed on the console. Probably a plymouth issue. I should be more precise, and say it's probably a _lack_ of plymouth issue... -- 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: Hey! Hard disk install of DVD iso works!
On Thu, 19 Apr 2012 00:05:42 +0100 Adam Williamson wrote: If grub2 isn't designed to be chainloaded in that way, it isn't. But it is supposed to work. I've already added a pointer to an upstream bug fixed not too long ago where blocklist booting was broken and the grub maintainers considered that a bug. Also Mads Kiilerich has built various different versions from the grub2 sources and gotten them to work correctly. It is clearly a grub2 bug and we either need Mads' new grub2 in the final release or we need to revert to the version in f16. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hey! Hard disk install of DVD iso works!
On 04/17/2012 07:02 PM, Adam Williamson wrote: On Tue, 2012-04-17 at 18:13 -0400, Tom Horsley wrote: (but why is it *always* broken in Alphas? :-). The clue is in the name ;) I disagree. Alphas obviously have bugs, but when the *same* bug (or different bugs with the same symptoms) are present in alpha after alpha (or beta after beta, etc.) then something is broken in the process. -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hey! Hard disk install of DVD iso works!
On Wed, 2012-04-18 at 19:54 -0400, Tom Horsley wrote: On Thu, 19 Apr 2012 00:05:42 +0100 Adam Williamson wrote: If grub2 isn't designed to be chainloaded in that way, it isn't. But it is supposed to work. I've already added a pointer to an upstream bug fixed not too long ago where blocklist booting was broken and the grub maintainers considered that a bug. I missed that reference. Could you add it to the bug report? Also Mads Kiilerich has built various different versions from the grub2 sources and gotten them to work correctly. Where is this documented? It is clearly a grub2 bug and we either need Mads' new grub2 in the final release or we need to revert to the version in f16. I don't see it as being a release blocking issue in any event. If you want to chainload, you can. If it can be 'fixed' then it would be nice to do so, of course. -- 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: F17 Beta DVD install options
On Wed, 2012-04-18 at 18:13 +0100, Adam Williamson wrote: Not all hacks involve the attacker posting some kind of 'HAHA U HAZ BEEN HACKED' notice to let you know about it. Those are the _nice_ hackers. Well they usually DO something with a machine they have 0wn3ed. No spam spewing forth, no probes against other hosts, etc. And rpm -Va doesn't show anything nasty in the packages that would give an intruder an in. OpenWrt is running on the gateway so I see what sort of things are going through the NAT. And it is up to date. Is all that enough to be 100% sure? Nah. On the other hand if I were the sort of paranoid who spent a lot of time with those sort of thoughts I'd be running OpenBSD. 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
Re: F17 Beta DVD install options
On Wed, 2012-04-18 at 19:25 -0500, John Morris wrote: On Wed, 2012-04-18 at 18:13 +0100, Adam Williamson wrote: Not all hacks involve the attacker posting some kind of 'HAHA U HAZ BEEN HACKED' notice to let you know about it. Those are the _nice_ hackers. Well they usually DO something with a machine they have 0wn3ed. Like, rifle through the data for anything useful? Keep it backdoored for future use? Things like that... No spam spewing forth, no probes against other hosts, etc. Doesn't mean a whole lot...see above. And rpm -Va doesn't show anything nasty in the packages that would give an intruder an in. If someone's owned the machine, they can make rpm -Va say whatever they like. Is all that enough to be 100% sure? Nah. On the other hand if I were the sort of paranoid who spent a lot of time with those sort of thoughts I'd be running OpenBSD. Well, sure, there's a line to be drawn somewhere. But even if you're not a security paranoiac, it's very important to know there's a huge world of difference between I'm not aware my machine has been hacked and I'm aware my machine has not been hacked... -- 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: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 16:48 -0400, Jonathan Kamens wrote: On 04/18/2012 04:45 PM, Bill Nottingham wrote: It shows up in the file manager; it's not mounted. Why not? In F16, it was mounted. In Windows, it's mounted. In Mac OS, it's mounted. Why should F17 behave differently from F17 and from every other mainstream OS people are familiar with? What is the justification for this different, unexpected, non-intuitive behavior? The arguments are really going downhill here. I'm not overly interested in wading into this, but I'll just say that whenever we do something automatically, somebody will get mad. In the past, auto-mounting (and even just automatically sniffing) of media has been construed as a security issue.. Anyway, http://git.gnome.org/browse/gvfs/commit/?id=e30a67f3215d829e95ee7e358c67af7d67635fe8 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 Beta DVD install options [OT]
On Wed, Apr 18, 2012 at 10:32 AM, Tommy Pham tommy...@gmail.com wrote: On Wed, Apr 18, 2012 at 10:00 AM, Felix Miata mrma...@earthlink.net wrote: On 2012/04/18 09:42 (GMT-0700) Tommy Pham composed: Tried a i386 F17 Beta on an old Dell Optiplex GX280 machine here at work and works fine. However my new upgraded home machine fails :( Hardware info: * Gigabyte GA-990FXA-UD5 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX * 3ware 9650SE-8LPML with 4x HDD on RAID5 * DVD-RW connected to a mobo SATA connection. All mobo SATAs (including eSATA) are set to AHCI, only the DVD-RW is connected to the mobo SATA. Presumably you mean all SATA on the new machine are set to AHCI? I can't find an AHCI setting in my GX280's BIOS, and would like to know where you did if you did. cf. https://bugzilla.novell.com/show_bug.cgi?id=757426#c23 -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- Yes, I'm sorry I wasn't explicit about the problems and the hardware info with related settings. The AHCI are set on my new Gigabyte mobo. (I only tested the F17 beta on GX280 just to make sure that the GUI install process should work.) Side note, I think there's like 3 SATA chip for that Gigabyte mobo: 1 AMD SB950 (4 SATA ports) and 2 x Marvell 88SE9172 chips (2 internal + 2 eSATA). I also remembering seeing that the kernel did detect that Marvell chip. I'll check on the messages later when I get home to get the details. Thanks, Tommy I did something last night that really broke F17. Unfortunately, I was a bit tired and didn't keep track of the things I did so I couldn't restore it. So I reinstalled F16 and about to do preupgrade to F17 again because the F17 alpha would only give me bare minimal install. Haven't had the chance to burn a F17 beta DVD yet. OK here is the info on new upgraded system (UUID 1e8f3c02-9ccd-45f7-9060-68f4d0aea671 - ID of submitted system profile - of reinstalled F16 from DVD)... [root@fedora /]# yum update Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update [root@fedora /]# uname -a Linux fedora.workgroup.domain 3.3.1-5.fc16.x86_64 #1 SMP Tue Apr 10 19:56:52 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux [root@fedora /]# grep -i 'sata' /var/log/messages Apr 18 18:02:14 fedora kernel: [0.939482] ahci :00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode Apr 18 18:02:14 fedora kernel: [0.940336] ata1: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19 Apr 18 18:02:14 fedora kernel: [0.940340] ata2: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19 Apr 18 18:02:14 fedora kernel: [0.940343] ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19 Apr 18 18:02:14 fedora kernel: [0.940346] ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19 Apr 18 18:02:14 fedora kernel: [0.940482] ahci :03:00.0: AHCI 0001. 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Apr 18 18:02:14 fedora kernel: [0.940864] ata5: SATA max UDMA/133 abar m512@0xfdaff000 port 0xfdaff100 irq 41 Apr 18 18:02:14 fedora kernel: [0.940867] ata6: SATA max UDMA/133 abar m512@0xfdaff000 port 0xfdaff180 irq 41 Apr 18 18:02:14 fedora kernel: [0.940994] ahci :0a:00.0: AHCI 0001. 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Apr 18 18:02:14 fedora kernel: [0.941390] ata7: SATA max UDMA/133 abar m512@0xfd0ff000 port 0xfd0ff100 irq 42 Apr 18 18:02:14 fedora kernel: [0.941393] ata8: SATA max UDMA/133 abar m512@0xfd0ff000 port 0xfd0ff180 irq 42 Apr 18 18:02:14 fedora kernel: [1.245074] ata5: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.245080] ata4: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.245109] ata6: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.245116] ata2: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.245149] ata1: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.245172] ata3: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.247052] ata7: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [1.401071] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Apr 18 18:02:14 fedora kernel: [1.404803] ata8: limiting SATA link speed to 1.5 Gbps Apr 18 18:02:14 fedora kernel: [6.861230] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 18 18:02:14 fedora kernel: [ 12.321242] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ** Note that my DVD-RW is installed on ata8 since that's the only port with link up. [root@fedora /]# lspci|egrep -i '(sb9x|marvell)' 00:11.0 SATA controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) provide 4 ports as
Re: No way to add a new app launcher from Gnome 3.x GUI?
On Wed, 2012-04-18 at 21:22 -0400, Matthias Clasen wrote: On Wed, 2012-04-18 at 15:04 -0300, Fernando Cassia wrote: I know this doesn´t solve my problem, but I´m outraged. In general, we expect an application to bring a suitable desktop file so it is usable after you installed it. That is even part of the packaging guidelines, last I checked. If the application you want a launcher for is something you created yourself, I don't think it is outrageous to expect you to write a desktop file after you already wrote the application... And nobody ever needed a launcher for a script or downloaded an app outside the package manager or did anything but be a nice little end user and let the GNOMEs take care of everything. Steve Jobs is smiling somewhere. I make .desktop files on a regular basis to fire off ssh sessions and such. Or did until I abandoned GNOME and found XFCE won't launch ssh via a .desktop link under some circumstances I haven't understood yet. Some of my existing desktop links work, others don't and I haven't nailed down the cause yet. Point being, creating app shortcuts is something a medium skill user should be expected to be able to figure out. Telling em to 'go fish' isn't really an answer that anyone should be willing to accept. 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
Re: F17 Beta DVD install options
On Thu, 2012-04-19 at 02:30 +0100, Adam Williamson wrote: And rpm -Va doesn't show anything nasty in the packages that would give an intruder an in. If someone's owned the machine, they can make rpm -Va say whatever they like. Which brings up a good point. I know that the only way to be sure is booting the machine from a known good[1] rescue media and then check with a copy of RPM running from there using the --root option to point at the suspect filesystem to ensure the system's rpm binary isn't trojaned or the kernel patched to show the original executables to rpm. And even then a REAL enemy would exploit a zero day buffer overflow in rpm via the infected rpm database. On the other hand, has there ever been a real case found in the wild of an infestation that was so good at covering its tracks? The security problems I saw in the past were the crudest script kiddies and I haven't even seen one of those attacks succeed since the 20th Century even on erratically updated machines. There aren't a lot of exploits against Linux to begin with, how many are going for deep penetration that aren't targeted hits by intelligence agencies? If the NSA wants to look at your or my machine they will and we will almost certainly never have a clue they were there. In short, just how theoretical an attack am I expending effort to repel? [1] And that IS the nub of the problem now isn't it; and the gateway to insanity. Do you trust the rescue media and/or the machine that downloaded and burned it? 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
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Wed, 2012-04-18 at 21:38 -0400, Matthias Clasen wrote: The arguments are really going downhill here. I'm not overly interested in wading into this, but I'll just say that whenever we do something automatically, somebody will get mad. In the past, auto-mounting (and even just automatically sniffing) of media has been construed as a security issue.. Anyway, http://git.gnome.org/browse/gvfs/commit/?id=e30a67f3215d829e95ee7e358c67af7d67635fe8 Honestly, I'm not sure there's any difference at all between 'mount on attach' and 'mount on any attempt to access' from a security POV. I think the decision to change this was a good one, and I doubt it'll make many people unhappy - and as several commenters have pointed out, it's only in line with what every other OS we can think of does by default, and what Fedora / GNOME has always done in the past. -- 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: F17 Beta DVD install options
On Wed, 2012-04-18 at 21:19 -0500, John Morris wrote: On the other hand, has there ever been a real case found in the wild of an infestation that was so good at covering its tracks? The security problems I saw in the past were the crudest script kiddies and I haven't even seen one of those attacks succeed since the 20th Century even on erratically updated machines. There aren't a lot of exploits against Linux to begin with, how many are going for deep penetration that aren't targeted hits by intelligence agencies? If the NSA wants to look at your or my machine they will and we will almost certainly never have a clue they were there. In short, just how theoretical an attack am I expending effort to repel? I'm not any kind of security expert, but I'm pretty sure the answer to your first question is 'yes' and the answer to your last is 'not theoretical'. One interesting thing to do is look at the things chkrootkit checks for. As far as I'm aware, most of the chkrootkit checks are responses to real-world attacks. If you look at the checks, you can deduce that some of the attacks are pretty sophisticated. Oh, I'm pretty sure quite a lot real-world attacks work in ways that an rpm -Va check wouldn't expose, without needing to actually mung the rpm -Va operation in any way - simply by using files that aren't rpm tracked, for instance. But yeah, I'm not an expert on security at all, I only know enough to be a danger to myself and others. ;) -- 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: F17 Beta DVD install options [OT]
On Wed, Apr 18, 2012 at 6:39 PM, Tommy Pham tommy...@gmail.com wrote: On Wed, Apr 18, 2012 at 10:32 AM, Tommy Pham tommy...@gmail.com wrote: On Wed, Apr 18, 2012 at 10:00 AM, Felix Miata mrma...@earthlink.net wrote: On 2012/04/18 09:42 (GMT-0700) Tommy Pham composed: Tried a i386 F17 Beta on an old Dell Optiplex GX280 machine here at work and works fine. However my new upgraded home machine fails :( Hardware info: * Gigabyte GA-990FXA-UD5 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX * 3ware 9650SE-8LPML with 4x HDD on RAID5 * DVD-RW connected to a mobo SATA connection. All mobo SATAs (including eSATA) are set to AHCI, only the DVD-RW is connected to the mobo SATA. Presumably you mean all SATA on the new machine are set to AHCI? I can't find an AHCI setting in my GX280's BIOS, and would like to know where you did if you did. cf. https://bugzilla.novell.com/show_bug.cgi?id=757426#c23 -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- Yes, I'm sorry I wasn't explicit about the problems and the hardware info with related settings. The AHCI are set on my new Gigabyte mobo. (I only tested the F17 beta on GX280 just to make sure that the GUI install process should work.) Side note, I think there's like 3 SATA chip for that Gigabyte mobo: 1 AMD SB950 (4 SATA ports) and 2 x Marvell 88SE9172 chips (2 internal + 2 eSATA). I also remembering seeing that the kernel did detect that Marvell chip. I'll check on the messages later when I get home to get the details. Thanks, Tommy I did something last night that really broke F17. Unfortunately, I was a bit tired and didn't keep track of the things I did so I couldn't restore it. So I reinstalled F16 and about to do preupgrade to F17 again because the F17 alpha would only give me bare minimal install. Haven't had the chance to burn a F17 beta DVD yet. OK here is the info on new upgraded system (UUID 1e8f3c02-9ccd-45f7-9060-68f4d0aea671 - ID of submitted system profile - of reinstalled F16 from DVD)... [root@fedora /]# yum update Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update [root@fedora /]# uname -a Linux fedora.workgroup.domain 3.3.1-5.fc16.x86_64 #1 SMP Tue Apr 10 19:56:52 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux [root@fedora /]# grep -i 'sata' /var/log/messages Apr 18 18:02:14 fedora kernel: [ 0.939482] ahci :00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode Apr 18 18:02:14 fedora kernel: [ 0.940336] ata1: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19 Apr 18 18:02:14 fedora kernel: [ 0.940340] ata2: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19 Apr 18 18:02:14 fedora kernel: [ 0.940343] ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19 Apr 18 18:02:14 fedora kernel: [ 0.940346] ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19 Apr 18 18:02:14 fedora kernel: [ 0.940482] ahci :03:00.0: AHCI 0001. 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Apr 18 18:02:14 fedora kernel: [ 0.940864] ata5: SATA max UDMA/133 abar m512@0xfdaff000 port 0xfdaff100 irq 41 Apr 18 18:02:14 fedora kernel: [ 0.940867] ata6: SATA max UDMA/133 abar m512@0xfdaff000 port 0xfdaff180 irq 41 Apr 18 18:02:14 fedora kernel: [ 0.940994] ahci :0a:00.0: AHCI 0001. 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Apr 18 18:02:14 fedora kernel: [ 0.941390] ata7: SATA max UDMA/133 abar m512@0xfd0ff000 port 0xfd0ff100 irq 42 Apr 18 18:02:14 fedora kernel: [ 0.941393] ata8: SATA max UDMA/133 abar m512@0xfd0ff000 port 0xfd0ff180 irq 42 Apr 18 18:02:14 fedora kernel: [ 1.245074] ata5: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.245080] ata4: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.245109] ata6: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.245116] ata2: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.245149] ata1: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.245172] ata3: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.247052] ata7: SATA link down (SStatus 0 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.401071] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Apr 18 18:02:14 fedora kernel: [ 1.404803] ata8: limiting SATA link speed to 1.5 Gbps Apr 18 18:02:14 fedora kernel: [ 6.861230] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 18 18:02:14 fedora kernel: [ 12.321242] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ** Note that my DVD-RW is installed on ata8 since that's the only port with link up. [root@fedora /]# lspci|egrep -i
Re: automatically mounting physically attached media (was Re: Move from /media to /run/media/$USER)
On Thu, 2012-04-19 at 03:26 +0100, Adam Williamson wrote: On Wed, 2012-04-18 at 21:38 -0400, Ma Honestly, I'm not sure there's any difference at all between 'mount on attach' and 'mount on any attempt to access' from a security POV. http://git.gnome.org/browse/gvfs/commit/?id=e30a67f3215d829e95ee7e358c67af7d67635fe8 is an example for the kind of unhappiness you get - and there's also very little difference between doing something automatically while the screen is locked or doing something automatically with an already plugged in device on login or unlock. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 16 updates-testing report
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-5058/expat-2.1.0-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-5999/puppet-2.6.16-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6061/gajim-0.15-2.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5410/libtiff-3.9.5-3.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6179/gridengine-6.2u5p2-7.fc16.3 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/selinux-policy-3.10.0-84.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6188/gnome-color-manager-3.2.3-2.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6204/libdrm-2.4.33-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6209/xorg-x11-drv-ati-6.14.3-5.20120201git36c190671.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6040/util-linux-2.20.1-2.3.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6004/sane-backends-1.0.22-10.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6039/systemd-37-19.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6062/livecd-tools-16.12-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6059/fuse-2.8.7-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-5906/rsyslog-5.8.10-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 The following builds have been pushed to Fedora 16 updates-testing abi-compliance-checker-1.97.4-1.fc16 abrt-2.0.7-3.fc16 cups-1.5.2-9.fc16 dnsperf-1.0.1.0-27.fc16 drupal7-features-1.0-0.5.rc2.fc16 drupal7-token-1.0-1.fc16 emacs-mew-6.5-1.fc16 euca2ools-1.3.2-1.fc16 gnome-color-manager-3.2.3-2.fc16 gogoc-1.2-15.fc16 gridengine-6.2u5p2-7.fc16.3 ibus-hangul-1.4.1-1.fc16 im-chooser-1.5.2.2-1.fc16 jcifs-1.3.17-3.fc16 kde-plasma-yawp-0.4.3-1.fc16 libdrm-2.4.33-1.fc16 libguestfs-1.16.19-1.fc16 newlisp-10.4.0-2.fc16 perl-Dist-Zilla-4.300014-1.fc16 perl-Test-Spec-0.43-1.fc16 python-auth-credential-0.6-1.fc16 python-fedora-0.3.28-1.fc16 python-fedora-0.3.28.1-1.fc16 python-messaging-0.6-1.fc16 python-pivy-0.5.0-3.hg609.fc16 python-rtslib-2.1.fb13-1.fc16 targetcli-2.0rc1.fb11-1.fc16 xorg-x11-drv-ati-6.14.3-5.20120201git36c190671.fc16 ypbind-1.35-2.fc16 zipios++-0.1.5.9-6.fc16 Details about builds: abi-compliance-checker-1.97.4-1.fc16 (FEDORA-2012-6202) An ABI Compliance Checker Update Information: Update to latest upstream release. ChangeLog: * Sun Apr 15 2012 Richard Shaw hobbes1...@gmail.com - 1.97.4-1 - Update to latest upstream release. * Thu Jan 12 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild References: [ 1 ] Bug #813340 - update to 1.97.x https://bugzilla.redhat.com/show_bug.cgi?id=813340 abrt-2.0.7-3.fc16 (FEDORA-2012-6193) Automatic bug detection and reporting tool
Fedora 15 updates-testing report
The following Fedora 15 Security updates need testing: 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-6055/puppet-2.6.16-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6001/gajim-0.15-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6177/gridengine-6.2u5-10.fc15.3 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-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-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/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 abi-compliance-checker-1.97.4-1.fc15 drupal7-features-1.0-0.5.rc2.fc15 drupal7-token-1.0-1.fc15 emacs-mew-6.5-1.fc15 euca2ools-1.3.2-1.fc15 gogoc-1.2-15.fc15 gridengine-6.2u5-10.fc15.3 ibus-hangul-1.4.1-1.fc15 im-chooser-1.5.2.2-1.fc15 kde-plasma-yawp-0.4.3-1.fc15 perl-Test-Spec-0.43-1.fc15 python-fedora-0.3.28-1.fc15 python-fedora-0.3.28.1-1.fc15 Details about builds: abi-compliance-checker-1.97.4-1.fc15 (FEDORA-2012-6218) An ABI Compliance Checker Update Information: Update to latest upstream release. ChangeLog: * Sun Apr 15 2012 Richard Shaw hobbes1...@gmail.com - 1.97.4-1 - Update to latest upstream release. * Thu Jan 12 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild References: [ 1 ] Bug #813340 - update to 1.97.x https://bugzilla.redhat.com/show_bug.cgi?id=813340 drupal7-features-1.0-0.5.rc2.fc15 (FEDORA-2012-6195) Provides feature management for Drupal Update Information: Update to upstream 1.0-rc2 release ChangeLog: * Sat Apr 14 2012 Jared Smith jsm...@fedoraproject.org - 1.0-0.5.rc2 - New upstream rc2 version - Leave the README.txt file in the module directory to avoid a Drupal warning References: [ 1 ] Bug #812517 - drupal7-features-1.0-rc2 is available https://bugzilla.redhat.com/show_bug.cgi?id=812517 drupal7-token-1.0-1.fc15 (FEDORA-2012-6207) Provides a method for site designers to control content presentation Update Information: Updated to 1.0, http://drupal.org/node/1517088. ChangeLog: * Tue Apr 17 2012 Peter Borsa peter.bo...@gmail.com - 1.0-1 - New upstream version.
