[QAT] 362726: 4x leftovers, 48x success

2014-07-25 Thread Ports-QAT
Clean up databases/rrdtool

Change library dependensies to use USES= where applicable.
Build ports documentation and examples, depending on respective option.
Add two new options, NLS and GRAPH, the GRAPH option enables the rrdtool graph
command, which pulls in cario and a lot of other dependencies.  [1]
Add missing dependencies.
Becase of shlib version bump, bump portrevision on depending ports.

PR: 192024 [1] (based on)
Submitted by:   asomers
Approved by:portmgr (blanket, portrevision bumps)
-

  Build ID:  20140723201200-60592
  Job owner: zeis...@freebsd.org
  Buildtime: 35 hours
  Enddate:   Fri, 25 Jul 2014 07:41:37 GMT

  Revision:  362726
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362726

-

Port:databases/jrrd 1.0.6_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383418/jrrd-1.0.6_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383419/jrrd-1.0.6_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383420/jrrd-1.0.6_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383421/jrrd-1.0.6_2.log

-

Port:databases/pecl-rrd 1.1.3_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383422/pecl-rrd-1.1.3_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383423/pecl-rrd-1.1.3_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383424/pecl-rrd-1.1.3_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383425/pecl-rrd-1.1.3_1.log

-

Port:databases/py-rrdtool_lgpl 1.0b1_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383426/py27-rrdtool_lgpl-1.0b1_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383427/py27-rrdtool_lgpl-1.0b1_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383428/py27-rrdtool_lgpl-1.0b1_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383429/py27-rrdtool_lgpl-1.0b1_4.log

-

Port:databases/rrdtool 1.4.8_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383430/rrdtool-1.4.8_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383431/rrdtool-1.4.8_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383432/rrdtool-1.4.8_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383433/rrdtool-1.4.8_2.log

-

Port:net-mgmt/collectd 4.10.9_10

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383434/collectd-4.10.9_10.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383435/collectd-4.10.9_10.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383436/collectd-4.10.9_10.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~zeis...@freebsd.org/20140723201200-60592-383437/collectd-4.10.9_10.log

---

"pkg upgrade" without using INDEX (pkg-1.3)

2014-07-25 Thread Beeblebrox
pkg-1.3 apparently uses INDEX to speed things along. I can't use INDEX and
need a way to do "pkg upgrade" the old way because:

I merge gnome3 and linux_c6 branches into the ports tree. The latest
linux_c6 merge breaks "make index" at emulators/linux-systemsimcell (PR
filed). As a result, "fethcindex" is not going to work for me since it won't
have a listing of the merged ports. So now the oddities that I face,

* Upgraded to pkg-1.3, then I had a number of very weird problems by pkg. I
then ran "portmaster -a", which did an upgrade for 2 ports: vo-aacenc and
vo-amrwbenc. After this pkg started behaving a little more sanely
(mentioning this, in case anyone else runs into similar problem)

* when starting portmaster, I get below message before it decides to
continue with the process anyway (repeats 3 times): "pkg: Cannot get a read
lock on a database, it is locked by another process"

* I have no INDEX in the ports tree, so "pkg version -PoL=" shows that pkg
is greatly confused by a number of ports. For example:
games/gnome-mahjongg   ?
deskutils/gnome-maps   ?
net/gnome-online-accounts  ?
deskutils/gnome-photos ?
games/gnome-robots ?
deskutils/gnome-screenshot ?
deskutils/gnome-search-tool?
x11/gnome-shell-extensions ?
games/gnome-sudoku ?
deskutils/gnome-system-log ?
x11-themes/gnome-themes-standard   ?
deskutils/gnome-tweak-tool ?
graphics/gnome-video-effects   ?
security/gnomint   <
security/gnutls<

* For the ports that pkg is *not* confused about, (the last two ports above
with "<" for example), my local poudriere build repo is now being ignored by
pkg and "pkg upgrade -r myrepo" completes with a not-so-reassuring "Your
packages are up to date" message. YEt as seen above, the version output says
otherwise.

* From another thread/post: "If you want the old behavior either delete the
INDEX file or use the -P flag" No INDEX as stated, and P not an option for
upgrade.

* I did a fresh merge of branches/trees and the problem persists.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/pkg-upgrade-without-using-INDEX-pkg-1-3-tp5931637.html
Sent from the freebsd-ports mailing list archive at Nabble.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: "pkg upgrade" without using INDEX (pkg-1.3)

2014-07-25 Thread Baptiste Daroussin
On Fri, Jul 25, 2014 at 02:09:58AM -0700, Beeblebrox wrote:
> pkg-1.3 apparently uses INDEX to speed things along. I can't use INDEX and
> need a way to do "pkg upgrade" the old way because:
> 
> I merge gnome3 and linux_c6 branches into the ports tree. The latest
> linux_c6 merge breaks "make index" at emulators/linux-systemsimcell (PR
> filed). As a result, "fethcindex" is not going to work for me since it won't
> have a listing of the merged ports. So now the oddities that I face,
> 
> * Upgraded to pkg-1.3, then I had a number of very weird problems by pkg. I
> then ran "portmaster -a", which did an upgrade for 2 ports: vo-aacenc and
> vo-amrwbenc. After this pkg started behaving a little more sanely
> (mentioning this, in case anyone else runs into similar problem)
> 
> * when starting portmaster, I get below message before it decides to
> continue with the process anyway (repeats 3 times): "pkg: Cannot get a read
> lock on a database, it is locked by another process"
> 
> * I have no INDEX in the ports tree, so "pkg version -PoL=" shows that pkg
> is greatly confused by a number of ports. For example:
> games/gnome-mahjongg   ?
> deskutils/gnome-maps   ?
> net/gnome-online-accounts  ?
> deskutils/gnome-photos ?
> games/gnome-robots ?
> deskutils/gnome-screenshot ?
> deskutils/gnome-search-tool?
> x11/gnome-shell-extensions ?
> games/gnome-sudoku ?
> deskutils/gnome-system-log ?
> x11-themes/gnome-themes-standard   ?
> deskutils/gnome-tweak-tool ?
> graphics/gnome-video-effects   ?
> security/gnomint   <
> security/gnutls<
> 
> * For the ports that pkg is *not* confused about, (the last two ports above
> with "<" for example), my local poudriere build repo is now being ignored by
> pkg and "pkg upgrade -r myrepo" completes with a not-so-reassuring "Your
> packages are up to date" message. YEt as seen above, the version output says
> otherwise.
> 
> * From another thread/post: "If you want the old behavior either delete the
> INDEX file or use the -P flag" No INDEX as stated, and P not an option for
> upgrade.
> 
> * I did a fresh merge of branches/trees and the problem persists.
> 
> 
> 
I do not understand what you do ask for.
Right now pkg version first rely on INDEX if index is not there then it query
ports by ports.

