Fedora 17 release status: blockers, builds and karma requirements
Hi, folks. It seems about time to send out an overview of the Fedora 17 release status, and what's needed to get us there. We're a long way behind on rolling a release candidate, because there are several unaddressed blockers (accepted and proposed). See the https://fedoraproject.org/wiki/Current_Release_Blockers . Here's a summary of the action needed, to be followed by a bug-by-bug account: The following updates need testing and karma: * https://admin.fedoraproject.org/updates/mesa-8.0.2-7.fc17 * https://admin.fedoraproject.org/updates/FEDORA-2012-7614/mutter-3.4.1-3.fc17 (these two together, especially by users of NVIDIA cards with =64MB VRAM) * https://admin.fedoraproject.org/updates/FEDORA-2012-7398/mysql-connector-java-5.1.17-5.fc17 * https://admin.fedoraproject.org/updates/FEDORA-2012-7648/abrt-2.0.10-3.fc17 * https://admin.fedoraproject.org/updates/glibc-2.15-37.fc17 * https://admin.fedoraproject.org/updates/os-prober-1.52-3.fc17 * https://admin.fedoraproject.org/updates/pam-1.1.5-6.fc17 The following bugs require further information from anyone who can reproduce: * http://bugzilla.redhat.com/show_bug.cgi?id=817037 * http://bugzilla.redhat.com/show_bug.cgi?id=820366 The following bugs require developer attention: * http://bugzilla.redhat.com/show_bug.cgi?id=811242 (NFS experience required) * http://bugzilla.redhat.com/show_bug.cgi?id=819138 (releng only) * http://bugzilla.redhat.com/show_bug.cgi?id=819492 (desktop team, if accepted) Accepted blockers - 1. http://bugzilla.redhat.com/show_bug.cgi?id=809647 - sourcing updates.img from installation repository does not work - this is verified to be fixed in TC4, and the update has appropriate karma to be pushed stable. No action needed 2. http://bugzilla.redhat.com/show_bug.cgi?id=811242 - PXE and repo=nfs or repo=nfsiso freezes installer - this is a very mysterious bug that breaks PXE installs via NFS. It doesn't seem to be a straightforward bug in anaconda; it seems to be to do with NFS. The latest information we have is that it only affects NFSv4; a test with NFSv3 seems to succeed. Any input from developers with experience with NFS would help. 3. http://bugzilla.redhat.com/show_bug.cgi?id=770197 - Gnome Shell corrupted on nVidia cards with low VRAM - an update to fix this has been submitted, https://admin.fedoraproject.org/updates/mesa-8.0.2-7.fc17 . Note that you also will need https://admin.fedoraproject.org/updates/FEDORA-2012-7614/mutter-3.4.1-3.fc17 for a full test. We need people with NVIDIA adapters with 64MB or less of VRAM to test if they can use Shell successfully with those two updates installed, and provide positive karma on the updates if so. 4. http://bugzilla.redhat.com/show_bug.cgi?id=755335 - Shutting down while auto-updating breaks the system - we have an update that works around this, https://admin.fedoraproject.org/updates/gnome-settings-daemon-3.4.1-4.fc17 . It is verified to fix the bug and has appropriate karma to be pushed stable. No action is needed. 5. http://bugzilla.redhat.com/show_bug.cgi?id=809111 - grub2-probe fails during install - the TC4 anaconda update, https://admin.fedoraproject.org/updates/FEDORA-2012-7623/anaconda-17.26-1.fc17 , is reported to fix this and has appropriate karma to be pushed stable. No action is needed. 6. http://bugzilla.redhat.com/show_bug.cgi?id=818378 - grub2 can't install because /proc/device-tree exists - an update to fix this, https://admin.fedoraproject.org/updates/FEDORA-2012-7531/kernel-3.3.4-5.fc17 , was pulled into TC4 and confirmed to fix it. It has appropriate karma to go stable. No action is needed. 7. https://bugzilla.redhat.com/show_bug.cgi?id=819139 - repoclosure failure on 17.TC4 DVDs (mysql-connector-java) - we have an update that should fix this once it's pushed stable (just pulling it via a side repo isn't enough, for dull reasons that aren't worth explaining). The update, https://admin.fedoraproject.org/updates/FEDORA-2012-7398/mysql-connector-java-5.1.17-5.fc17 , needs one more karma point. Obviously it'd be best if someone who actually connects MySQL with Java can test and see if it still works, but two of us have +1ed it on the basis that it at least resolves the dependency problem, and it'd be fine to have one more +1 on this basis. 8. http://bugzilla.redhat.com/show_bug.cgi?id=819138 - repoclosure failure on 17.TC4 DVDs (eclipse) - this is an annoying problem with Java dependencies, which dgilmore thought he could fix in TC4 but his idea didn't work. It's purely a compose issue, really, so we need dgilmore to figure this one out for the TC5/RC1 compose. Proposed blockers - All of these will be reviewed at the blocker meeting tomorrow. Please attend if you have any interest. 1. http://bugzilla.redhat.com/show_bug.cgi?id=819113 - abrt-ccpp service not enabled by default on F17 - there is a fix for this which I have verified to work. It needs karma:
Nomodeset in grub
I noticed, that as soon as grub comes up in graphical mode, the nomodeset boot option has no effect in F17. Is this a bug or a feature or is there a new option I am not aware off? Koos. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fftw-libs
On Fri, May 11, 2012 at 3:42 AM, Jayson Rowe jayson.r...@gmail.com wrote: Sorry for taking so long to reply - it's been a busy, busy day. On Thu, May 10, 2012 at 08:57:15PM +0200, Thomas Spura wrote: fftw changed the package structure completely and is now currently being pushed to stable: https://admin.fedoraproject.org/updates/FEDORA-2012-6879/python-anfft-0.1-4.fc17,fftw-3.3.1-3.fc17 In this case you definitely don't need to uninstall fftw, just wait, till it's in the normal updates repo and you won't see this again with 'yum distro-sync'. It's actually a little too late for that - i uninstalled it from both machines this morning. Now, if I try to re-install, I get this: Why do you want to reinstall fftw, when you don't need it? ;) You could try to reinstall fftw-libs, as that was always there, the -quad, -double, -single packages are all new and only available, when updates-testing is available. nsaction Check Error: file /usr/lib64/libfftw3q.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-quad-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-double-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3l.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-long-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3f.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-single-3.3.1-3.fc17.x86_64 If I try to reinstall those packages it tells me: [jayson@desktop ~]$ sudo yum reinstall fftw-libs-quad fftw-libs-double fftw-libs-single fftw-libs-long [sudo] password for jayson: Loaded plugins: langpacks, presto, refresh-packagekit Installed package fftw-libs-quad-3.3.1-3.fc17.x86_64 (from updates-testing) not available. Installed package fftw-libs-double-3.3.1-3.fc17.x86_64 (from updates-testing) not available. Installed package fftw-libs-single-3.3.1-3.fc17.x86_64 (from updates-testing) not available. Installed package fftw-libs-long-3.3.1-3.fc17.x86_64 (from updates-testing) not available. Error: Nothing to do See above. Those packages are only in updates-testing. You cannot install those with updates-testing disabled. ...and if I try to remove them, there are a ton of dependancies to be removed. Not sure what to do at this point. Wait, till fftw makes it to the proper updates repository (will happen in the next push) or try to reinstall fftw-libs only. I'm really hoping I haven't borked my installs. I'm pretty new to Fedora - I'm an Ubuntu refugee. I felt pretty comfortable with Yum having used CentOS extensively on servers, and I was a RH/FC user through FC2 before going to Ubuntu. I've never run a beta release of Fedora. Until now, I've had ZERO issues... I'd wouldn't call this a big issue too ;) Things like this can happen, when you suddently disable updates-testing. Sometimes a yum clean metadata all is needed and anything works fine again :) Greetings, Tom -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automount (autofs) not working (F17)
On 11/05/12 04:22, Braden McDaniel wrote: +auto.master /home auto.home /- auto.direct $ cat /etc/auto.home * -fstype=nfs4rail:/home/ $ cat /etc/auto.direct /share -fstype=nfs4rail:/share This identical configuration is working just fine on a Fedora 16 box. On my Fedora 17 prerelease installation (currently using autofs-5.0.6-13.fc17), it does not work at all. Just a side note: It seems to work for me on f17 (with unchanged config) for cifs-filesystems. I'm seeing here many nfs4 mounts. It may be related to some kerberos change? sssd? -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fftw-libs
On Fri, May 11, 2012 at 08:40:03AM +0200, Thomas Spura wrote: Why do you want to reinstall fftw, when you don't need it? ;) I'm not sure...I guess because it was there before? You could try to reinstall fftw-libs, as that was always there, the -quad, -double, -single packages are all new and only available, when updates-testing is available. It *was* the fftw-libs package I was trying to reinstall when I get the below messages... nsaction Check Error: file /usr/lib64/libfftw3q.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-quad-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-double-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3l.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-long-3.3.1-3.fc17.x86_64 file /usr/lib64/libfftw3f.so.3 from install of fftw-libs-3.3-4.fc17.x86_64 conflicts with file from package fftw-libs-single-3.3.1-3.fc17.x86_64 I'd wouldn't call this a big issue too ;) Me either - I'm very happy with Fedora overall :-) Things like this can happen, when you suddently disable updates-testing. Sometimes a yum clean metadata all is needed and anything works fine again :) I did try the yum clean metadata all. I'm just a worry-wart. As long as everything keeps working, I'll just not worry about it :-) Thanks for your help and time. Jayson -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
GRUB2 doesn't respect the changes made to /etc/default/grub
I am using F17 TC2 and I added few lines to /etc/default/grub. My config is GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=Fedora GRUB_DEFAULT=saved GRUB_SAVEDEFAULT=true GRUB_CMDLINE_LINUX=rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 quiet pci=nomsi noapic irqpoll #GRUB_BACKGROUND=/boot/danbo_cold_evening-wallpaper-1680x1050.jpg GRUB_DISABLE_RECOVERY=true Initially I wanted to add background which was not taken up after I did grub2-mkconfig -o /boot/grub2/grub.cfg. But then I commented it out. later i tried disabling recovery, which was also not updated. I tried in fedoraforums.org . No one seems to know why. http://forums.fedoraforum.org/showthread.php?t=279615 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-17 Branched report: 20120511 changes
Compose started at Fri May 11 08:15:04 UTC 2012 Broken deps for x86_64 -- [LuxRender] LuxRender-blender-0.8.0-13.fc17.x86_64 requires blender(ABI) = 0:2.61 [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires rubygem(fastercsv) 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 [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(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 [gnome-do-plugins] gnome-do-plugins-banshee-0.8.4-8.fc17.x86_64 requires mono(Banshee.CollectionIndexer) = 0:2.2.0.0 [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) [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-sqlite-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-sqlite-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) [mcollective] mcollective-common-1.3.1-7.fc17.noarch requires ruby(abi) = 0:1.8 [moksha] moksha-0.5.0-5.fc15.noarch requires pyevent [natus] libnatus-V8-0.1.5-2.fc15.x86_64 requires libv8-3.0.0.1.so()(64bit) [ocaml-augeas] ocaml-augeas-0.4-9.fc15.x86_64 requires ocaml(runtime) = 0:3.12.0 [openvrml] libopenvrml-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires java-1.6.0-openjdk(x86-64) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-xembed-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-xembed-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit)
Re: obsolete http://fedoraproject.org/wiki/Anaconda_Boot_Options
On Thu, May 10, 2012 at 06:35:52 -0700, Adam Williamson awill...@redhat.com wrote: Old habits die hard. I have to admit I never use ip either. I found it useful for cases where I needed to have multiple layer 3 networks on the same layer 2 network segment. For example when playing with wireless routers. It is a lot easier to add another network to an inferface using ip addr then playing with the high level network config tools. Particularly when the changes are meant to be short lived. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automount (autofs) not working (F17)
On Fri, 2012-05-11 at 09:05 +0200, Matthias Runge wrote: On 11/05/12 04:22, Braden McDaniel wrote: +auto.master /home auto.home /- auto.direct $ cat /etc/auto.home * -fstype=nfs4rail:/home/ $ cat /etc/auto.direct /share -fstype=nfs4rail:/share This identical configuration is working just fine on a Fedora 16 box. On my Fedora 17 prerelease installation (currently using autofs-5.0.6-13.fc17), it does not work at all. Just a side note: It seems to work for me on f17 (with unchanged config) for cifs-filesystems. I'm seeing here many nfs4 mounts. It may be related to some kerberos change? sssd? I use kerberos and sssd; but not to authenticate the NFS mounts. Here's the server's /etc/exports: $ cat /etc/exports /export 10.0.0.0/255.255.255.0(rw,insecure,no_subtree_check,nohide,fsid=0) /export/home 10.0.0.0/255.255.255.0(rw,insecure,sync,no_subtree_check,nohide) /export/share 10.0.0.0/255.255.255.0(rw,insecure,no_subtree_check,nohide) -- Braden McDaniel bra...@endoframe.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20120511 changes
Compose started at Fri May 11 08:15:02 UTC 2012 Broken deps for x86_64 -- [389-admin] 389-admin-1.1.28-1.fc18.i686 requires libicuuc.so.48 389-admin-1.1.28-1.fc18.i686 requires libicui18n.so.48 389-admin-1.1.28-1.fc18.i686 requires libicudata.so.48 389-admin-1.1.28-1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicudata.so.48()(64bit) [389-adminutil] 389-adminutil-1.1.15-2.fc17.i686 requires libicuuc.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicui18n.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicudata.so.48 389-adminutil-1.1.15-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicudata.so.48()(64bit) [389-dsgw] 389-dsgw-1.1.9-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicudata.so.48()(64bit) [TnL] TnL-07-19.fc18.x86_64 requires libiovmall.so.2()(64bit) [aeolus-all] aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-doc = 0:0.4.0-2.fc17 aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-daemons = 0:0.4.0-2.fc17 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [bibletime] bibletime-2.9.1-1.fc18.x86_64 requires libicuuc.so.48()(64bit) bibletime-2.9.1-1.fc18.x86_64 requires libicui18n.so.48()(64bit) [boost141] boost141-graph-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-graph-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-graph-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-graph-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) boost141-regex-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-regex-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-regex-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-regex-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) [couchdb] couchdb-1.1.1-1.fc18.x86_64 requires libicuuc.so.48()(64bit) couchdb-1.1.1-1.fc18.x86_64 requires libicui18n.so.48()(64bit) couchdb-1.1.1-1.fc18.x86_64 requires libicudata.so.48()(64bit) [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [evolution-couchdb] evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-cal-1.2.so.15()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-book-1.2.so.13()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libecal-1.2.so.11()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [evolution-rss] 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libedataserverui-3.0.so.1()(64bit) 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python2-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 [ghc-wai-extra] ghc-wai-extra-0.4.6-3.fc18.i686 requires libHSzlib-enum-0.2.1-ghc7.4.1.so ghc-wai-extra-0.4.6-3.fc18.i686 requires libHSzlib-bindings-0.0.3.2-ghc7.4.1.so ghc-wai-extra-0.4.6-3.fc18.i686 requires ghc(zlib-enum-0.2.1-55af94f47edaf6ddd74e441a7a34ef7e) ghc-wai-extra-0.4.6-3.fc18.i686 requires ghc(zlib-bindings-0.0.3.2-3d82a54b78146286e86c5a9fa9085ef2) ghc-wai-extra-0.4.6-3.fc18.x86_64 requires libHSzlib-enum-0.2.1-ghc7.4.1.so()(64bit) ghc-wai-extra-0.4.6-3.fc18.x86_64 requires libHSzlib-bindings-0.0.3.2-ghc7.4.1.so()(64bit) ghc-wai-extra-0.4.6-3.fc18.x86_64 requires ghc(zlib-enum-0.2.1-6264df6f05d62c31c73f13219fe69f53) ghc-wai-extra-0.4.6-3.fc18.x86_64 requires ghc(zlib-bindings-0.0.3.2-d83646b762e4c3d5f1dcf4b8665bb1c5) ghc-wai-extra-devel-0.4.6-3.fc18.i686 requires ghc-devel(zlib-enum-0.2.1-55af94f47edaf6ddd74e441a7a34ef7e) ghc-wai-extra-devel-0.4.6-3.fc18.i686 requires ghc-devel(zlib-bindings-0.0.3.2-3d82a54b78146286e86c5a9fa9085ef2) ghc-wai-extra-devel-0.4.6-3.fc18.x86_64 requires ghc-devel(zlib-enum-0.2.1-6264df6f05d62c31c73f13219fe69f53) ghc-wai-extra-devel-0.4.6-3.fc18.x86_64 requires ghc-devel(zlib-bindings-0.0.3.2-d83646b762e4c3d5f1dcf4b8665bb1c5)
Re: Nomodeset in grub
On 5/11/12 2:35 AM, A.J. Werkman wrote: I noticed, that as soon as grub comes up in graphical mode, the nomodeset boot option has no effect in F17. Is this a bug or a feature or is there a new option I am not aware off? You're going to need to be more specific than that. The kernel definitely still honors the nomodeset boot argument. - ajax -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2012-05-11 @ 17:00 UTC - F17 Final Blocker Bug Review #5
== #fedora-bugzappers: f17-final-blocker-review-meeting-5 == We were able to get through all of the proposed blockers but didn't get to the accepted blockers or proposed NTH. I will be scheduling another review meeting for early next week (probably Monday) to finish going over the remaining bugs. Minutes: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-05-11/f17-final-blocker-review-meeting-5.2012-05-11-17.04.html Minutes (text): http://meetbot.fedoraproject.org/fedora-bugzappers/2012-05-11/f17-final-blocker-review-meeting-5.2012-05-11-17.04.txt Log: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-05-11/f17-final-blocker-review-meeting-5.2012-05-11-17.04.log.html Meeting summary --- * roll call (tflink, 17:04:49) * Introduction (tflink, 17:15:59) * Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (tflink, 17:16:12) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 17:16:32) * LINK: https://fedoraproject.org/wiki/Current_Release_Blockers (tflink, 17:16:32) * LINK: https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria (tflink, 17:16:34) * LINK: https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria (tflink, 17:16:36) * LINK: https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria (tflink, 17:16:39) * (821015) Software Update claims all packages are untrusted (tflink, 17:18:28) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=821015 (tflink, 17:18:28) * Proposed Blocker, MODIFIED (tflink, 17:18:28) * AGREED: - 821015 - AcceptedBlocker - Violates the F17 alpha release criterion The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops for systems where the user doesn't have the root password (tflink, 17:26:38) * (819113) abrt-ccpp service not enabled by default on F17 (tflink, 17:26:53) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=819113 (tflink, 17:26:53) * Proposed Blocker, VERIFIED (tflink, 17:26:53) * AGREED: - RejectedBlocker, AcceptedNTH - While this doesn't hit any of the release criteria, losing crash reports is not something that we want to be doing and would take a well tested fix (tflink, 17:30:48) * according to the author, this fix has been in F16 stable for some time now (tflink, 17:31:12) * (813548) alsa bug makes kernel kill pulseaudio sometimes (tflink, 17:31:27) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=813548 (tflink, 17:31:27) * Proposed Blocker, NEW (tflink, 17:31:27) * AGREED: 813548 - RejectedBlocker - While somewhat ugly, this bug seems to be a corner case that only affects a few users and would be fixable with an update for installed systems. (tflink, 17:37:00) * (816742) Installer in EFI mode needs to use grub2 and allow /boot on LVM (tflink, 17:37:12) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=816742 (tflink, 17:37:15) * Proposed Blocker, NEW (tflink, 17:37:17) * AGREED: - 816742 - RejectedBlocker, RejectedNTH - This doesn't hit any of the release criteria - it is well known that grub2-efi is not ready for use. No NTH because it is too late to take grub changes that aren't accepted as blockers (tflink, 17:42:08) * (817037) Installer damage Disks (tflink, 17:42:20) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=817037 (tflink, 17:42:21) * Proposed Blocker, NEW (tflink, 17:42:21) * AGREED: - 817037 - RejectedBlocker, RejectedNTH - There is no clear reproducer and it is not clear that this isn't expected behavior (autopart with 'use all space' is supposed to clear off all disks') (tflink, 17:46:50) * (820366) Cannot boot 17 Beta installer: /dev/root does not exist (tflink, 17:47:04) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=820366 (tflink, 17:47:08) * Proposed Blocker, NEW (tflink, 17:47:10) * AGREED: - 820366 - There is not enough information to decide on whether or not this is actually a blocker - ask for more information and more re-testing of PXE and ks delivery over nfs (tflink, 17:54:06) * (813648) gnome-shell shows blank windows on hardware lacking NPOT textures (tflink, 17:54:21) * LINK: http://bugzilla.redhat.com/show_bug.cgi?id=813648 (tflink, 17:54:24) * Proposed Blocker, MODIFIED (tflink, 17:54:26) * AGREED: - 813648 - AcceptedNTH - This is a graphical issue that would affect a minority of users - there is unclear cosensus on whether or not this is enough to be a final blocker (can't fix livecds with an update) but enough for NTH. (tflink,
Nice-to-have
Hello... This is a bug that has been around since the very biginning of F17, and it is still here... It is NOT life-threathening or a crasher of any sort, but it is irritating nevertheless... Here it is... [root@RockingRobin metacity-1]# gedit metacity-theme-3.xml (gedit:1987): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.AVF4DW': No such file or directory (gedit:1987): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory ** (gedit:1987): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed (gedit:1987): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.SM2MDW': No such file or directory (gedit:1987): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory (gedit:1987): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.VBKPDW': No such file or directory (gedit:1987): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory -- Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nice-to-have
On Fri, 2012-05-11 at 21:58 -0700, Rob Healey wrote: Hello... This is a bug that has been around since the very biginning of F17, and it is still here... It is NOT life-threathening or a crasher of any sort, but it is irritating nevertheless... One of the key definitions of an NTH bug is that it can't be fixed with an update - i.e. there's a reason the fix needs to be baked into the media. If it can be fixed with an update there's no real reason to bring it through the freeze. So I don't think this would constitute an NTH bug. Remember, NTH bugs are bugs sufficiently important to break the release freeze for, so it's a pretty high bar. 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
