Mailinglist Archive: opensuse-buildservice (253 mails)

< Previous Next >
Re: [opensuse-buildservice] Request for new project
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Thu, 9 Nov 2006 16:01:53 +0100
  • Message-id: <200611091601.53377.adrian@xxxxxxx>
Am Thursday 09 November 2006 14:42 schrieb Gilles Fabio:
> Hello,
>
> I'm using SLED 10 (Novell has recently offered me a one-year
> subscription activation), openSUSE 10.1, openSUSE 10.2 beta and openSUSE
> Factory. I'm a huge fan of SUSE Linux distributions (I write a lof of
> SUSE howtos on my french blog) and I'm used to build my own packages for
> my own needs and friends.
>
> Well, I've made some packages for SLED 10 (F-Spot 0.2.2, banshee 0.11
> plugins, some Python libraries and Jokosher) but as my hosting provider

esp. banshee plugins, I hope there are no plugins affected by some patent ?
like supporting any codec or alike ?

> is really unstable (my hosting provider is my Internet provider, aka
> free.fr, it's a free hosting with often server troubles), it's a pain to
> maintain and share my packages. So, I recently remove my personal
> repository and I was waiting for a better solution. I think Build
> Service would be the best one.
>
> Well, if it's possible, I would be glad to have a Build Service account.
> But if it's not possible (for any reasons), I will find another solution
> to maintain and share my packages.
>
> I post this message on this mailing list because I already sent a
> request on http://build.opensuse.org but I didn't receive any answer, so
> I don't know if it's the correct process to request an account. Excuse
> me if this is not :/

it is ... it will come, I was just a bit lazy in the last weeks. sorry.

bye
adrian


--

Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian@xxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References