On 2/21/07, Pierre Schmitz wrote:

I think thjere is a typo in the pkgbuild:

install -m644 -D $startdir/src/pacman-lib/contrib/bash_completion \ $startdir/pkg/etc/bach_completion.d/pacman

should be bash and not bach

Well damn, i didn't actually mean to keep those in there. Must have overlooked them. Please upgrade/use this package, as it doesn't add the completion stuff (yet): http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.21-2-i686.pkg.tar.gz

On 2/21/07, Aaron Griffin wrote:

One more thing. Here is a list of remaining "bugs" assigned to pacman: http://bugs.archlinux.org/index.php?project=1&type=1&cat=6

All of these we have currently deemed non-critical to the release, but if you disagree, please bring it up. Also, if you find any that are closable, that's great too.

http://bugs.archlinux.org/task/6465 Not critical, but my take on it is there. -Dan

Fixed the segfault below. New package is here: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.22-1-i686.pkg.tar.gz On 2/21/07, Alessio 'mOLOk' Bolognino wrote:

sudo pacman3 -U ~/packages/ncmpc-svn-5200-2-i686.pkg.tar.gz ... Internal pacman error: Segmentation fault Please submit a full bug report, with the given package if appropriate.

Well, this is fixed, but not in the way it should be. The actual error is related to http://bugs.archlinux.org/task/3492 and is a complicated fix. For right now, I'm reporting an error due to: a) the difficulty in fixing that *correctly* b) the fact that it is an edge case, an operation typically done with -S Here is my output (trimmed for email purposes): $ sudo pacman3 -U ncmpc-svn-5200-2-i686.pkg.tar.gz ncmpc-svn 79.6K 112.7K/s 00:00:01 [###########] 100% loading package data... done. checking dependencies... error: replacing packages with -A and -U is not supported yet error: please remove 'ncmpc' first, using -Rd error: failed to prepare transaction (conflicting dependencies) While it's not the best solution, it will work for the time being.

When I'm doing a system upgrade or installing a package and i run makepkg3, it complains for pacman already running and tell that can not do the dependency check or so. Is this a bug or an intended behaviour?

Could you tell us what makepkg3's output was because I think stonecrest mentioned this on IRC and knowing if it is the same thing would be helpful. ~ Jamie / yankees26

On 2/25/07, Alessio 'mOLOk' Bolognino wrote:

On 08:59 Sun 25 Feb , James Rosten wrote:

...

...

When I'm doing a system upgrade or installing a package and i run makepkg3, it complains for pacman already running and tell that can not do the dependency check or so. Is this a bug or an intended behaviour?

Could you tell us what makepkg3's output was because I think stonecrest mentioned this on IRC and knowing if it is the same thing would be helpful.

here it is:

(12000)$> makepkg3 ==> Entering fakeroot environment ==> Making package: gpomme 1.1-3 (Sun Feb 25 16:34:25 CET 2007) ==> Checking Runtime Dependencies... error: unable to lock database ==> ERROR: pacman3 returned a fatal error (1): if you're sure a package manager is not already running, you can remove /tmp/pacman.lck ==> Checking Buildtime Dependencies... ==> Retrieving Sources... -> Found gpomme-1.1.tar.gz in build dir ==> Validating source files with md5sums gpomme-1.1.tar.gz ... Passed ==> WARNING: Integrity checks (sha1) are missing or incomplete. ==> Extracting Sources... -> tar -xf gpomme-1.1.tar.gz ==> Removing existing pkg/ directory... [...]

Did you try doing another pacman operation that locks the DB right after? That would have likely failed too. If you read the message, it indicates that the lock file exists, which happens if pacman is running an operation that requires a locked DB. Try following the instructions given- if you are sure pacman is not running, remove the lock file. If you can duplicate this bug after trying that, be sure to give the exact steps leading up to it. -Dan