[00:00] oojah: Cool. I have a couple of comments but I'll give you a conditional advocation [00:00] Laney: Ok, thanks. [00:01] What's the condition? [00:01] * Laney is writing it on REVU now [00:01] Duh, yeah [00:01] lfaraone, thanks for the advice on Debian package submission about 15 minutes ago. (Was AFK for a bit). Saved an IRC transcript and I'll read it over later -- only mildly confused at this point, which probably goes to show that I don't have my head wrapped around the process yet. :-) [00:01] Short descriptions should almost always start with a lowercase letter, right? [00:03] rmunn: no problem. for "normal" non-python packages (or those where you just feel like "being a rebel"), you can upload to mentors.debian.net (like REVU), and search for a sponsor, but with DPMT you're spared the sponsor search and get the benefits from group-maintenance. :) [00:03] good night guys ;) [00:05] oojah: go go go === mdomsch is now known as mdomsch_afk [00:05] you can ping me to re-advocate after you fix it if you want [00:06] but it's not really necessary [00:07] Laney: Thanks very much. [00:07] Very good point about the copyright which ought to have been obvious. [00:08] That's fresh in my mind because I did something with some PD work recently [00:09] I'll have to deal with them tomorrow now. [00:09] i made a needs packaging bug a couple months ago but nothing has really been done... how could i get someone to look at it? https://bugs.launchpad.net/ubuntu/+bug/416634 [00:09] Ubuntu bug 416634 in ubuntu "[needs-packaging] fastpatx - quick and simple web browser" [Wishlist,New] [00:10] !revu [00:10] REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [00:10] PATX: use revu if you have a package to submit [00:10] PATX: you should submit it to REVU :) [00:10] Laney, thanks :) [00:10] thanks everybody :) [00:10] Laney: Come out some time, I'll buy you a beer. [00:10] oojah: I will and maybe even can now that nlug seems to have moved to Wednesdays [00:11] hopefully the next US UDS will be on the East Coast <_<; [00:11] I think I'm doing something this week, but maybe that's lies because I don't actually remember what it is [00:11] oh, going to Fun in the Afternoon in London [00:12] lfaraone: if xdgapp is going to be pulled in to groundcontrol and the package is already in Ubuntu then we should remove xdgapp from Ubuntu for this release IMO [00:12] I rarely make it to nlug, but will be meeting former nlug peeps for drinks at some point in the next few weeks. [00:12] oojah: let me know if it's not a monday/thursday and I'll see what I can do [00:12] Will mention it in #nlug. [00:12] How do I upload to REVU? [00:12] Night! [00:12] james_w: well, we're still on appeal on that one :) [00:12] cool [00:13] see ya [00:13] PATX: see https://wiki.ubuntu.com/MOTU/Packages/REVU [00:13] I am repeating myself, but if someone has time to review a package, please take a look at http://revu.ubuntuwire.com/p/polygraph. The is one advocation already. [00:15] oojah: the link in debian/watch should be a comment, too [00:20] oh, rats [00:20] I noticed another thing >:( [00:20] Laney: ? [00:21] get-orig-source should always download the same thing [00:22] it will get more complex [00:22] so? [00:23] its purpose is to reconstruct the upstream tarball [00:23] oh shit [00:23] !language [00:23] Please watch your language and topic to help keep this channel family friendly. [00:24] that's actually a lie, and me misremebering policy [00:24] * Laney thinks that policy is wrong here [00:24] Laney: it has to grep the upstream version from debian/changelog and get the right git revision to checkout [00:25] (and not the other way around) [00:25] actually it has to get the most recent version [00:25] but I would rather it got the version that we want to upload [00:26] dpkg-parsechangelog can make this easy enough [00:30] Ok, so how long will it take for two MOTUs to review http://revu.ubuntuwire.com/p/fastpatx ? [00:31] a long time :) [00:31] you might try PAPT in Debian [00:32] PAPT? [00:32] PATX: fix all lintian reports and then ask again [00:32] bdrung_ ok... [00:35] PATX: example, apparently you're building a debian-native package. Did you forget to include the orig.tar.gz file above where your package directory is? [00:36] Laney: oh, that's what policy says? screw policy, then. [00:36] Laney: that's really odd. [00:36] yes, it sucks [00:37] Laney: here's the get-orig-source rule I used for a git-using package I work on: http://bazaar.launchpad.net/~lfaraone/gtksheet/debian/annotate/head%3A/debian/rules#L19 , that might be useful to borrow from. [00:38] lfaraone: tell it to oojah [00:38] * Laney is a mere reviewer here [00:38] oojah: here's the get-orig-source rule I used for a git-using package I work on: http://bazaar.launchpad.net/~lfaraone/gtksheet/debian/annotate/head%3A/debian/rules#L19 , that might be useful to borrow from. [01:18] ok one error is that my email is not @ubuntu.com how can i fix this? [01:20] PATX: Run update-maintainer in the package directory [01:20] ok thanks then i can use my email? [01:20] How do you mean? [01:21] I think he wants to set the maintainer address to his own e-mail address [01:21] well i do not have a patx@ubuntu.com so when i upload the pkg to REVU i need to use my gmail correct? [01:21] StevenK, could i do anything else? [01:22] but yea thats what i want [01:23] PATX: If you're submitting something to be included in Ubuntu, you want to set the maintainer to be an Ubuntu team (all the developers is the default). The common practice is to set one's own name and email as XSBC-Original-Maintainer. If you already have your own name and email as the Maintainer, update-maintainer will do this automatically. [01:23] ok [01:23] * persia wonders if this remains appropriate default behaviour given the proliferation of third-party repositories for which nobody in Ubuntu wishes to claim any responsibility [01:24] do i run that before or after buildng? [01:24] At any point, but you'll want to have run it before you prepare the source package for upload. [01:25] ok [01:34] Ok now how would I go about fixing "This package has no debian/watch file or get-orig-source rule."? [01:46] PATX: man uscan to read about watch files [01:46] ok ty [01:51] persia, so i have to make a debian/watch??? [01:52] That's the best practice, yes. [01:52] would my pkg have any chance of getting in w/ out one? [01:54] PATX: How would anyone know when the package needs to be updated without one? [01:54] idk [01:54] But that aside, since FeatureFreeze is in a couple days, your application has a decidedly low chance of making it anyway. [01:55] But yeah, the watch file is an important component of our ability to make sure the archive is in reasonable shape. [01:55] ok [01:56] so should i just wait to do this untill the next version of ubuntu? [01:58] Actually, now isn't a bad time to get a package in shape. [01:58] But don't be surprised if it doesn't make the lucid deadline. [01:58] My recommendation would be to get the package in the best shape you can, and submit it to Debian. [01:58] That way it can be synced when archive opens for the next release. [01:59] if it doesn't get into Debian in that time, you can go back to chasing REVU. [01:59] ok === mdomsch_afk is now known as mdomsch [03:24] I wasn't quite sure where to ask this, but the BZFlag client is out dated in the main repos - since they came out with an entirely new client today. http://sourceforge.net/projects/bzflag/ [03:27] Today? Ugh. That doesn't leave much time. [03:28] Please file a bug against bzflag requesting an upgrade. [03:28] using launchpad? [03:28] * Gaming4JC goes there... [03:28] ubuntu-bug bzflag is probably the easiest way to file it. [03:32] ok thanks, and what about another substantially outdated one... Blender? [03:32] file a bug report for that too? 2.49b has been out for almost a year [03:32] lol [03:33] Blender is kinda special. [03:33] 2.49.2 is in Lucid. [03:33] And yes, Blender is a very special thing. [03:34] really? o.O [03:34] Ah, and 2.49.2 is actually 2.49b [03:55] persia: This correct? :) https://bugs.launchpad.net/ubuntu/+source/bzflag/+bug/522448 [03:55] Error: This bug is private [03:56] I've been working on fixing a small bug, but I run into issues because the quilt patch is applying changes on a file that gets deleted at build time. So, how do I go about fixing it? [03:57] Gaming4JC: Except I don't know why you've made it private. [03:57] nigelb: Why are you patching a file that gets deleted at build time? [03:57] persia: hmm, I'm unsure as well considering I never checked that option anywhere lol o.O [03:58] Gaming4JC: If you make it less private, I'll tell you if it works. [03:58] persia: I'm still unsure where its being deleted at build time or renamed [03:58] s/where/whether [03:58] nigelb: The build log should tell you. [03:58] where do I see the build log? [03:59] ah, the .build file [03:59] How did you build it? [04:00] debuild -S -sa [04:00] yes, it is getting deleted "rm -f rules/evdev rules/evdev.xml.in" [04:00] persia: made it public. :) [04:00] so that means, I can ignore the mistake in that file since its going to be deleted anyway? [04:01] nigelb: Maybe: it depends on whether it gets used before it is deleted. [04:01] Is it possible to figure that out from the logs? [04:02] Usually. Look for previous uses of the filename in the log. [04:03] only the rm -f statement [04:03] Then it's probably not used. [04:03] so, I can skip patching that file and its okay? [04:03] Gaming4JC: Did bzflag do their usual thing and not allow older clients? [04:03] nigelb: Test and see :) [04:03] thank you. Checking now :) [04:03] persia: sort of, they still allow the old client but keep telling me to update all the time [04:04] Gaming4JC: Hrm. That's better than it used to be, but still a clear hint. Thanks. [04:04] np :) [04:04] well, 'tis late here [04:04] ttyl and thank man :D [04:04] thanks* [04:26] how do I know pbuilder successfully built a package? lack of errors? [04:36] how to create package for hunspell-ta ? i'm having the dic file and aff file. [04:49] how to i review the packages in revu.ubuntuwire.com [04:54] I'm looking for a main sponser to review a patch I have submitted :) [04:54] anyone around? [04:55] persia: ^^ [04:56] bug 398873 [04:56] Launchpad bug 398873 in xkeyboard-config "Typo in gnome-keyboard-properties" [Low,In progress] https://launchpad.net/bugs/398873 [05:48] any ubuntu-sru members around to see if something is SRU worthy? [05:58] nigelb: main sponsors are in #ubuntu-devel [06:02] oh, thanks micahg [06:58] hey guys i have read through the packaging documentation. how does one determine out of the various packaging methods available which one is the best for that particular package or situation? [07:15] i try to fill a syncrequest with: requestsync -d unstable -n --lp -s python-pisa lucid [07:15] but the error is: E: The package 'python-pisa' does not exist in the Debian primary archive in 'sid' [07:16] but the package is available: see http://packages.debian.org/sid/python-pisa [07:22] toabctl: this package is very new [07:23] randomaction, yes. that's a problem? [07:23] try again in several hours [07:23] ok [07:23] thx [07:23] yes, PTS has no information on it yet: http://packages.qa.debian.org/p/pisa.html [07:26] randomaction: im just wondering. i read through all the packaging guide and im a little lost. how does one determine which method is correct to use or does it depend on what the type of package is [07:27] eagles0513875: What's your problem? [07:27] randomaction: not a problem im just trying to understand the purpose of having so many different packaging methods and how to choose the right one. im hoping to eventually become an motu but i need to get my packaging skills up to snuff first. [07:35] good morning [07:37] good morning dholbach [07:38] hi eagles0513875 [07:38] dholbach: are motus responsible for all repos? or just in charge of the packages [07:40] eagles0513875: as a MOTU you can upload packages to universe and multiverse [07:41] im not motu yet im still trying to figure out packaging. i read through the complete packaging guide yet im confused as to how to determine which out of all the options available for packaging is ideal to use, or is it dependent on the type of package that needs to be created? [07:42] there's lots of different ways to get a package done [07:42] so it is dependent on what i get used to [07:42] I learned the most by working on existing packages [07:43] so you just modify small bits here and there in order to fix a bug and you get exposed to whatever the maintainer thought they'd use for packaging [07:43] that way you learn multiple approaches [07:43] ok kool will give that a try :) [07:44] question about mentoring. it is where someone takes me for ex under their wing and shows me how to fix the bugs etc? [07:44] AFAIK the mentoring programme is having difficulties at the moment [07:45] so it's probably better to start off on your own and just ask questions in here [07:45] there's always somebody around to help out [07:51] G'morning dholbach. [07:51] oi iulian! how are you doing? [07:54] dholbach: I'm doing fine. How about you? [07:54] * iulian is doing his physics homework now. [07:55] * eagles0513875 is doing programming hw [07:55] iulian: good - thanks :) [07:55] dholbach: last question. whose in charge over all of maintaining the repositories? cuz im trying to upgrade from karmic to lucid and im getting a 403 on one of the repos [07:58] eagles0513875: https://launchpad.net/ubuntu/+archivemirrors [07:58] some mirrors might be a bit out of sync [07:58] this one hasnt been working since yesterday though [08:03] Does anyone know what does 'Apply to be an official mirror of this distribution' mean when registering new mirror? [08:11] slytherin: you got me curious as well about that [08:12] eagles0513875: If I understand correctly the official mirror (whichever it is) will be used by installer when doing a fresh install. [08:15] slytherin: i dont quite understand [08:16] eagles0513875: When I install Ubuntu from scratch the installer will have a list of official mirror for each country. So if the country I selected ininstaller has a official mirror assigned that mirror will be set in /etc/apt/sources.list. [08:23] slytherin: i know that but the one i have i hate using it cuz its on such a slow connection. and there is only one for my country. im wondering if i could setup a virtual machine with another mirror for my country [08:24] eagles0513875: Or you could buy some hosting space through community funding and manager a mirror. [08:24] s/manager/manage [08:24] i have a monster desktop that i can run a vm on. thats not a problem for me [08:26] eagles0513875: Do you own a domain and static IP? [08:26] i do own a domain but its pointed at another server atm :( [08:31] eagles0513875: you can use services such a sdyndns [08:31] http://www.dyndns.com/ [08:31] slytherin: i already do [08:32] then setting up the mirror should not be a big trouble. [08:32] slytherin: do you have any documentation or anything for that [08:32] I believe Ubuntu wiki does have some documentation. [08:33] eagles0513875: https://wiki.ubuntu.com/Archive/Mirroring [08:33] thanks slytherin [09:09] Laney: I've uploaded a new sqlite3-pcre if you wanted to check the get-orig-source. [09:29] advocated [09:32] Ta [10:45] I'm looking for a second advocate for http://revu.ubuntuwire.com/p/sqlite3-pcre Can anybody help? [11:21] * Laney adds a ticker to the agda-stdlib build [11:21] Agda + armel are not friends [11:22] Laney: How does the ticker work? I think schroot suffers from the same issue (although it may be that it's trying to build stuff that shouldn't be built for arch:any) [11:24] persia: it just generates some output so the build isn't timed out [11:25] Laney: Does one do this with a parallel process, or just extra noisiness in the part that hits the timeout? [11:25] a parallel process (it's just a simple shell script) [11:25] watches for the build's PID and the creation of the build-stamp file, typically [11:26] http://git.debian.org/?p=pkg-haskell/agda.git;a=blob;f=debian/watcher.sh;h=0de582d7162cd262e89a43dbd19c154d460ca294;hb=HEAD [11:26] like that [11:26] Laney: And how does one call it? [11:27] sh debian/watcher.sh "$$PPID" "$(CURDIR)" "$(CURDIR)/build-stamp" 'ghc' & [11:28] the locking part was added by me because I couldn't figure out how to get cdbs not to call it multiple times [11:29] So PPID is the PID of the make executing debian/rules? [11:29] yes [11:30] Nifty. I'll definitely have to give that a shot. [11:30] you could definitely make it more specific to your failure case, but this is general enough to work without much effort [11:31] even if it adds some noise to the build output [11:33] Laney: That's why I asked :) I wanted something that didn't require thought to get stuff to compile. Actually optimising to make it not need to take so long is step two. [12:01] What's the status about the libmysqlclient problem? [12:02] lbrinkma: last I saw there was still discussion about how to fix it in an sane manner. I thought it only affected building packages. [12:04] persia: yes, it's true. But i want to upload a package to REVU that depends on anjuta and anjuta depends on libaprutil, and that on libmysqlclient. So it won't work [12:04] REVU doesn't build anything, so it'll be fine. [12:05] persia: but it's hard to test it when i can't build it [12:05] lbrinkma: Indeed, and hard to review for the same reason :) [12:32] i know it's not a question related to the channel, but i just would like to know if ppa lauchnpad accepts uploads of freewares ( i packaged a software whose source code is not available .... it's already built) [12:35] paissad: The Launchpad usage policy forbid that. [12:35] slytherin, ok thanks [12:36] Does it? [12:36] I know Ubuntu accepts some freeware under certain conditions (but we don't like it, and drop it if it's buggy) [12:44] paissad: persia: I remember reading the usage conditions some time back. Can not find a link to it now. Asking on #launchpad for clarification is best. [12:45] Generally :) [12:49] paissad: Found this - https://help.launchpad.net/PPATermsofUse [12:49] ok [12:52] if it want to update a package in lucid what should I do? open [needs packaging] bug or needs update/or something like that? [12:54] om26er: Are you going to work on update? [12:54] om26er: It's not a "needs packaging" bug. It's an "upgrade" bug. Just identify the target version, the rationale, and add the upgrade tag. [12:54] persia, ok, thanks [12:54] slytherin, I will try :) [12:55] as persia said, it is upgrade bug. But if the package exists in Debian then first check if anyone is working on upgrade. [12:57] slytherin, it just released [12:57] like an hour ago [12:58] om26er: that does not mean you have to update it in Ubuntu first. :-) [13:23] * Laney is going to kick off the haskell transition later, probably [13:23] fun fun fun :) [13:30] later = now [13:30] * Laney uploads ghc6 [13:32] Go, Go, Go! [13:34] http://people.canonical.com/~pitti/scripts/syncpackage is a useful script [13:35] Laney: Take care: I've seen requests that people not use that. [13:36] Laney: It's usually not *too* hard to get a friendly archive-admin to do a batch together. [13:36] persia: how come? [13:36] I will be requesting a *lot* of syncs in the next days [13:36] Because, although it does mostly the right thing, it does it in a way that is messy within Soyuz somehow. [13:36] oh [13:37] Just find an archive admin, and tell them the plan, and have them run the syncs. [13:37] I believe the current script is similar to the one you referenced, but it's designed to be run inside Soyuz, from what I understand. [13:38] it will just look like a normal upload [13:38] maybe syncs have some special processing [13:38] They do. [13:38] * persia doesn't know the details, but suspects an archive-admin would be willing to explain. Might ask in -devel [13:38] james_w: ^^^ ? [13:40] Laney: I'd be happy to bulk-sync things for you [13:41] cool. Is it really not advised to use that script? [13:41] * Laney mainly does it to avoid hassling people [13:41] Hey, any broken packages that need some packaging fixed? I looking to help a bit [13:42] subject: ghc6_6.12.1-9_source.changes rejected [13:42] :( [13:42] james_w: could you do that sync? ghc6 from unstable [13:42] Laney: I'd only be repeating what others told me if I said that it wasn't advised. I don't know the details [13:42] it's a big orig [13:42] Laney: I can try [13:42] thanks [13:52] what's the best way to turn a normal bug into a requestsync? [13:52] edit the title and description, i'd have thought [13:52] or invalid it and requestsync again [13:52] And add the appropirate team. [13:52] & subscribe archive admin, since i'm motu & it's in loonyverse? [13:52] yes [13:53] + confirmed [13:53] persia: urgh, cjwatson is on holidays this week, we have to find someone else to backport it on the buildmachines :\ [13:54] sebner: Check with jdong about the base backport: he is the backport master (but first make sure a backport to hardy works locally for you) [13:54] directhex: + wishlist if you are motivated :P [13:55] persia: aye [13:56] if --lp is recommended, as per --help, then why isn't it the default behaviour? [13:56] it requires setting up credentials, I guess [13:56] higher barrier to entry [13:57] Laney: funnily that never worked for me ¬_¬ [13:57] ~/.udtrc would be good though [13:57] sebner: what's that? [13:58] ripps: take a look at FTBFS page. http://qa.ubuntuwire.com/ftbfs [13:58] Laney: setting up credentials [13:59] sebner: What problem did you get? [13:59] directhex: mostly historic reason, as requestsync was using mail at first, then later used python-launchpad-bugs (still before the LP API) nobody wanted to change the default of "mail" [14:00] slytherin: hmm, can't remember but I'll give it another try so we can discuss that. Btw, what benefit do I have from it? [14:00] sebner: When you use --lp it retrives info from Launchpad and hence will skip a few questions. [14:00] sebner: you could use "ubuntu-build" for give-backs :) [14:01] geser: I believe the command is buildd [14:01] ah, yes that's quite something useful :D [14:02] slytherin: no, it got renamed to ubuntu-build in lucid since it conclicted with buildd from the package buildd (and I'm sure about it as I did the rename :) [14:03] Oh. I haven't moved to lucid yet and do not plan to until it becomes final. [14:03] slytherin: ok, how do I set this stuff up? =) [14:04] geser: what about "package-rebuild" or "ubuntu-rebuild" :P [14:04] sebner: "man manage-credentials" and c&p the example from there [14:04] sebner: man manage-credentials, simplest form - manage-credentials create -c ubuntu-dev-tools [14:05] what level of access is common? [14:06] write non-private [14:06] you need it for filing sync requests [14:08] persia: argh, I just realized that dpkg itself is now also debsrc3.0 -.- [14:08] slytherin: geser: seems to have worked :D [14:09] sebner: Well, in that case, find some recipe that allows you to handle the backport. Passing someone a working recipe and asking them to execute is surely smoother than "Please do this hard thing" :) [14:09] heh [14:11] sebner: backporting 3.0 package should not be hard. Try changing the 3.0 in format file to 1.0. [14:11] slytherin: well, it's not that easy with dpkg I suppose :P [14:11] sebner: How do you know, did you try? :-) [14:11] slytherin: I'm currently looking at it === Tonio__ is now known as Tonio_ [14:32] * Laibsch hopes we don't miss the boat again for http://revu.ubuntuwire.com/p/ffgtk [14:38] porthose: maybe you can take another look if it meets your requirements now? === dholbach_ is now known as dholbach [15:05] Could someone please take a look at sqlite3-pcre? I'm looking for a second advocate. === shadesla1er is now known as shadeslayer [15:27] Hi all [15:27] Jeeves_: hi [15:27] I'm building a private package for sophie (sophos libsavi virusscanner) [15:27] that package depends on libsavi, for which there isn't a package available [15:28] now dh_shlibdeps is byting me. [15:28] Any hints on skipping dh_shlibdeps? [15:29] Jeeves_: is libsavi part of sophie? [15:29] geser: No [15:29] It is part of a non-packaged piece of software [15:29] I've tried adding --dpkg-shlibdeps-params=--ignore-missing-info to dh in the rules file [15:29] then you need to package it first? else how should your sophie package work with it? [15:30] geser: I install the software before building the package [15:30] I cannot package the other software, which is closed source and dynamically updated [15:32] Jeeves_: and your user? the expect that "apt-get install sophie" gives them a working software [15:32] geser: We are the only users. [15:33] It's a private package in a completly controlled environment [15:36] the best solution would be to also package libsavi for your use (even if it's closed source, you can skip the compilation part) [15:37] please take a look for clean sync @ bug 522700 [15:37] Launchpad bug 522700 in convirt "Sync convirt 1.1-1 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/522700 [15:37] geser: There's no way to skip shlibdebs? [15:38] Jeeves_: I don't know of any (which would a hack anyways) [15:54] hyperair, congratulations! [15:54] jcastro: thanks. =) [15:54] * hyperair just saw jcastro's retweet [15:54] ok so that means I'll get new banshee in lucid ... ? :p === mathiaz_ is now known as mathiaz === nxvl_ is now known as nxvl [16:35] persia, you around? [16:36] Hey MOTUs, if someone could have a look at http://revu.ubuntuwire.com/p/cnetworkmanager I'd sure appreciate it. Thanks in advance. [16:37] tsmithe: Kinda, but in the middle of three different things. [16:37] tsmithe: I presume this is because I didn't actually upload musecore yet? [16:37] ok. pisa has just been uploaded to debian; i was wondering if it could be synced; how should i request that? [16:37] oh, and yeah :p [16:37] tsmithe: File a sync request bug (requestsync is a good tool for this). [16:37] ok. [16:38] if it gets in before you upload musescore, hold on, and i'll make a new package which employs pisa to generate the offline manauls [16:38] *manuals [16:38] (do you think that's likely?) [16:39] Let's do that as a bugfix later if it all works by feature-freeze. Adding more coordination increases the risk of failure prior to that. [16:39] I presume we can use the same orig.tar.gz? [16:39] that's what i thought [16:39] and yes [16:40] Yeah, let's do it that way then: so we don't hit the wall in 21 hours. [16:40] Err, 31 hours. [16:41] cool; i was just concerned that you'd "waste" an upload :) [16:45] persia, sync request done; thanks. it's bug 522718 [16:45] Launchpad bug 522718 in ubuntu "Sync pisa 3.0.32-1 (universe) from Debian sid (main)" [Undecided,New] https://launchpad.net/bugs/522718 [16:50] can someone point me to where I can learn about what a package branch is, and how it should be maintained? [16:54] * popey also has a question.. [16:55] I'm looking at packaging something which is mostly just a shell script and a few other support files - source only - is there a package in the repo that i could learn from in terms of debian/rules and debian/install ? [16:58] hi mhall119|work [16:58] https://wiki.ubuntu.com/DistributedDevelopment has some information [16:58] basically a package branch is just using bzr to do packaging [16:59] or indeed any other VCS [16:59] therefore it's basically using bzr, with a few extra commands layered on top for packaging-specific operations [17:00] popey: try ubumirror [17:00] thanks [17:00] thanks james_w [17:00] trying to learn the right way of doing all this [17:06] https://launchpad.net/~ubuntu-motu <-- "Ubuntu MOTU Developers does not use Launchpad ..." [17:06] heheh [17:13] ok, I'm making package for Qimo (https://launchpad.net/qimo), it has no upstream package, so what should I put in debian/watch to satisfy lintian? [17:15] # lintian sucks [17:16] mhall119|work: IMHO You should explain it into debian/watch! [17:16] mhall119|work: if you make it a "native package" then lintian shouldn't complain [17:17] james_w: what's the difference in a "native package"? [17:17] I'd just explain it in README.source or elsewhere [17:17] (I presume you are package as a snapshot) [17:17] james_w: thanks for sync'ing liblua-iconv [17:17] abogani: explain it how? a # comment? [17:17] yeah, a # comment [17:17] Laney: I'm the original developer [17:17] mhall119|work: it's a package that is only intended for Debian-based systems, and so doesn't have an upstream releasing tarballs etc. [17:17] mhall119|work: can't you make a release? [17:19] Laney: you mean just a tarball? [17:19] sure [17:19]