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: 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
libreoffice: 6.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
.2.so libHSxhtml-3000.2.1-ghc8.0.2.so Annotations: repo_type : binary repository : FreeBSD Flat size : 1.18GiB Description: The Glasgow Haskell Compiler is a state-of-the-art, open source, compiler and interactive environment for the functional language Haskell. Highlights: * Supports the entire Haskell 2010 language plus a wide variety of extensions. * Has particularly good support for concurrency and parallelism, including support for Software Transactional Memory (STM). * Generates fast code, particularly for concurrent programs. * Works on several platforms including FreeBSD, Windows, Mac, Linux, most varieties of Unix, and several different processor architectures. * Has extensive optimisation capabilities, including inter-module optimisation. * Compiles Haskell code either directly to native code or using LLVM as a back-end. It can also generate C code as an intermediate target for porting to new platforms. The interactive environment compiles Haskell to bytecode, and supports execution of mixed bytecode/compiled programs. * Profiling is supported, both by time/allocation and various kinds of heap profiling. * Comes with several libraries, and thousands more are available on Hackage. WWW: http://www.haskell.org/ghc/ -- 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 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: How to use cached packages
On Thu, 20 Apr 2017 13:17:35 -0700 Freddie Cash 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 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 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 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"
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&stype=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 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"
Re: Packages lagging for 10.2
On Tue, 08 Sep 2015 08:46:48 +0200
Jimmy Renner 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 wrote: > +--On 15 août 2015 22:25:47 +0200 Xavier 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"
Re: pkgng deviates from defaults?
On Mon, 09 Mar 2015 07:04:30 -0700 "Chris H" 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"
Re: Overriding binary package with local build
On Mon, 9 Mar 2015 09:43:24 + heasley 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: www/midori dislikes the letter h
On Fri, 27 Feb 2015 16:41:46 +0200 Beeblebrox 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"
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 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"
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: 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: 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: 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 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: 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"
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"
Poudriere fails to set up gimp support for xsane
.0 libgimpconfig-2.0.so.0 libgimpcolor-2.0.so.0 libgimpbase-2.0.so.0 libgimp-2.0.so.0 libgdk_pixbuf-2.0.so.0 libgdk-x11-2.0.so.0 libfreetype.so.6 libfontconfig.so.1 libcairo.so.2 libatk-1.0.so.0 Flat size : 4.72MiB Description: XSANE is a gtk based X11 frontend for SANE (Scanner Access Now Easy). It works either standalone or as a GIMP plugin. WWW: http://www.xsane.org/ = Details of xsane built with poudriere Note 8 missing shared libs: 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-2.0.so.0 libgimpbase-2.0.so.0 libgimp-2.0.so.0 = curlew:/home/mike% pkg info xsane xsane-0.999_2 Name : xsane Version: 0.999_2 Installed on : Fri Sep 5 10:29:08 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 libgdk_pixbuf-2.0.so.0 libgdk-x11-2.0.so.0 libfreetype.so.6 libfontconfig.so.1 libcairo.so.2 libatk-1.0.so.0 Annotations: repo_type : binary repository : poudriere Flat size : 4.71MiB Description: XSANE is a gtk based X11 frontend for SANE (Scanner Access Now Easy). It works either standalone or as a GIMP plugin. WWW: http://www.xsane.org/ = Details of xsane installed from FreeBSD repository Note the same 8 missing shared libs but also an extra 10 libX* shared libs not present in the other 2 versions = curlew:/home/mike% pkg info xsane xsane-0.999_2 Name : xsane Version: 0.999_2 Installed on : Fri Sep 5 10:40:15 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 libgdk_pixbuf-2.0.so.0 libgdk-x11-2.0.so.0 libfreetype.so.6 libfontconfig.so.1 libcairo.so.2 libatk-1.0.so.0 libXrender.so.1 libXrandr.so.2 libXinerama.so.1 libXi.so.6 libXfixes.so.3 libXext.so.6 libXdamage.so.1 libXcursor.so.1 libXcomposite.so.1 libX11.so.6 Annotations: repo_type : binary repository : FreeBSD Flat size : 4.71MiB Description: XSANE is a gtk based X11 frontend for SANE (Scanner Access Now Easy). It works either standalone or as a GIMP plugin. WWW: http://www.xsane.org/ ===== -- 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 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: [ImageMagick] build problem
andrew clarke wrote: > On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill (david at catwhisker.org) wrote: > > On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: > > > When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build > > > error: > > > > > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5 > > >/tests/.libs/co nstitute -storagetype > > > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > > > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check > > > failed: 6615/0.0587497/0.843137 FAIL: > > > tests/constitute_double_cmy.sh > > > > For what it's worth, I did not encounter this. > > Me neither. I get this problem both with the default options and with the same options as you, i.e. curlew:/usr/ports/graphics/ImageMagick# make showconfig ===> The following configuration options are available for ImageMagick-nox11-6.4.7.5: X11=off "X11 support" IMAGEMAGICK_TESTS=on "Run bundled self-tests after build" IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)" IMAGEMAGICK_PERL=off "Perl support" IMAGEMAGICK_MODULES=off "Modules support (broken)" IMAGEMAGICK_BZLIB=on "Bzlib support" IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support" IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)" IMAGEMAGICK_LCMS=off "LCMS support" IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)" IMAGEMAGICK_TTF=off "Freetype support" IMAGEMAGICK_FONTCONFIG=off "Fontconfig support" IMAGEMAGICK_JPEG=on "JPG format support" IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)" IMAGEMAGICK_PNG=on "PNG format support" IMAGEMAGICK_TIFF=on "TIFF format support" IMAGEMAGICK_FPX=off "FPX format support" IMAGEMAGICK_JBIG=off "JBIG format support" IMAGEMAGICK_JPEG2000=off "JPEG2000 format support" IMAGEMAGICK_DOT=off "GraphViz dot graphs support" IMAGEMAGICK_WMF=off "WMF format support" IMAGEMAGICK_SVG=off "SVG format support" IMAGEMAGICK_PDF=off "PDF format support" IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support" curlew:/usr/ports/graphics/ImageMagick# uname -a FreeBSD curlew.lan 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Sat Dec 13 10:56:34 GMT 2008 r...@curlew.lan:/usr/obj/usr/src/sys/GENERIC i386 My ports were last updated on Dec 12 09:24 -- 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"
