You (yes, YOU) can now definitely nominate blocker bugs
Exciting news from the fast-moving world of RH Bugzilla administration: a mere, fleeting year and a half after I filed the initial request, it is finally the case that any registered Bugzilla user can now change the Blocks: (and Depends On:) field of any Fedora bug! Thanks to Matt Tyson for doing this at last. What this means is you no longer need editbugs privileges to be able to propose blocker bugs. This was never intended to be the case, it was only an unfortunate consequence of the mechanism used for nominating bugs as blockers. Now anyone with a BZ account can follow the instructions at https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process to nominate a bug as a release blocker, or https://fedoraproject.org/wiki/QA:SOP_nth_bug_process to nominate one as 'NTH' (which means it does not block release, but freeze can be broken to take a fix for the bug: it denotes bugs important enough to merit freeze breaks). To nominate a bug as a blocker for F18 final, for instance, mark it as blocking the bug 'F18Blocker'. Please use these powers wisely! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On 11/26/2012 12:15 PM, Richard W.M. Jones wrote: You're asking for something very open-ended, and which is not even possible to implement in general -- what if the inspecting operating system is Linux, and the inspected operating system needs custom Mac OS X libraries? Perhaps I am just dense, but I can't follow you. I can't see how this is related to my latest post. And I can't see what leads you to think that cross-platform scanning is feasible today (standard-wise and performance-wise). In any case, the correct place to request this is with the SCAP standards team. Which request? Where did I requested something which has been bind to the SCAP? I only asked for an interface in a distribution. Regards, -- Simon Lukasik -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-18 Branched report: 20121128 changes
Compose started at Wed Nov 28 09:15:37 UTC 2012 Broken deps for x86_64 -- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.x86_64 requires znc = 0:0.206 Broken deps for i386 -- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.i686 requires znc = 0:0.206 Removed package: mod_pubcookie-3.3.4a-7.fc18 Summary: Added Packages: 0 Removed Packages: 1 Upgraded Packages: 0 Compose finished at Wed Nov 28 13:33:52 UTC 2012 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On Wed, Nov 28, 2012 at 01:43:48PM +0100, Simon Lukasik wrote: On 11/26/2012 12:15 PM, Richard W.M. Jones wrote: You're asking for something very open-ended, and which is not even possible to implement in general -- what if the inspecting operating system is Linux, and the inspected operating system needs custom Mac OS X libraries? Perhaps I am just dense, but I can't follow you. I can't see how this is related to my latest post. And I can't see what leads you to think that cross-platform scanning is feasible today (standard-wise and performance-wise). It's exactly what we plan to do with libguestfs openscap. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Schedule for Wednesday's FESCo Meeting (2012-11-28)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 17:00UTC (1:00pm EDT, 19:00 CEST) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #966 Fedora 19 Schedule proposal (DRAFT!) .fesco 966 https://fedorahosted.org/fesco/ticket/966 = New business = #topic #974 Allow releases on Wed and Thu as well .fesco 974 https://fedorahosted.org/fesco/ticket/974 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Schedule for Wednesday's FESCo Meeting (2012-11-28)
One more addition: On Wed, Nov 28, 2012 at 2:51 PM, Miloslav Trmač m...@volny.cz wrote: = Followups = #topic #896 Refine Feature process .fesco 896 https://fedorahosted.org/fesco/ticket/896 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-18 Branched report: 20121128 changes
Dne 28.11.2012 14:38, Fedora Branched Report napsal(a): Compose started at Wed Nov 28 09:15:37 UTC 2012 Broken deps for x86_64 -- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.x86_64 requires znc = 0:0.206 Spot, This is amazingly short list of broken dependencies. Thank you for the effort. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [fedora-java] broken compatibility from jna-3.4.0 to 3.5.0
Quoting Ismael Olea (2012-11-27 16:24:26) We have seen such problems many times in many packages. Usually adding a dummy method just to satisfy the signature is enough though in this case it might not be. I see. Please report it to svnkit developers too. Done: http://issues.tmatesoft.com/issue/SVNKIT-329 Ccing devel so that audience is bigger (I believe this deserves it) Just for future reference. What you have written in upstream bugreport is basically: I have tried to build your software in unsupported way (ant vs gradle) and used different versions of your dependencies and it failed. I've done it because other project has some silly rules. Can you fix it?. Upstream might or might not realize what you are asking for is a simple dependency bump with API fix (most likely). And they can get annoyed by your request (some upstreams definitely would). To be precise, this situation is not a bug in upstream at all, but it is caused by us (Fedora as a distribution). Therefore it's more of a RFE as far as upstream is concerned. RFEs written as bugreports can be hard to sell. This is not just for your benefit. I've seen several such bugreports from Fedora contributors. They can sometimes make dealing with upstreams difficult, so please be careful with the wording. -- Stanislav Ochotnicky sochotni...@redhat.com Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-18 Branched report: 20121128 changes
On 11/28/2012 09:17 AM, Vít Ondruch wrote: Dne 28.11.2012 14:38, Fedora Branched Report napsal(a): Compose started at Wed Nov 28 09:15:37 UTC 2012 Broken deps for x86_64 -- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.x86_64 requires znc = 0:0.206 Spot, This is amazingly short list of broken dependencies. Thank you for the effort. Even better news is that: * dhcp-forwarder update is pending stable: https://admin.fedoraproject.org/updates/FEDORA-2012-18155/dhcp-forwarder-0.10-1804.fc18 * gcc-python-plugin update is pending testing: https://admin.fedoraproject.org/updates/gcc-python-plugin-0.9-7.fc18 * kfaenza-icon-theme update is pending stable: https://admin.fedoraproject.org/updates/FEDORA-2012-17955/kfaenza-icon-theme-0.8.9-3.fc18 That just leaves us with znc-infobot. It was on my list of packages to kill off, but the maintainer plead with me to hold off, so I did. Nevertheless, there has yet to be a successful build of this package for Fedora 18 or 19 (due to the update of znc to 1.0), and the last attempt was on 2012-11-14. BUT: I gave it a fresh look and was able to fix it up. I did basic smoke testing to ensure that the module loads, but since I'm not a znc user, I'm not sure if everything still works as expected. Testing is appreciated. https://admin.fedoraproject.org/updates/znc-infobot-1.0-2.fc18 ... and with that, we might, maybe, reach 0 broken deps on F18! ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora ARM weekly status meeting - 2012-11-28
Good day all, This weeks Fedora ARM status meeting will take place today (Wednesday Nov 28th) in #fedora-meeting-1 on Freenode. Times in various time zones (please let us know if these do not work): PDT: 1pm MDT: 2pm CDT: 3pm EDT: 4pm UTC: 8pm BST: 9pm CST: 10pm Current items on the agenda: 1) Current Problem packages 2) F18 ARM Beta - target release date, vfad planning, Raspberry Pi 3) Kirkwood image testing - volunteers? 4) 3.7 Kernel and Device tree - support plan 5) Mirror syncing 6) Your topic here If you have any other items you would like to discuss that are not mentioned, please feel free to send an email to the list or bring it up at the end of the meeting. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
Hi Simon, On 28.11.2012 14:43, Simon Lukasik wrote: I can't see how this is related to my latest post. And I can't see what leads you to think that cross-platform scanning is feasible today (standard-wise and performance-wise). Please check this very informative post from Steve (OVAL board member): http://www.mail-archive.com/devel@lists.fedoraproject.org/msg50625.html We (the camp arguing for flexible configurations) should identify clever proposal at least conforming the following: * Will be able to be cold (statically) assessed through current or future OVAL (first and most important use-case - VM images evaluation, second - augeas and alike on the live systems, third - custom auditing agents) * Will looks cool for the sysadmins (the config languages users) (I am in doubt that any traditional scripting language will bring high score on this criteria) * Will enable desired (for the non-trivial cases) flexibility Kind regards, Alek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora ARM weekly status meeting - 2012-11-28
I'm not going to be able to make the meeting. This weeks Fedora ARM status meeting will take place today (Wednesday Nov 28th) in #fedora-meeting-1 on Freenode. Times in various time zones (please let us know if these do not work): PDT: 1pm MDT: 2pm CDT: 3pm EDT: 4pm UTC: 8pm BST: 9pm CST: 10pm Current items on the agenda: 1) Current Problem packages texlive and ruby for both rawhide and F-18 are the current blockers. The former is critical for rawhide and becoming more so for F-18. 2) F18 ARM Beta - target release date, vfad planning, Raspberry Pi The Raspberry is completely unrelated to mainline beta and as a result should be uncoupled from this item. 3) Kirkwood image testing - volunteers? 4) 3.7 Kernel and Device tree - support plan I've a build issue with rc7 that I'm been working with jonmasters on to resolve. Should have rc7 RSN. 5) Mirror syncing 6) Your topic here Koji: There have been a number of issues over the last couple of weeks that have been bought up and I haven't seen any form of update from Seneca as to the state: - DB perf tuning, it was done or at least there was an outage. What was the outcome - repo issues (the generally perl based build failures due to repo issues). I reported I thought I had found the offending host but the issue appears to have come back. Was the host re-enabled, what testing has Seneca done? - builder issues, seeing issues with things like the disk space on the large builders without a resolution, or a resolution being reported. What is the status, is it fixed? - Some people have remote access to the builders via a ssh key but it appears that not all build hosts are configured for this. What's the steps to resolution so that people can support the platform? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) evas - Canvas and scenegraph rendering library. In Fedora as evas (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore (I own it) embryo - Small Pawn based virtual machine and compiler. edje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping and glue layer library. eeze - Device abstraction library. elementary - Elementary, the widget set... emotion - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
RFC: Feature process improvements
Hello, this proposal was recently linked in various places, so let's formally introduce it: https://fedoraproject.org/wiki/User:Mmaslano/Feature_process This an incremental change, not a major overhaul designed to solve all problems. The benefits expected from this proposal: * Making proposed features more visible to Fedora contributors, and making it easier for Fedora contributors to discuss the feature before FESCo votes on it. * Simplifying the process for self-contained features (e.g. individual package version upgrades) * Getting FESCo more involved in scheduling and testing of features with large impact on the rest of the distribution or schedule. * Making sure some frequently forgotten-about items, like rel-eng impact, are included in the feature proposal. For details, please see the proposal at the above-mentioned link. Marcela Mašláňová, Tomáš Mráz, Jaroslav Řezník, Miloslav Trmač -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
It's not clear where this should be discussed? Editing the wiki talk page? On this list? Anyway, I'll kick this off by saying: * Simplifying the process for self-contained features (e.g. individual package version upgrades) I don't see why these are features at all. Surely it's better towards the end of each release cycle for someone to compare the versions of packages and add something in the release notes for each major GUI / programming language / user application that got a big update. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: You (yes, YOU) maybe can't yet definitely nominate blocker bugs
On Wed, 2012-11-28 at 01:45 -0800, Adam Williamson wrote: Exciting news from the fast-moving world of RH Bugzilla administration: a mere, fleeting year and a half after I filed the initial request, it is finally the case that any registered Bugzilla user can now change the Blocks: (and Depends On:) field of any Fedora bug! Thanks to Matt Tyson for doing this at last. What this means is you no longer need editbugs privileges to be able to propose blocker bugs. This was never intended to be the case, it was only an unfortunate consequence of the mechanism used for nominating bugs as blockers. Now anyone with a BZ account can follow the instructions at https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process to nominate a bug as a release blocker, or https://fedoraproject.org/wiki/QA:SOP_nth_bug_process to nominate one as 'NTH' (which means it does not block release, but freeze can be broken to take a fix for the bug: it denotes bugs important enough to merit freeze breaks). To nominate a bug as a blocker for F18 final, for instance, mark it as blocking the bug 'F18Blocker'. Please use these powers wisely! Sadly, I have now been informed that the change has only gone to staging and won't be in production until January. Mark your calendars, folks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Help Wanted] Which package provide the System Module for rawhide
Halli, I'm trying to build the kaya package for the rawnide branch of Fedora. Unfortunately, I have got the following error messages during the build process: make -C compiler make[1]: Entering directory `/builddir/build/BUILD/kaya-0.5.2/compiler' /usr/bin/happy -g -a -c ./Parser.y -iParser.out -oParser.hs unused terminals: 2 g++ -fPIC -fno-rtti -Wall -O2 -DNDEBUG -Wno-deprecated -I. -c -o repl_load.o repl_load.cc /usr/bin/ghc --make -fglasgow-exts ./Main.hs repl_load.o -pgml g++ -o kayac -i. -odir . on the commandline: Warning: -fglasgow-exts is deprecated: Use individual extensions instead Main.hs:31:8: Could not find module `System' It is a member of the hidden package `haskell98-2.0.0.1'. Use -v to see a list of the files searched for. It may be nice, if anyone can tell me in which package I could find the missed System module. Thanks in advance. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rawhide report: 20121128 changes
On 11/28/2012 06:32 AM, Fedora Rawhide Report wrote: [yum-cron] yum-cron-0.9.2-6.fc19.noarch requires yum-downloadonly Looks like the yum-cron package was never retired from the distribution. https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Announcing the release of Fedora 18 Beta!!!
The Fedora 18 Spherical Cow Beta release is rolling! This release offers a preview of some of the best free and open source technology currently under development. We are delighted to announce the availability of the beta release of Fedora 18. Want to get a taste of the future? Download it now: http://fedoraproject.org/get-prerelease *** What is the Beta Release? *** The Beta release is the last important milestone of Fedora 18. Only critical bug fixes will be pushed as updates leading to the general release of Fedora 18 in the beginning of the next year. We invite you to join us in making Fedora 18 a solid release by downloading, testing, and providing your valuable feedback. Of course, this is a beta release, meaning that some problems may still be lurking. A list of the problems we already know about is found at the Common F18 bugs page, seen here: http://fedoraproject.org/wiki/Common_F18_bugs There is a new upgrade system for Fedora 18 making its first appearance in Fedora 18 Beta. Upgrading via the system installer or the preupgrade tool is no longer possible. To upgrade to Fedora 18 from Fedora 17, you should use the new Fedup tool. Instructions and information on the new tool are here: http://fedoraproject.org/wiki/FedUp. The tool is still under active development, please take a look at the FedUp FAQ (in the wiki page) in case of any issues with the upgrade process, and back up your system before trying the upgrade. *** Features *** This release of Fedora includes a variety of features both over and under the hood that show off the power and flexibility of the advancing state of free software. Here are just a few of the new features: = For users everywhere = * Fedora 18 offers a brand-new version of the Gnome desktop, version 3.6, straight from the upstream development process. Updates have also been made to the KDE Plasma Workspaces, XFCE and Sugar]desktop environments; additionally, the MATE desktop is available for the first time in Fedora. * Fedora's new installer user interface enhances the anaconda installer with improvements in ease of use and installation. = For developers = * This release includes several language updates, including the move to Perl 5.16, updating the Python 3 stack from 3.2 to 3.3, Rails 3.2 and updated D and Haskell programming environments. = For system administrators = * Fedora 18 includes the final release of Samba 4, and can be used on an Active Directory domain member out of the box. An integrated, new native management software allows you to access data and server information easily. * OpenStack in Fedora 18 has been updated to Folsom, the most recent release by the OpenStack community. This Infrastructure-as-a-Service (IaaS) platform enables the creation and management of cloud infrastructure. * Eucalyptus 3.1, another IaaS platform, is available in Fedora for the first time, and includes the major components of Eucalyptus. * System Storage Management CLI tools simplify the user interface by providing unified abstraction and interface for multiple storage technologies, including lvm, btrfs and md raid. For more Features, please take a look on the complete list: http://fedoraproject.org/wiki/Releases/18/FeatureList *** Contributing *** Great releases like Fedora 18 don't get made in a vacuum. We can't do it without you! Bug reports are especially helpful as we move from the theory to the applied physics. If you encounter any issues, please report them! Fedora is a fantastic, friendly community, and we have many ways in which you can contribute, including Documentation, Marketing, Design, QA, Development, and more. To learn how to help us, visit: http://join.fedoraproject.org/ Thank you, and we hope to see you in the Fedora Project! --- You may notice this announcement is a day late! We'd like to apologize to the community for the delayed announcement and any consequences resulting from the delay. ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
Once upon a time, Richard W.M. Jones rjo...@redhat.com said: * Simplifying the process for self-contained features (e.g. individual package version upgrades) I don't see why these are features at all. Surely it's better towards the end of each release cycle for someone to compare the versions of packages and add something in the release notes for each major GUI / programming language / user application that got a big update. Rather than make someone review a whole bunch of stuff, it would be much easier for maintainers to submit what they are doing. Frankly, if a maintainer doesn't think it is worth their while to announce a major change, then it isn't worth someone else's time to sift through the whole distribution and look for notable changes. -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
I don't see why these are features at all. Surely it's better towards the end of each release cycle for someone to compare the versions of packages and add something in the release notes for each major GUI / programming language / user application that got a big update. Rich. I only have a comment relative to the release notes. I agree that the release notes are the appropriate place to 'feature' changes that might not meet the requirements of a 'Feature' . Comparing the version numbers is even relatively easy - we use a script for the Technical Notes that parses repository sqlite meta data and effectively spits out the fully formed TNs. This doesn't scale well to the verbose content expected in the release notes. A human still needs to identify changes, apply context, interpret scope and write the actual content. Determining what should be included and what changed is labor intensive. There are several mechanisms for a developer to get their work into the release notes. The rel-notes BZ tag was wholly unused during this cycle, to the best of my knowledge. There were no bugs filed against the release-notes bugzilla product to request inclusion. When no emails were sent to the Docs mailing list, we put out a request on devel-announce for developers to get in touch; the only person that responded already had a well composed Feature page for us to work from. So here's my suggestion : The guidelines for Features, however they turn out, should direct developers to contacting the Docs team in some way if the feature requirements are not met. We can still give our hard working contributors the appropriate exposure, but there are *far* more developers than docs maintainers and we need their help. --Pete -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
On Wed, Nov 28, 2012 at 15:01:21 -0700, There are several mechanisms for a developer to get their work into the release notes. The rel-notes BZ tag was wholly unused during this cycle, to the best of my knowledge. There were no bugs filed against the release-notes bugzilla product to request inclusion. When no emails were sent to the Docs mailing list, we put out a request on devel-announce for developers to get in touch; the only person that responded already had a well composed Feature page for us to work from. There was at least one bug where I suggested getting a release note in. But I didn't know of rel-notes tag. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rssh (need a sponsor and package from database)
Hello I have currently learned that the package rssh has been orphaned and I will like to keep this package alive. I will like to non-deprecated the fedora 17 rssh in the fedora packager database. I would like to work on the security issues. thank you Alex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
On , Tom Callaway wrote: On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore t:5px; width:100%embryo - Small Pawn based virtual machine an dje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping n - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project Thanks for the response Tom. I had searched the packages, however i realized i needed to go one more page in the package list to find those that you own. E17 currently needs all packages to be at the 1.7.2 release. The Enlightenment team plans on keeping them all at the same version number even if some packages have no changes. You probably already know this. I think i remember removing libeina when i installed my build of eina. If we can get libeina up to 1.7.2 then i will adjust the packages to look for libeina and not eina. I have all the packages up on my website http://www.edmann.com/Enlightenment/repo/Fedora/17/ Also i have the yum repo [Enlightenment] name=Enlightenment for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/X86_64/RPMS enabled=1 metadata_expire=7d gpgcheck=0 [Enlightenment - Sources] name=Enlightenment SRPMS for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/SRPMS enabled=1 metadata_expire=7d gpgcheck=0 Right now it's only for x86_64, i will build another vm and do i386 packages. Not sure if that will be needed, but people might come across it and want those. I will also do 18 beta as well. Do i need to make a bug request for each package or is that premature for me to do right now? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
On 11/28/2012 08:08 PM, Miloslav Trmač wrote: Hello, this proposal was recently linked in various places, so let's formally introduce it: https://fedoraproject.org/wiki/User:Mmaslano/Feature_process This an incremental change, not a major overhaul designed to solve all problems. The benefits expected from this proposal: * Making proposed features more visible to Fedora contributors, and making it easier for Fedora contributors to discuss the feature before FESCo votes on it. * Simplifying the process for self-contained features (e.g. individual package version upgrades) * Getting FESCo more involved in scheduling and testing of features with large impact on the rest of the distribution or schedule. * Making sure some frequently forgotten-about items, like rel-eng impact, are included in the feature proposal. For details, please see the proposal at the above-mentioned link. Marcela Mašláňová, Tomáš Mráz, Jaroslav Řezník, Miloslav Trmač Lacks clarification on what's considered an feature. Arguably it should be mandatory for feature owners to provide or work with the documentation and or marketing communities documenting and publishing what benefits changes their feature brings to users/community/the distribution in whole etc. it's just absurd having us ( QA ) adjusting release criteria while we are trying to follow it so feature that might affect the current release criteria and or critical components will need to be approved by QA before alpha so we can but not be limited to making the necessary changes to the release criteria in due time and make sure proper testing takes place and each approved feature arguably should have associated test day with it ( if relevant ). Will it still be optional to participate in the feature process? JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
On Wed, Nov 28, 2012 at 09:23:09PM +, Richard W.M. Jones wrote: * Simplifying the process for self-contained features (e.g. individual package version upgrades) I don't see why these are features at all. Surely it's better towards the end of each release cycle for someone to compare the versions of Major package upgrades certainly often represent features in the English-language and common usage sense from an end-user point of view. I think it's perfectly reasonable to leave that in the features process. It's not just the end of the cycle where it's interesting -- people like to look and see what's in progress. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rssh (need a sponsor and package from database)
On 28/11/2012 5:27 PM, Alexander Aristotle Davis wrote: Hello I have currently learned that the package rssh has been orphaned and I will like to keep this package alive. I will like to non-deprecated the fedora 17 rssh in the fedora packager database. I would like to work on the security issues. thank you Alex I would like to be the maintainer for the rssh for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting rssh on Fedora i will need to fix the security. Alex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
On Wed, Nov 28, 2012 at 09:08:59PM +0100, Miloslav Trmač wrote: this proposal was recently linked in various places, so let's formally introduce it: https://fedoraproject.org/wiki/User:Mmaslano/Feature_process As discussed earlier, I liked the three-tier approach better, but I'm in favor of any improvement, which I think this clearly is. I think we do need more clarity on system-wide/defaults changing features or critical path components. What's the threshold for defaults? (LVM, for a specific example.) What's the threshold for a change to a critical path component? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Feature process improvements
I would suggest that we create a clear SOP for fall back planning in case a feature, especially a crit path feature, is not ready for prime time. Obviously, if a feature is not %100 by feature freeze, then it needs to be dropped. I would even venture to suggest that we include in the SOP something along the lines of If feature is not 80% by point X (X being two weeks prior to freeze), then FESCo should at that point evaluate enacting the fall back. John. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rssh (need a sponsor and package from database)
Hi Alex! Do you have an srpm we can test with? Dan On Wed, Nov 28, 2012 at 4:18 PM, Alexander Aristotle Davis aadav...@learn.senecac.on.ca wrote: On 28/11/2012 5:27 PM, Alexander Aristotle Davis wrote: Hello I have currently learned that the package rssh has been orphaned and I will like to keep this package alive. I will like to non-deprecated the fedora 17 rssh in the fedora packager database. I would like to work on the security issues. thank you Alex I would like to be the maintainer for the rssh for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting rssh on Fedora i will need to fix the security. Alex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/develhttps://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Help Wanted] Which package provide the System Module for rawhide
On Wed, Nov 28, 2012 at 21:45:23 GMT, Jochen Schmitt wrote: Halli, I'm trying to build the kaya package for the rawnide branch of Fedora. Unfortunately, I have got the following error messages during the build process: make -C compiler make[1]: Entering directory `/builddir/build/BUILD/kaya-0.5.2/compiler' /usr/bin/happy -g -a -c ./Parser.y -iParser.out -oParser.hs unused terminals: 2 g++ -fPIC -fno-rtti -Wall -O2 -DNDEBUG -Wno-deprecated -I. -c -o repl_load.o repl_load.cc /usr/bin/ghc --make -fglasgow-exts ./Main.hs repl_load.o -pgml g++ -o kayac -i. -odir . on the commandline: Warning: -fglasgow-exts is deprecated: Use individual extensions instead Main.hs:31:8: Could not find module `System' It is a member of the hidden package `haskell98-2.0.0.1'. Use -v to see a list of the files searched for. The compiler found System, but is only using what it was told it was allowed to use. It appears as though kaya is using autotools instead of cabal. I don't know how to get it to accept haskell98 as a dependency. It may be nice, if anyone can tell me in which package I could find the missed System module. We use ghc-$cabal_name-devel in Fedora, so ghc-haskell98-devel is the BuildRequires (but given the error message it's installed). -- Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Help Wanted] Which package provide the System Module for rawhide
You can also try ' repoquery --whatprovides pkgconfig(haskell98-2.0.0.1) ' On Wed, Nov 28, 2012 at 7:13 PM, Ben Boeckel maths...@gmail.com wrote: On Wed, Nov 28, 2012 at 21:45:23 GMT, Jochen Schmitt wrote: Halli, I'm trying to build the kaya package for the rawnide branch of Fedora. Unfortunately, I have got the following error messages during the build process: make -C compiler make[1]: Entering directory `/builddir/build/BUILD/kaya-0.5.2/compiler' /usr/bin/happy -g -a -c ./Parser.y -iParser.out -oParser.hs unused terminals: 2 g++ -fPIC -fno-rtti -Wall -O2 -DNDEBUG -Wno-deprecated -I. -c -o repl_load.o repl_load.cc /usr/bin/ghc --make -fglasgow-exts ./Main.hs repl_load.o -pgml g++ -o kayac -i. -odir . on the commandline: Warning: -fglasgow-exts is deprecated: Use individual extensions instead Main.hs:31:8: Could not find module `System' It is a member of the hidden package `haskell98-2.0.0.1'. Use -v to see a list of the files searched for. The compiler found System, but is only using what it was told it was allowed to use. It appears as though kaya is using autotools instead of cabal. I don't know how to get it to accept haskell98 as a dependency. It may be nice, if anyone can tell me in which package I could find the missed System module. We use ghc-$cabal_name-devel in Fedora, so ghc-haskell98-devel is the BuildRequires (but given the error message it's installed). -- Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
Actually the baseurl provided in your paste does not work for me. here is the fixed entry: baseurl= http://www.edmann.com/Enlightenment/repo/Fedora/$releasever/x86_64/RPMS 2012/11/29 Edward Mann e@edmann.com ** On , Tom Callaway wrote: On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) evas - Canvas and scenegraph rendering library. In Fedora as evas (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore (I own it) embryo - Small Pawn based virtual machine and compiler. edje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping and glue layer library. eeze - Device abstraction library. elementary - Elementary, the widget set... emotion - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project Thanks for the response Tom. I had searched the packages, however i realized i needed to go one more page in the package list to find those that you own. E17 currently needs all packages to be at the 1.7.2 release. The Enlightenment team plans on keeping them all at the same version number even if some packages have no changes. You probably already know this. I think i remember removing libeina when i installed my build of eina. If we can get libeina up to 1.7.2 then i will adjust the packages to look for libeina and not eina. I have all the packages up on my website http://www.edmann.com/Enlightenment/repo/Fedora/17/ Also i have the yum repo [Enlightenment] name=Enlightenment for Fedora $releasever baseurl= http://edmann.com/Enlightenment/repo/Fedora/$releasever/X86_64/RPMS enabled=1 metadata_expire=7d gpgcheck=0 [Enlightenment - Sources] name=Enlightenment SRPMS for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/SRPMS enabled=1 metadata_expire=7d gpgcheck=0 Right now it's only for x86_64, i will build another vm and do i386 packages. Not sure if that will be needed, but people might come across it and want those. I will also do 18 beta as well. Do i need to make a bug request for each package or is that premature for me to do right now? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
Another comment: while you keep that repository up id really welcome if you could sign the packages in your private repo. 2012/11/29 Rudolf Kastl che...@gmail.com Actually the baseurl provided in your paste does not work for me. here is the fixed entry: baseurl= http://www.edmann.com/Enlightenment/repo/Fedora/$releasever/x86_64/RPMS 2012/11/29 Edward Mann e@edmann.com ** On , Tom Callaway wrote: On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) evas - Canvas and scenegraph rendering library. In Fedora as evas (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore (I own it) embryo - Small Pawn based virtual machine and compiler. edje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping and glue layer library. eeze - Device abstraction library. elementary - Elementary, the widget set... emotion - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project Thanks for the response Tom. I had searched the packages, however i realized i needed to go one more page in the package list to find those that you own. E17 currently needs all packages to be at the 1.7.2 release. The Enlightenment team plans on keeping them all at the same version number even if some packages have no changes. You probably already know this. I think i remember removing libeina when i installed my build of eina. If we can get libeina up to 1.7.2 then i will adjust the packages to look for libeina and not eina. I have all the packages up on my website http://www.edmann.com/Enlightenment/repo/Fedora/17/ Also i have the yum repo [Enlightenment] name=Enlightenment for Fedora $releasever baseurl= http://edmann.com/Enlightenment/repo/Fedora/$releasever/X86_64/RPMS enabled=1 metadata_expire=7d gpgcheck=0 [Enlightenment - Sources] name=Enlightenment SRPMS for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/SRPMS enabled=1 metadata_expire=7d gpgcheck=0 Right now it's only for x86_64, i will build another vm and do i386 packages. Not sure if that will be needed, but people might come across it and want those. I will also do 18 beta as well. Do i need to make a bug request for each package or is that premature for me to do right now? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Help Wanted] Which package provide the System Module for rawhide
On Wed, Nov 28, 2012 at 19:15:29 -0800, Dan Mashal wrote: You can also try ' repoquery --whatprovides pkgconfig(haskell98-2.0.0.1) ' I don't believe Haskell packages tend to install pkgconfig files (and haskell98 doesn't provide one). If you know the magic hash of the package, you can query for 'ghc-devel(haskell98-2.0.0.1-$magichash)'. The one on my (rawhide) machine has a magic hash of 6097c8615c4b5c52a204b7b899e54cb5. In any case, if ghc is giving the package it's in, it's usually a trivial change to get the Fedora package name. --Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
After yum install enlightenment running enlightenment_start makes it crash: enlightenment_start E - PID=22138, valgrind=0 /usr/bin/enlightenment: symbol lookup error: /usr/lib64/libedje.so.1: undefined symbol: EIO_MONITOR_FILE_CREATED 2012/11/29 Rudolf Kastl che...@gmail.com Another comment: while you keep that repository up id really welcome if you could sign the packages in your private repo. 2012/11/29 Rudolf Kastl che...@gmail.com Actually the baseurl provided in your paste does not work for me. here is the fixed entry: baseurl= http://www.edmann.com/Enlightenment/repo/Fedora/$releasever/x86_64/RPMS 2012/11/29 Edward Mann e@edmann.com ** On , Tom Callaway wrote: On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) evas - Canvas and scenegraph rendering library. In Fedora as evas (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore (I own it) embryo - Small Pawn based virtual machine and compiler. edje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping and glue layer library. eeze - Device abstraction library. elementary - Elementary, the widget set... emotion - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project Thanks for the response Tom. I had searched the packages, however i realized i needed to go one more page in the package list to find those that you own. E17 currently needs all packages to be at the 1.7.2 release. The Enlightenment team plans on keeping them all at the same version number even if some packages have no changes. You probably already know this. I think i remember removing libeina when i installed my build of eina. If we can get libeina up to 1.7.2 then i will adjust the packages to look for libeina and not eina. I have all the packages up on my website http://www.edmann.com/Enlightenment/repo/Fedora/17/ Also i have the yum repo [Enlightenment] name=Enlightenment for Fedora $releasever baseurl= http://edmann.com/Enlightenment/repo/Fedora/$releasever/X86_64/RPMS enabled=1 metadata_expire=7d gpgcheck=0 [Enlightenment - Sources] name=Enlightenment SRPMS for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/SRPMS enabled=1 metadata_expire=7d gpgcheck=0 Right now it's only for x86_64, i will build another vm and do i386 packages. Not sure if that will be needed, but people might come across it and want those. I will also do 18 beta as well. Do i need to make a bug request for each package or is that premature for me to do right now? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
the crash happens because of a collision with libeio which is in the fedora main repository. 2012/11/29 Rudolf Kastl che...@gmail.com After yum install enlightenment running enlightenment_start makes it crash: enlightenment_start E - PID=22138, valgrind=0 /usr/bin/enlightenment: symbol lookup error: /usr/lib64/libedje.so.1: undefined symbol: EIO_MONITOR_FILE_CREATED 2012/11/29 Rudolf Kastl che...@gmail.com Another comment: while you keep that repository up id really welcome if you could sign the packages in your private repo. 2012/11/29 Rudolf Kastl che...@gmail.com Actually the baseurl provided in your paste does not work for me. here is the fixed entry: baseurl= http://www.edmann.com/Enlightenment/repo/Fedora/$releasever/x86_64/RPMS 2012/11/29 Edward Mann e@edmann.com ** On , Tom Callaway wrote: On 11/27/2012 02:47 PM, Edward Mann wrote: I would like to be the maintainer for the Enlightenment e17 for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting e17 on Fedora i will need to build and install the following packages eina - Core data structure library. In Fedora as libeina (I own it) eet - Data encode/decode and storage library. In Fedora as eet (I own it) evas - Canvas and scenegraph rendering library. In Fedora as evas (I own it) ecore - Core mainloop, display abstraction and utility library. In Fedora as ecore (I own it) embryo - Small Pawn based virtual machine and compiler. edje - Abstract GUI layout and animation object library. efreet - Standards handling for freedesktop.org standards. e_dbus - Dbus wrapping and glue layer library. eeze - Device abstraction library. elementary - Elementary, the widget set... emotion - Emotion, video and audio codec API... ethumb - EThumb, thumbnail generation library... eio - Eio, async I/O library... I don't think any of these are in Fedora, so they'd be a great place to start. Let me know if you need any changes to the four packages I own, once you get in the packager group, I'd be happy to let you comaintain them. ~tom == Fedora Project Thanks for the response Tom. I had searched the packages, however i realized i needed to go one more page in the package list to find those that you own. E17 currently needs all packages to be at the 1.7.2 release. The Enlightenment team plans on keeping them all at the same version number even if some packages have no changes. You probably already know this. I think i remember removing libeina when i installed my build of eina. If we can get libeina up to 1.7.2 then i will adjust the packages to look for libeina and not eina. I have all the packages up on my website http://www.edmann.com/Enlightenment/repo/Fedora/17/ Also i have the yum repo [Enlightenment] name=Enlightenment for Fedora $releasever baseurl= http://edmann.com/Enlightenment/repo/Fedora/$releasever/X86_64/RPMS enabled=1 metadata_expire=7d gpgcheck=0 [Enlightenment - Sources] name=Enlightenment SRPMS for Fedora $releasever baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever/SRPMS enabled=1 metadata_expire=7d gpgcheck=0 Right now it's only for x86_64, i will build another vm and do i386 packages. Not sure if that will be needed, but people might come across it and want those. I will also do 18 beta as well. Do i need to make a bug request for each package or is that premature for me to do right now? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rssh (need a sponsor and package from database)
Alexander Aristotle Davis wrote: I would like to be the maintainer for the rssh for Fedora. I am sending this e-mail to seek guidance and also a sponsor. Getting rssh on Fedora i will need to fix the security. Hi Alex! I think you need a plan for how you will convince potential sponsors that you understand the packaging guidelines and can do a good job of maintaining a Fedora package. The usual ways of doing that are to make new packages of good quality and submit them for review, and to do informal reviews of others' packages. (You're not allowed to do formal reviews before you're sponsored, but you can always comment on review requests.) Those are just the usual ways though. Any way that works is good. One thing that I would want to see if I were a sponsor would be an RSSH package where all known security bugs are fixed, not as a new package but as a fixed version of the old package. If the current upstream maintainer doesn't want to continue maintaining RSSH, then a good way of showing that you're serious about keeping it alive would be to take over upstream maintenance. You might want to coordinate that with package maintainers in other distributions. Björn Persson -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 876974] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers [fedora-all]
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876974 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |CURRENTRELEASE Last Closed|2012-11-23 02:54:03 |2012-11-28 06:36:05 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877015] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 Bug 877015 depends on bug 876974, which changed state. Bug 876974 Summary: CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=876974 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |CURRENTRELEASE -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876974] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers [fedora-all]
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876974 --- Comment #13 from Fedora Update System upda...@fedoraproject.org --- perl-CGI-3.51-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877015] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 --- Comment #10 from Fedora Update System upda...@fedoraproject.org --- perl-CGI-3.51-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876221] perl-Wx does not provide perl(Wx::Dialog) and others.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876221 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-Wx-0.9914-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876974] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers [fedora-all]
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876974 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|CLOSED |ASSIGNED Resolution|CURRENTRELEASE |--- Keywords||Reopened --- Comment #14 from Petr Pisar ppi...@redhat.com --- Bug in bodhi. It closed this report despite F17 and F16 builds have not yet reached stable repository. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877015] CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 Bug 877015 depends on bug 876974, which changed state. Bug 876974 Summary: CVE-2012-5526 perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=876974 What|Removed |Added Status|CLOSED |ASSIGNED Resolution|CURRENTRELEASE |--- -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876221] perl-Wx does not provide perl(Wx::Dialog) and others.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876221 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Wx-0.9914-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Remove] Add missing buildtime deps
commit a8b61f77808a73caeb75df69295dcca285d6c285
Author: Petr Šabata con...@redhat.com
Date: Wed Nov 28 14:10:33 2012 +0100
Add missing buildtime deps
perl-File-Remove.spec | 24
1 files changed, 16 insertions(+), 8 deletions(-)
---
diff --git a/perl-File-Remove.spec b/perl-File-Remove.spec
index 846ff19..8a1ebf7 100644
--- a/perl-File-Remove.spec
+++ b/perl-File-Remove.spec
@@ -1,19 +1,21 @@
Name: perl-File-Remove
Version: 1.52
-Release: 3%{?dist}
+Release: 4%{?dist}
Summary: Convenience module for removing files and directories
License: GPL+ or Artistic
Group: Development/Libraries
URL: http://search.cpan.org/dist/File-Remove/
Source0:
http://search.cpan.org/CPAN/authors/id/A/AD/ADAMK/File-Remove-%{version}.tar.gz
-
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
-
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+BuildRequires: perl(constant)
+BuildRequires: perl(Cwd)
BuildRequires: perl(ExtUtils::MakeMaker)
-BuildRequires: perl(Test::More) = 0.42
-BuildRequires: perl(File::Spec) = 3.29
-BuildRequires: perl(File::Path)
BuildRequires: perl(File::Glob)
+BuildRequires: perl(File::Path)
+BuildRequires: perl(File::Spec) = 3.29
+BuildRequires: perl(File::Spec::Functions)
+BuildRequires: perl(inc::Module::Install::DSL)
+BuildRequires: perl(Test::More) = 0.42
BuildArch: noarch
@@ -22,9 +24,10 @@ BuildArch: noarch
%prep
%setup -q -n File-Remove-%{version}
+rm -rf inc
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
@@ -42,6 +45,11 @@ make test
%{_mandir}/man3/*
%changelog
+* Wed Nov 28 2012 Petr Šabata con...@redhat.com - 1.52-4
+- Add missing buildtime deps
+- Unbundle Module::Install
+- Drop command macros
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.52-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 859872] perl-5.16: perl -d:foo crashes if DB::DB is seen but not defined in Devel::foo
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=859872 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-5.16.2-234.fc18 Resolution|--- |CURRENTRELEASE Last Closed||2012-11-28 09:04:17 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Font-AFM] BuildRequire Carp and fix the License tag
commit 7e17968ce7dac8d5afd8d08160712a0e1012a039
Author: Petr Šabata con...@redhat.com
Date: Wed Nov 28 15:05:33 2012 +0100
BuildRequire Carp and fix the License tag
perl-Font-AFM.spec | 17 +++--
1 files changed, 11 insertions(+), 6 deletions(-)
---
diff --git a/perl-Font-AFM.spec b/perl-Font-AFM.spec
index d10f936..fdfe329 100644
--- a/perl-Font-AFM.spec
+++ b/perl-Font-AFM.spec
@@ -1,19 +1,20 @@
Name: perl-Font-AFM
Version:1.20
-Release: 11%{?dist}
+Release: 12%{?dist}
Summary:Perl interface to Adobe Font Metrics files
Group: Development/Libraries
-License: GPL+ or Artistic
+License: (GPL+ or Artistic) and Copyright only
URL: http://search.cpan.org/dist/Font-AFM/
Source0:
http://www.cpan.org/authors/id/G/GA/GAAS/Font-AFM-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version))
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
BuildArch: noarch
+BuildRequires: perl(Carp)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: %{_datadir}/a2ps/afm/phvr.afm
@@ -26,15 +27,14 @@ Interface to Adobe Font Metrics files
sed -i -e 's,Helvetica,phvr,g' t/afm.t
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+make pure_install DESTDIR=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} ';'
-find $RPM_BUILD_ROOT -type d -depth -exec rmdir {} 2/dev/null ';'
chmod -R u+w $RPM_BUILD_ROOT/*
@@ -52,6 +52,11 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/Font*
%changelog
+* Wed Nov 28 2012 Petr Šabata con...@redhat.com - 1.20-12
+- BuildRequire perl(Carp)
+- Drop command macros
+- Reflect metrics copyright in the License tag
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.20-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 745537] perl-Bio-Graphics-2.25-1.fc17.noarch requires non-existing perl(Bio::DB::BigWig)
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=745537 Emmanuel Seyman emman...@seyman.fr changed: What|Removed |Added CC||emman...@seyman.fr --- Comment #4 from Emmanuel Seyman emman...@seyman.fr --- (In reply to comment #2) Unfortunate, as I didn't update the perl-Bio-Graphics myself, this was done by spot in response to a update request. I'm afraid that's my fault. During FUDCon EMEA 2011, I asked spot if he could help me close some harmless bugs and I suspect #707919 was one of them. So much for harmless drive-by-updating. (In reply to comment #3) Hopefully I did it correctly using the new 4.9 rpm syntax. Will close bug when build finished and new rawhide compose complete and dep script doesn't produce an error. I believe the problem is indeed fixed. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Module-Signature-0.70.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Module-Signature: c13eabb8c2e6b12fd098710a81185ac6 Module-Signature-0.70.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Module-Signature] Update to 0.70
commit f0b0d9b8fb445c461192280b2719a70a15bd5ce8
Author: Paul Howarth p...@city-fan.org
Date: Wed Nov 28 20:55:39 2012 +
Update to 0.70
- New upstream release 0.70
- Don't check gpg version if gpg does not exist
perl-Module-Signature.spec |6 +-
sources|2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/perl-Module-Signature.spec b/perl-Module-Signature.spec
index 3580fd1..6d16cd4 100644
--- a/perl-Module-Signature.spec
+++ b/perl-Module-Signature.spec
@@ -1,5 +1,5 @@
Name: perl-Module-Signature
-Version:0.69
+Version:0.70
Release:1%{?dist}
Summary:CPAN signature management utilities and modules
Group: Development/Libraries
@@ -85,6 +85,10 @@ rm -rf %{buildroot}
%{_mandir}/man3/Module::Signature.3pm*
%changelog
+* Wed Nov 28 2012 Paul Howarth p...@city-fan.org - 0.70-1
+- Update to 0.70
+ - Don't check gpg version if gpg does not exist
+
* Fri Nov 2 2012 Paul Howarth p...@city-fan.org - 0.69-1
- Update to 0.69
- Support for gpg under these alternate names: gpg gpg2 gnupg gnupg2
diff --git a/sources b/sources
index eaccf7a..1eaa3d4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-57b252aa2788871718279353d170e1f7 Module-Signature-0.69.tar.gz
+c13eabb8c2e6b12fd098710a81185ac6 Module-Signature-0.70.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Module-Signature/f18] Update to 0.70
Summary of changes: f0b0d9b... Update to 0.70 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Module-Signature] Created tag perl-Module-Signature-0.70-1.fc18
The lightweight tag 'perl-Module-Signature-0.70-1.fc18' was created pointing to: f0b0d9b... Update to 0.70 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Module-Signature] Created tag perl-Module-Signature-0.70-1.fc19
The lightweight tag 'perl-Module-Signature-0.70-1.fc19' was created pointing to: f0b0d9b... Update to 0.70 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878005] Upgrade to new upstream version
Product: Fedora EPEL https://bugzilla.redhat.com/show_bug.cgi?id=878005 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- stompclt-0.6-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878005] Upgrade to new upstream version
Product: Fedora EPEL https://bugzilla.redhat.com/show_bug.cgi?id=878005 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2012-11-28 22:56:47 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877724] perl-DateTime-0.78 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=877724 --- Comment #12 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-0.78-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877724] perl-DateTime-0.78 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=877724 --- Comment #13 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-0.78-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878005] Upgrade to new upstream version
Product: Fedora EPEL https://bugzilla.redhat.com/show_bug.cgi?id=878005 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- stompclt-0.6-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878005] Upgrade to new upstream version
Product: Fedora EPEL https://bugzilla.redhat.com/show_bug.cgi?id=878005 --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- stompclt-0.6-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878829] FTBFS perl-prefork is missing build dependency
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=878829 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2012-11-29 01:39:27 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878829] FTBFS perl-prefork is missing build dependency
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=878829 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-prefork-1.04-10.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 878005] Upgrade to new upstream version
Product: Fedora EPEL https://bugzilla.redhat.com/show_bug.cgi?id=878005 --- Comment #10 from Fedora Update System upda...@fedoraproject.org --- stompclt-0.6-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[389-devel] please review: Ticket 395 - RFE - 389-ds shouldn't advertise in the rootDSE that we can handle a sasl mech if we really can't
https://fedorahosted.org/389/ticket/395 https://fedorahosted.org/389/attachment/ticket/395/0001-Ticket-395-RFE-389-ds-shouldn-t-advertise-in-the-roo.patch -- Mark Reynolds Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Announcing the release of Fedora 18 Beta!!!
The Fedora 18 Spherical Cow Beta release is rolling! This release offers a preview of some of the best free and open source technology currently under development. We are delighted to announce the availability of the beta release of Fedora 18. Want to get a taste of the future? Download it now: http://fedoraproject.org/get-prerelease *** What is the Beta Release? *** The Beta release is the last important milestone of Fedora 18. Only critical bug fixes will be pushed as updates leading to the general release of Fedora 18 in the beginning of the next year. We invite you to join us in making Fedora 18 a solid release by downloading, testing, and providing your valuable feedback. Of course, this is a beta release, meaning that some problems may still be lurking. A list of the problems we already know about is found at the Common F18 bugs page, seen here: http://fedoraproject.org/wiki/Common_F18_bugs There is a new upgrade system for Fedora 18 making its first appearance in Fedora 18 Beta. Upgrading via the system installer or the preupgrade tool is no longer possible. To upgrade to Fedora 18 from Fedora 17, you should use the new Fedup tool. Instructions and information on the new tool are here: http://fedoraproject.org/wiki/FedUp. The tool is still under active development, please take a look at the FedUp FAQ (in the wiki page) in case of any issues with the upgrade process, and back up your system before trying the upgrade. *** Features *** This release of Fedora includes a variety of features both over and under the hood that show off the power and flexibility of the advancing state of free software. Here are just a few of the new features: = For users everywhere = * Fedora 18 offers a brand-new version of the Gnome desktop, version 3.6, straight from the upstream development process. Updates have also been made to the KDE Plasma Workspaces, XFCE and Sugar]desktop environments; additionally, the MATE desktop is available for the first time in Fedora. * Fedora's new installer user interface enhances the anaconda installer with improvements in ease of use and installation. = For developers = * This release includes several language updates, including the move to Perl 5.16, updating the Python 3 stack from 3.2 to 3.3, Rails 3.2 and updated D and Haskell programming environments. = For system administrators = * Fedora 18 includes the final release of Samba 4, and can be used on an Active Directory domain member out of the box. An integrated, new native management software allows you to access data and server information easily. * OpenStack in Fedora 18 has been updated to Folsom, the most recent release by the OpenStack community. This Infrastructure-as-a-Service (IaaS) platform enables the creation and management of cloud infrastructure. * Eucalyptus 3.1, another IaaS platform, is available in Fedora for the first time, and includes the major components of Eucalyptus. * System Storage Management CLI tools simplify the user interface by providing unified abstraction and interface for multiple storage technologies, including lvm, btrfs and md raid. For more Features, please take a look on the complete list: http://fedoraproject.org/wiki/Releases/18/FeatureList *** Contributing *** Great releases like Fedora 18 don't get made in a vacuum. We can't do it without you! Bug reports are especially helpful as we move from the theory to the applied physics. If you encounter any issues, please report them! Fedora is a fantastic, friendly community, and we have many ways in which you can contribute, including Documentation, Marketing, Design, QA, Development, and more. To learn how to help us, visit: http://join.fedoraproject.org/ Thank you, and we hope to see you in the Fedora Project! --- You may notice this announcement is a day late! We'd like to apologize to the community for the delayed announcement and any consequences resulting from the delay. ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
