/srv/irclogs.ubuntu.com/2014/07/15/#ubuntu-devel.txt

=== salem_ is now known as _salem
hallynslangasek: i'm doing another fresh jessie install so i can test the proposed cgmanager (and systemd-shim and lxc whiel i'm at it).  what will be the next step in getting cgmanager into experimental?00:32
slangasekhallyn: none; why would I upload it to experimental instead of unstable? ;)00:32
hallynslangasek: bc i originally tagged it with experimental? :)00:41
slangasekpssh :)00:43
mbiebl_ hallyn: please upload it directly to unstable00:46
hallynslangasek: should i change the changelog msg then?00:48
slangasekhallyn: if you wish, though I figure it's fair game for me to adjust that during sponsorship00:48
=== _salem is now known as salem_
hallynhm.  stgraber: do you think cgmanager in debian ought to mount name=systemd, or not?01:55
hallyni guess it should01:55
hallyn(else lxc fails)01:56
stgraberhallyn: yeah, it probably should. Maybe make this conditional to logind's presence?01:56
stgraberhallyn: as in [ -e /lib/systemd/systemd-logind ] && args="$args -m name=systemd"01:57
stgraberhallyn: hmm, actually, I think we want to do it unconditionaly01:58
hallynstgraber: mbiebl was talking about no longer having the logind start script mount the cgroups, so i think that could break01:58
hallynbetter to just always mount it01:58
stgraberhallyn: because otherwise if you have a host without logind but a container with logind, things will fail due to lack of name=systemd01:59
hallyngood point02:00
hallynall right lxc works fine in jessie with cgmanager;  one more rebuild of systemd-shim to test that bit02:13
=== superm1_ is now known as superm1
hallynslangasek: had to update http://people.canonical.com/~serge/cgmanager-0.27.1/cgmanager_0.27-1.dsc anyway for one more one-line fix, so i changed release to unstable.  works here with lxc and systemd-shim, so i'm now stepping back from it.03:20
=== hyperair is now known as Guest90316
=== maxb is now known as Guest41692
=== salem_ is now known as _salem
pittiGood morning04:06
pittiinfinity: ddeb deps> ah right; so I guess, time for a more intrusive rewrite then, and then I can avoid everything else which makes this thing so slow, and also avoid having to maintain the cronjobs every release04:07
pittidoko_: did you see that the new twisted seems to break quite a number of rdeps?04:08
pittihallyn: I can have a look04:08
pittihallyn: is there a github pull request or similar for that?04:09
hallynpitti: hey!  no pull request yet;  waht would the pull request be to?  desrt's tree?  (he has a cgm.1 branch which i'm based off of)04:13
hallynfor now it's just in github.com/hallyn/systemd-shim #cgm.204:13
pittihallyn: ah, ok, can look there04:14
hallyncool04:17
pittihallyn: might take a bit though, I'm currently swamped in requests/todos04:25
hallynpitti: understandable - going to bed now;  I can look for review/sponsor in #debian-systemd tomorrow if need be.  thanks in either case04:43
=== Aki-Thinkpad is now known as snakes
=== snakes is now known as _snakes
=== _snakes is now known as D8
=== D8 is now known as _8D
=== _8D is now known as _8D[_]
=== Lutin_ is now known as Lutin
=== Guest41692 is now known as maxb
Saviqseb128, hey, will you guys have time to review https://code.launchpad.net/~mterry/ubuntu-system-settings/locking-hash/+merge/224346 ?08:06
seb128Saviq, I wouldn't mind a review from the security team on that one, they had lot of good reviews comments and specific notes on the first review (see the bug report)08:07
seb128Saviq, I can have a look today but I want a security ack before approving it08:07
Saviqseb128, yeah sure08:07
Saviqseb128, we're working on it on that front as well08:07
seb128great08:08
=== doko_ is now known as doko
dokopitti, yep, not unusual08:32
TribaalHi all. I opened a branch against an ubuntu package and would appreciate it if someone could have a look at it (it's waiting for sponsorship - but I'd like to make sure I followed the process properly).09:27
TribaalHere's the bug: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523 A "just wait" answer would be good enough :)09:28
ubottuUbuntu bug 1341523 in ubumirror (Ubuntu) "Update to upstream 0.4" [Undecided,In progress]09:28
jamespagecjwatson, around? bug 1341618 just got bought to my attention09:34
ubottubug 1341618 in grub2 (Ubuntu) "grub 1.99-21ubuntu3.15 will not boot on some hardware" [Undecided,Confirmed] https://launchpad.net/bugs/134161809:34
cjwatsonjamespage: left a comment09:38
jamespagecjwatson, ta - i'll poke Spads again09:38
sil2100@pilot in09:39
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: sil2100
Spadscjwatson: I've asked the APAC folks who had first-hand experience to elaborate.  thanks.09:41
zygahey, I'm back from holidays and my sbuild/schroot setup is now broken (all utopic), I seem to get a message saying that my chroots are not owned by root (they are owned by sbuild)10:25
zygagoogling didn't really help me much10:25
zygathe exact message is:10:25
zygaE: sid-amd64-sbuild-625b5676-4967-4132-b55e-cd4d95cb5fe5: Failed to lock chroot: /var/lib/sbuild/sid-amd64.tar.gz: File is not owned by user root10:25
darkxstpitti, running a autopkgtest with build-needed, doesn't pick up the build depends from the main package?10:37
pittidarkxst: it does10:37
pittidarkxst: well, for building10:38
pittidarkxst: not for the test10:38
darkxstpitti, I have to use --disable-unit-tests on the main build or it fails (unless I override that with ||true)10:39
pittidarkxst: that's not indended -- building the package should behave like on a buildd10:40
darkxstpitti, tracker tests won't run in buildd10:40
pittidarkxst: so tracker's debian/rules shoudl already use --disable-unit-tests during build?10:40
pittidarkxst: sorry, I'm afraid I still don't understand the question/problem10:41
darkxstpitti, yes it does, we want to run the unit-tests but they can't be run at build time10:41
darkxstsince they need the tracker dbus interfaces10:41
zygahmm10:41
* zyga digs through schroot code to understand what is causing the problem10:42
pittidarkxst: yeah, sounds like these unit tests are rather broken :/ (they ought to start a private D-BUS instance with the locally built tracker)10:42
darkxstpitti, so right now I have a autopackage test with "make -c tests check"10:42
pittidarkxst: ah, wrapped in a dbus-launch or so?10:42
darkxstxvfb-run10:42
Saviqjodh, hey, on bug #1222705, do you have a phone with Ubuntu on it by any chance?10:44
ubottubug 1222705 in upstart (Ubuntu) "init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL" [High,Confirmed] https://launchpad.net/bugs/122270510:44
jodhSaviq: I don't have a phone (still waiting ... :)10:45
Saviqjodh, the most reproducible case is "restart unity8" on the phone for us, let me try and get you some logs10:45
jodhSaviq: thanks10:45
Saviqjodh, will try and reproduce on emulator, too10:45
zygahmm10:50
zygait seems that all chroot files need to be owned by root because of $reasons10:50
zygaok, let's try10:50
zyga\o/10:51
zygaok10:51
zygathat worked10:51
* zyga looks at schroot changelog10:51
darkxstpitti, so the tests run in a fresh chroot?10:52
pittidarkxst: yes, with only the test dependencies installed10:52
Saviqjodh, https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1222705/comments/1810:53
ubottuUbuntu bug 1222705 in upstart (Ubuntu) "init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL" [High,Confirmed]10:53
jodhSaviq: ta10:54
darkxstpitti, so would be better to --enable-unit-tests and ignore test failure on build, then just run the tests from autopkgtest?10:55
darkxstor add all the build-deps to the tests/control ?10:55
pittidarkxst: you can do that, or you find a way to just build the tests (make -C tests) and run them against the installed tracker10:56
jodhSaviq: could you also attach the /var/crash/_sbin_init.*.txt?10:56
pittidarkxst: you can add @builddeps@ to the test dependencies if you want to build stuff in your test script10:56
Saviqjodh, sure, let me get some symbols in it first10:56
jodhSaviq: thanks, if you could also trigger the crash with the Session Init running as 'init --user --debug', that would also be fantastic.10:57
Saviqjodh, hmm any idea how would I go about that with lightdm auto-starting the session?10:58
jodhSaviq: well you could just 'initctl log-priority debug' before starting the tests.11:00
Saviqjodh, oh yeah that'd work11:00
jodhSaviq: last time I checked, lightdm runs the script /usr/bin/ubuntu-touch-session which you could hack to add '--debug' if you'd prefer.11:01
=== pete-woods is now known as pete-woods|lunch
Saviqjodh, added two attachments to the bug, not sure if there's any more useful info11:20
=== MacSlow is now known as MacSlow|lunch
ukiIs there anyway I can easily have gdb with python2 support on ubuntu 13/14 instead of python3?11:53
ukiAll my gdb scripts are broken as the newer gdb uses python311:53
darkxstuki, you need to make your scripts python3 compatible11:57
ukidarkxst: any easier way to downgrade?11:58
darkxstuki, only if you rebuild gdb against python211:58
darkxstnot possible with archive versions11:58
ukiah i see, thats sounds good. so id have to "apt-get source", uncompress the deb and rebuild?11:59
ukidarkxst: ^^12:00
darkxstuki, I have never tried, its pretty easy to convert most scripts. but at the very least you would need to modify build-depends12:01
ukidarkxst: im comfortable with python3, yes, but im using an entire lib written for use within gdb thats written in python2. conversion isn't really desirable at this point.12:02
=== psivaa is now known as psivaa-off
darkxstuki, try run the scripts through 2to312:14
=== _salem is now known as salem_
sil2100@pilot out12:18
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
* sil2100 lunch12:18
=== MacSlow|lunch is now known as MacSlow
darkxstpitti, will xvfb-run pass through test errors? or do I need to trap them somehow?12:40
pittidarkxst: it passes through stdout/err and exit code, so no need for anything special12:41
sil2100@pilot in12:41
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: sil2100
darkxstpitti, so this should be fine then? http://pastebin.com/ESPq5FNs12:45
Saviqjodh, just reproduced the same crash under i386 emulator, do you know the steps to get one?12:45
pittidarkxst: if that builds the unit tests and works, it looks fine12:45
darkxstpitti, runs fine locally with adt-run12:45
pittidarkxst: @builddeps@ because "make -C tests check" actually builds more stuff than what gets build with dpkg-buildpackage?12:46
LocutusOfBorg1xnox, did you read this? https://github.com/performous/performous/commit/79eff6c44b76f26366588e12a606a77bd6e97a8312:46
LocutusOfBorg1:)12:46
darkxstpitti, yes, as mentioned earlier main build has --disable-unit-tests12:48
pittidarkxst: right, but the test doesn't call ./configure again, that's why I wondered; so if that make call does it, then fine :)12:48
pittidarkxst: btw, if that works, the tests should also work during package build if you run them through xvfb-run in debian/rules override_dh_auto_test12:49
Saviqjodh, https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1222705/comments/2412:50
ubottuUbuntu bug 1222705 in upstart (Ubuntu) "init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL" [High,Confirmed]12:50
darkxstpitti, no I tried that first, but they require the tracker dbus, which of course isn't installed (although I will file a bug upstream about fixing that)12:50
jodhSaviq: thanks, I'll ping you if I need anything else.12:50
Saviqjodh, cheers12:50
darkxstpitti, they also require a utf-8 locale and $HOME set, fwiw12:52
pittidarkxst: ah, ok; thanks!12:52
smbxnox, It is a rather minor issue but I thought to document it anyway. Now what again would be the package related to current desktop installer?13:12
cjwatsonubiquity13:15
sil2100@pilot out13:16
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== Sweetsha1k is now known as Sweetshark
=== pete-woods|lunch is now known as pete-woods
smbcjwatson, thanks13:38
=== timrc-afk is now known as timrc
kgunnChrisTownsend: hey there, i'd normally pester stephen on this...14:17
kgunnbut, we're getting darn close to landing qtcomp14:17
kgunnbut we need one mp (1 line change)14:17
kgunnhttps://code.launchpad.net/~gerboland/unity8-desktop-session/qtcomp/+merge/22588414:17
kgunnreviewed14:18
kgunnwould you mind ?14:18
kgunnthere have been a few of us that have tested the silo against unity8-desktop14:18
kgunnhttps://wiki.ubuntu.com/Unity8/QtComp14:18
kgunnand it worked fine14:19
ChrisTownsendkgunn: Hey.  Sure, I can take a look.  Is the suggestion that Stephen made been done?14:21
kgunnChrisTownsend: uh.... :P14:22
ChrisTownsendkgunn: Also, that MP is marked WiP, but I assume it's ready for review since you are asking me:)14:23
kgunngreyback: ^ yeah, can we flip the switch to review ?14:24
greybackkgunn: done. Unsure what checklist to enter though14:24
ChrisTownsendkgunn: And when you "tested in the silo", does that mean unity8-desktop-session is already in a silo and this just needs approved so it can be published?14:25
kgunngreyback: something sensible....like, no api break, been tested as part of https://wiki.ubuntu.com/Unity8/QtComp14:25
kgunnChrisTownsend: yes, its a collection of MP's that all have to go at once...and its been under test by us & the community for over a week now14:26
kgunnand something we need for rtm14:26
kgunnhence my underwear being slightly wadded14:26
ChrisTownsendkgunn: Ok, makes sense.  I wasn't sure if a new silo, etc. needed to be set up.14:26
ChrisTownsendkgunn: lol, we'll get it in.14:26
kgunnChrisTownsend: yeah, we're just in the process of collecting approvals....and will just flip the switch on that silo from testing to "attempt to land"14:28
ChrisTownsendgreyback: kgunn:  So is bregma's comment about this also needing to be added to data/unity8-mir.conf legit.  You say it works already, so maybe that's not necessary, but I'm just wondering if it still needs to be there just to be safe.14:29
greybackChrisTownsend: yep I just saw that. I'll do it to be safe14:29
ChrisTownsendgreyback: Cool, thanks.14:30
ChrisTownsendgreyback: Let me know when you have that pushed and I'll approve.14:33
greybackChrisTownsend: just pushed14:34
ChrisTownsendgreyback: Ok, thanks14:34
greybackthank you!14:34
ChrisTownsendkgunn: greyback: Approved14:35
greybackone down....14:35
kgunnwoohoo14:35
* ChrisTownsend Hopes kgunn's underwear is slightly less wadded.14:36
kgunnlol thanks ChrisTownsend14:37
ChrisTownsendkgunn: np!14:38
=== Sweetsha1k is now known as Sweetshark
Riddellmvo_: ping, are you able to help debug an apt issue with me?14:58
mvo_Riddell: maybe, what is the issue you see?14:58
Riddellmvo_: I'm making a new meta package14:59
Riddellfor kubuntu-plasma5-meta14:59
Riddellit's in the kubuntu-ppa/next14:59
Riddellbut when I apt-get install kubuntu-plasma5-desktop it doesn't want to install because powerdevil says it breaks on kde-workspace-data14:59
Riddellmvo_: how do I tell it it's fine to remove kde-workspace-data ?15:00
Riddellif I explicitly   apt-get install kubuntu-plasma5-desktop powerdevil  it's fine with removing kde-workspace-data and anything else that's needed15:00
mvo_Riddell: this is against utopic? give me a sec to see what the resolver tells me15:00
Riddellmvo_: yep15:00
Riddellmvo_:  sudo apt-add-repository ppa:kubuntu-ppa/next ; sudo apt-add-repository ppa:ci-train-ppa-service/landing-00515:01
mvo_Riddell: ok, give me a minute to setup a chroot15:02
Riddellmvo_: oh I have an ec2 if you give me your ssh key15:02
Riddellmvo_: ssh ubuntu@ec2-54-91-220-158.compute-1.amazonaws.com15:03
hallynmbiebl: slangasek: pitti: so systemd-shim is nto useful in experimental as is anyway, so could we upload the patched version to experimental as soon as cgmanager goes into unstable, to make progress with systemd-208 after it gets some wider testing?15:04
mvo_Riddell: thanks, I will use that then15:05
mvo_Riddell: you have not added the ppa in the ec2 instance yet, is that correct?15:06
mvo_Riddell: unicorns eh :) ?15:06
Riddellmvo_: I have, in /etc/apt/sources.list.d/15:07
mvo_Riddell: aha, what is the binary package name I need to install to trigger the problem?15:07
Riddellmvo_: I've only installed kubuntu-desktop, the issue is with kubuntu-plasma5-desktop15:07
mvo_Riddell: thanks, that was the name I missed15:07
mvo_Riddell: so apt tries to keep it because installing it would causing removals of a package with a higher "score", but there is something more going on it seems. with the ppa and the landing silo I can not install kubuntu-desktop ( kubuntu-desktop : Depends: plasma-desktop but it is not going to be installed)15:15
Riddellmvo_: I don't think I've tried that, plasma 5 overlaps with the old stuff in various places so I'm not trying to support going back the way15:16
mvo_Riddell: which seems to come from a conflict of plasma-workspace against klipper15:16
mvo_Riddell: aha, ok15:16
Riddellmvo_: so maybe I should just keep the name of the meta package the same as kubuntu-desktop15:17
mvo_Riddell: the breaks in powerdevil says "Breaks: kde-workspace-data (<< 4:4.98.0)" - would that be a option? a updated kde-workspace-data ?15:18
Riddellmvo_: nah kde-workspace is going away in plasma5 land15:18
mvo_Riddell: that may well make sense, if kubuntu-desktop is going to vanish15:18
mvo_Riddell: ok, that is good to know, give me a sec then15:19
mvo_Riddell: if its going away then you may simply add a transitional package for those, I don't really know much about the way kde is packaged (or develooped :) so take my advice with a grain of salt. but if it is not co-installable, well :)15:21
Riddellmvo_: hmm yes that's another idea15:23
mvo_Riddell: a direct conflict/break in the kubuntu-plasma5-desktop would also work15:23
Riddellaah yes15:23
Riddellgood, I'll play around, thanks mvo_15:24
mvo_Riddell: good luck and sorry that this is so complicated, I wonder/wondered if it would be worth  to add/support a "obsoletes" tag just like in rpm15:24
sil2100didrocks: so, I was wondering... since in cu2d whenever, let's say, the cu2d-apps-head-2.1build job has finished with success, jenkins automatically started the cu2d-apps-head-2.2check job15:41
sil2100didrocks: while I didn't see any triggers configured from the jenkins side15:41
sil2100didrocks: nor in the cu2d scripts being executed15:41
didrockssil2100: there was master job IIRC15:41
didrockslet me check15:42
sil2100Ah15:42
sil2100!15:42
didrockshttps://wiki.ubuntu.com/DailyRelease/StackPublish#Different_phases_of_one_stack15:42
didrocksthis diagram can help15:42
sil2100didrocks: I see the job, hah, makes sense now15:43
didrocksso…15:43
sil2100Thanks!15:43
didrocksyou have the master job15:43
didrockswhich triggers the prepare jobs15:43
didrockswhich was traking the prepare-project ones, one per project on that stack15:43
didrocksthen, master was chaining (once prepare finishes successfully or only having warnings) to 2 jobs in parallel15:44
didrocksbuild and check15:44
didrocksboth were chaining to the publish one15:44
didrocksthis is a simplified case, there is the waitonstacks in reality, but not needed for that demonstration15:44
didrockssil2100: does that make sense? ^15:44
sil2100didrocks: makes sense indeed, thanks :)15:47
didrocksyw ;)15:47
=== lutostag_ is now known as lutostag
bdmurrayxnox: did you have a look at the issue regarding Contents.gz or did we win the race condition?16:37
brendanddoes anyone know how to use a binary from the build at build time?17:00
brendandi want to use a binary provided by the package i'm writing tests for, in the tests17:00
cjwatsonmangle paths, or run the tests in question via autopkgtest17:01
xnoxbdmurray: no, not yet. will look into it today.17:17
xnoxLocutusOfBorg1: \o/17:18
xnoxsmb: so which bug did you file about ubiquity?17:19
=== roadmr is now known as roadmr_afk
smbxnox, bug 134207118:01
ubottubug 1342071 in ubiquity (Ubuntu) "Invisible installer dialog on VM iso installation" [Low,New] https://launchpad.net/bugs/134207118:01
smbinstaller dialogue is a bot off as I mean the "eject media and press enter" back on the framebuffer18:02
=== alexisb is now known as alexisb_lunch
xnoxsmb: yeah. and i don't know how to make it more reliable.18:14
=== rpadovani_ is now known as rpadovani
=== lubko is now known as zmok
smbxnox, Hm, ok. Probably I should investigate a bit more into it. I was not sure it ever really was brought up and I get surprised every cycle when I play around with VM installations :-P18:18
smbAt least as long as I do them manually and not through netinst18:19
xnoxsmb: i think we should be doing systemd style pivot into a shutdown initramfs that shows that text....18:20
xnoxsmb: at the moment however it's a jumbo between kernel, plymouth messages and that text.18:20
smbxnox, Yeah, this has been a pain in other senses as well (racing on the way up). Though I cannot help myself from being doubtful that systemd is less painful when taking over the world.18:22
xnoxsmb: i haven't yet planned how to do ubiquity with systemd.18:33
xnoxsmb: i believe we will have to conflict and/or replace targets. or something like that.18:33
smbxnox, Its not so much knowledge that makes me doubtful. Though I cannot decide myself whether I should call it pessimistic or realistic. >:)18:36
=== roadmr_afk is now known as roadmr
=== timrc is now known as timrc-afk
brendandis there any variable i can use in debian/rules to reference the directory like 'build-area/url-dispatcher-0.1+14.10.20140619/obj-x86_64-linux-gnu'19:24
brendandi.e. the directory where binaries are built into19:24
* hallyn feels all accomplished now that he created a debian mentors account19:33
hallynslangasek: dunno if it helps in anyway, but i pushed cgmanager to mentors.debian19:34
xnoxhallyn: \o/19:53
xnoxhallyn: let me review that =)19:53
xnoxhallyn: well there are lintian errors already =)19:53
hallynxnox: the bad-distribution-in-changes-file unstable error?19:57
xnoxhallyn: nah, I'll comment on mentors, I see a few other issues.19:57
hallyncool, thanks19:57
=== timrc-afk is now known as timrc
hallynxnox: when responding to feedback with a new pkg, do i bump the version as i would in archive/ppa, or do i just delete and re-upload?20:14
hallyn(re-upload would be suboptimal as feedback-as-teaching is lost)20:14
xnoxhallyn: well, with mentors.20:17
xnoxhallyn: you would keep the version the same, but keep adding things in the changelog.20:17
xnoxe.g. * Fixed foobar and bar in jars.20:17
xnoxhallyn: and published a second comment about binaries.20:18
hallynxnox: i did look for an ITP bug to close, but didnt' see one.  the, uh, other cgmanager upload didn't close one so i assumed that was an optional formality.  is it not?20:24
xnoxhallyn: in Debian, the person who "Intends To Package" should open an "Intends To Package" bug against "WNNP" package. And close it on the first upload into debian.20:26
xnoxhallyn: I don't see any prior uploads in Debian.20:26
xnoxhallyn: there is no ITP bug equivalent in Ubuntu.20:26
xnoxhttps://www.debian.org/devel/wnpp/20:27
hallynxnox: right, there is a cgmanager (0.20 version) upload to ftp.debian somewhere.  that's the one i meant.20:27
hallynok, will open that bug then20:27
xnoxhallyn: you may use $ report-bug or just construct email by hand. They are cc'ed to debian-devel by default, so you can see plenty of examples.20:28
xnoxhallyn: i really don't see cgmanager 0.20 upload, that got accepted.20:29
hallynit didn't get accepted20:30
=== alexisb_lunch is now known as alexisb
hallynargh, i hate the symbols files :)20:38
dokoxnox, please don't revert gobjc back, won't help, and won't help for gfortran either. tvoss did promise to be ready today, so we can point to 4.9 again21:07
xnoxdoko: why will it "won't help" ?21:10
xnoxdoko: and it's not a revert, per se. At the moment a non-matching library was getting installed for the default compiler... Not sure how fortran operates, but it seems to be buildable.21:11
xnoxdoko: unlike fortran, which is a binary in path, cc1obj is just an internal gcc private executable. one uses gcc to compile objc code.21:12
dokoxnox, same as f95121:19
xnoxdoko: ok, so when you/slangasek reverted to 4.8, why was it not done for gobjc, gojbc++ and fortran as well? given that it left those in complete FTBFS state.21:20
xnox(in -proposed and -release)21:20
dokoxnox, because fortran is an ABI transition which already was in progress21:23
slangasekxnox: because we were implementing an immediate short-term fix for a critical phone issue, leaving a few packages ftbfs in the short term is acceptable collateral damage in the general case21:23
dokoand I didn't want to investigate if it is safe to revert gobjc21:23
slangasekxnox: and gcc-4.9 is supposed to be made the default again RSN21:23
dokoif you did investigate, then sure, that might be safe21:23
=== salem_ is now known as _salem
hallynxnox: looking at the dpkg-gensymbols output for libcgmanager0, it gives me symbol@Base...  with netcf it gives me symbol@NETCF_version.22:21
hallynproblem with my .pc file?22:22
xnoxhallyn: not the .pc file -> that one just encode paths to your header files & which libraries to link/depend on.22:27
xnoxhallyn: if you want to version your symbols, you'd need to use libtool symbol versioning facilities.22:27
hallynxnox: and if i don't want to?22:28
* hallyn looks to see what doing that might entail22:29
xnoxhallyn: you are fine just as it is. if later you want to update a symbol you would be able to provide two versions of the same symbol and mark one of them the default.22:30
xnoxhallyn: or like, just don't break you api/abi =)22:30
hallynxnox: but then how do i generate a symbols file,22:31
hallyni thought the "*@LIB_version package-version" was the whole point22:31
xnoxhallyn: the debian/libcgamanger0.sybmols?22:31
xnoxhttps://wiki.debian.org/UsingSymbolsFiles ?22:32
xnoxhallyn: the point of debian/*.symbols file to list _all_ symbols and when they were introduced. Such that you can catch if they change or get removed, and also get correct dependencies depending on which apis are used.22:37
hallynyeah that's where i'm looking.  that gives me a huge list, which you seemed not to want for netcf22:37
hallynok - i'll upload with the results of that- thanks22:38
xnoxhallyn: right, so netcf is special. Upstream has versioned all of their symbols very tightly, hence debian/libnetcf1.symbols is ok to use wildcards to get all symbols covered.22:38
xnoxhallyn: but that doesn't help to catch, if e.g. upstream make a mistake.22:39
xnoxhallyn: e.g. I like dbus-cpp symbols files the best.22:40
hallynnetcf does that in src/netcf_public.syms?22:40
hallyndbus-cpp symbols?22:40
hallynthe package?22:41
hallynnope22:42
xnoxhallyn: this symbols file for libcgmanager is correct one http://paste.ubuntu.com/7800703/22:42
hallynxnox: ok, that's what i've got (except 0.27 :)22:43
xnoxhallyn: in libnih, we do version symbols using a libtool versioning script e.g. https://github.com/keybuk/libnih/blob/master/nih/libnih.ver hence they are not @Base.22:43
xnoxhallyn: so just stick that into debian/libcgmanager0.symbols and you are done.22:43
hallynxnox: thanks.22:43
hallynxnox: (still looking at dbus-cpp)22:45
xnoxhallyn: that one is c++ hence symbols are different per-platform and 32/64/big/little.22:45
mbieblcyphermox_: calestyo being pleasant as always (re that NM bug)23:00
mbieblanyway, since we basically all agree, I'll try to cook up a patch and run it by you23:00
cjwatsonbrendand: "build-area/url-dispatcher-0.1+14.10.20140619" is almost certainly just your current directory; no need to put that together.  For the rest of it you want "obj-$(DEB_HOST_GNU_TYPE)".  You should normally put "DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)" near the top of debian/rules to make sure that variable is initialised.23:05
cjwatsonbrendand: But "obj-$(DEB_HOST_GNU_TYPE)" is something that your package's own build system controls - it's not set by anything central.  So if your package is buggy it's possible it's being set from something else, e.g. DEB_BUILD_GNU_TYPE.  You should really grep your package's source code to find out where that's set.23:06
cjwatsonbrendand: Or perhaps your package's build system.  For instance some cdbs classes set $(DEB_BUILDDIR) to that.23:06
cjwatsonOr indeed some debhelper modes.23:07
infinityrobert_ancell: 1:2.8.3-0ubuntu1build1 really?23:30
infinityrobert_ancell: ITYM -0ubuntu2 ;)23:31
robert_ancellinfinity, which package?23:32
infinityrobert_ancell: That was calligra.  I noticed it cause I was looking at the FTBFS.23:32
robert_ancellAh, I think I did that because I don't have access to lp:~kubuntu-packagers/kubuntu-packaging/calligra23:33
robert_ancellbut I'm not sure it's valid :)23:33
infinityrobert_ancell: For future reference, "dch -R" intelligently does the right thing (-NbuildN for unmodified Debian stuff, increments -NubuntuN for not)23:33
robert_ancellta, didn't know that23:33
infinityrobert_ancell: Oh, if it was intentional cause you expected them to throw it away, that sort of makes sense, ish. :)23:34
robert_ancellyeah.23:34

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