/srv/irclogs.ubuntu.com/2012/04/22/#ubuntu-devel.txt

=== jalcine- is now known as JackyAlcine
Logan_When I'm patching a package, do I need to update the series file in debian/patches, or will the package maintainer do that after merging?00:26
jelmerhi Logan_ ; if you're adding a file in debian/patches it's usually a good idea to update the series file too00:28
Logan_Aw, okay. :-P I already proposed it for merging. :-(00:28
* Logan_ fixes.00:28
Logan_My first patch, so I have no idea what I'm doing. :-P00:28
Logan_(Well, hopefully some idea.)00:29
jelmerLogan_: it's not the end of the world, I'm sure whoever reviews it knows how to update the series file too :)00:29
=== yofel_ is now known as yofel
penguin42I'd love to know why flash pauses when I boot a vm00:35
=== jalcine- is now known as JackyAlcine
clausenhow can I figure out the CFLAGS used to build a .deb?03:17
=== jalcine is now known as Guest54507
=== jalcine- is now known as JackyAlcine
hyperairhmmmm how is this multiarch arch:all dependency supposed to work?05:57
hyperairi tried to install acroread:i386, but it's trying to pull in acroread-common:i386 which doesn't exist because acroread-common is arch:all.05:57
hyperairso i rebuilt it setting Multi-Arch: allowed as mentioned in the multiarch spec...05:57
hyperairbut that doesn't seem to satisfy dpkg.05:58
imbrandonarch:all and arch:any are not the same i think you may want the other05:59
ScottKTry installing acroread-common acroread:i38606:00
hyperairScottK: aha, i see it. it's supposed to be Multi-Arch: foreign, not Multi-Arch: allowed.06:00
hyperairMulti-Arch: allowed merely permits Depends acroread-common:i38606:00
hyperairor something06:01
hyperairScottK: and you need Multi-Arch: to be defined on arch:all packages now.06:01
hyperairhttps://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages06:01
ScottKOh.06:02
hyperairwhich.... i haven't defined on my multiarch library packages =06:04
hyperair=\06:04
hyperairwe should have an MBF for this or something..06:04
=== JackyAlcine is now known as Jacky
vibhavShall I cereate a patch or sync python-scipy? https://bugs.launchpad.net/ubuntu/+source/python-scipy/+bug/65519208:49
ubottuLaunchpad bug 655192 in python-scipy (Ubuntu) "scipy.weave.inline requires python-dev to be installed" [Low,Confirmed]08:49
vibhavcreate*08:49
vibhavFYI, the package is unseeded08:49
Laneywhat else would be in the sync?08:50
micahgtons of rdeps08:50
vibhavhttp://pastebin.ubuntu.com/940778/08:51
micahgwell, not tons, but quite a few :)08:51
vibhavyes08:51
Laneyvery informative changelog there08:51
vibhavwhy?08:52
Laneyit doesn't say why any of the changes were made08:52
vibhavah, sarcasn :)08:52
vibhavsarcasm*08:52
Laney:P08:53
vibhavhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651760 might help you08:53
ubottuDebian bug 651760 in src:python-scipy "python-scipy: should recommend python-dev" [Minor,Fixed]08:53
Laneyoh, it's got a new upstream too08:53
vibhavBut isnt the bug a problem with the debian packaging files?08:54
Laneyif you sync you get everything08:54
Laneyi'm trying to answer your question08:54
vibhavah08:54
vibhavLets get a sync then08:55
vibhavthanks08:55
Laneyi didn't say that. looks like at least the Ubuntu diff would still be required (so, a merge)08:56
vibhavwhy would a ubuntu diff be required?08:57
Laneyhave a look at our changelog and you can see what it is08:57
LaneyI think doing the minimal change is going to be safer08:57
vibhavyou mean adding the python3 packages?08:59
Laneyadding the new recommends09:00
Laneybut jtaylor didn't just upload it (instead forwarded the bug) so perhaps it isn't worthwhile09:00
vibhavfine09:02
vibhavIll do the minimal change09:02
vibhavAlso, should I add it as a build-depend or a recommended package?09:06
vibhavcould anybody nominate https://bugs.launchpad.net/bugs/655192 for supported Ubuntu releases?10:54
ubottuLaunchpad bug 655192 in python-scipy (Ubuntu) "scipy.weave.inline requires python-dev to be installed" [Low,Confirmed]10:55
jtaylorI don't think its really SRU worthy10:58
vibhavjtaylor: why?11:03
jtaylorits a minor bug easily fixed by the user11:03
vibhavsince we are fixing it for precise, might as well get the fix in other versions11:04
jtaylorSRU's are considerably more work than fixes in precise11:04
vibhavah11:04
vibhavThen what about a backport?11:04
jtayloralso not really enough for a backport, though backporting 0.10.1 from Q might be a good idea11:06
jtaylorits a bit late to add that to precise now11:06
vibhavah11:07
vibhavWell, Ill keep it for U+1 then11:07
vibhavjtaylor: Is that fine?11:24
jtaylorvibhav: we could fix it for precise, if my numpy branch gets merged we could add dh_numpy3 usage too11:24
vibhavjtaylor: Could you give me the link to your branch?11:32
jtaylorhttps://code.launchpad.net/~jtaylor/ubuntu/precise/python-numpy/merge-8/+merge/10297011:33
Laneyit's seeded. I'm not sure that it will get in.11:38
jtayloryeah I guess its to late, but then we merge it in Q11:38
jtaylorits on no image though11:38
Laneyyeah it is11:40
Laneyask seeded-in-ubunbut11:40
Laneyor a correctly spelled variant thereof11:40
jtayloroh it got on the dvd :O11:41
raffa50hello. what is the command for rebuilding source. i want to upload it on launchpad13:15
hyperairhmm why do we have gccgo from gcc 4.7, but not gcc 4.7? =(13:35
raffa50hello. what is the command for rebuilding source. i want to upload it on launchpad14:07
cjwatsonwhat exactly do you mean?  Launchpad PPAs will build a source package into a binary package for you ...14:09
cjwatsoncould you clarify?14:09
cjwatsonhyperair: probably because introducing all of gcc 4.7 would involve an updated libgcc114:10
hyperaircjwatson: ah, that sucks.14:10
cjwatsonraffa50: perhaps https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage will help you14:11
clausenI think Ubuntu 11.04 has a miscompiled ssh14:36
clausenit is giving me failed MAC codes, and the openssh source code states that this is a well-known problem14:36
clausenwhen compiling with gcc optimizations enabled (-O2)14:37
clausenso it's important to compile the MAC bit without optimizations14:37
clausenI only just started getting problems, so I guess I'd like to trace the build history of the package14:37
clausenis there a good way to do thsi?14:37
clausen(can I see how each package was built, the history of packages uploaded, etc.?)14:38
ScottKclausen: https://launchpad.net/ubuntu/+source/openssh/+publishinghistory14:44
clausenScottK, thanks!14:46
clausenScottK, so how can I see the CFLAGS?14:48
ScottKShould be in the build logs.14:48
clausenaha14:49
=== fenris is now known as Guest1242
clausenit is indeed compiled with -O214:55
clausenalthough the source only complained about -O3 and higher...14:55
clausenlooks like I'm going to have to do some more digging!14:56
clausenis it possible to get the object files from the build?14:56
cjwatsonclausen: I see no such claim in the openssh source code.  Where do you see it?14:58
cjwatsonIt says you sometimes get incorrect results with -O3, not with -O2.14:59
cjwatsonAnd we don't use -O3.14:59
cjwatson(I guess you mean the header comment in umac.c)14:59
clausencjwatson, yes, you are right14:59
clausennevertheless, the code doesn't work for me14:59
clausenyes, umac.c14:59
clausenI regularly get corruption messages14:59
clausenso perhaps something else changed (eg: gcc moved some items from -O3 to -O2)14:59
cjwatsonI don't remember ever seeing those when I was running 11.0414:59
clausenit only just started recently15:00
clausen(I'm still using 11.04 on my machine...15:00
cjwatsonAre you sure it isn't a problem on the server side?15:00
clausenit started getting regular corruption about 2 weeks ago)15:00
clausenyes, I have no trouble if I use dropbear instead of openssh15:00
clausen(on the client side)15:00
cjwatsonAfter all, it's warning about a transport problem15:00
cjwatsonThat might not signify15:00
clausenI agree, it's not 100% evidence15:00
cjwatsonThey're sufficiently different in other ways that they might not tickle the same server bugs15:01
clausenbut I would like to get to the bottom of this...15:01
clausen(the way umac's are used shouldn't make a difference though...15:01
cjwatsonI suppose you could try building 12.04's openssh as a starting point for comparison15:01
clausen... it's a very simple interface)15:01
clausencjwatson, well, I could recompile myself (11.04) to see if it works :)15:02
clausenI will do that15:02
cjwatsonYes, though I'd be surprised if that changed anything15:02
clausendifferent gcc?15:02
cjwatsonWill it in fact be?15:02
clausenyou would know better than me :)  i don't know how the build machines are configured15:02
cjwatsonLast openssh upload to natty was 1 April 2011, not that far from release15:02
clausenoh15:03
clausenthat's odd15:03
clausengood point15:03
cjwatsonThere were a few gcc-4.5 changes since then, but I wouldn't have expected major code gen fixes, though it would depend on your architecture15:04
clausenok, that's a puzzle then, why I am suddenly getting MAC corruption15:05
clausensince the binary didn't change for a year15:05
clausenI guess I jumped to conclusions when I saw the comment in umac.c15:05
cjwatsonWell, that's why I'm suggesting it might not be a problem in that binary :-)15:05
cjwatsonNightmare to track down, though, I'm not experienced in that particular part of openssh15:05
cjwatsonWhat architecture is this, anyway?15:06
clausencome to think of it, it might be the server side15:06
clausenx8615:06
clausen(intel)15:06
cjwatsonOK, so shouldn't have been any relevant compiler changes15:06
clausenthe time-frame is similar to when I upgrade the server from 10.10 to 12.04 beta15:06
cjwatsonYou could try winding back recent library upgrades if you still think it might be a client bug15:06
cjwatsonThere was an eglibc update in natty a month and a half ago or so15:07
clausenhmmm15:07
cjwatsonOr an openssl update a few days ago15:07
cjwatsonBit tenuous15:07
clausenI'm wary about winding back, because this particular machine is a "secure" machine15:08
clausen(I guess I could clone it, and work off the clone...)15:08
clausen(but that's a lot of work!)15:08
cjwatsonAnother thing you could try is building 10.10 and 12.04 chroots on the server and starting sshd instances there on spare ports15:08
clausenyes15:09
cjwatsonSo that you can compare a bit more accurately15:09
clausenthat's a good idea15:09
cjwatsonThen possibly bisect at least at the level of uploads15:09
clausenin fact, I still have 10.10 on another partition, so I can chroot to that ;)15:10
clausenyes15:10
cjwatsondebootstrap's easy enough if not15:10
clausenvery good suggestion15:10
clausenthanks15:10
cjwatsongood luck ...15:10
clausenthankyou :)15:10
cjwatsonTo answer your earlier question, the object files from the build are discarded, although you might find some debug symbols on ddebs.ubuntu.com if it happens to have a matching version15:12
cjwatson(That service isn't desperately robust and it does sometimes not have matching versions)15:12
dupondjeStill allowed to do bugfix uploads?15:22
cjwatsonto unseeded packages in universe, yes15:22
cjwatsonotherwise ask the release team15:22
dupondjehttps://launchpad.net/ubuntu/+source/remmina => scrolling is broken in rdp connections. Because of GDK_SCROLL_SMOOTH.15:23
cjwatsonthat's on the desktop CD (among others) and it doesn't sound like a showstopper - I'd recommend an SRU15:25
dupondjeI'll prepare an SRU then :)15:26
dupondjeGood to have it fixed still. Quite annoying issue (for me at least ;))15:26
raffa50hello. what is the command for build the package of debian? i need to upload my software on launchpad16:36
astraljavaraffa50: Did you not understand the previous instructions? You don't need to build locally in order to use a PPA.16:44
astraljavaraffa50: https://help.launchpad.net/Packaging/PPA16:45
vibhavSince only 5 days are left for 12.04 , should we fix https://bugs.launchpad.net/ubuntu/+source/sivp/+bug/879097 in Ubuntu directly?16:52
ubottuLaunchpad bug 879097 in sivp (Ubuntu) "libraries are not properly loaded in etc/SIVP.start " [Undecided,Confirmed]16:52
vibhavinstead of getting it first into Debian?16:52
raffa50uhm i found16:52
jtaylorvibhav: do you have a working patch?17:02
=== ejat- is now known as ejat
ScottKvibhav: Yes.18:38
=== JanC_ is now known as JanC
=== ximion1 is now known as ximion
=== l3on_ is now known as l3on
nigelbDo we have a name for Q yet?18:51
arandnigelb: Don't think so, but it's generally around this time it gets announced iirc18:55
nigelbarand: It's far far later than normal. :)18:55
nigelbI wonder if sabdfl is saving it for the UDS opening keynote ;)18:56
micahgcjwatson: what do you think of removing packages that FTBFS in the rebuild on all archs that have been removed from testing?19:01
micahgcjwatson: oh and have no rdeps19:01
arandnigelb: Might just be very hard to find positive adjectives on Q...19:02
nigelbarand: HA. lol.19:03
penguin42arand: Quintessential Quetzalcoatlus, obvious really19:12
nigelbpenguin42: haha19:13
penguin42nigelb: I know Mark always likes things that are easy to spell and type19:15
nigelbpenguin42: yeah. he does care for us developers19:18
nigelbwho have to type it out many times ;-)19:18
* penguin42 is still just bitter that PP isn't penguin19:19
penguin42oh, nested KVM seems to work nicely on PP; I've just booted a OO VM on a PP server running on a PP host19:20
penguin42and given the number of impossible things I've done this weekend I should give up now :-)19:21
ScottKoneiric was not easy to type at first.19:31
* tumbleweed is hoping for a quirky quagga - quirky is a great name for a post-LTS release :)19:32
jtaylorwell it falls into debian freeze19:40
jtaylorso it won't be so bad19:40
ScottKI'm sure we'll invent plenty of crack on our own.19:41
ScottKQwality Quail19:42
ScottKhttp://dilbert.com/strips/comic/1996-06-11/ comes to mind.19:43
jtaylor^^19:44
tumbleweed:)19:44
cjwatsonmicahg: I'm gradually fixing or removing anything that has out-of-date binaries as a result of build failures.  I expect most of the packages in your category would be sane to remove, but I'd like to apply some case-by-case judgement all the same19:53
cjwatsonout-of-date binaries are more urgent IMO19:55
* ScottK doesn't understand why all the axiom binaries on the the outofdate list.20:00
cjwatsonYM from architectures that built?20:00
micahgpowerpc is behind20:01
cjwatsonThey're probably arch all.  LP nowadays keeps arch all around until there are no arch-specific binaries from the same version, to try to reduce skew-induced damage.20:01
Laneyit's the arch:all binaries being held because of the FTBFS20:01
cjwatsonFix or remove the arch-specific ones, and the arch all binaries will be dominated away on the next publisher run.20:01
micahgwhere's this out of date list?20:02
Laneyhttp://people.canonical.com/~ubuntu-archive/testing/precise_outdate_all.txt20:03
Laneyand s/testing/testing-ports/20:03
micahgmeh, I've added 2 to the list apparently20:03
cjwatsonit's about half the length it was on Friday :)20:03
cjwatsonit does fluctuate a bit20:03
cjwatsonone of these days I must add a currently-building indication to it20:04
ScottKIt definitely looks much better than the last time I looked at it.20:17
=== jussi is now known as android
=== ajmitch_ is now known as ajmitch
=== bradm_ is now known as bradm

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