[opensuse-packaging] pstoedit still needs new maintainer
Hello, I cannot maintain the package pstoedit. Currently it does not build in Factory because: ------------------------------------------------------------- dynload.cpp:141:6: error: #elif with no expression make[1]: *** [dynload.lo] Error 1 ------------------------------------------------------------- I have no time at all to look at it (regardless how little effort it might be to fix it). Perhaps one of kde-maintainers@suse.de gnome-maintainers@suse.de or sbrabec@novell.com could maintain it because they need it: $ whatdependson pstoedit - autotrace (sbrabec@novell.com) - koffice2 (kde-maintainers@suse.de) $ whatdependson -R pstoedit - inkscape [pstoedit=3.45-2.41] $ maintainer inkscape gnome-maintainers@suse.de FYI: "whatdependson" is an internal Suse/Novell tool "whatdependson package" shows build dependencies i.e. for which other packages is the package needed to build the other packages. "whatdependson -R package" shows run-time dependencies i.e. which other packages require the package to be installed so that the other packages work o.k. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 28 May 2009 09:31:51 Johannes Meixner wrote:
Currently it does not build in Factory because: ------------------------------------------------------------- dynload.cpp:141:6: error: #elif with no expression make[1]: *** [dynload.lo] Error 1 -------------------------------------------------------------
I have no time at all to look at it (regardless how little effort it might be to fix it).
Hi Johannes, I am not directly saying that I can take the maintenance of this package, but I will try to build it in my home-project to see if I can fix the error. If yes, then I might take the ownership. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 28 May 2009 09:31:51 Johannes Meixner wrote:
I cannot maintain the package pstoedit.
Currently it does not build in Factory because: ------------------------------------------------------------- dynload.cpp:141:6: error: #elif with no expression make[1]: *** [dynload.lo] Error 1 -------------------------------------------------------------
I have no time at all to look at it (regardless how little effort it might be to fix it).
Hi Johannes, I have rebuild the package in my home-project and fixed the above error. If you want I can take over and become the maintainer for this package. This also reminds me of the other package python-ReportLab that I took over. I have it build successfully in my home-project, awaiting the changes that are required to make me the official maintainer for this package. I will talk to Coolo about this to see what needs to be done. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 28 May 2009 09:31:51 Johannes Meixner wrote:
I cannot maintain the package pstoedit.
Hi Johannes, It seems that every Factory packages requires an Novell internal maintainer. This is part of the information I got from wolfiR: [11:38] <wolfiR> every Factory package needs a Novell internal maintainer [11:39] <wolfiR> usually if there are external contributors there exists a development project for the package you want to maintain [11:39] <wolfiR> then you can submitreq changes to that repo or probably even get write access to the devel repo [11:39] <wolfiR> the Novell internal maintainer has to review the changes and submit them to Factory This would be valid for both packages python-ReportLab and pstoedit. An possibility would be that I create a SR to your devel-repo and that you submit them to Factory after review. An alternative would be if there is another devel repo for the above mentioned packages (e.g. Gnome or KDE Desktop). Please let me know how to proceed in this case. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hello, On May 28 11:51 Raymond Wooninck wrote (shortened):
It seems that every Factory packages requires an Novell internal maintainer.
Therefore I wrote: ---------------------------------------------------------------- Perhaps one of kde-maintainers@suse.de gnome-maintainers@suse.de or sbrabec@novell.com could maintain it because they need it: $ whatdependson pstoedit - autotrace (sbrabec@novell.com) - koffice2 (kde-maintainers@suse.de) $ whatdependson -R pstoedit - inkscape [pstoedit=3.45-2.41] $ maintainer inkscape gnome-maintainers@suse.de ----------------------------------------------------------------
An possibility would be that I create a SR to your devel-repo and that you submit them to Factory after review.
No. I have no time at all to review it. I wrote: ----------------------------------------------------------------- I have no time at all to look at it (regardless how little effort it might be to fix it). ----------------------------------------------------------------- None of "my" packages needs pstoedit and I have no personal interest in pstoedit but other packages need pstoedit so that - as far as I see - the only reasonable way is: Either those who need it must maintain it or those who need it may find out they actually do not need it (perhaps it is actually only optionally "needed") so that we can drop it from Factory. Alternatively: A Novell internal higher priority to fix pstoedit gets enforced than anything else what I work on (i.e. fix pstoedit gets a higher priority than anything regarding printing and scanning). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Johannes Meixner wrote:
---------------------------------------------------------------- Perhaps one of kde-maintainers@suse.de gnome-maintainers@suse.de or sbrabec@novell.com could maintain it because they need it:
$ whatdependson pstoedit - autotrace (sbrabec@novell.com) Well, I can take the package. I already wrote the pcb patch for it.
-- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 28 May 2009 12:19:39 you wrote:
On May 28 11:51 Raymond Wooninck wrote (shortened):
It seems that every Factory packages requires an Novell internal maintainer.
Therefore I wrote: ---------------------------------------------------------------- Perhaps one of kde-maintainers@suse.de gnome-maintainers@suse.de or sbrabec@novell.com could maintain it because they need it:
Dear Johannes, Fortunately pstoedit already found a new maintainer in Stanislav, but this means that there is no maintainer any more for python-ReportLab. I would more than happy to maintain the package, but as I am just an external contributor I need a devel repo and an internal Novell maintainer before any changes can be submitted to factory. Given that nobody else indicated that they could take care of the package, I see only two alternatives going forward : 1) The package python-ReportLab is marked as unmaintained and as such I believe it should be removed from Factory. 2) The package python-ReportLab is marked as externally maintained and as such the package it moved from Factory to Contrib. Once in Contrib I can maintain it. There is an alternative in which external contributors are allowed to maintain Factory-packages if those packages falls into certain categories (e.g. No other package depends on it, etc). I would like to ask you and the other official Factory maintainers to let me know which option is preferred for the python-ReportLab packge, but also to keep in mind future requests where the official maintainers can no longer maintain certain packages. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag, 28. Mai 2009 11:51:00 schrieb Raymond Wooninck:
On Thursday 28 May 2009 09:31:51 Johannes Meixner wrote:
I cannot maintain the package pstoedit.
Hi Johannes,
It seems that every Factory packages requires an Novell internal maintainer. This is part of the information I got from wolfiR:
That was true for the past, but is about to change. There will be an announcement from Henne regarding this soon.
[11:38] <wolfiR> every Factory package needs a Novell internal maintainer [11:39] <wolfiR> usually if there are external contributors there exists a development project for the package you want to maintain [11:39] <wolfiR> then you can submitreq changes to that repo or probably even get write access to the devel repo [11:39] <wolfiR> the Novell internal maintainer has to review the changes and submit them to Factory
This would be valid for both packages python-ReportLab and pstoedit. An possibility would be that I create a SR to your devel-repo and that you submit them to Factory after review.
An alternative would be if there is another devel repo for the above mentioned packages (e.g. Gnome or KDE Desktop).
Please let me know how to proceed in this case.
Maybe just wait for two more weeks. But it should be no problem (at least from technical and policy point of view) to join any existing project which is used Factory submissions. Also submissions from there should be possible. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hello Stanislav, On May 28 13:10 Stanislav Brabec wrote (shortened):
Johannes Meixner wrote:
---------------------------------------------------------------- Perhaps one of kde-maintainers@suse.de gnome-maintainers@suse.de or sbrabec@novell.com could maintain it because they need it:
$ whatdependson pstoedit - autotrace (sbrabec@novell.com)
Well, I can take the package. I already wrote the pcb patch for it.
Many Thanks! I set sbrabec@novell.com as maintainer in our internal PDB and changed its BSDevelProject to openSUSE.org:home:sbrabec:Factory As far as I know it takes some time (perhaps until tomorrow) until those changes in our internal PDB have been committed to the openSUSE build service. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 28 May 2009 11:51:00 Raymond Wooninck wrote:
Hi Johannes,
It seems that every Factory packages requires an Novell internal maintainer.
Correct for today - but this will change pretty soon (in June). Henne will send out some mails soonish, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (5)
-
Adrian Schröter -
Andreas Jaeger -
Johannes Meixner -
Raymond Wooninck -
Stanislav Brabec