from Matthew Seaman and my previous post:
> > But what is happening with synth, supposed to make portupgrade and
> > portmaster obsolete?
> Synth is still being actively developed but the author is now working
> primarily on DFly. There is a new maintainer for the synth port who
> will be porting
On Fri, 6/9/17, Jonathan Chen wrote:
Subject: Re: Unable to update repository Synth
To: "Bob Willcox"
Cc: "ports list"
Date: Friday, June 9, 2017, 3:14 PM
On 10 June 2017 at 05:02, Bob
Willcox
wrote:
> I am running the drm-next-4.7
and w
Am 08.06.17 um 21:15 schrieb Dimitry Andric:
> On 8 Jun 2017, at 20:35, Mark Knight wrote:
>>
>> On 08/06/2017 18:35, Dimitry Andric wrote:
>>> I'm guessing that it is confused by an existing samba installation. Try
>>> removing all other samba installations before attempting to build this
>>> po
On 10 June 2017 at 05:02, Bob Willcox wrote:
> I am running the drm-next-4.7 and when I ran synth recently on my system
> up update the ports and at the end of the run received these errors:
>
> pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
> pkg: repository Synth contains
Matthew Seaman matthew at FreeBSD.org wrote on Fri Jun 9 13:21:34 UTC 2017
> Synth is still being actively developed but the author is now working
> primarily on DFly. There is a new maintainer for the synth port who
> will be porting the latest updates to FreeBSD, much like almost any
> other pi
On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
I haven't looked, but might this be due to:
# Option PICO
PICO_RUN_DEPENDS=pico:editors/pico-alpine
Since pico-alpine is a slave port of alpine, you'll want to make sure
you're overriding things correctly, and something that was replac
El día viernes, junio 09, 2017 a las 12:17:09p. m. -0600, Adam Weinberger
escribió:
> >
> > */usr/ports/net/gnetcat/Makefile:MAINTAINER=po...@freebsd.org
> > */usr/ports/net/netcat/Makefile:MAINTAINER= po...@freebsd.org
> > */usr/ports/net/rdesktop/Makefile:MAINTAINER= po...@freebs
> On 9 Jun, 2017, at 12:01, Matthias Apitz wrote:
>
>
> Hello,
>
> I'm a long time FreeBSD user, since 2.2.5 in the 1990, and nowadays run
> my own poudriere oven to compile from head for amd64 the ports I do need on
> my own laptops and netbooks, and of some colleague for which I do binary
> s
Hello,
I'm a long time FreeBSD user, since 2.2.5 in the 1990, and nowadays run
my own poudriere oven to compile from head for amd64 the ports I do need on
my own laptops and netbooks, and of some colleague for which I do binary
support of system and ports.
I'm already maintaining print/muttprint
I am running the drm-next-4.7 and when I ran synth recently on my system
up update the ports and at the end of the run received these errors:
pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64
Processing
style="margin-bottom:0.0001pt;text-align:justify;line-height:normal">style="color:rgb(0,32,96)">Hi,
style="margin-bottom:0.0001pt;text-align:justify;line-height:normal">style="color:rgb(0,32,96)">
style="margin-bottom:0.0001pt;text-align:justify;line-height:normal">style="color:rgb(0,32,96)">W
On 6/9/17 11:47 PM, Vick Khera wrote:
> I'm trying to build py3-iocage, which has as one dependeny py3-requests.
> When building this with poudriere, the py3-requests port somehow causes
> py27-chardet to be built instead of py36-chardet, which then results in
> py3-requests failing to find the dep
I'm trying to build py3-iocage, which has as one dependeny py3-requests.
When building this with poudriere, the py3-requests port somehow causes
py27-chardet to be built instead of py36-chardet, which then results in
py3-requests failing to find the dependency (which it just tried to build).
Here
On 09/06/2017 00:54, Thomas Mueller wrote:
> from René Ladan:
>
>> it is our pleasure to announce that Baptiste Daroussin (bapt@) is
>> back on portmgr.>
> Is this a new port in the works, or is portmgr a (confusing)
> abbreviation for portmanager?
No, portmgr is the group of people that adminis
On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
I think I had a brainfail, and I believe it is in-fact fine to use both
(if necessary) and the wording of the handbook might need to be tweaked
not to imply it.
That aside, I can't see use (testing) of PORT_OPTIONS:M or other
variables that p
On 6/9/17 9:50 PM, Marco Beishuizen wrote:
> On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
>
>> On 6/9/17 7:41 PM, Marco Beishuizen wrote:
>>
>> Hi Marco,
>>
>> I believe the reason is:
>>
>>> .include
>>
>> The port includes this ... AND
>>
>>
>>
>>> .include
>>
>> This -^
On 6/9/17 9:26 PM, Marco Beishuizen wrote:
> On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
>
>> On 6/9/17 7:41 PM, Marco Beishuizen wrote:
>>
>> Hi Marco,
>>
>> I believe the reason is:
>>
>>> .include
>>
>> The port includes this ... AND
>>
>>
>>
>>> .include
>>
>> This -^
On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
On 6/9/17 7:41 PM, Marco Beishuizen wrote:
Hi Marco,
I believe the reason is:
.include
The port includes this ... AND
.include
This -^
Use one or the other, or neither if its *all* options helpers, but not
both. Se
On Fri, 9 Jun 2017, the wise Kubilay Kocak wrote:
On 6/9/17 7:41 PM, Marco Beishuizen wrote:
Hi Marco,
I believe the reason is:
.include
The port includes this ... AND
.include
This -^
Use one or the other, or neither if its *all* options helpers, but not
both. Se
On 6/9/17 7:41 PM, Marco Beishuizen wrote:
Hi Marco,
I believe the reason is:
> OPTIONS_DEFINE=ASPELL CONS25 DOCS IPV6 LDAP MAILDIR MOUSE NLS
> NOSPELL PASSFILE PICO THREADS
> OPTIONS_DEFAULT+=MOUSE PICO THREADS
>
> CONS25_DESC=Add a patch to support color for default console
>
Hi,
Being the maintainer of mail/alpine, I'm trying to cleanup it's Makefile.
What I now have is this:
PORTNAME?= alpine
PORTVERSION=2.21
PORTREVISION?= 0
CATEGORIES?=mail news ipv6
MASTER_SITES= http://alpine.freeiz.com/alpine/release/src/
DIST_SUBDIR=alpine-${PORTVERSION}
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
Hi!
> > > I ask for little advice.
> > > I wrote web manager X.509 certificates http://minica.unix7.org/ and
> > > created a freebsd port for it.
> > >
> > > 1. Who could check quality and security of this code?
> >
> > The committer would check the port quality etc.
>
> Next dummy question
Hi!
> > > Submit patches via bugs.freebsd.org for the two ports, and
> > > the maintainers will decide if they include them.
> >
> > Btw, have you submitted the patches to those perl modules upstream as well ?
> First, I sent to perl modules authors/editors from CPAN. Two or more times, to
> d
On Fri, 9 Jun 2017 09:28:59 +0200
Kurt Jaeger wrote:
> Hi!
>
> > I ask for little advice.
> > I wrote web manager X.509 certificates http://minica.unix7.org/ and created
> > a freebsd port for it.
> >
> > 1. Who could check quality and security of this code?
>
> The committer would check t
On Fri, 9 Jun 2017 09:35:06 +0200
Kurt Jaeger wrote:
> Hi!
>
> > Submit patches via bugs.freebsd.org for the two ports, and
> > the maintainers will decide if they include them.
>
> Btw, have you submitted the patches to those perl modules upstream as well ?
>
First, I sent to perl modules
Hi!
> Submit patches via bugs.freebsd.org for the two ports, and
> the maintainers will decide if they include them.
Btw, have you submitted the patches to those perl modules upstream as well ?
--
p...@opsec.eu+49 171 3101372 3 years to go !
_
Hi!
> I ask for little advice.
> I wrote web manager X.509 certificates http://minica.unix7.org/ and created a
> freebsd port for it.
>
> 1. Who could check quality and security of this code?
The committer would check the port quality etc.
Security would be the task of 'the many eyes of open s
Hi!
I ask for little advice.
I wrote web manager X.509 certificates http://minica.unix7.org/ and created a
freebsd port for it.
1. Who could check quality and security of this code?
2. If quality the code is sufficient to be included in freebsd ports, then:
For the port it is necessary patches
29 matches
Mail list logo
