/srv/irclogs.ubuntu.com/2010/08/02/#ubuntu-motu.txt

freeflyingshadeslayer: ping01:08
freeflyingshadeslayer: do you still need a sponsor upload?01:08
stalcupwhat's up with REVU days as of late?01:08
bdrunglucas: why do you subscribe ubuntu-sponsors to a sync request?01:09
lucasoops, was a test, actually01:19
lucas(well, the fact that it needed to be synced was real)01:20
bdrunglucas: should i blow the whistle on you? i used syncpackage for it.01:28
stalcupi would blow the whistle01:29
* stalcup hands over a whistle01:29
* bdrung hopes that he has used the phrase correctly.01:31
stalcupbdrung: since I hate manpages, what is the proper context whilst using syncpackage01:31
stalcupyou did :)01:31
stalcupdo you use the dsc url or the actual dsc?01:31
bdrungstalcup: i used ack-sync, which uses syncpackage01:32
stalcupah01:33
stalcuphehe, bdrung we should eh?  but when?  :)01:33
bdrungstalcup: i don't get your question01:34
stalcupfrom the mailing list - when should REVU days be?01:35
bdrungstalcup: asap to get them into the archive, far away in getting the word about the revu day spread01:36
bdrungstalcup: maybe somewhere in the middle of now and FF?01:36
stalcupwith FF two weeks away, i was hoping we could see a good turn-out for 3 a week01:37
stalcupthat would give us 6 days01:37
stalcupi am afraid anything older than 6 months is time wasted for some people01:38
bdrungstalcup: you was thinking about more than one of them?01:39
stalcuphoping more than thinking01:39
stalcupwe could also ask for a push for 2 or three days01:39
stalcupie, tues thru thurs01:40
* stalcup doesn't know what would get the most support01:40
stalcupif it's just one day, i'm sure we'll miss out on people reviewing01:41
ajmitchthe problem is more getting people willing to review01:43
stalcupit just seems to get harder every cycle01:44
ajmitchbecause the queue doesn't really get shorter01:44
bdrungajmitch: i am working on getting the sponsors queue shorter. everything else comes after01:44
stalcupright, its out right silly long right now01:45
ajmitch& it's the usual problem of hoping that people will commit to helping with maintenance of the packages that they want pushed through REVU01:45
bdrungstalcup: let's select three days on three different weekdays01:45
stalcupi have no problem telling someone their software is crap, even if it is packaged perfectly01:46
bdrungstalcup: i begin with complaining about the packaging and after they fix it, i send them to debian - no need to test it :)01:47
stalcupI threw out Tues thru Thurs because no one likes extra stuff on Monday.  Tuedsay they start to let their mind wander, reviweing is the perfect distraction.  By Friday everyone is burned out for the week.01:47
bdrungstalcup: one thing for improving revu: voting wich application should be in the archive -> count the "affects me too" on the needs-packaging bug01:48
bdrungstalcup: ok01:48
stalcuphrm01:48
stalcupnot a bad idea01:49
bdrungstalcup: that's the reason why i looked at openshot in the previous release cycle01:49
stalcupin fact, (this brings up an old argument) maybe it should be suggested that only *needs packaging* bugs or some other method should allow new apps into REVU01:50
stalcupbackporting is another laggard01:52
stalcupbrb01:52
bdrungstalcup: possible. look into debian/changelog, grab lp bug, check if lp bug is a open needs-packaging bug01:52
=== Zhenech_ is now known as Zhenech
shadeslayerfreeflying: nah.. im doing it the old debian-> ubuntu way03:35
stalcup404:10
hyperairZhenech: ping.06:17
dholbachgood morning08:16
and471hi guys, I am trying to create a pbuilder environment, but it fails everytime08:24
dholbachand471: what's the error message can you put it on paste.ubuntu.com?08:25
and471log is here http://pastebin.ubuntu.com/472094/08:25
and471dholbach, hey :) log is ^08:25
dholbachand471: it's weird that it can't download all these packages08:26
dholbachand471: try adding this to ~/.pbuilderrc08:27
dholbachMIRRORSITE=http://archive.ubuntu.com/ubuntu/08:27
dholbachand   sudo pbuilder create --override-config08:27
and471dholbach, cool I shall try that, just to check, should I have COMPONENTS="main universe multiverse restricted" in my pbuilderrc?08:28
jpdsand471: That mirror looks fine: http://www.mirrorservice.org/DisplayScreen?action=print&media=projection08:28
dholbachand471: yep08:28
and471dholbach, jpds, okay trying again :)08:28
dholbachoh, it was lucid08:28
dholbachthen it's indeed weird08:29
and471dholbach, it has started failing to download packages again :(08:29
and471dholbach, is there a way to set a longer timeout or something?08:29
dholbachI really have no idea why that's happening08:30
and471dholbach, is my internet connection too sucky?08:31
dholbachI never thought that'd be a problem - I dunno08:31
jpdsand471: The other main GB mirror is http://ubuntu.datahop.net/ubuntu/ - it's usually gb.archive but I'm taking it down for maintenance.08:31
jpds(At some point)08:31
\shmicahg: zend-framework 1.10.7 is on its way....+ c/r on the debian zf package08:38
coolbhavihello all is the recent version of libtool having problems with libgtk2.0-dev?09:05
RhondaHmm. I can't upgrade a cowbuilder chroot from lucid to maverick, it complaints about "Unable to connect to Upstart".09:05
RhondaHow is that meant to work? Is maverick not supported anymore for chroots?09:05
coolbhavibecause i tried to build newest version of xchat and it failed with unhandled argument `/usr/lib/libgdk_pixbuf-2.0.la' and looking at the rebuild failures there are a lot of those errors09:07
tumbleweedRhonda: I've got an open bug for that09:08
tumbleweedpsmisc, right?09:08
maxwellianIf we're sending a patch to the original upstream, is it rude not to subscribe to the mailing list?09:11
gesercoolbhavi: that .la file is gone but some other .la files still reference it -> they need to get fixed09:11
coolbhavigeser, ah okay! thanks!09:12
tumbleweedRhonda: err, procps I meant. bug 60289609:12
ubottuLaunchpad bug 602896 in procps (Ubuntu) "Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused" [Undecided,Confirmed] https://launchpad.net/bugs/60289609:12
Rhondatumbleweed: Yes, procps.09:12
Rhondatumbleweed: Thanks for the headsup, then I can stop investigating further. :)09:13
RhondaAlright, will do a --login and apply the patch from there interactively. :)09:13
Zhenechhyperair, pong09:49
\shsiretart: I didn't get the attachment of your mail...09:50
hyperairZhenech: have you forgotten about ctpl and geany-plugins? =)09:50
hyperairZhenech: FF's coming up, and if those two don't get into debian in time, i'll just -0ubuntu1 them into maverick first.09:51
hyperairdo you mind if i do that?09:51
Zhenechi didnt forget09:54
Zhenechmind throwing me the source again? :)09:54
* hyperair digs in his email10:00
hyperairZhenech: http://bugs.debian.org/57950910:01
hyperairZhenech: http://mentors.debian.net/debian/pool/main/c/ctpl/ctpl_0.2.2-1.dsc10:08
Zhenechhyperair, is the maintainer somewhere on irc?10:08
Zhenechyeah, got it :)10:08
hyperairhmm that i'm not so sure..10:08
Zhenechhyperair, geany plugins is currently the only revdep for that, right?10:11
hyperairZhenech: pretty much so.10:11
Zhenechcould you drop the .a file from -dev.install, rebuild the package and see whether geany plugins still build?10:12
hyperairZhenech: not at the moment. soffice takes up too much RAM for me to do a build.10:28
hyperairZhenech: i'll give it a go tonight10:28
Zhenechhyperair, i'm vac tomorrow till the 8th…10:32
hyperairhmm10:32
hyperairnice timing =p10:32
hyperairlemme poke my sbuild and see if it still runs.10:32
Zhenechhyperair, basically the package looks great10:37
Zhenechi for myself would like to see the .a file away, policy 3.9.1 and done10:38
hyperaireh, there's a 3.9.1 now?10:39
hyperairZhenech: what's wrong with the .a?10:39
micahg\sh: thanks10:40
\shmicahg: uploaded already...10:41
Zhenechhyperair, its old and should not be used when pkg-config is there10:42
hyperairZhenech: i see. but what about those who want to compile static apps?10:42
Zhenechhyperair, dont do that? :)10:44
hyperairZhenech: you know, some of those people who want to come up with binaries that run on all distros?10:44
hyperairZhenech: removing .a means you can't, any more.10:44
hyperairwell, unless you recompile all your libraries into a separate prefix, which sucks.10:45
hyperairgrr. ftp.tw.debian.org is broken.10:45
Zhenechhyperair, well… the problem is: when there is an .a it will pull linker flags from there maybe and overlink the binary (shared)10:46
hyperairoh10:47
hyperairthat would be bad.10:47
Zhenechyepp, thats why i think .a files should die :)10:52
hyperairZhenech: uh hell, it seems my geany-plugins packaging changes have disappeared O-o11:02
Zhenechgreat :_11:03
hyperairZhenech: lemme just try adding ctpl and no changes and see what happens.11:06
alf__Hi all! Anyone interested in reviewing glmark2 (a benchmark for OpenGL (ES) 2.0) [LP: #605901] [http://revu.ubuntuwire.com/p/glmark2]11:12
hyperairZhenech: it works.11:17
hyperairZhenech: i'll prepare the geany-plugins properly later on11:18
quadrisproslangasek, hi, why the sync of dssi from debian is blacklisted?11:56
quadrisproI see bug #305268 right now but there is no explanation in the report11:57
ubottuLaunchpad bug 305268 in dssi (Ubuntu) "Please sync dssi 0.9.1-3 (universe) from Debian unstable (main)." [Wishlist,Fix released] https://launchpad.net/bugs/30526811:57
Laney# ... due to orig.tar.gz mismatch:11:58
Laneydssi11:58
quadrisproLaney, ahh, thank you12:07
Laneynps12:08
X3geser that ntfs-3g 5.22 upstream is compiling away for karmic lucid and maverick12:34
=== yofel_ is now known as yofel
X3just the x86 binaries are delayed but rest is built12:35
X3despite it failing locally it worked on ppa12:35
X3i made it depend on fuse 2.8.1 should work12:37
=== dholbach_ is now known as dholbach
siretart\sh: sorry?13:13
\shsiretart: you send me an email regarding fai + lucid13:19
siretartwasn't this quite some time ago?13:22
\shsiretart: 28.07 ian beardslee13:26
\shthe attachment of his bug wea13:26
\shwas missing13:26
jetienneq. if a package is not modified when the package is made, should i had -ubuntu1 or adding nothing is ok ?.13:40
Bachstelzejetienne: "not modified" from where?13:44
jetienneBachstelze: from the original source13:44
jetiennethis is plain compilation to make a package13:44
Bachstelzethen it's -0ubuntu113:44
Bachstelze0 means "not in Debian"13:45
Bachstelzethe fist digit normally is the Debian revision from which the Ubuntu package was created13:45
siretart\sh: aah, let now I remember, let me recheck13:45
* Rhonda . o O ( har. I'll upload a package with debian revision -0 then! )13:45
siretartRhonda: that would cause quite some confusion :-)13:46
Rhondapolicy allows!13:46
siretart\sh: and you mean you cannot open the attachment? i.e. you don't see ian's mail?13:47
jetienneBachstelze: hmm ok13:47
\shsiretart: I can't read ians mail :)13:47
siretartok, I've now tried again slightly differently, does it work for you this time?13:47
Bachstelzejetienne: though normally if a package is not in Debian, you should get it into Debian first, then let it go into Ubuntu through the usual merge process13:48
jetienneBachstelze: ok. i will do ppa for now13:50
jetienneBachstelze: how hard it is to be included in Debian ?13:50
\shsiretart: I only have the headers :( no mail body13:52
Bachstelzejetienne: not hard, one your package is done, you post a RFS (Request For Sponsor) on the debian-mentors mailing list, and hopefully someone will upload it13:52
Bachstelzeonce*13:52
jetienneBachstelze: how can i convince them ?13:53
siretart\sh: is that a display problem of you mail client? can you have a look at the message source?13:53
\shsiretart: evolution -> open with gedit13:54
\shsiretart: only envelope + headers -> no body13:55
siretart\sh: so source in gedit shows you ian's mail?13:55
Bachstelzejetienne: depends what the package is, I guess, but generally the package description in debian/control is enough to see whether the package should be included or not13:55
Bachstelze(and the package has to be lintien-clean)13:55
Bachstelzelintian*13:55
jetienneBachstelze: hmm i will try... but from outside it seems quite random13:58
jetienneBachstelze: would be cool to know if some criteria on what is ok to include and what is not13:58
Bachstelzemostly everything is OK, Debian is not Fort Knox13:59
\shsiretart: just copy the body ;)13:59
Bachstelzeespecially if it's a completely new package13:59
jetienneBachstelze: do i have to go thru this process at every new versino ?14:00
Bachstelzea fork of an existing package that does not offer substantial improvements would not be ok, for example14:00
Bachstelzejetienne: yes, or at least until you become a Debian Developer and get upload rights to the archive14:00
Bachstelzesomeone has to upload it for you14:01
jetienneBachstelze: ok so it will lag quite a lot behind :)14:01
siretart\sh: yeah, I can resend it, but I'm curious, is the problem in my or your MUA? is the message now contained in the mail or not?14:01
\shsiretart: nope..only the header...last mail from you 14:4714:01
jetienneBachstelze: ok thanks for your help14:02
\shsiretart: thinking about enabling bug tracking for the LP fai team...14:03
siretartisn't the distro fai bugpage enough?14:04
\shsiretart: as we don't have distro packages for fai in lucid ??? and I'm not quite sure if I would upload fai before FF into maverick...14:05
siretart\sh: didn't we have a standing freeze exception for fai?14:06
siretartI remember something like that14:06
\shsiretart: if you find something, because I don't know and I'm not sure ;)14:06
siretartI'm sure we had, and I'm confident that we can get it again14:07
siretarthow about uploading your packages as they are to maverick now14:07
siretarttargeting to install lucid14:08
siretartthen we could even consider backporting it14:08
\shsiretart: hmmm....14:08
\shsiretart: what was the bug ian wanted to report?14:08
siretartnow idea14:09
siretartno idea14:09
siretartthat's why I forwarded the mail to you ;-)14:09
\shsiretart: lol...copy the mail body pls...so I can have a look, eventually fix it and uploading to ubuntu-m release ;)14:09
siretartI already did?14:10
jetienneq. is it ok to ask ppa questions here ?14:10
\shah there it is14:10
siretartk, starbucks now. cultaer14:10
\shsiretart: have fun :)14:10
=== menesis1 is now known as menesis
bdrungDktrKranz: when will you release ubuntu-dev-tools 0.101?14:50
DktrKranzbdrung: should I? :)14:57
bdrungDktrKranz: yes, especially due to the updated man pages14:58
DktrKranzbdrung: jokes off, I see there are a lot of changes, maybe we could consider to do soo soon14:58
bdrungDktrKranz: define soon14:58
DktrKranzbdrung: I can do it this evening, or at worst tomorrow evening, both for maverick than unstable14:58
DktrKranzs/than/and/14:59
bdrungDktrKranz: great. (but isn't it the other way around? unstable and than maverick?)14:59
DktrKranzbdrung: it's usually uploaded in ubuntu first, then I "merge" it in debian15:00
bdrungDktrKranz: you can upload it to unstable and then use syncpackage on the uploaded dsc15:01
DktrKranzbdrung: it's not perfectly in sync, uploaders change a bit15:12
=== ogra_ is now known as ogra
bdrungDktrKranz: can't we get rid of these changes?16:01
DktrKranzbdrung: if I put "Ubuntu Developers" as Maintainer, and myself in Uploaders, sure16:03
DktrKranzthat's the only diff, IIRC16:03
DktrKranz(just because I want a "real" person behind the package)16:03
bdrungDktrKranz: that's the ubuntu->debian diff: http://paste.debian.net/82046/16:03
DktrKranzyeah16:04
bdrungDktrKranz: i like the idea of having "Ubuntu Developers" as Maintainer, and you in Uploaders16:05
=== mathiaz_ is now known as mathiaz
bdrungDktrKranz: if the version is the same, the content should be the same16:06
* DktrKranz looks if there are other packages with *Ubuntu* in maint16:06
DktrKranzjust to be coherent :)16:06
bdrungDktrKranz: how do you do this check?16:07
Laneygrep-dctrl can do it16:09
DktrKranzbdrung: projectb database, udd, Maintainers/Uploaders file on Indices, grep-dctrl16:10
DktrKranzthere are several sources16:10
Laneywhat is projectb?16:11
DktrKranzLaney: the monster behind Debian16:11
Laneysomething to do with dak?16:12
DktrKranzyeah, dak interface itself with projectb16:15
DktrKranza lot of "Ubuntu" teams: http://pastebin.com/cthitwXP16:17
=== fta_ is now known as fta
LaneyI don't think it should be a problem16:18
Laneyjust selecting the list where maintainer emails should go16:18
DktrKranzqueued (the thingie which processes the uploads) and dak (when accepting package) will spam a bit16:20
Laneyyes16:20
LaneyI don't know which ML would be appropriate for that16:20
DktrKranzI don't remember if we have a email addres for such a packages16:20
Laneymaybe a separate LP/alioth team16:20
LaneyLP team with ubuntu-dev as a member would work16:21
DktrKranzalso, ubuntu-devel-discuss would be spammed for bugs reported in debian, so a ubuntu-dev team on alioth could be the answer16:25
LaneyLP is probably better16:26
Laneyas teams can have MLs now16:26
slangasekquadrispro: because the source tarballs are (have been) different and unsyncable16:26
slangasekquadrispro: can be unblacklisted once a new upstream version happens16:26
DktrKranzah, right16:26
LaneyDktrKranz: I'll register it if you'd like16:29
Laneyalthough if it's just going to be for a mailing list then maybe a proper one is better16:29
bdrungDktrKranz: A ML for ~ubuntu-dev16:29
LaneyCan it be made clear that this ML is for maintenance of Debian packages?16:31
DktrKranzYeah, could go16:31
LaneyI worry that a mailing list attached to ubuntu-dev will be misleading16:31
DktrKranzLaney: maybe something like "ubuntu-dev-packages@lists.something" could do16:50
Laneyyep16:50
DktrKranzand description "Lists for ubuntu-dev maintained packages in Debian"16:50
LaneyI have no idea how to have a lists.ubuntu.com list created16:50
Laneymaybe ldo would be easier16:50
DktrKranzin LP maybe?16:50
Laneyyeah you can do it with teams16:51
DktrKranzI don't think an "official" list should be created16:51
DktrKranzit will be a low traffic one :)16:51
Laneyseems a bit weird to register a team just to have its list though16:51
Laneyoh well, I'll do it16:52
Laneyhttps://launchpad.net/~ubuntu-debian-maintainers16:54
DktrKranzI thought multiple MLs could be created for a single team16:55
LaneyI don't think so16:55
DktrKranzso, one for ~ubuntu-dev could be added as well16:55
LaneyDktrKranz: ubuntu-debian-maintainers@lists.launchpad.net17:00
DktrKranzbdrung: sounds good for you to have Maintainer Ubuntu Developers <ubuntu-debian-maintainers@lists.launchpad.net> ?17:01
bdrungDktrKranz: ubuntu-debian-maintainers@lists.launchpad.net is not perfect, but ok17:02
=== fta_ is now known as fta
Laneyerm17:02
DktrKranzit's just a collector to avoid being spammed17:02
bdrungDktrKranz: i meant the name17:03
LaneyI just thought... will it accept mails from Debian?17:03
DktrKranzbdrung: suggestions for a better one?17:03
bdrungDktrKranz: sadly, no17:05
DktrKranzin the end, name is just a placeholder, what really matters is a functional email address17:06
Laneywe definitely check that emails won't bounce17:06
DktrKranzor ftpteam will get spammed about it, and file RC bugs ;)17:06
DktrKranzLaney: I can send one from ftp-master, to see if it bounces17:07
Laneyif you wish17:07
RainCTLaney: LP mailing lists queue non-member posts for review by a team admin, if that's what you were asking17:08
LaneyRainCT: I was. Can they be made to be open?17:09
RainCTLaney: No. And I don't recommend it either, you'll get spammed to death17:10
LaneyDebian lists manage fine17:10
DktrKranzArchive Administrator <dak@ftp-master.debian.org>17:12
DktrKranzups17:12
RainCTLaney: Maybe you can ask some LP guy to set it open for you. iirc they use Mailman behind the scenes.17:13
LaneyRainCT: yep will do17:13
Laneyor whitelist *.d.o17:13
jetienneq. how to have a dh_make which understand mit license ?17:14
LaneyWrite your own copyright file17:14
jetienneLaney: how do i do that ? do you have pointer or keyword17:16
Laneyjetienne: Look at an existing one on your system — grep MIT /usr/share/doc/*/copyright17:17
jetienneLaney: thanks17:19
DktrKranzbdrung: for the time being, maybe a "ubuntu-dev-tools maintainer" could be fine17:21
DktrKranz+s17:21
bdrungDktrKranz: as name or email address?17:22
DktrKranzname17:22
DktrKranzfor email, we need one which doesn't bounce17:23
bdrungDktrKranz: will we get launchpad unbounced?17:24
bdrungRainCT: ping17:25
DktrKranzI could "intercept" those to ftp-master.d.o, but I guess other team members wouldn't be happy to get "subscription" mails17:25
DktrKranzso, I hope we can whitelist *debian.org addresses17:26
* bdrung hopes too17:26
DktrKranzthere are three, dak@ftp-m.d.o, installer@ftp-m.d.o and *@bugs.debian.org17:27
Laneywhat about bug mails17:31
Laney?17:31
LaneyThey come from the originator, don't they?17:31
=== fta_ is now known as fta
LaneyDktrKranz: I don't think we're going to have any luck here18:06
Laneyalioth list might be our best option18:06
=== fta_ is now known as fta
DktrKranzLaney: probably18:36
porthoseDktrKranz, do you have time to sponsor an RC bug fix into debian?18:40
RainCTbdrung: Sorry, did you want anything or was it so that I see the ML question?18:42
bdrungRainCT: yes, i want to ask you, if i can replace suspicous-source with a complete rewrite in python?18:43
RainCTbdrung: sure18:43
bdrungRainCT: it uses python-magic to determine the file types18:44
bdrungRainCT: thanks18:44
=== fta_ is now known as fta
DktrKranzporthose: sure18:45
porthoseDktrKranz, http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-5.dsc18:45
=== fta_ is now known as fta
DktrKranzporthose: I'd set urgency=medium18:53
DktrKranzLaney, bdrung: any suggested short name/extended name for an alioth project19:01
bdrungDktrKranz: short name: ubuntu-dev19:04
bdrungDktrKranz: i want to add the rewrite of suspicious-source before the release of 0.10119:05
DktrKranzOK, I'm going to ask for the team creation19:05
MuscovyI'm trying to import a package to Ubuntu (http://revu.ubuntuwire.com/p/shellinabox) but despite the .dsc file listing the .orig tarball, the tarball is never uploaded. Could anyone help?19:06
tumbleweedMuscovy: the .changes file needs to list the .orig tarball19:06
bdrungMuscovy: build the source with debuild -S -sa19:06
MuscovyOk.19:06
MuscovyThanks, it's uploading now.19:08
porthoseDktrKranz, done :) http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-5.dsc19:10
DktrKranzporthose: did you change just that?19:11
porthoseDktrKranz, yes19:11
DktrKranzI already adjusted it locally, so I avoid to refetch it :)19:11
porthose:)19:12
DktrKranzdone19:12
porthosethx :)19:12
Laneybdrung and DktrKranz: Isn't pkg- the usual prefix?19:13
bdrungthen pkg-ubuntu19:14
LaneyI wonder if in future it could be expanded for other packages mainained by ubuntu developers19:15
Laneybut, no, they probably shouldn't be isolated like that19:19
DktrKranzI asked for generic "ubuntu-dev", in case it will be useful for other things than package management19:19
DktrKranzin case, I'll turn that to pkg-ubuntu, or similar, if asked19:19
Laneyok19:20
rippslooks like somebody forgot to upload libcompizconfig to maverick before updating compiz19:26
plarsI have a package that I've submitted to REVU a while back, but nobody seems to have commented on it yet.  The upstream author notified me today that he has a new upstream version.  Would it be more appropriate to update the original package with the new upstream version, or add a new dch entry for the update and upload that, or just wait to see if it goes in, and do it as an update after the fact?19:35
shadeslayerplars: update old package and upload to revu19:36
plarsshadeslayer: ok, will do. Thanks19:36
shadeslayeri.e get new tarball + old debian folder19:36
shadeslayerand go from there ;)19:36
plarsbut just keep the old version right?19:36
plarswell19:36
plarsI guess I would have to change the version, since it is a new upstream, but don't add a new changelog entry is what I mean, right?19:37
shadeslayerplars: ill show you a chagelog hold on19:37
shadeslayerplars: https://edge.launchpad.net/ubuntu/+source/kde4libs/+changelog19:38
shadeslayersee how the version keeps getting bumped19:38
plars(still trying to get there... :)19:39
plarslp timing out bad for me today19:39
shadeslayerplars: yeah seems so.. some people complained on #launchpad.. i guess its because of maverick alpha 319:40
shadeslayertoo much pressure19:40
plarsshadeslayer: I understand how to make new entries, just that I figured it would seem kind of odd to have a brand new package with more than one debian changelog entry in it, especially since one of them references a version that was never uploaded to the archive19:41
shadeslayerhmm.. id rather have a changelog entry about that package.. since it was uploaded to revu19:42
plarsok19:42
micahgshadeslayer: idk about that...that seems weird since REVU isn't an official repo and just a staging ground19:45
shadeslayermicahg: but when someone views that package, and has also viewed it earlier, then the guy/gal might be in a fix as to what changed19:46
micahgshadeslayer: isn't there a comment system in REVU?  you certainly can't have a version in the first changelog as if it's released, it would have to be UNRELEASED for the first changelog if anything19:46
shadeslayeryes, the first entry will have to have UNRELEASED19:47
LaneySome people prefer both, sup to you/the sponsor19:47
shadeslayeri thought plars would know about that  :)19:47
shadeslayerLaney: yeah UNRELEASED is usually followed in the bzr system.. and i find that the best :)19:48
shadeslayerbut then again.. im not a MOTU/Sponsor19:48
* micahg neither :)19:49
shadeslayerLaney: btw suppose i have contributed towards main more ( like core KDE packages ) will that be considered in MOTU application?19:50
LaneyYou can put all of your stuff down19:51
shadeslayerdid a few merges/syncs in universe only19:51
shadeslayeroh goody19:51
Laneycan't comment on what the DMB will do with it19:51
shadeslayerhmm.. ok19:51
micahgshadeslayer: you don't do anything w/the universe KDE pacakges?19:54
shadeslayermicahg: i try to :P19:54
shadeslayerbut usually get sidetracked into main19:54
micahgshadeslayer: that counts towards MOTU :)19:54
shadeslayeryes i know19:55
shadeslayeri did a few merges and stuff... but then got pulled into main19:55
micahgshadeslayer: so, you might want to go for kubuntu-dev first and then MOTU later19:55
Laneybut if you're not interested in universe packages, maybe another team is more appropriate than MOTU19:55
* micahg did something similar19:55
shadeslayerLaney: i am interested.. but i get handed main stuff by #kubuntu-devel :P19:56
Laneymore experience is always good19:56
shadeslayerlike currently me and Quintasan are reviving project neon which provides nightly kde builds19:56
shadeslayerand then i got my first debian package into sid19:57
shadeslayerwhich was syncd to ubuntu..19:57
shadeslayerLaney: https://edge.launchpad.net/~rohangarg/+related-software << as you can see.. not alot of universe work :)19:59
Laneyperhaps you want kubuntu developer19:59
shadeslayerhmm.. maybe.. i was thinking of MOTU -> Kubuntu Dev20:00
shadeslayerbut might as well do it the other way around20:00
Laneysuch a linear path doesn't have to exist any more :)20:01
shadeslayeri know.. lex79 was approved as kubuntu dev, but was not a MOTU20:01
Quintasanshadeslayer: just get me or/and someone "high-ranked" from #kubuntu-devel to attend your MOTU meeting20:06
Quintasan:P20:06
shadeslayerlol20:06
* shadeslayer grabs Riddell apachelogger and Quintasan 20:07
shadeslayerJontheechidna aint around :P20:07
shadeslayermaco too! :D20:07
apacheloggerhuh?20:07
apacheloggerwhat is this highlighting in the middle of the night about?20:08
macoim not high rank in kubuntu20:08
shadeslayermaco: hows the python confrence20:08
gesershadeslayer: get them all comment (or even endorsements) on your application page20:08
macoi updated a kubuntu package successfully once20:08
macoshadeslayer: python conference?20:08
macoand unsuccessfully once as well :P20:08
shadeslayerarent you at one?20:08
macono20:08
macoim at debconf20:08
shadeslayerfrom identi.ca feed : ..  im in the python talk .. :P20:09
Laneyshadeslayer: I recommend you do more work on universe packages to see if motu is what you actually want20:09
shadeslayerLaney: ok20:09
Laneyor just carry on working with kubuntu if that's what you like :)20:10
gesershadeslayer: that one probably: http://penta.debconf.org/dc10_schedule/events/570.en.html20:10
macoshadeslayer: well if i was at a python conference, thatd describe ALL of them, now wouldnt it?20:10
shadeslayergeser: ah20:10
shadeslayermaco: yep.. hows debconf then? :)20:11
macopretty good. im gonna go wander to the hacklab for a bit of poking at qt20:11
apacheloggerdebconf \o/20:12
* apachelogger never gets invited to debconf ... supposedly needs to do more work in debian20:12
geserapachelogger: one needs an invitation for debconf? I assumed one can attend if one wants20:13
shadeslayerall the fun stuff happens in the US/Europe :P20:18
apacheloggergeser: I am so lazy I only act upon invitations ^^20:18
tumbleweedshadeslayer: yeah, sucks to be in a neglected part of the world :)20:19
shadeslayeryep20:19
shadeslayerparticulary india where there is not alot of FOSS movement20:20
apachelogger...one must invent one's own fun then20:20
apacheloggerlike they did with camp KDE20:20
shadeslayerbye everyone.. night20:21
dyfetogra: ping20:23
=== gnomefreak76 is now known as gnomefreak
=== fta__ is now known as fta
vishdo debian/control description changes have to be done by UIF or documentation string freeze , or does the Freeze not matter for changes in /control?21:24
=== fta_ is now known as fta
james_wvish: the freeze is for translators and documenters, so it depends on whether they are going to be translating the strings, including them in documentation or screenshots etc.21:46
vishjames_w: ah , ok. thanks21:54
=== fta_ is now known as fta
=== fta_ is now known as fta
valavanisalexHi all - can anyone help with a package merge issue?23:12
=== JanC_ is now known as JanC

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