don't fork portmaster source

> I'm asking myself how to manage the code. Should i create a new GitHub > repository? Fork the existing from freebsd/portmaster? How to handle the > LOCAL Master-Site? Talk to Bryan Drewery. "If someone else would like to maintain this please discuss with me and I will get you access to the

Ports with github private repository

Hello, reading the documentation[1],I find no way to use a private github repo in ports. They can give me a hand if possible or if I'm misreading the documentation [1] https://www.freebsd.org/doc/en/books/porters-handbook/book.html#makefile-master_sites-github-description thanks & regards --

Re: Removing documentation

On 02/10/16 12:21, John Marino wrote: > On 2/9/2016 9:27 PM, John Marino wrote: >> On 2/9/2016 9:20 PM, Warren Block wrote: >>> On Tue, 9 Feb 2016, John Marino wrote: >>> On 2/9/2016 7:20 PM, Warren Block wrote: >> If you have the build log, I'd like to see it. Dewayne G. got an error

Re: PHP7 package?

On 2/9/16 10:32 PM, Kurt Jaeger wrote: Hi! Everythig seemed to work fine but when I added LoadModule php7_modulelibexec/apache24/libphp7.so to the httpd.conf apache core dumped. Ah, that is a different issue. Use https://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh on

Re: maintaining portmaster ? was: Re: Removing documentation

Hi! > I'm asking myself how to manage the code. Should i create a new GitHub > repository? Fork the existing from freebsd/portmaster? How to handle the > LOCAL Master-Site? Fork it on Github, for now. It can later be merged with freebsd/portmaster. -- p...@opsec.eu+49 171 3101372

pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

I'm trying to upgrade my ports with a set that I built using poudriere. I'm running FreeBSD-current r295354, pkg 1.6.3. The packages are here on my local (localhost, vega) box: /usr/local/poudriere/data/packages/11amd64-default My repo pkg.conf (vega.conf) looks like this: vega: {

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, 10 Feb 2016, Daniel Eischen wrote: I'm trying to upgrade my ports with a set that I built using poudriere. I'm running FreeBSD-current r295354, pkg 1.6.3. The packages are here on my local (localhost, vega) box: /usr/local/poudriere/data/packages/11amd64-default My repo pkg.conf

Re: Removing documentation

On Mon, Feb 8, 2016 at 1:55 AM, John Marino wrote: > On 2/8/2016 10:30 AM, Mathias Picker wrote: > > Am Montag, den 08.02.2016, 08:35 +0100 schrieb John Marino: > > While I like the ideas of synth, and hoped I could use it to just build > > my 3-8 ports with modified

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On 10 Feb 2016, at 20:10, Daniel Eischen wrote: > > I'm trying to upgrade my ports with a set that I built using poudriere. > I'm running FreeBSD-current r295354, pkg 1.6.3. > > The packages are here on my local (localhost, vega) box: > >

Re: Removing documentation

On 2/10/2016 11:31 PM, Alphons van Werven wrote: > ???Between all the question marks (sorry, I just can't help myself) I > can reveal that Portmaster detects at least some of the above kinds of > changes. Perhaps not all four, but at least some (if not most). > > I suspect it's probably not

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, 10 Feb 2016, Dimitry Andric wrote: On 10 Feb 2016, at 20:10, Daniel Eischen wrote: I'm trying to upgrade my ports with a set that I built using poudriere. I'm running FreeBSD-current r295354, pkg 1.6.3. The packages are here on my local (localhost, vega) box:

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, Feb 10, 2016 at 10:16:44PM +0100, Dimitry Andric wrote: > On 10 Feb 2016, at 20:10, Daniel Eischen wrote: > > > > I'm trying to upgrade my ports with a set that I built using poudriere. > > I'm running FreeBSD-current r295354, pkg 1.6.3. > > > > The packages are

Re: Removing documentation

John Marino wrote: > Well, if I make the assume that Kevin has been using portmaster, and > that using Synth revealed 42 obsolete cached configurations, I would > have to conclude PM doesn't do this anymore or does it very poorly and > misses a large number of configs. Using the latest version

Re: Removing documentation

On 2/10/2016 10:15 PM, Kevin Oberman wrote: > > The stale configuration file issue has me a bit confused. The man page > does not make it clear just what makes a config "stale". All of my ports > are up to date as of 11:00 UTC this morning. As far as I know, all of > the configs are "current",

Re: Removing documentation

Freddie Cash wrote: >> A) An option is added >> B) An option is removed >> C) An option default changed. >> D) Any other option configuration changed. >> >> Synth is the *only* tool that detects this. > ???portmaster used to do this; was this option removed? It was one of the > nicer features

Re: Removing documentation

On Wed, Feb 10, 2016 at 01:15:58PM -0800, Kevin Oberman wrote: > On Mon, Feb 8, 2016 at 1:55 AM, John Marino wrote: > > > On 2/8/2016 10:30 AM, Mathias Picker wrote: > > > Am Montag, den 08.02.2016, 08:35 +0100 schrieb John Marino: > > > While I like the ideas of synth, and

Re: Removing documentation

On Wed, Feb 10, 2016 at 1:46 PM, John Marino wrote: > On 2/10/2016 10:15 PM, Kevin Oberman wrote: > > > > The stale configuration file issue has me a bit confused. The man page > > does not make it clear just what makes a config "stale". All of my ports > > are up to date as

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, 10 Feb 2016, Daniel Eischen wrote: On Wed, 10 Feb 2016, Dimitry Andric wrote: On 10 Feb 2016, at 20:10, Daniel Eischen wrote: I'm trying to upgrade my ports with a set that I built using poudriere. I'm running FreeBSD-current r295354, pkg 1.6.3. The packages

