Hello,
whether I add "Packager" in a spec file or not, rpmlint complains in both
cases. One time because of hardcoding. The other time because it is
missing.
Could this please be fixed?
What I would like to see is that the buildservice-email-address also used
in the GPG key of the repository is automatically copied into the spec
(like e.g. changelog or revision).
Is this possible (thought that would not fix the hardcoding error
message) or can the name+email be added in the build command directly?
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 trying to submit obs-server to factory, which doesn't exist there
yet.
This is what I get:
$ osc submitreq create openSUSE:Tools obs-server openSUSE:Factory --message="the latest obs for the sdk, fate #303298"
Server returned an error: HTTP Error 404: Not Found
Error getting meta for project 'openSUSE:Factory' package 'obs-server'
Unknown package 'obs-server'
So how can I achieve what I mean?
S.
--
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
OPS Engineering Maxfeldstraße 5
Processes and Infrastructure Nürnberg
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm happy to announce that the build service has a new mirror, which is
located in Russia.
http://dinarv.blogspot.com/2008/09/good-news-for-russian-opensuse-users.html
Russian users had the problem that they were redirected to Taiwan
before, where the only Asian build service mirror is located. But
network access to Taiwan was very slow.
We can thank Dinar Valeev, who arranged that Yandex (Russian network
operator) mirrors the tree, and who worked out with me all problems that
were to solve.
Peter
--
Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com)
#opensuse-mirrors on freenode.net
Info: http://en.opensuse.org/Mirror_Infrastructure
SUSE LINUX Products GmbH
Research & Development
Hi,
I'm trying to build ZABBIX packages for SLES9,
can somebody give me a hint? I see this in the buildlog:
I have the following modifications for zabbix.spec:
11c11
< Release: 1.1
---
> Release: 10.1
20c20
< BuildRequires: fdupes tcpd-devel postgresql-devel sqlite-devel
libmysqlclient-devel
---
> BuildRequires: fdupes tcpd-devel postgresql-devel sqlite-devel
61d60
< BuildRequires: libmysqlclient-devel
This is the relevant part of the spec file:
...
BuildRequires: fdupes tcpd-devel postgresql-devel sqlite-devel libmysqlclient-
devel
%if 0%{?sles_version} == 9
BuildRequires: net-snmp-5.3-snapshot-devel openssl-devel libcurl-devel
%endif
%if 0%{?sles_version} == 10
BuildRequires: curl-devel net-snmp-devel
%endif
...
I added the server:database/SLES_9 repository, so that libmysqlclient-devel
should be found. Like this it works for net-snmp-5.3-snapshot-devel package.
https://build.opensuse.org/package/show?package=ZABBIX&project=home%3Asteph…
--
Stephan Dühr stephan.duehr(a)dass-it.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi Adrian,
thanks for your quick answer.
> XEN is important to seperate builds better from each other
I can life without the XEN environment.
In /etc/init.d/obsworker there is some XEN stuff, but I' ll leave it untouched.
As I got some minor problems during the setup of OBS, I want to document it somewhere.
With information like where to find log files etc.
Thanks,
Ulf
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I installed my own local OBS. My packages are build without XEN.
But the packages from opensuse.org are built in a XEN environment.
In which case I' ve to use XEN and howto use XEN?
Where is the documentation, is it all in the Wiki http://en.opensuse.org/Category:Build_Service
Kind regards,
Ulf
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
present: lrupp, mjung, abauer, freitag, mls, tpatzig, adrian, froh
Topics:
* General Status
* openSUSE distro build status
General Status:
===============
lrupp:
* AI: finish product definition schema documentation
mjung:
* Tried second algorithm for user rating (but works worse than first)
* Will meet with mls discussing about architecture
* Worked much on users to learn RoR, some of the work can
be reused for trust rating
abauer:
* Worked on bugs, unfortunatly not many fixes yet.
freitag:
* Designed filter subscription abstraction layer for hermes, not sure
if this is really the solution, but tschmidt will do a first implementation.
* Found and fixed a bug which corrupts filter parameter in hermes database.
* Implemented better readable filter names in hermes.
mls:
* Working on image and inst-source automatization. Should work now, if
Factory ever finishes building.
Missing: automatic upload of trees and images.
froh:
* Worked on driver kit kmps.
Submitting new package to Factory did not work with osc.
AI: please test with new osc.
tpatzig:
* Worked on hermes and build service api
-> New "my watchlist" filter exists in hermes now.
Brief discussions if this might a privacy issue.
* Add new "rlog" command to osc.
-> show commit log for not checked out packages.
adrian:
* Building openSUSE pre beta images, fixing lots of bugs in all areas.
openSUSE distro build status
============================
* openSUSE distro build has currently problems
- The drop of eclipse package due to addition of closed source part,
this broke the complete java stack.
This has been fixed, but we need to wait for around 300 big packages.
So, we will have a first clean tree this evening as earliest time.
- wlan kmps currently broken, blocks installation-images creation.
- We need to implement new code part to sign more files on the media
due to changed handling in YaST.
- Some new expansion errors needs to be fixed around the dummy-release
package.
--
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,
during Linux Tag there was some discussion to get Coverity support for
the projects in the oBS. Did that go anywhere?
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
With svn 5191 i see this error on the worker side:
got job, run build...
Use of uninitialized value $projid in concatenation (.) or string at
./bs_worker line 648.
Use of uninitialized value $repoid in concatenation (.) or string at
./bs_worker line 648.
Building 'obs-imaging' for project '' repository '' arch 'i586'
fetching sources...Use of uninitialized value $projid in concatenation (.) or
string at ./bs_worker line 448.
remote error: 404 projid is empty
build failed, send back logfile...
Use of uninitialized value in concatenation (.) or string at ./bs_worker line
1110.
rpc failed: bad uri: /putjob?job=imaging::image::obs-
imaging-7333eb8af291e08e7d0fc243bce3d723&arch=i586&jobid=4f63cf6ba69ff4ad2a75f20d4aa47730&code=failed
Best regards
Jan-Simon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
The "how to verify and fix broken links?" thread brought up a question
I've always wondered about....
Why does osc not-exactly-duplicate the functionality of svn, instead
of just letting the user use svn directly?
In other words:
- Use svn for all checkout, diff, commit, merge, etc. operations
- Use osc for everything else osc does
??
Thanks,
-Archie
--
Archie L. Cobbs
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org