On Sat, 6 Feb 2010, Sergey Skvortsov wrote:
SS> Default Perl version is changed to 5.10.
SS>
SS> This change does not affect systems with already installed Perl (5.8 or
5.10).
SS>
SS> Only for systems without installed Perl new 5.10 port will be used.
SS>
SS> If you have already installed lang
06.02.2010 01:50, Erik Trulsson пишет:
On Fri, Feb 05, 2010 at 06:25:42PM +0300, cvs-...@yandex.ru wrote:
Hi there.
I see some massive port update in past hours, but not see what the
reason of it (nor on freebsd-ports@, nor on freshports.org). Can
anybody shed the light what was changed?
The
On Sat, 6 Feb 2010, Dmitry Morozovsky wrote:
DM> SS> Default Perl version is changed to 5.10.
DM>
DM> >>>
DM> r...@woozle:/usr/ports# portupgrade -o lang/perl5.10 -f perl-5.8.\*
DM> ---> Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.10)
DM> ---> Building '/usr/ports/lang/perl5.10'
DM> =
It appears CONFLICTS is checked before build instead of checking
it before install. Why?
# portmaster -Do lang/perl5.10 lang/perl5.8
===>>> Currently installed version: perl-threaded-5.8.9_3
===>>> Port directory: /usr/ports/lang/perl5.10
===>>> Launching 'make checksum' for lang/perl5.10 in back
Ion-Mihai Tetcu wrote:
> On Fri, 05 Feb 2010 18:25:42 +0300
> cvs-...@yandex.ru wrote:
>
>> Hi there.
>> I see some massive port update in past hours, but not see what the
>> reason of it (nor on freebsd-ports@, nor on freshports.org). Can
>> anybody shed the light what was changed? Thanks.
>
>
On 06/02/2010 09:36, Dominic Fandrey wrote:
> It appears CONFLICTS is checked before build instead of checking
> it before install. Why?
>
> # portmaster -Do lang/perl5.10 lang/perl5.8
>
> ===>>> Currently installed version: perl-threaded-5.8.9_3
> ===>>> Port directory: /usr/ports/lang/perl5.10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2010 09:40, Heino Tiedemann wrote:
> Shouldn't there be an entry in UPDATING, that "jpeg" has to be
> rebuildet first?
>
> I rebuilded everything - but i have no idea about the order aof port
> reinstalling.
Actually that's not necessary in
Since yesterday's portsnape and attempt updating my ports, ALL FreeBSD
boxes (running FreeBSD 8.0/amd64) fail to update ports via 'portmaster
-av' at the same point with the following error.
It seems that that port jpeg-8 has been updated and now offering
libjpeg.so.11 instead of the desired o
Matthew Seaman wrote:
> On 06/02/2010 09:36, Dominic Fandrey wrote:
>> It appears CONFLICTS is checked before build instead of checking
>> it before install. Why?
>> ...
>
> There was a discussion about this over on questions recently, starting here:
> http://lists.freebsd.org/pipermail/freebsd-qu
On Sat, 06 Feb 2010 11:13:08 +0100
"O. Hartmann" wrote:
> Since yesterday's portsnape and attempt updating my ports, ALL
> FreeBSD boxes (running FreeBSD 8.0/amd64) fail to update ports via
> 'portmaster -av' at the same point with the following error.
>
> It seems that that port jpeg-8 has been
On Sat, 6 Feb 2010 12:49:52 +0200
Ion-Mihai Tetcu wrote:
> On Sat, 06 Feb 2010 11:13:08 +0100
> "O. Hartmann" wrote:
>
> > Since yesterday's portsnape and attempt updating my ports, ALL
> > FreeBSD boxes (running FreeBSD 8.0/amd64) fail to update ports via
> > 'portmaster -av' at the same point
Do you are behind of proxy? This happens when have a proxy.
Regards,
Sylvio Cesar
2010/2/6 Jacob Myers :
> Hello,
>
> It seems portsnap1.freebsd.org has some sort of issue:
>
> IND-Serv003# portsnap fetch
> Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
> Fetching public key from
On Wed, 3 Feb 2010, Philip Paeps wrote:
PP> On 2010-02-01 16:40:45 (-0500), Mike Jakubik
wrote:
PP> > I am trying to obtain a daily smart status report on one of my servers
PP> > which uses a 3ware controller. To access these devices from
PP> > smartmontools you need to refer to each drive as
On Sat, 6 Feb 2010, Dmitry Morozovsky wrote:
DM> PP> > I am trying to obtain a daily smart status report on one of my
servers
DM> PP> > which uses a 3ware controller. To access these devices from
DM>
DM> Please try the patch attached. Note that you have to specify your 3ware
disks
DM> as
DM>
On Sat, 6 Feb 2010, Dmitry Morozovsky wrote:
DM> DM> r...@woozle:/usr/ports# portupgrade -o lang/perl5.10 -f perl-5.8.\*
DM> DM> ---> Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.10)
DM> DM> ---> Building '/usr/ports/lang/perl5.10'
DM> DM> ===> Cleaning for perl-5.10.1
DM> DM>
DM> DM>
There is a new jpeg 8 and you need to rebuild with for example portmaster -r
jpeg-\* if you use a portmaster (there are instructions in
/usr/ports/UPDATING).
But antwhere I have a problem with arts where I get an error 1. I am trying
again and will sent what kind of error I got.
On Sat, Feb 6, 2
Hi all,
Last night portsnap1 and portsnap2 broke under the combined load of the recent
ports mega-commit and a broken SSH firewalling script (mea culpa...). When I
woke up this morning they both had load averages of 300+ and couldn't fork to
allow me to log in. :-(
I've brought portsnap1 back on
On 02/06/10 16:24, Timur I. Bakeyev wrote:
Hi!
On Fri, Feb 05, 2010 at 11:02:18AM +, O. Hartmann wrote:
Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the
following error and it seems a bit sticky.
Check, that there is no memcache.h somewhere in your include paths, in
On Fri, Feb 05, 2010 at 10:42:09PM -0500, jhell wrote:
>
> I could have swore that I recently heard an announcement that barred this
> type of activity until after 7.3-RELEASE was made
>
> Guess that doesn't stand for everything.
>
As other people have already pointed out, the freeze itself
Hi, Spil!
On Fri, Feb 05, 2010 at 03:42:04PM +0100, Spil Oss wrote:
> On Fri, Feb 5, 2010 at 3:36 PM, Spil Oss wrote:
> >
> > First error was the pid-files related to /var/run/samba34 not existing
> >
> > Second error
> > "initialise_wins: failed to open wins.tdb. Error was No such file or
> > d
Hi!
On Fri, Feb 05, 2010 at 11:02:18AM +, O. Hartmann wrote:
> Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the
> following error and it seems a bit sticky.
Check, that there is no memcache.h somewhere in your include paths, in
particular in /usr/local/include.
Also, t
On Sat, 6 Feb 2010 07:53:04 -0600
Franci Nabalanci wrote:
> On Sat, Feb 6, 2010 at 4:58 AM, Ion-Mihai Tetcu
> wrote:
>
> > On Sat, 6 Feb 2010 12:49:52 +0200
> > Ion-Mihai Tetcu wrote:
> >
> > > On Sat, 06 Feb 2010 11:13:08 +0100
> > > "O. Hartmann" wrote:
> > >
> > > > Since yesterday's ports
Hi!
It looks like the problem was created by the --with-fhs flag, which
reset cachedir and statedir do it's default values.
With the flag removed those directories are the same as the lockdir.
Not sure, why rundir wasn't created by the package - this is done by
pkg-install script and should work
Hi, Oliver!
On Sat, Feb 6, 2010 at 4:46 PM, O. Hartmann
wrote:
> On 02/06/10 16:24, Timur I. Bakeyev wrote:
>> On Fri, Feb 05, 2010 at 11:02:18AM +, O. Hartmann wrote:
>>>
>>> Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the
>>> following error and it seems a bit sticky.
Matthew Seaman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2010 09:40, Heino Tiedemann wrote:
Shouldn't there be an entry in UPDATING, that "jpeg" has to be
rebuildet first?
I rebuilded everything - but i have no idea about the order aof port
reinstalling.
Actually that's
On Sat, 06 Feb 2010 21:05:54 +0100
Miroslav Lachman <000.f...@quip.cz> wrote:
> Matthew Seaman wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 06/02/2010 09:40, Heino Tiedemann wrote:
> >
> >> Shouldn't there be an entry in UPDATING, that "jpeg" has to be
> >> rebuildet fir
On Saturday 06 February 2010 04:49:52 Ion-Mihai Tetcu wrote:
> On Sat, 06 Feb 2010 11:13:08 +0100
>
> "O. Hartmann" wrote:
> > Since yesterday's portsnape and attempt updating my ports, ALL
> > FreeBSD boxes (running FreeBSD 8.0/amd64) fail to update ports via
> > 'portmaster -av' at the same poi
On Sat, Feb 6, 2010 at 12:45 PM, Ion-Mihai Tetcu wrote:
> On Sat, 06 Feb 2010 21:05:54 +0100
> Miroslav Lachman <000.f...@quip.cz> wrote:
>
>> Matthew Seaman wrote:
>> > -BEGIN PGP SIGNED MESSAGE-
>> > Hash: SHA1
>> >
>> > On 06/02/2010 09:40, Heino Tiedemann wrote:
>> >
>> >> Shouldn't th
Ion-Mihai Tetcu wrote:
On Sat, 06 Feb 2010 21:05:54 +0100
Miroslav Lachman<000.f...@quip.cz> wrote:
Matthew Seaman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2010 09:40, Heino Tiedemann wrote:
Shouldn't there be an entry in UPDATING, that "jpeg" has to be
rebuildet first
The recent change to jpeg required a lot of changes to a lot of ports all
just to bump a version number.
It is easy to miss things this way and requires a lot of work and
downloading.
I propose that some kind of MAJORVERSION be stored in /var/db/ports. Then
when a library's MAJORVERSION is changed
On Saturday 06 February 2010 15:36:22 Miroslav Lachman wrote:
> Ion-Mihai Tetcu wrote:
> > On Sat, 06 Feb 2010 21:05:54 +0100
> >
> > Miroslav Lachman<000.f...@quip.cz> wrote:
> >> Matthew Seaman wrote:
> >>> -BEGIN PGP SIGNED MESSAGE-
> >>> Hash: SHA1
> >>>
> >>> On 06/02/2010 09:40, Hein
My solution I work witho about 50 freebsd servers, is
to setup ONE server for each type (7.2,8.0) and install all the
ports I need..
Than using rsync I export
the /var/db/ports, /var/db/portsnap, /usr/ports (excluding
distfiles,packages, and work dirs)...
Than I use rsync and portsnap -PP -aBd
On Sat, Feb 06, 2010 at 11:48:33PM +0200, Eitan Adler wrote:
> The recent change to jpeg required a lot of changes to a lot of ports all
> just to bump a version number.
That is true, there is a script for in /usr/ports/Tools/scripts/
called bump_version.pl which can do most of the magic.
> It is
On Sat, Feb 06, 2010 at 03:53:57PM -0600, ajtiM wrote:
> I don't know why is a rush for something which doesn't work?
All the individual package builds were tested on our 'clean' build
environment (pointyhat.freebsd.org). portmgr wouldn't have approved
the commit otherwise.
We can't test every u
On Saturday 06 February 2010 17:47:05 Mark Linimon wrote:
> On Sat, Feb 06, 2010 at 03:53:57PM -0600, ajtiM wrote:
> > I don't know why is a rush for something which doesn't work?
>
> All the individual package builds were tested on our 'clean' build
> environment (pointyhat.freebsd.org). portmgr
On 2/6/2010 1:53 PM, ajtiM wrote:
> And in my case, I use portmaster, rebuilding of QT33 and arts doesn't work
> and
> I screw many applications. Thank you for your hard work but I don't know why
> is a rush for something which doesn't work?
I'm sorry to hear that you had problems with portmast
On 2/6/2010 12:52 PM, Garrett Cooper wrote:
> Excessive documentation is not any more helpful than no
> documentation. I would think it's relatively common sense to rebuild
> all applications that depend upon a library,
When that library bumps the major version, yes. If not, it's rarely
necess
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
On Sun, Feb 7, 2010 at 12:27 AM, Edwin Groothuis wrote:
> On Sat, Feb 06, 2010 at 11:48:33PM +0200, Eitan Adler wrote:
> > The recent change to jpeg required a lot of changes to a lot of ports all
> > just to bump a version number.
>
> That is true, there is a script for in /usr/ports/Tools/scrip
44 matches
Mail list logo
