FreeBSD Port: marble-18.08.3_2
===> Installing for marble-18.12.0 ===> Checking if marble already installed ===> Registering installation for marble-18.12.0 as automatic pkg-static: Unable to access file /usr/ports/astro/marble/work/stage/usr/local/include/marble/NullMarbleWebView.h:No such file or directory pkg-static: Unable to access file /usr/ports/astro/marble/work/stage/usr/local/include/marble/NullTinyWebBrowser.h:No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/astro/marble *** Error code 1 Stop. make: stopped in /usr/ports/astro/marble -- - 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: Apache24/libgdbm.so.4 (mod_php56)
Hi
> The criminal is apr (apr-util).
> httpd is linked with the result of the following command.
>
> > apu-1-config --dbm-libs
> # Actually it is as follows on ${WRKSRC}/configure.in
> # AP_LIBS="$AP_LIBS `$apu_config --avoid-ldap --link-libtool --libs`"
>
> Perhaps, you need to rebuild apache24.
> Because, when gdbm was updated, it was not portrevision bumped.
> https://svnweb.freebsd.org/ports?view=revision=484696
>
That helped I din't think of apache itself only went to the gdbm stuff. After
rebuilding apache24 with portmaster I redid the portmaster -a command and
everything is working fine
Thank you very much
/BR
philippe
___
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: Massive PORTREVSION bump for gcc8
This really answers nothing. Comments below. On Thu, Dec 13, 2018 at 1:36 AM Mathieu Arnold wrote: > On Wed, Dec 12, 2018 at 10:29:59AM -0800, Kevin Oberman wrote: > > This morning the PORTREVISION on at least hundreds of ports was bumped > > because gcc8 was declared as the "canonical" version. As a result, I will > > have about 300 ports to rebuild which will take many hours. > > Why? > > Because they need to be rebuilt so that they use the new default of gcc8. > Why does this matter? They were already working fine with gcc7. Why is it of any significant benefit to the user to do this massive rebuild? I installed gcc8, and I assume some of the rebuilds are using it, though with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang, c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib leaves me mystified as several of those items will not result in the use of gcc, though there may be some reason I miss. Still, this is the cause of the bump for many of the ports that are being rebuilt with clang. But why is this better than just letting gcc8 build port as they otherwise need updating? Again, this build will typically run for hours on many systems, using a great deal of power and slowing other uses of the systems, if they are not dedicated build systems. > If a port is built and running properly with gcc7, I see no reason to > force > > the rebuild of all of the ports that are built with gcc7. > > If you do not want to upgrade, do not upgrade. Now, if you want to keep > up-to-date, well, you do have to rebuild everything with the new gcc > default. > Since PORTREVISION is bumped, there is no quick way to tell whether a port is showing an update because of the gcc8 bump or because of a real update. Yes, I could look through the ports repository for each port and confirm that it does or does not need a rebuild, but this is really not a practical solution. I normally update all ports to LATEST recularly. I know that I am not alone in doing periodic updates. I know that the FreeBSD package building systems will spend days building LATEST packages, again, to no purpose I can discern. After two days of building, with several failures. I still have 45 to go. The only good thing is that, since there are no real updates, the failures don't really impact the system operations. I'd really just like a real, valid reason that this is beneficial. Honestly, I see no benefit to anyone. -- > Mathieu Arnold > Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How much memory to compile www/chromium?
bob prohaska writes:
> On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote:
>
>> ## bob prohaska (f...@www.zefox.net):
>>
>> > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS").
>> > >
>> > Thank you, I think that's the information needed. Come to think of it,
>> > will the -j option, such as -j2, work in this situation also? Two threads
>> > are much better than one 8-)
>>
>> If you had looked into bsd.port.mk yourself... right below the docs of
>> DISABLE_MAKE_JOBS (line 814) is some documentation for MAKE_JOBS_NUMBER
>> and MAKE_JOBS_NUMBER_LIMIT. -j won't help because there's a lot of
>
> Setting MAKE_JOBS_NUMBER_LIMIT=2 seems to have the desired effect. Still,
> top reports four c++ processes, but only two are running and swap use
> seldom exceeds 1GB at worst. So far, that's been enough to prevent stalling.
>
> Editing /usr/ports/Mk/bsd.port.mk looks like it'll affect all ports;
> what's the convention for making the change local to www/chromium only?
MAKE_JOBS_NUMBER_LIMIT is a user variable, so you can either set in
make.conf or Makefile.local e.g.,
$ cat <<\. >>${__MAKE_CONF:-/etc/make.conf}
.if ${.CURDIR:M*/www/chromium}
MAKE_JOBS_NUMBER_LIMIT=2
.endif
___
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: How much memory to compile www/chromium?
On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote: > ## bob prohaska (f...@www.zefox.net): > > > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS"). > > > > > Thank you, I think that's the information needed. Come to think of it, > > will the -j option, such as -j2, work in this situation also? Two threads > > are much better than one 8-) > > If you had looked into bsd.port.mk yourself... right below the docs of > DISABLE_MAKE_JOBS (line 814) is some documentation for MAKE_JOBS_NUMBER > and MAKE_JOBS_NUMBER_LIMIT. -j won't help because there's a lot of Setting MAKE_JOBS_NUMBER_LIMIT=2 seems to have the desired effect. Still, top reports four c++ processes, but only two are running and swap use seldom exceeds 1GB at worst. So far, that's been enough to prevent stalling. Editing /usr/ports/Mk/bsd.port.mk looks like it'll affect all ports; what's the convention for making the change local to www/chromium only? Thanks for your patience! 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: Updating poudriere jail
On 14/12/2018 05:41, Kurt Jaeger wrote: I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the new version 12, what do I have to do to update the poudriere jail? Plus, if I do update, will I have to rebuild all of my installed applications? I had a jail '120' created as poudriere jail -c -v 12.0-RC3 -a amd64 -j 120 I updated it with this: poudriere jail -u -t 12.0-RELEASE -j 120 +1 This upgrade command line has worked for me since 10.x for major and minor upgrades. Yes you will have to let poudriere rebuild your apps since the build process will clean your pkg repro on any jail updates. -- Simon Wright. -- Simon Wright Public key: http://www.santos-wright.net/pki/publickey.gpg smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache24/libgdbm.so.4 (mod_php56)
Hello.
The criminal is apr (apr-util).
httpd is linked with the result of the following command.
> apu-1-config --dbm-libs
# Actually it is as follows on ${WRKSRC}/configure.in
# AP_LIBS="$AP_LIBS `$apu_config --avoid-ldap --link-libtool --libs`"
Perhaps, you need to rebuild apache24.
Because, when gdbm was updated, it was not portrevision bumped.
https://svnweb.freebsd.org/ports?view=revision=484696
Regards.
Philippe Maechler wrote on 2018/12/14 00:05:
(snip)
___
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: Updating poudriere jail
Hi! > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applications? I had a jail '120' created as poudriere jail -c -v 12.0-RC3 -a amd64 -j 120 I updated it with this: poudriere jail -u -t 12.0-RELEASE -j 120 -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ 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: Request for commit approval (multimedia/webcamd)
Hi!
> > Mine last version:
> >
> > # Gamepad Logitech
> > notify 100 {
> > match "system" "USB";
> > match "subsystem" "INTERFACE";
> > match "type""ATTACH";
> > match "vendor" "0x046d";
> > match "product" "0xc216|0xc219";
> > action "/usr/local/etc/rc.d/webcamd start $cdev $interface";
> > };
>
> Can you submit this patch? Or do you want me to?
Please, just commit this fix (approved). Thanks!
> --HPS
>
> Index: files/webcamd.conf.in
> ===
> --- files/webcamd.conf.in (revision 487369)
> +++ files/webcamd.conf.in (working copy)
> @@ -59,12 +59,8 @@
> match "type""ATTACH";
>
> match "vendor" "0x046d";
> - match "product" "0xc216";
> + match "product" "0xc216|0xc219";
>
> - match "intclass""0x03";
> - match "intsubclass" "0x00";
> - match "intprotocol" "0x00";
> -
> action "%%PREFIX%%/etc/rc.d/webcamd start $cdev $interface";
> };
> ___
> 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"
--
p...@freebsd.org +49 171 3101372 2 years to go !
___
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: Request for commit approval (multimedia/webcamd)
On Thu, 13 Dec 2018 22:32:57 +0100
Hans Petter Selasky wrote:
> On 12/13/18 10:31 PM, Rozhuk Ivan wrote:
> > On Thu, 13 Dec 2018 15:33:06 +0100
> > Hans Petter Selasky wrote:
> >
> >> Add devd rule for a Logitech gamepad.
> >>
> >> Submitted by: Rozhuk Ivan
> >> Approved by:
> >>
> >> --HPS
> >
> > Mine last version:
> >
> > # Gamepad Logitech
> > notify 100 {
> > match "system" "USB";
> > match "subsystem" "INTERFACE";
> > match "type""ATTACH";
> > match "vendor" "0x046d";
> > match "product" "0xc216|0xc219";
> > action "/usr/local/etc/rc.d/webcamd start $cdev $interface";
> > };
>
> Hi,
>
> Can you submit this patch? Or do you want me to?
>
You, please.
PS: I start with new webcamd, will email later.
___
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: Request for commit approval (multimedia/webcamd)
On 12/13/18 10:31 PM, Rozhuk Ivan wrote:
On Thu, 13 Dec 2018 15:33:06 +0100
Hans Petter Selasky wrote:
Add devd rule for a Logitech gamepad.
Submitted by: Rozhuk Ivan
Approved by:
--HPS
Mine last version:
# Gamepad Logitech
notify 100 {
match "system""USB";
match "subsystem" "INTERFACE";
match "type" "ATTACH";
match "vendor""0x046d";
match "product" "0xc216|0xc219";
action "/usr/local/etc/rc.d/webcamd start $cdev $interface";
};
Hi,
Can you submit this patch? Or do you want me to?
--HPS
Index: files/webcamd.conf.in
===
--- files/webcamd.conf.in (revision 487369)
+++ files/webcamd.conf.in (working copy)
@@ -59,12 +59,8 @@
match "type" "ATTACH";
match "vendor""0x046d";
- match "product" "0xc216";
+ match "product" "0xc216|0xc219";
- match "intclass" "0x03";
- match "intsubclass" "0x00";
- match "intprotocol" "0x00";
-
action "%%PREFIX%%/etc/rc.d/webcamd start $cdev $interface";
};
___
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: Request for commit approval (multimedia/webcamd)
On Thu, 13 Dec 2018 15:33:06 +0100
Hans Petter Selasky wrote:
> Add devd rule for a Logitech gamepad.
>
> Submitted by: Rozhuk Ivan
> Approved by:
>
> --HPS
Mine last version:
# Gamepad Logitech
notify 100 {
match "system" "USB";
match "subsystem" "INTERFACE";
match "type""ATTACH";
match "vendor" "0x046d";
match "product" "0xc216|0xc219";
action "/usr/local/etc/rc.d/webcamd start $cdev $interface";
};
___
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: Updating poudriere jail
On Thu 2018-12-13 19:43:30 UTC+, Carmel NY (carmel...@outlook.com) wrote: > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applications? > > Thanks :) I found it simplest to create a new poudriere jail named 12amd64 to coincide with my existing 11amd64 jail. In my case the only port I build that needs non-standard options is mail/postfix, to enable Cyrus SASL support. Consequently I have this setting in /usr/local/etc/poudriere.d/make.conf (outside the jail) which from what I understand applies to both my 11amd64 and 12amd64 (and future) poudriere jails: # build Postfix with Cyrus SASL support mail_postfix_SET=SASL Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 repo, instead of your old 11.x repo. Regards Andrew ___ 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: Best way to deal with .pyc files?
On 12/13/18 1:35 AM, Mathieu Arnold wrote:
> On Mon, Dec 10, 2018 at 11:22:49AM -0800, John Baldwin wrote:
>> On 12/7/18 10:17 AM, John Baldwin wrote:
>>> On 12/6/18 11:17 AM, Michael Gmelin wrote:
> On 6. Dec 2018, at 19:21, John Baldwin wrote:
>
> The devel/gdb port installs python scripts into
> /usr/local/share/gdb/python.
> If you then run kgdb as root (not that unusual), it will generate .pyc
> files in
> those directories that are not deleted by 'pkg delete'. What is the best
> way to
> handle this case? Should the pkg-plist include @rmtry entries for each
> pyc
> file or is there a better way?
>
Pre-generate the pyc files on package build and install them with the
port, so they become part of plist (there are examples of that in the
ports tree, whenever possible for both py27 and py3x).
>>>
>>> Ok. One follow-up question. GDB's python bindings work with both py2 and
>>> py3, but the bindings are optional. Right now PYTHON is a port option
>>> (but on by default). If I wanted to add flavors I would probably want them
>>> to be conditional on the option, so the results would be 'gdb' and
>>> 'gdb-py3' packages by default, but if someone was using poudriere locally
>>> and disabled python, I would only want to build a single 'gdb' without
>>> python. So, can I make the flavors conditional on an option or is it too
>>> late to define flavors after including bsd.ports.options.mk?
>>>
>>> That is, can I do something this:
>>>
>>> OPTIONS_DEFINE= PYTHON
>>> OPTIONS_DEFAULT= PYTHON
>>>
>>> .include
>>>
>>> .if ${PORT_OPTIONS:MPYTHON}
>>> USES_PYTHON= flavors
>>> .endif
>>
>> FYI, this worked:
>
> All things considered, it does not matter when you set
> USE_PYTHON=flavors because it does nothing if USES does not contain python.
Yes, I eventually figured this out and the current patch just sets USE_PYTHON
unconditionally.
--
John Baldwin
___
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: Updating poudriere jail
On Thu, Dec 13, 2018 at 1:01 PM Carmel NY wrote:
>
> On Thu, 13 Dec 2018 12:49:07 -0700, Adam Weinberger stated:
>
> >On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote:
> >>
> >> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
> >> new version 12, what do I have to do to update the poudriere jail? Plus,
> >> if I do update, will I have to rebuild all of my installed applications?
> >
> >It's not really possible to cleanly upgrade a poudriere jail to a new
> >major. You'll need to delete the jail and recreate it.
> > poudriere jail -d -j $jailname
> > poudriere jail -c -j $jailname -v 12.0-RELEASE
> >
> >If the jail name stays the same, it will retain all the options,
> >make.conf, and poudriere.conf. If the jail name has changed, you'll
> >most likely want to move those things over:
> > cd /usr/local/etc/poudriere.d
> > mv oldjailname-{make.conf,poudriere.conf,options,etc} newjailname-...
> >
> >You will, unfortunately, need to rebuild everything. After rebuilding,
> >be sure to run "pkg upgrade -f" BEFORE the final "freebsd-update
> >install"!
> >
> ># Adam
>
> I build my packages. Do I really have to do the "pkg upgrade -f" procedure?
Yeah, it is necessary. The packages that are on your system are linked
against the 11.2 libraries. Once you do the final "freebsd-update
install", those 11.2 libraries will disappear. As a result, every
package you have installed will break. Rebuild everything, then "pkg
upgrade -f" to reinstall all the packages using the newly built
versions. That way, nothing will break after the final freebsd-update
install.
# 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: Updating poudriere jail
On Thu, 13 Dec 2018 12:49:07 -0700, Adam Weinberger stated:
>On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote:
>>
>> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
>> new version 12, what do I have to do to update the poudriere jail? Plus,
>> if I do update, will I have to rebuild all of my installed applications?
>
>It's not really possible to cleanly upgrade a poudriere jail to a new
>major. You'll need to delete the jail and recreate it.
> poudriere jail -d -j $jailname
> poudriere jail -c -j $jailname -v 12.0-RELEASE
>
>If the jail name stays the same, it will retain all the options,
>make.conf, and poudriere.conf. If the jail name has changed, you'll
>most likely want to move those things over:
> cd /usr/local/etc/poudriere.d
> mv oldjailname-{make.conf,poudriere.conf,options,etc} newjailname-...
>
>You will, unfortunately, need to rebuild everything. After rebuilding,
>be sure to run "pkg upgrade -f" BEFORE the final "freebsd-update
>install"!
>
># Adam
I build my packages. Do I really have to do the "pkg upgrade -f" procedure?
--
Carmel
___
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: Updating poudriere jail
On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote:
>
> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
> new version 12, what do I have to do to update the poudriere jail? Plus, if I
> do update, will I have to rebuild all of my installed applications?
It's not really possible to cleanly upgrade a poudriere jail to a new
major. You'll need to delete the jail and recreate it.
poudriere jail -d -j $jailname
poudriere jail -c -j $jailname -v 12.0-RELEASE
If the jail name stays the same, it will retain all the options,
make.conf, and poudriere.conf. If the jail name has changed, you'll
most likely want to move those things over:
cd /usr/local/etc/poudriere.d
mv oldjailname-{make.conf,poudriere.conf,options,etc} newjailname-...
You will, unfortunately, need to rebuild everything. After rebuilding,
be sure to run "pkg upgrade -f" BEFORE the final "freebsd-update
install"!
# 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"
Updating poudriere jail
I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the new version 12, what do I have to do to update the poudriere jail? Plus, if I do update, will I have to rebuild all of my installed applications? Thanks :) -- Carmel ___ 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: Pourdriere begginner
> Hello, > > Poudriere is installed, poudriere.conf adjusted to my config, then I > create the firts jail, following handbook/ports-poudriere.html : > > > poudriere jail -c -j 12amd64 -v 12.0-STABLE > > > > > > > > [00:00:00] Creating 12amd64 fs at /usr/local/poudriere/jails/12amd64... done > > [00:00:01] Fetching MANIFEST for FreeBSD 12.0-STABLE amd64 > > /usr/local/poudriere/jails/12amd64/fromftp/MAN 1045 B 13 MBps 00s > > [00:00:02] Fetching base for FreeBSD 12.0-STABLE amd64 > > fetch: > > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz: > > Not Found > > fetch: > > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz: > > Not Found > > [00:00:02] Error: Failed to fetch from > > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz > > [00:00:02] Error while creating jail, cleaning up. > > [00:00:02] Removing 12amd64 jail... done > > [00:00:04] Cleaning 12amd64 data... done > > What did I wrong ? Try poudriere jail -c -j 12amd64 -v 12.0-RELEASE Lorenzo Salvadore. ___ 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: A potential new porter seeking some clarifications
On Thu, Dec 13, 2018 at 11:00 AM George Mitchell wrote: > > On 12/13/18 10:06 AM, Matthew Seaman wrote: > > [...] So long as you have sufficient disk space > > and you aren't trying to rebuild the entire ports tree, it can work well > > on a very ordinary desktop machine. [...] > > Still getting used to the idea that a machine with >16GB would today > be considered a "very ordinary desktop machine." -- Decrepit old George Do yourself a favour though and use ZFS. Poudriere is fast and elegant on ZFS. It is unavoidably painfully slow on UFS/FFS. # 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"
Pourdriere begginner
Hello, Poudriere is installed, poudriere.conf adjusted to my config, then I create the firts jail, following handbook/ports-poudriere.html : > # poudriere jail -c -j 12amd64 -v 12.0-STABLE > [00:00:00] Creating 12amd64 fs at /usr/local/poudriere/jails/12amd64... done > [00:00:01] Fetching MANIFEST for FreeBSD 12.0-STABLE amd64 > /usr/local/poudriere/jails/12amd64/fromftp/MAN1045 B 13 MBps00s > [00:00:02] Fetching base for FreeBSD 12.0-STABLE amd64 > fetch: > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz: > Not Found > fetch: > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz: > Not Found > [00:00:02] Error: Failed to fetch from > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz > [00:00:02] Error while creating jail, cleaning up. > [00:00:02] Removing 12amd64 jail... done > [00:00:04] Cleaning 12amd64 data... done What did I wrong ? Thanks Regards Xavier -- Xavier Humbert - sysadmin & 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: A potential new porter seeking some clarifications
On 12/13/18 10:06 AM, Matthew Seaman wrote: > [...] So long as you have sufficient disk space > and you aren't trying to rebuild the entire ports tree, it can work well > on a very ordinary desktop machine. [...] Still getting used to the idea that a machine with >16GB would today be considered a "very ordinary desktop machine." -- Decrepit old George signature.asc Description: OpenPGP digital signature
Re: A potential new porter seeking some clarifications
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote: > Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing > on one package, a plugin for bitlbee, however I’d like to extend my hand to > maintain other ports in the future once I have more knowledge and practice > with the system. Hello! > Before I start, though, I just need some clarifications of things from the > porter’s handbook. > > 1. If I understand correctly, the version of the ports tree as fetched by > portsnap isn’t the best for working on the tree. I should instead make > another copy of the tree as an svn checkout? Distfiles, however, still go to > /usr/ports/distfiles You don't necessary need use a separated copy of the ports tree, you can use a svn copy in the default location; however it can become a bit problematic sometimes, like when you are working on ports that you use but you won't/can't use the updated version yet. Portsnap is intended for end users only, so it is not really practical to use while working with ports, and you can get all your work deleted with a random tree update. ;-) > 2. Is it absolutely necessary to use poudriere before submitting a port? >I’m still getting to grips with how it works, and if I need to get >comfortable with it first, I’ll do so. Poudriere is the default tool to test ports. The `poudriere testport` facility does several extra checks during the building-packaging process. So, it is very desirable to have its logs when you fill a bug report, since it can speed up the review process. Some help with poudriere: https://github.com/freebsd/poudriere/wiki This is a bit old but still helpful: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-poudriere-build-system-to-create-packages-for-your-freebsd-servers > Thanks! > Arthur You're welcome. > ___ > 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" -- Best Regards, Alexandre C. Guimarães. https://bitbucket.org/rigoletto-freebsd/ signature.asc Description: PGP signature
Re: A potential new porter seeking some clarifications
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote: > Hi all! I’m hoping to get into porting for FreeBSD, right now just > focusing on one package, a plugin for bitlbee, however I’d like to > extend my hand to maintain other ports in the future once I have more > knowledge and practice with the system. Welcome! :-) > > Before I start, though, I just need some clarifications of things from the > porter’s handbook. > > 1. If I understand correctly, the version of the ports tree as fetched > by portsnap isn’t the best for working on the tree. I should instead > make another copy of the tree as an svn checkout? Distfiles, however, > still go to /usr/ports/distfiles You can change this by setting DISTDIR variable in /etc/make.conf to a directory you like. See ports(7) manpage. > 2. Is it absolutely necessary to use poudriere before submitting a > port? I’m still getting to grips with how it works, and if I need to > get comfortable with it first, I’ll do so. That really depends on the change's size. Trivial patches can often be sub-/committed without a poudriere run. portlint -ac, make check-plist and make package can find potential issues for you. Bigger changes should be build in poudriere. You don't need to attach the logs to the PR, though. ___ 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: A potential new porter seeking some clarifications
On 13/12/2018 14:41, Arthur Pirika wrote: 1. If I understand correctly, the version of the ports tree as fetched by portsnap isn’t the best for working on the tree. I should instead make another copy of the tree as an svn checkout? Distfiles, however, still go to /usr/ports/distfiles If you're going to be submitting patches or creating Phabricator reviews, then it is definitely recommended that you checkout the ports out of either SVN or Git -- whichever you prefer -- and generate your diffs against the head of the development tree (eg. by 'svn diff'). Although there is a copy of the ports tree available via GitHub, don't try using GitHub to create pull requests for the ports. At worst, no one will notice and at best you'll just be asted to re-submit your diff as a PR or a Phab. review. Using one common distfiles location is usually what you'ld want to do in order to save on repeated downloads of the same distfiles. 2. Is it absolutely necessary to use poudriere before submitting a port? I’m still getting to grips with how it works, and if I need to get comfortable with it first, I’ll do so. It's absolutely necessary to test your work, and the generally accepted way to do that involves using poudriere to do clean-room builds. Other testing methodologies are possible, but generally less effective and less convenient. Don't be frightened of poudriere: it's much easier and nicer to use than many people seem to think. So long as you have sufficient disk space and you aren't trying to rebuild the entire ports tree, it can work well on a very ordinary desktop machine. Cheers, Matthew ___ 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"
Apache24/libgdbm.so.4 (mod_php56)
Hi I'm updating several FreeBSD 11.2-p4 Boxes to the latest FreeBSD Version 11.2-p6 including Ports with portmaster. After doing the first two boxes, apache couldn't start because the libgdbm.so.4 is missing. My solution was to go into the apache ports dir, make deinstall reinstall and everything was working again Further boxes didn't had any issues with the port/module, they worked fine after the upgrade. My current box gives me a somewhat similar error message: ===>>> www/mod_php56 1/11 ===>>> Currently installed version: mod_php56-5.6.38 ===>>> Port directory: /usr/ports/www/mod_php56 Shared object "libgdbm.so.4" not found, required by "httpd" Shared object "libgdbm.so.4" not found, required by "httpd" Shared object "libgdbm.so.4" not found, required by "httpd" ===> Cleaning for mod_php56-5.6.39 Shared object "libgdbm.so.4" not found, required by "httpd" Shared object "libgdbm.so.4" not found, required by "httpd" Shared object "libgdbm.so.4" not found, required by "httpd" ===> mod_php56-5.6.39 is marked as broken: : Error from apache.mk. Apache is installed and port requires 2.4. *** Error code 1 Stop. make: stopped in /usr/ports/www/mod_php56 ===>>> make build failed for www/mod_php56 ===>>> Aborting update ===>>> Update for www/mod_php56 failed ===>>> Aborting update The interesting part is, that apache24 is installed. What "2.4" is required? # pkg info | grep apac apache-xml-security-c-2.0.2Apache XML security libraries - C++ version apache24-2.4.37Version 2.4.x of Apache web server # My make.conf has some old entries in it # cat /etc/make.conf WITH_PKGNG= yes DEFAULT_VERSIONS+=perl5=5.24 # The system is running a 11.2-RELEASE-p4 kernel (-p6 is installed) The command used to upgrade the ports is portmaster -no-term-title -bD -a Then I got the above failure and tried to reinstall gdbm with portmaster -no-term-title -bD gdbm And afterwards the command portmaster gave me with the error message portmaster --no-term-title -bD www/mod_php56 databases/mysql56-server emulators/open-vm-tools-nox11 devel/php56-pcntl devel/pear@php56 net/php56-sockets databases/phpmyadmin@php56 lang/cython@py27 lang/ruby24 devel/subversion security/sudo /usr/ports/UPDATING only has something for */py* from 20171130 and gdb, is only mentioned as an example Maybe someone can help me get rid of these gdbm "issues"? Best regards Philippe ___ 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: Request for commit approval (multimedia/webcamd)
Hi! > Add devd rule for a Logitech gamepad. > > Submitted by: Rozhuk Ivan > Approved by: Approved by: pi -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ 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"
A potential new porter seeking some clarifications
Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing on one package, a plugin for bitlbee, however I’d like to extend my hand to maintain other ports in the future once I have more knowledge and practice with the system. Before I start, though, I just need some clarifications of things from the porter’s handbook. 1. If I understand correctly, the version of the ports tree as fetched by portsnap isn’t the best for working on the tree. I should instead make another copy of the tree as an svn checkout? Distfiles, however, still go to /usr/ports/distfiles 2. Is it absolutely necessary to use poudriere before submitting a port? I’m still getting to grips with how it works, and if I need to get comfortable with it first, I’ll do so. Thanks! Arthur ___ 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"
Request for commit approval (multimedia/webcamd)
Add devd rule for a Logitech gamepad.
Submitted by: Rozhuk Ivan
Approved by:
--HPS
Index: Makefile
===
--- Makefile (revision 487368)
+++ Makefile (working copy)
@@ -3,6 +3,7 @@
PORTNAME= webcamd
PORTVERSION= 4.20.0.1
+PORTREVISION= 1
CATEGORIES= multimedia
MASTER_SITES= http://www.selasky.org/hans_petter/distfiles/ \
http://home.selasky.org/distfiles/
Index: files/webcamd.conf.in
===
--- files/webcamd.conf.in (revision 487365)
+++ files/webcamd.conf.in (working copy)
@@ -51,3 +51,20 @@
action "%%PREFIX%%/etc/rc.d/webcamd start $cdev $interface";
};
+
+# Logitech gamepad
+notify 100 {
+ match "system" "USB";
+ match "subsystem" "INTERFACE";
+ match "type" "ATTACH";
+
+ match "vendor" "0x046d";
+ match "product" "0xc216";
+
+ match "intclass" "0x03";
+ match "intsubclass" "0x00";
+ match "intprotocol" "0x00";
+
+ action "%%PREFIX%%/etc/rc.d/webcamd start $cdev $interface";
+};
+
___
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: Request for commit approval (multimedia/webcamd)
Hi! > Update webcamd to version 4.20.0.1 > > This change updates the Linux source code to Linux v4.20 and fixes use > of USB HID Joysticks with webcamd. > > Approved by: Approved by: pi -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ 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"
Request for commit approval (multimedia/webcamd)
Hi, Update webcamd to version 4.20.0.1 This change updates the Linux source code to Linux v4.20 and fixes use of USB HID Joysticks with webcamd. Approved by: Index: Makefile === --- Makefile (revision 487365) +++ Makefile (working copy) @@ -2,11 +2,10 @@ # $FreeBSD$ PORTNAME= webcamd -PORTVERSION= 4.17.0.3 -PORTREVISION= 1 +PORTVERSION= 4.20.0.1 CATEGORIES= multimedia MASTER_SITES= http://www.selasky.org/hans_petter/distfiles/ \ - http://home.selasky.org:8192/distfiles/ + http://home.selasky.org/distfiles/ MAINTAINER= hsela...@freebsd.org COMMENT= Port of Linux USB webcam and DVB drivers into userspace Index: distinfo === --- distinfo (revision 487365) +++ distinfo (working copy) @@ -1,3 +1,3 @@ -TIMESTAMP = 1531558340 -SHA256 (webcamd-4.17.0.3.tar.bz2) = b52b29be861a469c230004c979e10b22bb7c1e12e84eab18553985acc1b8 -SIZE (webcamd-4.17.0.3.tar.bz2) = 13684415 +TIMESTAMP = 1544709894 +SHA256 (webcamd-4.20.0.1.tar.bz2) = c4741e68fef6f51bd6eeda232446d9dcac8d6b9e2a4709ca68f4a6696ec986ea +SIZE (webcamd-4.20.0.1.tar.bz2) = 13416890 ___ 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 +-+ devel/ocaml-ipaddr | 2.6.1 | 2.9.0 +-+ sysutils/freefilesync | 9.8 | 10.7 +-+ 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 Thanks. ___ 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: Massive PORTREVSION bump for gcc8
On Wed, Dec 12, 2018 at 10:29:59AM -0800, Kevin Oberman wrote: > This morning the PORTREVISION on at least hundreds of ports was bumped > because gcc8 was declared as the "canonical" version. As a result, I will > have about 300 ports to rebuild which will take many hours. > Why? Because they need to be rebuilt so that they use the new default of gcc8. > If a port is built and running properly with gcc7, I see no reason to force > the rebuild of all of the ports that are built with gcc7. If you do not want to upgrade, do not upgrade. Now, if you want to keep up-to-date, well, you do have to rebuild everything with the new gcc default. -- Mathieu Arnold signature.asc Description: PGP signature
Re: Best way to deal with .pyc files?
On Mon, Dec 10, 2018 at 11:22:49AM -0800, John Baldwin wrote:
> On 12/7/18 10:17 AM, John Baldwin wrote:
> > On 12/6/18 11:17 AM, Michael Gmelin wrote:
> >>
> >>
> >>> On 6. Dec 2018, at 19:21, John Baldwin wrote:
> >>>
> >>> The devel/gdb port installs python scripts into
> >>> /usr/local/share/gdb/python.
> >>> If you then run kgdb as root (not that unusual), it will generate .pyc
> >>> files in
> >>> those directories that are not deleted by 'pkg delete'. What is the best
> >>> way to
> >>> handle this case? Should the pkg-plist include @rmtry entries for each
> >>> pyc
> >>> file or is there a better way?
> >>>
> >>
> >> Pre-generate the pyc files on package build and install them with the
> >> port, so they become part of plist (there are examples of that in the
> >> ports tree, whenever possible for both py27 and py3x).
> >
> > Ok. One follow-up question. GDB's python bindings work with both py2 and
> > py3, but the bindings are optional. Right now PYTHON is a port option
> > (but on by default). If I wanted to add flavors I would probably want them
> > to be conditional on the option, so the results would be 'gdb' and
> > 'gdb-py3' packages by default, but if someone was using poudriere locally
> > and disabled python, I would only want to build a single 'gdb' without
> > python. So, can I make the flavors conditional on an option or is it too
> > late to define flavors after including bsd.ports.options.mk?
> >
> > That is, can I do something this:
> >
> > OPTIONS_DEFINE= PYTHON
> > OPTIONS_DEFAULT= PYTHON
> >
> > .include
> >
> > .if ${PORT_OPTIONS:MPYTHON}
> > USES_PYTHON= flavors
> > .endif
>
> FYI, this worked:
All things considered, it does not matter when you set
USE_PYTHON=flavors because it does nothing if USES does not contain python.
--
Mathieu Arnold
signature.asc
Description: PGP signature
