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.
stahnma
On Thu, 30 Oct 2008 23:24:13 -0500, Michael Stahnke wrote:
I think I solved the repo-closure/deps scripts issues. Now it should be back to sending only one email, (instead of 6).
If I knew where I could find the original script, I could contribute proof-reading. I dunno what infrastructure group membership is needed for that.
Still missing is to switch repoclosure arch to i686 when running for i386 repos. EL is i586 and above. Some packages are not available for i386 and create false positives (e.g. kernel related deps) unless you set the target arch to i686.
Also, there was an indentation issue in the reporting program that was causing the dependencies problems to be cleared.
Not true. Your indentation breaks it. Hint: It's supposed to stay a for...else statement, not if...else.
On Fri, 31 Oct 2008, Michael Schwendt wrote:
On Thu, 30 Oct 2008 23:24:13 -0500, Michael Stahnke wrote:
I think I solved the repo-closure/deps scripts issues. Now it should be back to sending only one email, (instead of 6).
If I knew where I could find the original script, I could contribute proof-reading. I dunno what infrastructure group membership is needed for that.
Still missing is to switch repoclosure arch to i686 when running for i386 repos. EL is i586 and above. Some packages are not available for i386 and create false positives (e.g. kernel related deps) unless you set the target arch to i686.
Also, there was an indentation issue in the reporting program that was causing the dependencies problems to be cleared.
Not true. Your indentation breaks it. Hint: It's supposed to stay a for...else statement, not if...else.
Its in our infrastructure repo -
http://git.fedorahosted.org/git/fedora-infrastructure.git/
-Mike
Michael Schwendt wrote:
If I knew where I could find the original script, I could contribute proof-reading. I dunno what infrastructure group membership is needed for that.
I believe this is from the fedora-infrastructure git repo:
git://git.fedorahosted.org/fedora-infrastructure.git http://git.fedorahosted.org/git/?p=fedora-infrastructure.git
On Fri, Oct 31, 2008 at 5:38 AM, Michael Schwendt bugs.michael@gmx.net wrote:
On Thu, 30 Oct 2008 23:24:13 -0500, Michael Stahnke wrote:
I think I solved the repo-closure/deps scripts issues. Now it should be back to sending only one email, (instead of 6).
If I knew where I could find the original script, I could contribute proof-reading. I dunno what infrastructure group membership is needed for that.
Still missing is to switch repoclosure arch to i686 when running for i386 repos. EL is i586 and above. Some packages are not available for i386 and create false positives (e.g. kernel related deps) unless you set the target arch to i686.
Hmm, that might be why I having odd issues. The problem when I was testing was that every time the dep list was blank. It seemed like that for/else combo was blanking out the container of broken deps. However, if i386 vs i686 understand kernel stuff, then there probably are not any broken deps on the repos I was able to test.
The issue with testing is that the repodata for the EPEL repos is assumed to be a local URI in the provided yum.conf. (and you can't get/send mail on pt16) So some repos I could get to and test with, others not so much.
Perhaps if just the i386/i686 issue and the single email thing are taken care of, everything will work correctly. Sorry for the confusion.
stahnma
Also, there was an indentation issue in the reporting program that was causing the dependencies problems to be cleared.
Not true. Your indentation breaks it. Hint: It's supposed to stay a for...else statement, not if...else.
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
On Fri, 31 Oct 2008 08:33:12 -0500, Michael Stahnke wrote:
Hmm, that might be why I having odd issues. The problem when I was testing was that every time the dep list was blank. It seemed like that for/else combo was blanking out the container of broken deps.
That's by design. At least one -k/--keyword value is needed to match repoids. [It could also be the reverse: match everything by default and exclude repos via cmdline args. That would be less convenient.]
With the changed indentation - it matches everything by default if no keyword is specified, - it works as before if exactly one keyword is specified, ;) and - it breaks if more than one keyword is specified.
Once more with feeling :)
Testing should be fairly simple. Just run it and disable emails. Also, you need a good yum.conf, and rc-report-epel.cfg. The checkEpel.sh script will look in the current directory, since that's how the git directory was setup.
stahnma
I apologize if you got this twice. In looking at the archives, it appears this didn't go through.
Once more with feeling :)
Testing should be fairly simple. Just run it and disable emails. Also, you need a good yum.conf, and rc-report-epel.cfg. The checkEpel.sh script will look in the current directory, since that's how the git directory was setup.
stahnma
On Thu, 30 Oct 2008, Michael Stahnke wrote:
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.
What are the testing proceedures?
-Mike
infrastructure@lists.fedoraproject.org