From owner-freebsd-ports-bugs@freebsd.org  Wed Dec 20 00:53:47 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@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 CE54FE870AE
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Wed, 20 Dec 2017 00:53:47 +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 BAA7C74044
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 20 Dec 2017 00:53:47 +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 vBK0rlSF013870
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 20 Dec 2017 00:53:47 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 223227] sysutils/logrotate doesn't correctly work after
 upgrading to 3.13.0
Date: Wed, 20 Dec 2017 00:53:48 +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: needs-patch, needs-qa, regression
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: linimon@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-223227-13-q4VC9l1Vyd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223227-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-223227-13@https.bugs.freebsd.org/bugzilla/>
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-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 00:53:47 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223227

--- Comment #10 from Mark Linimon <linimon@FreeBSD.org> ---
(In reply to js from comment #8)

The criteria for our new PR system were:

 - it had to be better than GNATS.
 - it had to be free and open-source.
 - it had to have some degree of community support (outside of FreeBSD).
 - it had to be better than the other alternatives that met the above.

I wasn't involved in the Bugzilla installation, but I was involved in the
previous round of discussions on how to replace it.

The first one, everyone agreed on*.  The second one and third ones, most pe=
ople
agreed on.  The fourth one, everyone had their own opinions and the one was
picked that the least number of people found objectionable.

My own opinion after years of working on various PR systems is that they are
all terrible.  I also read the big caution "Do not write your own!" on one =
web
page as being a sad story from experience.

(At one time I did try to customize a non-open-source alternative to our ne=
eds:
the effort failed.)

So, while I understand that Bugzilla is frustrating to use, I honestly beli=
eve
we made the best decision possible at the time, given the resources we had.

mcl

* a low bar, to be sure.
(In reply to js from comment #9)
(In reply to js from comment #9)

--=20
You are receiving this mail because:
You are the assignee for the bug.=