Re: Please test geodns.portsnap.freebsd.org
2012-05-12 05:54, Colin Percival skrev: Hi all, Please test: # portsnap fetch -s geodns.portsnap.freebsd.org If you experience any problems, please let me know where you are, which mirror was selected, and what address `host -t a $mirror` returns for it. (As the name suggests, different people should will get different mirrors.) I get portsnap fetch -s geodns.portsnap.freebsd.org Looking up geodns.portsnap.freebsd.org mirrors... none found. Fetching snapshot tag from geodns.portsnap.freebsd.org... failed. No mirrors remaining, giving up. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
On 05/12/12 00:02, Leslie Jensen wrote: > portsnap fetch -s geodns.portsnap.freebsd.org > Looking up geodns.portsnap.freebsd.org mirrors... none found. > Fetching snapshot tag from geodns.portsnap.freebsd.org... failed. > No mirrors remaining, giving up. Hmm, that's not good. What do # host -t srv _http._tcp.geodns.portsnap.freebsd.org and # portsnap fetch -s portsnap.freebsd.org give you? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
2012-05-12 09:04, Colin Percival skrev: On 05/12/12 00:02, Leslie Jensen wrote: portsnap fetch -s geodns.portsnap.freebsd.org Looking up geodns.portsnap.freebsd.org mirrors... none found. Fetching snapshot tag from geodns.portsnap.freebsd.org... failed. No mirrors remaining, giving up. Hmm, that's not good. What do # host -t srv _http._tcp.geodns.portsnap.freebsd.org and # portsnap fetch -s portsnap.freebsd.org give you? host -t srv _http._tcp.geodns.portsnap.freebsd.org ;; Truncated, retrying in TCP mode. ;; Connection to 172.17.0.1#53(172.17.0.1) for _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. portsnap fetch -s portsnap.freebsd.org Looking up portsnap.freebsd.org mirrors... 4 mirrors found. Fetching snapshot tag from portsnap5.freebsd.org... done. Latest snapshot on server matches what we already have. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
Rainer Hurling wrote: >>> Can't locate XML/SAX/Exception.pm in @INC (@INC contains: >>> /usr/local/lib/perl5/5.14.2/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.14.2/mach >>> /usr/local/lib/perl5/site_perl/5.14.2 /usr/local/lib/perl5/5.14.2/mach >>> /usr/local/lib/perl5/5.14.2 .) at >>> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. >>> Compilation failed in require at >>> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. >>> Compilation failed in require. >>> BEGIN failed--compilation aborted. >>> *** [install_sax_pureperl] Error code 2 >>> Stop in /usr/ports/textproc/p5-XML-SAX/work/XML-SAX-0.99. >>> *** [do-install] Error code 1 >>> Stop in /usr/ports/textproc/p5-XML-SAX. >>> ===>>> A backup package for p5-XML-SAX-0.96 should >>> be located in /usr/ports/packages/portmaster-backup >>> ===>>> Installation of p5-XML-SAX-0.99 (textproc/p5-XML-SAX) failed >>> ===>>> Aborting update >>> Terminated >>> ===>>> You can restart from the point of failure with this command line: >>> portmaster textproc/p5-XML-SAX >>> >>> >>> It seems that ParserFactory.pm (line 12) wants to use >>> XML::SAX::Exception, but there is no ParserDetails anymore (just deleted >>> before ...). >>> >>> This happens on several boxes with recent 10.0-CURRENT (amd64). Does >>> anyone else see this behaviour? >> >> >> installation of textproc/p5-XML-SAX-Base helped me > > Thanks for answering. It does not help, because > textproc/p5-XML-SAX-Base is already installed :-( Mee too! p5-XML-SAX-Base is there but p5-XML-SA fails. :( Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
Andriy Gapon wrote: >> >> Any help is appreciated. > > I think that p5-XML-SAX-Base has to be removed before installing (maybe even > building) p5-XML-SAX-0.99. does not work. :( Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
On 05/12/12 00:22, Leslie Jensen wrote: > host -t srv _http._tcp.geodns.portsnap.freebsd.org > ;; Truncated, retrying in TCP mode. > ;; Connection to 172.17.0.1#53(172.17.0.1) for > _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. Ok, you have a broken recursive DNS server configuration. I'll have A records as a fallback for situations like this where SRV can't be used. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
On 12.05.2012 10:09 (UTC+1), Heino Tiedemann wrote: Rainer Hurling wrote: Can't locate XML/SAX/Exception.pm in @INC (@INC contains: /usr/local/lib/perl5/5.14.2/BSDPAN /usr/local/lib/perl5/site_perl/5.14.2/mach /usr/local/lib/perl5/site_perl/5.14.2 /usr/local/lib/perl5/5.14.2/mach /usr/local/lib/perl5/5.14.2 .) at /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. Compilation failed in require. BEGIN failed--compilation aborted. *** [install_sax_pureperl] Error code 2 Stop in /usr/ports/textproc/p5-XML-SAX/work/XML-SAX-0.99. *** [do-install] Error code 1 Stop in /usr/ports/textproc/p5-XML-SAX. ===>>> A backup package for p5-XML-SAX-0.96 should be located in /usr/ports/packages/portmaster-backup ===>>> Installation of p5-XML-SAX-0.99 (textproc/p5-XML-SAX) failed ===>>> Aborting update Terminated ===>>> You can restart from the point of failure with this command line: portmaster textproc/p5-XML-SAX It seems that ParserFactory.pm (line 12) wants to use XML::SAX::Exception, but there is no ParserDetails anymore (just deleted before ...). This happens on several boxes with recent 10.0-CURRENT (amd64). Does anyone else see this behaviour? installation of textproc/p5-XML-SAX-Base helped me Thanks for answering. It does not help, because textproc/p5-XML-SAX-Base is already installed :-( Mee too! p5-XML-SAX-Base is there but p5-XML-SA fails. On 09.05.2012 11:19 I posted in a branch of this thread: Deinstalling textproc/p5-XML-SAX, reinstalling textproc/p5-XML-SAX-Base and then installing textproc/p5-XML-SAX again, fixes it for me. Hope, this helps, Rainer :( Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
Heino Tiedemann wrote: > Andriy Gapon wrote: > >>> >>> Any help is appreciated. >> >> I think that p5-XML-SAX-Base has to be removed before installing (maybe even >> building) p5-XML-SAX-0.99. > > does not work. :( it woks with cd /usr/ports/textproc/p5-XML-SAX make deinstall cd ../p5-XML-SAX-Base make deinstall make make install cd ../p5-XML-SAX make install No idea why, but portupgrade und pkg_deinstall was not he right way... thanks to Kurt! Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
2012-05-12 12:34, Colin Percival skrev: On 05/12/12 00:22, Leslie Jensen wrote: host -t srv _http._tcp.geodns.portsnap.freebsd.org ;; Truncated, retrying in TCP mode. ;; Connection to 172.17.0.1#53(172.17.0.1) for _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. Ok, you have a broken recursive DNS server configuration. I'll have A records as a fallback for situations like this where SRV can't be used. What exactly does that mean? The IP-address is my home router that acts as a caching DNS for my network. The router in turn uses my ISP's DNS. So if there is a configuration issue I'll be willing to drop a letter to my ISP in order to get it fixed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Patch for JBoss5 to make it buildable again (Maven/JBoss Repositories Problem)
Hi Jonathan, as portmaintainer could you please change the actual /usr/ports/jboss5/files/patch-pom-xml with this one patch-pom-xml Description: Binary data i change all repositories to the actual valid ones, the actual patch contains glassfish repo which responds with garbage... and jboss5 is not buildable with the actual patch tested it: on 8.2-RELEASE-p6 amd64 thanx in advance br horst PS if urgent for somebody change the /usr/ports/jboss5/files/patch-pom-xml with the attached one; nothing else todo___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] New framework options aka optionng
On Sat, May 12, 2012 at 08:34:37AM +0200, Alex Dupre wrote: > Erwin Lansing ha scritto: > > portmgr has been working for long on a new option framework for the ports > > to improve some of the deficiencies in the current framework. > > Great work! Looking quickly at the documentation I have a doubt: while I > think most ports handle NOPORTDOCS, I think WITHOUT_NLS is handled only > by a small percentage, so, if I have understood correctly, many ports > should include OPTIONS_EXCLUDE=NLS. Is it correct? You are right the documentation is not clear concerning that point. In this implementation option is enforced at all, only default value are set by the bsd.options.mk which are DOCS and NLS. crees can you fix that part of the doc? the infomation I sent to you first weren't clear about it, sorry. So currently DOCS and NLS are set on if they are defined by the maintainer and only if they are defined by the maintainer. So no change expected at all from the current defaults. Bapt pgpXuloZgQ0nO.pgp Description: PGP signature
portupgrade-devel / WITH_PKGNG
On 5/12/2012 9:44 AM, Michael C Voorhis wrote: > > This morning's new portupgrade-devel *appears* to define WITH_PKGNG in > spite of its not being in /etc/make.conf. Many portupgrades this > morning are hanging at the pkgdb update, with the process list showing: > > root 32920 0.0 0.0 3200 616 0 SN+ 9:33AM 0:00.01 make -V > WITH_PKGNG > root 33169 0.0 0.0 3200 692 0 SN+ 9:33AM 0:00.01 make -V > _JAVA_PORTS_INSTALLED USE_JAVA=1 -f /usr/ports/Mk/bsd.port.mk > > This process which used to take seconds is now taking many minutes. Yeah I'm seeing that too. Will look into it and get an updated snapshot out soon. Regards, Bryan Drewery -bsdcan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade-devel / WITH_PKGNG
> On 5/12/2012 9:44 AM, Michael C Voorhis wrote:
>>
>> This morning's new portupgrade-devel *appears* to define WITH_PKGNG in
>> spite of its not being in /etc/make.conf. Many portupgrades this
>> morning are hanging at the pkgdb update, with the process list showing:
>>
>> root 32920 0.0 0.0 3200 616 0 SN+ 9:33AM 0:00.01 make -V
>> WITH_PKGNG
>> root 33169 0.0 0.0 3200 692 0 SN+ 9:33AM 0:00.01 make -V
>> _JAVA_PORTS_INSTALLED USE_JAVA=1 -f /usr/ports/Mk/bsd.port.mk
>>
>> This process which used to take seconds is now taking many minutes.
>
The problem is that it's just going to take a *long time*.
Submitting a PR to update the port snapshot.
Thanks for the report!
This patch fixes in the meantime. Apply to your
/usr/local/lib/ruby/1.8/site_ruby/pkgtools/pkgdb.rb:
--- a/lib/pkgtools/pkgdb.rb
+++ b/lib/pkgtools/pkgdb.rb
@@ -105,6 +105,7 @@ class NeedsPkgNGSupport < StandardError
def with_pkgng?
if @with_pkgng.nil?
@with_pkgng = $portsdb.make_var('WITH_PKGNG')
+ @with_pkgng = false unless @with_pkgng
STDERR.puts "USING PKGNG" if @with_pkgng
end
@with_pkgng
signature.asc
Description: OpenPGP digital signature
Re: Please test geodns.portsnap.freebsd.org
On 05/12/12 05:16, Leslie Jensen wrote: > 2012-05-12 12:34, Colin Percival skrev: >> On 05/12/12 00:22, Leslie Jensen wrote: >>> host -t srv _http._tcp.geodns.portsnap.freebsd.org >>> ;; Truncated, retrying in TCP mode. >>> ;; Connection to 172.17.0.1#53(172.17.0.1) for >>> _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. >> >> Ok, you have a broken recursive DNS server configuration. >> >> I'll have A records as a fallback for situations like this where SRV can't be >> used. > > What exactly does that mean? The IP-address is my home router that acts as a > caching DNS for my network. The router in turn uses my ISP's DNS. > > So if there is a configuration issue I'll be willing to drop a letter to my > ISP > in order to get it fixed. It's your router. DNS is designed that you can fall back from UDP to TCP if the response is too big tosend in a UDP packet, but your router seems to not provide the fallback TCP service. This is sadly a common mis-design, but usually doesn't cause a huge problem since most DNS responses fit into a UDP packet. The A fallback will point you at the closest portsnap mirror, but you won't get the fail-over behaviour where portsnap will switch mirrors if the first one isn't responding. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: postgis-1.5.3_2
Just wondering when/if postgis-2.0 will make it to the FreeBSD ports tree: I'm starting a new project, and it looks easier to work with than 1.5. If it's likely to be soon, I can put off that section of the project until it makes it. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
On Sat, 12 May 2012 14:16:58 +0200 Leslie Jensen wrote: > > > 2012-05-12 12:34, Colin Percival skrev: > > On 05/12/12 00:22, Leslie Jensen wrote: > >> host -t srv _http._tcp.geodns.portsnap.freebsd.org > >> ;; Truncated, retrying in TCP mode. > >> ;; Connection to 172.17.0.1#53(172.17.0.1) for > >> _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. > > > > Ok, you have a broken recursive DNS server configuration. > > > > I'll have A records as a fallback for situations like this where > > SRV can't be used. > > > > What exactly does that mean? The IP-address is my home router that > acts as a caching DNS for my network. The router in turn uses my > ISP's DNS. > > So if there is a configuration issue I'll be willing to drop a letter > to my ISP in order to get it fixed. Probably your router doesn't support SRV records, try putting external servers in resolv.conf. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portsnap.FreeBSD.org is now geodns-enabled
Hi all,
The portsnap.FreeBSD.org SRV records now point at the magic geodns endpoints,
so users outside of North America will probably end up using a mirror in one
of {Ireland, Tokyo, Singapore, Sao Paulo}. Please let me know if you run into
any problems.
I will be writing a blog post about this in the upcoming days, so please don't
ask me to provide all the details right now. :-)
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
2012-05-12 16:19, RW skrev: On Sat, 12 May 2012 14:16:58 +0200 Leslie Jensen wrote: 2012-05-12 12:34, Colin Percival skrev: On 05/12/12 00:22, Leslie Jensen wrote: host -t srv _http._tcp.geodns.portsnap.freebsd.org ;; Truncated, retrying in TCP mode. ;; Connection to 172.17.0.1#53(172.17.0.1) for _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. Ok, you have a broken recursive DNS server configuration. I'll have A records as a fallback for situations like this where SRV can't be used. What exactly does that mean? The IP-address is my home router that acts as a caching DNS for my network. The router in turn uses my ISP's DNS. So if there is a configuration issue I'll be willing to drop a letter to my ISP in order to get it fixed. Probably your router doesn't support SRV records, try putting external servers in resolv.conf. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Well I had to read up on configuring dhclient.conf After adding prepend domain-name-servers y.y.y.y, x.x.x.x; To my /etc/dhclient.conf I now get the following and it looks to me as it works :-) host -t srv _http._tcp.geodns.portsnap.freebsd.org ;; Truncated, retrying in TCP mode. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 ap-southeast-1.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 1 10 80 geodns-1.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 2 10 80 geodns-2.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 3 10 80 geodns-3.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 isc.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 your-org.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 ec2-eu-west-1.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 ec2-sa-east-1.portsnap.freebsd.org. _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 ap-northeast-1.portsnap.freebsd.org. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
On Sat, May 12, 2012 at 5:08 AM, Heino Tiedemann wrote: > Heino Tiedemann wrote: > >> Andriy Gapon wrote: >> Any help is appreciated. >>> >>> I think that p5-XML-SAX-Base has to be removed before installing (maybe even >>> building) p5-XML-SAX-0.99. >> >> does not work. :( > > it woks with > > cd /usr/ports/textproc/p5-XML-SAX > make deinstall > cd ../p5-XML-SAX-Base > make deinstall > make > make install > cd ../p5-XML-SAX > make install > > > No idea why, but portupgrade und pkg_deinstall was not he right way... > > thanks to Kurt! The Exception.pm file was moved from p5-XML-SAX to the new p5-XML-SAX-Base port. Since p5-XML-SAX-Base is a dependency of p5-XML-SAX, it gets installed first and it installs Exception.pm over the existing copy that was previously installed by p5-XML-SAX. Then it updates p5-XML-SAX and, since p5-XML-SAX has Exception.pm in its pkg_plist, it deletes the file.Note that the error is during the 'install' operation, not the 'build'. The 'right' answer that there should have been a note in UPDATING that warns that you need to: pkg_delete p5-XML-SAX-0\* portmaster textproc/p5-XML-SAX-Base textproc/p5-XML-SAX (with similar command for portupgrade). -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
On 12 May 2012 16:59, Kevin Oberman wrote: > On Sat, May 12, 2012 at 5:08 AM, Heino Tiedemann > wrote: >> Heino Tiedemann wrote: >> >>> Andriy Gapon wrote: >>> > > Any help is appreciated. I think that p5-XML-SAX-Base has to be removed before installing (maybe even building) p5-XML-SAX-0.99. >>> >>> does not work. :( >> >> it woks with >> >> cd /usr/ports/textproc/p5-XML-SAX >> make deinstall >> cd ../p5-XML-SAX-Base >> make deinstall >> make >> make install >> cd ../p5-XML-SAX >> make install >> >> >> No idea why, but portupgrade und pkg_deinstall was not he right way... >> >> thanks to Kurt! > > The Exception.pm file was moved from p5-XML-SAX to the new > p5-XML-SAX-Base port. Since p5-XML-SAX-Base is a dependency of > p5-XML-SAX, it gets installed first and it installs Exception.pm over > the existing copy that was previously installed by p5-XML-SAX. Then it > updates p5-XML-SAX and, since p5-XML-SAX has Exception.pm in its > pkg_plist, it deletes the file.Note that the error is during the > 'install' operation, not the 'build'. > > The 'right' answer that there should have been a note in UPDATING that > warns that you need to: > pkg_delete p5-XML-SAX-0\* > portmaster textproc/p5-XML-SAX-Base textproc/p5-XML-SAX > (with similar command for portupgrade). Yup, I'm about to make such a note, and I've also registered a CONFLICT p5-XML-SAX-Base with p5-XML-SAX<0.99. Hopefully the error message will now be more informative :) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
On Sat, May 12, 2012 at 8:58 AM, Leslie Jensen wrote: > > > 2012-05-12 16:19, RW skrev: > >> On Sat, 12 May 2012 14:16:58 +0200 >> Leslie Jensen wrote: >> >>> >>> >>> 2012-05-12 12:34, Colin Percival skrev: On 05/12/12 00:22, Leslie Jensen wrote: > > host -t srv _http._tcp.geodns.portsnap.freebsd.org > ;; Truncated, retrying in TCP mode. > ;; Connection to 172.17.0.1#53(172.17.0.1) for > _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. Ok, you have a broken recursive DNS server configuration. I'll have A records as a fallback for situations like this where SRV can't be used. >>> >>> What exactly does that mean? The IP-address is my home router that >>> acts as a caching DNS for my network. The router in turn uses my >>> ISP's DNS. >>> >>> So if there is a configuration issue I'll be willing to drop a letter >>> to my ISP in order to get it fixed. >> >> >> Probably your router doesn't support SRV records, try putting external >> servers in resolv.conf. >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > Well I had to read up on configuring dhclient.conf > > After adding > > prepend domain-name-servers y.y.y.y, x.x.x.x; > > To my /etc/dhclient.conf > > I now get the following and it looks to me as it works :-) > > > > host -t srv _http._tcp.geodns.portsnap.freebsd.org > ;; Truncated, retrying in TCP mode. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ap-southeast-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 1 10 80 > geodns-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 2 10 80 > geodns-2.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 3 10 80 > geodns-3.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > isc.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > your-org.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ec2-eu-west-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ec2-sa-east-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ap-northeast-1.portsnap.freebsd.org. Warning! You will have more problems down the road. The real issue is that a firewall (or router ACL) is blocking port 53/tcp. This is distressingly common and will result in DNS issues more and more often. By default, DNS attempts to use UDP (53/udp) for DNS lookups. If the response is too big to fit into a UDP packet, the operation will fall back to using TCP, but many sites follow bad advice of blocking 53/tcp, so the lookup fails. This has been a growing problem as DNS responses are getting longer due to things like this, IPv6, and DNSSEC. Please contact whoever is responsible for your router/firewall and ask that 53/tcp be allowed. Otherwise, more and more things will break. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap.FreeBSD.org is now geodns-enabled
On Sat, May 12, 2012 at 07:44:25AM -0700, Colin Percival wrote:
> Hi all,
>
> The portsnap.FreeBSD.org SRV records now point at the magic geodns endpoints,
> so users outside of North America will probably end up using a mirror in one
> of {Ireland, Tokyo, Singapore, Sao Paulo}. Please let me know if you run into
> any problems.
Thank you.
>
> I will be writing a blog post about this in the upcoming days, so please don't
> ask me to provide all the details right now. :-)
And thank you again.
Nice work! now I can portsnap tarsnap really quick! ;)
--
- (2^(N-1))
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
problem running pkg_delete
Suddenly I'm getting: pkg_delete: the package info for package "Source" is corrupt Any ideas? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
El día Saturday, May 12, 2012 a las 02:24:16PM -0400, Robert Huff escribió: > > Suddenly I'm getting: > > pkg_delete: the package info for package "Source" is corrupt > > Any ideas? Check the content of /var/db/pkg/"Source" HIH matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On Sat, May 12, 2012 at 02:24:16PM -0400, Robert Huff wrote: > > Suddenly I'm getting: > > pkg_delete: the package info for package "Source" is corrupt > > Any ideas? > I would inspect the contents of the package directory in question. /var/db/pkg/Source/??? Does it differ from any of the other directories... If so rm -rf /var/db/pkg/Source and then reinstall the same version you had installed before and you should be fine to do whatever it is you are doing... There is not much info here... which leads to guessing. -- - (2^(N-1)) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On Sat, 12 May 2012 14:24:16 -0400 Robert Huff articulated: >pkg_delete: the package info for package "Source" is corrupt I had a similar experience about a year ago with a port I was trying to remove. I eventually did a force installation of the port and then deleted it normally. I have no idea if that would work for you or not. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ The Wright Brothers weren't the first to fly, they were just the first not to crash. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On 12 May 2012 20:58, Jerry wrote: > On Sat, 12 May 2012 14:24:16 -0400 > Robert Huff articulated: > >>pkg_delete: the package info for package "Source" is corrupt > > I had a similar experience about a year ago with a port I was trying to > remove. I eventually did a force installation of the port and then > deleted it normally. I have no idea if that would work for you or not. Almost certainly would help in this case, if /var/db/pkg/Source* were overwritten. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] New framework options aka optionng
On 12 May 2012 14:18, "Baptiste Daroussin" wrote: > > On Sat, May 12, 2012 at 08:34:37AM +0200, Alex Dupre wrote: > > Erwin Lansing ha scritto: > > > portmgr has been working for long on a new option framework for the ports to improve some of the deficiencies in the current framework. > > > > Great work! Looking quickly at the documentation I have a doubt: while I > > think most ports handle NOPORTDOCS, I think WITHOUT_NLS is handled only > > by a small percentage, so, if I have understood correctly, many ports > > should include OPTIONS_EXCLUDE=NLS. Is it correct? > > You are right the documentation is not clear concerning that point. > > In this implementation option is enforced at all, only default value are set by > the bsd.options.mk which are DOCS and NLS. > > crees can you fix that part of the doc? the infomation I sent to you first > weren't clear about it, sorry. > > So currently DOCS and NLS are set on if they are defined by the > maintainer and only if they are defined by the maintainer. > > So no change expected at all from the current defaults. > Done. I'll get the final references to WITH_ etc converted as soon as I can. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On Sat, 12 May 2012 14:24:16 -0400 Robert Huff wrote: > > Suddenly I'm getting: > > pkg_delete: the package info for package "Source" is corrupt > > Any ideas? Do you mean that you get that specific message, or that you are getting it for multiple packages and "Source" is a placeholder? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
RW writes: > > pkg_delete: the package info for package "Source" is corrupt > > Do you mean that you get that specific message, or that you are getting > it for multiple packages and "Source" is a placeholder? That specific message. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On 05/12/2012 01:24 PM, Robert Huff wrote: Suddenly I'm getting: pkg_delete: the package info for package "Source" is corrupt Any ideas? Is it possible that you created a directory by accident inside /var/db/pkg called "Source"? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On 05/12/2012 06:25 PM, Stephen Montgomery-Smith wrote: On 05/12/2012 01:24 PM, Robert Huff wrote: Suddenly I'm getting: pkg_delete: the package info for package "Source" is corrupt Any ideas? Is it possible that you created a directory by accident inside /var/db/pkg called "Source"? Also, I am trying to look through the source code in pkg_delete to see what could have created this message. As best as I can tell, this message must have been created by the function matchallbyorigin in /usr/src/usr.sbin/pkg_install/lib/match.c which was called by the function pkg_do in /usr/src/usr.sbin/pkg_install/delete/perform.c. The source code for pkg_do contains the disclaimer "This is seriously ugly code following. Written very fast!" Do you remember at all the command you typed that created this message? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
install py-matplotlib fails
Hello, I am trying to install the py-matplotlib but get this error:
BUILDING MATPLOTLIB
matplotlib: 1.0.1
python: 2.7.3 (default, May 12 2012, 17:36:49) [GCC 4.2.1
20070831 patched [FreeBSD]]
platform: freebsd9
REQUIRED DEPENDENCIES
numpy: no
* You must install numpy 1.1 or later to build
* matplotlib.
i have installed numpy
# pkg_version -v | grep py27-numpy
py27-numpy-1.6.1_1,1= up-to-date with port
but running python i get this traceback:
Python 2.7.3 (default, May 12 2012, 17:36:49)
[GCC 4.2.1 20070831 patched [FreeBSD]] on freebsd9
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/site-packages/numpy/__init__.py",
line 137, in
import add_newdocs
File "/usr/local/lib/python2.7/site-packages/numpy/add_newdocs.py",
line 9, in
from numpy.lib import add_newdoc
File "/usr/local/lib/python2.7/site-packages/numpy/lib/__init__.py",
line 13, in
from polynomial import *
File "/usr/local/lib/python2.7/site-packages/numpy/lib/polynomial.py",
line 17, in
from numpy.linalg import eigvals, lstsq
File "/usr/local/lib/python2.7/site-packages/numpy/linalg/__init__.py",
line 48, in
from linalg import *
File "/usr/local/lib/python2.7/site-packages/numpy/linalg/linalg.py",
line 23, in
from numpy.linalg import lapack_lite
ImportError: /usr/local/lib/libalapack.so.2: Undefined symbol "cblas_zswap"
i followed this thread
http://forums.freebsd.org/showthread.php?t=29085 but still no luck.
what am i missing?
thanks
--
%>>> "".join( [ {'*':'@','^':'.'}.get(c,None) or
chr(97+(ord(c)-83)%26) for c in ",adym,*)&uzq^zqf" ] )
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On Sat, May 12, 2012 at 06:31:44PM -0500, Stephen Montgomery-Smith wrote: > On 05/12/2012 06:25 PM, Stephen Montgomery-Smith wrote: > > On 05/12/2012 01:24 PM, Robert Huff wrote: > >> > >> Suddenly I'm getting: > >> > >> pkg_delete: the package info for package "Source" is corrupt > >> > >> Any ideas? > > > > Is it possible that you created a directory by accident inside > > /var/db/pkg called "Source"? > > Also, I am trying to look through the source code in pkg_delete to see > what could have created this message. As best as I can tell, this > message must have been created by the function matchallbyorigin in > /usr/src/usr.sbin/pkg_install/lib/match.c which was called by the > function pkg_do in /usr/src/usr.sbin/pkg_install/delete/perform.c. The > source code for pkg_do contains the disclaimer "This is seriously ugly > code following. Written very fast!" > > Do you remember at all the command you typed that created this message? > You would probably get the same message from: mkdir /var/db/pkg/Source pkg_delete Source Try it out! -- - (2^(N-1)) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
On 05/12/2012 08:06 PM, Jason Hellenthal wrote: On Sat, May 12, 2012 at 06:31:44PM -0500, Stephen Montgomery-Smith wrote: On 05/12/2012 06:25 PM, Stephen Montgomery-Smith wrote: On 05/12/2012 01:24 PM, Robert Huff wrote: Suddenly I'm getting: pkg_delete: the package info for package "Source" is corrupt Any ideas? Is it possible that you created a directory by accident inside /var/db/pkg called "Source"? Also, I am trying to look through the source code in pkg_delete to see what could have created this message. As best as I can tell, this message must have been created by the function matchallbyorigin in /usr/src/usr.sbin/pkg_install/lib/match.c which was called by the function pkg_do in /usr/src/usr.sbin/pkg_install/delete/perform.c. The source code for pkg_do contains the disclaimer "This is seriously ugly code following. Written very fast!" Do you remember at all the command you typed that created this message? You would probably get the same message from: mkdir /var/db/pkg/Source pkg_delete Source Try it out! I did think of this. But this creates the error message: pkg_delete: the package info for package 'Source' is corrupt (use -f to force removal) and is generated from within pkg_do in /usr/src/usr.sbin/pkg_install/delete/perform.c This has the additional part to the message "(use -f to force removal)" which the OP did not report. And if you look at the source, you will see that it has to have some kind of additional message, the other possibility being "(but I'll delete it anyway)". But maybe the OP forgot to report this. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem running pkg_delete
Stephen Montgomery-Smith writes: > > You would probably get the same message from: > > mkdir /var/db/pkg/Source > > pkg_delete Source > > > > Try it out! > > I did think of this. But this creates the error message: > > pkg_delete: the package info for package 'Source' is corrupt (use -f to > force removal) > > and is generated from within pkg_do in > /usr/src/usr.sbin/pkg_install/delete/perform.c > > This has the additional part to the message "(use -f to force > removal)" which the OP did not report. And if you look at the > source, you will see that it has to have some kind of additional > message, the other possibility being "(but I'll delete it > anyway)". But maybe the OP forgot to report this. No, they didn't. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
