I am new to the fedora infrastructure group. I am going throug few of the links in the site to get a feel of the work. I have submitted my .ssh_rsa_key.pub from the site. I think I will get some intimation on this. Please someone can let me know further proceedings from here onwards.
Regards & Thanks Prabir Senapati mailto: senapati2001(a)yahoo.com
AFAIK the build hosts are RHEL5 (or maybe F10 by now?). At any rate
the rpm used in rawhide is quite different than the ones from the
hosts, how has this been solved in the build hosts? Has the hosting OS
upgraded its rpm to be compatible to all hosted chroots? Or is the rpm
within the chroot used?
I'm asking in a double context: First I'd like to understand if smart
can properly handle chroots of rawhide/F11 on F10/RHEL5 hosts. Anders
Björklund (in the Cc, please keep him there on replies) has put a
great deal of effort to have smart working on F10 and F11, and a smart
version for managing F11 and later chroots on F10 or earlier would be
And second I'd like to know how to setup a build environment for F11
for getting some ATrpms packages out.
Axel.Thimm at ATrpms.net
I've been lurking on the mailing list for a while and I finally
registered for my fedora account today (username: chrisj)
I'm interested in helping out as time permits. I got on irc once
(lurking again) and haven't really logged in since. I'll try to make a
few meetings after the holidays
I'm planning to get my personal test systems setup soon. I just moved
and still getting things straight at home. Bought a 750GB drive last
night and will be installing F10 over the weekend. I had been running
the U... distro and it's time to get back to the fedora/RH rpm way of
doing things :-)
I've used RedHat since before Fedora existed (I think 6 was the first
one). Started as a hobbyist, 2 years. Then got a job as an admin and
have been doing Linux admin and Cisco networks for the last 5 years.
My current employer is a Win shop so I just get to run the DNS,
email, and network, but the network is 50 remote offices and 3
different data centers in the midwest. I don't mind the Windows too
much and can find my way around them, it's also kinda fun to get the
Linux and MS products to play nice together. I've worked with a lot of
different linux and OSS software products including: postfix,
openldap, apache, bind, samba, mailman, pam, built some custom rpm's,
etc. I use RHEL mostly at work and some fedora and Cent for testing
(some suse, deb, and slackware in the past). I used to do lots of
security firewall apliances with various linux distros (I was a big
fan of LRP when it would fit on a floppy), most of this is now done
with Cisco in my world. I can shell script pretty well and I've
written several perl scripts in the last few years (dabbled in php but
not enough to know it well). I've always been interested in python but
don't have much if any exp with it. I also don't have much experience
with SQL/DB or source control.
I was looking at the FIGs and would be interested in the base sysadmin
and sysadmin-noc for now while I figure out where everything is and
what it does. I'm also interested in more info on the sysadmin-tools
and sysadmin-web FIG.
So, next just apply for the FIGs, keep lurking, ask some questions,
show up for IRC meetings?
(I screwed up and did this w/o asking first; I expect thugs^Wenforcers
from the Chicago area to arrive momentarily; fortunately, steaks are
on the grill and hopefully they can be appeased. I can easily put the
content back if need be.)
I want to move the videos (ogg and avi files) currently hosted only
on torrent.fp.o, to alt.fp.o/pub/alt/videos/ with the other videos. I
have already copied the content over.
This request will remove the torrents, their contents, and their .ini
files on torrent1. Then, the normal processes will refresh the
torrent.fp.o web page and the tracker.
There are currently 0 or 1 seed, and 0 downloaders, for this content,
which dates back to January 2008 at the most recent.
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
I am doing MS in Network systems.
I have around 1 yr experience in network management company.
I know C, C++, Java , Perl. I also know web technologies related to web
I would like to join the team of fedora system admin.
Please let me know, If I have to do some extra steps.
Bhavinkumar G Patel
Name: Brennan Ashton
Fedora Account Name: bashton
Name: John Poelstra
Fedora Account Name: poelstra
Project Name: TriageWeb
Target Audience: Bug Triagers, Developers, Quality Assurance. To some
extent this might include the general public, as a way to see how
fedora is managing bugs and developing.
Expiration/Delivery Date (Required): 06/06/2009
TriageWeb is a turbogears application that automatically queries and
processes bugzilla bugs to generate user defined reports on triage
Base reports include:
* Number of bugs of each work flow status changed for Fedora product
as a whole over time
* Number of bugs of each work flow status changed for component D over time
* Number of bugs of each work flow status changed for component group
E over time
* Number of bugs of each work flow status changed by user F over time
* Number of bugs of each work flow status changed by user group G over time
Data is presented in both tabular and graphical displays (these lack
some UI changes for customizing queries):
Here are some samples:
Tabular data can be sorted and date ranges can be selected.
Graphical data can have data ranges limited, as well as statuses.
Refreshes of bug data would be updated at the end of each day, as
processing the few hundred bug reports changed each day take a fair
amount of time.
FutureFeatures (not so far away):
* Will integrate with FAS so that users can store there queries for
later, they also can create custom user and component groups here.
* Send weekly reports on rawhide bugs, and well as top reporters,
triagers, and bug closers.
* A Look Into Rawhide
--This is an idea that I discussed with jlaska, the idea is that this
is a work bench that people can visit to see how we are progressing
with blockers as milestone are reached. This would also include a
section that more effectively then bugzilla, shows the top duplicated
bugs, so that developers and traigers spend less time having to sort
through 50 dup bug reports filed when component X failed today.
*Create a section where FAS groups and users can create a monitor
goals that are compared to standard queries. What this means will be
partially determined by feedback on what people use and how they use
the core features.
* Currently the project is locally hosted and is in a nearly usable
state already. There is still one known bug in the scripts that pull
data from bugzilla, this just requires going back and tracing what
types of bugs cause the error and then fixing the script to process
* In a week or as soon as the RFR is granted, people are wanting to
start testing the app, the triage group is especially eager to start
using it, this will give me significant feedback as to what needs to
be changed or added.
*After this has become stable, I will request that the application be
pushed live as a release application.
* I need to start looking into optimizing the database queries and
format, as the application is database intensive.
* Once the core app is running smoothly I will start to integrate and
develop the tasks outlined in FutureFeatures in the order that I have
listed them. The development of these features will mostly take place
during the months of June and July, and then continue at a slower pace
during the school year where the focus will be primarily maintenance
and bug fixes as I will have more limited time.
==Specific Resources Needed==
*Webspace to run the turbogears application
*Ability to create cron jobs for daily data fetching scripts (no more
then an hour each day)
--When rebuilding the database to introduce feature requests a script
will take around 10-12 hours. This should happen only very
occasionally, and does not take much processing power as most of the
time is spent doing xmlrpc communications with bugzilla.
*Database space to store metrics data as well as user preferences.
The metrics data right now in a sqlite db is only a few MB, I would
not expect it to grow beyond 50MB even with heavy user usage. I have
no preference between MySQL and postgresql
*Package wise all dependencies are in fedora already, with the
exception of traigeweb itself.
There may be a few others, but that should be a very representative list.
The point of this project is to give the traige, packaging, and QA
groups some new tools so that they can better measure there status as
well as monitor critical areas. This should especially help with the
development cycles once some of the FutureFeatures have been
introduced. This also allows fedora to better recognize the commitment
of some members in the community who spend there time in the drudgery
of processing, reporting, and solving bugs.
* I am looking for someone in the sysadmin-web group to sponsor me.
* I have filed this as ticket #1314
Thank you for the consideration,
Andre Robatino wrote in fedora-test-list:
> I have made available a deltaiso from the i386 Preview DVD ISO to the
> i386 RC2 ISO. It is 233945224 bytes (about 6-7% the size of the full
> ISO) with MD5 f0413ba9d23be4dd1778a06f35c80a43, and can be downloaded from
> ... To apply
> it, one needs to have the deltarpm package installed, and then run the
> applydeltaiso Fedora-11-Preview-i386-DVD.iso
> Fedora-11-Preview_rc2-i386-DVD.diso Fedora-11-i386-DVD.iso
> ... Of
> course, one should check the sha256sum of the final ISO (listed in
> Fedora-11-i386-CHECKSUM as
> ... This was just done as a demonstration. ...
Hmm... Make the technology work *for* you. A novel idea.
Maybe the GA could be distributed the same way, like to mirrors and end
users. It only works for places that already have the previous image
(i.e., Preview in this case), but that's at least the testers.
This one's an oops, probably on me. I happened to notice proxy1 is an
x86_64 box. We have two options.
1) double it's ram
2) rebuild it as x86
I'd prefer to do 2 since the release slipped again and we've generally got
time for it. The concern is the boxes are tuned for i686 with 4G of ram
and don't generally like to operate if either of those change.