Re: Xorg error 'alphasort'

[Willem Jan Withagen]

On 31/05/2017 18:21, Masachika ISHIZUKA wrote:

   Hi.

   I was using 12-current r318249 and did 'pkg upgrade', and
could not start xorg with alphasort error.
   After updating r319315, xorg works again.


Right I had more or less the same with r319216.
And I was going to reinstall from a snapshot, but now I'll try and move 
forward.


--WjW

___
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: Sylpheed bug?

[Torfinn Ingolfsen]

Hello,

On Thu, Jun 1, 2017 at 6:39 AM, Waitman Gobble  wrote:
>
> Rececently installed Sylpheed Port on FreeBSD-11.0, everything works unless I 
> press 'Get' or 'Get All' buttons at the top, if i do that it instally kills 
> everything running from /usr/local and restarts xorg. Seconds flat. Maybe 
> it's good for a bug report? I haven't done much on this machine and I don't 
> think I dicked it up. But maybe I did?

FWIW, I run Sylpheed on my main workstation and upgrade from time to
time. I haven't seen any errors recently.
My workstation runs FreeBSD 10.3-stable:
root@kg-core1# uname -a
FreeBSD kg-core1.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r310083:
Wed Dec 14 21:00:13 CET 2016
r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

and the latest version of Sylpheed from ports:
root@kg-core1# pv sylp*
[Reading data from pkg(8) ... - 797 packages found - done]
sylpheed-3.5.1_1=  up-to-date with port

HTH
-- 
Regards,
Torfinn Ingolfsen
___
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: FreeBSD Port: lang/php71-extensions - missing php71-mssql

[Torsten Zuehlsdorff]

On 15.05.2017 16:46, Miroslav Lachman wrote:

Torsten Zuehlsdorff wrote on 2017/05/15 15:00:


I search the internet and didn't found any problem reports for this.

PHP manual still shows this
http://php.net/manual/en/mssql.requirements.php


If you read the manual this section is very important:
This extension is not available anymore on Windows with PHP 5.3 or later.


Yes, I know that, but the important part is "Windows". I think it was 
due to some licence / patent issue. For Windows there is SQLSRV provided 
by Microsoft for a long time.


After some more investigation, i don't see a - lets say - practicable 
way. The mssql module was completely removed from PHP code. There are 
only some missed entries in the .gitignore and in an date parser.


Of course i can try to port the PHP 5.6 mssql code to PHP 7.0. But this 
would be much work and i haven't a proper possibility to test or the 
free time for it. But i will give this some thoughts.


Greetings,
Torsten
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
devel/py-isort  | 4.2.5   | 4.2.8
+-+
graphics/opencollada| 1.6.47  | v1.6.51
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

samba 44 and bind 911

[Xavier]

Hello,

I hava a build problem while upgrading samba44 :

[root@numenor ~]# portupgrade -v samba44
[... building...]
===>  Staging for samba44-4.4.14
===>   samba44-4.4.14 depends on package: libarchive>=3.1.2 - found
===>   samba44-4.4.14 depends on package: py27-dnspython>=1.9.4 - found
===>   samba44-4.4.14 depends on package: py27-iso8601>=0.1.11 - found
===>   samba44-4.4.14 depends on package: talloc>=2.1.6 - found
===>   samba44-4.4.14 depends on package: tevent>=0.9.28 - found
===>   samba44-4.4.14 depends on package: tdb>=1.3.8 - found
===>   samba44-4.4.14 depends on package: ldb>=1.1.26 - found
===>   samba44-4.4.14 depends on package: bind910>=9.10.0.0 - not found

===>  bind910-9.10.5 conflicts with installed package(s):
  bind911-9.11.1

It seems that samba44 requires bind 910 while bind 911 doesent meet the
requisite bind910>=9.10.0.0

Is there another workaround than to downgrade bind911 to 910 ?

TIA,

Xav

-- 
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
___
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: The future of portmaster [and of ports-mgmt/synth]

[Mark Linimon]

On Wed, May 31, 2017 at 05:58:24PM +0100, Matthew Seaman wrote:
> Core has some proposals around planning for such changes that they will
> be talking about during the BSDCan devsummit next week.  These should
> also be published internally fairly soon afterwards for the benefit of
> people not at BSDCan.

I'll look forward to seein what the conclusions are.

mcl
___
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: samba 44 and bind 911

[Dimitry Andric]

On 1 Jun 2017, at 11:55, Xavier  wrote:
> 
> I hava a build problem while upgrading samba44 :
> 
> [root@numenor ~]# portupgrade -v samba44
> [... building...]
> ===>  Staging for samba44-4.4.14
> ===>   samba44-4.4.14 depends on package: libarchive>=3.1.2 - found
> ===>   samba44-4.4.14 depends on package: py27-dnspython>=1.9.4 - found
> ===>   samba44-4.4.14 depends on package: py27-iso8601>=0.1.11 - found
> ===>   samba44-4.4.14 depends on package: talloc>=2.1.6 - found
> ===>   samba44-4.4.14 depends on package: tevent>=0.9.28 - found
> ===>   samba44-4.4.14 depends on package: tdb>=1.3.8 - found
> ===>   samba44-4.4.14 depends on package: ldb>=1.1.26 - found
> ===>   samba44-4.4.14 depends on package: bind910>=9.10.0.0 - not found
> 
> ===>  bind910-9.10.5 conflicts with installed package(s):
>  bind911-9.11.1
> 
> It seems that samba44 requires bind 910 while bind 911 doesent meet the
> requisite bind910>=9.10.0.0
> 
> Is there another workaround than to downgrade bind911 to 910 ?

Run "make config" in the net/samba44 directory, and select "Use bind911
as AD DC DNS server frontend".

-Dimitry



signature.asc
Description: Message signed with OpenPGP

head/sysutils/testdisk failes on 12-CURRENT amd64

[Matthias Apitz]

Hello,

On

# uname -a
FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314251: Sat Feb 25 
17:14:40 CET 2017 root@r303343-amd64:/usr/obj/usr/src/sys/GENERIC  amd64

sysutils/testdisk PORTVERSION=7.0 fails to compile when in
/etc/make.conf  

CFLAGS+= -DDEBUG

is set.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature

Re: Sylpheed bug?

[Waitman Gobble]

On 2017-06-01 02:53, Torfinn Ingolfsen wrote:


Hello,

On Thu, Jun 1, 2017 at 6:39 AM, Waitman Gobble  
wrote:


Rececently installed Sylpheed Port on FreeBSD-11.0, everything works 
unless I press 'Get' or 'Get All' buttons at the top, if i do that it 
instally kills everything running from /usr/local and restarts xorg. 
Seconds flat. Maybe it's good for a bug report? I haven't done much on 
this machine and I don't think I dicked it up. But maybe I did?


FWIW, I run Sylpheed on my main workstation and upgrade from time to
time. I haven't seen any errors recently.
My workstation runs FreeBSD 10.3-stable:
root@kg-core1# uname -a
FreeBSD kg-core1.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r310083:
Wed Dec 14 21:00:13 CET 2016
r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

and the latest version of Sylpheed from ports:
root@kg-core1# pv sylp*
[Reading data from pkg(8) ... - 797 packages found - done]
sylpheed-3.5.1_1=  up-to-date with port

HTH





% uname -a
FreeBSD ayana.waitman.net 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: 
Tue Apr 11 08:48:40 UTC 2017 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

% pkg info | grep syl
sylpheed-3.5.1_1


"maybe" this is a log of the problem, Xorg

[ 15752.020] Failed to compile VS: 0:13(43): error: `pos' undeclared
0:13(14): error: operands to arithmetic operators must be numeric
0:13(13): error: operands to arithmetic operators must be numeric

[ 15752.020] Program source:
#define ATLAS_DIM_INV 0.0009765625
attribute vec2 primitive;
attribute vec2 source;
varying vec2 glyph_pos;
uniform vec2 fill_offset;
uniform vec2 fill_size_inv;
varying vec2 fill_pos;
uniform vec4 v_matrix;
void main() {
   gl_Position.xy = primitive.xy * v_matrix.xz + v_matrix.yw;
   gl_Position.zw = vec2(0.0,1.0);
   glyph_pos = source.xy * ATLAS_DIM_INV;
   fill_pos = (fill_offset + primitive.xy + pos) * fill_size_inv;
}
[ 15752.020] (EE)
Fatal server error:
[ 15752.020] (EE) GLSL compile failure
[ 15752.020] (EE)
[ 15752.020] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[ 15752.020] (EE) Please also check the log file at 
"/var/log/Xorg.0.log" for additional information.

[ 15752.020] (EE)
[ 15752.020] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 15752.155] (EE) Server terminated with error (1). Closing log file.


It seems this is mentioned as a bug/patched last year around August 2016 
so probably this version doesn't have the fix?


X.Org X Server 1.18.4
Release Date: 2016-07-19


--
Waitman Gobble




___
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: The future of portmaster [and of ports-mgmt/synth]

[Torsten Zuehlsdorff]

On 31.05.2017 20:31, Adam Weinberger wrote:

On 31 May, 2017, at 11:28, Per olof Ljungmark 
wrote:

On 2017-05-31 02:10, Kevin Oberman wrote:

On Tue, May 30, 2017 at 2:53 PM, Mark Linimon
mailto:lini...@lonesome.com>> wrote: On
Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote:

Hello, I have not followed this thread before but just wanted
to say that I use portmaster extensively, it works for us and I
would miss it if it went.  Are there actually plans to retire
it?

To reiterate the status: * some extensive changes to the ports
framework are coming; * these will require large changes to all
the port upgrade tools; * no one has stepped forwards to offer to
do the work for anything other than poudriere AFAIK. If no one
does the work, at the time the large changes come, the other
tools will break. People have been wanting subpackages (aka
flavors) for many years; IIUC these are parts of the changes that
are coming. Someone needs to step forwards and say "yes, I will
do the work." mcl Since portmaster is still popult and since the
only solutions that looks to be available in the near term are
pouderiere or raw make, neither terribly viable for many, I will
look into updating portmaster to deal with 'flavors'. This looks
fairly straight forward and I my have the sh capability to manage
it. (And then again, I am far from a great shell person, so I may
well be wrong.) I have looked at Doug's script and it is pretty
readable, but writing may require help. Can someone point me
where to look for documentation on flavors? I have poked around
the wiki, but to no avail. Unless there is documentation on what
needs to be done, doing it will be hopeless and waiting for the
packaging system to updated means portmaster WILL be broken for
some period of time.


Let me just say that I would really, really appriciate if we could
keep such a simple tool. Why does it suit us? Because we have a
limited number of systems, and they are all different meaning that
we custom build for almost every task. Portmaster makes very easy
to build what we need on each host. Yes, it brakes sometimes but it
is not that hard to figure out how to get around.


I want to reiterate that nobody is taking portmaster away from you.
It simply has not been actively developed for years. In all
likelihood, somebody will patch portmaster eventually. Poudriere is a
safer, more capable tool than portmaster, and it's better to migrate
when there's no immediate time pressure or breakage.

The changes are not about to drop. Portmaster is not going to stop
working tomorrow. We are bringing it up now so that you have time to
consider migrating to poudriere or synth. If your system(s) and
workflow make poudriere a viable option, we want to encourage and
help you to migrate while there's no time pressure.

Sending emails to this list about why you prefer portmaster doesn't
change the underlying problem, though: portmaster will only be
long-term viable if somebody actively develops it again.


Just as a short note: there is a complete rewrite of portmaster ongoing. 
Since its a beast and everything else is very hard there is no public 
evidence in case of failure. ;) Until now.


I'm currently try to convince all persons already got frustrated by 
portmaster-programming to come together and work on it. I'm also working 
at an decent automatic QA for it (and PHP and GitLab).


Greetings,
Torsten
___
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: Firefox (and other Mozilla products) after ino64

[Gary Jennejohn]

On Wed, 31 May 2017 23:27:16 +0200
Dimitry Andric  wrote:

[snip]
> This also applies to other Mozilla products, such as Thunderbird,
> SeaMonkey, and so on.  These should all be rebuilt from scratch under
> ino64.
> 

FYI Seamonkey still works after updating kernel and world to ino64.

-- 
Gary Jennejohn
___
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: The future of portmaster [and of ports-mgmt/synth]

[Matthieu Volat]

On Thu, 1 Jun 2017 15:45:43 +0200
Torsten Zuehlsdorff  wrote:

> [...]
> Just as a short note: there is a complete rewrite of portmaster ongoing. 
> Since its a beast and everything else is very hard there is no public 
> evidence in case of failure. ;) Until now.
> 
> I'm currently try to convince all persons already got frustrated by 
> portmaster-programming to come together and work on it. I'm also working 
> at an decent automatic QA for it (and PHP and GitLab).
>

Hi and thanks, is there a name and a public repository for this initiative?


pgpDnNHjpXSXE.pgp
Description: OpenPGP digital signature

nvidia drivers mutex lock

[blubee blubeeme]

I'm running nvidia-drivers 375.66 with a GTX 1070 on FreeBSD-Current

This problem just started happening recently but, every so often my laptop
screen will just blank out and then I have to power cycle to get the
machine up and running again.

It seems to be a problem with nvidia drivers acquiring duplicate lock. Any
info on this?

Jun  2 02:29:41 blubee kernel: acquiring duplicate lock of same type:
"os.lock_mtx"
Jun  2 02:29:41 blubee kernel: 1st os.lock_mtx @ nvidia_os.c:841
Jun  2 02:29:41 blubee kernel: 2nd os.lock_mtx @ nvidia_os.c:841
Jun  2 02:29:41 blubee kernel: stack backtrace:
Jun  2 02:29:41 blubee kernel: #0 0x80ab7770 at
witness_debugger+0x70
Jun  2 02:29:41 blubee kernel: #1 0x80ab7663 at
witness_checkorder+0xe23
Jun  2 02:29:41 blubee kernel: #2 0x80a35b93 at
__mtx_lock_flags+0x93
Jun  2 02:29:41 blubee kernel: #3 0x82f4397b at
os_acquire_spinlock+0x1b
Jun  2 02:29:41 blubee kernel: #4 0x82c48b15 at _nv012002rm+0x185
Jun  2 02:29:41 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM:
Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
(20170303/nsarguments-205)
Jun  2 02:29:42 blubee kernel: nvidia-modeset: Allocated GPU:0
(GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI::01:00.0

Best,
Owen
___
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: Sylpheed bug?

[Torfinn Ingolfsen]

Hello!
Some things to check:
1) is Sylpheed the only program that makes your Xorg crash?
2) which DE (Desktop Environment) are you using? I'm using Xfce
3) are any "special effects" turned on in your Xorg / DE setup? Things
like Compositor, ...?
4) if "yes" in 3 - does it help if you turn off those "special effects"?
5) Are you using ports exclusively, or are you mixing ports and packages?

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

3Com Users

[Daisy Fields]

Hi, 

 

Hope my email finds you well.

 

Would you be interested in all 3Com Clients email list for your sales,
marketing and email campaigns?

We can provide you Database across North America, EMEA, APAC and Latin
America.

 

We provide complete Information Fields like - Name, Title, Email address,
Phone Numbers, Company Name, and Company Details like, Physical Address, Web
Address, Revenue Size, Employee Size and industry.

 

We have list of 3Com Products which you may be interested in:

*  Juniper Networks

*  Netgear

*  Nortel

*  ProCurve

*  D-Link

*  Cisco

*  Intel

*  3M 

*  ZyXEL

*  Avaya and many more. 

 

Please review and let me know what technology users you are interested in
and I will get back to you with more information for the same.

 

I await your response and look forward to serving you!

 

Regards,

Daisy Fields

Cloud Consultant

 

If you wish not to receive these emails, please reply LEAVE OUT in the
subject line.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

___
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: Hosting distfiles on HTTPS w/Let's Encrypt - how?

[Marcin Cieslak]

On Thu, 1 Jun 2017, Jov wrote:

> can you dowload the file distfiles/INIT.2014-12-24.tgz
>  using
> browser such as chrome？

Yes, Firefox, IE11, no certificate warnings.

> be sure to use full chain cert file，I rember I had similar problem and use
> full chain cert fixed.

(Without the root CA):


Certificate chain
 0 s:/CN=marcincieslak.com   
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3 

How should fetch know that "=Digital Signature Trust Co./CN=DST Root CA X3" is
a valid CA if none have been installed?

Marcin Cieślak

smime.p7s
Description: S/MIME Cryptographic Signature

Re: nvidia drivers mutex lock

[Jeffrey Bouquet via freebsd-ports]

I see the same message, upon load, ...

On Thu, 6/1/17, blubee blubeeme  wrote:

 Subject: nvidia drivers mutex lock
 To: freebsd-ports@freebsd.org, freebsd-curr...@freebsd.org
 Date: Thursday, June 1, 2017, 11:35 AM
 
 I'm running nvidia-drivers 375.66 with a GTX
 1070 on FreeBSD-Current
 
 This problem just started happening
 recently but, every so often my laptop
 screen will just blank out and then I
 have to power cycle to get the
 machine up and running again.
 
 It seems to be a problem with nvidia
 drivers acquiring duplicate lock. Any
 info on this?
 
 Jun  2 02:29:41 blubee kernel:
 acquiring duplicate lock of same type:
 "os.lock_mtx"
 Jun  2 02:29:41 blubee kernel: 1st
 os.lock_mtx @ nvidia_os.c:841
 Jun  2 02:29:41 blubee kernel: 2nd
 os.lock_mtx @ nvidia_os.c:841
 Jun  2 02:29:41 blubee kernel:
 stack backtrace:
 Jun  2 02:29:41 blubee kernel: #0
 0x80ab7770 at
 witness_debugger+0x70
 Jun  2 02:29:41 blubee kernel: #1
 0x80ab7663 at
 witness_checkorder+0xe23
 Jun  2 02:29:41 blubee kernel: #2
 0x80a35b93 at
 __mtx_lock_flags+0x93
 Jun  2 02:29:41 blubee kernel: #3
 0x82f4397b at
 os_acquire_spinlock+0x1b
 Jun  2 02:29:41 blubee kernel: #4
 0x82c48b15 at _nv012002rm+0x185
 Jun  2 02:29:41 blubee kernel:
 ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM:
 Argument #4 type mismatch - Found
 [Buffer], ACPI requires [Package]
 (20170303/nsarguments-205)
 Jun  2 02:29:42 blubee kernel:
 nvidia-modeset: Allocated GPU:0
 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @
 PCI::01:00.0
 
 Best,
 Owen
 ___
 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"
 


... then Xorg will run happily twelve hours or so.  The lockups here happen 
usually
when too large or too many of number of tabs/ large web pages with complex CSS 
etc
are opened at a time.  
So no help, just a 'me too'.  
___
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: Sylpheed bug?

[Waitman Gobble]

On 2017-06-01 15:52, Torfinn Ingolfsen wrote:


Hello!
Some things to check:
1) is Sylpheed the only program that makes your Xorg crash?
2) which DE (Desktop Environment) are you using? I'm using Xfce
3) are any "special effects" turned on in your Xorg / DE setup? Things
like Compositor, ...?
4) if "yes" in 3 - does it help if you turn off those "special 
effects"?
5) Are you using ports exclusively, or are you mixing ports and 
packages?


HTH



So far it appears that Sylpheed is the only thing I have installed that 
crashes Xorg. But I'd probably need to see how they built Sylpheed, like 
if they used GTK or whatever. I glanced at the source for 60 seconds and 
nothing popped out.


I'm using KDE. I used to only use Xfce, I cannot remember why I switched 
to KDE but i've been using that on everything. On this machine I've only 
installed pkg.


I'm pretty sure the Xorg 'pos' bug was discovered and fixed in August 
2016, and this version probably does not have that fix.


This is obviously compositing, I'd have to research where to turn that 
off to see if it makes a difference. But maybe it's OK to wait for a new 
Xorg version.



---
Waitman Gobble
___
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: Hosting distfiles on HTTPS w/Let's Encrypt - how?

[Freddie Cash]

On Jun 1, 2017 4:06 PM, "Marcin Cieslak"  wrote:

On Thu, 1 Jun 2017, Jov wrote:

> can you dowload the file distfiles/INIT.2014-12-24.tgz
>  using
> browser such as chrome？

Yes, Firefox, IE11, no certificate warnings.

> be sure to use full chain cert file，I rember I had similar problem and use
> full chain cert fixed.

(Without the root CA):


Certificate chain
 0 s:/CN=marcincieslak.com
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3

How should fetch know that "=Digital Signature Trust Co./CN=DST Root CA X3"
is
a valid CA if none have been installed?

Marcin Cieślak


In your web server configuration, are you using the Let's Encrypt cert.pem
or fullchain.pem?

If you use the former, then any client that doesn't have the DST Root CA
pre-installed will error out. The latest versions of browsers will work, as
they include the DST Root CA.

If you use the latter, then it will just work, as the server will send all
the intermediate certificate info needed to reach the root.

Cheers,
Freddie
___
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: Hosting distfiles on HTTPS w/Let's Encrypt - how?

[Marcin Cieslak]

On Thu, 1 Jun 2017, Freddie Cash wrote:

> In your web server configuration, are you using the Let's Encrypt cert.pem
> or fullchain.pem?

fullchain.pem

> If you use the former, then any client that doesn't have the DST Root CA
> pre-installed will error out. The latest versions of browsers will work, as
> they include the DST Root CA.

My fullchain.pem as delivered by dehydrated does not include the DST Root CA.

> If you use the latter, then it will just work, as the server will send all
> the intermediate certificate info needed to reach the root.

To test this theory, I have added DST Root CA to my customized fullchain.pem
which now contains:

Certificate chain
 0 s:/CN=marcincieslak.com
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3

 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3

 2 s:/O=Digital Signature Trust Co./CN=DST Root CA X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3

so now we have "DST Root CA X3" extra.

And the result is:

=> INIT.2014-12-24.tgz doesn't seem to exist in /portdistfiles/ksh93.
=> Attempting to fetch 
https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz
Certificate verification failed for /O=Digital Signature Trust Co./CN=DST Root 
CA X3
34374329736:error:14090086:SSL routines:ssl3_get_server_certificate:certificate 
verify 
failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1264:
fetch: https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz: 
Authentication error
=> Attempting to fetch 
http://distcache.FreeBSD.org/ports-distfiles/ksh93/INIT.2014-12-24.tgz
fetch: http://distcache.FreeBSD.org/ports-distfiles/ksh93/INIT.2014-12-24.tgz: 
Not Found

so it cannot validate "DST Root CA X3" now, because it does not have the 
pre-installed CA bundle.


Marcin Cieślak

smime.p7s
Description: S/MIME Cryptographic Signature

Re: Hosting distfiles on HTTPS w/Let's Encrypt - how?

[Jov]

what's your /etc/ssl/cert.pem?
mine is:
ls -l /etc/ssl/cert.pem
lrwxr-xr-x  1 root  wheel  38  4月 29 09:15 /etc/ssl/cert.pem@ ->
/usr/local/share/certs/ca-root-nss.crt

you can use this command to get more ssl connection info:
openssl s_client -connect :443

Jov
blog: http:amutu.com/blog

2017-06-02 10:13 GMT+08:00 Marcin Cieslak :

> On Thu, 1 Jun 2017, Freddie Cash wrote:
>
> > In your web server configuration, are you using the Let's Encrypt
> cert.pem
> > or fullchain.pem?
>
> fullchain.pem
>
> > If you use the former, then any client that doesn't have the DST Root CA
> > pre-installed will error out. The latest versions of browsers will work,
> as
> > they include the DST Root CA.
>
> My fullchain.pem as delivered by dehydrated does not include the DST Root
> CA.
>
> > If you use the latter, then it will just work, as the server will send
> all
> > the intermediate certificate info needed to reach the root.
>
> To test this theory, I have added DST Root CA to my customized
> fullchain.pem
> which now contains:
>
> Certificate chain
>  0 s:/CN=marcincieslak.com
>i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
>
>  1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
>i:/O=Digital Signature Trust Co./CN=DST Root CA X3
>
>  2 s:/O=Digital Signature Trust Co./CN=DST Root CA X3
>i:/O=Digital Signature Trust Co./CN=DST Root CA X3
>
> so now we have "DST Root CA X3" extra.
>
> And the result is:
>
> => INIT.2014-12-24.tgz doesn't seem to exist in /portdistfiles/ksh93.
> => Attempting to fetch https://distfile.net/local-
> ports-distfiles/INIT.2014-12-24.tgz
> Certificate verification failed for /O=Digital Signature Trust Co./CN=DST
> Root CA X3
> 34374329736:error:14090086:SSL 
> routines:ssl3_get_server_certificate:certificate
> verify failed:/usr/src/secure/lib/libssl/../../../crypto/
> openssl/ssl/s3_clnt.c:1264:
> fetch: https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz:
> Authentication error
> => Attempting to fetch http://distcache.FreeBSD.org/
> ports-distfiles/ksh93/INIT.2014-12-24.tgz
> fetch: http://distcache.FreeBSD.org/ports-distfiles/ksh93/INIT.
> 2014-12-24.tgz: Not Found
>
> so it cannot validate "DST Root CA X3" now, because it does not have the
> pre-installed CA bundle.
>
>
> Marcin Cieślak
___
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: Hosting distfiles on HTTPS w/Let's Encrypt - how?

[Adam Weinberger]

> On 1 Jun, 2017, at 21:15, Jov  wrote:
> 
> what's your /etc/ssl/cert.pem?
> mine is:
> ls -l /etc/ssl/cert.pem
> lrwxr-xr-x  1 root  wheel  38  4月 29 09:15 /etc/ssl/cert.pem@ ->
> /usr/local/share/certs/ca-root-nss.crt
> 
> you can use this command to get more ssl connection info:
> openssl s_client -connect :443

I've tried fetching a distfile from my own server (which uses a Let's Encrypt 
cert) and it fetches fine in a poudriere jail. I'm suspecting that there's 
something unusual in your web server's SSL configuration, or in how you're 
generating your LE cert. Do you have any interesting arguments that you're 
giving dehydrated or your web server?

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org



> 
> Jov
> blog: http:amutu.com/blog
> 
> 2017-06-02 10:13 GMT+08:00 Marcin Cieslak :
> 
>> On Thu, 1 Jun 2017, Freddie Cash wrote:
>> 
>>> In your web server configuration, are you using the Let's Encrypt
>> cert.pem
>>> or fullchain.pem?
>> 
>> fullchain.pem
>> 
>>> If you use the former, then any client that doesn't have the DST Root CA
>>> pre-installed will error out. The latest versions of browsers will work,
>> as
>>> they include the DST Root CA.
>> 
>> My fullchain.pem as delivered by dehydrated does not include the DST Root
>> CA.
>> 
>>> If you use the latter, then it will just work, as the server will send
>> all
>>> the intermediate certificate info needed to reach the root.
>> 
>> To test this theory, I have added DST Root CA to my customized
>> fullchain.pem
>> which now contains:
>> 
>> Certificate chain
>> 0 s:/CN=marcincieslak.com
>>   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
>> 
>> 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
>>   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
>> 
>> 2 s:/O=Digital Signature Trust Co./CN=DST Root CA X3
>>   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
>> 
>> so now we have "DST Root CA X3" extra.
>> 
>> And the result is:
>> 
>> => INIT.2014-12-24.tgz doesn't seem to exist in /portdistfiles/ksh93.
>> => Attempting to fetch https://distfile.net/local-
>> ports-distfiles/INIT.2014-12-24.tgz
>> Certificate verification failed for /O=Digital Signature Trust Co./CN=DST
>> Root CA X3
>> 34374329736:error:14090086:SSL 
>> routines:ssl3_get_server_certificate:certificate
>> verify failed:/usr/src/secure/lib/libssl/../../../crypto/
>> openssl/ssl/s3_clnt.c:1264:
>> fetch: https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz:
>> Authentication error
>> => Attempting to fetch http://distcache.FreeBSD.org/
>> ports-distfiles/ksh93/INIT.2014-12-24.tgz
>> fetch: http://distcache.FreeBSD.org/ports-distfiles/ksh93/INIT.
>> 2014-12-24.tgz: Not Found
>> 
>> so it cannot validate "DST Root CA X3" now, because it does not have the
>> pre-installed CA bundle.
>> 
>> 
>> Marcin Cieślak
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"