Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9096 > unrolled thread
| Started by | Alberto Caso <alberto.caso@juntaex.es> |
|---|---|
| First post | 2016-12-18 19:20 +0100 |
| Last post | 2016-12-18 22:30 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
Upstream's new version for a package awaiting review and upload Alberto Caso <alberto.caso@juntaex.es> - 2016-12-18 19:20 +0100
Re: Upstream's new version for a package awaiting review and upload Sandro Tosi <morph@debian.org> - 2016-12-18 22:30 +0100
| From | Alberto Caso <alberto.caso@juntaex.es> |
|---|---|
| Date | 2016-12-18 19:20 +0100 |
| Subject | Upstream's new version for a package awaiting review and upload |
| Message-ID | <sPOdX-4zd-9@gated-at.bofh.it> |
Dear teams, pydbus 0.5.1-1 package [1] is awaiting review and sponsorship [2]. In the meantime, upstream has released a new version (0.6.0). Considering that my initial package release has not yet been uploaded (nor even reviewed), should I update master, upstream and pristine-tar to sync with upstream sources and modify the initial debian/changelog entry to reflect the new version number as if the current version never existed, or should I ignore that the package was never uploaded, tag the current version as 0.5.1-1 and add a new debian/changelog entry? Thank you in advance. [1] https://anonscm.debian.org/cgit/python-modules/packages/pydbus.git/ [2] https://lists.debian.org/debian-python/2016/12/msg00031.html -- Alberto Caso Palomino Servicio de Implantación de Sistemas Dirección Gral. de Admón. Electrónica y TI Consejería de Hacienda y Administración Pública Junta de Extremadura
[toc] | [next] | [standalone]
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Date | 2016-12-18 22:30 +0100 |
| Message-ID | <sPRbP-7ay-3@gated-at.bofh.it> |
| In reply to | #9096 |
On Sun, Dec 18, 2016 at 1:14 PM, Alberto Caso <alberto.caso@juntaex.es> wrote: > should I update master, upstream and pristine-tar > to sync with upstream sources and modify the initial debian/changelog > entry to reflect the new version number as if the current version never > existed yes, prepare the package as if it was the first time you were doing it (ok the git repo will contain the previous upstream release, but it's not a big deal) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web