On Tue, May 04, 2021 at 08:10:38AM -0600, @lbutlr wrote:
> With the move to FreeBSD 13.0 is there a simple (single step) way to
> reinstall all the current ports other than saving off a list of the ports and
> then stepping through that list to reinstall them? It was very inefficient
> when
, the 12.x dialog4ports was still going to fail
as the 12.x version of those libraries were already broken. I haven't checked
to see if the affected libraries have been added to misc/compat12x.
--
John Baldwin
___
freebsd-ports@freebsd.org mailing list
ht
Can someone take a look at bug # 252928?
I don't guarantee that it is anywhere near the right thing to do, but my
general issues trying to compile net/ipxe are:
net/ipxe requires mformat from emultators/mtools
When mtools is built, it gets libiconv loaded because of texinfo
On Fri, Feb 05, 2021 at 04:43:58AM -0800, David Wolfskill wrote:
> dmesg reports:
>
> link_elf_obj: symbol nvidia_driver_name undefined
> linker_load_file: /boot/modules/nvidia.ko - unsupported file type
> KLD nvidia-modeset.ko: depends on nvidia - not available or version mismatch
>
On Sun, Dec 27, 2020 at 03:49:10PM -0800, Dan Mahoney (Gushi) wrote:
> Hey there all.
>
> This is a "don't try this at home" question. This is not something I'm
> asking how to do in the general case, but I'd like to know.
>
> It seems recently (since 1.1.1, OpenSSL has deprecated a number of
On Sat, Dec 26, 2020 at 07:23:59PM -0800, Thomas Mueller wrote:
> ... An improved portmaster arouses my interest. Maybe modify the name so it
> can be added to the ports tree and coexist with the "official" portmaster.
> Desired features/options would be to keep going rather than stop when one
On Tue, Dec 22, 2020 at 05:25:41PM -0800, John Kennedy wrote:
> On Tue, Dec 22, 2020 at 08:47:35PM +0100, Christian Ullrich wrote:
> > Hello,
> >
> > I have started to notice poudriere builds of Python ports with compiled
> > extensions failing:
> >
> >
On Tue, Dec 22, 2020 at 08:47:35PM +0100, Christian Ullrich wrote:
> Hello,
>
> I have started to notice poudriere builds of Python ports with compiled
> extensions failing:
>
> [00:00:11] /usr/bin/strip
>
John-Mark Gurney wrote this message on Thu, Nov 05, 2020 at 16:13 -0800:
> I just discovered that we have a variable name colission between the
> FreeBSD base repo, and the ports tree. DISTDIR is used by the ports
> repo for:
> # DISTDIR - Where to search for and
someone figure out what we should do in this case?
This was discovered because ezjail-admin sets DISTDIR for ports, but it
was breaking my -DNO_ROOT installworld by putting the METALOG in an
incorrectly documented place (since fixed)...
--
John-Mark Gurney Voice: +1
On Fri, Sep 18, 2020 at 08:17:35PM +, Pau Amma wrote:
> On 2020-09-18 17:58, Carmel NY wrote:
> > On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:
> >> See
> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> >> and
On Sat, Apr 04, 2020 at 07:41:54PM -0400, Robert Huff wrote:
> Jonathan Chen writes:
>
>> Frankly speaking, if you're compiling your own ports, you
>> have to use either synth or poudriere; anything else will cost you
>> time hunting down broken dependencies.
>
> Speaking as someone
] databases/rrdtool: "VRULE:0" may cause segmentation fault
https://bugs.freebsd.org/244808
Thank you,
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
On Fri, Mar 13, 2020 at 11:25:51AM -0700, John Kennedy wrote:
> There seems to be something similar going on for devel/llvm10, and probably a
> lot more since they do the same kind of comparison.
Seems to be fixed as of 528375 (somewhere between e9ecbe62adad..71e1eb7115a2;
revision
On Fri, Mar 13, 2020 at 06:04:38PM +, Ports Index build wrote:
> --- describe.biology ---
> make[5]: "/home/indexbuild/tindex/ports/biology/canu/Makefile" line 34:
> warning: String comparison operator should be either == or !=
> make[5]: "/home/indexbuild/tindex/ports/biology/star/Makefile"
On Thu, Mar 12, 2020 at 12:22:21AM +, Grzegorz Junka wrote:
> On 10/03/2020 19:46, Hans Petter Selasky wrote:
> > On 2020-03-10 20:29, Grzegorz Junka wrote:
> > >
> > > On 09/03/2020 23:04, Hans Petter Selasky wrote:
> > > > On 2020-03-10 00:03, Grzegorz Junka wrote:
> > > > > I've upgraded
at folks have a lot of demands on their
time, PR surge or not, and appreciate your taking the time on this one.
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
Hello FreeBSD Ports,
This contribution [0] has been awaiting attention for about four weeks,
since 2020-02-01 22:20:44 UTC. Are there any friendly, neighborhood
committers who would be willing and available to take it?
[0] https://bugs.freebsd.org/243787
--
John W. O'Brien
OpenPGP keys
On Sat, Feb 15, 2020 at 09:02:39PM -0700, @lbutlr wrote:
> On 15 Feb 2020, at 16:32, @lbutlr wrote:
> > Sorry for the rather basic questions.
>
> Thanks everyone for your comments. One more dumb question I can???t find the
> answer to.
>
> Let???s say I want to build and install a single port
his in clang properly, though.
I think using the hack patch in devel/freebsd-gcc* is fine for now, but can
you confirm if both 6 and 9 need it or only 9?
--
John Baldwin
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf
https://bugs.freebsd.org/241766
Thank you,
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
On Mon, Oct 21, 2019 at 01:59:17PM +0100, Matthew Seaman wrote:
> On 21/10/2019 13:31, Sergei Vyshenski wrote:
> > Is it possible to instruct "poudriere testport" such
> > that it downloads depends (in a form of binary packages) from the
> > central repository,
> > and actually tests only the
eBSD toolchain. I would ask bapt@ and/or
manu@ what they think about having you maintain the bare metal ports.
--
John Baldwin
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send an
ls than gcc 4.2.1 based ones.
>> As I understand, being in devel/ instead of lang/ for gcc tools is tied to
>> being constructed for the system-building activities instead of for general
>> use.
>>
>> You might want to show your Makefile updates so that that the problem
UTF-8 to current locale.
[00:00:03] tar: Error exit delayed from previous errors.
[00:00:03] *** Error code 1
locale:
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
SVN
https://svn.freeb
On Sun, Dec 16, 2018 at 07:54:34AM -0500, George Mitchell wrote:
> On 12/15/18 1:10 PM, George Mitchell wrote:
> > I recently updated my port build machine to 11.2-RELEASE. I'm in the
> > process of recompiling my (previously) 10.4-based ports to 11.2, and
> > perhaps I shouldn't be trying to do
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 1
sure what the right solution is,
but it seems like 'pkg upgrade' of the previous default flavor should
upgrade to the new default flavor if the default flavor changes rather than
getting stuck on an old version (that in my case my poudriere build didn't
rebuild).
--
Jo
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.
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 .p
entries for each pyc
file or is there a better way?
--
John Baldwin
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
crypto_rsa.c:163:3: error: incomplete definition of type 'struct rsa_st'
r->e = get_key()->k_rsa->e;
~^
/usr/include/openssl/ossl_typ.h:110:16: note: forward declaration of 'struct
rsa_st'
typedef struct rsa_st RSA;
^
crypto_rsa.c:163:25: error: inco
s! It took me a while to clean up after the
> 12/openssl111 update.
>
Thank you, Kurt.
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
On 2018/10/26 19:41, John W. O'Brien wrote:
> On 2018/10/06 16:31, John W. O'Brien wrote:
>> Hello FreeBSD-Python,
>>
>> Are there any friendly neighborhood committers available to take
>> Nathan's patch [0]?
>>
>> [0] https://bugs.freebsd.org/231189
>
On 2018/10/06 16:31, John W. O'Brien wrote:
> Hello FreeBSD-Python,
>
> Are there any friendly neighborhood committers available to take
> Nathan's patch [0]?
>
> [0] https://bugs.freebsd.org/231189
Hello FreeBSD Ports,
Nathan's patch hasn't been getting any love over
PORT] devel/py-selectors2: Backported, durable, and portable
I/O selectors for python
https://bugs.freebsd.org/230873
[1] net-mgmt/py-ncclient: Update to 0.6.2
https://bugs.freebsd.org/230874
Thank you,
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description
Hello,
On Sun, 26 Aug 2018, at 12:12, Kubilay Kocak wrote:
> On 26/08/2018 9:07 pm, John wrote:
> > Hello lists,
> >
> > x11/nvidia-driver is broken again.
> >
> > Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
> >
> > Tried to bui
Hello lists,
x11/nvidia-driver is broken again.
Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
Tried to build with make distclean clean rmconfig && make MAKE_JOBS_UNSAFE=yes
It fails here:
=kernel -Wno-sign-compare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG
-Werror=undef
endif
> .endif
>
> (Not that I expect that this is tied to what I've been trying
> to figure out about lack of installing into staging.)
I'm not sure why that change is needed, but I also suspect it is
needed for armv7 and was just missed. Currently there isn't a
arm-gcc port for an external tool
On 2018/05/18 16:32, John W. O'Brien wrote:
> On 5/18/18 14:20, Kurt Jaeger wrote:
>> Hi!
>>
>>>>>>> The FreeBSD project could help by asking committers to qualify
>>>>>>> "Sponsored by" lines to indicate which participant
On 2018/05/18 07:38, John W. O'Brien wrote:
> On 2018/05/18 00:15, Kurt Jaeger wrote:
>> Hi!
>>
>>> The FreeBSD project could help by asking committers to qualify
>>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>>>
r to committers, or suggestive wording change, to fix-up
the the sponsorship line when applicable. I will submit a separate bug
with a candidate change that depends on the doc bug. I won't mind if the
doc bug is accepted and the subversion portbug is closed WONTFIX upon
review.
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
> One thing to note: FreeBSD has a custom patch to subversion to detect
> "ORGANIZATION_NAME" and automatically append it to the default
> template. This is likely why its getting added in unexpected places.
>
How do you think I should handle that in my forthcoming doc pat
gh. Also, since this would apply to trees
besides ports, is there a venue besides this list where I should solicit
feedback?
[0]
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#commit-log-message
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
maintainer)", or...]
Are non-committer contributors entitled to specify sponsorship credits?
Should I start requesting sponsorship credit under the name of my small,
one-man consulting operation? If I do, would that discourage committers
from taking my bugs who want to be able to credit
On 2018/05/17 19:18, Maxim Sobolev wrote:
> John, no, not really, sorry. Work is done, credit is given. The form and
> amount of this credit is between whoever does the work and whoever is
> being credited. I don't see why is there any third-party to be involved
> in gover
On 2018/05/14 20:25, Julian Elischer wrote:
> On 15/5/18 7:40 am, John W. O'Brien wrote:
>> Hello FreeBSD Ports,
>>
>> The Committer's Guide section on Commit Log Messages [0], doesn't cover
>> the use of the "Sponsored by" key word. As a non-committer cont
On 2018/05/14 20:14, Maxim Sobolev wrote:
> What's wrong with a current practice. Why is it of any concern to you,
> John? Just curious that is not very clear from your message. It is like
> someone trying to moderate what people in general or some group in
> particular (e.g. freebs
ps://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#commit-log-message
PS: I realize that this issue transcends ports, but it's not clear where
I should send this instead, and this list seems like it would have a
reasonably high concentration of people with a stake in the
https://bugs.freebsd.org/227812
Thank you,
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
signature.asc
Description: OpenPGP digital signature
On 2018/03/01 23:04, John W. O'Brien wrote:
> These new ports have not gotten any committer love for some time. I
> would appreciate any feedback or to have them added to the ports tree.
[...]
> 2017-12-26
> www/py-flask-moment
> https://bugs.freebsd.org/224587
>
> 2017-12-26
On 04/03/2018 07:37, Oleksandr Tymoshenko wrote:
> There is ongoing work on using RPi firmware port for all RPi models and
> switching u-boot-rpi3 to the same framework as u-boot-rpi2 but it
> involves changes across multiple areas (drivers, ports, release
> scripts). Some of this stuff is already
e. Committed, thanks very much!
>
Thank you, Kurt.
nork: Congratulations on your new port.
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
0x474ABD3C1A7B3F70 (expires 2018-03-14)
signature.asc
Description: OpenPGP digital signature
daemon
implemented in golang.
https://bugs.freebsd.org/218678
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
0x474ABD3C1A7B3F70 (expires 2018-03-14)
signature.asc
Description: OpenPGP digital signature
9:48 -0500 (Mon, 12 Feb 2018) | 10 lines
Submitted by: w.schwarzenf...@utanet.at
$ svn diff -c 461559 /usr/ports | grep MAINTAINER
+MAINTAINER=t...@freebsd.org
Nothing against tj@, by the way.
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
0x474ABD3C1A7B3F70 (expires
/show_bug.cgi?id=225508
Thank you,
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
0x474ABD3C1A7B3F70 (expires 2018-03-14)
signature.asc
Description: OpenPGP digital signature
On 2018/02/04 14:02, John W. O'Brien wrote:
> On 2018/01/27 12:20, John W. O'Brien wrote:
>> I would appreciate review [0] and test of my proposed patch to update
>> the ELK stack ports to the latest version in the 5.x series.
>>
>> The maintainer has not yet respond
On 2018/01/27 12:20, John W. O'Brien wrote:
> I would appreciate review [0] and test of my proposed patch to update
> the ELK stack ports to the latest version in the 5.x series.
>
> The maintainer has not yet responded to my request for review.
>
> [0] https://reviews.freebsd.
Good day FreeBSD Ports,
I would appreciate review [0] and test of my proposed patch to update
the ELK stack ports to the latest version in the 5.x series.
The maintainer has not yet responded to my request for review.
[0] https://reviews.freebsd.org/D14003
Thank you,
--
John W. O'Brien
On 2017/11/09 09:30, Ryan Steinmetz wrote:
> On (11/08/17 20:31), John W. O'Brien wrote:
>> On 2017/11/07 19:16, Ryan Steinmetz wrote:
>>> On (11/06/17 22:11), John W. O'Brien wrote:
>>>> Hello FreeBSD ports,
>>>>
>>>> The maintainer of net/f
n be made after maintainer timeout (2+ weeks).
>
> It's much easier and preferred to update maintainers with an explicit
> offer and change (in a bug), than to release a port with the possible
> prospect of having no maintainer.
Thank you, koobs. I will keep that strategy in
On 2017/11/07 19:16, Ryan Steinmetz wrote:
> On (11/06/17 22:11), John W. O'Brien wrote:
>> Hello FreeBSD ports,
>>
>> The maintainer of net/freeradius3 is unresponsive on two open bugs, both
>> with proposed patches.
>
> John,
>
> I was reviewin
is unable or unwilling to attend to
reported problems, that the port be released so that others could more
easily work to improve it.
Regards,
John
[0] net/freeradius3: Fix pkg-plist with IDN option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202684
[1] net/freeradius3: Does not link
rnel structures are changing, which means NVIDIA needs to recompile
> their binary blob aswell!
The blob does not generally use FreeBSD-specific structures. Part of
the driver is source and that interfaces with FreeBSD's APIs to implement
shims for the
Hello,
If you could add this to the port, that would be great. Thanks!
On Tue, Jun 13, 2017 at 9:51 AM, Maxim Sobolev <sobo...@freebsd.org> wrote:
> John, should I drop this into the port as a patch? Approved by: maintainer?
>
> -Max
>
> On Mon, Jun 12, 2017 at 4
n 2017 18:01:09 GMT
> Server: Apache
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
>
>
>
> 400 Bad Request
>
> Bad Request
> Your browser sent a request that this server could not understand.
>
>
>
>
--
John Mehr
Software De
gt; This GDB was configured as "powerpc-marcel-freebsd"...
> Failed to open vmcore: unsupported architecture
This is a different problem with libkvm. I would start with 'ps -M' and use
a debugger to step through the _powerpc_probe and _powerpc64_probe routines in
libkvm to see wh
hs either as others
have stated.
I wouldn't even mind if we had both /usr/local/man and /usr/local/share/man
so long as our default MANPATH included both if that means applying fewer
patches to ports.
--
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"
Hi,
On Mon, 6 Mar 2017, at 00:12, Walter Schwarzenfeld wrote:
> The old problem
> Either you deinstall lzmalib
> or
> add to the Makefile
>
> .if ${OSVERSION} < 100
> CFLAGS+="-I${LOCALBASE}/include"
> CPPFLAGS+= "-I${LOCALBASE}/include"
> LDFLAGS+= "-L${LOCALBASE}/lib"
>
Hello ports@
archivers/libarchive fails to build on 11.1-RELEASE-p8 and ports tree is
435506
===> Building for libarchive-3.2.2,1
/usr/bin/make all-am
/bin/sh ./libtool --tag=CC--mode=link cc -O2 -pipe
-I/usr/local/include -DLIBICONV_PLUG -fstack-protector
-fno-strict-aliasing -Wall
Hi,
On Sun, 19 Feb 2017, at 19:46, Marco Beishuizen wrote:
> On Sun, 19 Feb 2017, the wise tech-lists wrote:
>
> > I'm trying to build qt5 on a fresh freebsd-11-stable image. If it works,
> > then there's something wrong with ports on my desktop.
>
> I've just upgraded qt5 on my FreeBSD 11-ST
On 2/4/2017 16:24, Gerald Pfeifer wrote:
On Fri, 3 Feb 2017, John Marino wrote:
AFAIK it's not documented, but it's been spoken here quite a few times
and the result was "try to be nice and if you must use OSVERSION, guard
it with OPSYS". Anything else is a bug because OSVERSION
On 2/3/2017 14:55, Matthias Andree wrote:
Am 29.01.2017 um 20:22 schrieb John Marino:
Author: marino
Date: Sun Jan 29 19:22:47 2017
New Revision: 432796
URL: https://svnweb.freebsd.org/changeset/ports/432796
Log:
graphics/rawtherapee(-devel): Fix OSVERSION, use with OPSYS
The OSVERSION
oblem Reports" has been non-functional since
bugzilla come online. Are we ever going to get this useful
functionality back? I, for one, didn't think dumping gnats meant losing
that feature.
so basically: What's going on and what's the ETR to get portsmon fully
functional again?
s been non-functional since
bugzilla come online. Are we ever going to get this useful
functionality back? I, for one, didn't think dumping gnats meant losing
that feature.
so basically: What's going on and what's the ETR to get portsmon fully
functional again?
John
P.S. please keep me in
Hi,
On Sat, 28 Jan 2017, at 19:25, Matthew Seaman wrote:
> Hint: use poudriere. You're going to have a one-time hit to generate a
> repository full of packages, but after that, poudriere will be much
> cleverer about working out what is necessary to rebuild.
Does poudriere work on aarch64? I
In your message you wrote:
> ...
>On Wed, Jan 25, 2017 at 10:54:27PM -0800, john--- via freebsd-ports
>wrote: > Both llvm39 and binutils failed to install recently because
>they both have > hard links that cross directories. On this machine,
>those directories, both > in /u
.
Is this use of hard links something I should expect to see looking forward or
is it an error?
John Theus
TheUs Group
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
and
if they do, poudriere is the only game in town.
JOhn
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
On 12/20/2016 18:39, Warren Block wrote:
On Mon, 19 Dec 2016, John Marino wrote:
On 12/19/2016 20:22, Mark Linimon wrote:
On Mon, Dec 19, 2016 at 07:07:06PM -0600, John Marino wrote:
It's a natural reaction to stop attempting to contribute when previous
contributions don't get "atte
On 12/19/2016 20:22, Mark Linimon wrote:
On Mon, Dec 19, 2016 at 07:07:06PM -0600, John Marino wrote:
It's a natural reaction to stop attempting to contribute when previous
contributions don't get "attention they deserve".
Which some people (including me) see as odds with:
the
On 12/19/2016 18:36, Warren Block wrote:
On Mon, 19 Dec 2016, John Marino wrote:
On 12/19/2016 04:18, Boris Samorodov wrote:
17.12.2016 22:40, John Marino пишет:
I am not subscribed to the mail list
A port's committer is not subscribed to the ports@ ML?
Is it a joke?
I don't want
On 12/18/2016 23:42, Jim Trigg wrote:
On 12/18/2016 02:24 AM, John Marino wrote:
2) portmaster's dirty build method is inferior to clean environment
builds (true)
3) There is better and official alternative (true)
Maybe. I have a case where portmaster (on my current production box)
builds
On 12/19/2016 04:18, Boris Samorodov wrote:
17.12.2016 22:40, John Marino пишет:
I am not subscribed to the mail list
A port's committer is not subscribed to the ports@ ML?
Is it a joke?
I don't want to participate in this list. The only reason I'm stuck on
this topic is because Warren
On 12/19/2016 00:48, Peter Jeremy wrote:
On 2016-Dec-17 20:16:12 -0600, John Marino <freebsd.cont...@marino.st> wrote:
On 12/17/2016 19:35, Peter Jeremy wrote:
$ cd /usr/ports/ports-mgmt/synth/ && make
[ about an hour of grinding away elided ]
===> ini_file_manager-03_2 depe
Grzegorz Junka wrote:
On 17/12/2016 18:51, John Marino wrote:
On 12/17/2016 12:34, abi wrote:
2. It doesn't provide dialog for port options, so
2.1 I don't receive information if port options have changed. I don't
know what else will be pulled to my system after port tree update.
which
David wrote
On 12/16/2016 04:06 PM, John Marino wrote:
Starting with a clean system:
1) install synth from binary package from official freebsd builder (a
single package)
What about just building synth from ports? Then the OP have everything
built from ports.
--
David
In the example
On 12/18/2016 00:43, Greg 'groggy' Lehey wrote:
On Saturday, 17 December 2016 at 20:16:12 -0600, John Marino wrote:
On 12/17/2016 19:35, Peter Jeremy wrote:
$ cd /usr/ports/ports-mgmt/synth/ && make
[ about an hour of grinding away elided ]
===> ini_file_manager-03_2 depends on
nly
available for i386 and amd64. I think you already knew that and thus
this is a pure troll.
Use poudriere for non-x86 platforms. armv6 packages are built with
poudriere + QEMU, but I suspect you already knew this as well.
John
---
This email has been checked for viruses by Avast anti
you go.
Since reverting your name on that many ports is quite a bit of work,
maybe you could open one final PR and provide a patch that does this?
John
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_
thing. I don't care if the consequence is a
broken thread since FreeBSD has the ability to make it better.
John
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
freebsd-ports@freebsd.or
both synth
and poudriere build in parallel is a huge advantage to any single system
user.
John
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
freebsd-ports@freebsd.org mailing
ong enough to
understand how those tools actually work.
John
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listin
From Thomas Mueller:
From John Marino:
Starting with a clean system: 1) install synth from binary package
from official freebsd builder (a single
package) 2) Configure synth if necessary 3) command synth to build
itself 4) pkg delete synth (system is once again clean) 5) pkg add -F
/path
On 12/17/2016 01:49, Hrant Dadivanyan wrote:
On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote:
On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote:
Interestingly, the most vocal proponent of deleting portmaster and
portupgrade is the author/maintainer of synch.
It's not
On 12/17/2016 07:55, Michael Gmelin wrote:
On 17 Dec 2016, at 14:26, Alphons van Werven <free...@skysmurf.nl> wrote:
John Marino wrote:
In fact, anyone that updates ports should use either poudriere testport
or synth test.
Then consider these relinquished:
/usr/ports/archivers/zi
l message.
Which notice should we drop? There's no DEPRECATION set now. There's
no warning set. portmaster is not marked as "deprecated".
And as the handbook points out: You can't have EXPIRATION without
DEPRECATED, but it's perfectly legal to have the reverse. It's
documented cl
scarlet letter and fans of portmaster didn't
want the reputation defamed.
If Torsten drops maintainership then some sort of "strong" warning
should come with that drop. I would be satisfied with adding a
descriptive DEPRECATED message myself.
John
---
This email has been checked fo
ess than 30
minutes. Either is very appropriate for a system that must build
everything that is run on it.
John
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
freebsd-ports@freebsd.or
ing
significant changes but that's getting sidetracked).
The point is that these tools are in great shape and to imply otherwise
needs proof. It's portmaster that's not receiving updates.
John
---
This email has been checked for viruses by Avast antivirus softwa
1 - 100 of 706 matches
Mail list logo
