Hello,
I have no more time to support the following packages in the Fedora.
jack-audio-connection-kit -- The Jack Audio Connection Kit
klamav -- Clam Anti-Virus on the KDE Desktop
man-pages-uk -- Ukrainian man pages from the Linux Documentation Project
python-alsa -- Python binding for the ALSA library
qstat -- Real-time Game Server Status for FPS game servers
uniconvertor -- Universal vector graphics translator
--
With Best Regards,
Andy Shevchenko

Heya!
Please be aware that since the most recent systemd uploads /tmp is now
in tmpfs by default in Rawhide/F18.
For details please see this feature page:
https://fedoraproject.org/wiki/Features/tmp-on-tmpfs
If you have an explicit /tmp entry in fstab things should continue to
work the same as before. If you don't then you will now get a tmpfs on
/tmp by default.
This will most likely lead to a problem or two with software that isn't
happy about /tmp being small. We have created a tracker bug to keep
track of this:
https://bugzilla.redhat.com/show_bug.cgi?id=826015
If you have identified a bug that is triggered by /tmp being on tmpfs
now, please add it to this tracker bug!
For a bit of background on all of this and recommendations for
developers, please see:
http://0pointer.de/blog/projects/tmp.html
Thank you,
Lennart
--
Lennart Poettering - Red Hat, Inc.

Hello,
sorry to bring up the discussion again but I still have some grey areas in
my head.
According to the systemd snippets [1], the new macros should be only for
NEW packages, i.e. those that never had a SysV init script.
I have a few questions:
1- Since the packages I mantain build on RHEL5+ and Fedora 16+ (and have
for a long time), can I assume these macros in the spec file is optional?
If that's the case, what should I do with the bugs opened?
2- What's the status of the back-port of those macros to F16/F17 (with a
different expansion of course)? Is it under evaluation? Should I wait for
the resolution of this before starting to add the macros?
3- If I should start putting the macros in now in the spec files and still
keep the option to build the same package on all EPEL/Fedora supported
distributions, can I assume RHEL 7 = Fedora 18 for the various %if/%elif?
Thanks,
--Simone
[1] https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

Hi,
I currently maintains fusioninventory stack in Fedora / EPEL
fusioninventory-agent
perl-FusionInventory-Agent-Task-Deploy
perl-FusionInventory-Agent-Task-ESX
perl-FusionInventory-Agent-Task-NetDiscovery (to be EOL)
perl-FusionInventory-Agent-Task-NetInventory (new in F18, to be EOL)
perl-FusionInventory-Agent-Task-OcsDeploy (EOL in f17)
perl-FusionInventory-Agent-Task-SNMPQuery (EOL in f18)
Missing (new) package
perl-FusionInventory-Agent-Task-Network
(which replace Task-NetDiscovery and Task-NetInventory)
Because of lack of time (new job), lack of interest (I don't use it
anymore) and lack of understandind with upstream, this stack need a new
maintainer.
I will also accept a co-maintainer, to work with (for some time)
Else, I plan to orphan this stack and ask to remove packages from
repositories
Remi.

I have had no success whatsoever getting DirectFB to run under F17 as a regular user on my HP laptop.
# yum list DirectFB
Installed Packages
directfb.x86_64 1.5.3-7.fc17
@updates
I have discussed the problems on the DirectFB mailing list and they direct me back to the distro.
When trying to run any DirectFB command as a regular user I get permission errors like this:
$ dfbinfo
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.5.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2010 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2012-05-19 15:35)
(*) Direct/Memcpy: Using Generic 64bit memcpy()
(!) DirectFB/core/vt: Error opening `/dev/tty1'!
--> Permission denied
(!) DirectFB/Core: Could not initialize 'system_core' core!
--> A general initialization error occured
(#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured
Even when I go and change the permissions on /dev/ttyX and /dev/fb/0 and then put those into udev rules then I still get
an error about MEDIUMRAW mode.
I am able to run some DirectFB commands as root but that is no good for creating app for general user.
Can anyone, developer, packager, shed some light on why DirectFB will not run on F17 as a regular user?
Thank you.
.

Hi there,
I'm currently messing with xine-ui updates (sync with upstream 0.99.7,
epel6 build, split out xine-check). There were some plans in the past to
move all of xine to rpmfusion and, possibly, build more xine packages
from the same spec.
Is there any new development in this respect?
Michael

The 389 Project team is pleased to announce the release of
389-ds-base-1.2.11.12 for Testing. This release includes support for
POSIX attributes in Windows Sync, several bug fixes, and cleanup of
various issues found by valgrind and Coverity. The 389 team would like
to thank Carsten Grzemba for contributing his POSIX Windows Sync plugin
to the project.
The new packages and versions are:
389-ds-base 1.2.11.12
NOTE: 1.2.11 will not be available for Fedora 16 or earlier, nor for EL6
or earlier - 1.2.11 will only be available for Fedora 17 and later. We
are trying to stabilize current, stable releases - upgrades to 1.2.11
will disrupt stability.
Installation
yum install 389-ds --enablerepo=updates-testing
# or for EPEL
yum install 389-ds --enablerepo=epel-testing
setup-ds-admin.pl
Upgrade
yum upgrade 389-ds-base --enablerepo=updates-testing
# or for EPEL
yum upgrade 389-ds-base --enablerepo=epel-testing
setup-ds-admin.pl -u
How to Give Feedback
The best way to provide feedback is via the Fedora Update system.
Go to https://admin.fedoraproject.org/updates
In the Search box in the upper right hand corner, type in the name
of the package
In the list, find the version and release you are using (if you're
not sure, use rpm -qi <package name> on your system) and click on the
release
On the page for the update, scroll down to "Add a comment" and
provide your input
Or just send us an email to 389-users(a)lists.fedoraproject.org
Reporting Bugs
If you find a bug, or would like to see a new feature, use the 389 Trac
- https://fedorahosted.org/389
More Information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce