Dear all,

I've submitted an update to LCM for EL5 and EL6:

* <a href="https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el5" title="https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el5">https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el5</a>
* <a href="https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el6" title="https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el6">https://admin.fedoraproject.org/updates/lcm-0.9.2-1.el6</a>

While 0.9.2 doesn't bring any 'proffit' to Linux users, 0.9.1 does, specially:

- add --flush-interval option to periodically flush log file to disk.
- close and re-open logfile when SIGHUP is received. Should make it easier
to use lcm-logger with logrotate.

Any help validating this packages is most welcome. I did tested them
myself and I can see that one itch has been fixed for me.

NM

Hi,

I would like to make available to f17 and f16 a package I currently
own and maintain (currently only available for f18, EL5 and EL6); What
would be right procedure?

NM

Hi all,

For Reference: BZ#767649

LCM is a library for message passing and data marshaling targeted at
real time systems where high-bandwidth and low latency are critical.
It provides a publish/subscribe message passing model and a XDR-style
message specification language with bindings for applications in C,
Java and Python.

I will be maintaining this package for Fedora and Fedora EPEL (el5 and
el6).

Hi all,

I have a doubt regarding the '.so's' in devel packages... From my
understanding they go in devel packages to allow the installation of
several packages with different versioning....
Who defined this? Is this part of some standards (ex: LSB, etc) ?

Is there some written documentation about this ?

NM

If anyone can help with reviewing this 2 topics, it would be awesome,
considering that UH is on the Games SIG wishlist

- <a href="https://bugzilla.redhat.com/show_bug.cgi?id=718430" title="https://bugzilla.redhat.com/show_bug.cgi?id=718430">https://bugzilla.redhat.com/show_bug.cgi?id=718430</a>
- <a href="https://bugzilla.redhat.com/show_bug.cgi?id=744432" title="https://bugzilla.redhat.com/show_bug.cgi?id=744432">https://bugzilla.redhat.com/show_bug.cgi?id=744432</a>

Hi all,

Is there a %fdupes macro that packagers can use in %install? If not,
whats the current policy regarding using fdupes in %install? Any
recommended scriptlet or it's just a 'don't do it' policy ?

NM

One of the packages I'm submitting for Unknown Horizons support
(python-enet or pyenet) has no real version and it's just svn revision
24 (python bindings for ENet);
What would be the best way to express this in the spec file?

ex: Version: 0.0.0+svn24

Or any other? Opinions most welcome.

The FIFE[1] Engine package in Fedora in the past provided public
static and shared objects; From one of my talks with 'prock' from
upstream he stated that:

- public shared libraries are not supported by upstream and are not
used by any of the current clients;
- static blobs are not used by clients and aren't either supported;
- all that clients are expecting is the _fife.so in the python-fife
package and the respective python stuff;

During the update to 0.3.3r3 made by Tom on request to BZ757352 we
supressed the static package...

Dear all,

Following a previous thread debate about Unknown Horizons:

1) I'm available to maintain unknown-horizons (UH) in Fedora and EPEL (RHEL6);
2) For 1) to happen I would like to maintain also FIFE, which doesn't
seem to see much love for quite some time; I ask this because FIFE
flagship product is UH itself and the development of both is very
close... A FIFE release always preceeds a UH release;
3) If 1) and 2) happen, then I need to maintain also python-enet,
which provides the python bindings for ENet.

Hi all,

fedora-updates-testing as a new version of ImageMagick which is
currently not updating due to inkscape (error suggests inkscape needs
to be rebuilded against the new ImageMagik libraries.

NM

Is there anything I can help (main packaging related or triage/bug
fix) regarding GNOME in Fedora?

Hi all,

First of all, I would like to apologize for opening a new topic, but I
wasn't signed on the list, so I can't really reply to the original
thread, "Unity For Fedora (As in OpenSUSE or Arch)"[1] by Manuel
Escudero.

I would like to clarify a few things:

* Unity is not available for openSUSE and months ago I've filed a
request to nuke the GNOME:Ayatana repository. This repository only
exists for scavenging packages that might become useful.
* Unity will never become a part of openSUSE unless it uses upstream
API.