Hello,
I've closed this bug now with an upload that neuters the
dailystrips-update program temporarily with a view to removing it entirely
(this provides a migration period for people to remove it without getting
cron errors or the such immediately).
I've also strengthened the warning in the dailystrips-update man page
and the README, although please note that the man page in particular has
been warning against its use since 2007.
Still, I don't disagree with most of what you say (I won't unilaterally
remove a local defs file in case it has value), so I hope you agree this is
sufficient.
Please let me know if you have any other concerns, and thank you for
your contribution to Debian.
Rene
On Thu, Oct 29, 2009 at 11:00:56PM -0400, Ariel wrote:
> You should either disable the dailystrips-update program, or point it to a
> fresher defs file.
>
> If someone runs it, it should simply exit with a message, and it should
> delete the local defs file.
>
> I've been running it for probably a year without realizing it made things
> much worse.
>
> Upstream is dead. There is no reason to keep around this program.
>
> Either disable it, or host a defs file for people.
>
> If you don't have a source control location, then:
> http://code.google.com/projecthosting/
> is a good place to host the defs file.
>
> -Ariel
>
> -- System Information:
> Debian Release: 5.0.3
> APT prefers stable
> APT policy: (990, 'stable')
> Architecture: i386 (x86_64)
>
> Kernel: Linux 2.6.30 (SMP w/8 CPU cores)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/bash
>
> Versions of packages dailystrips depends on:
> ii debconf [debconf-2.0] 1.5.24 Debian configuration management
> sy
> ii libtimedate-perl 1.1600-9 Time and date functions for Perl
> ii libwww-perl 5.813-1 WWW client/server library for
> Perl
> ii perl 5.10.0-19lenny2 Larry Wall's Practical
> Extraction
>
> dailystrips recommends no packages.
>
> dailystrips suggests no packages.
>
> -- debconf information excluded
>
>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
