[10:14] <ara> superm1, hi!
[10:14] <ara> superm1, did bryce fix solved the problem you had with the installation with intel drivers?
[12:48] <CIA-4> pkgsel: cjwatson * r169 ubuntu/debian/ (po/lo.po po/si.po changelog po/se.po): merge from Debian 0.33
[12:50] <CIA-4> pkgsel: cjwatson * r170 ubuntu/debian/changelog: releasing version 0.33ubuntu1
[14:40] <CIA-4> console-setup: cjwatson * r379 ubuntu/debian/ (changelog keyboard-configuration.config):
[14:40] <CIA-4> console-setup: console-setup-udeb (<< 1.53) didn't set the seen flag in the installed
[14:40] <CIA-4> console-setup: system. Cope with this and avoid asking the layout and variant
[14:40] <CIA-4> console-setup: questions again if the default debconf priority is at least high
[14:40] <CIA-4> console-setup: (LP: #705883).
[15:14]  * cjwatson tries to figure out how to detect this console-setup upgrade breakage neatly
[15:15] <cjwatson> it's characterised at least in part by some dialogs being wrongly re-presented and wrongly having the first option as the default, so you tend to end up with keyboard-configuration/modelcode=a4techKB21 and keyboard-configuration/layoutcode=us,af
[15:15] <cjwatson> but I can't really guarantee that some people didn't hit down a bit before getting confused
[15:15] <cjwatson> perhaps I should just do something like:
[15:15] <cjwatson>   if previous-version was one of the broken ones:
[15:16] <cjwatson>     if XKB* in /etc/default/keyboard don't match commented-out XKB* in /etc/default/console-setup:
[15:16] <cjwatson>       reset to values from /etc/default/console-setup and ask questions again
[15:18] <cjwatson> so there'll be some final debconf noise while clearing things up, but it will be confined to people upgrading through natty
[15:18] <cjwatson> or I could s/ and ask questions again//, but that means anyone who's since modified /etc/default/keyboard gets their changes summarily overwritten
[15:18] <cjwatson> maybe if I accompany it with a mail to ubuntu-devel-announce ...
[15:41] <ev> sounds sensible
[16:41] <ev> cjwatson: what are your thoughts on fixing the usb-creator from natty creating usb disks for 10.10 and 10.04 by including maverick's syslinux in usb-creator or building a syslinux-legacy package?
[16:41] <cjwatson> have you tried isohybrid?
[16:42] <cjwatson> if that works it would be so much easier
[16:43] <ev> wouldn't that prevent us from writing a casper-rw file or partition?
[16:45] <cjwatson> I wouldn't rule that out
[16:45] <cjwatson> it might take a bit of fiddling but it should be doable
[16:45] <cjwatson> at least a partition
[16:46] <cjwatson> you *could* import the whole syslinux source and build it again in usb-creator.  it's certainly possible.  it's really ugly though :)
[16:46] <cjwatson> I'm not crazy about syslinux-legacy, it feels like it would tempt people to use it for other things
[16:49] <cjwatson> if isohybrid is unworkable, I'd prefer something that's explicitly private to usb-creator
[16:49] <ev> I'll give it a shot (isohybrid).  I had assumed that this isohybrid stuff worked without a partition table, but I haven't spent any time with it, so further investigation is in order.
[16:49] <ev> noted
[16:49] <ev> thanks bunches for the advice, as always
[16:50] <cjwatson> but if isohybrid is unworkable then I think we need to figure that out, because whenever we finally move to grub it will bear a lot of resemblance to isohybrid
[16:50] <cjwatson> isohybrid does use a partition table (possibly optionally, I'm not sure)0
[16:51] <cjwatson> doc/isolinux.txt says:
[16:51] <cjwatson> The ISO 9660 filesystem is encapsulated in a partition (which starts
[16:51] <cjwatson> at offset zero, which may confuse some systems.)  This makes it
[16:51] <cjwatson> possible for the operating system, once booted, to use the remainder
[16:52] <cjwatson> one thing to establish would be whether there are any other changes you need to make to the filesystem
[16:52] <cjwatson> if there are then you'd need to pack them back into an iso before running isohybrid, which might be slow/fiddly
[16:52] <ev> ah yes, there would be
[16:53] <cjwatson> or you could use xorriso to create a hybrid image in one shot
[16:53] <ev> (the kernel command line parameters in the configuration, assuming that's done on the filesystem)
[16:53] <cjwatson> yeah
[16:53] <cjwatson> xorriso's in main as of maverick, since we needed it for grub2
[16:54] <cjwatson> but the general approach of keeping it as an iso9660 filesystem as well would dodge the whole bullet of having to install a different boot loader, which seems worth trying
[16:54] <ev> indeed
[16:55] <cjwatson> you can look at grub-mkrescue if you want examples of xorriso usage
[16:55] <ev> will do, thanks
[16:55] <cjwatson> 16:51 [Freenode] !kornbluth.freenode.net *** Message to #ubuntu-installer throttled due to flooding
[16:55] <cjwatson> boo @freenode
[16:56] <ev> wow
[16:56] <cjwatson> I think it objected to me pasting four lines from isolinux.txt
[16:56] <ev> that was hardly anything approaching a flood
[16:56] <ev> ah
[16:56] <ev> still, quite agressive
[16:56] <cjwatson> yeah
[17:00] <CIA-4> ubiquity: superm1 * r4491 ubiquity/debian/changelog: add bug number
[17:09] <cjwatson> http://paste.ubuntu.com/559096/ vomit
[17:09]  * cjwatson builds to see what happens
[18:42] <bladernr> Has the policy changed for Natty Server where X is going to be installed??
[18:42] <bladernr> http://pastebin.ubuntu.com/559136/
[18:43] <bladernr> mlegris just pointed out that gtkperf is trying to run on servers, and turns out that x11-utils is being installed for some reason (along with other X packages, see pastebin)
[18:44] <cjwatson> no policy change although console-setup has always pulled in a certain amount via xkb-data
[18:45] <cjwatson> can I have an installer syslog?
[18:46] <cjwatson> hm, should topic that
[18:46] <bladernr> cjwatson:  let me see if I can grab it for you
[18:47] <bladernr> cjwatson:  just installer/syslog or would you prefer a tar of installer/
[18:47] <cjwatson> just installer/syslog
[18:48] <cjwatson> this looks like what happens if you install the uec-live task
[18:48] <cjwatson> gtkperf certainly isn't installed by default, it's in universe
[18:50] <cjwatson> (I mean the ubuntu-uec-live task, btw)
[18:51] <bladernr> right...  I'm starting to learn about using tasksel to find these things out, so sorry for bugging you about some of this stuff
[18:51] <cjwatson> was this an install you did, or somebody else?
[18:53] <bladernr> it's one of the preseeds on the enablement servers in Boston (for hardware cert)
[18:54] <bladernr> AFAIK, our preseed uses defaults and doesn't install any options for server
[18:54] <bladernr> I'm going to do a local install to make sure it's not something our preseed is pulling in though
[18:54] <cjwatson> then ideally I'd get a log with the DEBCONF_DEBUG=developer boot parameter, to try to determine why ubuntu-uec-live is being pulled in
[18:54] <bladernr> and the log is in your e-mail
[18:54] <cjwatson> thanks
[21:35] <cody-somerville> Whats the value for no password?
[21:35] <cody-somerville> (for use with preseeding)
[21:36] <cody-somerville> chpasswd no longer accepts no password for using unencrypted version no longer works
[23:02] <bladernr> cjwatson:  you can safely ignore my x11-utils question from before.  Turns out (I didn't find this out until well after I'd become invested in this) that the person who brought it to my attention initially had installed desktop on a server, which explains everything.


[00:06] <wxl> oh jeez now my container won't upgrade
 that seems odd.
[00:07] <RikMills> from what to what?
[00:12] <RikMills> when I did one the other day I just sed the sources.list for eoan -> focal
 same here
 mmmm nvidia+uefi, not trivial
 @wxl [<wxl> @tsimonq2: do you really plan on independently maintaining a release sched …], Agreed, axe
 @wxl [<wxl> @tsimonq2 looks like we also need to set the default branch in launchpad. …], Waaat
 wxl: exec dch -r doesn't work either
 sorry, dch -r ""
 exec germinate-update-metapackage --vcs … exec dch -r "" … still UNRELEASED
 maybe need to escape "" ??
 dch -r \"\" worked
 w/o need of exec
[08:55] -lugito:#lubuntu-devel- [T127: Screengrab not set to launch on PrtSc in 19.10] EinarMostad (Einar Mostad) commented on the task: https://phab.lubuntu.me/T127#2632
[08:56] -lugito:#lubuntu-devel- [T125: Lubuntu 19.10 QtPass problem] EinarMostad (Einar Mostad) commented on the task: https://phab.lubuntu.me/T125#2633
[09:02] -lugito:#lubuntu-devel- [T126: Where to report bugs is unclear] EinarMostad (Einar Mostad) commented on the task: https://phab.lubuntu.me/T126#2634
[09:23] -lugito:#lubuntu-devel- [T128: Alt-Tab and Alt-Shift-Tab feature request (openbox conf)] EinarMostad (Einar Mostad) commented on the task: https://phab.lubuntu.me/T128#2635
 guiverc2 @guiverc regarding your question in offtopic, we as lubuntu package a lot (if not all) lxqt
 examples are pcmanfmqt globalkeys....
[13:45] <guiverc2> As in we grab from github directly? or I was assuming we'd grab from debian  (automatically? or initiated/selected?)
 from git https://phab.lubuntu.me/source/lxqt-globalkeys/browse/ubuntu%252Ffocal/debian/watch
 https://phab.lubuntu.me/source/pcmanfm-qt/browse/ubuntu%252Ffocal/debian/watch
[13:46] <guiverc2> Thanks @HmollerCl
 np
 there is new redshift-qt upstream release https://github.com/Chemrat/redshift-qt/releases/tag/v0.5. I will update my ppa soon for eoan, still waiting for @tsimonq2 to create the repo.
[16:04] -lugito:#lubuntu-devel- [T78: Port Redshift From Gtk To Qt] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T78#2636
 @HMollerCl [there is new redshift-qt upstream release https://github.com/Chemrat/redshift-qt …], Repo is created but I can't activate it from mobile
 And no guarantees that permissions are correct
[18:26] <wxl> @HMollerCl can you update your diff to include the escaping?
[18:26] <wxl> @tsimonq2: as ready as i might ever be
[18:27] <kc2bez> wxl: ECHAN but ditto
[18:28] <wxl> @kc2bez: it's the *right* place
[18:28] <kc2bez> :D
[18:29] <kc2bez> I don't disagree.
[18:30]  * wxl upgrades his container the @RikMills way
[18:39] -lugito:#lubuntu-devel- [T127: Screengrab not set to launch on PrtSc in 19.10] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T127#2637
[18:40] -lugito:#lubuntu-devel- [T126: Where to report bugs is unclear] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T126#2639
[18:41] -lugito:#lubuntu-devel- [T128: Alt-Tab and Alt-Shift-Tab feature request (openbox conf)] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T128#2640
[18:45] <wxl> @HMollerCl https://phab.lubuntu.me/source/redshift-qt/
 Nice!!
[19:23] <wxl> @HMollerCl so go push to it!
 in which compar are we now? 14?
 *compat
[20:24] -lugito:#lubuntu-devel- [rMANUALbdadfd4e5aa1: Add Description for Discover icon] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALbdadfd4e5aa1
[20:25] <wxl> !info debhelper eoan
[20:25] <wxl> oops
[20:25] <wxl> !info debhelper focal
[20:25] <wxl> looks like 12 it is
 yep, debian is only at 12 currently for its compats too last I checked :)
[20:28] <wxl> !info debhelper experimental
[20:28] <wxl> !info debhelper unstable
[20:29] -lugito:#lubuntu-devel- [rMANUAL3b0b7ad529ff: Describe icon for Muon Package manager] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL3b0b7ad529ff
 12 it is then.
[20:38] -lugito:#lubuntu-devel- [rMANUAL05ea83e546e7: Describe Software Sources icon] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL05ea83e546e7
[20:46] <wxl> apparently the maintainer guide needs updating https://www.debian.org/doc/manuals/maint-guide/dother.en.html#compat
[20:49] -lugito:#lubuntu-devel- [rMANUAL89958817c620: Reword chapter 4 intro] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL89958817c620
[22:08] -lugito:#lubuntu-devel- [rMANUAL53d360211f46: Use consistant capitilization for shortcut] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL53d360211f46
[22:23] -lugito:#lubuntu-devel- [rMANUAL5a5b91e698dd: Add Select icon button for Qlipper custom icon] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5a5b91e698dd
[22:26] -lugito:#lubuntu-devel- [rMANUAL87150a0caa7e: Add Platform specific extensions checkbox] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL87150a0caa7e
[22:29] -lugito:#lubuntu-devel- [rMANUALb1266d517549: Add First menu selection for synchronization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb1266d517549
[22:39] -lugito:#lubuntu-devel- [rMANUALa6860a802d28: Add synchronize menu selection item stuff] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALa6860a802d28
 wxl @tsimonq2 @kc2bez someone there? Need help on how to add the files to redshift-qt new repo
 What's up?
 if I create a changelog with las version uscan doesn't bring me the tar
 so, how is the way to upload the first repo?
 What errors are being given?
 no errors
 uscan info:    => Package is up to date for from …       https://github.com/Chemrat/redshift-qt/archive/v0.5.tar.gz … uscan info: Scan finished
 Hmm
 What's in debian/watch?
 because it reads from the changelog...
 look at the changelog and see that it is the same number as last upstream
 version=4 … opts="filenamemangle=s/(?:.*\/)?v?(\d[\d.]*)\.tar\.gz/$1.tar.gz/" \ … https://github.com/Chemrat/redshift-qt/tags (?:.*/)?v?(\d[\d.]*)\.tar\.gz
 Don't worry about that for now if it's just your initial commit
[23:42] <wxl> ^ that
[23:43] <wxl> just set your remote and push
 ok, and how I test if it's ok?
 Check the web GUI once you think you've pushed it correctly
[23:43] <wxl> yep or pull it
 ok, thanks!
 Thank you :)


[10:04] <lawnchair> im trying to install ubuntu (12 or 13) and the installer crashes the same way for both versions: "console-setup-linux breaks console-setup" - has anyone ever seen this before?
[10:06] <cjwatson> 12 and 13 aren't versions of Ubuntu - your choices are 12.04, 12.10, 13.04, 13.10
[10:06] <cjwatson> Exactly which image (URL, preferably) are you installing?  Could I see the full log of the failure?
[10:11] <lawnchair> ubuntu-12.04.2-desktop-amd64.iso ubuntu-13.04-desktop-amd64.iso
[10:11] <lawnchair> i find it odd they both crash the same way
[10:11] <lawnchair> i dont have the full log of the failure but i submitted a crash report
[10:11] <lawnchair> i thought it might be a common failure, i guess not
[10:13] <lawnchair> ill go through the installer again and let it crash... then ill grab the log
[10:16] <cjwatson> console-setup-linux is a Debian thing; we've never merged it into Ubuntu
[10:16] <cjwatson> (It's in the queue, just a fair amount of effort and not high-priority)
[10:16] <cjwatson> So it's perplexing that you would be seeing it even mentioned at all in an Ubuntu installation
[10:16] <cjwatson> Are you doing anything at all unusual with the installer?
[10:17] <cjwatson> For example, writing the image to a USB stick using some special tool?
[10:18] <lawnchair> yep
[10:18] <lawnchair> i'm writing it to a usb stick w/ unetbootin
[10:19] <lawnchair> so yeah, that's def. a common factor
[10:19] <lawnchair> makes sense for that to be the issue
[10:20] <cjwatson> Right.  I blame unetbootin.  You can just write Ubuntu images to USB sticks with dd
[10:20] <lawnchair> ok cool. i'll do that.
[10:20] <cjwatson> It doesn't need a special tool unless you want extra persistent storage on the USB stick, or a pretty UI
[10:20] <lawnchair> nope, i don't need anything crazy
[10:20] <lawnchair> cool, thanks for the direction
[10:21] <lawnchair> much appreciated
[10:21] <cjwatson> The amount of odd stuff unetbootin apparently does is depressing, though :(
[10:21] <cjwatson> I wish we had more time to fix up usb-creator so that people wouldn't feel they needed it ...
[23:48] <jkitchen> question: I need to create a system user during preseed prior to installing a package (to prevent the package from just willy-nilly adding its user with whatever uid it decides). is this possible?
[23:49] <jkitchen> seems the d-i passwd/user-uid thing might be the way to go, but that's only one user, what if I need to make, say more than one?
[23:50] <jkitchen> the puppet package installs a user. I need that user to *always* be the same uid, period. my preseed script installs puppet. therefore I need to have that uid exist during my preseed
[23:52] <cjwatson> I would be inclined to write a preseed/early_command script that writes out an executable script in /usr/lib/post-base-installer.d/; that script can then call "in-target adduser --system --uid FIXED USERNAME" or whatever it would be
[23:53] <cjwatson> I am not aware of any specific facility for this (and passwd/user-uid isn't it, even for one system user), but the general facilities should work
[23:54] <jkitchen> I actually just came up with a really horrible way to do it which should just work: create a package which does nothing but create the required user.
[23:54] <jkitchen> and install that prior to installing puppet
[23:55] <cjwatson> You can do that.  I would prefer the post-base-installer approach myself.
[23:55] <jkitchen> yea
[23:55] <jkitchen> can I have more than one preseed/early_command?
[23:56] <cjwatson> Or, indeed, if you're installing puppet in preseed/late_command rather than pkgsel/include or whatever then you can just create the user first.
[23:56] <jkitchen> also, since I can't seem to find the thing, where are the docs specifically for ubuntu installer? (the preseed file itself specifically would be great)
[23:56] <jkitchen> I've been referring to d-i.alioth.debian.org, but I imagine there are some differences
[23:56] <jkitchen> and "ubuntu installer" on google gives me all sorts of completely irrelevant pages heh
[23:56] <cjwatson> No.  Think of preseeding as setting keys in a database, not as a script.  But of course preseed/early_command can contain more than one command.
[23:57] <cjwatson> https://help.ubuntu.com/12.04/installation-guide/i386/appendix-preseed.html
[23:57] <jkitchen> cjwatson: <3
[23:57] <jkitchen> I've been looking for that page for days.
[23:58] <jkitchen> and yea, I figured not with regard to multiple early_commands, but had to check (in case there was like a preseed/early_command/0, 1, 2, etc)
[23:58] <cjwatson> Nope.  But you can wget a script, chmod +x it, and execute it, if that's easier to manage
[23:59] <jkitchen> not a bad idea. we shall see :)
[23:59] <jkitchen> does that page you linked me to cover the available hooks (like the post-base-installer.d dir you mentioned) as well?