[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packages marked as testing auto-removel due to bug#999962



Manphiz <manphiz@gmail.com> writes:

> Nicholas D Steeves <sten@debian.org> writes:
>
>> Manphiz <manphiz@gmail.com> writes:
>>
>> To be fair, the following issue wasn't introduced by this MR, but was
[snip]
>> dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -l wgrep-subtest.el -l wgrep-test.el --eval \(ert-run-tests-batch-and-exit\) returned exit code 255
>> make: *** [debian/rules:4: binary] Error 25
>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
>>
>> I think that's unrelated to silversearcher-ag though ;)
>>
>
> I don't remember seeing this (or I missed it :P)
>
> But as I mentioned somewhere (mailing list or IRC, I forgot) it's
> probably easier just to fix siversearcher-ag directly.  So I'll
> retract this MR soon :)

This looks probably native-comp/trampoline-related to me, so I'm
guessing wgrep advises something.  No idea why why the issues presents
in emacs29 but not in emacs28.

> It seems that the maintainer has been MIA.  Do you suggest proposing an
> NMU?

Until a package has been orphaned by the MIA team, the question is NMU
vs salvaging:

  https://wiki.debian.org/PackageSalvaging
  https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging

If a minimal, targeted fix is possible (with a quilt patch) then an NMU
is faster, and doesn't implicate the uploader with long-term
responsibilities.  The allowed changes are narrow, and strict.

If that's not possible, then salvaging the package is the only way to
save it and its reverse dependencies.  Salvaging implies adoption.  I
took a look at the available forks and I suspect that salvaging the
Debian package is what will be required.

>> BTW, are you subscribed to this mailing list?  In Debian we
>> conventionally don't CC people on mailing lists, even though we do CC
>> people on bugs.
>>
>
> I'm subscribed. Feel free to directly reply to the mailing list.

Thanks!

Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: