INDEX build failed for 11.x

2021-01-01 Thread Ports Index build
INDEX build failed with errors:
Generating INDEX-11 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
--- describe.dns ---
--- describe.editors ---
--- describe.databases ---
make[5]: "/home/indexbuild/tindex/ports/databases/pypy-gdbm/Makefile" line 17: 
Cannot open 
/home/indexbuild/tindex/ports/databases/pypy-gdbm/../../lang/pypy/bsd.pypy.cffi.mk
make[5]: Fatal errors encountered -- cannot continue===> databases/pypy-gdbm 
failed
*** [describe.databases] Error code 1
[...]
--- describe.devel ---
make[6]: 
"/home/indexbuild/tindex/ports/devel/py-subversion/../../devel/subversion/Makefile.addons"
 line 30: Cannot open 
/home/indexbuild/tindex/ports/devel/py-subversion/../../devel/subversion-lts/Makefile.common
make[6]: "/home/indexbuild/tindex/ports/Mk/bsd.port.mk" line 1842: Malformed 
conditional (${WITH_PKG} == devel)
make[6]: "/home/indexbuild/tindex/ports/Mk/bsd.port.mk" line 2179: Malformed 
conditional (${PREFIX} == /usr)
make[6]: "/home/indexbuild/tindex/ports/Mk/bsd.port.mk" line 2698: Malformed 
conditional (${PREFIX} == /usr)
make[6]: "/home/indexbuild/tindex/ports/Mk/bsd.port.mk" line 4575: Malformed 
conditional ((${PREFIX} != ${LOCALBASE} && ${PREFIX} != ${LINUXBASE} &&  
${PREFIX} != "/usr" && ${PREFIX} != "/" && !defined(NO_PREFIX_RMDIR)))
make[6]: Fatal errors encountered -- cannot continue===> devel/py-subversion 
failed
*** [describe.devel] Error code 1

make[2]: stopped in /home/indexbuild/tindex/ports

make[2]: stopped in /home/indexbuild/tindex/ports
*** Error code 1

Stop.
make[1]: stopped in /home/indexbuild/tindex/ports
*** Error code 1

Stop.
make: stopped in /home/indexbuild/tindex/ports
3 errors

Committers on the hook:
 eugen gerald jhale jrm leres matthew mfechner novel pkubaj rene samm yuri 

Most recent SVN update was:
Updating '.':
Udatabases/rubygem-gitlab-pg_query/Makefile
Udatabases/rubygem-gitlab-pg_query/distinfo
Udatabases/rubygem-gitlab-pg_query/files/patch-ext_pg__query_extconf.rb
Udatabases/libpg_query/Makefile
Udatabases/libpg_query/distinfo
Umath/Makefile
Amath/sympol
Amath/sympol/Makefile
Amath/sympol/distinfo
Amath/sympol/files
Amath/sympol/files/patch-CMakeLists.txt
Amath/sympol/pkg-descr
Amath/sympol/pkg-plist
Amath/permlib
Amath/permlib/Makefile
Amath/permlib/distinfo
Amath/permlib/files
Amath/permlib/files/patch-CMakeLists.txt
Amath/permlib/files/patch-boost-from-arch
Amath/permlib/pkg-descr
Amath/permlib/pkg-plist
Uwww/qutebrowser/Makefile
Uwww/qutebrowser/distinfo
Umail/msmtp/Makefile
Umail/msmtp/distinfo
Dmail/msmtp/files/patch-src_net.c
Amail/msmtp/files/patch-src_msmtpd.c
Updated to revision 559813.
___
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: Committing New Ports on Bugzilla

2021-01-01 Thread Kurt Jaeger
Hi!

>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252314
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252226
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252224
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252223
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252185
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252151
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252152
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252150
> 
> Could one of you please commit these New Ports?

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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"


INDEX now builds successfully on 11.x

2021-01-01 Thread Ports Index build


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


Can someone please have a look at a few PRs

2021-01-01 Thread Daniel Engberg

Hi,

I know it's easy to miss PRs so this is just a friendly reminder of a 
few PRs that I'd appreciate if someone could have a look at.


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245930 - 
security/py-openssl: Update to 19.1.0 (maintainer timeout, maintainer 
feedback ok)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250985 - 
multimedia/libaacs: Update to 0.11.0  (no maintainer)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250986 - 
multimedia/libbdplus: Makefile cleanup  (no maintainer)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250988 - 
multimedia/libbluray: Update to 1.2.1 (no maintainer)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251357 - 
textproc/utf8proc: Update to 2.6.1 (maintainer timeout)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251890 - 
multimedia/oscam: Update to latest commit 2020-11-19 (maintainer 
feedback ok)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251989 - 
net-mgmt/netdata: Update to 1.28.0 (no maintainer)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252112 - print/libotf: 
Don't use freetype-config (maintainer feedback ok)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252114 - 
graphics/libwmf: Update to 0.2.12 (no maintainer)


Happy new year 2021! :-)

Best regards,
Daniel
___
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: Can someone please have a look at a few PRs

2021-01-01 Thread Kurt Jaeger
Hi!

> I know it's easy to miss PRs so this is just a friendly reminder of a few
> PRs that I'd appreciate if someone could have a look at.

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread George Mitchell

I applied the patch from https://reviews.freebsd.org/D27846 to my ports
tree and recompiled with no problems.  But it did not change the compose
key behavior (still fails in xfce4-terminal but works elsewhere).
-- George



OpenPGP_signature
Description: OpenPGP digital signature


Re: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread Guido Falsi via freebsd-ports

On 01/01/21 20:12, George Mitchell wrote:

I applied the patch from https://reviews.freebsd.org/D27846 to my ports
tree and recompiled with no problems.  But it did not change the compose
key behavior (still fails in xfce4-terminal but works elsewhere).


I actually have no idea. I don't know exactly how the compose key is 
managed in Xorg.


My intuition is it's Xorg itself who is managing it, intercepting the 
key presses before the application and sending it the result if any. But 
I don't know for sure.


Also maybe the setting can be per application. Have you tried 
configuring the compose key in XFCE settings?


Or setting it via command line before launching startxfce4?


--
Guido Falsi 
___
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: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread George Mitchell

On 1/1/21 2:57 PM, Guido Falsi via freebsd-ports wrote:

On 01/01/21 20:12, George Mitchell wrote:

I applied the patch from https://reviews.freebsd.org/D27846 to my ports
tree and recompiled with no problems.  But it did not change the compose
key behavior (still fails in xfce4-terminal but works elsewhere).


I actually have no idea. I don't know exactly how the compose key is 
managed in Xorg.


My intuition is it's Xorg itself who is managing it, intercepting the 
key presses before the application and sending it the result if any. But 
I don't know for sure.


Also maybe the setting can be per application. Have you tried 
configuring the compose key in XFCE settings?


Or setting it via command line before launching startxfce4?



I've been setting it in .csrhc (setxkbmap -option compose:lwin), and
originally worked for everything including xfce4-terminal.  It still
works for everything else (including mousepad), but not for
xfce4-terminal.  The XFCE keyboard settings compose key setting does
not seem to work for anything.-- George



OpenPGP_signature
Description: OpenPGP digital signature


Re: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread Guido Falsi via freebsd-ports

On 01/01/21 21:09, George Mitchell wrote:

On 1/1/21 2:57 PM, Guido Falsi via freebsd-ports wrote:

On 01/01/21 20:12, George Mitchell wrote:

I applied the patch from https://reviews.freebsd.org/D27846 to my ports
tree and recompiled with no problems.  But it did not change the compose
key behavior (still fails in xfce4-terminal but works elsewhere).


I actually have no idea. I don't know exactly how the compose key is 
managed in Xorg.


My intuition is it's Xorg itself who is managing it, intercepting the 
key presses before the application and sending it the result if any. 
But I don't know for sure.


Also maybe the setting can be per application. Have you tried 
configuring the compose key in XFCE settings?


Or setting it via command line before launching startxfce4?



I've been setting it in .csrhc (setxkbmap -option compose:lwin), and
originally worked for everything including xfce4-terminal.  It still
works for everything else (including mousepad), but not for
xfce4-terminal.  The XFCE keyboard settings compose key setting does
not seem to work for anything.    -- George



.cshrc does not look like the correct place for it anyway. That file is 
executed multiple times during a session. I'm not sure how it can work 
for everything else. Also the fact that XFCE has it's own configuration, 
if it's not configured from there could cause conflicts.


IMHO a better place would be .xsession if using a display manager or 
Xinit if using startx.


If using XFCE as your DE it's own settings tool would be the best place.

--
Guido Falsi 
___
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: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread George Mitchell

On 1/1/21 3:12 PM, Guido Falsi via freebsd-ports wrote:

[...]
.cshrc does not look like the correct place for it anyway. That file is 
executed multiple times during a session. I'm not sure how it can work 
for everything else. Also the fact that XFCE has it's own configuration, 
if it's not configured from there could cause conflicts.


IMHO a better place would be .xsession if using a display manager or 
Xinit if using startx.


If using XFCE as your DE it's own settings tool would be the best place.



Regardless of where I put setxkbmap, xev shows this sequence of events
when I type the compose key (Left Win), ', and e to enter "é":

KeyPress event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 89630, (34,51), root:(905,493),
 state 0x10, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
 XLookupString gives 0 bytes:
 XmbLookupString gives 0 bytes:
 XFilterEvent returns: True

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 89758, (34,51), root:(905,493),
 state 0x10, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
 XLookupString gives 0 bytes:
 XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 92574, (34,51), root:(905,493),
 state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
 XLookupString gives 1 bytes: (27) "'"
 XmbLookupString gives 1 bytes: (27) "'"
 XFilterEvent returns: True

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 92750, (34,51), root:(905,493),
 state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
 XLookupString gives 1 bytes: (27) "'"
 XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 98926, (34,51), root:(905,493),
 state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
 XLookupString gives 1 bytes: (65) "e"
 XmbLookupString gives 1 bytes: (65) "e"
 XFilterEvent returns: True

KeyPress event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 98926, (34,51), root:(905,493),
 state 0x10, keycode 0 (keysym 0xe9, eacute), same_screen YES,
 XLookupString gives 0 bytes:
 XmbLookupString gives 1 bytes: (e9) "�"
 XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
 root 0x50f, subw 0x2e2, time 99062, (34,51), root:(905,493),
 state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
 XLookupString gives 1 bytes: (65) "e"
 XFilterEvent returns: False

The same sequence in an xfce4-terminal window shows nothing, but
any following keypresses act normally.

I removed the setxkbmap command from my .cshrc and used the XFCE
keyboard settings to set the compose key to Left Win.  Then I logged
out and back in.  I verified that the keyboard settings dialog still
showed that Left Win was used for the compose key.  But it does not
work at all.  When I type Left Win, ', e in xfce4-terminal (or in
any other client in my session), it shows 'e.  Xev shows the three
keypresses and releases but no e with acute accent.  -- George



OpenPGP_signature
Description: OpenPGP digital signature


Re: Xfce, xfce4-terminal, and UTF-8

2021-01-01 Thread Guido Falsi via freebsd-ports

On 01/01/21 23:37, George Mitchell wrote:

On 1/1/21 3:12 PM, Guido Falsi via freebsd-ports wrote:

[...]
.cshrc does not look like the correct place for it anyway. That file 
is executed multiple times during a session. I'm not sure how it can 
work for everything else. Also the fact that XFCE has it's own 
configuration, if it's not configured from there could cause conflicts.


IMHO a better place would be .xsession if using a display manager or 
Xinit if using startx.


If using XFCE as your DE it's own settings tool would be the best place.



Regardless of where I put setxkbmap, xev shows this sequence of events
when I type the compose key (Left Win), ', and e to enter "é":

KeyPress event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 89630, (34,51), root:(905,493),
  state 0x10, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: True

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 89758, (34,51), root:(905,493),
  state 0x10, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 92574, (34,51), root:(905,493),
  state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
  XLookupString gives 1 bytes: (27) "'"
  XmbLookupString gives 1 bytes: (27) "'"
  XFilterEvent returns: True

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 92750, (34,51), root:(905,493),
  state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
  XLookupString gives 1 bytes: (27) "'"
  XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 98926, (34,51), root:(905,493),
  state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
  XLookupString gives 1 bytes: (65) "e"
  XmbLookupString gives 1 bytes: (65) "e"
  XFilterEvent returns: True

KeyPress event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 98926, (34,51), root:(905,493),
  state 0x10, keycode 0 (keysym 0xe9, eacute), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 1 bytes: (e9) "�"
  XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2e1,
  root 0x50f, subw 0x2e2, time 99062, (34,51), root:(905,493),
  state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
  XLookupString gives 1 bytes: (65) "e"
  XFilterEvent returns: False

The same sequence in an xfce4-terminal window shows nothing, but
any following keypresses act normally.

I removed the setxkbmap command from my .cshrc and used the XFCE
keyboard settings to set the compose key to Left Win.  Then I logged
out and back in.  I verified that the keyboard settings dialog still
showed that Left Win was used for the compose key.  But it does not
work at all.  When I type Left Win, ', e in xfce4-terminal (or in
any other client in my session), it shows 'e.  Xev shows the three
keypresses and releases but no e with acute accent.  -- George



From what you say it looks like xfce4-terminal is getting the special 
character you typed but is ignoring it or unable to display it for some 
reason.


If you think there is a bug in xfce4-terminal you should file a bug with 
upstream directly.


I'm sorry I have no idea where the blame is, I don't know how 
composition is actually implemented, here it just works for me.


Also make sure all your ports are aligned, I use binary packages from my 
own repo. I did have a glitch with composition (it was not working, much 
like you report above after setting it in xfce preferences) and forcing 
reinstallation of many Xorg and XFCE4 related ports "fixed" it. I 
usually think this is due to package upgrading libraries from below 
other packages and some hidden/unwanted binary compatibility change in 
the library.


This is quite a difficult one to diagnose!

--
Guido Falsi 
___
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

2021-01-01 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
+-+
lang/csharp-mode.el | 0.9.2   | v0.11.0
+-+
net/libilbc | 3.0.3   | v3.0.4
+-+
science/afni| 20.3.04 | afni_20.3.05
+-+
www/gophernicus | 3.0.1   | 3.1
+-+


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

Reported by:portscout!
___
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"


Looking at a few Ports updates and adoptions

2021-01-01 Thread Neel Chauhan

Hi freebsd-ports@,

If one of you don't mind, could you please commit these following Ports 
updates (and one adoption)?


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

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

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

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

-Neel
___
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: Looking at a few Ports updates and adoptions

2021-01-01 Thread Neel Chauhan

While you're at it, could you also look at:

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

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

-Neel

On 2021-01-01 19:16, Neel Chauhan wrote:

Hi freebsd-ports@,

If one of you don't mind, could you please commit these following
Ports updates (and one adoption)?

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

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

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

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

-Neel
___
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: Committing New Ports on Bugzilla

2021-01-01 Thread Neel Chauhan

Thanks!

-Neel

On 2021-01-01 02:07, Kurt Jaeger wrote:

Hi!


 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252314
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252226
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252224
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252223
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252185
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252151
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252152
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252150

Could one of you please commit these New Ports?


Done.

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