Date: Tue, 24 Dec 2013 11:37:28 -0500 From: Jay Borkenhagen <jayb@braeburn.org> To: Fernando =?iso-8859-1?Q?Apestegu=EDa?= <fernando.apesteguia@gmail.com> Cc: Rodrigo Osorio <rodrigo@bebik.net>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: ports/181836 Message-ID: <21177.47176.506931.459000@oz.mt.att.com> In-Reply-To: <CAGwOe2Y6KA8L5LxOXXT3Uy9aUxJHdmJGtYH-ve-_e8ENTEgRYQ@mail.gmail.com> References: <21172.22770.819388.859953@oz.mt.att.com> <20131220153213.GD5264@oldfaithful.bebik.local> <21172.28558.226554.619243@oz.mt.att.com> <CAGwOe2Y6KA8L5LxOXXT3Uy9aUxJHdmJGtYH-ve-_e8ENTEgRYQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Still no activity that I can see.=20 Is this really the way the ports process is supposed to work, that even after a port's maintainer has put a fix in SVN we need to hope a committer notices it and takes action=3F Sorry for being ignorant of the process -- I was just really hoping to be able to do some end-of-year admin tasks with this fixed port, and that's looking less promising now... Thanks. =09=09=09=09=09=09Jay B. Fernando Apestegu=EDa writes: > El 20/12/2013 17:26, "Jay Borkenhagen" <jayb@braeburn.org> escribi=F3= : > > > > Thanks, Rodrigo (and Fernando as well). > > > > Have I come to the right place to find someone who can and will do= > > that kind of thing=3F >=20 > IMHO, freebsd-ports@ is the proper place. Let's see if some committe= r reads > your message. >=20 > > > > > > > > Rodrigo Osorio writes: > > > > > > Hi, > > > > > > Ask/harass someone to commit the patch and bump PORTREVISION ..= =2E > That's all. > > > > > > - regard > > > > > > On 20/12/13 09:49 -0500, Jay Borkenhagen wrote: > > > > Hi, > > > > > > > > It was suggested to me that I ask this question here. > > > > > > > > Per http://www.freebsd.org/cgi/query-pr.cgi=3Fpr=3D181836 > > > > > > > > An issue in the FreeBSD port of smartmontools was fixed on > > > > 21-November, yet an update containing that fix has not yet pr= opagated > > > > through the ports system. > > > > > > > > What needs to happen for an updated port to be distributed=3F= > > > > > > > > Thank you. > > > > > > > > Jay B. > > > > > > > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F > > > > 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" > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebs= d.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21177.47176.506931.459000>