Last night's builds for the net-snmp project show a number of build failures for
the various repos, all of them happening on build03 and all of them ending in
md: stopping all md devices.
System halted.
Is build03 broken?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
how are projects and packages structured?
is it a fixed "one name for the project and then one for the package"
system, or are further subdirs possible?
I wonder about this: recent discussions with rpm experts have shown me
that merging several spec files into one only creates a horrible
maintainence hell. also they have compelling arguments, that one rpm for
all distributions was something they tried for years with lots of work,
and it never worked well.
so I see as best solution to have codenames (e.g. fc3,fc4,fc5, sles9,
sles10, oss10.0, dapper, edgy, etch, sarge, ...) and for each
distribution *.spec.$codename or *.diff.gz.$codename. but this would
require work on the build system side, and I get the impression noone
wants that.
the alternative from my side would be per distro packages.
e.g. instead of "openct" I could have packages "openct.fc" and
"openct.os" and "openct.sles" and "openct.sarge" and so on,
upload spec files for each. this wouldn't require changes in the code
base, and give me the flexibility I need, so I can simply build new
packages for my open source projects, with minimal changes to the last
spec file the distribution provides.
but that way the list of packages might grow very long. is it possible
to structure projects/packages a different way (i.e. path mechanism,
no flat one project, one package subdir structure)?
Regards, Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
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(a)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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
We are having problems getting a package to build - looks like dependncy
problems. It is a java based plugin in tomcat for AppArmor. The package
tomcat_apparmor is in factory but we would like to make a development version
available via the build service. Does the buildservice expand
java2-devel-packages to fill the required dependencies?
Here is the link showing the build problems:
http://build.opensuse.org/package/show?package=tomcat_apparmor&project=home…
Thanks,
dominic
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
Should a linked project be recompiled when the 'original' is being
modified?
Example:
The game opencity in games:strategy:realtim is linked to home:dimstar.
Last evening, I modified the source in home:dimstar and it started to
rebuild there.
But the version in games:strategy:realtime did not rebuild. Not even,
when triggering a rebuild, it contained the same information as the
original (so it remained without the modifications I did in
home:dimstar).
Only deleting and recreating it worked.
Should projects in public places not be linked to the home: I
especially liked about this idea that I don't have to 'look for' 'my'
packages across many projects and I would have them all centralized in
my home:
Tell me if this is not working and I change my behaviour.. that's
probably easier than changing the behaviour of BS
Dominique
Hi
Is there already a schedule available for syncing again STABLE and
Factory in BS? freetype2 in Factory(BS) is still 2.2.1. Therefore
X.Org build (patch) is failing. freealut is still missing, therefore
torcs is failing. Probably more issues than these ...
Best regards,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi Guys
Last night we created a new server:php:applications project. It's first
occupant is the RoundCube Webmail multilingual IMAP client
Anyone who has similar applications and wants to migrate them there, please
let me know.
Regards
--
Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc
Hello,
On the web site.
http://en.opensuse.org/Build_Service
Build Service Source Code
SVN Repository
The source and documentation of the Build Service tools gets hosted on
forge.novell.com. This repository contains the sources for the client
tools as well the sources for the servers.
A checkout is possible via
$ svn checkout
https://anonymous@forgesvn1.novell.com/svn/opensuse/trunk/buildservice
No longer is working. I tried to do a svn update and it fails with.
gerberb@blg:~/svn/opensuse/trunk> svn update
svn: PROPFIND request failed on '/svn/opensuse/trunk'
svn: PROPFIND of '/svn/opensuse/trunk': could not connect to server
(https://forgesvn1.novell.com)
--
Boyd Gerber <gerberb(a)zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Ref: home:Riggwelter/gimp-unstable
I've tried to wrap my BuildRequires lines in a %if statement to verify
that the SUSE version is recent enough to contain certain packages (in
this case python-gnome-devel), it looks like this:
%if %suse_version >= 1020
BuildRequires: foo-devel bar-devel
%else
BuildRequires: foo-devel bar
%endif
This statement should use the first version for FACTORY and the second
for 10.1, however it seems to ignore the first ans always use the
second, even on FACTORY.
I'm asking here before filing a bug on bnc just to check that I've got
the syntax and %suse_version right (the latter seems correct according
to /usr/lib/rpm/suse_macros)
--
James Ogley
james(a)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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org