Bug#887740: moon-buggy: Please bump the Debian part of the version number

Hi, On Tue, Mar 27, 2018 at 09:06:56PM -0400, Jeremy Bicha wrote: > On Tue, Feb 6, 2018 at 3:50 AM, Raphael Hertzog wrote: > > So I would also suggest to bump version to 1:1.0.51-12. Not for launchpad, > > but for end users. > > Christian, may I do an NMU now to bump the

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Tue, Feb 6, 2018 at 3:50 AM, Raphael Hertzog wrote: > So I would also suggest to bump version to 1:1.0.51-12. Not for launchpad, > but for end users. Christian, may I do an NMU now to bump the Debian revision number? Thanks, Jeremy Bicha

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Thu, Jan 25, 2018 at 08:07:52PM +0100, Christian T. Steigies wrote: > If I can not use an epoch to start version numbers from scratch, then > the whole implementation of epochs is broken. Epochs were mainly intended for handling the case where upstream changed their version numbering sequence

Bug#887740: moon-buggy: Please bump the Debian part of the version number

Hello, On Thu, 25 Jan 2018, Christian T. Steigies wrote: > If I can not use an epoch to start version > numbers from scratch, then the whole implementation of epochs is broken. > I doubt that I am the first to fall into this trap. epochs are meant to go backwards when upstream changes their

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Wed, Jan 24, 2018 at 07:39:24PM -0500, Jeremy Bicha wrote: > On Wed, Jan 24, 2018 at 3:05 PM, Christian T. Steigies > wrote: > > The bug report you mention has had no activity since more than a year, so I > > guess this is not seen as a problem. If it were a problem, the

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Wed, Jan 24, 2018 at 3:05 PM, Christian T. Steigies wrote: > The bug report you mention has had no activity since more than a year, so I > guess this is not seen as a problem. If it were a problem, the upload > should have been rejected and not progressed into testing. If we

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Fri, Jan 19, 2018 at 11:44:50AM -0500, Jeremy Bicha wrote: > On Fri, Jan 19, 2018 at 11:11 AM, Christian T. Steigies > wrote: > > Since the package migrated to Debian/testing, I consider this to be a bug in > > Ubuntu Launchpad, not Debian. Please forward it to Ubuntu as I

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Fri, Jan 19, 2018 at 11:11 AM, Christian T. Steigies wrote: > Since the package migrated to Debian/testing, I consider this to be a bug in > Ubuntu Launchpad, not Debian. Please forward it to Ubuntu as I can not fix > bugs in Ubuntu. The only thing that is needed now is to

Bug#887740: moon-buggy: Please bump the Debian part of the version number

Moin, On Fri, Jan 19, 2018 at 10:55:35AM -0500, Jeremy Bicha wrote: > On Fri, Jan 19, 2018 at 10:45 AM, Christian T. Steigies > wrote: > > The package has migrated to testing, what else needs to be synced in Debian? > > What is Launchpad? > > Oops, I meant to write "can't be

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Fri, Jan 19, 2018 at 10:45 AM, Christian T. Steigies wrote: > The package has migrated to testing, what else needs to be synced in Debian? > What is Launchpad? Oops, I meant to write "can't be synced to Ubuntu". Launchpad is the service Ubuntu uses for bug tracking and many

Bug#887740: moon-buggy: Please bump the Debian part of the version number

On Fri, Jan 19, 2018 at 10:07:26AM -0500, Jeremy Bicha wrote: > Source: moon-buggy > Version: 1:1.0.51-1 > > moon-buggy can't be automatically synced to Debian because Launchpad > gives this error: > > moon-buggy 1:1.0.51-1 in buster (moon-buggy_1.0.51-1.dsc already > exists in destination

Bug#887740: moon-buggy: Please bump the Debian part of the version number

Source: moon-buggy Version: 1:1.0.51-1 moon-buggy can't be automatically synced to Debian because Launchpad gives this error: moon-buggy 1:1.0.51-1 in buster (moon-buggy_1.0.51-1.dsc already exists in destination archive with different contents.) I believe all you need to do to fix this is to