/srv/irclogs.ubuntu.com/2013/05/20/#ubuntu-devel.txt

vipzrxhello02:53
=== NCommander is now known as Guest75457
vipzrxhello ,everyone03:25
=== jono is now known as Guest9541
Noskcajif kirkland or andreseal is online, get them to ping me please06:31
=== ckpringle_ is now known as ckpringle
jamespagejodh, around? have you seen upstart doing something like this before: http://paste.ubuntu.com/5683425/11:37
cjohnstoncjwatson: I believe /711:47
cjohnstonsorry. I believe I have an email pending on ubuntu-devel.. when you get a chance, could you please ack it11:48
=== Ursinha-afk is now known as Ursinha
cjwatsoncjohnston: done11:53
cjohnstonty cjwatson11:53
=== mmrazik is now known as mmrazik|afk
jodhjamespage: it looks correct based on what the somewhat elaborate .confs specify. I've never used ceph though :)12:51
jamespagejodh, the ceph processes are OK - I just wondered why there are not proc 1 owned (the sh wrapper is)12:52
jamespagei.e. init -> sh -> ceph-mon for example12:53
jodhjamespage: because the job doesn't specify "exec" in the script stanza so upstart spawns ad shell to run what is in that stanza.12:53
jamespagejodh, "exec /usr/bin/ceph-mon --cluster="${cluster:-ceph}" -i "$id" -f"12:53
jamespagelooks OK to me12:53
jamespagejodh, full listing - http://paste.ubuntu.com/5683597/12:55
cjwatson${cluster:-ceph} requires a shell to evaluate it12:55
jodhjamespage: ah - well, upstart cleverly detects that the exec line specifies shell syntax, and so passes the arguments through /bin/sh for you (otherwise, it wouldn't work :)12:55
cjwatsonSee init(5) - "Any special characters, e.g. quotes or `$' specified will result in the entire command being passed to a shell for expansion."12:55
jamespagecjwatson, jodh: ah! right - I thought it might be something like that12:55
jamespagethanks12:55
jodhjamespage: in your case, "$" is used, which causes the shell to be spawned.12:56
=== _salem is now known as salem_
=== mmrazik|afk is now known as mmrazik
=== wedgwood_away is now known as wedgwood
=== francisco is now known as Guest18525
=== hatch_ is now known as hatch
cjwatsonAny MIR folks want to have a look at graphite2?  It's a bit inconvenient for texlive to be uninstallable in saucy-proposed.14:27
=== Ursinha_ is now known as Ursinha
infinitycjwatson: It has no bug filed.14:29
infinitycjwatson: (Also, I'm about to go nap, yay long weekend, but if someone like jdstrand or mterry doesn't beat me to it, I'll look at it when I wake up)14:30
ogra_oh, canada too ?14:30
cjwatsonYeah, I was tracking down the version of texlive-bin that introduced the build-dep before filing a bug14:31
cjwatsonBut it's not in the changelog so that's involving a bit of downloading14:31
infinityHrm.  If graphite2 is a simple evolution of silgraphite2.0, you can just promote it without an MIR.  You might want to poke the sources and see if it's just a renaming of the upstream project.14:31
cjwatsonOh, hadn't twigged to silgraphite2.014:31
cjwatsonI'll see if the build-dep changes bear that out14:32
=== mitya57 is now known as mitya57_
cjwatsonLooks like libgraphite-dev (>= 1:2.3.1) -> libgraphite2-dev14:33
cjwatson-  --with-system-graphite  use installed silgraphite headers and library14:34
cjwatson+  --with-system-graphite2 use installed graphite2 headers and library14:34
infinitycjwatson: Yeah, I was more curious if it really is basically just a new version of the same source.14:34
infinityOr if it's an entirely new and differently sketchy version of a similar library.14:34
cjwatsonAlso would be nice if we could only have one in main14:35
infinityYeah, that's probably easily solved.  libgraphite3 has almost no rdeps.14:36
cjwatsonHmm.  If it's the same thing, it's laid out very differently.14:37
infinity*&%! tarball-in-tarball packaging of silgraphite2.0 makes diffing a bit of a pain. :P14:37
* infinity unpacks.14:37
cjwatsonThough graphite2's debian/copyright says http://sf.net/projects/silgraphite14:37
cjwatsonWhich says "Graphite2, a new version of the Graphite engine"14:38
tumbleweedtarball-in-tarball isn't dead yet? :/14:38
tumbleweedinfinity: are there any significant differences between PPA and primary archive chroots / environment? I'm trying to figure out why pypy PPA builds are hanging on a particular test14:39
infinitycjwatson: The layout's completely different, but if the upstream's the same, I'm all for screaming "la la la", and swapping them.14:39
cjwatsonThere seems to be a kind of spiritual ancestry here but I'm getting more of a rewrite-from-scratch sense14:39
infinitycjwatson: texlive is the only thing in main that depends on it.14:39
infinitytumbleweed: The chroots are identical, installed packages could differ if you haven't let your PPA depend on -proposed (it's a twiddle), and kernels could be different (virtual PPAs are hardy kernels on Xen, non-virt builders are precise kernels on bare metal)14:41
cjwatsonhttp://projects.palaso.org/projects/graphitedev/wiki14:41
cjwatsonOh, I guess c-m-proposed doesn't want to drop silgraphite2.0 yet because binary deps aren't yet up to date14:41
tumbleweedinfinity: ok, that gives me some things to play with. thanks14:41
cjwatsoninfinity: OK, sounds like "swap it", then - I'll make that happen today14:42
cjwatsonI have a bit of a chain of stuff on top of this.14:43
infinitycjwatson: Bonus points if we could ditch the old one entirely, but who knows if pango-graphite is ported.14:43
cjwatsoninfinity: Probably have to wait for Debian there14:44
infinitycjwatson: We didn't end up breaking the world with a tex transition this time at least, I hope?  Just this component oops?14:45
* infinity has nightmares about having to rebootstrap tex* crap yet again.14:45
cjwatsonHope not, but can't tell yet.14:45
cjwatsontexlive-bin doesn't seem to have tight build-deps.14:46
infinityWell, the killer used to be that we carried a delta on exactly one tex* package, and if we let autosync sync the rest, it would skew and none of it would build anymore.14:46
cjwatsonOr indeed to build-dep on anything texish.14:46
cjwatsonI *think* we got rid of that delta ...14:47
cjwatsonWasn't that tex-common?14:47
infinityYeah, that delta was in texlive-bin, I think.14:47
cjwatsonI've spent the best part of a day cleaning up bits in -proposed.  I should probably do some actual work at some point ...14:48
infinityHeh.  At least it was your work day.14:48
cjwatsonhttps://launchpad.net/builders/ - are the armhf builders a bit sad?14:48
cjwatson47 minute queue, allegedly 7 builders idle.  I suspect porkies.14:48
infinitycjwatson: They lost track of a PDU that happened to be the only way to stab a bunch of the Pandas, so as they've been dying for other reasons, they've been unrecoverable.14:48
infinityI'm told this is in progress.14:49
cjwatsonOh dear14:49
infinityThe idle buildds are suspicious, though.14:49
cjwatsonYeah, sounds more like buildd-manager fail.14:49
infinityThat could be a Network Event causing a mass Right to Choose exercise.14:49
NikThHello everybody.14:51
infinityAnyhow, I'm going to go enjoy my freedom to not be tied to a laptop for a day.14:52
NikThQUESTION: Do I have to do something special in order for debuild to sign a .dsc file when I want to upload a custom kernel on a PPA of mine ?14:52
infinityNikTh: Just run "debsign foo.changes" on the changes file that you plan to upload.14:53
NikThI uploaded without problems a custom package of unity-tweak-tool in my PPA ..14:53
NikThBut I'm not able to debuild correctly a custom kernel. Deubild does not product a .dsc file (only source.changes is not enough)14:54
NikThinfinity: Thanks I will try that immediately14:55
NikThI will describe here step by step what I'm doing right now.. (anyone who wants to help.. welcome)14:56
NikTh1) I'm downloading the source code of linux-image-3.8.0-21-generic14:56
NikThI'm patching the kernel.. "patch -p1 < ~/foo.patch14:58
NikTh3) Now editing the changelog file (dch -i)14:59
NikThOk, what is the next command ?15:00
NikThdebuild -S -sd -k<keyid> , is that correct ?15:01
NikThThe results are "Successfully signed changes file" (but not .dsc file created)15:06
cjwatsonNikTh: You're making life hard for yourself by passing -sd.  Why?15:15
cjwatsonI never use -sd.15:16
cjwatsonNikTh: But as for the rest of it, debuild -S should be sufficient to create a .dsc.  Post the whole output on a pastebin.15:16
NikThcjwatson: because the source code already exist in Ubuntu repositories. Despite that I used debuild -S -k (without -sd) but the results were the same.15:17
infinityNikTh: Also, due to the hilarious way the kernel is packaged, dch -i won't do what you think it will.15:18
infinityNikTh: It's going to update debian/changelog, and then when the clean target runs, debian.master/changelog will get copied over debian/changelog. :P15:18
NikThFull terminal results here: http://pastebin.com/mKbn2ggu15:20
NikThYes, yes, yes you have right about this infinity . Overrides my debian/changelog. But how can I fix that ? So I told before that MY source.changes file is exactly the same as the original :P  LoL15:21
infinityNikTh: "dpkg-source: info: building linux in linux_3.8.0-21.32.dsc"15:22
infinityNikTh: It built just fine, just with the old changelog.15:22
NikThHahahaha15:22
infinityNikTh: So, do your 'dch -i', then "cp debian/changelog debian.master/changelog", then do your debuild.15:22
NikThhmm.. lets see15:23
cjwatsonNikTh: already exists> -sd is not as necessary for that as you think it is.15:23
NikThcjwatson: I've read the instructions here> https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage (see the "options when building" paragraph)15:25
cjwatson-sd only makes any difference if you are packaging a *new upstream version* and have some specific reason not to include the upstream tarball in the upload.  Which is basically never the case - I haven't needed -sd in 14 years of development.15:25
cjwatsonYeah, that advice is, well, maybe not wrong as such but pointless.15:25
cjwatsonYou can quote me on that.15:26
cjwatsonAnyway, it's not actually the problem here, just a confusing red herring.15:26
cjwatson-sa *is* sometimes needed because, unlike Debian, our versioning for new upstream versions isn't nearly-always predictable by dpkg-genchanges.15:27
NikThThanks cjwatson . I have no reason to doubt about your development skills. I'm a newbie in ubuntu-devel and just followed the instructions there :-)15:27
cjwatsonYeah, I appreciate that it's often easiest to just follow the docs.  I didn't realise we were recommending -sd to people.15:28
NikThOK, now I did what infinity suggested (cp debian/changelog ...etc) . What is the most correct command for debuild ? debuild -S -k<keyid> (correct cjwatson ? )15:31
=== ckpringle_ is now known as ckpringle
cjwatsonYep, that should be fine.  You can put DEBSIGN_KEYID=<keyid> in ~/.devscripts so you don't have to type it all the time.15:32
cjwatsonSo most of the time for ordinary uploads I just use 'debuild -S'.15:32
NikThThanks !15:32
iBelieveI sent a message to the ubuntu-devel mailing list about a week ago with an idea for Click Packages, but I don't think it ever got posted (I checked the archives, and it isn't in there). Is there a way to see if it got sent to the list, or should I just resend it?15:34
cjwatsonit's probably in the mod queue15:35
cjwatsonI've flushed the remaining click-package-related things out of there now15:35
iBelievecjwatson, thanks, that is what I thought, but it just seemed a long time15:38
cjwatsonyours was in there15:38
iBelievecjwatson, good, that's nice to know that it actually did send.15:39
NikThVictory !!!15:40
NikThinfinity, cjwatson  !! Thanks a lot. :-)15:40
rbasakinfinity: I've redone the facter merge and included SRU debdiffs for precise, quantal and raring in bug 1173265 - also including a fixes for bug 1170325. Could you have a look when you get in, please?15:40
ubottubug 1173265 in facter (Ubuntu) "facter fails to run from rebuilt source package" [High,Triaged] https://launchpad.net/bugs/117326515:40
ubottubug 1170325 in facter (Ubuntu Raring) "Facter 1.6.X not considering Qemu/KVM virtual type" [Undecided,New] https://launchpad.net/bugs/117032515:41
infinityrbasak: Long weekend here (I'm both asleep and not at my computer, and possibly also partying and drunk right now), but if you poke me tomorrow, I'd be happy to review and sponsor the lot. :)15:42
rbasakinfinity: will do - thanks!15:47
NikThAnd the e-mail just arrived " Accepted: " :-) :-)15:50
=== sil2100_ is now known as sil2100
=== mmrazik is now known as mmrazik|afk
sil2100Hello, is there anyone from the SRU team here right now?16:40
zequenceI'd like some help with targetting this bug to releases quantal and precise https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1163638, anyone?16:50
ubottuLaunchpad bug 1163638 in pulseaudio (Ubuntu) "pulseaudio fails to release card to jack" [Undecided,Confirmed]16:50
bdmurraykirkland: do you have any plans to SRU bug 1173209?  If not I'll work on it today.16:52
kirklandbdmurray: go for it16:52
kirklandbdmurray: I'll verify it for you, if you like16:52
bdmurraykirkland: I'll let you know thanks16:52
kirklandbdmurray: thank you!16:53
ubottubug 1173209 in ubuntu-release-upgrader (Ubuntu Raring) "Prompted about New Release for 13.04 again after dist-upgrade and a restart" [Low,Triaged] https://launchpad.net/bugs/117320916:54
=== awe_ is now known as awe|lunch
=== Ursinha is now known as Ursinha-afk
psusishouldn't /etc/os-release identify the specific ubuntu flavor installed?  i.e. Ubuntu Studio or kubuntu?17:25
Riddellpsusi: they're all the same os17:26
psusihrm... I guess so..17:30
iBelieveI've reinstalled Ubuntu several times for various reasons (switching derivatives, etc) so now I have 3 OpenPGP keys (a new one and 2 old ones). Do I need the old ones, or can I delete them?17:57
=== Ursinha-afk is now known as Ursinha
iBelieve^^ OpenPGP keys in my Launchpad account.17:57
=== barry` is now known as barry_
=== barry_ is now known as barry
tumbleweediBelieve: if you aren't going to be signing things with the old ones, you don't need them18:12
iBelievetumbleweed, since I don't have them on my computer, no I won't be. Will deleting them affect things that I've already signed, like the Code of Conduct or projects I've contributed to?18:14
tumbleweedno18:14
tumbleweedin future, I recommend revoking keys before you lose control of them (or just back them up)18:15
iBelievetumbleweed, Okay, thanks for the help and advice.18:17
stgraber@pilot in18:27
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.04 released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: stgraber
lifelessbarry: so, you suggested we could arrange a chat about image upgrades18:50
barrylifeless: yep.  stgraber ^^18:50
stgraberyep, can definitely find some time this week. Today's a public holiday here though so trying to minimize work-related time ;)18:52
lifelessfair enough18:53
lifelesswhat tz's are you both in?18:53
stgraberwe're both on EDT (US/Canada eastern)18:55
lifelessstgraber: current local time for you?18:56
stgraber3pm18:56
lifelesshow about my thursday, your wednesday, at your 1600 ?18:59
barrylifeless: that would work for me19:01
lifelessI'd only have 30-45m then, but that's enough to have a solid chat.19:02
stgraberworks for me19:02
slangasekstgraber: this is officially my worst dpkg hack ever (ifupdown)19:04
* Laney is excited to see it19:04
stgraberslangasek: haha, yeah, I figured it'd have to be pretty ugly after I read your comment on the cause of the problem ;)19:05
slangasekLaney: uploaded, enjoy ;P19:06
slangasek(tested for precise conffile state -> 0.7.5ubuntu4; precise conffile state -> 0.7.5ubuntu3 w/ "no" response -> 0.7.5ubuntu4; precise conffile state -> 0.7.5ubuntu3 w/ "yes" response -> 0.7.5ubuntu4; raring conffile state -> 0.7.5ubuntu3 -> 0.7.5ubuntu4; raring conffile state -> 0.7.5ubuntu4)19:07
slangasekthe only case this doesn't test for is the possibility that in the *next* version of ifupdown the user installs, the md5sum of the conffile changes again19:08
slangasekin that case, we probably get another conffile prompt :/19:08
slangasek(only for the precise -> 0.7.5ubuntu4 -> somethingelse case, fwiw)19:09
slangasekstgraber: ^^ so that means that if you have any reason to change /etc/init.d/networking for saucy+1, we'll need some additional maintainer script handling at that point ;)19:12
stgraberslangasek: I don't plan on changing it myself, can't speak for Andrew though, he loves changing things ;)19:13
slangasekstgraber: yeah ;)  but if you *merge* a change, too :)19:14
lifelessstgraber: whats your ubuntu email ?19:17
stgraberlifeless: stgraber@ubuntu.com19:17
lifelessstgraber: barry: invity thing sent19:19
barrylifeless: cool19:20
catbus1Anyone know when kernel freeze will be for 12.04.3? No such info on https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule19:21
mlankhorstcatbus1: raring kernel is used19:27
catbus1mlankhorst: the kernel freeze date for LTS point release is for new hardware support, right? raring kernel is already frozen, only critical patches/fixes can go in as SRU.19:30
=== penguin421 is now known as penguin42
=== francisco is now known as Guest30322
cjwatsonLaney: Could you merge (ish) the new fonts-dejavu package from Debian?  It's needed to make texlive-fonts-extra installable again.20:53
cjwatsonAnd you're touched-it-last and ttf-dejavu20:54
cjwatsons/and/on/  # how did that happen?20:54
geserspell-checker? :)20:54
cjwatsonEvil things (so no)20:54
mwhudsondoko__: hey, are you around?21:14
Laneycjwatson: a renamed source package?21:48
LaneyI'm sure I can manage that21:48
cjwatsonYep, the usual ttf -> fonts dance.  Thanks21:50
=== kentb is now known as kentb-out
=== salem_ is now known as _salem
=== cinerama_ is now known as cinerama
=== wedgwood is now known as wedgwood_away

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