Re: [packman] New packages for packman

[Pascal Bleser]

2017-07-31 15:31 GMT+02:00 Walter Fey :
> Dear Packman Team

Hi Walter

> Thank you for the access to PMBS.
>
> I added some hamradio related packages which are not available in the
> official openSUSE distributions to my home project/subproject
> "home:dl8fcl:hamradio". One package "gpredict" is available in Leap 42.3 as
> an old version. It is a fork of the package I was maintaining for a long
> time. All these and more packages were maintained and updated by me at the
> openSUSE Build Service, project hamradio.

Do you mean to say that all the spec files and patches have been
written by you, only you, and do not include content from other spec
files that are under a different copyright ?

> Meanwhile I do not update this openSUSE project any longer and like to
> submit these packages to a project in PMBS from were they could be
> published.

You didn't exactly disclose much about why you want to move those to
Packman, that only came out later.
That's a bit of a stinky move, Walter, to remain polite.

> There is already one hamradio package "xdemorse" in "Extra". Meanwhile I
> submitted an update for "xdemorse" which was accepted and published.
>
> So "Extra" could be also a good place for these new packages.

Or not, Extra was and still is more of a legacy thing, that stemmed
from a time where Packman had way more packages, when there wasn't an
openSUSE Build Service where non-SUSE-employees could contribute to
the packages.

When Detlef and I reorganized the whole thing by setting up an OBS
instance for Packman and took the time to think of a structure, triage
and move the packages we had in our own package build system to the
Packman OBS, we shoved things that were in Packman but not available
elsewhere into "Extra".

In the mean time, a lot of those packages have been made available on
the openSUSE OBS independently, and there is no reason for us to host
those at Packman anymore.
Furthermore, a lot of packages have been moved from Packman into the
openSUSE OBS, too, including a lot of multimedia stuff.

The goal of Packman is clearly not to have an ever growing "Extra"
repository, *especially* if there is no reason to not host it on the
openSUSE Build Service instance (because more people can contribute
there, and because it has more resources).
The goal has rather been to move everything that can to the openSUSE
Build Service, not the opposite.

> For two of my packages it would be helpful to contact somebody of the team
> directly and discuss some items before submitting them.

Big -1 from me, if my opinion and experience still holds any value.

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] New packages for packman (Walter Fey)

[Pascal Bleser]

2017-08-02 10:08 GMT+02:00  :
[...]
> As Richard explained, this might be a bit dangerous adventure for
> packman.

I think we got the threatening message at this point.

> Apart from that I would say that motivation for moving to
> packman is a bit weak

+1

> my understanding is that move is motivated by hurt feelings after
> discussion about copyright attribution with OP, and
> by his opposition against including hamradio/sdr stuff in Factory and
> Leap.

Yes, clearly, there is no other reason to have those packages at
Packman rather than OBS.

> This would basically go against most of recent efforts to move
> everything that is possible/allowed to OBS/Leap/Factory and would put

+1

> additional load on packman's resources, which are much more scarce than
> those of OBS.

+1

Couldn't agree more.

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] New packages for packman (Walter Fey)

[Pascal Bleser]

2017-08-01 18:02 GMT+02:00 Richard Brown :
> On Tue 1. Aug 2017 at 15:33, Luigi Baldoni  wrote:
[...]
>> If so I suspect it's related to the missing header with copyright
>> attribution to SUSE AG.
>>
>> Now, the question is: would Packman be ok with that?
>
> I would hope the answer is "no"

It seems to me that the conflict here comes from a different
interpretation of how things happened.
I might be wrong but from what I've read, I'm under the impression that
- Walter says that he has maintained those spec files since years and,
hence, he is the copyright holder on the spec files, and in that case,
there would be no problem building and hosting them at Packman (*)
- Richard says that he took bits of spec files that were not his
copyright and/or had the copyright attribution to SUSE, and removed
those in the process
Maybe Walter means that he solely wants to base his packages in
Packman on his very own spec files.

(*) that being said...
I'm in no position to influence anything as I've pretty much retired
from everything, but as probably everyone knows, I have maintained a
lot of packages at Packman in the past, for quite a while.
Based on that experience, my personal opinion is that hamradio
packages have absolutely nothing to do on Packman.
MPlayer yes, hamradio? no. That is really not the purpose of Packman.
It's not a dissidence from the openSUSE project (even though it was a
bit of that in the olden days, before the openSUSE project started
:)), it's a complementary (and important) service to its community.

Is there maybe a way to resolve what seems to be a misunderstanding
(or misrepresentation of events), and keep those packages on the
openSUSE OBS ? (even though the tone of discourse makes it seem as if
it's already too late for that..)

> If Packman receives packages which clearly remove the legal copyright
> attribution of previous authors, Packman would need to be prepared for
> serious conversations with the copyright holder who's attributions are
> being removed.
> This is a very serious situation which fundamentally undermines the legal
> basis under which free and open source licenses operate, so is taken very
> seriously by corporations that run their business in compliance with those
> licenses.

Richard, seriously, those gratuitous threats...
Nothing happened, why are you throwing those around ? (including the
bit in a latter post you made..)

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Handbrake - Latest version?

[Pascal Bleser]

2017-02-13 14:28 GMT+01:00 Jörg Lorenzen :
[...]
> I think the patched libbluray can be deleted from PMBS because Handbrake now
> builds his own static libbluray,
> I don't know if there is any other package that requires a patched version.

Indeed, it's disabled

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Handbrake - Latest version?

[Pascal Bleser]

2017-02-12 13:39 GMT+01:00 Olaf Hering :
[...]
> Do  you  hard it still on the radar?

I just submitted a build where handbrake builds libbluray on its own, as static.
I'll send a cr to revert the patch on the package on multimedia:libs
(and packman, it's _link'ed there) to avoid spreading that
incompatibility to the stock libbluray package, as handbrake seems to
be the only piece of software that needs it.

As libbluray barely ever gets new releases, I think that's the better
approach, in hindsight.

cheers,
Pascal

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] dependencies of packman subpackages from same build

[Pascal Bleser]

It is indeed annoying because you end up with a setup that doesn't
play closed formats properly as it should be, with ffmpeg/libav
packages from different repositories. It also affects mplayer.

Until zypper implements that behavior (which sounds like a very good
idea to me), which won't be available until the next Leap to most
users anyhow, the best approach is probably to do hard requires with
version+release.

What we used to do in the past is to add a "pm" suffix in the release tag, e.g.
ffmpeg-1.2.3-23.pm

Might not be a bad idea to revive that for a few critical packages
(ffmpeg/libav definitely comes to mind) as it would make sure that we
would conflict release numbers with whatever is built in oss or in
multimedia:libs

Another approach would be a pattern or an empty package
("packman-ffmpeg") that just pulls everything of libav*/ffmpeg in with
hard requires -- that might sound crude but in the end, it is what
everyone wants if they add the Packman repos and want to install the
ffmpeg that's in there.

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Handbrake - Latest version?

[Pascal Bleser]

2017-02-07 11:00 GMT+01:00 Olaf Hering <o...@aepfle.de>:
> On Thu, Feb 02, Pascal Bleser wrote:
[...]
> Is libbluray ABI compatible with the version that was released with Leap?
> Both share the same SONAME, but given the history of libbluray failures
> its very likely that binaries not built against the new version will
> misbehave.

Sorry Olaf, I misunderstood, you mean the other way around

True.. that might happen indeed...

Then the better solution would be to make a static build of libbluray
into Handbrake, but not sure that is going to work without some heavy
patching

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Handbrake - Latest version?

[Pascal Bleser]

2017-02-07 11:00 GMT+01:00 Olaf Hering <o...@aepfle.de>:
> On Thu, Feb 02, Pascal Bleser wrote:
>
>> Having a look at it, but I'm currently stuck because they require a
>> patched libbluray so I have to submit the changes there first.
>
> Is libbluray ABI compatible with the version that was released with Leap?
> Both share the same SONAME, but given the history of libbluray failures
> its very likely that binaries not built against the new version will
> misbehave.

The patch adds six bytes in a struct to expose the "clip_id" which is
then used by Handbrake and hence, one will definitely need to use the
latest libbluray from multimedia:libs or from Essentials at Packman
(which is just a _link to multimedia:libs/libbluray)

Unfortunately, I'm not sure how to enforce that in the package...
Could add a Provides: libbluray+clip_id that is then Required in Handbrake
Or bump up the version artificially even though it's not an upstream
version and Require that explicitly in Handbrake (Requires: libbluray*
>= ...)
Both are ugly..

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Handbrake - Latest version?

[Pascal Bleser]

2017-02-01 18:56 GMT+01:00 Jason DeRose :
> Hello, I was curious if packman would be updated to the latest version
> of Handbrake soon? The current version in packman is 0.10.5 which is
> from February 2016. The current release is 1.0.2. The handbrake-unstable
> package is about 3 years old so seemingly abandoned.

Having a look at it, but I'm currently stuck because they require a
patched libbluray so I have to submit the changes there first.

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Issue with publishing ?

[Pascal Bleser]

Hi y'all

I committed an update of MPlayer yesterday and the build is fine but
it is not published (it is in the build service but not in the repos).
Is there currently an issue with publishing to the repos ?

Thanks

cheers,
Pascal

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Viber

[Pascal Bleser]

On Mon, Jan 6, 2014 at 3:46 AM, Mark Fairbairn far...@gmx.com wrote:
 any chance we might see Viber packaged up for openSUSE? Particularly
 considering the sorry state of Skype for linux.
 http://www.viber.com/products/linux/

Hi Mark

Unfortunately, Viber for Linux has the exact same issue as Skype in
terms of packaging:
it is a binary package, no sources available, and while I haven't
checked the redistribution
license, I'm expecting it to forbid any redistribution.

Hence while it could be done from a technical point of view, there is
just no way that
openSUSE or Packman could package and provide it.

cheers,
Pascal.

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] cuetools

[Pascal Bleser]

On Mon, Aug 19, 2013 at 9:04 PM, Dmitriy Perlow d...@open.by wrote:

 Ys musics...@gmx.com Sat, 17 Aug 2013 19:36:01 +0300:

  I see that the cuetools package has a problem.
 Do patches end in .patch? (I cannot fix the error)


 It links to https://build.opensuse.org/**package/show/multimedia:apps/**
 cuetoolshttps://build.opensuse.org/package/show/multimedia:apps/cuetoolsand 
 packman's diff from mm:a seems to be broken…


Builds fine now. Thanks for reporting.

cheers,
Pascal.
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] smplayer2 versioning scheme change

[Pascal Bleser]

On 2012-12-24 12:00:38 (+0300), Dmitriy Perlow d...@open.by wrote:
 Mariusz Fik fisi...@jabster.pl писал(а) в своём письме Mon, 24 Dec
 2012 01:06:51 +0300:

 Hi,

 for now, we use date format (20121017) for smplayer2 version. I'd like to
 change it to release scheme, like 0.8.0. But with that simple
 change in .spec
 file, for rpm, Version: 20121017  Version: 0.8.0. Is there a way
 handle clean
 update from old version (date format) to a new one (release number)?

 I have already prepared 0.8.0 package but not solved yet issue described
 above. Any help appreciated ;)

 What about obsoleting smplayer2  2011 or something like this?

No, that'll just make the package obsolete itself, as 2011
is considered to be higher than 0.8.0 by RPM.

I'm usually cautious enough to cope with such situations by
naming snapshots 0.0+2012 but alas, I didn't in this case.

No good solution to this situation now, except to always include
the timestamp, e.g. Version: 20121224+0.8.0

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpfY8fF4ub9B.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Packman sheduler

[Pascal Bleser]

On 2012-12-11 02:50:19 (+0100), Mariusz Fik fisi...@jabster.pl wrote:
 Hi,

 Our 64bit scheduler is unreachable. Status from 
 https://pmbs.links2linux.org/monitor/old says:
 x86_64: dead 

 Please fix it. Maybe simple restart will help...

Restarted.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpyokjxpXGdJ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Important GStreamer patch

[Pascal Bleser]

On 2012-11-19 19:55:55 (+0100), Martin Schlander martin.schlan...@gmail.com 
wrote:
 Hi

 One of the Phonon developers dropped by the #opensuse-kde IRC channel, saying 
 that:

 This bug: https://bugs.kde.org/show_bug.cgi?id=302652 (When going from a mp3 
 track to an ogg track, Amarok stops playing)

 Is fixed by this GStreamer patch: http://cgit.freedesktop.org/gstreamer/gst-
 plugins-base/commit/?id=3880323 

 Since I'm personally hit by that issue, I'd be very happy if someone could 
 apply that patch to the Packman GStreamer packages ;-)

Hi Martin

We just _link to openSUSE:Factory/gstreamer, so the patch needs
to be applied there.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpmpuZRE4MD6.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PMBS] SR 311 Essentials/x264

[Pascal Bleser]

On 2012-11-01 17:05:03 (+0100), Manfred Tremmel manf...@links2linux.de wrote:
 Am Donnerstag, 1. November 2012, 11:42:53 schrieb PMBS:
  New submit request 311 on x264 by marguerite
  https://pmbs.links2linux.org/request/show/311

  [please accept after gpac] build with gpac, ffmpeg and ffms2 for
  11.4/12.1/12.2/Tumbleweed/Factory. it requires packages' aggravations
  or path repository=openSUSE_XX project=Multimedia/ for those
  targets in Essentials' meta.

 I'm not sure, if ths cycling dependency (ffmpeg needs x264 to build, 
 x264 needs ffmpeg to build) is such a good idea. PMBs shouldn't have a 
 problem when both packages are build once, but whenever we add a new 
 Build-Target, it will fail to solve dependencies.

 Therefore I've allways build x264 binary without ffmpeg support. The 
 only clean way to solve this is, to split x264 into two package one for 
 the libs and devel package only without dependency to ffmpeg and one 
 only to build the x264 executeable with ffmpeg dependency.

Done, we now have libx264 and x264 packages in Essentials.

The x264 binary doesn't use the shared lib, to avoid any cycles
there, and transitive dependencies with ffmpeg.

We should just take are of trying to keep libx264 and x264 in
sync.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpT2cn7ZSe9r.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PMBS] SR 311 Essentials/x264

[Pascal Bleser]

On 2012-11-01 11:42:53 (+), PMBS p...@links2linux.org wrote:
 New submit request 311 on x264 by marguerite
 https://pmbs.links2linux.org/request/show/311

 [please accept after gpac] build with gpac, ffmpeg and ffms2 for 
 11.4/12.1/12.2/Tumbleweed/Factory. it requires packages' aggravations or 
 path repository=openSUSE_XX project=Multimedia/ for those targets in 
 Essentials' meta.

Marguerite, could you please submit the change again?

Now that x264 and libx264 are separate, we don't run into cycles
with ffmpeg.

So that makes x264 buildrequire gpac ?
Then we need to move gpac from Multimedia to Essentials.
(Essentials may not depend on anything, so we don't aggregate
into it, but we can just move a package from Multimedia to
Essentials).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpoGSyL1xOxg.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] handbrake-unstable 0.9.8+4913-1.6 (openSUSE 12.1/x86_64)

[Pascal Bleser]

On 2012-10-20 19:32:02 (+0800), Marguerite Su i...@marguerite.su wrote:
 On Sat, Oct 20, 2012 at 5:49 PM, Pascal Bleser
 pascal.ble...@opensuse.org wrote:
  Done, build is underway.

 Hi, Pascal,

 I have a similar bug report PM-48 at bugs.links2linux.org, I've fixed
 it in stable.

 But I don't have permission to mark it fixed.

Done :)

Thanks!

cheers,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpXDlm81oKFI.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PMBS] SR 304 Multimedia/screengen

[Pascal Bleser]

On 2012-10-20 20:09:43 (+), PMBS p...@links2linux.org wrote:
 New submit request 304 on screengen by Lazy_Kent
 https://pmbs.links2linux.org/request/show/304

 New package: Screenlist Generator. If accepted add me as maintainer/bugowner, 
 please.

Done, and added as maintainer+bugowner.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpoKztHgRKEH.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Registration approval (to admins)

[Pascal Bleser]

On 2012-09-11 11:03:34 (+0300), openSUSE user devel.opensuse@gmail.com 
wrote:
 Hi. I was the third week of waiting for an official reply to my
 previous letters.

Hi openSUSE user.

As explained on IRC, I will not authorize your account
registration because I have no idea who you are, as you keep
everything anonymous (your name, your email address, your
packaging track record and experience, ...).

That's fine, but that is not good enough for me to give you an
account and the possibilities (including potential attack
vectors) that come with it. We don't have enough manpower to
review and verify every submission and, hence, here more than
anywhere else, it is a lot about trust. Which is why a
completely anonymous request won't do.

Hope that's official enough ;)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpXTI93GGM4g.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Approval ***PLEASE***

[Pascal Bleser]

On 2012-09-05 10:59:15 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 5 September 2012 10:37, Philipp Thomas p...@suse.de wrote:
  I'm now waiting for approval of my registration for three days. Is there
  nobody that can do the approval?

Done.

 Probably just Pascal and... not sure anybody else. And I didn't know
 from him for some time. Probably on holidays.

Peter could too. Wasn't on holidays, just on my way out of the
openSUSE project, kinda, slowly, having too much to do, and not
having much interest in the project any more.

But apparently I'm the only one who can take care of certain
things at Packman and, hence, I won't be able to get out of this
too soon ;)

Sorry for the delay(s), but everyone will have to live with it
unless someone else steps up to invest time into this -- or
making OBS reliable and easy to work with outside of build.o.o,
that might help too.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpolklyXawqQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg and other dependency issues for 12.1

[Pascal Bleser]

On 2012-08-04 16:41:51 (+0200), Hans-Peter Jansen h...@urpla.net wrote:
 Hi Packmans,

 it looks like the ffmpeg dependencies are distorted:

Yeah, there is some odd dependency here because upstream didn't
bump the SONAME version on libavutil even though it actually
requires the most recent (or something like that, I don't
remember the details).

I don't remember the solution, I think you need to update the
libavutil51 first and then it's fine.

 Selecting 'ffmpeg-0.11.1-1.2.i586' from repository 'Packman repository 
 (openSUSE_12.1)' for installation.
 Resolving package dependencies...
 Force resolution: No
[...]

 I also noted another strange dep:
   Selecting 'ldvd-2.0.2-6.1.i586' from repository 'Packman repository 
 (openSUSE_12.1)' for installation.
 Resolving package dependencies...
 Force resolution: No

 Problem: nothing provides mkisofs = 1.15 needed by ldvd-2.0.2-6.1.i586
  Solution 1: do not install ldvd-2.0.2-6.1.i586
  Solution 2: break ldvd-2.0.2-6.1.i586 by ignoring some of its dependencies

It's a hard-coded dependency in our package, and apparently
mkisofs is not available with more recent openSUSE versions any
more. Just committed a change that requires
cdrkit-cdrtools-compat instead.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpR1pSar5L88.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PMBS] SR 248 Essentials/lame

[Pascal Bleser]

On 2012-07-18 14:48:14 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 15 July 2012 14:46, PMBS p...@links2linux.org wrote:
  New submit request 248 on lame by RedDwarf
  https://pmbs.links2linux.org/request/show/248

  - update to 3.99.5

 Given that two days later a different patch was committed and this SR
 was not even rejected it seems we still have a problem with #PM-9 and
 making people aware of SRs.

Yes, sorry, my bad, I was on a short 12.2 fixing spree after
adding it to the repos (and had to fix lame) and didn't see your
SR :\

 Anyway. About the committed version:
 - The license seems to be LGPL-2.0+, no LGPL-2.1+
 - lame-tgetstr.patch is kept, forcing a autoreconf call that makes the
 build fail in old distributions, even if I don't think it's needed. I
 don't know a lot about curses, but: When libtinfo was splitted it
 wasn't done in the best way, but soon after a linker script was used
 to avoid the need of patching other packages. In my SR I didn't use it
 and the only difference in the result is that in 12.2 I linked
 against libncurses instead of libncursesw... but since in = 12.2 only
 libtinfo is used I don't think it really matters.

I presume that libncurses on recent openSUSE versions is also
UTF-8 (normally only libncursesw is) and hence, indeed, you're
most probably right.

 SR#248 has other changes that are less important, but those two IMHO
 should be fixed.

Sorry again, and thanks for the changes.
I re-merged the funky patching that's needed on 12.2 to disable
outdated automake/autoconf features though.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpMBXMyiXrgZ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] How to mirror packman in the US

[Pascal Bleser]

On 2012-07-09 21:51:12 (-0400), Frank Gruman fgatw...@verizon.net wrote:
 Hello,

 I've been an openSUSE user for several years (I think I started at
 version 7) and have utilized the Packman repositories for quite a while,
 too.

 I recently saw the blog posting at
 http://dev-loki.blogspot.com/2012/05/speaking-of-packman-mirrors.html
 asking for mirroring support.  I am willing to try to set up the mirror
 through my hosted domain at my ISP (Dreamhost).  I do not see any
 statements in their ToS or AUP that would prohibit this.  It's a shared
 hosting account so the speed might not be screaming but I find it
 sufficient for almost all of my other hosted domains on their servers.

 what are the next steps?

Hi Frank

Thanks for your support, and sorry that your email slipped
through.

As far as I know, the next steps would be to be registered as a
mirror in order to be able to rsync from our primary server --
something Marc manages. Marc ?

An alternative, and a solution in the mean time, would be to
mirror one of our mirrors using rsync. e.g.
rsync://packman.inode.at/packman/suse/

/!\ Mind you, the whole shabang sums up to 43 GB /!\

12.1 is 6 GB and 12.2 is currently 3.7 GB (not all repos are
enabled yet, but the most important are (Essentials and
Multimedia)), so you might prefer to cherry-pick there and e.g.
only rsync
rsync://packman.inode.at/packman/suse/openSUSE_12.1
(which would already be very helpful to users on your side of
the big pond.)

Also, you should run the rsync at least every four hours in
order to be sufficiently up-to-date.

In any case, if you do mirror something, please keep us posted,
so we can advertise it accordingly :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpZTU4kzojuh.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] When to add 12.2?

[Pascal Bleser]

On 2012-07-14 15:22:43 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 We should wait:
 - to save build power

 We should add it right now:
 - because we will have more time to fix any problems that happen with
 12.2 (but not in 12.1 or Factory)
 - users will be happier to test 12.2 RC1 (and we want them to test it)
 if they have Packman available

Added 12.2 two days ago, pretty much everything seems to build
just fine in Essentials and Multimedia (at least the stuff that
also builds for 12.1 ;)).

Files are on our primary file server now and should hence be
picked up by mirrors in the next hours. Let's check by tomorrow.

We can then do a proper announcement/JFYI on the opensuse
project list. (But let's wait for mirrors to sync first :)).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpxf6s09E9MP.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] vlc: no h264/x264 decoder [SOLVED]

[Pascal Bleser]

On 2012-07-07 11:38:56 (+0200), Dominik Kopp m...@kabelfunk.de wrote:
 Manfred Tremmel wrote:
[...]
 I had used a libva package from X11 repo. (version 1.1.0)
 So I switched back to the default version of 1.0.14 (suse 12.1)
 and vlc works now!

Seems like we need to enforce that vlc uses the libva package
from Packman then.

(empty libva-packman that is required by vlc, and libva-packman
requires libva* = %{version}-%{package})

cheers
-- 
Pascal Bleser l...@fosdem.org   http://fosdem.org/
FOSDEM 2012 ::: 4 + 5 February 2012 in Brussels, Belgium
Free and Opensource Software Developers European Meeting


pgpW8MST9SCtl.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] mldonkey from packman repo stucks at the beginning

[Pascal Bleser]

On 2012-05-29 22:34:02 (+0200), GMAIL ajvp1...@gmail.com wrote:
 Hi, good evening:

Hi Alfredo
(sorry, sending again, had a typo in the mailing-list address
¬¬)

 first of all, thanks for your effort packaging mldonkey for opensuse,
 but at 12.1 version there is
 no way to make it work.
 Heavy CPU load and no answer on URL localhost:4080 nor
 192.168.250.120:4080 (my internal IP)
 The only answer is:

 alfredo@pb1400cen:~ mldonkey 
 [1] 6030
 alfredo@pb1400cen:~ 2012/05/29 22:09:14 [cO] Starting MLDonkey 3.1.1 ...
 2012/05/29 22:09:14 [cO] Language ES, locale UTF-8, ulimit for open files 1024
 2012/05/29 22:09:14 [cO] raised ulimit for open files from 1024 to 4096
 2012/05/29 22:09:14 [cO] MLDonkey is working in /home/alfredo/.mldonkey

 2012/05/29 22:09:14 [cO] creating new MLDonkey base directory in
 /home/alfredo/.mldonkey

 2012/05/29 22:09:14 [Gettext] Loading language resource
 mlnet_strings.es_ES.UTF-8
 2012/05/29 22:09:14 [cO] loaded language resource file
 2012/05/29 22:09:14 [DNS] Resolving [pb1400cen.mozoilo.site] ...

 where :
 my PC is named pb1400cen.
 my user (no privileges) is alfredo
 pb1400cen.mozoilo.site is my internal FQD. (resolved by host file, not bind)

 under .mldonkey there are tmp directory and mlnet_strings.es_ES.UTF-8
 file (both of them empty).

 No logs under /var/log/messages. No parameter found to make mldonkey
 start verbosed...

 Any clue? any forum where this problem has been resolved?

I'm afraid I really can't help, I don't even use mldonkey
myself, I just keep the package building and up-to-date.

Please report the problem with the mldonkey developers, as we
just package it, we don't write the software itself.

(And, sorry, I don't have the time to relay the bugs there
myself :\)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp0WM1MoD1Qd.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PMBS] SR 225 Extra/urwid

[Pascal Bleser]

On 2012-05-22 17:29:31 (+0200), Guido Berhoerster 
guido+links2linux...@berhoerster.name wrote:
 On 22.05.2012 17:07, PMBS wrote:
 New submit request 225 on urwid by posophe
 https://pmbs.links2linux.org/request/show/225

 Needed by wicd (coming soon)

 This should be named python-urwid according to packaging policy.
 Also, both packages are already maintained in OBS, why do you want
 to duplicate them here instead of pushing them into Factory? In
 particular python-urwid would be useful to have in Factory since
 it's a dependency for other packages as well.

Factory isn't that relevant here or, rather, a different topic.

I agree, I don't see why we would have wicd in Packman in the
first place, much better suited to be put into build.o.o and a
relevant repository there (and then pushed into Factory as
well).

In any case, if we do need something that is already packaged in
some repository on build.o.o, then we can link them, e.g.:

osc -Apm linkpac \
openSUSE.org:devel:languages:python/python-urwid \
Multimedia

You just need to put openSUSE.org: in front, as that will tell
our OBS instance that it has to use the remote API to build.o.o.

Please don't link to home: repositories, for obvious reasons
(quality) ;)

But as said, wicd should be packaged on build.o.o instead.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp4GgiQ6JrgX.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] deluge 1.3.4-1.13 (openSUSE 12.1/noarch)

[Pascal Bleser]

On 2012-05-23 00:55:08 (+1000), Stephen Poole step...@eloop.id.au wrote:
 Any chance that a build of deluge 1.3.5 could be released any time soon?

Done, will show up on the mirrors soon.
Thanks for prodding (hard to keep track of upstream packages
that are not annouced on freshmeat).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpS1GMsLaSoT.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] New request 224

[Pascal Bleser]

On 2012-05-20 18:24:23 (+0200), Marc Schiffbauer m...@links2linux.de wrote:
 Am Sonntag, 20. Mai 2012, 15:03:39 schrieb PMBS:
  New submit request 224 on guvcview by zaitor
  https://pmbs.links2linux.org/request/show/224

  Update to version 1.5.3

 Ich think these mails should not go to this list?

Seems my OBS plugin finally works ^^

 What do you think?

I would like those emails to be sent to the packagers.
I don't know whether it's worth creating an additional list for
that purpose.
Or maybe reuse packman-adm@ but then we'll need to subscribe
quite a few people there.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgppUVXMC7ucm.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Fwd: Re: [mythtv-users] Mythtv and Unicable?

[Pascal Bleser]

On 2012-05-10 23:17:57 (+0200), Pascal Bleser pascal.ble...@opensuse.org 
wrote:
 On 2012-05-10 22:45:20 (+0200), Smartysmart34 smartysmar...@web.de wrote:
  Ich bin know-how-seitig wirklich nicht in der Lage, Programmpakete zu
  patchen und neu zu compilieren. Wäre es denn aus Packman-Sicht denkbar,
  das Mythtv-Paket um den unten genannten Patch für Unicable-Support zu
  ergänzen?

 Bin dabei, ich sehe zu das es bei mir richtig baut, und lade
 anschließend die Änderungen auf den Server und dann kommt ein
 neues Release der Pakete ins Repository.

 Du brauchst dann nicht das SQL-Skript auszuführen, das habe ich
 noch in den Datenbank-Abgleich-Mechanismus von MythTV
 reingepatcht.

 Testen kann ich es aber leider nicht, da brauche ich deine Hilfe
 (ausprobieren und bescheid geben ob's klappt oder nicht) :)
 [...]

So, ich habe den Patch rückportiert auf MythTV 0.25 und in das
Paket eingebaut, sollte jetzt in den Repositories sein (Version
ist = 0.25-6.1).

Bitte testen :)


In English:
As requested, I added the patch for Unicable satellite channel
router to our MythTV 0.25 package
(http://code.mythtv.org/trac/ticket/9726); there is no need to
manually upgrade your database as described in that ticket, as
I've also patched that into the automatic database upgrade
mechanism of MythTV.

But it's totally untested so if you have MythTV and can afford a
short breakage, please upgrade to the new package and send us
feedback on whether it works or not, either here on the list or
on https://bugs.links2linux.org


cheers,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpMiX2ZnZDAV.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Fwd: Re: [mythtv-users] Mythtv and Unicable?

[Pascal Bleser]

On 2012-05-10 22:45:20 (+0200), Smartysmart34 smartysmar...@web.de wrote:
 Ich bin know-how-seitig wirklich nicht in der Lage, Programmpakete zu
 patchen und neu zu compilieren. Wäre es denn aus Packman-Sicht denkbar,
 das Mythtv-Paket um den unten genannten Patch für Unicable-Support zu
 ergänzen?

Bin dabei, ich sehe zu das es bei mir richtig baut, und lade
anschließend die Änderungen auf den Server und dann kommt ein
neues Release der Pakete ins Repository.

Du brauchst dann nicht das SQL-Skript auszuführen, das habe ich
noch in den Datenbank-Abgleich-Mechanismus von MythTV
reingepatcht.

Testen kann ich es aber leider nicht, da brauche ich deine Hilfe
(ausprobieren und bescheid geben ob's klappt oder nicht) :)
[...]

mfg,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpyZpPEa7crE.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Speaking of Packman mirrors...

[Pascal Bleser]

On 2012-05-07 20:52:21 (+0200), Lars Vogdt l...@linux-schulserver.de wrote:
 Reading http://dev-loki.blogspot.com/2012/05/speaking-of-packman-mirrors.html,
 I hope that every single mirror and every single Bit counts...

 As we reduced our own traffic (we outsourced much traffic to
 sourceforge.net by providing our openSUSE-Education ISO images
 there), we've currently ~4 TB/Month left until we reach our bandwith
 limit.

 So we can offer to host the packman repository on our server, if you like.
 What we already setup for public:

 rsync://rsync.opensuse-education.org/packman/
 http://www.opensuse-education.org/packman/

 If you like to run a push mirroring, please inform us - or tell us
 your rsync details, so we can start mirroring your repositories.

Thanks! I pass the buck to Marc, tracking it here:
https://bugs.links2linux.org/browse/PM-17

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpzPSJto1qpV.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Package update workflow?

[Pascal Bleser]

On 2012-05-04 23:49:27 (+0200), Manfred Tremmel manf...@links2linux.de wrote:
 Am Freitag, 4. Mai 2012, 18:36:26 schrieb Cristian Morales Vega:

  transcode is dead, let's accept it. And I see 11 packages that require
  it. Either the dependencies are wrong or those packages should have
  already started to move to something else. Those packages are usually
  DVD related... we are in 2012!!! DVDs??? Who uses those any more?

 I maintaine some packages which are not updated for years, but used by 
 other packages, like transcode. What's the alternate to DVD's on linux? 
 Blue-Ray Disks with HDCP, AACS and BD+ or Video On Demand over Internet 
 with DRM and no Linux clients? DVDs are well supported and CSS is no 
 real problem, so it simply works with linux.
 As long as I can manage transcode to build with new gcc versions and new 
 library versions from e.g. ffmpeg and no security problems are known, 
 why should we drop it?

  But more important. I somebody sees in the metadata that a package has
  a maintainer (even if that maintainer is not available any more) he
  is not going to offer himself to be the new maintainer.

 In the past we lost a lot of maintainer entries in the packages, I don't 
 know when and why this happend. I'm also a littel bit confused, because 
 osc commands have changed a while ago. I'm not sure, how to set 
 maintainer entry for my packages once again.

osc -Apackman maintainer --add=username --role=maintainer \
Essentials transcode

-Apackman is assuming you have an alias packman on pmbs-api,
like this, in ~/.oscrc:
---8
...

[https://pmbs-api.links2linux.org]
aliases=packman,pm
user=...
pass=...
---8

If you need more permissions, please let me know (private email
or poke me on IRC, I'm yaloki on irc://irc.freenode.net/#packman
;))

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpb1RrlFBiWP.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Removed clementine and clementine-unstable

[Pascal Bleser]

I deleted clementine and clementine-unstable in Multimedia.
The former is maintained and available on build.opensuse.org
(and failed to build in packman anyway), and the latter, well, I
didn't have time to maintain it anymore (not sure it's actually
still needed, it was outdated).

If there's any reason to have them on Packman, please speak up,
we can still re-add them, but I don't see any (doesn't need
ffmpeg or mad or ..., uses gstreamer for codecs).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpEikZUXFVSN.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] No connect

[Pascal Bleser]

On 2012-05-05 20:33:48 (+0300), VDeveloper musics...@gmx.com wrote:
 Is Packman.inode.at down? 

Apparently it is, let's see whether it's temporary.

In the mean time:
http://packman.links2linux.de/mirrors

But the mirror at warwick.ac.uk is gone, we have to update the
list.

If anyone spots a mirror elsewhere, please let us know :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp0zsD1gsDtQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] No connect

[Pascal Bleser]

On 2012-05-05 23:33:15 (+0400), Kyrill Detinov lazy.k...@opensuse.org wrote:

 On Sat, 5 May 2012 20:43:03 +0200 Pascal Bleser wrote:

  If anyone spots a mirror elsewhere, please let us know :)

 http://lists.links2linux.de/pipermail/packman/2011-March/009756.html

Thanks, added to the list.

Marc, can you update it on the website?

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp9ubl7cTM82.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Package update workflow?

[Pascal Bleser]

On 2012-05-05 22:21:39 (+0200), Stefan Seyfried 
stefan.seyfr...@googlemail.com wrote:
 Am 04.05.2012 17:48, schrieb Pascal Bleser:
  On 2012-05-04 15:58:33 (+0100), Cristian Morales Vega 
  reddw...@opensuse.org wrote:
  On 4 May 2012 15:39, Stefan Seyfried stefan.seyfr...@googlemail.com 
  wrote:
[...]
  To me, personally, I see it like this:
  - if I give you maintainer level on a package that's in a
non-home project (Essentials, Multimedia, Extra, Games), then
do as you wish because you have my complete trust

 I actually did not even check the maintainership -- in the openSUSE BS I
 am maintainer of all the Projects I am maintaining packages in, so it
 didn't even occur to me that there might be a permissions issue :-)

Added you as maintainer in all toplevel projects (Essentials,
Multimedia, Games, Extra).

 Anyway, for now the submitrequest is the only thing I can do to get it
 updated and that's what I have done: request 196.

Thanks, accepted.

[...]
 I think a common sense approach makes sense here: trivial stuff (like
 my clipgrab update) can go in directly, especially if it is a leaf
 package with no dependencies.
 Updates to core stuff like ffmpeg  friends by people who have not yet
 proven they know what they are doing should be SR'ed and reviewed.

Yes, that's indeed what it boils down to :)

  There have been quite a lot of packagers who have offered to
  help, and who have an account, but who have only done very minor
  fixes, or added new packages (e.g. because they weren't allowed
  to put them on build.o.o), and who pretty much disappear again.

 I'm trying to help changing this -- for example by encouraging our
 trainees to help out on packman (and openSUSE BS) and my boss is
 indirectly sponsoring this effort by letting us do that in our paid time.

Awesome :)

  Don't get me wrong, any help is much appreciated, but it would
  be even more useful if some packagers would step in and feel
  more like being in charge here and take ownership of some
  packages.

 That's actually what I'm trying to do :-)

Yes indeed, thanks a lot, even more useful from seasoned
packagers such as you (but every help is welcome, don't make me
say what I didn't :)).

  Don't be afraid of stepping on other people's toes too much:
[...]
  - if you have some time to spend, pick broken packages, fix
them, commit directly, there is no need for a review process,
our staffing is just way too thin for that -- especially if
you're a seasoned packager (like you ;)), you know what you're
doing
  - same goes with upgrades: Packman has always had the unwritten
policy of updating packages to their latest version, always;
while there are good points for going with a different
strategy (e.g. as for openSUSE releases, only backport
patches), my impression is that our user base is 50/50 on
that; with a lot more people on the team, we could surely even
do both, at least for the stuff in Essentials, but it isn't
the case; short version: newer upstream version, just go for
it, no need for reviews, you know what you're doing

 Ok, I'll probably go through the impressive list of build failures in
 Extra and fix some of those to get comfortable with the workflow :-)

Note that many packages are also only there for historic reasons
(Packman predates build.o.o by many years).
We didn't import everything we had before we used OBS, but there
are definitely a bunch of packages that we could or even should
delete, especially what's not in Essentials and Multimedia.

Typically because it's maintained (better) somewhere on
build.o.o (often with spec files that have been copied from
Packman, almost always without letting us know).

But, obviously, common sense, before deleting a package, better
prod on the list first.

  But it's perfectly fine to branch a package in order to submit
  it (but please clean up afterwards, once it's done, and rdelete
  your home: packages).

 Ok. I would feel quite uncomfortable to commit packages with only local
 build tested (although I'll try to implement some automatic local build
 for all repos thing so that I can run this overnight on my home server
 or something like that.

I think it's fine to do so.
Personally, I do local builds on 12.1 (x86_64) and then I
submit.
If builds fail on other variants, I do a local build to
reproduce, then fix, and probably also do local builds on a few
other distro versions (depends on the nature of the issue).
After all, if the build fails, the old version of the package
remains in the repository. Sometimes leads to issues when there
are interdependencies across packages (e.g. the gstreamer
stack), but typically that approach works fine.

Well, if I had only a handful of packages to maintain, I'm sure
I would test on all combos first but... ;)

 For now, I'll try to be careful to increase the quality of the packages
 I'm touchen and if I'm missing permissions on a project / package, I'll
 send a notification about

[packman] Maintainers speak up (was: Package update workflow?)

[Pascal Bleser]

On 2012-05-04 18:36:26 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 4 May 2012 16:48, Pascal Bleser pascal.ble...@opensuse.org wrote:
  On 2012-05-04 15:58:33 (+0100), Cristian Morales Vega 
  reddw...@opensuse.org wrote:
  That's why a lot of packages don't really have much of a
  maintainer and why, instead, I'm jumping from one package to
  another like a fire fighter. If someone feels like wanting to
  own packages in Packman, be my guest, please do so ;)

 A solution is to just lower the workload.
 I think a problem is that nobody wants to drop packages. If we had
 download statistics probably we would find packages with *zero*
 downloads! Usually packages that have been abandoned upstream and are
 therefore the ones that take more time to make them build in the
 latest versions.

Quite possibly, yes.

 transcode is dead, let's accept it. And I see 11 packages that require
 it. Either the dependencies are wrong or those packages should have
 already started to move to something else. Those packages are usually
 DVD related... we are in 2012!!! DVDs??? Who uses those any more?

dvdrip is still quite popular though, afaik. At least we did get
bug reports about it not too long ago.
mythtv uses it too.

 There a few packages I just don't feel motivated to fix because I
 don't think any user really cares. If you look at the Packman build
 service the situation looks bad. But we don't have so many users
 complaining here. Perhaps it's just that no user cares about those
 packages any more.

Possibly, but unfortunately we don't have good means to find
out.

Well, except removing them and waiting for users to scream.
That always works, and maybe that's the way to do it.

 And it could be argued that we could drop Evergreen and SLE targets
 from Essentials to also lower the workload. But if interested people
 can accept its current state I guess it's not such a problem.

They occasionally create some work because things don't build
there from time to time. I only bother with fixing the builds
for them with stuff from Essentials (e.g. backporting older
versions of dependencies, etc), at least for packages I believe
could be really useful (vlc, mplayer, ffmpeg).

Those are clearly best effort.

  So... there is no clear policy. And if you trust the
  maintainer/bugowner tags in the package metadata it's easy to be
  worried about stepping on the toes of somebody that isn't there.

  How do you mean?

 Just that, that I don't know who disappeared and who is just in a two
 weeks holiday. I don't do something expecting the maintainer to do it
 (searching for some other package broken...) or send an email to
 him... Just to find he is not there any more.

Yep, I understand. Hope my post clarified the situation a bit.

 But more important. I somebody sees in the metadata that a package has
 a maintainer (even if that maintainer is not available any more) he is
 not going to offer himself to be the new maintainer.

 Do you want new maintainers? Publish here a list of packages without
 maintainer and interested people will appear. But... there is a list
 of packages without a maintainer? Can it be created reliably at all?

Well, the situation, right now, as I see it:
* Manfred takes good care of a few packages that need some
  experience with them, most prominently ffmpeg and xine
* I'm staying on top of mixxx, MPlayer, smplayer and some jack
  related packages (because I use them all the time)
* almost everything else: has no maintainer and I'm jumping in
  because no one else does

Manfred, do you have other packages that you'd like to remain
the sole maintainer of ?

Or anyone else ? Please speak up so we can draw a map of what's
actually maintained (and where maintainers would like to stay in
charge). Everything else is up for takes.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpIW22sKHYVD.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Maintainers speak up (was: Package update workflow?)

[Pascal Bleser]

On 2012-05-04 20:05:51 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 4 May 2012 19:14, Pascal Bleser pascal.ble...@opensuse.org wrote:
  Well, the situation, right now, as I see it:
  * Manfred takes good care of a few packages that need some
   experience with them, most prominently ffmpeg and xine
  * I'm staying on top of mixxx, MPlayer, smplayer and some jack
   related packages (because I use them all the time)
  * almost everything else: has no maintainer and I'm jumping in
   because no one else does

  Manfred, do you have other packages that you'd like to remain
  the sole maintainer of ?

  Or anyone else ? Please speak up so we can draw a map of what's
  actually maintained (and where maintainers would like to stay in
  charge). Everything else is up for takes.

 I tried to keep the maintainer/bugowner up to date. I really maintain
 these (even if I don't use some of them so much)

 $ osc -A pm my -U RedDwarf pkg
 Essentials/amarok
 Essentials/gmtk
 Essentials/kdemultimedia4
 Essentials/kdemultimedia4-12.1
 Essentials/kdemultimedia4-Tumbleweed
 Essentials/mp4v2
 Essentials/npapi-vlc
 Essentials/opencv
 Essentials/opencv-12.1
 Essentials/strigi
 Essentials/vo-aacenc
 Essentials/vo-amrwbenc
 Games/libdevil
 Games/love
 Games/scummvm
 Games/scummvm-tools
 Multimedia/aegisub
 Multimedia/moc

 I keep distribution specific versions of opencv because it's tendency
 to break binary compatibility. And from kdemultimedia4 just because I
 don't know what would happen if you mix latest ones with older KDEs.
 You are set as the maintainer of gnome-mplayer/gecko-mediaplayer. If
 you don't want them I will take them to complement gmtk.

Sure, I made you maintainer there.

 I am used to the OBS informing me of upstream updates. How do you
 manage it? Any scripts?

Nope, nothing. Personally, I keep a daily eye on the
freshcode.net feed ;)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp48DUW7GO26.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Maintainers speak up (was: Package update workflow?)

[Pascal Bleser]

On 2012-05-04 20:12:05 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
[...]
 I can also take ownership of the gstreamer things (the latest ones,
 those gstreamer-0.10.4 and gstreamer010-plugins-good-0.10.24 can
 be kept as a community effort). I don't mind taking care of the
 relationship with multimedia:libs, fixing problems here.

Thank you, they're yours :)

Added you as maintainer to all the *gstreamer* in Essentials.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpCRu0PWlsP2.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] mplayer2-2.0+r20120414-1.1.x86_64 for openSUSE 11.4

[Pascal Bleser]

On 2012-05-02 06:45:11 (+0200), Martin Herkt lach...@hong-mailing.de wrote:
 I can’t reproduce that with any of my BDs; could you upload a small sample 
 cut 
 of that TS you have there? I’m using libav instead of ffmpeg, so this might 
 be 
 an ffmpeg regression (possibly demuxer-related).

The MPlayer package uses an in-tree build of ffmpeg (and hence
doesn't use the ffmpeg library from the libffmpeg package),
updating to the latest revision on a regular basis so, yes,
that's not excluded (there isn't such a thing as a stable
release in ffmpeg, unfortunately).

But then, arguably, we would have received more bug reports
about it, as it would have affected everyone (unless that file
is spechul and unique in some way ;)).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp2htpUW4paL.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Registered but not approved

[Pascal Bleser]

On 2012-04-29 18:09:05 (+0200), Stefan Seyfried 
stefan.seyfr...@googlemail.com wrote:
 After finally finding out that enabling cookies is needed to make the
 registration work... I now need approval so that I can start fixing my
 kids' packages :-)

Done, welcome aboard :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp3EPs0iraWQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Removed 11.3 in OBS

[Pascal Bleser]

I removed openSUSE_11.3 in Essentials, Multimedia, Extra and
Games, as of PM-10:
https://bugs.links2linux.org/browse/PM-10

If someone initiates Evergreen for 11.3, we can add it then to
Essentials, won't be that much to build.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpLzKR6eNeI0.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman: it's alive

[Pascal Bleser]

On 2012-04-29 12:53:25 (-0500), Malcolm malcolm_le...@bellsouth.net wrote:
 On Sun, 29 Apr 2012 10:45:12 -0700 upscope upsc...@nwi.net wrote:
[...]
  Just tried to get to link but browers report certificate is bad.:

  code:
  --
   bugs.links2linux.org uses an invalid security certificate.
   The certificate is not trusted because no issuer chain was provided.
   (Error code: sec_error_unknown_issuer)
  /code:
  

  Is it safe to proceed. do I need to get an update some where. I'm
  using SeaMonkey right now but Konquer gives simular error.

[...]

 AFAIK, you need to check if ca-certificates-cacert is installed.

Indeed, it's a CAcert certificate.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpKIDMFTC1JQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman: update

[Pascal Bleser]

On 2012-04-27 07:51:41 (+), Jürgen Weigert jnwei...@gmail.com wrote:
 Pmbs.links2linux.de has a link 'Reporting a bug' it points to
 http://en.opensuse.org/openSUSE:Submitting_bug_reports
 I suggest to make this point to the new jira instance, where some helpful
 links could point to chat, forum, suse bugzilla etc

Fixed, thanks.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpJFWcyBC68a.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Cream?

[Pascal Bleser]

On 2012-04-27 21:43:10 (+0300), Vdeveloper musics...@gmx.com wrote:
 Um, can Cream - http://cream.sourceforge.net/ be packaged? 

Why would that need to be on Packman ?

Might be a better idea to poke the KDE team (iirc it's qt or kde
based) at irc://irc.freenode.net/#opensuse-kde

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpCf1fq27gv4.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Bugtracker for Packman: it's alive

[Pascal Bleser]

I received the approval for an unlimited open source project
license for JIRA from Atlassian, yay :)

Hence the system is now live and ready for production:
https://bugs.links2linux.org

* it is HTTPS only (I might add a redirect HTTP - HTTPS)
* the certificate is CAcert, should be accepted out of the box
  on openSUSE
* anyone can create an account
* administrators are currently Marc Schiffbauer and myself
* JIRA is extremely configurable in its workflows, screens,
  fields, etc... -- if anyone has suggestions, please do make
  them on this list; I personally believe it should remain as
  simple as possible to avoid confusing less experienced users,
  but any idea is worth discussing :)
* I'll make a broad announcement on openSUSE channels

And, quite obviously: please use the bugtracker instead of
emails to report issues, package requests, etc...

It might be a little more effort than just sending an email, but
makes it a lot easier to
- not miss any of them that might get lost and forgotten in
  inboxes
- pick TODOs for people on the Packman team
- keep track of the status of things (okay, that's obvious :))
- highlight how badly we need more people to contribute to
  Packman

If you are a Packman packager (and hence have access to the
Packman OBS instance), please send me a short email or poke me
on IRC (I'm yaloki on freenode) to let me know, and I'll add you
to the packman-packagers JIRA group.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpmUh4HdKFRT.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman: update

[Pascal Bleser]

On 2012-04-26 16:08:29 (+0200), Christian ch...@computersalat.de wrote:
 Am 26.04.2012 02:04, schrieb Pascal Bleser:
 It's on HTTPS now:
 https://bugs.links2linux.org/

 (the cert is a CACert)

 great. :)
 Is this a fresh install ? Cause I can not login with the account
 (computersalat) I created on the previous URL.

Yes, it is a fresh installation. Sorry, you need to re-create
your user on https://bugs.links2linux.org :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpPtoTJ29Ng9.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman: update

[Pascal Bleser]

On 2012-04-25 01:07:12 (+0200), Pascal Bleser pascal.ble...@opensuse.org 
wrote:
 An update on the topic.

 I decided to go for JIRA (thanks to everyone for their
 feedback).

 It is now running on the infrastructure that is kindly provided
 by Marc Schiffbauer (whom we'll never thank enough :)).

 http://bugs.links2linux.org/

 But don't use it for real bugs just yet, as:
 * I made the request for a JIRA open source license at
   Atlassian, it's pending, I'll receive the approval (or not, but
   that would be surprising) within 10 days
 * we should run it exclusively behind HTTPS instead of HTTP to
   prevent user names and passwords to be sent in clear text

 I'll broadly announce it once those steps have been performed.

It's on HTTPS now:
https://bugs.links2linux.org/

(the cert is a CACert)

Waiting for Atlassian's response on the open source license
request and then we're good to go live :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpxJtzW5GTnR.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman: update

[Pascal Bleser]

On 2012-04-25 17:42:10 (-0700), upscope upsc...@nwi.net wrote:
 Can I setup an account on it now to get a feel for how it works or is 
 there a test account. 

Anyone can create an account:
https://bugs.links2linux.org/secure/Signup!default.jspa

I have created a project Test which has the same screens and
workflow, if you want to play with it a bit.

Essentially, I'm only waiting for Atlassian to grant us a free
license for open source projects to give it green light.
It's a matter of a few days, a week at most.

[...]

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpOdIRZoqMUB.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] hddtemp 0.3_beta15-13.8 (openSUSE 12.1/x86_64)

[Pascal Bleser]

On 2012-04-23 00:24:03 (+0400), Kyrill Detinov lazy.k...@opensuse.org wrote:

 On Sun, 22 Apr 2012 11:12:02 +0200 Alex wrote:

  It's impossible to compile on this architecture or it's only a
  missing? Can you provide it?

 Compilation failed for i586
 http://pmbs.links2linux.org/package/rawlog?arch=i586package=hddtempproject=Extrarepository=openSUSE_12.1

Having a look at it.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpQF2KKJwjMs.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] hddtemp 0.3_beta15-13.8 (openSUSE 12.1/x86_64)

[Pascal Bleser]

On 2012-04-22 11:12:02 (+0200), Alex alessandro.sturni...@gmail.com wrote:
 Hi,
 I've installed openSuE 12.1 on my netbook with i386 architecture
 (it's an Atom based netbook), and hddtemp is missing for i386/i586
 on your repository.
 It's impossible to compile on this architecture or it's only a missing?
 Can you provide it?
 Altought I think I can build the right package from the src.rpm.

Fixed, will be in the repos in a few hours at most.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpyFog9dL6IK.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] vlc-aout-pulse on opensuse 11.4 x86_64

[Pascal Bleser]

On 2012-04-17 12:50:44 (-0600), Joseph Short paga...@estreet.com wrote:
 I'm having a problem.  I am running opensuse 11.4 x86_64 and VLC appears
 to have been recently upgraded from 1.1.13-13.8 to 2.0.1-5.2.  I am
 being prevented from upgrading.

 I am using packman repository http://packman.inode.at/suse/openSUSE_11.4/

 It appears the cause is there is no vlc-aout-pulse-2.0.1-5.2-x86_64.rpm,
 and none is available anywhere.  I notice opensuse 12.1 has an upgrade
 with a higher version number and includes vlc-aout-pulse.

 Is this package not needed for this version only or was it just overlooked?

Indeed, it is only built for 12.1 and beyond.

Enabling it for 11.4 too, I'll see whether that works
(pulseaudio recent enough there for vlc) and I'll report back.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpojFWN2WbsZ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kdenlive

[Pascal Bleser]

On 2012-04-23 23:14:21 (-0500), rlee rleev...@gmail.com wrote:
 When I try to start kdenlive I get this:

 kdenlive: error while loading shared libraries: libmlt.so.4: cannot open
 shared object file: No such file or directory
 I checked, the libmlt5 in Packman provides libmlt.so.5 but not 4. It is my
 hope that it's a help.

On which version of openSUSE is this? And which arch?

Really odd unless it's tumbleweed or factory, where kdenlive
failed to build and hence didn't pick up the upgrade of libmlt.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpEJJbCLcEE8.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] DVDStyler 2.1

[Pascal Bleser]

On 2012-04-19 18:51:17 (+0200), Willem Franssen willemfrans...@planet.nl 
wrote:
 Can you package DVDStyler version 2.1 please.
 This version has been released on 20-12-2011
 http://www.dvdstyler.org/en/news

Done, sir ;)

Thanks for notifying. A few projects don't publish any update
information on freshcode.net, which makes it very difficult to
keep track of them, especially when one has to maintain a few
hundred packages.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpwR7I6VW6Xf.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] OpenShot 1.4.2

[Pascal Bleser]

On 2012-04-19 18:54:05 (+0200), Willem Franssen willemfrans...@planet.nl 
wrote:
 Can you package OpenShot version 1.4.2 please
 This version has been released on 05-02-2012
 http://www.openshotvideo.com/

Updated too.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpWbPQiYSsvX.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] openttd + naev

[Pascal Bleser]

On 2012-04-21 12:35:35 (+0200), Eric Schirra e...@schirra.net wrote:
 bei 64bit fehlen die aktuellen Paketversionen openttd und naev.
 Die openttd-data und die naev-data sind aktueller als die anderen beiden.
 Kann das bitte jemand korrigieren?

Beide Pakete sind im games Repository auf build.opensuse.org,
und nicht bei Packman :)

Entweder einen Bug im SUSE Bugzilla aufmachen, oder folgende
Personen direkt ansprechen:
* für naev: David Buck db...@novell.com
* für openttd: Marcel Gmür s...@ammler.ch

Beide Pakete sind lauf Build-Server aber auf dem neusten Stand.

mfg,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgprWfy4pAjSx.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] openttd + naev

[Pascal Bleser]

On 2012-04-21 16:23:12 (+0200), Eric Schirra e...@schirra.net wrote:
 Am 21.04.2012 16:17, schrieb Pascal Bleser:
  On 2012-04-21 12:35:35 (+0200), Eric Schirra e...@schirra.net wrote:
  bei 64bit fehlen die aktuellen Paketversionen openttd und naev.
  Die openttd-data und die naev-data sind aktueller als die anderen beiden.
  Kann das bitte jemand korrigieren?

  Beide Pakete sind im games Repository auf build.opensuse.org,
  und nicht bei Packman :)

 Oh. Sorry. Natürlich.
 Wie komme ich jetzt auf Packaman...

Kann sein dass wir diese Pakete früher mal in Packman hatten,
aber seitdem es das Games Repository auf build.o.o gibt, ist es
dort besser angelegt (mehr Leute die mitmachen können ;)).

mfg,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp4EFM3ekTPU.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman

[Pascal Bleser]

On 2012-04-18 20:46:59 (+0300), Sagi Ben-Akiva sagi...@gmail.com wrote:
 What about trac ?
 http://trac.edgewall.org/
 It is an open source project, it also allows a lot of customization, it has
 alot of plugins http://trac-hacks.org/

Really annoying to use in practice from my experience, and
annoying to set up too.
Trac is pretty useful as a web frontend to a SVN repository, or
if you need to combine a repo, a wiki and possibly a tracker
(although Redmine is nice too), but in this case, just for
bugtracking, I find Trac to be too much of an annoyance.

Bugzilla just needs CGI and a whole bunch of Perl modules (but
those are all in devel:languages:perl, or easily installable
with cpan), and JIRA just needs a JVM (and ideally also a recent
jsvc to run on port 80/443 and do privilege dropping).

[...]

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpZbBf2kAtWY.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman

[Pascal Bleser]

On 2012-04-19 01:01:40 (+0200), Philipp Seiler p.sei...@linuxmail.org wrote:
 On Thu, 19 Apr 2012 00:00:28 +0200
 Manfred Tremmel manf...@links2linux.de wrote:

  Am Dienstag, 17. April 2012, 17:49:46 schrieb Pascal Bleser:

   I did a quick set up of an instance of JIRA and one of Bugzilla:
   - Bugzilla: http://pmbs.links2linux.org:/
   - JIRA: http://pmbs.links2linux.org:/

  I don't dislike JIRA, but a proprietary system for a free and open 
  system like openSUSE is a total no-go for me.

 /signed

 And with bugzilla we're closer to the SUSE maintainance process.

Which means... what ?
That we have the same workflow for issues for Packman than for
SUSE maintenance ?
How is that relevant in any way ?
(and we can have the same in JIRA, btw)

Or that we have the same ugly and overly complex user interface
as the bugzilla at Novell ? (actually we won't because we won't
have the dozen additional custom fields and extensions that the
Novell bugzilla has)

If you believe the Novell/SUSE bugzilla is a cool thing, please
look at the ton of threads and complaints about it over the
years on the opensuse lists.

Our needs are quite simple, we don't need complex workflows,
we don't need a lot of fields nor customization, which also
means that bugzilla still qualifies as an option.

Ultimately, I personally believe the distinguishing factor
should probably be user-friendliness:
* how easy is it to register an account
* how easy and clear is the user interface to perform common
  actions

IMHO, JIRA is better on those points, but maybe that's just me
:)

[...]

  My vote, bugzilla.

 My vote, bugzilla.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp1DtScMWUsu.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] live vs live555 and redland-bindings-1.0.14

[Pascal Bleser]

On 2012-04-17 12:23:36 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 Are not live and live555 the same package? Why we have it twice?

Yeah, I packaged live555 by taking it over from dimstar's vlc
repo for vlc 2.0 and didn't notice that we had it already as
live.
I'm switching things over to live555-devel instead of live, and
will remove our package live (and keep live555) instead, as
live555 is much more up-to-date.

 And what the purpose of redland-bindings-1.0.14 for Tumbleweed??

Fixes the broken python-redland that is currently in Tumbleweed,
and which prevented the build of some packages (most notably
OpenOctaveMidi) because it was pulled in as some transitive
dependency.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpw8di0JKGKj.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] live vs live555 and redland-bindings-1.0.14

[Pascal Bleser]

On 2012-04-17 14:04:09 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 17 April 2012 13:48, Pascal Bleser pascal.ble...@opensuse.org wrote:
  And what the purpose of redland-bindings-1.0.14 for Tumbleweed??

  Fixes the broken python-redland that is currently in Tumbleweed,
  and which prevented the build of some packages (most notably
  OpenOctaveMidi) because it was pulled in as some transitive
  dependency.

 I see, redland-bindings should be included in Tumbleweed. Does Greg know?

It is, but it is some awkward combination:
* redland itself comes through a _link from some KDE repo
* redland-bindings (which python-redland spawns from) comes
  through layering (openSUSE:12.1)

$ osc ls openSUSE:Tumbleweed redland
_link
# - KDE:Release:48 redland (a5676e767421fd689dc628e5d6d2f273)
baselibs.conf
redland-1.0.15.tar.gz
[...]

$ osc ls -b openSUSE:Tumbleweed redland
standard/i586
libredland-devel-1.0.15-2.1.i586.rpm
libredland0-1.0.15-2.1.i586.rpm
[...]

And the prj meta of openSUSE:Tumbleweed says:
[...]
  repository rebuild=direct name=standard
  path repository=standard project=openSUSE:12.1/
[...]

$ osc ls openSUSE:12.1 redland-bindings
redland-bindings-1.0.13.1.tar.gz
[...]

The result is that python-redland (and the other packages that
spawn from redland-bindings) have a hard
Requires: libredland0 = 1.0.14
which is actually needed (I did it so, on purpose, after
experimenting a few options for redland-bindings a while ago
;)).
Problem is that as redland is oddly punched into Tumbleweed from
a KDE repo and with redland-bindings coming from 12.1, it just
doesn't match but the failure only shows up at runtime: as soon
as something requires python-redland, even as a transitive
dependency, as it is the case for some packages on Packman, the
build breaks as unresolvable because Tumbleweed doesn't have
libredland0=1.0.14 but libredland0=1.0.15

There is always a specific (well, one or two) upstream versions
of redland-bindings that fit a specific version of redland.
AFACS, redland 1.0.15 requires having redland-bindings-1.0.13*

