lini...@freebsd.org wrote:
portname: net-mgmt/portmon
deprecated because: No more public distfiles
I was able to fetch it earlier today:
$ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive )
=== Fetching all distfiles for portmon-2.0 and dependencies
=== Vulnerability check
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
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
On 24 August 2011 14:47, Mikhail T. mi+t...@aldan.algebra.com wrote:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It looks
like it's still available elsewhere but I can't find a replacement
Am 24.08.2011 15:47, schrieb Mikhail T.:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It
looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one
On 25.08.2011 08:48, Chris Rees wrote:
On 24 August 2011 14:47, Mikhail T.mi+t...@aldan.algebra.com wrote:
Can it be unbroken by using the Internet archive?
...
If so, quite a few other victims of this latest purging can be given a new
life.
Matthias recently made reference on this
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is
On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote:
On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote:
portname: cad/tkgate
description:A Tcl/Tk based digital circuit editor and simulator
maintainer: po...@freebsd.org
deprecated because: No more
On 23 August 2011 07:45, Chris Rees utis...@gmail.com wrote:
On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote:
On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote:
portname: cad/tkgate
description: A Tcl/Tk based digital circuit editor and simulator
On 2011-Aug-23 07:45:04 +0100, Chris Rees utis...@gmail.com wrote:
On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote:
On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote:
portname: cad/tkgate
I have no problem fetching this port from the mastersite.
I'll take a look.
On 22 August 2011 03:24, Mikhail T. mi+t...@aldan.algebra.com wrote:
On -10.01.-28163 14:59, lini...@freebsd.org wrote:
portname: audio/adpcm
description: An Intel/DVI IMA ADPCM codec library
maintainer:po...@freebsd.org
deprecated because: No more public distfiles
On 22.08.2011 04:46, Chris Rees wrote:
On 22 August 2011 03:24, Mikhail T.mi+t...@aldan.algebra.com wrote:
On -10.01.-28163 14:59, lini...@freebsd.org wrote:
portname: audio/adpcm
description:An Intel/DVI IMA ADPCM codec library
maintainer:po...@freebsd.org
deprecated
On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote:
portname: cad/tkgate
description:A Tcl/Tk based digital circuit editor and simulator
maintainer: po...@freebsd.org
deprecated because: No more public distfiles
expiration date:2011-09-01
build errors:
I notice in the list the port math/pari which is not some obscure
abandonware, but one of the most proeminent free computer algebra software.
So i look at the pari web page and then:
niobe% fetch
http://pari.math.u-bordeaux.fr/pub/pari/unix/pari-2.5.0.tar.gz
pari-2.5.0.tar.gz
On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote:
I notice in the list the port math/pari which is not some obscure
abandonware, but one of the most proeminent free computer algebra software.
So i look at the pari web page and then:
niobe% fetch
Hi!
On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote:
I notice in the list the port math/pari which is not some obscure
abandonware, but one of the most proeminent free computer algebra software.
[...]
In other words everything works completely out of the box, without any
On 21 August 2011 15:34, Kurt Jaeger li...@opsec.eu wrote:
Hi!
On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote:
I notice in the list the port math/pari which is not some obscure
abandonware, but one of the most proeminent free computer algebra software.
[...]
In other
Kurt Jaeger wrote:
Looks like the outdated version we have in ports isn't kept there any
more. Would you like to be the port's new maintainer?
I'll have a look at it.
I have played a little with the FreeBSD port for pari:
One needs to modify very little the Makefile:
CONFIGURE_ARGS=
On -10.01.-28163 14:59, lini...@freebsd.org wrote:
portname: audio/adpcm
description:An Intel/DVI IMA ADPCM codec library
maintainer:po...@freebsd.org
deprecated because: No more public distfiles
expiration date:2011-09-01
build errors: none.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Hi!
07.02.2010 10:30, lini...@freebsd.org пишет:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.
Can please
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
01/-10/37 14:59, lini...@freebsd.org wrote:
portname: devel/adabindx
description:An Ada-binding to the X Window System and *tif
maintainer:po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:
It looks like a noticeable share of the ports listed have one thing in common
-- they depend on Ada.
Various gnat-ports would not even build on anything but i386...
Is Ada-support really in such a bad shape by the GNU-project, or is it just a
FreeBSD problem?
'Lo.
Current situtation
Subject: Re: The state of Ada (Re: FreeBSD unmaintained ports which are
currently scheduled for deletion)
It looks like a noticeable share of the ports listed have one thing in common
-- they depend on Ada.
Various gnat-ports would not even build on anything but i386...
Is Ada-support
On Fri, 8 Jan 2010, John Merryweather Cooper wrote:
Well, the compiler needs to be upgraded to the latest version. Linux
gets a compiler out of the box, but we have to bend one to shape.
Most things stay the same, but there are always subtle differences.
I'd be happy to help do this (as I'm
On Fri, Jan 08, 2010 at 06:56:38PM +, freebsd-po...@coreland.ath.cx wrote:
I created the lang/gnat-gcc44 port a couple of months ago and have
worked to ensure that it works on 7/8 i386/x86_64. Unfortunately, there
won't be support for other platforms until somebody else decides to do
the
unmaintained ports which are
currently scheduled for deletion)
On Fri, 8 Jan 2010, John Merryweather Cooper wrote:
Well, the compiler needs to be upgraded to the latest version. Linux gets a
compiler out of the box, but we have to bend one to shape. Most things stay
the same, but there are always
01/08/10 14:59, Daniel Eischen написав(ла):
All the ports that I saw that were broken, were broken
*because* the compiler (lang/gnat) was updated. Those
ports seemed to be vastly out of date and didn't build
with the latest GPL gnat from ACT.
Well, I tried to fix one, but my system is amd64,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
101 - 171 of 171 matches
Mail list logo
