Subject: Re: pkgsrc NetBSD 3.0_BETA/x86_64 bulk build results 2005-06-21
To: Thomas Klausner <wiz@NetBSD.org>
From: Julio M. Merino Vidal <jmmv84@gmail.com>
List: pkgsrc-bulk
Date: 06/22/2005 17:11:23
On Wed, 2005-06-22 at 16:51 +0200, Thomas Klausner wrote:
> On Tue, Jun 21, 2005 at 09:59:03AM +0200, Krister Walfridsson wrote:
> > pkgsrc bulk build results
> > NetBSD 3.0_BETA/x86_64
> 
> Diff to previous:
> 7,8c7,8
> <          Build started:                  Wed Jun 15 12:34:21 2005 UTC
> <          Build ended:                    Fri Jun 17 22:46:24 2005 UTC
> ---
> >          Build started:                  Mon Jun 20 07:26:32 2005 UTC
> >          Build ended:                    Tue Jun 21 07:03:06 2005 UTC
> 10,15c10,15
> <          Successfully packaged:          4766
> <          Packages really broken:         205
> <          Pkgs broken due to them:        154
> <          Total broken:                   359
> <          Not packaged:                   344
> <          Total:                          703
> ---
> >          Successfully packaged:          4788
> >          Packages really broken:         204
> >          Pkgs broken due to them:        133
> >          Total broken:                   337
> >          Not packaged:                   343
> >          Total:                          680
> 20c20
> < ftp://ftp.NetBSD.org/pub/pkgsrc/misc/kristerw/pkgstat/amd64-3.0/20050617.2246/broken.html
> ---
> > ftp://ftp.NetBSD.org/pub/pkgsrc/misc/kristerw/pkgstat/amd64-3.0/20050621.0703/broken.html
> 27d26
> < audio/festival             24      tech-pkg@NetBSD.org
> 36a36
> > editors/speedbar           3       cjones@NetBSD.org
> 
> Segfault.
> 
> 43d42
> < audio/festival             24      tech-pkg@NetBSD.org
> 161a161
> > meta-pkgs/gnome-base       1       jmmv@NetBSD.org
> 
>  BULK>  /usr/sbin/pkg_add -K /var/db/pkg  /usr/pkgsrc/packages/All/gnome-vfs2-smb-2.10.1.tgz
>  tar: Cannot create lib/security (Not a directory)
>  tar: Cannot create lib/security (Not a directory)

AFAICS, it's used to store pam modules.

The problem seems to be caused by a package leaving an stale
lib/security *file* (or which was created by mistake), so after that,
no other package can install stuff into that directory.

Maybe by looking at the file that was left in the box we can guess were
it came from?

-- 
Julio M. Merino Vidal <jmmv84@gmail.com>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/