On Thu, November 1, 2018 04:18, Paul B. Henson wrote:
> For the past few years every time a new release came out, I've submitted
> this package and it's dep for potential inclusion in ports... I guess
> nobody's interested, so after this try I suppose I'll just maintain it
> locally and stop submitting it.
>
> Thanks...
>
Hi!
- HOMEPAGE and MASTER_SITES could be switched to https.
- Missing license marker.
- NO_BUILD=Yes and PKG_ARCH=* should be set
Other than this looks good port-wise
Wednesday, October 31, 2018
Re: New policy for mercurial extensions
On Wed, Oct 31, 2018 at 11:42:35PM +0100, Juan Francisco Cantero Hurtado wrote:
> For the last 6 months I've not updated the mercurial package to the
> recent major versions because py-hg-git was not compatible. The
> mercurial package contains code exposed to the network and I don't feel
> comfortable backporting bugfixes just because some extensions are not
> compatible with the recent API changes.
>
> Mercurial 4.8 will include a lot of good changes and I don't want to put
> on hold another version. In the next days, I will remove any broken
> extension. I will do the same in the future for new mercurial versions.
>
> This wiki explains how to keep a local copy in your home of the
> extensions which are not available from ports:
>
> https://www.mercurial-scm.org/wiki/UsingExtensions#Enabling_an_extension
>
> I will ask for OKs for the deletion of packages with active maintainers
> and will remove directly the ports with unactive maintainers. I will try
> to update the extensions with a new version available but I will not try
> too hard.
Just for information, regarding devel/py-hgnested, which I have proposed
to import, I don't use it anymore. So if nobody else use it, it could be
removed if it cause any problem.
I used it for Tryton (www.tryton.org), but the project switched to
another repository layout to avoid relying on an extension using
mercurial internals (and broken often at mercurial major changes).
Thanks.
--
Sebastien Marie
> For the last 6 months I've not updated the mercurial package to the
> recent major versions because py-hg-git was not compatible. The
> mercurial package contains code exposed to the network and I don't feel
> comfortable backporting bugfixes just because some extensions are not
> compatible with the recent API changes.
>
> Mercurial 4.8 will include a lot of good changes and I don't want to put
> on hold another version. In the next days, I will remove any broken
> extension. I will do the same in the future for new mercurial versions.
>
> This wiki explains how to keep a local copy in your home of the
> extensions which are not available from ports:
>
> https://www.mercurial-scm.org/wiki/UsingExtensions#Enabling_an_extension
>
> I will ask for OKs for the deletion of packages with active maintainers
> and will remove directly the ports with unactive maintainers. I will try
> to update the extensions with a new version available but I will not try
> too hard.
Just for information, regarding devel/py-hgnested, which I have proposed
to import, I don't use it anymore. So if nobody else use it, it could be
removed if it cause any problem.
I used it for Tryton (www.tryton.org), but the project switched to
another repository layout to avoid relying on an extension using
mercurial internals (and broken often at mercurial major changes).
Thanks.
--
Sebastien Marie
Which key shortcuts are safe to bind and some Q:s about history and OS diffs Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On Thursday, November 1, 2018 2:15 AM, Christian Weisgerber <naddy@mips.inka.de> wrote:
> On 2018-10-31, Stuart Henderson stu@spacehopper.org wrote:
>
> > No idea how ^4 is mapped to ^\, but for some reason it is,
>
> This goes back to the VT220, if not older terminals. Ctrl-3 for
> ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
> place as on most PC keyboards.
>
> See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
> the VT220 Programmer Reference Manual:
> https://vt100.net/docs/vt220-rm/table3-5.html
Historial reasons, a ha. Ok so this relates to a whole universe of
questions.
Is there a lot of effectively-unused legacy handling logics for
hardware that has not been manufactured for many decades, or is this
central today also?
Do unices e.g. OpenBSD/BSD, Linux, Solaris-whatever differ very much in
how they handle terminals?
Similar to how certain ctrl+ shortcut bindings are problematic, ESC is
also problematic as terminals easily confuse it right, e.g. ESC and
then rightarrow is easily confused for alt+rightarrow, right?
So this means that key bindings in your favourite console program, be
it KSH or TMUX or any other, better bind ctrl-shortcuts with great
discernment only, as they tend to have hardcoded lower-level terminal
behaviors so can't easily be preserved up to the tmux-etc. application
level and customized there, maybe you get it to work in a particular
setup but it would be fragile and maybe easily break when switching
terminal software or what not.
So binding ctrl+0-9 e.g. to switch windows is a bad idea.
More general-purpose are alt+ shortcuts e.g. alt+0-9.
Are shift+alt+-shortcuts, ctrl+shift+-, ctrl+alt+- shortcuts any
good, or any other control char I may not have thought of?
If I recall right, I did bind ctrl+0-9 successfully back in approx
OpenBSD 6.2 last year, from the latest Putty terminal then.
Did anything change in OpenBSD's terminal handling since then?
Last on this topic, are there any relevant terminal server-side
shortcut-related behaviors that can be tweaked in some environment
variable or configuration file?
Anyhow thanks for your comments, I think I kind of got the point about
what's safe and not safe shortcuts to bind.
If there are any further reading references or books on this topic feel
free to
share.
Thanks,
Tinker
> On 2018-10-31, Stuart Henderson stu@spacehopper.org wrote:
>
> > No idea how ^4 is mapped to ^\, but for some reason it is,
>
> This goes back to the VT220, if not older terminals. Ctrl-3 for
> ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
> place as on most PC keyboards.
>
> See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
> the VT220 Programmer Reference Manual:
> https://vt100.net/docs/vt220-rm/table3-5.html
Historial reasons, a ha. Ok so this relates to a whole universe of
questions.
Is there a lot of effectively-unused legacy handling logics for
hardware that has not been manufactured for many decades, or is this
central today also?
Do unices e.g. OpenBSD/BSD, Linux, Solaris-whatever differ very much in
how they handle terminals?
Similar to how certain ctrl+ shortcut bindings are problematic, ESC is
also problematic as terminals easily confuse it right, e.g. ESC and
then rightarrow is easily confused for alt+rightarrow, right?
So this means that key bindings in your favourite console program, be
it KSH or TMUX or any other, better bind ctrl-shortcuts with great
discernment only, as they tend to have hardcoded lower-level terminal
behaviors so can't easily be preserved up to the tmux-etc. application
level and customized there, maybe you get it to work in a particular
setup but it would be fragile and maybe easily break when switching
terminal software or what not.
So binding ctrl+0-9 e.g. to switch windows is a bad idea.
More general-purpose are alt+ shortcuts e.g. alt+0-9.
Are shift+alt+-shortcuts, ctrl+shift+-, ctrl+alt+- shortcuts any
good, or any other control char I may not have thought of?
If I recall right, I did bind ctrl+0-9 successfully back in approx
OpenBSD 6.2 last year, from the latest Putty terminal then.
Did anything change in OpenBSD's terminal handling since then?
Last on this topic, are there any relevant terminal server-side
shortcut-related behaviors that can be tweaked in some environment
variable or configuration file?
Anyhow thanks for your comments, I think I kind of got the point about
what's safe and not safe shortcuts to bind.
If there are any further reading references or books on this topic feel
free to
share.
Thanks,
Tinker
Re: NEW: sysutils/tenshi (and dep devel/p5-IO-BufferedSelect)
On Wed, Oct 31, 2018 at 06:18:26PM -0700, Paul B. Henson wrote:
> For the past few years every time a new release came out, I've submitted
> this package and it's dep for potential inclusion in ports... I guess
> nobody's interested, so after this try I suppose I'll just maintain it
> locally and stop submitting it.
>
> Thanks...
Your version of p5-IO-Buffered-Select doesn't have a MAINTAINER, but the
one that bluhm@ imported recently does, so I prefer his version.
tenshi seems interesting, but I don't currently have a use for it, so I
wasn't able to really test it out.
The port looks mostly OK, but I think sthen@ might have some style
suggestions and I don't know a lot about rc scripts or adding new users.
One thing I saw was that there are no regression tests, so probably it
needs "NO_TEST".
l8rZ,
--
andrew - http://afresh1.com
A printer consists of three main parts:
the case, the jammed paper tray and the blinking red light.
> For the past few years every time a new release came out, I've submitted
> this package and it's dep for potential inclusion in ports... I guess
> nobody's interested, so after this try I suppose I'll just maintain it
> locally and stop submitting it.
>
> Thanks...
Your version of p5-IO-Buffered-Select doesn't have a MAINTAINER, but the
one that bluhm@ imported recently does, so I prefer his version.
tenshi seems interesting, but I don't currently have a use for it, so I
wasn't able to really test it out.
The port looks mostly OK, but I think sthen@ might have some style
suggestions and I don't know a lot about rc scripts or adding new users.
One thing I saw was that there are no regression tests, so probably it
needs "NO_TEST".
l8rZ,
--
andrew - http://afresh1.com
A printer consists of three main parts:
the case, the jammed paper tray and the blinking red light.
sysutils/augeas - augtool gets killed if run in interactive mode
Hi all,
Running augtool in interactive mode, i.e. with '-i' or without any
command line options, produces this output:
$ augtool
augtool:/usr/lib/libreadline.so.4.0: undefined symbol 'tgetent'
ld.so: augtool: lazy binding failed!
Killed
Running augtool with, at least, some options, seems fine:
$ augtool print '/files/etc/ssh/sshd_config/Subsystem/sftp'
/files/etc/ssh/sshd_config/Subsystem/sftp = "/usr/libexec/sftp-server"
There's nothing in dmesg or system logs.
Recent ld change?
Regards,
Raf
Running augtool in interactive mode, i.e. with '-i' or without any
command line options, produces this output:
$ augtool
augtool:/usr/lib/libreadline.so.4.0: undefined symbol 'tgetent'
ld.so: augtool: lazy binding failed!
Killed
Running augtool with, at least, some options, seems fine:
$ augtool print '/files/etc/ssh/sshd_config/Subsystem/sftp'
/files/etc/ssh/sshd_config/Subsystem/sftp = "/usr/libexec/sftp-server"
There's nothing in dmesg or system logs.
Recent ld change?
Regards,
Raf
[UPDATE] devel/p5-Clone to 0.41
Most important change here is to fix the ". in @INC" requirement for
tests, but there is also a fix for some possible infinite loops.
https://metacpan.org/changes/distribution/Clone
OK?
Reverse dependency test results are the same, failures didn't change
from the old version.
* p5-Class-DBI-3.0.16
Needs some infrastructure fixes because it can't connect to mysql
* p5-HTML-FormFu-0.07003
Seems to need an update uses qw() as parens in a loop
* p5-Jifty-DBI-0.68
Seems to need an update as there are some syntax errors
* p5-Rose-DB-0.778
Seems to be missing some dependencies for tests to pass
* p5-Rose-DB-Object-0.815
Same as above
* p5-Rose-HTML-Objects-0.6061
Lots of warnings so it probably needs an update
* p5-SQL-Statement-1.407
Not really sure what's failing. "Non-zero wait status"
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/p5-Clone/Makefile,v
retrieving revision 1.25
diff -u -p -r1.25 Makefile
--- Makefile 20 Mar 2016 19:56:16 -0000 1.25
+++ Makefile 31 Oct 2018 00:38:13 -0000
@@ -3,7 +3,7 @@
COMMENT = recursively copy Perl datatypes
MODULES = cpan
-DISTNAME = Clone-0.38
+DISTNAME = Clone-0.41
CATEGORIES = devel
MAINTAINER = Andrew Fresh <afresh1@openbsd.org>
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-Clone/distinfo,v
retrieving revision 1.15
diff -u -p -r1.15 distinfo
--- distinfo 5 Jul 2015 00:53:41 -0000 1.15
+++ distinfo 31 Oct 2018 00:38:13 -0000
@@ -1,2 +1,2 @@
-SHA256 (Clone-0.38.tar.gz) = n7BTS7fvbKH2zB3D8pdQ1tQkOU0UxA79x3gy+tPOveg=
-SIZE (Clone-0.38.tar.gz) = 13636
+SHA256 (Clone-0.41.tar.gz) = 6MBW3PS8iIkHmglBKvcBlKVKJpaJunLtzZEpGkalFRg=
+SIZE (Clone-0.41.tar.gz) = 14441
tests, but there is also a fix for some possible infinite loops.
https://metacpan.org/changes/distribution/Clone
OK?
Reverse dependency test results are the same, failures didn't change
from the old version.
* p5-Class-DBI-3.0.16
Needs some infrastructure fixes because it can't connect to mysql
* p5-HTML-FormFu-0.07003
Seems to need an update uses qw() as parens in a loop
* p5-Jifty-DBI-0.68
Seems to need an update as there are some syntax errors
* p5-Rose-DB-0.778
Seems to be missing some dependencies for tests to pass
* p5-Rose-DB-Object-0.815
Same as above
* p5-Rose-HTML-Objects-0.6061
Lots of warnings so it probably needs an update
* p5-SQL-Statement-1.407
Not really sure what's failing. "Non-zero wait status"
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/p5-Clone/Makefile,v
retrieving revision 1.25
diff -u -p -r1.25 Makefile
--- Makefile 20 Mar 2016 19:56:16 -0000 1.25
+++ Makefile 31 Oct 2018 00:38:13 -0000
@@ -3,7 +3,7 @@
COMMENT = recursively copy Perl datatypes
MODULES = cpan
-DISTNAME = Clone-0.38
+DISTNAME = Clone-0.41
CATEGORIES = devel
MAINTAINER = Andrew Fresh <afresh1@openbsd.org>
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-Clone/distinfo,v
retrieving revision 1.15
diff -u -p -r1.15 distinfo
--- distinfo 5 Jul 2015 00:53:41 -0000 1.15
+++ distinfo 31 Oct 2018 00:38:13 -0000
@@ -1,2 +1,2 @@
-SHA256 (Clone-0.38.tar.gz) = n7BTS7fvbKH2zB3D8pdQ1tQkOU0UxA79x3gy+tPOveg=
-SIZE (Clone-0.38.tar.gz) = 13636
+SHA256 (Clone-0.41.tar.gz) = 6MBW3PS8iIkHmglBKvcBlKVKJpaJunLtzZEpGkalFRg=
+SIZE (Clone-0.41.tar.gz) = 14441
Re: update openldap to use modules
On Sun, Jul 01, 2018 at 11:54:53AM -0700, Paul B. Henson wrote:
> On Tue, Jun 26, 2018 at 08:47:03AM +0100, Stuart Henderson wrote:
>
> > Still interested, but I need to do some testing and it hasn't been high
> > enough priority to hit the top of my queue yet.
>
> Cool, thanks. No worries, just wondering; let me know when you have a
> chance to look at it if you need anything else from me to move it
> forward.
Looks like this port didn't change for 6.4, my last patch still seems to
work ok. Any chance on taking another look it this?
Thanks...
> On Tue, Jun 26, 2018 at 08:47:03AM +0100, Stuart Henderson wrote:
>
> > Still interested, but I need to do some testing and it hasn't been high
> > enough priority to hit the top of my queue yet.
>
> Cool, thanks. No worries, just wondering; let me know when you have a
> chance to look at it if you need anything else from me to move it
> forward.
Looks like this port didn't change for 6.4, my last patch still seems to
work ok. Any chance on taking another look it this?
Thanks...
NEW: sysutils/tenshi (and dep devel/p5-IO-BufferedSelect)
For the past few years every time a new release came out, I've submitted
this package and it's dep for potential inclusion in ports... I guess
nobody's interested, so after this try I suppose I'll just maintain it
locally and stop submitting it.
Thanks...
this package and it's dep for potential inclusion in ports... I guess
nobody's interested, so after this try I suppose I'll just maintain it
locally and stop submitting it.
Thanks...
Re: smtpd new "relay as" syntax?
On Wed, Oct 31, 2018 at 08:07:09PM -0400, TronDD wrote:
> Mail-from in the action options, I believe.
Ah, yes; that seems to work, thanks. The previous implementation was
documented as:
If the as parameter is specified, smtpd(8) will rewrite
the sender advertised in the SMTP session. address may
be a user, a domain prefixed with `@', or an email
address, causing smtpd(8) to rewrite the user-part, the
domain-part, or the entire address, respectively.
whereas this just said:
mail-from mailaddr
Use mailaddr as the MAIL FROM address within the SMTP
transaction.
It wasn't clear it would do the same rewriting functionality, I thought
at first it just took a single email address.
> Mail-from in the action options, I believe.
Ah, yes; that seems to work, thanks. The previous implementation was
documented as:
If the as parameter is specified, smtpd(8) will rewrite
the sender advertised in the SMTP session. address may
be a user, a domain prefixed with `@', or an email
address, causing smtpd(8) to rewrite the user-part, the
domain-part, or the entire address, respectively.
whereas this just said:
mail-from mailaddr
Use mailaddr as the MAIL FROM address within the SMTP
transaction.
It wasn't clear it would do the same rewriting functionality, I thought
at first it just took a single email address.
Re: SECURITY UPDATE: www/py-requests 2.20.0
On Wed, 31 Oct 2018 18:19:11 -0500, Edward Lopez-Acosta
<elopezacosta@gmail.com> wrote:
> Changelog:
> - Fixed in 2.20.0 - CVE 2018-18074
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18074
>
> The Requests package before 2.20.0 for Python sends an HTTP
> Authorization header to an http URI upon receiving a same-hostname
> https-to-http redirect, which makes it easier for remote attackers to
> discover credentials by sniffing the network.
>
> Diff attached. Builds fine on amd64 and only thing that requires it
> is upt-pypi (limited to py3 variant).
>
> Ok to merge?
The update looks good. The PLIST diff doesn't seem to be needed on my
side (and is removed if I regen the plist). I'd like to commit it
really soon. 2.20.0. was tagged two weeks ago so I guess it should be
fine as there's no .1 :)
Any objection? (or ok)
I'd like to add it to quirks as well. I'm not clever enough for the cve
stuff and I don't have any flavour example, is this diff correct?
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/quirks/Makefile,v
retrieving revision 1.634
diff -u -p -r1.634 Makefile
--- Makefile 31 Oct 2018 23:01:55 -0000 1.634
+++ Makefile 1 Nov 2018 00:23:47 -0000
@@ -5,7 +5,7 @@ CATEGORIES = devel databases
DISTFILES =
# API.rev
-PKGNAME = quirks-3.27
+PKGNAME = quirks-3.28
PKG_ARCH = *
MAINTAINER = Marc Espie <espie@openbsd.org>
Index: files/Quirks.pm
===================================================================
RCS file: /cvs/ports/devel/quirks/files/Quirks.pm,v
retrieving revision 1.648
diff -u -p -r1.648 Quirks.pm
--- files/Quirks.pm 31 Oct 2018 23:01:55 -0000 1.648
+++ files/Quirks.pm 1 Nov 2018 00:23:47 -0000
@@ -1212,6 +1212,8 @@ my $cve = {
'www/iridium' => 'iridium-<2018.5.67',
'www/mozilla-firefox' => 'firefox-<62.0.2p0',
'www/p5-CGI-Application' => 'p5-CGI-Application-<4.50p0',
+ 'www/py-requests' => 'py-requests-<2.20.0',
+ 'www/py-requests,python3' => 'py3-requests-<2.20.0',
'www/webkitgtk4' => 'webkitgtk4-<2.20.5',
'x11/gnome/gdm' => 'gdm-<3.28.3',
};
<elopezacosta@gmail.com> wrote:
> Changelog:
> - Fixed in 2.20.0 - CVE 2018-18074
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18074
>
> The Requests package before 2.20.0 for Python sends an HTTP
> Authorization header to an http URI upon receiving a same-hostname
> https-to-http redirect, which makes it easier for remote attackers to
> discover credentials by sniffing the network.
>
> Diff attached. Builds fine on amd64 and only thing that requires it
> is upt-pypi (limited to py3 variant).
>
> Ok to merge?
The update looks good. The PLIST diff doesn't seem to be needed on my
side (and is removed if I regen the plist). I'd like to commit it
really soon. 2.20.0. was tagged two weeks ago so I guess it should be
fine as there's no .1 :)
Any objection? (or ok)
I'd like to add it to quirks as well. I'm not clever enough for the cve
stuff and I don't have any flavour example, is this diff correct?
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/quirks/Makefile,v
retrieving revision 1.634
diff -u -p -r1.634 Makefile
--- Makefile 31 Oct 2018 23:01:55 -0000 1.634
+++ Makefile 1 Nov 2018 00:23:47 -0000
@@ -5,7 +5,7 @@ CATEGORIES = devel databases
DISTFILES =
# API.rev
-PKGNAME = quirks-3.27
+PKGNAME = quirks-3.28
PKG_ARCH = *
MAINTAINER = Marc Espie <espie@openbsd.org>
Index: files/Quirks.pm
===================================================================
RCS file: /cvs/ports/devel/quirks/files/Quirks.pm,v
retrieving revision 1.648
diff -u -p -r1.648 Quirks.pm
--- files/Quirks.pm 31 Oct 2018 23:01:55 -0000 1.648
+++ files/Quirks.pm 1 Nov 2018 00:23:47 -0000
@@ -1212,6 +1212,8 @@ my $cve = {
'www/iridium' => 'iridium-<2018.5.67',
'www/mozilla-firefox' => 'firefox-<62.0.2p0',
'www/p5-CGI-Application' => 'p5-CGI-Application-<4.50p0',
+ 'www/py-requests' => 'py-requests-<2.20.0',
+ 'www/py-requests,python3' => 'py3-requests-<2.20.0',
'www/webkitgtk4' => 'webkitgtk4-<2.20.5',
'x11/gnome/gdm' => 'gdm-<3.28.3',
};
Re: multimedia/mpv CVE-2018-6360
The loops are caused by the unique() function in configure, which spawns
many instances of ksh (it seems that bash handles 'eval' differently).
Its purpose is to turn a list of words into a list of unique words. I
propose the following perl script instead (beware, it's my first perl
script) called unique.pl:
#!/usr/bin/env perl
my %words_dict;
while (!eof(STDIN)){
my $line = readline(STDIN) or die("readline failed");
$line =~ s/\n//g;
my @line_words = split(/ /, $line);
foreach my $word (@line_words){
$words_dict{$word} = 0;
}
}
my @words_list = keys %words_dict;
print join(" ", @words_list), "\n";
Here is the diff for the configure script:
--- configure.orig Wed Jul 18 15:51:59 2018
+++ configure Mon Oct 29 23:15:01 2018
@@ -838,10 +838,10 @@
unique(){
var=$1
- uniq_list=""
- for tok in $(eval echo \$$var); do
- uniq_list="$(filter_out $tok $uniq_list) $tok"
- done
+ uniq_list=$(echo \$$var | ./unique.py)
eval "$var=\"${uniq_list}\""
}
With the following configure options, it builds on my amd64 machine, and
ffplay seems to work normally:
./configure --enable-shared --arch=amd64 --cc=cc \
--disable-altivec \
--disable-debug \
--disable-iconv \
--disable-indev=jack \
--disable-indev=oss \
--disable-lzma \
--disable-mips32r5 \
--disable-mips64r6 \
--disable-mipsdspr2 \
--disable-mipsfpu \
--disable-mmi \
--disable-msa \
--disable-outdev=oss \
--enable-fontconfig \
--enable-gpl \
--enable-libass \
--enable-libfreetype \
--enable-libfribidi \
--enable-libgsm \
--enable-libmp3lame \
--enable-libopus \
--enable-libspeex \
--enable-libv4l2 \
--enable-libvorbis \
--enable-libvpx \
--enable-libx264 \
--enable-libx265 \
--enable-libxvid \
--enable-nonfree \
--enable-openssl \
--extra-cflags="-I/usr/local/include -I/usr/X11R7/include" \
--extra-libs="-L/usr/local/lib -L/usr/X11R6/lib" \
--mandir=/usr/share/man \
--optflags="-Wno-redundant-decls"
I tried to modify the existing port (see attached file) but I'm very new
to OpenBSD and I haven't been able to include unique.pl yet, so at the
moment you would have to copy it in pobj after extraction and patching.
I did not try very hard: I simply modified the previous port, removing
patches first. Changes:
- versions for libs
- libavresample is now deprecated, use libswresample instead
- mipsdspr1 became mipsdsp
- I removed the --disable-outdev=sdl option because I do not understand
why it is here.
I haven't tried to build mpv yet so I don't know if it's the same problem.
many instances of ksh (it seems that bash handles 'eval' differently).
Its purpose is to turn a list of words into a list of unique words. I
propose the following perl script instead (beware, it's my first perl
script) called unique.pl:
#!/usr/bin/env perl
my %words_dict;
while (!eof(STDIN)){
my $line = readline(STDIN) or die("readline failed");
$line =~ s/\n//g;
my @line_words = split(/ /, $line);
foreach my $word (@line_words){
$words_dict{$word} = 0;
}
}
my @words_list = keys %words_dict;
print join(" ", @words_list), "\n";
Here is the diff for the configure script:
--- configure.orig Wed Jul 18 15:51:59 2018
+++ configure Mon Oct 29 23:15:01 2018
@@ -838,10 +838,10 @@
unique(){
var=$1
- uniq_list=""
- for tok in $(eval echo \$$var); do
- uniq_list="$(filter_out $tok $uniq_list) $tok"
- done
+ uniq_list=$(echo \$$var | ./unique.py)
eval "$var=\"${uniq_list}\""
}
With the following configure options, it builds on my amd64 machine, and
ffplay seems to work normally:
./configure --enable-shared --arch=amd64 --cc=cc \
--disable-altivec \
--disable-debug \
--disable-iconv \
--disable-indev=jack \
--disable-indev=oss \
--disable-lzma \
--disable-mips32r5 \
--disable-mips64r6 \
--disable-mipsdspr2 \
--disable-mipsfpu \
--disable-mmi \
--disable-msa \
--disable-outdev=oss \
--enable-fontconfig \
--enable-gpl \
--enable-libass \
--enable-libfreetype \
--enable-libfribidi \
--enable-libgsm \
--enable-libmp3lame \
--enable-libopus \
--enable-libspeex \
--enable-libv4l2 \
--enable-libvorbis \
--enable-libvpx \
--enable-libx264 \
--enable-libx265 \
--enable-libxvid \
--enable-nonfree \
--enable-openssl \
--extra-cflags="-I/usr/local/include -I/usr/X11R7/include" \
--extra-libs="-L/usr/local/lib -L/usr/X11R6/lib" \
--mandir=/usr/share/man \
--optflags="-Wno-redundant-decls"
I tried to modify the existing port (see attached file) but I'm very new
to OpenBSD and I haven't been able to include unique.pl yet, so at the
moment you would have to copy it in pobj after extraction and patching.
I did not try very hard: I simply modified the previous port, removing
patches first. Changes:
- versions for libs
- libavresample is now deprecated, use libswresample instead
- mipsdspr1 became mipsdsp
- I removed the --disable-outdev=sdl option because I do not understand
why it is here.
I haven't tried to build mpv yet so I don't know if it's the same problem.
Re: powerpc bulk build report
On 2018/10/31 15:00, George Koehler wrote:
> mupdf's MD5 code is broken on all big-endian machines.
> https://bugs.ghostscript.com/show_bug.cgi?id=699395
>
> I added a small patch (not the one in the bug report) and mailed it to
> maintainer Stuart Henderson on Monday. I don't know if MD5 works, but
> I can open a few PDF files.
I am looking into mupdf, I was already partway through updating to the newer
version but ran into lld-related problems that need figuring out (there is
the libssl-related thing you noticed too, actually that code is disabled
completely at the moment as it doesn't pass the pkg-config version check,
but if that's hacked away build fails due to libressl not having PKCS12_SAFEBAG
accessors yet).
> A copy of patch-thirdparty_lcms2_src_cmsmd5_c:
> =begin
> $OpenBSD$
>
> Fix "error: 'ContextID' undeclared" on big-endian machines.
> The argument will get ignored, so it can be NULL.
>
> Index: thirdparty/lcms2/src/cmsmd5.c
> --- thirdparty/lcms2/src/cmsmd5.c.orig
> +++ thirdparty/lcms2/src/cmsmd5.c
> @@ -33,7 +33,7 @@ void byteReverse(cmsUInt8Number * buf, cmsUInt32Number
> {
> do {
>
> - cmsUInt32Number t = _cmsAdjustEndianess32(ContextID, *(cmsUInt32Number *) buf);
> + cmsUInt32Number t = _cmsAdjustEndianess32(NULL, *(cmsUInt32Number *) buf);
> *(cmsUInt32Number *) buf = t;
> buf += sizeof(cmsUInt32Number);
>
> =end
> mupdf's MD5 code is broken on all big-endian machines.
> https://bugs.ghostscript.com/show_bug.cgi?id=699395
>
> I added a small patch (not the one in the bug report) and mailed it to
> maintainer Stuart Henderson on Monday. I don't know if MD5 works, but
> I can open a few PDF files.
I am looking into mupdf, I was already partway through updating to the newer
version but ran into lld-related problems that need figuring out (there is
the libssl-related thing you noticed too, actually that code is disabled
completely at the moment as it doesn't pass the pkg-config version check,
but if that's hacked away build fails due to libressl not having PKCS12_SAFEBAG
accessors yet).
> A copy of patch-thirdparty_lcms2_src_cmsmd5_c:
> =begin
> $OpenBSD$
>
> Fix "error: 'ContextID' undeclared" on big-endian machines.
> The argument will get ignored, so it can be NULL.
>
> Index: thirdparty/lcms2/src/cmsmd5.c
> --- thirdparty/lcms2/src/cmsmd5.c.orig
> +++ thirdparty/lcms2/src/cmsmd5.c
> @@ -33,7 +33,7 @@ void byteReverse(cmsUInt8Number * buf, cmsUInt32Number
> {
> do {
>
> - cmsUInt32Number t = _cmsAdjustEndianess32(ContextID, *(cmsUInt32Number *) buf);
> + cmsUInt32Number t = _cmsAdjustEndianess32(NULL, *(cmsUInt32Number *) buf);
> *(cmsUInt32Number *) buf = t;
> buf += sizeof(cmsUInt32Number);
>
> =end
Re: smtpd new "relay as" syntax?
On October 31, 2018 5:31:44 PM EDT, "Paul B. Henson" <henson@acm.org> wrote:
>I just upgraded to OpenBSD 6.4, and I'm trying to figure out how to do
>this with the new syntax:
>
>accept from local for any relay via smtp://smtp.domain.com as
>"@domain.com"
>
>This would rewrite the outbound message to masquerade as being from the
>TLD rather than a specific machine. Right now I've got:
>
>action local_relay relay host smtp.domain.com
>match from local for any action local_relay
>
>But this doesn't do the rewriting. The only thing I see in the man page
>talks about 'senders <users> [masquerade]' which seems to be for
>authenticated users.
>
>Am I missing something obvious?
>
>Thanks...
Mail-from in the action options, I believe.
>I just upgraded to OpenBSD 6.4, and I'm trying to figure out how to do
>this with the new syntax:
>
>accept from local for any relay via smtp://smtp.domain.com as
>"@domain.com"
>
>This would rewrite the outbound message to masquerade as being from the
>TLD rather than a specific machine. Right now I've got:
>
>action local_relay relay host smtp.domain.com
>match from local for any action local_relay
>
>But this doesn't do the rewriting. The only thing I see in the man page
>talks about 'senders <users> [masquerade]' which seems to be for
>authenticated users.
>
>Am I missing something obvious?
>
>Thanks...
Mail-from in the action options, I believe.
Re: games/ezquake and games/quakespasm broken on powerpc
On Wed, 31 Oct 2018 08:11:47 +0100
Solene Rapenne <solene@perso.pw> wrote:
> #1 0xb567523c in *_libc___stack_smash_handler (func=0xe38f5424 "X11_InitKeyboard", damaged=<optimized out>) at /usr/src/lib/libc/sys/stack_protector.c:79
> #2 0xe38a7ae0 in X11_InitKeyboard () from /usr/local/lib/libSDL2.so.0.5
This was https://bugzilla.libsdl.org/show_bug.cgi?id=4326
Please update to devel/sdl2 version 2.0.8p1. The snapshot packages
have 2.0.8p0, but if you build 2.0.8p1, its libSDL2.so.0.5 should
fix the crash, so you won't need to rebuild the games.
--
George Koehler <kernigh@gmail.com>
Solene Rapenne <solene@perso.pw> wrote:
> #1 0xb567523c in *_libc___stack_smash_handler (func=0xe38f5424 "X11_InitKeyboard", damaged=<optimized out>) at /usr/src/lib/libc/sys/stack_protector.c:79
> #2 0xe38a7ae0 in X11_InitKeyboard () from /usr/local/lib/libSDL2.so.0.5
This was https://bugzilla.libsdl.org/show_bug.cgi?id=4326
Please update to devel/sdl2 version 2.0.8p1. The snapshot packages
have 2.0.8p0, but if you build 2.0.8p1, its libSDL2.so.0.5 should
fix the crash, so you won't need to rebuild the games.
--
George Koehler <kernigh@gmail.com>
SECURITY UPDATE: www/py-requests 2.20.0
diff --git a/www/py-requests/Makefile b/www/py-requests/Makefile
index 99a31c7d4c0..95a1d504667 100644
--- a/www/py-requests/Makefile
+++ b/www/py-requests/Makefile
@@ -2,13 +2,9 @@
COMMENT= elegant and simple HTTP library for Python
-MODPY_EGG_VERSION= 2.18.4
+MODPY_EGG_VERSION= 2.20.0
DISTNAME= requests-${MODPY_EGG_VERSION}
PKGNAME= py-${DISTNAME}
-REVISION= 0
-
-# XXX remove during next update
-DISTFILES = ${DISTNAME}_1{${DISTNAME}}${EXTRACT_SUFX}
CATEGORIES= www
diff --git a/www/py-requests/distinfo b/www/py-requests/distinfo
index 6a3a0f542b2..dfbc7c0549f 100644
--- a/www/py-requests/distinfo
+++ b/www/py-requests/distinfo
@@ -1,2 +1,2 @@
-SHA256 (requests-2.18.4_1.tar.gz) = nEQ+cyS6W4UHDEqBit4ov6vt8W6hAgbaETLtqm3aI34=
-SIZE (requests-2.18.4_1.tar.gz) = 126224
+SHA256 (requests-2.20.0.tar.gz) = mdz9qusXyvblJvMrant4BGFRKrPx2ZIYeAFpTLpCdww=
+SIZE (requests-2.20.0.tar.gz) = 111179
diff --git a/www/py-requests/pkg/PLIST b/www/py-requests/pkg/PLIST
index bf0d0e12636..feac233b56f 100644
--- a/www/py-requests/pkg/PLIST
+++ b/www/py-requests/pkg/PLIST
@@ -1,4 +1,6 @@
@comment $OpenBSD: PLIST,v 1.12 2018/01/21 23:20:10 jung Exp $
+lib/python${MODPY_VERSION}/
+lib/python${MODPY_VERSION}/site-packages/
lib/python${MODPY_VERSION}/site-packages/requests/
lib/python${MODPY_VERSION}/site-packages/requests-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/
lib/python${MODPY_VERSION}/site-packages/requests-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
Changelog:
- Fixed in 2.20.0 - CVE 2018-18074
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18074
The Requests package before 2.20.0 for Python sends an HTTP
Authorization header to an http URI upon receiving a same-hostname
https-to-http redirect, which makes it easier for remote attackers to
discover credentials by sniffing the network.
Diff attached. Builds fine on amd64 and only thing that requires it is
upt-pypi (limited to py3 variant).
Ok to merge?
--
Edward Lopez-Acosta
index 99a31c7d4c0..95a1d504667 100644
--- a/www/py-requests/Makefile
+++ b/www/py-requests/Makefile
@@ -2,13 +2,9 @@
COMMENT= elegant and simple HTTP library for Python
-MODPY_EGG_VERSION= 2.18.4
+MODPY_EGG_VERSION= 2.20.0
DISTNAME= requests-${MODPY_EGG_VERSION}
PKGNAME= py-${DISTNAME}
-REVISION= 0
-
-# XXX remove during next update
-DISTFILES = ${DISTNAME}_1{${DISTNAME}}${EXTRACT_SUFX}
CATEGORIES= www
diff --git a/www/py-requests/distinfo b/www/py-requests/distinfo
index 6a3a0f542b2..dfbc7c0549f 100644
--- a/www/py-requests/distinfo
+++ b/www/py-requests/distinfo
@@ -1,2 +1,2 @@
-SHA256 (requests-2.18.4_1.tar.gz) = nEQ+cyS6W4UHDEqBit4ov6vt8W6hAgbaETLtqm3aI34=
-SIZE (requests-2.18.4_1.tar.gz) = 126224
+SHA256 (requests-2.20.0.tar.gz) = mdz9qusXyvblJvMrant4BGFRKrPx2ZIYeAFpTLpCdww=
+SIZE (requests-2.20.0.tar.gz) = 111179
diff --git a/www/py-requests/pkg/PLIST b/www/py-requests/pkg/PLIST
index bf0d0e12636..feac233b56f 100644
--- a/www/py-requests/pkg/PLIST
+++ b/www/py-requests/pkg/PLIST
@@ -1,4 +1,6 @@
@comment $OpenBSD: PLIST,v 1.12 2018/01/21 23:20:10 jung Exp $
+lib/python${MODPY_VERSION}/
+lib/python${MODPY_VERSION}/site-packages/
lib/python${MODPY_VERSION}/site-packages/requests/
lib/python${MODPY_VERSION}/site-packages/requests-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/
lib/python${MODPY_VERSION}/site-packages/requests-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
Changelog:
- Fixed in 2.20.0 - CVE 2018-18074
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18074
The Requests package before 2.20.0 for Python sends an HTTP
Authorization header to an http URI upon receiving a same-hostname
https-to-http redirect, which makes it easier for remote attackers to
discover credentials by sniffing the network.
Diff attached. Builds fine on amd64 and only thing that requires it is
upt-pypi (limited to py3 variant).
Ok to merge?
--
Edward Lopez-Acosta
Re: editors/emacs21 upgrade path?
On 2018-10-31, Jeremie Courreges-Anglas <jca@wxcvbn.org> wrote:
> We could force an upgrade to the latest version, like it was done for
> emacs22 and emacs23.
Yes, I think that makes sense.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
> We could force an upgrade to the latest version, like it was done for
> emacs22 and emacs23.
Yes, I think that makes sense.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
New policy for mercurial extensions
For the last 6 months I've not updated the mercurial package to the
recent major versions because py-hg-git was not compatible. The
mercurial package contains code exposed to the network and I don't feel
comfortable backporting bugfixes just because some extensions are not
compatible with the recent API changes.
Mercurial 4.8 will include a lot of good changes and I don't want to put
on hold another version. In the next days, I will remove any broken
extension. I will do the same in the future for new mercurial versions.
This wiki explains how to keep a local copy in your home of the
extensions which are not available from ports:
https://www.mercurial-scm.org/wiki/UsingExtensions#Enabling_an_extension
I will ask for OKs for the deletion of packages with active maintainers
and will remove directly the ports with unactive maintainers. I will try
to update the extensions with a new version available but I will not try
too hard.
Cheers.
--
Juan Francisco Cantero Hurtado http://juanfra.info
recent major versions because py-hg-git was not compatible. The
mercurial package contains code exposed to the network and I don't feel
comfortable backporting bugfixes just because some extensions are not
compatible with the recent API changes.
Mercurial 4.8 will include a lot of good changes and I don't want to put
on hold another version. In the next days, I will remove any broken
extension. I will do the same in the future for new mercurial versions.
This wiki explains how to keep a local copy in your home of the
extensions which are not available from ports:
https://www.mercurial-scm.org/wiki/UsingExtensions#Enabling_an_extension
I will ask for OKs for the deletion of packages with active maintainers
and will remove directly the ports with unactive maintainers. I will try
to update the extensions with a new version available but I will not try
too hard.
Cheers.
--
Juan Francisco Cantero Hurtado http://juanfra.info
smtpd new "relay as" syntax?
I just upgraded to OpenBSD 6.4, and I'm trying to figure out how to do
this with the new syntax:
accept from local for any relay via smtp://smtp.domain.com as "@domain.com"
This would rewrite the outbound message to masquerade as being from the
TLD rather than a specific machine. Right now I've got:
action local_relay relay host smtp.domain.com
match from local for any action local_relay
But this doesn't do the rewriting. The only thing I see in the man page
talks about 'senders <users> [masquerade]' which seems to be for
authenticated users.
Am I missing something obvious?
Thanks...
this with the new syntax:
accept from local for any relay via smtp://smtp.domain.com as "@domain.com"
This would rewrite the outbound message to masquerade as being from the
TLD rather than a specific machine. Right now I've got:
action local_relay relay host smtp.domain.com
match from local for any action local_relay
But this doesn't do the rewriting. The only thing I see in the man page
talks about 'senders <users> [masquerade]' which seems to be for
authenticated users.
Am I missing something obvious?
Thanks...
Re: [UPDATE] lang/python/3.6
Remi Pointel:
> attached is the diff to update to python 3.6.7.
> Please test this diff in a bulk build.
I have started an amd64 bulk build with this.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
> attached is the diff to update to python 3.6.7.
> Please test this diff in a bulk build.
I have started an amd64 bulk build with this.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
Re: spamd and google smtp ips
On 31.10.2018 17:09, Kevin Chadwick wrote:
> On 10/30/18 8:05 PM, Mario Theodoridis wrote:
>> I ran into this problem as well.
>> I ended up writing a script that parses the SPF entries out of the greylist and
>> if reasonable, whitelists those ranges and removes the grey
>> list entries. It runs every 15 minutes.
>
> smtpctl now has an spf walk function that may shorten your script?
Thanks Kevin.
That'd be one less wheel to invent.
--
Mit freundlichen Grüßen/Best regards
Mario Theodoridis
> On 10/30/18 8:05 PM, Mario Theodoridis wrote:
>> I ran into this problem as well.
>> I ended up writing a script that parses the SPF entries out of the greylist and
>> if reasonable, whitelists those ranges and removes the grey
>> list entries. It runs every 15 minutes.
>
> smtpctl now has an spf walk function that may shorten your script?
Thanks Kevin.
That'd be one less wheel to invent.
--
Mit freundlichen Grüßen/Best regards
Mario Theodoridis
Re: powerpc bulk build report
On Tue, 30 Oct 2018 23:45:14 -0600 (MDT)
landry@openbsd.org wrote:
> bulk build on macppc-1.ports.openbsd.org
> started on Fri Oct 12 09:46:26 MDT 2018
> finished at Tue Oct 30 18:15:58 MDT 2018
I recently built some packages on my OpenBSD/macppc machine,
and fixed failures in devel/vte3, textproc/mupdf, multimedia/x265.
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/vte3.log
ports-gcc can't build devel/vte3; this blocks x11/xfce4/terminal and
some other terminal emulators. I added a patch to build it (and get a
working xfce4-terminal). I mailed the patch to maintainers Jasper
Lievisse Adriaanse and Antoine Jacoutot on Monday 29 Oct 2018.
I don't know how to use cvs diff,
but here's a copy of patch-src_app_app_cc:
=begin
$OpenBSD$
Prevent error from ports-gcc.
app.cc:309:39: error: cannot convert 'const GdkRGBA {aka const _GdkRGBA}
to 'gdouble {aka double}' in initialization
Index: src/app/app.cc
--- src/app/app.cc.orig
+++ src/app/app.cc
@@ -306,7 +306,7 @@ class Options { (public)
else
alpha = get_alpha();
- GdkRGBA color{bg_color};
+ GdkRGBA color(bg_color);
color.alpha = alpha;
return color;
}
=end
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/textproc/mupdf.log
mupdf's MD5 code is broken on all big-endian machines.
https://bugs.ghostscript.com/show_bug.cgi?id=699395
I added a small patch (not the one in the bug report) and mailed it to
maintainer Stuart Henderson on Monday. I don't know if MD5 works, but
I can open a few PDF files.
A copy of patch-thirdparty_lcms2_src_cmsmd5_c:
=begin
$OpenBSD$
Fix "error: 'ContextID' undeclared" on big-endian machines.
The argument will get ignored, so it can be NULL.
Index: thirdparty/lcms2/src/cmsmd5.c
--- thirdparty/lcms2/src/cmsmd5.c.orig
+++ thirdparty/lcms2/src/cmsmd5.c
@@ -33,7 +33,7 @@ void byteReverse(cmsUInt8Number * buf, cmsUInt32Number
{
do {
- cmsUInt32Number t = _cmsAdjustEndianess32(ContextID, *(cmsUInt32Number *) buf);
+ cmsUInt32Number t = _cmsAdjustEndianess32(NULL, *(cmsUInt32Number *) buf);
*(cmsUInt32Number *) buf = t;
buf += sizeof(cmsUInt32Number);
=end
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xfce4/xfce4-whiskermenu.log
"error: expected primary-expression before '{' token"
I didn't fix this one. The '{' begins an initializer list. The error
is from base-gcc; this port might need C++11 and ports-gcc.
I got the error from xfce4-whiskermenu-2.3.0. CVS now has 2.3.0p0,
which adds a line "COMPILER = base-clang ports-gcc base-gcc", so it
will use ports-gcc and might have a chance to build. I have not tried
to build 2.3.0p0. I wonder if base-gcc should not be in COMPILER?
I forgot to contact maintainer Landry Breuil. I would have sent my
build log, but now I see that you already have one.
I have one more failure: multimedia/x265 version 2.9 is broken on all
non-x86 machines, https://bitbucket.org/multicoreware/x265/issues/442
That report has a patch; I mailed that patch (with my own comment) to
maintainer Brad Smith on Monday. I can build x265 but don't know if
it can encode or decode video.
A copy of patch-source_common_cpu_cpp:
=begin
$OpenBSD$
Move the definition of x265::detect512() outside of #if X265_ARCH_X86
to prevent a linker error on non-x86 platforms:
.../libx265.so.16.0: undefined reference to `x265::detect512()'
Patch from Adam Sampson,
https://bitbucket.org/multicoreware/x265/issues/442
Index: source/common/cpu.cpp
--- source/common/cpu.cpp.orig
+++ source/common/cpu.cpp
@@ -110,6 +110,11 @@ const cpu_name_t cpu_names[] =
{ "", 0 },
};
+bool detect512()
+{
+ return(enable512);
+}
+
#if X265_ARCH_X86
extern "C" {
@@ -123,10 +128,6 @@ uint64_t PFX(cpu_xgetbv)(int xcr);
#pragma warning(disable: 4309) // truncation of constant value
landry@openbsd.org wrote:
> bulk build on macppc-1.ports.openbsd.org
> started on Fri Oct 12 09:46:26 MDT 2018
> finished at Tue Oct 30 18:15:58 MDT 2018
I recently built some packages on my OpenBSD/macppc machine,
and fixed failures in devel/vte3, textproc/mupdf, multimedia/x265.
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/vte3.log
ports-gcc can't build devel/vte3; this blocks x11/xfce4/terminal and
some other terminal emulators. I added a patch to build it (and get a
working xfce4-terminal). I mailed the patch to maintainers Jasper
Lievisse Adriaanse and Antoine Jacoutot on Monday 29 Oct 2018.
I don't know how to use cvs diff,
but here's a copy of patch-src_app_app_cc:
=begin
$OpenBSD$
Prevent error from ports-gcc.
app.cc:309:39: error: cannot convert 'const GdkRGBA {aka const _GdkRGBA}
to 'gdouble {aka double}' in initialization
Index: src/app/app.cc
--- src/app/app.cc.orig
+++ src/app/app.cc
@@ -306,7 +306,7 @@ class Options { (public)
else
alpha = get_alpha();
- GdkRGBA color{bg_color};
+ GdkRGBA color(bg_color);
color.alpha = alpha;
return color;
}
=end
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/textproc/mupdf.log
mupdf's MD5 code is broken on all big-endian machines.
https://bugs.ghostscript.com/show_bug.cgi?id=699395
I added a small patch (not the one in the bug report) and mailed it to
maintainer Stuart Henderson on Monday. I don't know if MD5 works, but
I can open a few PDF files.
A copy of patch-thirdparty_lcms2_src_cmsmd5_c:
=begin
$OpenBSD$
Fix "error: 'ContextID' undeclared" on big-endian machines.
The argument will get ignored, so it can be NULL.
Index: thirdparty/lcms2/src/cmsmd5.c
--- thirdparty/lcms2/src/cmsmd5.c.orig
+++ thirdparty/lcms2/src/cmsmd5.c
@@ -33,7 +33,7 @@ void byteReverse(cmsUInt8Number * buf, cmsUInt32Number
{
do {
- cmsUInt32Number t = _cmsAdjustEndianess32(ContextID, *(cmsUInt32Number *) buf);
+ cmsUInt32Number t = _cmsAdjustEndianess32(NULL, *(cmsUInt32Number *) buf);
*(cmsUInt32Number *) buf = t;
buf += sizeof(cmsUInt32Number);
=end
> http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xfce4/xfce4-whiskermenu.log
"error: expected primary-expression before '{' token"
I didn't fix this one. The '{' begins an initializer list. The error
is from base-gcc; this port might need C++11 and ports-gcc.
I got the error from xfce4-whiskermenu-2.3.0. CVS now has 2.3.0p0,
which adds a line "COMPILER = base-clang ports-gcc base-gcc", so it
will use ports-gcc and might have a chance to build. I have not tried
to build 2.3.0p0. I wonder if base-gcc should not be in COMPILER?
I forgot to contact maintainer Landry Breuil. I would have sent my
build log, but now I see that you already have one.
I have one more failure: multimedia/x265 version 2.9 is broken on all
non-x86 machines, https://bitbucket.org/multicoreware/x265/issues/442
That report has a patch; I mailed that patch (with my own comment) to
maintainer Brad Smith on Monday. I can build x265 but don't know if
it can encode or decode video.
A copy of patch-source_common_cpu_cpp:
=begin
$OpenBSD$
Move the definition of x265::detect512() outside of #if X265_ARCH_X86
to prevent a linker error on non-x86 platforms:
.../libx265.so.16.0: undefined reference to `x265::detect512()'
Patch from Adam Sampson,
https://bitbucket.org/multicoreware/x265/issues/442
Index: source/common/cpu.cpp
--- source/common/cpu.cpp.orig
+++ source/common/cpu.cpp
@@ -110,6 +110,11 @@ const cpu_name_t cpu_names[] =
{ "", 0 },
};
+bool detect512()
+{
+ return(enable512);
+}
+
#if X265_ARCH_X86
extern "C" {
@@ -123,10 +128,6 @@ uint64_t PFX(cpu_xgetbv)(int xcr);
#pragma warning(disable: 4309) // truncation of constant value
Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 10/31/18 2:15 PM, Christian Weisgerber wrote:
> On 2018-10-31, Stuart Henderson <stu@spacehopper.org> wrote:
>
>> No idea how ^4 is mapped to ^\, but for some reason it is,
>
> This goes back to the VT220, if not older terminals. Ctrl-3 for
> ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
> place as on most PC keyboards.
>
> See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
> the VT220 Programmer Reference Manual:
> https://vt100.net/docs/vt220-rm/table3-5.html
>
Looks like this is implemented by the different terminal emulators so it varies. For vte
(gnome-terminal, terminator, ...), it looks like this is the code that sets up this behavior:
https://github.com/GNOME/vte/blob/master/src/keymap.cc#L146
- Aner
> On 2018-10-31, Stuart Henderson <stu@spacehopper.org> wrote:
>
>> No idea how ^4 is mapped to ^\, but for some reason it is,
>
> This goes back to the VT220, if not older terminals. Ctrl-3 for
> ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
> place as on most PC keyboards.
>
> See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
> the VT220 Programmer Reference Manual:
> https://vt100.net/docs/vt220-rm/table3-5.html
>
Looks like this is implemented by the different terminal emulators so it varies. For vte
(gnome-terminal, terminator, ...), it looks like this is the code that sets up this behavior:
https://github.com/GNOME/vte/blob/master/src/keymap.cc#L146
- Aner
Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 2018-10-31, Stuart Henderson <stu@spacehopper.org> wrote:
> No idea how ^4 is mapped to ^\, but for some reason it is,
This goes back to the VT220, if not older terminals. Ctrl-3 for
ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
place as on most PC keyboards.
See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
the VT220 Programmer Reference Manual:
https://vt100.net/docs/vt220-rm/table3-5.html
--
Christian "naddy" Weisgerber naddy@mips.inka.de
> No idea how ^4 is mapped to ^\, but for some reason it is,
This goes back to the VT220, if not older terminals. Ctrl-3 for
ESC aka ^[ is particularly handy if the Esc key is in some inconvenient
place as on most PC keyboards.
See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in
the VT220 Programmer Reference Manual:
https://vt100.net/docs/vt220-rm/table3-5.html
--
Christian "naddy" Weisgerber naddy@mips.inka.de
Re: Bluetooth Support
On 10/31/18 9:42 AM, Marco Menne wrote:
> Bluetooth I never liked. :-)
Especially when the Bluetooth spec, specified ecdh without following the
security requirements of must validate the curves as clearly laid out by GECC
(guide to ECC).
I guess Linux and some Intel products did the same or copied code.
Unbelievable!
> Bluetooth I never liked. :-)
Especially when the Bluetooth spec, specified ecdh without following the
security requirements of must validate the curves as clearly laid out by GECC
(guide to ECC).
I guess Linux and some Intel products did the same or copied code.
Unbelievable!
Re: spamd and google smtp ips
On 10/30/18 8:05 PM, Mario Theodoridis wrote:
> I ran into this problem as well.
> I ended up writing a script that parses the SPF entries out of the greylist and
> if reasonable, whitelists those ranges and removes the grey
> list entries. It runs every 15 minutes.
smtpctl now has an spf walk function that may shorten your script?
> I ran into this problem as well.
> I ended up writing a script that parses the SPF entries out of the greylist and
> if reasonable, whitelists those ranges and removes the grey
> list entries. It runs every 15 minutes.
smtpctl now has an spf walk function that may shorten your script?
Re: syntax error and doas.conf
Stuart Henderson <stu@spacehopper.org> writes:
> If you aren't sure about a change you're about to make, keep a spare
> root shell open (or at least keep the editor open - save the file
> but don't exit - and test on another terminal).
I would add that this is not really OpenBSD-specific. Yes there's no
direct analogue to visudo(8) but it's perfectly possible to lock
yourself out of sudo access even with a correctly formatted /etc/sudoers
file, and visudo will happily let you shoot yourself in the foot that
way. With the sudoers(5) man page clocking in at about 20x the size of
the doas.conf(5) page, it's probably quite likely.
Allan
> If you aren't sure about a change you're about to make, keep a spare
> root shell open (or at least keep the editor open - save the file
> but don't exit - and test on another terminal).
I would add that this is not really OpenBSD-specific. Yes there's no
direct analogue to visudo(8) but it's perfectly possible to lock
yourself out of sudo access even with a correctly formatted /etc/sudoers
file, and visudo will happily let you shoot yourself in the foot that
way. With the sudoers(5) man page clocking in at about 20x the size of
the doas.conf(5) page, it's probably quite likely.
Allan
Re: syntax error and doas.conf
Stuart Henderson <stu@spacehopper.org> wrote:
> On 2018-10-31, Markus Rosjat <rosjat@ghweb.de> wrote:
> > just something I notice while trying out stuff with doas and my python
> > scripts. If you do a mistake and have a syntax error in the doas.conf
> > file you can easily look you self out from root privilages :(
>
> If you aren't sure about a change you're about to make, keep a spare
> root shell open (or at least keep the editor open - save the file
> but don't exit - and test on another terminal).
When editing files, most of the time I go back to the shell using ^Z (editor go
in background), I do what's related to the file (try doas, restart httpd until
it works, etc..). And I use fg when I need to come back to the editor.
When playing with doas or sshd, I would recommend for doas to keep a root shell
opened in case you screw the file. And for sshd, when restarting it on a remote
machine, try to connect to it before exiting your current ssh session.
> On 2018-10-31, Markus Rosjat <rosjat@ghweb.de> wrote:
> > just something I notice while trying out stuff with doas and my python
> > scripts. If you do a mistake and have a syntax error in the doas.conf
> > file you can easily look you self out from root privilages :(
>
> If you aren't sure about a change you're about to make, keep a spare
> root shell open (or at least keep the editor open - save the file
> but don't exit - and test on another terminal).
When editing files, most of the time I go back to the shell using ^Z (editor go
in background), I do what's related to the file (try doas, restart httpd until
it works, etc..). And I use fg when I need to come back to the editor.
When playing with doas or sshd, I would recommend for doas to keep a root shell
opened in case you screw the file. And for sshd, when restarting it on a remote
machine, try to connect to it before exiting your current ssh session.
Re: syntax error and doas.conf
On 10/31/18 10:42 AM, Markus Rosjat wrote:
...
> doas vi /etc/doas.conf
# Edit in vi
:w
:! doas -C %
<if error correct and repeat>
<if OK :q>
You don't even have to leave your editor
...
> doas vi /etc/doas.conf
# Edit in vi
:w
:! doas -C %
<if error correct and repeat>
<if OK :q>
You don't even have to leave your editor
Re: Why&how do "sh" and "ksh" differ in behavior e.g. PS1 presentation, while their binaries are equal?
On Wednesday, October 31, 2018 10:19 PM, Joseph Mayer <joseph.mayer@protonmail.com> wrote:
> On Tuesday, October 30, 2018 4:33 PM, Sebastien Marie semarie@online.fr wrote:
>
> > On Tue, Oct 30, 2018 at 08:11:24AM +0000, Joseph Mayer wrote:
> >
> > > On a quick sourcecode check I didn't see any code paths e.g.
> > > "if (argv[0] matches "ksh") { something } else { something else }"
> > > however I presume I missed something.
> >
> > yes, the check was too quick, it seems :)
> > src/bin/ksh/main.c
> > 134 int
> > 135 main(int argc, char *argv[])
> > 136 {
> > 137 int i;
> > 138 int argi;
> > 139 Source *s;
> > 140 struct block *l;
> > 141 int restricted, errexit;
> > 142 char *wp;
> > 143 struct env env;
> > 144 pid_t ppid;
> > 145
> > 146 kshname = argv[0];
> > 147
> > ...
> > 236 / Check to see if we're /bin/sh. */237 if (!strcmp(kshname, "sh") || !strcmp(kshname, "-sh") ||
> > 238 (strlen(kshname) >= 3 &&
> > 239 !strcmp(&kshname[strlen(kshname) - 3], "/sh"))) {
> > 240 Flag(FSH) = 1;
> > 241 version_param = "SH_VERSION";
> > 242 }
> > 243
> >
> > Sebastien Marie
>
> Hi Sebastien,
>
> Thanks a lot for clarifying.
>
> sh's man page (http://man.openbsd.org/sh#DESCRIPTION) says:
>
> "This version of sh is actually ksh in disguise. As such, it also
> supports the features described in ksh(1). This manual page describes
> only the parts relevant to a POSIX compliant sh."
>
> When I read that originally, I perceived it as that "sh" and "ksh"
> normally would have equivalent behavior - which also seems logical
> given that their binaries are byte-equivalent.
>
> The meaning I gather from the sentence is that sh and ksh are
> equivalent and that instead the man pages will describe different
> functionalities that are actually available in both.
>
> Can that phrase in sh's man page be tweaked so that my misunderstanding
> no longer is possible?
>
> Do you find my misunderstanding a reasonable reading?
>
> Joseph
Moving this to bugs@ , sorry for spam.
> On Tuesday, October 30, 2018 4:33 PM, Sebastien Marie semarie@online.fr wrote:
>
> > On Tue, Oct 30, 2018 at 08:11:24AM +0000, Joseph Mayer wrote:
> >
> > > On a quick sourcecode check I didn't see any code paths e.g.
> > > "if (argv[0] matches "ksh") { something } else { something else }"
> > > however I presume I missed something.
> >
> > yes, the check was too quick, it seems :)
> > src/bin/ksh/main.c
> > 134 int
> > 135 main(int argc, char *argv[])
> > 136 {
> > 137 int i;
> > 138 int argi;
> > 139 Source *s;
> > 140 struct block *l;
> > 141 int restricted, errexit;
> > 142 char *wp;
> > 143 struct env env;
> > 144 pid_t ppid;
> > 145
> > 146 kshname = argv[0];
> > 147
> > ...
> > 236 / Check to see if we're /bin/sh. */237 if (!strcmp(kshname, "sh") || !strcmp(kshname, "-sh") ||
> > 238 (strlen(kshname) >= 3 &&
> > 239 !strcmp(&kshname[strlen(kshname) - 3], "/sh"))) {
> > 240 Flag(FSH) = 1;
> > 241 version_param = "SH_VERSION";
> > 242 }
> > 243
> >
> > Sebastien Marie
>
> Hi Sebastien,
>
> Thanks a lot for clarifying.
>
> sh's man page (http://man.openbsd.org/sh#DESCRIPTION) says:
>
> "This version of sh is actually ksh in disguise. As such, it also
> supports the features described in ksh(1). This manual page describes
> only the parts relevant to a POSIX compliant sh."
>
> When I read that originally, I perceived it as that "sh" and "ksh"
> normally would have equivalent behavior - which also seems logical
> given that their binaries are byte-equivalent.
>
> The meaning I gather from the sentence is that sh and ksh are
> equivalent and that instead the man pages will describe different
> functionalities that are actually available in both.
>
> Can that phrase in sh's man page be tweaked so that my misunderstanding
> no longer is possible?
>
> Do you find my misunderstanding a reasonable reading?
>
> Joseph
Moving this to bugs@ , sorry for spam.
Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 10/31/18 10:54 AM, Stuart Henderson wrote:
> On 2018-10-31, Tinker <t1nkr@protonmail.ch> wrote:
>> Hi,
>>
>> When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
>> /dev/zero", if I press ctrl+4, the program coredumps.
>>
>> Doing it in ksh or sh has no effect though.
>>
>> This is in OpenBSD 6.4 AMD64 from Putty on Windows.
>>
>> The console interaction looks like this:
>>
>> $ cat
>> ^\Quit (core dumped)
>>
>> $
>>
>>
>> Is ctrl+4 a universal SIGQUIT+coredump shortcut?
>>
>> Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
>> documented?
>>
>> Tinker
>>
>>
>
> No idea how ^4 is mapped to ^\, but for some reason it is, and this
> the default for "quit", see "stty -a".
>
> This is a useful sequence to interrupt boot if you weren't quick enough
> to "boot -s" to enter single-user mode.
>
>
You can also find more details in the termios(4) man page, specifically the Special
Characters section.
- Aner
> On 2018-10-31, Tinker <t1nkr@protonmail.ch> wrote:
>> Hi,
>>
>> When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
>> /dev/zero", if I press ctrl+4, the program coredumps.
>>
>> Doing it in ksh or sh has no effect though.
>>
>> This is in OpenBSD 6.4 AMD64 from Putty on Windows.
>>
>> The console interaction looks like this:
>>
>> $ cat
>> ^\Quit (core dumped)
>>
>> $
>>
>>
>> Is ctrl+4 a universal SIGQUIT+coredump shortcut?
>>
>> Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
>> documented?
>>
>> Tinker
>>
>>
>
> No idea how ^4 is mapped to ^\, but for some reason it is, and this
> the default for "quit", see "stty -a".
>
> This is a useful sequence to interrupt boot if you weren't quick enough
> to "boot -s" to enter single-user mode.
>
>
You can also find more details in the termios(4) man page, specifically the Special
Characters section.
- Aner
Re: syntax error and doas.conf
On 2018-10-31, Markus Rosjat <rosjat@ghweb.de> wrote:
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf
> file you can easily look you self out from root privilages :(
If you aren't sure about a change you're about to make, keep a spare
root shell open (or at least keep the editor open - save the file
but don't exit - and test on another terminal).
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf
> file you can easily look you self out from root privilages :(
If you aren't sure about a change you're about to make, keep a spare
root shell open (or at least keep the editor open - save the file
but don't exit - and test on another terminal).
Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 2018-10-31, Tinker <t1nkr@protonmail.ch> wrote:
> Hi,
>
> When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
> /dev/zero", if I press ctrl+4, the program coredumps.
>
> Doing it in ksh or sh has no effect though.
>
> This is in OpenBSD 6.4 AMD64 from Putty on Windows.
>
> The console interaction looks like this:
>
> $ cat
> ^\Quit (core dumped)
>
> $
>
>
> Is ctrl+4 a universal SIGQUIT+coredump shortcut?
>
> Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
> documented?
>
> Tinker
>
>
No idea how ^4 is mapped to ^\, but for some reason it is, and this
the default for "quit", see "stty -a".
This is a useful sequence to interrupt boot if you weren't quick enough
to "boot -s" to enter single-user mode.
> Hi,
>
> When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
> /dev/zero", if I press ctrl+4, the program coredumps.
>
> Doing it in ksh or sh has no effect though.
>
> This is in OpenBSD 6.4 AMD64 from Putty on Windows.
>
> The console interaction looks like this:
>
> $ cat
> ^\Quit (core dumped)
>
> $
>
>
> Is ctrl+4 a universal SIGQUIT+coredump shortcut?
>
> Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
> documented?
>
> Tinker
>
>
No idea how ^4 is mapped to ^\, but for some reason it is, and this
the default for "quit", see "stty -a".
This is a useful sequence to interrupt boot if you weren't quick enough
to "boot -s" to enter single-user mode.
Re: Why&how do "sh" and "ksh" differ in behavior e.g. PS1 presentation, while their binaries are equal?
On Tuesday, October 30, 2018 4:33 PM, Sebastien Marie <semarie@online.fr> wrote:
> On Tue, Oct 30, 2018 at 08:11:24AM +0000, Joseph Mayer wrote:
>
> > On a quick sourcecode check I didn't see any code paths e.g.
> > "if (argv[0] matches "ksh") { something } else { something else }"
> > however I presume I missed something.
>
> yes, the check was too quick, it seems :)
>
> src/bin/ksh/main.c
> 134 int
> 135 main(int argc, char *argv[])
> 136 {
> 137 int i;
> 138 int argi;
> 139 Source *s;
> 140 struct block *l;
> 141 int restricted, errexit;
> 142 char *wp;
> 143 struct env env;
> 144 pid_t ppid;
> 145
> 146 kshname = argv[0];
> 147
> ...
> 236 / Check to see if we're /bin/sh. */237 if (!strcmp(kshname, "sh") || !strcmp(kshname, "-sh") ||
> 238 (strlen(kshname) >= 3 &&
>
> 239 !strcmp(&kshname[strlen(kshname) - 3], "/sh"))) {
> 240 Flag(FSH) = 1;
> 241 version_param = "SH_VERSION";
> 242 }
> 243
>
> ---------------------------------------------------------------------------------------------------------------------
>
> Sebastien Marie
Hi Sebastien,
Thanks a lot for clarifying.
sh's man page (http://man.openbsd.org/sh#DESCRIPTION) says:
"This version of sh is actually ksh in disguise. As such, it also
supports the features described in ksh(1). This manual page describes
only the parts relevant to a POSIX compliant sh."
When I read that originally, I perceived it as that "sh" and "ksh"
normally would have equivalent behavior - which also seems logical
given that their binaries are byte-equivalent.
The meaning I gather from the sentence is that sh and ksh are
equivalent and that instead the man pages will describe different
functionalities that are actually available in both.
Can that phrase in sh's man page be tweaked so that my misunderstanding
no longer is possible?
Do you find my misunderstanding a reasonable reading?
Joseph
> On Tue, Oct 30, 2018 at 08:11:24AM +0000, Joseph Mayer wrote:
>
> > On a quick sourcecode check I didn't see any code paths e.g.
> > "if (argv[0] matches "ksh") { something } else { something else }"
> > however I presume I missed something.
>
> yes, the check was too quick, it seems :)
>
> src/bin/ksh/main.c
> 134 int
> 135 main(int argc, char *argv[])
> 136 {
> 137 int i;
> 138 int argi;
> 139 Source *s;
> 140 struct block *l;
> 141 int restricted, errexit;
> 142 char *wp;
> 143 struct env env;
> 144 pid_t ppid;
> 145
> 146 kshname = argv[0];
> 147
> ...
> 236 / Check to see if we're /bin/sh. */237 if (!strcmp(kshname, "sh") || !strcmp(kshname, "-sh") ||
> 238 (strlen(kshname) >= 3 &&
>
> 239 !strcmp(&kshname[strlen(kshname) - 3], "/sh"))) {
> 240 Flag(FSH) = 1;
> 241 version_param = "SH_VERSION";
> 242 }
> 243
>
> ---------------------------------------------------------------------------------------------------------------------
>
> Sebastien Marie
Hi Sebastien,
Thanks a lot for clarifying.
sh's man page (http://man.openbsd.org/sh#DESCRIPTION) says:
"This version of sh is actually ksh in disguise. As such, it also
supports the features described in ksh(1). This manual page describes
only the parts relevant to a POSIX compliant sh."
When I read that originally, I perceived it as that "sh" and "ksh"
normally would have equivalent behavior - which also seems logical
given that their binaries are byte-equivalent.
The meaning I gather from the sentence is that sh and ksh are
equivalent and that instead the man pages will describe different
functionalities that are actually available in both.
Can that phrase in sh's man page be tweaked so that my misunderstanding
no longer is possible?
Do you find my misunderstanding a reasonable reading?
Joseph
Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
Hi,
When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
/dev/zero", if I press ctrl+4, the program coredumps.
Doing it in ksh or sh has no effect though.
This is in OpenBSD 6.4 AMD64 from Putty on Windows.
The console interaction looks like this:
$ cat
^\Quit (core dumped)
$
Is ctrl+4 a universal SIGQUIT+coredump shortcut?
Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
documented?
Tinker
When in "cat" or "dd if=/dev/zero of=/dev/zero" or "gzip < /dev/zero >
/dev/zero", if I press ctrl+4, the program coredumps.
Doing it in ksh or sh has no effect though.
This is in OpenBSD 6.4 AMD64 from Putty on Windows.
The console interaction looks like this:
$ cat
^\Quit (core dumped)
$
Is ctrl+4 a universal SIGQUIT+coredump shortcut?
Where are the other shortcuts apart from ctrl+C, ctrl+Z, ctrl+D,
documented?
Tinker
Re: syntax error and doas.conf
Hi Bruno,
Am 31.10.2018 um 12:23 schrieb Bruno Flueckiger:
> On 31.10.18 10:42, Markus Rosjat wrote:
> Losing ten minutes time because of a mistake you've made all by yourself
> made you write this useles mail. Imagine how many times you could have
> read the man page of doas(8) and find out that there is the parameter -C
> to check the config file.
>
> Cheers,
> Bruno
>
thank you for the attitude!
Now I learned even more it's better not to share mistakes and keep them
to yourself so the real pros are not bored by your findings because they
are to simple to be made.
I appreciate it!
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Am 31.10.2018 um 12:23 schrieb Bruno Flueckiger:
> On 31.10.18 10:42, Markus Rosjat wrote:
> Losing ten minutes time because of a mistake you've made all by yourself
> made you write this useles mail. Imagine how many times you could have
> read the man page of doas(8) and find out that there is the parameter -C
> to check the config file.
>
> Cheers,
> Bruno
>
thank you for the attitude!
Now I learned even more it's better not to share mistakes and keep them
to yourself so the real pros are not bored by your findings because they
are to simple to be made.
I appreciate it!
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
[UPDATE] net/p5-POE-Component-Client-DNS 1.051 -> 1.054 (p5-POE* update 8/14)
Index: Makefile
===================================================================
RCS file: /cvs/ports/net/p5-POE-Component-Client-DNS/Makefile,v
retrieving revision 1.15
diff -u -p -u -p -r1.15 Makefile
--- Makefile 8 Dec 2017 12:31:48 -0000 1.15
+++ Makefile 28 Oct 2018 19:12:26 -0000
@@ -4,9 +4,9 @@ COMMENT= DNS module for the Perl Object
MODULES= cpan
PKG_ARCH= *
-DISTNAME= POE-Component-Client-DNS-1.051
+DISTNAME= POE-Component-Client-DNS-1.054
CATEGORIES= net
-FIX_EXTRACT_PERMISSIONS=Yes
+FIX_EXTRACT_PERMISSIONS= Yes
# perl
PERMIT_PACKAGE_CDROM= Yes
@@ -14,7 +14,9 @@ PERMIT_PACKAGE_CDROM= Yes
RUN_DEPENDS= devel/p5-POE \
net/p5-Net-DNS
BUILD_DEPENDS= ${RUN_DEPENDS}
+TEST_DEPENDS= devel/p5-Test-NoWarnings
-TEST_DEPENDS=devel/p5-Test-NoWarnings
+# requires Pod::Coverage::TrustPod that we don't ship.
+TEST_ENV= AUTHOR_TESTING=0
.include <bsd.port.mk>
Index: distinfo
===================================================================
RCS file: /cvs/ports/net/p5-POE-Component-Client-DNS/distinfo,v
retrieving revision 1.9
diff -u -p -u -p -r1.9 distinfo
--- distinfo 18 Jan 2015 03:14:48 -0000 1.9
+++ distinfo 28 Oct 2018 19:12:26 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Component-Client-DNS-1.051.tar.gz) = 7r2JRTKVXTC5RLFED4CSiBTKGF6idxjeTCdWuiX1v0Q=
-SIZE (POE-Component-Client-DNS-1.051.tar.gz) = 14824
+SHA256 (POE-Component-Client-DNS-1.054.tar.gz) = sZoGkgppt0wnErtaSLcZzliWUwnZvrPio12P94NiXDE=
+SIZE (POE-Component-Client-DNS-1.054.tar.gz) = 28412
Here is an update for POE::Component::Client::DNS, a DNS module for
POE.
The changelog has been truncated here too [1].
What's new in the port:
- fixed some spacing inconsistencies
Testing:
'make test' runs fine.
Any comment?
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Component-Client-DNS
===================================================================
RCS file: /cvs/ports/net/p5-POE-Component-Client-DNS/Makefile,v
retrieving revision 1.15
diff -u -p -u -p -r1.15 Makefile
--- Makefile 8 Dec 2017 12:31:48 -0000 1.15
+++ Makefile 28 Oct 2018 19:12:26 -0000
@@ -4,9 +4,9 @@ COMMENT= DNS module for the Perl Object
MODULES= cpan
PKG_ARCH= *
-DISTNAME= POE-Component-Client-DNS-1.051
+DISTNAME= POE-Component-Client-DNS-1.054
CATEGORIES= net
-FIX_EXTRACT_PERMISSIONS=Yes
+FIX_EXTRACT_PERMISSIONS= Yes
# perl
PERMIT_PACKAGE_CDROM= Yes
@@ -14,7 +14,9 @@ PERMIT_PACKAGE_CDROM= Yes
RUN_DEPENDS= devel/p5-POE \
net/p5-Net-DNS
BUILD_DEPENDS= ${RUN_DEPENDS}
+TEST_DEPENDS= devel/p5-Test-NoWarnings
-TEST_DEPENDS=devel/p5-Test-NoWarnings
+# requires Pod::Coverage::TrustPod that we don't ship.
+TEST_ENV= AUTHOR_TESTING=0
.include <bsd.port.mk>
Index: distinfo
===================================================================
RCS file: /cvs/ports/net/p5-POE-Component-Client-DNS/distinfo,v
retrieving revision 1.9
diff -u -p -u -p -r1.9 distinfo
--- distinfo 18 Jan 2015 03:14:48 -0000 1.9
+++ distinfo 28 Oct 2018 19:12:26 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Component-Client-DNS-1.051.tar.gz) = 7r2JRTKVXTC5RLFED4CSiBTKGF6idxjeTCdWuiX1v0Q=
-SIZE (POE-Component-Client-DNS-1.051.tar.gz) = 14824
+SHA256 (POE-Component-Client-DNS-1.054.tar.gz) = sZoGkgppt0wnErtaSLcZzliWUwnZvrPio12P94NiXDE=
+SIZE (POE-Component-Client-DNS-1.054.tar.gz) = 28412
Here is an update for POE::Component::Client::DNS, a DNS module for
POE.
The changelog has been truncated here too [1].
What's new in the port:
- fixed some spacing inconsistencies
Testing:
'make test' runs fine.
Any comment?
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Component-Client-DNS
[UPDATE] devel/p5-POE-Loop-Tk 1.302 -> 1.305 (p5-POE* update 7/14)
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Tk/Makefile,v
retrieving revision 1.13
diff -u -p -u -p -r1.13 Makefile
--- Makefile 5 Dec 2017 16:25:45 -0000 1.13
+++ Makefile 27 Oct 2018 21:35:32 -0000
@@ -2,8 +2,7 @@
COMMENT= bridge that allows POE to be driven by Tk
-DISTNAME= POE-Loop-Tk-1.302
-REVISION= 1
+DISTNAME= POE-Loop-Tk-1.305
CATEGORIES= devel
FIX_EXTRACT_PERMISSIONS=Yes
@@ -15,9 +14,11 @@ PERMIT_PACKAGE_CDROM= Yes
CONFIGURE_ARGS+= --default
-BUILD_DEPENDS= devel/p5-POE-Test-Loops
+BUILD_DEPENDS= devel/p5-POE-Test-Loops>=1.352
RUN_DEPENDS+= x11/p5-Tk \
- devel/p5-POE>=1.006
+ devel/p5-POE>=1.367
+TEST_DEPENDS= devel/p5-Term-Size \
+ net/p5-Socket-GetAddrInfo
TEST_IS_INTERACTIVE= x11
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Tk/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 18 Jan 2015 03:13:32 -0000 1.2
+++ distinfo 27 Oct 2018 21:35:32 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Loop-Tk-1.302.tar.gz) = TTjTIaztbIgyZ07ivXNgYyyKVrrK72FCylaERqhWYS8=
-SIZE (POE-Loop-Tk-1.302.tar.gz) = 8291
+SHA256 (POE-Loop-Tk-1.305.tar.gz) = IjNqvCXwzMoEMaiAwYuaHCRbRIQhdIi2TOZ+CjGuaV8=
+SIZE (POE-Loop-Tk-1.305.tar.gz) = 8674
Here is an update for POE::Loop::Tk, a bridge that allows POE to be
driven by Tk.
The changelog has been truncated here too [1].
What's new in the port:
- Enable more tests by adding test dependencies.
Testing:
- 'make test' doesn't pass because it can't find
comp_tcp_concurrent.pm (and me neither). This is not a regression, the
current version we're shipping has the same issue. Otherwise it's fine.
Comments and feedback are welcome!
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Loop-Tk
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Tk/Makefile,v
retrieving revision 1.13
diff -u -p -u -p -r1.13 Makefile
--- Makefile 5 Dec 2017 16:25:45 -0000 1.13
+++ Makefile 27 Oct 2018 21:35:32 -0000
@@ -2,8 +2,7 @@
COMMENT= bridge that allows POE to be driven by Tk
-DISTNAME= POE-Loop-Tk-1.302
-REVISION= 1
+DISTNAME= POE-Loop-Tk-1.305
CATEGORIES= devel
FIX_EXTRACT_PERMISSIONS=Yes
@@ -15,9 +14,11 @@ PERMIT_PACKAGE_CDROM= Yes
CONFIGURE_ARGS+= --default
-BUILD_DEPENDS= devel/p5-POE-Test-Loops
+BUILD_DEPENDS= devel/p5-POE-Test-Loops>=1.352
RUN_DEPENDS+= x11/p5-Tk \
- devel/p5-POE>=1.006
+ devel/p5-POE>=1.367
+TEST_DEPENDS= devel/p5-Term-Size \
+ net/p5-Socket-GetAddrInfo
TEST_IS_INTERACTIVE= x11
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Tk/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 18 Jan 2015 03:13:32 -0000 1.2
+++ distinfo 27 Oct 2018 21:35:32 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Loop-Tk-1.302.tar.gz) = TTjTIaztbIgyZ07ivXNgYyyKVrrK72FCylaERqhWYS8=
-SIZE (POE-Loop-Tk-1.302.tar.gz) = 8291
+SHA256 (POE-Loop-Tk-1.305.tar.gz) = IjNqvCXwzMoEMaiAwYuaHCRbRIQhdIi2TOZ+CjGuaV8=
+SIZE (POE-Loop-Tk-1.305.tar.gz) = 8674
Here is an update for POE::Loop::Tk, a bridge that allows POE to be
driven by Tk.
The changelog has been truncated here too [1].
What's new in the port:
- Enable more tests by adding test dependencies.
Testing:
- 'make test' doesn't pass because it can't find
comp_tcp_concurrent.pm (and me neither). This is not a regression, the
current version we're shipping has the same issue. Otherwise it's fine.
Comments and feedback are welcome!
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Loop-Tk
[UPDATE] devel/p5-POE-Loop-Event 1.302 -> 1.305 (p5-POE* update 6/14)
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Event/Makefile,v
retrieving revision 1.10
diff -u -p -u -p -r1.10 Makefile
--- Makefile 5 Dec 2017 16:25:45 -0000 1.10
+++ Makefile 27 Oct 2018 21:19:44 -0000
@@ -2,9 +2,9 @@
COMMENT= bridge that allows POE to be driven by Event.pm
-DISTNAME= POE-Loop-Event-1.302
-REVISION= 0
+DISTNAME= POE-Loop-Event-1.305
CATEGORIES= devel
+
FIX_EXTRACT_PERMISSIONS=Yes
MODULES= cpan
@@ -15,8 +15,10 @@ PERMIT_PACKAGE_CDROM= Yes
CONFIGURE_ARGS+= --default
-BUILD_DEPENDS= devel/p5-POE-Test-Loops
+BUILD_DEPENDS= devel/p5-POE-Test-Loops>=1.352
RUN_DEPENDS+= devel/p5-Event \
- devel/p5-POE>1.006
+ devel/p5-POE>=1.367
+TEST_DEPENDS= devel/p5-Term-Size \
+ net/p5-Socket-GetAddrInfo
.include <bsd.port.mk>
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Event/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 18 Jan 2015 03:13:32 -0000 1.2
+++ distinfo 27 Oct 2018 21:19:44 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Loop-Event-1.302.tar.gz) = tc/CbrNGFNFoMIrH2AdrBsG/oyKNDa3CxfQmN1gpdTk=
-SIZE (POE-Loop-Event-1.302.tar.gz) = 4739
+SHA256 (POE-Loop-Event-1.305.tar.gz) = lPIHRKRHJu2j8Esw8igH4KFK2wg2KGVqJdVFiHG1HzQ=
+SIZE (POE-Loop-Event-1.305.tar.gz) = 4980
Here is an update for POE::Loop::Event.
The changelog is there [1], there is nothing to say as it has been
truncated.
What's new in port:
- Enabled more tests with new dependencies.
Testing:
- 'make test' passes.
Comments are welcome!
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Loop-Event
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Event/Makefile,v
retrieving revision 1.10
diff -u -p -u -p -r1.10 Makefile
--- Makefile 5 Dec 2017 16:25:45 -0000 1.10
+++ Makefile 27 Oct 2018 21:19:44 -0000
@@ -2,9 +2,9 @@
COMMENT= bridge that allows POE to be driven by Event.pm
-DISTNAME= POE-Loop-Event-1.302
-REVISION= 0
+DISTNAME= POE-Loop-Event-1.305
CATEGORIES= devel
+
FIX_EXTRACT_PERMISSIONS=Yes
MODULES= cpan
@@ -15,8 +15,10 @@ PERMIT_PACKAGE_CDROM= Yes
CONFIGURE_ARGS+= --default
-BUILD_DEPENDS= devel/p5-POE-Test-Loops
+BUILD_DEPENDS= devel/p5-POE-Test-Loops>=1.352
RUN_DEPENDS+= devel/p5-Event \
- devel/p5-POE>1.006
+ devel/p5-POE>=1.367
+TEST_DEPENDS= devel/p5-Term-Size \
+ net/p5-Socket-GetAddrInfo
.include <bsd.port.mk>
Index: distinfo
===================================================================
RCS file: /cvs/ports/devel/p5-POE-Loop-Event/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 18 Jan 2015 03:13:32 -0000 1.2
+++ distinfo 27 Oct 2018 21:19:44 -0000
@@ -1,2 +1,2 @@
-SHA256 (POE-Loop-Event-1.302.tar.gz) = tc/CbrNGFNFoMIrH2AdrBsG/oyKNDa3CxfQmN1gpdTk=
-SIZE (POE-Loop-Event-1.302.tar.gz) = 4739
+SHA256 (POE-Loop-Event-1.305.tar.gz) = lPIHRKRHJu2j8Esw8igH4KFK2wg2KGVqJdVFiHG1HzQ=
+SIZE (POE-Loop-Event-1.305.tar.gz) = 4980
Here is an update for POE::Loop::Event.
The changelog is there [1], there is nothing to say as it has been
truncated.
What's new in port:
- Enabled more tests with new dependencies.
Testing:
- 'make test' passes.
Comments are welcome!
Charlène.
[1] https://metacpan.org/changes/distribution/POE-Loop-Event
[NEW] devel/p5-POE-Component-Syndicator 0.06 (p5-POE* update 5/14)
Hi ports!
Here is a new port for POE::Component::Syndicator. It will be needed
for updating net/p5-POE-Component-IRC.
From DESCR:
POE::Component::Syndicator is a base class for POE components which
need to handle a persistent resource (e.g. a connection to an IRC
server) for one or more sessions in an extendable way.
WWW: https://metacpan.org/pod/POE::Component::Syndicator
'make test' passes.
Any comments/feedback ?
Charlène.
Here is a new port for POE::Component::Syndicator. It will be needed
for updating net/p5-POE-Component-IRC.
From DESCR:
POE::Component::Syndicator is a base class for POE components which
need to handle a persistent resource (e.g. a connection to an IRC
server) for one or more sessions in an extendable way.
WWW: https://metacpan.org/pod/POE::Component::Syndicator
'make test' passes.
Any comments/feedback ?
Charlène.
UPDATE: x11/kde-applications/cervisia (KDE4 replacement)
Hi All.
please find attached cervisia 18.08.2. Added "@conflict kde-i18n-*" "@conflict
kde-l10n-*" to avoid conflicts with KDE3/4 l10n stuff.
Tested with our ports and src tree. Works fine and if you test it, you'll
really enjoy the visual `cvs log` functions.
$ pkg_info cervisia
---------------------------------------------------------------------------
Information for inst:cervisia-18.08.2
Comment:
CVS GUI for KDE
Description:
Cervisia is a user friendly version control system front-end. The
aim is to support CVS and other version control system programs in
a unified interface, featuring conflict resolution, difference and
history viewers, status for the working copy files, and support for
most version control functions.
Maintainer: KDE porting team <openbsd-kde@googlegroups.com>
---------------------------------------------------------------------------
OK to import, unhook KDE4 cervisia and adjust meta/kde4?
Rafael Sadowski
please find attached cervisia 18.08.2. Added "@conflict kde-i18n-*" "@conflict
kde-l10n-*" to avoid conflicts with KDE3/4 l10n stuff.
Tested with our ports and src tree. Works fine and if you test it, you'll
really enjoy the visual `cvs log` functions.
$ pkg_info cervisia
---------------------------------------------------------------------------
Information for inst:cervisia-18.08.2
Comment:
CVS GUI for KDE
Description:
Cervisia is a user friendly version control system front-end. The
aim is to support CVS and other version control system programs in
a unified interface, featuring conflict resolution, difference and
history viewers, status for the working copy files, and support for
most version control functions.
Maintainer: KDE porting team <openbsd-kde@googlegroups.com>
---------------------------------------------------------------------------
OK to import, unhook KDE4 cervisia and adjust meta/kde4?
Rafael Sadowski
Regarding x11/lxqt not working on powerpc
Thanks landry@ for the bulk:
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/compton-conf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libfm-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libqtxdg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libsysstat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/obconf-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/pavucontrol-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/qtermwidget.log
All give the same error:
eg++: error: -fuse-linker-plugin is not supported in this configuration
Maybe someone with more knowledge sees the error as spots the problem
right away...
Anyways, I really don't know much about powerpc and I'm short on time this days.
Should I flag this as:
NOT_FOR_ARCHS = powerpc
?
Cheers.
Elias.
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/compton-conf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libfm-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libqtxdg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libsysstat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/obconf-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/pavucontrol-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/qtermwidget.log
All give the same error:
eg++: error: -fuse-linker-plugin is not supported in this configuration
Maybe someone with more knowledge sees the error as spots the problem
right away...
Anyways, I really don't know much about powerpc and I'm short on time this days.
Should I flag this as:
NOT_FOR_ARCHS = powerpc
?
Cheers.
Elias.
[M. Update] net/py-zmq 17.1.2
Index: net/py-zmq/Makefile
===================================================================
RCS file: /cvs/ports/net/py-zmq/Makefile,v
retrieving revision 1.19
diff -u -p -u -r1.19 Makefile
--- net/py-zmq/Makefile 25 Sep 2018 14:49:12 -0000 1.19
+++ net/py-zmq/Makefile 31 Oct 2018 11:47:41 -0000
@@ -1,8 +1,8 @@
-# $OpenBSD: Makefile,v 1.19 2018/09/25 14:49:12 bket Exp $
+$OpenBSD: Makefile,v 1.19 2018/09/25 14:49:12 bket Exp $
COMMENT = Python bindings for ZeroMQ
-MODPY_EGG_VERSION = 16.0.3
+MODPY_EGG_VERSION = 17.1.2
DISTNAME = pyzmq-${MODPY_EGG_VERSION}
PKGNAME = ${DISTNAME:S/py/py-/}
EPOCH = 0
@@ -22,10 +22,6 @@ MODULES = lang/python
LIB_DEPENDS = ${MODPY_LIB_DEPENDS} \
net/zeromq
-
-# ssh tunnelling
-RUN_DEPENDS = security/py-paramiko${MODPY_FLAVOR} \
- devel/py-pexpect${MODPY_FLAVOR}
MODPY_PI = Yes
MODPY_DISTUTILS_BUILDARGS = --zmq=${LOCALBASE}
Index: net/py-zmq/distinfo
===================================================================
RCS file: /cvs/ports/net/py-zmq/distinfo,v
retrieving revision 1.14
diff -u -p -u -r1.14 distinfo
--- net/py-zmq/distinfo 25 Sep 2018 14:49:12 -0000 1.14
+++ net/py-zmq/distinfo 31 Oct 2018 11:47:41 -0000
@@ -1,2 +1,2 @@
-SHA256 (pyzmq-16.0.3.tar.gz) = iog4JBR1I8D+dtJH3ViZTBwo7wfxzF3eWVpP0cKPJYA=
-SIZE (pyzmq-16.0.3.tar.gz) = 1063036
+SHA256 (pyzmq-17.1.2.tar.gz) = pyuCrBkQ8s9hpJE59JdPmUmER193Gw+qcwg5YH7u3d8=
+SIZE (pyzmq-17.1.2.tar.gz) = 1080194
Index: net/py-zmq/pkg/PLIST
===================================================================
RCS file: /cvs/ports/net/py-zmq/pkg/PLIST,v
retrieving revision 1.12
diff -u -p -u -r1.12 PLIST
--- net/py-zmq/pkg/PLIST 25 Sep 2018 14:49:12 -0000 1.12
+++ net/py-zmq/pkg/PLIST 31 Oct 2018 11:47:41 -0000
@@ -4,8 +4,10 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}/
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}_future.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}decorators.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}error.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/_future.py
lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/${MODPY_PYCACHE}/
@@ -96,9 +98,11 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}/
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}_deprecated.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}future.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}ioloop.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}zmqstream.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/_deprecated.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/future.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/ioloop.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/minitornado/
@@ -194,6 +198,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_context.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_decorators.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_device.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_draft.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_error.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_etc.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_future.${MODPY_PYC_MAGIC_TAG}pyc
@@ -231,6 +236,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_context.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_decorators.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_device.py
+lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_draft.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_error.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_etc.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_future.py
@@ -277,6 +283,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/utils/ipcmaxlen.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/jsonapi.py
lib/python${MODPY_VERSION}/site-packages/zmq/utils/monitor.py
+lib/python${MODPY_VERSION}/site-packages/zmq/utils/mutex.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/pyversion_compat.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/sixcerpt.py
lib/python${MODPY_VERSION}/site-packages/zmq/utils/strtypes.py
This diff can now be reapplied (py-zmq was rollbacked to 16) now
working with the versions of matplotlib (thanks Daniel Dickman),
py-ipython and py-ipykernel.
Thanks to Björn Ketelaars for the help with this one.
Cheers.
Elias.
===================================================================
RCS file: /cvs/ports/net/py-zmq/Makefile,v
retrieving revision 1.19
diff -u -p -u -r1.19 Makefile
--- net/py-zmq/Makefile 25 Sep 2018 14:49:12 -0000 1.19
+++ net/py-zmq/Makefile 31 Oct 2018 11:47:41 -0000
@@ -1,8 +1,8 @@
-# $OpenBSD: Makefile,v 1.19 2018/09/25 14:49:12 bket Exp $
+$OpenBSD: Makefile,v 1.19 2018/09/25 14:49:12 bket Exp $
COMMENT = Python bindings for ZeroMQ
-MODPY_EGG_VERSION = 16.0.3
+MODPY_EGG_VERSION = 17.1.2
DISTNAME = pyzmq-${MODPY_EGG_VERSION}
PKGNAME = ${DISTNAME:S/py/py-/}
EPOCH = 0
@@ -22,10 +22,6 @@ MODULES = lang/python
LIB_DEPENDS = ${MODPY_LIB_DEPENDS} \
net/zeromq
-
-# ssh tunnelling
-RUN_DEPENDS = security/py-paramiko${MODPY_FLAVOR} \
- devel/py-pexpect${MODPY_FLAVOR}
MODPY_PI = Yes
MODPY_DISTUTILS_BUILDARGS = --zmq=${LOCALBASE}
Index: net/py-zmq/distinfo
===================================================================
RCS file: /cvs/ports/net/py-zmq/distinfo,v
retrieving revision 1.14
diff -u -p -u -r1.14 distinfo
--- net/py-zmq/distinfo 25 Sep 2018 14:49:12 -0000 1.14
+++ net/py-zmq/distinfo 31 Oct 2018 11:47:41 -0000
@@ -1,2 +1,2 @@
-SHA256 (pyzmq-16.0.3.tar.gz) = iog4JBR1I8D+dtJH3ViZTBwo7wfxzF3eWVpP0cKPJYA=
-SIZE (pyzmq-16.0.3.tar.gz) = 1063036
+SHA256 (pyzmq-17.1.2.tar.gz) = pyuCrBkQ8s9hpJE59JdPmUmER193Gw+qcwg5YH7u3d8=
+SIZE (pyzmq-17.1.2.tar.gz) = 1080194
Index: net/py-zmq/pkg/PLIST
===================================================================
RCS file: /cvs/ports/net/py-zmq/pkg/PLIST,v
retrieving revision 1.12
diff -u -p -u -r1.12 PLIST
--- net/py-zmq/pkg/PLIST 25 Sep 2018 14:49:12 -0000 1.12
+++ net/py-zmq/pkg/PLIST 31 Oct 2018 11:47:41 -0000
@@ -4,8 +4,10 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}/
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}_future.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}decorators.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/${MODPY_PYCACHE}error.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/_future.py
lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/asyncio/${MODPY_PYCACHE}/
@@ -96,9 +98,11 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}/
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}_deprecated.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}future.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}ioloop.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/${MODPY_PYCACHE}zmqstream.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/_deprecated.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/future.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/ioloop.py
lib/python${MODPY_VERSION}/site-packages/zmq/eventloop/minitornado/
@@ -194,6 +198,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_context.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_decorators.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_device.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_draft.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_error.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_etc.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/zmq/tests/${MODPY_PYCACHE}test_future.${MODPY_PYC_MAGIC_TAG}pyc
@@ -231,6 +236,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_context.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_decorators.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_device.py
+lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_draft.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_error.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_etc.py
lib/python${MODPY_VERSION}/site-packages/zmq/tests/test_future.py
@@ -277,6 +283,7 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/zmq/utils/ipcmaxlen.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/jsonapi.py
lib/python${MODPY_VERSION}/site-packages/zmq/utils/monitor.py
+lib/python${MODPY_VERSION}/site-packages/zmq/utils/mutex.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/pyversion_compat.h
lib/python${MODPY_VERSION}/site-packages/zmq/utils/sixcerpt.py
lib/python${MODPY_VERSION}/site-packages/zmq/utils/strtypes.py
This diff can now be reapplied (py-zmq was rollbacked to 16) now
working with the versions of matplotlib (thanks Daniel Dickman),
py-ipython and py-ipykernel.
Thanks to Björn Ketelaars for the help with this one.
Cheers.
Elias.
[M. Update] devel/py-jedi 0.12.1 -> 0.13.1
Index: devel/py-jedi/Makefile
===================================================================
RCS file: /cvs/ports/devel/py-jedi/Makefile,v
retrieving revision 1.5
diff -u -p -u -r1.5 Makefile
--- devel/py-jedi/Makefile 15 Jul 2018 23:04:32 -0000 1.5
+++ devel/py-jedi/Makefile 31 Oct 2018 11:36:30 -0000
@@ -2,7 +2,7 @@
COMMENT = autocompletion tool for Python
-MODPY_EGG_VERSION = 0.12.1
+MODPY_EGG_VERSION = 0.13.1
DISTNAME = jedi-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME}
@@ -23,17 +23,12 @@ MODPY_SETUPTOOLS = Yes
RUN_DEPENDS = devel/py-parso${MODPY_FLAVOR}
TEST_DEPENDS = ${RUN_DEPENDS} \
- devel/py-test${MODPY_FLAVOR}
+ devel/py-test${MODPY_FLAVOR} \
+ devel/py-docopt${MODPY_FLAVOR} \
+ devel/py-colorama${MODPY_FLAVOR}
FLAVORS = python3
FLAVOR ?=
-
-.if !${FLAVOR:Mpython3}
-TEST_DEPENDS += devel/py-docopt \
- devel/py-typing
-.else
-TEST_ARGS = --ignore=test/test_evaluate/flask-site-packages
-.endif
do-test:
cd ${WRKSRC} && ${MODPY_BIN} -m pytest ${TEST_ARGS} jedi test
Index: devel/py-jedi/distinfo
===================================================================
RCS file: /cvs/ports/devel/py-jedi/distinfo,v
retrieving revision 1.4
diff -u -p -u -r1.4 distinfo
--- devel/py-jedi/distinfo 15 Jul 2018 23:04:32 -0000 1.4
+++ devel/py-jedi/distinfo 31 Oct 2018 11:36:30 -0000
@@ -1,2 +1,2 @@
-SHA256 (jedi-0.12.1.tar.gz) = tAntD2kTpwHtR0phSju0bmlTY5Az4x92nKdYHaW9HsE=
-SIZE (jedi-0.12.1.tar.gz) = 361831
+SHA256 (jedi-0.13.1.tar.gz) = t0k/c6L+vg3DPVHJm0dFR/f2wLLI+ysh9FPu8gTBIUg=
+SIZE (jedi-0.13.1.tar.gz) = 365356
Changelog:
https://github.com/davidhalter/jedi/blob/master/CHANGELOG.rst#0131-2018-10-02
Mainly bugfixes and additions. Those changes shouldn't affect consumers.
Regression test passing.
Tested with devel/spyder/spyder OK.
Cheers.
Elias.
===================================================================
RCS file: /cvs/ports/devel/py-jedi/Makefile,v
retrieving revision 1.5
diff -u -p -u -r1.5 Makefile
--- devel/py-jedi/Makefile 15 Jul 2018 23:04:32 -0000 1.5
+++ devel/py-jedi/Makefile 31 Oct 2018 11:36:30 -0000
@@ -2,7 +2,7 @@
COMMENT = autocompletion tool for Python
-MODPY_EGG_VERSION = 0.12.1
+MODPY_EGG_VERSION = 0.13.1
DISTNAME = jedi-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME}
@@ -23,17 +23,12 @@ MODPY_SETUPTOOLS = Yes
RUN_DEPENDS = devel/py-parso${MODPY_FLAVOR}
TEST_DEPENDS = ${RUN_DEPENDS} \
- devel/py-test${MODPY_FLAVOR}
+ devel/py-test${MODPY_FLAVOR} \
+ devel/py-docopt${MODPY_FLAVOR} \
+ devel/py-colorama${MODPY_FLAVOR}
FLAVORS = python3
FLAVOR ?=
-
-.if !${FLAVOR:Mpython3}
-TEST_DEPENDS += devel/py-docopt \
- devel/py-typing
-.else
-TEST_ARGS = --ignore=test/test_evaluate/flask-site-packages
-.endif
do-test:
cd ${WRKSRC} && ${MODPY_BIN} -m pytest ${TEST_ARGS} jedi test
Index: devel/py-jedi/distinfo
===================================================================
RCS file: /cvs/ports/devel/py-jedi/distinfo,v
retrieving revision 1.4
diff -u -p -u -r1.4 distinfo
--- devel/py-jedi/distinfo 15 Jul 2018 23:04:32 -0000 1.4
+++ devel/py-jedi/distinfo 31 Oct 2018 11:36:30 -0000
@@ -1,2 +1,2 @@
-SHA256 (jedi-0.12.1.tar.gz) = tAntD2kTpwHtR0phSju0bmlTY5Az4x92nKdYHaW9HsE=
-SIZE (jedi-0.12.1.tar.gz) = 361831
+SHA256 (jedi-0.13.1.tar.gz) = t0k/c6L+vg3DPVHJm0dFR/f2wLLI+ysh9FPu8gTBIUg=
+SIZE (jedi-0.13.1.tar.gz) = 365356
Changelog:
https://github.com/davidhalter/jedi/blob/master/CHANGELOG.rst#0131-2018-10-02
Mainly bugfixes and additions. Those changes shouldn't affect consumers.
Regression test passing.
Tested with devel/spyder/spyder OK.
Cheers.
Elias.
[M. Update] x11/py-qtpy 1.5.1 -> 1.5.2
Index: x11/py-qtpy/Makefile
===================================================================
RCS file: /cvs/ports/x11/py-qtpy/Makefile,v
retrieving revision 1.6
diff -u -p -u -r1.6 Makefile
--- x11/py-qtpy/Makefile 29 Sep 2018 08:38:04 -0000 1.6
+++ x11/py-qtpy/Makefile 31 Oct 2018 11:36:09 -0000
@@ -2,7 +2,7 @@
COMMENT = provides an abstraction layer of various Qt bindings
-MODPY_EGG_VERSION = 1.5.1
+MODPY_EGG_VERSION = 1.5.2
DISTNAME = QtPy-${MODPY_EGG_VERSION}
PKGNAME = py-qtpy-${MODPY_EGG_VERSION}
CATEGORIES = x11
Index: x11/py-qtpy/distinfo
===================================================================
RCS file: /cvs/ports/x11/py-qtpy/distinfo,v
retrieving revision 1.5
diff -u -p -u -r1.5 distinfo
--- x11/py-qtpy/distinfo 29 Sep 2018 08:38:04 -0000 1.5
+++ x11/py-qtpy/distinfo 31 Oct 2018 11:36:09 -0000
@@ -1,2 +1,2 @@
-SHA256 (QtPy-1.5.1.tar.gz) = wMKgoUJbLBZnN+8hmQS+GwRWeh7/lMLtFG8DOir7ODs=
-SIZE (QtPy-1.5.1.tar.gz) = 30269
+SHA256 (QtPy-1.5.2.tar.gz) = TGkPkFhsgsEhC7b99enuTRIogJQh3Go0nFr6zCfKq80=
+SIZE (QtPy-1.5.2.tar.gz) = 30387
Changelog:
https://github.com/spyder-ide/qtpy/blob/master/CHANGELOG.md#version-152-2018-10-20
Mainly bugfixes and additions. Those changes shouldn't affect consumers.
Regression test passing.
Tested with devel/spyder/spyder OK.
Cheers.
Elias.
===================================================================
RCS file: /cvs/ports/x11/py-qtpy/Makefile,v
retrieving revision 1.6
diff -u -p -u -r1.6 Makefile
--- x11/py-qtpy/Makefile 29 Sep 2018 08:38:04 -0000 1.6
+++ x11/py-qtpy/Makefile 31 Oct 2018 11:36:09 -0000
@@ -2,7 +2,7 @@
COMMENT = provides an abstraction layer of various Qt bindings
-MODPY_EGG_VERSION = 1.5.1
+MODPY_EGG_VERSION = 1.5.2
DISTNAME = QtPy-${MODPY_EGG_VERSION}
PKGNAME = py-qtpy-${MODPY_EGG_VERSION}
CATEGORIES = x11
Index: x11/py-qtpy/distinfo
===================================================================
RCS file: /cvs/ports/x11/py-qtpy/distinfo,v
retrieving revision 1.5
diff -u -p -u -r1.5 distinfo
--- x11/py-qtpy/distinfo 29 Sep 2018 08:38:04 -0000 1.5
+++ x11/py-qtpy/distinfo 31 Oct 2018 11:36:09 -0000
@@ -1,2 +1,2 @@
-SHA256 (QtPy-1.5.1.tar.gz) = wMKgoUJbLBZnN+8hmQS+GwRWeh7/lMLtFG8DOir7ODs=
-SIZE (QtPy-1.5.1.tar.gz) = 30269
+SHA256 (QtPy-1.5.2.tar.gz) = TGkPkFhsgsEhC7b99enuTRIogJQh3Go0nFr6zCfKq80=
+SIZE (QtPy-1.5.2.tar.gz) = 30387
Changelog:
https://github.com/spyder-ide/qtpy/blob/master/CHANGELOG.md#version-152-2018-10-20
Mainly bugfixes and additions. Those changes shouldn't affect consumers.
Regression test passing.
Tested with devel/spyder/spyder OK.
Cheers.
Elias.
Re: spamd and google smtp ips
* Stuart Henderson <stu@spacehopper.org> le [30-10-2018 23:39:23 +0000]:
> On 2018-10-30, Chris Narkiewicz <hello@ezaquarii.com> wrote:
> > Hi,
> >
> > I'm configuring spamd and I noticed that when I send an e-mail from
> > GMail, each time the e-mail is submitted by a different IP address.
> >
> > Here is spamdb output after sending a test email to myself:
> >
> > GREY|209.85.219.182|mail-yb1-f182.google.com|...
> > GREY|209.85.219.177|mail-yb1-f177.google.com|...
> > GREY|209.85.219.176|mail-yb1-f176.google.com|...
> > GREY|209.85.219.172|mail-yb1-f172.google.com|...
> > GREY|209.85.219.180|mail-yb1-f180.google.com|...
> > GREY|209.85.219.175|mail-yb1-f175.google.com|...
> > GREY|209.85.219.173|mail-yb1-f173.google.com|...
> > GREY|209.85.219.179|mail-yb1-f179.google.com|...
> > GREY|209.85.208.46|mail-ed1-f46.google.com|...
> > GREY|209.85.161.52|mail-yw1-f52.google.com|...
> > ... snip ...
> >
> > Of course they are not whitelisted, as each submission
> > attempt is done by a different node and I guess google has A LOT of
> > them. I see 2 issues with that:
> >
> > 1) e-mail delivery takes a lot of time (as google uses exponential
> > backoff and stops frequent retries after few failures)
> >
> > 2) whitelisted IPs are more likely being expired, as my server is
> > not getting a lot of gmail traffic
> >
> > I suppose different big e-mail providers will
> > have similar issues.
> >
> > I'm also running BGP server to download a whitelist,
> > but it does not contain google servers.
> >
> > Are there any solutions get around this problem? Ideally I'd like
> > to just whitelist reputable mail providers as I see little chance
> > that any spammer will outsmart Google/Yahoo/Microsoft/etc.
To solve this problem, I use two methods :
## whitelist from bsdly.net (thaniks again peter : )
In /etc/pf.conf
table <nospamd> persist file "/etc/mail/nospamd"
pass in on egress proto tcp from <nospamd> to any port smtp
/in /etc/weekly.local :
echo "update nospamd file"
ftp -o /etc/mail/nospamd http://www.bsdly.net/~peter/nospamd
## whitelist from spf walk :
In /etc/mail/spamd.conf :
all:\
:nixspam:bgp-spamd:bsdlyblack:whitelist:
...
whitelist:\
:white:\
:method=file:\
:file=/etc/mail/whitelist.txt
In /etc/weekly.local :
/usr/local/bin/domain-white-spamd
In /usr/local/bin/domain-white-spamd, adjust with domins you need :
TMP=$(mktemp)
WHITELIST=/etc/mail/whitelist.txt
DOMAINS='outlook.com
gmail.com
google.com
hotmail.com
yahoo.com
yahoo.fr
live.fr
mail-out.ovh.net
mxb.ovh.net
gandi.net
laposte.net
github.com
protonmail.com
'
for d in $DOMAINS; do
echo "$d" | smtpctl spf walk >> "$TMP"
done
mv "$TMP" "$WHITELIST"
exit 0
--
thuban
> On 2018-10-30, Chris Narkiewicz <hello@ezaquarii.com> wrote:
> > Hi,
> >
> > I'm configuring spamd and I noticed that when I send an e-mail from
> > GMail, each time the e-mail is submitted by a different IP address.
> >
> > Here is spamdb output after sending a test email to myself:
> >
> > GREY|209.85.219.182|mail-yb1-f182.google.com|...
> > GREY|209.85.219.177|mail-yb1-f177.google.com|...
> > GREY|209.85.219.176|mail-yb1-f176.google.com|...
> > GREY|209.85.219.172|mail-yb1-f172.google.com|...
> > GREY|209.85.219.180|mail-yb1-f180.google.com|...
> > GREY|209.85.219.175|mail-yb1-f175.google.com|...
> > GREY|209.85.219.173|mail-yb1-f173.google.com|...
> > GREY|209.85.219.179|mail-yb1-f179.google.com|...
> > GREY|209.85.208.46|mail-ed1-f46.google.com|...
> > GREY|209.85.161.52|mail-yw1-f52.google.com|...
> > ... snip ...
> >
> > Of course they are not whitelisted, as each submission
> > attempt is done by a different node and I guess google has A LOT of
> > them. I see 2 issues with that:
> >
> > 1) e-mail delivery takes a lot of time (as google uses exponential
> > backoff and stops frequent retries after few failures)
> >
> > 2) whitelisted IPs are more likely being expired, as my server is
> > not getting a lot of gmail traffic
> >
> > I suppose different big e-mail providers will
> > have similar issues.
> >
> > I'm also running BGP server to download a whitelist,
> > but it does not contain google servers.
> >
> > Are there any solutions get around this problem? Ideally I'd like
> > to just whitelist reputable mail providers as I see little chance
> > that any spammer will outsmart Google/Yahoo/Microsoft/etc.
To solve this problem, I use two methods :
## whitelist from bsdly.net (thaniks again peter : )
In /etc/pf.conf
table <nospamd> persist file "/etc/mail/nospamd"
pass in on egress proto tcp from <nospamd> to any port smtp
/in /etc/weekly.local :
echo "update nospamd file"
ftp -o /etc/mail/nospamd http://www.bsdly.net/~peter/nospamd
## whitelist from spf walk :
In /etc/mail/spamd.conf :
all:\
:nixspam:bgp-spamd:bsdlyblack:whitelist:
...
whitelist:\
:white:\
:method=file:\
:file=/etc/mail/whitelist.txt
In /etc/weekly.local :
/usr/local/bin/domain-white-spamd
In /usr/local/bin/domain-white-spamd, adjust with domins you need :
TMP=$(mktemp)
WHITELIST=/etc/mail/whitelist.txt
DOMAINS='outlook.com
gmail.com
google.com
hotmail.com
yahoo.com
yahoo.fr
live.fr
mail-out.ovh.net
mxb.ovh.net
gandi.net
laposte.net
github.com
protonmail.com
'
for d in $DOMAINS; do
echo "$d" | smtpctl spf walk >> "$TMP"
done
mv "$TMP" "$WHITELIST"
exit 0
--
thuban
Re: syntax error and doas.conf
On 31.10.18 10:42, Markus Rosjat wrote:
> Hi all,
>
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf
> file you can easily look you self out from root privilages :(
>
> consider a a case where your root has no pw, you are the guy in the
> wheel group and of course you have only this line
>
> permit persist keepenv :wheel
>
> so far everything is peachy ok we are going to add a new line
>
> permit nopass foo as root cmt /root/scripts/dosomething
>
> and we save it ... ups we did a mistake an like to fix it, no worries we
> can ... or cant we?
>
> doas vi /etc/doas.conf
>
> doas: syntax error at line 15
>
>
> at this point you are a bit screwed because you cant edit the doas.conf
> you cant reboot you only way seems to be a switch off. Ok maybe there
> other was but hey I'm no pro Im a simple user and its a vm so switch it
> off. Boot in single user mode, make a fsck because , mount the
> patritions, export the TERM var so yu get a vi. Well seems we are back
> in business but no we cant edit /etc/doas.conf. Doesnt matter we came so
> far we simply copy the exmaple to /etc and be done with it. At that
> point 5 to 10 min of your life is wasted with silly stuff but you may
> have learn at least one thing ... read again what you just wrote before
> you save it :)
>
>
> Have a nice day list :) and happy helloween
>
> --
> Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
>
> G+H Webservice GbR Gorzolla, Herrmann
> Königsbrücker Str. 70, 01099 Dresden
>
> http://www.ghweb.de
> fon: +49 351 8107220 fax: +49 351 8107227
>
> Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
>
Losing ten minutes time because of a mistake you've made all by yourself
made you write this useles mail. Imagine how many times you could have
read the man page of doas(8) and find out that there is the parameter -C
to check the config file.
Cheers,
Bruno
--
Don't trust a man wearing a better suit than your own
> Hi all,
>
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf
> file you can easily look you self out from root privilages :(
>
> consider a a case where your root has no pw, you are the guy in the
> wheel group and of course you have only this line
>
> permit persist keepenv :wheel
>
> so far everything is peachy ok we are going to add a new line
>
> permit nopass foo as root cmt /root/scripts/dosomething
>
> and we save it ... ups we did a mistake an like to fix it, no worries we
> can ... or cant we?
>
> doas vi /etc/doas.conf
>
> doas: syntax error at line 15
>
>
> at this point you are a bit screwed because you cant edit the doas.conf
> you cant reboot you only way seems to be a switch off. Ok maybe there
> other was but hey I'm no pro Im a simple user and its a vm so switch it
> off. Boot in single user mode, make a fsck because , mount the
> patritions, export the TERM var so yu get a vi. Well seems we are back
> in business but no we cant edit /etc/doas.conf. Doesnt matter we came so
> far we simply copy the exmaple to /etc and be done with it. At that
> point 5 to 10 min of your life is wasted with silly stuff but you may
> have learn at least one thing ... read again what you just wrote before
> you save it :)
>
>
> Have a nice day list :) and happy helloween
>
> --
> Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
>
> G+H Webservice GbR Gorzolla, Herrmann
> Königsbrücker Str. 70, 01099 Dresden
>
> http://www.ghweb.de
> fon: +49 351 8107220 fax: +49 351 8107227
>
> Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
>
Losing ten minutes time because of a mistake you've made all by yourself
made you write this useles mail. Imagine how many times you could have
read the man page of doas(8) and find out that there is the parameter -C
to check the config file.
Cheers,
Bruno
--
Don't trust a man wearing a better suit than your own
Re: fix HOMEPAGE on security/libfprint
On Wed, Oct 31, 2018 at 10:41:12AM +0100, Solene Rapenne wrote:
> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > On Wed, Oct 31, 2018 at 10:01:05AM +0100, Solene Rapenne wrote:
> > > Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > > > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > > > >
> > > > > there is a "a" in HOMEPAGE, and use https now
> > > >
> > > > Needs a bump.
> > > >
> > >
> > > new diff with REVISION bump + CC maintainer
> >
> > REVISION starts at 0.
>
> should be good now...
OK aja with s/http/https ;-)
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 09:39:45 -0000
> @@ -3,12 +3,13 @@
> COMMENT= library for fingerprint reader devices
>
> DISTNAME= libfprint-0.6.0
> +REVISION= 0
>
> CATEGORIES= security
>
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > On Wed, Oct 31, 2018 at 10:01:05AM +0100, Solene Rapenne wrote:
> > > Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > > > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > > > >
> > > > > there is a "a" in HOMEPAGE, and use https now
> > > >
> > > > Needs a bump.
> > > >
> > >
> > > new diff with REVISION bump + CC maintainer
> >
> > REVISION starts at 0.
>
> should be good now...
OK aja with s/http/https ;-)
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 09:39:45 -0000
> @@ -3,12 +3,13 @@
> COMMENT= library for fingerprint reader devices
>
> DISTNAME= libfprint-0.6.0
> +REVISION= 0
>
> CATEGORIES= security
>
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
Re: ikev2 and road warriors setup
On 10/28/18 3:04 PM, Radek wrote:
> Hello,
> I really need your help.
> I am still trying to configure Ikev2 VPN Gateway (A.B.C.77/23) for road warriors clients (Windows).
> The problem is that it works ONLY if clients are in the same subnet as VPN Gateway (A.B.C.0/23).
> Clients from out of the gateway's subnet (!A.B.C.0/23) can not establish the connection (809 Error). It does not matter if they are behind NAT or not, tried different ISP - the same.
>
> Current tested client is Win7 (1.2.3.119). It works from A.B.C.0/23
>
> I do not know what I am doing wrong.
> Can anyone please help me with solving this problem?
> Thank you.
>
> This is a fresh 6.3/i386 install:
> # cat /etc/hostname.enc0
> inet 10.0.1.1 255.255.255.0 10.0.1.255
> up
You don't need an IP on enc0
>
> # cat /etc/iked.conf
> ikev2 "test" passive esp \
> from 0.0.0.0/0 to 0.0.0.0/0 \
> local A.B.C.77 peer any \
> srcid A.B.C.77 \
> config address 10.0.1.0/24 \
> config name-server 8.8.8.8 \
> tag "IKED"
Try something like this, it works for both Win7 and Win10:
/etc/iked.conf
---------------------------------
ikev2 "roadWarrior" ipcomp esp \
from 0.0.0.0/0 to 0.0.0.0/0 \
peer any \
srcid $srcid \
config address 10.0.1.0/24 \
config netmask 255.255.255.0 \
config name-server $dns1 \
config name-server $dns2 \
config access-server A.B.C.77 \
config protected-subnet 0.0.0.0/0 \
tag "$id"
'access-server' tells Windows what gateway to use for 'protected-subnet'
(see iked.conf(5)).
> Hello,
> I really need your help.
> I am still trying to configure Ikev2 VPN Gateway (A.B.C.77/23) for road warriors clients (Windows).
> The problem is that it works ONLY if clients are in the same subnet as VPN Gateway (A.B.C.0/23).
> Clients from out of the gateway's subnet (!A.B.C.0/23) can not establish the connection (809 Error). It does not matter if they are behind NAT or not, tried different ISP - the same.
>
> Current tested client is Win7 (1.2.3.119). It works from A.B.C.0/23
>
> I do not know what I am doing wrong.
> Can anyone please help me with solving this problem?
> Thank you.
>
> This is a fresh 6.3/i386 install:
> # cat /etc/hostname.enc0
> inet 10.0.1.1 255.255.255.0 10.0.1.255
> up
You don't need an IP on enc0
>
> # cat /etc/iked.conf
> ikev2 "test" passive esp \
> from 0.0.0.0/0 to 0.0.0.0/0 \
> local A.B.C.77 peer any \
> srcid A.B.C.77 \
> config address 10.0.1.0/24 \
> config name-server 8.8.8.8 \
> tag "IKED"
Try something like this, it works for both Win7 and Win10:
/etc/iked.conf
---------------------------------
ikev2 "roadWarrior" ipcomp esp \
from 0.0.0.0/0 to 0.0.0.0/0 \
peer any \
srcid $srcid \
config address 10.0.1.0/24 \
config netmask 255.255.255.0 \
config name-server $dns1 \
config name-server $dns2 \
config access-server A.B.C.77 \
config protected-subnet 0.0.0.0/0 \
tag "$id"
'access-server' tells Windows what gateway to use for 'protected-subnet'
(see iked.conf(5)).
Re: [UPDATE] devel/ipython 5.3.0p0 -> 5.8.0 and devel/py-ipykernel 4.6.1p0 -> 4.9.0
OK by me to do the update, there is at least a new version of
py-ipykernel, but if is not a problem I would prefer to push this
commit, fix the problem with the dependencies of ipykernel and ipython
and then update each for separate.
Cheers.
Elias.
El lun., 29 oct. 2018 a las 1:18, Björn Ketelaars
(<bjorn.ketelaars@hydroxide.nl>) escribió:
>
> On Thu 06/09/2018 13:17, Elias M. Mariani wrote:
> > You are right, I forgot to attach the diff...
> > Here is the change in py-ipykernel that you requested.
> >
> > Cheers.
> > Elias.
> >
> > 2018-08-30 14:39 GMT-03:00 Elias M. Mariani <marianielias@gmail.com>:
> > > 2018-08-30 6:09 GMT-03:00 Edd Barrett <edd@theunixzoo.co.uk>:
> > >> Hi Elias,
> > >>
> > >> I've installed and ran ipython for Python 2 and 3. Seems to be working.
> > >> I've not tested any QT stuff -- I'll take your word that that works.
> > >>
> > >> On Wed, Aug 29, 2018 at 11:37:35PM -0300, Elias M. Mariani wrote:
> > >>> The self-test returns 1 error, I think that is related to
> > >>> graphics/py-matplotlib.
> > >>> (I added matplotlib to the test depends, it wasn't there before)
> > >>
> > >> And does that make the test pass?
> > > Sorry, maybe I didn't explain this in the right way:
> > > The test was running without grapchis/matplotlib, I added the
> > > dependency to enable the full extent of the tests, before this the
> > > test was skipped, so, this reveals a problem that most likely was
> > > hidden by the lack of the test dependency.
> > > The error was something like: "cannot write mode RGBA as JPEG" or
> > > something of the sort, given by python-PIL, while running matplotlib
> > > invoked by IPython, it doesn't look like a problem from IPython.
> > >
> > >>
> > >>> I disabled the building of the docs, I will send in a later mail
> > >>> devel/ipython-docs with the same content
> > >>
> > >> That's annoying, but I don't object in the interim. It would be nice to
> > >> have the docs back soon after this goes in though.
> > > I will commit that port as soon as this gets committed.
> > >
> > >>
> > >>> Might generate some problem with the Qt version used by some consumer.
> > >>
> > >> Do we have any QT consumers in our tree? I didn't think so.
> > >>
> > >> By the way:
> > >> ---8<---
> > >> +RUN_DEPENDS += devel/ipython${MODPY_FLAVOR}>=4.0.0 \
> > >> + devel/py-jupyter_client${MODPY_FLAVOR} \
> > >> + devel/py-traitlets${MODPY_FLAVOR}>=4.1.0 \
> > >> + www/py-tornado${MODPY_FLAVOR}>=4.0
> > >>
> > >> -RUN_DEPENDS += devel/py-jupyter_client${MODPY_FLAVOR}>=5.0.1 \
> > >> - devel/py-traitlets${MODPY_FLAVOR} \
> > >> - www/py-tornado${MODPY_FLAVOR}
> > >> --->8---
> > >>
> > >> If you move the devel/ipython line you added to the end, then it will be
> > >> easier to see what changed in the diff.
> > > Note taken.
> > >
> > >>
> > >> --
> > >> Best Regards
> > >> Edd Barrett
> > >>
> > >> http://www.theunixzoo.co.uk
>
>
> OK bket@ for both py-ipykernel-4.9.0, and py-ipython-5.3.0.
py-ipykernel, but if is not a problem I would prefer to push this
commit, fix the problem with the dependencies of ipykernel and ipython
and then update each for separate.
Cheers.
Elias.
El lun., 29 oct. 2018 a las 1:18, Björn Ketelaars
(<bjorn.ketelaars@hydroxide.nl>) escribió:
>
> On Thu 06/09/2018 13:17, Elias M. Mariani wrote:
> > You are right, I forgot to attach the diff...
> > Here is the change in py-ipykernel that you requested.
> >
> > Cheers.
> > Elias.
> >
> > 2018-08-30 14:39 GMT-03:00 Elias M. Mariani <marianielias@gmail.com>:
> > > 2018-08-30 6:09 GMT-03:00 Edd Barrett <edd@theunixzoo.co.uk>:
> > >> Hi Elias,
> > >>
> > >> I've installed and ran ipython for Python 2 and 3. Seems to be working.
> > >> I've not tested any QT stuff -- I'll take your word that that works.
> > >>
> > >> On Wed, Aug 29, 2018 at 11:37:35PM -0300, Elias M. Mariani wrote:
> > >>> The self-test returns 1 error, I think that is related to
> > >>> graphics/py-matplotlib.
> > >>> (I added matplotlib to the test depends, it wasn't there before)
> > >>
> > >> And does that make the test pass?
> > > Sorry, maybe I didn't explain this in the right way:
> > > The test was running without grapchis/matplotlib, I added the
> > > dependency to enable the full extent of the tests, before this the
> > > test was skipped, so, this reveals a problem that most likely was
> > > hidden by the lack of the test dependency.
> > > The error was something like: "cannot write mode RGBA as JPEG" or
> > > something of the sort, given by python-PIL, while running matplotlib
> > > invoked by IPython, it doesn't look like a problem from IPython.
> > >
> > >>
> > >>> I disabled the building of the docs, I will send in a later mail
> > >>> devel/ipython-docs with the same content
> > >>
> > >> That's annoying, but I don't object in the interim. It would be nice to
> > >> have the docs back soon after this goes in though.
> > > I will commit that port as soon as this gets committed.
> > >
> > >>
> > >>> Might generate some problem with the Qt version used by some consumer.
> > >>
> > >> Do we have any QT consumers in our tree? I didn't think so.
> > >>
> > >> By the way:
> > >> ---8<---
> > >> +RUN_DEPENDS += devel/ipython${MODPY_FLAVOR}>=4.0.0 \
> > >> + devel/py-jupyter_client${MODPY_FLAVOR} \
> > >> + devel/py-traitlets${MODPY_FLAVOR}>=4.1.0 \
> > >> + www/py-tornado${MODPY_FLAVOR}>=4.0
> > >>
> > >> -RUN_DEPENDS += devel/py-jupyter_client${MODPY_FLAVOR}>=5.0.1 \
> > >> - devel/py-traitlets${MODPY_FLAVOR} \
> > >> - www/py-tornado${MODPY_FLAVOR}
> > >> --->8---
> > >>
> > >> If you move the devel/ipython line you added to the end, then it will be
> > >> easier to see what changed in the diff.
> > > Note taken.
> > >
> > >>
> > >> --
> > >> Best Regards
> > >> Edd Barrett
> > >>
> > >> http://www.theunixzoo.co.uk
>
>
> OK bket@ for both py-ipykernel-4.9.0, and py-ipython-5.3.0.
Re: spamd and google smtp ips
On Tue, 30 Oct 2018 18:54:43 +0000 Chris Narkiewicz wrote:
> Are there any solutions get around this problem? Ideally I'd like
> to just whitelist reputable mail providers ...
Yes Chris, see: http://web.Britvault.Co.UK/products/ungrey-robins/
Cheers,
--
Craig Skinner | http://linkd.in/yGqkv7
> Are there any solutions get around this problem? Ideally I'd like
> to just whitelist reputable mail providers ...
Yes Chris, see: http://web.Britvault.Co.UK/products/ungrey-robins/
Cheers,
--
Craig Skinner | http://linkd.in/yGqkv7
Re: syntax error and doas.conf
Hi
Am 31.10.2018 um 10:52 schrieb Consus:
> Well, that's why we have sudoedit. With doas your are forced to
>
> $ doas cp -p /etc/doas.conf /etc/doas.conf.new
> $ doas vi /etc/doas.conf.new
> $ doas -C /etc/doas.conf.new
> $ doas mv /etc/doas.conf.new /etc/doas.conf
>
yeah and by default there is no sudo package installed or is it (at
least it isnt in the 6.x releases if I remember right)?! Just try a
sudoedit on a fresh install and see if it works. As fas as I understand
the doas approach its there to provide a simple way of archiving things like
sudo /do/this/cmd
because 99% of the time you only need root priv to do something like
that. So some very nice guy, I think is name is Ted, thought "hey lets
simplify it and skip all the heavy stuff that sudo brings along". At
least I imagine he thought something like that :)
regard
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Am 31.10.2018 um 10:52 schrieb Consus:
> Well, that's why we have sudoedit. With doas your are forced to
>
> $ doas cp -p /etc/doas.conf /etc/doas.conf.new
> $ doas vi /etc/doas.conf.new
> $ doas -C /etc/doas.conf.new
> $ doas mv /etc/doas.conf.new /etc/doas.conf
>
yeah and by default there is no sudo package installed or is it (at
least it isnt in the 6.x releases if I remember right)?! Just try a
sudoedit on a fresh install and see if it works. As fas as I understand
the doas approach its there to provide a simple way of archiving things like
sudo /do/this/cmd
because 99% of the time you only need root priv to do something like
that. So some very nice guy, I think is name is Ted, thought "hey lets
simplify it and skip all the heavy stuff that sudo brings along". At
least I imagine he thought something like that :)
regard
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Re: syntax error and doas.conf
On 10:42 Wed 31 Oct, Markus Rosjat wrote:
> Hi all,
>
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf file
> you can easily look you self out from root privilages :(
>
> consider a a case where your root has no pw, you are the guy in the wheel
> group and of course you have only this line
>
> permit persist keepenv :wheel
>
> so far everything is peachy ok we are going to add a new line
>
> permit nopass foo as root cmt /root/scripts/dosomething
>
> and we save it ... ups we did a mistake an like to fix it, no worries we can
> ... or cant we?
>
> doas vi /etc/doas.conf
>
> doas: syntax error at line 15
>
>
> at this point you are a bit screwed because you cant edit the doas.conf you
> cant reboot you only way seems to be a switch off. Ok maybe there other was
> but hey I'm no pro Im a simple user and its a vm so switch it off. Boot in
> single user mode, make a fsck because , mount the patritions, export the
> TERM var so yu get a vi. Well seems we are back in business but no we cant
> edit /etc/doas.conf. Doesnt matter we came so far we simply copy the exmaple
> to /etc and be done with it. At that point 5 to 10 min of your life is
> wasted with silly stuff but you may have learn at least one thing ... read
> again what you just wrote before you save it :)
>
>
> Have a nice day list :) and happy helloween
Well, that's why we have sudoedit. With doas your are forced to
$ doas cp -p /etc/doas.conf /etc/doas.conf.new
$ doas vi /etc/doas.conf.new
$ doas -C /etc/doas.conf.new
$ doas mv /etc/doas.conf.new /etc/doas.conf
> Hi all,
>
> just something I notice while trying out stuff with doas and my python
> scripts. If you do a mistake and have a syntax error in the doas.conf file
> you can easily look you self out from root privilages :(
>
> consider a a case where your root has no pw, you are the guy in the wheel
> group and of course you have only this line
>
> permit persist keepenv :wheel
>
> so far everything is peachy ok we are going to add a new line
>
> permit nopass foo as root cmt /root/scripts/dosomething
>
> and we save it ... ups we did a mistake an like to fix it, no worries we can
> ... or cant we?
>
> doas vi /etc/doas.conf
>
> doas: syntax error at line 15
>
>
> at this point you are a bit screwed because you cant edit the doas.conf you
> cant reboot you only way seems to be a switch off. Ok maybe there other was
> but hey I'm no pro Im a simple user and its a vm so switch it off. Boot in
> single user mode, make a fsck because , mount the patritions, export the
> TERM var so yu get a vi. Well seems we are back in business but no we cant
> edit /etc/doas.conf. Doesnt matter we came so far we simply copy the exmaple
> to /etc and be done with it. At that point 5 to 10 min of your life is
> wasted with silly stuff but you may have learn at least one thing ... read
> again what you just wrote before you save it :)
>
>
> Have a nice day list :) and happy helloween
Well, that's why we have sudoedit. With doas your are forced to
$ doas cp -p /etc/doas.conf /etc/doas.conf.new
$ doas vi /etc/doas.conf.new
$ doas -C /etc/doas.conf.new
$ doas mv /etc/doas.conf.new /etc/doas.conf
Re: Bluetooth Support
Thanks for your help, but this does not work. The Bluetooth keyboard is
not recognized from the system.
As I wrote before, I closed this issue and use an USB-keyboard.
Bluetooth I never liked. :-)
On Tue, Oct 30, 2018 at 07:36:40PM -0400, martin@martinbrandenburg.com wrote:
> > From stu@spacehopper.org Tue Oct 30 19:32:56 2018
> > To: misc@openbsd.org
> > From: Stuart Henderson <stu@spacehopper.org>
> > Subject: Re: Bluetooth Support
> > Date: Tue, 30 Oct 2018 23:24:04 +0000 (UTC)
> >
> > On 2018-10-30, Marco Menne <marco.menne17@gmail.com> wrote:
> > > Hello there,
> > >
> > > I installed OpenBSD 6.4 on an old iMac from 2010 and nearly everything
> > > works fine. The sound is cruel but this is a minor problem.
> > > The Apple has a Bluetooth keyboard and I do not find a way to get it
> > > working. I read in some forum that Bluetooth is not supported in OpenBSD.
> > > Is this true?
> > > I can use an USB-Keyboard, of course, but the Apple keyboard is fine and it
> > > would be a little bit sad, if I had to change to an usb one.
> > >
> > > Greetings, Marco
> > > - - -
> > > Marco Menne
> > > marco.menne17@gmail.com
> > > GnuPG-Public-Key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x96A01AB59F6F7ECF
> > >
> >
> > AIUI the firmware on some Apples does actually present a Bluetooth
> > keyboard as a standard keyboard, but I suspect this one will be too
> > old for this and would need an OS that has its own Bluetooth support.
> >
> >
>
> Way back in 2012, I ran OpenBSD on a 2008 MacBook Pro with a Bluetooth
> keyboard and it presented as USB and worked fine.
>
> I ran it for a while actually before I realized and had to ask myself
> how in the world this even works.
>
> Marco, you can test this easily without installing simply by checking to
> see if you can type at the bootloader prompt.
>
--
Marco Menne
marco.menne17@gmail.com
not recognized from the system.
As I wrote before, I closed this issue and use an USB-keyboard.
Bluetooth I never liked. :-)
On Tue, Oct 30, 2018 at 07:36:40PM -0400, martin@martinbrandenburg.com wrote:
> > From stu@spacehopper.org Tue Oct 30 19:32:56 2018
> > To: misc@openbsd.org
> > From: Stuart Henderson <stu@spacehopper.org>
> > Subject: Re: Bluetooth Support
> > Date: Tue, 30 Oct 2018 23:24:04 +0000 (UTC)
> >
> > On 2018-10-30, Marco Menne <marco.menne17@gmail.com> wrote:
> > > Hello there,
> > >
> > > I installed OpenBSD 6.4 on an old iMac from 2010 and nearly everything
> > > works fine. The sound is cruel but this is a minor problem.
> > > The Apple has a Bluetooth keyboard and I do not find a way to get it
> > > working. I read in some forum that Bluetooth is not supported in OpenBSD.
> > > Is this true?
> > > I can use an USB-Keyboard, of course, but the Apple keyboard is fine and it
> > > would be a little bit sad, if I had to change to an usb one.
> > >
> > > Greetings, Marco
> > > - - -
> > > Marco Menne
> > > marco.menne17@gmail.com
> > > GnuPG-Public-Key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x96A01AB59F6F7ECF
> > >
> >
> > AIUI the firmware on some Apples does actually present a Bluetooth
> > keyboard as a standard keyboard, but I suspect this one will be too
> > old for this and would need an OS that has its own Bluetooth support.
> >
> >
>
> Way back in 2012, I ran OpenBSD on a 2008 MacBook Pro with a Bluetooth
> keyboard and it presented as USB and worked fine.
>
> I ran it for a while actually before I realized and had to ask myself
> how in the world this even works.
>
> Marco, you can test this easily without installing simply by checking to
> see if you can type at the bootloader prompt.
>
--
Marco Menne
marco.menne17@gmail.com
syntax error and doas.conf
Hi all,
just something I notice while trying out stuff with doas and my python
scripts. If you do a mistake and have a syntax error in the doas.conf
file you can easily look you self out from root privilages :(
consider a a case where your root has no pw, you are the guy in the
wheel group and of course you have only this line
permit persist keepenv :wheel
so far everything is peachy ok we are going to add a new line
permit nopass foo as root cmt /root/scripts/dosomething
and we save it ... ups we did a mistake an like to fix it, no worries we
can ... or cant we?
doas vi /etc/doas.conf
doas: syntax error at line 15
at this point you are a bit screwed because you cant edit the doas.conf
you cant reboot you only way seems to be a switch off. Ok maybe there
other was but hey I'm no pro Im a simple user and its a vm so switch it
off. Boot in single user mode, make a fsck because , mount the
patritions, export the TERM var so yu get a vi. Well seems we are back
in business but no we cant edit /etc/doas.conf. Doesnt matter we came so
far we simply copy the exmaple to /etc and be done with it. At that
point 5 to 10 min of your life is wasted with silly stuff but you may
have learn at least one thing ... read again what you just wrote before
you save it :)
Have a nice day list :) and happy helloween
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
just something I notice while trying out stuff with doas and my python
scripts. If you do a mistake and have a syntax error in the doas.conf
file you can easily look you self out from root privilages :(
consider a a case where your root has no pw, you are the guy in the
wheel group and of course you have only this line
permit persist keepenv :wheel
so far everything is peachy ok we are going to add a new line
permit nopass foo as root cmt /root/scripts/dosomething
and we save it ... ups we did a mistake an like to fix it, no worries we
can ... or cant we?
doas vi /etc/doas.conf
doas: syntax error at line 15
at this point you are a bit screwed because you cant edit the doas.conf
you cant reboot you only way seems to be a switch off. Ok maybe there
other was but hey I'm no pro Im a simple user and its a vm so switch it
off. Boot in single user mode, make a fsck because , mount the
patritions, export the TERM var so yu get a vi. Well seems we are back
in business but no we cant edit /etc/doas.conf. Doesnt matter we came so
far we simply copy the exmaple to /etc and be done with it. At that
point 5 to 10 min of your life is wasted with silly stuff but you may
have learn at least one thing ... read again what you just wrote before
you save it :)
Have a nice day list :) and happy helloween
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Re: fix HOMEPAGE on security/libfprint
Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> On Wed, Oct 31, 2018 at 10:01:05AM +0100, Solene Rapenne wrote:
> > Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > > >
> > > > there is a "a" in HOMEPAGE, and use https now
> > >
> > > Needs a bump.
> > >
> >
> > new diff with REVISION bump + CC maintainer
>
> REVISION starts at 0.
should be good now...
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 09:39:45 -0000
@@ -3,12 +3,13 @@
COMMENT= library for fingerprint reader devices
DISTNAME= libfprint-0.6.0
+REVISION= 0
CATEGORIES= security
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
> On Wed, Oct 31, 2018 at 10:01:05AM +0100, Solene Rapenne wrote:
> > Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > > >
> > > > there is a "a" in HOMEPAGE, and use https now
> > >
> > > Needs a bump.
> > >
> >
> > new diff with REVISION bump + CC maintainer
>
> REVISION starts at 0.
should be good now...
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 09:39:45 -0000
@@ -3,12 +3,13 @@
COMMENT= library for fingerprint reader devices
DISTNAME= libfprint-0.6.0
+REVISION= 0
CATEGORIES= security
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
Re: migrate python script from sudo to doas
Hi Vincent
Am 30.10.2018 um 16:03 schrieb Vincent Legoll:
> Maybe you should try like the following:
>
> cmd = ['doas', 'useradd',
> '-u', user_id,
> '-g', '=uid',
> '-s', '/sbin/nologin',
> '-d', mb_parent_dir,
> user_name]
> exit = subprocess.check_call(cmd)
>
this doesn't solve the problem, if I try like that check_call complains
that it need a string as user_id. If I do make something like
u_id = '%s' %user_id and plug u_id as the arg I'm back to square one. So
it seems this seems a doas related issue and needs some adjustment in
doas.conf. If this isnt resolvable I will just install sudo package
using the "pointing a cannon at a sparrow" approach :(
regards
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Am 30.10.2018 um 16:03 schrieb Vincent Legoll:
> Maybe you should try like the following:
>
> cmd = ['doas', 'useradd',
> '-u', user_id,
> '-g', '=uid',
> '-s', '/sbin/nologin',
> '-d', mb_parent_dir,
> user_name]
> exit = subprocess.check_call(cmd)
>
this doesn't solve the problem, if I try like that check_call complains
that it need a string as user_id. If I do make something like
u_id = '%s' %user_id and plug u_id as the arg I'm back to square one. So
it seems this seems a doas related issue and needs some adjustment in
doas.conf. If this isnt resolvable I will just install sudo package
using the "pointing a cannon at a sparrow" approach :(
regards
--
Markus Rosjat fon: +49 351 8107224 mail: rosjat@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Re: fix HOMEPAGE on security/libfprint
On Wed, Oct 31, 2018 at 10:01:05AM +0100, Solene Rapenne wrote:
> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > >
> > > there is a "a" in HOMEPAGE, and use https now
> >
> > Needs a bump.
> >
>
> new diff with REVISION bump + CC maintainer
REVISION starts at 0.
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 08:50:18 -0000
> @@ -6,9 +6,11 @@ DISTNAME= libfprint-0.6.0
>
> CATEGORIES= security
>
> +REVISION= 1
> +
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> > On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> > >
> > > there is a "a" in HOMEPAGE, and use https now
> >
> > Needs a bump.
> >
>
> new diff with REVISION bump + CC maintainer
REVISION starts at 0.
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 08:50:18 -0000
> @@ -6,9 +6,11 @@ DISTNAME= libfprint-0.6.0
>
> CATEGORIES= security
>
> +REVISION= 1
> +
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
Re: fix HOMEPAGE on security/libfprint
Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
> On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> >
> > there is a "a" in HOMEPAGE, and use https now
>
> Needs a bump.
>
new diff with REVISION bump + CC maintainer
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 08:50:18 -0000
@@ -6,9 +6,11 @@ DISTNAME= libfprint-0.6.0
CATEGORIES= security
+REVISION= 1
+
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
> On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
> >
> > there is a "a" in HOMEPAGE, and use https now
>
> Needs a bump.
>
new diff with REVISION bump + CC maintainer
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 08:50:18 -0000
@@ -6,9 +6,11 @@ DISTNAME= libfprint-0.6.0
CATEGORIES= security
+REVISION= 1
+
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= http://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
Re: fix HOMEPAGE on security/libfprint
On Wed, Oct 31, 2018 at 09:46:55AM +0100, Solene Rapenne wrote:
>
> there is a "a" in HOMEPAGE, and use https now
Needs a bump.
>
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 08:45:47 -0000
> @@ -8,7 +8,7 @@ CATEGORIES= security
>
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= https://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
>
> there is a "a" in HOMEPAGE, and use https now
Needs a bump.
>
> Index: Makefile
> ===================================================================
> RCS file: /data/cvs/ports/security/libfprint/Makefile,v
> retrieving revision 1.29
> diff -u -p -r1.29 Makefile
> --- Makefile 26 Apr 2018 16:01:45 -0000 1.29
> +++ Makefile 31 Oct 2018 08:45:47 -0000
> @@ -8,7 +8,7 @@ CATEGORIES= security
>
> SHARED_LIBS += fprint 1.1 # 0.0
>
> -HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
> +HOMEPAGE= https://www.freedesktop.org/wiki/Software/fprint/libfprint
> MASTER_SITES= http://people.freedesktop.org/~hadess/
> EXTRACT_SUFX= .tar.xz
>
>
--
Antoine
fix HOMEPAGE on security/libfprint
there is a "a" in HOMEPAGE, and use https now
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 08:45:47 -0000
@@ -8,7 +8,7 @@ CATEGORIES= security
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= https://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
Index: Makefile
===================================================================
RCS file: /data/cvs/ports/security/libfprint/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile 26 Apr 2018 16:01:45 -0000 1.29
+++ Makefile 31 Oct 2018 08:45:47 -0000
@@ -8,7 +8,7 @@ CATEGORIES= security
SHARED_LIBS += fprint 1.1 # 0.0
-HOMEPAGE=a http://www.freedesktop.org/wiki/Software/fprint/libfprint
+HOMEPAGE= https://www.freedesktop.org/wiki/Software/fprint/libfprint
MASTER_SITES= http://people.freedesktop.org/~hadess/
EXTRACT_SUFX= .tar.xz
games/ezquake and games/quakespasm broken on powerpc
Hi,
both games/ezquake and games/quakespasm won't even start. I think we should
mark them broken, but I have no idea what the issue is...
Below is a backtrace of ezquake crash and quakespasm crash log (I did not find
a .core file)
games/ezquake
-------------
Reading symbols from ezquake...(no debugging symbols found)...done.
[New process 545505]
warning: Unexpected size of section `.reg/545505' in core file.
Core was generated by `ezquake'.
Program terminated with signal SIGABRT, Aborted.
warning: Unexpected size of section `.reg/545505' in core file.
#0 0xb56d83b4 in thrkill () at {standard input}:5
5 {standard input}: No such file or directory.
(gdb) bt
#0 0xb56d83b4 in thrkill () at {standard input}:5
#1 0xb567523c in *_libc___stack_smash_handler (func=0xe38f5424 "X11_InitKeyboard", damaged=<optimized out>) at /usr/src/lib/libc/sys/stack_protector.c:79
#2 0xe38a7ae0 in X11_InitKeyboard () from /usr/local/lib/libSDL2.so.0.5
#3 0xe38af1e8 in X11_VideoInit () from /usr/local/lib/libSDL2.so.0.5
#4 0xe3896034 in SDL_VideoInit_REAL () from /usr/local/lib/libSDL2.so.0.5
#5 0xe37e9a40 in SDL_InitSubSystem_REAL () from /usr/local/lib/libSDL2.so.0.5
#6 0xe37f546c in SDL_InitSubSystem () from /usr/local/lib/libSDL2.so.0.5
#7 0x30a02424 in ?? ()
#8 0x3091f2b0 in ?? ()
#9 0x308ccb5c in ?? ()
#10 0x30a4c998 in ?? ()
#11 0x308b0264 in ?? ()
#12 0x00000000 in ?? ()
gamez/quakespasm
----------------
Command line: /usr/local/libexec/quakespasm -basedir /home/solene/quake
Found SDL version 2.0.8
Detected 1 CPUs.
Quake 1.09 (c) id Software
GLQuake 1.00 (c) id Software
FitzQuake 0.85 (c) John Fitzgibbons
FitzQuake SDL port (c) SleepwalkR, Baker
QuakeSpasm 0.93.1 (c) Ozkan Sezer, Eric Wasylishen & others
Host_Init
Playing registered version.
Console initialized.
UDP_Init: gethostbyname failed (Unknown host)
UDP Initialized
Server using protocol 666 (FitzQuake)
Exe: 13:51:42 Oct 29 2018
256.0 megabyte heap
zsh: abort quakespasm -basedir $PWD
both games/ezquake and games/quakespasm won't even start. I think we should
mark them broken, but I have no idea what the issue is...
Below is a backtrace of ezquake crash and quakespasm crash log (I did not find
a .core file)
games/ezquake
-------------
Reading symbols from ezquake...(no debugging symbols found)...done.
[New process 545505]
warning: Unexpected size of section `.reg/545505' in core file.
Core was generated by `ezquake'.
Program terminated with signal SIGABRT, Aborted.
warning: Unexpected size of section `.reg/545505' in core file.
#0 0xb56d83b4 in thrkill () at {standard input}:5
5 {standard input}: No such file or directory.
(gdb) bt
#0 0xb56d83b4 in thrkill () at {standard input}:5
#1 0xb567523c in *_libc___stack_smash_handler (func=0xe38f5424 "X11_InitKeyboard", damaged=<optimized out>) at /usr/src/lib/libc/sys/stack_protector.c:79
#2 0xe38a7ae0 in X11_InitKeyboard () from /usr/local/lib/libSDL2.so.0.5
#3 0xe38af1e8 in X11_VideoInit () from /usr/local/lib/libSDL2.so.0.5
#4 0xe3896034 in SDL_VideoInit_REAL () from /usr/local/lib/libSDL2.so.0.5
#5 0xe37e9a40 in SDL_InitSubSystem_REAL () from /usr/local/lib/libSDL2.so.0.5
#6 0xe37f546c in SDL_InitSubSystem () from /usr/local/lib/libSDL2.so.0.5
#7 0x30a02424 in ?? ()
#8 0x3091f2b0 in ?? ()
#9 0x308ccb5c in ?? ()
#10 0x30a4c998 in ?? ()
#11 0x308b0264 in ?? ()
#12 0x00000000 in ?? ()
gamez/quakespasm
----------------
Command line: /usr/local/libexec/quakespasm -basedir /home/solene/quake
Found SDL version 2.0.8
Detected 1 CPUs.
Quake 1.09 (c) id Software
GLQuake 1.00 (c) id Software
FitzQuake 0.85 (c) John Fitzgibbons
FitzQuake SDL port (c) SleepwalkR, Baker
QuakeSpasm 0.93.1 (c) Ozkan Sezer, Eric Wasylishen & others
Host_Init
Playing registered version.
Console initialized.
UDP_Init: gethostbyname failed (Unknown host)
UDP Initialized
Server using protocol 666 (FitzQuake)
Exe: 13:51:42 Oct 29 2018
256.0 megabyte heap
zsh: abort quakespasm -basedir $PWD
Tuesday, October 30, 2018
powerpc bulk build report
bulk build on macppc-1.ports.openbsd.org
started on Fri Oct 12 09:46:26 MDT 2018
finished at Tue Oct 30 18:15:58 MDT 2018
lasted 19D01h29m
done with kern.version=OpenBSD 6.4 (GENERIC) #231: Thu Oct 11 17:55:03 MDT 2018
built packages:8834
Oct 12:589
Oct 13:418
Oct 14:467
Oct 15:701
Oct 16:492
Oct 17:335
Oct 18:232
Oct 19:339
Oct 20:276
Oct 21:536
Oct 22:342
Oct 23:335
Oct 24:391
Oct 25:454
Oct 26:126
Oct 27:181
Oct 28:132
Oct 29:1059
Oct 30:1428
critical path missing pkgs: http://build-failures.rhaalovely.net//powerpc/2018-10-12/summary.log
build failures: 61
http://build-failures.rhaalovely.net//powerpc/2018-10-12/audio/siren.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/benchmarks/wrk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/cad/yosys.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/converters/p5-Convert-TNEF.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/avr/gcc.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/catch2.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/ocaml-graph.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/splint.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/unibilium.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/vte3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/xtensa-elf/gcc.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/editors/scintilla.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/emulators/higan.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/emulators/stella.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/easyrpg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/freeorion.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/gnubg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/openclonk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/prboom-plus.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/stockfish.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/geo/merkaartor.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/geo/qlandkartegt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/aqsis.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/asymptote.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/orthanc/webviewer-plugin.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/inputmethods/fcitx,-gtk3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/lang/bacon.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/lang/racket-minimal,no_jit.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/mail/rspamd.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/mail/solid-pop3d.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/kst.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/octave.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/z3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/multimedia/libvpx.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/multimedia/swfmill.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/fastnetmon.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/megatools.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/p5-Net-SSH-Perl.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/zeromq.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/print/ghostscript/gnu,a4,no_x11.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/sysutils/bacula,-bat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/sysutils/libolecf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/textproc/mupdf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/libsass.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/ruby-capybara-webkit,ruby24.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/webkitgtk4.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/gnome/gjs.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/gnome/usage.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/compton-conf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libfm-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libqtxdg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libsysstat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/obconf-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/pavucontrol-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/qtermwidget.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtgraphicaleffects.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtquickcontrols.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtquickcontrols2.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/spice-gtk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xfce4/xfce4-whiskermenu.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xscreensaver.log
recurrent failures
failures/benchmarks/wrk.log
failures/cad/yosys.log
failures/devel/avr/gcc.log
failures/devel/catch2.log
failures/devel/vte3.log
failures/devel/xtensa-elf/gcc.log
failures/emulators/higan.log
failures/emulators/stella.log
failures/games/easyrpg.log
failures/games/openclonk.log
failures/games/prboom-plus.log
failures/games/stockfish.log
failures/geo/merkaartor.log
failures/geo/qlandkartegt.log
failures/graphics/orthanc/webviewer-plugin.log
failures/inputmethods/fcitx,-gtk3.log
failures/lang/bacon.log
failures/lang/racket-minimal,no_jit.log
failures/mail/rspamd.log
failures/math/kst.log
failures/math/z3.log
failures/multimedia/swfmill.log
failures/net/fastnetmon.log
failures/net/megatools.log
failures/net/p5-Net-SSH-Perl.log
failures/net/zeromq.log
failures/textproc/mupdf.log
failures/www/libsass.log
failures/www/webkitgtk4.log
failures/x11/gnome/gjs.log
failures/x11/lxqt/compton-conf.log
failures/x11/lxqt/libqtxdg.log
failures/x11/lxqt/pavucontrol-qt.log
failures/x11/qt5/qtquickcontrols.log
failures/x11/qt5/qtquickcontrols2.log
failures/x11/spice-gtk.log
failures/x11/xscreensaver.log
new failures
+++ ls-failures Tue Oct 30 23:45:07 2018
+failures/audio/siren.log
+failures/converters/p5-Convert-TNEF.log
+failures/devel/ocaml-graph.log
+failures/devel/splint.log
+failures/devel/unibilium.log
+failures/editors/scintilla.log
+failures/games/freeorion.log
+failures/games/gnubg.log
+failures/graphics/aqsis.log
+failures/graphics/asymptote.log
+failures/mail/solid-pop3d.log
+failures/math/octave.log
+failures/multimedia/libvpx.log
+failures/print/ghostscript/gnu,a4,no_x11.log
+failures/sysutils/bacula,-bat.log
+failures/sysutils/libolecf.log
+failures/www/ruby-capybara-webkit,ruby24.log
+failures/x11/gnome/usage.log
+failures/x11/lxqt/libfm-qt.log
+failures/x11/lxqt/libsysstat.log
+failures/x11/lxqt/obconf-qt.log
+failures/x11/lxqt/qtermwidget.log
+failures/x11/qt5/qtgraphicaleffects.log
+failures/x11/xfce4/xfce4-whiskermenu.log
+failures/summary.log
resolved failures
--- ../old/powerpc/last//ls-failures Fri Oct 12 00:26:40 2018
-failures/audio/gimmix.log
-failures/cad/gtkwave.log
-failures/databases/sqlports,-compact.log
-failures/devel/geany.log
-failures/devel/libvmime.log
-failures/devel/protozero.log
-failures/editors/neovim.log
-failures/emulators/ppsspp.log
-failures/emulators/retroarch.log
-failures/games/godot.log
-failures/geo/libpostal.log
-failures/graphics/openscenegraph.log
-failures/multimedia/mlt.log
-failures/net/toxcore.log
-failures/print/texlive/base.log
-failures/security/hashdeep.log
-failures/www/ruby-capybara-webkit,ruby25.log
-failures/x11/kde4/marble.log
started on Fri Oct 12 09:46:26 MDT 2018
finished at Tue Oct 30 18:15:58 MDT 2018
lasted 19D01h29m
done with kern.version=OpenBSD 6.4 (GENERIC) #231: Thu Oct 11 17:55:03 MDT 2018
built packages:8834
Oct 12:589
Oct 13:418
Oct 14:467
Oct 15:701
Oct 16:492
Oct 17:335
Oct 18:232
Oct 19:339
Oct 20:276
Oct 21:536
Oct 22:342
Oct 23:335
Oct 24:391
Oct 25:454
Oct 26:126
Oct 27:181
Oct 28:132
Oct 29:1059
Oct 30:1428
critical path missing pkgs: http://build-failures.rhaalovely.net//powerpc/2018-10-12/summary.log
build failures: 61
http://build-failures.rhaalovely.net//powerpc/2018-10-12/audio/siren.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/benchmarks/wrk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/cad/yosys.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/converters/p5-Convert-TNEF.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/avr/gcc.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/catch2.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/ocaml-graph.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/splint.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/unibilium.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/vte3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/devel/xtensa-elf/gcc.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/editors/scintilla.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/emulators/higan.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/emulators/stella.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/easyrpg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/freeorion.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/gnubg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/openclonk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/prboom-plus.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/games/stockfish.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/geo/merkaartor.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/geo/qlandkartegt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/aqsis.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/asymptote.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/graphics/orthanc/webviewer-plugin.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/inputmethods/fcitx,-gtk3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/lang/bacon.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/lang/racket-minimal,no_jit.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/mail/rspamd.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/mail/solid-pop3d.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/kst.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/octave.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/math/z3.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/multimedia/libvpx.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/multimedia/swfmill.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/fastnetmon.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/megatools.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/p5-Net-SSH-Perl.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/net/zeromq.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/print/ghostscript/gnu,a4,no_x11.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/sysutils/bacula,-bat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/sysutils/libolecf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/textproc/mupdf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/libsass.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/ruby-capybara-webkit,ruby24.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/www/webkitgtk4.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/gnome/gjs.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/gnome/usage.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/compton-conf.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libfm-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libqtxdg.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/libsysstat.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/obconf-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/pavucontrol-qt.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/lxqt/qtermwidget.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtgraphicaleffects.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtquickcontrols.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/qt5/qtquickcontrols2.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/spice-gtk.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xfce4/xfce4-whiskermenu.log
http://build-failures.rhaalovely.net//powerpc/2018-10-12/x11/xscreensaver.log
recurrent failures
failures/benchmarks/wrk.log
failures/cad/yosys.log
failures/devel/avr/gcc.log
failures/devel/catch2.log
failures/devel/vte3.log
failures/devel/xtensa-elf/gcc.log
failures/emulators/higan.log
failures/emulators/stella.log
failures/games/easyrpg.log
failures/games/openclonk.log
failures/games/prboom-plus.log
failures/games/stockfish.log
failures/geo/merkaartor.log
failures/geo/qlandkartegt.log
failures/graphics/orthanc/webviewer-plugin.log
failures/inputmethods/fcitx,-gtk3.log
failures/lang/bacon.log
failures/lang/racket-minimal,no_jit.log
failures/mail/rspamd.log
failures/math/kst.log
failures/math/z3.log
failures/multimedia/swfmill.log
failures/net/fastnetmon.log
failures/net/megatools.log
failures/net/p5-Net-SSH-Perl.log
failures/net/zeromq.log
failures/textproc/mupdf.log
failures/www/libsass.log
failures/www/webkitgtk4.log
failures/x11/gnome/gjs.log
failures/x11/lxqt/compton-conf.log
failures/x11/lxqt/libqtxdg.log
failures/x11/lxqt/pavucontrol-qt.log
failures/x11/qt5/qtquickcontrols.log
failures/x11/qt5/qtquickcontrols2.log
failures/x11/spice-gtk.log
failures/x11/xscreensaver.log
new failures
+++ ls-failures Tue Oct 30 23:45:07 2018
+failures/audio/siren.log
+failures/converters/p5-Convert-TNEF.log
+failures/devel/ocaml-graph.log
+failures/devel/splint.log
+failures/devel/unibilium.log
+failures/editors/scintilla.log
+failures/games/freeorion.log
+failures/games/gnubg.log
+failures/graphics/aqsis.log
+failures/graphics/asymptote.log
+failures/mail/solid-pop3d.log
+failures/math/octave.log
+failures/multimedia/libvpx.log
+failures/print/ghostscript/gnu,a4,no_x11.log
+failures/sysutils/bacula,-bat.log
+failures/sysutils/libolecf.log
+failures/www/ruby-capybara-webkit,ruby24.log
+failures/x11/gnome/usage.log
+failures/x11/lxqt/libfm-qt.log
+failures/x11/lxqt/libsysstat.log
+failures/x11/lxqt/obconf-qt.log
+failures/x11/lxqt/qtermwidget.log
+failures/x11/qt5/qtgraphicaleffects.log
+failures/x11/xfce4/xfce4-whiskermenu.log
+failures/summary.log
resolved failures
--- ../old/powerpc/last//ls-failures Fri Oct 12 00:26:40 2018
-failures/audio/gimmix.log
-failures/cad/gtkwave.log
-failures/databases/sqlports,-compact.log
-failures/devel/geany.log
-failures/devel/libvmime.log
-failures/devel/protozero.log
-failures/editors/neovim.log
-failures/emulators/ppsspp.log
-failures/emulators/retroarch.log
-failures/games/godot.log
-failures/geo/libpostal.log
-failures/graphics/openscenegraph.log
-failures/multimedia/mlt.log
-failures/net/toxcore.log
-failures/print/texlive/base.log
-failures/security/hashdeep.log
-failures/www/ruby-capybara-webkit,ruby25.log
-failures/x11/kde4/marble.log
Subscribe to:
Posts (Atom)