OpenStack on F17
Hi, I'm trying to install OpenStack on F17 using Getting Started with OpenStack wiki but having some issues (note that the DB is on a different system): 1) nova db sync doesn't create the table migrate_version (bug 816424) 2) glance-manage db_sync ONLY creates the table migrate_version 3) keystone-manage db_sync doesn't create the table migrate_version Is anyone having the same issues? Thanks, Tommy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
dracut Warning: Unable to process initqueue was Re: F17 >> Rawhide iisues...
>> Greetings All: >>I was asked to write out what message/ error that I was getting on my >>screen before the dracut shell, so here it is: >>It's this bug: >>https://bugzilla.redhat.com/show_bug.cgi?id=814625 I have followed this bug down to the last comment! It does work!!! Latest dracut: http://koji.fedoraproject.org/koji/buildinfo?buildID=315269 Latest kernel: http://koji.fedoraproject.org/koji/buildinfo?buildID=315001 Steps I followed are: 1) yum install fedora-release-rawhide 2) Download dracut from the link above... 3) yum localupdate dracut-018-37.git20120425.fc18.1 4) yum update 5) reboot Wait a while and ignore the warnings as it will boot... Sincerely yours, Rob G. Healey >There is a workaround in comment 22. But if you can help with some of the >testing, >Harald has suggested in: comment 19 -- >Regards, >Frank >"Jack of all, fubars" -- 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-6371/nginx-1.0.15-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-5631/phpMyAdmin-3.5.0-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6395/openssl-1.0.0i-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6414/rubygems-1.7.2-5.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6349/samba4-4.0.0-26.alpha11.fc15.6 https://admin.fedoraproject.org/updates/FEDORA-2012-6396/bugzilla-3.6.9-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6511/wordpress-3.3.2-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6630/dokuwiki-0-0.10.20110525.a.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6610/xulrunner-12.0-1.fc15,firefox-12.0-1.fc15,gnome-python2-extras-2.25.3-35.fc15.7,perl-Gtk2-MozEmbed-0.09-1.fc15.11 https://admin.fedoraproject.org/updates/FEDORA-2012-5916/python3-3.2.3-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6629/gdb-7.3.1-50.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6177/gridengine-6.2u5-10.fc15.3 https://admin.fedoraproject.org/updates/FEDORA-2012-6398/cifs-utils-5.4-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-6629/gdb-7.3.1-50.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6610/xulrunner-12.0-1.fc15,firefox-12.0-1.fc15,gnome-python2-extras-2.25.3-35.fc15.7,perl-Gtk2-MozEmbed-0.09-1.fc15.11 https://admin.fedoraproject.org/updates/FEDORA-2012-6552/PackageKit-0.6.17-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6517/pcre-8.12-8.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6395/openssl-1.0.0i-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6373/fuse-2.8.7-1.fc15.1 https://admin.fedoraproject.org/updates/FEDORA-2012-5915/python-2.7.3-2.fc15,python-docs-2.7.3-1.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/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 bind-9.8.2-1.fc15 dokuwiki-0-0.10.20110525.a.fc15 emelfm2-0.8.1-1.fc15 firefox-12.0-1.fc15 gdb-7.3.1-50.fc15 ghc-void-0.5.5-1.fc15 gnome-python2-extras-2.25.3-35.fc15.7 perl-Gtk2-MozEmbed-0.09-1.fc15.11 python-cagraph-1.2-10.fc15 pytorctl-0-0.9.20111213git.fc15 rubygem-xmlparser-0.6.81-9.fc15 srptools-0.0.4-13.fc15 xulrunner-12.0-1.fc15 Details about builds: bind-9.8.2-1.fc15 (FEDORA-2012-6606) The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server Update Information: Update to the latest 9.8.2 stable release. ChangeLog: * Tue Apr 24 2012 Adam Tkac 32:9.8.2-1 - update to 9.8.2 - bind-9.5-overflow.patch is no longer needed dokuwiki-0-0.10.20110525.a.fc15 (FEDORA-2012-6630) Standards compliant simple to use wiki Update Information: Fix XSS Flaw ChangeLog: * Tue Apr 24 2012 Andrew Colin Kissa - 0-0.10.20110525.a - Fix CVE-2012-2129 - Fix Bugzilla bugs #815123 References: [ 1 ] Bug #815122 - CVE-2012-2128 CVE-2012-2129 dokuwiki: XSS and CSRF due improper escaping of 'target' parameter in preprocessing edit form data https://bugzilla.redhat.com/show_bug.cgi?id=815122 emelfm2-0.8.1-1.fc15 (FEDORA-2012-6618) File manager that implements the popular two-pane design Update Information: This update fixes a frequent crash with glib 2.32 and some other bugs as outlined at http://emelfm2.net/wiki/ChangeLog ChangeLog: * Tue Apr 24 2012 Christoph Wickert - 0.8.1-1 - Update to 0.8.1 - Patch edit
Fedora 16 updates-testing report
The following Fedora 16 Security updates need testing: https://admin.fedoraproject.org/updates/FEDORA-2012-6365/openstack-nova-2011.3.1-8.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6368/bugzilla-4.0.6-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5624/phpMyAdmin-3.5.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6403/openssl-1.0.0i-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6375/cifs-utils-5.4-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6411/nginx-1.0.15-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6409/rubygems-1.8.11-3.fc16.1 https://admin.fedoraproject.org/updates/FEDORA-2012-6529/argyllcms-1.4.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-6628/dokuwiki-0-0.10.20110525.a.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6622/firefox-12.0-1.fc16,xulrunner-12.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6542/wordpress-3.3.2-2.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-6612/asterisk-1.8.11.1-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6614/gdb-7.3.50.20110722-16.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6179/gridengine-6.2u5p2-7.fc16.3 https://admin.fedoraproject.org/updates/FEDORA-2011-14691/tomcat6-6.0.32-19.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6382/samba4-4.0.0-38.alpha16.fc16 The following Fedora 16 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/FEDORA-2012-6614/gdb-7.3.50.20110722-16.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6622/firefox-12.0-1.fc16,xulrunner-12.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6613/selinux-policy-3.10.0-86.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6550/bash-4.2.24-2.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6516/pcre-8.12-9.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6389/taglib-1.7.2-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6403/openssl-1.0.0i-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6416/fuse-2.8.7-1.fc16.1 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-6004/sane-backends-1.0.22-10.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5906/rsyslog-5.8.10-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-3319/GConf2-3.2.3-4.fc16 The following builds have been pushed to Fedora 16 updates-testing asterisk-1.8.11.1-1.fc16 bind-9.8.2-1.fc16 dokuwiki-0-0.10.20110525.a.fc16 emelfm2-0.8.1-1.fc16 firefox-12.0-1.fc16 gdb-7.3.50.20110722-16.fc16 ghc-void-0.5.5-1.fc16 is-interface-1.12.2-2.fc16 json_diff-1.3.3-1.fc16 libreoffice-3.4.5.2-13.fc16 mcollective-1.3.3-3.fc16 python-cagraph-1.2-10.fc16 pytorctl-0-0.9.20111213git.fc16 rubygem-xmlparser-0.6.81-10.fc16 selinux-policy-3.10.0-86.fc16 soundconverter-1.5.4-15.fc16 srptools-0.0.4-13.fc16 usb_modeswitch-1.2.3-1.fc16 usb_modeswitch-data-20120120-1.fc16 vanessa_socket-0.0.12-1.fc16 xulrunner-12.0-1.fc16 Details about builds: asterisk-1.8.11.1-1.fc16 (FEDORA-2012-6612) The Open Source PBX Update Information: The Asterisk Development Team has announced security releases for Asterisk 1.6.2, 1.8, and 10. The available security releases are released as versions 1.6.2.24, 1.8.11.1, and 10.3.1. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of Asterisk 1.6.2.24, 1.8.11.1, and 10.3.1 resolve the following two issues: * A permission escalation vulnerability in Asterisk Manager Interface. This would potentially allow remote authenticated users the ability to execute commands on the system shell with the privileges of the user running the Asterisk application. * A heap overflow vulnerability in the Skinny Channel driver. The keypad button message event failed to check the length of a fixed length buffer before appending a received digit to the end of that buffer. A remote authenticated user could send sufficient keypad button message events that the buffer would be overrun. In addition, the release of Asterisk 1.8.11.1 and 10.3.1 resolve the following
nfs-idmap.service removed
Is there anywhere documentation outlining the decision to remove a separate nfs-idmap.service from F17? It seems that nfs-server.service must be enabled and started in order for rpc.idmapd. It doesn't seem logical that a system running a NFS Client Only should be required to also run an NFS server. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
TC1 update errors
Installed x86_64 TC1 dvd image on a vbox guest. Updates won't work due to problems with the F17-branced repo being out of sync for apper and NetworkManager. (yum --skip-broken didn't work either.) Additionally, PackageKit still won't properly import the signing key. -- G.Wolfe Woodbury redwolfe (proventesters) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nouveau fails with F17 Beta on GeForce 6150 (NV4E)
Dear both, thanks for your replies. I have updated the bugzilla report with the requested F16 log files using remote ssh. However, I failed with both suggested methods to get boot logs off the F17 beta life CD. (a) 'nouveau.modeset=0' brings up plymouth, but when it finishes, it starts X with apparently the vesa driver, so working (poor) X and no nouveau debug output. I did not find a way to disable graphical boot completely (and then change to X with the full nouveau driver). (b) netconsole does not give me any output at the receiving end. I have verified carefully that the receiving machine and the network is set up properly, and the source machine can send (on a functioning F16) UDP packets to the logger on the receiving end. However, with the netconsole on the kernel parameter line, nothing happens. No idea how to debug this - I followed the instructions quite carefully and verified the MAC address as suggested as well. In any case, I suspect that the problem is not F17 specific, but rather tied to the 3.3 kernel, so that the F16 logs could possibly suffice. Could you let me know if you can work with the information provided, or if there anything else I could try? Regards, Marcel Konrad Rzeszutek Wilk writes: > On Thu, Apr 19, 2012 at 01:38:01PM +0200, Marcel Oliver wrote: > > Hi, > > > > I am having worsening problems with the nouveau driver on GeForce 6150 > > (NV4E), this is the onboard graphics on the ASUS M2NPV-VM. So I tried > > F17 Beta (x86) yesterday to see what the status is. Result: total > > failure - the screen goes to a very dark blue and the keyboard appears > > also dead. > > > > This same problem already shows up on F16 with any of the 3.3 kernels > > (last working kernel is 3.2.10-3 without acceleration, acceleration > > never worked on this chip), see > > > > https://bugzilla.redhat.com/show_bug.cgi?id=810490 > > > > Question: > > > > - Should I file another bug report on F17 beta? > > Can you just add the serial/dmesg output with drm.info=255 to the bug? > > > > - If so, what are the chances that someone looks at it? > > > > - Is there any easy way to extract the requested debug information > > from the system in the failing configuration? Ideally, I'd like to > > write out to USB stick without installing the system, but since no > > user interaction is possible, that seems too much to ask? > > Alternatively, if I install on a scratch partition, is there a way > > to instrument the startup code to write the necessary debug > > information to disk for later inspection from a working system? > > Networking would be a bit of a pain to bring up... > > You could boot in text mode (so recovery) with 'nouveau.modeset=0'. > Set up your network, SSH in the box, and then 'exec /sbin/init 5' > to start X. Then from your SSH session run 'dmesg' to get that > output. > > Oh, you should also have 'debug loglevel=8' on your Linux command > line. > > > > > Any comments appreciated, also an estimate of the chances of being > > able to use Fedora on this machine again... > > > > Regards, > > Marcel > > -- > > 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
F17 still complaining about write cache
These error messages keep coming even with today's fresh install. Apr 25 13:28:51 omen3 kernel: [ 942.329285] sd 12:0:0:0: [sdc] Test WP failed, assume Write Enabled Apr 25 13:28:51 omen3 kernel: [ 942.330985] sd 12:0:0:0: [sdc] Asking for cache data failed Apr 25 13:28:51 omen3 kernel: [ 942.330992] sd 12:0:0:0: [sdc] Assuming drive cache: write through Otherwise, install from DVD and from pxeboot using custom disk layout completed without problems. No problems seen with simple NFS ops. I am installing the apps that seem to trigger the Noveau wedge. -- Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F17: sudo reboot/shutdown -P now taking ~2 mins to shutdown
$ sudo reboot or $ sudo shutdown -P now takes ~1/2 mins to shutdown; using "Restart" or "Shutdown" in GDM/Gnome session menu takes ~10 seconds. Any ideas why? F17, x86. -- Pedro -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
On Wed, Apr 25, 2012 at 12:33 PM, Panu Matilainen wrote: > On 04/25/2012 07:45 PM, Chris Adams wrote: >> >> Once upon a time, Kevin Martin said: >>> >>> Transaction Check Error: >>> file /usr/bin from install of >>> google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with file from >>> package >>> filesystem-3.1-1.fc18.x86_64 >> >> >> It looks like a bunch of the common directories have been changed to >> read-only in the filesystem package (haven't seen any notice/discussion >> about that, but maybe I missed it). > > > The permission difference might've been there forever, rpm has only very > recently (in rawhide) started to raise file conflicts when user/group/mode > differences. > >> >> The other issue would be: why is google-chrome-unstable (wherever you >> are getting that from) packaing the /usr/bin directory? It shouldn't do >> that. > > > Yup, its a packaging bug in google-chrome. What? That's unpossible! -J > - Panu - > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
On 04/25/2012 07:45 PM, Chris Adams wrote: Once upon a time, Kevin Martin said: Transaction Check Error: file /usr/bin from install of google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with file from package filesystem-3.1-1.fc18.x86_64 It looks like a bunch of the common directories have been changed to read-only in the filesystem package (haven't seen any notice/discussion about that, but maybe I missed it). The permission difference might've been there forever, rpm has only very recently (in rawhide) started to raise file conflicts when user/group/mode differences. The other issue would be: why is google-chrome-unstable (wherever you are getting that from) packaing the /usr/bin directory? It shouldn't do that. Yup, its a packaging bug in google-chrome. - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
On Wed, 2012-04-25 at 12:47 -0400, Kamil Paral wrote: > Isn't it common to also include the directories you want to place files into? Only when there's any real chance of them not existing otherwise. I'd say packaging any directory which is part of FHS is a clear error. Packaging a directory is essentially to assert ownership of it. You can read it as meaning 'if this package is not installed, this directory should not exist'. That's a good test of whether you should be packaging any given directory: does that statement make sense? -- 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 update failed today with....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 25 Apr 2012 12:51:49 -0400 Jonathan Kamens wrote: > On 4/25/2012 12:47 PM, Kamil Paral wrote: > > Isn't it common to also include the directories you want to place > > files into? > > > > $ rpm -ql google-chrome-stable | grep /bin > > /usr/bin > > /usr/bin/google-chrome > No. This is not correct packaging. > > It is reasonable for an RPM to /require /the presence of the system > directories it uses as prerequisites before it can be installed, so > that if the filesystem layout changes in a way that the RPM doesn't > expect, it will refuse to install (which is correct behavior). > > It is /not/ reasonable for an RPM to /include/ shared directories > that it does not own. Files and directories should only be owned by a > single RPM. > > On my system, there are only four RPMs (out of 3616) that provide > /usr/bin: VirtualBox, filesystem, google-earth-stable, and > google-chrome-stable. It is telling that three of these four RPMs are > third-party RPMs. Their maintainers are shipping buggy RPMs and they > should fix them. > > This is generally a sign that they were lazy when writing their spec > files... Instead of constructing the %files section of the spec file > carefully to include only the files they actually own, they just put > "*" in the spec file to include the entire contents of the install > directory. Yuck. actually a * would have been preferable what they would have used is %{_bindir} they should have done %{_bindir}/* so they own whats in there but not the directory itself if they jsut used something like /* they would also own /usr but its very buggy packaging. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+YLmcACgkQkSxm47BaWffNfACfSuDzONlsYnujBTTbe2+A6hC8 1PIAnA9hqYry5AwnvbkEngNJJ+LL+QKY =+FIa -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
On 4/25/2012 12:47 PM, Kamil Paral wrote: Isn't it common to also include the directories you want to place files into? $ rpm -ql google-chrome-stable | grep /bin /usr/bin /usr/bin/google-chrome No. This is not correct packaging. It is reasonable for an RPM to /require /the presence of the system directories it uses as prerequisites before it can be installed, so that if the filesystem layout changes in a way that the RPM doesn't expect, it will refuse to install (which is correct behavior). It is /not/ reasonable for an RPM to /include/ shared directories that it does not own. Files and directories should only be owned by a single RPM. On my system, there are only four RPMs (out of 3616) that provide /usr/bin: VirtualBox, filesystem, google-earth-stable, and google-chrome-stable. It is telling that three of these four RPMs are third-party RPMs. Their maintainers are shipping buggy RPMs and they should fix them. This is generally a sign that they were lazy when writing their spec files... Instead of constructing the %files section of the spec file carefully to include only the files they actually own, they just put "*" in the spec file to include the entire contents of the install directory. Yuck. jik -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Karma needed for builds intended for TC1
On Wed, Apr 25, 2012 at 5:31 AM, Adam Williamson wrote: > On Tue, 2012-04-24 at 20:12 -0700, John Reiser wrote: >> >> EFI booting that DVD to update an existing Fedora 17 Beta x86_64 with >> EFI boot, and requesting "Do not change bootloader config", has left >> my system unbootable. > > That option is somewhat poorly named. What it really means is 'Don't let > anaconda change the bootloader config'. It doesn't prevent the kernel > post script from changing it, when the kernel package is updated; it'd > be very difficult to prevent that. So it's not actually particularly > unusual for the grub config file to be changed after such an upgrade. We > probably should rename the option somehow... > >> First, it did change /boot/efi/EFI/redhat/grub.conf, even though I asked >> for no change. Second, the update left only one stanza in grub.conf, >> completely erasing what was there before. This was an Update, so the >> old stanzas should have remained present. > > That certainly sounds wrong. > >> Third, the bootloader was >> changed to one that cannot find anything, and always drops to >> "grub rescue >". Fourth, there is no "help" command in grub rescue. > > Also wrong, but you're not providing much useful data. What exactly is > the grub config changed to? What shows in the anaconda logs from the > upgrade, particularly program.log Since there's a "grub rescue" prompt, has grub2 replaced grub-efi (which, IIUC, is an EFI version of grub1)? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GSoC 2012: On-Demand Fedora Build Service
> how we could build a more friendly image > building system to help the Fedora QA community during the testing > phase. Short latency tends to improve friendliness. By fiddling with pungi environment, I'm down to about 9.5 minutes to create an install .iso after downloads have finished. If makedeltaiso produced a new .iso from an old .iso plus a list of changed .rpms, then that might help (as long as the changes involve no new dependencies.) -- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
> Once upon a time, Kevin Martin said: > > Transaction Check Error: > > file /usr/bin from install of > > google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with > > file from package > > filesystem-3.1-1.fc18.x86_64 > > It looks like a bunch of the common directories have been changed to > read-only in the filesystem package (haven't seen any > notice/discussion > about that, but maybe I missed it). > > The other issue would be: why is google-chrome-unstable (wherever you > are getting that from) packaing the /usr/bin directory? It shouldn't > do > that. Isn't it common to also include the directories you want to place files into? $ rpm -ql google-chrome-stable | grep /bin /usr/bin /usr/bin/google-chrome -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
Once upon a time, Kevin Martin said: > Transaction Check Error: > file /usr/bin from install of > google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with file from > package > filesystem-3.1-1.fc18.x86_64 It looks like a bunch of the common directories have been changed to read-only in the filesystem package (haven't seen any notice/discussion about that, but maybe I missed it). The other issue would be: why is google-chrome-unstable (wherever you are getting that from) packaing the /usr/bin directory? It shouldn't do that. -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: yum update failed today with....
That would seem to be an issue with the google-chrome-unstable RPM, which almost certainly should not package /usr/bin. Since that RPM is provided by Google, not by Fedora, you need to take it up with them. jik On 4/25/2012 12:40 PM, Kevin Martin wrote: Transaction Check Error: file /usr/bin from install of google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with file from package filesystem-3.1-1.fc18.x86_64 Kevin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
yum update failed today with....
Transaction Check Error: file /usr/bin from install of google-chrome-unstable-20.0.1115.1-133713.x86_64 conflicts with file from package filesystem-3.1-1.fc18.x86_64 Kevin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GSoC 2012: On-Demand Fedora Build Service
On Wed, 25 Apr 2012 20:45:11 +0530 Amit Saha wrote: > Hello Everyone: > > I am Amit. I shall be working on the project "On-Demand Fedora Build > Service" [1], as part of the Google Summer of Code 2012. Over the past > few weeks, I have been in touch with Tim Flink, who is my mentor for > this project and we have been discussing (well, Tim has been sharing > his thoughts) with me about how we could build a more friendly image > building system to help the Fedora QA community during the testing > phase. > > I shall have more updates as I progress on this project, and I shall > look forward to your thoughts and comments on the proposed project. > > Since I am very much a newbie to the Fedora QA community (not Fedora), > I might have some silly questions to ask. > > > [1] > https://fedoraproject.org/wiki/GSOC_2012/Student_Application_amitksaha/OnDemandBuildService Welcome to QA land and congratulations again on being accepted for GSoC! I'm certainly looking forward to seeing this happen but then again, I tend to be one of the people who is building test images by hand :) Tim signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GSoC 2012: On-Demand Fedora Build Service
On Wed, 2012-04-25 at 20:45 +0530, Amit Saha wrote: > Hello Everyone: > > I am Amit. I shall be working on the project "On-Demand Fedora Build > Service" [1], as part of the Google Summer of Code 2012. Over the past > few weeks, I have been in touch with Tim Flink, who is my mentor for > this project and we have been discussing (well, Tim has been sharing > his thoughts) with me about how we could build a more friendly image > building system to help the Fedora QA community during the testing > phase. > > I shall have more updates as I progress on this project, and I shall > look forward to your thoughts and comments on the proposed project. > > Since I am very much a newbie to the Fedora QA community (not Fedora), > I might have some silly questions to ask. Hi Amit, and welcome! Thanks very much for volunteering for this project, it would be a big benefit to QA if it can be successfully created. -- 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: GSoC 2012: On-Demand Fedora Build Service
Hello Brendan: On Wed, Apr 25, 2012 at 9:13 PM, Brendan Jones wrote: > On 04/25/2012 05:15 PM, Amit Saha wrote: >> >> Hello Everyone: >> >> I am Amit. I shall be working on the project "On-Demand Fedora Build >> Service" [1], as part of the Google Summer of Code 2012. Over the past >> few weeks, I have been in touch with Tim Flink, who is my mentor for >> this project and we have been discussing (well, Tim has been sharing >> his thoughts) with me about how we could build a more friendly image >> building system to help the Fedora QA community during the testing >> phase. >> >> I shall have more updates as I progress on this project, and I shall >> look forward to your thoughts and comments on the proposed project. >> >> Since I am very much a newbie to the Fedora QA community (not Fedora), >> I might have some silly questions to ask. >> >> >> [1] >> https://fedoraproject.org/wiki/GSOC_2012/Student_Application_amitksaha/OnDemandBuildService >> >> Best, >> Amit >> > Hello and welcome Amit! > > Whilst I'm not very active in the Fedora QA community, I am a mentor for > another GSOC project (Audio spin), with which we also hope to indulge more > upon the support of the QA team. Will watch your progress with interest - > perhaps you can share the URL of your blog? Here it is: http://echorand.me/category/fedora/gsoc2012/ Best, Amit -- http://echorand.me -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GSoC 2012: On-Demand Fedora Build Service
On 04/25/2012 05:15 PM, Amit Saha wrote: Hello Everyone: I am Amit. I shall be working on the project "On-Demand Fedora Build Service" [1], as part of the Google Summer of Code 2012. Over the past few weeks, I have been in touch with Tim Flink, who is my mentor for this project and we have been discussing (well, Tim has been sharing his thoughts) with me about how we could build a more friendly image building system to help the Fedora QA community during the testing phase. I shall have more updates as I progress on this project, and I shall look forward to your thoughts and comments on the proposed project. Since I am very much a newbie to the Fedora QA community (not Fedora), I might have some silly questions to ask. [1] https://fedoraproject.org/wiki/GSOC_2012/Student_Application_amitksaha/OnDemandBuildService Best, Amit Hello and welcome Amit! Whilst I'm not very active in the Fedora QA community, I am a mentor for another GSOC project (Audio spin), with which we also hope to indulge more upon the support of the QA team. Will watch your progress with interest - perhaps you can share the URL of your blog? regards, Brendan -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Karma needed for builds intended for TC1
> you're not providing much useful data. https://bugzilla.redhat.com/show_bug.cgi?id=816238 -- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
GSoC 2012: On-Demand Fedora Build Service
Hello Everyone: I am Amit. I shall be working on the project "On-Demand Fedora Build Service" [1], as part of the Google Summer of Code 2012. Over the past few weeks, I have been in touch with Tim Flink, who is my mentor for this project and we have been discussing (well, Tim has been sharing his thoughts) with me about how we could build a more friendly image building system to help the Fedora QA community during the testing phase. I shall have more updates as I progress on this project, and I shall look forward to your thoughts and comments on the proposed project. Since I am very much a newbie to the Fedora QA community (not Fedora), I might have some silly questions to ask. [1] https://fedoraproject.org/wiki/GSOC_2012/Student_Application_amitksaha/OnDemandBuildService Best, Amit -- http://echorand.me -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Lots of schema related warnings on yum update
On 04/25/2012 12:50 PM, Ankur Sinha wrote: > Hello, > > I get these schema warnings on updating my F17 system: >> warning: Schema 'org.freedesktop.Telepathy.Logger' has path >> '/apps/telepathy-logger/'. Paths starting with '/apps/', '/desktop/' or >> '/system/' are deprecated. [...] > How should these be handled? Do we file bugs? Do we ignore these? There was a late change in glib-compile-schemas, introducing these warnings. A lot of packages run glib-compile-schemas in rpm scripts [1] at package install / uninstall time, so this also shows up during yum updates. The fix would be to redirect glib-compile-schemas output to /dev/null in each of the packages that run glib-compile-schemas. I've done a number of packages here: https://admin.fedoraproject.org/updates/FEDORA-2012-6591 Also see https://bugzilla.redhat.com/show_bug.cgi?id=814053 If you find any other packages with noisy %post scriptlets, beyond what I've already fixed in that update, file bugs against the packages. I used the following one-liner to identify packages needing fixing. If you apply the update above (might still see some warnings during the update from old packages uninstallation) and then run this, you might find some new ones that need fixing: rpm -qa | while read pkg ; do if rpm -q --scripts $pkg | grep glib-compile-schemas | grep -v '/dev/null' > /dev/null ; then echo "$pkg doesn't redirect glib-compile-schemas output" ; fi ; done [1] http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GSettings_Schema -- Kalev -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-17 Branched report: 20120425 changes
Compose started at Wed Apr 25 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 [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [egoboo] egoboo-2.7.5-11.fc17.x86_64 requires libenet-1.2.1.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 [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) [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) [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 [meshlab] meshlab-1.3.1-2.fc17.x86_64 requires libmuparser.so.0()(64bit) [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_6
[Test-Announce] ABRT Test Day tomorrow - 2012-Apr-26
Friends of ABRT, Quality Engineers, fellow testers - There's a Test Day going on tomorrow, Thursday 2012-Apr-26: https://fedoraproject.org/wiki/Test_Day:2012-04-26_ABRT_and_deduplication_service Looking at ABRT v2.0.10 (and related components) in Fedora 17 (see the feature page at https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication). As always, the event is in #fedora-test-day in Freenode IRC, and all the test instructions are on the Wiki. There will be a good turnout of developers, so it's a great chance to help shake out any remaining ABRT bugs for Fedora 17. Please help out if you have a chance! Thanks, Richard & Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Lots of schema related warnings on yum update
Hello, I get these schema warnings on updating my F17 system: > warning: Schema 'org.freedesktop.Telepathy.Logger' has path > '/apps/telepathy-logger/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.freedesktop.gstreamer-0.10.default-elements' has path > '/desktop/gstreamer/0.10/default-elements/'. Paths starting with '/apps/', > '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.freedesktop.ibus' has path '/desktop/ibus/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.freedesktop.ibus.general' has path > '/desktop/ibus/general/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.freedesktop.ibus.general.hotkey' has path > '/desktop/ibus/general/hotkey/'. Paths starting with '/apps/', '/desktop/' > or '/system/' are deprecated. > warning: Schema 'org.freedesktop.ibus.general.xkblayoutconfig' has path > '/desktop/ibus/general/xkblayoutconfig/'. Paths starting with '/apps/', > '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.freedesktop.ibus.panel' has path '/desktop/ibus/panel/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.Cheese' has path '/apps/cheese/'. Paths starting > with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.Vino' has path '/desktop/gnome/remote-access/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.crypto.cache' has path > '/desktop/gnome/crypto/cache/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.gnome.crypto.pgp' has path '/desktop/gnome/crypto/pgp/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.seahorse' has path '/apps/seahorse/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.seahorse.manager' has path > '/apps/seahorse/listing/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.gnome.system.dns_sd' has path '/system/dns-sd/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.system.locale' has path '/system/locale/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.system.proxy' has path '/system/proxy/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.system.proxy.http' has path '/system/proxy/http/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.system.proxy.https' has path > '/system/proxy/https/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.gnome.system.proxy.ftp' has path '/system/proxy/ftp/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.gnome.system.proxy.socks' has path > '/system/proxy/socks/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.gnome.system.smb' has path '/system/smb/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema > 'org.yorba.shotwell.sharing.org-yorba-shotwell-publishing-piwigo' has path > '/apps/shotwell/sharing/org-yorba-shotwell-publishing-piwigo/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema > 'org.yorba.shotwell.sharing.org-yorba-shotwell-publishing-yandex-fotki' has > path '/apps/shotwell/sharing/org-yorba-shotwell-publishing-yandex-fotki/'. > Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell' has path '/apps/shotwell/'. Paths > starting with '/apps/', '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.preferences' has path > '/apps/shotwell/preferences/'. Paths starting with '/apps/', '/desktop/' or > '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.preferences.ui' has path > '/apps/shotwell/preferences/ui/'. Paths starting with '/apps/', '/desktop/' > or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.preferences.slideshow' has path > '/apps/shotwell/preferences/slideshow/'. Paths starting with '/apps/', > '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.preferences.window' has path > '/apps/shotwell/preferences/window/'. Paths starting with '/apps/', > '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.preferences.files' has path > '/apps/shotwell/preferences/files/'. Paths starting with '/apps/', > '/desktop/' or '/system/' are deprecated. > warning: Schema 'org.yorba.shotwell.crop-settings' has path
Re: F17 vs. Pentium 4
On Tue, 2012-04-24 at 09:55 -0500, Michael Hennebry wrote: > On Wed, 18 Apr 2012, Michael Hennebry wrote: > > > On Wed, 18 Apr 2012, Adam Williamson wrote: > > > >> 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. > > Done. > > Which of these should I worry about? > [root@localhost ~]# grep -v stall install.log > warning: fontpackages-filesystem-1.44-2.fc15.noarch: Header V3 RSA/SHA256 > Signature, key ID a82ba4b7: NOKEY > /var/tmp/rpm-tmp.70BdJf: line 1: /usr/sbin/update-alternatives: No such file > or directory > warning: %post(tomcat-servlet-3.0-api-0:7.0.26-1.fc16.noarch) scriptlet > failed, exit status 127 > /var/tmp/rpm-tmp.pKiL8w: line 1: /usr/sbin/update-alternatives: No such file > or directory > warning: %post(tomcat-jsp-2.2-api-0:7.0.26-1.fc16.noarch) scriptlet failed, > exit status 127 > /var/tmp/rpm-tmp.NaLh0X: line 3: find: command not found > /var/tmp/rpm-tmp.hawg7Q: line 1: /usr/sbin/update-alternatives: No such file > or directory > warning: %post(tomcat-el-2.2-api-0:7.0.26-1.fc16.noarch) scriptlet failed, > exit status 127 > Running in chroot, ignoring request. > 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 > 6874 blocks > *** FINISHED INSTALLING PACKAGES *** > > > getenforce says Disabled, I expect because of the above Could nots. > Is this something that wold be fixed with an auto-relabel? Are you somehow missing the selinux-policy-targeted package? That should have the file in question. The RPM post errors could be reported as bugs in those packages, though they may be 'false errors', I guess. It _looks_ like those packages aren't properly requiring tools they execute in their %post scripts. -- 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: Karma needed for builds intended for TC1
On Tue, 2012-04-24 at 20:12 -0700, John Reiser wrote: > On 04/24/2012 02:56 PM, Tim Flink wrote: > > http://tflink.fedorapeople.org/iso/20120424_f17-preTC1-3.x64.boot.iso > > > I haven't done a bare metal install with this iso yet but it boots for > > me on multiple EFI machines, so I'm pretty confident that the kinks > > have been worked out. > > EFI booting that DVD to update an existing Fedora 17 Beta x86_64 with > EFI boot, and requesting "Do not change bootloader config", has left > my system unbootable. That option is somewhat poorly named. What it really means is 'Don't let anaconda change the bootloader config'. It doesn't prevent the kernel post script from changing it, when the kernel package is updated; it'd be very difficult to prevent that. So it's not actually particularly unusual for the grub config file to be changed after such an upgrade. We probably should rename the option somehow... > First, it did change /boot/efi/EFI/redhat/grub.conf, even though I asked > for no change. Second, the update left only one stanza in grub.conf, > completely erasing what was there before. This was an Update, so the > old stanzas should have remained present. That certainly sounds wrong. > Third, the bootloader was > changed to one that cannot find anything, and always drops to > "grub rescue >". Fourth, there is no "help" command in grub rescue. Also wrong, but you're not providing much useful data. What exactly is the grub config changed to? What shows in the anaconda logs from the upgrade, particularly program.log -- 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: NFS not working
FWIW, I did check an F16 system. Prior to issuing the mount command the nfs module is not loaded. It gets loaded as a consequence of the mount command. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NFS not working
On 04/25/2012 12:47 PM, Braden McDaniel wrote: > Apparently it's not just me: > > https://bugzilla.redhat.com/show_bug.cgi?id=806333 No, you are not alone. Same here -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
dracut Warning: Unable to process initqueue was Re: F17 >> Rawhide iisues...
On 25/04/12 05:39, Rob Healey wrote: Greetings All: I was asked to write out what message/ error that I was getting on my screen before the dracut shell, so here it is: It's this bug: https://bugzilla.redhat.com/show_bug.cgi?id=814625 There is a workaround in comment 22. But if you can help with some of the testing, Harald has suggested in: comment 19 -- Regards, Frank "Jack of all, fubars" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test