/srv/irclogs.ubuntu.com/2009/11/29/#ubuntu-devel.txt

mrmojohi guys00:14
faganmrmojo: hello00:14
mrmojoi am looking to get the source code for software-properties-gtk00:14
mrmojospecifically the version shipped in karmic00:15
mrmojowhat's the best way to go about to get that00:15
faganlaunchpad has everything ill get you a bzr for it00:15
mrmojocheers man00:16
faganmrmojo: here is a tar.gz https://edge.launchpad.net/ubuntu/karmic/+source/software-properties/0.75.4/+files/software-properties_0.75.4.tar.gz00:18
fagango nuts :)00:18
mrmojothanks00:19
faganmrmojo: np00:19
mrmojois there an IRC channel that I could join to ask questions about the source for this?00:24
mrmojoI'm not sure if it's a GNOME project or just Ubuntu-specific heh00:24
=== asac_ is now known as asac
mrmojoright i think I've fixed my 'bug', could someone point me to a guide on how to repackage my changes00:32
feastyI'm looking for some information on becoming a developer for Ubuntu. The wiki pages talks about starting a prospective developer by fixing bugs and working on new packages. If I were to look at working on a new package would it have to be a new package I have chose or is there a list of suggested packages I could choose from? I'm just looking at what I need to do to get myself started really. Can anyone help me?00:33
RAOFfeasty: We need fixing bugs much more than we need new packages; unless there's some software that you'd really like to see in Ubuntu that isn't yet, there's no need to look at adding new packages.00:35
feastyRAOF: No I am happy fixing bugs.00:36
RAOFExcellent!00:37
feastyWhere can I go to pick up a bug to fix? Launchpad?00:38
faganmrmojo: ask here on monday for the dev in charge of that package and they will be able to help you00:40
faganThey can push the fix for you00:40
mrmojoIt's actually not a fix for ubuntu00:41
mrmojoit's a fix for linux mint00:41
mrmojothough the bug has been marked as invalid00:41
mrmojoit's more of a fix for myself heh00:41
lifelessfagan: huh? you don't need to wait for a specific dev; just do the fix and propose it for merging.00:41
lifelessfagan: many devs are volunteers too00:41
faganlifeless: true00:41
faganvery true since im one00:42
faganmrmojo: id say if you tar.gz it someone in linux mint might package it for you00:42
faganits a complicated process00:43
=== bdefreese2 is now known as bddebian
mrmojook00:44
George_EWhat package provides the opengl headers?01:27
ebroderDoes anybody have any thoughts on bug #426614? binutils-dev is certainly very clear that nothing should link libbfd dynamically, and it seems we've discovered why02:11
ubottuLaunchpad bug 426614 in oprofile "oprofile should not link libbfd dynamically" [Low,New] https://launchpad.net/bugs/42661402:11
ebroderI like Anders' patch and think it should be uploaded, but the decision almost feels out of scope for me to make on my own02:12
ebroder(Especially given fabricesp's objections)02:13
ebroderSo...is there a standard response for the asshole-Debian-maintainer-who-doesn't-think-he-should-care-about-Ubuntu?04:58
ScottKebroder: Ignore it.  You probably aren't going to change his mind.05:00
* ebroder sighs05:00
ScottKebroder: Over time, the fraction of Debian maintainers that react that way has declined.  Just give the factors that are at work more time.05:05
ScottKAdditionally, he's perfectly within his rights not to worry about Ubuntu.05:06
ebroderI supposethat's true05:06
ebroder(I guess the rest of his reply was both civil and valid, even if I don't like it)05:06
ebroderI suppose the more productive question is this: is there anywhere that I can make a note that will be seen and respected that erlang should never be synced from Debian without a corresponding sync of erlang-doc?05:09
ebroder(I'd be OK with "never" applying only to manual post-DIF syncs)05:10
StevenKebroder: That's very difficult if erlang has no Ubuntu changes05:11
ebroderYeah, it doesn't, but this breakage has happened for the last two Ubuntu releases (erlang-doc doesn't get synced along with erlang, which makes the erlang-doc packages uninstallable because of the incredibly harsh conflicts in erlang)05:12
StevenKebroder: Then you should file a seperate bug a few days later asking that -doc be sync'd?05:13
ScottKebroder: Mostly someone needs to watch out for this stuff.  We have tools for uninstallable package detection that should show this.  Also this is potentially SRU worthy, so it can perhaps be fixed post-release if needed.05:13
ebroderStevenK: I don't personally care about the package - I'm just trying to come up with some way to prevent the breakage going forward05:13
StevenKebroder: Read as, I'm not sure how the archive admins can help, without us having to special case erlang05:14
ebroderScottK: Ok. I may try to pull Jaunty and Karmic SRUs together at some point in the near future05:14
ScottKStevenK: A check could, if someone contributed the patch, probably be put into MoM to make erlang-doc appear if it needed to be sync'ed.05:16
ScottKPerhaps ebroder would be motivated to provide it?05:18
ebroderPerhaps. Where is the source?05:19
ScottKebroder: merge-o-matic project on Launchpad.05:21
ebroderOk - I'll check it out05:21
ebroderActually, I'll start by filing a bug - that way if I don't get to it now, at least it won't be forgotten05:26
shankhshi i have changed prism to get prism-orkut , and i would like to make .deb package and put it in the repos.I have one problem i have never done such things and i want to learn any help?06:13
ebrodershankhs: I'm not sure it makes sense for Ubuntu to ship prism apps for specific websites. How do we choose which websites to include apps for?06:14
shankhsebroder: you have a point but i am using this package to learn how to make  a .deb package and put it in the ubuntu repos.If thats not permitted then its fine.06:18
ebrodershankhs: I just think it's unlikely that such a package would be approved for being added to Ubuntu06:19
shankhsebroder: ok06:20
shankhsebroder: but i really want to learn06:20
shankhsany suggestions?06:20
shankhs:(06:20
ebrodershankhs: You could check out https://wiki.ubuntu.com/UbuntuDevelopment/06:21
ebroderThere's a lot of docs being put together there06:21
shankhsebroder: thanx i hope you guys do not get disturbed by noobs like me. :)06:22
ebrodershankhs: Not at all - we could always use more help. I'm just a little distracted at the moment because I'm about to go to sleep06:22
shankhsebroder: ok good night06:23
=== Guest87841 is now known as Zic
=== Zic is now known as Guest81151
=== Guest81151 is now known as Zic
shiki-hi all08:52
shiki-any active dev who can give me a little help?08:52
shiki-well... when someone will be here: I get an error when I try to prepare a package for PPA upload. I got some PPA aldy, but I cant figure this error out. It gives : "debuild: fatal error at line 1334: \ dpkg-buildpackage -rfakeroot -d -us -uc -S -sa failed" when I use the "debuild -S -sa" command.08:54
shiki-I just need some hint where can I find that line 113408:54
shiki-*133408:54
shiki-ah lol ... wrong channel -.-08:55
=== Zic_ is now known as Zic
=== Zic is now known as Guest40040
hyperair+3 and that would be 133709:01
hyperairhe was so close..09:01
macohahaha09:01
macoi dont even understand what happens on line 1334 of debuild09:02
=== Guest40040 is now known as Zic
maco(or really much of what debuild does at all)09:02
hyperairnor do i09:03
cjwatsonLaney: oh, prod james_w at some point if it's out of date, or file a bug on the udd project09:14
cjwatsonshiki-: line 1334 of debuild is not significant, it's just where it happens to do the error detection for subprocesses: in this case the real failure is in dpkg-buildpackage, and should have been output a little bit further up, so you'll need to read the output with care and judgement09:15
shiki-cjwatson: I found the problem already. Thanks for the description though. It was a typo/problem in the debian/changelog09:16
shiki-and sorry for messing in the wrong channel. :)09:16
fqhHi, can anyone connect to network wth ADSL under ubuntu9.10?09:30
=== fabrice_sp_ is now known as fabrice_sp
=== azeem_ is now known as azeem
xeeHi, is there a channel where I can ask about packaging?13:23
azeemxee: #ubuntu-motu13:23
=== emma_ is now known as emma
asackees: https://svn.pardus.org.tr/pardus/2009/stable/system/devel/gcc/files/note-gnu-stack.dpatch ...14:29
asaceverywhere its +.section.note.GNU-stack,"",@progbits14:29
asacbut on arm its14:29
asac+.section.note.GNU-stack,"",%progbits14:29
asackees: any idea?14:29
=== LucidFox_ is now known as LucidFox
asackees: unping. we figured it a while ago ...18:16
youssefGood evening. Anyone knows something about the fop bug (310882)?18:44
youssefsee you later18:57
=== markus__ is now known as thekorn
=== stgraber_ is now known as stgraber
YokoZarmdz: I'm trying to remember what the policy was going to be regarding upstart jobs that we discussed at UDS.  Was it that start/restart should never fail (even with bad config), or that package install should never fail (even with a failing upstart job)?20:22
mdzYokoZar, I am of the opinion that maintainer scripts which fail due to transient error conditions are usually not best20:23
mdzand even some permanent ones, e.g. a daemon failing to start because something is wrong with its configuration20:23
YokoZarmdz: so something like start procps || true in the script?20:24
mdzYokoZar, unless something later in the maintainer script will fail in bad ways due to the daemon (or non-daemon in this case) failing, yes, that's what I would do20:25
mdzbut this is not a policy, just my view20:25
mdzI have heard that slangasek has a different view20:25
mdz(for example)20:25
YokoZarWell one problem is that we don't have a good way of notifying the user that their daemon is failing20:25
mdzseems like a reasonable topic to chat with the TB about20:25
YokoZarand in this particular case we're responsible for the bad configuration somehow (haven't figured out where exactly, but no one manually modified sysctl.d here)20:26
YokoZarbut yeah I agree ~ technical board20:26
mdzYokoZar, a bunch of errors from apt is not a very good way either ;-)20:26
YokoZarThis is definitely true :)20:27
YokoZarmdz: I see you put it on the agenda for the technical board.  Thanks :)20:43
keesasac: what was the solution?  I'd like to add it to the top of https://wiki.ubuntu.com/SecurityTeam/Roadmap/ExecutableStacks22:27
asackees: on arm @... is a asm comment ... so use %prog... and %object instead22:28
asaclike:22:28
asac.section        .note.GNU-stack, "", @progbits22:28
asac->22:28
asac.section        .note.GNU-stack, "", %progbits22:28
keesasac: interesting.  does %progbits work on non-arm (i.e. switch to using % everywhere instead of @?)22:29
asaci tried it and checked with readelf ... worked here on x86 ... but mybe double check22:30
keesok cool, I'll updated instructions.22:31
keess/ed/e/22:32
asackees: yeah. but plesae double check ... i am not really familiar with this topic ;)22:32
nixternaleveryone have their Google Waves right? I have 15 invites all of a sudden to hand out22:32
keesasac: it's possible that ARM is just doing the right thing regardless.22:33
keesasac: I will double-check22:33
asackees: on ARM %progbits is definitly right (according to binutils doc)22:34
asacnot so sure about other archs22:34
asacbut i think it just does the right thing on those22:35
keesasac: which section of the gas docs talk about it?22:36
keesI'm reading http://sourceware.org/binutils/docs-2.20/as/index.html at the moment22:36
asachttp://sourceware.org/binutils/docs-2.20/as/Section.html#Section22:37
asac"ote on targets where the @ character is the start of a comment (eg ARM) then another character is used instead. For example the ARM port uses the % character."22:37
asackees: ^22:37
asacbut i changed it and tried the same stuff on x86 ... and readelf looked identical22:38
asacso i assume that it at least works on x86* stuff22:38
* kees nods22:38
asac(the % that is)22:38
keesasac: confirmed.  % is also what gentoo recommends.  I've updated the documentation.  thanks for finding that!22:48
asacwelcome!22:48
asacthanks to chromium ;)22:48
asaci think that gas docs could be more clear ;)22:49
asacwhere what works ;)22:49
asacand if nothing works everywhere do something like here: http://sourceware.org/binutils/docs-2.20/as/Type.html#Type22:49
George_EIm having trouble getting dpkg_shlibdeps working. How do you have it put the Depends: info right into the control file?23:11
RAOFGeorge_E: This is probably better in #ubuntu-motu, but it semes quiet enough here ATM.  You have ${shlibs:Depends} in the Depends: line, and that'll get replaced by the appropriate dependencies.23:14
George_EWhat args do I pass? When I did it it put the stuff in a file shvars23:16
RAOFGeorge_E: You should be able to just call dh_shlibdeps, and it should do everything for you.23:16
George_EOoh. Ok.23:17
RAOFAlthough context might be important if you're doing something more complicated than "I want to fill in the dependencies of my app package"23:17
George_ENo. I just wanted to avoid copying and pasting.23:18
bdrung_jcastro, kenvandine: b-sides should drop arc-colors and depend on shiki-colors instead. we will probably move the wallpapers into shiki-colors and drop arc-colors. you should rename adblock-plus to xul-ext-adblock-plus (will be the name in lucid and works on karmic, too)23:43

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