[update] volatility 2.3.1

[jul_bsd@…]

bump to 2.3.1 + change of homepage + variant devel

[mf2k (Frank Schima)]

In the future, please append ".diff" to your patch name so Trac knows it is a patch file and shows differences visually.

The devel variant is not acceptable for 2 reasons:

• We do not allow different versions based on a selected variant. The proper course is to create a sub-port named volatility-devel.
• We do not allow a version based on the trunk of a subversion server. That is not supportable. You can pick a revision number however.

Also, the line python.default_version 27 can be removed since that is the default anyway.

[jul_bsd@…]

Most patch, I saw in the tree where just patch-* so I took the same format. do I need to report as a but if name is not correct?

Where is the documentation for sub-port? nothing in ​http://guide.macports.org. or a template/example?

I understand perfectly for trunk problem. After, what to do where there is lot of modifications and no release, or other appeal to try a recent one. I'm not sure all versioning tools accept a date as tag (svn, git, hg, ...). For volatility, can switch revision on {2014-02-01}

[ryandesign (Ryan Carsten Schmidt)]

Replying to jul_bsd@…:

Most patch, I saw in the tree where just patch-* so I took the same format. do I need to report as a but if name is not correct?

Well that's a slightly different thing. You're talking about patches that a port will use. Frank was talking about the patch you attached to this ticket, which will not be used by a port, but will be used by a committer to update a port.

But for both types of patch files, adding the ".diff" extension allows us to view the diff properly in Trac, so it's desired.

The decision to name patchfiles (those patchfiles that portfiles use) "patch-*.diff" was made probably 5-7 years ago if I recall. Ports that have not been touched since before then might still have patch names that don't conform to that pattern. Patch naming is not the most important thing in the world, but we have this standard naming convention that we decided on, so it's nice to use it.

Where is the documentation for sub-port? nothing in ​http://guide.macports.org. or a template/example?

I don't believe we have any documentation written yet. Grep the existing Portfiles for "subport" if you want to find example ports.

More comments:

• Is the custom livecheck needed? Usually googlecode projects don't need a custom livecheck; the default usually works fine.
• Could you tell us more about the "FIXME" comment you added, and what difficulties you're running into telling MacPorts to download and use that second distfile?

[jul_bsd@…]

• ok for patch naming
• for livecheck, with and without => needed

  $ port -v livecheck volatility
  volatility seems to have been updated (port version: 2.3.1, new version: 2.3)
  $ port -v livecheck volatility
  volatility seems to be up to date
  

• found the relevant command. fixed but I don't know how to specify that there is a tar.gz file and a zip file. it's not blocking (I keep it as archives in share/examples and there are more zip inside) but macports tries to uncompress it.

[jul_bsd@…]

For unknown reason (BadContent ???), I get "Erreur: Forbidden" when trying to upload new diff

see ​http://pastebin.com/2hWUAwHa

[mf2k (Frank Schima)]

More comments:

• You still need to add a svn revision to your devel sub-port.
• You hard-coded the version in the checksum. Use the ${version} variable instead.

[jul_bsd@…]

asked modifications

[jul_bsd@…]

• port lint --nitpick
• livecheck
• /tab/spacex4/

[jul_bsd@…]

• add more memory system profiles
• add subport volatility1 if someone needs
• plugins variant: timeliner (disabled as it's only for 2.0 currently), mimikatz, plugins (not used/dependencies not compiling)

the python deps are not resolving well if I don't set to py27- (py- -> py24- where default should be py27-)

[jul_bsd@…]

• Add memory profiles for linux too
• subport volatility1
• some plugin variants as work in progress, mostly mimikatz
• mode line

[jul_bsd@…]

For some reason, triggered Forbidden error and can't upload (very annoying that it doesn't give a hint of what is blocking ...)

put it here ​http://pastebin.com/7fYqdAHJ

[mf2k (Frank Schima)]

Can you please explain the mimikatz variant? It seems to be downloading an unversioned file called mimikatz.py from googlecode. What if it changes?

[jul_bsd@…]

I'm not really sure how to handle it if it changes. variant install failed

• either a way to download "​https://code.google.com/p/hotoloti/source/browse/mimikatz.py?spec=svn8ef1c09b65de434aad4f2d6afcdacdcebc9cf252&r=8ef1c09b65de434aad4f2d6afcdacdcebc9cf252" to get a specified revision
• either doing a git call for that but how to specify to use normal fetch for main source and git clone for this file?

  git.url             https://code.google.com/p/hotoloti/
  git.branch       8ef1c09b65de
  

[jul_bsd@…]

bump to 2.4.0

[jul_bsd@…]

• 2.4.1
• build/destroot/install ok
• run ok
• separate port for Profiles #46873

can remove/comment mimikatz part if blocking

[jul_bsd@…]

Trac Error when adding file...

​http://pastebin.com/jW1eSAgn

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

looks like this has moved to ​http://www.volatilityfoundation.org/ ​https://github.com/volatilityfoundation/volatility

[kurthindenburg (Kurt Hindenburg)]

I went ahead and committed what I have r145494 - let me know of any issues.