| hagbard | How can i trigger a rebuild of a package to generate a +b1 or +b2, and would that even be necessary? | 21:10 |
|---|---|---|
| LeePen | Which src package? You need to look at the binary Debian changelog and see if their reason to binNMU is relevant to Devuan. | 21:31 |
| LeePen | ATM, most are 32bit arch 64bit time_t rebuilds. | 21:35 |
| hagbard | was wondering in general, and for fluidsynth in particular. Where do I find changelogs about binary rebuilds? Only found the the changelogs for source/packaging in various places so far. | 21:45 |
| LeePen | IIRC the debian buildd logs | 22:04 |
| LeePen | and in the rebuilt binary packages themselves | 22:04 |
| hagbard | thx, found it in the build logs. So seemingly nothing relevant then. +b1: "Rebuild to sync binNMU versions" +b2: "Rebuild for time_t" | 22:11 |
| LeePen | We will probably need the time_t rebuild. But Debian is so unstable at the moment, I am minded to wait. Do say if you think it is urgent and I will trigger it. | 22:15 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!