[gentoo-science] ChangeLog in the overlay

[gentoo-science] ChangeLog in the overlay

[Justin Lecher (jlec)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi everyone,

What is your opinion on dropping the ChangeLog in the overlay in
favour of the git log as it has been done in the tree?

Justin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0

iQJ8BAEBCgBmBQJWGOn1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiyssQAJjDVYlY+FvmKAvpGDKaB5Tl
5w9107xsSnNv/CsWUUppXkV9rIi/YkJgU1zvMRcR9RRTraTBgDSJrprZeLT/UqfA
Iy7vbldImBw58lUUE7M32X5pH7qsPJqMn7w7qOYvUL9Y/9uCeU7XDYDxX8yBYsEa
LGcBg4DfWEGV0iKtHlShOeW3mUincfWwe79nP/DnCVZruVunzwKiAz2LJpxLgTpo
/Muj/9ZmG4QLsTjo70Pcrf8tYTzpX27PWyU0gZi62yEhT+1ab1sZ44192mMvSQAt
Y8Wu+/Zm4tnQbW1E+7xJaTXxpt+eadRFlcBAKLVXzyp8kGJkoowVEodrmQvvY+fE
mEqWpv4w3iL9pfNq1wHlUAucTX8DpHA0AQsPn+/RwYflKiZ9iJDFl15s8tdJBH6Y
Zat1mchYT7bbtWKwQ1D02DBddxiMCDkNe11oIA56FKHGcuWcmQoLeYvS9zxhUT43
IA3V0SDq7b2MKVpVBd7qPTpijjqdnUYR0y6Q7N46jOSfGeP9iPXFZ/H44wGs3vYb
TFcS9VfupXZ+J786avY59X3iH+AigUdCub+MfB7fdZgMr8SKm9O9E4Mju8GF33ws
jIxrMyChcY65rdgUkY6C0olQBRVwxflaCmOUjsW7e+cgGvD+M9ggtDRUB//c+yZu
WfplwzhEFR+6oo3HI7bl
=5qTU
-----END PGP SIGNATURE-----

Re: [gentoo-science] ChangeLog in the overlay

[François Bissey]

I am annoyed by the tree in that regard. A simple user doesn’t have access
to the changelog anymore because the git history is not shipped as far
as I can see.

The overlay would be a bit better because we can still call git log on it.

Any tools out there to get changelog without syncing the tree with git?

François

> On 10/10/2015, at 23:35, Justin Lecher (jlec) <jlec@gentoo.org> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi everyone,
> 
> What is your opinion on dropping the ChangeLog in the overlay in
> favour of the git log as it has been done in the tree?
> 
> Justin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0
> 
> iQJ8BAEBCgBmBQJWGOn1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
> OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiyssQAJjDVYlY+FvmKAvpGDKaB5Tl
> 5w9107xsSnNv/CsWUUppXkV9rIi/YkJgU1zvMRcR9RRTraTBgDSJrprZeLT/UqfA
> Iy7vbldImBw58lUUE7M32X5pH7qsPJqMn7w7qOYvUL9Y/9uCeU7XDYDxX8yBYsEa
> LGcBg4DfWEGV0iKtHlShOeW3mUincfWwe79nP/DnCVZruVunzwKiAz2LJpxLgTpo
> /Muj/9ZmG4QLsTjo70Pcrf8tYTzpX27PWyU0gZi62yEhT+1ab1sZ44192mMvSQAt
> Y8Wu+/Zm4tnQbW1E+7xJaTXxpt+eadRFlcBAKLVXzyp8kGJkoowVEodrmQvvY+fE
> mEqWpv4w3iL9pfNq1wHlUAucTX8DpHA0AQsPn+/RwYflKiZ9iJDFl15s8tdJBH6Y
> Zat1mchYT7bbtWKwQ1D02DBddxiMCDkNe11oIA56FKHGcuWcmQoLeYvS9zxhUT43
> IA3V0SDq7b2MKVpVBd7qPTpijjqdnUYR0y6Q7N46jOSfGeP9iPXFZ/H44wGs3vYb
> TFcS9VfupXZ+J786avY59X3iH+AigUdCub+MfB7fdZgMr8SKm9O9E4Mju8GF33ws
> jIxrMyChcY65rdgUkY6C0olQBRVwxflaCmOUjsW7e+cgGvD+M9ggtDRUB//c+yZu
> WfplwzhEFR+6oo3HI7bl
> =5qTU
> -----END PGP SIGNATURE-----
> 

Re: [gentoo-science] ChangeLog in the overlay

[Justin Lecher (jlec)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 10/10/15 12:42, François Bissey wrote:
> I am annoyed by the tree in that regard. A simple user doesn’t have
> access to the changelog anymore because the git history is not
> shipped as far as I can see.
> 
> The overlay would be a bit better because we can still call git log
> on it.
> 
> Any tools out there to get changelog without syncing the tree with
> git?
> 
> François
> 

Hi,

the ChangeLogs are recreated for rsync. If you are using rsync as
normal users should do, you will have the ChangeLog in place.
egencache --update-changelogs is used for that.

Justin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0

iQJ8BAEBCgBmBQJWGRS+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiF20P/RxNOLtmWNZZHbOnphLa0Bdc
kvbjIL6D91WakdvDvL7fP1YdYdabp+3RZm7gM7dy+NtbCFdUwdnZrVuOfn3uL5O3
ILX9HFlB2KJh2szlXF+5qyDsPDLaS1j6RgWpRggFUqXtyWm7ElRWlO7pv7DhgZ/R
+aGAJJvhW50qQlpU69/2+B+9xfJrn601NphiOwwORJhg7Zk/H5KvrCzXfmwu+nUZ
4sJVxyhMuPqGzCDixhucwVjx7ffJtcpXArXoz+1JNR9Uc0fmn9f86RUaQsfUeHc3
HcdFxWb/5EDFqgbuawbot5ImFH75OtzcUN0rr/pPFG8RumWf6IpfUFilFsCxKbzZ
X3WuvvLTwsIG2CyMPrp0l+uvQxDiP6KvsNIkL4Pr1oxWkvDRo9x+PfFKVi9JEpTP
kJt1k1i/Tg98JXHRl9ltXy1xLngzsIdiJNt9EsN/2Me5zL/AU8fy3leG9Xpbj7s0
p4uL6RWPTPJXfCoDFUGisQTht5HhSAXz0ot9iuryhRKsNvxVLksl82sWnrarRuP8
Hppu8fZuUZNWWNvKuUyCKMKYydJWXGY4n7HJxN/W3vSQzeB2dlIEBtXGd8Ecbs/R
+lyd8XfCk4I9CiASXKX+VEbpp47vXJ23IGHr2g2oWxWOV48zxuvQCKfSuTuFws2j
MU3iyufyQRbSlNB+qayL
=oNjO
-----END PGP SIGNATURE-----

Re: [gentoo-science] ChangeLog in the overlay

[Olivier Huber]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

Hi,

On Sat, Oct 10, 2015 at 8:38 AM, Justin Lecher (jlec) <jlec@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 10/10/15 12:42, François Bissey wrote:
>> I am annoyed by the tree in that regard. A simple user doesn’t have
>> access to the changelog anymore because the git history is not
>> shipped as far as I can see.
>>
>> The overlay would be a bit better because we can still call git log
>> on it.
>>
>> Any tools out there to get changelog without syncing the tree with
>> git?
>>
>> François
>>
>
> Hi,
>
> the ChangeLogs are recreated for rsync. If you are using rsync as
> normal users should do, you will have the ChangeLog in place.
> egencache --update-changelogs is used for that.

I use rsync to get the portage tree and the Changelog have not been
touched since the migration. Did I miss something here ?

Out of curiosity, I tried egencache --update-changelogs on the
gentoo-science repo. It created most Changelog, while complaining
several time and failing due to I think, utf8 characters being used.
See the attached file.

<shameless plug>

A few weeks back I was frustrated enough with the lack of Changelog
that I hacked a small tool to query the changes made on a file using
the GitHub API. You don't need to clone any git repo. It tries to
mimic the Changelog layout and colors. It's far from being perfect,
but it does the job for me. It is now available here:
https://github.com/xhub/changelog-gentoo Maybe it is also useful for
others ...

</shameless plug>

-- 
Olivier

[-- Attachment #2: egencache.txt --]
[-- Type: text/plain, Size: 3777 bytes --]

$ egencache --update-changelogs --repo science
ERROR: unexpected git file status for dev-cpp/eigen: [uT, ueigen-3.2.4.ebuild]
ERROR: unexpected git file status for dev-cpp/eigen: [uT, ueigen-3.2.2.ebuild]
ERROR: unexpected git file status for dev-python/brewer2mpl: [uT, ubrewer2mpl-1.4.1.ebuild]
ERROR: unexpected git file status for dev-python/ipykernel: [uT, uipykernel-4.0.3.ebuild]
ERROR: unexpected git file status for dev-python/line_profiler: [uT, uline_profiler-1.0.ebuild]
ERROR: unexpected git file status for dev-python/matlab_wrapper: [uT, umatlab_wrapper-0.9.6.ebuild]
ERROR: unexpected git file status for dev-python/prettyplotlib: [uT, uprettyplotlib-0.1.7.ebuild]
ERROR: unexpected git file status for dev-python/pyfftw: [uT, upyfftw-0.9.2.ebuild]
ERROR: unexpected git file status for dev-python/python-ivi: [uT, upython-ivi-0.14.9.ebuild]
ERROR: unexpected git file status for dev-python/simplepam: [uT, usimplepam-0.1.5.ebuild]
ERROR: unexpected git file status for sci-astronomy/missfits: [uT, umissfits-2.8.0.ebuild]
ERROR: unexpected git file status for sci-astronomy/psfex: [uT, upsfex-3.9.1.ebuild]
ERROR: unexpected git file status for sci-astronomy/psfex: [uT, upsfex-3.17.0.ebuild]
ERROR: unexpected git file status for sci-astronomy/sextractor: [uT, usextractor-2.19.5.ebuild]
ERROR: unexpected git file status for sci-astronomy/skymaker: [uT, uskymaker-3.10.5.ebuild]
ERROR: unexpected git file status for sci-astronomy/stiff: [uT, ustiff-2.4.0.ebuild]
ERROR: unexpected git file status for sci-astronomy/stuff: [uT, ustuff-1.26.0.ebuild]
ERROR: unexpected git file status for sci-astronomy/swarp: [uT, uswarp-2.38.0.ebuild]
ERROR: unexpected git file status for sci-astronomy/weightwatcher: [uT, uweightwatcher-1.12.ebuild]
ERROR: unexpected git file status for sci-biology/biopieces: [uT, ubiopieces-0.51.ebuild]
ERROR: unexpected git file status for sci-biology/biopieces: [uT, ubiopieces-0.51.ebuild]
ERROR: unexpected git file status for sci-biology/ngs_backbone: [uT, ungs_backbone-1.4.0.ebuild]
ERROR: unexpected git file status for sci-biology/tablet: [uT, utablet-1.14.04.10.ebuild]
ERROR: unexpected git file status for sci-biology/tablet: [uT, utablet-1.14.04.10.ebuild]
ERROR: unexpected git file status for sci-libs/asl: [uT, uasl-0.1.5.ebuild]
ERROR: unexpected git file status for sci-libs/asl: [uT, uasl-0.1.5.ebuild]
ERROR: unexpected git file status for sci-libs/blas-reference: [uT, ublas-reference-20131116-r1.ebuild]
ERROR: unexpected git file status for sci-libs/blas-reference: [uT, ublas-reference-20131116.ebuild]
ERROR: unexpected git file status for sci-libs/blas-reference: [uT, ublas-reference-20120925.ebuild]
ERROR: unexpected git file status for sci-libs/clfft: [uT, uclfft-0.9999.ebuild]
ERROR: unexpected git file status for sci-libs/clfft: [uT, uclfft-2.4.ebuild]
Traceback (most recent call last):
  File "/usr/lib/python-exec/python2.7/egencache", line 1154, in <module>
    sys.exit(egencache_main(sys.argv[1:]))
  File "/usr/lib/python-exec/python2.7/egencache", line 1136, in egencache_main
    gen_clogs.run()
  File "/usr/lib/python-exec/python2.7/egencache", line 896, in run
    self.generate_changelog(cp)
  File "/usr/lib/python-exec/python2.7/egencache", line 791, in generate_changelog
    c, --, .]).rstrip(n).split(n)
  File "/usr/lib/python-exec/python2.7/egencache", line 755, in grab
    encoding=_encodings[stdio], errors=strict)
  File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 209, in _unicode_decode
    s = unicode(s, encoding=encoding, errors=errors)
  File "/usr/lib64/python2.7/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: utf8 codec cant decode byte 0xe1 in position 14: invalid continuation byte

