mezz wrote:What kind of change did you made in the 0.5.4.1 tarball? It has been re-rolled two times. The first one was because of a lot of files that wasn't supposed to be in and tweaked a bit in setup.py for debian. The second one, I am not sure. Somehow I lost the second tarball to compare with the third tarball. I need to know what kind of change for security reason in our ports tree, because the checksum has been changed. Thanks.
MD5 (deluge-0.5.4.1.tar.gz) = 80aeb297b519d42ef3a0ff2d3c2dbecb
SHA256 (deluge-0.5.4.1.tar.gz) = 954fe23378431d6ab2444361b76653babb5767aef28081e62c434d1f4ccfc2b5
SIZE (deluge-0.5.4.1.tar.gz) = 1480071
MD5 (deluge-0.5.4.1.tar.gz) = 36debac83b41f1697da6805e8cc79435
SHA256 (deluge-0.5.4.1.tar.gz) = 242ced6abeda90e93c70b03fe3b84bed5a85059e5fcbd3faec7ef0ac29d52c87
SIZE (deluge-0.5.4.1.tar.gz) = 1473118
markybob wrote:i will commit to this, though, since i can see how this could be a problem: from this point on, if we need to reroll a tarball, there'll be a posting for it our on our news section of deluge-torrent.org. fair enough?
markybob wrote: * Fix up pieces, peers and files plugins
praveenmarkandu wrote:AWESOME! making great progress. i feel like learning phython suddenly.
Users browsing this forum: Bing [Bot] and 2 guests