Does anybody else have the situation where AUR packages seem to take eons?
Were normal (non-AUR) updates fast?
At that point it isn’t downloading from the AUR. It is downloading from whereever the package source is hosting. Potentially from brother in this case. You can take a look at the PKGBUILD and look at the SOURCE= line to see where it is coming from.
2 Likes
Yes
Eventually finished…
Dload Upload Total Spent Left Speed
0 3493 0 0 0 0 0 0 --:--:-- 0:15:01 --:--:-- 0
curl: (22) The requested URL returned error: 504
Warning: Problem : HTTP error. Will retry in 3 seconds. 3 retries left.
100 37664 100 37664 0 0 47775 0 --:--:-- --:--:-- --:--:-- 47736
-> Downloading dcp1610wcupswrapper-3.0.1-1.i386.rpm...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 3517 0 0 0 0 0 0 --:--:-- 0:15:00 --:--:-- 0
curl: (22) The requested URL returned error: 504
Warning: Problem : HTTP error. Will retry in 3 seconds. 3 retries left.
100 19008 100 19008 0 0 23665 0 --:--:-- --:--:-- --:--:-- 23641
==> Validating source files with md5sums...
dcp1610wlpr-3.0.1-1.i386.rpm ... Passed
dcp1610wcupswrapper-3.0.1-1.i386.rpm ... Passed
==> Making package: brother-dcp1610w 3.0.1-1 (Thu 30 Jun 2022 10:30:42)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found dcp1610wlpr-3.0.1-1.i386.rpm
-> Found dcp1610wcupswrapper-3.0.1-1.i386.rpm
==> Validating source files with md5sums...
dcp1610wlpr-3.0.1-1.i386.rpm ... Passed
dcp1610wcupswrapper-3.0.1-1.i386.rpm ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting dcp1610wlpr-3.0.1-1.i386.rpm with bsdtar
-> Extracting dcp1610wcupswrapper-3.0.1-1.i386.rpm with bsdtar
==> Sources are ready.
==> Making package: brother-dcp1610w 3.0.1-1 (Thu 30 Jun 2022 10:30:44)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "brother-dcp1610w"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: brother-dcp1610w 3.0.1-1 (Thu 30 Jun 2022 10:30:45)
==> Cleaning up...
loading packages...
resolving dependencies...
looking for conflicting packages...
Package (1) New Version Net Change
brother-dcp1610w 3.0.1-1 0.11 MiB
Total Installed Size: 0.11 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [--------------------------------------] 100%
(1/1) checking package integrity [--------------------------------------] 100%
(1/1) loading package files [--------------------------------------] 100%
(1/1) checking for file conflicts [--------------------------------------] 100%
:: Processing package changes...
(1/1) installing brother-dcp1610w [--------------------------------------] 100%
Optional dependencies for brother-dcp1610w
brscan4: scanner support
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
I had the problem once, solved it by aborting the installation (ctrl+c) and restarting my system. after that everything worked normally.
1 Like
please format your output as code by highlighting the entire output and then pressing the code button(</>). it is then easier to read.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.