[07:53] <Mirv> thanks LocutusOfBorg for vlc 3.0 in bionic :)
[08:17] <Skuggen>  Will bionic generate dbgsym packages automatically?
[08:21] <Unit193> Uhh, Ubuntu has been doing that since about edgy.
[08:21] <Unit193> So, yes.  Bionic will too.
[08:27] <Skuggen> I mean debhelper, for third-party builds, not what Ubuntu's build hosts do
[08:27] <Skuggen> i.e. What Debian Stretch does that Debian Jessie did not
[08:28] <Unit193> Using debhelper rather than pkg-create-dbgsym?  Yes that's already been changed, though I doubt it matters for the resulting dbgsym package.
[08:30] <Unit193> ...OK, I need to read better.  Sorry, yes.  This can already be done and has been for a little while (though in the past you could install that package.)
[08:38] <LocutusOfBorg> Mirv, you are welcome :) I'm sad for the missing chromecast support
[08:46] <Unit193> ricotz: Out of curiosity, do you do anything or know of anything done with libdvdcss?  I saw it in pkg-multimedia a bit ago.
[08:50] <ricotz> Unit193, I don't think it qualifies to be uploaded in the official archives
[08:50] <Unit193> Correct, it does not.
[08:51] <didrocks> xnox: I have a small ubiquity question once you are around: does the "recursive" property of record_removed() will remove all unused rdepends or just depends ? (It sounds like get_remove_list() only does cache._depcache.broken)
[08:52] <didrocks> xnox: and there is no apt autoremove at the end of the installation, correct?
[08:55] <Skuggen> Unit193: Thanks, what I mean is just whether dbgsym-files would automatically be created when running debuild. We (upstream MySQL) made some packaging changes for non-Stretch to replicate its behavior, and I noticed lintian is complaining about it in Bionic. We never used pkg-create-dbgsym (since as far as I know it's Ubuntu-specific)
[09:01] <Unit193> Skuggen: Yes, dbgsym packages as created by debhelper are default, like in Debian.
[09:02] <Skuggen> Thanks (just means we have to drop that change from the upstream 18.04 packages) :)
[09:03] <Unit193> Skuggen: Note that Ubuntu's will have a *.ddeb extension though.
[09:04] <Unit193> https://patches.ubuntu.com/d/debhelper/debhelper_11.1.4ubuntu1.patch that's the difference between debhelper in Debian and Ubuntu, pretty minimal now.  Not sure why we exclude changelogs though.
[09:05] <Skuggen> Unit193: Ah, that might actually matter, since our systems might just handle *.deb, thanks
[10:12] <doko> jamespage: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg   what have both python-libnacl and python-nacl?
[10:13] <jamespage> doko: you might be asking the wrong person about that bit
[10:13]  * jamespage looks
[10:15] <jamespage> but I agree having both seems a little silly
[10:15] <doko> hmm, no they seem to be something different
[10:17] <doko> roaksoax: ^^^
[11:05] <mvo> xnox: do you mind if I upload http://paste.ubuntu.com/p/vR7hNwZSkt/ to bionic? this fixes an issue we have with snapd caused by a dbus/apparmor mediation change (cc jdstrand, feel free to weight in here)
[11:34] <xeon_kyo> hi all i need a bit help about writing bash , does somebody know bash writing here?
[11:42] <juliank> xeon_kyo: I suggest you ask in #bash, this channel is about developing ubuntu
[11:44] <juliank> unless of course, it's an Ubuntu-specific bash question
[13:03] <mdeslaur> sil2100: do you have an exim4 merge planned soon?
[13:26] <mdeslaur> xnox: FYI, I'm switching clamav to 0.99.3 final
[13:45] <juliank> Did anyone hear something about s2disk (or rather, resume) breaking in a recent xenial update?
[13:47] <mdeslaur> juliank: the reverted intel microcode update was causing S3 problems
[13:50] <juliank> mdeslaur: I don't think there even are any microcode updates for Core i*-3* yet
[13:52] <juliank> latest updates were today
[13:52] <juliank> will do some more investigation
[14:27] <roaksoax> doko: TBH, no idea as i've not looked at what the differences are, but will take a look
[14:38] <doko> roaksoax: maybe you could ask cjwatson about the differences in python-nacl and python-libnacl, he is one of the Debian uploaders
[14:39] <roaksoax> doko: that's what I waas planning on doing :)
[14:42] <cjwatson> different upstream projects with incompatible APIs
[14:43] <cjwatson> more or less similar functions
[14:43] <cjwatson> but AIUI switching from one to the other is basically a rewrite
[14:44] <cjwatson> not my fault :P
[14:44] <jdstrand> xnox (cc mvo and tyhicks): +1 for the systemd change. fyi, tyhicks and I are going to revisit the upstream dbus changes so there is a possibility at some point we can drop this later in the cycle, but that all depends on what happens with upstream dbus
[14:54] <michagogo> Hey, can someone help me understand something? I'm trying to see if I can backport mingw-w64 from bionic (or artful?) to xenial, since the xenial version is badly broken
[14:55] <michagogo> Trying just a plain `backportpackage` into a PPA didn't really work, all kinds of dependency issues
[14:56] <raanst> michagogo what kind of dependency mingw-w64 want?
[14:56] <michagogo> One sec, let me look again
[14:57] <michagogo> Actually, mingw-w64 worked fine, but gcc-mingw-w64 wanted binutils-mingw-w64. I tried to `backportpackage` that, and it failed because it needed binutils
[14:58] <michagogo> When I tried binutils, it failed with this error: https://www.irccloud.com/pastebin/dFgEDKXz/
[14:58] <michagogo> In addition, gcc-mingw-w64 wanted gcc-7
[14:58] <raanst> Maybe it's stupid, but why You have computer date at 1999?
[14:59] <michagogo> Eh? I don't.
[14:59] <michagogo> I'm not Christopher, either.
[14:59] <raanst> dpkg-genchanges: warning:     debian/changelog(l7258): cannot parse non-comformant date '18 Sept 1999 01:21:05 -0400'
[14:59] <raanst> Okay, nevermid
[14:59] <raanst> nevermind
[15:00] <raanst> Are You try install binutils from tar.gz file?
[15:01] <michagogo> All I used was `backportpackage`. That was the command that failed with that error I pasted above.
[15:04] <cjwatson> you might just need to edit the changelog manually then and rerun that dpkg-buildpackage command
[15:05] <cjwatson> or run it with a different -v argument
[15:06] <michagogo> cjwatson: How do I do that? I have ~no experience with Ubuntu packaging
[15:07] <cjwatson> this will probably be too difficult a task then
[15:07] <michagogo> I'm not even sure if what I'm doing makes sense, or if I'm leading myself on a wild goose chase by trying to just `backportpackage` anything it says is missing
[15:07] <cjwatson> the changelog is in debian/changelog, and the dpkg-buildpackage command was in your paste (run in the temporary directory that backportpackage created)
[15:08] <michagogo> Maybe it's just a matter of editing the original gcc-mingw-w64 package to call for an older version or something?
[15:08] <cjwatson> you are probably in for a bad time in backporting a bunch of toolchain packages with no packaging experience, but OTOH there's probably little alternative if you want to backport mingw-w64, so ...
[15:08] <michagogo> Is it just that I don't have experience? Meaning, would it be particularly hard/complex for someone who does know what they're doing?
[15:09] <cjwatson> a toolchain backport is always a bit of an unknown quantity
[15:09] <cjwatson> it might just be this one changelog bump in the road, or it might be a task that requires intimate understanding of binutils ...
[15:10] <michagogo> Hmm. I was hoping that it might be simpler because it's not something that's used on the system itself, but rather just for cross-compiling
[15:10] <michagogo> But OTOH maybe that's completely misguided
[15:10] <cjwatson> you could certainly start by just fixing the changelog syntax and building the source package with that, but I have no idea how many other complexities there'll be
[15:10] <cjwatson> and you WILL have to be prepared to do some research for yourself (e.g. looking up how to edit a changelog is going to be one of your easiest tasks here)
[15:10] <michagogo> My end goal here is that I'm trying to find a way to allow people to build Bitcoin Core on Xenial
[15:11] <michagogo> Right now, the build docs say to edit the apt sources file to pull from the... zesty, I think? repository and apt-get upgrade
[15:11] <michagogo> And I know enough to know that that's... inadvisable
[15:12] <cjwatson> a chroot would no doubt be possible
[15:12] <michagogo> Last I heard, chroot wasn't implemented in WSL...
[15:14] <cjwatson> cryptocurrencies and WSL are two things I know little about and am not interested in learning, so good luck :)
[15:14] <michagogo> And in any case, I fear that may be too complicated
[15:14] <michagogo> I mean, we already have gitian for building in a VM/LXC container
[15:14] <michagogo> Heh, no need to learn about cryptocurrencies :-P
[15:15] <michagogo> You can replace 'Bitcoin Core' with 'Some arbitrary package that fails to build with the Xenial version of g++-mingw-w64'
[15:16] <michagogo> (Which, actually, _might_ actually be "all software" - I don't remember exactly what the problem was, but I think it was something pretty fundamental...)
[15:38] <michagogo> Does anyone know if there's a general guide somewhere to backporting packages that do need to be changed and can't just be built as-is? Even a step-by-step explanation of what `backportpackage` actually does, so I can read and learn what the steps are, and figure out where to step in and change things?
[15:39] <michagogo> I'm hoping (perhaps in vain?) that if I just change the dependencies to the GCC that's in Xenial it might work
[15:48] <rbasak> michagogo: backportpackage is a pretty small script
[15:48] <rbasak> I don't think it does much apart from tweak the changelog for you.
[15:49] <michagogo> Yeah, I saw. It would be nice if it were in bash
[15:49] <michagogo> But I see that it's all python using various libraries
[15:49] <rbasak> No thanks. Doing it in bash would be a little insane IMHO.
[15:50] <michagogo> Yeah, I didn't mean that I think the script should be in bash
[15:50] <michagogo> I assume that the process can be accomplished using a series of commands
[15:50] <michagogo> Hm
[15:50] <michagogo> Maybe I'll just throw pdb in there>
[15:50] <rbasak> Still, you'd have manipulate version string components.
[15:51] <rbasak> You'd end up writing a tool to do the manipulation and call that from bash.
[15:51] <rbasak> And we have that tool already - it's called backportpackage :)
[15:51] <michagogo> rbasak: Yeah, the thing is right now I'm trying to do a non-no-change backport
[15:52] <rbasak> michagogo: you know about debdiff, right? Run backportpackage, see what it did with debdiff, then throw away backportpackage and handle the changes you need manually.
[15:52] <michagogo> And I didn't see a flag to backportpackage that says "give me the opportunity to change something"
[15:52] <michagogo> Debdiff?
[15:52] <rbasak> http://manpages.ubuntu.com/manpages/xenial/en/man1/debdiff.1.html
[15:52] <michagogo> The thing is, I have ~no Ubuntu packaging experience
[15:52] <rbasak> Run it against two dsc files.
[15:53] <cjwatson> backportpackage leaves its stuff around in a temporary directory
[15:53] <cjwatson> you can go and edit it if you like
[15:53] <michagogo> To me, right now, backportpackage is pretty much a black box, with the end result being that the package ends up in the PPA
[15:53] <cjwatson> and then build the source package and upload it to the PPA manually
[15:54] <cjwatson> it writes the dpkg-buildpackage command it uses to build the source package to its output, so you can copy and paste that
[15:54] <rbasak> OK, so here are some pieces that I think you should learn: 1) how to get from an unpacked debian source tree to debian source package files (dsc, debian.tar.gz, changes).
[15:54] <rbasak> 2) how to unpack debian source package files into a directory
[15:55] <rbasak> 3) how to build from debian source package files a set of debs locally.
[15:55] <rbasak> 4) how to compare changes
[15:55] <rbasak> 5) how to upload to a PPA
[15:55] <rbasak> Once you've got that you should generally know what questions you need to ask I think.
[15:56] <cjwatson> rbasak speaks wisdom.
[15:56] <rbasak> Quick lookup: 1) dpkg-buildpackage; 2) dpkg-source -x; 3) sbuild (and mk-sbuild); 4) debdiff; 5) dput
[15:57] <rbasak> There are details and nuances with all of that and I have made some deliberate mistakes there in the interest of my summary
[15:58] <rbasak> But hopefully that's enough to get you started so you know what docs to look up
[15:59] <rbasak> After you've got to grips with those, you should see that backporting is really just a case of grabbing a source package and changing it as needed (just debian/changelog for a no-change backport, and more for other changes as needed) and uploading it again.
[16:00] <cjwatson> pull-lp-source is worth knowing about too.
[16:00] <rbasak> FWIW, nacc and I are working on a tool that makes all of this much easier, but I'm not sure I'd recommend newcomers to using it yet, because there are still many rough edges
[16:00] <rbasak> +1
[16:01] <cjwatson> all of these things have fairly decent man pages, plus https://wiki.ubuntu.com/SimpleSbuild and https://help.launchpad.net/Packaging/PPA
[16:03]  * juliank really wants lxd sbuild
[16:04] <rbasak> juliank: "git ubuntu build" roughly works and does it in lxd.
[16:04] <juliank> I have two options: Fix the autopkgtest backend to actually work, or write a separate lxd backend. I think the latter is easier, I already have a docker backend :)
[16:04] <juliank> rbasak: well, yeah, but it's not sbuild :D
[16:05] <rbasak> I don't think we're ever going to match feature parity with sbuild. Like you say, adding a lxd backend to sbuild would be better I think.
[16:05] <juliank> rbasak: and well, most stuff is not in git-ubuntu repos
[16:05] <rbasak> juliank: we're working on fixing that :)
[16:05] <juliank> rbasak: In theory, sbuild should be able to use lxd via it's autopkgtest virt-server integration. In practice, it just hangs or fails with weird errors.
[16:05] <rbasak> juliank: OOI (not that we're going to implement them), what does sbuild have that you would miss the most with git ubuntu build?
[16:06] <juliank> I'm not sure I'm missing something specific.
[16:06] <juliank> But I'd also like to use sbuild for debian builds and stuff
[16:07] <juliank> and being as close to a build server as possible is a bonus there
[16:07] <juliank> I think LP also uses _some_ sbuild
[16:10] <cjwatson> LP uses stock sbuild
[16:11] <cjwatson> only a few modifications these days and they're all wrapped around the standard package; see lp:launchpad-buildd, lpbuildd/binarypackage.py and sbuildrc
[16:12] <cjwatson> well, and bin/sbuild-package
[16:12] <juliank> the chroot is managed outside of sbuild in launchpad though AFAICT from build logs
[16:13] <rbasak> I didn't think sbuild managed its own chroots anyway?
[16:13] <rbasak> mk-sbuild isn't in the sbuild package for example
[16:13] <rbasak> (although sbuild-update is)
[16:14] <juliank> well, it has backends for chroot-like things
[16:14] <juliank> _normally_ it's used with schroot
[16:14] <rbasak> Oh, I see. That sense of "manage" :)
[16:14] <juliank> there are schroot, sudo, and autopkgtest backends
[16:14] <juliank> I guess LP uses the sudo one then
[16:15] <juliank> I also have a docker one, and am thinking about writing a lxd one
[16:15] <juliank> the docker is prototype-y, though
[16:15] <jbicha> there's also a sbuild-launchpad-chroot package that is useful
[16:16] <juliank> I don't want to build in chroots, because they are crazy insecure
[16:17] <michagogo> What does it mean when the Build-Depends line contains e.g. "mingw-w64-i686-dev <!stage1>"? I tried looking for the dsc file syntax, but a couple pages I saw didn't say anything about the <!stage1> part of the syntax
[16:19] <juliank> michagogo: these are build profiles, for bootstrapping new architectures
[16:19] <juliank> so you can have a stage1 with the least features compiled in, then a stage2 with more, ...
[16:19] <juliank> in order to resolve cycles
[16:19] <michagogo> Oh, for cases of circular dependencies etc.?
[16:19] <michagogo> I see.
[16:24] <michagogo> Now I'm confused about the version numbers of gcc-mingw-w64
[16:25] <michagogo> They're numbers like 17, 19.3, 20.2
[16:25] <michagogo> Those don't look like software version numbers
[16:25] <juliank> why not?
[16:26] <juliank> have you seen systemd's version?
[16:26] <michagogo> I mean, they don't look like they're version numbers for MinGW, which is at 5.0.3
[16:26] <juliank> right
[16:26] <michagogo> Or GCC, which is at 7.x.x (or 6.x.x or 5.x.x or whatever)
[16:26] <cjwatson> juliank: no, LP uses the schroot backend
[16:26] <juliank> cjwatson: interesting
[16:26] <michagogo> Now I'm starting to think I may not actually understand what the gcc-mingw-w64 package is...
[16:26] <juliank> michagogo: The binaries have a different version number.
[16:27] <juliank> michagogo: So, the gcc-mingw-w64 package probably build-depends on gcc-source and compiles gccs from that
[16:27] <cjwatson> juliank: The main oddity is that we use schroot type=plain and do the setup/teardown ourselves
[16:27] <juliank> and then it generates packages like gcc-mingw-w64 with versions like 7.2.0-20ubuntu1+20.2
[16:28] <cjwatson> juliank: But then the actual entry to the chroot is done using schroot (which means we get its ability to reliably kill a session, which sbuild's sudo mode couldn't do)
[16:30] <michagogo> Hm... so if it build-depended on, say, gcc-5-source rather than gcc-7-source, it would produce GCC 5 binaries, with the newer MinGW code?
[16:30] <michagogo> Dammit, I think this is turning into "Micha doesn't understand the relationship between GCC and mingw-w64"
[16:31] <cjwatson> The way I would answer that question would be by going to https://tracker.debian.org/mingw-w64, which links to https://anonscm.debian.org/cgit/collab-maint/mingw-w64.git, grabbing that git tree locally, and then looking back through its history to see if the Build-Depends change to gcc-7-source was accompanied by any other changes
[16:33] <cjwatson> That sort of approach is usually a good strategy for "help, I need to unwind this complicated new build-dependency for a backport, but I have no idea what else I might need to unwind at the same time"
[16:33] <michagogo> cjwatson: the Build-Depends on gcc-7-source is in gcc-mingw-w64, not in mingw-w64
[16:33] <rbasak> michagogo: gcc-mingw-w64? Sounds like you're diving in at the very deep end there.
[16:34] <rbasak> michagogo: I would step back and consider your approach. I don't know what problem you're solving, but there might be an easier way.
[16:34] <michagogo> Yeah, I'm thinking more and more that I'm looking at something much more complex than I hoped
[16:35] <michagogo> My starting point is this
[16:35] <michagogo> The version of mingw-w64 (or maybe it's g++-mingw-w64? I don't think I understand well enough how the different projects interact) in xenial is very broken
[16:36] <cjwatson> michagogo: ok, substitute the starting URL accordingly then
[16:37] <michagogo> It produces binaries that don't work, Leading to a certain project having instructions in the build guide to change apt sources in a xenial environment to point to the zesty repos and upgrade
[16:37] <michagogo> Which, if I'm not mistaken, is a very effective way to hose your environment.
[16:38] <rbasak> Zesty is EOL now.
[16:38] <rbasak> But you can usually fire up a lxd container and use a newer release to run a build just fine.
[16:38] <rbasak> No need to hose the host system.
[16:39] <michagogo> The build process for releases just uses a Trusty container to get around that issue, but it's desirable to have a way to build without all that
[16:39] <rbasak> Also, if the reason it doesn't work in Xenial is due to a bug, we're quite happy in general to cherry-pick the fix for all Xenial users to benefit.
[16:40] <michagogo> (One example being Windows users, who want to use WSL, which doesn't have containers or chroot afaik)
[16:40] <rbasak> Can they not use WSL with a different Ubuntu release?
[16:51] <Odd_Bloke> rbasak: We only provide xenial WSL images.
[16:51] <Odd_Bloke> You can upgrade the environment, but then you're on your own.
[16:52] <michagogo> AFAIK you're not given a choice as to which version to download
[16:52] <rbasak> Ah, OK
[16:53] <michagogo> And ISTR that do-release-upgrading breaks things
[16:56] <mvo> slangasek: hey, who should I talk to about a systemd fix? I have a debdiff ready (http://paste.ubuntu.com/p/W2w883BFgR/) and would love feedback if its ok to upload or if I should follow a different process (PR or somesuch)
[16:59] <nacc> mvo: i'm told elsewhwere that slangasek is away today and tmrw
[17:00] <mvo> nacc: aha, thank you
[17:02] <nacc> mvo: np, i wonder if xnox is around (although late for him)
[17:04] <juliank> nacc: it's earlier for xnox than for mvo :D
[17:04] <juliank> but I have not seen him
[17:05] <juliank> that said, a lot of people do not respond on IRC today :)
[17:06] <juliank> mvo: I would not do anything with systemd right now. it's stuck in the cryptsetup transition with test failures
[17:06] <juliank> I think xnox wanted to investigate them
[17:08] <mvo> juliank: ok, thank you
[17:13] <nacc> juliank: :) i never know anymore
[17:29] <michagogo> I think I’m probably not going to keep pursuing this right now, but:
[17:29] <michagogo> That stage1 stuff in the build-depends that we talked about earlier, is that also relevant for PPAs?
[17:30] <michagogo> Meaning, if I wanted to upload packages with circular dependencies to a PPA, would that work
[17:30] <michagogo> ?
[17:30] <nacc> michagogo: i believe PPAs don't have build-profiles exposed
[17:31] <nacc> michagogo: so you can't do the bootstrap in a PPA, except by hand (e.g., drop the stuff you don't need to get pkg1 built, then build pkg2, then rebuild pkg1 re-adding what you dropped)
[17:32] <cjwatson> That's correct.  It's a feature that might be worth adding in the feuture.
[17:32] <cjwatson> *future
[17:33] <juliank> cjwatson: what was that?
[17:33] <cjwatson> the ability to configure a PPA to build with certain build profiles
[17:34] <juliank> um, yeah, I meant the <DEL> character
[17:34] <cjwatson> err, dunno, something lag-induced
[17:34] <juliank> cjwatson: did you restart ddeb-retriever or did it finish?
[17:35] <juliank> in any case, we do have bionic-updates now :)
[17:44] <cjwatson> I didn't touch it except to deploy your change; I think it finished
[17:45] <juliank> Ah I guess it did not get yakkety,viid,zesty back from LP and hence did not regenerate them or something
[17:46] <juliank> I'm always amazed at how easy some things are too fix
[17:47] <tsimonq2> build-profiles in PPAs> That would be SUPER useful for Qt transitions.
[17:50] <juliank> tsimonq2: ooi how do you use build profiles for qt transitions?
[17:51] <tsimonq2> juliank: The base Qt packages have circular dependencies with the doc packages. If we had access to build with specific profiles, we'd go with nodoc for the first run and then from there unset nodoc and rebuild the packages one more time.
[17:52] <xevious> nacc: How's phpunit coming along? Is there anything I can help out with for php-defaults while you're working on that?
[17:53] <nacc> xevious: just working on monolog and then it should be good
[17:53] <nacc> xevious: if you can look to see any of them need retriggers, (e.g., the packag that was tested has already been updated in bionic-proposed or bionic), that would be helpful. Or if any need an update from Debian.
[17:53] <nacc> that's usually my first step
[17:54] <xevious> Yeah I can do that.
[17:54] <nacc> xevious: thanks, just ping me with what you find
[17:55] <juliank> tsimonq2: interesting
[18:39] <michagogo> rbasak/juliank/cjwatson: Thanks for your help. I also discussed the issue a bit with people who have a bit more understanding and think I have a slightly better idea of this whole story. I think I'm going to drop the issue for now, since I don't think I have enough time to learn enough about the various topics involved and get into it. On the horizon for Bitcoin Core specifically, we want our build tooling to optionally create and use its
[18:39] <michagogo> own toolchain, in order to be independent of Ubuntu (and other distro) packaging-related issues like this.
[18:40] <michagogo> Maybe at some point in the future I'll look into it again as a learning opportunity...
[18:40] <michagogo> And I mean, in the meantime mingw-w64 is broken for everyone, it's not just us, but...  🤷🏽‍♂️
[18:48] <jbicha> juliank: did you see LP: #1747033 ?
[18:49] <juliank> jbicha: Oh, well, the package is in the wrong section
[18:49] <juliank> it needs to be in oldlibs
[18:49] <jbicha> juliank: is that the only problem there?
[18:50] <juliank> jbicha: yeah, if its in oldlibs, gnome-tweak-tool becomes autoremovable, and gnome-tweaks gets the bit gnome-tweak-tool had before
[18:50] <jbicha> if so I'll reassign to gnome-tweaks and look for an AA to help
[18:51] <juliank> jbicha: Sorry I was confused last time I looked at it
[18:51] <juliank> and then I forgot about it
[18:52] <juliank> magic!
[20:01] <mdeslaur> infinity, kees, stgraber, slangasek: TB meeting?
[21:52] <xevious> nacc: Caught up with tickets. Got about 30% done writing a script to check for things needing retriggers.
[21:53] <nacc> xevious: nice :)
[21:54] <xevious> I'm getting back to that now.
[22:07] <Unit193> Debian #890287, #890288.  Fun.
[23:03] <nacc> xevious: once php-monolog (just uploaded) is published, I can retrigger phpunit's tests and should be able to pick up wherever you are on php-defaults
[23:10] <powersj> nacc: Is this still the best guide for git-ubuntu + workflow? https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow
[23:11] <xevious> nacc: I've been juggling a number of things today. I should have that script shortly. I'll drop it in a snippet or gist or something when it's ready.
[23:11] <xevious> nacc: Can I PM you to confirm some details?
[23:12] <nacc> xevious: ack
[23:12] <nacc> powersj: the manpages of the snap are probably a bit better
[23:12] <nacc> to enable them, LP: #1699526
[23:13] <nacc> powersj: (although i believe that i need to revisit that with some upstream changes recently in snapd)
[23:15] <powersj> nacc: thx!
[23:16] <nacc> powersj: np, i think the merge manpage is basically that wiki page still, but it's supposed to be the place to go
[23:16] <nacc> powersj: also use the beta snap
[23:18] <powersj> ah was on edge
[23:18] <nacc> powersj: edge would be fine
[23:18] <nacc> just a bit less stable :)
[23:18] <nacc> edge should be ok (I thikn that's what i am using)
[23:18] <nacc> note that some repos are currentlly ... in flux :)
[23:18] <nacc> because of our importer changes
[23:19] <nacc> powersj: if you hit issues, let me know, i can walk you through how to workaround them
[23:19] <powersj> nacc: ok thanks again
[23:19] <nacc> np
[23:38] <nacc> xevious: retriggering php-monolog now
[23:38] <xevious> Great.
[23:39] <nacc> xevious: i *think* that will also get a bunch of stuff in php-defaults through
[23:39] <nacc> because it's all the phpunit entangled packages that cause those mismatches
[23:50] <nacc> xevious: cacti just got fixed in debian, it *should* sync down once it builds/publishes there
[23:50] <xevious> Great.
[23:50] <xevious> How long does that usually take?
[23:50] <nacc> hopefully it will be done or in progress when i wake up trmw
[23:51] <nacc> *tmrw*
[23:51] <nacc> xevious: since you're still collecting data on php-defaults, i might try and get php-horde-test through, since that will unblock the rest of horde probably
[23:51] <xevious> Ok. I'm about to publish a gist with the script and the current results.
[23:52] <nacc> xevious: thanks
[23:57] <xevious> nacc: https://gist.github.com/iammattcoleman/88013cb5f92105b15a66ee2ada442a16