We want to create a telephony:Druid build directory for the Druid PBX
environment we develop and maintain together with voiceroute.
www.voiceroute.org
We also want to make it available on SLES and OSS ;)
With Regards, Mike Veltman
Gwayne in the buildenvironment.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
openSUSE will be present on the LinuxTag in Berlin 28-31st this month.
This gives us also the chance, beside the usual talks, to do any kind of
workshops or Bof's around the build service.
http://en.opensuse.org/LinuxTag_2008
Are people on this list, who will be at LinuxTag and have interest on special
topics to be shown/discuss/worked on there ?
Just some examples:
* Hacking on
- Web frontend
- osc command line tool
- server backend
- anything else
* Cross Distribution packaging workshop
* Image building with kiwi/OBS
We can also create workshop on other topics, if there is a common interest.
Or does anyone else want to held a workshop and needs just a room ? ;)
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,
when building using spec files or when using dsc files, is there a possibility
to have the 'Build Repository' name added to the resulting .rpm or .deb
filename?
For example: Rather than
glade-2.12.1-143.7.i586.rpm
it should be named:
glade-2.12.1-143.7.SUSE_Linux_10.1.i586.rpm
(or similar)
The reason I am asking is: When I build against various repositories and then
download the built files for example to my home dir they have all the same
name.
Of course I could change/add the reposi name when downloading but that is
annoying with more than a few packages.
Help is much appreciated.
many thanks
regards
Chris
--
http://www.acurana.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi
I'm getting expansion errors, I cannot explain. Once I understand them
I would like to fix the issue.
Project: CrossToochain:avr
Package: avr-libc/avr-gdb
Repository: openSUSE_Factory/i586
"Nothing provides cross-avr-gcc"
But you can see that cross-avr-gcc has been built successfully in the
same project!?! See also
https://build.opensuse.org/project/monitor?project=CrossToolchain%3Aavr
Any help would be appreciated.
Thanks,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
-----------------------------------------------------------------
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
My first blog entry :)
It is showing how easy it is to run a local web interface of the OBS for
developing, without the need to run an own instance of the build service
(after fixing just some minor things ;).
The five simple steps to an own web frontend are documented here:
http://lizards.opensuse.org/author/adriansuse/
Maybe someone can post something how easy it is to add/modify some small
things in the web interface using the usual Ruby on Rails stuff ? :)
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
>>> Stefan Dirsch <sndirsch(a)suse.de> 05/06/08 6:21 PM >>>
On Tue, May 06, 2008 at 05:04:31PM +0200, Dominique Leuenberger wrote:
> >>> On 06.05.2008 at 18:03, Stefan Dirsch <sndirsch(a)suse.de> wrote:
> > On Tue, May 06, 2008 at 04:47:14PM +0200, Dominique Leuenberger wrote:
> >> >>> On 06.05.2008 at 17:47, Stefan Dirsch <sndirsch(a)suse.de> wrote:
> >> > Hi
> >> >
> >> > I'm getting expansion errors, I cannot explain. Once I understand them
> >> > I would like to fix the issue.
> >> >
> >> > Project: CrossToochain:avr
> >> > Package: avr-libc/avr-gdb
> >> > Repository: openSUSE_Factory/i586
> >> >
> >> > "Nothing provides cross-avr-gcc"
> >> >
> >> > But you can see that cross-avr-gcc has been built successfully in the
> >> > same project!?! See also
> >> >
> >> > https://build.opensuse.org/project/monitor?project=CrossToolchain%3Aavr
> >> >
> >>
> >> Actually, the package that was built is called cross-avr-gcc43.
> >
> > Indeed. But why? The resulted package should be called cross-avr-gcc.
> >
>
> Actually from the spec file inside openSUSE:Factory (cross-avr-gcc43.spec):
> Name: cross-avr-gcc43
>
> in openSUSE:Factory, this makes part of the package gcc43
>
>So how can I force the package to be named cross-avr-gcc instead of
>cross-avr-gcc43? I think this would fix the issue finally.
Stefan,
I see several solutions that would work, you might want to pick the one that fits most for you:
a) you patch the original spec file comming using the link (tends to break on whatever update might be put in Factory... I normally try to avoid them). The patch can have multiple ways to be achieved; you either change the name tag back to the old one or you add a Provides: cross-avr-gcc
b) you change your spec files to no longer BuildRequires: cross-avr-gcc, but change them to BuildRequires: cross-avr-gcc43 (depending on how many specs, might be the cleanest solution)
c) you change your project config (osc meta -e prjconf CrossToochain:avr) and you add a Substitute: cross-avr-gcc cross-avr-gcc43. This substitute is immediate valid for all projects based on top of yours (inherited).
There might be other solutions as well, but that's the ones coming on my mind at this moment.
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi experts,
Is there a easy to use GUI or Front End to help a newbie as me to
manage graphicaly a spec file, or perhap's a tool with autocompletion
?
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I just attached a small patch for the frontend/scripts/import script
which automatically selects the appropriate source server. So we can
get rid of the hardcoded default values.
Marcus
present: mls, jcborn, mjung, rlihm, adrian, freitag, tpatzig, froh
* general Status
* Trust System
* Hermes
* 1.0 release
General Status:
===============
freitag:
* Open discussion about how to request changes in meta data of packages
and projects.
AI: clarify sync with internal tools.
tpatzig:
* working on openSUSE layout for Hermes with Robert.
mls:
* general debugging
jcborn:
* kiwi can create installation sources now via kiwi-inst-source package
-> meta data creation works, but needs some more work for the
content file generation, md5sum and signing support.
rlihm:
* busy with openSUSE Forum design.
adrian:
* general debugging, esp. in XEN build area
Trust System:
=============
Marco Jung joined the team for his diploma thesis working on a trust
system for openSUSE and esp. the build service. He is currently collecting
input on what is requested for the system. Welcome Marco :)
Hermes:
=======
Klaas works on getting mail and jabber notification running now.
Hermes test setup will happen next week.
Klaas thinks about to connect the web interface more deeply with users.o.o
interface.
1.0 Release Status:
===================
Andreas will implement branch request api call this week.
Michael will implement debuginfo handling this week.
Klaas and Adrian will take care about filling external Devel Project values
from current internal definitions.
--
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 wanted to get some more input from all the smart people here around; I have a bugzilla entry #378933 (https://bugzilla.novell.com/show_bug.cgi?id=378933) which seems not to get any attention.
So far all of us that are providing KMPs for whatever hardware have a tough luck, as none is working.
I did not find yet weather it's a OBS problem (maybe some missing macros in the Factory config) or if the corresponding macros should come from the kernel.
What I can tell is that the loop "for flavor in %flavors_to_build", which is normally used, does not pass a single time. %flavors_to_build is empty.
Often you see the package in state success, but the kmps simply do not exist (no error, as the build just did not pass a single time).
Thanks for having a look into it and maybe also communicating if you see similar errors... who knows, maybe it's just me.
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org