Hello Steven,
On Tue, 18 Apr 2017 13:09:22 +, Steven Hartland
wrote:
> You should use built in golang vendoring to ensure these
> dependencies, as their is no guarantee that someone won't update the
> library port and your app would break, so doing that is very fragile
Currently the GH_TUPL
On Tue, Apr 18, 2017 at 09:43:23PM +0200, Jan Beich wrote:
>
> See bug 211069 which was duped against bug 203989 that triggered a
> different assertion. The above error did show up on armv6 buildbot[1]
> but nowadays is blocked by other ports.
>
What is meant by the term "blocked by other ports"?
Jan Beich wrote:
qjail1 writes:
I maintain a port and I have users complaining that the pkg system
takes many months before the updated version of my port shows up in
the pkg system.
Better ask committer assigned to your bug to add MFH tag or send an
email to ports-secteam@ (and CC portmgr@)
On 4/18/17, 2:41 PM, "Jev Björsell" wrote:
Hi All,
Could I get a committer to apply my latest update patch for net-mg
mt/prometheus?
Patch is available here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218737
Thanks so much,
-Jev
Waiting for my me
On 18 Apr 2017, at 21:43, Jan Beich wrote:
>
> Dimitry Andric writes:
>
>> On 18 Apr 2017, at 20:47, bob prohaska wrote:
>>
>>>
>>> For some time (years?) firefox compiles have failed with an error message
>>> along the lines of
>>>
>>> Assertion failed: (isReg() && "This is not a register
Miroslav Lachman wrote on 2017/03/31 15:31:
I don't know if it was "pkg" fault or mariadb101-server and
mariadb101-client conflict.
I did standard "pkg upgrade" and at the end I have half files of
mariadb101-client missing:
# pkg check -Ba
Checking all packages: ...
pkg: fstat() failed for(/usr
Dimitry Andric writes:
> On 18 Apr 2017, at 20:47, bob prohaska wrote:
>
>>
>> For some time (years?) firefox compiles have failed with an error message
>> along the lines of
>>
>> Assertion failed: (isReg() && "This is not a register operand!"),
>> function getReg, file
>> /usr/src/contrib/ll
On 2017-04-18 15:22, Rainer Hurling wrote:
Am 18.04.2017 um 16:56 schrieb Mathieu Arnold:
Le 18/04/2017 à 15:59, Jim Trigg a écrit :
According to UPDATING as of 20161103, "The default Perl version has
been switched to Perl 5.24." However, when I follow the instructions
Yes, I added "DEFAULT_VE
Hi All,
Could I get a committer to apply my latest update patch for net-mg
mt/prometheus?
Patch is available here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218737
Thanks so much,
-Jev
___
freebsd-ports@freebsd.org mailing list
https://lists.fr
Am 18.04.2017 um 16:56 schrieb Mathieu Arnold:
> Le 18/04/2017 à 15:59, Jim Trigg a écrit :
>> According to UPDATING as of 20161103, "The default Perl version has
>> been switched to Perl 5.24." However, when I follow the instructions
>> there to switch, I get the following message (after running p
On 18 Apr 2017, at 20:47, bob prohaska wrote:
>
> For some time (years?) firefox compiles have failed with an error message
> along the lines of
>
> Assertion failed: (isReg() && "This is not a register operand!"), function
> getReg, file /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
For some time (years?) firefox compiles have failed with an error message
along the lines of
Assertion failed: (isReg() && "This is not a register operand!"), function
getReg, file /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
c++: error: unable to execute command: Abort trap (core dum
I've thought about that or perhaps a quick script to turn a vendor.json
in the the appropriate GH_TUPLE for a port Makefile, but even that seems
less necessary these days as more and more projects included a vendor
dir in their source tree.
Thanks to everyone for their input, seems we all agree, s
On Tue, Apr 18, 2017 at 4:31 AM, Rainer Hurling wrote:
> Hi Jochen,
>
> Am 18.04.2017 um 11:35 schrieb Jochen Neumeister:
>
>> Hi Rainer,
>>
>>
>> Am 18.04.2017 um 11:27 schrieb Rainer Hurling:
>>
>>> After the shebang rules where intensified, many ports have been fixed
>>> already. Many thanks f
qjail1 writes:
> I maintain a port and I have users complaining that the pkg system
> takes many months before the updated version of my port shows up in
> the pkg system.
Better ask committer assigned to your bug to add MFH tag or send an
email to ports-secteam@ (and CC portmgr@) which commit t
On Tue, Apr 18, 2017 at 7:57 AM, krad wrote:
> quarterly does seem very cautious, maybe a monthly might be a good
> alternative. I can understand people being hesitant about latest though. I
> guess these are not the people who ask though. Maybe the real answer though
> is to have a specific repo
Hi,
Are you selling SEO short?
Your business might be the best in the industry, but it is SEO that decides
your success. Not everyone is searching for your name on Google; they are
probably searching for the product you sell, and whoever turns up fast gets
the deal.
Don't lose your business to y
Hello,
Would you be interested in SonicWall Users Contact List for your marketing
campaigns?
Information Fields: Name, Title, Email, Phone, Company Name, Physical Address,
City, State, Zip Code, Country, Web Address, Employee Size, Revenue Size and
Industry.
Let me know if you are interested
quarterly does seem very cautious, maybe a monthly might be a good
alternative. I can understand people being hesitant about latest though. I
guess these are not the people who ask though. Maybe the real answer though
is to have a specific repo for that port for the bleeding edge people much
like
Le 18/04/2017 à 15:59, Jim Trigg a écrit :
> According to UPDATING as of 20161103, "The default Perl version has
> been switched to Perl 5.24." However, when I follow the instructions
> there to switch, I get the following message (after running portsnap
> fetch update manually even though it runs
I agree with you.
Maybe we should provide helpers to do the "fetching dependencies" part so
that will be less cumbersome.
On Mon, Apr 17, 2017 at 4:20 PM, Steve Wills wrote:
> Hi,
>
> I'd like to propose eliminating packaging of Go libs.
>
> Almost every Go app is developed with a different vers
According to UPDATING as of 20161103, "The default Perl version has been
switched to Perl 5.24." However, when I follow the instructions there to
switch, I get the following message (after running portsnap fetch update
manually even though it runs automatically every night):
" This is *NOT
I maintain a port and I have users complaining that the pkg system takes
many months before the updated version of my port shows up in the pkg
system.
My response is I tell them to change a line in their
/etc/pkg/FreeBSD.conf file
from url: "pkg+http://pkg.Freebsd.org/${ABI}/quarterly";,
to
You should use built in golang vendoring to ensure these dependencies, as
their is no guarantee that someone won't update the library port and your
app would break, so doing that is very fragile
On Tue, 18 Apr 2017 at 03:34, Christopher Hall <
christopherhall@gmail.com> wrote:
> Hello Steve,
>
Kevin Oberman writes:
> On Sat, Apr 15, 2017 at 3:09 PM, Peter Smith wrote:
>> # uname -a
>> > FreeBSD red 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22
>> > 06:12:04 UTC 2017
>> > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
[...]
>> ===> Applying FreeBSD
Hi Jochen,
Am 18.04.2017 um 11:35 schrieb Jochen Neumeister:
Hi Rainer,
Am 18.04.2017 um 11:27 schrieb Rainer Hurling:
After the shebang rules where intensified, many ports have been fixed
already. Many thanks for that!
For me, on 12.0-CURRENT, at least lang/go and www/libxul have non
fix
Hi Rainer,
Am 18.04.2017 um 11:27 schrieb Rainer Hurling:
After the shebang rules where intensified, many ports have been fixed
already. Many thanks for that!
For me, on 12.0-CURRENT, at least lang/go and www/libxul have non
fixed shebangs until now:
lang/go:
Error: '/bin/bash' is an inv
After the shebang rules where intensified, many ports have been fixed
already. Many thanks for that!
For me, on 12.0-CURRENT, at least lang/go and www/libxul have non fixed
shebangs until now:
lang/go:
Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for
'go/lib/time/updat
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
29 matches
Mail list logo
