Bug#970210: forcemerge vs. pkgreport.cgi

2021-01-16 Thread Robert Luberda
severity 970210 important thanks Don Armstrong pisze: > > retitle 970210 repeatmerged=no can't be configured to show a bug other than > the lowest numbered bug > severity 970210 wishlist It's not a wishlist, it's a bug, as the current behavior, that is based on some strange assumption that a re

Bug#970210: forcemerge vs. pkgreport.cgi

2021-01-15 Thread Don Armstrong
retitle 970210 repeatmerged=no can't be configured to show a bug other than the lowest numbered bug severity 970210 wishlist tag 970210 wontfix thanks On Sun, 10 Jan 2021, Robert Luberda wrote: > I agree with Dan. I've just forcemerged 979575 979549 979565, and then > marked 979575 as affecting

Bug#970210: forcemerge vs. pkgreport.cgi

2021-01-10 Thread Robert Luberda
severity 970210 important thanks On nie, 13 wrz 2020, 積丹尼 Dan Jacobson wrote: > Package: bugs.debian.org > > One would expect > forcemerge A B > to cause > pkgreport.cgi?package=X > to list A, not B. > I mean B gets A's version, etc. I agree with Dan. I've just forcemerged 979575 979549 979565,

Bug#970210: forcemerge vs. pkgreport.cgi

2020-09-12 Thread 積丹尼 Dan Jacobson
Package: bugs.debian.org One would expect forcemerge A B to cause pkgreport.cgi?package=X to list A, not B. I mean B gets A's version, etc. OK maybe pkgreport.cgi always lists the lower numbered bug no matter what. Well https://www.debian.org/Bugs/server-control#forcemerge should mention that.