Re: security/gnupg and security/signing-party without X11 -- not possible now?
On Thu, 11 Dec 2014, Dmitry Morozovsky wrote: after some updates security/gnupg and security/signing-party stop building with OPTIONS_UNSET+= X11: [00:00:40] [02][00:00:01] Finished build of sysutils/rsnapshot: Ignored: is marked as broken: Does not build with Perl 5.18 or above [00:00:55] [01][00:00:16] Finished build of graphics/gtk-update-icon-cache: Failed: configure [00:00:56] [01][00:00:17] Skipping build of security/gnupg: Dependent port graphics/gtk-update-icon-cache failed [00:00:56] [01][00:00:17] Skipping build of x11-toolkits/gtk20: Dependent port graphics/gtk-update-icon-cache failed [00:00:56] [01][00:00:17] Skipping build of security/p5-GnuPG-Interface: Dependent port graphics/gtk-update-icon-cache failed [00:00:56] [01][00:00:17] Skipping build of security/pinentry: Dependent port graphics/gtk-update-icon-cache failed [00:00:56] [01][00:00:17] Skipping build of security/signing-party: Dependent port graphics/gtk-update-icon-cache failed any hints? default GTK2 dependency on security/pinentry was the source of problem; sorry for the noise -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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
Giving Up Maintainership
Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance. PY-APSW [1] APSW stands for Another Python SQLite Wrapper CALIBRE [2] Ebook management application MEGAGLEST [3] Open source 3D real-time strategy game MEGAGLEST-DATA [4] MegaGlest data files WESNOTH [5] Fantasy turn-based strategy game SHOWIMAGE [6] Simple KDE based image viewer ASSP [7] Anti-Spam SMTP Proxy P5-NET-SENDERBASE [8] Query the SenderBase service KNUTCLIENT-KDE4 [9] Visual client for UPS system NUT MOZPLUGGER [10] Framework for loading web content in external viewers I'm hoping/betting that some new volunteers will jump in and do better than I did on some of these. Sincerely, Rusty Nejdl Links: -- [1] http://www.freshports.org/databases/py-apsw/ [2] http://www.freshports.org/deskutils/calibre/ [3] http://www.freshports.org/games/megaglest/ [4] http://www.freshports.org/games/megaglest-data/ [5] http://www.freshports.org/games/wesnoth/ [6] http://www.freshports.org/graphics/showimage/ [7] http://www.freshports.org/mail/assp/ [8] http://www.freshports.org/mail/p5-Net-SenderBase/ [9] http://www.freshports.org/sysutils/knutclient-kde4/ [10] http://www.freshports.org/www/mozplugger/ ___ 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: Another pkg showstopper-- more information
On 12/12/2014 19:22, Jeffrey Bouquet wrote: On 12/12/14 10:25, Steven Hartland wrote: Unless I'm missing something you don't actually provide any information about the issue your actually seeing? I personally have already updated 10 or so boxes with a wide range of packages to pkg 1.4 and apart from a change with the handling of pkg upgrade -f pkg, which was an intended fix, I didn't have any problems. So not sure what your show stopper is or what you think could be tested more thoroughly (don't forget the call for testing did go out the other week, so looks like there was quite a bit of opportunity to get involved. Regards Steve On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote: Reverted to pkg, by build, and FORCE PKG REGISTER. pkgs still cannot be installed. Still stuck with ports ( however portupgrade -- non-packages -- seems to be working with this pkg pkg-devel downgrade ) (/ portmaster? == no, cannot get handle, lock on database) only. ..###...##... Should pkg and/or pkg-devel be more thoroughly tested before release into the tree? No other pkg usually hints at similar pkg system(s) breakage without a proven recovery/rollback procedure already documented... similar to what portupgrade does with its saving of shared libraries prior to upgrade of a port. ___ To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Bringing the list back into this, as its not my area: pkg install wants to install extra ports and abort traps You'll want to post details about, OS version, pkg version, and the exact error with any stack trace pkg add a pkg fetched file, cannot install it by package, wrong architecture (freebsd FreeBSD or vice versa, setting somewhere, etc) This doesn't make any sense to me, to others it may do but, always best to include proper steps and the output of the commands so people know exactly what your doing and the issue your seeing. portupgrade works on some ports still, but machine machine broken because of pkg issues and portupgrade -P broken similarly portmaster cannot install, convoluted error (lock on database and/or already installed error(s)) So the /var/db/pkg build machine functionality also the portmaster -P portupgrade -P are broken. Here. Maybe these could be tested on all architectures before each new package upgrade? Another layer of machines, so to speak, just because NOT Again you don't provide any real details of the issues, you might of well have said its broken of SQlite.. ... one used to not have to post to the list or even subscribe to have reliable LAN build set. ___ 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: Giving Up Maintainership
On 12/15/14 15:09, Rusty Nejdl wrote: Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance. CALIBRE [2] Ebook management application I'll take this one since I use it. I'll commit the maintainer change later today. Unluckily upgrading it will be a problem since new version depends on Python QT5 libraries. So I take a chance to ask: Is there any active work on creating ports for these? Who should I talk about this to? -- Guido Falsi madpi...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Giving Up Maintainership
On 2014-12-15 09:05, Guido Falsi wrote: On 12/15/14 15:09, Rusty Nejdl wrote: Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance. CALIBRE [2] Ebook management application I'll take this one since I use it. I'll commit the maintainer change later today. Unluckily upgrading it will be a problem since new version depends on Python QT5 libraries. So I take a chance to ask: Is there any active work on creating ports for these? Who should I talk about this to? I had to completely stop on Calibre because of the dependency on QT5. I did start on 2.1.0 and can send you the pieces if that will help. Rusty ___ 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: Another pkg showstopper-- more information
On 15/12/2014 15:19, Jeffrey Bouquet wrote: On 12/15/14 07:03, Steven Hartland wrote: On 12/12/2014 19:22, Jeffrey Bouquet wrote: On 12/12/14 10:25, Steven Hartland wrote: Unless I'm missing something you don't actually provide any information about the issue your actually seeing? I personally have already updated 10 or so boxes with a wide range of packages to pkg 1.4 and apart from a change with the handling of pkg upgrade -f pkg, which was an intended fix, I didn't have any problems. So not sure what your show stopper is or what you think could be tested more thoroughly (don't forget the call for testing did go out the other week, so looks like there was quite a bit of opportunity to get involved. Regards Steve On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote: Reverted to pkg, by build, and FORCE PKG REGISTER. pkgs still cannot be installed. Still stuck with ports ( however portupgrade -- non-packages -- seems to be working with this pkg pkg-devel downgrade ) (/ portmaster? == no, cannot get handle, lock on database) only. ..###...##... Should pkg and/or pkg-devel be more thoroughly tested before release into the tree? No other pkg usually hints at similar pkg system(s) breakage without a proven recovery/rollback procedure already documented... similar to what portupgrade does with its saving of shared libraries prior to upgrade of a port. ___ To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Bringing the list back into this, as its not my area: pkg install wants to install extra ports and abort traps You'll want to post details about, OS version, pkg version, and the exact error with any stack trace pkg add a pkg fetched file, cannot install it by package, wrong architecture (freebsd FreeBSD or vice versa, setting somewhere, etc) This doesn't make any sense to me, to others it may do but, always best to include proper steps and the output of the commands so people know exactly what your doing and the issue your seeing. portupgrade works on some ports still, but machine machine broken because of pkg issues and portupgrade -P broken similarly portmaster cannot install, convoluted error (lock on database and/or already installed error(s)) So the /var/db/pkg build machine functionality also the portmaster -P portupgrade -P are broken. Here. Maybe these could be tested on all architectures before each new package upgrade? Another layer of machines, so to speak, just because NOT Again you don't provide any real details of the issues, you might of well have said its broken of SQlite.. ... one used to not have to post to the list or even subscribe to have reliable LAN build set. I just updated 195471 bugzilla with a two week update. Fixed (temporarily?) the wrong architecture error with a missing pkg.conf file or reversion of one of them which was not missing, and have a workaround for the errors that remain, but it is tedious and worrisome, to say the least. Compared to how it could be with more SQL coders on board... maybe. Cant say I've ever had any issues, its always just worked, so worth posting your customizations. Made a post in a thread on the forums with the same information as the update in the PR above. For what it is worth... Just read the digest of Freebsd-STABLE that arrived today, others are also disillusioned with the priority given to pkg(ng) fixes for what was once a not-exact but very reliable packaging system across releases. Thanks for forwarding to the list. Unsure with each email sent precisely the number of recipients, but the fewer, the more likelihood the sometimes could not be sent appears... Mostly wishing for a procedure to fix it before needing to upgrade to v10 !! Never had to reinstall since v5.0x AFAIK... Copying to the list again. You might want to see if you have a reply to list or reply to all option in your mail client there Jeffrey, as I said this not my area but the pkgng are very good, so given the right information I'm sure someone will be able to help. Regards Steve ___ 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: Giving Up Maintainership
On Mon, Dec 15, 2014 at 08:09:48AM -0600, Rusty Nejdl wrote: Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance. Thanks for doing this rather than letting them tmie out and stress yourself. As a former portmgr I can say this makes portmgrs' lives easier :-) Please feel free to send PRs on anything you are still working on. Thanks. 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
poudriere: bulk.sh: cpdup: Permission denied
Hey folks, I'm trying to get started with poudriere. I pulled from the latest version 3.1.1 (9f9e43d3). However I'm getting the following error: build2# env ZPOOL=zroot ZROOTFS=/ports \ GIT_URL=http://gitweb.norse-data.com/git/ports.git \ ./src/bin/poudriere bulk \ -f test_pkg_list -j poudriere-appliance [00:00:00] Creating the reference jail... done [00:00:01] Mounting system devices for poudriere-appliance-default [00:00:01] Mounting ports/packages/distfiles [00:00:01] Using packages from previously failed build [00:00:01] Mounting packages from: /usr/local/poudriere/data/packages/poudriere-appliance-default /etc/resolv.conf - /usr/local/poudriere/data/.m/poudriere-appliance-default/ref/etc/resolv.conf [00:00:01] Starting jail poudriere-appliance-default /usr/home/alfred/poudriere/src/share/poudriere/bulk.sh: cpdup: Permission denied [00:00:01] Cleaning up [00:00:01] Umounting file systems build2# Is there a way to get line numbers or stack trace or any help debugging this issue? grep -r for cpdup hasn't been helpful. I guess I can truss(1)? (set -x isn't very helpful) Is there some magic I can put into PS4 so I can get file:line in the set -x output? Or is shell just ... limited? Other ideas on sorting out why this is happening? JFYI: here are my notes so far (there are patches to use git(1) as a FreeBSD source tree): env ZPOOL=zroot ZROOTFS=/ports ./src/bin/poudriere jail -j poudriere-appliance -m git+http -b master -U gitweb.norse-data.com/git/trueos.git -c -v TrueOS # make a default ports tree, makes things go easier env \ ZPOOL=zroot ZROOTFS=/ports \ GIT_URL=http://gitweb.norse-data.com/git/ports.git \ ./src/bin/poudriere ports -c # make the freebsd chroot for building using git, patches here https://github.com/splbio/poudriere/tree/3.1.1-git env \ ZPOOL=zroot ZROOTFS=/ports \ GIT_URL=http://gitweb.norse-data.com/git/ports.git \ ./src/bin/poudriere ports -c -p poudriere-appliance-ports -m git -B master # start the jail with the ports tree now... env ZPOOL=zroot ZROOTFS=/ports ./src/bin/poudriere jail -s -p poudriere-appliance-ports -j poudriere-appliance # now build? env \ ZPOOL=zroot ZROOTFS=/ports \ GIT_URL=http://gitweb.norse-data.com/git/ports.git \ ./src/bin/poudriere bulk \ -f test_pkg_list -j poudriere-appliance Thanks all, -Alfred ___ 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: bulk.sh: cpdup: Permission denied
On Mon, Dec 15, 2014 at 10:20 AM, Alfred Perlstein alf...@freebsd.org wrote: Hey folks, I'm trying to get started with poudriere. I pulled from the latest version 3.1.1 (9f9e43d3). /usr/home/alfred/poudriere/src/share/poudriere/bulk.sh: cpdup: Permission denied cpdup is a binary (not shell script) which gets installed as part of the poudriere distribution. It looks like you haven't got it installed right in your setup. I advise you to install the poudriere-devel port instead of pulling poudriere directly from git and building it. The other thing I would recommend that you do is to check out the freebsd10 branch from https://github.com/freenas/freenas repository, and build it once. Then look at:' https://github.com/freenas/freenas/tree/freebsd10/build/ports https://github.com/freenas/freenas/blob/freebsd10/build/ports/build-ports.sh to see how poudriere is invoked to build the ports in FreeNAS. If you want to enable tracing in poudriere, then use -x as the first flag write after poudiere. For example: poudriere -x bulk -- Craig ___ 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: Giving Up Maintainership
Guido Falsi madpi...@freebsd.org writes: Unluckily upgrading it will be a problem since new version depends on Python QT5 libraries. So I take a chance to ask: Is there any active work on creating ports for these? Who should I talk about this to? I don't think anyone is working on this at the moment. If you're willing to do it, please keep kde@ in the loop, as we maintain the existing PyQt4 ports and will probably end up either maintaining or touching the Qt5 ports a lot. ___ 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: Giving Up Maintainership
On 12/15/14 22:22, Raphael Kubo da Costa wrote: Guido Falsi madpi...@freebsd.org writes: Unluckily upgrading it will be a problem since new version depends on Python QT5 libraries. So I take a chance to ask: Is there any active work on creating ports for these? Who should I talk about this to? I don't think anyone is working on this at the moment. If you're willing to do it, please keep kde@ in the loop, as we maintain the existing PyQt4 ports and will probably end up either maintaining or touching the Qt5 ports a lot. I could make some work in this direction, but I don't know if I have the time and know how to do this all by myself. Anyway I'll mail kde@ if and when I have something which resembles a plan :) -- Guido Falsi m...@madpilot.net ___ 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: bulk.sh: cpdup: Permission denied
Thanks Craig. Replies below. On Dec 15, 2014, at 12:21 PM, Craig Rodrigues rodr...@freebsd.org wrote: On Mon, Dec 15, 2014 at 10:20 AM, Alfred Perlstein alf...@freebsd.org wrote: Hey folks, I'm trying to get started with poudriere. I pulled from the latest version 3.1.1 (9f9e43d3). /usr/home/alfred/poudriere/src/share/poudriere/bulk.sh: cpdup: Permission denied cpdup is a binary (not shell script) which gets installed as part of the poudriere distribution. It looks like you haven't got it installed right in your setup. I advise you to install the poudriere-devel port instead of pulling poudriere directly from git and building it. That won't work as I'm doing development on poudriere. The other thing I would recommend that you do is to check out the freebsd10 branch from https://github.com/freenas/freenas repository, and build it once. Then look at:' https://github.com/freenas/freenas/tree/freebsd10/build/ports https://github.com/freenas/freenas/blob/freebsd10/build/ports/build-ports.sh to see how poudriere is invoked to build the ports in FreeNAS. Will do, thanks for the pointer. If you want to enable tracing in poudriere, then use -x as the first flag write after poudiere. For example: poudriere -x bulk Yup, done that already. Problem is that Bourne shell debugging is terrible. -x does not give line numbers, nor functions, nor files. Spent some time trying to do things using PS4 variable but it was for naught because $LINENO and $0 don't work properly in PS4 as far as I can tell in our version of Bourne shell. Bash on the other hand seems to have better support for expanding useful things into PS4, however it's still very poor as compared to the facilities of let's say Python or Ruby or probably even Javascript. I hear now that poudriere is being migrated to C of all things which IMO is a huge mistake. Almost as bad as having it in shell. As someone that would *like* to contribute to poudriere, (see my github which has patches already) I'm hoping the maintainers can look at using a high level language that offers debugging as well as built in string safety as opposed to going to an even more low level system. Moving to C would make that just more pain than it seems worth. -Alfred. -- Craig ___ 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: bulk.sh: cpdup: Permission denied
On Mon, Dec 15, 2014 at 1:50 PM, Alfred Perlstein bri...@mu.org wrote: Spent some time trying to do things using PS4 variable but it was for naught because $LINENO and $0 don't work properly in PS4 as far as I can tell in our version of Bourne shell. Bash on the other hand seems to have better support for expanding useful things into PS4, however it's still very poor as compared to the facilities of let's say Python or Ruby or probably even Javascript. I hear now that poudriere is being migrated to C of all things which IMO is a huge mistake. Almost as bad as having it in shell. I'm not 100% sure of the history, but I think that poudriere was originally intended to replace the scripts that the portmgr team used to build the official FreeBSD ports tree. It was written to not depend on any other ports or scripting language not in the FreeBSD base system to avoid breaking in case the ports broke. Most of it is in Bourne shell, but cpdup is in C for performance. As it is right now, poudriere I think meets the needs of the portmgr team, with those constraints. poudriere has become a generally useful tool for anyone (not just portmgr) to build the FreeBSD ports tree, because of its intimate knowledge of the FreeBSD ports Makefile rules and dependencies. That's why I integrated it into the FreeNAS build, which built around 200 ports. For the general user, having poudriere (or a similar tool) in another high level language would be perfectly fine. If there was a Python, ruby, node.js version of poudriere that worked, I would have integrated it into the FreeNAS build, with no problem. Lately, I have been building packages for Debian systems, and their build scripts are a mix of Python and bash scripts. I've also been building packages for Homebrew on MacOS X which is based on a Ruby build system. While each system has its quirks, both systems do work and are actively maintained, and life goes on. It would definitely be possible to have a poudriere-like tool written in another high-level language. The implementation details of poudriere basically boils down to the requirements and personal preferences/biases of the people working on these tools. -- Craig ___ 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: autoconf automake~pkg-renamed cruft in pkg db - how to fix?
On Mon, Dec 15, 2014 at 04:38:02PM -0700, Mike Brown wrote: One of the ports on my system needs automake, but somehow its name has been butchered in the pkg database. === Launching 'make checksum' for net/GeoIP in background === Gathering dependency list for net/GeoIP from ports === Launching child to update automake~pkg-renamed~8513-1.14 to automake-1.14_1 === GeoIP-1.6.2_1 automake~pkg-renamed~8513-1.14 (1/1) === No valid installed port, or port directory given === Try portmaster --help === Update for automake~pkg-renamed~8513-1.14 failed === Aborting update # pkg info auto\* autoconf-wrapper-20130530 autoconf~pkg-renamed~9939-2.69 autoconf~pkg-renamed~CD89-2.13.000227_6 automake-wrapper-20130530 automake~pkg-renamed~8513-1.14 automake~pkg-renamed~D475-1.4.6_6 How do I clean up this mess? You were having some very very old packages installed which have named collision this has been fixed during the last years. pkg 1.4 automatically renamed the collision to avoir upgrade failures. To fix that you can pkg delete them and reinstall automake and autoconf which will give you only the latest packages (where the name is fixed) regards, Bapt pgpod2Fbz5nTs.pgp Description: PGP signature
Just a local workaround for the not-finishing pkg install PR 195471
___ 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
Just a *local* workaround for the not-finishing pkg install PR 195471
[ Sorry for the duplicate empty message!] [ Just for the archives... ] [ More of a thumbs up to portupgrade than a reposting of the problem...] Seems to work handily... for the time being anyway. #portupgrade -P [ -i ] [port ] [2nd port ] [ grep lib somefileofports.dat ] once one has made a symlink to /usr/ports/packages/All [test first] making it reference /var/cache/pkg [tested it here every which way first... ] ___ 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
Discrepancy in postgresql entry in UPDATING
The entry reads: 20141208: AFFECTS: users of databases/postgresql??-(server|client) AUTHOR: mar...@freebsd.org PostgreSQL version 9.3 is now the default. To upgrade from a version lower than 9.3, follow the instructions on the PostgreSQL.org website. http://www.postgresql.org/docs/9.3/interactive/upgrading.html Please note that the pg_upgrade program is installed by the databases/postgresql93-contrib port When using binary packages, if you only use the client port, you can issue the following command to follow the default version: # pkg set -o databases/postgresql92-client:databases/postgresql93-client The problem is pg_upgrade requires both the old and new versions be installed concurrently--something pkg/ports can't do. So how are we supposed to upgrade? ___ 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
