It's been in the tree for more than 30 days and it's a binary package (therefore not getting any stable-er). Bug #376741 is a portage bug, which has been worked around in the ebuild. Targets: x86, amd64 Thanks!
Please hide: * QA Notice: Files built without respecting LDFLAGS have been detected * Please include the following list of files in your report: * /opt/google/talkplugin/libnpgtpo3dautoplugin.so * /opt/google/talkplugin/libnpgoogletalk64.so
works for me on amd64
(In reply to comment #1) > Please hide: > > > * QA Notice: Files built without respecting LDFLAGS have been detected > * Please include the following list of files in your report: > * /opt/google/talkplugin/libnpgtpo3dautoplugin.so > * /opt/google/talkplugin/libnpgoogletalk64.so Fixed. QA_DT_HASH uses regex not fmatch pattern.
ditto Ago
amd64: pass
(In reply to comment #0) > It's been in the tree for more than 30 days and it's a binary package > (therefore not getting any stable-er). > > Bug #376741 is a portage bug, which has been worked around in the ebuild. > > Targets: x86, amd64 > > Thanks! The problem with it is that google may opt to remove the package from its servers and the ebuild breaks, as in Bug #377915
(In reply to comment #6) > (In reply to comment #0) > > It's been in the tree for more than 30 days and it's a binary package > > (therefore not getting any stable-er). > > > > Bug #376741 is a portage bug, which has been worked around in the ebuild. > > > > Targets: x86, amd64 > > > > Thanks! > > The problem with it is that google may opt to remove the package from its > servers and the ebuild breaks, as in Bug #377915 Well, there is not much we can do! 'Stable' in this case means 'working'. And at least the x86 pkg can also be found outside google: http://apt-int.jolicloud.org/mirrors/pool/restricted/g/google-talkplugin/
As discussed in bug #357475, binary only applications should not go to stable tree when upstreams tends to remove old tarballs. amd64 will pass. If you would like the policy to change, please bring this issue to gentoo-dev. Last time I checked this was an unofficial policy and not documented anywhere
(In reply to comment #8) > As discussed in bug #357475, binary only applications should not go to stable > tree when upstreams tends to remove old tarballs. amd64 will pass. If you would > like the policy to change, please bring this issue to gentoo-dev. Last time I > checked this was an unofficial policy and not documented anywhere Sound reasonable to me! As it is not documented, I was just doing as it was done for sci-geosciences/googleearth. As google-talkplugin-1.8.0.0 is stable (and not available anymore) what do we do now?
(In reply to comment #9) > (In reply to comment #8) > > As discussed in bug #357475, binary only applications should not go to stable > > tree when upstreams tends to remove old tarballs. amd64 will pass. If you would > > like the policy to change, please bring this issue to gentoo-dev. Last time I > > checked this was an unofficial policy and not documented anywhere > Sound reasonable to me! As it is not documented, I was just doing as it was > done for sci-geosciences/googleearth. > > As google-talkplugin-1.8.0.0 is stable (and not available anymore) what do we > do now? @hwoarang: Any opinion?
Murphy's law: Google has removed google-talkplugin-2.1.7.0.