math/ess, deprecate or change maintainership
Hi, Emacs Speacks Statistics 15.09, which I maintain as math/ess, has been released in the end of September. However, as I outlined in http://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096678.html, I have severe doubts that packages for emacs modes generate any value. I do not plan to update math/ess and advocate for deprecating that port. Should anybody need math/ess in ports, I would like to hand over maintainership to said anybody willing to step in. Cheers, -- Christopher ___ 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: value of maintaining emacs-mode packages in ports
On So, 2014-11-23 at 07:32 -0500, Daniel Feenberg wrote: On Sun, 23 Nov 2014, Christopher J. Ruwe wrote: In that light and as the ports maintainer of math/ess, the Emacs speaks statistics R-mode of emacs, I am asking myself specifically whether I add any real benefit in maintaining math/ess. More generally, I am interested in community answers as to whether it is really useful to maintain Emacs-extension-packages in ports. As a non-Emacs user, can I raise some questions that should be asked every time a service/feature is withdrawn? If you stop maintaining math/ess, does it go away, or merely stop improving? I think eventually math/ess would be retired on go away. Emacs package installation is available since Emacs 24 and I believe emacs23 is retired as of 19th November this year. Does the Emacs package system support the same versions of Emacs that you support in math/ess? I have the impression they are more up to date. Latest MELPA package is from the 14th (http://melpa.org/#/ess). If a user upgrades FreeBSD will he lose what he has unless he converts to the new Emacs package system? Emacs packages are more like plugins (cf. firefox). Upgrades of FreeBSD do not touch these. On upgrades of Emacs, users might need to recompile, if the chose to run compiled Emacs Lisp modules. Is the Emacs package system something that requires an installation of its own? A clear no. ESS is just an interface to the R language/interpreter (math/R). It can run without R installed, although it is not very useful in my opinion the same way that having a languange-mode for an arbitrary languae is not really useful without the corresponding language compiler/interpreter around. But people do strange things .. May I suggest that if you let it go away, you place a README file where Emacs-extension-packages was that points users to the replacement, with instructions for how to get there? Not everyone using Emacs on FreeBSD follows the mailing lists for FreeBSD, (or Emacs). I do not now procedures for deprecated ports. I see emacs modes alike to plugins in firefox, which are not packaged as well, so I see the idea of potentially retiring math/ess in the wider setting of giving up more or less all emacs extensions. Anyhow, thanks for your thoughts. Cheers, -- Christopher ___ 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: value of maintaining emacs-mode packages in ports
On Mo, 2014-11-24 at 00:48 +0100, Roland Smith wrote: On Sun, Nov 23, 2014 at 12:32:14AM +0100, Christopher J. Ruwe wrote: I am well aware that very probably I might be starting a rant thread, however, I am genuinely interested in opinions from the community. Since version 24, Emacs, the very good operating system missing only a decent editor, has developed a package manager for Emacs extensions. Some good repos exist, packages are usually installed to ~/.emacs.d and I have come to really enjoy that way of installing packages. In that light and as the ports maintainer of math/ess, the Emacs speaks statistics R-mode of emacs, I am asking myself specifically whether I add any real benefit in maintaining math/ess. More generally, I am interested in community answers as to whether it is really useful to maintain Emacs-extension-packages in ports. Thanks for your thoughts, cheers, It might help to see this question in a broader context. There are several communities that have there own repositories/package managers these days, e.g: * TeX * Perl * Python * Ruby * Node * Emacs Yet the maintainers of the ports system go through the effort of maintaining ports for a lot of these packages, even though it might strictly speaking be considered a duplication of effort. There are at least two big reasons that I can think of; 1) FreeBSD specific patches are necessary to build a package. (I.e. every port that has a files subdirectory.) The ports tree is arguably the right place for that. The best case would be that such changes are merged upstream, but that doesn't always happen. 2) A foreign package might depend on a FreeBSD port or the other way around. How could this be handled properly if not in the ports tree? So by its very nature, if you want to reap the benefits of the ports infrastructure for your package, you have to *use* said infrastructure. Packages that *can* install in a user's $HOME directory and have no non-obvious dependencies are the exception to this rule, I think. No one will expect e.g. a vim bundle to do anything useful when vim is not installed! But such packages are obviously only available to the user that has installed them. So for a multi-user installation a port would still make more sense. Roland I think of Emacs modes differently than of Perl/Python/Ruby/Nodejs ... programs. The latter do not extend the languages, but use the language to provide independent utility to some user. Emacs modes, alike to the vim bundles you mentioned, extend Emacs (up to the ultimate goal that the user is for the whole duration of the session not forced to leave Emacs ;-) ). I cannot think of any Emacs mode being required by something non-Emacs. I have mentioned in a different answer that I see them alike to Firefox plugins. The only patches I noted so far to Emacs ports concern the placement of files, although I may well be wrong here. I have problems imaging a multi-user installation with multiple instances of Emacs mode packages installed. My elders have told tales of lore of mighty heroes connecting to machines using tools of magic called terminals, so they all could toil on the same computer. Jokes aside, I can only think of thin client settings where one would want to avoid multiple packages of the same program installed. Isn't everybody using independent so called personal computers now? Without any irony, that's a real question: I thought thin client computing has more or less died, am I wrong here? Anyhow, thanks for your thoughts on that matter -- Christopher signature.asc Description: This is a digitally signed message part
Re: value of maintaining emacs-mode packages in ports
On So, 2014-11-23 at 00:12 -0800, Perry Hutchison wrote: Christopher J. Ruwe c...@cruwe.de wrote: ... Emacs, the very good operating system missing only a decent editor ... Perhaps someone should port vi to it? [dons flame-proof suit] That's not necessary. You can run vi in ansi-term mode ... -- Christopher ___ 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
value of maintaining emacs-mode packages in ports
I am well aware that very probably I might be starting a rant thread, however, I am genuinely interested in opinions from the community. Since version 24, Emacs, the very good operating system missing only a decent editor, has developed a package manager for Emacs extensions. Some good repos exist, packages are usually installed to ~/.emacs.d and I have come to really enjoy that way of installing packages. In that light and as the ports maintainer of math/ess, the Emacs speaks statistics R-mode of emacs, I am asking myself specifically whether I add any real benefit in maintaining math/ess. More generally, I am interested in community answers as to whether it is really useful to maintain Emacs-extension-packages in ports. Thanks for your thoughts, cheers, -- Christopher ___ 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
could somebody please close ports/185614?
1) Could somebody with a commit bit please close ports/185614 (http://www.freebsd.org/cgi/query-pr.cgi?pr=185614) The issue I reported has gone away (or never was a real problem, I do not know). 2) We recently had a huge discussion about piles of old PRs sitting in GNATS and gathering dust. Would it be possible to grant reporters commit rights to their PR so that they could close the report themselves (and document why, of course)? As a reporter, I think it is my responsibility to accompany my PR over it's life. At this moment, PR reporters abilities are restricted to pestering freebsd-ports@, encouraging a more active role would not hurt, wouldn't it? Cheers and thanks, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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
[solved] Re: ports-mgmt/pkg failing to link when cross-compiling with qemu
On Thu, 23 Jan 2014 20:38:51 +0100 Christopher J. Ruwe c...@cruwe.de wrote: When trying the instructions on https://wiki.freebsd.org/QemuUserModeHowTo, I encountered a fairly basic port (ports-mgmt/pkg) failing to link properly: [... - everything fine until here] cc -static -O -pipe -DPORTSDIR=\/usr/ports\ -I../libpkg -I/usr/ports/ports-mg/work/pkg-1.2.5/pkg/../external/expat/lib -std=gnu99 -Qunused-arguments -Wsystemprototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwritepts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-int -static -o pkg-static add.o annotate.o audit.o autoremove.o backup.o check.ock.o main.o plugins.o progressmeter.o query.o register.o repo.o rquery.o update.otch.o shell.o stats.o ssh.o -L/usr/ports/ports-mgmt/pkg/work/pkg-1.2.5/pkg/../lib -lcrypto -lmd -lz -lbz2 -llzma -ljail -lelf -larchive -lsbuf -lfetch -lpt add.o: In function `exec_add': add.c:(.text+0x11c): undefined reference to `pkgdb_access' add.c:(.text+0x13c): undefined reference to `pkgdb_open' add.c:(.text+0x164): undefined reference to `pkg_manifest_keys_new' add.c:(.text+0x344): undefined reference to `pkg_fetch_file' add.c:(.text+0x364): undefined reference to `pkg_add' add.c:(.text+0x42c): undefined reference to `pkg_manifest_keys_free' add.c:(.text+0x434): undefined reference to `pkgdb_close' [ ... - they are all alike] version.o: In function `print_version': version.c:(.text+0x14fc): undefined reference to `pkg_get2' version.c:(.text+0x1514): undefined reference to `pkg_version_cmp' version.c:(.text+0x1590): undefined reference to `pkg_asprintf' version.c:(.text+0x15a4): undefined reference to `pkg_asprintf' version.c:(.text+0x1650): undefined reference to `pkg_printf' which.o: In function `exec_which': [...] Has anybody encountered something similar and would know how to fix that? Thanks and cheers, The problem is trying to build ARMv6 32b-binaries on 64b amd64. Building on i386 works. Would it be possible to include that in the wiki (https://wiki.freebsd.org/QemuUserModeHowTo) Cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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: security/krb5 segfaulting on ARMv6/STABLE-10 Raspberry
On Tue, 11 Feb 2014 19:50:24 +0100 Christopher J. Ruwe c...@cruwe.de wrote: Yesterday I ran into problems with self-compiled security/krb5 on ARMv6/10-STABLE Raspberry Pi. % uname -a FreeBSD armbld.hb22.cruwe.de 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #0 r260786+cc2516d(stable/10): Fri Jan 17 20:08:46 CET 2014 r...@dijkstra.cruwe.de:/usr/home/cjr/media/src/crochet-freebsd/work/obj/arm.arm/usr/home/cjr/media/src/freebsd-git/sys/RPI-B arm security/krb5 is segfaulting when kinit tries to connect to retrieve a ticket. Extensive information is on http://mailman.mit.edu/pipermail/kerberos/2014-February/019501.html The exact same configuration runs fine on amd64/9-STABLE [cjr@dijkstra:src/freebsd-doc]$ uname -a (02-11 19:28) FreeBSD dijkstra-old.hb22.cruwe.de 9.2-STABLE FreeBSD 9.2-STABLE #0 05d5e4d: Tue Jan 7 09:09:19 CET 2014 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd-git/sys/GEN_WDTRACE amd64 I suspect erronous compilation, but compiling thrice did not yield different results. 1) Does somebody successfully run security/krb5-1.12.1 on a Raspberry? 2) If true, could I have the instuctions to build or download your image and your make.conf-settings to enable me to reproduce your build? Thanks and cheers, Yesterday, I rebuilt on a clean Raspberry using FreeBSD-10.0-STABLE-arm-armv6-RPI-B-20140209-r261642.img from snapshots. Same result. I also tested security/krb5-maint. Same result. Currently, I am building the MIT-Kerberos ports in a chroot on 10-STABLE i386 machine to check if something breaks on the Raspberries - admittedly, Raspberries are not exactly what you would use to compile packages for redistribution, even if it would offer possibilities for a smile when thinking of a massive Raspberry-cluster ... I am hesitant to file a PR to request security/krb5 be marked broken on ARM as other Raspberry distros (ArchLinux e.g) have krb5 in their prebuilts and I did not find any mention of problems. Cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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: poudriere and texlive, and custom make.conf
On Wed, 12 Feb 2014 07:32:38 -0800 (PST) Anton Shterenlikht me...@bris.ac.uk wrote: What is the best way to build both tetex and texlive packages with poudriere? Do I need to create 2 different jails, one with TEX_DEFAULT=texlive in /etc/make.conf? Or is this possible to achive in the same jail, and with both texlive and tetex in the list of packages to build? Thanks Anton ___ 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 I would use a SET, see poudriere(8), section Customization for the hierarchy how customs make.conf-files are pulled in. To reduce compilation time, one could first build the with-tetex set and then copy over (or clone) all packages to the with-texlive set. All on the same jail and ports tree. poudriere would clean up the all tetex-dependencies and build anew with texlive. A bit hackish, but works. Cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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/krb5 segfaulting on ARMv6/STABLE-10 Raspberry
Yesterday I ran into problems with self-compiled security/krb5 on ARMv6/10-STABLE Raspberry Pi. % uname -a FreeBSD armbld.hb22.cruwe.de 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #0 r260786+cc2516d(stable/10): Fri Jan 17 20:08:46 CET 2014 r...@dijkstra.cruwe.de:/usr/home/cjr/media/src/crochet-freebsd/work/obj/arm.arm/usr/home/cjr/media/src/freebsd-git/sys/RPI-B arm security/krb5 is segfaulting when kinit tries to connect to retrieve a ticket. Extensive information is on http://mailman.mit.edu/pipermail/kerberos/2014-February/019501.html The exact same configuration runs fine on amd64/9-STABLE [cjr@dijkstra:src/freebsd-doc]$ uname -a (02-11 19:28) FreeBSD dijkstra-old.hb22.cruwe.de 9.2-STABLE FreeBSD 9.2-STABLE #0 05d5e4d: Tue Jan 7 09:09:19 CET 2014 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd-git/sys/GEN_WDTRACE amd64 I suspect erronous compilation, but compiling thrice did not yield different results. 1) Does somebody successfully run security/krb5-1.12.1 on a Raspberry? 2) If true, could I have the instuctions to build or download your image and your make.conf-settings to enable me to reproduce your build? Thanks and cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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-Ports-Announce] Time to bid farewell to the old pkg_ tools
On Wed, 5 Feb 2014 23:26:18 -0800 Kevin Oberman rkober...@gmail.com wrote: If you use poudriere, you can roll your own packages with custom options and maintain things pretty reasonably, but for a single system (or two), this is a bit of overkill. As things stand, this is a real pain to use customized ports and packages from the standard FreeBSD distributions. I'm waiting with great excitement for this to appear, though I have no idea if it is near or far. I really don't think so. Even with a single machine, poudriere literally saved my a.. pretty bottom several times breaking on implicit dependencies which would have popped up ages later with nasty and difficult to trace problems/errors. I think anybody who compiles from ports should _really_ use poudriere. I even think it should be strongly suggested in the handbook. (I'd be willing to write that up for that matter.) -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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-Ports-Announce] Time to bid farewell to the old pkg_ tools
On Thu, 6 Feb 2014 15:49:24 +0100 Matthias Apitz g...@unixarea.de wrote: El día Thursday, February 06, 2014 a las 02:36:30PM +0100, Christopher J. Ruwe escribió: On Wed, 5 Feb 2014 23:26:18 -0800 Kevin Oberman rkober...@gmail.com wrote: If you use poudriere, you can roll your own packages with custom options and maintain things pretty reasonably, but for a single system (or two), this is a bit of overkill. As things stand, this is a real pain to use customized ports and packages from the standard FreeBSD distributions. I'm waiting with great excitement for this to appear, though I have no idea if it is near or far. I really don't think so. Even with a single machine, poudriere literally saved my a.. pretty bottom several times breaking on implicit dependencies which would have popped up ages later with nasty and difficult to trace problems/errors. I think anybody who compiles from ports should _really_ use poudriere. I even think it should be strongly suggested in the handbook. (I'd be willing to write that up for that matter.) Please point me to the existing documentation. I don't see the string poudriere in our handbook. Thx matthias I wrote it should be suggested, which means that I think it would be a good idea, not that it already happened. I do not understand how that could be misunderstood. Cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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
ports-mgmt/pkg failing to link when cross-compiling with qemu
When trying the instructions on https://wiki.freebsd.org/QemuUserModeHowTo, I encountered a fairly basic port (ports-mgmt/pkg) failing to link properly: [... - everything fine until here] cc -static -O -pipe -DPORTSDIR=\/usr/ports\ -I../libpkg -I/usr/ports/ports-mg/work/pkg-1.2.5/pkg/../external/expat/lib -std=gnu99 -Qunused-arguments -Wsystemprototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwritepts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-int -static -o pkg-static add.o annotate.o audit.o autoremove.o backup.o check.ock.o main.o plugins.o progressmeter.o query.o register.o repo.o rquery.o update.otch.o shell.o stats.o ssh.o -L/usr/ports/ports-mgmt/pkg/work/pkg-1.2.5/pkg/../lib -lcrypto -lmd -lz -lbz2 -llzma -ljail -lelf -larchive -lsbuf -lfetch -lpt add.o: In function `exec_add': add.c:(.text+0x11c): undefined reference to `pkgdb_access' add.c:(.text+0x13c): undefined reference to `pkgdb_open' add.c:(.text+0x164): undefined reference to `pkg_manifest_keys_new' add.c:(.text+0x344): undefined reference to `pkg_fetch_file' add.c:(.text+0x364): undefined reference to `pkg_add' add.c:(.text+0x42c): undefined reference to `pkg_manifest_keys_free' add.c:(.text+0x434): undefined reference to `pkgdb_close' [ ... - they are all alike] version.o: In function `print_version': version.c:(.text+0x14fc): undefined reference to `pkg_get2' version.c:(.text+0x1514): undefined reference to `pkg_version_cmp' version.c:(.text+0x1590): undefined reference to `pkg_asprintf' version.c:(.text+0x15a4): undefined reference to `pkg_asprintf' version.c:(.text+0x1650): undefined reference to `pkg_printf' which.o: In function `exec_which': which.c:(.text+0xe8): undefined reference to `pkgdb_open' which.c:(.text+0xf8): undefined reference to `pkgdb_close' which.c:(.text+0x18c): undefined reference to `pkgdb_query_which' which.c:(.text+0x1ac): undefined reference to `pkgdb_it_next' which.c:(.text+0x250): undefined reference to `pkg_printf' which.c:(.text+0x260): undefined reference to `pkg_printf' which.c:(.text+0x284): undefined reference to `pkg_printf' which.c:(.text+0x298): undefined reference to `pkgdb_it_next' which.c:(.text+0x2a8): undefined reference to `pkg_free' which.c:(.text+0x2b0): undefined reference to `pkgdb_it_free' which.c:(.text+0x2b8): undefined reference to `pkgdb_close' fetch.o: In function `exec_fetch': fetch.c:(.text+0xa4): undefined reference to `pkg_config_bool' fetch.c:(.text+0xb0): undefined reference to `pkg_config_bool' fetch.c:(.text+0x1e8): undefined reference to `pkgdb_set_case_sensitivity' fetch.c:(.text+0x2c0): undefined reference to `pkgdb_access' fetch.c:(.text+0x2e0): undefined reference to `pkgdb_access' fetch.c:(.text+0x314): undefined reference to `pkgdb_open' fetch.c:(.text+0x330): undefined reference to `pkg_jobs_new' fetch.c:(.text+0x34c): undefined reference to `pkg_jobs_set_repository' fetch.c:(.text+0x360): undefined reference to `pkg_jobs_set_flags' fetch.c:(.text+0x37c): undefined reference to `pkg_jobs_add' fetch.c:(.text+0x38c): undefined reference to `pkg_jobs_solve' fetch.c:(.text+0x39c): undefined reference to `pkg_jobs_count' fetch.c:(.text+0x418): undefined reference to `pkg_jobs_apply' fetch.c:(.text+0x420): undefined reference to `pkg_jobs_free' fetch.c:(.text+0x428): undefined reference to `pkgdb_close' shell.o: In function `exec_shell': shell.c:(.text+0x54): undefined reference to `pkgdb_cmd' stats.o: In function `exec_stats': stats.c:(.text+0xe8): undefined reference to `pkgdb_open' stats.c:(.text+0x120): undefined reference to `pkgdb_stats' stats.c:(.text+0x13c): undefined reference to `pkgdb_stats' stats.c:(.text+0x1cc): undefined reference to `pkg_repos_total_count' stats.c:(.text+0x1e8): undefined reference to `pkgdb_stats' stats.c:(.text+0x204): undefined reference to `pkgdb_stats' stats.c:(.text+0x220): undefined reference to `pkgdb_stats' stats.c:(.text+0x23c): undefined reference to `pkgdb_stats' stats.c:(.text+0x294): undefined reference to `pkgdb_close' ssh.o: In function `exec_ssh': ssh.c:(.text+0x98): undefined reference to `pkg_sshserve' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[3]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.2.5/pkg *** Error code 1 Stop. make[2]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.2.5 *** Error code 1 Stop. make[1]: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Stop. make: stopped in /usr/ports/ports-mgmt/pkg Has anybody encountered something similar and would know how to fix that? Thanks and cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. -
Re: ports/185614: editors/openoffice-4 does not configure, dbus-deps missing
As MAINTAINER has timed out anyway, I cc freebsd-ports@. As of at least svn path=/head/; revision=340861, the problem of dbus not being pulled by editors/openoffice-4 disappears. I do not believe compilation without dbus has any practical relevance. I suggest to close the PR. -- Christopher J. Ruwe, Dipl.-Kfm. u. M.Comp.Sc. TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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: poudriere behave-alike for
On Mon, 25 Nov 2013 08:40:54 +0100 John Marino dragonfly...@marino.st wrote: On 11/25/2013 02:15, Christopher J. Ruwe wrote: I think my question is slightly off-topic, but I think freebsd-ports@ may be the best of many not so good fits: I need to build packages for Solaris and SmartOS. My first choice would be ports, which unfortunately are not very well suited to cross-building. Instead I use, as many people, pkgsrc. I would like to leverage pkgsrc with something like poudriere, especially as I have ZFS and zones in Solaris/SmartOS. I found in a message on the DragonFlyBSD list http://leaf.dragonflybsd.org/mailarchive/users/2013-01/msg8.html a mention of poudriere being used on DragonFly/pkgsrc. I was involved in that referenced email. The first point to make is that currently ports is *not* an option for solaris or SmartOS, regardless of its ability to cross compile. Point #2 is that I want to try to bring ports to the solaris-alike family in the future (aka sunports), but work on this hasn't started yet, and adapting solaris will be a lot more work than adapting DragonFly was (and believe me DF was *A LOT* of work. Point #3 is that if I were still heavily involved in pkgsrc, I would probably create a branch of poudriere that supported pkgsrc. It is something I would recommend highly to the pkgsrc community. However, it suffers greatly from Not invented Here syndrome, so most consider (without proper evaluation) that pkgsrc tools are more or less equivalent. The fact is that they are not. Does anybody know of the state of this piece of software? The git repos I can find on google are stale links. As etoilebsd is referenced in the mail from DragonFly, I chose to ask here first. There is no poudriere-for-pkgsrc. The current poudriere branches are here: https://fossil.etoilebsd.net/poudriere/brlist For pkgsrc your choices are: http://pkgsrc.se/pkgtools/distbb http://pkgsrc.se/pkgtools/pbulk Here's a recent post about setting up pbulk: http://mail-index.netbsd.org/pkgsrc-users/2013/11/09/msg018881.html In general its poorly documented and difficult to set up parallel building. The script above is yet another attempt to reduce the complexity but I don't think either pbulk or distcc have nearly the polish or features that poudriere has. But take that with a grain of salt because I haven't used either in a long time. One more thing: SmartOS not only uses pkgsrc officially, they have a full builder farm that makes a full set of packages quarterly packages available. It also works on other illumos platforms. The best approach is just use their work. Another tutorial how to set up bulk build: http://www.perkin.org.uk/posts/distributed-chrooted-pkgsrc-bulk-builds.html info about packages already built: http://www.perkin.org.uk/posts/whats-new-in-pkgsrc-2013Q2.html You might want to check out the reset of www.perkin.org.uk for interesting posts. John ___ 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 Thanks to both and Shane for your kind answers. I know of Jonathan Perkin's work and I also know of an approach roughly resembling poudriere ideas named 'pk' (github.com/mamash/pk), which however seems do have been abandoned by Joyent. While it would be well be possible to use Joyent's binaries, I am a huge fan of the ability of ports-like systems to be tuned. I am also a huge fan of the poudriere approach of building everything in clean jails, especially after being nastily bitten by implicit dependencies (i.e., such deps as introduced by autoconf runs instead of being declared in the port). I had the hopes that issue had come up sufficiently often that somebody already did a poudriere port or build a functional clone or however to call that. I do not really know whether I can port poudriere capability- and capacity-wise. However, many thanks, your answers have helped me a lot in getting a better picture. Cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr
poudirere behave-alike for
I think my question is slightly off-topic, but I think freebsd-ports@ may be the best of many not so good fits: I need to build packages for Solaris and SmartOS. My first choice would be ports, which unfortunately are not very well suited to cross-building. Instead I use, as many people, pkgsrc. I would like to leverage pkgsrc with something like poudriere, especially as I have ZFS and zones in Solaris/SmartOS. I found in a message on the DragonFlyBSD list http://leaf.dragonflybsd.org/mailarchive/users/2013-01/msg8.html a mention of poudriere being used on DragonFly/pkgsrc. Does anybody know of the state of this piece of software? The git repos I can find on google are stale links. As etoilebsd is referenced in the mail from DragonFly, I chose to ask here first. To all of you, have a nice week, cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: Lets eat Grandma. or Lets eat, Grandma. - Punctuation saves lives. A panda eats shoots and leaves. or A panda eats, shoots, and leaves. - Punctuation teaches proper biology. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. (RFC 1925) ___ 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
cross-compiling for arm6 with poudriere - has anybody done that?
I am cc'ing the persons originally describing a solution for my
problem.
I would like to cross-compile packages for FreeBSD on a Raspberry Pi
(arm6) on a stronger machine.
Various web-sources describe how to cross-compile kernel and world for
arm6/RaspberryPi [1,2,3]. Roughly a year ago, reportedly, ports have
been build successfully in chrooted environments, but have failed in
poudriere jails [4,5].
I have not found any more recent information on that approach. From
[5] i gather the issue in [4] has been fixed, so I will try to employ
poudriere to build packages for my raspberry on a stronger machine.
My idea is outlined as such: Build a 9.2-RELEASE jail, cross-compile a
arm6 obj tree in that jail and set poudriere make.conf options to
TARGET=arm TARGET_ARCH=armv6 TARGET_CPUARCH=armv6
PATH=/usr/obj/arm.armv6/usr/src/tmp/usr/bin:${PATH} CONFIGURE_HOST=amd64
STRIP_CMD=true
Has anybody tried a similar approach or can comment on my idea? Should
that be pointless, I do not want to waste much time trying.
[1] crochet-freebsd: https://github.com/kientzle/crochet-freebsd
[2] FreeBSD developer's notebook: http://kernelnomicon.org/?p=275
[3] How to install FreeBSD on a Raspberry Pi (or: How to cross compile
FreeBSD/arm): http://ogris.de/howtos/freebsd-raspberry.html
[4] yeren...@gmail.com, Ports cross-compiling:
http://lists.freebsd.org/pipermail/freebsd-hackers/2012-September/040428.html
[5] cr...@freebsd.org, Ports cross-compiling:
http://lists.freebsd.org/pipermail/freebsd-hackers/2012-November/041106.html
Many thanks,
--
Christopher
TZ: GMT + 1h
GnuPG/GPG: 0xE8DE2C14
FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013
c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE
Punctuation matters:
Lets eat Grandma or Lets eat, Grandma - Punctuation saves lives.
A panda eats shoots and leaves or A panda eats, shoots, and leaves -
Punctuation teaches proper biology.
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. (RFC 1925)
___
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: TeXLive build error on poudriere (Was: [patch included] teTeX and TeXLive)
On Tue, 21 May 2013 16:35:26 +0900 (JST) Hiroki Sato h...@freebsd.org wrote: Hiroki Sato h...@freebsd.org wrote in 20130519.070840.2265196291393572686@allbsd.org: hr Christopher J. Ruwe c...@cruwe.de wrote hr in 20130518025801.0659b...@dijkstra.cruwe.de: hr hr cj I have included the patches, they are rather trivial, hr cj although, I think, dirty. I have also included a complete hr cj logfile of a failed build for tex-formats. hr hr Where is the log file? hr hr What I need to investigate here is a build+install log for hr print/texlive-base on your environment. Running texconfig hr rehash in pre-install just hides your error and makes another hr problem. I committed a fix in r318651. Please try it if you got a build error when using poudriere. -- Hiroki Somehow, sometimes I am not getting through to the list. This works for me, too. Thank you very, very much for your effort. Thanks, -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC Punctuation matters: Lets eat Grandma or Lets eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. ___ 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: [patch included] teTeX and TeXLive
On Sun, 19 May 2013 07:08:40 +0900 (JST) Hiroki Sato h...@freebsd.org wrote: Christopher J. Ruwe c...@cruwe.de wrote in 20130518025801.0659b...@dijkstra.cruwe.de: cj I have included the patches, they are rather trivial, although, I cj think, dirty. I have also included a complete logfile of a failed cj build for tex-formats. Where is the log file? What I need to investigate here is a build+install log for print/texlive-base on your environment. Running texconfig rehash in pre-install just hides your error and makes another problem. -- Hiroki I am sorry, must have bungled the files. Here it is. What do you mean by build+install log? I hope it is the phase: partitions in poudriere's logfile. If it is not, could you help me producing these? Many thanks for your efforts. -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC Punctuation matters: Lets eat Grandma or Lets eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. ___ 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: [patch included] teTeX and TeXLive
On Fri, 17 May 2013 08:50:44 +0900 (JST)
Hiroki Sato h...@freebsd.org wrote:
Christopher J. Ruwe c...@cruwe.de wrote
in 20130517001153.1d7d4...@dijkstra.cruwe.de:
cj de Thank you very much, however I have a install failure on
cj de poudriere with ports tree up to date 5 minutes ago:
cj
cj Thank you for your report. I have received several reports
cj about install failures on poudriere and am investigating them.
cj
cj -- Hiroki
cj
cj Hello,
cj
cj I had exactly the same issue. I have a manual solution so far and
cj am trying out the automation from ports. I am posting my progress
cj hoping to save someone some time.
Could you try r318346?
-- Hiroki
Sorry, I have updated ports and built from r318394. That did not work
either. From the log:
=== Checking if print/tex-formats already installed
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found
(ls-R missing?).
fmtutil: config file `fmtutil.cnf' not found.
*** [do-fmtutil-amstex] Error code 1
My nightly poudriere-build after patching texlive-texmf resulted in
the same failures also.
Having had a look at the texlive-texmf-version.txz and the +MANIFEST
included therein showed that the post-install script I hoped to
include by my post-install target was not included in the package's
+MANIFEST.
After upgrading to r318394 and building and hitting the same error, I
had a look at texlive-base-version.txz and the +MANIFEST.
Therein, as post-install, is one line
/bin/rm -f share/texmf-var/ls-R
Isn't that what the error-message is complaining about?
I have a working solution for my installation, though. The idea is
similar to my attempt with texlive-texmf: I have included texconfig
rehash as pre-install or pre-build targets in the failing
packages. This results on tex-formats, tex-jadetex and auctex
compiling.
I have included the patches, they are rather trivial, although, I
think, dirty. I have also included a complete logfile of a failed
build for tex-formats.
I hope that helps.
--
Christopher J. Ruwe
TZ: GMT + 2h
GnuPG/GPG: 0xE8DE2C14
FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012
root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC
Punctuation matters:
Lets eat Grandma or Lets eat, Grandma - Punctuation saves lives.
A panda eats shoots and leaves or A panda eats, shoots, and leaves -
Punctuation teaches proper biology.
diff -uN /poudriere/ports/workstation/print/tex-jadetex/Makefile tree/print/tex-jadetex/Makefile
--- /poudriere/ports/workstation/print/tex-jadetex/Makefile 2013-05-17 14:34:13.546421312 +0200
+++ tree/print/tex-jadetex/Makefile 2013-05-17 14:54:01.191422074 +0200
@@ -26,6 +26,9 @@
NO_BUILD= yes
TEX_FORMATS= jadetex
+pre-install:
+ texconfig rehash
+
do-install:
${CAT} ${DISTDIR}/${DIST_SUBDIR}/${DISTNAME}${EXTRACT_SUFX} \
${EXTRACT_AFTER_ARGS}
diff -uN /poudriere/ports/workstation/print/auctex/Makefile tree/print/auctex/Makefile
--- /poudriere/ports/workstation/print/auctex/Makefile 2013-05-14 14:56:53.122240896 +0200
+++ tree/print/auctex/Makefile 2013-05-17 14:33:19.578422430 +0200
@@ -39,6 +39,9 @@
NOT_FOR_ARCHS= ia64
+pre-build:
+ texconfig rehash
+
post-install:
${MKTEXLSR} ${PREFIX}/${TEXMFDIR}
@${CAT} ${PKGMESSAGE}
diff -uN /poudriere/ports/workstation/print/auctex/Makefile~ tree/print/auctex/Makefile~
--- /poudriere/ports/workstation/print/auctex/Makefile~ 1970-01-01 01:00:00.0 +0100
+++ tree/print/auctex/Makefile~ 2013-05-17 13:49:04.413421912 +0200
@@ -0,0 +1,49 @@
+# Created by: Martin Kammerhofer
+# $FreeBSD: head/print/auctex/Makefile 317899 2013-05-11 17:58:55Z hrs $
+
+PORTNAME= auctex
+PORTVERSION= 11.87
+PORTREVISION= 1
+CATEGORIES= print elisp
+MASTER_SITES= ${MASTER_SITE_GNU}
+MASTER_SITE_SUBDIR= ${PORTNAME}
+PKGNAMESUFFIX= -${EMACS_PORT_NAME}
+
+MAINTAINER= h...@freebsd.org
+COMMENT= Integrated environment for writing LaTeX using GNU Emacs
+
+LICENSE= GPLv3
+
+USE_TEX= latex
+USE_GHOSTSCRIPT=yes
+GNU_CONFIGURE= yes
+CONFIGURE_ARGS= --with-lispdir=${PREFIX}/${LISPDIR} \
+ --with-auto-dir=${PREFIX}/${LISPDIR}/auctex/auto \
+ --with-texmf-dir=${PREFIX}/${TEXMFDIR}
+.if defined(NOPORTDOCS)
+MAKE_ENV= WITHOUT_AUCTEX_DOCSDIR=yes
+.else
+PORTDOCS= tex-ref.pdf
+.endif
+
+USE_EMACS= yes
+LISPDIR= ${EMACS_VERSION_SITE_LISPDIR}
+
+PLIST_SUB+= LISPDIR=${LISPDIR} \
+ TEXMFDIR=${TEXMFDIR} \
+ MKTEXLSR=${MKTEXLSR}
+INFO= auctex preview-latex
+
+TEXMFDIR= share/texmf
+MKTEXLSR= ${LOCALBASE}/bin/mktexlsr
+
+NOT_FOR_ARCHS= ia64
+
+pre-install:
+ texconfig rehash
+
+post-install:
+ ${MKTEXLSR} ${PREFIX}/${TEXMFDIR}
+ @${CAT} ${PKGMESSAGE}
+
+.include bsd.port.mk
Common subdirectories: /poudriere/ports/workstation/print/auctex/files and tree/print/auctex/files
diff -uN /poudriere/ports/workstation/print/tex-xmltex/Makefile tree/print/tex-xmltex/Makefile
--- /poudriere/ports/workstation/print/tex-xmltex/Makefile 2013-05-07 14:40:46.987298252 +0200
+++ tree/print/tex-xmltex/Makefile 2013-05-17 13:48
Re: [patch included] teTeX and TeXLive
On Fri, 17 May 2013 00:32:58 +0900 (JST) Hiroki Sato h...@freebsd.org wrote: David Demelier demelier.da...@gmail.com wrote in CAO+PfDe0nEdG=6zvnce90ktjsy4jyrk9jr1pmfbawrbj5cb...@mail.gmail.com: de 2013/5/12 Florent Peterschmitt flor...@peterschmitt.fr: de Le 11/05/2013 20:36, Hiroki Sato a écrit : de Hello, de de As you already noticed, TeXLive ports have been imported and de one can choose teTeX or TeXLive while the default value for de pre-compiled packages is still teTeX. de de If you want to use TeXLive, please try to use the following de knob: de de TEX_DEFAULT= texlive de de To do this, almost all of ports which use TeX will depend on de TeXLive. Although some ports which install a new TeX macro de package may not work because of incompatibility such as de difference of directory structure between the two, ones which de use TeX for typesetting should work fine. Ones to install de macro packages which were non-standard in teTeX but are de included in TeXLive will be fixed or removed. de de Please test TeXLive and send your failure report to me. Once de it is confirmed that TEX_DEFAULT=texlive works, I will switch de the default value from tetex to texlive at some point. de de de Thank you very much, however I have a install failure on poudriere de with ports tree up to date 5 minutes ago: Thank you for your report. I have received several reports about install failures on poudriere and am investigating them. -- Hiroki Hello, I had exactly the same issue. I have a manual solution so far and am trying out the automation from ports. I am posting my progress hoping to save someone some time. I reproduced the issue in an empty poudriere jail. After installing print/texlive-base and print/texlive-texmf via pkg add and $ cd /usr/ports/print/tex-formats $ make $ make install yields (taken only the last bit) ---Begin OPTIONS List--- ---End OPTIONS List--- ===phase: check-config == === ===phase: fetch== === Fetching all distfiles required by tex-formats-20120701 for building === ===phase: checksum == === Fetching all distfiles required by tex-formats-20120701 for building === ===phase: extract == === Fetching all distfiles required by tex-formats-20120701 for building === Extracting for tex-formats-20120701 === ===phase: patch== === Patching for tex-formats-20120701 === ===phase: configure== === Configuring for tex-formats-20120701 === ===phase: build== === ===phase: run-depends == === ===phase: install-mtree== === ===phase: install == === Installing for tex-formats-20120701 === Generating temporary packing list === Checking if print/tex-formats already installed tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found (ls-R missing?). fmtutil: config file `fmtutil.cnf' not found. *** [do-fmtutil-amstex] Error code 1 Stop in /usr/ports/print/tex-formats. running $ texconfig rehash $ make install solves the issue. I suspect my approach to constitute a dirty hack, but for the time being, I have added texconfig rehash as a post-install target to print/texlive-texmf. Compiling has started, I am off to bed now and will report tomorrow. Hope to save some people some time, even if what I am doing is actually not quite right. Cheers, -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC Punctuation matters: Lets eat Grandma or Lets eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. diff -uN /poudriere/ports/default/print/texlive-texmf/Makefile tree/print/texlive-texmf/Makefile --- /poudriere/ports/default/print/texlive-texmf/Makefile 2013-05-16 19:38:19.919421187 +0200 +++
Re: ports/174516: New port: java/glassfish for Glassfish Java EE reference implementation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 17 Dec 2012 22:38:21 -0500 Steve Wills swi...@freebsd.org wrote: Hi, Why the manual download? I don't see anything on the download site that makes me think this needs to be restricted, such as a forced license agreement before downloading. Steve Hello Steve, you are absolutely right that there is no legalese restriction or anything like it on the site. That's a workaround for a technical problem that I did not understand. When trying to do the automated download via the MASTERSITE, you will get: [cjr@dijkstra:java/glassfish]$ sudo make === glassfish-3.1.2.2 depends on file: /usr/local/sbin/pkg - found = glassfish-3.1.2.2.zip doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://download.java.net/glassfish/3.1.2.2/release/glassfish-3.1.2.2.zip fetch: http://download.java.net/glassfish/3.1.2.2/release/glassfish-3.1.2.2.zip: Moved Temporarily Fetching manually using the specified URL works, though. [cjr@dijkstra:java/glassfish]$ fetch http://download.java.net/glassfish/3.1.2.2/release/glassfish-3.1.2.2.zip glassfish-3.1.2.2.zip 2% of 83 MB 641 kBps So, this is the reason for the manual download. I am absolutely open to any other ideas to strip the port from this cludge. Cheers, - -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 Punctuation matters: Let's eat Grandma or Let's eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJQ0bY0AAoJEJTIKW/o3iwUikwP/2WeK1MqlqJxabcWda4mtfGb wzsdbUspSfpe/iQek2t4xajqdFlzN7w12DTao0dLmBMjMwXgQyO31TG+votqhzoz dt2OpcPYdLleONSkADitLVintDdCYwSDpw3EhnYsKhWyPysACsxznLLIpxI14sgL 5Jusjk7ui/ii3oyyQHmjXSUi0E3Kb3N6ffexctu7wiW63saONPLRAGLQnwxq+tRW vBrgkRojKbZ/cRJ7ZjWwgEzYxGJP0+RFeSdbEB5rI3qBFa15mbFryeN0ycZr972K AvjUwIPNIrc7GVpaYAdeK19vYPIoQWR0s4Qf7UHRlNgDCZjvVo1Y80SIOEcqfW3V ezf0ar1UbZgHe3v6mqAG6JAxeCLSGZ48uXGW3mH7QHcZMlU9gw1WW6FD5gkxanb8 YvDDXfz2cJ4t8Qz/yrvEssEapMHIsAyctSGPIu6R0aYEW1G7VT8SxUF6rXUb42Jd wIzjCII2zyFnZORA74x6SiagkRxjjIS04Re4JqHk9UubvTm+rekLZqD7+RpVVmTc ZDxPYoYeqW6M+mWeb2UZz5U6qo6PkZxnonqb8A+Kjy4qYtqThCpA8h6b0EChOX7V kWGvq51iqVFKhIsb96uOb7WiPv/4KOR2sOdUEfMVSXTDyDxo1sSN+nLlGbTQjCFE PkqSQ97+6CCox8nqOl0c =VP8V -END PGP SIGNATURE- ___ 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: no port for Glassfish - does it make sense to quickly write one?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 14 Dec 2012 18:44:45 + Chris Rees utis...@gmail.com wrote: On 14 Dec 2012 18:18, Christopher J. Ruwe c...@cruwe.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, using Netbeans I have learned that there is no port for the matching Glassfish application server. Having looked at the Netbeans port, making a port for Glassfish seems not to be a big deal, so I am a bit surprised that noone has stepped forward to contribute one. I am willing to be the one to step forward, however, I would like to ask beforehand whether there are any reasons I am not aware of that a port for Glassfish would be undesirable? I had often been surprised at the omission of very useful software from the Ports Tree. I don't know of any that have been actually rejected; it is simply a case of manpower vs the zillions of software packages out there. Before you rush to make a port, check there isn't a previous version in the Ports Tree that has been removed, or you may waste time reinventing the wheel :) http://people.freebsd.org/~crees/removed_ports/index.xml Chris Oops ... might be wise to address the list ... Thanks to all for the input. PR is ports/174516. Cheers, - - -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 Punctuation matters: Let's eat Grandma or Let's eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJQz1eiAAoJEJTIKW/o3iwULG4QAMO9Qo2fQLYhSmMKePACtkLQ qoXFGOAkROAbCAkxN1WaVrPvIvMT9D8CXsEL7mKIxyGwn2NCdVscQ08M6IlHVvnI Tj3+9ggjj1igOlDqD5P9SM9TE+m1THb/gzm07Tjw8BV5syTrmUWaJ7qy4oJhjTIn hykSCPjAMefGO8/VmPqgNiivaiuMKZtxR4SDPxEK77JrgKeNcMxq5bGHi39AZdvz 3XhYmvYmWmG1AOAOiNsv+l022Arx6ulqGRdrgNAiKOnseYkzh4Yo6R9S7J/CuWM1 ly/VIEVP5Dwz8Pqa/lYlaWgLeduaJ6Lfb9CT651YozvWDA3lfcACroM0zouOoAgV oqvOTQKTLvK6LW4jVstwZzGip5SpqR5iz3XUuZmjOKMEk+p5rrAz4cWsqxpeOLDc XoymuIDFuTOAzhLyvhMEOIWwQGo5I/lqsxZCVG/fV7KuSmzpxuUBKPCZjImlZEnj u+pYQDWLKIrd2NDVU0w1i68RIVZOGLg9ss0Bzm4d6XebAeJI7x7W27y+alAXv7tX cCGVMjW5TMe7S2C/lw42jvrEM72hmUicEyVOUnVzycs7q25vSYDocQewoDJlLWtM btxGh1y3Qf420AwhuBTcqTsuxxnrDC00f8eIb6H+gXXoml/eOsyzROhqGT6u5Oi+ vcfi3asgVuf1Xstcdivd =yJNu - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJQz3hIAAoJEJTIKW/o3iwUUGMQAK7SzC35Wr+4GtrRO/aEnukn PhoRBTXoPSUZQoaqJ1dmFBjek1+uZZkXL6OjKDLntf5g234hccncDDMI4ZiYgm1r zq3MF+Pk5Aw3cXyUSnQYD43z6Dwf9vaDgX+8UH4dmmRpvBP4qRu+Z3tZRwwMK84A 34/kbmzAuQPQs2HQbDCkna1CW6GVph2+mwM54J+qSr0jHY08utS3MGOGDBnym4Yl 7TyFhjWLlnsZHmB5Vr8T0vBxjlb/7AsnZ3OUrO/Ij5BfH1g2hmdlzb86SZKHYDfz TJzZpEd8bvf7AGmNC74OSOvv1ooQoaEcK+qQGKAOFzIIWer9TVXd8eUljpVXepkZ /aluDaSoZ252fshWzQuuxZQpbXQj5N56M6somDlg32nCoojOt2Rslro9mVRcFLnx 1ZEFLsacwWBMj17AqmwGSNjl45E/1SOxlMYBuHAedGcmHYhIPMyvnslZjUhOClGt T4BDS5bAIF/Y/G6r49+SbiCw42H1nHIR/KY0k9u36TrTHQqTZ+UW4ZMO8GYOb0Wl oTIQt7tVfYm3kAqw4Juj3Zqc0WM4aJ+Q1ZFqdgOhx1Vex2XMhnjwwrQnqsXzDp+w KQXfQRmfWkiZK6MZZ/rj3NuQ6o7LEa2XxtJK43MTqZC3Znszoaawtc4M5D0QBBHy e4216lHwfRklezztoF03 =7KoQ -END PGP SIGNATURE- ___ 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 port for Glassfish - does it make sense to quickly write one?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, using Netbeans I have learned that there is no port for the matching Glassfish application server. Having looked at the Netbeans port, making a port for Glassfish seems not to be a big deal, so I am a bit surprised that noone has stepped forward to contribute one. I am willing to be the one to step forward, however, I would like to ask beforehand whether there are any reasons I am not aware of that a port for Glassfish would be undesirable? Thanks for your consideration, cheers, - -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 Punctuation matters: Let's eat Grandma or Let's eat, Grandma - Punctuation saves lives. A panda eats shoots and leaves or A panda eats, shoots, and leaves - Punctuation teaches proper biology. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJQy21XAAoJEJTIKW/o3iwUyoUP/0zbnzwuMPtJG06ErnAa2+Tu 5AZ7vCFNu0+pIQ+dIhxhU4yQdw0F58lhD4aeZpUBqmoC00X+acRGhIEZY8U3Z11k DSGT+EcpX9SOlvb6174s1roURHDKR9DXQ3LJJylf/LeHM9xMXS5enWVEwMpXx8oQ scmrR04rDmCpZ6R+kyoq+OpKdy2WUQeVaMaWPS58FYXyjOwGnP0ke1YvqPhuyej/ DhLNWJTk44K/r2FRkSy19jDUPUYeSlcNqp7Tpv7JNdVqjj6UUhLo5uXTCrXR4nWY knsStPvFj9B3upI8VzgZL9BI/c7zhq+pITVPp45fJhWNpIyiYn6ZyjXAt8R2KG6p K0Vv0bxvUWQLX5odTSMTRctwhYwYsQl0AEVvl5rq8rw5NYUbGJ90HXVNQ7QwerAb jDiN+3O3ZQzs7nuRoTh7kQ2Tvt+L6xwiasmB3RMHYRB9+Xrv17yVLFrlcw5/m/OZ dkyu5XEygzx+/9AKm4ceTzBxNT6Cog/zG72OlL+5zKbZCN7hjNSi0ITmT9fnk76w JKxysFqzuuVfggCaCdUxztdfMZP1irpra4QTDoqBGT4UA0tXOfwpWXxa0Wo0B6Uy XSlmuH35h9DV30QnPo/iojV+c9R0MdH2MnrHYwZa6g6mdtJs5JjTAyM3YJU2VkP8 d7dZAj8QnPJmsID0BHX9 =Mejt -END PGP SIGNATURE- ___ 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: trying to build a port for vagrant and failing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 06 Nov 2012 17:58:42 -0500
Greg Larkin glar...@freebsd.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/6/12 4:00 PM, Christopher J. Ruwe wrote:
Currently, I am trying to write up a port for vagrant, a VirtualBox
managment thing (http://vagrantup.com/). I am failing with the
dependencies and would be grateful for some help.
I have
BUILD_DEPENDS=
minitar:${PORTSDIR}/archivers/rubygem-archive-tar-minitar \
RUN_DEPENDS=erubis:${PORTSDIR}/www/rubygem-erubis \
rubygem-childprocess=0.3.1:${PORTSDIR}/devel/rubygem-childprocess
\ rubygem-i18n=0.6.0:${PORTSDIR}/devel/rubygem-i18n \
rubygem-json=1.5.1:${PORTSDIR}/devel/rubygem-json \
rubygem-log4r=1.1.9:${PORTSDIR}/sysutils/rubygem-log4r \
rubygem-net-ssh=2.2.2:${PORTSDIR}/security/rubygem-net-ssh \
rubygem-net-scp=1.0.4:${PORTSDIR}/security/rubygem-net-scp
in the makefile.
From the build log (I am using poudriere for testing) I get
===phase:
run-depends== ===
rubygem-vagrant-1.0.5 depends on executable: erubis - not found
===Verifying install for erubis in
/usr/ports/www/rubygem-erubis === Installing existing package
/usr/ports/packages/All/rubygem-erubis-2.7.0.tbz === Returning
to build of rubygem-vagrant-1.0.5 === rubygem-vagrant-1.0.5
depends on package: rubygem-childprocess=0.3.1 - not found ===
Verifying install for rubygem-childprocess=0.3.1 in
/usr/ports/devel/rubygem-childprocess === Installing existing
package /usr/ports/packages/All/rubygem-childprocess-0.3.5.tbz
=== Returning to build of rubygem-vagrant-1.0.5 ===
rubygem-vagrant-1.0.5 depends on package: rubygem-i18n=0.6.0 -
not found ===Verifying install for rubygem-i18n=0.6.0 in
/usr/ports/devel/rubygem-i18n === Installing existing package
/usr/ports/packages/All/rubygem-i18n-0.6.0,2.tbz === Returning
to build of rubygem-vagrant-1.0.5 === rubygem-vagrant-1.0.5
depends on package: rubygem-json=1.5.1 - not found === Verifying
install for rubygem-json=1.5.1 in /usr/ports/devel/rubygem-json
=== Installing existing package
/usr/ports/packages/All/rubygem-json-1.7.5.tbz === Returning to
build of rubygem-vagrant-1.0.5 === rubygem-vagrant-1.0.5
depends on package: rubygem-log4r=1.1.9 - not found ===
Verifying install for rubygem-log4r=1.1.9 in
/usr/ports/sysutils/rubygem-log4r === Installing existing
package /usr/ports/packages/All/rubygem-log4r-1.1.10.tbz ===
Returning to build of rubygem-vagrant-1.0.5 ===
rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh=2.2.2 -
not found ===Verifying install for rubygem-net-ssh=2.2.2 in
/usr/ports/security/rubygem-net-ssh === Installing existing
package /usr/ports/packages/All/rubygem-net-ssh-2.1.4,2.tbz ===
Returning to build of rubygem-vagrant-1.0.5 ===
rubygem-vagrant-1.0.5 depends on package: rubygem-net-scp=1.0.4 -
not found ===Verifying install for rubygem-net-scp=1.0.4 in
/usr/ports/security/rubygem-net-scp === Installing existing
package /usr/ports/packages/All/rubygem-net-scp-1.0.4_1.tbz ===
Returning to build of rubygem-vagrant-1.0.5 ===
rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/gem18 - found
=== rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/ruby18
- found
===
So far so good. I noticed that rubygem-net-ssh-2.1.4.2 is supposed
to satisfy =rubygem-net-ssh-2.2.2, which I ignore for the while.
Now, building yields
===phase: install
== === Installing for
rubygem-vagrant-1.0.5 === rubygem-vagrant-1.0.5 depends on
executable: erubis - found === rubygem-vagrant-1.0.5 depends on
package: rubygem-childprocess=0.3.1 - found ===
rubygem-vagrant-1.0.5 depends on package: rubygem-i18n=0.6.0 -
found === rubygem-vagrant-1.0.5 depends on package:
rubygem-json=1.5.1 - found === rubygem-vagrant-1.0.5 depends
on package: rubygem-log4r=1.1.9 - found ===
rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh=2.2.2 -
found === rubygem-vagrant-1.0.5 depends on package:
rubygem-net-scp=1.0.4 - found === rubygem-vagrant-1.0.5 depends
on file: /usr/local/bin/gem18 - found === rubygem-vagrant-1.0.5
depends on file: /usr/local/bin/ruby18 - found === Generating
temporary packing list === Checking if emulators/rubygem-vagrant
already installed /usr/bin/env /usr/local/bin/gem18 install -l
--no-update-sources --no-ri --install-dir /usr/local/lib/r\
uby/gems/1.8 /usr/ports/distfiles/rubygem/vagrant-1.0.5.gem --
--build-args ERROR: While executing gem ... (Gem::DependencyError)
Unable to resolve dependencies: vagrant requires json (~ 1.5.1),
net-ssh (~ 2.2.2) *** Error code 1
The installation is right about net-ssh (confer above), but
definitely
trying to build a port for vagrant and failing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently, I am trying to write up a port for vagrant, a VirtualBox
managment thing (http://vagrantup.com/). I am failing with the
dependencies and would be grateful for some help.
I have
BUILD_DEPENDS= minitar:${PORTSDIR}/archivers/rubygem-archive-tar-minitar \
RUN_DEPENDS=erubis:${PORTSDIR}/www/rubygem-erubis \
rubygem-childprocess=0.3.1:${PORTSDIR}/devel/rubygem-childprocess \
rubygem-i18n=0.6.0:${PORTSDIR}/devel/rubygem-i18n \
rubygem-json=1.5.1:${PORTSDIR}/devel/rubygem-json \
rubygem-log4r=1.1.9:${PORTSDIR}/sysutils/rubygem-log4r \
rubygem-net-ssh=2.2.2:${PORTSDIR}/security/rubygem-net-ssh \
rubygem-net-scp=1.0.4:${PORTSDIR}/security/rubygem-net-scp
in the makefile.
- From the build log (I am using poudriere for testing) I get
===phase: run-depends==
=== rubygem-vagrant-1.0.5 depends on executable: erubis - not found
===Verifying install for erubis in /usr/ports/www/rubygem-erubis
=== Installing existing package
/usr/ports/packages/All/rubygem-erubis-2.7.0.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-childprocess=0.3.1 -
not found
===Verifying install for rubygem-childprocess=0.3.1 in
/usr/ports/devel/rubygem-childprocess
=== Installing existing package
/usr/ports/packages/All/rubygem-childprocess-0.3.5.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-i18n=0.6.0 - not found
===Verifying install for rubygem-i18n=0.6.0 in
/usr/ports/devel/rubygem-i18n
=== Installing existing package
/usr/ports/packages/All/rubygem-i18n-0.6.0,2.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-json=1.5.1 - not found
===Verifying install for rubygem-json=1.5.1 in
/usr/ports/devel/rubygem-json
=== Installing existing package
/usr/ports/packages/All/rubygem-json-1.7.5.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-log4r=1.1.9 - not
found
===Verifying install for rubygem-log4r=1.1.9 in
/usr/ports/sysutils/rubygem-log4r
=== Installing existing package
/usr/ports/packages/All/rubygem-log4r-1.1.10.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh=2.2.2 - not
found
===Verifying install for rubygem-net-ssh=2.2.2 in
/usr/ports/security/rubygem-net-ssh
=== Installing existing package
/usr/ports/packages/All/rubygem-net-ssh-2.1.4,2.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on package: rubygem-net-scp=1.0.4 - not
found
===Verifying install for rubygem-net-scp=1.0.4 in
/usr/ports/security/rubygem-net-scp
=== Installing existing package
/usr/ports/packages/All/rubygem-net-scp-1.0.4_1.tbz
=== Returning to build of rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/gem18 - found
=== rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/ruby18 - found
===
So far so good. I noticed that rubygem-net-ssh-2.1.4.2 is supposed to
satisfy =rubygem-net-ssh-2.2.2, which I ignore for the while.
Now, building yields
===phase: install ==
=== Installing for rubygem-vagrant-1.0.5
=== rubygem-vagrant-1.0.5 depends on executable: erubis - found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-childprocess=0.3.1 -
found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-i18n=0.6.0 - found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-json=1.5.1 - found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-log4r=1.1.9 - found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh=2.2.2 - found
=== rubygem-vagrant-1.0.5 depends on package: rubygem-net-scp=1.0.4 - found
=== rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/gem18 - found
=== rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/ruby18 - found
=== Generating temporary packing list
=== Checking if emulators/rubygem-vagrant already installed
/usr/bin/env /usr/local/bin/gem18 install -l --no-update-sources --no-ri
--install-dir /usr/local/lib/r\
uby/gems/1.8 /usr/ports/distfiles/rubygem/vagrant-1.0.5.gem -- --build-args
ERROR: While executing gem ... (Gem::DependencyError)
Unable to resolve dependencies: vagrant requires json (~ 1.5.1), net-ssh
(~ 2.2.2)
*** Error code 1
The installation is right about net-ssh (confer above), but definitely
not on json (1.7.5 1.5.1).
Can anybody hint me on a path to pursue to resolve that error?
Many thanks, cheers,
- --
Christopher
TZ: GMT + 2h
GnuPG/GPG: 0xE8DE2C14
Punctuation matters:
Let's eat Grandma or Let's eat, Grandma -
Re: math/ess CONFLICTS with devel/noweb, help with CONFLICTS= needed
On Sat, 09 Jun 2012 21:16:04 +0200 Mel Flynn rfl...@acsalaska.net wrote: On 9-6-2012 14:02, Matthew Seaman wrote: On 09/06/2012 12:25, Christopher J. Ruwe wrote: Thanks for your quick answer. Incidentally, I am at this moment also preparing a maintainer update for a new version of math/ess. Should I perpare two PRs, one for the CONFLICTS and one for the actual update or is it permissable to pack these two into one? It is best to put all the changes you want to make into one PR. That will get it processed most efficiently. And if there's a PR for the conflict problem, then mention in your update PR that this update closes PR xx. Thanks for reminding me, I would surely have forgotten. However, closing another PR does not apply, I was approached using private mail by a group apparently implementing something like a FreeBSD ports conflicts checker, who are systematically combing the ports tree for conflicts not yet known by the maintainers. Some maintainer update PRs already adress problems thus found. Thanks, cheers, -- Christopher J. Ruwe TZ: GMT + 1h signature.asc Description: PGP signature
Re: math/ess CONFLICTS with devel/noweb, help with CONFLICTS= needed
On Fri, 08 Jun 2012 22:03:49 +0100 Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 08/06/2012 19:41, Christopher J. Ruwe wrote: From http://www.freebsd.org/doc/en/books/porters-handbook/book.html#CONFLICTS I gather that I should add something like CONFLICTS=noweb Usually you'ld put something like: CONFLICTS=noweb-[0-9]* just to avoid accidentally matching a package which happened to have the string 'noweb' in its name. As it is, there is only devel/noweb that would match in the ports at the moment, but making that glob expression more specific is a good principle. to the Makefile. Am I correct in my assumption on using CONFLICTS instead of CONFLICTS_INSTALL and am I correct on the naming of noweb? CONFLICTS_INSTALL means you can build your package in the presence of the conflicting package. I'd guess that most of the conflicts in the ports tree are actually of this type: due to file name collisions in the installed packages. However, plain CONFLICTS is the popular choice for Makefiles, as it takes effect before you waste too much time building a package you can't install. In principle, CONFLICTS_INSTALL is frequently going to be the more correct choice. In practice, it seems to be up to the port maintainer to choose which to specify, and most just use plain CONFLICTS. Cheers, Matthew Thanks for your quick answer. Incidentally, I am at this moment also preparing a maintainer update for a new version of math/ess. Should I perpare two PRs, one for the CONFLICTS and one for the actual update or is it permissable to pack these two into one? Thanks, cheers, -- Christopher J. Ruwe TZ: GMT + 1h signature.asc Description: PGP signature
math/ess CONFLICTS with devel/noweb, help with CONFLICTS= needed
I am the (still inexperienced) maintainer of math/ess. Apparently, math/ess, an emacs mode for the statics lang R/S (Emacs Speaks Statistics) conflicts with the devel/noweb literate programming tool, more specifically, it's emacs mode. Both add a noweb-mode.el in share/emacs/site-lisp/, so that I will need to add a CONFLICTS-line to the port. From http://www.freebsd.org/doc/en/books/porters-handbook/book.html#CONFLICTS I gather that I should add something like CONFLICTS=noweb to the Makefile. Am I correct in my assumption on using CONFLICTS instead of CONFLICTS_INSTALL and am I correct on the naming of noweb? I hope this to be only a short term solution; as noweb amongst other languages also targets the R-language and the problem should in principle also apply to various Linux-distros, I have respectfully asked the Emacs Speaks Stastics-people if possibly the file (which is targeted at Sweave-integration) could be renamed. Anyways, the conflict should be marked and I would appreciate any input on my idea of writing a CONFLICTS-line. Thanks very much, cheers, -- Christopher J. Ruwe TZ: GMT + 1h ___ 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: [maintainer timeout] ports/160705: [patch] net/clamz: pkg-message on how to .amz-download
I submitted ports/160705 with attached patch on Tue, 13th Sep. The maintainer has timed out. In fact, an attempt to contact the maintainer beforehand was unsuccessful as well. Could you help me how to proceed to have my patch accepted? Thank you, cheers, -- Christopher J. Ruwe TZ GMT + 2 pgpmzbuNNmgYo.pgp Description: PGP signature
Re: [maintainer timeout] ports/160705: [patch] net/clamz: pkg-message on how to .amz-download
On Wed, 28 Sep 2011 19:33:31 +0100 Chris Rees cr...@freebsd.org wrote: On 28 September 2011 19:03, Christopher J. Ruwe c...@cruwe.de wrote: I submitted ports/160705 with attached patch on Tue, 13th Sep. The maintainer has timed out. In fact, an attempt to contact the maintainer beforehand was unsuccessful as well. Could you help me how to proceed to have my patch accepted? I've reopened the PR for you. By the way, please _never_ mess with the Subject: line when copying in bug-followup- it confuses GNATS and makes a junk PR that someone (usually linimon) has to tidy up :) 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 I am sorry. Thank you forpointing that out, I will not do it again. Cheers, -- Christopher J. Ruwe TZ GMT + 2 pgpGYnaA7CFFn.pgp Description: PGP signature
Re: Thank you (for making the ports less boring).
On Wed, 14 Sep 2011 00:20:13 +0200 Matthias Andree matthias.and...@gmx.de wrote: [...] I think you mentioned Arch Linux, further suggestions would be Gentoo Linux (you might like emerge), and further options are Debian GNU/kFreeBSD and using a FreeBSD base system with pkgsrc (rather than ports) on top. Came as Gentoo user, abandoned Gentoo because of to many quirks with updating packages (ebuilds). From my perspective, the situation is better here (FreeBSD). Cheers -- Christopher J. Ruwe TZ GMT + 2 pgpzNAteUNkv3.pgp Description: PGP signature
net/clamz should have pkg-message on how to set cookie to download amz-files
When reinstalling net/clamz I noticed that it is necessary to have a cookie from the local amazon site (amazon.com, amazon.de) confirming that the amazon downloader is installed when in fact it is not and you are using clamz. That information will only be accessible from the project website, http://code.google.com/p/clamz/, where users can also get a link to set the aformentioned cookie. It might be an idea to include a pkg-message in the port net/claz, for instance * For convenience, users may want to set a cookie using the link on http://code.google.com/p/clamz/. It is feasible to substitute the top level domain with the applicable amazon-TLD. Not having the cookie set, users will fail to download Amazon .amz files to download albums. * I do not want to be rude by making a PR without consulting you as maintainer and ports@ beforehand. Thank you for your consideration, cheers, -- Christopher J. Ruwe TZ GMT + 2 pkg-message Description: Binary data pgpoSPGmSX9dp.pgp Description: PGP signature
Re: FreeBSD ports you maintain which are out of date
On Sun, 24 Jul 2011 02:52:06 +0800 Martin Wilke m...@freebsd.org wrote: Hi, I finally managed to get portscout back on a stable server. I have removed all mail addresses from the old portscout to cleanup all the unused mail addresses. If you are a maintainer and would like to get a mail notification, please drop me a mail using your maintainer mail address and I'll add to the list. The RSS feature will be back very soon as well. Thanks to Martin Matuska (mm@) for hosting portscout now. Note that portscout.org will be rerouted as soon as possible. As for now, please use http://portscout.cc. - Martin Hello Martin, please include me on the list. Thanks for your effort, cheers -- Christopher J. Ruwe TZ GMT + 2 signature.asc Description: PGP signature
Re: PR ports/155331
On Tue, 21 Jun 2011 07:31:44 +0200 Simon Olofsson si...@olofsson.de wrote: Christopher, a nice tool to test your ports before submitting them is ports-mgmt/porttools: Just run `port test` and it'll run portlint and try to build you port etc. You can then submit your port with `port submit`. Read the manpage for all details. Simon ___ 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 Thank you for your replies. I will clean up my proposed port and will report back when done (hopefully by next week). Cheers, -- Christopher J. Ruwe TZ GMT + 2 ___ 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
PR ports/155331
Some time ago (actually, it has been the beginning of March), I submitted a proposition to include Emacs Speaks Statistics (ESS) (http://ess.r-project.org/), which is an interface to the language/statistics package R into ports. I have also included a probably erroneous patch (was my first one). I have asked for inclusion and correction and advice on the errors I am sure I have made. (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155331) I have not heard of any activity since then. I would be grateful to hear whether there is any interest in having ESS in ports. Of course I myself advocate for ESS, however, there might be valid reasons for choosing not to. Anyway, I would be glad if any decision could be reached on that subject. (I do not mean to be harsh, I just have found no other wording to formulate my request in a kinder fashion. If it sounds harsh, please do not be offended.) @miwi: Please take no offence of my public posting. I have been unsuccessful reaching you off list - which I hope you have not taken as spamming. Kind regards, -- Christopher J. Ruwe TZ GMT + 2 signature.asc Description: PGP signature
