Hello,
is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos
building against it in OBS.
openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a
while ago.
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
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
What is the difference between Support and Keep?
Like, let's say I have a package FOO that I'd like to always be
installed in the build environment, *if* it is available. If it is not
available, block all other builds until it *is* available, but do not
block FOO itself. How do I do that?
Is there a way to configure a project with more than one repository
with different configurations (such as, when using repo A, substitute
foo for bar)?
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I was trying out multiple actions in one request and noticed that the
notifications contain only the last action.
I looked at the code and found this in /usr/lib/obs/server/BSNotify.pm
line 82 :
# FIXME: how to handle multiple actions in one request here ?
# right now the last one just wins ....
So here's a proposed fix : add an actions key in the reqinfo hash, that
contains an ordered list of hashes that contain the details of the actions.
The Data::Dumper of reqinfo produced by the attached patch looks like this :
$VAR1 = {
'when' => '2010-09-30T00:12:13',
'actions' => [
{
'sourcerevision' => '1',
'sourceproject' => 'Foo:Devel:Personal',
'deletepackage' => undef,
'targetproject' => 'Foo:Trunk',
'sourcepackage' => 'libfoo',
'type' => 'submit',
'targetpackage' => 'libfoo',
'deleteproject' => undef
},
{
'sourcerevision' => '1',
'sourceproject' => 'Foo:Devel:Personal',
'deletepackage' => undef,
'targetproject' => 'Foo:Trunk',
'sourcepackage' => 'bar',
'type' => 'submit',
'targetpackage' => 'bar',
'deleteproject' => undef
}
],
'author' => 'bob',
'description' => 'Test',
'state' => 'new',
'comment' => undef,
'who' => 'bob',
'sender' => 'bob',
'id' => 32,
'type' => ''
};
Is this change acceptable ? If so, I guess the notification plugins will
have to be changed to accommodate this.
Thanks,
Islam Amer
Hi,
Here is a tiny patch that define a macro when packages are built inside OBS so that special packages built locally can be treated differently.
Anas
diff --git a/src/backend/bs_worker b/src/backend/bs_worker
index 948dd0b..2bbc838 100755
--- a/src/backend/bs_worker
+++ b/src/backend/bs_worker
@@ -1431,6 +1431,7 @@ sub dobuild {
push @args, '--oldpackages', $oldpkgdir if $oldpkgdir && -d $oldpkgdir;
push @args, '--norootforbuild' unless $BSConfig::norootexceptions && grep {"$projid/$packid" =~ /^$_$/} keys %$BSConfig::norootexceptions;
push @args, '--baselibs-internal';
+ push @args, '--define', "running_in_obs 1";
push @args, '--lint';
push @args, '--dist', "$buildroot/.build.config";
push @args, '--rpmlist', "$buildroot/.build.rpmlist";--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi, all!
I'm trying to configure an own RPM repository to use download on
demand, but I don't know how to do it, because into the OBS wiki[1]
there is only an example to use debian repository.
My repository is a classic repomd, like the Fedora repository.
Can anyone help me?
Regards.
[1] http://en.opensuse.org/openSUSE:Build_Service_Concept_CrossDevelopment
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm trying to create a source service to make my life easier (don't
think it would benefit anyone else), but I'm unsure of how to go about
that.
I know it's a bash script...
Are there any special variables or anything that I should be aware of?
--
later, Robert Xu
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi alltogether!
On http://en.opensuse.org/openSUSE:Build_Service_Concept_Smart_Dispatcher_Work… I started to take notes on
what goals/requirements/ideas to implement for such a feature.
Currently 2 main areas are covered:
* cross worker setup enhancements
* flexible worker assignment / flexible worker (re)setup
What other use-cases are there ?
Feel free to add your ideas and comments!
Best,
Jan-Simon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden.
no permission to execute command 'branch' for not existing package
Since we use linked projects as a Testing facility where developers can submit changes for staging, this will not work since otherwise we would need to make everyone admin of that project...
Any ideas how to fix this?
Anas--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org