plasma41 | In the eudev git repository what's the difference between the 'suites/unstable' branch and the suite/ceres' branch? Should one be dropped in favor of the other and if so, which one is the recommended branch name to use? | 06:10 |
---|---|---|
rrq | should be suites/unstable I think | 06:19 |
rrq | yes. pretty sure. | 06:21 |
plasma41 | Should the 'suites/beowulf' branch of that repository be fast-forwarded to commit 1e7f1dfd54c841816d6f9160e90653a271c4c6b0? | 06:34 |
plasma41 | afk | 06:36 |
rrq | plasma41: the "procedure" is to build for suites/unstable and then "move" that in dak, rather than build for suites/beowulf ... | 07:47 |
rrq | i.e. basically all branches other than 'suites/unstable' are historical only | 07:47 |
rrq | well suites/experimental is also a build branch | 07:49 |
gnu_srs1 | FYI: I'm working on building an updated version of eudev for unstable, followed by a version for beowulf-proposed-updates. | 10:49 |
gnu_srs1 | Will be completed in the beginning of next week :) | 10:49 |
onefang | Enough playtime with my new super desktop, I'm happy with the performance. Time to install Beowulf on it. | 12:31 |
onefang | If we need it, I'll be happy to put some sort of Devuan build VMs on it later. | 12:32 |
bgstack15 | Alright team, what's the current standards-version for dpkg in Beowulf or Ascii? | 16:42 |
bgstack15 | Just off the top of your head. | 16:42 |
fsmithred | 1.18.25 500 | 16:58 |
fsmithred | 500 https://sledjhamr.org/devuan/merged ascii/main amd64 Packages | 16:58 |
fsmithred | 1.19.7 500 | 16:58 |
fsmithred | 500 http://sledjhamr.org/devuan/merged beowulf/main amd64 Packages | 16:58 |
fsmithred | oops. not what you asked for. | 16:59 |
fsmithred | ascii is 9 and beowulf is 10 | 17:00 |
fsmithred | is that the right number? | 17:00 |
fsmithred | bgstack15, https://www.debian.org/doc/debian-policy/upgrading-checklist.html | 17:06 |
bgstack15 | Thanks, those are the numbers I needed. The 9 and 10 are the debhelper-compat or debhelper versions which are not what I was seeking this time. | 17:10 |
LeePen | bgstack15: The Standards Version isn't absolutely linked to the release. So you can have current (4.5.0) in Beowulf or even ASCII. | 19:32 |
LeePen | Or perhaps you meant debhelper compat version? | 19:33 |
bgstack15 | I did mean the 4.5.0 number. | 19:34 |
bgstack15 | I thought it was directly related to debhelper-compat though. | 19:34 |
LeePen | I don't think so. Standards is a sort of consensus on good packaging practice. | 19:34 |
LeePen | Debhelper compat defines the way the dh tools actually handle the build. | 19:35 |
bgstack15 | Does debhelper (or more importantly, lintian) act differently based on the standards value? | 19:35 |
LeePen | If you comply with Standards 4.5.0 you can state that irrespective of debhelper | 19:36 |
LeePen | The only think I know that might emit a warning is lintian if it encounters | 19:36 |
LeePen | a newer Standards Version than it knows about. | 19:36 |
LeePen | I don't think either debhelper or lintian actually behave differently | 19:37 |
LeePen | based on the Standards Version. | 19:37 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!