FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ www/drupal7 | 7.32| 7.34 +-+ x11-fm/xdiskusage | 1.48| 1.50 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt 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"
www/opera: looses plugins on restart
Each time Opera is re-started (or started for first time), it looses track of all plugins. Plugins (like flash) must be re-introduced. Start Opera, go to "opera:plugins", nothing. Go to: Settings > preferences > content > Plug-in options => shows empty list Find New => Plugins get listed, "opera:plugins" updates and list plugins correctly Close Opera and restart, back to zero. -- FreeBSD_amd64_11-Current_RadeonKMS ___ 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 update >> pkg install abort traps today Thursday and an off-topic
pkg update Downloaded new pkg database today. pkg install >>> abort trap every two of three "pkg install ..." (only one has proceeded.) This browser won't permit paste-ins, I've posted it in the forum in two threads (Xorg and Ports sections) pkg-1.4.0a3 Q 2is this to be addressed to freebsd-ports@freebsd.org OR po...@freebsd.org Q 3similar for p...@freebsd.org, is that instead or also freebsd-...@freeebsd.org Q 4How is pkg-devel supposed to be installed to fix the OP topic if it cannot install once it has been deinstalled, no pkg remaining to qualify it for registering which I think happens before it installs Q 5 Will we see a /var/db/pkg option in /pkg/ so that the above can be 'switched over' a few weeks of the year during such problematic times for reliability, when and if we have the time to code one up and beta test it. ___ 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 update >> pkg install abort traps today Thursday and an off-topic
On Thu, Nov 20, 2014 at 03:59:51AM -0800, Jeffrey Bouquet via freebsd-ports wrote: > pkg update > Downloaded new pkg database today. > > pkg install >>> abort trap > every two of three "pkg install ..." (only one has proceeded.) > > This browser won't permit paste-ins, I've posted it in the forum in two > threads > (Xorg and Ports sections) > > pkg-1.4.0a3 > We pkg is now at 1.4.0.b2 which have addressed all the reported bygs regards, Bapt pgpK4IGvsMVK4.pgp Description: PGP signature
Re: pkg problem
On 11/20/14 04:19, Jeffrey Bouquet wrote: > Only one port has not failed at "pkg install port" ... after today's > update and > also failed at deinstall pkg >> install pkg-devel to try to fix it. > > [ Duplicate post, so I could post the error and this update. ] > > > Script started on Thu Nov 20 04:09:36 2014 > > > pkg --version > 1.4.0.beta2 # pkg-devel newly installed, did not fix the below. > > pkg install tk86 > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, p2, > PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function > pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. Child > process pid=41497 terminated abnormally: Abort trap: 6 > > > Script done on Thu Nov 20 04:10:25 2014 ___ 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"
Request for (i386) testing: american fuzzy lop
I'm looking for testers for a port of American fuzzy lop. Quoting the pkg-descr: | American fuzzy lop is a fuzzer that employs a novel type of compile-time | instrumentation and genetic algorithms to automatically discover clean, | interesting test cases that trigger new internal states in the targeted | binary. This substantially improves the functional coverage for the | fuzzed code. | | WWW: http://lcamtuf.coredump.cx/afl/ The shar file is available at: http://www.fabiankeil.de/sourcecode/freebsd/afl-60b.shar The port is supposed to work on amd64 and i386 but so far it has only been tested on amd64 (with 64bit binaries). By default the port is supposed to build in jails, but actually using it requires shmget() which is unlikely to be available in build jails. If you have access to an i386 system, but no time to read documentation, you can still help by building a package outside a jail with the TEST_INSTRUMENTATION option enabled. Fabian pgpXfhI1gtocq.pgp Description: OpenPGP digital signature
Re: pkg update >> pkg install abort traps today Thursday and an off-topic
On Thu, 20 Nov 2014 13:13:15 +0100, Baptiste Daroussin stated: >We pkg is now at 1.4.0.b2 which have addressed all the reported bygs Port: pkg-devel-1.4.0.b2 Path: /usr/ports/ports-mgmt/pkg-devel Info: Package manager The regular branch is older. Port: pkg-1.3.8_3 Path: /usr/ports/ports-mgmt/pkg Info: Package manager Are you recommending that we should update to the newer development branch or will the older stable branch be updated shortly to reflect the demise of the known bugs? -- Jerry pgply3OwXISvd.pgp Description: OpenPGP digital signature
Re: pkg problem
On Thu, Nov 20, 2014 at 04:24:46AM -0800, Jeffrey Bouquet via freebsd-stable wrote: > > On 11/20/14 04:19, Jeffrey Bouquet wrote: > > Only one port has not failed at "pkg install port" ... after today's > > update and > > also failed at deinstall pkg >> install pkg-devel to try to fix it. > > > > [ Duplicate post, so I could post the error and this update. ] > > > > > > Script started on Thu Nov 20 04:09:36 2014 > > > > > > pkg --version > > 1.4.0.beta2 # pkg-devel newly installed, did not fix the below. > > > > pkg install tk86 > > Updating FreeBSD repository catalogue... > > FreeBSD repository is up-to-date. > > All repositories are up-to-date. > > > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, p2, > > PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function > > pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. Child > > process pid=41497 terminated abnormally: Abort trap: 6 > > > > > > Script done on Thu Nov 20 04:10:25 2014 Is that with pkg.freebsd.org repository, or custom one? regards, Bapt pgpS_BBzSecoI.pgp Description: PGP signature
Re: latex-texmf required-by
Russell L. Carter wrote: > I do not love the 2+ hours it takes to build the text/latex-texmf > port. I use pkg(8) to maintain a cluster of machines, and I've > checked the major culprits and I don't see how the latex-texmf > dependency occurs. (I don't specify it explicitly.) [snip] > What is the definitive way to figure out how this dependency has got > itself insinuated into my installed ports? There is no ports category "text". Nor is there a port called latex-texmf. You probably mean print/texlive-texmf. On my system, a quick $ pkg info -r texlive-texmf suggests that print/texlive-texmf is a dependency of print/texlive-full (and by extension of several other TeX ports). However, a quick $ make -C /usr/ports/print/texlive-base all-depends-list|grep texmf suggests that print/texlive-base doesn't pull print/texlive-texmf in. So maybe texlive-base instead of texlive-full is for you. HTH, AvW -- Imbibo, ergo sum. pgpuSbbdceUrr.pgp Description: PGP signature
Re: pkg update >> pkg install abort traps today Thursday and an off-topic
On 11/20/14 12:53, Jerry wrote: > Are you recommending that we should update to the newer development branch or > will the older stable branch be updated shortly to reflect the demise of the > known bugs? No. If you're already running pkg-devel, then please update to the latest pkg-devel. Known bugs have been addressed in pkg-devel, but it's still in beta-test, and there may well be other bugs as yet unreported. If you aren't running pkg-devel, but you would like to help testing and you have systems where you can fiddle about with the installed packages without too much consequence, then please consider testing with pkg-devel. Otherwise, stick with the regular pkg until we release pkg-1.4.0. Cheers, Matthew signature.asc Description: OpenPGP digital signature
How to stay with GnuPG 2.0.x (security/gnupg20)
I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26: # pkg version |grep gnupg gnupg-2.0.26_1 < However, GnuPG 2.1 is offered as an update: # pkg version -vIL= gnupg-2.0.26_1 < needs updating (index has 2.1.0) Inspecting the ports tree show that there are two different ports: security/gnupg20 and security/gnupg. How can I stay with security/gnupg20? Portmaster/pkg currently forces me to upgrade. Is there a switch in /etc/make.conf? Regards, Peter ___ 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: Request for (i386) testing: american fuzzy lop
On 2014-11-20 14:43, Fabian Keil wrote:> Quoting the pkg-descr:
> | American fuzzy lop is a fuzzer that employs a novel type of compile-time
> | instrumentation and genetic algorithms to automatically discover clean,
> | interesting test cases that trigger new internal states in the targeted
> | binary. This substantially improves the functional coverage for the
> | fuzzed code.
> |
> | WWW: http://lcamtuf.coredump.cx/afl/
I very much welcome this effort; I myself have tried to create a port
for it, but it required a whole lot of hacks (AFL is intertwined with
internals of GCC, which I failed to make work); I ended up needing
to rewrite it's assembly filters in a fairly hackish way... Can't
remember precisely what the problem was though.
> The shar file is available at:
> http://www.fabiankeil.de/sourcecode/freebsd/afl-60b.shar
>
> The port is supposed to work on amd64 and i386 but so far
> it has only been tested on amd64 (with 64bit binaries).
I don't know what this part is supposed to do:
# Workaround to make sure clang isn't confused for gcc
CC=${COMPILER_TYPE}
... but it seems to set CC to empty string on my machine; and I
get a whole bunch of this as the result:
--version: not found
make: "/usr/ports/Mk/Uses/compiler.mk" line 66: warning:
" --version" returned non-zero status
I also get this:
> ===> Building for afl-0.60b
> gmake[2]: Entering directory '/tmp/ports/security/afl/work/afl-0.60b'
> [*] Checking for the ability to compile x86 code...
> gcc: not found
>
> Oops, looks like your compiler can't generate x86 code.
>
> (If you are looking for ARM, see experimental/arm_support/README.)
>
> Makefile:46: recipe for target 'test_x86' failed
> gmake[2]: *** [test_x86] Error 1
> gmake[2]: Leaving directory '/tmp/ports/security/afl/work/afl-0.60b'
> ===> Compilation failed unexpectedly.
Missing GCC dependency?
(This is all on 10.0-RELEASE amd64).
___
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: Request for (i386) testing: american fuzzy lop
Vitaly Magerya wrote:
> On 2014-11-20 14:43, Fabian Keil wrote:> Quoting the pkg-descr:
> > | American fuzzy lop is a fuzzer that employs a novel type of compile-time
> > | instrumentation and genetic algorithms to automatically discover clean,
> > | interesting test cases that trigger new internal states in the targeted
> > | binary. This substantially improves the functional coverage for the
> > | fuzzed code.
> > |
> > | WWW: http://lcamtuf.coredump.cx/afl/
>
> I very much welcome this effort; I myself have tried to create a port
> for it, but it required a whole lot of hacks (AFL is intertwined with
> internals of GCC, which I failed to make work); I ended up needing
> to rewrite it's assembly filters in a fairly hackish way... Can't
> remember precisely what the problem was though.
0.57b and later have "[f]ixes to make things work on FreeBSD and
OpenBSD: use_64bit is inferred if not explicitly specified when
calling afl-as".
If you started with an earlier release, this might have been the problem.
> > The shar file is available at:
> > http://www.fabiankeil.de/sourcecode/freebsd/afl-60b.shar
> >
> > The port is supposed to work on amd64 and i386 but so far
> > it has only been tested on amd64 (with 64bit binaries).
>
> I don't know what this part is supposed to do:
>
> # Workaround to make sure clang isn't confused for gcc
> CC=${COMPILER_TYPE}
>
> ... but it seems to set CC to empty string on my machine; and I
> get a whole bunch of this as the result:
Interesting.
It was supposed to set CC for gmake to either clang or gcc,
otherwise a cc that is clang is treated as gcc.
However clobbering CC directly is obviously wrong and on
systems where cc is still gcc, the workaround shouldn't
be necessary anyway.
Does it work for you if you replace the line with:
MAKE_ARGS+= CC=${COMPILER_TYPE}
?
And if not, does it work if you remove it completely?
> --version: not found
> make: "/usr/ports/Mk/Uses/compiler.mk" line 66: warning:
> " --version" returned non-zero status
>
> I also get this:
>
> > ===> Building for afl-0.60b
> > gmake[2]: Entering directory '/tmp/ports/security/afl/work/afl-0.60b'
> > [*] Checking for the ability to compile x86 code...
> > gcc: not found
> >
> > Oops, looks like your compiler can't generate x86 code.
> >
> > (If you are looking for ARM, see experimental/arm_support/README.)
> >
> > Makefile:46: recipe for target 'test_x86' failed
> > gmake[2]: *** [test_x86] Error 1
> > gmake[2]: Leaving directory '/tmp/ports/security/afl/work/afl-0.60b'
> > ===> Compilation failed unexpectedly.
>
> Missing GCC dependency?
The base compiler should be fine, this is probably just the
fallout of the clobbered CC.
> (This is all on 10.0-RELEASE amd64).
Thanks for testing.
Fabian
pgpHZlAV7GB5F.pgp
Description: OpenPGP digital signature
Re: Request for (i386) testing: american fuzzy lop
On 11/20/14 17:02, Fabian Keil wrote:
> 0.57b and later have "[f]ixes to make things work on FreeBSD and
> OpenBSD: use_64bit is inferred if not explicitly specified when
> calling afl-as".
>
> If you started with an earlier release, this might have been
> the problem.
I was working with version 0.27b, so I guess lots of things changed
since then. They even have afl-clang now.
> Does it work for you if you replace the line with:
> MAKE_ARGS+= CC=${COMPILER_TYPE}
> ?
Yes, this fixes all the problems; AFL now installs fine.
I also tested actually compiling stuff with afl-clang and then running
afl-fuzz, which also seems to work.
I don't have an i386 system though.
> And if not, does it work if you remove it completely?
Removing it does not work ('test_build' fails).
___
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: Request for (i386) testing: american fuzzy lop
Vitaly Magerya wrote:
> On 11/20/14 17:02, Fabian Keil wrote:
> > Does it work for you if you replace the line with:
> > MAKE_ARGS+= CC=${COMPILER_TYPE}
> > ?
>
> Yes, this fixes all the problems; AFL now installs fine.
Great, thanks for the feedback. I updated the shar file in place.
Fabian
pgpyvKdGEvoVP.pgp
Description: OpenPGP digital signature
Re: Request for (i386) testing: american fuzzy lop
Fabian Keil writes:
> Vitaly Magerya wrote:
>> I don't know what this part is supposed to do:
>>
>> # Workaround to make sure clang isn't confused for gcc
>> CC=${COMPILER_TYPE}
>>
>> ... but it seems to set CC to empty string on my machine; and I
>> get a whole bunch of this as the result:
>
> Interesting.
>
> It was supposed to set CC for gmake to either clang or gcc,
> otherwise a cc that is clang is treated as gcc.
>
> However clobbering CC directly is obviously wrong and on
> systems where cc is still gcc, the workaround shouldn't
> be necessary anyway.
>
> Does it work for you if you replace the line with:
> MAKE_ARGS+= CC=${COMPILER_TYPE}
> ?
USE_GCC becomes a nop while setting explicitly fails
$ uname -rp
11.0-CURRENT amd64
$ echo CC=gcc49 >>/etc/.make.conf
$ make
...
===> Building for afl-0.60b
gmake[2]: Entering directory '/work/afl-0.60b'
[*] Checking for the ability to compile x86 code...
[+] All done! Be sure to review README - it's pretty short and useful.
gcc: not found
Why not patch the vendor Makefile? Here're my changes:
- use $(CC) --version to detect clang
- remove -g from CFLAGS (see WITH_DEBUG)
- strip(1) binaries during install
- global TESTing with generic option name
while poudriere caught Clang i386 failing
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
-fstack-protector -fno-strict-aliasing -Wall -D_FORTIFY_SOURCE=2
-Wno-pointer-sign -DAFL_PATH=\"/prefix/afl-0.60b/lib/afl\"
-DDOC_PATH=\"/prefix/afl-0.60b/share/doc/afl\" -DVERSION=\"0.60b\" -Wno-format
test-instr.c -o test-instr
/tmp/.afl-19244-1416499444.s: Assembler messages:
/tmp/.afl-19244-1416499444.s:222: Error: unknown pseudo-op: `.cfi_sections'
clang: error: assembler command failed with exit code 1 (use -v to see
invocation)
diff --git security/afl/Makefile security/afl/Makefile
index d7b2c93..bbe2992 100644
--- security/afl/Makefile
+++ security/afl/Makefile
@@ -9,10 +9,9 @@ MASTER_SITES= http://lcamtuf.coredump.cx/afl/releases/
MAINTAINER=f...@fabiankeil.de
COMMENT= Fast instrumented fuzzer
-USES= compiler gmake tar:tgz
+USES= gmake tar:tgz
-OPTIONS_DEFINE=DOCS TEST_INSTRUMENTATION
-TEST_INSTRUMENTATION_DESC= Execute tests expected to fail in jails
+OPTIONS_DEFINE=DOCS TEST
OPTIONS_DEFAULT= DOCS
ONLY_FOR_ARCHS=amd64 i386
@@ -20,17 +19,17 @@ ONLY_FOR_ARCHS_REASON= Uses binary instrumentation
.include
-# Workaround to make sure clang isn't confused for gcc
-MAKE_ARGS+=CC=${COMPILER_TYPE}
-
post-patch:
-.if ! ${PORT_OPTIONS:MTEST_INSTRUMENTATION}
+.if ! ${PORT_OPTIONS:MTEST}
# afl needs shmget() which usually isn't available in jails. Disabling
# the instrumentation tests makes sure building packages in jails works
# by default anyway.
${REINPLACE_CMD} -e 's@^\(all.*\) test_build@\1@' ${WRKSRC}/Makefile
.endif
- ${REINPLACE_CMD} -e 's@-O3@@' ${WRKSRC}/Makefile
+ ${REINPLACE_CMD} -e 's@ -O3@@; s@ -g@@' \
+ -e '/findstring clang/s@$$(CC)@$$(shell & --version)@' \
+ -e 's/install -m 755/${INSTALL_PROGRAM}/' \
+ ${WRKSRC}/Makefile
post-install:
.if ${PORT_OPTIONS:MDOCS}
-
VFEmail.net - http://www.vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
___
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: How to stay with GnuPG 2.0.x (security/gnupg20)
On Thu, 20 Nov 2014 14:40:21 +0100 "Dr. Peter Voigt" wrote: > I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26: > > # pkg version |grep gnupg > gnupg-2.0.26_1 < > > However, GnuPG 2.1 is offered as an update: > > # pkg version -vIL= > gnupg-2.0.26_1 < needs updating (index has > 2.1.0) > > Inspecting the ports tree show that there are two different ports: > security/gnupg20 and security/gnupg. > > How can I stay with security/gnupg20? Portmaster/pkg currently forces > me to upgrade. Is there a switch in /etc/make.conf? > > Regards, > Peter > ___ > 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" Well, found out that it is obviously a matter of changing a ports origin: # pkg set -o security/gnupg:security/gnupg20 Now portmaster/pkg do no longer "force" me to upgrade to version 2.1. I hope this is the right way to do, I am still too unexperienced with ports processing. Regards, Peter ___ 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"
system vimrc madness
> r372654 | alfred | 2014-11-16 23:55:10 +0100 (Sun, 16 Nov 2014) | 4 lines > Use vimrc from distribution. > Suggested by: many. There are significant problems with copying the *sample* vimrc to be used as the system vimrc. First of all, there is no way to disable reading it; even when ~/.vimrc is present, the system vimrc is still read - in that order, so ~/.vimrc cannot disable the loading of the system one; the only thing it can do is to undo the effects of system vimrc. I can immediately name three things which bit me after this change, but I cannot be positive there are not more: :set backup :set undofile :set mouse='a' The first two lead crap the filesystem with filename~ and filename.un~; if people want those, they can (and probably already done so) enable that in their ~/.vimrc. The third leads to not operational primary clipboard selection with mouse, at least in the case "xterm on linux -> ssh to freebsd -> vim", maybe more. The system vimrc should be as unobtrusive as possible. I think if we copy something like this (https://github.com/tpope/vim-sensible), or a subset of it, it will not cause any problems and provide some value. Cheers, \Anton. -- Our society can survive even a large amount of irrational regulation. -- John McCarthy ___ 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"
gnupg-2.1 -> 2.1 appears to break decryption of saved messages
It has been my practice for several years to email sensitive information (such as passwords) to myself via envrypted email, using mutt and GPG. This morning, one of the ports that was updated when I performed my daily refresh of installed ports on my laptop was: Upgrade gnupg-2.0.26_1 to gnupg-2.1.0 Then, a few minutes ago, I tried to retrieve a password from one of my saved encrypted messages... only to be informed "Could not copy message". I (re-)copied ~/.gnupg from my home "desktop"-type machine to my laptop, but that failed to change the behavior. I then used portmaster to switch from security/gnupg to security/gnupg20: portmaster -o security/gnupg20 gnupg-2.1.0 That done, I am now able to retrieve my encrypted messages once again. I don't have time right now to research this, b ut I wanted to let others who might be similarly situated know. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpQd4B2z5ReY.pgp Description: PGP signature
Increase Website Visibility: Chipsquips.Com
Hi Chipsquips.Com Hope you are doing well. I thought you might like to know some of the reasons why you are not getting enough Organic search engine and Social Media traffic for your website. Running and maintaining a website is not easy! With continuously changing digital market and its dynamics, it has become pretty much necessary to follow the right strategy in order to counter recent penguin 3.0 updates from Google and drive in relevant traffic. Well, you might consider this irrelevant but there are various tactics behind on-line marketing strategy and you should be well aware of the main drawbacks. Some of the major factors we keep in mind while promoting your website: 1. Fixing errors that prevents your website from being indexed properly by search engine. 2. Selecting right keywords with our SEO services to promote website. 3. Providing relevant content to create theme based back links. 4. Active and regular updates and posts on social media portals to increase the popularity and brand awareness. 5. Gaining more authority by writing articles and blogs through our SMM & SEM services We offer several services for your website such as Online Reputation Management, Social Media Optimization, SEO activities among others. We have excelled along with our customers because of some key propositions as delivering solution by competent Google Analytics certified professionals and we don't bind our customers with any set up fee or contract, i.e. *(NO CONTRACT or NO SET UP FEE)*. This e-mail provides you with a glimpse of some of the services which we offered from our company. If you have any queries about our services then kindly contact us back for a *free website audit report*. Should you be interested, get in touch with us on the mentioned email address or contact number. Best Regards, Jeff Thomas |DM Consultant PH. No: +1 805-900-0860 Skype: digital.marketinghm -- -- -- 1: This is a onetime email and you may ask us to "UNSUBSCRIBE". 2: If you are interested we will send more details on our "corporate identity", "company profile", "why you should choose us?", "Price list", "money back" etc. in our next mail. P.S: - This is our marketing strategy that we use the Gmail account. Once you reply us back, the next communication will be done from our corporate email ID. ___ 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: ettercap-0.8.0_2,1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm a developer of ettercap. I'm trying to improve the native support of ettercap on FreeBSD. Therefore I try to compile it from source on FreeBSD. However after fixing a number of cmake issues, I've been able to compile the program as normal on FreeBSD. However I've trouble running the program. As soon as threading comes onto the plate, it gets stuck within libthr. Could you help me in get ettercap work from source on FreeBSD. How have you got it work on FreeBSD? Thank you in advance. Regards Alex P.S. Hope that you answer me this time. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlRuheUACgkQS4gT86VyyKqb1gCeOWhKKeWrIwg/+tnWLnrmKo13 tqsAn26Di+x613kQKff32Dl6FNlvC2Ty =43BD -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: ghostscript9-9.06_8
Hi, Sorry to bother you, but I have a question about the ghostscript9 port... We have some issues with imageMagick which has a dependencie to this port and I've been told the problem is due to the old version of ghostscript I am using... >From this release history page: >http://www.ghostscript.com/doc/current/History9.htm#Version9.07 It seem the version 9.06 was released more than 2 years ago and there is no new release in the ports tree since then. Is there a reason (perhaps the license change to AGPL) or a compatibility problem that prevents to go higher than 9.06 ? I don't have the competency to update the port myself but if you need someone to make tests, I'll be more than happy to. Regards ~~ Ian Lord MSD Informatique 143 Rue des Fauvettes St-Colomban (Québec) J5K 0E2 Tél: (514) 776-6734 #201 Sans Frais: 1(877) 776-6734 #201 http://www.msdi.ca/ ___ 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: How to stay with GnuPG 2.0.x (security/gnupg20)
On Thu, Nov 20, 2014 at 9:26 AM, Dr. Peter Voigt wrote: > On Thu, 20 Nov 2014 14:40:21 +0100 > "Dr. Peter Voigt" wrote: > > > I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26: > > > > # pkg version |grep gnupg > > gnupg-2.0.26_1 < > > > > However, GnuPG 2.1 is offered as an update: > > > > # pkg version -vIL= > > gnupg-2.0.26_1 < needs updating (index has > > 2.1.0) > > > > Inspecting the ports tree show that there are two different ports: > > security/gnupg20 and security/gnupg. > > > > How can I stay with security/gnupg20? Portmaster/pkg currently forces > > me to upgrade. Is there a switch in /etc/make.conf? > > > > Regards, > > Peter > > Well, found out that it is obviously a matter of changing a ports > origin: > > # pkg set -o security/gnupg:security/gnupg20 > > Now portmaster/pkg do no longer "force" me to upgrade to version 2.1. > > I hope this is the right way to do, I am still too unexperienced with > ports processing. > > Regards, > Peter > Yes, that is one way to do it. Both portmaster and portupgrade also have a '-o' option that is used similarly. (E.g. portmaster -o security/gnupg20 security/gnupgp) Note the order of the arguments and that the delimiter is a space instead of a ':'. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
