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
Hi All,
I am trying to install my program on Mandriva but can't seem to add
the OBS repository.
It seems that the command urpmi.addmedia doesn't work with the
normal RPM PM. Someone on IRC mentioned that I could specify a
different type for the repository in my OBS raw config to
automatically generate a urpmi compatible repo. What do I put as the
type for my Mandriva repo to make it urpmi compatible?
Thanks,
Nick
--
Nick Peterson
Programmer @ Siepel Lab
Cell: (480) 600-2544
--
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
dolphin-emu from home:RedDwarf:NonFree, that uses the new tar_scm
source service, has been in "source update running" for more than an
hour.
Also, at least the tar_scm version I have installed from
openSUSE:Tools seems to have a typo that makes --filename not work.
Where it says
FILE="$FILENAME"
VERSION="$MYVERSION"
it should say
FILE="$MYFILENAME"
VERSION="$MYVERSION"
I would create a SR, but not sure what/where is upstream/devel project
for the source services.
--
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
When building ISO images using kiwi, I have a question:
It seems that I have no problems building ISO images for SUSE base distros
(no surprise there).
However, if I try to build an ISO image using something else (CentOS seems
to be my example...), I get an unresolvable error:
nothing provides kiwi, nothing provides kiwi-packagesmanager:instsource.
So... does the ISO building in OBS require those package compiled for the
target distribution? Or is kiwi independant of the OS the ISO image is
being built for?
--
Troy Telford
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
The openSUSE Build Service - OBS - is now officially at release 2.1. We're
delighted with the improvements in this release, including an enhanced web
interface, integration with online code management systems and better
access controls.
OBS 2.1 Introduces New Features
===========================
Enhanced web user interface
This iteration has enhanced the web user interface of openSUSE Build
Service with features that were previously only in the osc command line
client. It now allows submitting of packages to other projects, showing a
history of changes and who did them, with associated comments. This means
that the full work flow needed to build packages, contribute them to
projects and collaborate on them is available from the web interface.
Integration with online source code management tools
Users of the Build Service may now access a new concept called 'source
services'. Source services allow, for example, the automatic checkout of
source code for a package from a remote server via Git or Subversion,
building a tar ball from these checked out sources, and using them for
building a package. It also enables direct download of tar balls from
remote sites. This allows packagers to work with external sources without
downloading them to their own workstations, and makes it easy to rebuild
packages after upstream changes with a single click.
Better access controls
The access controls have been enhanced so that read/write access to a
project can be granted on an individual basis. This allows for tighter
control of work flows where needed. You can for example ensure people don't
have access to security updates while they are being tested.
Using OBS
=========
To use the Open Source Build Service, you can access the public instance on
build.opensuse.org or install it on your own hardware to have a private
Build Service. For local installations you can install from source, or use
the ready-to-run appliance image, either directly or in a virtual machine.
You can also obtain an installation image to install an openSUSE 11.3
system with the Build Service pre-installed. For details check
http://en.opensuse.org/openSUSE:Build_Service_installations
For more information about the Build Service, check
http://en.opensuse.org/Portal:Build_Service.
Thanks
======
This release of the OBS has received many contributions from other
companies, community members and foundations, making this release a truly
collaborative product. We would like to thank everyone who helped make the
openSUSE Build Service 2.1 possible! Special thanks go to Martin Mohring
and the OBS team at The Linux Foundation, who contributed the extended
access handling.
About the Build Service
==================
The Build Service is an open package and distribution development platform
providing a transparent infrastructure for developers to build packages for
a variety of Linux distributions and hardware architectures.
build.opensuse.org is a freely available service and can build packages for
the most popular distributions besides openSUSE including SUSE Linux
Enterprise, Debian, Fedora, Mandriva, Red Hat Enterprise Linux and Ubuntu.
The Build Service aims to significantly reduce the costs and risks related
to the distribution of applications, from building, providing and
maintaining them. It does so by providing a convenient web and command-line
interface, which developers can use to upload their code and build
instructions. The Build Service will then create a clean, virtualized
operating system, install any required build dependencies and create the
package. This process will be repeated for each supported operating system.
Once the build is finished, all packages will be made available in a set of
repositories for easy distribution.
The Build Service at build.opensuse.org currently builds about 100,000
packages from 25,000 users working on 15,000 different projects.
Communities and companies using their own Build Service installation
include the MeeGo Project, VLC team, Dell, Cray and many others.
For more information about the Build Service, check
http://en.opensuse.org/Portal:Build_Service.
--
Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Just a shot question:
Are there any plans to add Ubuntu 10.10 to the list of available
repositories?
Thanks in advance
-Fritz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFMuQ83boM4mAMyprARAu2fAJ9/bfyJ237nm5kkcvokxwvEmNvpXwCeOYGl
6GTQd2EOxM5QTfx+P821JfM=
=jHOs
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org