Re: pkg: how to retrieve the messages ports emit after install?
Am 18.03.20 um 07:28 schrieb Chris: > OK I'm a by ports make install as a rule. But I needed to > spin up a box quickly, and decided to use pkg(8). xorg, > and another port (package) I installed, dumped some > important information after the install. I stripped the > text from the console/terminal, and tried to paste it into > a fresh file. But the new graphics drivers don't allow > that sort of thing (graphics vs text mode). So I was left > with mostly gibberish. I need to get that information back. > I just guessed that pkg message might do it. > But no joy. How can I retrieve that information? You may be looking for some variant of: # pkg query -- '--- %n-%v ---\n%M' Regards, STefan ___ 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: pkg: how to retrieve the messages ports emit after install?
On 2020-03-18 07:28, Chris wrote:
OK I'm a by ports make install as a rule. But I needed to
spin up a box quickly, and decided to use pkg(8). xorg,
and another port (package) I installed, dumped some
important information after the install. I stripped the
text from the console/terminal, and tried to paste it into
a fresh file. But the new graphics drivers don't allow
that sort of thing (graphics vs text mode). So I was left
with mostly gibberish. I need to get that information back.
I just guessed that pkg message might do it.
But no joy. How can I retrieve that information?
Not sure I understand what you are asking for...
Perhaps
"pkg info -D {pkgname}"
or
"pkg info -D -a"
?
"pkg help info" might also be useful.
Sorry if that's not what you were asking.
bye
av.
___
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: pkg: how to retrieve the messages ports emit after install?
On Tue, 17 Mar 2020 23:28:49 -0700 Chris wrote: > OK I'm a by ports make install as a rule. But I needed to > spin up a box quickly, and decided to use pkg(8). xorg, > and another port (package) I installed, dumped some > important information after the install. I stripped the > text from the console/terminal, and tried to paste it into > a fresh file. But the new graphics drivers don't allow > that sort of thing (graphics vs text mode). So I was left > with mostly gibberish. I need to get that information back. > I just guessed that pkg message might do it. > But no joy. How can I retrieve that information? Simple! pkg info -D pkgname (or pkg info --pkg-message pkgname) There are more complicated ways... ___ 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 Port: atom-ide-1.45.0 Error build
XX(target)
Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy-sinksource.o
CXX(target)
Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy-stubs-internal.o
CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy.o
AR(target) Release/obj.target/deps/snappy/snappy.a
COPY Release/snappy.a
CXX(target) Release/obj.target/leveldown/src/batch.o
In file included from ../src/batch.cc:3:
In file included from ../node_modules/nan/nan.h:222:
In file included from ../node_modules/nan/nan_converters.h:67:
../node_modules/nan/nan_converters_43_inl.h:22:1: error: no viable
conversion from 'Local' to 'v8::Isolate *'
X(Boolean)
^~
../node_modules/nan/nan_converters_43_inl.h:18:23: note: expanded from
macro 'X'
val->To ## TYPE(isolate->GetCurrentContext())
\
^~~~
/usr/local/include/node/v8.h:2762:37: note: passing argument to
parameter 'isolate' here
Local ToBoolean(Isolate* isolate) const;
^
In file included from ../src/batch.cc:3:
In file included from ../node_modules/nan/nan.h:222:
In file included from ../node_modules/nan/nan_converters.h:67:
../node_modules/nan/nan_converters_43_inl.h:40:1: error: no viable
conversion from 'Local' to 'v8::Isolate *'
X(bool, Boolean)
^~~~
../node_modules/nan/nan_converters_43_inl.h:37:29: note: expanded from
macro 'X'
return val->NAME ## Value(isolate->GetCurrentContext());
\
^~~~
/usr/local/include/node/v8.h:2771:30: note: passing argument to
parameter 'isolate' here
bool BooleanValue(Isolate* isolate) const;
^
In file included from ../src/batch.cc:3:
In file included from ../node_modules/nan/nan.h:223:
In file included from ../node_modules/nan/nan_new.h:189:
../node_modules/nan/nan_implementation_12_inl.h:356:37: error: too few
arguments to function call, expected 2, have 1
return v8::StringObject::New(value).As();
~ ^
/usr/local/include/node/v8.h:5688:3: note: 'New' declared here
static Local New(Isolate* isolate, Local value);
^
In file included from ../src/batch.cc:3:
In file included from ../node_modules/nan/nan.h:2722:
../node_modules/nan/nan_object_wrap.h:24:25: error: no member named
'IsNearDeath' in 'Nan::Persistent >'
assert(persistent().IsNearDeath());
^
/usr/include/assert.h:56:21: note: expanded from macro 'assert'
#define assert(e) ((e) ? (void)0 : __assert(__func__, __FILE__, \
^
In file included from ../src/batch.cc:3:
In file included from ../node_modules/nan/nan.h:2722:
../node_modules/nan/nan_object_wrap.h:127:26: error: no member named
'IsNearDeath' in 'Nan::Persistent >'
assert(wrap->handle_.IsNearDeath());
~ ^
/usr/include/assert.h:56:21: note: expanded from macro 'assert'
#define assert(e) ((e) ? (void)0 : __assert(__func__, __FILE__, \
^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:16:26: error: too few arguments to function call,
single argument 'context' was not specified
return (!obj->ToObject().IsEmpty()
~ ^
/usr/local/include/node/v8.h:2754:3: note: 'ToObject' declared here
V8_WARN_UNUSED_RESULT MaybeLocal ToObject(
^
/usr/local/include/node/v8config.h:419:31: note: expanded from macro
'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:17:48: error: too few arguments to function call,
single argument 'context' was not specified
&& node::Buffer::HasInstance(obj->ToObject()))
~ ^
/usr/local/include/node/v8.h:2754:3: note: 'ToObject' declared here
V8_WARN_UNUSED_RESULT MaybeLocal ToObject(
^
/usr/local/include/node/v8config.h:419:31: note: expanded from macro
'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:18:42: error: too few arguments to function call,
single argument 'context' was not specified
? node::Buffer::Length(obj->ToObject())
~ ^
/usr/local/include/node/v8.h:2754:3: note: 'ToObject' declared here
V8_WARN_UNUSED_RESULT MaybeLocal ToObject(
^
/usr/local/include/node/v8config.h:419:31: note: expanded from macro
'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:19:21: error: too few arguments to function call,
single argument 'context' was not specified
Re: FreeBSD Port: atom-ide-1.45.0 Error build
Hi Alex, 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. Thanks, Hiroki (snip) gyp ERR! node -v v13.10.1 gyp ERR! node-gyp -v v5.0.5 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! leveldown@4.0.2 install: `prebuild-install || node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the leveldown@4.0.2 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /usr/ports/editors/atom/work/.npm/_logs/2020-03-18T11_13_11_923Z-debug.log *** Error code 1 Stop. make: stopped in /usr/ports/editors/atom ===>>> make build failed for editors/atom ___ 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: pkg: how to retrieve the messages ports emit after install?
On Wed, 18 Mar 2020 08:27:29 + Bob Eager r...@tavi.co.uk said On Tue, 17 Mar 2020 23:28:49 -0700 Chris wrote: > OK I'm a by ports make install as a rule. But I needed to > spin up a box quickly, and decided to use pkg(8). xorg, > and another port (package) I installed, dumped some > important information after the install. I stripped the > text from the console/terminal, and tried to paste it into > a fresh file. But the new graphics drivers don't allow > that sort of thing (graphics vs text mode). So I was left > with mostly gibberish. I need to get that information back. > I just guessed that pkg message might do it. > But no joy. How can I retrieve that information? Simple! pkg info -D pkgname (or pkg info --pkg-message pkgname) --pkg-message, argh... I was *so* close! Thanks, Bob. Really appreciated! and for the record. I *did* read the man page. But as others were also inclined to suggest; I thought the output would be related to *query* Thanks also, to everyone else who took the time to help! --Chris There are more complicated ways... ___ 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: pkg: how to retrieve the messages ports emit after install?
On Wed, 18 Mar 2020 07:18:40 -0700 Chris wrote: > > > OK I'm a by ports make install as a rule. But I needed to > > > spin up a box quickly, and decided to use pkg(8). xorg, > > > and another port (package) I installed, dumped some > > > important information after the install. I stripped the > > > text from the console/terminal, and tried to paste it into > > > a fresh file. But the new graphics drivers don't allow > > > that sort of thing (graphics vs text mode). So I was left > > > with mostly gibberish. I need to get that information back. > > > I just guessed that pkg message might do it. > > > But no joy. How can I retrieve that information? > > > > Simple! > > > > pkg info -D pkgname > > > > (or pkg info --pkg-message pkgname) > --pkg-message, argh... I was *so* close! > Thanks, Bob. Really appreciated! > and for the record. I *did* read the man page. But as others > were also inclined to suggest; I thought the output would be > related to *query* As it happens, I had the same problem a few days ago and eventually got round to a rather persistent search for the information! ___ 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: pkg: how to retrieve the messages ports emit after install?
Am 18.03.20 um 15:18 schrieb Chris: > On Wed, 18 Mar 2020 08:27:29 + Bob Eager r...@tavi.co.uk said > >> On Tue, 17 Mar 2020 23:28:49 -0700 >> Chris wrote: >> >> > OK I'm a by ports make install as a rule. But I needed to >> > spin up a box quickly, and decided to use pkg(8). xorg, >> > and another port (package) I installed, dumped some >> > important information after the install. I stripped the >> > text from the console/terminal, and tried to paste it into >> > a fresh file. But the new graphics drivers don't allow >> > that sort of thing (graphics vs text mode). So I was left >> > with mostly gibberish. I need to get that information back. >> > I just guessed that pkg message might do it. >> > But no joy. How can I retrieve that information? >> >> Simple! >> >> pkg info -D pkgname >> >> (or pkg info --pkg-message pkgname) > --pkg-message, argh... I was *so* close! > Thanks, Bob. Really appreciated! > and for the record. I *did* read the man page. But as others > were also inclined to suggest; I thought the output would be > related to *query* I do actually prefer the version I suggested based on pkg query, since I find it quite hard to see message boundaries in the pkg info output. With pkg query you can introduce any kind of separators (even multi-line) in the format string (and also print the origin and other information along with the message). Regards, STefan ___ 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
18.03.2020 18:57, Hiroki Tagato пишет: > Hi Alex, > > 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. > > Thanks, > Hiroki > > (snip) >> gyp ERR! node -v v13.10.1 >> gyp ERR! node-gyp -v v5.0.5 >> gyp ERR! not ok >> npm ERR! code ELIFECYCLE >> npm ERR! errno 1 >> npm ERR! leveldown@4.0.2 install: `prebuild-install || node-gyp rebuild` >> npm ERR! Exit status 1 >> npm ERR! >> npm ERR! Failed at the leveldown@4.0.2 install script. >> npm ERR! This is probably not a problem with npm. There is likely >> additional logging output above. >> >> npm ERR! A complete log of this run can be found in: >> npm ERR! >> /usr/ports/editors/atom/work/.npm/_logs/2020-03-18T11_13_11_923Z-debug.log >> >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/editors/atom >> >> ===>>> make build failed for editors/atom Your hint is great. It helps me. Thanks. -- - Alex. ___ 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: pkg: how to retrieve the messages ports emit after install?
On Wed, 18 Mar 2020 14:20:05 + Bob Eager r...@tavi.co.uk said On Wed, 18 Mar 2020 07:18:40 -0700 Chris wrote: > > > OK I'm a by ports make install as a rule. But I needed to > > > spin up a box quickly, and decided to use pkg(8). xorg, > > > and another port (package) I installed, dumped some > > > important information after the install. I stripped the > > > text from the console/terminal, and tried to paste it into > > > a fresh file. But the new graphics drivers don't allow > > > that sort of thing (graphics vs text mode). So I was left > > > with mostly gibberish. I need to get that information back. > > > I just guessed that pkg message might do it. > > > But no joy. How can I retrieve that information? > > > > Simple! > > > > pkg info -D pkgname > > > > (or pkg info --pkg-message pkgname) > --pkg-message, argh... I was *so* close! > Thanks, Bob. Really appreciated! > and for the record. I *did* read the man page. But as others > were also inclined to suggest; I thought the output would be > related to *query* As it happens, I had the same problem a few days ago and eventually got round to a rather persistent search for the information! I appreciate your persistence! I was going mad trying to figure it out. IMHO this should be added to the pkg(8) man page. Maybe the EXAMPLES section? Thanks again, Bob! --Chris ___ 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
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"
Re: pkg: how to retrieve the messages ports emit after install?
On 3/18/20 5:20 PM, Chris wrote: IMHO this should be added to the pkg(8) man page. Maybe the EXAMPLES section? https://github.com/freebsd/pkg/pull/1819 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"
Re: pkg: how to retrieve the messages ports emit after install?
On Wed, 18 Mar 2020 17:31:53 +0100 Mateusz Piotrowski mpp...@gmail.com said On 3/18/20 5:20 PM, Chris wrote: > IMHO this should be added to the pkg(8) man page. Maybe the EXAMPLES > section? https://github.com/freebsd/pkg/pull/1819 Cheers, Mateusz WOW! That was fast. Thank you!!! :) --Chris ___ 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"
drmn0: This code is obsolete abandonware. Install the graphics/drm-legacy-kmod pkg
erm... I *did* install the graphics/drm-legacy-kmod pkg what's going on here. This is on 12.1-CURRENT as is installed from the install media. Followed by a pkg install xorg-server xorg-drivers xorg-fonts xorg-apps \ drm-legacy-kmod xfce-4 slim pcmanfm echo startxfce4>~/.xinitrc echo 'kld_list="/boot/modules/i915kms.ko">>/etc/rc.conf and bounce the box. This drm problem also seems to be interfering with my ability to run xfce4 (of xorg) properly. What do I need to do? Thanks! --Chris ___ 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 +-+ graphics/nomacs | 3.6.1 | 3.14.2 +-+ 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"
