Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] what happened to ChangeLog for packages?
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
deefster
Tux's lil' helper
Tux's lil' helper


Joined: 19 Apr 2004
Posts: 77

PostPosted: Wed Nov 23, 2016 12:32 pm    Post subject: [solved] what happened to ChangeLog for packages? Reply with quote

/usr/portage/category/package/ChangeLog files no longer seem to exist

as a result

equery changes -l <package> no longer seems to work


Last edited by deefster on Thu Nov 24, 2016 1:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1181
Location: Italy

PostPosted: Wed Nov 23, 2016 1:25 pm    Post subject: Reply with quote

Same here. The following command returns nothing:
Code:
find /var/portage/repos/gentoo -name ChangeLog
Back to top
View user's profile Send private message
fedeliallalinea
Moderator
Moderator


Joined: 08 Mar 2003
Posts: 25389
Location: here

PostPosted: Wed Nov 23, 2016 1:40 pm    Post subject: Reply with quote

Point 3 of this announce
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 4628
Location: Illinois, USA

PostPosted: Wed Nov 23, 2016 1:51 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Point 3 of this announce

Should have been a notice in eselect news as well.
Back to top
View user's profile Send private message
fedeliallalinea
Moderator
Moderator


Joined: 08 Mar 2003
Posts: 25389
Location: here

PostPosted: Wed Nov 23, 2016 2:47 pm    Post subject: Reply with quote

Tony0945 wrote:
Should have been a notice in eselect news as well.

It's approved only two weeks ago by Gentoo council. Maybe there will be an announcement.

References:
https://projects.gentoo.org/council/meeting-logs/20161113-summary.txt
https://projects.gentoo.org/council/meeting-logs/20161113.txt
https://bugs.gentoo.org/show_bug.cgi?id=565566
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1611
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Wed Nov 23, 2016 5:28 pm    Post subject: Reply with quote

What is going to be the proper method of reading changelogs while updating a system for the default configuration of using rsync for the portage tree?

I ran into this the other day and any attempts to make the rsync module for the new home of the changelogs work.. doesn't.

packages.gentoo.org rss feed used to have the changes but this went away when the git move first happened. Even if you use git to sync you have to change to each git repo to read the logs.

What is so bad about changelogs?
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
deefster
Tux's lil' helper
Tux's lil' helper


Joined: 19 Apr 2004
Posts: 77

PostPosted: Thu Nov 24, 2016 1:40 pm    Post subject: Reply with quote

I agree, there should be a reasonable replacement. It seems they haven't really officially even announced it, which is more strange given the old method is already gone. In any case, thanks to those who answered my original question, marked thread as solved.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 4628
Location: Illinois, USA

PostPosted: Thu Nov 24, 2016 2:53 pm    Post subject: Reply with quote

I think it's a case of "Why do you care why we made a change? Just do what we say!"
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 9245
Location: beyond the rim

PostPosted: Thu Nov 24, 2016 3:17 pm    Post subject: Reply with quote

firephoto wrote:
What is so bad about changelogs?


Presumably they need substancial amounts of disk space and bandwidth, aren't necessary for the repository to function, aren't all that useful to begin with and are pretty much ignored by the majority of users anyway. But just guessing here.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1611
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Thu Nov 24, 2016 3:57 pm    Post subject: Reply with quote

Genone wrote:
firephoto wrote:
What is so bad about changelogs?


Presumably they need substancial amounts of disk space and bandwidth, aren't necessary for the repository to function, aren't all that useful to begin with and are pretty much ignored by the majority of users anyway. But just guessing here.


I understand the size issue, but it seems pretty simple to just have a file in the tree that represents the last change and that it gets updated with every change. It could also be incorporated into the ebuilds themselves, similar to the DESCRIPTION in that it's for info and doesn't have any impact on installing.

I've put some thought into this the last few days, and it is what it is, but the breaking of the existing system before any working replacement or notice that it will never work again doesn't seem very useful. Always being on unstable here I'm used to things not working smoothly but this goes all the way to stable and every install and the rsync server for changelogs just seems like a place for the historical storage of the changelogs rather than anything related to using them when things are updated on a system since they don't work with portage at the moment.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 9245
Location: beyond the rim

PostPosted: Fri Nov 25, 2016 9:41 am    Post subject: Reply with quote

