infrastructure December 2006

infrastructure@lists.fedoraproject.org

34 participants
34 discussions

Fedora Updates System
by Luke Macken 13 Dec '06

13 Dec '06

Hey Guys, I just committed the first bits to the new updates system[0]. At the moment it doesn't do much, but I defined an initial database model (which will also help us see how to integrate this with the package db) and a couple of controllers. I also updated the UpdatesSystem wiki[1] page with screenshots of the current system that is used to push out core package updates. Hopefully this will give people some context as to the direction this project is going in. The code should be pretty well commented, especially in places that *need* code. This project is going to become a top priority for me in about week, after finals. I'll try and produce a list of tasks at some point in the near future that people can just pick up and work on. But in the mean time, if you would like to help out, I recommend reading over the wiki and getting familiar with the current update process/system. From there, checkout the code, `yum install TurboGears` and start playing around with it. luke [0]: http://cvs.fedoraproject.org/viewcvs/fedora-updates-system/?root=fedora [1]: http://fedoraproject.org/wiki/Infrastructure/UpdatesSystem

2 4

Fwd: [Ticket#2006121110000016] New ticket notification! (Fedora planet RSS [...])
by Mike McGrath 12 Dec '06

12 Dec '06

Anyone familiar enough with our rss system that can take a look at this? If not I'll have a look tomorow. -Mike ---------- Forwarded message ---------- From: Fedora Ticket Notification <otrs(a)fedoraproject.org> Date: Dec 11, 2006 1:35 AM Subject: Re: [Ticket#2006121110000016] New ticket notification! (Fedora planet RSS [...]) To: mmcgrath(a)fedoraproject.org Hello, there is a new ticket in "Websites"! Aurelien Bompard <gauret(a)free.fr> wrote: <snip> > Hi, > > The Fedora Planet RSS feed seem to be broken : > http://fedoraproject.org/people/rss20.xml > > It seems to be broken by a link in David Lutterkort's entry > about "Kickstarting into puppet". > > There are errors using xmllint: > > $ xmllint rss20.xml > rss20.xml:647: parser error : EntityRef: expecting ';' > > <link>http://watzmann.net/blog/index.php?title=kickstarting_into_puppet&more=1& > > ^ <snip> https://admin.fedoraproject.org/tickets/index.pl?Action=AgentZoom&TicketID=… Users who would like to request access to be an agent in the ticketing system please see: http://fedoraproject.org/wiki/Infrastructure/Tickets Your OTRS Notification Master

3 4

Meetings
by Luke Macken 10 Dec '06

10 Dec '06

Hey guys, Due to poor scheduling[0] on my part, I will not be able to make any of the meetings for the next 10 weeks. I just couldn't resist and had to sign up for a class on Zen Buddhism at that time. As far as things are going now, I've been doing much hackery on the new UpdatesSystem[1], and should have a functional system shortly. Right now I have a local tree of test builds which I am using to push out to a test-stage. After I write up a bunch of nose tests for it, I'll commit a package or so from the test tree as well. I poked around at publictest2 last night, which doesn't seem to be public at all. I also was not able to get any traffic out. If anyone has a free second, could you take a look at this? Thanks, luke [0]: http://schedule.csh.rit.edu/?s=JxWp7Uj [1]: http://fedoraproject.org/wiki/Infrastructure/UpdatesSystem

4 5

OpenID Libraries
by Jeffrey Ollie 07 Dec '06

07 Dec '06

I've submitted for review a Python library for OpenID and some dependencies that weren't already in FE. Here are the relevant links: python-pycurl https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218787 python-urljr https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218831 pyflakes https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218839 python-yadis https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218844 python-openid https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218852 Jeff

1 0

IRC Meeting Log Posted - 12/07/2006
by Jeffrey Tadlock 07 Dec '06

07 Dec '06

The notes from today's Infrastructure meeting on IRC have been posted to the Wiki: http://fedoraproject.org/wiki/Infrastructure/Meetings/2006-12-07 --Jeffrey

1 0

Glump in Fedora Extras?
by Jeffrey Ollie 07 Dec '06

07 Dec '06

It looks like Glump might be the perfect tool for a project here at work. Is there anyone @ Duke that wanted to maintain the package in Fedora Extras? If not, I'm willing to be the maintainer. Jeff

2 2

Update on Plague/Brew status?
by Jeroen Janssen 06 Dec '06

06 Dec '06

Hello, Any information on what's going to happen with Plague/Brew yet? Best regards, Jeroen Janssen

1 0

new 1950
by Stacy J. Brandenburg 06 Dec '06

06 Dec '06

I received and installed a new 1950 from Dell... What is the purpose of this machine going to be so that I can label it correctly? -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden(a)redhat.com = = 919-754-4313 http://www.redhat.com = ========================================================

2 2

Re: Package DB Schema v3
by Toshio Kuratomi 05 Dec '06

05 Dec '06

On Tue, 2006-12-05 at 16:14 -0600, Jeffrey C. Ollie wrote: > On Tue, 2006-12-05 at 12:35 -0800, Toshio Kuratomi wrote: > > On Tue, 2006-12-05 at 13:43 -0600, Jeffrey C. Ollie wrote: > > > On Tue, 2006-12-05 at 11:32 -0800, Toshio Kuratomi wrote: > > > > > > > > We could solve both concerns by having a foreign key constraint into a > > > > table with the valid status phrases for each table that needs statuses > > > > but that makes things more complex. This would allow us to select the > > > > list of valid statuses from a database table which is a plus. But it > > > > would also require a join for the common case of giving a human readable > > > > name for the status. So I'd like to hear your justification. > > > > > > You could include localized versions of the status names in the database > > > table rather than doing the localization in the front-end (of which > > > there might be several). > > > > Okay. What do you think about doing it like this: > > > > create table StatusCode ( > > id serial primary key, > > ); > > > > create table Translations ( > > statusCodeId integer references StatusCode(id), > > language text not null default 'C', > > statusName text not null, > > primary key (statusCodeId, language) > > ); > > Yeah, that looks like what I had in mind, except that I would call the > table "StatusCodeTranslations." > That would be fine. > > create view CollectionStatusCode as select id from StatusCode where id = 1 or > > id = 3 or id = 7; > > > > create table Collection ( > > [...] > > status integer references CollectionStatusCode(id) > > ); > > > > Overengineered or good? > > Yeah, looks good to me. > > > (The view allows us to query which statuses are available for this > > table. I don't know of a sane way to do that with a check constraint.) > > Why not make CollectionStatusCode a table like this: > > create table CollectionStatusCode ( > id integer primary key references StatusCode(id) > ); That should be fine. With a dataset as small as the possible status codes I don't know that there would be much difference between the two implementations. -Toshio

1 0

OpenID on Slashdot
by Mike McGrath 05 Dec '06

05 Dec '06

http://it.slashdot.org/it/06/12/05/139204.shtml -Mike

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2006