patch for force fetch

I've noticed the following problem. If a distfile is updated by a distributor without renaming it (so that checksum and possibly size change), then more often than not the port build system would fail to fetch the distfile. An example: ... => SHA256 Checksum mismatch for eclipse/javax.servlet.js

Re: patch for force fetch

on 16/05/2011 10:02 Andriy Gapon said the following: > The following patch simply tries to remove the stale distfile before calling > fetch. Maybe there is a smarter way about this, like e.g. passing some option > to fetch. Sorry, that patch had incorrect syntax, here is a better patch: --- /usr

Re: patch for force fetch

On 16/05/2011 09:02, Andriy Gapon wrote: I've noticed the following problem. If a distfile is updated by a distributor without renaming it (so that checksum and possibly size change), then more often than not the port build system would fail to fetch the distfile. An example: ... => SHA256 Ch

Re: patch for force fetch

on 16/05/2011 11:14 David Demelier said the following: > On 16/05/2011 09:02, Andriy Gapon wrote: >> >> I've noticed the following problem. >> If a distfile is updated by a distributor without renaming it (so that >> checksum >> and possibly size change), then more often than not the port build sy

Re: Propose new macro: INSTALL_CONF

On 15 May 2011 23:59, Olli Hauer wrote: > On 2011-05-16 00:12, Chris Rees wrote: >> Is this the Right Thing though, or a hack around missing code? You've >> just hardcoded a mode in that people might not like. > > It is a hack to overcome the 444 mode and I used it only for some config files > >>

Re: patch for force fetch

On Mon, May 16, 2011 at 10:14:11AM +0200, David Demelier wrote: > On 16/05/2011 09:02, Andriy Gapon wrote: > > > >I've noticed the following problem. > >If a distfile is updated by a distributor without renaming it (so that > >checksum > >and possibly size change), then more often than not the por

Re: patch for force fetch

On 16/05/2011 10:41, Andriy Gapon wrote: on 16/05/2011 11:14 David Demelier said the following: On 16/05/2011 09:02, Andriy Gapon wrote: I've noticed the following problem. If a distfile is updated by a distributor without renaming it (so that checksum and possibly size change), then more ofte

Re: proper use of bsd.port.options.mk

On 16 May 2011 05:18, Warren Block wrote: > On Sun, 15 May 2011, Doug Barton wrote: > >> I'm confused (yeah, I know, nothing new about that). From >> ports/Mk/bsd.port.options.mk: >> >> # usage: >> # >> #       .include "bsd.port.options.mk" >> #       >> #       .include "bsd.port.pre.mk" >> #  

Current unassigned ports problem reports

(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 obsol

Clean up old PRs

There are several PRs that are years (literally) old. For example: o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make variable in some ports Maybe it is time that some of these extremely old PRs be put to rest. Perhaps

Re: Clean up old PRs

+1 2011/5/16 Jerry : > There are several PRs that are years (literally) old. For example: > > > o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make > variable in some ports > > Maybe it is time that some of these extremel

Re: Clean up old PRs

On 16/05/2011 13:02, Jerry wrote: > x - expired > This report is over 2 years old. If no one has bothered to fix it > by now, then in all probability no one will. I've had PRs committed after spending many years in the queue. Just because it's old doesn't mean it's pointless. Closing old

Re: Clean up old PRs

On 16 May 2011 13:03, "Jerry" wrote: > > There are several PRs that are years (literally) old. For example: > > > o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make variable in some ports > > Maybe it is time that some of

Re: patch for force fetch

On Mon, May 16, 2011 at 10:02:57AM +0300, Andriy Gapon wrote: > > I've noticed the following problem. > If a distfile is updated by a distributor without renaming it (so that > checksum > and possibly size change), then more often than not the port build system > would > fail to fetch the distfi

Re: Clean up old PRs

> From: Jerry > Date: Mon, 16 May 2011 08:02:07 -0400 > > There are several PRs that are years (literally) old. For example: > > > o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make > variable in some ports > > Maybe i

Re: Clean up old PRs

Matthew Seaman wrote: > On 16/05/2011 13:02, Jerry wrote: > > x - expired > > This report is over 2 years old. If no one has bothered to fix it > > by now, then in all probability no one will. > > I've had PRs committed after spending many years in the queue. Just > because it's old doesn

Re: patch for force fetch

On Mon, 16 May 2011 04:00:17 -0500, Peter Pentchev wrote: 4. Upstream makes a change without bumping the version. Please make sure when this happens you give upstream a piece of your mind. This is unacceptable anywhere. If the end product changes it is wholly irresponsible and downright

Re: patch for force fetch

On Mon, May 16, 2011 at 08:08:07AM -0400 I heard the voice of Diane Bruce, and lo! it spake thus: > > I've run into this myself and simply done the manual rm -f. This > looks like a great addition. Note that there _is_ an existing 'distclean' target that cleans work/ as well as rm'ing the distfil

Re: Clean up old PRs

> I am proposing a new one: > > x - expired >    This report is over 2 years old. If no one has bothered to fix it >    by now, then in all probability no one will. I am very against this proposal. Some bugs have persisted for over a decade, but are still problems (see bin/1375 for an example). As

Re: patch for force fetch

> I've run into this myself and simply done the manual rm -f. This looks like > a great addition. what about make distclean ? -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscr

Re: proper use of bsd.port.options.mk

On 5/16/2011 3:23 AM, Chris Rees wrote: On 16 May 2011 05:18, Warren Block wrote: On Sun, 15 May 2011, Doug Barton wrote: I'm confused (yeah, I know, nothing new about that). From ports/Mk/bsd.port.options.mk: # usage: # # .include "bsd.port.options.mk" # # .include "bsd.port.pre

Re: proper use of bsd.port.options.mk

On 16 May 2011 18:23, Doug Barton wrote: > On 5/16/2011 3:23 AM, Chris Rees wrote: >> >> On 16 May 2011 05:18, Warren Block  wrote: >>> >>> On Sun, 15 May 2011, Doug Barton wrote: >>> I'm confused (yeah, I know, nothing new about that). From ports/Mk/bsd.port.options.mk: # usag

Re: proper use of bsd.port.options.mk

On 2011-05-16 19:23, Doug Barton wrote: > On 5/16/2011 3:23 AM, Chris Rees wrote: >> On 16 May 2011 05:18, Warren Block wrote: >>> On Sun, 15 May 2011, Doug Barton wrote: >>> I'm confused (yeah, I know, nothing new about that). From ports/Mk/bsd.port.options.mk: # usage: #

Re: proper use of bsd.port.options.mk

On Mon, 16 May 2011, Chris Rees wrote: On 16 May 2011 05:18, Warren Block wrote: On Sun, 15 May 2011, Doug Barton wrote: I'm confused (yeah, I know, nothing new about that). From ports/Mk/bsd.port.options.mk: # usage: # #       .include "bsd.port.options.mk" #       #       .include "bsd.p

Compiling tomcat-native barfs

loyal# make ===> License check disabled, port has not defined LICENSE ===> Extracting for tomcat-native-1.1.20_2 => SHA256 Checksum OK for tomcat-native-1.1.20-src.tar.gz. ===> Patching for tomcat-native-1.1.20_2 ===> Applying FreeBSD patches for tomcat-native-1.1.20_2 ===> tomcat-native-1.1.

Re: Propose new macro: INSTALL_CONF

On 15 May 2011 21:56, Chris Rees wrote: > On 14 May 2011 18:32, Chris Rees wrote: >> On 14 May 2011 16:39, Chris Rees wrote: >>> Hi all, >>> >>> I'm getting frustrated with editing config files of ports in vi, and >>> being told it's read-only. >>> >>> This stops me using ZZ to quit, which makes

Re: proper use of bsd.port.options.mk

On 16 May 2011 19:47, Warren Block wrote: > > Could you give an example?  I looked, but nothing obvious jumped out. > I think you (and ohauer) missed my followup with an example [1]. Chris [1] http://www.mail-archive.com/freebsd-ports@freebsd.org/msg33780.html __

Re: patch for force fetch

on 16/05/2011 19:53 Eitan Adler said the following: >> I've run into this myself and simply done the manual rm -f. This looks like >> a great addition. > > what about make distclean ? Can you please elaborate? If you mean that I could just run 'make distclean', then my answer is why should I. I

Re: proper use of bsd.port.options.mk

On 2011-05-16 21:11, Chris Rees wrote: > On 16 May 2011 19:47, Warren Block wrote: >> >> Could you give an example? I looked, but nothing obvious jumped out. >> > > I think you (and ohauer) missed my followup with an example [1]. > > Chris > > [1] http://www.mail-archive.com/freebsd-ports@free

Re: patch for force fetch

On Mon, May 16, 2011 at 10:22:23PM +0300, Andriy Gapon wrote: > on 16/05/2011 19:53 Eitan Adler said the following: > >> I've run into this myself and simply done the manual rm -f. This looks like > >> a great addition. > > > > what about make distclean ? > > Can you please elaborate? > If you m

Re: Compiling tomcat-native barfs

On 2011-05-16 21:04, Christer Solskogen wrote: > loyal# make > ===> License check disabled, port has not defined LICENSE > ===> Extracting for tomcat-native-1.1.20_2 [...] > /usr/obj/usr/ports/devel/apr1/work/apr-1.4.4/libtool: Can't open > /usr/obj/usr/ports/devel/apr1/work/apr-1.4.4/libtool: No

Re: proper use of bsd.port.options.mk

On 16 May 2011 20:43, Olli Hauer wrote: > On 2011-05-16 21:11, Chris Rees wrote: >> On 16 May 2011 19:47, Warren Block wrote: >>> >>> Could you give an example?  I looked, but nothing obvious jumped out. >>> >> >> I think you (and ohauer) missed my followup with an example [1]. >> >> Chris >> >>

Re: proper use of bsd.port.options.mk

On 05/16/2011 13:17, Chris Rees wrote: You can't define USE_JAVA_after_ bsd.port.pre.mk and expect JAVA_PORT to be defined... What I'm looking for is an actual example of something that doesn't work for the common case. Where "actual" includes a path to a port that I can test. And I'm not

Re: Clean up old PRs

Am 16.05.2011 14:02, schrieb Jerry: > There are several PRs that are years (literally) old. For example: > > > o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make > variable in some ports > > Maybe it is time that some o

Re: proper use of bsd.port.options.mk

On Mon, May 16, 2011 at 01:32:18PM -0700, Doug Barton wrote: > On 05/16/2011 13:17, Chris Rees wrote: > > You can't define USE_JAVA_after_ bsd.port.pre.mk and expect JAVA_PORT > > to be defined... > > What I'm looking for is an actual example of something that doesn't work > for the common case.

Re: Compiling tomcat-native barfs

On Mon, May 16, 2011 at 10:13 PM, olli hauer wrote: > Quick fix for apr (just committed, copy to apr1/files) Gee, that was fast! Thanks! It works! :-) -- chs, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd

Re: Call for Testers: VirtualBox 4.0.6

http://www.virtualbox.org/wiki/Changelog 4.0.8 just released -- View this message in context: http://freebsd.1045724.n5.nabble.com/Call-for-Testers-VirtualBox-4-0-6-tp4332763p4402785.html Sent from the freebsd-ports mailing list archive at Nabble.com. _

Ports and Packages for Supported Releases

Portmgr published a new page on their website which describes the current support and EoL policies for the ports tree and released packages. The main take-home messages are: - Support of FreeBSD releases by ports and the ports infrastructure matches the policies set out by the FreeBSD Security O