[opensuse-buildservice] New project: usr-local-bin
Would there be any objections to me creating a new project 'usr-local-bin' for the packages that have historically formed the usr-local-bin project? -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2006-10-27 20:10:25 +0100, James Ogley wrote:
Would there be any objections to me creating a new project 'usr-local-bin' for the packages that have historically formed the usr-local-bin project?
hmm iirc you mostly had newer gnome stuff? wouldnt it be more useful to have something like GNOME:community? as we have it with KDE:community already? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
hmm iirc you mostly had newer gnome stuff? wouldnt it be more useful to have something like GNOME:community? as we have it with KDE:community already?
I'd be very happy to do this if the other GNOME guys are happy: Stanislav/JP/Gary? (That way I'll keep my non-GNOME stuff in my home project) -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2006-10-27 20:28:10 +0100, James Ogley wrote:
(That way I'll keep my non-GNOME stuff in my home project)
how much non gnome stuff do you have? and what is your home project?:) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
how much non gnome stuff do you have?
At the moment, nothing in the project, but I'll be adding camE & its dependency, giblib as soon as I get around to it.
and what is your home project?:)
home:Riggwelter, which is awkward since the iChain authentication came in because it forces the username to lower case. This means that strictly, it's home:riggwelter if I click on 'Home Project'. I've had to add the capitalised version to my watched projects list. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, 2006-10-27 at 20:28 +0100, James Ogley wrote:
hmm iirc you mostly had newer gnome stuff? wouldnt it be more useful to have something like GNOME:community? as we have it with KDE:community already?
I'd be very happy to do this if the other GNOME guys are happy: Stanislav/JP/Gary?
That sounds perfectly fine to me. -Gary --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 2006-10-30 at 06:24 -0700, Gary Ekker wrote:
On Fri, 2006-10-27 at 20:28 +0100, James Ogley wrote:
hmm iirc you mostly had newer gnome stuff? wouldnt it be more useful to have something like GNOME:community? as we have it with KDE:community already?
I'd be very happy to do this if the other GNOME guys are happy: Stanislav/JP/Gary?
That sounds perfectly fine to me.
I'm sure we all want James to put his GNOME packaging effort in that
GNOME:whatever :-) But we need to make sure we don't duplicate effort
between the internal packaging and the openSuSE packaging. Right now,
what we can do is synchronize the internal packages to openSuSE, as is
done with KDE AFAIK.
Or anyway, James, what is your plan, package unstable GNOME?
--
Rodrigo Moya
I'm sure we all want James to put his GNOME packaging effort in that GNOME:whatever :-) But we need to make sure we don't duplicate effort between the internal packaging and the openSuSE packaging. Right now, what we can do is synchronize the internal packages to openSuSE, as is done with KDE AFAIK. Or anyway, James, what is your plan, package unstable GNOME?
I agree that we don't want to duplicate efforts, that would waste all our time. The way I would envisage a GNOME:community based on darix's suggestion would be extra packages that don't form part of the core 'official' GNOME builds (but could in the future) So, I'd be thinking packages like gnome-themes-extras/mail-notification/sensors-applet etc... There'd also be the possibility of more recent versions of some packages than would get added to the core GNOME builds like I have in my home repo at the moment. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 2006-10-30 at 17:56 +0000, James Ogley wrote:
I'm sure we all want James to put his GNOME packaging effort in that GNOME:whatever :-) But we need to make sure we don't duplicate effort between the internal packaging and the openSuSE packaging. Right now, what we can do is synchronize the internal packages to openSuSE, as is done with KDE AFAIK. Or anyway, James, what is your plan, package unstable GNOME?
I agree that we don't want to duplicate efforts, that would waste all our time.
The way I would envisage a GNOME:community based on darix's suggestion would be extra packages that don't form part of the core 'official' GNOME builds (but could in the future)
So, I'd be thinking packages like gnome-themes-extras/mail-notification/sensors-applet etc...
you've got my vote then :-)
There'd also be the possibility of more recent versions of some packages than would get added to the core GNOME builds like I have in my home repo at the moment.
what GNOME version/packages do you mean? If it is 2.17, it might be a
good idea to package them.
--
Rodrigo Moya
what GNOME version/packages do you mean? If it is 2.17, it might be a good idea to package them.
To an extent, that would depend on what Stanislav's plans for GNOME:UNSTABLE are - if that's going to be STABLE+1 then there's no need for it. If it's going to STABLE for platforms other than Factory, then GNOME:community could also include STABLE+1. My train of thought had actually been thus: Let's say metacity is at 2.16.3 in FACTORY and 2.16.4 is released with an important bug fix. I (or another community packager) might be able to package the update more quickly than a Novell staffer. Once the FACTORY version was updated, the GNOME:community version would not be picked up by package managers anymore but it could be a handy interim measure in that sort of situation. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
James Ogley wrote:
what GNOME version/packages do you mean? If it is 2.17, it might be a good idea to package them.
To an extent, that would depend on what Stanislav's plans for GNOME:UNSTABLE are - if that's going to be STABLE+1 then there's no need for it. If it's going to STABLE for platforms other than Factory, then GNOME:community could also include STABLE+1.
I guess that GNOME:UNSTABLE should be 2.17.x or so and GNOME:STABLE 2.16.x or so. I can add you to the group.
My train of thought had actually been thus:
Let's say metacity is at 2.16.3 in FACTORY and 2.16.4 is released with an important bug fix. I (or another community packager) might be able to package the update more quickly than a Novell staffer. Once the FACTORY version was updated, the GNOME:community version would not be picked up by package managers anymore but it could be a handy interim measure in that sort of situation.
Yes, that's a problem. For example FACTORY now has stable branch, but we are after version upgrade freeze. In development phase it is OK to keep both in sync (or even sync with GNOME:UNSTABLE), but now it would be no more possible (if GNOME:STABLE will exist and be complete). Are there any scripts for SuSE -> OpenSuSE synchronization, where we can change rules? I am sorry, I planned to sync many packages from FACTORY to GNOME: but did not yet find enough time to fix failures and other issues. -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I guess that GNOME:UNSTABLE should be 2.17.x or so and GNOME:STABLE 2.16.x or so. I can add you to the group.
That would be great. In theory then, but GNOME:STABLE and GNOME:UNSTABLE can be ahead of whatever is in the current release version of [open]SUSE, even if only in terms of minor release number updates. GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well. Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
Yes, that's a problem. For example FACTORY now has stable branch, but we are after version upgrade freeze. In development phase it is OK to keep both in sync (or even sync with GNOME:UNSTABLE), but now it would be no more possible (if GNOME:STABLE will exist and be complete).
So maybe GNOME:[UN]STABLE needs to have a FACTORY repo as well as the other ones. That way even once FACTORY itself is in version freeze, people using FACTORY can still use the updates in the BS.
I am sorry, I planned to sync many packages from FACTORY to GNOME: but did not yet find enough time to fix failures and other issues.
That's okay, I imagine you're very busy. I still think it makes more sense for you to do the importing since you have access to autobuild. Once packages are imported, I can work on getting them to build (starting with glib2) and keeping them up to date. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 2006-11-09 at 08:43 +0000, James Ogley wrote:
I guess that GNOME:UNSTABLE should be 2.17.x or so and GNOME:STABLE 2.16.x or so. I can add you to the group.
That would be great. In theory then, but GNOME:STABLE and GNOME:UNSTABLE can be ahead of whatever is in the current release version of [open]SUSE, even if only in terms of minor release number updates.
GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well.
Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
I guess the GNOME:community would be what you said, packages not
packaged in the BS, or new versions of specific packages. If so, I guess
it makes a lot of sense, so yeah, go ahead, and add me to the group :)
This might force me to maintain better the (only one so far) packages I
have in my home project.
--
Rodrigo Moya
James Ogley wrote:
GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well.
Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
Feel free to create it.
Yes, that's a problem. For example FACTORY now has stable branch, but we are after version upgrade freeze. In development phase it is OK to keep both in sync (or even sync with GNOME:UNSTABLE), but now it would be no more possible (if GNOME:STABLE will exist and be complete).
Well, just now I am creating GNOME:STABLE. Please let me know about needed fixes and packages. I plan to add more application packages later.
So maybe GNOME:[UN]STABLE needs to have a FACTORY repo as well as the other ones. That way even once FACTORY itself is in version freeze, people using FACTORY can still use the updates in the BS.
Factory repository is in the intranet and has no connection to Build Service (yet). It is theoretically possible to create strictly read-only BS project GNOME:FACTORY, but I don't see a reason for it. Maybe we should define repository states as one of these: - FACTORY goes to GNOME:STABLE (and GNOME:STABLE is read-only) - FACTORY goes to GNOME:UNSTABLE (and GNOME:UNSTABLE is read-only) - FACTORY is frozen, both repositories are read-write Because just now we still fixing many problems for 10.2, I guess that we can live up to 10.2 RC with the first. It means, that all patches needed for Build Service needs to go to FACTORY just now.
I am sorry, I planned to sync many packages from FACTORY to GNOME: but did not yet find enough time to fix failures and other issues.
That's okay, I imagine you're very busy. I still think it makes more sense for you to do the importing since you have access to autobuild. Once packages are imported, I can work on getting them to build (starting with glib2) and keeping them up to date.
OK I have created simple mirroring script and try to start with a guessed package list in GNOME:STABLE. -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 2006-11-09 at 08:43 +0000, James Ogley wrote:
I guess that GNOME:UNSTABLE should be 2.17.x or so and GNOME:STABLE 2.16.x or so. I can add you to the group.
That would be great. In theory then, but GNOME:STABLE and GNOME:UNSTABLE can be ahead of whatever is in the current release version of [open]SUSE, even if only in terms of minor release number updates.
GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well.
Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
Yes, add me to it. Stanislav, would you add me to other gnome projects as well please. -Gary --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 2006-11-09 at 09:21 -0700, Gary Ekker wrote:
On Thu, 2006-11-09 at 08:43 +0000, James Ogley wrote:
I guess that GNOME:UNSTABLE should be 2.17.x or so and GNOME:STABLE 2.16.x or so. I can add you to the group.
That would be great. In theory then, but GNOME:STABLE and GNOME:UNSTABLE can be ahead of whatever is in the current release version of [open]SUSE, even if only in terms of minor release number updates.
GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well.
Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
Yes, add me to it. Stanislav, would you add me to other gnome projects as well please.
/me too
--
Rodrigo Moya
Gary Ekker wrote:
GNOME:community then would allow community members (and remember, that includes staff) to build and host packages that do not currently, or simply will not ever, form part of the core [o]S GNOME install. It could then form a handy staging area for packages that may in future be included in the distro as well.
Shall I create the GNOME:community project then? Would you (Stanislav, Gary, Rodrigo) like to be added to the group for it?
Yes, add me to it. Stanislav, would you add me to other gnome projects as well please.
Me too. (user sbrabec) Done. Please send me your user names, if you want to be added, too. I finished initial submit. The tool cannot yet be run automatically (createpac fails to sync descriptions and create package on random packages for some reasons), but it basically works. Please ping me for sync from FACTORY. I will try to sync it on regular basis in future. So the current status is: GNOME:community open for everybody (and to be created) GNOME:UNSTABLE open for everybody GNOME:STABLE sync from FACTORY. Please do not submit there anything, unless you do the same in FACTORY. When base will build, I will add more packages. I need your help: http://build.opensuse.org/project/monitor?project=GNOME%3ASTABLE I have no idea, why glib2 fails. And "expansion error" looks very strange, too. Maybe Build Service bug. -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Thursday 09 November 2006 18:40 schrieb Stanislav Brabec: ..
So the current status is:
GNOME:community open for everybody (and to be created)
You can create it yourself. Maybe you should name it :Community (capital C) to be in sync with the name at KDE. ....
And "expansion error" looks very strange, too. Maybe Build Service bug.
This usually means that a package for BuildRequires is missing. Maybe it did not build yet ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
Am Thursday 09 November 2006 18:40 schrieb Stanislav Brabec:
So the current status is:
GNOME:community open for everybody (and to be created)
You can create it yourself. Maybe you should name it :Community (capital C) to be in sync with the name at KDE.
Done.
And "expansion error" looks very strange, too.
This usually means that a package for BuildRequires is missing. Maybe it did not build yet ?
Maybe. Is there any chance to check, which package is missing? -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
You can create it yourself.
See my last mail :)
Maybe you should name it :Community (capital C) to be in sync with the name at KDE.
Happy to do that. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Done. Please send me your user names, if you want to be added, too.
Could you send them to me too please?
So the current status is: GNOME:community open for everybody (and to be created)
This is blocked by bnc #219369 at the moment
I have no idea, why glib2 fails.
Hmmm, it's the same error as in UNSTABLE isn't it? Once you've added me, I'll have a fiddle. I bet that commenting out the autoreconf will allow it to build without error. Intrigued by it though, especially since ISTR you saying that it built okay in autobuild with the same .spec and patch set. Have you filed it in bnc?
And "expansion error" looks very strange, too. Maybe Build Service bug.
Looking, randomly, at gconf-editor, it makes perfect sense, there is no gnome-doc-utils-devel package in 10.1... %if %suse_version >=1011 BuildRequires: gnome-common gnome-doc-utils gnome-doc-utils-devel intltool libgnomeui-devel libxslt mDNSResponder-devel perl-XML-Parser update-desktop-files %else BuildRequires: gnome-common gnome-doc-utils gnome-doc-utils intltool libgnomeui-devel libxslt mDNSResponder-devel perl-XML-Parser update-desktop-files %endif That should sort it (it's what I've done on packages that will go into GNOME:community that look for it). -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
James Ogley píše v Čt 09. 11. 2006 v 21:10 +0000:
Done. Please send me your user names, if you want to be added, too.
Could you send them to me too please?
So the current status is: GNOME:community open for everybody (and to be created)
This is blocked by bnc #219369 at the moment
Already created as GNOME:Community and you have been added as a maintainer. Maybe that this Internal Server Error means "project already exists" or "projects cannot differ only in case".
I have no idea, why glib2 fails.
Hmmm, it's the same error as in UNSTABLE isn't it? Yes. Once you've added me, I'll have a fiddle. Done. I bet that commenting out the autoreconf will allow it to build without error. Intrigued by it though, especially since ISTR you saying that it built okay in autobuild with the same .spec and patch set. Maybe it's the simplest solution, if its call is not required. Have you filed it in bnc? No.
Looking, randomly, at gconf-editor, it makes perfect sense, there is no gnome-doc-utils-devel package in 10.1...
%if %suse_version >=1011 BuildRequires: gnome-common gnome-doc-utils gnome-doc-utils-devel intltool libgnomeui-devel libxslt mDNSResponder-devel perl-XML-Parser update-desktop-files %else BuildRequires: gnome-common gnome-doc-utils gnome-doc-utils intltool libgnomeui-devel libxslt mDNSResponder-devel perl-XML-Parser update-desktop-files %endif
Maybe. But let's wait for solution of bug https://bugzilla.novell.com/show_bug.cgi?id=219323
That should sort it (it's what I've done on packages that will go into GNOME:community that look for it).
Feel free to use GNOME:STABLE and GNOME:UNSTABLE for fixes, only remember to send patches to FACTORY for synced projects. -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Already created as GNOME:Community and you have been added as a maintainer. Maybe that this Internal Server Error means "project already exists" or "projects cannot differ only in case".
This was before you created, but thanks for doing so :) -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Nov 09, 2006 at 06:40:20PM +0100, Stanislav Brabec wrote:
I finished initial submit. The tool cannot yet be run automatically (createpac fails to sync descriptions and create package on random packages for some reasons), but it basically works. Please ping me for sync from FACTORY. I will try to sync it on regular basis in future.
Could you give more details about what fails and how? Thanks, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
Dr. Peter Poeml wrote:
On Thu, Nov 09, 2006 at 06:40:20PM +0100, Stanislav Brabec wrote:
I finished initial submit. The tool cannot yet be run automatically (createpac fails to sync descriptions and create package on random packages for some reasons), but it basically works. Please ping me for sync from FACTORY. I will try to sync it on regular basis in future.
Could you give more details about what fails and how?
I am not sure, what failed.
I created list in GNOME\:STABLE.lst.
I did a simple loop:
for PACKAGE in $(
Hi Stanislav, thanks for the details. On Fri, Nov 10, 2006 at 02:53:28PM +0100, Stanislav Brabec wrote:
I did a simple loop:
for PACKAGE in $(
File unchanged. Not saving.
This means that osc successfully fetched the meta from the server, but EDITOR did not modify it. Ah, or rather osc _thought_ it was unmodified because it uses a simple timestamp to compare the file with. This is basically suitable for humans editing, because they need more than a second... I can change that to a real comparison. Meanwhile, you can add a small sleep ;) On the other hand, it would be even nicer if there would be a facility that wouldn't require you to work around with an EDITOR script at all. Noted in the todo.
Sometimes it reported a HTML error (sorry, it is scrolled out just now, but I guess it was 501).
I have no idea about this one. Regards, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
Dr. Peter Poeml píše v Pá 10. 11. 2006 v 16:04 +0100:
Hi Stanislav,
thanks for the details.
On Fri, Nov 10, 2006 at 02:53:28PM +0100, Stanislav Brabec wrote:
I did a simple loop:
for PACKAGE in $(
File unchanged. Not saving.
This means that osc successfully fetched the meta from the server, but EDITOR did not modify it.
I guess that EDITOR did modify it - even if pdb will fail, it will result different XML.
Ah, or rather osc _thought_ it was unmodified because it uses a simple timestamp to compare the file with. This is basically suitable for humans editing, because they need more than a second... I can change that to a real comparison. Meanwhile, you can add a small sleep ;)
OK. I'll do it.
On the other hand, it would be even nicer if there would be a facility that wouldn't require you to work around with an EDITOR script at all. Noted in the todo.
Yes.
Sometimes it reported a HTML error (sorry, it is scrolled out just now, but I guess it was 501). I have no idea about this one.
I suspect simpe HTML error (server did not respond in time, too many clients or so) It was very rare and occurred only once or twice. I will report it to you if it will occur again. -- 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 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Nov 10, 2006 at 04:09:18PM +0100, Stanislav Brabec wrote:
I guess that EDITOR did modify it - even if pdb will fail, it will result different XML.
Yes, I figured the same.
Sometimes it reported a HTML error (sorry, it is scrolled out just now, but I guess it was 501). I have no idea about this one.
I suspect simpe HTML error (server did not respond in time, too many clients or so) It was very rare and occurred only once or twice. I will report it to you if it will occur again.
The easiest is to blame iChain ;) But I'm glad I thought twice about the above issue. Thanks again :) Regards, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
participants (7)
-
Adrian Schröter
-
Dr. Peter Poeml
-
Gary Ekker
-
James Ogley
-
Marcus Rueckert
-
Rodrigo Moya
-
Stanislav Brabec