Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
Agree with previous sentiments, and:
On 17-04-18 10:59 PM, Christopher Hall wrote:
You should use built in golang vendoring to ensure these
dependencies, as their is no guarantee that someone won't update the
library port and your app would break, so doing that is very fragile
Currently the GH
Not only that, but pkg should not delete things until AFTER it
successfully replaces them!
I finally broke down and did a pkg upgrade yesterday, which cost
me the whole afternoon. I had to do it because pkg wasn't smart
enough not to use the current quarter's bits to install a package
on a machin
[Default] On Tue, 18 Apr 2017 21:45:47 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
>Miroslav Lachman wrote on 2017/03/31 15:31:
>> I don't know if it was "pkg" fault or mariadb101-server and
>> mariadb101-client conflict.
>>
>> I did standard "pkg upgrade" and at the end I have half files of
On 19 Apr 2017, at 00:17, bob prohaska wrote:
>
> On Tue, Apr 18, 2017 at 09:43:23PM +0200, Jan Beich wrote:
>>
>> See bug 211069 which was duped against bug 203989 that triggered a
>> different assertion. The above error did show up on armv6 buildbot[1]
>> but nowadays is blocked by other ports
scratch65...@att.net wrote on 2017/04/19 12:45:
[Default] On Tue, 18 Apr 2017 21:45:47 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
Miroslav Lachman wrote on 2017/03/31 15:31:
I don't know if it was "pkg" fault or mariadb101-server and
mariadb101-client conflict.
I did standard "pkg upgr
[Default] On Wed, 19 Apr 2017 13:45:54 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
>scratch65...@att.net wrote on 2017/04/19 12:45:
>> [Default] On Tue, 18 Apr 2017 21:45:47 +0200, Miroslav Lachman
>> <000.f...@quip.cz> wrote:
>>
>>> Miroslav Lachman wrote on 2017/03/31 15:31:
I don't k
Trying to build a repository via poudriere fails on recent 12-CURRENT (FreeBSD
12.0-CURRENT #2 r317090: Tue Apr 18 15:32:23 CEST 2017 amd64) initially with
failing to build ports-mgmt/pkg.
poudriere's log reports:
[...]
configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1':
con
scratch65...@att.net wrote on 2017/04/19 14:05:
[Default] On Wed, 19 Apr 2017 13:45:54 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
scratch65...@att.net wrote on 2017/04/19 12:45:
[Default] On Tue, 18 Apr 2017 21:45:47 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
Miroslav Lachman w
Can the original iocage port be restored? The replacements of py-iocage and
py3-iocage are not yet feature complete, and the original one still works
just great.
Thanks!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf
[Default] On Wed, 19 Apr 2017 14:52:56 +0200, Miroslav Lachman
<000.f...@quip.cz> wrote:
>scratch65...@att.net wrote on 2017/04/19 14:05:
>> [Default] On Wed, 19 Apr 2017 13:45:54 +0200, Miroslav Lachman
>> <000.f...@quip.cz> wrote:
>>
>>> scratch65...@att.net wrote on 2017/04/19 12:45:
[Defa
Hi all,
We are writing a port for a Java software that downloads a large number of
jar files (around 200) with Gradle (https://gradle.org/), that is similar
to other package managers like Pip or Ruby Gems but for Java projects.
What would be the best practice in this scenario? I am aware that we
On 2017-04-19, Vick Khera wrote:
> Can the original iocage port be restored?
I believe the old code has been forked and preserved under the
name iocell (https://github.com/bartekrutkowski/iocell) and is
available in pkg/ports under sysutils/iocell.
___
f
On 2017-04-18 21:45, Miroslav Lachman wrote:
Miroslav Lachman wrote on 2017/03/31 15:31:
I don't know if it was "pkg" fault or mariadb101-server and
mariadb101-client conflict.
I did standard "pkg upgrade" and at the end I have half files of
mariadb101-client missing:
# pkg check -Ba
Checking
On 19.04.2017 19:27, Xavi Garcia wrote:
Hi all,
We are writing a port for a Java software that downloads a large number
of
jar files (around 200) with Gradle (https://gradle.org/), that is
similar
to other package managers like Pip or Ruby Gems but for Java projects.
What would be the best
[Default] On Tue, 18 Apr 2017 15:57:02 +0100, krad
wrote:
>quarterly does seem very cautious, maybe a monthly might be a good
>alternative.
I have to STRONGLY disagree.
Right now, pkg isn't smart enough not to use version-skewed bits.
Which means that, for those of us trying to use freebsd a
Scratch65535, I think your best solution is to use latest and upgrade when
you need to. Unlike Freddie's comment re only desktop users using latest.
I ONLY upgrade my local svn of ports when there's a vulnerability or
significant (for users) functional improvement of a port.
It is a labour intens
On 19/4/17 12:13 am, Freddie Cash wrote:
On Tue, Apr 18, 2017 at 7:57 AM, krad wrote:
quarterly does seem very cautious, maybe a monthly might be a good
alternative. I can understand people being hesitant about latest though. I
guess these are not the people who ask though. Maybe the real answ
"O. Hartmann" writes:
> Trying to build a repository via poudriere fails on recent 12-CURRENT (FreeBSD
> 12.0-CURRENT #2 r317090: Tue Apr 18 15:32:23 CEST 2017 amd64) initially with
> failing to build ports-mgmt/pkg.
>
> poudriere's log reports:
>
> [...]
> configure: error: in `/wrkdirs/usr/port
On 20/4/17 4:37 am, scratch65...@att.net wrote:
[Default] On Tue, 18 Apr 2017 15:57:02 +0100, krad
wrote:
quarterly does seem very cautious, maybe a monthly might be a good
alternative.
I have to STRONGLY disagree.
Right now, pkg isn't smart enough not to use version-skewed bits.
Which means
On 20/4/17 6:29 am, Dewayne Geraghty wrote:
Scratch65535, I think your best solution is to use latest and upgrade when
you need to. Unlike Freddie's comment re only desktop users using latest.
I ONLY upgrade my local svn of ports when there's a vulnerability or
significant (for users) functional
Thanks Larry,
I have updated the patch on the bug, because the upstream project has just
released a minor version/bug fix release. New patch updates us to 1.6.1.
Thanks,
-Jev
On Tue, Apr 18, 2017 at 1:22 PM Larry Rosenman wrote:
> On 4/18/17, 2:41 PM, "Jev Björsell" behalf of j...@ecadlabs.co
Can you fill in the unknown stuff in the version package or should I just go
ahead and do it?
>
> On Apr 19, 2017 at 10:22 PM,wrote:
>
>
> Thanks Larry,
>
>
> I have updated the patch on the bug, because the upstream project has just
> released
On Wed, Apr 19, 2017 at 04:37:05PM -0400, scratch65...@att.net wrote:
> (Right now, it's quite hard to resist the paranoid suspicion that
> maybe this crazy, anti-real-user behavior is a subtle way to kill
> freebsd altogether by driving away the non-hobbyists.)
That's one explanation.
The other,
I understand that having the quarterlies is not meeting your use case.
You've said that. We get it.
So you want some kind of running -quarterly branch.
But where are the N hours of work per week to QA all the patches to
the -quarterly branch, or a -stable branch, or whatever people seem
to deman
On Thu, Apr 20, 2017 at 1:30 AM, Julian Elischer wrote:
> quarterly however is broken because the pkg mirors discard it all at the
> time of update.
>
Do they have to?
Why couldn't pkg mirrors keep say, the four latest quarterly sets all the time?
This would increase the usability of quarterly pa
Hi!
> On Thu, Apr 20, 2017 at 1:30 AM, Julian Elischer wrote:
> > quarterly however is broken because the pkg mirors discard it all at the
> > time of update.
> Do they have to?
> Why couldn't pkg mirrors keep say, the four latest quarterly sets
> all the time?
Because the URL for the latest qu
On Tue, Apr 18, 2017, at 02:54 PM, qjail1 wrote:
> I maintain a port and I have users complaining that the pkg system takes
> many months before the updated version of my port shows up in the pkg
> system.
>
> My response is I tell them to change a line in their
> /etc/pkg/FreeBSD.conf file
> f
On Thu, Apr 20, 2017, at 06:22 AM, Mark Linimon wrote:
> On Wed, Apr 19, 2017 at 04:37:05PM -0400, scratch65...@att.net wrote:
> > (Right now, it's quite hard to resist the paranoid suspicion that
> > maybe this crazy, anti-real-user behavior is a subtle way to kill
> > freebsd altogether by drivin
29 matches
Mail list logo
