Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
On 2020-Jun-16, at 22:21, bob prohaska wrote: > On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote: >> >> >> On 2020-Jun-16, at 21:34, bob prohaska wrote: >> >>> Just noticed there are now two u-boot ports for the RPi3, one >>> called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. >>> >>> The descriptions are equally bland, what's the difference? >>> The goal is to boot a recent snapshot of -current from USB >>> using a Pi3b (no +). Now it's suffering from cpu_reset failed. >> >> Looking, the check in history for sysutils/u-boot-rpi3-32 > > Could you write a few words about how one checks such history? > There doesn't seem to be anything in /usr/ports/UPDATING. Getting there directly: https://svnweb.freebsd.org/ports/head/sysutils/u-boot-rpi3-32/?view=log In steps via exploring: https://svnweb.freebsd.org then click on ports/ to get to: https://svnweb.freebsd.org/ports/ then click on head/ to get to: https://svnweb.freebsd.org/ports/head/ then click on sysutils/ to get to: https://svnweb.freebsd.org/ports/head/sysutils/ then select Page 2 in the Page popup so that the various u-boot* would be in range This gets one to: https://svnweb.freebsd.org/ports/head/sysutils/?dir_pagestart=1000 (currently) then click on the number to the right of u-boot-rpi3-32/ (536829 currently) This gets one to: https://svnweb.freebsd.org/ports/head/sysutils/u-boot-rpi3-32/?view=log For the example in use here there is only one log entry currently. >> reports for the creation of sysutils/u-boot-rpi3-32 : >> >> Revision 536829 - Directory Listing >> Added Fri May 29 01:27:16 2020 UTC (2 weeks, 5 days ago) by brd >> Add sysutils/u-boot-rpi3-32 to build a 32-bit version of u-boot >> >> This is useful for using the camera hardware, as >> misc/raspberrypi-userland does not support aarch64. >> >> Approved by: imp, manu >> Differential Revision: >> https://reviews.freebsd.org/D21603 >> >> >> So: >> >> A) sysutils/u-boot-rpi3 is for use with aarch64 FreeBSD >> B) sysutils/u-boot-rpi3-32 is for use with armv7 FreeBSD >> >> > > Mine is case A, but Case B is a little puzzling; will armv7 > run on a Pi3 ? I thought arm64 was mandatory. Sure, even Raspberry Pi OS still does not even have an official 64-bit release for any armv7 or later based Raspberry Pi that I'm aware of: all armv7 for official releases for such RPi*'s. (There are earlier stage 64-bit materials these days for the aarch64 capable RPi*'s, at least for the kernel. But no 64-bit/aarch64 userland that I'm aware of: just armv7.) I'm unclear on if there are contexts for which both sysutils/u-boot-rpi2/ and sysutils/u-boot-rpi3-32/ are possibilities for use with armv7 FreeBSD. sysutils/u-boot-rpi2/ does have a log entry indicating that it was tested on both a RPi2 V1.1 and a v1.2, but it is not explicit about which FreeBSD variant(s) were involved for either. If there are contexts where both u-boot's are possibilities, then I do not know why one would pick one over the other. May be sysutils/u-boot-rpi2/ can not handle an RPi3 despite handling a RPi2 V1.2? FYI: even under aarch64 FreeBSD, one can install an armv7 world in its own directory tree and chroot to it and run armv7 software (world material, ports, etc., not kernel). And poudriere can use such to do armv7 port builds on CortexA53/A57/A72 and many more without qemu being involved (or even installed). (There are oddities like Cortex-A32 that is ARMv8.0-A but 32-bit only and Cortex-A34 that is ARMv8.0-A but 64-bit only. Qualcomm also has an ARMv8.1-A that is AArch64 only, not 32-bit. There may be more such oddities.) === 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"
Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
On Tue, Jun 16, 2020 at 10:22 PM bob prohaska wrote: > On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote: > > > > > > On 2020-Jun-16, at 21:34, bob prohaska wrote: > > > > > Just noticed there are now two u-boot ports for the RPi3, one > > > called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. > > > > > > The descriptions are equally bland, what's the difference? > > > The goal is to boot a recent snapshot of -current from USB > > > using a Pi3b (no +). Now it's suffering from cpu_reset failed. > > > > Looking, the check in history for sysutils/u-boot-rpi3-32 > > Could you write a few words about how one checks such history? > There doesn't seem to be anything in /usr/ports/UPDATING. > You need to go to the web interface to the SVN repo for FreeBSD, http://svnweb.freebsd.org and walk down the tree. For ports, you probably want the ports->head repo. Then select the group and port of interest. You probably want to select Makefile and you can scroll down to what you are looking for. You'll need to play around to get a hang of how to do various things, but every commit ever made to FreeBSD since at least version 2.2 and I think before that as well as all ports from their creation. The repo is an incredible resource for looking for reasons for changes and, especially, to track down the commit that introduced a bug. That's how I tracked down a recent issue with 12.1-Stable that was panicking my system when I started a VirtualBox VM. I had no idea of how to fix it, but I knew who made the commit and, when I contacted him, I had a workaround in less than an hour and a fix in about 4 hours. It didn't take that long, but I was away from my system for a while Sunday evening before seeing the response with the patch. Obviously, the committer was not taking the evening off. (Thanks again, Mark!) -- Kevin Oberman, retired Network Engineer ___ 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: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote: > > > On 2020-Jun-16, at 21:34, bob prohaska wrote: > > > Just noticed there are now two u-boot ports for the RPi3, one > > called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. > > > > The descriptions are equally bland, what's the difference? > > The goal is to boot a recent snapshot of -current from USB > > using a Pi3b (no +). Now it's suffering from cpu_reset failed. > > Looking, the check in history for sysutils/u-boot-rpi3-32 Could you write a few words about how one checks such history? There doesn't seem to be anything in /usr/ports/UPDATING. > reports for the creation of sysutils/u-boot-rpi3-32 : > > Revision 536829 - Directory Listing > Added Fri May 29 01:27:16 2020 UTC (2 weeks, 5 days ago) by brd > Add sysutils/u-boot-rpi3-32 to build a 32-bit version of u-boot > > This is useful for using the camera hardware, as > misc/raspberrypi-userland does not support aarch64. > > Approved by: imp, manu > Differential Revision: > https://reviews.freebsd.org/D21603 > > > So: > > A) sysutils/u-boot-rpi3 is for use with aarch64 FreeBSD > B) sysutils/u-boot-rpi3-32 is for use with armv7 FreeBSD > > Mine is case A, but Case B is a little puzzling; will armv7 run on a Pi3 ? I thought arm64 was mandatory. Thanks for reading and the speedy reply! bob prohaska ___ 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: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
On 2020-Jun-16, at 21:34, bob prohaska wrote: > Just noticed there are now two u-boot ports for the RPi3, one > called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. > > The descriptions are equally bland, what's the difference? > The goal is to boot a recent snapshot of -current from USB > using a Pi3b (no +). Now it's suffering from cpu_reset failed. Looking, the check in history for sysutils/u-boot-rpi3-32 reports for the creation of sysutils/u-boot-rpi3-32 : Revision 536829 - Directory Listing Added Fri May 29 01:27:16 2020 UTC (2 weeks, 5 days ago) by brd Add sysutils/u-boot-rpi3-32 to build a 32-bit version of u-boot This is useful for using the camera hardware, as misc/raspberrypi-userland does not support aarch64. Approved by:imp, manu Differential Revision: https://reviews.freebsd.org/D21603 So: A) sysutils/u-boot-rpi3 is for use with aarch64 FreeBSD B) sysutils/u-boot-rpi3-32 is for use with armv7 FreeBSD === 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"
Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
Just noticed there are now two u-boot ports for the RPi3, one called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. The descriptions are equally bland, what's the difference? The goal is to boot a recent snapshot of -current from USB using a Pi3b (no +). Now it's suffering from cpu_reset failed. Thanks for reading, apologies if it's a dumb question... bob prohaska ___ 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 port can't build (again)
On 16 Jun 2020, at 21:14, George Mitchell wrote: > On 2020-06-16 23:12, George Mitchell wrote: >> On 2020-06-16 23:10, @lbutlr wrote: >>> [...] >>> Needless to say, I was expecting that checkout would give me 12.1, but I >>> don't see how to get that. > Pardon the typo: > > https://svn.freebsd.org/base/releng/12.1/ Thank you, cleared /usr/src and running the svn checkout with that URL now. It's still well over a gig so it will be a few minutes before trying to build lsof again. Yep. That solved the problem, and lsof built. Thanks again! -- Beware of the Leopard! ___ 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 port can't build (again)
On Wed, 17 Jun 2020 at 15:11, @lbutlr wrote:
>
> On 16 Jun 2020, at 06:40, Mike Bristow wrote:
> > What is the output of "egrep '^(TYPE|REVISION|BRANCH)'
> > /usr/src/sys/conf/newvers.sh" ?
>
> Well, this seems like it might be bad:
>
> # egrep '^(TYPE|REVISION|BRANCH)' /usr/src/sys/conf/newvers.sh
> TYPE="FreeBSD"
> REVISION="13.0"
> BRANCH=${BRANCH_OVERRIDE:-CURRENT}
>
> > How do you maintain the src tree on your machine?
>
> svn checkout https://svn.FreeBSD.org/base/head /usr/src
>
> And
>
> cd /usr/src
> make update SVN_UPDATE=yes
>
> Needless to say, I was expecting that checkout would give me 12.1, but I
> don't see how to get that.
It's in the handbook:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn.html
So for 12-stable, you should be using:
svn checkout https://svn.freebsd.org/base/stable/12 /usr/src
--
Jonathan Chen
___
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 port can't build (again)
On 16 Jun 2020, at 06:40, Mike Bristow wrote:
> What is the output of "egrep '^(TYPE|REVISION|BRANCH)'
> /usr/src/sys/conf/newvers.sh" ?
Well, this seems like it might be bad:
# egrep '^(TYPE|REVISION|BRANCH)' /usr/src/sys/conf/newvers.sh
TYPE="FreeBSD"
REVISION="13.0"
BRANCH=${BRANCH_OVERRIDE:-CURRENT}
> How do you maintain the src tree on your machine?
svn checkout https://svn.FreeBSD.org/base/head /usr/src
And
cd /usr/src
make update SVN_UPDATE=yes
Needless to say, I was expecting that checkout would give me 12.1, but I don't
see how to get that.
--
'You make us want what we can't have and what you give us is worth
nothing and what you take is everything and all there is left for
us is the cold hillside, and emptiness, and the laughter of the
elves.'
___
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"
Fwd: unifi5, mongodb and python2
Hi, Looking for some feedback on this. Or should I just go ahead and create PRs? Ronald. Van: Ronald Klop Datum: vrijdag, 12 juni 2020 11:08 Aan: f...@freebsd.org Onderwerp: unifi5, mongodb and python2 Hi, Currently unifi5 uses mongodb36. Mongodb36 and mongodb40 are marked as deprecated because they use python2 in the build stage. Both will expire/be removed on 2020-12-31 unless somebody (or upstream) fixes this. Mongodb42 uses python3 and will stay, but we don't know if it is compatible yet. Upgrade of mongodb is only supported in these steps according to the documentation: 3.6 -> 4.0 -> 4.2. So to help the users of Unifi5 on the quarterly branches the following scheme would be possible. * Switch unifi5 to mongodb40 before the next branch 2020Q3 (around 1th of July). * Then before 2020Q4 (1th of October) switch to mongodb42. This gives the people running on quarterly branches an easy upgrade path. Of course it should be tested if unifi5 runs on mongodb40 and -42 first. I can do that in my home setup the coming week. Maybe more testers are welcome, because my setup is pretty simple. Do you have thoughts about this? Regards, Ronald. ___ 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"
general R4I on ports
Folks, Not to start a flame war, but I've had a few issues in the ports tree, as STABLE readers have no doubt seen. This is a Request for Insights. IMHO, it's a black hole to stay current with ports designed to utilize GNU tools, especially documentation tools. I realize that given the complexity and size of the ports tree, eliminating GPL ports would cut out a huge swath of cool stuff, especially considering the ongoing EOL crisis in our SW world. I was looking at flex and bison, as examples. Flex is BSD-licensed, but bison is not. Byacc, however, is Public Domain. I would like to create an end-point system using FreeBSD that is BSD-clean insofar as licensing is concerned. I know that I am not alone in desiring this. We do have lots of Big GoshWhatta(tm) Corporations using FreeBSD, and the cleaner we can make it the happier their lawyers would be. I do realize that I can determine the dependencies of ports before I install them, and, because I am building a mule for pushing and shoving and developing, I choose to install docs, which in most cases kicks me into the black hole, but I'd like to offer a diffident suggestion. Could we initialize a /usr/ports/bsd tree, which would mirror /usr/ports (as it is developed) with bsd/devel, bsd/lang, etc.? I realize that there are far too few people smart and experienced enough to be committers and maintainers, but it seems that if one is familiar (much more than I am now) with the process and the individual ports, making a BSD-clean port would be possible for you guys. First by pruning things like non-BSD non-text documentation, etc, but then getting more ambitious like re-writing for byacc instead of bison and clang instead of g++. I know that Knuth used to do lots of cool docs with his TeX and other ideas. I'm not asking you to create a BSD world by magic wand, but maybe if the hooks were there some would accept the challenge. Who knows, maybe I'll get educated enough to have the courage to try it myself! -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ 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: might need to bump version of python ports after recent openssl changes
On 05/27, Konstantin Belousov wrote: > On Tue, May 26, 2020 at 11:31:32PM -0700, Kevin Oberman wrote: > > On Tue, May 26, 2020 at 11:09 PM Stefan Eßer wrote: > > > > > Am 27.05.20 um 04:24 schrieb Jan Beich: > > > > Pete Wright writes: > > > > > > > >> hello - on current i found myself in a situation where python37 was > > > >> unable to import ssl: > > > >> > > > >> $ python3.7 > > > >> Python 3.7.7 (default, May 9 2020, 01:37:42) > > > >> [Clang 10.0.0 (g...@github.com:llvm/llvm-project.git > > > >> llvmorg-10.0.0-0-gd32170dbd on freebsd13 > > > >> Type "help", "copyright", "credits" or "license" for more information. > > > > import ssl > > > >> Traceback (most recent call last): > > > >> File "", line 1, in > > > >> File "/usr/local/lib/python3.7/ssl.py", line 98, in > > > >> import _ssl # if we can't import it, let the error > > > >> propagate > > > >> ImportError: /usr/local/lib/python3.7/lib-dynload/_ssl.so: Undefined > > > >> symbol "SSLv3_method@OPENSSL_1_1_0" > > > > > > > >> > > > >> > > > >> after a little digging it looks like we recently disabled SSLv3 on > > > >> CURRENT (huzzah!): > > > >> https://reviews.freebsd.org/D24945 > > > >> > > > >> After forcing a re-install of python37 things are working again as it > > > >> looked like the pbuilder did rebuild python after this commit. But pkg > > > >> upgrade didn't detect a new version, so I think it might be helpful to > > > >> bump the python version's so that people on CURRENT don't end up in > > > >> the same situation I was in? Not sure what the usual process is for > > > >> stuff like this... > > > > > > > > OSVERSION was already bumped in base r361410, so poudriere will > > > > force-rebuild all packages. Those who hack .jailversion to avoid > > > > rebuilds can only blame themselves. > > > > > > OSVERSION bumps will be observed by poudriere, but not by other port > > > building tools. > > > > > > Did I miss an announcement that all other methods to keep your system > > > in a workable state are now considered obsolete and unsupported? > > > > > > A port version bump would have enabled rebuilding just the affected > > > ports, while a rebuild of all my ports based on OSVERSION will take > > > days to complete on my local build server. > > > > Even if the packages are updated in the repository, does pkg know it? > > It looks to me like pkg upgrade will simply not upgrade the port unless > > PORT_REVISION is bumped. > What this change needed, and missed, is the dso version bump for > libssl.so.111. It seems even after rebuilding some ports, we've still got the runtime error: ImportError: /usr/local/lib/python3.7/lib-dynload/_ssl.so: Undefined symbol "SSLv3_method@OPENSSL_1_1_0" signature.asc Description: PGP signature
Re: Lsof port can't build (again)
On Jun 16, 2020, at 06:41, Mike Bristow wrote: > > That is not present in the file on relent/12.1, which is probably the same as > yours. I suspect that you have an out-of-date /usr/src. I just installed the source, and ran the svn update just in case. > (This does beg the question of why your attempt to build lsof is looking > under /usr/src, but I'm not going there). Yeah, we covered this recently. The option appears to be either pkg install, or building requires src. I’ll check the output of your command when I get back to a terminal. ___ 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 port can't build (again)
Hi, On 15/06/2020 02:52, @lbutlr wrote: When trying to update lsof on FreeBSD 12.1-RELEASE-p5 GENERIC i386 I get the following fatal error: /usr/src/sys/sys/pcpu.h:224:10: fatal error: 'machine/pcpu_aux.h' file not found #include ^~~~ That is not present in the file on relent/12.1, which is probably the same as yours. I suspect that you have an out-of-date /usr/src. (This does beg the question of why your attempt to build lsof is looking under /usr/src, but I'm not going there). What is the output of "egrep '^(TYPE|REVISION|BRANCH)' /usr/src/sys/conf/newvers.sh" ? How do you maintain the src tree on your machine? Cheers, Mike ___ 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: cups-pdf crash status -139
> On 16. Jun 2020, at 11:47, Per olof Ljungmark wrote: > > On 2020-06-15 16:14, Michael Gmelin wrote: >>> On Mon, 15 Jun 2020 12:03:17 +0200 >>> Per olof Ljungmark wrote: >>> On 2020-06-15 09:50, Michael Gmelin wrote: > On 15. Jun 2020, at 09:45, Per olof Ljungmark > wrote: What happens if you run the gs command on the pdf you’re printing directly: > gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sstdout=? > -sDEVICE=ps2write -dShowAcroForm -sOUTPUTFILE=? -dLanguageLevel=2 > -r300 -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE ? ? -f ? >>> >>> A PDF is created. >>> >>> And, according to logs gs is OK: >>> >>> D [15/Jun/2020:09:16:23 +0200] [Job 1070] Wrote 1 pages... >>> D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37126 (pstops) exited >>> with no errors. >>> D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37125 (gs) exited with >>> no errors. >>> D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37123 >>> (/usr/local/libexec/cups/filter/pdftops) exited with no errors. >>> I [15/Jun/2020:09:16:23 +0200] [Job 1070] Backend returned status >>> -139 (crashed) >> Are you printer(s) shown as okay in the cups web UI? (like, not >> temporarily halted, stopped, etc.?). I sometimes had some issues after >> upgrading, especially with hplip. >> This upstream issue reported earlier this year sounds similar to what >> you're seeing, maybe it helps: https://github.com/apple/cups/issues/5765 > > The cups-pdf printer is paused with "Backend failed" but all other printers > are OK. HPLIP is not installed. > Can you enable the cups-pdf printer using the “cupsenable” command? And if so, will it stay enabled or go back to paused/failed at the next attempt? Cheers, Michael > The info from the link you sent looks related although the configs are not > the same, but it is an interesting lead that I will pursue further. There is > a severe lack of debug info though, the error_log is not helpful at all. > > Also, that thread is dated April 6 which is about the same time that the > problem showed up here too. > > Thanks, > > Per > ___ > 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" ___ 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: cups-pdf crash status -139
On 2020-06-15 16:14, Michael Gmelin wrote: On Mon, 15 Jun 2020 12:03:17 +0200 Per olof Ljungmark wrote: On 2020-06-15 09:50, Michael Gmelin wrote: On 15. Jun 2020, at 09:45, Per olof Ljungmark wrote: What happens if you run the gs command on the pdf you’re printing directly: gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sstdout=? -sDEVICE=ps2write -dShowAcroForm -sOUTPUTFILE=? -dLanguageLevel=2 -r300 -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE ? ? -f ? A PDF is created. And, according to logs gs is OK: D [15/Jun/2020:09:16:23 +0200] [Job 1070] Wrote 1 pages... D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37126 (pstops) exited with no errors. D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37125 (gs) exited with no errors. D [15/Jun/2020:09:16:23 +0200] [Job 1070] PID 37123 (/usr/local/libexec/cups/filter/pdftops) exited with no errors. I [15/Jun/2020:09:16:23 +0200] [Job 1070] Backend returned status -139 (crashed) Are you printer(s) shown as okay in the cups web UI? (like, not temporarily halted, stopped, etc.?). I sometimes had some issues after upgrading, especially with hplip. This upstream issue reported earlier this year sounds similar to what you're seeing, maybe it helps: https://github.com/apple/cups/issues/5765 The cups-pdf printer is paused with "Backend failed" but all other printers are OK. HPLIP is not installed. The info from the link you sent looks related although the configs are not the same, but it is an interesting lead that I will pursue further. There is a severe lack of debug info though, the error_log is not helpful at all. Also, that thread is dated April 6 which is about the same time that the problem showed up here too. Thanks, Per ___ 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: baikal-0.6.1
On Jun 15 2020, 21:47 UTC, Jim - OPP wrote: Are there any plans to update the port to version 0.7.0 in the bear future? The current port is requiring PHP 7.2 which ended active support in Nov 2019 and ends security only fixes in just over 5 months. The newest version has added support for PHP 7.4 per GitHub. Hi, I just pushed an update to 0.7.1 in r539335. I haven't tested it with 7.4 yet, but I plan to upgrade my server to it asap. Thanks for the heads up. -- Pietro Cerutti ___ 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"
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 +-+ comms/usbmuxd | 1.1.0 | 1.1.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: FreeBSD Port: phabricator-php73-20200514_1
> On 16. Jun 2020, at 08:41, Fabian Abplanalp - Legatech GmbH
> wrote:
>
> Hi
>
> Since we updated the Port to 20200514_1 we can't create milestones anymore
> with the following information... Is there anything known about that problem
> or should we place a bugreport at phabricator?
>
> Reproducible case (on our phab-test):
>
> Get PHID of the project where I want to add a milestone:
> https://phab-test.neratec.com/conduit/method/phid.lookup/
> names: ["#software_team"]
> result:
> { "#software_team":
> { "phid": "PHID-PROJ-32jtopr6klyrrpxe3pow",
> "uri": "https://phab-test.neratec.com/tag/software_team/";,
> "typeName": "Project",
> "type": "PROJ",
> "name": "Software Team",
> "fullName": "Software Team",
> "status": "open"
> }
> }
> Try to create milestone of "Software Team" project
> https://phab-test.neratec.com/conduit/method/project.edit/
> transactions:
> [{"type":"milestone","value":"PHID-PROJ-32jtopr6klyrrpxe3pow"},{"type":"name","value":"2020.15"},{"type":"description","value":"=
> Sprint 2020.15"}]
> Conduit > Unhandled Exception ("Error")
> Call to a member function getPHID() on null
> Error on server shows: EXCEPTION: (Error) Call to a member function getPHID()
> on null at
> [/src/applications/project/editor/PhabricatorProjectTransactionEditor.php:358]
>
Based on staring at the code[0], my wild guess is that your conduit user has no
or insufficient access to the parent project (above the code referenced a copy
of parent is created and adjusted for permissions).
The ticket referenced in the code can be found here[1].
Best,
Michael
[0]
https://github.com/phacility/phabricator/blob/d203a1004c7509109fccdf526e9941b89eeef662/src/applications/project/editor/PhabricatorProjectTransactionEditor.php#L349
[1] https://secure.phabricator.com/T13462
>
> --
> Fabian Abplanalp
> Senior IT System Administrator
>
> Legatech GmbH
> Etzelstrasse 14
> 8634 Hombrechtikon
> Switzerland
> Tel 055 244 36 39 / https://www.legatech.ch
___
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"
