[00:00] is my install line correct: cd src && $(MAKE) install prefix=$(CURDIR)/debian/msp430-binutils/usr ? [00:02] AdamDH: define prefix before the install target :) [00:03] cd src && make prefix=$(CURDIR)/debian/msp430-binutils/usr install [00:03] so some where I have made a mess of my VM and installed it somewhere! [00:03] thanks for all the help jmarsden [00:03] i will try that [00:03] Possibly, but only if you were running as root...? [00:05] You could test it by hand: mkdir -p /tmp/junk/usr && cd src && make prefix=/tmp/junk/usr install # and check what ends up under /tmp/junk [00:07] i am running as root probally a bad idea [00:08] Definitely a bad idea. The whole packaging system is designed so you do not need to do that... hence the fakeroot package, for example... [00:11] YES! got a working package, thanks all for the help, need to tidy up my rules but at least I know now how it all works [00:11] took some time but I got there [00:12] probally going to have more questions later as I have a few more packages to make [00:14] Have fun :) [00:15] one thing, my package has been named as msp430-binutils_msp430-binutils-2.18-msp430-cvs.0.0.20081229_amd64.deb instead of msp430-binutils_msp430-binutils-2.18-msp430-cvs.0.0.20081229_amd64.deb not sure why as the directory structure is correct [00:15] i mean the correct name should be msp430-binutils_binutils-2.18-msp430-cvs.0.0.20081229_amd64.de [00:16] AdamDH: the bit between the _s comes from your debian/changelog [00:17] thats in my changelog msp430-binutils-2.18-msp430-cvs.0.0.20081229 [00:17] well then [00:18] that explains it, no? [00:18] slightley confused [00:18] make the version in the changelog the same as what you want to be between the _s in the resulting deb [00:19] ie binutils-2.18-msp430-cvs.0.0.20081229 [00:19] AdamDH: name is PACKAGE_version-from-changelog_ARCH.deb [00:19] ah right follow looks like I screwed up the versioning then when I packaged it [00:24] for inclusion into the main tree do my packages need man pages? [00:25] Yes, I'm pretty sure they will. [00:27] looks like I have to write some as there are non with the project, in fact documentation is lacking, I wrote a php script to get the sources and make the patches etc and tidying things up before packaging and to mirror the project [00:31] No man pages for gcc and binutils??? Surely there are some? [00:35] its a cross compiler so non that are for the actual msp430 port [00:36] are for the general gcc just not for the arch the compiler is working with [00:36] i will see what the AVR project did === Kalidarn- is now known as Kalidarn [04:57] http://dpaste.com/103619/ dpkg-buildpackage ... line 164: debian/rules: Permission denied [05:00] chmod +x debian/rules [05:00] CarlFK: chmod 775 debian/rules [05:01] cool. thanks [05:10] kinda quiet [05:12] 775!? 755 [05:13] sure [05:21] hey StevenK [05:33] http://dpaste.com/103621/ Setting up libpoppler-glib3 (0.8.7-1.1) .... libpoppler-glib-dev depends on libpoppler-dev (= 0.8.7-1.1); however: Version of libpoppler-dev on system is 0.8.7-1. [05:33] lies! [05:33] oh wait..glib3... dev.. [05:34] never mind. all is well === Tweenaks is now known as Treenaks === fabo_ is now known as fabo === Guest89320 is now known as Zic [08:29] revu, anyone? http://revu.ubuntuwire.com/details.py?package=codelite === jussio1 is now known as jussi01 [09:53] has anybody ever seen something similar to this? [09:53] /usr/include/bits/stdio2.h: In function 'int sprintf(char*, const char*, ...)': [09:53] /usr/include/bits/stdio2.h:35: error: '__builtin_va_arg_pack' was not declared in this scope [10:25] * StevenK kicks ffmpeg-debian until bits fall off. [10:25] DktrKranz: See bug #293807. [10:25] Launchpad bug 293807 in gccxml "gccxml regression: fails to parse stdio.h" [Undecided,Confirmed] https://launchpad.net/bugs/293807 [10:25] So, not very hard, then. [10:25] Who's bright idea was it to move all of the header files around, anyway? [10:26] * StevenK grins at RAOF, and kicks ffmpeg-debian until it implodes [10:26] iulian, yep... I've seen it, and it's seems it's already fixed upstream [10:27] DktrKranz: Was that the package you were working on? [10:27] Mmmm, Mocha Chill. The drink no-one seems interested in shipping out east. [10:27] iulian, it was insighttoolkit [10:27] it FTBFS that way [10:27] * iulian takes a peek at it. [10:27] RAOF: Hmmm? [10:28] Hmmm. New wine. [10:29] StevenK: Wests Mocha Chill, or some such. It was briefly stocked in NSW supermarkets last year, but isn't any more. [10:30] * hyperair wonders if there's anybody free enough to review a package: http://revu.ubuntuwire.com/details.py?package=codelite [10:31] RAOF: Perhaps it got branded with the same disdain that West Coast gets and was ignored ... [10:32] - --with-ffmpeg-includes=/usr/include/ffmpeg [10:32] + --with-ffmpeg-includes=/usr/include/libavcodec\ -I/usr/include/libavformat [10:32] * StevenK sighs at siretart and ffmpeg-debian [10:32] That so shouldn't work [10:33] VideoEffectClip.H:31: error: conflicting declaration 'typedef struct gavl_video_frame_s gavl_video_frame_t' [10:33] /usr/include/gavl/gavl.h:1869: error: 'gavl_video_frame_t' has a previous declaration as 'typedef struct gavl_video_frame_t gavl_video_frame_t' [10:34] * StevenK whimpers pathetically === asac_ is now known as asac [11:49] Haha [12:01] How is it possible to have a package in my repo, and have a numbered release such as 1.0.2 [12:01] Then also have a package 1.0.2-svn2340??? [12:01] and if someone wants to run trunk, then they can, but otherwise they can only run the standard release??? [12:02] package and package-snapshog [12:02] t* [12:03] so it'd be handled like two different packages? [12:03] that works. [12:04] and your version number should be something like 1.0.2+svn2340-1 if it's based on 1.0.2 with addons, or 1.0.3~svn2340-1 if it's based on an as-yet unreleased 1.0.3 [12:06] awesome. thanks. === Igorots is now known as Igorot [12:16] Answer: experimental's grub2 appears to be missing the --fs-uuid option to search, thus breaking the config. Score! [12:17] Haha [12:18] At least it's got tab-autocompletion and a bash-like shell. [12:18] Now, if it only had a dvorak keymap... [12:19] well, grub1 also has tab completion and a shell [12:20] That wasn't meant to be a comparison; just that it's infinitely easier to fix because it *does* have those features than if it didn't. [12:20] yeah. [12:25] RAOF, your a dvoark user? [12:25] epic. [12:26] I'd learn dvorak, but I'm scared my wrists would break since they're use the brain-damage of qwerty [12:26] s/use/used to/ [12:29] StevenK, I used to use dvorak, but then I found that by being incompable with the rest of the world sucked [12:29] although I think in the end my WPM went up [12:29] Neat way to make sure no one touches your computer [12:30] Hard to ssh into other machines using other peoples keyboards, then [12:30] StevenK, yeah, thats why I never changed the caps back to QWERTY after the experiment [12:30] * NCommander is too paranoid on breaking this laptops caps to try and rearrange them though ... [12:32] StevenK, so how was your holiday BTW? [12:32] Still going [12:37] I accidentally forgot to include a binary file in the orig, how can I update the orig and upload it to launchpad? or delete the orig that's in launchpad? [12:38] StevenK: did you get anywhere with openmovieeditor? [12:38] I'm trying to execute: debuild -S -sd to rebuild the package with the binary file I forgot. but it's giving me the error: dpkg-source: error: cannot represent change to freeswitch-1.0.2/libs/libshout-2.2.2.tar.gz: binary file contents changed [12:39] * StevenK checks [12:39] And I can't change the orig and upload it because launch pad says it already has an orig. [12:40] james_w: Yeah. Now it wants img_convert from ffmpeg, but that isn't exported, since it's the old API, and disabled when you enable swscaler. [12:40] you need to change the upstream version number [12:40] StevenK: add libswscale-dev to Build-Depends [12:40] StevenK: see the Debian bug report [12:40] Hmm [12:41] james_w: from freeswitch-1.0.2-1ubuntu2 to??? [12:41] * StevenK tries that [12:41] StevenK: however, it uses another deprecated ffmpeg function which has been removed in the version we have. Upstream has completely rewritten the code. [12:42] * StevenK tries to not lose control and scream like a banshee [12:42] just pull it from the archive... [12:42] I'm seriously tempted to remove ffmpeg-debian and all of it's rdepends [12:45] AudioFileFfmpeg.cxx:135: error: 'avcodec_decode_audio' was not declared in this scope [12:45] james_w: I see that. [12:45] james_w: from freeswitch-1.0.2-1ubuntu2 to??? [12:46] StevenK: that's the one [12:46] quentusrex: freeswitch-1.0.2.0.repack-1ubuntu2 or something [12:48] should I be using debuild -S -sa or debuild -S -sd? [12:49] quentusrex: -sa, as you want to be uploading the orig tarball to launchpad [12:49] ok [12:49] FWIW, tarball in tarball is just sickening [12:50] the software either needs the tarball in the libs/ folder or it will use svn to get it during build. [12:50] but launchpad doesnt' allow internet access during build. [12:50] * StevenK retches [12:50] so, I have to manually include them... so that they'll build... [12:51] yeah, I hate it. but the software works REALLY well and builds well too [12:51] but it's hard to automatically package. [12:51] huats: hey 4k, how are you? [12:53] how do I cancel a launchpad build? It's hung.... [12:53] It'll time out eventually [12:53] maxb: that'll take too long and take up too much resources... [12:53] you can't. [12:53] :( [12:54] it's been an hour [12:54] https://launchpad.net/+builds/hassium [12:54] It will time out after 150 minutes [12:54] :( [12:54] but I need to trial and error to figure this out... [12:55] Wait, it gets tarballs from SVN? [12:55] StevenK: yes... [12:55] Oh man, it gets even more disgusting [12:55] Right, I'm not sure that will die on it's own [12:56] right... [12:56] I dont' think it will... [12:56] it'll keep trying the svn get. [12:56] :( [12:56] The wget will stop after 20 tries [12:56] quentusrex: If you're worried, join #canonical-sysadmin, and ask for it to be killed. But it is the 30th of December ... [13:02] Hm, why's it downloading libshout instead of using the Ubuntu packaged one? Is the upstream buildsystem hardwired to be unable to use installed deps? (If so, how hideous :-( ) [13:10] hey james_w ! [13:10] how are you my friend ? [13:15] huats: I am good thanks, how are you? [13:16] great too ! [13:16] james_w: on holidays ? [13:17] yup. you? [13:17] nope [13:17] still not a MOTU I see :-) [13:17] but I am working from home today... [13:17] not yet... [13:17] I am just returning from the US (and the trip I did after the UDS..) [13:18] ah, how was that? [13:23] Can someone here tell me how to use the touchpad? XDD Sometimes it rotates the desktop cube, but I don't know how I've done it XD [13:23] BUILD SUCCEEDED [13:23] Total time: 237.3 seconds. [13:24] ikvm, kiddies! [13:24] directhex: all ready? [13:25] Laney, not yet [13:25] Also, helo from the East Coast Mainline! [13:25] Laney, but i've got a build process going where it rebuilds the bootstrap binaries then rebuilds against those [13:25] * Laney choo choos [13:25] signed, no less! [13:26] directhex: NBS shows libgnome2.0-cil and such stuff. Do you know if all the applications need a rebuild? [13:27] sebner, no, no app needs rebuilding if it's been transitioned [13:27] directhex: I see, thx :) [13:28] sebner, that was the idea ;) [13:28] directhex: ^^, well, I just checked the NBS page and saw that so I wos confused =) [13:40] RAOF: More grub2 testing? [13:41] Ding. [13:47] how I detest when proprietary drivers go wrong [13:48] at 3am? [13:48] sure, couldn't sleep, decided to upgrade some stuff [13:48] big mistake [13:49] Haha [13:49] ajmitch: "U looz" [13:49] just installing the nvidia 180.11 driver should be painless, right? [13:49] What Could Possibly Go Wrong [13:49] no [13:50] StevenK: "No devices detected", of course [13:51] I should probably just try & reboot instead of relying on rmmod/modprobe === bddebian2 is now known as bddebian [14:09] can anyone help me get started packaging? [14:12] pschorf: See the topic, and ask if you have any specific questions [14:13] (start with a bitesize bug or two) [14:14] Laney, is there a better way than just scanning bugs to find one? [14:18] pschorf: https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.ha ... [14:18] any archive admin around who can process a sync bug? [14:18] ... s_cve.used=&field.tag=bitesize&field.tags_combinator=ANY&field.has_no_package.used= is a list of bugs that people have determined to be suitable for new contributors to work on [14:18] .. [14:19] http://is.gd/ebsa try that link === warp10_ is now known as warp10 [14:41] after I've written a patch and added it to debian/patches, does it matter which method I use to repackage the binary? [14:41] pschorf, Not really, although pbuilder and sbuild are recommended to convert source packages to binary packages. [14:42] persia, and to apply the patch, i just append it to series, right? [14:43] I'd say it depends on the scenario. Is there any point in using pbuilder/sbuild when developing a package? Their use is mainly checking that it works in a clean environment, no? [14:44] pschorf: https://wiki.ubuntu.com/MeetingLogs/openweekedgy/PatchPackaging [14:44] pschorf, Yes, add it to series, and then construct the source package with something like `debuild -S -us -uc` [14:44] a session where pitti explains the various patches system... [14:44] it might help.. [14:44] thanks [14:53] boy, setting up pbuild takes some time... [14:58] Linking program ==> 'blender' [14:58] sh: Syntax error: EOF in backquote substitution [14:58] ARGH [14:59] any archive admins around to process a sync bug? [15:01] which environment variable do you change so debsign knows the proper email address? [15:01] slytherin: Yes, but I'd rather not break my rule [15:01] StevenK: what rule? [15:01] "Thou shalt not do archive admin after midnight" [15:02] slytherin: If it's from unstable and easy, I'll do it [15:03] StevenK: it is from unstable, easy, and important because it will unblock jboss sync. [15:03] slytherin: Link me the bug [15:03] While I ponder hot, flaming and enjoyable death for the sadistic guy that wrote scons [15:05] pschorf, DEBEMAIL [15:05] StevenK: bug #311564 [15:05] Launchpad bug 311564 in libjboss-web-services-java "Please sync libjboss-web-services-java 0.0+svn5660+dak2-1 (multiverse) from Debian unstable (main)." [Undecided,New] https://launchpad.net/bugs/311564 [15:06] slytherin: Er, surely that will be pulled in via the autosyncer? [15:07] StevenK: The package was fixed in Debian just after DIF. [15:07] Tasty. [15:07] libjboss-web-services-java | 0.0+svn5660+dak1-1 | jaunty/multiverse | source [15:07] libjboss-web-services-java | 0.0+svn5660+dak1-1 | jaunty/universe | all [15:08] StevenK: and that is the reason I logged the bug. [15:08] StevenK: well, there is another bug for moving all jboss related packages to universe. [15:09] slytherin: Right, then point me at that bug, and I'll fix the source tomorrow [15:09] That's dangerous to do after midnight. Soyuz gets fussy if not tickled just right for component moves. [15:09] "and I'll fix the source tomorrow" [15:09] IE, after I sleep [15:10] StevenK: bug #309435 [15:10] Launchpad bug 309435 in libjboss-xml-binding-java "Please move jboss related packages to universe" [Undecided,New] https://launchpad.net/bugs/309435 [15:10] pbuilder would yell at me if there were any errors, correct [15:10] RIght. Just providing justification :) [15:11] slytherin: Done [15:11] 4 dupes? [15:11] Odd [15:12] StevenK: thanks to broken requestsync in last week. [15:12] Fun [15:12] StevenK: thanks for sync. I will evaluate jboss sync tomorrow and log another bug. [15:13] slytherin: No problem. Prod me with the bug for multiverse -> universe ? [15:13] Oh, you have [15:13] * StevenK goes back to hiding under his rock [15:14] That one requires a bunch of checking [15:16] After I add a debdiff to a bug report and subscribe the sponsors, I just wait? [15:17] pschorf, Pretty much. [15:30] pschorf: No. Go fix something else while you wait .... Don't just wait. [15:38] ScottK, time to review a fix for a main package? [15:38] DktrKranz: Not really. Just about to head off and do some stuff. [15:39] no problem, thanks [15:53] nhandler: When you add new stuff to u-d-t, you have to add the script to setup.py otherwise it won't get installed. [15:54] jpds: Ok, I didn't know that. [15:54] I'll push a new revision to fix it [15:55] nhandler: I just did and uploaded it to the archives. [15:55] Ok, thanks a lot jpds ! [15:55] nhandler: No problem, thank you for the great script. [15:59] OK; Looks like my 0.50.1 upload of u-d-t has been eaten. [16:00] Oh, wait, there it is. [16:08] hmm, and 0.49 was never uploaded [16:09] Adri2000: I just noticed that too ;) [16:10] Adri2000: Well nevermind. [16:13] it was probably confusing that my changelog entry had "jaunty" while it was not uploaded. when using git, tags can help to know if a version was uploaded or not; how are we supposed to do with bzr? use "UNRELEASED" until it's uploaded? [16:14] Yes, when you upload, make a new changelog entry with UNRELEASED and push. [16:15] Using "UNRELEASED" is a common practice. [16:15] Then, have a special commit when you set a target and publish. [16:18] ok [16:24] pschorf: have you cancel your mail to the mentoring mailing list ? [16:25] (am I asking that since I am taking care of it..) [16:27] huats, yes [16:27] i wasn't sure if i needed to join the list first... [16:27] ijust reposted it [16:27] pschorf: you cannot join the list [16:27] :) [16:27] that's what i realized :P [16:28] the list is just a way of communication between the mentoring reception team :) [16:28] pschorf: so the next step is to found a good mentor for you [16:29] it would help if you tell us (by an email) which aspect you want to work on (desktop/server/ubuntu/kubuntu/xubuntu/whatever). [16:29] and then we'll contact you soon with a good match :) [16:30] should I send another email to the main list? [16:31] it might be good yes.. [16:32] with that informations... [16:35] alright, I've sent another through [16:37] * Laney molests huats [16:37] good work on bakery :D! [16:37] thanks Laney [16:37] (I don't think I said this already...) [16:37] hope that help [16:37] well [16:37] thanks pschorf [16:37] glom crashes whenever I make a table [16:37] but that's not your fault :( [16:37] oh ! [16:37] hum [16:38] you should contact murray the author... [16:38] yeah I will do [16:38] just trying a test build from source [16:38] ok [16:38] Laney: if you need any help just let me know.. [16:38] thanks muchly [16:39] actually [16:39] fancy filing a bug on the BTS for bakery 2.6? [16:39] why not [16:39] :> [16:39] my goal is glom in Debian [16:40] but I really think that contacting murray about the pb is a better ay to deal with it [16:40] Laney: I know that Np237 is interested on tha [16:40] t [16:40] you should talk with him... [16:40] huats: Who's that? [16:41] one of the main gnome guy for debian [16:41] oh [16:41] do they have a channel? [16:41] gnome-debian on gimpnet [16:41] heh [16:41] it's joss [16:42] he's been controversial lately [16:42] he is joss indeed [16:42] well pkg-gnome seems to maintain bakery so I guess we want to coordinate with them [16:42] for bakery and glom [16:44] indeed that is the aim [16:46] rock === jtechidna is now known as JontheEchidna [17:04] huats, do you know how long the mentoring queue is? [17:13] pschorf: There's no need to wait for a formal mentor to be assigned. You can always ask questions in the channel and usually someone will be around to answer. [17:25] could someone help me take a look at bug #151011? I'm having trouble finding where in the code the changes need to occur. [17:25] Launchpad bug 151011 in update-manager-core "do-release-upgrade does not provide guidance after view details" [Medium,In progress] https://launchpad.net/bugs/151011 [17:26] imbrandon: Hey! :) [17:35] pschorf: mvo (you can usually find him on #ubuntu-devel) does substantially all the work on that package. You probably ought to talk to him. === goshawk_ is now known as goshawk [17:42] might be interesting to folks: http://arstechnica.com/news.ars/post/20081230-why-ubuntu-users-should-care-about-debian.html [17:55] jcastro: Thanks for pointing that out. Personally I'm pumped that they linked to the Python wiki page I wrote. [18:00] heh, neat [18:06] jpds: hello [18:07] heya jcastro [18:07] hi brandon, long time no see [18:07] heh yea, irc eats alot of time :) [18:08] been preparing for the move accross the pond :) [18:08] oh? [18:08] work is opening a new office in london [18:08] jcastro: Very interesting article. === jussio1 is now known as jussi01 [18:08] and i get to spend the next 2 years there getting it going :) [18:08] imbrandon: that sounds like fun [18:09] imbrandon: Which part of London? [18:09] jpds: not sure, i can get the addy here in a sec [18:09] jcastro: yea, considering the main client we opened that office for ( Turner/Cartoon Network ) it should be a blast [18:09] 18270 bluefox 20 0 1275m 521m 25m S 37 14.0 11:45.49 rhythmbox [18:09] 11594 bluefox 20 0 923m 471m 30m R 16 12.7 3173:27 firefox [18:10] jpds: The Griffin Building [18:10] 83 Clerkenwell Road [18:10] London [18:10] EC1R 5AR [18:11] imbrandon: This year's trip to KC ended up being very short. We got delayed by freezing rain/ice on the way there, so there was no time to get together. [18:11] Sorry I missed it. [18:11] imbrandon: You do know it's on the logs now? :( [18:11] ScottK-desktop: np :) [18:11] jpds: i am missing your point .... i think [18:11] rhythmbox uses a lot of RAM o.o [18:12] if you mean that irc is logged , yes i know :P [18:12] imbrandon: Oh, in Soho, nice. [18:13] :P [18:13] 13025 bluefox 20 0 659m 65m 23m S 0 1.8 0:05.03 rhythmbox [18:13] ScottK-desktop: just leaves more BBQ for me :) [18:13] this is a just-started rhythmbox [18:26] what? [18:26] ribs? [18:32] anyone available to help with a SRU? [18:40] rhpot1991_laptop: ask [18:44] I am working on this: https://bugs.launchpad.net/bugs/302104 [18:44] Ubuntu bug 302104 in mythexport "Nominate for release" [Low,Confirmed] [18:45] was rejected before, I believe cause I didn't provide enough information, I'd like to know if anything else is needed [18:45] it also needs an ack from a motu I believe [19:04] rhpot1991_laptop: I'm not a MOTU, but the description of how SRUs work is at https://wiki.ubuntu.com/StableReleaseUpdates, which should let you understand whether your bug is adequate. [19:05] I would suggest at the very least giving it a more descriptive summary line [19:06] There is no justification in the bug for *why* this package should be SRUed. You definitely need to add that [19:09] one of the comments says why, the package is useless as is [19:18] could someone review my package please? http://revu.ubuntuwire.com/details.py?package=codelite [19:25] If you forget to change a bug's status until after subscribing sponsors, does it make a difference? [19:25] no [19:28] also, if we submit a debdiff, does it automatically get pushed to an attached debian bug, or do we have to do it ourselves? [19:35] hey people.. [19:35] Hey rawler. [19:35] saw Debian Import Freeze was 25th of december.. is it the same deadline for packages from revu? [19:39] does anyone have time to look at a debdiff I put up earlier? [19:39] rawler: No, that's feature freeze time [19:39] pschorf: Which bug? [19:39] Laney bug 245898 [19:39] Launchpad bug 245898 in isns "isns fails to config with dpkg" [Medium,Confirmed] https://launchpad.net/bugs/245898 [19:42] Laney: cool.. I have a package I would like reviewed and sponsored.. also, upstream has just released a new minor-version.. I wonder if it's worth uploading the new version packaged as well.. :S [19:42] pschorf: Looks good, except you need to target to Jaunty and not intrepid [19:42] I trust you tested that it worked? [19:42] i.e. the old package exhibits the bug and the new one doesn't [19:43] erm, no [19:43] :( [19:43] hang on [19:43] heh [19:43] also, was there already a patch system implemented? [19:43] i didn't think so [19:44] i just manually made the patch [19:44] pschorf: in the changelog it should be LP: instead of Closes:, and modifying something inside debian/ shouldn't be done through a patch system [19:44] oh, I missed the debian/ [19:44] yeah, just edit that directly [19:44] Ok. [20:02] There are a couple of bugs in tvtime I fixed on my local box. Seems it's unmaintained upstream. I've browsed around the MOTU wiki a bit, but didn't find all the answers yet [20:02] Are bugs fixed in Debian first, then ubuntu? [20:02] Ideally yes. [20:03] Is there a Debian / ubuntu VC repository somewhere for tvtime? [20:03] Sometimes we fix it here and then send the patch to Debian. [20:03] ok [20:03] Laney, Adri2000: I think I've fixed your concerns, can you look at the updated one at http://www.pastebucket.net/0cr1gf [20:03] I'm guessing there's just the tarballs, no VC (CVS, SVN / whatever)? [20:03] pschorf: Don't change s-v [20:04] other than the original tvtime CVS on SF, that is [20:04] pschorf: Target to jaunty [20:04] but it's not obvious that I haven't just missed some repo somewhere [20:04] Laney: do I need to have a jaunty environment set up to do that? [20:04] pschorf: that was my next question, too :-) [20:05] pschorf: You should at least have a jaunty pbuilder/sbuild environment [20:05] Although you can't test what you're building without running jaunty somewhere [20:05] ok [20:05] Amaranth: You can test a lot of things by logging into a chroot [20:05] what is sbuild? I don't think I've used it yet [20:05] But even if you're running jaunty you should still use pbuilder to build the package [20:06] pschorf: It does the same job as pbuilder [20:06] Hello, i'm new at packaging software/contributing, and wondering if there's a way to search for packages in launchpad, that needed to be updated. [20:06] tectroc: There's an "update" tag, and also http://qa.ubuntuwire.com/uehs/no_updated.html [20:06] if "new upstream" is what you mean by update [20:07] Laney, thanks. To target jaunty, is it sufficient to set up the pbuilder environment and build inside? [20:07] pschorf: Change it in the changelog, build it on Jaunty, test it on Jaunty [20:08] I guess it depends on the bug really [20:08] it'd be cheeky to not test an ALSA-related bug on jaunty proper [20:08] ok thanks [20:08] but another bug I was hoping to fix in tvtime is just about config files, seems a chroot would be enough [20:09] to test, all I need to do is install the package [20:09] is that a fair description of ubuntu policy? [20:09] is there a way I can do that in a jaunty environment without a full install? [20:09] pschorf: Install old package, make bug happen, install new package, check bug is gone [20:09] jjlee: There's no policy on this really [20:09] Laney, is there a way to do that in pbuilder or something? [20:10] Depending on where we are in the release cycle people are generally more or less strict about testing. [20:10] pschorf: You can log into a pbuilder with pbuilder --login [20:10] Laney: so it's considered OK to test bugs in chroot or old system where reasonable? [20:10] jjlee: Use your judgement really [20:10] right, thanks [20:11] pschorf: You probably want --bindmounts to make your built .deb available to the chroot too [20:11] re my version control question again: is there a way to reliably find all VC repositories for a given package? [20:11] all "official" ones, that is [20:11] jjlee: Should be in debian/control [20:11] you mean for the packaging, not for upstream? [20:13] Laney, what would I pass to pbuilder create to get a jaunty environment? [20:13] pschorf: https://wiki.ubuntu.com/PbuilderHowto [20:13] that'll be more helpful for you [20:16] Laney: mostly packaging, but both, really [20:17] jjlee: Well if the packaging is in VCS then it should be in debian/control [20:17] for upstream you generally have to look at their homepage [20:17] tvtime has no Vcs-* fields, so I guess it's safe to assume there are none [20:17] right [20:17] thanks [20:37] Laney, i'm still not quite clear on how to build the package and then install it...I can build it successfully with pbuilder build, but it disappears by the time i login [20:38] pschorf: You have to login with --bindmounts /path/to/result [20:38] then install it again [20:38] the result is in /var/cache, correct? [20:39] I think the default is /var/cache/pbuilder/result [20:42] One of the tvtime bugs I have in mind is the lack of ALSA support. There's been a patch around for a long time (which does not remove OSS support). [20:42] Would that be suitable for jaunty? [20:44] before feature-freeze, so I suppose yes? [20:44] Presumably it's just a question of whether anybody reviews and applies the patch...? [20:45] (after I file a bug) [20:45] Laney, everything tests out properly in pbuilder [20:45] should I add a new comment with the updated debdiff? [20:47] Hmm, according to this message, *everything* is going to be in bzr for jaunty: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-September/000481.html [20:47] has that happened yet? [20:47] jjlee: I think so [20:48] is there a wiki page or something that discusses the current state of these VC etc. developments in jaunty? [20:48] no idea :( [20:48] the ones he discusses in second-to-last paragraph in that message? [20:48] there is also a channel #bzr it is possible that they know more [20:49] see https://wiki.ubuntu.com/DistributedDevelopment/ [20:49] the bzr people are heavily involved in ubuntu? [20:49] pschorf: Write that on the bug with the new debdiff [20:49] bzr I am pretty sure is sponsored by the same organization which sponsors Ubuntu [20:51] I see [20:51] Laney, is this all I need to do for the patch? [20:52] jjlee: the wiki page Laney posted looked pretty interesting [20:52] pschorf: Right, the sponsors are already subscribed and they'll get to it in time [20:52] yeah, thanks Laney, I'm reading through the linked-to stuff now [20:52] Laney, thanks for all your help. [20:53] pschorf: You can forward it to debian using "submittodebian" from ubuntu-dev-tools [20:54] hey Laney are you MOTU? [20:54] emet: no [20:54] not yet, anyway... [20:54] okay [20:55] this bzr repo for every package thing sounds pretty cool [20:55] I guess anyone could branch a package? [20:56] emet: that's what MS was saying in that post [20:58] emet: See also https://wiki.ubuntu.com/BzrContributorHowto [20:59] this is pretty cool [21:08] does anyone know how to add a po file to gettext? [21:14] pschorf: Use xgettext, and its friends? [21:16] jmarsden|work, i was going to add the german translation for the nautilus image converter from gnome's SVN. Can I just add the file in dpatch and add it to LINGUAS? [21:16] add de.po, that is [21:17] Possibly... that is going to be package specific; it all depends what the makefile(s) do. You'll have to read and understand the Makefile(s) concerned to be sure. [21:18] Ubuntu has it's own translation system, so I don't think adding it to the package actually works. [21:54] I hope this means somebody's working towards committing changes to the source itself rather than to the debian/ directory: https://wiki.ubuntu.com/NoMoreSourcePackages [22:13] jjlee: Why? Patches are a lot more understandable than undifferentiated diff in the source. [22:14] but it's easy to get the diff, right? [22:14] once it's in VC [22:14] it's easier to edit plain old source than on patches [22:15] the idea seems to be to use something similar to stacked-git to represent the patches in the VC repository [22:15] so the concept of patch is still there [22:15] Using the common patch systems in Debian/Ubuntu editing patches directly is almost never necessary. [22:15] (in addition to the concept of a commit / changeset) [22:15] Only if you have access to the vcs. It's not present in the source package any more. [22:16] what source package? See title of wiki page [22:16] Well that's a long ways down the road. [22:16] "Using the common patch systems": I thought the idea was to make maintaining packages easier? [22:17] If so, obsoleting some of the mountain of Debian odds and ends would be a good thing [22:17] If your comfortable using bzr, I'm sure it is/will be. [22:17] sure, a long way down the road is fine [22:18] In favor of an Ubuntu odd and end doesn't seem like progress, but that's just me. [22:18] being comfortable with systems like bzr is a transferable skill that solves a more general problem [22:18] VCS has advantages, but it's not pure win. [22:18] Right, so using something that's not virtually Ubuntu unique. [22:19] many people (cough) think that a lot of the Debian / ubuntu packaging stuff fills a much-needed gap [22:19] right [22:20] the community seems more valuable than the tools [22:23] Getting the packaging in a VCS is a long term win if we do it smart. [22:23] yes, it looks promising [22:38] rate my new site !! http://www.hardstylersunited.dk/ [22:38] That works too. [22:38] lol === santiago-ve is now known as mauler === mauler is now known as santiago-ve === ScottK-desktop is now known as ScottK3 === emgent is now known as emgent` === emgent` is now known as emgent`e === emgent`e is now known as emgent