Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes

The following reply was made to PR ports/146626; it has been noted by GNATS. From: ch...@officialunix.com To: bug-follo...@freebsd.org, am...@raisa.eu.org Cc: Subject: Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes Date: Sun, 16 May 2010 08:03:14 -0500 Thi

Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes

The following reply was made to PR ports/146626; it has been noted by GNATS. From: ch...@officialunix.com To: bug-follo...@freebsd.org Cc: Subject: Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes Date: Sun, 16 May 2010 08:57:24 -0500 This patch can be approv

Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes

The following reply was made to PR ports/146626; it has been noted by GNATS. From: ch...@officialunix.com To: bug-follo...@freebsd.org Cc: Subject: Re: ports/146626: [PATCH] print/hplip3 gzip files curruption with USE_DOS2UNIX=yes Date: Sun, 16 May 2010 08:59:02 -0500 Yeap, the patch is fine

security/openssh-portable maintainer

port, my skill set is not high enough to do it at least without some help. Failing that can someone help me with the freebed patches in the files dir to patch ok on openssh 5.6p1. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org

DRI build failing on 8.1-STABLE

; has no member named 'bindToTextureTargets' glcontextmodes.c:543: error: '__GLcontextModes' has no member named 'yInverted' glcontextmodes.c:543: error: '__GLcontextModes' has no member named 'yInverted' gmake[2]: *** [glcontextmodes.

Re: What about Firefox 11?

On 3/22/12, Jerry wrote: > On Thu, 22 Mar 2012 18:00:15 +0100 > Florian Smeets articulated: > >> Yes, after the ports freeze. We decided to stay with firefox 10.0.x >> for now and update www/firefox to 11 after the FreeBSD 8.3 release is >> out. > > Considering that Firefox is in a race to get to

graphics/mesa-demos fails to build

-STABLE, amd64. Also, I had to manually download MesaLib-7.6.1.tar.bz2 from the freedesktop.org site since there seems to be an MD5 and SHA256 checksum error with the mirror sites. The MesaDemos-7.6.1.tar.bz2 file seems to be fine, however. Any help here would greatly b

Re: graphics/mesa-demos fails to build

On Tue, Mar 22, 2011 at 10:49 AM, Chris wrote: > Hello, > > I'm seeing this when I try to build from ports: > > > /var/tmp//ccNBgj1B.o(.text+0x1c5): In function `main': > : undefined reference to `glXCreateGLXPixmapMESA' > gmake[2]: *** [glxpixmap] Error 1 >

Re: Limitations of Ports System

e to watch it but in addition I always like to compile my own binaries etc. rather than using something thats precompiled and limited to how the compiler compiled it. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listi

gnutls-2.2.2 segfaults

with gnutls-2.2.2. So my question is does anyone not have this problem? or they have had this problem but know how ti fix it without downgrading? I emailed both port maitainers for libgcrypt and gnutls and neither responded. Thanks Chris ___ freebsd

python support appears broken in the ports trree

Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 519768 Node Kind: directory Schedule: normal Last Changed Author: pizzamig Last Changed Rev: 519768 Last Changed Date: 2019-12-10 09:39:01 -0800 (Tue, 10 Dec 2019) Thank you for all your time, and consideration. --Chris __

Re: python support appears broken in the ports trree

On Tue, 10 Dec 2019 16:53:38 -0800 s...@troutmask.apl.washington.edu said Thank you very much for taking the time to reply. On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote: > I struggled all day yesterday with various ports barfing with similar > python messages. So today

Re: python support appears broken in the ports trree

On Wed, 11 Dec 2019 06:21:29 +0100 Jan Beich jbe...@freebsd.org said Chris writes: > I struggled all day yesterday with various ports barfing with similar > python messages. So today I blew everything off the disk, and started > from scratch. Which only repeats what happened yest

What is the actual syntax used to FLAVOR ports?

how to flavor, and build python flavors. But what of Perl? make FLAVOR=perl2.8. Nope. How about make FLAVOR=p5-28, and so it goes... Does there exist a definitive list of flavors? It'd also be valuable for defining defaults in make.conf(5) Thanks! --

Re: What is the actual syntax used to FLAVOR ports?

On Sat, 8 Feb 2020 21:44:35 -0800 Kevin Oberman rkober...@gmail.com said On Sat, Feb 8, 2020 at 1:27 PM Chris wrote: > OK I know FLAVOR is an evolving concept. But I can not find > the FLAVOR documentation. Only references in the porters > handbook. What I think needs to be availa

Re: What is the actual syntax used to FLAVOR ports?

On Tue, 11 Feb 2020 09:45:53 +0100 Mathieu Arnold m...@freebsd.org said On Mon, Feb 10, 2020 at 09:02:34PM -0500, Ernie Luzar wrote: > Kevin Oberman wrote: > > On Sat, Feb 8, 2020 at 1:27 PM Chris wrote: > > > > > OK I know FLAVOR is an evolving concept. But I can no

llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified.

stop it. :) Thanks! --Chris ___ 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: llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified.

On Thu, 27 Feb 2020 19:52:23 + Brooks Davis bro...@freebsd.org said On Thu, Feb 27, 2020 at 08:44:59AM -0800, Chris wrote: > I'm testing modifications of ports I maintain in > a jail. I have nothing in make.conf(5) except > DEVELOPER=true > But I get messages regarding pyt

Re: llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified.

On Thu, 27 Feb 2020 21:46:12 +0100 Mathieu Arnold m...@freebsd.org said On Thu, Feb 27, 2020 at 07:52:23PM +, Brooks Davis wrote: > On Thu, Feb 27, 2020 at 08:44:59AM -0800, Chris wrote: > > I'm testing modifications of ports I maintain in > > a jail. I have nothing in

Re: About protocols in openssl

ntation for your Makefile. I'll probably get a lot of grief for saying all this. So I'll share those details off list. So as not to give instructions on how to subvert the ports system. ;) HTH --Chris FreeBSD 14.0-FUTURE #0.000 cray256 --WjW

Re: New bacula release

;stype=name&method=match&num=100&deleted=excludedeleted&orderby=category&orderbyupdown=asc&search=Search indicates bacula is already at 9.6.2. :) HTH --Chris FreeBSD 14.0-FUTURE #0.000 cray256 ___ freebsd-ports@freebsd.org mail

Re: When to use TMPPLIST instead of pkg-plist?

ause of so many variables, that TMPPLIST isn't always correct. So to rely on it, as Mathieu stated, would be *bad* policy. As memory serves; it's also the product of make make-plist. Hope that helps in clarification. :) --Chris FreeBSD 14.0-

Re: When to use TMPPLIST instead of pkg-plist?

On Sat, 29 Feb 2020 19:44:40 + Bob Eager r...@tavi.co.uk said On Sat, 29 Feb 2020 11:29:18 -0800 Chris wrote: > TMPPLIST is an artifact of the QA process when making a port. It is > used for comparison to what you, as a port maintainer claim is the > pkg-plist, and whats found t

Re: When to use TMPPLIST instead of pkg-plist?

0%, and it's output is subject to scrutiny by the maintainer. --Chris Theron ___ 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: claws-mail search a new home

r hands (Maintain it). :) Thanks for your time, and consideration! --Chris FreeBSD 14.0-FUTURE #0.000 cray256 Cheers Jochen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any ma

7 month old bug squashed. Please commit

Hi I just picked up mail/claws-mail, and discovered a 7 month old bug. I resolved the problem, and created a patch to fix it. I wouldn't normally say anything except that it's such an old bug. pr: 239659 Thanks! --Chris ___ fre

pkg: how to retrieve the messages ports emit after install?

file. But the new graphics drivers don't allow that sort of thing (graphics vs text mode). So I was left with mostly gibberish. I need to get that information back. I just guessed that pkg message might do it. But no joy. How can I retrieve that information? Thanks

Re: pkg: how to retrieve the messages ports emit after install?

On Wed, 18 Mar 2020 08:27:29 + Bob Eager r...@tavi.co.uk said On Tue, 17 Mar 2020 23:28:49 -0700 Chris wrote: > OK I'm a by ports make install as a rule. But I needed to > spin up a box quickly, and decided to use pkg(8). xorg, > and another port (package) I installe

Re: pkg: how to retrieve the messages ports emit after install?

On Wed, 18 Mar 2020 14:20:05 + Bob Eager r...@tavi.co.uk said On Wed, 18 Mar 2020 07:18:40 -0700 Chris wrote: > > > OK I'm a by ports make install as a rule. But I needed to > > > spin up a box quickly, and decided to use pkg(8). xorg, > > > and another po

Re: pkg: how to retrieve the messages ports emit after install?

On Wed, 18 Mar 2020 17:31:53 +0100 Mateusz Piotrowski mpp...@gmail.com said On 3/18/20 5:20 PM, Chris wrote: > IMHO this should be added to the pkg(8) man page. Maybe the EXAMPLES > section? https://github.com/freebsd/pkg/pull/1819 Cheers, Mateusz WOW! That was fast. Tha

drmn0: This code is obsolete abandonware. Install the graphics/drm-legacy-kmod pkg

#x27;kld_list="/boot/modules/i915kms.ko">>/etc/rc.conf and bounce the box. This drm problem also seems to be interfering with my ability to run xfce4 (of xorg) properly. What do I need to do? Thanks! --Chris ___ freebsd-ports@f

Re: mail/mailman v3?

sn't that sort of redundant? I mean; have you ever seen a kitty that _wasn't_ *hyper* ? :) --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail

Re: mail/mailman v3?

and continue using mailman2 on it (I might help with this part)? <https://github.com/naftaliharris/tauthon> In sentiment I am inline with your thoughts as well. Would it be a worthy project to create a mailman(2)-lts port? I'd be fully up for helping, and or crea

Re: mail/mailman v3?

On Thu, 30 Apr 2020 02:03:20 +0200 Matthias Andree matthias.and...@gmx.de said Am 28.04.20 um 22:02 schrieb Chris: > In sentiment I am inline with your thoughts as well. > Would it be a worthy project to create a mailman(2)-lts port? > I'd be fully up for helping, and or crea

Re: Wrong Ports-OSVERSION in jails

ight help: https://www.freebsd.org/doc/en/books/porters-handbook/versions-12.html just change versions-12 to versions-13 for 13* Annoying, isn't it? :-) HTH --Chris When i connect into the jail, the Tree is available and ready to use with this entry in /etc/make.conf: KDIRPREFIX=/tmp

Re: Poudriere - Compile ALL Ports

On Tue, 5 May 2020 22:38:36 +0200 Leander Schaefer i...@netocean.de said Hello, I have been dealing with Poudriere for quite a while and one of the most issues I have is, that I have ports which won't compile along with another. Reason is mostly something like: pkg-static: ImageMagick7-7.0.

Re: Poudriere - Compile ALL Ports

On Thu, 7 May 2020 20:39:41 +0200 Leander Schaefer i...@netocean.de said Hello Chris, Hello List, I have checked out ports-mgmt/synth unfortunately it would be a massive downgrade compared to poudriere. Does anyone have the right clue about how the FreeBSD package managment team provides a

Re: Are broken ports retested before performing scheduled removal?

tp://www2u.biglobe.ne.jp/~hsaka/distfiles/oneko-2.0b-bsd0.2.tar.gz oneko-2.0b-bsd0.2.tar.gz 100% of 21 kB 159 kBps 00m00s ===> Fetching all distfiles required by oneko-2.0b_5 for building As you can see, oneko-2.0b-tip1.7.tar.gz failed, and re

Re: Conflict on very first port (xorg) on rpi3

g. > > Try disabling DOCS option on devel/llvm80 for now. > > I've opened a PR to track this issue: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246487 > Wish I'd known it was only the DOCS option! Too late now, sphinx18 is deinstalled and llvm80

Re: Gratuitous port splitting (was: Port Avidemux)

to propose making a meta-port called "avidemux" with options that pull only what's required to create a functional port. But decided to wait till I got through all my mail first, in case someone as (at least) as smart as I am beat me to the proposal. ;-) --Chris Cheers, Freddi

Re: Porting Practice

pting a port :-) HTH! --Chris The documentation for (diff -u) says "To create a suitable diff for a single patch, copy the file that needs patching to something.orig, save the changes to something and then create the patch:" % diff -u something.orig something > something.diff Im n

Re: Porting Practice

On Sun, 5 Jul 2020 13:07:53 +1200 Jonathan Chen j...@chen.org.nz said On Sun, 5 Jul 2020 at 12:47, Brandon helsley wrote: > > I have gotten a couple of emails from portscout about ports that need updated > and maintained. Before I go about updating and maintaining these ports I wanted > to do

Re: Gracefully killing and restarting a port build....

eading, apologies if it's a dumb question, Not at all. :-) I usually leverage multiple terminals, and simply dedicate one to the/a build session. So simply issuing a ^C to that terminal sends an INTR to the parent, and children. I've experienced no problems restarting the process (build)

Re: Gracefully killing and restarting a port build....

in. You'll want to add sh (/bin/sh) to the list of potential "victims" in your kill list. :-) --Chris Thanks for your help bob prohaska ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/l

Re: [HEADS UP] Planned deprecation of portsnap

also doesn't work offline which git does. With git, you can also easily add the history by running "git pull --unshallow" * This migration away from portsnap fits well with the planned migration to git. Please tell me that this doesn't mean a [HEADS UP] Planned deprecati

Re: [HEADS UP] Planned deprecation of portsnap

respond, Kurt! :-) This is very bad news for us. I can make so many arguments against dropping subversion. It's really not (needn't be) a matter of either/or. Thanks again, Kurt. Even if it wasn't what I wanted to hear. --Chris

ln -s python3 python2 && ln -s python37 python27?

his is quite maddening. There must be a way out. No? Thank you in advance for any, and all clues to salvation! :-) --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send a

Re: [HEADS UP] Planned deprecation of portsnap

Respectfully, Robert Huff --Chris -- Get it right: _physical_ distancing; _social_ cohesion ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe,

Re: pkg feature request

rmation to upgrade the ports tree in one go without needing to manually run svn. +1 Yes, please. Even if only the src rev the packages were built from. Cobbling up a script to capture the output of pkg srcrev/revno would be trivial to pass to svn up/co. :-) -- Mike Clarke [1] http:

Re: Bind master error on empty.db

.82, 0.063-2--H*UA:2.3654.0.3.2.82, 0.089-1--sample, 0.093-4--ignoring, 0.093-2--H*F:D*kreme.com, 0.116-+--error, 0.124-1--rushed, 0.126-+--etc BAYES_ST0.987-1--HX-Envelope-From:sk:kremels Looks to me that it (empty.db) may not be properly listed in the ports pkg-plist file.

Re: STOP rust!

on brake press to bend paper clips is stupid, and unreasonable. It's a hard point to argue when confronted with the fact that using a multi-gig builder to build a several-k library/program is just impractical, and unreasonable. Thanks for listening. :-) --Chris

What's the procedure to rename a port?

and as a result, it's potential popularity. Would better expressed as: tkrcs. How to proceed, where the ports infrastructure is concerned? Thanks! --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-

Re: Bug 251656

it's gets assigned, and addressed more promptly. :-)00 FYI ideally, the topic should have read: x11-servers/xorg-server: segmentation fault Seems insignificant. But the colon is significant. HTH --Chris ___ freebsd-ports@freebsd.org mailing

Re: portmaster new development

/bin/sh based version. The lovely thing about options, is that *everyone* gets to have one. The more the merrier! :-) @Stefan Really excited to hear about your LUA version of portmaster. Thanks! :-) --Chris Regards, STefan ___ fre

Re: How to fix/patch hardcoded values

On 2020-12-29 00:07, Mathieu Arnold wrote: On Sun, Dec 27, 2020 at 09:58:13PM +, Nuno Teixeira wrote: Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config in /usr/local/etc inst

Re: TeXLive 2020 Update

d any patches you may have already. It will also initiate conversation with any/all related individuals. Those already maintaining ports are already subscribed to this list, and will receive reports of your work here (bugzilla posts to this and other related lists). I hope t

Re: OpenSource app Simple Diary

: - GTK+3 x11-toolkits/gtk30/ ? - webkit2gtk-4.0 www/webkit2-gtk3/ - md4c and md4c-html - Not quite sure what these might translate to. --Chris Do we have them in our ports collection in head? I couldn't see them, at least not with the above names exactly. Thanks matthias S

GitHub: size of remote file is not known

a problem for those attempting to build ports on a system with limited resources -- especially during a meta-port build, and even more so for newcomers. Is anyone familiar with why this is so? I'd like to change this. Thanks! --Chris ___ freebsd-po

Re: GitHub: size of remote file is not known

On 2021-01-05 03:49, Mathieu Arnold wrote: On Mon, Jan 04, 2021 at 08:04:32PM -0800, Chris wrote: I don't use Github. So I'm not familiar with their service(s). But ports using source fetched from them always return: size of remote file is not known Is it that their servers simply

Can we create an (only for) ARCHS meta-category?

ports that were known to work on archs *besides* x86/amd64. They'd know what to anticipate, if they're looking to start (or continue) using FreeBSD. This seems especially important where meta-ports are concerned. Thanks! :-) --Chris ___ freeb

Re: Handling directory ownership in pkg-plist

On 2021-02-06 13:34, Chris Rees wrote: Hi all, Resurrecting audio/ampache-resurrect, and I have @owner www/@group www above all of the WWWDIR files, and they are correctly owned. However, the directories under it are all still owned by root:wheel, and if I explicitly add them all with @dir

Re: Handling directory ownership in pkg-plist

On 2021-02-07 02:18, Chris Rees wrote: Hi Chris, Thamks for the reply. On 7 February 2021 03:57:03 GMT, Chris wrote: On 2021-02-06 13:34, Chris Rees wrote: Hi all, Resurrecting audio/ampache-resurrect, and I have @owner www/@group www above all of the WWWDIR files, and they are correctly

Re: Handling directory ownership in pkg-plist

On 2021-02-07 02:18, Chris Rees wrote: Hi Chris, Thamks for the reply. On 7 February 2021 03:57:03 GMT, Chris wrote: On 2021-02-06 13:34, Chris Rees wrote: Hi all, Resurrecting audio/ampache-resurrect, and I have @owner www/@group www above all of the WWWDIR files, and they are correctly

Re: Handling directory ownership in pkg-plist

On 2021-02-07 12:19, Chris Rees wrote: Afternoon, On 7 February 2021 19:05:26 GMT, Chris wrote: On 2021-02-07 02:18, Chris Rees wrote: Hi Chris, Thamks for the reply. On 7 February 2021 03:57:03 GMT, Chris wrote: On 2021-02-06 13:34, Chris Rees wrote: Hi all, Resurrecting audio

Re: Creating port from pre-built package

I'm not sure how to properly create a port from a pre-built package. Does anyone have any non-xkcd pointers[1]? [1]: https://xkcd.com/138/ Thanks, --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-p

Re: Creating port from pre-built package

On 2021-02-11 09:08, Shawn Webb wrote: On Thu, Feb 11, 2021 at 09:03:19AM -0800, Chris wrote: On 2021-02-11 08:26, Shawn Webb wrote: > Hey all, > > The Splunk universal forwarder for FreeBSD is distributed as a package > tarball that you can use `pkg add` on. I'm in a position

Re: bogus warning from pkg

On 2021-02-15 22:20, Steve Kargl wrote: On Mon, Feb 15, 2021 at 08:18:13PM -0800, Mark Millard wrote: Steve Kargl sgk at troutmask.apl.washington.edu wrote on Tue Feb 16 02:14:06 UTC 2021 : > On Mon, Feb 15, 2021 at 05:10:54PM -0800, Mark Millard via freebsd-ports wrote: > > Steve Kargl sgk at

maintainer seeks available committer

No this isn't intended for the personal ads. ;-) I've got a couple of PRs that have been hanging for awhile that should be ready to commit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253240 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252257 Thanks! :-

When did pkg(8) drop support for 12-STABLE?

e any way to disable pkg completely. So I can simply build ports, rather than packages? maybe a WITH_PKG=false USE_PKG=false or something else? Thanks in advance for any enlightenment. --Chris ___ freebsd-ports@freebsd.org mailing list

Re: When did pkg(8) drop support for 12-STABLE?

On 2021-02-23 14:58, @lbutlr wrote: On 23 Feb 2021, at 13:26, Chris wrote: OK On a virgin 12 stable install. The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I am not sure what build you mean by "12-STABLE" It was from a 12-STABLE usb stick (probably

Re: When did pkg(8) drop support for 12-STABLE?

On 2021-02-23 16:04, Mark Millard wrote: Chris portmaster at bsdforge.com wrote on Tue Feb 23 23:31:09 UTC 2021 : On 2021-02-23 14:58, @lbutlr wrote: > On 23 Feb 2021, at 13:26, Chris wrote: >> OK On a virgin 12 stable install. > > The current release is 12.2-RELEASE. 12.0-RE

Re: When did pkg(8) drop support for 12-STABLE?

On 2021-02-23 18:25, Jonathan Chen wrote: On Wed, 24 Feb 2021 at 15:00, Chris wrote: On 2021-02-23 16:04, Mark Millard wrote: > Chris portmaster at bsdforge.com wrote on > Tue Feb 23 23:31:09 UTC 2021 : > >> On 2021-02-23 14:58, @lbutlr wrote: >> > On 23 Feb 2021

Re: When did pkg(8) drop support for 12-STABLE?

On 2021-02-24 00:56, @lbutlr wrote: On 23 Feb 2021, at 16:31, Chris wrote: It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, save building up to 12.2? It sounds like the version you want is -RELEASE, not -STABLE. Yep. Think of -STABLE as "We are still worki

Re: www/joomla3 is no longer in the FreeBSD pkg repo

On 2021-03-04 00:50, Patrick M. Hausen wrote: Hi all, Am 04.03.2021 um 02:17 schrieb Chris Rees : The problem is, that although the php80 flavour does not depend on pecl-pdflib, the default flavour does, which means that the package will not be built as it you have to agree to pecl-pdflib&#

Re: www/joomla3 is no longer in the FreeBSD pkg repo

On 2021-03-04 08:39, Chris Rees wrote: On 04/03/2021 16:16, Chris wrote: On 2021-03-04 00:50, Patrick M. Hausen wrote: Hi all, Am 04.03.2021 um 02:17 schrieb Chris Rees : The problem is, that although the php80 flavour does not depend on pecl-pdflib, the default flavour does, which means

comitter please

I have patch in a pr(1) that should be ready for commit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252257 Thanks! :-) --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe

Re: Python 2.7 removal outline

nsider our opinions on such matters? Is it just me? Or is there a gross disconnect here? Maintainers need a Forum where their views on ports matters get some semblance of credence. Hell. I maintain some 160 ports. That's got to be worth *somethi

Re: Python 2.7 removal outline

n for such large-sweeping changes? IMHO this will give portmgr@ the opportunity to get caught up, and perhaps get some assistance -- maybe we all come up with an idea that saves _everyones_ bacon. :-) Thanks for the thoughtful reply. --Chris ___ fre

Re: Python 2.7 removal outline

relevant. I'd not heard of it either, but from looking in ports/Mk/ it seems to be a way of modifying port builds. As I understand it. It allows you to graft out-of-tree ports/versions onto the ports-tree-proper. --Chris ___ freebsd-ports@freebsd.o

Re: Python 2.7 removal outline

I *fully* concur. In fact, at least 2 ports that I maintain added a depends on tauthon. Which really raised my ire hearing it's intended doom announcement. :( Honestly. If something "just works", isn't a "security risk". Than don't fix it! --Chris I know abou

Re: Python 2.7 removal outline

On 2021-03-26 15:18, Olivier Certner wrote: Le vendredi 26 mars 2021, 22:43:12 CET Chris a écrit : Honestly. If something "just works", isn't a "security risk". Than don't fix it! Not so simple... But for build-only dependencies, I concur. But anyway, all new

Committer for couple fixed ports that didn't get merged to Quarterly?

gi?id=252258 Thanks! --Chris ___ 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: poudriere: net/openldap24-server: stage/runaway , building forever

omething so small. The server was completely unloaded. Just my login and my small port build. It finally ran to completion without any ill affect. But I've never seen anything like it. A race condition creep into the ports framework, maybe? --Chris Van: "O. Hartmann" Datu

Re: Deprecation of portsnap

r VM for 3 days. Would this be a good time to mention the https://ohshitgit.com/ site? Warning: it contains strong language... It would! And the language is very appropriate, thank you. :-) -- Dave --Chris ___ freebsd-ports@freebsd.org mailing

Re: Deprecation of portsnap

On 2021-04-13 23:22, Stefan Esser wrote: Am 14.04.21 um 02:43 schrieb Chris: On 2021-04-13 15:53, Dave Horsfall wrote: On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote: Except that git will arbitrarily and randomly decide that it needs to run "gc" - which is similarly e

When will git be supported for ports?

hould probably be sent to docs@ I'm not on the list, and because this is ports related. I hope it finds value here as well. Thanks for listening. --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-

Re: When will git be supported for ports?

till do not see the forest for the trees 8-( Kurt, you're AWESOME! Vastly useful, and GREATLY appreciated. :-) Now, if we could only get this $hit in the docs. ;-) Thanks! --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/

Re: When will git be supported for ports?

#x27;t know how to 'git clone'. It's that there's a preferred procedure/protocol to becoming/being a FreeBSD ports Maintainer, and I simply want to get it right the first time. Thereby saving committers a good deal of time and effort. ;-) Thanks again! :-) --Chris > S

Looking for a committer

nication skills. tl;dr; I'd like to join the ports team. Please accept my application. :-) --Chris ___ 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: How to make 'named' rc script invokded earlier at boot time

followed by your "named" entry. Leaving everything else in /etc/rc.conf This (should) source all the rc.conf.local entries ahead of the rc.conf entries. Thereby providing name resolution before ntpdate(8)/time sync service(s) HTH --Chris Now let me use 'ntpdate' as an example.

Re: Ports recompile for 13.0-RELEASE

(ultimately) end up with a nice package repo that facilitates an image install or upgrade path from a fresh install. HTH --Chris ___ 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: Making a port to use OpenSSL of ports collection on FreeBSD 11.x

; in /etc/make.conf. But 'USES=ssl' doesn't provide such argument. I ran into a similar situation requiring freebsd 11 users not use SSL from base, and I simply used a conditional based against freebsd version, that also included a RUN_DEPENDS on security/openssl Wouldn't

Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x

On 2021-05-05 09:10, Yasuhiro Kimura wrote: From: Chris Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Wed, 05 May 2021 08:03:00 -0700 I ran into a similar situation requiring freebsd 11 users not use SSL from base, and I simply used a conditional based

Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x

On 2021-05-05 20:49, Dima Panov wrote: Moin! Chris, your suggestion leads to dll hell due to mix-links between ssl libraries :( At least, your setup easily face up situation where one lib will be built with “port openss” and consumers still get a “base openssl”. DEFAULT_VERSION here is set

pkg-fallout: License not correctly defined: defining both LICENSE_FILE and LICENSE_TEXT is not allowed

eport contains only: LICENSE=LGPL3 LICENSE_FILE= ${WRKSRC}/COPYING for the license section. Please advise, or tell me how to fix the pkg builder. Thanks! --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/fr

Re: pkg-fallout: License not correctly defined: defining both LICENSE_FILE and LICENSE_TEXT is not allowed

On 2021-05-13 09:08, Christoph Moench-Tegeder wrote: ## Chris (portmas...@bsdforge.com): HOWEVER the error returned by pkg-fallout@ makes absolutely no sense at all, given the Makefile for the report contains only: Foremost, that Makefile has an .include, and that's where the mess (for

Re: pkg-fallout: License not correctly defined: defining both LICENSE_FILE and LICENSE_TEXT is not allowed

On 2021-05-14 14:19, Christoph Moench-Tegeder wrote: ## Chris (portmas...@bsdforge.com): > but the way it currently interacts > with your port is not that fine: in the very least, it overwrites > your LICENSE variables, which cannot be your intention. (Try > "make -V LICE

Re: pkg-fallout: License not correctly defined: defining both LICENSE_FILE and LICENSE_TEXT is not allowed

On 2021-05-14 15:15, Christoph Moench-Tegeder wrote: ## Chris (portmas...@bsdforge.com): The problem I'm addressing in this case; is that the following as *always* worked for licenses which carried a copy in ${WRKSRC}/LICENSE_NAME: The problem you're trying to address is only a c

Is there a way to subscribe to the commit messages for only ports you maintain?

I'd like to subscribe to the commit messages ( dev-commits-ports-all ) but only receive messages that affect me -- the ports I currently maintain. Is it possible? Or am I just dreaming? ;-) Thanks in advance for any insight into this. --

Re: Is there a way to subscribe to the commit messages for only ports you maintain?

On 2021-05-17 16:30, Jan Beich wrote: Chris writes: I'd like to subscribe to the commit messages ( dev-commits-ports-all ) but only receive messages that affect me -- the ports I currently maintain. Is it possible? Or am I just dreaming? ;-) No clue but I use Herald rules for some

  1   2   3   4   5   6   7   8   9   10   >