pkg check -s -a output unusable/incomplete
Hi, today it occured to me due some power outage or something unexpected like that caused filesystem breakage. fsck with journal was not able to repair damage and the result was repeated restart. It is a virtual machine on HyperV hypervisor, by the way, but that is irrelevant to the problem I like to report and ask for solution if known or some hints. Basically, there are 91 ports/packages installed, everything works normally well. Then, issuing command 'pkg check -s -a' to find damages I was able to identify package, p5-Locale-gettext-1.05_4, as one with some damage to its files, but no more clue thereafter, that's what I got: # pkg check -s -a Checking all packages: 2% pkg: pkg_create_from_dir(lstat failed): No such file or directory Checking all packages: 24% pkg: pkg_create_from_dir(lstat failed): No such file or directory Checking all packages: 100% # I knew I needed to rebuild/reinstall asterisk (some modules were not able to load, which manifests itself clearly so is easily identifiable), after that, the same command's output somewhat changed: # pkg check -s -a Checking all packages: 24% pkg: pkg_create_from_dir(lstat failed): No such file or directory Checking all packages: 100% # and no idea now which package needs reinstall. Any idea on this one? There is no indication which file does not exist (and should, it would not be checked for in the first place if that's not the case) nor package name which should be reinstalled in order to fix the issue. Regards, Milan ___ 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/floatator | 0.2.1 | 0.5.0 +-+ 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
Re: pkg check -s -a output unusable/incomplete
On 07/12/14 09:38, Milan Obuch wrote: # pkg check -s -a Checking all packages: 24% pkg: pkg_create_from_dir(lstat failed): No such file or directory Checking all packages: 100% # and no idea now which package needs reinstall. Agreed. One need to use verbose output to identifiy the problem. Xav -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer ___ 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 check -s -a output unusable/incomplete
On Sun, 07 Dec 2014 11:43:24 +0100 Xavier xav...@groumpf.org wrote: On 07/12/14 09:38, Milan Obuch wrote: # pkg check -s -a Checking all packages: 24% pkg: pkg_create_from_dir(lstat failed): No such file or directory Checking all packages: 100% # and no idea now which package needs reinstall. Agreed. One need to use verbose output to identifiy the problem. Xav Thanks, 'pkg check -s -a -v' gives a clue here: [23/91] Checking gettext-tools-0.19.3: checksums...pkg: pkg_create_from_dir(lstat failed): No such file or directory Rebuilding/reinstalling gettext-tools-0.19.3 makes a clean check now. Anyway, in such an anomaly case, I would prefer message in non verbose check to include package name, at least. Regards, Milan ___ 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
dirmngr-1.1.0_12 conflicts with gnupg-2.1.0_1 (installs files into the same place)
I just updated, or rather tried to update the gnupg port. it failed with a message that it conflicts with the dirmngr port. I deleted that port and then preceded to install GNUPG. When I attempted to re-install the dirmngr port, it issued this error message: dirmngr-1.1.0_12 conflicts with gnupg-2.1.0_1 (installs files into the same place) Is this expected behavior or is the some other problem at play here? I did not see anything in the UPDATING file regarding this. -- Carmel ___ 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: emulators/linux_base-c6 and x11/nvidia-driver conflict
On Fri, Mar 07, 2014 at 01:45:38PM +, Alexey Dokuchaev wrote: On Fri, Mar 07, 2014 at 01:58:49PM +0100, Ren? Ladan wrote: I noticed that linux_base-c6 and nvidia-driver conflict when one selects the LINUX option in nvidia-driver (default on). The culprit is /compat/linux/usr/lib/libGL.so.1, which is a symbolic link to libGL.so.331.49 (nvidia-driver) and libGL.so.1.2.0 (linux_base-c6). nvidia-driver does indeed have a problem with conflicting libraries (not to mendion new recently added ones: EGL|eglcore|GLESv|glsi that even do not have properly registered CONFLICTS. It's on my list, but quite frankly I've not made my mind yet how to resolve them in the least obstructive way. :( Any estimate or idea of when this may be fixed? For now I've turned off Linux compatibility support in the nvidia-driver, but I don't know what that disables and would rather not have to do that. Bob -- Bob Willcox| He who foresees calamities suffers them twice over. b...@immure.com | Austin, TX | ___ 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: dirmngr-1.1.0_12 conflicts with gnupg-2.1.0_1 (installs files into the same place)
Carmel NY wrote: I just updated, or rather tried to update the gnupg port. it failed with a message that it conflicts with the dirmngr port. We're aware of it: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=526796+0+archive/2014/freebsd-ports/20141130.freebsd-ports But you might want to read the entire thread, it's only a couple of messages anyway. HTH, AvW -- Imbibo, ergo sum. pgp4bvVVFTkvL.pgp Description: PGP signature
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: biology/boinc-simap description:Similarity Matrix of Proteins project for BOINC maintainer: po...@freebsd.org deprecated because: Project shutting down, see http://boincsimap.org/boincsimap/forum_thread.php?id=88 expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=boinc-simap portname: devel/preps-gui description:Problem reporting system maintainer: po...@freebsd.org status: BROKEN deprecated because: upstream disappeared expiration date:2014-12-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=preps-gui portname: devel/prepstools description:Problem reporting system maintainer: po...@freebsd.org status: BROKEN deprecated because: upstream disappeared expiration date:2014-12-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=prepstools portname: ports-mgmt/portcheckout description:Checkout and build ports and all depending ports maintainer: po...@freebsd.org deprecated because: Uses ports cvs repo, which is long gone expiration date:2015-01-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ports-mgmtportname=portcheckout portname: science/mpb description:MIT Photonic-Bands maintainer: po...@freebsd.org status: BROKEN deprecated because: Broken for more than 6 months expiration date:2014-12-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=scienceportname=mpb portname: www/squid33 description:HTTP Caching Proxy maintainer: po...@freebsd.org deprecated because: Reached EOL on 28 August 2014, use www/squid (v3.4) instead expiration date:2015-01-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=squid33 ___ 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 which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: biology/boinc-simap description:Similarity Matrix of Proteins project for BOINC maintainer: po...@freebsd.org deprecated because: Project shutting down, see http://boincsimap.org/boincsimap/forum_thread.php?id=88 expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=boinc-simap portname: databases/db48 description:The Berkeley DB package, revision 4.8 maintainer: mand...@freebsd.org deprecated because: Please migrate to db5 or db6 expiration date:2015-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=db48 portname: devel/cedet description:Collection of Emacs Development Environment Tools maintainer: m...@freebsd.org status: BROKEN deprecated because: Fails to build, use Emacs' builtin cedet package instead expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=cedet portname: devel/ecb description:Emacs Code Browser maintainer: m...@freebsd.org status: BROKEN deprecated because: does not work with newer Emacs versions, use the elpa package instead expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ecb portname: devel/ocaml-equeue description:The Equeue library for OCaml maintainer: michip...@gmail.com deprecated because: Superseded by www/ocaml-net expiration date:2015-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ocaml-equeue portname: devel/preps-gui description:Problem reporting system maintainer: po...@freebsd.org status: BROKEN deprecated because: upstream disappeared expiration date:2014-12-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=preps-gui portname: devel/prepstools description:Problem reporting system maintainer: po...@freebsd.org status: BROKEN deprecated because: upstream disappeared expiration date:2014-12-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=prepstools portname: dns/bind10 description:Development version of ISC BIND 10 DNS Suite maintainer: m...@freebsd.org status: IGNORE deprecated because: Is not developed any more, use dns/bundy expiration date:2015-12-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=bind10 portname: dns/maradns1 description:DNS server with focus on security and simplicity maintainer: m...@freebsd.org deprecated because: MaraDNS 1 end-of-life: June 21, 2015, use dns/maradns expiration date:2015-06-21 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=maradns1 portname: games/secretmaryochronicles description:Secret Maryo Chronicles two-dimensional platform game maintainer: amd...@freebsd.org status: BROKEN deprecated because: Broken for more than 6 months expiration date:2014-12-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=secretmaryochronicles portname: games/secretmaryochronicles-music description:Background music for Secret Maryo Chronicles maintainer: amd...@freebsd.org deprecated because: Depends on expiring games/secretmaryochronicles expiration date:2014-12-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=secretmaryochronicles-music portname: graphics/ender description:Ender provide common API for enesim renderers maintainer: gbl...@freebsd.org status:
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: archivers/ruby-lha broken because: Does not build with Ruby 2.0 or Ruby 2.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=ruby-lha portname: audio/aureal-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=aureal-kmod portname: audio/padevchooser broken because: needs update to support pulseaudio 5.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=padevchooser portname: audio/qmidinet broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=qmidinet portname: audio/raproxy broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: audio/xmms-openspc broken because: does not build on FreeBSD 10.x and later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=xmms-openspc portname: cad/cider broken because: Will not build with bmake and USES=fmake will not solve the issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=cider portname: comms/wsjt broken because: Fails to configure build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/wsjt-9.1.r2511_3.log http://beefy2.isc.freebsd.org/bulk/101amd64-RELENG_10_1/latest/logs/errors/wsjt-9.1.r2511_5.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=wsjt portname: databases/freetds-devel broken because: Fails to build build errors: http://beefy2.isc.freebsd.org/bulk/101amd64-RELENG_10_1/latest/logs/errors/freetds-devel-0.92.812,1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=freetds-devel portname: databases/gtksql broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gtksql portname: databases/mariadb-client broken because: Does not build under FreeBSD 10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mariadb-client portname: databases/mariadb-server broken because: Does not build under FreeBSD 10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mariadb-server portname: databases/py-fdb broken because: Does not compile on FreeBSD
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=ntp-rc ___ 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 unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/raproxy broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: cad/cider broken because: Will not build with bmake and USES=fmake will not solve the issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=cider portname: databases/gtksql broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gtksql portname: databases/tora broken because: Does not compile with clang (include list) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=tora portname: deskutils/glipper broken because: Uses unknown GNOME components pygnomedesktop and pygnomeextras build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=glipper portname: deskutils/gnochm broken because: Uses unknown GNOME component pygnomeextras build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=gnochm portname: deskutils/kupfer broken because: Uses unknown GNOME component pygnomedesktop build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=kupfer portname: deskutils/timer-applet broken because: Uses unknown GNOME component pygnomedesktop build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=timer-applet portname: devel/p5-Cdk broken because: Does not build with Perl 5.18 or above build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Cdk portname: devel/preps-gui broken because: public distfiles unavailable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=preps-gui portname: devel/prepstools broken because: public distfiles unavailable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=prepstools portname: devel/xtla broken because: Fails to package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=xtla portname: editors/scribes broken because: Uses unknown GNOME component pygnomeextras build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editorsportname=scribes portname: emulators/linux_base-gentoo-stage3 broken
Difference between fetch(1) and firefox http-access
Running CURRENT (FreeBSD 11.0-CURRENT #2 r275512: Fri Dec 5 16:00:34 CET 2014 amd64), I ran into some kind of obscurity I can not fathom. Updating ports fails since a couple of days by now (I do updates on a daily basis). fetch isn't capable of reaching any(!) server it tries to download sourcecode tarballs from (neither via ports ftp, http, https). When manually copied the sources of the tarball to Firefox' URL requester, I can luckily download the sources to whatever destination I like and I have to copy them to the /usr/ports/distfiles[/blabla] destination manually. As I understood fetch it establishes a simple ftp, http or https connection, as Firefox does. But it seems that something is going terribly wrong. It would be nice if someone could push me towards a hint or something to solve the problem. I hope it's not a serious bug but a simple error in the configuration. Thanks in advance, Oliver ___ 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
