[07:57] <dholbach> good morning
[14:48] <michagogo|cloud> rbasak: What would be the process to do that?
[14:51] <rbasak> michagogo|cloud: I'm not sure. I suggest you try the ubuntu-release mailing list, point out that bitcoin is not in testing in Debian and ask for the same in Trusty.
[14:52] <rbasak> michagogo|cloud: I'm not sure that it's actually possible, but it sounds like a reasonable request to me. Just provide the list with the same justifications.
[14:53] <michagogo|cloud> Also, as I understand it, auto-upgrading the wallet is a BDB thing, not a Bitcoin thing -- in other words, when BDB 5.1 opens a BDB 4.8 database, it upgrades it. Also, upstream specifically always uses 4.8 -- the contrib/debian/control file's Build-Depends calls for libdb4.8++-dev specifically
[14:54] <michagogo|cloud> rbasak: Is there a deadline for that to happen, by the way?
[14:55] <rbasak> michagogo|cloud: is there no way to get BDB to not do that? Eg. open read-only and check version first?
[14:55] <michagogo|cloud> (I don't want to unilaterally start making requests, I'd like to discuss it in #bitcoin-dev and/or the bitcoin-development mailing list first)
[14:56] <rbasak> https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[14:56] <rbasak> michagogo|cloud: ^^ looks like Feb 20th for feature freeze. You should get it done in advance, though, since you'll need others to actually do things before that date.
[14:56] <michagogo|cloud> Right, of course
[14:56] <michagogo|cloud> Is FeatureFreeze the relevant date?
[14:58] <rbasak> It's a bit blurry for packages in universe, but I'd say that it's the most relevant point on the release schedule, yes. If it can be decided and done before then, then people shouldn't complain too much.