Re: cupsd.conf.N is missing here
On 27.09.2010 06:46, Boris Samorodov wrote: On Sat, 25 Sep 2010 20:13:12 +0200 dan wrote: If anyone else notices this behaviour Yep, I've got the same. and consider it necessary to send a bug report, I am open to send it. Please do. Thank you. I sent it. For any reference: " It has the internal identification `ports/150980'. The individual assigned to look at your report is: freebsd-ports-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=150980 " d ___ 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: cupsd.conf.N is missing here
On Sat, 25 Sep 2010 20:13:12 +0200 dan wrote: > If anyone else notices this behaviour Yep, I've got the same. > and consider it necessary to > send a bug report, I am open to send it. Please do. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
py-lxml 2.2.7 wont build on HEAD
while trying to build py-lxml 2.2.7 on FreeBSD 9 it hangs on this line cc -DNDEBUG -O2 -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.6 -c src/lxml/lxml.etree.c -o temp.freebsd-9.0-CURRENT-amd64-2.6/src/lxml/lxml.etree.o -w here is the complete output uname -a FreeBSD Sam.PuffyBSD.Com 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Sun Sep 26 21:48:08 CDT 2010 r...@fnfs.puffybsd.com:/usr/obj/usr/src/sys/WORKSTATION amd64 Sam# Sam# cd /usr/ports/devel/py-lxml/ Sam# make clean ===> Cleaning for py26-lxml-2.2.7 Sam# Sam# Sam# Sam# make install ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE ===> Extracting for py26-lxml-2.2.7 => MD5 Checksum OK for lxml-2.2.7.tar.gz. => SHA256 Checksum OK for lxml-2.2.7.tar.gz. ===> Patching for py26-lxml-2.2.7 ===> py26-lxml-2.2.7 depends on file: /usr/local/bin/easy_install-2.6 - found ===> py26-lxml-2.2.7 depends on file: /usr/local/bin/python2.6 - found ===> py26-lxml-2.2.7 depends on shared library: xml2.5 - found ===> py26-lxml-2.2.7 depends on shared library: xslt.2 - found ===> Configuring for py26-lxml-2.2.7 Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running config ===> Building for py26-lxml-2.2.7 Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running setopt Writing setup.cfg Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running setopt Writing setup.cfg Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running setopt Writing setup.cfg Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running setopt Writing setup.cfg Building lxml version 2.2.7. Building with Cython 0.13. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/local/lib running bdist_egg running egg_info writing src/lxml.egg-info/PKG-INFO writing top-level names to src/lxml.egg-info/top_level.txt writing dependency_links to src/lxml.egg-info/dependency_links.txt reading manifest file 'src/lxml.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'src/lxml.egg-info/SOURCES.txt' installing library code to build/bdist.freebsd-9.0-CURRENT-amd64/egg running install_lib running build_py creating lib.freebsd-9.0-CURRENT-amd64 creating lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/doctestcompare.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/builder.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/sax.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/cssselect.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/usedoctest.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/__init__.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/ElementInclude.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/pyclasslookup.py -> lib.freebsd-9.0-CURRENT-amd64/lxml copying src/lxml/_elementpath.py -> lib.freebsd-9.0-CURRENT-amd64/lxml creating lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/builder.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/diff.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/defs.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/_setmixin.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/formfill.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/soupparser.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/_html5builder.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/ElementSoup.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/_diffcommand.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/clean.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/__init__.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/html5parser.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/_dictmixin.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html copying src/lxml/html/usedoctest.py -> lib.freebsd-9.0-CURRENT-amd64/lxml/html running build_ext building 'lxml.etree' extension creating temp.freebsd-9.0-CURRENT-amd64-2.6 creating temp.freebsd-9.0-CURRENT-amd64-2.6/src creating temp.freebsd-9.0-CURRENT-amd64-2.6/s
Re: ptlib build failure - breaks pwlib - hence also asterisk - opal - & openh323
> On 2010-Sep-23 12:22:51 -0400, Jerry wrote: > >A few months ago, after upgrading to version 8/amd64 and installing > >OpenSSL from ports, I had several ports bomb out when I attempted to > >build them. I filed PR's against them and contacted the maintainers. It > >appeared that the majority of these port maintainers were not even aware > >that their port would not build in the presents of OpenSSL when it was > >installed via the ports tree. In any case, I was able to get them to > >fix their ports to build correctly. > > So it sounds like everything worked as expected. I fail to see any > deficiency in the way things worked. > > >What amazed me is that this is such a common occurrence that it should > >have been contemplated when the port was released. > > Why do you think that? It's quite likely that the port maintainers > didn't install OpenSSL from ports - I know I don't. > > > Perhaps the Porters > > > >Handbook should list ports that have a corresponding base system > >counterpart; thereby, alerting the maintainer that he/she should test > >against both versions to insure full compatibility. > > I disagree. I'd be surprised if any part of the base system _didn't_ > have one or more corresponding equivalents in ports. As well as > OpenSSL, there are 5 versions of gcc (and probably a half-dozen other > C compilers), binutils, 5 versions of bind (and several other DNS > implementations that presumably also implement resolver libraries), 3 > Kerberos variants, 2-4 versions of ncurses, readline, etc. Expecting > a ports maintainer to check that their port works with all of these on > 3 different FreeBSD branches and about 5 different architectures is > completely unrealistic. > > IMHO, the expectations on a port maintainer are that they verify that > the port works as expected in their environments (where any unusual > configurations are listed in the port dependencies) and at least > builds on all other supported branches/architectures (via tinderbox or > similar). Any issues beyond that realistically need to be dealt with > on a case-by-case basis. Frankly I have never heard such a load of inconsiderate thoughtlessness and denial of responsibility form anyone before. Installation of ssl from ports is part of a normal configuration. Mainainers need to take account of reality. David Photographic Artist Permanent Installations & Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography & Official Portraiture Combined darkroom & digital creations & Systems Adminstrator for the vizion2000.net network ___ 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: [HEADS-UP] graphics/claraocr out of date.
On Sat, Sep 25, 2010 at 07:54:42PM -0400, jhell wrote: > On 09/25/2010 19:01, Wesley Shields wrote: > > On Sat, Sep 25, 2010 at 02:49:02PM -0400, jhell wrote: > >> > >> Going through some of my old OCR uses, I could the subject listed port > >> out of date and the URL referenced in the pkg-descr is non functional. > >> > >> The new website for this port is: > >> http://www.claraocr.org/en/download.html > >> > >> And seems to be last updated as of: 11/18/09 which is the v1.1 release. > > > > [HEADS-UP] like subject lines are usually reserved for when something > > major is going to happen (like an update of gnome or kde). > > > > -- WXS > > So sue me. I'm just trying to educate you so that you can adhere to the social norms of the community in the future. -- WXS ___ 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: FreeBSD Port: openntpd-4.6_1,2
Shan Sa: > Why is the file ntpd.conf installed as read-only? (444) This is accidental. The example ntpd.conf is installed into EXAMPLEDIR with INSTALL_DATA, which sets the mode to 444. Later, ntpd.conf is copied from the example and those permissions are preserved. There are a lot of other instances of this in the tree, so I don't know if it is worth fiddling with the permissions. -- Christian "naddy" Weisgerber na...@mips.inka.de ___ 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"
