On Thu, 5 Jun 2014 10:00:39 -0700 (PDT), Beeblebrox wrote:
> Anyone per chance with insight into "filter failed" error? I have already
> removed and re-created the printer several times.
>
> Installed cups related packages: cups-base-1.7.2_1, cups-client-1.7.2,
> cups-filters-1.0.53_1, cups-pdf-2.
On 6/6/2014 05:37, Paul Schmehl wrote:
> Something like that would have been more than adequate. As I pointed
> out, the warning you get about pkgng and the 9/1/2014 deadline is
> perfect. It's been there for a couple of months, and it pops up ever
> time you do a port. If you miss that and don't
Some time ago the port of mysql-server has an option to turn DTRACE
support via HAVE_DTRACE.
Currently this option is not available and the dtrace -l on startup
of the MySQL server does not show any mysql-related probes, so this
feature is disabled by default.
For whatever reason this support has
--On June 5, 2014 at 8:08:35 PM -0700 Alfred Perlstein
wrote:
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wr
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't c
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force
> people to upgrade? You couldn't come up with a warning system
> instead of outright breaking ports? The idiots are apparently
> running the asylum. {{sigh}}
>
th
For me, I had to upgrade an 8.2 FreeBSD to 10.0 current.
and got the same issue...
What I did was:
1) copy the "make" program from the 10.0 series to replace
the /usr/bin/make
2) copy via tar /usr/src /usr/obj from the 10.0 to the 8.2
cd /usr/src
export KERNCONF to the config in /usr/src/sys/amd6
Upgrade snappy to 1.1.1, and bump all related PORTREVISION to chase shared
library version.
PR: ports/190409
Submitted by: ports at robakdesign.com
Approved by:portmgr@ (for NO_STAGE)
-
Build ID: 201
W dniu 2014-06-05 23:43, Paul Schmehl pisze:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>
On 06/05/14 23:43, Paul Schmehl wrote:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>> of ou
On 6/5/2014 23:43, Paul Schmehl wrote:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>> of ou
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running
Hi,
Is it just me, or is Filezilla 3.8 currently unable to install?? I get
messages like these:
pkg-static:
lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/vi_VN/LC_MESSAGES/):
No such file or directory
pkg-static:
lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/l
Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force people to
> upgrade? You couldn't come up with a warning system instead of outright
> breaking ports? The idiots are apparently running the asylum. {{sigh}}
It might help to know exactly what you're talkin
On 6/06/2014 6:09 AM, Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force
> people to upgrade? You couldn't come up with a warning system instead
> of outright breaking ports? The idiots are apparently running the
> asylum. {{sigh}}
>
Are you referring to t
On Thu, Jun 5, 2014 at 10:22 PM, Rusty Nejdl wrote:
>
>
> I've spent a few days trying to get these ports to support staging and
> to actually compile with any version of GCC or CLANG and I cannot.
>
> games/vegastrike-data
> games/vegastrike
>
> Currently the last release from the developer was
That decided it was a good idea to completely break ports to force people
to upgrade? You couldn't come up with a warning system instead of outright
breaking ports? The idiots are apparently running the asylum. {{sigh}}
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious,
I've spent a few days trying to get these ports to support staging and
to actually compile with any version of GCC or CLANG and I cannot.
games/vegastrike-data
games/vegastrike
Currently the last release from the developer was 2 years ago. In
reading threads, there are numerous patches flyi
I've submitted a patch updating graphics/sng and taking maintainership:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188775
Regards,
BL
On Thu, Jun 5, 2014 at 11:19 AM, wrote:
> Dear port maintainer,
>
> The portscout new distfile checker has detected that one or more of your
> ports appe
I reinstalled cups-base from the public FreeBSD repo rather than my poudriere
repo. The web interface has started working once more, but printing
continues to fail, with job state showing: "stopped - Filter failed".
Anyone per chance with insight into "filter failed" error? I have already
removed
On Thu, 05 Jun 2014 09:39:21 -0500 Bryan Drewery wrote:
> I don't know what .la files are used for and have no time currently to
> research it.
>
> What is the impact to non-ports consumers of removing .la files? Do they
> also need patches to make them build?
Removing a .la file is somewhat li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129741
Baptiste Daroussin changed:
What|Removed |Added
Status|In Discussion |Needs Help
CC
I built a clean jail yesterday, portsnapped a new ports tree (i.e. fetch
and extract) and built portmaster. Then I did
"portmaster -dgGH x11/xorg". It seemed to build Xorg properly, but
there were no packages built for any of the many dependencies. I tried
an older portmaster version that used t
On 5/8/14, 5:16 PM, Tijl Coosemans wrote:
On Thu, 8 May 2014 21:27:56 +0200 Alexander Leidinger wrote:
On Thu, 8 May 2014 00:24:20 +0200
Tijl Coosemans wrote:
USES=libtool modifiers :keepla and :oldver.
You wasn't explicit, which may be beneficial for people which don't
have English as thei
Port is stage safe
-
Build ID: 20140602151200-43046
Job owner: pa...@freebsd.org
Buildtime: 3 days
Enddate: Thu, 05 Jun 2014 14:10:40 GMT
Revision: 356235
Repository:
On 2014-06-04 19:03, Matthieu Volat wrote:
> 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
On Thu, Jun 05, 2014 at 03:35:49PM +0600, Muhammad Moinur Rahman wrote:
> Hi,
>
> Can anyone please tell me what are the jails used in pkg-fallout-freebsd? I
> can see that 9.1 is still being used. Beside these what are the legacy
> versions those are used in the builder?
>
> Thanks in advance.
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
Hi,
Can anyone please tell me what are the jails used in pkg-fallout-freebsd? I
can see that 9.1 is still being used. Beside these what are the legacy
versions those are used in the builder?
Thanks in advance.
BR,
Muhammad
___
freebsd-ports@freebsd.org
"# service cupsd onestart", then http://localhost:631/ > "Not Found" message
on browser page.
I can print through LPD, but cannot print through any cups defined printer.
* print/cups-base enabled options: LIBPAPER, PYTHON, DBUS, XDG_OPEN,
MDNSRESPONDER
* I have completely removed /usr/local/etc/cu
> On 05 Jun 2014, at 10:49, Anton Shterenlikht wrote:
>
> And what is this file for:
>
> $ cat /usr/ports/.arcconfig
> {
>"project.name": "P",
>"phabricator.uri" : "https://phabric.freebsd.org/";
> }
See https://wiki.freebsd.org/CodeReview
>
> Thanks
>
> Anton
> __
And what is this file for:
$ cat /usr/ports/.arcconfig
{
"project.name": "P",
"phabricator.uri" : "https://phabric.freebsd.org/";
}
Thanks
Anton
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
On 05.06.2014 02:19, Kevin Oberman wrote:
On Wed, Jun 4, 2014 at 12:59 AM, John Marino mailto:freebsd.cont...@marino.st>> 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 n
34 matches
Mail list logo
