/srv/irclogs.ubuntu.com/2017/06/13/#ubuntu-devel.txt

mdeslaurnacc: I haven't had time to look at it yet02:25
mdeslaurnacc: I have to basically modify the tool to use the main/universe split instead of looking at the support period listed in the Packages files02:26
mwhudsonoh heh i made some uploads just after a kde update03:03
mwhudsonso i'll get my autopkgtest results next week then03:03
lathiate07:14
=== CRogers_________ is now known as CRogers
=== CRogers_________ is now known as CRogers
jamespageany arm* linker guru's able to help my understand why I see this linker failure on armhf only - https://launchpadlibrarian.net/323794587/buildlog_ubuntu-artful-armhf.ceph_12.0.3-0ubuntu1~ubuntu17.10.1+ppa11_BUILDING.txt.gz12:24
jamespage?12:24
seb128hum13:19
ginggsjamespage: i recognize the compiler warning, but can't see what the actual linker error is.  where can i find the source package?13:20
jamespageginggs: you can pull it from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2779/+packages13:21
ginggsjamespage: ta13:21
seb128the urls to download the debs from https://launchpad.net/ubuntu/artful/+queue?queue_state=0&queue_text= don't work13:21
seb128they lead to "Lost something?" launchpad pages13:22
seb128e.g  libebook-1.2-19_3.24.2-0ubuntu2_amd64.deb (69.7 KiB) NEW13:22
seb128-> https://launchpad.net/ubuntu/artful/+upload/15539512/+files/libebook-1.2-19_3.24.2-0ubuntu2_amd64.deb13:22
seb128cjwatson, wgrant, hey, do you know if that's a launchpad bug/known issue?13:31
cjwatsonseb128: https://bugs.launchpad.net/launchpad/+bug/1697680 - reported by Didier earlier today and I pushed an MP to fix it13:33
ubottuLaunchpad bug 1697680 in Launchpad itself "Can't access binaries in NEW queue (source packages assets are fine though)" [Critical,In progress]13:33
seb128thanks13:33
seb128sorry for not checking launchpad reported bugs first, I should know better13:33
cjwatsonseb128: interesting that we rolled out the change that caused that regression on 2017-05-11 and you both noticed it within hours of each other :)13:33
seb128(I had IRC closed during lunch so didn't notice that didrocks hit that earlier)13:33
seb128hehe, yeah13:34
cjwatson(it was a consequence of the fix for bug 1663334)13:34
ubottubug 1663334 in Launchpad itself "make queue files dget'able" [Low,Fix released] https://launchpad.net/bugs/166333413:34
seb128archive admin reviews are not going strongly nowadays :-/13:34
cjwatsonseb128: (you can use queue fetch as a workaround)13:34
seb128ah, nice to see those becoming dget compatible!13:34
seb128I did get the binaries from the build page13:34
cjwatsonor that, yes13:35
seb128they are just not marked as New so a bit of forth and back but it was ok :-)13:35
seb128thanks!13:35
cjwatsonnp13:35
ginggsjamespage: i'm gonna try building with --no-parallel in case that makes the build log easier to follow13:37
jamespageginggs: ok it will take some time...13:37
jamespageginggs: thanks for the help13:37
ginggsdoko and infinity know of that warning.  I started a wiki page to keep track of affected packages https://wiki.ubuntu.com/GCC7#arm_gcc_7_abi_transition . ceph is the first build failure I've seen, the others fail autopkgtests because of the warning13:41
ginggsjamespage: ^13:41
=== Tm_K is now known as Tm_T
rbasakcyphermox: please see bug 1624519 - I pinned it down. I think it's related to your merge of tasksel 3.34ubuntu1.14:35
ubottubug 1624519 in tasksel (Ubuntu) "Debian-defined tasks override Ubuntu-defined ones" [Undecided,Triaged] https://launchpad.net/bugs/162451914:35
naccmdeslaur: yep, just checking, we had one user respond in a different bug (php7.0-fpm MIR) and referred to that bug as to why the status is what it is. Presumably it's a cherry-pick(s) back from the yakkety version?15:29
mdeslaurnacc: no, yakkety doesn't contain a fix....the tools needs to work around the fact that the Support tag wasn't updated correctly in previous releases15:34
mdeslaurright now yakkety is ok, just because it's not an LTS release15:34
mdeslauractually, I'm not even sure if yakkety is ok15:35
naccmdeslaur: oh! :) it's marked fix released by bdmurray15:35
mdeslauryeah, it's complicated...some of the yakkety universe packages have "Supported: 9m"15:36
mdeslaurwhen in fact...they probably shouldn't15:37
naccmdeslaur: ok, it seems like you have a solid handle on it :)15:37
mdeslaurkind of :P15:37
kyrofaHey infinity, I've got a click patch for xenial that works, and I figured I should just bump the ubuntu2 to ubuntu3. However, there is no debian/patches currently, and I'm not sure how to build a source deb using the 0.4.43 orig tarball without debian/patches15:53
kyrofa(my debian packaging chops need some work, so I'm pleased I'm getting exposed to this, but I could use some guidance)15:54
nacckyrofa: d/p only exists if there are patches to apply?15:59
nacckyrofa: that is, if it's an upstream source change15:59
nacckyrofa: is it? (or what is the patch specifically)15:59
cjwatsonkyrofa: click is a native package.  don't use debian/patches/15:59
cjwatsonkyrofa: just apply the thing directly16:00
cjwatsonwell, its versioning isn't technically native, but still16:00
nacccjwatson: ah, makes sense16:00
kyrofacjwatson, yeah the versioning was throwing me off. I tried applying directly, but of course when I use the 0.4.43 orig tarball I get complaints of local changes. Should I not be using that orig?16:01
cjwatsonkyrofa: I would be inclined to construct a version along the lines of 0.4.43+16.04.20170613-0ubuntu1.  bileto should be able to do that for you if you give it the right input16:01
cjwatsonkyrofa: e.g. an MP that's based on the correct starting point16:01
cjwatsonkyrofa: "Revert to r606" in your MP - why?  Why not just branch from r606 in the first place?16:02
kyrofacjwatson, ah, which would be a new tarball, that does make things easier. infinity just asked for a debdiff, I shouldn't need to make a new MP unless you want me to?16:02
cjwatsonwell, your branch, not your MP16:02
kyrofacjwatson, because I don't know bzr :P . If I was to make a MP it would of course be cleaned up16:03
cjwatsonkyrofa: It would be preferable to figure out how to land this using bileto if possible16:03
kyrofacjwatson, okay16:03
cjwatsonkyrofa: I've pushed lp:~click-hackers/click/xenial, which should help you; it should be possible to branch that and use it as the target for an MP16:04
kyrofacjwatson, excellent, I'll do that, thank you16:04
rbasakxnox, slangasek, rharper: do we have a bug tag for the netplan server iso related work? Bug 1697730 is a candidate I think.16:29
ubottubug 1697730 in systemd (Ubuntu) "Long boot time due to systemd-networkd-wait-online.service failure" [Undecided,New] https://launchpad.net/bugs/169773016:29
slangasekrbasak: bugs are being linked from the blueprint https://blueprints.launchpad.net/ubuntu/+spec/foundations-aa-migrating-to-netplan16:31
slangasekrbasak: also, cyphermox16:31
rbasakLinked, thanks.16:32
ograwow, you re-vived blueprints ?16:32
slangasekthey've never been dead16:34
ograwell, others said differently :)16:34
ogragood to see someone still uses them16:34
=== zyga is now known as zyga-fedora
tdaitxbdmurray, to enable staging it's enough to just add a 'staging' in the crashdb-conf's ubuntu entry, right? after that, how do I access the staging error tracker?17:01
bdmurraytdaitx: No - that's for apport. To switch whoopsie you'd do stop the whoopsie service and manually start it via 'sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com'. Then go to errors.staging.ubntu.com/OOPS/$OOPS_ID.17:03
kyrofacjwatson, so do I target xenial in bileto, then?17:04
bdmurraysudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f'17:04
bdmurraytdaitx: ^^ that's what I really meant17:04
tdaitxbdmurray, right, thanks, I will check why it is duplicating the tag, it shouldn't... I used the same logic from other places and there was no duplication check, I might have missed something17:05
cjwatsonkyrofa: I believe17:07
cjwatsonso17:07
kyrofacjwatson, alright, build is running. That MP is very nearly a clean backport of the MP you already reviewed if you have time to take a look17:09
cjwatsonkyrofa: which MP?  I thought I just approved one17:11
bdmurraytdaitx: well if 'tag' not in report['Tags'] would avoid it17:11
tdaitxbdmurray, sure, I know, but does that mean that the other reports also duplicate the tag?17:12
bdmurraytdaitx: I don't know. Maybe apport should review the tags for duplicates or something. Its really not a big deal though.17:13
tdaitxbdmurray, if the tag is being added twice then all that hs_err logic is also being run twice, I would like to understand why - and yeah, I can cut it at the very first if (no need to run all that again)17:14
kyrofacjwatson, oh you were fast, thank you!17:16
=== JanC_ is now known as JanC
tdaitxbdmurray, alright, no duplication on staging, I believe it was the way I ended up running stuff... for some reason the update-notifier-crash service is not detecting my X session, so the service wont activate (not even manually)17:28
tdaitxI ended up running apport-cli and then also installed apport-noui17:28
tdaitxas I was doing stuff in parallel apport might have run through the report twice or something17:29
tdaitxstarting update-notifier-crash manually send the report to staging and there was no tag duplication, as expected17:30
tdaitxnow I need to check why that service believes there is no X session =/17:30
bdmurraytdaitx: That seems like a special corner case.17:31
fossfreedomHi all - our package budgie-desktop was sync from debian/experimental today - but it failed to build.  It builds successfully in pbuilder and also in our PPA. Any guidance that you can give me why buildd would produce a different build result?18:03
naccfossfreedom: in https://launchpadlibrarian.net/323780787/buildlog_ubuntu-artful-amd64.budgie-desktop_10.3.1-2_BUILDING.txt.gz search for FAILED18:06
naccUnknown option -lm18:06
naccRun 'valac --help' to see a full list of available command line options.18:06
naccfossfreedom: is that why?18:06
fossfreedomyup - but I'm struggling why buildd is failing but the same source builds in an artful PPA and also artful pbuilder18:07
naccfossfreedom: does your PPA have proposed enabled? or your pbuilder?18:08
jbichawhen did you build it in your artful ppa?18:08
fossfreedomno18:08
naccfossfreedom: the builder does18:08
naccfossfreedom: and there is a new valac in artful-proposed :)18:09
fossfreedomabout 10 minutes ago jbicha18:09
naccfossfreedom: 0.34.7-1 (a) and 0.36.3-1~gi1 (a-p)18:09
fossfreedomahhh18:09
naccfossfreedom: so presumably the new valac has changed flags somehow?18:09
naccfossfreedom: but enablign proposed should make it reproducible18:09
jbichavalac is stricter so I expect several packages to FTBFS :(18:10
fossfreedomokey dokey - will try that.18:10
naccjbicha: ah, interesting18:10
jbichavalac 0.36 is the same vala released with GNOME 3.24 a few months ago18:10
jbichathere was also a glib2.0 update this morning18:11
jbichathe glib update is still in -proposed18:12
fossfreedomok - thanks.  Yeah - enabling proposed killed the build.18:16
naccfossfreedom: gl! :)18:16
infinityfossfreedom: Looks like a meson/ninja (well, somewhere in the build system) bug to me.19:11
infinityfossfreedom: That -lm should be passed to the cc call, but not the valac call.19:11
infinityfossfreedom: Or maybe it's self-inflicted.  src/lib/meson.build has "meson.get_compiler('c').find_library('m', required: false)," which seems to be to be forcing it to add C-style linking to a vala project.19:20
fossfreedominfinity, agreed.  very odd.  Upstream confirms that they are using the same valac compiler version as in proposed.19:20
jbichafossfreedom: you could try disabling -proposed in your PPA and selectively copying packages into the PPA to see which ones fails the build19:21
jbichafor instance, upstream is likely not using the latest glib development release19:22
infinityBased on the error, it can really only be meson or valac.19:22
infinityEither valac stopped ignoring the incorrect option or meson started injecting it into the valac call.19:22
infinityBoth are new in -proposed.19:22
jbichaoh I forgot that meson was stuck in -proposed too19:23
kyrofainfinity, that xenial click SRU MP has been approved and bileto is all green. I'm nervous to hit "publish" though given that I'm targeting xenial. Is that the next step?19:55
kyrofa(cc cjwatson, although I expect you're asleep)19:56
slangasekthat is the next step. hopefully the ticket was set up correctly to target xenial, and not xenial overlay?19:56
kyrofaslangasek, indeed, xenial: https://bileto.ubuntu.com/#/ticket/281219:57
infinityOh joy, a bileto SRU.  My favourite.19:59
kyrofainfinity, join the club man :P19:59
kyrofaAlright I hit publish20:04
kyrofaslangasek, I'm getting a "packaging diff requires ACK" even though I checked the ACK box... does someone else need to do that?20:12
slangasekkyrofa: you must have upload rights on the package to ack the packaging changes20:12
kyrofaYep, not me then20:12
kyrofaIs that not redundant given an approved MP?20:13
slangasekno, it is not20:13
kyrofaI guess given the fact that multiple MPs could be included makes it possible to get weird results20:13
slangasekthere is no guarantee that the people approving the MPs on the upstream project have upload rights to Ubuntu either20:14
kyrofaAh of course20:14
slangasekin this case if it was approved by cjwatson, then yes - but bileto doesn't try to discover that20:14
slangasekpublish clicked to publish click20:15
kyrofaHaha, thanks slangasek20:15
kyrofaWhat's next regarding the actual SRU process? I've never SRUd with bileto before20:16
slangaseknext it goes into the unapproved queue for the release, and one of the SRU team members grumbles at having to review a package copy in the queue as it forces them to do a full download20:16
kyrofaOkay good deal20:17
naccanyone have a suggestion on a python packaging question? dep8 tests are failing with the new celery, but I think the underlying issue is actually that the tests are no longer packaged in python{,3}-celery, because they moved from (in the upstream src) celery/tests to t/. So the python debhelper doesn't see them as being part of the celery/ directory and doesn't include them. Is it appropriate for me to20:19
naccoverride the build step for this? Or is it ok to skip installing the tests (they are run at build time and pass)20:19
slangaseknacc: we do not normally expect tests to be packaged in order to be used for autopkgtest; they're usually run from the source tree of the package in question20:20
naccslangasek: right, i think the old dep8 test used the as-installed version. So it'd be ok to, in theory, run them from the src tree using the as-installed package20:21
slangaseknacc: yes, that would be preferred20:21
naccslangasek: ok, i'll work on tweaking those around, thanks!20:21
naccslangasek: hrm, i think i'm seeing a broken pattern in dep8 python tests using pytest. A lot of packages do (roughly): for p in python-versions; do $p -m pytest tests/; done20:58
naccslangasek: but that (per the upstream and manpage) adds '.' to the PYTHONPATH20:58
naccslangasek: so it ends up, depending on the package layout, testing the source contents, not hte as-installed python lib20:58
slangasekscore20:58
naccslangasek: if instead, one does pytest or (pytest-3) tests/, the tests use the system python as-installed libs20:59
naccslangasek: but then you can't make it a pretty loop (since the invocation name is different)20:59
naccslangasek: i'm not sure if i'm right, but i definitely see different behavior with celery based upon how in invoke pytest20:59
kyrofabdmurray, the newly patched click is now in the unapproved queue for xenial21:01
naccmdeslaur: rbasak: fyi, upstream apache has unmarked http/2 as experimental in 2.4.2622:23
nacchttps://httpd.apache.org/docs/2.4/howto/http2.html#comments_section and https://httpd.apache.org/docs/2.4/mod/mod_http2.html22:23
sarnoldsweet22:23
naccand that version *should* be coming out soon, and i'm happy to update us to it this cycle for security team's comfort22:24
naccsarnold: --^ just fyi22:24
Unit193That's also the first version with openssl 1.1 support.22:24
naccUnit193: good to know22:24
naccslangasek: --^ i guess you'd also be interested then :)22:24
Unit193(Though of course I'd prefer it not, because that'd hold Ubuntu back from switching this cycle.)22:25
sarnoldhasn't debian done the work to transition all but three or four packages to openssl 1.1?22:26
gsilvaptHas anyone ever experienced issues with descripts' wrap-and-sort? When I run the command it does nothing and there are stuff to be organized22:26
gsilvaptAnd I'm running in the right directory22:26
Unit193sarnold: They have libssl1.0-dev.22:26
naccgsilvapt: it's python :) should be easy to debug?22:27
gsilvaptnacc, the problem is that I get literally nothing22:27
gsilvaptI run wrap-and-sort and nothing. even using the verbose option22:27
Unit193nacc: If that's the case, I have another python breakage that I'd love to know what'sgoing on. :>22:27
naccUnit193: :)22:28
naccgsilvapt: which srcpkg (is it in the archive)?22:28
gsilvaptwhat do you mean? What package I'm trying to sort debian/control?22:28
naccgsilvapt: yeah22:28
Unit193sarnold: For kicks, http://paste.openstack.org/show/61247422:29
gsilvaptI've tried in several but the one I'm currently trying to work on is lskat22:29
naccgsilvapt: well, the b-d in that srcpkg are allready sorted and wrapped22:30
gsilvaptI'm locally testing the package22:31
gsilvaptI'm taking one line out of order22:31
sarnoldUnit193: that looks like a depressing story22:31
naccgsilvapt: works fine here (17.04)22:31
sarnoldUnit193: this looked like a story with a happy ending https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=82706122:31
ubottuDebian bug 827061 in release.debian.org "transition: openssl" [Normal,Open]22:31
naccgsilvapt: i edited one line out of order, ran the script and it put it back22:31
gsilvaptIt's super odd. I have no clue what could be causing this22:32
gsilvaptand I definitely don't want to re-format this machine again22:32
naccgsilvapt: are you on 17.04?22:32
gsilvapt16.0422:32
naccgsilvapt: like i said, it's a pretty straightforward script, add some debugging and see?22:32
naccgsilvapt: ok, let me spin up a container22:32
Unit193sarnold: Depends really, curl was built against 1.0 due to its library, but does support 1.1.  Some things do have support, if not just a simple rebuild then new upstream.  Ruby 2.4.022:32
Unit193Erm...Ruby is one of them, but Debian is skipping 2.4.22:33
gsilvapthow do I do that, nacc ?22:33
naccgsilvapt: well i was assuming you knew python :) you can add print()s throughout, though22:33
gsilvaptI assume you're suggesting adding that to the script's source?22:34
naccgsilvapt: yes22:34
gsilvaptI can give that a try . I need to find where it is located though22:34
Unit193(And like alpine, just have to wait for my sponsor to come back, and I can push the new version that supports 1.0 and 1.1.  Sadly, gvpe isn't there yet, so I'm really hoping Ubuntu stick with 1.0)22:34
naccgsilvapt: `which wrap-and-sort`22:34
sarnoldanonymous cvs, oy :)22:36
Unit193I did https://bitbucket.org/unit193/gvpe, but I haven't kept up with it.  You might remember it from me asking you about openssl incompatibilities a few releases back.  There was a protocol issue that wouldn't allow it to communicate, never found out why.22:38
slangaseksarnold: don't worry, it's anonymous cvs with pgp-signed commits22:39
mdeslaurnacc: awesome! (re: apache2)22:40
naccmdeslaur: i updated the bug as well22:40
gsilvaptnacc, the script stops at the get_files function. It's not working but it gives no error22:42
sarnoldis this the kind of error were watching what it does via strace is useful?22:43
naccgsilvapt: ok, still setting up a repro env22:44
gsilvaptok, I can wait. Thank you and sorry for the trouble22:44
naccgsilvapt: nothing to apologize for :)22:44
naccgsilvapt: works fine in a 16.04 lxd22:46
Unit193nacc: Ask him for the source package?22:46
naccgsilvapt: http://paste.ubuntu.com/24852460/22:47
naccUnit193: i was testing the srcpkg gsilvapt mentioned (lskat)22:47
Unit193Oooh,dang.  Missed that part.22:47
naccUnit193: np22:47
naccgsilvapt: when you say it 'stops' at the get_files function ... what did you mean?22:48
gsilvaptnacc, I basically add print() in all variables and it stops running after the get_files function because it is not searching for files properly22:49
gsilvaptIt sets an empty list as files22:49
gsilvaptIf files are empty, then there's nothing else to run...22:49
naccgsilvapt: yes, files is empty to start, the function attempts to find entries from SUPPORTED_FILES that match in the shell22:50
naccgsilvapt: where are you running the command?22:50
gsilvaptsource package parent directory22:51
naccgsilvapt: oh22:51
Unit193sarnold: Inconsequential PM?22:51
naccgsilvapt: you need to run it from the srcpkg directory itself22:51
gsilvaptI'm running inside lskat/22:52
sarnoldUnit193: any time :)22:52
gsilvaptinside lskat, there's the debian/ folder22:52
naccgsilvapt: oh ok, i misunderstood what you meant by 'parent directory' then22:52
gsilvaptIt returns errors when running inside debian/ or outside lskat22:52
naccgsilvapt: can you run the command (or alterations) as i showed in my paste? or use a paste and show me your alterations and the failure?22:53
gsilvaptSure, I can copy/paste the script in a bin and show you the output. Potentially I'm doing the print() thing wrong but it seems unlikely22:53
gsilvaptnacc, do you prefer just a diff between my changes and the original file or do you wanna see the full script?22:55
naccgsilvapt: well in theory we have the same script (wrap-and-sort) -- i meant can you do exactly the alteration i did in my paste (just moves one line) and then show wrap-and-sort failing to fix it?22:55
gsilvaptI didn't add many prints22:55
naccgsilvapt: a diff is fine too -- my point is, i'm not seeing hte problem (in 16.04 or 17.04)22:55
gsilvaptI have a different debian/control file here but sure. Fixes were proposed but not yet merge. It doesn't matter because it doesn't work anyway.22:56
gsilvapt1 second then.22:56
gsilvaptnacc, this is the debian/control file: https://paste.ubuntu.com/24852525/ Notice line 17 and 18 should swap. when I run wrap-and-sort -v, this is what I get (using the prints inside the script, otherwise it would return literally nothing): https://paste.ubuntu.com/24852530/22:58
naccgsilvapt: http://paste.ubuntu.com/24852550/23:01
naccgsilvapt: works fine in my 16.04 lxd23:01
gsilvaptWell, I can't figure out what is causing the issue23:01
naccgsilvapt: try spinning up a lxd and reproducing it in a clean env23:02
gsilvaptAccording to the print thing, it can't find any files but they exist23:02
naccgsilvapt: can you paste your change to the scrpit?23:02
nacc*script23:02
gsilvaptsure23:02
gsilvaptI don't think a diff is very understandable here. Can I just send a paste of the source?23:04
naccgsilvapt: that's fine too23:04
gsilvaptdiff or source?23:04
gsilvaptlol :)(23:04
naccgsilvapt: a diff is always understandable :)23:04
sarnolddiff -u is usually more understandible23:05
sarnoldunderstandable too23:05
gsilvaptSorry if I always get confused with regular diffs :P23:05
gsilvapthttps://paste.ubuntu.com/24852571/23:05
naccsarnold: true :) -- i mentally assume everyone is doing -urpN due to kernel work23:05
naccgsilvapt: yeah, do `diff -urpN old new | pastebinit` instead23:05
nacc*please23:06
gsilvaptAhhh, this now looks cute23:06
gsilvaptlol23:06
gsilvaptI'm so noob, oh god...23:06
gsilvapthttps://paste.ubuntu.com/24852585/23:07
naccgsilvapt: it's reversed, but that's ok23:07
gsilvaptI noticed, I should've switched the order but I guessed you'd understand23:09
naccgsilvapt: http://paste.ubuntu.com/24852599/ can you apply this and re-run the command?23:09
gsilvaptnacc, https://paste.ubuntu.com/24852616/23:11
naccgsilvapt: hrm, are your files for some reason executable?23:13
gsilvaptThe option is ticked, yes23:14
naccgsilvapt: hrm? i mean the files in your scrpkg23:14
naccgsilvapt: e.g., d/control itself23:15
gsilvaptThe option to run d/control as executable is ticked, yes23:15
gsilvaptAllow executing file as program23:16
infinitynacc: Hint, "pastebinit -f diff" even gives it pretty colours.23:16
naccinfinity: oh nice!23:16
naccinfinity: thanks :)23:16
naccgsilvapt: um, it shouldn't be23:17
naccgsilvapt: you made that change?23:17
naccgsilvapt: in the current ubuntu source package, the only executable in debian/ is 'rules'23:17
gsilvaptNot really23:17
naccgsilvapt: `wrap-and-sort` will not wrap or sort any executable file23:17
naccgsilvapt: i'm still not sure what you mean by ticked? cna you pastebin `ls -ahl debian/` ?23:18
gsilvaptOkay, makes sense. What did I do to have this setting all files as executables?23:18
naccgsilvapt: i have no idea :)23:18
gsilvapthttps://paste.ubuntu.com/24852653/23:19
naccgsilvapt: yeah that's ... wrong :)23:19
gsilvaptThis has to be a configuration issue then because I experienced the same issue in all srcpckgs23:19
gsilvaptDid I mess up permissions and such?23:19
naccgsilvapt: run `pull-lp-source lskat` in /tmp, say23:19
naccgsilvapt: does it have the same permissions?23:19
naccgsilvapt: do you have an odd umask set?23:19
gsilvaptAFAIK, no23:19
naccgsilvapt: you can check with `umask`23:20
gsilvaptWhat value should I get?23:20
naccdefault is 002223:20
gsilvaptI have 000223:20
naccgsilvapt: did `pull-lp-source` produce hte same permissions?23:21
gsilvaptI don't have the same permissions when using pull-lp-source23:21
gsilvaptThe other source was pulled from git23:22
naccgsilvapt: for comparison: http://paste.ubuntu.com/24852666/23:22
naccgsilvapt: hrm, maybe a git config ? pulled from where?23:22
gsilvaptYep, that's what I have23:22
gsilvaptHere: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/lskat/23:22
naccgsilvapt: and more directly to your paste earlier: http://paste.ubuntu.com/24852672/23:23
naccgsilvapt: with just a git clone?23:23
infinityPermissions look fine in git.23:23
gsilvaptyes23:23
gsilvaptI have nothing overriding permissions in my gitconfig23:23
naccgsilvapt: a fresh git-clone also shows them executable?23:24
gsilvapthttps://paste.ubuntu.com/24852686/23:24
gsilvaptOh, wait. I sent the wrong url23:25
gsilvaptBarr, too many tabs. Nevermind. Testing a new clone in a new folder. Potentially the issue is in the target directory I have been using23:25
gsilvaptYeap, that has to be it23:26
naccgsilvapt: ok :)23:26
gsilvaptSo I tried cloning in my home directory, permissions worked fine. I have a folder in an external drive in which I have everything related to projects. It's the only way I can have multiple packages and not run out of space (small 128 gbs SSD + 1 TB HDD)23:27
gsilvaptHow can I set up this folder in my HDD so that it doesn't mess up permissions?23:27
infinitygsilvapt: Is said external drive formatted with a sketchy filesystem, like vfat?23:37
naccgsilvapt: what infinity said would be my next suspicion.23:38
infinityI suspect either it's a filesystem that doesn't support permissions at all (like fat/exfat/vfat), or a "foreign" filesystem that supports POSIX permissions via a bit of translation trickery but mount often decides the "defaults" should be something weird (NTFS and HFS+).23:40
infinityIn the latter case, you can mount it differently and fix some of your woes, but honestly, you shouldn't do package build type work on a non-UNIX-friendly filesystem.  Too many build systems make too many assumptions.23:41
infinitygsilvapt: If 'stat -c%T -f /path/to/build/area' is anything other than 'ext2/ext3', 'xfs', or 'btrfs', your success rate is likely to vary.23:46
infinity(Yes, there are a ton more fully POSIX-compliant filesystems the kernel supports, but those are the only three that get enough use that I'm comfortable recommending them)23:46
infinityOh, and I guess zfs now.23:46
* sarnold puts down the zfs-advocacy megaphone23:48
infinitysarnold: I refuse to believe anything good has come from SunOS/Solaris since sendfile()23:50
slangasekhaha23:51
sarnoldinfinity: but you should see all the blinking lights during a scrub!23:51

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