Re: [HEADS UP] Planned deprecation of portsnap

> On 5 August 2020, at 23:57, Eugene Grosbein wrote: > > 06.08.2020 13:23, Doug Hardie wrote: > >>> On 5 August 2020, at 21:30, Eugene Grosbein wrote: >>> >>> 06.08.2020 6:02, Tatsuki Makino wrote >>> : >>>> Is there any command

Re: [HEADS UP] Planned deprecation of portsnap

> On 5 August 2020, at 21:30, Eugene Grosbein wrote: > > 06.08.2020 6:02, Tatsuki Makino wrote > : >> Is there any command other than "rm -rf /usr/ports ; portsnap extract" >> that can be easily repaired? > > svnlite revert -R /usr/ports master# svnlite revert -R /usr/ports svn: E155007: '/usr

Re: fetch is tarpitted by Texas Instruments and/or Akamai and can not download distfiles for TI-related ports.

> On 2 April 2020, at 11:22, Lev Serebryakov wrote: > > > It is true for both IPv4 and IPv6, and for Russia and Germany (I can > not test from USA, though). > > You could try it yourself: > > http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/8_3_2_2/export/msp430-gcc-suppor

Re: Dovecot packages

Correct. There is no port tree. Packages are used exclusively > On May 23, 2019, at 01:16, @lbutlr wrote: > >> On 22 May 2019, at 16:41, Doug Hardie wrote: >> It appears that the dovecot package is now the one that is maintained and >> dovecot2 package has remai

Re: Dovecot packages

> On 22 May 2019, at 16:23, Miroslav Lachman <000.f...@quip.cz> wrote: > > Doug Hardie wrote on 2019/05/23 00:41: > > [...] > >> Unless you notice this interesting anomaly, you can get easily burned like I >> did. I would recommend that either the dovecot2

Dovecot packages

Some years ago I setup a server with dovecot2 package. At that time there were 2 dovecot packages: dovecot which had a version of 1.x and dovecot2 which had a version of 2.x. That made sense since dovecot v2 is quite different from v1. As time went on I was upgrading that server to FreeBSD 12-

Upgrading to 12.0

I upgraded via pkg a test system from 11.0 to 12.0 a couple days ago. After getting everything there working, I upgraded a 11.1 production system to 12.0. Things are a bit weird with this one. The htmldoc port never got updated on either system. It asks for libssl.so.8. That doesn't exist a

Re: Qpopper and openssl on FreeBSD 11.x

> On 23 March 2018, at 02:40, Matthias Andree wrote: > > Am 17.02.2018 um 04:22 schrieb Doug Hardie: >> I have encountered an interesting situation while trying to resolve a PR on >> qpopper. I am unable to build qpopper on 11.1 (and probably 11.0) because &g

Qpopper and openssl on FreeBSD 11.x

I have encountered an interesting situation while trying to resolve a PR on qpopper. I am unable to build qpopper on 11.1 (and probably 11.0) because the openssl function SSLv3_server_method has been removed. I can see where the SSLv2 functions are disabled in ssl.h, but the SSLv3 functions ap

Re: Of LSOF

> On 27 December 2017, at 16:05, Kevin Oberman wrote: > > On Wed, Dec 27, 2017 at 3:47 PM, Doug Hardie wrote: > > On 27 December 2017, at 13:26, Dave Horsfall wrote: > > > > On Tue, 26 Dec 2017, Kevin Oberman wrote: > > > >> [...] Putting header fi

Re: Of LSOF

> On 27 December 2017, at 13:26, Dave Horsfall wrote: > > On Tue, 26 Dec 2017, Kevin Oberman wrote: > >> [...] Putting header files into the port is a non-starter as they MUST match >> the kernel on which lsof is built. I added lsof to PORTS_MODULES so it is >> rebuilt with any new kernel on m

Fwd: [exp - 103i386-default-build-as-user][mail/qpopper] Failed for qpopper-4.1.0_5 in package

