From owner-freebsd-ports@FreeBSD.ORG Wed Oct 29 20:19:20 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A0D9AF7; Wed, 29 Oct 2014 20:19:20 +0000 (UTC) Received: from smtp11.services.sfr.fr (smtp11.services.sfr.fr [93.17.128.28]) by mx1.freebsd.org (Postfix) with ESMTP id D5058F72; Wed, 29 Oct 2014 20:19:19 +0000 (UTC) Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf1104.sfr.fr (SMTP Server) with ESMTP id CB57F7000105; Wed, 29 Oct 2014 21:19:17 +0100 (CET) Received: from wsfrf1114 (wsfrf1114 [10.18.24.28]) by msfrf1104.sfr.fr (SMTP Server) with ESMTP id C03137000090; Wed, 29 Oct 2014 21:19:17 +0100 (CET) X-SFR-UUID: 20141029201917787.C03137000090@msfrf1104.sfr.fr Date: Wed, 29 Oct 2014 21:19:17 +0100 (CET) From: listjm@club-internet.fr Reply-To: listjm@club-internet.fr To: matthew@freebsd.org, freebsd-ports Message-ID: <17341003.741730.1414613957776.JavaMail.www@wsfrf1114> Subject: pkg 1.4 freeze please test test test! MIME-Version: 1.0 X-SAVECOPY: true X-ORIGINATING-IP: 93.8.4.165 X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-REPLYTO: |~| Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 20:19:20 -0000 >> And now I bootstrapped pkg 1.3.8 and in every pkg operation I find this: >> >>> pkg: warning: database version 29 is newer than libpkg(3) version 27, >>> but still compatible > >Yeah. That's expected. There are DB schema changes in 1.4.2 *but* >nothing that should stop 1.3.8 from using the upgraded DB. ie. the >changes are generally adding new tables or new columns to existing >tables. Should be harmless, but do let us know if you get any >SQL-related errors. > > Cheers, > > Matthew No, all I did with 1.3.8 afterwards worked as expected: pkg update, upgrade, updating, check, autoremove, audit, delete and install. Best regards, Juan