Bug#767021: marked as done (unblock: volatility/2.4-1)
Your message dated Mon, 27 Oct 2014 21:42:10 +0100
with message-id <544EAE22.2020708@thykier.net>
and subject line Re: Bug#767021: unblock: volatility/2.4-1
has caused the Debian Bug report #767021,
regarding unblock: volatility/2.4-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
767021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767021
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@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
--- End Message ---
--- Begin Message ---
On 2014-10-27 21:34, Adam D. Barratt wrote:
> 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
>
>
I agree with Adam, there is no need for an unblock for the current
upload. Accordingly, I will close the bug.
~Niels
--- End Message ---
Reply to: