On 04.06.2014 02:34, Mark Linimon wrote:
On Tue, Jun 03, 2014 at 01:50:23PM -0700, Eitan Adler wrote:
I don't concede killing anonymous means killing trivial bug reporting,
but if that was the case: Oh well, I guess we have to focus on
non-trivial bugs.
Trivial bugs are important too.
I'll e
On 6/4/2014 09:46, Torsten Zuehlsdorff wrote:
>>
>> I know for certain that people in the past have given up after submitting
>> PRs that were never answered. While I know we don't have the manpower to
>> deal with all of them, that should at least be our ideal.
>
> Yes. It is really frustrating
Hello - any chance of this happening? 4.0.1+ has several useful
bug-fixes over 4.0.1 and hopefully wouldn't be too much effort.
Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, se
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
On 6/3/2014 7:50 AM, Alfred Perlstein wrote:
On 6/3/14, 5:16 AM, David Chisnall wrote:
On 3 Jun 2014, at 13:09, Vitaly Magerya wrote:
It doesn't seem to be possible to post comments (or bugs) without creating an
account and logging in.
That is correct. The current leaning is towards not p
FreeBSD 10.0-RELEASE-p3 amd64
I am unable to update the "devel/py-dbus" port.
The build end with this error message:
===> Staging for pydbus-common-1.1.1_4
===> Generating temporary packing list
/bin/mkdir -p
/usr/ports/devel/pydbus-common/work/stage/usr/local/include/dbus-1.0/dbus/
install
FreeBSD 10.0-RELEASE-p3 amd 64
I am unable to update the "net/libexosip2" port. It terminates with this
error message:
===> Building for libeXosip2-4.1.0
/usr/bin/make all-recursive
Making all in scripts
Making all in platform
Making all in vsnet
Making all in src
/bin/sh ../libtool --tag=CC
On Wed, 4 Jun 2014 06:42:51 -0400
Jerry wrote:
> FreeBSD 10.0-RELEASE-p3 amd64
>
> I am unable to update the "devel/py-dbus" port.
>
> The build end with this error message:
>
> ===> Staging for pydbus-common-1.1.1_4
> ===> Generating temporary packing list
> /bin/mkdir
> -p /usr/ports/dev
FreeBSD 10.0-RELEASE-p3 amd 64
I am unable to update the "net/libexosip2" port. It terminates with this
error message:
===> Building for libeXosip2-4.1.0
/usr/bin/make all-recursive
Making all in scripts
Making all in platform
Making all in vsnet
Making all in src
/bin/sh ../libtool --tag=CC
Hi,
Can you please try deinstalling net/libosip2 and starting it from scratch
again.
BR,
Muhammad
On Wed, Jun 4, 2014 at 4:51 PM, Jerry wrote:
> FreeBSD 10.0-RELEASE-p3 amd 64
>
> I am unable to update the "net/libexosip2" port. It terminates with this
> error message:
>
> ===> Building for
On wo, 2014-06-04 at 06:42 -0400, Jerry wrote:
> FreeBSD 10.0-RELEASE-p3 amd64
>
> I am unable to update the "devel/py-dbus" port.
>
> The build end with this error message:
Please read ports/UPDATING entry 20140525 to resolve this problem.
> ===> Staging for pydbus-common-1.1.1_4
> ===> Gen
On Wed, 4 Jun 2014 16:53:25 +0600, Muhammad Moinur Rahman stated:
> Hi,
>
> Can you please try deinstalling net/libosip2 and starting it from scratch
> again.
>
> BR,
> Muhammad
It failed. This is the output:
/usr/ports/net/libexosip2 # make deinstall && make reinstall && make clean
===> Dei
Hi,
It seems like your ports tree is not upto date. Right now net/libexosip2 do
not any longer point to 3.6.0. This has been moved to libexosip2-legacy. If
you are trying to build linphone remove exosip2, update ports tree, and
reinstall linphone.
BR,
Muhammad
On Wed, Jun 4, 2014 at 6:07 PM,
On Wed, 4 Jun 2014 18:12:06 +0600, Muhammad Moinur Rahman stated:
> It seems like your ports tree is not upto date. Right now net/libexosip2 do
> not any longer point to 3.6.0. This has been moved to libexosip2-legacy. If
> you are trying to build linphone remove exosip2, update ports tree, and
>
On 4 June 2014 06:34, Darren Pilgrim wrote:
>
> Requiring oauth will literally guarantee me and a whole bunch of other
> people will never have bugzilla accounts.
I don't think anyone's suggesting oauth would be required. It would
just be available as an alternate method for those who don't want
Hi.
I've just updated ejabberd to the latest 14.05 version, but alas it no
long runs. Normally I would do some debugging, but this is erlang, so
all bets are off as I have no idea what to look at, hence the vague
problem description.
I'd be very grateful is anyone has any idea why a perfectly fun
Hello,
thanks for your advices. :)
devel/fpp
Whats the next step? Writing a patch to change maintainer?
In a nutshell:
1. Check upstream to see if there's no newer version. If there is, try to
update the port.
2. Change MAINTAINER, indeed.
3. If you can, mirror the distfile and add your
INDEX build failed with errors:
Generating INDEX-8 - please wait.. Done.
make_index: /home/indexbuild/tindex/ports/graphics/radius-engine: no entry for
/home/indexbuild/tindex/ports/lang/lua
Committers on the hook:
amdmi3 demon miwi nemysis pawel skreuzer sunpoet wg
Most recent SVN update was:
Torsten Zuehlsdorff wrote:
>>3. If you can, mirror the distfile and add your site to MASTER_SITES.
>
> I could easily mirror the distfile. But i'm unsure where to add the entry.
> There is an entry MASTER_SITE_NETLIB in /usr/ports/Mk/bsd.sites.mk, which
> definies the url for the distfiles. But i
> On Jun 4, 2014, at 6:51 AM, Ed Maste wrote:
>
>> On 4 June 2014 06:34, Darren Pilgrim wrote:
>>
>> Requiring oauth will literally guarantee me and a whole bunch of other
>> people will never have bugzilla accounts.
>
> I don't think anyone's suggesting oauth would be required. It would
> j
On 04.06.2014 17:25, A.J. 'Fonz' van Werven wrote:
Torsten Zuehlsdorff wrote:
3. If you can, mirror the distfile and add your site to MASTER_SITES.
I could easily mirror the distfile. But i'm unsure where to add the entry.
There is an entry MASTER_SITE_NETLIB in /usr/ports/Mk/bsd.sites.mk, whi
On 04/06/2014 11:34, Darren Pilgrim wrote:
Requiring oauth will literally guarantee me and a whole bunch of other
people will never have bugzilla accounts.
I don't understand what the problem with logging in is? It surely is a
small price to pay for a secure modern bug tracking system?
--
R
On Wed, 04 Jun 2014 16:08:18 +0200
Neal Nelson wrote:
> Hi.
>
> I've just updated ejabberd to the latest 14.05 version, but alas it no
> long runs. Normally I would do some debugging, but this is erlang, so
> all bets are off as I have no idea what to look at, hence the vague
> problem descripti
On 03/06/2014 20:06, Ronald F. Guilmette wrote:
I am still desperately seeking assistance to fix this problem. I have
done everything I can to follow the Handbook instructions to the letter
and Firefox is still choking up on the vast majority of web sites.
(Apparently, almost every site on the
Torsten Zuehlsdorff wrote:
> Thank you very much!
You're welcome. And, of course, welcome to maintainerhood :-) I think it's
a nice and productive way of getting involved with FreeBSD.
AvW
--
I'm not completely useless, I can be used as a bad example.
pgp3ofo0dRI56.pgp
Description: PGP signa
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-06-02 22:15:53 -0400, Koichiro Iwao wrote:
> Would you please update linux-sun-jdk17 to update 60?
> linux-sun-jdk17 port says:
>
> ===> linux-sun-jre17-7.55 You must manually fetch the J2SE RE
> download for the Linux platform (jre-7u60-lin
Hi!
> > I spoke too soon.
> >
> > The problem is back again.
> >
> > As a friend of mine used to say "Problems that go away by themselves
> > come back by themselves".
[...]
> Try changing "gfx.xrender.enabled" from True to False in about:config.
> This solved a similar problem with scaled image
On 6/4/14, 9:12 AM, Gary J. Hayers wrote:
On 04/06/2014 11:34, Darren Pilgrim wrote:
Requiring oauth will literally guarantee me and a whole bunch of other
people will never have bugzilla accounts.
I don't understand what the problem with logging in is? It surely is a
small price to pay for
PR ports/189050 was submitted at 27 April, with a patch for a trivial
problem. So far, over a month later, said PR is still stuck on "awaiting
maintainer feedback" so I'd say this qualifies as a maintainer timeout.
Could a committer at least have a quick look at this?
Furthermore, if (and only if
In message <20140604195803.gj2...@home.opsec.eu>,
Kurt Jaeger wrote:
>Hi!
>
>> > I spoke too soon.
>> >
>> > The problem is back again.
>> >
>> > As a friend of mine used to say "Problems that go away by themselves
>> > come back by themselves".
>[...]
>> Try changing "gfx.xrender.enabled" from
On Wed, Jun 4, 2014 at 12:59 AM, John Marino
wrote:
> On 6/4/2014 09:46, Torsten Zuehlsdorff wrote:
> >>
> >> I know for certain that people in the past have given up after
> submitting
> >> PRs that were never answered. While I know we don't have the manpower
> to
> >> deal with all of them, th
On 3 June 2014 16:13, Michelle Sullivan wrote:
> Eitan Adler wrote:
>> On 3 June 2014 10:11, John Marino wrote:
>>
>>> ... it's doubtful most folks unwilling to register are
>>> about to make a meaningful report...
>>>
>>
>> This is *not* the reason for registation.
>>
>> The reason for registati
On 3 June 2014 17:58, Julian H. Stacey wrote:
> Hi,
> Postmaster@ & webmaster@ are precedents. The orthogonal address
> should be bugmaster@, (with an alias from bugmeister for the lost).
> A random German Meister appended to Bug invites a French Maitre for next name.
bugmeister@ is precedent.
>
On 04/06/14 13:36, Gregory Orange wrote:
I've got poudriere building most of a set of ports with default
settings, default jail, 8.4-RELEASE amd64 both host and target.
However, it's failing on a couple at the fetch stage. For example,
databases/db42, db42-4.2.52_5 fails to build devel/libtool.
On Tue, 3 Jun 2014 21:02:47 +0200
"O. Hartmann" wrote:
>
> After today's update of port x11/xterm from xterm-304 to xterm-305, the
> terminals I start on the desktop (windowmaker) do not show any coloured
> prompt or characters - they have the same colour as the background! Flying
> blind!
>
>
36 matches
Mail list logo