I can't reproduce this problem. The GUIDE.pdf file is built properly in /usr/local/share/doc/qpopper. I am at a loss as to what to do about this. > Begin forwarded message: > > From: pkg-fall...@freebsd.org > Subject: [exp - 103i386-default-build-as-user][mail

Clamd core dumps

I just upgraded a mail server from 9.3 to 11.0-BETA4. clamav worked fine on 9.3. However, after upgrading it and reinstalling the package clamd core dumps just after reading all the signatures. Ktrace shows nothing other than the sig 11. I then built clamav from ports so I would have source.

Re: pkg upgrade issue

> On 22 February 2016, at 02:13, Baptiste Daroussin wrote: > > On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote: >> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages: >> >> sermons# pkg upgrade >> Updating repository catal

Re: pkg upgrade issue

our entry below. > On 22 February 2016, at 00:56, Lars Engels wrote: > > On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote: >> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages: >> >> sermons# pkg upgrade >> Updating

pkg upgrade issue

On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages: sermons# pkg upgrade Updating repository catalogue pkg: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz: File unavailable (e.g., file not found, no access) — Doug ___

Re: Pourdriere produces faulty build results due to bsd.openssl.mk bug

> On 1 April 2015, at 14:21, Yuri wrote: > > On 04/01/2015 14:17, Jung-uk Kim wrote: >> I know bsd.openssl.mk has been broken for very long time. For example, >> >> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405 >> >> However, I am not sure whether entirely removing it is the best way >

Re: Approving a patch

> On 3 March 2015, at 22:45, Kubilay Kocak wrote: > > > Canonically and preferred: > > Set maintainer-approval flag to + *on the attachment/patch*. > > The maintainer-feedback flag is at the issue/bug scope, not the > attachment/patch scope. > > This of course requires the maintainer-approva

Approving a patch

I am the maintainer for a port. I received a suggested patch for the port that is good. There used to be a link in the notification email to click on to approve the patch. With the new port system, that is gone (or at least I didn’t find it). I went through the porters manual and didn’t find

Package issue updating a packag3

I posted this on questions earlier and got no response. In the meantime, I have a system that is not really functional. I needed to update clamav-milter. I used: pkg upgrade clamav-milter The result was an error: Checking integrity... done (1 conflicting) pkg: Cannot solve problem us

Re: Upgrading a Port on 8.2

On 17 February 2014, at 21:43, Erich Dollansky wrote: > Hi, > > On Mon, 17 Feb 2014 21:07:43 -0800 > Doug Hardie wrote: > >> I have an older, but basically clean, install of 8.2 on a production >> system. It has a few ports that were installed back when 8.2 was

Upgrading a Port on 8.2

I have an older, but basically clean, install of 8.2 on a production system. It has a few ports that were installed back when 8.2 was new. However, I need to add pdftk. Pkg_add did that nicely. HOwever, it added version 1.44. The history for pdftk shows that a major problem was fixed in 1.4

Qpopper Port

I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or hi

Re: Dropbox on FreeBSD

On 5 March 2013, at 11:20, Wojciech Puchar wrote: >>> place. One was to eliminate multiple votes from the same IP I believe. >> >> Hrm. That sounds silly. The Dropbox voting actually encourages it's > > can anyone explain me what is so great in that software. > > got into webpage, and i

Re: New Port Options

On 6 October 2012, at 06:32, Eitan Adler wrote: > On 6 October 2012 01:01, Doug Hardie wrote: >> I just converted a port over to the new options structure and have a few >> observations. I have not been involved in any of the discussions about the >> structure as I di

New Port Options

I just converted a port over to the new options structure and have a few observations. I have not been involved in any of the discussions about the structure as I didn't have the time to get involved. However, a couple things came to mind during the process: 1. The Port handbook is actually

Port abcde and cdparanoia

I am converting a system from 8.2 to 9.0 and have encountered a significant problem with abcde and cdparanoia. On the new system, both of them believe the CD is blank. Here is the output of cdparanoia as its a bit more informative: > master# cdparanoia -vsQ > cdparanoia III release 9.8 (March

