[00:04] it looks like there are only symbolic links in the /usr/bin directory - no subdirectories [00:04] aside from the executable files, of course [00:09] kostmo: Your first .py file requires the second to exist before it works? [00:10] do I have to run the full pbuilder procedure every time, or ist there a way to get a shorter build? [00:10] RAOF: that's correct [00:11] Then you'll need to make a rather more proper python package. You can check out the specto package for an example. [00:15] neversfelde: 'ccache' [00:17] lifeless: thx, I'll take a look at it [00:19] ah, got it in the pbuilder howto [00:19] neversfelde, use a chroot rather than what pbuilder does (extract a base chroot, install all build-deps every time) [00:22] will try it tomorrow, gn8 now and thx for your help === rockstar_ is now known as rockstar [00:41] siretart: around? [02:32] Hm. Something's strange in our python/gtk stack; Miro has a broken folderchooser on Intrepid, but it works fine on Sid. [02:34] This may be due to havinrg 2.13.3 in Ubuntu and 2.12.10 in Sid. Interesting. [02:43] hi, how can i configure pbuilder to include updates from updates and proposed? [02:46] borschty: pbuilder login --save-after-exit (or similar), edit the appropriate files, aptitude update. [02:49] --save-after-login [02:49] Ah, right. [02:49] Something of that kidney. [02:49] ah ok, thanks [02:49] Also, 'apt-get clean' before you logout. [02:50] Otherwise pbuilder happily includes /var/cache/apt/archives/* in the base tarball [02:50] :) [03:34] Hello, when is the next sync with Debian ? [03:37] AnAnt: All the time? Or, rather, when an admin next runs the autosync script, I think. [03:37] gpm needs to be sync'ed , the current package in Intrepid has some issues [03:38] Oh? You're one of those crazy mouse-on-the-console users? [03:38] :) [03:39] yup [03:39] Have you filed a sync bug? Is it a sync? There are currently Ubuntu changes. [03:41] what does that question "is it a sync" mean ? [03:42] AnAnt: Is it a sync, or a merge? Can the current Ubuntu changes be dropped? [03:43] Also, what are the current bugs, and are they actually fixed in Debian? [03:44] yes, gpm_1.20.4-1 & -2 fixes several bugs in Debian [03:44] -2 is now in unstable [03:44] as for Ubuntu changes, I dunno what is -D_GNU_SOURCE for [03:44] but that Ubuntu change is not in Debian [03:46] Hi, I'm not entirely sure if this is the proper place to be asking this, so feel free to scream at me (or direct me to the right area). I'm trying to build a package in pbuilder against a hardy chroot, but the package requires yamp .7, which is in the intrepid repos. Even if i set the mirror to the intrepid universe it won't update the package, and I can't build it [03:50] AnAnt: Heh. apt-cache showsrc gpm suggests that Debian's gpm package has been merged, but not yet built, or possibly FTBFS. [03:50] chubs_: You'll need an Intrepid chroot. Alternatively, how did you set the mirror to Intrepid? It's entirely possible that change didn't stick. [03:51] raof: I don't want to build it againts intrepid packages, as it's intended for use on hardy. I guess I never considered that that might be alright (would it?). Anyways i set it in the pbuilderrc and i'm positive the change has stuck [03:52] it gets packages from the mirror every time [03:52] just won't upgrade any [03:53] AnAnt: In fact, looking at https://edge.launchpad.net/ubuntu/intrepid/+source/gpm/1.20.3~pre3-3.1ubuntu1 suggests that the new gpm package FTBFS. Feel free to fix this ;) [03:53] RAOF: well, maybe they should try 1.20.4-2 [03:54] Hi. I struggled to create a couple packages, but it works! However, when the package is upgraded, the config file is replaced w/o question. I've seen some packages ask if it should overwrite, option to diff, etc. How? [03:54] AnAnt: Maybe. Again, feel free to merge ;) [03:55] RAOF: I built it on hardy without any problems [03:55] But it (presumably) still needs the _GNU_SOURCE change. [03:56] Unless you know that's not needed... [03:56] Alternatively, ask in #ubuntu-devel. gpm seems to be in main. [03:57] I daresay _GNU_SOURCE was added due to a libc change [03:57] (Difference in toolchain between Ubuntu and Debian) [03:57] PMantis: Is the config file marked as one? [03:57] ah [03:58] StevenK: Probably not, I don't know how. [03:58] PMantis: If it's installed under /etc, and you're using debhelper > 5, it should be automatically [03:58] Anything installed under /etc should be automatically marked as a config file. [03:59] Hmmm Build-Depends: debhelper (>= 5), cdbs [03:59] Or, listen to the more-experienced StevenK :) [03:59] heh [04:04] RAOF: where should I put it after merge ? REVU ? [04:05] You should attach the debdiff against the debian version (and possibly one against the previous Ubuntu version) to a merge bug. [04:05] Note that gpm doesn't seem to be up on merges.ubuntu.com; I'm not sure why this is. [04:07] what does that mean ? [04:07] Possibly that merges.ubuntu.com hasn't been updated since gpm 1.20.4 entered Sid? [04:08] Possibly some other problem. It's easier to pull merges from m.u.c; there's a bunch of stuff already done for you. [04:15] * StevenK notices his name on 3 manual merges [04:15] Er, make that six :-( [04:17] Is it okay to build a package intended for hardy installation inside intrepid? Is it just a dependency thing or will it screw stuff up? [04:17] intrepid chroot* [04:18] chubs_: If it's intended for Hardy, build it against Hardy, otherwise you might depend on a toolchain package version that isn't in Hardy. [04:19] stevenk: I figured i should, just building the package requires yasm .7, which is only in the intrepid repos. [04:19] Which means you should start by back-porting yasm [04:22] I'll go off and learn how to do that. I saw a backporting section and figured it didn't apply. Thanks for the help! [04:22] chubs_: No trouble. [04:24] 1.20.4-2 is building in PPA [04:25] StevenK: _GNU_SOURCE is needed if package does not build, right ? [04:25] AnAnt: May be needed, it depends on the error [04:25] ok [04:27] I'm not going to worry about the config file issue right now... but I *really* wish my apt repo was secure. When I add a Release.gpg, apt-get cannot download Release... [04:30] Hello! [05:01] If I have a python application that can be installed with a "setup.py" script, how can I wrap that as a .deb package? [05:02] kostmo: By calling 'setup.py' in debian/rules. Or using the CDBS magic. [05:03] ok, I tried that, but I get a 'permission denied' when I run debuild. [05:04] it seems to be actually installing the python application into my system, when all I really want to do is roll the .deb package [05:05] Right. So, you'd need to set the install path when using setup.py. [05:06] RAOF: ok, gpm built on my PPA (https://launchpad.net/~aelmahmoudy/+archive) how do I file a merge bug for gpm ? [05:07] the line that gets permission denied is: copying build/lib/rocket_backend.py -> /usr/lib/python2.5/site-packages [05:07] will setting the install path via setup.py make some kind of chroot environment? [05:07] kostmo: Yeah, you need to set the install prefix to something that isn't system-wide. [05:09] ok, once I do that, is there an easy way to grab the list of files that setup.py installed and pass them to dh_install? [05:10] kostmo: You won't have to. You should get setup.py to install the files to where they need to be (generally $(CURDIR)/debian/$pkgname) [05:11] AnAnt: https://wiki.ubuntu.com/MOTU/Contributing or https://wiki.ubuntu.com/MOTU/Launchpad/Guide [05:22] RAOF: thanks [05:28] ok, now I'm running this in my debian/rules: python setup.py install --prefix=`pwd`/debian/`dh_listpackages`/usr [05:29] and it gets past several commands after the line "running install_lib" [05:30] Those backticks probably won't get properly expanded. Since debian/rules is a makefile, you probably want something like $(CURDIR)/debian/ [05:30] kostmo: I suspect you want $(CWD) in place of `pwd` [05:30] but then it stops at this: [05:30] running install_data [05:30] creating /usr/share/pyrocket [05:30] error: could not create '/usr/share/pyrocket': Permission denied [05:30] or $(CURDIR) is even better :) [05:30] If you get that error, it usually means your setup.py isn't honoring your prefix request. [05:32] it honored it for the py_modules keyword, but not for the data_files keyword, it seems [05:44] Where do you tell setup.py to install it? [05:44] kostmo: ^^^ [05:46] this was the line from setup.py: data_files=[('/usr/share/pyrocket', ['joystick.svg', 'pyrocket.png'])] [05:47] my rules file says: python setup.py install --prefix=$(CURDIR)/debian/`dh_listpackages`/usr [05:48] kostmo: IIRC for data files in distutils /usr is assumed. Try leaving that off. [05:49] what if I want the same installation behavior whether my application is installed via setup.py directly or via a .deb? [05:50] The same thing applies; 'python setup.py install --prefix=/foo/bar' should stick _everything_ under /foo/bar [05:51] kostmo: You might want to pastebin your setup.py; that's likely to help people to help you. [05:52] i'm going to try omitting the usr part quick [05:55] I'm also getting a lintian error: E: pyrocket_0.5_i386.changes: bad-distribution-in-changes-file hardy [05:57] You'll want to call it 0.5-0ubuntu1 [05:57] You'll also want to make it arch: all rather than arch: any [06:08] RAOF: in my control file, it already does say Architecture: all [06:08] I'm not sure where that i386 is coming from [06:12] Here is my setup.py: http://paste.ubuntu.com/22286/ [06:13] debuild now completes, but the files that the setup.py installed do not copy into my system when I install the .deb file [06:14] do I need to respecify all the files in the *.install file for dh_install? [06:17] and here is my debian/rules file: http://paste.ubuntu.com/22289/ [06:28] and where is the package itself? [06:28] already in revu? [06:30] is it necessary that i have to fix some bugs(etc) before i can apply for a team? [06:31] nop [06:31] but the administrators won't accept you if they aren't sure you are woking [06:31] so you need to show some work [06:31] and make you known [06:32] for example [06:32] i started working on the server team on my early stages [06:32] nxvl :i was looking at some bugs in Pythonista, but wasnt sure of teh fixes as most of them require some expertise in the modules [06:32] but i didn't get approved on the LP team until i demostrate some work on the team [06:32] i am comfortable with Python, and hence am looking at contribution on the same lines. Can you guide me to some suitable starting points? [06:33] bliZZardz: If you can find bugs in python packages worth fixing (you figure out the python) we will help you learn to package the fix. [06:33] that is quite a big horizont [06:33] the python guy here is ScottK-laptop [06:33] but it's more important to find the type of packages you want to work with [06:34] ok. [06:34] nxvl : exactly. that is where i am going berserk. [06:34] ScottK-laptop: can you give me a few good starting tips. I did not quite understand " If you can find bugs in python packages worth fixing" [06:34] because to be comfortable with python doesn't mean you will be comfortable with pygtk or pyqt (if it exists) [06:34] bliZZardz: Perhaps have a look at Bug #241352 and tell me what you think. [06:34] Launchpad bug 241352 in enthought-traits-ui "mayavi2 willnot run" [Medium,Confirmed] https://launchpad.net/bugs/241352 [06:35] ok..give me few mins - let me have a look at it [06:35] so you need to focus on your packages of interes [06:36] for example i'm also comfortable with python, but i work on C packages because im interested in server stuff [06:36] so - most of the problems are with python packaging? ultimately leading to upstreams? [06:37] well yes [06:37] we use to work with upstream a lot [06:37] but not always [06:37] so you will need to code also [06:37] ScottK-laptop: btw, i finally started my nm process [06:37] :D [06:38] nxvl: Great. You may beat me at the rate I'm going. [06:38] ScottK-laptop: my advocate will be kees, i'm really happy [06:38] nxvl, ScottK-laptop : i would be more interested in development than packaging [06:39] ScottK-laptop: we are not far away in the list :D [06:39] bliZZardz: OK. What are your interests? KDE, Gnome, server? [06:39] in developing what? [06:40] ScottK-laptop : anything in python. would prefer something on server, also applications are fine. [06:40] heh [06:40] bliZZardz: Do you use KDE or Gnome? [06:40] gnome [06:40] so python is your new toy and you want to play with it? [06:40] or something like that? [06:40] nxvl: Are you writing your centralized server admin stuff in Python? [06:40] lucas: hi! [06:41] ScottK-laptop: not yet [06:41] nxvl : nope. i have been doing lots of application programming, which is like lot more boring stuff. not want to build more on top of that [06:41] ScottK-laptop: i'm writing lenses now [06:41] hey, if anyone's into python packaging [06:41] ScottK-laptop: and i think augeas will have enought lenses for intrepid+1 [06:41] i have a fun bug [06:41] ScottK-laptop: so i will start writing it then [06:41] pwnquin : share it, let me try [06:42] well [06:42] you will have to package a lot [06:42] its fixed in debian [06:42] but also to write code [06:42] so is not so packaging oriented [06:42] so a novice might be able to figure it out [06:42] https://bugs.edge.launchpad.net/gnome-games/+bug/234865 [06:42] Launchpad bug 234865 in gnome-games "Package glchess fails to install and ask removal of gnome-games" [Unknown,Confirmed] [06:43] technically, i think its part of main :/ [06:45] Looks like python-support needs to be updated in Intrepid then. [06:45] pwnguin : am a n00b on it, but can you guide me as to how one goes on fixing it(so that i can get a flavour of it) [06:45] well, this one's got a patch in debian, so you'll need to look there [06:46] bliZZardz: from a packaging perspective, have you done anything like read the guide yet? [06:47] pwnguin :this one : https://wiki.ubuntu.com/PackagingGuide ? [06:48] I think so. there's also a video by dholbach [06:48] pwnguin :i went though the video - one in youtube. [06:49] let me read the guides more and ask Qs(if i have any) [06:50] quick Q -> is packaging the first step for a Ubuntero? [06:50] uuh no? [06:51] if i remember correctly, you just need to sign the CoC [06:51] pwnguin : CoC? [06:51] !coc [06:51] The Ubuntu Code of Conduct to which we ask all Ubuntu users to adhere can be found at http://www.ubuntu.com/community/conduct/ [06:52] See also: https://help.ubuntu.com/community/SigningCodeofConduct [06:53] and after that? [06:53] after that you live by the code? [06:54] :) [06:55] i meant - CoC -> Packaging -> and then? [06:57] bliZZardz: It's not really a direct progression. [06:58] persia : Hi. ok.. i understand that some time is required in it [06:58] There are lots of different ways to help Ubuntu. Those participating in the community are encouraged to sign the CoC. After that, it's best to do as much as you like. [06:59] bliZZardz: we try to avoid declaring a hierarchy [06:59] except maybe sabdfl [06:59] This can be packaging, it can be artwork, it can be documentation, it can be testing, it can be community work, or really anything else. [06:59] This channel mostly concentrates on packaging. [07:00] ok. [07:00] there is a percieved Ubuntu developer path of Ubuntero -> Member -> Motu -> Core Dev [07:00] pwnguin : what is sabdfl ? [07:00] Mark Shuttleworth [07:00] !sabdfl [07:00] Mark "sabdfl" Shuttleworth is our favourite cosmonaut, the founder of Canonical and the primary driver behind Ubuntu. You can find pieces of his thinking at http://www.markshuttleworth.com [07:01] * pwnguin thinks the bot should know more about "Self Appointed Dictator For Life" and less about astronauts [07:02] sabdfl the nearest we have to a Big Boss [07:02] :D [07:02] * nxvl HUGS persia [07:02] aha... bdfl and sadfl! [07:02] * bliZZardz smiles [07:02] yes [07:02] this forum has been amazing...thanks for the members patience. i will read up more and contribute to the max. [07:04] q: request for a mentor can happen only after i contribute something? I am clueless sometimes and need some experienced eyes to correct me :) [07:05] bliZZardz: You can ask anytime, but it's not mandatory to have one. You can also just work with various people here in the channel. [07:05] * ScottK-laptop thinks that is actually better because you learn more from different people. [07:05] * bliZZardz concurs [07:06] * bliZZardz hopes to get some nice tshirt with ubuntu on soon ;) [07:08] My upstream project update that I hoped to get released/uploaded to Debian prior to DIF is done and uploaded. [07:08] ScottK-laptop: i have a doubt on the debian-policy [07:09] ScottK-laptop: a package can Suggest a package outside of main? [07:09] yes? [07:09] afaik, universe/multiverse were enabled by default a while ago [07:10] pwnguin: It's a somewhat false perception. While that sometimes happens, there are people who each any of those states directly [07:10] persia: of course [07:10] i mean in debian-policy, not the ubuntu adaptation of it :P [07:10] nxvl: You mean can it suggest something non-free or contrib? [07:10] nxvl: Suggest is OK, Recommends is not OK. [07:10] some of the core devs are now approved on a "dont touch the kernel" basis etc [07:11] can i suggest a package to be included? [07:11] ScottK-laptop: yep [07:11] pwnguin: There's been a couple now. It's not just kernel. [07:11] pwnguin: "Self Appointed"? "South African", right? :) [07:11] nxvl: Then what persia said. [07:11] Actually one of them was you may touch ONLY the kernel. [07:11] persia: yes, i know that Recommends, Depend and Build-Depends aren't ok, but i was unsure about Suggests [07:11] hence the etc [07:11] SCottK: I suspect the policy will move back into alignment, with Recommends-by-default. [07:13] persia: i'm reading the new policy (3.8) [07:13] and i think it's post-default_Recommends [07:14] nxvl: It is. Debian had recommends-by-default much earlier than Ubuntu. Ubuntu currently allows main to recommend universe, but that will likely change. [07:15] persia: intrepid will we a nightmare [07:15] Is it allowed, or just not explicitly forbidden? [07:15] (unless main/universe ceases to mean anything before such a rule is implemented) [07:15] Which may well happen. [07:15] wgrant: It was explicitly allowed at one point, which is part of why recommends-by-default was delayed. [07:16] persia: Ah, I hadn't realised. [07:16] Is such policy actually documented anywhere? [07:17] Not as such. There was a mailing list thread about it some long time back, and it basically reached consensus as "doesn't matter". When recommends-by-default came in Debian, it was blocked in Ubuntu due to that consensus. [07:17] (As I remember and understand: ask someone more intimately involved with apt packaging to get a better story) [07:19] slangasek suggested MIRs would be required for stuff to stay recommends if it was in Universe. Not sure if he was speaking policy or perspective. [07:20] ScottK: It's a result of the current implementation of main. Without either an MIR or recommends-removal, it's hard to make a CD. [07:20] Whether such an implementation accurately reflects intentional policy is a different matter. [07:21] BTW, not all installs have Universe enabled. It was just enabled for new installs. Upgraders may not have it enabled. [07:21] That's not such a huge impact. Even with recommends-by-default, apt will allow installs/upgrades cleanly (but with a different package set). [07:21] ggood morning [07:22] It's about how packages are selected for a CD, or for the images. [07:22] dholbach: guten nacht mein freund! [07:23] nxvl: sleep tight :) [07:23] i still have some time here [07:23] but it's funny how you wake up at the same time i go sleep [07:23] :D [07:23] :-) [07:24] btw [07:24] i didn't told you (i think) [07:24] they confirm me the next Packaging Jam [07:24] Guten Morgen dholbach [07:24] i will have a 4 hours session [07:24] hi geser [07:25] nxvl: NICE - that's great - is there a lot of excitement in your loco? [07:25] yes [07:26] they are really exited about the GBJ [07:26] ROCK :) [07:26] * dholbach hugs nxvl [07:26] so they are making me run some packaging jams to have more people be able to fix some bugs :D [07:26] * nxvl HUGS dholbach back [07:26] :) [07:26] hi guys!! anyone know which package provides mozilla-xpcom [07:26] for example RoAkSoAx is in charge of running he's city GBJ [07:26] :D [07:27] nxvl, still can't build after doing the patch by hand, now it shows checking for MOZILLA_COMPONENT... configure: error: Package requirements (mozilla-gtkmozembed >= 1.7 mozilla-xpcom >= 1.7) were not met: [07:27] using pbuilder? [07:28] nxvl, i'll do the GBJ if i get my things done by that date [07:28] nxvl, yep [07:28] Debian accepted my upload, so I think it's time for me to go to sleep. [07:28] Good night all. [07:29] nxvl, what could be wrong?? i'm guessing have to add a new build-dep? [07:32] did you merged the build-depends as i told you to do? [07:33] yeaaaaah [07:35] mm [07:35] then dunno [07:35] :D [07:35] maybe it is because i have to make a change in the patch or maybe i missed something i'll check T.T === Zic_ is now known as Zic [07:47] lol it built with a supposed old library [07:49] dholbach: i'm just going to sleep, can you please help RoAkSoAx [07:49] i'm going to sleep too [07:50] i'll take a look at it tomorrow :) [07:50] sleep tight RoAkSoAx and nxvl [07:50] thanks dholbach, have a nice day :) [07:50] chau nxvl [07:51] well good night! [07:51] read you tomorrow! [07:52] * nxvl HUGS everyone [07:52] nxvl: now im around :) [07:54] siretart: i'm just going [07:54] but [07:55] can you please take a look at augeas? [07:55] http://revu.ubuntuwire.com/details.py?package=augeas [07:55] http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=augeas [07:58] siretart: if you have some comments on it please send me an e-mail or comment there [07:59] siretart: i will be really thankful if you give it a look [07:59] :D [07:59] now i'm gone [08:28] ScottK: looked at Bug #241352 in enthought-traits-ui (Ubuntu) . Quite interesting. [08:28] Launchpad bug 241352 in enthought-traits-ui "mayavi2 willnot run" [Medium,Confirmed] https://launchpad.net/bugs/241352 [08:39] can someone correct me w.r.t Bug #242275 ? [08:39] Launchpad bug 242275 in pidgin "problem with any contacts..." [Undecided,Incomplete] https://launchpad.net/bugs/242275 [08:41] ScottK, persia, pwnguin : anyone there? === jscinoz_ is now known as jscinoz [08:44] bliZZardz: For myself, I'm not more likely to check an IRC channel for being pinged. That said, I'm not the best person to answer that: you likely will find help in #ubuntu-bugs for the best way to help with triage. === LucidFox is now known as LucidFix === LucidFix is now known as LucidFox [09:16] hi all [09:16] Hello [09:17] I want to request a sync for Midori web broswer 0.0.18 [09:17] I was building my own deb package for Hardy when a Midori dev told me to ask for a sync here [09:18] Pasteurized: make sure you follow the steps on https://wiki.ubuntu.com/SyncRequestProcess [09:18] Pasteurized: Have you reviewed the Ubuntu changes, and confirmed they are no longer required? [09:18] Given our preference for not implying Ubuntu is Debian, I suspect it needs a merge, rather than a sync. [09:19] (or maybe just a backport) [09:20] Pasteurized, does flash work now using midori? [09:20] I didnt try yet the .18 [09:21] Pasteurized: There's an .18 in intrepid (and a different one in Debian experimental). You might want to try one of those first. [09:22] I could use the .18 Intrepid version on my hardy ? [09:22] no epiphany-webkit package jet :( [09:23] Or maybe it'll better to finish my package building of v0.0.18 and install it [09:24] Pasteurized: Only if you really want. As two other people already packaged .18, I'd think you might save yourself some effort if you used one of theirs. [09:25] ok, so now I just need to know where to find it (I was hoping to find it one getdeb.net) [09:25] find it on getdeb.net* [09:26] Pasteurized: You can get source from launchpad.net/ubuntu/+source/midori [09:26] There are binaries compiled for intrepid, but they may not work if you are running hardy. [09:26] If it works for you, please request a backport so others may also share. [09:26] !backports [09:26] If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging [09:35] I have a dependency error (libpango1.0-0) while installing .18 on my hardy [09:38] Pasteurized: Try recompiling the source against hardy then. That might solve it. [09:40] i'm going to try it [09:43] I guess dustutils' deb packages, are not "valid", right? [09:43] * distutils [09:43] amikrop: Does distutils actually have a deb target? [09:44] RAOF: Hmm... it seems not.... [09:44] Heh. [09:45] :P === asac_ is now known as asac === fta_ is now known as fta [10:09] hi RainCT [10:09] <\sh> emgent: bug #227859 I'll take care of it when my buildds are updated [10:09] Launchpad bug 227859 in esperanza "Please merge esperanza 0.4.0-2 (universe) from Debian unstable" [Wishlist,Confirmed] https://launchpad.net/bugs/227859 [10:17] RainCT: should screenruler be showing up in hardy at this point? [10:20] Hi ianm_ [10:22] ianm_: not yet, I'm looking for someone who can upload it to Debian. Then it'll be for a while in the "NEW" queue (this can be just some days or up to a few weeks) and finally it will be in the Debian sid repos and will be copied into Intrepid's (once it's there you/me can request a backport for Hardy). [10:22] wow what a process :) [10:23] ianm_: There are also shorter processes, but that one is used to increase the number of users who will benefit from the new package. [10:25] In debian/rules, what entries are necessary? [10:26] I mean, which "make" entries are required? [10:27] amikrop: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules [10:28] Please do include get-orig-source and patch if they have meaning for your package (non-native or patched, respectively) [10:28] persia: ok, thanks [10:41] Do I need the dh_test* commands? [10:45] amikrop: If you do. What are you trying to accomplish, and how would the presence or absence of dh_test* help? [10:45] yes, dh_testdir and dh_testroot [10:46] persia: Alright, I understand :-) [10:47] RainCT: Those are certainly not required (although they are likely to be helpful) [10:49] If a package has an ubuntu revision, do we append build1 for rebuilds? [10:49] * RAOF looks at the uninstallable monodevelop [10:50] Doesn't dh_clean call the clean debian/rules entry? [10:50] amikrop: No [10:50] I ask this, because I don't see $(CURDIR)/build deleted after each package generation. [10:50] RAOF: No, just bump the Ubuntu revision. "build1" is code for "We built this too soon, and need to rebuild, but still want to sync, and Soyuz still doesn't support binary NMUs". [10:50] persia: Thought so. [10:51] * RainCT would say "dh_clean is called as part of clean", but better doesn't say nothing as he only knows cdbs :) [10:51] s/nothing/anything [10:51] <\sh> amikrop: dh_clean is being called inside clean: target [10:52] ok [10:53] hello. Some days ago I created a package for Debian, but I'm not finding any sponsor. What should be changed in it to try to get it uploaded in Ubuntu Universe? (Is there any useful link?) (I just joined the REVU Uploaders team) [10:53] RainCT: dh_clean can make clean: easier, but one is free to delete all the modified files differently if one prefers. [10:54] Tooba1: In 95% of cases, the change is to switch the version to -0ubuntu1, the target to intrepid, and the bug closure syntax in debian/changelog. [10:54] persia: yes, I know it's possible to create a package without debhelper at all, but that doesn't really make sense in most cases :) [10:54] imho [10:54] RainCT: Why not? [10:54] persia: I have this http://paste.ubuntu.com/22316/ debian/rules but $(CURDIR)/build stays on, after the generation, and I can't see why. [10:55] thanks, so I'll take a look at other package for those points [10:55] s/ckage/ckages [10:55] Tooba1: and change the Maintainer to be MOTU if the current address isn't @ubuntu.com [10:55] And also think very carefully about whether you want to do it. [10:55] You mean, remove my address? [10:56] Tooba1: you can keep it in a XSBC-Original-Maintainer field [10:56] ok [10:57] persia: well, because it's doing the same work yourself (and note the "imho" :)) [10:57] persia: Neither $(CURDIR)/debian/files is removed (although I have removed -k from dh_clean). It seems the "clean" entry is never called :-/ [10:57] RainCT: Where it is indeed the same work, I agree with you. I can imagine a package construction where it isn't, but perhaps I'm thinking too deeply :) [11:00] * RainCT syncs the REVU keyring [11:00] amikrop: What happens if you call debian/rules clean? [11:00] $ ./rules clean [11:00] dh_clean [11:00] dh_clean: cannot read debian/control: No such file or directory [11:00]