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


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

FYI: Fwd: RFS: pygithub/1.35-1[ITA]

Started by"eamanu15 ." <emmanuelarias30@gmail.com>
First post2018-01-17 22:40 +0100
Last post2018-01-20 00:30 +0100
Articles 6 — 6 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  FYI: Fwd: RFS: pygithub/1.35-1[ITA] "eamanu15 ." <emmanuelarias30@gmail.com> - 2018-01-17 22:40 +0100
    Re: FYI: Fwd: RFS: pygithub/1.35-1[ITA] Filip Pytloun <filip@pytloun.cz> - 2018-01-17 23:20 +0100
      Re: FYI: Fwd: RFS: pygithub/1.35-1[ITA] Dmitry Shachnev <mitya57@debian.org> - 2018-01-19 12:30 +0100
        Re: DPMT and git workflows Simon McVittie <smcv@debian.org> - 2018-01-19 12:50 +0100
          Re: DPMT and git workflows IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2018-01-19 18:40 +0100
            Re: DPMT and git workflows Stuart Prescott <stuart@debian.org> - 2018-01-20 00:30 +0100

#10067 — FYI: Fwd: RFS: pygithub/1.35-1[ITA]

From"eamanu15 ." <emmanuelarias30@gmail.com>
Date2018-01-17 22:40 +0100
SubjectFYI: Fwd: RFS: pygithub/1.35-1[ITA]
Message-ID<v93B7-4zG-11@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

FYI

---------- Forwarded message ---------
From: eamanu15 . <emmanuelarias30@gmail.com>
Date: mié., 17 de ene. de 2018 a la(s) 18:37
Subject: RFS: pygithub/1.35-1[ITA]
To: Debian Mentors List <debian-mentors@lists.debian.org>


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name    : pygithub
  Version         : 1.35-1
  Upstream Author : Adam Dangoor <adamdangoor@gmail.com>
                    Vincent Jacques <vincent@vincent-jacques.net>
                Jeremy Phelps <jphelps@linuxfoundation.org>
* URL             : https://pypi.python.org/pypi/PyGithub
* License         : LGPL-3+
  Section         : python

It builds those binary packages:
    python-github - Access to full Github API v3 from Python2
    python3-github - Access the full Github API v3 from Python3

To access further information about this package, please visit the
following URL:
    https://mentors.debian.net/package/pygithub

Alternatively, one can download the package with dget using this command:
    dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.35-1.dsc

Changes since the last upload:
   * New upstream release
   * Update Maintainer field from debian/control to intent to adopt
    the package (Closes: #851187)
   * Update Standards-Version from  3.9.6 to 4.1.3 from debian control
according to the up-to-date standards
   * Add new maintainer on copyright debian/* files field from
    debian/copyright to stay up-to-date
   * Remove override_dh_installchangelogs target from debian/rules due to
the new version (1.35) do not have README.rst file

Regards,
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

[toc] | [next] | [standalone]


#10068

FromFilip Pytloun <filip@pytloun.cz>
Date2018-01-17 23:20 +0100
Message-ID<v94dP-54V-3@gated-at.bofh.it>
In reply to#10067

[Multipart message — attachments visible in raw view] — view raw

Hello Emmanuel,

few notes to your package:

- it would be good to move under DPMT (have you joined the team
  already?), create git repository and use git-dpm to import current
  version and make your changes, also set Maintainer and Vcs-* to
  reflect this

- You should update bug #851187 and change topic s,RFA,ITA + assign to
  yourself

- d/compat + d/control: update debhelper to latest 11

- d/copyright:
    - add yourself into copyright holders for debian/*
    - use https in Format url

- d/control:
    - X-Python-Version and X-Python3-Version are not needed
    - Add support for autopkgtest (Testsuite: autopkgtest-pkg-python)
    - Run `wrap-and-sort -bast` if you haven't already

Filip

On 2018/01/17 21:37, eamanu15 . wrote:
> FYI
> 
> ---------- Forwarded message ---------
> From: eamanu15 . <emmanuelarias30@gmail.com>
> Date: mié., 17 de ene. de 2018 a la(s) 18:37
> Subject: RFS: pygithub/1.35-1[ITA]
> To: Debian Mentors List <debian-mentors@lists.debian.org>
> 
> 
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "pygithub"
> 
> * Package name    : pygithub
>   Version         : 1.35-1
>   Upstream Author : Adam Dangoor <adamdangoor@gmail.com>
>                     Vincent Jacques <vincent@vincent-jacques.net>
>                 Jeremy Phelps <jphelps@linuxfoundation.org>
> * URL             : https://pypi.python.org/pypi/PyGithub
> * License         : LGPL-3+
>   Section         : python
> 
> It builds those binary packages:
>     python-github - Access to full Github API v3 from Python2
>     python3-github - Access the full Github API v3 from Python3
> 
> To access further information about this package, please visit the
> following URL:
>     https://mentors.debian.net/package/pygithub
> 
> Alternatively, one can download the package with dget using this command:
>     dget -x
> https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.35-1.dsc
> 
> Changes since the last upload:
>    * New upstream release
>    * Update Maintainer field from debian/control to intent to adopt
>     the package (Closes: #851187)
>    * Update Standards-Version from  3.9.6 to 4.1.3 from debian control
> according to the up-to-date standards
>    * Add new maintainer on copyright debian/* files field from
>     debian/copyright to stay up-to-date
>    * Remove override_dh_installchangelogs target from debian/rules due to
> the new version (1.35) do not have README.rst file
> 
> Regards,
> Emmanuel
> 
> 
> -- 
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
> 
> 
> -- 
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com

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


#10071

FromDmitry Shachnev <mitya57@debian.org>
Date2018-01-19 12:30 +0100
Message-ID<v9D1U-2HS-11@gated-at.bofh.it>
In reply to#10068

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jan 17, 2018 at 11:14:41PM +0100, Filip Pytloun wrote:
> Hello Emmanuel,
>
> few notes to your package:
>
> - it would be good to move under DPMT (have you joined the team
>   already?), create git repository and use git-dpm to import current
>   version and make your changes, also set Maintainer and Vcs-* to
>   reflect this

I think for new packages it is better to use gbp-pq based workflow:
https://wiki.debian.org/Python/GitPackagingPQ

git-dpm is unmaintained and is (IMO) more difficult to work with.

--
Dmitry Shachnev

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


#10072 — Re: DPMT and git workflows

FromSimon McVittie <smcv@debian.org>
Date2018-01-19 12:50 +0100
SubjectRe: DPMT and git workflows
Message-ID<v9Dlf-2Oi-7@gated-at.bofh.it>
In reply to#10071
On Fri, 19 Jan 2018 at 14:25:57 +0300, Dmitry Shachnev wrote:
> I think for new packages it is better to use gbp-pq based workflow:
> https://wiki.debian.org/Python/GitPackagingPQ

Is there consensus that the gbp-pq workflow is now allowed? I only
maintain one package in DPMT (tap.py) and every time I upload it I have
to remind myself how git-dpm works, so I'd like to switch it over to
gbp-pq as soon as I can.

Relatedly, Alioth is going to be shut down at some point, with git
repositories frozen and made read-only, so it would seem a good idea to
start migrating git packaging to salsa.debian.org before that happens.
python-modules-team and python-apps-team groups, perhaps? I can create
a python-modules-team group and migrate tap.py as a sample if people
would like to see an example package.

    smcv

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


#10073 — Re: DPMT and git workflows

FromIOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org>
Date2018-01-19 18:40 +0100
SubjectRe: DPMT and git workflows
Message-ID<v9INX-6lf-1@gated-at.bofh.it>
In reply to#10072

[Multipart message — attachments visible in raw view] — view raw

On 01/19/2018 12:45 PM, Simon McVittie wrote:
> On Fri, 19 Jan 2018 at 14:25:57 +0300, Dmitry Shachnev wrote:
>> I think for new packages it is better to use gbp-pq based workflow:
>> https://wiki.debian.org/Python/GitPackagingPQ
> 
> Is there consensus that the gbp-pq workflow is now allowed? I only
> maintain one package in DPMT (tap.py) and every time I upload it I have
> to remind myself how git-dpm works, so I'd like to switch it over to
> gbp-pq as soon as I can.
> 
> Relatedly, Alioth is going to be shut down at some point, with git
> repositories frozen and made read-only, so it would seem a good idea to
> start migrating git packaging to salsa.debian.org before that happens.
> python-modules-team and python-apps-team groups, perhaps? I can create
> a python-modules-team group and migrate tap.py as a sample if people
> would like to see an example package.
> 

should we keep the structure of putting all packages into a separate
subdir (aka "sub-group").

i was also thinking about creating a single python-team group with a
PAPT and a DPMT subgroup, but apart from aesthetics i cannot think of
any good reason to do so. it probably creates more trouble than it is worth.

gfards
IOhannes

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


#10075 — Re: DPMT and git workflows

FromStuart Prescott <stuart@debian.org>
Date2018-01-20 00:30 +0100
SubjectRe: DPMT and git workflows
Message-ID<v9OgF-1pz-7@gated-at.bofh.it>
In reply to#10073
IOhannes m zmölnig (Debian/GNU) wrote:
> On 01/19/2018 12:45 PM, Simon McVittie wrote:
>> Relatedly, Alioth is going to be shut down at some point, with git
>> repositories frozen and made read-only, so it would seem a good idea to
>> start migrating git packaging to salsa.debian.org before that happens.
>> python-modules-team and python-apps-team groups, perhaps? I can create
>> a python-modules-team group and migrate tap.py as a sample if people
>> would like to see an example package.
>> 
> 
> should we keep the structure of putting all packages into a separate
> subdir (aka "sub-group").

I don't think there is anything to be gained by that and there are some 
limitations on sub-groups in salsa such as not being able to have rendered 
websites (that feature is prototyped but not yet enabled).

 
> i was also thinking about creating a single python-team group with a
> PAPT and a DPMT subgroup, but apart from aesthetics i cannot think of
> any good reason to do so. it probably creates more trouble than it is
> worth.

I don't know the historical origins of this split and I have never seen the 
advantage in splitting the two groups. Maybe it's time to have PAPT do the 
svn→git transition and put everything in the same debian-python-team?

cheers
Stuart

-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart@nanonanonano.net
Debian Developer   http://www.debian.org/         stuart@debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

[toc] | [prev] | [standalone]


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


csiph-web