Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13413 > unrolled thread

Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

Back to article view | Back to linux.debian.maint.python

Contents

  Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x Fabrice Bauzac-Stehly <noon@mykolab.com> - 2021-06-05 01:40 +0200
    Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click -  Python 3.x Stefano Rivera <stefanor@debian.org> - 2021-06-05 22:30 +0200
    Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click  - Python 3.x Fabrice Bauzac-Stehly <noon@mykolab.com> - 2021-06-08 00:40 +0200
    Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x Fabrice Bauzac-Stehly <noon@mykolab.com> - 2021-06-08 14:00 +0200

#13413 — Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-click-log":

 * Package name    : python-click-log
   Version         : 0.3.2-1
   Upstream Author : [fill in name and email of upstream]
 * URL             : https://github.com/click-contrib/click-log
 * License         : Expat
 * Vcs             : https://salsa.debian.org/python-team/packages/python-click-log
   Section         : python

It builds those binary packages:

  python3-click-log - Logging integration for Click - Python 3.x

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

  https://mentors.debian.net/package/python-click-log/

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

  dget -x https://mentors.debian.net/debian/pool/main/p/python-click-log/python-click-log_0.3.2-1.dsc

Changes since the last upload:

 python-click-log (0.3.2-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 12.
   * Set upstream metadata fields: Bug-Database, Repository, Repository-
     Browse.
   * Remove constraints unnecessary since stretch:
     + Build-Depends: Drop versioned constraint on dh-python.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
     contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
     layout.
 .
   [ Fabrice Bauzac-Stehly ]
   * New upstream release.
   * Upgrade d/watch to version 4.
   * Upgrade the Standards-Version to 4.5.1.
   * Declare Rules-Requires-Root: no.

Best regards

-- 
Fabrice Bauzac-Stehly
PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6

[toc] | [next] | [standalone]

#13414 — Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

Hi Nilesh (2021.06.05_15:21:22_+0000)
> > * What about adding an autopkgtest?
> 
> The test is running during build time.[1] I don't think running the same thing as autopkgtest does a very significant improvement.

I think there's generally an advantage in running the same upstream
tests at build time, as well as in an autopkgtest:

1. If something regresses the test suite, it'll block migration of that
   package into testing.
2. It verifies that the package behaves correctly, as installed. (This
   can mean that you need to disable part of the test-suite, that can't
   handle the installed layout.)

Yes, it's also good to have other kinds of tests in autopkgtests, that
verify installed behaviour (e.g. calling --help on an executable, to see
that it can start-up, and smoke testing library public interfaces).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13415 — Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

Emmanuel Arias <emmanuelarias30@gmail.com> writes:

> * What about adding an autopkgtest?

Added.

-- 
Fabrice Bauzac-Stehly
PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6

[toc] | [prev] | [next] | [standalone]

#13416

Nilesh Patra <nilesh@nileshpatra.info> writes:

> * The pristine tar contained <package-name>.tar.gz.*, it should
> instead contain .orig.tar.gz for origtargz both for the sake of
> consistency and for origtargz to run fine

Oops, OK, I have just re-run pristine-tar on the .orig file and
committed.

> * We are in freeze time, and a new version upload unless absolutely
> necessary isn't appropriate[2]. This package does not seem to have any
> (RC) bug or affecting any package that a version bump would be
> desired.
>
> Hence, this should be uploaded after bullseye release. Feel free to
> ping me then, and I'll happily sponsor. Also, please take a look at my
> commits in salsa.
>
> [2]: https://release.debian.org/testing/freeze_policy.html

I'm fine with waiting.  After the freeze, I think it will be ready for
uploading (I don't want to spam mentors.d.o during the freeze).

Thanks a lot for your help!

Best regards

-- 
Fabrice Bauzac-Stehly
PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web