[gentoo-science] Re: ChangeLog in the overlay

[Nicolas Bock]

On Mon, Oct 12, 2015 at 4:58 AM, Marius Brehler
<marbre@linux.sungazer.de> wrote:
>
>
> On 10/10/2015 12:35 PM, Justin Lecher (jlec) wrote:
>> Hi everyone,
>>
>> What is your opinion on dropping the ChangeLog in the overlay in
>> favour of the git log as it has been done in the tree?
>>
>> Justin
>>
>
> Hi,
> I prefer to drop the ChangeLogs. Since we give a lot advices and many
> contributes push their changes incremental without using 'repo-commit
> -t', or re-commit changed ebuilds, ChangeLogs often blow up. For example
> see [1], which is AFAIR not the worst one.
> Regards
>
Hi Marius,

out of curiosity: What does the -t option do? And how does one
re-commit a change using repoman?

Thanks,

Nick

> Marius
>
>
>
> [1]
> https://github.com/gentoo-science/sci/blob/master/dev-python/matrix2latex/ChangeLog

[gentoo-science] Re: ChangeLog in the overlay

[Nicolas Bock]

On Tue, Oct 13, 2015 at 2:42 PM, Marius Brehler
<marbre@linux.sungazer.de> wrote:
> On 10/13/2015 02:08 PM, Nicolas Bock wrote:
>> On Mon, Oct 12, 2015 at 4:58 AM, Marius Brehler
>> <marbre@linux.sungazer.de> wrote:
>>>
>>>
>>> On 10/10/2015 12:35 PM, Justin Lecher (jlec) wrote:
>>>> Hi everyone,
>>>>
>>>> What is your opinion on dropping the ChangeLog in the overlay in
>>>> favour of the git log as it has been done in the tree?
>>>>
>>>> Justin
>>>>
>>>
>>> Hi,
>>> I prefer to drop the ChangeLogs. Since we give a lot advices and many
>>> contributes push their changes incremental without using 'repo-commit
>>> -t', or re-commit changed ebuilds, ChangeLogs often blow up. For example
>>> see [1], which is AFAIR not the worst one.
>>> Regards
>>>
>> Hi Marius,
>>
>> out of curiosity: What does the -t option do? And how does one
>> re-commit a change using repoman?
>>
>> Thanks,
>>
>> Nick
>
>
> Hi,
> the -t option prevents adding a ChangeLog entry:
>
>   -t, --trivial           trivial changes (do not add a ChangeLog entry)
>
>
> With re-commiting, I mean one could reset without loosing the
> modifications with 'git reset --soft HEAD^' (or by specifying a commit
> hash/tag/e.g.), apply the new changes/caring for the annotations and
> than just executing 'repo-commit <previous commit message>' again.
> I hope that answers your question, if not please let me know.
> Regards
>
Thanks, that explains it! I missed that you are using 'repo-commit'
and not 'repoman' :) Is repo-commit recommended over repoman?