Re: Removing documentation

On 2/10/2016 10:37 AM, Lars Engels wrote: > On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote: >> On 2/9/2016 4:15 PM, Lars Engels wrote: >>> >>> root@fbsd01:~ # synth status >>> Querying system about current package installations. >>> Stand by, comparing installed packages against the

Re: maintaining portmaster ? was: Re: Removing documentation

Hi! > >> I did take a look. I could do both: maintaining the port and maintaining > >> the software. What do you need? ;) > > > >Submit patches to the 12 PRs open for portmaster: > > > >https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster > > That is just being silly. Sorry if

Re: Removing documentation

On 2/10/2016 11:09 AM, Lars Engels wrote: > On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote: >> On 2/10/2016 10:37 AM, Lars Engels wrote: >>> On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote: On 2/9/2016 4:15 PM, Lars Engels wrote: > > root@fbsd01:~ # synth

Re: Moving to synth (was: Removing documentation)

There are still issues moving to synth on non-Tier1 architectures: $ sudo pkg install synth-0.99_6 Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Updating database digests format: 100% pkg: No packages available to install matching

Re: Moving to synth

On 2/10/2016 12:10 PM, Peter Jeremy wrote: > There are still issues moving to synth on non-Tier1 architectures: This limitation has been known and published from the beginning (bapt@ recently iterated it for those that weren't aware). It would actually be possible to support ARM fairly easily,

Re: Removing documentation

On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote: > On 2/10/2016 10:37 AM, Lars Engels wrote: > > On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote: > >> On 2/9/2016 4:15 PM, Lars Engels wrote: > >>> > >>> root@fbsd01:~ # synth status > >>> Querying system about current

Re: Removing documentation

My rather short experience: Synth configuration profile: LiveSystem === [A] Ports directory/usr/ports [B] Packages directory /var/synth/live_packages [C] Distfiles directory

Re: Removing documentation

On 2/9/2016 9:27 PM, John Marino wrote: > On 2/9/2016 9:20 PM, Warren Block wrote: >> On Tue, 9 Feb 2016, John Marino wrote: >> >>> On 2/9/2016 7:20 PM, Warren Block wrote: > If you have the build log, I'd like to see it. Dewayne G. got an error > after overriding CPUTYPE (do you do that

Re: synth documentation

On 2/10/2016 2:57 AM, Greg 'groggy' Lehey wrote: > I installed the synth package a couple of days ago, mainly to take a > look. And yes, I agree, if you're happy with the package (I would > be), the Ada dependencies and long build times aren't an issue. I'm racking my brains and I can't find a

Re: synth documentation

Hi! > I'm racking my brains and I can't find a single rational reason why > somebody would refuse the package (especially if building it on an Atom > is the alternative). The famous paper from Ken Thompson: Reflections on trusting trust http://dl.acm.org/citation.cfm?doid=358198.358210 --

Re: synth documentation

On 2/10/2016 10:01 AM, Kurt Jaeger wrote: > Hi! > >> I'm racking my brains and I can't find a single rational reason why >> somebody would refuse the package (especially if building it on an Atom >> is the alternative). > > The famous paper from Ken Thompson: Reflections on trusting trust > >

FreeBSD ports you maintain which are out of date

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,

Re: Removing documentation

On Wed, Feb 10, 2016 at 11:16:10AM +0100, John Marino wrote: > On 2/10/2016 11:09 AM, Lars Engels wrote: > > On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote: > >> On 2/10/2016 10:37 AM, Lars Engels wrote: > >>> On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote: > On

Re: maintaining portmaster ? was: Re: Removing documentation

On 10.02.2016 06:47, Peter Jeremy wrote: On 2016-Feb-09 21:24:56 +0100, Kurt Jaeger wrote: Torsten wrote: I did take a look. I could do both: maintaining the port and maintaining the software. What do you need? ;) Submit patches to the 12 PRs open for portmaster:

Re: Removing documentation

On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote: > On 2/9/2016 4:15 PM, Lars Engels wrote: > > > > root@fbsd01:~ # synth status > > Querying system about current package installations. > > Stand by, comparing installed packages against the ports tree. > > Stand by, building pkg(8)

Re: Please commit PR#203931 dns/knot2

Hi! > has maintainer approval. thanks everyone > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203931 Done. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list

Please commit PR#203931 dns/knot2

has maintainer approval. thanks everyone https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203931 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, 10 Feb 2016, Warren Block wrote: On Wed, 10 Feb 2016, Daniel Eischen wrote: On Wed, 10 Feb 2016, Dimitry Andric wrote: On 10 Feb 2016, at 20:10, Daniel Eischen wrote: I'm trying to upgrade my ports with a set that I built using poudriere. I'm running

Re: pkg 1.6.3 unable to upgrade, URL in pkg.conf problem?

On Wed, 10 Feb 2016, Baptiste Daroussin wrote: On Wed, Feb 10, 2016 at 10:16:44PM +0100, Dimitry Andric wrote: On 10 Feb 2016, at 20:10, Daniel Eischen wrote: I'm trying to upgrade my ports with a set that I built using poudriere. I'm running FreeBSD-current r295354,