Hello Bastian By exchange on this bug #1134471 as well as #1123467, neither
- a proposed fix which would rely on more recent upstream data (from rubygem), as well - a proposed fix which attempts to «freeze» the state prior to the bug qualifies as «good enough» to resolve the problem. Then, the issue is too large for me. I think the best I still can do is to close my RFS / NMU bug, correct? Best regards, Norwid
