Re: List of packages upgraded last time `pkg upgrade` was executed
On Wed, 27 Jan 2021, Yasuhiro Kimura wrote:
From: Freddie Cash
Subject: Re: List of packages upgraded last time `pkg upgrade` was executed
Date: Tue, 26 Jan 2021 17:26:29 -0800
/var/log/messages and I think /var/log/daemon include the output of the pkg
commands. If you have the log files backed up from the last time it was
run, you could grep for pkg in those.
No idea if this info is also stored in the sqlite databases pkg uses.
Thank you for reply. But my intention is to write shell script that
gets the list of upgraded packages and does something by using
it. Because of that the list need to be gotton without any user
interaction. So unfortunately your method is not applicable to my
case.
Try something like this as a starting point for a shell script:
sqlite3 /var/db/pkg/local.sqlite \
"select datetime(time,'unixepoch'),origin,version from packages \
where datetime(time,'unixepoch')>=date('now','-7 day') \
order by time desc"
___
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: pkg feature request
On Wednesday, 12 August 2020 05:05:17 BST Tatsuki Makino wrote: > But it seems to be a mixture of various revisions because poudriere is > building it. > svnlite up -q -r COMMITTED $PORTSDIR/category/name seems to be a > revision of the package when it was built. What would be needed would be for pkg to provide the revision number of the ports tree used by poudriere at the time of the build, not the revision of each individual port. For example for 12.1- RELEASE amd64 http://beefy6.nyi.freebsd.org/jail.html?mastername=121amd64-default[1] shows that at the time of writing this email the latest completed build is 544349 and there is a build run in progress for 544776. If this revision number could be stored as a property of the repository then pkg could have a command (e.g. 'pkg revno') which would currently return 544349. After the current build has completed and propagated to the repository then 'pkg revno' would return 544776 after the next time I run 'pkg update'. I'm already using a manual version of this process. If today I needed to build one of the few ports for which I don't use packages I would get the revision number of the latest poudriere build and run 'svnlite up -q -r 544349 /usr/ports' to sync my ports tree with the version used for the repository. Providing I allow enough time for the new build to be transferred to the FreeBSD repository before doing this it works fine. It would, of course, be much better if I could obtain the revision number of the repository directly from pkg. The real icing on the cake would be to have a command 'pkg sync-ports' which would use the revision information to upgrade the ports tree in one go without needing to manually run svn. -- Mike Clarke [1] http://beefy6.nyi.freebsd.org/jail.html?mastername=121amd64-default ___ 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: [HEADS UP] Planned deprecation of portsnap
On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote: > What I'd like to see is a simple way to update the ports tree to match > what was used to build the current packages in the repository. Something I've felt in need of for a long time, and suggested from time to time in the past. What we need is a pkg command which returns the revision number of the ports tree which was used to build the current repository. When provided with that information I could run "svnlite up -q -r $REV $PORTSDIR" to keep my ports and packages in sync. -- Mike Clarke ___ 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"
PR commit request
Please could a committer take a look at https://bugs.freebsd.org/bugzilla/ show_bug.cgi?id=247771[1] - mail/filtermail: Fails to build. I provided maintainer feedback a month ago with an updated patch which should solve the problem but the status still shows as 'maintainer- feedback' and it hasn't been assigned to anybody. -- Mike Clarke [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247771 ___ 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: mail/filtermail fails to build with 13.0-CURRENT
On Monday, 29 June 2020 21:43:28 BST Jung-uk Kim wrote:
> I just checked the upstream and it seems the problem does not exist any
> more after this commit.
>
> https://sourceforge.net/p/mailfilter/code/ci/52e08609da8133e2cc0acd1961ebc1
> e1537f0c54
>
> Most applications should have similar fixes because all major Linux
> distros are using Flex 2.6 now. If you are maintaining such
> applications, you should update the ports, add devel/flex to
> BUILD_DEPENDS, and set FLEX=${LOCALBASE}/bin/flex for releng/stable
> branches.
Thanks Jung-uk Kim, your info got me moving along the right track.
I've patched the port to upgrade it to 0.8.6 and incorporated your
suggestions about devel/flex for releng/stable. I also needed to
conditionally add CPPFLAGS+= -I${LOCALBASE}/include/flex to prevent flex
2.5.37 from the rev 12 base system from being used.
With these changes filtermail 0.8.6 now builds and works on both 12.1-RELEASE
and 13.0-CURRENT but before I go ahead and submit a patch there's a point I'm
a bit concerned about.
I've successfully followed all the steps for testing the port in section 3.4
of the Porter's Handbook except for the final step, make package (as user),
which failed. Initially it was because I did not have write access to the
port directory. After temporarily running chmod a+w filtermail I was able to
build the package but the final step of copying it to /usr/ports/packages/
All/filtermail-0.8.6.txz not surprisingly failed. I'm puzzled why there is
this requirement to be able to build as a user when the default permissions
on the ports directories prevent this for unprivileged users.
I'm fairly confident that my patches to the port are working OK but this is a
task I rarely get involved with so I've appended the Makefile to this email
in case anybody can spot anything I've not done correctly.
I made the dependency of textproc/flex conditional on OSVERSION < 130. I
suppose that will only be correct if flex was in base from the start of 13.0-
CURRENT, if not is there a more specific value I should test against?
# $FreeBSD: head/mail/filtermail/Makefile 436247 2017-03-15 14:45:30Z mat $
PORTNAME= filtermail
PORTVERSION=0.8.6
CATEGORIES= mail
MASTER_SITES= http://sourceforge.net/projects/mailfilter/files/Mailfilter/
DISTNAME= mailfilter-${PORTVERSION}
MAINTAINER= jmc-filterm...@milibyte.co.uk
COMMENT=Filter mail on a POP3 server: saves downloading spam
LICENSE=GPLv3
.include
.if ${OPSYS} == FreeBSD && ${OSVERSION} < 130
BUILD_DEPENDS= ${LOCALBASE}/bin/flex:textproc/flex
.endif
USES= bison gmake ssl
# This port is filtermail, but the author called it mailfilter. To avoid a
# clash with another port called mailfilter, we change all files
# installed by this port from the form *mailfilter* to the form
# *filtermail*, and similarly the names in the man pages.
EXTRACT_CMD=${GZIP_CMD}
EXTRACT_BEFORE_ARGS=-dc
EXTRACT_AFTER_ARGS= | ${SED} 's/[mM][aA][iI][lL][fF][iI][lL][tT][eE][rR]/
filtermail/g' | ${TAR} -xf -
WRKSRC= ${WRKDIR}/${PORTNAME}-${PORTVERSION}
GNU_CONFIGURE= yes
MAKE_JOBS_UNSAFE= yes
CPPFLAGS+= -I${LOCALBASE}/include
.if ${OPSYS} == FreeBSD && ${OSVERSION} < 130
CPPFLAGS+= -I${LOCALBASE}/include/flex
FLEX=${LOCALBASE}/bin/flex
.endif
LDFLAGS+= -L${LOCALBASE}/lib
PLIST_FILES=bin/${PORTNAME} \
man/man1/${PORTNAME}.1.gz \
man/man5/${PORTNAME}ex.5.gz \
man/man5/${PORTNAME}rc.5.gz
post-patch:
@${REINPLACE_CMD} -e 's|filtermail.sourceforge|
mailfilter.sourceforge|g' ${WRKSRC}/README
post-extract:
@${RM} ${WRKSRC}/src/getopt.h
.include
--
Mike Clarke
___
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: mail/filtermail fails to build with 13.0-CURRENT
On Saturday, 27 June 2020 17:23:26 BST Kurt Jaeger wrote: > > As someone with very little experience with C++ I'd welcome advice on how > > to fix this for 13.0- CURRENT. It builds without problem on 12.1-RELEASE > > Did you build it in poudriere ? No, the reason I'm trying to get it to work is because it recently failed to build on the FreeBSD package build server with poudriere for 13.0-CURRENT http:// beefy18.nyi.freebsd.org/data/head-amd64-default/p540358_s362600/logs/ filtermail-0.8.3_1.log[1] . I've tried building on my home PC using make and get the same error. -- Mike Clarke [1] http://beefy18.nyi.freebsd.org/data/head-amd64-default/p540358_s362600/logs/ filtermail-0.8.3_1.log ___ 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"
mail/filtermail fails to build with 13.0-CURRENT
As someone with very little experience with C++ I'd welcome advice on how to fix this for 13.0- CURRENT. It builds without problem on 12.1-RELEASE Making all in src gmake[3]: Entering directory '/usr/ports/mail/filtermail/work/filtermail-0.8.3/src' c++ -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I. -I../include -I.. -DLOCALEDIR=\"/usr/local/share/ locale\" -I../intl -I.. -I../include -I. -I/usr/local/include -Wall -O2 -pipe -fstack-protector-strong -fno- strict-aliasing -MT rcfile.o -MD -MP -MF .deps/rcfile.Tpo -c -o rcfile.o rcfile.cc rcfile.ll:151:14: error: no viable overloaded '=' yyin = new ifstream (sub_file.c_str ()); ^ /usr/include/c++/v1/istream:200:20: note: candidate function not viable: no known conversion from 'std::__1::ifstream *' (aka 'basic_ifstream *') to 'std::__1::basic_istream' for 1st argument; dereference the argument with * basic_istream& operator=(basic_istream&& __rhs); ^ /usr/include/c++/v1/istream:211:20: note: candidate function not viable: no known conversion from 'std::__1::ifstream *' (aka 'basic_ifstream *') to 'const std::__1::basic_istream' for 1st argument; dereference the argument with * basic_istream& operator=(const basic_istream& __rhs) = delete; ^ rcfile.ll:153:15: error: cannot cast from type 'std::istream' (aka 'basic_istream') to pointer type 'std::__1::ifstream *' (aka 'basic_ifstream *') if (!((ifstream*) yyin)->is_open ()) ^~~~ 2 errors generated. gmake[3]: *** [Makefile:453: rcfile.o] Error 1 gmake[3]: Leaving directory '/usr/ports/mail/filtermail/work/filtermail-0.8.3/src' gmake[2]: *** [Makefile:382: all-recursive] Error 1 gmake[2]: Leaving directory '/usr/ports/mail/filtermail/work/filtermail-0.8.3' gmake[1]: *** [Makefile:320: all] Error 2 gmake[1]: Leaving directory '/usr/ports/mail/filtermail/work/filtermail-0.8.3' *** Error code 1 -- Mike Clarke ___ 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: Lsof port can't build (again)
Hi, On 15/06/2020 02:52, @lbutlr wrote: When trying to update lsof on FreeBSD 12.1-RELEASE-p5 GENERIC i386 I get the following fatal error: /usr/src/sys/sys/pcpu.h:224:10: fatal error: 'machine/pcpu_aux.h' file not found #include ^~~~ That is not present in the file on relent/12.1, which is probably the same as yours. I suspect that you have an out-of-date /usr/src. (This does beg the question of why your attempt to build lsof is looking under /usr/src, but I'm not going there). What is the output of "egrep '^(TYPE|REVISION|BRANCH)' /usr/src/sys/conf/newvers.sh" ? How do you maintain the src tree on your machine? Cheers, Mike ___ 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: Some KDE4 desktop effects not working after pkg upgrade
On Monday 16 April 2018 10:28:42 Greg Rivers wrote: > I reported the same issue on the FreeBSD KDE mailing list the other day: > <https://mail.kde.org/pipermail/kde-freebsd/2018-April/027704.html> > > No responses yet. Thanks for the info, I'll keep an eye on that thread in the FreeBSD KDE list. -- Mike Clarke ___ 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"
Some KDE4 desktop effects not working after pkg upgrade
0.2_3 -> 6.0.3
ca_root_nss: 3.36 -> 3.36.1
brotli: 1.0.2,1 -> 1.0.4,1
baloo-kde4: 4.14.3_8 -> 4.14.3_9
ark-kde4: 4.14.3_4 -> 4.14.3_5
Number of packages to be installed: 55
Number of packages to be upgraded: 56
--
Mike Clarke
___
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: When does a newly committed port become installable via 'pkg'?
On Sunday 28 Jan 2018 13:01:44 Freddie Cash wrote: > You can switch to the "latest" repo, which gets rebuilt every Tuesday, I > believe. It's more frequent than that now. Packages for 111amd64- default seem to be getting updated about every 2 days. -- Mike Clarke ___ 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: When does a newly committed port become installable via 'pkg'?
On Sunday 28 Jan 2018 17:01:09 James E Keenan wrote:
> Thanks. Upon reading 'man 5 pkg.conf', which identified the system-wide
> configuration file as being located as /etc/pkg/FreeBSD.conf. That file
> does contain this entry:
>
> #
> url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly;,
> #
>
> That file also states that to modify that file, create a new file as:
>
> #
> /usr/local/etc/pkg/repos/FreeBSD.conf
> #
>
> I have done so, and in that file I have placed this entry:
>
>
> FreeBSD: {
>url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
>mirror_type: "srv",
>signature_type: "fingerprints",
>fingerprints: "/usr/share/keys/pkg",
>enabled: yes
> }
> #
>
> Should that suffice?
That would work but it's better to leave /etc/pkg/FreeBSD.conf untouched and
create
/usr/local/etc/pkg/repos/FreeBSD.conf with the following:
FreeBSD: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
}
That way your setting doesn't get wiped out with the next update to base.
--
Mike Clarke
___
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"
lang/ghc -8.0.2_2 mismatched checksums
My daily periodic security run comes up with with these errors: Checking for packages with mismatched checksums: ghc-8.0.2_2: /usr/local/bin/haddock ghc-8.0.2_2: /usr/local/lib/ghc-8.0.2/package.conf.d/package.cache ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-33.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-36.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-43.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-46.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-58.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-60.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-61.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-62.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-92.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-A.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-All.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-B.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-C.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-D.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-E.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-F.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-G.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-H.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-I.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-J.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-K.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-L.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-M.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-N.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-O.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-P.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Q.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-R.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-S.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-T.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-U.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-V.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-W.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Y.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Z.html ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/index.html -- End of security output -- I've reinstalled the package but still get the errors. curlew:/home/mike% pkg info ghc ghc-8.0.2_2 Name : ghc Version: 8.0.2_2 Installed on : Mon Jan 1 09:35:19 2018 GMT Origin : lang/ghc Architecture : FreeBSD:11:amd64 Prefix : /usr/local Categories : haskell lang Licenses : BSD3CLAUSE Maintainer : hask...@freebsd.org WWW: http://www.haskell.org/ghc/ Comment: Compiler for the functional language Haskell Options: BOOT : off BOOTH : off DOCS : on DYNAMIC: on PROFILE: on Shared Libs required: libgmp.so.10 libiconv.so.2 libcharset.so.1 Shared Libs provided: libHSrts_thr-ghc8.0.2.so libHSrts-ghc8.0.2.so libHSfilepath-1.4.1.1-ghc8.0.2.so libHSghc-boot-th-8.0.2-ghc8.0.2.so libffi.so.6 libHSghc-prim-0.5.0.0-ghc8.0.2.so libHSCabal-1.24.2.0-ghc8.0.2.so libHSrts_thr_debug-ghc8.0.2.so libHSrts_debug-ghc8.0.2.so libHSpretty-1.1.3.3-ghc8.0.2.so libHSarray-0.5.1.1-ghc8.0.2.so libHStransformers-0.5.2.0-ghc8.0.2.so libHShoopl-3.10.2.1-ghc8.0.2.so libHShpc-0.6.0.3-ghc8.0.2.so libHSghc-boot-8.0.2-ghc8.0.2.so libHStemplate-haskell-2.11.1.0-ghc8.0.2.so libHSghc-8.0.2-ghc8.0.2.so libHSbinary-0.8.3.0-ghc8.0.2.so libHSghci-8.0.2-ghc8.0.2.so libHSdirectory-1.3.0.0-ghc8.0.2.so libHShaskeline-0.7.3.0-ghc8.0.2.so libHSunix-2.7.2.1-ghc8.0.2.so libHStime-1.6.0.1-ghc8.0.2.so libHSrts_l-ghc8.0.2.so libHSprocess-1.4.3.0-ghc8.0.2.so libHSbytestring-0.10.8.1-ghc8.0.2.so libHSrts_thr_l-ghc8.0.2.so libHSdeepseq-1.4.2.0-ghc8.0.2.so libHSinteger-gmp-1.0.0.1-ghc8.0.2.so libHScontainers-0.5.7.1-ghc8.0.2.so libHSterminfo-0.4.0.2-ghc8.0.2.so libHSbase-4.9.1.0-ghc8.0.2.so
Re: portmaster, portupgrade, etc
On Friday 06 Oct 2017 00:29:17 tech-lists wrote: > I'd use packages more were it not for the received wisdom that mixing > packages and ports is a Bad Thing (tm) - is this still the case? The main thing is to keep your ports tree synchronised with the version used for the package repository. I find that the script at https://gist.github.com/reedacartwright/8622973baf89b263a6d7 is a useful tool for this. The script hasn't been updated beyond 10.x-RELEASE so if you're running 11.x- RELEASE you need to patch the script by adding the following line: 110amd64-default) PKG_SERVER=beefy9.nyi.freebsd.org ;; If only pkg could be made to report the revision number of the ports tree it was built from we wouldn't need to hunt around for this information. -- Mike Clarke ___ 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: portmaster, portupgrade, etc
On Wednesday 04 Oct 2017 16:39:25 Ernie Luzar wrote: > Here's my take on that. > > The future direction has already been decided by the FreeBSD leaders 2 > years ago with their development of a better pkg system. > > The package system with flavors will cover 90% of the user community > needs. The remaining user's requirements are edge cases. Tools like > portmaster and portupgrad and even the native ports system usage on > personal machines will fad away. The ports system will mature into the > development system in the path to get things into the package system. Well I suppose I fall into the remaining 10% of the user community so here's my two cents worth. I rely almost entirely on installing binary packages but I need to run php71 for compatibility with a website I maintain. I also need phpMyAdmin but need to build this from ports because the currently available package is built against php56. Using poudriere for this one task would be equivalent to using a steamroller to crack a peanut. Building phpMyAdmin from ports is no great problem for me and perhaps future development of pkg might avoid the need to build my own version but I'd hope that documented methods will continue to exist for users with this type of need. -- Mike Clarke ___ 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: Upgrade PHP to 7.0
On Monday 05 Jun 2017 00:57:40 Jack L. wrote: > Yes, wordpress is compatible with php 7.1 Wordpress core will be OK but there may be problems with some plugins. Before upgrading PHP on a Wordpress site it would be worth installing the PHP Compatibility Checker plugin to check your plugins and themes for potential problems. https://wordpress.org/plugins/php-compatibility-checker/ -- Mike Clarke ___ 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: poudriere + bdb6 build issue (maybe newbie stupidity)
On Wed, 10 May 2017, Adam Weinberger wrote: On 10 May, 2017, at 10:59, Mike Andrews <mandr...@bit0.com> wrote: I’m experimenting with poudriere for the first time and running into an issue with some ports that use BDB. With this in make.conf: DEFAULT_VERSIONS= bdb=6 I get this for four ports that use BDB 6: [00:00:47] >> [04][00:00:00] Finished build of databases/p5-BerkeleyDB: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:47] >> [03][00:00:00] Finished build of databases/ruby-bdb: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:48] >> [06][00:00:01] Finished build of www/webalizer: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:49] >> [01][00:00:01] Finished build of textproc/redland: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb Installing the ports manually from source works just fine. Am I missing something stupid/obvious here, or is it an issue with those specific four ports? There's a licensing-related peculiarity with bdb 6. Add WITH_BDB6_PERMITTED=yes to your make.conf and it should build for you. That fixed it, thanks! Now where is that documented? Anywhere? Now that I Google that option, okay, it's in bdb.mk, but... hard to do that if you don't know it's there. :) I did (do) have DISABLE_LICENSES=yes in there, but that's more to disable prompts at 'poudriere options' time, I guess. ___ 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"
poudriere + bdb6 build issue (maybe newbie stupidity)
I’m experimenting with poudriere for the first time and running into an issue with some ports that use BDB. With this in make.conf: DEFAULT_VERSIONS= bdb=6 I get this for four ports that use BDB 6: [00:00:47] >> [04][00:00:00] Finished build of databases/p5-BerkeleyDB: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:47] >> [03][00:00:00] Finished build of databases/ruby-bdb: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:48] >> [06][00:00:01] Finished build of www/webalizer: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:49] >> [01][00:00:01] Finished build of textproc/redland: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb Installing the ports manually from source works just fine. Am I missing something stupid/obvious here, or is it an issue with those specific four ports? ___ 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: How to use cached packages
On Thu, 20 Apr 2017 13:17:35 -0700 Freddie Cash <fjwc...@gmail.com> wrote: > If you have the .txz/.tbz package file, then it's a simple: > > # pkg install /path/to/firefox-versions-blahblah.txz But the version in the cache could be earlier than the version that was previously installed, in which case you might have dependency problems if it requires earlier versions of dependencies than those already installed on your system. -- Mike Clarke ___ 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: Odd daily security run output message
On Sat, 18 Feb 2017 15:45:12 -0800
Kevin Oberman <rkober...@gmail.com> wrote:
> This belongs here because the message is a muddled mess. It might belong to
> gnome@ because I am only aware that gnome is the remaining ports user of
> this port. (I'm quite possibly wrong about this.)
>
> It's telling you (very poorly) that Samba v3.6 is no longer supported by
> the samba folks and you should stop using it and that it is scheduled to be
> deleted at hte end of June.
It's not just gnome. Kde4 requires it too:
curlew:/home/mike% pkg info -r samba36-libsmbclient-3.6.25_2
samba36-libsmbclient-3.6.25_2:
gvfs-1.26.3_2
gnome-vfs-2.24.4_4
kde-runtime-4.14.3_4
--
Mike Clarke
___
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: Firefox and sndio
On Sat, 28 Jan 2017 14:58:51 + Grzegorz Junka <li...@gjunka.com> wrote: > On 28/01/2017 11:37, Tobias Kortkamp wrote: > > On Sat, Jan 28, 2017, at 11:23, Grzegorz Junka wrote: > >> Audio in Firefox seems to be working fine when ALSA is enabled. But when > >> ALSA is disabled and only SNDIO is enabled there is no sound. In either > >> case I had PULSEAUDIO disabled. What's the expected configuration for > >> this to work? > > Is sndiod running? If not: > > > > sysrc sndiod_enable=YES > > service sndiod start > > > > Thanks Tobias. That helped. Out of interest. Is there any reason why I > should prefer either SNDIO, PUlSEAUDIO or ALSA? This currently creates a problem for those of us using Firefox from packages because the default build has SNDIO turned off. $ pkg info firefox firefox-51.0_2,1 Name : firefox Version: 51.0_2,1 Installed on : Sat Jan 28 09:32:22 2017 GMT Origin : www/firefox Architecture : freebsd:11:x86:64 Prefix : /usr/local Categories : ipv6 www Licenses : Maintainer : ge...@freebsd.org WWW: http://www.mozilla.com/firefox Comment: Web browser based on the browser portion of Mozilla Options: ALSA : on BUNDLED_CAIRO : on CANBERRA : off DBUS : on DEBUG : off DTRACE : on FFMPEG : on GCONF : off GNOMEUI: off GTK2 : off GTK3 : on INTEGER_SAMPLES: off LIBPROXY : off OPTIMIZED_CFLAGS: on PGO: off PROFILE: off PULSEAUDIO : on RUST : on SNDIO : off TEST : off [snip] Annotations: cpe: cpe:2.3:a:mozilla:firefox:51.0:freebsd11:x64:2 no_provide_shlib: yes repo_type : binary repository : FreeBSD -- Mike Clarke ___ 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: What's happened to flashplugin?
On Mon, 2 Jan 2017 11:16:38 +0100 Dimitry Andric <d...@freebsd.org> wrote: > It's been renamed to www/linux-flashplayer. Thanks. It's working fine now after installing the new renamed version. -- Mike Clarke ___ 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"
What's happened to flashplugin?
Both www/linux-c7-flashplugin24 and www/linux-c6-flashplugin24 appear to have been deleted from ports but I can't find information relating to why they've gone. Is this deletion permanent or can we expect a flash plugin to reappear? -- Mike Clarke ___ 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: mail/spamassassin config option AS_ROOT is confusing
On Tue, Dec 20, 2016 at 05:16:32PM -0700, Adam Weinberger wrote: > > On 20 Dec, 2016, at 16:51, RW <rwmailli...@googlemail.com> wrote: > > > > On Tue, 20 Dec 2016 11:53:43 -0700 > > Mike Brown wrote: > > > >> The AS_ROOT option in the mail/spamassassin port is really confusing > >> to me. Given that its description is "Run spamd as root > >> (recommended)", what actually happens is somewhat bonkers: > >> > >> The main spamd process always runs as root. If AS_ROOT is enabled, > >> then the child processes who do all the work will not run as root, > >> but rather as unprivileged user spamd. If AS_ROOT is disabled, then > >> the children *will* run as root, but as needed they will setuid to > >> the user calling spamc. > >> Which setting you want depends on where user prefs and Bayes data is > >> stored. If it's in user-owned ~/.spamassassin directories, then you > >> want AS_ROOT disabled or you'll get a plethora of error messages and > >> lock file warnings relating to permissions, since user spamd can't > >> write where it needs to. > > > > That shouldn't happen as the default (without virtual users) is to > > use /var/spool/spamd, the spamd user's home directory. I think we need to get to the bottom of this before I propose an extended help message for the FreeBSD port's config options. I don't want to misrepresent the expected behavior of using -u. The only thing I see in my SA config which could be causing the non-default behavior is in local.cf I have "allow_user_rules 1". Is that incompatible with -u? ___ 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"
mail/spamassassin config option AS_ROOT is confusing
The AS_ROOT option in the mail/spamassassin port is really confusing to me. Given that its description is "Run spamd as root (recommended)", what actually happens is somewhat bonkers: The main spamd process always runs as root. If AS_ROOT is enabled, then the child processes who do all the work will not run as root, but rather as unprivileged user spamd. If AS_ROOT is disabled, then the children *will* run as root, but as needed they will setuid to the user calling spamc. Which setting you want depends on where user prefs and Bayes data is stored. If it's in user-owned ~/.spamassassin directories, then you want AS_ROOT disabled or you'll get a plethora of error messages and lock file warnings relating to permissions, since user spamd can't write where it needs to. It took me a while to figure this out on a fresh installation. I enabled the option, thinking "yes, of course I want it to run as root, so that it can write to the users' home directories"... then I was confused when it ended up not running as root but rather as user spamd, and the behavior I wanted was only possible if I configured the port to *not* run spamd as root. I guess I am just griping, but I would like to think there is a better way to describe and name the configuration option. Maybe AS_SPAMD_USER with description "Run spamd as unprivileged user (recommended)"? Not sure this really would've helped me know which option to choose, but it would've spared me from part of the wild goose chase I've been on all day. Thanks for listening. ___ 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"
Make index fails with no entry for /usr/ports/audio/linux-c7-mikmod
curlew:/root# freebsd-version -ku 11.0-RELEASE-p2 11.0-RELEASE-p5 curlew:/root# make -C /usr/ports index Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- [snip] --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/games/linux-uplink-demo: no entry for /usr/ports/audio/linux-c7-mikmod curlew:/root# ls -l /usr/ports/audio/linux-c7-mikmod ls: /usr/ports/audio/linux-c7-mikmod: No such file or directory https://www.freebsd.org/cgi/ports.cgi?query=linux-c7-mikmod=all reports nothing found so what's causing make index to try to index it? -- Mike Clarke ___ 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: dependency explosions
On Mon, 3 Oct 2016 13:11:43 + Grzegorz Junka <li...@gjunka.com> wrote: > Shouldn't all packages default to noX dependencies? If I am not mistaken > FreeBSD is predominantly a server-side system, with X running only > occasionally I'd disagree with that. I don't know whether or not the majority of FreeBSD installations are servers or personal computers but the chances are that the majority of server installations will have relatively few packages installed whereas most PC's are likely to make use of far more packages and are also likely to be using X. Building from ports to get the required options would be a much bigger task for these installations than it would be for the servers. -- Mike Clarke ___ 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: Checking port option descriptions
On Friday 16 Sep 2016 20:09:06 Kevin Oberman wrote: > Even when the meaning is clear in global sense, what are the implications > for an application. E.g. "RTC=on: Add support for kernel real time clock" > in mplayer. I know exactly what the RTC is, but I have no idea why I might > or might not want it in mplayer. For cases where one line comments won't suffice how about providing the facility to include an extra text file in a port (perhaps "pkg-options") containing notes about why some particular options would be chosen? In its simplest form a user would be able to refer to the file before selecting an option, A further enhancement could be to modify the way that configure works so that the user can select an option and press "?" to see the section of text, if any, from pkg-options explaining that option. -- Mike Clarke ___ 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"
pulseview 0.4.0 not linking. Help with Qt5 app build?
I'm working on new versions of the sigrok ports (libserialport, libsigrok, libsigrokdecode and pulseview being the critical bits). While the C things all build and seem to work with little problem, the GUI package - pulseview - fails to link with a bunch of references to undefined variables. Those seem to be not only things from the sigrok libraries, but some standard parts of C++ as well. I'm don't generally do much C++ or Qt work, so am out of my depth. Figures that the thing that doesn't work is the thing I have the least ability to fix. Anyway, here's the link command and the errors it generates. There were no errors before that during the build. If someone can provide a clue as to what might be missing, or what to tell cmake, to get this to work, I'd appreciate it. The old 0.3.0 port does build, but examining it hasn't turned up anything that works. Plugging in C++ libraries, using -pthread, and trying different ways to get to the clang c++ compiler all result in linker errors. Please leave my address in the Cc: list, as I'm not subscribed. /usr/bin/CC-fPIC -O2 -g -DNDEBUG CMakeFiles/pulseview.dir/main.cpp.o CMakeFiles/pulseview.dir/pv/application.cpp.o CMakeFiles/pulseview.dir/pv/devicemanager.cpp.o CMakeFiles/pulseview.dir/pv/mainwindow.cpp.o CMakeFiles/pulseview.dir/pv/session.cpp.o CMakeFiles/pulseview.dir/pv/storesession.cpp.o CMakeFiles/pulseview.dir/pv/util.cpp.o CMakeFiles/pulseview.dir/pv/binding/binding.cpp.o CMakeFiles/pulseview.dir/pv/binding/inputoutput.cpp.o CMakeFiles/pulseview.dir/pv/binding/device.cpp.o CMakeFiles/pulseview.dir/pv/data/analog.cpp.o CMakeFiles/pulseview.dir/pv/data/analogsegment.cpp.o CMakeFiles/pulseview.dir/pv/data/logic.cpp.o CMakeFiles/pulseview.dir/pv/data/logicsegment.cpp.o CMakeFiles/pulseview.dir/pv/data/signaldata.cpp.o CMakeFiles/pulseview.dir/pv/data/segment.cpp.o CMakeFiles/pulseview.dir/pv/devices/device.cpp.o CMakeFiles/pulseview.dir/pv/devices/file.cpp.o CMakeFiles/pulseview.dir/pv/devices/hardwaredevice.cpp.o CMakeFiles/pulseview.dir/pv/devices/inputfile.cpp.o CMakeFiles/pulseview.dir/pv/devices/sessionfile.cpp.o CMakeFiles/pulseview.dir/pv/dialogs/about.cpp.o CMakeFiles/pulseview.dir/pv/dialogs/connect.cpp.o CMakeFiles/pulseview.dir/pv/dialogs/inputoutputoptions.cpp.o CMakeFiles/pulseview.dir/pv/dialogs/storeprogress.cpp.o CMakeFiles/pulseview.dir/pv/popups/deviceoptions.cpp.o CMakeFiles/pulseview.dir/pv/popups/channels.cpp.o CMakeFiles/pulseview.dir/pv/prop/bool.cpp.o CMakeFiles/pulseview.dir/pv/prop/double.cpp.o CMakeFiles/pulseview.dir/pv/prop/enum.cpp.o CMakeFiles/pulseview.dir/pv/prop/int.cpp.o CMakeFiles/pulseview.dir/pv/prop/property.cpp.o CMakeFiles/pulseview.dir/pv/prop/string.cpp.o CMakeFiles/pulseview.dir/pv/toolbars/mainbar.cpp.o CMakeFiles/pulseview.dir/pv/view/analogsignal.cpp.o CMakeFiles/pulseview.dir/pv/view/cursor.cpp.o CMakeFiles/pulseview.dir/pv/view/cursorpair.cpp.o CMakeFiles/pulseview.dir/pv/view/flag.cpp.o CMakeFiles/pulseview.dir/pv/view/header.cpp.o CMakeFiles/pulseview.dir/pv/view/marginwidget.cpp.o CMakeFiles/pulseview.dir/pv/view/logicsignal.cpp.o CMakeFiles/pulseview.dir/pv/view/rowitem.cpp.o CMakeFiles/pulseview.dir/pv/view/ruler.cpp.o CMakeFiles/pulseview.dir/pv/view/signal.cpp.o CMakeFiles/pulseview.dir/pv/view/signalscalehandle.cpp.o CMakeFiles/pulseview.dir/pv/view/timeitem.cpp.o CMakeFiles/pulseview.dir/pv/view/timemarker.cpp.o CMakeFiles/pulseview.dir/pv/view/trace.cpp.o CMakeFiles/pulseview.dir/pv/view/tracegroup.cpp.o CMakeFiles/pulseview.dir/pv/view/tracepalette.cpp.o CMakeFiles/pulseview.dir/pv/view/tracetreeitem.cpp.o CMakeFiles/pulseview.dir/pv/view/tracetreeitemowner.cpp.o CMakeFiles/pulseview.dir/pv/view/triggermarker.cpp.o CMakeFiles/pulseview.dir/pv/view/view.cpp.o CMakeFiles/pulseview.dir/pv/view/viewitem.cpp.o CMakeFiles/pulseview.dir/pv/view/viewitemowner.cpp.o CMakeFiles/pulseview.dir/pv/view/viewitempaintparams.cpp.o CMakeFiles/pulseview.dir/pv/view/viewport.cpp.o CMakeFiles/pulseview.dir/pv/view/viewwidget.cpp.o CMakeFiles/pulseview.dir/pv/widgets/colourbutton.cpp.o CMakeFiles/pulseview.dir/pv/widgets/colourpopup.cpp.o CMakeFiles/pulseview.dir/pv/widgets/devicetoolbutton.cpp.o CMakeFiles/pulseview.dir/pv/widgets/exportmenu.cpp.o CMakeFiles/pulseview.dir/pv/widgets/hidingmenubar.cpp.o CMakeFiles/pulseview.dir/pv/widgets/importmenu.cpp.o CMakeFiles/pulseview.dir/pv/widgets/popup.cpp.o CMakeFiles/pulseview.dir/pv/widgets/popuptoolbutton.cpp.o CMakeFiles/pulseview.dir/pv/widgets/sweeptimingwidget.cpp.o CMakeFiles/pulseview.dir/pv/widgets/timestampspinbox.cpp.o CMakeFiles/pulseview.dir/pv/widgets/wellarray.cpp.o CMakeFiles/pulseview.dir/signalhandler.cpp.o CMakeFiles/pulseview.dir/pv/binding/decoder.cpp.o CMakeFiles/pulseview.dir/pv/data/decoderstack.cpp.o CMakeFiles/pulseview.dir/pv/data/decode/annotation.cpp.o CMakeFiles/pulseview.dir/pv/data/decode/decoder.cpp.o CMakeFiles/pulseview.dir/pv/data/decode/row.cpp.o CMakeFiles/pulseview.dir/pv/data/decode/rowdata.cpp.o
Re: mail/roundcube (bsd.php.mk broken?)
On 2016-03-23 09:33 PM, Guido Falsi wrote: On 03/24/16 01:56, Mike Jakubik wrote: On 2016-03-23 08:42 PM, Guido Falsi wrote: On 03/24/16 01:09, Mike Jakubik wrote: ports tree. I guess i can try upgrading to 5.5 and hope that my applications are compatible with it. Sigh, FreeBSD has become a PITA lately to maintain unless everything installed is bleeding edge. In any case, thanks for the help. Sorry I beg to disagree. php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You should complain to the php project about this, not the ports tree, which is just complying with upstream. You are correct, however I think php is a special case, because it's a slow adopter, sadly a lot of hosting providers have not updated and a lot of software is still not compatible with the latest versions. For example, the default version of php in CentOS 7 is still 5.4, so I don't see why removing it from ports was a good idea. The reason is it is not supported, bugs and vulnerabilities are not fixed, we would end up giving potentially insecure software, or even worse, software with known vulnerabilities. I get what you are saying, but I think these kind of changes could be handled better. You go to update something and shit breaks or you get some incomprehensible errors such as in this case forcing you to rummage through some UPDATING file or mailing lists. What ever happened to POLA? Why couldn't it have prompted me upon trying to perform a minor update of roundcube that my version of PHP is no longer supported, and perhaps give me an option to continue anyways at my own risk since it works just fine with the php i have installed. Now i have to manually reinstall all the php packages and binaries that depend on them and hope that my php software will still function with the new php. That is why i say that FreeBSD is a PITA to maintain. ___ 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: mail/roundcube (bsd.php.mk broken?)
On 2016-03-23 08:42 PM, Guido Falsi wrote: On 03/24/16 01:09, Mike Jakubik wrote: ports tree. I guess i can try upgrading to 5.5 and hope that my applications are compatible with it. Sigh, FreeBSD has become a PITA lately to maintain unless everything installed is bleeding edge. In any case, thanks for the help. Sorry I beg to disagree. php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You should complain to the php project about this, not the ports tree, which is just complying with upstream. You are correct, however I think php is a special case, because it's a slow adopter, sadly a lot of hosting providers have not updated and a lot of software is still not compatible with the latest versions. For example, the default version of php in CentOS 7 is still 5.4, so I don't see why removing it from ports was a good idea. -- http://w3techs.com/technologies/details/pl-php/5/all ___ 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: mail/roundcube (bsd.php.mk broken?)
On 2016-03-23 05:56 PM, Guido Falsi wrote: On 03/23/16 22:26, Mike Jakubik wrote: Hello, I am getting the following errors trying to update roundcube, this is on FreeBSD 9, using default version of php (5.4). I've tried adding DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference. Any ideas? Are you tracking the head of the ports tree or the 2016Q1 branch? I'm guessing you're with ports head. In head the default php version is 5.6 and version 5.4 has been removed because it has reached EOL on September 3rd, 2015. you could also use php 5.5, but it will EOL in July, so, if you're tracking the head of the ports tree, I'd suggest you try again using php 5.6. If you're tracking 2016Q1 it should work, and I don't really know what's happening. I am using portsnap to keep my ports tree up to date, i wasn't aware you can choose different branches with it, so whatever is the default there is what i have. Sure enough after checking, 5.4 has disappeared from my ports tree. I guess i can try upgrading to 5.5 and hope that my applications are compatible with it. Sigh, FreeBSD has become a PITA lately to maintain unless everything installed is bleeding edge. In any case, thanks for the help. ___ 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: mail/roundcube (bsd.php.mk broken?)
On 2016-03-23 06:51 PM, Miroslav Lachman wrote: Guido Falsi wrote on 03/23/2016 22:56: On 03/23/16 22:26, Mike Jakubik wrote: Hello, I am getting the following errors trying to update roundcube, this is on FreeBSD 9, using default version of php (5.4). I've tried adding DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference. Any ideas? Are you tracking the head of the ports tree or the 2016Q1 branch? I'm guessing you're with ports head. In head the default php version is 5.6 and version 5.4 has been removed because it has reached EOL on September 3rd, 2015. you could also use php 5.5, but it will EOL in July, so, if you're tracking the head of the ports tree, I'd suggest you try again using php 5.6. If you're tracking 2016Q1 it should work, and I don't really know what's happening. I think that "Malformed conditional" errors are caused by too old "make". I have seen this error on old machines in the process of upgrade to 10.2 (old 'make' working with newer Makefiles) What version of 9.x it is? Miroslav Lachman It is fairly up to date world/kernel. FreeBSD illidan.local 9.3-STABLE FreeBSD 9.3-STABLE #0 r293423: Fri Jan 8 11:50:36 EST 2016 ___ 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"
mail/roundcube (bsd.php.mk broken?)
Hello,
I am getting the following errors trying to update roundcube, this is on
FreeBSD 9, using default version of php (5.4). I've tried adding
DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference.
Any ideas?
Thanks.
root@illidan.local:/usr/local/www# portmaster roundcube-1.1.1
===>>> Currently installed version: roundcube-1.1.1,1
===>>> Port directory: /usr/ports/mail/roundcube
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mpcre} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mmbstring} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Msession} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Miconv} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mdom} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mxml} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mjson} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mintl} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mzip} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mfilter} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mpdo_pgsql} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Mpspell} != "")
"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 367: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 1885: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 5825: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 5828: if-less endif
make: fatal errors encountered -- cannot continue
___
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: Cant install any perl module via ports "Undefined symbol "PL_tainting"
On 2015-11-17 12:58 PM, Mark Martinec wrote: On 2015-11-17 18:19, Mike Jakubik wrote: Undefined symbol "PL_tainting" at /usr/local/lib/perl5/5.16/XSLoader.pm line 68. at /usr/local/lib/perl5/site_perl/mach/5.16/Encode.pm line 10. Looks like a mismatch between a version of perl and a module. Odd, it was only a minor update, in any case i ended up updating Perl to 5.20 and rebuilding everything, that did the trick. I decided to update spamassassin today and its dependencies only to find out that perl is now somehow broken, i get the following errors during installation. Btw, the recent update of p5-Net-DNS to 1.03 broke its compatibility with spamassassin-3.4.1_4 (as is currently in ports). So, after you sort out your perl installation, until a better solution is available, please consider downgrading Net::DNS to 1.02, e.g. installing it from CPAN. See the recent topic on the us...@spamassassin.apache.org mailing list: "DNS lookups fail with SpamAssassin since Net::DNS 1.03" Thanks for the info. ___ 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"
Cant install any perl module via ports "Undefined symbol "PL_tainting"
Hello, I decided to update spamassassin today and its dependencies only to find out that perl is now somehow broken, i get the following errors during installation. ===> Staging for p5-IO-Socket-SSL-2.020 ===> Generating temporary packing list Pod::Man is not available: Can't load '/usr/local/lib/perl5/site_perl/mach/5.16/auto/Encode/Encode.so' for module Encode: /usr/local/lib/perl5/site_perl/mach/5.16/auto/Encode/Encode.so: Undefined symbol "PL_tainting" at /usr/local/lib/perl5/5.16/XSLoader.pm line 68. at /usr/local/lib/perl5/site_perl/mach/5.16/Encode.pm line 10. Compilation failed in require at /usr/local/lib/perl5/5.16/Pod/Man.pm line 34. BEGIN failed--compilation aborted at /usr/local/lib/perl5/5.16/Pod/Man.pm line 34. Compilation failed in require at /usr/local/lib/perl5/site_perl/ExtUtils/Command/MM.pm line 103. Man pages will not be generated during this install. Installing /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/IO/Socket/SSL.pod Installing /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/IO/Socket/SSL.pm Installing /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/IO/Socket/SSL/PublicSuffix.pm Installing /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/IO/Socket/SSL/Utils.pm Installing /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/IO/Socket/SSL/Intercept.pm /bin/mkdir -p /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/share/examples/IO-Socket-SSL/ install -m 555 /usr/ports/security/p5-IO-Socket-SSL/work/IO-Socket-SSL-2.020/example/* /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/share/examples/IO-Socket-SSL/ > Compressing man pages (compress-man) ===> Installing for p5-IO-Socket-SSL-2.020 ===> Checking if p5-IO-Socket-SSL already installed ===> Registering installation for p5-IO-Socket-SSL-2.020 pkg-static: Unable to access file /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/man/man3/IO::Socket::SSL.3.gz: No such file or directory pkg-static: Unable to access file /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/man/man3/IO::Socket::SSL::Intercept.3.gz: No such file or directory pkg-static: Unable to access file /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/man/man3/IO::Socket::SSL::PublicSuffix.3.gz: No such file or directory pkg-static: Unable to access file /usr/ports/security/p5-IO-Socket-SSL/work/stage/usr/local/lib/perl5/site_perl/man/man3/IO::Socket::SSL::Utils.3.gz: No such file or directory *** [fake-pkg] Error code 74 This applies to any p5\ package i try to install. Any ideas? root@illidan.local:~# perl -v This is perl 5, version 16, subversion 3 (v5.16.3) built for amd64-freebsd-thread-multi root@illidan.local:~# uname -a FreeBSD illidan.local 9.3-STABLE FreeBSD 9.3-STABLE #0 r279015: Thu Feb 19 13:49:28 EST 2015 root@illidan.local:/usr/obj/usr/src/sys/ILLIDAN amd64 Thanks. ___ 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: Cant install any perl module via ports "Undefined symbol "PL_tainting"
On 2015-11-17 12:38 PM, Michelle Sullivan wrote: Hate to tell you this but you're going to get w**kered by people for the versions.. You installed part of it from binary (pkgng) ...? You upgraded perl? (or didn't upgrade perl) ? IIRC perl 5.16 got 'retired' recently so if you got anything using pkgng you probably got mismatched versions. My advice uninstall all perl modules and perl itself and reload everything from either ports or pkgng (not both)... You could just deinstall and rebuild p5-Encode as a shortcut - however it is likely soemthing else is broken so you might see the same over and over again... I find deinstalling recursively and reinstalling fixes and levels the playing field. Regards, Michelle I did a minor update of perl 5.16.3, now nothing that uses perl works, get the same error. Everything is installed from ports on the system, guess ill try to update to a newer version of perl and hope that doesn't break my perl applications. Thanks. ___ 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: 'too many errors' when compiling mysql56-client yassl code
On Thu, Sep 10, 2015 at 07:54:14AM -0600, Mike Brown wrote: > I'm trying to build mysql56-server from the ports collection, and during the > build of the yassl part of mysql56-client, compilation aborts due to too many > errors. > > Here's the relevant output: http://pastebin.com/raw.php?i=kXaDDJJY Various ports were affected. Related PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192723 Discussion, workaround, and notice of global fix: https://forums.freebsd.org/threads/mysql56-client-build-errors-on-10-stable.53193/ Global fix, committed to ports collection today: https://svnweb.freebsd.org/ports?view=revision=397026 I updated my ports collection to pick up the fix, and the build of MySQL completes without error now, so the issue is resolved for me. ___ 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"
'too many errors' when compiling mysql56-client yassl code
I'm trying to build mysql56-server from the ports collection, and during the build of the yassl part of mysql56-client, compilation aborts due to too many errors. Here's the relevant output: http://pastebin.com/raw.php?i=kXaDDJJY The problems seem to be in the source code, but I don't understand why no one else has reported it, if that's really the problem. This is on my BeagleBone Black (armv6) running the latest FreeBSD 10.2 snapshot: FreeBSD-10.2-STABLE-arm-armv6-BEAGLEBONE-20150903-r287435.img.xz from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/10.2/ I did a 'portsnap fetch extract' and installed a few ports successfully, and all I'm doing now is 'portmaster -d databases/mysql56-server'. Is there something else I need to do? ___ 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: Packages lagging for 10.2
On Tue, 08 Sep 2015 08:46:48 +0200
Jimmy Renner <ji...@renner.se> wrote:
> I don't know if this is the right list to post to but for me lots (a
> bit over 100) of ports are updated but if I do a pkg upgrade not much
> is updated. This has been the case since I upgraded to 10.2. No
> complaints, I was just wondering if I have done anything wrong :-)
10.2 now uses the quarterly repository by default but you can switch to
using the latest packages if you
create /usr/local/etc/pkg/repos/FreeBSD.conf as below:
FreeBSD: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;
}
This will override the url attribute in /etc/pkg/FreeBSD.conf
--
Mike Clarke
___
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: Perl 5.20 breaks /usr/bin/perl
On Sat, 15 Aug 2015 21:38:22 +0200 Mathieu Arnold m...@freebsd.org wrote: +--On 15 août 2015 22:25:47 +0200 Xavier xav...@groumpf.org wrote: [snip] | IMHO, the port should at least emit a warning, since almost every Perl | program I'm aware of (including those I wrote for 20 years, since | MacPerl) use shebang /usr/bin/perl. I even remember it's mentioned in the | Camel Book. It was mentionned in UPDATING, in the 20150513 entry, the one explaining how you upgrade from 5.18 to 5.20 :-) Although it was mentioned in UPDATING there could be problems for users who rely entirely on pkg and never build from ports. Many of these users will not have, nor need, an up to date ports tree in which case they will not be aware of this. IMHO the note about the symlink having been removed should also have been included as pkg-message. -- Mike Clarke ___ 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: Synchronising ports with package cluster
On Tuesday 14 Apr 2015 11:30:19 Don Lewis wrote: On 14 Apr, Mike Clarke wrote: [snip] The problem is that 101amd64-default hasn't been built on beefy2.isc.freebsd.org since version 381523 on 2015-03-18_03h47m09s. The mystery is where do we get the logs from now? Look for 101amd64-default in this mail list archive: https://docs.freebsd.org/mail/current/freebsd-pkg-fallout.html I found this message: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=19023048+0+current/freebsd-pk g-fallout which says tht the place to look is: http://beefy6.nyi.freebsd.org/data/101amd64-default/ Not the most user friendly way of finding this information, but ... Many thanks, that provided the essential clue. beefy6.nyi.freebsd.org provides logs for 101amd64-default and 84amd64-default. A bit of digging around enabled me to put together the following list: beefy1.isc.freebsd.org 93i386-default 101i386-quarterly beefy2.isc.freebsd.org 93amd64-default 101amd64-quarterly beefy3.isc.freebsd.org head-i386-default 93i386-quarterly beefy4.isc.freebsd.org head-amd64-default 93amd64-quarterly beefy5.nyi.freebsd.org 101i386-default 84i386-default beefy6.nyi.freebsd.org 101amd64-default 84amd64-default Also it looks like the build schedules might have been revised, it looks like 101amd64-default started on Monday. I'm now able to synchronise my ports tree with the package repository but can't help wondering if the servers might change again in the future. -- Mike Clarke ___ 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: Synchronising ports with package cluster
On Tuesday 14 Apr 2015 02:06:35 Reed A. Cartwright wrote: It is possible to grab the revision information from the build logs. I have written a script to pull the number and update a local svn copy of the ports. https://gist.github.com/reedacartwright/8622973baf89b263a6d7 That script is what I've been using, with minor mods because I need to update /usr/ports instead of a poudriere jail which I'm not using here. The problem is that 101amd64-default hasn't been built on beefy2.isc.freebsd.org since version 381523 on 2015-03-18_03h47m09s. The mystery is where do we get the logs from now? -- Mike Clarke ___ 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: Synchronising ports with package cluster
On Thursday 02 Apr 2015 10:13:34 Mel Pilgrim wrote: On 2015-04-01 13:42, Mike Clarke wrote: Where can I now obtain the revision number for the ports tree used for the latest package build? Although the above method has worked in the past it's a bit of a bodge. The ideal way would be if this information could be accessed directly from the relevant package repository. Would it be possible to provide such a facility? This is has been asked for many times in many forms--from SVN branching to simply an extra bit of metadata provided by pkg itself. The usual answer is, we'll put this in a future version, but it remains not implemented. Sounds like it would be a useful feature but in the meantime could anyone point me to where I can find the SVN revision used by the ports cluster when building for 101amd64-default? It used to be on beefy2.isc.freebsd.org/#latest_builds but that now only shows 101amd64- quarterly and 93amd64-default. I assume the build logs must be available somewhere. -- Mike Clarke ___ 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
Synchronising ports with package cluster
I use pkg upgrade to maintain most of my ports but a small number need to be built from source. To avoid problems I aim to keep my ports tree in sync with the snapshots used by the package cluster. Until a couple of weeks ago I was able to obtain the revision number of the ports snapshot by parsing the results of fetching beefy2.isc.freebsd.org/data/101amd64- default/.data.json. That server now appears to be only building 93amd64-default and 101amd64-quarterly. So now my ports are stuck at revision 381523 from about two weeks ago. Where can I now obtain the revision number for the ports tree used for the latest package build? Although the above method has worked in the past it's a bit of a bodge. The ideal way would be if this information could be accessed directly from the relevant package repository. Would it be possible to provide such a facility? -- Mike Clarke ___ 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/portell distfiles no longer on SourceForge
ports-mgmt/portell can't be installed now because its SourceForge project has disappeared. It looks like the author is now just using a GitHub Gist for it: https://gist.github.com/rkulla/1122022 Is that usable? ___ 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: Overriding binary package with local build
On Mon, 9 Mar 2015 09:43:24 + heasley h...@shrubbery.net wrote: For example. On this system I've built gld with postgres instead of mysql and postfix with another option. The mysql dependency is coming from the binary gld with the default options. And, in theory postfix has different options, but also needs an update. pkg lock gld This will prevent gld from being updated by pkg but it will also prevent you from installing it when you rebuild it so you will need to unlock it for the duration while you're building it. See pkg-lock(8). -- Mike Clarke ___ 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: pkgng deviates from defaults?
On Mon, 09 Mar 2015 07:04:30 -0700 Chris H bsd-li...@bsdforge.com wrote: You might be able to avoid the issue you're having, by using: DEFAULT_VERSIONS+=php=5.5 in your make.conf(5) (/etc/make.conf) file. As far as I know this won't have any effect on pkg. If the OP wishes to use pkg then the only option is to switch to using php5.6. This will involve uninstalling all the php5.5 packages and reinstalling default php5.6 versions. I went through this process recently and described the steps involved in questions@ https://lists.freebsd.org/pipermail/freebsd-questions/2015-March/264525.html -- Mike Clarke ___ 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
License compatibility issues?
After a discussion on another list, I'm wondering if anyone has ever done anything to verify that the license requirements of the dependencies of a package (I don't know of any licenses that would cause problems for a port, as those don't involve distribution of derived works in the form of a binary) are actually met? For instance, a port licensed under the EPL that is statically linked with a GPL'ed library would produce a binary that couldn't be legally distributed. Searching google didn't turn much up, but I do notice that bsd.license.txt doesn't worry about the license requirements of dependencies. Since it is run at build time, this isn't a problem, as the license issues we deal with will turn up when the dependencies are built. But incompatible licenses don't seem to be dealt with at all. Maybe I just need better google search words? ___ 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: www/midori dislikes the letter h
On Fri, 27 Feb 2015 16:41:46 +0200 Beeblebrox zap...@berentweb.com wrote: OK, this should be fun. Open Midori, start typing a URL (without www) Nothing out of the ordinary happens if the first char you type is a -g or i-z. But if you type h as the very first char, Midori segfaults and closes. Segfaulting on the letter h does not look like a very good omen to me... I don't have the problems here with midori 0.5.9 on 10.1-RELEASE-p6 -- Mike Clarke ___ 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 upgrade wants to leave me with a mix of php5.4 and php5.6
curlew:/# pkg info -x pkg- pkg-1.4.12 curlew:/# pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (62 candidates): 77% mod_php5 has no direct installation candidates, change it to mod_php5? [Y/n]: n mod_php5 has no direct installation candidates, change it to mod_php55? [Y/n]: n mod_php5 has no direct installation candidates, change it to mod_php56? [Y/n]: n Checking for upgrades (62 candidates): 100% Processing candidates (62 candidates): 100% The following 76 packages will be affected (of 0 checked): New packages to be INSTALLED: php56-xml: 5.6.6 php56: 5.6.6 php56-hash: 5.6.6 php56-gd: 5.6.6 php56-curl: 5.6.6 php56-tokenizer: 5.6.6 php56-mysql: 5.6.6 php56-zlib: 5.6.6 php56-zip: 5.6.6 php56-session: 5.6.6 php56-ctype: 5.6.6 php56-openssl: 5.6.6 php56-mcrypt: 5.6.6_1 php56-filter: 5.6.6 php56-json: 5.6.6 php56-mysqli: 5.6.6 php56-mbstring: 5.6.6 php56-bz2: 5.6.6 Installed packages to be UPGRADED: xcalc: 1.0.5 - 1.0.6 webkit-gtk3: 2.4.8 - 2.4.8_1 webkit-gtk2: 2.4.8 - 2.4.8_1 unzip: 6.0_5 - 6.0_6 unbound: 1.5.1_2 - 1.5.2 samba36-libsmbclient: 3.6.24_2 - 3.6.25_2 samba36: 3.6.24_2 - 3.6.25 rest: 0.7.92 - 0.7.92_1 py27-twistedCore: 14.0.0_1 - 15.0.0_1 phpMyAdmin: 4.3.9 - 4.3.10 php5-zlib: 5.4.37 - 5.4.38 php5-zip: 5.4.37 - 5.4.38 php5-xmlwriter: 5.4.37 - 5.4.38 php5-xmlreader: 5.4.37 - 5.4.38 php5-xml: 5.4.37 - 5.4.38 php5-tokenizer: 5.4.37 - 5.4.38 php5-sqlite3: 5.4.37_1 - 5.4.38_1 php5-simplexml: 5.4.37 - 5.4.38 php5-session: 5.4.37 - 5.4.38 php5-posix: 5.4.37 - 5.4.38 php5-phar: 5.4.37 - 5.4.38 php5-pdo_sqlite: 5.4.37_1 - 5.4.38_1 php5-pdo: 5.4.37 - 5.4.38 php5-openssl: 5.4.37 - 5.4.38 php5-mysqli: 5.4.37 - 5.4.38 php5-mysql: 5.4.37 - 5.4.38 php5-mcrypt: 5.4.37_1 - 5.4.38_1 php5-mbstring: 5.4.37 - 5.4.38 php5-json: 5.4.37 - 5.4.38 php5-iconv: 5.4.37 - 5.4.38 php5-hash: 5.4.37 - 5.4.38 php5-gd: 5.4.37 - 5.4.38 php5-filter: 5.4.37 - 5.4.38 php5-dom: 5.4.37 - 5.4.38 php5-curl: 5.4.37 - 5.4.38 php5-ctype: 5.4.37 - 5.4.38 php5-calendar: 5.4.37 - 5.4.38 php5-bz2: 5.4.37 - 5.4.38 php5: 5.4.37 - 5.4.38 phonon-gstreamer: 4.8.2 - 4.8.2_1 pciids: 20150124 - 20150217 p5-libwww: 6.08_1 - 6.13 p5-URI: 1.65 - 1.67 p5-Socket: 2.016_1 - 2.018 p5-IO-Socket-SSL: 2.009 - 2.012 libreoffice: 4.3.5_3 - 4.3.6 libraw: 0.15.4_1 - 0.16.0 libkdcraw: 4.14.2 - 4.14.2_1 libcmis: 0.4.1_3 - 0.5.0 krdc: 4.14.2 - 4.14.2_1 gnupg: 2.1.1_1 - 2.1.2 fusefs-libs: 2.9.3_3 - 2.9.3_4 en_GB-libreoffice: 4.3.5 - 4.3.6 chromium: 40.0.2214.111 - 40.0.2214.115 bind99: 9.9.6P1_3 - 9.9.6P2 babl: 0.1.10_2 - 0.1.12 Installed packages to be REINSTALLED: wordpress-4.1,1 (direct dependency changed) cmake-3.1.3 (options changed) The process will require 23 MiB more space. 195 MiB to be downloaded. Proceed with this action? [y/N]: n --- Looks like I need to delete all my php* packages, install php56* versions and then run pkg upgrade. Is there a neater way of fixing this? -- Mike Clarke ___ 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
PHP 5.6 is default. What do lang/php5 users do?
The default version of PHP is now 5.6, but lang/php5 is still 5.4. From looking at the commits,[1] it seems that if I didn't have lang/php5 (5.4) installed, and then I installed something that requires PHP, I'd get lang/php56. Is that right? But since I do have lang/php5 installed, upgrading with 'portmaster php5' will just get me 5.4.38, not 5.6. So should I install lang/php56 myself now, or is it expected that lang/php5 will eventually become 5.6 and I should just wait, or what? Sorry if this is a dumb question. [1] https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2313743+0+/usr/local/www/db/text/2015/svn-ports-head/20150222.svn-ports-head ___ 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: new warning - ap24-mod_perl2 has no direct installation candidates, change it to ap24-mod_perl2
On Fri, 13 Feb 2015 09:55:46 -0800
Patrick Powell papow...@astart.com wrote:
{142} # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (43 candidates): 97%
ap24-mod_perl2 has , change it to
ap24-mod_perl2 has no direct installation candidates, change it to
ap24-mod_perl2? [Y/n]:
I get the same no direct installation candidates message for mod_php5
which is locked.
curlew:/root# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (4 candidates): 50%
mod_php5 has no direct installation candidates, change it to mod_php5?
[Y/n]: n
mod_php5 has no direct installation candidates, change it to mod_php55?
[Y/n]: n
mod_php5 has no direct installation candidates, change it to mod_php56?
[Y/n]: n
The messages only appear when it's locked.
I have re-installed mod_php5 but still get the messages.
I have a total of 4 locked packages (exim-sa-exim, kde, mod_php5 and
xsane) but have only ever seen the message for mod_php5.
--
Mike Clarke
___
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
Dependent ports use different c++ compilers
Hi, kicad-devel depends at least on two c++ libraries: boost-lib and webkit-gtk2. kicad-devel and boost uses: USES+= compiler:c++11-lang This leads at least under FreeBSD 9.3 and 10.* to the usage of clang++ webkit-gtk2 uses: USES += compiler:c++11-lib This leads at least under FreeBSD 9.3 to the usage of GNU g++ (FreeBSD 10+ is using clang++) and this leads to missing symbols when linking kicad-devel. How can this dilemma be resolved? Greetings --- Mike (mr@) ___ 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 upgrade says mod_php5 has no direct installation candidates
FreeBSD 10.1-RELEASE, pkg-1.4.3 I maintain most of my packages with pkg. However I build mod_php5 from ports because I need to use it with apache22. To stop pkg upgrade from pulling in apache24 I have locked mod_php5. When I run pkg upgrade I see the following: - curlew:/root# pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (3 candidates): 66% mod_php5 has no direct installation candidates, change it to mod_php5? [Y/n]: n mod_php5 has no direct installation candidates, change it to mod_php55? [Y/n]: n mod_php5 has no direct installation candidates, change it to mod_php56? [Y/n]: n Checking for upgrades (3 candidates): 100% Processing candidates (3 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. - I've tried replying yes to change it to mod_php5 but still get the same questions next time I run pkg upgrade. As an experiment I unlocked mod_php5 and the no direct installation candidates questions did not appear but I had to cancel the upgrade since it would replace apache22 wirh apache24, I also have xsane and exim-sa-exim locked but have never seen similar messages for either of these. It's not causing any problems because pkg is not allowed to alter mod_php5 but I'm curious what's causing this behaviour and how to prevent it. -- Mike Clarke ___ 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?
Baptiste Daroussin wrote: # 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) That worked. Thanks for the explanation and solution. Mike ___ 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: Tomcat7: Unable to stop process (unlike tomcat6)
After i slept on this I remembered the rc.d system offers a force
option.
root@illidan.local:~# /usr/local/etc/rc.d/tomcat7 forcestop, seems to
work.
Thanks.
On 2014-12-08 06:09 PM, Mike Jakubik wrote:
Hello,
I've Noticed that the rc.d script for tomcat7 has changed from version
6. In tomcat6 a function called tomcat_stop() would force kill after a
certain timeout, this no longer happens in tomcat7 and sometimes we
are unable to stop it using the rc.d script, it just sits there
waiting for PID.
In tomcat6 we had:
tomcat_stop() {
rc_pid=$(tomcat_check_pidfile $pidfile)
if [ -z $rc_pid ]; then
[ -n $rc_fast ] return 0
echo ${name} not running? (check $pidfile).
return 1
fi
echo Stopping ${name}.
${java_command} stop
tomcat_wait_max_for_pid
${tomcat%%TOMCAT_VERSION%%_stop_timeout} ${rc_pid}
kill -KILL ${rc_pid} 2 /dev/null echo Killed.
rm -f ${pidfile}
}
This function is no longer available in the version 7 rc.d script, is
there any way it can be modified to function like in version 6?
Thank you.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Tomcat7: Unable to stop process (unlike tomcat6)
Unfortunately after actually trying this, it does not work, forcestop or
faststop does absolutely nothing different than stop. Shouldnt these
options be properly utilized? It seems to me that the rc.d script for
tomcat7 is a step backwards from tomcat6.
Thanks.
On 2014-12-09 09:50 AM, Mike Jakubik wrote:
After i slept on this I remembered the rc.d system offers a force
option.
root@illidan.local:~# /usr/local/etc/rc.d/tomcat7 forcestop, seems to
work.
Thanks.
On 2014-12-08 06:09 PM, Mike Jakubik wrote:
Hello,
I've Noticed that the rc.d script for tomcat7 has changed from version
6. In tomcat6 a function called tomcat_stop() would force kill after a
certain timeout, this no longer happens in tomcat7 and sometimes we
are unable to stop it using the rc.d script, it just sits there
waiting for PID.
In tomcat6 we had:
tomcat_stop() {
rc_pid=$(tomcat_check_pidfile $pidfile)
if [ -z $rc_pid ]; then
[ -n $rc_fast ] return 0
echo ${name} not running? (check $pidfile).
return 1
fi
echo Stopping ${name}.
${java_command} stop
tomcat_wait_max_for_pid
${tomcat%%TOMCAT_VERSION%%_stop_timeout} ${rc_pid}
kill -KILL ${rc_pid} 2 /dev/null echo Killed.
rm -f ${pidfile}
}
This function is no longer available in the version 7 rc.d script, is
there any way it can be modified to function like in version 6?
Thank you.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Tomcat7: Unable to stop process (unlike tomcat6)
Hello,
I've Noticed that the rc.d script for tomcat7 has changed from version
6. In tomcat6 a function called tomcat_stop() would force kill after a
certain timeout, this no longer happens in tomcat7 and sometimes we are
unable to stop it using the rc.d script, it just sits there waiting for
PID.
In tomcat6 we had:
tomcat_stop() {
rc_pid=$(tomcat_check_pidfile $pidfile)
if [ -z $rc_pid ]; then
[ -n $rc_fast ] return 0
echo ${name} not running? (check $pidfile).
return 1
fi
echo Stopping ${name}.
${java_command} stop
tomcat_wait_max_for_pid ${tomcat%%TOMCAT_VERSION%%_stop_timeout}
${rc_pid}
kill -KILL ${rc_pid} 2 /dev/null echo Killed.
rm -f ${pidfile}
}
This function is no longer available in the version 7 rc.d script, is
there any way it can be modified to function like in version 6?
Thank you.
___
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: building legacy packages with poudriere ?
On 12/5/2014 3:24 AM, Shane Ambler wrote: default method is portsnap - pkg_install is an svn branch name poudriere ports -m svn+https -B pkg_install -c If that fails you could manually checkout with svn and use poudriere ports -c -p pkg_install -F -f none -M /path/to Thanks! I had to blow away the default as it was from head, and poudriere kept saying I already had a default. How does one typically maintain distinct ports trees on the same box, or do they bother to ? Anyways, at this point I achieved what I wanted to do (build a python package), so my immediate need is solved! Next is to integrate poudriere into future projects. Thanks everyone for the help! ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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
building legacy packages with poudriere ?
I have a number of old legacy nanobsd boxes that I want to retrofit with a couple of packages remotely. Remote full image upgrade is not something I really want to do, as I would just like to add a couple of packages. I was looking at poudriere which seems the way to go, but it seems to only want to build .txz / pkgng style packages. Is there a way to get poudriere to build packages that an older releng8 installation would understand ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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
Re: building legacy packages with poudriere ?
On 12/4/2014 7:51 PM, Bryan Drewery wrote: Poudriere (as of latest 3.1) still supports pkg_install packages. It is *ports* that does not. You will need to use an older ports tree. You can use the /branches/pkg_install/ branch, but it is stuck at 2014 Sep. Excellent! Sept 2014 is fine for what I need to build from. Next question, how do I fetch that branch ? # poudriere ports -B pkg_install -c [00:00:00] Extracting portstree default... Looking up portsnap.FreeBSD.org mirrors... none found. Fetching public key from portsnap.FreeBSD.org... done. Fetching snapshot tag from portsnap.FreeBSD.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Thu Dec 4 19:12:03 EST 2014: 4ae3b8d808ed153ed27a765a9518a5bcb8e59126c5b08e100% of 70 MB 319 kBps 00m00s Extracting snapshot... and # poudriere ports -l # returns nothing ? I grabbed # poudriere version 3.1-RC3 # ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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
Re: Port Name Clash: What To Do?
On Wednesday 01 Oct 2014 11:54:36 Enrico Maria Crisostomo wrote: I'm the author of fswatch (https://github.com/emcrisostomo/fswatch), a cross-platform file change monitor, and I would like to submit a new port for it. The port is ready (kudos to the FreeBSD community for the high-quality documentation available) but I have not submitted yet because I discovered that there exists another port with the same name: security/fswatch. I'm now wondering what to do. I could rename the port itself but a problem would remain: two different ports would contain files with the same name. In fact, the two ports clash on one file: Until recently there was a port called filtermail which was renamed from mailfilter due to a name conflict. It was recently deleted due to not being staged but I recently got it working again and submitted a PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193721 suggesting that my modified version of the original port might be reinstated in the ports tree. I don't know if that will happen or not but if you look at the makefile attached to the PR you might be able to use the same technique for renaming the port and relevant files. -- Mike Clarke ___ 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: bash velnerability
On 9/30/2014 5:25 PM, Charles Swiger wrote:
bash-3.2$ echo Testing Exploit 4 (CVE-2014-7186)
Testing Exploit 4 (CVE-2014-7186)
bash-3.2$ CVE7186=$(bash -c 'true EOF EOF EOF EOF EOF EOF EOF EOF EOF EOF EOF
EOF EOF EOF' 2/dev/null ||echo -n V)
bash-3.2$ [ ${CVE7186} == V ] echo VULNERABLE || echo NOT VULNERABLE
NOT VULNERABLE
This being said, I'm not confident that there won't be further issues found
with bash
What are people using to check these issues ? I was using
https://github.com/hannob/bashcheck
Not sure if that gives false positives ? Even on linux with all patches
applied, it coredumps on 7186.
Yet the BASH maintainer says all holes are patched ? Or does he
consider 2014-7186 not a security issue ?
http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00341.html
# bash ./bashcheck
Not vulnerable to CVE-2014-6271 (original shellshock)
Not vulnerable to CVE-2014-7169 (taviso bug)
./bashcheck: line 18: 19749 Segmentation fault (core dumped) bash
-c true $(printf 'EOF %.0s' {1..79}) 2 /dev/null
Vulnerable to CVE-2014-7186 (redir_stack bug)
Test for CVE-2014-7187 not reliable without address sanitizer
Variable function parser inactive, likely safe from unknown parser bugs
#
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.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
Re: bash velnerability
On 9/26/2014 5:01 PM, Bryan Drewery wrote:
On 9/26/2014 12:41 PM, Bryan Drewery wrote:
On 9/26/2014 11:51 AM, Bryan Drewery wrote:
On 9/26/2014 11:46 AM, Bartek Rutkowski wrote:
Apparently, the full fix is still not delivered, accordingly to this:
http://seclists.org/oss-sec/2014/q3/741
Kind regards,
Bartek Rutkowski
I'm pretty sure they call that a feature. This is a bit different.
I've disabled environment function importing in the port. Using
--import-functions will allow it to work if you need it.
Hi Bryan,
With the latest ports, bashcheck still sees some issues with bash. Are
these false positives on FreeBSD ?
Using
https://raw.githubusercontent.com/hannob/bashcheck/master/bashcheck
Not vulnerable to CVE-2014-6271 (original shellshock)
Not vulnerable to CVE-2014-7169 (taviso bug)
./bashcheck: line 18: 54908 Segmentation fault (core dumped) bash
-c true $(printf 'EOF %.0s' {1..79}) 2 /dev/null
Vulnerable to CVE-2014-7186 (redir_stack bug)
Test for CVE-2014-7187 not reliable without address sanitizer
Variable function parser inactive, likely safe from unknown parser bugs
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.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
Re: FreeBSD Port: x11-servers/xorg-server
On Tuesday 23 Sep 2014 20:46:29 Patrick Powell wrote: I can't check this out right now, BUT are the keyboard/mouse drivers on the WITH_NEW_XORG repo server built correctly? They appear to be built OK, curlew:/home/mike% pkg rquery %n %v %R xf86-input-mouse xf86-input-mouse 1.9.0_4 FreeBSD xf86-input-mouse 1.9.0_4 FreeBSD_new_xorg curlew:/home/mike% pkg rquery %n %v %R xf86-input-keyboard xf86-input-keyboard 1.8.0_5 FreeBSD xf86-input-keyboard 1.8.0_5 FreeBSD_new_xorg Both repos have the same version but when I ran pkg upgrade it used FreeBSD for both these drivers with the result that I couldn't log in with KDM until I forcibly installed them from FreeBSD_new_xorg If that is the case then you can force PKG to fetch them from that REPO and then you can (using some magic I don't understand, setting something in the comment field) force PKG to always fetch from this repo. I have a plan B on this, which is to have a 'repo search order' capability added to PKG. IF you search the WITH_NEW_XORG repo first, THEN search the standard repo AND if you have two packages with the same version, etc, then you get it from the first repository you searched. Would an alternative approach when upgrading a package be to check to see if the existing package is annotated with a repository tag and use its value to decide which repository to use. This would have worked in my above example. curlew:/home/mike% pkg query %n %At %Av xf86-input-mouse xf86-input- keyboard xf86-input-mouse repo_type binary xf86-input-mouse repository FreeBSD_new_xorg xf86-input-keyboard repo_type binary xf86-input-keyboard repository FreeBSD_new_xorg It would however require the repository to be specified by the user when initially installing the package. The instructions in https://lists.freebsd.org/pipermail/freebsd-ports/2013-November/087487.html give the impression that the value of the annotation should influence the choice of repository but this does not appear to happen. -- Mike Clarke ___ 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 upgrade attempts to use the wrong repository for some packages
I use 3 repositories for packages, FreeBSD, FreeBSD_new_xorg and a local repository named poudriere which has a small number of packages which are either not available from the FreeBSD repositories or require non standard options, On attempting to run pkg upgrade I see that it will attempt to get some packages from FreeBSD when they should be from one of the other repositories. This will cause problems for at least three of my packages - audacity, xf86-input-keyboard and xf86-input-mouse. curlew:/home/mike% uname -a FreeBSD curlew.lan 9.3-RELEASE-p2 FreeBSD 9.3-RELEASE-p2 #0: Mon Sep 15 16:44:27 UTC 2014 root@amd64- builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 curlew:/home/mike% pkg query %n %v pkg pkg 1.3.7 curlew:/home/mike% pkg query %n %R audacity audacity poudriere curlew:/home/mike% pkg search -Q repository audacity audacity-2.0.5_3 FreeBSD [pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest] audacity-2.0.5_3 poudriere [file:/usr/local/poudriere/data/packages/9-3R-default] So audacity was installed from my local poudriere repository and the latest version 2.0.5_3 is available in my repository but pkg upgrade wants to fetch it from the FreeBSD repository Similar things happen with FreeBSD and FreeBSD_new_xorg curlew:/home/mike% pkg query %n %R xf86-input-keyboard xf86-input-keyboard FreeBSD_new_xorg Curlew:/home/mike% pkg search -Q repository xf86-input-keyboard xf86-input-keyboard-1.8.0_5FreeBSD [pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest] xf86-input-keyboard-1.8.0_5FreeBSD_new_xorg [pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/new_xorg] curlew:/home/mike% pkg query %n %R xf86-input-mouse xf86-input-mouse FreeBSD_new_xorg curlew:/home/mike% pkg search -Q repository xf86-input-mouse xf86-input-mouse-1.9.0_4 FreeBSD [pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest] xf86-input-mouse-1.9.0_4 FreeBSD_new_xorg [pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/new_xorg] The repository order shown by pkg -vv is FreeBSD, poudriere and finally FreeBSD_new_xorg. I can force these three packages to be upgraded from the correct repositories before upgrading the rest but there are several other xorg related packages which will be upgraded from FreeBSD and which I know also exist in FreeBSD_new_xorg. I know from a previous upgrade that things break if xf86-input-keyboard comes from FreeBSD and I suspect this might apply for some of the others, especially xf86- input-mouse. When the right version of a package exists in more than one repository shouldn't pkg upgrade default to using the repository that the existing package came from? -- Mike Clarke ___ 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: unable to set default apache port
On Tuesday 09 Sep 2014 08:09:10 Vick Khera wrote: Thanks. This seems to be working. Should I file a bug report? It seems to me that the DEFAULT_VERSIONS ought to be sufficient. Things have changed. It looks like it got fixed with version 367897 of Mk/bsd.apache.mk on September 10. APACHE_PORT= now causes the build to fail but DEFAULT_VERSIONS+=apache=2.2 works now. -- Mike Clarke ___ 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: service doen't get started at boottime, but can start manually
On Monday 08 Sep 2014 09:47:07 Stefan Esser wrote: This was for a reason: [snip detailed explanation why PROVIDE: is needed in local rc scripts] This is obviously a shortcoming in the documentation, which should be fixed. AFAIK, the old style startup files have never been deprecated and are still fully supported ... Thanks for explaining this, it was very informative. I think it would be good if the documentation could indicate that the PROVIDE: line is mandatory for scripts in /usr/local/etc/rc.d. A couple of months ago I created a simple rc script based on the example at https://www.freebsd.org/doc/en/articles/rc-scripting/rcng-confdummy.html which does not use PROVIDE:. Since this script needed to run before local filesystems were mounted I had to install it into /etc/rc.d so fortunately it worked for me. If it had gone into /usr/local/etc/rc.d I would have been having difficulty working out why the documentation was providing code that didn't work. -- Mike Clarke ___ 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: unable to set default apache port
On Monday 08 Sep 2014 15:52:17 Vick Khera wrote: My recent run of poudriere to build my package collection rebuilt all my apache dependents against 2.4. I knew this was coming, so had set in my poudriere make.conf the following: DEFAULT_VERSIONS=mysql=5.5 pgsql=9.2 apache=2.2 perl5=5.16 However, that seems to be ignored. The build logs do show that make.conf being pulled in properly. Is there something else I need to set? The bsd.apache.mk file implies that the above is the correct way to do it. I had the same problem but found that this worked: APACHE_PORT=www/apache22 -- Mike Clarke ___ 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: service doen't get started at boottime, but can start manually
On Sunday 07 Sep 2014 04:03:25 Scot Hetzel wrote: I had a look at scripts/refdb.in, it is not a proper rc script for FreeBSD, as it is missing several keywords: # PROVIDE: - all scripts need this I'm not sure that PROVIDE is still mandatory. But run_rc_command() in rc.subr does require name to be defined. There are several example scripts at https://www.freebsd.org/doc/en/articles/rc-scripting/index.html, most of which which do not include PROVIDE. Only one of the example scripts uses PROVIDE but the text implies that it's only needed if other scripts are to depend on it. https://www.freebsd.org/doc/en/articles/rc-scripting/rcng-hookup.html -- Mike Clarke ___ 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: service doen't get started at boottime, but can start manually
On Sunday 07 Sep 2014 09:53:51 Scot Hetzel wrote:
The scripts in 3-6, and 8 are wrong. According to /etc/rc.subr, the
'# PROVIDE: ' is mandatory to detect a rc script:
Well it appears that they are only half wrong.
Scripts without PROVIDE will work if they're in /etc/rc.d but not if
in /usr/local/etc/rc.d. I have run a test case to confirm this.
In /etc/rc we have:
95 # Do a first pass to get everything up to $early_late_divider so
that
96 # we can do a second pass that includes $local_startup directories
97 #
98 files=`rcorder ${skip} ${skip_firstboot} /etc/rc.d/* 2/dev/null`
99
100 _rc_elem_done=' '
101 for _rc_elem in ${files}; do
102 run_rc_script ${_rc_elem} ${_boot}
103 _rc_elem_done=${_rc_elem_done}${_rc_elem}
104
105 case $_rc_elem in
106 */${early_late_divider})break ;;
107 esac
108 done
109
110 unset files local_rc
111
112 # Now that disks are mounted, for each dir in $local_startup
113 # search for init scripts that use the new rc.d semantics.
114 #
115 case ${local_startup} in
116 [Nn][Oo] | '') ;;
117 *) find_local_scripts_new ;;
118 esac
119
120 # The firstboot sentinel might be on a newly mounted filesystem;
look for it
121 # again and unset skip_firstboot if we find it.
122 if [ -e ${firstboot_sentinel} ]; then
123 skip_firstboot=
124 fi
125
126 files=`rcorder ${skip} ${skip_firstboot} /etc/rc.d/* ${local_rc}
2/dev/null`
127 for _rc_elem in ${files}; do
128 case $_rc_elem_done in
129 * $_rc_elem *)continue ;;
130 esac
131
132 run_rc_script ${_rc_elem} ${_boot}
133 done
So all files in /etc/rd.d are potential startup scripts but those in
/usr/local/etc must meet the requirement of having a PROVIDE line.
This inconsistency isn't mentioned anywhere in the examples in
https://www.freebsd.org/doc/en/articles/rc-scripting/index.html so
it looks like either the documentation needs this adding or perhaps
the test for PROVIDE in find_local_scripts_new() should be replaced by
a test for defining the variable name (which is mandatory) or
perhaps there's no longer any need to apply this test?
--
Mike Clarke
___
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 fails to set up gimp support for xsane
I first raised this issue a few weeks ago under the thread Cant get gimp to use xsane with FreeBSD 10.-RELRASE but after further testing it's starting to look like an issue with poudriere so I thought it appropriate to start a new thread. The problem doesn't appear to be related to the version of gimp, xsane or the OS but, for the record, here's what I currently have curlew:/home/mike% uname -a FreeBSD curlew.lan 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r268512: Thu Jul 10 23:44:39 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 curlew:/home/mike% pkg info gimp-app xsane pkg poudriere gimp-app-2.8.10_5,1 xsane-0.999_2 pkg-1.3.7 poudriere-3.0.17 The problem first became apparrent with gimp and xsane installed from packages. Despite pkg info indicating that xsane was built with gimp plugin support the option to use xsane did not appear in gimp's File - Create menu. The output from gimp --verbose contained the following message: Parsing '/home/mike/.gimp-2.8/pluginrc' Querying plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' /home/mike/.gimp-2.8/plug-ins/xsane: GIMP support missing (gimp:4780): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error Terminating plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' Thinking that there might be a problem with the copy of xsane in the FreeBSD repository I then used poudriere to build a package for xsane and installed that but had exactly the same problem. I then used portmaster to build xsane from ports with exactly the same options and could access xsane from gimp without any problem. I've attached output from pkg info for all three versions of the package where it can be seen that the working package built by portmaster requires 8 libgimp* shared libs but these do not appear in the output for the faulty packages from the FreeBSD repository or my poudriere repository = Details of xsane built with portmaster = curlew:/home/mike% pkg info xsane xsane-0.999_2 Name : xsane Version: 0.999_2 Installed on : Thu Sep 4 20:32:06 BST 2014 Origin : graphics/xsane Architecture : freebsd:9:x86:64 Prefix : /usr/local Categories : graphics Licenses : GPLv2 Maintainer : koalat...@gmail.com WWW: http://www.xsane.org/ Comment: Gtk-based X11 frontend for SANE (Scanner Access Now Easy) Options: DOCS : on GIMP : on NLS: on Shared Libs required: libtiff.so.4 libsane.so.1 libpng15.so.15 libpangoft2-1.0.so.0 libpangocairo-1.0.so.0 libpango-1.0.so.0 liblcms.so.1 libjpeg.so.11 libintl.so.9 libgtk-x11-2.0.so.0 libgobject-2.0.so.0 libglib-2.0.so.0 libgio-2.0.so.0 libgimpwidgets-2.0.so.0 libgimpui-2.0.so.0 libgimpmodule-2.0.so.0 libgimpmath-2.0.so.0 libgimpconfig-2.0.so.0 libgimpcolor
Re: Cant get gimp to use xsane with FreeBSD 10.-RELRASE
On Monday 18 August 2014 21:10:46 I wrote: The output from gimp --verbose shows the following problem: Parsing '/home/mike/.gimp-2.8/pluginrc' Querying plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' /home/mike/.gimp-2.8/plug-ins/xsane: GIMP support missing Terminating plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' Writing '/home/mike/.gimp-2.8/pluginrc' After doing a bit more digging around I've tracked it down to a problem with xsane-0.999_2 when installed with pkg install Running gimp-app-2.8.10_5,1 and xsane-0.999_2 installed from packages on 9,3-RELEASE I get the error message Parsing '/home/mike/.gimp-2.8/pluginrc' Querying plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' /home/mike/.gimp-2.8/plug-ins/xsane: GIMP support missing Terminating plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' But after deleting xsane and building the same version (0.999_2) from ports with exactly the same options (+DOCS +GIMP +NLS) gimp runs just fine and shows the xsane line in the File - Create menu. Could it be that the copy of xsane-0.999_2 at pkg.FreeBSD.org/freebsd:9:x86:64/latest has been corrupted? -- Mike Clarke ___ 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: Cant get gimp to use xsane with FreeBSD 10.-RELRASE
On Friday 29 August 2014 00:35:03 Carlos Jacobo Puga Medina wrote: I installed graphics/gimp-app including the xsane plugin on 11-CURRENT/i386 and it works fine. Current versions installed: % pkg info gimp-app xsane gimp-app-2.8.10_5,1 xsane-0.999_2 Port configure options chosen: % make -C /usr/ports/graphics/gimp-app/ pretty-print-config +AA +DBUS -GHOSTSCRIPT +GVFS +HELPBROWSER -JASPER +LIBEXIF +LIBMNG +LIBRSVG2 +POPPLER -SIMD +WMF I've rebuilt gimp-app with exactly the same options as you and still have the problem, even after upgrading from 2.8.10_4 to 2.8.10_5. As it turns out I'm having a number of other inexplicable problems with 10.0-RELEASE and I'm reverting to 9.3-RELEASE. I don't have any problems with gimp and xsane on 9.3 but I'm still running gimp- app-2.8.10_3,1 there so this might be a problem with versions later than 2.8.10_3 - I'll need to run some tests before the next time I upgrade my ports. -- Mike Clarke ___ 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
Cant get gimp to use xsane with FreeBSD 10.-RELRASE
I've just upgraded from 9,1-RELEASE to 10.0-RELEASE After deleting and reinstalling all packages I can't get gimp to use the xsane dialog. The option to use xsane doesn;t appear in the File - Create menu The output from gimp --verbose shows the following problem: Parsing '/home/mike/.gimp-2.8/pluginrc' Querying plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' /home/mike/.gimp-2.8/plug-ins/xsane: GIMP support missing Terminating plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane' Writing '/home/mike/.gimp-2.8/pluginrc' But xsane was built with gimp support curlew:/home/mike% pkg query %n %Ok %Ov xsane gimp-app xsane DOCS on xsane GIMP on xsane NLS on gimp-app AA on gimp-app DBUS on gimp-app GHOSTSCRIPT off gimp-app GVFS off gimp-app HELPBROWSER on gimp-app JASPER off gimp-app LIBEXIF on gimp-app LIBMNG on gimp-app LIBRSVG2 on gimp-app POPPLER on gimp-app SIMD on gimp-app WMF on curlew:/home/mike% pkg info gimp-app xsane gimp-app-2.8.10_3,1 Xsane-0.999_1 And I have the symbolic link in my plug-ins subdirectory. curlew:/home/mike% ls -l ~/.gimp-2.8/plug-ins/ total 1 lrwxr-xr-x 1 mike mike 20 18 Aug 15:17 xsane@ - /usr/local/bin/xsane And the target exists curlew:/home/mike% ls -l /usr/local/bin/xsane -r-xr-xr-x 1 root wheel 602240 18 Aug 20:06 /usr/local/bin/xsane* I've tried this using packages and then by building gimp-app and xsane from ports with the same result each time. I had no problems on 9.0RELEASE with the same package versions and build options so I'm wondering if we have an issue specific to 10.RELEASE here. curlew:/home/mike% uname -a FreeBSD curlew.lan 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root@amd64- builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Mike Clarke ___ 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: Some suggestions about PKGNG documentation
Warren Block wrote: The documentation team has a standing offer to either assist with markup or accept content-only submissions and do the markup on them. That's good to know. I was under the impression it had to be submitted as DocBook XML. 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: Some suggestions about PKGNG documentation
Patrick Powell wrote: TUTORIAL: The Savant's Guide To Ports, Packages, PkgNG Try to put a lot of the information about pkgng, repositories, etc. in a single place. I suggest a tutorial format, rather than a user manual format, with references to the various man pages, other documents, etc. Your suggestions sound good to me. Unfortunately, it's not like there's a team of tech writers sitting around waiting for suggestions of things to write and put into the docs. Rather, updating pretty much anything in the documentation -- or the ports for that matter -- requires suggesting the actual changes you want in the form of patches that replace the existing content with your version. http://lists.freebsd.org/mailman/listinfo/freebsd-doc http://www.freebsd.org/docproj/ http://www.freebsd.org/doc/en/books/fdp-primer/book.html After starting down this road, you may decide it's less of an ordeal just to write something yourself and put it up on your own blog. :/ ___ 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: pdksh put path to man page in /etc/shells
On 3/19/14, 7:22 AM, Bob Willcox wrote: When portupgrade updated the shells/pdksh port on my system today it stored the path to its man page in the /etc/shells file rather than the path to the executable file, thus causing mail and login to fail for accounts that use /usr/local/bin/ksh as their login shell. Bob Hello Specifically I see this in /etc/shells : /usr/local/man/man1/ksh.1.gz instead of: /usr/local/bin/ksh It happens both from building from source and when installing using pkg. How do we report this - to the port maintainer rodr...@freebsd.org ? thanks, -- Mike ___ 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
Recompile of xfce due to new xorg lib bump broke my desktop
Hello, So i updated my ports yesterday using the method described in UPDATING, everything was fine till i rebooted my desktop today. I logged in and everything looked different. The fonts are messed up, half the icons don't display (some are blank some show an X). Everrything looks blocky, changing the styles or icon sets does nothing, my keybinds dont work, it's a mess. I was already using new xorg prior to this, so i don't think that's the problem. Any ideas what caused this and how i can fix it, or start from scratch if i have to? 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: Recompile of xfce due to new xorg lib bump broke my desktop
On 04/23/14 14:32, Sergey V. Dyatko wrote: On Wed, 23 Apr 2014 13:51:08 -0400 Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, So i updated my ports yesterday using the method described in UPDATING, everything was fine till i rebooted my desktop today. I logged in and everything looked different. The fonts are messed up, half the icons don't display (some are blank some show an X). Everrything looks blocky, changing the styles or icon sets does nothing, my keybinds dont work, it's a mess. I was already using new xorg prior to this, so i don't think that's the problem. Any ideas what caused this and how i can fix it, or start from scratch if i have to? 1. install sysutils/bsdadminscripts 2. run pkg_libchk -q 3. rebuilding packages from [2] should help. i'm using xfce on desktoplaptop, all forks fine after xorg lib bump, also look at 20140416 entry All is well again! I had to recompile xfce4-settings. Thanks 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
FreeBSD Port: www/tomcat-native
Hello,
It looks like the recent update of apr has broken this port. However
there is a simple fix.
LIB_DEPENDS=libapr-1.so.4:${PORTSDIR}/devel/apr1
needs to be changed to
LIB_DEPENDS=libapr-1.so.5:${PORTSDIR}/devel/apr1
Or perhaps its better not to specify the exact library version.
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: pkg upgrade today (20140320) breaks VirtualBox
Also noticed that since yesterday at least... its not in the latest repo.. only in quarterly and release. Same for other ports like kde... I guess those failed to build. How often is the latest repo updated? weekly? Guess the only option for those is build from ports. Mike On 20 March 2014 19:13:33 WET, CeDeROM cede...@tlen.pl wrote: On Thu, Mar 20, 2014 at 7:06 PM, Greg Rivers gcr+freebsd-po...@tharned.org wrote: I found it necessary to `pkg delete compat9x\*`. I don't know why that compat package is getting installed. Ugh, I have uninstalled that package, but before I have tried to reinstall virtualbox-ose... it seems its gone from repositories! Daaamn I need that VBox :-( # pkg install -x virtualbox Updating repository catalogue The following 9 packages will be installed: Installing php5: 5.4.26 Installing php5-xml: 5.4.26 Installing php5-simplexml: 5.4.26 Installing php5-json: 5.4.26 Installing virtualbox-ose-kmod: 4.3.8 Installing virtualbox-ose-kmod-legacy: 4.2.22 Installing php5-session: 5.4.26 Installing php5-soap: 5.4.26 Installing phpvirtualbox: 4.3.1_1 The installation will require 26 MB more space 5 MB to be downloaded -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
py-setuptools fails to install on 10-stable
Hello, devel/py-setuptools27 is a dependency of textproc/py-MarkupSafe, however it fails to install on 10-stable due to some conflict. === Installing for py27-setuptools27-2.0.1 === Checking if devel/py-setuptools27 already installed === Registering installation for py27-setuptools27-2.0.1 as automatic Installing py27-setuptools27-2.0.1...pkg-static: py27-setuptools27-2.0.1 conflicts with py27-setuptools-2.0.1 (installs files into the same place). Problematic file: /usr/local/lib/python2.7/site-packages/easy-install.pth.dist *** Error code 70 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: bash 4.3 problem
On 03/04/14 15:33, Albert Shih wrote: Hi all, I don't known if it's a problem with bash 4.3 or with bash 4.3-FreeBSD. But when you got a file with a name like (my_file) begin with a ( the completion don't work. Albert, This works just fine for me on two machines. GNU bash, version 4.2.45(1)-release (amd64-portbld-freebsd9.2) GNU bash, version 4.3.0(1)-release (amd64-portbld-freebsd10.0) Maybe you have something broken in /usr/local/etc/bash_completion.d. 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: 11-CURRENT iconv build failures
Same problem on 10-stable, I am unable to compile many ports including a VirtualBox which I depend on a daily basis. On 02/20/14 14:27, CiPHER nl wrote: Hello, I'm running FreeBSD 11-CURRENT r262235 (as of this morning) and building Virtualbox from ports (emulators/virtualbox-ose) fails for me. The Makefile contains USES=iconv. Removing that did not make it use the libiconv from ports instead of base iconv, as i had expected. Any pointers to how to get this fixed would be welcome. :) kBuild: Compiling VBox-kStuffStaticBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/libs/kStuff/iprt/kRdrFile-iprt.cpp kBuild: Linking VBox-kStuffStaticBldProg kBuild: Installing VBox-kStuffStaticBldProg = /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a kBuild: Compiling scm - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scm.cpp kBuild: Compiling scm - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmdiff.cpp kBuild: Compiling scm - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmrw.cpp kBuild: Compiling scm - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmstream.cpp kBuild: Compiling scm - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmsubversion.cpp kBuild: Linking scm /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o): In function `rtstrConvertCached': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:200: undefined reference to `libiconv' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:184: undefined reference to `libiconv_open' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:244: undefined reference to `libiconv_close' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o): In function `rtStrConvertUncached': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:315: undefined reference to `libiconv_open' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:330: undefined reference to `libiconv' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:351: undefined reference to `libiconv_close' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:340: undefined reference to `libiconv_close' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o): In function `rtStrIconvCacheDestroy': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:115: undefined reference to `libiconv_close' collect2: ld returned 1 exit status kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm] Error 1 The failing command: @g++46-m64 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmdiff.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmrw.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmstream.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmsubversion.o -L/usr/local/lib -lpthread -lrt /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/rel ease/lib/RuntimeBldProg.a -lpthread -lssl -lcrypto *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. make: stopped in /usr/ports/emulators/virtualbox-ose ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports
FreeBSD Port: converters/recode
Hello, I am having trouble compiling this. FreeBSD freebsd.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r261907: Fri Feb 14 20:18:46 EST 2014 root@freebsd.local:/usr/obj/usr/src/sys/FREEBSD amd64 ./fr-charname.h:4909:6: warning: illegal character encoding in string literal [-Winvalid-source-encoding] FBi-ou,/* \377\070 */ ^~~~ 1029 warnings generated. libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c fr-charname.c -o fr-charname.o /dev/null 21 /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c -fPIC -DPIC -o .libs/hash.o libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c -o hash.o /dev/null 21 /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c libiconv.c libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c libiconv.c -fPIC -DPIC -o .libs/libiconv.o libiconv.c:50:3: warning: implicit declaration of function 'iconvctl' is invalid in C99 [-Wimplicit-function-declaration] iconvctl (conversion, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:50:25: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' iconvctl (conversion, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:51:33: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' iconvctl (conversion_to_utf8, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:102:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:104:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' ICONV_SET_TRANSLITERATE, transliterate); ^ 1 warning and 4 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/ports/converters/recode/work/recode-3.6/src 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: FreeBSD Port: converters/recode
Great, thanks! On 02/18/14 15:07, Dmitry Sivachenko wrote: Hello, This should be fixed after rev. 344949 has been committed. On 18 февр. 2014 г., at 23:14, Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, I am having trouble compiling this. FreeBSD freebsd.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r261907: Fri Feb 14 20:18:46 EST 2014 root@freebsd.local:/usr/obj/usr/src/sys/FREEBSD amd64 ./fr-charname.h:4909:6: warning: illegal character encoding in string literal [-Winvalid-source-encoding] FBi-ou,/* \377\070 */ ^~~~ 1029 warnings generated. libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c fr-charname.c -o fr-charname.o /dev/null 21 /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c -fPIC -DPIC -o .libs/hash.o libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c -o hash.o /dev/null 21 /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c libiconv.c libtool: compile: cc -DLIBDIR=\/usr/local/lib\ -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c libiconv.c -fPIC -DPIC -o .libs/libiconv.o libiconv.c:50:3: warning: implicit declaration of function 'iconvctl' is invalid in C99 [-Wimplicit-function-declaration] iconvctl (conversion, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:50:25: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' iconvctl (conversion, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:51:33: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' iconvctl (conversion_to_utf8, ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:102:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' ICONV_SET_TRANSLITERATE, transliterate); ^ libiconv.c:104:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE' ICONV_SET_TRANSLITERATE, transliterate); ^ 1 warning and 4 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/ports/converters/recode/work/recode-3.6/src 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
FreeBSD Port: www/chromium
Hello, I just updated to the latest version of chromium, now as soon as I attempt any operation chromium crashes with the following error. [77827:318843904:0123/145145:ERROR:form_data.cc(108)] Bad pickle of FormData, no version present [77827:318843904:0123/145145:ERROR:form_data.cc(108)] Bad pickle of FormData, no version present [77827:318843904:0123/145145:ERROR:form_data.cc(108)] Bad pickle of FormData, no version present 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: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]
On 01/13/14 03:42, Bernhard Fröhlich wrote: On Mon, Jan 13, 2014 at 7:46 AM, Craig Rodrigues rodr...@freebsd.org wrote: There is really no reason to make that dance so complicated or why you need to destroy your /usr/ports. WARNING: If there are issues with that ports please contact jkim@ Just wanted to let everyone know this compiles and works perfect for me on 10.0-PRE. The only issue I have is with the vboxwebsrv rc.d script, when I try to start it nothing happens, no errors, however manually running vboxwebsrv -b does the job. Thanks to everyone that's worked on this port, hopefully it will be committed soon. ___ 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: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]
On 01/17/14 14:17, Mike Jakubik wrote: Just wanted to let everyone know this compiles and works perfect for me on 10.0-PRE. The only issue I have is with the vboxwebsrv rc.d script, when I try to start it nothing happens, no errors, however manually running vboxwebsrv -b does the job. Thanks to everyone that's worked on this port, hopefully it will be committed soon. Sigh, guess I spoke too soon. This just happened while copying a large file from a shared folder to a raw disk partition. Restarted and repeated the operation but it worked fine this time. Jan 17 16:25:01 bigjail kernel: pid 95177 (VBoxHeadless), uid 0: exited on signal 11 (core dumped) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: emulators/virtualbox-ose
Hello, Having trouble compiling on a freshly installed 10.0-PRE, below is the error. The only port options selected are GUESTADDITIONS, VNC, WEBSERVICE. Thanks. kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/VMM/testcase/tstVMStructRC.cpp kBuild: Linking tstVMStructRC Using built-in specs. COLLECT_GCC=g++46 COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/lto-wrapper Target: x86_64-portbld-freebsd10.0 Configured with: ./../gcc-4.6.4/configure --disable-bootstrap --disable-nls --libdir=/usr/local/lib/gcc46 --libexecdir=/usr/local/libexec/gcc46 --program-suffix=46 --with-as=/usr/local/bin/as --with-gmp=/usr/local --with-gxx-include-dir=/usr/local/lib/gcc46/include/c++/ --with-ld=/usr/local/bin/ld --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib --disable-libgcj --enable-languages=c,c++,objc,fortran --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/gcc46 --build=x86_64-portbld-freebsd10.0 Thread model: posix gcc version 4.6.4 (FreeBSD Ports Collection) COMPILER_PATH=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/bin/ LIBRARY_PATH=/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-m32' '-g' '-g' '-nostdlib' '-v' '-o' '/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC' '-L/usr/lib32' '-shared-libgcc' '-mtune=generic' '-march=x86-64' /usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/collect2 --eh-frame-hdr -m elf_i386_fbsd -V -dynamic-linker /libexec/ld-elf.so.1 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC -L/usr/lib32 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../.. /usr/lib32/crt1.o /usr/lib32/crti.o /usr/lib32/crtbegin.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o /usr/lib32/crtend.o /usr/lib32/crtn.o /usr/lib32/libc.so GNU ld (GNU Binutils) 2.24 Supported emulations: elf_x86_64_fbsd elf_i386_fbsd elf_x86_64 elf_i386 elf_l1om elf_l1om_fbsd elf_k1om elf_k1om_fbsd kBuild: Installing tstVMStructRC = /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC kBuild: Generating tstVMStructSize - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: ( unexpected /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: Error in command substitution kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] Error 2 kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. make: stopped in /usr/ports/emulators/virtualbox-ose I then tried again but with gcc47 but I got a different errror. Build: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp:40:0: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/include/iprt/vfslowlevel.h:217:120: warning: trigraph ??) ignored, use -trigraphs to enable [-Wtrigraphs] kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errinfo.cpp kBuild: Generating /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h /usr/local/bin/kmk_sed: file /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errmsg.sed line 31: Unmatched [ or [^ kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h] Error 1
USE_PYTHON version range no longer valid?
A port I maintain (sorta) can only be built under Python 2.2.1 through 2.4.x. The app isn't being developed any longer, so patches to get it to build under 2.5+ aren't likely to be forthcoming. The port Makefile previously had USE_PYTHON= 2.2-2.4, but it was changed this week to simply USE_PYTHON=2, with this comment: Python cleanup: - USE_PYTHON* = 2.X - USE_PYTHON* = 2 - USE_PYTHON* = 2.X+ - USE_PYTHON* = yes Reviewed by: python (mva, rm) Approved by: portmgr-lurkers (mat) By removing 2.4 as the maximum version, there are inevitable build errors for this app. Reverting to USE_PYTHON= 2.2-2.4 results in 'make' failing with this: === py27-4suite-1.0.b1_1 needs an unsupported version of Python. I'm fine with that, although I'm unsure what the ramifications are of Python 2.4 being unsupported. Do people have the option of installing Python 2.4.6 and using it with this port, or do we need to decommission the port? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: emulators/virtualbox-ose
On 01/15/14 16:37, Bernhard Fröhlich wrote: On Wed, Jan 15, 2014 at 7:58 PM, Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, Having trouble compiling on a freshly installed 10.0-PRE, below is the error. The only port options selected are GUESTADDITIONS, VNC, WEBSERVICE. Thanks. kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/VMM/testcase/tstVMStructRC.cpp kBuild: Linking tstVMStructRC Using built-in specs. kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h' *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. Could it be that you have a custom kernel and removed COMPAT_FREEBSD32 option from it? Doh, so sorry! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: emulators/virtualbox-ose
Hello, I've updated to the recent 4.2.20 version only to find a runtime error due to libstdc++, I see the recent commit made to fix this on 10, however I am running 9-stable and do not have compat9x installed. I wish thisport did not need gcc to compile, it always seems to be a problem. $ VirtualBox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found $ uname -a FreeBSD freebsd.local 9.2-STABLE FreeBSD 9.2-STABLE #0: Wed Dec 11 13:51:20 EST 2013 mjakubik@freebsd.local:/usr/obj/usr/src/sys/FREEBSD amd64 $ pkg info|grep virtualbox virtualbox-ose-4.2.20 A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.20 VirtualBox kernel module for FreeBSD $ pkg info|grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 /etc/make.comf WITH_CLANG_IS_CC=true WITHOUT_GCC=true 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: FreeBSD Port: emulators/virtualbox-ose
On 12/11/13 15:32, Bernhard Fröhlich wrote: I can only repeat myself. It will not happen any day soon because clang does not support global register variables and they do not seem to have any interest to implement that. Got it. Could you please send me the following output just to verify: strings /usr/lib/libstdc++.so.6 | grep GLIBCXX $ strings /usr/lib/libstdc++.so.6 | grep GLIBCX GLIBCXX_3.4 GLIBCXX_3.4.1 GLIBCXX_3.4.2 GLIBCXX_3.4.3 GLIBCXX_3.4.4 GLIBCXX_3.4.5 GLIBCXX_3.4.6 GLIBCXX_3.4.7 GLIBCXX_3.4.8 GLIBCXX_3.4.9 GLIBCXX_FORCE_NEW make delete-old and delete-old-libs does not remove anything from my system at this point, i am going to try compile again but with gcc47 this time. 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: FreeBSD Port: emulators/virtualbox-ose
On 12/11/13 18:34, Bernhard Fröhlich wrote: Am 11.12.2013 22:16 schrieb Mike Jakubik mike.jaku...@intertainservices.com mailto:mike.jaku...@intertainservices.com: On 12/11/13 15:51, Bernhard Fröhlich wrote: That definitely is the libstdc++ from our ancient gcc 4.2 in base. Could you try to temporary rename the so and try to start vbix again? Don't forget to rename it afterwards if there are any binaries that still need it. Renaming /usr/lib/libstdc++.so.6 addresses the problem. Do you know a way to check if anything else might need this? Thank you. You could either try manually with ldd which so a binary needs or I think bsdadmin scrips contains some libcheck script that can check that in bulk. Ahh yes, pkg_libchk did the job, it appears nothing was using this, thanks again. ___ 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: www/linux-f10-flashplugin11 r333784 breaks nspluginwrapper
On 11/14/13 14:25, Greg Rivers wrote: r333784 | jkim | 2013-11-14 12:45:54 -0600 (Thu, 14 Nov 2013) | 4 lines Move the libflashplayer.so to its own directory. Approved by:eadler (maintainer) FYI, now nspluginwrapper can't find libflashplayer.so: $ nspluginwrapper -a -v -u Auto-update plugins from /usr/local/lib/browser_plugins Looking for plugins in /usr/local/lib/browser_plugins Auto-update plugins from /local/gcr/.mozilla/plugins Looking for plugins in /local/gcr/.mozilla/plugins Update plugin /local/gcr/.mozilla/plugins/npwrapper.libflashplayer.so NPAPI plugin /usr/local/lib/browser_plugins/libflashplayer.so is no longer available, removing wrapper Remove plugin /local/gcr/.mozilla/plugins/npwrapper.libflashplayer.so I had the same problem, this fixed it for me. % nspluginwrapper -v -a -i ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: emulators/virtualbox-ose-additions
Hello, I am unable to compile this on FreeBSD 10. This is on a freshly installed FreeBSD 10.0-BETA1 #0 r256420. kBuild: Linking VBoxControl kBuild: Linking VBoxService kBuild: Linking VBoxClient /usr/bin/ld: cannot find -lsupc++ cc: error: linker command failed with exit code 1 (use -v to see invocation) kmk: *** [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] Error 1 The failing command: @cc -m64 -o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/main.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/seamless.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/seamless-host.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/thread.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/display.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 -L/usr/X11R6/lib -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -lX11 -lXrandr -lXt -lsupc++ -lgcc_eh -lXext -lXmu /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.2.18/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a -lpthread kmk: *** Waiting for unfinished jobs kmk: *** Exiting with status 2 *** Error code 2 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
FreeBSD Port: security/php5-filter
Hello, I am having trouble compiling this port, below is the error. cc -I. -I/usr/ports/security/php5-filter/work/php-5.4.20/ext/filter -DPHP_ATOM_INC -I/usr/ports/security/php5-filter/work/php-5.4.20/ext/filter/include -I/usr/ports/security/php5-filter/work/php-5.4.20/ext/filter/main -I/usr/ports/security/php5-filter/work/php-5.4.20/ext/filter -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -DHAVE_CONFIG_H -O2 -pipe -mssse3 -march=native -fno-strict-aliasing -c /usr/ports/security/php5-filter/work/php-5.4.20/ext/filter/logical_filters.c -fPIC -DPIC -o .libs/logical_filters.o In file included from /usr/ports/security/php5-filter/work/php-5.4.20/ext/filter/logical_filters.c:25: /usr/local/include/php/ext/pcre/php_pcre.h:29:10: fatal error: 'pcre.h' file not found #include pcre.h ^ 1 error generated. *** [logical_filters.lo] Error code 1 Stop in /usr/ports/security/php5-filter/work/php-5.4.20/ext/filter. # locate pcre.h /usr/local/include/pcre.h /usr/local/include/php/ext/pcre/php_pcre.h /usr/local/share/doc/pcre/html/pcre.html 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
