emerge -f transmission These are the packages that would be fetched, in order: Calculating dependencies... done! [ebuild U ] net-p2p/transmission-1.0.4 [1.0.1] USE="gtk" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB >>> Emerging (1 of 1) net-p2p/transmission-1.0.4 to / * transmission-1.01.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking transmission-1.01.tar.bz2 ;-) ... From ebuild: MY_PV="1.01" should be MY_PV="1.04" Reproducible: Always
(In reply to comment #0) > From ebuild: MY_PV="1.01" should be MY_PV="1.04" Erm, it just shouldn't have any such thing hardcoded. Why are we using a different versioning scheme from upstream?
(In reply to comment #1) > Erm, it just shouldn't have any such thing hardcoded. Why are we using a > different versioning scheme from upstream? It could be because the upstream provides tarballs in a weird versioning scheme, the file is "transmission-1.04.tar.bz2" when for protage's sake it should be "transmission-1.0.4.tar.bz2" (note the dot between minor and bug-fix number).
fixed and fixed.