Re: Dealing with upstream only releasing gems

this is all about upstream, we > > should really encourage them to at least tag there stuff. Packaging and > > maintaining in essence "release/version-less" software is undoable. > > Even more so if it is team-maintained since you might know what the > > situation

Re: Dealing with upstream only releasing gems

Packaging and > maintaining in essence "release/version-less" software is undoable. > Even more so if it is team-maintained since you might know what the > situation is but not the other team members. Of course, you could use versioning as 20100409 - if you are confident enough with t

Re: Merb 1.1.0

Joshua Timberman dijo [Mon, Mar 29, 2010 at 01:23:20PM -0600]: > Just wanted to note that I'm not planning on updating the Merb package > for the latest release, 1.1.0 quite yet. Merb's existence in Debian is > largely because of the dependency for Chef Server, and the WebUI > component of Ch

Re: libnet-{scp,sftp,sftp2,ssh,ssh2}-ruby

On Wed, Mar 31, 2010 at 03:01:28PM +0900, Tatsuki Sugiura wrote: > I'm Sorry. It's my fault! > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572036#36 > > > Upstream distributes both (1.x and 2.x). I think it's convenient > > so on debian. I should revert version of libnetnet-ssh-ruby and > > l