Haven't told Greg about it yet, putting him in CC as well as the
other (listed) maintainers of openSUSE:Tumblweed.

Greg  all: I did an SR of redland-bindings to
openSUSE:Tumbleweed, which will fix the issue: 114198

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgplPctBCrqqI.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Bugtracker for Packman

[Pascal Bleser]

Something I wished for since several years, a bugtracker for
Packman, in order to be able to handle bugs and todos a lot
better than just having a mailing-list where, frankly, I miss at
least half the issues and where it is a bit more difficult to
assign things to people and keep track of what's to do and
what's done. Well, in essence, bugtrackers have been invented
for that purpose.

I did a quick set up of an instance of JIRA and one of Bugzilla:
- Bugzilla: http://pmbs.links2linux.org:/
- JIRA: http://pmbs.links2linux.org:/

Note that while JIRA is a proprietary system, it is free for
open source projects (I still have to request an open source
license if we chose to use JIRA though). It is used by some
large FOSS projects around the globe (because it's probably the
best bugtracker out there), e.g. all the apache.org projects.

Have a look, and please give me opinions, then I'll finalize and
will look for a proper place to host it (pmbs.links2linux.org is
already under pretty heavy load all the time as it runs the OBS
scheduler). I'll prolly put it on opensu.se instead.

Note that for both, you have to create users, which you can on
your own without the need for an admin to step in. It is not
connected to any SSO such as Novell's, which is both good and
bad, but nothing we can change anyway as it is not accessible
outside opensuse.org (well, SUSE and Novell operating centers,
actually). Yeah, a more global opensuse.org identity management
would be sweet... sigh.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp3srI5PIXot.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bugtracker for Packman

[Pascal Bleser]

On 2012-04-17 21:46:34 (+0200), Mariusz Fik fisi...@jabster.pl wrote:
 Dnia wtorek, 17 kwietnia 2012 17:49:46 Pascal Bleser pisze:
  Something I wished for since several years, a bugtracker for
  Packman, in order to be able to handle bugs and todos a lot
  better than just having a mailing-list where, frankly, I miss at
  least half the issues and where it is a bit more difficult to
  assign things to people and keep track of what's to do and
  what's done. Well, in essence, bugtrackers have been invented
  for that purpose.

  I did a quick set up of an instance of JIRA and one of Bugzilla:
  - Bugzilla: http://pmbs.links2linux.org:/
  - JIRA: http://pmbs.links2linux.org:/

[...]

 Jira has nice option for dashboard customization. It's really neat ;)
 After login we can see in 'one-shoot' what is going on with our bugs, about 
 changes in roadmaps, votes, comments, etc. I really like it.
 If field customization for bug entry is possible (I bet it is) I vote for 
 jira 
 as our bts.

Yes, JIRA allows for almost any sort of customization.
In a way, JIRA is overkill for our needs, as we only have one
product (packman), and only a very few fields anyway.
But still, it's quite powerful and convenient to use in my
experience.

The one feature which might be useful is for JIRA or Bugzilla to
have a field that is filled from the list of packages that exist
in our OBS instance, but that would require implementing a
plugin etc... -- no time for that right now.
A plain text field should be good enough anyway :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpMNNNHQhzCD.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] pulseaudio-equalizer (Project Multimedia) SLE Target?

[Pascal Bleser]

On 2012-04-16 08:34:21 (-0500), Malcolm malcolm_le...@bellsouth.net wrote:
 Hi
 Is it possible to add SLE 11 SP2 as a build repository for the above
 package?

 The SWH LADSPA plugins have already been built, so this is the only
 dependency outside of the normaly available files.

I moved it from Multimedia to Essentials, through SR 185, there
we have SLE as build target too. I'm going to see where it
builds and where not (prolly won't on SLE 11 (SP0)).

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp3FsrL38IDS.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] more dependecy breakage while doing zypper dup

[Pascal Bleser]

On 2012-04-15 09:11:07 (+0200), Mathias Homann ad...@eregion.de wrote:
 Problem: libavcodec53-32bit-0.10.2-2.2.x86_64 requires libx264.so.122, but
 this requirement cannot be provided
   uninstallable providers:
 libx264-122-0.122svn20120414-1.1.i586[packman.inode.at-suse]
  Solution 1: keep obsolete libavcodec53-32bit-0.10.2-2.1.x86_64
  Solution 2: install libx264-122-0.122svn20120414-1.1.i586 despite the
 inferior architecture
  Solution 3: break libavcodec53-32bit by ignoring some of its dependencies

Hmm... seems we're missing libx264-32bit then.
[...]

Actually, the package does have a baselibs.conf, but it is not
up-to-date and does not match any of the packages.

I fixed this by changing the content of baselibs.conf from
libx264-120
to
libx264-122

Always bugged me that there was no validation check in the build
about whether baselibs actually matches something or not..
grmbl..

Well, should be fixed as soon as the packages are built, in the
repositories and synched with our mirrors (half a day at most,
normally).

Thanks for reporting, and sorry for the bug.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpHYtqAHCCR2.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] more dependecy breakage while doing zypper dup

[Pascal Bleser]

On 2012-04-15 14:32:03 (+0200), Erwin Lam erwin...@dds.nl wrote:
 On Sun, 15 Apr 2012 11:39:30 +0200, Pascal Bleser
 pascal.ble...@opensuse.org wrote:
[...]
 avidemux also depends on libx264-120 and needs to be recompiled because
 this library is no longer available in the Packman repository.

That's odd, OBS should have rebuilt on its own...
I manually triggered a rebuild, let's see whether that helps.
Our build servers are pretty busy atm rebuilding everything that
has to do with x264, could take a few hours.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpOEsUZV2Fwx.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Live555 build?

[Pascal Bleser]

On 2012-04-16 00:39:10 (+0930), Rodney Baker rodney.ba...@iinet.net.au wrote:
 On Mon, 16 Apr 2012 00:28:46 Pascal Bleser wrote:
  On 2012-04-15 23:27:43 (+0930), Rodney Baker rodney.ba...@iinet.net.au 
 wrote:
   I note that live555-devel version 2012.02.04-1.1 is available in packman
   but not the main live555 package. Can this be addressed please?

  There is none because live555-devel consists solely of headers
  and a static library, hence not requiring anything at runtime.

  Did you run into a package that requires live555 at runtime ?

  cheers

 Thanks for your prompt response, Pascal.

 No, unless you want to directly use the live555 tools themselves. It is also 
 optional for mplayer and ffmpeg and I'd like to be able to build them with 
 live555 support. The current devel package conflicts with the full build 
 package currently installed (2010.something) and yast wants to uninstall it 
 to 
 install the current devel package.

 If that is what is supposed to happen then fair enough. It sems different to 
 the usual way of having the main application/library packages and then a -
 devel package with the header files required for compiling other apps against 
 it (assuming shared libs are built). 

 Maybe only this devel package is needed for compiling mplayer and ffmpeg with 
 live555 support?

Ouch, I see, the package has a manual install routine, which is
why none of those tools or the shlibs show up anywhere in the
file list.

I'll have a look at the package.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpYVT8j8teXj.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg is missing the --enable-x11grab

[Pascal Bleser]

On 2012-04-14 12:29:37 (+0200), Bruno Friedmann br...@ioda-net.ch wrote:

 From some times now (several months) the ffmpeg build is missing the 
 --enable-x11grab 

 That avoid the fact to use ffmpeg as recorder for screencast.
 Could be it re-enable

It is enabled in the call to configure, so there must be another
reason for it to be disabled.

The configure log even states this:
---8-
Enabled indevs:
alsalavfi   v4l
dv1394  libdc1394   v4l2
fbdev   oss x11_grab_device
jack
---8-

libavdevice/x11grab.o gets linked into the libraries too.

What's not working, exactly?
Error message?

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpw4UiCUKP91.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] VLC 2.0

[Pascal Bleser]

On 2012-04-10 09:42:09 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 10 April 2012 05:39, rlee rleev...@gmail.com wrote:
  My question is it possible to repackage VLC2.0 so that when one updates
  they'll get the vlc-aout-pulse along with it instead of having to do this
  separately?

 The package is fine. It's the repo that's broken:
 http://lists.links2linux.de/pipermail/packman/2011-November/010441.html

The metadata of the repositories is (re-)created separately from
our OBS instance on the public file server, which is a Debian
with some version of createrepo.

I wonder whether that version of createrepo is too old or
whether we have to apply additional openSUSE specific patches.

The former seems quite likely already, as openSUSE 12.1 ships
createrepo 0.9.8, and our server has 0.4.9.

Marc, could you please have a look at upgrading createrepo to
something more recent?

As build.o.o is down at the moment (or at least having heavy
hiccups), I can't check whether we apply patches to it right
now.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpeQbZbVt1v8.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] vlc 2.0

[Pascal Bleser]

JFYI, been working on vlc 2.0 the past few days.
I obviously started from dimstar's spec file but made a few
adjustments to build properly on all our distros in Essential,
and also enabled libtar support.

Hence I had to package a few things only for SLE_11, SLE-11-SP2,
and sometimes for Evergreen_11.1 or 11.2 in order to have all
the dependencies (those packages are named libxxx-for-sle or
libxxx-for-older-than-11.4, etc... in Essentials).

vlc = 2.0 won't build for SLE_11 though, as it requires qt4 =
4.6, but I'll keep vlc 1.1.x for SLE_11 only in
Essentials/vlc-old.

phonon-backend-vlc builds just fine with vlc-2.0.1 (just needs a
few changes to the spec file as it currently requires vlc 
1.2). I can't test it myself, but I'll submit the changes and if
people notice that phonon-backend-vlc is broken at runtime,
I'll see what I can do, but that would essentially mean prodding
the phonon-backend-vlc upstream devs (which is going to be fun
for something that seems to be unmaintained, so let's hope it
just works.)

I've just submitted vlc 2.0.1 to replace vlc 1.1.x in
Essentials/vlc.

Please report issues at upstream first, as this is a fairly
standard build of vlc with only very few patches, unless it's
clearly a packaging issue.
If you don't know whether it's a packaging issue, it's not, and
do report upstream :)

I personally hate _service files with a vengeance, but I'm using
it in this case, as vlc-2.0.1.tar.xz is 17MB ^^

It is going to take some time to build, including all the
dependencies, but it should hit the mirrors in a few hours (some
mirrors pull every hour, some only every four hours), or be
available by tomorrow at worst.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpxxZdw1gApj.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] vlc 2.0

[Pascal Bleser]

On 2012-04-05 14:06:12 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 5 April 2012 08:16, Pascal Bleser pascal.ble...@opensuse.org wrote:
  Hence I had to package a few things only for SLE_11, SLE-11-SP2,
  and sometimes for Evergreen_11.1 or 11.2 in order to have all
  the dependencies (those packages are named libxxx-for-sle or
  libxxx-for-older-than-11.4, etc... in Essentials).

 libmatroska-for-older-than-11.4, libebml-for-older-than-11.4,
 lash-for-sle and fluidsynth-for-sle were building against *every*
 version. I disabled the build to what I understood the name meant
 (older-than-11.4 includes both SLE_11 and SLE-11-SP2?) and wiped the
 binaries.

Yeah, I wrongly assumed that the meta in the branch would also
be transferred through SRs, but they don't.
Forgot to check and disable the in Essentials as well, thanks.

 Unrelated... why are we building against both SLE_11 and SLE-11-SP2?
 Every binary compiled against SLE_11 should work with SLE-11-SP2.

Does it? I mean, really? SLE-11-SP2 ships different libs and
different versions of libs so ...

-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpZj2qfZK2Ey.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] vlc 2.0

[Pascal Bleser]

On 2012-04-05 15:54:17 (+0200), Christian ch...@computersalat.de wrote:
 Am 05.04.2012 15:06, schrieb Cristian Morales Vega:
 On 5 April 2012 08:16, Pascal Bleserpascal.ble...@opensuse.org  wrote:
 Hence I had to package a few things only for SLE_11, SLE-11-SP2,
 and sometimes for Evergreen_11.1 or 11.2 in order to have all
 the dependencies (those packages are named libxxx-for-sle or
 libxxx-for-older-than-11.4, etc... in Essentials).
 libmatroska-for-older-than-11.4, libebml-for-older-than-11.4,
 lash-for-sle and fluidsynth-for-sle were building against *every*
 version. I disabled the build to what I understood the name meant
 (older-than-11.4 includes both SLE_11 and SLE-11-SP2?) and wiped the
 binaries.

 Unrelated... why are we building against both SLE_11 and SLE-11-SP2?
 Every binary compiled against SLE_11 should work with SLE-11-SP2.
 right.
 I would prefer to remove SLE-11-SP2
 and would change SLE_11 to:

 repository name=SLE_11
 path repository=standard project=openSUSE.org:SUSE:SLE-11:SP1/
 archx86_64/arch
 archi586/arch
 /repository

Henne added SLE-11-SP2. And why go with SP1 if we can go with SP2 ?

I mean, this compatibility thing is only half true: e.g. SP2
ships with Qt = 4.8, while SP0 doesn't.

I wouldn't mind, less distros to build against means less pain,
and dropping old ones even more so.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp9gV083sfKQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] vlc 2.0

[Pascal Bleser]

On 2012-04-05 16:02:30 (+0100), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 On 5 April 2012 15:45, Pascal Bleser pascal.ble...@opensuse.org wrote:
  Henne added SLE-11-SP2. And why go with SP1 if we can go with SP2 ?

 SP1 seems to be the oldest supported version. Building against it
 warranties it will work with all the supported versions of SLE-11
 (those being SP1 and SP2, but no GA).

  I mean, this compatibility thing is only half true: e.g. SP2
  ships with Qt = 4.8, while SP0 doesn't.

 Which means a binary build against SP2 perhaps will not work in SP0.
 But a binary build in SP0 will work in SP2 (if you trust Qt ABI is
 100% stable).

Yes, but there are things we can build on SP2 which we can't
build on SP1 (e.g. vlc 2.x).

I guess that the ideal setup then would be to build Essentials
against SP1, and then only build against SP2 when we can't build
against SP1.

The trouble though is that users of SP2 need to add both the
(Packman) repo for SP1 and the (Packman) repo for SP2, at least
if they want to use those additional packages (such as vlc 2.x).
Still sounds like a viable option, but IMHO experience shows
that this kind of information is very difficult to get across to
users.

Opinions?

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpAofc3ZZ6Yd.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [obs submit-request 111098] KDE:Extra/kdenlive: revoked by RedDwarf

[Pascal Bleser]

On 2012-04-02 13:55:43 (+0200), Sascha Peilicke sasc...@suse.de wrote:
 On 04/02/2012 01:25 PM, Cristian Morales Vega wrote:
  On 26 March 2012 12:51, Sascha Peilicke sasc...@suse.de wrote:
  On 03/26/2012 01:24 PM, Ismail Dönmez wrote:
  Sascha, any reason for kdenlive not going to Factory?
  No, seems like nobody submitted it yet ;-)

  libmlt is already in Factory. So either kdenlive is moved to KDE:Extra
  or submitted to Factory.
  I'm set as maintainer of kdenlive. But even if I packaged it in my
  home repo I never really used it... IMHO to go to Factory someone that
  *really* cared about it should be set as maintainer. Since Packman is
  still packaging an old version of MLT (after a month and a half of the
  0.7.8 release) I'm not sure anybody there cares either. Pascal it's
  supposed to be the maintainer, but I guess he is kind of a default
  one...

Updated to 0.7.8

  If needed I can take care of updating it and keeping it building, but
  not sure if that's up to the standards of Factory.
 let's discuss in #opensuse-kde, I'm pretty sure we want kdenlive in
 Factory, it's quite a popular app.

-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpbVh1JCL9oX.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] MLT going to KDE:Distro:Factory (and Factory?), link package?

[Pascal Bleser]

On 2012-03-17 14:04:20 (+), Cristian Morales Vega reddw...@opensuse.org 
wrote:
 saschpe decided to take the packages from my home repo to
 KDE:Distro:Factory (https://build.opensuse.org/request/show/107172,
 https://build.opensuse.org/request/show/107175). Not sure if they are
 supposed to go to Factory (saschpe?)
 The MLT package is already more updated than the Packman version.
 Should we substitute our packages? (and if kdenlive ends in Factory
 stop building it at all for 12.1)

Why not, but I'd prefer to keep building it in the Packman
repository for a while, as people are used to finding it there
:)

 Since in my home repo I don't care for anything but the latest release
 and Factory they fail to build even for 11.4, but that should be
 easily fixable.

Yes, we'd have to fix it for 11.4 for sure.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpCh9wBaDACH.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] libmms and openSUSE-12.1

[Pascal Bleser]

On 2012-03-16 13:59:16 (+0100), todd rme toddrme2...@gmail.com wrote:
 I notice that building for libmms (in Essentials) is disabled for
 openSUSE-12.1.  Could someone please enable building of this package
 on openSUSE-12.1?

 The version of libmms in Essentials has a critical improvement over
 the version shipped with openSUSE-12.1: it has a -32bit compatibility
 version (libmms0-32bit).  Without this,
 gstreamer-0_10-plugins-bad-32bit is uninstallable on openSUSE-12.1.

Enabled for all repos now. The rationale was that libmms was
shipping openSUSE since 12.1, but having a fixed one is a good
reason to re-enable, indeed :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpxHV8RgAHOV.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Audacity 2.0?

[Pascal Bleser]

On 2012-03-15 21:16:04 (+0100), Philipp Seiler p.sei...@linuxmail.org wrote:
 On Thu, 15 Mar 2012 19:59:31 +0100
 Smartysmart34 smartysmar...@web.de wrote:
  Are there any plans on packaging Audacity 2.0 for Suse 11.4/64?
  I would be as amazed as I lack technical knowledge to do it by
  myself… ;-)

 I've already packaged this and sent a submit request to Multimedia. The
 maintainers must just accept that. ;)

Done

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp7Zsi04wW6m.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] New worker

[Pascal Bleser]

Thanks to Martin Herkt, we now have an additional build host for
Packman \o/
It's an i7 with a pretty nifty setup (but going more than 4 or 6
parallel workers just results in I/O trashing, at least from our
experience -- Detlef ran extensive tests on that a while ago).

Thanks Martin, much appreciated, will definitely be put to good
use :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpouyB4qPNPy.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] Lame 3.98.4-7.1 (openSUSE 12.1/x86_64)

[Pascal Bleser]

On 2012-03-08 15:10:02 (+), trevor blight trevor.bli...@gmail.com wrote:
 Hi,

Hi Trevor

 I notice that the current version of lame has removed the libsound library:

 * Tue Nov 22 2011 pascal.ble...@opensuse.org
 - disable sndfile for IO, causes more issues than anything else (warnings
 and
   issues in several applications that use lame)

 I have attached a patch that allows use of the sndfile libs without causing
 the interface issues seen for some apps.

 (With this patch, lame normally uses libsnd but switches to the internal io
 whenever libsnd would fail, so you get the best of both worlds)

 I've attached a suitably modified spec file as well.

Sounds great! But I didn't get the patches (no attachments) :)

Could you please send them to me so I can review and apply them?

Thanks :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp4NdAPFIIMi.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS Localbuild with packages from Packman

[Pascal Bleser]

On 2012-03-06 16:03:01 (+0100), Ludwig Nussel ludwig.nus...@suse.de wrote:
 Ismail Dönmez wrote:
  Just use osc build --no-verify

 Well, that's a workaround but not the solution.
 osc just fetches the _pubkey of every involved project. Looks like
 pmbs doesn't return the key used for top level projects. That needs to
 be fixed at server side.

Like.. how? Is it an OBS bug?
If it isn't, I don't even know where to start looking, we didn't
patch anything on the key serving.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpbi7Aw4PvOp.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Application for contributing

[Pascal Bleser]

On 2012-03-05 12:14:52 (+0100), todd rme toddrme2...@gmail.com wrote:
 Hi, I am interested in helping with packman.  I don't currently plan
 on adding new packages, rather I am more interested in general cleanup
 and maintenance.  I already have experience with OBS, having
 contributed to dozens of packages in at least a half dozen projects.
 What is the process for applying for access?

Hi Todd :)

Please register an account first, here:
https://pmbs.links2linux.org/user/register_user

Then poke me by private email or on IRC (I'm yaloki) and I'll
activate it, and will give you further details then.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpG2O4S6STrO.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] osc and sslcertck

[Pascal Bleser]

With osc 0.133.90.git.1330080558-310.1, the sslcertck=0 is not
needed any more to access the Packman API.
(it's the osc package from the repo
openSUSE:Tools:Unstable/osc)

Ludwig did a bugfix in osc:
https://github.com/openSUSE/osc/commit/0f2e8e257d3f298dc034b212267bbb5ba04d2430

Could all the packagers please remove their sslcertck=0 in
~/.oscrc ?

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpYuNMDsWXvA.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Packagers: VLC 2.0, anyone?

[Pascal Bleser]

Is anyone up to take a shot at VLC 2.0 ?
If not, I'll do.
We should actually look at Dominique DimStar Leuenberger's
builds in his VLC repo first -- no point in repeating tedious
work, especially when it's as high quality as his :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpAop1OSjcFv.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Clean up PMOBS part 1: gstreamer

[Pascal Bleser]

On 2012-02-28 16:06:42 (+0100), Detlef Reichelt det...@die-mafia.de wrote:
 Hi,

 i've setup an own OBS to fix/cleanup gstreamer for PMOBS, as you can
 see (1), for every $DIST an extra version of gstreamer. Also build
 required packages only if $DIST doesn't fullfill the requires. For
 example:

 1140_libmms

 Build libmms up to 1140, 1210 and later have libmms in oss.

 If nobody have a problem with this style, i ci it to PMOBS.

I do, please don't commit those changes.
I'm not sure about a better solution yet, but that is a very
radical change that has quite a lot of consequences:

* we don't link from multimedia:libs any more, hence duplication
  of work (arguably, there are issues in that repository, I've
  tried to explain that to maintainers there),

* frozen packages rather than the latest: both options are
  fine, but we always did the latter (ideally we'd have both),

* I believe we should rather use different OBS _projects_ to do
  that, rather than those weird package names.

On the latter: what about

* Essentials-11.4 - frozen uncrippled versions of what ships with
 openSUSE 11.4 (oss)
* Essentials-12.1 - same for 12.1
* Essentials - latest, built for 11.4, 12.1 and Factory

For SLE11, I guess we only need a Essentials-SLE11 and not
build for SLE11 in Essentials, as it's going more and more out
of date.

Dunno about Tumbleweed. It's not much different from Factory,
hence only built in Essentials.

But let's please give it more thought before making changes.

Thanks on your work on this, let's try to find an optimal way.

And if people want to help out by maintaining packages, please
speak up. Would be even better if we could re-assign
maintainership across a lot more people.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpTttCoUEjJX.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] dvswitch for SUSE

[Pascal Bleser]

On 2012-02-06 11:18:42 (+), Jürgen Weigert jnwei...@gmail.com wrote:
 Hey packman team!

 I'd like to make dvswitch available for openSUSE and friends. It originates
 at debian, has not yet been packaged as RPMs.
 What is the procedure for getting an account at packman?
 I worked with the software during FOSDEM, and would like to replicate the
 setup e.g. for upcoming SUSE conferences.

Cool :)

Please register an account at https://pmbs.links2linux.org then
poke me by private email or on #packman (on freenode) with your
account name and I'll enable it.

Then, as usual, package it in your home: project there, and
submit it to the repository Multimedia (but please also poke
by email or on IRC as we don't have hermes, for me to ack it).

In your ~/.oscrc you'll have to add this:
---8---
[https://pmbs-api.links2linux.org]
aliases=packman,pm
user=YOUR_USER_NAME
pass=YOUR_PASSWORD
sslcertck=0
---8---

(yes, bypassing the SSL cert check sucks, but our certificate is
broken apparently)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpKgioADCgiE.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Build Service. SSL Error

[Pascal Bleser]

On 2012-01-18 07:52:50 (-0600), Malcolm malcolm_le...@bellsouth.net wrote:
 On Wed, 18 Jan 2012 17:17:49 +0400
 Kyrill Detinov lazy.k...@opensuse.org wrote:
  When I try to connect to server via osc I get error:
  SSL Error: sslv3 alert handshake failure
  How to fix?

 Add sslcertck=0 to your ~/.oscrc file for the moment.

Yep, specifically in the section for pmbs.links2linux.org

The reason is not that our SSL certificate is invalid, but that
recent versions of osc introduced stronger SSL peer certificate
requirements, and apparently our CAcert certificate is too weak
for that.

But we don't have a budget to buy one from Verisign, so it'll
have to do.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp6HdW1qBJzO.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] xine broken

[Pascal Bleser]

On 2012-01-08 10:16:21 (+), Cristian Morales Vega cmorv...@yahoo.es wrote:
 On 8 January 2012 01:37, Manfred Tremmel manf...@links2linux.de wrote:
  Am Samstag, 7. Januar 2012, 22:23:25 schrieb Smartysmart34:
  Am 07.01.2012 21:19, schrieb Mirco Redlingshöfer:
   A few hours ago, I experienced the same behaviour.
   Just search for updates again, and install the missing
   libxine2-codecs. After that, it should work again.
 
  Thank you, that did the trick
 
  I've switched to libxine2 within some frontend guis to enable all the
  new features like VDPAU support. The libxine2 has a Recommends entry to
  libxine2-codecs, normaly it should be installed automaticly.
 
 Packman doesn't generate any soft dependencies in the repo metadata. A
 new createrepo must be installed in the servers...
 
 http://lists.links2linux.de/pipermail/packman/2011-November/010445.html

Marc, any help needed with that ?

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpL9tUIEyD5z.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] OpenOctave Midi

