On Tue, Jul 22, 2008 at 08:01:59PM -0500, Dan McGee [EMAIL PROTECTED] wrote:
# get setup correct
sudo rm
/var/lib/pacman/sync/{community,extra,pacman-git,testing,unstable}/.lastupdate
Ouch, this is ugly. Why not using -Syy?
pgpCkz90IT4QB.pgp
Description: PGP signature
On Wed, Jul 23, 2008 at 3:18 AM, Xavier [EMAIL PROTECTED] wrote:
On Wed, Jul 23, 2008 at 3:01 AM, Dan McGee [EMAIL PROTECTED] wrote:
Here is a bisect script I have used with pacman in the past to do it
automatically, I can't remember exactly which bug we were trying to
track down but the ideas
On Wed, Jul 23, 2008 at 3:01 AM, Miklos Vajna [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 08:01:59PM -0500, Dan McGee [EMAIL PROTECTED] wrote:
# get setup correct
sudo rm
/var/lib/pacman/sync/{community,extra,pacman-git,testing,unstable}/.lastupdate
Ouch, this is ugly. Why not using
On Wed, Jul 23, 2008 at 07:05:43AM -0500, Dan McGee [EMAIL PROTECTED] wrote:
On Wed, Jul 23, 2008 at 3:01 AM, Miklos Vajna [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 08:01:59PM -0500, Dan McGee [EMAIL PROTECTED]
wrote:
# get setup correct
sudo rm
On Wed, Jul 23, 2008 at 7:18 AM, Miklos Vajna [EMAIL PROTECTED] wrote:
On Wed, Jul 23, 2008 at 07:05:43AM -0500, Dan McGee [EMAIL PROTECTED] wrote:
On Wed, Jul 23, 2008 at 3:01 AM, Miklos Vajna [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 08:01:59PM -0500, Dan McGee [EMAIL PROTECTED]
On Wed, Jul 23, 2008 at 2:01 PM, Dan McGee [EMAIL PROTECTED] wrote:
It makes 'make check' (and with that, 'make distcheck', etc.) fail if
the pactest script returns anything but zero. I've had this change in
a local branch for ages, but we need something else- a way to indicate
known failure
On Wed, Jul 23, 2008 at 7:42 AM, Xavier [EMAIL PROTECTED] wrote:
On Wed, Jul 23, 2008 at 2:01 PM, Dan McGee [EMAIL PROTECTED] wrote:
It makes 'make check' (and with that, 'make distcheck', etc.) fail if
the pactest script returns anything but zero. I've had this change in
a local branch for
On Wed, Jul 23, 2008 at 2:51 PM, Dan McGee [EMAIL PROTECTED] wrote:
I was thinking of adding some kind of self.knownoutcome flag to
pactest, and have that basically suppress the return code incrementing
if it was set to fail or something. (or just
self.knownfailure=true.) Does that make sense
I was thinking of adding some kind of self.knownoutcome flag to
pactest, and have that basically suppress the return code incrementing
if it was set to fail or something. (or just
self.knownfailure=true.) Does that make sense to anyone? The problem
is right now we have no way of
On Wed, Jul 23, 2008 at 07:29:45AM -0500, Dan McGee [EMAIL PROTECTED] wrote:
Ahh, and I forgot to mention that the core .lastupdate was not
deleted. This was a key part of the equation if I remember right
because of interactions with packages also in testing.
Thanks, that was the part I
On Sat, Jul 19, 2008 at 2:25 PM, Nagy Gabor [EMAIL PROTECTED] wrote:
Hi!
I've tried -Su again...
I've just run into a very hard to fix error.
[EMAIL PROTECTED] ~]$ LANG=C sudo pacman -Su --ignore mplayer
...
xulrunner: /usr/include/xulrunner-1.9 exists in filesystem
xulrunner:
On Sat, Jul 19, 2008 at 2:25 PM, Nagy Gabor [EMAIL PROTECTED]
wrote:
Hi!
I've tried -Su again...
I've just run into a very hard to fix error.
[EMAIL PROTECTED] ~]$ LANG=C sudo pacman -Su --ignore mplayer
...
xulrunner: /usr/include/xulrunner-1.9 exists in filesystem
xulrunner:
On Tue, Jul 22, 2008 at 12:34 PM, Nagy Gabor [EMAIL PROTECTED] wrote:
I think this is not a regression, but a behaviour change. What did the
old pacman do when we have a real symlink-dir conflict? I mean a
conflict which won't disappear after the upgrade_remove part:
fileconflict003 should
Signed-off-by: Dan McGee [EMAIL PROTECTED]
:04 04 ea3e9f52732a5412f2e77e2a1060c3247636de7b
a234d7e4ca725edc301f696640d897ce54dfb3b8 Mlib
OMG. That part is totally unrelated here, but it makes our
fileconflict003.py pass (due to its bug);-). Obviously that won't
solve
OMG. That part is totally unrelated here, but it makes our
fileconflict003.py pass (due to its bug);-). Obviously that won't
solve our problem (unfortunately).
typo: fileconflict004.py
For example, this will fail:
self.description = foo
p1 = pmpkg(pkg1, 1.0-1)
Hi!
I've tried -Su again...
I've just run into a very hard to fix error.
[EMAIL PROTECTED] ~]$ LANG=C sudo pacman -Su --ignore mplayer
...
xulrunner: /usr/include/xulrunner-1.9 exists in filesystem
xulrunner: /usr/lib/xulrunner-1.9 exists in filesystem
xulrunner: /usr/lib/xulrunner-devel-1.9
Nagy Gabor wrote:
Hi!
I've tried -Su again...
I've just run into a very hard to fix error.
[EMAIL PROTECTED] ~]$ LANG=C sudo pacman -Su --ignore mplayer
...
xulrunner: /usr/include/xulrunner-1.9 exists in filesystem
xulrunner: /usr/lib/xulrunner-1.9 exists in filesystem
xulrunner:
17 matches
Mail list logo
