Postings by Jesse Keating

Announcing the release of Fedora 13 Alpha!!

The Fedora 13 "Goddard" Alpha release is available! What's next for the
free operating system that shows off the best new technology of
tomorrow? You can see the future now at:

http://fedoraproject.org/get-prerelease?anF13a

== What is the Alpha release? ==

The Alpha release contains all the features of Fedora 13 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.

[Test-Announce] Announcing the release of Fedora 13 Alpha!!

The Fedora 13 "Goddard" Alpha release is available! What's next for the
free operating system that shows off the best new technology of
tomorrow? You can see the future now at:

http://fedoraproject.org/get-prerelease?anF13a

== What is the Alpha release? ==

The Alpha release contains all the features of Fedora 13 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.

Worthless updates

It took me all of about 2 minutes to find a worthless pending update for
Fedora 11.

https://admin.fedoraproject.org/updates/perl-Locale-Maketext-Lexicon-0.7...

No data in the bodhi ticket.

Rpm changelog says "Upstream update"

If I google for upstream and look for a changelog, I come to this:

http://cpansearch.perl.org/src/DRTECH/Locale-Maketext-Lexicon-0.79/Changes

in which the grand total of changes between what shipped with F11, and
what is in this update is:

* Locale::Maketext::Lexicon::Tie
- Removed a deprecated use of "defined %" for Perl 5.11+

* Locale::Maketext::Lexic

Feodra 13 Alpha slip by one week

Today at the go / no-go meeting[1] we decided to slip the Alpha by one
week. This slip is needed to verify blocker bug fixes and validate new
builds of software necessary to fix those bugs. We are confident that
the fixes we have are valid, however we do not have enough time to prove
them valid. We will spend the next few days doing that validation. In
the mean time builds will continue to be pushed to updates-testing for
13, and even to 13 stable, however critical path packages might not be
pushed unless they are fixing a release blocking issue.

