Re: Building packages for EPEL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dennis Gilmore wrote: EPEL is now using koji to build instead of plague. please make sure that you update th common directory in your checkout to pick up the needed changes to submit builds. I was able to do builds for EL-4/EL-5 using koji. thanks a lot! Bodhi support will come early next week to issue updates. Please let us know as and when make update will be available. Until then, what is the alternative? http://admin.fedoraproject.org/updates ? Thanks a lot, - -Greg the buildroots are only populated by packages from stable if you need to build against something in testing or that you have just build please email your request to epel-rel...@lists.fedoraproject.org thanks Dennis ___ Fedora-devel-announce mailing list fedora-devel-annou...@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce - -- +-+ Please also check the log file at /dev/null for additional information. (from /var/log/Xorg.setup.log) | Greg Hosler ghos...@redhat.com| +-+ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkpN0JcACgkQ404fl/0CV/T1LwCfZhc7U9ZvPeI8yafQX6SI8/gT lFYAoLJXluDxeH4qMWs6n0nlHLS2xJoO =w4dv -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dracut now has a wiki page in the Fedora wiki...
On Thu, 2009-07-02 at 23:22 +, Jóhann B. Guðmundsson wrote: The Dracut wiki page has now been moved from my drafts to it's permanent location. https://fedoraproject.org/wiki/Dracut Debugging can be found here https://fedoraproject.org/wiki/Dracut/Debugging Note i'm not sure if the http://fedoraproject.org/wiki/Dracut#Getting_the_Source containst correct git commands hence I've label them #FIXME the maintainer(s) can confirm or fix the entry's Thanks for this! tar xzf dracut-$version.tar.bz2 This won't work. z means 'this is a gzip formatted archive'. The letter for bzip2 is j, so you could do: tar xjf dracut-$version.tar.bz2 but it's actually a lot less trouble to just do: tar xf dracut-$version.tar.bz2 which auto-detects the archive type. It's much easier to just let it be handled by autodetection, and only bother specifying the archive type manually if the autodetection trips up. It would be nice if someone who actually who's primary language is English reviews and fixes potential ken lee entry's i've made. Haha, 'ken lee entries' needs to go into common usage :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Building packages for EPEL
On Fri, Jul 3, 2009 at 11:34 AM, Gregory Hoslerghos...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dennis Gilmore wrote: EPEL is now using koji to build instead of plague. please make sure that you update th common directory in your checkout to pick up the needed changes to submit builds. I was able to do builds for EL-4/EL-5 using koji. thanks a lot! Bodhi support will come early next week to issue updates. Please let us know as and when make update will be available. Until then, what is the alternative? http://admin.fedoraproject.org/updates ? make update goes to bodhi as well as http://admin.fedoraproject.org/updates; which is bodhi UI. epel-releng will be taking care of the updates for now. -- Xavier.t Lamien -- http://fedoraproject.org/wiki/XavierLamien GPG-Key ID: F3903DEB Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dracut now has a wiki page in the Fedora wiki...
On Thu, 2009-07-02 at 23:22 +, Jóhann B. Guðmundsson wrote: It would be nice if someone who actually who's primary language is English reviews and fixes potential ken lee entry's i've made. I did a copyedit on the page, correcting a few errors, using lists and templates more consistently, moving most of the 'introduction' into a named section so it doesn't eat up the entire top of the page, using links to User pages for the author list and just generally cleaning up. Hope you find it an improvement. Thanks for working on this! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
readline update?
I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? The package list is: GMT-4.4.0-2.fc11 Macaulay2-1.2-4.fc12 afpfs-ng-0.8.1-2.fc11 bti-015-1.fc11 calc-2.12.2.1-13.fc11 callweaver-1.2.0.1-3.fc11 cgdb-0.6.4-4.fc11 chrony-1.23-5.20081106gitbe42b4.fc12 clisp-2.47-3.fc11 coda-6.9.4-2.fc11 devtodo-0.1.20-3.fc12 fityk-0.8.1-14.fc10 gnu-smalltalk-3.1-5.fc12 gnubg-0.9.0.1-7.fc11 gnuplot-4.2.5-4.fc12 grass-6.3.0-12.fc11 kdeedu-4.2.95-1.fc12 ktechlab-0.3.70-1.20090304svn.fc11 lvm2-2.02.48-1.fc12 maxima-5.18.1-3.fc12 ocfs2-tools-1.3.9-10.20080221git.fc11 socat-1.7.0.0-2.fc11 -- Miroslav Lichvar -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On 07/03/2009 03:57 PM, Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? Have you talked to upstream and checked on what they suggest that we do about this? Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On Fri, Jul 03, 2009 at 04:00:02PM +0530, Rahul Sundaram wrote: On 07/03/2009 03:57 PM, Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? Have you talked to upstream and checked on what they suggest that we do about this? No. Some time ago they asked if there were any GPLv2 projects, I gave them a list, but they changed the license anyway. -- Miroslav Lichvar -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dracut now has a wiki page in the Fedora wiki...
On 07/03/2009 10:18 AM, Adam Williamson wrote: On Thu, 2009-07-02 at 23:22 +, Jóhann B. Guðmundsson wrote: It would be nice if someone who actually who's primary language is English reviews and fixes potential ken lee entry's i've made. I did a copyedit on the page, correcting a few errors, using lists and templates more consistently, moving most of the 'introduction' into a named section so it doesn't eat up the entire top of the page, using links to User pages for the author list and just generally cleaning up. Hope you find it an improvement. Thanks for working on this! I manage to catch Harald on irc yesterday he gladly filled me in what was needed on the report against this component so with swift action I created the page which leaves us with one less component to worry about now we only have ca 6999 to go... JBG -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: rawhide report: 20090702 changes
On Thu, 02 Jul 2009 19:52:35 +0530, Rahul wrote: On 07/02/2009 06:58 PM, Adam Miller wrote: +1 on the Books idea Does this look ok? --- comps-f12.xml.in.orig 2009-07-02 15:39:02.0 +0530 +++ comps-f12.xml.in 2009-07-02 19:49:32.108616562 +0530 @@ -520,6 +520,17 @@ /packagelist /group group +idbooks/id +_nameTechnical Books/_name +_description/ +defaultfalse/default +uservisibletrue/uservisible +packagelist + packagereq type=defaultdiveintopython/packagereq + packagereq type=defaultldd-pdf/packagereq +/packagelist + /group + group idbuildsys-build/id _nameBuildsystem building group/_name _description/ Rahul No, it doesn't. First of all, in my opinion it doesn't make sense to separate books from other forms of documentation. Secondly, samba-doc is missing in above package list, and there are probably more books included in other packages. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20090703 changes
Compose started at Fri Jul 3 06:15:05 UTC 2009 New package perl-CGI-Application-Dispatch Dispatch requests to CGI::Application based objects New package perl-CGI-Application-Plugin-ConfigAuto Easy config file management for CGI::Application New package php-pear-HTML_Javascript Class for creating simple JS scripts New package pypar Parallel programming with Python Removed package hunspell-ee Updated Packages: PyQt4-4.5.1-2.fc12 -- * Thu Jul 02 2009 Rex Dieter rdie...@fedoraproject.org - 4.5.1-2 - fix build with qt-4.5.2 - PyQt4-devel multilib conflict (#509415) alsa-plugins-1.0.20-2.fc12 -- * Wed Jun 24 2009 Eric Moret eric.mo...@gmail.com - 1.0.20-2 - Added speex subpackage - Removed ascii-art from jack's plugin description amqp-1.0.790661-1.fc12 -- * Thu Jul 02 2009 Nuno Santos nsan...@redhat.com - 0:1.0.790661-1 - Rebased to svn rev 790661 anaconda-12.0-1.fc12 * Thu Jul 02 2009 Chris Lumens clum...@redhat.com - 12.0-1 - network --bootproto no longer implies DHCP. (clumens) - Don't unconditionally skip the network config screen in kickstart. (clumens) - Allow creating new groups through kickstart. (clumens) - Set focus on hostname entry in network UI screen (#494135) (rvykydal) - Fix upgrade selected in UI after storage reset (#503302) (rvykydal) - Add support for specifying upgrade partition in ks (#471232) (rvykydal) - Add missing liveinst/* files. (dcantrell) - Update code that checks for devices that contain install media. (dlehman) - Rework tracking of devices containing installation media. (#497087) (dlehman) - Add function storage.udev.udev_resolve_devspec. (dlehman) - Prevent false positives in devtree's device lookup methods. (dlehman) - Skip exceptionDisks if exn originated in devtree.populate. (#497240) (dlehman) - Stop using rhpl.arch in writeRpmPlatform() (katzj) - Move simpleconfig (back) into anaconda from rhpl (katzj) - Use iutil arch specifiers rather than rhpl (katzj) - Remove unused rhpl imports (katzj) - Switch to using iutil.isS390 instead of rhpl.getArch (katzj) - Stop using rhpl.translate (katzj) - Default to /boot on ext4 (katzj) - Allow /boot on ext4 now that we have a grub that allows it (katzj) - Make sure the library directory is always set (notting) - Write out MAILADDR root into mdadm.conf (#508321) (rvykydal) - Do not install grub more times than needed. (rvykydal) - Ensure we set the SELinux context correctly on symlinks (#505054) (katzj) - udev dropped vol_id (#506360) (katzj) - Handle installing multilib into the installer intramfs correctly. (notting) - Set LIBDIR appropriately on PPC64. (notting) - Fix grub upgrade (#505966) (rvykydal) - Include yum.log in anacdump.txt too. (rvykydal) - Access format options property instead of mountopts attr. (#506219) (dlehman) - Be more careful about identifying NFS fstab entries. (dlehman) - Don't add leading directory for files twice. (#503830) (dlehman) - booty changes for iswmd (Jacek.Danecki) - Support for MD containers. (Jacek.Danecki) - New iswmd parameter for kernel cmdline (Jacek.Danecki) - New udev rule for using mdadm for isw_raid_member (Jacek.Danecki) - Use isohybrid to make boot.iso a hybrid image (katzj) - Log yum messages. (rvykydal) - Tell booty to rescan for bootable drivers when an extra disks get added (hdegoede) - Do not encourage VNC when doing kickstart text installs (#506534) (dcantrell) - Rename bootstrap to autogen.sh (dcantrell) - Include the contents of /proc/cmdline in exception reports (katzj) - Include libwrap library for sshd and telnet in s390 installs (jgranado) - Enforcing matching rootfs type on LVs as well as for partitions (#504743) (katzj) - Remove problem packages before attempting a re-download (#501887). (clumens) - Be more explicit about what's lacking on EFI systems (#501341). (clumens) - If not enough memory is installed, enforce swap partition creation (#498742). (clumens) - Convert to using automake/autoconf. (dcantrell) - Convert po/ subdirectory to GNU gettext template system. (dcantrell) - Restructure liveinst/ for the new build system. (dcantrell) - Add m4/ subdirectory with autoconf macros. (dcantrell) - Removed py-compile script. (dcantrell) - Rename anaconda.spec to anaconda.spec.in (dcantrell) - Ignore autoconf and automake files in the tree. (dcantrell) - Removed toplevel Makefile and Makefile.inc (dcantrell) - Show MAC address of network device in combo box (#504216) (dcantrell) - Remove loader/tr/.cvsignore (dcantrell) - Increase max NIC identification duration to 5 minutes (#473747). (dcantrell) - Use /sbin/ipcalc for IP address validation (#460579) (dcantrell) - Fix an obvious traceback when doing part --ondisk= (#504687). (clumens) - Catch errors from bootloader installation (#502210). (clumens) - Remove umask temporarily so device permissions are correct (#383531, wmealing). - Remove the name check on driver disk packages (#472951). (clumens) -
Re: readline update?
Miroslav Lichvar wrote: kdeedu-4.2.95-1.fc12 kdeedu only uses readline in KAlgebra which is GPLv2+ (and only in the command-line version (calgebra) at that), so no problems there. (I also verified that calgebra doesn't use any GPL v2 only libraries.) Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On 03/07/09 11:27, Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? The package list is: GMT-4.4.0-2.fc11 Macaulay2-1.2-4.fc12 afpfs-ng-0.8.1-2.fc11 bti-015-1.fc11 calc-2.12.2.1-13.fc11 callweaver-1.2.0.1-3.fc11 cgdb-0.6.4-4.fc11 chrony-1.23-5.20081106gitbe42b4.fc12 clisp-2.47-3.fc11 coda-6.9.4-2.fc11 devtodo-0.1.20-3.fc12 fityk-0.8.1-14.fc10 gnu-smalltalk-3.1-5.fc12 gnubg-0.9.0.1-7.fc11 gnuplot-4.2.5-4.fc12 grass-6.3.0-12.fc11 kdeedu-4.2.95-1.fc12 ktechlab-0.3.70-1.20090304svn.fc11 lvm2-2.02.48-1.fc12 maxima-5.18.1-3.fc12 ocfs2-tools-1.3.9-10.20080221git.fc11 socat-1.7.0.0-2.fc11 You've missed perl-Term-ReadLine-Gnu (and I wonder how many other packages?) but that one's OK as it's GPL+. Paul. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On 07/03/2009 03:27 AM, Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? Can we parallel install readline5 and readline6? -Toshio signature.asc Description: OpenPGP digital signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Mass-Package Orphanage
Hi All, I'm orphaning a bunch of packages for various reasons, mainly though -ENOSPARETIME to update. Although there are some mono packages there and I definately don't have enough time to make them work properly. Mono Packages: f-spot -- Photo management application ndesk-dbus -- Managed C# implementation of DBus ndesk-dbus-glib -- Provides glib mainloop integration for ndesk-dbus PHP Based Packages: php-pecl-json -- PECL library to implement JSON in PHP Horde: horde -- The common Horde Framework for all Horde applications imp -- The Internet Messaging Program: webmail access to IMAP/POP3 accounts ingo -- The Horde web-based Email Filter Rules Manager jeta -- Horde Java SSH module kronolith -- The Horde calendar application turba -- The Horde contact management application Mediawiki Related: mediawiki-Cite -- An extension to provide Citation tools for Mediawiki mediawiki-SpecialInterwiki -- An extension to provide an interwiki management system I'm going to be marking them as Orphaned over the next day (hopefully now, but just in case I don't get them all right away). Thanks, Nigel -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
Toshio Kuratomi a.bad...@gmail.com writes: On 07/03/2009 03:27 AM, Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? Can we parallel install readline5 and readline6? Maybe somebody should work on fixing whatever editline deficiencies are seen as showstoppers. regards, tom lane -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
On Fri, Jul 3, 2009 at 10:02 AM, Nigel Jonesd...@nigelj.com wrote: PHP Based Packages: php-pecl-json -- PECL library to implement JSON in PHP Got this one since it's a dependency for the MW stuff below. ] Mediawiki Related: mediawiki-Cite -- An extension to provide Citation tools for Mediawiki mediawiki-SpecialInterwiki -- An extension to provide an interwiki management system And these, we use them in Fedora Infrastructure. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
On 07/03/2009 09:23 AM, Jason L Tibbitts III wrote: NJ == Nigel Jonesd...@nigelj.com writes: NJ Horde: All of these packages (horde, imp, ingo, jeta, kronolith, turba) are PHP-based webapps, which should strike fear into most maintainers. I happen to be co-maintainer so I guess I've been promoted, although honestly I haven't had time to put much effort into these packages either. So, I'm pretty sure I can't be the only person in Fedora who cares about these packages. They need at least two maintainers, preferably three. Please feel free to pile on. I've recently decided to try to help out by being a package maintainer... I haven't submitted a package, I don't have any new packages I need. I'm wondering if it is possible to be a co-maintainer with someone willing? I've got lots of experience creating packages for our own server farm and workstations, but none with fedora approved packaging... What's the policy here? I wouldn't mind helping out with the horde stack, but am guessing I would need some sort of sponsor, double check commits before they happen type thing... ? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
NDN == Nathanael D Noblet nathan...@gnat.ca writes: NDN I'm wondering if it is possible to be a co-maintainer with NDN someone willing? In general, all you need is a sponsor. The usual route to that is via the submission of new packages, but it's not the only way. I happen to be a sponsor, so that's not an issue. What is an issue is that fact that the horde suite is somewhat delicate and security sensitive, and not really the best set of packages for a first-time packager. This is somewhat offset by the fact that the packages already exist and just need maintenance. I think that if you're interested, you should start by requesting watchcommits and watchbugzilla on at least the Fedora branches of those packages. (I have no desire to maintain the EPEL5 branch, so someone else needs to step in to take care of that one.) The URLs are: https://admin.fedoraproject.org/pkgdb/packages/name/horde https://admin.fedoraproject.org/pkgdb/packages/name/imp https://admin.fedoraproject.org/pkgdb/packages/name/ingo https://admin.fedoraproject.org/pkgdb/packages/name/jeta https://admin.fedoraproject.org/pkgdb/packages/name/kronolith https://admin.fedoraproject.org/pkgdb/packages/name/turba Later we can progress to sponsorship and commit access. I still hope we can find at least one other person to assist in maintaining these packages. Otherwise I fear I will just end up orphaning them again. - J -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
On 07/03/2009 10:52 AM, Jason L Tibbitts III wrote: NDN == Nathanael D Nobletnathan...@gnat.ca writes: NDN I'm wondering if it is possible to be a co-maintainer with NDN someone willing? In general, all you need is a sponsor. The usual route to that is via the submission of new packages, but it's not the only way. I happen to be a sponsor, so that's not an issue. What is an issue is that fact that the horde suite is somewhat delicate and security sensitive, and not really the best set of packages for a first-time packager. This is somewhat offset by the fact that the packages already exist and just need maintenance. Yeah, I figured as much. There are a few other packages I wouldn't mind helping out with all in all but without submitting a package for review it seems I'm coming at this a bit sideways... I think that if you're interested, you should start by requesting watchcommits and watchbugzilla on at least the Fedora branches of those packages. (I have no desire to maintain the EPEL5 branch, so someone else needs to step in to take care of that one.) The URLs are: Ok, well I could definitely use the EPEL5 packages as I up to now have been installing them on CentOS 5 servers manually. https://admin.fedoraproject.org/pkgdb/packages/name/horde https://admin.fedoraproject.org/pkgdb/packages/name/imp https://admin.fedoraproject.org/pkgdb/packages/name/ingo https://admin.fedoraproject.org/pkgdb/packages/name/jeta https://admin.fedoraproject.org/pkgdb/packages/name/kronolith https://admin.fedoraproject.org/pkgdb/packages/name/turba Later we can progress to sponsorship and commit access. I still hope we can find at least one other person to assist in maintaining these packages. Otherwise I fear I will just end up orphaning them again. Sounds good.. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
On Fri, Jul 3, 2009 at 5:56 PM, Nathanael D. Nobletnathan...@gnat.ca wrote: On 07/03/2009 10:52 AM, Jason L Tibbitts III wrote: NDN == Nathanael D Nobletnathan...@gnat.ca writes: NDN I'm wondering if it is possible to be a co-maintainer with NDN someone willing? In general, all you need is a sponsor. The usual route to that is via the submission of new packages, but it's not the only way. I happen to be a sponsor, so that's not an issue. What is an issue is that fact that the horde suite is somewhat delicate and security sensitive, and not really the best set of packages for a first-time packager. This is somewhat offset by the fact that the packages already exist and just need maintenance. Yeah, I figured as much. There are a few other packages I wouldn't mind helping out with all in all but without submitting a package for review it seems I'm coming at this a bit sideways... I think that if you're interested, you should start by requesting watchcommits and watchbugzilla on at least the Fedora branches of those packages. (I have no desire to maintain the EPEL5 branch, so someone else needs to step in to take care of that one.) The URLs are: Ok, well I could definitely use the EPEL5 packages as I up to now have been installing them on CentOS 5 servers manually. Then help Jason maintain the EPEL branches by sending him spec file patches, re-basing Fedora carried patches to new versions, etc. Submitting patches is great alternative way to prove yourself for getting sponsored. -- Mat Booth www.matbooth.co.uk -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 03/07/2009 18:52, Jason L Tibbitts III a écrit : NDN == Nathanael D Noblet nathan...@gnat.ca writes: NDN I'm wondering if it is possible to be a co-maintainer with NDN someone willing? In general, all you need is a sponsor. The usual route to that is via the submission of new packages, but it's not the only way. I happen to be a sponsor, so that's not an issue. Interesting. I thought people were obliged to submit _new_ packages to request sponsorship, and to be honest, I have always found unfortunate that people like Nathanael would'd want to help co-maintain an existing package would be left out of the door just because they wouldn't be interested in submitting a new package. Out of curiosity, could you point me to a reference documentation that explains the process to sponsor a co-maintainer who is not a fedora packager already ? The only link I was aware of was this one: http://fedoraproject.org/wiki/PackageMaintainers/Join#Make_a_Package, where it's stated: You should make sure that it is a new package. Thanks. - -- Dodji Seketeli Red Hat, Inc. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEUEARECAAYFAkpORjsACgkQPejI7lrem2G7NQCfe60L/w1FfUMLDJEYfP9n+Xrb 34UAmNPQRaU55lhGV5fKOqJj4D/GtmI= =7HEZ -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 03/07/2009 18:52, Jason L Tibbitts III a écrit : NDN == Nathanael D Noblet nathan...@gnat.ca writes: NDN I'm wondering if it is possible to be a co-maintainer with NDN someone willing? In general, all you need is a sponsor. The usual route to that is via the submission of new packages, but it's not the only way. I happen to be a sponsor, so that's not an issue. Interesting. I thought people were obliged to submit _new_ packages to request sponsorship, and to be honest, I have always found unfortunate that people like Nathanael would'd want to help co-maintain an existing package would be left out of the door just because they wouldn't be interested in submitting a new package. Out of curiosity, could you point me to a reference documentation that explains the process to sponsor a co-maintainer who is not a fedora packager already ? The only link I was aware of was this one: http://fedoraproject.org/wiki/PackageMaintainers/Join#Make_a_Package, where it's stated: You should make sure that it is a new package. Thanks. - -- Dodji Seketeli Red Hat, Inc. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEUEARECAAYFAkpORjsACgkQPejI7lrem2G7NQCfe60L/w1FfUMLDJEYfP9n+Xrb 34UAmNPQRaU55lhGV5fKOqJj4D/GtmI= =7HEZ -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
DS == Dodji Seketeli do...@redhat.com writes: DS Interesting. I thought people were obliged to submit _new_ DS packages to request sponsorship, Any user can request sponsorship without doing anything. That doesn't mean they're going to get it, of course. It is the sponsor's responsibility to monitor and mentor the person they've sponsored, and they make the decision about who they wish to sponsor. (And here I'm talking about the packager group only, not any other group which also has sponsors and which may have their own rules.) It is true that one significant path to this is the submission of new packages. I don't think you'll find it anywhere documented that the only possible path is the submission of new packages. DS Out of curiosity, could you point me to a reference documentation DS that explains the process to sponsor a co-maintainer who is not a DS fedora packager already ? If you're a sponsor, you just go to the account system and sponsor them (assuming they've already applied, of course). The procedure isn't any different than any other situation where someone is sponsored into a group. DS The only link I was aware of was this one: DS http://fedoraproject.org/wiki/PackageMaintainers/Join#Make_a_Package, DS where it's stated: You should make sure that it is a new DS package. That's the document on submitting new packages, yes. As such, you can expect that it talks about submitting new packages. - J -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? The package list is: latest xfsprogs uses libreadline too (it can also be configured to use editline) -Eric GMT-4.4.0-2.fc11 Macaulay2-1.2-4.fc12 afpfs-ng-0.8.1-2.fc11 bti-015-1.fc11 calc-2.12.2.1-13.fc11 callweaver-1.2.0.1-3.fc11 cgdb-0.6.4-4.fc11 chrony-1.23-5.20081106gitbe42b4.fc12 clisp-2.47-3.fc11 coda-6.9.4-2.fc11 devtodo-0.1.20-3.fc12 fityk-0.8.1-14.fc10 gnu-smalltalk-3.1-5.fc12 gnubg-0.9.0.1-7.fc11 gnuplot-4.2.5-4.fc12 grass-6.3.0-12.fc11 kdeedu-4.2.95-1.fc12 ktechlab-0.3.70-1.20090304svn.fc11 lvm2-2.02.48-1.fc12 maxima-5.18.1-3.fc12 ocfs2-tools-1.3.9-10.20080221git.fc11 socat-1.7.0.0-2.fc11 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Mass-Package Orphanage
On Sat, 2009-07-04 at 02:02 +1200, Nigel Jones wrote: ndesk-dbus -- Managed C# implementation of DBus ndesk-dbus-glib -- Provides glib mainloop integration for ndesk-dbus I'd be happy to take these two, since Banshee and Tomboy (among others) require them. :) -- Peter Gordon (codergeek42) pe...@thecodergeek.com Who am I? :: http://thecodergeek.com/about-me signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. I thought, we banned all non-utf-8 aware packages? Ralf -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On Fri, Jul 3, 2009 at 9:29 PM, Ralf Corsepiusrc040...@freenet.de wrote: Miroslav Lichvar wrote: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. I thought, we banned all non-utf-8 aware packages? err .. what? no we still have a lot of them... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dracut now has a wiki page in the Fedora wiki...
On Fri, Jul 03, 2009 at 10:43:34 +0100, Adam Williamson awill...@redhat.com wrote: but it's actually a lot less trouble to just do: tar xf dracut-$version.tar.bz2 which auto-detects the archive type. It's much easier to just let it be handled by autodetection, and only bother specifying the archive type manually if the autodetection trips up. How long has that feature been there? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
Miroslav Lichvar (mlich...@redhat.com) said: I'd like to update readline to the latest version 6.0. The problem is that the license was changed to GPLv3+ and we have some GPLv2 packages using readline. A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. Are we stuck with readline 5.2? Suggestions? I suppose the first question is whether or not 5.2 and 6.0 are ABI-compatible; if they're not, a parallel intsall would be simplest. Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
Jussi Lehtola wrote: Quoting Ralf Corsepius rc040...@freenet.de: drago01 wrote: On Fri, Jul 3, 2009 at 9:29 PM, Ralf Corsepiusrc040...@freenet.de wrote: Miroslav Lichvar wrote: A possible replacement is the editline library which provides a compatible interface and is licensed under BSD, unfortunately it doesn't handle UTF-8. I thought, we banned all non-utf-8 aware packages? err .. what? Yes, utf-8 awareness had been a review criterion since the earliest Fedora days. No. What you are thinking of is spec files and rpm filenames (and documentation that is in non-ASCII character set). No, I am talking about applications and libraries, not about documentation. no we still have a lot of them... Packages to get rid off ... did somebody say Fedora is leading edge? Just because a program doesn't support UTF8 doesn't make it broken. Wrong, it is broken. I can state a lot of programs that aren't UTF8 compatible but still offer a lot of functionality and are important for daily work. Most programs automatically are utf8 compatible on Linux and don't need further treatment. Ralf -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dracut now has a wiki page in the Fedora wiki...
On Fri, 2009-07-03 at 15:00 -0500, Bruno Wolff III wrote: On Fri, Jul 03, 2009 at 10:43:34 +0100, Adam Williamson awill...@redhat.com wrote: but it's actually a lot less trouble to just do: tar xf dracut-$version.tar.bz2 which auto-detects the archive type. It's much easier to just let it be handled by autodetection, and only bother specifying the archive type manually if the autodetection trips up. How long has that feature been there? I'm as amused as you are that I didn't know about that either (my guess is it's been there a while and we're just all stuck in our ways). At least we're not stuck in the 1970s and willing to move with the times - a lot of people still like to use pipes of the individual utilities ;) Jon. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On Fri, 2009-07-03 at 12:27 +0200, Miroslav Lichvar wrote: bti-015-1.fc11 lvm2-2.02.48-1.fc12 I mailed Greg and Alasdair about these just so they know. Jon. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rpms/perl-IO-Socket-SSL/devel .cvsignore, 1.17, 1.18 perl-IO-Socket-SSL.spec, 1.20, 1.21 sources, 1.17, 1.18
Author: pghmcfc
Update of /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv31097
Modified Files:
.cvsignore perl-IO-Socket-SSL.spec sources
Log Message:
Update to 1.25 (fix t/nonblock.t for OS X 10.5 - CPAN RT#47240)
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/.cvsignore,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -p -r1.17 -r1.18
--- .cvsignore 3 Apr 2009 09:20:34 - 1.17
+++ .cvsignore 3 Jul 2009 08:33:25 - 1.18
@@ -1 +1 @@
-IO-Socket-SSL-1.24.tar.gz
+IO-Socket-SSL-1.25.tar.gz
Index: perl-IO-Socket-SSL.spec
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/perl-IO-Socket-SSL.spec,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -p -r1.20 -r1.21
--- perl-IO-Socket-SSL.spec 3 Apr 2009 09:20:34 - 1.20
+++ perl-IO-Socket-SSL.spec 3 Jul 2009 08:33:25 - 1.21
@@ -4,7 +4,7 @@
#
Name: perl-IO-Socket-SSL
-Version: 1.24
+Version: 1.25
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -57,9 +57,12 @@ done
%defattr(-,root,root,-)
%doc BUGS Changes README docs/ certs/ example/ util/
%{perl_vendorlib}/IO/
-%{_mandir}/man3/*.3*
+%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Fri Jul 3 2009 Paul Howarth p...@city-fan.org - 1.25-1
+- Update to 1.25 (fix t/nonblock.t for OS X 10.5 - CPAN RT#47240)
+
* Thu Apr 2 2009 Paul Howarth p...@city-fan.org - 1.24-1
- Update to 1.24 (add verify hostname scheme ftp, same as http)
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/sources,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -p -r1.17 -r1.18
--- sources 3 Apr 2009 09:20:34 - 1.17
+++ sources 3 Jul 2009 08:33:25 - 1.18
@@ -1 +1 @@
-53a407291bf9b3e09ae0f0cff90799a9 IO-Socket-SSL-1.24.tar.gz
+4866fb7023e74731bd379a315a021cd8 IO-Socket-SSL-1.25.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
