[10:40:01] moritzm: what would be an example of 0.2.8-2 release for the debmonitor-client? [10:42:54] e.g. a change which only changes a dependency in debian/control or so [10:44:02] I've asked in the CR too, but maybe easier here, given that we add the debNNuM suffix at build time, wouldn't be 'wrong' to have in the repo 2 changelog entries with the same version? [10:46:24] it it's all scripted, -2 is equally fine, it doesn't make much of a difference as long as debmonitor is not in the upstream Debian repo [10:47:33] how is this managed upstream? each distro has a different debian/ branch? [10:52:47] there's no single scheme, but typically a master/latest branch for unstable and if needed (many applications never need a specific branch for an older suite) a separate buster branch [11:11:07] ok, so not something we can replicate without having to adjust the scripts each time we move the latest distro [11:11:27] I'm happy with any solution that is easily scriptable [11:19:41] volans: moritzm: i think lets go with -2, this seems the most scriptable further i just checked the content of and unstable instance's archive folder and i dont see any deb11u1 files which makes me think the unstable version shouldn't bother with the debNNu1? [11:22:37] * jbond42 imagines there are egecases im unaware of though [11:38:08] sounds good to me [11:39:01] ack thanks [15:45:28] XioNoX: you didn't init the pad yet for tomorrow? :-P [16:08:59] I don't have the proper algo to randomize the roundtable [16:10:30] lol, a super complicated one right?