Gary Dale wrote:
...
I appreciate the people doing this, but this is a serious issue. I have
to resort to firing up a VM or resorting to the command line on my local
server to update my web sites because I can't do it from Testing. I see
it also impacts other programs that I (fortunately) don't use as much.
i know it is frustrating to hit something like this when you
are trying to just get a website updated. all i can say is that
if you are running testing you are taking this sort of happening
as a risk and if you do not want that risk then you should step
back to stable instead. especially if you are doing this for
something that might be time critical or a production issue.
i keep a stable partition for this reason and while i rarely
have needed it in the past this year i've had to use it twice.
once for the FileZilla issue as you are facing and another for
a program which hasn't been converted to python3 yet (and for
all i know it may not ever be).
When faced with a major bug, shouldn't there be a procedure to pull back
the testing version - like restoring the previous version with a
bumped-up version number while working on the known buggy version in
experimental (no need to punish people using SID)?
it didn't affect enough people for it to be noticed before
the affected packages went from sid to testing. that's the
problem when you get particular older packages that only a
few people use once in a while. it would have been nice to
have caught it in sid before testing, but, well...