From bugzilla-noreply at freebsd.org Thu Mar 5 22:47:20 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Thu, 05 Mar 2015 22:47:20 +0000 Subject: [Bug 197748] ports-mgmt/pkg: ignores error conditions at exit time In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197748 Baptiste Daroussin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Fri Mar 6 01:24:52 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Fri, 06 Mar 2015 01:24:52 +0000 Subject: [Bug 198337] pkg version reporting incorrect results for python3 sqlite3 module Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198337 Bug ID: 198337 Summary: pkg version reporting incorrect results for python3 sqlite3 module Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: freebsd-ports-bugs at FreeBSD.org Reporter: rsimmons0 at gmail.com CC: pkg at FreeBSD.org, portmgr at FreeBSD.org I have the most recent version of sqlite3 and python3, but the results from pkg version lists for databases/py34-sqlite3 are not correct: # pkg version py34-sqlite3-3.4.3_6 > I'm not sure whether this is a problem with the ports tree or with ports-mgmt/pkg -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla-noreply at freebsd.org Sat Mar 7 13:30:24 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Sat, 07 Mar 2015 13:30:24 +0000 Subject: [Bug 197345] ports-mgmt/pkg estimates 0 GiB additional disk space In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197345 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Component|bin |Individual Port(s) Product|Base System |Ports & Packages Version|10.1-RELEASE |Latest Assignee|freebsd-bugs at FreeBSD.org |pkg at FreeBSD.org Summary|pkg estimates 0 GiB |ports-mgmt/pkg estimates 0 |additional disk space |GiB additional disk space -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Sun Mar 8 13:50:46 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Sun, 08 Mar 2015 13:50:46 +0000 Subject: [Bug 197345] ports-mgmt/pkg estimates 0 GiB additional disk space In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197345 --- Comment #1 from Baptiste Daroussin --- Can you specify which version of pkg? -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Sun Mar 8 15:12:25 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Sun, 08 Mar 2015 15:12:25 +0000 Subject: [Bug 197345] ports-mgmt/pkg estimates 0 GiB additional disk space In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197345 --- Comment #2 from Matthew Seaman --- Fixed some time back in git: https://github.com/freebsd/pkg/commit/3bdbed6aa34b34e325c506fbbde44516c947633d -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Sun Mar 15 04:40:12 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Sun, 15 Mar 2015 04:40:12 +0000 Subject: [Bug 192539] pkg search: wxgtk30 & wxgtk29 aren't found In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192539 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Component|bin |Individual Port(s) Product|Base System |Ports & Packages Summary|Ports Query: wxgtk30 & |pkg search: wxgtk30 & |wxgtk29 aren't found |wxgtk29 aren't found Assignee|freebsd-bugs at FreeBSD.org |pkg at FreeBSD.org Version|10.0-STABLE |Latest -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Sun Mar 15 15:00:20 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Sun, 15 Mar 2015 15:00:19 +0000 Subject: [Bug 192539] pkg search: wxgtk30 & wxgtk29 aren't found In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192539 Matthew Seaman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthew at FreeBSD.org --- Comment #4 from Matthew Seaman --- This is because pkg(8) now searches based on package *names* by default, and the package name for these ports is quite different to the origin in the ports tree: lucid-nonsense:...etc/pkg/repos:# pkg search -g 'wx*gtk*' wx28-gtk2-2.8.12_5 wx28-gtk2-common-2.8.12_5 wx28-gtk2-contrib-2.8.12_5 wx28-gtk2-contrib-common-2.8.12_5 wx28-gtk2-unicode-2.8.12_5 wx28-gtk2-unicode-contrib-2.8.12_5 wx30-gtk2-3.0.2_2 Or you can search explicitly on the package origin: lucid-nonsense:...etc/pkg/repos:# pkg search -S origin -x wxgtk x11-toolkits/wxgtk28 x11-toolkits/wxgtk28-common x11-toolkits/wxgtk28-contrib x11-toolkits/wxgtk28-contrib-common x11-toolkits/wxgtk28-unicode x11-toolkits/wxgtk28-unicode-contrib x11-toolkits/wxgtk30 -- You are receiving this mail because: You are the assignee for the bug. From jeffreybouquet at yahoo.com Thu Mar 19 10:46:42 2015 From: jeffreybouquet at yahoo.com (Jeffrey Bouquet) Date: Thu, 19 Mar 2015 03:44:43 -0700 Subject: Feature request for pkg-devel Message-ID: <1426761883.87170.YahooMailBasic@web140903.mail.bf1.yahoo.com> I buillt today's pkg-devel and running a simple "pkg-static upgrade" from /src/ segfaults and exits. That might be an edge case (would not happen if installed, as usual, instead) OR pkg-devel (and maybe pkg) could use a full-backup-before-upgrade-install option, probably on by default, to avoid such breakage. OR maybe both apply (/s/OR/AND/) I'd rather see effort toward the latter than testing the former... similar to "portmaster -w " but more comprehensive. I'd certainly use it each time AFAIK. Thanks. No hurry. J. Bouquet From s.kasap at turquoise.com.tr Thu Mar 19 13:45:50 2015 From: s.kasap at turquoise.com.tr (SERKAN KASAP) Date: Thu, 19 Mar 2015 15:35:33 +0200 Subject: pkg install help Message-ID: <1322BB69A0BA4E7589FD54F8B9013A1D.MAI@hanturizm.com> hi i'am serkan. in older version i use pkg_add -rfi i=nodeps. but in new version i couldn't find this options. for example when i install a package it want from me intall package and following 3 package. can you help me? best regars. serkan. From bapt at FreeBSD.org Thu Mar 19 15:07:18 2015 From: bapt at FreeBSD.org (Baptiste Daroussin) Date: Thu, 19 Mar 2015 16:06:46 +0100 Subject: Feature request for pkg-devel In-Reply-To: <1426761883.87170.YahooMailBasic@web140903.mail.bf1.yahoo.com> References: <1426761883.87170.YahooMailBasic@web140903.mail.bf1.yahoo.com> Message-ID: <20150319150646.GA14611@ivaldir.etoilebsd.net> On Thu, Mar 19, 2015 at 03:44:43AM -0700, Jeffrey Bouquet via freebsd-pkg wrote: > I buillt today's pkg-devel and running a simple "pkg-static upgrade" from /src/ segfaults and > exits. I would be interested in the gdb trace, as I have not been able to crash pkg upgrade for a while! so anything reproducible would be more than interesting! > > That might be an edge case (would not happen if installed, as usual, instead) > OR > pkg-devel (and maybe pkg) could use a full-backup-before-upgrade-install option, probably on > by default, to avoid such breakage. > OR > maybe both apply (/s/OR/AND/) I'll think about the full-backup before upgrade but this is not as easy as it looks like :) regards, Bapt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From list_freebsd at bluerosetech.com Sun Mar 22 23:31:27 2015 From: list_freebsd at bluerosetech.com (list_freebsd at bluerosetech.com) Date: Sun, 22 Mar 2015 16:31:18 -0700 Subject: Segfault on pkg upgrade wit php5-pgsql locked Message-ID: <550F50C6.2060002@bluerosetech.com> This is happening on 10.1-p3 amd64 after upgrading pkg from 1.4.4 to 1.4.12: # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (48 candidates): 100% Processing candidates (48 candidates): 100% php5-pgsql-5.4.36 is locked and may not be modified Child process pid=69616 terminated abnormally: Segmentation fault Doing `pkg install -f pkg` then `pkg update -f` does not resolve this, but the problem is related to php5-pgsql being locked: # pkg info -k php5-pgsql php5-pgsql-5.4.36 yes # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (48 candidates): 100% Processing candidates (48 candidates): 100% php5-pgsql-5.4.36 is locked and may not be modified Child process pid=69731 terminated abnormally: Segmentation fault # pkg unlock -xy php5-pgsql Unlocking php5-pgsql-5.4.36 # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (48 candidates): 100% Processing candidates (48 candidates): 100% The following 50 packages will be affected (of 0 checked): New packages to be INSTALLED: postgresql93-client: 9.3.6_1 php56-session: 5.6.6 php56: 5.6.6 php56-xmlrpc: 5.6.6 php56-xml: 5.6.6 php56-mysql: 5.6.6 php56-mbstring: 5.6.6 php56-pgsql: 5.6.6 Installed packages to be UPGRADED: vim-lite: 7.4.560 -> 7.4.657 unzip: 6.0_2 -> 6.0_6 unbound: 1.5.1_2 -> 1.5.3_1 tevent: 0.9.21 -> 0.9.22 tdb: 1.2.13,1 -> 1.3.4,1 tcpdump: 4.5.1 -> 4.6.2 talloc: 2.1.0 -> 2.1.1 sqlite3: 3.8.7.4 -> 3.8.8.2 screen: 4.2.1_3 -> 4.2.1_5 samba36: 3.6.24_2 -> 3.6.25 postgresql92-server: 9.2.9_1 -> 9.2.10 postgresql92-client: 9.2.9_1 -> 9.2.10_1 pkgconf: 0.9.7 -> 0.9.8 php5-xmlrpc: 5.4.36 -> 5.4.38 php5-xml: 5.4.36 -> 5.4.38 php5-session: 5.4.36 -> 5.4.38 php5-pgsql: 5.4.36 -> 5.4.38 php5-mysql: 5.4.36 -> 5.4.38 php5-mbstring: 5.4.36 -> 5.4.38 php5: 5.4.36 -> 5.4.38 p5-Net-DNS: 0.81_1 -> 0.83_1 p5-BerkeleyDB: 0.54_2 -> 0.55 openssl: 1.0.1_16 -> 1.0.1_18 ntp: 4.2.8_3 -> 4.2.8p1 nsd: 4.1.0_1 -> 4.1.1 libtool: 2.4.2.418 -> 2.4.5 libpcap: 1.5.2 -> 1.6.2 libevent2: 2.0.21_3 -> 2.0.22_1 ldns: 1.6.17_3 -> 1.6.17_4 isc-dhcp42-server: 4.2.7 -> 4.2.8 gettext-tools: 0.19.3 -> 0.19.4 gettext-runtime: 0.19.3 -> 0.19.4 gettext: 0.19.3 -> 0.19.4 curl: 7.39.0_1 -> 7.41.0 cmake-modules: 3.1.0 -> 3.1.3 cmake: 3.1.0 -> 3.1.3 ca_root_nss: 3.17.3_1 -> 3.17.4_1 bind-tools: 9.10.1P1 -> 9.10.2 bash-static: 4.3.30_1 -> 4.3.33 automake: 1.14_1 -> 1.15 Installed packages to be REINSTALLED: postfixadmin-2.3.7_1 (direct dependency changed) phppgadmin-5.1 (direct dependency changed) The process will require 30 MiB more space. 62 MiB to be downloaded. Proceed with this action? [y/N]: From melissa at bluerosetech.com Mon Mar 23 19:04:05 2015 From: melissa at bluerosetech.com (Melissa Pilgrim) Date: Mon, 23 Mar 2015 12:03:57 -0700 Subject: Segfault on pkg upgrade wit php5-pgsql locked In-Reply-To: <550F50C6.2060002@bluerosetech.com> References: <550F50C6.2060002@bluerosetech.com> Message-ID: <5510639D.5070305@bluerosetech.com> On 2015-03-22 16:31, list_freebsd at bluerosetech.com wrote: > This is happening on 10.1-p3 amd64 after upgrading pkg from 1.4.4 to 1.4.12: > > # pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking for upgrades (48 candidates): 100% > Processing candidates (48 candidates): 100% > > php5-pgsql-5.4.36 is locked and may not be modified > Child process pid=69616 terminated abnormally: Segmentation fault > > Doing `pkg install -f pkg` then `pkg update -f` does not resolve this, > but the problem is related to php5-pgsql being locked: I should note that it's specifically this pkg for me. When doing this testing, I had other ports locked. Unlocking only php5-pgsql made the segfault go away, so it's not a case of pkg-upgrade segfaulting when encountering locks in general. This is also new behaviour after the upgrade to 1.4.12. From bugzilla-noreply at freebsd.org Wed Mar 25 15:10:58 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Wed, 25 Mar 2015 15:10:57 +0000 Subject: [Bug 198898] ports-mgmt/pkg: No syntax warning from pkg version In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198898 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Wed Mar 25 15:11:14 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Wed, 25 Mar 2015 15:11:14 +0000 Subject: [Bug 198900] ports-mgmt/pkg: pkg version show status '?' when using multiple repos In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198900 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Wed Mar 25 15:13:26 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Wed, 25 Mar 2015 15:13:26 +0000 Subject: [Bug 196068] ports-mgmt/pkg: incorrect output for pkg query '%n %B' In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196068 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Wed Mar 25 15:13:44 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Wed, 25 Mar 2015 15:13:43 +0000 Subject: [Bug 194981] ports-mgmt/pkg pkg-delete(8) man page incorrectly describes behaviour if unfulfilled dependencies In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194981 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From bugzilla-noreply at freebsd.org Wed Mar 25 15:13:50 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Wed, 25 Mar 2015 15:13:50 +0000 Subject: [Bug 194273] ports-mgmt/pkg: no package dependency on known shlib dependency In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194273 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From list_freebsd at bluerosetech.com Thu Mar 26 18:53:52 2015 From: list_freebsd at bluerosetech.com (list_freebsd at bluerosetech.com) Date: Thu, 26 Mar 2015 11:53:33 -0700 Subject: Segfault on pkg upgrade wit php5-pgsql locked In-Reply-To: <550F50C6.2060002@bluerosetech.com> References: <550F50C6.2060002@bluerosetech.com> Message-ID: <551455AD.1040002@bluerosetech.com> Can anyone help me with this? I'm not the only one who has reported segfaults with locked packages and right now this is reliably reproducible on this system, but I can't just sit on this due to security. Someone please help. On 2015-03-22 16:31, list_freebsd at bluerosetech.com wrote: > This is happening on 10.1-p3 amd64 after upgrading pkg from 1.4.4 to 1.4.12: > > # pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking for upgrades (48 candidates): 100% > Processing candidates (48 candidates): 100% > > php5-pgsql-5.4.36 is locked and may not be modified > Child process pid=69616 terminated abnormally: Segmentation fault > > Doing `pkg install -f pkg` then `pkg update -f` does not resolve this, > but the problem is related to php5-pgsql being locked: > > # pkg info -k php5-pgsql > php5-pgsql-5.4.36 yes > > # pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking for upgrades (48 candidates): 100% > Processing candidates (48 candidates): 100% > > php5-pgsql-5.4.36 is locked and may not be modified > Child process pid=69731 terminated abnormally: Segmentation fault > > # pkg unlock -xy php5-pgsql > Unlocking php5-pgsql-5.4.36 > > # pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking for upgrades (48 candidates): 100% > Processing candidates (48 candidates): 100% > The following 50 packages will be affected (of 0 checked): > > New packages to be INSTALLED: > postgresql93-client: 9.3.6_1 > php56-session: 5.6.6 > php56: 5.6.6 > php56-xmlrpc: 5.6.6 > php56-xml: 5.6.6 > php56-mysql: 5.6.6 > php56-mbstring: 5.6.6 > php56-pgsql: 5.6.6 > > Installed packages to be UPGRADED: > vim-lite: 7.4.560 -> 7.4.657 > unzip: 6.0_2 -> 6.0_6 > unbound: 1.5.1_2 -> 1.5.3_1 > tevent: 0.9.21 -> 0.9.22 > tdb: 1.2.13,1 -> 1.3.4,1 > tcpdump: 4.5.1 -> 4.6.2 > talloc: 2.1.0 -> 2.1.1 > sqlite3: 3.8.7.4 -> 3.8.8.2 > screen: 4.2.1_3 -> 4.2.1_5 > samba36: 3.6.24_2 -> 3.6.25 > postgresql92-server: 9.2.9_1 -> 9.2.10 > postgresql92-client: 9.2.9_1 -> 9.2.10_1 > pkgconf: 0.9.7 -> 0.9.8 > php5-xmlrpc: 5.4.36 -> 5.4.38 > php5-xml: 5.4.36 -> 5.4.38 > php5-session: 5.4.36 -> 5.4.38 > php5-pgsql: 5.4.36 -> 5.4.38 > php5-mysql: 5.4.36 -> 5.4.38 > php5-mbstring: 5.4.36 -> 5.4.38 > php5: 5.4.36 -> 5.4.38 > p5-Net-DNS: 0.81_1 -> 0.83_1 > p5-BerkeleyDB: 0.54_2 -> 0.55 > openssl: 1.0.1_16 -> 1.0.1_18 > ntp: 4.2.8_3 -> 4.2.8p1 > nsd: 4.1.0_1 -> 4.1.1 > libtool: 2.4.2.418 -> 2.4.5 > libpcap: 1.5.2 -> 1.6.2 > libevent2: 2.0.21_3 -> 2.0.22_1 > ldns: 1.6.17_3 -> 1.6.17_4 > isc-dhcp42-server: 4.2.7 -> 4.2.8 > gettext-tools: 0.19.3 -> 0.19.4 > gettext-runtime: 0.19.3 -> 0.19.4 > gettext: 0.19.3 -> 0.19.4 > curl: 7.39.0_1 -> 7.41.0 > cmake-modules: 3.1.0 -> 3.1.3 > cmake: 3.1.0 -> 3.1.3 > ca_root_nss: 3.17.3_1 -> 3.17.4_1 > bind-tools: 9.10.1P1 -> 9.10.2 > bash-static: 4.3.30_1 -> 4.3.33 > automake: 1.14_1 -> 1.15 > > Installed packages to be REINSTALLED: > postfixadmin-2.3.7_1 (direct dependency changed) > phppgadmin-5.1 (direct dependency changed) > > The process will require 30 MiB more space. > 62 MiB to be downloaded. > > Proceed with this action? [y/N]: > _______________________________________________ > freebsd-pkg at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe at freebsd.org" > From bugzilla-noreply at freebsd.org Fri Mar 27 02:59:22 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Fri, 27 Mar 2015 02:59:22 +0000 Subject: [Bug 198922] ports-mgmt/pkg: pkg2ng: Assertion failed In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198922 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|pkg2ng: Assertion failed |ports-mgmt/pkg: pkg2ng: | |Assertion failed Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org Component|Package Infrastructure |Individual Port(s) -- You are receiving this mail because: You are the assignee for the bug. From wjw at digiware.nl Fri Mar 27 11:57:39 2015 From: wjw at digiware.nl (Willem Jan Withagen) Date: Fri, 27 Mar 2015 12:57:30 +0100 Subject: pkg is not doing what I want..... Message-ID: <551545AA.7080107@digiware.nl> Hi, I'm trying to migrate as much as I can to using poudriere/pkg, but once in a while it just tries to put me in a corner where I do not want to be. Below is a attempt to remove perl from a php5 only jail. If I'd accept this, I'd be removing just about everything from that jail, leaving it useless. Whereas I almost certain that perl is only used for the autoconf and automake stuff, which is used by just about everything. So it is impossible to upgrade perl, because the "buildtime" dependancies require me to upgrae everything. But then adding new php5 stuff also runs into the same trap. So how do I remove perl, and maybe the runtime dependancies like p5-* and stuff, without pkg trashing everything?? --WjW root at CMSserver:/usr/ports/lang/perl5.18 # pkg delete perl-5.14.4_1 Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 53 packages (of 0 packages in the universe): Installed packages to be REMOVED: perl-5.14.4_1 p5-Carp-Clan-6.04 p5-TimeDate-2.30_1,1 p5-File-Tail-0.99.3 p5-YAML-Syck-1.27 p5-Date-Manip-6.34 net-snmp-5.7.2_3 p5-Bit-Vector-7.3 p5-Date-Calc-6.3 p5-Locale-gettext-1.05_3 swatch-3.2.3_2 help2man-1.43.3 autoconf-2.69 automake-1.14 pecl-APC-3.1.14_1 php5-mysql-5.4.19 php5-mysqli-5.4.19 php5-mcrypt-5.4.19 php5-openssl-5.4.19 php5-mbstring-5.4.19 php5-ldap-5.4.19 php5-session-5.4.19 php5-json-5.4.19 php5-simplexml-5.4.19 php5-imap-5.4.19 php5-soap-5.4.19 php5-iconv-5.4.19 php5-sockets-5.4.19 php5-gettext-5.4.19 php5-xml-5.4.19 php5-filter-5.4.19 php5-ctype-5.4.19 php5-curl-5.4.19_1 php5-xmlrpc-5.4.19 php5-dom-5.4.19 php5-xsl-5.4.19 php5-xmlreader-5.4.19 php5-zip-5.4.19 php5-fileinfo-5.4.19 php5-zlib-5.4.19 php5-bz2-5.4.19 php5-gd-5.4.19 pecl-pdflib-2.1.10 glib-2.36.3 liblqr-1-0.4.1_5 ImageMagick-nox11-6.8.0.7_3 pecl-imagick-3.1.2 php5-5.4.23 php5-hash-5.4.23 apache22-2.2.27_5 phpMyAdmin-4.2.2 php5-pdo_mysql-5.4.23 php5-pdo-5.4.23 The operation will free 179 MiB. From mat at mat.cc Fri Mar 27 13:08:54 2015 From: mat at mat.cc (Mathieu Arnold) Date: Fri, 27 Mar 2015 14:08:46 +0100 Subject: pkg is not doing what I want..... In-Reply-To: <551545AA.7080107@digiware.nl> References: <551545AA.7080107@digiware.nl> Message-ID: <00F808B7CB89DB6100C93D53@ogg.in.absolight.net> +--On 27 mars 2015 12:57:30 +0100 Willem Jan Withagen wrote: | So how do I remove perl, and maybe the runtime dependancies like p5-* and | stuff, without pkg trashing everything?? It seems this is a very old installation, the perl package has been called perl5 for quite a long time now. Also, I'd say it wants to remove all that because you do have an old installation where mod_php5 was included in php5, and apache22 needs perl at runtime. And mod_php needs apache. So all of php needs perl. It's all documented in UPDATING, but to sum up: pkg set -n perl:perl5 should take care of at least not trying to remove everything. -- Mathieu Arnold From wjw at digiware.nl Fri Mar 27 13:31:52 2015 From: wjw at digiware.nl (Willem Jan Withagen) Date: Fri, 27 Mar 2015 14:31:24 +0100 Subject: pkg is not doing what I want..... In-Reply-To: <00F808B7CB89DB6100C93D53@ogg.in.absolight.net> References: <551545AA.7080107@digiware.nl> <00F808B7CB89DB6100C93D53@ogg.in.absolight.net> Message-ID: <55155BAC.2060502@digiware.nl> On 27-3-2015 14:08, Mathieu Arnold wrote: > +--On 27 mars 2015 12:57:30 +0100 Willem Jan Withagen > wrote: > | So how do I remove perl, and maybe the runtime dependancies like p5-* and > | stuff, without pkg trashing everything?? > > It seems this is a very old installation, the perl package has been called > perl5 for quite a long time now. Now age is something in the eye of the beholder. :) But yes, the jail has been up and running since quite some time. Looking at some timestamps, its conception was August 2013 > Also, I'd say it wants to remove all that because you do have an old > installation where mod_php5 was included in php5, and apache22 needs perl > at runtime. And mod_php needs apache. So all of php needs perl. > It's all documented in UPDATING, but to sum up: upgrading perl does complain that 5.14 is (soon) no longer supported. 'mmm, wasn't aware of the fact that apache22 needed perl at runtime. And probably you are right that it is in UPDATING, but I probably overlooked it. > pkg set -n perl:perl5 > > should take care of at least not trying to remove everything. Thanx for the hint and I'll give it a go. --WjW From portscout at FreeBSD.org Sat Mar 28 08:59:59 2015 From: portscout at FreeBSD.org (portscout at FreeBSD.org) Date: Sat, 28 Mar 2015 08:59:58 +0000 Subject: FreeBSD ports you maintain which are out of date Message-ID: <201503280859.t2S8xwgU080290@portscout.freebsd.org> An embedded and charset-unspecified text was scrubbed... Name: not available URL: From bugzilla-noreply at freebsd.org Mon Mar 30 21:44:47 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Mon, 30 Mar 2015 21:44:46 +0000 Subject: [Bug 199049] ports-mgmt/pkg: [wishlist]: 'pkg fetch' should re-fetch files part from where it previously left off In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199049 Mathieu Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr at FreeBSD.org |pkg at FreeBSD.org Summary|pkg (pkgng) [wishlist]: |ports-mgmt/pkg: [wishlist]: |'pkg fetch' should re-fetch |'pkg fetch' should re-fetch |files part from where it |files part from where it |previously left off |previously left off Component|Package Infrastructure |Individual Port(s) -- You are receiving this mail because: You are the assignee for the bug. From bapt at FreeBSD.org Tue Mar 31 19:03:29 2015 From: bapt at FreeBSD.org (Baptiste Daroussin) Date: Tue, 31 Mar 2015 21:03:23 +0200 Subject: [CFT] Call for testing pkg 1.5.0 Message-ID: <20150331190323.GF30115@ivaldir.etoilebsd.net> Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Here is what happened since pkg 1.4.0: - pkg has grown with an initial support for provides/requires: this is a naive version but good enough to at least make major upgrade of php safer as well as making pear/pecl maintenance saner (note that this will need modifications in the ports tree) - Lots of new regression tests has been added, which allows us not less break your systems an unexpected way (do not worry there are still rooms for breakage) - Initial support for OS X - Initial support for NetBSD/EdjeBSD - Update most of the bundled third party software has been updated to their latest version - Improve the messages reported by pkg (and probably make some other worse) - Properly support file flags - Implement argument support for custom keywords - Extend setting credential via plist to allow to set file flags - Make credential syntax via plist more flexible allow to only defines the first fields and not latest for example @(user,,) can now be written just @(user) - pkg updating now supports case insensitive matching - pkg create now support a verbose mode - Add an option to change the default on question, until now the default answer was "No" with that option set it would be "Yes" - lots of fixes to pkg audit -r - Global memory usage reduction and speed up - Improvements and cleanup on pkg alias - pkg annotate --show --all has been fixed - Make pkg.h C++ friendly - Lots of improvements in the solver - Lots of fixes on 32 bits platforms - Add support for: pkg create -M ./plop.ucl -p ./plop.plist - New pkg -r that will install in the given rootdir without chrooting - Export PKG_ROOTDIR to scripts allow to make them as portable as possible - Stop trying to remove all installed package with the argument of pkg delete is a local file - Be more explicit about why the solver it going to reinstall, remove or upgrade (when possible) - Plenty of bug fixes - Plenty of new bugs Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Plan is to release 1.5.0 as soon as possible Best regards, Bapt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From bapt at FreeBSD.org Tue Mar 31 19:23:23 2015 From: bapt at FreeBSD.org (Baptiste Daroussin) Date: Tue, 31 Mar 2015 21:23:16 +0200 Subject: [CFT] Call for testing pkg 1.5.0 In-Reply-To: <1427829555.3892.7.camel@hardenedbsd.org> References: <20150331190323.GF30115@ivaldir.etoilebsd.net> <1427829555.3892.7.camel@hardenedbsd.org> Message-ID: <20150331192315.GH30115@ivaldir.etoilebsd.net> On Tue, Mar 31, 2015 at 03:19:15PM -0400, Shawn Webb wrote: > On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: > > Hi all, > > > > We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), > > Hey Baptiste, > > Great work to you and all those involved in this project! I'm grateful > to have such an awesome tool. > > For those of us who run our own package repos via Poudriere, what kinds > of changes should we expect to make once pkg 1.5.0 is released? Do we > need to do a full rebuild of our package repo? I'm also assuming that > the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running > `pkg upgrade`, right? > > Thanks again for your hard work. > Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) Best regards, Bapt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From shawn.webb at hardenedbsd.org Tue Mar 31 19:43:38 2015 From: shawn.webb at hardenedbsd.org (Shawn Webb) Date: Tue, 31 Mar 2015 15:19:15 -0400 Subject: [CFT] Call for testing pkg 1.5.0 In-Reply-To: <20150331190323.GF30115@ivaldir.etoilebsd.net> References: <20150331190323.GF30115@ivaldir.etoilebsd.net> Message-ID: <1427829555.3892.7.camel@hardenedbsd.org> On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: > Hi all, > > We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Hey Baptiste, Great work to you and all those involved in this project! I'm grateful to have such an awesome tool. For those of us who run our own package repos via Poudriere, what kinds of changes should we expect to make once pkg 1.5.0 is released? Do we need to do a full rebuild of our package repo? I'm also assuming that the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running `pkg upgrade`, right? Thanks again for your hard work. Thanks, Shawn -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part URL: From sg-ball at laposte.net Tue Mar 31 22:12:03 2015 From: sg-ball at laposte.net (sg-ball at laposte.net) Date: Tue, 31 Mar 2015 23:48:41 +0200 (CEST) Subject: Problem with pkg behind a chunking proxy In-Reply-To: <902242756.31277524.1427836544530.JavaMail.zimbra@laposte.net> Message-ID: <1476070491.31317997.1427838521190.JavaMail.zimbra@laposte.net> Some times ago I tried to install a FreeBSD 10.1 Release at work, where internal network is isolated from internet through a corporate proxy. And I could not make pkg work correctly. I finally confirmed the problem was caused by the proxy using Transfer-Encoding: chunked instead of giving in first place a ContentLength header by using a python script acting as a proxy and forcing either chunked or not chunked response, and filed a bug report : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198772 (got no followup till now ...) I could dive in pkg 1.4.12 source code (thanks to the port) and found that the real cause was that in libpkg/fetch.c function pkg_fetch_file_to_fd used remote = fetchXGet(u, &st, sbuf_data(fetchOpts)); to get remote file meta data in st (notably the file size) but did not test that st.size was not -1 (what it is when using Transfer-Encoding: chunked), so the following loop getting data up to st.size simply did not run. So I could make some minimal changes to this file (fetch.c) to accept st.size == -1. Currently it simply writes "Fetching file: 0%" until the file is fully downloaded and then write full line with "100% size speed time". Of course it runs unchanged if it gets the file size through a ContentLength header. It would certainly be better to trace the size all along the download, but it would require changes to libpkg/event.c as well, and I prefered to limit the changes for now. For anyone interested, I join the patch to this mail. My questions now are : - is this the correct way to propose a patch ? - would it be better to propose the patch for pkg-devel ? - or should I use directly github a submit a pull request ? - or the feature must first be discussed here ? - or ... I think this feature could be interesting since Transfer-Encoding: chunked is valid as HTTP 1.1 but I'm not used to submitting patches even if I've been using FreeBSD since release 3.x -------------- next part -------------- A non-text attachment was scrubbed... Name: pkg_1_4_14_libpkg_fetch.patch Type: text/x-patch Size: 1797 bytes Desc: not available URL: From bapt at FreeBSD.org Tue Mar 31 22:33:26 2015 From: bapt at FreeBSD.org (Baptiste Daroussin) Date: Wed, 1 Apr 2015 00:33:20 +0200 Subject: Problem with pkg behind a chunking proxy In-Reply-To: <1476070491.31317997.1427838521190.JavaMail.zimbra@laposte.net> References: <902242756.31277524.1427836544530.JavaMail.zimbra@laposte.net> <1476070491.31317997.1427838521190.JavaMail.zimbra@laposte.net> Message-ID: <20150331223320.GJ30115@ivaldir.etoilebsd.net> On Tue, Mar 31, 2015 at 11:48:41PM +0200, sg-ball at laposte.net wrote: > Some times ago I tried to install a FreeBSD 10.1 Release at work, where internal network is isolated from internet through a corporate proxy. And I could not make pkg work correctly. > > I finally confirmed the problem was caused by the proxy using Transfer-Encoding: chunked instead of giving in first place a ContentLength header by using a python script acting as a proxy and forcing either chunked or not chunked response, and filed a bug report : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198772 (got no followup till now ...) > > I could dive in pkg 1.4.12 source code (thanks to the port) and found that the real cause was that in libpkg/fetch.c function pkg_fetch_file_to_fd used > remote = fetchXGet(u, &st, sbuf_data(fetchOpts)); > to get remote file meta data in st (notably the file size) but did not test that st.size was not -1 (what it is when using Transfer-Encoding: chunked), so the following loop getting data up to st.size simply did not run. > > So I could make some minimal changes to this file (fetch.c) to accept st.size == -1. Currently it simply writes "Fetching file: 0%" until the file is fully downloaded and then write full line with "100% size speed time". Of course it runs unchanged if it gets the file size through a ContentLength header. > > It would certainly be better to trace the size all along the download, but it would require changes to libpkg/event.c as well, and I prefered to limit the changes for now. For anyone interested, I join the patch to this mail. > > My questions now are : > - is this the correct way to propose a patch ? > - would it be better to propose the patch for pkg-devel ? > - or should I use directly github a submit a pull request ? > - or the feature must first be discussed here ? > - or ... > > I think this feature could be interesting since Transfer-Encoding: chunked is valid as HTTP 1.1 but I'm not used to submitting patches even if I've been using FreeBSD since release 3.x First thank you for the patch! fixing this is on my TODO like forever. Second sorry to not have followed up on the bug tracker, I am very busy in lot of areas. So usually the feature should be discussed in pkg at FreeBSD.org or in #pkgng (freenode) or on github issue, I have to confess that I do track more often github issue tracker than freebsd's bugzilla for pkg related issues. (which is bad I should more track both). Concerning your feature it is very welcome :) usually we do like pull request on github. Note that you are just in time for pkg 1.5 which will be released soon :) The preferred way is usually pull request, but I'm flexible if the submitter is anti github then I can just grab patches. That part of the code hasn't been modified since pkg 1.4 so the patch should apply just fine. Note that the bootstrap /usr/sbin/pkg in base suffer the same problems so that patch will also apply there (maybe needed to be tuned a bit) So as a conclusion first make a pull request on github, then once it is well tested enough you can provide a patch for base (or I'll do) if so open a ticket in the bug tracker for base and do not hesitate to harass me :) Thanks again, Bapt > --- old/fetch.c 2015-02-13 20:34:33.000000000 +0100 > +++ new/fetch.c 2015-03-31 19:41:25.000000000 +0200 > @@ -618,30 +618,50 @@ > > pkg_emit_fetch_begin(url); > pkg_emit_progress_start(NULL); > - while (done < sz) { > - int to_read = MIN(sizeof(buf), sz - done); > + if (sz > 0) { > + while (done < sz) { > + int to_read = MIN(sizeof(buf), sz - done); > + > + pkg_debug(1, "Reading status: want read %d over %d, %d already done", > + to_read, sz, done); > + if ((r = fread(buf, 1, to_read, remote)) < 1) > + break; > + > + if (write(dest, buf, r) != r) { > + pkg_emit_errno("write", ""); > + retcode = EPKG_FATAL; > + goto cleanup; > + } > > - pkg_debug(1, "Reading status: want read %d over %d, %d already done", > - to_read, sz, done); > - if ((r = fread(buf, 1, to_read, remote)) < 1) > - break; > + done += r; > + pkg_debug(1, "Read status: %d over %d", done, sz); > > - if (write(dest, buf, r) != r) { > - pkg_emit_errno("write", ""); > + pkg_emit_progress_tick(done, sz); > + } > + > + if (done < sz) { > + pkg_emit_error("An error occurred while fetching package"); > retcode = EPKG_FATAL; > goto cleanup; > } > - > - done += r; > - pkg_debug(1, "Read status: %d over %d", done, sz); > - > - pkg_emit_progress_tick(done, sz); > - } > - > - if (done < sz) { > - pkg_emit_error("An error occurred while fetching package"); > - retcode = EPKG_FATAL; > - goto cleanup; > + } > + else { > + while ((r = fread(buf, 1, sizeof(buf), remote)) > 0) { > + if (write(dest, buf, r) != r) { > + pkg_emit_errno("write", ""); > + retcode = EPKG_FATAL; > + goto cleanup; > + } > + done += r; > + } > + if (r != 0) { > + pkg_emit_error("An error occurred while fetching package"); > + retcode = EPKG_FATAL; > + goto cleanup; > + } > + else { > + pkg_emit_progress_tick(done, done); > + } > } > pkg_emit_fetch_finished(url); > > _______________________________________________ > freebsd-pkg at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe at freebsd.org" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From bugzilla-noreply at freebsd.org Tue Mar 31 22:35:28 2015 From: bugzilla-noreply at freebsd.org (bugzilla-noreply at freebsd.org) Date: Tue, 31 Mar 2015 22:35:27 +0000 Subject: [Bug 194981] ports-mgmt/pkg pkg-delete(8) man page incorrectly describes behaviour if unfulfilled dependencies In-Reply-To: References: Message-ID: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194981 --- Comment #4 from Baptiste Daroussin --- Merged in git master will be in pkg 1.5.0 thanks -- You are receiving this mail because: You are the assignee for the bug.