On 1/2/19 9:44 PM, Cédric Boutillier wrote: > > Hi! > > I wanted to fix > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912245 > in ruby-nio4r about too small RSA keys in tests. > > I see that experimental contains ruby-nio4r 2.3.x for several months, > and reverse dependencies build successfully [1]. I pushed and 2.3.1 with > a fix for #912245 to experimental. > > Praveen, Sruthi, Is there a reason for this new version to be still in > experimental or is it safe to upload it to unstable? I think was uploaded to experimental because we could not really determine if it will break ruby-celluloid-io or not. But we were not able to get ruby-celluloid-io tests to work. We are considering to use systemd directly to replace ruby-eye, if that happens, ruby-cellulid-io won't be required for diaspora. > More generally, is there a place where are listed packages with version > in experimental with the reason why they are not in unstable? Following > reverse (build)dependencies, one often goes back to gitlab or diaspora, > as the big softwares consuming Ruby libraries, but it is not easy to see > where in the path problems are. And given the number of packages under > the team's umbrella, it does not scale. Generally we stage major updates in experimental till diaspora or gitlab is ready for unstable. We keep track of all the dependencies and problems for each update in a gitlab issue. So that would be https://git.fosscommunity.in/debian-ruby/TaskTracker/issues/134 for diaspora. > What about using explicitly the Breaks statement of the control file for > the version uploaded to experimental? Also, what about using > another branch than master (like 'experimental') to push these changes, > as it makes things a bit more difficult that it should to update > packages in unstable. I started using that recently from last ruby-github-linguist update Breaks: gitaly (<< 0.129.0+debian~), gitlab (<< 11.5.3+dfsg~) From now I will use it for all experimental uploads. > > Cheers, > > Cédric > > > 1:(celluloid-io seems to have tests failing without the testsuite > throwing errors though) >
Attachment:
signature.asc
Description: OpenPGP digital signature