Re: Conflict between lang/tcl85 and x11-toolkits/open-motif?
Yes the problem exists indeed. I suggest that you reconfigure (make config) in lang/tcl85 and unselect the TCL85_MAN option, then reinstall tcl85. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org from Chris Petrik c.petrik.s...@gmail.com: This can be fixed by using either the mentioned or if you require the tcl man pages add: WITHOUT_OPENMOTIF_MANUALS=yes to make.conf and rebuild open-motif. Chris I looked in the Makefile again and found that TCL85_MAN is off by default, Maybe I should stick to that and rebuild lang/tcl85 before retrying the rest of the upgrade with portmaster. But then how did I previously get away with installing man pages for both lang/tcl85 and x11-toolkits/open-motif? And why no warning in the Makefile or somewhere else? Why are these two ports set up to install man pages to the same directory, or are the man pages of the same name and same directory really the same? I just rebuilt lang/tcl85, took only about two minutes on new computer, was successful, after unselecting TCL85_MAN option. Tom ___ 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
Need help committing a new version of the port databases/percona55-server
Hi, The port databases/percona55-server has been deleted due to a typo which has never been fixed. Now I updated the port to the latest Percona 5.5 Server Release but I don't know how to commit it. I would be happy if somebody could help me. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Need help committing a new version of the port databases/percona55-server
On 10/24/2012 15:17, Benedikt Nießen wrote: Hi, Hi, The port databases/percona55-server has been deleted due to a typo which has never been fixed. Now I updated the port to the latest Percona 5.5 Server Release but I don't know how to commit it. I would be happy if somebody could help me. Thanks. I'm working on that. See http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164072, the patch in the PR doesn't have the latest version, yet but I have that in my svn tree and intend to commit the latest version of 5.5 and 5.6 after the release of FreeBSD 9.1. Florian ___ 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: [CFT] fusefs-ntfs and fusefs-libs updates
On 10/22/2012 10:05, Dominic Fandrey wrote: On my RELENG_9 system apart from ntfs non of the fusefs systems works any more: fusefs-smbnetfs-0.5.3a fusefs-sshfs-2.4 fusefs-wdfs-1.4.2_4 And concerning ntfs, ports/170695 is still present. All in all, I was much better off before the updates. Yes, I'm aware of the problems. We are working on making the fuse import from head work on older releases and update the fusefs-kmod with that. Also we are currently looking into the problem why certain fusefs filesystems don't work with the current versions in ports. Florian ___ 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
Index not being built again
After two days of having no ports to update on any systems I built the index myself and: ldns-1.6.13_1 needs updating (port has 1.6.14) libevent2-2.0.19 needs updating (port has 2.0.20) libvdpau-0.5 needs updating (port has 0.5_1) lighttpd-1.4.31_4 needs updating (port has 1.4.31_5) mosh-1.2.3needs updating (port has 1.2.3_1) openjdk6-b26_1needs updating (port has b26_2) portmaster-3.14_5 needs updating (port has 3.14_6) wireshark-1.8.2_1 needs updating (port has 1.8.3) xterm-284 needs updating (port has 284_1) Looks like the index build is broken again or I have some problem that is common to all of my systems. Since the recent issue, I suspect that it is the former. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
'pkg check -d' showing missing dependencies after upgrading lang/perl
I noticed at some point after installing and switching to pkgng, then
upgrading Perl from 5.12 to 5.14 with 'portmaster -o lang/perl5.14
lang/perl5.12', the 'pkg check -d' command would still list some ports
with perl5.12 as a missing dependency:
devel/gamin has a missing dependency: lang/perl5.12
devel/gio-fam-backend has a missing dependency: lang/perl5.12
irc/irssi has a missing dependency: lang/perl5.12
irc/irssi-scripts has a missing dependency: lang/perl5.12
mail/maildrop has a missing dependency: lang/perl5.12
misc/mc has a missing dependency: lang/perl5.12
mail/p5-Mail-SpamAssassin has a missing dependency: lang/perl5.12
Running 'pkg info -d irssi-scripts' would list both perl-5.12 and
perl-5.14.
Not being too familiar with pkgng's internals I decided I'd just do
pkg del gamin gio-fam-backend irssi (etc)
then rebuild reinstall those ports with portmaster, but presumably
there's a better alternative. ('pkg del perl5.12' wasn't it, though. :)
Also I can't say for certain whether I did something incorrectly
(wrong order?) with the Perl upgrade or if portmaster is to blame for
the duelling dependencies. So consider this more of an observation
than a bug report - at least until I can reproduce the problem in a VM
when I'm more awake. :-)
tl;dr: this may be my fault.
Regards
Andrew
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: 'pkg check -d' showing missing dependencies after upgrading lang/perl
On Thu, 25 Oct 2012 06:04:05 +1100 andrew clarke m...@ozzmosis.com wrote: I noticed at some point after installing and switching to pkgng, then upgrading Perl from 5.12 to 5.14 with 'portmaster -o lang/perl5.14 lang/perl5.12', the 'pkg check -d' command would still list some ports with perl5.12 as a missing dependency: I think this is a bug with portmaster. Portmaster should have run this command on your behalf: # pkg set -o lang/perl5.14:lang/perl5.12 This runs a query in the pkg sqlite database and update dependencies. This clearly didn't happen for you yet, so thats where your errors come from. There's a way to do this manually but I can't find it in my notes. Hopefully someone can quickly reply to you with the solution or perhaps I'll find it in a few minutes... ___ 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: 'pkg check -d' showing missing dependencies after upgrading lang/perl
On 24/10/2012 20:48, Mark Felder wrote: # pkg set -o lang/perl5.14:lang/perl5.12 This runs a query in the pkg sqlite database and update dependencies. This clearly didn't happen for you yet, so thats where your errors come from. There's a way to do this manually but I can't find it in my notes. Hopefully someone can quickly reply to you with the solution or perhaps I'll find it in a few minutes... uh... Typing that command /is/ the way to do it manually. Well, not exactly that command. The way it's written says take any dependency on perl5.14 and make it a dependency on perl5.12 instead. I believe the OP wanted the opposite, like so: # pkg set -o lang/perl5.12:lang/perl5.14 If you've installed perl5.14 locally, and consequently have PERL_VERSION=5.14.2 in /etc/make.conf then anything compiled by portmaster would depend on perl5.14. Stuff from before you installed perl5.14 would depend on whichever version you had installed previously, possibly perl5.12, and it is those you want to fix the dependency for. Note too, any actual perl modules will need more than just this fix: they need to be reinstalled or otherwise moved into the /usr/local/lib/perl5/5.14.2/ directory tree. perl-after-upgrade(1) is one way of doing that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Index not being built again
On Wed, Oct 24, 2012 at 10:21:45AM -0700, Kevin Oberman wrote: Looks like the index build is broken again The machine that builds the port index was physically moved on Sunday. Expect a few more interruptions before everything is sorted out. 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
Re: Cannot upgrade FlySpray
Nick Hilliard n...@foobar.org writes: On 23/10/2012 10:12, Andrea Venturoli wrote: 1 out of 1 hunks failed--saving rejects to includes/fix.inc.php.rej = Patch patch-includes-fix.inc.php failed to apply cleanly. *** Error code 1 Damn, the patch submission process turned all the CRLFs into LFs. Here's a new patch. I'll submit it to GNATS. Fixed in r306358 by setting the svn:eol-style property to CRLF for that file. ___ 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 in Google Code-In 2012? You can help too!
(cc'ing -ports and cutting most of the rest) From: Eitan Adler . On 24 October 2012 13:24, Fernando Apesteguía wrote: Also related to that, what about writing a section about redports[1] in the porter's handbook[2]? This is a good documentation task... but we need more *coding* tasks as well. We do need to port and test patch (1) from NetBSD or DragonFly to replace GNU patch, and this shouldn't be difficult. I would guess there are other interesting possibilities in the ports tree and new ports count as coding: http://wiki.freebsd.org/WantedPorts So i guess we need porting mentors. Pedro. ___ 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: Conflict between lang/tcl85 and x11-toolkits/open-motif?
On Wed, Oct 24, 2012 at 2:37 AM, Thomas Mueller muelle...@insightbb.com wrote: Yes the problem exists indeed. I suggest that you reconfigure (make config) in lang/tcl85 and unselect the TCL85_MAN option, then reinstall tcl85. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org from Chris Petrik c.petrik.s...@gmail.com: This can be fixed by using either the mentioned or if you require the tcl man pages add: WITHOUT_OPENMOTIF_MANUALS=yes to make.conf and rebuild open-motif. Chris I looked in the Makefile again and found that TCL85_MAN is off by default, Maybe I should stick to that and rebuild lang/tcl85 before retrying the rest of the upgrade with portmaster. But then how did I previously get away with installing man pages for both lang/tcl85 and x11-toolkits/open-motif? And why no warning in the Makefile or somewhere else? Why are these two ports set up to install man pages to the same directory, or are the man pages of the same name and same directory really the same? I just rebuilt lang/tcl85, took only about two minutes on new computer, was successful, after unselecting TCL85_MAN option. First, the old package system was not at all smart about such conflicts. That file would always be that of the last of the ports to be installed. With the flat file DB used by the old package system, this simply went unnoticed unless a human noticed it and did something. The new system uses sqlite as its database. As a result, it does notice if a port tries to install a file of the same name as one already installed, so shows a conflict. I suspect that there are a number of similar conflicts that will pop up now and then, especially for non-default options. The two files happen to have the same names and both seem to be installing in the normal locations. With the very large number of man pages involved, it's pretty easy to see why it went unnoticed. The only way it would notice would be if someone tried to bring up the man page for the first installed, got the wrong page and then spent the time to track down why.or, at least report it. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