[Fwd: I'm leaving packaging on Fedora]

-------- Forwarded Message --------
From: Zarko Pintar
To: fedora-devel-<...> at redhat dot com
Subject: I'm leaving packaging on Fedora
Date: Fri, 19 Feb 2010 07:57:05 +0100

Because of my obligations I must leave packaging on Fedora.

Please, if someone want to take my packages for further maintaining

This is the list of packages maintained by me:

me-tv
easystroke
photoprint
photoprint-borders
camcardsync
imgtarget

kind regards,

Zarko (Grof

Bogus broken deps

The dep checker script seems to have detected some bogus broken deps.
We're still tracking down the root cause, for now you can ignore the
broken deps spam.

Fedora 13 has been branched!!

That's right folks, we are now branched for Fedora 13. What does this
mean to you? Well that depends on who "you" are, here are some "you"s
that we wrote about:
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Use_Cases

The real take away here is explained at
https://fedoraproject.org/wiki/Branch_Freeze_Policy

The upshot is that if you want to get a build into Fedora 13, you gotta
build from F-13/ and you gotta put it in bodhi. The good news is that
if your package isn't critical path, it's just like any other update in
bodhi, you decide when it goes stable.

Draft wiki page to document the branch freeze

We're moments away from the CVS outage to branch F13 away from rawhide.
I've just created a wiki page that seeks to explain the branch event and
subsequent "freeze" for the remainder of the Fedora 13 development
cycle. Please take a moment to review this page and provide any
feedback you may have. I'll announce this page to devel-announce during
the CVS outage to let maintainers know how to function once the outage
is over.

https://fedoraproject.org/wiki/Branch_Freeze_Policy

Thanks!

Fedora 13 Branching (and thus freezing) tomorrow

Tomorrow (or well the day after tomorrow to some of you) we will be
branching off F-13 in CVS. This will start at 00:00 UTC on Feb 17.
After this point, when the outage ends, all builds for Fedora 13 will
happen from the F-13/ branch in CVS. All builds must go through bodhi
in order to make it into Fedora 13. When you submit your build to
bodhi, please push to testing first, as it will allow your peers to test
your update before it makes it into the Fedora 13 tree.

Unblocked orphans

There are still a few orphans which are unblocked due to dep issues.
Please somebody take ownership of these:

Unblocked orphan SDL_image
Unblocked orphan SDL_mixer
Unblocked orphan SDL_net
Unblocked orphan SDL_ttf
Unblocked orphan cowbell
Unblocked orphan ggz-gtk-client
Unblocked orphan gtk-sharp
Unblocked orphan perl-libwhisker2
Unblocked orphan python-crypto

List of deps left behind by orphan removal:

Orphan: SDL_image
CriticalMass requires SDL_image-devel = 1.2.10-1.fc13
CriticalMass requires libSDL_image-1.2.so.0
KoboDeluxe requires SDL_image-devel = 1.2.10-1.fc13
KoboDe

CVS Outage Notification - 2010-02-17 00:00 UTC

There will be a CVS outage starting at 2010-02-17 00:00 UTC, which will
last approximately 3 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2010-02-17 00:00 UTC'

Affected Services:
CVS / Source Control

Unaffected Services:
Everything else.

Reason for Outage:
The CVS server will not accept connections so that we can mass-branch for Fedora 13.

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to track
the status of this outage.

Fedora Release Engineering Meeting moved to 2100 UTC on Wed

We've moved the time / day of the release engineering meeting to
Wednesdays at 2100 UTC. I've updated the meeting page accordingly. See
ya there!

Name that Tree!

As part of no frozen rawhide, we'll have a new tree on the mirrors,
pub/fedora/linux/development/13 That's where we'll be putting things
that are tagged for the release after they get through testing. We
don't yet have a clever name for this concept yet, and we've just been
calling it "Pending".
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Tree.2FRe...

Want to help us come up with a term we could use to reference this tree?
Email away!

Fedora 13 Alpha Freeze in one week (minus one day)!

I forgot to send this out yesterday, but the Fedora 13 Alpha freeze is
this coming Tuesday.

https://fedoraproject.org/wiki/Alpha_Freeze_Policy

This time around things are going to be different and interesting.
We're in the middle of deploying No Frozen Rawhide¹ which will change
how freeze breaks are requested. The intention is to use bodhi to
submit update requests for Fedora 13. When requested for testing, these
will be published to the fedora 13 updates-testing repo where peers can
review and provide karma on your request.

No Frozen Rawhide coming soon! New paths on mirrors!

With a burst of testing last week, we confirmed that our infrastructure
should handle No Frozen Rawhide
http://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal . Feature
freeze is tomorrow, which is when we'd branch our source control, and
when we'd enact no frozen rawhide. The timing is a bit tight, so we may
have to delay a day or two in order to get this done, but the end result
would be two nightly trees being published.

/pub/fedora/linux/development/rawhide/ will become the new path of
Rawhide.

Today's Fedora Release Engineering Meeting has been moved to 2100 UTC

I have a conflict this morning and wish to move the meeting to 2200 UTC
(2pm US pacific, 5 pm US eastern). This may be a permanent move, to be
decided at the meeting.

Purging the F13 orphans

It's that time of the release cycle again, to purge the orphans before
we get to feature freeze. Any unblocked orphans will be purged by the
feature freeze. A list of unblocked orphans and the broken deps they
would cause is at the end of this email.

Taking ownership of an orphan on the devel collection will prevent them
from being blocked. Remember, it is OK to let software die. Don't view
this as a list of things that somebody should pick up if they have the
spare time.

dist-git refresh

Just an FYI that I've refreshed the repos at
pkgs.stg.fedoraproject.org . I had picked up some tips on setting up
the repos a bit better and so I've done that. Anybody with existing
clones will have to remove them and re-clone.

Fedora Release Engineering meeting summary for 2010-01-18

http://meetbot.fedoraproject.org/fedora-meeting/2010-01-18/fedora-releng...

Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2010-01-18/fedora-releng...

Log:
http://meetbot.fedoraproject.org/fedora-meeting/2010-01-18/fedora-releng...

Meeting summary
* No Frozen Rawhide (Oxf13, 18:09:00)

* dist-git (Oxf13, 18:17:16)
* repos on pkgs.stg will be refreshed today (Oxf13, 18:17:56)

* Standard Operating Procedures (Oxf13, 18:20:34)
* LINK:
https://fedoraproject.

Question about dist-cvs make targets

As I proceed to port our make system over into fedpkg, I've ran across a
couple targets that are giving me pause.

Is anybody out there making use of the following targets?

check
export
patch
unused-patches
unused-fedora-patches

If so, please reply to which one, and in what scenario you use those
targets. Thanks!

Phase 3 of dist-git project under way

Over the holiday break I coded up the framework for fedpkg, the utility
to replace Make within dist-git. I'm now ready to accept help with
developing this tool. See
https://fedoraproject.org/wiki/Dist_Git_Project#fedpkg if you would like
to help develop / test and then contact me.

dist-git help wanted: write me a regex!

The kernel module is full of changelogs that start with:

Thu Dec 17 2009 Jarod Wilson <<...> at redhat dot com> 2.6.32.1-11

of course the date, name, email and revision will change, but the format
is the same. This data is not really necessary in git, as we have all
of that already, and it makes shortlog rather useless.

parsecvs has a feature that allows one to filter out parts of log
messages, and it requires a perl regex to find the lines to strip out.
I'm no regex hacker, but I bet some of you are.

dist-git proof of concept phase 2 ready for testing

Phase two, write access with ACLs, is ready for testing. Please not
that URLs have changed since my original announcement.

git clone ssh://[fedoraaccount@]pkgs.fedoraproject.org/

will get you a cone via ssh, in which you can git pull and git push.

The repos are the same from phase1, although I've done a few commits
here and there to test things.

dist-git proof of concept phase 1 complete

In my effort to create a proof of concept for using git to manage our
package source control, I have completed what I am calling phase one,
that is taking our current dist-cvs and converting it into git format.

pkgs/rpms//devel is now the git origin/master. All release
subdirs have been turned into git branches. History back to F7, as well
as the EPEL branches have been converted, from a snapshot of the CVS
tree I took last week.

Currently I only have anonymous git:// access setup, as we play with
some options for authenticated writing.

Help wanted with dist-cvs to git conversion

I'm currently playing with a utility called parsecvs to convert our cvs
stuff into git. This utility can also translate the raw usernames that
CVS has into more useful names+email addresses that you'd typically get
out of git.