www/mod_authz_unixgroup24 is not gone, just moved

2017-05-04 Thread Burns, Tyler 
Hello,

I noticed the apache unix group module was removed from ports:

[tburns@repo /usr/ports]$ pwd
/usr/ports
[tburns@repo /usr/ports]$ grep -n unixgroup MOVED
7099:www/mod_authz_unixgroup|www/mod_authz_unixgroup22|2014-10-26|Reflect 
Apache version in portsdir
9298:www/mod_authz_unixgroup24||2017-04-30|Has expired: Unfetchable for more 
than six months (google code has gone away)
9311:www/mod_authz_unixgroup22||2017-04-30|Has expired: Unfetchable for more 
than six months (google code has gone away)

Here is the github URL:

https://github.com/phokz/mod-auth-external/tree/master/mod_authz_unixgroup

Thanks,

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

2017-05-04 Thread 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/tass64| 1.51.727| 1.53.1515
+-+


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: pkg and packages

2017-05-04 Thread RW via freebsd-ports 
On Thu, 04 May 2017 07:43:30 -0600
Jim Trigg wrote:

> ISTR that it's Thunar that depends on Samba by default.

Yes it looks like it came in when Thunar defaulted to depending on the
"Trash Panel Applet Plugin". Unfortunately the options framework
caches old defaults.
___
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: pkg and packages

2017-05-04 Thread Jim Trigg 
ISTR that it's Thunar that depends on Samba by default.

Jim


On May 4, 2017 7:18:46 AM MDT, RW via freebsd-ports  
wrote:
>On Thu, 04 May 2017 08:09:47 -0400
>scratch65...@att.net wrote:
>> 
>> I can't imagine what code could possibly be in thunar and samba
>> that the xfce desktop would need, particularly since the desktop
>> is very simple, and also because I've never got samba
>> functionality for free after installing xfce which if you're
>> right I should have done.  But I'll check on that, and report
>> back.  
>
>AFAIK samba isn't a dependency of XFCE. I don't have it and it's not in
>the output of make all-depends-list.
>
>Thunar is scarcely "unrelated", it's the XFCE integrated file manager.
>XFCE uses the  libthunarx library if built with the Thunar option.
>
>If you want something without integrated utilities you might be better
>off with a window manager, like Fluxbox, rather than a desktop
>environment. 
>
>It is possible to have XFCE without THUNAR from ports, or by building
>custom packages.   
>___
>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"

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
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: does inkscape-0.92.0_1 works for you ?

2017-05-04 Thread Patrick Lamaiziere 
Le Thu, 4 May 2017 10:47:56 +0200,
Patrick Lamaiziere  a écrit :

> Hello,
> 
> I've upgraded my workstation (10.3-STABLE / amd64) via poudriere and
> ports svn://svn0.eu.freebsd.org/ports/branches/2017Q2 (rev 440002) and
> inkscape does not work anymore and fails with a segfault.
> 
> $ inkscape
> (inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL'
> failed ...
> (inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL'
> failed ...
> Emergency save activated!
> Emergency save completed. Inkscape will close now.
> If you can reproduce this crash, please file a bug at www.inkscape.org
> with a detailed description of the steps leading to the crash, so we
> can fix it. Incident de segmentation

It appears to be a problem when my locales are in fr_FR.ISO8859-15.
That works fine with locales in fr_FR.UTF-8.

I don't know if the problem depends directly on Inkscape.
The previous version was inkscape-0.91_8 and worked fine.

(I will keep fr_FR.utf-8 because i've got many linux using UTF-8 here
and that looks better in xterm)

Thanks to all
Best regards,

___
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: pkg and packages

2017-05-04 Thread RW via freebsd-ports 
On Thu, 04 May 2017 08:09:47 -0400
scratch65...@att.net wrote:
> 
> I can't imagine what code could possibly be in thunar and samba
> that the xfce desktop would need, particularly since the desktop
> is very simple, and also because I've never got samba
> functionality for free after installing xfce which if you're
> right I should have done.  But I'll check on that, and report
> back.  

AFAIK samba isn't a dependency of XFCE. I don't have it and it's not in
the output of make all-depends-list.

Thunar is scarcely "unrelated", it's the XFCE integrated file manager.
XFCE uses the  libthunarx library if built with the Thunar option.

If you want something without integrated utilities you might be better
off with a window manager, like Fluxbox, rather than a desktop
environment. 

It is possible to have XFCE without THUNAR from ports, or by building
custom packages.   
___
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: pkg and packages

2017-05-04 Thread Baptiste Daroussin 
On Thu, May 04, 2017 at 08:09:47AM -0400, scratch65...@att.net wrote:
> On Wed, 3 May 2017 16:53:41 +0100, Matthew Seaman
>  wrote:
> 
> >>> Trying to install the desktop package, I discovered that it's
> >>> bundled with at least 2 unrelated pieces of software:  Thunar,
> >>> and samba44.  That bothered me, but I needed the desktop.
> >
> >'Bundling' isn't the right term -- Thunar and samba44 are /dependencies/
> >of the xfce4-desktop.  That is: other packages that need to be installed
> >before the package in question will work.  Sorting out dependency trees
> >like this is much of what pkg(8) exists for.
> 
> I can't imagine what code could possibly be in thunar and samba
> that the xfce desktop would need, particularly since the desktop
> is very simple, and also because I've never got samba
> functionality for free after installing xfce which if you're
> right I should have done.  But I'll check on that, and report
> back.  
> 
> That kind of tight coupling at the macro level *is* a very
> serious problem for the ports system, though.  It's strangling
> it.
> 
> How many ports just build, first go?  Are there *any*?  I suspect
> not.  And yet the maintainers presumably thought they would.
> 
> I stopped trying to build ports because I could never get a make
> to run to completion.  There was always at least one dependency
> that (a) couldn't be found at all, (b) was the wrong version, or
> (c) failed compilation.  That didn't happen when I was writing
> stuff under sco or sys v.
> 
> It shouldn't happen with our ports system, either, because it
> completely prevents code freeze and stability, a basic
> requirement for high-quality software.   The stuff being fetched
> from Timbuktu or somebody's cat's litter box should be cleaned
> up, built into a library, and be fetched from there subsequently.
> There should never be a dependency on code that the ports project
> doesn't control.  
> 
> 
> >The thing that seems to trip most people up is thinking they can
> >substitute some other package instead of the exact dependency listed in
> >the package metadata.  This is not an unreasonable request, especially
> >when you know your alternate package does exactly the same thing as the
> >one you want to replace.  Unfortunately it just doesn't work right now,
> >and it would take quite a lot of disruptive change in the ports tree and
> >to pkg(8) itself to make that happen.
> 
> You call it "disruptive" change, but from  here it looks exactly
> like *healthy*, *professional* change.  Really.

There is no garanty the libsmb.so.X provided by samba44 is binary compatible
with the one from samba46 this is why there is a strong dependency here.

For more defaly look at my answer here
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219036

Bapt


signature.asc
Description: PGP signature

Re: pkg and packages

2017-05-04 Thread scratch65535 
On Wed, 3 May 2017 16:53:41 +0100, Matthew Seaman
 wrote:

>>> Trying to install the desktop package, I discovered that it's
>>> bundled with at least 2 unrelated pieces of software:  Thunar,
>>> and samba44.  That bothered me, but I needed the desktop.
>
>'Bundling' isn't the right term -- Thunar and samba44 are /dependencies/
>of the xfce4-desktop.  That is: other packages that need to be installed
>before the package in question will work.  Sorting out dependency trees
>like this is much of what pkg(8) exists for.

I can't imagine what code could possibly be in thunar and samba
that the xfce desktop would need, particularly since the desktop
is very simple, and also because I've never got samba
functionality for free after installing xfce which if you're
right I should have done.  But I'll check on that, and report
back.  

That kind of tight coupling at the macro level *is* a very
serious problem for the ports system, though.  It's strangling
it.

How many ports just build, first go?  Are there *any*?  I suspect
not.  And yet the maintainers presumably thought they would.

I stopped trying to build ports because I could never get a make
to run to completion.  There was always at least one dependency
that (a) couldn't be found at all, (b) was the wrong version, or
(c) failed compilation.  That didn't happen when I was writing
stuff under sco or sys v.

It shouldn't happen with our ports system, either, because it
completely prevents code freeze and stability, a basic
requirement for high-quality software.   The stuff being fetched
from Timbuktu or somebody's cat's litter box should be cleaned
up, built into a library, and be fetched from there subsequently.
There should never be a dependency on code that the ports project
doesn't control.  


>The thing that seems to trip most people up is thinking they can
>substitute some other package instead of the exact dependency listed in
>the package metadata.  This is not an unreasonable request, especially
>when you know your alternate package does exactly the same thing as the
>one you want to replace.  Unfortunately it just doesn't work right now,
>and it would take quite a lot of disruptive change in the ports tree and
>to pkg(8) itself to make that happen.

You call it "disruptive" change, but from  here it looks exactly
like *healthy*, *professional* change.  Really.

Slàinte mhath!
___
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: does inkscape-0.92.0_1 works for you ?

2017-05-04 Thread Jan Beich 
Patrick Lamaiziere  writes:

> I've upgraded my workstation (10.3-STABLE / amd64) via poudriere and
> ports svn://svn0.eu.freebsd.org/ports/branches/2017Q2 (rev 440002) and
> inkscape does not work anymore and fails with a segfault.

inkscape-0.92.0_1 from either /latest or /quarterly binary package repo
seems to work fine here inside 10.3R amd64 jail on 12.0C amd64 kernel.

Not enough details about environment to reproduce.

>
> $ inkscape
> (inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed

This is probably precursor to the crash. Build WITH_DEBUG=1 the port
itself and all library dependencies then try

  $ G_DEBUG=fatal_warnings gdb inkscape
  (gdb) run
  
  (gdb) backtrace

> ...
> (inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed
> ...
> Emergency save activated!
> Emergency save completed. Inkscape will close now.
> Incident de segmentation
>
> Any clue ?

- Try removing ~/.config/inkscape and ~/.cache/inkscape
- Try force-rebuilding all dependencies
- Try running from a pristine jail
- Try bisecting if you know which version last worked
- Look at backtrace for more clues
___
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: does inkscape-0.92.0_1 works for you ?

2017-05-04 Thread Rainer Hurling 

Am 04.05.2017 um 10:47 schrieb Patrick Lamaiziere:

Hello,

I've upgraded my workstation (10.3-STABLE / amd64) via poudriere and
ports svn://svn0.eu.freebsd.org/ports/branches/2017Q2 (rev 440002) and
inkscape does not work anymore and fails with a segfault.


Works for me on recent 12.0-CURRENT amd64, build and installed from 
ports (HEAD) via portmaster.


HTH,
Rainer



$ inkscape
(inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed
...
(inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed
...
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Incident de segmentation

Any clue ?

Thanks, regards.

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

does inkscape-0.92.0_1 works for you ?

2017-05-04 Thread Patrick Lamaiziere 
Hello,

I've upgraded my workstation (10.3-STABLE / amd64) via poudriere and
ports svn://svn0.eu.freebsd.org/ports/branches/2017Q2 (rev 440002) and
inkscape does not work anymore and fails with a segfault.

$ inkscape
(inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed
...
(inkscape:1234): GLib-CRITICAL **: g_convert: assertion 'str != NULL' failed
...
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Incident de segmentation

Any clue ?

Thanks, regards.

___
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: diff and submissions

2017-05-04 Thread Kurt Jaeger 
Hi!

> I maintain and couple of ports and I submit patches for others
> every so often. The process of preparing a patch file is slightly
> awkward as documented [1]

> If we want to use the github pull process is that now possible?

It's not possible, but if you provide a link to the pull process
in a problem report at bugzilla.freebsd.org, this might work, even
if it takes a bit more work.

> There are 61 pull requests here:
> https://github.com/freebsd/freebsd-ports/pulls

Yes, we're aware, but there's no automation that provides
a PR from a pull request. I vaguely remember that someone was working
on some stuff to get this, but I might mis-remember.

-- 
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: diff and submissions

2017-05-04 Thread Mathieu Arnold 
Le 04/05/2017 à 09:58, Aristedes Maniatis a écrit :
> I maintain and couple of ports and I submit patches for others every so 
> often. The process of preparing a patch file is slightly awkward as 
> documented [1]
>
> If we want to use the github pull process is that now possible? There are 61 
> pull requests here: https://github.com/freebsd/freebsd-ports/pulls


Right now, using pull requests is not supported, the problem is that
they cannot be disabled on Github. If you open one, it will take a very
long time to be seen and most certainly closed with saying "please open
a PR on bugzilla". We have a "github issue" -> "bugzilla" tool in the
work, but it is not ready yet.

If you went as far as being able to create a pull request, you can do a
git show HEAD or git diff origin/trunk...HEAD and submit that in the
FreeBSD PR as well.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

diff and submissions

2017-05-04 Thread Aristedes Maniatis 
I maintain and couple of ports and I submit patches for others every so often. 
The process of preparing a patch file is slightly awkward as documented [1]

If we want to use the github pull process is that now possible? There are 61 
pull requests here: https://github.com/freebsd/freebsd-ports/pulls


Ari



[1] https://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html

-- 
-->
Aristedes Maniatis
CEO, ish
https://www.ish.com.au
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A



signature.asc
Description: OpenPGP digital signature