November 2007 - openSUSE Build Service

Re: [opensuse-buildservice] Re: Including Qmail + vpopmail + ... to BuildService
by aledr 30 Nov '07

30 Nov '07

I've commented the line 471 of /usr/lib/obs/server/bs_worker to enable the root build and worked perfectly for me. To compile qmail as non root user we have the problem of permissions. I'm contacting You in private to send the build log and the spec file (the spec is in a initial release). As I said, for now, there is no way to build vpopmail as abuild, but soon it'll be solved (according vpopmail developers). 2007/11/30, aledr <matrixworkstation(a)gmail.com>: > I'll do that right now. I sent a message to the vpopmail list last > month asking for a non root build, and after a while they said that > will make it possible in the next releases. I'm waiting for them, but > qmail itself is a problem, I'll try to fix It again today. > > Many regards! > Thanks for your quickly replies! > > 2007/11/30, Adrian Schröter <adrian(a)suse.de>: > > On Friday 30 November 2007 15:41:04 wrote Adrian Schröter: > > ... > > > > There are some projects at build service but or they are not updated > > > > (like maildrop as example) or they didn't build successful. > > > > Is there a way to apply a patch to my local build service or to > > > > provide "build as root" int the openSuSE build service? > > > > > > Just do not call the bs_worker with the --norootforbuild switch. > > > > sorry, the build script must not be called with --norootforbuild. > > > > search the line with --norootforbuild in bs_worker code and remove it. > > > > bye > > adrian > > > > -- > > > > Adrian Schroeter > > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > > email: adrian(a)suse.de > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > > For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org > > > > > -- > [ ]'s > Aledr - Alexandre > "OpenSource Solutions for SmallBusiness Problems" > -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"

1 0

[opensuse-buildservice] Re: Including Qmail + vpopmail + ... to BuildService
by Adrian Schröter 30 Nov '07

30 Nov '07

On Friday 30 November 2007 15:26:15 wrote aledr: > Good day! > > Qmail is officially public domain now! \o/ > So we can include It into openSuSE. =D > > But now I went out to the same issue I've asked some time ago: some > packages needs to be build as root and the build service does not > allow It. > There are some projects at build service but or they are not updated > (like maildrop as example) or they didn't build successful. > Is there a way to apply a patch to my local build service or to > provide "build as root" int the openSuSE build service? Just do not call the bs_worker with the --norootforbuild switch. Actually we could allow this in OBS instance as well, since we are secured by XEN, but I would like to enfore a bit more clean package builds ;) But couldn't you fix the qmail build enviroment to support non-root builds ? It would be really helpfull for all packages ;) bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] unsubscribe
by Adam Lebsack 30 Nov '07

30 Nov '07

unsubscribe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] giftrans not found in xUbuntu_7.10
by Tom Parker 30 Nov '07

30 Nov '07

I can't seem to build my package as it needs giftrans, and the xUbuntu_7.10 repository doesn't appear to include giftrans, despite it being present in Ubuntu since dapper (http://packages.ubuntu.com/cgi-bin/search_packages.pl?searchon=names&versio…) Ideas? Also, there's no build service product in the Novell Bugzilla, so I can't register this there yet, and linking to it as "report a bug" from the build service is not so useful right now. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Re: merge request concept page from Klaas
by Klaas Freitag 30 Nov '07

30 Nov '07

Hi, this is a followup on a discussion about package merge requests that slipped inside accidentially, sorry for that. It discusses the first draft of the concept here: > >> http://en.opensuse.org/Build_Service/Concepts/Merge_Request I already updated the wiki page according to the discussion in this mail. [adrian & abauer wrote:] > > what about this version: > > > > <mergerequest creationTS="..."> > > <source project="home:<person>" package="my_package"/> > > <destination project="openSUSE:Factory" package="your_package"/> > > <state>new|declined|accepted|deleted|review</state> > > <reason> please fix your build first and resubmit ! </reasons> > > </mergerequest> Ok, the difference is that there is a source- and a destination tag which is nice. You also propose to not restrict source packages/projects to a special directory which I wrote down initially. That also sounds very reasonable for me now, the reason why I did that initially was that it would make /search/requests/merge/<username> easier. > Klaas, could you explain the meaning of the name and desc elements? They have the same meaning as the word 'Klaas' in the sentence above ;o) Everything needs a name, why not a patch proposal? People probably prefer to talk about the "Enable PDF"-Patch for Okular than about the ??? Patch Proposal. And one of the targets of this is to foster talking about these requests I think. Description gives the requester the chance to give some explanation. Name and description are of course "weak" attributes which are usefull for human beings and not so much for needed from a technical POV (beside the name, see below). > Why is the prefix named /request/branches? Wouldn't /request/merge make > more sense? Sure. > > GET /request/branches/project and GET /search/branches/project looks to > me as they serve the same purpose. Yes, they do. But I think they should be both there for consistency of the API. And maybe in the future the /search path might be more featurerich like searching with wildcards or so which we probably do not implement for dir listings. > How is a request identified? Is this the name field you propose? How > would this name be determined? Shouldn't the request identifier be put > into the URI? Yeah - thats a real good question. The initial proposal only allows one request per package which is probably not what we want. Why not use the name from above for this? That gives us this URIs /requests/branches/<project>/<package>/<name> for example /requests/branches/KDE4/okular/enable_pdf Thank you all for taking the time to read and comment :-) regards, Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] [ANN] new osc release
by Dr. Peter Poeml 30 Nov '07

30 Nov '07

Hi, Marcus and I rolled a new osc package. osc got two new commands, and bug fixes. - rdiff: new command for server-side diffs between arbitrary packages - cat: new command to print a file on the standard output - diff: reworked functionality to show newly added files, and behaving more like svn when doing diff against a certain revision - bugfix in {link,aggregate,copy}_pac (<person> elements) - checkout an empty project instead of doing nothing - fix prjresults for newly added packages, where build status is missing Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

Re: [opensuse-buildservice] New project "drivers:wireless"
by Adrian Schröter 30 Nov '07

30 Nov '07

On Thursday 29 November 2007 15:00:10 wrote Mauricio Teixeira: > On Thu, 2007-11-29 at 13:46 +0100, Adrian Schröter wrote: > > > I'd like to create a new project "drivers:wireless" to push out some > > > wireless-drivers for testing. > > > > > > Is that possible? > > > > we have already a "drivers:wlan" project, how about to join there ? > > > > Project owners are CC'd. > > Sorry guys. I'm not using SUSE anymore. :( > > You can handle ownership to someone else. k, I suggest to drop drivers:wlan and to create drivers:wireless for Helmut in that case. Helmut, please tell me your account name in PM. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6

[opensuse-buildservice] urllib2.HTTPError: HTTP Error 502: Bad Gateway
by Karl Eichwalder 30 Nov '07

30 Nov '07

Committing https://build.opensuse.org/package/show?project=XML&package=tei_5 with osc this error occurs: urllib2.HTTPError: HTTP Error 502: Bad Gateway I tried again and arbitrary sequence of osc commands (up and ci), the repository now looks fine to me. I verified it with a new checkout. Strangely, the build service still tries to build the previous version (0.6, obviously using an old SPEC) and fails, because the source packages do not match any longer. But if I view the SPEC, it is version 1.0. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] i586 stills failing
by aledr 29 Nov '07

29 Nov '07

I've installed obs-worker-0.1.1_2643-2, obs-api-0.1.1_2643-2 and obs-server-0.1.1_2643-2, and there's the same issue for i586 builds: " build on server/2 did not create a logfile" Anybody else with the same problem? -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Re: Novell ID's for OSC Plugins
by Dr. Peter Poeml 29 Nov '07

29 Nov '07

Hi, how about discussing this on the public opensuse-buildservice list? I'm sending my reply there. On Thu, Nov 29, 2007 at 01:12:33PM +0100, Adrian Schröter wrote: > Regarding the current status of the diff functionality, what you asked for, > from https://api.opensuse.org/apidocs > > POST /source/<project>/<package>?cmd=diff > Arguments: > project - Project name > package - Package name > Create a source diff > rev: revision of new package, optional oproject: old project, optional > opackage: old package, optional orev: old revision, optional > Result: diff as text/plain > > So you can do this via the api: > > curl -X POST -H "Content-Length: 0" -0 -n \ > "https://api.opensuse.org/source/openSUSE:Tools/build?cmd=diff&oproject=open…" An osc equivalent of this command would be osc req -m POST "/source/openSUSE:Tools/build?cmd=diff&oproject=openSUSE:Factory" > to diff the new "build" package in openSUSE:Tools project against the version > in openSUSE:Factory . > > osc has IMHO not yet a nice interface for this (something like cvs rdiff). > Right Peter ? > > bye > adrian osc has no support for requesting a diff between *two* arbitrary packages. So far, "osc diff" can create diffs of different revisions of *one* package. It should be possible to implement an osc subcommand for this with a few lines. To integrate the functionality into the existing osc diff subcommand might be a little more work (it needs some consideration to come up with a sane user interface). Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

3 7