Hi there,
This script try to help eclipse packager to stay update with upstream by checking updates using the eclipse P2 api (eclipse repo), generate up-to-date specfile and send mail alert on packager - you can get more information about this script there -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=250076
It need some thing to run, here is a list: - a mail server (to send alert) - a http server to put the generated specfile. - a FAS integration to get mail address, packager name and they packages - I mail Toshio about this, hoping it's do-able.
Cheers, Alphonse
You were wanting something from https://fedorahosted.org/web/faq ?
Replying to [comment:1 mmcgrath]:
You were wanting something from https://fedorahosted.org/web/faq ? No preference where to host the code but I thing that it would be easily for eclipse linux-distros commiters if we put the code at @eclipse, Andrew?
Replying to [comment:2 alcapcom]:
Replying to [comment:1 mmcgrath]: You were wanting something from https://fedorahosted.org/web/faq ? No preference where to host the code but I thing that it would be easily for eclipse linux-distros commiters if we put the code at @eclipse, Andrew?
Yeah, we really just want a place we can run a cron job and send mail. And maybe from time to time modify what's being run.
Where is the script? The referenced bug report just seems to have patches.
Would this be useful for packagers to run on their own in addition to being run in infrastructure?
In your email you mentioned that you need to get additional information about the owners of eclipse packages. Could you define an eclipse package and owner in this context? I think you'll need to get this out of the pkgdb rather than (or in addition to) fas.
Replying to [comment:4 toshio]:
Where is the script? The referenced bug report just seems to have patches. Sorry, just attach it to the bug report. Would this be useful for packagers to run on their own in addition to being run in infrastructure? I don't think (at less if it's not personalized) In your email you mentioned that you need to get additional information about the owners of eclipse packages. Could you define an eclipse package and owner in this context? I think you'll need to get this out of the pkgdb rather than (or in addition to) fas.
Where is the script? The referenced bug report just seems to have patches. Sorry, just attach it to the bug report.
Would this be useful for packagers to run on their own in addition to being run in infrastructure? I don't think (at less if it's not personalized)
Right, if we can get the owner email of a package out pkgdb? we need the package name, owner name or nickname and the owner email.
Thanks
Like you supposed in your preview post a mix of pkgdb and fas was needed. The only issue is that fas need a username and password and at this time it's hardcoded in the script - any idea to fix that?
Now, The script need to mock build automatically all eclipse packages for each release that we support so that osgideps.pl can be run on it. I hope to have time to code that this evening.
A step deeper should be to automatically build a SRPM and scratch build it using koji but that a other story :)
for testing you can give it your FAS username and password. When we deploy it, we'll use a system account that we run all our scripts under.
Hey, sorry this hasn't had any update in a while - did this end up getting worked out somewhere, or would you still like to get that setup with us?
Replying to [comment:8 ricky]:
Yeah, we want to have that running here. Be aware that the code of this ticket is out of date and that the last version can be found there -> https://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/p2-update-checker.
Thanks, Alphonse
The last link above is now a 404. ;(
Do we still want to look at doing this? or did it get setup somewhere else?
I'm going to close this, do reopen or file a new ticket if there's anything we can do from here.
Login to comment on this ticket.