Re: clamav problem

[Kurt Jaeger]

Hi!

> On Mon, 21 Mar 2016 14:30:25 -0700, Kevin Oberman stated:
> 
> >Hmm. Let's see. A bug that may allow the defeat of a security
> >mechanism and allow a black-hat to do bad stuff before the bug con
> >even be looked at. Why would anyone have an issue with that? I mean,
> >don't we all want more zero-day vulnerabilities? (Sorry, Guess I put
> >on my sarcasm hat today.)
> 
> You are right. Hell, if I had cancer why should the doctor tell me if
> there is no cure for it. By the way, you must be a government employee.
> You know, the type thats wants to keep everything secret but pry into
> everyone else's life.

The problem report is now public, btw. No need to get personal 8-)

-- 
p...@opsec.eu+49 171 3101372 4 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"

nvm

[Ganbold Tsagaankhuu]

Hi,

Is there any reason why nvm not ports yet?

thanks a lot,

Ganbold
___
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: Future of pecl ports

[Martin Waschbüsch]

> Am 14.03.2016 um 11:37 schrieb Gasol Wu :
> 
> Hi miwi,
> 
> First of all, I'm appreciated for your PHP support in FreeBSD.
> 
> I have received many outdated notices regarding the PECL ports from
> portscout because I'm the maintainer.
> I saw the same problem here when I start to packaging, So I'm so happy
> to see this discussion here.
> 
> IMHO, I will vote option (c). Here is my thought.
> 
> 1. Explicit is better than implicit
> 2. It will be bad if we upgrade ports without changing port name,
> especially they have BC problems.
> 3. I would like to see official support for installing different
> version of PHP in same FreeBSD box
>without using 3rd-party tools like phpbrew or phpenv.
>Imagine that we have /usr/local/bin/{php55,php56,php70} respectively
Totally agree.
If this is where we're headed, I'd like to pitch in and help make #3 happen.

Martin
___
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: clamav problem

[Carmel]

On Mon, 21 Mar 2016 14:30:25 -0700, Kevin Oberman stated:

>Hmm. Let's see. A bug that may allow the defeat of a security
>mechanism and allow a black-hat to do bad stuff before the bug con
>even be looked at. Why would anyone have an issue with that? I mean,
>don't we all want more zero-day vulnerabilities? (Sorry, Guess I put
>on my sarcasm hat today.)

You are right. Hell, if I had cancer why should the doctor tell me if
there is no cure for it. By the way, you must be a government employee.
You know, the type thats wants to keep everything secret but pry into
everyone else's life.

-- 
Carmel
___
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: clamav problem

[Kevin Oberman]

On Sun, Mar 20, 2016 at 1:32 PM, Carmel  wrote:

> On Sun, 20 Mar 2016 16:42:54 +0100, Kurt Jaeger stated:
>
> >Hi!
> >
> >> >The make check of clamav exposes some issues, I've reported them
> >> >upstream:
> >> >
> >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542
> >>
> >> For whatever reason, I keep getting this error message when I try an
> >> access that report:
> >>
> >> You are not authorized to access bug #11542.
> >
> >Yes. It seems clamav bugzilla is restrictive and I can not change
> >that, as submitter of that bug.
>
> Now that makes about "ZERO" sense. Why would you (meaning clamav) want
> to hide bug information? Dumbest thing I ever saw (almost).


Hmm. Let's see. A bug that may allow the defeat of a security mechanism and
allow a black-hat to do bad stuff before the bug con even be looked at. Why
would anyone have an issue with that? I mean, don't we all want more
zero-day vulnerabilities? (Sorry, Guess I put on my sarcasm hat today.)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: What is proper way to re-do "check-plist" after pkg-plist editing?

[Mathieu Arnold]

+--On 21 mars 2016 21:11:13 +0100 Kurt Jaeger  wrote:
| Hi!
| 
|>  What should I call after I fixed issues in pkg-plist found by "make
|> check-plist"? New "make check-plist" doesn't work for me.
| 
| cd work
| rm -rf .stage* stage
| cd ..

Or as we call it, make restage. (Which is way easier for those of us who
have MAKEOBJDIRPREFIX set.

| make check-plist
| 
| There should be a target for this, like make recheck-plist or so 8-)



-- 
Mathieu Arnold

pgpzH_UUOzrHP.pgp
Description: PGP signature

Is the KMymoney port broken?

[Christian Baer]

Hey guys!

Because the precompiled KMymoney does not have homebanking compiled into it, I 
tried to compile the software with the ports. This normally works very well, 
but also often installs a lot of stuff that is only needed at compile time 
(and usually results in a long wait too), so if I don't have to, I usually do 
not choose this option.

In this case however the port will not install. What I did:

make config [to enable KBANKING]
Note: NLS and CALENDAR are enabled too.

make all

This actually runs through.

make install
then stops before installing everything. I have put part of the output below 
the message. It seems like there is something missing, which make me think 
that possibly not everthing required is actually being built.

System: FreeBSD falbala 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 
01:32:46 UTC 2016 amd64 (GENERIC kernel)

Ports: revision 411445

Is this a known issue? Is there a workaround?

Kind regards,
Chris

Output of make install (in part):
-- Installing: /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/share/doc/HTML/pt_BR/kmymoney/index.docbook
-- Installing: /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/share/doc/HTML/pt_BR/kmymoney/credits.docbook
-- Installing: /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/share/doc/HTML/pt_BR/kmymoney/details-
reports.docbook
-- Installing: /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/share/doc/HTML/pt_BR/kmymoney/reference.docbook
> Compressing man pages (compress-man)
root@falbala:/usr/ports/finance/kmymoney-kde4 # make install
===>  Installing for kmymoney-4.7.2_1
===>   kmymoney-4.7.2_1 depends on executable: update-mime-database - found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtDBus.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtGui.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtNetwork.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libphonon.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtSql.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtSvg.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/qt4/libQtXml.so - 
found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/libkdecore.so - found
===>   kmymoney-4.7.2_1 depends on file: /usr/local/lib/libkpimutils.so - 
found
===>   kmymoney-4.7.2_1 depends on shared library: libboost_graph.so - found 
(/usr/local/lib/libboost_graph.so)
===>   kmymoney-4.7.2_1 depends on shared library: libalkimia.so - found 
(/usr/local/lib/libalkimia.so)
===>   kmymoney-4.7.2_1 depends on shared library: libical.so - found 
(/usr/local/lib/libical.so)
===>   kmymoney-4.7.2_1 depends on shared library: libgwengui-qt4.so - found 
(/usr/local/lib/libgwengui-qt4.so)
===>   kmymoney-4.7.2_1 depends on shared library: libaqbanking.so - found 
(/usr/local/lib/libaqbanking.so)
===>   kmymoney-4.7.2_1 depends on shared library: libintl.so - found 
(/usr/local/lib/libintl.so)
===>  Checking if kmymoney already installed
===>   Registering installation for kmymoney-4.7.2_1
pkg-static: Unable to access file /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/include/kde4/kmymoney/importinterface.h: No such 
file or directory
pkg-static: Unable to access file /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/include/kde4/kmymoney/imymoneyprocessingcalendar.h: 
No such file or directory
pkg-static: Unable to access file /usr/ports/finance/kmymoney-
kde4/work/stage/usr/local/include/kde4/kmymoney/imymoneyserialize.h: No such 
file or directory
___
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: gnome-post-install ordering

[Don Lewis]

On 21 Mar, Mathieu Arnold wrote:
> +--On 21 mars 2016 11:18:26 -0700 Don Lewis  wrote:
> | gnome-post-install does several different things.  I haven't looked to
> | see if all of them should be moved.  Unfortunately I'm not sure that an
> | exp-run would pick up some of the more subtle breakage.
> 
> Then, we just extract the INSTALL_ICONS bits into a gnome-install-icons
> target, and run it later, much later.  The gnome-post-install target could
> benefit from being split up.  It was not so before because USES=gnome is
> quite new, and adding stuff to the target ordering system was a pain. Now,
> it could be splitted in gnome-gconf-schemas, gnome-glib-schemas,
> gnome-installs-omf, and gnome-install-icons.  It was on my roadmap when I
> rewrote the target ordering system to use numbers, but I decided against
> changing too many things at once.

That sounds fine to me.  I didn't closely look at the rest of
gnome-post-install since I was concentrating on the problem at hand.

I'd also like a target explicity for generating a dynamic plist that
runs after post-install.  Doing it in post-install works most of the
time unless you start using post-install option helpers to install
additional files.

> | One of my concerns is that if we start using TARGET_ORDER_OVERRIDE all
> | over the place, that will make maintaining the framework a lot more
> | difficult.
> 
> There's a difference between all over the place and in a dozen ports :-)
> (it only makes it about 0.05% of the time, if I get my math right)

Well, here are a bunch more ... these contain both INSTALLS_ICONS and
"autoplist", which I'm assuming comes from USES_GNOME=autoplist

audio/puddletag/Makefile
deskutils/gtg/Makefile
deskutils/rednotebook/Makefile
deskutils/syncthing-gtk/Makefile
deskutils/vboxgtk/Makefile
deskutils/virt-manager/Makefile
deskutils/zim/Makefile
devel/bzr-gtk/Makefile
devel/gaphor/Makefile
devel/qbzr/Makefile
games/pyspacewar/Makefile
multimedia/tovid/Makefile
net-im/turpial/Makefile
net-p2p/deluge/Makefile
print/frescobaldi/Makefile
www/linkchecker/Makefile
x11/hotwire-shell/Makefile

___
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: What is proper way to re-do "check-plist" after pkg-plist editing?

[Thierry Thomas]

Le lun 21 mar 16 à 20:29:10 +0100, Lev Serebryakov 
 écrivait :
> 
>  What should I call after I fixed issues in pkg-plist found by "make
> check-plist"? New "make check-plist" doesn't work for me.

Run `make restage' and then `make check-plist'.

Regards,
-- 
Th. Thomas.


pgpa2FymKYIS3.pgp
Description: PGP signature

Re: What is proper way to re-do "check-plist" after pkg-plist editing?

[Kurt Jaeger]

Hi!

>  What should I call after I fixed issues in pkg-plist found by "make
> check-plist"? New "make check-plist" doesn't work for me.

cd work
rm -rf .stage* stage
cd ..
make check-plist

There should be a target for this, like make recheck-plist or so 8-)

-- 
p...@opsec.eu+49 171 3101372 4 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"

What is proper way to re-do "check-plist" after pkg-plist editing?

[Lev Serebryakov]

 What should I call after I fixed issues in pkg-plist found by "make
check-plist"? New "make check-plist" doesn't work for me.

-- 
// Lev Serebryakov



signature.asc
Description: OpenPGP digital signature

Re: gnome-post-install ordering

[Mathieu Arnold]

+--On 21 mars 2016 11:18:26 -0700 Don Lewis  wrote:
| gnome-post-install does several different things.  I haven't looked to
| see if all of them should be moved.  Unfortunately I'm not sure that an
| exp-run would pick up some of the more subtle breakage.

Then, we just extract the INSTALL_ICONS bits into a gnome-install-icons
target, and run it later, much later.  The gnome-post-install target could
benefit from being split up.  It was not so before because USES=gnome is
quite new, and adding stuff to the target ordering system was a pain. Now,
it could be splitted in gnome-gconf-schemas, gnome-glib-schemas,
gnome-installs-omf, and gnome-install-icons.  It was on my roadmap when I
rewrote the target ordering system to use numbers, but I decided against
changing too many things at once.

| One of my concerns is that if we start using TARGET_ORDER_OVERRIDE all
| over the place, that will make maintaining the framework a lot more
| difficult.

There's a difference between all over the place and in a dozen ports :-)
(it only makes it about 0.05% of the time, if I get my math right)

-- 
Mathieu Arnold

pgpDMVpkRvI0a.pgp
Description: PGP signature

Re: clamav problem

[Kurt Jaeger]

Hi!

> >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542  
> >> 
> >> For whatever reason, I keep getting this error message when I try an
> >> access that report:
> >> 
> >> You are not authorized to access bug #11542.   

> >Yes. It seems clamav bugzilla is restrictive and I can not change
> >that, as submitter of that bug.
> 
> Now that makes about "ZERO" sense. Why would you (meaning clamav) want
> to hide bug information? Dumbest thing I ever saw (almost).

I added you to the Cc: for this bug, so that you can see it.

-- 
p...@opsec.eu+49 171 3101372 4 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: gnome-post-install ordering

[Don Lewis]

On 21 Mar, Mathieu Arnold wrote:
> +--On 16 mars 2016 10:57:54 -0700 Don Lewis  wrote:
> | I'm trying to debug why gtk-update-icon-cache isn't getting run when
> | the OpenOffice package is installed and ran into something that I don't
> | understand.
> | 
> | The Makefile contains INSTALLS_ICONS=yes, which has the side effect of
> | setting USES+=gnome, USE_GNOME+=gtk-update-icon-cache, and
> | _USES_install+=690:gnome-post-install, and that target is responsible
> | for parsing ${TMPPLIST} and invoking gtk-update-icon-cache as needed.
> | I do see gtk-update-icon-cache in the dependency list in +MANIFEST, so
> | it appears that INSTALLS_ICONS=yes is being detected.
> | 
> | It appears that things go wrong because I'm using the Makefile
> | post-install target to generate the plist.  If I look at bsd.port.mk, I
> | see that _STAGE_SEQ contains 700:post-install.  It looks to me like
> | gnome-post-install is getting run before the plist is generated, which
> | would explain why gnome-post-install isn't detecting any icons and not
> | invoking gtk-update-icon-cache.
> | 
> | Why is gnome-post-install earlier than post-install, which at least some
> | ports use to do plist generation?  Some ports do plist generation in
> | do-install, but that doesn't work if there are do-install option helpers
> | because those get run after the main do-install target.
> | 
> | There is the TARGET_ORDER_OVERRIDE knob, but it is very lightly used.
> 
> It is there exactly for the problem you have, change the order targets are
> run for one port.
> 
> And it is very lightly used because it's only needed when you do some
> strange things that nobody else does ;-)
> 
> For example, I just added it to devel/p5-ReadLine-TTYtter because I needed
> to run post-install before fix-perl-things.  And it was ok to do it because
> it's a somewhat unique case.

I think that this particular instance is pretty subtle and may be more
widespread than you think.  It has taken a long time for someone to
notice the problem with openoffice and file a PR.  It looks like
editors/libreoffice also ran into this problem and "fixed" it by getting
rid of INSTALLS_ICONS and instead added a new tarket that adds the stuff
to TMPPLIST to run gtk-update-icon-cache, and adds that target to
${POST_PLIST}.

These other port Makefiles also use INSTALLS_ICONS and are doing
something with TMPPLIST, so they may also need to use
TARGET_ORDER_OVERRIDE:

  editors/libreoffice4/Makefile
  games/openttd/Makefile
  games/rocksndiamonds/Makefile
  multimedia/qmmp-qt5/Makefile
  multimedia/qmmp/Makefile
  multimedia/vlc/Makefile
  x11-themes/gnome-icons-faenza/Makefile

The previous person to reply to this thread mentioned the case of 
USES=python:autoplist, which generates the plist *very* late.

Running fix-perl-things after post-install seems like a very resonable
default.  I think there are quite a few ports that use the default
do-install target and then fiddle around with the contents of
${STAGEDIR} in post-install.

> So, basically, you need to put:
> 
> TARGET_ORDER_OVERRIDE= 650:post-install
> 
> so that it's ran before gnome-post-install, and you're set.

Changing the sequence number of post-install isn't a good general fix
because that doesn't change the order of post-install-OPTION-on to match.
 
> Now, I don't have a problem with moving gnome-post-install after
> post-install (like, 710), which would also fix your problem, but it will
> need an exp-run to make sure nothing breaks.

gnome-post-install does several different things.  I haven't looked to
see if all of them should be moved.  Unfortunately I'm not sure that an
exp-run would pick up some of the more subtle breakage.

One of my concerns is that if we start using TARGET_ORDER_OVERRIDE all
over the place, that will make maintaining the framework a lot more
difficult.  I think we need to try to get the defaults right for more
cases.  That requires taking a step back and looking at when things get
done in the install phase and when are they needed.  We need to be able
to define when all the files and directories need to be present in
${STAGEDIR}.  We can't generate a dynamic plist until after that step.
Also, tasks like fix-perl-things shouldn't run until after that.  How do
the last two items interact?  When can we count on all files and
directories being in the plist?  Parsing the plist, as is done by
gnome-post-install shouldn't be done until after that point.

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

devel/poco (Re: FreeBSD ports you maintain which are out of date)

[Mikhail T.]

On 21.03.2016 04:52, portsc...@freebsd.org wrote:
> devel/poco  | 1.7.0   | 
> poco-1.7.2-release
Whoever takes this on, please, watch:

https://github.com/pocoproject/poco/issues/1208

Yours,

-mi

___
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: gnome-post-install ordering

[Mathieu Arnold]

+--On 16 mars 2016 10:57:54 -0700 Don Lewis  wrote:
| I'm trying to debug why gtk-update-icon-cache isn't getting run when
| the OpenOffice package is installed and ran into something that I don't
| understand.
| 
| The Makefile contains INSTALLS_ICONS=yes, which has the side effect of
| setting USES+=gnome, USE_GNOME+=gtk-update-icon-cache, and
| _USES_install+=690:gnome-post-install, and that target is responsible
| for parsing ${TMPPLIST} and invoking gtk-update-icon-cache as needed.
| I do see gtk-update-icon-cache in the dependency list in +MANIFEST, so
| it appears that INSTALLS_ICONS=yes is being detected.
| 
| It appears that things go wrong because I'm using the Makefile
| post-install target to generate the plist.  If I look at bsd.port.mk, I
| see that _STAGE_SEQ contains 700:post-install.  It looks to me like
| gnome-post-install is getting run before the plist is generated, which
| would explain why gnome-post-install isn't detecting any icons and not
| invoking gtk-update-icon-cache.
| 
| Why is gnome-post-install earlier than post-install, which at least some
| ports use to do plist generation?  Some ports do plist generation in
| do-install, but that doesn't work if there are do-install option helpers
| because those get run after the main do-install target.
| 
| There is the TARGET_ORDER_OVERRIDE knob, but it is very lightly used.

It is there exactly for the problem you have, change the order targets are
run for one port.

And it is very lightly used because it's only needed when you do some
strange things that nobody else does ;-)

For example, I just added it to devel/p5-ReadLine-TTYtter because I needed
to run post-install before fix-perl-things.  And it was ok to do it because
it's a somewhat unique case.

So, basically, you need to put:

TARGET_ORDER_OVERRIDE= 650:post-install

so that it's ran before gnome-post-install, and you're set.

Now, I don't have a problem with moving gnome-post-install after
post-install (like, 710), which would also fix your problem, but it will
need an exp-run to make sure nothing breaks.

-- 
Mathieu Arnold

pgpqWlMUH1iO1.pgp
Description: PGP signature

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
+-+
devel/poco  | 1.7.0   | 
poco-1.7.2-release
+-+


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"

FreeBSD Port: cgilib-0.7

[Sergei Tsetlin]

--- cgi.h.orig	2008-04-06 13:43:42.0 +0400
+++ cgi.h	2016-03-18 01:18:48.0 +0400
@@ -143,7 +143,7 @@
 char *cgiEscape (char *string);
 
 #ifdef __cplusplus
-extern }
+}
 #endif
 
 #endif /* _CGI_H_ */
___
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"