Hi,
I've just submitted mono-2.10.1 for building and it's failed giving me
make[8]: Entering directory `/builddir/build/BUILD/mono-2.10.1/mcs/tools/gacutil' MCS [basic] gacutil.exe Inconsistency detected by ld.so: dl-deps.c: 623: _dl_map_object_deps: Assertion `nlist > 1' failed!
I had this a short while back with x86_64 but the problem seems to have been fixed on x86_64 at least.
Anyone knows what gives on this?
http://koji.fedoraproject.org/koji/getfile?taskID=2898569&name=build.log
TTFN
Paul
On 03/10/2011 12:05 AM, Paul Johnson wrote:
Hi,
I've just submitted mono-2.10.1 for building and it's failed giving me
make[8]: Entering directory `/builddir/build/BUILD/mono-2.10.1/mcs/tools/gacutil' MCS [basic] gacutil.exe Inconsistency detected by ld.so: dl-deps.c: 623: _dl_map_object_deps: Assertion `nlist > 1' failed!
That's probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=673014
I believe it should be fixed with glibc-2.13.90-6, but the update is currently stuck in Bodhi with 7 karma and not getting pushed even to the requested updates-testing repo: https://admin.fedoraproject.org/updates/glibc-2.13.90-6
Perhaps a Bodhi admin could take a look at the update.
On Sat, 12 Mar 2011 14:33:34 +0200 Kalev Lember kalev@smartlink.ee wrote:
That's probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=673014
I believe it should be fixed with glibc-2.13.90-6, but the update is currently stuck in Bodhi with 7 karma and not getting pushed even to the requested updates-testing repo: https://admin.fedoraproject.org/updates/glibc-2.13.90-6
Perhaps a Bodhi admin could take a look at the update.
ok, it should be headed to testing in the next testing push. (which will be after the next branched compose lands, which has been taking a while).
The maintainer should be able to push it to stable after that...
kevin
On 03/12/2011 04:33 AM, Kalev Lember wrote:
On 03/10/2011 12:05 AM, Paul Johnson wrote:
Hi,
I've just submitted mono-2.10.1 for building and it's failed giving me
make[8]: Entering directory `/builddir/build/BUILD/mono-2.10.1/mcs/tools/gacutil' MCS [basic] gacutil.exe Inconsistency detected by ld.so: dl-deps.c: 623: _dl_map_object_deps: Assertion `nlist> 1' failed!
That's probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=673014
I believe it should be fixed with glibc-2.13.90-6, but the update is currently stuck in Bodhi with 7 karma and not getting pushed even to the requested updates-testing repo: https://admin.fedoraproject.org/updates/glibc-2.13.90-6
Perhaps a Bodhi admin could take a look at the update.
As I noted in the update several days ago, the update was marked obsolete/unstable when it reached karma of -3. It got to -7 at some point. This should have been submitted as a new update instead of editing the broken one.
On Sat, 2011-03-12 at 16:06 -0800, Christopher Aillon wrote:
On 03/12/2011 04:33 AM, Kalev Lember wrote:
I believe it should be fixed with glibc-2.13.90-6, but the update is currently stuck in Bodhi with 7 karma and not getting pushed even to the requested updates-testing repo: https://admin.fedoraproject.org/updates/glibc-2.13.90-6
Perhaps a Bodhi admin could take a look at the update.
As I noted in the update several days ago, the update was marked obsolete/unstable when it reached karma of -3. It got to -7 at some point. This should have been submitted as a new update instead of editing the broken one.
I expressed that sentiment some months ago and was told that editing updates is accepted practice. The real problem is that the karma was not reset. I filed a ticket about it:
https://fedorahosted.org/bodhi/ticket/413
On Sun, 2011-03-13 at 15:48 -0400, Matt McCutchen wrote:
On Sat, 2011-03-12 at 16:06 -0800, Christopher Aillon wrote:
On 03/12/2011 04:33 AM, Kalev Lember wrote:
I believe it should be fixed with glibc-2.13.90-6, but the update is currently stuck in Bodhi with 7 karma and not getting pushed even to the requested updates-testing repo: https://admin.fedoraproject.org/updates/glibc-2.13.90-6
Perhaps a Bodhi admin could take a look at the update.
As I noted in the update several days ago, the update was marked obsolete/unstable when it reached karma of -3. It got to -7 at some point. This should have been submitted as a new update instead of editing the broken one.
I expressed that sentiment some months ago and was told that editing updates is accepted practice. The real problem is that the karma was not reset. I filed a ticket about it:
Right, editing the update should be the best practice, but Bodhi kinda needs to handle it a bit better, flagging up the change and re-setting the karma when an update is edited.