http://sourceforge.net/projects/libgaminggear/files/ 0.7.0 is out
Created attachment 398672 [details] New ebuild for sys-apps/roccat-tools-3.2.0
Created attachment 398674 [details] New ebuild for dev-libs/libgaminggear-0.7.0
Could someone who has rights please update description of this bug to be "sys-apps/roccat-tools-3.2.0 and its dependency dev-libs/libgaminggear-0.7.0 version bump".
explicitly assign to proxy maintainer, and CC to Gentoo @proxy-maint team give maintainer permissions (edit, close.. etc)
here are ebuild made by proxy-maitainer. why is it even not confirmed, not telling of portage tree update?
(In reply to Perfect Gentleman from comment #5) > here are ebuild made by proxy-maitainer. why is it even not confirmed, not > telling of portage tree update? If I could understand just what you mean I'd have a chance of supplying an answer. I think this is language barrier. I think you mean why has it not been acted on by us and added. Well, basically there is no reason other than no-one has yet. As users and proxy maintainers you are basically reliant upon us serving your requests in our own free time if and when we can. I shall do this tomorrow since it's too late at night atm unless another of the devs does it first.
(In reply to Ian Delaney from comment #6) > (In reply to Perfect Gentleman from comment #5) > > here are ebuild made by proxy-maitainer. why is it even not confirmed, not > > telling of portage tree update? > > If I could understand just what you mean I'd have a chance of supplying an > answer. I think this is language barrier. I think you mean why has it not > been acted on by us and added. Well, basically there is no reason other > than no-one has yet. As users and proxy maintainers you are basically > reliant upon us serving your requests in our own free time if and when we > can. I shall do this tomorrow since it's too late at night atm unless > another of the devs does it first. by "it" I meant bug. It's been ten 10 days as proxy-maintainer published ebuilds, but bug is not confirmed neither resolved. I mean it's too long, isn't it?
(In reply to Perfect Gentleman from comment #7) > > by "it" I meant bug. It's been ten 10 days as proxy-maintainer published > ebuilds, but bug is not confirmed neither resolved. I mean it's too long, > isn't it? Let's put that another way. How long is a piece of string. The next day I attempted to find this bug and seems I brought up the version bump req for the version -3.0.0 inadvertently and found this again by chance. There is no decisive answer to that question. This is opensource, voluntary efforts. Replies are hit and miss, no matter how that my not seem good enough to you. I can show you far worse. *libgaminggear-0.7.0 (24 Mar 2015) 24 Mar 2015; Ian Delaney <idella4@gentoo.org> +libgaminggear-0.7.0.ebuild, -libgaminggear-0.2.0.ebuild, -libgaminggear-0.3.0.ebuild, -libgaminggear-0.4.0.ebuild: bump; rm old ~/cvsPortage/gentoo-x86/sys-apps/roccat-tools $ sudo ebuild roccat-tools-3.2.0.ebuild clean install >>> Completed installing roccat-tools-3.2.0 into /mnt/gen2/TmpDir/portage/sys-apps/roccat-tools-3.2.0/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version usr/lib64/libroccat.so.3.2.0 usr/bin/roccateventhandler usr/lib64/libroccatwidget.so.3.2.0 ecompressdir: bzip2 -9 /usr/share/doc No indication of any new input devices. *roccat-tools-3.2.0 (24 Mar 2015) 24 Mar 2015; Ian Delaney <idella4@gentoo.org> +roccat-tools-3.2.0.ebuild, -roccat-tools-2.4.0.ebuild: bump; rm 1 old
