You are not logged in.
Currently my process is to make a one-line list of all packages to be upgraded, then give them to a bash script (named ogle) that's just:
pacman -Si $1
paclog -l 5 $1
pactree -r $1Then with a .bash_profile alias I have "ogle {huge list of packages} > og.txt ; vim og.txt", which helps me get an idea/reminder of what a package is and why it might need upgrading, and then I can simply recall the command and delete the first package on the list to move onto the next.
Except of course for those times where the 5 last commits aren't enough (needing a better guess for the right number), or when paclog can find no commit messages (requiring hunting down the right part of the right site to find the commit log), or when the dependency tree is changing for the update (not something I've solved, since pactree -sr can't filter further, but I'm just using it to understand what a package is for, so it's ok).
So, with effort, this process works, but it is a lot slower than it needs to be, and I would like to get it the level of efficiency such that I no longer dread updating.
Would any of you be willing to detail your own methods for reviewing packages and deciding which ones to hold back?
(The end goal of course being to prevent all unwanted changes and spot all potential conflicts before anything gets broken, since fixing even a few broken things still takes a lot longer than the five hours it takes to review.)
(P.S. I also have an idea about collecting pertinent bug reports based on installed packages, which seems like a more reliable way of avoiding disasters, but I have no idea how to implement it, since bug reports are so scattered and have so many kinds.)
Offline
I just -Syu without reviewing anything, in the 5+ years I've been using Arch I can only remember 2 breakages, and each only took minutes to fix.
You're wasting far more time reviewing than it would take to fix any issues that arise.
Offline
then I can simply recall the command and delete the first package on the list to move onto the next
So you feed it a big list every time, but it only uses the first one? Just use a for loop and call it once:
for pkg in $@; do
pacman -Si $pkg >| /tmp/whatever.txt
paclog -l 5 $pkg >> /tmp/whatever.txt
pactree -r $pkg >> /tmp/whatver.txt
vim /tmp/whatever.txt
doneNote, I've not used paclog before, but if that's the tool from pacutils, those flags don't seem to be valid.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Online
Thank you, Trilby; I suspect I had known all the building blocks for that script, but did not realize I could put them together. (It is slow, but only because paclog is slow [which is because the sources are slow, I think].)
Note, I've not used paclog before, but if that's the tool from pacutils, those flags don't seem to be valid.
I was going to post the AUR link, but apparently my version is out of date; the redirection says this is the current form I need to update to. (I will check out this pacutils version.)
I just -Syu without reviewing anything, in the 5+ years I've been using Arch I can only remember 2 breakages, and each only took minutes to fix.
Might be luck, might be standardization; I tend to customize until I get the behavior/security I want, but I'm rarely sure whether a problem is from something I've changed or whether it's from obscure conflicts/bugs (or whether it's intended behavior I don't agree with, but that's rarer).
Last edited by Torignit (2017-04-29 12:51:17)
Offline
My strategy is to update often (once a day is absolute minimum for me, 3 or 4 times on 1 day is not unusual[1] ).
That allows me to notice fast if something broke/changed and makes troubleshooting much easier.
[1] one of the unofficial repos i use has new packages every 6 hours
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
My strategy is to update often (once a day is absolute minimum for me, 3 or 4 times on 1 day is not unusual
This. Dealing with smaller increments of change means less to debug in the unlikely event of an issue.
Not a Pacman Issue, moving to NC...
Offline
Not sure if that's what you're after, but the script traverses all available updates and allows you to inspect the package or (attempt to) delete it.
You may trail it with "sudo pacman -Su"
#!/bin/bash
while read -u 7 LINE; do
echo $LINE
while true; do
read -p " [U]pdate, [i]nspect or [d]elete: " -N1 ACT
echo -e '\r'
case "$ACT" in
i|I)
pacman -Qi ${LINE%% *} | less
tput cuu1; tput el
;;
d|D)
sudo pacman -Rs ${LINE%% *}
break
;;
*)
break
;;
esac
done
done 7< <(checkupdates)Offline