From owner-freebsd-pkg@freebsd.org Sun Oct 11 03:48:39 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B672A110A7 for ; Sun, 11 Oct 2015 03:48:39 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id E21937C4 for ; Sun, 11 Oct 2015 03:48:38 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.TOMSK.ru ([212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 38900780 for freebsd-pkg@freebsd.org; Sun, 11 Oct 2015 09:48:35 +0600 Received: from admin.sibptus.TOMSK.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.TOMSK.ru (8.14.9/8.14.7) with ESMTP id t9B3mWjX018267 for ; Sun, 11 Oct 2015 09:48:34 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.TOMSK.ru (8.14.9/8.14.7/Submit) id t9B3mVG7018266 for freebsd-pkg@freebsd.org; Sun, 11 Oct 2015 09:48:31 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.TOMSK.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Sun, 11 Oct 2015 09:48:31 +0600 From: Victor Sudakov To: freebsd-pkg@freebsd.org Subject: Deleting a ports tree in poudriere Message-ID: <20151011034831.GA18209@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: OAO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 03:48:39 -0000 Colleagues, I have deleted the default ports tree with "poudriere ports -d", but the files are still there in /var/poudriere/ports/default/. I did not give the "-k" option. Am I supposed to remove the tree manually or what? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru From owner-freebsd-pkg@freebsd.org Sun Oct 11 21:00:27 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28A169B1074 for ; Sun, 11 Oct 2015 21:00:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 092301A3F for ; Sun, 11 Oct 2015 21:00:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 003F99B106B; Sun, 11 Oct 2015 21:00:27 +0000 (UTC) Delivered-To: pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F40719B106A for ; Sun, 11 Oct 2015 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B36AF1A26 for ; Sun, 11 Oct 2015 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9BL0Q6s060349 for ; Sun, 11 Oct 2015 21:00:26 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201510112100.t9BL0Q6s060349@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: pkg@FreeBSD.org Subject: Problem reports for pkg@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 11 Oct 2015 21:00:26 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 21:00:27 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 193995 | [PATCH] ports-mgmt/pkg: floating point exception 1 problems total for which you should take action. From owner-freebsd-pkg@freebsd.org Mon Oct 12 02:48:02 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B91EAA11515 for ; Mon, 12 Oct 2015 02:48:02 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 29DE381A for ; Mon, 12 Oct 2015 02:48:00 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.TOMSK.ru ([212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 38901742 for freebsd-pkg@freebsd.org; Mon, 12 Oct 2015 08:47:58 +0600 Received: from admin.sibptus.TOMSK.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.TOMSK.ru (8.14.9/8.14.7) with ESMTP id t9C2ltR2029645 for ; Mon, 12 Oct 2015 08:47:57 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.TOMSK.ru (8.14.9/8.14.7/Submit) id t9C2lt0Q029644 for freebsd-pkg@freebsd.org; Mon, 12 Oct 2015 08:47:55 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.TOMSK.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 12 Oct 2015 08:47:55 +0600 From: Victor Sudakov To: freebsd-pkg@freebsd.org Subject: Re: Deleting a ports tree in poudriere Message-ID: <20151012024755.GA29622@admin.sibptus.tomsk.ru> References: <20151011034831.GA18209@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151011034831.GA18209@admin.sibptus.tomsk.ru> Organization: OAO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2015 02:48:02 -0000 Victor Sudakov wrote: > > I have deleted the default ports tree with "poudriere ports -d", but > the files are still there in /var/poudriere/ports/default/. I did not > give the "-k" option. > > Am I supposed to remove the tree manually or what? Opened an issue: https://github.com/freebsd/poudriere/issues/353 -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru From owner-freebsd-pkg@freebsd.org Mon Oct 12 21:09:24 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1A54A1250C for ; Mon, 12 Oct 2015 21:09:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9583D1A5E for ; Mon, 12 Oct 2015 21:09:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from karviainen.kapsi.fi ([217.30.184.182] helo=roundcube.kapsi.fi) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ZlkLS-0002Uh-IQ for freebsd-pkg@freebsd.org; Tue, 13 Oct 2015 00:09:22 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 13 Oct 2015 00:09:22 +0300 From: Arto Pekkanen To: freebsd-pkg@freebsd.org Message-ID: <0e4a66578a8ad68e97dd320458bec514@kapsi.fi> X-Sender: isoa@kapsi.fi User-Agent: RoundCube Webmail/0.9.4 X-SA-Exim-Connect-IP: 217.30.184.182 X-SA-Exim-Mail-From: isoa@kapsi.fi X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 Subject: pkg always tries to install graphics/jpeg as bogus dependency X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mail.kapsi.fi) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2015 21:09:24 -0000 Here follows the console output: """ # pkg install wifimgr Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. Updating Local repository catalogue... Local repository is up-to-date. All repositories are up-to-date. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: wifimgr: 1.11_1 [FreeBSD] jpeg: 8_6 [FreeBSD] The process will require 2 MiB more space. 94 KiB to be downloaded. Proceed with this action? [y/N]: y Fetching wifimgr-1.11_1.txz: 100% 94 KiB 96.7kB/s 00:01 Checking integrity... done (2 conflicting) Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: wifimgr: 1.11_1 [FreeBSD] The process will require 405 KiB more space. Proceed with this action? [y/N]: y [1/1] Installing wifimgr-1.11_1... [1/1] Extracting wifimgr-1.11_1: 100% [root@leno ~]# pkg info jpeg pkg: No package(s) matching jpeg [root@leno ~]# pkg rquery "%n-%v [%R]" jpeg jpeg-8_6 [FreeBSD] jpeg-8_6 [Local] [root@leno ~]# pkg rquery "%n-%v [%R] %rn" jpeg [root@leno ~]# """ Why does pkg try to install jpeg8_6 even if no package run-depends on it? It does not prevent packages from installing, but it does waste time with the conflict resolution. What should I do to resolve this issue? PS. The "Local" repository is my overlay repository where I've built some packages with specific options. It is configured with priority 100. -- Arto Pekkanen From owner-freebsd-pkg@freebsd.org Tue Oct 13 16:12:58 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1FDEA128C5 for ; Tue, 13 Oct 2015 16:12:58 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9452110E6 for ; Tue, 13 Oct 2015 16:12:58 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from karviainen.kapsi.fi ([217.30.184.182] helo=roundcube.kapsi.fi) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Zm2C4-0006gJ-Up for freebsd-pkg@freebsd.org; Tue, 13 Oct 2015 19:12:53 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 13 Oct 2015 19:12:52 +0300 From: Arto Pekkanen To: freebsd-pkg@freebsd.org In-Reply-To: <0e4a66578a8ad68e97dd320458bec514@kapsi.fi> References: <0e4a66578a8ad68e97dd320458bec514@kapsi.fi> Message-ID: <0cfd68b732214528b11f950b24a0cddb@kapsi.fi> X-Sender: isoa@kapsi.fi User-Agent: RoundCube Webmail/0.9.4 X-SA-Exim-Connect-IP: 217.30.184.182 X-SA-Exim-Mail-From: isoa@kapsi.fi X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 Subject: Re: pkg always tries to install graphics/jpeg as bogus dependency X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mail.kapsi.fi) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 16:12:58 -0000 I seem to have fixed this problem by remove graphics/jpeg from the Local repository. However, I really think this is a bug. Arto Pekkanen kirjoitti 13.10.2015 00:09: > Here follows the console output: > """ > # pkg install wifimgr > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > Updating Local repository catalogue... > Local repository is up-to-date. > All repositories are up-to-date. > The following 2 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > wifimgr: 1.11_1 [FreeBSD] > jpeg: 8_6 [FreeBSD] > > The process will require 2 MiB more space. > 94 KiB to be downloaded. > > Proceed with this action? [y/N]: y > Fetching wifimgr-1.11_1.txz: 100% 94 KiB 96.7kB/s 00:01 > Checking integrity... done (2 conflicting) > Checking integrity... done (0 conflicting) > Conflicts with the existing packages have been found. > One more solver iteration is needed to resolve them. > The following 1 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > wifimgr: 1.11_1 [FreeBSD] > > The process will require 405 KiB more space. > > Proceed with this action? [y/N]: y > [1/1] Installing wifimgr-1.11_1... > [1/1] Extracting wifimgr-1.11_1: 100% > > [root@leno ~]# pkg info jpeg > pkg: No package(s) matching jpeg > > [root@leno ~]# pkg rquery "%n-%v [%R]" jpeg > jpeg-8_6 [FreeBSD] > jpeg-8_6 [Local] > > [root@leno ~]# pkg rquery "%n-%v [%R] %rn" jpeg > [root@leno ~]# > """ > > Why does pkg try to install jpeg8_6 even if no package run-depends on > it? > > It does not prevent packages from installing, but it does waste time > with the conflict resolution. > > What should I do to resolve this issue? > > PS. The "Local" repository is my overlay repository where I've built > some packages with specific options. It is configured with priority > 100. -- Arto Pekkanen From owner-freebsd-pkg@freebsd.org Tue Oct 13 22:39:21 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93230A1397F for ; Tue, 13 Oct 2015 22:39:21 +0000 (UTC) (envelope-from ben@electricembers.coop) Received: from npomail1.electricembers.net (mail.electricembers.net [208.90.215.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.electricembers.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82CEAECD for ; Tue, 13 Oct 2015 22:39:20 +0000 (UTC) (envelope-from ben@electricembers.coop) Received: from private by npomail1.electricembers.net; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=electricembers.coop; s=internal; t=1444775478; bh=gTgN8N5y+2h1JCljaEFF09xUYzHBA/1YiR8S/bhEQCM=; l=1273; h=To:From:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=Cyg0WNgQZNMs40Pud0yHpzL9OkFmyK/zR5l2+9DX/0zh5DUjMFTmrT1ekcOWaLJ2C OGdBdvzbyECKidmahQGemqV+roubFWdbcCCtbu8Q+Ij+BocFxLOIabCjus370yqKa2 Xo9fxd5HeyHrUM6UfzWWRTjT/kcSRIWcKyGXzOdo= To: freebsd-pkg@freebsd.org From: Benjamin Connelly Subject: locked packages got upgraded anyway Message-ID: <561D8634.40103@electricembers.coop> Date: Tue, 13 Oct 2015 15:31:16 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 22:39:21 -0000 We have a few ports we compile with different compile time options than the FreeBSD binary repo, so we keep them locked. Last night when doing some patching, we saw those locked packages get updated anyhow. For example, pkg said all of these things on one system: Installed packages to be UPGRADED: pkg: 1.5.6 -> 1.6.1 dovecot2-2.2.18 is locked and may not be modified Installed packages LOCKED: Package dovecot2-2.2.18 is locked and may not be upgraded to version 2.2.19 (dovecot was not listed in the "Installed packages to be UPGRADED:" section, but then it was fetched) Fetching dovecot2-2.2.19.txz: 100% 3 MiB 2.9MB/s 00:01 Installed packages LOCKED: Package dovecot2-2.2.18 is locked and may not be upgraded to version 2.2.19 (it still did not after fetching appear on the list of packages to be upgraded, but) [17/71] Upgrading dovecot2 from 2.2.18 to 2.2.19... [17/71] Extracting dovecot2-2.2.19: 100% dovecot-pigeonhole was always on the list of packages to be upgraded, and it depends on dovecot2. Is this a bug, or did we learn a bad habit that's no longer workable, to lock the ports we build with different compile time options to keep 'pkg upgrade' from touching them. Benjamin From owner-freebsd-pkg@freebsd.org Tue Oct 13 22:42:59 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83088A13AC7 for ; Tue, 13 Oct 2015 22:42:59 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1A5D1213 for ; Tue, 13 Oct 2015 22:42:58 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 39547 invoked by uid 89); 13 Oct 2015 22:42:18 -0000 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 13 Oct 2015 22:42:18 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\)) Subject: Re: locked packages got upgraded anyway From: Rainer Duffner In-Reply-To: <561D8634.40103@electricembers.coop> Date: Wed, 14 Oct 2015 00:42:17 +0200 Cc: freebsd-pkg@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <561D8634.40103@electricembers.coop> To: Benjamin Connelly X-Mailer: Apple Mail (2.3094) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 22:42:59 -0000 > Am 14.10.2015 um 00:31 schrieb Benjamin Connelly = : >=20 > We have a few ports we compile with different compile time options = than the FreeBSD binary repo, so we keep them locked. Last night when = doing some patching, we saw those locked packages get updated anyhow. = For example, pkg said all of these things on one system: >=20 IMO, you either compile all of the packages you use yourself - or none. Until FreeBSD gets a sort of =E2=80=9Estable=E2=80=9C ports-tree that = lives for longer than three months, running your own repo is almost a = must for anything even semi mission-critical. From owner-freebsd-pkg@freebsd.org Wed Oct 14 15:00:07 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE217A1302B for ; Wed, 14 Oct 2015 15:00:07 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 9269514BE for ; Wed, 14 Oct 2015 15:00:07 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id ECB07204F7 for ; Wed, 14 Oct 2015 10:59:59 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Wed, 14 Oct 2015 10:59:59 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=J4tRgfI7KSkaG9j QboiKVuU1y0Y=; b=mkp9GYm32azr22KyT/sZvFGuqWyV4qeoZvbFv6CfmF98Iof mt4M9Ms40wUcQKCFRTIx3sxdygWLc13zilDOOZQ7I0e/nqkicdXYeJvZQccznMxL /UZIYgZ42GnG8cBk7+ZXWZRJJ16uX1WmG6u2rYMG2LmCgezlo5OB/DgpzTWU= Received: by web3.nyi.internal (Postfix, from userid 99) id C64AC103BBB; Wed, 14 Oct 2015 10:59:59 -0400 (EDT) Message-Id: <1444834799.3166860.410090913.6644022C@webmail.messagingengine.com> X-Sasl-Enc: Fe75n/QNOWH533213FN/yvO908UqTJHnTGRbK8Fj0fUQ 1444834799 From: Mark Felder To: freebsd-pkg@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-25d3ec43 In-Reply-To: References: <561D8634.40103@electricembers.coop> Subject: Re: locked packages got upgraded anyway Date: Wed, 14 Oct 2015 09:59:59 -0500 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 15:00:07 -0000 On Tue, Oct 13, 2015, at 17:42, Rainer Duffner wrote: >=20 > > Am 14.10.2015 um 00:31 schrieb Benjamin Connelly : > >=20 > > We have a few ports we compile with different compile time options than= the FreeBSD binary repo, so we keep them locked. Last night when doing som= e patching, we saw those locked packages get updated anyhow. For example, p= kg said all of these things on one system: > >=20 >=20 >=20 > IMO, you either compile all of the packages you use yourself - or none. >=20 > Until FreeBSD gets a sort of =E2=80=9Estable=E2=80=9C ports-tree that liv= es for longer > than three months, running your own repo is almost a must for anything > even semi mission-critical. >=20 He has a valid use case and I don't know why it was upgraded. Sounds like a bug. Perhaps because it was a dependency? Hmm... A planned* feature is for a user to be permitted to have packages with custom build options and "pkg upgrade" will handle fetching the required parts of the ports tree and building the updated package so you don't have to play this "lock your package, manually upgrade it later" game. Not everyone should be forced to run poudriere just so they can change one option on one package... * Planned as in "bapt or someone said we should do this when we have time" --=20 Mark Felder ports-secteam member feld@FreeBSD.org From owner-freebsd-pkg@freebsd.org Wed Oct 14 18:24:02 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B772CA1349A for ; Wed, 14 Oct 2015 18:24:02 +0000 (UTC) (envelope-from vmunix.old@gmail.com) Received: from mail-yk0-x243.google.com (mail-yk0-x243.google.com [IPv6:2607:f8b0:4002:c07::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 80E2B1783 for ; Wed, 14 Oct 2015 18:24:02 +0000 (UTC) (envelope-from vmunix.old@gmail.com) Received: by ykcg132 with SMTP id g132so4799852ykc.2 for ; Wed, 14 Oct 2015 11:24:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=8Brum9COjn5hIxuuj7e7JJ0M/eAHd/RnuX+MThSDyjw=; b=AyeKAOLfJDHfPSRYSann9EDnBuyb1r0URLj1L1lR5Ig40u/3PTizV9B6gi0USEiqzX 1jh5Q2t6rEPkbqKS3tKn0Nj5U6GvBvpM82ijGZNW85wZXeIGbT7C8SrJT64QXxvToETP 6Ft6Hs/W5iPbAx9vnowi6xhAxYd6hWpoHQylBAedkEZy8vXC2pZPoC+egyIZvG52Kb1J 3Bz7S9rOQBD86gTV5BJNo0uHwgSnzCfknuUSXrgAHVLOjldPeryUP++RltRVk/mrJoTC oChlTcjDaHBOIYgjfdgjtxzLnoLC7WwfCuq/X26DBZiVez8WXGrN6VEt6OCH+BO/bgJp 5Plw== MIME-Version: 1.0 X-Received: by 10.13.232.146 with SMTP id r140mr2555755ywe.284.1444847041373; Wed, 14 Oct 2015 11:24:01 -0700 (PDT) Received: by 10.37.82.133 with HTTP; Wed, 14 Oct 2015 11:24:01 -0700 (PDT) Date: Wed, 14 Oct 2015 20:24:01 +0200 Message-ID: Subject: Re: locked packages got upgraded anyway From: To: freebsd-pkg@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 18:24:02 -0000 * Mark Felder wrote: > > > On Tue, Oct 13, 2015, at 17:42, Rainer Duffner wrote: >> >> > Am 14.10.2015 um 00:31 schrieb Benjamin Connelly : >> > >> > We have a few ports we compile with different compile time options tha= n the FreeBSD binary repo, so we keep them locked. Last night when doing so= me patching, we saw those locked packages get updated anyhow. For example, = pkg said all of these things on one system: >> > >> >> >> IMO, you either compile all of the packages you use yourself - or none. >> >> Until FreeBSD gets a sort of =E2=80=9Estable=E2=80=9C ports-tree that li= ves for longer >> than three months, running your own repo is almost a must for anything >> even semi mission-critical. >> > > He has a valid use case and I don't know why it was upgraded. Sounds > like a bug. Perhaps because it was a dependency? Hmm... > > A planned* feature is for a user to be permitted to have packages with > custom build options and "pkg upgrade" will handle fetching the required > parts of the ports tree and building the updated package so you don't > have to play this "lock your package, manually upgrade it later" game. > Not everyone should be forced to run poudriere just so they can change > one option on one package... > > * Planned as in "bapt or someone said we should do this when we have > time" Are there any plans to introduce sub-packages or "flavors"? Because that would solve the issue of having to fiddle with Poudriere in order to build packages with more options enabled once and for all for probably 99% of all users. From owner-freebsd-pkg@freebsd.org Wed Oct 14 18:44:54 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFAD4A13AD9 for ; Wed, 14 Oct 2015 18:44:53 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8687AB8B for ; Wed, 14 Oct 2015 18:44:53 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by wicgb1 with SMTP id gb1so141850853wic.1 for ; Wed, 14 Oct 2015 11:44:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=80o9AT7ujrApIOvxqalKT+gSrPLIG8bUY/0syGYw4B0=; b=jJSHhJ185Illoi9Xz1bm/izqiJfuJ+cZHmKVZETa33pOJkUIYEvKAj4AQjz9Nf+sNe p5rO17NB+Z6RGR1W5Zbp4KSwHhlQZPCEjTBxYs/l2o4jG/a3CFkygrTdnxmI1Vm2TPJc 4fO7bw2bm0xiTI55Yij2U54fXD/a8MM0OisBsbowX+g3f83tp5Zii7Z3UB4EiS2AYgKf cFFbriUzg4NIJect6x5uo1tKZuZzowmfjnxI4nPcqgWpDqhGKEabNIRmRmXS/n4JBgmg HBDmXMe7/1O3OWgXTPckatRL3iHsMJ23zJtIilbaRekzCWisoNtRERKtKaPweQf22QGc 6Ruw== X-Received: by 10.180.85.229 with SMTP id k5mr30622637wiz.76.1444848292106; Wed, 14 Oct 2015 11:44:52 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id he3sm11636779wjc.48.2015.10.14.11.44.51 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Oct 2015 11:44:51 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 14 Oct 2015 20:44:49 +0200 From: Baptiste Daroussin To: vmunix.old@gmail.com Cc: freebsd-pkg@freebsd.org Subject: Re: locked packages got upgraded anyway Message-ID: <20151014184449.GM55137@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JvUS8mwutKMHKosv" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 18:44:54 -0000 --JvUS8mwutKMHKosv Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 14, 2015 at 08:24:01PM +0200, vmunix.old@gmail.com wrote: > * Mark Felder wrote: > > > > > > On Tue, Oct 13, 2015, at 17:42, Rainer Duffner wrote: > >> > >> > Am 14.10.2015 um 00:31 schrieb Benjamin Connelly : > >> > > >> > We have a few ports we compile with different compile time options t= han the FreeBSD binary repo, so we keep them locked. Last night when doing = some patching, we saw those locked packages get updated anyhow. For example= , pkg said all of these things on one system: > >> > > >> > >> > >> IMO, you either compile all of the packages you use yourself - or none. > >> > >> Until FreeBSD gets a sort of =E2=80=9Estable=E2=80=9C ports-tree that = lives for longer > >> than three months, running your own repo is almost a must for anything > >> even semi mission-critical. > >> > > > > He has a valid use case and I don't know why it was upgraded. Sounds > > like a bug. Perhaps because it was a dependency? Hmm... > > > > A planned* feature is for a user to be permitted to have packages with > > custom build options and "pkg upgrade" will handle fetching the required > > parts of the ports tree and building the updated package so you don't > > have to play this "lock your package, manually upgrade it later" game. > > Not everyone should be forced to run poudriere just so they can change > > one option on one package... > > > > * Planned as in "bapt or someone said we should do this when we have > > time" >=20 > Are there any plans to introduce sub-packages or "flavors"? Because that > would solve the issue of having to fiddle with Poudriere in order to build > packages with more options enabled once and for all for probably 99% of > all users. Yes there are plan for all of this but it takes a lot of time and we have v= ery little manpower. Best regards, Bapt --JvUS8mwutKMHKosv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlYeoqAACgkQ8kTtMUmk6Ewh+QCeIYe+B/c6oC6GQfveZE8I+16v jgoAn3wiMg7CcUeuA1ajIax8zlVJlw7K =j6xd -----END PGP SIGNATURE----- --JvUS8mwutKMHKosv-- From owner-freebsd-pkg@freebsd.org Wed Oct 14 19:06:19 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 721F0A154DC for ; Wed, 14 Oct 2015 19:06:19 +0000 (UTC) (envelope-from markham_breitbach@ssimicro.com) Received: from smail.ssimicro.com (smail.ssimicro.com [64.247.129.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smail.ssimicro.com", Issuer "test CA 1" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C3971F04 for ; Wed, 14 Oct 2015 19:06:18 +0000 (UTC) (envelope-from markham_breitbach@ssimicro.com) Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by smail.ssimicro.com (8.15.1/8.14.9) with ESMTPSA id t9EIsNEI045227 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Wed, 14 Oct 2015 12:54:23 -0600 (MDT) (envelope-from markham_breitbach@ssimicro.com) Subject: Re: locked packages got upgraded anyway To: freebsd-pkg@freebsd.org References: From: markham breitbach X-Enigmail-Draft-Status: N1110 Message-ID: <561EA57C.9010705@ssimicro.com> Date: Wed, 14 Oct 2015 12:57:00 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 19:06:19 -0000 Something like a local override list would be great. I am currently in a situation where I am trying to build a sendmail package from ports with the LDAP option enable, but it has a dependency of saslauthd, but that also needs the LDAP option and there is no (simple and obvious) way for me to tell the sendmail package to use my custom saslauthd+LDAP as a dependency. Admittedly I have not spent a great deal of time looking into this yet, as it just came up, nor have I had the time to setup a poudriere repo with all my customizations. -M On 2015-10-14 12:24 PM, vmunix.old@gmail.com wrote: > * Mark Felder wrote: >> >> On Tue, Oct 13, 2015, at 17:42, Rainer Duffner wrote: >>>> Am 14.10.2015 um 00:31 schrieb Benjamin Connelly : >>>> >>>> We have a few ports we compile with different compile time options t= han the FreeBSD binary repo, so we keep them locked. Last night when doin= g some patching, we saw those locked packages get updated anyhow. For exa= mple, pkg said all of these things on one system: >>>> >>> >>> IMO, you either compile all of the packages you use yourself - or non= e. >>> >>> Until FreeBSD gets a sort of =E2=80=9Estable=E2=80=9C ports-tree that= lives for longer >>> than three months, running your own repo is almost a must for anythin= g >>> even semi mission-critical. >>> >> He has a valid use case and I don't know why it was upgraded. Sounds >> like a bug. Perhaps because it was a dependency? Hmm... >> >> A planned* feature is for a user to be permitted to have packages with= >> custom build options and "pkg upgrade" will handle fetching the requir= ed >> parts of the ports tree and building the updated package so you don't >> have to play this "lock your package, manually upgrade it later" game.= >> Not everyone should be forced to run poudriere just so they can change= >> one option on one package... >> >> * Planned as in "bapt or someone said we should do this when we have >> time" > Are there any plans to introduce sub-packages or "flavors"? Because tha= t > would solve the issue of having to fiddle with Poudriere in order to bu= ild > packages with more options enabled once and for all for probably 99% of= > all users. > _______________________________________________ > freebsd-pkg@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe@freebsd.org" > From owner-freebsd-pkg@freebsd.org Wed Oct 14 19:14:26 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3343A156D0 for ; Wed, 14 Oct 2015 19:14:26 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10E2F63C for ; Wed, 14 Oct 2015 19:14:25 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 70630 invoked by uid 89); 14 Oct 2015 19:13:51 -0000 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 14 Oct 2015 19:13:51 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\)) Subject: Re: locked packages got upgraded anyway From: Rainer Duffner In-Reply-To: <1444834799.3166860.410090913.6644022C@webmail.messagingengine.com> Date: Wed, 14 Oct 2015 21:13:50 +0200 Cc: freebsd-pkg@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <561D8634.40103@electricembers.coop> <1444834799.3166860.410090913.6644022C@webmail.messagingengine.com> To: Mark Felder X-Mailer: Apple Mail (2.3094) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 19:14:26 -0000 > Am 14.10.2015 um 16:59 schrieb Mark Felder : >=20 >=20 >=20 > He has a valid use case and I don't know why it was upgraded. Sounds > like a bug. Perhaps because it was a dependency? Hmm... >=20 > A planned* feature is for a user to be permitted to have packages with > custom build options and "pkg upgrade" will handle fetching the = required > parts of the ports tree and building the updated package so you don't > have to play this "lock your package, manually upgrade it later" game. > Not everyone should be forced to run poudriere just so they can change > one option on one package... Well, I feel the reality is different. =E2=80=9EShould have=E2=80=9C or =E2=80=9EShould not have=E2=80=9C = doesn=E2=80=99t buy you anything in the end ;-) It=E2=80=99s probably not a problem locking a package with no = dependencies. But do you have to lock the dependencies, too? I=E2=80=99m too afraid of the outcome, so I don=E2=80=99t even try. And if you=E2=80=99re running poudriere for a couple of packages = already, you can just let it build the rest, too. IMO. The only thing I found useful was locking pkg itself. That way, I could downgrade everything to an earlier cut of the = ports-tree (except for pkg, which would probably have had problems = reading the newer version of the pkg-db created by a more recent version = of pkg). I realize not everyone wants to run their own repo - but in practice, = this is currently the best way to do it if you=E2=80=99re not 100% happy = with what you get from the official repo, with the least possible ways = to totally F-U. I, too, would be glad if there were =E2=80=9Eflavors=E2=80=9C, so I = could stop running my own build-server and just mirror the official = repo, like we do for Ubuntu and CentOS. But in the end of the day, I live in reality, not in la-la-land. I appreciate all the work done by the committers on the ports-tree and = packages - I save an absurd amount of time just by walking in these = foot-steps. From owner-freebsd-pkg@freebsd.org Wed Oct 14 21:56:20 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CB83A1226C for ; Wed, 14 Oct 2015 21:56:20 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D5CBBCB; Wed, 14 Oct 2015 21:56:19 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from karviainen.kapsi.fi ([217.30.184.182] helo=roundcube.kapsi.fi) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ZmU1u-0006RE-Se; Thu, 15 Oct 2015 00:56:16 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 15 Oct 2015 00:56:14 +0300 From: Arto Pekkanen To: Baptiste Daroussin Cc: vmunix.old@gmail.com, freebsd-pkg@freebsd.org In-Reply-To: <20151014184449.GM55137@ivaldir.etoilebsd.net> References: <20151014184449.GM55137@ivaldir.etoilebsd.net> Message-ID: <6448fb53ff5e03747dfee109a67770f8@kapsi.fi> X-Sender: isoa@kapsi.fi User-Agent: RoundCube Webmail/0.9.4 X-SA-Exim-Connect-IP: 217.30.184.182 X-SA-Exim-Mail-From: isoa@kapsi.fi X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 Subject: Re: locked packages got upgraded anyway X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mail.kapsi.fi) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 21:56:20 -0000 In my opinion the best solution would be to write a separate program that would enable one to create a local repository so that only those ports that have custom options will be built, other packages would be included verbatim from base repository. However, such a program would require some way of knowing the revision number or date of revision of the ports tree used to create the base repository. One could try parsing the "start time" tags from http://pkg-status.freebsd.org, that would kind of work (not perfectly though). Parsing start of build timestamp is kinda ugly, and there is no guarantee that the start time of a repository build is exactly the same as the date of revision the ports tree from which the repository was created. Other solution would be to create a plugin for pkg. It would detect if a user has set custom port options for the package currently being installed, and would instead call "make package" on the port and install the built package. However, this might be tricky, since pkg must resolve dependencies before any package will be installed. Thus hooking the installation event for a node would not work. One would have to be able to hook the actual dependency caching event for a node, decide whether to install from repo or install from ports, and dispatch the dependencies of the node back to the resolver. I have some ideas on how to create a repository mixer, as described as the first solution. I was going to create such a software for my own use, but I never finished because of irl stuff. Baptiste Daroussin kirjoitti 14.10.2015 21:44: > On Wed, Oct 14, 2015 at 08:24:01PM +0200, vmunix.old@gmail.com wrote: >> * Mark Felder wrote: >> > >> > >> > On Tue, Oct 13, 2015, at 17:42, Rainer Duffner wrote: >> >> >> >> > Am 14.10.2015 um 00:31 schrieb Benjamin Connelly : >> >> > >> >> > We have a few ports we compile with different compile time options than the FreeBSD binary repo, so we keep them locked. Last night when doing some patching, we saw those locked packages get updated anyhow. For example, pkg said all of these things on one system: >> >> > >> >> >> >> >> >> IMO, you either compile all of the packages you use yourself - or none. >> >> >> >> Until FreeBSD gets a sort of „stable“ ports-tree that lives for longer >> >> than three months, running your own repo is almost a must for anything >> >> even semi mission-critical. >> >> >> > >> > He has a valid use case and I don't know why it was upgraded. Sounds >> > like a bug. Perhaps because it was a dependency? Hmm... >> > >> > A planned* feature is for a user to be permitted to have packages with >> > custom build options and "pkg upgrade" will handle fetching the required >> > parts of the ports tree and building the updated package so you don't >> > have to play this "lock your package, manually upgrade it later" game. >> > Not everyone should be forced to run poudriere just so they can change >> > one option on one package... >> > >> > * Planned as in "bapt or someone said we should do this when we have >> > time" >> >> Are there any plans to introduce sub-packages or "flavors"? Because >> that >> would solve the issue of having to fiddle with Poudriere in order to >> build >> packages with more options enabled once and for all for probably 99% >> of >> all users. > > Yes there are plan for all of this but it takes a lot of time and we > have very > little manpower. > > Best regards, > Bapt -- Arto Pekkanen