-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
HI I'm "ANUBISG1"..i'm having problems building 64bit packages.. they
are enabled but nothing happened..
thanks
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHCUWn9l8CpdtqVRsRAuSLAKDc4NMFOf1Hz78Lvb8i5aPF+f3rYwCgtZkk
qyxMDpAvIbG2szLYQ+i5v1g=
=D7T4
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I broke the validation for pattern files a while. If you noticed that an
uploaded pattern did not result in a .ymp file, you are affected, because the
backend
You have an invalid pattern file in that case, api.o.o should have never
accepted this file and does report now an error, if you try to upload it
again.
You can try to resubmit your current pattern to get the xmllint error output
for fixing your file.
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
Hi!
Please take a look at home:dl9pf, packages ifolder3-server-svn and simias-svn.
No log for x86_64 and no updated binaries ....
Any idea ? Whats in the backend logs ?
Greets & Thanks
Jan-Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
when trying to add repository, *all* repositories are offered - i.e.
including those which I have already added. Selecting such repository
yields an error:
-------------------------------------
OpenSUSE Frontend Error:
Error Details:
Errorcode: uncaught_exception
Message: Mysql::Error: Duplicate entry '912-openSUSE_10.3' for key 2:
INSERT INTO repositories (`name`, `db_project_id`)
VALUES('openSUSE_10.3', 912)
Exception from API:
ActiveRecord::StatementInvalid: Mysql::Error: Duplicate entry
'912-openSUSE_10.3' for key 2: INSERT INTO repositories (`name`,
`db_project_id`) VALUES('openSUSE_10.3', 912)
Stack Trace:
-------------------------------------
<stack trace available, yet it should be easily reproducible>
Either the system should check already selected repositories and not
offer them for adding or redesign of the according storage structures
("SET" columns come to mind) is in place to prevent such things from
happening.
Best regards
Petr
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
* New backend server seems to run stable, setup will start on thursday.
We have no date yet for moving the service to the new system yet.
* Project deletion in the backend is implemented and running
* api does support project deletion as well, but needs to get deployed
to support it.
* mod_zrkadlo (the code behind download.o.o redirector)
can redirect now to a certain mirror, if the client
comes from a concrete IP. Also wildcard support has been
added to use a certain mirror for a concrete country
* Release Handling Requirements
We spoke about how to provide the OBS code in future to allow all kind
of users to run stable instances of an own build service. We figured out
the following so far:
- We need stable packages
- Move extra files from packages to svn (AI: adrian)
- multiple tar balls and spec files for each part
* api
* web clients
* backend
* worker
* signing daemon package only for distros with patched gpg
* signing client package ?
- A release must be possible at any time
- A release must be done on each milestone from the roadmap
- We guarantee forward compatibility, either by supporting
old data or converting data automatically
- We make binary packages only from svn tags.
- Releases should be pre-announced to allow developers to bring their
code into shape.
We will follow up on this when Klaas is back on thursday.
--
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 was under the impression that the build service was not to be used for
patent encumbered software... is this not the case?
I'm seeing:
ffmpeg (project home:enzokiel)
mythtv (project home:zCougar)
What are the policies about this?
(If this software is allowed... maybe the packman packages should also
be added?)
Wade
Good day!
Some of my packages needs RPMs from other projects...
How can I include these additional RPMs for my package builds?
I've published a package but everything I got from the repo is an 404
error. Is there any problem yet?
--
[ ]'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
I have a quick question about the debuginfo packages the buildservice
automatically creates. Is it possible to tune the cflags and buildflags
used for that debug package? I've got some compile-time flags I need to
pass to the configure script for more verbosity, but I don't want them
enabled unless the user installs the debug package too.
I didn't see anything about debug settings in the documentation I have,
which is why I ask.
Thanks in advance,
~~ Andrew D.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
when I press the button to prevent publishing in a package I get the
message:
ERROR publish can only be enabled/disabled in the project
When the idea of the whole is, that certain packages required for building
are not published, then this message is very strange. It would mean I can
only decide it for a whole project and not for the individual packages.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm building SUSE, Fedora and Mandriva packages for Zero Install
(http://0install.net) in my home project at the moment:
http://build.opensuse.org/package/show?package=zeroinstall-
injector&project=home%3Atalex5
Should I move this somewhere else now that it is working? It could be a
top-level project, or it could go in a new 'installation:' group or
something.
Also, a second question (I'm fairly new to the BS): I found that the
built packages often didn't install because I got the dependencies wrong.
Getting feedback from users about this took a long time, so I created a
'test' package which does nothing except depend on the real package (to
make sure that the real package installs and --version works):
http://build.opensuse.org/package/show?package=zeroinstall-injector-
test&project=home%3Atalex5
Is this the right approach? Is there an easier way? If automatic testing
is encouraged, there is a whole unit-test suite in the Zero Install
tarball that could be run, but I don't want to use too many resources on
the build service.
Thanks,
--
Dr Thomas Leonard http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org