From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 07:39:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80BCD106566B for ; Sun, 24 Apr 2011 07:39:15 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 39D538FC0C for ; Sun, 24 Apr 2011 07:39:15 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1QDtuU-0006mD-4R>; Sun, 24 Apr 2011 09:39:14 +0200 Received: from e178026072.adsl.alicedsl.de ([85.178.26.72] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1QDtuU-0001wo-1Y>; Sun, 24 Apr 2011 09:39:14 +0200 Message-ID: <4DB3D3A1.3000005@mail.zedat.fu-berlin.de> Date: Sun, 24 Apr 2011 09:39:13 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: dinoex@FreeBSD.org References: <201104240510.p3O5AubZ095846@freefall.freebsd.org> In-Reply-To: <201104240510.p3O5AubZ095846@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.26.72 Cc: freebsd-ports@freebsd.org Subject: Re: ports/156598: graphics/netpbm: if: No such file or directory (netpbm-10.35.80_2) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 07:39:15 -0000 On 04/24/11 07:10, dinoex@FreeBSD.org wrote: > Synopsis: graphics/netpbm: if: No such file or directory (netpbm-10.35.80_2) > > State-Changed-From-To: open->closed > State-Changed-By: dinoex > State-Changed-When: Sun Apr 24 07:10:38 CEST 2011 > State-Changed-Why: > fix was aready committed, thanks. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=156598 I opened the above PR after three times the port graphics/netpbm has changed/fixed and the error is still present. I tried a few minutes ago, same error: -- ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE => netpbm-10.35.80.tgz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch http://heanet.dl.sourceforge.net/project/netpbm/super_stable/10.35.80/netpbm-10.35.80.tgz netpbm-10.35.80.tgz 100% of 2487 kB 794 kBps ===> Extracting for netpbm-10.35.80_2 => SHA256 Checksum OK for netpbm-10.35.80.tgz. ===> netpbm-10.35.80_2 depends on file: /usr/local/bin/perl5.12.3 - found ===> Patching for netpbm-10.35.80_2 ===> netpbm-10.35.80_2 depends on file: /usr/local/bin/perl5.12.3 - found ===> Applying FreeBSD patches for netpbm-10.35.80_2 ===> netpbm-10.35.80_2 depends on executable: gmake - found ===> netpbm-10.35.80_2 depends on file: /usr/local/libdata/pkgconfig/x11.pc - found ===> netpbm-10.35.80_2 depends on file: /usr/local/bin/perl5.12.3 - found ===> netpbm-10.35.80_2 depends on shared library: tiff.4 - found ===> netpbm-10.35.80_2 depends on shared library: jpeg.11 - found ===> netpbm-10.35.80_2 depends on shared library: png.6 - found ===> netpbm-10.35.80_2 depends on shared library: jbig.1 - found ===> netpbm-10.35.80_2 depends on shared library: jasper.4 - found ===> netpbm-10.35.80_2 depends on shared library: xml2.5 - found ===> Configuring for netpbm-10.35.80_2 if test -d "//usr/local/include/pm.h if: No such file or directory *** Error code 1 Stop in /usr/ports/graphics/netpbm. -- Regards Oliver From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 09:18:10 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8581E1065677 for ; Sun, 24 Apr 2011 09:18:10 +0000 (UTC) (envelope-from akabsd@yandex.ru) Received: from forward10.mail.yandex.net (forward10.mail.yandex.net [77.88.61.49]) by mx1.freebsd.org (Postfix) with ESMTP id 395AE8FC17 for ; Sun, 24 Apr 2011 09:18:10 +0000 (UTC) Received: from smtp9.mail.yandex.net (smtp9.mail.yandex.net [77.88.61.35]) by forward10.mail.yandex.net (Yandex) with ESMTP id C5A5C102104E; Sun, 24 Apr 2011 13:02:40 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1303635760; bh=xF6N8+WPL1rbrHpldmTwmqcP5h3yeRlszzD4YGwLOD0=; h=Subject:From:Reply-To:To:Cc:Content-Type:Date:Message-ID: Mime-Version:Content-Transfer-Encoding; b=EMz4ZipuhwodjU5PK5LO+LeMP0+niml5/a2dTRzLvXqfnUTWtdzsJMpNzitJyuF0r 5A1hvhzcT5G4NGPaKwFtXryzbenuORoWJw9sUsG/2rz1zg0q1ObJfS50ajm7CTxfFa sebpLU/vlDsczixdoxLoBrTi1FrgI0dIHLWnKgJM= Received: from [192.168.1.2] (unknown [178.137.131.125]) by smtp9.mail.yandex.net (Yandex) with ESMTPA id 7AD704BA0075; Sun, 24 Apr 2011 13:02:40 +0400 (MSD) From: paranormal To: ports@mark.reidel.info Content-Type: text/plain; charset="UTF-8" Date: Sun, 24 Apr 2011 12:02:29 +0300 Message-ID: <1303635749.26359.12.camel@localhost.eva02> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Yandex-Spam: 1 Cc: freebsd-ports@freebsd.org Subject: audio/musicpd and avahi (error message on startup) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: akabsd@yandex.ru List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 09:18:10 -0000 On default installation musicpd I have error: Apr 18 09:50:05 ---hostname-- mpd: avahi: Failed to create client: Daemon not running Apr 18 09:50:06 ---hostname-- avahi-daemon[1574]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Apr 18 09:50:09 ---hostname-- wpa_supplicant[448]: CTRL-EVENT-SCAN-RESULTS Because musicpd start early avahi. After I add to /usr/local/etc/rc.d/musicpd this: # # PROVIDE: musicpd -# REQUIRE: mixer LOGIN avahi_daemon +# REQUIRE: mixer LOGIN # KEYWORD: shutdown I have start musicpd without error. Apr 23 18:06:53 ---hostname-- mpd: avahi: Service 'Music Player' successfully established. I not find how build musicpd without avahi from ports. From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 09:20:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBD8A1065675 for ; Sun, 24 Apr 2011 09:20:48 +0000 (UTC) (envelope-from freebsd@heesakkers.info) Received: from server3.ohos.nl (server3.ohos.nl [IPv6:2a00:dd0:0:2::10]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD608FC17 for ; Sun, 24 Apr 2011 09:20:48 +0000 (UTC) Received: from [2001:470:1f15:1555::2] (helo=pcoliver.heesakkers.info) by server3.ohos.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.75) (envelope-from ) id 1QDvUk-000Lfg-8m for freebsd-ports@freebsd.org; Sun, 24 Apr 2011 11:20:47 +0200 From: Oliver Heesakkers To: freebsd-ports@freebsd.org Date: Sun, 24 Apr 2011 11:20:45 +0200 User-Agent: KMail/1.13.6 (FreeBSD/8.2-RELEASE-p1; KDE/4.6.2; amd64; ; ) References: <201104240510.p3O5AubZ095846@freefall.freebsd.org> <4DB3D3A1.3000005@mail.zedat.fu-berlin.de> In-Reply-To: <4DB3D3A1.3000005@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104241120.45646.freebsd@heesakkers.info> Subject: Re: ports/156598: graphics/netpbm: if: No such file or directory (netpbm-10.35.80_2) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 09:20:48 -0000 On Sunday 24 April 2011 09:39:13 O. Hartmann wrote: > On 04/24/11 07:10, dinoex@FreeBSD.org wrote: > > Synopsis: graphics/netpbm: if: No such file or directory (netpbm-10.35.80_2) > > > > State-Changed-From-To: open->closed > > State-Changed-By: dinoex > > State-Changed-When: Sun Apr 24 07:10:38 CEST 2011 > > State-Changed-Why: > > fix was aready committed, thanks. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=156598 > > I opened the above PR after three times the port graphics/netpbm has > changed/fixed and the error is still present. > > I tried a few minutes ago, same error: > (...) > ===> Configuring for netpbm-10.35.80_2 > if test -d "//usr/local/include/pm.h > if: No such file or directory > *** Error code 1 Take a look at the Makefile. If it has the lines highlighted in red here[1] then your portstree is not yet up to date. [1]. http://www.freebsd.org/cgi/cvsweb.cgi/ports/graphics/netpbm/Makefile.diff?r1=1.195;r2=1.196;f=h From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 09:45:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7943F106564A for ; Sun, 24 Apr 2011 09:45:54 +0000 (UTC) (envelope-from romain.garbage@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 312738FC1F for ; Sun, 24 Apr 2011 09:45:53 +0000 (UTC) Received: by vws18 with SMTP id 18so1711694vws.13 for ; Sun, 24 Apr 2011 02:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=or9CtKLoQKDJMrUW6910FxYOh984O/GGRFVEF769FWY=; b=aPpwCQYE7gqMvLoyb4Ueq6dlYuFB1fesJbMqm3veI4XmYKWROunsG3oXWr5Sw9LFPX OpmK/CadWmpUMgRRG5RVK63EtMnJ1BWBpODTwtIkWqqqRfcXmBdfy9Bkv2n0hAboXf70 KRzWv+TYPZRS/3ZJdsienS/rpig9/H9akn/w4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SIJn43SjSfO+e4sNvq0/jIpo7wKHJoGEbupv93Kwc/F1NV80BfqwUcaD4rGGsiIdC4 HM2FqFO7uPTXw6x/tn3JtBYMcNdlNO4izCfeMPTOtmObw74DwrxAl0E3rK2VlgPvL1C+ mSVmBMuMUF6Ls/BqOKRBZ4xyKXnIeAVgkwY78= MIME-Version: 1.0 Received: by 10.220.88.134 with SMTP id a6mr898693vcm.66.1303636543097; Sun, 24 Apr 2011 02:15:43 -0700 (PDT) Received: by 10.220.84.80 with HTTP; Sun, 24 Apr 2011 02:15:43 -0700 (PDT) Date: Sun, 24 Apr 2011 11:15:43 +0200 Message-ID: From: Romain Garbage To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: USE_PYDISTUTILS and easy_install X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 09:45:54 -0000 Hello list, I'm currently trying to create my first port. The program to port is python-based and the setup.py contains an install_requires directive. I was wondering if dependencies could be triggered by the setup.py file by just putting USE_PYDISTUTILS=easy_install in the Makefile, or do I have to use RUN_DEPENDS and BUILD_DEPENDS variables? I searched for ports using USE_PYDISTUTILS=easy_install, but all I have looked into also use RUN_DEPENDS and BUILD_DEPENDS. Regards, Romain From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 12:02:02 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E8421065670; Sun, 24 Apr 2011 12:02:02 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id CEEE38FC08; Sun, 24 Apr 2011 12:02:01 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 02D10F; Sun, 24 Apr 2011 14:02:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Sun, 24 Apr 2011 14:02:01 +0200 From: Bernhard Froehlich To: , In-Reply-To: <430fcb25aefc374bf256e45e3151de15@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> Message-ID: <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B020B.4DB41138.006C,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 12:02:02 -0000 On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: > PBIs for PC-BSD are currently worked on and will hopefully be available > in a few days. Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts to provide the PBIs! PC-BSD 8.x 32bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi PC-BSD 8.x 64bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi Feedback (positive and negative) from PC-BSD users is very welcome! -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 12:34:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FBF8106564A for ; Sun, 24 Apr 2011 12:34:45 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1A9218FC08 for ; Sun, 24 Apr 2011 12:34:44 +0000 (UTC) Received: by qyk27 with SMTP id 27so951811qyk.13 for ; Sun, 24 Apr 2011 05:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=RYeNeRJer5uTATKjS45G/dF3DQ4teNr7BWT8zEOa8TU=; b=N8gTuV91kU46vOVcuVdvC3zKYEx9VbCTkT7q2NZHgsKnte6+SOI2G4AT+GGXX7cJAX Y1Px6GmKAhpdNkXqsIJ557Iriu5rvUZ1F8TUAPFmvI8M1fORS6NiS6I7m0b4vRanj7T/ oKoJPk4jFP0b7BgHah+N7FAl8aw5y2OhtkLrY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bj2ESdrAOSWXaafgSzUYOvmSEzFuZLKbU9sTYC/e76EEVhX7aADrNuLQFtBtgi30cy 9KcPmS0dj56VFTrfJKmergp28URztJy7awb1aAwFuudwUjFHazl7j2GB4/HNGr66TB8p RSLuL2eux6AQegHndQgvGOup62nGMNrPffNfk= MIME-Version: 1.0 Received: by 10.224.212.8 with SMTP id gq8mr2172781qab.250.1303646676071; Sun, 24 Apr 2011 05:04:36 -0700 (PDT) Received: by 10.224.29.1 with HTTP; Sun, 24 Apr 2011 05:04:35 -0700 (PDT) In-Reply-To: References: Date: Sun, 24 Apr 2011 20:04:35 +0800 Message-ID: From: wen heping To: Romain Garbage Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org Subject: Re: USE_PYDISTUTILS and easy_install X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 12:34:45 -0000 2011/4/24 Romain Garbage : > Hello list, > > I'm currently trying to create my first port. The program to port is > python-based and the setup.py contains an install_requires directive. > I was wondering if dependencies could be triggered by the setup.py > file by just putting USE_PYDISTUTILS=easy_install in the Makefile, or > do I have to use RUN_DEPENDS and BUILD_DEPENDS variables? USE_PYDISTUTILS=easy_install only make port depend on python and setuptools. If your ports depends other python package, you should use DEPENDS. I would be glad to test it if you send your shar file of the new port. wen > I searched for ports using USE_PYDISTUTILS=easy_install, but all I > have looked into also use RUN_DEPENDS and BUILD_DEPENDS. > > Regards, > Romain > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 13:22:06 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16E5E106566C for ; Sun, 24 Apr 2011 13:22:06 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0898FC1C for ; Sun, 24 Apr 2011 13:22:05 +0000 (UTC) Received: by bwz12 with SMTP id 12so1830412bwz.13 for ; Sun, 24 Apr 2011 06:22:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:date:message-id:subject :from:to:cc:content-type; bh=HGjw7zxXsBvEcg59Rx6YjLzxzOiDPP04qRXV5tlYFPI=; b=vycE8qcOu6YQWtisO9sRCIkTL8Tc9UD2MCAIDw0F+G0iYXhWeh3WlLvpNhIPnD7RXS JkJkbftWsHaXjeigy/pAPgxvKq2lR547B5C6ZlBPzMXirSq2EUrFPPStWBasHcraqVJP zUbRTtaN0DALD8nMVsTeZQb/Iz2MP9eVrmk3E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; b=dpePGAENVoYWNpEqflhHEUYJjRHgHx4VYonZFRd0Fpmq0sqomsiGMDzonRZFBi4k0e eTOYXo0VOvVrtWlpxZFfYlSwqKS4HuH0PcFmwDrUtg2Fu6bZRWMEmKFblXMj9K6kqqdg 4IyeXS+mK7ge125zIgNZmZP2LKJuz417irGHg= MIME-Version: 1.0 Received: by 10.204.74.11 with SMTP id s11mr2597089bkj.43.1303651324369; Sun, 24 Apr 2011 06:22:04 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Sun, 24 Apr 2011 06:22:04 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Sun, 24 Apr 2011 06:22:04 -0700 (PDT) Date: Sun, 24 Apr 2011 14:22:04 +0100 Message-ID: From: Chris Rees To: akabsd@yandex.ru Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@mark.reidel.info, freebsd-ports@freebsd.org Subject: Re: audio/musicpd and avahi (error message on startup) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 13:22:06 -0000 On 24 Apr 2011 10:18, "paranormal" wrote: > > On default installation musicpd I have error: > > > Apr 18 09:50:05 ---hostname-- mpd: avahi: Failed to create client: > Daemon not running > Apr 18 09:50:06 ---hostname-- avahi-daemon[1574]: WARNING: No NSS > support for mDNS detected, consider installing nss-mdns! > Apr 18 09:50:09 ---hostname-- wpa_supplicant[448]: > CTRL-EVENT-SCAN-RESULTS > > Because musicpd start early avahi. After I add > to /usr/local/etc/rc.d/musicpd this: > > # > # PROVIDE: musicpd > -# REQUIRE: mixer LOGIN avahi_daemon > +# REQUIRE: mixer LOGIN > # KEYWORD: shutdown > > > I have start musicpd without error. > Apr 23 18:06:53 ---hostname-- mpd: avahi: Service 'Music Player' > successfully established. > > I not find how build musicpd without avahi from ports. > > I'll have a look later. For future reference, please CC maintainers when you have a question about a port, makes it easier to see! Do a make -V MAINTAINER in the port directory. Thanks for your suggested fix, Chris From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 15:12:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C555106564A for ; Sun, 24 Apr 2011 15:12:02 +0000 (UTC) (envelope-from romain.garbage@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 38D938FC12 for ; Sun, 24 Apr 2011 15:12:01 +0000 (UTC) Received: by vxc34 with SMTP id 34so1835328vxc.13 for ; Sun, 24 Apr 2011 08:12:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jKlgIGUpGALqcTuL8lpbv0rADOPXMMAhv1oUnR+JIB0=; b=R0iUHm81dQeCnTaaurZqTKopxuZ14yXAgLnB9Ntgy7u0J5TZC63DK66RKR0yIdTjeq PdY1eIQ0pTGoU8Jgp0oDEqizYuDrfA4TOGI0V+PCmG9BVAuZpH9/cVyX/ZnpKAqjvyua AcO1ZPvX616PsPUFXXRot2jG7ZSiNm0Z2JSy4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lJM5vkgp/T6JBpoOjjjSw9to/tSf5H+fR5/30KOIYNzj4ltIjc39/kj/qNw1yk1RHT hJxeduau3TbIBej2DWtsnN3w9TSe1mEIWVdX5PHCq1jb1OjRA1Xaoar4xe/OhaEHGiZc QQNmTHJbb/QSReo0Ua3heia2QNPn3BmjsTMKM= MIME-Version: 1.0 Received: by 10.220.101.72 with SMTP id b8mr969920vco.136.1303657921270; Sun, 24 Apr 2011 08:12:01 -0700 (PDT) Received: by 10.220.84.80 with HTTP; Sun, 24 Apr 2011 08:12:01 -0700 (PDT) In-Reply-To: References: Date: Sun, 24 Apr 2011 17:12:01 +0200 Message-ID: From: Romain Garbage To: wen heping Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org Subject: Re: USE_PYDISTUTILS and easy_install X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 15:12:02 -0000 2011/4/24 wen heping : > > USE_PYDISTUTILS=easy_install only make port depend on python and > setuptools. If your ports depends other python package, you should use > DEPENDS. Ok, thank you. So if my port depends on another python module that doesn't exist in Ports, I also have to make a new port for that? > I would be glad to test it if you send your shar file of the new port. Ok, thank you very much, I'll send it to you when I'm done with it before filling a PR. Regards, Romain From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 15:14:43 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FA3D106566C for ; Sun, 24 Apr 2011 15:14:43 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 5637B8FC08 for ; Sun, 24 Apr 2011 15:14:42 +0000 (UTC) Received: by qyk35 with SMTP id 35so456500qyk.13 for ; Sun, 24 Apr 2011 08:14:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bHQQcMFzKfpAqVEzwPQZw+OofVSSJb4Q8+bXHzJpVIs=; b=xAv4wQdeslGTz4ScRwsfCyzUmJJmCC8WnGFTKXz3lqXHjQU+1hKjYiHLXJNUHoYjq+ x1z+VzyZRRwgnuhWEQspX8SF9PXsbsRl/7nTgBY8YzFP9Is9Tpo8nTgWdjfGQiYXDUjr nX2q4gGWdwApe1+NnIpP230MV0bJZGOEejCZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=oq8HNcAC0fX5Z9WVF0/gEWcMIwuJcLqQ+Dc+URBtfbXxlnbkIK6Rvh5hvSqx2RTvcH Y4Kn5s8YhvQBY1fV3+/qXbMwcSQTr2P2Obsidpq+T9SsROJzNYDyIfZuGGqPjgrBpUDc nRFuVusWe0JIkN69qIBNFoHp+f/PzNGXL9Q54= MIME-Version: 1.0 Received: by 10.224.215.131 with SMTP id he3mr2078634qab.300.1303658082183; Sun, 24 Apr 2011 08:14:42 -0700 (PDT) Received: by 10.224.29.1 with HTTP; Sun, 24 Apr 2011 08:14:42 -0700 (PDT) In-Reply-To: References: Date: Sun, 24 Apr 2011 23:14:42 +0800 Message-ID: From: wen heping To: Romain Garbage Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org Subject: Re: USE_PYDISTUTILS and easy_install X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 15:14:43 -0000 2011/4/24 Romain Garbage : > 2011/4/24 wen heping : >> >> USE_PYDISTUTILS=easy_install only make port depend on python and >> setuptools. If your ports depends other python package, you should use >> DEPENDS. > > Ok, thank you. So if my port depends on another python module that > doesn't exist in Ports, I also have to make a new port for that? Yes. wen > >> I would be glad to test it if you send your shar file of the new port. > > Ok, thank you very much, I'll send it to you when I'm done with it > before filling a PR. > > Regards, > Romain > From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 15:57:08 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01EDA106566B; Sun, 24 Apr 2011 15:57:08 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 855E18FC0A; Sun, 24 Apr 2011 15:57:07 +0000 (UTC) Received: by yie12 with SMTP id 12so605465yie.13 for ; Sun, 24 Apr 2011 08:57:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer; bh=asJL+14NyklSN0cbOG61FnqUmXAP6OC6WpT92TMh1ig=; b=k8/yDhSUUWqMlO2qFa8ukIg4Sq1cFRVyAyjoYcwvSCCj+7psuSPxHNGKcMQMG1/Eds 5LvBknUD+34xqxYBNwFoMXv5w78UgY4qONxfOFRLkIQv+8FVzCYVyFmY3yjPp/Iy2Qd4 s3OHBZYXV0CP09RLzPT/O3F9o4BI2FX7ajEhA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer; b=f+vl6UNxDzRU8kST3nJwNeSd9e2XTRY+9/5xeW07uHkDp3p4U9ojNIVUwxef8A5SeF m5asY0fKpSvi5QJ5GkKdli1EbWnDr2m8DI99CQtepV+zd8w/i4+G6+7Oreg9P+E49cSG P2uIsJ/2T2tFNjLb1v5dYbRJKiS4kaj4y2/Xk= Received: by 10.101.189.34 with SMTP id r34mr1629045anp.77.1303658988296; Sun, 24 Apr 2011 08:29:48 -0700 (PDT) Received: from [192.168.6.230] ([201.21.167.145]) by mx.google.com with ESMTPS id c21sm4824283anc.40.2011.04.24.08.29.45 (version=SSLv3 cipher=OTHER); Sun, 24 Apr 2011 08:29:46 -0700 (PDT) From: Sergio de Almeida Lenzi To: Bernhard Froehlich In-Reply-To: <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Date: Sun, 24 Apr 2011 12:29:43 -0300 Message-ID: <1303658983.36234.7.camel@z6000.lenzicasa> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: emulation@FreeBSD.org, ports@FreeBSD.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 15:57:08 -0000 For me it is working... running windows XP dnd linux over an old(4.0.2) image it is ok... very stable... Only a problem remains (that is not still fixed): it is the problem with the vnc in VBoxHeadless the cursor is not in sync (the vnc cursor) is not in sync with the XP cursor.. although the sync is better (compared with 4.0.2 but is still out of sync)... How to reproduce: VBoxHeadless --vnc --vncport 5901 --startvm XPimg then goto another machine and execute: vncviewer x.x.x.x:5901, the system opens works but the mouse cursor is not in sync... Question: Will there be a fix??? Thanks for your attention.... Happy Easter for all From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 16:26:34 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFC39106564A; Sun, 24 Apr 2011 16:26:33 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 734508FC0A; Sun, 24 Apr 2011 16:26:33 +0000 (UTC) Received: by gxk28 with SMTP id 28so608273gxk.13 for ; Sun, 24 Apr 2011 09:26:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer; bh=u1ZyVcKF2GSTTsM2TKQVCJg2DboN+xkfWT3qss/LL0E=; b=HVz4VpXQSAUOboZXY26rUPMrycr75In3p6OXuTNs/XtuKoKr6o4DALDvEMljhPuJ4z WwDf9qbzU1aGJ5NEbMbSQvHrZ7e6VECWUnyqU2nKatNts62xaVC8SgNyZDCqeID8v86/ f4fP1uSfhP8NWAazw/p5dwj1rNlyEXeu0/cws= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer; b=OB7SqM9mvwfUqQn9I5ef5l8xHxuyKh/Wk2MG4Blj2QfZFi53F25s9nmL47kt+HA72G WZcuN0o9IY13qbR86sWEwMOnQ0O6rgC0qp8cXF42A+MprFsY2JxPGVDoNCRnGvLuSAMj X0OzGWsut8KtSOjNP/+3qXQ4C2fH2QF9z7HPA= Received: by 10.150.61.13 with SMTP id j13mr2794772yba.180.1303662392541; Sun, 24 Apr 2011 09:26:32 -0700 (PDT) Received: from [192.168.6.230] ([201.21.167.145]) by mx.google.com with ESMTPS id p11sm2756871ann.49.2011.04.24.09.26.29 (version=SSLv3 cipher=OTHER); Sun, 24 Apr 2011 09:26:31 -0700 (PDT) From: Sergio de Almeida Lenzi To: Bernhard Froehlich In-Reply-To: <430fcb25aefc374bf256e45e3151de15@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> Date: Sun, 24 Apr 2011 13:26:28 -0300 Message-ID: <1303662388.42253.5.camel@z6000.lenzicasa> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: emulation@FreeBSD.org, ports@FreeBSD.org Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 16:26:34 -0000 For me it is working... running windows XP dnd linux over an old(4.0.2) image it is ok... very stable... Only a problem remains (that is not still fixed): it is the problem with the vnc in VBoxHeadless the cursor is not in sync (the vnc cursor) is not in sync with the XP cursor.. although the sync is better (compared with 4.0.2 but is still out of sync)... How to reproduce: VBoxHeadless --vnc --vncport 5901 --startvm XPimg then goto another machine and execute: vncviewer x.x.x.x:5901, the system opens works but the mouse cursor is not in sync... Question: Will there be a fix??? Thanks for your attention.... Happy Easter for all From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 17:06:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30932106564A for ; Sun, 24 Apr 2011 17:06:16 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B27DA8FC14 for ; Sun, 24 Apr 2011 17:06:15 +0000 (UTC) Received: by bwz12 with SMTP id 12so1923899bwz.13 for ; Sun, 24 Apr 2011 10:06:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=583q9YUU3Ia1u+t4woDJIWpJW0pZXsuWWxWF0L0GExc=; b=PYgFemHLH9cwVFECNYFJi6YNgZHt0C8KOlFoBB2F9pvaWpqSx4adlm/qzLhM7G9b5s lhOam1uWM6P6mj061SLRIn+IRuy4guNUf/xbu38SVaKlAZr8PJGJPGaUw8wvLCal55hb 99QYisz/omQOpU5Tj2C6xrFn7nvWlftHyOGfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=BqF0+HqoO18oZk2HBeFfAwx5tk0EyHow3qmn4SE1B4oFuXaWgXjV7a1Zfh/eInROBu UCfR7kAWiq0PMYw2OhoSSc8iFFkmkSHyXeiY5loXPVZiTwx0rd7Kq+twvxiURrzqjhjO 3N6i0C0kx4O6NKHW6dPJWvA+AbNk8qpWEhZwc= Received: by 10.204.19.76 with SMTP id z12mr2572264bka.205.1303664774194; Sun, 24 Apr 2011 10:06:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.42.21 with HTTP; Sun, 24 Apr 2011 10:05:44 -0700 (PDT) In-Reply-To: References: From: Chris Rees Date: Sun, 24 Apr 2011 18:05:44 +0100 Message-ID: To: akabsd@yandex.ru Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: ports@mark.reidel.info, freebsd-ports@freebsd.org Subject: Re: audio/musicpd and avahi (error message on startup) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 17:06:16 -0000 On 24 April 2011 14:22, Chris Rees wrote: > > On 24 Apr 2011 10:18, "paranormal" wrote: >> >> On default installation musicpd I have error: >> >> >> Apr 18 09:50:05 ---hostname-- mpd: avahi: Failed to create client: >> Daemon not running >> Apr 18 09:50:06 ---hostname-- avahi-daemon[1574]: WARNING: No NSS >> support for mDNS detected, consider installing nss-mdns! >> Apr 18 09:50:09 ---hostname-- wpa_supplicant[448]: >> CTRL-EVENT-SCAN-RESULTS >> >> Because musicpd start early avahi. After I add >> to /usr/local/etc/rc.d/musicpd this: >> >> =9A# >> =9A# PROVIDE: musicpd >> -# REQUIRE: mixer LOGIN avahi_daemon >> +# REQUIRE: mixer LOGIN >> =9A# KEYWORD: shutdown >> >> >> I have start musicpd without error. >> Apr 23 18:06:53 ---hostname-- mpd: avahi: Service 'Music Player' >> successfully established. >> >> I not find how build musicpd without avahi from ports. >> >> > > I'll have a look later. For future reference, please CC maintainers when = you > have a question about a port, makes it easier to see! Do a make -V > MAINTAINER in the port directory. > > Thanks for your suggested fix, > Please test the fix I've knocked together [1], see if it works for you. You can now choose to compile with or without avahi support -- pick your poison. Avahi's compiling for me now, so I'll let you know if it works when I'm don= e. Chris [1] http://www.bayofrum.net/~crees/patches/musicpd-avahi.diff From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 17:52:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 333021065670; Sun, 24 Apr 2011 17:52:01 +0000 (UTC) (envelope-from dnaeon@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AD0448FC17; Sun, 24 Apr 2011 17:52:00 +0000 (UTC) Received: by vxc34 with SMTP id 34so1896814vxc.13 for ; Sun, 24 Apr 2011 10:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=kVlSMsOvsphl4b/zsR0mGX7ryWe3AGRTD8GAeh5jeTA=; b=oJjgUEwtlG+hcx/mddZALYZUCHBRpigpDyO3S/RKDJvPb18FkVHth3Dz6jrQu4DLd9 eDp5CGyYGF4CEY92MUtCx01JIovlOoxJ/YXOjvx1qgVmGwSIv+0S1E61l1M7wIZWo1Ys y7UUcVLGxhD+RUO01+qoo5JKYqvxyugeDbw/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hFRqtengf0nbdmnEphpi5f0ADMG4QYVPAsWYIzQFuhnLdBlOFsLqKARzBG4eWSdfL1 p3f3m2Qd0hWpfnc6bfqxue6G6BXXFpAtokeWW4hRyEV1SNW3isZon4InAmVJlK8J8y+A BTI/Tiumo7z5FR/ZhW+NXD3uCI7eiytOs7SaY= MIME-Version: 1.0 Received: by 10.52.98.39 with SMTP id ef7mr60342vdb.145.1303665779282; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Received: by 10.52.160.226 with HTTP; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Date: Sun, 24 Apr 2011 20:22:59 +0300 Message-ID: From: Marin Atanasov Nikolov To: freebsd-ports@freebsd.org, ml-freebsd-stable , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Configuration Management with Cfengine 3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 17:52:01 -0000 Hello, Recently I've been working on automating my FreeBSD systems, as much as possible and the viable solution was to try out Cfengine 3. Currently I'm running most of my hosts and jails under Cfengine 3 control, and wanted to share this you, because I think some might find it useful. Therefore I've created a little documentation that explains how to setup Cfengine 3 on your systems and use it for managing your hosts and jails - starting from simple configuration deployments and daemon processes control, and package management with Cfengine 3. Anyway the document can be found here: - http://unix-heaven.org/node/50 Hope you find it useful. Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 19:03:42 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91A8C106566B for ; Sun, 24 Apr 2011 19:03:42 +0000 (UTC) (envelope-from akabsd@yandex.ru) Received: from forward10.mail.yandex.net (forward10.mail.yandex.net [77.88.61.49]) by mx1.freebsd.org (Postfix) with ESMTP id 148628FC15 for ; Sun, 24 Apr 2011 19:03:41 +0000 (UTC) Received: from smtp6.mail.yandex.net (smtp6.mail.yandex.net [77.88.61.56]) by forward10.mail.yandex.net (Yandex) with ESMTP id 7CF341020EF4; Sun, 24 Apr 2011 23:03:40 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1303671820; bh=FdIASPFmZIATvHcgZUiuvpt38p3sgYp5suymF+wxn9k=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type: Date:Message-ID:Mime-Version; b=LFI19hSP3gHwRpPVvYeYNVi7dkx3kKqZ4SFr7njsDWIyoaMj7DMiZPiLFdJQ/IAWl 5tQhMAkxJkk/X9ni3AZ+CrvunRZ9cPsrudcsL4CLiDmTVQsBOz8McFTJZ7iZmgQyzt AAppEDEOsKmYsLUcY0Yw8CVr5xphzPnvO82VQp80= Received: from [192.168.1.2] (unknown [178.137.131.125]) by smtp6.mail.yandex.net (Yandex) with ESMTPA id 3543B2A8051; Sun, 24 Apr 2011 23:03:40 +0400 (MSD) From: paranormal To: utisoft@gmail.com In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-+QGiNg0Inob8SxEJkgME" Date: Sun, 24 Apr 2011 22:03:39 +0300 Message-ID: <1303671819.21735.2.camel@localhost.eva02> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Yandex-Spam: 1 Cc: freebsd-ports@freebsd.org Subject: Re: audio/musicpd and avahi (error message on startup) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: akabsd@yandex.ru List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 19:03:42 -0000 --=-+QGiNg0Inob8SxEJkgME Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable With patch, for me work both version (with and without avahi) Thx. On Sun, 2011-04-24 at 18:05 +0100, Chris Rees wrote: > On 24 April 2011 14:22, Chris Rees wrote: > > > > On 24 Apr 2011 10:18, "paranormal" wrote: > >> > >> On default installation musicpd I have error: > >> > >> > >> Apr 18 09:50:05 ---hostname-- mpd: avahi: Failed to create client: > >> Daemon not running > >> Apr 18 09:50:06 ---hostname-- avahi-daemon[1574]: WARNING: No NSS > >> support for mDNS detected, consider installing nss-mdns! > >> Apr 18 09:50:09 ---hostname-- wpa_supplicant[448]: > >> CTRL-EVENT-SCAN-RESULTS > >> > >> Because musicpd start early avahi. After I add > >> to /usr/local/etc/rc.d/musicpd this: > >> > >> # > >> # PROVIDE: musicpd > >> -# REQUIRE: mixer LOGIN avahi_daemon > >> +# REQUIRE: mixer LOGIN > >> # KEYWORD: shutdown > >> > >> > >> I have start musicpd without error. > >> Apr 23 18:06:53 ---hostname-- mpd: avahi: Service 'Music Player' > >> successfully established. > >> > >> I not find how build musicpd without avahi from ports. > >> > >> > > > > I'll have a look later. For future reference, please CC maintainers whe= n you > > have a question about a port, makes it easier to see! Do a make -V > > MAINTAINER in the port directory. > > > > Thanks for your suggested fix, > > >=20 > Please test the fix I've knocked together [1], see if it works for > you. You can now choose to compile with or without avahi support -- > pick your poison. >=20 > Avahi's compiling for me now, so I'll let you know if it works when I'm d= one. >=20 > Chris >=20 > [1] http://www.bayofrum.net/~crees/patches/musicpd-avahi.diff --=-+QGiNg0Inob8SxEJkgME Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAABAgAGBQJNtHQLAAoJEK5aDkRw5y5METAP/2DnKawob8d/x6uubnYqT8Wv A3tp0rpHrhBbYvaLRWLc3uVOLYx3b4E1O5rhZIX/2wVKAG4ancfdX+5iYXmkVO1E L4gxVf8VoqBzv9hFc/B+Ha/6wkSTN8vC+HQORS+hKwW1gYdHjePtLC4leCwvlAq2 j+KmirTA5uaoOF1Z9J63KE0dlcYkoUnMUIKnY/H9UFIK6kGrNFgoi7tGAnY0PMdE xyTszLr6kZVLSJlJ6K6ea8xPGnAXWZmu9GOhPoadN0Ox71ppUzDVrdL6y/wtCYU+ xtjglne3KBc3sfqcMriR1eIYroPHX3dKL1kzCupExgWpvTjrFeKbrVFD0aW4qV11 hOESCgaEOgltPmivc780T4VgWbSGWCvOCBzDrcU9594FoqwJhqB+SdO/FThiRdhI F5+D2aiP7VwzY5Y3I3LH6AsIFDVtfQPaPFFf5O7wgoqeJT9DxWdXBOztd6LQPKuR oaOhtiCQDvIHpQEg0vmxVzcx9VXJUoi+CXZOT5YPjsPECh70hPC5N2ywHQc4/8Iy xs55IxWIOulIKwbONnUmU28ua59jF0a+34QHbuMW2gWQEIGBydCNVfIZSjb9FmiA 1fIHspHvV367Kgxz0TdodHOJyMssGzw38HUzw46+5bQm1SwYtUrmLccPzVDvV8fP tXHSH03vWvxhEy4p9jad =rTt3 -----END PGP SIGNATURE----- --=-+QGiNg0Inob8SxEJkgME-- From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 20:14:25 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0992106566C for ; Sun, 24 Apr 2011 20:14:25 +0000 (UTC) (envelope-from hirner@bitfire.at) Received: from wurd.dev001.net (wurd.dev001.net [IPv6:2a01:4f8:120:9162::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5DB688FC1F for ; Sun, 24 Apr 2011 20:14:25 +0000 (UTC) Received: by wurd.dev001.net (Postfix, from userid 65534) id E2436188AF; Sun, 24 Apr 2011 22:14:23 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on wurd.dev001.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.1 Received: from [10.0.0.11] (d83-191-117-31.cust.tele2.at [83.191.117.31]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hirner@bitfire.at) by wurd.dev001.net (Postfix) with ESMTPSA id 31E2C188A8 for ; Sun, 24 Apr 2011 22:14:23 +0200 (CEST) From: Richard Hirner To: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" Organization: bitfire it services Date: Sun, 24 Apr 2011 22:14:22 +0200 Message-ID: <1303676062.2488.1.camel@gladsheim> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Content-Transfer-Encoding: 7bit Cc: Subject: TeamSpeak 3 PR #154453 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: info@bitfire.at List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 20:14:25 -0000 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/154453 Is there any way that I can help getting this into the current ports? Or do I just have to wait - maybe you can tell me how long? Thanks in advance, Richard From owner-freebsd-ports@FreeBSD.ORG Sun Apr 24 21:37:30 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF100106566C; Sun, 24 Apr 2011 21:37:30 +0000 (UTC) (envelope-from jandrese@vt.edu) Received: from vms173013pub.verizon.net (vms173013pub.verizon.net [206.46.173.13]) by mx1.freebsd.org (Postfix) with ESMTP id 911D98FC12; Sun, 24 Apr 2011 21:37:30 +0000 (UTC) Received: from escaflowne.ceyah.org ([unknown] [96.255.143.186]) by vms173013.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LK600NFJBY33980@vms173013.mailsrvcs.net>; Sun, 24 Apr 2011 15:37:17 -0500 (CDT) Date: Sun, 24 Apr 2011 16:37:15 -0400 From: Jason Andresen To: Bernhard Froehlich Message-id: <20110424163715.d3bf4ced.jandrese@vt.edu> In-reply-to: <430fcb25aefc374bf256e45e3151de15@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> X-Mailer: Sylpheed 3.1.0 (GTK+ 2.22.1; i386-portbld-freebsd8.2) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Cc: emulation@FreeBSD.org, ports@FreeBSD.org Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 21:37:30 -0000 On Fri, 22 Apr 2011 13:01:40 +0200 Bernhard Froehlich wrote: > It's about two months since the last call for testers and a lot of > bugfixing has happened since then. Not all of the reported problems were > FreeBSD related which is a good indication that we're not too far behind > the stability of the other hosts. So let's get it one once again. > > Last time I asked for some help and Baptiste Daroussin (bapt@) made the > classic mistake to respond. So all please welcome bapt to the FreeBSD > Vbox Team! Good news and bad news. The good news is that it appears to be stable with my WinXP Pro VM. Bad news is that enabling 3D acceleration still causes the VM to immediately crash when I try to start it. Also, the USB pass-through is closer to working. I have a couple of USB devices now that show up in the control panel, but they still don't appear in the Devices menu of the VM, nor does the VM have an inkling of their existence. -- \__/ Jason Andresen -- My opinions are my own. \__/19\__/1A\__/1B\__/ /21\ That's the thing about people who think they hate computers. /2C\ \__/ What they really hate is lousy programmers. __/3B\__/ /41\ -- Larry Niven and Jerry Pournelle in "Oath of Fealty" /4B\__/4C\ \__/51\__/52\__/53\__/54\__/55\__/56\__/57\__/58\__/59\__/5A\__/5B\__/ From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 11:06:06 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D8F21065670 for ; Mon, 25 Apr 2011 11:06:06 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0A62E8FC16 for ; Mon, 25 Apr 2011 11:06:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3PB66Xh083793 for ; Mon, 25 Apr 2011 11:06:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3PB65DM083791 for freebsd-ports@FreeBSD.org; Mon, 25 Apr 2011 11:06:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Apr 2011 11:06:05 GMT Message-Id: <201104251106.p3PB65DM083791@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD ports list Cc: Subject: Current unassigned ports problem reports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 11:06:06 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/156639 [PATCH] www/free-sa-devel: update to 2.0.0b4 o ports/156635 Change maintainer of "net/howl" port f ports/156629 [patch] sysutils/puppet patch to use PACKAGEROOT inste o ports/156623 [ports] [patch] fix databases/p5-DBD-cego from a linki o ports/156622 [maintainer] [patch] editors/texmacs Update to 1.0.7.1 o ports/156620 [new port] chinese/bug5 o ports/156619 [maintainer update] converters/bsdconv to 4.5 o ports/156618 Port update: games/searchandrescue o ports/156617 Port update: games/searchandrescue-data o ports/156616 New port: sysutils/aird Handles Apple IR receiver butt o ports/156615 Please update sysutils/fusefs-ntfs o ports/156608 [patch] port net-ngmt/nagvis update to version 1.5.9 o ports/156595 New port: www/httpsqs - a Simple Queue Service o ports/156590 games/KnightCap: coeffs.dat: No such file or directory o ports/156588 games/KnightCap: warning: "INFINITY" redefined o ports/156577 Upgrade of graphics/netpbm-10.26.64_4 to netpbm-10.35. f ports/156555 [PATCH] net-mgmt/nagiosql: update to 3.1.1 (superseed f ports/156553 [PATCH] net-mgmt/nagiosql: update to 3.1.1 o ports/156548 ports/mail/exmh2 uses old Tcl/Tk 8.4, not default vers o ports/156547 relayd exits when disabling and enabling hosts o ports/156544 [PATCH] x11/rxvt-devel: don't crash on paste from non- o ports/156542 [PATCH] x11/rxvt: don't crash on paste from non-ICCCM o ports/156541 [MAINTAINER] Upgrade lang/gnat-aux to release version o ports/156539 [NEW PORT] print/frescobaldi: A music score editor for o ports/156535 New port: games/fairymax o ports/156518 [maintainer] mail/opendkim update to 2.3.2 o ports/156516 Update port: graphics/yed: new version 3.7 o ports/156497 [maintainer-update] devel/eclipse-eclemma 1.5.1 to 1.5 o ports/156495 [NEW PORT] audio/mscore: MuseScore music notation prog o ports/156492 Multiple versions of Perl not supported f ports/156489 [PATCH] fix build of astro/qlandkartegt with astro/gps o ports/156478 [NEW PORT] net/mkntpwd: A utility to create the Samba o ports/156473 [new port] textproc/ocaml-text - OCaml library to deal o ports/156472 [new port] devel/ocaml-react - OCaml library for react f ports/156471 [PATCH] devel/libchipcard: Update to 5.0.1test o ports/156466 Updated port: comms/esmska -- Program for sending SMS f ports/156443 databases/mysql-connector-java -- update to 5.1.15 f ports/156437 [PATCH] java/java3d: make it available for java/openjd o ports/156426 New ports: devel/libg19, devel/libg19draw - libs to he o ports/156415 [NEW PORT] net-im/py-hotot, Twitter and Identi.ca micr o ports/156413 [NEW PORT] print/latex-ltablex: Combines the features o ports/156412 New port: www/py-flask-gravatar Small extension for Fl o ports/156398 [NEW PORT] net/ssspl: A Simple Socks Server for Perl o ports/156378 mail/phplist port update o ports/156377 databases/mariadb: missing charsets support in port f ports/156376 [PATCH] graphics/optipng: update to 0.6.5 o ports/156362 New port: games/rftg Race for the Galaxy AI o ports/156343 multimedia/xbmc 10.1_1 mp3 playback problem - CALSADir o ports/156341 security/barnyard2: sguil-sensor port relies on barnya o ports/156331 [patch] math/parmetis -- support (optional) build agai o ports/156316 [maintainer update] databases/sqldeveloper version upd o ports/156313 [patch][new port] astro/gkrellsun2 (Gkrellm2 Plugin) o ports/156307 [new port] math/ocamlsgl -- an ocaml interface for the o ports/156304 [maintainer update] net-mgmt/noc: update from 0.6.2 to o ports/156299 graphics/mupdf is still marked vulnerable o ports/156291 New port: audio/pure-audio - a digital audio interface o ports/156289 New port: graphics/pure-gl - Pure language interface t o ports/156265 [New Port] graphics/fotoxx, image editor and collectio o ports/156255 New port: x11-themes/nimbus GTK+ 2.x engine from the O o ports/156253 [patch] Update devel/boost-* from 1.45 to 1.46.1 o ports/156252 New port: devel/radar Opensource tools to disasm, debu o ports/156189 [new port] mail/muttils: python utilities for console f ports/156176 [patch] multimedia/libva: update to 1.0.12 o ports/156173 [patch] security/nettle update to 2.1 f ports/156171 port multimedia/mplayer patch-libao2-ao_oss.c is incor o ports/156161 [NEW PORT] devel/serdisplib: Library to drive graphica o ports/156143 New port: devel/arduino-mk: Build Arduino sketches fro f ports/156140 security/dradis: Update Dradis Framework from 2.6.0 to o ports/156119 x11-fonts/font-manager: ignore a problem caused by the o ports/156112 [NEW PORT] audio/linux-f10-pulseaudio-libs: Libraries o ports/156103 new ports: lots of bindings for the Pure language (tex o ports/156085 Update of cad/linux-eagle5 to the most recent version o ports/156075 [PATCH] graphics/openfst: [SUMMARIZE CHANGES] f ports/156034 print/lyx-devel spell checking with enchant does not w o ports/156002 New port: sysutils/pefs-kmod kernel level stacked cryp f ports/155941 mwserv library support is not included in nepenthes.co f ports/155931 [patch] sysutils/arcconf: update to v6_50_18771 f ports/155898 Update port devel/libthai o ports/155875 hungarian/hunspell misfiled under "ports/hungarian" o ports/155788 ports security/cfsd startup -- multiple problems o ports/155779 [PATCH] mail/policyd2: fix RC script f ports/155766 Vendor update: net/kvirc o ports/155763 update of mail/phplist to version 2.10.13 f ports/155750 www/p5-RT-Authen-ExternalAuth stopped working after up f ports/155697 ports-mgmt/pkg_replace doesn't want to replace java/op f ports/155655 [patch] science/meep Add Option to support MPI build f ports/155595 [PATCH] lang/guile: update to 1.8.8 o ports/155593 lang/mpd .16.1 ignores embedded cue sheets in FLAC fil f ports/155592 polish/ekg, after polish/libgadu update, contacts are f ports/155563 net/tucan: update to 0.3.10 o ports/155547 java/jboss 5 port build failure f ports/155545 Updating port multimedia/mediainfo to 0.7.42 o ports/155538 new port devel/radlib radlib developer library. Event- o ports/155525 [MAINTAINER] games/assaultcube: fixes and additions o ports/155509 Update port: net/xrdp update to current cvs version an f ports/155469 [patch] science/meep missing build dependency gsed o ports/155456 security/openssh-portable fails to compile with LPK en o ports/155417 [patch] www/nspluginwrapper: NSPlugin Viewer WARNING: o ports/155413 devel/pwlib fails to install f ports/155404 [PATCH] mail/mutt-devel: doesn't build in presence of f ports/155393 [PATCH] www/speedtest-mini: update to 2.1.8 f ports/155356 audio/xwave changed master site o ports/155344 New port: irc/inspircd12 f ports/155306 multimedia/openshot doesn't work o ports/155225 plz split antlr2 and antlr3 ports. not update antlr2 - f ports/155200 [UPDATE] devel/libchipcard: Update to 5.0.0, remove de f ports/155170 [update] www/ocaml-net to 3.2.1 o ports/155166 update deskutils/org-mode.el to 7.4 f ports/155143 /usr/ports/irc/unreal - Unreal IRCD runs as root by d f ports/155120 Update of port devel/php-libawl o ports/155116 new port: devel/antlr2-python-runtime, ANTLR v2 python f ports/155115 devel/doxygen: dependancy loop o ports/155105 Port science/vis5d+ does not build. o ports/155070 NEW PORT: games/CastleVox - new fast strategy board ga o ports/155064 New port: devel/stringtemplate, a java lib for text fo o ports/155063 Port update: devel/antlrworks a ports/155062 Port update: devel/antlr o ports/154995 [NEW PORT] audio/umurmur: Minimalistic Murmur (Mumble f ports/154973 [PATCH] security/ike: fix plist when QTGUI=off, respec o ports/154942 net/scribe: rc.d/thrift starts no matter what the rc.c f ports/154902 [patch] Port devel/libedit: added libedit.pc for gnome o ports/154869 [maintainer] mail/mimedefang update to latest version f ports/154765 [NEW PORT] games/ghost++: Warcraft 3 game hosting bot o ports/154730 security/openssh-portable is 5.2 f ports/154719 [PATCH] net/netdude update to 0.5.1 (incl. libnetdude o ports/154711 security/heimdal: kadmin: hdb_open: hdb_open failed in f ports/154682 net/iaxmodem: add rc script for running more than 1 ia o ports/154548 textproc/pootle: Pootle's rc.d script don't take into f ports/154546 update port: games/gemrb to version 0.6.3 o ports/154453 Rewritten port: audio/teamspeak_server f ports/154431 [patch] ports/Tools/scripts: python scripts use bad sh o ports/154401 New port: www/jetty7 - newer fork by Eclipse/Codehaus o ports/154285 [NEW PORT] java/netty: Java NIO client server framewor o ports/154254 [patch] asmail imap login broken with gmail at al. f ports/154217 New port: ports-mgmt/portsreinstall o ports/154202 New port: security/scannedonly - A Samba VFS virus sca f ports/154194 net/freeswitch: update portversion and remove portrevi o ports/154031 New port: audio/shoutcast2: SHOUTcast Distributed Netw o ports/153926 New port net/freeswitch-snapshot o ports/153810 [PATCH] Fix usb_interrupt_read() in devel/libusb for f f ports/153733 [patch] emulators/visualboyadvance-m: problem with joy o ports/153715 net/freeradius: FreeRADIUS exiting with Signal 11 on F f ports/153645 Update ports: emulators/mame update to v0.141 f ports/153622 [patch] sysutils/jfbterm: improve TERMCAP option f ports/153612 Update devel/arm-elf-binutils to version 2.17 f ports/153607 Update devel/djgpp-binutils to version 2.17 o ports/153601 New port: security/msktutil Active Directory keytab ma o ports/153503 Patch to add PostgreSQL health check to net/haproxy o ports/153473 [patch] mail/courier port upgrade from 0.63.0 to 0.65. o ports/153452 New port: science/py-ws2300 A driver for the LaCrosse o ports/153429 [patch] Fix explicite uses of unzip in ports f ports/153425 [PATCH] www/limesurvey: Added a switch to use PostgreS o ports/153422 [NEW PORT] databases/memcacheq-0.2.0: Simple queue ser o ports/153379 [PATCH] www/hastymail2 add options to add dependencies f ports/153287 [PATCH] net-mgmt/ndpmon: [SUMMARIZE CHANGES] o ports/153263 [NEW PORT] databases/percona-server: Multithreaded SQL f ports/153251 www/drush is out of date f ports/153148 change port: deskutils/x-tile A tiling application for o ports/153130 sysutils/k3b: problem with k3b and mounting ntfs with o ports/152982 [patch] net/nss_ldap, ignore option nss_initgroups_ign o ports/152958 The port of www/mnogosearch 3.3.10 is using an out-of- f ports/152915 russian/xmms v. 1.2.11_12 don't see cdinfo and tag's i f ports/152669 no work innodb (databases/mariadb) o ports/152467 [new port] net/openafs port o ports/152453 textproc/urlview port should install gecko.sh optional o ports/152376 New port: audio/lastfmsubmitd f ports/152304 sysutils/fcron: illegal instruction 4 o ports/152236 [patch] x11/slim: Enable pam support, add hald and dbu s ports/152195 [PATCH] deskutils/pinot update to xapian-core 1.2.3 f ports/152192 [PATCH] databases/xapian-bindings update to 1.2.3 o ports/152191 [PATCH] databases/xapian-core update to 1.2.3 o ports/152186 [NEW PORT] lang/python-doc-text: Documentation for the o ports/152175 New port: lang/javascript-v8 Google's open source Java f ports/152152 math/polymake: Port upgrade request o ports/152118 New port: deskutils/linux-tahometer A worktime trackin o ports/152109 New port: x11/keylaunch2 A fork of keylaunch that a o ports/152082 [NEW PORT] www/encode-explorer: A PHP script to browse f ports/152045 New port: www/links-hacked browser with tricks for tab o ports/152006 New Port: archivers/unzip-iconv: Slave port of unzip w o ports/151973 New port: security/arpCounterattack -- Detects and rem f ports/151930 [PATCH] net-mgmt/netams links to libmysqlclient/libpq o ports/151837 [patch] sysutils/bsdstats : does honor BATCH when inst f ports/151783 mail/fetchmail: rc.d script broken in case of MDA use f ports/151777 deskutils/xfce4-volstatus-icon Segmentation fault and f ports/151774 [new port] sysutils/pprotectd o ports/151747 new port: emulators/wine-fbsd64: request for (a variat f ports/151689 dns/rbldnsd does not use preassigned UID/GIDs f ports/151637 Update port: security/maia Much needed updates for Per o ports/151572 The first start of net/tucan failed because it can't w o ports/151467 New port: sysutils/autojump acts as a complement to cd f ports/151431 Update to include ZFS module in sysutils/grub2-1.98 f ports/151296 [patch] ports/sysutils/fusefs-kmod build fails: MNT_NF o ports/150883 Ports games/openastromenace won't compile on 64 bit f ports/150783 mail/qpopper: fails to configure ocasionally o ports/150542 [new port]: sysutils/createrepo o ports/150541 [new port] sysutils/yum - Installer/updater for rpm o ports/150493 Update for: security/openssh-portable port from 5.2p1 o ports/150425 www/squid31: rc.d/squid's squid_fib setting ineffectiv o ports/150361 [patch] provide script to bind with nautilus for multi f ports/150316 new port: net/neatx o ports/150287 [patch] Segfault: games/spider crashes after 51 moves f ports/150235 sysutils/smartmontools build system bug o ports/150194 There is no startup script for databases/cassandra f ports/150169 www/havp: Assertion failed: file llvm/lib/System/Mutex o ports/150086 [NEW PORT] net-im/tkabber-plugins-devel: External Plug f ports/149947 [NEW PORT] devel/smartCVS, a powerful graphical CVS cl o ports/149564 patch for various games/ adding appropriate LICENSEs t o ports/149538 sysutils/fusefs-ntfs panic on writte on 8.1 f ports/148871 bad packages: p5-XML-Parser-2.36_1 p5-XML-SAX-Expat-0. o ports/148605 security/ipsec-tools rc.d/racoon startup script fails o ports/148415 new port: devel/libsysinfo, GNU libc's sysinfo port fo f ports/148027 New port: graphics/ramenhdr, node based video composit f ports/147943 New port: net/radsecproxy Radsecproxy is a generic RAD o ports/147847 audio/zynaddsubfx mxml error when opening instruments s ports/147829 Improved net/ucarp startup script: multiple VHID and F o ports/147553 NEW port: graphics/VisualizationLibrary s ports/147169 bsd.ruby.mk: Adding GEM_ARGS f ports/145966 port devel/pwlib fails to build: cast error: patch att o ports/144597 security/openssh-portable fails to compile with KERBER f ports/143938 [NEW PORTS] textproc/linux-f10-ibus-qt et al.: Linux v o ports/143566 sysutils/diskcheckd runs constantly when using gmirror o ports/142824 [patch] security/openssh-portable: add VersionAddendum f ports/139203 sysutils/freebsd-snapshot more careful patch not depen o ports/137378 Advisory locks fail with ports/security/cfs on FreeBSD o ports/133563 security/cfs rc script needs "mntudp" option on 8-CURR o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs o ports/122333 net/arping - patch to lookup for interface and src ip, s ports/57498 HEIMDAL_HOME should be defined in src or ports Makefil 228 problems total. From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 11:15:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73075106564A for ; Mon, 25 Apr 2011 11:15:56 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.49.45]) by mx1.freebsd.org (Postfix) with ESMTP id 503B98FC1A for ; Mon, 25 Apr 2011 11:15:55 +0000 (UTC) Received: by syn.atarininja.org (Postfix, from userid 1001) id 8E2995C3A; Mon, 25 Apr 2011 07:16:38 -0400 (EDT) Date: Mon, 25 Apr 2011 07:16:38 -0400 From: Wesley Shields To: Mickey Harvey Message-ID: <20110425111638.GA41897@atarininja.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org Subject: Re: on boot starting jails hangs X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 11:15:56 -0000 On Fri, Apr 22, 2011 at 09:32:13AM -0700, Mickey Harvey wrote: > When I boot up my host rc hangs at "starting jails:" indefinitely. If i > Control^C during the hang boot continues as usual so I login ,run jls and > the jail appears to have started correctly. I can login to the jail as usual > using "jexec 1 sh". I'm using 8.2-RELEASE i386 on a VirtualBox VM. My rc is > set up as follows: > > ifconfig_em0="DHCP" > ifconfig_em0_alias0="10.0.2.16 netmask 255.255.255.255" > jail_enable="YES" > jail_list="www" > jail_www_rootdir="/usr/local/jails/www" > jail_www_hostname="www" > jail_www_ip="10.0.2.16" > jail_www_devfs_enable="YES" It's most likely something inside the jail failing to start properly. My money is on sendmail trying to get a reverse lookup completed. Try disabling sendmail entirely and see if the jail starts properly. -- WXS From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 14:02:52 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A3FF106566C; Mon, 25 Apr 2011 14:02:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id A82238FC12; Mon, 25 Apr 2011 14:02:51 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3PE2G0A039637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Apr 2011 17:02:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3PE2GuR036744; Mon, 25 Apr 2011 17:02:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3PE2Gk7036743; Mon, 25 Apr 2011 17:02:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Apr 2011 17:02:16 +0300 From: Kostik Belousov To: current@freebsd.org Message-ID: <20110425140216.GI48734@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LFN/h9p3ZzIorjyq" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: ports@freebsd.org Subject: NX stacks on amd64 and powerpc X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 14:02:52 -0000 --LFN/h9p3ZzIorjyq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I added a support for non-executable stacks on amd64 and PowerPC architectures some time ago, but did not enabled it. Passed time allowed to fix some bugs in the implementation, and I consider it would be good to have NX stacks enabled for architectures that support it. I plan to commit the following knob twiddle in approximately a week. Some ports, if any, that erronously handle PT_GNU_STACK phdr may break. Anybody interested should and could test the change before the commit, by setting sysctl kern.elf64.nxstack and kern.elf32.nxstack to 1. diff --git a/sys/kern/imgact_elf.c b/sys/kern/imgact_elf.c index b41741a..7358e40 100644 --- a/sys/kern/imgact_elf.c +++ b/sys/kern/imgact_elf.c @@ -116,7 +115,12 @@ static int elf_legacy_coredump =3D 0; SYSCTL_INT(_debug, OID_AUTO, __elfN(legacy_coredump), CTLFLAG_RW,=20 &elf_legacy_coredump, 0, ""); =20 -static int __elfN(nxstack) =3D 0; +static int __elfN(nxstack) =3D +#if defined(__amd64__) || defined(__powerpc__) /* both 64 and 32 bit */ + 1; +#else + 0; +#endif SYSCTL_INT(__CONCAT(_kern_elf, __ELF_WORD_SIZE), OID_AUTO, nxstack, CTLFLAG_RW, &__elfN(nxstack), 0, __XSTRING(__CONCAT(ELF, __ELF_WORD_SIZE)) ": enable non-executable sta= ck"); --LFN/h9p3ZzIorjyq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk21fuUACgkQC3+MBN1Mb4jAfACfdORTV/jFy9b2ue6EugbyLRf1 zDMAniPXcyuURzmVw/5P/Yryq8BfotQc =kMuV -----END PGP SIGNATURE----- --LFN/h9p3ZzIorjyq-- From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 16:42:48 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFADF1065672; Mon, 25 Apr 2011 16:42:48 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 4AF738FC24; Mon, 25 Apr 2011 16:42:48 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 0C1B16; Mon, 25 Apr 2011 18:42:47 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Mon, 25 Apr 2011 18:42:47 +0200 From: Bernhard Froehlich To: Jason Andresen In-Reply-To: <20110424163715.d3bf4ced.jandrese@vt.edu> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <20110424163715.d3bf4ced.jandrese@vt.edu> Message-ID: <45532902d1937774f08aef5c0ad926e2@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0207.4DB5A487.003B,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: emulation@FreeBSD.org, ports@FreeBSD.org Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 16:42:48 -0000 On Sun, 24 Apr 2011 16:37:15 -0400, Jason Andresen wrote: > On Fri, 22 Apr 2011 13:01:40 +0200 > Bernhard Froehlich wrote: > >> It's about two months since the last call for testers and a lot of >> bugfixing has happened since then. Not all of the reported problems were >> FreeBSD related which is a good indication that we're not too far behind >> the stability of the other hosts. So let's get it one once again. >> >> Last time I asked for some help and Baptiste Daroussin (bapt@) made the >> classic mistake to respond. So all please welcome bapt to the FreeBSD >> Vbox Team! > > Good news and bad news. The good news is that it appears to be > stable with my WinXP Pro VM. Bad news is that enabling 3D > acceleration still causes the VM to immediately crash when I try to > start it. Please try to get a coredump and stacktrace. You need to have the DEBUG option enabled or use the binary packages and set sysctl kern.sugid_coredump=1 first to also get coredumps for suid binaries like VirtualBox is. Once you have a core file please run "gdb /usr/local/lib/virtualbox/VirtualBox your_corefile.core" and send me the output of "bt full". -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 19:44:14 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6008106564A for ; Mon, 25 Apr 2011 19:44:14 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from ifdnrg29.ifdnrg.com (outbound.ifdnrg.com [193.200.98.138]) by mx1.freebsd.org (Postfix) with ESMTP id 554C38FC0C for ; Mon, 25 Apr 2011 19:44:13 +0000 (UTC) Received: from [192.168.1.99] (188-221-77-161.zone12.bethere.co.uk [188.221.77.161]) (authenticated bits=0) by ifdnrg29.ifdnrg.com (8.14.4/8.14.4) with ESMTP id p3PJPnFH069238; Mon, 25 Apr 2011 20:25:49 +0100 (BST) (envelope-from paul@ifdnrg.com) Message-ID: <4DB5CABD.8010803@ifdnrg.com> Date: Mon, 25 Apr 2011 20:25:49 +0100 From: Paul Macdonald User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svyatoslav.lempert@gmail.com Subject: ioncube checksum mismatch X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 19:44:14 -0000 Hi, experienced over the past few days, (with updated portstree) fetch: http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_fre_8_x86-64.tar.gz: size mismatch: expected 3157148, actual 3157150 => Attempting to fetch http://ls.fvds.ru/ioncube/4.0.8/ioncube_loaders_fre_8_x86-64.tar.gz ===> License check disabled, port has not defined LICENSE => SHA256 Checksum mismatch for ioncube_loaders_fre_8_x86-64.tar.gz. ===> Giving up on fetching files: ioncube_loaders_fre_8_x86-64.tar.gz Make sure the Makefile and distinfo file (/usr/ports/devel/ioncube/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** Error code 1 best regards Paul. -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07534206249 e: paul@ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ------------------------- From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 22:05:06 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ED6E106566C for ; Mon, 25 Apr 2011 22:05:06 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.freebsd.org (Postfix) with ESMTP id 2D78B8FC12 for ; Mon, 25 Apr 2011 22:05:05 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p3PM4p7J021507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 08:04:52 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p3PM4op4024692; Tue, 26 Apr 2011 08:04:50 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p3PM4lZG024686; Tue, 26 Apr 2011 08:04:47 +1000 (EST) (envelope-from peter) Date: Tue, 26 Apr 2011 08:04:47 +1000 From: Peter Jeremy To: freebsd-ports@freebsd.org Message-ID: <20110425220447.GE10901@server.vk2pj.dyndns.org> References: <20110422114116.GZ1553@albert.catwhisker.org> <20110422122006.GA1682@elch.exwg.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9l24NVCWtSuIVIod" Content-Disposition: inline In-Reply-To: <20110422122006.GA1682@elch.exwg.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Christoph Moench-Tegeder , David Wolfskill Subject: Re: Errors during Upgrade netpbm-10.26.64_4 to netpbm-10.35.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 22:05:06 -0000 --9l24NVCWtSuIVIod Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Apr-22 14:20:06 +0200, Christoph Moench-Tegeder wrote: >THe current graphics/netpbm port does not compile if there's an older >version of netpbm installed - /usr/local/include/pm.h from the older >netpbm takes precedence over the port's lib/pm.h but misses some macros >(well, it's an upgrade...) as PM_GNU_PRINTF_ATTR(a, b) which then confuse >the compiler. Note that just deleting /usr/local/include/pm.h isn't enough to make netpbm-10.35.80_2 compile so there are more incompatibilities than that. >pkg_delete -f the old netpbm and re-install the port, worked for me. Followed by 'portmaster --check-depends' or equivalent to clean up the dangling dependencies. Since netpbm isn't solely a leaf port, I believe this warrants an entry in UPDATING. --=20 Peter Jeremy --9l24NVCWtSuIVIod Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk217/8ACgkQ/opHv/APuId1BgCfe+k8/5iStlD981hOShMsABho Dr8An3HK/YKqKgmliPejNBPHF4nG5aBG =FlJe -----END PGP SIGNATURE----- --9l24NVCWtSuIVIod-- From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 22:08:35 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 383E3106564A for ; Mon, 25 Apr 2011 22:08:35 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id CD96D14E3D5; Mon, 25 Apr 2011 22:08:34 +0000 (UTC) Message-ID: <4DB5F0E2.8010804@FreeBSD.org> Date: Mon, 25 Apr 2011 15:08:34 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: Peter Jeremy References: <20110422114116.GZ1553@albert.catwhisker.org> <20110422122006.GA1682@elch.exwg.net> <20110425220447.GE10901@server.vk2pj.dyndns.org> In-Reply-To: <20110425220447.GE10901@server.vk2pj.dyndns.org> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Christoph Moench-Tegeder , freebsd-ports@freebsd.org, David Wolfskill Subject: Re: Errors during Upgrade netpbm-10.26.64_4 to netpbm-10.35.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 22:08:35 -0000 On 04/25/2011 15:04, Peter Jeremy wrote: > On 2011-Apr-22 14:20:06 +0200, Christoph Moench-Tegeder wrote: >> pkg_delete -f the old netpbm and re-install the port, worked for me. > > Followed by 'portmaster --check-depends' or equivalent to clean up > the dangling dependencies. If you use portmaster to install it right after doing the pkg_delete it's not necessary to do --check-depends as a separate step, portmaster will do it after installing the new netpbm. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Apr 25 23:47:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16CAC106567B for ; Mon, 25 Apr 2011 23:47:47 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C5EFC8FC17 for ; Mon, 25 Apr 2011 23:47:46 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QEVVH-0000aI-Ty for freebsd-ports@freebsd.org; Tue, 26 Apr 2011 01:47:43 +0200 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 01:47:43 +0200 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 01:47:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: martinko Date: Tue, 26 Apr 2011 01:47:30 +0200 Lines: 13 Message-ID: <4DB60812.1000109@users.sf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.18) Gecko/20110424 SeaMonkey/2.0.13 Cc: freebsd-multimedia@FreeBSD.org, itetcu@FreeBSD.org Subject: expiration of net/skype ?! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 23:47:47 -0000 Hi all, So what is this deprecation and expiration of net/skype port please ?? I'm asking because I've been using it successfully for more than a year and installed it again just this weekend without any issue. And I've read in the mailing lists many others use it too. So why all that black-listing ? Should I copy the port to my home folder for future installations ? Or can I / we do something about keeping it in the ports tree ? I would surely appreciate if it could stay there. With regards, Martin From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 00:02:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FB641065672 for ; Tue, 26 Apr 2011 00:02:17 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id DC0A28FC15 for ; Tue, 26 Apr 2011 00:02:16 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QEVjK-0006tK-SF for freebsd-ports@freebsd.org; Tue, 26 Apr 2011 02:02:14 +0200 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 02:02:14 +0200 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 02:02:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: martinko Date: Tue, 26 Apr 2011 02:02:02 +0200 Lines: 37 Message-ID: References: <20110317091244.GA17060@lonesome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.18) Gecko/20110424 SeaMonkey/2.0.13 In-Reply-To: <20110317091244.GA17060@lonesome.com> Subject: Re: Deprecation campaign X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 00:02:17 -0000 Mark Linimon wrote: > For those that want to see the state of all this, you can check out > the following URL: > > http://portsmon.freebsd.org/portsconcordancefordeprecated.py > > In particular, the "interesting" entries for you may be the unmaintained > ports (e.g. maintainer = "ports@FreeBSD.org".) In some of the other > cases, the maintainer had already asked for the port to be deprecated > (e.g. obsolete versions of databases/postgresql, dns/bind, > emulators/linux_base, etc.) > > If you find that any of the ports on this list are ports that you use at > your site, please consider taking them over as maintainer. This would > help FreeBSD out. > > fwiw, an email version of this will go out on the 21st via a cronjob. > > Thanks. > > mcl I understand you want to remove a port if it does not build and there is no one (in long time) to fix it. However, deprecating because a dist file moved, while port may be perfectly functional, seems a bit too much, imho. I've just glanced at the list linked above and I've noticed a few ports I've used in (not that distant) past. So I believe there are still users of them out there. So why would we deny them using the ports if all it takes is publishing the port files somewhere ? And since FreeBSD has the infrastructure and resources I see no issue in providing parking for such distfiles, especially if we believe they are used by minority of users. Or is there something I miss here ? With regards, Martin From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 00:29:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A3BB1065678 for ; Tue, 26 Apr 2011 00:29:11 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id EC5128FC12 for ; Tue, 26 Apr 2011 00:29:10 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QEW94-0008Fg-Ph for freebsd-ports@freebsd.org; Tue, 26 Apr 2011 02:28:50 +0200 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 02:28:50 +0200 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Apr 2011 02:28:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: martinko Date: Tue, 26 Apr 2011 02:28:39 +0200 Lines: 9 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.18) Gecko/20110424 SeaMonkey/2.0.13 Subject: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 00:29:11 -0000 Ok, I skimmed through the list of deprecated ports and I identifed the following that I may be using or at least used in past and I could take over their maintenance to save them from death: graphics/gimp-greycstoration misc/wmweather sysutils/wmmemmon All of them have already distfiles mirrored on FreeBSD's FTP. M. From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 00:29:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74182106566B for ; Tue, 26 Apr 2011 00:29:23 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id 092348FC17 for ; Tue, 26 Apr 2011 00:29:22 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p3Q0TJuK022653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 10:29:20 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p3Q0THXH088228; Tue, 26 Apr 2011 10:29:17 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p3Q0THIo088227; Tue, 26 Apr 2011 10:29:17 +1000 (EST) (envelope-from peter) Date: Tue, 26 Apr 2011 10:29:16 +1000 From: Peter Jeremy To: martinko Message-ID: <20110426002916.GF10901@server.vk2pj.dyndns.org> References: <4DB60812.1000109@users.sf.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="A9z/3b/E4MkkD+7G" Content-Disposition: inline In-Reply-To: <4DB60812.1000109@users.sf.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-multimedia@freebsd.org, itetcu@freebsd.org, freebsd-ports@freebsd.org Subject: Re: expiration of net/skype ?! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 00:29:23 -0000 --A9z/3b/E4MkkD+7G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Apr-26 01:47:30 +0200, martinko wrote: >So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. --=20 Peter Jeremy --A9z/3b/E4MkkD+7G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk22EdwACgkQ/opHv/APuIdcdQCgjKlhPrWnNl9Pjxly4T7KyI4r lGsAoKnfLr4LpDvsPIqm7ShToOe4QPRL =4OXR -----END PGP SIGNATURE----- --A9z/3b/E4MkkD+7G-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 00:46:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51F66106566B for ; Tue, 26 Apr 2011 00:46:58 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.freebsd.org (Postfix) with ESMTP id DB78A8FC0C for ; Tue, 26 Apr 2011 00:46:57 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p3Q0ksIS032493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 10:46:55 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p3Q0koho009554; Tue, 26 Apr 2011 10:46:50 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p3Q0ko1Q009543; Tue, 26 Apr 2011 10:46:50 +1000 (EST) (envelope-from peter) Date: Tue, 26 Apr 2011 10:46:49 +1000 From: Peter Jeremy To: martinko Message-ID: <20110426004649.GG10901@server.vk2pj.dyndns.org> References: <20110317091244.GA17060@lonesome.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AGZzQgpsuUlWC1xT" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org Subject: Re: Deprecation campaign X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 00:46:58 -0000 --AGZzQgpsuUlWC1xT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Apr-26 02:02:02 +0200, martinko wrote: >I understand you want to remove a port if it does not build and there is= =20 >no one (in long time) to fix it. However, deprecating because a dist=20 >file moved, while port may be perfectly functional, seems a bit too=20 >much, imho. For these ports, the port as it stands does not fetch. Someone needs to update the port with the new distfile location - this is the responsibility of the port's maintainer. If a port remains broken for an extended period, it indicates that no-one cares about it any longer and therefore no-one should miss it if it's deleted. > So why would we deny them using the=20 >ports if all it takes is publishing the port files somewhere ? And=20 >since FreeBSD has the infrastructure and resources I see no issue in=20 >providing parking for such distfiles, especially if we believe they are=20 >used by minority of users. Or is there something I miss here ? Who do you see as responsible for doing this? Whilst the FreeBSD Project has resources for storing/distributing distfiles, it takes human effort to verify that the port's license allows the FreeBSD Project to host the distfile and to actually copy the distfile. That person also needs to distinguish between the cases: a) The port is up-to-date and the distfile has moved b) The project (and hence distfile) have been renamed c) The port is so out-of-date that the distfie has been removed by the vendor Whilst the effort required for a single port may not be great, the total effort to work through all the ports in this situation would be substantial. This is not the task of the port committers group. It's up to the port's users to come up with a maintainer - if none of a port's users are willing to put in the effort to ensure that the port remains usable, why should the FreeBSD Project expend scarce resources to offering that port? If there are ports on the deprecated list that you use, maybe it's up to you to step up and maintain them. --=20 Peter Jeremy --AGZzQgpsuUlWC1xT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk22FfkACgkQ/opHv/APuIedQQCcCpwM8DQ8nmTAYy/x+At3wp1j KhMAn2xm+z8o2p+3eEsLBxqWHuVUNG40 =tkAB -----END PGP SIGNATURE----- --AGZzQgpsuUlWC1xT-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 00:49:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 67BF11065674 for ; Tue, 26 Apr 2011 00:49:28 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 0C8B2163B5D; Tue, 26 Apr 2011 00:48:32 +0000 (UTC) Message-ID: <4DB6165F.1010806@FreeBSD.org> Date: Mon, 25 Apr 2011 17:48:31 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: martinko References: In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 00:49:28 -0000 On 04/25/2011 17:28, martinko wrote: > Ok, > I skimmed through the list of deprecated ports and I identifed the > following that I may be using or at least used in past and I could take > over their maintenance to save them from death: Generally by the time that a port has deteriorated to the point where the distfiles are gone, and it has no maintainer, it's usually a pretty good sign that it's time to move on. This isn't just because of the distfile issue. Every port in the tree consumes resources, whether it's for pointyhat runs, space on the package sites (including the mirrors), etc. They also consume time to deal with when they get broken by changes in the OS, etc. What we're trying to do here is to eliminate ports that are no longer useful. You might want to consider whether or not some of these can be replaced by different alternatives. > misc/wmweather Give misc/wmweather+ a try. It's actively developed and maintained. > sysutils/wmmemmon There are a million other dockapps that do similar jobs, and this one does not seem that special. :) As for the gimp thing that you mentioned, I don't know anything about it, but if you wish to become its maintainer the polite thing to do would be to provide resources to host its distfile(s). Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 01:57:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59873106566B for ; Tue, 26 Apr 2011 01:57:15 +0000 (UTC) (envelope-from mezz.freebsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id CDFAA8FC12 for ; Tue, 26 Apr 2011 01:57:14 +0000 (UTC) Received: by vxc34 with SMTP id 34so209778vxc.13 for ; Mon, 25 Apr 2011 18:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+qZPnFbE1DCEIuzL2q22mc0IHzmcrvph54O9pP9ayQE=; b=RaD5H8HCyWhZeNvJrbnrcmtTZvgG9uDxujmiFbakgqCin0aiHv1ErGqKX6e3BSWh4x Xnv7E+YSNy4BzLMkmUm5veKIVwH3sI0E8EDzScWDom13+LnRrSV/6zvTO8LMpS3nZ5jk cUHjwYbX5TqXrH6B/Y35rcb0gM0pfQ2OR/LqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rD7TO9RlY7TMr95IuaYGi/3xE8jeHwPZY2BqjeP+8CutRbz5mMMg+ttP6l6V3EU3VZ USqxJKnPZMLnfzqcqkpg92CxCUBPvnjlLqjpLmdcP1x9TnTaULygHrKyIZ6n6iuWgqP/ 2Z2QAmVa+YkCmHWFhcpJOzGL3vFo8Zzh7yEy0= MIME-Version: 1.0 Received: by 10.220.66.18 with SMTP id l18mr53862vci.105.1303783033758; Mon, 25 Apr 2011 18:57:13 -0700 (PDT) Received: by 10.220.180.2 with HTTP; Mon, 25 Apr 2011 18:57:13 -0700 (PDT) In-Reply-To: <4DB6165F.1010806@FreeBSD.org> References: <4DB6165F.1010806@FreeBSD.org> Date: Mon, 25 Apr 2011 20:57:13 -0500 Message-ID: From: Jeremy Messenger To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org, martinko Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 01:57:15 -0000 On Mon, Apr 25, 2011 at 7:48 PM, Doug Barton wrote: > On 04/25/2011 17:28, martinko wrote: >> >> Ok, >> I skimmed through the list of deprecated ports and I identifed the >> following that I may be using or at least used in past and I could take >> over their maintenance to save them from death: > > Generally by the time that a port has deteriorated to the point where the > distfiles are gone, and it has no maintainer, it's usually a pretty good > sign that it's time to move on. This isn't just because of the distfile > issue. Every port in the tree consumes resources, whether it's for pointy= hat > runs, space on the package sites (including the mirrors), etc. They also > consume time to deal with when they get broken by changes in the OS, etc. > What we're trying to do here is to eliminate ports that are no longer > useful. > > You might want to consider whether or not some of these can be replaced b= y > different alternatives. > >> misc/wmweather > > Give misc/wmweather+ a try. It's actively developed and maintained. > >> sysutils/wmmemmon > > There are a million other dockapps that do similar jobs, and this one doe= s > not seem that special. :) > > As for the gimp thing that you mentioned, I don't know anything about it, http://registry.gimp.org/node/137 "GREYCstoration has been discontinued, and is now replaced by the G'MIC project, which contains all the former GREYCstoration features, but also much much much more !" http://gmic.sourceforge.net/gimp.shtml (G'MIC project) Cheers, Mezz > but if you wish to become its maintainer the polite thing to do would be = to > provide resources to host its distfile(s). > > > Doug > > -- > > =A0 =A0 =A0 =A0Nothin' ever doesn't change, but nothin' changes much. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-- OK Go > > =A0 =A0 =A0 =A0Breadth of IT experience, and depth of knowledge in the DN= S. > =A0 =A0 =A0 =A0Yours for the right price. =A0:) =A0http://SupersetSolutio= ns.com/ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > --=20 mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 02:41:26 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27BB8106564A for ; Tue, 26 Apr 2011 02:41:26 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id D88A28FC08 for ; Tue, 26 Apr 2011 02:41:25 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta03.westchester.pa.mail.comcast.net with comcast id c2gM1g0060vyq2s532hSax; Tue, 26 Apr 2011 02:41:26 +0000 Received: from comcast.net ([98.203.142.76]) by omta05.westchester.pa.mail.comcast.net with comcast id c2hP1g01Q1f6R9u3R2hQLZ; Tue, 26 Apr 2011 02:41:25 +0000 Received: by comcast.net (sSMTP sendmail emulation); Mon, 25 Apr 2011 19:41:22 -0700 Date: Mon, 25 Apr 2011 19:41:22 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110426024122.GA38579@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB6165F.1010806@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4DB6165F.1010806@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 02:41:26 -0000 On Mon 25 Apr 2011 at 17:48:31 PDT Doug Barton wrote: >What we're trying to do here is to eliminate ports that are no longer >useful. If we had some popularity stats, it would be interesting to see where the unmaintained ports fall on the list. Unfortunately, bsdstats doesn't include this anymore. Maybe freshports could implement a voting system like the one at osx.iusethis.com? From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 04:55:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED8C8106564A for ; Tue, 26 Apr 2011 04:55:22 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [95.108.130.93]) by mx1.freebsd.org (Postfix) with ESMTP id 9E6C38FC16 for ; Tue, 26 Apr 2011 04:55:22 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward11.mail.yandex.net (Yandex) with ESMTP id DA3D8E80DE6; Tue, 26 Apr 2011 08:55:20 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1303793720; bh=LL8AuuEhVT/alsdJucVDEk9W1STZlmOB4TXtpw6vyHg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JC9ddH3iSFdLnQiEj+yoQ7z3DXUrX0KcStuHZdYLlAcR++KwbtQZWAjUG8gst9Ozk knRVccCSPr9jcxJmGu5ATXUvhHxT0TUdoNA/pGqjw1OJ64W3Wp6ELi0dG5Gjxd7SUs uI3a43nqSVDGWg+PIv3sokDgJk3fy8tlwQPO7NL0= Received: from smeshariki2.local (unknown [178.76.212.172]) by smtp11.mail.yandex.net (Yandex) with ESMTPSA id 9D5EF4CC0079; Tue, 26 Apr 2011 08:55:20 +0400 (MSD) Message-ID: <4DB64FC2.2060408@yandex.ru> Date: Tue, 26 Apr 2011 08:53:22 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.15) Gecko/20110425 Thunderbird/3.1.9 MIME-Version: 1.0 To: martinko References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Yandex-Spam: 1 Cc: freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 04:55:23 -0000 26.04.2011 04:28, martinko пишет: > Ok, > I skimmed through the list of deprecated ports and I identifed the following > that I may be using or at least used in past and I could take over their > maintenance to save them from death: > graphics/gimp-greycstoration Use graphics/gimp-gmic-plugin instead. Please see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/154596 for details. -- Regards, Ruslan From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 05:55:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1436106566C for ; Tue, 26 Apr 2011 05:55:22 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id C9AD18FC08 for ; Tue, 26 Apr 2011 05:55:22 +0000 (UTC) Received: from cpe-66-68-128-204.austin.res.rr.com ([66.68.128.204] helo=inferno.lab.lovett.com) by panix.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QEbF3-000606-Od; Tue, 26 Apr 2011 05:55:21 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Ade Lovett In-Reply-To: <20110426024122.GA38579@comcast.net> Date: Tue, 26 Apr 2011 00:55:10 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> To: Charlie Kester , FreeBSD Ports X-Mailer: Apple Mail (2.1084) Cc: Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 05:55:23 -0000 On Apr 25, 2011, at 21:41 , Charlie Kester wrote: > Maybe freshports could implement a voting system like the one at > osx.iusethis.com? "Voting" implies some kind of democracy. This may come as a shock to folks, but FreeBSD in general is in fact not = democratic. It's based around the concept of folks putting in their own = time to keep a part of the Project alive. Whether it's a device driver, some chunk of base userland, = ports//, or support for an entire architecture and/or release = of FreeBSD -- doesn't matter. Without at least a modicum of active = maintainership (hint: MAINTAINER=3D ports@FreeBSD.org is _not_ active) = then it will eventually fall by the wayside and die. For ports, there's a non-zero cost associated with each and every single = one in the tree. Directly, in terms of clusters trying to build = packages for the combination of supported releases and architectures, = and indirectly, in case of infrastructural changes affecting chunks of = the tree, when it comes to determining whether port breakage is a result = of said changes, or whether it was broken already. Generally speaking, such "dead" ports are marked DEPRECATED with a = sizable amount of time before being reaped. Honestly, I'd personally = prefer the variable to be named PUT_UP_OR_SHUT_UP (but that's just me). = The fact remains though, that that is _exactly_ what it is. If, in the = period between a port being marked DEPRECATED and it being removed from = the tree, and especially in the case of UNMAINTANED=3DYES (that'd be = ports@FreeBSD.org for those in the back), no-one steps up to (a) fix the = problem, (b) take maintainership and (c) _continue_ with maintainership. Well, in that case, the port does not _deserve_ to live. After all, = no-one cares about it. If they did, they'd take care of (a) thru (c) = above. -aDe From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 06:43:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF09D1065670; Tue, 26 Apr 2011 06:43:48 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from worf.ds9.tecnik93.com (worf.ds9.tecnik93.com [81.196.207.130]) by mx1.freebsd.org (Postfix) with ESMTP id 853948FC12; Tue, 26 Apr 2011 06:43:48 +0000 (UTC) Received: from User-PC (unknown [81.181.146.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by worf.ds9.tecnik93.com (Postfix) with ESMTPSA id 25E6A22C5513; Tue, 26 Apr 2011 09:43:46 +0300 (EEST) Date: Tue, 26 Apr 2011 09:43:43 +0300 From: Ion-Mihai Tetcu To: Peter Jeremy Message-Id: <20110426094343.765dbf41.itetcu@FreeBSD.org> In-Reply-To: <20110426002916.GF10901@server.vk2pj.dyndns.org> References: <4DB60812.1000109@users.sf.net> <20110426002916.GF10901@server.vk2pj.dyndns.org> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-multimedia@freebsd.org, itetcu@freebsd.org, freebsd-ports@freebsd.org, martinko Subject: Re: expiration of net/skype ?! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 06:43:49 -0000 On Tue, 26 Apr 2011 10:29:16 +1000 Peter Jeremy wrote: > On 2011-Apr-26 01:47:30 +0200, martinko wrote: > >So what is this deprecation and expiration of net/skype port please ?? > > Whilst the Skype port still works, the version of Skype referenced by > the port is no longer available and later versions of Skype do not > (currently) work on FreeBSD. My reading of the Skype license suggests > that the FreeBSD Project cannot host the distfile without an agreement > with Skype. This means that someone who doesn't currently have the > Skype distfile cannot install the Skype port. True, and we've kept it like this for a long time. I have asked people at skype to allow us to redistribute the distfile, but that's impossible for legal reasons (not theirs). > I believe work is underway to support the currently available version > of Skype. It is, and it's kinda workoing on HEAD plus some patches. One thing all of oyu could do is bug skype on their forums to provide an OSS version; I recently argued about that with their linux product manager, so more voices would help. -- Ion-Mihai Tetcu From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 09:00:18 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6A54106568D; Tue, 26 Apr 2011 09:00:18 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 223888FC13; Tue, 26 Apr 2011 09:00:13 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 319877; Tue, 26 Apr 2011 11:00:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Tue, 26 Apr 2011 11:00:09 +0200 From: Bernhard Froehlich To: Sergio de Almeida Lenzi In-Reply-To: <1303658983.36234.7.camel@z6000.lenzicasa> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> <1303658983.36234.7.camel@z6000.lenzicasa> Message-ID: <29f5c61fd03d55c5009a4c1c3a514b54@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0201.4DB68998.0268,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: emulation@FreeBSD.org, ports@FreeBSD.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 09:00:19 -0000 On Sun, 24 Apr 2011 12:29:43 -0300, Sergio de Almeida Lenzi wrote: > For me it is working... > running windows XP dnd linux over an old(4.0.2) image it is ok... > very stable... > > Only a problem remains (that is not still fixed): > it is the problem with the vnc in VBoxHeadless > the cursor is not in sync (the vnc cursor) is not > in sync with the XP cursor.. although the sync > is better (compared with 4.0.2 but is still out of sync)... > How to reproduce: > VBoxHeadless --vnc --vncport 5901 --startvm XPimg > then goto another machine and execute: > vncviewer x.x.x.x:5901, the system opens works but the > mouse cursor is not in sync... > > Question: Will there be a fix??? Don't know if that is a bug or a problem of the implementation. I would recommend waiting for the VNC extpack. -- Bernhard Fröhlich http://www.bluelife.at/ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 12:16:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FC76106566B for ; Tue, 26 Apr 2011 12:16:39 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id E45D98FC17 for ; Tue, 26 Apr 2011 12:16:38 +0000 (UTC) Received: by ywf7 with SMTP id 7so254494ywf.13 for ; Tue, 26 Apr 2011 05:16:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=WIZ9PK8CAGxsWWinoJi6nVQg2qzX6Fw0IF4CoForPSQ=; b=HY7a0kPgKFT/chtDVLgPIbvnFOlx4K4v4EP14kBtaXEWjEDipMzx3vsiP6fo3kzVPh IlH6Jw+ho//iCH5D60J+9Oj242tuWDK3SdGtoengkcGIzPN0Ij1XpTOniQtZvr8ddlBN uQoMEGQVua9jRufAO2jrZuqkYLnxAuK3L3M1A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=W8V3WMTSfE6TvHTyrNqVpUD5kOYnK97HHqCSP5JaWI6PbwmCZ+MaLOU2Wb7EUN8OuS kHswR6AQBsp/6U0qlHmSiWKk39YQZE/zWA7fqhDUshd8KbsRnApjT69Tk895FVw+B+Xh qAFysvhHZ5Hcwc6jcE1rMX1MwYVP1QPGfenWs= MIME-Version: 1.0 Received: by 10.101.99.18 with SMTP id b18mr439826anm.120.1303820197435; Tue, 26 Apr 2011 05:16:37 -0700 (PDT) Received: by 10.100.197.7 with HTTP; Tue, 26 Apr 2011 05:16:37 -0700 (PDT) In-Reply-To: References: <777868.6417.qm@web110513.mail.gq1.yahoo.com> <1302722172.4802.7.camel@mars> Date: Tue, 26 Apr 2011 13:16:37 +0100 Message-ID: From: "Sevan / Venture37" To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: OpenNMS link/port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 12:16:39 -0000 On 22 April 2011 17:31, Sevan / Venture37 wrote: > On 21 April 2011 17:40, Sevan / Venture37 wrote: >> I've shoved all the revisions of the port I created into a mercurial >> repo & pushed it up to bitbucket. >> https://bitbucket.org/sevan/opennms/overview > > Another repo for the unstable branch of OpenNMS > https://bitbucket.org/sevan/opennms-dev/overview > v1.8.11 port http://www.geeklan.co.uk/files/opennms/opennms-1811-freebsd-port.tgz v1.9.7 port http://www.geeklan.co.uk/files/opennms/opennms-dev-197-freebsd-port.tgz From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 16:47:37 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69261106566B for ; Tue, 26 Apr 2011 16:47:37 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 4E1D18FC13 for ; Tue, 26 Apr 2011 16:47:37 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta05.emeryville.ca.mail.comcast.net with comcast id cEpf1g00A1u4NiLA5GaSql; Tue, 26 Apr 2011 16:34:26 +0000 Received: from comcast.net ([98.203.142.76]) by omta21.emeryville.ca.mail.comcast.net with comcast id cGaQ1g00X1f6R9u8hGaRu0; Tue, 26 Apr 2011 16:34:26 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 09:34:24 -0700 Date: Tue, 26 Apr 2011 09:34:24 -0700 From: Charlie Kester To: FreeBSD Ports Message-ID: <20110426163424.GB38579@comcast.net> Mail-Followup-To: FreeBSD Ports References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 16:47:37 -0000 On Mon 25 Apr 2011 at 22:55:10 PDT Ade Lovett wrote: > >On Apr 25, 2011, at 21:41 , Charlie Kester wrote: >> Maybe freshports could implement a voting system like the one at >> osx.iusethis.com? > >"Voting" implies some kind of democracy. I just thought it might be useful to get some actual data to support the inference that an unmaintained port is likely to be an unused and therefore unneeded port. I have no objection to your argument that what gets done is what someone is willing to do. And I am sensitive to the fact that every port imposes some additional burden on the system. I'm all for cleaning out the cruft. I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of unmaintained ports and manually check them against the popularity ratings on a site like freshmeat. It's a bit of a leap to assume that a program that's popular on Linux will be as popular on BSD, but it's the best data we have for the time being. From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 17:23:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C7921065672 for ; Tue, 26 Apr 2011 17:23:38 +0000 (UTC) (envelope-from duchateau.olivier@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E0E638FC0A for ; Tue, 26 Apr 2011 17:23:37 +0000 (UTC) Received: by bwz12 with SMTP id 12so1022298bwz.13 for ; Tue, 26 Apr 2011 10:23:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=Li5H+JRwlvi+6c7fv3B3Lomr5b+/8Czw3YwyHRspz1c=; b=L2ZokquQw8A6+bbtEbn7+LH1a5+UMFdtqTsXwWqpUYhwwy4sqN4o+Swnvdd8XvLfat ZwGIIZ1SOqOvT6NWvrZOiILvZkH/B3YTu9G7VzUBY70ADRMvX+6ShoGIY0oNpKj3ugsP 7jkt9qfskQf8JS8Gc6mqI0TxbjPHBcTGGIgzQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=Mn9qs8AzNs0uikwvlrnOq92lYSBk/DtdFJANsRcVSSgt+Er8S74CpYuQifs77VuH3m aJ3pC1N8asoCCl/OySnmYjuf11KRcoA53CCIdOU9z8Ly8aVPhh/thZE4jZAdeyyX0OmM +Em5JxoeUOXBVodNjfOb4ILq3q2baMYIVrPHE= MIME-Version: 1.0 Received: by 10.204.154.194 with SMTP id p2mr948014bkw.58.1303838616532; Tue, 26 Apr 2011 10:23:36 -0700 (PDT) Received: by 10.204.118.9 with HTTP; Tue, 26 Apr 2011 10:23:36 -0700 (PDT) Date: Tue, 26 Apr 2011 19:23:36 +0200 Message-ID: From: Olivier Duchateau To: FreeBSD Ports ML Content-Type: text/plain; charset=ISO-8859-1 Cc: pav@freebsd.org Subject: Why archivers/thunar-archive plugin is broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 17:23:38 -0000 Hi, I noticed port, archivers/thunar-archive-plugin is marked as broken. I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. May I have log, please ? -- olivier From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 17:49:42 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E09471065670 for ; Tue, 26 Apr 2011 17:49:42 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from sup.oook.cz (sup.oook.cz [94.23.0.135]) by mx1.freebsd.org (Postfix) with ESMTP id 7E3E18FC12 for ; Tue, 26 Apr 2011 17:49:42 +0000 (UTC) Received: from [192.168.0.23] (ip-78-102-160-251.net.upcbroadband.cz [78.102.160.251]) (authenticated bits=0) by sup.oook.cz (8.14.4/8.14.4) with ESMTP id p3QHocKF022289; Tue, 26 Apr 2011 19:50:39 +0200 (CEST) (envelope-from pav@FreeBSD.org) From: Pav Lucistnik To: Olivier Duchateau In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-9Gu16XVP0M1O3KW/z9pq" Date: Tue, 26 Apr 2011 19:49:38 +0200 Message-ID: <1303840178.30113.3.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Scanned-By: MIMEDefang 2.68 on 94.23.0.135 X-Milter: Spamilter (Reciever: sup.oook.cz; Sender-ip: 78.102.160.251; Sender-helo: [192.168.0.23]; ) Cc: FreeBSD Ports ML Subject: Re: Why archivers/thunar-archive plugin is broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 17:49:43 -0000 --=-9Gu16XVP0M1O3KW/z9pq Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: quoted-printable Olivier Duchateau p=ED=B9e v =FAt 26. 04. 2011 v 19:23 +0200: > Hi, >=20 > I noticed port, archivers/thunar-archive-plugin is marked as broken. > I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. >=20 > May I have log, please ? Sure, http://portsmon.freebsd.org/portoverview.py?category=3D&portname=3Dthunar-a= rchive-plugin Missing dependency most probably. --=20 --=20 Pav Lucistnik Two sausages are in a frying pan. One says, "Geez, it's hot in here isn't it?" And the other one says, "Aaaaaah! A talking sausage!" --=-9Gu16XVP0M1O3KW/z9pq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk23Ba4ACgkQntdYP8FOsoJgtACeI6ZjX47asOMMecECs+oFnogu UfQAoIiIGi3Wg8lFaIJuRaJHWyfh0FnS =6LG0 -----END PGP SIGNATURE----- --=-9Gu16XVP0M1O3KW/z9pq-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 18:28:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB738106564A for ; Tue, 26 Apr 2011 18:28:58 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gw0-f68.google.com (mail-gw0-f68.google.com [74.125.83.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF688FC13 for ; Tue, 26 Apr 2011 18:28:58 +0000 (UTC) Received: by gwj19 with SMTP id 19so152448gwj.7 for ; Tue, 26 Apr 2011 11:28:57 -0700 (PDT) Received: by 10.90.8.34 with SMTP id 34mr1030869agh.9.1303841532277; Tue, 26 Apr 2011 11:12:12 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id s11sm1959201anm.40.2011.04.26.11.12.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 11:12:11 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QJsvY6BFgz2CG52 for ; Tue, 26 Apr 2011 14:12:09 -0400 (EDT) Date: Tue, 26 Apr 2011 14:12:09 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110426141209.0d07bccf@seibercom.net> In-Reply-To: <20110426163424.GB38579@comcast.net> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 18:28:58 -0000 On Tue, 26 Apr 2011 09:34:24 -0700 Charlie Kester articulated: > It's a bit of a leap to assume that a program that's popular on Linux > will be as popular on BSD, but it's the best data we have for the time > being. If you want to definitively ascertain the popularity of an application, just remove it from the ports structure and see how many users complain. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 18:43:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14D861065670 for ; Tue, 26 Apr 2011 18:43:21 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id CEC7C8FC08 for ; Tue, 26 Apr 2011 18:43:20 +0000 (UTC) Received: from c-24-22-230-24.hsd1.wa.comcast.net ([24.22.230.24] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QEnED-0004Tw-6L for freebsd-ports@freebsd.org; Tue, 26 Apr 2011 14:43:18 -0400 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Tue, 26 Apr 2011 11:43:15 -0700 Date: Tue, 26 Apr 2011 11:43:15 -0700 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20110426184315.GA2320@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <20110426141209.0d07bccf@seibercom.net> User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 18:43:21 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Jerry on Tuesday, 26 April 2011: > On Tue, 26 Apr 2011 09:34:24 -0700 > Charlie Kester articulated: >=20 > > It's a bit of a leap to assume that a program that's popular on Linux > > will be as popular on BSD, but it's the best data we have for the time > > being. >=20 > If you want to definitively ascertain the popularity of an application, > just remove it from the ports structure and see how many users complain. >=20 There could be quite a delay in that reaction -- it might not hit home until the port needs to be rebuilt. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJNtxJDAAoJEIpckszW26+RpHYIAMQ8XoMAjZ9U50Wxp0PcSiUD vqbTr2k1gf3GVlPPQTfTWo1aKh3mxoZ0baBZ0WJoO+n+iv/oIEqSGFBEw2TkuJJq ZzVXEpxvXgMH3aIrHCGVa/QX8ux+YjSbBIFoRCIwGmQ1lJyuu5Hv9YMjGX+MMdIv 17x4xfY6eXeqqN43yd9wT90Lz/HnT1cOM6t0vhGW5H4VEw8NSwPQzFwQLeS7hS+s 7E8RNxE7jkEIpazxHkXUiWLOZPXxxa/1Auoif4nuS21gAxhKVl6lZLELcc36swlE +xzjux3FRMQsmNIu1abTGotLZMT2N+1lKhxqAbv2bKA3TUM11NwW7iLu/lemqDc= =Qfxl -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 19:17:00 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33981106564A for ; Tue, 26 Apr 2011 19:17:00 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [95.108.130.92]) by mx1.freebsd.org (Postfix) with ESMTP id BD0958FC08 for ; Tue, 26 Apr 2011 19:16:59 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward14.mail.yandex.net (Yandex) with ESMTP id F260A1982129; Tue, 26 Apr 2011 23:16:57 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1303845418; bh=QBNMs1FBm+LzH44OGBFpULkW26OPgBjqA0h5i7Bnlw8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=I/kn4sMUihlq3sEWxpiPH3AnE2o+OhbuArpQTe2U0AbqXhRZqZKBwrwbGVIUbPiKQ P96RNVp/W43ICXDC98A775C+YnaE3B1Tg6WlUXw49wSud3hPhlUvgPJFVuXbli6sRN yBvlQC0JE/HYMnsJ5HA7avGUNEAXUNY6sBJm+9SU= Received: from smeshariki2.local (unknown [178.76.212.172]) by smtp11.mail.yandex.net (Yandex) with ESMTPSA id 9A4F64CC0033; Tue, 26 Apr 2011 23:16:57 +0400 (MSD) Message-ID: <4DB719B2.1090409@yandex.ru> Date: Tue, 26 Apr 2011 23:14:58 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.15) Gecko/20110425 Thunderbird/3.1.9 MIME-Version: 1.0 To: pav@FreeBSD.org References: <1303840178.30113.3.camel@hood.oook.cz> In-Reply-To: <1303840178.30113.3.camel@hood.oook.cz> Content-Type: multipart/mixed; boundary="------------010803070207020705090007" X-Yandex-Spam: 1 Cc: Olivier Duchateau , FreeBSD Ports ML Subject: Re: Why archivers/thunar-archive plugin is broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 19:17:00 -0000 This is a multi-part message in MIME format. --------------010803070207020705090007 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 26.04.2011 21:49, Pav Lucistnik пишет: > Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: >> Hi, >> >> I noticed port, archivers/thunar-archive-plugin is marked as broken. >> I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. >> >> May I have log, please ? > > Sure, > > http://portsmon.freebsd.org/portoverview.py?category=&portname=thunar-archive-plugin > > Missing dependency most probably. This patch should work. -- Regards, Ruslan --------------010803070207020705090007 Content-Type: text/plain; name="Makefile.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Makefile.txt" LS0tIE1ha2VmaWxlLm9yaWcJMjAxMS0wNC0yNiAwMTo1NTo1NS4wMDAwMDAwMDAgKzA0MDAK KysrIE1ha2VmaWxlCTIwMTEtMDQtMjYgMjM6MTM6MzAuMDAwMDAwMDAwICswNDAwCkBAIC0y Miw3ICsyMiw3IEBACiBVU0VfWEZDRT0JY29uZmlnZW52IGxpYmV4byB0aHVuYXIKIFVTRV9H RVRURVhUPQl5ZXMKIElOU1RBTExTX0lDT05TPQl5ZXMKLVVTRV9HTk9NRT0JZGVza3RvcGZp bGV1dGlscworVVNFX0dOT01FPQlkZXNrdG9wZmlsZXV0aWxzIGludGx0b29sCiBVU0VfR01B S0U9CXllcwogCiAuaW5jbHVkZSA8YnNkLnBvcnQubWs+Cg== --------------010803070207020705090007-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 20:10:44 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D6E0106564A; Tue, 26 Apr 2011 20:10:44 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4532B8FC0C; Tue, 26 Apr 2011 20:10:42 +0000 (UTC) Received: by ewy1 with SMTP id 1so425738ewy.13 for ; Tue, 26 Apr 2011 13:10:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=V+3iVq6Yyb5epd7YiYBCvEVd/2P6mK5lxj294sHNyNk=; b=n9/Ie8eD66iK7+mMEVxVnSLO9EjXr4iasUOLignVfns0XhKRKqHdNzcQxlxW4rZ+Xc 4lDHBaijbyP+9/xHnIdgAmgghnM+Oq0xPTW8+O9ISKfJ1sutxY/TEYzzu8x1bGVRoJwB 1OB47VEWy5Xj0BPmXRtCo+4RMCdYoa9/MV8UQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hVB0xnagGKJpnGyVF1cEU7/KWW9WFkfeZrkp++uitahQeETzP8YkPqO5yxEyKGJHsj 8BPXTe/00sAR52OtZb51MXR9lgQPjY+71Yk4OW29tBkWnAyO9L2FtQV3dTNvV67XFtto CpqU32RB7To8zgq3KAiCXl8DvG97JHnzgLmBE= MIME-Version: 1.0 Received: by 10.213.29.73 with SMTP id p9mr1849496ebc.149.1303846949815; Tue, 26 Apr 2011 12:42:29 -0700 (PDT) Received: by 10.213.35.70 with HTTP; Tue, 26 Apr 2011 12:42:29 -0700 (PDT) In-Reply-To: <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Date: Tue, 26 Apr 2011 15:42:29 -0400 Message-ID: From: Ryan Stone To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 20:10:44 -0000 On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich wrote: > On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: >> PBIs for PC-BSD are currently worked on and will hopefully be available >> in a few days. > > Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts > to provide the PBIs! > > PC-BSD 8.x 32bit: > http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi > ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi > > PC-BSD 8.x 64bit: > http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi > ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi > > > Feedback (positive and negative) from PC-BSD users is very welcome! > I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable to start any virtual machines(both pre-existing VMs or a new VM that I tried to create). I get the following error dialog: Failed to open a session for the virtual machine RELENG_8_amd64. Failed to load VMMR0.r0 (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED). Unknown error creating VM (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED). Details: Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882} From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 20:18:03 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C915310656F6; Tue, 26 Apr 2011 20:18:03 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 644198FC15; Tue, 26 Apr 2011 20:18:03 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 2AAE26; Tue, 26 Apr 2011 22:18:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 26 Apr 2011 22:18:03 +0200 From: Bernhard Froehlich To: Ryan Stone In-Reply-To: References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Message-ID: <4acc18c7c3c97bcb9052c7c13389216b@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.5.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0203.4DB7287A.00AD,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 20:18:03 -0000 On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote: > On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich > wrote: >> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: >>> PBIs for PC-BSD are currently worked on and will hopefully be available >>> in a few days. >> >> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts >> to provide the PBIs! >> >> PC-BSD 8.x 32bit: >> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi >> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi >> >> PC-BSD 8.x 64bit: >> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi >> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi >> >> >> Feedback (positive and negative) from PC-BSD users is very welcome! >> > > I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable > to start any virtual machines(both pre-existing VMs or a new VM that I > tried to create). I get the following error dialog: > > Failed to open a session for the virtual machine RELENG_8_amd64. > > Failed to load VMMR0.r0 > (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED). > > Unknown error creating VM > (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED). > > Details: > > Result Code: > NS_ERROR_FAILURE (0x80004005) > Component: > Console > Interface: > IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882} Yeah, thanks we already know. They added some strict hardening checks in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently rebuilding the PBIs with some modifications. That's exactly why we have call for testers so find such weird problems that nobody could think of. -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 20:32:36 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 398981065673 for ; Tue, 26 Apr 2011 20:32:36 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from sup.oook.cz (sup.oook.cz [94.23.0.135]) by mx1.freebsd.org (Postfix) with ESMTP id CC5E78FC12 for ; Tue, 26 Apr 2011 20:32:35 +0000 (UTC) Received: from [192.168.0.23] (ip-78-102-160-251.net.upcbroadband.cz [78.102.160.251]) (authenticated bits=0) by sup.oook.cz (8.14.4/8.14.4) with ESMTP id p3QKXUwE037137; Tue, 26 Apr 2011 22:33:32 +0200 (CEST) (envelope-from pav@FreeBSD.org) From: Pav Lucistnik To: Ruslan Mahmatkhanov In-Reply-To: <4DB719B2.1090409@yandex.ru> References: <1303840178.30113.3.camel@hood.oook.cz> <4DB719B2.1090409@yandex.ru> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-xs9klpMOoj7fSrx0ggwD" Date: Tue, 26 Apr 2011 22:32:29 +0200 Message-ID: <1303849950.78146.0.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Scanned-By: MIMEDefang 2.68 on 94.23.0.135 X-Milter: Spamilter (Reciever: sup.oook.cz; Sender-ip: 78.102.160.251; Sender-helo: [192.168.0.23]; ) Cc: Olivier Duchateau , FreeBSD Ports ML Subject: Re: Why archivers/thunar-archive plugin is broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 20:32:36 -0000 --=-xs9klpMOoj7fSrx0ggwD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ruslan Mahmatkhanov p=C3=AD=C5=A1e v =C3=BAt 26. 04. 2011 v 23:14 +0400: > 26.04.2011 21:49, Pav Lucistnik =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Olivier Duchateau p=C3=AD=C5=A1e v =C3=BAt 26. 04. 2011 v 19:23 +0200: > >> Hi, > >> > >> I noticed port, archivers/thunar-archive-plugin is marked as broken. > >> I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. > >> > >> May I have log, please ? > > > > Sure, > > > > http://portsmon.freebsd.org/portoverview.py?category=3D&portname=3Dthun= ar-archive-plugin > > > > Missing dependency most probably. >=20 > This patch should work. It does. --=20 --=20 Pav Lucistnik It also explains why paper clips just lie there while you look at them, but as soon as you turn your back, they run away, giggling wildly, and transform themselves into coat hangers. --=-xs9klpMOoj7fSrx0ggwD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk23K9oACgkQntdYP8FOsoKQegCfZBuRm2Zzacpn0Vw3A0dqFyOt 2/8An3jcniIKh2rhd8fXic9UmgFVGGff =hjKL -----END PGP SIGNATURE----- --=-xs9klpMOoj7fSrx0ggwD-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 21:18:26 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 427EE106564A for ; Tue, 26 Apr 2011 21:18:26 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp03.lnh.mail.rcn.net (smtp03.lnh.mail.rcn.net [207.172.157.103]) by mx1.freebsd.org (Postfix) with ESMTP id EB0988FC0C for ; Tue, 26 Apr 2011 21:18:25 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 26 Apr 2011 17:18:25 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id AVN68258; Tue, 26 Apr 2011 17:18:24 -0400 Received-SPF: None identity=pra; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@jerusalem.litteratus.org.litteratus.org"; x-conformance=sidf_compatible Received: from 209-6-91-204.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.91.204]) by smtp01.lnh.mail.rcn.net with ESMTP; 26 Apr 2011 17:18:18 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19895.13977.553973.609431@jerusalem.litteratus.org> Date: Tue, 26 Apr 2011 17:18:17 -0400 To: Chip Camden In-Reply-To: <20110426184315.GA2320@libertas.local.camdensoftware.com> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr17.lnh.mail.rcn.net) Cc: freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 21:18:26 -0000 Chip Camden writes: > > If you want to definitively ascertain the popularity of an application, > > just remove it from the ports structure and see how many users complain. > > There could be quite a delay in that reaction -- it might not hit > home until the port needs to be rebuilt. It is also possible it is only important to a fairly small number ... but to those it is absolutely crucial. Robert Huff From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 21:27:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D777106566B for ; Tue, 26 Apr 2011 21:27:50 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 82D1A8FC12 for ; Tue, 26 Apr 2011 21:27:50 +0000 (UTC) Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta07.emeryville.ca.mail.comcast.net with comcast id cMN31g00216AWCUA7MTqEd; Tue, 26 Apr 2011 21:27:50 +0000 Received: from comcast.net ([98.203.142.76]) by omta06.emeryville.ca.mail.comcast.net with comcast id cMTn1g00i1f6R9u8SMTo7B; Tue, 26 Apr 2011 21:27:49 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 14:27:47 -0700 Date: Tue, 26 Apr 2011 14:27:47 -0700 From: Charlie Kester To: FreeBSD Ports Message-ID: <20110426212747.GC38579@comcast.net> Mail-Followup-To: FreeBSD Ports References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <20110426163424.GB38579@comcast.net> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 21:27:50 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: > >I'm not a web programmer and don't have access to the freshports >sourcecode. So all I can do there is make a suggestion. But perhaps I'll >take some time to go through the list of unmaintained ports and manually >check them against the popularity ratings on a site like freshmeat. >It's a bit of a leap to assume that a program that's popular on Linux >will be as popular on BSD, but it's the best data we have for the time >being. FWIW, here are some popularity/vitality stats from freshmeat for unmaintained ports in the sysutils category. Freshmeat calculates these stats as follows: popularity = ((record hits + URL hits) * (subscriptions + 1))^(1/2) where record hits = hits on the freshmeat project page, url hits = clickthroughs to author's projectpage or download site, and subscriptions = freshmeat users following the project. vitality = ((announcements * age) / (last_announcement))^(1/2) "The number of announcements a project has made is multiplied by the number of days it has existed in the database, which is then divided by the days passed since the last release. This way, projects with lots of announcements that have been around for a long time and have recently come out with a new release earn a high vitality score, and old projects that have only been announced once get a low vitality score." For comparison and to give a sense of scale, here are the stats for some well-known projects: Name Popularity Vitality mplayer 3,995.20 45.16 MySQL 3,310.55 73.39 mutt 1,032.71 42.53 conky 173.67 3.60 exaile 64.48 3.75 In the attached file, ports listed with popularity and vitality scores = 0 are those where there is no entry in the freshmeat database. I made no effort to verify that a freshmeat project with the same name as the port is in fact the same program, so there might be some false positives in the data. --0F1p//8PRICkK4MW-- From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 21:34:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B0EE106564A for ; Tue, 26 Apr 2011 21:34:04 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 269238FC0C for ; Tue, 26 Apr 2011 21:34:03 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta13.westchester.pa.mail.comcast.net with comcast id cMZy1g0090bG4ec5DMa4V5; Tue, 26 Apr 2011 21:34:04 +0000 Received: from comcast.net ([98.203.142.76]) by omta03.westchester.pa.mail.comcast.net with comcast id cMa21g00e1f6R9u3PMa2g0; Tue, 26 Apr 2011 21:34:04 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 14:34:00 -0700 Date: Tue, 26 Apr 2011 14:34:00 -0700 From: Charlie Kester To: FreeBSD Ports Message-ID: <20110426213400.GD38579@comcast.net> Mail-Followup-To: FreeBSD Ports References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426212747.GC38579@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20110426212747.GC38579@comcast.net> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 21:34:04 -0000 On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: >On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: >> >>I'm not a web programmer and don't have access to the freshports >>sourcecode. So all I can do there is make a suggestion. But perhaps I'll >>take some time to go through the list of unmaintained ports and manually >>check them against the popularity ratings on a site like freshmeat. >>It's a bit of a leap to assume that a program that's popular on Linux >>will be as popular on BSD, but it's the best data we have for the time >>being. > >FWIW, here are some popularity/vitality stats from freshmeat for >unmaintained ports in the sysutils category. > >Freshmeat calculates these stats as follows: > >popularity = ((record hits + URL hits) * (subscriptions + 1))^(1/2) > >where record hits = hits on the freshmeat project page, url hits = >clickthroughs to author's projectpage or download site, and >subscriptions = freshmeat users following the project. > >vitality = ((announcements * age) / (last_announcement))^(1/2) > >"The number of announcements a project has made is multiplied by the >number of days it has existed in the database, which is then divided by >the days passed since the last release. This way, projects with lots of >announcements that have been around for a long time and have recently >come out with a new release earn a high vitality score, and old projects >that have only been announced once get a low vitality score." > >For comparison and to give a sense of scale, here are the stats for some >well-known projects: > >Name Popularity Vitality > >mplayer 3,995.20 45.16 > >MySQL 3,310.55 73.39 > >mutt 1,032.71 42.53 > >conky 173.67 3.60 > >exaile 64.48 3.75 > >In the attached file, ports listed with popularity and vitality scores = 0 >are those where there is no entry in the freshmeat database. > >I made no effort to verify that a freshmeat project with the same name >as the port is in fact the same program, so there might be some false >positives in the data. Drat, the mailinglist rejected the attachment. If anyone wants to see it, send me a private email and I'll reply with a copy. From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 21:54:05 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id CA31E1065686 for ; Tue, 26 Apr 2011 21:54:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9F43217992F; Tue, 26 Apr 2011 21:54:05 +0000 (UTC) Message-ID: <4DB73EFD.1070502@FreeBSD.org> Date: Tue, 26 Apr 2011 14:54:05 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: Robert Huff References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> In-Reply-To: <19895.13977.553973.609431@jerusalem.litteratus.org> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 21:54:05 -0000 On 04/26/2011 14:18, Robert Huff wrote: > It is also possible it is only important to a fairly small > number ... but to those it is absolutely crucial. Fair enough, then one of them needs to step forward to maintain the port. :) FWIW, I think that the person who suggested deleting the port as a way to gain a metric of its popularity was joking ... Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 22:09:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFDBB1065672 for ; Tue, 26 Apr 2011 22:09:14 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id D75F28FC19 for ; Tue, 26 Apr 2011 22:09:14 +0000 (UTC) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta06.emeryville.ca.mail.comcast.net with comcast id cN6B1g0011wfjNsA6N9E6L; Tue, 26 Apr 2011 22:09:14 +0000 Received: from comcast.net ([98.203.142.76]) by omta23.emeryville.ca.mail.comcast.net with comcast id cN9B1g00j1f6R9u8jN9CUQ; Tue, 26 Apr 2011 22:09:13 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 15:09:11 -0700 Date: Tue, 26 Apr 2011 15:09:11 -0700 From: Charlie Kester To: FreeBSD Ports Message-ID: <20110426220911.GE38579@comcast.net> Mail-Followup-To: FreeBSD Ports References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426212747.GC38579@comcast.net> <20110426213400.GD38579@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20110426213400.GD38579@comcast.net> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 22:09:15 -0000 On Tue 26 Apr 2011 at 14:34:00 PDT Charlie Kester wrote: >On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: >>FWIW, here are some popularity/vitality stats from freshmeat for >>unmaintained ports in the sysutils category. > >Drat, the mailinglist rejected the attachment. If anyone wants to see >it, send me a private email and I'll reply with a copy. Here are the top ten most "popular" unmaintained ports from this category, in case someone's looking for one to adopt: "name" "popularity" "vitality" "k3b" 754.12 120.91 "sg3_utils" 444.46 41.9 "LPRng" 303.65 5.13 "afio" 292.62 2.44 "anteater" 237.11 4.26 "bchunk" 215.97 2.71 "userinfo" 211.26 23.51 "ddrescue" 210.72 8.82 "cpuburn" 207.73 1 "cw" 207.28 11.25 k3b looks like an obvious choice. I restricted my search to this category while hammering out my approach. Now that I have my code proved out, I'm going to expand it to look at all unmaintained ports regardless of category. Any suggestions for where I should post the results? (That is, unless you think the bitbucket is the only suitable place for it.) From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 22:15:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28444106564A for ; Tue, 26 Apr 2011 22:15:58 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gw0-f68.google.com (mail-gw0-f68.google.com [74.125.83.68]) by mx1.freebsd.org (Postfix) with ESMTP id CDEC48FC15 for ; Tue, 26 Apr 2011 22:15:57 +0000 (UTC) Received: by gwj19 with SMTP id 19so177450gwj.7 for ; Tue, 26 Apr 2011 15:15:57 -0700 (PDT) Received: by 10.236.189.69 with SMTP id b45mr1665474yhn.293.1303856157047; Tue, 26 Apr 2011 15:15:57 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id h4sm81788yhm.80.2011.04.26.15.15.55 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 15:15:56 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QJzJp5Sjcz2CG54 for ; Tue, 26 Apr 2011 18:15:54 -0400 (EDT) Date: Tue, 26 Apr 2011 18:15:54 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110426181554.6ddd9393@seibercom.net> In-Reply-To: <4DB73EFD.1070502@FreeBSD.org> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB73EFD.1070502@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 22:15:58 -0000 On Tue, 26 Apr 2011 14:54:05 -0700 Doug Barton articulated: > On 04/26/2011 14:18, Robert Huff wrote: > > It is also possible it is only important to a fairly small > > number ... but to those it is absolutely crucial. > > Fair enough, then one of them needs to step forward to maintain the > port. :) > > FWIW, I think that the person who suggested deleting the port as a > way to gain a metric of its popularity was joking ... Sorry, but I was dead serious. "Don't Know What You Got (Till It's Gone)" "Cinderella" If no one steps up claiming to need the port, then good riddance. If on the other hand a user claims a valid use of the port, let them take responsibility for it or find someone who will. Leaving intact ports that either don't build, cannot be fetched, etcetera does not really make a lot of sense. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 22:55:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A47E81065670 for ; Tue, 26 Apr 2011 22:55:59 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by mx1.freebsd.org (Postfix) with ESMTP id 622CD8FC08 for ; Tue, 26 Apr 2011 22:55:59 +0000 (UTC) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta15.westchester.pa.mail.comcast.net with comcast id cNaB1g0031swQuc5FNvzjV; Tue, 26 Apr 2011 22:55:59 +0000 Received: from comcast.net ([98.203.142.76]) by omta15.westchester.pa.mail.comcast.net with comcast id cNvx1g01U1f6R9u3bNvy7k; Tue, 26 Apr 2011 22:55:59 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 15:55:56 -0700 Date: Tue, 26 Apr 2011 15:55:56 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110426225556.GF38579@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB73EFD.1070502@FreeBSD.org> <20110426181554.6ddd9393@seibercom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20110426181554.6ddd9393@seibercom.net> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 22:55:59 -0000 On Tue 26 Apr 2011 at 15:15:54 PDT Jerry wrote: > >If no one steps up claiming to need the port, then good riddance. If on >the other hand a user claims a valid use of the port, let them take >responsibility for it or find someone who will. Leaving intact ports >that either don't build, cannot be fetched, etcetera does not really >make a lot of sense. No disagreement here. Just now I ran a query on freshports and found almost 5000 ports with maintainer=ports@FreeBSD.org. That's way too many! My search for "popularity" metrics is intended to point me, as a maintainer, to ports I might want to adopt now, rather than wait for someone to complain about them. Everything *I* use is already maintained, so I've moved on to looking for things other people might need. But I don't want to waste my time on something that nobody uses. :) From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 23:28:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A11331065670 for ; Tue, 26 Apr 2011 23:28:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C1EDC14F9AA for ; Tue, 26 Apr 2011 23:28:09 +0000 (UTC) Message-ID: <4DB75508.9050007@FreeBSD.org> Date: Tue, 26 Apr 2011 16:28:08 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: FreeBSD Ports References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426212747.GC38579@comcast.net> <20110426213400.GD38579@comcast.net> <20110426220911.GE38579@comcast.net> In-Reply-To: <20110426220911.GE38579@comcast.net> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 23:28:11 -0000 On 04/26/2011 15:09, Charlie Kester wrote: > Now that I have my code proved out, I'm going to expand it to look at > all unmaintained ports regardless of category. Any suggestions for > where I should post the results? (That is, unless you think the > bitbucket is the only suitable place for it.) As a matter of curiosity, sure, put it on a web site somewhere, no worries. Meanwhile, I think you might be missing the point. :) We should not be looking for reasons to save unmaintained ports. We should be providing resources for those that would like to adopt them, pointing users to suitable alternatives, marking them deprecated so as to encourage maintainers to come forward, etc. In other words, exactly what we have been doing. Yes, there will likely be a period after the ports actually disappear where some of them will need to be resurrected because someone will finally be motivated to step forward. But that's easily done. Meanwhile, let's nuke as much as we can, as fast as we can. We're rapidly closing in on 23,000 ports, which is already an unmanageable mess. We need to be able to delete the cruft if we have any hope of keeping the ship afloat. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 01:43:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F9CD106564A for ; Wed, 27 Apr 2011 01:43:47 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 193CE8FC08 for ; Wed, 27 Apr 2011 01:43:46 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta14.emeryville.ca.mail.comcast.net with comcast id cR7p1g0071smiN4AERjm9n; Wed, 27 Apr 2011 01:43:46 +0000 Received: from comcast.net ([98.203.142.76]) by omta20.emeryville.ca.mail.comcast.net with comcast id cRjj1g00S1f6R9u8gRjjHe; Wed, 27 Apr 2011 01:43:45 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 18:43:43 -0700 Date: Tue, 26 Apr 2011 18:43:43 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110427014343.GJ38579@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 01:43:47 -0000 Well, due to some serious philosophical differences re these deprecation campaigns and what seems to be resistance to any further discussion, I don't think I can continue working with the committers. So I'm stepping down. If no one else wants to maintain them, please reset the maintainer of the following ports to ports@FreeBSD.org: audio/mcplay deskutils/osmo deskutils/teapot devel/argtable devel/egypt devel/gengetopt devel/libXGP devel/libYGP finance/xinvest finance/xquote graphics/box graphics/boxer graphics/fly graphics/sng math/ised misc/vifm misc/xsw multimedia/gpodder multimedia/openshot multimedia/photofilmstrip security/beecrypt security/ccrypt security/nettle security/ranpwd sysutils/dircomp sysutils/gaffitter sysutils/iextract sysutils/lookat sysutils/moreutils sysutils/moreutils-parallel sysutils/ncdu sysutils/rdup textproc/tdhkit x11/fbpanel From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 03:35:23 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E91C2106564A for ; Wed, 27 Apr 2011 03:35:23 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by mx1.freebsd.org (Postfix) with ESMTP id 524FA8FC08 for ; Wed, 27 Apr 2011 03:35:22 +0000 (UTC) Received: from smtp5.server.rpi.edu (localhost.localdomain [127.0.0.1]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id p3R2KhS5014350 for ; Tue, 26 Apr 2011 22:20:44 -0400 Received: (from defang@localhost) by smtp5.server.rpi.edu (8.13.1/8.13.0/Submit) id p3R2KfL4014330 for freebsd-ports@freebsd.org; Tue, 26 Apr 2011 22:20:41 -0400 Received: from gilead.netel.rpi.edu (gilead.netel.rpi.edu [128.113.124.121]) by smtp5.server.rpi.edu (envelope-sender ) (MIMEDefang) with ESMTP id p3R2Kecp014324; Tue, 26 Apr 2011 22:20:41 -0400 (EDT) Message-ID: <4DB77D78.1010503@FreeBSD.org> Date: Tue, 26 Apr 2011 22:20:40 -0400 From: Garance A Drosehn User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4 MIME-Version: 1.0 To: fb-ports References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 1.50 (*) [Hold at 10.00] COMBINED_FROM,RATWARE_GECKO_BUILD X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Cc: Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 03:35:24 -0000 On 4/25/11 8:28 PM, martinko wrote: > Ok, > I skimmed through the list of deprecated ports Speaking of which, I haven't noticed the old lists of "FreeBSD unmaintained ports which are currently marked broken" and "FreeBSD ports which are currently scheduled for deletion" show up recently. I did have some mixup in my email account for a short period, so I assume I just missed an announcement on how that is handled now. Where is the current list of deprecated ports? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 03:41:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24870106564A for ; Wed, 27 Apr 2011 03:41:51 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp01.lnh.mail.rcn.net (smtp11.lnh.mail.rcn.net [207.172.157.101]) by mx1.freebsd.org (Postfix) with ESMTP id CA15E8FC0A for ; Wed, 27 Apr 2011 03:41:50 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 26 Apr 2011 23:41:51 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BAU99519; Tue, 26 Apr 2011 23:41:49 -0400 Received-SPF: None identity=pra; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@jerusalem.litteratus.org.litteratus.org"; x-conformance=sidf_compatible Received: from 209-6-91-204.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.91.204]) by smtp01.lnh.mail.rcn.net with ESMTP; 26 Apr 2011 23:41:49 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19895.36988.850986.935251@jerusalem.litteratus.org> Date: Tue, 26 Apr 2011 23:41:48 -0400 To: Garance A Drosehn In-Reply-To: <4DB77D78.1010503@FreeBSD.org> References: <4DB77D78.1010503@FreeBSD.org> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr16.lnh.mail.rcn.net) Cc: fb-ports Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 03:41:51 -0000 Garance A Drosehn writes: > Speaking of which, I haven't noticed the old lists of > "FreeBSD unmaintained ports which are currently marked broken" > and > "FreeBSD ports which are currently scheduled for deletion" > > show up recently. I did have some mixup in my email account > for a short period, so I assume I just missed an announcement > on how that is handled now. I get regular e-mails for "marked as broken". Robert Huff From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 03:46:10 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDD61106564A for ; Wed, 27 Apr 2011 03:46:09 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6FCCE8FC08 for ; Wed, 27 Apr 2011 03:46:09 +0000 (UTC) Received: by gyg13 with SMTP id 13so597712gyg.13 for ; Tue, 26 Apr 2011 20:46:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=oPuhP39ZuWxWyjvCLkav3r4WWZO1GsVNKFO99h05eFs=; b=tyqiaQIO00yL5L1VYSfIqhvBkwHoqijSlLT5CdoLDXvZfdEgJs9t6M7NDFH4IGXO9f cnGxaq1nVOeg9g+b1my5RHOGW2ARrVQb2+zPYDH43gjw6Y14qv6wmBhRdL/PZhavpbar zQ4TrVcKSNJTNYkeKG9ARJ8QdydiS9GHIW478= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-openpgp-key-id :x-openpgp-key-fingerprint:x-openpgp-key-url; b=KBZlEop88jc23Ew3jSLvrLJHTQA6zgVqBnmmaSbvm/UTlU6choUEtWPGkoEafDNNW9 JDyQ/G7euMgsZ+GwIsUV08e684WtyQh5O9jWp9pQ+usfIdy7HH6SNMoqPVgwLqohuPON Zm+OCPassBiv1pWFuOGAt8VQErO0oDJBICHeo= Received: by 10.236.170.225 with SMTP id p61mr1997415yhl.231.1303875968607; Tue, 26 Apr 2011 20:46:08 -0700 (PDT) Received: from DataIX.net (adsl-99-190-84-116.dsl.klmzmi.sbcglobal.net [99.190.84.116]) by mx.google.com with ESMTPS id 25sm236411yhl.5.2011.04.26.20.46.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 20:46:07 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p3R3k3Bx084315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 23:46:04 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p3R3k3ou084314; Tue, 26 Apr 2011 23:46:03 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Tue, 26 Apr 2011 23:46:03 -0400 From: "Jason J. Hellenthal" To: martinko Message-ID: <20110427034602.GA80558@DataIX.net> References: <4DB60812.1000109@users.sf.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <4DB60812.1000109@users.sf.net> X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-multimedia@freebsd.org, itetcu@freebsd.org, freebsd-ports@freebsd.org Subject: Re: expiration of net/skype ?! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 03:46:10 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable martinko, Hi, Ive read your post below and the following two messages on this among other messages regarding the deprecation of ports. One thing that should be noted is that once the deprecation process is done and over and the port nolonger becomes part of the tree, you are still more than able and welcome to keep the distfiles you have as well checkout just the port directory in question that you are worried about to a seperate place other than the ports tree to maintain it locally. The port may not exactly be in the snapshot tree but just because of that does not mean it will not work for you from a different location. Also note that it may actually be good practice for those that need to use those ports but are unsure of exactly what it involves to upkeep them. It could lead you to another time where you might be interested in being the maintainer for that port. On Tue, Apr 26, 2011 at 01:47:30AM +0200, martinko wrote: >Hi all, > >So what is this deprecation and expiration of net/skype port please ?? >I'm asking because I've been using it successfully for more than a year=20 >and installed it again just this weekend without any issue. And I've=20 >read in the mailing lists many others use it too. So why all that=20 >black-listing ? Should I copy the port to my home folder for future=20 >installations ? Or can I / we do something about keeping it in the=20 >ports tree ? I would surely appreciate if it could stay there. > --=20 Regards, (jhell) Jason Hellenthal --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJNt5F6AAoJEJBXh4mJ2FR+bHkH/iFaC6RZF5884cqKdPZ0cyOC FSq4gSEQfb051ZjpTfMZXSfmymvdaFVN7w2jg3zjVdOFXEk2q6aTJBPgaUPIM7dM F8+Fh7ZKzOccQ/uJwIzUxraO5IeCZ5fRI/FeCsyM03nQtNL3xyC3sVoVyXnjEcUS FnmXy+uuMhxdrXqXmdRcDTcFieNrZxenKgMwtyEFAEIbU2JrZ8+GGU9DG1lvPtZ0 /mrzLDOiXKE9p2MrZ/lXgxpaYQtR/6jHv8+mNComK1FI3/bXmlGkmPBgmEyjCb4J jFa5kFjZRgyxHh8zGqAJ5xNlHnyYxGr6GIrqfucPFdOQd4cqnwatVEdOpi1g1+8= =Oztd -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 04:18:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91DF0106567C; Wed, 27 Apr 2011 04:18:39 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id EF95B8FC1C; Wed, 27 Apr 2011 04:18:37 +0000 (UTC) Received: by fxm11 with SMTP id 11so1258148fxm.13 for ; Tue, 26 Apr 2011 21:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZBRaFm1Ab6r7y+glpTQZDO/Cyqfnz/g3DsxC3EVyfYQ=; b=mxNzwGFWAo5fBlynE8+TScMdMr6vz0Zz9Q52VP2S1rrj7TDrJhvXsat8gbFIv1JbZi kNNQfVeV+/muulnHD2nuy3ARXBthezPY0mFQ/0T+t6sBSzf9FJ8Ts7at9NVadc0sAfKx KyJ2s9acnHpLKOz0Jla9P6QO4mH2AEOEXIHIk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hYZ+K226E5iPNkkm/lFcl2uW0q8Fv6jOQQiq4zEwdAXYzJVauj7tk6pc5tpKgC0gfF OwCpFeEGi0ENCSOoWzMJbG6jL0258XPn/NHtp6zv12vQI8v0ueedUUIpF4ZXxZXk9Dox /7Fh9+OqduoV00aG2F3/uN5jH/4kuidMaR9gc= MIME-Version: 1.0 Received: by 10.223.54.213 with SMTP id r21mr135753fag.54.1303876299176; Tue, 26 Apr 2011 20:51:39 -0700 (PDT) Received: by 10.223.20.145 with HTTP; Tue, 26 Apr 2011 20:51:39 -0700 (PDT) In-Reply-To: <19895.36988.850986.935251@jerusalem.litteratus.org> References: <4DB77D78.1010503@FreeBSD.org> <19895.36988.850986.935251@jerusalem.litteratus.org> Date: Tue, 26 Apr 2011 22:51:39 -0500 Message-ID: From: Adam Vande More To: Robert Huff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: fb-ports , Garance A Drosehn Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 04:18:40 -0000 On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > > Garance A Drosehn writes: > > > Speaking of which, I haven't noticed the old lists of > > "FreeBSD unmaintained ports which are currently marked broken" > > and > > "FreeBSD ports which are currently scheduled for deletion" > > > > show up recently. I did have some mixup in my email account > > for a short period, so I assume I just missed an announcement > > on how that is handled now. > > I get regular e-mails for "marked as broken". > Last one I have is from Jan 21, prior to that it was twice monthly. -- Adam Vande More From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 04:30:34 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0EA71065672 for ; Wed, 27 Apr 2011 04:30:34 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 629128FC13 for ; Wed, 27 Apr 2011 04:30:34 +0000 (UTC) Received: by yie12 with SMTP id 12so618826yie.13 for ; Tue, 26 Apr 2011 21:30:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=o5HXdvOgOMc1iyIYtSLn2ELfYP/V7pWqRqyBolvzIxs=; b=tVeC4I5PMb6mZUQElfy/jMYzYzzSfzsjKVzlBm+BvV8Y/IAj3kSc+lZlI+RkF5MbKg ilwZ0uQ5U3iOXPk4VJVv2OGFwmtOcFwhrEb9C6b4gyPdU6fkyg+XA1plYD0wrhJU7bNp GvVWaSHwphXoQPr43cHdM4uGYrUb2SOhAf+Hk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-openpgp-key-id :x-openpgp-key-fingerprint:x-openpgp-key-url; b=K2cq4IRhzc3cdJZdmwCBBIz39c2aa5Sg4FF4uLApQNYjCbfXPeL9WxKKcQJnPCsrjP FuobjroJ0iHxmuMYae3kXtzX7hm8lISlXkJGZSm29RIdoOAk4rqgE2fhmbIIDaqVW6NF Xgraymp56RwCjVs2OMBrc2CXSyzUN1ym5GMxg= Received: by 10.236.146.106 with SMTP id q70mr2058275yhj.459.1303878633680; Tue, 26 Apr 2011 21:30:33 -0700 (PDT) Received: from DataIX.net (adsl-99-190-84-116.dsl.klmzmi.sbcglobal.net [99.190.84.116]) by mx.google.com with ESMTPS id f73sm247929yhc.41.2011.04.26.21.30.31 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 21:30:32 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p3R4USGx087584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Apr 2011 00:30:29 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p3R4UScF087583; Wed, 27 Apr 2011 00:30:28 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Wed, 27 Apr 2011 00:30:27 -0400 From: "Jason J. Hellenthal" To: Adam Vande More Message-ID: <20110427043027.GA84328@DataIX.net> References: <4DB77D78.1010503@FreeBSD.org> <19895.36988.850986.935251@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: Robert Huff , Garance A Drosehn , fb-ports Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 04:30:35 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Adam, On Tue, Apr 26, 2011 at 10:51:39PM -0500, Adam Vande More wrote: >On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > >> >> Garance A Drosehn writes: >> >> > Speaking of which, I haven't noticed the old lists of >> > "FreeBSD unmaintained ports which are currently marked broken" >> > and >> > "FreeBSD ports which are currently scheduled for deletion" >> > >> > show up recently. I did have some mixup in my email account >> > for a short period, so I assume I just missed an announcement >> > on how that is handled now. >> >> I get regular e-mails for "marked as broken". >> > >Last one I have is from Jan 21, prior to that it was twice monthly. > Must be they were scheduled for deletion ;) last ones I received here for the two first listed subjects above were recieved January. --=20 Regards, (jhell) Jason Hellenthal --azLHFNyN32YCQGCU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJNt5vjAAoJEJBXh4mJ2FR+i3oH/1ddLEWGiGP47MOebrcerpeE 12YVpu323XdCdo4Oz8LQw0MPOmJ1S6KNeeRbQ2ViWJZyuuBOHeZvqg98MOr9jdHU 95rrOugwBhDhByjKcU0J4vo5dkaDPOASw3+ccdiNUfPb6fQZ1kURvYL4zVO7AMLr xxUdIwJ3v6b+48UOHiuZcL9Vgk1WShvvmLusFz1P7VmW3VkFIFmyi/cIqyPn+Tr9 3VBzMGBUhRrqLNXmGYn+zgatWkarw1vdHm/idKPpn86FFu/334bM3jJqrekjlYpJ WCjjKHy37K6etwC3X8kk/Sr9tVOglAfcxRxVIoukLgV/fFKoxu5QDcvr20l9fp0= =rj8o -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 05:00:25 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E22B1065672 for ; Wed, 27 Apr 2011 05:00:25 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3BECC8FC0C for ; Wed, 27 Apr 2011 05:00:25 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id BC92D56161; Wed, 27 Apr 2011 00:00:24 -0500 (CDT) Date: Wed, 27 Apr 2011 00:00:24 -0500 From: Mark Linimon To: Garance A Drosehn Message-ID: <20110427050024.GA12630@lonesome.com> References: <4DB77D78.1010503@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB77D78.1010503@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: fb-ports Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 05:00:25 -0000 I need to migrate portsmon to another server so that we can start up these periodic emails again. mcl From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 05:14:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5677D1065670 for ; Wed, 27 Apr 2011 05:14:56 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward15.mail.yandex.net (forward15.mail.yandex.net [95.108.130.119]) by mx1.freebsd.org (Postfix) with ESMTP id 0970A8FC08 for ; Wed, 27 Apr 2011 05:14:55 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward15.mail.yandex.net (Yandex) with ESMTP id 49DF89E167E for ; Wed, 27 Apr 2011 09:14:54 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1303881294; bh=ycdCzTC9Btjl128SeMv39uH5g2g08+1mPHdnJ9rYbFU=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=OglNZj/eD0klCkY9qEjMC2K9lvvyF/hjLT+T2X/YDdthJWkvKHbPvgGV28tAA/v7J qSnUgJiXeQQwN8G8nwlVNKGKHoW3orYSdDbfevhTqrWzCijm0mxJDq2DTiSAYsLxpc arMF63qrDvGV/1T+Dl/ZAfcE65GPsIMdeAuBsWp4= Received: from smeshariki2.local (unknown [178.76.212.172]) by smtp12.mail.yandex.net (Yandex) with ESMTPSA id 1B12B572803C for ; Wed, 27 Apr 2011 09:14:54 +0400 (MSD) Message-ID: <4DB7A5D6.2010004@yandex.ru> Date: Wed, 27 Apr 2011 09:12:54 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.15) Gecko/20110425 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20110427014343.GJ38579@comcast.net> In-Reply-To: <20110427014343.GJ38579@comcast.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Yandex-Spam: 1 Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 05:14:56 -0000 27.04.2011 05:43, Charlie Kester пишет: > > Well, due to some serious philosophical differences re these > deprecation campaigns and what seems to be resistance to any further > discussion, I don't think I can continue working with the committers. > So I'm stepping down. > > If no one else wants to maintain them, please reset the maintainer of the > following ports to ports@FreeBSD.org: > I'm interesting in maintaing of this ports: > multimedia/gpodder > sysutils/rdup -- Regards, Ruslan From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 05:15:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2EC1106566B for ; Wed, 27 Apr 2011 05:15:59 +0000 (UTC) (envelope-from lichray@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6B52C8FC12 for ; Wed, 27 Apr 2011 05:15:59 +0000 (UTC) Received: by fxm11 with SMTP id 11so1282858fxm.13 for ; Tue, 26 Apr 2011 22:15:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Ve8yufIXG5w1OCGSlrpNqkJdidJf8eOmj3PBneGX9xU=; b=TGJLFmAlXYuBbya1j4Z4i1lC/QsRRORW70IitsZH2gZFrXYGwUeOaWnLed+IaYGe8E U/+T4OGVLSvx5loDZ/px9bO9KVmtBqgV5OTV/umPIxq1UJRwgZpqQrfLs+j9eDoU2zZt 5lKGKKWvjbXQj41aj+8tFPl2axOElozfUaquA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tuQzWzyONWr7jDhsR7kI5AqsXaMEhP/oqFXN8FeT4+8AgN/iB4hP1oIKQGllH04OqS txfqeXLmENwpgUhbsyOYdrxO/Zk+NoE5N1WAtWx/htGmISZ94k9C1B76qiRzuEH2uSkp 4qd3bnl7xgQ1ZMqg9ER+7gV3EAJ0hH0CYopdU= MIME-Version: 1.0 Received: by 10.223.106.78 with SMTP id w14mr1800505fao.35.1303881358277; Tue, 26 Apr 2011 22:15:58 -0700 (PDT) Received: by 10.223.73.199 with HTTP; Tue, 26 Apr 2011 22:15:58 -0700 (PDT) In-Reply-To: <20110427014343.GJ38579@comcast.net> References: <20110427014343.GJ38579@comcast.net> Date: Wed, 27 Apr 2011 00:15:58 -0500 Message-ID: From: Zhihao Yuan To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 05:15:59 -0000 On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester wrote: > > Well, due to some serious philosophical differences re these > deprecation campaigns and what seems to be resistance to any further > discussion, I don't think I can continue working with the committers. > So I'm stepping down. > > If no one else wants to maintain them, please reset the maintainer of the > following ports to ports@FreeBSD.org: > > audio/mcplay > deskutils/osmo > deskutils/teapot > devel/argtable > devel/egypt > devel/gengetopt > devel/libXGP > devel/libYGP > finance/xinvest > finance/xquote > graphics/box > graphics/boxer > graphics/fly > graphics/sng > math/ised > misc/vifm > misc/xsw > multimedia/gpodder > multimedia/openshot > multimedia/photofilmstrip > security/beecrypt > security/ccrypt > security/nettle > security/ranpwd > sysutils/dircomp > sysutils/gaffitter > sysutils/iextract > sysutils/lookat > sysutils/moreutils > sysutils/moreutils-parallel > sysutils/ncdu > sysutils/rdup > textproc/tdhkit > x11/fbpanel O-o-ok... philosophical differences. audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many users, AFAIK, and require much works. We need to someone to take them soon. > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 06:09:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF2EA1065672 for ; Wed, 27 Apr 2011 06:09:21 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 91C428FC1C for ; Wed, 27 Apr 2011 06:09:21 +0000 (UTC) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta10.westchester.pa.mail.comcast.net with comcast id cW651g0010SCNGk5AW9MNR; Wed, 27 Apr 2011 06:09:21 +0000 Received: from comcast.net ([98.203.142.76]) by omta09.westchester.pa.mail.comcast.net with comcast id cW9K1g00y1f6R9u3VW9LQT; Wed, 27 Apr 2011 06:09:21 +0000 Received: by comcast.net (sSMTP sendmail emulation); Tue, 26 Apr 2011 23:09:18 -0700 Date: Tue, 26 Apr 2011 23:09:17 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110427060917.GB73524@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110427014343.GJ38579@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 06:09:22 -0000 On Tue 26 Apr 2011 at 22:15:58 PDT Zhihao Yuan wrote: >On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester wrote: >> >> Well, due to some serious philosophical differences re these >> deprecation campaigns and what seems to be resistance to any further >> discussion, I don't think I can continue working with the committers. >> So I'm stepping down. >> >> If no one else wants to maintain them, please reset the maintainer of the >> following ports to ports@FreeBSD.org: >> >> audio/mcplay >> deskutils/osmo >> deskutils/teapot >> devel/argtable >> devel/egypt >> devel/gengetopt >> devel/libXGP >> devel/libYGP >> finance/xinvest >> finance/xquote >> graphics/box >> graphics/boxer >> graphics/fly >> graphics/sng >> math/ised >> misc/vifm >> misc/xsw >> multimedia/gpodder >> multimedia/openshot >> multimedia/photofilmstrip >> security/beecrypt >> security/ccrypt >> security/nettle >> security/ranpwd >> sysutils/dircomp >> sysutils/gaffitter >> sysutils/iextract >> sysutils/lookat >> sysutils/moreutils >> sysutils/moreutils-parallel >> sysutils/ncdu >> sysutils/rdup >> textproc/tdhkit >> x11/fbpanel > >O-o-ok... philosophical differences. > >audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many >users, AFAIK, and require much works. We need to someone to take them >soon. I don't know what you mean by "requires much works". The only ones of these ports that are not up-to-date are xquote and nettle. There is already an open PR to update nettle. All it needs is some attention from a committer. Frankly, xquote should be deprecated, as it's an old-style Motif app that's so ugly I'll bet no one uses it. I only took it (and the related xinvest) because they got reinstated after I pointed out they were still fetchable at a new location. Everything else is in good shape. I've been told that we shouldn't be looking for reasons to save any unmaintained port, and I was specifically told this in response to my efforts to identify ports that have a lot of users. So I don't think current policy supports the conclusion that "we need to find someone to take them soon." There, in a nutshell, you have the philosophical disagreement which led to my decision to be done with ports. If the powers-that-be want to deprecate all of these and lighten the load on the system and themselves, I no longer care. I know how to download a tarball and run through the configure/make/install routine, so I'll still be able to run the software I need. I thought I'd lend a hand to those who don't have those skills, but it doesn't seem that this contribution is welcomed or appreciated. "There are too many ports!" (Sorry if I'm ranting, I am still very angry about all this.) From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 06:12:40 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D46E1065675 for ; Wed, 27 Apr 2011 06:12:40 +0000 (UTC) (envelope-from kline@thought.org) Received: from thought.org (plato.thought.org [209.180.213.209]) by mx1.freebsd.org (Postfix) with ESMTP id D77048FC17 for ; Wed, 27 Apr 2011 06:12:39 +0000 (UTC) Received: by thought.org (Postfix, from userid 1001) id 45C54E805FF; Tue, 26 Apr 2011 22:53:32 -0700 (PDT) Date: Tue, 26 Apr 2011 22:53:32 -0700 From: Gary Kline To: freebsd-ports@freebsd.org Message-ID: <20110427055332.GB9467@thought.org> References: <20110427014343.GJ38579@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427014343.GJ38579@comcast.net> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: With 24++ years of service to the Unix community. User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 06:12:40 -0000 sorry for the top post, but shouolder is killing me. idea 1: can the 'summer of code' guys help us out with this. idea 2. why oh why can we not live with the fbsd and debian paradigm? the reason i've kept my domain here at home is because i like the flexibility i see. but keeping ports current is getting to be impossible. there are too many distros of every open src os and maybe if net and free [RE]-hjoined arms that 3rd idea would work. i'm sure that many of you guys kno w that aristotle was a polymath; he was as sharp as anybody i have ever studied. his highest 'virtue' was pragmatism. given the headaches with maintaining ports, and much more, isn' t it time to look in new directions? idea 4. axe the number of ports. if person x or y want to maintain a port of his ow n , outstanding. he can post a note to the lists. idea 5. beging a completely separate, independent group for orphaned ports [ for free, net, debian, ubuntu, redhat, foobar opsys. a last note: i started out as a porter. loved i t and excelled at it. but it never was easy. it's still 3/2 * bear|bitch|swine. ergo, i know why many of this list and org are slowing or dropping out. Enuf, -g . On Tue, Apr 26, 2011 at 06:43:43PM -0700, Charlie Kester wrote: > Date: Tue, 26 Apr 2011 18:43:43 -0700 > From: Charlie Kester > Subject: Dropping maintainership of my ports > To: freebsd-ports@freebsd.org > Mail-Followup-To: freebsd-ports@freebsd.org > X-Mailer: Mutt 1.4.2.3i > > > Well, due to some serious philosophical differences re these > deprecation campaigns and what seems to be resistance to any further > discussion, I don't think I can continue working with the committers. > So I'm stepping down. > > If no one else wants to maintain them, please reset the maintainer > of the following ports to ports@FreeBSD.org: > > audio/mcplay > deskutils/osmo > deskutils/teapot > devel/argtable > devel/egypt > devel/gengetopt > devel/libXGP > devel/libYGP > finance/xinvest > finance/xquote > graphics/box > graphics/boxer > graphics/fly > graphics/sng > math/ised > misc/vifm > misc/xsw > multimedia/gpodder > multimedia/openshot > multimedia/photofilmstrip > security/beecrypt > security/ccrypt > security/nettle > security/ranpwd > sysutils/dircomp > sysutils/gaffitter > sysutils/iextract > sysutils/lookat > sysutils/moreutils > sysutils/moreutils-parallel > sysutils/ncdu > sysutils/rdup > textproc/tdhkit > x11/fbpanel > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- Gary Kline kline@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.98a release of Jottings: http://jottings.thought.org From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 06:23:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F101106564A for ; Wed, 27 Apr 2011 06:23:39 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id 271DF8FC15 for ; Wed, 27 Apr 2011 06:23:39 +0000 (UTC) Received: from [192.168.0.11] (atoulouse-256-1-41-46.w90-38.abo.wanadoo.fr [90.38.232.46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 14165435D7 for ; Wed, 27 Apr 2011 01:05:29 -0500 (CDT) Message-ID: <4DB7B237.7000603@marino.st> Date: Wed, 27 Apr 2011 08:05:43 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 06:23:39 -0000 Since we're already in the mood to discuss FreeBSD ports issues, maybe somebody can clear something up for me. Several days ago, I submitted a patch for a port I maintain: ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release version and add C++" Nobody has touched it, but many other PRs after that submission have been assigned, etc. So I have two questions: 1) What's involved with processing a patch from a maintainer? Is it simply a committer commits it on behalf of the maintainer (iow very easy?). Or is it the other end of the spectrum where it has to go through Tinderbox? I would assume the maintainer is trusted and the patch is applied without testing. 2) I have very well aware that people dedicate their own time, etc, and I think that explains why the PRs are getting cherry picked. But seriously, shouldn't there be a policy to process these PRs in order? I'm sure it's been like this for years, but it doesn't seem like the best approach to me. Or at least the fairest. Maybe if an interesting PR is submitted it will give extra incentive to process the waiting PRs to get to it. -- John From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 06:27:27 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCA96106564A for ; Wed, 27 Apr 2011 06:27:27 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id A65FB8FC08 for ; Wed, 27 Apr 2011 06:27:27 +0000 (UTC) Received: from [192.168.0.11] (atoulouse-256-1-41-46.w90-38.abo.wanadoo.fr [90.38.232.46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 85BDB435D7 for ; Wed, 27 Apr 2011 01:27:26 -0500 (CDT) Message-ID: <4DB7B75C.7080902@marino.st> Date: Wed, 27 Apr 2011 08:27:40 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> In-Reply-To: <20110427060917.GB73524@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 06:27:27 -0000 On 4/27/2011 8:09 AM, Charlie Kester wrote: > > I've been told that we shouldn't be looking for reasons to save any > unmaintained port, and I was specifically told this in response to my > efforts to identify ports that have a lot of users. So I don't think > current policy supports the conclusion that "we need to find someone to > take them soon." > > There, in a nutshell, you have the philosophical disagreement which led > to my decision to be done with ports. I skimmed the entire conversation this morning. The summary is you have an opinion that apparently nobody else shares. I maintain 7 ports. The majority of these ports had already been deleted years ago, or should have already been deprecated. So after years, somebody (me) showed up with enough motivation to resurrect the ports. That's all people are saying: If the port is important enough, somebody will step up to save it or resurrect it. If that doesn't happen, then it doesn't deserve to be in the tree once it doesn't build anymore. > If the powers-that-be want to deprecate all of these and lighten the > load on the system and themselves, I no longer care. I know how to > download a tarball and run through the configure/make/install routine, > so I'll still be able to run the software I need. I thought I'd lend a > hand to those who don't have those skills, but it doesn't seem that this > contribution is welcomed or appreciated. "There are too many ports!" > > (Sorry if I'm ranting, I am still very angry about all this.) Obviously the maintenance of ports is appreciated and welcomed. You're just sulking because your idea of identifying popular ports wasn't met with enthusiasm. If the port really is popular, somebody will take it over, I'm sure. I don't know you, or your history of contributions, etc, so all I can judge is what I read today. I don't think this reaction shows a lot of character. Anyway, I'm sure your wish of returning all the ports to nobody will be granted and life will go on. As a FreeBSD user, thanks for effort that you did in the past. Regards, John From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 07:15:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92C631065677 for ; Wed, 27 Apr 2011 07:15:47 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 561EF8FC13 for ; Wed, 27 Apr 2011 07:15:47 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta10.westchester.pa.mail.comcast.net with comcast id cXEc1g0021wpRvQ5AXFnnm; Wed, 27 Apr 2011 07:15:47 +0000 Received: from comcast.net ([98.203.142.76]) by omta18.westchester.pa.mail.comcast.net with comcast id cXFl1g0011f6R9u3eXFl63; Wed, 27 Apr 2011 07:15:47 +0000 Received: by comcast.net (sSMTP sendmail emulation); Wed, 27 Apr 2011 00:15:43 -0700 Date: Wed, 27 Apr 2011 00:15:43 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110427071543.GD73524@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4DB7B75C.7080902@marino.st> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 07:15:47 -0000 On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote: > >You're just sulking because your idea of identifying popular ports >wasn't met with enthusiasm. > No, it's more than that. I got the distinct impression that many of the committers would be unhappy if I took maintainership of some of the ports I might identify as "popular", because it would interfere with their plans to trim the portstree. Re-read the thread. At every point I'm talking about looking for ports I (and others) might want to maintain, as a service to their users. Now ask yourself why I've been getting so much resistance to that, when we keep hearing how deprecated ports can be easily resurrected if someone steps up to maintain them? Every response from the committers ignored what I said I was trying to do, and instead repeated the same old arguments about stale, unfetchable, broken or superceded ports. That "talking points" response tells me that they didn't want me doing what I was doing to buck an already-established policy of letting unmaintained ports die unless and until someone complains. Today wasn't the first time I've had this discussion with them. But it was the last straw as far as I'm concerned. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 07:50:57 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28AB1106564A for ; Wed, 27 Apr 2011 07:50:57 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp04.sth.basefarm.net (ch-smtp04.sth.basefarm.net [80.76.153.5]) by mx1.freebsd.org (Postfix) with ESMTP id AFC0E8FC12 for ; Wed, 27 Apr 2011 07:50:56 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:26735 helo=falcon.midgard.homeip.net) by ch-smtp04.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QEzVd-0002yW-G2 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 09:50:12 +0200 Received: (qmail 14699 invoked from network); 27 Apr 2011 09:49:58 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 27 Apr 2011 09:49:58 +0200 Received: (qmail 28878 invoked by uid 1001); 27 Apr 2011 09:49:58 +0200 Date: Wed, 27 Apr 2011 09:49:58 +0200 From: Erik Trulsson To: freebsd-ports@freebsd.org Message-ID: <20110427074958.GA28824@owl.midgard.homeip.net> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> <20110427071543.GD73524@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427071543.GD73524@comcast.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QEzVd-0002yW-G2. X-Scan-Signature: ch-smtp04.sth.basefarm.net 1QEzVd-0002yW-G2 b1f03155b08e7be85c871013534ceabf Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 07:50:57 -0000 On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote: > On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote: > > > >You're just sulking because your idea of identifying popular ports > >wasn't met with enthusiasm. > > > > No, it's more than that. I got the distinct impression that many of the > committers would be unhappy if I took maintainership of some of the > ports I might identify as "popular", because it would interfere with > their plans to trim the portstree. Then you have misunderstood things. I don't think anybody would be unhappy if you (or anybody else) took maintainership of one or more of the currently unmaintained ports. What plans there are, are not so much about trimming the portstree in general but trimming the number of unmaintained ports. What is met with uninterest is your plans to identify "popular" ports. > Re-read the thread. At every point I'm talking about looking for ports > I (and others) might want to maintain, as a service to their users. Now > ask yourself why I've been getting so much resistance to that, when we > keep hearing how deprecated ports can be easily resurrected if someone > steps up to maintain them? Actually you spend much time speaking about/looking for "popular" ports and that is what is met with uninterest. If you want to take maintainership of a port because you personally use that port and want to have it working, that is great. If you want to take maintainership of a port because you believe that it is a "popular" port, then go ahead, just don't expect much help with identifying such ports. > > Every response from the committers ignored what I said I was trying to > do, and instead repeated the same old arguments about stale, > unfetchable, broken or superceded ports. That "talking points" response > tells me that they didn't want me doing what I was doing to buck an > already-established policy of letting unmaintained ports die unless and > until someone complains. (Actually the policy is that unmaintained and non-working ports should be let to die, unless somebody steps up to fix the port and take maintainership.) Nobody is stopping you from assuming maintainership of one or more of those unmaintained ports, and thus preventing them from being removed. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 07:55:24 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 612EF1065670 for ; Wed, 27 Apr 2011 07:55:24 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp04.sth.basefarm.net (ch-smtp04.sth.basefarm.net [80.76.153.5]) by mx1.freebsd.org (Postfix) with ESMTP id EADE38FC12 for ; Wed, 27 Apr 2011 07:55:23 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:41592 helo=falcon.midgard.homeip.net) by ch-smtp04.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QEzaO-0004Pm-E5 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 09:55:05 +0200 Received: (qmail 14706 invoked from network); 27 Apr 2011 09:54:59 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 27 Apr 2011 09:54:59 +0200 Received: (qmail 28887 invoked by uid 1001); 27 Apr 2011 09:54:59 +0200 Date: Wed, 27 Apr 2011 09:54:59 +0200 From: Erik Trulsson To: John Marino Message-ID: <20110427075459.GB28824@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB7B237.7000603@marino.st> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QEzaO-0004Pm-E5. X-Scan-Signature: ch-smtp04.sth.basefarm.net 1QEzaO-0004Pm-E5 3dc943bff410a842e62f7b96ff176929 Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 07:55:24 -0000 On Wed, Apr 27, 2011 at 08:05:43AM +0200, John Marino wrote: > Since we're already in the mood to discuss FreeBSD ports issues, maybe > somebody can clear something up for me. > > Several days ago, I submitted a patch for a port I maintain: > ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release version > and add C++" > > Nobody has touched it, but many other PRs after that submission have > been assigned, etc. So I have two questions: > > 1) What's involved with processing a patch from a maintainer? Is it > simply a committer commits it on behalf of the maintainer (iow very > easy?). Or is it the other end of the spectrum where it has to go > through Tinderbox? I would assume the maintainer is trusted and the > patch is applied without testing. A committer is always responsible for his/her commits and so should do at least minimal testing of any patches even if it is from a maintainer. > > 2) I have very well aware that people dedicate their own time, etc, and > I think that explains why the PRs are getting cherry picked. But > seriously, shouldn't there be a policy to process these PRs in order? Not really, since some PRs might require a *lot* of work (and/or might be controversial) and thus could block other, far simpler, PRs if they were taken strictly in order. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 07:58:08 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC551065674 for ; Wed, 27 Apr 2011 07:58:08 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3CD8FC12 for ; Wed, 27 Apr 2011 07:58:07 +0000 (UTC) Received: by vws18 with SMTP id 18so1428304vws.13 for ; Wed, 27 Apr 2011 00:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=x72H5Kdi+VBav37RY0dnJO8+JsU2a2iZNlfDlCeWV+o=; b=d6GQ2C680eMtCc8sFlVo9839J82Rkra87m5rhwlfb9wlw3pxBUurv7uxIGJDUPq3vC 5qvlhvDiAsEw8AoSQn20CLa7/OD0P/pBq63UXs/n2gmj8TD3bI9lFvTCpDQaKXNUBzr8 cAHHsSYKU9ETvq4+Y1MuGL0SuqblUFZaCjP8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=kkW6+1ISK2QgCJDHMOlzXQ+i2U2JwvtGaPBEuXFFnjtli9t7lwxQvt8B/+Ura0h5CU +7l3FohCinYRAZJLBWvJjcywldiEibfv6hp63a95Efojcpdm7NCJN1uvpL3mvpyRde9J iL6T7SY0kS7oEzAVf7KbCnjMxywI+DiAzBbkY= Received: by 10.52.186.104 with SMTP id fj8mr2707530vdc.209.1303891087185; Wed, 27 Apr 2011 00:58:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.167.40 with HTTP; Wed, 27 Apr 2011 00:57:47 -0700 (PDT) In-Reply-To: <4DB7B237.7000603@marino.st> References: <4DB7B237.7000603@marino.st> From: arrowdodger <6yearold@gmail.com> Date: Wed, 27 Apr 2011 11:57:47 +0400 Message-ID: To: John Marino Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 07:58:08 -0000 On Wed, Apr 27, 2011 at 10:05 AM, John Marino wrote: > Several days ago, I submitted a patch for a port I maintain: > ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release version and > add C++" > > Nobody has touched it, but many other PRs after that submission have been > assigned, etc. > Ha, i've submitted mine about two months ago and still no luck. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 08:23:24 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69BC6106566B for ; Wed, 27 Apr 2011 08:23:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2978B8FC1B for ; Wed, 27 Apr 2011 08:23:24 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QF01r-000CsJ-I6 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 10:23:23 +0200 Date: Wed, 27 Apr 2011 10:23:23 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110427082323.GI34314@home.opsec.eu> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> <20110427071543.GD73524@comcast.net> <20110427074958.GA28824@owl.midgard.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427074958.GA28824@owl.midgard.homeip.net> Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 08:23:24 -0000 Hi! > > No, it's more than that. I got the distinct impression that many of the > > committers would be unhappy if I took maintainership of some of the > > ports I might identify as "popular", because it would interfere with > > their plans to trim the portstree. > Then you have misunderstood things. I don't think anybody would be > unhappy if you (or anybody else) took maintainership of one or more of > the currently unmaintained ports. There are two things. Becoming a maintainer seems to be really easy. Having one's PRs committed is a bit more difficult and sometimes takes 4-6 weeks (I had a case recently with 155399 and 155400). Maybe, if maintainer can "somehow easily" become ports committer, this hurdle might be lower ? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 08:32:55 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78FE71065677; Wed, 27 Apr 2011 08:32:55 +0000 (UTC) (envelope-from adrik@salesmanager.nl) Received: from www.salesmanager.nl (mail.salesmanager.nl [213.201.133.38]) by mx1.freebsd.org (Postfix) with ESMTP id 19B5C8FC16; Wed, 27 Apr 2011 08:32:54 +0000 (UTC) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 27 Apr 2011 10:20:47 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD Port: ntp-4.2.7p78 Thread-Index: AcwEtAK/kdKhuHUqScmz7r2JQaiw6A== From: "Adri Koppes" To: Cc: ports@FreeBSD.org Subject: FreeBSD Port: ntp-4.2.7p78 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 08:32:55 -0000 Dear Mr. I noticed the ntp-devel port has not been updated in nearly 6 months. The port currently has ntp version 4.2.7p78, while the current development version at ntp.org is 4.2.7p158. Do you have any plans in the near future to keep the development ntp port more up to date with ntp.org? Best regards, Adri Koppes From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 08:39:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B2AD106566C for ; Wed, 27 Apr 2011 08:39:50 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 95C4A8FC08 for ; Wed, 27 Apr 2011 08:39:49 +0000 (UTC) Received: by fxm11 with SMTP id 11so1383994fxm.13 for ; Wed, 27 Apr 2011 01:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:content-type; bh=Mm27LI1eYRArOjlPH6cRICMe5WxV5T4PYw4K9AzlHtI=; b=CezWCC5uIk1hchLE1Qgg78OSfGoSrTBKRvtdy9y/U0P79OteN3oVtcfR2z0MWXY0fz spkUlTFQP5osao7lX3widwKqftayTk7c6dAT3GJAGDUC2Sh7m8jwvwnpH5RE2ZhQ0gAe PfLInMu5rJW3os6lLOV6lZyZwrbM0hYgjP138= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=RXGhymLr6zKkQRIvXF+fsFeeRTDFiLeaKrTmTCgKL5uzznAMGuheS3DdwN8ZlqwJFZ 9GVw2JcjrXifL8tBdczgq/TLJYW0p4Tfe2q+ItDE1GrYFFUhU4S9wXTpSOjAJsdlpjoa UJ2Sk7ReV6LuT3gUmHCEn41a7CB5DF2p3g2xU= Received: by 10.223.57.86 with SMTP id b22mr689277fah.95.1303893588474; Wed, 27 Apr 2011 01:39:48 -0700 (PDT) MIME-Version: 1.0 Sender: baptiste.daroussin@gmail.com Received: by 10.223.110.197 with HTTP; Wed, 27 Apr 2011 01:30:56 -0700 (PDT) In-Reply-To: <4DB77D78.1010503@FreeBSD.org> References: <4DB77D78.1010503@FreeBSD.org> From: Baptiste Daroussin Date: Wed, 27 Apr 2011 10:30:56 +0200 X-Google-Sender-Auth: KZgDkXCbBhaEsCZWCD-MY75nHXg Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 08:39:50 -0000 > Where is the current list of deprecated ports? > You can find the deprecated ones here http://www.freshports.org/ports-deprecated.php and the one set to expire there : http://www.freshports.org/ports-expiration-date.php regards, Bapt From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 09:15:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 763D8106564A for ; Wed, 27 Apr 2011 09:15:50 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2D51C8FC18 for ; Wed, 27 Apr 2011 09:15:49 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1QF0pV-0001RO-T1 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 10:15:48 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QF0pV-0001Yy-O0 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 10:14:41 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4) with ESMTP id p3R9EfOc057652 for ; Wed, 27 Apr 2011 10:14:41 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4/Submit) id p3R9Efeu057651 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 10:14:41 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Wed, 27 Apr 2011 10:14:41 +0100 From: Anton Shterenlikht To: freebsd-ports@freebsd.org Message-ID: <20110427091441.GA50124@mech-cluster241.men.bris.ac.uk> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB73EFD.1070502@FreeBSD.org> <20110426181554.6ddd9393@seibercom.net> <20110426225556.GF38579@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110426225556.GF38579@comcast.net> User-Agent: Mutt/1.4.2.3i Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 09:15:50 -0000 On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: > > My search for "popularity" metrics is intended to point me, as a > maintainer, to ports I might want to adopt now, rather than wait for > someone to complain about them. Everything *I* use is already > maintained, so I've moved on to looking for things other people might > need. But I don't want to waste my time on something that nobody uses. > :) Interesting.. I used this sh(1) script to find unmaintained ports that I use. (I couldn't find a way to do the job with the existing tools like pkg_info or portmaster): #!/bin/sh prefix=/usr/ports/ makefile=/Makefile for file in `pkg_info -oxa | grep "/"` do yes=`grep MAIN ${prefix}${file}${makefile} | grep ports` if [ -n "$yes" ] then echo $file fi done I got: print/libpaper graphics/libwmf print/mgv x11-toolkits/open-motif devel/t1lib print/transfig textproc/urlview graphics/xfig all of which I use daily, either directly of via dependencies (xpdf or ImageMagick). So if you have the time and determination, I'd be extremely grateful if you decide to take up the maintainership of either of these ports. Many thanks Anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 10:28:33 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1D27106566B for ; Wed, 27 Apr 2011 10:28:33 +0000 (UTC) (envelope-from freebsdlists-ports@chillibear.com) Received: from mail.sundive.org (mail.sundive.org [212.13.197.214]) by mx1.freebsd.org (Postfix) with ESMTP id 376F68FC17 for ; Wed, 27 Apr 2011 10:28:32 +0000 (UTC) Received: from [87.112.169.120] (helo=[192.168.0.44]) by sundive.org with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QF1XX-0006Wl-T7; Wed, 27 Apr 2011 11:00:17 +0100 User-Agent: Microsoft-Entourage/12.29.0.110113 Date: Wed, 27 Apr 2011 10:58:31 +0100 From: Eric To: Message-ID: Thread-Topic: saving a few ports from death Thread-Index: AcwEwam/O5uqV9slpky3RULs5sffOw== In-Reply-To: <20110427091441.GA50124@mech-cluster241.men.bris.ac.uk> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam: No X-bounce-key: sundive.org-1; freebsdlists-ports@chillibear.com; 1303900203; 695df531; Cc: Anton Shterenlikht Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 10:28:33 -0000 > From: Anton Shterenlikht > Date: Wed, 27 Apr 2011 10:14:41 +0100 > To: > Subject: Re: saving a few ports from death > > On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: >> >> My search for "popularity" metrics is intended to point me, as a >> maintainer, to ports I might want to adopt now, rather than wait for >> someone to complain about them. Everything *I* use is already >> maintained, so I've moved on to looking for things other people might >> need. But I don't want to waste my time on something that nobody uses. >> :) > > Interesting.. > > I used this sh(1) script to find > unmaintained ports that I use. > (I couldn't find a way to do the > job with the existing tools like > pkg_info or portmaster): > > #!/bin/sh > > prefix=/usr/ports/ > makefile=/Makefile > > for file in `pkg_info -oxa | grep "/"` > do > yes=`grep MAIN ${prefix}${file}${makefile} | grep ports` > if [ -n "$yes" ] > then > echo $file > fi > done > [SNIP] Small observation, since that script picks up all of us who use 'ports' in our maintainer email addresses (myself for example), might I suggest the following tweak to your script (full address and checking for file existence): #!/bin/sh prefix=/usr/ports/ makefile=/Makefile for file in `pkg_info -oxa | grep "/"` do if test -f ${prefix}${file}${makefile} then yes=`grep MAIN ${prefix}${file}${makefile} | grep -i 'ports@freebsd\.org'` if [ -n "$yes" ] then echo $file fi fi Done Although in only greping makefiles that exist it doesn't alert you to your installed ports when the port has been removed from the tree... It's an interesting situation and I wonder if there is a tool (I suppose akin to portaudit) that alerts sys admins when ports they have installed are depreciated or maintainers drop them? Obviously one can sign up for the various types of alerts from Freshports, but I expect a few people here have rolled their own periodic alert tools... Regards Eric From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 11:36:03 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9E9106564A for ; Wed, 27 Apr 2011 11:36:03 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gx0-f196.google.com (mail-gx0-f196.google.com [209.85.161.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3BBF68FC14 for ; Wed, 27 Apr 2011 11:36:02 +0000 (UTC) Received: by gxk19 with SMTP id 19so266359gxk.7 for ; Wed, 27 Apr 2011 04:36:02 -0700 (PDT) Received: by 10.236.97.46 with SMTP id s34mr2498573yhf.491.1303904162288; Wed, 27 Apr 2011 04:36:02 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id 27sm340018yhl.25.2011.04.27.04.36.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 04:36:01 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKK3z3Nvbz2CG54 for ; Wed, 27 Apr 2011 07:35:59 -0400 (EDT) Date: Wed, 27 Apr 2011 07:35:58 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427073558.439bf198@seibercom.net> In-Reply-To: <20110427074958.GA28824@owl.midgard.homeip.net> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> <20110427071543.GD73524@comcast.net> <20110427074958.GA28824@owl.midgard.homeip.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 11:36:03 -0000 On Wed, 27 Apr 2011 09:49:58 +0200 Erik Trulsson articulated: > On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote: > > On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote: > > > > > >You're just sulking because your idea of identifying popular ports > > >wasn't met with enthusiasm. > > > > > > > No, it's more than that. I got the distinct impression that many > > of the committers would be unhappy if I took maintainership of some > > of the ports I might identify as "popular", because it would > > interfere with their plans to trim the portstree. > > > Then you have misunderstood things. I don't think anybody would be > unhappy if you (or anybody else) took maintainership of one or more of > the currently unmaintained ports. > What plans there are, are not so much about trimming the portstree in > general but trimming the number of unmaintained ports. > > What is met with uninterest is your plans to identify "popular" ports. > > > > Re-read the thread. At every point I'm talking about looking for > > ports I (and others) might want to maintain, as a service to their > > users. Now ask yourself why I've been getting so much resistance > > to that, when we keep hearing how deprecated ports can be easily > > resurrected if someone steps up to maintain them? > > Actually you spend much time speaking about/looking for "popular" > ports and that is what is met with uninterest. > If you want to take maintainership of a port because you personally > use that port and want to have it working, that is great. > If you want to take maintainership of a port because you believe that > it is a "popular" port, then go ahead, just don't expect much help > with identifying such ports. > > > > > Every response from the committers ignored what I said I was trying > > to do, and instead repeated the same old arguments about stale, > > unfetchable, broken or superceded ports. That "talking points" > > response tells me that they didn't want me doing what I was doing > > to buck an already-established policy of letting unmaintained ports > > die unless and until someone complains. > > (Actually the policy is that unmaintained and non-working ports should > be let to die, unless somebody steps up to fix the port and take > maintainership.) > > Nobody is stopping you from assuming maintainership of one or more of > those unmaintained ports, and thus preventing them from being removed. I concur with Erik. I think you are totally missing the point of the original post. The desired wish was to remove dead ports that could not be fetched, or would not build. Possibly, even superseded ports; although that was not specifically mentioned I don't believe. In to many of those cases those ports have no formal maintainer. Unfortunately, some do. In any case, it was proposed that those said ports be removed. Ports that are current would not be affected. As you stated, your ports are current and in working order. This proposal would therefore not effect you unless I am also misreading the intent of the proposal. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The more we disagree, the more chance there is that at least one of us is right. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 11:54:41 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B6881065670 for ; Wed, 27 Apr 2011 11:54:41 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yw0-f68.google.com (mail-yw0-f68.google.com [209.85.213.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1A0988FC08 for ; Wed, 27 Apr 2011 11:54:40 +0000 (UTC) Received: by ywt2 with SMTP id 2so269734ywt.7 for ; Wed, 27 Apr 2011 04:54:40 -0700 (PDT) Received: by 10.236.185.66 with SMTP id t42mr2625360yhm.335.1303905280311; Wed, 27 Apr 2011 04:54:40 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id i10sm347913yhd.10.2011.04.27.04.54.38 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 04:54:39 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKKTT1Q32z2CG54 for ; Wed, 27 Apr 2011 07:54:37 -0400 (EDT) Date: Wed, 27 Apr 2011 07:54:36 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427075436.70ae18ac@seibercom.net> In-Reply-To: References: <4DB7B237.7000603@marino.st> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 11:54:41 -0000 On Wed, 27 Apr 2011 11:57:47 +0400 arrowdodger <6yearold@gmail.com> articulated: > On Wed, Apr 27, 2011 at 10:05 AM, John Marino > wrote: > > > Several days ago, I submitted a patch for a port I maintain: > > ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release > > version and add C++" > > > > Nobody has touched it, but many other PRs after that submission > > have been assigned, etc. > > Ha, i've submitted mine about two months ago and still no luck. Personally, I believe that the current system, if not partially broken, is far from ideal. I would prefer to see a system where each submitted PR is assigned a specific number (I believe it is actually) and then assigned in numeric order to the next available committer. That committer would then be responsible for either committing the PR/Port/Whatever within a preset time frame, or informing the original submitter why the said article was not/could not be approved at the present time. Allowing a submitter to languish while pondering what has become of their document certainly does seem justified. I am sure that the old, "But they are all volunteers", or some such tirade will erupt. It must be remembered that those who submit items for approval are also volunteers. They deserve at least as much respect as those who are actively working on those submitted items. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Every time you manage to close the door on Reality, it comes in through the window. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 12:00:24 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7CE11065693 for ; Wed, 27 Apr 2011 12:00:24 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8248FC14 for ; Wed, 27 Apr 2011 12:00:24 +0000 (UTC) Received: by bwz12 with SMTP id 12so1872434bwz.13 for ; Wed, 27 Apr 2011 05:00:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=OmrDB4p1eZLyVepQ6Vb8uK0SE7KedDPmCuOTAe81//w=; b=Z9s5grbqhXCVw3UPJ+7ZcT7DwA93L2nf2oV2vp6avuMC5O2kl0JPZXVsc+9jVBt6C7 uQQ4DrIsAl/VCHm23IFp9XGKePYRR2NUk8+b9fYT7MxpUgCCOTJovNbJlGuUC5WM/jPE XBH8hXG33WX5o0cXlmrr83o3ScYsFySW8SzvU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=JQKHhpn9vh8+lei7oecRxswvJGYVZWazOvkW72LzUkkiGccW5RPw1r4soc5Hdxcs0p AvSgo6b64Wsl889kNtWlBoX1n4yjj/EU7IJEyUfvmtgZXUNswpYy/eRp9z153JGukBTx jElIOwIIqF75eAcfnyHyXWqm2VfSCYyR/vd3w= MIME-Version: 1.0 Received: by 10.204.19.76 with SMTP id z12mr1846277bka.205.1303905617611; Wed, 27 Apr 2011 05:00:17 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Wed, 27 Apr 2011 05:00:17 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Wed, 27 Apr 2011 05:00:17 -0700 (PDT) In-Reply-To: <20110427075436.70ae18ac@seibercom.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> Date: Wed, 27 Apr 2011 13:00:17 +0100 Message-ID: From: Chris Rees To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 12:00:24 -0000 On 27 Apr 2011 12:55, "Jerry" wrote: > > On Wed, 27 Apr 2011 11:57:47 +0400 > arrowdodger <6yearold@gmail.com> articulated: > > > On Wed, Apr 27, 2011 at 10:05 AM, John Marino > > wrote: > > > > > Several days ago, I submitted a patch for a port I maintain: > > > ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release > > > version and add C++" > > > > > > Nobody has touched it, but many other PRs after that submission > > > have been assigned, etc. > > > > Ha, i've submitted mine about two months ago and still no luck. > > Personally, I believe that the current system, if not partially broken, > is far from ideal. I would prefer to see a system where each submitted > PR is assigned a specific number (I believe it is actually) and then > assigned in numeric order to the next available committer. That > committer would then be responsible for either committing the > PR/Port/Whatever within a preset time frame, or informing the original > submitter why the said article was not/could not be approved at the > present time. Allowing a submitter to languish while pondering what has > become of their document certainly does seem justified. > > I am sure that the old, "But they are all volunteers", or some such > tirade will erupt. It must be remembered that those who submit items for > approval are also volunteers. They deserve at least as much respect as > those who are actively working on those submitted items. How do you define respect? I find the committers extremely respectful. Chris From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 12:40:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 228CD106566B for ; Wed, 27 Apr 2011 12:40:49 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id CFDD58FC17 for ; Wed, 27 Apr 2011 12:40:48 +0000 (UTC) Received: by vws18 with SMTP id 18so1639802vws.13 for ; Wed, 27 Apr 2011 05:40:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=Ibe/NSwqS5D/TkNCaUQxtyUher6919i03fejxCJl/Tg=; b=GXEQ0y6ES6g7am/+ENzj0ie83TIjgcwVsLA5O4nbJZn+F5nNk8Wd+5wnKQHJi6gAmd T5yWUtJaLYs+gQVsH3Zmmu7I/SDDBzBMMR6FVZR2U+1kTGNNdKuHH+tO07R5HU1GaNGt q/dPrJRnDOEX2awkEtr+gqyHYuqjjCQIjSdcc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=E8qV/ApBgtp1p/QHfi+uMMCYrBn7I2Y4IQ2oHdqSPn8whCdfXnvBJpuTEp9PaQDwvY 4DDO9LflzJr1wqGkLHebGiDv4WUBvyRM3U2dX7RD8Ziw3sqc9b0gbonuTcLSAmCK2TUJ MfwAnClolCXfc4Q71b/KCYrJlX+EoR5+XAzjg= Received: by 10.52.108.8 with SMTP id hg8mr3147929vdb.100.1303908048097; Wed, 27 Apr 2011 05:40:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Wed, 27 Apr 2011 05:40:18 -0700 (PDT) In-Reply-To: <20110427060917.GB73524@comcast.net> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> From: Eitan Adler Date: Wed, 27 Apr 2011 08:40:18 -0400 Message-ID: To: freebsd-ports@freebsd.org, lists@opsec.eu, corky1951@comcast.net Content-Type: text/plain; charset=UTF-8 Cc: Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 12:40:49 -0000 If after this thread you still want to drop maintership I'd like the following: >>> deskutils/teapot >>> math/ised >>> security/ccrypt >>> sysutils/moreutils >>> sysutils/moreutils-parallel >> I've been told that we shouldn't be looking for reasons to save any > unmaintained port, What you have been told is "no-one steps up to (a) fix the problem, (b) take maintainership and (c) _continue_ with maintainership. Well, in that case, the port does not _deserve_ to live. After all, no-one cares about it. If they did, they'd take care of (a) thru (c) above." If you are stepping up to do the work that is great and we thank you for that! We we don't want is people who only volunteer for part (a) and don't continue with (b) and (c). This is because the work for fixing these ports falls on the rest of the community, and mainly the committers if it were to break again or when making "sweeping" changes to the tree. A large amount of the work that goes into things like a gmake or autotools upgrade is fixing individual ports that broke. If people step up to continue to maintain the now deprecated ports I see nothing wrong with helping them to do so. If that someone is you - even better! > and I was specifically told this in response to my > efforts to identify ports that have a lot of users. Merely finding "popular" ports does not help. We need people who have the time and energy to maintain the ports. I do not want to say that "we are a volunteer project" and as such are forgiven however such a model does change how we must do things. We can not "assign" ports to people, even committers, unless they agree to do the work. Furthermore we can use maintainership to judge popularity if indirectly and imperfectly. If no one steps up to do the work of all the port's users it is not that popular. If you are the one stepping up to do the work I would urge you continue! However merely pointing at the port and saying "this needs to be fixed" won't help as someone still has to fix it. > So I don't think current policy supports the conclusion that "we need to find someone to take them soon." The policy is one of passiveness and this seems to be the main difference between the others and the you. Correct me if I am wrong but you believe that we should be trying as hard as we can to find somehow or someone to save these ports. Others believe that if someone wants to they can step up and do the work to save these ports. On Wed, Apr 27, 2011 at 4:23 AM, Kurt Jaeger wrote: > Then you have misunderstood things. I don't think anybody would be > unhappy if you (or anybody else) took maintainership of one or more of > the currently unmaintained ports. > There are two things. Becoming a maintainer seems to be really easy. Becoming a maintainer requires that you commit to do the work to ensure that a certain program works on FreeBSD. How easy this is depends on you. > Having one's PRs committed is a bit more difficult and sometimes > takes 4-6 weeks (I had a case recently with 155399 and 155400). There is a lot of work that has to be done in the background even if no new ports are added. Things like the gmake upgrade and new ports features take a lot of time. Furthermore adding a port seems to be a "trivial" task, however the committers have to (a) fix it up if it is formatted badly (b) test it in a tinderbox and only then (c) commit it. This takes more time than just "cvs commit". A lot of work has been done in recent years to make this process faster and I'm sure more could be done - but a lot of people don't realize how much work goes on behind the scenes -- Eitan Adler From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 12:51:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F572106566B for ; Wed, 27 Apr 2011 12:51:22 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp03.lnh.mail.rcn.net (smtp03.lnh.mail.rcn.net [207.172.157.103]) by mx1.freebsd.org (Postfix) with ESMTP id C28388FC0C for ; Wed, 27 Apr 2011 12:51:21 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 08:51:22 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id AVO22950; Wed, 27 Apr 2011 08:51:20 -0400 Received-SPF: None identity=pra; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.91.204; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@jerusalem.litteratus.org.litteratus.org"; x-conformance=sidf_compatible Received: from unknown (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.91.204]) by smtp01.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 08:51:14 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19896.4396.161941.282904@jerusalem.litteratus.org> Date: Wed, 27 Apr 2011 08:50:52 -0400 To: freebsd-ports@freebsd.org In-Reply-To: <20110427075436.70ae18ac@seibercom.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr17.lnh.mail.rcn.net) Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 12:51:22 -0000 Jerry writes: > > Ha, i've submitted mine about two months ago and still no luck. > > Personally, I believe that the current system, if not partially > broken, is far from ideal. I would prefer to see a system where > each submitted PR is assigned a specific number (I believe it is > actually) and then assigned in numeric order to the next > available committer. Not all committers are created equal. Asking Joe-the-fonts- guru to work on Mary's network monitoring application is probably not productive. Keeping a centralized list of who/what pairs - more importantly, keeping it useful - is another job on someone's desk. Are you that someone? > I am sure that the old, "But they are all volunteers", or some > such tirade will erupt. Not a tirade, but ... guilty. > It must be remembered that those who submit items for approval > are also volunteers. They deserve at least as much respect as > those who are actively working on those submitted items. Am I correct you are asking for a (far) higher level of dedication from the committers than from those who submit changes? Consider the port that goes untouched (in spite of substantial upstream changes) for months or even years; someone picks up the torch, and the poor committer gets N-thousend lines of new features, security patches, and dependency changes dumped on them to be checked in ... how long was that? Do I think there are flaws in the current system? Sure. But as long as we're faced with this particular choice of evils - slow updating versus lowered quality - I vote "first, do no harm". Respectfully, Robert Huff From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 12:54:24 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C9871065695 for ; Wed, 27 Apr 2011 12:54:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id CAD7A8FC15 for ; Wed, 27 Apr 2011 12:54:23 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QF4G8-000HCv-MG for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 14:54:24 +0200 Date: Wed, 27 Apr 2011 14:54:24 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110427125424.GJ34314@home.opsec.eu> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 12:54:24 -0000 Eitan Adler wrote: > On Wed, Apr 27, 2011 at 4:23 AM, Kurt Jaeger wrote: > > Then you have misunderstood things. I don't think anybody would be > > unhappy if you (or anybody else) took maintainership of one or more of > > the currently unmaintained ports. > > > There are two things. Becoming a maintainer seems to be really easy. > > Becoming a maintainer requires that you commit to do the work to > ensure that a certain program works on FreeBSD. How easy this is > depends on you. Yes, that's how I handle it. > > Having one's PRs committed is a bit more difficult and sometimes > > takes 4-6 weeks (I had a case recently with 155399 and 155400). > > There is a lot of work that has to be done in the background even if > no new ports are added. I'm aware of this. What I see is that only a few ports committer do most of the commits of the small leaf ports. This would burn me out as well, if I had to do it 8-} So, if the maintainers of the small leaf ports would be able to commit their work themselves, it would free the ports committers with the large ports projects on their hands to work on those ? Would this work ? > Things like the gmake upgrade and new ports > features take a lot of time. Furthermore adding a port seems to be a > "trivial" task, however the committers have to (a) fix it up if it is > formatted badly (b) test it in a tinderbox and only then (c) commit > it. I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to test. I do not use a tinderbox, as I assume considerable complexity to set one up. Does using a tinderbox make a large difference ? > This takes more time than just "cvs commit". A lot of work has > been done in recent years to make this process faster and I'm sure > more could be done - but a lot of people don't realize how much work > goes on behind the scenes I agree, the infrastructure is massive! -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 12:54:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48A00106566B for ; Wed, 27 Apr 2011 12:54:50 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yx0-f196.google.com (mail-yx0-f196.google.com [209.85.213.196]) by mx1.freebsd.org (Postfix) with ESMTP id EAD9A8FC19 for ; Wed, 27 Apr 2011 12:54:49 +0000 (UTC) Received: by yxt3 with SMTP id 3so182779yxt.7 for ; Wed, 27 Apr 2011 05:54:49 -0700 (PDT) Received: by 10.91.10.7 with SMTP id n7mr1946809agi.5.1303908889014; Wed, 27 Apr 2011 05:54:49 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id q8sm760148ann.45.2011.04.27.05.54.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 05:54:48 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKLpt4kcDz2CG54 for ; Wed, 27 Apr 2011 08:54:46 -0400 (EDT) Date: Wed, 27 Apr 2011 08:54:45 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427085445.391a015e@seibercom.net> In-Reply-To: References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 12:54:50 -0000 On Wed, 27 Apr 2011 13:00:17 +0100 Chris Rees articulated: > How do you define respect? I find the committers extremely respectful. Allowing a submitter to languish for an indeterminate period without any notification of what is transpiring with his/her submission is not respectful, it is benign neglect. As I stated, each submitted item should be handled in a basic FIFO order unless there is a specific reason for not doing so. If such reason exists then the original submitter should be informed of this irregularity. Waiting for months while items submitted after the submitter's item are approved without notifying the submitter of why is certainly not friendly or respectful, unless of course you work for the motor vehicle or parking department in which case it is just business as usual. I have been at both extremes of the spectrum on this, having had items committed within days and conversely waiting for an extended period of time and finally asking specifically why an item was not committed before anything happened. The present system is broken, or at the very least poorly implemented, unless the goal is to keep a submitter in the dark. I reiterate, there is no logical reason to jump over one user's submission and proceed with another user's submission without formally notifying the submitter of the older item why his/her item is being bypassed. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:11:00 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BA73106564A for ; Wed, 27 Apr 2011 13:11:00 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id DB1D58FC12 for ; Wed, 27 Apr 2011 13:10:59 +0000 (UTC) Received: by vws18 with SMTP id 18so1671320vws.13 for ; Wed, 27 Apr 2011 06:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=vXaDvWW07uXrykKRE41/zMf46hxBcJujdUrdXo6orgc=; b=CgSD/XNXJvxI25DkV+mFkrQ5pw+vrl9AjuUpFhqdUhr7MXzeZLJkzpfLeJ6GlTDB5B +VzLcxFOL+FZt8OfcYPv9BwkBYceGITqVxM6fsti/Gjt6OCcZ9HmxjbIpD72G7+3z+rf 9i6kj7qGCAc4bHasTqt6J6wOWxXH/BxLw8mbs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=hrtyP+dXrQG68q+io/JAodCRze8yC+MCwY2OkD4WhEvrUWI9c5+qZ1Dy0CdNa3NpuL vRo35nyfT4FzkEzAdu7DBEOy7U0yJ+EuJX+nnSa2f1FyjvlV0FZODXbrzeNMOBvUJxzd z1Y5+367a/GX8W9lcDJRoxFVMpWNqExcPHVDw= Received: by 10.52.75.165 with SMTP id d5mr1082851vdw.300.1303909859064; Wed, 27 Apr 2011 06:10:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Wed, 27 Apr 2011 06:10:29 -0700 (PDT) In-Reply-To: <20110427125424.GJ34314@home.opsec.eu> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <20110427125424.GJ34314@home.opsec.eu> From: Eitan Adler Date: Wed, 27 Apr 2011 09:10:29 -0400 Message-ID: To: Kurt Jaeger Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:11:00 -0000 > So, if the maintainers of the small leaf ports would be able > to commit their work themselves, it would free the ports committers > with the large ports projects on their hands to work on those ? > > Would this work ? If you look through this list's archives I actually proposed this idea myself once ;-) The problem is that (a) often maintainers don't do the work 100% well. I am not knocking everyone - but just because you _say_ you will do the work doesn't mean you _will_ do it. Furthermore becoming a committer implies a certain level of trust beyond just "you can submit patches" as you get shell access to the FreeBSD machines and other such things. > > I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to > test. I do not use a tinderbox, as I assume considerable complexity > to set one up. You may want to mention that you use said three machines in the PR - it would be of service. Different committers have differing policies for what they will commit. Some will accept that, others will want tinderbox logs, and others will always test every patch themselves. > > Does using a tinderbox make a large difference ? Using a tinderbox ensures that a "clean" build works (ie that there are no missing dependencies). > I agree, the infrastructure is massive! 23,000 ports held together with Makefiles - I'm still surprised it works ;) -- Eitan Adler From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:17:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54144106566C for ; Wed, 27 Apr 2011 13:17:47 +0000 (UTC) (envelope-from sjk4015@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2311C8FC13 for ; Wed, 27 Apr 2011 13:17:46 +0000 (UTC) Received: by pvg11 with SMTP id 11so1549764pvg.13 for ; Wed, 27 Apr 2011 06:17:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=CDert60beE4JKJbdOPQqlvnEslPZXrXR/YxkzM9+usk=; b=aRxVez5aD+0PHJRivx2jeaMtP4kV1hKsh3tXpAs/QHe1zFytcCFb+gkH8hXLU8lRQH 7DUtHYIRN8W56Rl5+gLdMzeVa3eD6yiGOCHSbU3SPDhKMXhJxwf+ATtDnrJlFa+R5ocT axqzyZNQyYsOgr1enJiiGNEv7+3QsUl+YA/FQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=OHg4tGpTreFWaiaAEaVZq8vgQdEtPabU67QpzNA/bToXREWpvCZsbHWkrVT+m4agAP uZ8Dvz2ipHrozV0IN+lmtXG+KsWiRwhjsT0tXajBeGgFmT4EJx2IhfvDv5vNDpxS0350 Tcr5leLVQMUkSg4eVylyhhEMqv9f6LhNPunMw= MIME-Version: 1.0 Received: by 10.68.58.226 with SMTP id u2mr2226303pbq.459.1303910266538; Wed, 27 Apr 2011 06:17:46 -0700 (PDT) Sender: sjk4015@gmail.com Received: by 10.68.64.42 with HTTP; Wed, 27 Apr 2011 06:17:46 -0700 (PDT) In-Reply-To: <20110427075436.70ae18ac@seibercom.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> Date: Wed, 27 Apr 2011 09:17:46 -0400 X-Google-Sender-Auth: MlFb-HjfgMjlOq8MfWavRngcaYs Message-ID: From: Steven Kreuzer To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:17:47 -0000 > Personally, I believe that the current system, if not partially broken, > is far from ideal. Speaking as a ports committer, I do agree with you that the current workflow that we have in place is less then ideal for the size of the ports tree as well as the number of patches that we receive. When the current workflow was first developed, the ports tree was much smaller and easier to work with. It has grown to over 23,000 ports and we are starting to see scaling issues. However, these issues have been known for quite some time. Behind the scenes, numerous ideas have been kicked around on how to better deal with contributions from independent developers, how to accept and review patches quicker and how to generally streamline our workflow. Unfortunately, the problem really becomes that unless we want to severely disrupt what we currently have in place for an extended period of time, we can really only make small gradual changes and hope that eventually we end up in a better position then when we started. > I would prefer to see a system where each submitted > PR is assigned a specific number (I believe it is actually) and then > assigned in numeric order to the next available committer. That > committer would then be responsible for either committing the > PR/Port/Whatever within a preset time frame, or informing the original > submitter why the said article was not/could not be approved at the > present time. Allowing a submitter to languish while pondering what has > become of their document certainly does seem justified. The problem with this system is that certain developers sometimes only work on a certain subset of the tree. Your fifo system does not take that into account For example, I maintain quite a few perl modules and often grab PRs for perl related things. This is mainly because I have an interest in keeping the perl stuff in good shape because I use it every day. I generally never deal with any PR that deals with ruby since I don't use ruby. As a result, I am not familiar with the ruby specific knobs in the ports tree. I would rather let another developer who is familiar with those and has an interest in keeping ruby well maintained deal with those PRs. Unfortunately, from time to time, the person who deals with the ruby stuff could be swamped with work or family issues and is unable to attend to it as quickly as I may have been able to. Would you prefer to wait a little while longer for that person to grab the PR, or would you rather have me commit the patch and possibly break your application running in production? Also, with your fifo system, what would happen if I don't commit an update within the allotted time frame? Perhaps the happy medium is that if you submit a PR and it doesn't get assigned for a few days, maybe ask in #bsdports on irc if someone could take a look at the PR. If you submit a patch and it does get assigned but a few days goes by and it doesn't get committed, we could update the PR to let you know that we haven't had a chance to look at it but hope to have a little bit of time in the next few days to take care of it. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:33:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8D2C106566C for ; Wed, 27 Apr 2011 13:33:02 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yi0-f68.google.com (mail-yi0-f68.google.com [209.85.218.68]) by mx1.freebsd.org (Postfix) with ESMTP id 763038FC08 for ; Wed, 27 Apr 2011 13:33:02 +0000 (UTC) Received: by yih10 with SMTP id 10so281050yih.7 for ; Wed, 27 Apr 2011 06:33:01 -0700 (PDT) Received: by 10.150.210.15 with SMTP id i15mr449023ybg.377.1303911181684; Wed, 27 Apr 2011 06:33:01 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id p41sm801326ybk.14.2011.04.27.06.33.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 06:33:00 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKMfz18xWz2CG6F for ; Wed, 27 Apr 2011 09:32:59 -0400 (EDT) Date: Wed, 27 Apr 2011 09:32:58 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427093258.3966cfd2@seibercom.net> In-Reply-To: <19896.4396.161941.282904@jerusalem.litteratus.org> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:33:02 -0000 On Wed, 27 Apr 2011 08:50:52 -0400 Robert Huff articulated: > > Jerry writes: > > > > Ha, i've submitted mine about two months ago and still no luck. > > > > Personally, I believe that the current system, if not partially > > broken, is far from ideal. I would prefer to see a system where > > each submitted PR is assigned a specific number (I believe it is > > actually) and then assigned in numeric order to the next > > available committer. > > Not all committers are created equal. Asking Joe-the-fonts- > guru to work on Mary's network monitoring application is probably > not productive. > Keeping a centralized list of who/what pairs - more > importantly, keeping it useful - is another job on someone's desk. > Are you that someone? > > > I am sure that the old, "But they are all volunteers", or some > > such tirade will erupt. > > Not a tirade, but ... guilty. > > > It must be remembered that those who submit items for approval > > are also volunteers. They deserve at least as much respect as > > those who are actively working on those submitted items. > > Am I correct you are asking for a (far) higher level of > dedication from the committers than from those who submit changes? > Consider the port that goes untouched (in spite of substantial > upstream changes) for months or even years; someone picks up the > torch, and the poor committer gets N-thousend lines of new features, > security patches, and dependency changes dumped on them to be > checked in ... how long was that? > > Do I think there are flaws in the current system? Sure. > But as long as we're faced with this particular choice of > evils > - slow updating versus lowered quality - I vote "first, do no harm". I am not sure how the Hippocratic Oath got involved here. In any case, I see no reason why the "slow" and "lowered" qualities cannot find happiness together. Please reread what I posted. I stated that if a submitter's item was to be delayed for an extended period or bypassed in favor of a later submission by another submitter then the submitter of the older item should be notified as to why and if possible given an approximate commit date. I fail to see why that would cause undo stress or an unbearable burden on the committer(s). The committer(s) could create a boiler plate document to handle just such cases. However, I do find troubling you statement regarding a large update to an older port or even a new port submission for that matter. I see no logical reason for a committer to bypass an item simple based on its size or the amount of work involved in getting it committed. After all, consider that the original submitter invested a large amount of his/her time in that same item. The only honest and fair way to handle ports request is on a FIFO basis unless a bona fied excuse can be shown to deviate from that procedure. To simplify the system, a two week limit, or whatever reasonable time frame can be agreed upon, should be put into effect. Any submitted item that cannot be committed within that time frame would require the committer to notify the submitter of such and if possible a reasonable date to complete the commit. I do not believe that, that is by any stretch of the imagination excessive. Many government and private organizations work under those same basic constraints without undo harm. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The great nations have always acted like gangsters and the small nations like prostitutes. Stanley Kubrick From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:45:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60D3A106566B for ; Wed, 27 Apr 2011 13:45:51 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gw0-f68.google.com (mail-gw0-f68.google.com [74.125.83.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1149E8FC18 for ; Wed, 27 Apr 2011 13:45:50 +0000 (UTC) Received: by gwj19 with SMTP id 19so281445gwj.7 for ; Wed, 27 Apr 2011 06:45:50 -0700 (PDT) Received: by 10.151.78.4 with SMTP id f4mr2134142ybl.240.1303911950009; Wed, 27 Apr 2011 06:45:50 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id q29sm424130ybk.25.2011.04.27.06.45.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 06:45:49 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKMxl2cYSz2CG5G for ; Wed, 27 Apr 2011 09:45:47 -0400 (EDT) Date: Wed, 27 Apr 2011 09:45:46 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427094546.798d8367@seibercom.net> In-Reply-To: References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:45:51 -0000 On Wed, 27 Apr 2011 09:17:46 -0400 Steven Kreuzer articulated: > > Personally, I believe that the current system, if not partially > > broken, is far from ideal. > > Speaking as a ports committer, I do agree with you that the current > workflow that we have in place is less then ideal for the size of the > ports tree as well as the number of patches that we receive. > > When the current workflow was first developed, the ports tree was much > smaller and > easier to work with. It has grown to over 23,000 ports and we are > starting to see scaling issues. > > However, these issues have been known for quite some time. Behind the > scenes, numerous ideas have been kicked around on how to better deal > with contributions from > independent developers, how to accept and review patches quicker and > how to generally > streamline our workflow. > > Unfortunately, the problem really becomes that unless we want to > severely disrupt what > we currently have in place for an extended period of time, we can > really only make small > gradual changes and hope that eventually we end up in a better > position then when we > started. > > > I would prefer to see a system where each submitted > > PR is assigned a specific number (I believe it is actually) and then > > assigned in numeric order to the next available committer. That > > committer would then be responsible for either committing the > > PR/Port/Whatever within a preset time frame, or informing the > > original submitter why the said article was not/could not be > > approved at the present time. Allowing a submitter to languish > > while pondering what has become of their document certainly does > > seem justified. > > The problem with this system is that certain developers sometimes only > work on a certain > subset of the tree. Your fifo system does not take that into account > > For example, I maintain quite a few perl modules and often > grab PRs for perl related things. This is mainly because I have an > interest in keeping > the perl stuff in good shape because I use it every day. I generally > never deal with > any PR that deals with ruby since I don't use ruby. As a result, I am > not familiar with > the ruby specific knobs in the ports tree. I would rather let another > developer who is > familiar with those and has an interest in keeping ruby well > maintained deal with those > PRs. Unfortunately, from time to time, the person who deals with the > ruby stuff could be > swamped with work or family issues and is unable to attend to it as > quickly as I may have > been able to. Would you prefer to wait a little while longer for that > person to grab the PR, or > would you rather have me commit the patch and possibly break your > application running in > production? > > Also, with your fifo system, what would happen if I don't commit an > update within the allotted > time frame? > > Perhaps the happy medium is that if you submit a PR and it doesn't get > assigned for a few days, > maybe ask in #bsdports on irc if someone could take a look at the PR. > If you submit a patch > and it does get assigned but a few days goes by and it doesn't get > committed, we could update the > PR to let you know that we haven't had a chance to look at it but hope > to have a little bit of time in > the next few days to take care of it. Thank you. A well thought out reply and one that I can agree with in most aspects. I think that 'UPDATING' the PR to let the submitter know that he/she has not been forgotten and to keep them aware of any problems with the PR is certainly a welcome suggestion. Unfortunately, that is rarely presently done. Certainly, we should all be able to come to some consensus as to what constitutes a reasonable time frame. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:48:55 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70610106566B for ; Wed, 27 Apr 2011 13:48:55 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp05.sth.basefarm.net (ch-smtp05.sth.basefarm.net [80.76.153.6]) by mx1.freebsd.org (Postfix) with ESMTP id F28008FC1A for ; Wed, 27 Apr 2011 13:48:54 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:30766 helo=falcon.midgard.homeip.net) by ch-smtp05.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QF56e-0000FX-HX for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 15:48:45 +0200 Received: (qmail 16341 invoked from network); 27 Apr 2011 15:48:36 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 27 Apr 2011 15:48:36 +0200 Received: (qmail 30121 invoked by uid 1001); 27 Apr 2011 15:48:36 +0200 Date: Wed, 27 Apr 2011 15:48:36 +0200 From: Erik Trulsson To: freebsd-ports@freebsd.org Message-ID: <20110427134836.GA30085@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427093258.3966cfd2@seibercom.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QF56e-0000FX-HX. X-Scan-Signature: ch-smtp05.sth.basefarm.net 1QF56e-0000FX-HX cd903afe1e314733bad1435407676a6c Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:48:55 -0000 On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: > On Wed, 27 Apr 2011 08:50:52 -0400 > > However, I do find troubling you statement regarding a large update to > an older port or even a new port submission for that matter. I see no > logical reason for a committer to bypass an item simple based on its > size or the amount of work involved in getting it committed. After all, > consider that the original submitter invested a large amount of his/her > time in that same item. Very simple. A particular committer during one particular period of time maybe only 45 minutes of free time to spend on handling PRs. If the committer estimates that one large submitted PR would take at least two hours to review, test, and commit, while another, smaller, PR would only take 30 minutes to handle. Then the committer in question would have two choices: Don't handle either submission, or handling the smaller submission, while skipping the large one and hoping that some other committer with more free time will pick up that one. I see no reason to prefer the first of these choices. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 14:13:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 849B81065675 for ; Wed, 27 Apr 2011 14:13:02 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yw0-f68.google.com (mail-yw0-f68.google.com [209.85.213.68]) by mx1.freebsd.org (Postfix) with ESMTP id 33B908FC08 for ; Wed, 27 Apr 2011 14:13:01 +0000 (UTC) Received: by ywt2 with SMTP id 2so285620ywt.7 for ; Wed, 27 Apr 2011 07:13:01 -0700 (PDT) Received: by 10.151.62.38 with SMTP id p38mr1977223ybk.12.1303913581048; Wed, 27 Apr 2011 07:13:01 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id f5sm817524ybh.13.2011.04.27.07.12.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 07:13:00 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKNY626xXz2CG5G for ; Wed, 27 Apr 2011 10:12:58 -0400 (EDT) Date: Wed, 27 Apr 2011 10:12:57 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427101257.414aaf8b@seibercom.net> In-Reply-To: <20110427134836.GA30085@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 14:13:02 -0000 On Wed, 27 Apr 2011 15:48:36 +0200 Erik Trulsson articulated: > On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: > > On Wed, 27 Apr 2011 08:50:52 -0400 > > > > However, I do find troubling you statement regarding a large update > > to an older port or even a new port submission for that matter. I > > see no logical reason for a committer to bypass an item simple > > based on its size or the amount of work involved in getting it > > committed. After all, consider that the original submitter invested > > a large amount of his/her time in that same item. > > Very simple. A particular committer during one particular period of > time maybe only 45 minutes of free time to spend on handling PRs. > If the committer estimates that one large submitted PR would take at > least two hours to review, test, and commit, while another, smaller, > PR would only take 30 minutes to handle. > > Then the committer in question would have two choices: Don't handle > either submission, or handling the smaller submission, while skipping > the large one and hoping that some other committer with more free time > will pick up that one. > I see no reason to prefer the first of these choices. If the committer cannot finish the project in their allotted time frame they simply stop and pick up from that point in their next session. I have literally hundreds of projects that I cannot complete in one day; however, I don't simply shrug them off. If I did nothing would ever get accomplished, or at best only the easiest assignments. One of the basic fallacies in your analysis is that someone else will pick up the slack. Unfortunately, our society has become over run by those who are always ready to blame others or expect others to do our job for us. Quite honestly, I find that pathetic. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 14:32:26 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB320106566B for ; Wed, 27 Apr 2011 14:32:26 +0000 (UTC) (envelope-from spotter@eastlink.ca) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 8785A8FC12 for ; Wed, 27 Apr 2011 14:32:26 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1QF5WF-0005AE-80 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 07:15:07 -0700 Date: Wed, 27 Apr 2011 07:15:07 -0700 (PDT) From: spotter To: freebsd-ports@freebsd.org Message-ID: <1303913707221-4343776.post@n5.nabble.com> In-Reply-To: <19CCC0EE-AAF8-401B-875F-F2A43E780642@huibsmeets.com> References: <19CCC0EE-AAF8-401B-875F-F2A43E780642@huibsmeets.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD Port: squeezeboxserver-7.5.3, build okay but fails to start. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 14:32:26 -0000 I am having the exact same problem with a brand new FreeBSD 8.1-RELEASE install and a fresh squeezeboxserver (v7.5.3) port build. (Slimserver was working fine under FreeBSD 6.2, until I tried to get miniDLNA working, as well, for a BluRay player access to same music library. sigh) Any solutions worked out for squeezeboxserver v7.5.3 under FreeBSD 8.1-RELEASE? -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-Port-squeezeboxserver-7-5-3-build-okay-but-fails-to-start-tp3861984p4343776.html Sent from the freebsd-ports mailing list archive at Nabble.com. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 14:52:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F35BC106566C for ; Wed, 27 Apr 2011 14:52:16 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id D63808FC14 for ; Wed, 27 Apr 2011 14:52:16 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 4706B2282A for ; Wed, 27 Apr 2011 08:31:40 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id C9C5B683D; Wed, 27 Apr 2011 10:36:25 -0400 (EDT) Date: Wed, 27 Apr 2011 10:36:25 -0400 From: Diane Bruce To: freebsd-ports@freebsd.org Message-ID: <20110427143625.GA44433@night.db.net> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> <20110427071543.GD73524@comcast.net> <20110427074958.GA28824@owl.midgard.homeip.net> <20110427073558.439bf198@seibercom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427073558.439bf198@seibercom.net> User-Agent: Mutt/1.4.2.3i Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 14:52:17 -0000 On Wed, Apr 27, 2011 at 07:35:58AM -0400, Jerry wrote: > On Wed, 27 Apr 2011 09:49:58 +0200 > Erik Trulsson articulated: > > > On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote: > > > On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote: > > > > ... > > > > > > Every response from the committers ignored what I said I was trying > > > to do, and instead repeated the same old arguments about stale, > > > unfetchable, broken or superceded ports. That "talking points" No, no and no. If you have a copy of the upstream package the port was based upon and it is open source, you can 'fork' it. Create a project on sourceforge, or Berlioz, or somewhere, put the package there, announce it get some people together to maintain it. That has the advantage of having FreeBSD minded people maintaing it upstream. That's all. Easy Peasy. That's for unfetchable ports or even superceded ports. If you prefer an older program than a supposed newer suggested replacement, you can fork the older program. That's how it works. > > (Actually the policy is that unmaintained and non-working ports should > > be let to die, unless somebody steps up to fix the port and take > > maintainership.) Exactly. > > > > Nobody is stopping you from assuming maintainership of one or more of > > those unmaintained ports, and thus preventing them from being removed. > > I concur with Erik. I think you are totally missing the point of the > original post. The desired wish was to remove dead ports that could not > be fetched, or would not build. Possibly, even superseded ports; Right. - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db Why leave money to our children if we don't leave them the Earth? From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 15:02:42 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D217B1065677 for ; Wed, 27 Apr 2011 15:02:42 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9098FC2E for ; Wed, 27 Apr 2011 15:02:39 +0000 (UTC) Received: from c-24-22-230-24.hsd1.wa.comcast.net ([24.22.230.24] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QF6GC-0001su-BL for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 11:02:37 -0400 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Wed, 27 Apr 2011 08:02:34 -0700 Date: Wed, 27 Apr 2011 08:02:34 -0700 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20110427150234.GA85280@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110427091441.GA50124@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:02:43 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Eric on Wednesday, 27 April 2011: > > From: Anton Shterenlikht > > Date: Wed, 27 Apr 2011 10:14:41 +0100 > > To: > > Subject: Re: saving a few ports from death > >=20 > > On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: > >>=20 > >> My search for "popularity" metrics is intended to point me, as a > >> maintainer, to ports I might want to adopt now, rather than wait for > >> someone to complain about them. Everything *I* use is already > >> maintained, so I've moved on to looking for things other people might > >> need. But I don't want to waste my time on something that nobody uses. > >> :) > >=20 > > Interesting.. > >=20 > > I used this sh(1) script to find > > unmaintained ports that I use. > > (I couldn't find a way to do the > > job with the existing tools like > > pkg_info or portmaster): > >=20 > > #!/bin/sh > >=20 > > prefix=3D/usr/ports/ > > makefile=3D/Makefile > >=20 > > for file in `pkg_info -oxa | grep "/"` > > do > > yes=3D`grep MAIN ${prefix}${file}${makefile} | grep ports` > > if [ -n "$yes" ] > > then > > echo $file > > fi > > done > >=20 >=20 > [SNIP] >=20 > Small observation, since that script picks up all of us who use 'ports' in > our maintainer email addresses (myself for example), might I suggest the > following tweak to your script (full address and checking for file > existence): >=20 > #!/bin/sh >=20 > prefix=3D/usr/ports/ > makefile=3D/Makefile >=20 > for file in `pkg_info -oxa | grep "/"` > do > if test -f ${prefix}${file}${makefile} > then > yes=3D`grep MAIN ${prefix}${file}${makefile} | grep -i 'ports@freebsd\.= org'` > if [ -n "$yes" ] > then > echo $file > fi > fi > Done >=20 Good catch -- even with that change, my list has 57 ports in it (including, ironically, sysutils/bsdstats). A lot of the ones on my list are requirements for other ports, though. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJNuDAKAAoJEIpckszW26+R1wMIAJtOPZHYK6fGJpsfZq2MKYvx nk1dE3Q3Z+o/d3ri5ipmnXq59zzdhVZ15Dr5Z8OwNOK9MPK0hGi/1zChlUWgbtjC 1bYKpLLXuwoMLu7CTEIdLnlWYf23OoGUdj+0p3IMmySXaBiKN7bkHZ9VaM7SqjUr JsXBy7rTDZnpAqDwzo+/uiCtMFKiOLXgD/qsit+NPuSnjwA5wRSJ43WV1IgA0+o5 yV0DQ7QQ3qE3+EjYixA6PGFim7UP1QZ9tdiJLciJ0jYe82C4KFnl5volcH8dW3gM DLF4dtXstexZyOzMOeqeP7JFgC50EHrnR2MpZvQ4Hix+KF/i2vLpJXQ+gvR4cI4= =nfpQ -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 15:04:44 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2656A1065670; Wed, 27 Apr 2011 15:04:44 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id C1C4C8FC0C; Wed, 27 Apr 2011 15:04:42 +0000 (UTC) Received: by qwc9 with SMTP id 9so1010242qwc.13 for ; Wed, 27 Apr 2011 08:04:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9eBZfRMv7Kf2ebTZ8zD6jC0iTSjrkaTrpVRFknyvkTE=; b=iQ2RvF5ejRi2a4uBGgsoGFChxIv65T+wo4WV6u6E1T0xlwctIA2oORE4bZwqkysYVl Ye96OxWftEBBSZ/6Dwu77hzFNCM50RmwOzAvRQCKee8Vu+VOFN51hnWt/LiPSB4fH5J4 Kv4QVzHP6aXa94/ofAjdJBnq/fMU50s63U3Iw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d2OCAMwLfal2RzmXRCi2AxgL180IEUavwdCHdWzL51muDEpT4dTpvp9Ve+C7x6wSHV kZ97kSdL37/Ux6IEV3lYgPH0LFo5ymgrOOqLV8ZpWglDD6zmKgbVnZ38vZ4MeV1XftJH qpYG1ycx5uI/VnGblEQx31+4mBfL23C4gzvqg= MIME-Version: 1.0 Received: by 10.224.104.80 with SMTP id n16mr1830751qao.361.1303915082095; Wed, 27 Apr 2011 07:38:02 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Wed, 27 Apr 2011 07:38:02 -0700 (PDT) In-Reply-To: <20110427050024.GA12630@lonesome.com> References: <4DB77D78.1010503@FreeBSD.org> <20110427050024.GA12630@lonesome.com> Date: Wed, 27 Apr 2011 10:38:02 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Mark Linimon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: fb-ports , Garance A Drosehn Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:04:44 -0000 On Wed, Apr 27, 2011 at 1:00 AM, Mark Linimon wrote: > I need to migrate portsmon to another server so that we can start up > these periodic emails again. > > mcl > _______________________________________________ > With the large number of ports to be maintained , tasks to be performed becomes very complex . The current structure of problem report submitting and e-mails about current problems may be modified to reduce the tasks to be performed even for slightly. On the problem report submitting page , http://www.freebsd.org/send-pr.html the following fields may be added to make it more structured and to be able to generate e-mails to maintainers directly : Remove field Category . Add the following fields : FreeBSD Version : ( Selected from a drop-down list like Category ) FreeBSD Architecture : ( Selected from list ... ) Related to ( Radio Button ) Base : Program Name : ... in Directory : ... --------------------------------------------------------- Port : Port Name in .../Latest/ Directory : ... Port Version : If there is a working version in another operating system Name : ... operating system Version : ... Port Name : ... Port Version : ... Source Repository URL : --------------------------------------------------------- Into Class field : Add item : Feature Suggestion . Under the box "How to repeat the problem" , add Which tests are applied : add Testing software available : add Testing Software URL : With the above structure , it is possible . to generate e-mails to maintainers automatically , . to eliminate problem reports when operating system or port version numbers of the respective ports changes by moving them to an archive . Problem report query page http://www.freebsd.org/cgi/query-pr-summary.cgi?query may be adapted accordingly . ........................................................... In e-mails , a more structured listing will be helpful : PR FreeBSD FreeBSD Port Port Number Version Architecture Name Version Description ----------- ------------- ------------------ --------- ---------- ----------------- In the present system , mentioning only the category with vague descriptions causes difficulty to understand structure of the problem , at least for persons foreigner to port maintenance . Also , supplying a link to problem report numbers during generation of e-mails automatically makes them easily accessible . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 15:09:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CF6C1065672 for ; Wed, 27 Apr 2011 15:09:02 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2606D8FC1A for ; Wed, 27 Apr 2011 15:09:01 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 919E52282A for ; Wed, 27 Apr 2011 09:04:29 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id E4BC4683D; Wed, 27 Apr 2011 11:09:14 -0400 (EDT) Date: Wed, 27 Apr 2011 11:09:14 -0400 From: Diane Bruce To: freebsd-ports@freebsd.org Message-ID: <20110427150914.GA44985@night.db.net> References: <20110427091441.GA50124@mech-cluster241.men.bris.ac.uk> <20110427150234.GA85280@libertas.local.camdensoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427150234.GA85280@libertas.local.camdensoftware.com> User-Agent: Mutt/1.4.2.3i Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:09:02 -0000 On Wed, Apr 27, 2011 at 08:02:34AM -0700, Chip Camden wrote: > Quoth Eric on Wednesday, 27 April 2011: ... > > >> My search for "popularity" metrics is intended to point me, as a > > >> maintainer, to ports I might want to adopt now, rather than wait for > > >> someone to complain about them. Everything *I* use is already > > >> maintained, so I've moved on to looking for things other people might > > >> need. But I don't want to waste my time on something that nobody uses. > > >> :) I have suggested in the past that part of the ports infrastructure could toggle a count somewhere each time a port is made. This should be opt in of course. It would make it very easy to see which port might need a maintainer. - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db Why leave money to our children if we don't leave them the Earth? From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 15:47:35 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B251106566C for ; Wed, 27 Apr 2011 15:47:35 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id E45F68FC08 for ; Wed, 27 Apr 2011 15:47:34 +0000 (UTC) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p3RFl7aa026956 for ; Wed, 27 Apr 2011 17:47:21 +0200 (CEST) X-Ids: 165 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id D541820588 for ; Wed, 27 Apr 2011 17:47:06 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id EF67A4120; Wed, 27 Apr 2011 17:47:08 +0200 (CEST) Date: Wed, 27 Apr 2011 17:47:08 +0200 From: Michel Talon To: freebsd-ports@freebsd.org Message-ID: <20110427154708.GA98819@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Miltered: at jchkmail.jussieu.fr with ID 4DB83A7C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4DB83A7C.000/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:47:35 -0000 Eitan Adler wrote: > There is a lot of work that has to be done in the background even if > no new ports are added. Things like the gmake upgrade and new ports > features take a lot of time. Furthermore adding a port seems to be a > "trivial" task, however the committers have to (a) fix it up if it is > formatted badly (b) test it in a tinderbox and only then (c) commit > it. This takes more time than just "cvs commit". A lot of work has > been done in recent years to make this process faster and I'm sure > more could be done - but a lot of people don't realize how much work > goes on behind the scenes I think it is important to clean up ports because otherwise there is a big burden on the FreeBSD organization, and also on each individual user, when they upgrade their machine. I think on the other hand that some ports are especially important, and don't always receive the care they need, for reasons that i don't know. I have taken some time to look at some ports in the "lang" category that are unmaintained or are severely old. I have noted that eiffel 13a is deprecated and has an expiration date. Indeed i have found old copies of this software, and it seems that the people doing it have disappeared someway. However at least one is now listed as contributor to gobo-eiffel http://sourceforge.net/projects/gobo-eiffel/ which is not a freebsd port. There is the "official" eiffelstudio port, which has a valid download link but no maintainer, and smarteiffel which is maintained. I am more interested by the cmucl lisp compiler. In the ports we can find cmucl 19f which is maintained by Martin Cracauer, but is already quite old, and there is no maintainer for cmucl-extras. In fact the cmucl project does the work of providing precompiled stuff for various architectures (the lisp compiler is written in lisp so can only be compiled by a recent enough precompiled compiler, anyways) and in particular one finds freebsd binaries here: http://common-lisp.net/project/cmucl/downloads/snapshots/2011/04/ These binaries are compiled on freebsd_8.1, and there are two versions the unicode version and the non-unicode version, plus the cmucl-extra (localized messages, an adapted editor, called hemlock plus some goodies). So my point is, how is it that cmucl freebsd version finds care and love in the cmucl community, but that this does not extend to an adequate place in the freebsd ports? The other big lisp from the same ancestry, sbcl is better maintained, since the last version is 1.0.47, while freebsd is at 1.0.43, that is 6 months old. These lisps are *very* important for their use in the CAS software maxima, which is actively developed and used by a lot of people (in ancient times the traditional compiler for maxima was gcl but it seems it doesn't work well nowadays, and clisp is far too slow). But they are also important for many other uses, and at this point i see an important omission in the ports system. The "standard" way nowadys to install lisp packages is to use quicklisp http://www.quicklisp.org/beta/ and after that hundreds of applications can be installed automatically in the same way as cpan does for perl modules. Instead there are a select few lisp applications in the ports, which have a clisp and a sbcl slave port. This is strange. -- Michel TALON From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 15:48:57 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C72A71065670 for ; Wed, 27 Apr 2011 15:48:57 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 533AE8FC16 for ; Wed, 27 Apr 2011 15:48:56 +0000 (UTC) Received: by bwz12 with SMTP id 12so2137537bwz.13 for ; Wed, 27 Apr 2011 08:48:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=MGIV2ugYu/TkMU4fLZCB3yW4rKjeNe3U0G4DVj6ztbc=; b=T2t4JiNqwdP69roVXA0SfTKoMG91aMeuIwpEowheG+PjT9BAJTmiiicEkxxq6P52GE k3rIk3kEnIKtrxn28pUiLRtD0JmpXF3KogcL3Q2CQA8HwiWlcMq2TKDLk0sZTNGofvHO Az/AbP4skjYXkk+anfqBpjNenVOs8vqWr5gqc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=fxmDE2MpQzCL13C/8lJPQbl6+hKJIo54WiKzUxlUA+QncBWMd7Q1faslqI24ah/dxR Kf3sCNAeQRPD9SF0v9wUB0DiX6V8z0CAhckxxNdO28NrTdImQIhqQmk61cmqhOVSp5Wm 5cvEJCl9fvoyf3kF2TDgNAIuHwpsOSsmW2jsA= Received: by 10.204.181.7 with SMTP id bw7mr2124944bkb.16.1303919336107; Wed, 27 Apr 2011 08:48:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.42.21 with HTTP; Wed, 27 Apr 2011 08:48:26 -0700 (PDT) In-Reply-To: <20110427125424.GJ34314@home.opsec.eu> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <20110427125424.GJ34314@home.opsec.eu> From: Chris Rees Date: Wed, 27 Apr 2011 16:48:26 +0100 Message-ID: To: Kurt Jaeger Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:48:57 -0000 On 27 April 2011 13:54, Kurt Jaeger wrote: > Eitan Adler wrote: >> Things like the gmake upgrade and new ports >> features take a lot of time. =A0Furthermore adding a port seems to be a >> "trivial" task, however the committers have to (a) fix it up if it is >> formatted badly (b) test it in a tinderbox and only then (c) commit >> it. > > I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to > test. I do not use a tinderbox, as I assume considerable complexity > to set one up. Nah, have a look at [1]. Easy as pie. > Does using a tinderbox make a large difference ? Yes! It finds hiccups in pkg-plist (very difficult to notice manually), it tests in different versions -- just add them to the queue. If you'd really like to try it out, I'll give you an account on my machine. Let me know. Chris [1] http://tinderbox.marcuscom.com/README/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 16:49:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 293041065672 for ; Wed, 27 Apr 2011 16:49:31 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 5BAFD8FC0A for ; Wed, 27 Apr 2011 16:49:29 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.4/8.14.4) with ESMTP id p3R9Jxn3050973; Wed, 27 Apr 2011 04:19:59 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.4/8.14.4/Submit) id p3R9Jx7K050972; Wed, 27 Apr 2011 04:19:59 -0500 (CDT) (envelope-from brooks) Date: Wed, 27 Apr 2011 04:19:59 -0500 From: Brooks Davis To: spotter Message-ID: <20110427091959.GH43345@lor.one-eyed-alien.net> References: <19CCC0EE-AAF8-401B-875F-F2A43E780642@huibsmeets.com> <1303913707221-4343776.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbfcI4OLZ4XW0yH2" Content-Disposition: inline In-Reply-To: <1303913707221-4343776.post@n5.nabble.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 27 Apr 2011 04:19:59 -0500 (CDT) Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: squeezeboxserver-7.5.3, build okay but fails to start. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 16:49:31 -0000 --VbfcI4OLZ4XW0yH2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 27, 2011 at 07:15:07AM -0700, spotter wrote: > I am having the exact same problem with a brand new FreeBSD 8.1-RELEASE > install and a fresh squeezeboxserver (v7.5.3) port build. > (Slimserver was working fine under FreeBSD 6.2, until I tried to get > miniDLNA working, as well, for a BluRay player access to same music libra= ry. > sigh) > Any solutions worked out for squeezeboxserver v7.5.3 under FreeBSD > 8.1-RELEASE? Assuming you aren't using mysql for anything else, you might try manually installing an older version and then reinstalling the port. My squeezeboxserver is running with 5.0. If that works we should be able to restrict the allowed versions of mysql to ones that work. -- Brooks >=20 >=20 > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBS= D-Port-squeezeboxserver-7-5-3-build-okay-but-fails-to-start-tp3861984p43437= 76.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >=20 --VbfcI4OLZ4XW0yH2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFNt9++XY6L6fI4GtQRAoEaAJ9BP/q6IfXIlpjMHp80OKUVOHC4EQCfRuER XeO2vD+UjEznkt05TgbQEv4= =oRzJ -----END PGP SIGNATURE----- --VbfcI4OLZ4XW0yH2-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 16:29:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C156106564A for ; Wed, 27 Apr 2011 16:29:02 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp03.lnh.mail.rcn.net (smtp03.lnh.mail.rcn.net [207.172.157.103]) by mx1.freebsd.org (Postfix) with ESMTP id 2AA488FC1C for ; Wed, 27 Apr 2011 16:29:01 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 12:00:12 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id AVO53417; Wed, 27 Apr 2011 12:00:11 -0400 Received-SPF: None identity=pra; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="mi+thun@aldan.algebra.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="mi+thun@aldan.algebra.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="postmaster@utka.zajac"; x-conformance=sidf_compatible X-Auth-ID: anat Received: from unknown (HELO utka.zajac) ([209.6.61.133]) by smtp01.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 12:00:12 -0400 Message-ID: <4DB83D6E.9000800@aldan.algebra.com> Date: Wed, 27 Apr 2011 11:59:42 -0400 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Robert Huff References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> In-Reply-To: <19895.13977.553973.609431@jerusalem.litteratus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Apr 2011 17:32:28 +0000 Cc: Chip Camden , freebsd-ports@freebsd.org Subject: Re: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 16:29:02 -0000 On -10.01.-28163 14:59, Robert Huff wrote: > It is also possible it is only important to a fairly small > number ... but to those it is absolutely crucial. Or the port might become useful/essential/critical to somebody in the future... What is not broken -- just old, like databases/db2 or www/apache13*, for example -- should be left alone (until it becomes both broken and unmaintained). And even then, the removal should not be mass-scale/automatic... Maybe, for cleanliness and neatness, we should have a separate directory (and category): "obsolete" -- where ports can go to die peacefully. But it should not be cvs' "Attic"... -mi From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 18:16:55 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EC28106564A for ; Wed, 27 Apr 2011 18:16:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 00D928FC0A for ; Wed, 27 Apr 2011 18:16:54 +0000 (UTC) Received: by vxc34 with SMTP id 34so2019901vxc.13 for ; Wed, 27 Apr 2011 11:16:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=fAxdy29OKnD6nQ+jPJW4lZvbIFViOtHpp2KRq8Ei+Ww=; b=Q6P3UE3Uo3sqi38lgmjond6rFPETUw5951qQm1qmTbyw8IAY3go91yyzrsRoWL1HPf 6vsm7ATU5zpDQXjmIRe/4kv4gWW7+LWYxuYQUtXNwTjte70e6Qa4xBlFKbnNNj7hDoQJ v+TbHcy9tkajI3bILdcZtOUXxqwU3b+n0mS5o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=DXCpHv67z9ocvmbDLrnn3pmfDrD+kKGgXiTV7MGrpJ98md8oGHaPklfnSAGI5rDkst Lt1K60ReqibdAgdx39QraFN1racj0YBUY5+s7ZprAiFOduFgm4dzn4UWUUHiLLvEIPk1 w1cmLgqmunCZg4B5UDPq37iHXhn4lZGwxn6lg= Received: by 10.52.179.100 with SMTP id df4mr3738194vdc.220.1303928214076; Wed, 27 Apr 2011 11:16:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Wed, 27 Apr 2011 11:16:24 -0700 (PDT) In-Reply-To: <4DB83D6E.9000800@aldan.algebra.com> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> From: Eitan Adler Date: Wed, 27 Apr 2011 14:16:24 -0400 Message-ID: To: "Mikhail T." Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:16:55 -0000 > What is not broken -- just old, like =C2=A0databases/db2 or www/apache13*= , for > example -- should be left alone (until it becomes both broken and > unmaintained). And even then, the removal should not be > mass-scale/automatic... This recent sweep was neither mass scale nor automatic. 536/22816 ports is only 3.234% of all the ports. Furthermore bapt@, myself, and a few other people went through each of the categories ensuring the projects were actually dead (not necessarily that the distfile couldn't be found). Then bapt@ marked the ports *deprecated* which does not mean deleted. It was a warning that people who were interested should step up and take up the work. If after N amount of time no one does so they will be individually deleted. > Maybe, for cleanliness and neatness, we should have a separate directory > (and category): "obsolete" -- where ports can go to die peacefully. But i= t > should not be cvs' "Attic"... Who will be the ones to deal with that category, ensuring new infrastructure works, etc? The port maintainer? oh wait! cvs's Attic can be easily restored if people take up the slack. I see no reason to change this policy. --=20 Eitan Adler From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 18:38:53 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id D0F08106566C for ; Wed, 27 Apr 2011 18:38:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8828C157584; Wed, 27 Apr 2011 18:38:53 +0000 (UTC) Message-ID: <4DB862BD.5080500@FreeBSD.org> Date: Wed, 27 Apr 2011 11:38:53 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Mikhail T." References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> In-Reply-To: <4DB83D6E.9000800@aldan.algebra.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:38:53 -0000 On 04/27/2011 08:59, Mikhail T. wrote: > What is not broken -- just old, like ... or www/apache13* apache13 is way past EOL, and the apache team is working hard to move the default to apache22, at which point I personally hope that apache13 dies a quick and painful death :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 18:46:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C110F1065675 for ; Wed, 27 Apr 2011 18:46:30 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id 86E518FC25 for ; Wed, 27 Apr 2011 18:46:30 +0000 (UTC) Received: from c-24-22-230-24.hsd1.wa.comcast.net ([24.22.230.24] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QF9ko-00013Y-VF for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 14:46:28 -0400 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Wed, 27 Apr 2011 11:46:25 -0700 Date: Wed, 27 Apr 2011 11:46:25 -0700 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20110427184625.GC2729@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:46:30 -0000 --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Eitan Adler on Wednesday, 27 April 2011: > > What is not broken -- just old, like =A0databases/db2 or www/apache13*,= for > > example -- should be left alone (until it becomes both broken and > > unmaintained). And even then, the removal should not be > > mass-scale/automatic... >=20 > This recent sweep was neither mass scale nor automatic. > 536/22816 ports is only 3.234% of all the ports. Furthermore bapt@, > myself, and a few other people went through each of the categories > ensuring the projects were actually dead (not necessarily that the > distfile couldn't be found). Then bapt@ marked the ports *deprecated* > which does not mean deleted. It was a warning that people who were > interested should step up and take up the work. If after N amount of > time no one does so they will be individually deleted. >=20 > > Maybe, for cleanliness and neatness, we should have a separate directory > > (and category): "obsolete" -- where ports can go to die peacefully. But= it > > should not be cvs' "Attic"... >=20 > Who will be the ones to deal with that category, ensuring new > infrastructure works, etc? The port maintainer? oh wait! > cvs's Attic can be easily restored if people take up the slack. I see > no reason to change this policy. >=20 > --=20 > Eitan Adler Modifying the script that was posted earlier, we can list out all installed ports that are currently deprecated, and why: #!/bin/sh = =20 = =20 prefix=3D/usr/ports/ = =20 makefile=3D/Makefile = =20 = =20 for file in `pkg_info -oxa | grep "/"` = =20 do = =20 yes=3D`grep DEPRECATED=3D ${prefix}${file}${makefile}` if [ -n "$yes" ] = =20 then echo $file $yes fi = =20 done=20 When I ran this on my system, I found only lang/libutils. It must have been needed by something I've since uninstalled, because nothing depends on it now -- so I deleted it. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJNuGSBAAoJEIpckszW26+R6vsIALzI2MZkLeV8pUhlVf+LPZ3g yUDOQhRQ/0n7/I7JuBBoz9eOWOp5H5fEra8W1+t6hmwa9XebL1GRs2BGoWufB/0m /tewHWxBAqmCocdZsEAMq+XV9q5gHCoVBTA2J7NOq3DjUKrX6Oih2jmVqlXMPv29 a6HUGfytaPDJFGtgnrwwkM+XxCujyqj1GbO6GVCSjVjEbtXkAJ2GbkRt+l9EJIgh RHHzZbTvoV0hnkAgtBRCL8OFzwCX6p144ME7X8k4tbI5mUuYMJTZErR9XmdL7wpj P3K1AFjpYUfizcl4ZB6voZ2RQ0AeYJvXhOze9bj/qi9yfofySRt5/BzOAmtUL8c= =5HSn -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 18:53:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72CB6106566B for ; Wed, 27 Apr 2011 18:53:51 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id 45A078FC13 for ; Wed, 27 Apr 2011 18:53:51 +0000 (UTC) Received: from [192.168.0.11] (atoulouse-256-1-41-46.w90-38.abo.wanadoo.fr [90.38.232.46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id DAB24435D7 for ; Wed, 27 Apr 2011 13:53:49 -0500 (CDT) Message-ID: <4DB8664D.70001@marino.st> Date: Wed, 27 Apr 2011 20:54:05 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> In-Reply-To: <20110427101257.414aaf8b@seibercom.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:53:51 -0000 On 4/27/2011 4:12 PM, Jerry wrote: > On Wed, 27 Apr 2011 15:48:36 +0200 > Erik Trulsson articulated: > >> On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: >> Very simple. A particular committer during one particular period of >> time maybe only 45 minutes of free time to spend on handling PRs. >> If the committer estimates that one large submitted PR would take at >> least two hours to review, test, and commit, while another, smaller, >> PR would only take 30 minutes to handle. >> >> Then the committer in question would have two choices: Don't handle >> either submission, or handling the smaller submission, while skipping >> the large one and hoping that some other committer with more free time >> will pick up that one. >> I see no reason to prefer the first of these choices. > If the committer cannot finish the project in their allotted time > frame they simply stop and pick up from that point in their next > session. I have literally hundreds of projects that I cannot complete > in one day; however, I don't simply shrug them off. If I did nothing > would ever get accomplished, or at best only the easiest assignments. > > One of the basic fallacies in your analysis is that someone else will > pick up the slack. Unfortunately, our society has become over run by > those who are always ready to blame others or expect others to do our > job for us. Quite honestly, I find that pathetic. > I seemed to have kicked off quite a dialog! First of all, I want to thank Frederic Culot for committing my patch today. Basically, I'm in complete agreement with Jerry with regards to FIFO. The proposal was made that given a short amount a time, a committer should choose the simpler project and bypass the first one simply based on time/complexity. I couldn't disagree more. As soon as it's possible to skip valid ports, then that's what is going to happen. If people can physically cherry-pick, then they'll exercise their ability to do that and immediately you sink into the current situation. Unfortunately, a FIFO setup requires that all the requests go through a single entity who then assigns them. I don't really buy the joe-the-font-guy with mary-the-network-gal mismatch. Nobody said the PRs have to be assigned as round-robin. And then that changes the dynamic since the PR is assigned rather than chosen. This entity can't just assign a PR without knowing the committer's timeline, availability, etc, so there are clearly implementation details to work out. Maybe a compromise would be to keep the current system in place with the addition of having somebody do these assignments if the new PRs are unclaimed for more than 3-7 days. Yes, it means a new job for someone, but if one believes that FIFO is the fair and respectful approach, the extra effort should be worth it. -- John From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 18:55:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B20C7106566C for ; Wed, 27 Apr 2011 18:55:36 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 420968FC0A for ; Wed, 27 Apr 2011 18:55:35 +0000 (UTC) Received: by bwz12 with SMTP id 12so2359861bwz.13 for ; Wed, 27 Apr 2011 11:55:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=EIvamhPY8aZxpcUVvVNKl4zL8ggpQJicuARyLf+tBmA=; b=egsuTIVGRNpdt+cb1lZYGxfwo5T/Dqh+uPVxhRtnA4v91sklGX/2/ig5dJVWVNCp2c +s7UnjMhZWvPrG+MM9B7sz0OSSlJx7dFSYQlFag5Os830svzsxRwZwmwq/zU6yhr9YYc K8XlBL7xnfIFgobrw2xX+5edP+WPaXwr21yr0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=w3OAZN7MgV8AvO7qSFMuZnXW1+IuvaKlel2FhH0/UGL9cbePs5irOEdFqbGMD9wdhE HF0RRf7epUNW1QDlrBY1HSa5owFkwkONCW6bgb5vHWAspMdmcECF2xyLuSHV3L+JywcI fpHG0lzc/VObl7a1nsZ4Zosn2vxNWnokqLcBs= Received: by 10.204.74.11 with SMTP id s11mr2356663bkj.43.1303930535128; Wed, 27 Apr 2011 11:55:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.42.21 with HTTP; Wed, 27 Apr 2011 11:55:05 -0700 (PDT) In-Reply-To: <20110427085445.391a015e@seibercom.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <20110427085445.391a015e@seibercom.net> From: Chris Rees Date: Wed, 27 Apr 2011 19:55:05 +0100 Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:55:36 -0000 On 27 April 2011 13:54, Jerry wrote: > On Wed, 27 Apr 2011 13:00:17 +0100 > Chris Rees articulated: > >> How do you define respect? I find the committers extremely respectful. > > Allowing a submitter to languish for an indeterminate period without > any notification of what is transpiring with his/her submission is not > respectful, it is benign neglect. > > As I stated, each submitted item should be handled in a basic FIFO > order unless there is a specific reason for not doing so. If such > reason exists then the original submitter should be informed of this > irregularity. Waiting for months while items submitted after the > submitter's item are approved without notifying the submitter of why is > certainly not friendly or respectful, unless of course you work for > the motor vehicle or parking department in which case it is just > business as usual. > > I have been at both extremes of the spectrum on this, having had items > committed within days and conversely waiting for an extended period of > time and finally asking specifically why an item was not committed > before anything happened. The present system is broken, or at the very > least poorly implemented, unless the goal is to keep a submitter in the > dark. I reiterate, there is no logical reason to jump over one user's > submission and proceed with another user's submission without formally > notifying the submitter of the older item why his/her item is being > bypassed. > I believe the standard protocol is to jump on IRC and ask for advice -- it could be something very little -- or it's been lost in the swarm (less likely). I honestly don't think that there's much wrong with the system as it is; once you get better at making submissions, taking time to read the Porter's Handbook your patches become committed more and more quickly. Chris From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 19:00:35 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6FD91065675 for ; Wed, 27 Apr 2011 19:00:35 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id BDA0A8FC19 for ; Wed, 27 Apr 2011 19:00:35 +0000 (UTC) Received: from cpe-66-68-128-204.austin.res.rr.com ([66.68.128.204] helo=inferno.lab.lovett.com) by panix.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QF9yU-000BEh-RH for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 19:00:35 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Ade Lovett In-Reply-To: <20110427184625.GC2729@libertas.local.camdensoftware.com> Date: Wed, 27 Apr 2011 14:00:23 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <66B715DB-4C55-4508-AD14-C7A0CF51C111@FreeBSD.org> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <20110427184625.GC2729@libertas.local.camdensoftware.com> To: FreeBSD Ports X-Mailer: Apple Mail (2.1084) Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:00:36 -0000 On Apr 27, 2011, at 13:46 , Chip Camden wrote: >=20 > Modifying the script that was posted earlier, we can list out all > installed ports that are currently deprecated, and why: Won't work -- need to handle slave ports etc, where the DEPRECATED may = be in the MASTER_PORT. Try this: #!/bin/sh # PORTSDIR=3D${1-"/usr/ports"} for port in $(pkg_info -oa | grep /) do dep=3D$(make -C ${PORTSDIR}/${port} -V DEPRECATED) [ -n "${dep}" ] && echo "${port}: ${dep}" done -aDe From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 19:22:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id E1EF51065675 for ; Wed, 27 Apr 2011 19:22:54 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A975215830D; Wed, 27 Apr 2011 19:22:53 +0000 (UTC) Message-ID: <4DB86D0D.7020006@FreeBSD.org> Date: Wed, 27 Apr 2011 12:22:53 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <20110427094546.798d8367@seibercom.net> In-Reply-To: <20110427094546.798d8367@seibercom.net> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jerry Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:22:55 -0000 On 04/27/2011 06:45, Jerry wrote: > I think that 'UPDATING' the PR to let the submitter know > that he/she has not been forgotten and to keep them aware of any > problems with the PR is certainly a welcome suggestion. Unfortunately, > that is rarely presently done. If the PR is still open, it has not been forgotten. Committers have limited time available, would you rather have them spend time to make meaningless changes to open PRs, or would you rather have them spend that time working on closing some? > Certainly, we should all be able to come > to some consensus as to what constitutes a reasonable time frame. I hear you (and others) saying that they current system does not seem to be "fair." I can certainly understand why you would feel that way. Unfortunately, there literally are not any other answers we can provide. This topic has come up periodically for all the years I've been involved in FreeBSD (contrary to what someone else said about it having been easier in "the old days" when the ports tree was smaller) and no one has come up with an answer for it yet. We try to identify and train new committers on a fairly aggressive pace, but that is also a volunteer effort. To summarize, we hear your frustration, and we ask you to be patient. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 19:28:13 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77BA8106566B; Wed, 27 Apr 2011 19:28:13 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id B4AC08FC0A; Wed, 27 Apr 2011 19:28:12 +0000 (UTC) Received: by eyg7 with SMTP id 7so816230eyg.13 for ; Wed, 27 Apr 2011 12:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ROo1w9DJHmlZERBj8E7rbGWribYsrolnCcGY9hspjDA=; b=G35LpdQTwlZ2VgXf5L1uzheO3KDL5BX1tTFtiC25YTV2xv3B3LpChq5U7UH1svuPU5 v7o0NznEKU4ul0bYF1KiZuZJy/eXVnK+aYCcWnIxPI/I8pKPbpB8ZYOd2WG8yh0dumOK pcLPzAFKkBeAgfY/dQ4Agydyz+j1RNZifRono= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=k9rhXzlaU+mfI0cUH7fAystiYx5u2c/4PmBXniFs/9+K4crjzGZL6Hiyf6GIHTx3so 5fv4vyfTgGxLYTbZ/XLzxGW83tEcXXadWf10SIEiajTKw9HyKA+xw4EJ7oJaPL4uGzX+ JdvQl5QMYMR2v2MSwcUqp9AJNZjt4DNOKNJCQ= MIME-Version: 1.0 Received: by 10.213.7.216 with SMTP id e24mr2625871ebe.35.1303932491465; Wed, 27 Apr 2011 12:28:11 -0700 (PDT) Received: by 10.213.35.70 with HTTP; Wed, 27 Apr 2011 12:28:11 -0700 (PDT) In-Reply-To: <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Date: Wed, 27 Apr 2011 15:28:11 -0400 Message-ID: From: Ryan Stone To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:28:13 -0000 (Sorry for the noise earlier about the PBIs not working under PC-BSD; I'm not sure how I missed that had been already reported). I tried the new amd64 PBI and I am able to successfully start VMs now. I had one VM(running some relatively recent version of amd64 HEAD) boot up fine, but a second one (also running amd64 HEAD, but maybe a different svn revision) gets a Guru Meditation during startup. I'm not sure what is causing the crash. In their original configurations the working VM booted off of an emulated IDE disk while the broken VM booted of an emulated SATA disk, however I just tried changing the SATA disk to instead be an IDE disk and it doesn't seems to have resolved the problem. I'm not getting a corefile for the crash(or I'm unable to find it). I do have kern.sugid_coredump=1 and I'm running the PBI. Is this expected for a Guru Meditation, or should it be putting a core somewhere? I've put the VBox.log for the most recent crash here: http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log This seems to be easy to reproduce so let me know if there's any more information that I can gather. Also, the working VM was emulating uniprocessor machine. I tried adding a second CPU and that VM started crashing, too. I tried changing the broken VM to have only one core but it still crashes. I'm not sure if it's related to the first crash or not. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 19:18:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D377F1065670 for ; Wed, 27 Apr 2011 19:18:39 +0000 (UTC) (envelope-from mfl-commissioner@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id A65108FC14 for ; Wed, 27 Apr 2011 19:18:39 +0000 (UTC) Received: from [192.168.0.11] (atoulouse-256-1-41-46.w90-38.abo.wanadoo.fr [90.38.232.46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id EE38D435D7 for ; Wed, 27 Apr 2011 14:00:28 -0500 (CDT) Message-ID: <4DB867DD.50702@marino.st> Date: Wed, 27 Apr 2011 21:00:45 +0200 From: MFL Commissioner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <20110427085445.391a015e@seibercom.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Apr 2011 19:54:02 +0000 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:18:39 -0000 On 4/27/2011 8:55 PM, Chris Rees wrote: > I honestly don't think that there's much wrong with the system as it > is; once you get better at making submissions, taking time to read the > Porter's Handbook your patches become committed more and more quickly. > > > Chris Come on. There's no relationship between quality of the patch and when it's picked up by a commiter. I ran my patch through tinderbox until was right, and it's not like that made a difference. There is no way to tell the quality without taking a real look. There's plenty wrong with the current system. The real question is what's the most practical way to address it. John From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 20:04:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6FA106564A for ; Wed, 27 Apr 2011 20:04:01 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp03.lnh.mail.rcn.net (smtp03.lnh.mail.rcn.net [207.172.157.103]) by mx1.freebsd.org (Postfix) with ESMTP id 1D11E8FC12 for ; Wed, 27 Apr 2011 20:04:00 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 16:04:00 -0400 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr17.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id AVR08426; Wed, 27 Apr 2011 16:03:59 -0400 X-Auth-ID: anat Received: from 209-6-61-133.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com (HELO utka.zajac) ([209.6.61.133]) by smtp04.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 16:03:58 -0400 Message-ID: <4DB876AE.9050906@aldan.algebra.com> Date: Wed, 27 Apr 2011 16:03:58 -0400 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Eitan Adler References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:04:01 -0000 On 27.04.2011 14:16, Eitan Adler wrote: > Then bapt@ marked the ports*deprecated* which does not mean deleted. It was a warning that people who were interested should step up and take up the work. If after N amount of time no one does so they will be individually deleted. The ports I listed -- db2 and apache13* family -- are/were not broken. What "work" are you talking about? Yet, mandree deleted db2 on April 12th and dougb is anxious to delete apache13 as well instead of simply disowning it... >> > Maybe, for cleanliness and neatness, we should have a separate directory >> > (and category): "obsolete" -- where ports can go to die peacefully. But it >> > should not be cvs' "Attic"... > Who will be the ones to deal with that category, ensuring new > infrastructure works, etc? The port maintainer? oh wait! The same entity(ies), that currently busy themselves marking things "deprecated". But it was just a proposal -- for those, who don't like to see "obsolete" software mixed with the latest and greatest. I'm perfectly satisfied with not touching "obsolete" things at all. Certainly not until they break -- and stay broken for "too long". > cvs's Attic can be easily restored if people take up the slack. I see > no reason to change this policy No, not easily. It requires the CVS tree, which is not automatically installed. /usr/ports/obsoleted, on the other hand, would be rolled out together with the rest of the ports-tree. And, under my proposal, the packages for the "obsolete" stuff will continue building. The "if people take up the slack" seems to imply need to continuously work on the software. But the db2 needed no serious changes since 2004 and the last meaningful change was in 2008... The only reason to kill it was "too old"... Now all current users of db2 have to move onto later dbX, which means not only patching up the API-calls in their source-code (if the source code is even available!), but recreating their databases too -- because Berkeley DB files are not backwards-compatible. And for what reason?.. Same goes for apache13 -- last change was an upgrade to 1.3.42 (February 2010) -- it does not seem to require much work. There may well be good reasons to hate it, but somebody with a custom module, for example, may be perfectly satisfied with it... I happen to know one such site, for example. There may be more. If apache@ does not want it, they can drop maintainership. But deletion is not called for. Upgrading the OS should not /require/ upgrading (and replacing!) the applications. Yours, -mi From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 20:18:16 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 026BE106564A; Wed, 27 Apr 2011 20:18:16 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 93A7F8FC1A; Wed, 27 Apr 2011 20:18:15 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 290355; Wed, 27 Apr 2011 22:18:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Wed, 27 Apr 2011 22:18:15 +0200 From: Bernhard Froehlich To: Ryan Stone In-Reply-To: References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Message-ID: <03556d6e44f27c7c6ba74f59f1f6971a@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.5.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0206.4DB87A06.00AF,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:18:16 -0000 On Wed, 27 Apr 2011 15:28:11 -0400, Ryan Stone wrote: > (Sorry for the noise earlier about the PBIs not working under PC-BSD; > I'm not sure how I missed that had been already reported). > > I tried the new amd64 PBI and I am able to successfully start VMs now. > I had one VM(running some relatively recent version of amd64 HEAD) > boot up fine, but a second one (also running amd64 HEAD, but maybe a > different svn revision) gets a Guru Meditation during startup. I'm > not sure what is causing the crash. In their original configurations > the working VM booted off of an emulated IDE disk while the broken VM > booted of an emulated SATA disk, however I just tried changing the > SATA disk to instead be an IDE disk and it doesn't seems to have > resolved the problem. > > I'm not getting a corefile for the crash(or I'm unable to find it). I > do have kern.sugid_coredump=1 and I'm running the PBI. Is this > expected for a Guru Meditation, or should it be putting a core > somewhere? I've put the VBox.log for the most recent crash here: No, that looks fine. > http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log > > This seems to be easy to reproduce so let me know if there's any more > information that I can gather. I've added it to the Todo list for 4.0.6 and will report it to the vbox developers tomorrow. Sorry, don't have a clue what is going wrong there - but i'm sure they know. http://wiki.freebsd.org/VirtualBox/ToDo > Also, the working VM was emulating uniprocessor machine. I tried > adding a second CPU and that VM started crashing, too. I tried > changing the broken VM to have only one core but it still crashes. > I'm not sure if it's related to the first crash or not. Look at the relevant parts of VBox.log and see if they look about the same. 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current pointer ffffffffffffffff vs 0000000084362000 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current VMCS version e 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Entered Cpu 3 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current Cpu 2 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current pointer 0000000000000000 vs 0000000084365000 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current VMCS version 0 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Entered Cpu 0 00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current Cpu 0 00:00:08.374 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 00:00:08.374 !! 00:00:08.374 !! Guru Meditation -4001 (VERR_VMX_INVALID_VMCS_PTR) 00:00:08.374 !! 00:00:08.374 !! 00:00:08.374 !! {mappings, } 00:00:08.374 !! -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 20:46:42 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27A92106564A for ; Wed, 27 Apr 2011 20:46:42 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.49.45]) by mx1.freebsd.org (Postfix) with ESMTP id F19938FC08 for ; Wed, 27 Apr 2011 20:46:41 +0000 (UTC) Received: by syn.atarininja.org (Postfix, from userid 1001) id 02EE25C3A; Wed, 27 Apr 2011 16:47:24 -0400 (EDT) Date: Wed, 27 Apr 2011 16:47:23 -0400 From: Wesley Shields To: "Mikhail T." Message-ID: <20110427204723.GA74591@atarininja.org> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB876AE.9050906@aldan.algebra.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Eitan Adler , Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:46:42 -0000 On Wed, Apr 27, 2011 at 04:03:58PM -0400, Mikhail T. wrote: > On 27.04.2011 14:16, Eitan Adler wrote: > > Then bapt@ marked the ports*deprecated* which does not mean deleted. It was a warning that people who were interested should step up and take up the work. If after N amount of time no one does so they will be individually deleted. > The ports I listed -- db2 and apache13* family -- are/were not broken. What > "work" are you talking about? > > Yet, mandree deleted db2 on April 12th and dougb is anxious to delete > apache13 as well instead of simply disowning it... apache13 is EOL upstream. We should not have ports for EOL software. I don't care if it works perfectly fine and someone wants to hand-roll patches back to it. If upstream says it's dead, who are we to keep it alive? -- WXS From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 20:55:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54B2B1065673 for ; Wed, 27 Apr 2011 20:55:01 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id F3DB18FC1A for ; Wed, 27 Apr 2011 20:55:00 +0000 (UTC) Received: by vws18 with SMTP id 18so2123146vws.13 for ; Wed, 27 Apr 2011 13:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=yBuoSvmzH7ElcIsBBZ5a27f4jg8T+ELIjoVS/8Ajmtk=; b=hKne5u8ESDhV4PuQ+LINM5QKlqv6Tb5Ad9Ln+heFWdStmEd9bXnjwai/Elg3kUYJk4 4xVvwWG9yZJANYMOiWpAl40Uz43T1GFNctiUBDROEgaNN6BQ/hq5ZJy24iKx5zAspSt7 ywilk6onDIIi3KwYxvXXRpELip2Zhx7H9gq5E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=S/xXYZWxOa6gYwiHLTWdgZXcmSOpMbFd/fd0vyu8VLdqS35c5NSzRaAO4ssNeQXfg9 B4lVFSMVPxfVNcAM/Hc7o3nvwiCJRS0NS589Ht1cFG9/oMBgWyhrlPM680125zWyt7fI EAeJNCI/licCN1Ir3HMy/rFFs9arc6u0RK0Ow= Received: by 10.52.75.165 with SMTP id d5mr1774747vdw.300.1303937700124; Wed, 27 Apr 2011 13:55:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Wed, 27 Apr 2011 13:54:30 -0700 (PDT) In-Reply-To: <4DB876AE.9050906@aldan.algebra.com> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> From: Eitan Adler Date: Wed, 27 Apr 2011 16:54:30 -0400 Message-ID: To: "Mikhail T." Content-Type: text/plain; charset=UTF-8 Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:55:01 -0000 >dougb is anxious to delete apache13 as well instead of simply disowning it... The upstream maintainer already called it "end of life". FreeBSD does not and will not ever take over the development of dead upstream ports (and in this case there is a upstream version) >The same entity(ies), that currently busy themselves marking things >"deprecated". The ports marked "broken with no one to fix them" (shortened to 'deprecated') take a significant amount of time and energy to fix. Think of the warning as a "call to fix" for those parts. If you feel > No, not easily. It requires the CVS tree, which is not automatically > installed. /usr/ports/obsoleted, on the other hand, would be rolled out > together with the rest of the ports-tree. And for those who want to use old, and likely broken ports, they can take that effort to install the tree. > And, under my proposal, the > packages for the "obsolete" stuff will continue building. Which is a *major* drain of resources. One of the reasons for ceasing the building of packages for broken/completely obsolete is to avoid draining the computer time building said packages. Take a guess how long it takes to build from start to completion a complete set of packages. I'll bet you get it wrong. Furthermore in order to continue building packages the ports have to *work* which most of them presently do not. What you fail to understand is that we are NOT marking ports as 'obsolete' or 'bad' or 'there exists a better program' but as broken and unmaintained. What we ARE saying is that "this port does not presently work and no one took up the mantle to (a) fix it (b) maintain it (c) continue to the maintain it in the future. There are hundreds if not thousands of obsolete ports in the tree. This is because someone decided to MAINTAIN the ports. We can not support BROKEN ports unless someone does the work. [snip] > Same goes for apache13 -- last change was an upgrade to 1.3.42 (February > 2010) -- it does not seem to require much work. Apache 1.3 is DEAD and been supplanted upstream. If you wish to fork apache 1.3 and make a new project we will GLADY host a port for it (if someone decided to maintain it) I strongly doubt that you have any idea of the amount of work it takes to support 23,000 ports. Furthermore it seems that your proposals fail to consider the amount of infrastructure work that must be delayed or even prevented due to sheer number of broken and unmaintained ports. -- Eitan Adler From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 20:55:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D15F1065670 for ; Wed, 27 Apr 2011 20:55:47 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp01.lnh.mail.rcn.net (smtp11.lnh.mail.rcn.net [207.172.157.101]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9ED8FC16 for ; Wed, 27 Apr 2011 20:55:45 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 16:55:44 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BAW08630; Wed, 27 Apr 2011 16:55:44 -0400 Received-SPF: None identity=pra; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="mi+thun@aldan.algebra.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="mi+thun@aldan.algebra.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.61.133; receiver=smtp01.lnh.mail.rcn.net; envelope-from="mi+thun@aldan.algebra.com"; x-sender="postmaster@utka.zajac"; x-conformance=sidf_compatible X-Auth-ID: anat Received: from 209-6-61-133.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com (HELO utka.zajac) ([209.6.61.133]) by smtp01.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 16:55:38 -0400 Message-ID: <4DB882C8.8090604@aldan.algebra.com> Date: Wed, 27 Apr 2011 16:55:36 -0400 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Wesley Shields References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> <20110427204723.GA74591@atarininja.org> In-Reply-To: <20110427204723.GA74591@atarininja.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Apr 2011 21:04:11 +0000 Cc: Eitan Adler , Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:55:47 -0000 On 27.04.2011 16:47, Wesley Shields wrote: > apache13 is EOL upstream. We should not have ports for EOL software. Why not, exactly?.. > If upstream says it's dead, who are we to keep it alive? We are a major Operating System project, which maintains ports of third-party applications for the convenience of our users. An EOL-declaration by the authors does not mean, the users must stop using it immediately -- it simply says, the authors will not be releasing updates/bug-fixes. -mi From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 21:06:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7985A106564A for ; Wed, 27 Apr 2011 21:06:28 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 21A3E8FC16 for ; Wed, 27 Apr 2011 21:06:27 +0000 (UTC) Received: by vws18 with SMTP id 18so2130916vws.13 for ; Wed, 27 Apr 2011 14:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=8mHjvomwOI3w5IPx7cAFLQ8DUzxccbR/SmCTWn6Y5YQ=; b=ariqPIg0HUbP/GLrnbtYdaihYkn8Fx5SypBHmasWTCM5GZUf3QOwu6hgbicjfnxh70 9hdN+FA5FRDCTwDaPIzRh/hi9UKVpOLcLlDli7B7szuwWdUHNSGC0yGj0hdzQL+i862a FCjQNW6vK0Z5vt2iUbvTRbGpRpjhKK4pRQ/Nk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=GcnNJkiKap3JDdHph/eKwssImfJ6OTUGJj/GdCR5PJZOtB0flol49OEpD77AL74omq pIqmPkIwvFm6rvp5Fd0ElnAU7Z2kehAt/LocpJhMBBMIrf82MEs0j0qa3asY5Zkw+mkE SH/AYQMYx/a8vxIYVt/bRtq+GJG6VcaIpDjaw= Received: by 10.52.98.3 with SMTP id ee3mr3923734vdb.140.1303938387088; Wed, 27 Apr 2011 14:06:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Wed, 27 Apr 2011 14:05:57 -0700 (PDT) In-Reply-To: <4DB882C8.8090604@aldan.algebra.com> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> <20110427204723.GA74591@atarininja.org> <4DB882C8.8090604@aldan.algebra.com> From: Eitan Adler Date: Wed, 27 Apr 2011 17:05:57 -0400 Message-ID: To: "Mikhail T." Content-Type: text/plain; charset=UTF-8 Cc: Wesley Shields , Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:06:28 -0000 >> apache13 is EOL upstream. We should not have ports for EOL software. > > Why not, exactly?.. What happens if a security hole or a bug is found? Are we the ones to fix it? If yes are we to host the patches? Where should the bug reports go to - our bug tracker? What if our implementation ceases to match established documentation? Should we host the docs too? The ports collection is one of *third party* software (with a couple of small exceptions). If the third party says "this program is done, has bugs which won't be fixed, etc" we should no longer support it. >> >> If upstream says it's dead, who are we to keep it alive? > > We are a major Operating System project, which maintains ports of > third-party applications for the convenience of our users. An > EOL-declaration by the authors does not mean, the users must stop using it > immediately -- it simply says, the authors will not be releasing > updates/bug-fixes. Correct. However (a) if the third party gave an upgrade path we should encourage our users to use it and (b) if there *are* known bugs and especially security holes we should cease to make it available through our tree. If a user says "I found an issue with X and it is EOL upstream" the correct response is to "upgrade to a supported version". However this discussion is different to the one that we started with (namely that of deprecated ports) so lets try and get back on track :-) -- Eitan Adler From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 21:37:57 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA35F106566B for ; Wed, 27 Apr 2011 21:37:57 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6F40F8FC1A for ; Wed, 27 Apr 2011 21:37:57 +0000 (UTC) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta01.westchester.pa.mail.comcast.net with comcast id cldx1g0071uE5Es51ldx8G; Wed, 27 Apr 2011 21:37:57 +0000 Received: from comcast.net ([98.203.142.76]) by omta16.westchester.pa.mail.comcast.net with comcast id cldq1g00l1f6R9u3clduJG; Wed, 27 Apr 2011 21:37:57 +0000 Received: by comcast.net (sSMTP sendmail emulation); Wed, 27 Apr 2011 14:37:48 -0700 Date: Wed, 27 Apr 2011 14:37:48 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110427213748.GK38579@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> <20110427204723.GA74591@atarininja.org> <4DB882C8.8090604@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:37:57 -0000 On Wed 27 Apr 2011 at 14:05:57 PDT Eitan Adler wrote: >>> apache13 is EOL upstream. We should not have ports for EOL software. >> >> Why not, exactly?.. > >What happens if a security hole or a bug is found? Are we the ones to >fix it? No. The rule of caveat emptor should apply. We don't warranty anything else in the portstree, why would you think that there's an implied warranty in this scenario? >If yes are we to host the patches? The question is moot, given a negative answer to the preceding one. >Where should the bug reports go to - our bug tracker? If they do get submitted there, they should be immediately closed as "Won't Fix". >What if our implementation ceases to match established documentation? >Should we host the docs too? Same answers as above. > >The ports collection is one of *third party* software (with a couple >of small exceptions). If the third party says "this program is done, >has bugs which won't be fixed, etc" we should no longer support it. Keeping it in the tree != obligation to provide support, i.e., bugfixes for anything except the port Makefile and other port-related files. As long as there's a maintainer willing to do the work to keep it running (warts and all) on the currently-supported FreeBSD releases, I don't see any reason why it can't be kept in the tree. >>> >>> If upstream says it's dead, who are we to keep it alive? >> >> We are a major Operating System project, which maintains ports of >> third-party applications for the convenience of our users. An >> EOL-declaration by the authors does not mean, the users must stop using it >> immediately -- it simply says, the authors will not be releasing >> updates/bug-fixes. > >Correct. However (a) if the third party gave an upgrade path we should >encourage our users to use it and (b) if there *are* known bugs and >especially security holes we should cease to make it available through >our tree. Agree with (a) but maybe not (b). That's a decision that should be left to the users. > > If a user says "I found an issue with X and it is EOL upstream" the >correct response is to "upgrade to a supported version". See above. >However this discussion is different to the one that we started with >(namely that of deprecated ports) so lets try and get back on track :-) Actually, it's a closely related question. From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 21:39:29 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CA94106564A for ; Wed, 27 Apr 2011 21:39:29 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id E13428FC14 for ; Wed, 27 Apr 2011 21:39:28 +0000 (UTC) Received: from c-24-22-230-24.hsd1.wa.comcast.net ([24.22.230.24] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QFCSD-0004Cg-53 for freebsd-ports@freebsd.org; Wed, 27 Apr 2011 17:39:26 -0400 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Wed, 27 Apr 2011 14:39:24 -0700 Date: Wed, 27 Apr 2011 14:39:24 -0700 From: Chip Camden To: FreeBSD Ports Message-ID: <20110427213924.GE2729@libertas.local.camdensoftware.com> Mail-Followup-To: FreeBSD Ports References: <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <20110427184625.GC2729@libertas.local.camdensoftware.com> <66B715DB-4C55-4508-AD14-C7A0CF51C111@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tVmo9FyGdCe4F4YN" Content-Disposition: inline In-Reply-To: <66B715DB-4C55-4508-AD14-C7A0CF51C111@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:39:29 -0000 --tVmo9FyGdCe4F4YN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Ade Lovett on Wednesday, 27 April 2011: > On Apr 27, 2011, at 13:46 , Chip Camden wrote: > >=20 > > Modifying the script that was posted earlier, we can list out all > > installed ports that are currently deprecated, and why: >=20 > Won't work -- need to handle slave ports etc, where the DEPRECATED may be= in the MASTER_PORT. >=20 > Try this: >=20 > #!/bin/sh > # > PORTSDIR=3D${1-"/usr/ports"} > for port in $(pkg_info -oa | grep /) > do > dep=3D$(make -C ${PORTSDIR}/${port} -V DEPRECATED) > [ -n "${dep}" ] && echo "${port}: ${dep}" > done >=20 >=20 > -aDe >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Nice, thanks! --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --tVmo9FyGdCe4F4YN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJNuI0MAAoJEIpckszW26+RlS0IAKLIWd6tx9ALrw+rIUe1qJkb InggdaEPoe3xWS4PrHcJbASD/+ahKpehvC5XRPgnNflPPmhR7dMiXee6mo0Sje3Q XV8bMc1y03HTtz/9GlzjLkc8BqBnyURkbTI4OlYqOI6mLJZwu3b7iIERNLvrJLqK hQrxxiFNOIKz17HaGr2UDehNiDjy/n0KHnsk8n6W6nBIxIC6FpXYOwXsR9qH8yFX eVcnzXm8xkhFwEU/eo7/HxZhnIE3d0z9xb5TIlwdTcGWrqJZ7dPcR6LL3l4HmuN5 xTOGHBHrH97CEoTrEUflfkd2WigvwXv5TvzRw31AVSvfuUIoCuXlJBqUcbQOKN8= =eHB/ -----END PGP SIGNATURE----- --tVmo9FyGdCe4F4YN-- From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 21:10:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 495221065670 for ; Wed, 27 Apr 2011 21:10:04 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp03.lnh.mail.rcn.net (smtp03.lnh.mail.rcn.net [207.172.157.103]) by mx1.freebsd.org (Postfix) with ESMTP id E67408FC1D for ; Wed, 27 Apr 2011 21:10:03 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 17:10:03 -0400 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BAW11549; Wed, 27 Apr 2011 17:10:02 -0400 X-Auth-ID: anat Received: from 209-6-61-133.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com (HELO utka.zajac) ([209.6.61.133]) by smtp04.lnh.mail.rcn.net with ESMTP; 27 Apr 2011 17:10:01 -0400 Message-ID: <4DB88629.9060802@aldan.algebra.com> Date: Wed, 27 Apr 2011 17:10:01 -0400 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Eitan Adler References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> In-Reply-To: X-Mailman-Approved-At: Wed, 27 Apr 2011 21:40:12 +0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:10:04 -0000 Eitan, you are entitled to your opinions, but not to your own facts. My factual corrections are inline below. Arguing about opinions and policy is useless until the facts are accepted as such by all participants: On 27.04.2011 16:54, Eitan Adler wrote: > The upstream maintainer already called it "end of life". FreeBSD does > not and will not ever take over the development of dead upstream ports > (and in this case there is a upstream version) I never suggested, we undertake /development/ of upstream software -- EOLed or not. Fact 1. >> The same entity(ies), that currently busy themselves marking things>"deprecated". > The ports marked "broken with no one to fix them" (shortened to > 'deprecated') take a significant amount of time and energy to fix. db2 was not broken. Neither is apache13... Fact 2. > Which is a *major* drain of resources. "Major"? Didn't you say earlier, that the most recent sweep -- only deleted about 3% of the ports? I'd say, this is Fact 3, but, maybe, even 3% qualifies as "major" in your view... And was not this sweep the largest in our history? > What you fail to understand is that we are NOT marking ports as > 'obsolete' or 'bad' or 'there exists a better program' but as broken > and unmaintained. I can only repeat the example of db2. It was never broken, but deleted nonetheless... The same is about to happen to apache13... -mi From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:01:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69DDD106566B for ; Wed, 27 Apr 2011 22:01:48 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp05.sth.basefarm.net (ch-smtp05.sth.basefarm.net [80.76.153.6]) by mx1.freebsd.org (Postfix) with ESMTP id E664E8FC18 for ; Wed, 27 Apr 2011 22:01:47 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:29934 helo=falcon.midgard.homeip.net) by ch-smtp05.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QFCnd-0001pG-HT for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 00:01:35 +0200 Received: (qmail 18876 invoked from network); 27 Apr 2011 23:54:52 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 27 Apr 2011 23:54:52 +0200 Received: (qmail 32174 invoked by uid 1001); 27 Apr 2011 23:54:52 +0200 Date: Wed, 27 Apr 2011 23:54:52 +0200 From: Erik Trulsson To: Eitan Adler Message-ID: <20110427215452.GA32138@owl.midgard.homeip.net> References: <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> <20110427204723.GA74591@atarininja.org> <4DB882C8.8090604@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QFCnd-0001pG-HT. X-Scan-Signature: ch-smtp05.sth.basefarm.net 1QFCnd-0001pG-HT 4e228d245335f4222b45dd655a3fd01a Cc: "Mikhail T." , Robert Huff , Wesley Shields , freebsd-ports@freebsd.org, Chip Camden Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:01:48 -0000 On Wed, Apr 27, 2011 at 05:05:57PM -0400, Eitan Adler wrote: > >> apache13 is EOL upstream. We should not have ports for EOL software. > > > > Why not, exactly?.. > > What happens if a security hole or a bug is found? Are we the ones to > fix it? If yes are we to host the patches? Where should the bug > reports go to - our bug tracker? What if our implementation ceases to > match established documentation? Should we host the docs too? "We"? Who is this "we" you keep talking about here? If a port has a security hole then it is up to the maintainer to find a fix for it - if this fix is a patch he/she comes up with or a switch to a newer upstream version is irrelevant. If there is no maintainer and nobody else provides a fix either, it is time to mark the port as FORBIDDEN and DEPRECATED and remove it after the deprecation period expires, just like how other broken ports are handled. > > The ports collection is one of *third party* software (with a couple > of small exceptions). If the third party says "this program is done, > has bugs which won't be fixed, etc" we should no longer support it. Depends on what you mean by "support", but removing a port just because upstream development has ceased is just plain silly. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:18:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AFAA106566C for ; Wed, 27 Apr 2011 22:18:23 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp04.sth.basefarm.net (ch-smtp04.sth.basefarm.net [80.76.153.5]) by mx1.freebsd.org (Postfix) with ESMTP id 25A868FC20 for ; Wed, 27 Apr 2011 22:18:22 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:32672 helo=falcon.midgard.homeip.net) by ch-smtp04.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QFD3m-0000wt-DY for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 00:18:16 +0200 Received: (qmail 18985 invoked from network); 28 Apr 2011 00:18:13 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 28 Apr 2011 00:18:13 +0200 Received: (qmail 32269 invoked by uid 1001); 28 Apr 2011 00:18:13 +0200 Date: Thu, 28 Apr 2011 00:18:13 +0200 From: Erik Trulsson To: John Marino Message-ID: <20110427221813.GB32138@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB8664D.70001@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB8664D.70001@marino.st> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QFD3m-0000wt-DY. X-Scan-Signature: ch-smtp04.sth.basefarm.net 1QFD3m-0000wt-DY 75065ffda588adab56627b070cf34ea7 Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:18:23 -0000 On Wed, Apr 27, 2011 at 08:54:05PM +0200, John Marino wrote: > On 4/27/2011 4:12 PM, Jerry wrote: > > On Wed, 27 Apr 2011 15:48:36 +0200 > > Erik Trulsson articulated: > > > >> On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: > >> Very simple. A particular committer during one particular period of > >> time maybe only 45 minutes of free time to spend on handling PRs. > >> If the committer estimates that one large submitted PR would take at > >> least two hours to review, test, and commit, while another, smaller, > >> PR would only take 30 minutes to handle. > >> > >> Then the committer in question would have two choices: Don't handle > >> either submission, or handling the smaller submission, while skipping > >> the large one and hoping that some other committer with more free time > >> will pick up that one. > >> I see no reason to prefer the first of these choices. > > If the committer cannot finish the project in their allotted time > > frame they simply stop and pick up from that point in their next > > session. I have literally hundreds of projects that I cannot complete > > in one day; however, I don't simply shrug them off. If I did nothing > > would ever get accomplished, or at best only the easiest assignments. > > > > One of the basic fallacies in your analysis is that someone else will > > pick up the slack. Unfortunately, our society has become over run by > > those who are always ready to blame others or expect others to do our > > job for us. Quite honestly, I find that pathetic. > > > > I seemed to have kicked off quite a dialog! First of all, I want to > thank Frederic Culot for committing my patch today. > > Basically, I'm in complete agreement with Jerry with regards to FIFO. > The proposal was made that given a short amount a time, a committer > should choose the simpler project and bypass the first one simply based > on time/complexity. I couldn't disagree more. As soon as it's possible > to skip valid ports, then that's what is going to happen. If people can > physically cherry-pick, then they'll exercise their ability to do that > and immediately you sink into the current situation. And if the committers can't choose what they are going to work on, you are likely going find yourself with a lot fewer committers fairly soon. > > Unfortunately, a FIFO setup requires that all the requests go through a > single entity who then assigns them. And who is going to do all that extra work? You volunteering? > I don't really buy the > joe-the-font-guy with mary-the-network-gal mismatch. Nobody said the > PRs have to be assigned as round-robin. And then that changes the > dynamic since the PR is assigned rather than chosen. This entity can't > just assign a PR without knowing the committer's timeline, availability, > etc, so there are clearly implementation details to work out. Details indeed, and the devil is in the details as the saying goes. First of all there is no entity that knows about the timeline, availability, etc. of the various committers. The only way to get that information would be if committers were to report it at regular intervals which they don't have any reason to do. There is also the question of what to do if a committer doesn't like all the proposed extra rules and bureacracy and simply ignores a PR he has been assigned. There isn't really any way force a given committer to work on something he doesn't want to work on. The only sanction available is to remove the commit bit at which point you have one committer less, and that work still isn't done. > > Maybe a compromise would be to keep the current system in place with the > addition of having somebody do these assignments if the new PRs are > unclaimed for more than 3-7 days. Yes, it means a new job for someone, > but if one believes that FIFO is the fair and respectful approach, the > extra effort should be worth it. Worth it for who? Hardly to the guy who is going to do the extra work. As for "fair" you haven't convinced me why it should be a requirement. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:33:27 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12B0E106564A for ; Wed, 27 Apr 2011 22:33:27 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp04.sth.basefarm.net (ch-smtp04.sth.basefarm.net [80.76.153.5]) by mx1.freebsd.org (Postfix) with ESMTP id 91FDD8FC16 for ; Wed, 27 Apr 2011 22:33:26 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:26359 helo=falcon.midgard.homeip.net) by ch-smtp04.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QFDI9-0004pP-Em for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 00:33:07 +0200 Received: (qmail 19048 invoked from network); 28 Apr 2011 00:33:05 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 28 Apr 2011 00:33:05 +0200 Received: (qmail 32332 invoked by uid 1001); 28 Apr 2011 00:33:05 +0200 Date: Thu, 28 Apr 2011 00:33:05 +0200 From: Erik Trulsson To: freebsd-ports@freebsd.org Message-ID: <20110427223305.GA32276@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427101257.414aaf8b@seibercom.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QFDI9-0004pP-Em. X-Scan-Signature: ch-smtp04.sth.basefarm.net 1QFDI9-0004pP-Em 229f8eff2288bd4f5b94bea85659132f Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:33:27 -0000 On Wed, Apr 27, 2011 at 10:12:57AM -0400, Jerry wrote: > On Wed, 27 Apr 2011 15:48:36 +0200 > Erik Trulsson articulated: > > > On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: > > > On Wed, 27 Apr 2011 08:50:52 -0400 > > > > > > However, I do find troubling you statement regarding a large update > > > to an older port or even a new port submission for that matter. I > > > see no logical reason for a committer to bypass an item simple > > > based on its size or the amount of work involved in getting it > > > committed. After all, consider that the original submitter invested > > > a large amount of his/her time in that same item. > > > > Very simple. A particular committer during one particular period of > > time maybe only 45 minutes of free time to spend on handling PRs. > > If the committer estimates that one large submitted PR would take at > > least two hours to review, test, and commit, while another, smaller, > > PR would only take 30 minutes to handle. > > > > Then the committer in question would have two choices: Don't handle > > either submission, or handling the smaller submission, while skipping > > the large one and hoping that some other committer with more free time > > will pick up that one. > > I see no reason to prefer the first of these choices. > > If the committer cannot finish the project in their allotted time > frame they simply stop and pick up from that point in their next > session. Or they can take a look at that project, decide that they are not interested in doing that particular project, and say "Screw this, I have better things do with my free time" and go off and read a book instead. > I have literally hundreds of projects that I cannot complete > in one day; however, I don't simply shrug them off. If I did nothing > would ever get accomplished, or at best only the easiest assignments. Hundreds? Sounds a bit excessive if you were to ask me. If you have that many things to do then FIFO is a downright stupid way to approach them unless you know you have enough time to do *all* of them. (And it is rare that there is that much time available.) With that many things to do one needs to prioritize. First one should do the important stuff, and if there is any time left after having done that one might as well pick the fun projects, because there just isn't much point in doing boring, unimportant stuff. > > One of the basic fallacies in your analysis is that someone else will > pick up the slack. Unfortunately, our society has become over run by > those who are always ready to blame others or expect others to do our > job for us. Quite honestly, I find that pathetic. And yet you are so quick at blaming committers for not doing things the way you think they should be done. Pot. Kettle. Black. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:39:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAD7F106566B for ; Wed, 27 Apr 2011 22:39:58 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id BB4CC8FC15 for ; Wed, 27 Apr 2011 22:39:58 +0000 (UTC) Received: from [192.168.0.11] (atoulouse-256-1-41-46.w90-38.abo.wanadoo.fr [90.38.232.46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 94D78435D7 for ; Wed, 27 Apr 2011 17:39:57 -0500 (CDT) Message-ID: <4DB89B38.4000404@marino.st> Date: Thu, 28 Apr 2011 00:39:52 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB8664D.70001@marino.st> <20110427221813.GB32138@owl.midgard.homeip.net> In-Reply-To: <20110427221813.GB32138@owl.midgard.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:39:59 -0000 On 4/28/2011 12:18 AM, Erik Trulsson wrote: > And if the committers can't choose what they are going to work on, you > are likely going find yourself with a lot fewer committers fairly soon. > As you notice, I never said they are limited what they work on. The order of the work is the focus. > And who is going to do all that extra work? You volunteering? If finding a volunteer is the only thing holding a reform back, then we have nothing to worry about. > > Details indeed, and the devil is in the details as the saying goes. > First of all there is no entity that knows about the timeline, > availability, etc. of the various committers. The only way to get that > information would be if committers were to report it at regular > intervals which they don't have any reason to do. I thought it was clear that I was saying that wouldn't work. > There is also the question of what to do if a committer doesn't like > all the proposed extra rules and bureacracy and simply ignores a PR he > has been assigned. There isn't really any way force a given committer > to work on something he doesn't want to work on. The only sanction > available is to remove the commit bit at which point you have one > committer less, and that work still isn't done. I was working the assumption that he agrees to the port up front or voluntarily picks up the next task. However, if someone has a repeated history of refusals or only wants to do a very narrow set of tasks, then maybe commit bit removal isn't that dramatic. > Worth it for who? Hardly to the guy who is going to do the extra work. > As for "fair" you haven't convinced me why it should be a requirement. I don't consider it extra work. I consider it doing the job correctly. And if I need to convince you that "fair" is correct, then basically I just wasted 5 minutes answering this post. Jerry pretty much outlined why it's correct to process these things in order, or at some semblance of order. Look, your mind is made up. You like the status quo. Everything is fine and no effort should be made to improve. I'm not interested in a long, drawn out discussion. I just wanted to give my opinion which I did, so I'm done. John From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:40:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43D251065670 for ; Wed, 27 Apr 2011 22:40:23 +0000 (UTC) (envelope-from ohauer@FreeBSD.org) Received: from u18-124.dslaccess.de (unknown [194.231.39.124]) by mx1.freebsd.org (Postfix) with ESMTP id DE6DB8FC0A for ; Wed, 27 Apr 2011 22:40:22 +0000 (UTC) Received: from [172.20.1.100] (cde1100.uni.vrs [172.20.1.100]) (Authenticated sender: ohauer) by u18-124.dslaccess.de (Postfix) with ESMTPSA id A9E042020B; Thu, 28 Apr 2011 00:40:13 +0200 (CEST) Message-ID: <4DB89B4E.4050206@FreeBSD.org> Date: Thu, 28 Apr 2011 00:40:14 +0200 From: Olli Hauer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Mikhail T." References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> In-Reply-To: <4DB83D6E.9000800@aldan.algebra.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ohauer@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:40:23 -0000 On 2011-04-27 17:59, Mikhail T. wrote: > On -10.01.-28163 14:59, Robert Huff wrote: >> It is also possible it is only important to a fairly small >> number ... but to those it is absolutely crucial. > Or the port might become useful/essential/critical to somebody in the future... > > What is not broken -- just old, like databases/db2 or www/apache13*, for > example -- should be left alone (until it becomes both broken and unmaintained). > And even then, the removal should not be mass-scale/automatic... What are you missing in the db2 implementation of FreeBSD which is in the OS and maintained by the OS developers? For myself I see the apache13 EOL with a whining and a laughing eye, and can understand if users don't want to upgrade to 22/24 because of complex and working configurations. But I also look at the future development of the OS and environment where such old dinosaur should see a ice time to make room for new live. Within the apache13/20 deprecation also other ports will go since they are not compatible with newer apache version. For anyone interested I've done a quick grep over my local build logs to get a list of ports which depends on apache13/20 http://people.freebsd.org/~ohauer/diffs/apache_ports/apache13_ports.log http://people.freebsd.org/~ohauer/diffs/apache_ports/apache20_ports.log Most of the ports have equivalents for apache22. http://people.freebsd.org/~ohauer/diffs/apache_ports/apache22_ports.log All those ports where build with the following setting in bsd.apache.mk DEFAULT_APACHE_VERSION= 22 APACHE_SUPPORTED_VERSION= 22 13 20 -- olli From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 22:54:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C6D2106566C for ; Wed, 27 Apr 2011 22:54:48 +0000 (UTC) (envelope-from ohauer@FreeBSD.org) Received: from u18-124.dslaccess.de (unknown [194.231.39.124]) by mx1.freebsd.org (Postfix) with ESMTP id 2E2BA8FC0A for ; Wed, 27 Apr 2011 22:54:48 +0000 (UTC) Received: from [172.20.1.100] (cde1100.uni.vrs [172.20.1.100]) (Authenticated sender: ohauer) by u18-124.dslaccess.de (Postfix) with ESMTPSA id D5D1F2020B; Thu, 28 Apr 2011 00:54:43 +0200 (CEST) Message-ID: <4DB89EB5.2010603@FreeBSD.org> Date: Thu, 28 Apr 2011 00:54:45 +0200 From: Olli Hauer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> In-Reply-To: <20110427101257.414aaf8b@seibercom.net> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Jerry Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ohauer@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:54:48 -0000 On 2011-04-27 16:12, Jerry wrote: > On Wed, 27 Apr 2011 15:48:36 +0200 > Erik Trulsson articulated: > >> On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: >>> On Wed, 27 Apr 2011 08:50:52 -0400 >>> >>> However, I do find troubling you statement regarding a large update >>> to an older port or even a new port submission for that matter. I >>> see no logical reason for a committer to bypass an item simple >>> based on its size or the amount of work involved in getting it >>> committed. After all, consider that the original submitter invested >>> a large amount of his/her time in that same item. >> >> Very simple. A particular committer during one particular period of >> time maybe only 45 minutes of free time to spend on handling PRs. >> If the committer estimates that one large submitted PR would take at >> least two hours to review, test, and commit, while another, smaller, >> PR would only take 30 minutes to handle. >> >> Then the committer in question would have two choices: Don't handle >> either submission, or handling the smaller submission, while skipping >> the large one and hoping that some other committer with more free time >> will pick up that one. >> I see no reason to prefer the first of these choices. > > If the committer cannot finish the project in their allotted time > frame they simply stop and pick up from that point in their next > session. I have literally hundreds of projects that I cannot complete > in one day; however, I don't simply shrug them off. If I did nothing > would ever get accomplished, or at best only the easiest assignments. > > One of the basic fallacies in your analysis is that someone else will > pick up the slack. Unfortunately, our society has become over run by > those who are always ready to blame others or expect others to do our > job for us. Quite honestly, I find that pathetic. > Maybe you have some time to spend? If my quick lookup was not totally wrong I cannot find one PR opened by you. http://www.freebsd.org/cgi/query-pr-summary.cgi?originator=seibercom&closedtoo=on From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 23:10:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 4A662106566C for ; Wed, 27 Apr 2011 23:10:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6B59414D879; Wed, 27 Apr 2011 23:10:19 +0000 (UTC) Message-ID: <4DB8A25B.50407@FreeBSD.org> Date: Wed, 27 Apr 2011 16:10:19 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Marino References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB8664D.70001@marino.st> <20110427221813.GB32138@owl.midgard.homeip.net> <4DB89B38.4000404@marino.st> In-Reply-To: <4DB89B38.4000404@marino.st> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 23:10:21 -0000 On 04/27/2011 15:39, John Marino wrote: > As you notice, I never said they are limited what they work on. The > order of the work is the focus. John, You (and others) seem to be very focused on the idea of what's "fair." Specifically you seem to believe that FreeBSD committers have a duty to handle PRs in a FIFO order, because that is what is "most fair" to the PR submitters. Short answer, that view is unrealistic, and will not be implemented. Longer answer. I understand your frustration. Those are not just empty words, I may be a committer for FreeBSD but I'm also an "individual contributor" for other projects, and I have to sit around and wait until someone looks at the bugs and/or patches that I contribute to those projects just like people contributing to FreeBSD do. It's really annoying to put a lot of work into a submission and then have it wallow in the queue. No one is denying that. However, and I realize that many of you don't like this answer, but it's the truth. This *is* a volunteer project. If we tried to "require" committers to do what you suggest, we'd lost most of them. Let me give you a very real, concrete example. Recently I picked up a new task, and needed a tool to do that task. We had a version of the tool in the ports collection but it was out of date. Before embarking on updating it myself, I looked in the PR db, and there was exactly what I needed, a patch to update the port to the latest version. Now let's assume that we adopted your rule. At that point I would have 2 options. Either commit all the patches between it and the one I needed, or leave the patch uncommitted. I'm a busy guy, I have a lot of demands on my time. (And don't forget, I got here because I have an actual project that needs to be finished.) Is it "fair" to me to require me to do all of that unrelated work just so I can get this one patch into the tree? Is it "fair" to the submitter of the patch that I _not_ commit it because I don't have the time to do all that other work? Let's look at it another way. Let's suppose we implement your idea, but in order to make it more practical we implement a companion policy that before you can _submit_ a patch you have to go through all the other patches in the queue ahead of yours and test them, then submit your findings. (We're going to do this because that way when a committer gets around to a patch they will have a very good idea of whether it's suitable or not.) Is that "fair" to you? How many patches do you think we'd get from individual contributors if we required that amount of work before you could even submit a patch? hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 23:15:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98E1D106566B for ; Wed, 27 Apr 2011 23:15:23 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by mx1.freebsd.org (Postfix) with ESMTP id 436CE8FC08 for ; Wed, 27 Apr 2011 23:15:22 +0000 (UTC) Received: by gxk19 with SMTP id 19so1123540gxk.17 for ; Wed, 27 Apr 2011 16:15:22 -0700 (PDT) Received: by 10.151.59.18 with SMTP id m18mr2452139ybk.94.1303946122242; Wed, 27 Apr 2011 16:15:22 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id t5sm666970ybe.14.2011.04.27.16.15.21 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 16:15:21 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKcZw0DJwz2CG5G for ; Wed, 27 Apr 2011 19:15:20 -0400 (EDT) Date: Wed, 27 Apr 2011 19:15:19 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427191519.6388a158@seibercom.net> In-Reply-To: <20110427223305.GA32276@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <20110427223305.GA32276@owl.midgard.homeip.net> Followup-To: freebsd-ports@freebsd.org Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 23:15:23 -0000 On Thu, 28 Apr 2011 00:33:05 +0200 Erik Trulsson articulated: > On Wed, Apr 27, 2011 at 10:12:57AM -0400, Jerry wrote: > > On Wed, 27 Apr 2011 15:48:36 +0200 > > Erik Trulsson articulated: > > > > > On Wed, Apr 27, 2011 at 09:32:58AM -0400, Jerry wrote: > > > > On Wed, 27 Apr 2011 08:50:52 -0400 > > > > > > > > However, I do find troubling you statement regarding a large > > > > update to an older port or even a new port submission for that > > > > matter. I see no logical reason for a committer to bypass an > > > > item simple based on its size or the amount of work involved in > > > > getting it committed. After all, consider that the original > > > > submitter invested a large amount of his/her time in that same > > > > item. > > > > > > Very simple. A particular committer during one particular period > > > of time maybe only 45 minutes of free time to spend on handling > > > PRs. If the committer estimates that one large submitted PR would > > > take at least two hours to review, test, and commit, while > > > another, smaller, PR would only take 30 minutes to handle. > > > > > > Then the committer in question would have two choices: Don't > > > handle either submission, or handling the smaller submission, > > > while skipping the large one and hoping that some other committer > > > with more free time will pick up that one. > > > I see no reason to prefer the first of these choices. > > > > If the committer cannot finish the project in their allotted time > > frame they simply stop and pick up from that point in their next > > session. > > Or they can take a look at that project, decide that they are not > interested in doing that particular project, and say "Screw this, I > have better things do with my free time" and go off and read a book > instead. They might do that anyway. Seriously though, once you start cherry picking through assignments you have started down a slippery slope. > > I have literally hundreds of projects that I cannot complete > > in one day; however, I don't simply shrug them off. If I did nothing > > would ever get accomplished, or at best only the easiest > > assignments. > > Hundreds? Sounds a bit excessive if you were to ask me. > > If you have that many things to do then FIFO is a downright stupid way > to approach them unless you know you have enough time to do *all* of > them. (And it is rare that there is that much time available.) > With that many things to do one needs to prioritize. First one should > do the important stuff, and if there is any time left after having > done that one might as well pick the fun projects, because there just > isn't much point in doing boring, unimportant stuff. Following through on that logic, only the highest priority items would ever get done. Since there is a never ending list of things that have to be done at any given time, the lowest priority ones would never get any attention. Do you work for the government by any chance? > > One of the basic fallacies in your analysis is that someone else > > will pick up the slack. Unfortunately, our society has become over > > run by those who are always ready to blame others or expect others > > to do our job for us. Quite honestly, I find that pathetic. > > And yet you are so quick at blaming committers for not doing things > the way you think they should be done. Pot. Kettle. Black. It is not the committers per se that I am questioning, but rather the overall protocol used for assigning each project and seeing it through to completion. I have all ready had a few who either are more knowledgeable about the present situation or at least are better equipped to converse about it than yourself, post regarding the present situation. By the way, is your reference to "Black" a race reference? And what could you possibly have against a defenseless "Kettle"? Personally, I think you have been spending too much time with the "Pot". You are becoming increasingly paranoid. Perhaps you should, as you so eloquently stated, "pick the fun projects, because there just isn't much point in doing boring, unimportant stuff." Lets leave those other projects for those who actually take pride in their work and don't just choose the easy way out. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Grief can take care of itself; but to get the full value of a joy you must have somebody to divide it with. Mark Twain From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 23:23:10 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A9EA4106566B for ; Wed, 27 Apr 2011 23:23:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 7B8D11551BE; Wed, 27 Apr 2011 23:23:09 +0000 (UTC) Message-ID: <4DB8A55C.9070101@FreeBSD.org> Date: Wed, 27 Apr 2011 16:23:08 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: Eitan Adler References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Mikhail T." , Robert Huff , Chip Camden , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 23:23:10 -0000 On 04/27/2011 13:54, Eitan Adler wrote: > Which is a*major* drain of resources. One of the reasons for ceasing > the building of packages for broken/completely obsolete is to avoid > draining the computer time building said packages. ... and in addition to CPU cycles there is also storage on the dozens of mirrors for packages, distfiles, cvs, etc. Almost all of those mirrors are provided by organizations that donate their resources to help the FreeBSD community. Many of them are already stretched thin. I don't think the view that "we don't provide a warranty" is realistic. If you took 100 FreeBSD users and asked them, "Would you be surprised to find a known-bad version of something in the ports tree?" I think 99 of them would say, "yes!" Those who want to keep EOL stuff around also seem to be ignoring that in FreeBSD the model is generally "maintainer knows best." To take apache13 as a specific example, the maintainers of that port have said pretty clearly, "it's a bad idea to keep using this, and we want to get rid of it ASAP." At least one of those maintainers is part of the ASF, so I tend to take his word on such things. Finally, as someone else pointed out, if you decide for yourself that you really really need something that's been removed from the ports tree, you can always dig it out of CVS. Yes, I realize that's extra work on your part, but that's part of the "price" of "free" software. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 23:25:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D31FB1065672 for ; Wed, 27 Apr 2011 23:25:59 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB968FC1A for ; Wed, 27 Apr 2011 23:25:59 +0000 (UTC) Received: by ywf7 with SMTP id 7so1063744ywf.13 for ; Wed, 27 Apr 2011 16:25:59 -0700 (PDT) Received: by 10.150.164.6 with SMTP id m6mr2573627ybe.351.1303946758118; Wed, 27 Apr 2011 16:25:58 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id w1sm669466ybl.24.2011.04.27.16.25.56 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 16:25:57 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKcq762Ygz2CG5G for ; Wed, 27 Apr 2011 19:25:55 -0400 (EDT) Date: Wed, 27 Apr 2011 19:25:55 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427192555.65add0de@seibercom.net> In-Reply-To: <4DB89EB5.2010603@FreeBSD.org> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 23:25:59 -0000 On Thu, 28 Apr 2011 00:54:45 +0200 Olli Hauer articulated: > Maybe you have some time to spend? Before I could reasonable be expected to set aside time, I would need a detailed job description, etcetera. Perhaps you can supply me with one? > If my quick lookup was not totally wrong I cannot find one PR opened > by you. > http://www.freebsd.org/cgi/query-pr-summary.cgi?originator=seibercom&closedtoo=on And you won't either. The ports I maintain, and there are only a few, are under a different alias. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ nohup rm -fr /& From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 23:42:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0178B1065670 for ; Wed, 27 Apr 2011 23:42:31 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id AE8B88FC1A for ; Wed, 27 Apr 2011 23:42:30 +0000 (UTC) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta04.westchester.pa.mail.comcast.net with comcast id cn8G1g0011swQuc54niXeH; Wed, 27 Apr 2011 23:42:31 +0000 Received: from comcast.net ([98.203.142.76]) by omta15.westchester.pa.mail.comcast.net with comcast id cniU1g00w1f6R9u3bniVA8; Wed, 27 Apr 2011 23:42:30 +0000 Received: by comcast.net (sSMTP sendmail emulation); Wed, 27 Apr 2011 16:42:26 -0700 Date: Wed, 27 Apr 2011 16:42:26 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110427234226.GL38579@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <20110427223305.GA32276@owl.midgard.homeip.net> <20110427191519.6388a158@seibercom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20110427191519.6388a158@seibercom.net> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 23:42:31 -0000 On Wed 27 Apr 2011 at 16:15:19 PDT Jerry wrote: > >Following through on that logic, only the highest priority items would >ever get done. Since there is a never ending list of things that have >to be done at any given time, the lowest priority ones would never get >any attention. Which is as it should be, if it's true that we're faced with insufficient resources. The problem is that we don't have any objective way to determine priorities. Instead we leave this up to the personal interests and whims of the people involved -- maintainers AND committers. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 00:06:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F3DE1065670 for ; Thu, 28 Apr 2011 00:06:54 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp05.sth.basefarm.net (ch-smtp05.sth.basefarm.net [80.76.153.6]) by mx1.freebsd.org (Postfix) with ESMTP id 97F538FC15 for ; Thu, 28 Apr 2011 00:06:53 +0000 (UTC) Received: from c83-255-51-20.bredband.comhem.se ([83.255.51.20]:64645 helo=falcon.midgard.homeip.net) by ch-smtp05.sth.basefarm.net with esmtp (Exim 4.73) (envelope-from ) id 1QFEkZ-00064N-Ij for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 02:06:33 +0200 Received: (qmail 19608 invoked from network); 28 Apr 2011 02:06:31 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 28 Apr 2011 02:06:31 +0200 Received: (qmail 32929 invoked by uid 1001); 28 Apr 2011 02:06:31 +0200 Date: Thu, 28 Apr 2011 02:06:31 +0200 From: Erik Trulsson To: John Marino Message-ID: <20110428000631.GA32870@owl.midgard.homeip.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB8664D.70001@marino.st> <20110427221813.GB32138@owl.midgard.homeip.net> <4DB89B38.4000404@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB89B38.4000404@marino.st> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 83.255.51.20 X-Scan-Result: No virus found in message 1QFEkZ-00064N-Ij. X-Scan-Signature: ch-smtp05.sth.basefarm.net 1QFEkZ-00064N-Ij 340990d5accc04bf75b726eaa64c79e8 Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 00:06:54 -0000 On Thu, Apr 28, 2011 at 12:39:52AM +0200, John Marino wrote: > On 4/28/2011 12:18 AM, Erik Trulsson wrote: > > And if the committers can't choose what they are going to work on, you > > are likely going find yourself with a lot fewer committers fairly soon. > > > As you notice, I never said they are limited what they work on. The > order of the work is the focus. But if they are forced to do certain tasks first, there might well not be time over to do other things later. I.e. they are limited in what they work on. > > > > And who is going to do all that extra work? You volunteering? > > If finding a volunteer is the only thing holding a reform back, then we > have nothing to worry about. Hardly the only thing, merely one of the things. > > There is also the question of what to do if a committer doesn't like > > all the proposed extra rules and bureacracy and simply ignores a PR he > > has been assigned. There isn't really any way force a given committer > > to work on something he doesn't want to work on. The only sanction > > available is to remove the commit bit at which point you have one > > committer less, and that work still isn't done. > I was working the assumption that he agrees to the port up front or > voluntarily picks up the next task. However, if someone has a repeated > history of refusals or only wants to do a very narrow set of tasks, then > maybe commit bit removal isn't that dramatic. I didn't say anything about dramatic. My point is that removing that persons commit bit would not serve any useful purpose, and is not enough punishment that the threat of it is likely to convince any committer to do anything he doesn't fell like doing. > > Worth it for who? Hardly to the guy who is going to do the extra work. > > As for "fair" you haven't convinced me why it should be a requirement. > > I don't consider it extra work. I consider it doing the job correctly. > And if I need to convince you that "fair" is correct, then basically I > just wasted 5 minutes answering this post. Jerry pretty much outlined > why it's correct to process these things in order, or at some semblance > of order. Only under certain assumptions that are far from obviously correct. > > Look, your mind is made up. You like the status quo. Everything is > fine and no effort should be made to improve. I'm not interested in a > long, drawn out discussion. I just wanted to give my opinion which I > did, so I'm done. Oh, I am not saying that the current situation is ideal. It isn't. Far from it. What I am saying is that your proposed solution is a bad idea that is more likely to cause problems than to solve them. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 02:29:17 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9F3E106564A; Thu, 28 Apr 2011 02:29:17 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id E2F758FC0C; Thu, 28 Apr 2011 02:29:16 +0000 (UTC) Received: by fxm11 with SMTP id 11so2201829fxm.13 for ; Wed, 27 Apr 2011 19:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WrFNzp7F7Mkn7JYqs87gVGhP0E+Pk09TOvGxlv2fphQ=; b=B1y6LBINRqzpg6vYiYuE+uKmhWm6H73qdYoxEQVv5QOB/Kx8Su4PeV5BuOfmPkNmHj 4wAgXcPQS7i4teilSDvFAdy57sWZZJ/0Du8QDNL3EYR1n3Astb84OI4l80ZYQdtWu6rM GJBAkRACPfPULXezuev0R6WC4meAdrWgEB7+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=D0aTdTWPvnSLzSbg4vtNxHwdgFyZsNmNPc2tH0auBhcDc2I8zPqIpdZxF8zwYzjNDH C2Ngot8l1r2aXr9Ldqf1vC+Ruv1JeJ7is+LyIvslDKDkLJkaPuwaWp+KJizIU6qViE/9 I47LqmqAnw6MRNqZWPoiCaxO1LJQUDYCs0zOY= MIME-Version: 1.0 Received: by 10.223.106.78 with SMTP id w14mr1166429fao.35.1303956404008; Wed, 27 Apr 2011 19:06:44 -0700 (PDT) Received: by 10.223.20.145 with HTTP; Wed, 27 Apr 2011 19:06:42 -0700 (PDT) In-Reply-To: <430fcb25aefc374bf256e45e3151de15@bluelife.at> References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> Date: Wed, 27 Apr 2011 21:06:42 -0500 Message-ID: From: Adam Vande More To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 02:29:17 -0000 On Fri, Apr 22, 2011 at 6:01 AM, Bernhard Froehlich wrote: > It's about two months since the last call for testers and a lot of > bugfixing has happened since then. Not all of the reported problems were > FreeBSD related which is a good indication that we're not too far behind > the stability of the other hosts. So let's get it one once again. > Probably not a FreeBSD specific issue, but my legacy XP VM had an issue. When viewing the Settings screen, a warning came up saying invalid VM name. Checking that field revealed a blank name. Reentering the correct one allowed me to proceed with settings changes, but after closing and reopening the main Vbox GUI, then Settings tab again the VM name was again blank. I then created a new XP VM with an identical name which took. At first this seemed odd, but I see Virtualbox changed it's configuration directory location to perhaps a more Windows friendly. I ended up deleting the old configuration and it seems to be working correctly with the new one. Thanks for the work, -- Adam Vande More From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 07:59:29 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3447106566C; Thu, 28 Apr 2011 07:59:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id C21508FC16; Thu, 28 Apr 2011 07:59:29 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 5DB4856166; Thu, 28 Apr 2011 02:59:29 -0500 (CDT) Date: Thu, 28 Apr 2011 02:59:29 -0500 From: Mark Linimon To: freebsd-ports@freebsd.org Message-ID: <20110428075929.GA31875@lonesome.com> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427093258.3966cfd2@seibercom.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: linimon@FreeBSD.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 07:59:30 -0000 Let's play "let's pretend". Let's pretend I'n on the ports management team (true). Let's pretend I have enough influence to talk the rest of the ports management team into agreeing with me (very debatable, based on past performance.) Then, let's pretend that portmgr promotes a new policy, "all PRs must be handled in a FIFO manner." So ... what will the committers say? "Hey, no one asked me what I think, I didn't sign up for this, I think I'll find something else better to do. Wonder what's on TV?" And what should the portmgrs do? Hold our breaths until we turn blue? Well. As pointed out above, portmgr can either: suspend someone's commit bit, or not. In general, we only suspend for a year of inactivity. (For maintainers, the timeout on PRs is 2 weeks; we can reset after 3 months of inactivity). Anything more aggressive than that, will simply discourage existing, and potential, volunteers: both maintainers, and commiters. IMVVHO. (And yes, behind the scenes portmgr does a lot of work with twisting arms nd asking "are you sure you want to keep maintainership of port foo, since we have someone that seems willing to work on it?" But that's not the same as adding a new requirement for committers, ex post facto.) mcl From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 10:30:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAB751065707 for ; Thu, 28 Apr 2011 10:30:54 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 9BE458FC1C for ; Thu, 28 Apr 2011 10:30:54 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p3SAUm4B092219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Apr 2011 03:30:50 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p3SAUm15092218; Thu, 28 Apr 2011 03:30:48 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA01996; Thu, 28 Apr 11 02:51:33 PDT Date: Thu, 28 Apr 2011 02:50:19 -0700 From: perryh@pluto.rain.com To: lists@eitanadler.com Message-Id: <4db9385b.BbyRUhsUk+xTfsCB%perryh@pluto.rain.com> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: lists@opsec.eu, corky1951@comcast.net, freebsd-ports@freebsd.org Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 10:30:54 -0000 Eitan Adler wrote: > > I've been told that we shouldn't be looking for reasons > > to save any unmaintained port, > > What you have been told is "no-one steps up to (a) fix the > problem, (b) take maintainership and (c) _continue_ with > maintainership ... > > If you are stepping up to do the work that is great and we thank > you for that! We we don't want is people who only volunteer for > part (a) and don't continue with (b) and (c). > > > and I was specifically told this in response to my > > efforts to identify ports that have a lot of users. > > Merely finding "popular" ports does not help. We need people > who have the time and energy to maintain the ports. My reading was that Charlie _was_ "stepping up to do the work" -- all 3 parts of it. Since there weren't any unmaintained ports that he personally uses, he was volunteering to take on some that he does _not_ personally use, as a service to the community. In order to achieve The Greatest Good For The Greatest Number (TM), he wanted a way to identify "popular" unmaintained ports. His proposed method of finding out _where his efforts would do the most good for the community_ was met not with constructive suggestions, nor even mere indifference, but with outright hostility. Can you blame him for getting fed up, especially since this is apparently not the first time he has encountered that sort of attitude from those who should know better? > I do not want to say that "we are a volunteer project" and as such > are forgiven however such a model does change how we must do > things ... FreeBSD is indeed a volunteer project. Driving away would-be volunteers like Charlie -- and others who will now hesitate to take on port maintainership after reading how he has been treated -- is not in the Project's best interest. I think several contributors to this thread owe both Charlie and the community an apology. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 10:32:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D49FA1065675 for ; Thu, 28 Apr 2011 10:32:49 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5864B8FC12 for ; Thu, 28 Apr 2011 10:32:48 +0000 (UTC) Received: by bwz12 with SMTP id 12so3086881bwz.13 for ; Thu, 28 Apr 2011 03:32:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=eswBGi9cb2ighdsk37VrY81rkNMsdAHuN1IyewKtxpo=; b=v83C3Q0iZy7pH3ll1JdwfPiQ5IY4ST8OgX0SV7RPfizE7hm3HXkUmqMulo9NtkWTUf Gi5n7UGV2A1K4vbuW5e9UDCD0n3FT60BBUO9cJ1dpbmnbE4gMpwnGi9CvM/aoXc7UCX9 ARQ3Ak5fd3wiTYvs/5nPxfEZ37RG1hEr86ZSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=sKb0BwqZGHjne+sEFAIMXyp2psyMcTzIrRSrbWSy6hZ924QIMleNR913uRsszYHdJe yAixrGKhY5qaLVGraGobEjSEsfhsAOn5fhOdualfi99zs4Cgz+xSIeUKRkDQRBNd3T27 Fp5VF7IhtqRG0hX0VvXP+zSGuX5HRdoKXj684= MIME-Version: 1.0 Received: by 10.204.181.7 with SMTP id bw7mr3071482bkb.16.1303986767730; Thu, 28 Apr 2011 03:32:47 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Thu, 28 Apr 2011 03:32:45 -0700 (PDT) Received: by 10.204.42.21 with HTTP; Thu, 28 Apr 2011 03:32:45 -0700 (PDT) In-Reply-To: <4DB876AE.9050906@aldan.algebra.com> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB83D6E.9000800@aldan.algebra.com> <4DB876AE.9050906@aldan.algebra.com> Date: Thu, 28 Apr 2011 11:32:45 +0100 Message-ID: From: Chris Rees To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Adler , Chip Camden , Robert Huff , freebsd-ports@freebsd.org Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 10:32:49 -0000 On 27 Apr 2011 21:04, "Mikhail T." wrote: >> cvs's Attic can be easily restored if people take up the slack. I see >> no reason to change this policy > > No, not easily. It requires the CVS tree, which is not automatically installed. What are you on about? Just do an anonymous checkout, like every other time you access cvs for reading. Chris From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 11:04:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A654C1065674 for ; Thu, 28 Apr 2011 11:04:25 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gw0-f68.google.com (mail-gw0-f68.google.com [74.125.83.68]) by mx1.freebsd.org (Postfix) with ESMTP id 507CB8FC14 for ; Thu, 28 Apr 2011 11:04:25 +0000 (UTC) Received: by gwj19 with SMTP id 19so409737gwj.7 for ; Thu, 28 Apr 2011 04:04:24 -0700 (PDT) Received: by 10.236.18.106 with SMTP id k70mr4221489yhk.203.1303988664471; Thu, 28 Apr 2011 04:04:24 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id x72sm816435yhn.1.2011.04.28.04.04.22 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Apr 2011 04:04:23 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKwK11rcrz2CG5L for ; Thu, 28 Apr 2011 07:04:21 -0400 (EDT) Date: Thu, 28 Apr 2011 07:04:20 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110428070420.4a4704c1@seibercom.net> In-Reply-To: <20110427234226.GL38579@comcast.net> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <20110427223305.GA32276@owl.midgard.homeip.net> <20110427191519.6388a158@seibercom.net> <20110427234226.GL38579@comcast.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 11:04:25 -0000 On Wed, 27 Apr 2011 16:42:26 -0700 Charlie Kester articulated: > On Wed 27 Apr 2011 at 16:15:19 PDT Jerry wrote: > > > >Following through on that logic, only the highest priority items > >would ever get done. Since there is a never ending list of things > >that have to be done at any given time, the lowest priority ones > >would never get any attention. > > Which is as it should be, if it's true that we're faced with > insufficient resources. I hope, no, I pray that one of your PR's falls into that category. I can't wait to see how long it takes your ass to get online bitching and moaning about the lack of attention given to your trivial submission. > The problem is that we don't have any objective way to determine > priorities. Instead we leave this up to the personal interests and > whims of the people involved -- maintainers AND committers. If you had actually been paying attention rather than cherry picking assignments you would have noticed that this thread was about implementing a more effective protocol for handling submissions. The axiomatic statement, "Lead, follow, or get out of the way." by Thomas Paine would seem apropos. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ You can lead a horse to water, but you can't stop him from running off into the desert and dying of thirst. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 14:49:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73672106566C for ; Thu, 28 Apr 2011 14:49:17 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 278C18FC0C for ; Thu, 28 Apr 2011 14:49:16 +0000 (UTC) Received: by ywf7 with SMTP id 7so1383170ywf.13 for ; Thu, 28 Apr 2011 07:49:16 -0700 (PDT) Received: by 10.151.62.38 with SMTP id p38mr3173480ybk.12.1304002156109; Thu, 28 Apr 2011 07:49:16 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id q33sm924510yba.13.2011.04.28.07.49.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Apr 2011 07:49:14 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QL1JT12wMz2CG5L for ; Thu, 28 Apr 2011 10:49:13 -0400 (EDT) Date: Thu, 28 Apr 2011 10:49:12 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110428104912.1327aa49@seibercom.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: netpbm-10.35.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 14:49:17 -0000 The "netpbm-10.35.80_2" port won't build. There is a notation that the previous version has to be removed first. I saw something here a few days ago regarding that problem. Is the recommended method to do a "make deinstall && make reinstall" to get the updated port installed? I know that portupgrade chocks on the port if a previous version is installed. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Hire the morally handicapped. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 15:20:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2FD51065678 for ; Thu, 28 Apr 2011 15:20:28 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id BE3918FC21 for ; Thu, 28 Apr 2011 15:20:28 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.4/8.14.4) with ESMTP id p3SFKSnw016647 for ; Thu, 28 Apr 2011 08:20:28 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.4/8.14.4/Submit) id p3SFKSck016646 for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 08:20:28 -0700 (PDT) (envelope-from david) Date: Thu, 28 Apr 2011 08:20:28 -0700 From: David Wolfskill To: freebsd-ports@freebsd.org Message-ID: <20110428152028.GS1733@albert.catwhisker.org> References: <20110428104912.1327aa49@seibercom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JQ29orswtRjjfiJM" Content-Disposition: inline In-Reply-To: <20110428104912.1327aa49@seibercom.net> User-Agent: Mutt/1.4.2.3i Subject: Re: netpbm-10.35.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 15:20:29 -0000 --JQ29orswtRjjfiJM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 28, 2011 at 10:49:12AM -0400, Jerry wrote: > The "netpbm-10.35.80_2" port won't build. There is a notation that the > previous version has to be removed first. I saw something here a few > days ago regarding that problem. Is the recommended method to do a > "make deinstall && make reinstall" to get the updated port installed? I > know that portupgrade chocks on the port if a previous version is > installed. > .... As (I) documented in ports/156577, what worked for me was: pkg_delete -f netpbm-10.26.64_4 portmaster graphics/netpbm I subsequently heard from one person who reported that this did not work for him. For convenince: . Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --JQ29orswtRjjfiJM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk25hbsACgkQmprOCmdXAD3q4QCePAxwzqRhwf3fcefHwXxvxvDv z8kAnj/ygFgvdBqyk/6DK5X1gKfFSwMj =5zWg -----END PGP SIGNATURE----- --JQ29orswtRjjfiJM-- From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 18:04:32 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D13106566B for ; Thu, 28 Apr 2011 18:04:32 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [95.108.130.92]) by mx1.freebsd.org (Postfix) with ESMTP id 5FFC88FC08 for ; Thu, 28 Apr 2011 18:04:32 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward14.mail.yandex.net (Yandex) with ESMTP id 842881980D93; Thu, 28 Apr 2011 22:04:30 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1304013870; bh=aTp8eN7jOUe4arkJcOcQVR/A0QlzIRivyfuwL29QhA4=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:Content-Type; b=pBw6CbB4hjPRZ9vyjdGvCoAYhIYndx+xyd2umNjKai6dwmHyEggK0Cdzs4OclmMxD 5GAxXUpcslZHylLizABkMG2ede4SDviWq7m7NJQrkOsreuH1NKTpRS1X56eR0dkAEh QYWhIhZ54hZ8WhFwz9zUCDgXJRXloJWZFhapbVzs= Received: from smeshariki2.local (unknown [178.76.212.172]) by smtp12.mail.yandex.net (Yandex) with ESMTPSA id 17F2F572802F; Thu, 28 Apr 2011 22:04:30 +0400 (MSD) Message-ID: <4DB9ABB5.4030309@yandex.ru> Date: Thu, 28 Apr 2011 22:02:29 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.15) Gecko/20110425 Thunderbird/3.1.9 MIME-Version: 1.0 To: FreeBSD Ports Mailing List Content-Type: multipart/mixed; boundary="------------030709060003040601040009" X-Yandex-Spam: 1 Cc: "Todd J." Subject: Fwd: [todd@packetstormsecurity.org: update for freebsd ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:04:33 -0000 This is a multi-part message in MIME format. --------------030709060003040601040009 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit As far i understand original Todd's message to ports@ is in moderation stage, so i forward his (forwarded) message by myself. Tomorrow i faced with the fact that packetstormsecurity.nl that goes first in our MASTER_SITE_PACKETSTORM isn't avalaible, so i request packetstorm people about it's status. So we should patch our bsd.sites.mk to actualize mirror list. dl.packetstormsecurity.net (main file archive) goes first. Patch attached. Please commit. -------- Исходное сообщение -------- Тема: [todd@packetstormsecurity.org: update for freebsd ports] Дата: Thu, 28 Apr 2011 17:07:06 +0000 От: Todd J. Кому: cvs-src@yandex.ru fyi ----- Forwarded message from "Todd J." ----- Return-Path: todd@packetstormsecurity.org X-Original-To: staff@packetstormsecurity.org Delivered-To: staff@packetstormsecurity.org Received: by packetstormsecurity.org (Postfix, from userid 1013) id 95D0F23F4019; Thu, 28 Apr 2011 16:27:33 +0000 (UTC) Date: Thu, 28 Apr 2011 16:27:33 +0000 From: "Todd J." To: ports@freebsd.org Subject: update for freebsd ports Message-ID: <20110428162733.GA6276@packetstormsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Status: RO Content-Length: 615 Lines: 13 Greetings ports team - It was brought to my attention that our Packet Storm mirrors are leveraged for building certain packages in the ports collection (and your list of mirrors is now out of date). http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.sites.mk?rev=1.536;content-type=text%2Fplain They're under MASTER_SITE_PACKETSTORM. These mirrors come and go over time, so it's probably best to leverage the main site directly for this data ( http://dl.packetstormsecurity.net/%SUBDIR%/ ) or alternatively, the updated list of mirrors is kept here: http://packetstormsecurity.org/mirrors/ Thanks, Todd ----- End forwarded message ----- --------------030709060003040601040009 Content-Type: text/plain; name="bsd.sites.mk.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bsd.sites.mk.diff" LS0tIGJzZC5zaXRlcy5tay5vcmlnCTIwMTEtMDQtMjggMTU6NDA6NTQuMDAwMDAwMDAwICsw NDAwCisrKyBic2Quc2l0ZXMubWsJMjAxMS0wNC0yOCAyMTo1NzowMC4wMDAwMDAwMDAgKzA0 MDAKQEAgLTkxNSwxOCArOTE1LDE2IEBACiAKIC5pZiAhZGVmaW5lZChJR05PUkVfTUFTVEVS X1NJVEVfUEFDS0VUU1RPUk0pCiBNQVNURVJfU0lURV9QQUNLRVRTVE9STSs9IFwKLQlodHRw Oi8vcGFja2V0c3Rvcm1zZWN1cml0eS5ubC8lU1VCRElSJS8gXAotCWh0dHA6Ly9wYWNrZXRz dG9ybS5saW51eHNlY3VyaXR5LmNvbS8lU1VCRElSJS8gXAotCWh0dHA6Ly9wYWNrZXRzdG9y bS5zZXRuaW5lLmNvbS8lU1VCRElSJS8gXAorCWh0dHA6Ly9kbC5wYWNrZXRzdG9ybXNlY3Vy aXR5Lm5ldC8lU1VCRElSJS8gXAogCWh0dHA6Ly9wYWNrZXRzdG9ybS5hdXN0aW4yNjAwLm5l dC8lU1VCRElSJS8gXAotCWh0dHA6Ly9wYWNrZXRzdG9ybS5mb29mdXMuY29tLyVTVUJESVIl LyBcCiAJaHR0cDovL3BhY2tldHN0b3JtLmNvZGFyLmNvbS5ici8lU1VCRElSJS8gXAotCWh0 dHA6Ly9wYWNrZXRzdG9ybS5ybHouY2wvJVNVQkRJUiUvIFwKLQlodHRwOi8vcGFja2V0c3Rv cm0ud293aGFja2VyLmNvbS8lU1VCRElSJS8gXAotCWh0dHA6Ly9wYWNrZXRzdG9ybS5vZmZl bnNpdmUtc2VjdXJpdHkuY29tLyVTVUJESVIlLyBcCisJaHR0cDovL3BhY2tldHN0b3JtLmNy YXp5ZG9nLnB0LyVTVUJESVIlLyBcCiAJaHR0cDovL3BhY2tldHN0b3JtLmlnb3Iub25saW5l ZGlyZWN0LmJnLyVTVUJESVIlLyBcCisJaHR0cDovL3BhY2tldHN0b3JtLmludGVyaG9zdC5j by5pbC8lU1VCRElSJS8gXAorCWh0dHA6Ly9wYWNrZXRzdG9ybS5mb29mdXMuY29tLyVTVUJE SVIlLyBcCisJaHR0cDovL3BhY2tldHN0b3JtLmxpbnV4c2VjdXJpdHkuY29tLyVTVUJESVIl LyBcCiAJaHR0cDovL3BhY2tldHN0b3JtLnVuaXh0ZWFjaGVyLm9yZy8lU1VCRElSJS8gXAot CWh0dHA6Ly9wYWNrZXRzdG9ybS5vcmlvbi1ob3N0aW5nLmNvLnVrLyVTVUJESVIlLworCWh0 dHA6Ly9wYWNrZXRzdG9ybS53b3doYWNrZXIuY29tLyVTVUJESVIlLwogLmVuZGlmCiAKIC5p ZiAhZGVmaW5lZChJR05PUkVfTUFTVEVSX1NJVEVfUEVSTF9DUEFOKQo= --------------030709060003040601040009-- From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 18:52:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id A1837106566B for ; Thu, 28 Apr 2011 18:52:38 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (unknown [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 09E3325ADB2 for ; Thu, 28 Apr 2011 16:05:22 +0200 (CEST) Message-ID: <4DB97422.5090102@FreeBSD.org> Date: Thu, 28 Apr 2011 16:05:22 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Mnenhy/0.8.3 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> In-Reply-To: <20110427192555.65add0de@seibercom.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:52:39 -0000 Am 28.04.2011 01:25, schrieb Jerry: > On Thu, 28 Apr 2011 00:54:45 +0200 > Olli Hauer articulated: > >> Maybe you have some time to spend? > > Before I could reasonable be expected to set aside time, I would need a > detailed job description, etcetera. Perhaps you can supply me with one? See, and that's what committers might think, too: 'before I do lots of paperwork, I get something else done.' Be that some PR filed by someone else than you, or reading a book rather than doing ports work. :-) Counting recreation into "something else" because it's also useful to make any headway sustainably. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 18:52:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id D35D61065674 for ; Thu, 28 Apr 2011 18:52:38 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (unknown [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 68BEE25AD7F for ; Thu, 28 Apr 2011 15:42:33 +0200 (CEST) Message-ID: <4DB96EC9.8000506@FreeBSD.org> Date: Thu, 28 Apr 2011 15:42:33 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Mnenhy/0.8.3 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> In-Reply-To: <20110427075436.70ae18ac@seibercom.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:52:39 -0000 Am 27.04.2011 13:54, schrieb Jerry: > Personally, I believe that the current system, if not partially broken, > is far from ideal. I would prefer to see a system where each submitted > PR is assigned a specific number (I believe it is actually) and then > assigned in numeric order to the next available committer. That > committer would then be responsible for either committing the > PR/Port/Whatever within a preset time frame, or informing the original > submitter why the said article was not/could not be approved at the > present time. Allowing a submitter to languish while pondering what has > become of their document certainly does seem justified. Greetings, I know from the times when I wasn't a committer that it was sometimes frustrating if PRs were lingering for weeks. Your idea of assigning ports to committers rests upon the assumption that all port/update submissions were equal with respect to the sub-tasks to be performed by a committer, and/or the required skills. I for one am not knowledgeable about Ada or the related build systems such as GNAT ports, so I'd not usually pick up such a PR - Robert Huff mentioned something similar yesterday. Then there are many more non-trivial commits, with downstream dependencies, or dangerous to other ports, and these require more thorough testing, building downstream ports, possibly an experimental build of ALL ports, the so-called -exp run, documenting updating requirements and so on. These take time, and I've recently returned a port which, thankfully, mentioned "-exp run advised" or similar, that I couldn't tend to due to vacation, lack of time for holiday preparations, never having requested an -exp run before IOW I'd need to get acquainted with the procedures, and all that. > I am sure that the old, "But they are all volunteers", or some such > tirade will erupt. It must be remembered that those who submit items for > approval are also volunteers. They deserve at least as much respect as > those who are actively working on those submitted items. True enough, but I think that committers are not disrespectful. I know that intent and feeling are different matters. I agree that transparency of the "why hasn't my PR been addressed" would be desirable to maintainers, but I don't see a technical solution to that, meaning that it requires manual action by committers. One idea might be to team up maintainers with committers somehow (I don't know how yet), so some kind of who-is-who list that Robert mentioned, might be useful. Providing it's up to date. But it requires setting up and maintenance, too. Again, I don't believe this kind of neglect is deliberate, as frustrating though it may be. Yes, we committers can do better, and it seems we're in some kind of unfreezing before a non-trivial change, and that thinking and talking about *how* to change our procedures has started and looks promising IMHO, and I've also skimmed Charlie-Hester's-stepping-down thread with pity (although I believe some misunderstanding, possibly across language boundaries, on both sides was a major part of that problem) It all will require some work before we will have changed though, procedural changes don't happen in a few days. Not with 20000+ ports and established policies and procedures behind us anyways. So if we can abstract away from the frustration of individual ports not getting addressed to ideas HOW we can PRACTICALLY improve, we may actually achieve that desired improvement. I hope you can bear with us while we ponder the required changes. Best Matthias From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 18:52:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 490741065675 for ; Thu, 28 Apr 2011 18:52:39 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (unknown [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 9144B25ADB1 for ; Thu, 28 Apr 2011 15:58:33 +0200 (CEST) Message-ID: <4DB97289.3080208@FreeBSD.org> Date: Thu, 28 Apr 2011 15:58:33 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Mnenhy/0.8.3 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB8664D.70001@marino.st> <20110427221813.GB32138@owl.midgard.homeip.net> <4DB89B38.4000404@marino.st> In-Reply-To: <4DB89B38.4000404@marino.st> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:52:39 -0000 Am 28.04.2011 00:39, schrieb John Marino: > I was working the assumption that he agrees to the port up front or > voluntarily picks up the next task. However, if someone has a repeated > history of refusals or only wants to do a very narrow set of tasks, then > maybe commit bit removal isn't that dramatic. It will leave one frustrated committer who will likely turn his back to the project and leave altogether, and, that point was made before, leave his work undone -- and that means BOTH the work he didn't pick that you wanted to punish for, and the work he did do. And redistributing the latter is painful for all others. Given that committers aren't likely to inflict pain to themselves, such a system isn't going to be established. Let's for the sake of the argument assume that committers are neither deliberately brushing maintainers off, nor ignoring/neglecting them, nor bored. If you work with volunteers, you need incentive, not repression or threat. Robert suggested a who's who of committers, which might be helpful for some auto-assignment after a week or two. I for one am not against such auto-assignments, and I believe that there's some overhead in the status quo that causes this to NOT happen. Teaming up maintainers for a set of ports means setting up aliases or lists. Teaming up committers for a set of ports either happens through projects such as KDE or GNOME, or not at all. I for one am also open for teaming up and getting some ports in my areas of expertise auto-assigned to me, but I am not actively looking for them. Let's think a bit more about Robert's who's who list, what it could be used for (technical auto-assignment after timeouts, or a mere contacts list for maintainers were mentioned), and about incentive for committers. The cheapest incentive would be to make some process easier. Now, what to we want to make easier? For committers? For maintainers? How can we keep maintainers in a good mood and motivated even if their submissions linger for longer than they feel fair? From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 18:57:10 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E68EF106566B for ; Thu, 28 Apr 2011 18:57:10 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (sludge.pil.dk [195.41.47.48]) by mx1.freebsd.org (Postfix) with ESMTP id 715DF8FC15 for ; Thu, 28 Apr 2011 18:57:10 +0000 (UTC) Received: by mail.droso.net (Postfix, from userid 1001) id 90AFAC00; Thu, 28 Apr 2011 20:57:09 +0200 (CEST) Date: Thu, 28 Apr 2011 20:57:09 +0200 From: Erwin Lansing To: Ruslan Mahmatkhanov Message-ID: <20110428185709.GA52363@droso.net> References: <4DB9ABB5.4030309@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AzNpbZlgThVzWita" Content-Disposition: inline In-Reply-To: <4DB9ABB5.4030309@yandex.ru> X-Operating-System: FreeBSD/amd64 8.2-RELEASE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Ports Mailing List , "Todd J." Subject: Re: Fwd: [todd@packetstormsecurity.org: update for freebsd ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:57:11 -0000 --AzNpbZlgThVzWita Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 28, 2011 at 10:02:29PM +0400, Ruslan Mahmatkhanov wrote: Hi Ruslan, Todd, > As far i understand original Todd's message to ports@ is in moderation st= age, so=20 > i forward his (forwarded) message by myself. Tomorrow i faced with the fa= ct that=20 > packetstormsecurity.nl that goes first in our MASTER_SITE_PACKETSTORM isn= 't=20 > avalaible, so i request packetstorm people about it's status. So we shoul= d patch=20 > our bsd.sites.mk to actualize mirror list. dl.packetstormsecurity.net (ma= in file=20 > archive) goes first. Patch attached. Please commit. Thanks for bringing this to our attention and thanks for providing the patch as well. I've committed the update. Thanks again, -erwin >=20 > -------- ???????????????? ?????????????????? -------- > ????????: [todd@packetstormsecurity.org: update for freebsd ports] > ????????: Thu, 28 Apr 2011 17:07:06 +0000 > ????: Todd J. > ????????: cvs-src@yandex.ru >=20 > fyi >=20 > ----- Forwarded message from "Todd J." ---= -- >=20 > Return-Path: todd@packetstormsecurity.org > X-Original-To: staff@packetstormsecurity.org > Delivered-To: staff@packetstormsecurity.org > Received: by packetstormsecurity.org (Postfix, from userid 1013) > id 95D0F23F4019; Thu, 28 Apr 2011 16:27:33 +0000 (UTC) > Date: Thu, 28 Apr 2011 16:27:33 +0000 > From: "Todd J." > To: ports@freebsd.org > Subject: update for freebsd ports > Message-ID: <20110428162733.GA6276@packetstormsecurity.org> > MIME-Version: 1.0 > Content-Type: text/plain; charset=3Dus-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.17+20080114 (2008-01-14) > Status: RO > Content-Length: 615 > Lines: 13 >=20 > Greetings ports team - >=20 > It was brought to my attention that our Packet Storm mirrors are leverage= d for=20 > building certain packages in the ports collection (and your list of mirro= rs is=20 > now out of date). >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.sites.mk?rev=3D1.536;c= ontent-type=3Dtext%2Fplain=20 >=20 >=20 > They're under MASTER_SITE_PACKETSTORM. These mirrors come and go over ti= me, so=20 > it's probably best to leverage the main site directly for this data (=20 > http://dl.packetstormsecurity.net/%SUBDIR%/ ) or alternatively, the updat= ed list=20 > of mirrors is kept here: >=20 > http://packetstormsecurity.org/mirrors/ >=20 >=20 > Thanks, > Todd >=20 > ----- End forwarded message ----- >=20 >=20 > --- bsd.sites.mk.orig 2011-04-28 15:40:54.000000000 +0400 > +++ bsd.sites.mk 2011-04-28 21:57:00.000000000 +0400 > @@ -915,18 +915,16 @@ > =20 > .if !defined(IGNORE_MASTER_SITE_PACKETSTORM) > MASTER_SITE_PACKETSTORM+=3D \ > - http://packetstormsecurity.nl/%SUBDIR%/ \ > - http://packetstorm.linuxsecurity.com/%SUBDIR%/ \ > - http://packetstorm.setnine.com/%SUBDIR%/ \ > + http://dl.packetstormsecurity.net/%SUBDIR%/ \ > http://packetstorm.austin2600.net/%SUBDIR%/ \ > - http://packetstorm.foofus.com/%SUBDIR%/ \ > http://packetstorm.codar.com.br/%SUBDIR%/ \ > - http://packetstorm.rlz.cl/%SUBDIR%/ \ > - http://packetstorm.wowhacker.com/%SUBDIR%/ \ > - http://packetstorm.offensive-security.com/%SUBDIR%/ \ > + http://packetstorm.crazydog.pt/%SUBDIR%/ \ > http://packetstorm.igor.onlinedirect.bg/%SUBDIR%/ \ > + http://packetstorm.interhost.co.il/%SUBDIR%/ \ > + http://packetstorm.foofus.com/%SUBDIR%/ \ > + http://packetstorm.linuxsecurity.com/%SUBDIR%/ \ > http://packetstorm.unixteacher.org/%SUBDIR%/ \ > - http://packetstorm.orion-hosting.co.uk/%SUBDIR%/ > + http://packetstorm.wowhacker.com/%SUBDIR%/ > .endif > =20 > .if !defined(IGNORE_MASTER_SITE_PERL_CPAN) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" --=20 Erwin Lansing http://droso.org Prediction is very difficult especially about the future erwin@FreeBSD.org --AzNpbZlgThVzWita Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iD8DBQFNubiFqy9aWxUlaZARAqnkAJ48q7jxliiH7QLApC+XLVD0/9vMbgCgi3Fl KmmAI6SoV9TcVaSg22nxPGc= =LKCw -----END PGP SIGNATURE----- --AzNpbZlgThVzWita-- From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:06:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B6E106566C; Thu, 28 Apr 2011 19:06:56 +0000 (UTC) (envelope-from bmah@kitchenlab.org) Received: from kaga.kitchenlab.org (unknown [IPv6:2001:470:1f04:55c::2]) by mx1.freebsd.org (Postfix) with ESMTP id 160BF8FC0A; Thu, 28 Apr 2011 19:06:56 +0000 (UTC) Received: from morimoto.local ([IPv6:2001:470:1f05:888:21b:63ff:fecd:f07c]) (authenticated bits=0) by kaga.kitchenlab.org (8.14.4/8.14.4) with ESMTP id p3SJ6qbB031649 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 28 Apr 2011 12:06:53 -0700 (PDT) (envelope-from bmah@kitchenlab.org) Message-ID: <4DB9BACB.8060704@kitchenlab.org> Date: Thu, 28 Apr 2011 12:06:51 -0700 From: "Bruce A. Mah" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Brooks Davis References: <19CCC0EE-AAF8-401B-875F-F2A43E780642@huibsmeets.com> <1303913707221-4343776.post@n5.nabble.com> <20110427091959.GH43345@lor.one-eyed-alien.net> In-Reply-To: <20110427091959.GH43345@lor.one-eyed-alien.net> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig671D4A938A2E553683D3B3BA" X-Virus-Scanned: clamav-milter 0.96.5 at kaga.kitchenlab.org X-Virus-Status: Clean Cc: spotter , freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: squeezeboxserver-7.5.3, build okay but fails to start. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:06:56 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig671D4A938A2E553683D3B3BA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Brooks Davis wrote: > On Wed, Apr 27, 2011 at 07:15:07AM -0700, spotter wrote: >> I am having the exact same problem with a brand new FreeBSD 8.1-RELEAS= E >> install and a fresh squeezeboxserver (v7.5.3) port build. >> (Slimserver was working fine under FreeBSD 6.2, until I tried to get >> miniDLNA working, as well, for a BluRay player access to same music li= brary. >> sigh) >> Any solutions worked out for squeezeboxserver v7.5.3 under FreeBSD >> 8.1-RELEASE? >=20 > Assuming you aren't using mysql for anything else, you might try > manually installing an older version and then reinstalling the port. M= y > squeezeboxserver is running with 5.0. If that works we should be able > to restrict the allowed versions of mysql to ones that work. Just another data point: I have squeezeboxserver-7.5.3 running successfully with mysql-server-5.1.55 on FreeBSD 8.2-RELEASE/amd64. Thanks, Bruce. --------------enig671D4A938A2E553683D3B3BA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk25uswACgkQ2MoxcVugUsOXdgCePejprQkZRa70Zo7oiGKxA191 zjQAoI9ciOzqi6FwAI+yYOysivqhXdsu =vDSG -----END PGP SIGNATURE----- --------------enig671D4A938A2E553683D3B3BA-- From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:07:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2D9E1065678 for ; Thu, 28 Apr 2011 19:07:50 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id 95A208FC1E for ; Thu, 28 Apr 2011 19:07:50 +0000 (UTC) Received: from c-24-22-230-24.hsd1.wa.comcast.net ([24.22.230.24] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QFWZ1-0002GD-3Q for freebsd-ports@freebsd.org; Thu, 28 Apr 2011 15:07:48 -0400 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Thu, 28 Apr 2011 12:07:45 -0700 Date: Thu, 28 Apr 2011 12:07:45 -0700 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20110428190745.GE77343@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <4DB96EC9.8000506@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fWddYNRDgTk9wQGZ" Content-Disposition: inline In-Reply-To: <4DB96EC9.8000506@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:07:50 -0000 --fWddYNRDgTk9wQGZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Correct me if I'm wrong, but as I understand it committers have commit privilege for all ports. What if certain qualified port maintainers who aren't committers were nevertheless given commit access for only the leaf ports that they maintain? Wouldn't that speed up the overall process? --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --fWddYNRDgTk9wQGZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJNubsBAAoJEIpckszW26+RmeoH/imGlQmeoMoWvO3077WsJDH+ +aWj/KQ41twPX9N3OWdYlUko+5Vy9S19k8Up4lKA8//LPImD6W4bZCfgeeLajU0x lCrDwr2Yr0IcmpApKykZ6bC9Cili6Y2TrqwttpAGO+CRPTUwspE1NpdRQGzaSgYy RFTJDLPt7lP0o+pZ6AiiRcRpxPkg76vW+kOyxjAxGy//pTjsUUgkdM36HoK01qRd CpJJqQevFnKnlmBajtRgMEu26oDxYNTvwdcd01fusmnrXbyy22u5F2hypfnjKc7q RDxVn9JY6R/14dc0dk9bt0nak1oYnKgBxIFYI+56kIyKPh5jwkUdoThnV1L7Bts= =hin3 -----END PGP SIGNATURE----- --fWddYNRDgTk9wQGZ-- From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:23:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83DD0106566B for ; Thu, 28 Apr 2011 19:23:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 12C298FC08 for ; Thu, 28 Apr 2011 19:23:47 +0000 (UTC) Received: by wwc33 with SMTP id 33so3201771wwc.31 for ; Thu, 28 Apr 2011 12:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=pY0I7lnGP/OK10s/+TWK426oqdQAmq3fD9hm2k2AKE0=; b=ipeLsSVvodfCTyPK6TstfVUsq+XCO4+YhHcVgfJqpr+O9q0Ro0L+YAXK6hGkQCAUay dJXxIp1s78s2zRRV70vyB0MYlmlkSM0bhhjGZQipWy7JA4RNinEsPFy+r4xfnhQ5SFmi 54XwPcDhJLxLgLGw9tjS2SleLVroQ8dp3//Ac= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=OsSZurteB/6sUBU+mvSoTrBQHYMa/iiVNdHek6cmCmjqYNhAIuiJEF9nVe5zK5labE xIJdVnmwPUN+99vA3If04cLZYE85WUrkr9u7QmkwOdPlhcAWzEgO0oTJoYp0jhXAn69+ ivKWiJlQs69M8W654J3GXxq1BjtX0eSFg0tOg= MIME-Version: 1.0 Received: by 10.216.142.224 with SMTP id i74mr4321095wej.3.1304018626932; Thu, 28 Apr 2011 12:23:46 -0700 (PDT) Received: by 10.216.243.143 with HTTP; Thu, 28 Apr 2011 12:23:46 -0700 (PDT) Received: by 10.216.243.143 with HTTP; Thu, 28 Apr 2011 12:23:46 -0700 (PDT) In-Reply-To: <20110428190745.GE77343@libertas.local.camdensoftware.com> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <4DB96EC9.8000506@FreeBSD.org> <20110428190745.GE77343@libertas.local.camdensoftware.com> Date: Thu, 28 Apr 2011 20:23:46 +0100 Message-ID: From: Chris Rees To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:23:48 -0000 On 28 Apr 2011 20:08, "Chip Camden" wrote: > > Correct me if I'm wrong, but as I understand it committers have commit > privilege for all ports. What if certain qualified port maintainers who > aren't committers were nevertheless given commit access for only the leaf > ports that they maintain? Wouldn't that speed up the overall process? > Search the archives for an answer or ten. Chris From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:41:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5D30106566C for ; Thu, 28 Apr 2011 19:41:04 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 35CE58FC14 for ; Thu, 28 Apr 2011 19:41:03 +0000 (UTC) Received: by wwc33 with SMTP id 33so3218156wwc.31 for ; Thu, 28 Apr 2011 12:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=ikvTLuJ9Dhj+7h9crciN1mKVc9r2kWFkIiws6UjXCss=; b=qayj+PVWrCkAUGk6IfWC5L6XXezvKv/FF0cN5q1hUksjTvTSYQCSWN1gf9jKkwtQWQ eroyw8FpTQ77cC/AOSLumAmL5BjauUiMuytjD2SfVZzvepzYInJJKeIVROL390epKENG gBQ/wo6t8hwecGtY5e5TZqmTgdkhfV6ijBNEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding; b=JReQGfuYwx2RJwX+/Oan2WSWdXq8a8365X1LH+ER+4+36BFuKI4y0Tiw9BvGxjFecy j59Bc3QyNETlGvDXF4X56bP1C+Ecu+i0HKmoWtGthLq0EreUjt8ldzQ4qjG2eqNWbv07 056ivf0oBwcNxuqPzkkb9MqJi7NEeUxHkoQis= Received: by 10.217.7.71 with SMTP id z49mr8592790wes.33.1304019663095; Thu, 28 Apr 2011 12:41:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.243.143 with HTTP; Thu, 28 Apr 2011 12:40:33 -0700 (PDT) In-Reply-To: References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <4DB96EC9.8000506@FreeBSD.org> <20110428190745.GE77343@libertas.local.camdensoftware.com> From: Chris Rees Date: Thu, 28 Apr 2011 20:40:33 +0100 Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:41:04 -0000 On 28 April 2011 20:23, Chris Rees wrote: > > On 28 Apr 2011 20:08, "Chip Camden" wrote: >> >> Correct me if I'm wrong, but as I understand it committers have commit >> privilege for all ports. =A0What if certain qualified port maintainers w= ho >> aren't committers were nevertheless given commit access for only the lea= f >> ports that they maintain? =A0Wouldn't that speed up the overall process? >> > > Search the archives for an answer or ten. > Sorry for the terse response, touchscreen phones are horrible to email on. I've found one of the conversations I was thinking of [1] -- these often come up. It should probably be on some kind of FAQ list... Chris [1] http://www.mail-archive.com/freebsd-ports@freebsd.org/msg28399.html From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:42:42 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11FEE106564A for ; Thu, 28 Apr 2011 19:42:42 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [95.108.130.93]) by mx1.freebsd.org (Postfix) with ESMTP id A3DBE8FC0C for ; Thu, 28 Apr 2011 19:42:41 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward11.mail.yandex.net (Yandex) with ESMTP id C0BE0E82526; Thu, 28 Apr 2011 23:42:37 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1304019757; bh=v6NjxoUXEB/FjQMKyaPW9zswfWOi5PrSa6rn2sReDX0=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ZcKEpEg2xsIm73PVT9xlCIsgghlkTj5iqI5/9qsB8aTwhx1GjFltQe7IYuVJkNsRM ko/ZpFwqa3Yo/4FaPeDj1c/dIxqpH2IKX8UZ5/LcxQ8OJfLCBGSOn6ANSKe+PLolFq EQB2ZxlcQhjN2cXuowHB64o6mps9nG9XxjSlicTc= Received: from smeshariki2.local (unknown [178.76.212.172]) by smtp11.mail.yandex.net (Yandex) with ESMTPSA id 7334A4CC0033; Thu, 28 Apr 2011 23:42:37 +0400 (MSD) Message-ID: <4DB9C2B4.4070609@yandex.ru> Date: Thu, 28 Apr 2011 23:40:36 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.15) Gecko/20110425 Thunderbird/3.1.9 MIME-Version: 1.0 To: Erwin Lansing References: <4DB9ABB5.4030309@yandex.ru> <20110428185709.GA52363@droso.net> In-Reply-To: <20110428185709.GA52363@droso.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Yandex-Spam: 1 Cc: FreeBSD Ports Mailing List , "Todd J." Subject: Re: Fwd: [todd@packetstormsecurity.org: update for freebsd ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:42:42 -0000 28.04.2011 22:57, Erwin Lansing пишет: > On Thu, Apr 28, 2011 at 10:02:29PM +0400, Ruslan Mahmatkhanov wrote: > > Hi Ruslan, Todd, > >> As far i understand original Todd's message to ports@ is in moderation stage, so >> i forward his (forwarded) message by myself. Tomorrow i faced with the fact that >> packetstormsecurity.nl that goes first in our MASTER_SITE_PACKETSTORM isn't >> avalaible, so i request packetstorm people about it's status. So we should patch >> our bsd.sites.mk to actualize mirror list. dl.packetstormsecurity.net (main file >> archive) goes first. Patch attached. Please commit. > > Thanks for bringing this to our attention and thanks for providing the > patch as well. I've committed the update. > > Thanks again, > -erwin Thanks a lot. -- Regards, Ruslan From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 19:55:40 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 869121065670 for ; Thu, 28 Apr 2011 19:55:40 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3486D8FC14 for ; Thu, 28 Apr 2011 19:55:39 +0000 (UTC) Received: by gxk28 with SMTP id 28so1492492gxk.13 for ; Thu, 28 Apr 2011 12:55:39 -0700 (PDT) Received: by 10.236.72.226 with SMTP id t62mr4872304yhd.495.1304020539164; Thu, 28 Apr 2011 12:55:39 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id u74sm47963yha.54.2011.04.28.12.55.37 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Apr 2011 12:55:37 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QL8601qZ6z2CG4n for ; Thu, 28 Apr 2011 15:55:36 -0400 (EDT) Date: Thu, 28 Apr 2011 15:55:35 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110428155535.6cad9970@seibercom.net> In-Reply-To: <4DB97422.5090102@FreeBSD.org> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> <4DB97422.5090102@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 19:55:40 -0000 On Thu, 28 Apr 2011 16:05:22 +0200 Matthias Andree articulated: > Am 28.04.2011 01:25, schrieb Jerry: > > On Thu, 28 Apr 2011 00:54:45 +0200 > > Olli Hauer articulated: > > > >> Maybe you have some time to spend? > > > > Before I could reasonable be expected to set aside time, I would > > need a detailed job description, etcetera. Perhaps you can supply > > me with one? > > See, and that's what committers might think, too: 'before I do lots of > paperwork, I get something else done.' Be that some PR filed by > someone else than you, or reading a book rather than doing ports > work. :-) Counting recreation into "something else" because it's also > useful to make any headway sustainably. No disrespect meant; however, I just showed your response to two other individuals who both concurred with me that your reply is nonsensical. Would you please rewrite it in basic English using proper sentence structure. Perhaps we should start at the beginning. Do you know what a "Job Description" actually is? -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 20:10:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 63CB9106564A for ; Thu, 28 Apr 2011 20:10:28 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 297E81A92E7; Thu, 28 Apr 2011 20:10:26 +0000 (UTC) Message-ID: <4DB9C9B2.9040003@FreeBSD.org> Date: Thu, 28 Apr 2011 13:10:26 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> <4DB97422.5090102@FreeBSD.org> <20110428155535.6cad9970@seibercom.net> In-Reply-To: <20110428155535.6cad9970@seibercom.net> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jerry Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 20:10:28 -0000 Jerry, I realize that you care deeply about this topic, however IMO your last few posts are a little more vitriolic than we we usually like to see on the FreeBSD lists. (And yes, I'm sure your response would be that this is not how they were intended, so I'll save you time writing it.) You need to realize that the FIFO PR assignment idea is not going to happen. Given that it's not going to happen, you might want to reconsider whether or not continuing to post on the topic will be helpful. Meanwhile, I would like to request (on a personal level, I'm not in charge of anything) that you take 24 hours off and refrain from posting altogether. Then if you still feel strongly that you have something to say (keeping in mind paragraph 2 above) the hope would be that with a little time to cool off you can say it with less emotion. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 20:45:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id D4A8A1065670 for ; Thu, 28 Apr 2011 20:45:29 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (unknown [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 9B63F25AD7F for ; Thu, 28 Apr 2011 22:45:28 +0200 (CEST) Message-ID: <4DB9D1E8.50204@FreeBSD.org> Date: Thu, 28 Apr 2011 22:45:28 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Mnenhy/0.8.3 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> <4DB97422.5090102@FreeBSD.org> <20110428155535.6cad9970@seibercom.net> In-Reply-To: <20110428155535.6cad9970@seibercom.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 20:45:30 -0000 Am 28.04.2011 21:55, schrieb Jerry: > On Thu, 28 Apr 2011 16:05:22 +0200 > Matthias Andree articulated: > >> Am 28.04.2011 01:25, schrieb Jerry: >>> On Thu, 28 Apr 2011 00:54:45 +0200 >>> Olli Hauer articulated: >>> >>>> Maybe you have some time to spend? >>> >>> Before I could reasonable be expected to set aside time, I would >>> need a detailed job description, etcetera. Perhaps you can supply >>> me with one? >> >> See, and that's what committers might think, too: 'before I do lots of >> paperwork, I get something else done.' Be that some PR filed by >> someone else than you, or reading a book rather than doing ports >> work. :-) Counting recreation into "something else" because it's also >> useful to make any headway sustainably. > > No disrespect meant; however, I just showed your response to two other > individuals who both concurred with me that your reply is nonsensical. > Would you please rewrite it in basic English using proper sentence > structure. Perhaps we should start at the beginning. Do you know what a > "Job Description" > actually is? Neither did I mean disrespect. What I'm saying is: You expect a job description before committing more of your time and working power to volunteer work on FreeBSD ports. However, for a FreeBSD committer, I can fancy not all of them are interested in something that gets too formal -- which would be a consequence of PR FIFO assignments or similar. Their idea is to care about some set of ports they are interested in, have a need in, and also have some expertise on. A clear job description with strict "fail to respond on stuff you hardly know and have no interest in X times in Y weeks and get all other work privileges removed" is what I alluded to when writing "paperwork". Personally, I would rather want to contribute to something where I can just work on some of the ports, rather than having someone else assign me PRs. I am fully aware that we cannot *guarantee* any service level this way. And I've myself been in situations when I had to accept that committers (or packagers for other projects) priorize (prioritize?, anyways, rank in their ordering of the tasks) my PR different than I'd hoped for. I may have found that unfair, but talking about starting at the beginning, not everybody's idea of "fair" will be the same. :-) Now I fail to see what incentive you'll provide to committers so that they actually adhere to an external PR assignment. While I'm only speaking on my behalf through the whole discussion, I read between other people's lines that I'm not alone with this opinion. I hope that is clearer now. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 20:52:33 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 13DA11065674 for ; Thu, 28 Apr 2011 20:52:33 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (unknown [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 1B38525AD7F for ; Thu, 28 Apr 2011 22:52:32 +0200 (CEST) Message-ID: <4DB9D390.2090102@FreeBSD.org> Date: Thu, 28 Apr 2011 22:52:32 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Mnenhy/0.8.3 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <4DB96EC9.8000506@FreeBSD.org> <20110428190745.GE77343@libertas.local.camdensoftware.com> In-Reply-To: <20110428190745.GE77343@libertas.local.camdensoftware.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 20:52:33 -0000 Am 28.04.2011 21:07, schrieb Chip Camden: > Correct me if I'm wrong, but as I understand it committers have commit > privilege for all ports. What if certain qualified port maintainers who > aren't committers were nevertheless given commit access for only the leaf > ports that they maintain? Wouldn't that speed up the overall process? It looks like you're asking for a technical solution to a non-technical problem. Chris Rees has posted an archive link, and my take is that we're already trying to ask such "qualified port maintainers" to become ports committers and not care too much about how fine-grained ports access is. From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 21:41:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E92511065680; Thu, 28 Apr 2011 21:41:25 +0000 (UTC) (envelope-from prvs=092be6323=pschmehl_lists@tx.rr.com) Received: from ip-001.utdallas.edu (ip-001.utdallas.edu [129.110.20.107]) by mx1.freebsd.org (Postfix) with ESMTP id AB2668FC13; Thu, 28 Apr 2011 21:41:25 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au0JAFXXuU2BbgogSmdsb2JhbACmEAEBIAIkiRW9U4V2BIYJlno X-IronPort-AV: E=Sophos;i="4.64,283,1301893200"; d="scan'208";a="59459610" Received: from zxtm01.utdallas.edu (HELO [129.110.200.11]) ([129.110.10.32]) by ip-001.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Apr 2011 16:12:13 -0500 Date: Thu, 28 Apr 2011 16:12:12 -0500 From: Paul Schmehl To: Matthias Andree , freebsd-ports@freebsd.org Message-ID: In-Reply-To: <4DB9D390.2090102@FreeBSD.org> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <4DB96EC9.8000506@FreeBSD.org> <20110428190745.GE77343@libertas.local.camdensoftware.com> <4DB9D390.2090102@FreeBSD.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 21:41:26 -0000 --On April 28, 2011 10:52:32 PM +0200 Matthias Andree wrote: > Am 28.04.2011 21:07, schrieb Chip Camden: >> Correct me if I'm wrong, but as I understand it committers have commit >> privilege for all ports. What if certain qualified port maintainers who >> aren't committers were nevertheless given commit access for only the leaf >> ports that they maintain? Wouldn't that speed up the overall process? > > It looks like you're asking for a technical solution to a non-technical > problem. Chris Rees has posted an archive link, and my take is that > we're already trying to ask such "qualified port maintainers" to become > ports committers and not care too much about how fine-grained ports > access is. > I personally think it's a bad idea for a port maintainer to be the committer for their own ports. Getting even minor changes committed to the tree should require two independent sets of eyes. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell From owner-freebsd-ports@FreeBSD.ORG Thu Apr 28 23:53:46 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F134106566B for ; Thu, 28 Apr 2011 23:53:46 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 125958FC15 for ; Thu, 28 Apr 2011 23:53:45 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 6117656161; Thu, 28 Apr 2011 18:53:45 -0500 (CDT) Date: Thu, 28 Apr 2011 18:53:45 -0500 From: Mark Linimon To: Kurt Jaeger Message-ID: <20110428235345.GB9411@lonesome.com> References: <20110427014343.GJ38579@comcast.net> <20110427060917.GB73524@comcast.net> <4DB7B75C.7080902@marino.st> <20110427071543.GD73524@comcast.net> <20110427074958.GA28824@owl.midgard.homeip.net> <20110427082323.GI34314@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110427082323.GI34314@home.opsec.eu> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-ports@freebsd.org Subject: Re: Dropping maintainership of my ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 23:53:46 -0000 On Wed, Apr 27, 2011 at 10:23:23AM +0200, Kurt Jaeger wrote: > Maybe, if maintainer can "somehow easily" become ports committer, > this hurdle might be lower ? This has been discussed before. The barrier to entry is currently set at the "seems to be willing to work on FreeBSD over a period of many months, and a fair number of PRs." The problem with lowering it is that the Ports Collection is complex; new committers need to e.g. understand how a single port commit might affect other ports (e.g. broken INDEX), among many other things. Again, it's not a new idea; it's just that we have decided not to do it. mcl From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 00:16:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01013106564A for ; Fri, 29 Apr 2011 00:16:48 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id D5B488FC08 for ; Fri, 29 Apr 2011 00:16:47 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 90CC556161; Thu, 28 Apr 2011 19:16:47 -0500 (CDT) Date: Thu, 28 Apr 2011 19:16:47 -0500 From: Mark Linimon To: Jerry Message-ID: <20110429001647.GE9411@lonesome.com> References: <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> <4DB97422.5090102@FreeBSD.org> <20110428155535.6cad9970@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110428155535.6cad9970@seibercom.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 00:16:48 -0000 On Thu, Apr 28, 2011 at 03:55:35PM -0400, Jerry wrote: > Would you please rewrite it in basic English using proper sentence > structure. Please note: although the primary language of the project is English, probably less than half of FreeBSD committers are native Enligsh speakers. See ports/xearth/files/freebsd.committers.markers. mcl From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 01:55:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE46A1065670 for ; Fri, 29 Apr 2011 01:55:51 +0000 (UTC) (envelope-from nzp@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [204.13.164.18]) by mx1.freebsd.org (Postfix) with ESMTP id C45748FC16 for ; Fri, 29 Apr 2011 01:55:51 +0000 (UTC) Received: from spoonbill.riseup.net (spoonbill-pn.riseup.net [10.0.1.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 60099191089 for ; Thu, 28 Apr 2011 18:37:56 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: nzp@spoonbill.riseup.net) with ESMTPSA id 3E42C9F6C Date: Fri, 29 Apr 2011 03:37:53 +0200 From: Nikola =?utf-8?B?UGF2bG92acSH?= To: freebsd-ports@freebsd.org Message-ID: <20110429013753.GB7154@sputnjik.localdomain> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110428104912.1327aa49@seibercom.net> <20110428152028.GS1733@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110428152028.GS1733@albert.catwhisker.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.97 at mx1 X-Virus-Status: Clean Subject: Re: netpbm-10.35.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 01:55:51 -0000 On Thu, Apr 28, 2011 at 08:20:28AM -0700, David Wolfskill wrote: > On Thu, Apr 28, 2011 at 10:49:12AM -0400, Jerry wrote: > > The "netpbm-10.35.80_2" port won't build. There is a notation that the > > previous version has to be removed first. I saw something here a few > > days ago regarding that problem. Is the recommended method to do a > > "make deinstall && make reinstall" to get the updated port installed? I > > know that portupgrade chocks on the port if a previous version is > > installed. > > .... > > As (I) documented in ports/156577, what worked for me was: > > pkg_delete -f netpbm-10.26.64_4 > portmaster graphics/netpbm > > I subsequently heard from one person who reported that this did not work > for him. > > For convenince: . > Yes, there was an error in the makefile. I had to leave the machine and didn't have time to investigate further, but it was fixed later that day[1][2], and the deinstall/install procedure worked fine after that. [1] [2] -- Hark ye, Clinker, you are a most notorious offender. You stand convicted of sickness, hunger, wretchedness, and want. -- Tobias Smollet From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 12:50:13 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from pointyhat.freebsd.org (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by hub.freebsd.org (Postfix) with ESMTP id 5CF3F1065674; Fri, 29 Apr 2011 12:50:13 +0000 (UTC) (envelope-from "") Received: from pointyhat.freebsd.org (localhost [127.0.0.1]) by pointyhat.freebsd.org (8.14.3/8.14.3) with ESMTP id p3TCoD2w025474; Fri, 29 Apr 2011 12:50:13 GMT Received: (from erwin@localhost) by pointyhat.freebsd.org (8.14.3/8.14.3/Submit) id p3TCoCwc025404; Fri, 29 Apr 2011 12:50:12 GMT Date: Fri, 29 Apr 2011 12:50:12 GMT Message-Id: <201104291250.p3TCoCwc025404@pointyhat.freebsd.org> X-Authentication-Warning: pointyhat.freebsd.org: erwin set sender to <> using -f From: erwin@FreeBSD.org To: erwin@FreeBSD.org X-FreeBSD-Chkversion: PKGORIGIN Cc: ports@FreeBSD.org, sylvio@FreeBSD.org, pgollucci@FreeBSD.org, erwin@FreeBSD.org, tabthorpe@FreeBSD.org Subject: Ports with a broken PKGORIGIN: chinese/joe, security/p5-Auth-Yu... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: erwin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 12:50:13 -0000 ** The following ports have an incorrect PKGORIGIN ** PKGORIGIN connects packaged or installed ports to the directory they originated from. This is essential for tools like pkg_version or portupgrade to work correctly. Wrong PKGORIGINs are often caused by a wrong order of CATEGORIES after a repocopy. Please fix any errors as soon as possible. The ports tree was updated at Fri Apr 29 2011 12:00:22 UTC. - *chinese/joe* : editors/joe | revision 1.27 | date: 2010/10/28 21:00:07; author: erwin; state: Exp; lines: +1 -1 | Deprecate md5 in favour of sha256 checksums. md5 checksums will no longer | be generated or checked, and will be silently ignored for now. Also, | generalize the MD5_FILE macro to DISTINFO_FILO. | | PR: 149657 | Submitted by: rene | Approved by: portmgr | Tested on: pointyhat i386 7-exp (master: editors/joe) | revision 1.32 | date: 2010/12/29 20:04:18; author: pgollucci; state: Exp; lines: +0 -1 | - DISTNAME= ${PORTNAME}-${PORTVERSION} is the default and not needed. | | PR: ports/153292 | Submitted by: myself (pgollucci) | Tested by: -exp run by pav | Approved by: portmgr (pav) - *security/p5-Auth-YubikeyDecrypter* : perl5/p5-Auth-YubikeyDecrypter | revision 1.2 | date: 2011/04/28 20:26:29; author: tabthorpe; state: Exp; lines: +1 -1 | - Reset maintainer due to email bounces | | Final-Recipient: rfc822; fbsd-ports@opsec.eu | Original-Recipient: rfc822;fbsd-ports@opsec.eu | Action: failed | Status: 5.0.0 | Remote-MTA: dns; home.opsec.eu | Diagnostic-Code: smtp; 550 Unrouteable address | | Submitted by: erwin | With hat: portmgr From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 14:50:27 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D9DD1065679 for ; Fri, 29 Apr 2011 14:50:27 +0000 (UTC) (envelope-from sjk4015@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4FAC38FC14 for ; Fri, 29 Apr 2011 14:50:26 +0000 (UTC) Received: by pvg11 with SMTP id 11so3064257pvg.13 for ; Fri, 29 Apr 2011 07:50:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=tsUIol2oeQAmjimjqtLrlSCFxbfXjNekT8vGRfWOhYM=; b=aFvGQUByGOnw40a1nQyKjeB19TD435xxgdFJu1KVAwxnK/7uUpUtFFeKSZAxGm1mqu c2XNIYf3mNZ7720ZnE0IBZULGXw126gJqWpx+32usGxdiq5rwfIcCH5F8rUH4BFSXJXf I8l42V5GdI2a/mQ8kFXqi4RHvZ+JU9MOuCEgA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=BYdZoBIkISq0Jw5uIvOBvRNT+e+fMMz60j/NAXUSpykArpW5bdARqopZZpTumUoqAb RuVSI9SZO83/6QgXxFMth6pCFfyH+OLCZj1vYn9ahN8PnVQzo8GJt+xl+/WN8y454T+n W8iR6GBehI4qoDvYx7SQxUjcwFZouKvNz2vlM= MIME-Version: 1.0 Received: by 10.68.41.129 with SMTP id f1mr1361372pbl.74.1304087212534; Fri, 29 Apr 2011 07:26:52 -0700 (PDT) Sender: sjk4015@gmail.com Received: by 10.68.54.42 with HTTP; Fri, 29 Apr 2011 07:26:52 -0700 (PDT) In-Reply-To: <201104291250.p3TCoCwc025404@pointyhat.freebsd.org> References: <201104291250.p3TCoCwc025404@pointyhat.freebsd.org> Date: Fri, 29 Apr 2011 10:26:52 -0400 X-Google-Sender-Auth: BPdMfuM_svSu92GRg5RSxp5dDRM Message-ID: From: Steven Kreuzer To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Ports with a broken PKGORIGIN: chinese/joe, security/p5-Auth-Yu... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 14:50:27 -0000 I took care of security/p5-Auth-YubikeyDecrypter On Fri, Apr 29, 2011 at 8:50 AM, wrote: > ** The following ports have an incorrect PKGORIGIN ** > > =A0PKGORIGIN connects packaged or installed ports to the directory they > =A0originated from. This is essential for tools like pkg_version or > =A0portupgrade to work correctly. Wrong PKGORIGINs are often caused by a > =A0wrong order of CATEGORIES after a repocopy. > > =A0Please fix any errors as soon as possible. > > =A0The ports tree was updated at Fri Apr 29 2011 12:00:22 UTC. > > - *chinese/joe* : editors/joe > =A0 | revision 1.27 > =A0 | date: 2010/10/28 21:00:07; =A0author: erwin; =A0state: Exp; =A0line= s: +1 -1 > =A0 | Deprecate md5 in favour of sha256 checksums. =A0md5 checksums will = no longer > =A0 | be generated or checked, and will be silently ignored for now. =A0A= lso, > =A0 | generalize the MD5_FILE macro to DISTINFO_FILO. > =A0 | > =A0 | PR: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0149657 > =A0 | Submitted by: =A0 =A0 =A0rene > =A0 | Approved by: =A0 =A0 =A0 portmgr > =A0 | Tested on: pointyhat i386 7-exp > =A0(master: editors/joe) > =A0 | revision 1.32 > =A0 | date: 2010/12/29 20:04:18; =A0author: pgollucci; =A0state: Exp; =A0= lines: +0 -1 > =A0 | - DISTNAME=3D ${PORTNAME}-${PORTVERSION} is the default and not nee= ded. > =A0 | > =A0 | PR: =A0 =A0 =A0 =A0 =A0 =A0 ports/153292 > =A0 | Submitted by: =A0 myself (pgollucci) > =A0 | Tested by: =A0 =A0 =A0-exp run by pav > =A0 | Approved by: =A0 =A0portmgr (pav) > > - *security/p5-Auth-YubikeyDecrypter* : perl5/p5-Auth-= YubikeyDecrypter > =A0 | revision 1.2 > =A0 | date: 2011/04/28 20:26:29; =A0author: tabthorpe; =A0state: Exp; =A0= lines: +1 -1 > =A0 | - Reset maintainer due to email bounces > =A0 | > =A0 | Final-Recipient: rfc822; fbsd-ports@opsec.eu > =A0 | Original-Recipient: rfc822;fbsd-ports@opsec.eu > =A0 | Action: failed > =A0 | Status: 5.0.0 > =A0 | Remote-MTA: dns; home.opsec.eu > =A0 | Diagnostic-Code: smtp; 550 Unrouteable address > =A0 | > =A0 | Submitted by: =A0 =A0 =A0erwin > =A0 | With hat: =A0portmgr > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 14:58:20 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EBB4106567E for ; Fri, 29 Apr 2011 14:58:20 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id C418C8FC19 for ; Fri, 29 Apr 2011 14:58:19 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QFp9A-000Cm0-9U for ports@freebsd.org; Fri, 29 Apr 2011 16:58:20 +0200 Date: Fri, 29 Apr 2011 16:58:20 +0200 From: Kurt Jaeger To: ports@freebsd.org Message-ID: <20110429145820.GL34314@home.opsec.eu> References: <201104291250.p3TCoCwc025404@pointyhat.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Subject: Re: Ports with a broken PKGORIGIN: chinese/joe, security/p5-Auth-Yu... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 14:58:20 -0000 Hi! > I took care of security/p5-Auth-YubikeyDecrypter Sorry, I had a temporary spam flood on the maintainer e-mail fbsd-ports@opsec.eu. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Fri Apr 29 23:27:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 93427106564A; Fri, 29 Apr 2011 23:27:24 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-emulation@FreeBSD.org Date: Fri, 29 Apr 2011 19:27:11 -0400 User-Agent: KMail/1.6.2 References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> In-Reply-To: <430fcb25aefc374bf256e45e3151de15@bluelife.at> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_Ql0uN0E9ZXdthKb" Message-Id: <201104291927.12924.jkim@FreeBSD.org> Cc: Bernhard Froehlich , freebsd-ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 23:27:25 -0000 --Boundary-00=_Ql0uN0E9ZXdthKb Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Friday 22 April 2011 07:01 am, Bernhard Froehlich wrote: > It's about two months since the last call for testers and a lot of > bugfixing has happened since then. Not all of the reported problems > were FreeBSD related which is a good indication that we're not too > far behind the stability of the other hosts. So let's get it one > once again. > > Last time I asked for some help and Baptiste Daroussin (bapt@) made > the classic mistake to respond. So all please welcome bapt to the > FreeBSD Vbox Team! > > This is also the first time that we provide FreeBSD binary > packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 > platform and have the DEBUG option enabled. If you use a STABLE > kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary > package but have to compile the kernel module port for your kernel > yourself. > (emulators/virtualbox-ose-kmod) For very long time, I had a serious performance/timer issues with VirtualBox where TSC is not constant and timecounter hardware is not TSC. Today, I finally found a workaround (please see the attached patch). With this patch, TSC frequency is quite reasonable now. Basically, we were using nano(up)time(9) and they were too expensive for VirtualBox timekeeping. I believe it is okay to use getnano(up)time(9) here because a) VirtualBox already assumes these calls do not return accurate time (unless high-res timer is available, i.e., Linux) and b) we already report timer granularity is equal to kern.hz via RTTimerGetSystemGranularity(). Any thoughts? Thanks for your hard work! Jung-uk Kim --Boundary-00=_Ql0uN0E9ZXdthKb Content-Type: text/plain; charset="iso-8859-1"; name="patch-src-VBox-Runtime-r0drv-freebsd-time-r0drv-freebsd.c" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch-src-VBox-Runtime-r0drv-freebsd-time-r0drv-freebsd.c" --- src/VBox/Runtime/r0drv/freebsd/time-r0drv-freebsd.c.orig 2011-04-21 06:31:45.000000000 -0400 +++ src/VBox/Runtime/r0drv/freebsd/time-r0drv-freebsd.c 2011-04-29 18:57:26.000000000 -0400 @@ -41,7 +41,7 @@ RTDECL(uint64_t) RTTimeNanoTS(void) { struct timespec tsp; - nanouptime(&tsp); + getnanouptime(&tsp); return tsp.tv_sec * UINT64_C(1000000000) + tsp.tv_nsec; } @@ -68,6 +68,6 @@ RTDECL(uint64_t) RTTimeSystemMilliTS(voi RTDECL(PRTTIMESPEC) RTTimeNow(PRTTIMESPEC pTime) { struct timespec tsp; - nanotime(&tsp); + getnanotime(&tsp); return RTTimeSpecSetTimespec(pTime, &tsp); } --Boundary-00=_Ql0uN0E9ZXdthKb-- From owner-freebsd-ports@FreeBSD.ORG Sat Apr 30 08:10:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAD4C106564A for ; Sat, 30 Apr 2011 08:10:01 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8D5288FC14 for ; Sat, 30 Apr 2011 08:10:01 +0000 (UTC) Received: by iyj12 with SMTP id 12so5039699iyj.13 for ; Sat, 30 Apr 2011 01:10:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tmmYfiIWwocwTcPXoG3i2E4IyM1Ik1lmQ+ZJpGDZNoA=; b=ei7+cy4s/SaCX+TVMnXdzhsALZB/i9nWBMF87gGIDbGbYJ0kDGZ3aAmg9BUgNHzXVB EHraDtPcA6dQ9VTOAlDAbm5NTiUw0mjkQxax/U3C8gIcA8u4OTlTzI2jnjzF6HEihybH EhQGtuDuN8+F3/IPSH6hHTyYNmE0AYY6Fzj/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rWpLYIcQ28YYGTiuXNiY7SoZesiLcAkfvSF2wr4BIkGi7tSGvPIGX3mrKhiUS+CJDF BlMMWMojWR8FFxXf18Cug7XgpEUARpOnd+0KZXlQxDtnZ3mvgdGH0duuKFjaViqPB7NW J1ORCKUQ/2NEYZMm27CfGtApjjIuz61W5E4ew= MIME-Version: 1.0 Received: by 10.42.29.201 with SMTP id s9mr733332icc.188.1304151000701; Sat, 30 Apr 2011 01:10:00 -0700 (PDT) Received: by 10.231.10.68 with HTTP; Sat, 30 Apr 2011 01:10:00 -0700 (PDT) In-Reply-To: References: Date: Sat, 30 Apr 2011 12:10:00 +0400 Message-ID: From: Pavel Timofeev To: Warren Block Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Olivier Duchateau , freebsd-ports@freebsd.org Subject: Re: xfce 4.8 upgrade errors X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 08:10:01 -0000 I just found this http://www.freebsd.org/cgi/query-pr.cgi?pr=3D156721 Maybe it helps me. I'll try it soon 2011/4/15 Pavel Timofeev : > Thanks. I have deleted this line. > > 15.04.2011 18:16 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82= =D0=B5=D0=BB=D1=8C "Warren Block" =D0=BD=D0=B0=D0=BF= =D0=B8=D1=81=D0=B0=D0=BB: > From owner-freebsd-ports@FreeBSD.ORG Sat Apr 30 12:49:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B220D106566C for ; Sat, 30 Apr 2011 12:49:45 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 41D438FC12 for ; Sat, 30 Apr 2011 12:49:44 +0000 (UTC) Received: by wwc33 with SMTP id 33so4580454wwc.31 for ; Sat, 30 Apr 2011 05:49:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ITjevIM7dN5gt/Ji2Mpo4ahE4E3MCSb/+ZxqNiw4OjA=; b=qhxx4BE6L2pIcBkotpWI6k5NhLmRS2Zqb6QC5JtM23/MFBAO/SNOOn7pcLKIbHBOLf lvx35GNjLGEMbfwUpiXm6pB4tW35hEMaph8w7w4LkMN9JyNp/8/Vq4xh18e/ri5ah2N2 BQpf2OoGZDGkk8psJ5JKyeBEYyYbgbNSVwI9w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=TOcuGav9M94dbAl4GbDz8XS1RDB5idQ9VIsF6MTXzZaaXdZnhugjTpp7LfNCKJhvIw JpRkWue6q32tL+9EPc6MnO0QZkOmiZHE7f1vMFwt5yKExKs6fgGjmDPhatTqkqyWreZI MEb7jHEGla43dT2cVxa50YOka1na/XxjXEluY= Received: by 10.227.196.140 with SMTP id eg12mr615290wbb.59.1304167784075; Sat, 30 Apr 2011 05:49:44 -0700 (PDT) Received: from Melon.malikania.fr (65.21.102-84.rev.gaoland.net [84.102.21.65]) by mx.google.com with ESMTPS id b20sm2255206wbb.16.2011.04.30.05.49.41 (version=SSLv3 cipher=OTHER); Sat, 30 Apr 2011 05:49:42 -0700 (PDT) Message-ID: <4DBC053C.1000102@gmail.com> Date: Sat, 30 Apr 2011 14:49:00 +0200 From: David Demelier User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> In-Reply-To: <430fcb25aefc374bf256e45e3151de15@bluelife.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Call for Testers: VirtualBox 4.0.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 12:49:45 -0000 On 22/04/2011 13:01, Bernhard Froehlich wrote: > It's about two months since the last call for testers and a lot of > bugfixing has happened since then. Not all of the reported problems were > FreeBSD related which is a good indication that we're not too far behind > the stability of the other hosts. So let's get it one once again. > > Last time I asked for some help and Baptiste Daroussin (bapt@) made the > classic mistake to respond. So all please welcome bapt to the FreeBSD > Vbox Team! > > This is also the first time that we provide FreeBSD binary packages. > They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 platform and > have the DEBUG option enabled. If you use a STABLE kernel you can use > the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary package but have to > compile the kernel module port for your kernel yourself. > (emulators/virtualbox-ose-kmod) > > PBIs for PC-BSD are currently worked on and will hopefully be available > in a few days. > > > What has happened since the last cft: > > - VirtualBox update to 4.0.6 > - phpvirtualbox updated to 4.0-5 > - VIMAGE support added > - vboxheadless startscript added > - vboxwebsrv rc startscript fixes > - Build fixed with LOCALBASE != PREFIX > - Documentation of USB configuration (see pkg-message or Wiki) > > > Thanks to all people that have contributed to that release and also > reported problems for the last cft. We really appreciate that! > > > Changes in the port: > http://svn.bluelife.at/index.cgi/blueports/log/emulators > > Changelog for 4.0.6: > http://www.virtualbox.org/wiki/Changelog > > FreeBSD specific configuration: > http://wiki.freebsd.org/VirtualBox > > Todo List: > http://wiki.freebsd.org/VirtualBox/ToDo > > > Ports: > http://home.bluelife.at/ports/virtualbox-cft-20110421.tar.gz > > > FreeBSD 8.2/amd64 packages: > virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz > virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz > virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz > > FreeBSD 8.2/i386 packages: > virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz > virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz > virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz > > FreeBSD 7.4/amd64 packages: > virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz > virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz > virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz > > FreeBSD 7.4/i386 packages: > virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz > virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz > virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz > > > Checksums: > SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-amd64.tbz) = > d7bdad02d2a04dd9dc3f12cc3ee002ce3bfc196b > SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-i386.tbz) = > e3023f5117fd15e918cba749d1ace2b7366bdc88 > SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-amd64.tbz) = > bd2785ac54e8363d217e35433d942ccae8bb7ffd > SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-i386.tbz) = > f6c437febf60828218cb42d7bfab8b536ecb7301 > SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz) = > 31bbe5ff1e8d9b14dbd64c5d1f964fb702efda9e > SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz) = > 019955d07293f25421a0ca49d67975c165ee3e85 > SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz) = > e56736714e01dbe693515ed89e239337c7df77d3 > SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz) = > 8f59294036b2f1ef407849f874139a80b6aabbcb > SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz) = > cc7e72fdcf0e2cd0bcd21bb152ffa8b1b1adcaae > SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz) = > be14e942cd2b426007b2d9a395cc65843340970d > SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz) = > d5be908e99f9dfc4f7a1efe1570b67ad2d6b8d27 > SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz) = > 2627acdb5ea9008bfa6ac6c2f452d6b883cfa40e > SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz) = > e846f4a94bf14d0a50d3deab0ae325da25e79448 > SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz) = > 68144054e11bebe21fcb2b19e99cb33cead6f25b > SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz) = > 7f08351028f18a3d76ed8c57aba525b11b47ee9a > SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz) = > 6e9bbfe0a2b19985b556e739f02f02a86ef873dd > > > Mirrors: > http://disasterarea.chruetertee.ch/virtualbox/4.0.6/ (master) > http://files.etoilebsd.net/vbox/4.0.6/ > > > Thanks and good luck, > Bernhard, on behalf of the FreeBSD Vbox Team > It works like a charm, please import it as emulators/virtualbox-ose update! Cheers, -- David Demelier From owner-freebsd-ports@FreeBSD.ORG Sat Apr 30 20:12:58 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0B03106566B; Sat, 30 Apr 2011 20:12:58 +0000 (UTC) (envelope-from barbara.xxx1975@libero.it) Received: from cp-out3.libero.it (cp-out3.libero.it [212.52.84.103]) by mx1.freebsd.org (Postfix) with ESMTP id 815688FC08; Sat, 30 Apr 2011 20:12:58 +0000 (UTC) X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A0B0203.4DBC6D49.0024,ss=1,re=0.000,fgs=0 X-libjamoibt: 1419 Received: from wmail36 (172.31.0.225) by cp-out3.libero.it (8.5.133) (authenticated as barbara.xxx1975@libero.it) id 4D7F478503C43F52; Sat, 30 Apr 2011 22:12:57 +0200 Message-ID: <26147693.832461304194377029.JavaMail.defaultUser@defaultHost> Date: Sat, 30 Apr 2011 22:12:57 +0200 (CEST) From: Barbara To: bug-followup@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain;charset="UTF-8" Content-Transfer-Encoding: 7bit X-SenderIP: 82.54.221.164 Cc: naddy@freebsd.org, freebsd-ports@freebsd.org Subject: Re: ports/156580: audio/vorbis-tools: optionally get rid of libkate dependency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Barbara List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 20:12:59 -0000 Note that the patch doesn't remove the dependency if someone doesn't want to!!! It just add an option yet offered from libkate authors! Just like many other ports! I think that most of the people having vorbis-tools installed don't even know what is libkate. And as I posted a fix for libkate (which is still missing the dependecy from python!!!) in pr 155280 about two months ago, and it seems that the maintainer is not active since *long* time, can someone please review/comment/commit that pr instead of just closing this one? From owner-freebsd-ports@FreeBSD.ORG Sat Apr 30 21:38:40 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 445411065677 for ; Sat, 30 Apr 2011 21:38:40 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id EF0898FC1C for ; Sat, 30 Apr 2011 21:38:39 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1QGHs5-0003Vg-Ah; Sat, 30 Apr 2011 22:38:37 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QGHs4-00063t-18; Sat, 30 Apr 2011 22:38:36 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4) with ESMTP id p3ULcZ9R031844; Sat, 30 Apr 2011 22:38:35 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4/Submit) id p3ULcZal031843; Sat, 30 Apr 2011 22:38:35 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Sat, 30 Apr 2011 22:38:35 +0100 From: Anton Shterenlikht To: Mark Linimon Message-ID: <20110430213835.GA31804@mech-cluster241.men.bris.ac.uk> References: <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> <20110427093258.3966cfd2@seibercom.net> <20110427134836.GA30085@owl.midgard.homeip.net> <20110427101257.414aaf8b@seibercom.net> <4DB89EB5.2010603@FreeBSD.org> <20110427192555.65add0de@seibercom.net> <4DB97422.5090102@FreeBSD.org> <20110428155535.6cad9970@seibercom.net> <20110429001647.GE9411@lonesome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110429001647.GE9411@lonesome.com> User-Agent: Mutt/1.4.2.3i Cc: Jerry , freebsd-ports@freebsd.org Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 21:38:40 -0000 On Thu, Apr 28, 2011 at 07:16:47PM -0500, Mark Linimon wrote: > On Thu, Apr 28, 2011 at 03:55:35PM -0400, Jerry wrote: > > Would you please rewrite it in basic English using proper sentence > > structure. > > Please note: although the primary language of the project is English, > probably less than half of FreeBSD committers are native Enligsh speakers. > See ports/xearth/files/freebsd.committers.markers. ports/astro/xearth/... Wow, that is cool! One problem with 23k ports is that a poor ignorant user (myself) sometimes doesn't know what is best for him/her. I was fretting about not having a native Google earth (I just don't like USE_LINUX=yes ports), yet here is another brilliant port. I just wonder why so few submitters on the list: BUZI> wc /usr/local/lib/X11/xearth/freebsd.* 335 2284 17912 /usr/local/lib/X11/xearth/freebsd.committers.markers 73 386 3484 /usr/local/lib/X11/xearth/freebsd.ftp.markers 14 78 594 /usr/local/lib/X11/xearth/freebsd.submitters.markers 422 2748 21990 total BUZI> Mark, many thanks for the hint. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423