[Pascal Bleser]

On 2012-01-04 15:56:14 (+0200), Yevgney pc_windows_w...@lavabit.com wrote:
 Hi, is there a Package for OpenOctave Midi?

No there isn't, unfortunately it requires a few dependencies we
don't have either right now. I'm quite a bit too busy at the
moment to have a shot at it, but maybe someone else has time.

cheers
-- 
Pascal Bleser l...@fosdem.org   http://fosdem.org/
FOSDEM 2012 ::: 4 + 5 February 2012 in Brussels, Belgium
Free and Opensource Software Developers European Meeting


pgp8qqujmXzMj.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] a2jmidid

[Pascal Bleser]

On 2011-12-30 21:30:16 (+0200), Yevgney pc_windows_w...@lavabit.com wrote:
 where is the package for A2JMIDID?

Seems it has been lost while we migrated to OBS some time ago.
I'll repackage it.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpaoqomlu3yf.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] bombono 1.2.0-1.1 (openSUSE 12.1/x86_64)

[Pascal Bleser]

On 2011-12-30 21:41:54 (+0100), Thomas Harms th...@gmx.de wrote:
 I recognized that bombono did not work after the latest update of
 ffmpeg. According to the developer this bug is already fixed.
 Please note the thread posted in the bombono forum:
 
 http://forum.bombono.org/viewtopic.php?f=1t=3402
 http://forum.bombono.org/viewtopic.php?f=1t=3402

Sorry for the late reply.

I added the patch and fixed the build.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpboLds4OUpU.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Was ist los mit PackMan?

[Pascal Bleser]

On 2011-12-28 23:19:09 (+0100), Detlef Reichelt det...@die-mafia.de wrote:
 Moin an alle,
 
 nach dreimonatiger Abwesenheit stelle ich mal wieder fest, das PackMan
 in einem desolatem Zustand ist. Keiner kümmert sich um kaputte Builds,
 jeder hühnert in den Repos rum wie er möchte und keiner muckt auf, wenn
 irgendwo etwas schief läuft!
 
 Von mir wurden einige Paket stumpf gelöscht, andere Pakete wurden
 Richtung OBS verlinkt, ohne sich um die Konsequenzen nen Kopf zu machen
 (mjpegtools-devel - libmjpegtools-devel) und so weiter
 Es gab mal Zeiten, da wurde hier in der ML besprochen, was als nächstes
 gemacht wird, und ob auch alle einverstanden sind. Jetzt macht jeder
 was er will, und zerstört die Arbeit anderer. Wer hat das Recht meine
 Pakete, zB qtractor, claws-mail und licq einfach so zu löschen, ohne
 mich zu fragen? Wer erlaubt es sich, meine Entscheidung, das ich diese
 Pakete bei PackMan baue (und das seit vielen Jahren) zu revidieren,
 ohne mit mir zu sprechen? WAS SOLL DAS?
 
 So macht es keinen Spaß mehr, seine Arbeit anderen zukommen zu lassen.
 Ich baue mir meine eigenen Pakete schon seit einiger Zeit für mich
 selber, da mir das PackMan-Repo manchmal doch zu suspekt ist.
 
 Muss das sein, oder sollten wir doch wieder das gute alte PackMan
 finden, wo wir alle zusammen gearbeitet haben, um unser Ziel zu
 erreichen?

Ja, aber wer denn?

Ich komme nur noch gerade mal dazu, die Pakete upzudaten und
hier und da mal einige zu fixen. Die Mailing-Liste zu lesen
schaffe ich schon lange nicht mehr.

Detlef, ausser dir und mir ist ja so gut wie keiner mehr da.
Soweit ich weiss kümmert sich Manfred der undankbaren Aufgabe,
ein Auge auf ffmpeg zu halten. That's it.
(Es soll auch nicht als Kritik an einzelne genommen werden, oder
erst gar nicht als Kritik, aber die Situation ist nun mal so.)

Es gibt zwar einige openSUSE-Leute die auch einen Account auf
dem Packman OBS haben und hier und da ab und zu mal etwas
machen, aber niemand der auch nur annähernd soviel abarbeitet
wie wir beide.

Wir funktionieren auch gar nicht als Team oder als Projekt,
haben wir auch noch nie gemacht. Habe schon in der Vergangenheit
mehrmals versucht, mehr Leute z.B. auf IRC zu bewegen, um dort
zeitnah Sachen besprechen zu können.
Wir sollten auf jeden Fall zusehen, dass das Packman-Projekt uns
auch überleben kann.

Meiner Meinung nach ist die einzige Lösung frisches Blut.
Wenn Detlef und ich unser momentanes Arbeitspensum nicht
reduzieren können, geht das nicht mehr. Seit Toni auf einmal
komplett verschwunden ist, sind uns ja etliche Pakete noch
zusätzlich in die Hände gefallen.

* wir brauchen einen eigenen Bugtracker, denn der
  Novell-Bugzilla ist einfach zu kompliziert, und man findet
  dort kaum die Packman zugewiesenen Bugs (landen in der Regel
  bei mir), nicht mehr Meldungen per Mailing-Liste, sondern in
  einem Bugtracker, sonst blickt keiner mehr durch

* Leute die Probleme melden, sollen *zuerst* an Upstream wenden;
  das ist aber auch ein generelles Problem mit openSUSE, alles
  wird zuerst bei openSUSE oder Packman gemeldet, statt Upstream
  erst mal zu fragen (dort ist auch fast immer das Problem, und
  nicht im Paket)

* mehr Pakete im OBS und in Packman verlinkt heisst auch, dass
  sich mehr Leute drum kümmern können und dass mehr
  Applikationen, die nicht unbedingt in Packman sein müssen, auf
  build.o.o gepflegt werden können; es bedeutet prinzipiell und
  im Schnitt auch weniger Probleme für Benutzer bzgl Versionen
  in Repositories auf build.o.o und in Packman. Ich gebe dort
  sehr gerne meine Pakete ab, aber es muss natürlich
  abgesprochen sein, keine Frage, einfach löschen oder verlinken
  ohne den Maintainer zu fragen geht nicht

* wir müssen einen Hilferuf publizieren, wir brauchen einfach
  mehr Packager, die auch mehr Zeit investieren können als nur
  2-3 Pakete zu pflegen

* Deutsch - Englisch, sonst schränken wir die Liste der
  Kandidaten schonmal stark ein ;)

Wenn wir nicht jetzt die Kurve kriegen und aus Packman mehr
Projekt machen, ist es meiner Meinung nach spätestens in
einigen Monaten tot.

mfg,
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpPRJozxVsUj.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Tumbleweed: avformat_close_input needed by mlt missing from libavformat53

[Pascal Bleser]

On 2012-01-01 17:17:06 (+0100), Martin Rehn martinr...@gmx.com wrote:
 The mlt framework (Packman version 0.7.6-1.5) requires the function
 avformat_close_input() to be found in libavformat.so.53. This is
 missing from the package libavformat53 (Packman version 0.9-1.3).
 
 Error message from running kdenlive, which uses mlt:
 
 mlt_repository_init: failed to dlopen /usr/lib64/mlt/libmltavformat.so
   (/usr/lib64/libavfilter.so.2: symbol avformat_close_input, version
 LIBAVFORMAT_53 not defined
  in file libavformat.so.53 with link time reference)
 
 The missing function seems to have been added quite recently,
 deprecating the older av_close_input_file():
 
 http://permalink.gmane.org/gmane.comp.video.libav.scm/3684
 
 I suppose updating ffmpeg might be the easiest fix?

I'm baffled that mlt builds in the first place, because the
compilation or linking stage should have noticed that that
function is not available in the ffmpeg it builds against...

Well, mlt doesn't even use that function (avformat_close_input),
but uses av_close_input_file() instead.

Manfred, any idea what happens in ffmpeg there? oO

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpHgSvR91YQ7.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] pmount for openSUSE 12.1

[Pascal Bleser]

On 2011-12-02 17:26:23 (-0500), Patrick Shanahan ptilopt...@gmail.com wrote:
 pmount-0.9.23-2.6 
 
 on packman_tumbleweed,
   http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials
 
 requires hal.
 But hal is not available for 12.1, no longer used.  

Upgraded to 0.9.99-alpha, and fixed for 12.1 (and tumbleweed).

Thanks for letting me know :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpx0mtHVDNu2.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] openSUSE 12.1 in our OBS

[Pascal Bleser]

JFYI: I've just added openSUSE:12.1:Update to our build service
instance (it's actually RC1).

I'm still trying to find out how to prioritize builds for 12.1
first -- if I do, I'll configure our OBS to do so.

cheers

-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp949GhFHBBQ.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Build Service upgrade

[Pascal Bleser]

JFYI, I just upgraded our build service on pmbs from 2.1.10 to
2.1.11 because several packages that linked to build.o.o failed
with unknown attribute: lsrcmd5 -- hopefully that'll fix it.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgp4eQORGvzBk.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] LiVES 1.4.2-1.pm.1.1 (openSUSE 11.4/x86_64)

[Pascal Bleser]

On 2011-06-08 14:27:28 (+0200), Ulrich Fieseler fiese...@uni-wuppertal.de 
wrote:
 Hi there!

Hallo Urlich

 Any chance we are going to see an update of the LiVES package that would
 allow me to update the mjpegtools package to version 2.0.0-1.pm.1.1 (and
 afterwards transcode and cinelerra to the most recent versions)?

Sorry about that, actually we packaged 1.4.2 but had a stupid
little thing missing and the build was failing.

Works now, 1.4.2 will be in our repos and mirrors in = 4 hours.

Sorry again.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpp2EaHrF1mp.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Puddletag 0.10.6

[Pascal Bleser]

On 2011-06-07 20:43:21 (+0200), Jeremy Meunier jeremy.meun...@gmail.com wrote:
 Hi Pascal,
 Puddletag software 0.10.6 has been released since yesterday.
 Could you please update links on Packman repositories ?

Hi Jeremy. Done, thanks for prodding :)

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpGZXtQ5oMGC.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] confusion of rpm release numbers

[Pascal Bleser]

On 2011-05-31 21:36:47 (+0200), Norbert Meyer norbert.meye...@t-online.de 
wrote:
 Hallo,
 
 some rpm release numbers would be downgraded.
 example:
 -rw-r--r--  1 1 1 7458 2011-03-11 
 05:40 
 ./packman/suse/openSUSE_11.3/Extra/i586/dhcpdetector-1.0b-1.pm.1.1.i586.rpm
 -rw-r--r--  1 1 1 6510 2010-12-05 
 01:45 
 ./packman/suse/openSUSE_11.3/Extra/i586/dhcpdetector-1.0b-1.pm.2.1.i586.rpm
 
 The new rpm has a lower release number (and the same version).
 Is it a mistake?

Hmm yeah, but we don't have complete control over those
release numbers, as part of it (what's behind the .pm.) is
managed automatically by the OBS.

 Some rpms changed the release number from 0.pm.x.y to x.z.
 example:
 ./packman/suse/openSUSE_11.3/Extra/i586/libgdal1-debugsource-1.8.0-1.pm.1.17.i586.rpm
  
 and 
 ./packman/suse/openSUSE_11.3/Extra/i586/libgdal1-debugsource-1.8.0-1.19.i586.rpm
 Is it a mistake?

Yes, that was my bad, I forgot to apply a patch after our last
OBS upgrade. Fixed now.

cheers
-- 
  -o) Pascal Bleser
  /\\ http://opensuse.org -- we haz green
 _\_v http://fosdem.org   -- we haz conf


pgpCuPxenzCnO.pgp
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman