Call for Testing: OpenOCD 0.10.0

[Steven Kreuzer]

Hi All-

I have a patch that updates devel/openocd to version 0.10.0. I did
some quick testing but if anyone happens to use this port and wants to
give me a hand testing it you can find the patch at
https://people.freebsd.org/~skreuzer/patches/devel-openocd.patch

Please let me know if you have any issues

Thanks
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: awscli-1.9.11

[Steven Kreuzer]

devel/awscli

On Tue, Jan 12, 2016 at 2:51 PM, Alexey Degtyarev
 wrote:
> On 10:07 Tue 12 Jan, Steven Kreuzer wrote:
>
>> On Tue, Jan 12, 2016 at 9:46 AM, Daniel Neades  wrote:
>> > Hi Steven,
>> >
>> >> On 12 Jan 2016, at 14:01, Steven Kreuzer  wrote:
>> >> On Tue, Jan 12, 2016 at 8:05 AM, Daniel Neades  wrote:
>> >>> Please would it therefore be possible to have the py27-botocore port 
>> >>> updated to the latest available version, and the awscli port’s 
>> >>> dependencies appropriately updated?
>> >>
>> >> Would you mind trying out this patch and letting me know if it fixes the 
>> >> issue?
>> >>
>> >> https://people.freebsd.org/~skreuzer/patches/botocore.patch
>> >>
>> >> I'll also open up a PR to get this port updated.
>> >>
>> >> Thanks for reporting this
>> >
>> > That patch does indeed appear to fix the problem. Many thanks for the 
>> > prompt response.
>>
>> Great. Thanks for testing.
>>
>> Alexey-
>>
>> Do I have your approval to commit the patches attached to
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205949
>> Please let me know
>>
>
> Agreed.  Please proceed.  Thanks!

devel/awscli and devel/py-botocore have been updated. Please let me
know if you continue to have issues.
Sorry for all the agita this may have caused
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: awscli-1.9.11

[Steven Kreuzer]

On Tue, Jan 12, 2016 at 9:46 AM, Daniel Neades  wrote:
> Hi Steven,
>
>> On 12 Jan 2016, at 14:01, Steven Kreuzer  wrote:
>> On Tue, Jan 12, 2016 at 8:05 AM, Daniel Neades  wrote:
>>> Please would it therefore be possible to have the py27-botocore port 
>>> updated to the latest available version, and the awscli port’s dependencies 
>>> appropriately updated?
>>
>> Would you mind trying out this patch and letting me know if it fixes the 
>> issue?
>>
>> https://people.freebsd.org/~skreuzer/patches/botocore.patch
>>
>> I'll also open up a PR to get this port updated.
>>
>> Thanks for reporting this
>
> That patch does indeed appear to fix the problem. Many thanks for the prompt 
> response.

Great. Thanks for testing.

Alexey-

Do I have your approval to commit the patches attached to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205949
Please let me know

Thanks
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: awscli-1.9.11

[Steven Kreuzer]

On Tue, Jan 12, 2016 at 9:02 AM, Kurt Jaeger  wrote:
> There is
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205949
>
> already, with an upgrade for awscli, as well.

Thanks. I just grabbed the PR
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: awscli-1.9.11

[Steven Kreuzer]

Hi Daniel-

On Tue, Jan 12, 2016 at 8:05 AM, Daniel Neades  wrote:
> Please would it therefore be possible to have the py27-botocore port updated 
> to the latest available version, and the awscli port’s dependencies 
> appropriately updated?

Would you mind trying out this patch and letting me know if it fixes the issue?

https://people.freebsd.org/~skreuzer/patches/botocore.patch

I'll also open up a PR to get this port updated.

Thanks for reporting this
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Would appreciate a committer's attention to these

[Steven Kreuzer]

On Thu, Jan 8, 2015 at 3:06 PM, Paul Schmehl  wrote:
> I submitted change maintainer requests for all my remaining ports.  1/30 is
> my retirement date.  I would appreciate it if someone could pick these up
> and process them by that date.
>
> 

Hi Paul-

I grabbed most of those PRs and I will start working through them all.
Thank you for your service to the FreeBSD community and
congratulations on the retirement.

SK
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

New Maintainer for devel/rubygem-rcov

[Steven Kreuzer]

Would anyone be interested in adopting devel/rubygem-rcov. I just
received a notice that this port is going to be deleted because it
doesn't work with Ruby 2.0

It appears that the original rcov was forked and the new version that
works with 2.0 is located at https://github.com/relevance/rcov

However, I don't use ruby anymore so I don't think I am the best
person to be the maintainer of this port.

If you are interested in adopting this port, please let me know

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: cfengine36-3.6.1_3,1

[Steven Kreuzer]

On Wed, Nov 19, 2014 at 5:23 AM, Jurica Borozan
 wrote:
> Hi Steven,
>
> I tested proposed solution which is partially ok.
>
> XML processing is there but segmentation fault/core dump is still
> present due to a problem in backup-ing processed files.

Can you send me the core file?

> Even more: I tested non-xml functionality to investigate this "backup" issue 
> and it
> is there too. On linux there is no problem with this issue.

I am not sure what you mean when you saying backing up processed files?
Can you send me an example agent that caused this issue and I can take
a closer look.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: cfengine36-3.6.1_3,1

[Steven Kreuzer]

Hi Jurica-

On Mon, Nov 17, 2014 at 12:18 PM, Jurica Borozan
 wrote:
> Hi,
>
> I am trying to run cfengine 3.6.1 and 3.5.8 but it will not work with
> XML files: "error: Cannot edit XML files without LIBXML2"

It looks like the current version of the port doesn't have the option
to pull in libxml2 to enable this feature.
Can you try out this patch and let me know if it solves your issue?
https://people.freebsd.org/~skreuzer/patches/cfengine36-libxml.patch

The following commands will download the patch into your home
directory, apply the changes to the port and build and install a
version of
cfengine with xml support

$ cd ~
$ fetch https://people.freebsd.org/~skreuzer/patches/cfengine36-libxml.patch
$ cd /usr/ports
$ patch < ~/cfengine36-libxml.patch
$ cd /usr/ports/sysutils/cfengine36
$ sudo make WITH="LIBXML2" install

Let me know if you have any problems.

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

New Ganglia Maintainer

[Steven Kreuzer]

Would anyone be interested in adopting sysutils/ganglia-monitor-core
and sysutils/ganglia-webfrontend from me?

I no longer use ganglia and since its a pretty complex port I think it
will be better off in the hands of someone that has it deployed and
works with it frequently

It still needs staging support added and is a few version behind so it
needs some attention.

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Are there plans for updating OpenOCD to version 0.8.0?

[Steven Kreuzer]

Hi Torfinn-

On Sun, May 4, 2014 at 4:38 PM, Torfinn Ingolfsen  wrote:
> Hello,
> Are there plans for updating devel/openocd to version 0.8.0?

I don't think I am going to get a chance to update this port in the
very near future. If you are interested in taking a shot at upgrading,
feel free to send me any patches for review.
I added it to my todo and hopefully will get a chance to update it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: shebangfix for /bin/sh

[Steven Kreuzer]

On Wed, Mar 26, 2014 at 12:01 PM, Baptiste Daroussin  wrote:
> On Wed, Mar 26, 2014 at 11:44:21AM -0400, Steven Kreuzer wrote:
>> On Tue, Mar 25, 2014 at 9:48 AM, Baptiste Daroussin  wrote:
>> > On Tue, Mar 25, 2014 at 09:36:37AM -0400, Steven Kreuzer wrote:
>> >> On Fri, Mar 14, 2014 at 1:08 PM, Steven Kreuzer  
>> >> wrote:
>> >> > Hi All-
>> >> >
>> >> > I am in the process of cleaning up sysutils/DTraceToolkit and I would
>> >> > like to make use of USES=shebangfix
>> >> >
>> >> > However, it looks like on solaris, sh is /usr/bin/sh so I would like
>> >> > to propose the following change:
>> >> >
>> >> > http://people.freebsd.org/~skreuzer/patches/shebang.patch
>> >>
>> >> Can someone from portmgr chime in on this? I would like to get it 
>> >> committed so
>> >> I can commit some changes to sysutils/DTraceToolkit
>> >>
>> >> Thanks
>> >
>> > How many ports are concerned?
>> > if just one there is no need to add this into shebangfix.mk
>>
>> So far I have only seen this in one port. I am not sure how widespread it is.
>> However, it looks like this is a solaris-ism so it seems like we should just
>> include it as part of shebangfix instead of doing it in just that one port.
>>
>> If you guys disagree, I will just do it in the port.
>>
> I disagree, I prefer it be be done in a couple of ports and if the number of
> ports using that is growing then we can merge it into the infra.

Sounds like a plan. Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: shebangfix for /bin/sh

[Steven Kreuzer]

On Tue, Mar 25, 2014 at 9:48 AM, Baptiste Daroussin  wrote:
> On Tue, Mar 25, 2014 at 09:36:37AM -0400, Steven Kreuzer wrote:
>> On Fri, Mar 14, 2014 at 1:08 PM, Steven Kreuzer  wrote:
>> > Hi All-
>> >
>> > I am in the process of cleaning up sysutils/DTraceToolkit and I would
>> > like to make use of USES=shebangfix
>> >
>> > However, it looks like on solaris, sh is /usr/bin/sh so I would like
>> > to propose the following change:
>> >
>> > http://people.freebsd.org/~skreuzer/patches/shebang.patch
>>
>> Can someone from portmgr chime in on this? I would like to get it committed 
>> so
>> I can commit some changes to sysutils/DTraceToolkit
>>
>> Thanks
>
> How many ports are concerned?
> if just one there is no need to add this into shebangfix.mk

So far I have only seen this in one port. I am not sure how widespread it is.
However, it looks like this is a solaris-ism so it seems like we should just
include it as part of shebangfix instead of doing it in just that one port.

If you guys disagree, I will just do it in the port.

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: shebangfix for /bin/sh

[Steven Kreuzer]

On Fri, Mar 14, 2014 at 1:08 PM, Steven Kreuzer  wrote:
> Hi All-
>
> I am in the process of cleaning up sysutils/DTraceToolkit and I would
> like to make use of USES=shebangfix
>
> However, it looks like on solaris, sh is /usr/bin/sh so I would like
> to propose the following change:
>
> http://people.freebsd.org/~skreuzer/patches/shebang.patch

Can someone from portmgr chime in on this? I would like to get it committed so
I can commit some changes to sysutils/DTraceToolkit

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

shebangfix for /bin/sh

[Steven Kreuzer]

Hi All-

I am in the process of cleaning up sysutils/DTraceToolkit and I would
like to make use of USES=shebangfix

However, it looks like on solaris, sh is /usr/bin/sh so I would like
to propose the following change:

http://people.freebsd.org/~skreuzer/patches/shebang.patch

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Question regarding creating a port with dependencies

[Steven Kreuzer]

Hi Joe-

On Thu, Mar 13, 2014 at 9:13 PM, Joseph Benden  
wrote:
> I am porting Vagrant to FreeBSD.

This is very good news. I have been looking at potentially deploying
vagrant at work to make QA testing
way easier. Having a FreeBSD port of this would be extremely helpful

> It requires a handful of extra gems to be installed. When I go to create a PR 
> for this; should I submit
> everything necessary as a single PR or each individual port as a PR?

I would submit one PR per new port and then in the vagrant port
perhaps mention that these other PRs need
to be committed before the vagrant one.

Its a bit more work, but it might be easier to keep track of
everything in case certain changes need to be made
to an individual ruby port.

Thanks for working on this. Feel free to ping me via irc or shoot me
an email if you need any assistance.

SK
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Adopt shells/pdksh?

[Steven Kreuzer]

On Fri, Aug 30, 2013 at 06:08:05PM +0200, Rodrigo OSORIO wrote:
> 
> hi,
> 
> If nobody is interested by your port, I'll take it.
> May I ask you to update the port owner to rodr...@bebik.net for me :)

Thanks Rodrigo. I updated the MAINTAINER to be you. If you figure out
what is going on in ports/181438 please shoot me a patch and I will
commit it

Thanks

> 
> regards
> 
> -rodrigo
> 
> 
> On 30/08/13 10:12 -0400, Steven Kreuzer wrote:
> > Any pdksh users out there that would like to take over as maintainer
> > of the port?
> > 
> > I am no longer using ksh and it doesn't play well on FreeBSD-10
> > (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/181438)
> > 
> > I marked the port as broken and I doubt I am going to have any time to
> > attempt to resolve the issue.
> > 
> > If you are interested, let me know
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


pgpctCILlpTWU.pgp
Description: PGP signature

Adopt shells/pdksh?

[Steven Kreuzer]

Any pdksh users out there that would like to take over as maintainer
of the port?

I am no longer using ksh and it doesn't play well on FreeBSD-10
(http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/181438)

I marked the port as broken and I doubt I am going to have any time to
attempt to resolve the issue.

If you are interested, let me know
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [devel/openocd] who wants to takeover maintenance?

[Steven Kreuzer]

On Tue, Jul 30, 2013 at 3:18 PM, CeDeROM  wrote:

> On Tue, Jul 30, 2013 at 8:33 PM, Steven Kreuzer 
> wrote:
> > On Mon, Jul 29, 2013 at 8:17 AM, CeDeROM  wrote:
> >>
> >> Hello :-)
> >>
> >> If there are any people that want to take over the devel/OpenOCD
> >> project port, its free to take. I got some disagreement with OpenOCD
> >> developers and started my own project, so if anyone has some time to
> >> put into this port feel free to do so :-)
> >
> >
> > Hi Tomek-
> >
> > I just set the MAINTAINER to myself. Thanks for maintaing this port for
> > the past couple of years.
>
> Thank you Steven! :-) Please note, that you have a chance to update
> port to version 0.7.0. I am working on something totally new :-)


Yup. I saw that upstream has released a new version and I will look into
updating the port
in the very near future. Good luck on your new project and let me know when
you have a release
and I can add a port for it
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [devel/openocd] who wants to takeover maintenance?

[Steven Kreuzer]

On Mon, Jul 29, 2013 at 8:17 AM, CeDeROM  wrote:

> Hello :-)
>
> If there are any people that want to take over the devel/OpenOCD
> project port, its free to take. I got some disagreement with OpenOCD
> developers and started my own project, so if anyone has some time to
> put into this port feel free to do so :-)
>

Hi Tomek-

I just set the MAINTAINER to myself. Thanks for maintaing this port for
the past couple of years.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainer reset for benchmarks/fio, sysutils/ataidle and x11-clocks/wmclock

[Steven Kreuzer]

Thanks Bruce-

On Thu, Jun 27, 2013 at 12:17 PM, Bruce Cran  wrote:

> On 27/06/2013 17:03, Steven Kreuzer wrote:
>
>> I've adopted benchmarks/fio from you.
>>
>
> Thanks. It needs updated to 2.1.1 - I've attached the patch, though the
> Makefile change probably won't apply now.
>

I made some slight changes to the patch and just committed it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainer reset for benchmarks/fio, sysutils/ataidle and x11-clocks/wmclock

[Steven Kreuzer]

On Thu, Jun 27, 2013 at 8:20 AM, Bruce Cran  wrote:

> I've given up my commit bit: could someone reset the maintainer for
> benchmarks/fio, sysutils/ataidle and x11-clocks/wmclock please?


I've adopted benchmarks/fio from you. Thanks for maintaining over the past
couple of years
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD related NKIs for robotfindskitten

[Steven Kreuzer]

I don't see any reason why it couldn't. Not sure how many NKIs would be
appropriate entires for a fortune file, but it should be easy enough to
convert from 1 format to the other


On Mon, Jan 14, 2013 at 10:36 AM, Eitan Adler  wrote:

> On 14 January 2013 09:34, Steven Kreuzer  wrote:
> > I recently updated games/robotfindskitten to the latest version. One of
> the
> > nice new features is that fact that non kitten items (nki) are no longer
> > hard coded in the source.
> >
> > This allows you to add additional nki to the game fairly easily so I
> > started to make a list of freebsd related history, inside jokes, and
> random
> > cultural references.
> >
> > Once the list gets large enough, I will add it to the port so I am asking
> > for some help from the community to compile a nice long list. If you have
> > anything to add, please let me know.
> >
> > My current list can be found here: https://gist.github.com/4521897
>
> Just a thought: perhaps this could automatically be turned into a
> fortune(6) file as well?
>
> --
> Eitan Adler
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD related NKIs for robotfindskitten

[Steven Kreuzer]

I recently updated games/robotfindskitten to the latest version. One of the
nice new features is that fact that non kitten items (nki) are no longer
hard coded in the source.

This allows you to add additional nki to the game fairly easily so I
started to make a list of freebsd related history, inside jokes, and random
cultural references.

Once the list gets large enough, I will add it to the port so I am asking
for some help from the community to compile a nice long list. If you have
anything to add, please let me know.

My current list can be found here: https://gist.github.com/4521897

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD related NKIs for robotfindskitten

[Steven Kreuzer]

I recently updated games/robotfindskitten to the latest version. One of the
nice new features is that fact that non kitten items (nki) are no longer
hard coded in the source.

This allows you to add additional nki to the game fairly easily so I
started to make a list of freebsd related history, inside jokes, and random
cultural references.

Once the list gets large enough, I will add it to the port so I am asking
for some help from the community to compile a nice long list. If you have
anything to add, please let me know.

My current list can be found here: https://gist.github.com/4521897

Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: downloading source code from github

[Steven Kreuzer]

The documentation for doing this is in Mk/bsd.sites.mk (cut and pasted
below)
Also, You can take a look at devel/py-kazoo as an example

#
# In order to use GitHub your port must define USE_GITHUB and the following
# variables:
#
# GH_ACCOUNT- account name of the GitHub user hosting the project
# default: not set, mandatory
#
# GH_PROJECT- name of the project on GitHub
# default: ${PORTNAME}
#
# GH_TAGNAME- name of the tag to download (master, 2.0.1, ...)
# default: ${DISTVERSION}
#
# GH_COMMIT - first 7 digits of the commit that generated GH_TAGNAME
# (man git-describe(1))
# default: not set, mandatory
#


On Tue, Dec 11, 2012 at 6:40 AM, Radim Kolar  wrote:

> its good practice to download source code using git from github if it is
> not available for download, just tagged in repo?
> __**_
> 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
> "
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Can we please just remove the old Makefile headers?

[Steven Kreuzer]

On Thu, Aug 30, 2012 at 3:56 PM, Thomas Abthorpe  wrote:
> On Sun, Aug 26, 2012 at 02:02:47PM -0700, Doug Barton wrote:
>> The old Makefile headers, ala:
>>
>> # New ports collection makefile for:BIND 9.9.x
>> # Date created: 27 January 2012
>> # Whom: dougb
>> #
>> # $FreeBSD: head/dns/bind99/Makefile 301487 2012-07-24 19:23:23Z dougb $
>>
>> have not served a purpose for longer than almost anyone who has a ports
>> commit bit has been around. My proposal is simple, let's remove
>> everything before the # $FreeBSD$.
>
> Traditions are great, particularly when they have meaning.  When they
> just become "Doing it that way because we always done it" is no
> substitute for maintaining a tradition for a meaningful purpose.
>
>>
>> In the past when this has been proposed the objection was that it would
>> cause too much churn. If we had done this back when we had 5,000 ports
>> then we would have solved the problem with less churn, and no drama for
>> the 15,000 ports that followed. Every day we don't do this we make the
>> "churn" problem worse, and deepen the roots of something that has no
>> relevance.
>>
>> Can we please just deal with this now and be done with it? ... and yes,
>> I am volunteering to help with and/or do the work myself.
>
> We discussed this on portmgr@, and we have agreed it is time to make the
> change.
>
> We do request that this be done sparingly in the short term, as we do not
> want to cause any additional churn on the repo as we approach our
> upcoming Ports Feature Freeze, still tentatively scheduled for September
> 7.
>
> So please proceed only on existing updates.  Please do not do any
> sweeping commits until we have the ports tree stablised post 9.1
> tagging.  Also bear in mind that Redports/QAT queues a job for every
> change done to a Makefile, we do not want to overburden the QAT at this
> time.  It is important to allow this service to run at peek efficiency
> at this time to ensure it's full potential as we approach the upcoming
> Feature Freeze.
>
> So without further ado, this is what we would like to see at the top of
> the makefile
>
> #
> # $FreeBSD$
> #
>
> PORTNAME=
>
> It is as easy as that :)

This would make me happy. Another option I would like to throw out there is
to just stick the # $FreeBSD$ at the end of the file so the first line
is PORTNAME=
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: ports-mgmt/porttools - Update to work with svn

[Steven Kreuzer]

On Tue, Aug 21, 2012 at 10:35 PM, Steve Wills  wrote:
> Hi,
>
> I did a quick hack to make porttools work with svn. It's far from perfect, 
> but it makes "port submit" work for me. It's available here:
>
> http://meatwad.mouf.net/~steve/porttools_svn.diff

It looks like the diff might be reversed
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: need porting advice: one tool from a larger package

[Steven Kreuzer]

I think it makes sense to name the package i2c-tools since if someone finds out 
about this software, they are going to look for it by that name in the ports 
tree.

When the person goes to install it, add a pkg-message saying that only certain 
parts run on freebsd etc.

I did something very similar with the dtracetoolkit. When I made the port, 
FreeBSD didn't have the pid provider yet, so a large majority of the scripts 
could not be run. The ones that I could get to run get installed and the other 
ones don't.

-- 
Steven Kreuzer


On Tuesday, April 17, 2012 at 5:49 AM, Andriy Gapon wrote:

> 
> There is a package of a variety of tools, i2c-tools
> (http://www.lm-sensors.org/wiki/I2CTools).
> I want to port to FreeBSD only a single tool from that package, decode-dimms.
> How should I name my port, "i2c-tools" or "decode-dimms"?
> In my opinion, "decode-dimms" has an advantage of being honest and
> straightforward, but "i2c-tools" has an advantage of preserving the original
> upstream package name. In the future someone might want to port another tool
> from that package and instead of having to create a new port they could just 
> add
> necessary patches and modify the install target and the plist.
> 
> Thank you.
> -- 
> Andriy Gapon
> ___
> freebsd-ports@freebsd.org (mailto:freebsd-ports@freebsd.org) mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org 
> (mailto:freebsd-ports-unsubscr...@freebsd.org)"
> 
> 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: innotop-1.8.0_2 and mytop-1.6_7 cannot be installed together

[Steven Kreuzer]

Hi Miroslav-

On Oct 31, 2011, at 3:59 PM, Miroslav Lachman wrote:

> Hi,
> 
> I tried to install innotop and mytop together by portmaster command:
> 
> portmaster databases/mytop databases/innotop
> 
> ===>>> The following actions will be taken if you choose to proceed:
>Install databases/mytop
>Install databases/p5-DBD-mysql
>Install databases/p5-DBI
>Install devel/p5-Term-ReadKey
>Install databases/innotop
>Install databases/p5-DBD-mysql51
> 
> As you can see, there is problem with conflicting dependencies: p5-DBD-mysql 
> vs. p5-DBD-mysql51
> 
> The portmaster installed p5-DBD-mysql and mytop first, then innotop 
> installation failed with:
> 
> ===>  p5-DBD-mysql51-4.019 conflicts with installed package(s):
>  p5-DBD-mysql-4.019
> 
>  They will not build together.
>  Please remove them first with pkg_delete(1).
> 
> 
> If innotop is installed separately first (with it's dependency 
> p5-DBD-mysql51), then mytop will install OK and will use p5-DBD-mysql51 
> instead of default p5-DBD-mysql.
> 

Can you apply this patch to mytop and try one more time. 
http://exit2shell.com/~skreuzer/patches/mytop.patch

Thanks

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Speling Mistakes

[Steven Kreuzer]

I would like to apply this patch
(http://www.exit2shell.com/~skreuzer/patches/speling.diff) which fixes
a few spelling mistakes in the COMMENT field for some
unmaintained ports:

games/qudos
editors/ne
misc/ftdi-eeprom
games/egl
devel/py-period
devel/p5-Penguin-Easy
games/r1q2
games/tremor
textproc/mkcatalog
databases/p5-DBIx-AnyDBD
net/ncplib

Anyone have any objections?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Submitting a follow up to a port update

[Steven Kreuzer]

I just committed the update and closed the PR.

Thanks.

On Sun, Jul 17, 2011 at 4:54 PM, Gavin McDonald  wrote:
>
>
>> -Original Message-
>> From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd-
>> po...@freebsd.org] On Behalf Of Chris Rees
>> Sent: Saturday, 16 July 2011 11:33 AM
>> To: ga...@16degrees.com.au
>> Cc: skreu...@freebsd.org; freebsd-ports@freebsd.org
>> Subject: Re: Submitting a follow up to a port update
>>
>> On 12 July 2011 23:38, Gavin McDonald  wrote:
>> > Hi All,
>> >
>> > I'm the current maintainer for the scons port.
>> >
>> > http://www.freebsd.org/cgi/query-pr.cgi?pr=158205
>> >
>> > As you can see, on the 24th June an update/patch was requested.
>> > I also received 2 emails, one from skreuzer via FreeBSD-gnats-submit
>> > and then also one from Edwin via bug-followup.
>> >
>> > So I check it out etc, looks fine and I want to approve it. So what
>> > did I do I clicked on the 'Submit Followup' link on the webpage
>> >
>> > (mailto:bug-
>> follo...@freebsd.org,skreu...@freebsd.org?subject=Re:%20po
>> > rts/15
>> >
>> 8205:%20%5BPATCH%5D%20devel%2Fscons%3A%20update%20to%20%32.%
>> 30.%31)
>> >
>> > I send my email there and to 'bug-follo...@freebsd.org';
>> > 'skreu...@freebsd.org' on the 25th June.
>> >
>> > Not only have I not heard anything but my follow up and approval to
>> > patch has not appeared on the patch [158205]
>> >
>> > I assume I have done something wrong?
>> >
>> > I also assume folks think I have been ignoring them and will get
>> > ousted by a maintainer timeout when in fact I replied approving the
>> > patch after only one day.
>> >
>> > What do I need to do now?
>> >
>> > Thanks
>> >
>> > Gav...
>> >
>>
>> pgollucci@ has just fixed it for you.
>>
>> All you have to do is wait for skreuzer@ to commit it ;)
>>
>> Chris
>
> Great, thanks Chris, Philip and skreuzer :)
>
> Gav...
>
>> ___
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports with a broken PKGORIGIN: chinese/joe, security/p5-Auth-Yu...

[Steven Kreuzer]

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 **
>
>  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-po...@opsec.eu
>   | Original-Recipient: rfc822;fbsd-po...@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
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO?

[Steven Kreuzer]

> 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.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PearPC port broken?

[Steven Kreuzer]

I just ran pearpc through a 8.2 amd64 tinderbox and it bombed out.
Looks like whatever is causing it not to compile in 8 has been fixed
in 9. We can change the port so thats its only marked as broken if the
OS is not >= 9

On Wed, Apr 13, 2011 at 5:57 PM, Artur Bednarek  wrote:
> Hi
>
> Why pearpc port (emulators/pearpc) was marked as BROKEN, DEPRECATED etc.
>
> It working for me, compile without any error with base compiler:
>
> http://img810.imageshack.us/i/pearpc.png/
>
> Artur Bednarek
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

devel/gdb Port

[Steven Kreuzer]

With the help of jhb@, I have a port of gdb 7.1 that has been modified to 
recognize freebsd threads. I would like to get this added to the ports tree
but I would like some feedback as to how it should be added.

Currently, the latest version of gdb in the ports tree is 6.6 and its under 
devel/gdb66. I was thinking of adding this as gdb71 but the latest version of
the 7.x branch is 7.2 and someone already created a port for it (ports/151077) 
but it doesn't recognize threads.

So, for the 7 branch, would it make sense to check in version 7.1 as devel/gdb7 
and eventually update it to 7.2, or should it be checked in as devel/gdb71?

shar file can be found at http://exit2shell.com/~skreuzer/patches/gdb71.shar

SK___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership of my ports

[Steven Kreuzer]

On Sep 27, 2010, at 7:36 PM, Charlie Kester wrote:

> On Mon 27 Sep 2010 at 12:32:56 PDT Tobias Roth wrote:
>> x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more
> 
> I use this and can take maintainership.

You have been set as the maintainer.

Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership of my ports

[Steven Kreuzer]

On Sep 27, 2010, at 4:23 PM, Ruslan Mahmatkhanov wrote:

> 27.09.2010 23:32, Tobias Roth пишет:
>> Hi
>> 
>> I haven't been using FreeBSD as a desktop for a while now, and am thus
>> dropping maintainerships of my ports. If anyone wants to step up and
>> take over maintainership, please send me an email. For everything left
>> over, I will send PRs to reset the maintainer to ports@ in about two weeks.
>> 
>> The ports are
>> 
>> audio/py-eyed3 : Python module for processing ID3 tags
>
> I want this one

Updated MAINTAINER to cvs-...@yandex.ru

Thanks!___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Adopting www/rt38

[Steven Kreuzer]

Hi All-

I would like to put www/rt38 up for adoption. My company no longer uses it and 
I don't really have the time
to support it anymore. As a result, the port is 2 versions out of date and 
badly in need of some attention.

Please let me know if you have interest in maintaing it.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

CFT: www/rt38 v3.8.8

[Steven Kreuzer]

Hello-

RequestTracker v3.8.8 has been released and I got a chance to sit down and 
update the port from 3.8.6 to 3.8.8
I am looking for some people who can help me test it out. Patch to update the 
port can be found at http://exit2shell.com/~skreuzer/patches/rt38-388.patch

Please reply directly to me if you are able to test it out.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: innotop 1.7.2

[Steven Kreuzer]

On May 22, 2010, at 2:16 PM, cronfy wrote:

> Hello Steven,
> 
> you are the maintainer of databases/innotop port for FreeBSD. Have you
> seen that there is a new version of innotop:
> http://code.google.com/p/innotop/ ? Would you mention updating it in
> the ports collection?

Thanks for the heads up.

I just committed the update. Update your ports tree and you should be all set.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: python and HUGE_STACK_SIZE

[Steven Kreuzer]

On Mar 25, 2010, at 1:07 AM, Adam Vande More wrote:

> On Wed, Mar 24, 2010 at 5:50 PM, Chuck Swiger  wrote:
> 
>> 
>> I've run and written quite a bit of Python (including Trac, Mailman, the
>> Python IDE, our own custom stuff [like some log munging and web processing
>> stuff], and even a few graphical Python games) without ever turning
>> HUGE_STACK_SIZE on.
>> 
>> I don't have any objection to turning it on, but it's not needed by default
>> for most things.  YMMV.
>> 
>> 
> Yes, I've had the same experience.  When doing socket level python stuff,
> I've had to increase the buffer size, which seems to be at least indirectly
> related to stack size but setting it manually has been easy enough.  Are
> there any negative repercussions to turning on huge ie like would scripts
> start using more memory, or is just giving them the ability to use it
> without explicitly setting it?

So, it seems like most of the time python scripts will work with HUGE_STACK_SIZE
turned off, but every once and a while some scripts will fail in non obvious 
ways
that could leave a person scratching their head for weeks trying to get to the 
bottom of it

To me, it seems like the best behavior would be to default to compiling with 
that set. I'll create
a patch over the weekend and open a PR

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

python and HUGE_STACK_SIZE

[Steven Kreuzer]

A coworker of mine got bit by this bug on and off for the last few weeks and it 
appears he might not
be the only one as documented in this blog:

http://tomster.org/blog/archive/2006/09/27/size-does-matter

If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a 
reason
to provide the option to not compile python with it, or at the very least, 
should it default to
being on?

I'm not a python guy, so I am just asking in case what is in the blog post is 
true.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer



--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Ports with same name

[Steven Kreuzer]

Hello-

As documented in http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144277
we have two ports with the same name:

Port:   gag-2.9
Path:   /usr/ports/security/gag
Info:   A stacheldraht (DOS attack) agent detector
Maint:  po...@freebsd.org
B-deps: 
R-deps: 
WWW:http://www.washington.edu/People/dad/

Port:   gag-4.9
Path:   /usr/ports/sysutils/gag
Info:   Graphical Boot Manager
Maint:  alepul...@freebsd.org
B-deps: 
R-deps: 
WWW:http://gag.sourceforge.net/

I am looking for some advice on whats the best course of action to deal with 
this.

My gut feeling is that sysutils/gag should remain the same and that 
security/gag should be
renamed to security/gag-stacheldraht.

Anyone vehemently opposed to this?

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: net-mgmt/netxms

[Steven Kreuzer]

Hey Sergey-

On Feb 22, 2010, at 9:01 AM, Sergey V. Gershovich wrote:

> Hello!
> NetXMS port are broken now:
> 
> # uname -a
> FreeBSD test.szkti.ru 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0:
> Tue Jan  5 16:02:27 UTC 2010 
> r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
> 
> # portsnap fetch update
> Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
> Fetching snapshot tag from portsnap1.FreeBSD.org... done.
> Latest snapshot on server matches what we already have.
> No updates needed.
> Ports tree is already up to date.
> 
> # cd /usr/ports/net-mgmt/netxms && make fetch
> => netxms-0.2.24.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
> => Attempting to fetch from http://www.netxms.org/download/.
> fetch: http://www.netxms.org/download/netxms-0.2.24.tar.gz: Not Found
> => Attempting to fetch from 
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
> fetch: 
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/netxms-0.2.24.tar.gz: File 
> unavailable (e.g., file not found, no access)
> => Couldn't fetch it - please try to retrieve this
> => port manually into /usr/ports/distfiles/ and try again.
> *** Error code 1
> 
> Stop in /usr/ports/net-mgmt/netxms.

It appears that the upstream provider moved previous versions from downloads/ 
to downloads/archives
This patch should fix this issue: 
http://people.freebsd.org/~skreuzer/patches/netxms.patch

Give that patch a shot and if it works out, let me know and I will fix the port 
in the tree.

Also, please consider adopting this port if you use it. It is currently out of 
date and does not have a maintainer
so issues like this will keep cropping up as time goes on.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: My ports.

[Steven Kreuzer]

Hey Marcelo-

On Feb 22, 2010, at 6:48 AM, Marcelo Araujo wrote:

> Hi guys,
> 
> There are some ports that I haven't interested and neither used anymore,
> so I'm here to check if there is anyone that would be interested to push
> them and maintain those updated before set up those to po...@.
> 
> Please, send me a list of ports that you want and I'm gonna release to you
> or fell free to take it by yourself.
> 
> Follow bellow those ports that I haven't interest anymore.
> 
> net/p5-Net-Analysis
> net/passlogd

I took these two ports from you.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: rt-3.8.4_1

[Steven Kreuzer]

On Dec 3, 2009, at 5:19 PM, Steven Kreuzer wrote:

> 
> On Dec 3, 2009, at 4:44 PM, Kyle McKinley wrote:
> 
>> Hello,
>> 
>> I was just wondering when the 3.8.6 would be available?  Thanks!
> 
> I am currently running 3.8.6 through tinderbox so the answer is in the very 
> near
> future..
> 
> If you (or anyone on the ports mailing list) happen to be in a position to 
> help me test out this update,
> please get in touch with me

Patch can be found at http://exit2shell.com/~skreuzer/patches/rt38.patch

This is a fairly complex port so if anyone is able to assist in testing a live 
install, please do so and let me know if you encounter any problems.
I am going to test it out a little bit more and hopefully next week I'll commit 
it to the ports tree. 

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: rt-3.8.4_1

[Steven Kreuzer]

On Dec 3, 2009, at 4:44 PM, Kyle McKinley wrote:

> Hello,
> 
> I was just wondering when the 3.8.6 would be available?  Thanks!

I am currently running 3.8.6 through tinderbox so the answer is in the very near
future..

If you (or anyone on the ports mailing list) happen to be in a position to help 
me test out this update,
please get in touch with me

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Whitelist certain MASTER_SITES in portlint

[Steven Kreuzer]

I would like to propose the following change to portlint to silence  
the warning when only one MASTER_SITES is defined under certain  
conditions.
It adds a variable that is a list of "cloud" providers such as google  
code that appear as a single site but are, in theory,
massively redundant. If a whitelisted site is set for MASTER_SITES, it  
doesn't throw that warning.


Patch for review: http://exit2shell.com/~skreuzer/patches/portlint.patch

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: status of FreeBSD ports you maintain as of 20090705

[Steven Kreuzer]

Hey Frank-

On Jul 16, 2009, at 10:37 AM, Frank Steinborn wrote:


Martin Tournoij wrote:


games/avanor
games/crimson
games/wrogue


I would take these.


You are now that maintainer of those ports. Treat them well ;)

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: status of FreeBSD ports you maintain as of 20090705

[Steven Kreuzer]

Hey Sylvio-

On Jul 16, 2009, at 7:36 AM, Sylvio Cesar wrote:


Hi guys,

I would like to be the maintainer of ports

audio/csound
devel/cdialog
print/scribus
sysutils/bashburn
sysutils/daa2iso
sysutils/mybashburn
sysutils/uif2iso


You are now that maintainer of those ports. Treat them well ;)

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Port of "service" command

[Steven Kreuzer]

On Jun 9, 2009, at 1:46 PM, Edwin Shao wrote:


Hello,

I was wondering if there was a port of the Linux/UNIX service
<http://www.manpagez.com/man/8/service/>,
<http://linux.die.net/man/8/service> command? If not, is there any
philosophical reason or roadblock to my creating one?


Not to long ago I wrote a FreeBSD specific version of service.
I have some additional things I want to add in at a later date,
but this version works pretty well.

http://www.exit2shell.com/~skreuzer/patches/service.diff

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mtools vs X11 (Re: FreeBSD Port: syslinux-3.72)

[Steven Kreuzer]

On Mar 20, 2009, at 6:15 PM, Michel Talon wrote:


Steven Kreuzer wrote:


Can we consider people who use the CLI an advanced user? If so, the
expectation that they will be able to build a port with -DWITHOUT_X11
is not unreasonable.
People who are more likely to use the GUI are the ones who will not  
be

aware of the WITHOUT_X11 knob.


And the end user who uses prepackaged packages will get mtools with
a totally useless GUI. I have hard time beleiving you are not trolling
with such theories.


As I said in a previous email, you are more then welcome to fork the  
port

and modify it in whatever way you please. When you do so, open a PR
and I will gladly commit it for you.

Take a look at net/cvsup and net/cvsup-without-gui if you need  
inspiration


--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mtools vs X11 (Re: FreeBSD Port: syslinux-3.72)

[Steven Kreuzer]

On Mar 20, 2009, at 5:24 PM, Cynthia Flynn wrote:


Steven Kreuzer wrote:

On Mar 19, 2009, at 4:06 AM, per...@pluto.rain.com wrote:

Gary Jennejohn  wrote:

Luigi Rizzo  wrote:

... Cynthia Flynn wrote:

[snip - syslinux pulls in too much X11 stuff]

I think the extra dependencies that you find listed for syslinux:
[snip]
come directly from mtools ...


Yeah.  It looks like mtools uses X11 by default, which IMHO is
incorrect.  Instead it should have an option to turn X11 _on_,
rather than one for turning it _off_, as it currently does.


IMO it is a POLA violation for mtools to depend on X11 *at all*.

Instead of having an option, maybe the port should be split so that
mtools itself just provides the code to access FAT filesystems, and
(say) mtools-gui does the fancy display stuff.
mtools already supports WITHOUT_X11 so if you don't want the GUI  
stuff, you can build the port
without it. Personally, I think it makes more sense for mtools to  
be the full and complete representation

of the actual program.


Can someone confirm for me that a normal port install of mtools  
brings up a configuration menu in which the WITHOUT_X11 option can  
be set? I do not remember seeing any such thing, but it has probably  
been 6 months since I last tried it.


when you do a make install for the mtools port, it does not prompt you  
if you would like to build the port without X11. This can be enabled  
by passing
-DWITHOUT_X11 to make, or adding WITHOUT_X11=yes to make.conf to apply  
it to all ports that you build on that system


Perhaps I am not as typical a user as I thought, and you folks  
certainly aren't obligated to address the requirements of niche  
users, but if the setting of WITHOUT_X11 is not clearly presented  
for setting during a normal port install then I would humbly suggest  
that for all practical purposes it doesn't exist for most users.


Can we consider people who use the CLI an advanced user? If so, the  
expectation that they will be able to build a port with -DWITHOUT_X11  
is not unreasonable.
People who are more likely to use the GUI are the ones who will not be  
aware of the WITHOUT_X11 knob.


--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mtools vs X11 (Re: FreeBSD Port: syslinux-3.72)

[Steven Kreuzer]

On Mar 19, 2009, at 4:06 AM, per...@pluto.rain.com wrote:


Gary Jennejohn  wrote:

Luigi Rizzo  wrote:

... Cynthia Flynn wrote:

[snip - syslinux pulls in too much X11 stuff]

I think the extra dependencies that you find listed for syslinux:
[snip]
come directly from mtools ...


Yeah.  It looks like mtools uses X11 by default, which IMHO is
incorrect.  Instead it should have an option to turn X11 _on_,
rather than one for turning it _off_, as it currently does.


IMO it is a POLA violation for mtools to depend on X11 *at all*.

Instead of having an option, maybe the port should be split so that
mtools itself just provides the code to access FAT filesystems, and
(say) mtools-gui does the fancy display stuff.


mtools already supports WITHOUT_X11 so if you don't want the GUI  
stuff, you can build the port
without it. Personally, I think it makes more sense for mtools to be  
the full and complete representation

of the actual program.

If you would like to create a new port and call it mtools-without-gui  
and strip out all the X11 stuff, similar to

cvsup and cvsup-without-gui, I say go for it.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for potential ports maintainers

[Steven Kreuzer]

On Feb 27, 2009, at 10:17 AM, Steven Kreuzer wrote:



On Feb 27, 2009, at 6:03 AM, Lars Engels wrote:


Quoting Lars Engels :


Quoting Thomas Abthorpe :


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This topic came up in IRC, and I was encouraged to go out, and  
find some new

maintainers.

At any given time, approximately 20 - 25% of all ports are  
unmaintained. Not
all unmaintained ports need updating, but some do. That is where  
you folks

come in.


To find out which of your installed ports are unmaintained, I hacked
together a little script. Just run it and it will show all currently
unmaintained ports that you have installed.


The list ate the attachment, so here it is:

http://bsdpaste.bsdgroup.de/1099

--
Lars Engels
E-Mail: lars.eng...@0x20.net


You can also pull that list up by searching on freshports.org for  
ports with the maintainer set to po...@freebsd.org


http://www.freshports.org/search.php?stype=maintainer&method=match&query=ports%40freebsd.org&num=10&orderby=category&orderbyupdown=asc&search=Search

That search currently returns 4633 ports all waiting for someone to  
adopt them


Never mind. I read your script to fast. That returns every port that  
is currently unmaintained. Yours just returns the unmaintained ports  
you have installed.


Sorry about that.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for potential ports maintainers

[Steven Kreuzer]

On Feb 27, 2009, at 6:03 AM, Lars Engels wrote:


Quoting Lars Engels :


Quoting Thomas Abthorpe :


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This topic came up in IRC, and I was encouraged to go out, and  
find some new

maintainers.

At any given time, approximately 20 - 25% of all ports are  
unmaintained. Not
all unmaintained ports need updating, but some do. That is where  
you folks

come in.


To find out which of your installed ports are unmaintained, I hacked
together a little script. Just run it and it will show all currently
unmaintained ports that you have installed.


The list ate the attachment, so here it is:

http://bsdpaste.bsdgroup.de/1099

--
Lars Engels
E-Mail: lars.eng...@0x20.net


You can also pull that list up by searching on freshports.org for  
ports with the maintainer set to po...@freebsd.org


http://www.freshports.org/search.php?stype=maintainer&method=match&query=ports%40freebsd.org&num=10&orderby=category&orderbyupdown=asc&search=Search

That search currently returns 4633 ports all waiting for someone to  
adopt them


--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Port Request: gluster

[Steven Kreuzer]

On Feb 20, 2009, at 9:51 AM, Pathiakis, Paul wrote:


Hi,



I'd like to request that the gluster clustering/filesystem software be
ported and supported.  This looks to be a very simple, straightforward
and viable clustering solution which FreeBSD has always lacked.


This looks like a very interesting project. I might be able to take  
some time

over the weekend and create a port for this.

Out of curiosity, have you been using it in production? If so, can you  
describe your setup

and your experience with it?

Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: rt-3.8.1_5

[Steven Kreuzer]

On Feb 5, 2009, at 11:42 AM, Boris Samorodov wrote:


Steven Kreuzer  writes:


Let me take a
closer look and hopefully I can get both
of these patches applied today.


You need only one last patch since it contains all needed changes
for current port.


Sorry, I mean your patch and the patch for PR ports/130869

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: rt-3.8.1_5

[Steven Kreuzer]

On Feb 4, 2009, at 12:45 AM, Boris Samorodov wrote:


Chris Jones  writes:


I'm just curious if you will be updating the 3.8 branch to 3.8.2? I
noticed that there are quite a few fixes in 3.8.2.


You may try this an submit a followup to the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131167


WBR
--  
Boris Samorodov (bsam)

Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve




I just looked at the patch and submitted a followup. Its incomplete  
because pkg-plist also needs to be updated. I am currently waiting for  
wxs@ to commit ports/130869 for me and then I will bring the port up  
to date in a day or so.


--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: rt-3.8.1_5

[Steven Kreuzer]

On Feb 5, 2009, at 11:18 AM, Boris Samorodov wrote:


Steven Kreuzer  writes:

On Feb 4, 2009, at 12:45 AM, Boris Samorodov wrote:

Chris Jones  writes:


I'm just curious if you will be updating the 3.8 branch to 3.8.2? I
noticed that there are quite a few fixes in 3.8.2.


You may try this an submit a followup to the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131167


I just looked at the patch and submitted a followup. Its incomplete
because pkg-plist also needs to be updated. I am currently waiting  
for

wxs@ to commit ports/130869 for me and then I will bring the port up
to date in a day or so.


You were a little bit late. ;-) I've submitted a revised patch
to the PR.


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org 
"


Wow. Thanks. I grabbed the original patch when the PR was first opened  
and just got around

to looking at it. I didn't realize the PR was updated by you

I just eyeballed your patch and so far it looks good. Let me take a  
closer look and hopefully I can get both

of these patches applied today.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: RT 3.8?

[Steven Kreuzer]

On Jan 21, 2009, at 4:34 PM, Arnold Cavazos Jr. wrote:




I am trying to install the rt38 port in the tree on a fresh 7.1-STABLE
build.  The Makefile's id is:

# $FreeBSD: ports/www/rt38/Makefile,v 1.6 2009/01/08 16:50:17 pav  
Exp $



a "/usr/local/sbin/rt-setup-database --dba root --action init"
yeilds the following error:

DBD::mysql::st execute failed: Table 'Attachments' already exists at
/usr/local/lib/perl5/site_perl/5.8.8/RT/Handle.pm line 470.

Any ideas as to where I should look to solve this?

--
Arnold Cavazos, Jr.


Hi Arnold-

This is a known issue documented in PR ports/130425

I recently inherited maintenance of this port and I currently have two  
patches
that are being reviewed by ports committers that fix other problems in  
the port.


Once those get checked in, which I was told *should* be done today, I  
will fix the

issue you are having. (I have patches ready to go)

Sorry for any inconvenience this may have caused you. This should be  
fixed

in the very near future.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: RT 3.8?

[Steven Kreuzer]

On Dec 15, 2008, at 2:32 PM, Philip M. Gollucci wrote:


Wesley Shields wrote:
I've also added him as CC to this reply so he can speak up if he  
has any

more information to add.
I've gotten several comments (esp recently).  My first thought is to  
commit it as is and let the PRs come it.  Several people have been  
using the prototype in production for a while now.


I have been running this port in both production with roughly 15  
people using it. (This number of users should grown to around 40 in  
the near future).
The production version has been extremely reliable and I would say  
that it ready to be added into the ports tree.


I am willing to assist with any PRs that open up regarding this port.  
If you would like, put me down as the maintainer until your workload  
dies down and then you can

take maintainership back from me.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: A place to upload distfiles?

[Steven Kreuzer]

On Nov 24, 2008, at 1:58 PM, [EMAIL PROTECTED] wrote:

I maintain a port for which the vendor provided me a customized  
distfile.  They don't have it available for download from their  
site, so I need to find a home for it.  Does the FreeBSD Project or  
Foundation provide hosting space for such cases or do I need to find  
my own space?


I can provide a mirror for the tarball on exit2shell.com. Let me know  
if you are still looking for a place.


Steven Kreuzer
http://www.exit2shell.com/~skreuzer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: p5-GD-SecurityImage-1.66,1

[Steven Kreuzer]

On Nov 7, 2008, at 12:12 PM, Benat Dagorret wrote:



Hello,

I'm writing a webapp that uses the Catalyst::Plugin::Captcha module,
which depends on GD::SecurityImage.

As far as I understand the GD::SecurityImage documentation, using the
ImageMagick backend is optional : the module needs to be loaded only  
if

GD::SecurityImage is "required" by other modules.

So, my question is whether it would be possible to include an option  
in
the GD::SecurityImage Makefile to allow the user build the port  
without

ImageMagick. Or am I missing a way to do that with the current port ?
(I use FreeBSD RELEASE 7.0).

Thanks for the great work to the FreeBSD developers and maintainers.

Regards.

--
Benat Dagorret
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED] 
"


Try out the attached patch and let me know how it works for you

Steven Kreuzer
http://www.exit2shell.com/~skreuzer



p5-GD-SecurityImage.patch
Description: Binary data


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Request Tracker 3.8.1

[Steven Kreuzer]

I created a new port for version 3.8.1 of Request Tracker.

Before I submit a PR and get it added into svn, I want to see if I can  
find some people to help test it out since RT is a fairly complex  
application. I have had it up and running for a little over a day and  
so far I seems to be working as expected.


Also, I stripped out the MULTIPLE_INSTANCES support, mainly because I  
don't use it and needed to get rt38 up and running as quickly as  
possible. As time permits, I will add it back it, but its not as  
simple as it seems because, mainly because the patches no longer  
cleanly apply.


You can find the shell archive at http://www.exit2shell.com/~skreuzer/rt38.shar

Thanks

SK
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Maintainer Timeout on ports/125250

[Steven Kreuzer]

Hi-

I opened up a PR to update games/robotfindskitten a little over a month
ago and I have not heard from the maintainer.

Would it be possible to get a timeout on that PR and have the patch commited?

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125250

Thanks

-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Close PR ports/122823

[Steven Kreuzer]

Hi-

Roughly 2 months ago I submitted a PR with a patch to update p5-Crypt-PassGen.
It looks like tobaz@ updated the port but the ticket has not be updated.

Anyway, I think PR ports/122823 can be marked as resolved.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD unmaintained ports which are currently marked broken

[Steven Kreuzer]

On Wed, Apr 30, 2008 at 10:27:14AM -0400, Vivek Khera wrote:
> 
> On Apr 30, 2008, at 4:22 AM, Philip M. Gollucci wrote:
> 
> >> portname:   www/rt3
> 
> seriously, who still uses RT 3.0?  RT 3.6 is current, and the beta of  
> the next major version just came out.

And RT 3.6.6 is available in ports (www/rt36). I personally think rt3
should be marked for deletion. 3.0.12 was the last release from the 3.0
series and was released close to 4 years ago without an update to that branch
since then.

However, since someone stepped up to maintain it, I guess if they can fix the
port so it no longer uses a random gid, might as well keep it around.

-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Building Ruby Ports

[Steven Kreuzer]

Greetings-

I am currently in the process of building a FreeBSD port for a Ruby on Rails
application and I have run into an issue I am hoping someone can help
provide me a solution for.

The port had a couple of dependencies on Ruby gems that no port currently
exists for, so I created ports and opened PRs for them.

However, the application I am currently building a port for requires
ruby-gettext 1.9.0. The port that currently exists in cvs is 1.10.0 and the
application refuses to run with that version. I believe this is for
compatibility with the gettextilize plugin

I am currently working around this issue by installing the gem by hand
(gem install -v 1.9.0)

Right now it looks like my only course of action is to create a port for
this and keep it at that version, which seems kinda sloppy. I am curious if
anyone has a cleaner solution. I am all ears.

Thanks

-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: www/links port fails to build with DirectFB library

[Steven Kreuzer]

Hey Adam-

I think the best course of action would be for you to correct the offending
lines in the Makefile and then open up a PR with the patch. After the
maintainer of the port approves the patch, it can be commited to cvs.

Thanks for catching this.

SK

On Tue, Apr 15, 2008 at 12:38:50AM -0400, Adam Martin wrote:
> To whom it might concern,
> 
>   I've started a rebuild of all ports, on my home system, and links  
> port failed, with the libdirectfb.  I have fixed it -- the dependancy  
> line with the "libdirectfb" entry should be changed to "directfb".
> 
> Line 51 (as of my last portsnap fetch; portsnap update, a few minutes  
> ago) of /usr/ports/www/links/Makefile should read:
> 
> LIB_DEPENDS+=   directfb:${PORTSDIR}/devel/directfb
> 
> Instead it reads:
> 
> LIB_DEPENDS+=   libdirectfb:${PORTSDIR}/devel/directfb
> 
> 
> Hopefully this hasn't affected too many people, and hopefully I'm not  
> pestering the wrong people.
> 
> Regards,
> 
> --
> ADAM David Alan Martin
> 
> Filesystem and Storage Lab, SUNY Stony Brook
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ports/121370

[Steven Kreuzer]

Can you take a look at that patch and commit it. The PR is
3 weeks old.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/121370

Many Thanks
-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Installing a shell script

[Steven Kreuzer]

Greetings-

I am in the process of updating a port to the latest version (dns/dnsperf)
and I ran into an issue I was able to work around but I want to see if
there is a nicer way to do it.

One of the differences between the version in ports and the current version
is the addition of a shell script called resperf-report. If I simply use stock
install method, I end up with the following error:

strip: /usr/local/bin/resperf-report: File format not recognized
install: wait: No such file or directory
*** Error code 70

So, to work around this what I ended up doing is basically installing the
binaries and man pages by hand:

-PLIST_FILES=   bin/dnsperf bin/resperf
+PLIST_FILES=   bin/dnsperf bin/resperf bin/resperf-report
 MAN1=  dnsperf.1 resperf.1

  +do-install:
  +   ${INSTALL} ${WRKSRC}/dnsperf ${PREFIX}/bin
  +   ${INSTALL} ${WRKSRC}/resperf ${PREFIX}/bin
  +   ${INSTALL_SCRIPT} ${WRKSRC}/resperf-report ${PREFIX}/bin
  +.for MAN in ${MAN1}
  +   ${INSTALL_MAN} ${WRKSRC}/${MAN} ${PREFIX}/man/man1
  +.endfor
  +
   .include 

Is there a better way to do this? Can I someone
set a flag to tell the stock do-install to not strip the resperf-report
when doing an install?

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: KeePassX-0.2.2_2

[Steven Kreuzer]

On Tue, Mar 18, 2008 at 10:53:24AM -0500, Matt wrote:
> Hello.
> 
> It looks like the KeePassX folks have recently updated to the 0.3.x
> branch.  I've looked at trying to build a local port from the updated
> version but it fails with multiple build errors (I'm running
> 7.0-RELEASE and all qt4 ports are at version 4.3.4).  Can someone take
> a look and see if there are obvious changes needed to make it compile?
> 
> Thanks,
> Matt
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Cut and paste the errors you are getting. It might be something fairly trivial,
or it might be related to a specific setting on your machine.
-- 
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Renaming a Port

[Steven Kreuzer]

Greetings-

I am the maintainer of the mysqltoolkit port. Recently, the project  
underwent a name change and is now maatkit.
The application has also undergone some updates so I would like to  
update the port to the latest version.


While I am sure I am not the first person to ever have this problem,  
its a new one for me so I figured I would ping the

list and see what people have to say.

Is this the best way to go about this?

1) Have someone mark mysqltoolkit as DEPRECATED
2) Take my port, rename it to maatkit and make the changes necessary  
to the Makefile, etc

3) Submit the port and have it checked in.

However, do I need to provide some sort of migration path for existing  
users of mysqltoolkit? Is that even possible?

If so, how do I go about doing it.

Any advice or guidance is greatly appreciated.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Limitations of Ports System

[Steven Kreuzer]

This thread was called "results of ports re-engineering survey" but I  
figured I would start a new thread.


On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote:



We *know* it can be done better.  We *know* the scaling limits of  
the current system, and most of us are completely amazed it even  
still works.


If y'all want to make a difference, concepts and ideas we have  
plenty of.  Code talks.


Out of curiosity, are any of these shortcomings documented anywhere? I  
have been using ports on my home machine for a long time and I've never
had any problems with it. I assume the issues come into play when you  
work with multiple systems you are trying to keep in sync, etc.


I would be interested in reading about some of the limitations people  
have run into when using ports.


--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Upcoming changes to ifstated port

[Steven Kreuzer]

Greetings-

I just wanted to give everyone who is using the port of ifstated a  
heads up for some changes that I am going to make in the near future.  
Please don't hesitate to post any questions or comments. All feedback  
is appreciated.


I recently received a patch from Artemiev Igor (see ports/29 for  
all the details) that I am currently evaluating. I plan on merging  
his patch with files/patch-ifstated.c


In addition, I plan to change the VERSION from 20050505 to 3.7, since  
the code came from OpenBSD 3.7. When I make updates to the port in  
the future, the version number is going to be the version of OpenBSD  
it came from. Personally, I think that makes a little more sense then  
using a date.


Finally, I need your help:

1) If you are running ifstated and would be able to test an updated  
version ported from OpenBSD 4.1 in a non production environment,  
please contact me. I would like to make sure there is no regression  
since this is going to be somewhat of a major update.


2) If you can help host the 16K source tarball for version 3.7,  
please grab it from http://skreuzer.f2o.org/mirror/ifstated/ 
ifstated-3.7.tar.gz and send me the url and I will update MASTER_SITES


Thanks,

SK
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD ports you maintain which are out of date

[Steven Kreuzer]

On Mar 20, 2007, at 1:33 PM, [EMAIL PROTECTED] wrote:


Dear port maintainer,

The portscout new distfile checker has detected that one or more of  
your

ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,  
you can

safely ignore the entry.

You will not be e-mailed again for any of the port/version  
combinations

below.

Full details can be found at the following URL:
http://beta.inerd.com/portscout/[EMAIL PROTECTED]


Port| Current version |  
New version
+- 
+
devel/p5-Getopt-Mixed   | 1.008   |  
1.09
+- 
+
net-mgmt/nrpe   | 1.9 |  
2.8b1
+- 
+


nrpe is listed as being out of date. However, for some reason, there  
are two versions of nrpe in ports: nrpe at v1.9, nrpe2 at v2.7 (2.7.1  
is the latest stable version, so the nrpe2 port is out of date)
Would it make sense to remove the port for nrpe which is currently  
unmaintained and rename nrpe2, which is maintained to just nrpe?


Also, while p5-Getopt-Mixed is currently out of date, the author has  
listed the module as obsolete on the CPAN page (Its been replaced by  
Getopt::Long). I submitted a PR with a patch to update it 1.09  
earlier today, but perhaps it should be considered for removal from  
the tree since it has no port maintainer, and the module is no longer  
maintained as well. I spoke privately with Anton Berezin (who is  
assigned to the PR) privately and we both agree that it would make  
sense to update it to 1.09, but at the same time, deprecate and mark  
it for deletion in the ports collection.


Figured I would post this to the list to see if anyone has any strong  
feelings against it.

The PR can be found at http://www.freebsd.org/cgi/query-pr.cgi?pr=110595

SK

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

p5-Nagios-Plugin Update

[Steven Kreuzer]

Greetings-

Nagios::Plugin 0.15 was recently released and I made some changes to  
net-mgmt/p5-Nagios-Plugin to bump the version from 0.14 to 0.15.


Changes in a nutshell:

* Now depends on Class::Accessor and Params::Validate
* Changed MASTER_SITE_SUBDIR from Ton Voon to Gavin Carr
* Changed COMMENT to blurb from the CPAN page

Thanks,

Steven



p5-Nagios-Plugin.diff
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"