On Jan 30, 2008 5:44 AM, Sebastian Nowicki firstname.lastname@example.org wrote:
I was just packaging btg in order to move it to community, but I realised that rb_libtorrent is in unsupported. I looked at the details page and it appears pressh moved it from community. Was there any reason for moving it back to unsupported?
No other reason that we had a lengthy discussion about orphaned packages in [community]. rb_libtorrent was on this list as it was a package of zeus, who is not a TU anymore. None of the current TUs was interested. You can find the complete discussion on the mailing list, an the list of removed packages here: http://bbs.archlinux.org/viewtopic.php?id=43043
You are free to move it back to [community] of course.
There's also a small annoyance with the libtorrent and rb_libtorrent packages - they conflict. The two packages provide different libraries, but conflict due to having the same paths. There is a package in unsupported called librtorrent  which resolves the issue. Since libtorrent already exists in community, the package, along with rs_rtorrent, should be either removed or the changes should be implemented in libtorrent. There was also some discussion about this conflict on the bbs , which provides more detail. It appears Debian is having the same problem . Their solution is to rename the packages to libtorrent-rakshasa and libtorrent-rasterbar, which may be better package names than rb_libtorrent and librtorrent.
I think it would be better if these packages wouldn't conflict, but excessive renaming of packages is probably unnecessary.
 http://aur.archlinux.org/packages.php?do_Details=1&ID=14940  http://aur.archlinux.org/packages.php?do_Details=1&ID=10572  http://bbs.archlinux.org/viewtopic.php?pid=234044#p234044  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402462
Contact Jeff (codemac) if he does not reply here, he is the maintainer of libtorrent in [community] I see from the web interface. I guess you guys can work something out.