I think I solved the repo-closure/deps scripts issues. Now it should
be back to sending only one email, (instead of 6). Also, there was an
indentation issue in the reporting program that was causing the
dependencies problems to be cleared.
Please test this once before putting in production. I tested the best
I could on publictest16 and my home systems, but I didn't have full
access to all yum repos anywhere. Additionally, I changed the shell
script to reference local copies of yum.conf and rc-report.cfg. I
think that is probably ok, but somebody should verify.
I was pretty clear with you on IRC. Fedora People is not a location to
bypass Fedora's normal policies and procedures. You asked for space on
Fedora People to post your ISO, it was denied because its going through
the approval process for Fedora. The Board approved it and I assume
releng will soon at which point in time the spin will get built and
distributed through normal means.
In short, remove it. Fedora people is not an iso distribution mirror.
We have procedures in place to host isos and you have been made aware of
these procedures. I'm not sure who increased your space for this but when
someone says no, asking others until someone says yes is in poor
judgement. I know this sounds harsh but I want this message to be as
clear as I can as it was ignored a few days ago.
Been lurking a bit, decided to say hello.
I have been using RH/Fedora since the Mother's Day release, and it has
been my primary desktop since then.
I have in the past been a line SA doing 1st, 2nd, and 3rd level support.
I have been a sales-engineer supporting Linux solutions.
I have been a php developer.
I have been a enterprise solutions consultant (love that term :).
I am currently a senior engineer at a large bank support RHEL.
I was a member of the Red Hat Beta team pretty much its whole time.
I have RHCE for RH 6.x, 8, and RHEL 5.
I have at one point or another been postmaster, webmaster, firewall
master, configuration tzar, provisioning tzar, and hardware monkey.
I live in America/Chicago timezone (just outside of Houston, TX).
How can I help? :)
. Don Harper, RHCE . We first make our habits, and .
. duck(a)duckland.org . then our habits make us. - John .
. www.donharper.org . Dryden .
Hi every body i want to join to the fedora infrastructure team, add
something of my skills
- System Administrator on RedHat 7.3, RedHat Advanced Server 2.1, RedHat
Enterprise Linux 3, RedHat Enterprise Linux 4, RedHat Enterprise Linux 5,
- Configurations and Installations of Redhat servers through PXE and
- Configurations of yum repositories for provisioning redhat servers ( 2.1,
3, 4, and 5 )
- LVM Filesystems
- Bash Scripting
- Technical Management of network services on Redhat (Radius, DNS, DHCP,
- Technical Management on VMware Server and Xen.
- Backup Administrator in tape library MSL6000 with Omniback II.
- Storage Administrator in Storage Strategies with EVA500
- Monitoring Administrator with Nagios, open source tool.
- Technical knowledge on IBM and HP Hardware such as Blade Servers
HS21(IBM), xSeries 3250-3850 (IBM), Blades Server BL20PG2 (HP), DL360 G2 ,
DL380 G2 , DL580 G2 (HP).
- Firewall and VPNs Administrator on Netscreen Appliance
Thank you ever body ...
19:59 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Role Call. Who's here?
19:59 * ricky
20:00 < themayor> nope were good
20:00 < themayor> thanks guys
20:00 * SmootherFrOgZ here
20:00 * wcattey makes his way to the exit as the meeting changes.
20:01 < smooge> here
20:01 < mmcgrath> Ok, lets get started
20:01 -!- notting [n=notting@redhat/notting] has joined #fedora-meeting
20:02 < fugolini> Just a small comunication for FAmSCo members, the meeting is going to be held in #fedora-ambassadors
20:02 < mmcgrath> First we'll hit up the release tickets.
20:02 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Release Tickets
20:02 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/report/9
20:02 < zodbot> mmcgrath: http://tinyurl.com/5onzad
20:02 < mmcgrath> .ticket 932
20:02 < zodbot> mmcgrath: #932 (Preview website) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/932
20:02 < mmcgrath> ricky: if you've got that would you mind accepting the ticket?
20:03 < ricky> Sure
20:03 < mmcgrath> solid
20:03 < mmcgrath> ricky: are there any blockers with that or anything you need from us?
20:03 -!- wcattey [n=devnull(a)HANTA-YO.MIT.EDU] has left #fedora-meeting ["Leaving"]
20:03 < ricky> Nope, I'll just make sure to confirm the torrent URLs early, and we'll be using the current get-fedora for the preview
20:04 < mmcgrath> Will you be doing the actual flip on release day or should someone else? If not you please note it in the ticket.
20:04 < mmcgrath> <nod> feel free to cc f13 on there and have him give the names to you.
20:04 < mmcgrath> next ticket
20:04 < mmcgrath> .ticket 933
20:04 < zodbot> mmcgrath: #933 (Preview release - Verify mirror space) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/933
20:04 < mmcgrath> I'm going to do this, I'm pretty sure we're find
20:04 < mmcgrath> err fine
20:04 < mmcgrath> .ticket 935
20:04 < zodbot> mmcgrath: #935 (Preview - Mirror Coordination) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/935
20:04 < mdomsch_> hi
20:04 < mmcgrath> f13: mdomsch_: what do we do for preview releases there? Anything special? do we even need to tell them about it or do we just let it happen?
20:04 -!- AndreasR [n=zeus(a)80-218-142-182.dclient.hispeed.ch] has left #fedora-meeting ["Verlassend"]
20:05 -!- moixs [n=chatzill(a)77-56-144-93.dclient.hispeed.ch] has left #fedora-meeting 
20:05 < mdomsch_> f13 usually sends an email before posting the bits
20:05 < mdomsch_> when he knows they're close to being ready
20:05 < mdomsch_> that's all
20:06 < mmcgrath> kew, I figured its simple
20:06 < mmcgrath> .ticket 936
20:06 < zodbot> mmcgrath: #936 (Preview release - Mirror bit verification) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/936
20:06 < mmcgrath> SmootherFrOgZ: you're on this one. We've never really done this before (which is bad) but you're the man now, care to let us know what you're going to do? :)
20:07 < SmootherFrOgZ> no pb ;)
20:07 < mmcgrath> part of it is making sure the permissions are right and syncing, what else is there?
20:08 < SmootherFrOgZ> i think that's it
20:08 < mdomsch_> and that jesse lands the content in the right place :-)
20:08 < mmcgrath> k, I suppose we could -V the packages too if you were real hard core about it.
20:08 < SmootherFrOgZ> correct
20:08 < mmcgrath> mdomsch_: yeah, good point :)
20:09 < mmcgrath> .ticket 937
20:09 < zodbot> mmcgrath: #937 (Preview - Infrastructure Change Freeze) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/937
20:09 < mmcgrath> I've got this one, everything's been fine.
20:09 < mmcgrath> It is interesting to note how much more quiet nagios is when we're in a change freeze :)
20:09 * dgilmore is here
20:09 * mmcgrath hopes he doesn't jynx it
20:09 < mmcgrath> and
20:09 < mmcgrath> .ticket 934
20:09 * nirik wonders if this release will be the first with no RHIT interaction needed... or do they still need to flip something?
20:09 < mmcgrath> dgilmore: yo
20:09 < zodbot> mmcgrath: #934 (Preview Release Ticket) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/934
20:10 -!- sternecg [n=sternecg(a)ohnat.bristolwest.com] has joined #fedora-meeting
20:10 -!- buggbot [n=supybot(a)landfill.bugzilla.org] has quit Read error: 104 (Connection reset by peer)
20:10 < mmcgrath> nirik: this could be the first one, I can't remember if they were involved for F9 or not...
20:10 < mdomsch_> nirik, they do not
20:10 < dgilmore> mmcgrath: i think alot of nagios noise is people not scheduling downtime when doing work
20:10 < mdomsch_> mmcgrath, nope, not since the composes happen in PHX now
20:10 < mmcgrath> kew
20:11 * nirik nods. Cool.
20:11 < mmcgrath> so that release ticket is mostly just a tracker. it'll be closed when the release is out.
20:11 < mmcgrath> So thats really it with the preview release, any one have any questions or concerns? Speak your mind.
20:11 < dgilmore> mmcgrath, nirik: i think they were not involved in F-9
20:11 * nirik thought they were, but could be misremembering.
20:11 < mmcgrath> my brain doesn't go back that far.
20:11 < ricky> What is the status of myfedora with regard to the final release?
20:12 * ricky remembers seeing a blog post about it
20:12 < mmcgrath> ricky: wait till the floor is open :-P
20:12 < mmcgrath> which is pretty soon
20:12 < ricky> Oop, sorry
20:12 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets
20:12 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
20:12 < zodbot> mmcgrath: http://tinyurl.com/5g3oxm
20:12 < mmcgrath> err not that
20:12 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
20:12 < zodbot> mmcgrath: http://tinyurl.com/2hyyz6
20:12 < mmcgrath> that one ^^
20:12 < mmcgrath> only one
20:12 < mmcgrath> .ticket 740
20:13 < zodbot> mmcgrath: #740 (Loaning out system time to OLPC participants) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/740
20:13 < mmcgrath> dgilmore: heard any news on this? I haven't. I assume its a pretty low priority
20:13 < dgilmore> mmcgrath: not heard anything more
20:13 < mmcgrath> k
20:13 < mmcgrath> in that case
20:13 < mmcgrath> I've just got a couple of items this week.
20:14 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- oVirt
20:14 < mmcgrath> Nothing real new with the ovirt looks this week, I also just started looking at enomalism.
20:14 < mmcgrath> They did release 0.84 (ovirt) and I've downloaded that.
20:14 < mmcgrath> So nothing real new.
20:14 < f13> sorry I'm late.
20:14 < mmcgrath> f13: no worries
20:14 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Backup2
20:15 < mmcgrath> I'm working to get our off-site backup solution in order. It will be at ibiblio. It will help me sleep better at night.
20:15 < mmcgrath> Its basically going to be a combination lvm + snapshot + nightly rsync type setup.
20:15 < ricky> Will it be everything or just a specific subset?
20:16 < mmcgrath> ricky: specific subset. Basically everything we'd need to get going again if the worst happened.
20:16 < mmcgrath> so databases, puppet configs, cvs, lookaside cache, etc.
20:16 < mdomsch_> hosted
20:16 < mmcgrath> it will likely be on an encrypted filesystem of some kind.
20:16 < mmcgrath> mdomsch_: actually hosted is already setup. We've got replicated data from hosted1 -> hosted2 in VA, and an offsite backup in PHX.
20:16 < ricky> Cool, that sounds really interesting
20:16 < mdomsch_> nice
20:16 -!- rdieter is now known as rdieter_away
20:16 < mmcgrath> yeah, we did hosted right :)
20:17 < mmcgrath> its not live replication but it is hourly IIRC.
20:17 -!- stickster is now known as stickster_afk
20:17 < mmcgrath> I've thought about doing live replication but haven't sat down and done it yet.
20:17 < mmcgrath> anywho, any questions about backup2?
20:17 < mmcgrath> kew
20:17 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Open Floor
20:17 < mmcgrath> ricky: I believe you had something? :)
20:17 -!- rkastl__ [n=rkastl(a)e181097103.adsl.alicedsl.de] has joined #fedora-meeting
20:18 < ricky> 20:11:55 < ricky> What is the status of myfedora with regard to the final release?
20:18 < ricky> 20:12:05 * ricky remembers seeing a blog post about it
20:18 < mmcgrath> ahh yes
20:18 < mmcgrath> I've not heard any status reports about myfedora
20:18 < mmcgrath> J5: lmacken: either of you two around?
20:18 < mmcgrath> can you give us a status report of my fedora or perhaps email a larger status report to the list?
20:19 * mmcgrath assumes they're absent right now.
20:19 < mmcgrath> ricky: so I'd say they have a status, but not sure what it is. I'll drop an email to see whats up
20:19 < ricky> Cool
20:19 < mmcgrath> Anyone have anything else they'd like to duscuss?
20:19 < mmcgrath> err discuss even?
20:20 < mmcgrath> mdomsch_: the ubuntu guys are pretty sweet on your mirrormanager stuff.
20:20 < mdomsch_> yeah?
20:20 < mdomsch_> pointers?
20:20 < f13> I'm getting quite close to being able to release the .newkey stuff for F8 and F9 Everything trees
20:20 * ricky wonders if nirik wanted to ask about ticket 651
20:20 < ricky> .ticket 651
20:20 < f13> it'll baloon up our mirror space for a period of time, until we prune the non .newkey content
20:20 < zodbot> ricky: #651 (system account for tier2 ppc32/x86_64 hosting for cvsextras) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/651
20:20 < mdomsch_> f13, for Preview you're not changing the repo=rawhide parts of fedora-release, right?
20:20 < nirik> oh yeah... any news there?
20:20 < mdomsch_> but you will for RC?
20:21 < f13> however I'm not sure of the timing of releaseing this stuff, given the need to stage Preview and the F0 Final.
20:21 < mmcgrath> mdomsch: http://irclogs.ubuntu.com/2008/10/30/%23ubuntu-website.txt <-- towards the bottom.
20:21 < f13> mdomsch_: that's correct. post-preview is when I'll make all the bits look like the real thing, including the repo change.
20:21 < mmcgrath> f13: when will that happen? how much of a baloon are we talking about?
20:22 < f13> mmcgrath: I'm not sure when it'll happen. I'm more inclined to wait until after F10 goes out at this point, just because of all the churn that's upcoming.
20:22 * dgilmore would like to see ticket 651 done
20:22 -!- fbijlsma [n=fbijlsma(a)188.8.131.52] has joined #fedora-meeting
20:22 < mmcgrath> f13: k
20:22 < f13> it'll double the size of the Everything/ tree for 8 and 9
20:23 < mmcgrath> f13: mind opening a ticket for mirrorspace verification on that?
20:23 < mmcgrath> ricky: one sec on 651
20:24 * mdomsch_ gets evil thought
20:24 < mdomsch_> create a new hidden category "Ubuntu" in MM
20:24 < mdomsch_> and pretend they're at /pub/Ubuntu/
20:24 < mdomsch_> and start serving download.fedoraproject.org/pub/Ubuntu/...
20:25 < f13> mmcgrath: I'll do that before I put any bits in place.
20:25 < mmcgrath> mdomsch_: heh
20:25 < mmcgrath> f13: solid
20:25 < mmcgrath> Ok,
20:25 < ricky> Hehe
20:25 < mmcgrath> ricky: what about 651?
20:25 < ricky> I think nirik was just asking about that
20:25 < nirik> yeah, whats the status?
20:26 < mmcgrath> loupgaroublond: you around?
20:26 * mmcgrath thinks loupgaroublond had this done but not merged to a recent tree.
20:26 < mmcgrath> we talked about it a bit ago but I don't remember its status
20:27 < loupgaroublond> mmcgrath, yes?
20:27 < loupgaroublond> mmcgrath, done what?
20:27 < mmcgrath> .ticket 651
20:27 < zodbot> mmcgrath: #651 (system account for tier2 ppc32/x86_64 hosting for cvsextras) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/651
20:28 < loupgaroublond> is this the 'thirdparty' system deal?
20:29 < mmcgrath> yeah
20:29 < loupgaroublond> ok, iirc, we're using the privacy security features to implement this...
20:29 < loupgaroublond> in the config, a certain group is assigned 'thirdparty' and any third party system should have a login account that is a member of that group
20:30 < loupgaroublond> when pulling stuff from FAS, authenticate with that user, and not with an administrator user
20:30 < loupgaroublond> the privacy stuff, when sending out the userlists, should call the filter_private() method, which will drop the password bits, and possibly something else, though i can't remember offhand
20:31 < mmcgrath> loupgaroublond: and this is in version 0.8.4.5 or in HEAD or not yet completed?
20:31 < loupgaroublond> it's completed, though i'm not sure what's in version 0.8.4.5, so you'll have to check the git log for that
20:32 < mmcgrath> <nod>
20:32 < J5> mmcgrath: whats up?
20:32 < mmcgrath> ricky: while we're getting the next release ready lets make sure to check on that. Give it a test, etc. Then on deployment we'll let nirik and dgilmore know so they can do testing.
20:32 < mmcgrath> J5: ono momento
20:32 < mmcgrath> any other questions on ticket 651?
20:32 < ricky> mmcgrath: Sure
20:33 -!- che_ [n=rkastl@redhat/che] has quit Read error: 110 (Connection timed out)
20:33 * ricky has kvm machines setup now that'd be perfect :-)
20:33 < ricky> **virtual machines
20:33 < mmcgrath> J5: we were wondering if you could give us a status report on MyFedora?
20:33 < nirik> and it just gets ssh keys and logins, no passwords, right?
20:33 < ricky> nirik: Yup, that's the plan
20:34 < J5> ok, we are doing cleanups right now, the whole stack is packaged though the myfedora package needs some more cleanups.
20:34 < ricky> Also no real name, etc. info for people with privacy on
20:34 < nirik> great. Let me know when to test.
20:34 -!- sternecg [n=sternecg(a)ohnat.bristolwest.com] has quit "Leaving"
20:34 < J5> we have a test instance up at https://publictest16.fedoraproject.org/community
20:35 < mmcgrath> Do we have an estimated date on when it will be ready for deployment?
20:35 < ricky> Will it run on the same boxes as our other TG apps?
20:35 < J5> you can push updates from the updates tool, I show controls in the builds tool but haven't hooked that up yet
20:35 < J5> should be ready for deployment with F10 release
20:35 < dgilmore> ricky: just want public keys and usernames
20:36 < loupgaroublond> mmcgrath, the git commit's SHA is 3067a96d6cc0260c8c8bf179b93471fcb185475a
20:36 < SmootherFrOgZ> great
20:36 < mmcgrath> loupgaroublond: thank you.
20:36 < ricky> dgilmore: Hm, OK - we might have to make make sure fasClient works with just that info, then
20:36 < mmcgrath> ricky: and group info
20:36 < loupgaroublond> mmcgrath, and that appears to be master
20:36 < J5> We really just need to clean up some of the screen in terms of css and have better error handling
20:37 < dgilmore> mmcgrath: ahh yeah we might need that also
20:37 < dgilmore> ricky: ill just as gladly not have Real Names
20:37 * nirik nods at dgilmore.
20:38 < J5> just a warning to the rest of the infrastructure, I'm going to be sending in a bunch of patches during the F11 time frame as we had to drop a bunch of features because the API wasn't exposed or was exposed in a way we couldn't use very easily
20:39 < J5> mmcgrath: I have a couple of questions about deployment
20:39 < mmcgrath> J5: sure, shoot them my way.
20:39 < mmcgrath> J5: do we have any estimated date on when it will be ready for deployment?
20:39 < dgilmore> whats the url for the test instance?
20:39 < ricky> dgilmore: https://publictest16.fedoraproject.org/community
20:40 < J5> where do you want to mount myfedora? If it is under the admin.fd.o we can link off to other infrastructure bits better
20:40 < J5> two more weeks I would say
20:40 < mmcgrath> J5: doesn't matter to me, we can do admin.fedoraproject.org/myfedora/ or myfedora.fedoraproject.org/
20:40 < ricky> That sounds good - depending on how auth is done, maybe they can share auth cookies
20:40 < J5> admin.fedoraproject.org/community
20:40 < mmcgrath> we have a *.fedoraproject.org certificate now so secure sites are cheap.
20:40 < J5> ricky: I'm already using the same cookies
20:40 < mmcgrath> yeah, wherever you guys want, doesn't matter to me.
20:41 < ricky> Nice
20:41 < J5> mmcgrath: I would like community.fedoraproject.org but that puts us in a different domain
20:42 < dgilmore> J5: have you guys tested in konqueror?
20:42 < mmcgrath> <nod>
20:42 < J5> any reason why cookies are not attached to fedoraproject.org or is that a browser thing?
20:42 < ricky> There are pages under fedoraproject.org which we couldn't 100% trust the content of
20:42 < J5> dgilmore: mostly firefox but I ran it on safari and it looked and worked fine
20:42 < ricky> Like the old wiki allowed arbitrary HTML
20:42 -!- fbijlsma [n=fbijlsma(a)184.108.40.206] has quit "Leaving"
20:42 < J5> dgilmore: would be good if we got more testing
20:43 < ricky> And then there's people.fedoraproject.org
20:43 < dgilmore> J5: i generally use konq and it seemed busted
20:43 < dgilmore> J5 i had to hit close nearly 10 times before hiting the front page
20:43 < J5> dgilmore: file bugs, some parts are busted in general that we need to clean up
20:44 < dgilmore> J5: it kept showing planet feeds on top of everything else
20:44 < dgilmore> J5: where do bugs get files
20:44 < dgilmore> filed
20:44 < dgilmore> J5: blog about it please
20:44 < J5> myfedora.fedorahosted.org
20:44 < J5> dgilmore: I did, a couple of days ago
20:44 < dgilmore> J5: i missed it
20:44 < J5> k
20:44 < dgilmore> be louder :)
20:45 < J5> NEXT TIME I WILL POST IN ALL CAPS :)
20:45 < ricky> More <blink>s in the entry
20:45 < mmcgrath> heh
20:45 < mmcgrath> Ok ok, I'm thinking we can close the meeting a little early. Anyone have anything else they'd like to discuss?
20:45 < dgilmore> J5: this could be something cool. but It needs some noise :)
20:45 < J5> ya
20:45 * dgilmore got a G1 this afternoon
20:46 < J5> mmcgrath: so I was told you use mod_ssl not mod_nss - how do you want me to configure myfedora's package?
20:46 < dgilmore> J5: AFAIK we use mod_ssl everywhere not mod_nss
20:47 < dgilmore> i know koji uses mod_ssl
20:47 < mmcgrath> J5: actually you probably won't need to worry about that, the app servers don't exist at our encryption layer.
20:48 < J5> so take out the ssl apache configs?
20:48 < mmcgrath> J5: leave it on the publictest boxes, but when it gets deployed on app[1-6] take it out, the proxy servers do our ssl encryption
20:49 < J5> my biggest problem with that is if a user installs it without ssl they could potentially send fedora passwords over the wire
20:49 < mmcgrath> if a user installs what exactly?
20:49 < J5> the myfedora rpm
20:49 < mmcgrath> and thats the webapp?
20:49 < J5> yes
20:50 < mmcgrath> ah, typically that stuff is left up to the admins.
20:51 < J5> ok, I just copied what func did
20:51 -!- DemonJester [n=DemonJes@fedora/DemonJester] has quit "leaving"
20:51 < J5> so you don't want me installing the myfedora.conf in /etc/httd/conf.d?
20:51 < mmcgrath> <nod> with Func we don't pass it through the proxy layer, its not quite a traditional webapp.
20:52 < mmcgrath> J5: thats up to you but whatever you do with it we'll be changing it and controlling it via puppet anyway :)
20:52 < mmcgrath> being a config file and all
20:52 < J5> ok cool
20:53 < mmcgrath> Ok, well we'll look forward to that in the comming weeks.
20:53 < mmcgrath> Anyone have anything else they'd like to discuss? If not we'll close the meeting in 30
20:54 < mmcgrath> 10
20:54 < J5> hey guys, test it out and blog about it
20:54 < mmcgrath> J5: sure thing
20:54 < J5> and file bugs :)
20:54 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting closed
I wonder whether it is possible to use a fedoraproject.org email
alias in bugzilla without decoupling it from FAS?
The connection between a bugzilla account and a Fedora account is
based on the primary email address in FAS, right? So, if I update my
bugzilla preferences to use the fedoraproject mail alias, does that
disconnect my bugzilla account from FAS?
I would like to perform a trivial bodhi upgrade that contains the
@@ -168,7 +168,7 @@ class Root(controllers.RootController):
forward_url= cherrypy.request.headers.get("Referer", "/")
# This seems to be the cause of some bodhi-client errors
- # cherrypy.response.status=403
return dict(message=msg, previous_url=previous_url, logging_in=True,
This reverts a workaround for a problem in python-fedora-0.2.x, which has since
been resolved. This bodhi patch should hopefully resolve
https://bugzilla.redhat.com/show_bug.cgi?id=466510 as well.