Request for qpopper testers

I didn't see my first announcement come back to me so am trying again. Qpopper 4.1.0 has been released and I have a first cut at the port files ready for testing. It builds fine with and without APOP. Presently I don't have a way to actually run it as my test machine is setup for a client who

Re: "stable" ports?

On 29 March 2010, at 08:57, Ivan Voras wrote: > In some cases the burdens are obvious - the maintainer(s) would need to > e.g. maintain three versions of the ports - a random example would be > e.g. X.Org 7.0 for 6.x, 7.2 for 7.x and 7.4 for 8.x. Another would be > keeping PHP 5.2 for 7.x and 8.x

sendip port

Has anyone managed to get sendip on 7.2 to work for IPv6? No matter what I have tried it always sets the next header field to 'ff'. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send

Bug in OpenBSD spamd

There is a bug in OpenBSD's spamd. The value for the whitelist expiration that can be set with the arguments to spamd is not used by spamlogd. It uses the hard-coded value of 36 days in grey.h. As a result if you think you are changing the time a whitelist entry is retained, you are actu

Re: Mail services checking - URGENT

On Sep 8, 2008, at 06:04, Jeremy Chadwick wrote: On Mon, Sep 08, 2008 at 05:59:54AM -0700, David Southwell wrote: On Monday 08 September 2008 05:19:51 Jeremy Chadwick wrote: On Mon, Sep 08, 2008 at 05:10:27AM -0700, David Southwell wrote: I have had a series of attacks on a system which resul

qpopper update

I am in the final stages of updating the qpopper port from version 4.0 to 4.1. However, there are a number of patches that have been incorporated into qpopper in the past that raise some questions. qpopper alters the names of all the binaries from popper* to qpopper*. I first thought tha

Qpopper 4.0.12

Qpopper 4.0.12 has recently been released. However there are a few bugs in that version. It can be made to work, but it requires altering the format of the config file. I have been working with the qpopper developers to get those fixed and a new config file parser has been created that w

Re: Package location

On Mar 3, 2008, at 11:43, Ion-Mihai Tetcu wrote: On Mon, 3 Mar 2008 00:39:54 -0800 Doug Hardie <[EMAIL PROTECTED]> wrote: On Mar 2, 2008, at 23:50, Scot Hetzel wrote: On 3/2/08, Doug Hardie <[EMAIL PROTECTED]> wrote: Adding ports to FreeBSD 7 I normally build from source

Re: Package location

On Mar 2, 2008, at 23:50, Scot Hetzel wrote: On 3/2/08, Doug Hardie <[EMAIL PROTECTED]> wrote: Adding ports to FreeBSD 7 I normally build from source and create a package. With previous versions the created packages went into /usr/ ports/packages/All. However the packages directory w

Package location

Adding ports to FreeBSD 7 I normally build from source and create a package. With previous versions the created packages went into /usr/ ports/packages/All. However the packages directory was not created on a new installation. The packages were being built in the ports top level directory

spamd port

I am trying to get the port mail/spamd to work on FreeBSD 6.2. There is not a lot of information on actually using spamd. So far I have figured out that I have to kldload pf and then a pfctl -e before attempting to start spamd. However, spamd-setup actually does nothing. pfctl -s rules

Re: FreeBSD Port: qpopper-4.0.9_1

On Oct 16, 2007, at 04:52, Walter Ian Kaye wrote: Hi, I tried to [mostly] follow instructions at but I don't know if ./configure overrides the port's "Options" screen or vice versa, so I don't know if I turned things on or off.

portconf port

I have been trying to figure out how to configure portconf. The 3 examples given are not much help with complex ports. I am starting with the dspam port (mail/dspam) as if I can figure that one out the rest should be easy. I first tried to use the arguments from the configure command:

Port Update format

I am the maintainer of the qpopper port. I now have the IPv6 patches working for qpopper-4.0.9 and would like to update the port with them. What is the proper format to submit the update? ___ freebsd-ports@freebsd.org mailing list http://lists.free