ebuild for tcpreplay-3.4.0 will be attached. Reproducible: Always
Created attachment 183907 [details] new version 3.4.0 ebuild Made from version 3.3.2 without changes.
I reduced the keywords to "~x86", since it's new, and that's all it's been built on.
Please only apply ebuild patches and only when you did really important changes to the ebuild. There's no need to mess with KEYWORDS as there are arch-herds for this in Gentoo and the devs will most likely just revbump the ebuild and move all arches in KEYWORDS to unstable. Reassigning to netmon herd.
Created attachment 184060 [details] tcpreplay ebuild file (Unix) Changed from DOS to Unix text file format so ebuild doesn't complain about it.
(In reply to comment #3) > Please only apply ebuild patches and only when you did really important > changes to the ebuild. I'm not really sure what this sentence means. Don't post ebuild files? People grab ebuild files out of version-bump bugs all the time. Patches aren't as convenient. Does it mean don't attach anything to version bump requests? Don't post anything unless it's important? Go away and leave us alone? When I do the work to get a package working or upgraded, I like to post what I have in a format that others can use. Gentoo needs to be receptive to that. Don't turn away free development. > There's no need to mess with KEYWORDS as there are arch-herds for this in > Gentoo and the devs will most likely just revbump the ebuild and move all > arches in KEYWORDS to unstable. OK, but it was x86 and amd64, and I didn't want to imply that it had been tested on those platforms to that degree.
(In reply to comment #5) > > Please only apply ebuild patches and only when you did really important > > changes to the ebuild. > I'm not really sure what this sentence means. Don't post ebuild files? People > grab ebuild files out of version-bump bugs all the time. Patches aren't as > convenient. Does it mean don't attach anything to version bump requests? Don't > post anything unless it's important? Go away and leave us alone? This sentense means that if you want to make developer's life easier you need to attach patch instead of full ebuild. Patch clearly shows what was left untouched in ebuild and what was changed and thus greatly simplifies review of changes. > When I do the work to get a package working or upgraded, I like to post what I > have in a format that others can use. Gentoo needs to be receptive to that. > Don't turn away free development. We don't turn away. We just suggest you how to make our life easier. If you are not interested in that I'm sorry but we prefer to educate our users instead of keep silence. > > There's no need to mess with KEYWORDS as there are arch-herds for this in > > Gentoo and the devs will most likely just revbump the ebuild and move all > > arches in KEYWORDS to unstable. > OK, but it was x86 and amd64, and I didn't want to imply that it had been > tested on those platforms to that degree. Nobody have tested that's why we have unstable branch. It exists exactly for testing purposes. tcpreplay-3.4.1 was added to the tree. Thank you for report.
