Mailinglist Archive: opensuse-factory (508 mails)
| < Previous | Next > |
Re: [opensuse-factory] Tumbleweed request for packages
- From: Stefan Seyfried <stefan.seyfried@xxxxxxxxxxxxxx>
- Date: Tue, 14 Dec 2010 09:13:32 +0100
- Message-id: <20101214091332.25d8bbec@susi>
On Mon, 13 Dec 2010 15:34:39 -0800
Greg KH <gregkh@xxxxxxx> wrote:
FACTORY or Base:System (I test them in home:seife:testing, if it "works"
in the way of "does not instantly segfault", I'll push them to Base:System
and, depending on what changed etc. a bit later to FACTORY). If it's in
FACTORY for a week or longer, it's probably good for Tumbleweed.
But the easiest would be to wait for my submitrequest instead of linking
to any repo.
I did the sr 55896 for bluez-4.81, you'll need to linkpac bluez to
bluez-gstreamer in oS:Tumbleweed (with no revision etc, they should always
be the same). The package is split to avoid circular dependencies.
I'm actually not sure if anyone still uses bluez-gstreamer, but as long as
it builds without me holding its hand, I had no real reason to
investigate... ;-)
Have fun,
seife
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Greg KH <gregkh@xxxxxxx> wrote:
On Thu, Dec 09, 2010 at 07:56:27PM +0100, Stefan Seyfried wrote:
On Thu, 9 Dec 2010 10:01:58 -0800
Greg KH <gregkh@xxxxxxx> wrote:
But, what I need from you all, is a request for what packages do you
feel I should be updating right now, and hopefully you can provide a
pointer to the repo for where these packages are (if they are only in
FACTORY, that's fine as well.)
Something that's usually worth updating is BlueZ, as the upstream code
quality is usually very high with very little regressions, but one or the
other nice fix and new feature coming along all the time.
What repo and packages should I rely on stable packages for BlueZ to be
based on?
FACTORY or Base:System (I test them in home:seife:testing, if it "works"
in the way of "does not instantly segfault", I'll push them to Base:System
and, depending on what changed etc. a bit later to FACTORY). If it's in
FACTORY for a week or longer, it's probably good for Tumbleweed.
But the easiest would be to wait for my submitrequest instead of linking
to any repo.
I would volunteer to maintain this for tumbleweed also, which probably
would consist of doing a submitrequest maybe a week after it was pushed to
FACTORY without reports.
Wonderful, I'll gladly accept submitreqs from Factory for packages like
this, feel free to send them my way.
I did the sr 55896 for bluez-4.81, you'll need to linkpac bluez to
bluez-gstreamer in oS:Tumbleweed (with no revision etc, they should always
be the same). The package is split to avoid circular dependencies.
I'm actually not sure if anyone still uses bluez-gstreamer, but as long as
it builds without me holding its hand, I had no real reason to
investigate... ;-)
Have fun,
seife
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |