This is a bugfix release. A test suite is shipped with it. hppa, ppc, ppc64 and ia64, you can opt out, if you don't want to stabilise it. Thanks.
amd64 stable
ia64 will pass
ppc64 and ppc are seeing a test failure... TestFailure: where: tests/t_atom.cc:96 in void<unnamed>::local::verifyCompare(const std::string&, const std::string&, int) message: atom1 : string : =x11-libs/gtk+-2.10.14 valid : true negated : false exact : true qualified package name: false prefix : = category : x11-libs name : gtk+ version tokens : 2, 10, 14 revision : r0 atom2 : string : =x11-libs/gtk+-2.12.0-r2 valid : true negated : false exact : true qualified package name: false prefix : = category : x11-libs name : gtk+ version tokens : 2, 12, 0 revision : r2 expected: -1 FAIL: t_atom ideas?
(In reply to comment #3) > ppc64 and ppc are seeing a test failure... > > > TestFailure: > [...] > Hmm, I cannot reproduce this failure on both amd64 and x86; however, when trying to "# emerge -av =gatt-0.6.1" i get: " * checking gatt-0.6.1.tar.bz2 ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/distfiles/gatt-0.6.1.tar.bz2 !!! Reason: Filesize does not match recorded size !!! Got: 293715 !!! Expected: 218632 " Maybe this is somehow connected to your problems....
(In reply to comment #3) > ppc64 and ppc are seeing a test failure... > > > TestFailure: Btw.: Can you reproduce this with gatt-9999?
Yes, the failure is present in -9999 as well. Opfer, if you want access to a ppc box, i can arrange.
Stable for HPPA.
Created attachment 161542 [details] gatt-ppc.patch This patch should fix >=app-portage/gatt-0.6.1 on PPC. Please test.
would one of the devs related to gatt make a -r1 so I can test and stabilize it for ppc and ppc64? If nobody has time, i suppose I could do this.
Created attachment 161546 [details, diff] gatt pcc patch upps, wrong patch.
I can confirm this works.
I have bumped gatt to 0.6.1-r1 with Matthais' patch.
ppc and ppc64 keyworded