naccrbasak: iirc, it didn't work the way it seems like it should00:00
naccrbasak: let me see if i have notes00:00
rbasakWe'd need to drop the extracted_dir os.listdir search thing too. Maybe hardcode it to "$extract_dir/x" or similar.00:01
naccright, but like i said, i think that's what i had before and it didn't do what you expected00:01
naccrbasak: ah, it's because the output directory must not already exist00:02
naccand there's no way to make it a temp directory then, without our own managment00:02
rbasakThat's what I meant by "$extract_dir/x".00:03
naccrbasak: i guess we could racily do a tempname() or whatever, but then... racy00:03
rbasakLet me show you what I mean.00:03
naccrbasak: ok00:04
rbasaknacc: roughly rewritten dsc_to_tree_hash: http://paste.ubuntu.com/23784442/ (untested, diff not helpful)00:07
naccrbasak: won't, line 59 create the temp directory?00:09
naccrbasak: per `man dpkg-source` the output dir cannot already exist00:09
naccthat's what i was trying to say above00:09
rbasaknacc: 59 will create temp_dir, yes. But dpkg-source will run on $temp_dir/x, not $temp_dir.00:09
naccrbasak: oh i see what you're doing00:10
rbasakSo then I don't have to search to find out what it called it, and I get to use $temp_dir for $temp_dir/index later on as well.00:10
naccif you can test it, then sure, that's fine00:10
naccit seems reasonable, i mean00:10
rbasakOK, thanks. I'll clean up and rebase.00:10
nacci'd like a comment or something, maybe? it's basically a sneaky way to workaround dpkg-source behavior00:10
naccand easy to miss, imo :)00:11
naccrbasak: otherwise, in general, the changes for unapproved look good00:11
naccrbasak: how hard was it for you to spin up the changes? just wondering how non-pythonic i'm being00:11
rbasaknacc: your code is pretty nice and Pythonic IMHO. The only pain was in shoring up some leaky abstractions, but I think that's to be expected. The number of times the code has been adjusted, and not knowing where we were going in the first place meant that it was inevitable. And I think it's fine to clean up as we go along, so anything I touch I'm cleaning up.00:13
rbasaknacc: maybe a few missing context managers (cleaning up stuff by hand instead of using "with" blocks). But nothing major.00:14
naccrbasak: yeah i think i didn't/don't know enough about the pythonic way at the start, so it's probably more imperative and LBYL than it should be. I've been cleaning that up as I go as well00:15
rbasakAs we're talking about it:00:16
rbasak            raise SourceExtractionException00:16
rbasakThat raises the class object. Should be SourceExtractionException() really - an instance of an exception rather than the definition of one itself.00:16
naccah of course, makes sense00:16
rbasakBut this stuff is minor really. Doesn't matter much!00:17
rbasakI intend to extend the unapproved stuff and call it "queue" BTW. Since I realised today I want NEW handling too.00:17
rbasakSince in SRUs, stuff that hits NEW is often backported from the dev release, and I want to diff against those and they can be imported.00:18
naccrbasak: yep, makes sense to me00:18
naccrbasak: would 'unapproved' be a flag to queue then for that specific case?00:18
rbasakMy plan is that "usd queue" will update all queue/{new,unapproved}/<release> tags as necessary.00:19
naccah ok00:20
rbasakAssuming you run that from something you have already done "usd clone" on.00:20
naccright, this is all 'detached' from the usd side, right? local-only, i mean?00:20
rbasakOne catch is that I need some way to know what package name to operate on. I'm not sure we store that currently. So I might ask for that to be added with "git config" at "usd clone" time or something.00:20
naccusd git side, i meant00:20
rbasakCorrect. All local only.00:20
naccyeah, it's probably not a bad idea to stuff that somewhere00:21
rbasakThen, later, I might add something that pulls the entire queue for a release, or all stable releases, or all releases, clones them all, makes sure they're all up-to-date (rerunning "usd import") and then runs "usd queue" in all.00:21
rbasakAlso perhaps "usd queue approve" or something to accept from the queue a given tag.00:22
rbasakAs I'm storing the Launchpad queue object API URI in the tag, that should be reliable.00:22
naccah ok00:23
rbasak(or reject)00:23
rbasakI need to think about the CLI a little.00:23
naccyeah that seems tricky00:23
naccwe can always mark that part as 'alpha' :)00:23
rbasakIt's only a small set of people who can usefully use it, so I think that's feasible :)00:23
naccand, presuming deps are installed, tab complete works now, so maybe that will help with the options too00:24
rbasakI saw that commit. Neat!00:24
naccit's a bit slow, which i think is because of my ordering decisions, which can be fixed00:27
naccbut it does work, so little steps :)00:28
rbasaknacc: I've updated my branch (fast-forward) so it works but will rebase and squash later to tidy it up.00:43
naccrbasak: ack, just ping me when you're ready for me to merge it in (even if just hte cleanup stack)00:45
rbasakWill do00:45
naccrbasak: thanks!00:48
naccrbasak: ah, so nice to remerge something i've merged before, it's already broken up (so `git fetch lpusip; usd merge lpusip/ubuntu/devel lpusip/debian/sid; git rebase -i [to drop the empty merge commits]`, puts me at a fully deconsructed state already00:53
=== JanC is now known as Guest39941
=== JanC_ is now known as JanC
=== _salem is now known as salem_
Mirvmitya57: retrying pyqt5 i386 as lack of it is blocking Qt 5.7.1 transition and it seems qtwebengine is however now built for i38611:35
Mirvmitya57: nope, still failed with "Depends: qtwebengine5-dev (>= 5.7.1+dfsg-3~) but it is not going to be installed", maybe it's unistallable for some reason11:40
=== jamespag` is now known as jamespage
Mirvmitya57: ah, pyqt5 amd64 binaries are in new queue11:58
tsdgeosMirv: what's holding Qt 5.7.1 landing?12:23
tsdgeosi see it marked as "Valid candidate" in the excuses page12:23
Mirvtsdgeos: did you read the lines below which you wrote? :)12:26
tsdgeosreading which kind of crazyness is this?12:26
tsdgeosi see, tx12:27
=== hikiko_ is now known as hikiko
acheronukMirv: i386 still did not build, or did you prod it too soon for the amd64 indep packages to have published and be available?13:04
acheronukE: Package 'libqt5webengine-data' has no installation candidate13:15
acheronukso I guess needs to wait a bit13:15
rbasakpdeee: can you tell me the relationship between the python-letsencrypt, python-acme and python-certbot source packages please? Which replaced which?13:28
rbasakIs it that acme remains unchanged as the backend protocol library, and letsencrypt->certbot?13:30
=== hikiko_ is now known as hikiko|ln
rbasakpdeee: I don't understand why I don't see a python-letsencrypt transitional package in src:python-certbot in the Xenial new queue.13:33
rbasakOnly one for letsencrypt with no prefix.13:34
rbasakpdeee: I commented in the bug.13:45
LocutusOfBorgslangasek, FYI I syncd "libdfp"14:05
Mirvacheronuk: seems like that, now it's building14:08
acheronukMirv: so is my staging ppa stuff that was waiting on it :)14:09
=== hikiko|ln is now known as hikiko
=== scottt is now known as Guest97906
pete-woodsxnox: hi. just looking back at your change in indicator-network at this revision: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-network/trunk/revision/66014:36
pete-woodsin the maintscript you do etc/.../ instead of /etc/.../14:36
pete-woodsi.e. without the leading /14:36
pete-woodsis that intentional, or a mistake?14:36
pete-woodscause it looks like the scripts are not successfully removing the old XDG files14:37
pete-woodsjust wanted to double-check before I blunder in and naïvely stuff a / in14:38
cjwatsonlooks like a clear mistake to me.  lots of debhelper files don't need the leading / (and it's conventional to avoid it since the paths are really relative to the installation hierarchy), but .maintscript is just passed through to dpkg-maintscript-helper which does need the leading /.14:39
pete-woodscjwatson: thanks for having a look :) - will put a MR together to fix it, then14:41
cjwatsonalso IMO that should have a version in it somewhere14:41
xnoxpete-woods, mistake.14:41
pete-woodsRemoving obsolete conffile /etc/xdg/autostart/indicator-network.desktop ...14:41
pete-woodswoot, looks like it's behaving again now14:41
xnoxpete-woods, but fixed seperately14:41
xnoxpete-woods, https://launchpad.net/ubuntu/+source/indicator-network/0.9.0+17.04.20161223.3-0ubuntu214:41
xnoxi think that needs remerging, and relanding.14:42
xnoxcjwatson, there should be a version, but i did not know how to do it properly with substitution of magic version numbers in the silo.14:42
cjwatsondoesn't have to be a version that exists, as long as it's comparable :-)14:42
pete-woodsoh, did you land that without going through CI train?14:42
cjwatson(also I think bileto supports some kind of poorly-named hack along the lines of 0replaceme14:43
pete-woodswill try and make the same change again14:43
pete-woodscjwatson: would 0.9.0+17.04.20161223.3-0ubuntu1~ work as the version to compare?14:48
pete-woods(that's the revision that the conf file was removed from)14:48
pete-woodsthere are so many special characters in the bileto versions, I don't know what is greater or less than anything else14:48
xnoxpete-woods, it should be the version that successfully removes it so 0.9.0+17.04.20161223.3-0ubuntu2~ and whatever new for xenial.14:48
xnoxi'll try to find the docs for the replaceme stuff.14:49
pete-woodsxnox: so I need to know the replaceme thing then, okay14:49
pete-woodsalso, a link to those docs would be great14:49
pete-woodsI don't see, e.g. 0replaceme, in https://wiki.ubuntu.com/Bileto14:49
dobeypete-woods: well apparently now you have to manually merge the changes from zesty, and then do a no change rebuild14:52
pete-woodsdobey: indeed. always a bit annoying when this happens14:52
dobeyor change the version in the maintscript to be @replaceme14:52
pete-woodsdobey: i'm happy enough with 0replaceme, if I can find the correct string14:53
cjwatsonpete-woods: use dpkg --compare-versions to test things out14:53
cjwatson(badly-named> the design basically assumes there's only ever one thing that might want to be replaced, and it isn't self-documenting)14:54
cjwatsonpete-woods: https://wiki.ubuntu.com/DailyRelease/FAQ documents 0replaceme14:55
dobeypete-woods: it's "0replaceme"14:55
cjwatsonalbeit in stuff about symbols files, but same idea14:55
dobey (c++)"UbuntuOne::Token::addOAuthTimestamp(QString) const@Base" 0replaceme14:55
cjwatsonin this case it should be 0replaceme~ though, I think14:55
dobeyfrom a previous branch i landed14:55
dobeycjwatson: maybe, but i think the ~ might break it?14:56
cjwatsonbreak it how?14:56
dobey0replaceme~ != 0replaceme14:56
cjwatsonscripts/vcs.sh:    find debian/ -type f -print0 | xargs -0 perl -p -i -e "s/0replaceme/$VERSION/g"14:56
dobeyoh ok14:56
cjwatsonso I shouldn't think so14:56
dobeyyeah if the regex is that dumb it's fine. i just didn't know how clever it was trying to be :)14:57
dobeypete-woods: ^^ so 0replaceme~ is what you want in the maintscript for the version14:57
pete-woodsCool, will stuff that in14:58
LocutusOfBorghello, how do I fix this bug? https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/155767515:49
ubottuLaunchpad bug 1557675 in xpdf (Ubuntu) "AppStream icon for xpdf.desktop" [Undecided,Fix released]15:49
LocutusOfBorgsorry https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/164966015:49
ubottuLaunchpad bug 1649660 in hedgewars (Ubuntu) "Gnome Software catalog entry missing for Hedgewars" [Undecided,Confirmed]15:49
LocutusOfBorgthis one15:49
LaneyLocutusOfBorg: http://appstream.ubuntu.com/zesty/universe/issues/hedgewars.html15:53
Laneysame @ debian15:53
LocutusOfBorgso no icon is missing15:54
LocutusOfBorgso adding a Comment section is enough15:55
caribouinfinity: I had a question about silently changing a conffile for tftpd-hpa on Trusty16:09
caribouinfinity: that's a discussion we had with rbasak recently16:09
infinitycaribou: What's the question, and can I answer it with "don't do that"?16:10
caribouinfinity: right now, tftpd-hpa will fail to start if the NIC is not available because it is listening on [::]:6916:10
caribouinfinity: the fix is to change it to :69 in the conffile. rbasak had worries about that triggering a conffile prompt upon update16:10
infinityOh.  Triggering a conffile prompt because a conffile was updated is exactly why the prompts exist.16:11
caribouinfinity: and thought that we might sed it in the postinst, since :69 encompass the [::]:69 value and will work in every situation16:11
infinityNo.  Changing it in postinst is wrong.16:11
caribouinfinity: I know, but it seemed to bother rbasak16:11
caribourbasak: got a comment on this ?16:12
rbasakI said preinst, but I also decided that may not work.16:12
caribourbasak: yes, sorry preinst16:12
rbasakI wondered if there was some way to work around a conffile prompt since the two are exactly equivalent, so we may be able to sed in all cases.16:12
rbasakBut I'm not sure there is.16:12
rbasakAnyway. Someone wants a conffile change? Automatic referral to infinity :-P16:12
infinityChanging it in preinst is also wrong. :)16:13
ogra_nah, just to a boit that says "don't do that !"16:13
infinityIf they've customized their config, we assume they like the one they have, hence the prompt.16:13
infinityIf they haven't touched it, they get the new one silently.16:14
ogra_unless an insane developer mangled it from a maintainer script before :)16:14
infinityThe default may be "bad", but we have to assume that if they've touched the file, they audited and decided they liked the bad default.16:14
infinityogra_: And that developer will be flogged later.16:15
caribourbasak: infinity: I had a similar query regarding a conffile mod for a makedumpfile SRU16:16
caribourbasak: infinity: I'm doing an SRU of a fix in Zesty that brought in two new values to a conffile. Those values are not required to be present in the conffile and can be added later to alter some timings. Would it be sufficient to add a mention in the README to avoid a conffile prompt ?16:16
infinityNow, that said, I don't see a conffile in tftpd-hpa...16:16
LocutusOfBorgLaney, how long will it take to regenerate that info on software catalog once hedgewars is uploaded?16:16
LaneyLocutusOfBorg: Not long, few hours at most16:16
LocutusOfBorgok I uploaded it a few seconds ago16:17
LocutusOfBorgso, do I need to apt update  or is something automatic?16:17
infinityrbasak, caribou: /etc/default/tftpd-hpa is *not* a dpkg conffile, it's created by postinst.16:17
infinityrbasak, caribou: And that throws all your concerns about dpkg conffile prompts out the window.  It's managed by debconf.16:18
rbasakcaribou: sorry!16:18
caribouinfinity: sorry!16:18
LaneyLocutusOfBorg: Did you run desktop-file-validate?16:19
LaneyI think that you made a syntax error16:19
rbasakWell then we can just sed it. Though policy does still require that we preserve user changes.16:19
infinityWell, "managed".  It seems to be a broken setup that doesn't allow debconf to reconfigure. :P16:19
rbasakAnd do we also need to manipulate the debconf db?16:19
LocutusOfBorgLaney, I did run it16:19
caribourbasak: the sed would only change it if it was set to the previous default ([::]:69]16:19
infinityrbasak: debconf is not a registry, you should never need to touch the db.16:20
LaneyLocutusOfBorg: share/hedgewars/Data/misc/hedgewars.desktop: error: file contains line "Comment: Funny turn-based artillery game, featuring fighting hedgehogs!", which is not a comment, a group or an entry16:20
infinityrbasak: If maintainer scripts aren't written to prefer the config file over the DB, that's a bug.16:20
LocutusOfBorgyou are right16:20
LocutusOfBorgI didn't quilt push16:20
rbasakinfinity: what if debconf suggested the previous default to the user, and then stored it?16:20
LocutusOfBorgdpkg-buildpackage unapplies patches16:20
rbasakrbasak: then a future dpkg-reconfigure would restore the old default, no?16:20
infinityrbasak: See above.  The authoritative version is always the config file, never the debconf DB, per policy.16:20
rbasakAh, so the config script should read the config file over the DB when prompting for future defaults? That makes sense, thanks.16:21
infinityrbasak: And, indeed, the tftpd-hpa package does that correctly (sources the config file, stores the values, then asks questions).16:21
cjwatsonpicking the current state out of the config file and stuffing it into debconf as the default value before asking a question is OK though16:21
cjwatsonyeah, that16:21
infinityrbasak: What I don't see it doing is actually rewriting the config file on reconfigure. :)16:21
infinityBut hey, minor oops.16:22
LaneyLocutusOfBorg: Might want to cancel the builds to save the environment a bit. :)16:22
infinitycaribou: As to your makedumpfile thing, you can either ship a new conffile with the new keys or not.  Your call as the maintainer.16:24
infinitycaribou: If it behave correctly without the keys specified, mentions of them in changelog, READMEs, or manpages are all fine.  *shrug*16:25
caribouinfinity: the new keys are only comments for reference16:25
caribouinfinity: k, I started to have second thoughts after rbasak's comments about tftpd-hpa16:25
infinitycaribou: To be fair, people will see that conffile prompt on 16.04->18.04 upgrades anyway, so you can't avoid it forever.16:25
infinitycaribou: (Well, they'll see it if they changed their local copy)16:26
infinityconffile prompts aren't evil, what's evil is when packages alter conffiles outside the proper dpkg mechanism and create *spurious* prompts.16:26
infinityUsers being prompted because *they* changes the file and then you shipped a new one is working as designed.16:27
caribouinfinity: yeah,never worried too much about it as I saw it as expected behavior16:27
rbasakOne problem though is that some people never see conffile prompts (unattended upgrades, etc). So then default conffile handling behaviour takes over, which I think may be confold? And then that defeats some of the point of fixing it, if the goal is to get those users as well.16:28
rbasakThis applies to server stuff quite a bit, where a commonly conffiles have to be edited for their packages to be useful.16:28
infinityDefault should be confold, yeah.  I'd like to think people who run unattended-upgrades on critical infrastructure also go looking for .dpkg-new in /etc occasionally.16:29
infinityBut I bet they don't.16:29
infinityI wonder if we could motd snippet that or something.16:29
cjwatsonI've gone through all the stages of grief on this and eventually decided that conffile prompts (or ucf) are still the least painful thing.16:29
infinity"A recent upgrade resulted in N unmerged conffiles in /etc"16:29
rbasakThat's a good idea.16:29
cjwatsonAfter having years of accretion of weird sshd_config editing runes in openssh-server.postinst.16:30
cjwatsoninfinity: Very Gentoo :-)16:30
caribouyeah, I like the fact of being told about things that should be looked at16:30
cjwatson(It has something very similar IIRC)16:30
infinitycjwatson: Oh, I thought you were punning about emerge.16:30
infinitycjwatson: But yeah, if they have something like this, they might be doing something right.  rbasak's not wrong that there's a general conflict between silent upgrades and conffile updates.  Post-facto notification seems not entirely bad.16:31
cjwatsonGentoo doesn't have any automatic conffile merging, so it *has* to have a prompt at the end to tell you to apply changes.  But that's not to say it's a bad idea.16:31
infinityI wish we'd done etckeeper-by-defalt long ago, so we could just say "/etc has unresolved conflicts, fix plz".16:36
infinityWell, and hook it into dpkg, so a conffile update is actually a merge attempt that vomits to conffile.rej on failure, etc.16:37
infinityWoulda shoulda coulda.16:37
infinityI suppose we still could some day.16:38
=== Foxtrot is now known as foxtrot
infinityThough, I guess working toward the new world oder of "defaults in /usr, overrides in /etc" is a better use of time.16:40
infinityMaybe we can actually have an empty /etc by 2038.16:40
infinityWell, empty except for /etc/rmt, because that bit of backward compatibility is super important to someone from 1972.16:42
philrocheHi guys, I'm hoping someone can steer me in the right direction. Earlier today gce-compute-image-packages was accepted in to xenial-proposed pocket but the binaries are not being published to the repository. The amd64 build is stuck "Pending publication" (See https://launchpad.net/ubuntu/+source/gce-compute-image-packages) Is there anything I need to do to get past that stage or is it just a matter of waiting?17:22
naccphilroche: i'm guessing here, but it's a new src and binary, so it will need approval by an AA to migrate to -proposed.17:27
seb128could somebody from the SRU team copy https://launchpad.net/ubuntu/+source/evolution/ over from xenial-proposed to updates? the update was accepted without a bug reference and is probably stucked because of that but the change is fine and has been tested17:28
seb128bdmurray, ^ you maybe?17:28
bdmurrayseb128: looking17:29
seb128bdmurray, thanks17:29
cjwatsonnacc is correct; the binaries are new in that suite so it's in the NEW queue for approval.17:29
naccphilroche: --^17:29
bdmurrayseb128: released it17:31
philrochecjwatson: nacc: Thanks17:31
seb128bdmurray, thanks!17:31
naccphilroche: note that you can also see that from https://launchpad.net/ubuntu/+source/gce-compute-image-packages/20160930-0ubuntu3~16.04.0 (the '(New)') next to the build17:34
philrochenacc: Ah. I see thanks17:34
naccphilroche: and you can also see it here: https://launchpad.net/ubuntu/xenial/+queue17:35
philrochenacc: This process is new to me so thanks for that.17:45
naccphilroche: np, I often forget about it too :)17:46
naccphilroche: / it's new to me as well17:46
sil2100Laney: hey! Would you mind if I re-upload the dbus package with just the ssh/logind workaround?17:48
Laneysil2100: If you take over the other fix too17:49
sil2100Laney: what do you mean?17:50
sil2100Laney: I see it's marked as verification-failed right now and causing some issues, right?17:50
sil2100We just want to get the ssh fix released as soon as possible as many users are waiting for it17:50
Laneysil2100: Yes, but it's not buggy itself. If you want to revert it to get your other fix in, then I would appreciate you taking care of putting it back when it is safe to do so.17:52
sil2100Laney: ah, like this17:52
sil2100Laney: I can do that sure17:53
naccrbasak: still around?18:01
mitya57Mirv, it looks like pyqt5 built everywhere now.18:11
Mirvmitya57: yes. if you or someone has time, look at the qtquickcontrols examples installability issue on excuses page (I'm going to sleep now already)18:46
Mirvqtquickcontrols5-examples/amd64 unsatisfiable Depends: qml-module-qtquick-extras etc18:47
Mirvacheronuk: ^ note, at least that found from excuses page, no need yet to decipher update_output more18:48
bdmurrayLaney: Do you know what Code 20 means in autopkgtest results?18:50
davmor2bdmurray: it's a countdown to total global annihilation you really need to stop it before it gets to 0 ;)18:53
mitya57Mirv, qtquickcontrols5-examples is installable in my amd64 chroot.18:53
mitya57Though, qml-module-qtquick-extras is the only dependency that is in universe, so probably that is the issue.18:55
mitya57Maybe someone can promote it to main? (It comes from qtquickcontrols-opensource-src source which is in main.)18:57
pdeeerbasak, hlieberman and RAOF may be better equipped to answer your questions, but19:00
pdeeeAFAICT python-certbot Replaces: python-letsencrypt19:01
pdeeepython-acme is a dependency of either of those19:03
pdeeenot sure how that relates to source packages, though19:03
bdmurrayjbicha: How was bug 1649995 fixed in zesty? Just setting it to Fix Released doesn't help me from an SRU perspective.20:20
ubottubug 1649995 in gnome-online-accounts (Ubuntu Yakkety) "Replace Google API key used by GNOME services" [High,In progress] https://launchpad.net/bugs/164999520:20
bdmurrayzul: The existing nova-lxd SRU hasn't been verified (bug 1642274). Do you want the new upload to supersede it?20:29
ubottubug 1642274 in nova-lxd (Ubuntu Yakkety) "[SRU] newton nova-lxd 14.0.1 point release " [High,Fix committed] https://launchpad.net/bugs/164227420:29
zulbdmurray: lemme check around20:30
bdmurrayzul: okay20:30
=== salem_ is now known as _salem
smoserhttp://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html <-- why is cloud-initramfs-tools there ?20:36
smoser'missing build' seems relevant, but there is a build20:36
hliebermanrbasak: Hiya.  Debian maintainer of the certbot stuff here.20:37
hliebermanrbasak: So, yes, you're correct: python-acme stays the same, python-letsencrypt => python-certbot, letsencrypt => certbot, python-letsencrypt-apache => python-certbot-apache20:37
hliebermanGenerally, users wouldn't have installed python-letsencrypt directly, so there's no transitional package there.20:38
cjwatsonmitya57: done20:41
hliebermanIf they did, they could be using plugins that wouldn't work in the new namespace.20:45
jbichabdmurray: it was fixed in gnome-online-acccounts 3.22.3-1, I've added that to Other Info on the bug now20:48
jbichawe have to figure out how to get evolution through phased-updates though…20:49
bdmurrayjbicha: Do you know anything about this new crash?20:52
jbichano, it does look new; I can ping the evolution maintainers about it20:54
jbichaactually it was evolution-data-server that needed to be updated first but that's fully phased so we don't need to let that stop us from updating g-o-a now20:57
bdmurraylooking at the error tracker I don't see any other crashes with webkit_editor20:58
jbicharight and it was in yakkety that evolution switched from webkit1 to webkit2 so it's probably new to yakkety21:01
jbichabdmurray: thanks. Could you look into the libicns yakkety SRU? it's needed for hdhomerun-config-gui to build there21:21
=== smoser` is now known as smoser
naccjuliank: do you know what's going on with LP: #1522675? seen an uptick lately in people hitting it on #ubuntu21:46
ubottuLaunchpad bug 1522675 in update-notifier (Ubuntu) "Warning messages about unsandboxed downloads" [Medium,Confirmed] https://launchpad.net/bugs/152267521:46
julianknacc: More users upgrading to >= xenial?21:47
juliankSomeone may want to play with update-notifier's use of apt-helper and have it download stuff into a directory writeable by the _apt user21:48
naccjuliank: checking on the current user who brought it up21:49
juliankSame for synaptic apparently.21:51
juliankFunny how ubottu  says bug in update-notifier (Ubuntu)  but the link it gives redirects to https://bugs.launchpad.net/debian/+source/synaptic/+bug/152267521:51
ubottuLaunchpad bug 1522675 in update-notifier (Ubuntu) "Warning messages about unsandboxed downloads" [Medium,Confirmed]21:51
naccjuliank: in this case, user already ahd fonts package installed, and a regular update failed, it seems (on 16.04). Not dist-upgrading.21:52
naccjuliank: multiple tasks in same bug21:52
juliankWell, nothing is failing there21:52
naccjuliank: can be referred to by multiple src pkgs (therefore)21:52
julianknacc: I think you really meant bug 165192321:53
ubottubug 1651923 in apt (Ubuntu Yakkety) "apt https method decodes redirect locations and sends them to the destination undecoded." [Medium,Triaged] https://launchpad.net/bugs/165192321:53
naccjuliank: ah that's the underlying spaces issue?21:54
juliankThere's a workaround in zesty, and I'll backport this shortly to yakkety and xenial, but I first want to write a regression test case and optimally do the whole thing in an upstream release (scheduled in 4-5 days)21:55
naccjuliank: ack, just trying to get context so I can provide the best answer(s) in #ubuntu21:55
naccjuliank: right now, folks are manually installing the .deb from unstable21:55
naccfor the fonts package21:55
juliankThat works too as it skips the redirector or something21:56
naccyeah, i think the fonts package (debian) has changed that as well21:57
naccso it's like there are two fixes :) (for that particular package)21:57
juliankYeah, but there's others mentioned in the bug log21:57
naccyep, presumably any of the ones that are downloading something during the install could be affected21:57
jbichaI'm guessing bug 1607535 is the same issue21:57
ubottubug 1607535 in msttcorefonts (Ubuntu) "ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts and should be updated to version 3.6 from Debian" [Medium,Confirmed] https://launchpad.net/bugs/160753521:57
naccjuliank: thanks for the bug link and clarification!21:57
naccjbicha: ack, that's the one i saw yesterday21:58
juliankIf anyone is an http expert: I only urlencoded the path component of URLs we give to curl. I wonder if I should also urlencode some more parts - but I'm not sure.21:58
naccjbicha: dunno if you want to update with references to the other two bugs21:58
jbichaif 1651923 is the main bug, we can duplicate the other bugs to there21:58
juliankjbicha: Keep one open for the package update request?21:59
juliankIt's the same underlying issue of course, but a package update obviously also entails other things and is good to have in either case.21:59
jbichaoh for ttf-mscorefonts? I'll open a different bug requesting that be updated22:00
juliankYes. I remember someone tried merging that yesterday, but it was a bit complicated.22:01
rbasakhlieberman: hi22:33
rbasakhlieberman: still, it makes python-letsencrypt un-updateable, so I think we do need an update for it bundled with this SRU.22:33
hliebermanrbasak: A dummy?22:34
rbasakhlieberman: we could drop letsencrypt from src:python-letsencrypt, and the same for apache if that works the same way.22:34
rbasakhlieberman: since src:python-certbot is taking the package over.22:34
hliebermansrc: python-letsencrypt can be RMed.22:35
hliebermanIt's completely replaced.22:35
rbasakhlieberman: not from a stable release, unfortunately.22:35
rbasakWe could replace it with an empty package, but users may still theoretically be using python-letsencrypt ("import letsencrypt"), and I don't think there's any need to drop that from a stable release here.22:36
hliebermanpython-certbot Break's python-letsencrypt.22:36
rbasakWell, that's something that should be discussed in the bug then.22:36
rbasakBecause it's a use case that could exist that we definitely are breaking.22:37
hliebermanBecause it ships a symlink for /usr/bin/letsencrypt and Provides: letsencrypt.22:37
rbasakSurely that's letsencrypt, not python-letsencrypt?22:37
rbasakUh, sorry.22:37
rbasakSurely that's certbot, not python-certbot?22:37
hliebermanOh, yeah. Sure. I suppose someone could theoretically want python-letsencrypt but not letsencrypt, though it would be very strange.22:38
rbasakWhy aren't they the same package?22:38
hliebermanThe library isn't really meant to stand alone, like python-acme is.22:39
hliebermanThey're the same source package.22:39
rbasakWhy aren't they the same binary package?22:39
hliebermanSorry; I'm on my cell phone, so I might not be explaining this very well.22:40
rbasakIf it's not meant to stand alone, shouldn't it be in /usr/lib/certbot?22:40
rbasakhttps://www.debian.org/doc/packaging-manuals/python-policy/ch-programs.html#s-current_version_progs "4.2.1 Programs Shipping Private Modules22:40
hliebermanIt's can't be private in that sense, since a third package does depend on it. python-certbot-apache.22:41
rbasakI see, OK.22:41
rbasakWhy must python-certbot Breaks: python-letsencrypt?22:42
hliebermanAnd python-certbot-nginx, though that's not relevant.22:42
rbasakAFAICT, they provide different files.22:42
hliebermanIt doesn't. I'm sorry, I meant s/python-// before.22:42
hliebermanThat's my fault.22:42
hliebermancertbot breaks letsencrypt.22:43
rbasakActually it looks like it does.22:43
rbasakIn queue/xenial/new22:43
rbasakPackage: python-certbot22:43
rbasakBreaks:...python-letsencrypt (<= 0.6.0)22:43
rbasakReplaces: python-letsencrypt22:44
hliebermanAh -- are you going to be around in a bit? This really should wait until I'm actually in front of my computer.22:44
rbasakI appreciate that's fine for ongoing development.22:44
rbasakBut for the SRU, maybe we could drop that?22:44
rbasakI'll be going to bed soon, sorry. We can chat another time though, just ping me.22:44
hliebermanSince I am clearly not word-ing very well.22:44
hliebermanSure thing. I'll put something in the bug and try and catch you tomorrow.22:44
rbasakOK. I appreciate you getting in touch. Thank you for helping with this.22:45
hliebermanOf course! Sorry for the confusion22:45
rbasakNo problem. It's confusing by its nature. I don't mind working through it, just want to get to the bottom of it and reach an agreement and get it done :)22:45
hliebermanYeah. The differences between Debian and Ubuntu is just slight enough to really trip me up, too.22:48
hliebermanLike with Maintainer. I know I knew that, once upon a time.22:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!