Re: Package building logs, http://pointyhat.freebsd.org/ ?
On Sun, Nov 17, 2013 at 08:51:38AM +0200, Kimmo Paasiala wrote: > The porter's handbook states that the "package building logs and > errors" would be found at http://pointyhat.freebsd.org/ but the site > is not working. Where are the package building logs now? The porter's handbook is stale. pointyhat is no longer operational. mcl ___ 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"
Package building logs, http://pointyhat.freebsd.org/ ?
The porter's handbook states that the "package building logs and errors" would be found at http://pointyhat.freebsd.org/ but the site is not working. Where are the package building logs now? -Kimmo ___ 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: Proposal for Authors / Vendors in ports
On 11/16/2013 2:08 PM, Eitan Adler wrote: On Sat, Nov 16, 2013 at 2:41 PM, Darren Pilgrim wrote: On 11/16/2013 8:25 AM, Eitan Adler wrote: That's parseable using the regex or literal matching built into every scripting language, most programming languages, and your average human. Sure, but it requires extra tooling to make it work. I don't care which file the data are stored in, I just (a) don't want it to be free form (b) want it to be in some standard format. If you want to carry on about using an existing format, the above is CSV (character-separated values)--one of the most well-established and well-supported file formats in existence. Eh, the format proposed does not even come close to RFC 4180 (CSV). Heh. Pre-coffee brain failure. :) It is, however, the same format used for headers is pretty much everything. ___ 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"
Adding WITH_DEBUG_PORTS to add WITH_DEBUG for specific ports.
What do people think of something like the following? This would
allow users to compile specific ports with debugging capabilities.
Index: Mk/bsd.port.mk
===
--- Mk/bsd.port.mk (revision 333538)
+++ Mk/bsd.port.mk (working copy)
@@ -311,6 +311,8 @@ FreeBSD_MAINTAINER= port...@freebsd.org
# passed to the compiler by setting DEBUG_FLAGS. It is
# set to "-g" at default.
#
+# WITH_DEBUG_PORTS - A list of origins for which
WITH_DEBUG will be set
+#
# WITH_SSP_PORTS
# - If set, SSP_FLAGS (defaults to
-fstack-protector)
#is added to CFLAGS and the necessary flags
@@ -1303,6 +1305,10 @@ MAKE_ENV+= TMPDIR="${TMPDIR}"
CONFIGURE_ENV+=TMPDIR="${TMPDIR}"
.endif # defined(TMPDIR)
+.if defined(WITH_DEBUG_PORTS) && ${WITH_DEBUG_PORTS:M${PKGORIGIN}}
+WITH_DEBUG=yes
+.endif
+
# Reset value from bsd.own.mk.
.if defined(WITH_DEBUG) && !defined(WITHOUT_DEBUG)
STRIP= #none
--
Eitan Adler
___
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: Proposal for Authors / Vendors in ports
On Sat, Nov 16, 2013 at 2:41 PM, Darren Pilgrim wrote: > On 11/16/2013 8:25 AM, Eitan Adler wrote: > That's parseable using the regex or literal matching built into every > scripting language, most programming languages, and your average human. Sure, but it requires extra tooling to make it work. I don't care which file the data are stored in, I just (a) don't want it to be free form (b) want it to be in some standard format. > If > you want to carry on about using an existing format, the above is CSV > (character-separated values)--one of the most well-established and > well-supported file formats in existence. Eh, the format proposed does not even come close to RFC 4180 (CSV). -- Eitan Adler ___ 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"
security/gnutls3 fails to install
Hi, I'm getting failures on the install step for security/gnutls3. Is this related to the problems with staging and INFO? What are possible workarounds? ... cd /usr/ports/security/gnutls3/work/gnutls-3.1.16 && install -o root -g wheel -m 444 doc/examples/*.c /usr/ports/security/gnutls3/work/stage/usr/local/share/examples/gnutls3 install -o root -g wheel -m 444 /usr/ports/security/gnutls3/work/gnutls-3.1.16/AUTHORS /usr/ports/security/gnutls3/work/stage/usr/local/share/doc/gnutls3 install -o root -g wheel -m 444 /usr/ports/security/gnutls3/work/gnutls-3.1.16/NEWS /usr/ports/security/gnutls3/work/stage/usr/local/share/doc/gnutls3 install -o root -g wheel -m 444 /usr/ports/security/gnutls3/work/gnutls-3.1.16/README /usr/ports/security/gnutls3/work/stage/usr/local/share/doc/gnutls3 install -o root -g wheel -m 444 /usr/ports/security/gnutls3/work/gnutls-3.1.16/THANKS /usr/ports/security/gnutls3/work/stage/usr/local/share/doc/gnutls3 > Compressing man pages (compress-man) ===> Installing ldconfig configuration file ===> Building package for gnutls3-3.1.16_1 Creating package /usr/ports/security/gnutls3/work/gnutls3-3.1.16_1.tbz Registering depends: libgpg-error-1.12 libidn-1.28_1 gettext-0.18.3.1 libiconv-1.14_1 p11-kit-0.20.1 libffi-3.0.13 nettle-2.7.1 gmp-5.1.3 ca_root_nss-3.15.2_1 libtasn1-3.3. Creating bzip'd tar ball in '/usr/ports/security/gnutls3/work/gnutls3-3.1.16_1.tbz' tar: info/gnutls3/gnutls.info-5: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** [do-package] Error code 1 Stop in /usr/ports/security/gnutls3. -- Jonathan Chen -- The Internet: an empirical test of the idea that a million monkeys banging on a million keyboards can produce Shakespeare ___ 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: Proposal for Authors / Vendors in ports
On 11/16/2013 8:25 AM, Eitan Adler wrote: On Sat, Nov 16, 2013 at 10:19 AM, Melvyn Sopacua wrote: 2) If meta-information is moved to pkg-descr, it might be worthwhile to add some knowledge about formats and restrictions to portlint. If we go this route I would *strongly* prefer that we do not invent our own format. We should use an existing format. (I don't care which one: YAML, JSON, ...) ? Which both require parsing libraries. We don't need that and neither does anything else that might want to read the ports tree and extract this information. This is easily implemented with simple keywords: We have "WWW:" in pkg-descr. So add "License:", "Vendor:", etc. to pkg-descr. That's parseable using the regex or literal matching built into every scripting language, most programming languages, and your average human. If you want to carry on about using an existing format, the above is CSV (character-separated values)--one of the most well-established and well-supported file formats in existence. ___ 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"
NO_PACKAGE=yes and STAGE
Hi, As NO_PACKAGE=yes do not let the scripts build a package so how can we add STAGE support to such a port? Are they mutually exclusive? Thanks in advance. Regards, Muhammad ___ 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: py27-pytz-2013.8,1
On Sat, Nov 16, 2013 at 14:34:55 +0100, Fabien Debuire wrote: > Hello, > Since the update to the 2013.8,1 I'm not able to install the port. I'm > running freebsd 9.2 svn with ports up-to-date. > > The error I have is: > > ---> Installing the new version via the port > ===> Staging for py27-pytz-2013.8,1 > ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/easy_install-2.7 > - found > ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/python2.7 - found > ===> py27-pytz-2013.8,1 depends on executable: python - found > ===> Generating temporary packing list > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: option --user not recognized > *** [do-install] Error code 1 > > Stop in /usr/ports/devel/py-pytz. > *** [reinstall] Error code 1 > > Stop in /usr/ports/devel/py-pytz. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade20131116-48239-bu0vrp env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=py27-pytz-2013d UPGRADE_PORT_VER=2013d make reinstall > ---> Restoring the old version > 362 > 385 Hi, Could you check again you have the latest version of devel/py-distribute? Thanks, Li-Wen -- Li-Wen Hsu http://lwhsu.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: Proposal for Authors / Vendors in ports
On Sat, Nov 16, 2013 at 10:19 AM, Melvyn Sopacua wrote: >> 2) If meta-information is moved to pkg-descr, it might be worthwhile >> to add some knowledge about formats and restrictions to portlint. If we go this route I would *strongly* prefer that we do not invent our own format. We should use an existing format. (I don't care which one: YAML, JSON, ...) ? -- Eitan Adler ___ 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: Proposal for Authors / Vendors in ports
On Fri, 15 Nov 2013, Stefan Esser wrote: Am 15.11.2013 08:23, schrieb Matthew Seaman: On 15/11/2013 00:54, Eitan Adler wrote: On Thu, Nov 14, 2013 at 5:41 PM, Jaap Akkerhuis wrote: On Nov 14, 2013, at 8:30, Erwin Lansing wrote: That sounds like an excellent idea. I'm just a bit worried about spreading the information over too many places, and would rather split content from logic and add these to pkg-descr as well next to the current WWW. I know we're not consistent already with things like COMMENT and LICENSE already in the Makefile, so won't ojbect too much to where these end up. Apart from spreading this information into to many places (pkg_desc seams a proper place to have such information), why have the Makefile double up as a database? pkg_descr is free form. Makefiles are parsable (make -V). pkg_descr is only as free-form as we define it to be. It's a lot quicker to parse out the WWW entry from pkg_descr than it is to run 'make -V' to extract values from port Makefiles. That's because make includes and parses a whole stack of different files from /usr/ports/Mk and elsewhere and does a bunch of other processing -- takes about 200ms per port just to print out the variables used in the INDEX. +1. I also fail to see the upside of adding extra variables to the makefiles. Requestor of this feature already hinted it's going to be queried using the pkg command, so all it needs is a pkg command that can parse a single line into 2 meaningful chunks, using well-defined delimiters. In addition, there's no descision being made based upon these variables in the building/installation process. So, unless the variable is needed as part of the build process for a port putting it in pkg_decr makes sense to me. This could include some well-known values like MAINTAINER if we want to go that far. Two comments: 1) I think that pkg-descr contains information about the ported software, not the port. I.e. the web-site, the organisation, or the license are good candidates for pkg-descr. The maintainer or other information that does not relate to the ported software itself but just to how it is managed in the FreeBSD ports tree should be kept in some other place. (IMHO) License is used in port building logic. Adding more metadata to pkg-descr fills up the 4k holes mentioned earlier in the thread and adds possibilities for sites like freshports to add more content with minimal effort. Since metadata and description are words with similar meaning, I don't see a need for a name change or new file, as proposed earlier. 2) If meta-information is moved to pkg-descr, it might be worthwhile to add some knowledge about formats and restrictions to portlint. +1 -- Melvyn Sopacua ___ 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"
D101S/D117S/103/D406/504/406/407/409/305/307/108/109/108/105/104/208/209/205
Hi!Dear , how are you? Our promotional price for the Samsung MLT_D101 chips is from 6.7USD/PCS to 8.6USD/PCS and Lexmark E260 chips price from 15USD/PCS to 25USD/PCS ,our discounts based on your order quantity,you can let me know your order quantity for best quotation! I have some new chips for you,Please check our new price list attached: Riso ComColor 3010, 3050, 7010, 7050, 9050 Risograph ComColor 3010, 3050, 7010, 7050, 9050 Ricoh Aficio SP 100 100 E, 100SF SP100LA LEXMARK C746/C748 LEXMARK C935 LEXMARK C734 Lexmark t650 LEXMARK E360 LEXMARK E460 Lexmark E260 oki2731 OKI es3640 OKI C801/c821 OKI C610 OKI B710/B720/B730 Samsung MLT-D111S SAMSUNG MLT-D115L SAMSUNG MLT-D116L SAMSUNG MLT-R116 SAMSUNG MLT-D203S SAMSUNG MLT-D203L SAMSUNG MLT-D203E SAMSUNG MLT-D203U SAMSUNG MLT-D204S SAMSUNG MLT-D204L SAMSUNG MLT-D204E RICOH AFICIO MP C3001/C3501/C3300 CRTG RICOH MP C2031/2051/2531/2551 RICOH AFICIO MP D4501/C5000/C5501 CRTG our company has passed the certification of the ISO14001 and ISO9001!Please check our certification below! And our quality guarantee is for 12monthes with 100% replacement and return if there is any quality problem!You can check more certification about us on [1]www.toner-cartridge-chip.com.cn If you have any question,please let me know! best wishes! yours, Sherry Sherry Sales Manager Company:NPC, Nanchang Printer Color Technology Co., LtD Address: Room 602,Unit 1,Building 3,Hongcheng Road No.589,Nanchang City,Jiangxi province ,China Tel:86-0791-86207670 Fax:86-0791-86207670 Mobile:0086-13576261899 Post code:330046 MSN: [2]she...@printercolorltd.com,ad...@printercolorltd.com Skype:sherryhuang01 Email: [3]she...@printercolorltd.com,ad...@printercolorltd.com, Web:http://printercolorltd.en.alibaba.com/ [4]http://www.printercolorltd.com [5]www.toner-cartridge-chip.com.cn online shop:http://www.aliexpress.com/store/401088 my Facebook address:https://www.facebook.com/npctonerchip CERTIFICATE:http://www.toner-cartridge-chip.com.cn/column/208392025/Cer tificates.html golden member:http://en.trade2cn.com/companyShop/11090211243708n.html;jsession id=D66F7EB010C669C88801D1AF46803D3B 03108068171/8068198 [6]https://twitter.com/NPCtonerchips NPC ISO14001 and ISO9001 certification: References 1. http://www.toner-cartridge-chip.com.cn/ 2. mailto:she...@printercolorltd.com,ad...@printercolorltd.com 3. mailto:she...@printercolorltd.com,ad...@printercolorltd.com 4. http://www.printercolorltd.com/ 5. http://www.toner-cartridge-chip.com.cn/ 6. https://twitter.com/NPCtonerchips ___ 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: py27-pytz-2013.8,1
I can build pytz-2013.8,1 well on my FreeBSD-9.2 amd64 system. wen 2013/11/16 Fabien Debuire : > Hello, > Since the update to the 2013.8,1 I'm not able to install the port. I'm > running freebsd 9.2 svn with ports up-to-date. > > The error I have is: > > ---> Installing the new version via the port > ===> Staging for py27-pytz-2013.8,1 > ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/easy_install-2.7 > - found > ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/python2.7 - found > ===> py27-pytz-2013.8,1 depends on executable: python - found > ===> Generating temporary packing list > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: option --user not recognized > *** [do-install] Error code 1 > > Stop in /usr/ports/devel/py-pytz. > *** [reinstall] Error code 1 > > Stop in /usr/ports/devel/py-pytz. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade20131116-48239-bu0vrp env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=py27-pytz-2013d UPGRADE_PORT_VER=2013d make reinstall > ---> Restoring the old version > 362 > 385 > > > -- > Fabien Debuire > debuire.fab...@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" ___ 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: py27-pytz-2013.8,1
Hello, Since the update to the 2013.8,1 I'm not able to install the port. I'm running freebsd 9.2 svn with ports up-to-date. The error I have is: ---> Installing the new version via the port ===> Staging for py27-pytz-2013.8,1 ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/easy_install-2.7 - found ===> py27-pytz-2013.8,1 depends on file: /usr/local/bin/python2.7 - found ===> py27-pytz-2013.8,1 depends on executable: python - found ===> Generating temporary packing list usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --user not recognized *** [do-install] Error code 1 Stop in /usr/ports/devel/py-pytz. *** [reinstall] Error code 1 Stop in /usr/ports/devel/py-pytz. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20131116-48239-bu0vrp env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py27-pytz-2013d UPGRADE_PORT_VER=2013d make reinstall ---> Restoring the old version 362 385 -- Fabien Debuire debuire.fab...@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"
www/aria2 dependencies & lang/llvm33 build error
Hi, I'm running FreeBSD 8.4-RELEASE-p4. www/aria2 1.18.1 requires lang/clang33. Is this really necessary? Previous aria2 versions didn't require clang. If so, I already have lang/clang-devel (3.4) installed, but the port still wants to build lang/clang33, which of course requires devel/llvm33. However on 8.4-REL, currently llvm33 fails to build: gmake[1]: Leaving directory `/usr/ports/devel/llvm33/work/llvm-3.3.src/bindings' llvm[0]: * Completed Release Build sphinx-build -b man -d _build/doctrees . _build/man Traceback (most recent call last): File "/usr/local/bin/sphinx-build", line 5, in from pkg_resources import load_entry_point File "build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py", line 2805, in File "build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py", line 696, in require File "build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py", line 594, in resolve pkg_resources.DistributionNotFound: markupsafe gmake: *** [man] Error 1 *** Error code 2 Stop in /usr/ports/devel/llvm33. *** Error code 1 Thanks. Regards Andrew ___ 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: [QAT] r333268: 4x leftovers
On Sat, Nov 16, 2013 at 01:06:26PM +0100, Baptiste Daroussin wrote: > On Sun, Nov 10, 2013 at 04:38:44PM -0500, Gerald Pfeifer wrote: > > On Sun, 10 Nov 2013, Antoine Brodin wrote: > > > You can try patch at: > > > http://people.freebsd.org/~antoine/ports/stage-info_subdir.diff > > > (totally untested) > > > > Thanks for looking into this, Antoine. I tested this using > > lang/gcc47 and unfortunately info/gcc47 still remains in my > > testing. > > > > Gerald > > Sorry I missed that one, I'll have a look as soon as possible. > > regards, > Bapt Antoine's patch should be ok for pkg_install, this is what you need for pkgng: http://people.freebsd.org/~bapt/info-dir.diff also 100% untested ;) regards, Bapt pgpn27tOKy4cO.pgp Description: PGP signature
why to the same versions of clang
H! I like to know what is different with default clang on FreeBSD 10.0-BETA3 and cland from /devel. I like to install blender and graphics/blender and graphics/openshadinglanguage need/wanted clang from /devel. The same version as I have: clang -v FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 Target: x86_64-unknown-freebsd10.0 Thread model: posix Thank you. -- Mitja --- http://www.redbubble.com/people.lumiwa ___ 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: [QAT] r333268: 4x leftovers
On Sun, Nov 10, 2013 at 04:38:44PM -0500, Gerald Pfeifer wrote: > On Sun, 10 Nov 2013, Antoine Brodin wrote: > > You can try patch at: > > http://people.freebsd.org/~antoine/ports/stage-info_subdir.diff > > (totally untested) > > Thanks for looking into this, Antoine. I tested this using > lang/gcc47 and unfortunately info/gcc47 still remains in my > testing. > > Gerald Sorry I missed that one, I'll have a look as soon as possible. regards, Bapt pgplHdKoKOIFP.pgp Description: PGP signature
FreeBSD ports you maintain which are out of date
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 +-+ math/coinmp | 1.7.1 | 1.7.2 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org Thanks. ___ 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"
