On Sat, Nov 1, 2008 at 7:48 AM, Allan McRae <[EMAIL PROTECTED]> wrote: > Dan McGee wrote: >> >> On Fri, Oct 31, 2008 at 10:31 AM, Nagy Gabor <[EMAIL PROTECTED]> >> wrote: >> >>>> >>>> On Fri, Oct 24, 2008 at 12:53 AM, Xavier <[EMAIL PROTECTED]> wrote: >>>> >>>>> >>>>> On Fri, Oct 24, 2008 at 2:09 AM, Nagy Gabor >>>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>>> >>>>>> See: >>>>>> http://repo.or.cz/w/pacman-ng.git?a=shortlog;h=refs/heads/working >>>>>> >>>>>> This is a big behavior change (iirc it restores the old behavior). >>>>>> Opinions? >>>>>> >>>>>> >>>>> >>>>> This is fine for me. But that means we consider bug 7884 as invalid, >>>>> which was opened by Dan. So as I said in the last comment of that >>>>> bug, we have to wait for his input :) >>>>> >>>> >>>> Damn, this is a huge code cleanup. I like it. I've pulled it into my >>>> working branch (the latest version). >>>> >>>> One thing I noticed and/or thought of- should we make the return >>>> status of this command different depending on whether there are >>>> upgrades available? That would make this super-easy to wrap in some >>>> sort of "up2date" script or something rather than having to parse the >>>> output. >>>> >>> >>> This is a good idea. But there is something I missed before my comment >>> on FS#11737. The new -Qu ignores replacements. However, my comment >>> there has some suggestions (independent from -Qu) which could "fix" >>> this. (However this is a minor issue irl, imho) >>> >> >> Hmm, this isn't quite what I expected either. Can we clean up this >> garbage in any way? >> >> $ ./src/pacman/pacman -Qu >> warning: alsa-lib: local (1.0.17a-2) is newer than extra (1.0.17a-1) >> warning: gvim: local (7.2.25-1) is newer than extra (7.1.330-1) >> warning: namcap: local (2.1-2) is newer than extra (2.1-1) >> warning: openoffice-base: local (3.0.0-3) is newer than extra (3.0.0-2) >> warning: pacman-git: local (20081031-1) is newer than pacman-git-64 >> (20081028-1) >> warning: pycairo: local (1.6.4-2) is newer than extra (1.6.4-1) >> warning: pygobject: local (2.15.4-2) is newer than extra (2.15.4-1) >> warning: pygtk: local (2.13.0-2) is newer than extra (2.13.0-1) >> warning: python: local (2.6-2) is newer than extra (2.5.2-5) >> warning: python-numeric: local (24.2-3) is newer than extra (24.2-2) >> warning: sonata: local (1.5.3-2) is newer than extra (1.5.3-1) >> warning: vi: local (7.2.25-1) is newer than core (7.1.330-1) >> warning: vim: local (7.2.25-1) is newer than extra (7.1.330-1) >> warning: vte: local (0.17.4-2) is newer than extra (0.17.4-1) >> > > They all look like python rebuilds from [testing]. Are you using a local > conf file there which has testing disabled?
Oh, I know exactly what they are- sorry for not being more descriptive. I was just pointing to the fact that this new -Qu operation even prints these guys, as no other query operation AFAIK would perform similar behavior. It seems irrelevant from the "-u as a filter" point of view. (And the reason you see these is because my testing repo is much more up to date than my "regular" repos) -Dan _______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev