Hi. This is probably not the message you were expecting. ;-)
While I know most all the committers with any tenure.
It's my understanding that doing this directly "shopping
for a committer" is strictly frowned upon.
So please consider this my CV for application as a ports
committer.
I've been w/Fre
On Sat, Apr 10, 2021 at 11:55 AM Newton Terry wrote:
>
> It seems https://calcurse.org is down, distfile un-fetchable.
>
> Please wait the commit until the website situation has been clarified,
> seeing if it's permanent or temporarily.
Temporary failure? The web site seems to be up now at least.
On 4/10/21 12:40 PM, Newton Terry wrote:
Greetings.
Can a committer have a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251807
The port is waiting quite a while to be updated. Thanks.
Best regards.
It seems https://calcurse.org is down, distfile un-fetchable.
Please wait the c
Greetings.
Can a committer have a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251807
The port is waiting quite a while to be updated. Thanks.
Best regards.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
Hi!
> Hello, I'm looking for a port committer to take a look at the following port:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253782
Done.
--
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-ports@freebsd
Hello, I'm looking for a port committer to take a look at the following port:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253782
signature.asc
Description: This is a digitally signed message part.
On Wed, Nov 4, 2020 at 3:05 AM abi via freebsd-ports
wrote:
>
> Hello,
>
> looking for a committer for
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250234
>
> @lwhsu had pointed me to some issues, however he didn't reply after I
> fixed them.
Committed. S
Hello,
looking for a committer for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250234
@lwhsu had pointed me to some issues, however he didn't reply after I
fixed them.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebs
Hello,
I'm looking for a committer for these PRs.
First (containing vuxml entries also):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239717 (mongodb34
security update)
And then these two dependencies:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240126 (mongodb36
sec
Hi,
Can someone please have a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224113
Thanks,
Dmitri
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-p
Hi all,
I'm looking for a committer to PR #222703 to have postgis24 in ports.
This is necessary for the postgis framework PR #213038.
Thank you.
Regards
Loïc
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
I'll take care of it
Best regards,
pizzamig
On Thu, Oct 26, 2017 at 7:08 AM, L.Bartoletti wrote:
> Hi all,
>
> Since codeblocks is still buggy, I'm looking for a committer to PR #221703
> to have codeblocks-devel which works.
>
> Tha
Hi all,
Since codeblocks is still buggy, I'm looking for a committer to PR
#221703 to have codeblocks-devel which works.
Thank you.
Regards
Loïc
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-
Hello, can you commit zoneminder updates?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217896
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218292
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-por
Howdy!
I've got several PRs for a number of my ports that are in good order; they just
need to be committed. I'd be ever appreciative if someone would do the honors :)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213353
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213586
https://bugs.f
Thank you Kurt for committing both ports. For the prometheus one, I see now
I attached a stale patch file that referenced version 1.1.3. Thanks for
going the extra mile and fixing that for me. I have learned a lesson, and
will be much more careful in the future.
Again, thank you!
Jev
On Fri, Oct
Hi!
> I just updated https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 patch
> attachment to build the latest release of prometheus. It's now 1.2.1
Well, the version number in the patch was 1.1.3, but
changing that to 1.2.1 was easy, test-building was OK, so: done.
> Can I get a committer
Hi All,
I just updated https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 patch
attachment to build the latest release of prometheus. It's now 1.2.1
Can I get a committer to review, and possibly commit? This new port request
and my other one (node_exporter:
https://bugs.freebsd.org/bugzilla
Can someone look at these?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212625
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213150
--
`whois vmeta.jp | nkf -w`
meta
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman
El 09/09/2015 21:52, "Kurt Jaeger" escribió:
>
> Hi!
>
> > That seems to be the case. The pkg-plist doesn't change either.
> > Successfully built for {9.3,10.2}amd64
> >
> > I updated the PR.
>
> Test-builds done on cur 93a 10a 10i.
>
> Committed, thanks.
Thanks!
>
> --
> p...@opsec.eu
Hi!
> That seems to be the case. The pkg-plist doesn't change either.
> Successfully built for {9.3,10.2}amd64
>
> I updated the PR.
Test-builds done on cur 93a 10a 10i.
Committed, thanks.
--
p...@opsec.eu+49 171 3101372 5 years to go !
On Wed, Sep 9, 2015 at 8:35 PM, Kurt Jaeger wrote:
> Hi!
>
>> > It fails to fetch ? Any ideas ?
>>
>> I suppose it's because they released the new version (20150902) and
>> removed the old one.
>
> If this is all, I've changed and started the make makesum.
> 250 MB distfile...
>
>> This project ha
Hi!
> > It fails to fetch ? Any ideas ?
>
> I suppose it's because they released the new version (20150902) and
> removed the old one.
If this is all, I've changed and started the make makesum.
250 MB distfile...
> This project has a funny record of doing things
> like that, re-rolling releases
On Wed, Sep 9, 2015 at 8:21 PM, Kurt Jaeger wrote:
> Hi!
>
>> Please, can a committer have a look at this?
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202752
>
> It fails to fetch ? Any ideas ?
I suppose it's because they released the new version (20150902) and
removed the old one. Th
Hi!
> Please, can a committer have a look at this?
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202752
It fails to fetch ? Any ideas ?
===> visualparadigm-12.2.20150820 depends on file: /usr/local/sbin/pkg - found
=> Visual_Paradigm_CE_12_2_20150820_Unix_InstallFree.tar.gz doesn't se
Please, can a committer have a look at this?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202752
Thanks in advance.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Hey there,
since I didn’t raise the PR, it’s not marked as maintainer-update, but the
linked patch (not the included one) is ready to be committed.
Cheers,
Stefan
--
Stefan BethkeFon +49 151 14070811
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 13/10/2010 16:52, Warren Block wrote:
> On Wed, 13 Oct 2010, Dominic Fandrey wrote:
>
>> I'm looking for a committer for the openarena port:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=146818
>>
>> The PR sits there since May.
>
> FWIW, I'v
On Wed, 13 Oct 2010, Dominic Fandrey wrote:
I'm looking for a committer for the openarena port:
http://www.freebsd.org/cgi/query-pr.cgi?pr=146818
The PR sits there since May.
FWIW, I've tested this port successfully. The multiple patches and
files in the PR made it confusing to
I'm looking for a committer for the openarena port:
http://www.freebsd.org/cgi/query-pr.cgi?pr=146818
The PR sits there since May.
I'd like to work on the ioquake3, ioquake3-devel and iourbanterror
ports. The pending openarena commit is blocking, because of changes
to the ioquake3 m
30 matches
Mail list logo
