I've got a few patches lined up for Koji, and I'd love to see them get
reviewed and merged. I'm happy to answer any questions about them.
(Please also let me know if there is a more appropriate avenue to get
these reviewed and merged.)
https://fedorahosted.org/koji/ticket/224 Avoid pgdb's _quoteparams()
https://fedorahosted.org/koji/ticket/227 fix pkgorigins.gz file creation in F16
These two are necessary to make Koji work on Fedora 16.
https://fedorahosted.org/koji/ticket/225 better examples for Kerberos
auth options
This is essentially a doc fix, should be really simple.
https://fedorahosted.org/koji/ticket/229 make SCM URL validity check
more verbose
This is an attempt to make the errors more helpful when Koji can't
understand the user's SCM URL. As a Koji newbie it was difficult for
me to figure out the precise SCM string format that Koji expects;
these error messages helped me troubleshoot my way through the fog.
The next two are "bigger" logic changes.
https://fedorahosted.org/koji/ticket/226 Don't rewrite HTTPS URLs as HTTP
This is a tweak to Koji-web so that I don't get kicked back to an HTTP
URL when I click "logout".
https://fedorahosted.org/koji/ticket/230 add HTTP "proxy" option to builder
This is a feature that implements an HTTP proxy option for the
builders. It allows me to easily use my Squid box as a cache so I
don't have to hit a mirror over the internet each time. This mailing
list thread from 2008 was the inspiration:
https://lists.fedoraproject.org/pipermail/buildsys/2008-November/002271.html
- Ken
I have a small private Koji setup here which has worked well for quite
some time. I have only two builders, both running up to date x86_64
Fedora 16. I am having a strange issue where when I build Asterisk 10
for Fedora 15 x86_64 on one of the builders, Asterisk will fail to start
with an invalid 'opcode message'. However, If I build it on the other
builder, Asterisk will work as expected.
I am truly not sure where to begin, but I've only seen this issue start
to occur within the last month or so.
The only real difference between the two builders are the CPUs. Showing
the first of each below, the builder that produces Asterisk builds which
fail is:
~]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
stepping : 7
microcode : 0x25
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx
smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts
dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 6784.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
And the builder that produces a working Asterisk build is:
~]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 2.80GHz
stepping : 4
microcode : 0x4
cpu MHz : 2800.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc pebs bts nopl pni dtes64 monitor ds_cpl est
cid cx16 xtpr pdcm lahf_lm
bogomips : 5585.86
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
The (first) CPU of the Fedora 15 x86_64 system on which I am attempting
to run the Asterisk build is:
~]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 3
cpu MHz : 2800.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc pebs bts nopl pni dtes64 monitor ds_cpl cid
cx16 xtpr
bogomips : 5585.42
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
As I said, I'm not even sure where to begin, so I'm not sure that
information is helpful.
The build log which creates the inoperable Asterisk:
[1080956.984634] asterisk[2294] trap invalid opcode ip:516e52
sp:7fffcfef3600 error:0 in asterisk[400000+197000]
is here:
http://messinet.com/~amessina/asterisk_invalid_opcode_build.log
The 'good' build log is here:
http://messinet.com/~amessina/asterisk_success_build.log
The spec file is 99.9% the same as Jeffrey Ollie's official Fedora spec
file and is here:
http://messinet.com/~amessina/asterisk.spec
Thanks in advance for your help. -A
--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E