regards,
Bapt


pgpsfsWne5BQp.pgp
Description: PGP signature


Re: "pkg upgrade" without using INDEX (pkg-1.3)

2014-07-25 Thread Beeblebrox
Hi Bapt,

The problem was that "pkg upgrade -r myrepo" did nothing. The rest of the
information was provided as supporting evidence.

It turns out, the poudriere repo was not being updated after the poudriere
run. A verbose run of poudriere showed this message:
"pkg package missing, skipping sanity"
I deleted pkg-1.3.0.txz from the repo, and re-ran poudriere for
ports-mgmt/pkg only. The problem cleared up and the poudriere repo was
updated correctly at the end of the run.
[SOLVED]

Thanks.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/pkg-upgrade-without-using-INDEX-pkg-1-3-tp5931637p5931661.html
Sent from the freebsd-ports mailing list archive at Nabble.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: tex-formats fails build (package stage) - teXlive issue

2014-07-25 Thread Michelle Sullivan
Fixed by setting TEX_DEFAULT=tetex in make.conf  (removing everything
tex related in build list did not help - it's a dependency of something
else which is a dependency of something I need - probably
cups-image->cups-client (which I don't need either, but something I do
need requires cups-client...) ...!)

Michelle

Michelle Sullivan wrote:
> ===
> ===
> ===>  Building package for tex-formats-20120701_2
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/amstex.log
> /usr/local/share/texmf-var/web2c/pdftex/amstex.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/cont-en.log
> /usr/local/share/texmf-var/web2c/pdftex/cont-en.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/cslatex.log
> /usr/local/share/texmf-var/web2c/pdftex/cslatex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/pdfcslatex.log
> /usr/local/share/texmf-var/web2c/pdftex/pdfcslatex.fmt' (package tools
> out of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/eplain.log
> /usr/local/share/texmf-var/web2c/pdftex/eplain.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/latex.log
> /usr/local/share/texmf-var/web2c/pdftex/latex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/pdflatex.log
> /usr/local/share/texmf-var/web2c/pdftex/pdflatex.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/metafont/mf.log
> /usr/local/share/texmf-var/web2c/metafont/mf.base' (package tools out of
> date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/mex.log
> /usr/local/share/texmf-var/web2c/pdftex/mex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/pdfmex.log
> /usr/local/share/texmf-var/web2c/pdftex/pdfmex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/utf8mex.log
> /usr/local/share/texmf-var/web2c/pdftex/utf8mex.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/mllatex.log
> /usr/local/share/texmf-var/web2c/pdftex/mllatex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/mltex.log
> /usr/local/share/texmf-var/web2c/pdftex/mltex.fmt' (package tools out of
> date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/mptopdf.log
> /usr/local/share/texmf-var/web2c/pdftex/mptopdf.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/pdftex.log
> /usr/local/share/texmf-var/web2c/pdftex/pdftex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/etex.log
> /usr/local/share/texmf-var/web2c/pdftex/etex.fmt
> /usr/local/share/texmf-var/web2c/pdftex/pdfetex.log
> /usr/local/share/texmf-var/web2c/pdftex/pdfetex.fmt' (package tools out
> of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/tex/tex.log
> /usr/local/share/texmf-var/web2c/tex/tex.fmt' (package tools out of date?)
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/texsis.log
> /usr/local/share/texmf-var/web2c/pdftex/texsis.fmt' (package tools out
> of date?)
> pkg_create: write_plist: unknown command type -1
> (/usr/local/share/texmf-var/web2c/pdftex/amstex.log
> /usr/local/share/texmf-var/web2c/pdftex/amstex.fmt)
> Creating package
> /wrkdirs/usr/ports/print/tex-formats/work/pkg/tex-formats-20120701_2.tbz
> Registering depends: texlive-texmf-20120701_4 texlive-base-20120701_11
> libXaw-1.0.12_2,2 libXp-1.0.2_2,1 libXmu-1.1.2_2,1 libgd-2.1.0_4,1
> libXpm-3.5.11_2 libXext-1.3.2_2,1 libXt-1.1.4_2,1 poppler-0.24.5_4
> cairo-1.10.2_10,2 libXrender-0.9.8_2 libX11-1.6.2_2,1
> xcb-util-renderutil-0.3.9 xcb-util-0.3.9_3,1 libxcb-1.10_2
> libxml2-2.9.1_1 ghostscript9-nox11-9.06_7 cups-image-1.7.3
> cups-client-1.7.3_1 libidn-1.28_1 silgraphite-2.3.1_2 libiconv-1.14_3
> perl5-5.16.3_11 gdbm-1.11_2 icu-53.1 libpthread-stubs-0.3_5
> t1lib-5.1.2_2,1 tex-web2c-20120701_3 tex-ptexenc-1.3.0_1
> tex-kpathsea-6.1.0_2 zziplib-0.13.62_1 jbig2dec-0.11_2 openjpeg15-1.5.2
> lcms2-2.6_3 tiff-4.0.3_4 jbigkit-2.1_1 jpeg-8_5 fontconfig-2.11.0_3,1
> freetype2-2.5.3_2 png-1.5.18 poppler-data-0.4.6 svgalib-1.4.3_7
> freetype-1.3.1_4 gsfonts-8.11_6 indexinfo-0.2 psutils-1.17_4
> libpaper-1.1.24_2 teckit-2.5.1_1 expat-2.1.0_1 kbproto-1.0.6
> libSM-1.2.2_2,1 libICE-1.0.9,1 libXau-1.0.8_2 libXdmcp-1.1.1_2
> pixman-0.32.4_3 printproto-1.0.5 renderproto-0.11.1 xextproto-7.3.0
> xproto-7.0.26.
> Registering conflicts: teTeX-[0-9]* *-teTeX-[0-9]* teTeX-*-[0-9]*
> *-teTeX-*-[0-9]* latex2e-[0-9]*.
> *** [do-package] Error code

Re: tex-format fails build (package)

2014-07-25 Thread Matthew D. Fuller
On Thu, Jul 24, 2014 at 10:19:55PM +0200 I heard the voice of
Michelle Sullivan, and lo! it spake thus:
>
> pkg_create: read_plist: unknown command '@fmtutil
> /usr/local/share/texmf-var/web2c/pdftex/amstex.log
> /usr/local/share/texmf-var/web2c/pdftex/amstex.fmt' (package tools out
> of date?)

