private ports and pkgs versioning

Is there a standard way of naming a pkg that is locally compiled (maybe with a different set of options, or a local patch) so that it doesn't get confused with generic ports that are from freeBSD.org? I want to use mostly standard pkgs but need to compile a few myself (this can't be an

Re: pkg: cached package size mismatch, again

On Mon, Oct 17, 2016 at 7:17 PM, Baptiste Daroussin wrote: > On Mon, Oct 17, 2016 at 06:11:45PM +0300, Rostislav Krasny wrote: >> On Mon, Oct 17, 2016 at 5:55 PM, Rostislav Krasny >> wrote: >> > Hi, >> > >> > I've a fresh FreeBSD 11.0 installed. When I try

update math/matio

Built, test by cd work/matio-1.5.8 gmake check, and installed on FreeBSD 12.0-CURRENT r306998: Mon Oct 10 11:17:59 PDT 2016 amd64 Index: Makefile === --- Makefile(revision 423677) +++ Makefile(working copy) @@ -2,8 +2,8 @@

Re: Alternatives to rsync

On Monday, 17 October 2016 at 6:51:05 -0700, Freddie Cash wrote: > On Oct 17, 2016 1:21 AM, "Lars Engels" wrote: >> >> rsync 2 has a different algorithm for checking if a file changed. The >> new one is much faster. > > Rsync 2 also spent a long time building a list of

Please commit the Tor 0.2.8.8 update

It is considered to be a security update. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212952 Thanks! Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: Checking port option descriptions

[Default] On Mon, 19 Sep 2016 10:13:56 +0100, Matthew Seaman wrote: >Well, how about phpmyadmin as a for-instance? There are about eight PHP >modules which phpmyadmin will automagically adapt to the presence or >absence of at runtime and turn on or off corresponding bits of

Re: pkg: cached package size mismatch, again

On Mon, Oct 17, 2016 at 06:11:45PM +0300, Rostislav Krasny wrote: > On Mon, Oct 17, 2016 at 5:55 PM, Rostislav Krasny wrote: > > Hi, > > > > I've a fresh FreeBSD 11.0 installed. When I try to install x11/kde4 by > > pkg(8) it fails to install the very first dependency

Re: pkg: cached package size mismatch, again

On Mon, 17 Oct 2016 18:11:45 +0300 Rostislav Krasny wrote: > On Mon, Oct 17, 2016 at 5:55 PM, Rostislav Krasny wrote: > > Hi, > > > > I've a fresh FreeBSD 11.0 installed. When I try to install x11/kde4 by > > pkg(8) it fails to install the very first

poudriere: failed update via svn

Hi, i would like to update all jails from poudriere. The both FreeBSD 12 Jails are created via svn. # poudriere jail -u -j 12amd64 [00:00:00] >> Upgrading using svn [00:00:00] >> Updating the sources from svn.../lib/libc.so.7: version FBSD_1.5 required by /usr/local/lib/libapr-1.so.0 not

Re: pkg: cached package size mismatch, again

On Mon, Oct 17, 2016 at 5:55 PM, Rostislav Krasny wrote: > Hi, > > I've a fresh FreeBSD 11.0 installed. When I try to install x11/kde4 by > pkg(8) it fails to install the very first dependency package: > > Fetching ktux-4.14.3.txz: 100% 117 KiB 119.7kB/s00:01 > pkg:

pkg: cached package size mismatch, again

Hi, I've a fresh FreeBSD 11.0 installed. When I try to install x11/kde4 by pkg(8) it fails to install the very first dependency package: Fetching ktux-4.14.3.txz: 100% 117 KiB 119.7kB/s00:01 pkg: cached package ktux-4.14.3: size mismatch, fetching from remote Fetching ktux-4.14.3.txz: 100%

Re: wireshark 2.2.x build fail

On 10/16/16 18:56, Michael Butler wrote: On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail

Re: Alternatives to rsync

On Oct 17, 2016 1:21 AM, "Lars Engels" wrote: > > On Mon, Oct 17, 2016 at 09:46:31AM +1100, Greg 'groggy' Lehey wrote: > > On Friday, 14 October 2016 at 8:01:51 +0300, reko.turja--- via freebsd-ports wrote: > > > > > > Greg, I've actually put some thought in making a local

Re: FreeBSD Port: artifactory-4.12.0.1

Hi, Please ignore below, I believe this was an issue with passwd file. Don’t believe it was an issue with the port. Regards, Mike > On 17 Oct 2016, at 11:38, Michael Lewis wrote: > > Hi, > > I’ve tried to install the artifactory 4.12.0.1 port onto my machine > >

FreeBSD Port: artifactory-4.12.0.1

Hi, I’ve tried to install the artifactory 4.12.0.1 port onto my machine 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 The install seems to run through without error, but when I tried a

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

Re: harder and harder to avoid pkg

On 16.10.2016 05:16, Alfred Perlstein wrote: Has anyone actually looked/asked how other OS's solve this problem? Yes, for various linux distributions. This provided me with so many reasons to stay and work with the ports-tree. I too found "xxx-dev" vs "xxx-lib" annoying until I realized

Re: Alternatives to rsync

On Mon, Oct 17, 2016 at 09:46:31AM +1100, Greg 'groggy' Lehey wrote: > On Friday, 14 October 2016 at 8:01:51 +0300, reko.turja--- via freebsd-ports > wrote: > > > > Greg, I've actually put some thought in making a local port of > > rsync2. I've done some research on it and it seems to be fairly

Re: Alternatives to rsync

Am 17.10.2016 um 00:46 schrieb Greg 'groggy' Lehey: > On Friday, 14 October 2016 at 8:01:51 +0300, reko.turja--- via freebsd-ports > wrote: >> Greg, I've actually put some thought in making a local port of >> rsync2. I've done some research on it and it seems to be fairly >> usable and security

Re: pkg: PRE-INSTALL script failed

On 17.10.2016 08:21, Baptiste Daroussin wrote: > On Mon, Oct 17, 2016 at 08:09:12AM +0200, Jochen Neumeister wrote: >> The following 12 package(s) will be affected (of 0 checked): >> >> Installed packages to be UPGRADED: >> kde-workspace: 4.11.21_1 -> 4.11.21_2 >> gstreamer-plugins-vp8:

Re: pkg: PRE-INSTALL script failed

On Mon, Oct 17, 2016 at 01:20:09AM -0500, Mark Linimon wrote: > Is this with pkg 1.9.0 or the just-issued 1.9.1? > It has nothing to do with pkg but rather with pw. To be honnest I have no idea what was causing the problem. I have been able to reproduce only once: when binary upgrading to

Re: pkg: PRE-INSTALL script failed

On Mon, Oct 17, 2016 at 08:09:12AM +0200, Jochen Neumeister wrote: > The following 12 package(s) will be affected (of 0 checked): > > Installed packages to be UPGRADED: > kde-workspace: 4.11.21_1 -> 4.11.21_2 > gstreamer-plugins-vp8: 0.10.23_3,3 -> 0.10.23_4,3 > firefox: 49.0_3,1 ->

Re: pkg: PRE-INSTALL script failed

Is this with pkg 1.9.0 or the just-issued 1.9.1? mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

pkg: PRE-INSTALL script failed

The following 12 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: kde-workspace: 4.11.21_1 -> 4.11.21_2 gstreamer-plugins-vp8: 0.10.23_3,3 -> 0.10.23_4,3 firefox: 49.0_3,1 -> 49.0_7,1 filezilla: 3.19.0 -> 3.21.0 feh: 2.16.1 -> 2.17.1 conky: