This repository has been archived by the owner. It is now read-only.

please update dependency on addressable #216

Open
swills opened this Issue Aug 7, 2012 · 10 comments

Comments

Projects
None yet
7 participants
@swills

swills commented Aug 7, 2012

Please update the dependency on addressable to support 2.3.2.

Thanks,
Steve

@solnic

This comment has been minimized.

Show comment
Hide comment
@solnic

solnic Aug 8, 2012

Contributor

already bumped in release-1.2. if the build passes I'll push 1.2.1

Contributor

solnic commented Aug 8, 2012

already bumped in release-1.2. if the build passes I'll push 1.2.1

@swills

This comment has been minimized.

Show comment
Hide comment
@swills

swills Aug 13, 2012

So, uh... Did it pass?

swills commented Aug 13, 2012

So, uh... Did it pass?

@solnic

This comment has been minimized.

Show comment
Hide comment
@solnic

solnic Aug 13, 2012

Contributor

Nope. Our CI is not in a good shape and requires major maintenance work. I'll be fixing it next week.

Contributor

solnic commented Aug 13, 2012

Nope. Our CI is not in a good shape and requires major maintenance work. I'll be fixing it next week.

@swills

This comment has been minimized.

Show comment
Hide comment
@swills

swills Sep 7, 2012

Any update on this?

swills commented Sep 7, 2012

Any update on this?

@fedya

This comment has been minimized.

Show comment
Hide comment
@fedya

fedya Nov 1, 2012

Any fix?

fedya commented Nov 1, 2012

Any fix?

@sporkmonger

This comment has been minimized.

Show comment
Hide comment
@sporkmonger

sporkmonger Dec 22, 2012

Contributor

Anything I can do to help here? It's been a very, very long time without a release... :-/

Contributor

sporkmonger commented Dec 22, 2012

Anything I can do to help here? It's been a very, very long time without a release... :-/

@gogolok

This comment has been minimized.

Show comment
Hide comment
@gogolok

gogolok Jan 7, 2013

The branch 'release-1.2' contains all the fixes.

What blocks the release?

gogolok commented Jan 7, 2013

The branch 'release-1.2' contains all the fixes.

What blocks the release?

@lsimoneau

This comment has been minimized.

Show comment
Hide comment
@lsimoneau

lsimoneau Jan 9, 2013

Yep, we're having to use release-1.2 from GitHub as well. A release would be much appreciated. Anything we can do to help?

Yep, we're having to use release-1.2 from GitHub as well. A release would be much appreciated. Anything we can do to help?

@gogolok

This comment has been minimized.

Show comment
Hide comment
@gogolok

gogolok Jan 9, 2013

As a side note: ATM the FreeBSD port of dm-core ( http://www.freshports.org/databases/rubygem-dm-core/ ) is marked broken because it can only use official ruby gems instead of a git commit AFAIK.

gogolok commented Jan 9, 2013

As a side note: ATM the FreeBSD port of dm-core ( http://www.freshports.org/databases/rubygem-dm-core/ ) is marked broken because it can only use official ruby gems instead of a git commit AFAIK.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.