/srv/irclogs.ubuntu.com/2017/05/08/#ubuntu-devel.txt

=== s1aden is now known as sladen
mwhudsonwhat the heck is going on here? https://launchpadlibrarian.net/318753835/buildlog_ubuntu-artful-amd64.paste_1.7.5.1-6ubuntu3_BUILDING.txt.gz00:45
mwhudsondpkg-genbuildinfo: error: cannot fstat file ../python-paste_1.7.5.1-6ubuntu3_all.deb: No such file or directory00:45
=== wendar_ is now known as wendar
cjwatsonmwhudson: read up slightly above that - need to stop using -Z bzip2 (default is now xz which is generally better)02:55
mwhudsoncjwatson: ah ok02:56
mwhudsonwgrant: do you (or anyone else) know stuff about python packaging?04:05
mwhudsonthe story is that the current jinja2 package doesn't install some files that have syntax that python 3.5 doesn't accept04:06
mwhudsonbut without them, jinja2 doesn't install under python 3.604:06
mwhudsoner doesn't import04:06
mwhudsonso i changed the package to include them but now it doesn't install properly because errors get spat out by python3.5 during install04:06
mwhudsonoh wait, man dh_python3 explains this04:09
=== Spads_ is now known as Spads
=== kitterma is now known as ScottK
=== zyga_ is now known as zyga
mwhudsonno, that doesn't work07:32
SkuggenIs there some way to get dput (for uploading to a launchpad ppa) working behind a proxy?07:46
infinitySkuggen: If it's a proxy that forwards active FTP but fails miserably at passive you could try twiddling passive_ftp to 0 in /etc/dput.cf07:49
infinitySkuggen: Alternately, sftp might work better, see https://help.launchpad.net/Packaging/PPA/Uploading#Uploading_with_SFTP07:50
Skuggeninfinity: Thanks, I'll give it a try :)08:04
SkuggenI tried changing a ~/.dput.cf before, but according to the debug output it was still using passive, but can try with the file in /etc instead08:05
=== tyhicks` is now known as tyhicks
rbasak!dmb-ping15:06
ubottubdmurray, BenC, cyphermox, infinity, micahg, rbasak, sil2100: DMB ping.15:06
naccgsilvapt: i'm around now15:27
nacctjaalton: do you know if the dogtag trac moved somewhere else with fedorahosted reitrement (re: LP: #1662654)16:23
ubottuLaunchpad bug 1662654 in tomcat8 (Ubuntu) "Please remove resteasy (3.1.0) from zesty-proposed" [Undecided,Fix released] https://launchpad.net/bugs/166265416:23
naccthe link goes to the retirement page16:23
nacctjaalton: and do you have the link to the resteasy bug16:25
sarnoldgsilvapt: now that the update is pushed, you can go through the pull-ubuntu-source, patch, build, test, iterations17:04
gsilvaptah. okay. I can try to do that now. Thanks, sarnold17:17
gsilvaptI need help solving a community issue. Can someone forward me to the right place?17:17
wxlwhat's up gsilvapt ? also hey :)17:18
gsilvapthey wxl, long time no see17:18
naccgsilvapt: what community issue?17:19
gsilvaptThere's this guy that I'm not sure what the hell is his goal. He started my suggesting an edit that had swastikas in the page and thought it was okay and now he removed content from Wiki pages that were useful and he didn't ask anyone before doing any changes17:19
naccgsilvapt: spammer?17:20
gsilvaptOf course we can revert that back but it's getting extremely ridiculous at this point17:20
naccgsilvapt: on the wiki?17:20
gsilvaptI have no idea. I once emailed him suggesting to keep his cool, get to know the people around, ask & suggest stuff in the *proper* way and not spam/do stuff right-of-the-box because nobody would listen to him17:20
wxllinks may be helpful17:20
gsilvaptHe said he had been contributing for 9 years and he would be fine. lol17:21
gsilvapts/page/wiki17:21
cjwatsonswastikas in pages are just a matter of banning, IMO.  the Ubuntu code of conduct does not require you to negotiate with Nazis17:21
naccheh17:21
naccsad that it's even a thing17:21
wxlwhat if it's the more eastern persuastion of swastika?17:22
cjwatson(OK, unless it's explicitly in one of the relevant Asian religious contexts, but I can't see why that would be on-topic in the Ubuntu wiki either)17:22
wxlthat17:22
wxli guess someone could use them for bulletpoints17:22
cjwatson... but shouldn't17:22
gsilvaptlink to page where he deleted content, according to Brian Murray: https://lists.ubuntu.com/archives/ubuntu-quality/2017-May/006887.html17:22
wxli don't see it as RELEVANT, but that doesn't mean someone wouldn't use them17:22
cjwatsonI don't think it's interesting playing the what-if game on this.  If it was actually a relevant non-Nazi use then I assume gsilvapt would have said17:23
cjwatsondon't be played by trolls17:23
gsilvaptAnd this all started here: https://lists.ubuntu.com/archives/ubuntu-quality/2017-April/006847.html17:24
gsilvaptHe later removed the images of swastikas, FYI17:24
cjwatsonwhere was the swastika thing?17:24
jbichaI think original was https://commons.wikimedia.org/wiki/File:Blueprint_of_Victory._Avoid_the_Black_Widow_of_war_production_-_NARA_-_534556.jpg17:25
jbichatweaked to https://wiki.ubuntu.com/es20490446e/Reporting%20bugs?action=AttachFile&do=view&target=Blueprint.jpg17:25
tjaaltonnacc: oh right, I'll update that17:25
nacctjaalton: thanks!17:25
wxlum, equating windows (?) to nazis?17:25
cjwatsonok, I guess that's super bad taste rather than Nazi advocacy17:26
wxlwhere did you find that btw, jbicha ?17:27
jbichawxl: by digging through https://wiki.ubuntu.com/es20490446e/Reporting%20bugs?action=info17:27
cjwatsonthough I would not defend it and perhaps the poster needs a cooling-off period17:27
naccalso, i think there is a general issue with es20490446e on bugs :)17:28
wxlyeah i hadn't seen it when i searched through there17:28
wxlXD17:28
naccgsilvapt: so it's not like you are unique here :)17:28
wxlnacc: that is a WHOLE different story XD17:28
naccwxl: :)17:28
gsilvaptLook, I stopped reading his stuff a long ago. I feel he is trying to troll us. He sends youtube videos as replies to emails on the mailing list17:29
wxlum17:29
gsilvaptToday I got another email from someone complaining he removed parts he considered important in the Wiki17:29
wxlso Alberto is the one who did that?17:29
gsilvaptYes, wxl17:29
naccwxl: it appears so (the original image)17:29
* wxl sighs17:29
cjwatsonsee also https://bugs.launchpad.net/launchpad/+bug/168651817:29
ubottuLaunchpad bug 1686518 in Launchpad itself "The reporting guidelines aren't well fitted" [Undecided,New]17:29
cjwatsonthe "just a joke" defence he used for the swastika bit is unacceptable17:30
jbichahttps://help.ubuntu.com/community/ReportingBugs17:30
jbichahttps://help.ubuntu.com/community/ReportingBugs?action=recall&rev=29917:31
gsilvaptAnd I thought this had to stop. I have no clue if I'm just being too naggy or if this is actually crossing the line of reason and thus asked for help for some to check this17:31
gsilvaptI emailed the council once, I don't want to email again if they did nothing on this before17:31
gsilvapt(before being the Swastika and his "just a joke" comment)17:31
cjwatsonthis certainly seems like a matter for the CC, anyway17:31
wxlhe's a very avid contributor, it seems, at least in terms of the frequency of contributions17:31
wxlquality of contributions may be open for discussion..17:31
naccSNR is low, in my experience17:32
naccnot that they are not making ubuntu better, admittedly17:32
wxland i've found him entirely convinced of his own opinion and unwilling to listen otherwise17:32
wxlthis has come up more than once17:32
wxli'm sure the cc looks at the former point as trumping the latter ones, though17:32
cjwatsonthey may do, but they should actually respond17:33
cjwatsonrather than leaving people to guess17:33
naccyep17:33
gsilvaptyea wxl, I was surprised to see his LP karma page. He might have been around for 9 years after all but it seems most of his contributions are more setbacks rather than progress. What he is doing is not aligned with anything other than his opinions17:34
wxlkarma is of no real value :)17:34
gsilvaptSure but it says if a person is active or not17:34
wxlright17:34
naccseb128: will you be merging/fixing gnome-menus this cycle? just tracking stuff in merges i'm associated with :)17:35
naccslangasek: are you doing an lvm2 merge? rbalint's fix for LP: #1576341 will add to the delta and i wonder if we should just send it to Debian?17:36
ubottuLaunchpad bug 1576341 in systemd (Ubuntu) "systemd in degraded state on startup in LXD containers" [High,Confirmed] https://launchpad.net/bugs/157634117:36
wxlwhat i would suggest is contacting them again with https://bugs.launchpad.net/launchpad/+bug/1686518 being a really concrete example of the problems he causes. you might want to check out #ubuntu-community-team as some cc members hang out there17:36
ubottuLaunchpad bug 1686518 in Launchpad itself "The reporting guidelines aren't well fitted" [Undecided,New]17:36
wxlgsilvapt: ^^17:36
wxlwith popey, mhall119 being the most active17:36
cjwatsonhttps://bugs.launchpad.net/launchpad/+bug/1686518 is an "annoys Colin" kind of thing, not a "should be banned" kind of thing; I think it's at most illustrative17:37
wxlcjwatson: well, i'm not suggesting the cc ban him. but suggesting better behavior might be appropriate.17:37
cjwatsonI think the terrible stuff around the proposed wiki edit is a much better example, but it's probably worth accumulating things17:37
wxlhe may think he can just bully people around, but i doubt he would be so inclined with the cc.17:38
gsilvaptOkay, I can try to get in touch with them again and bring this example to the table17:38
wxlalso, colin, you really eloquently reflect my feelings about video. the post that drove me crazy was https://lists.ubuntu.com/archives/ubuntu-quality/2017-May/006888.html17:39
cjwatson(I've encountered this user a few times, but before seeing the stuff gsilvapt posted here I only considered them annoying rather than anything more)17:39
wxlgsilvapt: feel free to cc me in further emails. i certainly agree with your concerns and would be willing to support you17:39
jbichahe also annoyed GNOME recently, https://bugzilla.gnome.org/78200217:41
ubottuGnome bug 782002 in general "Making GNOME really pleasant to use" [Normal,Resolved: incomplete]17:41
gsilvaptcjwatson, yep, that's my problem. I stopped reading his stuff a while back, when he posted a private video entitled "I feel Ubuntu is facing doom". From thereon, I just ignored his stuff. Then some answers started getting my attention. First the swastika, now the user complaining he deleted important parts of the wiki page. Men... Trolls are trolls, this is something else17:41
gsilvaptThank you wxl, I think I'll reply to my own email to add this another example and keep the previous message17:42
infinityI kinda feel like he's using Ubuntu mailing lists to get impressions on his youtube channel. :P17:42
gsilvaptWho knows....17:42
wxlcjwatson: my concern is that even annoying can be severely problematic. what's annoying to us might be infuriating to others. maybe even causing them to give up contributions and/or assume the community consists of and supports people with similar attitudes17:43
slangaseknacc: am I doing an lvm2 merge> grep-merges tells me that you TIL; I don't particularly care who does it, it's been a pretty trivial merge up to now17:43
naccinfinity: heh17:43
naccslangasek: ack, i was just going to remerge it now and pull in rbalint's fix at the same time17:43
wxl"I know this project doesn't like reports in video, but I think this is the exception rather than the rule:"17:43
naccslangasek: if it wasn't on your plate, you had just done the last merge17:43
* wxl facepalms17:43
slangaseknacc: yeah, go for it :)17:43
naccslangasek: thanks17:44
cjwatsonwxl: yes17:45
slangasekgsilvapt, wxl: uh... what's this about swastikas and wiki page deletions?17:45
slangasekfwiw bdmurray has a lot of context on this particular contributor17:45
wxlgsilvapt: if you read the CoC, i think there are some points where there is clear violation. i'd be willing to reply to your initial email with further elaboration on that.17:47
wxlslangasek: i didn't know about it, but jbicha summarized the relevant links above. tl;dr ReportingBugs wiki :(17:47
cjwatsonfeels like a more or less well-intentioned contributor whose idea of being constructive is at right-angles to everyone else's and isn't listening to feedback, which is one of the most difficult cases to deal with17:49
naccrbalint: are you ok with me pulling your fix for the above bug into the merge?17:49
rbalintnacc: perfectly, thanks :-)17:49
naccrbalint: might do the same for open-iscsi if that's ok with you17:49
naccrbalint: also, thank you very much for the bug feedback!17:49
slangasekcjwatson: not counting that one time when he tried to troll debian-devel into fighting with the Ubuntu community for him17:49
cjwatsonslangasek: I don't remember that one17:51
rbalintnacc: sure, please update open-iscsi17:52
naccrbalint: thanks!17:52
rbalintnacc: i'm building the systemd, but some tests are failing17:52
naccrbalint: fun :)17:52
infinitycjwatson: Well-intentioned or not, I've just wasted several minutes of my life on more than one video response of his from that thread that amount to "sorry, not sorry", and "people will always be angry about something, so you should let me publish swastikas in the wiki, you fascists".17:53
bdmurrayI was hoping the video re "ubuntu is facing down" would lead to a walking away.17:53
cjwatsoninfinity: yeah, quite17:54
cjwatsonslangasek: was that https://lists.debian.org/debian-user/2013/11/msg00410.html ?17:54
slangasekcjwatson: yeah17:54
slangasekwait17:54
slangasekcjwatson: no17:54
cjwatson(my "more or less well-intentioned" comment is not intended as a defence BTW; regardless of intention this person is currently wasting people's time and IMO needs to shape up or ship out)17:55
slangasekcjwatson: https://lists.debian.org/debian-devel/2014/04/msg00319.html17:55
naccthe most annoying thing to me, is he sets the priority of bugs (which results in an e-mail) without ever (afaict) actually fixing anything. And the priority hover text claims to be about when bugs will get fixed17:56
naccso it ends up lying to users about when to expect a fix17:57
cjwatsonslangasek: whee17:57
gsilvaptI can't stand his name or email address anymore, oh lord17:57
gsilvaptIt's decided, I'll gather these links and send them to the CC, wxl17:57
gsilvaptWhen running dpkg-buildpackage -S -nc -d it returns clearsign failed: "No secret key"18:09
gsilvaptAny help?18:09
naccgsilvapt: did you insert a changelog entry?18:09
naccgsilvapt: you can't sign a package with a changelog entry for a different user -- you can pass -us -uc to not sign the .dsc and .changes files18:10
gsilvaptHum, I thought it was because of that. I didn't write anything because the log is not changed since 2016. Not sure if I should or not write something18:11
naccgsilvapt: are you making a change?18:11
gsilvaptediting the man pages to remove the hyphens18:12
naccgsilvapt: then you need to add a changelog entry :)18:13
naccgsilvapt: dch -i18:13
gsilvaptOkay, I'm in the changelog file. Lets see if I don't mess this one up18:13
naccgsilvapt: i would recommend using dch18:13
naccgsilvapt: as inserting by hand can be error-prone18:13
gsilvaptyes, I used that command18:14
gsilvaptI had it before in the step-by-step guide you sent over18:14
naccgsilvapt: ack, ok18:14
gsilvaptNow, I'm afraid I have no clue about the software version, lol18:14
naccgsilvapt: `dch -i` should have done the right thing already18:15
gsilvaptThe LP is confusing, the github page is only upstream18:15
naccgsilvapt: what is the prior version in the srcpkg?18:15
gsilvaptis there a command to check that? I have no clue where/how to find it18:16
naccgsilvapt: just look in the changelog?18:16
=== fossfreedom_ is now known as fossfreedom
naccgsilvapt: it will be the one just below what you're entering18:17
gsilvapt1:4.2-3.2Ubuntu1 yakkety18:17
gsilvaptRight, I froze there because there are no entries since september18:17
naccgsilvapt: what release are you trying to work on?18:18
gsilvaptViviv18:18
naccgsilvapt: vivid??18:19
naccgsilvapt: vivid is eol18:19
naccsarnold: ping -- i just saw your shadow update went out for y and z but not a (per rmadison)?18:19
naccsarnold: so a is behind z now18:19
gsilvaptWait, not vivid. Should be artful18:19
naccsarnold: is that a latency thing?18:19
sarnoldnacc: two pronged -- (a) I don't have upload privs to -devel, only released releases (b) since they're fixed in debian, a merge from debian would handle that well18:20
naccsarnold: sure, just wasn't sure if it's what was expected18:21
naccsarnold: and  means gsilvapt's artful upload is missing context that will be dropped on the next update18:21
naccsarnold: but it's ok18:21
sarnoldnacc: :(18:21
naccsarnold: and (a), understood, makes sense18:21
naccgsilvapt: ok, so for artful, since it's in development18:22
naccgsilvapt: your version will be 1:4.2-3.2ubuntu2. But note that it is probably better to wait for a merge18:23
naccgsilvapt: as i think the merge will pick up the thing you want to backport anyways, right? (bumps upstream version to 4.4)18:23
gsilvaptWhen they merge with upstream, the man pages will be fixed. So yes, I believe the answer is yes18:23
naccgsilvapt: to be clear, not just upstream, but specfically 4.418:24
gsilvaptOnly upstream has this fix, as far as I could see18:24
naccgsilvapt: in a released version?18:24
gsilvaptNor Ubuntu or Debian had this fix yet but it was fixed in November last year upstream18:25
gsilvaptNot sure if it is in a released version, apparently not, nacc.18:25
naccgsilvapt: how have you checked?18:25
naccgsilvapt: oh i see 4.4 is from september, but the fix was in november?18:26
naccgsilvapt: ok so it won't be fixed by the merge, got it18:26
naccgsilvapt: merge is not with upstream, but with debian18:26
naccgsilvapt: and debian is at 4.418:26
gsilvaptWait, you're way over my head :D18:26
naccgsilvapt: i'll start over18:26
gsilvaptLets recap: I've recreated the bug in my system and it confirmed. I download all source deos from Debian and Ubuntu and neither have the fix. The upstream source has the fix, made in November last year.18:27
naccgsilvapt: what i'm trying to understand is if this particular change you've found from upstream is present in the version packaged in Debian right now18:27
naccgsilvapt: and an ubuntu merge is merging with debian, not with upstream18:27
gsilvapts/deos/packages18:27
naccgsilvapt: so, back to your srcpkg18:27
naccyour veresion will be what i said before18:27
naccand insert an appropriate chagnelog entry18:28
nacctarget it for artful18:28
naccthen dpkg-buildpackage should work, it will try to sign it with gpg18:28
gsilvaptBut shouldn't I wait for a merge? Or because it is not in a debian release there is no use in that?18:29
naccgsilvapt: right, unless debian is also planning on bumping it's version, a merge doesn't help18:30
naccgsilvapt: but that's gated by an upstream release anyways18:30
naccgsilvapt: we can do multiple merges too18:30
gsilvaptOkay, I think I understood. Thanks! I'll give it a try to, at least, finish the first fix I made18:31
naccgsilvapt: sounds good, feel free to ping if you want a review18:31
gsilvaptI have to do dpkg-buildpackage before doing that, right, nacc?18:33
gsilvaptAhum... Invalid user id :D18:34
* gsilvapt faceplam18:35
gsilvaptDid the entry, forgot to add details for gpg18:35
gsilvaptI think I've broken the changelog... Oh dear me18:40
gsilvaptnacc, how do I ask for review?18:48
gsilvaptPost it anyways in LP bug report or is there another way?18:48
naccgsilvapt: from me or generally?18:51
gsilvaptI understood you were going to do it but if you're too busy I can request a general review. After all, that's the right process, isn't it?18:52
naccgsilvapt: yeah, so upload a debdiff to the bug and subscribe ubuntu-sponsors18:56
gsilvaptOkay, thanks, nacc18:59
gsilvaptI think I've done it right: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/142780718:59
ubottuLaunchpad bug 1427807 in shadow (Ubuntu) "usermod's man refers to --*-sub-uids but accepts only --*-subuids" [Medium,Fix committed]18:59
naccgsilvapt: i don't think 'fix committed' is right19:07
naccgsilvapt: notyour  fault19:07
naccgsilvapt: ok, few things i see with https://launchpadlibrarian.net/318864267/remove-extra-hyphens-as-LP427807-suggests%2A19:08
naccgsilvapt: lots of trailing newlines in the changelog entry19:08
naccgsilvapt: it's not targetting a release (UNRELEASED rather than artful)19:08
naccgsilvapt: you made it 1:4.2-3.2ubuntu3 rather than ubuntu219:08
naccgsilvapt: and you changed an unrelated chagnelog entry19:08
naccgsilvapt: finally there is no content to debdiff, that's just the changelog changes :)19:09
rbasakslashd: thanks for the ping. Sorry, it keeps being bumped by things :-/19:28
rbasakslashd: it's been long enough now I'll add it to my list of immediate highlighted todos.19:29
rbasakIt had almost fell off the page :-/19:29
slashdrbasak, no problem thanks for looking at it19:53
slangasekgsilvapt, wxl, jbicha: when all is said and done, is someone reverting the changes on https://help.ubuntu.com/community/ReportingBugs, or...?20:42
wxlslangasek: bdmurray asked that same question on the mailing list, so i take it he's leading the charge20:43
slangasekwxl: I bet he, like I, was trying to get somebody else to do it ;)20:43
bdmurrayHonestly, I'm not happy with either version but sorting it out isn't a high priority yet.20:44
jbichaI defer to bdmurray :)20:45
=== manjo` is now known as manjo
gsilvaptoh, so I need to work a lot on those. The UNRELEASED entry is not mine, or is it?22:23
gsilvaptnacc, first and foremost, thank you for the time reviewing this. Loads of lessons are being learned thanks to you!22:26
gsilvaptis there a way to cancel that commit so that I can start over? It somehow feels more adequate, considering I did changes to unrelated entries that I didn't even realize :|22:27
infinitygsilvapt: rm -r shadow-4.2 ; dpkg-source -x shadow_4.2-3.2ubuntu1.dsc22:29
infinityginggs: And try again from there.22:29
infinitygsilvapt: ^22:29
infinityginggs: Tab completion fail, ignore me.22:29
gsilvaptwill give that a try. Thanks, infinity22:29
infinitygsilvapt: Also, "Do the stuff bug #foo requests" isn't a useful changelog entry.22:29
infinitygsilvapt: You want something more like "foo.xml: Correct type in --switch-thing docs (LP: #12356)"22:30
ubottuLaunchpad bug 8012 in linux-source-2.6.15 (Ubuntu) "duplicate for #12356 other devices (sound, wireless?) fail to work when lp/parport modules are loaded due to IRQ conflict" [High,Fix released] https://launchpad.net/bugs/801222:30
Unit193type → typo22:31
infinitygsilvapt: Changelogs should document the changes done, not just document that "some change" was done. ;)22:31
infinityUnit193: That's the one problem you had with that? ;)22:31
gsilvaptHum, it makes sense. Thanks!22:31
Unit193infinity: Well that's the issue that jumped out at me enough to fix! :P22:31
gsilvaptI'll try to do it again22:31
infinity;)22:31
infinitygsilvapt: If you're ever use Windows and been frustrated by the fact that literally every Windows Update changelog entry is "Update Product: see KB123456", you'll understand why some people prefer changelogs to actually have useful information.22:33
gsilvaptYes, I understand. Was in a hurry at the time and did a poor job :)22:33
gsilvaptSorry. I'm starting over now22:33
gsilvaptCreating the changelog entry is actually really difficult22:43
gsilvaptI think I know how/why I deleted/changed an entry without even realizing it22:44
gsilvaptwhen doing dpkg-source --commit and after entering the patch name, it opens a menu with some info to fill in. Can/Should you remove anything in that file aside from those you have to actually edit?22:44
gsilvaptinfinity ^ (I keep forgetting to reference the people I'm calling out :D )22:46
infinitygsilvapt: Creating the changelog entry should be a simple matter of calling "dch -i"22:47
infinitygsilvapt: As for the patch headers, you should keep the relevant ones and delete the ones that don't make sense for your patch, yes.22:48
naccgsilvapt: i'm around again22:49
naccgsilvapt: yes, by default `dch -i` inserts an UNRELEASED entry22:49
nacci believe i said earlier, you need to mark it for artful22:49
naccrbalint: did you see my comment in the systemd bug? as to whether or not it's correct to never allow systemd-remount-fs.service to run in containers?22:51
naccrbalint: as i think there are advanced container configurations that use real disks22:51
naccrbalint: where we do want to remount them to match fstab22:51
rbalintnacc: yes, but one can easily override the stock .service file23:07
rbalintnacc: i see no clean solution here :-(23:10
naccrbalint: yeah, neither do I, but we'd need to document that in the 17.04 release notes, i think, as it's a change in behavior23:10
naccrbalint: if we decided to go that route, i mean23:10
rbalintnacc: one other not too clean option is diverting /lib/systemd/systemd-remount-fs in image generation to check "mount -f /" before actually doing the remount and reporting success when  "mount -f /"  fails23:14
rbalintnacc: quite ugly, but if there is a working / in fstab it gets remounted23:15
naccrbalint: yeah -- nothing is great. I was just reading `man systemd-remount-fs` and it indicates more than just / is handled by it (all kernel virtual fs, e.g.)23:16
naccrbalint: and specifically /usr for some reason23:16
nacccpaelzer: just to be sure, your lvm2 upload to zesty of 2.02.167-1ubuntu5, that was because ubuntu4 was accidentally uploaded?23:18
rbalintnacc: those mount points are typically set up properly in containers23:24
infinitynacc: Why do people have containers with bogus info in /etc/fstab to begin with?23:24
naccinfinity: cloud-image generation23:27
naccrbalint: i agree, they should be -- i just don't want to break anyone :))23:27
naccrbalint: if you're confident in the change, i'm cool with it, tbh23:27
infinitynacc: fstab(5) isn't a random dumping ground for garbage, it's a list of filesystems that the system *can* mount successfully, and the onus is on the sysadmin to make sure it's accurate (or on the image creator, if you're creating bogus ones out of the gate).23:27
rbalintinfinity: some ubuntu container images are preset with fstab containing LABEL=cloudimg-rootfs : LP: #157634123:27
ubottuLaunchpad bug 1576341 in open-iscsi (Ubuntu) "systemd in degraded state on startup in LXD containers" [High,In progress] https://launchpad.net/bugs/157634123:27
naccinfinity: CPC image generation that is :)23:27
naccinfinity: it's hardcoded in the CPC code23:27
infinityCode can change. :P23:28
naccinfinity: yeah, i have a note in there to figure that out23:28
naccinfinity: i think it's needed for VMs, possibly23:28
naccinfinity: but in containers it doesnt make sense23:28
infinityI'm just saying systemd isn't buggy here.  Perhaps a bit overzealous, but it's not a bug to assume entries in fstab should be mountable.23:28
naccinfinity: agree, and i wasn't suggesting to fix systemd in my original request23:28
naccmore that we needed to understand the issue and figure out the 'right fix'23:28
naccOdd_Bloke: rcj: --^ you may have input on the above too23:29
rbalintinfinity: if  generating separate container and vm images for cloud would be an option then we could go that way23:30
=== Guest7204 is now known as RAOF
rbalintnacc: maybe adding the diversion to only remount working / would be better, let's collect some feedback on the various options23:41
naccrbalint: ack, i'd like to hear from CPC too23:42
infinityrbalint: Is it really "the same image"?23:44
infinityrbalint: On cloud-images dailies, I see a -lxd.tar.gz, which would imply otherwise.23:44
infinityOh, that's also only 848 bytes. :P23:45
rbalintinfinity: definitely different :-)23:45
infinityWell.  That appears to be metadata about mangling/overwriting files.23:46
infinitySo, if could also whack fstab.23:46
naccinfinity: oh that's a good point23:46
naccso maybe stgraber *is* the one to ask :)23:46
infinitynacc: If official lxd images are our only concern, I think that's the right place to fix it.  If we want people to download our generic cloud images and run them in "any container" without that metadata mangling, a first-boot job that accomplishes the same thing would also be sane.23:55
infinitynacc: Which would need to run early enough that it gets there before systemd-remount-fs, obviously.23:55
rbalintinfinity: the image i got with the lxc command seems to be built with livecd-rootfs:23:56
rbalintroot@unified-ox:~# cat /etc/init/ttyS0.conf  | grep Cloud23:56
rbalint# CLOUD_IMG: This file was created/modified by the Cloud Image build process23:56
rbalintinfinity: but yes, probably it was post-processed23:57
rbalintinfinity: how do you feel about the local diversion?23:58
rbalintinfinity: "fstab(5) : stab is only read by programs, and not written;" :-)23:59

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