I'm definitely checked out in the master branch:
[tgl@rh3 master]$ git push
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.13 KiB, done.
Total 6 (delta 3), reused 0 (delta 0)
d44dce3..2e73ff7 master -> master
[tgl@rh3 master]$ fedpkg build
Building postgresql-9.1.3-1.fc17 for f17-candidate
Created task: 3822862
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=3822862
Watching tasks (this may be safely interrupted)...
3822862 build (f17-candidate, /postgresql:2e73ff757cfdd20a708fc783e09ff23f3d8644e0): free
3822862 build (f17-candidate, /postgresql:2e73ff757cfdd20a708fc783e09ff23f3d8644e0): free -> open (x86-02.phx2.fedoraproject.org)
WTF? Do I need to fix this, and if so how?
regards, tom lane
Following is the list of topics that will be discussed in the FESCo
meeting tomorrow at 18:00UTC (1:00pm EST) in #fedora-meeting on
Links to all tickets below can be found at:
= Followups =
#topic #799 Issues with maintainer responsiveness (clamav)
#topic #802 F17 Features - progress at Feature Freeze
= New business =
#topic #803 Add johannbg to provenpackager explicitly to work on
#topic #806 Request for exception for iptables and ip6tables to provide
a small init script
#topic #807 static linking exception for dmtcp's mtcp_restart
#topic #810 Clarify our position on forks
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
I don't have access to edit this so I hope someone who does will.
I've noticed with several packages lately that frequently the wrong
build flags are used or appened to the ones the cmake macro sets.
Sometimes this can happen because the main cmake configuration file
forces the type to "Release" (bad!) but not always.
I've found that adding: "-DCMAKE_RELEASE_TYPE=RelWithDebinfo" often
takes care of this.
I am sending this because, we have a lot of FTBFS packages which I have
see at least one blog griping about, I accidentally fixed something that
was blocking other work (in the sense that I didn't know that other work
that I wouldn't have to do was waiting for this problem to be solved) and
I fixed something for someone that asked for help in a roundabout way.
We are all not experts in everything and it isn't a problem to ask for
help if you are stuck on something for a package. Someone else on the
devl list (or one of the programming language specific lists) may be able
to easily solve a problem that you could spend hours on without making
a lot of progress.
For those that can help, doing so is a good idea. By removing a blocker
you let someone else do work they can do on Fedora. By showing them
the resolution, they may be able to resolve similar situations when they
see them again, including cases when other developers run across the
problem. It's nice to help your fellow contributors. Fixing things makes
Fedora better for everyone.
Fedora is a feature rich Linux distribution containing the latest advancements
in open source software and I simply love Fedora.
Why does Fedora still decide to use yum? The package management system of
Fedora is still very primitive.
Here are my reasons why yum needs to go or needs *major* changes:
1) yum's interface (command line) is non-interactive. I always fail to
understand why it is
taking so long. "Setting up update process" stays for more than 1 minute at
times! (On a fairly fast PC with high speed internet connection). Atleast it
should show the user some progress as to what it is doing.
2) Quitting by CTRL-C isn't very easy. Is it?
3) On 64-bit machines, there *always* come up some issues with i686 packages
and protected multilib versions.
4) I have used Fedora for more than 5 years, I have faced "Unable to retreive
repository information repomd.xml" for like infinite times. Yes, the error
eventually gets resolved but it still comes again and again.
5) Need for autocomplete to work properly in package name argument of command
line when pressing TAB. It is painfully slow.
6) yum requires to download repository information separately for each user.
7) yum is strangely clubbed with package-cleanup,
yum-complete-transaction and I don't know what else.
These are my ramblings about yum. I know I could have filed a few of the above
as bugs and may be help to resolve them, But someone really needs to address
the bigger issue that is yum's design philosophy rather than just solve bugs in
Rather than providing me workarounds or solutions to make it work better,
Fedora needs to recognise that yum is really a huge pain to work with.
I will share one experience I had. Yesterday I did yum --enable-repo=updates
update on Fedora 16. It gave me an error stating protected multi-lib versions
of a dozen or so packages. Running package-cleanup --clean-dupes
removed 691 packages
leaving my system crippled. It removed the entire KDE and also network manager.
Now I unable to login to GNOME shell and not able to connect to any network. I
had to take backup using recovery mode before proceeding to reinstall.
I now need to reinstall my operating system. Reason : yum screwed up.
And these are the issues only regarding to the command line yum, The
GUI front-end to yum has more issues.
I do not intend to criticise any of the developers but only suggest
that yum *really* needs major changes.
Keep up the good work.
Thanks and Best Regards,
Hot dog! The Fedora 17 "Beefy Miracle" Alpha Release is available! This
release offers a preview of some of the best and meatiest free and open
source technology currently under development. Relish in a glimpse of
== What is the Alpha release? ==
The Alpha release contains all the bunderful features of Fedora 17 in a
form that anyone can help test. This testing, guided by the Fedora QA
team, helps us target and identify bugs. When these bugs are fixed, we
make a Beta release available. A Beta release is code-complete, and
bears a very strong resemblance to the third and final release. The
final release of Fedora 17 is due in early May.
Frankly, we think Fedora 17 will be the best release ever, but we know
we can't do it without your help. Please take a moment of your time to
download and try out the Alpha and make sure the things that are
important to you are working. If you find a bug, please report it --
every bug you uncover is a chance to improve the experience for millions
of Fedora users worldwide. Together, we can make Fedora a franktastic,
rock-solid distribution. (Read down to the end of this announcement for
more information on how to help.)
== Condiments ==
When we said Beefy, we weren't kidding: an a-bun-dance of condiments,
err, features, are available to help you feed your hunger for the best
in free and open source software. We take pride in our toppings, and in
our fine ingredients; Fedora 17 includes both over- and under-the-bun
improvements that show off the power and flexibility of the advancing
state of free (range) software.
Check out our menu, certain to please a variety of appetites:
* End Users *
End users will see numerous improvements in Fedora 17.
* GIMP has been updated to the long awaited 2.8 release, with an
a-bun-dant list of new features, such as the single window mode, layer
groups, and on-canvas text editing.
* Improved language and font support: A number of Lohit fonts, enabling
Indian script, have been added, as well as support for Inscript 2 for
keymapping; libpinyin increases pinyin input speed by adding predictive
* Desktops galore! Whether you like your bun covered in GNOME, KDE,
Sugar, or otherwise, we've updated it to the sauciest, tastiest version
* Systems Administrators *
Serving up hot dogs all day long? Increase your reliability and
versatility with the new enhancements to the clustering stack in Fedora
17. Load balancing and high availability improvements have been made,
allowing systems administrators to deploy Fedora in environments
requiring greater availability and clustered file systems; both Corosync
2.0 and the Pacemaker Cluster Resource Manager 1.1.7 are included. JBoss
Application Server (AS) 7 has also been added to Fedora 17; this fast,
lightweight, and modular application server allows you to run full Java
* Developers *
Developers can cook up fresh code with the updates and additions of
numerous languages in Fedora 17. Java 7, Ruby 1.9.3, and PHP 5.4 are
just some of the latest-and-greatest; we've also got updates and
additions in the Haskell platform, Erlang, and D, as well as the
addition of the Opa programming language. GCC has been updated to 4.7,
and Fedora 17 has additionally been rebuilt with this new version,
resulting in compiled code improvements.
* Virtualization *
A a-bun-dance of virtualization features are ready for consumption in
* Open vSwitch is a flexible, multi-layer software switch typically used
in virtualization environments as the network switching component in the
hypervisor, providing virtual machines their network connectivity.
* KVM improvements, including the addition of a virtualized PMU
(performance monitoring unit)for guests, and a live block copy features,
allowing an image backing a guest disk to be copied while the guest is
* Virtualization sandboxing provides a new application development
library (libvirt-sandbox) to facilitate the embedding of virtualization.
* Hot Dogs as a Service (HDaaS) *
Kidding! We couldn't resist jumping into the game with our own acronym.
Seriously, though, we have a frank-tastic variety of cloud technologies
coming in Fedora 17, including the fresh additions of some of the best
Infrastructure-as-a-Service (IaaS) platforms in free and open source
software -- Cloudstack, Eucalyptus, and OpenNebula. OpenStack gets
bumped in Fedora 17 to the Essex release, and other OpenStack features
have been added or updated as well, including Horizon and Quantum, and
the ability to use OpenStack with libguestfs and qpid.
These and many other improvements provide a wide and solid base for
future Fedora releases. This release increases the range of
possibilities for developers and helps Fedora to maintain its position
at the leading edge of free and open source technology.
Ketchup with the full list of features for Fedora 17 here:
We also have nightly composes of alternate spins available here:
== Issues and Details ==
For more information including common and known bugs, tips on how to
report bugs, and the official release schedule, please refer to the
A shorter list of common bugs can be found here:
== Contributing ==
Ever wonder how sausage is made? Yeah, we didn't want to know either.
Hot dogs, on the other hand, are glorious creations, and the Alpha
release of Beefy Miracle is yet another fine example of a long line of
solid Alpha releases. We can't do it without you, though. Bug reports
are especially helpful as we move from the hot dog factory to the
finished Beefy Miracle. If you encounter any issues, please report them!
Mustard up the confidence to contribute? Don't worry -- we don't bite!
(Except... tasty, delicious hot dogs. Mmmmmm. Hot dogs.) Fedora is a
fantastic, friendly community, and we have many ways in which you can
contribute, including Documentation, Marketing, Design, QA, Development,
To learn how to help us cook a better hot dog, visit:
Thank you, and we hope to see you in the Fedora project!
test-announce mailing list
2nd sentence reads: Note that you cannot install Fedora on UEFI-based AMD64 and Intel 64 systems from a USB flash drive, although you can use a USB flash drive to boot the Fedora installer on UEFI-based AMD64 and Intel 64 systems
This appears to say "you cannot install, but you can boot". It's quite confusing. I have used livecd-tools to create UEFI bootable LiveCD media on a USB stick and also installed it onto an Intel-64 system. So this portion of documentation appears to be incorrect. If so, I'll volunteer to file a documentation bug - however the bugzilla only has a documentation bug report version of "devel" so it's slightly unclear how to file such a doc bug report. If it's a bug.