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

st33medWell, I am looking to help00:02
st33medLaney, hmm, what about this bug00:14
st33medbug 34397900:14
ubottuLaunchpad bug 343979 in evolution-rss "needs update for jaunty" [Undecided,New] https://launchpad.net/bugs/34397900:14
st33medHelp me learn with that?00:14
nhandlerst33med: That bug is a duplicate00:36
st33mednhandler, yeah, thanks for the update00:37
=== jrib1 is now known as jrib
=== rgreening_ is now known as rgreening
ryanakcaIf I only have one binary package (produced by the source package), and it has ``Architecture: all'', do I need Build-Depends? Or can they all go in Build-Depends-Indep?01:09
Ryan52ryanakca: you need Build-Depends for the things needed for the clean target.01:18
Ryan52so probably cdbs, debhelper, &c.01:18
ryanakcaRyan52: So, http://pastebin.com/f2f604696 is fine?01:20
Ryan52maybe? :P01:24
Ryan52looks okay. I dunno about cmake or python packaging, tho.01:24
ryanakcaOk, thanks01:25
st33medSo uh...01:28
st33medI am a new-ish Ubuntu Member looking to help in Python areas for Jaunty01:29
=== simon__ is now known as frostburn2
TomJaegerCould someone upload the updated thinkfinger package attached to bug #311732 ?03:06
ubottuLaunchpad bug 311732 in linux "2.6.28-4 breaks thinkfinger" [Undecided,Fix released] https://launchpad.net/bugs/31173203:06
TomJaegerThinkfinger doesn't currently work on jaunty.  Thank you.03:06
stgraberTomJaeger: is there a way you can provide a debdiff with only the needed changes ? the .diff.gz I saw on that bug report seems huge03:25
stgraberstgraber@sahal:~/code/thinkfinger$ debdiff thinkfinger_0.3+r118-0ubuntu3.dsc thinkfinger_0.3+r118-0ubuntu4.dsc | wc -l03:26
stgraber743803:27
stgraberTomJaeger: that's a lot more than it should for a bugfix03:27
TomJaegerstgraber, The version that's currently in ubuntu contains all sorts of junk files that have been deleted03:27
TomJaegerCheck out the diffstat03:29
TomJaeger 61 files changed, 21 insertions(+), 7123 deletions(-)03:29
TomJaegerAs far as I understand it, a .debdiff can't represent deletion of files, that's why I posted the .diff.gz03:31
stgraberWhat's the package like in Debian ? our general goal is to avoid unnecessary delta with Debian as it'll only make it harder for the next release (having to merge the changes) ?03:32
TomJaegerI think we already diverged.  Debian's not going to have the fixes, though, since we're on a newer kernel.03:35
TomJaegerstgraber, http://packages.debian.org/changelogs/pool/main/t/thinkfinger/thinkfinger_0.3+rev118.2-4/changelog03:37
ScottKTomJaeger: At this point in the release cycle 'cleaning up the package' is not something we want.  We want to limit changes to minimally invasive ways to fix problems.03:55
TomJaegerScottK, these are .svn files and leftover dependencies files, they won't affect the package in any way.03:58
ScottKThey don't particulalry hurt to leave them either.03:59
TomJaegerIt'd probably take me at least 10 minutes to put them all back in and prepare a new .debdiff04:00
* ScottK is just off to bed, so not in a sponsoring mood. Take my advice for what you will.04:00
TomJaegerI really don't have time for this kind of busywork right now.  So it's either the package I posted, or someone else will have to put the junk back in, or we won't have a working thinkfinger package in jaunty.04:04
fabrice_sp__TomJaeger, why don't just just redownload he original package, apply your diff, and reget the debdiff?04:06
fabrice_sp__debdiff would ignore deletion04:06
=== fabrice_sp__ is now known as fabrice_sp
TomJaegerNo, the debdiff will represent deletion as removing the content of the files.04:08
TomJaegerAnyway, my standpoint is that my time is too valuable for these kind of antics.04:09
rgreeningTomJaeger: I dont see this as antics. sry you feel that way04:10
rgreeningduring freeze, we need to minomize changes.04:11
rgreeningminimize even04:11
rgreeningit's more of a 'cover your butt' scenario :P04:11
TomJaegerSince the deleted files don't affect the package build in any way, there's no change04:11
ScottKTomJaeger: And no file deletion ever had an inadvertent effect?04:12
rgreeningAnd I agree thazt that clean-up should get done after freeze04:12
rgreeningIt's easier to 'oops' when you have 7000 lines to review in changes.04:13
* ScottK decides to quit arguing and play killbots instead.04:13
TomJaegerScottK, the deletion of .svn directories? please04:14
TomJaegerrgreening, geany is really nice to review diffs04:15
rgreeningTomJaeger, in the time you spent arguing over this, you could have made the changes requested by the sponsor.04:15
rgreening:)04:15
rgreeningjust to be facitious :P04:15
* rgreening ducks04:15
TomJaegerthe thing is, I've already made up my mind.  I'm not going to make the changes04:16
rgreeningoh well....04:16
TomJaegerI'd argue that it's much more likely that I'd screw up re-adding those files than that the deletion causes a regression.04:17
wgrantWe need to ensure that diffs are easy to review.04:20
wgrantWe really do not want to break things at this point.04:20
TomJaegerthere are easy to review for anyone who's ever heard of diffstat04:20
TomJaegerthinkfinger is _completely broken_ at this point anyway04:20
wgrantEven if I use diffstat, I have to work out which files are actually entirely gone and which aren't and blah blah blah.04:21
wgrantWith a proper diff, I can just glance at it and see that it's not doing anything stupid.04:21
rgreeningTomJaeger: wheres your debdiff and bug report04:22
TomJaegerbug #31173204:22
ubottuLaunchpad bug 311732 in linux "2.6.28-4 breaks thinkfinger" [Undecided,Fix released] https://launchpad.net/bugs/31173204:22
rgreeninghmm.. reading this looks like simply getting a clean package via apt-get source and grabbing the patch from the kernel bug is easy enough.04:24
TomJaegerThere's quite a few fixes in that package, not just that one that the bug is about04:25
rgreeningoh, then you probably should file a seperate bug report asking for the update and all your changelog entries for every single change will need to be documented to get accepted.04:26
TomJaegerThere are bugs filed for all of them04:27
rgreeningHaving accurate changelog entries is a critical part of updating any package04:27
TomJaegerDid you even look at the changelog?04:27
TomJaegercomment #1904:28
=== Andre_Gondim is now known as Andre_Gondim-afk
bdrungScottK: https://bugs.launchpad.net/bugs/34043504:30
ubottuUbuntu bug 340435 in adblock-plus "[needs-update] adblock-plus to 1.0.1 in Jaunty" [Undecided,New]04:31
rgreeningTomJaeger: yes I read it. And yes I saw the changelog entry and my comment stands. You don't meantion zapping the changelog entries which differs from upstream.04:32
rgreeningfor one04:32
TomJaegerzapping the changelog entries?04:32
rgreeninganyway, a debdiff would be nice.04:32
ScottKbdrung: It's not bug fix only.04:35
ScottKasac: I thought we agreed you weren't going to shove unsupported Firefox versions in Universe anymore?04:35
ScottKasac: Does mozillateam intend to support Firefox-3.1 though the life of Jaunty?04:35
TomJaegerrgreening, posted a .debdiff04:36
rgreeningTomJaeger: Let me have a peek04:36
fabrice_spScottK, did you had time to have a look at Bug #34385104:36
ubottuLaunchpad bug 343851 in setools "FTBFS randomly because of a race condition in creating debian/stamp/binary" [Undecided,Confirmed] https://launchpad.net/bugs/34385104:36
fabrice_sp?04:36
ScottKfabrice_sp: I did.  I'm uncertain how to tell if you fixed the FTBFS since the previous version works in a PPA.04:36
ScottKfabrice_sp: I'm considering maybe this is a packagebinarymangler bug.04:37
fabrice_spScottK, I far I understand this package, in each binary, it's trying to check and create debian/stamp/binary if not exist. I could happen that it enters at the same time in the condition and try to create it04:38
fabrice_spby moving the creation outside of the binaries target, it should work04:38
ScottKOK.   I didn't have more to do than toss it at my PPA.04:38
ScottKhave time to do more than ...04:38
fabrice_spI think build machines are too fast :-)04:39
fabrice_spare the ppa ones slower?04:39
bdrungScottK: updated bug title. something missing?04:41
rgreeningTomJaeger: ok, so you definately have something funky in the diff. At one point the thinkfinger.orig is the first entry and sometimes the second, which leads me to believe you cat'd these together. not such a big deal, but does make it easy for you to remove the .svn parts which all apear at the beginning.04:48
rgreening:)04:48
rgreeningTomJaeger: and it appears you made changes directly in the source rather than via patching04:49
TomJaegerThe debdiff was created using the debdiff command from the two .dsc files04:50
XiXaQis there any way to get a list of completely new packages in one distro from another? That is, packages that aren't just new versions, but that haven't been in the repos before at all? And packages that have been promoted or demoted?04:51
rgreeningTomJaeger: and they should still yield whether a patch was used. I don't see that.04:51
rgreeningunless I missed something...04:51
TomJaegerI figured changing the source directly is less intrusive than adding a patch system04:51
rgreeningTomJaeger: completely the opposite04:52
rgreeningfor us04:52
=== sdh_ is now known as sdh
TomJaegerPatch systems are kludges anyway04:52
rgreeningAs a rule of thumb, never change the source. Always generate a patch. submit the debdiff . pass the patch upstream.04:52
rgreeningTomJaeger: if you are interested in learning the ropes, and how we work, there are some processes we have to follow.04:53
rgreeningand patch systems are not kludges.04:53
TomJaegerThey are. Horrible kludges.04:53
TomJaegerPITA to deal with.04:54
rgreeningdo I sense any undue hostilities? cause, I am quite willing to walk away...04:54
rgreeningrather than help04:54
TomJaegerPut the source package under proper version control04:54
TomJaegerWell, I've wasted a lot of time dealing with patch systems.04:55
rgreeningTomJaeger: we don't own the source, and therefore we patch and pass upstream. if/when upstream accepts the patch, we update the package and remove the patch. this keeps things much cleaner and much easier to modify or remove a patch when required.04:55
rgreeningTell me, how easy is it to back out your change? with a patch system, I comment out a single entry in a file and let it rebuild. done.04:56
TomJaegerWell, a .diff.gz is a patch, too04:56
rgreeningTomJaeger: no, not in the strict sense we are looking for here. Patches goe in the debian/patches dir and are part of a patch system like quilt, dpatch, etc.04:57
TomJaegerIt's as easy as removing a .orig and a .rej file after running uupdate04:57
rgreeningAnyway, if you wish to have patches/diffs reviewed and uploaded, it will go a lot easier if you follow the ubuntu packaging guide.04:57
rgreeningmaking life easy for your uploader/sponsor is in your and the packages best interest.04:58
rgreeningbut I digress... its late here... and Im much too tired...04:59
TomJaegerAt this point, I'm really fine with keeping the package in my PPA.04:59
fabrice_spWoah! We still have 128 packages that cannot be installed, 48 of which are from python (that's what apt-cache -i unmet tell me...).04:59
fabrice_spand Beta is in 3 days? That will be hot!05:00
punkrockguy318Can someone try to get the latest version of my NES emulator into intrpeid?  http://fceux.com .  It version 2 of fceu and gfceu, but it does not replace them , since its called (g)fceux.  it's works a lot more nicely with ubuntu 8.10/9.04 and it would be a shame to see only the ancient 0.98 release in the archives05:02
TomJaegerrgreening, again, I don't have the time for this busywork.  It's late here, too and I still have 3 hours of work ahead of me.  If you want changes to the package to be versioned, I would suggest to adopt a solution centered around a version control system.  Patch systems are extremely difficult to work with when you're tracking upstream changes.05:11
rgreeningTomJaeger: it's not me, its policy. I think you really need to read up on how packages are done in debian and Ubuntu05:13
TomJaegerI don't seem to remember that patch systems are a hard requirement.05:13
TomJaegerAs a matter of fact, I've gotten packages in that didn't use a patch system...05:14
rgreeningTomJaeger: If there's no good reason to not use a patch system, then we use it. We avoid patching the source directly.05:14
rgreeningif the source has issues and MUST be modified directly, then this is a case-by-case review. in this case, It is not warranted.05:15
rgreeningand wehat happens for the next person who wishes to fix? What happens when a source update occurs and the change disappears...05:16
TomJaegerWhat's troubling me here is that there is a lack of a sense how things should be properly done05:16
rgreeningthats what patch systems are useful..05:16
rgreeningTomJaeger: I think you are really failing to understand.05:16
TomJaegerWhat don't I understand?05:16
TomJaegerThere's a tradeoff here: Patch systems are a considerable amount of work to set up and maintain, and the benefits are not worth it in this case, at least not for me.05:18
rgreeningTomJaeger: If it was my source tree, then it would be in bzr. This is an upstreams source, and presumably its in an rcs of some kind. a proper patch should be provided to them, and they will updates thier rcs. we maintain only small diffs/patches and re-sync with debian and upstream at various times.05:18
rgreeningconsiderable amount of work? not at all.05:18
TomJaegerSmall patches, huh?  This is the reason why everybody runs autoreconf on the source tree and then sticks the result into the .diff.gz?05:19
rgreeningTomJaeger: that shouldn't occur (on reasonably new packages)05:19
rgreeningTomJaeger: I take it you've never used quilt.05:20
rgreeningquilt is a dream.05:21
wgrantWhich is why the new source format is based on it.05:21
rgreeningTomJaeger: https://wiki.kubuntu.org/Kubuntu/Ninjas/QuiltMagic05:22
TomJaegerI've used quilt, and I can tell you, it just doesn't interoperate with git very well.05:22
rgreeningI can see this discussion is circular, and Im feeling quite dizzy. so adieu05:23
wgrantTomJaeger: Is the thinkfinger packaging in a VCS?05:23
=== fabrice_sp_ is now known as fabrice_sp
TomJaegerI do know what I'm talking about, I've developed all the patches that I got into the X Server before 1.6 came using a git archive with a debian/ directory in it.  It was not very pleasant, but it beats setting up an upstream X build system any day.05:25
TomJaegerwgrant, upstream uses svn05:25
wgrantTomJaeger: If the packaging doesn't use a VCS, there is little excuse not to use a patch system.05:26
rgreeningupstream != packaging05:26
TomJaegerwgrant, except that it would probably take me an hour to separate the changes into patches and setting everything up, time that I don't have.  And the patch system won't be of much use anyway if the is ever merged with debian again.05:31
rgreeningTomJaeger: actually the 3 changes are in patch format already here: http://bugzilla.kernel.org/show_bug.cgi?id=1230105:32
ubottubugzilla.kernel.org bug 12301 in USB "Fingerprint reader doesn't respod after the first use" [Normal,Closed: code_fix]05:32
rgreeningwhich is where you got them05:32
wgrantTomJaeger: You had to apply the changes as patches in the first place.05:32
wgrantAnd I hadn't noticed before that it was derived from Debian in ancient times.05:33
rgreeningand TomJaeger we sync/merge with debian after each release05:33
TomJaegerexactly, so right now, we should only be worrying about fixing the bugs, and not duplicating work05:34
rgreeningmaybe getting the patch into the original code would be more your style :) I hear they have a vcs05:35
rgreening:)05:35
wgrantSince it is in fact somewhat derived from Debian, and it doesn't appear to have a patch system at the moment, AND it's raw old-style debhelper, applying the patches inline isn't an entirely terrible crime.05:36
TomJaegerThe patch was written by the thinkfinger author, so, yes, I'd expect it to become available upstream sooner or later05:36
rgreeningew...05:36
rgreeningold debhelper is god awful05:36
TomJaegerrgreening, since you said earlier that quilt was so easy to use and set up, I've had a quick look at how things work (maybe the impression that I got when I first dealt with this a long time ago, was wrong after all)05:59
rgreeningawesome06:00
rgreeningquilt is powerful06:00
TomJaegerSo I checked the PackagingGuide, and they explain how to use it.06:00
TomJaegerIt seems a little complicated to my, I will definitely continue to create my patches with git and then stick them into the debian/patches directory06:01
TomJaegerI'd also be worried about forgetting the add step and creating inline patches by accident.06:01
TomJaegerBut the packaging guide says nothing about how to set it up.  But they give an example package, xterm.06:02
TomJaegerSo I checked out the xterm package and looked at their debian/rules file06:03
TomJaegerThe file is 231 lines long and contains a lot of quilt boilerplate.  Not exactly what I'd call easy to set up.06:03
rgreeningIt's simpler than that06:04
rgreening1. add a dep on cdbs and quilt in the build-deps06:04
rgreening2. add the patch to debian/patches and add the name to debian/series06:05
TomJaegermaybe that should be explained in the packaging guide?06:05
TomJaegerWhat if my package doesn't use cdbs?06:05
rgreening3. add include /usr/share/cdbs/1/rules/patchsys-quilt.mk to rules06:05
rgreeningthats it06:05
rgreeningcdbs is for step 3.06:06
rgreeningand it's onlt for build dep and not run=time06:06
TomJaegerAnd it'll work with a debhelper package?06:06
rgreeningmost newer packages will likely work with this 3 step06:06
rgreeningyes06:06
rgreeningadd the step 3. just after tyhe debhelps like in rules06:07
rgreeningTomJaeger: in this package, since its an real old debhelper, two ways to update... 1) use quilt and update the rules file to work with cdbs (doesn't appear to at the moment). 2) add patch definitions to rules and forget quilt.06:10
TomJaegerIs there a reason why the simple patchsys and dpatch are featured more prominently in the packaging guide than quilt06:10
TomJaegerdpatch should be deprecated in my opinion, I've had nothing but trouble with it.06:11
rgreeninglook at balder2d. I recently updated it in this way06:11
rgreeningTomJaeger: http://paste.ubuntu.com/132323/06:12
rgreeningadd that to rules and forget adding cdbs and quilt deps.06:12
rgreeningyou won't need a series file either with that06:13
TomJaegerIn this particular instance, I really don't think it's worth it, though.  The package should be fixed properly before any more work is done on it.06:13
rgreeningbut you still copy the patch to debian/patches and nam,e .patch06:13
rgreeningading the paste I supplied and http://paste.ubuntu.com/132324/ as the patch should do it06:14
rgreening(I was working on it at the same time here...)06:15
TomJaegerrgreening, is anyone working on updating the packaging guide?  It seems like quilt is superior to the alternatives, yet it's not at all obvious from the guide that you should use it or how you should use it.06:20
rgreeningnot that I am aware.06:21
a|wenthis looks pretty much like af rebuildd hick-up http://builder.ubuntuwire.com:9998/job/47540 ... can we do anything to get the rebuildd to try again?06:28
=== santiago-pgsql is now known as santiago-ve
TomJaegerrgreening, as much as I'm sympathetic to your cause, I really can't justify any work on the thinkfinger package at the moment.  I'm pretty caught up in real life right now, and I've got other linuxy things to worry about that are more important to me, for example I've got patches related to bug #217908 that I've been meaning to send to the cairo list for weeks.  If this means that we're not going to see an update to the thinkfin06:48
TomJaegerger package, then that sucks for the people that want to use their fingerprint reader on a jaunty system.  I've gotten used to maintaining packages outside the distribution in various PPAs anyway, one more package won't hurt.06:48
ubottuLaunchpad bug 217908 in xserver-xorg-video-radeonhd "Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD implementation in several video drivers" [Medium,Fix released] https://launchpad.net/bugs/21790806:48
wgranta|wen: It was sort of a hiccup, but not really - the package was actually deleted from Jaunty after the job was created.06:59
wgrantSo a few days later it tried to build, and BOOM.06:59
wgranta|wen: But please ping me with any issues with the rebuild.06:59
a|wenwgrant: okay, that's makes sense; is there any way to get it off the list?07:00
a|wenand i'll ping you if i see any other strange things through the list07:00
wgranta|wen: Nothing that makes sense. But I intend to improve the listing some time this week to only show failures for current sources.07:00
wgrantAt the moment it will show all failures for the distroseries.07:01
a|wenwgrant: okay; that would solve the purpose :)07:01
wgrantWhich isn't too useful if it is fixed later.07:01
wgrantAlso, I can give people tarballs of failed build logs to grep through for common issues.07:04
dholbachgood morning07:04
wgrantLike the 70 distutils /usr/local-related ones I grepped into recently.07:04
wgrantMorning dholbach.07:05
dholbachhi wgrant07:05
fabrice_sphi dholbach ;-)07:06
dholbachhiya fabrice_sp07:07
a|wenwgrant: we probably still have a number of "use --without-arts" ... that is those i'm on lookout for now07:07
wgranta|wen: Yes, around 56 at last count.07:07
wgrantBut that was about 2500 builds ago.07:08
wgrantI can give you a list in a minute or so...07:08
a|wenwgrant: i've fixes 68 of those within the last 3 days ... so should be lower now :)07:08
a|wenwgrant: that would be cool with a list, thx07:08
wgranta|wen: http://paste.ubuntu.com/132329/07:11
a|wenwgrant: don't they disappear from the list, when they get fixed ... or how often are they updated?07:12
wgranta|wen: No, they stay there forever at the moment. That's what I plan to fix.07:12
wgrantBut the rebuild only started 6 days ago, so it's not too bad yet.07:13
a|wenokay, i've got it now ... the good news is that all the kde-i18n-* from that list is fixed07:13
iulianGood morning dholbach.07:16
dholbachhiya iulian07:17
RAOFHello everyone!  I now have internet again!07:44
wgrantRAOF: I'm sure I can get Telstra to fix that.07:47
wgrantAlthough I probably don't need to intervene for it to happen.07:48
RAOFProbably not.  Apparently the main problem was that the wiring in this building is corroded to buggery.07:48
RAOFNetting me the lightning fast download sync speed of 4Mbit/sec.07:49
wgrantExcellent.07:49
* RAOF goes back to ensuring the en_AU translation of GNOME Do isn't in Arabic.07:49
slytherinRAOF: which Telstra service are you using?07:53
RAOFslytherin: None.  Only the local loop that they own.07:55
slytherinoh07:55
RAOFI've got me an Internode "please, don't make me have to contact Telstra" naked DSL plan.07:55
savvasDepends: python (<< 2.7), python (>= 2.5), python-central (>= 0.6.11), python2.607:57
savvasis there any way to make 2.5 and 2.6 libs, but not to add python2.6 ?07:57
Toadstoolg'morning07:58
savvashere's the pbuilder log: http://paste.ubuntu.com/132335/07:59
maxbsavvas: grep for any #!/usr/bin/python2.6 lines that might inadvertently be present08:00
savvasmaxb: none unfortunately08:01
savvasI think it has to do with the fact that it builds libs for 2.6: -rw-r--r-- root/root     70488 2009-03-17 08:51 ./usr/lib/python2.6/dist-packages/imgSeekLib/imgdb.so08:01
savvasbut then again, what do I know :P08:01
maxbhm08:02
savvashere's the debdiff I'm preparing: http://paste.ubuntu.com/132337/08:03
* savvas bbl08:10
LaneyI have 123 emails from LP since last night...08:47
* Laney eyes rosetta08:48
=== fta_ is now known as fta
binarymutant]3.08:58
binarymutant0+69-0008:58
sorenLaney: Lucky.09:11
LaneyDid I get off lightly?09:14
directhexMD2 beta 2 is out. i shall prep a merge09:28
sorenLaney: I think you did. I wish I only got that many a day :)09:32
gesergood morning09:35
slytheringeser: good morning09:35
directhexgrr, gnomish things going on mean i can't test-build monodevelop 2 beta 210:14
slytherindirecthex: test build where? on your machine or ppa?10:22
directhexslytherin, local machine. looks like not all deps have caught up yet (libfontconfig1 is the current baddie)10:23
slytherindirecthex: hmm10:24
directhex  libfontconfig1: Depends: fontconfig-config (= 2.6.0-1ubuntu7) but 2.6.0-1ubuntu9 is to be installed.10:24
directhexit'll right itself in a few hours. the timing just sucks10:24
DktrKranzdirecthex: if it blocks you, ask a buildd-admin to rescore it a bit, so it will be mirrored sooner10:25
directhexDktrKranz, nah, not that urgent - anyway, it's a test build for the most recent monodevelop 2 beta, some poor bugger would still need to sponsor the merge10:26
* DktrKranz hides10:27
DktrKranz:)10:27
* slytherin wishes eclipse's latest release was in repos to give tough competition to monodevelop.10:37
directhexslytherin, not happening for jaunty? :/10:37
slytherindirecthex: Nope. The Debian java packages who used to work on eclipse are MIA.10:38
directhexslytherin, gah!10:38
directhexslytherin, something to aim for for karmic, perhaps?10:38
slytherindirecthex: yes, sure. And by that time eclipse will have added another bunch of build deps. eclipse is becoming mammoth.10:39
directhexslytherin, far be it for me to ever consider using words like "bloat" in the same sentance as "java" ;)10:40
directhexslytherin, i really hope java 7's reshufflinf of the class library can help bring some of this crap back under control10:40
directhexand it's pretty unfortunate for dev tools to EVER be outdated in a release - that's one reason i pushed for MD2 FFe: MD1 in <=intrepid sucks10:42
slytherindirecthex: at least we have netbeans updated.10:44
directhexslytherin, are there any qt-java apps in the archive, out of interest?10:46
savvasis it normal for pycentral to request in "Depends:" a specific python version, i.e. python2.6 when it packages a 2.6 library ?11:14
savvas(there's no python2.6 hashbang as far as I can see)11:15
slytherindirecthex: don't think so. I don't even know if there are any java bindings for Qt11:16
directhexslytherin, there are - the recent announcement was that nokia were dropping them, so the community would need to maintain them if they care11:17
directhexslytherin, i ask as the first ever real Qyoto app has surfaced, an XMPP client written in C# for Qt411:18
savvasqyoto?11:19
savvasI hope that's a typo :P11:20
directhexsavvas, current Qt CLI bindings project11:20
savvasoh, hehe11:20
directhexlibqyoto4.3-cil - CLI bindings for the Qt 4 toolkit11:20
directhexalso, a monodevelop addin to generate c# from Qt Designer files11:21
Laney"Looks sexy, very alphaish" was my assessment of Synapse11:21
Laney<311:21
savvas* libqyoto4.4-cil11:21
savvas:)11:22
directhexLaney, yes11:22
directhexLaney, but points for sheer awesomeness11:22
directhexLaney, need to start thinking about karmic mono goals11:23
slomoslytherin: ping12:00
slytherinslomo: hi, long time no see. I wanted to discuss the broken dvd playback on jaunty. Had some discussion with seb128. I have even mailed debin maintainer of libdvdread but yet to receive the reply.12:02
* directhex puts his net gun away12:03
slomoslytherin: ok, give me some details please :)12:03
directhex"configure2 sucks"12:04
slytherinslomo: currently all apps that link against libdvdread4 are broken. This includes totem with gstreamer backend, mplayer, vlc, thoggen etc.12:04
slomoslytherin: why?12:05
slytherinslomo: The upstream libdvdread4 is shipping some script configure2 and a Makefile which seem to be creating some problem. I am not sure what the problem is exactly.12:05
slomoslytherin: hm, ok... so "something is broken"? :) there's no known fix yet? and is the problem in libdvdread or in the using applications?12:07
slytherinslomo: I know a workaround. The problem is in using all applications that use libdvdread4.12:08
slytherinslomo: I initially thought this snippet in dvd_input.c was causing problem.12:09
slytherin/* dlopening libdvdcss */12:09
slytherin#ifdef HAVE_DLFCN_H12:09
slytherin#include <dlfcn.h>12:09
slytherin#else12:09
slytherinbut the Makefile has HAVE_DLFCN_H defined, so this should not be the problem.12:10
slomoslytherin: so what's the workaround?12:12
slytherinslomo: workaround is to use the old configure script, which needs to be generated with autogen.sh12:13
slomoslytherin: but you don't know the difference between the configure scripts?12:16
slytherinslomo: No. I tried hard to figure out. :-(12:17
slomoslytherin: no differences in config.h for example?12:21
slomoslytherin: also, is this bug already filed in debian or known by the maintainer?12:21
slytherinslomo: I wasn't sure if the bug is present in Debian. Hence I mailed the maintainer offline.12:21
slomoslytherin: ok, i don't know either because i have no dvds here :)12:22
white_slomo: just replied to your email, thanks for working on it :)12:24
=== white_ is now known as white
slytherinslomo: I will see if any of my friends have Debian unstable system12:24
slomowhite: np... it's only glib that is affected btw, libsoup is fixed since 2.2.101 (by using glib functions) and gst-plugins-base 0.10.19 and before in stable are also not affected12:25
whiteslomo: did you check oldstable as well?12:25
slomowhite: libsoup in oldstable has the bug, right... so that's glib for stable and oldstable and libsoup for oldstable... debdiffs will follow in some minutes ;)12:26
whiteslomo: much appreciated :), i suppose gst-* in oldstable is not affected either?12:27
slomowhite: no12:27
slomowhite: i've sent you the three debdiffs12:45
slomowhite: if you're confused by the uploaders changes in the debdiffs, that's caused by the gnome-pkg-tools uploaders.mk12:51
whiteslomo: just for the record, gst-plugins-base uses glib?13:03
slomowhite: yes (and the version i've uploaded to unstable today fixes the base64 CVE, should move to testing asap)13:04
whiteslomo: ok, i am always getting confused by the various gst* packages and their versions and where the plugins are ..., but if you say they are not affected in stable/oldstable, then that's even better :)13:07
slomowhite: the problem was a feature that was added in 0.10.20 of gst-plugins-base (images in vorbis tags) and it used the glib base64 functions ;)13:10
bddebianHeya gang14:17
directhexafternoon, bazza14:17
bddebian:)14:18
=== balbir_ is now known as bsa
=== bsa is now known as bsarora
=== Andre_Gondim-afk is now known as Andre_Gondim
* RainCT can't boot with the latest kernel (jaunty) :(14:51
sorenThis feels like a silly question, but what is the functional difference between the Apache license and the BSD license?14:53
ScottKWhich BSD license?14:54
soren/usr/share/common-licenses/BSD14:55
ScottKA quick read leads me to believe the patent grant and the requirement to document what you've changed are the major differences.14:55
ScottKIIRC the patent grant is what makes the Apache license GPL v2 incompatible.14:57
sorenOh, right. The patent thing.14:57
directhexyay, patents14:57
ScottKYou would say that.14:57
directhexof course!14:58
* directhex patents IRC14:58
sorenSo if I'm reading the legalese correctly, if you contribute to an ASL licensed project something that is covered by a patent you hold, you implicitly grant the project a patent license?15:02
ScottKThat's pretty much my reading.15:02
ScottKAnd you get patent licenses for anything anyone else contributed.15:03
sorenThat doesn't offer much of an incentive to contribute those patches back to the project.15:03
ScottKWhich vanishes as soon as you sue someone.15:03
ScottKSo it's a bit of an enforced patent peace.15:03
ScottKSo making the contribution gets you some protection too.15:03
sorenAh, I see.15:04
sorenScottK: Thanks!15:05
ScottKsoren: yw.15:05
mok0Argh we have no latex equation editor for Ubuntu... :-(15:40
=== Andre_Gondim is now known as Andre_Gondim-afk
directhexDktrKranz, if it helps, MD2 beta 2 is a pure bugfix release - 130 closed tickets. so no FFe worrying this time \o/15:43
DktrKranzdirecthex: well, I think it has been approved anyway15:44
directhexjust sayin'...15:45
directhexshould mean a simple uupdate-only update, but i can't test until mirror.ox.ac.uk stops sucking15:45
DktrKranzdirecthex: don't worry, just ping when ready :)15:51
adelie42I hope someone can help... I just discovered that, evidently, I have two launchpad accounts.  When I discovered it, it says there had been no activity in over 3 years, now it is gaining as a contributor. I am VERY confused. It says I am making bazaar revisions, but the account doesn't even have any registered keys.15:53
ScottKadelie42: #launchpad is the place to ask.15:54
adelie42k15:54
mok0adelie42: or post a question on LP... I believe your accounts can be merged15:54
adelie42that would be nice15:55
mok0adelie42: You're not the only one who has had that problem :-)15:57
adelie42It is a little funny to see myself as #2 and #4 contributor in a project...15:58
RoAkSoAxHi guys. how can i create a jaunty pbuilder on debian?16:12
maxbAt a guess, install jaunty's debootstrap .deb ?16:14
maxbAssuming Debian's debootstrap doesn't already handle jaunty?16:15
maxbActually all ubuntu since gutsy have used the same debootstrap script16:17
maxbso you can probably get away with just adding another symlink to /usr/share/debootstrap/scripts/16:17
ScottKEither way shoule be fine.16:31
ScottKshoule/should16:31
cjwatsonRoAkSoAx: debootstrap >= 1.0.11 in Debian supports jaunty16:32
RoAkSoAxthanks cjwatson :)16:32
cjwatsonas of a while back we've been making efforts to keep debootstrap pretty much in sync16:32
cjwatsonin fact, I was just going to sync it up again now16:32
RoAkSoAxok :) great to hear :D16:33
AnAntHello, is Scott James Remnant here ?16:35
cjwatsonAnAnt: try #ubuntu-devel16:36
=== azeem_ is now known as azeem
savvasjames_w: bug 297847 - is there a reason shares-admin / "shared folders" was disabled in the menus and not shown in gnome? :)17:16
ubottuLaunchpad bug 297847 in gnome-system-tools "Shared Folders Administration Tool missing" [Undecided,Confirmed] https://launchpad.net/bugs/29784717:16
vadi2Hi, I have a question - a certain package is broken and is unusable in jaunty. How can I get it looked at if its not too late?17:46
maxbFile a bug to start with17:50
vadi2where?17:50
vadi2the offending project was tagged as affected, but I doubt anyone will see it anytime soon.17:50
maxbWhy are you avoiding mentioning what the package/project is?17:51
vadi2er, because it was not asked for?17:52
vadi2the project is gnome-web-photo and here is the report: https://bugs.launchpad.net/shutter/+bug/34240817:52
ubottuUbuntu bug 342408 in gnome-web-photo "[jaunty] can't take web screenshot: libxul.so not found" [Undecided,Confirmed]17:52
=== warp10 is now known as gaspa2
maxbvadi2: You could make a fixed package and follow http://wiki.ubuntu.com/SponsorshipProcess17:55
vadi2and what is the success rate of that? (I just have a very poor experience when dealing with debian/ubuntu packagers, so just inquiring before I commit time)17:57
maxbDunno, but I'd imagine "greater than the success rate of hoping someone will make the fix for you"17:58
vadi2heh17:58
vadi2that's fine then I guess. breaking & not caring about it ftw :)17:58
adelie42I made a merge proposal of a branch that fixed a bunch of minor bugs. My proposal is still pending review, but I found another bug on launchpad that I believe I can fix.  Are merge proposals are on a per revision basis, or per branch, and if I want to make further contributions, do I need to start a new branch, or can I keep working on the current one?17:58
=== gaspa2 is now known as warp10
adelie42basically, does merge say, "This is stable and complete enough of a revision point to add" or "I'm done, lets move this into the trunk"18:01
joaopintomaxb, was your answer expected to provide motivation for someone asking how to followup a problem resolution ?18:03
=== iulian is now known as Guest20156
maxbIt was an attempt to be truthful, in the face of a fairly unanswerable question18:08
=== Andre_Gondim-afk is now known as Andre_Gondim
jpdsadelie42: You should have a separate branch per fix/feature.18:17
adelie42jpds: According to the documentation, it says it is easier for maintainers to do a branch merge than apply a debdiff. bzr has the latest development editions while apt-get source is the lastest stable. Should I really be registering a new branch for every minor fix?18:23
jpdsadelie42: Well, you could have all the fixes in one branch.18:25
c_korncan bug 344168 be acked?18:26
ubottuLaunchpad bug 344168 in apt-cacher-ng "FeatureFreezeException: please sync apt-cacher-ng 0.3.4-1 (universe) from debian (sid)" [Undecided,New] https://launchpad.net/bugs/34416818:26
adelie42ok, but once I make a merge proposal, that means any additional work should go into a new branch, not the old one?18:26
sorenadelie42: That's the general idea, yes.18:26
sorenIt allows work to continue on the two different features in parallel if they for some reason are not going to get merged in the order in which they're implemented, for instance.18:27
adelie42So if I got new feature A v1.0 and want to get it merged, I should open a new branch for feature A v1.1?18:29
sorenI would, yes.18:29
sorenDon't be afraid of branches. They're your friend :)18:30
iulianc_korn: Could you please give me a link to the upstream ChangeLog?18:30
adelie42Ok, thanks!18:30
iulianc_korn: I see that it's a new upstream release.  If it's a bug fix only release, it does not need an exception.18:31
c_kornthe source is here: http://ftp.debian.org/debian/pool/main/a/apt-cacher-ng/apt-cacher-ng_0.3.4.orig.tar.gz18:31
c_korniulian: http://pastebin.com/d3a955dd6 changelog in the tarball18:32
adelie42I think I just have a fear someone is going to say "What, he started a whole new branch for THIS? wtf, stop with all the branches!"18:32
iulianc_korn: It does need a FFe, please subscribe motu-release.18:33
c_korniulian: done18:34
iulianc_korn: See https://wiki.ubuntu.com/FreezeExceptionProcess18:34
c_kornoops, I missed the first point18:35
iulianc_korn: I've unsubscribed u-u-s for now.18:36
Laneyright, cool18:44
LaneyI think I can push a python 2.6 miro18:44
Laneyit seems pretty solid18:44
savvasalways expect a bugstorm hehe :P18:45
LaneyI'd rather have that than it not working at all18:45
LaneyI'm after an FFe on bug 336029. New features are minor compared to the amount of bugfixes18:54
ubottuLaunchpad bug 336029 in miro "[FFe] Merge miro 2.0.3-1 (universe) from Debian unstable (main)" [High,In progress] https://launchpad.net/bugs/33602918:54
adelie42So my branch fixing several bugs was merged recently, should I go back to all those bugs and mark them as "fix committed"? Further, I am looking for bugs I can fix, but keep looking through "new" bugs to find that there are already patches submitted. Can these be marked as something other than 'new'? Would 'in progress' be more appropriate, or would it be helpful to round these up as branches, test them, and propose merge?18:54
Laneyadelie42: There's a --fixes option to bzr which I think automatically changes the status18:55
Laneyaaaaaand have you heard of harvest for finding things to fix?18:56
adelie42I could not figure out the syntax for --fixes based on the info in the man page, and no, have not heard of harvest18:56
Laneyhttp://daniel.holba.ch/harvest/18:57
savvasdarn, pastebinit doesn't work with http://paste.ubuntu.com anymore :\18:59
adelie42Laney: So if I failed on the '--fixed' part, then I should go back and mark those as 'fix committed' for branches that have already been merged?19:00
Laneysavvas: the author is here!19:00
Laneyadelie42: If they're going to be uploaded to Ubuntu and the task is against an Ubuntu package then yes19:01
LaneyI usually set fix committed after I sponsor an upload from a debdiff19:01
savvasLaney: actually, ignore that comment, the problem seems to be with characters in the text :)19:01
adelie42Laney: and for patches submitted, if there is no related branch, then that means it has not yet been applied and some work of a maintainer could be saved by turning the patch into a merge proposel after testing the patch?19:01
Laneyadelie42: branch merges aren't the normal way of sponsoring yet19:02
Laneythere's not much point converting a debdiff to a bzr branch really19:02
adelie42if a reasonable enough looking patch has been submitted, can at least mark the but as 'in progress'?19:03
Laneyno, that's not what in progress is for19:04
Laneyhttps://wiki.ubuntu.com/Bugs/Status19:04
adelie42laney: ok, so if I fixed a bug in my own branch, bug can be marked 'fix committed' even before it is merged into the main project. If a patch has been submitted, but bug is still marked new, then I could independently confirm the bug and mark as 'confirmed'.19:09
Laneyerm19:09
LaneyI would only mark fix committed once it gets merged19:09
adelie42ok19:10
adelie42Laney: err... than what does '--fixes' change the status to?19:11
Laneynot sure how it works19:11
cristihy, realated to the python transition, should i change in debian/pyversions from 2.4- to 2.6- ?19:17
Laneyno19:17
jpdsadelie42: It just links the branch to the bug report.19:17
cristiLaney: ok, thank you19:17
adelie42Laney: Read through the 'bug status' page you sent me. It looks like if someone else confirmed the bug in comments then it is reasonable to set the status to confirmed even if it wasn't confirmed yourself. Is that too liberal? I am reading through harvest, but I am still get used to launchpad. Trying to make myself useful  :)19:18
Laneythat sounds right19:19
Laneyby the way, #ubuntu-bugs is better for bug triage questions19:19
adelie42jpds: thanks, that makes sense. can you give an example if --fixes syntax for launchpad?19:19
adelie42Laney: ok19:20
jpdsadelie42: bzr commit --fixes lp:bug###19:20
adelie42jpds: ha ha, I was very close  :)19:20
jpdsadelie42: Now try: "bzr rocks"19:22
adelie42ha ha19:22
LaneyPurpose: Statement of optimism.19:22
adelie42nice19:22
Laneyhaha19:22
Turlhi19:47
Turlin CDBS, how can I add a rule post-make install ?19:47
Laneybinary-post-install/foo::19:47
Laney  bar19:47
Laney(iirc)19:48
Turland install/foo:: is pre-make install?19:48
Laneybinary-install19:49
Laneynot sure, check the manual19:49
Laneyit's something like that19:49
Laneyactually, maybe binary-install is what you want19:49
RainCT(wow, I've reinstalled Jaunty and now the laptop boots 30 seconds faster)19:56
Laney:O19:58
jdongzero length files speed bootup??19:59
jdong(kidding!)19:59
JontheEchidnaha20:02
RainCTeither there's something really wrong with updating or ext4 is awesome (I already had ext4 before, but without reformating) :P20:02
jdongRainCT: without reformatting you don't get the extent allocation benefits20:03
jdongthat makes a huge difference on even modestly sized files20:03
RainCTjdong: I see.. I've heard that there's some "online defrag" tool, is that available on Jaunty? (I guess /home would like it too :P)20:04
jdongRainCT: it's not available yet AFAICT20:06
jdongI believe there isn't solid consensus on the API yet20:06
jdongi.e. you can probably find some git patchset if you dare20:06
RainCTnah, I'll wait20:06
jdongIMO the fragmentation on ext4 is not nearly that bad to warrant defragging any time within the next 6 months anyway!20:07
RainCTbut /home is upgraded from ext3 :)20:07
jdongRainCT: home tends to be easy. Tar up its contents and unpack it.20:09
jdongor rsync shuffling20:09
jdongI had the rsync shuffling method described in my ext4dev howto20:09
jdongit more or less, on my volume with 70% free space, gives clean ext4 performance20:09
RainCTjdong: URL? :)20:10
NCommanderhey RainCT, can I steal you for a REVU?20:11
NCommander(ecosconfig-imx was ACCEPTed on the first go today :-))20:11
RainCTcool20:11
jdongRainCT: http://ubuntuforums.org/showthread.php?t=97370120:11
NCommanderRainCT, http://revu.ubuntuwire.com/p/redboot-imx20:11
jdongsee "OPTIONAL: Converting all files to extent format"20:11
NCommanderjdong, also, if your interested?20:11
RainCTjdong: thanks20:12
RainCTlet me reboot, I want my proprietary driver! :P     /me hides20:12
jdonghaha20:12
NCommanderREDboot :-P20:12
=== fabrice_sp_ is now known as fabrice_sp
RainCT....   apt-get and aptitude are segfaulting now at "generating dependencies..." if I try to install/update something20:21
RainCTanyone seen this before?20:22
fabrice_spRainCT, do you have debug repository enabled?20:25
RainCTfabrice_sp: what is that? :P20:25
RainCTwait, it's fixed now20:25
RainCTweird20:26
RainCTand now it happens again20:26
fabrice_spyes :-/20:26
RainCTsudo dpkg --configure -a  fixes it for the next run20:26
fabrice_spit's http://ddebs.ubuntu.com20:26
RainCTnope20:27
RainCTapport tries to file a bug about it but crashes :/20:27
=== Andre_Gondim is now known as Andre_Gondim-afk
fabrice_spit is similar to Bug #341402 ?20:30
ubottuLaunchpad bug 341402 in apt "apt-get: segmentation fault (jaunty)" [Undecided,New] https://launchpad.net/bugs/34140220:30
RainCTI don't know, but it's like bug #16331620:31
ubottuLaunchpad bug 163316 in apt "Segmentation fault" [Undecided,Invalid] https://launchpad.net/bugs/16331620:31
fabrice_spnot the same backtrace, so it's not the same bug20:32
RainCTok, removing those .bin files mentioned in the first report fixed it20:32
fabrice_spReally? So it was a pb with the mirror, then20:33
RainCTcool, Launchpad has "Klingon" in the languages list :P20:38
NCommanderIt does?20:39
NCommanderneat20:39
* RainCT cries20:41
NCommanderRainCT, ?20:42
RainCTmy Development folder (which contains all coding stuff) is empty . . .20:42
NCommanderO_O;20:42
NCommanderAre you running ext4?20:42
RainCTyes20:43
NCommanderOuch :-/20:44
Laneybackups?20:46
RainCTNo.20:46
LaneyBest way to learn is to be burned ;)20:46
* Laney offers RainCT sympathies20:47
* NCommander guesses this isn't a good time to ask for a REVU :-/20:47
RainCTLuckily, much of the stuff is online (bazaar branches and stuff) or are abandoned projects..20:48
RainCTehmmmmm20:49
RainCTmkdir: cannot create directory `Python': File exists          mkdir: cannot create directory `hi': Input/output error20:49
RainCTlooks like everything is still there, but I can't see it20:50
NCommanderRainCT, fsck?20:51
RainCTunmounting home, see you later20:52
jdongouch am I seeing ext4 trashing?20:57
nxvlScottK: ping21:01
=== RainCT_ is now known as RainCT
RainCTit's back :D21:01
NCommanderRainCT, BTW, did the PPA improt feature ever get turned on?21:04
NCommander(and can we get a link to the mian index?)21:04
RainCTNCommander: Yes, it's running (imports are processed every 5 minutes; uploads every 3, and I'll get that down to "as soon as they're complete" -with inotify :)-).21:06
NCommandervery impressive21:07
NCommanderNow I can just suck download from ym PPA :-)21:07
RainCTNCommander: about the link, sure, but import.py still needs some polish (like actually implementing the check that ensures that the package builds, or remove the text about that)21:08
NCommanderRainCT, well, implementing that requires parsing Packages.gz; not difficult, but I haven't touch REVU in ages21:08
fabrice_spShould I fix this error: pycentral: pycentral debhelper: missing XB-Python-Version attribute in package ?21:08
fabrice_spor it's not important21:08
NCommanderfabrice_sp, yes21:08
fabrice_sp?21:08
fabrice_spok21:08
=== erhesrhsrtb54vyh is now known as Elbrus
RainCTNCommander: I see you've got the copyright file sorted out.. :)21:12
NCommanderRainCT, it grew expontentionally21:13
NCommanderIt was over 1000 lines, but Apache 2 is a common license so I was able to cut some fat out21:13
RainCTNCommander: well, I've no further comments about the packaging, and I can't build nor test it :P21:20
NCommanderRainCT, well, you need an iMX51 babbage board to test, and ARM hardware just to build, but I can point you to a PPA with it built21:20
RainCTNCommander: the output of  dpkg-deb -c *.deb  will do21:22
NCommanderRainCT, http://paste.ubuntu.com/132701/21:23
NCommanderah ****21:23
NCommanderI just saw a mistake :-)21:23
RainCThehe21:24
NCommanderRainCT, http://paste.ubuntu.com/132702/21:29
NCommanderRainCT, new version uploading21:31
RainCTNCommander: tell me when it's up21:35
NCommanderRainCT, its up21:36
joaopintobug 344500 should be a Xorg bug, right ?21:36
ubottuLaunchpad bug 344500 in alarm-clock "The entire system crashes when opening the alarm-clock applet" [Undecided,New] https://launchpad.net/bugs/34450021:36
joaopintoshould a X app be able to override xorg events for the other windows and preventing screen redraw ?21:39
RainCTNCommander: (advocated)21:39
NCommanderRainCT, O_O; so the copyright looks ok to you?21:39
RainCTNCommander: I'd have written which files belong to whom, but well..21:40
NCommanderRainCT, its a little crazy to do that21:40
NCommanderlike a few thousand lines crazy21:40
RainCTwildcards exist21:41
RainCTbut yes, /me is a bit crazy :)21:41
NCommanderRainCT, so you think its good to upload?21:49
NCommanderRainCT, and the copyright is serviceable?21:49
=== bastiao__ is now known as k0p
LaneyScottK: Responded to you on the miro ffe21:51
alberticohi, where can I look for info/tutorials in order to learn how to create a debian package for an application22:23
albertico?22:23
iantoalbertico: What sort of tutorials are you interested in? Text or video?22:23
alberticoanything useful  :)22:24
iantohttps://wiki.ubuntu.com/MOTU/Videos22:24
alberticoianto, both are fine22:24
iantoAnd the rest of the /MOTU section too :)22:24
alberticoianto, thanks, looking into it22:24
iantoHave fun with the videos :)22:25
alberticoianto, another thing, how are packages mantained on ubuntu?22:25
iantoBy the MOTU team, they get uploaded to the repositories22:25
alberticoianto, I mean, how is the package updating handled in regards to new versions?22:25
iantoOh anyone can come along and update it, just make sure that others know that you are so the effort isn't duplicated22:26
alberticoianto, so the MOTU team uploads new versions of a new program22:26
iantoalbertico: If it is a Universe application yeah22:26
iantoUniverse as in free as in beer ;)22:26
iantoIf it's main, the core-devs do it, or so I recall22:27
iantoAnd the other two, I can't remember who does them for the life of me :)22:27
alberticoianto, so an update to the nginx package, which is on universe, must be uploaded by a MOTU team member22:27
iantoalbertico: Basically, you can make the changes yourself just notify a member when you are done22:28
alberticoianto, how can I know who is maintaining that package?22:28
iantoAnd they will look over and see if it is good or bad22:28
iantoalbertico: There aren't maintainers are there are  in debian, but you can check the changelog and ask the last uploader to see if they know of the newer version and don't mind you working on it22:29
ianto*like there are22:29
iantoYou are asking about the nginx package then?22:29
alberticoianto, yeah22:30
alberticoianto, btw, does it work the same for the server and desktop distros?22:30
iantoYeah they use the same mirrors/repos22:30
iantoJose Parrella was the last uploader on 14th Sep 200622:31
ianto*contributoor22:31
iantoalbertico: Have you packaged before by the way?22:32
alberticoianto, the debian packages web page shows Jose Parrella and Fabio Tranchitella22:32
iantois there an updated version in Debian?22:32
alberticoianto, nope, I want to learn how to package... and then, try to see if my work can contribute somehow22:33
adelie42So I have noticed when I push a branch for the first time, I always get: 'Target directory ... already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway.' Is that just normal, or is there something else it was anticipating me doing first?22:34
alberticoianto, nginx on lenny stable is a little bit old22:34
iantoIt may be what Debian call an "orphaned project", I'm not a Debi guy but regardless, if you feel that you can update it, do it but I recommend doing instead a new simple package22:34
iantoSomething like mv in other words ;)22:34
alberticoianto, jeje, will take that into account... better start simple  ;)22:35
iantoalbertico: Nederlander? :p22:35
alberticoianto, nope, Puerto Rico22:36
iantoI just assuumed from the j instead of h22:36
iantoCould've been a  typo though ;)22:36
iantohttps://wiki.ubuntu.com/PackagingGuide/Complete22:37
iantoThat will also help when starting to package 622:37
ianto^22:37
alberticoianto, hehe... in spanish we put the j instead of the h... my fingers work faster than the translation part of my brain22:37
adelie42Is 'Target directory already exists, but does not have a valid .bzr directory.' normal for a first push just to inform the user that there has never been a push to that directory before?22:38
alberticoianto, many thanks!  going to start reading and watching the tutorials  :)22:41
iantoalbertico: Have lots of fun22:42
RainCTNCommander: copyright should be OK if you've listed everything22:59
NCommanderThanks23:00
RainCTNCommander: and whether I think if it's good to upload, I do think so if you do :P23:00
RainCTand your previous upload has also got an advocate from someone else23:01
RainCTI'm off now, good night :)23:01
binarymutantis there a pidgin team?23:02
=== asac_ is now known as asac

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