pidgin version bump to 2.52 Reproducible: Always
You mean "2.5.2", not "2.52". Also, it's only been three days, and it's considered polite to wait a week before posting version bump bugs.
Thanks for the version bump report, and thanks Randall for the version correction. However, I'd like to clarify Gentoo developers' attitude about "0-day bump requests": most of us are happy to get them! There have been problems in the past where impatient users would file grumpy bugs trying to get developers to update faster, but polite reports (that are not duplicates) are welcome -- they just tell developers that somebody is enthusiastic about the package and eagerly awaiting the update. There are a few developers who like the 1 week waiting period because they are already drowning in bug mail, but they are in the minority -- if you do happen to file a quick bump request to one of these developers, they can politely request that you wait a week next time.
Anyone who wants 2.5.2 can simply: # cd /usr/portage/net-im/pidgin # cp pidgin-2.5.1.ebuild pidgin-2.5.2.ebuild # ebuild pidgin-2.5.2.ebuild digest # emerge -av pidgin I tested it, and it works (compiles successfully and runs) on amd64 [although the source tarball does not exist on Gentoo's mirrors, but emerge simply jumped to sourceforce and succeeded downloading it anyways...] * of course, be advised that this will be overwritten on the next emerge --sync and could result in a downgrade if you sync & update your system before an official change is pushed to the portage tree.
bumped, sorry for the delay, I somehow missed this bug..
(In reply to comment #3) > Anyone who wants 2.5.2 can simply: > > # cd /usr/portage/net-im/pidgin > # cp pidgin-2.5.1.ebuild pidgin-2.5.2.ebuild > # ebuild pidgin-2.5.2.ebuild digest > # emerge -av pidgin > > I tested it, and it works (compiles successfully and runs) on amd64 [although > the source tarball does not exist on Gentoo's mirrors, but emerge simply jumped > to sourceforce and succeeded downloading it anyways...] > > * of course, be advised that this will be overwritten on the next emerge --sync > and could result in a downgrade if you sync & update your system before an > official change is pushed to the portage tree. > BTW, though it's no longer relevant to this bug, a suggestion for the future: instead of doing what you specify there, you can copy the entire /usr/portage/app-category/program/ folder to your local Portage overlay (e.g., /usr/local/portage/app-category/program/) and put the renamed ebuild there. This way, your changes won't be overwritten by emerge --sync.
