Re: Repeat e-mail syndrome shows up in 2.2.26+
On Mon, Nov 07, 2016 at 01:33:00PM -0700, The Doctor wrote: > On Fri, Nov 04, 2016 at 11:29:16AM -0600, The Doctor wrote: > > On Wed, Nov 02, 2016 at 07:15:17PM +0200, Timo Sirainen wrote: > > > On 01 Nov 2016, at 18:26, The Doctor wrote: > > > > > > > > Getting complaints from people about pop/imap > > > > > > > > issues. > > > > > > > > some people are getting repaeted e-mail. > > > > > > > > Other are not able to delete their e-mails from an IMAP lcient. > > > > > > Anything in error logs? POP3 duplicates sound like IMAP UIDs were changed > > > (or are still changing?) > > > > Tat is what I see in the log. > > > > I did send a huge attachment. > > > > Dovecot was adding the UID by 1 for some odd reason. > > > > Can you track down why this is occuring? > > > > And even IMAP folder cannot update. > > > > I right have to revert to 2.2.25 for now until these issues > > are addressed. > > > > Reverting will not work. > > I have clients turning into dragons over this issue. > > Any fix on the horizon? > doing some research, I did use Thunderbird in this case with IMAP Mail. In my own account I used roundcube mail delete unhidden trash and seems to have solved my problem. In another account, I see lots of white items in RoundCude as if these items are hidden from Thunderbird hance blocking the IMAP Client from deleting e-mails. Has anyone ran into this before? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Solved] lang/perl5.24 upgrade breaks munin-graph in sysutils/munin-master
Hi! > GregOn Sunday, November 06, 2016 16:49:18 wrote: > > After upgrading to perl 5.24, munin-graph now exits thusly: > > > > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $dom in > > concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, > > line 1. [...] > I was mistaken as to the cause of the problem I was seeing. Munin > apparently grew a new dependency on CGI::Fast. Installing www/p5-CGI-Fast > fixed the problem. Sorry for the false alarm. Should www/p5-CGI-Fast > be added to Munin's run time dependency list? Yes. Can you submit a PR ? -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
PR Commit Request.
Hello, Can someone please commit this (it's been waiting a while and is only a simple "sed" change in the Makefile). If there's anything else I need to do, let me know. Thanks! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210138 Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
[Solved] lang/perl5.24 upgrade breaks munin-graph in sysutils/munin-master
GregOn Sunday, November 06, 2016 16:49:18 wrote: > After upgrading to perl 5.24, munin-graph now exits thusly: > > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $dom in > concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, > line 1. > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $host in > concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, > line 1. > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $serv in > concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, > line 1. > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $scale in > concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, > line 1. > 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $scale in > pattern match (m//) at /usr/local/share/munin/munin-graph line 133, > line 1. > 2016/11/06 16:40:42 [WARNING] Request for graph without specifying domain. > Bailing out. > 2016/11/06 16:40:42 Invalid parameters! > > and no charts are produced. > I was mistaken as to the cause of the problem I was seeing. Munin apparently grew a new dependency on CGI::Fast. Installing www/p5-CGI-Fast fixed the problem. Sorry for the false alarm. Should www/p5-CGI-Fast be added to Munin's run time dependency list? -- Greg ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Resurrecting games/wmfortune (Was: Re: misc/jive deleted)
> Julian H. Stacey wrote: > > > FYI in case newer than yours, Fonz, I have > > MD5 (9.2-RELEASE/wmfortune-0.241.tar.gz) =3D fa8db5d9a46d9afe7757f498c7= > 81e8c9 > > SHA256 (9.2-RELEASE/wmfortune-0.241.tar.gz) =3D b149067b7e3521f7e03354b= > 12754baaf9c5556af4d286bbd6d169b1db9f6dba0 > >=20 > > It builds & run on my 9.2, I've not tried on current. > > That matches what I've got and appears to be the most recent, thanks. > > Considering the overly aggressive pruning of the ports tree that the > Powers That Be have been conveying (but what to me rather more seems like > attempting to perform intricate neurosurgery using a sledgehammer and a > chainsaw), it's unlikely that a port which is no longer maintained > upstream will be welcomed back into the tree, even though people are > willing to maintain the port and host the distfiles. There probably needs > to be some sort of alternative--or "underground" if you like--tree that > can serve those ports that are not to the liking of a select few (and/or > that have been taken away from the tolerant in order to appease the > intolerant, such as in the misc/jive case). Agreed. I will also contribute deleted working ports. > I'm currently looking into > what's the best way to go about setting up such a supplementary tree. To prevent ports deleters further disruption, I created http://mailman.berklix.org/mailman/listinfo/freebsd-ports & cc'd "FreeBSD Ports Resuscitation" I can offer a FreeBSD server, space for freebsd.org + supplmentary SVN trees, + ftp & http (as used for http://ctm.berklix.org ) . Initially non SVN'd last working copies would be something. We'd next want SVN to maintain it. SVN is already installed on server, I would need to add http support for SVN (suggestions welcome). Hopefully others would volunteer for SVN admin & port meta data recovery. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
simple PRs with maintainer patches for commits
Could these 2 PRs get a committer please? I'm the maintainer for both. No upstream changes, just ports-related improvements. www/h2o: - support integrated mruby & clean up option handling - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213733 net-mgmt/riemann: - fix reload under daemon(8) using pkill - use new upstream master site - add conf.d for more complex configurations - add named daemon(8) process info - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212671 A+ Dave ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clang support for compiler:openmp
On Mon, Nov 07, 2016 at 10:12:59PM +0100, Matthieu Volat wrote: > On Mon, 7 Nov 2016 16:59:36 + > Brooks Davis wrote: > > > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > > Hi, > > > > > > is there a specific reason, why we do not (yet) have openmp support for > > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > > expect compiler:openmp to set > > > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > > per-port level. > > > > I talked with Baptiste about this in Belgrade. I think the best way > > forward would be to remove the OPENMP option from the llvm ports and > > alter the clang-patch-fopenmp.diff patch to use the .so from > > devel/openmp. > > > > I have a major deadline at the end of the week so it definitely won't > > happen this week. > > > > Would not that make that every clang use the llvm 3.8 libomp snapshot? It > might be useful to use later versions in some cases, but anyway, that would > be great! It would mean sticking to a single version, but I'd be pretty surprised if mixing them ended well so that's probably for the best. > It would also be awesome if base clang would be able to find omp.h and libomp > more "out of the box" once the package is installed... libomp is pretty easy once I realized I needed to hardcode the path to the .so, I'll have to see what's involved for omp.h. -- Brooks signature.asc Description: PGP signature
Re: clang support for compiler:openmp
On Mon, 7 Nov 2016 18:59:26 -0300 "Nilton Jose Rizzo" wrote: > Em Mon, 7 Nov 2016 22:12:59 +0100, Matthieu Volat escreveu > > On Mon, 7 Nov 2016 16:59:36 + > > Brooks Davis wrote: > > [...] > > I have one question about a llvm and clang ports. it's possible > port the llvm 3.9 and clang 4.0.0 with cuda support? > > I don't think we'll see that anytime soon: even if there are now some compilers that produce cuda PTX bytecode, you neeed userland and kernel code to actually compile it to native GPU code/push it/do data transfert, and only the nvidia official driver do that for now. There's some of that in the linux compatibility part of the nvidia driver, and some people managed to use it in the past, but right now, I'm not so sure. -- Mazhe pgpvVxoF50Yx7.pgp Description: OpenPGP digital signature
Re: clang support for compiler:openmp
Em Mon, 7 Nov 2016 22:12:59 +0100, Matthieu Volat escreveu > On Mon, 7 Nov 2016 16:59:36 + > Brooks Davis wrote: > > > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > > Hi, > > > > > > is there a specific reason, why we do not (yet) have openmp support for > > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > > expect compiler:openmp to set > > > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > > per-port level. > > > > I talked with Baptiste about this in Belgrade. I think the best way > > forward would be to remove the OPENMP option from the llvm ports and > > alter the clang-patch-fopenmp.diff patch to use the .so from > > devel/openmp. > > > > I have a major deadline at the end of the week so it definitely won't > > happen this week. > > > > Would not that make that every clang use the llvm 3.8 libomp > snapshot? It might be useful to use later versions in some cases, > but anyway, that would be great! > > It would also be awesome if base clang would be able to find omp.h > and libomp more "out of the box" once the package is installed... > > -- Mazhe I have one question about a llvm and clang ports. it's possible port the llvm 3.9 and clang 4.0.0 with cuda support? --- /* **Nilton José RizzoUFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clang support for compiler:openmp
On Mon, 7 Nov 2016 16:59:36 + Brooks Davis wrote: > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > Hi, > > > > is there a specific reason, why we do not (yet) have openmp support for > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > expect compiler:openmp to set > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > per-port level. > > I talked with Baptiste about this in Belgrade. I think the best way > forward would be to remove the OPENMP option from the llvm ports and > alter the clang-patch-fopenmp.diff patch to use the .so from > devel/openmp. > > I have a major deadline at the end of the week so it definitely won't > happen this week. > Would not that make that every clang use the llvm 3.8 libomp snapshot? It might be useful to use later versions in some cases, but anyway, that would be great! It would also be awesome if base clang would be able to find omp.h and libomp more "out of the box" once the package is installed... -- Mazhe pgpl3cmFmrGvS.pgp Description: OpenPGP digital signature
Re: Repeat e-mail syndrome shows up in 2.2.26+
On Fri, Nov 04, 2016 at 11:29:16AM -0600, The Doctor wrote: > On Wed, Nov 02, 2016 at 07:15:17PM +0200, Timo Sirainen wrote: > > On 01 Nov 2016, at 18:26, The Doctor wrote: > > > > > > Getting complaints from people about pop/imap > > > > > > issues. > > > > > > some people are getting repaeted e-mail. > > > > > > Other are not able to delete their e-mails from an IMAP lcient. > > > > Anything in error logs? POP3 duplicates sound like IMAP UIDs were changed > > (or are still changing?) > > Tat is what I see in the log. > > I did send a huge attachment. > > Dovecot was adding the UID by 1 for some odd reason. > > Can you track down why this is occuring? > > And even IMAP folder cannot update. > > I right have to revert to 2.2.25 for now until these issues > are addressed. > Reverting will not work. I have clients turning into dragons over this issue. Any fix on the horizon? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clang support for compiler:openmp
On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > Hi, > > is there a specific reason, why we do not (yet) have openmp support for > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > expect compiler:openmp to set > > LIB_DEPENDS+= libomp.so:devel/openmp > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > per-port level. I talked with Baptiste about this in Belgrade. I think the best way forward would be to remove the OPENMP option from the llvm ports and alter the clang-patch-fopenmp.diff patch to use the .so from devel/openmp. I have a major deadline at the end of the week so it definitely won't happen this week. -- Brooks signature.asc Description: PGP signature
Demandas Laborales - Acciones Preventivas
En línea y en Vivo / Para todo su Equipo con una sola Conexión Acciones Preventivas contra Demandas Laborales 24 de noviembre - Online en Vivo - 10:00 a 13:00 y de 15:00 a 18:00 Hrs Debemos de tomar en cuenta que una demanda es el inicio de un juicio laboral, en la cual se dirige a los miembros de la Junta Especial de Conciliación y Arbitraje, ya sea local o federal, en donde el trabajador, quien normalmente es quien promueve, manifiesta su inconformidad con su patrón mediante la vía legal, reclamando diversas prestaciones, las cuales pueden ser justificadas o no. Esto le representa una considerable pérdida de tiempo y recursos en caso de no tener una correcta cultura preventiva. TEMARIO: 1. Desarrolle mecanismos de prevención de Demandas Laborales para la protección de su empresa u organización. 2. Conozca los alcances de los recursos legales del Patrón y cómo aprovechar los mismos. 3. Aprenda a ejecutar acciones contundentes y eficaces en esta materia. ...¡Y mucho más! ¿Requiere la información a la Brevedad? responda este email con la palabra: Info - Demandas. centro telefónico: 018002129393 Lic. Arturo López Coordinador de Evento ¿Demasiados mensajes en su cuenta? Responda este mensaje indicando que solo desea recibir CALENDARIO y sólo recibirá un correo al mes. Si desea cancelar la suscripción, solicite su BAJA. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net-mgmt/prometheus update to 1.3.1, committer requested
Hi! > Could I get a committer to apply my latest update patch for > net-mgmt/prometheus, which is available here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214245 Yes, done. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PR commit request
Hi! > Would someone please commit following 2 PRs with maintainer timeout? > > Bug 212898 - textproc/trang: update to 2015.11.27 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212898 > Bug 212899 - textproc/jing: update to 2015.11.27 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212899 Done. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
net-mgmt/prometheus update to 1.3.1, committer requested
Hi All, Could I get a committer to apply my latest update patch for net-mgmt/prometheus, which is available here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214245 Thanks, -Jev ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Resurrecting games/wmfortune (Was: Re: misc/jive deleted)
Julian H. Stacey wrote: > FYI in case newer than yours, Fonz, I have > MD5 (9.2-RELEASE/wmfortune-0.241.tar.gz) = fa8db5d9a46d9afe7757f498c781e8c9 > SHA256 (9.2-RELEASE/wmfortune-0.241.tar.gz) = > b149067b7e3521f7e03354b12754baaf9c5556af4d286bbd6d169b1db9f6dba0 > > It builds & run on my 9.2, I've not tried on current. That matches what I've got and appears to be the most recent, thanks. Considering the overly aggressive pruning of the ports tree that the Powers That Be have been conveying (but what to me rather more seems like attempting to perform intricate neurosurgery using a sledgehammer and a chainsaw), it's unlikely that a port which is no longer maintained upstream will be welcomed back into the tree, even though people are willing to maintain the port and host the distfiles. There probably needs to be some sort of alternative--or "underground" if you like--tree that can serve those ports that are not to the liking of a select few (and/or that have been taken away from the tolerant in order to appease the intolerant, such as in the misc/jive case). I'm currently looking into what's the best way to go about setting up such a supplementary tree. Fonz -- A.J. "Fonz" van Werven mailsig: Help! I'm a prisoner in a Chinese fortune cookie factory. signature.asc Description: PGP signature
Re: [HEADSUP] Default Perl changed to 5.24.
On 07/11/2016 06:47, Mark Millard wrote: > Here is what I found looking back in 5.22 after switching to 5.24: > >> > # find /usr/local/lib/perl5/site_perl/mach/5.22/ -print | grep packlist | >> > more >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/File/Listing/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/Net/HTTP/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/URI/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/Mozilla/CA/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/LWP/MediaTypes/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/LWP/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/Digest/HMAC/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/IO/Socket/IP/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/IO/Socket/SSL/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/IO/HTML/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/Encode/Locale/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/HTTP/Negotiate/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/HTTP/Message/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/HTTP/Cookies/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/HTTP/Daemon/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/WWW/RobotRules/.packlist >> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/Authen/NTLM/.packlist > None of this had 5.24 equivalents present. > .packlist files are autogenerated by perl during the installation of a module into staging. They contain a manifest of the module as installed on your system. This makes them redundant considering that a pkg file already contains this, and more, information. I believe the current consensus is that .packlist files should not be copied out of the staging area when creating a pkg of a perl module, and should not be considered part of a pkg. Although it seems that consensus is not followed by all perl module packages. Unfortunately, there is nothing to clean up any pre-existing .packlist files already installed in you $PERL5LIB and it's only at the relatively rare occasions like this when the perl module library switches to a new directory that their presence becomes obvious. Cheers, Matthew signature.asc Description: OpenPGP digital signature
