Feature request: current and updated versions in pacman -Su

DavidSouther · 2010-11-17 02:20:09

I think it'd be really nice to have an option to display both the current installed and new upgraded version of packages when running pacman -Su

I often find myself wondering "how different" are the changes- is it a rev release? A major version upgrade? I don't really want to do that with 50 packages every week, but if it were easy I'd like to know that.

Instead of:

Targets (50): alsa-utils-1.0.23-3 tzdata-2010o-1 glibc-2.12.1-4 coreutils-8.7-1 db-5.1.19-3 heimdal-1.3.3-3 libcups-1.4.5-1 cups-1.4.5-1 glib2-2.26.1-1
dbus-glib-0.92-1 gdk-pixbuf2-2.22.1-1 python2-bonobo-2.28.1-5 python2-gconf-2.28.1-5 python2-libgnome-2.28.1-5 python2-gnomecanvas-2.28.1-5
python2-gnomevfs-2.28.1-5 gnome-python-2.28.1-5 gvfs-1.6.6-1 inputproto-2.0.1-1 libgnome-data-2.32.0-3 libgnome-2.32.0-3
nvidia-utils-260.19.21-1 libva-1.0.6-1 libxi-1.4.0-1 man-pages-3.31-1 mercurial-1.7.1-1 nvidia-260.19.21-1 orc-0.4.11-1 perl-xml-parser-2.40-1
qt-4.7.1-1 smbclient-3.5.6-1 samba-3.5.6-1 tar-1.25-1 texlive-bin-2010.1-5 texlive-core-2010.20288-1 transmission-cli-2.12-1
transmission-gtk-2.12-1 upower-0.9.7-1 usbmuxd-1.0.6-1 xorg-xgamma-1.0.4-1 xorg-xinput-1.5.3-1 xorg-xkill-1.0.3-1 xorg-xrandr-1.3.4-1
xorg-xrdb-1.0.7-1 xorg-xrefresh-1.0.4-1 xorg-xset-1.2.1-1 xorg-xsetroot-1.1.0-1 xorg-xwd-1.0.4-1 xorg-xwud-1.0.3-1 xproto-7.0.19-1

Do:

Targets (50):
alsa-utils-1.0.23-2 to alsa-utils-1.0.23-3
tzdata-2010o to tzdata-2010o-1
glibc-2.12.1-3 to glibc-2.12.1-4

and so forth.

falconindy · 2010-11-17 02:38:26

You can abstract this information on your own. I've got an alias you mind find useful:

alias pqu='paste -d "" <(printf "%-20.20s %12s => \n" $(pacman -Qu)) <(pacman --config <(grep -v "^Ignore" /etc/pacman.conf) -Sdp --print-format "%v" $(pacman -Qqu))'

Allan · 2010-11-17 02:46:07

There is a bug tracker where requests like this should be made. Otherwise the people who matter will likely never see the bug. But I believe this one is already there...

kazuo · 2010-11-17 03:12:34

Uhh, but this is not already clearly? I follow this:

if (rev > 1):
    revision bump
else if (rev == 1):
    version bump

for example "foo 1.2.33-4" means that the previous version is "foo 1.2.33-3". and "bar 4.3-1" meant that the previous version is "bar 4.2-n"

This only break when a 4.3-1 is quickly followed by a 4.3-2, but the solutions is clearly, update more frequently than the devs solve a break in rev 1 =].

This too don't work when 4.2-n is followed by a 4.4-1, but if this is so probably the 4.3 can be ignored.

Updating more frequently than a week make all this works, as you get all the version and revisions (including the bogus ones).

When I update I always scan for -1, so I know that a version update happened. Of course I read the mailing list too.

Last edited by kazuo (2010-11-17 03:17:24)

theapodan · 2010-11-17 03:17:37

I notice it's your first post. Welcome.

Yaourt, and possibly other libalpm & pacman wrappers, have this functionality. Some people prefer to stick with pacman though, which is not an unreasonable course of action.

karol · 2010-11-17 03:58:24

https://bbs.archlinux.org/viewtopic.php?id=103714
It's basically what falconindy suggested.

Last edited by karol (2010-11-17 03:59:10)

Arch Linux

#1 2010-11-17 02:20:09

Feature request: current and updated versions in pacman -Su

#2 2010-11-17 02:38:26

Re: Feature request: current and updated versions in pacman -Su

#3 2010-11-17 02:46:07

Re: Feature request: current and updated versions in pacman -Su

#4 2010-11-17 03:12:34

Re: Feature request: current and updated versions in pacman -Su

#5 2010-11-17 03:17:37

Re: Feature request: current and updated versions in pacman -Su

#6 2010-11-17 03:58:24

Re: Feature request: current and updated versions in pacman -Su

Board footer