Fixes for git repos not configured as bare on hosted1
by Todd Zullinger
It was reported that with the recent update to git-1.7.4.1 that a
number of the repositories on hosted1 lacked the proper core.bare
setting, which caused git to refuse to allow updates. I added a check
for the this to the git check-perms script and ran it with the -f
option to fix up misconfigured repositories. The output:
$ time sudo git check-perms -f
/git/amber.git: core.bare not true
/git/anaconda-help.git: core.bare not true
/git/anaconda-images.git: core.bare not true
/git/anaconda.git: core.bare not true
/git/astronomy.git: core.bare not true
/git/bluecurve: core.bare not true
/git/bluecurve-classic-metacity-theme: core.bare not true
/git/bluecurve-gdm-theme: core.bare not true
/git/bluecurve-gnome-theme: core.bare not true
/git/bluecurve-gtk-themes: core.bare not true
/git/bluecurve-icon-theme: core.bare not true
/git/bluecurve-kde-theme: core.bare not true
/git/bluecurve-kdm-theme: core.bare not true
/git/bluecurve-kwin-theme: core.bare not true
/git/bluecurve-metacity-theme: core.bare not true
/git/bluecurve-qt-engine: core.bare not true
/git/bluecurve-xmms-skin: core.bare not true
/git/booty.git: core.bare not true
/git/chkconfig.git: core.bare not true
/git/cobbler: core.bare not true
/git/comps-extras.git: core.bare not true
/git/cronie.git: core.bare not true
/git/d-feet.git: core.bare not true
/git/desktop-effects.git: core.bare not true
/git/dhcdbd.git: core.bare not true
/git/dhcpv6.git: core.bare not true
/git/docs/about-fedora.git: core.bare not true
/git/docs/homepage.git: core.bare not true
/git/docs/install-guide.git: core.bare not true
/git/docs/readme-burning-isos.git: core.bare not true
/git/docs/readme-live-image.git: core.bare not true
/git/docs/readme.git: core.bare not true
/git/docs/release-notes.git: core.bare not true
/git/dts.git: core.bare not true
/git/echo-icon-theme: core.bare not true
/git/eunectes.git: core.bare not true
/git/fedora-gnome-theme: core.bare not true
/git/fedora-icon-theme: core.bare not true
/git/fedora-infrastructure.git: core.bare not true
/git/fedora-screensaver-theme: core.bare not true
/git/fedora-web.old.git: core.bare not true
/git/fedorabubbles-gdm-theme: core.bare not true
/git/fedoradna-gdm-theme: core.bare not true
/git/fedoradna-kdm-theme: core.bare not true
/git/fedoraflyinghigh-gdm-theme: core.bare not true
/git/fedoraflyinghigh-kdm-theme: core.bare not true
/git/fedorainfinity-gdm-theme: core.bare not true
/git/fedorainfinity-screensaver-theme: core.bare not true
/git/firstaidkit.git: core.bare not true
/git/firstboot.git: core.bare not true
/git/freeipa.git: core.bare not true
/git/func.git: core.bare not true
/git/generic-logos.git: core.bare not true
/git/gnome-applet-vm.git: core.bare not true
/git/hwdata.git: core.bare not true
/git/idm-console-framework.git: core.sharedRepository not set
/git/idm-console-framework.git/config: Not group writable (should be "0664")
/git/initscripts.git: core.bare not true
/git/koji: core.bare not true
/git/kudzu.git: core.bare not true
/git/libdhcp.git: core.bare not true
/git/liberation-fonts.git: core.bare not true
/git/livecd: core.bare not true
/git/mash: core.bare not true
/git/mirrormanager: core.bare not true
/git/mkinitrd: core.bare not true
/git/monkey.git: core.bare not true
/git/nodoka: core.bare not true
/git/olpc-vault.git: core.bare not true
/git/opyum: core.bare not true
/git/pam_krb5.git: core.bare not true
/git/perl-rpm2.git: core.bare not true
/git/pilgrim.git: core.bare not true
/git/pirut.git: core.bare not true
/git/presto: core.bare not true
/git/pump.git: core.bare not true
/git/pungi.git: core.bare not true
/git/pyblock.git: core.bare not true
/git/pyjigdo.git: core.bare not true
/git/pykickstart.git: core.bare not true
/git/pyparted.git: core.bare not true
/git/pyrpm.git: core.bare not true
/git/python-bugzilla.git: core.bare not true
/git/pyxf86config.git: core.bare not true
/git/readahead: core.bare not true
/git/redhat-rpm-config: core.bare not true
/git/releng: core.bare not true
/git/revisor: core.bare not true
/git/rhgb.git: core.bare not true
/git/rhpl.git: core.bare not true
/git/rhpxl.git: core.bare not true
/git/rpmdevtools.git: core.bare not true
/git/setuptool.git: core.bare not true
/git/sigul.git: core.bare not true
/git/snake: core.bare not true
/git/splatbind.git: core.bare not true
/git/supybot-fedora.git: core.bare not true
/git/supybot-koji.git: core.bare not true
/git/supybot-notify.git: core.bare not true
/git/symbolic.git: core.bare not true
/git/system-config-display.git.old: core.bare not true
/git/system-config-firewall.git: core.bare not true
/git/system-config-kickstart.git: core.bare not true
/git/system-config-securitylevel.git: core.bare not true
/git/system-setup-keyboard.git: core.bare not true
/git/thetango: core.bare not true
/git/umltester: core.bare not true
/git/updatinator: core.bare not true
/git/vsp.git: core.bare not true
/git/wevisor: core.bare not true
/git/yumex.git: core.bare not true
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
America wasn't founded so that we could all be better. America was
founded so we could all be anything we damned well pleased.
-- P.J. O'Rourke
13 years, 1 month
Meeting *TODAY* 2011-03-10 at 2000 UTC in #fedora-admin
by Derek Carter
The infrastructure team will be having it's weekly meeting today at
2000UTC in #fedora-admin on the freenode network.
Suggested topics (suggested by whom):
* Update on the ServerBeach Outage. (nirik et all)
* Killing CVS (nirik)
* Server updates -- report by (skvidal)
* Meeting Time/Location
We've tried to do the meeting in #fedora-admin so we can go longer
than the hour we need to get everything done. This is problematic as
people come to that channel to get help during the meeting and it is
distracting. As next week is the change in DST for the folks in the
United States, there's been a suggestion to move the meeting back to the
#fedora-meeting channel, and to 1900UTC. We need to discuss this in the
meeting today.
* Do we want to talk about the "gathering community feedback" thing any
further? (goozbach)
* Meeting tagged tickets:
https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
Submit your agenda items, as tickets in the trac instance and/or send a
note replying to this thread.
Thanks
13 years, 1 month
Gathering community feedback...
by Jóhann B. Guðmundsson
As Brian mentioned in [1],[2] as in the CWG wanted to get a constructive
feedback on COC and COCE proposed drafts from the whole community on the
FAB list highlights one issue that the project is facing as in we don't
have a good way of gathering community feedback on topics.
This issue is probably know but for some reason not being worked upon?
( Feel free to correct me if I'm wrong )
Anyway to point out the obvious encase nobody was aware of this issue.
( we have been without one for now about 15 release cycles so something
is amiss )
He posts the proposed drafts to a single mailing list which..
a)
Has a limited number of users subscribed to it
b)
Requires all members of the community to be subscribed to that
particular list.
c)
Mailing list provide the ability to see and reply to others people feed
back resulting in so called *noise* as in people reassuring their
feedback encase the message/meaning did get through and etc.. rather
then constructive discussion.
That results in an end result that is far from being effective and
reaching the whole community.
Coming up with a rough solution to gather the feedback is a no brainer
First we need a common dominator that applies to all community members
and that one is obvious FAS account.
Next we need a web server with a DB backend, hooked up to FAS with an
simple web page that the community member logs into that displays to him
what he needs to provide his feedback and two text boxes one for the
feedback and another one for any question he might have with regards to
the proposal/draft itself.
With the above in place all that is needed is to request the feedback
via our public channels like a mail to the announce or something similar.
Now the tricky part is coming up with a simple yet scalable to the total
number of community members solution, to work through all that feedback
I got couple of ideas up my sleeves for that but instead of reinventing
the wheel I propose that existing survey tools like [1],[2] be looked at
first to see how they have solved the problem we are facing.
JBG
1.
http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010525...
2.
http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010526...
3. http://www.limesurvey.org/
4. http://www.doodle.com
13 years, 1 month
Meeting *TODAY* 2011-03-10 at 2000 UTC in #fedora-admin
by Derek Carter
The infrastructure team will be having it's weekly meeting today at
2000UTC in #fedora-admin on the freenode network.
Suggested topics (suggested by whom):
* Update on the ServerBeach Outage. (nirik et all)
* Killing CVS (nirik)
* Server updates -- report by (skvidal)
* Meeting Time/Location
We've tried to do the meeting in #fedora-admin so we can go longer
than the hour we need to get everything done. This is problematic as
people come to that channel to get help during the meeting and it is
distracting. As next week is the change in DST for the folks in the
United States, there's been a suggestion to move the meeting back to the
#fedora-meeting channel, and to 1900UTC. We need to discuss this in the
meeting today.
* Do we want to talk about the "gathering community feedback" thing any
further? (goozbach)
* Meeting tagged tickets:
https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
Submit your agenda items, as tickets in the trac instance and/or send a
note replying to this thread.
Thanks
--
Derek aka goozbach
13 years, 1 month
updating elusive contributor stats
by Karsten Wade
I was looking at this nifty graphic:
http://fedoraproject.org/wiki/Statistics#Contributors
... noting that it hasn't been updated in a year.
That looks like a base FAS dump of total accounts, which I reckon is
easy enough to get. But can it be automated? Or made easy for a yokel
like me to do it?
Along the same path, how about slicing contributors in to pools by FAS
groups?
From here I reckon I've just started asking for a new tool, like
previous tools discussed, and some of which may exist, and datanommer
and ... halp?
Thanks - Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
13 years, 1 month
Updating SSL keys on fedoraproject.org 2011-03-10
by Stephen John Smoogen
Various SSL keys are aging out so we will be updating them before anyone
gets a <This CERT is not valid.> page.
We have already updated fedorahosted.org and will now be updating the
cert for the main site: fedoraproject.org.
The old certificate came from Equifax, was a 1024 bit key and had the
fingerprint:
SHA1 Fingerprint=E7:6D:26:72:D6:A2:2D:7A:5C:CF:BB:D2:05:B9:8E:7C:49:F5:F8:A8
The new certificate is issued by GeoTrust, Inc and is a 4096 bit key
with the fingerprint:
SHA1 Fingerprint=F6:D6:28:85:64:B1:11:19:38:2A:82:EF:F8:F0:22:E8:27:4F:A5:CF
Please report any problems with these certificates to
admin(a)fedoraproject.org
The change in certs will happen around 2011-03-10 20:00 UTC
Stephen Smoogen
* Seasonal Infrastructure Chief Koffee Officer
13 years, 1 month
Freeze change request: increase varnish timeout for pkgdb to 90s
by Kevin Fenzi
modules/varnish/files/proxy-el6.vcl | 1 +
modules/varnish/files/proxy.vcl | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/modules/varnish/files/proxy-el6.vcl b/modules/varnish/files/proxy-el6.vcl
index 384dedf..c66ebc6 100644
--- a/modules/varnish/files/proxy-el6.vcl
+++ b/modules/varnish/files/proxy-el6.vcl
@@ -18,6 +18,7 @@ backend mirrorlists {
backend pkgdb {
.host = "localhost";
.port = "10003";
+ .first_byte_timeout = 90s;
}
backend fas {
diff --git a/modules/varnish/files/proxy.vcl b/modules/varnish/files/proxy.vcl
index a92ce55..baf02d5 100644
--- a/modules/varnish/files/proxy.vcl
+++ b/modules/varnish/files/proxy.vcl
@@ -18,6 +18,7 @@ backend mirrorlists {
backend pkgdb {
.host = "localhost";
.port = "10003";
+ .first_byte_timeout = 90s;
}
backend fas {
13 years, 1 month
