On Mon, May 06, 2019 at 01:17:56PM -0500 I heard the voice of
Bob Willcox, and lo! it spake thus:
>
> Any word on when/if your patch will be integraded into the port
> proper?
I presume the route would be it getting integrated upstream, and then
a new release with the change makes it into the
Yeah, bdrewery is listed as the maintainer of portupgrade in its Makefile.
On Mon, May 06, 2019 at 06:05:24PM -0700, Kevin Oberman wrote:
> Oops. Disregard. Confusing portupgrade with portmaster.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
Oops. Disregard. Confusing portupgrade with portmaster.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Mon, May 6, 2019 at 6:03 PM Kevin Oberman wrote:
> Looks like the maintainer
Looks like the maintainer should be on the CC, so I added Stefan.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Mon, May 6, 2019 at 11:35 AM Bob Willcox wrote:
> On Sun, Apr 07, 2019
On Sun, Apr 07, 2019 at 08:51:57PM -0500, Matthew D. Fuller wrote:
> For any portupgrade users still out there wishing for FLAVOR support,
> I have patches to add it. I've been running them here locally for a
> few weeks without incident (apart from an extra upgrade or two
> actually working
Right
On Wed, Apr 10, 2019 at 5:54 PM Matthew D. Fuller
wrote:
>
> My best guess is still something along the way tweaked up the patch
> you're trying; check the md5 vs the one in my earlier mail.
saved from (shudder) Gmail
tingo@kg-core1$ md5 patch-flavors_gmail
MD5 (patch-flavors_gmail) =
On Wed, Apr 10, 2019 at 04:06:00PM +0200 I heard the voice of
Torfinn Ingolfsen, and lo! it spake thus:
>
> Ah. I use portsnap to upgrade my ports tree. Is there a delay or
> difference?
A delay, sure, but the last commit in devel/portupgrade was over a
year ago. You'd probably notice if it
On Mon, Apr 8, 2019 at 11:51 PM Matthew D. Fuller
wrote:
>
> Torfinn,
>
> > It doesn't apply cleanly to portupgrade in an up to date ports tree
>
> Hm. Seems to work fine here.
>
> % svn up
> Updating '.':
> At revision 498434.
Ah. I use portsnap to upgrade my ports tree. Is there a delay or
Marco,
> Any reason why not just submit it in Bugzilla?
Well, I s'pose one _could_ split a hair and argue that it's
FreeBSD-specific, and so should be a ports patch rather than an
upstream change. But that'd be an awful fine hair to try and cleave
in this case :p
It's in a PR to upstream.
Torfinn,
> It doesn't apply cleanly to portupgrade in an up to date ports tree
Hm. Seems to work fine here.
% svn up
Updating '.':
At revision 498434.
% ports-make.sh clean patch
===> Cleaning for portupgrade-2.4.16,2
===> License BSD3CLAUSE accepted by the user
===> portupgrade-2.4.16,2
Hello,
On Mon, Apr 8, 2019 at 3:53 AM Matthew D. Fuller
wrote:
>
> For any portupgrade users still out there wishing for FLAVOR support,
> I have patches to add it. I've been running them here locally for a
> few weeks without incident (apart from an extra upgrade or two
> actually working
On Sun, 7 Apr 2019, the wise Matthew D. Fuller wrote:
For any portupgrade users still out there wishing for FLAVOR support, I
have patches to add it. I've been running them here locally for a few
weeks without incident (apart from an extra upgrade or two actually
working without manual
For any portupgrade users still out there wishing for FLAVOR support,
I have patches to add it. I've been running them here locally for a
few weeks without incident (apart from an extra upgrade or two
actually working without manual intervention/resort to portmaster,
that is). Dropping the
13 matches
Mail list logo
