On 12/2/13 2:02 PM, Mikhail Tsatsenko wrote:
As I can see maintainer of vim vim-lite ports is just reset, so I
want to maintain them.
It looks like you're too late by minutes.
https://svnweb.freebsd.org/ports?view=revisionrevision=335535
But there's good news too!
Hello freebsd-ports@,
I'm trying to build and maintain my own package repository and
understand how everything is put together in the process. Right now, I'm
having trouble understanding how the signatures are made and verified.
The following should illustrate both the problem I'm having and how
On 2/8/14 6:50 PM, John W. O'Brien wrote:
Hello freebsd-ports@,
I'm trying to build and maintain my own package repository and
understand how everything is put together in the process. Right now, I'm
having trouble understanding how the signatures are made and verified.
The following should
Hello decke,
Could you help me understand what's going on with this build [0]? Did an
admin kill the job, and if so, why? Otherwise, what happened and is it
because I'm doing something wrong?
Thank you,
John
[0] https://redports.org/buildarchive/20140210032800-24135/
signature.asc
On 2/10/14 9:52 AM, John W. O'Brien wrote:
Could you help me understand what's going on with this build [0]? Did an
admin kill the job, and if so, why? Otherwise, what happened and is it
because I'm doing something wrong?
[0] https://redports.org/buildarchive/20140210032800-24135
On 2/15/14 12:53 PM, John W. O'Brien wrote:
On 2/10/14 9:52 AM, John W. O'Brien wrote:
Could you help me understand what's going on with this build [0]? Did an
admin kill the job, and if so, why? Otherwise, what happened and is it
because I'm doing something wrong?
[0] https://redports.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/2013 04:52 AM, Baptiste Daroussin wrote:
Let's go for USES then!
regards,
Bapt
Clearly I'm a bit late to the party here, and I don't wish to reopen
litigation of this particular design choice. However, I would like to
respectfully
Hello ports@,
In the bad old days before poudriere and various improvements to
OptionsNG came to town, when I was using portmaster* to handle upgrades,
I cobbled together a configuration management practice that involved
using rsync and git to store /var/db/ports in a repository. The usual
On 3/30/14 10:21 PM, Randy Pratt wrote:
On Sun, 30 Mar 2014 17:13:15 -0400
John W. O'Brien j...@saltant.com wrote:
[blah blah blah]
[...]
The first part of my solution to these problems is to store only the
options that I know I care about. That is, I know I need to find out
where
On 3/31/14 3:47 PM, Kevin Oberman wrote:
This is something I've wanted to have for quite a while, but never
enough to dig through the Makefiles.
I think the proper way would be for make showconfig to print out the
current config as it does now, but to tag default options (e.g. '+') so
that
On 10/28/2012 09:58 PM, Thomas Mueller wrote:
This time, the checksum apparently fails on two files in math/py-numpy.
[snip]
= SHA256 Checksum OK for numpy-1.6.2.tar.gz.
= SHA256 Checksum mismatch for numpy-ref.pdf.
= SHA256 Checksum mismatch for numpy-user.pdf.
=== Giving up on fetching
Last action was assignment to maintainer on 2014-08-22 (3 wk ago) by
marino@. I would appreciate either an available committer or some
feedback on the offered patch.
Thank you,
John
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192904
signature.asc
Description: OpenPGP digital signature
On 12/13/15 3:25 AM, Kurt Jaeger wrote:
> Hi!
>
> [ports marked BROKEN are build in poudriere and fail]
>
>> But poudriere goes ahead with the build, fails on the broken dependency,
>> and skips the port without printing or logging my helpful BROKEN message.
>>
>> Is this by design, or a flaw in
Are there any committers willing to take this bug? Current timeout is
sitting at about six weeks depending on how you count.
security/john: OPENMP option has no effect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204903
Thank you,
John
signature.asc
Description: OpenPGP digital
On 7/17/16 5:02 AM, Kubilay Kocak wrote:
> On 17/07/2016 11:17 AM, John W. O'Brien wrote:
>> Hello all,
>>
>> I was just going through my old bugs and found this one still open from
>> 2016-02-27. Is there a committer willing and available to take a look?
>>
>&
Hello all,
I was just going through my old bugs and found this one still open from
2016-02-27. Is there a committer willing and available to take a look?
net/freeradius3 w/ non-standard config option depends on IDN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202684
Thank you,
John
Hello FreeBSD ports,
The maintainer of net/freeradius3 is unresponsive on two open bugs, both
with proposed patches.
In one case [0], the submitter responded to feedback on 2016-02-03,
there has been no further action on the part of the maintainer, and the
port remains broken w.r.t. Kerberos.
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
On 2017/11/06 22:31, Kubilay Kocak wrote:
[...]
> If you'd like (or are offering) to maintain the port, please create a
> separate issue updating the MAINTAINER line and have it depend on the
> existing open issues (so they can be committed first).
>
> The maintainer change can then be made after
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
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
> 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
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
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
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
Mon, May 14, 2018, 4:40 PM John W. O'Brien <j...@saltant.com
> <mailto:j...@saltant.com>> 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
nk my employer might feel slighted? What if I had done 80% of the
work?
> On Thu, May 17, 2018 at 3:43 PM, John W. O'Brien <j...@saltant.com
> <mailto:j...@saltant.com>> wrote:
>
> On 2018/05/14 20:14, Maxim Sobolev wrote:
> > What's wrong with a current practice.
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/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,
>>>
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 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.
/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
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
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
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
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
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
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
>
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
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
https://bugs.freebsd.org/241766
Thank you,
--
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
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
] 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
47 matches
Mail list logo
