Re: lsof marked ignored
21.03.2020 4:30, @lbutlr wrote: > On 20 Mar 2020, at 14:10, Robert Huff wrote: >> Adam Weinberger writes: >> ===>>> Currently installed version: lsof-4.93.2_9,8 ===>>> Port directory: /usr/ports/sysutils/lsof ===>>> This port is marked IGNORE ===>>> requires kernel sources >>> >>> That error should only occur if system sources are missing from >>> /usr/src. Check that they're still there, and if not then check them >>> out from svn. >> >> (Last time I checked ) >> Not only does it require kernel sources, but those sources need >> to match the running kernel. > > Why was this changed (I did not install the source and my /usr/src/ directory > is empty and has been since I moved to 12.1) Nothing changed really. lsof needs the whole file sys/fs/pseudofs/pseudofs.h for struct pfs_node and all other parts (types etc.) it uses from same file and it needs the definition of struct lock_owner from sys/kern/kern_lock.c. It tastes some other files in sys/ to enable -DHAS_LOCKF_ENTRY -DHAS_PAUSE_SBT -DHAS_CDEV2PRIV -DHASFUSEFS -DHAS_ZFS but does not really needs their contents, so these flags could be enabled unconditionally by the port. So if we could "export" pseudofs.h and struct lock_owner to /usr/include, then lsof could be built without need of kernel sources. ___ 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: lsof marked ignored
On 03/20/2020 9:09 pm, Robert Huff wrote: Larry Rosenman writes: I'd love to see the kernel folks make better interfaces. I've been saying that for 2 years. Can you be one step more specific on what interface it needs? Respectfully, Robert Huff No, because I'm not a great C programmer, and don't know the kernel real well. I've been maintaining lsof for the last 5 years, mostly as a proxy for Vic Abell (the original Author, now retired at 80+ years old). We have a github project (https://github.com/lsof-org). I'm still officially the maintainer, but need some help from the kernel folks to clean up all the #ifdef mess going back to FreeBSD 2.2(if not earlier). and modernize the interfaces between lsof<->kernel. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ 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: lsof marked ignored
Larry Rosenman writes: > I'd love to see the kernel folks make better interfaces. > > I've been saying that for 2 years. Can you be one step more specific on what interface it needs? Respectfully, Robert Huff ___ 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: users of xorg, in particular on FreeBSD 11.3
21.03.2020 6:41, Niclas Zeising wrote: > [ This is cross-posted across several mailing lists for maximum visibility. > Please respect reply-to and keep replies to x...@freebsd.org . Thank you! ] > > In order to improve support when using evdev to manage input devices, in > particular keyboards, we have switched the default in x11/libxkbcommon to the > evdev instead of the legacy ruleset. This was done in ports r528813 . > > On FreeBSD 11.3, the default configuration still requires the legacy ruleset. > > If you are using FreeBSD 11.3, or if you are using xf86-input-keyboard on > FreeBSD 12 or later, you need to change the ruleset used by x11/libxkbcommon. > > If you have issues with your keyboard, most notably arrow keys, and if > /var/log/Xorg.*.log shows that the "kbd" or "keyboard" driver is being used, > you need to switch to legacy rules by setting the environment variable > XKB_DEFAULT_RULES to xorg. > > The easiest way to accomplish this is by adding it to your shell startup file. > > As an example, for users of [t]csh, put > setenv XKB_DEFAULT_RULES xorg > in ~/.login > > For users of bourne type shells (sh, bash, ksh, zsh, ...) instead put > export XKB_DEFAULT_RULES=xorg > in ~/.profile Please consider improving x11/libxkbcommon so that it uses -Ddefault-rules=xorg if OSVERSION notes 11.x at build time, so there would be no breakage for us building xorg from ports. ___ 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"
users of xorg, in particular on FreeBSD 11.3
[ This is cross-posted across several mailing lists for maximum visibility. Please respect reply-to and keep replies to x...@freebsd.org . Thank you! ] In order to improve support when using evdev to manage input devices, in particular keyboards, we have switched the default in x11/libxkbcommon to the evdev instead of the legacy ruleset. This was done in ports r528813 . On FreeBSD 11.3, the default configuration still requires the legacy ruleset. If you are using FreeBSD 11.3, or if you are using xf86-input-keyboard on FreeBSD 12 or later, you need to change the ruleset used by x11/libxkbcommon. If you have issues with your keyboard, most notably arrow keys, and if /var/log/Xorg.*.log shows that the "kbd" or "keyboard" driver is being used, you need to switch to legacy rules by setting the environment variable XKB_DEFAULT_RULES to xorg. The easiest way to accomplish this is by adding it to your shell startup file. As an example, for users of [t]csh, put setenv XKB_DEFAULT_RULES xorg in ~/.login For users of bourne type shells (sh, bash, ksh, zsh, ...) instead put export XKB_DEFAULT_RULES=xorg in ~/.profile Regards -- Niclas Zeising FreeBSD Graphics Team ___ 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: lsof marked ignored
On 03/20/2020 5:53 pm, Adam Weinberger wrote: On Fri, Mar 20, 2020 at 4:45 PM Dave Horsfall wrote: On Fri, 20 Mar 2020, Adam Weinberger wrote: > That error should only occur if system sources are missing from > /usr/src. Check that they're still there, and if not then check them out > from svn. Does it not require kernel header files only? Only distributed with the source, which annoyed me because at the time I didn't have the room... That's a good question. I'm not sure whether it requires just the headers or kernel sources beyond that. The lsof/Makefile explicitly checks for sys/kern/kern_lockf.c so the port is definitely looking for more than the headers. If you want to save space, you should probably be safe checking out just /usr/src/sys. Please let me know if I'm wrong about that; you're certainly neither the first nor the last person to want lsof without needing the entire src tree. # Adam it needs the sources. I'd love to see the kernel folks make better interfaces. I've been saying that for 2 years. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ 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: lsof marked ignored
On Fri, Mar 20, 2020 at 4:45 PM Dave Horsfall wrote: > > On Fri, 20 Mar 2020, Adam Weinberger wrote: > > > That error should only occur if system sources are missing from > > /usr/src. Check that they're still there, and if not then check them out > > from svn. > > Does it not require kernel header files only? Only distributed with the > source, which annoyed me because at the time I didn't have the room... That's a good question. I'm not sure whether it requires just the headers or kernel sources beyond that. The lsof/Makefile explicitly checks for sys/kern/kern_lockf.c so the port is definitely looking for more than the headers. If you want to save space, you should probably be safe checking out just /usr/src/sys. Please let me know if I'm wrong about that; you're certainly neither the first nor the last person to want lsof without needing the entire src tree. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ 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: lsof marked ignored
On Fri, 20 Mar 2020, Adam Weinberger wrote: That error should only occur if system sources are missing from /usr/src. Check that they're still there, and if not then check them out from svn. Does it not require kernel header files only? Only distributed with the source, which annoyed me because at the time I didn't have the room... -- Dave ___ 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: lsof marked ignored
On 20 Mar 2020, at 15:30, @lbutlr wrote: > PORTS+MODULE=sysutils/lsof Oops. -- Say, give it up, give it up, television's taking its toll That's enough, that's enough, gimme the remote control I've been nice, I've been good, please don't do this to me Turn it off, turn it off, I don't want to have to see ___ 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: lsof marked ignored
On 20 Mar 2020, at 14:10, Robert Huff wrote: > Adam Weinberger writes: > >>> ===>>> Currently installed version: lsof-4.93.2_9,8 >>> ===>>> Port directory: /usr/ports/sysutils/lsof >>> >>>===>>> This port is marked IGNORE >>>===>>> requires kernel sources >> >> That error should only occur if system sources are missing from >> /usr/src. Check that they're still there, and if not then check them >> out from svn. > > (Last time I checked ) > Not only does it require kernel sources, but those sources need > to match the running kernel. Why was this changed (I did not install the source and my /usr/src/ directory is empty and has been since I moved to 12.1) > My solution has been to add "sysutils/lsof" to PORTS_MODULES in > /etc/make.conf. How does this help? # cat /etc/make.conf DEFAULT_VERSIONS+=ssl=openssl apache=2.4 php=7.2 perl5=5.30 mysql=10.3m PORTS+MODULE=sysutils/lsof Building lsof still fails pkg install works. -- Sarah, age 18, says "man, once you go Crayola you can't go back.” ___ 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: lsof marked ignored
Adam Weinberger writes: > > ===>>> Currently installed version: lsof-4.93.2_9,8 > > ===>>> Port directory: /usr/ports/sysutils/lsof > > > > ===>>> This port is marked IGNORE > > ===>>> requires kernel sources > > That error should only occur if system sources are missing from > /usr/src. Check that they're still there, and if not then check them > out from svn. (Last time I checked ) Not only does it require kernel sources, but those sources need to match the running kernel. My solution has been to add "sysutils/lsof" to PORTS_MODULES in /etc/make.conf. Respectfully, Robert Huff ___ 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: lsof marked ignored
On Fri, Mar 20, 2020 at 1:02 PM @lbutlr wrote: > > Got this when trying tu update lsof: > > ===>>> lsof-4.93.2_9,8 > ===>>> New version available: lsof-4.93.2_10,8 > > ===>>> Currently installed version: lsof-4.93.2_9,8 > ===>>> Port directory: /usr/ports/sysutils/lsof > > ===>>> This port is marked IGNORE > ===>>> requires kernel sources > > Don’t see anything in MOVED or UPDATIN about changes to lsof? > > Since I built the previous version should I just comment the IGNORE line in > the makefile and not worry about why I > got this error (didn’t get it before). That error should only occur if system sources are missing from /usr/src. Check that they're still there, and if not then check them out from svn. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ 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"
lsof marked ignored
Got this when trying tu update lsof: ===>>> lsof-4.93.2_9,8 ===>>> New version available: lsof-4.93.2_10,8 ===>>> Currently installed version: lsof-4.93.2_9,8 ===>>> Port directory: /usr/ports/sysutils/lsof ===>>> This port is marked IGNORE ===>>> requires kernel sources Don’t see anything in MOVED or UPDATIN about changes to lsof? Since I built the previous version should I just comment the IGNORE line in the makefile and not worry about why I got this error (didn’t get it before). -- 'Things either exist or they don't,' said Jeremy. 'I am very clear about that. I have medicine.' --The Thief of Time ___ 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 error: cannot rollback ..., there is a snapshot ... more recent ....
Miroslav Lachman writes: > [...] > Any possibility that you have some kind of automatic snapshoting utility > run from crontab recursively on filesystem where poudriere have builder > jails mounted? > > I saw this error when I setup zfsnap in crontab with resursive snapshot > of /vol0 (each 5 minutes) and my poudriere is in /vol0/poudriere. > > The workaround was to not create recursive snapshots on /vol0 but on > each /vol0 sub-filesystem except /vol0/poudriere. > > I don't know it this is your problem too. That's quite likely, sanoid's snapshot-ing regularly. Doing the sub-filesystems might be a pain in the butt, might be easier to stick the builds somewhere else. Or perhaps even just pause the snapshot-ing while I'm rebuilding. GREAT LEAD. Thanks! g. ___ 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 error: cannot rollback ..., there is a snapshot ... more recent ....
George Hartzell wrote on 2020/03/20 18:13: I have a FreeBSD 12.1p3 (just updated) root-on-zfs system that's having trouble doing Poudriere builds. It started off life as a FreeBSD 12.1 system and has been building it's own set of packages using Poudriere successfully since its inception. I few updates ago I started seeing errors in the Poudriere builds. I'm trying to run one now and am seeing the errors again. Here's an example: [...] [00:30:24] [02] [00:00:00] Building devel/py-more-itertools@py37 | py37-more-itertools-8.2.0 cannot rollback 'zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02': there is a snapshot or bookmark more recent than 'zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02@prepkg' [00:30:26] [02] [00:00:02] Error: Unable to rollback zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02 to prepkg =>> Error: Unable to rollback zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02 to prepkg [...] After crashing, I can hit ^T and see: [...] load: 1.01 cmd: sh 36519 [piperd] 1994.36r 0.08u 0.13s 0% 3188k [12_1-ports_and_hartzell] [2020-03-20_09h30m34s] [parallel_build:] Queued: 149 Built: 72 Failed: 1 Skipped: 4 Ignored: 0 Tobuild: 72 Time: 00:33:31 [01]: crashed [02]: devel/p5-IO-stringy | p5-IO-stringy-2.111 package (00:00:00 / 00:00:06) [00:33:33] Logs: /usr/local/poudriere/data/logs/bulk/12_1-ports_and_hartzell/2020-03-20_09h30m34s [...] a bit later, that builder seems to recover and continue sucessfully with new jobs: [...] load: 3.40 cmd: sh 36519 [piperd] 2282.32r 0.09u 0.15s 0% 3188k [12_1-ports_and_hartzell] [2020-03-20_09h30m34s] [parallel_build:] Queued: 149 Built: 80 Failed: 3 Skipped: 10 Ignored: 0 Tobuild: 56 Time: 00:38:19 [01]: lang/cython@py27 | py27-cython-0.29.15 build (00:01:00 / 00:01:12) [02]: devel/icu | icu-66.1,1build (00:03:10 / 00:03:24) [00:38:21] Logs: /usr/local/poudriere/data/logs/bulk/12_1-ports_and_hartzell/2020-03-20_09h30m34s [...] I'd like to get it working normally again. Any ideas what might be going wrong? Any possibility that you have some kind of automatic snapshoting utility run from crontab recursively on filesystem where poudriere have builder jails mounted? I saw this error when I setup zfsnap in crontab with resursive snapshot of /vol0 (each 5 minutes) and my poudriere is in /vol0/poudriere. The workaround was to not create recursive snapshots on /vol0 but on each /vol0 sub-filesystem except /vol0/poudriere. I don't know it this is your problem too. Kind regards Miroslav Lachman ___ 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 error: cannot rollback ..., there is a snapshot ... more recent ....
I have a FreeBSD 12.1p3 (just updated) root-on-zfs system that's having trouble doing Poudriere builds. It started off life as a FreeBSD 12.1 system and has been building it's own set of packages using Poudriere successfully since its inception. I few updates ago I started seeing errors in the Poudriere builds. I'm trying to run one now and am seeing the errors again. Here's an example: [...] [00:30:24] [02] [00:00:00] Building devel/py-more-itertools@py37 | py37-more-itertools-8.2.0 cannot rollback 'zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02': there is a snapshot or bookmark more recent than 'zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02@prepkg' [00:30:26] [02] [00:00:02] Error: Unable to rollback zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02 to prepkg =>> Error: Unable to rollback zroot/poudriere/jails/12_1-ports_and_hartzell-ref/02 to prepkg [...] After crashing, I can hit ^T and see: [...] load: 1.01 cmd: sh 36519 [piperd] 1994.36r 0.08u 0.13s 0% 3188k [12_1-ports_and_hartzell] [2020-03-20_09h30m34s] [parallel_build:] Queued: 149 Built: 72 Failed: 1 Skipped: 4 Ignored: 0 Tobuild: 72 Time: 00:33:31 [01]: crashed [02]: devel/p5-IO-stringy | p5-IO-stringy-2.111 package (00:00:00 / 00:00:06) [00:33:33] Logs: /usr/local/poudriere/data/logs/bulk/12_1-ports_and_hartzell/2020-03-20_09h30m34s [...] a bit later, that builder seems to recover and continue sucessfully with new jobs: [...] load: 3.40 cmd: sh 36519 [piperd] 2282.32r 0.09u 0.15s 0% 3188k [12_1-ports_and_hartzell] [2020-03-20_09h30m34s] [parallel_build:] Queued: 149 Built: 80 Failed: 3 Skipped: 10 Ignored: 0 Tobuild: 56 Time: 00:38:19 [01]: lang/cython@py27 | py27-cython-0.29.15 build (00:01:00 / 00:01:12) [02]: devel/icu | icu-66.1,1build (00:03:10 / 00:03:24) [00:38:21] Logs: /usr/local/poudriere/data/logs/bulk/12_1-ports_and_hartzell/2020-03-20_09h30m34s [...] I'd like to get it working normally again. Any ideas what might be going wrong? g. ___ 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"
[CFT] deskutils/calibre python 3 support
Hello! I have committed just now changes to the calibre port to add an option to build it against python 3. (r528772) As you all know python 2 is on it's way out and all software must be migrated, or removed from the ports tree. You may also know that calibre porting to python 3 is still experimental, that's why I added an option and did not simply switch over right away. At present the port default is still to build with python 2, so nothing changes by default. My plan is to switch the default in head after 2020Q2 quarterly is branched. I'm writing this to ask anyone who uses calibre and has time/resources to spare to test switching the option to python 3 and test it. This will become even easier once we branch 2020Q2, since by switching the default the latest binary packages will get python 3 calibre by default. I've been running this setup for the last two weeks without problems, but I only use basic functionality, and I'd especially like the USB device sync functionality to be stressed a little to make sure nothing breaks. Any feedback is appreciated. Thanks in advance! -- Guido Falsi ___ 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: FreeBSD Port: atom-ide-1.45.0 Error build
Hi Mateusz, Thanks for the suggestion. I didn't know a package (and a version) could be specified as a dependency. I will amend the dependency line next time I update the port. Thanks, Hiroki On 2020/03/19 1:21, Mateusz Piotrowski wrote: On 3/18/20 5:12 PM, Alex V. Petrov wrote: 18.03.2020 18:57, Hiroki Tagato пишет: It appears the leveldown module fails to build with Node 12 or 13. Can you retry with Node 10? The port specifies www/node10 as a build dependency. Would it be possible to specify that the port depends on a package instead of a binary? For example, instead of node:www/node10 we would use node10>0:www/node10 in *_DEPENDS. Cheers, Mateusz ___ 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"
