I just had to setup a new machine, and new ssh keys.
I chose my new id_rsa.pub to upload.
But I get:
git push --verbose
Pushing to ssh://email@example.com/mercurial
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
the current xine-lib maintainer speaking. :-)
The Xine project:
has recently released a new major version, version 1.2.0.
Unfortunately, among the list of changes:
there are these new "features":
* Use libavutil-provided implementations for CRC, SHA1 and BASE64 algorithms,
this makes use of libavutil even outside the FFmpeg decoding plugin,
but avoid duplication of algorithms between different plugins.
* Use av_mallocz() when xine_xmalloc_aligned() wouldn't be needed.
* FFmpeg is now required as an external dependency; if you want to build
xine-lib from source, please download a copy of FFmpeg from their SVN
which basically mean that xine-lib now has a global, non-optional dependency
on FFmpeg's libavutil library.
So there are 4 possible ways forward:
(a) Stick with 1.1.x forever. I don't think that's a good idea in the long
run, upstream won't be providing security fixes for the old branch forever.
(b) Package libavutil (and only libavutil) from FFmpeg in Fedora. (I don't
think libavutil, as opposed to libavcodec, is actually patent-encumbered,
though that'd also have to be checked.) The issue there is that FFmpeg
upstream obviously doesn't support this. It would need some more black
packaging magic of the kind already done in xine-lib, and more legal
auditing. I don't think I want to investigate going down that road.
(c) Bundle parts or all of libavutil with xine-lib. Yuck!!!
(d) Move the whole thing (back) to RPM Fusion (where it originally was, before
we started needing xine-lib for Amarok and Phonon, which both no longer
use it). It would go to the Free section, of course.
My proposal is to go with (d).
The following packages currently depend on xine-lib:
* (k9copy – already in RPM Fusion, not affected)
* kaffeine (my package, the reason why I maintain xine-lib in the first place)
These packages would have to move to RPM Fusion along with xine-lib.
In Kaffeine's case, upstream is switching from xine-lib to MPlayer in their git
repository, so it will likely have to move to RPM Fusion sooner or later
anyway. This means the affected packages are basically *xine*.
So my plan is to retire (for my packages, resp. have the respective maintainer
retire) the listed packages in Fedora for Fedora ≥ 17 and get (or have the
respective maintainer get) them into RPM Fusion Free instead. (I'd take care
of xine-lib and kaffeine myself, I hope the maintainers of the other packages
will take care of them.)
Hey, folks. It's that time again - time to start thinking about Test
Days for Fedora 18.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization, or any combination of the
two. To propose a Test Day, just file a ticket in QA trac - full details
are at https://fedoraproject.org/wiki/QA/Test_Days/Create . For
instructions on hosting a Test Day, see
You can see the schedule at
https://fedoraproject.org/wiki/QA/Fedora_18_test_days . There are many
slots open right now, with the earliest on 2012-08-09 and the latest
2012-11-01. Consider the development schedule, though, in deciding when
you want to run your Test Day - for some topics you may want to avoid
the time before the Alpha release or the time after the feature freeze
or the Final freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any other member of the QA team on test@ or in
#fedora-qa on IRC. Thanks!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list
The old Fedora, heavily patched OpenBSD nc package was just
obsoleted by the nmap ncat implementation, available as the
nmap-ncat subpackage. Those are mostly compatible and this
change shouldn't cause much headache but please check your
netcat dependant scripts or apps.
Related bug: #226187
Thanks to Michal Hlavinka for this.
Unfortunately, I'm no longer in a position to maintain the projectM
packages (libprojectM, libprojectM-qt, projectM-jack,
projectM-libvisual, and projectM-pulseaudio), so I will need to orphan
these. If anyone would like to pick these up, feel free to come to me
with questions, or help.
2011-06-23 : FTBFS not responded to
2010-06-30 : -static packaging bug not responded to
Plus, release 0.89 from 20-May-2011 is available whereas Fedora contains
0.84 from 2010 ( http://sourceforge.net/projects/courier/files/cone/ ).
This looks like somebody with interest in Cone should sign up as
co-maintainer and find out what's up with the current maintainer.
Fedora release 16 (Verne) - Linux 3.1.1-2.fc16.x86_64
loadavg: 0.82 1.09 0.87
I hope someone here can help me out..
I have a new Intel DQ77MK motherboard, based on the Intel Q77 chipset.
CPU is Intel Ivy Bridge i7-3770.
I'm running the latest BIOS version (0048), and UEFI boot is enabled in the BIOS.
I've tried UEFI booting the following operating systems from burned DVDR discs:
- Fedora 16 x64 DVD.
- Fedora 17 x64 DVD.
- Redhat Enterprise Linux (RHEL) 6.3 Server DVD. (Redhat Linux is supposed to be UEFI supported per the motherboard manuals).
UEFI boot fails with all of the listed operating systems. Symptoms:
- I get the Fedora/RHEL EFI boot menu, and I let it boot with the default options.
- I get text on the screen about allocating memory pages for Linux-EFI, loading VMLINUZ, etc.
- The screen goes empty/black, there's only a cursor blinking, and nothing happens..
- The boot failed or is stuck with nothing happening. I need to reset the box.
It looks like Linux kernel doesn't get started at all.. so it could be a UEFI firmware or a bootloader problem.
I'm actually expecting this is an Intel BIOS/UEFI firmware bug,
because I've seen reports about UEFI boot problems on other Intel 7-series chipset aswell.
Does anyone know how to debug/troubleshoot UEFI boot problems?
The motherboard in question has Intel vPro/AMT, so it has SOL, so I could use a serial console,
if there's a way to use it with UEFI/bootloader before Linux is started..
Any help is welcome!
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,
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:
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:
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:
Lennart Poettering - Red Hat, Inc.