[00:57] <Bachstelze> guys, what do with #577627 ? it could warrant a SRU, but I'm not familiar with the process
[01:01] <Bachstelze> oho wow, I really need to go to bed, there's one from 2 months ago already >.>
[01:04] <lfaraone> bug 577627
[01:05] <lfaraone> Bachstelze: Warnings like that probably do not meet the SRU criteria. Will the problem cause applications to fail?
[01:06] <Bachstelze> nope, I wonder why it's still there, though
[01:06] <Bachstelze> given it was reported before the release
[01:07] <lfaraone> Bachstelze: nobody found it, and the user did not subscribe ubuntu-sponsors.
[01:08] <lfaraone> Bachstelze: can you provide a command that demostrates the issue?
[01:08] <Bachstelze> anything with php-cli
[01:08] <Bachstelze> like  php --version
[01:08] <Bachstelze> with mcrypt installed
[01:09] <Bachstelze> there's also a bunch of other extensions with the same problem
[01:10] <lfaraone> Bachstelze: I see.
[01:11] <lfaraone> Bachstelze: It might be useful to report the problems when they occur to the upstream maintainers, as well as Debian. Carrying an ubuntu delta for a bunch of packages just to fix deprecation warnings seems a bit overkill if you can get upstream or Debian to cooperate.
[01:11] <lfaraone> *as to Debian
[01:12] <Bachstelze> it's fiit was fixed in Debian in 5.3.2-1
[01:14] <lfaraone> Bachstelze: Okay. The reason it was not fixed in Ubuntu was because the patch provided by the original reporter did  not fix the problem.
[01:14] <lfaraone> (Reading bug 540208, from what I can tell)
[01:23] <Bachstelze> lfaraone: you can also mark #577591 as a duplicate (or Invalid)
[01:24] <lfaraone> Bachstelze: already done.
[01:27] <Bachstelze> no, you did 577627 ;)
[08:04]  * hyperair wonders when the debian autosync begins
[08:05] <imbrandon> hyperair: i'd assume sometime monday durring UDS when someone has time to turn the bits on
[08:05] <hyperair> oh cool
[08:05] <imbrandon> maybe later today if someone is stuck in transit or got there early
[08:06] <imbrandon> but again this is just my guess , from prior cycles
[08:06] <imbrandon> but its normaly very very soon after the "archive open" email comes
[08:07] <imbrandon> they also may be waiting for the default gcc discussion too
[08:08] <hyperair> i see.
[10:38] <om26er> how do I know which package is synced from debian and which is not?. after packaging a newer version if I get 'we sync this from debian' thats not good.
[10:54] <nigelbabu> om26er: packages without ubuntu specific changes are synced from debian
[10:55] <om26er> nigelbabu, that would make it more than 80%packages?
[10:55] <nigelbabu> om26er: yup
[10:55] <om26er> thanks nigelbabu
[12:01] <BlackZ> if there are bugs in some files of the debian package which I'm packaging from scratch, is it better to apply a patch for the files or modify the files instead? (license: GPL3 +)
[12:02] <BlackZ> s/debian package/source
[12:06] <astraljava> BlackZ: From what I understand, you should be patching, as you're not upstream, are you?
[12:08] <BlackZ> astraljava: no
[12:11] <BlackZ> astraljava: OK, I've patched it. Thanks ;)
[12:12] <imbrandon> ScottK: can you prod a package through binary NEW ?
[12:13] <imbrandon> the source package is the same as before, it just builds a few more binarys now ( from a debian sync )
[12:14] <imbrandon> btw hopefully your flight(s) were uneventful :)
[12:14] <imbrandon> i saw crimsun and a few others wernt so lucky
[12:57] <ScottK> imbrandon: I made it.  What package?
[13:11] <imbrandon> ScottK: opensync
[13:11] <imbrandon> is the source package
[13:11]  * ScottK looks
[13:14] <ScottK> Love the debian/changelog entry.
[13:14] <azeem> yeah
[13:15] <azeem> one of my favourite messups!
[13:18] <imbrandon> heh what part?
[13:18] <azeem> http://packages.qa.debian.org/o/opensync/news/20100206T230242Z.html
[13:20] <imbrandon> ahh
[13:20] <nigelbabu> oh what a messup indeed!
[13:20] <nigelbabu> and what is 'unreleased'!
[13:22] <azeem> it's a secret Debian distribution which will reclaim victory from Ubuntu
[13:22] <azeem> got accidently leaked through this upload
[13:23] <nigelbabu> yes, and they tend to not have changelog entires to confuse us :D
[13:23] <ScottK> imbrandon: Done.
[13:24] <imbrandon> ScottK: ty
[13:26] <nigelbabu> azeem: I wonder, isn't lintian supposed to catch such type of mistakes?
[13:27] <azeem> the guy probably didn't run lintian
[14:03] <azeem> imbrandon, ScottK: http://packages.qa.debian.org/o/opensync/news/20100509T130257Z.html
[14:05] <ScottK> Revisonism ...
[14:05] <ScottK> We'll get it on the next autosync run.
[14:06] <azeem> ScottK: there was a subversion tag of -3 with those changes already, so...
[14:06] <azeem> plus it fixes an RC bug
[14:06] <ScottK> It will come in the next autosync run.
[14:06] <azeem> sure
[19:49] <laymansterms> Hi, I need to get a dependency packaged for a piece of software that I work on. The dependency I need is very similar to another package that is already in universe. What is the best way to get in contact with the packager? The package in question is pyclutter-gtk.
[19:49] <nigelbabu> laymansterms: look at changelog and get in touch with last updater
[19:50] <nigelbabu> especially if that person has @ubuntu or @debian email ID
[19:51] <laymansterms> nigelbabu, the ChangeLog for pyclutter-gtk says it was generated by 'configure.' Does that matter?
[19:51] <laymansterms> or should I still try to contact that person?
[19:51] <maco> ChangeLog? no, look at debian/changelog
[19:51] <nigelbabu> um, yeah debian/changelog
[19:52] <laymansterms> oh, oops. Sorry, I forget about the debian changelog.
[19:52]  * laymansterms has very little packaging experience.
[19:54] <laymansterms> nigelbabu, the email in the changelog is a debian email address. Do you know of a good channel to ask in? Something equivalent to #ubuntu-motu for Debian?
[19:54] <nigelbabu> #debian-mentors on oftc
[19:54] <hyperair> someone with a notebook with one battery please tell me what battery number you have (/sys/class/power_supply/BATN)
[19:54] <ScottK> laymansterms: If the package comes straight from Debian unmodified, I'd email the maintainer
[19:54] <hyperair> apparently mine's BAT1, but conky hardcodes BAT0
[19:55] <laymansterms> ScottK, okay, I'll give that a shot.
[19:55] <ScottK> hyperair: BAT1 on a Dell mini 10v.
[19:55] <laymansterms> nigelbabu, thanks.
[19:55] <hyperair> ScottK: thanks.
[19:55] <hyperair> anyone else?
[19:56] <nigelbabu> hyperair: one sec
[19:56] <maco> ScottK: so, what country are you in?
[19:56] <nigelbabu> hyperair: BAT0
[19:56] <ScottK> maco: Belgium.
[19:56] <hyperair> nigelbabu: interesting.
[19:57] <hyperair> nigelbabu: so only some computers are affected. whee.
[19:57] <maco> ScottK: ok so you made it then. dan's plane got a flat tire last night and wasnt allowed to cross the ocean. i think he's hanging out at the airport on standby right now
[19:57] <BlackZ> could a MOTU review/advocate http://revu.ubuntuwire.com/p/autotrash ? thanks
[19:57] <nigelbabu> maco: oh, dan still doesn't have  flight?
[19:58] <maco> nigelbabu: well he came home last night and was still here when i went out this morning
[19:58] <ScottK> maco: Ouch.
[19:58] <maco> but he's gone now, so i assume at airport
[20:04] <imbrandon> hyperair: mine also is BAT1
[20:04] <imbrandon> hyperair: toshiba , old intel celeron m based laptop
[20:06] <imbrandon> ScottK: are autosyncs on/running now ?
[20:06] <ScottK> I think it was run the first time earlier toda.
[20:06] <ScottK> y
[20:07] <ScottK> Not sure how it worked out.
[20:07] <imbrandon> k
[20:07] <imbrandon> how often does merges.u.c update ?
[20:07] <geser> imbrandon: cjwatson started one
[20:07] <imbrandon> geser: great
[20:09] <ScottK> imbrandon: I think /6 hoours
[20:09] <imbrandon> k
[20:09] <imbrandon> trying to plan for my next 2 days, gonna be offline for 4 hours chunks 3x over the next 2 days
[20:09] <imbrandon> so i'm trying to stack a bit of "offline" stuff to do
[20:10] <geser> the buildds are busy the next three days at least
[20:10] <imbrandon> oh i'm sure
[20:11] <imbrandon> i got some "real" work to do also ( as in my day job ) so i'll likely do some of that too
[20:12] <imbrandon> ScottK: i tell you i switched companies ?
[20:13] <ScottK> imbrandon: I thought you started your own store, or is that just a side job?
[20:13] <imbrandon> ScottK: thats just a side thing , online only
[20:14] <imbrandon> ScottK: i went to work for the company BenC is working at now, actualy working on the same project ;)
[20:14] <ScottK> Ah.
[20:14] <ScottK> I see.
[20:14] <ScottK> No, you hadn't mentioned it.
[20:15] <imbrandon> yes, its really a quite cool project, and its based on Ubuntu LTS , woot
[20:16] <imbrandon> its mostly a 4 to 5 guy team, he is doing the drive/kernel stuff, i got the front end, and there there is some SA and QA guys
[20:16] <imbrandon> driver*
[20:25] <laymansterms> hello again, is there a Ubuntu meta package that is helpful for installing helpful packaging tools? I feel like there is but I can't remember the name of it. devscripts or something.
[20:26] <c_korn> laymansterms: correct, http://packages.ubuntu.com/lucid/devscripts
[20:27] <laymansterms> c_korn, I just did an apt-cache search for "packaging" and saw ubuntu-dev-tools. Do you know the difference between devscripts and ubuntu-dev-tools?
[20:27] <hyperair> laymansterms: and ubuntu-dev-tools
[20:28] <hyperair> laymansterms: devscripts originates from debian.
[20:28] <laymansterms> I'd like to use bzr builddeb... is that plugin in one of those packages?
[20:28] <hyperair> laymansterms: ubuntu-dev-tools is ubuntu-specific.
[20:28] <hyperair> bzr builddeb is a package of its own afaik
[20:28] <imbrandon> laymansterms: use both, devscripts is more generic but required and u-d-t makes your life easier ;)
[20:30] <laymansterms> imbrandon, ubuntu-dev-tools says it replaces devscripts
[20:30] <imbrandon> laymansterms: yea it probably has some of the updated scripts , it used to depend on it
[20:30] <imbrandon> now probably encompases it
[20:31] <laymansterms> it's weird: Depends: devscripts Conflicts: devscripts Replaces: devscripts
[20:31] <laymansterms> (lines from apt-cache depends ubuntu-dev-tools)
[20:46] <imbrandon> hum
[20:58] <crimsun> imbrandon: congrats. Good to be able to hook people up
[20:58] <imbrandon> crimsun: ty ty
[20:59] <imbrandon> crimsun: i already got some of the hardware in hand to install monday, looks like its going to be a fun project
[20:59] <crimsun> nice
[21:02] <imbrandon> crimsun: did you finaly make it , or still waiting somewhere in-between
[21:09] <crimsun> imbrandon: I'm still at the origin; our rebooked flight is scheduled for 1715 departure from Dulles
[21:10] <crimsun> four of us are going to be dragging at the opening meeting
[21:10] <imbrandon> heh i bet, that sucks