Hello Lucas, > This is because pry 0.15.2-1 was uploaded a couple days ago. > > @Arlisson Jacques, Sameul Henrique: are you aware of this? Do you plan > to work on it? (it will prevent pry from migrating to testing)
I wasn't aware of it, thank you for the heads up. We have to package the latest ruby-pry-byebug which adds support for pry>=15, but we could also just update the version requirement, since upstream didn't really change anything to support the newer pry: https://github.com/deivid-rodriguez/pry-byebug/compare/deivid-rodriguez:daa3032...deivid-rodriguez:458c74b The problem is that ruby-pry-byebug is currently FTBFS and it doesn't look related to the bump on pry, did this FTBFS show up in your service Lucas? The first problem that needs to be solved is ruby-pry-byebug's FTBFS, then bumping it will be straightforward. Cheers, -- Samuel Henrique <samueloph>
