Re: Large builds with poudriere

On 2021-05-20 13:47, Mark Millard wrote: Chris portmaster at bsdforge.com wrote on Thu May 20 20:09:29 UTC 2021 : On 2021-05-20 12:21, Kevin Oberman wrote: > . . . >> > You can greatly reduce the build-time for devel/llvm* by changing the > config to BE_NATIVE to avoid bu

Re: Large builds with poudriere

On 2021-05-20 12:21, Kevin Oberman wrote: On Thu, May 20, 2021 at 8:08 AM Chris wrote: On 2021-05-20 06:15, Ronald Klop wrote: > On 5/20/21 2:47 PM, Fernando Apesteguía wrote: >> El jue., 20 may. 2021 14:45, Alexis Praga >> escribió: >> >>> >>> Hi

Re: Large builds with poudriere

know that. :-/ Thanks, Ronald. Today you are a hero! :-) --Chris Ronald. Thanks, [1] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010 [2] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255233 -- Alexis Praga ___ freebsd

Re: Large builds with poudriere

ts. Even with 8 cores, 16 threads @4.2Ghz && 128Gb RAM. It's a daunting task. I generally use jail(8) otherwise. --Chris Thanks, [1] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010 [2] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255233

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

On 2021-05-19 03:45, Willem Jan Withagen wrote: On 18-5-2021 03:56, Chris wrote: On 2021-05-17 18:17, Julian H. Stacey wrote: Chris wrote: On 2021-05-17 16:30, Jan Beich wrote: > Chris writes: > >> I'd like to subscribe to the commit messages >> ( dev-commits-ports-all ) &

Re: port files/patch-*: PREFIX or LOCALBASE

iable? ${PREFIX} or ${LOCALBASE}? Right or wrong. I've always used ${PREFIX} with great success. pkg(8) can assist you as well. Have a look at make -DBATCH makeplist to see what pkg thinks you mean. HTH --Chris Thanks in advance, eduardo ___ free

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

e a 1/4 billion IPv4 addresses. Over 99% of them are UNMAINTAINED. Proving the hype over IPv4 exhaustion is pure BS. I track them, they remain unmaintained, and OUT of my mail queues. :-) Thanks for taking the time to share your (wisdom) and hacks, Julian! :-) --Chris Cheers, _

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

ook closer. Thanks again! :-) --Chris Li-Wen ___ 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: Is there a way to subscribe to the commit messages for only ports you maintain?

On 2021-05-17 23:46, Michael Gmelin wrote: On Tue, 18 May 2021 03:17:03 +0200 "Julian H. Stacey" wrote: Chris wrote: > On 2021-05-17 16:30, Jan Beich wrote: > > Chris writes: > > > >> I'd like to subscribe to the commit messages > >> ( dev-commits

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

On 2021-05-17 18:17, Julian H. Stacey wrote: Chris wrote: 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 curr

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 something

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. --Chris

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 consecutive

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

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

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/freebsd

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

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

' 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 that work in your case? --Chris --- Yasuhiro Kimura

Re: Ports recompile for 13.0-RELEASE

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: How to make 'named' rc script invokded earlier at boot time

uot; 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. If I run `rcorder /etc/rc.d/* /usr/loc

Looking for a committer

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: When will git be supported for ports?

tocol 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 > Shouldn't this be at the very beginning of the ports doc? This below should work, and I agree w

Re: When will git be supported for ports?

, 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/mailman/listinfo/freebsd-ports To unsubscribe, send any

When will git be supported for ports?

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-ports To unsubscribe, send any

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

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: poudriere: net/openldap24-server: stage/runaway , building forever

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" Datum: vrijdag, 9 april 2021 07:27 Aan: FreeBSD

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

=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: 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 secu

Re: Python 2.7 removal outline

ly* 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 about the archive incompatibi

Re: Python 2.7 removal outline

ot 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.org mailing list http

Re: Python 2.7 removal outline

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 ___ freebsd-ports

Re: Python 2.7 removal outline

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 *something*. Chris out

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: 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

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

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 that the package will not be built

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's

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

On 04/03/2021 13:21, Patrick M. Hausen wrote: Hi Chris, Am 04.03.2021 um 14:11 schrieb Chris Rees : $ ll PDFlib-Lite-7.0.5p3.tar.gz -rw-r--r-- 1 pmh staff 8179201 4 Mär 11:38 PDFlib-Lite-7.0.5p3.tar.gz $ shasum PDFlib-Lite-7.0.5p3.tar.gz 42e0605ae21f4b6d25fa2d20e78fed6df36fbaa9 PDFlib

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

  If so, I suggest the latter, and that's easy to do. 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: www/joomla3 is no longer in the FreeBSD pkg repo

Hi Patrick, On 04/03/2021 08: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

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

oesn't realise that. Sorry-- you'll have to build it yourself until php80 is the current version. @Larry, how about we change pdflib to be an off-by-default OPTION? That'd mean we'd have packages built at least. Chris ___ freebsd-ports@fr

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 wo

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

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

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 https

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! :-) --Chris

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

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 wher

Re: Creating port from pre-built package

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-ports To unsubscribe, send

Re: Handling directory ownership in pkg-plist

On 8 February 2021 08:01:22 GMT, Chris Rees wrote: > > >On 8 February 2021 01:28:06 GMT, Chris wrote: >>On 2021-02-07 12:19, Chris Rees wrote: >>> Afternoon, >>> >>> On 7 February 2021 19:05:26 GMT, Chris >>wrote: >>&g

Re: Handling directory ownership in pkg-plist

On 8 February 2021 01:28:06 GMT, Chris wrote: >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, >>>> >>>

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: Handling directory ownership in pkg-plist

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: >&

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

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, an

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

Handling directory ownership in pkg-plist

to find them. Would it be unacceptable to just have @exec chown -R www:www %D/%%WWWDIR%% at the bottom? Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports

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

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 ___ freebsd-ports@freebsd.org

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 refuse

GitHub: size of remote file is not known

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-ports@freebsd.org

Re: OpenSource app Simple Diary

are: - 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 Simple

Re: TeXLive 2020 Update

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 this helps, and thanks again! :-) --Chris Thanks! Travis

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

Re: portmaster new development

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 ___ freebsd-ports@freebsd.org mailing list

Re: Bug 251656

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 list https

What's the procedure to rename a port?

, 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-ports To unsubscribe

Re: STOP rust!

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 ___ freebsd-ports@freebsd.org

Re: Bind master error on empty.db

*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. As an aside; w

Re: pkg feature request

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://beefy6.nyi.freebsd.org/jail.html?mastername=121amd64-defau

Re: [HEADS UP] Planned deprecation of portsnap

tfully, 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, send any mail to &q

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

te 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 any mail to

Re: [HEADS UP] Planned deprecation of portsnap

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 ___ freebsd-ports@fre

Re: [HEADS UP] Planned deprecation of portsnap

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 deprecation of subversio

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

(/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/listinfo/freebsd-ports To unsub

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

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) after doing so. HTH! :-) --Chris

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: Porting Practice

) 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 not sure

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, Freddie

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

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 is building. This is probabl

Re: Are broken ports retested before performing scheduled removal?

a/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 required freebsd's discache. Al

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

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:

Re: Wrong Ports-OSVERSION in jails

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 DISTDI

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 creating

Re: mail/mailman v3?

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 creating it myself. There's a port that's a shim for py2.x-

Re: mail/mailman v3?

'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 to "freeb

Re: Deluge port for FreeBSD

Yes, thanks, I saw that today. Next I was asking for feedback from Ruslan on net-p2p/deluge and peers. Thanks, Yuri. - Chris > On Mar 27, 2020, at 21:06, Yuri wrote: > > On 2020-03-02 13:33, Chris Ross wrote: >> Yuri, will you be able to un-BROKEN net-p2p/py-libto

Re: Deluge port for FreeBSD

bar. I can't test w/o it. Hello again. I wanted to inquire as to whether there have been any progress on updating the ports tree to deluge 2. It looks like libtorrent-rasterbar (and py-libtorrent-rasterbar) should be available now. Thank you. - Chris __

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

ist="/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@freebsd.org

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

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 port (p

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 installed, du

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

. 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! --Chris

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 ___ freebsd-ports

Re: claws-mail search a new home

(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 mail to &quo

Re: Deluge port for FreeBSD

Yuri, will you be able to un-BROKEN net-p2p/py-libtorrent-rasterbar sometime soon? From reading and my own testing, version 1.2.4 does not have the "doesn't install any files" problem that earlier releases did on FreeBSD. Fixing that port will also allow deluge to be updated

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

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"

  1   2   3   4   5   6   7   8   9   10   >