Re: F17 self-built boot.iso queries
On Sun, May 13, 2012 at 3:56 AM, Amit Saha amitks...@fedoraproject.org wrote: On Thu, May 10, 2012 at 10:33 AM, Amit Saha amitks...@fedoraproject.org wrote: On Thu, May 10, 2012 at 9:58 AM, Adam Williamson awill...@redhat.com wrote: On Thu, 2012-05-10 at 09:46 +0530, Amit Saha wrote: On Tue, May 8, 2012 at 8:44 PM, Adam Williamson awill...@redhat.com wrote: On Tue, 2012-05-08 at 13:54 +0530, Amit Saha wrote: On Tue, May 8, 2012 at 11:35 AM, Adam Williamson awill...@redhat.com wrote: On Tue, 2012-05-08 at 07:48 +0530, Amit Saha wrote: Here is the screenshot of the screen [1]. I was hoping to work around it to do a fresh install by clicking on Continue Install, but from what I remember now, the Installer crashed, and I attempted to save the logs, for which it attempted to connect to the Network, but which never succeeded. I shall attempt to try this again and retrieve more information. [1] https://twitter.com/#!/echorand/status/199682569703407616/photo/1/large Ah. 'product mismatch' there means you had a 32-bit system installed and booted the 64-bit installer, or vice versa, I believe. The installer crash may well not have been related, but if you couldn't save logs, it's difficult to tell. :/ It would be interesting to know if you can recreate the failure by doing the same thing again. Please find a screenshot of the exception/bug [1] when I click on the Continue button after the previous error dialog box. Sorry, but once again I tried to save the log and the network configuration step didn't quite work. (That's probably another investigation required). It seems like a Dbus exception. You should be able to get a copy of the traceback and logs from /tmp if you go to the ctrl-alt-f2 console when you hit the error. You can just copy them to a manually-mounted USB stick, or bring up the network manually and fpaste them out, I guess. Thanks. Here is the anaconda.log [1]. I have the other logs saved as well. Please let me know if you would like to take a look at any other file. [1] https://gist.github.com/2650996 Hope it helps you in tracking the problem. Can you file a bug against anaconda, and attach all the logs? Thanks! Done [1]. https://bugzilla.redhat.com/show_bug.cgi?id=820467 was closed citing that dbus may not have been installed correctly or is not running. Any idea how I can find that out? I built a boot.iso again and the installer crashes with the same exception. Also, I see towards building the boot.iso: code .. rebuilding boot/initramfs-3.3.4-4.fc17.i686.img E: Dracut module anaconda cannot be found. E: Dracut module nfs cannot be found. E: Dracut module nfs cannot be found. E: Dracut module anaconda cannot be found. E: Dracut module nfs cannot be found. E: Dracut module nfs cannot be found. rebuilding boot/initramfs-3.3.4-4.fc17.i686.PAE.img E: Dracut module anaconda cannot be found. E: Dracut module nfs cannot be found. E: Dracut module nfs cannot be found. E: Dracut module anaconda cannot be found. E: Dracut module nfs cannot be found. E: Dracut module nfs cannot be found. .. /code Is this ignnorable or should I be checking something? I disabled SElinux on the build machine and the problem disappeared. Best, Amit -- http://echorand.me -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: abrt backtrace failures
On 05/23/2012 06:06 AM, Chuck Anderson wrote: During F17 RC testing, twice now [1][2] I've been unable to submit bugs using abrt because the backtrace was considered unusable by abrt. 1. Is there a problem with the debuginfo's or abrt functionality during this F17 final RC stage? 2. What happened to the Retrace Server? I don't see that option for F17, only Local GNU Debugger. This is caused by: https://bugzilla.redhat.com/show_bug.cgi?id=823812 You can just yum install abrt-retrace-client to get it back. 3. Can the abrt behavior be changed to allow the bug to be created, but perhaps without the bad backtrace, or perhaps marked in some way so it is known to have a bad backtrace? - right now ABRT uses a scale 1-4 to rate the backtrace and allows only 3 and 4 to be reported - we're thinking about adding a possibility to create the whole bug manually like in the web interface only it would be easier (using some kind of wizard probably) It is still helpful to the bug reporter to have abrt create the bug with as much info as possible, with the expectation that better/usable backtraces could be attached later manually if possible. - when ABRT finds a dupe in bugzilla it checks the quality of the attached backtrace and if the one being reported is better it attaches it - so this part is done - but on the other hand developer won't start working on a bug before he gets a good backtrace, so I think it's better to wait for a good one and then create the ticket rather than creating a ticket and waiting for a good backtrace - in that case the bug might go out of the developer's radar.. It is frustrating to be informed of a crash by abrt and go through all the effort to submit the bug report via abrt, only to be told sorry, I'm not going to let you submit this bug report because it doesn't meet our standards of quality. Frankly, it's a waste of the reporter's time and it conditions the user to not care to submit bugs in the future. - I totally agree, but please be patient. We're trying to make the whole process less painful. There are already few ongoing projects trying to deal with it like minidebuginfo and ABRT server (not the retrace server) Cheers, Jirka Thanks, Chuck [1] https://bugzilla.redhat.com/show_bug.cgi?id=823755 [2] https://bugzilla.redhat.com/show_bug.cgi?id=824228 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-17 Branched report: 20120524 changes
Compose started at Thu May 24 08:15:05 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 [calf] lv2-calf-plugins-0.0.18.6-6.fc17.x86_64 requires lv2core [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [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) [lilv] lilv-devel-0.5.0-3.fc17.i686 requires pkgconfig(lv2core) lilv-devel-0.5.0-3.fc17.x86_64 requires pkgconfig(lv2core) [lv2-EQ10Q-plugins] lv2-EQ10Q-plugins-1.0-10.fc17.x86_64 requires lv2core [lv2-abGate] lv2-abGate-1.1.3-4.fc17.x86_64 requires lv2core [lv2-avw-plugins] lv2-avw-plugins-0.0.6-3.fc17.x86_64 requires lv2core [lv2-fil-plugins] lv2-fil-plugins-2.0-5.fc17.x86_64 requires lv2core [lv2-invada-plugins] lv2-invada-plugins-1.2.0-6.fc17.x86_64 requires lv2core [lv2-kn0ck0ut] lv2-kn0ck0ut-1.1-0.4.git60421a3.fc17.x86_64 requires lv2core [lv2-ll-plugins] lv2-ll-plugins-0.2.8-9.fc17.x86_64 requires lv2core [lv2-mdaEPiano] lv2-mdaEPiano-0-0.2.git9db45842.fc17.x86_64 requires lv2core [lv2-swh-plugins] lv2-swh-plugins-1.0.15-7.20110510.9c9935egit.fc17.x86_64 requires lv2core [lv2-vocoder-plugins] lv2-vocoder-plugins-1-4.fc17.x86_64 requires lv2core [lv2-zynadd-plugins] lv2-zynadd-plugins-1-6.fc17.x86_64 requires lv2core [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)
Re: dracut kernel-panci
On 23/05/12 16:27, Harald Hoyer wrote: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) this means there was no initramfs even loaded check your bootloader config and the existence of the initramfs image This is what happens when manually trying to create initramfs: dracut initramfs-3.5.0-0.rc0.git3.1.fc18.i686.img kernel-3.5.0-0.rc0.git3.1.fc18.i686 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory F: installkernel failed in module kernel-modules I even installed kernel-modules-extra in case of something there. There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/* -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dracut kernel-panci
On Thu, May 24, 2012 at 7:10 AM, Frank Murphy frankl...@gmail.com wrote: On 23/05/12 16:27, Harald Hoyer wrote: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) this means there was no initramfs even loaded check your bootloader config and the existence of the initramfs image This is what happens when manually trying to create initramfs: dracut initramfs-3.5.0-0.rc0.git3.1.fc18.i686.img kernel-3.5.0-0.rc0.git3.1.fc18.i686 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory F: installkernel failed in module kernel-modules I even installed kernel-modules-extra in case of something there. There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/* Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64? josh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dracut kernel-panci
On 24/05/12 12:53, Josh Boyer wrote: There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/* Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64? josh Apologies, it happens on both 32 and 64. -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dracut kernel-panci
On 24/05/12 12:53, Josh Boyer wrote: Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64? josh Put up some more info: http://frankly3d.eu/kernel-error -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
New BugZapper Introduction
Hello Folks, I am Bckurera (Buddhike) and I am working with some Fedora teams(FAms, Design, Marketing, etc..) and I would like to join with the Bug Zappers Team as well. I am not a geek but would like to join with the some technical work as well. My userpage[1] contains more info please refer to that if anyone seeks more info. I ll start studying the work and contribute as time permits, thanks and see you all around ! [1] http://fedoraproject.org/wiki/User:Bckurera -- Regards, Buddhike Chandradeepa Kurera(bckurera) Fedora Ambassador - APAC region Event Liaison - Design Team Email: bckur...@fedoraproject.org | IRC: bckurera -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dracut kernel-panci
On Thu, May 24, 2012 at 9:08 AM, Frank Murphy frankl...@gmail.com wrote: On 24/05/12 12:53, Josh Boyer wrote: Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64? josh Put up some more info: http://frankly3d.eu/kernel-error dracut initramfs-3.5.0-0.rc0.git3.1.fc18.x86_64 kernel-3.5.0-0.rc0.git3.1.fc18.x86_64 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory F: installkernel failed in module kernel-modules ls -R frank@test08 ~$ su - Password: [root@test08 ~]# ls -R /usr/lib/modules/3.5.0-0.rc0.git3.1.fc18.x86_64 Look closely. You're telling dracut the kernel version is 'kernel-3.5.0' and it takes that very literally. Remove the 'kernel-' prefix and just use '3.5.0-0.rc0.git3.1.fc18.x86_64'. None of that explains why there is no initramfs being created from the kernel update itself though. If you yum update to today's rawhide kernel, is one created? josh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20120524 changes
Compose started at Thu May 24 08:15:03 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) [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 [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) [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) [fawkes] fawkes-plugin-xmlrpc-0.4.2-10.fc18.x86_64 requires libxmlrpc_server++.so.7()(64bit) fawkes-plugin-xmlrpc-0.4.2-10.fc18.x86_64 requires libxmlrpc++.so.7()(64bit) [gambas2] gambas2-gb-pdf-2.23.1-10.fc18.x86_64 requires libpoppler.so.19()(64bit) [gambas3] gambas3-gb-pdf-3.1.1-2.fc18.x86_64 requires libpoppler.so.19()(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 [gdb-heap] gdb-heap-0.5-8.fc17.x86_64 requires glibc(x86-64) = 0:2.15 [ghc-warp] ghc-warp-0.4.6.3-3.fc18.i686 requires libHSwai-0.4.3-ghc7.4.1.so ghc-warp-0.4.6.3-3.fc18.i686 requires ghc(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-0.4.6.3-3.fc18.x86_64 requires libHSwai-0.4.3-ghc7.4.1.so()(64bit) ghc-warp-0.4.6.3-3.fc18.x86_64 requires ghc(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) ghc-warp-devel-0.4.6.3-3.fc18.i686 requires ghc-devel(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-devel-0.4.6.3-3.fc18.x86_64 requires ghc-devel(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) [gnome-pilot] gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserverui-3.0.so.1()(64bit) gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [gnome-python2-desktop] gnome-python2-evolution-2.32.0-9.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [inkscape] inkscape-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) inkscape-view-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) [koji] koji-hub-1.6.0-3.fc17.noarch requires mod_python koji-web-1.6.0-3.fc17.noarch requires mod_python [mapnik] mapnik-2.0.0-4.fc17.i686 requires libicuuc.so.48 mapnik-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit)
Re: dracut kernel-panci
On 24/05/12 14:27, Josh Boyer wrote: On Thu, May 24, 2012 at 9:08 AM, Frank Murphyfrankl...@gmail.com wrote: snipped Look closely. You're telling dracut the kernel version is 'kernel-3.5.0' and it takes that very literally. Remove the 'kernel-' prefix and just use '3.5.0-0.rc0.git3.1.fc18.x86_64'. After removing prefix: ]# dracut initramfs-3.5.0-0.rc0.git3.1.fc18.x86_64 3.5.0-0.rc0.git3.1.fc18.x86_64 F: installkernel failed in module multipat # rpm -qa | grep multipath device-mapper-multipath-libs-0.4.9-22.fc18.x86_64 device-mapper-multipath-0.4.9-22.fc18.x86_64 None of that explains why there is no initramfs being created from the kernel update itself though. If you yum update to today's rawhide kernel, is one created? Today's kernel-3.5.0-0.rc0.git5.1.fc18 no auto initramfs, also same manual fail multipath -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: prevent anaconda start
On Thu, 2012-05-24 at 00:40 -0400, Felix Miata wrote: On 2012/05/23 18:45 (GMT-0700) Adam Williamson composed: On Wed, 2012-05-23 at 20:48 -0400, Felix Miata wrote: Intel 865 gfxchip. No idea whether this result is intentional or not, but I put a 3 on end of Grub cmdline to start an HTTP installation of F17 from a mirror. After the installation system downloaded, I got login prompts on most ttys, and no Anaconda anywhere, text or GUI. Well, that seems rather expected. If you want a text mode install, use the option on the boot menu or pass parameter 'text'. I wasn't looking for a text mode install. The 3 was just a habit from normal booting. For openSUSE and Mandriva/Mageia installation (and IIRC *buntu's and maybe even Debian's), including it will cause their installation programs to also include the 3 in the Grub menu stanzas, but have no effect on the installation process itself. Having it totally prevent any kind of installation initialization having booted an installation kernel and initrd to me is completely unexpected. Well, 3 gets interpreted by systemd as 'boot to runlevel 3 equivalent', so you get a text mode boot. But nothing told anaconda to start up in text mode. So you just get...not much. You can't really assume that how it behaves on another distro is how it'll behave on Fedora, unless it's written down somewhere, and I don't recall ever seeing that. It's a bit of a 'doctor it hurts', I think... -- 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-presto to get multicore support
On 05/22/2012 05:45 AM, Andre Robatino wrote: For some people with fast connections/slow PCs, using deltarpms via yum-presto can be slower than downloading the full RPMs. Jonathan Dieter just did a Rawhide build (yum-presto-0.8.0-1.fc18) that adds multicore support to yum-presto. Would be interested if people would note what rebuild speed they get before and after updating to this version, and if the speedup is close to linear. My experience is that rebuilding drpms is CPU-bound so there's a good chance it will be. Excellent! I'm one of those people who have been removing yum-presto for exactly the reason that you describe (40Mbps connection, 4-core SandyBridge CPU). Would love to test this out. Can we a F17 build? -- 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: dracut kernel-panci
On 23/05/12 10:17, Frank Murphy wrote: Anyone else have a kernel-panic with initramfs created by: dracut-018-74.git20120522.fc18 Can't get anywhere myself so: https://bugzilla.redhat.com/show_bug.cgi?id=824981 -- Regards, Frank Jack of all, fubars -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: prevent anaconda start
On 2012/05/24 09:24 (GMT-0700) Adam Williamson composed: On Thu, 2012-05-24 at 00:40 -0400, Felix Miata wrote: On 2012/05/23 18:45 (GMT-0700) Adam Williamson composed: On Wed, 2012-05-23 at 20:48 -0400, Felix Miata wrote: Intel 865 gfxchip. No idea whether this result is intentional or not, but I put a 3 on end of Grub cmdline to start an HTTP installation of F17 from a mirror. After the installation system downloaded, I got login prompts on most ttys, and no Anaconda anywhere, text or GUI. Well, that seems rather expected. If you want a text mode install, use the option on the boot menu or pass parameter 'text'. I wasn't looking for a text mode install. The 3 was just a habit from normal booting. For openSUSE and Mandriva/Mageia installation (and IIRC *buntu's and maybe even Debian's), including it will cause their installation programs to also include the 3 in the Grub menu stanzas, but have no effect on the installation process itself. Having it totally prevent any kind of installation initialization having booted an installation kernel and initrd to me is completely unexpected. Well, 3 gets interpreted by systemd as 'boot to runlevel 3 equivalent', so you get a text mode boot. But nothing told anaconda to start up in text mode. So you just get...not much. You can't really assume that how it behaves on another distro is how it'll behave on Fedora, unless it's written down somewhere, and I don't recall ever seeing that. It's a bit of a 'doctor it hurts', I think... I think too. I just looked through over a dozen Grub menus containing Rawhide installation stanzas, and found none containing a 3 on a Rawhide kernel line, so likely I've never before tried it with Fedora. Nevertheless, some people who ever use X don't habitually use runlevel 3 to get there, and I think it may be a shortcoming that an installation kernel and initrd may care in the usual sense about runlevels or would fail to initialize their primary purpose for existence just because a runlevel 5 state had not been reached. Maybe it's purposeful, maybe not. I brought it up here instead of Bugzilla purely to try to flesh out whether it may be good, bad, or don't care. IMO, an installation set should start the installation process in any event in which something specifically designed to thwart it has not been interposed. I don't think a 3 on cmdline should qualify as such. A standalone 3 could easily be an inadvertent result of a mistyped and unnoticed 192.168.0.133 or 192.168.1.13. -- 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
Fedora 15 updates-testing report
The following Fedora 15 Security updates need testing: https://admin.fedoraproject.org/updates/FEDORA-2012-8114/libreoffice-3.3.4.1-5.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-7567/php-5.3.13-1.fc15,maniadrive-1.2-32.fc15.5,php-eaccelerator-0.9.6.1-9.fc15.5 https://admin.fedoraproject.org/updates/FEDORA-2012-8161/ikiwiki-3.2006-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8205/python-tornado-2.2.1-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6630/dokuwiki-0-0.10.20110525.a.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-7246/libsoup-2.34.3-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6629/gdb-7.3.1-50.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8339/rt3-3.8.12-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8360/drupal7-7.14-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8365/moodle-1.9.18-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8372/kernel-2.6.43.7-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2011-17233/tor-0.2.1.32-1500.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8024/openssl-1.0.0j-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-7131/seamonkey-2.9.1-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8041/xinetd-2.3.14-37.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8010/sudo-1.7.4p5-5.fc15 The following Fedora 15 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/FEDORA-2012-8372/kernel-2.6.43.7-1.fc15 https://admin.fedoraproject.org/updates/iproute-2.6.38.1-7.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8206/mdadm-3.2.5-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8027/libogg-1.3.0-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8010/sudo-1.7.4p5-5.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-8024/openssl-1.0.0j-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-7909/perl-5.12.4-166.fc15 https://admin.fedoraproject.org/updates/dracut-009-15.fc15 The following builds have been pushed to Fedora 15 updates-testing ATpy-0.9.6-1.fc15 CGSI-gSOAP-1.3.5-2.fc15 Zim-0.56-2.fc15 abrt-2.0.3-7.fc15 bind-9.8.3-1.fc15 drupal7-7.14-2.fc15 dsi-1.0.7-3.fc15 fcitx-chewing-0.1.1-1.fc15 fcitx-cloudpinyin-0.2.1-1.fc15 fcitx-configtool-0.4.3-1.fc15 fcitx-fbterm-0.1.4-1.fc15 fcitx-keyboard-0.1.3-1.fc15 fcitx-table-extra-0.3.0-1.fc15 fcitx-ui-light-0.1.3-2.fc15 kernel-2.6.43.7-1.fc15 moodle-1.9.18-1.fc15 nagios-plugins-check_sip-1.3-2.fc15 python-rhsm-1.0.1-1.fc15 qlandkartegt-1.4.2-1.fc15 rcssserver3d-0.6.6-1.fc15 rt3-3.8.12-1.fc15 simspark-0.2.3-1.fc15 spin-kickstarts-0.15.7-1.fc15 subscription-manager-1.0.2-1.fc15 sugar-portfolio-23-1.fc15 sugar-portfolio-24-1.fc15 wireshark-1.4.13-1.fc15 zeroinstall-injector-1.8-1.fc15 Details about builds: ATpy-0.9.6-1.fc15 (FEDORA-2012-8378) Astronomical Tables in Python Update Information: New upstream source ChangeLog: * Mon May 21 2012 Sergio Pascual sergiopr at fedoraproject.org - 0.9.6-1 - New upstream release. CGSI-gSOAP-1.3.5-2.fc15 (FEDORA-2012-8330) GSI plugin for gSOAP Update Information: Update to version 1.3.5 (EMI 2 version) ChangeLog: * Thu May 24 2012 Mattias Ellert mattias.ell...@fysast.uu.se - 1.3.5-2 - Use the right svn tag * Thu May 24 2012 Mattias Ellert mattias.ell...@fysast.uu.se - 1.3.5-1 - Update to version 1.3.5 (EMI 2 release) Zim-0.56-2.fc15 (FEDORA-2012-8319) Desktop wiki notekeeper Update Information: Fix BZ822454 ChangeLog: * Thu May 24 2012 Robin Lee cheese...@fedoraproject.org - 0.56-2 - BZ#822454 abrt-2.0.3-7.fc15 (FEDORA-2012-8356) Automatic bug detection and reporting tool
Re: running speakup on f17 beta
Josh Boyer writes: You would contact the fedora kernel list. They would tell you that Fedora doesn't enable staging drivers except in very specific cases. Hmmm, I presume there's a document describing the selection criteria? Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net The Linux Foundation Chair, Open Accessibility: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols Formats http://www.w3.org/wai/pf Indie UIhttp://www.w3.org/WAI/IndieUI/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
