From owner-freebsd-pkg@freebsd.org Sun Jun 4 21:01:10 2017 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 65B9EBEEF1F for ; Sun, 4 Jun 2017 21:01:10 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4E23B847FC for ; Sun, 4 Jun 2017 21:01:10 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4CBDFBEEF1D; Sun, 4 Jun 2017 21:01:10 +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 4BEACBEEF1C for ; Sun, 4 Jun 2017 21:01:10 +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 1E6FD847F5 for ; Sun, 4 Jun 2017 21:01:10 +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 v54L01PE013858 for ; Sun, 4 Jun 2017 21:01:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201706042101.v54L01PE013858@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: pkg@FreeBSD.org Subject: Problem reports for pkg@FreeBSD.org that need special attention Date: Sun, 04 Jun 2017 21:01:09 +0000 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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, 04 Jun 2017 21:01:10 -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 ------------+-----------+--------------------------------------------------- In Progress | 212022 | ports-mgmt/pkg: Segfaults when installing sensu p Open | 211141 | ports-mgmt/pkg: pkg+pw: Doesn't run pwd_mkdb, may New | 193995 | [PATCH] ports-mgmt/pkg: floating point exception 3 problems total for which you should take action. From owner-freebsd-pkg@freebsd.org Tue Jun 6 14:37:41 2017 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 58894BEE0A5 for ; Tue, 6 Jun 2017 14:37:41 +0000 (UTC) (envelope-from rosettas@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 1F8FF6EBF2 for ; Tue, 6 Jun 2017 14:37:41 +0000 (UTC) (envelope-from rosettas@gmail.com) Received: by mail-oi0-x234.google.com with SMTP id h4so179170544oib.3 for ; Tue, 06 Jun 2017 07:37:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FOGCazV0p1ZJdEFpd76KAkwWvlHTsoQ2315lvzpxpVw=; b=H5e4Uc7kooudi0+HSPhOtRE7cqYL/fagKz18sf5ulA83AjGbcctu6NG3pf1w7ObY+3 mIOZ3SRWnlA27AVPA6GB1986GgUpF7OW1RF7o4TJaXKcvo9qWvxZddato/kjb3NXOAr9 KuXJhI36UbTEtRJ7/K3Aw0rzNeLmJ/HhlMFEkBuuuJ1sq4tokLJ5IGujsXFiXuI9YpRb Rcio++ibWgG5qZvROgVElp0mI6a5jeAormhnKsfr/BPM+RRNfitQB2Jy3lAX6h7VIVW9 YL9QfUAafCYTJMyEE/24eNBG57LPghsqauLiFBYibT44SSR0+/gKoWdupPHPhIoUo4I4 H9jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FOGCazV0p1ZJdEFpd76KAkwWvlHTsoQ2315lvzpxpVw=; b=AfZJq13oYe4Y5qyrnklvXvPtMK/WhkwOgXxHENydC6hffYtDanX/VTxnQJJrfQJIdC QDtvcjRPYm4oN8qiglJcewwwfWJd+ODhUSKIz4Z5W6/7nG6ypBUOiTY91TCTZsVUxbe/ QlwLnuCr6oQyGY7RabyPRU7xalH+iaFvqEIUb4FHeY4+1JDeXQyRh5+LhudL2BzY3l3v ofvi/IH8SYMNLJLfHKzegF7XGFujEkuyGwqHsCj7+oWB8tVidyywG9g1mfkT4ogZS/FS UTffC+b7vlWIIFK1H4kSt9qLbNe0ZGsR1uWDdgr/e+ojRhrMoRfqvIQYIjVYcaXInlW0 XP1g== X-Gm-Message-State: AODbwcBMxRUrCiE+DV40dU347/KotUefIq6slybU9yOT1cr+1CKi+6mB z7iu6TGDSo2L02NRqFLvWjft1M9pG2U97e8= X-Received: by 10.202.231.83 with SMTP id e80mr14262197oih.132.1496759860226; Tue, 06 Jun 2017 07:37:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.24.110 with HTTP; Tue, 6 Jun 2017 07:37:39 -0700 (PDT) From: Cos Chan Date: Tue, 6 Jun 2017 16:37:39 +0200 Message-ID: Subject: wget 1.19 missed IRI supporting To: freebsd-pkg@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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, 06 Jun 2017 14:37:41 -0000 I got mistake while running this command: wget --no-verbose --remote-encoding=UTF-8 --local-encoding=UTF-8 --mirror --directory-prefix=/foo/ --no-parent --no-host-directories --cut-dirs=2 --force-directories --accept=*.pdf --restrict-file-names=nocontrol http://bar/Documents/ the mistake is : This version does not have support for IRIs the wget version is: $ wget --version GNU Wget 1.19 built on freebsd11.0. -cares +digest -gpgme +https +ipv6 -iri +large-file -metalink +nls +ntlm +opie -psl +ssl/openssl Wgetrc: /usr/local/etc/wgetrc (system) Locale: /usr/local/share/locale Compile: clang -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/usr/local/etc/wgetrc" -DLOCALEDIR="/usr/local/share/locale" -I. -I../lib -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -D_THREAD_SAFE -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing Link: clang -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -L/usr/local/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -fstack-protector /usr/local/lib/libssl.so /usr/local/lib/libcrypto.so -Wl,-rpath -Wl,/usr/local/lib -lz ftp-opie.o openssl.o http-ntlm.o ../lib/libgnu.a -L/usr/local/lib -lintl -Wl,-rpath=/usr/local/lib This issue was not happened in previous versions. Could anyone add back IRI supporting to V1.19 binary package? -- with kind regards From owner-freebsd-pkg@freebsd.org Wed Jun 7 13:40:28 2017 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 C6FEBC31F80 for ; Wed, 7 Jun 2017 13:40:28 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (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 8EDC574AED for ; Wed, 7 Jun 2017 13:40:28 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: by mail-ot0-x22e.google.com with SMTP id a2so7074274oth.2 for ; Wed, 07 Jun 2017 06:40:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VLoTvy/Y62lfFYhq/WTVvrlEvhwNfPq7K2fIUbMvVHA=; b=QYxBzDL8sSz4TKCHeOrdoHl+Mk5iJgRyOzGg3MbR+i8S8/FCm0K317aZKBFUBpVI+T 3lnxg+5qN03MF4EOpoPvKPp1guFJ5d4Kcp3SzQdX8sUHAAJ2//BiQBki01eJhhKqDi/4 Hy9UVwCyU8c5nXZvfiX+lmDSOsANpr0IPf1Wbs3MioT7fcd1f7DQz1pJXoxxeimFEdLg XoqjYb4yCPgZRZ93UAC0cZvvxArpcOV+kJuQNJpgrkEBpHNuBcSeJbZAp8YHCqi5NrKT QmCLaRnDybLoMbbxlK4AR92rxyrU8SI9bqD3k9x51YANdkvbJzOrDNPVtPrentIgaUtf VOXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VLoTvy/Y62lfFYhq/WTVvrlEvhwNfPq7K2fIUbMvVHA=; b=OAJNA4F81fBGr2nJK0tcy1c3mgDPnjAH2jXMjNOvmggVne4GwdwD8wY0EeNAWFBFdF F2wAWhgxnlxojoYGgFbIWb3Iku/BWNt4FOdWdOI5FB/giAVZFK+O/uoGA9ULQsmGyUl1 IhBYfXMGkFanCUuPWXt4X53cs6/KvuYdipdEJ/4OINA1WS/bEhb66ouuQSfakZcQ03SW xev5f4W2knYnG4Pb0jPlnhm886m/ukOdYDFKo3XDpyQkQ9b9IzIoMsrpqduAe7TRZ2/a KRXpy4K/iEXp9jfaQyAcc4KNg6GZK8XlwZzbe9vOf839JLo0A/pahmG3BCIzrrwNiHep MPLQ== X-Gm-Message-State: AKS2vOxeyUglFzMBXGCz09zUp3AdoqMRBOedQJsuFS/QW0Md5/To1i1m 88nl6o9Jcp54Ub0YjkEKjafWiNZ/sMD8NaY= X-Received: by 10.157.84.22 with SMTP id j22mr18376646oth.252.1496842827474; Wed, 07 Jun 2017 06:40:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.47.103 with HTTP; Wed, 7 Jun 2017 06:40:07 -0700 (PDT) From: Luca Pizzamiglio Date: Wed, 7 Jun 2017 15:40:07 +0200 Message-ID: Subject: pkg rollback To: freebsd-pkg@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Jun 2017 13:40:28 -0000 Hi all, I'm trying to figure out how an automatic process to upgrade packages on production machines can look like. A kind of: # pkg upgrade # restart services # if everything not OK # rollback # restart services I'm considering a package repository that is not guaranteeing 100% stability, like `latest`. Even intercepting events needing manual intervention (i.e. reported by UPDATING), a blind pkg upgrade can break the web application running on top. So, I was thinking if it's possible to perform some kind of rollback. to proof if it's possible, I wrote a shell scripts with two features (it helped me a lot to understand how pkg works): # backup ## backup the repo sqlite database ## run `pkg update` and determine all actions would be performed by `pkg upgrade` (a kind of `pkg upgrade` simulation) ## backup all packages from the cache that would be replaced by `pkg upgrade` ## download all new packages to determine potentially conflicts ## backup all packages from the cache that would be replaced by `pkg upgrade` (after determined conflicts) ## restore the repo sqlite database # rollback ## restore the repo sqlite database ## install all previously backup'ed packages Another approach, less complex, but I guess even valid, could be: # backup (or snapshot) ## backup of the repo sqlite database ## take a snapshot of all installed packages # rollback (a previously stored snapshot) ## restore the repo sqlite database ## reinstall all previously backup'ed packages Adding two features [snapshot and rollback] to pkg(8), the automated upgrade process would become: # pkg snapshot # pkg upgrade # restart services # if everything not OK # rollback # restart services What do you think? What am I missing? Ideas, suggestions and feedback are welcome, so, please, feel free to reply. Best regards, Luca PS: I'd use `pkg snapshot`, because `pkg backup` already exist and it has another meaning. PS2: In some case, `zfs snapshot` could work as well, but it's not always possible PS3: if feebacks are positive, I'd like to implement those features From owner-freebsd-pkg@freebsd.org Thu Jun 8 00:53:33 2017 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 DE03FB95416 for ; Thu, 8 Jun 2017 00:53:33 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 97EF96684C for ; Thu, 8 Jun 2017 00:53:33 +0000 (UTC) (envelope-from isoa@kapsi.fi) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=g4OAzPakvgjSDpFl33MJzOzrrtUf+mgw8BQyLUsKdlk=; b=J9fulX/tirvY9HXRFLN25fw3JeEJnIE1g51SD+IOVGymgGd+KzVlsOjymTdytcI8doyw6b6F/UHMI4JL9uh8kzbbps1ZqYI2vlQ1wbNfEkxYlzt03dIcosYH3kfqrTm3CgR2g6JP3S2iaPZfi0k/Kg/fO9ET6ZEW0Aea0nt+KprhSunlAyb8FUDlkf/tuBeW7qW+yElyOSIFq+nanuXnzLAjjSGa7jcnpBA/hM4+Zs21SbvhqEV6gY2RmjViWRWBMDyTTw0GzkSb1a1ABjg/E/x7u+0yYstaAs48HM2GE2TbjJeVlEF5JbvcNFGfvSQy1qo4QX3HWZJnSXKgaKw9uA==; Received: from dsl-jklbng11-54fa58-115.dhcp.inet.fi ([84.250.88.115] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1dIlhZ-0002q2-NG for freebsd-pkg@freebsd.org; Thu, 08 Jun 2017 03:53:29 +0300 Subject: Re: pkg rollback To: freebsd-pkg@freebsd.org References: From: Arto Pekkanen Message-ID: Date: Thu, 8 Jun 2017 03:53:18 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DOu5U8Set5d3w8wiurfCTmmJ9i7J0vjtH" X-SA-Exim-Connect-IP: 84.250.88.115 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 08 Jun 2017 00:53:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DOu5U8Set5d3w8wiurfCTmmJ9i7J0vjtH Content-Type: multipart/mixed; boundary="gFgSloURdD92owwCbcDwrjK9q8uBsEeXW"; protected-headers="v1" From: Arto Pekkanen To: freebsd-pkg@freebsd.org Message-ID: Subject: Re: pkg rollback References: In-Reply-To: --gFgSloURdD92owwCbcDwrjK9q8uBsEeXW Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Why does not ZFS snapshot and rollback work for this scenario? On 7.6.2017 16:40, Luca Pizzamiglio wrote: > Hi all, >=20 > I'm trying to figure out how an automatic process to upgrade packages > on production machines can look like. >=20 > A kind of: > # pkg upgrade > # restart services > # if everything not OK > # rollback > # restart services >=20 > I'm considering a package repository that is not guaranteeing 100% > stability, like `latest`. > Even intercepting events needing manual intervention (i.e. reported by > UPDATING), a blind pkg upgrade can break the web application running > on top. > So, I was thinking if it's possible to perform some kind of rollback. >=20 > to proof if it's possible, I wrote a shell scripts with two features > (it helped me a lot to understand how pkg works): > # backup > ## backup the repo sqlite database > ## run `pkg update` and determine all actions would be performed by > `pkg upgrade` (a kind of `pkg upgrade` simulation) > ## backup all packages from the cache that would be replaced by `pkg up= grade` > ## download all new packages to determine potentially conflicts > ## backup all packages from the cache that would be replaced by `pkg > upgrade` (after determined conflicts) > ## restore the repo sqlite database > # rollback > ## restore the repo sqlite database > ## install all previously backup'ed packages >=20 > Another approach, less complex, but I guess even valid, could be: > # backup (or snapshot) > ## backup of the repo sqlite database > ## take a snapshot of all installed packages > # rollback (a previously stored snapshot) > ## restore the repo sqlite database > ## reinstall all previously backup'ed packages >=20 > Adding two features [snapshot and rollback] to pkg(8), the automated > upgrade process would become: > # pkg snapshot > # pkg upgrade > # restart services > # if everything not OK > # rollback > # restart services >=20 > What do you think? > What am I missing? > Ideas, suggestions and feedback are welcome, so, please, feel free to r= eply. >=20 > Best regards, > Luca >=20 > PS: I'd use `pkg snapshot`, because `pkg backup` already exist and it > has another meaning. > PS2: In some case, `zfs snapshot` could work as well, but it's not > always possible > PS3: if feebacks are positive, I'd like to implement those features > _______________________________________________ > 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" >=20 --=20 Arto Pekkanen --gFgSloURdD92owwCbcDwrjK9q8uBsEeXW-- --DOu5U8Set5d3w8wiurfCTmmJ9i7J0vjtH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlk4oAkACgkQTBivhqtJa26pUQD/WU63lDyYeSXLu/y0kgJ7duqO n9jqCsc7vYuLnWNdgAAA/0xQwqRXUUxbCE0f82Cqr1TsUIAZWs88GsxZlQ0Ez1vm =Fqx+ -----END PGP SIGNATURE----- --DOu5U8Set5d3w8wiurfCTmmJ9i7J0vjtH-- From owner-freebsd-pkg@freebsd.org Thu Jun 8 07:58:30 2017 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 AD5CFBF8CE2 for ; Thu, 8 Jun 2017 07:58:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9531078743 for ; Thu, 8 Jun 2017 07:58:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 91814BF8CE1; Thu, 8 Jun 2017 07:58:30 +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 90D34BF8CE0 for ; Thu, 8 Jun 2017 07:58:30 +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 7E74178742 for ; Thu, 8 Jun 2017 07:58:30 +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 v587wTMB035545 for ; Thu, 8 Jun 2017 07:58:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 217286] ports-mgmt/pkg: pkg-1.9.4_1 Assertion failed in pkg_conflicts_check_chain_conflict Date: Thu, 08 Jun 2017 07:58:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkg@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 08 Jun 2017 07:58:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217286 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 190 | |84 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-pkg@freebsd.org Thu Jun 8 08:00:26 2017 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 D8888BF8F9D for ; Thu, 8 Jun 2017 08:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C0C9878828 for ; Thu, 8 Jun 2017 08:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BD459BF8F9C; Thu, 8 Jun 2017 08:00:26 +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 BC98CBF8F9B for ; Thu, 8 Jun 2017 08: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 AA34678827 for ; Thu, 8 Jun 2017 08: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 v5880POY046256 for ; Thu, 8 Jun 2017 08:00:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 217286] ports-mgmt/pkg: pkg-1.9.4_1 Assertion failed in pkg_conflicts_check_chain_conflict Date: Thu, 08 Jun 2017 08:00:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkg@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 08 Jun 2017 08:00:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217286 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2190 | |84 | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-pkg@freebsd.org Thu Jun 8 09:42:50 2017 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 69C0EBFAC12 for ; Thu, 8 Jun 2017 09:42:50 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 2E9087B503 for ; Thu, 8 Jun 2017 09:42:50 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: by mail-oi0-x232.google.com with SMTP id s3so16255272oia.0 for ; Thu, 08 Jun 2017 02:42:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Dj9Cvjz81huzECczUxr1/UL5RhIw+4L7vaT8kK6ihZs=; b=WOfNc7o+tAvQFQ6Ppcjojvu+aMV2gycObThWM71C3K5j+L6wDUHRQvRl3tk61hFsUY xIUxxf6Wahm+9GMg+NKSSejZv48i7A3FqNr802CNv2Wmja6MsLlVSW3tTo1aIt3Jj5/a C9Ik2Ili2N+mjVxm8d97BJ83OYxC5sEeLIqkBiEVoF5YbykQdlovOuFtBd44hUkXr41u KYm82rHeJLDrmoR9bFeaxJaGxrJjKa7sY9qVR8VAtNZVlDkeuMN9geeT/a5K8MIxRrMQ PDhROBvL2x/UEZ0f4vq+IVM4o5IEzp/G2yLjfJE7yjEi7gh1acP+v/uRObbDuh2unyhf Nh2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Dj9Cvjz81huzECczUxr1/UL5RhIw+4L7vaT8kK6ihZs=; b=Bcm6fOY9EcS47mQveDsniOegoyCBu9/PyZRPp1r7Tr3Z0oJjd4drmn6hHFZR6zOi+g Hz9mMPVxyDbAGoy8j0MWNAm8Murs9PUUgJZE7rIL12TOzW/TyyPQZva1jDkKVd23xZy+ +7ClHzmdxopuodG/CkFTAIqUmkNZJ8g1Dkm9mupT/6npLSwPXOVypEmBBQfD0zZniiLv S+BC4Pko7sfvXAGbrj0HxwSMmVCRc+0XRbVKN8UIz1IE/cLGrJkujbb/r+h5v20qkxjo 1gmmd0dfmej0TXj/DPa8Wdbq6rIO3CV/ZWrTCVPyze3v09dGqH9WTkRbh11gTUOBn1+A viqQ== X-Gm-Message-State: AODbwcA9J/3tGXP3JXcYI4BAxq2jxuVe3YlT07lrEGFd0B4kc8wqlJ2a 996peynPkpdAu/+GW7z2M9Z5NyVSdZhT X-Received: by 10.202.168.85 with SMTP id r82mr5469527oie.91.1496914969535; Thu, 08 Jun 2017 02:42:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.47.103 with HTTP; Thu, 8 Jun 2017 02:42:29 -0700 (PDT) In-Reply-To: References: From: Luca Pizzamiglio Date: Thu, 8 Jun 2017 11:42:29 +0200 Message-ID: Subject: Re: pkg rollback To: Arto Pekkanen Cc: freebsd-pkg@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 08 Jun 2017 09:42:50 -0000 yes zfs snapshot/rollback could be usable, if /usr/local is on zfs. If /usr/local is on ufs, zfs snapshot is not an option :) Several older systems here were installed with root based on ufs and /usr/local is not on the zfs tank :( Reinstall all of them is, currently not an option. IMHO pkg snapshot/rollback would work on ufs and only for packages, but I see zfs as a valuable option, if applicable. Best regards, Luca On Thu, Jun 8, 2017 at 2:53 AM, Arto Pekkanen wrote: > Why does not ZFS snapshot and rollback work for this scenario? > > On 7.6.2017 16:40, Luca Pizzamiglio wrote: >> Hi all, >> >> I'm trying to figure out how an automatic process to upgrade packages >> on production machines can look like. >> >> A kind of: >> # pkg upgrade >> # restart services >> # if everything not OK >> # rollback >> # restart services >> >> I'm considering a package repository that is not guaranteeing 100% >> stability, like `latest`. >> Even intercepting events needing manual intervention (i.e. reported by >> UPDATING), a blind pkg upgrade can break the web application running >> on top. >> So, I was thinking if it's possible to perform some kind of rollback. >> >> to proof if it's possible, I wrote a shell scripts with two features >> (it helped me a lot to understand how pkg works): >> # backup >> ## backup the repo sqlite database >> ## run `pkg update` and determine all actions would be performed by >> `pkg upgrade` (a kind of `pkg upgrade` simulation) >> ## backup all packages from the cache that would be replaced by `pkg upgrade` >> ## download all new packages to determine potentially conflicts >> ## backup all packages from the cache that would be replaced by `pkg >> upgrade` (after determined conflicts) >> ## restore the repo sqlite database >> # rollback >> ## restore the repo sqlite database >> ## install all previously backup'ed packages >> >> Another approach, less complex, but I guess even valid, could be: >> # backup (or snapshot) >> ## backup of the repo sqlite database >> ## take a snapshot of all installed packages >> # rollback (a previously stored snapshot) >> ## restore the repo sqlite database >> ## reinstall all previously backup'ed packages >> >> Adding two features [snapshot and rollback] to pkg(8), the automated >> upgrade process would become: >> # pkg snapshot >> # pkg upgrade >> # restart services >> # if everything not OK >> # rollback >> # restart services >> >> What do you think? >> What am I missing? >> Ideas, suggestions and feedback are welcome, so, please, feel free to reply. >> >> Best regards, >> Luca >> >> PS: I'd use `pkg snapshot`, because `pkg backup` already exist and it >> has another meaning. >> PS2: In some case, `zfs snapshot` could work as well, but it's not >> always possible >> PS3: if feebacks are positive, I'd like to implement those features >> _______________________________________________ >> 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" >> > > -- > Arto Pekkanen >