Re: pkg 1.4 freeze please test test test!
El 30/10/2014 00:09, Baptiste Daroussin escribió: On Wed, Oct 29, 2014 at 09:57:55PM +0100, Juan Ramón Molina Menor wrote: The problem I have now is that when trying to install new packages, pkg insists on being downgraded. Locking it has not helped. # pkg install vim-lite Updating FreeBSD repository catalogue... pkg: Repository FreeBSD has a wrong packagesite, need to re-create database Fetching meta.txz: 100% 944 B 0.9k/s00:01 Fetching packagesite.txz: 100%5 MB 296.7k/s00:18 Processing entries: 100% FreeBSD repository update completed. 23724 packages processed Updating FreeBSD_new_xorg repository catalogue... pkg: Repository FreeBSD_new_xorg has a wrong packagesite, need to re-create data base Fetching meta.txz: 100% 944 B 0.9k/s00:01 Fetching packagesite.txz: 100% 192 KB 196.3k/s00:01 Processing entries: 100% FreeBSD_new_xorg repository update completed. 799 packages processed New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The following 1 packages will be affected (of 0 checked): Installed packages to be DOWNGRADED: pkg: 1.4.0.a3 -> 1.3.8_3 [FreeBSD] The operation will free 8 MB. There is also that "wrong packagesite message". What am I doing wrong? # cat /etc/make.conf WITH_NEW_XORG="YES" WITH_GALLIUM="YES" WITH_PKGNG="YES" WITH_PKG=devel What version of freebsd are you on I would bet 9.1 where the bootstrap was dumb and may have created for you a bad /usr/local/etc/pkg.conf No, I’m on 10.0-RELEASE: # uname -a FreeBSD Marianne.Juan.home 10.0-RELEASE-p10 FreeBSD 10.0-RELEASE-p10 #0: Mon Oct 20 12:38:37 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 for the fact that pkg wants to be downgraded I ll track the bug. Do you have net-snmp installed? No. # pkg info net-snmp pkg: No package(s) matching net-snmp Can you host somewhere your /var/db/pkg/local.sqlite so that I can study it to discover what is causing that? Because I can't reproduce. regards, Bapt Sure: http://www.eurovertice.eu/tmp/local.sqlite Hope it helps, Juan ___ 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"
Strange failure on the build cluster: strip: ...//portsearch: File format not recognized
Hello, I am puzzled by this: ===> Generating temporary packing list /usr/bin/make -C src build install -s -o root -g wheel -m 555 src/portsearch /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin/ strip: /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin//portsearch: File format not recognized install: wait: No such file or directory *** Error code 70 Full log at: http://beefy1.isc.freebsd.org/data/10i386-default/2014-10-29_10h42m30s/logs/errors/portsearch-1.3.4.log and also below in this email. It works on my computer and I cannot reproduce this. Any idea what's going on? - Forwarded message from pkg-fall...@freebsd.org - Date: Wed, 29 Oct 2014 14:08:43 GMT From: pkg-fall...@freebsd.org To: v...@freebsd.org Cc: pkg-fall...@freebsd.org Subject: [package - 10i386-default][ports-mgmt/portsearch] Failed for portsearch-1.3.4 in stage You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: v...@freebsd.org Last committer: v...@freebsd.org Ident: $FreeBSD: head/ports-mgmt/portsearch/Makefile 371422 2014-10-24 06:31:47Z vd $ Log URL: http://beefy1.isc.freebsd.org/data/10i386-default/2014-10-29_10h42m30s/logs/portsearch-1.3.4.log Build URL: http://beefy1.isc.freebsd.org/build.html?mastername=10i386-default&build=2014-10-29_10h42m30s Log: >> Building ports-mgmt/portsearch build started at Wed Oct 29 14:08:40 UTC 2014 port directory: /usr/ports/ports-mgmt/portsearch building for: FreeBSD 10i386-default-job-21 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 i386 maintained by: v...@freebsd.org Makefile ident: $FreeBSD: head/ports-mgmt/portsearch/Makefile 371422 2014-10-24 06:31:47Z vd $ Poudriere version: 3.1-pre Host OSVERSION: 1100040 Jail OSVERSION: 1000510 ---Begin Environment--- UNAME_m=i386 UNAME_p=i386 OSVERSION=1000510 UNAME_v=FreeBSD 10.0-RELEASE-p9 UNAME_r=10.0-RELEASE-p9 BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM= MASTERMNT=/usr/local/poudriere/data/.m/10i386-default/ref PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk PKGNAME=portsearch-1.3.4 OLDPWD=/root PWD=/usr/local/poudriere/data/.m/10i386-default/ref/.p/pool MASTERNAME=10i386-default USER=root HOME=/root POUDRIERE_VERSION=3.1-pre LOCALBASE=/usr/local PACKAGE_BUILDING=yes ---End Environment--- ---Begin OPTIONS List--- ---End OPTIONS List--- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work TMPDIR="/tmp" SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work HOME=/wrkdirs/usr/ports/ports-mgmt/portsearch/work TMPDIR="/tmp" NO_PIE=yes SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR="/usr/lib" CC="cc" CFLAGS="-O2 -pipe -fno-strict-aliasing" CPP="cpp" CPPFLAGS="" LDFLAGS="" LIBS="" CXX="c++" CXXFLAGS="-O2 -pipe -fno-strict-aliasing" MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -s -o root -g wheel -m 555" BSD_INSTALL_LIB="install -s -o root -g wheel -m 444" BSD_INSTALL_SCRIPT="install -o root -g wheel -m 555" BSD_INSTALL_DATA="install -o root -g wheel -m 0644" BSD_INSTALL_MAN="install -o root -g wheel -m 444" --End MAKE_ENV-- --PLIST_SUB-- OSREL=10.0 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local PORTDOCS="" PORTEXAMPLES="" LIB32DIR=lib DOCSDIR="share/doc/portsearch" EXAMPLESDIR="share/examples/portsearch" DATADIR="share/portsearch" WWWDIR="www/portsearch" ETCDIR="etc/portsearch" --End PLIST_SUB-- --SUB_LIST-- PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/portsearch DOCSDIR=/usr/local/share/doc/portsearch EXAMPLESDIR=/usr/local/share/examples/portsearch WWWDIR=/usr/local/www/portsearch ETCDIR=/usr/local/etc/portsearch --End SUB_LIST-- ---Begin make.conf--- ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles /usr/local/etc/poudriere.d/make.conf WITH_PKGNG=yes #WITH_PKGNG=devel # clean-restricted via poudriere.conf NO_RESTRICTED #NO_RESTRICTED=yes DISABLE_MAKE_JOBS=poudriere ---End make.conf--- === ===> License BSD2CLAUSE accepted by the user === === ===> portsearch-1.3.4 depends on file: /usr/local/sbin/pkg - not found ===>Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg ===> Installing existing package /
Re: Strange failure on the build cluster: strip: ...//portsearch: File format not recognized
On Thu, Oct 30, 2014 at 09:40:51AM +0200, Vasil Dimov wrote: > Hello, > > I am puzzled by this: > > ===> Generating temporary packing list > /usr/bin/make -C src build > install -s -o root -g wheel -m 555 src/portsearch > /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin/ > strip: > /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin//portsearch: > File format not recognized > install: wait: No such file or directory > *** Error code 70 > > Full log at: > http://beefy1.isc.freebsd.org/data/10i386-default/2014-10-29_10h42m30s/logs/errors/portsearch-1.3.4.log > and also below in this email. > > It works on my computer and I cannot reproduce this. > > Any idea what's going on? Yes your distfile is unclean and comes with a prebuilt binary in src you can see on the logs that nothing is being built here: ===> Building for portsearch-1.3.4 /usr/bin/make -C src build === The targets are already satisfied. However you are doing your tests on an amd64 box and the binary in the distfiles are amd64 one do install -s which run strip(1) works as expected on any amd64 box using that precompiled binary, but beefy1 is building i386 packages so strip fails on unknown amd64 binaries. Best regards, Bapt pgppWBwX7sbsP.pgp Description: PGP signature
Re: Strange failure on the build cluster: strip: ...//portsearch: File format not recognized
On 30 October 2014 09:49, Baptiste Daroussin wrote: > On Thu, Oct 30, 2014 at 09:40:51AM +0200, Vasil Dimov wrote: [...] >> install -s -o root -g wheel -m 555 src/portsearch >> /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin/ >> strip: >> /wrkdirs/usr/ports/ports-mgmt/portsearch/work/stage/usr/local/bin//portsearch: >> File format not recognized >> install: wait: No such file or directory [...] > Yes your distfile is unclean and comes with a prebuilt binary in src [...] Oh, no! I screwed it up: /usr/ports/ports-mgmt/portsearch# make extract ... /usr/ports/ports-mgmt/portsearch# ls -l work/portsearch-1.3.4/src/portsearch -rwxr-xr-x 1 root wheel 35342 Oct 8 14:16 work/portsearch-1.3.4/src/portsearch /usr/ports/ports-mgmt/portsearch# Thanks for the quick reply! ___ 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: CFT: Update to xf86-video-ati 7.5.0
On 29.10.2014 23:01, Christian Weisgerber wrote: > Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > and re-starting the X server led to this failure: What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14.6? If that's true, then the failure is expected because xf86-video-ati 6.14.6 will have loaded the old non-KMS kernel Radeon driver (radeondrm.ko). xf86-video-ati 7.5.0 can't work this old module and failed to load the new one because they conflict. That would explain why a reboot fixed the problem: radeondrm.ko wasn't loaded anymore. -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Re: CFT: Update to xf86-video-ati 7.5.0
On 30.10.2014 00:14, Miguel Clara wrote: >> However, I see no change in the output connectors handling code in >> xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it works >> for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-ati >> 7.2.0 installed? > > It doens't work for the ati one... as I've reported in the mailing list > I've posted, but you say the connector behaviour changed in xorg-server > 1.15, so maybe I should install that version and test!? I understand that you can't use the Radeon card, but if xf86-video-ati 7.2.0 is installed, does the X server start correctly (instead of crashing, like with 7.5.0)? I suppose it does. In this case, could you please post Xorg.0.log with 7.2.0 installed? You don't need to update to xorg-server 1.15. -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Calibre: KeyError: "No plugin named u'qt_hack'" again
*Bug 183808[1]* - deskutils/calibre missing dependency py-cssutils and qt_hack
checked as
"Issue Resolved FIXED"
but!:
/usr/local/bin/ebook-convert 68876.fb2 68876.pdf
1% Конвертирую входной файл в HTML...
InputFormatPlugin: FB2 Input running
on /usr/home/alex/ALEX/down/68876.fb2
Parsing all content...
Forcing index.xhtml into XHTML namespace
Generating default TOC from spine...
34% Выполняю преобразования книги...
Merging user specified metadata...
Detecting structure...
Auto generated TOC with 684 entries.
Flattening CSS and remapping font sizes...
Source base font size is 12.0pt
Removing fake margins...
Cleaning up manifest...
Trimming unused files from manifest...
Trimming u'son_max.jpg' from manifest
Creating PDF Output...
67% Запускается плагин PDF Output
The cover image has an id != "cover". Renaming to work around bug in Nook Color
Traceback (most recent call last):
File "/usr/local/bin/ebook-convert", line 20, in
sys.exit(main())
File "/usr/local/lib/calibre/calibre/ebooks/conversion/cli.py", line 359, in
main
plumber.run()
File "/usr/local/lib/calibre/calibre/ebooks/conversion/plumber.py", line
1194, in run
self.opts, self.log)
File
"/usr/local/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line
145, in
convert
self.convert_text(oeb_book)
File
"/usr/local/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line
268, in
convert_text
'toc', None))
File
"/usr/local/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line
294, in write
writer.dump(items, out_stream, PDFMetadata(self.metadata))
File "/usr/local/lib/calibre/calibre/ebooks/pdf/render/from_html.py", line
186, in dump
mark_links=opts.pdf_mark_links)
File "/usr/local/lib/calibre/calibre/ebooks/pdf/render/engine.py", line 325,
in __init__
mark_links=mark_links)
File "/usr/local/lib/calibre/calibre/ebooks/pdf/render/engine.py", line 90,
in __init__
self.qt_hack, err = plugins['qt_hack']
File "/usr/local/lib/calibre/calibre/constants.py", line 185, in __getitem__
raise KeyError('No plugin named %r'%name)
KeyError: "No plugin named u'qt_hack'"
calibre-1.48.0
FreeBSD amd64 10.1-PRERELEASE #12 r273822: Wed Oct 29 21:51:28 KRAT 2014
--
-
Alex V. Petrov
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183808
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ misc/freeguide | 0.11| 0.11.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes
Hi. I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in /etc/src.conf ryby20 port throw this error: ... checking for valgrind/memcheck.h... no checking for strip... strip configure: error: dtrace(1) is missing ===> Script "configure" failed unexpectedly. I see you have sophisticated check depending on OS version for CONFIGURE_ARGS+=--enable-dtrace IMHO, it should be replaced to test dtrace binary presence instead. -- http://ache.vniz.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"
Re: Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes
On Thu, Oct 30, 2014 at 01:11:33PM +0300, Andrey Chernov wrote: > Hi. > I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in > /etc/src.conf > ryby20 port throw this error: > ... > checking for valgrind/memcheck.h... no > checking for strip... strip > configure: error: dtrace(1) is missing > ===> Script "configure" failed unexpectedly. > > I see you have sophisticated check depending on OS version for > CONFIGURE_ARGS+=--enable-dtrace > IMHO, it should be replaced to test dtrace binary presence instead. > To be previse the port should not care about WITHOUT_CDDL :) but it should detect if the host has dtrace or note, probably a .if exists(/usr/sbin/dtrace) CONFIGURE_ARGS+= --enable-dtrace .endif Should do the trick (to be tested of course :) regards, Bapt pgpzLHlAfIo7E.pgp Description: PGP signature
Re: Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes
On 30.10.2014 13:17, Baptiste Daroussin wrote: > On Thu, Oct 30, 2014 at 01:11:33PM +0300, Andrey Chernov wrote: >> Hi. >> I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in >> /etc/src.conf >> ryby20 port throw this error: >> ... >> checking for valgrind/memcheck.h... no >> checking for strip... strip >> configure: error: dtrace(1) is missing >> ===> Script "configure" failed unexpectedly. >> >> I see you have sophisticated check depending on OS version for >> CONFIGURE_ARGS+=--enable-dtrace >> IMHO, it should be replaced to test dtrace binary presence instead. >> > > To be previse the port should not care about WITHOUT_CDDL :) but it should > detect if the host has dtrace or note, probably a > .if exists(/usr/sbin/dtrace) > CONFIGURE_ARGS+= --enable-dtrace > .endif > > Should do the trick (to be tested of course :) Yes, the thing .if exists(/usr/sbin/dtrace) CONFIGURE_ARGS+=--enable-dtrace .else CONFIGURE_ARGS+=--disable-dtrace .endif works (at least for no dtrace case) -- http://ache.vniz.net/ signature.asc Description: OpenPGP digital signature
courier-authdaemond supposedly not running
Hey all, wondering if anyone else's noticed this? After an upgrade courier-authdaemond starts fine, but the startup script then claims it isn't running. The script itself seems fine, and: # /usr/local/etc/rc.d/courier-authdaemond status courier_authdaemond is not running. # cat /var/run/authdaemond/pid 1348 # ps 1348 PID TT STAT TIME COMMAND 1348 10 I 0:00.00 /usr/local/sbin/courierlogger -facility=mail -pid=/var/run/authdaemond/pid -start /usr/local/libexec/courier-authlib/authdaemond # ps | grep authdaemond 1348 10- I 0:00.00 /usr/local/sbin/courierlogger -facility=mail -pid=/var/run/authdaemond/pid -start /usr/local/libexec/courier-authlib/authdaemond 1349 10- I 0:00.00 /usr/local/libexec/courier-authlib/authdaemond 1350 10- S 0:00.00 /usr/local/libexec/courier-authlib/authdaemond 1351 10- S 0:00.00 /usr/local/libexec/courier-authlib/authdaemond 1352 10- S 0:00.00 /usr/local/libexec/courier-authlib/authdaemond 1353 10- I 0:00.00 /usr/local/libexec/courier-authlib/authdaemond 1354 10- I 0:00.00 /usr/local/libexec/courier-authlib/authdaemond ___ 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: CFT: Update to xf86-video-ati 7.5.0
On Thu, Oct 30, 2014 at 8:17 AM, Jean-Sébastien Pédron wrote: > On 30.10.2014 00:14, Miguel Clara wrote: > >> However, I see no change in the output connectors handling code in > >> xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it works > >> for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-ati > >> 7.2.0 installed? > > > > It doens't work for the ati one... as I've reported in the mailing list > > I've posted, but you say the connector behaviour changed in xorg-server > > 1.15, so maybe I should install that version and test!? > > I understand that you can't use the Radeon card, but if xf86-video-ati > 7.2.0 is installed, does the X server start correctly (instead of > crashing, like with 7.5.0)? I suppose it does. In this case, could you > please post Xorg.0.log with 7.2.0 installed? > > You don't need to update to xorg-server 1.15. > Ah I see now, I misunderstood what you meant the first time. Would pkg remove -f xf86-video-ati, and pkg install xf86-video-ati (since its the 7.2 package version) be enough or do I need to reinstall xorg-server from pkg to make sure dependencies are linked properly? Fro the record, with just remove 7.5 and install 7.2 I get this in gdb: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 2014 (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [New Thread 803406400 (LWP 101070/Xorg)] (II) [KMS] Kernel modesetting enabled. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 803406400 (LWP 101070/Xorg)] 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at xf86Crtc.c:1829 1829xf86Crtc.c: No such file or directory. in xf86Crtc.c Current language: auto; currently minimal (gdb) bt #0 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at xf86Crtc.c:1829 #1 0x004eb1ea in xf86SetScrnInfoModes (scrn=0x803512400) at xf86Crtc.c:1843 #2 0x004ebf13 in xf86InitialConfiguration (scrn=0x803512400, canGrow=1) at xf86Crtc.c:2503 #3 0x0008047234a7 in ?? () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #4 0x00080472090b in ?? () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #5 0x004a4e19 in InitOutput (pScreenInfo=0x8acdb0, argc=1, argv=0x7fffead8) at xf86Init.c:586 #6 0x00424c66 in main (argc=1, argv=0x7fffead8, envp=0x7fffeae8) at main.c:203 Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log > -- > Jean-Sébastien Pédron > > ___ 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: CFT: Update to xf86-video-ati 7.5.0
Jean-Sébastien Pédron: > > Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > > and re-starting the X server led to this failure: > > What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14.6? No, just the instance I had running before: X server 1.12.4 and xf86-video-ati 7.2.0. -- 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"
Re: pkgng "requirements" script equivalent
On Wed, Oct 29, 2014 at 5:44 PM, Baptiste Daroussin wrote: > On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote: > > On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin > > wrote: > > > > > On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote: > > > > Hello, > > > > > > > > I am in the process of upgrading some proprietary software that has > > > always > > > > been deployed via a "custom" package created by the old pkg_create. > So > > > far > > > > I've been able to use "pkg create" to achieve what I want, but it > seems > > > > that the "requirements" script is no longer a part of the new pkg > > > > framework. This used to be a script that you could include with a > package > > > > that could halt the pkg add or remove process by returning a non-zero > > > exit > > > > code from the script. I've been using it with the old pkg tools as a > way > > > to > > > > enforce some proprietary requirements logic that goes beyond > requiring > > > > certain pkg dependencies, architecture, etc. One example is to make > sure > > > a > > > > specific custom kernel is running by analyzing uname output. > > > > > > > > I am wondering if anyone has a suggestion as to how to interrupt the > pkg > > > > add process in a similar way. It looks like the "requirements" > script has > > > > been removed entirely, and from what I can tell a failure in the > > > > pre-install script does not halt pkg add. > > > > > > What is the requirement script you are speaking about? I never heard > of it? > > > > > > > man pkg_create(1) > > > https://www.freebsd.org/cgi/man.cgi?query=pkg_create&apropos=0&sektion=1&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html > > -r rscript > > Set rscript to be the ``requirements'' procedure for the package. > > This can be any executable program (or shell script). It will be > > invoked automatically at installation/deinstallation time to > > determine whether or not installation/deinstallation should pro- > > ceed. To differentiate between installation and deinstallation, > > the keywords INSTALL and DEINSTALL are passed respectively, along > > with the package's name. > > > > > > > Explain me in detail the way you were producing the package with > > > pkg_create and > > > I'll explain you how to do the same with pkg(8). > > > > > > > I was running pkg_create with the following arguments: > > > > pkg_create -f plistfile -c -'comment' -d -description' -v -P 'list of > > dependency packages' -v -r requirements_script_file -i > > pre-install_script_file -I post-install-script_file -k > > pre-deinstall_script_file -K post-deinstall_script_file -s > > /space/build/trunk -D displayfile -p /space/rxg -o category/name pkg.tbz > > > > For the most part I've figured out the appropriate +MANIFEST file and > > manifest directory contents, except for the "requirements procedure" > script. > > > > Ok requirements are gone, and you have a perfectly justified use case, I > will > readd such functionnality as soon as I can when dealing with binary > upgrade it > is basically a wrong idea to fail the procedure because a script fails so > I need > to add the notion of trigger and run the requirements prior the procedure. > > Might be complicated to add but it is for sure something we need. > > I cannot promise anything for pkg 1.4 which is in freeze time but I'll try > to > see what I can do. > Yeah that is what I suspected. I will probably find a way to accomplish what I am doing some other way (i.e., outside of pkg), as I am trying to get this working for upcoming 10.1-RELEASE. However it would be nice to have a requirements procedure again sometime in the future. Thanks! > 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 "requirements" script equivalent
On Thu, Oct 30, 2014 at 07:52:51AM -0700, Nick Rogers wrote: > On Wed, Oct 29, 2014 at 5:44 PM, Baptiste Daroussin > wrote: > > > On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote: > > > On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin > > > wrote: > > > > > > > On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote: > > > > > Hello, > > > > > > > > > > I am in the process of upgrading some proprietary software that has > > > > always > > > > > been deployed via a "custom" package created by the old pkg_create. > > So > > > > far > > > > > I've been able to use "pkg create" to achieve what I want, but it > > seems > > > > > that the "requirements" script is no longer a part of the new pkg > > > > > framework. This used to be a script that you could include with a > > package > > > > > that could halt the pkg add or remove process by returning a non-zero > > > > exit > > > > > code from the script. I've been using it with the old pkg tools as a > > way > > > > to > > > > > enforce some proprietary requirements logic that goes beyond > > requiring > > > > > certain pkg dependencies, architecture, etc. One example is to make > > sure > > > > a > > > > > specific custom kernel is running by analyzing uname output. > > > > > > > > > > I am wondering if anyone has a suggestion as to how to interrupt the > > pkg > > > > > add process in a similar way. It looks like the "requirements" > > script has > > > > > been removed entirely, and from what I can tell a failure in the > > > > > pre-install script does not halt pkg add. > > > > > > > > What is the requirement script you are speaking about? I never heard > > of it? > > > > > > > > > > man pkg_create(1) > > > > > https://www.freebsd.org/cgi/man.cgi?query=pkg_create&apropos=0&sektion=1&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html > > > -r rscript > > > Set rscript to be the ``requirements'' procedure for the package. > > > This can be any executable program (or shell script). It will be > > > invoked automatically at installation/deinstallation time to > > > determine whether or not installation/deinstallation should pro- > > > ceed. To differentiate between installation and deinstallation, > > > the keywords INSTALL and DEINSTALL are passed respectively, along > > > with the package's name. > > > > > > > > > > Explain me in detail the way you were producing the package with > > > > pkg_create and > > > > I'll explain you how to do the same with pkg(8). > > > > > > > > > > I was running pkg_create with the following arguments: > > > > > > pkg_create -f plistfile -c -'comment' -d -description' -v -P 'list of > > > dependency packages' -v -r requirements_script_file -i > > > pre-install_script_file -I post-install-script_file -k > > > pre-deinstall_script_file -K post-deinstall_script_file -s > > > /space/build/trunk -D displayfile -p /space/rxg -o category/name pkg.tbz > > > > > > For the most part I've figured out the appropriate +MANIFEST file and > > > manifest directory contents, except for the "requirements procedure" > > script. > > > > > > > Ok requirements are gone, and you have a perfectly justified use case, I > > will > > readd such functionnality as soon as I can when dealing with binary > > upgrade it > > is basically a wrong idea to fail the procedure because a script fails so > > I need > > to add the notion of trigger and run the requirements prior the procedure. > > > > Might be complicated to add but it is for sure something we need. > > > > I cannot promise anything for pkg 1.4 which is in freeze time but I'll try > > to > > see what I can do. > > > > Yeah that is what I suspected. I will probably find a way to accomplish > what I am doing some other way (i.e., outside of pkg), as I am trying to > get this working for upcoming 10.1-RELEASE. However it would be nice to > have a requirements procedure again sometime in the future. Thanks! > I have added it in my TODO list and will push it in priority. Regards, Bapt pgp8as5qZTV8Q.pgp Description: PGP signature
Re: Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes
On Thu, Oct 30, 2014 at 01:26:02PM +0300, Andrey Chernov wrote: > On 30.10.2014 13:17, Baptiste Daroussin wrote: > > On Thu, Oct 30, 2014 at 01:11:33PM +0300, Andrey Chernov wrote: > >> Hi. > >> I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in > >> /etc/src.conf > >> ryby20 port throw this error: > >> ... > >> checking for valgrind/memcheck.h... no > >> checking for strip... strip > >> configure: error: dtrace(1) is missing > >> ===> Script "configure" failed unexpectedly. > >> > >> I see you have sophisticated check depending on OS version for > >> CONFIGURE_ARGS+=--enable-dtrace > >> IMHO, it should be replaced to test dtrace binary presence instead. > >> > > > > To be previse the port should not care about WITHOUT_CDDL :) but it should > > detect if the host has dtrace or note, probably a > > .if exists(/usr/sbin/dtrace) > > CONFIGURE_ARGS+= --enable-dtrace > > .endif > > > > Should do the trick (to be tested of course :) > > Yes, the thing > .if exists(/usr/sbin/dtrace) > CONFIGURE_ARGS+=--enable-dtrace > .else > CONFIGURE_ARGS+=--disable-dtrace > .endif > works (at least for no dtrace case) The checks for OS version weren't meant to detect presence of dtrace, they were meant to detect presence of dtrace with usable USDT. Unfortunately, presence of /usr/sbin/dtrace doesn't necessarily mean USDT works. So, both checks need to be there. I'll take a look when I can, but if someone else gets there first, great. Steve ___ 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 1.4.0.alpha3 - pkg: pkg_repo_fetch_remote_mmap(cannot mmap fetched): Invalid argument / Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file pkg_solve.c, line 537.
Hello:
Errors shown toward end of email.
Note this is a cleanly installed jail but an previously built repository
from an older
version of head. I can nuke the head repository and rebuild from
scratch but I wanted to
present these errors first.
--mikej
FreeBSD bsd11 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r273857: Thu Oct 30
08:50:37 EDT 2014
mikej@bsd11:/usr/obj/usr/src/sys/GENERIC amd64
JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
10stable 10.1-PRERELEASE r273580 amd64 svn2014-10-24 11:10:51
/usr/local/poudriere/jails/10stable
head 11.0-CURRENT r273858amd64 svn2014-10-30 10:45:31
/usr/local/poudriere/jails/head
9stable 9.2-STABLE amd64 svn
/usr/local/poudriere/jails/9stable
9stable32 9.2-STABLE i386 ftp
/usr/local/poudriere/jails/9stable32
root@bsd11:~ # pkg -vv
Version : 1.4.0.alpha3
PKG_DBDIR = "/var/db/pkg";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-11";
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
"/etc/pkg/",
"/usr/local/etc/pkg/repos/",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = true;
ABI = "FreeBSD:11:amd64";
ALTABI = "freebsd:11:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.bz2";;
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = "";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
AUTOMERGE = true;
Repositories:
myrepo: {
url :
"File:///usr/local/poudriere/data/packages/head-default",
enabled : yes
}
FreeBSD_ssp: {
url : "pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/ssp";,
enabled : yes,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
root@bsd11:~ #
And here execution from the console:
root@bsd11:/usr/local/poudriere/data/packages # rm -r head-default/
root@bsd11:/usr/local/poudriere/data/packages # cd
root@bsd11:~ # poudriere bulk -j head archivers/arc
[00:00:00] >> Creating the reference jail... done
[00:00:00] >> Mounting system devices for head-default
[00:00:00] >> Mounting ports/packages/distfiles
[00:00:00] >> Converting package repository to new format
[00:00:00] >> Stashing existing package repository
[00:00:00] >> Mounting ccache from: /var/cache/ccache
[00:00:00] >> Mounting packages from:
/usr/local/poudriere/data/packages/head-default
[00:00:00] >> Mounting /var/db/ports from:
/usr/local/etc/poudriere.d/options
[00:00:00] >> Appending to make.conf:
/usr/local/etc/poudriere.d/head-make.conf
/etc/resolv.conf ->
/usr/local/poudriere/data/.m/head-default/ref/etc/resolv.conf
[00:00:00] >> Starting jail head-default
[00:00:01] >> Logs:
/usr/local/poudriere/data/logs/bulk/head-default/2014-10-30_11h12m11s
[00:00:01] >> Loading MOVED
[00:00:01] >> Calculating ports order and dependencies
[00:00:01] >> pkg package missing, skipping sanity
[00:00:01] >> Skipping incremental rebuild and repository sanity
checks
[00:00:01] >> Cleaning the build queue
[00:00:01] >> Recording filesystem state for prepkg... done
[00:00:03] >> Building 3 packages using 3 builders
[00:00:03] >> Starting/Cloning builders
[00:00:03] >> Hit CTRL+t at any time to see build progress and stats
[00:00:03] >> [01][00:00:00] Starting build of ports-mgmt/pkg
[00:01:10] >> [01][00:01:07] Finished build of ports-mgmt/pkg:
Success
[00:01:11] >> [01][00:00:00] Starting build of devel/ccache
[00:01:19] >> [01][00:00:08] Finished build of devel/ccache: Success
[00:01:20] >> [01][00:00:00] Starting build of archivers/arc
[00:01:25] >> [01][00:00:05] Finished build of archivers/arc:
Success
[00:01:26] >> Stopping 3 builders
[00:01:27] >> Creating pkgng repository
Creating repository in /tmp/packages: 100%
Packing files for repository: 100%
[00:01:29] >> Committing packages to repository
[00:01:29] >> Removing old packages
[00:01:29] >> Built ports: ports-mgmt/pkg devel/ccache archivers/arc
[head-default] [2014-10-30_11h12m11s] [committing:] Queued: 3 Built: 3
Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 0 Time: 00:01:28
[00:01:29] >> Logs:
/usr/local/poudriere/data/logs/bulk/head-default/2014-10-30_11h12m11s
[00:01:29] >> Cleaning up
[00:01:29] >> Umounting file systems
root@bsd11:~ #
root@bsd11:~ # p
Re: CFT: Update to xf86-video-ati 7.5.0
On 30.10.2014 14:21, Miguel Clara wrote: > Fro the record, with just remove 7.5 and install 7.2 I get this in gdb: > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 2014 > (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d" > (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" > [New Thread 803406400 (LWP 101070/Xorg)] > (II) [KMS] Kernel modesetting enabled. > > Program received signal SIGSEGV, Segmentation fault. > (...) > (gdb) bt > #0 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at > xf86Crtc.c:1829 > (...) > > Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log Ok, so the problem is exactly the same with either 7.2.0 and 7.5.0. I "prefer" that, because I didn't see the difference between both versions in this particular code :) We'll add the fix from xserver 1.15 in our xorg-server port, it should fix that crash. What I don't understand is how could this could work before. Are you sure you had xf86-video-ati 7.2.0 installed? Can you check your logs (/var/log/messages) and look for lines like these: pkg-static: pkg-1.3.8_3 deinstalled pkg-static: pkg-1.4.0.a3 installed The program could be "pkg" or "pkg-static". And it should say that a package was installed/deinstalled/upgraded, with the version of the package. Can you check the first time you installed xf86-video-ati 7.5.0 if it actually replaced 7.2.0 or something else? -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Re: CFT: Update to xf86-video-ati 7.5.0
On 30.10.2014 14:31, Christian Weisgerber wrote: > Jean-Sébastien Pédron: > >>> Well, terminating the old X server, updating xf86-video-ati to 7.5.0, >>> and re-starting the X server led to this failure: >> >> What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14.6? > > No, just the instance I had running before: X server 1.12.4 and > xf86-video-ati 7.2.0. Ok. Does the problem still happen now? -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Re: pkg 1.4.0.alpha3 - pkg: pkg_repo_fetch_remote_mmap(cannot mmap fetched): Invalid argument / Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file pkg_solve.c, line 537.
On Thu, Oct 30, 2014 at 12:53:29PM -0400, Michael Jung wrote: > Hello: > > Errors shown toward end of email. > > Note this is a cleanly installed jail but an previously built repository > from an older > version of head. I can nuke the head repository and rebuild from > scratch but I wanted to > present these errors first. Can you try alpha4 before nuking the head repository? regards, Bapt pgpGX8lftbaWF.pgp Description: PGP signature
Re: pkg2ng question -- fails to show converted pkgs in stats
TOP POSTED SORRY Moot point on this machine, vs others , probably; also, part of the message below was wrong. they are only installed if desinstalling from the port subdirectory and not thru package IIRC WORKAROUND: meanwhile I copied a local.sqlite from a more recent machine to the failed pkg2ng one and pkg delete -n -g "a*" | grep -v requested | grep -v operation | grep -v REMO| grep -v Reinstall | xargs -J % pkg install -f % "dry runs" the a* reinstalls, and -y after -f actually performs... takes much longer though , tuning for disk space, ... unwanted reinstalls... etc On Thu, 10/30/14, Jeffrey Bouquet via freebsd-pkg wrote: Subject: pkg2ng question -- fails to show converted pkgs in stats To: p...@freebsd.org Date: Thursday, October 30, 2014, 5:48 AM v9 pkg2ng converts, the local.sqlite is huge... but pkg stats ... no installed packages. If one wants to desintall them, they are installed... if one wants to install them, they are not installed yet, whereas they were converted so are... Some other command to run maybe? Or pkg2ng is not just not reliable yet? ___ freebsd-...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-pkg To unsubscribe, send any mail to "freebsd-pkg-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg 1.4.0.alpha3 - pkg: pkg_repo_fetch_remote_mmap(cannot mmap fetched): Invalid argument / Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file pkg_solve.c, line 537.
On 2014-10-30 13:10, Baptiste Daroussin wrote: On Thu, Oct 30, 2014 at 12:53:29PM -0400, Michael Jung wrote: Hello: Errors shown toward end of email. Note this is a cleanly installed jail but an previously built repository from an older version of head. I can nuke the head repository and rebuild from scratch but I wanted to present these errors first. Can you try alpha4 before nuking the head repository? regards, Bapt Ok, I built archivers/zoo, pkg update and pkg install. Looks ok know. I'll let it build my pkg list for head/10/9 with a few new packages and report back it I see any problems. --mikej root@bsd11:/usr/ports/ports-mgmt/pkg-devel # make reinstall root@bsd11:~ # pkg -v 1.4.0.alpha4 root@bsd11:~ # root@bsd11:~ # poudriere bulk -j head archivers/zoo [00:00:00] >> Creating the reference jail... done [00:00:00] >> Mounting system devices for head-default [00:00:00] >> Mounting ports/packages/distfiles [00:00:00] >> Stashing existing package repository [00:00:00] >> Mounting ccache from: /var/cache/ccache [00:00:00] >> Mounting packages from: /usr/local/poudriere/data/packages/head-default [00:00:00] >> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options [00:00:00] >> Appending to make.conf: /usr/local/etc/poudriere.d/head-make.conf /etc/resolv.conf -> /usr/local/poudriere/data/.m/head-default/ref/etc/resolv.conf [00:00:00] >> Starting jail head-default [00:00:00] >> Logs: /usr/local/poudriere/data/logs/bulk/head-default/2014-10-30_14h33m25s [00:00:00] >> Loading MOVED [00:00:01] >> Calculating ports order and dependencies [00:00:01] >> Sanity checking the repository [00:00:01] >> Checking packages for incremental rebuild needed [00:00:02] >> Deleting stale symlinks [00:00:02] >> Deleting empty directories [00:00:02] >> Cleaning the build queue [00:00:02] >> Recording filesystem state for prepkg... done [00:00:03] >> Building 1 packages using 1 builders [00:00:03] >> Starting/Cloning builders [00:00:03] >> Hit CTRL+t at any time to see build progress and stats [00:00:03] >> [01][00:00:00] Starting build of archivers/zoo [00:00:17] >> [01][00:00:14] Finished build of archivers/zoo: Success [00:00:18] >> Stopping 1 builders [00:00:18] >> Creating pkgng repository Creating repository in /tmp/packages: 100% Packing files for repository: 100% [00:00:19] >> Committing packages to repository [00:00:19] >> Removing old packages [00:00:19] >> Built ports: archivers/zoo [head-default] [2014-10-30_14h33m25s] [committing:] Queued: 1 Built: 1 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 0 Time: 00:00:20 [00:00:20] >> Logs: /usr/local/poudriere/data/logs/bulk/head-default/2014-10-30_14h33m25s [00:00:20] >> Cleaning up [00:00:20] >> Umounting file systems root@bsd11:~ # root@bsd11:~ # pkg update Updating myrepo repository catalogue... Fetching meta.txz: 100% 264 B 0.3k/s00:01 Fetching packagesite.txz: 100%2 KB 1.6k/s00:01 Processing entries: 100% myrepo repository update completed. 4 packages processed Updating FreeBSD_ssp repository catalogue... FreeBSD_ssp repository is up-to-date. root@bsd11:~ # pkg install zoo Updating myrepo repository catalogue... myrepo repository is up-to-date. Updating FreeBSD_ssp repository catalogue... FreeBSD_ssp repository is up-to-date. All repositories are up-to-date. Updating database digests format: 100% The following 1 packages will be affected (of 0 checked): New packages to be INSTALLED: zoo: 2.10.1_3 [myrepo] The process will require 112 KB more space. 56 KB to be downloaded. Proceed with this action? [y/N]: y Checking integrity... done (0 conflicting) [1/1] Installing zoo-2.10.1_3... [1/1] Extracting zoo-2.10.1_3: 100% root@bsd11:~ # ___ 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"
A script to locate outdated, unmaintained ports on your machine
Hi all, one of the questions I ask myself from time to time is "Which umaintained ports that have upstream updates available live on my machine?". Knowing the answer might lead to the adoption and update of some orphaned ports. To answer this question for myself I hacked a simple shell script perusing the 'pkg query' command and scraping portscout.freebsd.org. Please feel free to take a look, test and comment. I hope somebody will find it useful. https://github.com/blabber/lps Best regards, Tobias pgpU9ElDsz5Ep.pgp Description: PGP signature
Re: CFT: Update to xf86-video-ati 7.5.0
Jean-Sébastien Pédron: > >>> Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > >>> and re-starting the X server led to this failure: > >> > >> What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati > >> 6.14.6? > > > > No, just the instance I had running before: X server 1.12.4 and > > xf86-video-ati 7.2.0. > > Ok. Does the problem still happen now? What do you mean? Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was a one-time event. -- 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"
FreeBSD Port: zabbix
Hi! Is there a change that there will be an upgrade to Zabbix to the 2.4 version or later? I see that ports/pkgs has 2.0 and 2.2. Thank you, it's most appreciated. P. ___ 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: CFT: Update to xf86-video-ati 7.5.0
On Thu, Oct 30, 2014 at 5:08 PM, Jean-Sébastien Pédron wrote: > On 30.10.2014 14:21, Miguel Clara wrote: > > Fro the record, with just remove 7.5 and install 7.2 I get this in gdb: > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 2014 > > (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d" > > (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" > > [New Thread 803406400 (LWP 101070/Xorg)] > > (II) [KMS] Kernel modesetting enabled. > > > > Program received signal SIGSEGV, Segmentation fault. > > (...) > > (gdb) bt > > #0 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at > > xf86Crtc.c:1829 > > (...) > > > > Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log > > Ok, so the problem is exactly the same with either 7.2.0 and 7.5.0. I > "prefer" that, because I didn't see the difference between both versions > in this particular code :) > > We'll add the fix from xserver 1.15 in our xorg-server port, it should > fix that crash. > > What I don't understand is how could this could work before. Are you > sure you had xf86-video-ati 7.2.0 installed? Can you check your logs > (/var/log/messages) and look for lines like these: > pkg-static: pkg-1.3.8_3 deinstalled > pkg-static: pkg-1.4.0.a3 installed > > The program could be "pkg" or "pkg-static". And it should say that a > package was installed/deinstalled/upgraded, with the version of the > package. Can you check the first time you installed xf86-video-ati 7.5.0 > if it actually replaced 7.2.0 or something else? > > [miguelc@hpbsd]~% cat /var/log/messages | grep xf86 Oct 28 18:09:38 hpbsd pkg-static: xf86-video-ati-7.5.0 deinstalled Oct 28 18:09:39 hpbsd pkg-static: xf86-video-ati-7.5.0 installed Oct 30 14:09:33 hpbsd pkg: xf86-video-ati-7.5.0 deinstalled Oct 30 14:09:54 hpbsd pkg: xf86-video-ati-7.2.0_4 installed [miguelc@hpbsd]~% bzcat /var/log/messages.1.bz2 | grep xf86 Oct 27 13:58:24 hpbsd pkg: xf86-video-ati-7.2.0_4 deinstalled Oct 27 13:58:24 hpbsd pkg-static: xf86-video-ati-7.5.0 installed However I don't understand why you say "it worked before" cause what I've reported before and now is that It didn't work (with ATI) I still have the old xorg log, from back when I reported this in the list, if I'm not mistaken this is the one: http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log So It was not working with ATI even before 7.2,a and with 7.2 I also can't get xorg to start, although I was getting a black screen at some point, but the log states Xorg crashed! maybe in this new report I've somehow gave the impression that It worked, but I only works with the Intel card! Or, I'm not getting what you mean by "it worked" :P -- > Jean-Sébastien Pédron > > ___ 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"
