You are not logged in.
Since the Pacman 3.3.0 upgrade every time I try to run a command using yaourt I see this integrity check message at the end of the output.
yaourt -Syu
Synchronizing package databases...
testing is up to date
core is up to date
extra is up to date
community is up to date
Checking the integrity of the local database in /var/lib/pacman/
However I don't see it when using pacman
pacman -Syu
:: Synchronizing package databases...
testing is up to date
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
local database is up to date
Any ideas?
Last edited by flowheat (2009-08-06 00:06:25)
Offline
That is because yaourt issues a call to testdb to validate the local database integrity. I don't know any way of silencing the output of testdb, but you could patch yaourt to not run this step...
--- yaourt.orig 2009-08-05 19:10:17.969351775 -0400
+++ yaourt 2009-08-05 19:10:35.892722153 -0400
@@ -674,7 +674,7 @@
fi
# testdb
- testdb
+ # testdb
# save original of backup files (pacnew/pacsave)
if [ "$MAJOR" != "remove" ] && [ $AUTOSAVEBACKUPFILE -eq 1 ] && ! diff "$INSTALLED_BEFORE.full" "$INSTALLED_AFTER.full" > /dev/null; then
Offline
That did the trick, but shouldn't I have been seeing that msg before the pacman 3.3.0 update?
Offline
Offline
> pacman -Qo $(which testdb)
/usr/bin/testdb is owned by pacman 3.3.0-2
Looks more than co-incidental to me...
Offline
> pacman -Qo $(which testdb) /usr/bin/testdb is owned by pacman 3.3.0-2
Looks more than co-incidental to me...
Like I said... I didn't look into it. However, Allan (as usual) is right. Looks like yaourt was updated to impliment a new feature in pacman.
Offline
Nah, my point was that testdb is part of pacman which was just updated. I guess this update made testdb more verbose (in fact, I am fairly sure it did...)
Offline
All makes sense now. Thanks for the help as always.
Offline
That is because yaourt issues a call to testdb to validate the local database integrity. I don't know any way of silencing the output of testdb, but you could patch yaourt to not run this step...
--- yaourt.orig 2009-08-05 19:10:17.969351775 -0400 +++ yaourt 2009-08-05 19:10:35.892722153 -0400 @@ -674,7 +674,7 @@ fi # testdb - testdb + # testdb # save original of backup files (pacnew/pacsave) if [ "$MAJOR" != "remove" ] && [ $AUTOSAVEBACKUPFILE -eq 1 ] && ! diff "$INSTALLED_BEFORE.full" "$INSTALLED_AFTER.full" > /dev/null; then
Can you please explane step by step how to use this patch? Thanks
I do not speak English, but I understand...
Offline
1.) cd /usr/bin
2.) sudo nano yaourt
3.) Locate "testdb" line and make it "#testdb"
Offline
Me thinks the testing is done for a reason? I don't find the message very clutter-y anyway, and I think I'd want to know if/when there's a problem with my pacman db.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
well the yaourt maintainers should have had this fixed before pacman was moved to extra, but they didnt so there came a bug, you report it , they fix it ?? Profit.
Offline
1.) cd /usr/bin
2.) sudo nano yaourt
3.) Locate "testdb" line and make it "#testdb"
Thanks!
I do not speak English, but I understand...
Offline
well there is no clean way to filter this message and still let the errors show up.
just "testdb | grep -v Checking" which is rather ugly
so I am fine with removing this not so useful message from testdb
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
well there is no clean way to filter this message and still let the errors show up.
Maybe
testdb 1> /dev/null
?
Last edited by helios91 (2009-08-07 14:49:56)
Offline
shining wrote:well there is no clean way to filter this message and still let the errors show up.
Maybe
testdb 1> /dev/null
?
testdb > /dev/null would remove all the results, because they are not displayed on stderr. so it would make running testdb useless
unless you also check for the return value and display a warning if non 0
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Fixed in yaourt-git ;-)
Offline
Fixed in yaourt-git ;-)
just to inform you that testdb 3.3.1 will be more quiet, like before :
http://projects.archlinux.org/?p=pacman … d7e32a3f24
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline