Problem commiting to the new CVs repository for libvirt localization
by Daniel Veillard
Since the move out of elvis I have been unable to commit the updated
pot file for libvirt in the new CVS, this has been failing with various
errors on the server side:
paphio:~/i18n/libvirt -> cvs -z9 commit
cvs commit: Examining .
Can't locate Config/Simple.pm in @INC (@INC contains: /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.2/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.1/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.2/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.1/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at /usr/bin/i18n-access line 48.
BEGIN failed--compilation aborted at /usr/bin/i18n-access line 48.
**** Access allowed: veillard is in ACL for libvirt.
cvs commit: Pre-commit check failed
cvs [commit aborted]: correct above errors first!
cvs commit: saving log message in /tmp/cvsOuP4H5
paphio:~/i18n/libvirt -> cat CVS/Root
paphio:~/i18n/libvirt -> cat CVS/Repository
Seems the commit scripts on the server side have never been tested,
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
Mailman List Policy for Fedora Hosted
by Jeffrey Ollie
Well, I believe that I have most of the technical bits in place for
Mailman for Fedora Hosted. Now we just need to figure out a few
1) Who can request lists? My proposal: anyone that is listed as an
administrator in the project's group in FAS.
2) What sorts of lists can be requested? My proposal: Lists may be
reqested for discussing the use of, development of, or disseminating
other useful information about (e.g. announcement or commit lists)
projects hosted with Fedora. Lists about non-F/OSS topics or F/OSS
projects not hosted with Fedora would not be acceptable.
3) What should the policy on list names be? My proposal:
A) All list names must be prefixed with "<projectname>-".
B) All list names must be suffixed with "-list".
C) Lists may optionally have something between the prefix and suffix,
as long as it's not obviously vulgar or obscene.
For example, the following would be acceptable list names:
The purpose for the "-list" suffix is to keep lists in a separate
namespace in case we want to use <something>@fedorahosted.org for some
other purpose in the future.
The exceptions to this rule would be the default "mailman" site list
and possibly a list dedicated to discussing the Fedora Hosted service
itself (name to be determined later). FESCo or the Fedora Board could
approve other exceptions.
4) What should the policy on archives be? My proposal:
A) All lists must have public archives. The exception would be the
default "mailman" list.
B) Requests to remove a post from the archives will be denied unless
it can be shown that by *not* removing the post RedHat and/or Fedora
face a credible threat of civil or criminal liability. We'll likely
require the assistance of RH Legal to make these sorts of
determinations (hopefully they will never happen).
Meeting Log - 2008-02-28
by Ricky Zhou
15:01 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Who's Here?
15:01 < mmcgrath> So... who's here?
15:01 < ivazquez> Pong.
15:01 < gkrpan> Greg Krpan here
15:01 * f13
15:01 < f13> although going to get a snack
15:01 * jeremy waves
15:01 < mmcgrath> gkrpan: hello Greg
15:02 < gkrpan> hi Mike
15:02 * Wakko666 watches from the cheap seats.
15:02 * skvidal is here
15:03 < mmcgrath> alllrighty then, lets get started
15:03 < mmcgrath> First the tickets
15:03 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets
15:03 * nirik is also in the spectator seats.
15:03 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
15:03 < zodbot> mmcgrath: http://tinyurl.com/2hyyz6
15:03 < mmcgrath> first ticket
15:03 < mmcgrath> .421
15:03 < mmcgrath> err
15:03 < mmcgrath> .ticket 421
15:04 < zodbot> mmcgrath: #421 (Fedora Mirror Space) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/421
15:04 < mmcgrath> So the board has decided that secondary arch's are worth of official fedora mirror space. I agree.
15:04 < mmcgrath> So now we've got to find mirror space.
15:04 < mmcgrath> Some of you may have seen my call yesterday (http://mmcgrath.net/) for space.
15:05 < mmcgrath> there are a couple of wheels in motion right now but exactly what solution we're going to do is unclear.
15:05 < f13> mmcgrath: hrm, you know, all we have to do for the stuff that's not older than 3 years old is keep the old url functional, the one we did our export file on.
15:05 -!- jmbuser [n=jmbuser(a)220.127.116.11] has left #fedora-meeting ["Time to go"]
15:05 < f13> mmcgrath: we could move that content to another host and setup a redirect, and keep it off the master netapp
15:05 < mmcgrath> f13: yeah, we still have to host it somewhere though, and we don't have that much space available right this second.
15:05 < f13> mmcgrath: that could let us archive 4,5,and 6
15:05 < f13> mmcgrath: sure.
15:05 < mmcgrath> <nod>
15:05 < mmcgrath> lots of options.
15:06 < mmcgrath> I really don't think we'll get stuck not being able to put the bits up there, just a matter of finding out where the bits go :)
15:06 < f13> yeah
15:06 < mmcgrath> f13: did you happen to talk to legal about the test releases and our obligations?
15:06 < mmcgrath> I'm not really sure who's charge that is. Maybe spot?
15:06 < f13> mmcgrath: we haven't talked yet
15:06 < f13> I was going to do that today, utnil I was surpised with the need to work from home
15:06 < f13> maybe spot and I can do that tomorrow
15:07 * spot nods
15:07 -!- cebbert_ [n=cebbert@nat/redhat/x-222f1705c2f83827] has joined #fedora-meeting
15:07 < mmcgrath> cool, not a huge rush or anything. but it'd be nice to know.
15:07 < f13> yeah, it's chewing on my mind
15:08 < mmcgrath> alrighty, anyone have any questions about 421? If not we'll move on.
15:08 * glezos is here in case he's needed
15:08 < mmcgrath> .ticket 347
15:08 < zodbot> mmcgrath: #347 (Set localtime on all our servers to UTC) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/347
15:08 < mmcgrath> dgilmore: we still all set for tonight?
15:09 * mmcgrath thinks it was tonight.
15:09 < mmcgrath> https://www.redhat.com/archives/fedora-devel-announce/2008-February/msg00...
15:09 * mmcgrath thinks dgilmore might be in a meeting. We can get back to that.
15:10 < mmcgrath> .ticket 365
15:10 < zodbot> mmcgrath: #365 (mailman setup (project/hosted)) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/365
15:10 < mmcgrath> jcollie has a $dayjob meeting but this bit is basically up and ready. It really just needs a couple of people to make a test list, make sure we like it all.
15:10 < mmcgrath> then add it to the faq on how to request mailing lists
15:11 < mmcgrath> anyone have any questions / comments on that?
15:12 < ivazquez> Have we finalized on -list@ or @list.?
15:12 < mmcgrath> allrighty
15:12 < mmcgrath> going to be a short meeting I suspect.
15:12 < mmcgrath> ivazquez: afaik, no.
15:12 < ivazquez> Alright.
15:12 -!- jcollie_ [n=jcollie(a)18.104.22.168] has quit Read error: 110 (Connection timed out)
15:13 < mmcgrath> we'll need to do that though, ivazquez mind bringing it back up on the list?
15:13 < ivazquez> Sure thing.
15:13 < mmcgrath> thanks
15:13 < mmcgrath> next ticket:
15:13 < mmcgrath> .ticket 395
15:13 < zodbot> mmcgrath: #395 (Audio Streaming of Fedora Board Conference Calls) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/395
15:13 < mmcgrath> jcollie's also been working on this so we can move it to next week.
15:14 < mmcgrath> next
15:14 < mmcgrath> .ticket 398
15:14 < zodbot> mmcgrath: #398 (elfutils `monotone' (mtn) error) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/398
15:14 * mmcgrath reads up on ticket.
15:15 < ivazquez> Have we talked to the mtn devs about this?
15:15 < mmcgrath> ivazquez: seems likely that we haven't
15:15 < mmcgrath> fun #monotone is #unavailable
15:15 < mmcgrath> ivazquez: I'll make a note in the ticket about that. we can move it to next week for now and see what jcollie says.
15:16 < ivazquez> It's on oftc I think.
15:16 < mmcgrath> <nod>
15:16 < mmcgrath> alrighty, I've also had a request to bring up
15:16 < mmcgrath> .ticket 399
15:16 < ivazquez> Yup, oftc.
15:16 < zodbot> mmcgrath: #399 (Damned Lies setup change: Move cronned update-stats to a separate app server) - Fedora Infrastructure - Trac - https://fedorahosted.org/projects/fedora-infrastructure/ticket/399
15:16 < mmcgrath> glezos: whats up with that?
15:17 < glezos> Basically it's a task to reduce the load on our web servers, and to move to mysql
15:17 < mmcgrath> sounds like a win win win to me.
15:17 < glezos> move the stats update script to a different server
15:17 < glezos> The (3rd) server running the cronned script producing the stats will need to output some files in a place the web servers could access.. Not sure how to setup that, I'll need someone to help me out drive this
15:18 < mmcgrath> glezos: have you tried to convert the sqlite db's to mysql? Or would we just start with a blank mysql and re-run the stats script?
15:18 -!- jsmith-away is now known as jsmith
15:18 -!- jsmith [n=jsmith(a)22.214.171.124] has left #fedora-meeting ["Leaving"]
15:18 < glezos> mmcgrath: yeah, we can do that too in a clean environment, like described on comment #1.
15:19 < glezos> mmcgrath: I'll need a third app server with an NFS the other ones can readonly from.
15:19 < glezos> or something like that
15:19 < mmcgrath> we'll likely just run that on one of the servers that already has the environment on it.
15:19 < mmcgrath> similar to what we do for mirrormanager.
15:20 < glezos> ok
15:20 < gkrpan> what about an scp push to the remaining servers?
15:20 < mmcgrath> how much information / storage are we talking about pushing around?
15:20 < mmcgrath> both right now and this time next year?
15:20 < glezos> 3GB
15:20 < glezos> oops, wrong
15:20 < glezos> much less, sorry
15:20 < mmcgrath> 3GB, is that for dl or transifex?
15:21 < glezos> mmcgrath: we need the update script to produce the contents of http:.../POT/
15:21 < mmcgrath> how much space is that?
15:21 * glezos checking
15:21 -!- bpepple|lt [n=bpepple|(a)rrcs-70-61-160-147.central.biz.rr.com] has joined #fedora-meeting
15:21 < glezos> 600M
15:21 < mmcgrath> by tying ourselves to nfs we're pretty much committing to only hosting this information in PHX.
15:22 < mmcgrath> which is doable, but not desirable.
15:22 < mmcgrath> how often would this cron job run?
15:22 < glezos> mmcgrath: every 6-8 hours, however these files don't change often, so rsync will be fast.
15:23 < mmcgrath> k, its possible to do it with the rsync or nfs. its 600M now, ohw much will it be next year at our current growth rate?
15:23 < glezos> mmcgrath: could become up to 3 times in the next year.
15:24 -!- rsc [n=robert@fedora/rsc] has quit Read error: 54 (Connection reset by peer)
15:24 < mmcgrath> k, then we probably will just want to use an nfs store.
15:24 < mmcgrath> What time frame did you have in mind for these changes?
15:25 < glezos> mmcgrath: things work now, so I'm not in a hurry. But it will reduce the load on app1,2 a lot for ~1.5-2 hours each day
15:25 < mmcgrath> <nod>
15:25 < glezos> (or just one of them)
15:25 < mmcgrath> We can probably do that in the next month or so without issue. I'd say try to get ahold of paulobanon or yingbull for some help.
15:25 < mmcgrath> anything else on that?
15:26 < glezos> thanks (eof)
15:26 < mmcgrath> solid
15:26 < mmcgrath> Alrighty, thats all the tickets we have
15:26 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Xen2 instabilities
15:26 < mmcgrath> So I still haven't heard back from anyone on whats going on with this, I finally got an oops capture though
15:27 < mmcgrath> skvidal has been kind enough to be on call the last couple of nights so I could sleep. But it didn't crash so thats good.
15:27 < mmcgrath> we're keeping an eye on it though.
15:27 * skvidal thinks it did not crash B/C he was on call
15:27 < mmcgrath> that could very well be.
15:27 * skvidal is clearly a good luck charm
15:27 < skvidal> oh god
15:27 < mmcgrath> good luck :)
15:27 < mmcgrath> heh
15:27 < skvidal> this means I have to be on call forever
15:28 < mmcgrath> alrighty moving on....
15:28 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- FAS2
15:28 < mmcgrath> So toshio, ricky and I have been hitting FAS2 pretty hard core to strip ldap out and get it ready for a pre-beta release.
15:28 < mmcgrath> 1) we're basically back to the functionality of where we were with LDAP now.
15:28 < mmcgrath> 2) It will allow us to do a ton
15:28 < mmcgrath> and 3) its almost ready.
15:29 < mmcgrath> Expect an email over the next week to help us test.
15:29 -!- rsc [n=robert@fedora/rsc] has joined #fedora-meeting
15:29 < mmcgrath> I'm hoping to package this as well, the installation process is quite simple, even getting shell account integration.
15:29 < mmcgrath> This will be of use to more people then just Fedora.
15:29 -!- wolfy [n=lonewolf@fedora/wolfy] has joined #fedora-meeting
15:29 < mmcgrath> and thats really all I had for this week
15:29 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Open Floor
15:30 < abadger1999> 4) it's based on TG-126.96.36.199 and SA-0.4 so people need to test their apps on publictest10 so we can roll this all out concurrently :-)
15:30 < mmcgrath> what toshio said :)
15:30 < mmcgrath> anyone have anything else they'd like to talk about this meeting?
15:30 < mmcgrath> if not we'll close the meeting in 30
15:31 < mmcgrath> 10
15:31 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting Closed
15:31 < mmcgrath> thanks for coming everyone!
Fedora Needs another Primary mirror! (fwd)
by Mike McGrath
PS guys, if you know anyone who might be able to provide this stuff,
please let me know.
---------- Forwarded message ----------
Date: Wed, 27 Feb 2008 11:19:11 -0600 (CST)
From: Mike McGrath <mmcgrath(a)redhat.com>
Reply-To: A private discussion group for official mirrors of ftp.redhat.com
Subject: Fedora Needs another Primary mirror!
For secondary content. Does anyone out there have anything like the
following specs? If so please contact me.
by Mike McGrath
Does anyone happen to have a contact at MIT that could find out who runs
pgp.mit.edu and whats going on with it? Over the last few months we've
seen the site become less and less responsive and since its in the
critical path to becoming a contributor (can't sign the cla without it)
this is a real problem.
What alternative options do we have besides running our own server? I've
never actually run a key server like that, the security concerns alone
worry me. Anyone have any ideas?
15 years, 1 month
a fresh member introduction
by Loretta TIOIELA
I'm glad to join the fedora project team as a contributor and hope to be able to help .
I'm Loretta aka myuusan;
Here's some details about my skills and professionnal experience :
MCSE Level on Windows 2003
RedHat FedoraCore, Debian
Planning, Designing, Implementing,
Troubleshooting Network Infrastructure
MS Exchange 2003 Server
Microsoft Office Communicator Server
Microsoft SQL Server :
load balancing, caching, clustering,
building redundant networks, SAN architecture
Cluster configuration ,
RAID solutions Shadow Copy Services
ISA Server Firewalling:
Proxy, Reverse Proxy services, Filtering capabilities ,
IAS Server: Kerberos, EAP,SSO solutions
Cisco CCNA Certification:
configuration of Cisco hardware routers switches
bridges and firewalls in a LAN/WAN environment
Connection types: MPLS, Frame-Relay, ATM
Routing protocols, BGP, EIGRP
Cisco Client VPN/site-to-site VPN
Cisco LAN Wireless network
Voice-data network integration;
WSUS, SMS, Microsoft System Center
Infrastructure Engineer IT operations
IMPLEMENTATION, MAINTENANCE AND MONITORING; UPGRADES, TRANSFORMATIONS AND INTEGRATION
Experience working closely with infrastructure and database architects, as well as with application development teams
Assisting in the development and maintenance of broadband & IP Network architectures taking into account both business and technology requirements
Delivering an end-to-end highly performing and stable Operational Support System (OSS)
Monitoring of operational IT infrastructure, addressing operational issues when they arise, troubleshooting and performance tuning of multiple technology products
Coordinating with designing team to provide efficient and durable changes for IT organization defined in project portfolio, while keeping up-to-date all operations asset records and reports
PROCESSES; STRATEGIES; AUDITS AND REPORTS
Ensuring compliance with organization policies, procedures and IT Strategies
Process re-engineering and implementation of process, technology, and organizational change in order to improve business value
Identifying and scoping the infrastructure risks and constraints
Delivering specialized preventative services such as technology Health Checks
Supporting continually build skills and capabilities training to adapt to a changing IT environment and Technologies
Maintaining timely and accurate updates on project status according to IT Strategies
Documenting projects using defined project methodology standards
Experience of most stages in the systems delivery lifecycle: from requirements definition through to implementation
Hoping to get started soon
Express yourself instantly with MSN Messenger! Download today it's FREE!
15 years, 1 month
Re: Fedora-infrastructure-list Digest, Vol 21, Issue 34
by Rajagopal Swaminathan
(respect to everything that is to be respectd -- veda)
I am just a human being eking out a living by RHEL and Linux (not working on
the monstrous OS which dominates the planet)..
I am from India. I would like to be useful to this noble project in my
aa no bhadraaH kratavo yantu vishvataH
(Let noble thoughts come to us from the Universe -- veda)
15 years, 1 month
Infrastructure beat is ready
by Huzaifa Sidhpurwala
-----BEGIN PGP SIGNED MESSAGE-----
Infrastructure beat is ready, Sorry thomas could not do that last week
as i was travelling.
Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas)
3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
15 years, 1 month
by Greg Krpan
My name is Greg Krpan, and I'm in Colorado USA. I am currently a contractor to IBM as a UNIX Administrator, supporting AIX, Solaris, and of course, Linux.
I have been working with Linux since 1995 when I was a student at DeVry. I started on Slackware, but quickly moved to RedHat once I took over administration of the DeVry Calgary website in the summer of 1995. Upon graduation in 1997, I started working for IBM Global Services Canada, where I was administering AIX, Solaris and Linux systems for various clients. After 3 years at IBM Canada, I took a position working for the USGS at the EROS Data Center in Sioux Falls, SD. My first tasks at EROS were to design and build a Beowulf Class supercomputer, which was implemented for use in developing 3-D models for land usage. I also took over the entire Linux infrastructure, which I increased from 3 workstations, to 12 servers and 90 workstations. After 3 years at EROS, I left for Colorado, and a return to IBM, where I remain today.
At home, I have been running Linux exclusively on my personal system for 6 years, starting with SuSE 8, and then moving to RedHat 9, and progressively forward through Fedora Core, with my main system running Fedora Core 8, and my development system running Fedora Core 9 Alpha.
I look forward to participating in the meetings and discussions, and working with all of you in the upcoming weeks, months, and years.
Thanks for taking the time to see what I'm about, and see you all in the next meeting!
In honor of those who lost their lives exploring the final frontier:
Apollo 1; January 27, 1967
Virgil "Gus" Ivan Grissom, Edward Higgins White II, Roger Bruce Chaffee
Space Shuttle Challenger, Mission STS-51-L; January 28, 1986
Francis R. Scobee, Michael J. Smith, Judith A. Resnik, Ellison S. Onizuka, Ronald E. McNair, Gregory B. Jarvis, Sharon Christa McAuliffe
Space Shuttle Columbia, Mission STS-107; February 1, 2003
Rick D. Husband, William C. McCool, Michael P. Anderson, Kalpana Chawla, David M. Brown, Laurel Blair Salton Clark, Ilan Ramon
Helping your favorite cause is as easy as instant messaging. You IM, we give.
15 years, 1 month
by Jonathan Roberts
There's an open ticket here:
for a news.fedoraproject.org site but unfortunately it's not been
updated in the past 4 months. Does anybody have any news on what's
happening with it, and if not, would anybody mind if I picked it up?
I'm not an expert but willing to learn, and if somebody a bit more
knowledgable than me was willing to give me a bit of help from time to
time I think we can get this done. I think it's quite an important
piece to get in place, as there's more and more content I'm wanting to
put out from a marketing perspective and this would be the perfect
Oh, and do tell me if this is the wrong list!
15 years, 1 month