You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2012-02-10 09:03:21
- FernandoBasso
- Member
- From: Brazil
- Registered: 2010-10-27
- Posts: 90
- Website
How to know why package was update?
How to know why a package was upgraded? for example,
pacman.log:
[2012-02-10 06:38] upgraded lynx (2.8.7-4 -> 2.8.7-5)
[2012-02-10 06:37] upgraded gvim (7.3.401-1 -> 7.3.434-1)The package 'gvim' was probably upgraded to provide more patches, but
what was the problem with 'lynx', since only the the pkgrel changed from -4 to -5,
Is it possible to discover the reason why a package was upgraded in cases like that?
There is a difference between knowing the path and walking the path.
Offline
#2 2012-02-10 09:11:57
- hadrons123
- Member
- From: chennai
- Registered: 2011-10-07
- Posts: 1,249
Re: How to know why package was update?
well, you could see the upstream's site for that info.
I don't think its the job of pacman to provide you those details if that's what you are asking for.
LENOVO Y 580 IVYBRIDGE 660M NVIDIA
Unix is user-friendly. It just isn't promiscuous about which users it's friendly with. - Steven King
Offline
#3 2012-02-10 09:32:43
- Runiq
- Member
- From: Germany
- Registered: 2008-10-29
- Posts: 1,053
Re: How to know why package was update?
`man pacman` tells you that pacman has a --changelog option; alas, it's rarely used.
As a rule of thumb, the pkgrel changes whenever there's an issue to correct that has not been introduced upstream. You'd have to ask the maintainer of the specific package why they had to update it, though. I'd recommend subscribing to the arch-commits mailing list instead.
As for pkgver, that obviously only changes when upstream releases a new stable version.
Last edited by Runiq (2012-02-10 09:40:18)
Offline
#4 2012-02-10 09:32:52
- FernandoBasso
- Member
- From: Brazil
- Registered: 2010-10-27
- Posts: 90
- Website
Re: How to know why package was update?
well, you could see the upstream's site for that info.
I don't think its the job of pacman to provide you those details if that's what you are asking for.
I'm not talking about upstream, I'm talking about pgkrel - that is related only to arch linux.
There is a difference between knowing the path and walking the path.
Offline
#5 2012-02-10 09:35:02
- Awebb
- Member
- Registered: 2010-05-06
- Posts: 6,311
Re: How to know why package was update?
The pkgrel has nothing to do with upstream changes, hadrons123.
Klick on Packages in the navigation bar on top of this page, search for lynx and click on View Changes (under Package Actions).
Offline
#6 2012-02-10 09:43:31
- Runiq
- Member
- From: Germany
- Registered: 2008-10-29
- Posts: 1,053
Re: How to know why package was update?
Klick on Packages in the navigation bar on top of this page, search for lynx and click on View Changes (under Package Actions).
Ooh, nice. That's useful. Thanks for the info!
Offline
#7 2012-02-10 10:00:18
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,405
- Website
Re: How to know why package was update?
Offline
#8 2012-02-10 18:29:50
- FernandoBasso
- Member
- From: Brazil
- Registered: 2010-10-27
- Posts: 90
- Website
Re: How to know why package was update?
"View Changes" in archlinux.org/packages/ is fine; pkgcl is more practical.
Packagers should really provide a changelog, since it is supported by pacman by default.
There is a difference between knowing the path and walking the path.
Offline
#9 2012-02-10 18:44:26
- fsckd
- Forum Fellow
- Registered: 2009-06-15
- Posts: 4,173
Re: How to know why package was update?
I was going to suggest commit messages and then I saw Allan's link to pkgcl thread. So happy.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Pages: 1