Hello Fukui, I was able to have a proper look at the package now, and its huge diff between the latest release and this one (although most of it is related to autotools).
The packaging changes (copyright and changelog) are good, but you forgot to push pristine-tar and upstream. It's impossible for me to review the whole of upstream's diff due to the autotools changes, but I did check the source diff on Github (which was smaller). I then noticed that the release being packaged is marked as a "Pre-release" and "for testing purposes". https://github.com/libyal/libewf-legacy/releases/tag/20140814 Considering this, I think we need to have a good reason for picking that release, and this includes testing the reverse dependencies to make sure they don't break. Do you reckon there's a specific need (eg.: it fixes certain issues) for this release? To be clear, I think it's fine (and we should) to update packages mostly to be up-to-date with upstream, but that's as long as the release is not marked as beta, rc, and such. When that's the case, then we need to be more careful and confirm the need to package that release. In the case of libewf, if we were to go that route, we could even consider packaging from the new repo (which is also in "experimental" stage): https://github.com/libyal/libewf Thank you for contributing! -- Samuel Henrique <samueloph>
