> All three of my newly released GNOME 2.32.0 projects failed to build
> on koji (f14) today:
> I've been told it's something to do with the way glibc decides to
> interpret posix rules for character classes, which seems to have
> broken grep.
> Can we revert the new glibc from the buildsystem please, until the
> breakage is fixed upstream. Thanks.
> devel mailing list
AFAIK the following message from build log indicates incorrect regular expressions in docbook-utils:
> grep: character class syntax is [[:space:]], not [:space:]
The character class must be inside bracketed expression, thus double brackets, please see man grep. The new grep-2.7 checks for this common fault:
> grep now diagnoses (and fails with exit status 2) commonly mistyped
> regular expression like [:space:], [:digit:], etc. Before, those were
> silently interpreted as [ac:eps] and [dgit:] respectively. Virtually
> all who make that class of mistake should have used [[:space:]] or
> [[:digit:]]. This new behavior is disabled when the POSIXLY_CORRECT
> environment variable is set.
I apologize for this little bit of hubris. I recently filed my 1000th bug
report at bugzilla.redhat.com (unfortunately closed NOTABUG). I thought I'd
take a look at my statistics.
First bug filed 2002-12-07 (RHL 8.0)
Avg rate of bugs - 1 / 2.85 days
Most bugs filed in a day: 7
(Hmm, what is it about the ides of March! (probably testing new releases))
121 2010 (a little slow to hit my ~200/year pace)
19 autofs (we automount home and data dirs)
73 Package Review
91 selinux-policy ( I like quiet logwatch reports! )
112 anaconda (I do a lot of automated installs)
6 palindrome bugs:
10 CLOSED CANTFIX
134 CLOSED CURRENTRELEASE
2 CLOSED DEFERRED
75 CLOSED ERRATA
125 CLOSED NEXTRELEASE
265 CLOSED RAWHIDE
19 CLOSED UPSTREAM
70 CLOSED DUPLICATE
8 CLOSED INSUFFICIENT_DATA
99 CLOSED NOTABUG
70 CLOSED WONTFIX
18 CLOSED WORKSFORME
So 26.5% (so far) of my reports are no so useful. I shall have to try harder!
Here's to the next 1000!
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
I keep getting the same error trying to build fldigi on rawhide x64 but
not on rawhide i686 I don't know what to do to fix it. Attached is the
koji build report.
I've successfully built the package locally using mock for rawhide on
i686 but for some reason the koji build fails on x64 and I don't
understand what the output of the log is telling me.
Excerpt from log: (the only obvious error)
/usr/bin/ld: fldigi-trx.o: 'thread_id_' accessed both as normal and
thread local symbol
fldigi-trx.o: could not read symbols: File format not recognized
collect2: ld returned 1 exit status
make: *** [fldigi] Error 1
The Fedora web resources (e.g. http://fedoraproject.org/get-fedora )
continue to promote i686 installs over x86_64, the result being that
only a third of fedora users are on x86_64.
When will the Fedora project begin recommending x86_64 as the
preferred option on the relevant hardware?