I agree that it appears to be rushed quite a bit and not coordinated very well. I just remembered that we discussed removing Changelogs many years ago for the listed reasons, particulary lack of use as in most cases you had to check VCS history or upstream changelog anyway to figure out the actually relevant changes. Now that git is firmly in place I guess someone decided it's finally time to pursue this.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1611
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Fri Nov 25, 2016 9:06 pm    Post subject: Reply with quote

Genone wrote:
I agree that it appears to be rushed quite a bit and not coordinated very well. I just remembered that we discussed removing Changelogs many years ago for the listed reasons, particulary lack of use as in most cases you had to check VCS history or upstream changelog anyway to figure out the actually relevant changes. Now that git is firmly in place I guess someone decided it's finally time to pursue this.


Well my latest issue is that even with the tree set to fetch from git, there's nothing for git log to show except the last commit. I thought maybe it was just because of an initial sync with git, or maybe using gentoo-mirror with metadata but gentoo without metadat is the same, but I just checked some other overlay git repos and they have commit logs going back for some time.

It looks like this is related to 'git clone --depth 1'.

So, "sync-depth = 1000" in repos.conf/gentoo.conf and off we go. Seems to work.

The size difference from '--depth 1' to '--depth 1000' is less than 14 MiB.
Code:

>>> Syncing repository 'gentoo' into '/usr/portage'...
/usr/bin/git fetch origin --depth 1000
remote: Counting objects: 42314, done.
remote: Compressing objects: 100% (24846/24846), done.
remote: Total 42314 (delta 28303), reused 26913 (delta 16937), pack-reused 0
Receiving objects: 100% (42314/42314), 13.81 MiB | 220.00 KiB/s, done.
Resolving deltas: 100% (28303/28303), completed with 9677 local objects.
From https://github.com/gentoo-mirror/gentoo
   896dac5f8..4bea66c85  stable     -> origin/stable
=== Sync completed for gentoo


