Re: Debian part of a version number when epoch is bumped

2018-04-02 Thread James McCoy
On Mon, Apr 02, 2018 at 11:01:30PM -0400, The Wanderer wrote: > On 2018-04-02 at 15:41, Simon McVittie wrote: > > > On Mon, 02 Apr 2018 at 20:30:54 +0200, Christian T. Steigies wrote: > > > >> I don't understand why everybody is so afraid of an epoch, but ok. > > > > It's a source of confusion (

Re: Debian part of a version number when epoch is bumped

2018-04-02 Thread The Wanderer
On 2018-04-02 at 15:41, Simon McVittie wrote: > On Mon, 02 Apr 2018 at 20:30:54 +0200, Christian T. Steigies wrote: > >> I don't understand why everybody is so afraid of an epoch, but ok. > > It's a source of confusion (and confusing side-effects) that, once > added, can never be removed, howev

Re: Debian part of a version number when epoch is bumped

2018-04-02 Thread Simon McVittie
On Mon, 02 Apr 2018 at 20:30:54 +0200, Christian T. Steigies wrote: > I don't understand why everybody is so afraid of an epoch, but ok. It's a source of confusion (and confusing side-effects) that, once added, can never be removed, however many upstream releases might happen. > On Fri, Mar 30, 2

Re: Debian part of a version number when epoch is bumped

2018-04-02 Thread Adrian Bunk
On Mon, Apr 02, 2018 at 08:30:54PM +0200, Christian T. Steigies wrote: > Moin, Hi, > On Fri, Mar 30, 2018 at 02:21:43PM +0300, Adrian Bunk wrote: > > > > There are two problems here. > > > > The first is the use of an epoch in a situation where it shouldn't be used. > > > > The actual "trap" i

Re: Debian part of a version number when epoch is bumped

2018-04-02 Thread Christian T. Steigies
Moin, On Fri, Mar 30, 2018 at 02:21:43PM +0300, Adrian Bunk wrote: > > There are two problems here. > > The first is the use of an epoch in a situation where it shouldn't be used. > > The actual "trap" is when a maintainer used an epoch in such a situation. > > Once introduced in a package an e

Re: What problem might happen when bumping soname without adding Conflicts:/Breaks:?

2018-04-02 Thread Russ Allbery
Adrian Bunk writes: > The default in Debian is to allow coinstallation of the libraries, > but there are actually cases where it is better to add a Conflicts. > Without symbol versioning it is a problem if you end up with both > libraries in a binary, in this case e.g.: > deepin-menu -> libdf

Re: What problem might happen when bumping soname without adding Conflicts:/Breaks:?

2018-04-02 Thread Gert Wollny
Am Donnerstag, den 29.03.2018, 21:43 +0300 schrieb Adrian Bunk: > On Wed, Mar 28, 2018 at 08:08:07PM -0700, Russ Allbery wrote: > > Boyuan Yang <073p...@gmail.com> writes: > > > > > * Upstream released new version and bumped SONAME to 2 > > > * -dev package didn't change its name > > > * My mentor

Bug#894633: ITP: r-cran-openxlsx -- GNU R package for XLSX files

2018-04-02 Thread Dirk Eddelbuettel
Package: wnpp Owner: Dirk Eddelbuettel Severity: wishlist * Package name: r-cran-openxlsx Version : 4.0.17 Upstream Author : Alexander Walker * URL or Web page : https://github.com/awalker89/openxlsx * License : GPL-3 Description : GNU R package for XLSX files This