Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2018-07-05 Thread Helmut Grohne
Hi Axel, On Thu, Jul 05, 2018 at 10:03:49PM +0200, Axel Beckert wrote: > Replacing any dependency on "ruby-ronn" with "ronn | ruby-ronn (<< > 0.7.3-5.1~)" should do the trick. That doesn't do what you think it does. Alternatives in Build-Depends are discarded in unstable. So this variant does not

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2018-07-05 Thread Axel Beckert
Hi Helmut, Helmut Grohne wrote: > I was aware that it would break stuff, but I saw little alternatives to > just making things break: > * Filing the bugs before adding the ronn package would be annoying, as >those bugs would be unfixable. Not at all: Replacing any dependency on "ruby-ronn"

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2018-07-05 Thread Helmut Grohne
Hi Axel, On Thu, Jul 05, 2018 at 07:34:47PM +0200, Axel Beckert wrote: > I would have been nice if this would have been done in _advance_ > instead of getting to hear in a just fixed FTBFS bug report that my > package now FTBFS due to today's ruby-ronn upload. (c.f. > https://bugs.debian.org/cgi-b

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2018-07-05 Thread Axel Beckert
Hi Helmut, Helmut Grohne wrote: > > Introducing this new package is not trivial: It must go through the NEW > > queue and we need to review the other 35 source packages that depend on > > ruby-ronn and maybe switch their dependency over to ronn. Still this > > solution sounds manageable to me. >

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2018-06-17 Thread Helmut Grohne
Control: tags -1 + pending On Sun, Nov 19, 2017 at 08:25:52PM +0100, Helmut Grohne wrote: > Your package suddenly became relevant to architecture bootstrap when > libidn2 started to build-depend on it. Unfortunately, this dependency > makes libidn2's Build-Depends unsatisfiable for cross compilati

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2017-11-24 Thread Simon McVittie
On Sun, 19 Nov 2017 at 20:25:52 +0100, Helmut Grohne wrote: > That puts us in a difficult spot: We must mark it and we cannot. Looking > closer, libidn2 really needs /usr/bin/ronn, not the ruby module. A > package containing just the script could be marked. Thus I propose > splitting ruby-ronn into

Bug#882163: ruby-ronn: unable to satisfy cross Build-Depends

2017-11-19 Thread Helmut Grohne
Package: ruby-ronn Version: 0.7.3-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap Control: affects -1 + src:libidn2 Hi ruby-ronn maintainers, Your package suddenly became relevant to architecture bootstrap when libidn2 started to build-depend on it. Unfortunately, this dependency mak