This plugin allows Pidgin to get current song from the MPRIS-aware players and set it as its status Reproducible: Always
Created attachment 162447 [details] pidgin-mpris-0.2.4.ebuild attahced the proposed ebuild
I will be testing this against Audacious shortly.
Created attachment 163972 [details] pidgin-mpris-0.2.4.ebuild Thank you for your ebuild. I have made some slight modifications: - corrected the copyright header (please confirm that you agree) - removed src_compile (the default is identical, so no need to specify it) However, I can't currently commit it, because: Connecting to m0n5t3r.info|86.120.77.234|:80... failed: Connection timed out. Retrying. If you have the distfile and expect the site to return, please let me know. If you want to do a small homepage with download area for it (perhaps on atheme infrastructure?), that would fix everything. Sorry for the delayed response.
(In reply to comment #3) > Thank you for your ebuild. I have made some slight modifications: > - corrected the copyright header (please confirm that you agree) You can do whatever you want with it. > - removed src_compile (the default is identical, so no need to specify it) Yeah, I'm a newbie at writing ebuilds. > However, I can't currently commit it, because: > Connecting to m0n5t3r.info|86.120.77.234|:80... failed: Connection timed out. > Retrying. > > If you have the distfile and expect the site to return, please let me know. If > you want to do a small homepage with download area for it (perhaps on atheme > infrastructure?), that would fix everything. Sorry, but I don't have it anymore, but I'll try to contact the author. > Sorry for the delayed response. No problem. Cristi
It seems that now the website is up and running. Please fetch it from there, or just use the ebuild. Cristi
(In reply to comment #5) > It seems that now the website is up and running. > Please fetch it from there, or just use the ebuild. Tried that, it came back up but still doesn't give me what I want: Connecting to m0n5t3r.info|86.120.75.214|:80... connected. HTTP request sent, awaiting response... 403 Forbidden
Cristi, could you reopen this bug if the software author starts supporting automated distfile fetches? Without that, I'm afraid I can't package it. Sorry about that.
Created attachment 166696 [details] Downloaded File for ebuild Downloading the file directly from the website worked fine for me, though I have yet to try it out. (http://m0n5t3r.info/work/pidgin-mpris) I noted that this ebuild was for the 0,2,4 version, as the link from their website links to the 0.2.6 version, but the 0.2.4 version is still there. http://m0n5t3r.info/stuff/pidgin-mpris//pidgin-mpris-0.2.4.tar.bz2 I hope this helps, I really want this plugin working. If anything needs to be done then pleas let me know, though this is my first post on bugzilla, so treat me as a newbie. Though I am willing to learn in the little spare time I have.
(In reply to comment #8) > Downloading the file directly from the website worked fine for me, though I > have yet to try it out. (http://m0n5t3r.info/work/pidgin-mpris) If you try again using wget, you'll see what I'm complaining about. I can't add ebuilds for sites that block automated downloads. After all, that is what portage does. It automatically downloads sources for you and compiles them. You will likely receive a 403 error for the same URL that works perfectly in a browser.
Hmm, I wasn't expecting that. I suppose it is not possible to have the file placed on a gentoo mirror server, I see that links has such a mirror. So failing that, could the ebuild be modified to be Fetch restricted?
author here... sorry for the hassle, the wget problem was due to mod_security overdoing its job, it looks fixed now; also, I switched my nameservers away from xname, so there should be no more extended downtimes (it was DNS related).
Thank you gentlemen. Let's get this show on the road.
+*pidgin-mpris-0.2.6 (01 Oct 2008) + + 01 Oct 2008; <chainsaw@gentoo.org> +metadata.xml, + +pidgin-mpris-0.2.6.ebuild: + Initial commit, ebuild based on the one submitted by Cristi Magherusan + <majeru@gentoo.ro> in bug #234193. With thanks to upstream developer Sabin + Iacob for resolving an automated fetch issue. You should find this ebuild within the tree within the next 2 hours.
Great stuff, is there any reason why this is marked as amd64 only though? This isn't listed in the specification on the plugin's homepage.
If you want this package keyworded for your architecture, you should file a separate bug for that. The developer that committed your ebuild uses AMD64 hardware. As such, that is what the initial keyword is.
