Created attachment 345868 [details] ebuild, works for me Ported torrentinfo to python-r1.
I'd like to mention that the original author no longer maintains the software and values listed under HOMEPAGE and SRC_URI don't exist anymore. I have since picked-up the project at https://github.com/ShanaTsunTsunLove/torrentinfo if you're interested.
Nice :) Was looking for new version, but did not find anything related to torrentinfo in http://vrai.net/ Do you have ebuilds for your fork? Does it support python-3? What are the most important and visible changes since current portage tree version?
Created attachment 345984 [details] ebuild for fork
Mateusz, i like utf support and tests, but why you removed several useful features? 1) Timezone in 'created on' 2) --dump does not show now announce announce-list comment created by creation date encoding publisher publisher-url I use torrentinfo for viewing this info, please restore it. Why you renamed /usr/bin/torrentinfo to /usr/bin/torrentinfo.py?
Opened bugs: https://github.com/ShanaTsunTsunLove/torrentinfo/issues/5 https://github.com/ShanaTsunTsunLove/torrentinfo/issues/6 https://github.com/ShanaTsunTsunLove/torrentinfo/issues/7 https://github.com/ShanaTsunTsunLove/torrentinfo/issues/8
It's very much work in progress. I'll be looking to resolve the issues in the next few days. I do not have an ebuild.
Created attachment 346072 [details] ebuild for fork All these bugs were fixed upstream, no known regressions now, torrentinfo-1.8.3 works great, thank you Mateusz! Markos, please commit.
(In reply to comment #7) > Created attachment 346072 [details] > ebuild for fork > > All these bugs were fixed upstream, no known regressions now, > torrentinfo-1.8.3 works great, thank you Mateusz! > > > Markos, please commit. not sure if we want to have an ebuild for this fork. There might be other forks around and this may cause some confusion. Are we pretty sure the fork is the official continuation of the project? Do existing apps work with the fork?
https://encrypted.google.com/search?hl=en&inlang=en&newwindow=1&q=torrentinfo+fork does not find any other forks, 'qgrep -N net-p2p/torrentinfo' does not find anything using torrentinfo, also look at http://people.bath.ac.uk/mk440//torrentinfo/#why-fork So i think it is safe to call https://github.com/ShanaTsunTsunLove/torrentinfo new upstream.
I haven't seen any other forks and when I e-mailed the original author couple of months ago about licensing, he said that he has totally forgotten about writing it which implies that he hasn't had anyone contact him about it. >Do existing apps work with the fork? While the output is pretty close to the original, there are now new flags and few old ones have changed their meaning. The implementation (and function names etc.) was reworked so anything scripting directly against the functions defined in the file will be broken. Having said that, I haven't seen anything actually relying on torrentinfo. ‘equery d torrentinfo’ shows nothing as well. Anything that actually could possibly break can be easily fixed: it's just the matter of changing the flags as the output is largely the same. I should mention that the original had some large issues that I haven't seen mentioned anywhere (such as a typo in a variable name meaning an outright crash in certain conditions) so I don't imagine many people rely on the original behaviour for large scripts.
Thanks. Committed +*torrentinfo-1.8.4 (23 Apr 2013) + + 23 Apr 2013; Markos Chandras <hwoarang@gentoo.org> +torrentinfo-1.8.4.ebuild, + metadata.xml: + Version bump. Switch to fork in + https://github.com/ShanaTsunTsunLove/torrentinfo since upstream is dead. Bug + #466328. Thanks to Nikoli <nikoli@lavabit.com> for the ebuild + http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/torrentinfo/metadata.xml?r1=1.2&r2=1.3 http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/torrentinfo/torrentinfo-1.8.4.ebuild?revision=1.1&view=markup&pathrev=HEAD
