Hello,
Since the switch to koji I cannot rebuild my packages anymore as I am on debian, and there is no way to install koji cleanly https://fedorahosted.org/koji/ticket/91
I don't know exactly what to do in that case. Orphan my packages? Search for co-maintainers who, upon receiving cvs commit, would build the package? If somebody is interested in that, please put you at least in watchcommits and commit for my EPEL packages (and preferably also in watchbugzilla and I would gladly accept full co-maintainer).
In any case my packages will new maintainers for EL-6 since I won't maintain them myself given that I am not in fedora anymore -- though I could co-maintain them, like I do for my former fedora packages.
-- Pat
On Sun, Jun 28, 2009 at 1:46 AM, Patrice Dumaspertusus@free.fr wrote:
Hello,
Since the switch to koji I cannot rebuild my packages anymore as I am on debian, and there is no way to install koji cleanly https://fedorahosted.org/koji/ticket/91
I don't know exactly what to do in that case. Orphan my packages? Search for co-maintainers who, upon receiving cvs commit, would build the package? If somebody is interested in that, please put you at least in watchcommits and commit for my EPEL packages (and preferably also in watchbugzilla and I would gladly accept full co-maintainer).
In any case my packages will new maintainers for EL-6 since I won't maintain them myself given that I am not in fedora anymore -- though I could co-maintain them, like I do for my former fedora packages.
Hello Patrice, thankyou for all your help and work in the past. How many packages do you currently maintain? It would probably be good to work on a transition plan sot hat the 4,5, and 6 releases are covered.
On Sun, Jun 28, 2009 at 12:03:41PM -0600, Stephen John Smoogen wrote:
Hello Patrice, thankyou for all your help and work in the past. How many packages do you currently maintain? It would probably be good to work on a transition plan sot hat the 4,5, and 6 releases are covered.
I maintain 62 packages, Kevin did the list.
For the 4 and 5 releases, I'll send the build requests to Kevin. For EL-6, people have to step up and ask for branches as usual, I think. I don't think there is even an implicit promise that a package will be available for the next release. Maybe what is needed is a way to have the list of packages that are up for grabs for recent releases only, for instance all my EPEL packages for EL-6.
For existing distribution, maybe it would be nice to have a summary page that shows which packages are in FC-X and not in EL-Y. Problem is that it would also list some packages that are not in EL on purpose (for example, for my packages, acpi, and bes for EL-4 and EL-5).
-- Pat
On Sun, 28 Jun 2009 09:46:18 +0200 Patrice Dumas pertusus@free.fr wrote:
Hello,
Since the switch to koji I cannot rebuild my packages anymore as I am on debian, and there is no way to install koji cleanly https://fedorahosted.org/koji/ticket/91
:(
Can you run a virtual instance on one of your machines, or use some remote virtual like amazon EC2?
I don't know exactly what to do in that case. Orphan my packages? Search for co-maintainers who, upon receiving cvs commit, would build the package? If somebody is interested in that, please put you at least in watchcommits and commit for my EPEL packages (and preferably also in watchbugzilla and I would gladly accept full co-maintainer).
I could do that if need be. Or I might be able to set you up with a login here on a fedora machine to use for builds and such.
In any case my packages will new maintainers for EL-6 since I won't maintain them myself given that I am not in fedora anymore -- though I could co-maintain them, like I do for my former fedora packages.
ok.
These 62 epel packages seem to be the ones you are listed as maintainer on. I guess some may have co-maintainers already who might want to be primary maintainer:
BibTool acpitool asa bibexport bitmap boolstuff cernlib cernlib-g77 cppunit dap-freeform_handler dap-hdf4_handler dap-netcdf_handler dap-server docbook2X elektra esmtp flasm g2clib gnochm gpicview grads halevt html2ps kchmviewer libdap libdockapp libesmtp libnc-dap libsx ooo2txt pam_ssh perl-Algorithm-CurveFit perl-Cache perl-Feed-Find perl-File-BaseDir perl-File-DesktopEntry perl-File-MimeInfo perl-File-NFSLock perl-HTML-FormatText-WithLinks perl-Heap perl-LWP-Authen-Wsse perl-Math-MatrixReal perl-Math-Symbolic perl-Module-Signature perl-Parse-Yapp perl-Statistics-Descriptive perl-Test-Distribution perl-Text-CHM perl-Text-Unidecode pmount ps2eps python-chm tetex-elsevier tetex-lineno tetex-tex4ht uread wdm wmacpi wmix xbae xchm xdialog
kevin
On Sun, Jun 28, 2009 at 02:59:08PM -0600, Kevin Fenzi wrote:
:(
Can you run a virtual instance on one of your machines, or use some remote virtual like amazon EC2?
I don't have enough disk space nor knowledge for a virtual instance. And I wouldn't trust a distant service (not to mention that I won't pay for the free software I do).
I could do that if need be. Or I might be able to set you up with a login here on a fedora machine to use for builds and such.
Ok, I'll send you my build needs, it should be very very rare anyway, thanks.
In any case my packages will new maintainers for EL-6 since I won't maintain them myself given that I am not in fedora anymore -- though I could co-maintain them, like I do for my former fedora packages.
ok.
As a side note, tetex-lineno is only for EL-4, I'd be in favor of dropping wdm it is dead upstream and too complicated, in my opinion, to be maintained only in fedora. Some of my former fedora packages should be added, like bes (though it is still orphaned in fedora), gnash.
These 62 epel packages seem to be the ones you are listed as maintainer on. I guess some may have co-maintainers already who might want to be primary maintainer:
Indeed. Manuel, for example is co-maintainer of some of them and is in EPEL.
BibTool acpitool asa bibexport bitmap boolstuff cernlib cernlib-g77 cppunit dap-freeform_handler dap-hdf4_handler dap-netcdf_handler dap-server docbook2X elektra esmtp flasm g2clib gnochm gpicview grads halevt html2ps kchmviewer libdap libdockapp libesmtp libnc-dap libsx ooo2txt pam_ssh perl-Algorithm-CurveFit perl-Cache perl-Feed-Find perl-File-BaseDir perl-File-DesktopEntry perl-File-MimeInfo perl-File-NFSLock perl-HTML-FormatText-WithLinks perl-Heap perl-LWP-Authen-Wsse perl-Math-MatrixReal perl-Math-Symbolic perl-Module-Signature perl-Parse-Yapp perl-Statistics-Descriptive perl-Test-Distribution perl-Text-CHM perl-Text-Unidecode pmount ps2eps python-chm tetex-elsevier tetex-lineno tetex-tex4ht uread wdm wmacpi wmix xbae xchm xdialog
-- Pat
On Fri, 3 Jul 2009 09:36:25 +0200 Patrice Dumas pertusus@free.fr wrote:
On Sun, Jun 28, 2009 at 02:59:08PM -0600, Kevin Fenzi wrote:
:(
Can you run a virtual instance on one of your machines, or use some remote virtual like amazon EC2?
I don't have enough disk space nor knowledge for a virtual instance. And I wouldn't trust a distant service (not to mention that I won't pay for the free software I do).
Yeah. Understandable.
I could do that if need be. Or I might be able to set you up with a login here on a fedora machine to use for builds and such.
Ok, I'll send you my build needs, it should be very very rare anyway, thanks.
Happy to help. I assume you will be watching for bugs on the packages still?
In any case my packages will new maintainers for EL-6 since I won't maintain them myself given that I am not in fedora anymore -- though I could co-maintain them, like I do for my former fedora packages.
Yeah, we should come up with concrete plans for EL-6.
One thought was to do a mass build of all the fedora packages in whatever release EL-6 is based off of. See how many of them build ok, etc. Then try and see if we can have enough coverage to maintain them all in EL-6 somehow.
kevin
epel-devel@lists.fedoraproject.org