On Monday 04 January 2010 07:19:34 Doug Barton wrote:
> First, if you could start a new thread for each problem that would
> help me keep track of them.
of course! sorry, i'm used to have everything in only one big box :)
> Second, if you could write a brief
> explanation of what you see as the p
Alberto,
I genuinely appreciate your testing and use of portmaster, so please
don't get the wrong idea about my response. But it would be very
helpful to me if you could do a couple of things for bug reports.
First, if you could start a new thread for each problem that would
help me keep track of
hello! new problem here: http://pastebin.ca/1736942 (it happens with
portmaster -a too)
`--> cat /usr/local/etc/portmaster.rc
ALWAYS_SCRUB_DISTFILES=dopt
LOCAL_PACKAGEDIR=/usr/ports/packages
MAKE_PACKAGE=gopt
PM_DEL_BUILD_ONLY=pm_dbo
PM_PACKAGES_BUILD=pmp_build
`--> ls /usr/ports/packages/*/boos
Miroslav Lachman wrote:
> It is not working - pkg_add on 6.3 has no option for "Install the
> package without fetching and installing dependencies". I mean, there is
> no long nor short option for this, so this portmaster's functionality
> cannot be easily ported to 6.3. That's why I suggest to dis
Doug Barton wrote:
Miroslav Lachman wrote:
I don't know if it is well known / documented somewhere in portmaster,
but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long
options
This is why all of the ports tools should be in the ports tree. :)
I just added the fix to the svn
Miroslav Lachman wrote:
> I don't know if it is well known / documented somewhere in portmaster,
> but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long
> options
This is why all of the ports tools should be in the ports tree. :)
I just added the fix to the svn version of portma
Doug Barton wrote:
Howdy!
I'm very excited to announce that what I hope to be the final version
of the new portmaster with package support is now available for
testing. I've done quite a bit of regression testing myself, but the
last time I posted about the beta version several people were kind
Alberto Villa wrote:
> On Saturday 12 December 2009 05:55:09 Alberto Villa wrote:
>> good... thanks for listening to me! i could have some question/suggestion
>> about --packages-build and --delete-build-only in the future, but i need
>> some real usage to test it, now...
>
> hello again :)
>
>
On Saturday 12 December 2009 05:55:09 Alberto Villa wrote:
> good... thanks for listening to me! i could have some question/suggestion
> about --packages-build and --delete-build-only in the future, but i need
> some real usage to test it, now...
hello again :)
here's my question/suggestion: i i
On Saturday 12 December 2009 03:10:34 Doug Barton wrote:
> Yes, the error message you posted is exactly what's supposed to
> happen. "There is nothing at $PACKAGESITE" is a whole different
> category of problems than "the latest version of the package is not
> available at $PACKAGESITE." In the lat
Alberto Villa wrote:
> On Friday 11 December 2009 20:22:26 Doug Barton wrote:
>> First, I'm assuming that you are using version 2.14 from ports. That's
>> the latest version at the moment.
>
> i was using the latest revision, which seems to be the same as 2.14.
> upgraded to 2.14, now
>
>> Next
On Saturday 12 December 2009 02:09:52 Alberto Villa wrote:
> could it be because my PACKAGESITE is actually an empty directory?
ok, i see that i should use the default (8-current), but the program shouldn't
fail anyway
--
Alberto Villa
http://wiki.FreeBSD.org/AlbertoVilla
I don't do it for the
On Friday 11 December 2009 20:22:26 Doug Barton wrote:
> First, I'm assuming that you are using version 2.14 from ports. That's
> the latest version at the moment.
i was using the latest revision, which seems to be the same as 2.14.
upgraded to 2.14, now
> Next, I tried the exact same command l
Alberto Villa wrote:
> On Friday 11 December 2009 15:12:58 Alberto Villa wrote:
>> On Thursday 10 December 2009 21:08:41 Doug Barton wrote:
>>> The fix for this is in the svn tree now, please give it a try. I have
>>> fixed a few bugs since 2.13 was committed, so I'll be pushing the svn
>>> code in
On Friday 11 December 2009 15:12:58 Alberto Villa wrote:
> On Thursday 10 December 2009 21:08:41 Doug Barton wrote:
> > The fix for this is in the svn tree now, please give it a try. I have
> > fixed a few bugs since 2.13 was committed, so I'll be pushing the svn
> > code into cvs very soon.
>
> t
On Friday 11 December 2009 15:12:58 Alberto Villa wrote:
> by the way, will it always abort when the option --packages-build won't
> find a package?
the same happens with -P
--
Alberto Villa
http://wiki.FreeBSD.org/AlbertoVilla
You are fairminded, just and loving.
_
On Thursday 10 December 2009 21:08:41 Doug Barton wrote:
> The fix for this is in the svn tree now, please give it a try. I have
> fixed a few bugs since 2.13 was committed, so I'll be pushing the svn
> code into cvs very soon.
thanks! i'm testing it right now
by the way, will it always abort whe
Alberto Villa wrote:
> On Thursday 10 December 2009 01:53:01 Alberto Villa wrote:
>>> --delete-build-only
>>> For packages/ports that are ONLY listed as build dependencies for the
>>> ports being updated in this run, delete them when the run is over.
>> it's still building, then i don't know if
On Thursday 10 December 2009 01:53:01 Alberto Villa wrote:
> > --delete-build-only
> > For packages/ports that are ONLY listed as build dependencies for the
> > ports being updated in this run, delete them when the run is over.
>
> it's still building, then i don't know if the second case abov
On Tuesday 01 December 2009 23:44:44 Doug Barton wrote:
> --packages-build
> For packages that are ONLY listed as build dependencies for the ports
> being updated in this run, download packages if available.
i'm not completely sure i've understood how this works. please, put some
light on t
On Sunday 06 December 2009 06:40:22 Doug Barton wrote:
> Dima Panov wrote:
> > Doug, haw about missed feature (portupgrade had this earlier)?
> > If -r (recursive) flag present, after upgrade package repack all depended
> > on him.
>
> I thought more about this and realized that I'm not 100% sure
On Sat, Dec 5, 2009 at 9:29 PM, Doug Barton wrote:
> If you see any more problems that require --check-depends to fix them
> please let me know as that would indicate a bug at this point.
>
My first round of testing showed that your fix worked. Nice work, Doug!
--
chs
_
Christer Solskogen wrote:
> Err... Delete that. setenv PACKAGESITE /usr/ports/packages is the
> correct one. IMHO PACKAGESITE should be set to that by default.
In r200168 I just added the --local-packagedir option so that you can
properly specify this. You can use 'portmaster
--local-packagedir=/u
Dima Panov wrote:
> Doug, haw about missed feature (portupgrade had this earlier)?
> If -r (recursive) flag present, after upgrade package repack all depended on
> him.
I thought more about this and realized that I'm not 100% sure what
you're asking for. :)
If you use -g along with -r now, all
Christer Solskogen wrote:
> On Fri, 04 Dec 2009 07:53:52 +0100, Christer Solskogen wrote:
>
>
>> Err... Delete that. setenv PACKAGESITE /usr/ports/packages is the
>> correct one. IMHO PACKAGESITE should be set to that by default.
>
> I also see that I need to run 'portmaster --check-depends' man
On Fri, 04 Dec 2009 07:53:52 +0100, Christer Solskogen wrote:
> Err... Delete that. setenv PACKAGESITE /usr/ports/packages is the
> correct one. IMHO PACKAGESITE should be set to that by default.
I also see that I need to run 'portmaster --check-depends' manually after
doing a 'portmaster -a -P
On Fri, Dec 4, 2009 at 6:36 AM, Doug Barton wrote:
> Christer Solskogen wrote:
>> Setting PACKAGESITE to /usr/ports/packages/All also seem to remedy the
>> problem.
>
> Ok, good. That's actually a pleasant side effect of some code I added
> recently, but this is why I ask for beta/RC testing, y'a
Christer Solskogen wrote:
> On Thu, Dec 3, 2009 at 10:29 PM, Doug Barton wrote:
>
>> Nope. I need to know more about what you're doing when you see those
>> error messages.
>>
>
> Well, there are not that much more I can tell you ;-)
> web# pkg_version -IL=
> web#
> web# portmaster -a -PP
> /usr
On Thu, Dec 3, 2009 at 10:29 PM, Doug Barton wrote:
> Nope. I need to know more about what you're doing when you see those
> error messages.
>
Well, there are not that much more I can tell you ;-)
web# pkg_version -IL=
web#
web# portmaster -a -PP
/usr/local/sbin/portmaster: cannot create : No su
Christer Solskogen wrote:
> Doug Barton wrote:
>
>> You can find the information on accessing the svn version at
>> http://dougbarton.us/portmaster-proposal.html
>>
>> A more-or-less complete list of the new features:
>>
>> - -P|--packages, -PP|--packages-only
>> Basically like the portupgrade
Freddie Cash wrote:
> On Wed, Dec 2, 2009 at 8:31 AM, Doug Barton wrote:
>
>> Dima Panov wrote:
>>> Doug, haw about missed feature (portupgrade had this earlier)?
>>> If -r (recursive) flag present, after upgrade package repack all depended
>> on him.
>>> This feature very useful when packqage re
Doug Barton wrote:
You can find the information on accessing the svn version at
http://dougbarton.us/portmaster-proposal.html
A more-or-less complete list of the new features:
- -P|--packages, -PP|--packages-only
Basically like the portupgrade features to try downloading a package
firs
On Wed, Dec 2, 2009 at 8:31 AM, Doug Barton wrote:
> Dima Panov wrote:
> > Doug, haw about missed feature (portupgrade had this earlier)?
> > If -r (recursive) flag present, after upgrade package repack all depended
> on him.
> >
> > This feature very useful when packqage repository used to deplo
Dima Panov wrote:
> Doug, haw about missed feature (portupgrade had this earlier)?
> If -r (recursive) flag present, after upgrade package repack all depended on
> him.
>
> This feature very useful when packqage repository used to deploy packages on
> another
> machines
I'll take a look at th
On Wednesday 02 December 2009 08:44:44 Doug Barton wrote:
> Howdy!
>
> I'm very excited to announce that what I hope to be the final version
> of the new portmaster with package support is now available for
> testing. I've done quite a bit of regression testing myself, but the
> last time I posted
35 matches
Mail list logo
