/srv/irclogs.ubuntu.com/2008/11/05/#ubuntu-motu.txt

marcin_anthello00:06
nhandlerHello marcin_ant00:06
marcin_antis there any packaging guru that could answer me few questions?00:07
jdongI'd suggest going ahead and asking instead of asking if you can ask :)00:07
marcin_antok I'll shoot00:08
marcin_antI think that debian policy and ubuntu packaging guide are pretty weird and I really don't understand it's policy according to non-native packages00:09
marcin_antI got an example00:09
marcin_antI want to package application that is available as upstream tar.gx00:09
marcin_antgz00:09
marcin_antbut inside this tar there is a bunch of directories let's say dira dirb dirc00:11
marcin_antI want to create few packages from this upstream let's call it test-dira, test-dirb, test-dirc00:12
=== asac_ is now known as asac
marcin_antso I created directory named test-dira-1.0 then directory named debian00:12
marcin_antin it00:12
marcin_antand in debian dir I created all required files and watch file with required path00:13
marcin_antI also added get-orig-source target with uscan script00:13
Adri2000marcin_ant: if you have one orig.tar.gz, you have one source package and one debian/ directory. then from that source package you can create multiple binary packages00:14
marcin_antthen I returned to test-dira-1.0 and: debian/rules get-orig-source00:14
marcin_antAdri2000: please read carefully what I write00:14
marcin_antAdri2000: I understand that I got one source package and I understand that I can create multiple packages from it00:15
marcin_antAdri2000: but this "story" is not about it00:15
jdongmarcin_ant: well you're not doing it correctly00:15
jdongand that's what Adri2000 is trying to tell you.00:15
jdongit's unclear from your abstract example exactly what you are trying to do00:16
jdongwhat are dira, dirb, and dirc in relation to the orig.tar.gz?00:16
marcin_antjust few words00:16
marcin_antjdong: problems are: 1. orig.tar.gz doesn;t have single directory inside it has 3 directories called dira, dirb, dirc00:17
jdongyou've said that.00:17
marcin_antanyway I'll just finish00:17
jdongI asked what specifically are a b and c?00:17
jdongand what would you like to turn them into?00:17
marcin_antso I run debian/rules get-orig-source00:17
marcin_antthen get-orig-source downloads upstream package to parent of debian00:18
marcin_antthis is the place where should upstream orig.tar.gz go00:18
marcin_antso I got:00:19
marcin_ant~/dira.orig.tar.gz00:19
marcin_ant~/test-dira-1.0/00:19
jdongwhy do you have dira.orig.tar.gz?00:19
jdongI thought you said orig.tar.gz contained dira, dirb, and dirc?00:19
marcin_antjdong: because it is upstream name00:20
jdongok, then what are dirb, and dirc for?00:20
jdongare they supporting libraries / dependenices?00:20
jdongrelated binaries?00:20
marcin_antjdong: read again - they are inside of dira.orig.tar.gz00:20
jdong*YOU SAID THAT*00:21
jdongI am saying your abstract example is too vague for me to say anything useful.00:21
jdongI'm trying to understand why upstream has three directories inside a source tarball for a project where one name is dominant00:22
marcin_antjdong: get this upstream: http://plone.org/products/archetypes/releases/1.4.6/archetypes-1-4-6-final-bundle-tar.gz00:22
jdonglol ok that's annoying enough upstream made a bundle that's a tarbomb00:22
marcin_antjdong: or maybe better 1.4.5 release because 1.4.6 has bug in it's name...00:24
marcin_anthttp://plone.org/products/archetypes/releases/1.4.500:24
marcin_antanyway take a look what is inside00:24
jdongyeah I am looking at it right now00:25
jdongupstream's site is timing out right now (45s and counting), is the software available in an unbundled tarball?00:25
jdongit seems like the sub-directories are distinct python modules (packages)00:25
marcin_antapt-get source zope-archetypes00:26
marcin_antyou will get orig.tar.gz 1.4.2 version (afair)00:26
jdongok, cool, so it has already been packaged00:27
marcin_antjdong: packaged 1.4.2 current from 1.4 branch is 1.4.600:27
jdongok, so you just need to update it to the latest upstream version00:28
marcin_antjdong: ok but now we can talk about something less abstract ;)00:28
jdongso, it uses the one "source package generates multiple binary packages" paradigm00:28
marcin_antjdong: ok but let's say that I want to make few changes in /debian directory00:29
jdongthe alternate case is repacking the source tarball into several distinct source packages00:29
jdongalright?00:29
marcin_antjdong: ok propably - but it's not a problem for me to produce multiple binaries from this source tar00:29
marcin_antjdong: problem is different00:29
jdongcontinue :)00:29
=== woody86- is now known as woody86
marcin_antjdong: I really don't understand what to do with it's internal directory structure00:30
ajmitchNB: zope-archetypes was removed from debian, replaced by zope-plone300:30
jdongmarcin_ant: what ajmitch is probably relevant now00:30
jdongmarcin_ant: but at any rate, to answer your original question00:30
jdongmarcin_ant: so the orig.tar.gz file is simply the same thing as the tar.gz you get from upstream00:31
marcin_antjdong: right00:31
jdongmarcin_ant: the diff.gz file from Debian is a patch to the extracted .tar.gz directory00:31
jdongmarcin_ant: it primarily is supposed to add the debian/ directory00:31
jdongmarcin_ant: roughly what's done when you apt-get source is "tar xzvf orig.tar.gz; cd orig-folder; zpatch -p1 < ../diff.gz"00:31
marcin_antjdong: and if I will run tar zxvf on it I will get a bunch of directories instead of single dir00:31
jdongmarcin_ant: in this case, there's a notable exception that the upstream tarball is a tarbomb00:32
jdongi.e. it blows up into multiiple directories in the current directory :)00:32
jdongmarcin_ant: dpkg-source (the extractor) is smart enough to detect this situation00:32
marcin_antjdong: right00:32
jdongmarcin_ant: it automagically creates a sourcepackage-1.2.3 directory first and then unpacks inside of there00:32
panglosshey guys, I am trying to do the debian/watch part of the packaging guide, and usan is not finding anything at the url I am putting in00:33
jdongmarcin_ant: if you want to make a change and build a source package again, you simply run debuild -S00:33
marcin_antjdong: ok but let's use this as an example00:33
jdongmarcin_ant: the system will be smart enough to detect what you changed, use the orig.tar.gz and update the diff.gz00:33
jdongmarcin_ant: if you want to update to a new version, you need to use the uupdate tool00:33
jdongmarcin_ant: it takes a tarball for the new upstream version as an argument, and correctly rebases the existing diff.gz on top of the new orig.tar.gz00:34
marcin_antjdong: let's say that I want to do this from scratch let's forget about 1.4.2.deb etc00:34
jdongmarcin_ant: ok, if you want to do it from scratch, in this case00:34
jdongmarcin_ant: you'd first make a archetypes-1.4.2 directory00:34
jdongmarcin_ant: then you'd unpack the orig.tar.gz into there00:35
marcin_antjdong: zope-archetypes-1.4.200:35
jdongmarcin_ant: yeah, you get my point00:35
marcin_antjdong: ok and that is a problem(!)00:35
jdongmarcin_ant: then you can run dh_make inside there, letting it know where your orig.tar.gz is00:35
marcin_antjdong: orig.tar.gz will not unpack into this directory00:35
jdongmarcin_ant: why not?00:36
marcin_antjdong: https://wiki.ubuntu.com/PackagingGuide/Complete says that:00:36
marcin_antmkdir ~/hello && cd ~/hello && wget http://ftp.gnu.org/gnu/hello/hello-2.1.1.tar.gz00:36
jdongmarcin_ant: the packaging guide is written under the assumption upstream isn't retarded and packages their product as a tarbomb.00:37
marcin_antjdong: so in our case I should: mkdir ~/zope-archetypes-1.4.200:37
jdongmarcin_ant: so yes, in our case we have an exceptional case where upstream is retarded00:37
marcin_antjdong: cd zope-archetypes-1.4.200:37
marcin_antjdong: ok I get it00:37
marcin_antjdong: but another thing00:37
marcin_antjdong: this upstream is really nightmare00:38
jdongmarcin_ant: note that the orig.tar.gz doesn't get wgetted into ~/zope-archetypes-1.4.2 :)00:38
jdongmarcin_ant: so it'd be more like mkdir ~/zope; cd ~/zope; mkdir z-a-1.4.2; wget tar.gz, cd z-a-1.4.2; tar xzvf ../*.tar.gz, and so on00:38
jdongbut you get my point00:38
marcin_antjdong: yes I noticed and this is a part of my next question00:38
marcin_antjdong: there is a lot of packages that have single directory inside tarball00:39
jdongyep, that's the way it's supposed to be, in fact00:39
marcin_antjdong: but these direcories have different name00:40
marcin_antjdong: let's say that we want to create package zope-archetypes and got zope-archetypes.orig.tar.gz00:40
marcin_antjdong: with single dir inside called Archetypes00:40
jdongmarcin_ant: the dpkg-source helpers that handle the orig.tar.gz for you are generally smart enough to figure this out00:41
jdongmarcin_ant: they work around most of the quirks with packaging conventions00:41
marcin_antjdong: then I just can untar and create debian dir inside this Archetypes directory - right?00:41
jdongmarcin_ant: correct00:41
jdongmarcin_ant: note for dh_make to work you must rename that dir to archetypes-1.4.200:41
marcin_antjdong: ok so last thing00:41
jdongmarcin_ant: dh_make requires the current directory to be in format (name)-(upstream version)00:42
marcin_antjdong: let's say that I don't have upstream tarball yet00:42
* pangloss pokes nhandler00:42
marcin_antjdong: or I want to create new upstream version00:42
marcin_antjdong: I got: ~/zope-archetypes/zope-archetypes-1.4.2/debian00:43
marcin_antjdong: I create all required files in debian dir and I also watch file with url to upstream and get-orig-source00:43
marcin_antjdong: then I cd to ~/zope-archetypes/zope-archetypes-1.4.2 and run debian/rules get-orig-source00:44
marcin_antjdong: it will download tar.gz for me and this will be renamed to orig.tar.gz and will go to: ~/zope-archetypes (parent of zope-archetypes-1.4.2)00:45
marcin_antjdong: so far so good but it's not good because zope-archetypes-1.4.2.orig.tar.gz will not untar sources to zope-archetypes-1.4.2 (where debian directory is)00:46
jdongmarcin_ant: that's okay00:46
marcin_antjdong: it will untar sources to Archetypes.... and what should I do with this?00:46
jdongmarcin_ant: dpkg-source doesn't just blindly run an untar00:46
jdongmarcin_ant: the actual dpkg-source command that unpacks a Debian source figures this out00:47
jdongmarcin_ant: I'll give you an example from your archetypes package:00:47
jdongmarcin_ant: go back to "apt-get source zope-archetypes" like we did before00:47
jdongmarcin_ant: if you notice, it fetches three files: .dsc, .diff.gz, .orig.tar.gz00:47
marcin_antjdong: ok I need to test it00:47
jdongmarcin_ant: if you look at the .orig.tar.gz, it's the same 5-different-directory source archive00:47
marcin_antjdong: right00:48
jdongmarcin_ant: but when apt-get source runs "dpkg-source -x foo.dsc", it gets unpacked into zope-archetypes-1.4.2/00:48
jdongmarcin_ant: that's what I'm saying -- dpkg-source -x takes care of this discrepancy for you00:48
jdongit's something that you don't have to worry about00:48
marcin_antjdong: what if it;s initial release?00:48
marcin_antI need to untar this manually to zope-archetypes-1.4.2?00:48
jdongmarcin_ant: ok so let's say we're dh_making manually because this is the first release00:49
jdongmarcin_ant: remember how we just got over how to manually unpack the tar.gz to the right directory, then run dh_make?00:49
jdongmarcin_ant: well, after you do that *once* , run dh_make, and tweak debian/* to be the way you like it00:50
jdongthen you run debuild -S00:50
jdongthat builds the orig.tar.gz, .diff.gz, and .dsc file in ../00:50
marcin_antjdong: ok I (propably) get it ;)00:52
jdongmarcin_ant: alright, cool. hopefully that was a bit helpful :)00:52
jdongmarcin_ant: it takes some time to sink in, and a lot of practice ;-)00:52
marcin_antjdong: it's weird and it's NOT described at all in CompleteGuide(!)00:53
jdongI also might suggest starting off trying your first package with something that goes by the rules a bit better00:53
jdongmarcin_ant: Over my entire course of packaging software for Fedora, Ubuntu, and Gentoo this is about the 3rd time I've seen a tarbomb from upstream00:53
jdongmarcin_ant: it is by far the minority of cases :)00:53
marcin_antit's not my first package it's first that has so ugly upstream00:53
jdongmarcin_ant: but I think the key point to take from this is that dpkg-source's extractor and builder has a bunch of magical rules built in that try to intelligently work around these inconsistencies00:54
marcin_antjdong: I got bad luck as always ;)00:54
jdongin general that stuff will work if you trust your tools :)00:54
jdongotherwise a bit of digging through manpages and script sources might get you a more concrete understanding00:54
jdongI admit that I'm not in the latter group :)00:54
jdongI just blindly use my tools and scream loudly here when they don't work!00:55
marcin_antjdong: to be honest I really would like just download tar and put it untarred in package and then use tarball.mk from cdbs and it would work without any problem :)00:55
jdong:)00:55
jdongholy crap who exploded in my launchpad account?00:56
jdongI've got 50 new bugmail00:56
marcin_antjdong: thank you very much00:56
effie_jayxHeh00:56
jdongmarcin_ant: you're absolutely welcome :)00:57
StevenHarperUkHi, I am submitting a new version of my Package (Easycrypt) I need to update both Hardy and Ibex - do I submit 2 bugs?01:02
ThayleHow can I get involved?01:09
jdongThayle: see link in topic01:10
ThayleOh, hehe, didn't notice that...01:11
jdongno probs, let us know if you have any specific questions that doesn't address :)01:11
ThayleAlright, thanks jdong.01:11
jdongasac: stupid question: How do you start firefox with a different profile but NOT have it remember that profile the next time you invoke a firefox?01:31
jdongasac: i.e. I have a "default" and "appliance" profile. How do I make Firefox use profile "default" unless I explicitly start it with the "appliance" profile?01:32
jdongplaying around it seems like FF is pretty good at remember the last profile you told it to use01:33
StevenHarperUkhi Any MOTUS abot o check https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/29390301:46
ubottuLaunchpad bug 293903 in easycrypt "Candidate revision easycrypt_0.2.3.0-0ubuntu" [Undecided,Confirmed]01:46
asacjdong: err not sure ;) -P ?01:55
asacyeah just -P and then select the profile without "remember" ;)01:56
asacmaybe not the best solution cant really remember that it remembers the last used if you specify it at command line01:56
asacif it does that then -P is most likely the only workaround01:56
lifelessasac: hope I have given enough info on  bug 8322901:58
ubottuLaunchpad bug 83229 in firefox "could not close window with ctrl-W until I clicked on thebackground" [Undecided,Incomplete] https://launchpad.net/bugs/8322901:58
jdongasac: lol ha like there's a "remember" option ;-)02:00
nhandlerHi Jazzva02:08
JazzvaHello nhandler02:09
nhandlerIs MoM being updated? It only goes up to 'm' right now02:58
lifelessthere was an issue02:58
Keybukyes03:00
lifelesslol03:00
* jdong gives himself stupidity cookie.03:02
jdong /usr/bin/skype: "cd /usr/lib/skype && skype"03:02
jdong5 minutes and 10 gigs of swap later. D'OH03:02
copprohuh?03:03
jdongcoppro: think about it.03:03
* coppro is not that familiar with skype...03:03
jdongcoppro: /usr/bin/skype runs "cd /usr/lib/skype && skype"03:03
copprooh03:04
copprothat would be a problem03:04
jdong:)03:04
coppro./ much?03:04
TheMusoouch.03:04
jdongcoppro: yeah yeah :P03:04
jdongcoppro: that's revision ~crack2 :P03:05
NCommanderAnyone having any issues uploading to REVU?03:09
copproNCommander: I don't think so03:09
* NCommander had one of his uploads rejected03:09
coppronope, I'm good03:09
copprothe update for http://revu.ubuntuwire.com/details.py?package=metakit worked fine03:10
copproNCommander: is it set to jaunty? I've had some issues related to that (not with REVU, but other package tools)03:10
NCommanderYeah03:10
ajmitchNCommander: you don't deserve to upload yet?03:11
NCommander....03:11
* NCommander whacks ajmitch with a stick of DOOM03:11
NCommanderwhere do the crontab logs end up on spooky?03:11
copprospooky?03:13
nhandlercoppro: The server hosting REVU03:13
copprooh03:13
NCommanderTheMuso, I have two merges that needs uploading, cegui-mk2, and midori03:58
TheMusoNCommander: Do you have bugs for them, or do you just have some files I can grab from somewhere?03:59
NCommanderI can kick the changesets onto mentors since REVU is kinda broken ATM03:59
TheMusoNCommander: Whereever is easiest for you.03:59
NCommanderTheMuso, http://mentors.debian.net/debian/pool/main/m/midori/midori_0.1.0-1ubuntu1.dsc04:01
TheMusograbbing.04:03
ajmitchNCommander: revu ought to work... sort of04:05
NCommanderajmitch, its been fixed?04:05
NCommander(or hit with a big enough hammer?)04:05
TheMusoheh04:05
ajmitchNCommander: I said that before04:05
ajmitchmkdir /root/.gnupg to work around it for now04:05
ajmitchuntested with running it from cron, but it should have accepted your upload04:06
ajmitchthe directory just has to exist, it doesn't even need to put anything in there04:07
NCommanderoh good, I can stop using mentors04:07
ajmitchs/using/abusing/04:07
TheMusolol04:07
NCommandernothing in mentors ToS says it has to be used for Debian review work04:07
NCommanderOr more specifically, nothing outlaws Ubuntu reviewers from using it04:07
ajmitchI doubt that the admins want the bandwidth & diskspace used for such a purpose04:08
* NCommander notes he uses REVU for Debian package reviewing04:08
NCommanderand mentors for Ubuntu ...04:08
NCommanderGo figure04:08
TheMusoNCommander: re midori, since it is a merge, you have dropped all prior changelog entries. I.e the only changelog entry you have is the merge entry, and no other entries from previous ubuntu changes.04:14
NCommanderI swore I didn't do that ...04:15
NCommanderArgh04:15
NCommanderTheMuso, hold on04:15
TheMusonp04:15
NCommanderTheMuso, there04:17
NCommanderFixed and reuploading04:17
TheMusoNCommander: Ok.04:17
TheMusoNCommander: on mentors?04:17
NCommanderno, REVU, since that's working now04:18
TheMusooh ok.04:18
TheMusonot on front page yet.04:18
* ajmitch refreshes & hopes that it shows up04:22
ajmitchhm..04:22
ajmitchthe directory exists04:23
NCommanderajmitch, its working04:23
ajmitchI just didn't see it on the revu frontpage04:24
NCommanderajmitch, its in updated packages04:24
NCommander(since its not new)04:24
ajmitchgood04:25
TheMusoNCommander: test building midori.04:28
TheMusoNCommander: uploaded.04:30
NCommanderyay for my first jaunty upload04:31
TheMusoNCommander: And your second merge? Is that ready for review/upload?04:31
NCommanderyup04:31
* ajmitch needs to find something to merge04:31
TheMusook04:31
NCommanderajmitch, MoM04:31
ajmitchNCommander: MoM doesn't have its main/universe lists generated at the moment, either04:31
NCommanderajmitch, yes it does04:31
ajmitchso it's digging through package directories04:32
ajmitchhttp://merges.ubuntu.com/ <-- do you see universe.html there?04:32
NCommanderOh04:32
NCommanderHrm04:32
NCommanderWhere'd it go04:32
NCommanderIt was there less than an hour ago04:32
ajmitchran off with DaD04:32
TheMusoI see it not on revu...04:32
TheMusoNCommander: cegui-mk2 doesn't seem to be on revu.04:33
NCommanderyeah04:33
NCommanderOdd04:33
NCommanderOh04:33
NCommanderbah04:33
NCommanderits on its way04:33
TheMusook.04:34
NCommanderUpload complete04:42
TheMusook.04:42
NCommanderajmitch, run move_uploads.sh for me04:42
* jdong starts debdiffing marillat04:42
TheMusoGrabbing.04:45
ScottKStevenK: Would you be around and able to do a sync for me to fix a security bug?04:52
StevenKScottK: Possibly04:53
ScottKStevenK: Would you be up for syncing libspf2 out of incoming.  The Debian Maintainer nicely left the LP reference in debian/changelog and everything.04:54
TheMuso8/c04:55
StevenKScottK: Version in Intrepid/Jaunty is -0ubuntu1. Do you have a sync bug? :-)04:56
ScottKI'm writing it as we speak.04:57
ScottKStevenK: Bug #29395604:58
ubottuLaunchpad bug 293956 in libspf2 "Please sync libspf2 1.2.9-1 from Debian Unstable (Main)" [Undecided,New] https://launchpad.net/bugs/29395604:58
StevenKIs it unstable, or incoming?04:59
ScottKIncoming04:59
ScottKIt's aimed at Unstable.04:59
ScottKStevenK: ^^05:00
fabrice_spHi all.Can we already request syncs for Jaunty? I've just updated Bug #275534.05:02
ubottuLaunchpad bug 275534 in enblend "[sync request]Please sync enblend 3.2 from Debian experimental" [Wishlist,Confirmed] https://launchpad.net/bugs/27553405:02
ScottKfabrice_sp: You can, but you shouldn't mark it confirmed unless you are MOTU and have confirmed it is ready.05:04
fabrice_spScottK: ok. So I'll let him as NEW. Thanks.05:05
StevenKScottK: Synced05:05
ScottKStevenK: Thanks.05:06
* StevenK adds one to the beer tally05:06
ScottKInterestingly enough he nicely said "merge changes from Ubuntu" and left the Ubuntu changelog entries in.05:06
ScottKThat's more generous than I usually see.05:06
NCommanderScottK, most debian developers like to forget we exist05:07
* ScottK is still not going to UDS, so keep the list in a safe palce.05:07
ScottKwgrant: I thought you might enjoy Bug 29395005:08
ubottuLaunchpad bug 293950 in launchpad "Software related to ... page lists wrong "Uploaded to" for packages in Testing/Unstable" [Undecided,New] https://launchpad.net/bugs/29395005:08
wgrantScottK: Its presence in Lenny or Sid is unrelated to Ubuntu.05:10
wgrantBut yes, it's still wrong.05:10
ScottKwgrant: True.  Feel free to pile on.05:10
wgrantIt might just be because gina was run over Lenny first,.05:11
wgrantSo it should be fine for future packages.05:11
ScottKwgrant: The why isn't my problem.05:11
ScottKI'll be able to tell once auto-sync runs.05:11
wgrantI'm not sure if the autosync is going to be using NSS yet, so that might well be irrelevant.05:12
StevenKNSS?05:13
StevenKWhich would the autosyncer using Name Service Switch?05:14
wgrantNative source syncing05:14
StevenKOh05:14
TheMusoNCommander: cegui-mk2 uploaded.05:15
NCommander\p/05:15
NCommanderuh05:15
NCommander\o/05:15
* StevenK is trying to understand native source syncing05:17
lifelesswhy would it be differnet05:18
lifelessjust don't copy a base tarball05:18
lifelessor rather, only copy05:18
NCommanderStevenK, new LP interface/CLI?05:20
StevenKNCommander: Huh?05:21
NCommanderStevenK, I take it some sorta new launchpad interface for doing native source syncing?05:22
StevenKNCommander: I have no idea05:22
NCommanderIs it active yet?05:23
StevenKNCommander: I don't know anything about it myself05:23
NCommanderAh05:23
persiahttps://blueprints.launchpad.net/soyuz/+spec/native-source-syncing05:24
ScottKpersia: As is usual for a LP spec the useful information isn't available "You are not allowed to view this page."05:30
persiaScottK, Certainly, although it helps make it clear that "native" is about native-to-Soyuz, rather than being about native packages.05:31
ScottKpersia: Perhaps for you.  From the small crumbs the customers are allowed to see it's not clear how that relates to syncing at all to me.05:32
persiaHuh?  I don't see anything different than you.05:33
NCommanderhttps://dev.launchpad.net/ - it will be here soon enough05:33
ScottKpersia: Yes, but it sounds like you (or someone) is making a connection that I'm not understanding.05:33
ScottKNCommander: It's already past the promised date for it.05:34
ajmitchNCommander: sorry, I was out, hopefully revu did the right thing for you05:34
persiaScottK, Oh.  That's me.  As I read it, it's about having some shiny button that lets one sync sources directly, rather than having someone run the syncpackage script.05:35
NCommanderScottK, ?05:35
persiaShould address the Hobbsee-can't-sync issue.05:36
ScottKOK.  I don't see that in the snipper, but we'll see someday I guess.05:37
persiaWell, I could be mistaken, but as I understand it, the archive-admins just run a script to work around it missing in Soyuz now, and "natively" means to me "inside Soyuz".05:39
persia(at least in the context of a Soyuz spec)05:39
ScottKRight and I read it as mashing stuff from one Ubuntu pocket to another.  No idea if that's at all right.05:41
persiaAh.  The difference being that I've also looked at the summaries for https://blueprints.launchpad.net/soyuz/+spec/sync-workflows and have seen glimpses of an apparent Debian archive import on staging in the past.05:47
Hobbseehmm?05:58
persiaHobbsee, native-source-syncing possibly meaning you get a button to perform syncs (as I believe that's one of the archive-admin tasks that doesn't work for you).06:01
Hobbseeoh, that would be nice!06:07
Hobbseeany ETA, or?06:07
Hobbseejust that they're planning it?06:07
superm1i hope the button is shiny.  shiny buttons are always more exciting06:08
persiaNo.  The spec just came up in conversation, and the spec is private, so I was guessing as to the effect.06:08
Hobbseehmm.  That looks old to me.06:10
persiaRather old.  Yes.  Still desired by many.06:10
Hobbseethat's irrelevant, surely :P06:11
Hobbseea whole lot of them are sitting with 1.2.x milestones, which, afaik, has long passed, so it certainly doesn't look anywhere near current.06:11
HobbseeThrerefore, no point at all getting excited.06:12
wgrantHobbsee: NSS is being implemented. That's why we have Debian imported into LP now.06:12
Hobbseewgrant: yes, that one is.  That affects a lot more people.06:13
Hobbseewgrant: doesn't necessarily mean that anything's happening on related bits.06:13
wgrantPerhaps.06:13
persiaHrm?  Doesn't NSS mean a shiny button for archive-admins?  A shiny button for the rest of us would be nice, but I thought that was sync-workflows06:13
Hobbseepersia: via command line, yes.06:14
wgrantIt makes the shiny button possible to implement.06:14
ScottKwgrant: What is NSS.06:14
wgrantScottK: Native Source Syncing.06:14
ScottKwgrant: I know what the acronym is.  I don't know what that translates to in the system.06:15
wgrantScottK: copy-package.py, but for Debian packages too, basically.06:15
wgrantSo copying the package within Soyuz.06:16
HobbseeScottK: means you can do stuff like copy packages from -proposed to -updates and such, too.06:16
wgrantRather than downloading it from Debian and falsifying a changes file.06:16
Hobbseeor from ppa directly to ubuntu, etc.06:16
wgrantRight, pocket copies are part of it.06:16
ScottKHobbsee: I got that, I'm just having trouble with how it affects syncing.06:16
NCommandercan you copy from backports->updates?06:16
ScottKNCommander: Yes.06:16
NCommanderoh good06:17
wgrantScottK: Since they now run gina over sid and lenny, they can use copy-package.py on it just like they can PPAs or other pockets.06:17
ScottKThat's been possible for some time.06:17
NCommanderThat will make it easy to do an SRU of Xfce 4.4.3 <g>06:17
ScottKNCommander: Look at KDE 3.5.1006:17
NCommanderThat was released to SUR?06:17
NCommander*SRU?06:17
ScottKYep.  It's in -updates now.06:18
krishnaI was trying to build gnome-games from source.. I have built most of the dependencies.. but still i get this error.. http://paste.ubuntu.com/67751/  can someone have a look at it?06:29
persiakrishna, Are you working from upstream sources or Ubuntu sources?06:31
krishnapersia: upstrean06:33
krishna*upstream06:33
krishnapersia: but how does it really matter?06:34
persiaOK.  Take a look at what gets done before running ./configure in the gnome-games debian/rules from the Ubuntu sources.  It looks to me like you're missing some preparation steps.06:34
iuliannhandler: ping (Wanted to know if you're working on checkinstall merge. I already merged it and all I have to do now is to file a bug).07:45
StevenKArgh. No fair merging checkinstall07:46
iulianHmm07:48
* iulian wonders why07:48
Hobbseeunless 'merge' == 'remove'07:49
NCommandercheckinstall is packaged?07:55
NCommanderew07:55
* NCommander agrees w/ Hobbsee 07:55
Hobbseeyes,it is07:55
StevenKcheckinstall was one of the first packages I fixed.07:56
StevenKHobbsee thanked me by thwaping me07:56
Hobbseehe deserved it.07:56
* StevenK ponders a removal/blacklist07:57
Hobbseethat'd be nice07:58
Hobbseeoh, there must be a release goal for killing yada from the archive, too.07:58
persiaYou know, as much as I dislike checkinstall, and somewhat regret being in the changelog, it's probably better to fix it's egregious issues than to ban it, and have people use random buggy versions.07:58
Hobbseewell, ifthey use random buggy versions, then we don't have to support it.  same deal as automatix, etc.07:59
StevenKStill 23 things Build-Depend on it07:59
* wgrant stabs Hobbsee dead.08:00
persiaHobbsee, We don't support checkinstall-created packages now, but we do support checkinstall.08:00
* Hobbsee dies bloodily all over wgrant, and carefully rebuilds him with yada before duying.08:00
persiaThere is no careful rebuilding with yada!08:00
Hobbseepersia: yes, and i'm objecting to the supporting of checkinstall :P08:00
wgrantI had to SRU a package that used yada once... that hurt.08:00
persiaHobbsee, I guess.  You know, it could be improved...08:01
persiaIt's horrid mostly because it's incomplete, rather than being purely a bad idea.08:01
Hobbseei was thinking more based on how people used it,but yes08:02
siretartuh, archive already open? that was quicker than I expected...08:02
StevenKsiretart: It's a lie08:02
persiasiretart, Indeed.  Opened a few hours ago.08:02
Hobbseeit's still a lie.  just like the cake.08:02
Hobbseeand the ponies.08:02
* persia misses the ponies08:02
siretartah. so I have a few more days finishing the ffmpeg package :-)08:02
* NCommander reads from the book of the dead and revives Hobbsee 08:02
wgrantsiretart: It would have been earlier if it weren't for some surprise bootstrappings.08:03
Hobbseeoh, thanks08:03
NCommandersiretart, someone decided to care about ports!08:04
siretartwow. who did that?08:08
siretarterr. who does care?08:08
Hobbseesiretart: the insane one.08:08
siretartelmo?08:08
siretart;)08:08
framstaghi there, the guys from #ubuntu-server told me this is the correct channel for my question:08:21
framstagI want to add a new server application to ubuntu - where should I start?08:21
persiahttps://wiki.ubuntu.com/UbuntuDevelopment/NewPackages08:22
framstagI am using ubuntu for several years, but only as consument, not as a developper or maintainer08:22
framstaggreat, https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages is exacrly what I was looking for!08:25
framstaga meta-question: how difficult is it as non-motu-member to file in a new package?08:26
framstagin respect to social acceptance of a "newbie" :-)08:26
framstagI want to avoid of hearing: "we don't know you. go away and earn some recognitions"08:28
NCommanderframstag, generally it is08:29
NCommanderframstag, normally because getting something packaged is a rather large piece of work08:30
NCommanderOnce you do a few uploads with people to fix bugs and such, people are usually more receptive to packaging things08:30
framstagok, then is this approach better (more successfull): I ask a motu-member to package my software?08:34
framstagI then only have to convince one thar my software is import enough :-)08:35
framstagor is there already a huge queue of packinging requests?08:37
=== not_rly is now known as orly_owl
verwilstemgent: ping11:41
StevenHarperUKhi, are any motus about to check https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/29390312:16
ubottuLaunchpad bug 293903 in easycrypt "Candidate revision easycrypt_0.2.3.0-0ubuntu" [Undecided,Confirmed]12:16
=== thekorn_ is now known as thekorn
RainCThi12:48
RainCTporthose: it's all yours12:48
porthoseRainCT:  thx12:50
RainCTvorian: if you're planning to do the ncpfs merge: the package is maintained by the Debian QA Group now, so try to get any remaining changes directly into Debian13:23
RainCTvorian: and I forgot the actual question, are you planning to do the merge? :)13:27
nxvl\o/ jaunty is open!13:32
lfaraoneHow exactly does one use MoM?13:36
emgentgo.13:36
lfaraoneemgent: ?13:37
nxvlemgent: exactly!13:37
stefanlsdWe filing bugs like normal for merges?13:43
nxvlyep13:45
nxvltitle: Please merge $PACKAGE $VERSION from debian unstable13:45
stefanlsdnxvl: thanks :)13:46
nxvlReport: Debian has a new version of $PACKAGE that needs to be merged13:46
nxvland attach the debdiff13:46
nxvlthat's pretty much it13:46
ScottKjdong: I can't set importance on intrepid-backports bugs (just like Hardy started out).13:50
sebnerstefanlsd: and subscribe u-u-s ;) (if it's in universe)13:55
nxvljames_w: around?13:56
nxvlsebner: right13:56
nxvlsebner: are you merging ssmtp or should i?13:56
nxvli think i a sync is needed13:57
sebnernxvl: didn't even know that there is something new :) If you like it you can do it. otherwise I'll do it in the evening13:57
nxvlsebner: ok, i will take care of it13:58
sebnernxvl: thank you13:58
nxvlsebner: indeed it is, you took your patch from debian13:58
nxvl:P13:58
sebnernxvl: /me doesn't have a jaunty pbuilder yet ... :P13:58
sorensebner: Dude, it's been almost 24 hours! :)13:59
lfaraoneAnybody care to explain how a non-motu requests a merge?14:00
sebnersoren: I know, sry :P I didn't have time, I also have to upgrade to jaunty. don't forget that :P14:00
nxvllfaraone: file a bug, attach you debdiff and subscribe u-u-s14:00
sebnernxvl: but in the evening I also need some security power (if you are interested)14:00
nxvlheh14:00
james_wnxvl: hey hey!14:01
jdongScottK: should be fixed now14:01
sorensebner: :)14:01
sebnerbbl :)14:01
james_wlfaraone: https://wiki.ubuntu.com/UbuntuDevelopment/Merging14:02
sebnersoren: btw, tell colin, upgrading is *cool*. also that lenny is frozen not that much can break :P14:02
ScottKjdong: Yep.  Thanks.14:02
sorensebner: Tell him yourself :)14:03
* sebner hides14:03
nxvljames_w: now that jaunty is open, are there already any plans on how to do the bzr transition?14:08
nxvl(as in move everything to bzr)14:08
* geser searches after sebner :)14:08
james_wnxvl: lots of plans :-)14:08
nxvljames_w: :D as in starting now?14:08
james_wnxvl: I have most of the branches ready, we will hopefully be opening them up for testers soon14:09
nxvljames_w: or we will wait a bit?14:09
nxvljames_w: ok, count on me14:09
lfaraonejames_w, nxvl , thanks!14:09
james_wnxvl: launchpad isn't quite ready to host them yet, so they won't be as useful, but we're getting there14:09
james_wnxvl: and you can't merge from Debian natively in bzr yet, which means it doesn't help this period that much14:09
lfaraonejames_w: this is going to be a very interesting cycle. (with the bzr features yet)14:09
james_wnxvl: but I look forward to your feedback14:10
james_wlfaraone: I agree14:10
nxvljames_w: ok, then when i can put my hands on it please let me know14:11
nxvljames_w: we can discuss it widely next week with some beers and pisco!14:11
nxvl:P14:11
james_wnxvl: I look forward to it :-)14:11
stefanlsddoes anyone have an idea why debian is doing this - http://paste.ubuntu.com/67910/14:14
stefanlsdits in the .pot file14:15
brooniestefanlsd: if there's no textual difference I'd expect the .pot file has been edited with a tool that did the reformatting.14:16
StevenHarperUKhi, are any motus about to check https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/29390314:16
ubottuLaunchpad bug 293903 in easycrypt "Candidate revision easycrypt_0.2.3.0-0ubuntu" [Undecided,Confirmed]14:17
stefanlsdbroonie: yeah. would appear so.  Should i just delete them from the debdiff, or should we actually just fall in line with what they did so we dont need to keep doing it manually?14:17
* broonie shrugs14:18
nxvl\o/ i think i'm done with all my packages14:18
nxvlthis is fun14:18
lfaraoneWon't debian devel be slow since they'd be working on perfecting lenny?14:20
verwilstif i have a deb in my ppa14:23
verwilstwell, ready to be sent to my ppa14:23
verwilstbut i want to build it for hardy and intrepid14:23
verwilstwhat do i need to do?14:23
verwilstmake 2 seperate changelogs?14:24
verwilstone with a hardy entry and one with an intrepid one?14:24
directhexverwilst, yes14:24
verwilststrange but ok ;)14:24
ScottKStevenHarperUK: Unless that's a typo on the bug title, you'll want a 1 on the end of the revision number.14:25
ScottKstefanlsd: Delete them from the debdiff.14:25
stefanlsdScottK: yeah thanks. ended up doing that.14:25
ScottKverwilst: #launchpad is a more appropriate place for PPA questions.14:25
StevenHarperUKScottK: your right - its just a typo - fixing it now14:26
StevenHarperUKScottk: another Q I have put ibex in my debian changelog - is that wrong?14:26
ScottKStevenHarperUK: jaunty14:27
StevenHarperUKScottk: its for Hardy -> jaunty14:27
azeemcan maybe somebody quickly install "avogadro" on intrepid and see whether it crashes on startup? (it's a QT4 app)14:27
ScottKStevenHarperUK: If it's for an upload now, it should say jaunty for the target release.14:28
verwilstScottK: ok!14:29
StevenHarperUKScottk: i want users og hardy to get it14:29
StevenHarperUK*of14:29
ScottKStevenHarperUK: First get it into jaunty and then get it backported.14:29
ScottK!backports | StevenHarperUK14:29
ubottuStevenHarperUK: 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 !packaging14:29
StevenHarperUKScottK: is that a simple job?14:30
ScottKGenerally.14:30
StevenHarperUKScottK: I am targetting 2 major bugs in hardy and intrepid, is the correct route the backport one?14:32
directhexwhat's the best way to track changes in build-dep names, for backportability?14:32
directhexuse libfoo-dev | libfooold-dev ?14:32
ScottKStevenHarperUK: If you're fixing major bugs then perhaps not.14:32
james_wdirecthex: that would work14:33
directhexjames_w, any better ideas?14:33
ScottKStevenHarperUK: See https://wiki.ubuntu.com/StableReleaseUpdates14:33
StevenHarperUKScottK: ok so I set to hardy - if I do will it get to intrepid also?14:33
james_wdirecthex: though a change in -dev name usually indicates a change in API, is that not the case there?14:33
ScottKStevenHarperUK: No.  You need to provide a debdiff with appropriate naming and numbering for each release.14:33
directhexjames_w, no. or if it is, not enough to prevent building.14:33
StevenHarperUKScottk: sounds like a lot of effort14:34
directhexcups (1.3.7-6) unstable; urgency=low14:35
directhex  * Rename the package to cups.14:35
ScottKStevenHarperUK: It can be, but we need to be careful with changes to released versions.14:35
james_wdirecthex: what would be the problem with the alternatives approach?14:35
directhexjames_w, just want to make sure to do the right thing. libcupsys2-dev -> libcups2-dev is a build-dep change to worry about between releases14:36
StevenHarperUKScottK: can I confirm - hardy (easycrypt_0.2.3.0-0ubuntu1) intrepid (easycrypt_0.2.3.1-0ubuntu1) jaunty (easycrypt_0.2.3.2-0ubuntu1)14:37
james_wdirecthex: yeah, I just wondered why you asked if there were any better ideas. I don't see a problem with using "|"14:37
ScottKStevenHarperUK: For Hardy/Intrepid we don't ship a new upstream release.  We patch the existing one.14:37
* ScottK goes AFK for a while.14:37
StevenHarperUKScottK: so I make the Jaunty one (easycrypt_0.2.3.0-0ubuntu1) and it gets patch for me?14:38
james_wStevenHarperUK: easycrypt is at 0.2.2.10-0ubuntu1 in hardy/intrepid/jaunty14:40
james_wfor jaunty upload your 0.2.3.0-0ubuntu114:40
StevenHarperUKok I will and il diff it against the 0.2.1014:41
james_wfor hardy create a patch to fix the bug and apply it to the existing hardy package, changing the version number to 0.2.2.10-0ubuntu1.08.04.1 or similar14:41
james_wsimilar for Intrepid, with 0.2.2.10-0ubuntu1.08.10.114:41
james_wStevenHarperUK: https://wiki.ubuntu.com/SecurityUpdateProcedures has a guide to choosing a version number for a particular release14:42
james_wthe last line of that table is your case14:42
StevenHarperUKjames_w: I have never done a patch before as I am upstream I do a full release14:42
james_wStevenHarperUK: ok that's probably ok as long as the release just fixes major bugs, you may want to check with someone from motu-sru14:43
StevenHarperUKjames_w: do I make 3 seperate bugs in launchpad too?14:44
james_wnope14:44
james_wjust nominate the bug for the affected releases14:45
jcastropersia: ~6 minutes!14:54
=== cody-somerville_ is now known as cody-somerville
=== Czessi_ is now known as Czessi
slytherinNCommander: there?15:44
StevenHarperUKjames_w: hi you still here?15:50
james_wStevenHarperUK: yep15:51
StevenHarperUKjames_w: I have done the jaunty one : https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/29390315:52
ubottuLaunchpad bug 293903 in easycrypt "Candidate revision easycrypt_0.2.3.0-0ubuntu1" [Undecided,Confirmed]15:52
StevenHarperUKjames_w: what should I do for the others?15:52
StevenHarperUKjames_w: just some deb-diffs?15:53
james_wfor the jaunty one please provide the .diff.gz from the source package you created, along with a pointer to the tarball that you released15:54
StevenHarperUKjames_w pointer is there15:55
james_wthe .diff.gz isn't15:55
StevenHarperUKjames_w: is that ok now15:56
james_wlooks better, I haven't reviewed it15:57
StevenHarperUKjames_w: now the other releases - do I need to make anything?15:58
StevenHarperUKjames_w: there the same, its just the changelog that needs to be right15:58
james_wyes, something needs to be different15:59
james_wat least the changelog15:59
StevenHarperUKjames_w: do I have to make more and compare them to the 2.2.10 ?15:59
james_wcompare them?15:59
StevenHarperUKjames_w: create the diffs + interdiffs?16:00
james_wyeah16:00
james_winterdiffs aren't needed I don't think16:00
james_wbut you need to build source packages for each release and provide the .diff.gz for them16:01
sorengeser: Bored? There's an iptables merge with your name on it :)16:01
StevenHarperUKjames_w: ok back in a few mins :)16:01
sebnerpersia: nice session :) btw, /me hasn't seen norsetto for a while now, you?16:02
persiasebner, Thanks, and not recently.16:05
sebnerkk16:05
* DktrKranz kidnapped norsetto.. but please don't spread word16:07
sebnerlol16:07
gesersoren: on the contrary, too much work is waiting for me. But I will try to get the merge done, so the changes don't get lost again.16:10
sorengeser: No worries. I might do it myself if I can work up the motivation.16:10
karoogahi, I'm trying to do a new package of someone else's tar.gz.  In the past they have been responsive but now, not so responsive.  What options do I have if I am to make fixes (and rebundle that package) - do I use LP to host the code?16:12
Laneysoren: I can take a look. Is there anything special about it?16:14
gesersoren: perlipq FTBFS on AMD64 without a libipq.a build with -fPIC16:14
nxvlNCommander: around?16:14
sorenLaney: It's not straightforward, but certainly not rocket science either.16:15
sebnernxvl: you already updated ssmtp. cool! /me has to update his pbuilder, become a MOTU ASAP you will steal all my syncs and merges :P16:15
persiakarooga, I'd recommend just patching in the packaging initially.  If upstream remains unresponsive for a protracted period, or there is another reason to fork, you might do it, in which case it doesn't matter whether you use LP, sourceforge, google code, savannah, etc. : that's up to you.16:15
sorenLaney: The only thing I didn't manage to do in a snap was geser's PIC libraries.16:16
nxvlsebner: i asked you and you said that was ok16:16
nxvl:P16:16
sebnernxvl: but you are speed :P16:16
sebner+ on16:16
nxvl:D16:16
nxvlmerges are easy16:17
nxvlMoM does almost all for you16:17
nxvljust a little QA is needed16:17
karoogapersia:  thanks.  Define protracted period?  (1 week?) :-)16:17
persiaAt least a few months.  Maybe a year?16:17
sebnernxvl: pssssssstt. MoM is evil. watch out or persia slaps you :P16:17
Laneysoren: Will look tomorrow16:17
persiakarooga, Essentially, if you fork it, you're the new upstream, and unless the entire community surrounding the project joins you, it's just going to be unpleasant.16:18
sorenLaney: Coolness.16:18
gesersoren: without a libipq_pic.a this happens when one tries to build perlipq: http://buildd.debian.org/fetch.cgi?pkg=perlipq;ver=1.25-1.1;arch=amd64;stamp=121563122816:18
nxvlsebner: MoM is cool16:18
bobbojames_w: ping16:18
persiasebner, MoM isn't evil, it's just not human-equivalent automation.  Blindly using MoM tends to get people in trouble, but some people find some parts of it useful.16:18
sebnernxvl: if it get's the commenting function like DaD has ... :P16:18
james_whey bobbo16:19
sebnerpersia: hehe, I know. it was just a joke :)16:19
nxvlsebner: yeah, it actually has a hack already, but Keybuk still haven't look at it and include it16:19
LaneyWhy hasn't Debian adopted the PIC change?16:19
bobbojames_w: you requested some sponsoring request spam, so Bug #294200 ;)16:20
ubottuLaunchpad bug 294200 in mpd "Please merge mpd 0.13.2-3ubuntu1 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/29420016:20
sebnernxvl: kk =)16:20
karoogapersia: yeah, I don't think forking is necessary, it's really just minor fixes.  I'm just being over eager and impatient... Thanks.16:20
sebnerpersia: though, again bad boys used it. See http://thc.emanuele-gentili.com/utu/utu_jaunty.php  rank 21 :\16:21
james_wbobbo: has the diff been forwarded?16:21
bobbojames_w: writing the email as we speak :)16:22
james_wbobbo: cool16:22
james_wbobbo: if the Debian bug numbers are in the changelog then you don't make me ask :-)16:22
persiasebner, Indeed.  You'd be doing a service to figure out who, and reply to the -changes email to -motu discussing why it's important to check.16:23
bobbojames_w: ah, I didnt know we were supposed to put Debian bug number in changelogs, never seen that before :S16:23
james_wbobbo: some do, some don't. I advocate it.16:24
james_wbobbo: mentioning the fact in the bug report would be ok too16:24
geserLaney: I guess it wasn't forwarded to Debian yet (there is a won't fix bug for PIC version of libiptc only)16:24
Laneygeser: Right, I'll do that too then16:24
sebnerpersia: If I have time I'll try16:25
=== apachelogger is now known as Oxyhydrogen
=== gouki_ is now known as gouki
james_wbobbo: sorry, to disappoint you, but you Intrepid has been released :-)16:29
james_wbobbo: and no need to mention the maintainer change.16:29
james_wbobbo: if you could fish out bug numbers for the Ubuntu changes from earlier in the changelog and add them back that would be good as well.16:29
james_wbobbo: I think it's helpful to have rationale/bugs in the recent entry, rather than having to search for the original place the change was made.16:30
bobbojames_w: ok thanks! Now I have a debian bug number should I put that into the changelog?16:30
james_wbobbo: up to you16:31
james_wI'd like to see it, but where you put it is your choice16:31
bobbojames_w: ok :)16:31
james_wsistpoty sent a mail to the mailing list today suggesting that they go in the changelog16:31
=== rNhxYA_r is now known as LjL
StevenHarperUKjames_w: the source tar is teh same for the revisions its just the diff tahts needed16:35
james_windeed16:35
StevenHarperUKjames_w: ta16:35
bobbojames_w: http://pastebin.ubuntu.com/67974/plain/ . Fixed maintainer field, distribution, added Debian bug number. Couldnt add rationales/bug numbers for previous changes because none were given anywhere in the changelog.16:41
james_wouch16:42
james_wthanks16:42
james_wI'll finish reviewing and upload in a little while16:42
bobbojames_w: thanks :)16:43
StevenHarperUKjames_w: is that ok now (easycrypt one)16:43
james_wStevenHarperUK: you should have .1 at the end of the version numbers for Hardy and Intrepid16:45
goukiWhat happens when a software is not using any license, and the author doesn't reply when you ask for it's work to be licensed?16:45
lucasgouki: you lose16:45
StevenHarperUKjames_w: where at the end? or the end of teh version can you give example pls16:45
StevenHarperUK08.04.1?16:46
james_wStevenHarperUK: I gave you a wiki page with examples16:46
goukilucas, really? Just like that? Ohh well, was worth a try :)16:46
StevenHarperUKjames_w: right ill fix em16:47
nxvlgouki: yup16:48
nxvlgouki: it's merging time16:48
nxvlthe jackalope season is open16:48
nxvlgouki: go to merge.ubuntu.com16:50
nxvland find some package of your interest16:50
nxvlgouki: https://wiki.ubuntu.com/UbuntuDevelopment/Merging16:51
goukinxvl, OK16:52
StevenHarperUKjames_w: ok do they look correct now please (thanks again for persisting)16:54
Yasumotonxvl: I was about to ask that question, thanks :)16:54
james_wStevenHarperUK: yeah, I'd have to review diffs to be able to say more though16:55
nxvlYasumoto: :D16:56
StevenHarperUKjames_w: thanks16:56
james_wdoes anybody want to organise a Debian RC bugs day?16:58
nxvljames_w: o/17:00
james_wnxvl: wicked17:01
james_wI don't have a day off for a couple of weeks, and they might have all gone by then17:02
nxvljames_w: sunday!17:02
nxvljames_w: i will head the hotel at noon or early afernoon17:03
james_wnxvl: that's an idea17:03
bobbojames_w: fancy some more sponsoring request spam? Bug #294232 :P17:20
ubottuLaunchpad bug 294232 in seq24 "Please merge seq24 0.8.7-2 (universe) from Debian sid (main)" [Undecided,New] https://launchpad.net/bugs/29423217:20
james_wbobbo: I'll take that one, but I don't have much time this week.17:23
bobbojames_w: ok, all sponsoring is appreciated greatly :D17:23
james_walso it's better if you come to me with things that are more complicated than what looks to be a straightforward merge, that will show of your skills more17:23
=== santiago-pgsql is now known as Guest70218
=== Guest70218 is now known as santiago-ve
=== LucidFox_ is now known as LucidFox
RainCTargh, why doesn't any of the @lists.ubuntu.com lists set a proper Reply-to header? :/17:59
=== santiago-pgsql is now known as Guest17735
=== Guest17735 is now known as santiago-ve
ScottKnxvl: Are you using -v when you build your merge packages so the debian/changelog entries of the debian updates you're merging end up in .changes?18:04
ScottKRainCT: Get a proper MUA with "Reply to list" and you'll be fine.18:05
nxvlScottK: huh?18:05
nxvloh18:05
nxvlScottK: my fault18:05
ScottKnxvl: I noticed it on courier and ssmtp ...18:05
ScottKnxvl: Not a big deal.  We've all done it.18:06
nxvl:D18:06
ScottKJust wanted to make sure it didn't become a habit.18:06
nxvl:D18:06
nxvli haven't do merges in a while18:06
ScottKYep.  No one has.18:07
sebnerRainCT created such a nice "MOTU beginner's page". I hope it's also mentioned there :P18:08
=== Milyardo_ is now known as Milyardo
slytherinCan anyone please tell me if having word 'exec' before a command in the shell script is one of the bashisms?18:21
gesercheck "man dash" and also the check-bashism script18:24
slytheringeser: thanks, exec is valid in dash. Also checkbashisms does not complain about the script.18:32
=== Skiessi is now known as Skiessio
RainCTsebner: :)18:58
=== Oxyhydrogen is now known as apachelogger
NCommanderCool, I got my final MOTU +119:02
sebnerNCommander: CONGRATULATIONS! :D19:03
* pochu congrats NCommander 19:03
sebnerpochu: hihihi, first one. :P19:03
RainCTNCommander: gratz!19:03
NCommanderNow only if I was a member of ~motu19:03
laganeat19:03
* NCommander is shot repeatively19:03
lagacongrats :)19:03
pochusebner: I cut my hair last week ;)19:03
sebnerpochu: dito =)19:03
pochusebner: did you take pictures before and after? :)19:03
sebnerpochu: nope :P but I'm keen to see yours :P19:04
sebnerNCommander: yeah! know you are the official MOTU FTBFS guy! aweasome =)19:04
NCommanderI'm not an MOTU yet19:04
NCommanderStill need to wait for someone to add me to the gorup19:05
james_wdoes uehs exclusively show packages that are in Ubuntu but not Debian?19:05
sebnerNCommander: well, but you are a MOTU now. doesn't matter if you are in the group or just in 10 minutes19:05
NCommander\o/19:06
RainCTjames_w: afaik, it shows packages which are unmaintained (either not in Debian or owned by the Debian QA Group)19:06
james_wRainCT: ah, thanks19:07
NCommanderjdong, ping19:09
* NCommander looks at the build backlog19:11
NCommanderWow19:11
ScottKNCommander: That's pretty usual on the first autosync run.19:20
* NCommander nods19:20
NCommanderScottK, I just didn't realize how many packages get uploaded to Debian in six months19:20
ScottKThis one's actually kind of light due to the freeze.19:21
ScottKI does give you an idea of how much we leverage Debian.19:21
ScottKI've never seen "Building private build"19:21
ScottKI guess that's because they're doing security is Soyuz now.19:21
NCommanderScottK, I've seen it on occansion19:22
keesScottK: yeah, that's the SiS stuff.19:23
* ScottK hopes he knows what one of those is.19:24
ScottKNCommander: This is the time when you can really tell what's Main and what's Universe as Main stuff gets scored to build ahead of Universe.19:26
NCommanderyup19:27
sebnerScottK: when debian is released before DIF I suppose many packages get from experimental -> unstable -> ubuntu. Isn't there a risk that it breaks our stuff?19:28
ScottKsebner: There is always risk of getting stuff out of sync via autosync.  I don't think that appreciably changes it.19:29
ScottKThat's part of why it gets turned off as early as it does so we can find and fix such things.19:29
sebnerand sebner sync bot can continue syncing :)19:30
ScottKsebner: Don't go overboard.  Have a good reason to do it.19:30
sebnerScottK: why did I know that you react like that ... :P19:31
ScottKBecause it's the right answer.19:31
sebneryes and because I knew that you'll answer it ^^19:32
sebnerScottK is always killing my jokes :\19:32
* ScottK is grumpy today even compared to his usual self.19:32
sebnernp19:33
sebnerthe fun has just begun so let's be happy =)19:33
RainCTuhm.. gpg says that my secret key cannot be used, any idea?19:48
geserRainCT: what's the exact error message?19:51
RainCTgpg: skipped "rainct@ubuntu.com": la clau secreta és inusable19:52
RainCTgpg: [stdin]: clearsign failed: la clau secreta és inusable19:52
RainCTdebsign: gpg error occurred!  Aborting....19:52
RainCTwith LANG=C,     unusable secret key19:52
geserdoes using gpg still work for you?19:53
RainCTnot sure, I only use it for package signing :P19:54
RainCTlet me try unencripting something19:54
NCommanderRainCT, it sounds like your key went and corrupted itself :-/19:54
NCommandergeser, hey19:54
geserHi NCommander19:54
NCommandergeser, how goes it?19:54
geserNCommander: fine, just very busy the last days and I don't see an improvement in the near future19:55
RainCTbah, I have to find my backup then.. :(19:55
NCommandergeser, that sucks, but it could be worse19:55
geserRainCT: compare todays date and the expiry date of your key :)20:01
RainCTcrap!20:02
RainCTI guess it can't be unexpired? :P20:02
RainCTand why doesn't that damn gpg thing warn you some days before? :P20:03
geserI guess you should be able to update the expiry date20:03
RainCTuop, what is the expiry date for then? to scare you? :D20:04
geserhmm, perhaps you can't. I didn't find an option on a quick look to update it20:05
RainCTgeser: I can, just did it with seahorse :)20:05
geseryes, google helped me too: "expire" in the gpg --edit-key menu20:06
RainCTgeser: thanks :)20:07
=== ogra_ is now known as ogra
geserRainCT: don't forget to tell the Ubuntu keyserver that you changed the expiry date20:07
RainCTgeser: because I have no signature from any DD yet and the window is closed, else I'd have jumped out *g*20:08
geserI don't know if soyuz will accept your signature otherwise20:08
RainCTyep, I'm searching how to do this (seahorse can't because there's a bug in the code for it :P)20:08
gesergpg --send-key rainct@ubuntu.com20:09
geseror use your keyid instead of the email address20:09
ajmitchhi20:10
geserHi ajmitch20:10
RainCTajmitch: hey20:10
iulianRainCT: You might want to use the keyserver option too.20:12
iuliangeser: I thought that you must specify the keyserver first.20:12
iuliankeyserver.ubuntu.com20:13
geseriulian: unless you have one set in your .gnupg/gpg.conf20:13
tbielawahellooo everybody20:13
iuliangeser: Ah, right.20:13
RainCTiulian, geser: done, thanks20:14
geserRainCT: don't forget to put a sticky note on your monitor to remind you when your key expires again :)20:14
RainCTgeser: I won't forget :)20:15
ajmitchyou say that now20:15
iulianOr set it to never expire?20:15
* iulian agrees with ajmitch.20:15
* RainCT goes to do homework where pbuilder slowly downloads bdeps20:16
=== santiago-ve is now known as Guest34739
iulianRainCT: I said exactly the same thing when I generated my second key. After a couple of weeks when I tried to sign a document using that key, I couldn't remember my password.20:17
iulianFortunately, after ~50 combinations I entered the correct one and recovered my key ;)20:18
* NCommander uses a password but doesn't expire his keys20:18
RainCTlol20:18
* ajmitch wonders why that RC bug day has to be on sunday20:18
iulianRainCT: Well, I wrote a small program which gives me the passwords in a nice way. And yes, that file is in a safe place, encrypted.20:19
tbielawalol20:20
RainCTiulian: and if you forget the password to decrypt it? :D20:21
=== Guest34739 is now known as santiago-ve
iulianYeah, it sucks when you don't remember something which you need it in a few moments.20:22
iulianRainCT: Impossible. ;)20:22
* iulian goes back to hunt some merges.20:24
ScottKiulian: I'd rather you hunted patches to send to Debian out of those merges.20:25
tbielawaDoes anyone have time to do a REVU for me? http://revu.ubuntuwire.com/details.py?package=lucidlife it would be much appreciated.20:25
=== dfiloni is now known as devfil
iulianScottK: Sure, I'm looking at some of them right now. So, we send the patches to Debian, wait until the patches are included and then sync?20:32
ScottKiulian: That's my preferred workflow.  If it gets close to DIF and they haven't updated, merge then.20:32
iulianCool, thanks.20:33
ScottKiulian: If there's a case where you know we have changes that won't go in Debian, then you should still send them the stuff that's relevant, but there's no real need to wait to do the merge.20:34
iulianScottK: OK, that's what I thought.20:37
pochudevfil: do you want to take the wx2.6 merge for me? :)20:39
devfilpochu: there is a wx2.6 merge? ...20:39
devfilok :)20:40
devfilthanks20:40
pochudevfil: thanks to you! :) I've assigned it to you in a comment in http://dad.dunnewind.net/universe.php20:41
pochudevfil: this needs to be merged: http://packages.qa.debian.org/w/wxwidgets2.6/news/20080909T143211Z.html20:41
YasumotoThis is a ridiculous question, but where's the fedora bugzilla?20:41
Yasumotomy google skills are terrible right now, I guess.. :/20:42
YasumotoDoes redhat use https://bugzilla.redhat.com/ for both RHEL and fedora?20:43
pochuI think so20:43
iulianYes, IIRC.20:44
Yasumotothanks guys. I found the fedora wiki, and it looks like bugzilla.redhat.com is it: http://fedoraproject.org/wiki/Bugzilla20:44
pochuLaney: you've got to do the fet merge ;)20:46
pochunhandler: and the mmorph merge is yours!20:46
pochuLaney, nhandler: feel free to ping me if you want sponsorship for those20:47
directhexhm, looking at planet, it seems gnome-do is popular20:54
stefanlsdcan debian still fix stuff in unstable?20:56
ScottKstefanlsd: Yes.  It just doesn't get into Lenny without approvals (which are very hard to get).20:57
stefanlsdScottK: kk. cause we have time still. Some of the merge stuff i'm rather forwarding and getting them to fix so we can just sync.20:57
ScottKstefanlsd: That's the preferred approach.20:57
directhexbug fixes will get into lenny. UVF is pretty strict20:58
james_wany REVU admins around?20:58
james_wjelmer uploaded a new version of ptabtools yesterday, but it hasn't shown up on REVU, could someone see if there is something wrong?20:58
stefanlsdanyone having issues with the requestsync script?20:58
pochustefanlsd: we can sync from experimental anyway20:59
pochuin case your changes are uploaded there20:59
ScottKdirecthex: Only for RC bugs.20:59
james_wah, don't worry, he worked it out, he uploaded binaries, not a source package21:00
=== Kmos_ is now known as Kmos
ajmitchjames_w: there was an issue with REVU yesterday as well, which meant that packages weren't being accepted for awhile21:01
pochuScottK: non-rc are also approved for lenny sometimes21:01
james_wah, might have hit that as well, thanks ajmitch21:01
ScottKpochu: True, but it's definitely the exception.21:02
ScottKtbielawa: You assert that part of your package is public domain.  How do you know that?21:11
tbielawaScottK, you are referring to "pattern archive in patterns/..."?21:13
ScottKYes21:13
tbielawaone moment please.21:14
ScottKtbielawa: I have to run out, but consider that copyright law in many contries doesn't have the concept of public domain.21:14
tbielawaScottK, then I should also provide a reference URL which declares their public domain status, or perhaps including the text of the american public domain definition would be better suitable?21:15
tbielawa(also, README from upstream tarball is where they are declared as public domain)21:16
ScottKtbielawa: "Public domain" works can be problematic is some respects.  If they created it then it'd be simplest if they also licensed it under some really broad license like the wtfpl.21:18
tbielawaScottK, would you recommend I attempt to contact the public domain author?21:20
lagathe wtfpl sounds neat21:21
tbielawaI like that license21:26
pochui can has jaunty ppa pliz? :)21:26
YasumotoSo on http://dad.dunnewind.net/universe.php, anything that has a /!\ needs to be looked at by a human, right?21:27
LutinYasumoto: everything needs to. the ones marked /!\ are broken, and consequently the output of DaD should not be taken into account when merging21:35
=== Skiessio is now known as Skoiessio
=== Skoiessio is now known as Skoioessio
=== Skoioessio is now known as Skioooessoio
=== Skioooessoio is now known as Skiessi
logari81hi, I try to upload for first time something on my ppa and I get the following error21:41
logari81Unable to find distroseries: unstable21:41
logari81but I see packages in ppa's of other members, built against "unstable", am I missing something?21:41
=== RAOF_ is now known as RAOF
YasumotoLutin: ah, cool. thanks21:45
ScottKYasumoto: They ALL need to be looked at by a human.21:53
YasumotoScottK: yeah, I'm looking at the outstanding merges for universe (300!). reading the UbuntuDevelopment/Merging wiki page now21:58
ScottKOK.21:58
ajmitchdown to 300 already?21:59
cody-somervilleajmitch, Debian has been in a freeze22:00
Yasumotoyeah, according to http://merges.ubuntu.com/universe.html22:00
ajmitchcody-somerville: yes I know22:00
directhexjaunty will suffer unless lenny releases pronto. close an RC bug today!22:02
ajmitchfew of the remaining RC bugs in debian will be just quick fixes22:05
* ScottK wraps his head around using pbuilder to build the new pbuilder ...22:08
pochulogari81: try in #launchpad22:09
logari81pochu: thnx I ll try, but I think I ll build my packages explicitly against intrepid and/or jaunty22:11
ScottKlogari81: PPA is run by Launchpad.  You need to ask there.22:13
NCommanderScottK, your pbuildering pbuilder?22:17
ScottKYep.22:17
ScottKAnd then I'm doing it again to test the result of the first one.22:17
NCommanderScottK, I ... uh ...22:20
* NCommander feels confused22:20
ScottKI need to know if the new pbuilder works for the backport, so I need to install it and build something for a test ...22:20
ajmitchNCommander: I'm surprised22:20
=== fta_ is now known as fta
ScottKBTW, with debchroot from Jaunty backported to Intrepid it's no trouble to make a new pbuilder chroot for Jaunty.22:22
ScottKNot that I'd have expected anything else.22:23
sebnerScottK: debchroot = debootstrap?22:28
ScottKsebner: Yes.  My typo.  Sorry.22:29
sebnerScottK: np, thx for the hint =)22:29
ajmitchor you just put in another symlink for jaunty22:31
ScottKThat too.22:32
sebnerScottK: does autosync already runs?22:32
ScottKsebner: Yes.22:32
superm1ScottK, i seem to remember you were tracking some bug where hotkeys are broke in kde 4, like vol+/vol- and play/pause etc?  Do you have that handy?22:33
tuxmaniacwhere can I find some information on rising sru for intrepid?22:33
sebnerScottK: cool thx. so /me has to upgrade to jaunty =)22:33
ScottKsebner: Look how many are in queue https://launchpad.net/+builds22:33
ScottKsuperm1: jdong was working on that.22:33
* ScottK looks22:33
ScottKsuperm1: Bug #26724522:33
ubottuLaunchpad bug 267245 in kdemultimedia "Keyboard volume keys only change PCM volume" [Low,In progress] https://launchpad.net/bugs/26724522:33
superm1great thanks22:33
ScottKIIRC he was still trying to sort out brightness keys.22:34
wasabiHey... trying to get a cdbs package to work and something is eluding me.  Using makebuilddir/source-package-name:: to do some stuff before configure. but it's never being run.22:34
tuxmaniacok got it thans22:34
wasabiAlso tried to use a binary package name.22:34
superm1I just saw some hal-info bug filed which I was pretty confident was actually a KDE bug, there's an upstream tracker for it too, so i'll add that22:35
jdongScottK: talked to Riddell regarding the brightness keys; fixing them will require work on qt4-x11 to bring out those hotkeys.22:35
sebnerScottK: yep, quite busy our mighty machines =)22:35
jdongsuperm1 / ScottK: Base problem is qt4 doesn't support the XF86MonBrightness{Up,Down} KeySyms22:35
ScottKjdong: Sounds like something worth doing in Jaunty then.22:35
jdongScottK: agreed.22:35
jdongsuperm1: the current Kubuntu workaround is basically xmodmapping brightness keycodes to various "unused"/esoteric keys, in particular XF86Launch4/XF86Launch5 which QT does understand22:36
jdongsuperm1: that, though, breaks the brightness keys in GNOME :)22:36
superm1jdong, gosh how silly22:37
jdongso yeah, I think this is something to work on in Jaunty, not Intrepid.22:37
jdongit's quite a hairy mess and I don't want to cause regressions for Kubuntu users who already have working brightness keys22:37
ScottKYes.  Please.22:37
superm1i think crack for jaunty is more fun anyway, get adding :)22:38
=== LcrxqYLe is now known as LjL
sebnerScottK: btw, another question. if some of my major sponsors are in the MC I don't need to CC them right?22:42
ScottKsebner: Dunno.22:42
sebner^^22:42
ScottKPersonally, I'd cc everyone.  I don't think there's a rule though.22:43
NCommandersebner, you applying for MOTU?22:44
* sebner hides22:44
sebnerScottK: I just thought recieving 2 times the same email isn't that fun22:45
nhandlersebner: If a person is CC'd on a mailing list message, the list will not send them another copy iirc22:46
TheMusonhandler: I think it depends on list and user settings.22:48
ScottKnhandler: That's not the default for mailman.22:48
nhandlerScottK: I thought it was. I know I don't get duplicate messages if I am CC'd22:48
ScottKIt's a config option.  Dunno how the MC list is set.22:48
RainCTjames_w: https://wiki.ubuntu.com/MOTU/Packages/REVU/JauntyCleanu22:48
RainCT* https://wiki.ubuntu.com/MOTU/Packages/REVU/JauntyCleanupMessage22:48
RainCTany improvements welcome ^22:49
ScottKRainCT: I have a REVU feature request.22:49
ajmitchScottK: a 'nuke all' button?22:49
ScottKRainCT: It'd be nice to have something to click on that would run grep -ir copyright * on the source and output the result.22:50
* sebner is happy that he started a discussion about mail settings ^^ 22:50
ScottKajmitch: That too.22:50
logari81I got my questions about ppa answered, but now I need some feedback about my first packaging attempt. Could anyone take a look here https://launchpad.net/~logari81/+archive/ and give me feedback?22:50
ScottKajmitch: My equivalent is generally "Don't look at REVU".22:50
james_wRainCT: nice job, I think that strikes a good balance.22:51
james_wRainCT: thank you22:51
sebnerNCommander: to be honest I wanted to wait some time after I saw your application ;)22:51
ScottKRainCT: The reason I ask is that I often end up doing reviews just for licensing stuff and that's save me bothering with some downloading.22:52
RainCTScottK: That's an interesting proposal. Perhaps it could be written to a file, like with lintian. What exact command would you suggest?  "grep -ir copyright * | tee ...; licensecheck * | tee -a ..." ?22:52
ScottKRainCT: I don't generally use licensecheck so I'm not able to say about that.22:53
james_wlicensecheck has a copyright flag22:53
ScottKMaybe that's all we need then.22:53
RainCTjames_w: (re the message) Thanks :). Anything which could be improved?22:54
james_w"licensecheck -r --copyright . " I think22:54
james_wis the best way to call it22:54
RainCTthinking about it again, perhaps dinamically generated is indeed better.. else siretart may kill me for filling up the disk :D22:54
RainCTalright, let me try if I can get it ready right now22:54
james_wRainCT: I can't think of anything, I think that is a good message for this point.22:55
nhandlerRainCT: I have another suggestion. Could you please grep the changelog file for (LP: #NNNNNN), and either display a link to the needs-packaging bug or display a warning stating that the package does not close a needs-packaging bug on LP?22:56
RainCTnhandler: yep, that's on my TODO, too22:56
nhandlerAwesome RainCT22:57
ScottKnhandler: Why do we care if it closes the bug?  The bug won't close because of that.23:00
nhandlerbobbo: You should really contact the last uploader of a package before doing a merge (especially this early in the cycle). I was already working on the seq24 merge23:00
Yasumotowow, I like how I submitted a bug report upstream for clisp, and I just realized the upstream guy already pretty much shot down the bug. whoops..23:00
nhandlerScottK: It makes it easier to check that it does in fact close a needs-packaging bug (which is a requirement), and it also makes it easier to see what discussion (if any) has occured regarding the package23:01
ScottKnhandler: I guess I don't see the point in the requirement.23:01
nhandlerScottK: Well, I'm not the one who made that requirement ;)23:01
bobbonhandler: sorry, wont do it again!23:04
nhandlerNo problem bobbo. I probably should have opened a bug report when I started working on it23:05
RoAkSoAxis merging for jaunty open?23:05
sebnerRoAkSoAx: yep23:06
RoAkSoAxright on!23:07
RAOFIn case anyone's interested, you're welcome to do the miro merge.  Don't think I've got a maintainer-lock on it! :P23:07
YasumotoSpeaking of which, what's the best way to see if a maintainer's working on a package? ping them on irc?23:08
RAOFCheck the bug page first, and DnD's comment section.23:08
YasumotoRAOF: good idea, thanks23:09
RainCTScottK: I think this will be discussed Friday 14th (there's "wnpp package for Ubuntu" on the schedule)23:09
RAOFThen a ping on IRC; if you can't get them on IRC then what you should do next depends on the stage of development, the history of uploads (I'm likely to be much more interested in a merge if, say, I'm the Debian maintainer too, or I've consistently uploaded the package).23:10
YasumotoRAOF: yeah, it's probably something you're quite familiar with, and it's at the top of your list23:13
RAOFYasumoto: What? Miro?  I'm familiar with it, but you're absolutely welcome to take it if you wish.23:13
Yasumotohaha :)23:14
RAOFThe merge should be reasonably simple.23:14
YasumotoAlright, sounds great to me, I'll grab it now23:14
RAOFMy test-build ability will be somewhat limited for a while by the fact that my something in my buildbox decided to catch fire this morning.23:15
james_wRainCT: have you considered the timing of that mail with the REVU day?23:18
YasumotoRAOF: sounds brutal.. :(23:19
RAOFIt'll be the power supply or something.23:19
RainCTjames_w: Not sure what you mean. "that mail" -> the mail I'll send to announce it?23:20
james_wRainCT: sorry, I meant moving the packages to "Needs Work"23:21
james_wRainCT: if you do it today then there will be people who will miss a REVU day23:21
james_wif you do it after then it doesn't help the reviewers on Friday23:22
james_wdo you know how often the REVU days will be?23:22
RainCTjames_w: weekly, every Friday23:22
james_wah, cool23:22
james_wno problem then23:22
wasabiAny cdbs people here? I am having trouble getting makebuilddir/ to work.23:23
NCommanderRainCT, stupid question. I got three +1s on my MOTU application, but I'm not in ~motu yet. Can I still +1 on REVU apps?23:23
wasabiAs in, it's simply not being called, and I can't figure out why.23:23
RainCTNCommander: I can't answer to that :)23:23
NCommanderRainCT, your the REVU coordinate ;-)23:23
NCommander*cooridinator23:23
james_wdoes anybody want to review http://revu.ubuntuwire.com/details.py?package=ptabtools ?23:24
james_wI haven't advocated yet, but I plan to once I get a build environment sorted out23:24
NCommanderI will23:24
NCommanderjames_w, the copyright file is incomplete23:26
james_wwhy?23:26
NCommanderIt doesn't list who holds the copyright23:26
james_wah, downloaded from?23:26
james_wCopyright (C) 2005-2008 Jelmer Vernooij <jelmer@samba.org>23:27
NCommanderNo, the entire line is blank23:27
NCommanderNo23:27
NCommandergo one down23:27
NCommanderOh23:27
NCommanderwait23:27
NCommanderThe upstream is the packager?23:27
james_wyeah23:27
james_wI don't see a problem with lumping it all in together23:27
james_wbut I'm not an archive admin23:28
NCommanderjames_w, ok, fair enough23:28
NCommanderWhy does it use *.links?23:28
james_wbecause the Makefile is incomplete I believe23:28
* NCommander would normally file a bug w/ the upstream on that ;-)23:29
NCommanderThe dirs files can be removed, they are only needed if make install will not create them23:30
james_wagain, the Makefile :-)23:32
NCommandermake install doesn't work?23:32
NCommanderARGH23:32
* NCommander thunks his head23:32
NCommanderOk23:32
NCommanderI don't mind +1ing the package if the resulting binaries are lintian clean and it builds in a jaunty pbuilder chroot23:33
james_wno, that does work23:33
james_wI'll mention it to him23:33
NCommanderIt FTBFS in pbuilder23:33
james_wNCommander: ok, thanks. Please drop the error in a comment and I'll work with him to get a working package.23:34
copproNCommander: http://revu.ubuntuwire.com/details.py?package=metakit? I haven't tried it on a jaunty pbuilder yet, I'm making the chroot now23:35
NCommanderWant me to build it?23:35
copproreview it, if you would be so kind :)23:38
NCommanderI can already see a critical issue23:40
NCommander"0ubuntu2"23:40
copproyeah, I know23:40
copproI'm not sure about REVU's versioning scheme; and it won't let me update without increasing the version23:40
NCommanderCare to explain?23:40
NCommandercoppro, revu will accept anything and it will clobber23:40
NCommanderIs this package from Debian?23:41
copproit just straight clobbers, wihtout anything so much as "new upload?"23:41
NCommander(why are there README.Debian files)23:41
copprono, it's not Debian23:41
copprooh, what should I be using then?23:41
NCommandercoppro, every upload is perserved23:41
copproNCommander: well, last time I tried, it didn't work23:41
NCommanderREADME.Ubuntu, unless you intend to submit this to Debian23:41
copproand someone said to bump the version23:41
copproNCommander: ok, I'll change that23:41
NCommanderWHoever said that probably thought you meant PPAs23:41
copprooh23:42
copprowell it didn't work23:43
coppromy upload never showed up23:43
RainCTNCommander: README.Ubuntu? o.O23:43
NCommanderREVU last night was having issues23:43
copprowas a couple of days ago23:43
NCommanderRainCT, as an aside, next time you edit a script, try it afterwards. GPG validation was broken because a permission got screwed up23:43
NCommander:-)23:43
RainCToh ok, I was wondering why there's that much rejected stuff lying around :P23:44
RainCTNCommander: which file was wrong?23:44
NCommanderYou managed to get GPG trying to write scratch files in /root/.gnupg23:45
NCommanderWhich didn't exist23:45
NCommanderRainCT, anyway, I thought on Ubuntu specific packaging, the README files should be README.Ubuntu23:45
NCommander(so if the package ever exists in Debian and then are merged, both are available)23:45
RainCTthere should only be one if they are merged :P23:46
NCommanderHaving a README.Debian file seems wrong on a 0ubuntuX package23:46
copprowell, I've made the change23:47
james_wI don't see a need to break convention23:47
coppro*shrug*23:47
james_wyes, it makes a sense, but why break the association of "information specific to a .deb" => "README.Debian"?23:48
* RainCT agrees with james_w 23:48
RainCTScottK: http://revu.ubuntuwire.com/report.py/legal?upid=3818 :)23:52
james_wRainCT: wow, nice work :-)23:53
RainCTjames_w: was actually quite easy to add :)23:54
james_wdon't say that!23:54
* NCommander gives up on the README.Ubuntu23:54
csilkIf an app came in a zip file can I just unzip, create tar.gz of source, create .orig.tar.gz then get rid of the zip?23:55
RainCTNCommander: do you have a double personality which fighted against yourself on this? *g*23:55
csilkmaking a note in the changelog of course23:55
RainCTcsilk: if that's the only option, yes. but do that automatically using a get-orig-source rule23:55
csilkRainCT, k thanks23:55
RainCT(sponsors are supposed to generate the tarball themselves using get-orig-source before updating, to ensure that the tarball wasn't modificated)23:56
RainCT(not sure if anyone does this, but well, get-orig-source rules are nice nevertheless :))23:57
csilkusing the get-orig-source rule wasn't mentioned in holbachs video tutorials23:58
RainCTcsilk: it's just an additional target in debian/rules, which does whatever you want23:58
csilkI'll read up on how that works23:59

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