pkgd: a daemon for sharing pkgs over your LAN

Xyne · 2010-01-16 04:26:41

@n17ikh
Reread the text that you quoted. I've already explained why logging doesn't work.

n17ikh · 2010-01-16 06:58:36

Xyne wrote:

@n17ikh
Reread the text that you quoted. I've already explained why logging doesn't work.

So you did. Not having logging implemented certainly might explain why I can't get it to work.

Xyne · 2010-01-16 08:02:31

I actually had implemented the logging code so I'm not sure why it isn't working for others. I've added code to create the path if it doesn't exist but other than that I haven't changed anything.

Post your pkgd.conf and the permissions of the log file if it still doesn't work. Also try running pkgd as a regular user in a terminal and set the log path from the command line just to test it, e.g. "pkgd -l pkgd.log".

n17ikh · 2010-01-20 06:39:07

Xyne wrote:

I actually had implemented the logging code so I'm not sure why it isn't working for others. I've added code to create the path if it doesn't exist but other than that I haven't changed anything.
Post your pkgd.conf and the permissions of the log file if it still doesn't work. Also try running pkgd as a regular user in a terminal and set the log path from the command line just to test it, e.g. "pkgd -l pkgd.log".

My pkgd.conf is the same one I posted earlier in the thread:

peter@Yggdrasil ~ % cat /etc/pkgd.conf
# Comments begin with "#"

# The default cache is /var/cache/pacman/pkg
# If a cache is specified here on on the command line,
# it overrides the default cache. Include the default
# cache if you wish to use multiple caches.
#Cache = /var/cache/pacman/pkg/
#Cache = /some/other/cache

# The interval is the time that pkgd sleeps between
# notifications to the master pkgds.
#Interval = 300

# The path to the log file. The log will only
# be written if a path is specified.
Log = /var/log/pkgd/pkgd.log

# The master pkgd servers, listed on separate lines.
#Master = 192.168.0.1:14687
#Master = 192.168.0.2:14687

# The port for this pkgd to use.
# The default is 14687.
#Port = 14687

# Enabling quiet mode will suppress output.
# This is mostly for running pkgd as a daemon.
#Quiet

As of perl-xyne-arch 1.0.42-1, running pkgd from the rc script with this configuration causes it to not log. Running it from the command line with su pkgd -c "pkgd -l /var/log/pkgd/pkgd.log" causes it to log, and create the path and file with appropriate permissions if they're missing. Running it without -l, with the same command-line options it has in the script (just --quiet) it doesn't log, but strace shows it reading the conf file in, so unless I've mangled the configuration I don't know why it's not logging. I did notice a pkgd.conf.pacnew exists, but I don't see any real differences on comparison.

I did notice that making /var/log/pkgd as root and then failing to give it writable permissions for the pkgd user causes the pkgd -l command above to error out because it can't create or write to the log file. However, running it from the init script, it starts up without complaint - not even trying to write the file, as I saw with strace.

I went back and checked, and it looks like logging broke at the same time on all 3 of my machines running pkgd, where that last big update came down the pipe.

So, in the middle of writing this post, I re-checked some things, and figured out the following:
Turns out, it was the thing I missed in my eyeballing of the new config file - it needs "[options]" at the top now. Everything else is the same. It's logging again now.
However, I did notice that enabling "Quiet" in the config file seems to have no effect - whether it's enabled or not, after starting pkgd with the init script (where --quiet is called anyway!) it prints "logging" to the screen every time something happens with logging enabled.

Xyne · 2010-01-20 08:21:12

@n17ikh
Sorry, I had forgotten to remove the line that was printing out "logging" after I finished debugging the code. It's been removed in perl-xyne-arch 1.0.44.

Funny that I didn't catch the missing [options] tag either.

twa022 · 2010-02-05 06:07:06

My pkgd setup recently stopped working. When pkgs are requested from the master pkgd, it logs:

PkgD now listening on port 44567...
request received from 192.168.1.100: {"operation":"notify_master","port":"44567"}

registered slave 192.168.1.100:44567
request received from 192.168.1.100: GET /xcb-util-0.3.6-1-x86_64.pkg.tar.gz HTTP/1.1
Host: 192.168.1.103:44567
User-Agent: pacman/3.3.3 (Linux x86_64) libalpm/4.0.3
Connection: close