This would seem to be the key point...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Matthew D. Fuller wrote:
> On Thu, Jul 24, 2014 at 10:19:55PM +0200 I heard the voice of
> Michelle Sullivan, and lo! it spake thus:
>   
>> pkg_create: read_plist: unknown command '@fmtutil
>> /usr/local/share/texmf-var/web2c/pdftex/amstex.log
>> /usr/local/share/texmf-var/web2c/pdftex/amstex.fmt' (package tools out
>> of date?)
>> 
>
> This would seem to be the key point...
>
>
>   
If that were true then everyone should switch to pkgng now.. the problem
is fmtutil and fmtutil-sys does not exist on my system and appears to be
included only in tetex not texlive .. it appears there used to be a port
for it, but it is no more (merged into tetex?)

.. you might want to check my other post, TEX_DEFAULT=tetex in make.conf
fixes it...  all my build servers (which auto-update both the jails and
ports trees) failed for the last 24-48 hours because of this... putting
in the TEX_DEFAULT at 5am today all the failed build lights have gone
out...  still got to build 9.3 amd64 & i386 as well as 10 on both archs
for both PKGNG and non PKGNG... but it is looking good so far.

Michelle


-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Kurt Jaeger
Hi!

> If that were true then everyone should switch to pkgng now..

Well, I've tested it and, yes, everyone should switch 8-)

> the problem
> is fmtutil and fmtutil-sys does not exist on my system and appears to be
> included only in tetex not texlive .. it appears there used to be a port
> for it, but it is no more (merged into tetex?)

/usr/local/bin/fmtutil was installed by package texlive-base-20120701_11

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Kurt Jaeger wrote:
> Hi!
>
>   
>> If that were true then everyone should switch to pkgng now..
>> 
>
> Well, I've tested it and, yes, everyone should switch 8-)
>
>   
>> the problem
>> is fmtutil and fmtutil-sys does not exist on my system and appears to be
>> included only in tetex not texlive .. it appears there used to be a port
>> for it, but it is no more (merged into tetex?)
>> 
>
> /usr/local/bin/fmtutil was installed by package texlive-base-20120701_11
>
>   
I wonder whether no options for texlive does not add -base ?  I might
try removing it and explicitly adding texlive (-base) to the build list
and see if that fixes it (will let everything build successfully first.)

Michelle

-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Michelle Sullivan wrote:
> Kurt Jaeger wrote:
>   
>> Hi!
>>
>>   
>> 
>>> If that were true then everyone should switch to pkgng now..
>>> 
>>>   
>> Well, I've tested it and, yes, everyone should switch 8-)
>>
>>   
>> 
>>> the problem
>>> is fmtutil and fmtutil-sys does not exist on my system and appears to be
>>> included only in tetex not texlive .. it appears there used to be a port
>>> for it, but it is no more (merged into tetex?)
>>> 
>>>   
>> /usr/local/bin/fmtutil was installed by package texlive-base-20120701_11
>>
>>   
>> 
> I wonder whether no options for texlive does not add -base ?  I might
> try removing it and explicitly adding texlive (-base) to the build list
> and see if that fixes it (will let everything build successfully first.)
>
> Michelle
>
>   
Ahh - base is a complete package... I wonder if tex-formats (or
something it depends on) is not installing texlive-base - build logs
show it was built...

-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Kurt Jaeger
Hi!

> Ahh - base is a complete package... I wonder if tex-formats (or
> something it depends on) is not installing texlive-base - build logs
> show it was built...

Well, in all the pkg-1.3/exim/tetex->texlive etc uproar, I lost
track and I just re-build what needs to be re-build 8-}

It's a bit much all at once 8-}

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
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: tex-format fails build (package)

2014-07-25 Thread Matthew D. Fuller
On Fri, Jul 25, 2014 at 01:30:48PM +0200 I heard the voice of
Michelle Sullivan, and lo! it spake thus:
>
> If that were true then everyone should switch to pkgng now.. the
> problem is fmtutil and fmtutil-sys does not exist on my system and
> appears to be included only in tetex not texlive .. it appears there
> used to be a port for it, but it is no more (merged into tetex?)
>
> .. you might want to check my other post, TEX_DEFAULT=tetex in
> make.conf fixes it...

No, this doesn't have anything to do with 'fmtutil' the-command; this
is '@fmtutil' the-plist-directive, which is in print/tex-formats's
plist (via indirect logic down in bsd.tex.mk).  Since that doesn't get
built with TeTex, of course it doesn't error in that case.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Matthew D. Fuller wrote:
> On Fri, Jul 25, 2014 at 01:30:48PM +0200 I heard the voice of
> Michelle Sullivan, and lo! it spake thus:
>   
>> If that were true then everyone should switch to pkgng now.. the
>> problem is fmtutil and fmtutil-sys does not exist on my system and
>> appears to be included only in tetex not texlive .. it appears there
>> used to be a port for it, but it is no more (merged into tetex?)
>>
>> .. you might want to check my other post, TEX_DEFAULT=tetex in
>> make.conf fixes it...
>> 
>
> No, this doesn't have anything to do with 'fmtutil' the-command; this
> is '@fmtutil' the-plist-directive, which is in print/tex-formats's
> plist (via indirect logic down in bsd.tex.mk).  Since that doesn't get
> built with TeTex, of course it doesn't error in that case.
>
>
>   
So where's the error - the build is fine, I have the latest ports tree,
staging is fine, it's just using texlive that breaks my build runs on
all platforms on all arches...  I've even tried deleting/creating the
ports tree and running -C -c for all packages... (poudriere)..? (surely
your not suggesting pkg_create is the problem across everything? (before
EOL))

Michelle

-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Matthew D. Fuller
On Fri, Jul 25, 2014 at 02:07:10PM +0200 I heard the voice of
Michelle Sullivan, and lo! it spake thus:
>
> So where's the error

That pkg_create doesn't know what to do with the @fmtutil in the
plist.

Whether that devolves to "you shouldn't still be using pkg_*", or
"@fmtutil wasn't setup quite right on pkg_* and you're just the first
to notice", or "@fmtutil was never intended to work in pkg_* and a gun
was jumped", I express no opinion   :)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Matthew D. Fuller wrote:
> On Fri, Jul 25, 2014 at 02:07:10PM +0200 I heard the voice of
> Michelle Sullivan, and lo! it spake thus:
>   
>> So where's the error
>> 
>
> That pkg_create doesn't know what to do with the @fmtutil in the
> plist.
>
> Whether that devolves to "you shouldn't still be using pkg_*", or
> "@fmtutil wasn't setup quite right on pkg_* and you're just the first
> to notice", or "@fmtutil was never intended to work in pkg_* and a gun
> was jumped", I express no opinion   :)
>
>
>   
Thanks, at least eyes are on it...  It does seem that most of my
problems over the last 2 months with packages have been 'broken'
updates/changes.. would be nice to get a week of "build ok" reports so I
could actually get some real work done.

-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Matthew D. Fuller
On Fri, Jul 25, 2014 at 02:15:09PM +0200 I heard the voice of
Michelle Sullivan, and lo! it spake thus:
>
> Thanks, at least eyes are on it...

Well, _my_ eyes can't really do anything about it   :)

I think bapt@ has been the one doing most of the TeXery, so he'd
probably be the one to talk to about it.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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/firefox vs. vulnerabilities vs. libevent --> libevent2

2014-07-25 Thread David Wolfskill
/usr/ports is a working copy of head@r362876; during my daily portmaster
run to update all installed ports on my laptop, I see that libevent1 is
now replaced by libevent2.

Apparently www/firefox had been linked against libevent, so portmaster
tries to update www/firefox (after having updated several other ports).

That process terminates rather abrutly, however:

===>>> All >> firefox-30.0_1,1 (12/15)
0;portmaster: All >> firefox-30.0_1,1 (12/15)^G
===>  Cleaning for firefox-30.0_2,1
===>  firefox-30.0_2,1 has known vulnerabilities:
firefox-30.0_2,1 is vulnerable:
mozilla -- multiple vulnerabilities
CVE: CVE-2014-1561
CVE: CVE-2014-1560
CVE: CVE-2014-1559
CVE: CVE-2014-1558
CVE: CVE-2014-1557
CVE: CVE-2014-1556
CVE: CVE-2014-1555
CVE: CVE-2014-1552
CVE: CVE-2014-1551
CVE: CVE-2014-1550
CVE: CVE-2014-1549
CVE: CVE-2014-1548
CVE: CVE-2014-1547
CVE: CVE-2014-1544
WWW: http://portaudit.FreeBSD.org/978b0f76-122d-11e4-afe3-bc5ff4fb5e7b.html

1 problem(s) in the installed packages found.
=> Please update your ports tree and try again.
=> Note: Vulnerable ports are marked as such even if there is no update 
available.
=> If you wish to ignore this vulnerability rebuild with 'make 
DISABLE_VULNERABILITIES=yes'
*** [check-vulnerable] Error code 1

Stop in /common/ports/www/firefox.
*** [build] Error code 1

Stop in /common/ports/www/firefox.

===>>> make build failed for www/firefox
===>>> Aborting update


As a reality check, I did take a quick look at
 to see
if, perchance, there were commits to www/firefox to address those
reported vulnerabilities since r362876, but the most recent commit
I see there now is r362887 -- and none of the commits since r362876
is about/for www/firefox (or anything related, AFAICT).

So I'm left wondering how this is actually useful: I'm left with a copy
of firefox installed (more or less) that has known vulnerabilities and
is broken (since it's still linked against a library that no longer
exists).  At least I was able to use a copy of firefox on a machine I
haven't started to upgrade yet (so I could refer to the cited Web
page(s)).

Since I'm disinclined to globally disable all vulnerability checking,
I'm proceeding with updates to the ports that portmaster hadn't yet got
to first, before (temporarily) disabling the checks so I can have a
working graphical Web browser with which I'm familiar again.

Which reminds me: the cited directive re. the libevent change (in
UPDATING): "pkg delete libevent" also deleted sysutils/tmux, so the
subsequent "portmaster -ad" had no clue that tmux was supposed to be
rebuilt.  I was able to re-install it manually, but I mention this in
case it helps someone else.

(Ugh.  It appears that the "portmaster -aF" that I ran earlier this
morning didn't actually fetch the firefox-30.0.source.tar.bz2... wait
up; that should have been there already.  Making me wait while that's
re-fetched is ... not good: I'm trying to get this laptop updated before
I go in to work this morning  OK; I found a local copy on another
machine.)

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.


pgp32Bp0lXhqQ.pgp
Description: PGP signature


pkg-1.3 comment and questions

2014-07-25 Thread Richard Kuhns
Hello,

First the comment: I've also noticed that checking for out-of-date
packages now takes 3 to 5 times longer than it used to. I've never used
an INDEX before, as it didn't seem to offer me anything I needed/wanted.
Is it considered (almost) a requirement now?

Second, how do I delete a single package that has dependencies without
deleting the dependencies? For example, UPDATING says

libevent1 has been replaced by libevent2 via the compatibility layer.
  All applications that used libevent1 must be rebuilt.

  Please remove libevent1 before upgrading, by running:
pkg delete libevent

If I try 'pkg delete libevent', pkg wants to delete no only libevent but
every other package that requires libevent. It's as if the recursive
flag is now on by default and I can't find any way to turn it off. 'pkg
help delete' doesn't offer anything.

I don't have a pkg.conf file installed anywhere (that I can find, anyway).

Thanks,
-- 
Richard Kuhns  Main Number:  765-742-8428
Wintek Corporation Direct:   765-269-8541
427 N 6th Street   Internet Support: 765-269-8503
Lafayette, IN 47901-2211   Consulting:   765-269-8504
___
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: tex-format fails build (package)

2014-07-25 Thread Michelle Sullivan
Matthew D. Fuller wrote:
> On Fri, Jul 25, 2014 at 02:15:09PM +0200 I heard the voice of
> Michelle Sullivan, and lo! it spake thus:
>   
>> Thanks, at least eyes are on it...
>> 
>
> Well, _my_ eyes can't really do anything about it   :)
>   
:)
> I think bapt@ has been the one doing most of the TeXery, so he'd
> probably be the one to talk to about it.
>
>
>   
Here's the log in any case (for 8.4 because the others are not uploaded
yet):

http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-07-24_15h22m40s/logs/errors/tex-formats-20120701_2.log

-- 
Michelle Sullivan
http://www.mhix.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: tex-format fails build (package)

2014-07-25 Thread Baptiste Daroussin
On Fri, Jul 25, 2014 at 03:32:14PM +0200, Michelle Sullivan wrote:
> Matthew D. Fuller wrote:
> > On Fri, Jul 25, 2014 at 02:15:09PM +0200 I heard the voice of
> > Michelle Sullivan, and lo! it spake thus:
> >   
> >> Thanks, at least eyes are on it...
> >> 
> >
> > Well, _my_ eyes can't really do anything about it   :)
> >   
> :)
> > I think bapt@ has been the one doing most of the TeXery, so he'd
> > probably be the one to talk to about it.
> >
> >
> >   
> Here's the log in any case (for 8.4 because the others are not uploaded
> yet):
> 
> http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-07-24_15h22m40s/logs/errors/tex-formats-20120701_2.log
> 

Yes the code for supporting pkg_* as been forgotten I'll added it as soon as
possible

regards,
Bapt


pgpbRwpK1nVyv.pgp
Description: PGP signature


Merging several branches with ports tree

