On Wed, Jul 15, 2015 at 11:17:19AM -0300, Antonio Terceiro wrote: > On Wed, Jul 15, 2015 at 10:50:21AM -0300, Antonio Terceiro wrote: > > On Tue, Jul 14, 2015 at 01:26:21PM +0300, Hleb Valoshka wrote: > > > Hi team. > > > > > > I want to update ruby-hashie to version 2.1.2 (the latest of 2.x > > > branch), because I'm packaging gem which depends on hashie (>= 2.1, < > > > 3), as other packages depends on ruby-hashie or on ruby-hashie (>= > > > 1.2, < 3) I don't expect to have problems with this update. > > > > > > If nobody objects I'll push changes in several days. > > > > I am also needing hashie 2.1, do you already have the packaging done? > > I just tried this myself, and 2.1 has inumerous incompatibilities with > rspec3, while the latest upstream version (3.4.2) passes clean. > > Can your thing be patched to accept 3.x?
I have pushed ruby-hashie 3.4.2-1 to git, but didn't upload yet. I see several ruby-omniauth* packages that depend on < 3, but their new upstream version seems to have < 4 instead. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
