# Fedora Quality Assurance Meeting
# Date: 2012-07-09
# Time: 15:00 UTC
# Location: #fedora-meeting on irc.freenode.net
Well, we've skipped meetings for the last couple of weeks as there was
nothing much to discuss, but there seem to be a few topics worth kicking
around this week, so let's get the ball rolling again.
Special call-outs to Bruno (for the 'blocker bug analysis' topic) and to
Jóhann and Luke (for the 'Bodhi 2.0 design ideas' topic) - if it would
be convenient for you folks to attend that'd be great. If none of those
folks turn out to be available, it may be a short meeting!
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.
== Proposed Agenda Topics ==
1. Anaconda new UI testing
2. Blocker bug analysis
3. Bodhi 2.0 design ideas
4. AutoQA update
5. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list
Hi to all,
my name is Robert Mayr, alias robyduck , and I'm a Fedora user
since the Core 1b release. Before that I used Redhat 7.3, but only
In January 2005 I founded the Italian Fedora community Fedora Online
 and I'm actually also in the websites group and gitmuffin.
I'm living near Milan since 2010, before I spent most time of my life
in Bolzano (South Tyrol). I have 2 daughters and the third child (a
son this time!) is coming within the next 10 days.
It would be nice to contribute to the package maintainers team, I'm in
contact with other italian members of the package-group and have just
created my first package:
You can find it as Bug 838362 , I'm searching for a sponsor now and
hope someone could help me to learn quickly all the skills, which I
know only learned through the wiki documents.
After some time procrastinating I've finally bumped STIX fonts to 1.1.0 in
This is a major update (1 years and a half work upstream IIRC)
Gone is the huge pile of files only TEX macros could beat some sense in,
the new font layout finally approaches sanity. The cons being that if
you've used the old font names in documents, you're in trouble. I've tried
to limit the breakage through fontconfig aliasing (but that only works for
apps smart enough to use fontconfig).
Please report problems (if any).
For the aforementioned reasons, I don't intend to push this update to
current and past releases.
After some procrastination time I've bumped STIX fonts to 1.1 in Rawhide.
This is a major release (1 year and a half work upstream IIRC)
The font layout and naming has been changed to something approaching
sanity, and the complexfont piles only TEX ma
When fedpkg chain-build fails with the message "Unsuccessfully waited 120:09
for GtkAda-2.24.2-1.fc18 to appear in the f18-build repo", how can I check
later whether the package has appeared yet so that I can build the next
package in the dependency chain?
Ok, I guess this topic has been brought up before, but I think some
things changed recently that would warrant seriously considering adding
a default caching name server in fedora installs.
There are at least 2 situations where it is needed, and they are common
or will be common enough.
The 2 use cases for which a properly configurable and dynamically
changeable caching DNA name server would be really useful are:
- DNSSEC verification
- Clients using VPNs into private networks.
The first case is already in the works, and the reason it needs a
caching DNS name server is the complexity of dealing with DNSSEC
verification. I won't spend time on that except for saying this effort
should be part of a unified solution.
The second case is what is really hurting me.
I have my own DNS server at home that resolves address only for my
private network, and forwards any other request.
When I connect to my employer VPN however I need to use their DNS server
to resolve their internal machines, the same happens to pretty much any
other VPN service I have used. Also I do not need to route all DNS
traffic in the VPN for all web sites, mostly for performance reasons,
but also for privacy reasons.
This could be easily solved if we have a caching DNS server that can be
dynamically change to forward DNS requests to the proper DNS server only
for the private domains they provide.
A good name caching server would forward all .redhat.com DNs request top
the DNS addresses provided by the VPN connection, all my .home addresses
to my local DNS server (provided by dhcp) and perhaps all other
addresses to a configurable 'default DNS server'.
Of course for this to work properly we need some level of integration
between Network Manager and the DNS caching server so that the dynamic
configurations can be pushed in/out when the related networks come
Simo Sorce * Red Hat, Inc * New York
Upstart has been orphaned in rawhide since 2012-04-26.
I would like to drop support for it from the initscripts package proper, but
if someone is willing to maintain upstart, I'd be glad to give you the boot
infrastrucutre bits therein in whatever form you'd like to maintain along
If you would like to pick up upstart, let me know (and pick it up in pkgdb).
Otherwise, I'll likely drop it at some point in the next couple of weeks.