What is oscupstream?
I can not find a lot of documentation on it.
Is it ready for prime time?
--
Paul Elliott 1(512)837-1096
pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J
http://www.io.com/~pelliott/pme/ Austin TX 78758-3117
Hi,
Even I've observed that "# norootforbuild" isn't considered when building the package. In my local OBS installation, I've to modify the scripts to remove "--norootforbuild" option to always build as root - I know its not advisable to build RPMs as root, but sometimes its inevitable. :(
Srinidhi.
>>> aledr <matrixworkstation(a)gmail.com> 09/30/07 1:35 AM >>>
Hi!
I've built spamassassin perfectly on my machine using "# norootforbuild".
But I ever get this message when trying to build in the webclient:
"+ exit 0
Finding Provides: /usr/lib/rpm/find-provides spamassassin
error: Couldn't exec
/usr/src/packages/SOURCES/filter-requires-spamassassin.sh: Permission
denied
getOutputFrom(): Broken pipe"
And here is the content of the script:
"#!/bin/sh
/usr/lib/rpm/find-requires $* | grep -v 'perl(Net::SMTP::Server' |
grep -v 'perl(MIME::Body'"
Thanks in advice. :D
--
[ ]'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
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
I did like specified in the wiki, I did not provide a debian changelog file so
that the buildservice would build one based in the .changes file for me.
But It did not work, I get:
dpkg-parsechangelog: error: cannot open debian/changelog to find format: No
such file or directory
dpkg-buildpackage: unable to determine source package is
So what is the solution ?
My package is:
http://build.opensuse.org/package/show?project=home%3Aamilcarlucas&package=…
--
Amilcar Lucas
Webmaster
The KDevelop project
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
"Dr. Peter Poeml" <poeml(a)suse.de> writes:
> Hi Susanne,
>
> On Thu, Sep 27, 2007 at 09:41:58AM +0200, Susanne Oberhauser wrote:
> > cool, thx, what would be a good place for this on the wiki?
> > http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
> > ?
>
> Yes, I'd think so!
ok :)
would you mind to have a look wether the sample code is correct?
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to#Buil…
S.
--
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
Partner Engineering Maxfeldstraße 5
developer.novell.com 90409 Nürnberg
SUSE LINUX GmbH, GF: Volker Smid, HRB 21284 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Marcus Rueckert <mrueckert(a)suse.de> writes:
> On 2007-09-26 19:51:30 +0200, Christian Boltz wrote:
> > on Mittwoch, 26. September 2007, Susanne Oberhauser wrote:
> > > I just updated the svn file property to actually update the Revision
> > > string, as I hoped the next release should at least have a
> > > meaningfull svn revision in it:
> >
> > > Then I realized this string will only be updated when this very file
> > > changes. Hmmm.
> >
> > What about using the output of
> > svn info |grep Revision
>
> wrong approach. svn trees can have mixed revisions.
> http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.i…
>
> the correct approach is described here:
> http://subversion.tigris.org/faq.html#version-value-in-source
>
> darix
thx for the pointer.
Hmmm... That then needs a svn co instead of a svn export in the tar
ball, though.
I'd rather prefer to have the whole source package in svn and collect
all files that are needed in some script.
Like a 'dist/' subdir in
https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice, in there
the extra files you need for distribution and packaging, for starters
all the files of the package, plus some Makefile somewhere that runs a
svn export and extracts the revision from the output and then wraps
all that's needed to a source_rpm.
A buildservice/documentation/common/xslt/common/de.xml
A buildservice/documentation/common/xslt/common/l10n.xml
Exported external at revision 313.
Exported revision 2265.
Wether this helps or not depends on how we want to manage the build
server deployment / 'maintenance' of the obs-* packages going forward.
I'd personally prefer to have a working copy checked out in svn, work
on that, do my builds locally from a directory in there (containing
the spec file and some more), update that locally built package and
once everything works upload the working dir to the bs.
This approach is using the priviledge of being the maintainer of both
the code and the package.
Alternative is to do as if the code maintainers and the package
maintainers were not the same: work on the package until it works for
distribution, then integrate the changes and add-on files to the svn,
then adjust the package for that, having parts of what you need
manitained with osc or such and parts of it in svn.
We _can_ do that and we do it right now.
S.
--
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
Partner Engineering Maxfeldstraße 5
developer.novell.com 90409 Nürnberg
SUSE LINUX GmbH, GF: Volker Smid, HRB 21284 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Cornelius Schumacher <cschum(a)suse.de> writes:
> On Tuesday 18 September 2007 08:43, Martin Mohring wrote:
> >
> > I would also suggest to have "obs-server-development" and
> > "obs-server-deployment" packages, like we have e.g.
> > for the linux kernel.
>
> What would these packages contain? Different versions of the build service or
> do you think of splitting off parts only needed for development?
>
> > Maybe Adrian provides us with some Information, on which Revision
> > .opensuse.org OBS deployment is based.
>
> There is http://build.opensuse.org/main/about, but it doesn't seem
> to be up to date or overly useful. Maybe it would be nice to fix
> this page to actually show which versions are deployed.
I just updated the svn file property to actually update the Revision
string, as I hoped the next release should at least have a meaningfull
svn revision in it:
0 froh@byron:/home/SVN/opensuse-forge/trunk/buildservice $ \
svn propset svn:keywords "Revision" ./src/webclient/app/views/main/about.rhtml
Then I realized this string will only be updated when this very file
changes. Hmmm.
So we should rather add the rpm package version to that file during
build.
Would this do?
0 froh@byron:/tmp/openSUSE:Tools/obs-server $ osc diff
Index: obs-server.spec
===================================================================
--- obs-server.spec (revision 100)
+++ obs-server.spec (working copy)
@@ -81,6 +81,8 @@
mkdir -p $RPM_BUILD_ROOT/srv/www/obs/
cp -a $i $RPM_BUILD_ROOT/srv/www/obs/$i
done
+# add version to 'about' page
+echo '<p>Build: %{version}-%{release}</p>' >> $RPM_BUILD_ROOT/srv/www/obs/webclient/app/views/main/about.rhtml
# configure lighttpd web service
mkdir -p $RPM_BUILD_ROOT/etc/lighttpd/vhosts.d/
install -m 0644 %SOURCE7 $RPM_BUILD_ROOT/etc/lighttpd/vhosts.d/
Index: obs-server.changes
===================================================================
--- obs-server.changes (revision 100)
+++ obs-server.changes (working copy)
@@ -1,3 +1,8 @@
+-------------------------------------------------------------------
+Wed Sep 26 17:21:23 CEST 2007 - froh(a)novell.com
+
+- add build id to about page in front end
+
-------------------------------------------------------------------
Fri Jan 26 16:20:12 CET 2007 - poeml(a)suse.de
I feel a bit hacky about it, but I wonder to which extend what we have
in svn is made for being packaged and distributed yet, and what the
common practice is to set up some ruby app for being packaged and
distributed?
S.
--
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
Partner Engineering Maxfeldstraße 5
developer.novell.com 90409 Nürnberg
SUSE LINUX GmbH, GF: Volker Smid, HRB 21284 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On 2007-09-26 08:42:53 -0600, Novell Forge SVN wrote:
> Author: froh
> Date: 2007-09-26 08:42:49 -0600 (Wed, 26 Sep 2007)
> New Revision: 2263
>
> Modified:
> trunk/buildservice/src/webclient/app/views/main/about.rhtml
> Log:
> - enable keyword expansion so the about pages shows a meaningfull svn
> revision
>
>
> Modified: trunk/buildservice/src/webclient/app/views/main/about.rhtml
> ===================================================================
> --- trunk/buildservice/src/webclient/app/views/main/about.rhtml 2007-09-26 14:13:14 UTC (rev 2262)
> +++ trunk/buildservice/src/webclient/app/views/main/about.rhtml 2007-09-26 14:42:49 UTC (rev 2263)
> @@ -5,4 +5,4 @@
> <p>This is the web client for the openSUSE build service.</p>
> <p>Check the openSUSE <a href="http://en.opensuse.org/Build_Service">
> openSUSE Build Service wiki page</a> for details.</p>
> -<p>SVN Revision: $Revision: 509 $</p>
> +<p>SVN Revision: $Revision$</p>
>
>
> Property changes on: trunk/buildservice/src/webclient/app/views/main/about.rhtml
> ___________________________________________________________________
> Name: svn:keywords
> + Revision
this change doesnt help. as it would only expand to the last changed
revision of the about.rhtml. this is not the revision of the whole tree.
see this FAQ entry
http://subversion.tigris.org/faq.html#version-value-in-source
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi, don't know if this is known and/or intended. When you specify an
URI the download de source from, it only works with http. If you
specify a ftp server it dies with a time out.
Regards,
Ciro
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
[Amber]
* The Build Service backend server is filled to 95%, what is really critical.
We will get double space as soon as the new build service backend server has
been fixed (hardware damage).
Space on SAN is already prepared.
We may need to remove some old base distros to get some more space
meanwhile.
Quota system is urgently needed anyway.
* Thomas Scholz, writing his thesis has successfully finished is studies and
is leaving us. Thomas, thanks a lot for your good work, you made really good
contributions like the TAG system, the new build flag implementation and
lots of other improvements or bugfixes.
I wish you all the best for your future and please call back when you are
around.
[Green]
* openSUSE 10.3 has been imported and updated to RC1 inside of the OBS.
* Many Build Service Team members are on tour (vacation, movement or
trainings) this week.
--
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
Hi.
I added repo 10.3 for my home project (lmich) few weeks ago. But I
can't see it in the directory:
http://download.opensuse.org/repositories/home:/lmich/. The packages
are built successfully.
Where could be the problem?
Regards Ladislav.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org