Hi, A user reported an issue which should have been fixed by 1.23, however it seems this ebuild uses an unofficial download location and is actually still offering 1.21. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/get_flash_videos/get_flash_videos-1.23.ebuild?view=markup Refers to: http://omploader.org/vNGdjYQ/ this is not something that we released. Please use: http://github.com/monsieurvideo/get-flash-videos/tarball/v1.23 instead. Thanks. Reproducible: Always
omploader should be banned from SRC_URI entirely.
I fixed the SRC_URI Sorry for the confusion. If only upstream provided actual tarballs instead of git tags Anyway
Technically we release a single script rather than a tarball, until I saw this ebuild I wasn't aware anyone took things straight from our git repo and built it for a distro. Once I've understood what this ebuild is doing I'll see if we can release what you want.
An ideal way is to provide a tarball with a single makefile+sources. The makefile should be a minimal as possible. Just remove all the script for project users. Finally the make file should build the manpage and the script like it does now Thank you
*** Bug 334305 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > *** Bug 334305 has been marked as a duplicate of this bug. *** Happened again :-(
$ ./get_flash_videos -v get_flash_videos version 1.22 (http://code.google.com/p/get-flash-videos/) But SRC_URI="http://github.com/monsieurvideo/get-flash-videos/tarball/v1.23 -> ${P}.tar.gz" So blame upstream for not tagging code correctly And since it seems that the actual code is 1.22 and NOT 1.23 I will drop 1.23 ebuild and bring 1.22 instead @monsieurvideo@gmail.com Any suggestion on that please?
Oops, sorry about that, seems like a bug in our migration to git, the code was actually v1.23 just it seems the version increment happened one commit after the tag. The tag is now in the correct place. (BTW: The next version will be packaged using ExtUtils::MakeMaker so it will be more like a normal perl app.)
Please do not move tags around the code. This is quite annoying for packagers. You could have used another tag like 1.23.1 or so. Anyway. I remanifest the ebuild to match the latest checksum and I hope this will stay as it is from now on