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

Bug#1069078: marked as done (RFS: lua-mode/20210802-4 [RC] [Team] -- Emacs major-mode for editing Lua programs)

Your message dated Sat, 20 Apr 2024 07:30:28 +0100
with message-id <874jbw8s1n.fsf@zephyr.silentflame.com>
and subject line Re: Bug#1069078: RFS: lua-mode/20210802-4 [RC] [Team] -- Emacs major-mode for editing Lua programs
has caused the Debian Bug report #1069078,
regarding RFS: lua-mode/20210802-4 [RC] [Team] -- Emacs major-mode for editing Lua programs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1069078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069078
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "lua-mode":

 * Package name     : lua-mode
   Version          : 20210802-4
   Upstream contact : immerrr <immerrr@gmail.com>
 * URL              : https://github.com/immerrr/lua-mode
 * License          : GPL-2+
 * Vcs              : https://salsa.debian.org/emacsen-team/lua-mode
   Section          : lisp

The source builds the following binary packages:

  elpa-lua-mode - Emacs major-mode for editing Lua programs

To access further information about this package, please visit the following URL:

  https://mentors.debian.net/package/lua-mode/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20210802-4.dsc

Changes since the last upload:

 lua-mode (20210802-4) unstable; urgency=medium
 .
   * Team upload
   * Mark lexical binding patch as Forwarded and Applied-Upstream
   * Add patch to use eval in lexical scope to fix tests (Closes: #1069073)
   * Keep source *.el in autopkgtest to make it work
   * Add Upstream-Contact in d/copyright
   * Update homepage to github page in d/control (old link no longer works)
   * Set Rules-Requires-Root to no in d/control
   * Drop Built-Using from arch:all package in d/control
   * Trim trailing whitespace in d/changelog
   * Bump debhelper from old 10 to 13
   * Set debhelper-compat version in Build-Depends
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
     Repository-Browse
   * Update Standards-Version to 4.7.0; no change needed
   * Modernize d/watch with substitute strings to be more robust

Regards,
-- 
Xiyue Deng

--- End Message ---
--- Begin Message --- 
Hello,

On Fri 19 Apr 2024 at 01:23pm -07, Xiyue Deng wrote:

> So it turns out using "disable" in d/elpa-test also disable dh_elpa_test
> in d/rules so that the test is not run as part of the package building,
> which would be suboptimal in that we don't run any test at all.  I'll
> try to see a way to disable it only in autopkgtest in dh-elpa.
>
> On the other hand, it looks like I misjudged the situation of the
> buttercup tests that with "autopkgtest_keep = test/*" it just works,
> which is much better than disabling.

Yes, that's fine, thanks.

> Ack.  I also checked that bug before and wondering why that lintian tag
> is still enabled.  Hopefully Bug#1069256 will move things forward.

The reason it's still enabled is probably #1012289.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: