Hi!
> There are currently two remaining PRs with patches for mail/ifile
> (202572) and net-p2p/namecoin (2012603), getting those committed soon
> would avoid traumas in the ports tree once FORTIFY_SOURCE is committed.
202603: done
--
p...@opsec.eu+49 171 3101372
+--On 1 septembre 2015 14:08:09 -0700 Xin Li wrote:
| Hi,
|
| I hit a conflict between pkg behavior and the Porters' handbook, it
| confused me.
|
| In this example:
|
| https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefi
| le-distfiles.html#idp59327440
|
| The handbook
On 09/01/15 14:16, Xin Li wrote:
> On 09/01/15 14:11, Larry Rosenman wrote:
>> On 2015-09-01 16:08, Xin Li wrote:
> [...]
>> I, as sysutils/lsof maintainer, depend on the behavior you see (the >).
>>
>> Vic Abell uses the letters as "fixup" releases, until a full release,
>> for example;
>>
>> 4.89
On 09/01/15 14:11, Larry Rosenman wrote:
> On 2015-09-01 16:08, Xin Li wrote:
[...]
> I, as sysutils/lsof maintainer, depend on the behavior you see (the >).
>
> Vic Abell uses the letters as "fixup" releases, until a full release,
> for example;
>
> 4.89A -> 4.89B -> 4.89C -> 4.89 -> 4.90A -> 4.
On 2015-09-01 16:08, Xin Li wrote:
Hi,
I hit a conflict between pkg behavior and the Porters' handbook, it
confused me.
In this example:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#idp59327440
The handbook suggested that the right PORTVERSION sho
Hi,
I hit a conflict between pkg behavior and the Porters' handbook, it
confused me.
In this example:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#idp59327440
The handbook suggested that the right PORTVERSION should be 0.7.1.d if
DISTVERSION is 0.7.
Hi!
> Could someone of the committer(s) please commit this port ?
>
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188437)
Done.
As this port has complex features, I would like to see run-test-reports and
success reports against several clients 8-}
Maybe my colleague will have the opport
Hi!
> > Second: The files/patch* are working, but contain ^M newlines at the end,
> > which is not allowed and rejected when committing with this message:
[...]
> You should use the dos2unix USES [1] on those files and generate patches
> against the "fixed" ones.
Ah, thanks! Will try.
--
p...@o
On 09/01/15 18:13, Kurt Jaeger wrote:
> Hi!
>
>> Could someone of the committer(s) please commit this port ?
>>
>> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188437)
>>
>> I would like to use the official ports for install this software on our
>> systems.
>
> First: With a bit of tweaking
Hi!
> Could someone of the committer(s) please commit this port ?
>
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188437)
>
> I would like to use the official ports for install this software on our
> systems.
First: With a bit of tweaking, it builds fine, which is very nice.
Second: The
On Sun, Aug 30, 2015 at 10:21 PM, Kurt Jaeger wrote:
> Committed, thanks!
TANKS!! =)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, se
Hi!
> Could someone of the committer(s) please commit this port ?
>
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188437)
>
> I would like to use the official ports for install this software on our
> systems.
Testing@work.
--
p...@opsec.eu+49 171 3101372
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Could someone of the committer(s) please commit this port ?
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188437)
I would like to use the official ports for install this software on our
systems.
Thanks,
Kind Regards,
C. D.
-BEGIN
During the "update all installed ports" phase of today's daily updates
on my laptop, I received a bit of an unpleasant surprise.
As I build stable/10, it is my habit to also run "portmaster -aF" --
pre-fetching distribution files (to the extent that I can). This
occurred without incident.
My por
14 matches
Mail list logo
