Re: Travelling
On Jun 21, 2009, at 18:35, Toshio Kuratomi a.bad...@gmail.com wrote: I'm going to be going to Brazil for FISL and a FUDCon this week. I'm not sure what my Internet situation is going to be but if anything comes up send me a message and I'll work on it once I get the message. -Toshio Same for me, but Berlin Germany. Will get on when I can. -- Jes ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Outage Notification - 2009-06-23 20:00 UTC
There will be an outage starting at 2009-06-23 20:00 UTC, which will last approximately 2 and a half hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2009-06-23 20:00 UTC' Affected Services: CVS / Source Control Unaffected Services: Buildsystem Database DNS Fedora Hosted Fedora People Fedora Talk Mail Mirror System Torrent Translation Services Websites Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/1472 Reason for Outage: Step 1 of a two step migration process for cvs (moving to different hardware). If this goes well, step 2 will come later in the week. CVS commits will continue to work during this time. Lookaside cache availability will be intermittent. If a build fails, just re-try later. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Travelling
On Mon, Jun 22, 2009 at 1:28 AM, Jesse Keatingjkeat...@j2solutions.net wrote: On Jun 21, 2009, at 18:35, Toshio Kuratomi a.bad...@gmail.com wrote: I'm going to be going to Brazil for FISL and a FUDCon this week. I'm not sure what my Internet situation is going to be but if anything comes up send me a message and I'll work on it once I get the message. -Toshio Same for me, but Berlin Germany. Will get on when I can. I am on and learnign the ropes this week. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. The Merchant of Venice ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: fedora-git-commit-mail-hook: Fix command for finding previous tag
I wrote: configs/system/fedora-git-commit-mail-hook |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 226e06441f2fab7c7c52609834e86c236910e963 Author: Todd Zullinger t...@pobox.com Date: Sun Jun 21 03:34:20 2009 + fedora-git-commit-mail-hook: Fix command for finding previous tag The spacewalk maintainers reported problems when pushing tags[1]. The root of the problem appears to be in determining the previous tag, which used 'git describe' piped to sed. The sed call is better replaced with the --abbrev=0 option to 'git describe' and should correct the problems noted by the spacewalk maintainers. This fix was made to the upstream update hook in c47e6a4[2], and was required because the format of git describe changed. It is worth noting that the upstream update hook has been completely re-worked. Email notification has been removed from the update hook[3] and implemented in the post-receive hook[4]. I think we may want to look at converting from our use of the update hook to the post-receive hook for sending commit notifications. Upstream moved the mail notification bits from the update hook to a new post-receive hook only a few weeks after Jeremy added the initial fedora-git-commit-mail-hook. So what we're running now isn't something which will receive any attention or bug fixes from upstream, unfortunately. The reasoning for upstream moving mail notification is stated in the the commit message for 46d409d: The update hook's only job is to decide is a particular update is allowed or not. It was not the right place to send out update notification e-mails from to begin with, as the final stage of updating refs can fail after this hook runs. [1] https://fedorahosted.org/fedora-infrastructure/ticket/1362 [2] http://git.kernel.org/?p=git/git.git;a=commitdiff;h=c47e6a4 [3] http://git.kernel.org/?p=git/git.git;a=commitdiff;h=46d409d [4] http://git.kernel.org/?p=git/git.git;a=commitdiff;h=4557e0d diff --git a/configs/system/fedora-git-commit-mail-hook b/configs/system/fedora-git-commit-mail-hook index 85359ca..e80a461 100644 --- a/configs/system/fedora-git-commit-mail-hook +++ b/configs/system/fedora-git-commit-mail-hook @@ -82,7 +82,7 @@ then git cat-file tag $3 | sed -n '5,$p' echo fi - prev=$(git describe $3^ | sed 's/-g.*//') + prev=$(git describe --abbrev=0 $3^) # the first tag in a repo will yield no $prev if [ -z $prev ]; then echo Changes since the dawn of time: -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The man who is a pessimist before forty-eight knows too much; the man who is an optimist after forty-eight knows too little. -- Mark Twain pgpnYMF2evOa2.pgp Description: PGP signature ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: fedora-git-commit-mail-hook: Fix command for finding previous tag
On Monday, June 22 2009, Todd Zullinger said: [snip] I think we may want to look at converting from our use of the update hook to the post-receive hook for sending commit notifications. Upstream moved the mail notification bits from the update hook to a new post-receive hook only a few weeks after Jeremy added the initial fedora-git-commit-mail-hook. So what we're running now isn't something which will receive any attention or bug fixes from upstream, unfortunately. The reasoning for upstream moving mail notification is stated in the the commit message for 46d409d: That sounds sensible. I have no problem with us changing, although I won't have the time to sit down and make it happen any time in the next couple of weeks. If someone can get to it before, I'm more than happy to look over it. Alternately, I can stick on my queue for July :) Jeremy ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
New to the group
Hello everyone, I am new to the group and would like to introduce myself. I'm employed as a systems engineer (admin/developer) in the NOC of a large hosting provider. Most of our infrastructure systems run RHEL and various open source and/or in-house applications for supporting and monitoring a large network. My coding skills are probably consistent with those of a long time systems admin and linux geek, but are not near OS Developer levels. When given the choice I code in PHP or Perl, and a number of the applications I work with at the moment are written in Ruby and Python, so I can find my way around in them as well. I've enjoyed lurking and helping in IRC and would like to get a bit more involved in the project. By joining the project I am hoping to make some worthwhile contributions and possibly get some exposure to different systems and software practices. Thanks! Chris ckrough in IRC -- Chris Krough ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