dropped unrecognized request from 192.168.1.100

nothing is logged on the slave pkgd, but pacman on the slave logs

error: failed retrieving file 'openbox-3.4.10-3-x86_64.pkg.tar.gz' from 192.168.1.103 : Success
warning: failed to retrieve some files from extra
error: failed to commit transaction (Success)

This is my pkgd.conf from the master pkgd:

[options]

################################################################################
# Bind PkgD to this address, e.g. "-a 192.168.0.1". Leave it blank to allow
# access to PkgD through all interfaces.

# Address = <address>
################################################################################





################################################################################
# The path to the package cache. Multiple may be specified and they will be
# checked in that order.

CacheDir = /var/cache/pacman/pkg
CacheDir = /share/programs/build-pkg
CacheDir = /share/programs/build-pkg/Mine
CacheDir = /share/programs/build-pkg/Mine/Screenlets
################################################################################





################################################################################
# The PkgD master notification interval (in seconds), i.e. how often PkgD should
# inform master PkgDs that it is available. The default is five minutes (300 s).

Interval = 300
################################################################################





################################################################################
# The PkgD log file.

# Log = /var/log/pkgd.log
################################################################################





################################################################################
# An address and port of a master PkgD. Multiple may be specified.

# Master = <address:port>
################################################################################





################################################################################
# The maximum number of nodes in each query path, e.g. each immediate slave is
# the first node, each slave of a slave is a second node, etc.

MaxDepth = 3
################################################################################





################################################################################
# The port on which to listen, e.g. "-p 44567". The default port is 14687

Port = 44567
################################################################################





################################################################################
# Suppress console output (this has no effect on logging).

# Quiet
################################################################################

Xyne · 2010-02-05 08:07:31

request received from 192.168.1.100: GET /xcb-util-0.3.6-1-x86_64.pkg.tar.gz HTTP/1.1

It seems that you forgot to add "$repo" to the server line in pacman.conf (or the mirrorlist).

It should be

Server = http://<address>:<port>/$repo

The GET request in the line above will then be:

request received from 192.168.1.100: GET /extra/xcb-util-0.3.6-1-x86_64.pkg.tar.gz HTTP/1.1

tjpp · 2010-05-13 16:52:04

I had once pkgdd working nicely. From some time from now that I cannot precisely tell when, the master only provides packages that are stored in its local disk (/var/cache/pacman/pkg) and does not provided packages that are stored in the other machines. How can I fix it ? Is there any debug option that I could use in order to provide additional info ?

Xyne · 2010-05-13 22:13:27

@tjpp
Run pkgd in a terminal on each machine and check if the master pkgd detects the slaves when they start up (it should display a message). After that check the messages when attempting to download a package from a slave via the master and directly (e.g. does the slave even receive a request?). You can use the log option to log the messages but they should be the same as what you see in the terminal.

Possible causes the come to mind:
*) your firewall and|or connection settings have changed
*) you haven't updated pkgd on some systems in a long time and thus have incompatible versions (unlikely though as I updated the internal protocol a while ago)

tjpp · 2010-05-14 18:55:16

@Xyne

thanks for replying. I think I have submit a false positive: pkgd is running but sometimes I update all machines at almost the same time. In previous versions I could change the time pkgd slaves send informations to the server. It seems to be hardcoded in new versions and there is no enough time for propagating the new package information to the server. That is why local packages are always sent.

best regards

Xyne · 2010-05-14 20:43:20

You can control how often the slaves notify the master with the "interval" option but that should have no effect on the availability of packages once the master has registered the slave. The notification interval just ensures that the master will re-register the slaves if it is restarted.

What's probably happening is that the packages have not finished downloading when you send the requests so they appear to be unavailable. Try updating one system at a time and it should work. You just need to wait for the packages to finish downloading before you start the next upgrade.

tjpp · 2010-06-23 17:07:00

it is me, again!

After upgrading pacman to 3.4, if I include the pkgd Server line in mirrorlist, pacman does not find it and any other server (no address record). If I remove :14687, it does not find the pkgd server but at least search for others.

Thanks in advance

:wq

Last edited by tjpp (2010-06-23 17:12:05)

Xyne · 2010-06-24 01:17:54

@tjpp
That's actually 2 separate issues.

The first is that Pacman now sends a HEAD request before a GET request. PkgD only implements a limited subset of the HTTP protocol so it was unable to deal with the request. I have now added support for the HEAD request and it seems to work as expected. Install perl-xyne-arch>=2010.06.24.2 from my site or from [community] once your local mirror has synced.

The second issue is that Pacman doesn't handle HTTP errors correctly any longer. Check if a bug report has already been opened and open one if it hasn't. I think I saw one in another thread that was related to networking issues.

Ravenman · 2010-10-13 17:29:58

Hi to everyone:

I'm trying to install one updates server in my LAN. I'm using pkgd, but pacman doesn't works

Messages from the client side:

[root@workstation ~]# pacman -Sy
:: Synchronizing package databases...
--2010-10-13 12:24:37--  http://192.168.0.1:14687/core/core.db.tar.gz
Connecting to 192.168.0.1:14687... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-10-13 12:24:37 ERROR 404: Not Found.

error: failed to update core (error invoking external downloader)
--2010-10-13 12:24:39--  http://192.168.0.1:14687/extra/extra.db.tar.gz
Connecting to 192.168.0.1:14687... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-10-13 12:24:39 ERROR 404: Not Found.

error: failed to update extra (error invoking external downloader)
--2010-10-13 12:24:41--  http://192.168.0.1:14687/community/community.db.tar.gz
Connecting to 192.168.0.1:14687... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-10-13 12:24:41 ERROR 404: Not Found.

error: failed to update community (error invoking external downloader)
error: failed to synchronize any databases

Messages from the server side:

[root@server ~]# pkgd
PkgD now listening on port 14687...
request received from 192.168.0.2: GET /core/core.db.tar.gz HTTP/1.0
User-Agent: Wget/1.12 (linux-gnu)
Accept: */*
Host: 192.168.0.1:14687
Connection: Keep-Alive

returning 404 to 192.168.0.2
request received from 192.168.0.2: GET /extra/extra.db.tar.gz HTTP/1.0
User-Agent: Wget/1.12 (linux-gnu)
Accept: */*
Host: 192.168.0.1:14687
Connection: Keep-Alive

returning 404 to 192.168.0.2
request received from 192.168.0.2: GET /community/community.db.tar.gz HTTP/1.0
User-Agent: Wget/1.12 (linux-gnu)
Accept: */*
Host: 192.168.0.1:14687
Connection: Keep-Alive

returning 404 to 192.168.0.2
request received from 192.168.0.2: {"operation":"notify_master","port":"14687"}

registered slave 192.168.0.2:14687
request received from 192.168.0.2: {"operation":"notify_master","port":"14687"}

slave 192.168.0.2:14687 has already been registered
request received from 192.168.0.2: {"operation":"notify_master","port":"14687"}

slave 192.168.0.2:14687 has already been registered

What can I do for fix it?

Last edited by Ravenman (2010-10-13 17:37:00)

Xyne · 2010-10-15 15:40:49

PkgD only shares packages, not databases. It's normal that it would fail when a database is requested. Pacman should ignore those errors and try the next server in your mirrorlist. It should do the same when it requests a packages that the pkgd server doesn't have.

The errors can be safely ignored. There is no way to avoid them because of the way pacman works.

You could also use powerpill or bauerbill instead of pacman. They both support pkgd internally via a custom protocol and thus will not return any errors.

Ravenman · 2010-10-28 20:23:44

Xyne wrote:

PkgD only shares packages, not databases. It's normal that it would fail when a database is requested. Pacman should ignore those errors and try the next server in your mirrorlist. It should do the same when it requests a packages that the pkgd server doesn't have.
The errors can be safely ignored. There is no way to avoid them because of the way pacman works.

You could also use powerpill or bauerbill instead of pacman. They both support pkgd internally via a custom protocol and thus will not return any errors.

Something doesn't work on my LAN:

Console messages from one workstation:

[root@workstation ~]#powerpill -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update core (Not Found)
error: failed retrieving file 'extra.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update extra (Not Found)
error: failed retrieving file 'community.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update community (Not Found)
error: failed to synchronize any databases
:: Starting full system upgrade...
 there is nothing to do
[root@workstation ~]

and

[root@workstation ~]# bauerbill -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update core (Not Found)
error: failed retrieving file 'extra.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update extra (Not Found)
error: failed retrieving file 'community.db.tar.gz' from 192.168.0.1 : Not Found
error: failed to update community (Not Found)
error: failed to synchronize any databases
No unprivileged user specified with the "BuildAs" option
Please specify an unprivileged user for this operation: w1user
--> Searching for upgradable repo packages...
--> Switching to pacman: '/usr/bin/pacman' '--config' '/etc/pacman.conf' '-S' '-u'
:: Starting full system upgrade...
 there is nothing to do

I can't update the workstations from my LAN server ... somebody can help me ?

Last edited by Ravenman (2010-10-28 20:26:46)

SanskritFritz · 2010-10-28 20:28:41

man bauerbill says:

--pkgd [address:port]
[Powerpill option]

Xyne · 2010-10-28 21:26:52

@Ravenmann
Remove the PkgD servers from the Pacman configuration file and transfer them to the Bauerbill (or Powerpill) configuration file (PkgD =...). The remote servers will be used for database updates and then the PkgD servers will be queried for packages before moving on to remote servers for packages if necessary.

Ravenman · 2010-10-28 21:46:29

Xyne wrote:

@Ravenmann
Remove the PkgD servers from the Pacman configuration file and transfer them to the Bauerbill (or Powerpill) configuration file (PkgD =...). The remote servers will be used for database updates and then the PkgD servers will be queried for packages before moving on to remote servers for packages if necessary.

I made the changes and after I tried again:

[root@workstation ~]# powerpill -Syu
:: Synchronizing package databases...
downloading core.db.tar.gz...
downloading extra.db.tar.gz...
downloading community.db.tar.gz...
:: Starting full system upgrade...
 there is nothing to do
[root@workstation ~]

The LAN server is updated and exists changes (some new packages) but this update from workstation doesn't work. What am I doing wrong ?

Xyne · 2010-10-29 00:55:50

If it's downloading the databases then claiming that there is nothing to do, either the mirror is out-of-date or there really is nothing to do. You could try using a different mirror. Also check that you're using the same mirror on different machines.

Which packages are available to the server but not the workstation? Are they using the same architecture?

Ravenman · 2010-10-29 15:01:34

Xyne wrote:

If it's downloading the databases then claiming that there is nothing to do, either the mirror is out-of-date or there really is nothing to do. You could try using a different mirror. Also check that you're using the same mirror on different machines.
Which packages are available to the server but not the workstation? Are they using the same architecture?

I'm using the same mirror for all machines: Server = http://mirrors.kernel.org/archlinux/$repo/os/$arch

Updating messages from the server:

[root@server ~]# pacman -Syu 
:: Synchronizing package databases...
--2010-10-29 09:37:34--  http://mirrors.kernel.org/archlinux/core/os/i686/core.db.tar.gz
Resolving mirrors.kernel.org... 204.152.191.39, 130.239.17.6, 199.6.1.174
Connecting to mirrors.kernel.org|204.152.191.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 36472 (36K) [application/x-gzip]
Saving to: "/var/lib/pacman/core.db.tar.gz.part"

100%[===================================================>] 36,472      --.-K/s   in 0.003s  

2010-10-29 09:37:40 (11.1 MB/s) - "/var/lib/pacman/core.db.tar.gz.part" saved [36472/36472]

--2010-10-29 09:37:41--  http://mirrors.kernel.org/archlinux/extra/os/i686/extra.db.tar.gz
Resolving mirrors.kernel.org... 204.152.191.39, 130.239.17.6, 199.6.1.174
Connecting to mirrors.kernel.org|204.152.191.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 490165 (479K) [application/x-gzip]
Saving to: "/var/lib/pacman/extra.db.tar.gz.part"

100%[===================================================>] 490,165     --.-K/s   in 0.05s   

2010-10-29 09:37:46 (9.86 MB/s) - "/var/lib/pacman/extra.db.tar.gz.part" saved [490165/490165]

--2010-10-29 09:37:47--  http://mirrors.kernel.org/archlinux/community/os/i686/community.db.tar.gz
Resolving mirrors.kernel.org... 130.239.17.6, 199.6.1.174, 204.152.191.39
Connecting to mirrors.kernel.org|130.239.17.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 402301 (393K) [application/x-gzip]
Saving to: "/var/lib/pacman/community.db.tar.gz.part"

100%[===================================================>] 402,301     --.-K/s   in 0.06s   

2010-10-29 09:37:56 (6.76 MB/s) - "/var/lib/pacman/community.db.tar.gz.part" saved [402301/402301]

--2010-10-29 09:37:56--  http://repo.archlinux.fr/i686/archlinuxfr.db.tar.gz
Resolving repo.archlinux.fr... 213.186.62.207
Connecting to repo.archlinux.fr|213.186.62.207|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22709 (22K) [application/x-gzip]
Saving to: "/var/lib/pacman/archlinuxfr.db.tar.gz.part"

100%[===================================================>] 22,709      --.-K/s   in 0.003s  

2010-10-29 09:37:59 (7.86 MB/s) - "/var/lib/pacman/archlinuxfr.db.tar.gz.part" saved [22709/22709]

 Foreign packages: / 5 / 5

==> Software upgrade (new version) :
core/dhcpcd 5.2.7-1 -> 5.2.8-1

==> Continue upgrade ? [Y/n]
==> [V]iew package detail   [M]anually select packages
==> --------------------------------------------------
==> Y
:: Starting full system upgrade...
:: Replace antlr with extra/antlr2? [Y/n] 
resolving dependencies...
looking for inter-conflicts...

Remove (1): antlr-2.7.7-8

Total Removed Size:   1.26 MB

Targets (2): antlr2-2.7.7-1  dhcpcd-5.2.8-1

Total Download Size:    0.58 MB
Total Installed Size:   1.48 MB

Proceed with installation? [Y/n] 
:: Retrieving packages from core...
--2010-10-29 09:39:04--  http://mirrors.kernel.org/archlinux/core/os/i686/dhcpcd-5.2.8-1-i686.pkg.tar.xz
Resolving mirrors.kernel.org... 199.6.1.174, 204.152.191.39, 130.239.17.6
Connecting to mirrors.kernel.org|199.6.1.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 57656 (56K) [application/x-tar]
Saving to: "/var/cache/pacman/pkg/dhcpcd-5.2.8-1-i686.pkg.tar.xz.part"

100%[===================================================>] 57,656      --.-K/s   in 0.005s  

2010-10-29 09:39:05 (10.2 MB/s) - "/var/cache/pacman/pkg/dhcpcd-5.2.8-1-i686.pkg.tar.xz.part" saved [57656/57656]

:: Retrieving packages from extra...
--2010-10-29 09:39:05--  http://mirrors.kernel.org/archlinux/extra/os/i686/antlr2-2.7.7-1-i686.pkg.tar.xz
Resolving mirrors.kernel.org... 204.152.191.39, 130.239.17.6, 199.6.1.174
Connecting to mirrors.kernel.org|204.152.191.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 552136 (539K) [application/x-tar]
Saving to: "/var/cache/pacman/pkg/antlr2-2.7.7-1-i686.pkg.tar.xz.part"

100%[===================================================>] 552,136     --.-K/s   in 0.09s   

2010-10-29 09:39:15 (5.56 MB/s) - "/var/cache/pacman/pkg/antlr2-2.7.7-1-i686.pkg.tar.xz.part" saved [552136/552136]

checking package integrity...
(2/2) checking for file conflicts                       [##############################] 100%
(1/1) removing antlr                                    [##############################] 100%
(1/2) installing antlr2                                 [##############################] 100%
(2/2) upgrading dhcpcd                                  [##############################] 100%

Updating messages from the workstation (few minutes after the server upgrade):

[root@workstation ~]# powerpill -Syu
:: Synchronizing package databases...
 core                           3.4K   20.9M/s 00:00:00 [##############################] 100%
downloading extra.db.tar.gz...
 community                      3.4K   23.6M/s 00:00:00 [##############################] 100%
:: Starting full system upgrade...
 there is nothing to do

Some different packages between Server:

[root@server ~]# pacman -Qs firefox
local/firefox 3.6.12-1
    Standalone web browser from mozilla.org
[root@server ~]# pacman -Qs thunderbird
local/thunderbird 3.1.6-1
    Standalone Mail/News reader
[root@server ~]# pacman -Qs dhcpcd
local/dhcpcd 5.2.8-1 (base)
    RFC2131 compliant DHCP client daemon
[root@server ~]# pacman -Qs antlr
local/antlr2 2.7.7-1
    ANother Tool for Language Recognition, (formerly PCCTS) is a language tool that provides
    a framework for constructing recognizers, compilers, and translators from grammatical
    descriptions containing C++ or Java actions
[root@server ~]

and Workstation:

[root@workstation ~]# pacman -Qs firefox
local/firefox 3.6.11-1
    Standalone web browser from mozilla.org
[root@workstation ~]# pacman -Qs thunderbird
local/thunderbird 3.1.5-1
    Standalone Mail/News reader
[root@workstation ~]# pacman -Qs dhcpcd
local/dhcpcd 5.2.7-1 (base)
    RFC2131 compliant DHCP client daemon
[root@workstation ~]# pacman -Qs antlr
local/antlr 2.7.7-8
    ANother Tool for Language Recognition, (formerly PCCTS) is a language tool that provides
    a framework for constructing recognizers, compilers, and translators from grammatical
    descriptions containing C++ or Java actions
[root@workstation ~]

Yes, all the machines are using the same architecture.

Last edited by Ravenman (2010-10-29 15:03:25)

Xyne · 2010-10-30 17:10:18

What's the output of "-Si" instead of "-Qi" for those packages?

I suspect that this is unrelated to PkgD because it seems to be related to the database upgrades. You could try "pacman -Syy" to force an upgrade of all database.

What happens if you try to upgrade without using PkgD?

dwidmann · 2011-01-27 13:41:33

I've just recently stumbled onto pkgd and it seems nice Xyne. It took me a few minutes though after initially setting it up that it doesn't like it when I use pacman.conf's XferCommand option (in particular I was using (XferCommand = /usr/bin/curl -C - %u > %o). I don't know if it's mentioned somewhere within this monster thread. Unsetting that helped. I'm not sure if that's a broad issue or a specific issue. I just thought I'd chime in because it doesn't seem to be mentioned in the manpage.

Xyne · 2011-01-27 16:29:28

dwidmann wrote:

it doesn't like it when I use pacman.conf's XferCommand option (in particular I was using (XferCommand = /usr/bin/curl -C - %u > %o)

That isn't very informative. Please include a description of the problem next time, along with terminal output from both pacman and pkgd (or whatever is relevant).

I was able to determine that this is a Pacman bug, not a PkgD bug. PkgD only serves packages that is has. It returns HTTP 404 status when anything else is requested, e.g. other packages or the databases.

Pacman's internal downloader is able to detect the 404 status and move on to the next server in the list, which is expected behavior. When using the XferCommand, however, it doesn't detect the failed download and move on as it should.

I have opened a ticket on the bug tracker.

Note that powerpill has internal support for pkgd and bypasses the 404 errors by using a custom protocol to communicate with the pkgd servers.

Last edited by Xyne (2011-01-27 16:31:11)

Ravenman · 2011-01-27 21:19:09

Xyne wrote:

What's the output of "-Si" instead of "-Qi" for those packages?

Server:

[root@server ~]# pacman -Si firefox
Repository     : extra
Name           : firefox
Version        : 3.6.13-1
URL            : http://www.mozilla.org/projects/firefox
Licenses       : MPL  GPL  LGPL
Groups         : None
Provides       : None
Depends On     : xulrunner=1.9.2.13  desktop-file-utils
Optional Deps  : None
Conflicts With : None
Replaces       : None
Download Size  : 759.92 K
Installed Size : 3540.00 K
Packager       : Ionut Biru <ibiru@archlinux.org>
Architecture   : i686
Build Date     : Thu 09 Dec 2010 12:53:45 PM COT
MD5 Sum        : f99cf7218f5581755f27c078a9500b5c
Description    : Standalone web browser from mozilla.org

[root@server ~]# pacman -Si thunderbird
Repository     : extra
Name           : thunderbird
Version        : 3.1.7-3
URL            : http://www.mozilla.org/projects/thunderbird
Licenses       : MPL  GPL
Groups         : None
Provides       : None
Depends On     : gtk2  gcc-libs  mozilla-common  nss  libxt  shared-mime-info  alsa-lib dbus-glib  hunspell  sqlite3>=3.7.4
Optional Deps  : libcanberra: for sound support
Conflicts With : None
Replaces       : None
Download Size  : 8787.48 K
Installed Size : 32828.00 K
Packager       : Ionut Biru <ibiru@archlinux.org>
Architecture   : i686
Build Date     : Thu 30 Dec 2010 01:07:52 PM COT
MD5 Sum        : 9ed9a839b71cf6397aaa1366f7ab0f75
Description    : Standalone Mail/News reader

[root@server ~]# pacman -Si dhcpcd
Repository     : core
Name           : dhcpcd
Version        : 5.2.9-1
URL            : http://roy.marples.name/dhcpcd/
Licenses       : BSD
Groups         : base
Provides       : None
Depends On     : glibc  sh
Optional Deps  : None
Conflicts With : None
Replaces       : None
Download Size  :  56.39 K
Installed Size : 220.00 K
Packager       : Ronald van Haren <ronald.archlinux.org>
Architecture   : i686
Build Date     : Tue 07 Dec 2010 02:17:48 PM COT
MD5 Sum        : 7dc73b1738ae3b76c46f981bc8ef0308
Description    : RFC2131 compliant DHCP client daemon

Workstation:

[root@workstation ~]# pacman -Si firefox
error: package 'firefox' was not found
[root@workstation ~]# pacman -Si thunderbird
error: package 'thunderbird' was not found
[root@workstation ~]# pacman -Si dhcpcd
error: package 'dhcpcd' was not found
[root@workstation ~]#

Xyne wrote:

I suspect that this is unrelated to PkgD because it seems to be related to the database upgrades. You could try "pacman -Syy" to force an upgrade of all database.

[root@workstation ~]# pacman -Syy
:: Synchronizing package databases...
--2011-01-27 16:25:00--  http://mirrors.kernel.org/archlinux/core/os/i686/core.db.tar.gz
Resolving mirrors.kernel.org... 130.239.17.6, 149.20.20.135, 199.6.1.174, ...
Connecting to mirrors.kernel.org|130.239.17.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/core.db.tar.gz.part'

    [ <=>                                                 ] 3,435       --.-K/s   in 0s      

2011-01-27 16:25:00 (172 MB/s) - `/var/lib/pacman/core.db.tar.gz.part' saved [3435]

--2011-01-27 16:25:00--  http://mirrors.kernel.org/archlinux/extra/os/i686/extra.db.tar.gz
Resolving mirrors.kernel.org... 149.20.20.135, 199.6.1.174, 204.152.191.39, ...
Connecting to mirrors.kernel.org|149.20.20.135|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/extra.db.tar.gz.part'

    [ <=>                                                 ] 3,437       --.-K/s   in 0s      

2011-01-27 16:25:00 (160 MB/s) - `/var/lib/pacman/extra.db.tar.gz.part' saved [3437]

--2011-01-27 16:25:00--  http://mirrors.kernel.org/archlinux/community/os/i686/community.db.tar.gz
Resolving mirrors.kernel.org... 199.6.1.174, 204.152.191.39, 130.239.17.6, ...
Connecting to mirrors.kernel.org|199.6.1.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/community.db.tar.gz.part'

    [ <=>                                                 ] 3,445       --.-K/s   in 0s      

2011-01-27 16:25:00 (158 MB/s) - `/var/lib/pacman/community.db.tar.gz.part' saved [3445]

[root@workstation ~]#

Xyne wrote:

What happens if you try to upgrade without using PkgD?

[root@workstation ~]# powerpill -Syu
:: Synchronizing package databases...
--2011-01-27 16:28:03--  http://mirrors.kernel.org/archlinux/core/os/i686/core.db.tar.gz
Resolving mirrors.kernel.org... 199.6.1.174, 204.152.191.39, 130.239.17.6, ...
Connecting to mirrors.kernel.org|199.6.1.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/core.db.tar.gz.part'

    [ <=>                                                 ] 3,435       --.-K/s   in 0s      

2011-01-27 16:28:03 (118 MB/s) - `/var/lib/pacman/core.db.tar.gz.part' saved [3435]

--2011-01-27 16:28:03--  http://mirrors.kernel.org/archlinux/extra/os/i686/extra.db.tar.gz
Resolving mirrors.kernel.org... 204.152.191.39, 130.239.17.6, 149.20.20.135, ...
Connecting to mirrors.kernel.org|204.152.191.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/extra.db.tar.gz.part'

    [ <=>                                                 ] 3,437       --.-K/s   in 0s      

2011-01-27 16:28:03 (180 MB/s) - `/var/lib/pacman/extra.db.tar.gz.part' saved [3437]

--2011-01-27 16:28:03--  http://mirrors.kernel.org/archlinux/community/os/i686/community.db.tar.gz
Resolving mirrors.kernel.org... 130.239.17.6, 149.20.20.135, 199.6.1.174, ...
Connecting to mirrors.kernel.org|130.239.17.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/var/lib/pacman/community.db.tar.gz.part'

    [ <=>                                                 ] 3,445       --.-K/s   in 0s      

2011-01-27 16:28:03 (141 MB/s) - `/var/lib/pacman/community.db.tar.gz.part' saved [3445]

:: Starting full system upgrade...
 there is nothing to do
[root@workstation ~]#

Arch Linux

#126 2010-01-16 04:26:41

Re: pkgd: a daemon for sharing pkgs over your LAN

#127 2010-01-16 06:58:36

Re: pkgd: a daemon for sharing pkgs over your LAN

#128 2010-01-16 08:02:31

Re: pkgd: a daemon for sharing pkgs over your LAN

#129 2010-01-20 06:39:07

Re: pkgd: a daemon for sharing pkgs over your LAN

#130 2010-01-20 08:21:12

Re: pkgd: a daemon for sharing pkgs over your LAN

#131 2010-02-05 06:07:06

Re: pkgd: a daemon for sharing pkgs over your LAN

#132 2010-02-05 08:07:31

Re: pkgd: a daemon for sharing pkgs over your LAN

#133 2010-05-13 16:52:04

Re: pkgd: a daemon for sharing pkgs over your LAN

#134 2010-05-13 22:13:27

Re: pkgd: a daemon for sharing pkgs over your LAN

#135 2010-05-14 18:55:16

Re: pkgd: a daemon for sharing pkgs over your LAN

#136 2010-05-14 20:43:20

Re: pkgd: a daemon for sharing pkgs over your LAN

#137 2010-06-23 17:07:00

Re: pkgd: a daemon for sharing pkgs over your LAN

#138 2010-06-24 01:17:54

Re: pkgd: a daemon for sharing pkgs over your LAN

#139 2010-10-13 17:29:58

Re: pkgd: a daemon for sharing pkgs over your LAN

#140 2010-10-15 15:40:49

Re: pkgd: a daemon for sharing pkgs over your LAN

#141 2010-10-28 20:23:44

Re: pkgd: a daemon for sharing pkgs over your LAN

#142 2010-10-28 20:28:41

Re: pkgd: a daemon for sharing pkgs over your LAN

#143 2010-10-28 21:26:52

Re: pkgd: a daemon for sharing pkgs over your LAN

#144 2010-10-28 21:46:29

Re: pkgd: a daemon for sharing pkgs over your LAN

#145 2010-10-29 00:55:50

Re: pkgd: a daemon for sharing pkgs over your LAN

#146 2010-10-29 15:01:34

Re: pkgd: a daemon for sharing pkgs over your LAN

#147 2010-10-30 17:10:18

Re: pkgd: a daemon for sharing pkgs over your LAN

#148 2011-01-27 13:41:33

Re: pkgd: a daemon for sharing pkgs over your LAN

#149 2011-01-27 16:29:28

Re: pkgd: a daemon for sharing pkgs over your LAN

#150 2011-01-27 21:19:09

Re: pkgd: a daemon for sharing pkgs over your LAN

Board footer