[09:14] <mwhudson> tsimonq2: debian/patches?
[12:12] -queuebot:#ubuntu-release- Unapproved: network-manager-openconnect (bionic-proposed/universe) [1.2.4-1 => 1.2.4-1ubuntu1] (no packageset)
[16:41] -queuebot:#ubuntu-release- New binary: cpdb-libs [amd64] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:41] -queuebot:#ubuntu-release- New binary: cpdb-libs [s390x] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:41] -queuebot:#ubuntu-release- New binary: cpdb-libs [ppc64el] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:42] -queuebot:#ubuntu-release- New binary: cpdb-libs [armhf] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:43] -queuebot:#ubuntu-release- New binary: cpdb-libs [arm64] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:43] -queuebot:#ubuntu-release- New binary: cpdb-libs [i386] (cosmic-proposed/universe) [1.2.0-0ubuntu1] (no packageset)
[16:43] <tsimonq2> mwhudson: I need a config variable set in a native package via /etc/xdg/xdg-Lubuntu/lxqt/panel.conf
[16:43] <tsimonq2> It should be on the live system only.
[17:11] <tsimonq2> wxl: Heya.
[17:11] <wxl> o/
[17:12] <tsimonq2> wxl: You've read through https://wiki.ubuntu.com/ProposedMigration or at least skimmed it?
[17:12] <wxl> yep
[17:12] <tsimonq2> Cool.
[17:13] <tsimonq2> So, with transitions as big as ours, there's gotta be something failing an autopkgtest.
[17:13] <tsimonq2> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html has a full list, and you can access specific packages via http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src
[17:13] <wxl> well there's only one of 5 possibilites so you've got a 20% chance of being right :)
[17:14] <tsimonq2> hahahaha
[17:14] <tsimonq2> wxl: We want it to say "Valid candidate" at the bottom.
[17:14] <tsimonq2> From there, that part of the testing has passed, and then it goes to http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[17:15] <wxl> @tsimonq2: ignore the ignored failures i assume?
[17:15] <tsimonq2> wxl: Right.
[17:15] <tsimonq2> All of the "hints", or known failures, are available here: https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/files
[17:15] <tsimonq2> We
[17:15] <tsimonq2> grr
[17:16] <tsimonq2> We're trying to move it over to team files, such as "ubuntu-release" instead of e.g. "vorlon"
[17:16] <wxl> looks like there's a handful of always failed. shouldn't be too difficult
[17:17] <tsimonq2> wxl: So, if you know an autopkgtest is bad, you can either make an MP there or ask someone here.
[17:17] <tsimonq2> But right.
[17:17] <tsimonq2> *Usually* it's annotated with a comment.
[17:18] <tsimonq2> wxl: What isn't documented though, is there's an update_output.txt that's *before* all the tests are passed.
[17:18] <tsimonq2> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output_notest.txt
[17:18] <tsimonq2> So what I typically do, for e.g. Qt to migrate, is search for the first entry in the file for qtbase-opensource-src where it's grouped in with a bunch of other packages.
[17:19] <tsimonq2> From then on, it tries to separate it into different migratable chunks.
[17:20] <wxl> like the one that begins with qtserialport-opensource-src and ends with khangman?
[17:20] <tsimonq2> Right.
[17:20] <tsimonq2> So, with these, you can sometimes diff the listing in update_output.txt with the listing in update_output_notest.txt.
[17:21] <tsimonq2> Because the latter is with tests *not* considered.
[17:22] <tsimonq2> Either way, if you're in update_output.txt and the "got" stanza does not contain any other -proposed packages in it, you might want to try looking at Ben: https://people.canonical.com/~ubuntu-archive/transitions/
[17:22] <tsimonq2> Ben is a graphical representation of some of these transitions; I would encourage you to look into it.
[17:23] <tsimonq2> The trick is to try to make A) Ben happy for a transition. B) All autopkgtests passable. C) Make everything installable.
[17:23] <wxl> ok so let's work on an example. walk me through it step by step.
[17:24] <tsimonq2> So, that big one you mentioned before starting with qtserialport and ending with khangman.
[17:24] <wxl> ok
[17:24] <tsimonq2> The only reason why it can't all migrate now is because of these lines:
[17:24] <tsimonq2>     got: 32+0: a-3:a-2:a-4:i-2:p-19:s-2
[17:24] <tsimonq2>     * ppc64el: emacs25, emacs25-lucid, libsbml5-octave, octave-lhapdf, octave-ocs, octave-odepkg, octave-plplot, paraview, paraview-dev, paraview-python, performous, rbdoom3bfg, ring, ring-daemon, tupi, vcmi, vdr-plugin-softhddevice
[17:25] <tsimonq2> So, when these packages are installed, upgrading that whole stack shown in "trying" breaks all of these *somehow*.
[17:25] -queuebot:#ubuntu-release- New source: cpdb-backend-file (cosmic-proposed/primary) [1.0.0-0ubuntu1]
[17:25] <wxl> and it's only affecting ppc64el?
[17:26] <tsimonq2> It cycles through all of the architectures in every run.
[17:26] <tsimonq2> So this run it'll be ppc64el, next run should be s390x, etc.
[17:26] <wxl> oic
[17:27] <tsimonq2> In Ubuntu, unlike Debian, we don't split arch:all and amd64, so amd64 could(!) yield more results.
[17:27] <wxl> we need a vim plugin with custom folding
[17:27] <tsimonq2> Oh? :)
[17:27] <tsimonq2> I don't catch your drife.
[17:27] <tsimonq2> *drift
[17:27] <wxl> so you could fold away the lines that are irrelevant and focus only on the important bits
[17:27] <wxl> anyways carry on
[17:28] <tsimonq2> So, that's what is uninstallable. Often times within that you can find a dep tree.
[17:29] <tsimonq2> I personally scan Ben next to see if there's something that corresponds to any of these packages.
[17:29] <tsimonq2> https://people.canonical.com/~ubuntu-archive/transitions/
[17:30] <tsimonq2> I see Octave.
[17:31] <wxl> i'm with you
[17:31] <tsimonq2> Indeed: https://launchpad.net/ubuntu/+source/emacs25/25.2+1-6build2
[17:31] <tsimonq2> So the goal with all of these is to find source packages and what's wrong with them.
[17:31] <tsimonq2> That's a bit of a unique error, so I'll look into it.
[17:32] <tsimonq2> INFO Upload was rejected:
[17:32] <tsimonq2> INFO 	emacs25-lucid_25.2+1-6build2_amd64.deb: Version older than that in the archive. 25.2+1-6build2 <= 1:25.2+1-10
[17:32] <tsimonq2> INFO 	emacs25-nox_25.2+1-6build2_amd64.deb: Version older than that in the archive. 25.2+1-6build2 <= 1:25.2+1-10
[17:32] <tsimonq2> INFO 	emacs25_25.2+1-6build2_amd64.deb: Version older than that in the archive. 25.2+1-6build2 <= 1:25.2+1-10
[17:32] <wxl> what about octave?
[17:32] <tsimonq2> INFO Committing the transaction and any mails associated with this upload.
[17:32] <tsimonq2> Fun.
[17:32] <tsimonq2> wxl: Well, Ben needs to be looked at for that it seems.
[17:33] <acheronuk> emacs took over emacs25 package + friends
[17:33] <tsimonq2> acheronuk: Got it, so that probably needs AA processing if I'm not wrong?
[17:33] <acheronuk> [23:44] <slangasek> emacs needed a binary promotion (because emacs stole emacs25 source)
[17:34] <tsimonq2> Bingo.
[17:34] <tsimonq2> wxl: So, that's part of what's blocking it; an Archive Admin such as slangasek (there's a few more victims^Mpeople you can poke) needs to press buttons.
[17:34] <tsimonq2> Otherwise, I'll look at Octave.
[17:35] <wxl> let's find an "easy" one for me and i'll leave the hard ones for you
[17:35] <acheronuk> octave is not on the last update_output for i386
[17:35] <acheronuk> * i386: emacs25, emacs25-lucid, paraview, paraview-dev, paraview-python, performous, pfsglview, pfstools, pfsview, rbdoom3bfg, ring, ring-daemon, tupi, vcmi, vdr-plugin-softhddevice
[17:36] <tsimonq2> Hmm.
[17:36] <tsimonq2> Oh, I was looking at notest, hah.
[17:36] <tsimonq2> wxl: So, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#octave is an example of a package with failing tests.
[17:37] <tsimonq2> Since Debian started testing for those, you can usually(!) find a corresponding Debian bug.
[17:38] <tsimonq2> Looks like octave-ocs is not in Testing, so it might need a demotion: https://tracker.debian.org/pkg/octave-ocs
[17:38] <tsimonq2> (Demotion to -proposed.)
[17:39] <tsimonq2> wxl: This demonstrates the general point that this is a rabbit hole. :P
[17:39] <wxl> yes
[17:40] <wxl> and at this point i'm starting to wonder how i'm going to be helpful because it's going to take half the time to explain to me what it is i'm even looking at
[17:40] <tsimonq2> Once you learn what you're looking at, it's easy enough to understand what you're dealing with.
[17:41] <tsimonq2> wxl: If you want, I can continue to hunt the transition on my own, but it'd be cool if you could continue to stick around for the ride. :)
[17:41] <acheronuk> don't think we need octave for Qt though. normal output where it's not grouped due to the failing tests would migrate Qt without it
[17:41] <wxl> i'm here to help
[17:42] <tsimonq2> acheronuk: Right.
[17:43] <tsimonq2> Fixing https://launchpad.net/ubuntu/+source/ring/20180712.2.f3b87a6~ds1-1build1 is needed it seems.
[17:43]  * tsimonq2 hunts for upstream patches...
[17:45] -queuebot:#ubuntu-release- New source: cpdb-backend-file (cosmic-proposed/primary) [1.0.1-0ubuntu1]
[17:53] <wxl> so going back to octave.. it's passing in excuses, so i guess that's what you mean about the tests before the tests?
[17:53] <tsimonq2> Yeah, kinda.
[17:53] <tsimonq2> What our real concern right now is is ring.
[17:54] <tsimonq2> https://launchpad.net/ubuntu/+source/ring/20180712.2.f3b87a6~ds1-1build1
[17:54] <tsimonq2> The build passes in Debian but not in Ubuntu. I'm trying a fresh build locally.
[17:54] <tsimonq2> If it FTBFS in a fresh Sid chroot, I'll file a bug there and it'll be their problem. ;)
[17:57] <acheronuk> that may be so, but it's still OUR problem as it's blocking OUR transition
[17:58] <tsimonq2> You're not *wrong*. :P
[17:59] <acheronuk> I just mean more may be required from us than just 'passing the ball'
[18:00] <acheronuk> if we want our transition through this year!
[18:13] <tsimonq2> Oh, that's probably why.
[18:13] <tsimonq2> It's FTBFS with the new boost!
[18:13] <tsimonq2> grr
[18:15]  * tsimonq2 wonders why doko switched our default Boost to 1.67 while Debian's is still at 1.62...
[18:18] <tsimonq2> For these FTBFS packages, I'm going to switch the build dep to explicitly pull in 1.62 (even though it's in Universe, it's still default in Debian) and file bugs there that it FTBFS with 1.67... eventually once those are solved we should be able to sync.
[18:18] <tsimonq2> Because some of these don't even have patches upstream yet.
[18:22] <ginggs> tsimonq2: boost 1.65 was default for bionic, and debian didn't have that either
[18:22] <tsimonq2> ginggs: Ah, got it.
[18:23] <tsimonq2> ginggs: Where's the source package for 1.65? I can't seem to find it under the normal naming scheme.
[18:23] <ginggs> https://launchpad.net/ubuntu/+source/boost1.65.1
[18:23] <tsimonq2> ack
[18:24] <ginggs> apparently ftp-master weren't happy with debian/copyright in boost
[18:25] <tsimonq2> With which one?
[18:25] <ginggs> all of them
[18:27] <tsimonq2> Oh. :P
[18:30] <tsimonq2> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906690
[18:40] <tsimonq2> doko, xnox: Since Boost 1.67 was something you both were involved in, could you please solve the ring FTBFS? I don't know enough about Boost.
[18:54] <tsimonq2> Trying a new version of yaml-cpp from Debian's Git repo.
[18:57] <acheronuk> tsimonq2: missing include?
[18:57] <tsimonq2> acheronuk: New yaml-cpp drops depends on boost 😆
[18:58] <tsimonq2> acheronuk: So if this works, I call it a workaround. :P
[18:58] <tsimonq2> It doesn't help that the maintainer is MIA though.
[18:58] <wxl> can we easily get a list of all the ones that require boost?
[18:59] <tsimonq2> What do you mean?
[19:02] <wxl> well we have could generate a list of potentially problematic packages, then iterate through them checking to see if they have depends on boost
[19:04] <tsimonq2> wxl: Right, that's just grepping excuses :)
[19:04] <tsimonq2> Aww, yaml-cpp is FTBFS :(
[19:51] <tsimonq2> There, I'm thinking that yaml-cpp upload will fix it.
[19:51] <tsimonq2> We shall see......
[19:56] <tsimonq2> slangasek: Could you please demote vdr-plugin-softhddevice to cosmic-proposed? There's been an open bug in Debian since January about fixing support with ffmpeg, which hasn't been solved. Debian bug 888331.
[20:13] <tsimonq2> NICE, yaml-cpp does fix it.
[20:14] <LocutusOfBorg> slangasek, it turned out to be relatively simple to do, and fixing a build failure gave me 12 hours of "good work" in fixing what was left to do, instead of seeing aways the same useless stuff in update_output... so not entirely a waste of time
[20:14] <LocutusOfBorg> :)
[20:23] <tsimonq2> wxl: A good challenge is to find yaml-cpp rdeps with `reverse-depends [-b]` and give me a list to retry :)
[20:25] <LocutusOfBorg> paraview... anybody has hints?
[20:25] <LocutusOfBorg> I rebuilt the last two xorg packages
[20:25] <tsimonq2> I was looking at that and couldn't quite figure it out.
[20:25] <LocutusOfBorg> we probably missed them because they are arch:arm* only
[20:25] <LocutusOfBorg> I even tried a build with no-parallel...
[20:25] <tsimonq2> LocutusOfBorg: Tag team you in? :) I will be mostly AFK for the next 6 hours.
[20:25] <LocutusOfBorg> nothing changes
[20:26] <LocutusOfBorg> tsimonq2, paraview FTBFS in debian too
[20:26] <LocutusOfBorg> so you can open an RC bug there
[20:26] <tsimonq2> ack
[20:26] <tsimonq2> I can do that later unless you want to now.
[20:26] <LocutusOfBorg> I can give you a link to build log
[20:26] <tsimonq2> Please do, pastebin?
[20:27] <LocutusOfBorg> http://debomatic-amd64.debian.net/distribution#unstable/paraview/5.4.1+dfsg4-3/buildlog
[20:27] <LocutusOfBorg> there
[20:27] <LocutusOfBorg> various MB of logs...
[20:47] <wxl> @teward: doesn't look like it. you're it.
[20:48] <teward> heh, was merely curious, since nginx is now tracking Mainline at least for 18.10 and 19.04
[20:48] <teward> ... and I may have implemented something to stop the "Can't start nginx, something's already on port 80" "not-a-bug" bug reports that keep getting filed
[20:49] <teward> not going to start the release notes yet though :p
[20:49] <wxl> an apport-hook that looks for "80" in the report and rejects it? :)
[20:51] <teward> wxl: preemots even that
[20:51] <teward> preempts*
[20:51] <teward> https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1782226
[20:51] <wxl> oh my
[20:53] <teward> mhm
[20:53] <teward> wxl: preempts those issues by addressing the problem in the postinst
[20:54] <teward> if it's a new install but something else is bound to port 80 it doesn't attempt to start nginx at all, but spits a note out into the logs
[20:54] <teward> Not my favorite approach, but...
[20:54] <teward> i'm tired of 20+ "I just installed nginx and it won't start idk why" bugs which are really "Something else is bound to Port 80, go find it and shut it off" Invalid NotABugs.
[20:55] <teward> to be honest i think everyone is :P
[21:42] -queuebot:#ubuntu-release- New binary: budgie-wallpapers [amd64] (cosmic-proposed/universe) [18.10] (personal-fossfreedom, ubuntu-budgie)
[22:05] <mwhudson> tsimonq2: oh, live system only hacks might be more appropriate in livecd-rootfs i guess
[23:42] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.6 => 18.04.14.7] (core)
[23:48] -queuebot:#ubuntu-release- Unapproved: base-files (bionic-proposed/main) [10.1ubuntu2.1 => 10.1ubuntu2.2] (core)