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
Hello all of you, virtualization addicts!
[reference]
OpenVZ is container-based virtualization for Linux
-> http://wiki.openvz.org/Main_Page
[/reference]
It's been quite a while since any OpenVZ kernel package shows up on the
Build Service. SLES10 2.6.16 kernel is still maintain by the OpenVZ team
but openSUSE users had it hard getting newer OpenVZ kernel running
without giving up on Suse kernel configuration and patches.
So here comes the new 'Virtualization:OpenVZ' project hosted on BS.
It aims at providing recent openvz kernel builds while being as close as
possible to the original Suse kernel ABIs and default configurations.
Some trade-offs had to be made though. Most notably, Apparmor patches
could not accommodate with OpenVZ ones. I suspect this would take a
significant amount of work and testing to get them both.
Two OpenVZ kernels has been packaged:
- 2.6.24 -> Virtualization:OpenVZ:STABLE sub-project,
available repositories : SLE_10, openSUSE_10.3 and openSUSE_11.0.
- 2.6.26 git -> Virtualization:OpenVZ:HEAD sub-project,
available repositories : openSUSE_11.0 and openSUSE_Factory.
Appropriate administration tools are included in each repository.
Packages are:
kernel-ovz-default, kernel-ovz-pae, kernel-ovz-debug
vzctl, vzquota,
linux-kernel-headers, kernel-ovz-source.
OpenVZ requires templates to create containers. You can find some of
them at http://wiki.openvz.org/Download/template/precreated or create
one yourself (search openvz wiki). I will soon add an openSuse 11.0
template in the 'Virtualization:OpenVZ' repository.
Also you need IPv6 enabled (use Yast) to load required openvz kernel
modules.
Last but not least, please consider those packages at beta stage.
Comments/bug reports are greatly appreciated.
Especially I would be grateful to any experienced kernel packager who
would have a look at Virtualization:OpenVZ:HEAD/kernel-source and the
set of diff applied to Kernel:HEAD/kernel-source and tell me if I did
commit any 'spec file blasphemy'.
Project homepages:
http://build.opensuse.org/project/show?project=Virtualization:OpenVZhttp://build.opensuse.org/project/show?project=Virtualization:OpenVZ:STABLEhttp://build.opensuse.org/project/show?project=Virtualization:OpenVZ:HEAD
have a lot of fun!
-Jb. G
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
as you probably noticed, the buildservice web interface now has a wizard
that helps with writing spec files. Yesterday, I improved it to generate
better spec files for perl and python modules (not yet on build.o.o) and
I hot already advice on how to add support for apache modules and ruby
gems ;-). Of course I'd like the wizard to be able to package as many
kinds of packages as possible, but I see some problems I'd like to solve
somehow before adding more features:
Problem #1 (more theoretical than practical): the main part of the
wizard is implemented in the frontend (aka API), the webclient only
translates xml to html forms and vice versa. The reason for this is that
I'd like to add a wizard interface also to osc one day. The problem is
that so far, the frontend has been just a simple proxy to the backend,
with access control, without any fancy functionality. Now the wizard
adds potentially buggy code that doesn't necessarily need to be there
(it would be easily implemented as a standalone application talking to
the frontend). The only reason for having the wizard on the frontend is
to be able to use it from different clients easily.
Problem #2 (practical): To implement good heuristics, the wizard at
least needs to look into the source tarball (if not run some
commands...). Here comes the problem: 'tar tf foo-1.1.tar.bz2' can take
a *lot* of cpu time, so where to perform such expensive actions?
a) on the frontend - can be abused for DoS easily
b) let the client send the filelist along with the tarball - makes the
client implementation too complicated, plus moves the DoS problem
from the frontend to the webclient
c) on the backend, dispatching the jobs to workers - would also allow
for more dangerous analysis of the package, but would impose
additional delays
d) create a separate wizard service and do all the job there - would
also solve problem #1, but would make the client implementation a bit
more difficult (need to talk to two different servers)
e) [insert great idea here]?
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
in order to fit better into the current buildservice structure the
OpenLDAP project has been moved into the newly created "network:ldap"
namespace. Additionally I took the chance to reorganize the packaging a
bit. There are different subprojects for the different release branches
of OpenLDAP.org. For Packages from the 2.4 release branch that makes:
http://download.opensuse.org/repositories/network:/ldap:/OpenLDAP:/RE24/
and packages from the 2.3 release branch can be found here:
http://download.opensuse.org/repositories/network:/ldap:/OpenLDAP:/RE23/
If you were using the repositories from
http://download.opensuse.org/repositories/OpenLDAP/
please update you configuration to one of the above as I plan to remove
the old project in a few weeks. (Rebuilds have already been disabled
for the old project).
Additionally I have plans to add other LDAP related packages (nss_ldap,
pam_ldap) to the "network:ldap" namespace as time permits.
Contributions and other feedback are of course very welcome.
Have a lot of fun...
Ralf
--
Ralf Haferkamp
OpenLDAP Engineering Team
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
While working with OBS, I've noticed that all the meta data configuring
the projects and packages is stored only on the server, and is treated
with special commands.
This has the disadvantages of making it harder for users to backup their
projects locally. It is a key piece of information that does not follow
the source code and spec files.
It would be really useful if this information were at least cached in
the .osc subdirectories somewhere, in my opinion.
Just thought I'd mention it.
- Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi list,
I have some prepared packages (i.e. specfile & tarball) that build OK locally.
Now I'd like to add them to an OBS project. When I use
osc meta pkg -e project-name package-name,
I'm asked to fill in the package title and description. Couldn't this step be
avoided as the description and title are already available in the package
specfile? Or am I simply supposed to copy & paste it? (BTW what takes
precedence - specfile metadata of 'obs metadata') ?
TIA
--
Best regards / s pozdravem
Petr Uzel
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: petr.uzel(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 964
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi All !
There are lots of packages in the build-service, but I still consider
those as "third-party", because they aren't part of openSUSE Factory
tree,
therefore they won't become part of openSUSE 11.1 release.
I would like to take the job of integrating *stable* packages from the
community's Build Service home projects,
and taking them to Factory.
Unstable packages will remain as-is (third-party).
I will begin with my own package: "banner" :)
Now: May I get commit access ?
--
-Alexey Eromenko "Technologov"
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
When accepting requests, the log entry always shows <no message>. Where
do the messages supplied with the accept command using -m <message> go?
Is there a way to get log message into target package when accepting?
Anas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Who is responsible for the Asterisk and Zaptel packges in the
network:telephony repo?
Or if that is not how it works how can someone correct errors with
these packages?
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
before using a local obs I was building packages with "build".
There I was able to use inside specfile:
Release: 1.CS
Is there a possibility to use this with obs ?
Thanks
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org