Hey,
why is audio/akode marked as BROKEN: Unfetchable?
It IS fetchable, e.g. here:
http://www.kde-apps.org/CONTENT/content-files/30375-akode-2.0.2.tar.bz2
Or here:
http://pkgs.fedoraproject.org/repo/pkgs/akode/30375-akode-2.0.2.tar.bz2/659ced0c9c735cb3e55b9138ff02342c/30375-akode-2.0.2.tar
On 7/10/2011 6:32 AM, Heino Tiedemann wrote:
Hey,
why is audio/akode marked as BROKEN: Unfetchable?
Hello,
See ports/155297. (http://www.freebsd.org/cgi/query-pr.cgi?pr=155297)
Regards,
Frank Laszlo
___
freebsd-ports@freebsd.org mailing list
htt
On 10 Jul 2011 13:21, "Frank J. Laszlo" wrote:
>
> On 7/10/2011 6:32 AM, Heino Tiedemann wrote:
>>
>> Hey,
>>
>>
>> why is audio/akode marked as BROKEN: Unfetchable?
>>
>
> Hello,
>
> See ports/155297. (http://www.freebsd.org/cgi/query-pr.cgi?pr=155297)
>
> Regards,
>
> Frank Laszlo
>
>
Is there
On Sun, Jul 10, 2011 at 12:32:13PM +0200, Heino Tiedemann wrote:
> Hey,
>
>
> why is audio/akode marked as BROKEN: Unfetchable?
>
>
> It IS fetchable, e.g. here:
>
>
> http://www.kde-apps.org/CONTENT/content-files/30375-akode-2.0.2.tar.bz2
>
>
> Or here:
>
> http://pkgs.fedoraproject.org/r
On Sun, Jul 10, 2011 at 8:21 AM, Chris Rees wrote:
> On 10 Jul 2011 13:21, "Frank J. Laszlo" wrote:
>>
>> On 7/10/2011 6:32 AM, Heino Tiedemann wrote:
>>>
>>> Hey,
>>>
>>>
>>> why is audio/akode marked as BROKEN: Unfetchable?
>>>
>>
>> Hello,
>>
>> See ports/155297. (http://www.freebsd.org/cgi/qu
On 10 Jul 2011 15:34, "Scot Hetzel" wrote:
>
> On Sun, Jul 10, 2011 at 8:21 AM, Chris Rees wrote:
> > On 10 Jul 2011 13:21, "Frank J. Laszlo" wrote:
> >>
> >> On 7/10/2011 6:32 AM, Heino Tiedemann wrote:
> >>>
> >>> Hey,
> >>>
> >>>
> >>> why is audio/akode marked as BROKEN: Unfetchable?
> >>>
>
On 10 Jul 2011 07:37, "Ruslan Mahmatkhanov" wrote:
>
> 10.07.2011 03:52, lini...@freebsd.org пишет:
>>
>> Synopsis: [UPDATE] dns/py-dns: update to 2.3.5
>>
>> State-Changed-From-To: open->closed
>> State-Changed-By: linimon
>> State-Changed-When: Sat Jul 9 23:51:15 UTC 2011
>> State-Changed-Why:
>
10.07.2011 19:56, Chris Rees пишет:
On 10 Jul 2011 07:37, "Ruslan Mahmatkhanov" wrote:
10.07.2011 03:52, lini...@freebsd.org пишет:
Synopsis: [UPDATE] dns/py-dns: update to 2.3.5
State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sat Jul 9 23:51:15 UTC 2011
St
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: hs-wai-0.4.0: no entry for /usr/ports
make_index: hs-wai-0.4.0: no entry for /usr/ports
make_index: hs-hoogle-4.2.5: no entry for /usr/ports
make_index: hs-hoogle-4.2.5: no entry for /usr/ports
make_index: hs-warp-
It seems that after the commit of math/hs-Agda + math/hs-Agda-executable +
www/hs-wai + www/hs-warp, INDEX-8 doesn't get updated.
The last one updated is sysutils/fusefs-ntfs
$ cd /usr/ports
$ grep PORTVERSION www/hs-wai/Makefile
PORTVERSION=0.4.0
$ grep ^hs-wai INDEX-8 | cut -d "|" -f 1
hs
On 10 July 2011 22:29, Barbara wrote:
>
> It seems that after the commit of math/hs-Agda + math/hs-Agda-executable +
> www/hs-wai + www/hs-warp, INDEX-8 doesn't get updated.
> The last one updated is sysutils/fusefs-ntfs
>
> $ cd /usr/ports
> $ grep PORTVERSION www/hs-wai/Makefile
> PORTVERSION=
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: hs-wai-0.4.0: no entry for /usr/ports
make_index: hs-wai-0.4.0: no entry for /usr/ports
make_index: hs-hoogle-4.2.5: no entry for /usr/ports
make_index: hs-hoogle-4.2.5: no entry for /usr/ports
make_index: hs-warp-
Barbara writes:
> It seems that after the commit of math/hs-Agda + math/hs-Agda-executable +
> www/hs-wai + www/hs-warp, INDEX-8 doesn't get updated.
> The last one updated is sysutils/fusefs-ntfs
> $ cd /usr/ports
> $ grep PORTVERSION www/hs-wai/Makefile
> PORTVERSION= 0.4.0
> $ grep ^hs-wai
Erwin Lansing writes:
> INDEX build failed with errors:
> Generating INDEX-7 - please wait.. Done.
> make_index: hs-wai-0.4.0: no entry for /usr/ports
> make_index: hs-wai-0.4.0: no entry for /usr/ports
> make_index: hs-hoogle-4.2.5: no entry for /usr/ports
> make_index: hs-hoogle-4.2.5: no entry f
On 2011-Jul-07 23:13:08 +0400, Max Brazhnikov wrote:
>Until ports are not broken or/and forbidden I see no reason for deprecation
>and removing them.
>However you may consider this step as a recommendation to migrate from
>Qt3/KDE3 ports to anything else.
I would suggest that deprecation (witho
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Mon, Jul 11, 2011 at 08:51:02AM +1000, Peter Jeremy wrote:
> It would be useful if there was a mechanism to warn users
> that the port they are about to install (or have installed) is no
> longer recommended.
IMHO using DEPRECATED without EXPIRATION_DATE is just fine for this.
mcl
17 matches
Mail list logo