Re: Unable to print from firefox
2013-06-24 21:01, Warren Block skrev: On Thu, 13 Jun 2013, Bernt Hansson wrote: On 2013-06-12 11:01, Albert Shih wrote: Hi I'm unable to print from firefox/chrome/opera so that really s***.. When I try to print something in firefox I got this message (firefox:45435): Gtk-WARNING **: Unknown paper size A4 Do you have for example print/libpaper, print/papersize-default-a4 or any other paper size stuff installed. Just getting back to this. I decided to see what had installed cups-client as a dependency. To my surprise, pkg_delete did not complain and just went ahead and deleted it. Now Firefox printing is fine. ___ 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 Interesting! If I do that I get: pkg delete cups-client pkg: Error while trying to delete packages, dependencies that are still required: print/cups-client: print/cups-base, print/cups-image, print/cups-pstoraster, print/ghostscript9, x11-themes/gtk-engines2, graphics/librsvg2, graphics/ImageMagick, devel/libglade2, net/avahi-gtk, print/teTeX-base, print/cm-super, print/dvipsk-tetex, devel/gconf2, graphics/libopenraw, x11-toolkits/gtkmm24, sysutils/gsmartcontrol, x11-themes/gtk-xfce-engine, print/gutenprint-base, print/gutenprint-cups, print/gutenprint-ijs, audio/libcanberra, devel/libnotify, x11-toolkits/libwnck, www/nspluginwrapper, x11-toolkits/py-gtk2, print/dvipdfmx, print/teTeX, x11/xfce4-conf, x11/libxfce4menu, x11/libexo, x11-fm/thunar-vfs, x11-toolkits/vte, x11/wbar, x11/wbarconf, print/xdvik, print/foomatic-filters, print/hplip, x11-toolkits/gtksourceview2, editors/mousepad, security/libgnome-keyring, devel/libsoup-gnome, sysutils/policykit-gnome, sysutils/gnome-mount, devel/gvfs, www/webkit-gtk2, print/gimp-gutenprint, print/gutenprint, x11-toolkits/unique, x11-fm/thunar, x11-toolkits/libxfce4gui, x11-wm/xfce4-panel, deskutils/orage, archivers/squeeze, misc/xfce4-appfinder, x11-wm/xfce4-desktop, audio/xfce4-mixer, deskutils/xfce4-notifyd, print/xfce4-print, sysutils/xfce4-settings, x11/xfce4-terminal, x11-wm/xfce4-wm, x11-wm/xfce4-session, x11-wm/xfce4, sysutils/xfce4-battery-plugin, sysutils/xfce4-systemload-plugin, sysutils/xfce4-wavelan-plugin, mail/thunderbird, mail/thunderbird-i18n, www/firefox, www/firefox-i18n, www/libxul, audio/pulseaudio, net/freerdp, java/icedtea-web, x11-toolkits/gtk20, graphics/gegl, net/remmina, net/remmina-plugin-i18n, net/remmina-plugin-vnc, editors/libreoffice, editors/libreoffice-sv, graphics/gimp-app, graphics/gimp /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... ___ 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
Log rotation kills squeezeboxserver CLI
I haven't figured out why, unfortunately, but if you use SBS' CLI interface, it stops responding when the log gets rotated by newsyslog. Removing it from newsyslog.conf fixes the problem (obviously at the cost of no log rotation :-). It also logs a _lot_ of crap, btw. ___ 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
math/scilab port
Hi,
I suggest the following patch for math/scilab: due to a problem in the
port math/suitesparse umfpack is not linked to suitesparseconfig and
-lsuitesparseconfig must be explicitely added each time -lumfpack is
used.
Best regards,
Olivier
$ pkg_info -E suitesparse\*
suitesparse-4.0.2_1
$ pkg_info -E scilab\*
scilab-5.3.3_5
$ uname -a
FreeBSD banyan2.cs.ait.ac.th 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #8: Tue Jun
18 08:39:59 ICT 2013 r...@banyan2.cs.ait.ac.th:/usr/obj/usr/src/sys/CSIM
amd64
/usr/ports/math/scilab/files/patch-configure
--- configure.orig 2011-07-20 15:15:42.0 +0700
+++ configure 2013-06-25 17:16:06.0 +0700
@@ -22347,13 +22347,13 @@
fi
- { $as_echo $as_me:${as_lineno-$LINENO}: checking for umf_divcomplex in
-lumfpack 5
-$as_echo_n checking for umf_divcomplex in -lumfpack... 6; }
+ { $as_echo $as_me:${as_lineno-$LINENO}: checking for umf_divcomplex in
-lumfpack -lsuitesparseconfig 5
+$as_echo_n checking for umf_divcomplex in -lumfpack -lsuitesparseconfig...
6; }
if test ${ac_cv_lib_umfpack_umf_divcomplex+set} = set; then :
$as_echo_n (cached) 6
else
ac_check_lib_save_LIBS=$LIBS
-LIBS=-lumfpack $LIBS
+LIBS=-lumfpack -lsuitesparseconfig $LIBS
cat confdefs.h - _ACEOF conftest.$ac_ext
/* end confdefs.h. */
@@ -22392,7 +22392,7 @@
{ $as_echo $as_me:${as_lineno-$LINENO}: result:
$ac_cv_lib_umfpack_umf_divcomplex 5
$as_echo $ac_cv_lib_umfpack_umf_divcomplex 6; }
if test x$ac_cv_lib_umfpack_umf_divcomplex = xyes; then :
- UMFPACK_LIB=-L$with_umfpack_library -lumfpack $UMFPACK_LIB; UMFPACK_OK=yes
+ UMFPACK_LIB=-L$with_umfpack_library -lumfpack -lsuitesparseconfig
$UMFPACK_LIB; UMFPACK_OK=yes
else
as_fn_error $? libumfpack : Library missing. (Cannot find umf_divcomplex).
Check if libumfpack is installed and if the version is correct (also called lib
suitesparse) $LINENO 5
@@ -22463,13 +22463,13 @@
fi
LIBS=$UMFPACK_LIB $LIBS
- { $as_echo $as_me:${as_lineno-$LINENO}: checking for umf_divcomplex in
-lumfpack 5
-$as_echo_n checking for umf_divcomplex in -lumfpack... 6; }
+ { $as_echo $as_me:${as_lineno-$LINENO}: checking for umf_divcomplex in
-lumfpack -lsuitesparseconfig 5
+$as_echo_n checking for umf_divcomplex in -lumfpack -lsuitesparseconfig...
6; }
if test ${ac_cv_lib_umfpack_umf_divcomplex+set} = set; then :
$as_echo_n (cached) 6
else
ac_check_lib_save_LIBS=$LIBS
-LIBS=-lumfpack $LIBS
+LIBS=-lumfpack -lsuitesparseconfig $LIBS
cat confdefs.h - _ACEOF conftest.$ac_ext
/* end confdefs.h. */
@@ -22508,7 +22508,7 @@
{ $as_echo $as_me:${as_lineno-$LINENO}: result:
$ac_cv_lib_umfpack_umf_divcomplex 5
$as_echo $ac_cv_lib_umfpack_umf_divcomplex 6; }
if test x$ac_cv_lib_umfpack_umf_divcomplex = xyes; then :
- UMFPACK_LIB=-lumfpack $UMFPACK_LIB; UMFPACK_OK=yes
+ UMFPACK_LIB=-lumfpack -lsuitesparseconfig $UMFPACK_LIB; UMFPACK_OK=yes
else
as_fn_error $? libumfpack: Library missing. (Cannot find symbol
umf_divcomplex). Check if libumfpack is installed and if the version is correct
(also called lib suitesparse) $LINENO 5
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) regards, Bapt pgp5L24unaVxs.pgp Description: PGP signature
Re: pkgng seems to be out of date?
On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? But that doesn't explain why pkg says tcl85 and ports says tcl86 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I'll try to figure out that bug. regards, Bapt pgpBfIRCq2iTb.pgp Description: PGP signature
Re: pkgng seems to be out of date?
On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... How can I force pkg to rebuild its dependencies? Is it even possible? Is there any way for pkg to check the integrity of its database? I'll try to figure out that bug. regards, Bapt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 11:56:46AM +0100, Ben Laurie wrote: On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... I think is it a bug in portmaster and/or not having fully follow 20130206 of UPDATING. pkg only registers dependencies it is being told to register by the ports tree/portmaster. How can I force pkg to rebuild its dependencies? Is it even possible? portmaster -af should do it probably (I'm not a portmaster user) Is there any way for pkg to check the integrity of its database? pkg check -d will do, but imho will find nothing. regards, Bapt pgpHNf6xD4D7M.pgp Description: PGP signature
Re: pkgng seems to be out of date?
On 25 June 2013 12:32, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:56:46AM +0100, Ben Laurie wrote: On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... I think is it a bug in portmaster and/or not having fully follow 20130206 of UPDATING. pkg only registers dependencies it is being told to register by the ports tree/portmaster. How can I force pkg to rebuild its dependencies? Is it even possible? portmaster -af should do it probably (I'm not a portmaster user) I just did a portmaster -a, that's how I got into this situation... What port management tool _does_ work with pkg? Is there any way for pkg to check the integrity of its database? pkg check -d will do, but imho will find nothing. # pkg check -d x11-toolkits/py-wxPython28-common has a missing dependency: lang/tcl-modules x11-toolkits/py-wxPython28-unicode has a missing dependency: lang/tcl-modules textproc/xml2rfc has a missing dependency: lang/tcl-modules ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 12:53:42PM +0100, Ben Laurie wrote: On 25 June 2013 12:32, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:56:46AM +0100, Ben Laurie wrote: On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... I think is it a bug in portmaster and/or not having fully follow 20130206 of UPDATING. pkg only registers dependencies it is being told to register by the ports tree/portmaster. How can I force pkg to rebuild its dependencies? Is it even possible? portmaster -af should do it probably (I'm not a portmaster user) I just did a portmaster -a, that's how I got into this situation... What port management tool _does_ work with pkg? both portmaster and portupgrade, I'm sure what you hit is the UPDATING that has not been followed, there is a decicated part for tcl. Is there any way for pkg to check the integrity of its database? pkg check -d will do, but imho will find nothing. # pkg check -d x11-toolkits/py-wxPython28-common has a missing dependency: lang/tcl-modules x11-toolkits/py-wxPython28-unicode has a missing dependency: lang/tcl-modules textproc/xml2rfc has a missing dependency: lang/tcl-modules That proves you haven't followed the 20130206 entry. regards, Bapt pgpMCrkWgYPwo.pgp Description: PGP signature
Re: Log rotation kills squeezeboxserver CLI
Hi Ben, if you change newsyslog.conf to recreate the file with slimserv ownership, does it fix the error (although not the warnings)? /var/log/squeezeboxserver/server.logslimserv:slimserv 644 3 100 * J /var/run/squeezeboxserver/squeezeboxserver.pid -- Mark Knight Mobile: +44 7880 556751. Home: +44 1223 858596 Email: ma...@knigma.org. Skype: knigma On 25/06/2013 10:35, Ben Laurie wrote: I haven't figured out why, unfortunately, but if you use SBS' CLI interface, it stops responding when the log gets rotated by newsyslog. Removing it from newsyslog.conf fixes the problem (obviously at the cost of no log rotation :-). It also logs a _lot_ of crap, btw. ___ 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: make: /usr/ports/Mk/bsd.port.mk line 1638: warning: Couldn't read shell's output for if /sbin/sysctl -n compat.ia32.maxvmem /dev/null 21; then echo YES; fi
On Fri, Jun 21, 2013 at 04:54:22PM +0200, John Marino wrote: On 6/21/2013 16:42, Anton Shterenlikht wrote: On ia64 r252055 with ports at r321471 make issues lots of warnings like: # make -C /usr/ports/ fetchindex make: /usr/ports/Mk/bsd.port.subdir.mk line 101: warning: Couldn't read shell's output for if /sbin/sysctl -n compat.ia32.maxvmem /dev/null 21; then echo YES; fi make: /usr/ports/Mk/bsd.port.mk line 1638: warning: Couldn't read shell's output for if /sbin/sysctl -n compat.ia32.maxvmem /dev/null 21; then echo YES; fi *and many more idencal ones* That looks like bmake output. There should be an else part of the conditional that returns TRUE or echo. bmake shell commands don't like null output. The bsd.port.subdir.mk needs to be tweaked for bmake. John Fixed as of r321735 and r321739 regards, Bapt pgpOwD5oofXta.pgp Description: PGP signature
Re: pkgng seems to be out of date?
On 25 June 2013 12:57, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 12:53:42PM +0100, Ben Laurie wrote: On 25 June 2013 12:32, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:56:46AM +0100, Ben Laurie wrote: On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... I think is it a bug in portmaster and/or not having fully follow 20130206 of UPDATING. pkg only registers dependencies it is being told to register by the ports tree/portmaster. How can I force pkg to rebuild its dependencies? Is it even possible? portmaster -af should do it probably (I'm not a portmaster user) I just did a portmaster -a, that's how I got into this situation... What port management tool _does_ work with pkg? both portmaster and portupgrade, I'm sure what you hit is the UPDATING that has not been followed, there is a decicated part for tcl. Is there any way for pkg to check the integrity of its database? pkg check -d will do, but imho will find nothing. # pkg check -d x11-toolkits/py-wxPython28-common has a missing dependency: lang/tcl-modules x11-toolkits/py-wxPython28-unicode has a missing dependency: lang/tcl-modules textproc/xml2rfc has a missing dependency: lang/tcl-modules That proves you haven't followed the 20130206 entry. Oh, sorry, I missed that reference the first time round. Hmm, just discovered pkg updating. It'd be nice if there were a way to skip all the things that say rebuild everything that depends on it, which seems kinda obvious... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On 25 June 2013 13:35, Ben Laurie b...@links.org wrote: On 25 June 2013 12:57, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 12:53:42PM +0100, Ben Laurie wrote: On 25 June 2013 12:32, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:56:46AM +0100, Ben Laurie wrote: On 25 June 2013 11:40, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 11:36:07AM +0100, Ben Laurie wrote: On 25 June 2013 11:31, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Jun 25, 2013 at 10:36:14AM +0100, Ben Laurie wrote: ping? On 22 June 2013 18:46, Ben Laurie b...@links.org wrote: $ pwd /usr/ports/textproc/xml2rfc $ make build-depends-list /usr/ports/ports-mgmt/pkg $ make run-depends-list /usr/ports/lang/tcl86 /usr/ports/x11-toolkits/tk86 But... $ pkg query '%n: %do' xml2rfc xml2rfc: textproc/expat2 xml2rfc: x11-fonts/fontconfig xml2rfc: print/freetype2 xml2rfc: x11/kbproto xml2rfc: x11/libX11 xml2rfc: x11/libXau xml2rfc: x11/libXdmcp xml2rfc: x11-fonts/libXft xml2rfc: x11/libXrender xml2rfc: devel/libpthread-stubs xml2rfc: x11/libxcb xml2rfc: devel/pkgconf xml2rfc: x11/renderproto xml2rfc: lang/tcl-modules xml2rfc: lang/tcl85 xml2rfc: x11-toolkits/tk85 xml2rfc: x11/xproto a) Why so many more dependencies, and... b) Why different versions of tcl/tk? And ... how do I fix it? BTW, I use portmaster to maintain my installed ports... That is how the ports tree works for eons, and that can't be fixed until we can totally get rid if pkg_install (to many corner egdes) pkg_install to work properly needs to track fully direct and indirect dependencies, pkg does not, but because the ports tree still need to be compatible with pkg_install and lots of people are still using all habits from the pkg_install time, it is very hard to remove this right now.) But yes for sure this feature will get removed :)) So are you saying that pkg includes indirect dependencies, while ports do not? Yes But that doesn't explain why pkg says tcl85 and ports says tcl86 That is probably a bug of run-depends not discovering you have tcl85 installed so getting to the default tcl for its dependency which is tcl86. I actually have both installed, so I think the bug is in pkg. I'd like to remove ports I don't need but pkg won't let me remove tcl85, which I think I don't really need... I think is it a bug in portmaster and/or not having fully follow 20130206 of UPDATING. pkg only registers dependencies it is being told to register by the ports tree/portmaster. How can I force pkg to rebuild its dependencies? Is it even possible? portmaster -af should do it probably (I'm not a portmaster user) I just did a portmaster -a, that's how I got into this situation... What port management tool _does_ work with pkg? both portmaster and portupgrade, I'm sure what you hit is the UPDATING that has not been followed, there is a decicated part for tcl. Is there any way for pkg to check the integrity of its database? pkg check -d will do, but imho will find nothing. # pkg check -d x11-toolkits/py-wxPython28-common has a missing dependency: lang/tcl-modules x11-toolkits/py-wxPython28-unicode has a missing dependency: lang/tcl-modules textproc/xml2rfc has a missing dependency: lang/tcl-modules That proves you haven't followed the 20130206 entry. Oh, sorry, I missed that reference the first time round. Hmm, just discovered pkg updating. It'd be nice if there were a way to skip all the things that say rebuild everything that depends on it, which seems kinda obvious... Hmmm. pkg updating doesn't actually show the relevant 20130206 entry - so not actually useful. ___ 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: sqlite: no such column: infos (pkgdb.c:1086)
I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, but still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) version 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no column named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.c:2266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton ___ 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: sqlite: no such column: infos (pkgdb.c:1086)
On Tue, Jun 25, 2013 at 02:22:31PM +0100, Anton Shterenlikht wrote: I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, but still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) version 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no column named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.c:2266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton ___ 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 Why downgrading? Please upgrade again to 1.1.2 :) and report bug if any. regards, Bapt pgp1GKJ8PVG2A.pgp Description: PGP signature
Re: pkg: sqlite: no such column: infos (pkgdb.c:1086)
On Tue, Jun 25, 2013 at 02:57:16PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Tue Jun 25 14:52:59 2013 On Tue, Jun 25, 2013 at 02:22:31PM +0100, Anton Shterenlikht wrote: I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: Running ldconfig /sbin/ldconfig -m /usr/local/lib Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, but= still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) version = 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no colum= n named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.c:2= 266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton Why downgrading? Please upgrade again to 1.1.2 :) and report bug if any. Sorry, I don't get you. I need the ports tree to be at 319054. I then do pkg info -xd xorg-server /root/xorg-dep portmaster -f `cat /root/xorg-dep` Is this not supported? You mean you went forward and switch back to a former version? Switching from 1.1 back to 1.0 has been taken in account during the pkg-devel phase, but not considered for after 1.1 is offically released which explains why you have this message. We could had the compatibility he really needed. Normal path is not to go backward :) regards, Bapt pgpaBr38MopG9.pgp Description: PGP signature
Re: pkg: sqlite: no such column: infos (pkgdb.c:1086)
From baptiste.darous...@gmail.com Tue Jun 25 14:52:59 2013 On Tue, Jun 25, 2013 at 02:22:31PM +0100, Anton Shterenlikht wrote: I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: Running ldconfig /sbin/ldconfig -m /usr/local/lib Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, but= still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) version = 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no colum= n named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.c:2= 266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton Why downgrading? Please upgrade again to 1.1.2 :) and report bug if any. Sorry, I don't get you. I need the ports tree to be at 319054. I then do pkg info -xd xorg-server /root/xorg-dep portmaster -f `cat /root/xorg-dep` Is this not supported? Thanks Anton ___ 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: sqlite: no such column: infos (pkgdb.c:1086)
On Tue, Jun 25, 2013 at 03:23:54PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Tue Jun 25 15:20:11 2013 On Tue, Jun 25, 2013 at 02:57:16PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Tue Jun 25 14:52:59 2013 =20 On Tue, Jun 25, 2013 at 02:22:31PM +0100, Anton Shterenlikht wrote: I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: Running ldconfig /sbin/ldconfig -m /usr/local/lib Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, = but=3D still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) versi= on =3D 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no co= lum=3D n named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.= c:2=3D 266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton =20 Why downgrading? Please upgrade again to 1.1.2 :) and report bug if any. =20 Sorry, I don't get you. =20 I need the ports tree to be at 319054. I then do =20 pkg info -xd xorg-server /root/xorg-dep portmaster -f `cat /root/xorg-dep` =20 Is this not supported? You mean you went forward and switch back to a former version? yes Switching from 1.1 back to 1.0 has been taken in account during the pkg-dev= el phase, but not considered for after 1.1 is offically released which explain= s why you have this message. We could had the compatibility he really needed. Normal path is not to go backward :) ok, so what if I keep only ports-mgmt/pkg up to date, and leave the rest of the ports tree at 319054? Will this work, i.e. wil I be able to use pkg tools with older portmaster? Or maybe I need to keep both pkg and portmaster up to date? Will this work? Normally only keeping ports-mgmt/pkg up to date will work, however I will recommand anyway to keep portmaster uptodate either. regards, Bapt pgp6VG3pN5hq2.pgp Description: PGP signature
Re: pkg: sqlite: no such column: infos (pkgdb.c:1086)
From baptiste.darous...@gmail.com Tue Jun 25 15:20:11 2013 On Tue, Jun 25, 2013 at 02:57:16PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Tue Jun 25 14:52:59 2013 =20 On Tue, Jun 25, 2013 at 02:22:31PM +0100, Anton Shterenlikht wrote: I'm debugging X11 on sparc64. I need to roll the ports tree back to 319054. On downgrading pkg I get: Running ldconfig /sbin/ldconfig -m /usr/local/lib Registering installation for pkg-1.0.12_1 pkg: warning: database version 19 is newer than libpkg(3) version 12, = but=3D still compatible pkg: sqlite: no such column: infos (pkgdb.c:1086) pkg-static: warning: database version 19 is newer than libpkg(3) versi= on =3D 12, but still compatible Installing pkg-1.0.12_1...pkg-static: sqlite: table packages has no co= lum=3D n named infos (pkgdb.c:1757) pkg-static: sqlite: cannot rollback - no transaction is active (pkgdb.= c:2=3D 266) *** Error code 70 Stop. make: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Shall I open a PR? Thanks Anton =20 Why downgrading? Please upgrade again to 1.1.2 :) and report bug if any. =20 Sorry, I don't get you. =20 I need the ports tree to be at 319054. I then do =20 pkg info -xd xorg-server /root/xorg-dep portmaster -f `cat /root/xorg-dep` =20 Is this not supported? You mean you went forward and switch back to a former version? yes Switching from 1.1 back to 1.0 has been taken in account during the pkg-dev= el phase, but not considered for after 1.1 is offically released which explain= s why you have this message. We could had the compatibility he really needed. Normal path is not to go backward :) ok, so what if I keep only ports-mgmt/pkg up to date, and leave the rest of the ports tree at 319054? Will this work, i.e. wil I be able to use pkg tools with older portmaster? Or maybe I need to keep both pkg and portmaster up to date? Will this work? Thanks Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013, at 7:50, Ben Laurie wrote: Hmmm. pkg updating doesn't actually show the relevant 20130206 entry - so not actually useful. pkg updating literally just reads /usr/ports/UPDATING... is your ports tree up to date? Did the committer of this tcl incident commit the changes before touching UPDATING and you're caught inbetween? I suppose this could use a bit of investigation... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 09:58:55AM -0500, Mark Felder wrote: On Tue, Jun 25, 2013, at 7:50, Ben Laurie wrote: Hmmm. pkg updating doesn't actually show the relevant 20130206 entry - so not actually useful. pkg updating literally just reads /usr/ports/UPDATING... is your ports tree up to date? Did the committer of this tcl incident commit the changes before touching UPDATING and you're caught inbetween? I suppose this could use a bit of investigation... pkg updating tries match the installed packages origin in AFFECTS line, via strstr, in that case it does not match that is why it fails at showing it up. I'm fixing the UPDATING entry. regards, Bapt pgpWmzpARPDlx.pgp Description: PGP signature
Re: pkgng seems to be out of date?
On Tue, Jun 25, 2013 at 05:17:08PM +0200, Baptiste Daroussin wrote: On Tue, Jun 25, 2013 at 09:58:55AM -0500, Mark Felder wrote: On Tue, Jun 25, 2013, at 7:50, Ben Laurie wrote: Hmmm. pkg updating doesn't actually show the relevant 20130206 entry - so not actually useful. pkg updating literally just reads /usr/ports/UPDATING... is your ports tree up to date? Did the committer of this tcl incident commit the changes before touching UPDATING and you're caught inbetween? I suppose this could use a bit of investigation... pkg updating tries match the installed packages origin in AFFECTS line, via strstr, in that case it does not match that is why it fails at showing it up. I'm fixing the UPDATING entry. In fact that would mean too many entries in AFFECTS. Best would be to improve pkg updating matching. regards, Bapt pgpvZvlgSOzxy.pgp Description: PGP signature
Re: Ocaml ports needs love
Baptiste Daroussin wrote: On Wed, Feb 27, 2013 at 01:09:34PM +, b.f. wrote: Probably creating a ocaml@ team would be a good idea? It feels good to see that more people are willing to improve the support of OCaml in FreeBSD. Besides maintaining individual ports, we also want to integrate GODI or OASIS in ports, so it is probably a good idea to have a common place to discuss these projects, to keep a list of open tasks and describe best practices. A mailing list could be useful, as would a section on the wiki [1]. I am pleased to announce that I improved my submission for OCaml-4.00 [2] (there is still a minor issue) and applied for a project ocaml-freebsd on OCamcore's forge. [1] https://wiki.freebsd.org/Haskell [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=173364cat=ports Regards, Michael ___ 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
rc.d scripts to control multiple instances of the same daemon?
I'm in the process of (re)writing an rc.d script for kadmind (security/krb5). Unlike the main Kerberos daemon, kadmind needs to have a separate instance for each realm on the server -- it can't support multiple realms in a single process. What I need to be able to do: 1) Have different flags and pidfiles for each instance. 2) Be able to start, stop, restart, and status each individual instance by giving its name on the command line. 3) Have all instances start/stop automatically when a specific instance isn't specified. I've looked around for examples of good practice to emulate, and haven't found much. The closest to what I want looks to be vboxheadless, but I'm uncomfortable with the amount of mechanism from rc.subr that it needs to reimplement. Are there any better examples? -GAWollman ___ 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: rc.d scripts to control multiple instances of the same daemon?
On 2013-06-25 21:44, Garrett Wollman wrote: I'm in the process of (re)writing an rc.d script for kadmind (security/krb5). Unlike the main Kerberos daemon, kadmind needs to have a separate instance for each realm on the server -- it can't support multiple realms in a single process. What I need to be able to do: 1) Have different flags and pidfiles for each instance. 2) Be able to start, stop, restart, and status each individual instance by giving its name on the command line. 3) Have all instances start/stop automatically when a specific instance isn't specified. I've looked around for examples of good practice to emulate, and haven't found much. The closest to what I want looks to be vboxheadless, but I'm uncomfortable with the amount of mechanism from rc.subr that it needs to reimplement. Are there any better examples? -GAWollman Take a look into the openvpn rc script (works with softlinks). A more complex script that supports multiple instances can be found in the www/apache2x ports. -- 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: rc.d scripts to control multiple instances of the same daemon?
On Tue, 2013-06-25 at 15:44 -0400, Garrett Wollman wrote: I'm in the process of (re)writing an rc.d script for kadmind (security/krb5). Unlike the main Kerberos daemon, kadmind needs to have a separate instance for each realm on the server -- it can't support multiple realms in a single process. What I need to be able to do: 1) Have different flags and pidfiles for each instance. 2) Be able to start, stop, restart, and status each individual instance by giving its name on the command line. 3) Have all instances start/stop automatically when a specific instance isn't specified. I've looked around for examples of good practice to emulate, and haven't found much. The closest to what I want looks to be vboxheadless, but I'm uncomfortable with the amount of mechanism from rc.subr that it needs to reimplement. Are there any better examples? The one like that I use the most is service netif restart fpx0 but I'm not sure the complex network stuff will be the cleanest example of anything except how to do complex network stuff. :) -- Ian ___ 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: rc.d scripts to control multiple instances of the same daemon?
On 2013-Jun-25, 15:44, Garrett Wollman wrote:
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a single process. What I need to be able
to do:
1) Have different flags and pidfiles for each instance.
2) Be able to start, stop, restart, and status each individual
instance by giving its name on the command line.
3) Have all instances start/stop automatically when a specific
instance isn't specified.
I've looked around for examples of good practice to emulate, and
haven't found much. The closest to what I want looks to be
vboxheadless, but I'm uncomfortable with the amount of mechanism from
rc.subr that it needs to reimplement. Are there any better examples?
Wouldn't something like this be enough?
#!/bin/sh
. /etc/rc.subr
name=kadmind
rcvar=${name}_enable
start_cmd=kadmind_start $2
load_rc_config $name
kadmind_start()
{
if [ -z $1 ]; then
echo starting all instances
else
echo starting instance $1
fi
}
run_rc_command $1
# /usr/local/etc/rc.d/kadmind start
starting all instances
# /usr/local/etc/rc.d/kadmind start myinst
starting instance myinst
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgpnOo3225fay.pgp
Description: PGP signature
Re: rc.d scripts to control multiple instances of the same daemon?
On Tue, Jun 25, 2013 at 03:44:31PM -0400, Garrett Wollman wrote: I'm in the process of (re)writing an rc.d script for kadmind (security/krb5). Unlike the main Kerberos daemon, kadmind needs to have a separate instance for each realm on the server -- it can't support multiple realms in a single process. What I need to be able to do: 1) Have different flags and pidfiles for each instance. 2) Be able to start, stop, restart, and status each individual instance by giving its name on the command line. 3) Have all instances start/stop automatically when a specific instance isn't specified. I've looked around for examples of good practice to emulate, and haven't found much. The closest to what I want looks to be vboxheadless, but I'm uncomfortable with the amount of mechanism from rc.subr that it needs to reimplement. Are there any better examples? -GAWollman ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org This is a simple multi instance rc.d script: http://svnweb.freebsd.org/ports/head/www/fcgiwrap/files/fcgiwrap.in?revision=307542view=markup regards, Bapt pgpIEL4BT9BqO.pgp Description: PGP signature
Re: REWARD for working pam_mount
On 8/06/2013 1:57 PM, Janet Sullivan wrote: The /usr/ports/sysutils/pam_mount port is broken, because it's expecting an older version of libHX. I'd really like to have a working pam_mount, and am willing to paypal US $50 over to the first person who gets it working. I'm not subscribed to the list, so please email me directly to claim the prize. ___ 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 Hi Janet, Just wanted to get a follow-up on whether the patched worked for you so I can submit is as a PR for the maintainer and get it committed Koobs ___ 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: Are ports supposed to build and run on 10-CURRENT?
On Sat, 22 Jun 2013 00:27:53 +0200
Dimitry Andric d...@freebsd.org wrote:
On Jun 21, 2013, at 22:07, Dimitry Andric d...@freebsd.org wrote:
On Jun 13, 2013, at 03:15, Michael Gmelin free...@grem.de wrote:
...
Hi Dimitry,
Despite my patch to mitigate the problem I discussed and analyzed the
initialization order issue and I think there is a something wrong in
10-CURRENT.
The problem is that static initialization happens in the expected
order (same translation unit), but termination does *not* happen in the
reverse order of initialization, which - according to the C++ standard
section 3.6.3 should be guaranteed:
If the completion of the constructor or dynamic initialization of an
object with static storage duration is sequenced before that of
another, the completion of the destructor of the second is sequenced
before the initiation of the destructor of the first.
The following conditions have to be met in order to show the problem:
1. Two static objects defined in the translation unit containing main
2. Definition of one of the underlying objects is in a separate
source which is used to build a shared library
3. Both, the translation unit containing main an the one forming the
shared library are compiled using -fPIC (or -fpic).
The problem happens on:
- 10-CURRENT with system clang
- 10-CURRENT with clang 3.3 from ports
It doesn't happen on:
- 10-CURRENT with system gcc
- 9.1-RELEASE with system gcc
- 9.1-RELEASE with system clang
- 9.1-RELEASE with clang 3.3 from ports
Also, it does *not* happen on:
- 9.1-RELEASE running executables built on 10-CURRENT (any compiler)
I stripped the problem down to an easy to handle test case, you can
find as an patch at the end of this mail or download a tarball at
http://blog.grem.de/majortom.tgz
To execute the test:
fetch -o - http://blog.grem.de/majortom.tgz | tar -xzf -
cd majortom
make run
The expected outcome is:
Ground | Outer::Outer
Control | Inner::Inner
to |main()
Major| Inner::~Inner
Tom| Outer::~Outer
The actual outcome on 10-CURRENT system clang or clang33 from ports is:
Ground | Outer::Outer
Control | Inner::Inner
to |main()
Tom| Outer::~Outer
Major| Inner::~Inner
Which is really bad (not just for Bowie).
Time to open another PR?
Cheers,
Michael
--- majortom.patch begins here ---
diff -x .git -ruN majortom.old/Makefile majortom/Makefile
--- majortom.old/Makefile 1970-01-01 00:00:00.0 +
+++ majortom/Makefile 2013-06-25 22:40:48.039332456 +
@@ -0,0 +1,21 @@
+CXX?=c++
+
+all: example
+
+out.o: out.cpp out.h
+ $(CXX) -pthread -c -fPIC out.cpp -I. -I/usr/local/include -o out.o
+
+libout.so: out.o
+ $(CXX) -pthread -shared -fPIC out.o -o libout.so
+
+main.o: main.cpp out.h
+ $(CXX) -pthread -c -fPIC main.cpp -I. -I/usr/local/include -o main.o
+
+example: libout.so main.o
+ $(CXX) -pthread -fPIC -L. -lout main.o -o example
+
+run: example
+ @LD_LIBRARY_PATH=. ./example
+
+clean:
+ rm -f *.so example *.o *~
\ No newline at end of file
diff -x .git -ruN majortom.old/main.cpp majortom/main.cpp
--- majortom.old/main.cpp 1970-01-01 00:00:00.0 +
+++ majortom/main.cpp 2013-06-25 22:43:27.116055202 +
@@ -0,0 +1,20 @@
+#include stdio.h
+#include out.h
+
+struct Inner
+{
+Inner() {
+printf(\t Control | Inner::Inner\n);
+}
+
+~Inner() {
+printf(\t Major| Inner::~Inner\n);
+}
+};
+
+static Outer outerInstance;
+static Inner innerInstance;
+
+int main() {
+ printf(\tto |main()\n);
+}
diff -x .git -ruN majortom.old/out.cpp majortom/out.cpp
--- majortom.old/out.cpp1970-01-01 00:00:00.0 +
+++ majortom/out.cpp2013-06-25 22:42:55.188061650 +
@@ -0,0 +1,10 @@
+#include out.h
+#include stdio.h
+
+Outer::Outer() {
+printf(\tGround | Outer::Outer\n);
+}
+
+Outer::~Outer() {
+printf(\tTom| Outer::~Outer\n);
+}
diff -x .git -ruN majortom.old/out.h majortom/out.h
--- majortom.old/out.h 1970-01-01 00:00:00.0 +
+++ majortom/out.h 2013-06-25 22:25:44.817345120 +
@@ -0,0 +1,11 @@
+#ifndef OUT_H
+#define OUT_H
+
+class Outer
+{
+public:
+Outer();
+~Outer();
+};
+
+#endif
--- majortom.patch ends here ---
--
Michael Gmelin
___
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
Recent Mk/bsd.perl.mk changes (r320679)
(I am not subscribed to -ports so please keep me CC'd)
To the committers and reviewers of r320679:
http://svnweb.freebsd.org/ports?view=revisionrevision=320679
The pathing change in bsd.perl.mk has broken things quite badly for
anyone who **does not** upgrade lang/perl* but chooses to upgrade a perl
module port (ex. p5-*) -- or even reinstall an existing one. This
creates a very broken situation. The issue is 100% reproducible;
simplest method:
pkg_add -r perl (this will install perl-5.14.2_3.tbz)
svn up /usr/ports
cd /usr/ports/whatever/p5-whatever
make install
pkg_delete p5-whatever
What I'd like to know:
- Why the major.minor.patchlevel -- major.minor path change in the
first place. I have never, ever seen this done anywhere on any *IX
system I've used. Where's the justification? Was this discussed on
some perl mailing list somewhere as a new and better way? It's
essentially saying x.y.z is always going to be compatible with x.y.z+1
which is not true (particularly with XS, as I understand it). Where
was this discussed publicly?
- Why bsd.perl.mk was changed how it was, i.e. why it didn't stick with
using the major.minor.patchlevel pathing scheme by default, and if one
of the newer perl versions was used (which would warrant the user having
to uninstall their perl, thus forced to rebuild/reinstall all their p5-*
stuff anyway), use the newer pathing scheme? It could be dealt with
equivalently (pseudo-code per se) as:
if ($PERL_VERSION =~ /^5\.12\.[5-9]/
or $PERL_VERSION =~ /^5\.14\.[4-9]/
or $PERL_VERSION =~ /^5\.16\.[3-9]/) {
$use_newer_paths = 1;
}
else {
$use_newer_paths = 0;
}
The logic here could be modified (or inverted) if desired. And this
framework would only have to be left in for a little while (maybe a few
years) until all the older FreeBSD versions had been officially EOL'd.
(Remember: those using EOL'd FreeBSD versions but with ports trees
updated past that EOL date are living dangerously, as no compatibility
is guaranteed -- this has come up many times on the lists, and even
somewhat recently).
You should have seen the look on my face when I went to update
p5-Mail-SpamAssassin (and nothing else) on my system and suddenly found
it shitting the bed, forcing me to pkg_delete -af rm -fr /usr/local
and start over fresh due to leftover cruft populating /usr/local.
I say all this well aware of what ports/UPDATING said -- however the
instructions blindly make the assumption the person is building from
source or using pkg (not pkg_* tools). The versions of perl on the
official package mirrors in Latest/ do not work properly with these
changes, and those are still packages which are **actively used**
during **present-day-supported** FreeBSD installations. FreeBSD users
do expect to pkg_add -r something (which can also be done from the
installer on fresh installations), then install things from /usr/ports
with make install; this is normal and must be supported.
Something tells me this is one of those situations where if we still had
dougb@ he would have caught it in advance and yelled loudly.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: samba36-3.6.13
Hello timur, Please bump samba to 3.6.16. Thanks, dutchman ___ 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 portmaster
Hi, I noticed portmaster developed a problem after a recent update to ports-mgmt/pkg where the following appears in the output: [: false: bad number I traced it to lines in portmaster where np_orphan is set: np_orphan=`pkg query %a $upg_port` It appears 'pkg query %a' used to return 0 or 1 and now it returns 'true' or 'false'. The 'pkg help query' text says %a Returns 1 if the matched package is an orphan package and can be pkg-autoremove(1)'d, 0 otherwise I further ran into trouble with ports-mgmt/pkg-devel today where portmaster calls: pkg info pkg This fails with ports-mgmt/pkg-devel unless the line is changed to: pkg info pkg-devel This stopped portmaster from working. I reverted to using ports-mgmt/pkg to get around this. Regards, Adrian ___ 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: Recent Mk/bsd.perl.mk changes (r320679)
Hi! - Why the major.minor.patchlevel -- major.minor path change in the first place. Probably this: Currently, if the perl port is updated to the next patchlevel, one has to recompile a lot of ports. One of my reference hosts still compiles, started approx. a week ago. -- p...@opsec.eu+49 171 3101372 7 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: Recent Mk/bsd.perl.mk changes (r320679)
On Wed, Jun 26, 2013 at 06:50:51AM +0200, Kurt Jaeger wrote: Hi! - Why the major.minor.patchlevel -- major.minor path change in the first place. Probably this: Currently, if the perl port is updated to the next patchlevel, one has to recompile a lot of ports. That doesn't make any sense. An example of what we (FreeBSD users/ports) had prior to r320679: User has perl-5.12.3 installed (package or port, doesn't matter), and also some perl module (we'll call it p5-Snakes-1.00). User updates /usr/ports, and finds that lang/perl5.12 has been updated to perl 5.12.4 -- this doesn't matter in the least, nothing forces them to update to that, it's unnecessary unless the individual port mandates it (via $PERL_LEVEL). The user also sees p5-Snakes has been updated to 1.02, so the user pkg_delete/deinstalls it, make installs, and now has p5-Snakes-1.02 (fully usable) on their system. It Just Works(tm), built completely off the existing perl-5.12.3 bits. If the user wants to update to perl-5.12.4, yes, they will need to reinstall all their ports -- and justifiably so. Expanding on that: There is no reason I'd assume a.b.c would necessarily be completely compatible with a.b.c+1 or subsequent updates. The two things that come to mind with perl are perlxs and libperl.so (note that there is no .so.N versioning scheme with perl .so bits). The DBI/DBD layer comes to mind here (and that degree of breakage would really upset FreeBSD users). Perl as a language tries to be backwards-compatible as much as possible, but AFAIK this is purely a language/operational compatibility; whether or not the underlying libraries and ABI/API of the shared objects are compatible between minor revisions is an assumption -- unless someone can show me proof otherwise. But even if they can show such proof, it's not justification for the backwards-compatibility breakage in bsd.perl.mk One of my reference hosts still compiles, started approx. a week ago. I understand, but prior to r320679, you wouldn't have had to do that unless you chose to updated lang/perl5.xx. Instead, what we have *right now* is something that makes assumptions (see above paragraph) **and** breaks fresh FreeBSD installs where the person chooses to install the perl package + update /usr/ports + install a perl module from ports, **as well** as an existing system where an admin just wants to update a perl module from ports. This is for present-day supported FreeBSD versions, not EOL! I'm fine with the major.minor.patchlevel -- major.minor pathname change, **as long** as shims in bsd.perl.mk are put in place to retain use of major.minor.patchlevel paths if an older version of perl is installed on the system. Those shims were not written, and I want to know why, because as I see it we *can* have it both ways. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Recent Mk/bsd.perl.mk changes (r320679)
Hello, and first please accept my apologies for this situation. pkg_add -r perl (this will install perl-5.14.2_3.tbz) svn up /usr/ports cd /usr/ports/whatever/p5-whatever make install pkg_delete p5-whatever As I know we are never supported mixing of ports and packages. If you initially installed something from package and decide to use ports in this case better to rebuild all or stay with packages. What I'd like to know: - Why the major.minor.patchlevel -- major.minor path change in the first place. I have never, ever seen this done anywhere on any *IX system I've used. Where's the justification? Was this discussed on some perl mailing list somewhere as a new and better way? It's essentially saying x.y.z is always going to be compatible with x.y.z+1 which is not true (particularly with XS, as I understand it). Where was this discussed publicly? http://docs.freebsd.org/cgi/getmsg.cgi?fetch=26605+0+archive/2013/freebsd-perl/20130609.freebsd-perl I don't want to start yet another bikeshed here. Maybe link above will make some things more clear to you. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
