Re: Bug#539749: Time for a new maintainer for Auctex?
>>>>> fant == Frank Küster [2009-8-21]
fant> "Davide G. M. Salvetti" <salve@debian.org> wrote:
fant> But I also think that your style of working is not encouraging for
fant> collaborators. You actually *do* accept patches, sometimes as-is,
fant> sometimes you take them as inspiration, but solve the issue your
fant> way. That's okay. But you do not talk to the patch submitters,
fant> you often don't tell them whether you think it's the right
fant> approach, whether you'll fix the bug soon, or whether you plan an
fant> upload at all.
[...]
Dear Frank,
I understand that you have good points, so I'll do what you asked, at
least this time, and hopefully for the future as well.
I plan to upload auctex 11.83-8 today or tomorrow, as time permits; here
is my latest changelog.Debian:
--8<---------------cut here---------------start------------->8---
auctex (11.83-8) unstable; urgency=medium
* COPYRIGHT, copyright.in, variables: Update copyright.
* control (Homepage): New field.
* control (Standards-Version): Updated to 3.8.2.
* control (auctex/Description): Reflow text.
* control (preview-latex-style/Description): Fix typo (unpublished
change obsoleted by 11.83-7.1 NMU); thanks to Rafael Laboissiere.
(Closes: #440397)
* control (preview-latex-style/Homepage): New field.
* po/cs.po, po/de.po, po/es.po, po/eu.po, po/fi.po, po/fr.po, po/gl.po,
po/it.po, po/ja.po, po/nl.po, po/pt.po, po/pt_BR.po, po/ru.po,
po/sv.po, po/vi.po: Normalized.
* po/it.po: Updated.
* auctex/templates.in: Reflow text. Keep debian-l10n-english team
review comment from flowing to "auctex/templates".
* control, rules.in (binary-indep-auctex), auctex/bug.script.in (FLAVORS),
auctex/conffiles.in, auctex/install.in, auctex/remove.in,
auctex/update-auctex-elisp.in (FLAVORS),
auctex/update-auctex-install.in (FLAVORS): Add Emacs 23 support.
(Closes: #539749, #540093)
* config.in: No more need to register "doauto/logfile" here.
* install.in (do_auto): Do not remove log files here. New log files
names.
* remove.in (undo_auto): Remove log files here. New log files names.
(Closes: #508348)
* update-auctex-install: New log files names.
* variables (TMPMASK): Remove it.
* variables (LOGFILE): New variable.
* install.in (do_install): For each flavor, for every byte compiled
file, install a symlink to the corresponding Elisp source from the
installation directory to the source directories, for the sole purpose
of allowing `find-function-search-for-symbol' (invoked by clicking on
the help-function-def-button provided by a function definition help
string) to find it. (Closes: #443930)
* remove.in (undo_install): Remove the symlinks to the Elisp sources
installed by "install.in (do_install)".
* rules.in (binary-arch): Strip "$(checkdir)" and "$(checkroot)".
[Lintian]
* auctex/lintian.in: Fix "debconf-is-not-a-registry" overrides paths.
Remove no more needed
"maintainer-script-does-not-check-for-existence-of-installdocs"
overrides.
* auctex/update-auctex-install.in, auctex/lintian.in: Needs no more
Debconf interaction.
* preview-latex-style/lintian.in: Remove no more needed
"maintainer-script-does-not-check-for-existence-of-installdocs"
lintian overrides.
* config.in: Implement Debconf backup capability.
* rules.in (debconf-test, debconf-ask-for-translations): New phonies.
* rules.in (build-package): Call lintian after building the package.
--8<---------------cut here---------------end--------------->8---
I still need to check latest policy (3.8.3), but I might also decide to
upload with 3.8.2 standards, deferring possibly needed changes to a
later moment (say one week).
fant> He means (I think) that the problem is pressing enough for him to
fant> want a solution *really*soon*. Since he can't NMU for a non-RC
fant> bug without your explicit Okay, the only "solution" for him would
fant> be to use a locally patched package, which is bad.
Well, unfortunately, that's what I do as well, for a number of package,
Debian or not, and I think that's what most of us do. Being free
software allows us to do it, and we have a lot of nice VCSs to cope with
it. It might be "bad" because it forces _us_ to do the work, but OTOH,
as I understand it, forcing others to work doesn't really work outside
commercial projects.
fant> It seems you block people from testing emacs23 if one of their
fant> main uses is TeX stuff. BTDT - using different emacs versions for
fant> different tasks is not an option if you want to do real work.
I feel people _testing_ emacs23 should now how to add something to the
load-path variable. :-)
Anyway, thank you for taking the time to elaborate on what you feel I
was missing, I appreciate it. I will try to avoid disappointing
reasonable people.
--
Ciao, Davide
Reply to: