Django 1.5 was released about two days ago. I'd like to push a build to
rawhide, but I assume, that will break many dependent packages.
The plan is, to delay the push, until other packages are fixed, or to
push in about 14 days.
I have a scratch-build build ready, one might to try, it should install
cleanly e.g. on Fedora 18.
Matthias Runge <mrunge(a)matthias-runge.de>
due to the Enrico Scholz saga, I realized that we have 4 packages in Rawhide
which BuildRequire dietlibc:
There are 2 things that strike me as broken there:
1. As far as I can tell, those packages are STATICALLY linked against
dietlibc. Yet there is no dietlibc-static subpackage, and apparently the
static library is in the main package (not even -devel!). There are also
dietlibc-devel and dietlibc-header subpackages, but nothing BuildRequires or
Requires those. The dietlibc package needs to be fixed to comply to the
packaging guidelines (which also means that either Enrico lets go the devel
branch or it should be forcibly removed from him!) or retired entirely (Do
we really need a second libc in Fedora?).
2. I think those packages should not build against dietlibc at all, but just
use the system glibc. Now that Enrico let them go, can we PLEASE get those
Is it possible to use abrt as intended and still be able to get core dumps from
non-fedora binaries (e.g., my own code)? Right now, all core dumps are
redirected to abrt.
We need a way to be able to use gdb to debug core dumps.
I know we can turn off abrt entirely
but that's not acceptable!
We need a way that allows abrt to be used for fedora packages, while at the same
time allowing capturing core dumps to run gdb on for non-fedora packages.
If there is a way in the current abrt design, it is not sufficiently
# Fedora Quality Assurance Meeting
# Date: 2013-03-04
# Time: 16:00 UTC
# Location: #fedora-meeting on irc.freenode.net
It's meeting time again very soon. Crap on a stick, so soon. Note to
self: Angry Birds is not a good choice of app with which to 'test your
tablet'. Especially not the night before a meeting. For three hours solid.
This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
The current proposed agenda is included below. It's short, but I'm not
cancelling the meeting, as we have several follow-up topics and likely a
discussion on what to do with trac.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list
I have good knowledge of Java as well as JS
but not strong enough for C and C++ which is
the Core of Fedora?? Or are there other areas
where Java and JS is useful !! Please guide me!!
Thank you !!
P.S. This is my last chance for participating in GSoC
coz after this GSoC my academics will over.
-----BEGIN PGP SIGNED MESSAGE-----
I recently took over gpick package in order to include it in design
suite. Since two weeks, there aren't any response for reviewing this
package and it would be nice to hear for you.
In addition, as design team member, I would like several applications
from wishlists packaged as soon as possible because I cannot do all
stuff alone. I understood every one of us are busy with daily life,
having at least a feedback would be nice.
Graphic & Web Designer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
-----END PGP SIGNATURE-----
Hi all! (and sorry for post to sooo many lists)
As we already have a final schedule (for a three weeks now) and we're
getting closer to release windmills - I'd like to make the schedule
easy to use for everyone (and that means for me too), to be sure
it makes sense etc. And inform you about recent changes I did to schedule
,plans but also I'm going to ask you for a little assistance.
These are a few changes/or requests for your feedback:
1. from F19, schedule moved to FPGM neutral site , you can get
there from standard wiki schedule page.
Over the time, schedule got messy, some teams are even not aware what
a specific milestone means, why it's there, many times it's historical
relict and even collective memory does not work to remember what's
the reason to have it in schedule. On the other hand, I don't want
to remove anything people still relies on, based on my "common sense".
So please, take a look and let me know (some people already contacted
me and I work it in asap).
3. links in schedule
Thanks to Robyn, with her great TJ foo skillz, I'm now able to link
milestones in schedule to wiki and SOPs. Fedora QA asked for that,
I'll try to match as many as possible by myself but if you want to
link specific event to specific url, let me know.
4. future of scheduling, for F20+
For F19, we used a different way to schedule, based on the scope
of submitted features. It worked quite well from developers POV but
we completely forgot other teams and made the scheduling of theirs
tasks harder. I created a FESCo ticket , please take a look
(and comment it if you have ideas!). Also we would like to start
F20 as early as possible so the submission period should start
at F19 branch date (or shortly after) to let people propose the
ideas in advance.
5. new TJ3
And the main goal of the move, cleanups and so on is to jump on TJ3
board - I have initial port done, but a lot of changes are needed
and I'd like to start with TJ3 based schedule from a clean old one.
Btw. with any question, ping me, report ideas to schedule Trac 
and you know ;-)