I'm seeing a weird "issue" with these 2 ports. I have the "check for
mismatched checksums" enabled for periodic, which is how I first noticed
this problem. Short version, whichever one I update last corrupts the
files of the other one.
Other than the mismatched checksums I haven't noticed any actu
Doug Barton ha scritto:
Other than the mismatched checksums I haven't noticed any actual
problems, so this is more of an "Is this a problem?" question.
AFAIK all ports should switch to giflib and libungif should be removed
from the tree.
--
Alex Dupre
On 01/26/2012 00:40, Alex Dupre wrote:
> Doug Barton ha scritto:
>> Other than the mismatched checksums I haven't noticed any actual
>> problems, so this is more of an "Is this a problem?" question.
>
> AFAIK all ports should switch to giflib and libungif should be removed
> from the tree.
Well 2
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: froxlor-0.9.22_3: no entry for
/usr/ports/databases/proftpd-mod_sql_mysql
make_index: syscp-1.4.2.1_3: no entry for
/usr/ports/databases/proftpd-mod_sql_mysql
Committers on the hook:
arved ashish dougb mm oliver
Doug Barton ha scritto:
Well 2 of the ports that I have on my desktop that were using it are
mine, so if it's agreed that this is the right direction to go I'm happy
to update. I just tested them and they seem to work fine.
Do it, please. If I remember correctly danfe@ proposed himself to do it
On 1/26/12 2:56 AM, Doug Barton wrote:
On the plus side, we have dozens of production FreeBSD VM's running on a
mid-size vSphere 4 development.
On the minus side this is down significantly from this time last year.
We are migrating to FreeBSD-on-KVM as fast as we can because VMware's
support f
Hello,
please update the port fusefs-ntfs.
current is: ntfs-3g_ntfsprogs-2012.1.15, released on January 22, 2012.
regard,
Raymond
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send an
Hello,
My answer to your message was considered as spam and rejected by your server.
Then I guess that the better way for us to communicate is you to send a PR.
Regards,
--
Th. Thomas.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.or
On Wed, Jan 18, 2012 at 5:39 AM, Heino Tiedemann
wrote:
> Michael Johnson wrote:
>
> > Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*'
> > show?
>
> Nothing. No Output.
>
I have the same problem, on two machines, with updated ports.
Machine a:
root@kg-v2# uname -a
FreeB
___
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"
Hello,
On Thu, Jan 26, 2012 at 1:24 AM, Zhihao Yuan wrote:
> On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann
> wrote:
> > Michael Johnson wrote:
> >
> >> Out of curiosity, what does 'grep xcb-aux
> /usr/local/libdata/pkgconfig/*'
> >> show?
> >
> > Nothing. No Output.
> >
> > Heino
> >
> > _
FreeBSD on ESX here. Unfortunately our boss wants us to move to Citrix Xen
even though they don't* support VMotion type features on FreeBSD because
we've spent upwards of $50,000 USD in support/licensing on VMWare over the
last year and it's been over a year without a fix to our crash bug
d
(followups set to ports@)
I am trying to track down a persistent bug in swatch.
swatch sets y $commandLineString = $0 . ' ' . join(' ', @ARGV);
, and if the len of the cmdargs is > (x?), then ps gets borked, rc
scripts can't find it (so service status won't work), service restart
won' t kill o
so, this hack is ugly. and I have been trying to track this down for YEARS.
swatch will (every now and then, some patch, some os upgrade, some
ARCH), will mash the $0 line and then rc.script can't status or stop it.
Good:
/swatch start
Starting swatch.
scanner.secnap.net# ps -auxww | grep sw
On Thu, Jan 26, 2012 at 5:23 AM, Torfinn Ingolfsen wrote:
> Hello,
>
> On Thu, Jan 26, 2012 at 1:24 AM, Zhihao Yuan wrote:
>
>> On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann
>> wrote:
>> > Michael Johnson wrote:
>> >
>> >> Out of curiosity, what does 'grep xcb-aux
>> /usr/local/libdata/pkgc
> ps -auxww | grep swatch
> root 86920 0.0 0.7 7496 6960 ?? Is9:33AM 0:00.01
> /usr/local/bin/perl /tmp//.swatch_script.86918
^^
> ./swatch status
> 329
> swatch is not running.
Ruling out the obvious, command_interpreter is
On 1/26/12 12:36 PM, rfl...@acsalaska.net wrote:
Also, it looks like swatch is creating a temporary script that is
actually run, so the status command is not supposed to find it.
It's a design issue upstream that you want them to find a better
solution for.
I am thinking:
either do what SHOU
Hello,
On Thu, Jan 26, 2012 at 6:20 PM, Kevin Oberman wrote:
> Have you run 'pkg-libchk -o | grep xcb-' from
> sysutils/bsdadminscripts? it should provide a list of ports that need
> to be re-built after the xcb-utils upgrade to 1.8.
>
> Funny, I logged in just now to write about this posting f
I have trouble with one of our boxes running FBSD 10.0/amd64 while
updating ports with portmaster. The box in question refuses
compiling/upgrading x11/kde4-workspace. I tried compiling with both
legacy GCC and CLANG.
What's going wrong and how can this repaired?
Thanks in advance,
Oliver
[ 72%
On 22/01/2012 10:40, Matthew Seaman wrote:
> On 21/01/2012 20:46, Mark Linimon wrote:
>> tl;dr: I want to switch the default assumption we're making.
>>
>> IMHO when new ports come into the tree, we should make our default
>> assumption that we will try to build them on amd64 and i386. For cases
>
"O. Hartmann" writes:
> I have trouble with one of our boxes running FBSD 10.0/amd64 while
> updating ports with portmaster. The box in question refuses
> compiling/upgrading x11/kde4-workspace. I tried compiling with both
> legacy GCC and CLANG.
>
> What's going wrong and how can this repaired?
On 1/26/12 12:41 PM, Michael Scheidell wrote:
On 1/26/12 12:36 PM, rfl...@acsalaska.net wrote:
Also, it looks like swatch is creating a temporary script that is
actually run, so the status command is not supposed to find it.
It's a design issue upstream that you want them to find a better
s
FreeBSD-8.2 amd64
I am unable to build nautilus. The build ends with this error message:
grep: /usr/local/lib/libxcb-aux.la: No such file or directory
sed: /usr/local/lib/libxcb-aux.la: No such file or directory
gnome-libtool: link: `/usr/local/lib/libxcb-aux.la' is not a valid libtool
archive
g
On Thu, 26 Jan 2012 11:20:27 -0600, Kevin Oberman
wrote:
Have you run 'pkg-libchk -o | grep xcb-' from
sysutils/bsdadminscripts? it should provide a list of ports that need
to be re-built after the xcb-utils upgrade to 1.8.
What's strange is that this didn't work for me the first five time
On 1/26/12 2:55 PM, Carmel wrote:
FreeBSD-8.2 amd64
I am unable to build nautilus. The build ends with this error message:
grep: /usr/local/lib/libxcb-aux.la: No such file or directory
sed: /usr/local/lib/libxcb-aux.la: No such file or directory
gnome-libtool: link: `/usr/local/lib/libxcb-aux
On Thu, 26 Jan 2012 16:36:54 -0500
Michael Scheidell articulated:
>
>
> On 1/26/12 2:55 PM, Carmel wrote:
> > FreeBSD-8.2 amd64
> >
> > I am unable to build nautilus. The build ends with this error
> > message:
> >
> > grep: /usr/local/lib/libxcb-aux.la: No such file or directory
> > sed: /usr/l
> On Thu, 26 Jan 2012 16:36:54 -0500
> I just ran "portclean -C" and then updated the ports tree, and deleted
> all old files in "/usr/ports/distfiles". I then attempted to build the
> port again. The exact same thing happened again. I checked, and the
> "/usr/local/lib/libxcb-aux.la" file does no
On Thu, 26 Jan 2012 13:49:44 -0900 (AKST)
rfl...@acsalaska.net articulated:
> > On Thu, 26 Jan 2012 16:36:54 -0500
>
> > I just ran "portclean -C" and then updated the ports tree, and
> > deleted all old files in "/usr/ports/distfiles". I then attempted
> > to build the port again. The exact same
> On Thu, 26 Jan 2012 13:49:44 -0900 (AKST)
> rfl...@acsalaska.net articulated:
>
>> > On Thu, 26 Jan 2012 16:36:54 -0500
>>
>> > I just ran "portclean -C" and then updated the ports tree, and
>> > deleted all old files in "/usr/ports/distfiles". I then attempted
>> > to build the port again. The e
On Thu, Jan 26, 2012 at 4:05 PM, wrote:
>> On Thu, 26 Jan 2012 13:49:44 -0900 (AKST)
>> rfl...@acsalaska.net articulated:
>>
>>> > On Thu, 26 Jan 2012 16:36:54 -0500
>>>
>>> > I just ran "portclean -C" and then updated the ports tree, and
>>> > deleted all old files in "/usr/ports/distfiles". I t
30 matches
Mail list logo
