From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /usr/portage/packages/Packages - what for?
Date: Tue, 15 Sep 2009 15:08:47 +0100 [thread overview]
Message-ID: <20090915150847.0e1c4a3f@zaphod.digimed.co.uk> (raw)
In-Reply-To: <tkrat.ca998f2262d7f59a@igpm.rwth-aachen.de>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Tue, 15 Sep 2009 15:19:01 +0200 (CEST), Helmut Jarausch wrote:
> I have the impression that when rsync'ing /usr/portage/packages from
> another machine (BINSERVER),
> emerge --update --newuse --deep --buildpkg @system @world
> doesn't update packages which are upto-date on BINSERVER
> but not upto-date on the local machine.
Does "emaint --fix binhost" help?
--
Neil Bothwick
One person's error is another person's data.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-09-15 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:19 [gentoo-user] /usr/portage/packages/Packages - what for? Helmut Jarausch
2009-09-15 13:21 ` Frank Steinmetzger
2009-09-15 14:04 ` Fabrice Delliaux
2009-09-15 17:45 ` Mike Williams
2009-09-15 14:08 ` Neil Bothwick [this message]
2009-09-15 16:30 ` Helmut Jarausch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090915150847.0e1c4a3f@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox