[00:00] hi [00:00] https://bugs.launchpad.net/ubuntu/+source/gsequencer/+bug/1728294 [00:00] Launchpad bug 1728294 in gsequencer (Ubuntu) "Sync gsequencer 1.1.4-1 (universe) from Debian unstable (main)" [Undecided,New] [00:01] does it require any special action? [00:01] it is still unassigned. [00:23] joelkraehemann: Looking. [00:27] thank you infinity [00:44] joelkraehemann: Synced. One note, though. Your libags.so.1.0.0 seems underlinked (unless it dlopen()s ags_thread, which I couldn't find in a quick grep). [00:44] dpkg-shlibdeps: warning: symbol ags_mutex_manager_get_instance used by debian/libags1/usr/lib/x86_64-linux-gnu/libags.so.1.0.0 found in none of the libraries [00:44] dpkg-shlibdeps: warning: symbol ags_mutex_manager_get_application_mutex used by debian/libags1/usr/lib/x86_64-linux-gnu/libags.so.1.0.0 found in none of the libraries [00:44] Both those symbols are from ags_thread. [00:53] circular dependency of libags.so.1 and libags_thread.so.1 [00:55] infinity: both are provided by libags [00:55] package [00:56] in general you have to link libags.so.1 and libags_thread.so.1 as using one of it === infinity0 is now known as Guest30381 === infinity0_ is now known as infinity0 [06:30] Any ubuntu-devel-announce moderators present? [06:30] I've just sent a notice about firewall maintenance that I'd like approved, please. :-) [07:27] blahdeblah: Can I reject and make you fix your grammar? [07:27] absolutely [07:28] If I had bad grammar, I deserve to get rejected [07:28] blahdeblah: (Joking, but you have an incorrect use of a reflexive pronoun, which drives me batty) [07:28] I'm usually pretty good on that - what was the error? [07:28] "The progress of the updates will be communicated in #canonical-sysadmin [07:28] on Freenode IRC by myself" [07:28] Should be s/myself/me/ [07:29] I had better go look up Mr. Fowler to understand why that's wrong. [07:29] Unless you mean "I will be communicating them by myself (because no one loves me)", but then you missed the first conjugation and pronoun. :) [07:30] ♫ nobody loves me, everybody hates me, think I'll go & eat some worms ♫ [07:31] "Guess I'll go eat worms" is the version I know. >_> [07:31] blahdeblah: myself is always a reflexive callback to the subject of an earlier verb. "I kicked myself." "He kicked himself." "She kicked him." "I kicked you." Only appropriate when the subject and object are the same actor. [07:31] Unit193: "I think I'll go and eat worms" for me [07:31] Huh. [07:31] blahdeblah: And never appropriate as a subject. Only as an object. [07:32] dax: Artistic license [07:32] blahdeblah: i'm expecting it's more "three different countries" [07:32] blahdeblah: Now that I've been a language pedant for the night, shall I accept this anyway? :) [07:32] infinity: Well, at least I didn't make the mistake of using it as a subject... ;-) [07:32] infinity: Use your judgement :-) [07:32] blahdeblah: You did. It's a passive subject there. [07:33] I mean, sort of. Depending on how you prefer to diagram sentences. [07:33] OK, here's where I put my foot down. If it's after a preposition, it ain't the subject. [07:33] "Who is communicating updates?" "Myself" (cringe) ... "Me?" [07:34] blahdeblah: Well, yes, not actually the subject of the verb, because passive voice, but it obeys the same rules as a subject because... Passive voice. [07:34] (Accepted) [07:34] thanks :-D [07:35] blahdeblah: Passive inverts subject and object, but the reflexive pronoun rules still apply, so it's "subject-esque" :P [07:37] infinity: The longer you talk about this, the less I respect your expertise. :-) [07:37] blahdeblah: Hahaha. [07:38] blahdeblah: I feel like that's a generally useful statement. [09:37] infinity: hey, that's perfectly good dialect you're complaining about there [09:39] cjwatson: Yes, we refer to it as "hockey player TV interview". [09:40] infinity: nah, using reflexive forms for emphasis is v common in Ireland (it's borrowed from Irish grammar) [09:41] cjwatson: Is that "myself" or "meself" in that case? [09:41] That depends how you want to transcribe it :) [09:41] cjwatson: Somehow, I can tolerate it better when it sounds silly. [09:41] cjwatson: Just like "ain't" sounds better with a southern drawl. [10:50] I succesfully built the zesty release imagemagick for xenial in the ppa:laurencelumi/ppa, [10:50] I apt-get upgrade results in the The following packages have been kept back: etc [10:51] if I install it using apt-get install [10:51] it won't to remove a number of things, including calibre and inkscape [10:52] Do I need to rebuild inkscape and calibre, or is the way to resolve this? [10:57] You need to remove your custom imagemagick install. That should fix inkscape and calibre. [10:58] But you should ask in #ubuntu really. This channel is for the development of Ubuntu itself. [11:01] I want my new built package and a working version of Inkscape and calibre, so was sinking guidance on how to move forward not backward :-) I thought this was the correct spot to ask those kind of questions [14:16] LocutusOfBorg: https://launchpad.net/ubuntu/+source/remmina/1.2.0-rcgit.24-2ubuntu2 is that becuase of main? [14:17] yep [14:17] also because it is not building right now :p [14:23] Missing deps, that came in later I'd presume. [14:24] https://launchpad.net/ubuntu/+source/remmina/1.2.0-rcgit.24-2ubuntu1 hmm actually... [14:50] Unit193: also is anyone sure that building with the Ayatana version won't currently regress the Ubuntu & Unity sessions? [14:51] jbicha: I'm not sure who's looking at it, not part of -desktop. [14:52] that's fine, I'm just pointing out that we should keep what works until someone does look into it :) [14:52] Sounds unfortunate. [14:53] why? do you need the Ayatana version for some reason? [15:01] but I believe flexion is working on all that later this cycle anyway [15:02] Ah, nice. [15:24] this is disturbing, I did sudo apt install zekr and it gave me a popup using zenity to ask me to install ttf-me-quran [15:24] worse, I don't think ttf-me-quran was ever in Ubuntu [15:25] ok, so I hit ok and then it has another popup: "Do you want to leave warning messages enabled?" [15:41] xnox: britney on Bileto fixed \o/ [15:41] I mean, at least it *should* be fixed, I saw 3 successful ticks now [15:51] jamespage: So is ceph verified for zesty? Bug 1706566 [15:51] bug 1706566 in ceph (Ubuntu Zesty) "[SRU] ceph 10.2.9" [Medium,Fix committed] https://launchpad.net/bugs/1706566 [15:53] sil2100, cool =) [16:07] coreycb, hey, for packages that are openstackish and are at 0ubuntu1 version, do we eventually sync those in from debian, when debian catches up? [16:08] e.g. looking at example python-keystonemiddleware [16:08] or do we keep it self packaged, because that's sane, and we will be ahead again with the next openstack release anyway. [16:20] xnox: well, debian development for OpenStack ceased for a while this year and just started picking back up [16:21] xnox: I'm in the midst of merging with debian on deps for bionic [16:24] coreycb, ack, nice. so it is "fluid", cool. [16:24] xnox: yes :) [16:42] bdmurray: its tangled in that other bug I discovered - I can't get a clean test run atm [16:43] jamespage: okay [17:14] I used backportpackage to build imagemagick from zesty for xenial, this resulted imagemagick being held back, an attempted to apt-get install imagemagick, resulted in calibre being removed. Calibre does not require a specific version of imagemagick, but the dependencies for imagemagick have changed, is this why it needs to be removed? [17:15] LaurenceLumi: is there a reason you don't simply upgrade to Ubuntu 17.10? [17:17] yes, 1. I would like to stay on 16 2. I writing a piece of software that I would like to release, that relies on a imagemagick, and I would like those users not to have to upgrade as well. :-) 3. I like to understand how things work, so maybe I can help myself or others going forward :-) [17:19] LaurenceLumi: if you try to install calibre again, what happens? [17:19] 1. If you reason to stay on Ubuntu 16.04 LTS is stability, replacing system libraries with packages from outside the regular 16.04 repos doesn't help stability :| [17:19] bdmurray: errors.u.c isn't showing the actual crash reports for me - known? [17:20] LaurenceLumi: and "those users" you mention in 2 will have to use your PPA, which means they are not running an ubuntu-supported package anymore. [17:21] ok but what about point 3 :-) [17:22] LaurenceLumi: in a pastebin, `apt show imagemagick calibre` [17:22] LaurenceLumi: was calibre the only package apt had to remove? [17:23] when I try install calibre it just installs, so I am guessing that the reason it needed to be removed was not becuase of particular version but because the dependency tree was different, and remove and new install works becuase it uses the new dependency tree, could I be right? [17:24] no inkscape also needed to be removed, but I want to understand calibre first, then I can probably understand inkscape bymeself [17:26] LaurenceLumi: calibre has a build-time dependency on libmagickwand-dev, and inkscape does for libmagick++-dev [17:27] pastebin https://pastebin.com/NkQfcgT5 [17:29] nacc: I get that it has build-time dependency, but what I am trying to understand is how calibre if there is any run-time dependency, I can't see any [17:30] LaurenceLumi: one of its dependencies might [17:30] LaurenceLumi: ah it looks like you rebuilt calibre [17:30] LaurenceLumi: so perhaps it uninstalled the old calibre? [17:33] I built calibre, yes upgraded the old version, but I won't to understand why, as it did not make sense [17:33] wanted to^ [17:34] i.e for calibre how is the version in the ppa any different to the one found in the archive [17:35] from a packaging perspective (I get the code is updated slightly) [17:37] LaurenceLumi: it's a totally different version than in xenail, right? [17:38] yes its a different version but how the dependencies changed, this is what I am trying to understand [17:38] i.e. why can't I just install the xenial version of calibre [17:38] ? [17:42] LaurenceLumi: did you try? see what apt says [17:43] I just did apt-get install calibre=2.55.0+dfsg-1 and it installed fine [17:43] so was I right about the reason? [17:44] LaurenceLumi: i don't know [17:44] i.e. it was just caused by a changed dependency tree, rather than a requirement for a specific version? [17:44] and apt-get is just being carefull? [17:45] Laney: actual crash reports? [17:45] Laney: oh, I see [17:48] Laney: So, no not known [18:10] Ok I can see there is a dependency in calibre-bin, however I am trying to follow the tree from top to bottom, shouldn't there be something in calibre, that says that calibre depends on calibre-bin? [18:11] LaurenceLumi: there is one, afaict [18:16] Ok I can see it, sorry, will try and figure it out now thanks [19:57] Laney: its fixed now, thanks [22:42] bdmurray: Hi Brian, do you have an idea why it takes so long for language-selector 0.182 to make it from bionic-proposed to bionic-release? [22:42] https://launchpad.net/ubuntu/+source/language-selector [22:45] it says "test in progress" at http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html [22:46] GunnarHj: we're in the middle of doing the initial autosync from Debian plus a qt transition plus a perl upload (perl triggers many thousand autopkgtests) [22:46] hrm but the docs page doesn't say what "Not considered" means [22:46] GunnarHj: We're down a cloud region, and everything's very slow and grumpy right now. Patience. [22:47] sarnold: "Not considered" is the opposite of "Valid candidate". As in "nope, not migrating because reasons (see above)". [22:49] infinity: thanks! [22:53] sarnold, jbicha, infinity: Thanks for trying to explain. Don't understand all the implications, but accept the "patience" advice for now. [22:55] GunnarHj: Yeah, the short answer is "everything is glacial right now due to a perfect storm of archive events (opening, some kernel livepatching, etc) that all coincided with us taking down a cloud region for redeployment". [22:55] I guess that answer wasn't very short. [22:55] "Patience" is better. :P [23:07] part like it's 2010 [23:07] partY like it's 2010 dammit [23:48] Who is the right person to contact to get the source package of this bumped? https://launchpad.net/ubuntu/+source/libnl3 [23:50] There is a new major release for Bionic: https://github.com/thom311/libnl/releases -- It'd be nice to use that version [23:51] Sargun, getting it updated in debian would be nice. https://tracker.debian.org/pkg/libnl3 did upstream move?