[00:06] sistpoty, can i suggest people offer to help with lenny RC bugs? nothing's gonna impact jaunty development more than a stagnant debian [00:07] hello === asac_ is now known as asac [00:13] directhex: I won't hinder you to do so ;) [00:13] sistpoty, i meant as part of your mail, but i guess i'm a bit late [00:14] anyway, bedtime pour moi [00:14] directhex: sorry, mail already sent [00:15] * sistpoty also goes to bed... gn8 everyone === bdrung_ is now known as bdrung [02:31] anyone help with the libGL.so.1 cannot be overwritten nvidia issue? 32 bit system [02:37] What's the variable for packager name? It keeps using the username, instead of my full name. === LucidFox is now known as Sikon === Sikon is now known as LucidFox [02:57] gouki: set DEBFULLNAME= in the environment [02:57] Elbrus, thank you very much! [02:59] gouki: you might also want to set DEBEMAIL and DEBSIGN_KEYID [03:03] Very helpful indeed Elbrus. Both set. Thank you. [03:05] your welcome [03:05] s/your/you're [03:08] Wahoo. Launchpad. Now improved with even mor slowness. [03:08] mor/more [03:08] Heheh [03:22] Would someone please hunt down shirish (see -devel-discuss) and explain how ridiculous it is to put a license statement in every email you send. [03:22] Please before I find myself violating the CoC. [03:22] :) [03:23] I thought that too when I read his email [03:30] I really should just killfile him. [03:37] * StevenK stops reading -devel-discuss before he gets more depressed by shirish [03:39] * ScottK adds a new rule to his Kmail. [03:39] * StevenK finds himself a little disappointed the startup sound didn't change for intrepid [03:42] * ScottK finds himself disappointed he can't find his car keys. [03:43] Did anyone else besides me respond to Mark Ellse? [03:46] why did shirish reply to himself and just quote his entire message? [03:46] is that like thread bumping in mailing list world? [03:48] jdong: I was wondering that, then realised it was shirish. [03:48] wgrant: heh 10 hour 37 minutes in between too. That's no accidental double-click on send. [03:48] Oh. [03:50] Hmm. [03:50] ~20% of the failed builds from Intrepid that have so far been retried in Jaunty have built fine. [03:50] Unfortunate that we didn't have a mass give-back near the end of Intrepid. [04:02] jdong, did your /var/lib/bluetooth transition over from hardy to intrepid? [04:02] jdong, i'm doing the upgrade right now, and didn't even consider that scenario - what happens... [04:04] superm1: I never tried it with hardy [04:04] superm1: I started fresh at Intrepid, it should be fine [04:04] the format looks identical to me [04:04] jdong, well i figure for most people it's not a big deal if it doesn't, but i *really* dont want to repair my keyboard :) [04:04] superm1: haha, repair is the right word :D [04:05] jdong, funny how re-pair and repair are both applicable here. that and i dont even remember if the mouse was trouble too pairing [04:05] superm1: the mouse is bliss [04:05] no trouble at all [04:06] but the keyboard.... I sure hope for your sake there's no repair involved! [04:13] ScottK: shirish is usually variable in his level of cluelessness. I'll hunt him down again (i've had reasonable success the last few times i've done it) [04:13] Hobbsee: Depends on how you define success. He's still breathing. [04:14] ScottK: well, defining success in most other ways would be violating the code of conduct. [04:14] wgrant: hppa? [04:14] besides, he does get more clueful / less objectionable occasionally. [04:14] It got a fixed libc and gcc very near the end. [04:14] Hobbsee: If you say so. He invited someone to join him on linked-in via debian-devel ML earlier this week. [04:15] ScottK: ouch. [04:15] ScottK: okay, so make that *very* occasionally. [04:16] He's the only person I still remember individually who was on my list of reasons why I gave up user ML. [04:17] ScottK: And lpia and powerpc... [04:18] OK. Well I'm not suprised at all about hppa. [04:18] Through much of the later part of the dev cycle there were enough hppa FTBFS that the hppa buildd's actually kept up. [04:19] Yeah... [04:21] urgh, why am i browsing u-d-d now? [04:24] man...there's madness on this list [04:24] and surprisingly, i'ts not from shirish. [04:25] Yeah. I'm considering giving it up. [04:25] Hobbsee: Which madness in particular? [04:25] i gave it up long ago, i'm just looking at the archives. [04:26] ScottK: Vincenzo Ciancia seems to be the main offender. At this point, the "Deleting an alpha iso for the safety of users hardware" thread [04:26] But the lack of Midnight Commander is what is holding Ubuntu back from taking over the desktop! [04:26] jdong, nope, they both look to have tried hard, but didn't come through :( [04:26] Ah. I remember that. [04:26] superm1: that's what she s... I mean.. err... did you back up /var/lib/bluetooth? [04:27] wgrant: Oddly enough my welcoming call to do the actual work involved in getting it on the CD seems to have ended that thread. [04:27] ScottK: I noticed... [04:27] jdong, yeah, but not gonna do a lot of good at this point [04:27] wgrant: and the lack of inverse searches for dvi in ubuntu...which apparently uses kde now. [04:27] i'll play the repairing game i guess :( [04:27] superm1: ouch. [04:28] ScottK: that's normal. [04:28] superm1: remember that after pairing you need to edit did separately to inject the right id :) [04:28] ScottK: you mean the devs won't just drop everyhing to fix what users want, OMGNOW? [04:28] Hobbsee: I actually fixed that one. I did some Googling and found a real constituency for it. [04:28] i saw that. and apparently ubuntu's (which doesn't use kdvi) is much better for users as a result. [04:29] Hobbsee: The inverse searching was a legitimate issue. [04:29] Hobbsee: It's in Universe, so arguably it's for either. [04:30] well, it starts with a k :P [04:30] So does Kompozer. [04:30] ;-) [04:31] But Kompozer is Mozilla-based. [04:31] So it is known to be insane. [04:31] Yes, well. [04:31] * ScottK just lasted an entire hour and 10 minutes in #kubuntu. [04:32] Of course I was out of the house picking up teenager #2 from a party for most of that. [04:32] Heh. [04:35] jdong, wooohoo. 8th try :) [04:36] superm1: how do you get so lucky? [04:36] superm1: I freaking spent all of last week on this [04:36] jdong, it probably helps that this is the same machine it "was" paired with before [04:40] Ooh. Good press for .au: http://www.cnn.com/2008/WORLD/asiapcf/10/31/australia.residency.denied.ap/index.html?eref=rss_topstories [04:40] how is that good press? [04:41] Sarcasm. [04:41] ah, yes. [04:41] ScottK: you should see the proposed filtering legislation. [04:41] I saw something about that. [04:41] We love you, Senator Conroy. [04:42] wgrant: yes, and will filter your internet experience so it only allows you access to about 10 sites, just to see how you like it - 10 sites we define. [04:43] * ScottK decides that he's had too much alcohol to know if further comment is appropriate. [04:43] ScottK: Always! [04:44] I might take that seriously if I didn't ~ know how old you are. [04:44] heh [04:45] Heh. [04:45] ScottK: Have a bit more alcohol and file some bugs with 2000-word paragraphs. They're always lots of fun. [04:46] Nah. I'm pretty happy with things computerish. [04:47] jdong, i think i spoke too soon... did buttons 1-3 on your mouse not go over nicely? [04:47] (the keyboard works great though) [04:47] You know, you could just not get broken hardware. [04:47] that would make life easy ya know :) [04:48] superm1: We're getting questions about when kdebluetooth will be fixed. Do you have any notion of the timeline? [04:48] i found it interesting to note how much of this stuff actually does attribute to bad hardware. [04:48] superm1: they went wine for me [04:48] * wgrant takes a deep breath and joins #ubuntu to see what everybody is complaining about with 8.10. [04:48] wgrant: you'll regret it. [04:48] wgrant: WAAH PULSE SKYPE FLASH [04:48] *ducks* [04:48] wgrant: forums might be quicker [04:49] I think I summed it up pretty well :D [04:49] jdong: you forgot 'firefox' in there, to go with the flash. [04:49] ScottK, hopefully in the next two weeks provided things keep going smoothly [04:49] Hobbsee: The forums are painful. [04:49] jdong: oh, and 'midnight commander isn't by default!!!' [04:49] jdong: I'm expecting more WAAAH TOUCHPAD RESOLUTION TABLET [04:49] wgrant: you've been there/ [04:49] Hobbsee: Yes. [04:49] wgrant: xorg.conf, refresh rate, etc :) [04:49] ouch [05:03] superm1: Thanks. [05:05] NCommander: Welcome. [05:06] NCommander: It looks like a bzr backport is needed. [05:06] uh oh [05:06] can we just get away with backporting bzr-svN? [05:06] NCommander: No. It needs the newer bzr. [05:07] So it's backport bzr or patch bzr-svn into submission. [05:08] NCommander: I'm guessing there are enough bzr fanboys around you can get help. [05:08] well [05:08] On the plus side, the guy who wanted the bzr backport will be happy [05:12] Good night all. [05:41] Oh dear god. [05:41] Ultimate Edition is being advertised by some users on ubuntuforums. [05:42] you're surprised? [05:42] I would have thought somebody would have killed them all. [05:43] no, because all these things are popular [05:44] I hoped UE itself would die after Canonical made them remove Ubuntu from the name. [05:44] Then there's the guy who is suggesting that people move to Linux Mint because it has Firefox 3.0.3. [05:45] now that's intelligence [05:46] I really should avoid ubuntuforums... but once I get there I can't leave without attempting to correct the misinformation... [05:47] "I can't go to bed yet, someone is _wrong_ on the internet!" [05:47] Heh. [05:48] xkcd, ever a fount of wisdom for our age [05:48] It has an answer for almost everything. [05:49] The office next to mine at uni has its walls plastered with what could well be every xkcd comic. [05:50] * NCommander running tackles wgrant [05:50] * wgrant is crushed. [05:50] * NCommander pulls out dpkg-bicyclepump [05:50] * NCommander sticks one end in wgrant and starts inflating on the pump [05:51] It's Bicycle Repair Man! [05:51] * NCommander inflates [07:31] hellooo === dfiloni is now known as devfil === shani is now known as shani^work [09:21] only MOTU's allowed here?! [09:21] no [09:22] you a MOTU? [09:22] no, just a lazy MOTU hopeful [09:22] laga: You can stop being lazy in a couple of days and fix Jaunty. [09:22] * wgrant cracks the whip. [09:23] oh crap, i promised to do thirty merges [09:23] but hey, i have lots of free time between moving and (hopefully) starting a new job :) [09:23] whats Jaunty? [09:24] elvis: the new ubuntu release, due next year [09:25] laga: 30!? I only have to do 3 by now [09:25] pochu: i lost a bet, kinda. [09:25] but one of them is wxwidgets... if we counted binary packages, I'd win :-) [09:26] emgent: we want jaunty now!! ;-) http://thc.emanuele-gentili.com/utu/ [09:26] oh neat, 14 packages for me [09:26] Ubuntu devel only involves packaging and patching, and no app dev? [09:29] elvis: mostly packaging and patching, but there are some applications developed by Ubuntu [09:29] e.g. ubiquity and update-manager [09:31] and jockey [09:40] And upstart. [09:40] And modifications to existing apps. [09:42] any work for a c/c++/python programmer in dev team... [09:56] elvis: if you want to contribute, update-manager, gnome-app-install, ubiquity and jockey are written in python, and update-notifier in C++ IIRC. If you are looking for an employment, http://webapps.ubuntu.com/employment/ may interest you [09:58] how do i get to know more about contributing to update-manager, gnome-app-install, ubiquity and jockey... [10:02] elvis: you can contact the project authors. You might also want to ask in #ubuntu-devel and read https://wiki.ubuntu.com/UbuntuDevelopment#Starting%20points [10:03] elvis: for ubiquity you can ask in #ubuntu-installer === geser_ is now known as geser [11:04] thanks people [11:10] siretart: ping? ffmpeg in experimental has broken dependencies for the -dev packages... something needs libraw1394-dev, libtheora-dev and libvorbis-dev because of some pkg-config file... please fix ;) [11:12] hi slomo :) [11:12] hi pochu :) [11:21] slomo: ok [11:21] hi slomo! [11:21] slomo: do you follow pkg-multimedia? [11:22] siretart: sometimes, depends on how much free time i have :) it was already discussed there? [11:24] slomo: I'm currently waiting for Diego's visibility patch to get committed and then update the package [11:24] that was discussed ther. [11:26] and then the dependencies inside the pkg-config file are not needed anymore because the symbols are invisible? [11:26] I don't understand that comment [11:27] that change does not touch any .pc files [11:28] why are the dependencies in the pc file needed? does some header actually include/use stuff of libtheora and friends? [11:29] I would expect so, (haven't checked that bit yet) [11:30] ok, well... the dependencies should be added :) shall i file a bug so it doesn't get lost? [11:31] yes. bonus points for proper explanation of the issue. I don't understand the problem yet, but that needs to go upstram [11:32] and least that's my impression [11:32] siretart: nope, it's a package dependency problem... some pc files requires libtheora and the corresponding -dev package doesn't depend on libtheora [11:34] slomo: let's continue that discussion in the bug report. OK? [11:34] siretart: sure === RainCT_ is now known as RainCT [12:12] Does someone agree that bug #231611 should be Invalid? [12:12] Launchpad bug 231611 in tremulous "package does not use debian/patches" [Low,Confirmed] https://launchpad.net/bugs/231611 [12:14] RainCT: indeed, it's up to the Debian maintainer to choose how he wants to modify the upstream source [12:15] so it's not a bug, and shouldn't be forwarded [12:21] pochu: that's what I think, too. I'll close it then :) === Kmos_ is now known as Kmos === LucidFox_ is now known as LucidFox [13:27] pochu: ehehe correct. I will update UTU :-) [13:54] Jaunty is in utu. :-) [14:07] ScottK, re bug 291476, I'm unable to reproduce it, maybe I haven't understand steps to reproduce the bug. [14:08] Launchpad bug 291476 in clamtk "Clamtk scans bookmarks " [Undecided,New] https://launchpad.net/bugs/291476 [14:08] DktrKranz: I expect that the user has some other issue, but since I don't run Gnome, I can't say what. [14:08] clamtk doesn't support on access file scanning, so I've no idea what can be happening. [14:09] DktrKranz: I'd encourage you to engage with the user to try and find out what the actual bug is. [14:09] I'm unable to run clamtk from nautilus or from GNOME panel, nor to reach such an option in clamtk itself [14:10] DktrKranz: I've no idea what's actually going on in that bug. I'd say either mark it invalid and move on or work with the user to get more info. [14:12] I asked user to provide a more detailed description or attach a screenshot, just to make sure I'm in the right direction [14:13] Great. Thanks. [14:14] DktrKranz: What are your thoughts on SRU to fix Bug 285793 and Bug 290691? I've asked upstream for input on the proposed patch for the latter. [14:14] Launchpad bug 285793 in mnemosyne "mnemosyne crashed with NameError in ()" [Undecided,Confirmed] https://launchpad.net/bugs/285793 [14:14] Launchpad bug 290691 in mnemosyne "mnemosyne causes cpu usage in pulseaudio" [Undecided,New] https://launchpad.net/bugs/290691 [14:22] emgent: cool, thanks! [14:22] can has jaunty upload? [14:22] pochu: np :) [14:22] if I upload something now, I'll be the third most uploader to Jaunty :P [14:23] hehehe [14:31] pochu, I don't thing, they will be on unapproved for a while, so no uploads at all for now ;) [14:31] *think [14:36] ScottK, no issues for the first bug, I'm unsure for the second one because upstream seems not to agree to work around on mnemosyne [14:37] DktrKranz: What I just got off list from him was "It look OK to me. In fact, I'll also add it to the 1.x codebase." [14:38] I think it was more he wasn't going to sort through it since he' [14:38] but attached patch seems good enought to deserve some testing [14:38] is focused on developing the new version. [14:38] I think since upstream has said he's going to incorporate the patch, we should be reasonably happy. [14:38] * ScottK goes to mark that in the bug. [14:38] * DktrKranz agrees [14:40] anyway, I'm mostly fine with it, it should not break anything and should be easily reproducible [14:41] * ScottK makes an SRU. [14:43] thanks [14:45] Actually it's later than I thought and I need to run out, but I'll do it later. [15:31] On oct 26, it was decided here that bug 275688 should be SRU. To me (but I might not see specific things) nothing has happened on it sinse. Can/should I provide more help? Maybe rename the bug to show that it contains a license issue? [15:31] Launchpad bug 275688 in fpc "Please sync fpc 2.2.2-3 (universe) with patch from bug #260464" [High,Confirmed] https://launchpad.net/bugs/275688 [15:50] lol [15:50] in #ubuntu some guy is complaining about wmv files not playing in firefox [15:51] he messaged me with a link to the file not playing [15:51] it's a porn site/video [15:51] possible troll? [15:51] I now give up voluntary tech support [15:52] Hello! My question is not exactly motu-related, but maybe you can help me anyways. [15:52] reminds me of that bug report in the fedora tracker.. the bug report contained some saucy file names ;) [15:53] How do you cross-compile gtk/gtkmm/cairomm apps for windows? [15:53] I tried http://blog.heuristicdesign.co.uk/archives/2007/07/01/cross-compiling-gtkmm-applications-to-windows/, but it didn't work out for me. [15:55] homy: try asking in #win32 on GimpNet [15:56] pochu: what server is GimpNet? [15:56] homy: irc.gimp.org [15:57] thanks. [16:07] pochu: nobody answering :) [16:10] Hello, I think that initrd image (in Intrepid) does not start console-setup script, is there a way I can verify that ? and to which package should I submit a bug report ? === RainCT_ is now known as RainCT [17:32] Hi. Is anyone available to revu my package? [17:33] * RainCT may be in a while [17:36] thanks RainCT. :-) [17:37] karooga, out of curiosity, is it a new package or an update? [17:38] csilk: only new packages need to go through REVU [17:38] I guess that answers my question [17:38] csilk: new package [17:39] RainCT, what's the process for getting an update into the repo then? [17:40] csilk: file a bug and attach the diff.gz, then subscribe ubuntu-{universe,main}-sponsors [17:40] csilk: just file a bug on Launchpad and attach the .diff.gz [17:40] (depending whether the package is on main or universe) [17:40] Ok cool, thanks for the info [17:41] hi [17:42] pochu: is there any specific mailing lists I should join if I'm hoping to be a maintainer? [17:42] i just wanted to ask, if there is maybe a packaging problem with kile [17:42] kile (kde3) wants to install konsole (kde4) that can't be right, can it? [17:43] i assume people renamed konsole-kde4 to konsole and forgot to fix the package dependency of kile ... [17:47] karooga: there is motu-mentors if you are new to packaging and want to ask questions. ubuntu-motu would be interesting, too [17:47] karooga: but you aren't forced to join them if you don't want [17:47] pochu: are they high volume? [17:48] karooga: 112 messages in ubuntu-motu on October, and 12 in ubuntu-motu-mentors [17:53] karooga: I have to leave but will look later at it [17:54] RainCT: thanks muchly. Do you need a link? [19:01] what do i have to do, if i want to update the standards version from 3.7.3 to 3.8.0? [19:01] make sure the source package is compliant with the latter version of Policy [19:06] how do i know what was changed? [19:07] the changelogs for debian-policy and ubuntu-policy should be helpful there [19:07] is there a possibility to read the changelogs online? [19:09] aptitude changelog {debian,ubuntu}-policy [19:10] grumble ok it's not alsa's fault... something else in kernelland is hanging everything for 0.1-0.2secs every few minutes [19:10] that's a job for latencytop, correct? [19:10] jdong: yes, it can help [19:11] alright, time to do some sleuthing [19:11] bdrung: also, http://changelogs.ubuntu.com/changelogs/pool/universe/d/debian-policy/debian-policy_3.8.0.1ubuntu2/changelog and http://changelogs.ubuntu.com/changelogs/pool/universe/u/ubuntu-policy/ubuntu-policy_3.8.0.1ubuntu4/changelog, respectively [19:13] thx [19:38] bdrung: you can see what changed between 3.7.3 and 3.8.0 in /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the debian-policy package [19:43] pochu: thx [20:06] siretart: ffmpeg bug is filed now, i hope that's enough information now ;) sorry for being not very verbose this morning [20:10] siretart: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504220 [20:10] Debian bug 504220 in libavcodec-dev, "Missing dependencies" [Grave,Open] [22:11] Hi all! :) Can I ask here for a problem at boot time after intrepid upgrade with encrypted root partition? [22:12] Volans22, general support is in #ubuntu [22:14] csilk: I know, but I think that is a possible bug because LUKS ask me for the passphrase twice and the 2nd time it say that is not correct [22:14] (twice for the same partition) [22:15] Volans22, Ok, I'd still ask in #ubuntu as someone else may have an answer for you, if you genuinely think you have found a bug you can report it at bugs.ubuntu.com [22:20] ok csilk, I will ask there, I was thinking that asking here and maybe directly siretart (the cryptsetup package maintainer) would be simpler, but if you prefer to not talk about that here no problem [22:22] hi all [22:22] could someone explain me what does this warning mean? "This package has a Debian revision number but there does not seem to be [22:22] an appropriate original tar file or .orig directory in the parent directory;" ? [22:24] I'm trying to follow maint-guide but really don't understand how to handle directories in non-native upstream tarballs [22:24] could someone help me with this warning? [22:25] marcin_ant, can you paste the debian/changelog file at paste.ubuntu.com [22:28] csilk: why debian/changelog? it's initial release of non-native upstream.... [22:28] csilk: there is nothing in changelog [22:28] marcin_ant, is your error a lintian generated error? [22:29] crimsun: any clues on Assertion 'pthread_setspecific(t->key, userdata) == 0' failed at pulsecore/thread-posix.c:194, function pa_tls_set()? [22:29] csilk: yes [22:29] crimsun: seems like UT2004 triggers it, mentioned in bug 219281 [22:29] Launchpad bug 219281 in totem "totem-gstreamer crashed with SIGSEGV in _int_malloc()" [Medium,Invalid] https://launchpad.net/bugs/219281 [22:30] marcin_ant, I don't understand why the changelog would be empty? [22:32] csilk: oh it's not empty it just has single entry * Initial release [22:32] marcin_ant: I assume you are trying to make a package for the first time? [22:32] marcin_ant, I was more interested in the version numbers [22:32] such as [22:32] 1ubuntu or 0ubuntu [22:33] marcin_ant: to get rid of this warning make sure that there is a file package_version.orig.tar.gz [22:33] marcin_ant: mind the underscore, in the directory below your package directory [22:35] marcin_ant: I am packaging winff-0.43 (directory) and I have a winff_0.43.orig.tar.gz in the same directory as the winff-0.43 directory [22:35] csilk: 0ubuntu1 [22:36] Elbrus, where the error said he has a debian revision number I was wondering whether he hadn't changed the default dhmake value of 1ubuntu to 0ubuntu [22:36] ahh looks like he has [22:36] yeah in that case you just need the orig.tar.gz as the error states [22:36] I guess a "debain revision number" just means any revision number then rather than something that's come from the debian repo [22:37] re [22:38] marcin_ant, you need to cd to the tarball you unpacked at the beginning of the process and do : cp softwareapp-1.2.tar.gz softwareapp_1.2.orig.tar.gz [22:40] csilk: right and this is a problem I really don't understand [22:41] csilk: what should I do if inside of tarball there is no directory like softwareapp-1.2 ? [22:41] that was supposed to be variable -_- [22:41] csilk: but instead of I got some random files in / and few subdirectories ? [22:41] marcin_ant, you need to make a copy of the original upstream tarball and include that with your package [22:42] and it has to be named like APPNAME_VERSIONNUMBER.orig.tar,gz [22:42] csilk: https://wiki.ubuntu.com/PackagingGuide/Complete says that wrong directory layout is not a reason to modify original tarball [22:43] hey guys, can anyone tell me how debuild decides that a package is a native debian package? [22:43] marcin_ant, this won't modify the original tarball, your just making a copy of it [22:43] I am having trouble packaging this piece of software. it's released as a .zip and it has a date-based version number with dashes in it. :P [22:44] csilk: you don't understand me - I'll try to explain [22:44] csilk: let's say I got Blabla.tar.gz = upstream [22:44] ok [22:45] csilk: and I want to create ubuntu-blabla package from this upstream [22:45] csilk: so I follow guide and I do: [22:45] csilk: mkdir ~/ubuntu-blabla [22:46] csilk: cd ~/ubuntu-blabla [22:46] csilk: wget http://www.example.com/Blabla.tar.gz [22:47] csilk: cp Blabla.tar.gz ubuntu-blabla_1.0.0.orig.tar.gz [22:48] csilk: ok until now - right? [22:48] marcin_ant, you shouldnt get the lintain error you pasted if you made the orif.tar.gz [22:48] *lintian [22:48] csilk: so, I tar zxvf ubuntu-blabla_1.0.0.orig.tar.gz [22:48] ok you can stop showing me what you did now [22:49] csilk: but there is no subdirectory inside Blabla.tar.gz vel ubuntu-blabla_1.0.0.tar.gz [22:49] csilk: so where should I create debian dir? [22:50] marcin_ant, dh_make will create the debian dir for you in /ubuntu-blabla [22:50] csilk: if I will create ~/ubuntu-blabla/debian then I will get this error because orig.tar.gz is expected in _parent_ [22:50] correct [22:50] csilk: "This package has a Debian revision number but there does not seem to be [22:50] an appropriate original tar file or .orig directory in the parent directory;" [22:51] csilk: so the only way to get rid of this warning is to modify original tarball and create subdirectory in it [22:51] csilk: right? [22:51] no [22:52] csilk: because I should got something like this: ~/ubuntu-blabla/ubuntu-blabla-1.0.0/debian [22:52] correct [22:53] and the orig in generallu in ubuntu-blabla [22:53] csilk: and my upstream tarball should be in ~/ubuntu-blabla renamed to orig [22:53] yes [22:53] csilk: and it should unpack sources to ~/ubuntu-blabla/ubuntu-blabla-1.0.0 [22:54] csilk: but to do this it should have this dir inside tarball - but there is no such directory in upstream [22:55] marcin_ant, you're actually confusing me know.. Give me 3 mins I'm going to very quicky make a dirty package to see if I get the same problem as you [22:55] **NOW [22:56] what's the problem? [22:57] marcin_ant, the orig should be in /blabla along with blabla.tar.gz [22:57] simple [22:58] csilk: ok and where should sources go? [22:58] in the unpacked dir [22:58] csilk: and where should be /debian in this structure? [22:58] oh wait [22:58] what? [22:58] -_- [22:58] you claim to have read the compelte guide [22:58] ? [22:59] csilk: and this is a problem [22:59] why don't I have this problem? [23:00] csilk: complete guide says that: If you are packaging your own software, or the software is not available as a tar.gz file, you can create the required .tar.gz from an unpacked source directory with a command like the following: [23:00] tar czf hello-2.1.1.tar.gz hello-2.1.1 [23:00] csilk: I think the problem is that the upstream tarball does not organize all of its files into a directory, but rather has them at the root of the tarball [23:00] radix: exactly! [23:00] at least that's my impression from when marcin said " csilk: what should I do if inside of tarball there is no directory like softwareapp-1.2 ?" [23:01] I must of glazed over that ^ [23:01] as it happens, I'm having a vaguely similar problem, so I'd like to hear the solution as well. [23:02] csilk: and what now ;) ? [23:03] marcin_ant, link to tarball please [23:05] csilk: well if you want something simple you could just tar some random files yourself [23:06] csilk: but I'm trying to package for example something like this http://plone.org/products/archetypes/releases/1.5/Archetypes-1.5.9.tar.gz [23:06] hmm sorry for not understanding you earlier, probably something to do with my impaitience today, marcin_ant you could contact upstream and request a dir layout change, alot of the time upstream are quite responsive when you tell them you are packaging for ubuntu repo [23:07] *impatience [23:07] csilk: it has a bunch of directories in / of tarball each subdirectory contains files for different deb [23:08] csilk: well maybe it's a kind of solution - but for me it's just a workaround [23:09] csilk: because Guide should describe such cases [23:09] Yes it is, personally I think the policy on not changing dir layout yourself in this case needs reviewing [23:09] marcin_ant, you could be a rebel and just change the dir layout anyway then submit the new tar.gz as a patch upstream [23:11] csilk: and provide some real solution - not just "The following are not reasons to change the original tarball: * Wrong Directory Layout " [23:12] csilk: :-) [23:13] marcin_ant, yes, I'll mention is on the mailing list, I think the policy should be changed for this specific purpose and some provision introduced as sometimes upstream wont accept pactches nor will they make the requested changes, personally all the upstream devs I've ever contacted have been more than willing to make small changes in order to get their app into the ubuntu repo [23:13] **it [23:13] but some people can be funny, it's a kind of "don't tell me how to make my software" kind of arogance [23:15] csilk: well another thing is that there are packages that are orphaned for years [23:15] csilk: I mean upstream applications [23:15] marcin_ant, I think packages like that aren't really wanted in the repo [23:15] You can use debian/rules to put files where they need to be in the binary packages. No need to re-arrange the source tarball to accomplish that. [23:15] csilk: there are libraries that are needed in ubuntu but they are few years old and they are not developed anymore [23:16] ubottu: are you alive? [23:16] Sorry, I don't know anything about are you alive? [23:16] marcin_ant, yeah that is true, it's not an ideal situation [23:16] bug #135864 [23:16] Launchpad bug 135864 in ubuntu "[needs-packaging]ppgplot" [Wishlist,In progress] https://launchpad.net/bugs/135864 [23:16] ScottK, is that documented anywhere? [23:17] csilk: thank you anyway :) [23:17] csilk: just use dh_install/install/cp/mv [23:17] I'm sure it is. I've on idea where, but debian/rules is just a make file. Bend it to your will. [23:17] on/no [23:18] crap, 15 minutes a package review and now I delete it :'( [23:20] csilk: ?? [23:21] on/no [23:21] ^ignore [23:21] csilk: "I've on idea" -> "I've no idea" [23:21] yeah i know [23:21] didnt mean to paste that === Pici` is now known as Pici [23:43] oh, cool... kvirc seems to be compatible between unstable and intrepid (unlike the rest of kde *g*) === azeem_ is now known as azeem [23:46] I know that the Ubuntu desktop edition is based upon the Debian unstable branch, but what branch of Debian is the Ubuntu server edition based upon? [23:47] Hi ricosecada. Upon the same. [23:47] ricosecada: All of Ubuntu (Desktop/Server, Kubuntu, Edubuntu..) is actually in the same repository and many packages are shared between them all [23:48] RainCT, Thanks! :-) [23:49] np [23:50] Doesn't that make the server edition a rather "buggy" system (please forgive me, but I come from a Debian "point of view" trying to understand whats Ubuntu does different regarding dev) [23:51] actually unstable is quite stable, despite its name ;) [23:52] unstable refers to how fast things change [23:52] not how many times it crashes [23:52] also, after some time in the development cycle (DebianImportFreeze), we don't sync just any new version from debian blindly any longer, but these are subject to manual reviews instead [23:53] I see [23:53] right. Ubuntu is based off Debian Unstable the same way Debian releases are based off Debian unstable. [23:53] ricosecada: well, packages are massively importe from Debian at the start of the cycle but after that only when a developer request them (and some months before release we enter "Feature Freeze" and no new versions are not allowed anymore), so there is a stabilization process [23:54] So one could argue that Debian stable is in no way "safer" than Debian unstable? [23:55] dear exim, please don't try to send me a mail via remote smtp, that says, that you don't support remote smtp with your configuration. Thanks, stefan. [23:55] What I understand is that debian stable is based upon unstable (skipping testing here), but a lot of bugs has been fixed. [23:55] ricosecada: well I think one should argue that deriving a distribution off debian unstable doesn't say much about its final stability. [23:55] I'm trying to sign a package with debsign, but it's not using my key, even though I changed DEBSIGN_KEYID. Any ideas? [23:55] well, actually debian stable is quite solid, since the freeze period (where packages no longer migrate from unstable to testing, but only after a manual review) is much longer [23:56] ricosecada: both Debian and Ubuntu have a period of stopping the influx of changes for a period before release (freezing) and focusing on stamping out bugs [23:57] Ah, okay.. so the debian freezing is just a longer freeze and perhaps, but not for sure, more bugs are caught. [23:57] RainCT, good point [23:57] Sorry, I meant jdong [23:57] ricosecada: indeed, Debian freezes for a much longer time and tries much harder to stamp out ALL the bugs. [23:57] gouki: the latest changelog entry author maybe? [23:58] cyphermox, exactly. [23:58] ricosecada: whether that's worth delaying your release X (months, years, etc) is a matter that there will never be 100% agreement on [23:58] that is ultimately why we have both Ubuntu and Debian :) [23:58] gouki: i see. did you run dch -i ? [23:58] No. Let me read about it, cyphermox [23:58] sistpoty: lol [23:59] Thanks a lot! :-) I finally get it now! jdong, your explanation was very helpful! [23:59] ricosecada: no problems, glad to be able to help :)