Why not add the new 1.50 beta 3 to portage? Copied the 1.42 ebuild, except the upstream version is 1.50b3 instead of 1.50_beta3... So I hardcoded MY_PV and set S="${WORKDIR}/${PN}-${MY_PV}". If anyone knows how to manipulate MY_PV with versionator that would be dandy... Attached ebuild Reproducible: Always Steps to Reproduce: 1. Look for the new transmission 1.50 betas in portage 2. They're not there!
Created attachment 179848 [details] ebuild for transmission-1.50b3
(In reply to comment #0) > Why not add the new 1.50 beta 3 to portage? well, because portage is not,generally, a place for alpha/beta/gamma/omega/unstable prereleases... especially when there is a stable release on a horizon should be wontfix or later i think :)
Transmission 1.50 is out.
http://bugs.gentoo.org/show_bug.cgi?id=259385
*** Bug 259385 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Transmission 1.50 is out. > The 1.42 ebuild works fine for 1.50 by the way, except the patch fails. Commented it out and transmission compiles and runs
(In reply to comment #6) > The 1.42 ebuild works fine for 1.50 by the way, except the patch fails. > Commented it out and transmission compiles and runs > It fails when the configure script tests intltool in ppc arch: ... checking for intltool >= 0.23... found ./configure: line 24486: test: : integer expression expected configure: error: Your intltool is too old. You need intltool 0.23 or later.
Transmission 1.51 is out.
1.51 got the same intltool error on amd64 for me, i don't know anything about automake n stuff but i solved it by installing step by step via ebuild and using the solution given here: http://forums.fedoraforum.org/showthread.php?t=155606 dunno how to fix this properly in the ebuild so i just leave that to s.o. else. here's the new flag-patch for 1.51 btw besides this error from autotools the ebuild works fine just by renaming
Created attachment 184140 [details, diff] new flag patch for transmission-1.51
After renaming transmission-1.50_beta3.ebuild to transmission-1.51.ebuild, I was getting the following errors: >>> Unpacking source... >>> Unpacking transmission-1.51.tar.bz2 to /var/tmp/portage/net-p2p/transmission-1.51/work >>> Source unpacked in /var/tmp/portage/net-p2p/transmission-1.51/work >>> Configuring source in /var/tmp/portage/net-p2p/transmission-1.51/work ... * * ERROR: net-p2p/transmission-1.51 failed. * Call stack: * ebuild.sh, line 49: Called src_configure * environment, line 2805: Called econf '--enable-gtk' '--enable-libnotify' '--disable-dependency-tracking' '--with-wx-config=no' * ebuild.sh, line 548: Called die * The specific snippet of code: * die "no configure script found" * The die message: * no configure script found I found that by hashing out this line: S="${WORKDIR}/${PN}-${MY_PV}" It was able to move past the configure step and actually compile. Not that it would matter, but I'm on amd64 here.
Transmission 1.52 is out. Zero-day report, I know.
If nobody in net-p2p prefers me not to, I'd like to take care of this bump (and maybe the package itself).
A new maintainer would be great since the ebuild in the testing tree (1.42) doesn't even contain a working init script. See bug http://bugs.gentoo.org/show_bug.cgi?id=238260 Also transmission got bumped to version 1.52.
Committed 1.52 to tree.
