Re: Please help test packages!
On Wed, 05 Dec 2012 16:46:50 -1000, Erinn Looney-Triggs wrote: http://fedoraproject.org/wiki/QA:Update_feedback_guidelines Thanks! Well I never knew about that handy little tool. Thanks for pointing that out, knocked out a bunch of them. Here's a very important part of the Update Feedback Guidelines every tester ought to understand: http://fedoraproject.org/wiki/QA:Update_feedback_guidelines#Previously_reported_bugs | Previously reported bugs | | If your testing uncovers no problems but you see that another tester has | identified a serious problem with the package, please try to replicate | their problem, and post negative feedback if you are now able to confirm | it. | | If you are not able to confirm the problem but you suspect this may be | because you cannot recreate the necessary conditions, please post neutral (!) | feedback noting that you were unable to duplicate the problem. Only post | positive feedback if you are sure your testing indicates the other | reporter's negative feedback is a mistake. If we don't adhere to these guidelines, we would be vote against eachother often. Please be very careful with your feedback in bodhi if you see that previous testers have voted -1 already. -- Fedora release 18 (Spherical Cow) - Linux 3.6.7-5.fc18.x86_64 loadavg: 0.00 0.01 0.05 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode?
On 2012-12-06 10:05 (GMT+0100) Mateusz Marzantowicz composed: Felix Miata wrote: For those unfamiliar, Mageia as a fork of Mandriva retained the same installation cmdline option readonly=1. Using it presents the following partitioning windows during installation, quite logically, prior to software selection: #1 http://fm.no-ip.com/SS/mgaReadonly1s1.png #2 http://fm.no-ip.com/SS/mgaReadonly1s2.png Sorry, but I can't see any usability gain here. Choosing only devices that you want to partition, reduces number of things/partitions you must deal with or you can accidentally corrupt. I'm not sure I understand your meaning. What readonly=1 in Ma*a offers is reduction of the amount of partition tables you don't need or want touched yet can be touched to zero. For those of us who (with a familiar tool or tools) partition in advance, any ability more than to specify mount points adds nothing but opportunity for unwanted, and potentially disastrous, results. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Liberation 2.0 Vs Liberation 1.0 (Need comments)
If you do keep the current blurry fonts as default (god forbid), please at least provide an easy way to switch to Fedora 17 rendering style. Thanks. We all thought we need to wait for some more times for this feature. Decided in Fedora i18 meeting to defer this feature now. I will build liberation 1.07.2 soon for Fedora 18. It will solve the issue. Backward compatibility is difficult in this case. But next time i will give better try. Pravin, what exactly this means - will F18 repo contain both liberation 1 and liberation 2 fonts? That means liberation 2 will automatically replace liberation 1 fonts on update, unless I use some yum extension to force the old version? Or is the solution different, like renaming liberation 2 fonts to liberation2 package? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Failed login popup?
When the login screen comes up, I get a popup saying: Failed login from my system at work Anyone know where this comes from? I'd like to make it go away. It is always going to be caused by my system at work attempting to ssh into my system at home, and I haven't yet installed the proper ssh authorized users and wot-not that it needs to succeed on fedora 18. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-18 Branched report: 20121206 changes
Compose started at Thu Dec 6 09:16:22 UTC 2012 New package: erlang-emmap-0-0.1.git8725d46.fc18 Erlang mmap interface New package: plug-1.1-6.fc18 Linux software for Fender Mustang amplifiers Updated Packages: anaconda-18.35-1.fc18 - * Tue Dec 04 2012 Brian C. Lane b...@redhat.com - 18.35-1 - Fix a bug when switching back to an HDISO install source (#879612). (clumens) - Lower case the DONE button on media check. (clumens) - Change mirrorlist checkbox text (#883191). (clumens) - Change the bootloader button to indicate you can also not install one. (clumens) - Stop writing /etc/sysconfig/keyboard (#871543) (mschmidt) - Stop writing /etc/sysconfig/i18n (#871543) (mschmidt) - Write /etc/hostname (#871543) (mschmidt) - Correct doing string substitution for encryption. (clumens) - Add install.py to POTFILES.in so a lot more strings can be translated. (clumens) - Only instantiate main line action objects when they are needed. (clumens) - Add a category to POTFILES.in so USER SETTINGS gets translated. (clumens) - Make sure product info and spoke titles are translated throughout. (clumens) - Substitute on new_install_name when it's needed, not at the top of custom.py. (clumens) - Compare the protocol combox box on position, not text. (clumens) - When we retranslate the welcome window, inform glibc. (clumens) - Add gettext checks to widgets/configure.ac. (clumens) - The initial welcome screen is the only one that needs to do retranslation. (clumens) - Remove the generic retranslate method from the python portion of the UI. (clumens) - Do not allow manipulating protected devices in the reclaim dialog (#882147). (clumens) - ISOImage needs to look at /run/install/source for the mounted image (#879142). (clumens) - Minor TODO list update. (clumens) - Get rid of the unneeded action1. (clumens) - Do not list some layouts twice (#882526) (vpodzime) - Check if the given NTP server is a valid hostname (#865869) (vpodzime) - Improve and document network.sanityCheckHostname (vpodzime) - don't write network settings on image install (bcl) * Sat Dec 01 2012 Brian C. Lane b...@redhat.com - 18.34-1 - remove extra space in custom.py (bcl) * Fri Nov 30 2012 Brian C. Lane b...@redhat.com - 18.33-1 - Escape single percent signs in RPM changelog entries. (dcantrell) - Fixes for PkgWrangler review. (dcantrell) - Don't let defaults override user-specified container settings. (#879702) (dlehman) - Fix partition allocation when enabling container encryption. (#879702) (dlehman) - Remove partitions from all appropriate DiskLabel instances. (#870586) (dlehman) - Add a way for users to set the names of lvm and md devices. (dlehman) - Update the RAID-specific UI after changing the device's disk set. (dlehman) - Correctly handle the default vg not having been instantiated yet. (dlehman) - Drop requested container disks that don't have enough space. (#873293) (dlehman) - Don't allow LVM disk set selection via configure button. (dlehman) - Try to add new device to an existing container if disks are full. (dlehman) - Fix code to lock encryption checkbutton for LV in existing VG (#877871) (dlehman) - Add support for changing a new LV's VG. (dlehman) - Fix check for in-use LV name to include VG name. (#875477) (dlehman) - Remove the automatic show_all from those info_bar related functions. (clumens) - Add set_info, set_error, set_warning functions to the BaseWindow object. (clumens) - set_info functions may not be called from outside the main thread (#873600). (clumens) - Test if path is valid before using it (NTPConfigDialog) (vpodzime) * Wed Nov 28 2012 Brian C. Lane b...@redhat.com - 18.32-1 - Bootloader checking should work in terms of self.stage1/2_ attrs (#880277). (clumens) - Catch OverflowError in manual partitioning. (sbueno+anaconda) - Do not accept tabs in the keyboard layout test box (#897312). (clumens) - Wait for slower dhcp for payload setup and hostname setting (#873468) (rvykydal) * Mon Nov 26 2012 Brian C. Lane b...@redhat.com - 18.31-1 - Rename icons for liveinst (conflict with redhat-logos) (#878037) (rvykydal) - Rework actions in the resize dialog to avoid shortcomings (#866209, #867770). (clumens) - Check that everything's a GDK window before attempting to manipulate it. (clumens) - On live installs, the progress hub should have a Quit button (#854904). (clumens) - If no bootloader is to be installed, pop up a warning. (clumens) - Escape ampersands in spoke status text. (clumens) - Allow not setting any boot device via the UI (#867469). (clumens) - Allow specifying whether the URL you've given is a mirrorlist or not (#868558). (clumens) - Prevent false positives when checking for encryption change. (dlehman) - Don't add incomplete VGs to the LVM reject filter. (#878225) (dlehman) - Show device names for devices in the Unknown page/subsection. (#855646) (dlehman) - Add a page to the custom RHS notebook for uneditable
rawhide report: 20121206 changes
Compose started at Thu Dec 6 08:15:09 UTC 2012 Broken deps for x86_64 -- [ansible] ansible-fireball-0.9-1.fc19.noarch requires python-keyczar ansible-node-fireball-0.9-1.fc19.noarch requires python-keyczar [cp2k] cp2k-mpich2-2.3-1.fc19.x86_64 requires libmpichf90.so.3()(64bit) cp2k-mpich2-2.3-1.fc19.x86_64 requires libmpich.so.3()(64bit) [dogtag-pki] dogtag-pki-10.0.0-0.16.b3.fc19.noarch requires dogtag-pki-server-theme = 0:10.0.0 [dragonegg] dragonegg-3.1-18.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 [ember] ember-0.6.3-3.fc19.x86_64 requires libOgreMain.so.1.7.4()(64bit) [epiphany-extensions] epiphany-extensions-3.6.0-1.fc19.x86_64 requires epiphany(abi) = 0:3.6 [gcc-python-plugin] gcc-python2-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python2-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 [ghc-wai-extra] ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-conduit-0.4.0.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-bindings-0.1.0.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-0.5.3.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSwai-1.2.0.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSvoid-0.5.6-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSvault-0.2.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSunordered-containers-0.2.1.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSunix-2.5.1.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStransformers-base-0.4.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStransformers-0.3.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStime-1.4-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStext-0.11.2.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSsemigroups-0.8.3.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSresourcet-0.3.2.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSparsec-3.1.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSold-time-1.1.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSold-locale-1.0.0.4-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSnetwork-2.3.0.13-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSmtl-2.1.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSmonad-control-0.3.1.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSlifted-base-0.1.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSinteger-gmp-0.4.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHShttp-types-0.6.11-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHShashable-1.1.2.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSghc-prim-0.2.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSfilepath-1.3.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSfast-logger-0.0.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSdlist-0.5-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSdirectory-1.1.0.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSdeepseq-1.3.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSdata-default-0.4.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHScontainers-0.4.2.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSconduit-0.4.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHScase-insensitive-0.4.0.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSbytestring-0.9.2.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSblaze-builder-conduit-0.4.0.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSblaze-builder-0.3.1.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSbase-unicode-symbols-0.2.2.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSbase-4.5.0.0-ghc7.4.1.so()(64bit)
Re: Please help test packages!
On Thu, 2012-12-06 at 09:59 +0100, Michael Schwendt wrote: On Wed, 05 Dec 2012 16:46:50 -1000, Erinn Looney-Triggs wrote: http://fedoraproject.org/wiki/QA:Update_feedback_guidelines Thanks! Well I never knew about that handy little tool. Thanks for pointing that out, knocked out a bunch of them. Here's a very important part of the Update Feedback Guidelines every tester ought to understand: http://fedoraproject.org/wiki/QA:Update_feedback_guidelines#Previously_reported_bugs | Previously reported bugs | | If your testing uncovers no problems but you see that another tester has | identified a serious problem with the package, please try to replicate | their problem, and post negative feedback if you are now able to confirm | it. | | If you are not able to confirm the problem but you suspect this may be | because you cannot recreate the necessary conditions, please post neutral (!) | feedback noting that you were unable to duplicate the problem. Only post | positive feedback if you are sure your testing indicates the other | reporter's negative feedback is a mistake. If we don't adhere to these guidelines, we would be vote against eachother often. Please be very careful with your feedback in bodhi if you see that previous testers have voted -1 already. Thanks, Michael, that is indeed important. fedora-easy-karma shows all existing comments, so it's easy enough to check through them before filing your vote. -- 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: Final criteria/Test cases interconnection
On Út, 2012-12-04 at 10:02 -0800, Adam Williamson wrote: On Tue, 2012-12-04 at 17:28 +0100, Petr Schindler wrote: Obsolete TCs: * Hardware and BIOS RAID TCs - Do we support those now? Yes. Why would they be obsolete? https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_windows Ditto? I'm sorry, my fault, I used wrong word. The right word is outdated. Those TCs should be amended to reflect changes in anaconda. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Final criteria/Test cases interconnection
On Thu, 2012-12-06 at 15:38 +0100, Petr Schindler wrote: On Út, 2012-12-04 at 10:02 -0800, Adam Williamson wrote: On Tue, 2012-12-04 at 17:28 +0100, Petr Schindler wrote: Obsolete TCs: * Hardware and BIOS RAID TCs - Do we support those now? Yes. Why would they be obsolete? https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_windows Ditto? I'm sorry, my fault, I used wrong word. The right word is outdated. Those TCs should be amended to reflect changes in anaconda. Ah, right. Yes, good point. Yes, we still support such devices (though it's arguable whether a 'hardware RAID' test makes much sense, as any hardware RAID device that works at the kernel level is transparent at higher levels - it just looks like a disk). -- 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: Manual Partitioning and LVM, Re: Puzzled
On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski g...@czarc.net wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y for-each-VG and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski g...@czarc.net wrote: OK, I boot up the live gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if reclaim was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new criterion proposal: core kickstart commands
On Wed, Dec 05, 2012 at 09:39:41PM -0800, Adam Williamson wrote: I think that may be the case _now_ with our current Anaconda situation, but the more I think about it, the more strongly I feel about making this the approach for future releases. When there's _not_ a big Anaconda rewrite, kickstart commands shouldn't change drastically without planning. So, I don't think it's unreasonable in the real world. The commands themselves shouldn't change, but it's certainly possible - and frequently happens - for something to change in anaconda or some layer below anaconda which happens to have the effect of breaking a kickstart directive. ... which should be a blocker. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new criterion proposal: core kickstart commands
On Thu, 6 Dec 2012, Matthew Miller wrote: On Wed, Dec 05, 2012 at 09:39:41PM -0800, Adam Williamson wrote: I think that may be the case _now_ with our current Anaconda situation, but the more I think about it, the more strongly I feel about making this the approach for future releases. When there's _not_ a big Anaconda rewrite, kickstart commands shouldn't change drastically without planning. So, I don't think it's unreasonable in the real world. The commands themselves shouldn't change, but it's certainly possible - and frequently happens - for something to change in anaconda or some layer below anaconda which happens to have the effect of breaking a kickstart directive. ... which should be a blocker. I agree with Matt. Kickstart is not only a lowest common denominator it is a critical functionality for tons of our testing and deployment tools. We don't want revolutionary change in kickstart and we definitely cannot have it be broken. Slow, gradual change properly documented is critical for kickstart. I'm less concerned about changes in anaconda's UI if I know kickstart will continue functioning. -sv -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Cryptically zoned out Firewall
On 11/06/2012 07:55 AM, Thomas Woerner wrote: On 11/06/2012 04:26 PM, Thomas Woerner wrote: On 11/06/2012 01:07 AM, Chuck Forsberg WA7KGX N2469R wrote: The new firewall replaces the old trusted interface with multiple zones . This would be fine if one could easily tell which zone each network interface was in and make changes. firewalld is not selecting the zone for an interface related to a connection. NetworkManager does this. The zone is set in the ifcfg config file, if it is not the default zone. The only to change an interface's zone is with an arcane firewall-cmd incantation. There is a patch for the gtk nm-connection-editor to add a very simple selection menu for connections. The NM connection editor in KDE is providing support for this already. This has been integrated into network-manager-applet upstream and should hit Fedora soon. Within nm-connection-editor the zone for interfaces related to a connection can be changed. Given the new concepts of persistence and zones, the adminfirewall applet needs to present these concepts to the user in a clearly intuitive, easy to change way. Ok, the firewall-applet should provide information on how to do change zones for connections, I agree. The current view should be radio buttons. Each interface should have a selector for which zone it should be in. Finally, do we need so many zones? A default of two zones should suffice and be more understandable. At least don't show zones that aren't used. There are the base zones: block, drop, public, work and trusted. The other zones have been added on request. You can also add own zones according to your needs. Thomas It is a month later and and there is no apparent coordination on zones between Network Manager and firewall zones. Just now I tried to bring up firewall to see if it had a useful help option and all I got was a dbus error. If one can add zones at will, let's ship Firewall with two or three zones - say public, work, and trusted. And each network config GUI should have a GUI to assign a zone to each network interface. -- 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
systemd: Failed to initialize SELinux context: Permission denied
As one bitten by https://bugzilla.redhat.com/show_bug.cgi?id=858373 I was hoping to set SELinux back to enforcing on my F18 test box in order to provide feedback for https://admin.fedoraproject.org/updates/FEDORA-2012-19802/livecd-tools-18.13-1.fc18 . I've had SEL disabled for quite awhile on this box now because building images with livecd-creator was more important. Seeing that an update was available, I changed /etc/sysconfig/selinux for enforcing and rebooted and was promptly greeted with the message show in the subject. The box just hangs there at this message. I wasn't expecting this behavior -- figured livecd-creator would be as before or better. I guess for now I need to boot with selinux=0 unless someone has any suggestions for this problem. -- John Florian -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: systemd: Failed to initialize SELinux context: Permission denied
On Thu, Dec 06, 2012 at 12:03:20 -0500, john.flor...@dart.biz wrote: I wasn't expecting this behavior -- figured livecd-creator would be as before or better. I guess for now I need to boot with selinux=0 unless someone has any suggestions for this problem. It's normally better to use permissive mode than to disable selinux. You won't be required to relabel to turn selinux on. You will get logs of what accesses are being blocked, so that you can provide a better report on the problem and use a local policy fix if desired to work around the issue. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/06/2012 10:12 AM, Gene Czarcinski wrote: On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski g...@czarc.net wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y for-each-VG and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski g...@czarc.net wrote: OK, I boot up the live gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. Son of a gun! Booted up the install DVD on another system and it looks great! Partitions, LVs, other systems (it is multi-boot) just like the live one did. OK, there still seems to be some systems (at least mine) that does have a problem so I will collect what info I can and submit a bug report. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if reclaim was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
yum update failing for last 2 days....can't find any mirrors....
--- Package snakeyaml.noarch 0:1.11-1.fc19 will be installed -- Running transaction check --- Package jboss-jaxrpc-1.1-api.noarch 0:1.0.1-1.fc19 will be installed -- Processing Dependency: jboss-servlet-3.0-api for package: jboss-jaxrpc-1.1-api-1.0.1-1.fc19.noarch --- Package jboss-transaction-1.1-api.noarch 0:1.0.1-2.fc19 will be installed --- Package sisu.noarch 0:2.3.0-1.fc19 will be an update -- Processing Dependency: osgi(org.sonatype.sisu.guava) for package: sisu-2.3.0-1.fc19.noarch -- Running transaction check --- Package jboss-servlet-3.0-api.noarch 0:1.0.1-3.fc18 will be installed --- Package sisu.noarch 0:2.3.0-1.fc19 will be an update -- Processing Dependency: osgi(org.sonatype.sisu.guava) for package: sisu-2.3.0-1.fc19.noarch http://mirror.seas.harvard.edu/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found : http://mirror.seas.harvard.edu/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2 Trying other mirror. http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found : http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2 Trying other mirror. http://linux.mirrors.es.net/fedora/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found : http://linux.mirrors.es.net/fedora/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2 Trying other mirror. http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found : http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2 Trying other mirror. http://mirrors.syringanetworks.net/fedora/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found : http://mirrors.syringanetworks.net/fedora/development/rawhide/x86_64/os/repodata/e92b9ceb3d0f11e5812bdfbb7ad9f971e5c7b8d95712d9731da91131e49c1462-filelists.sqlite.bz2 Trying other mirror. -- Regards, Kevin Martin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Samba issue after yesterday
I don't have much time to spend troubleshooting this, but thought I'd ask if anyone else has run into it. I have a small samba share on my workstation that my group uses. I've been using AD authentication which has always worked without problem. Set it up using authconfig-tui and just filling in the usual For smb.conf again, pretty standard, this configuration worked in F17 and worked until I restarted the machine this morning. The update yesterday was to samba and friends, to 4-0.0-170.fc18.rc6.x86_64 I can join the domain run testjoin, but if I try smbclient -L //mymachine/share -Umyname%password (or -UDOMAIN/myname%password) I get NT authentication fail. As I said, I'm not going to spend much time troubleshooting--for the moment, just changed it (there are only three people who use it, all in IT, and all who know that F18 is experimental) for the moment to security by user--but I am wondering if anyone else has experienced it. So therefore, I won't be filing a bug report at this point--this is more a general inquiry as to whether anyone else has run into it or something similar. There is no iptables on the machine and selinux is disabled. Thanks for any answers to what I realize is not a very good question. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Will, wait. I'm really sorry. Willow: Buff, I'm storming off. It doesn't really work if you come with me. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Samba issue after yesterday
On Thu, Dec 06, 2012 at 01:05:23PM -0500, Scott Robbins wrote: smbclient -L //mymachine/share -Umyname%password (or -UDOMAIN/myname%password) I get NT authentication fail. As I said, I'm not going to spend much time troubleshooting--for the moment, just changed it (there are only three people who use it, all in IT, and all who know that F18 is experimental) for the moment to security by user--but I am wondering if anyone else has experienced it. I should add that I've checked the obvious, to the point where I am sure I am typing the password correctly, and all the usual tests, such as wbinfo -a myname%mypassword work. The errors are along the lines of session setup failed: NT_STATUS_LOGON_FAILURE. I realize that I haven't given anyone much to go on and reiterate that at this point, I'm just wondering if it's hit anyone else. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: You know, for someone who teaches human behavior, you might try showing some. Professor Walsh:It's not my job to coddle my students. Buffy: You're right. A human being in pain has nothing to do with your job. (leaves) Professor Walsh: I like her. Riley: Really? You don't think she's a little peculiar? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/06/2012 12:19 PM, Gene Czarcinski wrote: On 12/06/2012 10:12 AM, Gene Czarcinski wrote: On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski g...@czarc.net wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y for-each-VG and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski g...@czarc.net wrote: OK, I boot up the live gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. Son of a gun! Booted up the install DVD on another system and it looks great! Partitions, LVs, other systems (it is multi-boot) just like the live one did. OK, there still seems to be some systems (at least mine) that does have a problem so I will collect what info I can and submit a bug report. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if reclaim was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. The problem turned out to be an old mobo with an enabled floppy interface with nothing attached. Disable the interface in the BIOS and things work. However, that should not have hung up the install. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode? (Re: community etiquette (Re: Rename anaconda to cryptoconda?))
On Dec 5, 2012, at 10:44 PM, Adam Williamson awill...@redhat.com wrote: On Wed, 2012-12-05 at 22:00 -0700, Chris Murphy wrote: On Dec 4, 2012, at 5:58 PM, Adam Williamson awill...@redhat.com wrote: I don't know why you'd expect a 'partition assignment only' mode to exist, given that there wasn't one in F17 and there was no indication of one in any of the design documents for newui. Maybe it's expected because 95% of the world's desktop/server OS's have this option. Erm. Really? Are you sure we're not talking at cross-purposes here? I'm not sure I recall seeing any installer other than Mandriva's which offers a special version of its partitioning interface where you cannot create or remove partitions, only select mount points for existing partitions. That is what the OP is describing. It is a crudely different interface, but the concept is identical to what I'm talking about. Windows and OS X present properly formatted volumes as install destinations for the user to choose from. No repartitioning or reformatting is required. And this means an overwhelming majority of basic and advanced user requirements. And done in one screen. And maybe it's expected because it actually works with a very simple and discoverable UI for both basic and advanced user needs. Let's rephrase the question, open to the whole list: why is a point and shoot install to a volume (or partition) such a bad idea that it isn't even an option in anaconda? I'm not sure that question makes any sense in context. The context is that other installers do have such capability, and front and center, this one doesn't. So why not? Reuse of existing partitions/volumes is possible, but limited, and totally buried: click 1 and click 2= get to Manual Partitioning. Click 3= reveal your partitions. Click 4= choose the partition you want to reuse. Click 5= choose a mount point. Click 6= reveal custom options. Click 7= check reformat which is not actually custom or an option, it's a requirement by anaconda. Why am I required to reformat? It prevents me from using file system options set at format time. The basic user who simply wants to reuse a partition or volume needs to go through 7 really non-discoverable clicks, and the expert can't even do what he wants unless he learns kickstart. Both requirements solved by point and shoot to a valid partition/volume, presented and selected in a single window. Why is the first thing we do choosing a device, rather than a partition or a volume? Because people find it very valuable to be able to leave certain disks out of the installation and be entirely sure they will not be touched by the install process… By choosing a partition they are giving permission, nothing else has permission to be modified. It's the very same concept as with a disk, with a finer granularity. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode?
On Dec 6, 2012, at 12:34 AM, Felix Miata mrma...@earthlink.net wrote: On 2012-12-05 21:44 (GMT-0800) Adam Williamson composed: On Wed, 2012-12-05 at 22:00 -0700, Chris Murphy wrote: Why is the first thing we do choosing a device, rather than a partition or a volume? Because people find it very valuable to be able to leave certain disks out of the installation and be entirely sure they will not be touched by the install process... I found the screen confusing, because: 1-The system had only one HD. 2-IIRC: selected state wasn't instantly recognizable. Repeated clicks on it toggled selected state on and off. Only after several did I figure selected out, and why the reaction to a click on the lower left link produced inexplicable responses. I suspect the overwhelmingly majority of installations are 1-2 disks. I imagine the first window showing partitions/volumes and the instruction is: choose at least one partition/volume for your Fedora installation, or choose Show More Options. More options can include iSCSI, FCoE, whole disks, whatever. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode?
On 2012-12-06 14:38 (GMT-0700) Chris Murphy composed: Why am I required to reformat? It prevents me from using file system options set at format time. Justification: https://bugzilla.redhat.com/show_bug.cgi?id=629311 cf. https://bugzilla.redhat.com/show_bug.cgi?id=810022 -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Canon printer/scanner driver installation problem Fedora 18 Beta
On Thu, Dec 06, 2012 at 01:22:52AM -0500, Joerg Lechner wrote: Thank You for Your help. I found libpng12.so.0in the Rawhide package (libpng12-1.2.50-2.fc19.i686.rpm). For libtiff.so.3 so far I found nothing, # yum provides '*/libtiff.so.3' libtiff-compat-4.0.2-5.fc18 As Adam suggested if you will do yum install scangearmp-common-1.20-1.i386.rpm instead of rpm -U scangearmp-common-1.20-1.i386.rpm then yum should find required libraries by itself (that on an assumption that you are running on 32-bits; if not then you would have to add 32-bit repositories to a set searched by yum). A presence of libtiff-compat strongly indicates that there is no conflict between the current libtiff and libtiff.so.3 so all fun-and-games with LD_LIBRARY_PATH is not needed as correct libraries will be linked in a default configuration. Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode?
On Dec 6, 2012, at 3:02 PM, Felix Miata mrma...@earthlink.net wrote: On 2012-12-06 14:38 (GMT-0700) Chris Murphy composed: Why am I required to reformat? It prevents me from using file system options set at format time. Justification: https://bugzilla.redhat.com/show_bug.cgi?id=629311 Fedup doesn't require a reformat of root, does it? If not, why is that OK, but new installs need not merely a formatted file system, but a formatted file system done expressly and only by anaconda? To properly install to hardware RAID 0 or RAID 5 I have to use kickstart? That is absurd. And then there's the case of Btrfs which makes this untenable policy also, twice: 1. A Btrfs volume is compromised of one or more devices, it makes no sense to show me devices, but rather the volume. And I cannot reformat such a volume in the normal use case because by nature of that file system I can contain one or more OS's in their own subvols. The policy described in the bug above, in a Btrfs context, is as untenable as saying you must lose all of your partitions in order to install Fedora, or learn kickstart. (!) I'm seriously getting sand in my hoo ha now. 2. Anaconda's current default behavior for Btrfs installs, puts home in a Btrfs subvolume. Not on a separate partition. So this presents a contradiction. Either F19's anaconda needs to allow reuse of a Btrfs volume without reformatting it, or admit that F18's anaconda is making the wrong default recommendation. So which is it? Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Failed login popup?
- Original Message - When the login screen comes up, I get a popup saying: Failed login from my system at work Anyone know where this comes from? I'd like to make it go away. It is always going to be caused by my system at work attempting to ssh into my system at home, and I haven't yet installed the proper ssh authorized users and wot-not that it needs to succeed on fedora 18. Can you file a bug against gdm ? That is probably something we want to suppress. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new criterion proposal: core kickstart commands
On Thu, 2012-12-06 at 11:29 -0500, Seth Vidal wrote: On Thu, 6 Dec 2012, Matthew Miller wrote: On Wed, Dec 05, 2012 at 09:39:41PM -0800, Adam Williamson wrote: I think that may be the case _now_ with our current Anaconda situation, but the more I think about it, the more strongly I feel about making this the approach for future releases. When there's _not_ a big Anaconda rewrite, kickstart commands shouldn't change drastically without planning. So, I don't think it's unreasonable in the real world. The commands themselves shouldn't change, but it's certainly possible - and frequently happens - for something to change in anaconda or some layer below anaconda which happens to have the effect of breaking a kickstart directive. ... which should be a blocker. I agree with Matt. Kickstart is not only a lowest common denominator it is a critical functionality for tons of our testing and deployment tools. We don't want revolutionary change in kickstart and we definitely cannot have it be broken. Slow, gradual change properly documented is critical for kickstart. I'm less concerned about changes in anaconda's UI if I know kickstart will continue functioning. Do I see two volunteers to help fix kickstart bugs? :) -- 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: new criterion proposal: core kickstart commands
On Thu, Dec 6, 2012 at 7:41 PM, Adam Williamson awill...@redhat.com wrote: Do I see two volunteers to help fix kickstart bugs? :) If it came down to crunch time, and a kickstart bug was keeping us from being able to do a release, you bet I'd volunteer to help fix the kickstart bug. -- Jared Smith -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 16 updates-testing report
The following Fedora 16 Security updates need testing: Age URL 76 https://admin.fedoraproject.org/updates/FEDORA-2012-14452/bacula-5.0.3-33.fc16 4 https://admin.fedoraproject.org/updates/FEDORA-2012-19538/weechat-0.3.9.2-2.fc16 49 https://admin.fedoraproject.org/updates/FEDORA-2012-16415/389-ds-base-1.2.10.16-1.fc16 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19822/bind-9.8.4-3.P1.fc16 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19823/mysql-5.5.28-2.fc16 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19828/xen-4.1.3-6.fc16 33 https://admin.fedoraproject.org/updates/FEDORA-2012-17553/libproxy-0.4.10-1.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19347/cups-1.5.4-10.fc16 154 https://admin.fedoraproject.org/updates/FEDORA-2012-10314/revelation-0.4.14-1.fc16 74 https://admin.fedoraproject.org/updates/FEDORA-2012-14654/tor-0.2.2.39-1600.fc16 13 https://admin.fedoraproject.org/updates/FEDORA-2012-18927/cups-pk-helper-0.1.3-4.fc16 55 https://admin.fedoraproject.org/updates/FEDORA-2012-16032/cobbler-2.4.0-beta2.fc16 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19227/squashfs-tools-4.2-5.fc16 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19449/drupal6-ctools-1.10-1.fc16 37 https://admin.fedoraproject.org/updates/FEDORA-2012-17291/thunderbird-16.0.2-1.fc16 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19455/php-symfony2-HttpFoundation-2.0.19-1.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19715/qt-4.8.4-1.fc16 8 https://admin.fedoraproject.org/updates/FEDORA-2012-18330/perl-CGI-3.52-203.fc16,perl-5.14.3-203.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19740/bogofilter-1.2.3-1.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19752/dovecot-2.0.21-4.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19750/kernel-3.6.9-2.fc16 15 https://admin.fedoraproject.org/updates/FEDORA-2012-18661/firefox-17.0-1.fc16,xulrunner-17.0-3.fc16,thunderbird-enigmail-1.4.6-2.fc16,thunderbird-lightning-1.9-1.fc16,thunderbird-17.0-1.fc16 The following Fedora 16 Critical Path updates have yet to be approved: Age URL 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19917/mdadm-3.2.6-3.fc16 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19823/mysql-5.5.28-2.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19750/kernel-3.6.9-2.fc16 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19715/qt-4.8.4-1.fc16 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19471/xulrunner-17.0.1-1.fc16,firefox-17.0.1-1.fc16 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19486/phonon-backend-gstreamer-4.6.2-2.fc16 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19265/lxpanel-0.5.10-3.fc16 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19227/squashfs-tools-4.2-5.fc16 13 https://admin.fedoraproject.org/updates/FEDORA-2012-18927/cups-pk-helper-0.1.3-4.fc16 8 https://admin.fedoraproject.org/updates/FEDORA-2012-18330/perl-CGI-3.52-203.fc16,perl-5.14.3-203.fc16 The following builds have been pushed to Fedora 16 updates-testing OmegaT-2.3.0_06-2.fc16 csmith-2.1.0-7.fc16 ghc-vector-0.7.1-4.fc16 h5py-2.1.0-1.fc16 mdadm-3.2.6-3.fc16 postgresql-9.1.7-1.fc16 rubygem-systemu-2.5.2-1.fc16 Details about builds: OmegaT-2.3.0_06-2.fc16 (FEDORA-2012-19890) Computer Aid Translation tool Update Information: fixing #884212 ChangeLog: * Thu Dec 6 2012 Ismael Olea ism...@olea.org - 2.3.0_06-2 - update hunspell patch to 1.3.* * Mon Feb 6 2012 Ismael Olea ism...@olea.org - 2.3.0_06-1 - updating to 2.3.0_06 - removing patch OmegaT-fix-encoding-java7.patch since is now in upstream - cosmetic changes * Thu Jan 12 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org - 2.3.0_03-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild * Tue Nov 22 2011 ism...@olea.org - 2.3.0_03-2 - added OmegaT-fix-encoding-java7.patch: java 1.7 now managed as error encoding typos References: [ 1 ] Bug #884212 - Spell-checking does not work because of missing libhunspell https://bugzilla.redhat.com/show_bug.cgi?id=884212 csmith-2.1.0-7.fc16 (FEDORA-2012-19919) Tool to generate random C programs for compiler testing Update Information: - fix build on all arches by adding
Fedora 17 updates-testing report
The following Fedora 17 Security updates need testing: Age URL 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19442/php-symfony2-HttpFoundation-2.1.4-1.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19717/xen-4.1.3-7.fc17 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19830/bind-9.9.2-3.P1.fc17 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19833/mysql-5.5.28-2.fc17 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19892/librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 4 https://admin.fedoraproject.org/updates/FEDORA-2012-19533/weechat-0.3.9.2-2.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19341/openstack-keystone-2012.1.3-3.fc17 74 https://admin.fedoraproject.org/updates/FEDORA-2012-14650/tor-0.2.2.39-1700.fc17 13 https://admin.fedoraproject.org/updates/FEDORA-2012-18950/cups-pk-helper-0.2.2-2.fc17 55 https://admin.fedoraproject.org/updates/FEDORA-2012-16048/cobbler-2.4.0-beta2.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19606/cups-1.5.4-16.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19203/squashfs-tools-4.2-5.fc17 154 https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19464/drupal6-ctools-1.10-1.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19705/bogofilter-1.2.3-1.fc17 2 https://admin.fedoraproject.org/updates/FEDORA-2012-19605/totpcgi-0.5.4-1.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19282/perl-CGI-3.52-218.fc17,perl-5.14.3-218.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19726/mate-settings-daemon-1.5.4-1.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19759/qt-4.8.4-1.fc17 The following Fedora 17 Critical Path updates have yet to be approved: Age URL 0 https://admin.fedoraproject.org/updates/FEDORA-2012-19916/mdadm-3.2.6-3.fc17 1 https://admin.fedoraproject.org/updates/FEDORA-2012-19759/qt-4.8.4-1.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19496/control-center-3.4.3-1.fc17,libwacom-0.6.1-1.fc17,gnome-settings-daemon-3.4.2-4.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2012-19446/phonon-backend-gstreamer-4.6.2-2.fc17 7 https://admin.fedoraproject.org/updates/FEDORA-2012-19344/xorg-x11-drv-intel-2.20.14-1.fc17 7 https://admin.fedoraproject.org/updates/FEDORA-2012-19350/ModemManager-0.6.0.0-2.fc17 7 https://admin.fedoraproject.org/updates/FEDORA-2012-19354/xfwm4-4.8.3-3.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19262/bash-4.2.39-2.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19282/perl-CGI-3.52-218.fc17,perl-5.14.3-218.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19208/lxpanel-0.5.10-3.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-19203/squashfs-tools-4.2-5.fc17 11 https://admin.fedoraproject.org/updates/FEDORA-2012-19048/json-c-0.10-2.fc17 11 https://admin.fedoraproject.org/updates/FEDORA-2012-19014/json-c-0.10-1.fc17 11 https://admin.fedoraproject.org/updates/FEDORA-2012-19006/nss-util-3.14-1.fc17,nss-softokn-3.14-5.fc17,nss-3.14-7.fc17 13 https://admin.fedoraproject.org/updates/FEDORA-2012-18950/cups-pk-helper-0.2.2-2.fc17 13 https://admin.fedoraproject.org/updates/FEDORA-2012-18937/kdelibs-4.9.3-4.fc17 8 https://admin.fedoraproject.org/updates/FEDORA-2012-18850/cronie-1.4.10-1.fc17 0 https://admin.fedoraproject.org/updates/FEDORA-2012-18542/dnsmasq-2.64-1.fc17 2 https://admin.fedoraproject.org/updates/FEDORA-2012-18329/abrt-2.0.19-2.fc17,libreport-2.0.19-3.fc17,btparser-0.23-1.fc17 The following builds have been pushed to Fedora 17 updates-testing OmegaT-2.3.0_06-4.fc17 csmith-2.1.0-7.fc17 fedmsg-0.6.3-1.fc17 gfal2-2.1.0-2.fc17 ghc-data-inttrie-0.0.8-1.fc17 ghc-vector-0.9.1-7.fc17 h5py-2.1.0-1.fc17 librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 libteam-0.1-23.20121206git659a848.fc17 mate-power-manager-1.5.1-3.fc17.1 mcollective-qpid-plugin-1.1.1-1.fc17 mdadm-3.2.6-3.fc17 mspdebug-0.21-2.fc17 openshift-origin-cartridge-abstract-1.1.7-1.fc17 openshift-origin-cartridge-cron-1.4-1.1.3-1.fc17 openshift-origin-cartridge-diy-0.1-1.1.4-1.fc17 pam_url-0.3.2-2.fc17 perl-ExtUtils-CppGuess-0.07-3.fc17 perl-SNMP-Info-2.09-1.fc17 postgresql-9.1.7-1.fc17 python-logutils-0.3.2-1.fc17 rubygem-cairo-1.12.3-1.fc17 rubygem-gdk_pixbuf2-1.1.6-1.fc17 rubygem-gio2-1.1.6-1.fc17 rubygem-glib2-1.1.6-1.fc17 rubygem-goocanvas-1.1.6-1.fc17 rubygem-gstreamer-1.1.6-1.fc17 rubygem-gtk2-1.1.6-1.fc17 rubygem-gtksourceview2-1.1.6-1.fc17 rubygem-openshift-origin-auth-mongo-0.8.9-1.fc17 rubygem-openshift-origin-dns-bind-0.8.12-1.fc17 rubygem-openshift-origin-msg-broker-mcollective-1.1.6-2.fc17 rubygem-pango-1.1.6-1.fc17
Re: systemd: Failed to initialize SELinux context: Permission denied
On Thu, Dec 06, 2012 at 15:39:55 -0500, john.flor...@dart.biz wrote: Yeah, if I was actually worried about security in this case, that would've been my usual approach. I had it turned off to bring greater visibility to other errors long before F18 alpha and was waiting for this BZ to move along before worrying further about SELinux again. So do I just need to do a relabel at this point? Once you boot with selinux enabled, a relabel should happen automatically. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Reclaim disk space doesn't reuse existing swap, should it?
A partition in either MBR/GPT is set to the partition type for Linux swap, but Reclaim space considers it Unknown and won't automatically use it. Bug? Feature request? Seems like autopart should just figure this out automatically and use it rather than a.) considering it unknown; b.) making a new one just for Fedora. Is it considered acceptable to reuse one swap for multiple linux OS's? I'm pretty sure I'd read that LiveCD's will use an available swap partition on a local disk, if available. If so it seems multiple linux distros can use a single swap partition rather than each having their own. True/False? Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: why not a partition assignment mode? (Re: community etiquette (Re: Rename anaconda to cryptoconda?))
On Thu, 2012-12-06 at 14:38 -0700, Chris Murphy wrote: click 1 and click 2= get to Manual Partitioning. Click 3= reveal your partitions. Click 4= choose the partition you want to reuse. Click 5= choose a mount point. Click 6= reveal custom options. Click 7= check reformat which is not actually custom or an option, it's a requirement by anaconda. Why am I required to reformat? It prevents me from using file system options set at format time. The basic user who simply wants to reuse a partition or volume needs to go through 7 really non-discoverable clicks, and the expert can't even do what he wants unless he learns kickstart. Both requirements solved by point and shoot to a valid partition/volume, presented and selected in a single window. I'm not sure that your assumption that 'basic users' just want to reuse a partition really holds true. It's not a hugely common use case in my experience, and tends to be more popular among *experienced* users, who have a favourite partition scheme or tool or whatever. But without any data, we're just comparing theories... -- 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: selinux-policy-3.11.1-57 and 3.11.1-58 breaking access to 'storage' drives
On Fri, 2012-12-07 at 17:46 +1100, Ankur Sinha wrote: On Mon, 2012-12-03 at 12:53 -0600, Bruno Wolff III wrote: In bohdi, people have reported that -59 fixed the problem going forward. But people already affected need to relabel. Looks like I got caught with this one. However, the updated and a relabel isn't working for me. My USB attached HDDs are still unusable: Miroslav is asking us to try -60 now. -- 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
