You are not logged in.

#1 2008-12-31 02:49:47

silvernode
Member
From: Chicago
Registered: 2008-08-29
Posts: 45

Problem upgrading smbclient

Appently my friend does not have this problem with smbclient but when I perform a full upgrade I get this.



:: Retrieving packages from core...
 zlib-1.2.3.3-3-i686      111.0K   94.2K/s 00:00:01 [#####################] 100%
:: Retrieving packages from extra...
 sqlite3-3.6.7-2-i686     391.3K   56.6K/s 00:00:07 [#####################] 100%
 hwd-5.4.2-1-i686          17.8K   38.2K/s 00:00:00 [#####################] 100%
 imagemagick-6.4.8.2...     2.1M   49.8K/s 00:00:43 [#####################] 100%
 liferea-1.4.23-1-i686    988.3K   50.8K/s 00:00:19 [#####################] 100%
 smbclient-3.2.6-2-i686    13.1M   49.0K/s 00:04:34 [#####################] 100%
checking package integrity...
:: File smbclient-3.2.6-2-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package)
smbclient-3.2.6-2-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded.

I think I can fix this myself but I thought I would post it incase it's an AUR issue. Although like I said, my friend does not have this problem.

I am using the first repository available to select when installing Arch linux.

Last edited by silvernode (2008-12-31 03:06:32)

Offline

#2 2008-12-31 02:52:06

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,404
Website

Re: Problem upgrading smbclient

silvernode wrote:
:: File smbclient-3.2.6-2-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] n

You really want to say "Y" there.  If it downloads corrupt again, file a bug report with the mirror you are using.

Offline

#3 2009-01-14 17:22:09

silvernode
Member
From: Chicago
Registered: 2008-08-29
Posts: 45

Re: Problem upgrading smbclient

I got this last month and was able to fix it by advice from a friend. I don't remember what it was since it was months ago. I just installed arch again after reformatting and yet I get this same error even using a different mirror. This is strange and I can't pinpoint what the issue is. All mirrors couldn't possibly all have corrupted files could they? Well not much on the forums about this so I suppose gnome will have to wait :-(

Offline

Board footer

Powered by FluxBB