=== pieq_ is now known as pieq === ricab is now known as ricab|lunch === ricab|lunch is now known as ricab === Wryhder is now known as Lucas_Gray [15:32] Unit193, did I smell debhelper backport? [15:32] I think we should do it! :) [15:32] care to open a bug against debhelper? happy to discuss/sponsor, we really need compat level 12 for bionic, now that Debian is widely using it [17:02] LocutusOfBorg: I don't see how it follows that Debian using 12 in unstable means our stable release needs it. [18:48] infinity, because some developers are using bionic as their base os... [18:48] and you can't even create a dsc or changes without the required compat 12... [18:48] so, not even able to create something to upload in a ppa or pbuilder [18:48] I manually backported it in my laptop, but still, I need it for e.g. backbox ppa and somewhere else [18:49] and when many people need the same thing, for different reasons... maybe an SRU is worth [19:26] LocutusOfBorg: Wat? [19:27] LocutusOfBorg: You don't need debehlper at all, regardless of version, to create a "dsc or changes". [19:27] LocutusOfBorg: If you're running full no-op clean targets on source builds, those should always be done in target chroots. If you're not, you need no debhelper. [19:30] LocutusOfBorg: Anyhow, "I can't figure out how to develop for the devel release" is never a reason to backport the devel toolchain to stables. (using your argument, DDs that don't Debian stable should be petitioning for debhelper 12 in stretch, and I'm assuming you don't think that's a good idea) [19:40] LocutusOfBorg: There are a lot of options for you: (1) use a devel lxd (2) upgrade to devel (3) build source package with -nc [19:41] Oh, infinity I think it did get harder to build without a debhelper due to Build-Depends: dh-compat (= 12) [19:41] but I'm not sure [19:41] no, -nc ignores b-d too [19:41] So ignore that bit, I was stupid [19:42] I usually build packages for releases like this [19:42] lxc exec $release -- sudo -i -u ubuntu bash -c "cd $PWD && -S -uc -us" [19:42] and then debsign on the host [19:42] and have $HOME mounted into $release container [19:43] Well, mostly applies to apt/xenial [19:45] I try building on host (which runs devel), and then do debdiff of .dsc for non-devel upload to see if there are any spurious changes [19:59] juliank: Yeah, I do all my builds -nc where I know it's safe, and if it's not safe, it's because the package does Weird Stuff in clean, in which case it should be in a target chroot anyway (so as to not skew autotools versions, etc), so... [20:27] hm, question about the d/.symbols file. Ubuntu backported a certain feature, which added new symbols, and added them to the symbols file [20:27] at the version of the backported package: 1.5.7-2ubuntu1~ [20:28] later, debian adopted a new upstream version which had that feature, and updated its symbols file at that version: 1.6.2 [20:28] so the question is if we should keep setting it to 1.5.7-2ubuntu1~, which is when ubuntu introduced it [20:28] but that means keeping a delta with debian [20:29] I'm inclined to drop the delta [20:29] the 1.5.7 package will still have that versioned symbol, but now we are ahead [20:30] ahasenack: Dropping the delta is fine, just means that packages built against the new library will pick up a newer versioned dep if they use those symbols, which isn't a big deal. [20:32] ahasenack: The versioned dep will be a bit of a lie for Ubuntu, but we also don't actually want people running eoan binaries with bionic libraries (or whatever), so eh. [20:32] I will have to rebuild everyting, though [20:32] No you won't.. [20:32] Why would you? [20:32] or else the reverse-deps won't be installable? let me check what that dep looks like [20:33] Current deps will be >= 1.5.7-2ubuntu1~, and last I checked, 1.6.2 is bigger than 1.5.7 [20:33] right, it's >= [20:34] Things will organically pick up the higher dep as they're rebuilt for other reasons, but no need to force the issue. [20:34] cool, thanks === gusnan_ is now known as gusnan