/srv/irclogs.ubuntu.com/2009/03/27/#ubuntu-motu.txt

=== Marce_ is now known as Marce
MewcenaryHey everyone....00:18
MewcenaryI've got a package update trying to go through on Debian... but finding it hard to get a sponsor.  Is anyone here one who would like to help out... ?00:18
MewcenaryI'd like to get it done on Debian, so it flows down to Ubuntu naturally...00:18
directhexMewcenary, what kind of package?00:45
MewcenaryI'll link:00:47
Mewcenaryhttp://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=siege00:48
directhexwhat a big diff00:51
directhexoh, autocrap. that explains it00:51
MewcenaryYes, sadly so.00:51
MewcenaryUpstream running automake1.600:51
directhexhow handy00:52
MewcenaryPrevious Debian release had a mixture of direct source code changes + use of quilt, which lintian did not like.00:52
MewcenarySo put everything into quilt, which feels a bit cleaner.00:52
directhexlintian has a point00:52
MewcenaryI have grown to love quilt.00:53
directhexIME, mentors can be a bit of a black hole - much easier to find a mentor for team-maintained packages00:53
JontheEchidnaQuilt ftw00:54
JontheEchidnaOnce you get used to it it's real easy and convenient00:54
directhexquilt occasionally involves fighting IME00:55
directhexsadly00:55
directhexbut computers hate me00:55
directhexalso, anyone from motu-release about?00:55
JontheEchidnaheh, it's just that it has a steep learning curve, and you can screw it up accidentally easily >.>00:55
MewcenaryHopefully, a kind sponsor will step forward.  One step towards being a 'real' Debian developer etc!00:56
directhexiulian or ScottK appear to be connected, though not necessarily awake00:56
directhexMewcenary, like i said, life would be easier if it were a team package - or perhaps of interest to a team (even if not technically 'theirs')?00:57
MewcenaryThere's always bribery.00:58
directhexbribery?01:00
directhexseems you've worked with the debian cabal before!01:01
* Mewcenary smiles.01:01
MewcenaryYes, I did witness some of that.01:01
MewcenarySomeone trying to get a sponsor for a version already in Ubuntu, but got nigh-on shouted down re: YOUR PACKAGE IS WORTHLESS, UBUNTU HAVE DIFFERENT AIMS etc.01:01
MewcenaryI wnated to give him a hug.01:01
directhexit largely comes down to who you know, and who you work with. some teams have excellent cooperation, some have slight cooperation, some aren't on speaking terms01:02
directhextry the mono, kde, and mozilla teams in order for examples of the above01:03
slangasekI don't think what you're describing is "the debian cabal"01:04
directhexindeed01:06
directhexbut like the illuminati, a diluted brand remains enigmatic01:06
amikropHello, how can I fix these lintian warnings/errors?02:07
amikropW: webpage source: out-of-date-standards-version 3.7.3 (current is 3.8.0)02:08
amikropE: webpage source: missing-python-build-dependency02:08
amikropE: webpage source: missing-build-dependency cdbs02:08
amikropE: webpage source: missing-build-dependency python-support02:08
amikropW: webpage: extended-description-line-too-long02:08
amikropW: webpage: new-package-should-close-itp-bug02:08
JontheEchidnaany particular ones you need help with?02:09
amikropJontheEchidna: Mainly the errors :-)02:09
JontheEchidnaCould you paste your debian/control file please?02:10
twbI'd like to find out who is maintaining the Ubuntu midori package, so I can discuss the -fPIC issue with them.02:10
JontheEchidnain pastebin, of course :)02:10
amikropJontheEchidna: http://dpaste.com/19785/02:10
twbHmm, I guess I can get it from debian/changelog...02:11
JontheEchidnaamikrop: Ok, the errors are quite simple to fix. Just add the packages specified to the Build-Depends line02:11
JontheEchidna(cdbs, python, python-support)02:11
directhextwb, yeah, that's the first place to look02:11
directhextwb, otherwise known as the "he who touched it last" issue02:12
JontheEchidnaamikrop: Actually you probably would only need python-support rather than both02:12
JontheEchidnasince python-support depends on python02:12
amikropJontheEchidna: I manually changed Standards-Version to 3.8.0 after lindian's warning, and I added ${python:Depends} myself (I don't know if it was a right thing to do).02:12
twbdirecthex: thanks.02:12
JontheEchidnaamikrop: You would want to add cdbs and python-support to Line 502:13
JontheEchidnajust put a comment after debhelper (>=7) and then put cdbs, python support02:13
amikropJontheEchidna: any (>= x) things after them?02:13
JontheEchidnanah, just the package names02:13
JontheEchidna*python-support02:14
amikropJontheEchidna: Build-Depends: debhelper (>= 7), cdbs, python-support02:14
amikropJontheEchidna: like that?02:14
JontheEchidnaamikrop: yup, that should do it02:14
amikropJontheEchidna: Was it right to manually change Standards-Version and add ${python:Depends} myself?02:15
JontheEchidnaYes02:15
amikropJontheEchidna: E: webpage source: missing-python-build-dependency <-- persists02:16
JontheEchidnahmm, maybe you do need to build-depend on both02:16
amikropJontheEchidna: What do you mean?02:17
JontheEchidnaadd python to the build-depends is probably required02:17
amikropI 've done it.02:17
amikropAnd got this error.02:17
JontheEchidnapython and python-support?02:17
amikropJontheEchidna: http://dpaste.com/19789/02:18
JontheEchidnaamikrop: You'd want that line to be like this:02:19
JontheEchidnaBuild-Depends: debhelper (>= 7), cdbs, python-support, python02:19
amikropJontheEchidna: Worked. Thank you very much, for everything. :-)02:20
JontheEchidnaYou're quite welcome. :-)02:20
amikropJontheEchidna: OK, now, after running debuild the command ended well but did not prosuce any .deb file.02:24
amikropJontheEchidna: http://dpaste.com/19791/02:24
JontheEchidnaamikrop: To get the obvious out of the way, I'm guessing you've looked in the directory above where you debuild'd?02:26
amikropJontheEchidna: Yes.02:26
JontheEchidnastrange02:26
JontheEchidnait even says that it made a deb in the log02:26
* JontheEchidna thinks02:28
amikropJontheEchidna: Oh my God, it was a Nautilus problem. Although I changed directories with Nautilus, it didn't refresh. I had to manually refresh to see the .deb file. I am sorry.02:28
JontheEchidnaHehe :)02:28
amikrop:-P02:28
JontheEchidnaIt had me really going there for a minute, :P02:28
amikropMe too ;)02:34
JontheEchidnaI'm stepping out for 15 mins or so, if you have any further questions I'll get back to you then02:34
amikropJontheEchidna: alright :-)02:38
amikropJontheEchidna: for when you get back (or for anyone else): what is the standard way of distributing our packages? .orig.tar.gz .diff.gz .dsc <-- these 3 files?02:38
dtchenfor non-native (specific to Debian and/or Ubuntu), yes, you'll want an orig, a dsc, and a diff02:44
dtchensorry, to clarify: non-native == *not* specific to Debian and/or Ubuntu02:44
* ajmitch is surprised at how few python packages have files in /usr/local after the recent transition02:44
wgrantajmitch: They'll FTBFS if they do.02:44
ajmitchwgrant: sadly not02:44
wgrantajmitch: And lots of them do FTBFS because of that.02:44
wgrantajmitch: They did two weeks ago...02:44
ajmitchwell they may FTBFS after a recent python upload02:44
wgrantAnd they'll only end up in /usr/local after a recent Python upload.02:45
* ajmitch has fixed a package recently which had many files in /usr/local, python was changed that day for --prefix & the layout option to be mutually exclusive02:45
amikropdtchen: ok, thank you02:49
amikropanyway, thanks guys :)03:06
amikropbye03:06
amikropI have Architecture: any in debian/control. Why do I get an "i386" .deb and not a "any" one?04:05
wgrantamikrop: any means it will build a different binary for each architecture.04:07
wgrantYou might be thinking of 'all', which generates one that installs on everything.04:07
amikropwgrant: but it built a binary only for i38604:08
amikropand not for each architecture04:08
wgrantamikrop: It can't exactly magically transform your computer into all of the other architectures and build them.04:09
amikropwgrant: ok, I 'll use "all", then04:30
* calc thinks amikrop didn't get it04:46
calcif/when he comes back someone should remind him to read the documentation, you can't just make an any package an all package for fun04:47
calcand expect it to work anyway04:47
wgrantcalc: I know, but I only saw it after he left :(04:54
calcwgrant: yea, me too05:00
=== Andre_Gondim is now known as Andre_Gondim-afk
=== jmarsden_ is now known as jmarsden
dholbachgood morning05:48
fabrice_spHey dholbach :-)05:51
dholbachhiya fabrice_sp05:51
slangasekfabrice_sp: bug #348160> oh yay, then I don't have to worry about the yucky build failure I got when trying to migrate kmediafactory to libdvdread-dev :)06:00
ubottuLaunchpad bug 348160 in kmediafactory "libmagick10 transition to libmagickcore1" [Undecided,In progress] https://launchpad.net/bugs/34816006:00
fabrice_spslangasek, yes: I'm fighting to have it build, and I'm just having a link error now (no compilation error), so the patch is close ;-)06:02
slangasek\o/06:02
fabrice_spand guess what: the link error is because libavcodec ;-)06:03
=== cyberix_ is now known as cyberix
Toadstoolgood morning!07:47
Toadstoolyay free LWN subscription, mine is about to expire07:47
* wgrant bought one just a couple of months ago :(07:52
=== thekorn_ is now known as thekorn
=== azeem_ is now known as azeem
* directhex fills out FFe paperwork for Bug #34688409:37
ubottuLaunchpad bug 346884 in boo "[FFe] Please sync boo 0.8.2.2960+dfsg-1 (universe) from Debian unstable (main)." [Undecided,New] https://launchpad.net/bugs/34688409:37
Laney\o09:41
* iulian takes a look at it.09:42
iuliandirecthex: What testing of the package have you done?09:46
iuliandirecthex: What about the rdepends?09:46
directhexiulian, there are 2 rdepends - banshee and monodevelop-boo09:47
directhexiulian, i don't know whether any banshee addins actually make use of boo, so i've not found a rational way to test that. and monodevelop-boo needs rebuilding anyway as the 1.9.2 in the archive is incompatible with monodevelop 1.9.309:48
directhexand monodevelop-boo 1.9.3 needs boo 0.8.2+, which is how we got here in the first place09:49
directhexbasic machine testing implies ABI compatibility, but not API, iirc. let me check my irc logs09:49
=== a|wen_ is now known as a|wen
* fransman wanna know what got to be done for solving Bug #330150 ?09:50
ubottuLaunchpad bug 330150 in asterisk "Please sync Asterisk 1.6 from Debian experimental" [Undecided,New] https://launchpad.net/bugs/33015009:50
Laneyfransman: is it not too late for this?09:52
directhexhm, no, ABI testing was inconclusive, as machine tools generate false positives for some internal types09:53
directhex21-03-2009 13:34:22 > directhex: meebey, how did boo do in your abi testing?09:53
directhex21-03-2009 13:34:37 < meebey!meebey@booster.qnetp.net: directhex: couldn't test09:53
directhex21-03-2009 13:34:47 > directhex: so "sod it" approach?09:53
directhex21-03-2009 13:34:51 < meebey!meebey@booster.qnetp.net: yeah09:53
fransmanLaney: late because off?09:53
Laneybecause of the stage in the release cycle we're at09:54
iulianfransman: https://wiki.ubuntu.com/JauntyReleaseSchedule09:54
LaneyI mean, it's up to the release managers but I'd say wait until karmic09:55
directhex"library transition" means "EEK!" btw09:55
fransmanI did post it on 16 Feb 0909:55
directhexunless only 2 packages are affected. in which case it's fine & dandy. *cough*09:55
Laneyfransman: the sponsors were never subscribed :(09:55
iulianfransman: Indeed, but you didn't subscribe nobody.09:55
fransmanI am not able to do that Am I ?09:56
iuliandirecthex: I've just acknowledged it.  You'll need one more ack.09:57
iulianfransman: Actually, you can.09:57
fransmancool09:57
fransmanI did add Tags: sync09:57
directhexiulian, thanks. depends on one of them materializing though, of course09:57
iulianfransman: You have some buttons above "Subscribers".09:58
iuliandirecthex: OK.09:58
directhexiulian, note that debian has 0.8.2 rather than 0.9.1 purely because to make a FFe easier to swallow ;)09:59
fransmaniulian: yes I have subscribe someone else, thanks for pointing10:00
iulianYou're welcome.10:02
* iulian -> lunch, school. bbl10:04
=== jtechidna is now known as JontheEchidna
e-jatmay i know why this happened ? http://paste.ubuntu.com/138930/ <--13:01
directhexdelete debian/files ?13:03
e-jatBuild needed 00:00:02, 46548k disk space <---13:05
e-jatim building it at launchpad .13:05
=== thunderstruck is now known as gnomefreak
directhexbuilding what?13:05
e-jatmy PPA13:05
directhexwith your package?13:05
e-jatyeap ..13:06
e-jatby seing the log ..13:06
directhexand does your source package, as uploaded to your ppa, contain a debian/files file?13:06
geserit does: http://launchpadlibrarian.net/24366527/mymeeting_2.2-ubuntu3.1.diff.gz13:11
directhexdon't do that then13:12
directhexalso, delete debhelper log13:12
gesere-jat: and why did you change it from arch:all to arch: i386 amd64?13:12
geserjudging from the log your package doesn't support building arch-dependent packages13:12
e-jatjust want to make it available to amd6413:14
e-jator should i change it back to all ..13:14
e-jatthat was my 1st package .. so need mo comment from guys in here ..13:15
e-jatmore*13:15
directhexall means "architecture-independent package"13:15
directhexthings like documentation, where cpu arch is irrelevant13:15
gesere-jat: arch:all packages are build on i386 but work on all archs (i386, amd64, lpia, etc.)13:16
e-jatgeser: ic ..13:17
e-jatso i need to delete the package .. reupload changes n rebuild it with arch : all .. ?13:18
directhexe-jat, other things confuse me. you have a debian/ folder in the orig.tar.gz?13:24
e-jatowh misplace it .. deleting..13:35
e-jatdirecthex: thanks13:35
=== thunderstruck is now known as gnomefreak
bddebianHeya gang14:01
sistpoty|workhi bddebian14:01
bddebianHeya sistpoty|work14:02
LaneyIs there any point of a binary package conflicting on itself?14:27
sistpoty|workLaney: no14:27
Laneythought as much14:27
sistpoty|workLaney: otherwise almost every binary package would need to conflict itself, since it obviously would have file clashes ;)14:28
=== emgent is now known as z\
=== z\ is now known as emgent
Laneysistpoty|work: Right, that was my thinking. I just wondered whether there was an edge-case14:29
ScottKThere actually is.14:32
ScottKI remember seeing one package that did this.  It regenerated a bunch of symlinks and they'd be messed up if the old package was still around.14:33
ScottKSomething like that.14:33
sistpoty|workthat rather sounds like a workaround of buggy maintainer scripts than a proper use of conflicts... ;)14:34
ScottKI vaguely remember it being less bad than the other options, but it was a while ago.14:38
ScottKWasn't my package either.14:38
=== Tonio__ is now known as Tonio_
=== emgent_ is now known as emgent
=== emgent_ is now known as emgent
amikropHello, debuild gives me this error: http://dpaste.com/20020/ Here is my debian/control: http://dpaste.com/20019/16:35
amikropAny help would be appreciated much.16:35
directhexamikrop, you need a " ." as your spacer, not a blank line16:36
amikropdirecthex: ok, thank you :)16:37
amikropdirecthex: Also, I need to put an actual line break in the description (not an empty line).16:42
amikropdirecthex: How can I do this? gDebi seems to ignore my line breaks. It doesn't break the lines, it only leaves empty ones when it sees " .".16:43
directhexamikrop, look at where "." is appropriate in http://svn.debian.org/wsvn/pkg-mono/monodoc/trunk/debian/control?op=file&rev=0&sc=016:44
amikropdirecthex: I understood the use of " .". It leaves an empty line (\n\n). I just want to do a single line break (\n). How can I do that?16:52
amikropdirecthex: If I just press Enter, a \n doesn't get in the description.16:55
amikropdirecthex: Wether I press Enter or not, the final result is the same.16:55
amikropAnd I don't want that.16:55
amikropWhat can I do to avoid that? To actually get a \n in the result?16:55
amikropAnyone else, too, any help, please?16:56
sistpoty|workamikrop: I doubt you can do this, at least that's how I interprete 5.6.13 of debian policy17:03
amikropsistpoty|work: I can't just leave a line break?17:06
amikropsistpoty|work: All I want is to just change a line.17:06
sistpoty|workamikrop: imho, you can't do this... but take a look at 5.6.13 yourself ;)17:06
amikropsistpoty|work: Actually, I have some example code at my description, so I do need to leave a line break.17:06
sistpoty|workamikrop: ah... then use verbatim formatting (two leading spaces)17:07
amikropsistpoty|work: Can I do this to my whole description, too? (not just the code)17:07
sistpoty|workamikrop: I guess so17:08
sistpoty|workamikrop: if you think you'll need to have it verbatim *shrug*17:08
amikropsistpoty|work: I read about verbatim, but I can't see where it says: "line breaks will actually take effect"17:10
amikropsistpoty|work: it only says it will "hradly" wrap them17:10
sistpoty|workamikrop: if it wouldn't display line breaks, I guess the note about indenting wouldn't make too much sense?17:11
amikropsistpoty|work: I hope so17:12
amikropsistpoty|work: I made them verbatim, but still, my newlines were ignored.17:21
sistpoty|workamikrop: then I don't know17:25
amikropsistpoty|work: ok, thanks, anyway17:25
Technovikinghi all, need some packaging help17:38
Technovikingtrying to apply a debdiff to a source package with pbuilder17:38
Technovikingwhen I debuild -S -us -uc when source I get the following error17:40
Technovikingmake: *** No rule to make target `/usr/share/gnome-pkg-tools/1/rules/uploaders.mk'.  Stop.17:40
Technovikingany ideas?17:40
amikropMy package is GPLed. I am the upstream author. I have a file named LICENSE, which contains the GPL 3. But it isn't placed anywhere by my deb. Should it be placed somewhere? What can I do about it? Here is my debian/rules http://dpaste.com/20049/17:43
amikropI also have a file called README, which is places in /usr/share/docs/mypackage/README, but LICENSE is not placed anywhere.17:44
amikrop* placed17:44
amikropSo, what can I do, for my LICENSE file to be placed somewhere during my .deb installation?17:46
tgm4883amikrop, I don't think the LICENSE file needs to be installed, if it's like the COPYING files that I have in my source, they should just need to be in the source tarball17:48
sistpoty|workamikrop: you could mention it in debian/docs... but OTOH if LICENSE *only* contains the GPL-3, you don't need to have it in the .deb17:48
* tgm4883 notes that I am not a MOTU17:48
fabrice_sp_slangasek, I've just uploaded the debdiff for kmediafactory. Waiting for a sponsor :-)17:49
fabrice_sp_Bug #34816017:49
ubottuLaunchpad bug 348160 in autotrace "libmagick10 transition to libmagickcore1" [Undecided,In progress] https://launchpad.net/bugs/34816017:49
=== fabrice_sp_ is now known as fabrice_sp
amikroptgm4883: So, I should rename it to COPYING and retry?17:49
tgm4883amikrop, read what sistpoty|work said, you shouldn't need it in the .deb, just in the orig.tar.gz17:51
amikropsistpoty|work: why don't I need it in the .deb?17:51
sistpoty|workamikrop: the rationale is that you can use a .deb only on a debian/ubuntu system, and in the system there's always a copy of the GPL (in each major version) installed, hence this would be duplication17:51
amikropsistpoty|work: but 3?17:52
* sebner waves at sistpoty|work :)17:52
amikropGPL 3?17:52
sistpoty|workamikrop: yep, /usr/share/common-licenses/GPL-317:52
sistpoty|workhi sebner17:52
amikropsistpoty|work: ok, so it will only be in .org.tar.gz17:52
sistpoty|workamikrop: yep... unlike the deb, the orig.tar.gz can be used w.o. having debian/ubuntu installed ;)17:53
amikropsistpoty|work: ok, thanks ;-)17:53
sistpoty|worknp17:53
amikroptgm4883: thank you, too17:53
tgm4883np17:54
=== Andre_Gondim-afk is now known as Andre_Gondim
slangasekfabrice_sp_: <yoink>17:57
fabrice_sp_slangasek, yoink?! :-D17:58
fabrice_sp_ok. got it :-)17:59
=== fabrice_sp_ is now known as fabrice_sp
amikropsistpoty|work: Is -c gpl3 an option for dh_make?18:21
sistpoty|workamikrop: no idea... haven't used dh_make in a while myself18:22
amikropsistpoty|work: Because, although my upstream program is licensed under GPL 3, I ran dh_make with -c gpl18:22
amikropsistpoty|work: and now debian/copyright points to `/usr/share/common-licenses/GPL'.18:23
amikropwhich has gpl 218:23
sistpoty|workamikrop: /u/s/c-l/GPL will always point to the latest version (mine points to GPL-3, are you running an old release?)18:24
sistpoty|workamikrop: however you can (and should) always adjust debian/copyright to your liking (or let's say to your and the archive admins liking *g*)18:25
amikropsistpoty|work: there is no gpl3 option18:25
amikropsistpoty|work: but ok, it points to 3 for me, too18:25
amikrop:-)18:25
sistpoty|workamikrop: some people prefer to have debian/copyright point to the non-symlink, some the other way round... your choice (unless you have v3 only, then I guess pointing to GPL-3 directly seems better to me)18:26
amikropsistpoty|work: no, I 'm OK with th symlink ;)18:28
amikrop* the18:28
sistpoty|work:)18:28
* sistpoty|work calls it a day and heads home18:31
sistpoty|workcya18:31
=== DRebellion is now known as sbasuita
=== sbasuita is now known as sbasuita_
=== sbasuita_ is now known as sbasuita__
=== sbasuita__ is now known as sbasuita
=== ScottK2 is now known as ScottK-desktop
=== Andre_Gondim is now known as Andre_Gondim-afk
=== Andre_Gondim-afk is now known as Andre_Gondim
ahasenackhi, I'm trying to build a source package (debuild -S). The package is for jaunty, and I'm on intrepid. I thought it should work, but it fails when trying to include a file from debian/rules that doesn't exist. Should it be possible? Here is the log: http://pastebin.ubuntu.com/139178/20:33
ahasenack /usr/share/python/python.mk doesn't exist on intrepid (or I don't know which package installs it)20:33
sistpotyahasenack: that file isn't present in intrepid20:34
ahasenacksistpoty: correct. So while in general it could work, in this case I can't build a source package?20:35
sistpotyahasenack: well, not without fiddling with it. (/me hasn't done a python package since ages, so I haven't too much clue about it)20:35
ahasenacksistpoty: so I have to install jaunty if I want to build this jaunty source package. I might as well build the binary then too, I was thinking about using ppa20:36
sistpotyahasenack: or you could create a jaunty chroot20:36
ahasenacksistpoty: I tried using mk-sbuild-lv (which I use for other distros), but debootstrap knows nothing about jaunty and it fails20:37
ScottKahasenack: That's a new file than only exists with Python 2.6.  You'll need to build the source package in Jaunty.20:38
ScottKahasenack: You need the deboostrap from intrepid-backports.20:38
ahasenackso, get debootstrap which knows about jaunty, create the chroot, then build the source package and upload the source to ppa so I get the binary. I guess I can then skip the ppa part and just build the binary locally20:41
sistpotyyep20:41
ahasenacklots of stuff to build a source package, too bad the source build is not distro agnostic20:42
LaneyI can see the whole sponsor queue without scrolling now20:42
ScottKahasenack: True.  Generally it is, just sometimes new stuff has to get introduced.20:44
ahasenackI guess I thought the files would not be "run", just packaged, when a source package is built20:45
ahasenacklike a tarball20:45
ScottKGenerally the clean rule is called when the source package is built.20:45
ScottKThat can sometimes needs lots of stuff.20:45
ahasenackwell, I have time to walk the dog now that the jaunty chroot is being built and packages downloaded :)20:46
=== Andre_Gondim is now known as Andre_Gondim-afk
_stochastic_Hi room, I'm having some real troubles getting this package to build, can anyone give me a hand: https://launchpad.net/~stochastic/+archive/ppa/+build/91691521:27
jcfp_stochastic_: it's looking for avcodec.h and avformat.h in the wrong place?21:37
_stochastic_yeah, I think so21:38
jcfplibavformat-dev: /usr/include/ffmpeg/avformat.h   but the compile does this: -I/usr/include/ffmpeg//libavcodec -I/usr/include/ffmpeg//libavformat21:38
_stochastic_hmm, so I need to patch the source code?21:38
jcfpdunno, first test this is actually the problem as I'm not some gcc guru :)21:39
rippsI'm not getting alot of help from #launchpad, it seems somethings wrong with my team ppa, it can't find dependencies that have been the ppa for over a day. It just stopped working around 2 hours ago.21:46
sbasuitaHi! The last comment on this needs-upgrade bug: https://bugs.launchpad.net/ubuntu/+source/cifer/+bug/342350 says that I need to follow the process documented here: https://wiki.ubuntu.com/FreezeExceptionProcess . However, under the relevant section (Universe->Bug fix only), it says that the bug should just be filed with changelog/justification (done) and a MOTU should just upload. Am I right in thinking I don't need to do anything more t21:46
sbasuitao push this bug along?21:46
ubottuUbuntu bug 342350 in cifer "Upgrade Cifer to 1.2.0" [Undecided,New]21:46
ScottK-desktopripps: PPA is a #launchpad thing.21:58
=== IVBela1 is now known as IVBela
=== thunderstruck is now known as gnomefreak
YasumotoI'm trying to build a package using pdebuild, and it's telling me that the build dependency of python-cheetah is an uninstallable virtual package, although an apt-cache search seems to show that it isn't23:31
Yasumotodoes anyone happen to know of a way I can check if it's actually a virtual package?23:31
rippsYasumoto: I tend to get this when pbuilder is looking for a package in Universe, try adding "COMPONENTS="main restricted universe multiverse"" to your .pbuilderrc.23:40
Yasumotoripps: thanks a million, I'll give that a try now23:41
cody-somervilleyou'll need to do a pbuilder update --override-config23:46
Yasumotocody-somerville: ah, that's what it is23:48
Yasumotoripps + cody-somerville: thank you23:48

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