Hi List,
As a normal user who has read the emails, but not taken part in the
discussion due to lack of time for commitments, I would like to comment.
2010-07-19 18:54, Giovanni Mascellani skrev:
Yes, that's my interpretation too. But I think that, in order to have
good communication with upstream, we'll have to show that the package
can be maintained and won't fall forgotten as last time.
As I read the reaction from upstream, they were frustrated that people
installed the package with the expectation that it should be current and
just work.
As Tim stated, I think the problem was that it entered into a repository
where people expect such things, and that this happened when it was
released as part of a stable ubuntu release. That is, the problem was
not primarily debian-related.
The response and proposals from upstream also seem to argue about ubuntu
rather than debian.
IMHO and AFAIUI:
For stable debian, people probably do not expect packages to be up-to-date.
For unstable debian, people probably do not expect packages to be bug-free.
For experimental debian, people probably do not install packages without
knowing what they are doing, and without expecting them to work without
problems.
It was also stated (by Tim?) that due to a process involving the
NEW-queue (I think), removing the package from debian and then
reintroducing it again could be much more work than moving to
experimental and working from there.
I would appreciate getting an up-to-date sage-package in debian again,
so I hope you find time and interest enough to continue the work.
Regards
Johan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