Depth 1000 seems to track QA checks (grep'd 1000 of those entries) on the gentoo-mirror/gentoo plus older commits of GLSA and news items so there's actually a lot more than 1000 commits shown but it gets you about 2 weeks of commits. On gentoo/gentoo git you get about a month history with no GLSA or news commits. I was aiming for 2 weeks with '1000' but my method that got me there was just luck.

Hopefully this is helpful to someone, not better than changelogs but not worse considering they had become optional apparently.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
rogerx
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 118

PostPosted: Sat Dec 24, 2016 5:53 am    Post subject: Reply with quote

--- Snip ---
Approximately 2016/Nov/01, a new module will be available:
- rsync.gentoo.org::gentoo-repo-changelog
--- Snip ---

/etc/portage/repos.conf/gentoo.conf
[gentoo-changelogs]
location = /tmp/portage
sync-type = rsync
sync-uri = rsync://rsync.us.gentoo.org/gentoo-repo-changelog
#sync-uri = rsync.gentoo.org::gentoo-repo-changelog

# emaint sync -r gentoo-changelogs

Neither sync-uri's appear to work as of 2016.12.24. Shrugs...

Personally, I think each package should still contain a Changelog per GNU coding standards. People who do not comment their code are usually just lazy, and stripping the Changelog file now leaves most end users stumped when fixing bugs or wondering as to why a "package_name-r4.ebuild" release version was made. Users now have to diff -urN file-1.ebuild file-2.ebuild, and likely most changes do not include any comments alongside more difficult to read sections. (eg. Insert your most favorite non-readable and undocumented sed or regex match here, along with any rarely utilized scripting concoction.) So instead of simply scanning a ChangeLog file for pertinent changes, end users now need to perform several more steps, hindering debugging for most if not everybody now. And as I further think on this, pushing changelogs within a separate tree are just likely going to minimize the importance of changelog documentation internally. ... but maybe I'm wrong and things are now more easier. Have yet to see the rsync gentoo-repo-changelog tree.
_________________
Roger
http://rogerx.freeshell.org/
Back to top
View user's profile Send private message
Cyker
Veteran
Veteran


Joined: 15 Jun 2006
Posts: 1746

PostPosted: Mon Jan 09, 2017 9:27 am    Post subject: Reply with quote

Hi,

Just came from https://forums.gentoo.org/viewtopic-t-1057352.html

Is there any word or update on what's happening with this?

It's making my life that much more difficult trying to resolve problems due to package changes because this is literally the only place any of that sort of thing is documented without having to spend hours trawling through bgo.

What even is the reason for removing them? They contained genuinely useful pieces of information for people like me that have custom setups.

It makes no sense!
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6227
Location: Room 101

PostPosted: Mon Jan 09, 2017 10:15 am    Post subject: Reply with quote

Cyker wrote:
Is there any word or update on what's happening with this?

Cyker ... it looks like the only way of getting changelogs back is by switching to (non-default) git (and in which case you have 'git log').

Cyker wrote:
It's making my life that much more difficult trying to resolve problems due to package changes because this is literally the only place any of that sort of thing is documented without having to spend hours trawling through bgo.

Me too ... I not only used it to see what, but whom, and having to do this via packages.gentoo.org is far too time consuming.

Cyker wrote:
What even is the reason for removing them? They contained genuinely useful pieces of information for people like me that have custom setups. It makes no sense!

The current wisdom is that it takes up needed space ... go figure.

best ... khay
Back to top
View user's profile Send private message
rogerx
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 118

PostPosted: Mon Jan 09, 2017 4:07 pm    Post subject: Reply with quote

mmm... I'm in agreement with the last posts as well.

The only other rational besides taking up space, the Change Log data are now apparently incorporated with each git ebuild commit (with likely even shorter comments), preventing duplicate entries within a Change Log? And inherently having the end user having to sed/awk through the large git log?
_________________
Roger
http://rogerx.freeshell.org/
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6227
Location: Room 101

PostPosted: Mon Jan 09, 2017 5:49 pm    Post subject: Reply with quote

rogerx wrote:
The only other rational besides taking up space, the Change Log data are now apparently incorporated with each git ebuild commit (with likely even shorter comments), preventing duplicate entries within a Change Log? And inherently having the end user having to sed/awk through the large git log?

rogerx ... well, there is/was a tool for parsing changelogs:

equery -NC changes =sys-fs/eudev-3.1.5:
!!! Fatal error: /var/pkg/gentoo/sys-fs/eudev/ChangeLog does not exist or is unreadable
Add '--debug' to global options for traceback

... the recently released "stable" version of which takes no account for the fact that changelog's no longer exist (and so "breaking the user experience"),

qlop -Cl $(equery belongs =equery) | tail -n 1:
Tue Jan  3 10:48:45 2017 >>> app-portage/gentoolkit-0.3.2-r1

As for 'sync-type', I seem to remember a news item (that I can no longer find ... go figure) that stated that rsync was still the default and that "nothing changes". So while developers can unilaterally opt to drop support for changelogs (without consideration for the "user experience", or bringing the "user experience" up-to-speed) we had just better accept that unless you're following developers (so, running ~arch, or migrating to git) then such things can suddenly disappear from your workflow. Add to this the disclaimer that what is being done is "keeping the majority happy" or some such doublespeak, and throw a "your opinions are meaningless ... show us the code" at anyone criticising such changes and you have a fairly good picture of where you, dear user, stand in the scheme of things.

best ... khay
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6921

PostPosted: Wed Jan 11, 2017 10:16 pm    Post subject: Reply with quote

Oddly enough you *do* get the ChangeLog{,-2015} files in webrsync tarballs, but they're out of date which leaves `equery changes` in a worse than useless state - it's actively misleading.
Back to top
View user's profile Send private message
rogerx
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 118

PostPosted: Sun Aug 27, 2017 4:13 pm    Post subject: Reply with quote

Still no change on this, for a method of checking a change log on a specific package ebuild?

I currently have broken package(s) and need to check the ebuild's date of creation/introduction.

The only current method is by using the release date of the source package, but this is extremely inaccurate as an ebuild could have been more recently published, using an older package version.

This is my first step when tracking ebuild related bugs, or monitoring newer published ebuilds. Without being able to check these dates or check the notes possibly related to the bug, I am (as well as many others) are left to resorting to only filing a bug first, with the opened bug likely lacking much more information than in the past.
_________________
Roger
http://rogerx.freeshell.org/
Back to top
View user's profile Send private message
miket
Guru
Guru


Joined: 28 Apr 2007
Posts: 427
Location: Gainesville, FL, USA

PostPosted: Wed Aug 30, 2017 4:25 am    Post subject: Reply with quote

rogerx wrote:
Still no change on this, for a method of checking a change log on a specific package ebuild?

I'll grant that it's more of a pain, but actually their proposal that we look at the Git logs is not half bad.

I thiink that the argument that the changelogs took up a lot of space is out-and-out specious. The changelog files are already rather short, even the "longish" ones. The real reason, I suspect, was that it was double work to edit the changelog and to make the commit message.

Take a look at either packages.gentoo.org or znurt.org. The p.g.o site includes the top 5 commit messages on the page for a package; znurt has a link labelled "changelog" that points to the changelog page for the package on Gentoo's Github tree. Both of these show you the commit date, the committer's name, and commit message. The log pertains to all the ebuilds for a package.

Of note: it is typical when using a version-control system that you commit more than one file at once. It is usually helpful to see all the files commited at one time, not just one file. Pretty much every VCS since CVS shows you all the files made during a commit (yes, I was glad to say good-bye to CVS).

Going deeper: if you're using packages.gentoo.org and want more changelog information, click on the "Git log" link toward the bottom of the page. This brings up a page on gitweb.gentoo.org and shows you the same information as the github.com/gentoo/ pages you get when you go through znurt--except that the formatting of the page is different between github and gitweb. Either way, you're now in Version-Control land. Click on a revision and see a bunch of diffs right there!

So here it is. I wasn't pleased when I saw what happened to the old changelogs, but now I think that what has replaced them is better. I can see dates of commits and see just exactly what changed.

Here's a way that the new method is an improvement on the old way. If you want to know when a particular line in an ebuild was changed, you can ask to see the "git blame" output. This is easy to get on github.com; I still haven't seen a good way to get that on gitweb.gentoo.org.

All in all, after finding these things, I haven't missed the changelogs. If I would start cloning the whole repository I might be able to get more information, but thus far using the online repository browsers has been working out well for me.

Edit to add:

rogerx wrote:
I currently have broken package(s) and need to check the ebuild's date of creation/introduction.


So here's a way to find not just the creation time, but all the modifications. Say you're following the kde-plasma/powerdevil-5.10.4 ebuild that's been causing me problems. Go to https://github.com/gentoo/gentoo/ and click on "kde-plasma" and then "powerdevil". Now you see a listing of the files you would expect to see in /usr/portage/kde-plasma/powerdevil/. Click on the ebuild of interest. This shows the current contents of the file. Click on the History button and see the revisions to the file. The dates are all right there in one place--no having to grep through the changelog file like you had to do before.
Back to top
View user's profile Send private message
rogerx
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 118

PostPosted: Thu Aug 31, 2017 2:42 am    Post subject: Reply with quote

Thanks you.

Just what I needed to know.
_________________
Roger
http://rogerx.freeshell.org/
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 18820

PostPosted: Thu Sep 21, 2017 2:57 pm    Post subject: Reply with quote

*sigh*

So is there no way to read the changes from the command line?
_________________
Magna Carta (1215) | Spectral evidence no longer permissible (c. 1792) | Cancel culture, deplatforming (c. 2016)
Back to top
View user's profile Send private message
ct85711
Veteran
Veteran


Joined: 27 Sep 2005
Posts: 1791

PostPosted: Thu Sep 21, 2017 3:25 pm    Post subject: Reply with quote

I don't think there is a way if you are using rsync to sync the tree, if you use git to sync the tree; you should be able to use the git log command from the portage tree (recommend using -p 5 to limit to the last 5 messages, otherwise prints all). My default, git log command, lists the commit messages in reverse chronological order.
https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History

Update: I was slightly wrong on the -p 2 portion. The -p shows the file changes along with the commit message. To just limit the number of messages, you only need to use -5 (where 5 is the number of messages).


Last edited by ct85711 on Thu Sep 21, 2017 6:01 pm; edited 1 time in total
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 18820

PostPosted: Thu Sep 21, 2017 4:10 pm    Post subject: Reply with quote

Thanks.

I wonder how many non-programming users know or care to learn git.
_________________
Magna Carta (1215) | Spectral evidence no longer permissible (c. 1792) | Cancel culture, deplatforming (c. 2016)
Back to top
View user's profile Send private message
ct85711
Veteran
Veteran


Joined: 27 Sep 2005
Posts: 1791

PostPosted: Thu Sep 21, 2017 5:59 pm    Post subject: Reply with quote

Alas the most we can do is work with the tools we have, or get someone to make a new tool for them to use.

I was going to mention that someone could possibly make a small hook in the postsync to generate a log file, but it seems git has no way of pulling the log from a remote tree without downloading the repository first. Everything I was seeing on a quick search says the same thing you can only use git log on your copy only (hence you have to fetch from remote first) or use the git website to view the logs.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum