/srv/irclogs.ubuntu.com/2011/05/27/#ubuntu-devel.txt

=== william is now known as Guest90482
=== Guest90482 is now known as wcchandler
=== dendrobates is now known as dendro-afk
=== kenvandine_ is now known as kenvandine
=== carif_ is now known as carif-offsite
=== asac_ is now known as asac
pittikees: thanks for adding me back05:27
pittigood morning05:27
elmo005:34
=== dendro-afk is now known as dendrobates
=== _LibertyZero is now known as LibertyZero
cpatrick08i think oneiric will be better than natty even in this very early stage of development it is better than natty06:33
cpatrick08is there any way to get the gnome-shell on oneiric06:49
didrocksgood morning07:11
mdkedoes anyone have an idea what might be causing bug 788949. I've seen a couple of them for ubuntu-docs but have no idea what the dpkg error message means08:00
ubottuLaunchpad bug 788949 in ubuntu-docs (Ubuntu) "package ubuntu-docs 10.10.4ubuntu0.1 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/gnome/help/keeping-safe/vi/keeping-safe.xml': Input/output error" [Undecided,New] https://launchpad.net/bugs/78894908:00
=== dendrobates is now known as dendro-afk
gesermdke: looks like the harddisk is dying if I read the dmesg correctly08:08
mdkegeser: aha, what do I look for in there? I have a couple of other similar bugs that I need to check too08:10
gesermdke: see the lines with "sd 0:0:0:0" and "ata1.00" at the end of dmesg.txt where the kernel logs it unsuccessfull attempts to write something to the harddisk08:12
mdkegeser: that's great, thanks a lot for the help08:13
=== tkamppeter_ is now known as tkamppeter
=== smb` is now known as smb
DktrKranzmvo: hi! I checked your branch yesterday, it looks good. I also tested it with a GNOME3 box, and worked fine08:30
mvoDktrKranz: awsome, thanks a lot, sounds like a candidate for uploading then :) what is the state of the gir stuff in debian? is it in unstable yet or would this be experimental?08:36
DktrKranzmvo: still experimental, there are some pieces still to be fixed, and release team to assign a spot to schedule transitions08:37
DktrKranzprobably, it won't happen before 3.208:38
DktrKranzsome pieces are in unstable, but at least not vte. so experimental is the only way right now08:39
Laneybroder: No, I didn't. But it looked OK to me (since there are no rdepends and the reporter says he test it runs)08:45
Laneytested08:45
mvoDktrKranz: ok, thanks. that should be fine, I guess its best to push it in ubuntu first then so that it gets wider testing (but I feel its pretty solid)08:46
micahggood morning pitti, would you be able to pocket copy chromium from -proposed to -security/-updates for lucid-natty, bug 78784608:56
ubottuLaunchpad bug 787846 in chromium-browser (Ubuntu Natty) "11.0.696.68 -> 11.0.696.71" [High,Fix committed] https://launchpad.net/bugs/78784608:56
pittimicahg: yes, can do08:59
cjwatsonmdke: I've no idea why we still file bugs for "Input/output error" - it's defined to mean physical read/write errors, i.e. almost exclusively not software bugs08:59
micahgpitti: thanks08:59
DktrKranzmvo: sounds good. we could also asking for testing via planet debian, I see it attracts more people09:00
cjwatsonI assume it's simply because at the apport level it's awkward to figure out reliably which errno was involved, e.g. due to translations09:00
pittimicahg: all done09:03
micahgpitti: great, thanks, have a good day09:03
=== htorque_ is now known as htorque
zaytsevhi! does anyone know of the top of their head, how the livecd decides if it will autologin in casper or show the dialog "install or try ubuntu blah-blah-blah"?10:03
cjwatsonzaytsev: the 'maybe-ubiquity' boot parameter causes the latter to happen10:04
zaytsevI am trying to remaster the official natty livecd as per LiveCDCustomization wiki page and everything was fine, but now I updated the packages in the chroot and somehow the resulting image autologins without showing this standard window10:04
zaytsevcjwatson, oh, thanks! it means that somehow I unknowingly changed the boot options :-/10:05
cjwatsonzaytsev: our gfxboot theme adds 'maybe-ubiquity' if it's booting in splash mode, which happens if 'hidden-timeout=1' is in /isolinux/gfxboot.cfg10:07
cjwatsonit's a bit convoluted, I'm afraid10:07
infinityJust a tad...10:08
infinityI know how it works, and that still confused me. :P10:08
cjwatsonit confuses me and I wrote it10:08
zaytsevoh right, so I have hidden-timeout=2 in gfxboot.cfg, I didn't change it though. It was like this in the official media.10:08
cjwatson=2 should be fine too10:09
StevenKinfinity: What's wrong with Canadian lamb? :-)10:09
infinityStevenK: A general lack thereof.10:09
infinityStevenK: Canadian ranchers are silly and keep letting them grow up.10:09
infinityStevenK: And mutton is crap.10:09
cjwatsonzaytsev: also I don't think it will take you into the try/install dialog if you press a key at the CD boot splash screen to get the boot menu10:09
zaytsevnah, I didn't press a key and still it autologins :-/ I am trying to boot my kvm test vm off the official media and it shows the prompt. when I do the same with my remastered one it doesn't. and now that I sort the files by date the only thing that really changed is the chroot which I updated with the latest packages from natty-updates. what a looser...10:13
cjwatsonzaytsev: you could just hardcode maybe-ubiquity into the kernel parameters10:14
cjwatson(kind of wrong, but whatever)10:14
ftadoko_, hi, here are my ld-gold results: http://paste.ubuntu.com/613663/10:15
ftadoko_, i wonder if it has to do with the PIE hardening10:16
doko_fta: ok. please cc kees on hardening issues too10:16
apwev, are you aware that usb-creator-gtk is now triggering 4-5 "not permitted by policy" popups per install ?10:22
zaytsevcjwatson, so I should add maybe-ubiquity to the first (default) boot option in /boot/grub/loopback.cfg ? and how to reliably achieve the opposite effect, is there something like no-ubiquity ?10:23
zaytsevthe thing that bugs me here is that I updated the chroot and now it autologins. tomorrow I will do this again and it will show ubiquity instead. I would kind of like a defined behavior.10:23
evapw: yeah, it was to fix a security issue.  I plan to dig into making it less of a pain in the ass a bit later in the cycle10:25
apwev, eek10:25
cjwatsonzaytsev: wait, you're using grub to boot this?10:27
zaytsevcjwatson, I have no idea :-) I have downloaded the original image and use whatever it uses. then I found an article on Ubuntu wiki how to unsquashfs the filesystem and make your customizations (install/update packages). then I remastered the image again using the updated chroot10:28
zaytsevalso, the difference is that when the image that boots to ubiquity starts, it changes purple background to black and yellow letters and when it autologins directly it stays purple10:29
cjwatsonzaytsev: /isolinux/isolinux.cfg, then10:30
cjwatsonzaytsev: if I were you, rather than just comparing file lists, I would loop-mount the old and new images and use 'diff -ru' to compare them10:30
cjwatsonone of the changes listed by that will be responsible10:30
zaytsevcjwatson, in isolinux.cfg I would just add a line that says maybe-ubiquity ?10:31
infinitydiff -ruN even, could be a new file poviding an override to something.10:31
zaytsevcjwatson, ok, reasonable I will do that. thanks.10:31
cjwatsonzaytsev: sorry, I meant /isolinux/txt.cfg.  change the 'append' line corresponding to the relevant menu label.  (but analyse the image with diff first; this is just a fallback option for if you can't find what changed.)10:33
private_I am looking for a programmer to hire to clean up some code10:34
zaytsevhmm, manifests are different (updated packages), filesystem size, filesystem AND /isolinux/isolinux.bin has a different checksum. weird.10:37
zaytsevand compared to the original image, there are even more differences. I wonder it it's rsync's fault, maybe I called it with the wrong flags. ok, will try to figure after lunch10:40
zaytsevactually, it seems that the md5sum generation command is wrong10:42
zaytsevfind -type f -print0 | sudo xargs -0 md5sum | grep -v isolinux/boot.cat | sudo tee md5sum.txt <--- should be grep -v isolinux, because the original md5sum doesn't include any of the isolinux stuff.10:43
zaytsevhttps://help.ubuntu.com/community/LiveCDCustomization10:44
* doko_ looks away from NBS10:45
jibelpitti, are these files useful on the ISO ? http://paste.ubuntu.com/613655/10:52
jibelpitti, The raw size is 25MB but that would save something like 3 to 4MB of CD space10:52
pittijibel: apt lists are, I think10:52
pitti4.3M 2011-05-27 10:22 srcpkgcache.bin10:52
pittithat's something I keep asking mvo about10:53
pittiwe just ditched it in a project, and it doesn't seem to be very useful10:53
pittibut I keep forgetting why we need it10:53
jibel*bin files are regenerated on first run of apt10:53
pittiright, we could remove it from the CD certainly10:54
pittiand I think the dpkg -old files can certainly go10:54
pittijibel: thanks for pointing these out!10:55
jibeland apt list files are regenerated on first run of apt-get update.10:55
pittithese are pretty much "nice to have", if you do an apt-get install etc.10:55
pittiin the live system10:55
didrocksmaybe we can run an apt-get update as soon as internet is available?10:56
didrockson the live/ubiquity10:56
didrocks(well s/internet/any network/)10:56
jibelif you don't have an internet access you only need cd rom list, if you have one we can run an update at some point10:57
pittiright10:57
geserhmm, if available-old is 1.3M, I guess available is around the same size. What was the purpose of available again?10:58
jibeland since the update timestamp on the CD is far behind the time the user actually uses the CD, update-manager will propose to run a check anyway10:58
cjwatsonjibel: that's already going away with live-build10:58
cjwatson(pkgcache.bin etc.)10:58
cjwatsonno point analysing the current CD10:58
cjwatsonthe -old files go away with live-build too10:58
pittinice10:59
jibelcjwatson, oh cool, not analyzing the CD, just playing with the freshly backed isos, and found this.10:59
superm1cjwatson, there's a plan to switch to live-build for this cycle?11:05
cjwatsonyes11:06
cjwatsonhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-o-live-build11:07
ohsixis live build cooler than casper and sealing up your own images11:07
cjwatsonlive-build and casper are apples and oranges11:07
ohsixok11:07
ohsixlast time i looked it was casper, dunno what's on live images now11:08
superm1ah v. good thanks.11:08
cjwatsonohsix: casper stays where it is.  live-build replaces livecd-rootfs.11:08
ohsixi see11:08
cjwatsonas would be clear if you'd looked at my URL11:09
ohsixdid11:10
ohsixno idea what role that stuff plays, going to read about livecd-rootfs11:10
=== MacSlow is now known as MacSlow|lunch
zaytsevcjwatson, Binary files image-orig/isolinux/boot.cat and image-new/isolinux/boot.cat differ, Binary files image-orig/isolinux/isolinux.bin and image-new/isolinux/isolinux.bin differ, is that normal when re-generating the ISO file?12:36
zaytsevI checked up on isolinux.bin and it shows one bit flipped: http://paste.ubuntu.com/613701/12:37
zaytsevare these cosmic rays or what?12:37
cjwatsonI think it probably depends on your installed syslinux(-common) packages12:38
zaytsevoh, I'm on maverick, and re-generating image from natty, but I'm just using mkisofs, I don't even have syslinux installed. I'm not doing the bootstrapping from scratch12:39
zaytsevand also same 82 -> 83 byte flipped in boot.cat12:42
cjwatsonI don't know if that's relevant, anyway12:43
cjwatsonit may just be because the rest of the ISO is different and so mkisofs needs to fiddle with the catalog12:43
zaytsevI think it's mkisofs, because the file has the modification date is when I ran it12:43
cjwatsonI doubt it's relevant to your problem12:45
zaytsevwell, all the other changes that diff picked up are in package lists (updated packages) and squashfs file system12:49
zaytsevso it can only be the file system, but that's a bit big to diff :-(12:50
zaytsevok, I added append  file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash maybe-ubiquity -- to live12:58
zaytsevit still logins directly12:58
cjwatsonare you sure you still have ubiquity in your squashfs?12:59
cjwatson(at this point, I would loop-mount the squashfses and diff them, particularly /etc)12:59
zaytsevand when I press esc on boot it shows my modified commandline. so this is fine.12:59
zaytsevno I am not sure, although I didn't remove it. will do as you say. thanks.13:00
zaytsevdiff -Naur on etc only revealed differences in fs-old/etc/ld.so.cache fs-new/etc/ld.so.cache... hmmm. will do whole fs.13:03
zaytsevhopeless, there was a libreoffice upgrade, so the diff is polluted by 200 mb of binary files :-(13:09
mdeslaur@pilot in13:09
=== udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: NCommander, mdeslaur
zaytsevhere are the updated packages: http://paste.ubuntu.com/613720/ ... I don't see anything dangerous in here.13:14
zaytsevcould it have to do with motd? I changed the motd.13:15
cjwatsonno ...13:18
=== MacSlow|lunch is now known as MacSlow
zaytsevis there like a way to debug stuff?13:19
zaytsevI now see it's being launched by upstart13:20
zaytsevthe file /usr/bin/ubiquity-dm is in place13:20
zaytsevok, I have an idea of what could have gone wrong13:21
zaytsevmaybe it's initctl, there was an advice to add a diversion on the wiki, maybe I screwed it up13:22
cjwatsonyou'd certainly need to undivert that at the end of the build13:22
zaytsevI'VE GOT IT~!, it's initctl. somehow in the new image it doesn'13:23
zaytsevexist anymore at all. maybe I ran some command twice13:23
zaytsevmany thanks for all your help13:23
zaytsevI learned a lot13:23
cjwatsonglad you got it sorted13:24
ftadoko_, I tried ld.gold on natty without PIE, it still crashes.13:55
tkamppeterAny UDEV expert around? Is there some mechanism which removes files from /etc/udev/rules.d/?13:56
tkamppeterpitti, ping13:56
pittihey tkamppeter13:56
pittitkamppeter: how do you mean, mechanism? there are standard recipes for removing obsolete conffiles, yes13:56
tkamppeterpitti, what I do is connecting an HP LaserJet 1020 (the ugly thingy which needs firmware loaded).13:57
tkamppeterpitti, this triggers the command "sudo hp-plugin" to be run and this installs a bunch of fresh files into /etc/udev/rules.d/. You can try "sudo hp-plugin" manually and then see what you get in /etc/udev/rules.d/.13:58
pittier,what?13:58
pittian udev rule calls sudo?13:59
pittino, I don't think I'll run a program like that13:59
tkamppeterpitti, probably the rule does it without sudo.13:59
tkamppeterpitti, the rule simply runs hp-plugin.13:59
tkamppeterpitti, now I check whether the newly installed rules in /etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules actually load the firmware into the printer.14:00
pittihm, I only see /lib/udev/rules.d/56-hpmud_support.rules14:01
pittitkamppeter: how does the file get there?14:01
tkamppeterpitti, these rules get installed if you run hp-plugin.14:01
pittiso we have an udev rule which calls hp-plugin which installs udev rules into /etc/?14:01
tkamppeterpitti, so run "sudo hp-plugin" on a console and you get the files.14:02
tkamppeterpitti, they get into /etc because HP does it this way.14:02
pittican we please kill hp-plugin?14:02
tkamppeterpitti, and how do we support these printers then?14:03
pittiand perhaps just ship the sensible part of their rules directly in hplip, in /lib/udev/rules.d/14:03
pitti?14:03
tkamppeterpitti, we must support rules in /etc, to support third-party software.14:03
pittiyes, but hplip is not a third-party software, it's an Ubuntu package14:03
cjwatsonhaving udev rules themselves go around installing udev rules is a different matter, though!14:04
pittiwhich aren't supposed to install rules into /etc/udev/rules.d14:04
pittiand as such it shoudn't do crazy things like that14:04
pittiright, what cjwatson says14:04
tkamppeterpitti, but the proprietary driver plugin of HPLIP is a third-party software, as it gets installed separately.14:04
pittitkamppeter: how is that related to the initial rules?14:05
tkamppeterpitti, the initial rules which we ship in /lib are 100% OK.14:05
pittitkamppeter: what are the rules that hp-plugin installs doing?14:05
tkamppeterpitti, the rules which get installed by HP's proprietary plugin are doing the auto-upload of firmware into HP's cheapo lasers.14:06
tkamppeterpitti, the problem which I am experiencing is that these rules get executed once (the first time when I power-cycle the printer) and after that the rules file (only the one for my printer) gets removed.14:08
geserwho removes them?14:09
tkamppetergeser, pitti, I do not know.14:09
geserhopefully not the script doing the firmware upload14:10
pittican we stilll kill hp-plugin, or the part of it that does the crazy rules install?14:10
cjwatsonnothing in the standard distribution should be removing files in /etc/udev/rules.d/.  However, given that you already have a crazy thing automatically installing rules into /etc/udev/rules.d/ (rather than using a single static rule which uses IMPORT or something to import properties from a program), all bets are off14:11
pittitkamppeter: so, to get back to your original question, we certainly don't have a "standard mechanism" to remove any files from /etc, as this is EBW14:12
tkamppetergeser, pitti, the script gets removed exactly after its first use. After having run "hp-plugin" and completed the wizard I wait some seconds and power-cycle the printer. The printer loads its firmware and the /etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules is gone. All other 86-hpmud-hp_*.rules files stay.14:13
pittiso I guess the rules that it puts into /etc/ have a builtin auto-destruct and delete themselves?14:14
tkamppeterpitti, here is the rules file: http://paste.ubuntu.com/613748/14:15
pittiso, apart from them using an outdated syntax, it seems that /usr/bin/hp-firmware removes them?14:16
tkamppeterpitti, /usr/bin/hp-firmware is a Python program and I do not find anything in it which deletes the UDEV rule.14:20
tkamppeterpitti, I have copied 86-hpmud-hp_laserjet_1020.rules into /lib/udev/rules.d/ now and there it survives. I can do as many power-cycles as I want and the file survives and every time the firmware gets uploaded.14:23
tkamppeterpitti, is there a way to find out which program has deleted a file?14:26
hallyn_afkseriously, people, "Development is completed for the 'natty' version of Ubuntu, so you should use technical support channels unless you know for certain it should be reported here?' is not a question14:28
=== hallyn_afk is now known as hallyn
Laneywhat?14:29
hallynkirkland: thanks for the quick byobu (uh, screen) fix :)  now lemme see if i can reliably reproduce it before upgrading14:32
tkamppeterpitti, still there?14:33
pittitkamppeter: not retroactively; you could grep your entire file system for files which contain the name, though14:44
=== victorp_ is now known as victorp
gesertkamppeter: try setting the rules file in /etc to immutable and check if something complains that it couldn't remove it14:52
pittiI thought nothing would remove it again?14:52
pittiand this is entirely after-the-fact debugging?14:52
tkamppetergeser, how does one set /etc/ to immutable?14:53
gesertkamppeter: not the whole directory but only /etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules14:54
gesersudo chattr +i /etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules (as long as the file exists)14:54
tkamppetergeser, the "chattr +i" actually protects the file, but I did not see any error. Nothing in syslog.14:58
geserhmm14:58
geserthen I'm out of ideas15:02
pittifew programs actually check the result of unlink()15:02
tkamppeterpitti, I have also two other files in /etc/udev/rules.d/ which seem to be generated by programs from our distro: 70-persistent-cd.rules and 70-persistent-net.rules.15:03
pittiI'd go with grepping the file system for "86-hpmud-hp_laserjet_1020.rules"15:03
pittimight take ages, but it's effective15:03
pittitkamppeter: those are expected15:03
tkamppeterpitti, I have started the search now.15:06
jibelev, can you look at bug 789152 when you have a minute or maybe that's expected at this stage of the release.15:08
ubottuLaunchpad bug 789152 in ubiquity (Ubuntu) "When booting an ISO, "try or install" dialog doesn't start" [Undecided,New] https://launchpad.net/bugs/78915215:08
cjwatsonjibel: dup of bug 788859?15:08
ubottuLaunchpad bug 788859 in ubiquity (Ubuntu Oneiric) "3D session selected even if not supported; availability of 2D session not obvious" [High,Fix committed] https://launchpad.net/bugs/78885915:08
evalmost certainly is a duplicate15:08
cjwatsonev: (are you planning to upload ubiquity today, BTW?)15:09
charlie-tcajibel: I tried yesterday from the cd menu to just get to a live desktop in VBox, and got the same screen with top and bottom panels15:09
evcjwatson: yes15:09
charlie-tcaThere was no icon to install, though15:09
cjwatsonexcellent15:10
evmore towards EOD though, might see how well this pygi stuff works15:10
evbut probably without that merged in15:10
kirklandhallyn: its only a partial fix15:12
kirklandhallyn: but you should be okay, as long as you don't split screens15:12
kirklandhallyn: i need to cherry pick a couple of patches from git against screen to get the real fix going15:12
kirklandhallyn: but before doing that, I need a way to reproduce it ;-)15:13
jibelcjwatson, yes maybe, but I was unsure because on this report there's a mix of "try/install" doesn't start and some 3D/2D bits with "oh no" dialogs, that's a bit confusing.15:16
tkamppeterpitti, geser, I did more tests: I renamed the file to /etc/udev/rules.d/00-x.rules and did NOT make it immutable and it survives. After having done so I have created an empty file /etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules and after the rules which are actually in 00-x.rules being executed the file 86-hpmud-hp_laserjet_1020.rules gets removed, 00-x.rules still surviving.15:22
infinitytkamppeter: Sounds like a recursive grep of doom is in your future.15:24
tkamppeterpitti, any file fitting the mask ??-hpmud-hp_laserjet_1020.rules gets removed.15:32
hallynkirkland: yeah i can't reproduce it...  (and i dno't split screens)15:33
pittitkamppeter: ah, so extend your grep to search for "hpmud-hp_laserjet_1020"?15:33
kirklandhallyn: darn15:38
hallyni assume a flaky connection is the key15:38
pitticjwatson: I assume it's ok for you if I steal the gnome-python merge from you?15:47
cjwatsonpitti: absolutely, I think I marked it as "feel free to take" on MoM15:51
=== Quintasan_ is now known as Quintasan
doko_sladen: ping15:56
ogra_pitti, any idea why the WI tracker didnt pick up all specs for ubuntu-armel yet ?16:29
ogra_they should all be in approved state, targeted to oneiric and have a priority set16:29
ogra_so i dont get why http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html isnt picking them up16:30
james_wogra_, have an example of one that isn't showing up?16:31
ogra_https://blueprints.edge.launchpad.net/ubuntu/+spec/other-o-arm-netinstall16:32
ogra_and all the others from https://blueprints.edge.launchpad.net/~davidm?searchtext=o-arm16:32
pittiogra_: it's just proposed for oneiric, not accepted16:33
james_wogra_, "Proposed for oneiric", it needs to be accepted16:33
ogra_davidm_, ^^^16:33
ogra_davidm_, you need to accept all our specs for oneiric16:34
ogra_approving isnt enough16:34
loolHmm language-support-en isn't in the archive anymore; are these deprecated?16:34
lool(and language-support-writing-*)16:34
davidm_ogra_, working it now16:34
ogra_davidm_, thx16:34
davidm_Sorry missed that step16:34
ogra_me too16:34
pittilool: yes, they're gone16:34
ogra_else i would have shouted earlier :)16:35
pittilool: https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-clean-up-language-support FYI16:35
loolpitti: thanks16:35
pittilool: we have had the split l-support-* and the dynamic check-language-support for a while, but that's a bit of a mess16:35
=== dendro-afk is now known as dendrobates
loolpitti: Ok; makes sense16:37
lool(more dynamic language support)16:37
kirklandpitti: finally just started using lp-project-upload :-)16:39
kirklandpitti: awesome :-)16:39
pittikirkland: :)16:39
kirklandpitti: i have wasted too many clicks, for too long16:39
kirklandpitti: question for you...  is it possible to pass the changelog as stdin or a file argument, or something?16:39
kirklandpitti: i can easily carve that out of my debian/changelog, from the top entry16:40
pittikirkland: hm, haven't tried that; I just :e them in vim, and then edit them a bit16:40
Bagatellewho can help me with this? A username and password are being requested by http://localhost:49810. The site says: "bookmarkable-user-auth"16:40
kirklandpitti: yeah;  i take care to maintain my debian/changelog so that it doubles as my upstream release changelog16:40
Bagatelleit seems there are problems with a port, but I dont know anything else16:41
kirklandpitti: if i patch lp-project-upload to optionally take the changelog text on STDIN, would you accept that change?16:41
pittikirkland: of course; it's in ubuntu-dev-scripts, have at it :)16:41
kirklandpitti: ie, if there's input on STDIN, use it as the changelog text?16:41
kirklandpitti: sweet, thanks16:41
pittikirkland: just keep in mind that there's two editors -- one for changelog, one for release notes16:49
pittiyou can add options for both, and allow one to be '-'16:49
kirklandpitti: right16:50
kirklandpitti: i was wondering how to handle that16:51
pittigood night everyone, have a nice weekend!16:51
kirklandpitti: i only ever use changelog, and always leave releasenotes16:51
kirklandblank16:51
pittikirkland: you could do --changelog --notes /dev/null or so16:51
kirklandpitti: yeah16:51
pittior --notes ''16:51
kirklandpitti: that would work16:51
kirklandpitti: i'll get to it16:52
kirklandpitti: thanks for the awesome tool;  i feel dumb for not having used it before :-)16:52
pittikirkland: so you'll use some dpkg-parsechangelog | sed | lp-project-upload chain?16:52
pittikirkland: heh, one day I got so fed up with the 20 clicks you have to do, that I just wrote it16:52
pittiand since then I'm actually making more releases, as it's a lot less painful16:52
kirklandpitti: yeah, something like that16:52
kirklandpitti: currently, i'm using:16:53
kirklandgrep -B 10000 -m1 '^ \-\- ' debian/changelog16:53
pittiheh, that'd work16:53
kirklandpitti: yeah, it gets me what I want16:53
kirklandpitti: see bikeshed's 'release' and 'release-build' scripts16:53
kirklandpitti: it's the two scripts I use to release and publish 20+ upstream projects and packages16:53
pittiah, grep -B, clever16:53
kirklandpitti: i use a standard naming scheme for all my projects/packages16:54
pittiI had used sed -n '/^ --/ q; p' or so16:54
kirklandpitti: always register both the team name and the project name in LP16:54
kirklandpitti: always create a ppa16:54
kirklandpitti: and when I release, I always release backports of the package to PPA for each of the supported ubuntu releases16:54
pittikirkland: I have "do-release" scripts, too, with that I could actually integrate the uploading as well16:54
kirklandpitti: so people can track ppa:powernap/ppa for current powernap on older ubuntu releases16:55
kirklandpitti: this is my step 1: http://paste.ubuntu.com/613820/16:55
kirklandpitti: release-build ^16:55
kirklandpitti: and my step 2 is http://paste.ubuntu.com/613821/16:56
kirklandpitti: release ^16:56
pittiI bet if we throw together everyone's release scripts, everything would be fully automatic16:56
pittiwell, build recipes in LP certainly went a long way towards automation16:56
mdeslaur@pilot out17:04
=== udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: NCommander
slangasekdoko_: you comment that the rpcbind dependency is "still outstanding" for the nfs-utils merge, but there's an MIR for it?17:08
cjwatsonsmoser: I already had a busybox merge partly done :-(17:28
cjwatsondo I have to reconcile it all now?17:28
cjwatsonthat's about twice as much work as just doing it (I was touched-it-last)17:28
smosercjwatson, bah. sorry.17:29
smoserwell, you can take a look at my diff. i think it is done. but if you want to pitch it, feel free.17:29
smosersorry for not asking first.17:30
smosertake a quick look, and if it doesn't look like you think it should, then ditch it.17:30
smoseri pretyt throughally went through all the changes from debian and made sure that everything in the changelog delta list was accounted for and that nothing else really was.17:31
smosertheres a ppa build of my merge at https://launchpad.net/~smoser/+archive/ppa/+packages17:42
=== dendrobates is now known as dendro-afk
smoseris 'lsb-release -is' the "right way" to determine if this release is ubuntu versus if it is debian ?18:23
j1mcdpm: i'm not sure if you're the right person for this, but the openstack team just updated some of their site, and they18:23
j1mcthey've done some interesting stuff on their community page: http://www.openstack.org/community/18:24
j1mci like the 'developers in action' bit that shows real-time commits18:25
j1mcthey use launchpad, so i'd be curious to know how they did that.18:25
j1mc... just thought i would pass that along18:25
=== hallyn is now known as hallyn_afk
ScottKsmoser: I think dpkg-vendor is preferred.18:51
ScottKThat avoid a need for an lsb depends.18:52
smoserScottK, well that comes from dpkg-dev which is 'optional' in debian18:55
macosmoser: but build-depends pulls it in18:55
macoerm i mean18:55
macobuild-essential18:55
smoseryeah, in ubuntu its probably goign to be there. but my interest was in getting something into 'jigit' to take a different path if "this is ubuntu"18:57
slangasekbuild-essential isn't going to be pulled in on the runtime19:02
slangaseklsb_release is preferred for that - you don't even need to depend on it really, if the command is missing you can just assume Debian19:03
slangasek(since it's part of ubuntu-minimal)19:03
slangasekbarry: --package-merge> duuuude19:08
slangasekwhen'd that get there?19:08
sladendoko_: dong19:13
barryslangasek: dunno, but i just found out about it yesterday!19:16
=== hallyn_afk is now known as hallyn
janimojames_w, thanks for fixing up my BPs whiteboard ! I completely forgot LP ID is to be used19:50
james_wnp19:50
petarwhy is update-initramfs executing scripts i put into /etc/initramfs-tools/scripts/* ?  i thought thats what hooks/* is for?20:13
petar(thats on 11.04)20:13
slangasekpetar: you're correct, that is the difference between hooks and scripts; I haven't heard of this issue you describe20:17
petarslangasek: i have one script in scripts/init-bottom and after every update-initramfs it gets executed..  and it doesn't get executed during a subsequent boot.. i remember that feature working pretty well on 9.1020:19
slangaseka brief scan of 11.04's initramfs-tools code doesn't show me anything that explains why this would be20:20
slangasekcan you trace it?20:20
petarto be honest i cant even see where this scripts stuff comes into it when reading update-initramfs20:21
* slangasek nods20:22
petarthere is not much sourcing either..20:22
petari need to eat something.. will try again, when i'm back20:25
=== Quintasan_ is now known as Quintasan
=== dendro-afk is now known as dendrobates
NCommander@pilot out20:47
=== udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
NCommanderoops20:47
petarslangasek, its called cache_run_scripts and i have no idea why mkinitramfs uses that to run my scripts on update-initramfs -u21:23
petarit seems that i could set NOEXEC but how can i set something that i dont understand in order to solve something that i dont understand either? ;)21:24
slangasekpetar: oh, yes, because it's trying to query the scripts to find out what their dependencies are21:26
slangasekpetar: does your script not handle the 'prereqs' option?21:27
petarhmm, no, i thought i have no prereqs so...21:29
slangasekright; but initramfs-tools still needs to call it with prereqs to find that out, so the script has to behave sensibly when this is done21:29
petaraaaa.. i see now.21:30
slangasekthe only new behavior here is that we do this at update-initramfs time, to cache the order once instead of having an expensive query on every boot21:30
petarok, i'll add that.. makes sense.21:31
petarthanks for your help!21:31
slangaseksure :21:31
slangasek)21:31
petarvery good, seems to work now21:33
=== dendrobates is now known as dendro-afk
slangasekbdmurray: looking at bug #781874 still; is your thought that this should supersede the SRU currently in -proposed, or that that one should be published to -updates and the new one uploaded?21:50
ubottuLaunchpad bug 781874 in aptdaemon (Ubuntu Natty) "<type 'exceptions.TypeError'>: __init__() takes exactly 2 arguments (1 given)" [High,In progress] https://launchpad.net/bugs/78187421:50
bdmurrayslangasek: is the order important?22:37
slangasekbdmurray: it impacts what -v option needs to be passed when uploading; I don't have a preference per se22:38
bdmurrayslangasek: well the one in proposed has been there for quite some time now22:40
slangasekyep, apparently without verification22:41
bdmurrayand without testcases22:41
broderScottK: do you have thoughts on bug #787383? since u-d-t 0.124 introduces a versioned dependency on a current version of devscripts, dholbach's suggestion to just backport the bitsize bugfixes makes sense to me, but i'd like a second opinion22:42
ubottuLaunchpad bug 787383 in natty-backports "Include bitesize script in ubuntu-dev-tools" [Undecided,New] https://launchpad.net/bugs/78738322:42
bdmurrayI wrote a bug pattern for 781874 already so either way is fine with me.  I just didn't want the fix not making it into Natty.22:43
slangasekwell, let me prod the bugs to see if we can get a test case22:44
slangasekno sense in uploading the next SRU either way if it's going to stay wedged forever on verification of the current SRU bugs22:45
slangasekstgraber: do you happen to have a reproducible test case for bug #742935?22:49
ubottuLaunchpad bug 742935 in aptdaemon (Ubuntu Oneiric) "aptd crashed with OSError in release(): [Errno 9] Bad file descriptor" [High,New] https://launchpad.net/bugs/74293522:49
=== JayFo is now known as JFo
psusiis there someone I need to poke to activate my universe-contributors membership?23:12
ScottKbroder: I think just backporting bitesize makes sense.23:24
bdrung_psusi: normally the chair of the meeting23:24
bdrung_psusi: feel free to poke him23:25
psusihrm.. seems the minutes haven't been posted yet23:27
psusiand the irclogs for ubuntu-meeting are empty...23:28
psusierr, oops, that was lp-meeting23:28
psusicjwatson, bug #770600 has been waiting for a while now for a sponsor, could you handle it?  it's a release regression in dmraid from the 64bit pdc patch that I added... branch proposed to simply disable the patch.23:33
ubottuLaunchpad bug 770600 in dmraid (Ubuntu) "22_add_pdc_64bit_addressing.patch: breaks some pdc raid sets" [High,In progress] https://launchpad.net/bugs/77060023:33
psusippa tested and fix verified by multiple users23:34
stgraberslangasek: nope23:38
cjwatsonpsusi: it's end of week for me now, but my patch pilot day is coming up so I'll handle it then if not before23:38
cjwatson(it's 23:38 here)23:38
psusicjwatson, cool23:39
slangasekstgraber: k; was worth a shot23:40
cjwatsonI'm only still here because I was finishing up debugging bug 728088 in order to release a kind user's test machine23:40
ubottuLaunchpad bug 728088 in open-iscsi (Ubuntu Natty) "iscsi root with or without auth fails to boot" [High,In progress] https://launchpad.net/bugs/72808823:40
psusicjwatson, it used to be recommended to create a raid1 partition for /boot and install grub to those disks, then raid5 for / ( assuming you want a raid5 )... with grub2 you can now just make a single raid5 for /, and install grub to all of the disks, so should that now be the recommended method?23:46
cjwatsonpsusi: probably, if it's working well23:49
cjwatsonseparate /boot isn't harmful of course, it's just extra work23:49
psusiright, and so if it isn't necessary, best to avoid it...23:51
cjwatsonit is more complexity in the boot loader, of course, and some people like to avoid *that*23:51
cjwatsondepends on your point of view really23:52

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