Bug#767021: unblock: volatility/2.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the package volatility. This package is very important for forensics activities, allowing a full memory analysis. The current version, that adds support to Windows 8 memory dumps (and others) was released in end of August. This is a complex program and I spent time doing several tests and talking with the developers. Another point is that I needed to submit a new dependency, distorm3, to NEW and it was accepted on 2014-10-19 (I sent to NEW in 2014-09-20). I delayed the packaging because the upstream changed his site (from GitHub to another place[1]) and I had no information about this change and a new version via watch file. I uploaded the final package yesterday (Sunday) and I need one day only to get it in testing. So, please, reduce the migration time to 5 days. The package is fully tested, clean and working fine. The changelog can be viewed here[2]. Thanks a lot in advance. Regards, Eriberto [1] http://www.volatilityfoundation.org [2] http://metadata.ftp-master.debian.org/changelogs/main/v/volatility/unstable_changelog unblock volatility/2.4-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767021: unblock: volatility/2.4-1
On Mon, 2014-10-27 at 16:57 -0200, Joao Eriberto Mota Filho wrote: Please unblock the package volatility. This package is very important for forensics activities, allowing a full memory analysis. [...] I uploaded the final package yesterday (Sunday) and I need one day only to get it in testing. So, please, reduce the migration time to 5 days. According to my maths, tonight's britney run is day one of volatility's 10 day count. Counting forward another nine days takes us to the package being eligible for migration in the evening run on the 5th, which is (just) before the freeze. Unless you plan to upload a further update to the package, I believe volatility will manage to migrate before the freeze without our intervention. Given the size of the diff, I'd personally be happier leaving that to happen. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
