/srv/irclogs.ubuntu.com/2010/01/22/#ubuntu-motu.txt

superm1RainCT, i guess you can nuke that fake team then alltogether00:00
superm1it's not gonna serve any purpose ever00:01
RainCTYeah00:01
RainCTsuperm1: uhm, the confirmation page has no "OK" button, only "Cancel" :P00:02
superm1yay launchpad00:02
RainCTsuperm1: Also, I'm not sure whether that will send a mail to everyone. Maybe I should just leave it.00:03
superm1i found the same problem trying to delete ~ubuntu-mythtv yesterday when i was doing other team cleanup00:03
happyaronCan I request for syncing a package that is still in Debian new queue?00:51
crimsunanything that's dgetable.01:01
crimsunprobably best if you wait til it's accepted, though.01:01
happyaronoh, thanks01:03
happyaronone of may package is in the new queue from Jan 2nd till now, don't know when will it be accept to archive01:03
micahg\sh: libjs-dojo made it into unstable :)01:06
* StevenK bugs wgrant 01:22
wgrantStevenK: Hi.01:33
StevenKwgrant: Isn't there a timeout to kill builds that sit there and spin?01:33
StevenK(See https://edge.launchpad.net/builders/sejong )01:34
wgrantStevenK: Yes, but it's slave-side.01:40
wgrantSo if the slave dies, no timeout.01:40
StevenKAh, so sejong might have just rolled over and died01:41
wgrantNot completely.01:41
wgrantIt's still responding to XML-RPC.01:41
wgrantBut maybe sbuild has hung.01:41
StevenKMmmm01:41
micahgRAOF: file a bug if you need dh_xulrunner updated :)01:50
RAOFmicahg: I was going to, with a patch attached.01:50
micahgcool :)01:50
hakaishiHello everyone! Anyone up to advocate/review qt-shutdown-p? - I think there are no more Bugs, Errors and no lintian warnings. qt-shutdown-p is a small program to shutdown the computer. http://revu.ubuntuwire.com/p/qt-shutdown-p02:00
=== jdong- is now known as jdong
RAOFYes!  I (finally) win!05:26
RAOFgnome-shell (and anything else that depends on gjs, which is nothing at the moment) now builds!05:26
SevenMachinesi can sense the relief :)05:29
micahgRAOF: BTW, xulrunner is moving to universe...05:31
ScottKmenesis: There is a Debian/Ubuntu Zope team that works mostly by getting stuff into Debian first.  I would recommend you contaxt them.05:31
RAOFmicahg: You mean the current xulrunner package, which is 1.8, right?  Not xulrunner-1.9.1, which is needed for Firefox?05:33
micahgRAOF: xulrunner-1.8 shoudl have been dropped already05:33
RAOFAnd xulrunner-dev is still going to point to xulrunner-1.9.1-dev, right?05:33
micahgxulrunner-1.9.2 for lucid will be in universe05:33
micahgonce the ff migration is done05:33
RAOFWhat's FF migrating to?05:34
micahgRAOF: all in one package05:34
RAOFNo longer pretending you can use it as a lib, eh? :)05:34
RAOFWait.  Does that mean we'll have two copies of the xulrunner code?05:34
micahgRAOF: no, it's so we can jump major upgrades for FF without breaking all the rdepends on xulrunner05:35
micahgRAOF: yes05:35
ScottKSounds like xulrunner needs to be removed then.05:35
ScottKNo way we can maintain it.05:35
RAOFEeep.05:35
micahgthat's why it's going to universe05:35
micahgapps still build against it05:35
ScottKmicahg: What do you think we do here?05:35
micahgScottK: I know05:35
micahgsorry05:35
ScottK"Going to Universe" doesn't mean doesn't need maintaining.05:35
RAOFWe should, instead, have libs building against the firefox package?05:36
ScottKIf it's too hard for mozillateam to maintain in Main, what hope do we have?05:36
micahgRAOF: no -dev packages05:36
ScottKSounds like time for a pile of removal bugs then05:36
RAOFMan, this would be so much easier if gecko was an actual library.05:36
micahgRAOF: I already showed you the bug for that :)05:37
micahgScottK: you'll have to talk to asac about that05:37
RAOFmicahg: No, that was the bug to make SquirrelMonkeyFish an actual library :)05:37
micahgit seems like most upstreams are moving away from xulrunner anyways05:37
RAOFOn the basis that it's a huge pain in the arse, I'd guess.05:38
ScottKNo.  I'll take it up with the release team.05:38
RAOFApart, of course, for gnome-shell.  This could make MM... interesting.05:38
RAOFI presume we'll want gnome-shell in main for MM, which means gjs in main, which means some form of libmozjs in main available for it to link to.05:39
micahgScottK: here's the blueprint: https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-new-firefox-support-model05:39
ScottKI'm familiar with the Firefox part, not the dumping unsupportable crap on the community part.05:39
micahgsorry ScottK, I never thought of it like that05:42
ScottKmicahg: That's the effect.05:42
RAOFPresumably something's been done about couchdb, too, which I presume we still want in main for Lucid?05:43
ScottKSeems like an odd thing for a database to depend on.05:43
RAOFJavascript!05:44
micahgRAOF: idk, we might help them port to webkit if they're willing05:44
RAOFChromium has an actual javascript library, doesn't it.05:44
RAOFlibv8 IIRC.05:44
micahgRAOF: they're worse than mozilla about versioning05:45
micahgScottK: can I ask you about the zend framework backport?05:46
RAOFDoes *anyone* have a javascript library that has an actual stable ABI?05:46
zookoGreetings, folks!  We're hard at work on a new version of Tahoe-LAFS.  Our plan for releasing a new version in time to get uploaded into Lucid has slipped twice now: http://allmydata.org/pipermail/tahoe-dev/2010-January/003621.html05:46
micahgRAOF: I think webkit does05:46
RAOFDear lord!05:46
ScottKmicahg: What bug?05:47
micahgbug 48863305:47
ubottuLaunchpad bug 488633 in karmic-backports "Please backport zend-framework 1.9.6-0ubuntu1 from Lucid" [Wishlist,Fix released] https://launchpad.net/bugs/48863305:47
zookoAnd by the way, check out this praise of Tahoe-LAFS from a blue-ribbon panel of USA national cyber defense experts: http://tinyarro.ws/zooko05:47
micahgScottK: there was a security alert for that version and we pushed 1.9.7 already05:48
micahgcan I change the bug to that version?05:48
ScottKmicahg: Yes.05:48
micahgcan you reack afterwards?05:48
ScottKLet me know when you're done and I'll ack the change.05:48
fabrice_spDoes it makes sense to drop .la files from a -dev package ? I'm looking after a merge, and the main difference is that .la files are not installed anymore05:49
micahgScottK: done05:50
micahgoops, I should confirm too05:50
RAOFfabrice_sp: .la files aren't useful at best and are annoying at worst.  If the new debian revision doesn't install the .la files, that's perfectly fine.05:51
micahgScottK: really done this time :)05:51
fabrice_spRAOF: thanks! That means that one can be a sync ;-)05:51
fabrice_spis it the same with .a files?05:52
fabrice_sparen't they used for static linking?05:52
RAOFYes, they are.05:52
RAOFThat't exactly what they are.05:52
fabrice_spok. Thanks again :-)05:53
siretartfabrice_sp: libtool requires them. they are not strictly needed by ld(1)05:53
RAOF.la are quite different, though.  They do a similar job to pkg-config, but in a more convoluted way that everyone seems to hate.05:53
siretartthey are plain text files with various meta information05:53
siretartoh, I'm talking about .la files. .a files are ar(1) archives of object files (.o)05:54
fabrice_spok. Just in case, I'll check that rdepends still builds then05:55
ScottKmicahg: Ack'ed.06:01
micahgScottK: thanks06:01
dholbachgood morning07:04
keesYokoZar: wine isn't installable.07:24
keesYokoZar: wine (1.1.36-0ubuntu2) Depends: wine1.2, but wine1.2 (1.1.36-0ubuntu2) Conflicts: wine (<< 1.2)07:24
=== Quintasan1 is now known as Quintasan
andrukhow do i tell pbuilder to add my ppa from launchpad to its sources.list?08:03
Hobbseeandruk: othermirror in .pbuilderrc08:17
andrukso i put the line 'OTHERMIRROR="deb http://ppa.launchpad.net/csm-ticc/tablettray/ubuntu karmic main"' in my ~/pbuilderrc, but how do i add my gpg key?08:27
directhexandruk, you don't need your gpg key, apt in pbuilder runs unauthenticated08:32
andruktell that to: http://pastebin.ubuntu.com/360524/08:34
andrukon second look though, thats only a warning...08:35
andrukthanks Hobbsee and directhex09:47
andruk:-)09:47
BlackZI have this error when I run "debuild -S": http://paste.ubuntu.com/360560/10:12
BlackZand I can't sign the public key10:12
randomactionBlackZ: debuild -S -us -uc will create an unsigned package10:13
BlackZrandomaction, yes, but I should sign it, or not?10:14
=== virtuald_ is now known as virtuald
gesersigning is only important when you want to upload it10:15
BlackZgeser, yes, I should upload it10:16
randomactionsigning is necessary when you are uploading to archive or PPA10:16
BlackZso I must sign it10:16
randomactionyou need a key, then10:16
BlackZI have created, but I can't sign it10:16
gesertry "debsign -k0x22C75AE3 autotrash_0.1.1-0ubuntu1_source.changes"10:17
BlackZgeser, http://paste.ubuntu.com/360563/10:19
randomactionyour key ID must match your name/address in changelog10:19
geserhe did specify the key id in the last attempt10:19
randomactionit may be a problem with your gpg setup, as it can't find the key10:21
geserBlackZ: does "gpg --list-secret-keys" list your key?10:22
BlackZgeser, yes10:24
geserhmm10:26
geserhave you tried if you can sign a file (doesn't matter what kind of file) with gnupg?10:32
BlackZgeser, Successfully signed dsc and changes files10:33
BlackZsolved10:33
BlackZthank you10:33
BlackZI have re-created the key10:34
BlackZwithout "BlackZ" as comment in the key10:34
=== arand_ is now known as arand
=== dholbach_ is now known as dholbach
^arky^Hi, any compiz packing team member help me patch bug 50796412:22
ubottuLaunchpad bug 507964 in compiz "Application Switcher keybinds conflicts with gnome default" [Undecided,New] https://launchpad.net/bugs/50796412:22
dholbach^arky^: try #ubuntu-dekstop12:26
dholbach^arky^: try #ubuntu-desktop12:26
dholbachsorry :)12:26
^arky^thanks dholbach will do that12:27
YokoZarkees: yeah I meant to do it the other way (and have wine >> wine1.2)13:10
hakaishiHello everyone! Anyone up to advocate/review qt-shutdown-p? - I think I've done everything that fabricesp said. http://revu.ubuntuwire.com/p/qt-shutdown-p13:58
sebnerhakaishi: I don't really have time to review it but another point would be the changelog. Use -0ubuntu1 instead of -0ubuntu214:02
sebnerhakaishi: maybe make rules files more readable too (some newlines wouldn't be bad)14:03
hakaishisebner: I thought that it should be -0ubuntu2 if it is a second upload with the same source...14:04
hakaishisebner: okay, thanks14:04
sebnerhakaishi: oh, I didn't know it's already in the archive14:04
hakaishisebner: ah^^ ... seems I mistook something right now14:06
sebnerhakaishi: nah it's not in the archive. New stuff enters the archive generally with -0ubuntu1, then you increment the versionsnumber for further uploads14:06
hakaishisebner: Is it okay now?14:21
sebnerhakaishi: looks better now but wondering about your rules file anyways. Normally, http://pastebin.com/m4b8274cf should be enough but it fails. What's with this permissioned deniend stuff?14:26
sebnerhakaishi: found the issue14:30
sebnerhakaishi: proper solution: http://pastebin.com/m5e49785814:30
sebnerhakaishi: that's all you need in your rules file14:30
sebnerwb hakaishi , got my messages?14:36
persiahakaishi: sebner: Why call dh_auto_build in override_dh_auto_build if the right thing to do is "qmake" ?14:39
persiaJust don't bother including that line :)14:39
sebnerpersia: ah right, was confused with his $(MAKE) so I replaced it the sane command :)14:40
persiasebner: Ah, if was previously qmake; ${MAKE}, then it's correct to call dh_auto_build14:40
persia(or at least this does no harm)14:41
sebnerpersia: haha, right. DON'T confuse me!14:41
sebnerpersia: yeah, just testbuild. auto_build is necessary14:41
persiaBut dh_auto_install oughtn't drop out of a build if it can't do anything.  That seems like a bug.14:42
sebnerpersia: well, dh_auto_install normally calls make install and there is no such thing, he installs the stuff manually with dh_install (.install file), so you have to skip it or it fails imho14:43
persiasebner: Right, I understand the application here.  I just think it's a workaround for a bug.14:44
sebnerpersia: sure, bug of debhelper. shouldn't fail but skip automatically14:44
persiaI think dh_auto_install ought fail gracefully if there isn't an install rule.14:44
persiaRight.14:44
sebnerpersia: poor people like us have to use workarounds :)14:45
persiasebner: Why?  Surely your perl is sufficient to fix it :)14:45
sebnerpersia: no perl et al :P14:45
persiaOh well.14:46
sebnerpersia: C#, java and after some dirty haXX0ring and copying python. nahh, .. the youth of today. such useless languages :P14:46
Laneydate14:46
sebnerhi Laney14:46
Laneyexcuse me14:47
persiaFri Jan 22 14:46:58 UTC 201014:47
Laneyhi sebner14:47
sebnerLaney: haha, we now have persia bot :P14:47
hakaishipersia: just a moment please. I'm a little confused. I just have to override_auto_build: with qmake? But pbuilder will fail with permission denied... so I'll have to add a override_auto install: dh_install. Is that right?14:47
sebnerhakaishi: proper solution: http://pastebin.com/m5e49785814:47
* persia agrees with sebner14:48
hakaishiokay, thank you14:48
sebnerhakaishi: auto_install only fails because there is nothing to install14:48
sebnerdh_install is for the .install file14:48
persiaWell, at least it's as proper as we're going to get without hacking debhelper.14:48
sebnerwhich would be override_dh_install what you don't need14:48
persiaOr creating an install: rule and overriding the entire sequence.14:48
persia(which you also don't need)14:48
sebnerpersia: I'll check if there is already an open dh bug about it14:48
persiasebner: The workaround is mentioned in the manpage :)14:49
sebnerhakaishi: the easiest for now is really my proposed solution14:49
sebnerpersia: haha, fail by design then14:49
hakaishi^^14:49
persiasebner: Well, it still works for 90% of packages, which was the point.14:49
sebnerpersia: you are right but speaking about sanity ...14:50
persiaheh.14:51
hakaishiperhaps this ist because I have a install rule in the Makefile14:51
sebnerhakaishi: you should make sane makefiles then :P14:51
persiahakaishi: If you put an install rule in your makefile that respects DESTDIR, you should be able to drop your install file and let dh_auto_install do it's magic.14:53
sebnerpersia: wah wah wah, the manpage speaks about 90% working packages and "Skip it and ***run make install manually***", and the manpage says: if there's a Makefile and it contains a "install" target. The word here is ***if*** so it's a real bug imho as it seems that it should work/skip automatically14:53
persiasebner: Interesting point.  I can see that argument.  File the bug :)14:53
hakaishiahm, the Makefile is generated like that, because I want the possibilty to install from Source to14:54
Laneywhy does it fail here?14:54
* Laney has projects where the makefile doesn't have an install target which dh7 copes with fine14:55
sebnerpersia: Laney : Oh, it might be another bug. It fails with "permissioned" deniend for some files so the makefile might be b0rken and not dh_auto_install itself14:55
persiahakaishi: have your upstream Makefile install to ${DESTDIR}/${PATH} rather than /${PATH}.  If DESTDIR is unset, it will install to system locations.  If it is set, it will install for packaging.14:55
persiaIndeed.  It sounds like an issue with the Makefile.14:55
LaneyI would guess that is the case14:55
Laneyit's probably trying to install into the system14:56
* sebner says sorry to his beloved dh7 and gives it a cookie :)14:56
hakaishipersia: why do I need to upstream the Makefile, if it is generated by qmake?14:56
persiahakaishi: You don't.  In that case, you want to draft a qmake source file that generates an install rule that installs to ${DESTDIR}/${PATH}14:57
hakaishipersia: Sorry, I don't get it...15:00
persiaOK.  Let's set qmake aside for the purposes of discussion.  We'll get back to it once the desired behaviour is clear.15:00
persiaSo, you have a Makefile with an install rule.  You want this to be able to be used by people who don't use the package, so they can run make; make install15:01
persiaBut when you run that install rule inside a package build, it fails, because it doesn't have permission to write to system locations.15:01
hakaishipersia: but this is what it already does, isn't it?15:01
persiaYes.15:01
persiaThe Makefile probably has lots of lines like `install -m 755 /usr/bin/foo`15:02
c_korncan someone explain me what the deploy.tar.gz here is for ? I thought in source format 3 there is only a orig.tar.gz and debian.tar.gz file: http://packages.debian.org/source/sid/jxplorer15:02
persiaIf the Makefile instead had lines like `install -m 755 ${DESTDIR}/usr/bin/foo`, then if DESTDIR is unset, the behaviour would be unchanged.15:02
persiaThis is good for the `make; sudo make install` case.15:03
persiaWithin the packaging, DESTDIR will be set, so it ends up installing in /foo/bar/baz/quux/debian/tmp/usr/bin/foo15:03
hakaishiaha, I get it. thanks15:03
persiaWhich means that the *same* rule in the Makefile can work for both the non-packaged case and the packaged case.15:04
persiaSo you just need to change the qmake source to do that.15:04
persiac_korn: See the .dsc.  As I understand it, one can have an arbitrary number of objects defined, and the dsc ties them together.15:05
sebnerpersia: isn't it about multiple tarballs?15:05
persiac_korn: In this specific case, it appears that upstream has a separate source release and installer release, and these have been packaged together.15:06
^arky^Modifying site packages variable, need help with bug 49999015:06
ubottuLaunchpad bug 499990 in labyrinth "fails to start due to missing package import" [Undecided,New] https://launchpad.net/bugs/49999015:06
persiasebner: "objects" can be "tarballs", if one likes :)  I believe one can also use zip archives, flat files, etc.15:06
sebnerc_korn: http://wiki.debian.org/Projects/DebSrc3.0  ... samples: # sample1: 3.0 (quilt) with orig.tar.gz / debian.tar.gz and additional tarballs with all compressions schemes   <-- this might be15:06
sebnerpersia: ohh, I didn't know zip and that stuff is allowed too15:07
sebnerpersia: ah, *all* compressions schemes15:07
persiasebner: I'm not 100% sure that other stuff works now, but I believe that was the long-term intent.15:08
c_kornsebner, persia: thank you15:08
sebnerpersia: nvm. I'm just happy that now .gz and .bz2 is allowed as upstream tarball :)15:08
sebnerc_korn: yw15:08
^arky^dholbach: a quick question about labyrinth package15:14
dholbach^arky^: shoot15:16
^arky^dholbach: bug 499990  'site-package' is hardcoded15:18
ubottuLaunchpad bug 499990 in labyrinth "fails to start due to missing package import" [Undecided,New] https://launchpad.net/bugs/49999015:18
^arky^in bin/labyrinth and labyrinth/defs.py15:19
dholbach^arky^: if you want to fix it, please go ahead, I'm happy to sponsor it or take a look at it15:19
hakaishipersia: I don't know how do this in the .pro file, can you tell me?15:22
persiahakaishi: Sorry, I've never used qmake.15:22
^arky^dholbach: Thanks, doing just that. My question is should I patch all the files under debian/ directory ?15:22
hakaishipersia: okay, then I'll just try another time. cu15:23
=== arand_ is now known as arand
dholbach^arky^: https://wiki.ubuntu.com/PackagingGuide/PatchSystems#CDBS with Simple Patchsys15:27
^arky^dholbach: thank you15:31
dholbachno worries :)15:31
dholbachthank YOU15:31
jariqUpload to revu via ftp from network behind the proxy does not work for me ? Is there any way to upload via http ?15:37
persiajariq: There isn't.15:40
=== yofel_ is now known as yofel
=== solarion is now known as Solarion
ockhamhi, i'm a newbie with a rather trivial question: what do i have to specify in debian/rules if the actual sources (including autotools files and everything) are in a subdirectory of a package?16:40
^arky^dholbach: you still around man16:44
dholbach^arky^: yep16:45
ockhamanyone? i tried  dh $@ --sourcedirectory=src, but that doesn't seem to do the trick16:46
^arky^dholbach: source uses '@PYTHONDIR@' variables where does this get site in debian package?16:46
ockhamthere's a line: AUTOMAKE=automake-1.9 autoreconf -ivf16:46
ockhamthat causes a choke: autoreconf: `configure.ac' or `configure.in' is required16:46
ockham(in override_dh_auto_clean)16:47
^arky^dholbach: Is it the  'configure' file  that gives '@PYTHONDIR@' values ?16:47
dholbach^arky^: I don't know - might be worth forwarding that bug to upstream16:48
^arky^dholbach: ok16:49
jdongAAAH stupid PPA!17:01
=== mathiaz_ is now known as mathiaz
=== fta_ is now known as fta
=== cyphermo1 is now known as cyphermox
sistpotyhi folks19:51
geserHi sistpoty19:51
sistpotyhi geser19:51
sistpotyhaha, I'm so lazy, I don't even upload anything myself anymore: bug 495772 :)19:52
ubottuLaunchpad bug 495772 in pearpc "Unable to compile package acquired through apt-get source" [Undecided,Fix released] https://launchpad.net/bugs/49577219:52
BlackZhello geser ;)19:53
ajmitchhi19:53
geserHi BlackZ, ajmitch19:53
sistpotyhi ajmitch19:53
sistpoty(so ctrl-w closes a kvirc window, as I just figured *g*)19:54
ajmitchheh19:56
* ajmitch wonders when wgrant will be around this morning19:56
* sistpoty grumbles a little bit about ScottK for sagemath... downloading a 57MiB tarball doesn't suggest getting it in shape again will be a simple task19:58
ScottKsistpoty: I think we're going to have to remove it.19:59
sistpotyScottK: oh? so I should focus my work elsewhere?19:59
ScottKDebian maintainer said it needs a new upstream release to work with Python 2.6.19:59
ScottKYes.19:59
ScottKUnless you really want to package it (it's a beast I understand)19:59
sistpotyScottK: not really20:00
ScottKBoost transition is done.20:00
ScottKMy suggestion is work on FTBFS or NBS.20:00
ScottKI don't have a hard one handy.20:00
sistpotyok, will do, thanks ScottK!20:00
siretartsistpoty: I noticed a bunch of ftbfs packages while rebuilding ffmpeg's reverse depends20:05
sistpotyhi siretart20:05
siretartsistpoty: I didn't check all logs, but none of those I've seen were because of ffmpeg, all were because of other problems20:05
siretarthi sistpoty  :-)20:05
sebnerhuhu sistpoty siretart :D20:05
sistpotyhi sebner20:05
siretarthi sebner!20:06
* sebner reads the backlog in case somebody already asked siretart about gstreamer-plugins-bad20:06
sistpotysiretart: got a package you want me to look at in particular?20:07
siretartsistpoty: http://paste.ubuntu.com/360846/20:08
siretartis a copy of my ftbfs folder20:08
sistpotythanks siretart, I'll start with k9copy20:09
sistpotyhm, where is k9copy from? marillat?20:10
sistpotyoh, looks like ubuntu native one :)20:11
gesersiretart: you can strike out smilutils from that list, this one is already fixed20:13
randomactionsebner: I'm not sure what's the deal with gstreamer-plugins-bad, but we have a ftbfs fix for gst-plugins-bad0.10 waiting to be sponsored20:16
sebnerrandomaction: sounds interesting :D20:16
siretartgeser: excellent. thanks20:16
sebnerhola hola geser :)20:16
geserHi sebner20:17
Quintasanhello20:21
wgrantajmitch: Hi.20:23
ajmitchwgrant: morning, going to head out & enjoy the sunshine today? :)20:25
wgrantajmitch: Ahem.20:25
* ajmitch has had breakfast but probably needs some caffeine to function for the day20:27
sistpotyhm.... /var/lib/dpkg/info/tex-common.postinst: 1011: kpsewhich: not found (dependency problem? worked fine after a dpkg --configure -a)20:31
randomactioncould it be somehow related to texlive-base binaries sitting in the NEW queue?20:48
geserbah :( no new TeX before next week20:54
siretartoh, tl2009 is in lucid NEW? \o/21:03
gesersiretart: actually texlive-base 2009-7 is already through NEW21:06
geserthanks to out-of-order processing done by jdstrand :)21:06
jdstrandjeez, give me a second to get through it! ;P21:07
jdstrandgeser: what else is needed besides that?21:08
geserjdstrand: I don't see anything TeX related in the NEW queue left21:09
jdstrandk21:10
jdstrandfyi, texlive was the only thing I deNEWed related to that21:10
nixternalhello21:45
highvoltage!ops21:46
ubottuHelp! Hobbsee, Riddell, sladen, fbond, mneptok, gnomefreak, Seveas, dholbach, elkbuntu, PriceChild, or jpds!21:46
xvdYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
xvdYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
xvdYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
xvdYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
nixternal!ops +R this channel21:46
ubottuError: I am only a bot, please don't think I'm intelligent :)21:46
ybtbkYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
ybtbkYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
xvdYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
ybtbkYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
hxukurqYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
hxukurqYour machine COULD BE INFECTED by the recent spam attacks - visit http://fix.freenode.pl/ for a quick and easy solution.21:46
nixternalthanks tsimpson21:46
jussi01just a note, do not click that link21:46
nigel_nbokay, now i understood what those attacks were21:47
nixternallol21:48
nixternaltsimpson: no worries, you got it under control21:48
tsimpsonahh, SECURE is set21:48
dhillon-v10hi all, I filed this bug a little while ago: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/507778 so can anyone sponsor it, it been on the queue for a while23:01
ubottuUbuntu bug 507778 in acpid "Please merge acpid (1:2.0.0-1) from Debian testing" [Undecided,New]23:01
geseryou need a core-dev for that as it's in main23:04
jpdsdhillon-v10: slangasek and mathiaz discussed that request yesterday.23:05
dhillon-v10geser: alright23:05
dhillon-v10jpds: so what happens now, I should wait for some time right23:05
jpdsI'd talk to thme firsyt.23:07
dhillon-v10mathiaz: ping regarding a merge :)23:07
dhillon-v10jpds: alright :)23:07
mathiazdhillon-v10: well - the question is whether the new version of acpid (2.0.0) should be pulled in lucid - considering that it's new code (?) for a an LTS23:08
mathiazdhillon-v10: as I'm not familiar enough with acpid, I defer to slangasek on wether 2.0.0 should be pulled in23:09
dhillon-v10mathiaz: alright that makes sense, well the good thing is that I am getting better at merges (slowly)23:09
mathiazdhillon-v10: right - the issue here is not wether your work is should be improved, but rather if we should *actually* merge the new version23:10
dhillon-v10mathiaz: understood :) thanks for the info.23:10
mathiazdhillon-v10: some packages are more touchy - it may well turn out that 2.0.0 should be included in Lucid23:10
mathiazdhillon-v10: in which case your merge proposal will be reviewed again23:11
dhillon-v10mathiaz: true, this one goes to main so its understandable23:11
dhillon-v10mathiaz: oh wait, while you are around, can you tell me why one of my patches isn't applying, let me get you the link23:12
dhillon-v10mathiaz: alright this one: https://bugs.launchpad.net/ubuntu/+source/cln/+bug/50899523:13
ubottuUbuntu bug 508995 in cln "Please merge cln (1.3.1-2) from Debian Testing" [Undecided,New]23:13
mathiazdhillon-v10: which package did you merge from?23:14
mathiazdhillon-v10: the changelog entry in the diff shows an entry for unstable23:14
mathiazdhillon-v10: so you haven't probably merged from the *latest* version of debian23:14
dhillon-v10mathiaz: the testing one, here: http://packages.debian.org/changelogs/pool/main/c/cln/current/changelog23:15
mathiazdhillon-v10: the base debian package you've used is 1.3.1-123:16
mathiazdhillon-v10: in the diff, you can see entry for 1.3.1-2 - that shouldn't be there23:16
mathiazdhillon-v10: you wanna attach the debdiff between the debian version and the merged ubuntu version23:17
mathiazdhillon-v10: the *latest* debian version - which in this case is 1.3.1-223:17
dhillon-v10mathiaz: alright I see what I did wrong, but the merge was mostly done by bzr so I don't understand what went wrong there23:18
mathiazdhillon-v10: probably that the bzr branch for the Debian package wasn't up-to-date23:18
dhillon-v10mathiaz: alright I guess I am better off merging by hand :)23:19
dhillon-v10mathiaz: would you be around in like 5 mins. so i can show you my diff23:19
mathiazdhillon-v10: I should be23:20
* persia idly notes that #ubuntu-devel may be a more appropriate place to discuss issues with seeded packages.23:28
persia(or some more specific channel)23:29
dhillon-v10persia: alright so there's a different package and when I merge that, it turns out that the only change is in changelog and control file, that's it, I double checked and nothing is there, is that possible23:34
persiaYep.  I just fixed FTBFS for plymouth on four architectures with a change like that to libdrm recently.23:35
gesersure, if Debian merged our changes, then only our changelog entries and the updated Maintainer field are left after a merge (which should be a sync then)23:35
persiaThe important thing to check is *which* changes to debian/control23:36
persiaAnother example would be the outstanding tiemu merge, which just has some dependency changes because we don't have iceweasel.23:37
dhillon-v10persia: yeah I checked that like 4 times, and the last upload fixed got about everything so :)23:38
persiaAs geser said, if all the fixes have been applied upstream, you can just sync and drop the changelog and maintainer changes.23:40
persiaJust make sure there's nothing missing.23:41
=== vorian is now known as v

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