Mike McGrath (mmcgr...@redhat.com) said:
What does everyone else have?
1) no frozen rawhide which requires faster composes
2) dist-git
3) A functioning message bus with services passing messages
I think I know what you'd want from us on 2 and 3, can you think of
anything off hand
Toshio Kuratomi (a.bad...@gmail.com) said:
I have a new deltarpm package built for the rel-eng repo:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1721745
I can put it into the rel-eng repository to update the servers but who
do I talk to about testing it? We'll also need approval
Toshio Kuratomi (a.bad...@gmail.com) said:
I can put it into the rel-eng repository to update the servers but who
do I talk to about testing it? We'll also need approval to brakinfra
change freeze to deploy it once it's tested.
If it's in rawhide, it's already being tested to produce
Jon Stanley (jonstan...@gmail.com) said:
I'd like some mailman experts (if we have any) to take a look at this
procedure to migrate lists from redhat.com to lists.fp.o and let me
know if there's something obviously missing from it or if there's some
way that it can be improved. Feel free to
Mike McGrath (mmcgr...@redhat.com) said:
So I was going to finish the upgrade to cvs1 on Thursday or Friday. Both
Jesse and Toshio are out of the country though and it strikes me as a bad
idea to make potentially massive changes to that box without having at
least one of them around
Mike McGrath (mmcgr...@redhat.com) said:
I'm all for pruning, lets have a plan for it though. Anyone see any
reason not to have these up there?
Should we come up with some test for what does and does not get removed?
I agree. Here's what I am going by:
a) content that has
Chuck Anderson (c...@wpi.edu) said:
The infrastructure should either delete and regenerate drpms after the
rpm signatures have changed or they should use the code fragment from
https://fedorahosted.org/koji/ticket/38#comment:3 to attach rpm
signatures to deltarpms.
That's *really* hard,
Seth Vidal (skvi...@fedoraproject.org) said:
That's *really* hard, as there's not any state to track when packages
have been signed out from under the prior delta rpms.
The simplest solution would be to just nuke the old ones by hand.
when they are signed? or nuke them in createrepo?
When
seth vidal (skvi...@fedoraproject.org) said:
In the last day I set up cgit as a replacement for gitweb. It's only in
testing right now. You can see it here:
http://hosted2.fedoraproject.org/cgit/
I'd like to see it replace gitweb as our web-based git repo browser.
However, it will mean
Jesse Keating ([EMAIL PROTECTED]) said:
In order to push out the first round of Fedora 10 updates, a few changes
need to be made in the infrastructure.
1) add the 10 release to fedora-updates-push in puppet
2) Update bodhi with 10 mash configs
Can I get a few +1s on this?
+1
Bill
Mike McGrath ([EMAIL PROTECTED]) said:
So I was going through some old tickets and stumbled across this:
https://fedorahosted.org/fedora-infrastructure/ticket/164
I gave it a quick look over and I'm not against this integration but I'm
generally apathetic about it. So I ask if anyone
Mike McGrath ([EMAIL PROTECTED]) said:
[1]https://fedorahosted.org/fedora-infrastructure/ticket/714
So I guess the best thing from here is to send an email to each group
notifying them of what has happened and why we'd like to remove their
project. tell them how to get the code off if
Jesse Keating ([EMAIL PROTECTED]) said:
So I realized something last night. We created a user masher to have
the ability to write to /mnt/koji/mash/ but not any of the other koji
space. This is useful to prevent too much damage from a horribly wrong
rawhide compose. To make things easier
Nigel Jones ([EMAIL PROTECTED]) said:
Problem here, is that there are a LOT of old tarballs in that folder, which
leaves me wondering if we should do a spring clean ~1 mo after release.
Until we get something like correspondingsource up and running, we don't
have a good mechanism for weeding
Mike McGrath ([EMAIL PROTECTED]) said:
The *real* freeze has started.
I'd like to build a different box for the secondary.fedoraproject.org
bits. Initial space requirements were off, I'd like to move the bits to a
host in PHX. This will require kicking a new host with enough storage.
Mike McGrath ([EMAIL PROTECTED]) said:
We now have all the tapes we need to do koji backups of /mnt/koji. Can I
get a +1?
Backups are good. +1
Bill
___
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
Toshio Kuratomi ([EMAIL PROTECTED]) said:
The Bugzilla sync scripts are currently running on a RHEL4 machine on
Jeremy's desk. There are a few problems with them that would be hard to
fix without RHEL 5. Since it would be helpful to move this out to a Fedora
box anyway so anyone can
Jon Stanley ([EMAIL PROTECTED]) said:
John Poelstra and I were just thinking about a mailing list for
watching incoming bugs. Unfortunately, I don't know that there's the
right combination of checkboxes in Bugzilla to just get mail about new
bugs. However, filtering based on mail header
Jon Stanley ([EMAIL PROTECTED]) said:
freemedia is a closed list with private archives, because of the
personal information to be found there. fedora-board-list is another
one, and I'm sure there's more, dealing with security for example.
There needs to be a method of exception to the rule.
Toshio Kuratomi ([EMAIL PROTECTED]) said:
Here's a short script to test our TG apps run via supervisor for excessive
memory usage and restart them if necessary. We could run this via cron in
alternate hours on each app server. Does this seem like a good or bad idea
to people?
It's a
seth vidal ([EMAIL PROTECTED]) said:
build: koji, plague, local mirrors for building, cvs, bodhi, pkgdb
distribution: mirrormanager, mirrormaster, staging, torrent
primary site: fp.o, wiki, docs, start.fp.o
meta services all of the above will or do require:
vpn, fas[2], puppet,
Ignacio Vazquez-Abrams ([EMAIL PROTECTED]) said:
Just saw this, figured someone here might be interested.
http://www.fusionio.com/
$30/GB. That's gonna hurt.
Bill
___
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
Mike McGrath ([EMAIL PROTECTED]) said:
Just letting you guys know I'll be off on Monday, going to a cubs game and
generally doing everything you've seen in:
Woo, our infrastructure leader, the sausage king of Chicago!
Bill
___
Axel Thimm ([EMAIL PROTECTED]) said:
The interesting part is to create a graph over time to answer the
question whether the 13 month EOL is really paying off. And perhaps on
base of that graph one could revise this decision. At the very leats
it would be interesting to notice the upgrade
Toshio Kuratomi ([EMAIL PROTECTED]) said:
Depends...
What is the reason for those boxes to be on Fedora instead of RHEL?
For the mash/bodhi box, it's because it requires yum-3.2.x and current
createrepo. At the moment it's running them recompiled for FC6, and,
well, I'd rather not do that
Karel Zak ([EMAIL PROTECTED]) said:
My wish is git rebase always after upgrade to new upstream code.
The current make prep is nightmare...
See Linux kernel. That's normal that people maintain their patches
outside official tree(s) for pretty long time. The modern VCS is the
right tool
Jeremy Katz ([EMAIL PROTECTED]) said:
Right. I really don't think we want to just take our current system,
switch out CVS, and end up with all of the same workflows. The change
should be more about how do we improve workflows. That means thinking
about things like:
* How do we make it
Stephanos Manos ([EMAIL PROTECTED]) said:
Apologies for the noise if this is not the right place to report this
it seams that the createrepo script didn't run correctly for updates-7
updates-7-testing since it includes the debuginfo packages
The problem is visible either with cli yum or
Luke Macken ([EMAIL PROTECTED]) said:
By the looks of the fedora-release-tools module, there are two scripts
that have been used to sign packages, ftsign and fedorasign, both of
which call /usr/local/bin/rpm-4.1-sign, which is a symlink to
/usr/lib/rpm/rpmk.
... which doesn't interact well
Mmm, plumbing. bodhi is heading for production soon. To push updates, what
bodhi currently does is, for any update:
- sign the package
- copy the package to a 'staging' tree of the entirety of updates
- read a static list of packages that should be multilib, act on that
- run createrepo
- check
The board has sent a list of suggested names for Fedora 7 to our legal
department, and they have responded with the names that have passed preliminary
legal approval.
Please vote for your favorite choice at:
https://admin.fedoraproject.org/voting/vote.cgi
The choices are 'Lee',
Dimitris Glezos ([EMAIL PROTECTED]) said:
Our translators have made it clear they want to use a SCM for the translations
and said an *additional* web-based tool would be nice. So, let's first create
our SCM and we'll see about whether we should use pootle.
Use *one* SCM. How to gate currently
Máirín Duffy ([EMAIL PROTECTED]) said:
- Is the main Fedora Project wiki up for redesign as well? I think it
could use a little tweaking.
Well, there has been talk of moving the frontpage to a static
site that is actually designed, along with the docs and other
more static content. Doesn't
33 matches
Mail list logo