2014-07-25 Thread Beeblebrox
I have several ports branches that get merged to the ports tree. The
structure is such that a pristine (un-merged) copy of each branch is located
under: /asp/git/ports, /asp/git/marcuscom, /asp/git/linux-c6, /asp/git/my-pc

I then want to copy all files under each branch to /usr/ports using a
combination of rsync and the marcusmerge script. The steps I wish to run:
1. rsync -uav --exclude=.git /asp/git/ports/ /usr/ports/
2. marcusmerge (works, no problem)
3. rsync -av --exclude=.git/ /asp/git/linux-c6/ /usr/ports/ (works, no
problem)
4. rsync -av /asp/git/my-pc/ /usr/ports/

Steps #1 and #4 are the problem.
* a simple "rsync -a OR -ua" in step 1 does not seem to work when rsyncing
onto a merged structure and causes problems. What can I use here, so as to
ensure updates to the primary port tree get written to the combined folder
(/usr/ports)?
* my-pc is a self maintained my ports collection. It has one folder with my
collection in it, but the problem is that the top-level Makefile and
Mk/bsd.port.mk "VALID_CATEGORIES" must be modified to include the myports
collection. How can I merge this set to /usr/ports?




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Merging-several-branches-with-ports-tree-tp5931719.html
Sent from the freebsd-ports mailing list archive at Nabble.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: Lots of installed ports show "succeeds index"

2014-07-25 Thread Christian Weisgerber
On 2014-07-24, Kevin Oberman  wrote:

>> > Is there a reason you want to avoid using the index? It's worked just
>> fine
>> > for me for several months on systems with well over 1000 ports installed.
>>
>> It isn't in sync with my ports tree
>
> Which begs the question, why is it out of sync? If you update your ports
> tree, all you need to do is:
> make -C /usr/ports fetchindex (takes a few seconds)

Which fetches an INDEX file that is regularly generated on some
FreeBSD server, but is not in sync with the exact revision of the
ports tree I just updated to.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
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"


[QAT] 362806: 4x ignored: needs an existing installation of perl built with with_threads=yes, 1x depend (??? in graphics/netpbm), 129x success, 1x depend (makefile in x11-toolkits/gnustep-gui), 4x ign

2014-07-25 Thread Ports-QAT
Reset maintainership for ports not staged with no pending PR

With hat:   portmgr
-

  Build ID:  20140724153801-18880
  Job owner: b...@freebsd.org
  Buildtime: 25 hours
  Enddate:   Fri, 25 Jul 2014 16:49:54 GMT

  Revision:  362806
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362806

-

Port:misc/amanda-server 3.3.2_1,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383842/amanda-server-3.3.2_1,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383843/amanda-server-3.3.2_1,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383844/amanda-server-3.3.2_1,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383845/amanda-server-3.3.2_1,1.log

-

Port:misc/amanda25-server 2.5.1p3_7,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383846/amanda25-server-2.5.1p3_7,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383847/amanda25-server-2.5.1p3_7,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383848/amanda25-server-2.5.1p3_7,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383849/amanda25-server-2.5.1p3_7,1.log

-

Port:misc/amanda26-server 2.6.1p2_5,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383850/amanda26-server-2.6.1p2_5,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383851/amanda26-server-2.6.1p2_5,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383852/amanda26-server-2.6.1p2_5,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383853/amanda26-server-2.6.1p2_5,1.log

-

Port:misc/amanda32-server 3.2.3_1,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383854/amanda32-server-3.2.3_1,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383855/amanda32-server-3.2.3_1,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383856/amanda32-server-3.2.3_1,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383857/amanda32-server-3.2.3_1,1.log

-

Port:misc/c-hey 2.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383858/c-hey-2.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383859/c-hey-2.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   IGNORED: IS MARKED AS BROKEN: FAILS TO BUILD WITH NEW UTMPX

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   IGNORED: IS MARKED AS BROKEN: FAILS TO BUILD WITH NEW UTMPX

-

Port:misc/color-theme.el 6.6.0_12

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383862/color-theme.el-emacs-6.6.0_12.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140724153801-18880-383863/color-theme.el-emacs-6.6.0_12.log

  Buildgroup: 9.2-QAT

[QAT] 362809: 4x leftovers

2014-07-25 Thread Ports-QAT
This port was not stage-safe as it was making direct writes to /var. Fix that,
along with making do-install substantially easier to read. While here, stop
muting the build command.
-

  Build ID:  20140724155000-19214
  Job owner: ad...@freebsd.org
  Buildtime: 25 hours
  Enddate:   Fri, 25 Jul 2014 16:50:38 GMT

  Revision:  362809
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362809

-

Port:games/greed 3.10

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140724155000-19214-384014/greed-game-3.10.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140724155000-19214-384015/greed-game-3.10.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140724155000-19214-384016/greed-game-3.10.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140724155000-19214-384017/greed-game-3.10.log


--
Buildarchive URL: 
redports 
___
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"


[QAT] 362817: 4x leftovers, 20x success

2014-07-25 Thread Ports-QAT
- Switch devel/hwloc to USES=libtool, drop .la files
- Bump dependent ports as .so version has changed
- Add LICENSE_FILE
- While here, fix stagedir reference in www/trafficserver

Approved by:portmgr blanket
-

  Build ID:  20140724161001-61844
  Job owner: amd...@freebsd.org
  Buildtime: 26 hours
  Enddate:   Fri, 25 Jul 2014 17:48:43 GMT

  Revision:  362817
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362817

-

Port:devel/hwloc 1.9_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384042/hwloc-1.9_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384043/hwloc-1.9_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384044/hwloc-1.9_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384045/hwloc-1.9_1.log

-

Port:net/mpich 3.1.1_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384046/mpich-3.1.1_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384047/mpich-3.1.1_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384048/mpich-3.1.1_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384049/mpich-3.1.1_1.log

-

Port:net/openmpi 1.8.1_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384050/openmpi-1.8.1_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384051/openmpi-1.8.1_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384052/openmpi-1.8.1_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384053/openmpi-1.8.1_2.log

-

Port:net/openmpi-devel 1.7.5_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384054/openmpi-devel-1.7.5_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384055/openmpi-devel-1.7.5_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384056/openmpi-devel-1.7.5_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384057/openmpi-devel-1.7.5_2.log

-

Port:sysutils/slurm-hpc 2.6.4_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384058/slurm-hpc-2.6.4_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384059/slurm-hpc-2.6.4_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384060/slurm-hpc-2.6.4_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384061/slurm-hpc-2.6.4_4.log

-

Port:www/trafficserver 4.1.2_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140724161001-61844-384062/trafficserver-4.1.2_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.or

Re: pkg-1.3 comment and questions

2014-07-25 Thread Lars Engels
On Fri, Jul 25, 2014 at 08:57:00AM -0400, Richard Kuhns wrote:
> Hello,
> 
> First the comment: I've also noticed that checking for out-of-date
> packages now takes 3 to 5 times longer than it used to. I've never used
> an INDEX before, as it didn't seem to offer me anything I needed/wanted.
> Is it considered (almost) a requirement now?
> 
> Second, how do I delete a single package that has dependencies without
> deleting the dependencies? For example, UPDATING says
> 
> libevent1 has been replaced by libevent2 via the compatibility layer.
>   All applications that used libevent1 must be rebuilt.
> 
>   Please remove libevent1 before upgrading, by running:
> pkg delete libevent
> 
> If I try 'pkg delete libevent', pkg wants to delete no only libevent but
> every other package that requires libevent. It's as if the recursive
> flag is now on by default and I can't find any way to turn it off. 'pkg
> help delete' doesn't offer anything.
> 
> I don't have a pkg.conf file installed anywhere (that I can find, anyway).
> 

pkg delete -f libevent

will only delete the libevent package.


pgpsZlPyrDWWl.pgp
Description: PGP signature


Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-25 Thread Craig Rodrigues
On Thu, Jul 17, 2014 at 11:25 AM, Craig Rodrigues 
wrote:

>
> For (2), encouraging people to move away from Linux to FreeBSD
> on the server, may be something where we can get more wins.
> I think we can do this by having more HOWTO articles on
> the FreeBSD web page that explain the following:
>
>
> (1)  We need a HOWTO article that explains for each command using apt
> or yum for installing packages,
>   how can I do the same thing using "pkg".
>   Even if we have a web page with a table, contrasting the
>   apt/yum commands, and pkg commands, that would be super
>   useful.
>
>   A lot of folks have moved away from FreeBSD, purely because
>   they are sick of pkg_add.  We need to explain to folks that
>   we have something better, that is quite competitive to
>   apt/yum, and it is easy to use.
>
>  (2)  We need a HOWTO article that explains how to set up
>a FreeBSD environment with some of the major cloud providers,
>i.e. Amazon, Rackspace, Microsoft Azure, etc.
>
>
>
>

Hi,

While I appreciate the enthusiasm of the responses to this
e-mail thread, especially the patches to service(8), I feel that my
original e-mail was hijacked into the weeds,
and none of the questions that I asked were answered. :)

So, I am assuming that no one is working on the HOWTO's that I mentioned
in my original e-mail. :)

In the latest edition of BSDNow (
http://www.bsdnow.tv/episodes/2014_07_23-des_challenge_iv ), they refer to
a blog article where someone who was used to Linux posted their experience
setting up FreeBSD:

http://thiagoperrotta.wordpress.com/2014/07/20/here-be-dragons-freebsd-overview-part-i/
http://thiagoperrotta.wordpress.com/2014/07/21/here-be-packages-freebsd-overview-part-ii/

The Part II article goes in-depth into installing packages, and the user
had a positive experience with using pkg, which is great.

What I'd like to see is an article on freebsd.org either on the wiki
or in the handbook, which compares using apt, yum, rpm, whatever
to pkg.  Is anyone interested in working on an article like this?
I don't have the bandwidth right now.

--
Craig
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Merging several branches with ports tree

2014-07-25 Thread Beeblebrox
Andrzej Tobola wrote:

> I do not understand exactly ...
> but from a few years  I am using unionfs to place my mods of ports
> tree over the original:
>
>   /ftp/pub/BSD/FreeBSD/GIT/ports2,1T1,6T553G
> 74%/usr/ports :/usr/local/ports  2,2T2,2T
> 18G99%/usr/ports
> 
>   % mount | grep ports
>   /ftp/pub/BSD/FreeBSD/GIT/ports on /usr/ports (nullfs, read-only)
>   :/usr/local/ports on /usr/ports (unionfs, read-only)

That's an interesting approach and nice idea.
My aim is to have a separate category for the modded ports, because
a) They're mostly not in the tree anyway and,
b) I need a way to keep track of modded ports for update failure.

In case there are others who find my explanation a bit incomprehensible:
* I download each repo/tree (git/svn) into its own folder.
* I then want to overlay each tree into /usr/ports, starting with ports,
gnome3, linux-c6 and finally my-port-collection
* When I update base ports tree, and try to place the latest overlay into
/usr/ports, the "rsync -au" command results in a ports tree with unforseen
errors. I need to correct this.
* I prefer to have my ports collection under a separate category and I need
to correct the script that injects categories into /usr/ports/Makefile &
Mk/bsd.ports.mk. Sending the folder for sub-category is of course trivial
with rsync.

Thanks for the idea!



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Merging-several-branches-with-ports-tree-tp5931719p5931780.html
Sent from the freebsd-ports mailing list archive at Nabble.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: Merging several branches with ports tree

2014-07-25 Thread olli hauer
On 2014-07-25 16:13, Beeblebrox wrote:
> I have several ports branches that get merged to the ports tree. The
> structure is such that a pristine (un-merged) copy of each branch is located
> under: /asp/git/ports, /asp/git/marcuscom, /asp/git/linux-c6, /asp/git/my-pc
> 
> I then want to copy all files under each branch to /usr/ports using a
> combination of rsync and the marcusmerge script. The steps I wish to run:
> 1. rsync -uav --exclude=.git /asp/git/ports/ /usr/ports/
> 2. marcusmerge (works, no problem)
> 3. rsync -av --exclude=.git/ /asp/git/linux-c6/ /usr/ports/ (works, no
> problem)
> 4. rsync -av /asp/git/my-pc/ /usr/ports/
> 
> Steps #1 and #4 are the problem.
> * a simple "rsync -a OR -ua" in step 1 does not seem to work when rsyncing
> onto a merged structure and causes problems. What can I use here, so as to
> ensure updates to the primary port tree get written to the combined folder
> (/usr/ports)?
> * my-pc is a self maintained my ports collection. It has one folder with my
> collection in it, but the problem is that the top-level Makefile and
> Mk/bsd.port.mk "VALID_CATEGORIES" must be modified to include the myports
> collection. How can I merge this set to /usr/ports?
> 
> 

Perhaps ports-mgmt/portshaker is a possible tool.

With the line in make.conf there is no need to patch bsd.port.mk for own $CAT
  VALID_CATEGORIES+=foo bar

Use .sinclude instead .include for own Makefile extensions, then there is no 
issue in case the file is missing.

-- 
olli
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-25 Thread Warren Block

On Fri, 25 Jul 2014, Craig Rodrigues wrote:


What I'd like to see is an article on freebsd.org either on the wiki
or in the handbook, which compares using apt, yum, rpm, whatever
to pkg.  Is anyone interested in working on an article like this?
I don't have the bandwidth right now.


A person to write that article needs detailed knowledge of pkg and the 
Linux package systems.  I don't have that, but would be willing to help 
you develop an outline for the article.  Having a design like that makes 
it easier to write when time and resources are available.


Writing "an article" is hard.  Writing a small section on how deleting 
packages is different between pkg and, say, apt, is much easier.  The 
scope is known.

___
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"


[QAT] 362884: 8x leftovers, 32x success

2014-07-25 Thread Ports-QAT
- Convert texproc/uim and friends to USES=libtool, drop .la files
- Bump ports dependent on uim as some .so versions have changed
- While here, convert some USE_BZIP2 to USES=tar:bzip2

Approved by:portmgr blanket
-

  Build ID:  20140725122000-17714
  Job owner: amd...@freebsd.org
  Buildtime: 10 hours
  Enddate:   Fri, 25 Jul 2014 22:37:25 GMT

  Revision:  362884
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362884

-

Port:japanese/scim-uim 0.2.0_9

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384334/ja-scim-uim-0.2.0_9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384335/ja-scim-uim-0.2.0_9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384336/ja-scim-uim-0.2.0_9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384337/ja-scim-uim-0.2.0_9.log

-

Port:japanese/uim-anthy 1.8.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384338/ja-uim-anthy-1.8.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384339/ja-uim-anthy-1.8.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384340/ja-uim-anthy-1.8.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384341/ja-uim-anthy-1.8.6_1.log

-

Port:japanese/uim-tomoe-gtk 0.6.0_13

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384342/ja-uim-tomoe-gtk-0.6.0_13.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384343/ja-uim-tomoe-gtk-0.6.0_13.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384344/ja-uim-tomoe-gtk-0.6.0_13.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384345/ja-uim-tomoe-gtk-0.6.0_13.log

-

Port:textproc/uim 1.8.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384346/uim-1.8.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384347/uim-1.8.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384348/uim-1.8.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384349/uim-1.8.6_1.log

-

Port:textproc/uim-el 1.8.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384350/uim-el-emacs24-1.8.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384351/uim-el-emacs24-1.8.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384352/uim-el-emacs24-1.8.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384353/uim-el-emacs24-1.8.6_1.log

-

Port:textproc/uim-gtk 1.8.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725122000-17714-384354/uim-gtk-1.8.6_1.log

  Buildgroup:

make checksum problems

2014-07-25 Thread RW

There seems to be a change in "make checksum" where it's deleting
preexisting files that don't match their checksums. 

This is having two effects:

1. downloads don't resume any more because the partial file is deleted

2. if a make checksum runs while another make process is downloading a
   distfile, the file is deleted and a new file is created. The first
   process is then writing to a deleted file, so when it completes it
   checks the new incomplete file and deletes that. This can cycle until
   they both reach their FETCH_REGET limit. Usually one ends up with a
   checksum error. 


I suspect that 2  may be affecting portmaster, which runs make checksum
in the background. I have a script that does something similar, and I've
been seeing occasional failed builds like this with portupgrade.

 
Is this a known problem? I don't like to file a PR without doing a
search, and Bugzilla searches are all hanging with "Please stand
by ...".
___
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"


[QAT] 362912: 4x leftovers

2014-07-25 Thread Ports-QAT
Stagify, implement the DOCS option correctly, and enable Apache 2.4.
-

  Build ID:  20140725141801-8257
  Job owner: d...@freebsd.org
  Buildtime: 9 hours
  Enddate:   Fri, 25 Jul 2014 23:05:03 GMT

  Revision:  362912
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362912

-

Port:www/mod_dnssd 0.6_9

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~d...@freebsd.org/20140725141801-8257-384482/ap24-mod_dnssd-0.6_9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~d...@freebsd.org/20140725141801-8257-384483/ap24-mod_dnssd-0.6_9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~d...@freebsd.org/20140725141801-8257-384484/ap24-mod_dnssd-0.6_9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~d...@freebsd.org/20140725141801-8257-384485/ap24-mod_dnssd-0.6_9.log


--
Buildarchive URL: 
redports 
___
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: zoneminder staging patches in the works

2014-07-25 Thread G. Paul Ziemba
I wrote:

>I'm happy to say that I have made good progress on stagifying
>this port and hope to submit patches in the next day or two.
>I'm working with the existing version (1.25.0) because I want
>to get the staging support added ASAP.

Patch submitted with bugzilla entry

192123 [patch] multimedia/zoneminder: Enable STAGE support
-- 
G. Paul Ziemba
FreeBSD unix:
 4:16PM  up 12 days,  4:45, 13 users, load averages: 1.26, 1.31, 1.44
___
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"


[QAT] 362932: 4x leftovers

2014-07-25 Thread Ports-QAT
- Drop .la files, no dependees require them and they are not used to load 
plugins
- Convert USE_XZ to USES

Approved by:portmgr blanket
Approved by:kwm (converting leaf gnome@ ports to USES=libtool)
-

  Build ID:  20140725203800-32444
  Job owner: amd...@freebsd.org
  Buildtime: 4 hours
  Enddate:   Sat, 26 Jul 2014 00:27:10 GMT

  Revision:  362932
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362932

-

Port:net-im/ekiga 4.0.1_5

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725203800-32444-384586/ekiga-4.0.1_5.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725203800-32444-384587/ekiga-4.0.1_5.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725203800-32444-384588/ekiga-4.0.1_5.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~amd...@freebsd.org/20140725203800-32444-384589/ekiga-4.0.1_5.log


--
Buildarchive URL: 
redports 
___
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: Merging several branches with ports tree

2014-07-25 Thread Beeblebrox
> Perhaps ports-mgmt/portshaker is a possible tool.
I like portshaker and I have tried it. For gnome3 / marcuscom it resulted in 
some strange ports errors so I was forced to revert back to the marcusmerge 
script.
 
Perhaps I could have a process where the scripts are chained.
1. portshaker -UM for ports tree only
2. marcusmerge for gnome3
3. rsync linux-c6 & my-pc
I'll look into this idea...

> With the line in make.conf there is no need to patch bsd.port.mk for
> own $CAT VALID_CATEGORIES+=foo bar
> 
> Use .sinclude instead .include for own Makefile extensions, then
> there is no issue in case the file is missing.

I'm not sure I understand this - .sinclude should be specified where / in which 
file?

Regards.

-- 
FreeBSD_amd64_11-Current_RadeonKMS




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Merging-several-branches-with-ports-tree-tp5931719p5931863.html
Sent from the freebsd-ports mailing list archive at Nabble.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: www/firefox vs. vulnerabilities vs. libevent --> libevent2

2014-07-25 Thread Kevin Oberman
On Fri, Jul 25, 2014 at 5:45 AM, David Wolfskill 
wrote:

> /usr/ports is a working copy of head@r362876; during my daily portmaster
> run to update all installed ports on my laptop, I see that libevent1 is
> now replaced by libevent2.
>
> Apparently www/firefox had been linked against libevent, so portmaster
> tries to update www/firefox (after having updated several other ports).
>
> That process terminates rather abrutly, however:
>
> ===>>> All >> firefox-30.0_1,1 (12/15)
> 0;portmaster: All >> firefox-30.0_1,1 (12/15)^G
> ===>  Cleaning for firefox-30.0_2,1
> ===>  firefox-30.0_2,1 has known vulnerabilities:
> firefox-30.0_2,1 is vulnerable:
> mozilla -- multiple vulnerabilities
> CVE: CVE-2014-1561
> CVE: CVE-2014-1560
> CVE: CVE-2014-1559
> CVE: CVE-2014-1558
> CVE: CVE-2014-1557
> CVE: CVE-2014-1556
> CVE: CVE-2014-1555
> CVE: CVE-2014-1552
> CVE: CVE-2014-1551
> CVE: CVE-2014-1550
> CVE: CVE-2014-1549
> CVE: CVE-2014-1548
> CVE: CVE-2014-1547
> CVE: CVE-2014-1544
> WWW:
> http://portaudit.FreeBSD.org/978b0f76-122d-11e4-afe3-bc5ff4fb5e7b.html
>
> 1 problem(s) in the installed packages found.
> => Please update your ports tree and try again.
> => Note: Vulnerable ports are marked as such even if there is no update
> available.
> => If you wish to ignore this vulnerability rebuild with 'make
> DISABLE_VULNERABILITIES=yes'
> *** [check-vulnerable] Error code 1
>
> Stop in /common/ports/www/firefox.
> *** [build] Error code 1
>
> Stop in /common/ports/www/firefox.
>
> ===>>> make build failed for www/firefox
> ===>>> Aborting update
>
>
> As a reality check, I did take a quick look at
>  to see
> if, perchance, there were commits to www/firefox to address those
> reported vulnerabilities since r362876, but the most recent commit
> I see there now is r362887 -- and none of the commits since r362876
> is about/for www/firefox (or anything related, AFAICT).
>
> So I'm left wondering how this is actually useful: I'm left with a copy
> of firefox installed (more or less) that has known vulnerabilities and
> is broken (since it's still linked against a library that no longer
> exists).  At least I was able to use a copy of firefox on a machine I
> haven't started to upgrade yet (so I could refer to the cited Web
> page(s)).
>
> Since I'm disinclined to globally disable all vulnerability checking,
> I'm proceeding with updates to the ports that portmaster hadn't yet got
> to first, before (temporarily) disabling the checks so I can have a
> working graphical Web browser with which I'm familiar again.
>
> Which reminds me: the cited directive re. the libevent change (in
> UPDATING): "pkg delete libevent" also deleted sysutils/tmux, so the
> subsequent "portmaster -ad" had no clue that tmux was supposed to be
> rebuilt.  I was able to re-install it manually, but I mention this in
> case it helps someone else.
>
> (Ugh.  It appears that the "portmaster -aF" that I ran earlier this
> morning didn't actually fetch the firefox-30.0.source.tar.bz2... wait
> up; that should have been there already.  Making me wait while that's
> re-fetched is ... not good: I'm trying to get this laptop updated before
> I go in to work this morning  OK; I found a local copy on another
> machine.)
>
> 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.
>

David,

Since the old firefox was vulnerable and we don't have a port of Firefox 31
yet, the best choice seems to be to install the new, libevent2 version (_2)
with DISABLE_VULNERABILITIES defined so that it will still install.
Obviously, you just set DISABLE_VULNERABILITIES for the firefox build and
then unset it. Not ideal, but the only available work around.

Also, the solver in pkg will re-install all dependent ports when a port is
deleted. (It does ask first.) I just note the "extra" deleted ports and
re-install. But I do wish we had had a hears-up on this as I lost gnuplot
yesterday for quite a while which rather seriously impacted my web pages as
new graphs were not being generated. After that first system, I was
smarter, but there really needs to be a BIG warning in UPDATING and when
pkg delete deletes dependent packages. There ought to be a better way, but
-o does not help as libevent2 already existed. This one is VERY user
unfriendly!
--
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"


Re: Lots of installed ports show "succeeds index"

2014-07-25 Thread Kevin Oberman
On Fri, Jul 25, 2014 at 7:51 AM, Christian Weisgerber 
wrote:

> On 2014-07-24, Kevin Oberman  wrote:
>
> >> > Is there a reason you want to avoid using the index? It's worked just
> >> fine
> >> > for me for several months on systems with well over 1000 ports
> installed.
> >>
> >> It isn't in sync with my ports tree
> >
> > Which begs the question, why is it out of sync? If you update your ports
> > tree, all you need to do is:
> > make -C /usr/ports fetchindex (takes a few seconds)
>
> Which fetches an INDEX file that is regularly generated on some
> FreeBSD server, but is not in sync with the exact revision of the
> ports tree I just updated to.
>
> --
> Christian "naddy" Weisgerber  na...@mips.inka.de
>

Yes, but the INDEX is guaranteed to  older than your tre, so you never get
the ports installed as being newer than those in the ports tree.

I always issue a fetchindex immediately after an 'svn up /usr/ports' so
they are very close. It's worked for me for many years, going back to CVS
days, of course.
--
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"


Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-25 Thread Dylan Leigh
On Fri, Jul 25, 2014 at 03:05:32PM -0600, Warren Block wrote:
> On Fri, 25 Jul 2014, Craig Rodrigues wrote:
> 
> >What I'd like to see is an article on freebsd.org either on the wiki
> >or in the handbook, which compares using apt, yum, rpm, whatever
> >to pkg.  Is anyone interested in working on an article like this?
> >I don't have the bandwidth right now.
> 
> A person to write that article needs detailed knowledge of pkg and
> the Linux package systems.  I don't have that, but would be willing
> to help you develop an outline for the article.  Having a design
> like that makes it easier to write when time and resources are
> available.

My 2 cents as someone who uses both Ubuntu and FreeBSD: I find
that pkg is basically identical to using apt. The basic commands
are the same. Look&feel and configuration files are different
but that is to be expected, and neither require much tweaking.

The big difference between them from a user POV is that pkg
still requires a bit of knowledge of ports and how it works
(what options are, categories etc.) whereas using apt requires
no knowledge of the Ubuntu package infrastructure or how .deb
files are built.

I was already familiar with ports long before Pngng came around,
but to a new user migrating from Linux I can see how trying to
use pkg while bypassing the ports documentation could result in
later confusion.

-- Dylan


-- 
Dylan Leigh // VU# s4081906 // www.dylanleigh.net

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"