Re: svnup is b0rken!

2017-06-12 Thread Kubilay Kocak 
On 6/13/17 4:03 AM, Maxim Sobolev wrote:
> Hi, latest version of the svnup package is broken on several of my boxes.
> I've tried few public svn mirrors makes no difference.
> 
> -Max
> 
> [sobomax@van01 ~/projects/softswitch]$ svnup ports
> # Revision: 443456
> 
> Command Failure: HTTP/1.1 400 Bad Request
> Date: Mon, 12 Jun 2017 18:01:09 GMT
> Server: Apache
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
> 
> 
> 
> 400 Bad Request
> 
> Bad Request
> Your browser sent a request that this server could not understand.
> 
> 

The issue is being tracked here:

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

tldr: Affects SVN over http[s] (WebDAV), due to mirrors no longer
(unknown reason) supporting REPORT command.

No response from cluster admin (who are svn admin) yet.


___
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: svnup is b0rken!

2017-06-12 Thread John Mehr 
Hello,

It looks like the latest version of Subversion has become more strict with
regards to CR+LFs and the attached patch should get things working for you
again.  Please give it a try and let me know how it goes.

I've got a couple other fixes I'm working on and I'm hoping to have 1.08
rolled out in the next week or so.  I used to host the tarball on my
personal web server (which due to an ISP change is no longer available) and
I'm looking into finding a new place to host it (probably github).

On Mon, Jun 12, 2017 at 1:03 PM, Maxim Sobolev  wrote:

> Hi, latest version of the svnup package is broken on several of my boxes.
> I've tried few public svn mirrors makes no difference.
>
> -Max
>
> [sobomax@van01 ~/projects/softswitch]$ svnup ports
> # Revision: 443456
>
> Command Failure: HTTP/1.1 400 Bad Request
> Date: Mon, 12 Jun 2017 18:01:09 GMT
> Server: Apache
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
>
> 
> 
> 400 Bad Request
> 
> Bad Request
> Your browser sent a request that this server could not understand.
> 
> 
>
>


-- 
John Mehr
Software Developer / Database Administrator
Humphrey School of Public Affairs, University of Minnesota
54c54
< #define SVNUP_VERSION "1.07"
---
> #define SVNUP_VERSION "1.07a"
1542d1541
<   struct stat  local;
1565,1570c1564,1569
<   "\n"
<   "/%s\n"
<   "%d\n"
<   "unknown\n"
<   "\n"
<   "\n"
---
>   ""
>   "/%s"
>   "%d"
>   "unknown"
>   " start-empty=\"true\">"
>   "\r\n"
1575c1574
<   strlen(connection->branch) + revision_length + revision_length 
+ strlen(SVNUP_VERSION) + 206,
---
>   strlen(connection->branch) + revision_length + revision_length 
> + 205,
2392,2394c2391,2393
<   "PROPFIND %s HTTP/1.1\n"
<   "Depth: 1\n"
<   "Host: %s\n\n",
---
>   "PROPFIND %s HTTP/1.1\r\n"
>   "Depth: 1\r\n"
>   "Host: %s\r\n\r\n",
2474,2476c2473,2475
<   "GET %s HTTP/1.1\n"
<   "Host: %s\n"
<   "Connection: Keep-Alive\n\n",
---
>   "GET %s HTTP/1.1\r\n"
>   "Host: %s\r\n"
>   "Connection: 
> Keep-Alive\r\n\r\n",
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Looking for good sould with a commit bit

2017-06-12 Thread Ultima 
done!

On Mon, Jun 12, 2017 at 1:31 PM, Łukasz Wąsikowski 
wrote:

> I'm looking for someone with a commit bit to look at
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208147 - new port
> [sysutils/modman]
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219825 - maintainer
> approves [security/rkhunter]
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219726 - maintainer
> update [www/mod_mpm_itk]
>
> Thank you!
>
> --
> best regards,
> Lukasz Wasikowski
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: wget 1.19 missed IRI supporting

2017-06-12 Thread Martin Wilke 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Approved.

On Mon, Jun 12, 2017 at 08:07:44PM +0200, Vasil Dimov wrote:
> On Tue, Jun 06, 2017 at 14:03:01 -0400, Matthew Seaman wrote:
> > On 06/06/2017 10:37, Cos Chan wrote:
> > > I got mistake while running this command:
> > > 
> > > wget --no-verbose --remote-encoding=UTF-8 --local-encoding=UTF-8 --mirror
> > > --directory-prefix=/foo/ --no-parent --no-host-directories --cut-dirs=2
> > > --force-directories --accept=*.pdf --restrict-file-names=nocontrol
> > > http://bar/Documents/
> > > 
> > > the mistake is : This version does not have support for IRIs
> > > 
> > > the wget version is:
> > > 
> > > $ wget --version
> > > GNU Wget 1.19 built on freebsd11.0.
> > > 
> > > -cares +digest -gpgme +https +ipv6 -iri +large-file -metalink +nls
> > > +ntlm +opie -psl +ssl/openssl
> > > 
> > > Wgetrc:
> > > /usr/local/etc/wgetrc (system)
> > > Locale:
> > > /usr/local/share/locale
> > > Compile:
> > > clang -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/usr/local/etc/wgetrc"
> > > -DLOCALEDIR="/usr/local/share/locale" -I. -I../lib -I../lib
> > > -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG
> > > -D_THREAD_SAFE -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector
> > > -fno-strict-aliasing
> > > Link:
> > > clang -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector
> > > -fno-strict-aliasing -L/usr/local/lib -L/usr/local/lib
> > > -Wl,-rpath,/usr/local/lib -fstack-protector
> > > /usr/local/lib/libssl.so /usr/local/lib/libcrypto.so -Wl,-rpath
> > > -Wl,/usr/local/lib -lz ftp-opie.o openssl.o http-ntlm.o
> > > ../lib/libgnu.a -L/usr/local/lib -lintl -Wl,-rpath=/usr/local/lib
> > > 
> > > This issue was not happened in previous versions. Could anyone add back 
> > > IRI
> > > supporting to V1.19 binary package?
> > 
> > Hi,
> > 
> > freebsd-ports@ is a better mailing list to ask this question on.
> > 
> > IRI support should be enabled in the default wget package build.  It
> > looks like IDN support was broken in 1.19 but fixed in 1.19.1 according
> > to this commit:
> > 
> > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2102070+0+/usr/local/www/mailindex/archive/2017/svn-ports-head/20170409.svn-ports-head
> > 
> > Unfortunately it looks like that has only been applied to the HEAD
> > branch of the ports tree, but not the 2017Q2 branch, and it is the
> > 2017Q2 branch which is where the default packages are built from at the
> > moment.
> > 
> > I've CC'd the ports maintainer to see if he'd consider a MFH of r437857.
> >  That should be permitted under the rules, as it's fixing broken
> > functionality.
> [...]
> 
> Hello,
> 
> As per
> https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-misc-request-mfh
> I am requesting approval to merge r437857 from head to 2017Q2.
> 
> -- 
> Vasil Dimov
> gro.DSBeerF@dv
> %
> LOVE:
> When, if asked to choose between your lover
> and happiness, you'd skip happiness in a heartbeat.



- -- 
+-oOO--(_)--OOo-+
With best Regards,
Martin Wilke (miwi_(at)_FreeBSD.org)


  Mess with the Best, Die like the Rest


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZPwxhAAoJEB8/xmUxOhJnZJUIALs4qjZNpW5uCwNh1UgqsoHz
a6xhX+yqGD0AjVMs/tbQIjL13B+ObRmd8SOSAqv67VWipLcUTRHCteeHO1f3jjNA
aGwKlyfRahU/6eeUdbFasq1vqmel4VUWsN69XH3CuDncmYzop/WGJitSF3Qta9S5
e4rcBLiO2WKyuXUfTTyLt6KjBOLCVLkbaBdQvem3vfHK13MVElbIk5Va86coTuKN
oM0ZDoQk7b7GQmPN4fTKJmjmNxxej8Hb0yfg5qlorVxpJeG5ejg5t6UY4yfP0yxF
5JX3ZY/l4b8sobsmjo3Na2vyA9JEsemDJGwjHzvi3GEdEUsBHCenNipC8dfdrOY=
=ftZX
-END PGP SIGNATURE-
___
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: Audacity program appears to be dead

2017-06-12 Thread Kevin Oberman 
On Mon, Jun 12, 2017 at 12:53 AM, Andrew Johnson 
wrote:

> Thanks  Kevin, unfortunately I only got around to emailing the
> maintainer on Saturday. I would have emailed him a week ago but an
> older issue with shotcut & kdenlive already had me trying port updates
> (which is when audacity stopped working) and repeatedly checking the
> system's sanity and in desperation rebuilding the entire ports tree to
> ensure there were no hidden legacy issues.
>
> Thanks Lars, the update for wxgtk30 sounds promising but it'll be
> another 24hr before I get the update and can test the downstream apps.
>
>  :)
>
> On Sun, 2017-06-11 at 09:07 -0700, Kevin Oberman wrote:
> > On Sun, Jun 11, 2017 at 12:21 AM, Andrew Johnson
> >  wrote:
> > > It builds nicely but Audacity has ceased working and produces the
> > > following message:
> > > % audacity
> > > Fatal Error: Mismatch between the program and library build
> > > versions
> > > detected.
> > > The library used 3.0 (wchar_t,compiler with C++ ABI 1002,wx
> > > containers,compatible with 2.6,compatible with 2.8),
> > > and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx
> > > containers,compatible with 2.6,compatible with 2.8).
> > > Abort (core dumped)
> > >
> > > == It is possible that this began with my first update that
> > > included an edit in audacity/Makefile that was done back on
> > > 1/April.
> > I see the same error. I have nor run it is a while, so I have no idea
> > when it started.
> >
> > Have you notified the maintainer? That and opening a  bug report
> > should be your first actions. You can find the maintainer (if any) by
> > running "make maintainer" in the port's directory. In this case the
> > maintainer is xxjack1...@gmail.com. A bug report can be filed at
> > https://bugs.freebsd.org/bugzilla/.
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer


>From the discussion on bsdforen.de, it looks like this is, at best, a
workaround. (My German is very bad, so I may not understand the issue
properly.)

Since audacity is the only port I have installed that depends on wx30-gtk2,
it works for me.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Looking for good sould with a commit bit

2017-06-12 Thread Łukasz Wąsikowski 
I'm looking for someone with a commit bit to look at

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208147 - new port
[sysutils/modman]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219825 - maintainer
approves [security/rkhunter]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219726 - maintainer
update [www/mod_mpm_itk]

Thank you!

-- 
best regards,
Lukasz Wasikowski
___
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: lang/rust: build problems after r443109

2017-06-12 Thread Thomas Zander 
On Mon, Jun 12, 2017 at 08:58:30AM +0200, Rainer Hurling wrote:

> [patch]

Thank you!
Test building right now ...

Riggs
___
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: wget 1.19 missed IRI supporting

