On Mon, May 03, 2021 at 01:36:18PM +0100, tech-lists wrote:
> Hi, not sure where this goes. Seems to be a ports tree error, so posting
> here.
>
> full error from poudriere:
>
> [00:00:24] Warning: (misc/mc-nox11): Error: Duplicated origin for
> mc-nox11-4.8.26: misc/mc-nox
Hi, not sure where this goes. Seems to be a ports tree error, so posting
here.
full error from poudriere:
[00:00:24] Warning: (misc/mc-nox11): Error: Duplicated origin for
mc-nox11-4.8.26: misc/mc-nox11 AND misc/mc. Rerun with -v to see which
ports are depending on these.
[00:00:41] Error
___
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"
use, at least for pkg itself.
>
> Ports are rebuilt on the system as the pre-built ports
> have options selected that do not match the requirements
> of the system. It takes a week or more to rebuild
> everything, which why I'm concerned with the bogus
> warning and whether 'p
On Tue, Feb 16, 2021 at 07:46:05AM +0900, Tatsuki Makino wrote:
> There is a difference between the pkg in /usr/sbin and the pkg in
> /usr/local/sbin.
> The manual for /usr/sbin/pkg is man 7 pkg.
pkg in /usr/sbin does two things:
- if /usr/local/sbin/pkg exists, exec it.
- else bootstrap pkg.
-
On Mon, Feb 15, 2021 at 08:44:46PM -0800, Mark Millard wrote:
>
> Do you use:
>
> https://www.freshports.org/ports-mgmt/port-maintenance-tools/
>
First port installed on any system is pkg. Second port
installed is portmaster. Everything after that is installed
with portmaster.
--
Steve
tall"
> > > but just pkg install use, at least for pkg itself.
> >
> > Ports are rebuilt on the system as the pre-built ports
> > have options selected that do not match the requirements
> > of the system. It takes a week or more to rebuild
> > everythi
use, at least for pkg itself.
>>
>> Ports are rebuilt on the system as the pre-built ports
>> have options selected that do not match the requirements
>> of the system. It takes a week or more to rebuild
>> everything, which why I'm concerned with the bogus
>&
> have options selected that do not match the requirements
> of the system. It takes a week or more to rebuild
> everything, which why I'm concerned with the bogus
> warning and whether 'pkg bootstrap -f' would rebuild
> everything.
>
> I also do
>
> % cd /usr
all"
> but just pkg install use, at least for pkg itself.
Ports are rebuilt on the system as the pre-built ports
have options selected that do not match the requirements
of the system. It takes a week or more to rebuild
everything, which why I'm concerned with the bogus
warning and
t; bogus warnings from pkg.
> > >
> > > % pkg info > /dev/null
> > > pkg: Warning: Major OS version upgrade detected. Running \
> > > "pkg bootstrap -f" recommended
> > >
> > > Short of running the bootstrap command, how do I get
> &g
There is a difference between the pkg in /usr/sbin and the pkg in
/usr/local/sbin.
The manual for /usr/sbin/pkg is man 7 pkg.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any ma
On Mon, Feb 15, 2021 at 08:56:51PM +, RW via freebsd-ports wrote:
> On Mon, 15 Feb 2021 12:39:13 -0800
> Steve Kargl wrote:
>
>
> > BTW, there is no documentation as what 'pkg bootstrap -f'
> > does. In particular, the -f option is no described.
> >
> >From pkg(8) (in 12.2):
>
> boots
On Mon, 15 Feb 2021 12:39:13 -0800
Steve Kargl wrote:
> BTW, there is no documentation as what 'pkg bootstrap -f'
> does. In particular, the -f option is no described.
>
>From pkg(8) (in 12.2):
bootstrap
This is for compatibility with the pkg(7) bootstrapper.
If
ts tree. All
> > installed ports where builtin after I installed FreeBSD. So,
> > I am running FreeBSD-14.0. For some reason, I am getting
> > bogus warnings from pkg.
> >
> > % pkg info > /dev/null
> > pkg: Warning: Major OS version upgrade detected. Running
ning FreeBSD-14.0. For some reason, I am getting
> bogus warnings from pkg.
>
> % pkg info > /dev/null
> pkg: Warning: Major OS version upgrade detected. Running \
> "pkg bootstrap -f" recommended
>
> Short of running the bootstrap command, how do I get
> r
am running FreeBSD-14.0. For some reason, I am getting
> bogus warnings from pkg.
>
> % pkg info > /dev/null
> pkg: Warning: Major OS version upgrade detected. Running \
> "pkg bootstrap -f" recommended
>
> Short of running the bootstrap command, how do I
I have a system installed from late January FreeBSD-current
sources and at that point an up-to-date ports tree. All
installed ports where builtin after I installed FreeBSD. So,
I am running FreeBSD-14.0. For some reason, I am getting
bogus warnings from pkg.
% pkg info > /dev/null
pkg: Warn
Dewayne,
Yesss ! Thanks it did the job !
I reinstalled port-maintenance-tools, and now the arch column in pkg DB
is correct, FraaBDS:13:*
I dunno why the generated ABI in this file was wrong (line was commented
out -> auto-detection)
Thanks again,
Cheers,
Xavier
On 01/02/2021 07:38, Dew
3-CURRENT, and as of 01/22 I switched to 13-STABLE
Now, when I run any ports/pkg command - I use only ports-, I got
pkg-static: Warning: Major OS version upgrade detected. Running "pkg
bootstrap -f" recommended
No a big deal, I thought, but :
[root@numenor ~]# pkg bootstrap -f
The
A while ago, due to mismatching ABI, I had to insert into:
/usr/local/etc/pkg.conf
ABI = "freebsd:12:x86:64";
Perhaps explicitly stating "freebsd:13:x86:64"; may help?
BUT this will require maintenance. :/
___
freebsd-ports@freebsd.org mailing list
http
Am 30.01.21 um 23:02 schrieb Xavier Humbert:
> Hi,
>
> I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE
>
> Now, when I run any ports/pkg command - I use only ports-, I got
>
>> pkg-static: Warning: Major OS version upgrade detected. Running "pkg
Xavier Humbert xavier at groumpf.org wrote on
Sat Jan 30 22:02:51 UTC 2021 :
> I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE
>
> Now, when I run any ports/pkg command - I use only ports-, I got
>
> > pkg-static: Warning: Major OS version upgrade detec
Hi,
I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE
Now, when I run any ports/pkg command - I use only ports-, I got
pkg-static: Warning: Major OS version upgrade detected. Running "pkg
bootstrap -f" recommended
No a big deal, I thought, but :
[root@numen
On 24/03/2019 8:34 pm, Xavier wrote:
Hi everyone,
Since last update of python modules py27-cryprography and
py27-matplotlib, duplicity emits a warning :
CryptographyDeprecationWarning: Support for unsafe construction of public
numbers from encoded data will be removed in a future version
Hi everyone,
Since last update of python modules py27-cryprography and
py27-matplotlib, duplicity emits a warning :
> CryptographyDeprecationWarning: Support for unsafe construction of public
> numbers from encoded data will be removed in a future version. Plea
[Some more notes after looking around.]
On 2018-Aug-16, at 10:04 AM, Mark Millard wrote:
> I've no clue if this is significant or not, so I figured I'd
> report it in case it is. I've never seen one of these before.
> See the "[10:59:31]" line b
I've no clue if this is significant or not, so I figured I'd
report it in case it is. I've never seen one of these before.
See the "[10:59:31]" line below if you care about the warning.
. . .
[04:59:38] [01] [00:00:00] Building devel/llvm60 | llvm60-6.0.1_2
load: 4.
>
> > > /bin/mkdir -p
> > > '/usr/ports/graphics/utsushi/work/stage/usr/local/libexec/utsushi'
> > > /bin/sh ../libtool --mode=install install -s -m 555 main
> > > '/usr/ports/graphics/utsushi/work/stage/usr/local/libexec/
> utsushi/./ut
s before? A lot of the files don't get
> > copied to the staging area.
> >
> > /bin/mkdir -p
> > '/usr/ports/graphics/utsushi/work/stage/usr/local/libexec/utsushi'
> > /bin/sh ../libtool --mode=install install -s -m 555 main
> > '/usr/ports/gr
ool --mode=install install -s -m 555 main
> > '/usr/ports/graphics/utsushi/work/stage/usr/local/libexec/
> utsushi/./utsushi-main'
> > libtool: warning: '../lib/libutsushi.la' has not been installed in
> > '/usr/local/lib/utsushi'
> > libto
sushi'
> /bin/sh ../libtool --mode=install install -s -m 555 main
> '/usr/ports/graphics/utsushi/work/stage/usr/local/libexec/utsushi/./utsushi-main'
> libtool: warning: '../lib/libutsushi.la' has not been installed in
> '/usr/local/lib/utsushi'
> l
sushi/work/stage/usr/local/libexec/utsushi/./utsushi-main'
libtool: warning: '../lib/libutsushi.la' has not been installed in
'/usr/local/lib/utsushi'
libtool: warning: '../filters/libflt-all.la' has not been installed in
'/usr/local/lib/utsushi'
libtool:
Le 12/10/2016 à 20:15, Kyle Evans a écrit :
> Hi,
>
> On Wed, Oct 12, 2016 at 10:35 AM, Mathieu Arnold wrote:
>> The warning will never be turned into errors. Maybe add a comment to the
>> makefile saying that files must not be stripped. Maybe a bit like go
>>
Hi,
On Wed, Oct 12, 2016 at 10:35 AM, Mathieu Arnold wrote:
> The warning will never be turned into errors. Maybe add a comment to the
> makefile saying that files must not be stripped. Maybe a bit like go
> ports do it, something like:
>
> STRIP= # Elf firmwares, do not strip
in concern here is that I don't intend to strip these, but the
> comment for stripped() would leave me to believe that there's a chance
> these warnings could eventually turn into errors, and I don't want
> this to be the case if it's not something that should be s
Hello!
I've got a port with a dozen+ ELF binaries for microcontroller
firmware that I don't think I should be stripping, but qa.sh does not
like this. They're *.elf and *.lib files, so I don't know that adding
these to the general exception of `find` in stripped() is necessarily
a good idea, but i
AMPLES=""
LIB32DIR=lib
DOCSDIR="share/doc/virtualbox-ose"
EXAMPLESDIR="share/examples/virtualbox-ose"
DATADIR="share/virtualbox-ose"
WWWDIR="www/virtualbox-ose"
ETCDIR="etc/virtualbox-ose"
--End PLIST_SUB--
--SUB_LIST--
VBOXDIR=/usr/local/lib/
ing directory '/usr/ports/devel/ocl-icd/work/ocl-icd-2.2.7'
cd . && /bin/sh /usr/ports/devel/ocl-icd/work/ocl-icd-2.2.7/build-aux/missing
automake-1.14 --foreign
Makefile /usr/ports/devel/ocl-icd/work/ocl-icd-2.2.7/build-aux/missing:
automake-1.14: not found WARNING: 'auto
Sorry for my delay replying, Thanks to
olli hauer wrote Thu Jun 18 04:28:49 UTC 2015 :
> On 2015-06-16 17:06, Julian H. Stacey wrote:
> > bsd.port.mk test below is too agressive, let's have it just Warn, not Fail.
> > Also prefix text "Error: " or "
On 2015-06-16 17:06, Julian H. Stacey wrote:
> bsd.port.mk test below is too agressive, let's have it just Warn, not Fail.
> Also prefix text "Error: " or "Warning: " make it obvious which is happening.
>
> It seems likely people may have different opinions
bsd.port.mk test below is too agressive, let's have it just Warn, not Fail.
Also prefix text "Error: " or "Warning: " make it obvious which is happening.
It seems likely people may have different opinions if it should
just Warn or Error, so kets add an environent swit
On Fri, 13 Feb 2015 09:55:46 -0800
Patrick Powell wrote:
> {142} # pkg upgrade
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> Updating database digests format: 100%
> Checking for upgrades (43 candidates): 97%
> ap24-mod_perl2
I upgraded pkg to today to 1.4.10 and got the following new (and
different) warning:
{142} # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (43 candidates): 97
Your mailbox is almost full.
Dear po...@freebsd.org,
3840MB4096MB
Current size Maximum size
Please reduce your mailbox size. Delete any items you don't need from your
mailbox and empty your Deleted Items folder. Click here to do reduce size
automatically. Th
Using ddclient on a FreeBSD CURRENT gateway (FreeBSD 11.0-CURRENT #1 r268450:
Wed Jul 9
09:59:41 CEST 2014 amd64) fails to update the DNS entry at the dynDNS
provider's side
with this error message logged to mail:
WARNING: file /var/tmp/ddclient.cache, line 3: Invalid Value for keywor
On Mon, Jul 07, 2014 at 08:34:06PM +0200, A.J. 'Fonz' van Werven wrote:
> [CC: Portlint maintainer]
>
> Presently, running Portlint on an unstaged port results in a *warning*
> that says "Consider adding STAGE support". I'd surmise that a fatal error
> a
[CC: Portlint maintainer]
Presently, running Portlint on an unstaged port results in a *warning*
that says "Consider adding STAGE support". I'd surmise that a fatal error
along the lines of "STAGE support will be mandatory pretty damn soon"
would be more appropria
Just updated my ports and ran into this issue:
MyServer % > svn update /usr/src
Updating '/usr/src':
At revision 268212.
Updating '/usr/ports':
>> Skipped
'/usr/ports/net-mgmt/nagios-plugins/files/patch-plugins-check_ssh.c' --
Node remains in conflict <<
At revision 36
On 27/06/2014 3:55 PM, Matthias Andree wrote:
> Am 27.06.2014 07:50, schrieb Joe Marcus Clarke:
>> Apparently there was some discussion on IRC about this. A PR (Bugzilla)
>> has been opened requesting the portlint warning about only a single
>> MASTER_SITE to be done a
On 26 June 2014 22:50, Joe Marcus Clarke wrote:
> Apparently there was some discussion on IRC about this. A PR (Bugzilla) has
> been opened requesting the portlint warning about only a single MASTER_SITE
> to be done away with.
>
> https://bugs.freebsd.org/bugzilla/show_bu
Am 27.06.2014 07:50, schrieb Joe Marcus Clarke:
> Apparently there was some discussion on IRC about this. A PR (Bugzilla)
> has been opened requesting the portlint warning about only a single
> MASTER_SITE to be done away with.
>
> https://bugs.freebsd.org/bugzilla/show_bu
Apparently there was some discussion on IRC about this. A PR (Bugzilla)
has been opened requesting the portlint warning about only a single
MASTER_SITE to be done away with.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191079
This was added before my time with portlint, and I could go
gt; > > > > error on every start of ClamAV:
> > > > > >
> > > > > > # service clamav-clamd start
> > > > > > Starting clamav_clamd.
> > > > > > LibClamAV Warning: Cannot dlopen libclamunrar_ifa
; > > > On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt
> > > > wrote:
> > > > > After the upgrade to clamav-0.98.3_2 I am obtaining following
> > > > > error on every start of ClamAV:
> > > > >
> > > > > # service cla
t; > > > After the upgrade to clamav-0.98.3_2 I am obtaining following
> > > > error on every start of ClamAV:
> > > >
> > > > # service clamav-clamd start
> > > > Starting clamav_clamd.
> > > > LibClamAV Warning: Cannot dlopen libclamu
t; error on every start of ClamAV:
> > >
> > > # service clamav-clamd start
> > > Starting clamav_clamd.
> > > LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not
> > > found - unrar support unavailable
> > >
> > > ClamAV, how
rting clamav_clamd.
> > LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found -
> > unrar support unavailable
> >
> > ClamAV, however, seems to work correctly. Is this a known issue?
> >
> > I am on 10.0-RELEASE-p3 amd64.
> >
> > Regards,
d start
> > Starting clamav_clamd.
> > LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found
> > - unrar support unavailable
> >
> > ClamAV, however, seems to work correctly. Is this a known issue?
> >
> > I am on 10.0-RELEASE-p3 amd64.
> >
> &g
error
> > > on every start of ClamAV:
> > >
> > > # service clamav-clamd start
> > > Starting clamav_clamd.
> > > LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found
> > > - unrar support unavailable
> > >
> > >
On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt wrote:
> After the upgrade to clamav-0.98.3_2 I am obtaining following error on
> every start of ClamAV:
>
> # service clamav-clamd start
> Starting clamav_clamd.
> LibClamAV Warning: Cannot dlopen libclamunrar_iface: file n
After the upgrade to clamav-0.98.3_2 I am obtaining following error on
every start of ClamAV:
# service clamav-clamd start
Starting clamav_clamd.
LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found -
unrar support unavailable
ClamAV, however, seems to work correctly. Is this a
Hello,
Would someone please close this PR? My intension was achieved with
commit of r351972.
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any m
On Fri, 11 Apr 2014 10:57:00 +0200
Alex Dupre wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> O. Hartmann ha scritto:
> > Since a couple of days by now I get bothered by this nasty error
> > corrupting all the services provided via Apache24/PHP:
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
O. Hartmann ha scritto:
> Since a couple of days by now I get bothered by this nasty error
> corrupting all the services provided via Apache24/PHP:
>
> [...] PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lo
Since a couple of days by now I get bothered by this nasty error corrupting all
the
services provided via Apache24/PHP:
[...]
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/local/lib/php/20100525-zts/xsl.so' - Cannot open
"/usr/local/lib/php/20100525-zts
This
Shane Ambler wrote:
>On 08/02/2014 08:24, O. Hartmann wrote:
>>
>> Today a couple of updates has been introduced, one of them was an
>> update of port devel/icu.
>>
>> I the good manner/tradition of updating UPDATING, I expect a
>> warning/hint/
> On Fri, Feb 07, 2014 at 10:54:45PM +0100, O. Hartmann wrote:
> >
> > Today a couple of updates has been introduced, one of them was an
> > update of port devel/icu.
> >
> > I the good manner/tradition of updating UPDATING, I expect a
> > warning/hint/
On Sat, 08 Feb 2014 18:42:44 +1030
Shane Ambler wrote:
> On 08/02/2014 08:24, O. Hartmann wrote:
> >
> > Today a couple of updates has been introduced, one of them was an
> > update of port devel/icu.
> >
> > I the good manner/tradition of updating UPDATING, I
On 08/02/2014 08:24, O. Hartmann wrote:
>
> Today a couple of updates has been introduced, one of them was an
> update of port devel/icu.
>
> I the good manner/tradition of updating UPDATING, I expect a
> warning/hint/advice a couple of days from now - when everybody has
>
On Fri, Feb 07, 2014 at 10:54:45PM +0100, O. Hartmann wrote:
>
> Today a couple of updates has been introduced, one of them was an
> update of port devel/icu.
>
> I the good manner/tradition of updating UPDATING, I expect a
> warning/hint/advice a couple of days from now -
Today a couple of updates has been introduced, one of them was an
update of port devel/icu.
I the good manner/tradition of updating UPDATING, I expect a
warning/hint/advice a couple of days from now - when everybody has
already stepped into the mess.
On several boxes running 11.0-CURRENT and
Hello.
I've got sendmail with authentication: it uses saslauthd, which in turn
is configured to use PAM; I'm also using nss_ldap.
Authentication works; however I've got my logs filled with messages like:
sm-mta[78808]: s0U6haTm078808: AUTH failure (DIGEST-MD5): user not found
(-20) SASL(-13):
Do what pkg said :)
In /usr/local/etc/pkg/FreeBSD.conf should replace:
enabled:"yes"
to
enabled:true
And everything will fine
Cheers
Zsolt
2013/12/1 Derek Tattersall :
> I get the following message with any use of pkg. How should I fix it?
> pkg: Warning: expecting a
I get the following message with any use of pkg. How should I fix it?
pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD' repo,
the value has been correctly converted, please consider fixing
I'm using pkg-1.2.1
--
Best regards,
Derek T
> On Nov 27, 2013, at 11:07 AM, Tom Evans wrote:
>
>> On Wed, Nov 27, 2013 at 4:55 PM, Ajtim wrote:
>> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013
>> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>>
>> When I boot a com
On Wed, Nov 27, 2013 at 4:55 PM, Ajtim wrote:
> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013
> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>
> When I boot a computer I got one warning:
>
> /etc/rc: WARNING: $tcsd_enable is not set properly
...
--- describe.russian ---
GhostScript not found in PATH
make[5]: "/usr/ports/russian/koi8r-ps/Makefile" line 23: warning:
"/bin/sh /usr/ports/russian/koi8r-ps/files/find-fontmap.sh" returned
non-zero status
It turns out that the Makefile of this port is trying to run
On 6/28/2013 7:31 AM, Anton Shterenlikht wrote:
> This is on amd64 r252033 with ports at 321955:
>
> Running portmaster -a I see this:
>
> ===>>> Returning to update check of installed ports
>
> make: "/usr/ports/graphics/ImageMagick/Makefile" line 83:
This is on amd64 r252033 with ports at 321955:
Running portmaster -a I see this:
===>>> Returning to update check of installed ports
make: "/usr/ports/graphics/ImageMagick/Makefile" line 83: warning: Couldn't
read shell's output for "/bin/sh -c 'case `per
On Fri, Jun 21, 2013 at 04:54:22PM +0200, John Marino wrote:
> On 6/21/2013 16:42, Anton Shterenlikht wrote:
> > On ia64 r252055 with ports at r321471 make issues lots of warnings
> > like:
> >
> > # make -C /usr/ports/ fetchindex make:
> > "/usr/ports/Mk
On 6/21/2013 16:42, Anton Shterenlikht wrote:
On ia64 r252055 with ports at r321471 make issues lots of warnings
like:
# make -C /usr/ports/ fetchindex make:
"/usr/ports/Mk/bsd.port.subdir.mk" line 101: warning: Couldn't read
shell's output for "if /sbin/sysctl -n compa
On ia64 r252055 with ports at r321471
make issues lots of warnings like:
# make -C /usr/ports/ fetchindex
make: "/usr/ports/Mk/bsd.port.subdir.mk" line 101: warning: Couldn't read
shell's output for "if /sbin/sysctl -n compat.ia32.maxvmem >/dev/null 2>&1;
then
15.06.2013 15:07, Alex Kozlov пишет:
> On Sat, Jun 15, 2013 at 02:48:11PM +0400, Boris Samorodov wrote:
>> Just FYI: since we now use USES+=gettext the following warning seems
>> to be stale:
>> -
>> WARN: /usr/ports/sysutils/LPRng/pkg-plist: [18]: installing g
On Sat, Jun 15, 2013 at 02:48:11PM +0400, Boris Samorodov wrote:
> Just FYI: since we now use USES+=gettext the following warning seems
> to be stale:
> -
> WARN: /usr/ports/sysutils/LPRng/pkg-plist: [18]: installing gettext
> translation files, please define USE_GETTEXT
Hi All,
Just FYI: since we now use USES+=gettext the following warning seems
to be stale:
-
WARN: /usr/ports/sysutils/LPRng/pkg-plist: [18]: installing gettext
translation files, please define USE_GETTEXT as appropriate
-
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http
On 13-3-2013 13:07, Chris Torek wrote:
On Sun, Mar 10, 2013 at 3:34 PM, Koop Mast
wrote:
Thanks for the report, this is already known. Sadly I haven't
managed to find a solution for this :/
-Koop
The Makefile in net-im/empathy tries to build its included header
files using glib-mkenums
On Sun, Mar 10, 2013 at 3:34 PM, Koop Mast
wrote:
> Thanks for the report, this is already known. Sadly I haven't
> managed to find a solution for this :/
>
> -Koop
The Makefile in net-im/empathy tries to build its included header
files using glib-mkenums, but it assumes they're in the curr
v-empathy-audio-sink.o
In file included from empathy-audio-sink.c:25:
In file included from
/usr/local/include/gstreamer-0.10/gst/audio/audio.h:26:
In file included from
/usr/local/include/gstreamer-0.10/gst/audio/multichannel.h:21:
/usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:4:11:
6:
In file included from
/usr/local/include/gstreamer-0.10/gst/audio/multichannel.h:21:
/usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:4:11:
warning: extra tokens at end of #ifndef
directive [-Wextra-tokens]
#ifndef __/USR/LOCAL/INCLUDE/GSTREAMER_0.10/GST/AUDIO/AUDIO_ENUM
Hi John,
On Wed, 20 Feb 2013 13:00:18 +0100, John Marino writes:
>On 2/20/2013 12:46, Chris Rees wrote:
>> Simon Gerraty has cleverly written some sed magic that makes the ports
>> tree work with bmake.
There is also a patch for Mk/bsd.port.mk
>> Hopefully it'll be ready at some point, but major
On 2/20/2013 12:46, Chris Rees wrote:
Simon Gerraty has cleverly written some sed magic that makes the ports
tree work with bmake.
Hopefully it'll be ready at some point, but major testing will be
required, since the ports tree has other weird behaviours of pmake that
it relies on.
I'm sure he'
gt;> Well, I'm brave and switched several "beta switches" on my FreeBSD
>> 10.0-CUR systems on and I realize, that I receive a lot of
>>
>> make: "/usr/ports/Mk/bsd.port.mk" line 5137: warning: using previous
>> script for "-depends" def
y FreeBSD
10.0-CUR systems on and I realize, that I receive a lot of
make: "/usr/ports/Mk/bsd.port.mk" line 5137: warning: using previous
script for "-depends" defined here
make: "/usr/ports/Mk/bsd.port.mk" line 5140: warning: duplicate script
for target "-depends&quo
Well, I'm brave and switched several "beta switches" on my FreeBSD
10.0-CUR systems on and I realize, that I receive a lot of
make: "/usr/ports/Mk/bsd.port.mk" line 5137: warning: using previous
script for "-depends" defined here
make: "/usr/ports/Mk/bs
port, then import the data.
Just trying to preserve configuration files and data upon deinstallation
is prone to introduce hard to track errors for this product, so this does
not seem to be a viable option.
Currently, I'm just displaying a warning for 10 seconds during which the
user has time fo
evice-monitor.c:90:1: warning: type specifier missing,
defaults to 'int' [-Wimplicit-int]
cheese_camera_device_monitor_handle_udi (CheeseCameraDeviceMonitor
*monitor,
^~~
cheese-camera-device-monitor.c:109:5: error: no
On 13 January 2013 03:32, Scot Hetzel wrote:
> On Sat, Jan 12, 2013 at 4:31 PM, Anton Shterenlikht
> wrote:
>> If neither csup nor subversion are
>> in base, then how do I get the ports
>> tree in the first instance, if I
>> forgot or intentionally didn't install
>> ports as part of bsdinstall?
On Sat, Jan 12, 2013 at 4:31 PM, Anton Shterenlikht wrote:
> Date: Thu, 10 Jan 2013 08:55:50 -0700 (MST)
> From: Warren Block
>
> Given the upcoming cvs deprecation in a little over a month, how about
> putting a reminder in /usr/ports/UPDATING now?
>
> Men
1 - 100 of 177 matches
Mail list logo
