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 +-+ x11-wm/awesome-vicious | 2.4.0 | v2.4.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 Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports from github
i am ahead of you in learning about making ports - if no one more experienced can help you out, feel free to contact me privately and I'll do what I can to help. The FreeBSD ports system is pretty awesome in my opinion - it's far easier than RPMs or DEBs. dave c - Kailua, HI 96734 Cornejo for Congress https://davidcornejo.org/ On Sat, May 23, 2020 at 4:40 PM Montgomery-Smith, Stephen wrote: > > Is there a "howto" that explains how to build a port from a project that > is on github? The FreeBSD porters handbook seems to assume a lot of > knowledge is already understood. > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Kailua, Hawaiʻi US +1 (808) 728-3050 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Gratuitous port splitting (was: Port Avidemux)
On Sat, May 23, 2020 at 8:27 PM Greg 'groggy' Lehey wrote: > On Friday, 22 May 2020 at 21:38:44 -0700, Kevin Oberman wrote: > > On Fri, May 22, 2020 at 1:55 PM Wiebe Pestman > wrote: > > > >> Dear maintainer(s), > >> Today I tried to install the port avidemux-2.7.4_1, but unfortunately > >> without success. > >> When running the command "make install" the whole process proceeds > >> without any error message. > >> But at the end there is no binary ... > >> Neither in /usr/local/bin, nor in > >> > >> /usr/ports/multimedia/avidemux/work/stage/usr/local/bin > >> > >> Am I overlooking something in the installation procedure? > >> The kernel on my machine is: > >> > >> FreeBSD zwaluw 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 > >> > >> Hope to get an answer from you :-) > >> Best regards from Holland, > >> Wiebe Pestman > > > > avidemux does not install any executable. Oddly, it just installs > libraries > > and the like. You must also install avidemux-plugins and either or both > > avidemux-cli and avidemux-qt5. If you only need the GUI, you can skip > > avidemux-cli. > > > > The command to run the GUI version of avidemux is avidemux3_qt5. The CLI > > interface is avidemux3_cli. > > Yes, I've run into this problem too. Arguably it's broken. The > official documentation expects it to be a single installation, and I > don't see any reason to split avidemux into five ports (there's also > avidemux-qt4). What good is the avidemux port on its own? Or the > combination of avidemux-qt5 without avidemux-plugins? Just finding > out that you need all this stuff is a pain. I'd recommend folding > both of these ports, and probably avidemux-cli, into the ports > avidemux-qt4 and avidemux-qt5. > > At the very least there should be a warning in avidemux/pkg-descr, but > I don't think that's the right approach. > > Thoughts? > You are completely right, but this application is weird. It a bear of a port because it used to include tar files of all of its dependencies due to ever changing APIs that kept breaking the build. It also makes for a very messy build that actually is separate builds with a bash script to drive it. As a result, the creation of four ports was probably somewhat natural. It's still a bad idea and I have twice worked with committers who wanted to rework it, but people are busy. Tobias was very helpful to get this port back into the system after it had been deleted. I will submit an updated pkg-descr that at least lets people know that they need to install at least three ports. I hope to do that tomorrow. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Gratuitous port splitting (was: Port Avidemux)
On Friday, 22 May 2020 at 21:38:44 -0700, Kevin Oberman wrote: > On Fri, May 22, 2020 at 1:55 PM Wiebe Pestman wrote: > >> Dear maintainer(s), >> Today I tried to install the port avidemux-2.7.4_1, but unfortunately >> without success. >> When running the command "make install" the whole process proceeds >> without any error message. >> But at the end there is no binary ... >> Neither in /usr/local/bin, nor in >> >> /usr/ports/multimedia/avidemux/work/stage/usr/local/bin >> >> Am I overlooking something in the installation procedure? >> The kernel on my machine is: >> >> FreeBSD zwaluw 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 >> >> Hope to get an answer from you :-) >> Best regards from Holland, >> Wiebe Pestman > > avidemux does not install any executable. Oddly, it just installs libraries > and the like. You must also install avidemux-plugins and either or both > avidemux-cli and avidemux-qt5. If you only need the GUI, you can skip > avidemux-cli. > > The command to run the GUI version of avidemux is avidemux3_qt5. The CLI > interface is avidemux3_cli. Yes, I've run into this problem too. Arguably it's broken. The official documentation expects it to be a single installation, and I don't see any reason to split avidemux into five ports (there's also avidemux-qt4). What good is the avidemux port on its own? Or the combination of avidemux-qt5 without avidemux-plugins? Just finding out that you need all this stuff is a pain. I'd recommend folding both of these ports, and probably avidemux-cli, into the ports avidemux-qt4 and avidemux-qt5. At the very least there should be a warning in avidemux/pkg-descr, but I don't think that's the right approach. Thoughts? Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Ports from github
Is there a "howto" that explains how to build a port from a project that is on github? The FreeBSD porters handbook seems to assume a lot of knowledge is already understood. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere-devel failed to build lang/rust (rust-1.43.1)
On Sat, May 23, 2020 at 03:56:09PM -0700, David Wolfskill wrote: > ... > load: 8.59 cmd: sh 99503 [piperd] 35609.83r 1.23u 1.88s 0% 2156k > [12amd64-ports-home] [2020-05-23_12h08m48s] [parallel_build:] Queued: 1003 > Built: 999 Failed: 1Skipped: 2Ignored: 0Tobuild: 1 Time: > 09:53:48 > [05]: www/chromium | chromium-81.0.4044.138_1 build > (03:59:48 / 04:08:53) > [09:53:49] Logs: > /tank/poudriere/poudriere/data/logs/bulk/12amd64-ports-home/2020-05-23_12h08m48s > ... > I expect that once www/chromium finally finishes, I'll give poudriere > another chance at the "stragglers" (and record the results in > http://www.catwhisker.org/~david/FreeBSD/ports/rust/). > Retry appears to have worked : [00:00:16] Starting/Cloning builders [00:00:17] Hit CTRL+t at any time to see build progress and stats [00:00:17] [01] [00:00:00] Building lang/rust | rust-1.43.1 [01:00:51] [01] [01:00:34] Finished lang/rust | rust-1.43.1: Success [01:00:53] [01] [00:00:00] Building devel/rust-cbindgen | rust-cbindgen-0.14.2 [01:02:27] [01] [00:01:34] Finished devel/rust-cbindgen | rust-cbindgen-0.14.2: Success [01:02:27] [01] [00:00:00] Building www/firefox | firefox-76.0.1_3,1 [01:39:07] [01] [00:36:40] Finished www/firefox | firefox-76.0.1_3,1: Success [01:39:08] Stopping 3 builders Peace, david -- David H. Wolfskill da...@catwhisker.org "The Liar Tweets Tonight": https://www.youtube.com/watch?v=TkU1ob_lHCw See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
INDEX now builds successfully on 11.x
___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
poudriere-devel failed to build lang/rust (rust-1.43.1)
In my environment, I have a designated "build machine" (named "freebeast"); in addition to building FreeBSD for itself and a couple of other machines, it also builds packages (via devel/poudriere-devel) for those other machines. (Each machine is amd64, running stable/12.) The other machines get weekly updates (every Sunday), so I set up freebeast to build the bulk of the packages every Saturday, then (usually) the Sunday set of packages to build is relatively small (so I can get the weekly updates done faster than if I were to wait until Sunday to build all the packages that warrant rebuilding). Details are in http://www.catwhisker.org/~david/FreeBSD/upgrade.html. Today, after building stable/12 & head, I set freebeast to building packages; a while later, Spouse and I took the tandem bike out for a ride (for about 2.5 hours). A whlie later, I noticed that freebeast was still chugging away; ^T revealed that it was building www/chromium (which was expected); it also revealed that there had been a failure (which was not): load: 8.59 cmd: sh 99503 [piperd] 35609.83r 1.23u 1.88s 0% 2156k [12amd64-ports-home] [2020-05-23_12h08m48s] [parallel_build:] Queued: 1003 Built: 999 Failed: 1Skipped: 2Ignored: 0Tobuild: 1 Time: 09:53:48 [05]: www/chromium | chromium-81.0.4044.138_1 build (03:59:48 / 04:08:53) [09:53:49] Logs: /tank/poudriere/poudriere/data/logs/bulk/12amd64-ports-home/2020-05-23_12h08m48s A quick check revealed that lang/rust was the failing port; I've dumped a copy of the poudriere log (there's a gzipped copy there, as well) and an "info.txt" file that shows things like "uname -a" output from freebeast, as well as information about ports-mgmt/poudriere-devel and the current state of the SVN working copies for src & ports. It appears (to my eye that is quite unfamiliar with rust) that the first failure in the log is: sysroot: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/build/x86_64-unknown-freebsd/stage1" libdir: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/build/x86_64-unknown-freebsd/stage1/lib" error: could not compile `rustc_lint`. (which shows up quite near the end of the supplied log file). Please note that the machine has been building www/firefox (and thus, lang/rust) routinely for quite some time, so this is a little surprising. Even more surprising is that my laptop, where I also have www/firefox installed, and which I update via ports-mgmt/portmaster, has rust-1.43.1 built and installed, apparently without issue (other than consuming time and generating heat). I expect that once www/chromium finally finishes, I'll give poudriere another chance at the "stragglers" (and record the results in http://www.catwhisker.org/~david/FreeBSD/ports/rust/). Peace, david -- David H. Wolfskill da...@catwhisker.org "The Liar Tweets Tonight": https://www.youtube.com/watch?v=TkU1ob_lHCw See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Missing /dev/io on rpi3 running 12-stable
On 2020-May-20, at 11:16, bob prohaska wrote: > On Wed, May 20, 2020 at 07:09:11PM +0200, Mika??l Urankar wrote: >> Le mer. 20 mai 2020 ?? 18:46, bob prohaska a ??crit : >>> >>> Is there supposed to be a /dev/io by default in FreeBSD on a Pi3? >>> Attempts to start X under 12.1-STABLE r361271 GENERIC fail with >>> a report of "failed to open /dev/io". There is indeed no /dev/io, >>> but there's also no /dev/io on a pi2 running 12-stable. >>> >>> Nor does there seem to be a kernel module with matching name >>> >>> Thanks for reading! >>> >>> bob prohaska >> >> I haven't looked closely but it seems the error is in >> x11-servers/xorg-server/files/configure.ac, AC_DEFINE(USE_DEV_IO) >> > > Alas, the remedy does not suggest itself, at least not to me > > Can somebody offer a hint? Only partially . . . I've got a RPi3 going and: A) It has the xf86EnableIO routine that would try the open and call xf86Msg to report the issue. B) Setting a breakpoint on xf86EnableIO and running never triggers the breakpoint in my context. So having USE_DEV_IO defined is not sufficient to see the problem. You have one context that gets the problem and another that does not (changing users). Overall suggests that there is some login-specific configuration is controlling which way it works at runtime. A possibility here is: QUOTE 20200220: AFFECTS: users of x11-servers/xorg-server AUTHOR: zeis...@freebsd.org x11-servers/xorg-server has been updated to 1.20.7. With this update, xorg-server has switched from using the devd backend to the udev backend for device configuration on FreeBSD 12 and 13. If you have issues with input devices, please see the install message for details. The HAL backend option has been completely removed, as it was deprecated. If you have problems with input devices, ensure that both x11/libinput and x11-drivers/xf86-input-libinput are installed. They are installed in the default configuration, but if you have a custom configuration, they might not be. END QUOTE Are you using udev in both user contexts? devd? A mix across the contexts? I'm consistently using udev. This does seem to match up with what you have reported in that the context that worked had the below message (for example) but the failing one did not: [253234.564] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. The message was before reporting the "Module ABI versions" information. So your failing context is either devd based or still has the environment configured for HAL or is otherwise messed up such that udev is not in use. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
INDEX build failed for 11.x
INDEX build failed with errors: Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- describe.comms --- --- describe.converters --- --- describe.databases --- --- describe.deskutils --- --- describe.devel --- --- describe.dns --- --- describe.editors --- --- describe.emulators --- --- describe.finance --- --- describe.french --- --- describe.ftp --- [...] --- describe.security --- --- describe.shells --- --- describe.sysutils --- --- describe.textproc --- --- describe.sysutils --- sh: freebsd-version: not found make[5]: "/home/indexbuild/tindex/ports/sysutils/etc_os-release/Makefile" line 18: warning: "freebsd-version -u" returned non-zero status --- describe.ukrainian --- --- describe.vietnamese --- --- describe.www --- --- describe.x11 --- --- describe.x11-clocks --- --- describe.x11-drivers --- --- describe.x11-fm --- --- describe.x11-fonts --- --- describe.x11-servers --- --- describe.x11-themes --- --- describe.x11-toolkits --- --- describe.x11-wm --- Done. make_index: /home/indexbuild/tindex/ports/misc/py-onnx-tf: no entry for /home/indexbuild/tindex/ports/math/py-onnx Committers on the hook: amdmi3 arrowd brnrd decke madpilot olgeni stephen yuri Most recent SVN update was: Updating '.': UMOVED Dmisc/onnx Umisc/Makefile Amisc/py-onnx Amisc/py-onnx/Makefile Amisc/py-onnx/distinfo Amisc/py-onnx/files Amisc/py-onnx/files/patch-setup.py Amisc/py-onnx/pkg-descr Dmath/py-onnx Umath/octave-forge-octclip/Makefile Umath/octave-forge-octclip/distinfo Umath/octave-forge-octproj/Makefile Umath/octave-forge-octproj/distinfo Umath/Makefile Umath/lis/Makefile Umath/lis/distinfo Umath/py-arviz/Makefile Umath/py-arviz/distinfo Ucad/qrouter/Makefile Ucad/qrouter/distinfo Ucad/verilator/Makefile Ucad/verilator/distinfo Ucad/verilator/pkg-plist Asecurity/cfssl Asecurity/cfssl/Makefile Asecurity/cfssl/pkg-descr Asecurity/cfssl/distinfo Asecurity/cfssl/files Asecurity/cfssl/files/patch-cli_version_version.go Usecurity/openssl-devel/Makefile Usecurity/openssl-devel/pkg-plist Usecurity/openssl/Makefile Asecurity/openssl/files/extra-patch-ktls Usecurity/openssl/pkg-plist Usecurity/py-scrypt/Makefile Usecurity/py-scrypt/distinfo Usecurity/Makefile Ulang/racket-minimal/Makefile Ulang/racket-minimal/distinfo Ulang/racket-minimal/pkg-plist Ulang/racket/Makefile Ulang/racket/distinfo Ulang/racket/files/patch-share_pkgs_gui-lib_mred_private_wx_gtk_queue.rkt Ulang/racket/files/patch-src_racket_sconfig.h Ulang/racket/pkg-plist Usysutils/bsdisks/Makefile Usysutils/bsdisks/distinfo Udeskutils/calibre/Makefile Udeskutils/calibre/distinfo Ushells/fd/pkg-descr Ueditors/o/Makefile Ueditors/o/distinfo Ddns/dnscontrol/files Udns/dnscontrol/Makefile Udns/dnscontrol/distinfo Udns/subfinder/Makefile Udns/subfinder/distinfo Udns/subfinder/pkg-descr Udevel/RStudio/Makefile Udevel/RStudio/distinfo Udevel/RStudio/files/patch-src_cpp_core_system_PosixSched.cpp Udevel/RStudio/files/patch-src_cpp_core_system_PosixSystem.cpp Udevel/RStudio/files/patch-src_cpp_desktop_DesktopMain.cpp Udevel/RStudio/files/patch-src_cpp_session_CMakeLists.txt Udevel/RStudio/files/patch-src_cpp_session_session-config.h.in Udevel/RStudio/pkg-descr Updated to revision 536349. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ffmpeg 4.2.3'1
Am 23.05.20 um 11:17 schrieb ajtiM via freebsd-ports: > On FreeBSD 12.1-RELEASE-p5 I cannot build ffmpeg update: > > ===> Cleaning for ffmpeg-4.2.3,1 > ===> License GPLv3+ LGPL3+ accepted by the user > ===> ffmpeg-4.2.3,1 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by ffmpeg-4.2.3,1 for building > ===> Extracting for ffmpeg-4.2.3,1 > => SHA256 Checksum OK for ffmpeg-4.2.3.tar.xz. > => SHA256 Checksum OK for > 0001-Add-ability-for-ffmpeg-to-run-svt-vp9.patch. ===> Patching for > ffmpeg-4.2.3,1 ===> Applying distribution patches for ffmpeg-4.2.3,1 > 2 out of 8 hunks failed--saving rejects to libavformat/matroskaenc.c.rej > ===> FAILED Applying distribution patch > 0001-Add-ability-for-ffmpeg-to-run-svt-vp9.patch with -p1 *** Error > code 1 > > Stop. > make[1]: stopped in /usr/ports/multimedia/ffmpeg > *** Error code 1 > > Stop. > make: stopped in /usr/ports/multimedia/ffmpeg > > ===>>> make build failed for multimedia/ffmpeg > ===>>> Aborting update > > ===>>> Update for multimedia/ffmpeg failed > ===>>> Aborting update > > Thank you. > VVD alread opened PR 246673 [1] about this failure. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246673 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ffmpeg 4.2.3'1
On FreeBSD 12.1-RELEASE-p5 I cannot build ffmpeg update: ===> Cleaning for ffmpeg-4.2.3,1 ===> License GPLv3+ LGPL3+ accepted by the user ===> ffmpeg-4.2.3,1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by ffmpeg-4.2.3,1 for building ===> Extracting for ffmpeg-4.2.3,1 => SHA256 Checksum OK for ffmpeg-4.2.3.tar.xz. => SHA256 Checksum OK for 0001-Add-ability-for-ffmpeg-to-run-svt-vp9.patch. ===> Patching for ffmpeg-4.2.3,1 ===> Applying distribution patches for ffmpeg-4.2.3,1 2 out of 8 hunks failed--saving rejects to libavformat/matroskaenc.c.rej ===> FAILED Applying distribution patch 0001-Add-ability-for-ffmpeg-to-run-svt-vp9.patch with -p1 *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/ffmpeg *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/ffmpeg ===>>> make build failed for multimedia/ffmpeg ===>>> Aborting update ===>>> Update for multimedia/ffmpeg failed ===>>> Aborting update Thank you. -- Ernst Lubitsch’s Ninotchka: “‘Waiter! A cup of coffee without cream, please!’ ‘I’m sorry, sir, we have no cream, only milk, so can it be a coffee without milk?’” ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
