Re: pkg 1.4 freeze please test test test!

On Sat, Nov 01, 2014 at 04:13:32PM +0100, Marc UBM wrote:
> On Wed, 29 Oct 2014 00:19:33 +0100
> Baptiste Daroussin <bapt_at_FreeBSD.org> wrote:
> 
> > Hi all,
> > 
> > We are starting the release process of pkg 1.4, we want to have a better release
> > process than with every single previous version of pkg. For that we will need
> > you help!
> > 
> > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > 
> > Changes you can expect in pkg 1.4 are the following:
> > - Loads of bug fixes
> > - Stricter checking of the path passed via the plist
> > - Removal of the bundled libyaml
> > - new --raw-format to chose the output format for info -R and search -R
> > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become FreeBSD:10:amd64)
> >   the old ABI is available as a fallback in ALTABI
> > - pkg check now support a quiet mode
> > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> >   configuration files
> > - new _at_config keyword to mark a file as a config file (during
> >   upgrade/reinstallation it will try to merge the configuration with the one the
> >   user may have modified) an option AUTOMERGE is available to prevent
> >   automerging if automerge fails a .pkgnew file will be created along with the
> >   untouched user version of the configuration
> > - The update procedure has been improved and speed up a lot (in particular for
> >   machine with low resources)
> > - The unique identifier has been modified to be pkgname meaning now ports can be
> >   moved in new categories without having to be considered a different package
> > - Only libraries starting by lib* are added to the provided libraries
> > - General speed up of all operations
> > 
> > We need help in testing, but we also need help in writing regression tests !
> > The more we have tests the more stable the releases will be.
> > 
> > The release will also allow to be able to package base!
> > 
> > regards,
> > Bapt
> 
> The update is failing for me with:
> 
> .../usr/ports/ports-mgmt/pkg-devel# make all install clean
> ===>  Installing for pkg-1.4.0.a3
> ===>  Checking if pkg already installed
> pkg-static: sqlite error while executing DROP INDEX
> packages_unique;CREATE UNIQUE INDEX packages_unique ON packages(name);
> in file pkgdb.c:2246: UNIQUE constraint failed: packages.name *** Error
> code 74
> 
> Stop.
> make[1]: stopped in /usr/ports/ports-mgmt/pkg-devel
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/ports-mgmt/pkg-devel
> 
> 
> 
> portmaster fails with:
> root_at_ubm:/usr/ports/ports-mgmt/pkg-devel# portmaster -d pkg
>         ===>>> No ORIGIN in /var/db/pkg/pkgconf-0.9.7/+CONTENTS
> 
> 
> ===>>> Cannot continue
> ===>>> Aborting update
> 
> ===>>> Killing background jobs
> Terminated
> ===>>> Exiting
> 
> make.conf related options:
> 
> #enable pkgng (might be superfluous)
> WITH_PKGNG=yes
> #enable PKGNG devel
> WITH_PKGNG=devel
> 
> Am I doing something wrong?

You are doing nothing wrong but that probably means you have ancient packages
that never got upgraded (in the old time it was allowed to have 2 packages
installed with the same name) we have fixed that over the time and that is why
we had unicity set to origin as a hack for a while, we are now moving to unique
name so you have to make sure that all your installed packages are up to date
before moving to new pkg.

At least make sure you do not have 2 packages with the same name.

Concerning portmaster I have no idea why it now thinks you are not using
pkg :(

regards,
Bapt