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

Bug#910898: marked as done (RFS: elpy/1.25.0-1)

Your message dated Sat, 13 Oct 2018 10:31:19 +0000
with message-id <E1gBHCZ-0006L6-Az@quantz.debian.org>
and subject line closing RFS: elpy/1.25.0-1
has caused the Debian Bug report #910898,
regarding RFS: elpy/1.25.0-1
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.)


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

Hi Chris and dear mentors,

I am looking for a sponsor for my package "elpy"

Package name    : elpy
Version         : 1.25.0-1
URL             : https://elpy.readthedocs.io/en/latest/index.html
License         : GPL-3+
Section         : devel

It builds this binary package:

  elpa-elpy  - Emacs Python Development Environment

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

  https://mentors.debian.net/package/elpy

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

  dget -x https://mentors.debian.net/debian/pool/main/e/elpy/elpy_1.25.0-1.dsc

Or clone the repository

  git clone https://salsa.debian.org/emacsen-team/elpy.git
  # gbp will work out of the box
  # alternative use git deborig to generate orig tarball from tag
  # or use uscan

Changes since the last upload:

elpy (1.25.0-1) unstable; urgency=medium

  * New upstream version.
  * Upstream no longer distributes NEWS.rst
    - debian/rules: Drop build/NEWS generation.
    - Drop debian/local-var-snippet which was only used in NEWS.
    - debian/docs: do not install build/NEWS.
    - debian/elpa-test: Do not run test for elpy-news-should-insert-file,
      because it depends on NEWS.rst, which was dropped upstream.
  * Support 'nodoc' build profile
    - debian/control: Add <!nodoc> to python3-sphinx and texinfo build deps.
    - debian/rules: Only attempt to generate documentation when nodoc is
      not present in DEB_BUILD_PROFILES.
    - debian/rules: Workaround Bug #908078, because dh_sphinxdoc does not
      yet detect when "nodoc" is active and --with sphinxdoc will fail when
      python3-sphinx is not installed.
  * Add lintian-override for wrong-section-according-to-package-name, because
    section "devel" is most appropriate for an IDE for Python development
    when that IDE is implemented in Emacs Lisp.
  * debian/rules: Fix typo.
  * Enable support for Black, the uncompromising Python code formatter, now
    that it has been added to the Debian archive.
    - debian/control: Add black to Build-Depends and Suggests.
    - Drop debian/patches/0002-Disable-tests-for-black-code-formatter.patch.
  * Import upstream 0002-Handle-sphinx-warnings-linked-to-indexnode.patch
    This patch fixes numerous warnings of "4 column based index found" when
    building.
  * Fix sentence fragment in long description.
  * debian/elpa-test: Temporarily disable
    elpy-promise-wait-should-return-early-for-resolved and related tests
    in elpy-promise-wait-test.el.  This test passes 100% of the time with
    python3.6=3.6.6-1 and python3.7=3.7.1~rc1-1 and fails ~40% of the time
    with python3.6=3.6.7~rc1-1.  Issue has been forwarded upstream.  Tests
    involving Elpy "promises" will be reenabled after the Python 3.7
    transition. (Closes: #910311)

 -- Nicholas D Steeves <nsteeves@gmail.com>  Fri, 12 Oct 2018 18:16:00 -0400

elpy (1.24.0-1) unstable; urgency=medium


Regards,
Nicholas D Steeves

--- End Message ---
--- Begin Message --- 
Package elpy version 1.25.0-1 is in unstable now.
https://packages.qa.debian.org/elpy

--- End Message ---
Reply to: