/srv/irclogs.ubuntu.com/2011/11/07/#ubuntu-motu.txt

broderhmm...does anybody do processing on lintian.d.o for things like tags over time?00:58
highvoltagehey broder02:14
highvoltagedo you know if there's a script or site that can show me packages that are in universe but not in debian?02:15
ajmitchhighvoltage: why yes there are scripts :)02:29
ajmitchhttp://qa.ubuntuwire.com/mdt/universe.html02:29
highvoltagethanks, ajmitch02:29
highvoltageNot in Wheezy : 1135 packages02:30
highvoltageI honestly didn't expect that number to be so high.02:30
ajmitchthat includes a lot of i18n packages, packages removed from testing, etc02:30
ajmitchusually the comparison is between sid & the current ubuntu release, but the LTS is special02:31
jbichaand that's not including main packages02:41
ajmitchright, there's probably quite a few more in main02:42
highvoltageyeah, at least the packages in main are probably cared for. I'm wondering about packages that should be dropped/orphaned in universe. (stuff like feisty-session-splashes, potentially)02:44
micahghighvoltage: we need to do a lot of cleaning before the LTS, so feel free to start now :)02:45
highvoltagemicahg: yep. I'll do my part. If that list of 1135 packages could be halved for 12.04 then that would already be good I think.02:47
highvoltageso that script just compares between wheezy and precise? I guess some of those packages might be in unstable too02:47
micahgyep, some are updated in unstable, some removed02:47
ajmitchhighvoltage: I can get you a list of the difference between unstable & precise02:48
ajmitchjust not as pretty as mdt02:48
micahgwell, that's not entirely good either, we don't want everything from unstable02:48
micahgah, you mean in precise but missing in unstable02:49
ajmitchyes02:49
micahgcarry on :)02:49
highvoltageajmitch: yeah, I need to learn how that works. Ideally I'd like a column that says when the package was last updated, and how many bugs it has against it02:49
ajmitchmicahg: I have that list somewhere as a byproduct of the rcbugs list02:49
highvoltagewould be nice to have some kind of idea of which packages are bad and kind of abandoned02:49
ajmitchhighvoltage: that's possible, might be best to do that with UDD02:49
broderhighvoltage: i think tumbleweed put a report kind of like that together02:50
brodersomething like "packages that have gone the longest without being uploaded"02:50
broderlet me see if i can find it02:50
micahgwell, there's a semi-automated script I think which can remove stuff that's been removed from Debian where we have no diff, maybe we can get that run before we start to file removal requests02:50
highvoltagebroder: that would make sense, tumbleweed is always 2 steps ahead of me :)02:51
ajmitchhttp://qa.ubuntuwire.com/oldmerges/02:51
broderajmitch: that's the one02:51
broderalso, lintian run is on "z" :)02:52
ajmitchit doesn't include packages that haven't been touched for years in debian & are unmodified in ubuntu, but that probably wouldn't be hard to get either02:52
ajmitchbroder: nice02:52
broderthough i bet it'll take it a while to generate the html reports after it finishes02:52
broderajmitch: i think those packages are definitely a secondary concern for us02:52
ajmitchbroder: I need to sort out stuff on mekaneck with wgrant, so that I can set up a CNAME record for lintian.uw.o02:53
ajmitchbroder: agreed, the oldmerges page should keep us busy enough :)02:53
broderajmitch: no worries. i'll keep working on the output some anyway02:54
ajmitchbroder: you plan to push the lintian reports there regularly?02:55
broderyeah, i was planning to put it on a cron job02:56
ajmitchfair enough, tell me if you need me to set anything else up02:56
broderi think all i need is somewhere to throw it02:57
ajmitchsure, you can put it somewhere in your home dir & I'll point apache to it02:58
broderok. sounds good. i guess i'll push it to people.uw.o for the time being until we get the CNAME setup02:58
ajmitchit's the same host, so whatever works :)02:58
ajmitch"arkose exists in precise (universe) but not in Debian" - not the most detailed output there per package, I guess02:59
wgrantajmitch: What's up?03:02
ajmitchwgrant: can you check if I have sudo access on mekaneck?03:04
wgrantajmitch: You seem to...03:05
StevenKajmitch: sudo -l ?03:06
ajmitchit's more likely that I can't recall which password I'd used at some time in the distant past on that machine, but I've never had a ~/.sudo_as_admin_successful on there03:07
StevenKajmitch: That is a slightly seperate problem :-)03:08
ajmitchStevenK: yeah, a pity that sudo doesn't just trust my ssh key :)03:09
StevenKHaha03:09
funkyHatajmitch: alias sudo="ssh root@localhost"03:26
funkyHat;)03:26
ajmitchfunkyHat: /win 2803:30
ajmitchoops :)03:30
* funkyHat looks in window 28. Huh, that's just #ubuntu-devel. ;)03:30
ajmitchfunkyHat: yeah, that'd work with agent forwarding, and if the public key was allowed for root as well03:30
ajmitch#ubuntu-devel should be in your top 10 at least03:30
funkyHatIt would break if you tried to use -i or anything else though03:31
funkyHatajmitch: I have bindings for windows up to 10003:31
ajmitchstill no excuse :)03:31
funkyHatAnd -motu is 8, so -devel being 28 is nice because they have almost the same keybinding ⢁)03:32
funkyHat(I have a whole bunch like that, -meta sits on top of #u for example)03:32
funkyHatHow sad ❡⢁)03:33
ajmitchbroder: lintian stuff still rsyncing?03:52
broderajmitch: uh...it seems to have followed a recursive symlink :)04:49
broderajmitch: there04:51
broderhttp://people.ubuntuwire.org/~broder/lintian/ (note: for those playing along at home, url not permanent. skinning not permanent. etc.)04:52
ajmitchbroder: right, I was looking at the tags there & found I couldn't access them earlier :)04:55
ajmitchI'll point lintian.uw.o there04:55
brodercool :)04:55
wgrantHmmm.05:12
wgrantI wonder if I still have my Ubuntu lintian instance around somewhere.05:12
wgrantI ran one for a little while years ago, but then liw started one in the DC.05:13
broderhttp://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ is still the canonical source for "ubuntu policy", in so much as it exists distinct from "debian policy", right?05:13
broderok. made a half-hearted effort to ubuntu-ify the output :)05:23
ajmitchbroder: how long did it take to run over the whole archive?05:29
broderday and a half, i guess?05:30
brodermaybe longer05:30
ajmitchso I guess you won't be updating it too often05:30
broderwasn't really paying attention, and had to restart it a couple of times05:30
broderit does incremental updates05:30
ajmitchah good05:30
ajmitchI was about to ask that :)05:30
broderajmitch: ok. lab and sync is on a cron job now05:55
=== jussio1 is now known as jussi
dholbachgood morning08:38
tumbleweedhighvoltage: you are actually looking for http://ubuntu-dev.alioth.debian.org/cgi-bin/neglected-packages.cgi11:05
=== dpm is now known as dpm-lunch
=== medberry is now known as med_temp
highvoltagesladen vs kinect: http://www.youtube.com/watch?feature=player_embedded&v=sxZplO4XPpE13:29
sladendamn youtube13:36
=== yofel_ is now known as yofel
genjixtumbleweed: you mentioned before about debian unstable for a library with a constantly changing API/ABI. is there some kind of thing where i can hand over the packages to a maintainer?15:07
genjixi already made the packages but i have no idea what i'm doing because i'm a lacklustre maintainer15:08
genjixhttps://launchpad.net/~genjix/+archive/libbitcoin15:08
=== dpm-lunch is now known as dpm
=== dholbach_ is now known as dholbach
=== Quintasan_ is now known as Quintasan
jdstranddholbach: hey, do you know who owns the ubuntu fridge calendar?15:36
dholbachjdstrand, you should be able to make modifications if I read https://wiki.ubuntu.com/Fridge/Calendar correctly15:37
jdstranddholbach: yes. I was able to add a calendar15:38
jdstranddholbach: err, calendar item15:38
jdstranddholbach: problem is, I want it to forget about one that is not in a calendar I control15:38
jdstranddholbach: ie, kees'15:38
dholbachgood question15:38
jdstranddholbach: 'Security Team Catch-up' should be forgotten by the Ubuntu Fridge clendar15:39
dholbachmaybe the guys in #ubuntu-news (or was it #ubuntu-news-team) know?15:39
jdstrandI'm fairly certain kees can't access that calendar any more too15:39
* jdstrand tries15:39
jdstranddholbach: thanks15:39
Quintasandholbach: Your air hockey match should be up on internets soon, depending on when my ISP unbreaks my internet :)15:41
dholbachQuintasan, oh man.............. it's not like I was actually good :)15:42
QuintasanWell, but the idea of playing with two of those disks was superb15:43
dholbachok, let's wait for the video then ;-)15:44
tumbleweedgenjix: Actually, I was talking about experimental. Having libraries like that in ustable isn't easy because you'll have lots of transitions to handle.16:51
genjixtumbleweed: ok17:10
genjixbut same thing still17:10
highvoltage+    Has there been a recent scrub to highlight the orphaned packages in Universe? It might be useful to make them visible and put them up for adoption? Failing that, possibly look at removing from the archive?17:26
highvoltagedholbach: should that perhaps also be a work item? ^^^ (to initiate/drive a scrub?)17:26
dholbachmaybe17:28
dholbachor bring it up on the mailing list?17:28
highvoltageok17:33
LaserJockso if I have a package in Oneiric that segaults, and an to fix it I need to fix a library and then rebuild, would I need to do 2 separate SRUs?18:04
LaserJocks/and an/and/18:04
AnAntHello, what was the last sync from Debian testing to precise ?18:04
AnAnts/what/when18:04
mewerner_arandIs it not ongoing still?18:06
geserAnAnt: try asking an archive admin in #ubuntu-devel18:06
AnAntgeser: how can I know archive admins ?18:07
gesersimply ask and hopefully someone will answer18:07
micahgLaserJock: yes, well, 2 uploads, I think 1 bug can track both18:08
LaserJockif the library is used to build other packages would I have to rebuild those too or is it enough to leave them alone?18:09
LaserJockthere are only a handful, but I'd rather not have to SRU a bunch of packages to fix 118:09
micahgLaserJock: are you breaking ABI with the fix?18:10
jtaylordepends, if the soversion changes yes, else no18:10
LaserJockthere were just headers that failed to be installed via the .install18:10
LaserJockthe broken packages need those headers, the code isn't changing18:11
jtaylorhow did the rdeps build then in the first place?18:11
jtaylorwithout the headers18:11
LaserJockthey must not have needed those particular one18:12
LaserJocks18:12
jtaylornot needed, or disabled some features?18:12
LaserJockI don't know yet18:12
AnAntis there a reason that the following packages are not sync'ed from Debian testing: xpra & xcb-util-renderutil18:13
jtaylorshould be checked, it would be problematic if yes, as the next update of the rdeps will enable new features not previsously in the release18:13
micahgAnAnt: there probably hasn't been a sync since before UDS18:14
AnAntok18:14
ajmitchxpra is version 0.0.6+dfsg-1ubuntu1, so it needs merged or manually synced after explaining why the diff can be dropped18:14
AnAntajmitch: oh18:14
highvoltagemjeanson: btw, here's the link to the ding-libs source package I last uploaded: http://mentors.debian.net/package/ding-libs18:15
jtaylordoes request-sync also only look in testing?18:15
jtaylorit always complains that ubuntu version is newer18:15
jtayloralthough its not since 3 days18:15
micahgAnAnt: the other one is a new package apparently and those are syncd less frequently than what's already in then archive18:15
AnAntmicahg: ?18:16
AnAntmicahg: why's that ?18:16
micahgdifferent set of commands I think?18:16
micahgAnAnt: if it's needed relatively soon, you can file a sync request (still has to go through NEW though) (idk about syncpackage and new packages)18:17
AnAntmicahg: ok, thanks18:18
geserNEW syncing also includes checking if the new binary packages don't "overwrite" other binary packages from existing source packages and also processing of the NEW queue (accept/review the source package)18:18
jtaylorhm is something wrong with importing new versions from debian?18:18
jtaylordeleted my lpcache and its still not letting me sync ._.18:19
gesernew versions or NEW source packages?18:19
jtaylorjust version numbers18:19
gesercheck what LP knows about the package in Debian and Ubuntu18:19
jtaylorrequestsync thinks python-django-piston is newer in ubuntu than debian18:19
geserwhich package btw?18:19
micahgjtaylor: requestsync should be looking at testing, so that's correct18:20
jtaylorhow do I force it to unstable?18:20
jtaylortried setting the base version18:20
micahgjtaylor: -d unstable18:20
AnAntah, xpra is also a new package !18:20
AnAntand parti-all needs to be removed18:20
micahgAnAnt: ah, yes, new source, binaries are in already18:21
jtayloryey changelog not found ._.18:22
tumbleweedthat shouldn't be a blocker18:22
jtaylorok then the manual way ._.18:22
jtayloror can one already sync via a button in launchpad? if yes can someone do that? its an security update18:23
tumbleweedwe use a script (syncpackage) not a button18:23
AnAntmicahg: so, should a removal be requested for parti-all (because of the Ubuntu delta), or that isn't needed anyways ?18:24
tumbleweeda security update probably shouldn't have used urgency=low18:24
rryan`hi all, i just uploaded a package to REVU (my first) and I was wondering if anybody could spot-check it for me to see if there are any serious issues: http://revu.ubuntuwire.com/p/mixxx18:24
micahgAnAnt: yeah, if we have a diff, you can file that after the new source is sync'd though18:25
jtaylortumbleweed: I agree, it was a bit weirdly handled, debian stable hasn't got the update yet either18:25
tumbleweedrryan`: we're trying to get rid of REVU, and generally trying to get new packages in via Debian18:25
tumbleweedrryan`: but in this case, mixx is already in Ubuntu, are you trying to update it?18:26
AnAntmicahg: shouldn't the removal be requested first before syncing xpra (since both provide the same binary packages) ?18:26
LaserJockwhat's the best way to build a package if it requires a package not in the archives? PPA, local repo, some trick with pbuilder?18:26
micahgAnAnt: no, the new binaries will supersede the old ones18:26
AnAntmicahg: thanks18:26
rryan`tumbleweed : yup, we just released a new bugfix release18:26
broderLaserJock: PPA is probably most straightforward18:26
brodershouldn't have to do anything special - just upload the out-of-archive dependencies, then the actual package18:27
rryan`tumbleweed : oneiric onwards has 1.9.0+dfsg0-4, 1.9.2 is our latest version18:27
LaserJockbroder: make sense, thanks18:27
tumbleweedrryan`: I suggest you contact the debian maintainers of the package. Packages filter through from Debian to Ubuntu (unless there's a good reason for them not to)18:28
tumbleweed(also in this case, the maintainer is active in Ubuntu too)18:28
tumbleweedhttp://packages.qa.debian.org/m/mixxx.html18:28
rryan`tumbleweed: gotcha, thanks. I did send alessio a note but haven't heard back from him yet18:29
micahgindeed, also, that team is pretty open, so if you'd like to help maintain in Ubuntu/Debian, I'd suggest joining the team and doing it in the Debian Multimedia git repo18:30
tumbleweedrryan`: he was at UDS last week, probably still getting home / recovering. Give him a few days...18:30
rryan`tumbleweed : k, will do18:30
tumbleweed(assuming you poked him in the last week)18:31
tumbleweedjtaylor: synced18:35
jtaylorthx18:36
tumbleweedjtaylor: need release nominations for the bug?18:37
jtayloris already on the security sponsors todolist18:37
* tumbleweed should probably learn more about Ubuntu's security workflows at some point...18:37
jdstrandjtaylor: I suggest joining #ubuntu-security18:37
jtaylornot -hardened?18:38
jdstrandjtaylor: we have a role for processing sponsored patches18:38
jtaylorthats what I was told last time is the place to go :)18:38
jdstrandjtaylor: either. -security forwards to -hardened18:38
jdstrandUDS kinda put last week behind, but I think tyhicks may be looking at it18:38
highvoltageLaney: I see you got mentioned on bansheegeddon18:49
ajmitchhighvoltage: of course he would be18:49
ajmitchhighvoltage: he's part of the supersecretelite debian team that looks after such packages18:52
micahggeser: DMB?19:03
gesernow?19:07
micahggeser: yes19:16
geserforgot that due to DST change it's now an hour earlier for me19:18
micahgmdeslaur: ^^ you win :)19:19
ajmitchheh19:19
mdeslaurmicahg: hehe :)19:20
gesermicahg: what did he win?19:20
micahggeser: the right to say "I told you so" :)19:20
brodertumbleweed: have you pushed any of your requestbackport stuff anywhere yet? i want to experiment with writing a backport bugbot19:39
=== Amaranth_ is now known as Amaranth
=== Amaranth_ is now known as Amaranth
tumbleweedbroder: right, I think I finished that on the plane, let me test it and push it to a branch for you to play with20:56
blairi wrote commit and pushed it into a bzr branch to update python-rbtools 0.2 to 0.3.4.  the package is also in debian, so does the new ubuntu version number have "ubuntu" in it?21:03
blairas in 0.3.4-1ubuntu1 or should it be 0.3.4-1?21:04
ajmitchit would be 0.3.4-0ubuntu1 in that case21:04
* ajmitch saw that the maintainer hadn't replied to the 'new upstream version' bug filed in february21:04
blairi want to get this into the 12.04 release that i want to move our company to (from fedora13), is doing the work in ubuntu the best way, or having debian get the upgrade and doing a sync to ubuntu?21:05
ajmitchit'd be best to get it done in debian first & synced - you'd have until feature freeze to get that done21:06
ajmitchproviding an updated package for the debian maintainer to look at can be useful21:06
blairok, so take my bzr changes and make the same change to the debian package?21:06
ajmitchyes, though you'd be basing it off the upstream tarball21:08
blairright21:08
ajmitchthe debian maintainer may not find a bzr branch useful :)21:08
blairno, probably not :)21:08
ajmitchwas it much work to update it to the new version?21:08
micahgmentors.debian.net might be useful21:08
blairno, not too much work21:08
blairbut i had some questions:21:09
blair1) it's one debian policy version behind, does it need to be updated?21:09
blair2) in the bzr checkout, there's a .pc directory at the top level that had some patching info in it, it's not in debian's checkout or anywhere else, so i deleted it in my branch since it seemed like cruft21:09
ajmitchif you've checked that the package follows the policy updates in 3.9.2, then you could update it in debian/control21:10
blairyeah, i've been doing a few debian packages over the years, but definitely not an expert to know the differences between policy updates21:11
blairi did a git diff in the debian policy repository, but didn't see anything relevant21:11
ScottKThere's a checklist in the debian-policy package.21:11
ScottKIn general, I wouldn't worry about it.21:11
ajmitchhttp://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt also has it21:12
blairBTW, i'm a MacPorts committer and we have a policy where if a ticket isn't responded to in 3 days a non-maintainer can make a change, is there a similar policy in debian or ubuntu21:12
ScottKThere is actually Ubuntu policy not to update the policy version relative to Debian since it generates meaningless diff.21:12
ajmitchpolicy changes in minor version are generally minimal21:12
ajmitchScottK: I figured that it'd be ok to update the version in this case when offering it to the debian maintainer21:12
LaneyScottK: this is about preparing a diff for Debian (iiuc)21:12
ScottKblair: Debian has a similar policy for severe (release critical) bugs.  For Ubuntu there are no dedicated maintainers so anyone can fix anything.21:12
ScottKajmitch: True.21:12
ScottKLaney: OK.  Nevermind then.21:12
ajmitchblair: also, we're not going to hold up 0.3.4 from going into ubuntu if you can't get a response from the debian maintainer in a reasonable amount of time21:18
tumbleweedbroder: lp:~stefanor/ubuntu-dev-tools/requestbackport21:20
brodertumbleweed: cool. i'll check it out tonight21:21
tumbleweedbroder: my demo bug https://bugs.staging.launchpad.net/bugs/86091921:22
ubottuError: malone bug 860919 not found21:22
tumbleweednote that all the non-production launchpads don't know that precise is the current dev release, so play along21:22
* broder nods21:23
tumbleweeddogfood thinks we are on 'rusty robot' :P21:23
broderlooks reasonable21:23
blairajmitch, thanks, i'll prepare the patch for upstream and update the ubuntu tickets with the status21:23
ajmitchalright, thanks21:24
brodertumbleweed: that seems to have all the information we'd expect to show up in the bug report21:24
broderas a random thought, it might be cool to have a verification checklist in the "testing" section21:24
tumbleweedyes, if you will provide one of those21:24
broderi'll see what i can come up with21:24
broder...but not while i'm at work. i'm far enough behind from UDS :)21:25
tumbleweedit currently has << Mention any build & install tests you've done >>, < List the reverse dependencies that you've tested >21:25
broderoh right, we got stuck because there's no good way to lookup rdeps for the not-current release in the absence of chdist/chroot/etc. setup, right?21:25
tumbleweedwe decided to solve that with a webservice21:26
tumbleweedwe just need to write it...21:26
ajmitchbroder: unless you went with manually grabbing the Packages files & using grep-dctrl21:27
broderajmitch: *good* way :-P21:27
ajmitch:)21:27
Laneywe should make the ubuntu-dev-tools refuse to proceed if you've left templates in21:28
* ajmitch still has to get that backport tester in a working shape for demo purposes21:28
Laneyespecially submittodebian21:28
tumbleweedLaney: good point, but please file a bug because I'm pretty tired (thankfully, slept until 2pm today...)21:28
Laneyditto21:29
ajmitchtumbleweed: it's not like you would have had a long flight? :)21:29
* ajmitch was tired after UDS, but that was more because of getting up at 2AM to listen in on sessions21:29
tumbleweedajmitch: no, it was shorter on the way back, only 18 hours total :)21:30
ajmitchthat's nothing21:30
tumbleweed:)21:31
ajmitchdunedin->seville was about 36 hours travelling each way, was a fun trip :)21:32
brodertumbleweed: hmm...looks like the determine_destinations isn't quite working correctly. determine_destinations('precise', 'hardy') -> ['hardy', 'lucid']21:51
broderbut as of right now we'd still need to do maverick/natty/oneiric backports for that as well21:51
tumbleweedtrue21:59
broderit might be sufficient to reset support_gap every time you hit an LTS22:00
tumbleweedthat sounds reasonable22:01
tumbleweedbroder: pushed22:04
micahgwhy not just take every supported release between the 2 in question22:12
micahgah, nevermind :)22:12

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