> Marius

Re: [gentoo-science] ChangeLog in the overlay

[François Bissey]

On 10/11/15 02:38, Justin Lecher (jlec) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 10/10/15 12:42, François Bissey wrote:
>> I am annoyed by the tree in that regard. A simple user doesn’t have
>> access to the changelog anymore because the git history is not
>> shipped as far as I can see.
>>
>> The overlay would be a bit better because we can still call git log
>> on it.
>>
>> Any tools out there to get changelog without syncing the tree with
>> git?
>>
>> François
>>
>
> Hi,
>
> the ChangeLogs are recreated for rsync. If you are using rsync as
> normal users should do, you will have the ChangeLog in place.
> egencache --update-changelogs is used for that.
>

Sorry to take so long, it's been very busy around here.
Well it looks like I am not set to do that my Changelog
files are frozen from before the change to git.

Francois

[gentoo-science] Re: ChangeLog in the overlay

[Nicolas Bock]

Hi Marius,

thanks for the details! I noticed that lately repoman is adding the
category/package name at the beginning of the commit message. Good to
know about the --echangelog=n option.

Thanks again!

Nick

On Wed, Oct 14, 2015 at 12:16 AM, Marius Brehler
<marbre@linux.sungazer.de> wrote:
>
>
> On 10/13/2015 10:50 PM, Nicolas Bock wrote:
>> On Tue, Oct 13, 2015 at 2:42 PM, Marius Brehler
>> <marbre@linux.sungazer.de> wrote:
>>> On 10/13/2015 02:08 PM, Nicolas Bock wrote:
>>>> [..]
>>>> Hi Marius,
>>>>
>>>> out of curiosity: What does the -t option do? And how does one
>>>> re-commit a change using repoman?
>>>>
>>>> Thanks,
>>>>
>>>> Nick
>>>
>>>
>>> Hi,
>>> the -t option prevents adding a ChangeLog entry:
>>>
>>>   -t, --trivial           trivial changes (do not add a ChangeLog entry)
>>>
>>>
>>> With re-commiting, I mean one could reset without loosing the
>>> modifications with 'git reset --soft HEAD^' (or by specifying a commit
>>> hash/tag/e.g.), apply the new changes/caring for the annotations and
>>> than just executing 'repo-commit <previous commit message>' again.
>>> I hope that answers your question, if not please let me know.
>>> Regards
>>>
>> Thanks, that explains it! I missed that you are using 'repo-commit'
>> and not 'repoman' :) Is repo-commit recommended over repoman?
>
> I actually don't know if there is a recommendation. I use 'repo-commit'
> for short commit messages and 'repoman commit', if line breaks in the
> commit message are desired. By the way, 'repoman commit --echangelog=n',
> actually does the same as 'repo-commit -t'.
>
> Regarding re-commiting, 'repo-commit' is a little easier to handle as it
> allows to pass the commit message via the shell. 'repoman commit' allows
> this when passing '-m "commit message"', but does not add the
> category/packagename in front of the commit message.
> Thus, copying the commit message and using 'repoman commit' requires
> more effort than using 'repo-commit'
> Regards
>
> Marius

