Torfinn Ingolfsen wrote:
Hello again,
Just a reminder: portupgrade 2.4.6 hasn't been fixed yet - it is still broken:
Yes, I remember, thanks. I'm very busy this year. I'd glad to give
maintainership to somebody else. Write me, if you like.
--
Dixi.
Sem.
Hello,
On Thu, Apr 9, 2009 at 6:37 PM, Parv p...@pair.com wrote:
Does this Perl (5.8 onwards) program ...
http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00
... produces anything when run *without any arguments*?
FWIW, I tried it on two machines, no it does not produce any
in message b79ecaef0904091219t4f20f65br36f6e2405ff60...@mail.gmail.com,
wrote Chris Rees thusly...
2009/4/9 Parv p...@pair.com:
in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com,
wrote Chris Rees thusly...
I recall from
Hi,
On Fri, Apr 10, 2009 at 2:57 PM, p...@pair.com wrote:
What was the last working version? It would be simpler for this
Ruby simpleton to generate a patch than to debug through the
stack trace.
FWIW, my current workaround for thi problem is to portdowngrade to the
latest portupgrade 2.4.3
Torfinn Ingolfsen writes:
What was the last working version? It would be simpler for this
Ruby simpleton to generate a patch than to debug through the
stack trace.
FWIW, my current workaround for thi problem is to portdowngrade to the
latest portupgrade 2.4.3
in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com,
wrote Chris Rees thusly...
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break
when a port is recursively (-R)
On Thursday 09 April 2009 09:37:49 am Parv wrote:
in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com,
wrote Chris Rees thusly...
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing
2009/4/9 Parv p...@pair.com:
in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com,
wrote Chris Rees thusly...
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break
when a
Chris Rees wrote:
Dear all on freebsd-ports@,
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break
when a port is recursively (-R) upgraded; it's surfacing for me too :(
Assuming you are
Dear all on freebsd-ports@,
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break
when a port is recursively (-R) upgraded; it's surfacing for me too :(
Hello,
On Wed, Apr 8, 2009 at 2:51 PM, Chris Rees utis...@googlemail.com wrote:
Is the bug still there, or is my pkgdb hosed? If so, how do I fix it?
IMO, the bug is still in portupgrade, even in the latest 2.4.6
version. I have also seen it very recently.
--
Regards,
Torfinn Ingolfsen
On Wed, 8 Apr 2009 13:51:48 +0100
Chris Rees utis...@googlemail.com wrote:
Dear all on freebsd-ports@,
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break
when a port is recursively (-R)
On Wednesday 08 April 2009 05:51:48 am Chris Rees wrote:
Dear all on freebsd-ports@,
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break when a
port is recursively (-R) upgraded; it's
2009/4/8 Kent Stewart kstew...@owt.com:
On Wednesday 08 April 2009 05:51:48 am Chris Rees wrote:
Dear all on freebsd-ports@,
I recall from
http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
that there was a bug in portupgrade last year, causing it to break when a
port
Hello again,
On Wed, Apr 8, 2009 at 4:17 PM, Torfinn Ingolfsen tin...@gmail.com wrote:
IMO, the bug is still in portupgrade, even in the latest 2.4.6
version. I have also seen it very recently.
Yep, still there with latest portupgrade:
r...@kg-v2# portupgrade -R ImageMagick diablo-jdk ffmpeg
I've wrote many time to the maintainer about the problem, I think since about 2
years ago, and I've also received some answer from him about other issues. But
he never answered about that problem.
regards
Barbara
___
freebsd-ports@freebsd.org
16 matches
Mail list logo