From owner-freebsd-ports@freebsd.org Wed May 23 07:45:37 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2B4CEF38E5 for ; Wed, 23 May 2018 07:45:37 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 389247CC30 for ; Wed, 23 May 2018 07:45:36 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 40rPYR69TzzZsl; Wed, 23 May 2018 09:39:55 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 2A7AmMWYoz47; Wed, 23 May 2018 09:39:41 +0200 (CEST) Received: from marvin.madpilot.net (host122-157-dynamic.180-80-r.retail.telecomitalia.it [80.180.157.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Wed, 23 May 2018 09:39:41 +0200 (CEST) Subject: Re: unreliable pkg upgrades To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-ports@freebsd.org References: From: Guido Falsi Openpgp: preference=signencrypt Autocrypt: addr=mad@madpilot.net; prefer-encrypt=mutual; keydata= xsBNBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAHNHkd1aWRvIEZhbHNpIDxtYWRAbWFkcGlsb3QubmV0PsLAeQQTAQgAIwIbAwIeAQIXgAUL CQgHAwUVCgkICwQWAgMBBQJS79AgAhkBAAoJEBrmhg5Wy9KTc0kH/RO64ORBlTbTHaUaOj8F Je5O5NU2Pt9Cyt5ZWBRvxntr1zPTJGKRPS9ihlIfqT4ZvEngQGp57EUyFbCpI0UWasTerImM tt5WACnGmCzUTB39UXx8Oy4b1EgWeTJQ747e/F1mQLXTNa6ijRBE9fYlTb4gAkPN88/wVV9v 3PZozKLTg16ghBzHM/P7Lk8L7clPEZChX1FTa/6eSt3nvzfCuTMZbBPJF/ph+q1KyPqRgVfh tyhu5dvgMoPz/ni41IfeSrkJTD5RXzdyGR9q4Z1NYeBsLkRjC4LxKAP5KqUsvlOUjKvO1byj ApYdMarol+IGkaSk9e3zVYAJkWKjn/ni8XbOwU0EUxB7QQEQAKFhrDceoPdK/IHDSmoj6SQY isvM7VdhcleS7E9DoEAVt7yMbf6HbbMVTTY6ckvwTWQssywLBXNVqxgc4WLJjzfUhgef+WE7 5M3+WFYlOVQLGZY/zEVgma1raYnOHNAOzeHLDmEXjbZP6vGAeDyBbGfQPpE7qGYZ7ubeT3Xw QO+PklcCrvOPj2ZPcAxGNS2xVU/LzONqCrJqLMJSIcCdsbiSP4G5PnDFHtMokaTY6OEr8OEQ fOAerhcHUa/z7Uu8YtmaqKH+QGkE/WEgaRqSiTnv0JOTD+DxehaqvoKPPZ++2NpCZMHB2i6A /xifmQwEiIjEXtcueBRzkNUQkxhqZyS13SrhocL9ydtaVPBzZatAEjUDDEJmAMLVFs45qfyh MiNapHJo2n3MW/E5omqCvEkDdWX/en3P7CK2TemeaDghMsgkNKax/z0wNo5UZCkOPOz0xpNi UilOVbkuezZZNg65741qee2lfXhQIaZ66yT7hphc/N/z3PIAtLeze4u1VR2EXAuZ2sWAdlKC NTlJMsaU/x70BV11Wd/ypnVzM68dfdQIIAj1iMFAD/lXGlEUmKXg5Ov2VQDlTntQoanCYrAg +8CttPzjrydgLZFq3hrtQmfc0se5yv1WHS69+BsUOG09RvvawUDZxUjW19kyeN9THaNRgow3 kSuArUp6zSmJABEBAAHCwF8EGAEIAAkFAlMQe0ECGwwACgkQGuaGDlbL0pMN5wgA4bCkX/qw EVC06ToeR6C2putmSWQMgpDaqrv65Hubo+QGmg2P4ewTYQQ4g6oYWS03qHxqVVWhKz7FjfrV +dH8qbCLfSgIcvdBha7ayGZVrsiuMLKGbw36fcmkZPpSDOfHcP0XH8Z+u9CWj0xUkTxAlZ/7 i6gYSUpG2JWNtdmE/X8VVEyXusCLwy0K0BI60A/4dRTIX3C4QKrJ3ZbUXegz70ynjHf+lQMZ 9IZKASoRMuS5FozPQh6abvmwZEPdf5I9riUElzvHrqJ8Bx0t3Pujdoth+yNHpnBxrtO8LkQd rQ58P0SwcaIX33T2U9pG8bhu5YVR88FQ8OQ0cEsPBpDncg== Message-ID: Date: Wed, 23 May 2018 09:39:40 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2018 07:45:37 -0000 On 05/22/18 23:58, Miroslav Lachman wrote: > Am I the only one seeing occasional unreliable pkg upgrades? [...] > root@jahoda ~/# pkg upgrade devel/php-composer > Updating codelab repository catalogue... > codelab repository is up to date. > All repositories are up to date. > The following 1 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: >         php71-composer: 1.6.3 > > Number of packages to be installed: 1 > > The process will require 2 MiB more space. > 380 KiB to be downloaded. > > Proceed with this action? [y/N]: y > [1/1] Fetching php71-composer-1.6.3.txz: 100%  380 KiB 389.3kB/s    00:01 > Checking integrity... done (1 conflicting) >   - php71-composer-1.6.3 conflicts with php-composer-1.6.2 on > /usr/local/bin/composer > Checking integrity... done (0 conflicting) > Conflicts with the existing packages have been found. > One more solver iteration is needed to resolve them. > The following 2 package(s) will be affected (of 0 checked): > > Installed packages to be REMOVED: >         php-composer-1.6.2 > > New packages to be INSTALLED: >         php71-composer: 1.6.3 > > Number of packages to be removed: 1 > Number of packages to be installed: 1 > > Proceed with this action? [y/N]: y > [1/2] Deinstalling php-composer-1.6.2... > [1/2] Deleting files for php-composer-1.6.2: 100% > [2/2] Installing php71-composer-1.6.3... > [2/2] Extracting php71-composer-1.6.3: 100% Since this is referencing a port to which I committed lately I'm felling compelled to reply. Adding php flavors to composer required changhing the pkgname, so pkg considers it a different one. I added an entry in UPDATING about this, entry 20180412, explaining you had to take a manual step to let pkg know about the name change. If you skipped that what you're seeing is normal. Unluckily for flavoring php (and also python) ports there is no other way than to change the package name to include the php (or python) version they are flavored as, which introduces a discontinuity in pkg update work. Usually UPDATING file has some indication about this. > > > Why it is not handled automatically like in other OSes? The present infrastructure accounts different package names as different packages, but flavoring requires a package name change in these situations and there is no general was to discover which one of the new flavors is the desired one anyway. pkg manages automatically a lot of situation but from time to time manual intervention is required. In my experience this holds true for all OSes. Flavoring (especially php/python flavoring)introduces changes which simply cannot be automated. (The quantity of manual intervention changes from OS to OS and from time to time, but that's also normal) -- Guido Falsi