On Sat, Oct 08, 2011 at 04:50:35PM BST, Stefano Zacchiroli wrote:
> To nitpick a bit, your third possibility mentioned that the fix is "not
> worth", but there are at least two sub-cases there: (1) maintainer does
> not want to spend *their own time* preparing the fix, but would gladly
> accept patches from others and (2) the maintainer does not want the fix
> to reach user machines (e.g. because they consider the fix might make
> things worse).
The fix is trivial and it won't make things worse.
Now probably not worth it but what could have been done in version 5-1:
if [ -f /etc/cron.d/git-repack-repositories ]
then
sed -i 's/bin\/git-repack-repositories/bin\/git-repack-repositories-cron/g'
\
/etc/cron.d/git-repack-repositories
fi
> Given Raf's interest in getting this particular issue fixed, I wonder
> whether he has tried proposing a patch to the maintainer (there is no
> trace of it in the buglog mentioned in this thread). Going that way can
> be way more useful in actually improving the life of users affected by
> the issue than this intriguing discussion about who *in theory* is
> responsible of cleaning up old debris.
No I hadn't as I've mentioned before, the fix is trivial and would have
taken me longer to do that than the maintainer, who already knows his
package and is dealing with debian packages on a daily basis, I on the
other hand hadn't created any packages in years.
> Share the code, we'll all be happier.
:^)
--
Raf
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111011191058.GA20160@thor.local
