I've been using ports-mgmt/portupgrade pretty much ever since it
started to exist. Unfortunately portupgrade seems to be pretty much
"abandonware" so I've been told to move on to portmaster. Despite the
very long manpage I can't seem to be able to achieve the following
thing with portmaster:
$ por
On 08/06/2010 00:24, Sandra Kachelmann wrote:
> I've been using ports-mgmt/portupgrade pretty much ever since it
> started to exist. Unfortunately portupgrade seems to be pretty much
> "abandonware" so I've been told to move on to portmaster. Despite the
> very long manpage I can't seem to be able
On 08/06/2010 00:24, Sandra Kachelmann wrote:
> I've been using ports-mgmt/portupgrade pretty much ever since it
> started to exist. Unfortunately portupgrade seems to be pretty much
> "abandonware" so I've been told to move on to portmaster. Despite the
> very long manpage I can't seem to be able
On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton wrote:
> On 08/06/2010 00:24, Sandra Kachelmann wrote:
>> I've been using ports-mgmt/portupgrade pretty much ever since it
>> started to exist. Unfortunately portupgrade seems to be pretty much
>> "abandonware" so I've been told to move on to portmaster
"Sergey V. Dyatko" writes:
> A>> ===> libvpx-0.9.1 depends on file: /usr/local/bin/perl5.10.1 - found
> A>> sed:
> A>>
> /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
> A>> No such file or directory
> A>> *** Error code 1
> A>
> A>Can it be related to
On Fri, 06 Aug 2010 13:51:01 +0400
Anonymous wrote:
> "Sergey V. Dyatko" writes:
>
> > A>> ===> libvpx-0.9.1 depends on file: /usr/local/bin/perl5.10.1 -
> > A>> found sed:
> > A>>
> > /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
> > A>> No such fil
On 08/06/2010 04:58, Sandra Kachelmann wrote:
> On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton wrote:
>> On 08/06/2010 00:24, Sandra Kachelmann wrote:
>>> I've been using ports-mgmt/portupgrade pretty much ever since it
>>> started to exist. Unfortunately portupgrade seems to be pretty much
>>> "aba
Synopsis: Update port: devel/p5-ParseLex
Responsible-Changed-From-To: pirzyk->freebsd-ports
Responsible-Changed-By: pirzyk
Responsible-Changed-When: Fri Aug 6 12:00:34 UTC 2010
Responsible-Changed-Why:
Approve diff, please commit. Thanks
http://www.freebsd.org/cgi/query-pr.cgi?pr=149264
__
Hello Sandra
I was in a similar situation. I found the following paramters very usefull:
portmaster -a -d --no-confirm
-a: Take all installed ports
-d: Delete any dependicies
-no--confirm: Wait not after the check which ports are upgradable
With the above switch portmaster waits in two case:
1.
On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
wrote:
> Hello Sandra
>
> I was in a similar situation. I found the following paramters very usefull:
>
> portmaster -a -d --no-confirm
>
> -a: Take all installed ports
> -d: Delete any dependicies
> -no--confirm: Wait not after the check which port
On Fri, 6 Aug 2010 14:44:09 +0200
Sandra Kachelmann wrote:
> It would be extremely nice if there would be a --batch option that
> would act like portupgrade.
Does setting BATCH in the environment not work?
___
freebsd-ports@freebsd.org mailing list
ht
On Fri, Aug 06, 2010 at 01:52:40PM +0200, Martin Schweizer wrote:
> Hello Sandra
>
> I was in a similar situation. I found the following paramters very usefull:
>
> portmaster -a -d --no-confirm
>
> -a: Take all installed ports
> -d: Delete any dependicies
Errr... careful, there:
-d alw
> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann
> wrote:
> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
> > wrote:
> >> Hello Sandra
> >>
> >> I was in a similar situation. I found the following paramters very usefull:
> >>
> >> portmaster -a -d --no-confirm
> >>
> >> -a: Take all inst
On Fri, Aug 6, 2010 at 6:26 AM, Sandra Kachelmann
wrote:
>> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann
>> wrote:
>> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
>> > wrote:
>> >> Hello Sandra
>> >>
>> >> I was in a similar situation. I found the following paramters very
>> >> usef
On Fri, Aug 6, 2010 at 3:38 PM, Freddie Cash wrote:
> On Fri, Aug 6, 2010 at 6:26 AM, Sandra Kachelmann
> wrote:
>>> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann
>>> wrote:
>>> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
>>> > wrote:
>>> >> Hello Sandra
>>> >>
>>> >> I was in a sim
On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More wrote:
> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash wrote:
>>
>> If you absolutely do not want to see the OPTIONS screens, no matter
>> what, then add -G (see man page for details).
>
> No, that's not what -G does. -G makes portmaster handle the
On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann
wrote:
> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More wrote:
>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash wrote:
>>>
>>> If you absolutely do not want to see the OPTIONS screens, no matter
>>> what, then add -G (see man page for details).
>
Am 06.08.2010 15:59, schrieb Sandra Kachelmann:
> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More wrote:
>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash wrote:
>>>
>>> If you absolutely do not want to see the OPTIONS screens, no matter
>>> what, then add -G (see man page for details).
>>
>> No, t
On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash wrote:
>
> If you absolutely do not want to see the OPTIONS screens, no matter
> what, then add -G (see man page for details).
>
No, that's not what -G does. -G makes portmaster handle the options screen
similar to portupgrade eg waiting to ask you u
While updating ports some take a long time to compile and when it
finally comes time to install I need to type password again.
Is there an option to prevent that? Smth like running
$ sudo true
would be enough to update time stamp. They're per tty by default, anyway.
On Fri, Aug 6, 2010 at 4:09 PM, Sandra Kachelmann
wrote:
> On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann
> wrote:
>> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More
>> wrote:
>>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash wrote:
If you absolutely do not want to see the OPTIONS
On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann <
s.kachelm...@googlemail.com> wrote:
> Hmm...
>
> I just tried to update an outdated system with:
>
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.
>
On Fri, Aug 6, 2010 at 7:28 AM, Sandra Kachelmann
wrote:
> I just tried to update an outdated system with:
>
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.
What's the exact message? Is it asking abou
On Fri, Aug 6, 2010 at 4:31 PM, Freddie Cash wrote:
> On Fri, Aug 6, 2010 at 7:28 AM, Sandra Kachelmann
> wrote:
>> I just tried to update an outdated system with:
>>
>> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>>
>> after a while it asked me whether I want to delete pcre - so -m
>> BATCH=y
On Fri, Aug 6, 2010 at 4:30 PM, Adam Vande More wrote:
> On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann
> wrote:
>>
>> Hmm...
>>
>> I just tried to update an outdated system with:
>>
>> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>>
>> after a while it asked me whether I want to delete pcre
Synopsis: Update port: devel/p5-ParseLex
Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Changed-By: itetcu
Responsible-Changed-When: Fri Aug 6 14:43:52 UTC 2010
Responsible-Changed-Why:
Correct assignment (don't assign to the mailing list).
http://www.freebsd.org/cgi/
Anonymous writes:
> While updating ports some take a long time to compile and when it
> finally comes time to install I need to type password again.
> Is there an option to prevent that? Smth like running
> $ sudo true
How about using `timestamp_timeout` option in sudoers(5) ? OR maybe using
N
On Aug 6, 2010, at 9:28 AM, Sandra Kachelmann wrote:
> Hmm...
>
> I just tried to update an outdated system with:
>
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.
Somewhere along the thread you los
ash...@freebsd.org (Ashish SHUKLA) writes:
> Anonymous writes:
>> While updating ports some take a long time to compile and when it
>> finally comes time to install I need to type password again.
>> Is there an option to prevent that? Smth like running
>
>> $ sudo true
>
> How about using `time
On Fri, Aug 06, 2010 at 04:37:42PM +0200, Sandra Kachelmann wrote:
> On Fri, Aug 6, 2010 at 4:30 PM, Adam Vande More wrote:
> > On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann
> > wrote:
> >>
> >> Hmm...
> >>
> >> I just tried to update an outdated system with:
> >>
> >> $ portmaster --no-confi
Hi,
I just wanted to try games/connect4 but it segfaults here on FreeBSD
8.1-RELEASE and amd64.
It's a long backtrace so I think you should try it by yourself.
Kind regards.
--
Demelier David
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
Quoth David DEMELIER on Friday, 06 August 2010:
> Hi,
>
> I just wanted to try games/connect4 but it segfaults here on FreeBSD
> 8.1-RELEASE and amd64.
>
> It's a long backtrace so I think you should try it by yourself.
>
> Kind regards.
>
> --
> Demelier David
seg faults for me, too -- but w
Dear porters,
unfortunately I need to step down from all the FreeBSD
ports that I currently maintain, namely:
audio/ices0
audio/linux-shoutcast
audio/shoutcast
benchmarks/nbench
devel/libgee
games/avanor
games/crimson
games/wrogue
irc/minbif
misc/apparix
multimedia/gpodder
net-im/pino
net-mgmt/na
David DEMELIER writes:
> Hi,
>
> I just wanted to try games/connect4 but it segfaults here on FreeBSD
> 8.1-RELEASE and amd64.
>
> It's a long backtrace so I think you should try it by yourself.
Hmm, I have a very short one here, on gdb71 + gcc45.
Program received signal SIGSEGV, Segmentation
On Fri 06 Aug 2010 at 11:51:05 PDT Frank Steinborn wrote:
multimedia/gpodder
I can take this one.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsub
On 08/06/2010 04:52, Martin Schweizer wrote:
> Hello Sandra
>
> I was in a similar situation. I found the following paramters very usefull:
>
> portmaster -a -d --no-confirm
>
> -a: Take all installed ports
> -d: Delete any dependicies
That's not what -d means. You would be better off with the
On 08/06/2010 05:44, Sandra Kachelmann wrote:
> Thank you for your answer (and everyone else who replied). This is
> exactly the reason why I keep going back to portupgrade. Default
> OPTIONS almost always work for me - if not I go to the ports directory
> and run make config then let the --batch
On 08/06/2010 04:34, jhell wrote:
> Doug,
>
> One fallback that I cannot seem to get over is the creation of a backup
> package failed do you want to ignore [i] message prompt & the package
> messages that are displayed with $PAGER at the end of the upgrades. I
> do not recall the packages that
Are there any examples of how to use the USERS functionality together
with the SHAREOWN functionality in a port makefile? I'm working on
updating the ecartis port to use standard functionality for its user
ID, but can't seem to tell how to make sure that the USERS are created
before files are inst
On 08/06/2010 07:27, Anonymous wrote:
> While updating ports some take a long time to compile and when it
> finally comes time to install I need to type password again.
> Is there an option to prevent that? Smth like running
>
> $ sudo true
>
> would be enough to update time stamp. They're per
On Fri, Aug 6, 2010 at 5:26 PM, Doug Barton wrote:
> On 08/06/2010 04:34, jhell wrote:
>> Do not prompt for a backup package creation failure
>
> I need to add an option for this, but it will likely be an "expert"
> option that you can set in the rc file. The theory is that package
> creation fail
On 08/06/2010 14:33, Jim Trigg wrote:
> One example I have (unfortunately): I accidentally wiped out
> /usr/local/. Reinstalling all my ports was easy -- first reinstall
> portmaster and then run "portmaster -af". The problem was that for
> every single port I had to say "Yes, ignore the fact th
On Fri, Aug 6, 2010 at 4:26 PM, Doug Barton wrote:
> I need to add an option for this, but it will likely be an "expert"
> option that you can set in the rc file. The theory is that package
> creation failure should be a rare thing, and since portmaster has no way
> to know what packages are real
On Fri, Aug 06, 2010 at 05:28:50PM -0400, Jim Trigg thus spake:
Are there any examples of how to use the USERS functionality together
with the SHAREOWN functionality in a port makefile? I'm working on
updating the ecartis port to use standard functionality for its user
ID, but can't seem to tell
On 08/06/2010 15:03, Adam Vande More wrote:
> While your in the mood for for taking portmaster suggestions,
I am always in the mood for taking suggestions. :)
> I think an
> option to backup all currently installed packages would be useful.
for pkg in /var/db/pkg/* ; do
pkg_create -b $
On Fri, 2010-08-06 at 13:16:49 -0700, Charlie Kester wrote:
> On Fri 06 Aug 2010 at 11:51:05 PDT Frank Steinborn wrote:
> >
> >multimedia/gpodder
>
> I can take this one.
Done.
--
Sahil Tandon
___
freebsd-ports@freebsd.org mailing list
http://lists.
On 08/06/2010 14:03, Doug Barton wrote:
> On 08/06/2010 05:44, Sandra Kachelmann wrote:
>
>> Thank you for your answer (and everyone else who replied). This is
>> exactly the reason why I keep going back to portupgrade. Default
>> OPTIONS almost always work for me
In my haste to point out the ex
Doug Barton writes:
> On 08/06/2010 07:27, Anonymous wrote:
>> While updating ports some take a long time to compile and when it
>> finally comes time to install I need to type password again.
>> Is there an option to prevent that? Smth like running
>>
>> $ sudo true
>>
>> would be enough to
On 08/06/2010 15:54, Anonymous wrote:
> Doug Barton writes:
>
>> On 08/06/2010 07:27, Anonymous wrote:
>>> While updating ports some take a long time to compile and when it
>>> finally comes time to install I need to type password again.
>>> Is there an option to prevent that? Smth like running
>
About two months ago I submitted a PR for a new port
(http://www.freebsd.org/cgi/query-pr.cgi?pr=147768)
>From the tracking page it looks like it got bounced around a little and
then didn't go anywhere. It's a game, so I understand it being a low
priority, but I'm wondering if there is anything I
On Fri, Aug 6, 2010 at 6:58 PM, Doug Barton wrote:
> On 08/06/2010 15:54, Anonymous wrote:
>> Doug Barton writes:
>>> While I can sympathize with your situation, I think you'd be better off
>>> in this case running your portmaster commands in an actual root shell.
>>
>> Wouldn't periodic hook be
On Fri, Aug 6, 2010 at 5:41 PM, Doug Barton wrote:
> On 08/06/2010 15:03, Adam Vande More wrote:
>
>> While your in the mood for for taking portmaster suggestions,
>
> I am always in the mood for taking suggestions. :)
>
On that note, I suggest that portmaster should fallback on PKG_PATH,
which i
On 08/06/2010 16:01, Andres Perera wrote:
> On Fri, Aug 6, 2010 at 5:41 PM, Doug Barton wrote:
>> On 08/06/2010 15:03, Adam Vande More wrote:
>>
>>> While your in the mood for for taking portmaster suggestions,
>>
>> I am always in the mood for taking suggestions. :)
>>
>
> On that note, I sugges
Doug Barton wrote:
> On 08/06/2010 15:03, Adam Vande More wrote:
>
> > While your in the mood for for taking portmaster suggestions,
>
> I am always in the mood for taking suggestions. :)
>
> > I think an
> > option to backup all currently installed packages would be useful.
>
> for pkg in /
On Fri, Aug 6, 2010 at 5:11 PM, Doug Barton wrote:
> On 08/06/2010 15:03, Adam Vande More wrote:
>
> for pkg in /var/db/pkg/* ; do
>pkg_create -b $pkg
> done
>
Yes, that is basically what I'm talking about, my script is a little fancier
now, prompts for directory with a default if you ju
OK, I'm trying to set up tinderbox to validate the port I maintain and
another that I'm attempting to put together (well, technically to
update since the maintainer has not responded to my inquiry). How do
I set up ports trees for individual ports and their dependencies? The
README only shows how
On 08/06/2010 17:26, Doug Barton wrote:
>> and force creation of whatever you have on the system already?
> Not sure what this means, can you explain it in more detail?
No matter what the state of a package is I feel deeply that when making
a backup package, that should not fail because of a missi
On 08/06/2010 18:03, Adam Vande More wrote:
> On Fri, Aug 6, 2010 at 4:26 PM, Doug Barton wrote:
>
>> I need to add an option for this, but it will likely be an "expert"
>> option that you can set in the rc file. The theory is that package
>> creation failure should be a rare thing, and since por
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 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 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
64 matches
Mail list logo
