TEMPORARY: Revert this patch after bitcoin-io v0.1.4 merges

We want CI to pass on the io-0.1.x branch but `bitcoin` is currently
borked and its breaking the build. Since we are only doing the `io`
release add a patch that fixes the build, after we build and tag the
patch before this one we can then revert this one. Ugly as sin I know.

Author: tcharding

bitcoin/src/blockdata/locktime/absolute.rs

@@ -284,7 +284,12 @@ impl LockTime {
     }
 }
 
-units::impl_parse_str_from_int_infallible!(LockTime, u32, from_consensus);
+// REVERT THIS CHANGE SOON AS `bitcoin-io v0.1.4` IS RELEASED.
+//
+// This macro call is borked because `btcoin` does not have the `alloc` feature and the macro
+// contains feature gating `<insert usual rand about calling macros across crate boundries>`.
+//
+// units::impl_parse_str_from_int_infallible!(LockTime, u32, from_consensus);
 
 impl From<Height> for LockTime {
     #[inline]

bitcoin/src/blockdata/transaction.rs

@@ -526,7 +526,12 @@ impl fmt::Debug for Sequence {
     }
 }
 
-units::impl_parse_str_from_int_infallible!(Sequence, u32, from_consensus);
+// REVERT THIS CHANGE SOON AS `bitcoin-io v0.1.4` IS RELEASED.
+//
+// This macro call is borked because `btcoin` does not have the `alloc` feature and the macro
+// contains feature gating `<insert usual rand about calling macros across crate boundries>`.
+//
+// units::impl_parse_str_from_int_infallible!(Sequence, u32, from_consensus);
 
 /// Bitcoin transaction output.
 ///