Bug#653332: thin is unmaintained

2012-01-07 Thread Faidon Liambotis
On Mon, Dec 26, 2011 at 10:04:32PM -0800, Ryan Niebur wrote: On Tue, Dec 27, 2011 at 04:44:31AM +0200, Faidon Liambotis wrote: The package in its current version works for me. However, I believe it is unsuitable for a release (and hence inclusion in testing) as it's clearly lacking a

Bug#653332: [DRE-maint] Bug#653332: thin is unmaintained

2012-01-07 Thread Paul van Tilburg
On Sat, Jan 07, 2012 at 05:01:52PM +0200, Faidon Liambotis wrote: On Mon, Dec 26, 2011 at 10:04:32PM -0800, Ryan Niebur wrote: On Tue, Dec 27, 2011 at 04:44:31AM +0200, Faidon Liambotis wrote: The package in its current version works for me. However, I believe it is unsuitable for a

Bug#653332: [DRE-maint] Bug#653332: thin is unmaintained

2012-01-07 Thread Ryan Niebur
On Sat, Jan 07, 2012 at 05:15:54PM +0100, Paul van Tilburg wrote: On Sat, Jan 07, 2012 at 05:01:52PM +0200, Faidon Liambotis wrote: On Mon, Dec 26, 2011 at 10:04:32PM -0800, Ryan Niebur wrote: On Tue, Dec 27, 2011 at 04:44:31AM +0200, Faidon Liambotis wrote: The package in its current

Bug#653332: [DRE-maint] Bug#653332: thin is unmaintained

2011-12-27 Thread Paul van Tilburg
On Mon, Dec 26, 2011 at 10:04:32PM -0800, Ryan Niebur wrote: On Tue, Dec 27, 2011 at 04:44:31AM +0200, Faidon Liambotis wrote: The package in its current version works for me. However, I believe it is unsuitable for a release (and hence inclusion in testing) as it's clearly lacking a

Bug#653332: thin is unmaintained

2011-12-26 Thread Faidon Liambotis
Package: thin Version: 1.2.4-1.1 Severity: serious Hi, I noticed that the package thin hasn't been maintained properly. It hasn't had a maintainer upload since September 2009 when 1.2.4-1 was uploaded; during that time, upstream released 1.2.6 (Feb 2010), 1.2.7 (March 2010), 1.2.8 (February

Bug#653332: thin is unmaintained

2011-12-26 Thread Ryan Niebur
On Tue, Dec 27, 2011 at 04:44:31AM +0200, Faidon Liambotis wrote: The package in its current version works for me. However, I believe it is unsuitable for a release (and hence inclusion in testing) as it's clearly lacking a maintainer. I'd suggest either to start working on it, or O/RFH it.