gt; and proceeded usual rebuilding procedure.
>
> Fortunately, there was only 3 commits between r298836 and r298920,
> and I got right one in first attempt.
>
> But unfortunately, fixing portupgrade[-devel] or file/libmagic beyonds
> my hand. :-<
I have taken Tomoaki'
On Thu, 27 Jun 2013 16:14:31 +0200, Chris H wrote:
Warren Block wrote:
On Wed, 26 Jun 2013, Chris H wrote:
On Wed, 26 Jun 2013, Chris H wrote:
Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg
The last one is the most recently modified. Update your ports tr
On Thu, 27 Jun 2013, Garrett Wollman wrote:
In article ,
wbl...@wonkity.com writes:
On Thu, 27 Jun 2013, Garrett Wollman wrote:
Having just gone through this in two different environments, I can
very very strongly recommend doing the following. It's not the "easy
button" of the TV commercial
In article ,
wbl...@wonkity.com writes:
>On Thu, 27 Jun 2013, Garrett Wollman wrote:
>
>> Having just gone through this in two different environments, I can
>> very very strongly recommend doing the following. It's not the "easy
>> button" of the TV commercials, but it will make things much much
>
> Warren Block wrote:
>> On Wed, 26 Jun 2013, Chris H wrote:
On Wed, 26 Jun 2013, Chris H wrote:
Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg
The last one is the most recently modified. Update your ports tree,
follow all the
Warren Block wrote:
On Wed, 26 Jun 2013, Chris H wrote:
On Wed, 26 Jun 2013, Chris H wrote:
Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg
The last one is the most recently modified. Update your ports tree,
follow all the steps that apply to your system sin
On Thu, 27 Jun 2013, Garrett Wollman wrote:
Having just gone through this in two different environments, I can
very very strongly recommend doing the following. It's not the "easy
button" of the TV commercials, but it will make things much much
easier in the future.
This is an interesting pro
t I already have installed, _and_ respect the "options"
>> > used during the
>> > original make && make install, or those options expressed in make.conf.
>> > As portupgrade(1) && portmaster(8) appear to be the most used in this
>> > sce
> In article <5e20544e3580a75759c3858f31894dc9.authentica...@ultimatedns.net>,
> bsd-li...@lcommand.com writes:
>
>> I haven't upgraded my tree(s) for awhile. My last attempt to rebuild
>>after an updating
>>src && ports, resulted in nearly installing the entire ports tree, which
>>is why I've
>>wa
In article <5e20544e3580a75759c3858f31894dc9.authentica...@ultimatedns.net>,
bsd-li...@lcommand.com writes:
> I haven't upgraded my tree(s) for awhile. My last attempt to rebuild
>after an updating
>src && ports, resulted in nearly installing the entire ports tree, which
>is why I've
>waited so l
.
That should say "all the steps in /usr/ports/UPDATING that apply to your
system since that date."
I recommend portmaster. It does almost everything portupgrade does, but
without the overhead of Ruby or bdb.
Greetings Warren, and thank you for your reply.
Sounds like the plan. I&#x
> On Wed, Jun 26, 2013 at 05:34:45PM -0700, Chris H wrote:
>> Greetings, and thank you for your reply.
>>
>> I understand that portupgrade _will_ pull in other dependencies _as
>> needed_ -- I _do_ read the man(1) pages. :)
>>
>> But it installed (pull
that it doesn't appear to honor the original build
>> options recorded in /var/db/ports//options. Nor, do I recall that
>> it
>> honored /etc/make.conf -- make.conf(5). Maybe things have changed?
>
> Both portupgrade and portmaster did and do honor these. Both are
&g
On Wed, Jun 26, 2013 at 05:34:45PM -0700, Chris H wrote:
> Greetings, and thank you for your reply.
>
> I understand that portupgrade _will_ pull in other dependencies _as
> needed_ -- I _do_ read the man(1) pages. :)
>
> But it installed (pulled in) far more than those depen
build
options recorded in /var/db/ports//options. Nor, do I recall that it
honored /etc/make.conf -- make.conf(5). Maybe things have changed?
Both portupgrade and portmaster did and do honor these. Both are
automated versions of installing the ports manually. That can be
overridden wit
e
>> waited so long. Try as I might, I've had great difficulty finding something
>> that will
>> _only_ upgrade what I already have installed, _and_ respect the "options"
>> used during the
>> original make && make install, or those options expre
On 27/06/2013, at 5:53, Jeremy Chadwick wrote:
> cd /usr/ports/whatever
> make install clean
> {lather rinse repeat until done}
The faster version of this is
find /usr/ports -maxdepth 3 -name work -type d -print0 | xargs -0 rm -rf
Simpler is to put..
WRKDIRPREFIX=/foo/bar
in /etc/make.conf
The
On Wed, 26 Jun 2013, Jeremy Chadwick wrote:
When rebuilding everything, I have always resorted to this:
rsync -avH /usr/local/ /usr/local.old/
pkg_delete -a -f
rm -fr /usr/local/*
rm -fr /var/db/ports/*
rm -fr /usr/ports/distfiles/*
cd /usr/ports/whatever
make install clean
{lather rinse repeat
used during the
> > original make && make install, or those options expressed in make.conf.
> > As portupgrade(1) && portmaster(8) appear to be the most used in this
> > scenario,
> > I'm soliciting opinions on which of these works best, or if th
On Wed, Jun 26, 2013 at 01:23:32PM -0700, Jeremy Chadwick wrote:
> On Wed, Jun 26, 2013 at 09:42:43AM -0700, Chris H wrote:
> {snipping}
Also, hoping the OP is subscribed to -stable -- you should probably deal
with this. This is not the first time I've seen problems with mail
delivery to a 1comma
ed so long. Try as I might, I've had great difficulty finding something
> that will
> _only_ upgrade what I already have installed, _and_ respect the "options"
> used during the
> original make && make install, or those options expressed in make.conf.
> As port
s I might, I've had great difficulty finding something
> that will
> _only_ upgrade what I already have installed, _and_ respect the "options"
> used during the
> original make && make install, or those options expressed in make.conf.
> As portupgrade(1) &&a
l
_only_ upgrade what I already have installed, _and_ respect the "options" used
during the
original make && make install, or those options expressed in make.conf.
As portupgrade(1) && portmaster(8) appear to be the most used in this scenario,
I'm soliciting opinions
On 12/20/12 00:21, CeDeROM wrote:
On Wed, Dec 19, 2012 at 11:57 PM, Jakub Lach wrote:
Prerelease was using -STABLE packages.
Are -stable packages in sync with port tree? Are -release frozen
version of -stable when a release is made?
Magic of enviroment variables...
http://www.freebsd.org/doc
On Thu, Dec 20, 2012 at 2:05 PM, Bas Smeelen wrote:
> I don't know what the current pkg repositories for the new generation pkg
> tools (or the older pkg_tools) are, thus I build them for myself with
> poudriere.
I prefer to use binary packages that are consistent and well tested.
Many times I ha
e with the make tools or you can use portmaster, portupgrade and
friends for keeping them up to date via source and/or binary packages.
I also was wondering why on RC portupgrade was working fine, while on
a release it failed. I know there are no packages yet and no release,
but it should fal
ore for a current port
tree (or its up to date snapshot).
It would be great to have debian's "apt-get" functionality in FreeBSD :-)
I also was wondering why on RC portupgrade was working fine, while on
a release it failed. I know there are no packages yet and no release,
but it s
On 12/20/12 00:21, CeDeROM wrote:
On Wed, Dec 19, 2012 at 11:57 PM, Jakub Lach wrote:
Prerelease was using -STABLE packages.
Are -stable packages in sync with port tree? Are -release frozen
version of -stable when a release is made?
Magic of enviroment variables...
http://www.freebsd.org/doc
On Wed, Dec 19, 2012 at 11:57 PM, Jakub Lach wrote:
> Prerelease was using -STABLE packages.
Are -stable packages in sync with port tree? Are -release frozen
version of -stable when a release is made?
> Magic of enviroment variables...
> http://www.freebsd.org/doc/handbook/packages-using.html
Y
Prerelease was using -STABLE packages.
Magic of enviroment variables...
http://www.freebsd.org/doc/handbook/packages-using.html
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portupgrade-problem-after-upgrading-to-9-1-PRE-RELEASE-tp5770666p5770897.html
Sent from the
On Wed, Dec 19, 2012 at 5:50 PM, Ben Morrow wrote:
> 9.1-RELEASE isn't out yet. That means the packages may not have been
> built yet, and even if they have, they may not be right. Wait for the
> release announcement.
Yes I know there is no release yet, but I can test what is already out there :-
Quoth CeDeROM :
>
> I was using portupgrade/portinstall -PP on 9.1-RC3 with no problem.
> After freebsd-update -r 9.1-RELEASE I cannot install any port from
> packages. Should I additionally configure my system somehow? Where did
> the portupgrade took the packages from last time /
Hello :-)
I was using portupgrade/portinstall -PP on 9.1-RC3 with no problem.
After freebsd-update -r 9.1-RELEASE I cannot install any port from
packages. Should I additionally configure my system somehow? Where did
the portupgrade took the packages from last time / before upgrade?
Any hints
Hi!
> >>>> Worst of all, you're running portupgrade from cron without
> >>>> reading UPDATING, which is just asking for trouble.
> >>> What specifically is your concern here?
> Yes, but updating correctly in first place is better than trying to
On Sun, Oct 23, 2011 at 2:14 PM, Stefan Bethke wrote:
> Am 23.10.2011 um 13:11 schrieb Ross:
>
>> On Sun, Oct 23, 2011 at 1:32 PM, Stefan Bethke wrote:
>>> Am 23.10.2011 um 08:47 schrieb Chris Rees:
>>>
>>>> Worst of all, you're running portu
Am 23.10.2011 um 08:47 schrieb Chris Rees:
> Worst of all, you're running portupgrade from cron without reading UPDATING,
> which is just asking for trouble.
What specifically is your concern here?
I've been running portupgrade from cron for six years on a multitude of sys
I won't be in a position to create a simpler test case, raise a PR or
> >>> try patches till Tuesday evening (UK) at the earliest.
> >
> >> So far I have been unable to reproduce the problem with portupgrade
(and
> >> will probably move to portmaster).
> &
On Sat, Oct 15, 2011 at 10:45:18PM +0300, Mikolaj Golub wrote:
> On Sat, 15 Oct 2011 11:50:22 +0200 Stefan Bethke wrote:
> SB> Seems to do the trick, thanks!
> Thanks for testing! Committed. I am going to MFC it soon.
Gentlemen, thank you!
I can confirm that at $JOB with a RELENG_8 system post t
On Sat, 15 Oct 2011 11:50:22 +0200 Stefan Bethke wrote:
SB> Am 15.10.2011 um 09:36 schrieb Mikolaj Golub:
>>
>> On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote:
>>
>> SB> I finally figured out why my ports aren't updating anymore: when
>>
Am 15.10.2011 um 09:36 schrieb Mikolaj Golub:
>
> On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote:
>
> SB> I finally figured out why my ports aren't updating anymore: when running
> portupgrade -a --batch from cron, stdin is /dev/null, and that produces the
>
On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote:
SB> I finally figured out why my ports aren't updating anymore: when running
portupgrade -a --batch from cron, stdin is /dev/null, and that produces the
gobs of ^D in the output, as well as the script file that portupgrade
>> > try patches till Tuesday evening (UK) at the earliest.
>> So far I have been unable to reproduce the problem with portupgrade (and
>> will probably move to portmaster).
>> I have however found a different but possibly related problem with the
>> new ver
r I have been unable to reproduce the problem with portupgrade (and
AW> will probably move to portmaster).
AW> I have however found a different but possibly related problem with the
AW> new version of script in RELENG_8, for which I have raised this PR:
AW> misc/161526: script out
try patches till Tuesday evening (UK) at the earliest.
>
>> So far I have been unable to reproduce the problem with portupgrade (and
>> will probably move to portmaster).
>
>> I have however found a different but possibly related problem with the
>> new version of s
r I have been unable to reproduce the problem with portupgrade (and
> will probably move to portmaster).
> I have however found a different but possibly related problem with the
> new version of script in RELENG_8, for which I have raised this PR:
> misc/161526: script outputs corr
On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote:
> I won't be in a position to create a simpler test case, raise a PR or
> try patches till Tuesday evening (UK) at the earliest.
So far I have been unable to reproduce the problem with portupgrade (and
will proba
ose to idle)
when running a batch job which calls portupgrade. I had two hangs, in
different places, while upgrading the first package. Process trees
below.
Reverting to an older version of script (1.24.30.4 2010/10/14 01:21:44
obrien) showed the 100% processor utilisation problem, but at least my
p
On Tue, 04 Oct 2011 18:34:07 +0200 Michiel Boland wrote:
MB> On 10/04/2011 13:15, Mikolaj Golub wrote:
>> On Sun, Sep 18, 2011 at 1:58 PM, Mikolaj Golub wrote:
MB> [...]
>>>
>>> I believe the behaviour is after this commit:
>>>
>>> http://svnweb.freebsd.org/base?view=revision&revision=125
-0400, Jason Hellenthal wrote:
>>> On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
>>> > Hi,
>>> >
>>> > I'm running portupgrade in screen to update all the ports for
>>> > 9-BETA2/9-CURRENT on amd64. While doing this
On 10/04/2011 13:15, Mikolaj Golub wrote:
On Sun, Sep 18, 2011 at 1:58 PM, Mikolaj Golub wrote:
[...]
I believe the behaviour is after this commit:
http://svnweb.freebsd.org/base?view=revision&revision=125848
I think we should skip select on STDIN after reading EOF from it, like in the
patc
> >>> On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
> >>> > Hi,
> >>> >
> >>> > I'm running portupgrade in screen to update all the ports for
> >>> > 9-BETA2/9-CURRENT on amd64. While doing this script eat
On Sep 18, 2011 11:25 AM, "Kostik Belousov" wrote:
> Please note that interpreting the receiving of 0 bytes on the terminal
> as EOF is only a convention. If done absolutely properly, script shall
> not interpret zero-byte read as EOF. Might be, the reasonable thing to
> do would be to only look a
On Sun, Sep 18, 2011 at 11:57:57PM +0300, Mikolaj Golub wrote:
>
> On Sun, 18 Sep 2011 20:24:23 +0300 Kostik Belousov wrote:
>
> KB> On Sun, Sep 18, 2011 at 02:54:34PM +0300, Mikolaj Golub wrote:
> >>
> >> On Sun, 18 Sep 2011 13:25:26 +0200 Ronald Klop wrote:
> >>
> >> RK> It is a while s
On Sun, 18 Sep 2011 20:24:23 +0300 Kostik Belousov wrote:
KB> On Sun, Sep 18, 2011 at 02:54:34PM +0300, Mikolaj Golub wrote:
>>
>> On Sun, 18 Sep 2011 13:25:26 +0200 Ronald Klop wrote:
>>
>> RK> It is a while since I programmed C, but why will writing 0 bytes give
>> RK> the reader an e
On Sun, Sep 18, 2011 at 02:54:34PM +0300, Mikolaj Golub wrote:
>
> On Sun, 18 Sep 2011 13:25:26 +0200 Ronald Klop wrote:
>
> RK> It is a while since I programmed C, but why will writing 0 bytes give
> RK> the reader an end-of-file? Shouldn't the fd be closed to indicate
> RK> end-of-file?
>
>
On Sun, 18 Sep 2011 13:25:26 +0200 Ronald Klop wrote:
RK> It is a while since I programmed C, but why will writing 0 bytes give
RK> the reader an end-of-file? Shouldn't the fd be closed to indicate
RK> end-of-file?
AFAIR, this trick with writing 0 to emulate EOF because we can't close the fd
t;> > Hi,
>>> >
>>> > I'm running portupgrade in screen to update all the ports for
>>> > 9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
>>> > Because portupgrade -fa crashed I'm running this command to update the
>
Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
>>> > Hi,
>>> >
>>> > I'm running portupgrade in screen to update all the ports for
>>> > 9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
>>> > Because portupgr
>> Hi,
> >>>
> >>> I'm running portupgrade in screen to update all the ports for
> >>> 9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
> >>> Because portupgrade -fa crashed I'm running this command to update the
> >
On Sun, 18 Sep 2011 07:39:01 +0200, Jeremy Chadwick
wrote:
On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
> Hi,
>
> I'm running portupgrade in screen to update all the ports for
> 9-BETA2/9
On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
> On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
> > Hi,
> >
> > I'm running portupgrade in screen to update all the ports for
> > 9-BETA2/9-CURRENT on amd64. While doing this s
Hi,
I'm running portupgrade in screen to update all the ports for
9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
Because portupgrade -fa crashed I'm running this command to update the
remaining non-updates ports.
find /var/db/pkg -name +DESC -mtime +2 |cut
so I
suppose it's
like login name field); however, entering anything there does not lead
anywhere.
portupgrade -f gdm does not help; portupgrade -f ${direct gdm
dependencies}
does not help, either.
And, of course, I even rebooted the machine without a bit of success.
Any hints? Thanks
, entering anything there does not lead
anywhere.
portupgrade -f gdm does not help; portupgrade -f ${direct gdm dependencies}
does not help, either.
And, of course, I even rebooted the machine without a bit of success.
Any hints? Thanks in advance!
--
Sincerel
[If you reply, please strip off freebsd-stable@, thanks.]
Jens Rasmus Liland wrote:
> That seems to have have done something more. But I still got some funky
> errors after running portmaster -a:
> ===>>> The x11/xphelloworld port has been deleted: Xprint application,
> deprecated upstream
> ===>
Oh, I did forget to forward this to the list.
-- Forwarded message --
From: Jens Rasmus Liland
Date: Sun, Aug 2, 2009 at 3:46 PM
Subject: Re: Error when using 'portupgrade -ay' (and several others) [Second
attempt]
To: Greg Miller
[r...@machine ~]# pkg_deinstall -f
is out of ideas on what I am to do. I've tried to fix the problem
> > > using many different methods (i.e. csup stable-ports-supfile;
> > > Portmaster
> >
> > -a/-af,
> >
> > > portupgrade -ay, nuking the entire ports tree and then doing fetch
> &g
>>> The x11/xphelloworld port has been deleted: Xprint application,
deprecated upstream
===>>> Aborting update
[r...@machine ~]#
On Sat, Aug 1, 2009 at 8:58 PM, Barney Wolff wrote:
> portupgrade -k x11-drivers/xorg-drivers x11/xorg
> Barney
>
> On Sat, Aug 01, 200
portupgrade -k x11-drivers/xorg-drivers x11/xorg
Barney
On Sat, Aug 01, 2009 at 07:50:45PM +0200, Jens Rasmus Liland wrote:
> So what command am I supposed to run?
>
> On Sat, Aug 1, 2009 at 4:50 PM, Barney Wolff wrote:
>
> > I got around this by using -k. Dependencies ar
e. csup stable-ports-supfile; Portmaster -a/-af,
portupgrade -ay, nuking the entire ports tree and then doing fetch ports;
extract, and similar stuff), but everyone seems to get the same error,
and
not come any further. The ports my system is trying to update is not in
the
ports tree anymore eit
and he
> > is out of ideas on what I am to do. I've tried to fix the problem using
> > many different methods (i.e. csup stable-ports-supfile; Portmaster
> -a/-af,
> > portupgrade -ay, nuking the entire ports tree and then doing fetch ports;
> > extract, and simil
problem using many
> > different methods (i.e. csup stable-ports-supfile; Portmaster -a/-af,
> > portupgrade -ay, nuking the entire ports tree and then doing fetch ports;
> > extract, and similar stuff), but everyone seems to get the same error,
> and
> > not come any furthe
s (i.e. csup stable-ports-supfile; Portmaster -a/-af,
> portupgrade -ay, nuking the entire ports tree and then doing fetch ports;
> extract, and similar stuff), but everyone seems to get the same error, and
> not come any further. The ports my system is trying to update is not in the
> ports tree
rts. I've
> already discussed this with Dan Naumov on the stable mailing list, and he is
> out of ideas on what I am to do. I've tried to fix the problem using many
> different methods (i.e. csup stable-ports-supfile; Portmaster -a/-af,
> portupgrade -ay, nuking the entire ports t
rtmaster -a/-af,
portupgrade -ay, nuking the entire ports tree and then doing fetch ports;
extract, and similar stuff), but everyone seems to get the same error, and
not come any further. The ports my system is trying to update is not in the
ports tree anymore either, so it is really strange that
On Fri, Jul 10, 2009 at 9:00 PM, Jens Rasmus Liland wrote:
> Hello!
>
> I had an error just now running 'portupgrade -ay'. Got this output:
>
> ---OUTPUT START---
>
> ---> Session started at: Fri, 10 Jul 2009 18:58:30 +0200
> ** Port directory not found:
Hello!
I had an error just now running 'portupgrade -ay'. Got this output:
---OUTPUT START---
---> Session started at: Fri, 10 Jul 2009 18:58:30 +0200
** Port directory not found: x11-drivers/xf86-video-vga
** Port marked as IGNORE: x11-drivers/xf86-video-via:
requires pciVid
Gianni Doe wrote:
I'm upgrading a system from 6.4 to 7.1 and rebuilding all the ports.
I'd rather use packages where present to speed things up a bit so I'm
using:
# portupgrade -faP
The problem is that it never finds the packages as the URL is invalid,
there seems to be
On Monday 16 February 2009 12:56:25 am Gianni Doe wrote:
> I'm upgrading a system from 6.4 to 7.1 and rebuilding all the ports.
> I'd rather use packages where present to speed things up a bit so I'm
> using:
> # portupgrade -faP
>
> The problem is that it never
On 16/feb/09, at 10:47, Michel Talon wrote:
I think you can access that in the ruby program pkg_fetch
(/usr/local/sbin/pkg_fetch)
in function real_fetch_pkg, i have the following:
$pkg_site_uris.each do |uri_base|
PKG_SUFFIXES.each do |suffix|
uri = uri_base + (subdir + '/' + pkgname +
I think you can access that in the ruby program pkg_fetch
(/usr/local/sbin/pkg_fetch)
in function real_fetch_pkg, i have the following:
$pkg_site_uris.each do |uri_base|
PKG_SUFFIXES.each do |suffix|
uri = uri_base + (subdir + '/' + pkgname + suffix)
path = path_base + suffix
I'm upgrading a system from 6.4 to 7.1 and rebuilding all the ports.
I'd rather use packages where present to speed things up a bit so I'm
using:
# portupgrade -faP
The problem is that it never finds the packages as the URL is invalid,
there seems to be a missing s
Thanks for the help. I went ahead and installed portmaster and followed its
instructions for deleting all ports and then reinstalling.
1. portmaster -l > ~/installed-port-list
2. Update your ports tree
3. portmaster --clean-distfiles-all
4. portmaster -Faf
5. pkg_delete '*'
6. rm -rf /usr/local/l
,--- Doug Barton (Sun, 03 Aug 2008 22:14:54 -0700) *
| It's really not appropriate to hijack the portupgrade thread for this,
| so I'm starting a new subject. Also, please respect followups to
| -ports.
[ Being an inexperienced poster: sorry. Am I using a good cc: list now?
ts-all' and
> > 'src-all' numerous times (does src-all include ports-all? It takes forever)
> > along with portupgrade.
>
> src-all does not include ports-all.
>
> "It takes forever" is wonderfully vague. :-) Chances are the cvsup
> server you&
On Sun, 03 Aug 2008 22:14:54 -0700, Doug Barton wrote:
> It's really not appropriate to hijack the portupgrade thread for this,
> so I'm starting a new subject. Also, please respect followups to -ports.
>
> Alex Goncharov wrote:
>> Don't remember everything of t
Alex Goncharov wrote:
,--- You/Jeremy (Sun, 3 Aug 2008 19:26:18 -0700) *
| I'd start by ceasing use of portupgrade. Try Doug Barton's portmaster,
| which is in ports/ports-mgmt/portmaster. It's an extensive shell
| script, and does not require ruby.
Over the last couple
It's really not appropriate to hijack the portupgrade thread for this,
so I'm starting a new subject. Also, please respect followups to -ports.
Alex Goncharov wrote:
Don't remember everything of that sort but here are a couple of things
I would like to ask portmaster users'
,--- You/Jeremy (Sun, 3 Aug 2008 19:26:18 -0700) *
| I'd start by ceasing use of portupgrade. Try Doug Barton's portmaster,
| which is in ports/ports-mgmt/portmaster. It's an extensive shell
| script, and does not require ruby.
Over the last couple of months, I've mad
nclude ports-all? It takes forever)
> along with portupgrade.
src-all does not include ports-all.
"It takes forever" is wonderfully vague. :-) Chances are the cvsup
server you're using is slow (usually caused by heavy disk I/O, not so
much network I/O); pick another. Try them a
Hello,
I've recently updated to freeBSD 6.3-STABLE from 5.3-RELEASE (amd64) and am
struggling with out of date ports. I have tried updating 'ports-all' and
'src-all' numerous times (does src-all include ports-all? It takes forever)
along with portupgrade.
For example
Below is the hunk of ports that continually fail to upgrade due to problems
with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance with this greatly appreciated.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! lang/ruby18 (ruby-1.8.6.111_1,1) (patch
Steven Hartland wrote:
Would fix this particular package but again: how many others
do this? Maybe this is something that BSDPAN could / should
override?
It might be possible, you should talk to the BSDPAN maintainer.
Kris
___
freebsd-stable@freebsd
n. So I've
spent some time digging through the info I had here from the
upgrade, luckily I saved a list of installed ports before starting.
The issue appears to down to the fact ExtUtils::MakeMaker when
installed via CPAN installs to:
/usr/local/lib/perl5/5.8.8
So obviously when portupgrad
use a portupgrade to
rebuild and reinstall all the packages, I needed to uninstall a large
number of them. Basically, every time the port build fell over, I would
need to pkg_which the shared object mentioned in the error message,
uninstall that package and take note of the name then reinstall
On Sat, 2008-03-01 at 14:53 +0100, Kris Kennaway wrote:
> Steven Hartland wrote:
> > Seems portupgrade can easily break the perl install.
> >
> > How? Well there are various modules which can be updated
> > but are also part of the base perl and are hence required.
Steven Hartland wrote:
Seems portupgrade can easily break the perl install.
How? Well there are various modules which can be updated
but are also part of the base perl and are hence required.
A good example of this is ExtUtils::MakeMaker. If you
uninstall any version of this port your done for
Seems portupgrade can easily break the perl install.
How? Well there are various modules which can be updated
but are also part of the base perl and are hence required.
A good example of this is ExtUtils::MakeMaker. If you
uninstall any version of this port your done for, as
trying to build it
Hi,
I've got make problem, whether using portupgrade or cd /usr/ports/xx/xx
&& make.
#uname -a
FreeBSD lisa.bob.selfip.org 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #5:
Sun Nov 25 18:35:33 CET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LISA i386
As you can see below, when it enters o
Diane Bruce wrote:
On Mon, Oct 29, 2007 at 09:04:12PM +0100, Kris Kennaway wrote:
Diane Bruce wrote:
On Sun, Oct 28, 2007 at 11:38:26PM +0100, Kris Kennaway wrote:
...
What do you mean by obsolete libs? The portupgrade -fa should have
fixed precisely that ;)
Yes, I was going to suggest
1 - 100 of 307 matches
Mail list logo
