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

Bug#921130: marked as done (RFS: php-elisp/1.21.0-1 [ITA])



Your message dated Sat, 02 Feb 2019 12:40:40 -0500
with message-id <87bm3u142v.fsf@curie.anarc.at>
and subject line Re: Bug#921130: RFS: php-elisp/1.21.0-1 [ITA]
has caused the Debian Bug report #921130,
regarding RFS: php-elisp/1.21.0-1 [ITA]
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.)


-- 
921130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921130
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Control: block 902633 by -1

Dear Mentors, Ola, and Moritz,

I am looking for a sponsor for my update/adoption of "php-elisp".

Package name    : php-elisp
Version         : 1.21.0-1
Upstream Author : USAMI Kenta <tadsan@zonu.me> (current maintainer)
URL             : https://github.com/emacs-php/php-mode
License         : GPL-3+
Section         : lisp

It builds these binary packages:

  elpa-php-mode - PHP Mode for GNU Emacs
  php-elisp - transitional package, php-elisp to elpa-php-mode

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

  https://mentors.debian.net/package/php-elisp

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

  dget -x https://mentors.debian.net/debian/pool/main/p/php-elisp/php-elisp_1.21.0-1.dsc

Alternatively, clone this git repo and use upstream git tag or uscan for the upstream source:

  git clone https://salsa.debian.org/emacsen-team/php-elisp.git

Changes since the last upload:

php-elisp (1.21.0-1) unstable; urgency=medium

  * Adopt package (Closes: #902633).
    - Add Emacsen team VCs links.
    - Set Maintainer to Debian Emacsen Team.
    - Add Ola Lundqvist and myself to Uploaders.
  * New upstream release (Closes: #895743).
  * Elpafy php-elisp:
    - Implicitly drops support for xemacs (Closes: #665314).
    - Add dh-elpa to Build-Depends.
    - Add new package: elpa-php-mode.
    - Convert php-elisp to dummy transitional package.
    - Rewrite debian/rules.
    - Enable autopkgtests.
    - Drop obsolete emacsen packaging directives: php-elisp.dirs,
      php-elisp.emacsen-install, php-elisp.emacsen-remove,
      php-elisp.emacsen-startup, php-elisp.emacsen-startup.new
      (Closes: #827827).
  * Declare compat level 11.
  * Switch to debhelper 11.
  * Declare Standards-Version: 4.3.0.
  * Update watchfile to v4, and update upstream project's location.
  * Suggest php and php-cli rather than php5 and php5-cli.
  * Add gbp.conf.
  * Add patch to disable php-project-root selftest.
  * Add upstream README.
  * Update Homepage, because php-mode has a new upstream maintainer.
    The project's transfer of ownership is documented here:
    https://github.com/emacs-php/php-mode/issues/387
  * Drop out-of-date php-elisp.README.Debian.  The upstream README contains
    this information.
  * Add debian/NEWS to notify users of depreciated PHP 2 support, and show
    how to restore the behaviour of past php-elisp releases.

 -- Nicholas D Steeves <nsteeves@gmail.com>  Fri, 01 Feb 2019 14:43:45 -0700

php-elisp (1.13.5-3) unstable; urgency=medium

Regards,
Nicholas D Steeves

--- End Message ---
--- Begin Message ---
I uploaded the package, but I'll note some improvements that could be
done on it:

 1. newer versions of debhelper allow deduplicating information between
    the control file and debian/compat. just remove the latter and
    change the control dependency to "debhelper-compat (=11)" (or
    12). see also:

    https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/

 2. very minor, but i like to keep the "transitional package" phrase on
    a separate line in package descriptions so it's more obvious to
    someone looking at the description

 3. why was the php-root self-test disabled? what's the next step for
    that patch? can it be sent upstream or will we have to carry this on
    forever?

Thanks for your work! :)

A.

-- 
I'm no longer accepting the things I cannot change.
I'm changing the things I cannot accept.
                        - Angela Davis

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: