Package update comments.

Weeks · 2007-05-14 19:52:39

I'm always happy to know I'm fully up-to-date when I run pacman -Syu, but I'd often like to know what's changed. For instance, just now I updated to the latest versions of pidgin and pacman and I wanted to know what had changed. So I went to the CVS page for pacman and, to be frank, I'm none the wiser.

The pidgin update may be a bad example, because it did tell me the 'bonjour' plugin had been included. But that kind of information rarely appears. Has anyone got any ideas that would help integrate this kind of information when new features and major changes happen?

Ramses de Norre · 2007-05-14 20:23:55

I'd also like to have easy access to changelogs for updated packages, I haven't found them yet...

phrakture · 2007-05-14 20:31:01

Ok two things here:
a) If pidgin is updated, you'll find the full changelog at the pidgin site. You can't really expect us to maintain dual changelogs for code that's not ours, can you?
b) pacman 3 has changelog support - we just need to wait a bit to get everything on to pacman 3 before we can begin using full pacman 3 packages.

Weeks · 2007-05-15 11:31:08

'A' is a fair point in retrospect. So is pacman's changelog support just for pacman, or for all applications?

xerverius · 2007-05-15 11:43:34

Maybe more logs like: "Pidgin is updated to 2.0.1", "Fixed FS bug #0000 in the init scripts" and "Update to latest alsa and fixed e1000 module", something like that. More 1 liners that give a description why the package is updated.

attila · 2007-05-15 12:00:57

b) pacman 3 has changelog support - we just need to wait a bit to get everything on to pacman 3 before we can begin using full pacman 3 packages.

Nice to know but how can i use it to integrate a changelog in my own local packages?

phrakture · 2007-05-15 15:13:34

attila wrote:

b) pacman 3 has changelog support - we just need to wait a bit to get everything on to pacman 3 before we can begin using full pacman 3 packages.
Nice to know but how can i use it to integrate a changelog in my own local packages?

pacman will detect a "ChangeLog" file next to the PKGBUILD, and stick it into the package when building.

attila · 2007-05-15 17:47:46

pacman will detect a "ChangeLog" file next to the PKGBUILD, and stick it into the package when building.

Nice feature. Thanks for the information.

attila · 2007-05-15 18:46:57

Sorry, i wrote too early all is good. I have problems to see the changelog from an own package.
I use an exact copy of the PKBUILD for kplayer from community and run "makepkg -c". The last lines of makepkg looks good.

...
==> Copying package changelog
==> Compressing package...
==> Cleaning up...
==> Finished making: kplayer

But it don' get found if i use "pacman -Qc kplayer " or "pacman --changelog kplayer" because i even get a "Fehler: Kein Änderungsprotokoll für 'kplayer' verfügbar" which is the german version for "no changelog". Could it be that the ChangeLog files has to have a specific look as used at example for rpm packages? Here is the content of my ChangeLog:

0.6.2-1 13.05.2007
- User manual updated with all the new 0.6 features 
- Improvements in multimedia library and playlists 
- Many bug fixes and other improvements 
- Updated translations

attila · 2007-05-15 21:21:00

Okay, i promise this is the last time that i comment myself.-)

"pacman -Qc" works but only as root. Strange because at example "pacman -Qi" works as normal user ... ah, i see it why: the changelog file in /var/lib/pacman/local is owned by root:root and the permissions be "-rw-r-----".

Is this a bug so i should write a report or is the error that i made the package with my user account which have umask 007? A "find /var/lib/pacman/local -type f -perm 640" shows me that the *.install files from my own packages has the same file permissions.

phrakture · 2007-05-16 05:39:05

attila wrote:

Okay, i promise this is the last time that i comment myself.-)
"pacman -Qc" works but only as root. Strange because at example "pacman -Qi" works as normal user ... ah, i see it why: the changelog file in /var/lib/pacman/local is owned by root:root and the permissions be "-rw-r-----".
Is this a bug so i should write a report or is the error that i made the package with my user account which have umask 007? A "find /var/lib/pacman/local -type f -perm 640" shows me that the *.install files from my own packages has the same file permissions.

Oh good catch - I guess we didn't test this one all that much just yet because we can't use changelogs in packages yet

Can you add this to the bug tracker so we can get to it?

attila · 2007-05-17 06:34:56

Can you add this to the bug tracker so we can get to it?

Done. Thanks for your help.

phrakture · 2007-05-17 07:00:56

could you post a link to the bug?

attila · 2007-05-17 07:58:12

could you post a link to the bug?

Sorry, I use the rss feed of it and so forgot it to post here:
http://bugs.archlinux.org/task/7182

Weeks · 2007-05-17 08:38:49

attila wrote:

pacman will detect a "ChangeLog" file next to the PKGBUILD, and stick it into the package when building.
Nice feature. Thanks for the information.

ditto.

Arch Linux

#1 2007-05-14 19:52:39

Package update comments.

#2 2007-05-14 20:23:55

Re: Package update comments.

#3 2007-05-14 20:31:01

Re: Package update comments.

#4 2007-05-15 11:31:08

Re: Package update comments.

#5 2007-05-15 11:43:34

Re: Package update comments.

#6 2007-05-15 12:00:57

Re: Package update comments.

#7 2007-05-15 15:13:34

Re: Package update comments.

#8 2007-05-15 17:47:46

Re: Package update comments.

#9 2007-05-15 18:46:57

Re: Package update comments.

#10 2007-05-15 21:21:00

Re: Package update comments.

#11 2007-05-16 05:39:05

Re: Package update comments.

#12 2007-05-17 06:34:56

Re: Package update comments.

#13 2007-05-17 07:00:56

Re: Package update comments.

#14 2007-05-17 07:58:12

Re: Package update comments.

#15 2007-05-17 08:38:49

Re: Package update comments.

Board footer