2017-06-12 Thread Vasil Dimov 
On Tue, Jun 06, 2017 at 14:03:01 -0400, Matthew Seaman wrote:
> On 06/06/2017 10:37, Cos Chan wrote:
> > I got mistake while running this command:
> > 
> > wget --no-verbose --remote-encoding=UTF-8 --local-encoding=UTF-8 --mirror
> > --directory-prefix=/foo/ --no-parent --no-host-directories --cut-dirs=2
> > --force-directories --accept=*.pdf --restrict-file-names=nocontrol
> > http://bar/Documents/
> > 
> > the mistake is : This version does not have support for IRIs
> > 
> > the wget version is:
> > 
> > $ wget --version
> > GNU Wget 1.19 built on freebsd11.0.
> > 
> > -cares +digest -gpgme +https +ipv6 -iri +large-file -metalink +nls
> > +ntlm +opie -psl +ssl/openssl
> > 
> > Wgetrc:
> > /usr/local/etc/wgetrc (system)
> > Locale:
> > /usr/local/share/locale
> > Compile:
> > clang -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/usr/local/etc/wgetrc"
> > -DLOCALEDIR="/usr/local/share/locale" -I. -I../lib -I../lib
> > -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG
> > -D_THREAD_SAFE -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector
> > -fno-strict-aliasing
> > Link:
> > clang -DNDEBUG -O2 -pipe -DLIBICONV_PLUG -fstack-protector
> > -fno-strict-aliasing -L/usr/local/lib -L/usr/local/lib
> > -Wl,-rpath,/usr/local/lib -fstack-protector
> > /usr/local/lib/libssl.so /usr/local/lib/libcrypto.so -Wl,-rpath
> > -Wl,/usr/local/lib -lz ftp-opie.o openssl.o http-ntlm.o
> > ../lib/libgnu.a -L/usr/local/lib -lintl -Wl,-rpath=/usr/local/lib
> > 
> > This issue was not happened in previous versions. Could anyone add back IRI
> > supporting to V1.19 binary package?
> 
> Hi,
> 
> freebsd-ports@ is a better mailing list to ask this question on.
> 
> IRI support should be enabled in the default wget package build.  It
> looks like IDN support was broken in 1.19 but fixed in 1.19.1 according
> to this commit:
> 
> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2102070+0+/usr/local/www/mailindex/archive/2017/svn-ports-head/20170409.svn-ports-head
> 
> Unfortunately it looks like that has only been applied to the HEAD
> branch of the ports tree, but not the 2017Q2 branch, and it is the
> 2017Q2 branch which is where the default packages are built from at the
> moment.
> 
> I've CC'd the ports maintainer to see if he'd consider a MFH of r437857.
>  That should be permitted under the rules, as it's fixing broken
> functionality.
[...]

Hello,

As per
https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-misc-request-mfh
I am requesting approval to merge r437857 from head to 2017Q2.

-- 
Vasil Dimov
gro.DSBeerF@dv
%
LOVE:
When, if asked to choose between your lover
and happiness, you'd skip happiness in a heartbeat.


signature.asc
Description: PGP signature

svnup is b0rken!

2017-06-12 Thread Maxim Sobolev 
Hi, latest version of the svnup package is broken on several of my boxes.
I've tried few public svn mirrors makes no difference.

-Max

[sobomax@van01 ~/projects/softswitch]$ svnup ports
# Revision: 443456

Command Failure: HTTP/1.1 400 Bad Request
Date: Mon, 12 Jun 2017 18:01:09 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=iso-8859-1



400 Bad Request

Bad Request
Your browser sent a request that this server could not understand.


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

Re: Looking for python-pecan

2017-06-12 Thread Dimitry Andric 
On 12 Jun 2017, at 13:29, Willem Jan Withagen  wrote:
> 
> For one the Ceph port I'm doing I'm going to need python-pecan in het
> close future.
> 
> Not sure how this works with python-modules since it is something that
> is only used by the ceph-ports. But my guess is that I won't be
> able/allowed to just have a post execute like:
> 
>   ping install python-pecan.

Normally you would use pip, ping is something entirely different. :)

Here is a patch to add a devel/py-pecan port, plus one of its
dependencies that is not yet in the ports tree, devel/py-logutils.

Tested only very lightly, please take care.

-Dimitry


add-devel_py-pecan-and-deps.diff
Description: Binary data


signature.asc
Description: Message signed with OpenPGP

Looking for python-pecan

2017-06-12 Thread Willem Jan Withagen 
Hi,

For one the Ceph port I'm doing I'm going to need python-pecan in het
close future.

Not sure how this works with python-modules since it is something that
is only used by the ceph-ports. But my guess is that I won't be
able/allowed to just have a post execute like:

ping install python-pecan.

Suggestions...

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

FreeBSD ports you maintain which are out of date

2017-06-12 Thread portscout 
Dear port maintainer,

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

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

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


Port| Current version | New version
+-+
editors/latexila| 3.22.1  | 3.24.1
+-+
lang/micropython| 1.5.1   | v1.9.1
+-+
multimedia/vdr  | 1.7.29  | 2.3.7
+-+
net/ladvd   | 1.1.0   | v1.1.1
+-+


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

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

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"

Reminder: MFH build/checksum fixes to quarterly

2017-06-12 Thread Johannes Jost Meixner 
Please remember to ensure that build fixes get merged from head into
quarterly branches (currently 2017Q2).

If you're reporting bugs, make sure to set the merge-quarterly flag to
at least ?.

The committer's guide has the relevant information in section 19.6 on
how to go about MFH'ing.

https://www.freebsd.org/doc/en/articles/committers-guide/article.html#ports-qa-quarterly



signature.asc
Description: OpenPGP digital signature

Re: Audacity program appears to be dead

2017-06-12 Thread Andrew Johnson 
Thanks  Kevin, unfortunately I only got around to emailing the
maintainer on Saturday. I would have emailed him a week ago but an
older issue with shotcut & kdenlive already had me trying port updates
(which is when audacity stopped working) and repeatedly checking the
system's sanity and in desperation rebuilding the entire ports tree to
ensure there were no hidden legacy issues.

Thanks Lars, the update for wxgtk30 sounds promising but it'll be
another 24hr before I get the update and can test the downstream apps. 

 :)

On Sun, 2017-06-11 at 09:07 -0700, Kevin Oberman wrote:
> On Sun, Jun 11, 2017 at 12:21 AM, Andrew Johnson
>  wrote:
> > It builds nicely but Audacity has ceased working and produces the
> > following message:
> > % audacity
> > Fatal Error: Mismatch between the program and library build
> > versions
> > detected.
> > The library used 3.0 (wchar_t,compiler with C++ ABI 1002,wx
> > containers,compatible with 2.6,compatible with 2.8),
> > and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx
> > containers,compatible with 2.6,compatible with 2.8).
> > Abort (core dumped)
> > 
> > == It is possible that this began with my first update that
> > included an edit in audacity/Makefile that was done back on
> > 1/April.
> I see the same error. I have nor run it is a while, so I have no idea
> when it started.
> 
> Have you notified the maintainer? That and opening a  bug report
> should be your first actions. You can find the maintainer (if any) by
> running "make maintainer" in the port's directory. In this case the
> maintainer is xxjack1...@gmail.com. A bug report can be filed at
> https://bugs.freebsd.org/bugzilla/.
> --
> Kevin Oberman, Part time kid herder and retired 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: lang/rust: build problems after r443109

2017-06-12 Thread Jean-Sébastien Pédron 
On 12.06.2017 08:58, Rainer Hurling wrote:
> When I try to update from rust-1.17.0 to 1.18.0, I get the following
> breakage:

Hi!

Yes, this is a known issue and a patch is pending review [1]. I'm still
under mentorship so I can't commit it without the approval of one of my
mentors.

Thank you for the report and the patch!

[1] https://reviews.freebsd.org/D10857

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

lang/rust: build problems after r443109

2017-06-12 Thread Rainer Hurling 
When I try to update from rust-1.17.0 to 1.18.0, I get the following 
breakage:


#make
===>  License APACHE20  MIT accepted by the user
===>   rust-1.18.0 depends on file: /usr/local/sbin/pkg - found
=> rustc-1.18.0-src.tar.gz doesn't seem to exist in 
/usr/ports/distfiles/rust.
=> Attempting to fetch 
http://static.rust-lang.org/dist/rustc-1.18.0-src.tar.gz
rustc-1.18.0-src.tar.gz   100% of   31 MB   31 MBps 
00m01s
=> 2017-04-27/rustc-1.17.0-x86_64-unknown-freebsd.tar.gz doesn't seem to 
exist in /usr/ports/distfiles/rust.
=> Attempting to fetch 
https://static.rust-lang.org/dist/2017-04-27/rustc-1.17.0-x86_64-unknown-freebsd.tar.gz
2017-04-27/rustc-1.17.0-x86_64-unknown-freebsd100% of   39 MB   33 MBps 
00m01s
=> 2017-04-27/rust-std-1.17.0-x86_64-unknown-freebsd.tar.gz doesn't seem 
to exist in /usr/ports/distfiles/rust.
=> Attempting to fetch 
https://static.rust-lang.org/dist/2017-04-27/rust-std-1.17.0-x86_64-unknown-freebsd.tar.gz
2017-04-27/rust-std-1.17.0-x86_64-unknown-free100% of   53 MB   36 MBps 
00m01s
=> 2017-04-27/cargo-0.18.0-x86_64-unknown-freebsd.tar.gz doesn't seem to 
exist in /usr/ports/distfiles/rust.
=> Attempting to fetch 
https://static.rust-lang.org/dist/2017-04-27/cargo-0.18.0-x86_64-unknown-freebsd.tar.gz
2017-04-27/cargo-0.18.0-x86_64-unknown-freebsd100% of 4921 kB   18 MBps 
00m00s
=> rust-registry-1.18.0.tar.xz doesn't seem to exist in 
/usr/ports/distfiles/rust.
=> Attempting to fetch 
http://distcache.FreeBSD.org/local-distfiles/riggs/rust/rust-registry-1.18.0.tar.xz
rust-registry-1.18.0.tar.xz   100% of 7534 kB 5562 kBps 
00m01s

===> Fetching all distfiles required by rust-1.18.0 for building
===>  Extracting for rust-1.18.0
=> SHA256 Checksum OK for rust/rustc-1.18.0-src.tar.gz.
=> SHA256 Checksum OK for 
rust/2017-04-27/rustc-1.17.0-x86_64-unknown-freebsd.tar.gz.
=> SHA256 Checksum OK for 
rust/2017-04-27/rust-std-1.17.0-x86_64-unknown-freebsd.tar.gz.
=> SHA256 Checksum OK for 
rust/2017-04-27/cargo-0.18.0-x86_64-unknown-freebsd.tar.gz.

=> SHA256 Checksum OK for rust/rust-registry-1.18.0.tar.xz.
/bin/ln -sf 
/usr/ports/distfiles/rust/2017-04-27/rustc-1.17.0-x86_64-unknown-freebsd.tar.gz 
 /usr/ports/lang/rust/work/rustc-1.18.0-src/build/cache/2017-04-27
/bin/ln -sf 
/usr/ports/distfiles/rust/2017-04-27/cargo-0.18.0-x86_64-unknown-freebsd.tar.gz 
 /usr/ports/lang/rust/work/rustc-1.18.0-src/build/cache/2017-04-27
/usr/bin/tar -x -C /usr/ports/lang/rust/work/rustc-1.18.0-src -f 
/usr/ports/distfiles/rust/2017-04-27/rust-std-1.17.0-x86_64-unknown-freebsd.tar.gz
cc -O2 -pipe  -fstack-protector -isystem /usr/local/include 
-fno-strict-aliasing -fPIC -c -o 
/usr/ports/lang/rust/work/rustc-1.18.0-src/old_fstat.o 
/usr/ports/lang/rust/files/old_fstat.c
(cd /usr/ports/lang/rust/work/rustc-1.18.0-src && ar x 
/usr/ports/lang/rust/work/rustc-1.18.0-src/rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd/lib/libstd-aef6cb139bd07bdc.rlib 
std-aef6cb139bd07bdc.0.o)
ar: fatal: Failed to open 
'/usr/ports/lang/rust/work/rustc-1.18.0-src/rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd/lib/libstd-aef6cb139bd07bdc.rlib'

*** Error code 70
Stop.
make[1]: stopped in /usr/ports/lang/rust
*** Error code 1


It seems, the some strings in Makefile have not been updated 
accordingly. The following patch solves this for me:



#diff -urN Makefile.orig Makefile
--- Makefile.orig   2017-06-12 07:28:00.0 +0200
+++ Makefile2017-06-12 08:50:21.592902000 +0200
@@ -46,6 +46,7 @@

 RUST_BOOTSTRAP_DIR?=   2017-04-27
 RUST_BOOTSTRAP_VERSION?=   1.17.0
+RUST_BOOTSTRAP_HASH?=  f4594d3e53dcb114
 RUSTC_BOOTSTRAP=	 
${RUST_BOOTSTRAP_DIR}/rustc-${RUST_BOOTSTRAP_VERSION}-${RUST_TARGET}.tar.gz
 RUST_STD_BOOTSTRAP=	 
${RUST_BOOTSTRAP_DIR}/rust-std-${RUST_BOOTSTRAP_VERSION}-${RUST_TARGET}.tar.gz


@@ -135,8 +136,8 @@
exit 1;\
fi

-LIBSTD= 
rust-std-1.16.0-${RUST_ARCH_${ARCH}}-unknown-freebsd/rust-std-${RUST_ARCH_${ARCH}}-unknown-freebsd/lib/rustlib/${RUST_ARCH_${ARCH}}-unknown-freebsd/lib/libstd-aef6cb139bd07bdc.rlib

-STDF=  std-aef6cb139bd07bdc.0.o
+LIBSTD= 
rust-std-${RUST_BOOTSTRAP_VERSION}-${RUST_ARCH_${ARCH}}-unknown-freebsd/rust-std-${RUST_ARCH_${ARCH}}-unknown-freebsd/lib/rustlib/${RUST_ARCH_${ARCH}}-unknown-freebsd/lib/libstd-${RUST_BOOTSTRAP_HASH}.rlib

+STDF=  std-${RUST_BOOTSTRAP_HASH}.0.o

 post-extract:
@${MKDIR} \
@@ -157,7 +158,7 @@
${LD} -r -o ${WRKSRC}/std.xx.o ${WRKSRC}/${STDF} ${WRKSRC}/old_fstat.o
${MV} ${WRKSRC}/std.xx.o ${WRKSRC}/${STDF}
(cd ${WRKSRC} && ${AR} r ${WRKSRC}/${LIBSTD} ${STDF})
-	${TAR} -cy -C ${WRKSRC} -f ${WRKSRC}/rustc.tbz 
rust-std-1.16.0-${RUST_ARCH_${ARCH}}-unknown-freebsd
+	${TAR} -cy -C ${WRKSRC} -f ${WRKSRC}/rustc.tbz 
rust-std-${RUST_BOOTSTRAP_VERSION}-${RUST_ARCH_${ARCH}}-unknown-freebsd

${MV} ${WRKSRC}/rustc.tbz

Re: Audacity program appears to be dead

2017-06-12 Thread Lars Engels 
On Sun, Jun 11, 2017 at 09:07:39AM -0700, Kevin Oberman wrote:
> On Sun, Jun 11, 2017 at 12:21 AM, Andrew Johnson 
> wrote:
> 
> > It builds nicely but Audacity has ceased working and produces the
> > following message:
> >
> > % audacity
> > Fatal Error: Mismatch between the program and library build versions
> > detected.
> > The library used 3.0 (wchar_t,compiler with C++ ABI 1002,wx
> > containers,compatible with 2.6,compatible with 2.8),
> > and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx
> > containers,compatible with 2.6,compatible with 2.8).
> > Abort (core dumped)
> >
> >
> > == It is possible that this began with my first update that included an
> > edit in audacity/Makefile that was done back on 1/April.
> >
> > There's been a couple more updates in audacity during the past week but
> > the program continues to die with the same Fatal Error message.
> >
> > FreeBSD 10.3-STABLE FreeBSD 10.3-STABLE Sun Jun  4 18:11:09 2017
> > GENERIC  amd64
> >
> 
> I see the same error. I have nor run it is a while, so I have no idea when
> it started.
> 
> Have you notified the maintainer? That and opening a  bug report should be
> your first actions. You can find the maintainer (if any) by running "make
> maintainer" in the port's directory. In this case the maintainer is
> xxjack1...@gmail.com. A bug report can be filed at
> https://bugs.freebsd.org/bugzilla/.

See
http://www.bsdforen.de/threads/audacity-abi-fehler.33577/#post-292112
for a workaround / solution.


pgpTjJ2RqNACf.pgp
Description: PGP signature