Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#18279 - pacman -Scc --noconfirm

Attached to Project: Pacman
Opened by Dimitrios Apostolou (jimis) - Wednesday, 10 February 2010, 20:51 GMT
Last edited by Dan McGee (toofishes) - Friday, 02 September 2011, 15:05 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Pacman -Scc --noconfirm doesn't clean the cache because the first question default answer is N. Is this in purpose, or is it a bug?

My workaround is to do:
echo -e 'y\ny' | /usr/bin/pacman -Scc
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 02 September 2011, 15:05 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 10 February 2010, 20:58 GMT
  • Field changed: Attached to Project (Arch Linux → Pacman)
--noconfirm do not ask for any confirmation

In other words, put a default in all questions.
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 10 February 2010, 21:02 GMT
you can use "yes" command for that purpose (instead of echo...)
Comment by Dimitrios Apostolou (jimis) - Wednesday, 10 February 2010, 21:06 GMT
So it is normal for this command not to actually perform anything? It's just a dead combination of options...
Comment by Nagy Gabor (combo) - Thursday, 11 February 2010, 19:45 GMT
In general, pacman defaults to the safest answer. But I am with jimis here: User (script) should know what -Scc and means (moreover, he is asked), and I don't think that it is a more dangerous operation than -Rc (where the default is Y).

Btw, there is a hidden and undocumented --ask switch to answer these questions, but it is for internal usage only (the syntax is complicated, it requires a bitvector etc.)
Comment by Xavier (shining) - Friday, 12 February 2010, 01:24 GMT
I am not sure what we could do differently.
But people should not use pacman -Scc anyway...
And there is already plenty of options :
1) use echo y or yes
2) rm /var/cache/pacman/pkg/*
...
Comment by Nagy Gabor (combo) - Friday, 12 February 2010, 02:30 GMT
Well, I wanted to say that in my opinion the Y default answer would be more coherent here (see also -Sc). But changing the default answer is maybe worse than changing nothing.
Comment by Xavier (shining) - Friday, 12 February 2010, 10:58 GMT
The idea is that -Scc is more destructive than -Sc , and is not advised.
It's recommended to keep installed packages for two main reasons :
1) reinstall (because its broken, or files were lost, or need to change install reason)
2) downgrade after an upgrade
Comment by Nagy Gabor (combo) - Friday, 12 February 2010, 12:55 GMT
Well, I use -Scc when I need more free disk space. ;-)

I don't think that someone uses -Scc "accidentally". If someone does, we ask a "Do you want to ... ALL ...?" question.

But OK, this is a minor issue(?), I am fine with "won't implement", too.
Comment by Dimitrios Apostolou (jimis) - Thursday, 18 February 2010, 20:28 GMT
Now I understand why most programs prefer having a --yes flag rather than a --no-confirm. It's clear to the user that the outcome won't depend on the default answer.
Comment by Thomas Dziedzic (tomd123) - Saturday, 03 July 2010, 23:39 GMT
status?

yes | pacman -Scc works as well as any of the other previously mentioned methods
Comment by Karol Błażewicz (karol) - Tuesday, 30 August 2011, 22:13 GMT
Status?

Loading...