Re: [gentoo-science] ChangeLog in the overlay

[Justin Lecher (jlec)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 10/10/15 12:35, Justin Lecher (jlec) wrote:
> Hi everyone,
> 
> What is your opinion on dropping the ChangeLog in the overlay in 
> favour of the git log as it has been done in the tree?
> 
> Justin
> 


Hi,

I dropped the Changelogs now. Everyone should be able to read the
changes from either GH or gitweb.gentoo.org.

Justin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0

iQJ8BAEBCgBmBQJWjnKVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmifjEQALSIX8qewzJBCcqG4ZNwMXOg
4lj7PxiGdkhGSiG7/fiEqu9Fmf3AA5cwC4CEIBMP2wW/C1WFY5P9gTPG55A6L7Al
zQsalvvwZlWgo+HvyAyrEPhDMkKW4URDr2UCkEVxtT1xW1Ndx5VubnQzYzszZ2dV
BWZn3KlnBtwK7rrv63EoRsrIHvq0Eu7Lcu47cSNWr05uphPaIFFCijCkx41jb+pH
L+lZeIWAL5IkOZHBGu8t1w0+oW+gogPT4K46D4K3cImL4LJeVscsstOuOTfMk2Ws
nwLfKLocq3u6TMPHkdTAYjmWy8FK55FT5Ie4HKH1RKs8YHlt4ePGiHeBgOGo4IMg
supOLAb/nOultNzSAqnxeXqOI7YJRBK4fuvu3VoRrFVi/G7vIfD30KZWY/vDSMK7
n5lm8Lm5Ju8aLHTUOY7gh89NJyMziC2EA87fU8wRRU0Q1IbSmf/V1RiFCy9aa3v4
ZxwzLgzL/O31iuiHAMg/J3eITZa+r9iQxAFjC4S3YQ8K6357wxGnR0qQ43XJjS+D
jktpGI/D1neYF5/cfBkBHivwnu4lvWI0kcYuPfr8WztN7qFhyWcfFllsY1CE7q6D
2N5HLrP7vumjyDmK8vFK5O3Iyq1djfYQOTQP3ygK7fQAUf1gujihm+Y1C58uBMS4
7EnCXt+Bm5UDVROHirHt
=QBG8
-----END PGP SIGNATURE-----