Re: review of google-compute-engine: better quality of the GCE image

[Helen Koike]

On 2017-07-22 04:38 PM, Helen Koike wrote:

Hi,

On 2017-06-28 08:25 PM, Helen Koike wrote:

Hi,

In order to increase the quality of the FreeBSD image for the Google 
Cloud Engine platform, having the package google-compute-engine would 
enable several features that allows the machine to be controlled by 
the GCE tools (web console or gcloud) and other security features, so 
FreeBSD wouldn't stay behind the other distributions on this.


I would really appreciate if anyone could review this package so it 
can be included in the FreeBSD ports, please, see more details in the 
link below:


 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219687

Thanks
LN Koike
___
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"



I just updated the patch to version 2.4.1, I would appreciate if anyone 
could review it.


 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219687

Thanks a lot
Helen
___
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"


Hi,

I received good feedback from the last version that I sent. Could 
someone with access to freebsd-ports be my sponsor/mentor on this, take 
a quick (hopefully) last review and upload it to freebsd-ports please? I 
would appreciate it a lot.


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219687
Thanks
Helen
___
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"

misc/pinfo fails on not being to use ncurses

[Thomas Mueller]

Last night I attempted to build misc/pinfo on FreeBSD 11.1-STABLE amd64, but it 
found ncurses not usable for whatever reason.

I had something like that previously, about three years ago.

Should I include the whole config.log (87869 bytes)?

Briefly, error was

checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: checking location of readline.h file...
Found readline on /usr/local/include/readline/readline.h
checking for readline version... 7
checking location of curses.h file... /usr/local/include/ncurses/ncurses.h
checking if curses is usable... no
configure: error: Curses not found. You need curses to compile pinfo
===>  Script "configure" failed unexpectedly.
Please report the problem to po...@freebsd.org [maintainer] and attach the
"/BETA1/usr/ports/misc/pinfo/work11/pinfo-0.6.10/config.log" including the
output of the failure of your make command. Also, it might be a good idea to
provide an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.


I could also ask what other info file viewers there are, better than the GNU 
info that was formerly part of FreeBSD base system.

When I was using Linux Slackware, Konqueror had a good info viewer, but I don't 
want to have to build and install KDE.

I didn't like Emacs' info viewer when I tried that years ago but haven't run 
Emacs recently.

Tom

___
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: portinstall failure

[Yasuhiro KIMURA]

From: Yasuhiro KIMURA 
Subject: Re: portinstall failure
Date: Sun, 06 Aug 2017 18:55:10 +0900 (JST)

>> Will "make -C /usr/ports/devel/gettext-tools clean" help?
> Sadly it doesn't make any change.

Though I'm not sure if it has something to do with portinstall
failure, 'make -C /path/to/some/port install' results in same error.

root@rolling-vm-freebsd1[962]# pwd
/root
root@rolling-vm-freebsd1[962]# make -C /usr/ports/devel/gettext-tools install
make[1]: don't know how to make 
/usr/ports/devel/gettext-tools/work/.install_done.gettext-tools._usr_local. Stop

make[1]: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gettext-tools
*** Error code 2

Stop.
make: stopped in /usr/ports/devel/gettext-tools
root@rolling-vm-freebsd1[963]#

So it seems there is something wrong with port framework.

---
Yasuhiro KIMURA
___
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: State of FUSE on FreeBSD

[Ben RUBSON]

> On 03 Aug 2017, at 22:22, Julian Elischer  wrote:
> 
> On 3/8/17 7:38 pm, Nikolaus Rath wrote:
>> Hello,
>> 
>> I am the upstream maintainer of libfuse. I'd like to refresh / improve
>> the FreeBSD support in libfuse. My goal is for libfuse not to require
>> any FreeBSD specific patches.
> 
> Hi, great to hear from you!
> at $JOB we use libfuse and We have always worried that we don't really
> have anyone in FreeBSD that really has fuse as a priority.

Glad to hear from Nikolaus too, seeing that efforts are taken to keep
libfuse FreeBSD compatible out of the box ! For sure this is great !

I also hugely use fuse, so having it to work correctly (at least bug-free)
is mandatory for me.

> Rick Maclem has looked at it a little, as have a few people (see the commit 
> logs)
> but generally as long as it more or less works, people tend to steer
> clear of it.
> 
> For us libfuse "just worked" so we haven't touched it.
> We had to touch the kernel part of fuse a little so remove some overly 
> restrictive
> permission checks, and fix some issues to do with page boundaries (from 
> memory)
> but nothing in the library.

I've also reported a few bugs which were in kernel, and have been corrected 
thanks to
the great FreeBSD community.
Fuse kernel support lacks some features, such as entry_timeout / attr_timeout 
(reported),
but it then concerns kernel, not libfuse.

Thx !

Ben
___
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: portinstall failure

[Yasuhiro KIMURA]

From: Boris Samorodov 
Subject: Re: portinstall failure
Date: Sun, 6 Aug 2017 12:24:59 +0300

> Will "make -C /usr/ports/devel/gettext-tools clean" help?

Sadly it doesn't make any change.

root@rolling-vm-freebsd1[896]# make -C /usr/ports/devel/gettext-tools clean
===>  Cleaning for gettext-tools-0.19.8.1
root@rolling-vm-freebsd1[897]# portinstall -c devel/gmake
[Reading data from pkg(8) ... - 140 packages found - done]
--->  Installing 'gmake-4.2.1_1' from a port (devel/gmake)
--->  Building '/usr/ports/devel/gmake'
===>  Cleaning for gmake-4.2.1_1
===>  License GPLv3 accepted by the user
===>   gmake-4.2.1_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by gmake-4.2.1_1 for building
===>  Extracting for gmake-4.2.1_1
=> SHA256 Checksum OK for make-4.2.1.tar.bz2.
===>  Patching for gmake-4.2.1_1
===>  Applying FreeBSD patches for gmake-4.2.1_1
===>   gmake-4.2.1_1 depends on executable: msgfmt - not found
make[3]: don't know how to make 
/usr/ports/devel/gettext-tools/work/.install_done.gettext-tools._usr_local. Stop

make[3]: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gettext-tools
*** Error code 2

Stop.
make[2]: stopped in /usr/ports/devel/gettext-tools
*** Error code 1

Stop.
make[1]: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gmake
*** Error code 1

Stop.
make: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gmake
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portinstall20170806-21342-xqq3tr env make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! devel/gmake   (unknown build error)
root@rolling-vm-freebsd1[898]#

---
Yasuhiro KIMURA
___
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: portinstall failure

[Boris Samorodov]

06.08.2017 07:17, Yasuhiro KIMURA пишет:
> I have noticed installing port with 'portinstall' fails when other
> ports are installed as dependency. For example,
> 
> root@rolling-vm-freebsd1[876]# portinstall -c devel/gmake
> [Reading data from pkg(8) ... - 140 packages found - done]
> --->  Installing 'gmake-4.2.1_1' from a port (devel/gmake)
> --->  Building '/usr/ports/devel/gmake'   
> ===>  Cleaning for gmake-4.2.1_1  
> ===>  License GPLv3 accepted by the user  
> ===>   gmake-4.2.1_1 depends on file: /usr/local/sbin/pkg - found 
>   ===> Fetching all distfiles 
> required by gmake-4.2.1_1 for building
>   ===>  Extracting for gmake-4.2.1_1  
>   
> => SHA256 Checksum OK for make-4.2.1.tar.bz2. 
> ===>  Patching for gmake-4.2.1_1  
> ===>  Applying FreeBSD patches for gmake-4.2.1_1  
> ===>   gmake-4.2.1_1 depends on executable: msgfmt - not found
>   make[3]: don't know how to make 
> /usr/ports/devel/gettext-tools/work/.install_done.gettext-tools._usr_local. 
> Stop 

Will "make -C /usr/ports/devel/gettext-tools clean" help?

> make[3]: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gettext-tools 
>   *** Error code 2   
> 
> Stop.  
> make[2]: stopped in /usr/ports/devel/gettext-tools
> *** Error code 1   
> 
> Stop.  
> make[1]: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gmake 
>*** Error code 1   
> 
> Stop.  
> make: stopped in /am/eastasia/usr0/freebsd/ports/ports/devel/gmake
>   ** Command failed [exit code 
> 1]: /usr/bin/script -qa /tmp/portinstall20170806-4867-dmtlzo env make 
>  ** Fix the problem and try again.
>  
> ** Listing the failed packages (-:ignored / *:skipped / !:failed) 
>   ! devel/gmake   
> (unknown build error) 
> root@rolling-vm-freebsd1[877]#
> 
> I don't think there was such problem before. Does anyone else
> experience this?
> 
-- 
WBR, bsam
___
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"

FreeBSD ports you maintain which are out of date

[portscout]

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 can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
games/gottet| 1.1.3   | 1.1.4
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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: Minor bug in pkg?

[Kurt Jaeger]

Hi!

> Shouldn't pkg be incrementing the first number when installing/upgrading 
> packages?
> 
> [1/247] Reinstalling blender-2.78c_3...
> Extracting blender-2.78c_3: 100%

Yes, it should increment:

https://github.com/freebsd/pkg/issues/1592

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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: Minor bug in pkg?

[Fernando Apesteguía]

El 6 ago. 2017 9:43, "Grzegorz Junka"  escribió:

Shouldn't pkg be incrementing the first number when installing/upgrading
packages?

[1/247] Reinstalling blender-2.78c_3...
Extracting blender-2.78c_3: 100%
[1/247] Reinstalling abiword-3.0.1_5...
Extracting abiword-3.0.1_5: 100%
[1/247] Upgrading R from 3.4.0_2 to 3.4.1_4...
Extracting R-3.4.1_4: 100%
[1/247] Upgrading GraphicsMagick from 1.3.25_3,1 to 1.3.26,1...
Extracting GraphicsMagick-1.3.26,1: 100%


Not really. It depends on the version of the software itself (and the
versioning scheme it uses[1]) and the version of the port itself.

In your example two packages are reinstalled so no increase in any number
takes place. In the two upgrades the third number is updated. That's
perfectly normal.

[1] https://en.m.wikipedia.org/wiki/Software_versioning



___
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"
___
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: Minor bug in pkg?

[Ben Woods]

On 6 August 2017 at 15:18, Grzegorz Junka  wrote:

> Shouldn't pkg be incrementing the first number when installing/upgrading
> packages?
>
> [1/247] Reinstalling blender-2.78c_3...
> Extracting blender-2.78c_3: 100%
> [1/247] Reinstalling abiword-3.0.1_5...
> Extracting abiword-3.0.1_5: 100%
> [1/247] Upgrading R from 3.4.0_2 to 3.4.1_4...
> Extracting R-3.4.1_4: 100%
> [1/247] Upgrading GraphicsMagick from 1.3.25_3,1 to 1.3.26,1...
> Extracting GraphicsMagick-1.3.26,1: 100%
>


For the record, I have also seen this erroneous behaviour before, but
haven't been able to work out why it only happens some of the time.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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"

Maintainer timeout on PR

[Jonathan Chen]

Hi,

Could a kind committer please take a look, and possibly commit:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220782

The port maintainer has not responded in more than 2 weeks.

Cheers.
-- 
Jonathan Chen 
___
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"

Minor bug in pkg?

[Grzegorz Junka]

Shouldn't pkg be incrementing the first number when installing/upgrading 
packages?


[1/247] Reinstalling blender-2.78c_3...
Extracting blender-2.78c_3: 100%
[1/247] Reinstalling abiword-3.0.1_5...
Extracting abiword-3.0.1_5: 100%
[1/247] Upgrading R from 3.4.0_2 to 3.4.1_4...
Extracting R-3.4.1_4: 100%
[1/247] Upgrading GraphicsMagick from 1.3.25_3,1 to 1.3.26,1...
Extracting GraphicsMagick-1.3.26,1: 100%


___
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: FreeBSD Port: ossec-hids-local-2.8.3_1

[Kurt Jaeger]

Hi!

> There is a bug in 99th line of "security/ossec-hids-server/Makefile":
> @cd ${WRKSRC}/src;${MAKE} setlocal;${MAKE} all;${MAKE} build;
> 
> The line should be:
> @cd ${WRKSRC}/src;${MAKE} setlocal;${MAKE} setdb;${MAKE} all;${MAKE} build;
> 
> Although "setdb" makes not much sense for "agent" installation, it is valid 
> for "local" installation.

It would help if you submit this via bugs.freebsd.org -- can you try that ?

A bug report with a fix can run into maintainer timeout and can be
committed by any ports committer.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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"

FreeBSD Port: ossec-hids-local-2.8.3_1

[Dominik Lisiak via freebsd-ports]

There is a bug in 99th line of "security/ossec-hids-server/Makefile":
@cd ${WRKSRC}/src;${MAKE} setlocal;${MAKE} all;${MAKE} build;

The line should be:
@cd ${WRKSRC}/src;${MAKE} setlocal;${MAKE} setdb;${MAKE} all;${MAKE} build;

Although "setdb" makes not much sense for "agent" installation, it is valid for 
"local" installation.


Regards,
Dominik
___
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"