Of late openoffice.org and a few other packages have been not
generating delta rpms in pushes. ;(
They error with:
Error genDeltaRPM for chunkd: exitcode was 256 - Reported Error: bad cpio archive
But looking later at both rpms, things seem fine. ;(
I've talked with jdieter and we would like to add in more debugging:
<jdieter> nirik: We're still having the "bad cpio archive" with openoffice.org updates
<jdieter> I have a patched version of deltarpm available at: http://www.lesloueizeh.com/jdieter/deltarpm-3.6-0.1.20101230git.fc14.src.rpm
<jdieter> If run with -vv, it will report old rpm, new rpm, and tell us what the actual first six bytes of what's actually in the rpm
<jdieter> vs the 070701 that it's supposed to be
<jdieter> I don't have an el6 system, so it will have to be rebuilt for releng2
<jdieter> /usr/lib/python2.4/site-packages/createrepo/deltarpms.py needs to modified as well
<jdieter> The line with "makedeltarpm -v" needs to be changed to "makedeltarpm -vv"
epel5 scratch build at:
(releng02 is rhel5).
If I can get enough +'s I'd be happy to put this in place whenever.
Otherwise we can wait until next week after the freeze.
Thoughts? Comments? Other ideas?
My name is Thiago Glauco from Brazil/gmt -3.
I would like to help you from Fedora Project.
I know you are most of time at IRC but I'm following the how-to of
yours, which recommends an introduction at this list, so:
I've good skills on System administration, network management and like
to write Perl applications for Network and Server monitoring. I can
say I really love Perl and I give classes about it in Brazil.
Actually my wish to join this wonder group is a little selfish. I like
to preserve and improve my skills on server administration because I'm
working hardly with cisco and enterasys devices nowadays.
My contributions should be near to 16 hours a month.
Oh, I also know a little about C programing.
I am Prabin Kumar Datta, a Final Year IT Student of Govt. College Of
Engg. And Ceramic Tech, Belaghata. Currently, I am staying at Kolkata,
West Bengal, India.
I am an Active member of fedora Projects:
Now, I am thinking to work more and increase my participation work. I
LIKE TO JOIN sysadmin-test, sysadmin-hosted and sysadmin-web. Also,
this will help to continue my practice with what I have learn in RHCE.
My Global Certificate
* DB2 9(Database Associate).
* Cisco Networking Academy Program(WEBEL informatics kolkata) +
Cisco Certified Network Associate.
* RHCE training.
* .Net (SAP)
* XHTML (IBM).
* PHP (WEBEL)
* Advance Java (HCL CDC).
* JAVA + Advance Java + TDS + DB2 + WBS (IBM- TGMC)
* Detail Study Of Motherboard and basic Networking.
* Infosys Aspiration zonal level winner.
frankly saying I have programming knowledge which I have learned from
college, training institute
and programming contest. But I have always tried to learn everything sincerely.
Also, I believe I can work 18hours each week on fedora project.
I hope you will be kind enough to grant my request.
Have A Nice Day
by Prabin Kumar Datta
pub 2048R/1E0CFA36 2010-11-06
uid PRABIN KUMAR DATTA <linux.n.pkd(a)gmail.com>
sub 2048R/AF311EF8 2010-11-06
pkgs01 was built partially by puppet and partially by hand. We never
went through the step of completely rebuilding pkgs01 via puppet.
Recently I (re)discovered that the gitolite package has locally modified
files (4 of them: /usr/bin/gl-auth-command, /usr/bin/gl-compile-conf,
Also most unfortunately it appears I did not keep patch files around,
rather I directly modified files while attempting to make things work.
Shame on me :(
I have spent the last few days working on an updated package for
gitolite for EL6, to go from 1.5.3 to 1.5.7. Part of this motivation
was to get a new feature for error messages when attempting to clone a
repo that doesn't exist, and the other part is to have proper upstream
support for our setup, eliminating the need to locally modify files.
I have tested the new package on pkgs01.stg.phx2 and adjusted the
gitolite.rc file accordingly (changed in puppet stg branch). I've
tested that expected access works, and expected denials work as well.
I'm confident that the new package + changes from puppet will work in
I'd like to get pkgs01 production to a state where it can be built
entirely from puppet and function correctly. There are a couple
different options at this point:
A) Upgrade gitolite package and cherry-pick gitolite.rc changes from stg
B) rebuild existing gitolite package with local modifications done as
patches and make available in the infrastructure repo (and upgrade the
package in production)
C) use puppet hotfix module to stash the modified files so that puppet
puts them in place.
I'm requesting A, and offering to be on-call for this system during the
break, should something go wrong.
The changes in gitolite between 1.5.3 and 1.5.7 largely don't effect us.
The biggest change that does is proper upstream support for our setup,
where we don't have gitolite manage ssh files or repo creations. Our
ACL generation script does not need to change.
Diff of gitolite.rc changes:
diff --git a/modules/gitolite/files/distgit/gitolite.rc
index 4af1be8..03149e3 100644
@@ -89,6 +89,9 @@ $GIT_PATH="";
$GL_BIG_CONFIG = 1;
$GL_NO_DAEMON_NO_GITWEB = 1;
+$GL_NO_CREATE_REPOS = 1;
+$GL_NO_SETUP_AUTHKEYS = 1;
The upstream author of gitolite will be available during the break
should we have any emergency issues.
I'm looking for a couple +1s to attempt option A of upgrading gitolite
and merging the gitolite.rc change into production. I will make backups
of the modified files should we need to roll back the changes.
Fedora -- Freedom² is a feature!
Ok I am not doing a good job of greeting new people and helping to get
them oriented. For the many people on this list I apologize.
My time for getting people into the group has been overloaded and it
keeps getting put back. So it is time for a new approach... currently
we have a page for getting started, what to expect, and how to get
sponsored... but we have not been good about greeting people and
finding places where their skills match.
We also need to show the separation between groups, sysadmin,
sysadmin-noc, sysadmin-test, sysadmin-main etc. Some groups are going
to take a while for someone to get into (sysadmin-releng and
sysadmin-main) mainly because it is a matter of trust and work. Other
groups are 'easier' to get into but still require trust. Anyway, I
would like to get ideas on how e can do this better and move forward.
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
I'm Kavitha.C.K from India . I work as coporate trainer.I would like to be a
contributor for the fedoraproject.Kernel development and device drivers is
my passion. I know some concepts of kernel internals and drivers.I would
request for a sponsor who can guide me how to be a successfull contributor
and teach me how does the fedoraproject work.Please do the needful
I've heard that the fallout from the NFS problems in PHX2 datacenter is
still in full force.
Do we want to have our weekly meeting today? Or should we
I move to cancel and we can come back and have a proper post-mortem of
the outage next week.
That being said. Make sure to post your meeting ideas to
https://fedorahosted.org/fedora-infrastructure/report with the keyword