Daniel wrote > Osamu Aoki wrote: > > Since there is no upstream changelog included (not even URL pointer) it > > is quite difficult to find what does it mean by > > upstream changelog is the obligation of upstream, I'm sure Dustin will > include it in the future.
Shall I do a git log dump between releases, and package that in the release tarball? > > This package seem to use tar ball from Ubuntu. > > no, I'm using the official upstream tarball. Ubuntu does use the > official tarball too. Correct, we're using the same tarball. > > If it is too much to download git changelog with git-log, please include git > > location URL somewhere. > > > > Git URL > > git://git.kernel.org/pub/scm/linux/kernel/git/mhalcrow/ecryptfs-utils.git > > > > http://www.kernel.org/pub/scm/linux/kernel/git/mhalcrow/ecryptfs-utils.git > > > > Or browsable one: > > > > http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=summary > > this should be included on the upstream website, I'm sure Dustin can add > this. It's already at: * https://edge.launchpad.net/ecryptfs There are git-clone instructions, as well as the git summary under the "Homepage" link. > > Current copyright has only reference to > > Download: https://launchpad.net/ecryptfs/trunk > > ...were the official upstream tarballs are published. Correct. > > Current control has: > > Homepage: https://launchpad.net/ecryptfs > > ...where the official upstream website is. Correct. :-Dustin
signature.asc
Description: This is a digitally signed message part
