=== pieq_ is now known as pieq [07:26] anybody knows why the hugepages package is not in focal anymore (https://bugs.launchpad.net/ubuntu/+source/libhugetlbfs/+bug/1873103)? [07:26] Launchpad bug 1873103 in libhugetlbfs (Ubuntu) "The hugepages package isn't available on Focal repos anymore" [Undecided,Confirmed] [07:29] Try libhugetlbfs-bin? [07:30] it is not found either [07:31] ah, wait, it should be there [07:34] thanks [07:34] Sure thing. === ricab_ is now known as ricab [09:56] huh maybe glib really is causing a regression here https://autopkgtest.ubuntu.com/packages/s/sbd/groovy/amd64 [09:58] doko: so gcc-10/binutils are next? but when can i do libffi? or shall we wait on response from upstream? [10:04] xnox: binutils 2.35 already is in groovy. gcc-10 is not related. which soname do you want to use? [10:05] doko: .so.8 and bash upstream to bump it to .so.9 if they break it between now and going forward. [10:06] doko: that is take current git snapshot and roll with it. [10:08] no, that would assume a decision on upstream. either don't bump the soname, and change the package name to libffi7-1, or bump it to 80, and change the package name to libffi80 === M_hc[m] is now known as _hc [10:58] mwhudson, could be really buggy but it seems it has been forced hinted now... [10:58] whoops, I hinted and then unhinted it, guess I was too late with that [10:59] but there was another retry since which also failed, sooooo [12:48] doko: but upstream master has bumped soname [12:49] doko: so their master is 8, and package name should be libffi8. I guess i want it to be explicit, so should email them. [12:54] rbasak: hi, I have a packaging question [12:54] rbasak: when adding a d/.maintscript file to a package that has, let's say, just d/postinst [12:55] but not the other d/postrm, d/prerm, etc files [12:55] I suppose I have to add them with the #DEBHELPER# marker, so that dpkg-maintscript-helper can do its job? [12:55] IIRC, you don't. [12:55] debhelper will create the ones that don't exist [12:55] xnox: it's not a release, you don't know if it will change until the release [12:55] Easy enough to verify in the built deb, but I'm pretty sure [12:56] rbasak: hm, create when? At build time, and ship in the binary? [12:56] At build time, into the binary - without changing the source [12:58] thanks, I'll verify === Eighth_Doctor is now known as Conan_Kudo === Conan_Kudo is now known as Eighth_Doctor [13:12] ahasenack: postinst will be installed into the main package regardless of whether it has a #DEBHELPER# marker or not. [13:12] xnox: postinst is fine, I was wondering about the others that dpkg-maintscript-helper would need to touch, if they don't exist in the source package [13:12] ahasenack: for example people omit that marker on purpose, to prevent from debhelper injecting its snippets, because they are too large / have deps not avialable / are borken / etc. [13:13] ahasenack: if you create .maintscript it's enough, it is smart. [13:13] nice [13:13] You definitely don't need to add empty files with #DEBHELPER# markers, indeed. [13:13] (Otherwise-empty, I mean) [13:13] that's what I was wondering about, if I had to add the "template" files with #DEBHELPER# [13:13] ahasenack: note that postinst is _an override_ / complete replacement. [13:13] ahasenack: and #DEBHELPER# is like "but yeah, please ressurect the stock snippets" [13:14] ahasenack: This is documented in debhelper(7) - please read [13:14] and put them on this line please. [13:14] "Automatic generation of Debian install scripts" [13:15] "If a script does not exist at all and debhelper needs to add something to it, then debhelper will create the complete script." <-- that settles it, thanks === alan_g_ is now known as alan_g [23:47] dpkg-source: warning: source directory 'pam' is not - 'pam-1.1.8' [23:47] * mwhudson stares [23:51] uh pam really is a native package in bionic?