 well, rebuilding for a library transition is usually reason enough, and the most common
 yup
 And all sorts of fun if it FTBFS against  the new  ABI
 hah yup
 As a MOTU I seem to spend much time hunting for fixed for those :/
 welcome to the Real World :)
 as a core dev i touch a bit of everything when I have to, even when I don't touch things I watch what others touch thanks to DMB XD
 though i'm waiting for Canonical Server Team to ACK the yanking of something from the NGINX source that'll make things a lot easier for the Security team xD
 ('cause freeze having the Canonical Team on my side is a good xD)
 Oh, I also look at the stuff in main often. I just have to poke some core devs I often talk to to get an action (re @teward001: as a core dev i touch a bit of everything when I have to, even when I don't touch things I watch what others touch thanks to DMB XD)
 well thankfully you have one here you can prod :)
 lubuntu or not.
 Yeah, I was just going to add that I think I can include you in the list now :) (re @teward001: well thankfully you have one here you can prod :))
 :P
 Studio bugs me a ton whenever they need new things through, MOTU or not.  Especially if it needs me to poke other things xD
 but they have a packageset and I think Erich has MOTU now so :)
 but i digress.
 *goes to make food*
 Saying that, I should probably look at working on getting core dev in the not too distant future
[00:17] -lugito:#lubuntu-devel- [rMANUAL49d09bb2a661: Update lxqt-panel version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL49d09bb2a661
[00:18] -lugito:#lubuntu-devel- [rMANUALe505b4b51602: Update brightness version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe505b4b51602
[00:20] -lugito:#lubuntu-devel- [rMANUALbdc0c488f7c0: Update Appearance version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALbdc0c488f7c0
[00:25] -lugito:#lubuntu-devel- [rMANUAL26a9ea8cdaa9: Update LXQt Configuration center version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL26a9ea8cdaa9
[00:28] -lugito:#lubuntu-devel- [rMANUALcbe36beb4dfa: Update Date and time version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALcbe36beb4dfa
[00:30] -lugito:#lubuntu-devel- [rMANUALb300103a7e81: Update desktop version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb300103a7e81
[00:32] -lugito:#lubuntu-devel- [rMANUALb100b7d80bc8: Uppdate desktop notifications version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb100b7d80bc8
[00:34] -lugito:#lubuntu-devel- [rMANUAL443d5f384608: Update desktop notifications version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL443d5f384608
[00:35] -lugito:#lubuntu-devel- [rMANUALe6f72876858f: Update file associations version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe6f72876858f
[00:38] -lugito:#lubuntu-devel- [rMANUAL0f5234898f2b: Update keyboard and mouse version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0f5234898f2b
[00:42] -lugito:#lubuntu-devel- [rMANUAL2d803b1a9b2a: Update openbox settings] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2d803b1a9b2a
[00:46] -lugito:#lubuntu-devel- [rMANUAL939a5309789c: Update power management version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL939a5309789c
[00:48] -lugito:#lubuntu-devel- [rMANUALc694ac6d1812: Update session settings version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALc694ac6d1812
[00:49] -lugito:#lubuntu-devel- [rMANUAL9ae06d85def7: Update shortcut keys version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL9ae06d85def7
[00:50] -lugito:#lubuntu-devel- [rMANUAL0d73d9641aca: Update users and groups version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0d73d9641aca
 Will do - already done some tests but will run thru all the file formats as well (re @lubuntu_bot: (irc) <wxl> testers please check to make sure that lxqt-archiver integration is functioning properly in pcmanfm-qt and also check to ensure that lxqt-archiver is the default application opening any archive filetype)
[01:05] -lugito:#lubuntu-devel- [rMANUAL8627568a4b4d: Update pcmanfm-qt version numbers] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8627568a4b4d
[01:07] -lugito:#lubuntu-devel- [rMANUAL2da22c7276c4: Fix wording on Qt style menu] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2da22c7276c4
[01:09] -lugito:#lubuntu-devel- [rMANUALba62aed4ac4e: Explain what Qt palatte section does] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALba62aed4ac4e
[01:13] -lugito:#lubuntu-devel- [rMANUAL8a9b80781889: Add changing window color] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8a9b80781889
[01:22] -lugito:#lubuntu-devel- [rMANUALfc04c87d0950: Add View button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfc04c87d0950
[01:29] -lugito:#lubuntu-devel- [rMANUAL34a291c8b85f: Add Selection Text] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL34a291c8b85f
[01:44] <wxl> kc2bez[m]: yeah i saw that one. thinking of that report that we had where they lost natural scrolling?
[03:11] <guiverc> anyone got a preference when I setup testing.checklist for hirsute.. I didn't plan doing it before optional.testing (thursday just passed), but a month before release, six weeks?  (currently <8)
 Ready whenever.. (re @lubuntu_bot: (irc) <guiverc> anyone got a preference when I setup testing.checklist for hirsute.. I didn't plan doing it before optional.testing (thursday just passed), but a month before release, six weeks?  (currently <8))
[05:04] <guiverc> ack & thanks @Leokolb
[05:06] <guiverc> wxl; a new hirsute qa-test install & `dpkg -l |grep lxqt` all have 0.16.0
[06:31] -lugito:#lubuntu-devel- [Lubuntu CI] merger_sddm FAILURE: https://ci.lubuntu.me/job/merger_sddm/273/
[06:52] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/551/
[07:03] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/820/
[07:03] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/119/
[07:03] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/368/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/552/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/552/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/329/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/115/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/329/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/115/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/821/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/120/
[07:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/369/
[07:23] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/821/
[07:33] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/160/
[07:33] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/160/
[07:33] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/387/
[07:33] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/387/
[07:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/603/
[07:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/815/
[07:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/815/
[07:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/256/
[07:43] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/604/
[07:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/386/
[07:44] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/257/
[07:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/816/
[07:54] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/123/
[07:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/386/
[07:54] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/123/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/612/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/612/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/552/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/212/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/612/
[08:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/611/
[08:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/611/
[08:19] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/553/
[08:19] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/213/
[08:20] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/391/
[08:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/613/
[08:34] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/613/
[08:34] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/121/
[08:34] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/611/
[08:34] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/121/
[08:34] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/392/
[08:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/614/
[09:05] <kc2bez[m]> <wxl "kc2bez: yeah i saw that one. thi"> Yes, same here.
[09:06] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/789/
[09:10] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-config/379/
[09:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/789/
[09:25] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/121/
[09:26] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/789/
[10:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/644/
[10:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/644/
[10:28] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-session/615/
[10:28] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-session/615/
[10:31] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/644/
[10:42] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_nm-tray/577/
[10:42] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_nm-tray/577/
[10:42] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_nm-tray/334/
[10:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/909/
[10:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_nm-tray/334/
[10:57] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qps/117/
[10:57] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/652/
[10:57] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/652/
[11:07] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/125/
[11:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_obconf-qt/610/
[11:08] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/375/
[11:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qterminal/910/
[11:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/652/
[11:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/405/
[11:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/405/
[11:09] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just failed after being unstable: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/126/
[11:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_obconf-qt/610/
[11:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/640/
[11:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/120/
[11:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/369/
[11:27] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/641/
[11:27] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/375/
[11:28] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/387/
[11:28] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/641/
[11:28] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/411/
[11:28] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/411/
[11:28] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps just failed after being unstable: https://ci.lubuntu.me/job/hirsute_stable_qps/118/
[11:29] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/821/
[11:29] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qterminal/910/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/612/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/553/
[11:42] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/213/
[11:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/612/
[11:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/612/
[11:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/160/
[11:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/388/
[11:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/613/
[11:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/604/
[11:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/161/
[11:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/644/
[11:55] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/645/
[11:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-config just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-config/380/
[11:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/790/
[11:59] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/122/
[12:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal FAILURE: https://ci.lubuntu.me/job/focal_stable_qterminal/910/
[12:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/653/
[12:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-session just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-session/616/
[12:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/405/
[12:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/653/
[12:09] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/126/
[12:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_obconf-qt/611/
[12:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/376/
[12:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_nm-tray just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_nm-tray/335/
[12:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_nm-tray/578/
[12:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_nm-tray/578/
[12:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/613/
[12:21] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/553/
[12:21] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/213/
[12:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/613/
[12:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/613/
[12:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/389/
[12:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/120/
[12:23] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/369/
[12:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/389/
[12:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/911/
[12:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just became unstable after failing: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/127/
[12:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/821/
[12:34] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/405/
[12:34] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/653/
[12:34] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/411/
[12:34] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just became unstable after failing: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/127/
[12:36] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/604/
[12:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/614/
[12:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/645/
[12:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/646/
[12:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/911/
[12:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/654/
[12:39] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps just became unstable after failing: https://ci.lubuntu.me/job/hirsute_stable_qps/119/
[12:51] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/377/
[18:26] <wxl> anyone see fritz' email about wifi? has anyone tested the new nm-tray at all?
[18:27] <wxl> i mean it shouldn't be very different
[18:27] <wxl> same upstream version
 Yes - I saw it and am lost—I test WiFi everyday - no problems that I am aware of - I am busy right now but can look into this a bit further later .. havent tested todays ISO yet .. (re @lubuntu_bot: (irc) <wxl> anyone see fritz' email about wifi? has anyone tested the new nm-tray at all?)
 @wxl -Updating 794 packages ?! not surprised that something might have gone wrong
[18:39] <wxl> heheheheh
[18:40] <kc2bez[m]> There is always the "right click, edit connections" option to see if they show there.
[18:40] <wxl> the fact you're testing wifi every day is pretty telling
 just booted up todays ISO and connected 2.r4 G and also tested 5Ghz no probs,,sorry am busy but would need maybe info as to what hardware he is using (re @lubuntu_bot: (irc) <wxl> heheheheh)
[18:41] <kc2bez[m]> He has a 2009 vintage Mac book pro
[18:41] <wxl> i'm not going to get too deep into it
[18:42] <wxl> fritz can be a bit of a support black hole
 most likely broadcom —sometimes a problem (re @lubuntu_bot: (irc) <kc2bez[m]> He has a 2009 vintage Mac book pro)
 I mean problem with the driver
[18:43] <kc2bez[m]> The discourse thing is weird too but that is yet another rabbit hole.
[18:44] <wxl> i have something weird with that and firefox mobile beta but it wasn't always that way so it's probably a cache/cookie/profile issue maybe that i have 3 million tabs open
 2,999,999 tabs is the limit in Firefox - at least my version (re @lubuntu_bot: (irc) <wxl> i have something weird with that and firefox mobile beta but it wasn't always that way so it's probably a cache/cookie/profile issue maybe that i have 3 million tabs open)
 @wxl @teward001 @kc2bez Just got bug 1917292 on todays iso efi testing!!
[19:37] <kc2bez[m]> bug 1917292
[19:37] <kc2bez[m]> uff
[19:37] <kc2bez[m]> ok
[19:38] <wxl> aww eez
[19:38] <wxl> do you think this is an infra issue again @teward001?
[19:38] <kc2bez[m]> Might need that no-change rebuild after all
[19:38] <wxl> no dan this is the grub one
 i thought that crap was fixed. RE: 1917292 (re @Leokolb: @wxl @teward001 @kc2bez Just got bug 1917292 on todays iso efi testing!!)
[19:39] <wxl> it was
[19:39] <wxl> !
 you all are imbecils
 because it's still "Invalid" and fixed
 Nice.. (re @teward001: you all are imbecils)
 are you saying it's *not*?  and if so where's the proof?
[19:39] <kc2bez[m]> oh yeah
[19:39] <kc2bez[m]> geeze
 sorry i'm grumpy, no sleep due to anxiety for getting the vaccine
 kc2bez[m]: yeah we *fixed* that.  or rather cjwatson and vorlon did
 it was a sync issue on the iso builder
 they unfubar'd it
 once we confirmed it worked I marked it as "Invalid" because it's not a Cala or any other package bug
[19:40] <kc2bez[m]> grub went through another migration
 it's an ISO Builder bug that they fixed.
[19:40] <wxl> @leokolb you at least had oen day where you weren't having that problem right?
 you got the vaccine? (re @teward001: sorry i'm grumpy, no sleep due to anxiety for getting the vaccine)
 is it broke again?
[19:40] <kc2bez[m]> might be stuck again
 first dose, in arm (re @RikMills: you got the vaccine?)
 see -offtopic
 as of about 30 minutes ago
[19:40] <wxl> we got a new grub2-signed 3 hours ago
[19:40] <wxl> so i'm thinking it may be that
 it probably is but that'll be on the next ISO spin (re @lubuntu_bot: (irc) <wxl> so i'm thinking it may be that)
 let's wait 24h before we reopen an old bug
 congrats (re @teward001: first dose, in arm)
[19:41] <wxl> or i could just rebuild the iso
 wxl: i mean you could
 or wait for autobuild :P
 i don't know the update schedule on the iso builders sync though wxl
 hence why i said wait 24
 Thats right (maybe 2?) we did many tests yesterday (also the partitioning etc) at least 15 with no errors (re @lubuntu_bot: (irc) <wxl> @leokolb you at least had oen day where you weren't having that problem right?)
[19:42] <wxl> we should have just got our new iso
[19:43] <wxl> um
[19:43] <wxl> wth is the time zone on the time stamps on cdimage. i'd think utc but isn't 17:51 on the 5th in the future?
 today's the fifth ya numpty
 it's UTC
[19:43] <wxl> yes
[19:43] <kc2bez[m]> No that was a couple of hours ago
[19:44] <wxl> i thought it's 7:42
 17:51 UTC = 12:51 GMT-5 that was a few hours ago
 it it 19:44 here
[19:44] <wxl> oh gosh darn it
 wxl: 17 - 12 is 5
 your math sucks
 That is the ISO I tested
[19:44] <kc2bez[m]> `date -u`
[19:44] <wxl> i did date -u but it gave me 12 hour time yuck
[19:44] <wxl> got to fix that alias
 heheh.  do you need a hug wxl?  :P
 20:45 (re @RikMills: it is 19:44 here)
 UTC and GNT are the same time (my time zone)
 14:45 here :)
 GMT
[19:46] <wxl> there that's better
[19:46] <wxl> date -uR
 Well, I am in the UK. So currently on GMT and UTC, and it is 19:46
 :P
[19:46] <wxl> YOU"RE A LIAR
[19:46] <wxl> FAKE NEWS
 Same here in Iceland (re @RikMills: Well, I am in the UK. So currently on GMT and UTC, and it is 19:46)
[19:46] <wxl> so i'm gonna rebuild the iso then
[19:47] <kc2bez[m]> Cool, fingers crossed.
[19:47] <wxl> building…
 ready to test when it completes
[19:48] <wxl> i don't know what sense to make out of this change though
[19:48] <wxl>   * Compile grub-efi-amd64 installable i386 platform on hirsute, to make
[19:48] <wxl>     it available in bionic and earlier as part of onegrub builds.
 Testing latest build ..
[20:29] <wxl> looks like the right grub on the manifest
 Failed again - same error.. (re @lubuntu_bot: (irc) <wxl> looks like the right grub on the manifest)
 got the pastebin of the logs?
 logs would be nice :P
 np - hang on a min (re @teward001: got the pastebin of the logs?)
 session log — does not look complete at all - https://paste.ubuntu.com/p/SvvyvHN2qQ/ (re @teward001: got the pastebin of the logs?)
[20:41] <wxl> i think he meant the Calamares log XD
[20:43] <wxl> @leokolb ^
 hang on (re @lubuntu_bot: (irc) <wxl> i think he meant the Calamares log XD)
[20:51] -lugito:#lubuntu-devel- [rMANUALeffb234bc1a0: Add link color changing] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALeffb234bc1a0
 sorry - earthquakes here ...https://paste.ubuntu.com/p/xBMpQRWtNz/
 sorry for the delay .. http://paste.ubuntu.com/p/xBMpQRWtNz/ (re @teward001: got the pastebin of the logs?)
[21:01] -lugito:#lubuntu-devel- [rMANUAL0a794bce29b6: Add view text button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0a794bce29b6
 that's a grub mismatch problem all right
[21:03] -lugito:#lubuntu-devel- [rMANUAL570c5e7bbde0: Add Selected Text button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL570c5e7bbde0
[21:08] -lugito:#lubuntu-devel- [rMANUAL2237639e6cfc: Add Default palette button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2237639e6cfc
[21:14] <wxl> keep an eye out for a new iso. the release team is clearing some things in the queue and once that is done, they'll kick off a new build
[21:15] <wxl> i advise checking the .list and see what version of the grub packages are included. if it's -1ubuntu44 we're good.
[21:18] -lugito:#lubuntu-devel- [rMANUALf76b71ebf12a: Change multiple monitors for sliders] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALf76b71ebf12a
[21:24] -lugito:#lubuntu-devel- [rMANUALd7489032c667: Add battery life savings of less backlight] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALd7489032c667
[21:32] -lugito:#lubuntu-devel- [rMANUAL0797fb460595: Add Default Applications tabB] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0797fb460595
[21:35] -lugito:#lubuntu-devel- [rMANUAL70be3caa12b1: Add Change button for each application] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL70be3caa12b1
[21:48] -lugito:#lubuntu-devel- [rMANUAL77a2937c6533: Update monitor settings version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL77a2937c6533
[21:52] -lugito:#lubuntu-devel- [rMANUALc3be4718a576: Fix date and time version number] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALc3be4718a576
[22:01] <wxl> should be coming soon
[22:01] <wxl> release team says it's looking good
[22:18] -lugito:#lubuntu-devel- [rMANUAL9ee20403795b: Add Stub of lxqt-archiver] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL9ee20403795b
[22:34] -lugito:#lubuntu-devel- [rMANUAL0a6b4be8fb31: Add basic open extract and file navigation to lxqt-archiver] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0a6b4be8fb31
[22:35] -lugito:#lubuntu-devel- [rMANUAL7203eab71987: Fix version] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL7203eab71987
 Testing (re @lubuntu_bot: (irc) <wxl> release team says it's looking good)
[22:42] -lugito:#lubuntu-devel- [rMANUAL8352ad7d747d: Add view selected items] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8352ad7d747d
 Boot successful! Now some shuteye.. (re @lubuntu_bot: (irc) <wxl> release team says it's looking good)
[22:46] <wxl> thanks @leokolb have a good night and don't fall out of bed ;)
 no comment! (re @lubuntu_bot: (irc) <wxl> thanks @leokolb have a good night and don't fall out of bed ;))
[22:52] -lugito:#lubuntu-devel- [rMANUAL90471500d1bf: Add Extract and use Delete a file] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL90471500d1bf
[23:09] <lynorian> is there a bug for failing to add files to lxqt-archiver to newly created archives?
[23:13] <lynorian> just checked and nope
[23:26] <wxl> i'm not sure i know what you mean @lynorian
[23:27] <lynorian> wxl filed bug 1917960
[23:54] <wxl> @lynorian: thanks i'll take a look at it
[23:54] <wxl> ^ but if anyone else wants to confirm/triage, that would be great


[10:43] <cjwatson> isc-dhcp binaries could use NEWing
[10:49] <cjwatson> Riddell: could you commit your sync-blacklist changes from yesterday with some appropriate message?
[10:52] <Riddell> yes, one sec
[10:56] <Riddell> done
[10:57] <cjwatson> thanks
[11:08] <ogra> hmpf
[11:09]  * ogra wonders why base-files and base-passwd appear to be uninstallable on armel
[18:07] <cjwatson> could somebody look at isc-dhcp in NEW?  it needs to go to main (replacing dhcp3)


[05:11] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 Preparing packages
[05:12] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[05:27] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 Preparing packages
[05:48] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4030 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[06:10] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4030 Preparing packages
[11:16] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4015 Needs rebuild due to higher version at destination
[16:31] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4030 Uploading build
[16:51] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4030 Successfully built
[22:10] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 Uploading build
[22:30] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 Pending binary packages
[22:50] -queuebot:#ubuntu-ci-eng- wgrant, https://bileto.ubuntu.com/#/ticket/4029 Successfully built


[05:55] <tjaalton> bryce: what mlankhorst said :) guess it's xserver and at least some drivers today
[07:18] <tjaalton> llvm built, finally
[07:18] <tjaalton> still no sign of doko or sylvestre
[07:18] <tjaalton> I'll just email them
[08:52] <tjaalton> updating libdrm for newer mesa snapshot
[10:07] <mlankhorst> I guess I better test mesa 9.0.2 now then :P
[10:16] <mlankhorst> time to run the piglit tests I suppose
[10:17] <tjaalton> meh, how hard can it be to get reprepro signing work.. i've done this before, years ago
[10:18] <RAOF> What are you trying to do?
[10:18] <tjaalton> to test the builds locally with sbuild
[10:18] <tjaalton> pulling from a local repo
[10:18] <tjaalton> include/export works, now sbuild-update claims the pubkey isn't known
[10:18] <RAOF> http://paste2.org/p/2834017
[10:19] <tjaalton> oh :)
[10:19]  * mlankhorst just builds on launchpad with high priority, evil, I know
[10:19] <mlankhorst> I do feel guilty about it though, so it's ok!
[10:20] <RAOF> tjaalton: Dump in /etc/schroot/setup.d as 60add-local-repository, combine with http://paste.ubuntu.com/1619254/ and you've got a raring-local chroot that builds against ~/Builds
[10:21] <tjaalton> that's neat
[10:21] <tjaalton> I'll probably use reprepro still for some stuff, but this is good enough for builds :)
[10:22] <mlankhorst> but if I had to test before pushing, I'd probably mess up my own raring chroot/netboot image instead. It can do both :-)
[10:22] <RAOF> Arsing llvm
[10:22] <RAOF> What's a man got to do to build mesa in a ppa these days :)
[10:23] <mlankhorst> push dh-exec 0.6 to precise? :P
[10:23] <tjaalton> next I'd like it to build under /run/shm, guess my ssd will wear more quickly because of sbuilding all the time :)
[10:23] <mlankhorst> It needs 0.3 or newer for building llvm-3.2
[10:24] <RAOF> tjaalton: Heh. My sbuild config used to also have raring-tmpfs, too, before btrfs-snapshot.
[10:24] <mlankhorst> tjaalton: it will kill itself even faster here because I'm using encryption, I tested, it's not cpu limited any more after a fix!
[10:24] <mlankhorst> and it's going like 400 mb/s
[10:25] <RAOF> tjaalton: I could probably find the config I was using to do tmpfs stuff.
[10:25] <tjaalton> that would be nice
[10:26] <tjaalton> my ssd died after one year, so will try to minimize it's use now
[10:27] <mlankhorst> I'm a terrible person, and keep backups for that. :-)
[10:28] <tjaalton> me too, but only of my own $HOME, screw the others :)
[10:28] <tjaalton> or the system files
[10:28] <mlankhorst> oh everything important is in a git repository
[10:28] <tjaalton> still don't have a working smtp config..
[10:28] <RAOF> Actually, from memory I think it's pretty easy - you mount /var/lib/schroot/tmpfs-overlay in /etc/fstab, then use that as the overlay dir in the schroot config.
[10:29] <mlankhorst> since ssd's have been so fast I've been pretty lazy though. I'm just building from ssd since doing otherwise takes more effort and longer
[10:29] <tjaalton> i have 16 gigs of ram, better use it for something!
[10:29] <mlankhorst> I do too
[10:30] <mlankhorst> Cached:         12110996 kB
[10:30] <mlankhorst> it's practically building from memory already
[10:32] <tjaalton> hmm, I should probably clean up my build dir :)
[10:33] <tjaalton> a ton of cruft there slowing sbuild down
[10:33] <mlankhorst> that's why I don't use tmpfs ;-)
[10:34] <tjaalton> the destination is on ssd
[10:39] <tjaalton> E: 60add-local-repository: gpg: keyring `/var/lib/sbuild/apt-keys/secring.gpg' created
[10:39] <tjaalton> E: 60add-local-repository: gpg: keyring `/var/lib/sbuild/apt-keys/pubring.gpg' created
[10:39] <tjaalton> E: 60add-local-repository: gpg: no default secret key: secret key not available
[10:39] <tjaalton> E: 60add-local-repository: gpg: signing failed: secret key not available
[10:40] <tjaalton> did I miss something?
[10:41] <tjaalton> probably should create the key first :)
[10:47] <tjaalton> meh, refuses to install llvm-3.2-dev
[10:52] <tjaalton> RAOF: I guess your sbuild runs update too :)
[10:58] <mlankhorst> did I mess up? :s
[10:58] <mlankhorst> oh wait in sbuild I suppose
[10:58] <tjaalton> nah, it's the repo
[10:58] <tjaalton> well, now it's claiming libdrm* is unsigned
[10:59] <tjaalton> the llvm maintainer promised to add the backend \o/
[10:59] <mlankhorst> \o/
[11:19] <tjaalton> grr
[11:19] <tjaalton>  sbuild-build-depends-mesa-dummy : Depends: libdrm-dev (>= 2.4.39) but it is not going to be installed
[11:26] <mlankhorst> you forgot to bump libdrm-dev? :P
[11:27] <mlankhorst> probably needs to be 2.4.42 there
[11:28] <tjaalton> didn't update the branch yet
[11:28] <tjaalton> this is the apt resolver failing
[11:28] <tjaalton> refuses to install stuff from the local repo
[11:31] <tjaalton> ok, it was 2.4.42-1 test build that was broken
[11:32] <tjaalton> rebuilt -0u1 and it's fine now
[11:39] <tjaalton> mlankhorst: did you test that it built using shared llvm libs?
[11:39] <tjaalton> I got the same issue with gensymbols
[11:40] <tjaalton> or did i
[11:41] <mlankhorst> I'm testing on quantal atm
[11:42] <mlankhorst> I want to get the 9.0.2 sru done first :)
[11:43] <tjaalton> I'll pastebin this.. guess it's normal after all
[11:53] <tjaalton> http://pastebin.com/8bMUBdDU
[11:54] <tjaalton> hm no :)
[11:55] <mlankhorst> do you have the full debdiff to llvm-3.2 btw? I'm missing radeonsi
[11:56] <mlankhorst> hm indeed, tons of symbols
[11:58] <mlankhorst> sounds like it statically linked against libgallium or something
[11:59] <mlankhorst> surprise surprise, it probably did
[12:01] <mlankhorst> oh well build libgallium dynamically and you're fine
[12:03] <tjaalton> is there a separate option for it?
[12:04] <mlankhorst> one line hack would be noinst_LTLIBRARIES -> lib_LTLIBRARIES
[12:05] <mlankhorst> in src/gallium/auxiliary/Makefile.am, but no idea if it works yet
[12:05] <tjaalton> ok
[12:08] <tjaalton> wth, the diff with the upstream branch shows changes all over the place
[12:12] <mlankhorst> aw still broken
[12:13] <mlankhorst> grabbing rbug, svga and some vmw symbols
[12:14] <mlankhorst> could be fixed in the same way I suppose
[12:14] <mlankhorst> either that or I just hack in the visibility things for now
[12:17] <mlankhorst> probably better for now
[12:19] <tjaalton> so my merge of git master on jan 9th created issues
[12:22] <tjaalton> dunno what's the best way to get out of it, other than maybe cleaning them up in a separate commit, or losing history of debian/
[12:23] <mlankhorst> do you want to rewind?
[12:23] <mlankhorst> or move forward
[12:24] <tjaalton> well, rewind wouldn't be that bad
[12:24] <tjaalton> I guess..
[12:27] <mlankhorst> well trying to build it atm, hopefully working this time by adding some visibility cflags back
[12:30] <tjaalton> I'll rebuild the branch, first merge whatever was there before the bad merge, then cherry pick the commits to debian/ after that
[12:31] <mlankhorst> down a lot of symbols..
[12:31] <mlankhorst> still missed a few
[12:37] <mlankhorst> driver_descriptor@Base remaining
[12:38] <mlankhorst> as good as it gets I suppose
[12:39] <mlankhorst> tjaalton: http://paste.ubuntu.com/1620151/
[12:40] <mlankhorst> there's probably a better fix, but meh..
[13:03] <tjaalton> mlankhorst: ok, thanks
[13:04] <mlankhorst> you need to add driver_descriptor@Base to the symbols list btw
[13:34] <tjaalton> sigh
[13:35] <tjaalton> conclusion; git merge does funky stuff
[13:35] <tjaalton> despite merge -s ours
[13:35] <tjaalton> i got exactly the same diff
[13:37] <tjaalton> for some reason it decides the remote is more important
[13:37] <mlankhorst> you can override it. :P
[13:37] <mlankhorst> git checkout whatevercommit . git commit --amend
[13:38] <tjaalton> hmh?
[13:38] <mlankhorst> to amennd the merge commit
[13:39] <tjaalton> what's whatevercommit
[13:40] <mlankhorst> erm what you want the HEAD to look like after merge
[13:40] <tjaalton> sure I can touch whatever but it's work
[13:41] <tjaalton> http://pastebin.com/kGwnuACC
[13:42] <mlankhorst> git rm debian src; git checkout COMMIT src ?
[13:43] <tjaalton> don't want to lose history for debian
[13:43] <mlankhorst> erm skip the rm debian then
[13:43] <tjaalton> hmm
[13:46] <tjaalton> hah
[13:46] <tjaalton> did the trick
[13:46] <tjaalton> amended with the merge
[13:48] <tjaalton> checkout $path sounds interesting..
[13:50] <mlankhorst> :-)
[13:50] <tjaalton> well, it does lose history, so it's not useful for pulling the packaging
[13:51] <mlankhorst> not really? or at least git log debian/ kept working for me
[13:51] <tjaalton> only if your branch had debian/ at some point
[13:52] <mlankhorst> yeah you need to start from debian branch
[13:52] <tjaalton> but if you checkout the upstream branch and then the packaging on top of it
[13:52] <tjaalton> right
[13:52] <tjaalton> works for src/ etc
[13:52] <tjaalton> now where was I ..
[13:52] <tjaalton> have a dozen branches to weed through :P
[15:01] <tjaalton> attached a power meter between the outlet and ups, combined consumption is around max 200W including the monitor and DAC when building mesa with ivb :)
[15:01] <tjaalton> idle is 90-100
[15:03] <tjaalton> libgles2 needed one symbol added, seems fine now
[15:11] <tjaalton> mlankhorst: libxatracker1 is still big, but at least it didn't complain about the symbols
[15:12] <mlankhorst> tjaalton: yeah that was the goal :-)
[15:12] <mlankhorst> I didn't feel like making all those libraries shared just yet
[15:31] <tjaalton> ok now onto the ubuntu branch..
[15:42] <mlankhorst> well radeon piglit results done, now i915 I suppose.
[15:49] <mlankhorst> well afaict no regressions on radeon \o/
[16:05] <tjaalton> ugh, the gallium dricore patches make my head hurt.. I'll just push what I have so far
[16:05] <mlankhorst> want me to rebase the gallium and dricore patches again? :P
[16:06] <tjaalton> well, yeah, all the files 117 touches have vanished :)
[16:06] <tjaalton> for starters
[16:06] <mlankhorst> well I'm waiting on piglit to finish anyway
[16:06] <mlankhorst> why not
[16:14] <tjaalton> mlankhorst: force-pushed
[16:15] <mlankhorst> tjaalton: nitpick, it's not from llvm. it's from libgallium and those other static libs where I added the flags to
[16:16] <tjaalton> well, do it properly and we can drop the patch :)
[16:16] <tjaalton> with a properly-named one
[16:16] <tjaalton> er, replace it with..
[16:16] <mlankhorst> I'm probably just going to push it upstream..
[16:17] <tjaalton> of course, even better
[16:20] <mlankhorst> tjaalton: 117 patch should no longer apply, but the fix is even easier to make :-)
[16:21] <tjaalton> good
[16:23] <mlankhorst> but I think it's better to just check with upstream first
[16:25] <mlankhorst> actually I guess I could just do an ugly hack for now
[16:26] <mlankhorst> seems we don't add version to libgallium in previous patches anyway
[16:28] <mlankhorst> done with libgallium, now dricore gallium..
[16:32] <mlankhorst> oh right, that one was annoying
[16:34] <mlankhorst> it was a bit of abuse since I needed libmesagallium to be done after libdricore, so I had to move it to the mesa/libdricore directory
[16:39] <mlankhorst> wow, only d3d1x is still using makefiles
[16:46] <mlankhorst> ok I'm still thinking about the best way to approach the dricore fix, but gallium was easy
[16:57] <tjaalton> so it wasn't a great idea to push libxi to raring, need to revert the new stuff for now :P
[17:02] <mlankhorst> broke unity?
[17:02] <tjaalton> kde builds
[17:02] <mlankhorst> ah, worse
[17:02] <tjaalton> but probably others too
[17:03] <tjaalton> if includes both XInput2.h and Xfixes.h it'll go boom, duh
[17:04] <mlankhorst> well lets see if it builds now
[17:04] <mlankhorst> oh right
[17:04] <mlankhorst> need new llvm and new libdrm
[17:05] <mlankhorst> tjaalton: I pushed what I have
[17:05] <mlankhorst> it's guaranteed to break on building
[17:06] <mlankhorst> but hopefully that only happens when it finds a new libmesagallium*.so
[17:06] <mlankhorst> if not, let me know
[17:10] <tjaalton> yup, fails
[17:11] <tjaalton> http://pastebin.com/xQM8QVb5
[17:24] <ricotz> tjaalton, hi :)
[17:24] <ricotz> mlankhorst, hey
[17:25] <ricotz> tjaalton, did you notice some conflicts between libxi-dev and libxfixes-dev?
[17:25] <ricotz> /usr/include/X11/extensions/Xfixes.h:274:17: error: conflicting types for 'BarrierEventID'
[17:25] <ricotz> /usr/include/X11/extensions/XInput2.h:173:22: note: previous declaration of 'BarrierEventID' was here
[17:25] <Sarvatt> #ubuntu-devel :P
[17:25] <ricotz> ah good
[17:26] <mlankhorst> ricotz: hello
[17:26] <tjaalton> ricotz: yeah, fixed already
[17:27] <tjaalton> I'll upload another one to the ppa, reverting the revert.. and then libxfixes dropping the old stuff
[17:27] <ricotz> tjaalton, thanks!
[17:27] <mlankhorst> tjaalton: yeah looks like I'm including too much somehow
[17:27] <mlankhorst> I guess you need to exclude state_tracker/st_glsl_to_tgsi.cpp from the 118 patch
[17:27] <mlankhorst> in src/mesa/libdricore/Makefile.am
[17:28] <ricotz> tjaalton, will be barrier stuff move away from xfixes?
[17:28] <ricotz> be/the
[17:28] <mlankhorst> looks funny there anyway, it was probably to work around some issue
[17:28] <tjaalton> ricotz: yes
[17:28] <ricotz> tjaalton, ah i see
[17:28] <tjaalton> slightly different anyway
[17:28] <mlankhorst> tjaalton: anyhow I have to leave for a bit, I think that specific issue should be easy to fix with that hint :-)
[17:29] <tjaalton> mlankhorst: ok, I'll give it a got..
[17:29] <tjaalton> -t
[17:29] <mlankhorst> afk!
[18:04] <tjaalton> fixesproto and lib pushed to c-x/x-s
[18:09]  * mlankhorst back-ish
[18:19] <tjaalton> hmm, could I upload xserver to the ppa then
[18:19] <mlankhorst> did you get mesa running?
[18:20] <tjaalton> ah, no
[18:20] <tjaalton> http://pastebin.com/xQM8QVb5
[18:20] <mlankhorst> that's  the same you posted earlier?
[18:20] <tjaalton> oh right :)
[18:22] <tjaalton> http://pastebin.com/p65CeikP
[18:23] <mlankhorst> oh so that's why I needed that file
[18:36] <mlankhorst> tjaalton: I pushed the fix, I hope..
[18:36] <tjaalton> building..
[18:40] <tjaalton> mlankhorst: http://pastebin.com/axgf3Wst
[18:41] <mlankhorst> still the case? evil!
[18:41] <tjaalton> :)
[18:41] <mlankhorst> I guess it needs to be moved around
[18:43] <mlankhorst> tjaalton: what if you move that egl_gallium_la_LIBADD += $(MESAGALLIUM_LIBS) line in egl-static/Makefile.am all the way down to bottom of the file?
[18:44] <mlankhorst> I'm just guessing, I need to get my hands on a working llvm-3.2 build
[18:52] <tjaalton> mlankhorst: grab it from the ppa :)
[19:01] <tjaalton> mlankhorst: still the same
[19:01] <mlankhorst> oh :/
[19:01] <mlankhorst> I'll look tomorrow
[19:01] <tjaalton> yeah
[19:02] <Sarvatt> tjaalton: going to upload xserver?
[19:03] <Sarvatt> or want me to do it? I can do the drivers too
[19:03] <Sarvatt> oh, long queues :(
[19:04] <Sarvatt> and sorry for not pushing it to expeirmental, didn't realize it was there also
[19:13] <tjaalton> ha, no worries, sorry for being tired/grumpy last night :)
[19:13] <tjaalton> feel free to upload them!
[19:34] <Dandel> Sarvatt: I spotted a major problem with piglit packages :/
[19:35] <Dandel> when running from installed packages, I found out that resume is broken.
[19:36] <Sarvatt> doh, did it just start happening one day or always been like that?
[19:36] <Sarvatt> it's building daily git snapshots and i haven't looked at git in like 8 months
[19:37] <Dandel> it's not a one day issue
[19:37] <Dandel> it's a combination of bugs
[19:39] <Dandel> 1 sec while i get the log from git to find out which commit is the likely culprit.
[19:40] <Dandel> most likely, it's this file ( in combination): http://cgit.freedesktop.org/piglit/log/framework/shader_test.py
[19:45] <Dandel> Sarvatt: also, on a similar note, piglit really needs to capture the core dumps ( and heap stacks )
[19:49] <bryce> Dandel, agreed
[19:49] <bryce> Dandel, well possibly we need a wrapper
[19:49] <Dandel> bryce: that's actually somewhat easy to "mimic"
[19:49] <Dandel> it already can identify when the test crashes
[19:50] <Dandel> it just needs a little bit of expansion ( based on what xbmc does for their launcher ) to be able to fully capture the stack.
[20:43] <Dandel> Sarvatt: I have a few fixes that should work... want to give em a try?
[23:21] <Dandel> just double checked, and there's some patches on the piglit mailer that seem to address the issue about resuming tests.


[00:07] <LaserJock> Burgundavia: bahhh, leave me alone ;-)
[00:16] <keescook> cjwatson: cool, thanks.
[00:29] <Fujitsu> keescook: In ubuntu-cve, what do you do about CVEs in universe packages at the moment?
[00:29] <keescook> Fujitsu: currently we just document them, and marked the "needs-triage"
[00:30] <keescook> (but this is why I want to changelog scanner running again -- the universe CVEs are getting out of date)
[00:30] <Fujitsu> keescook: Do you attach package references to them? (sorry, still checking it out, X died on me a couple of times)
[00:31] <keescook> Fujitsu: yes, we assign the CVE to packages.
[00:31] <keescook> (the "new CVE" process is codified in the "check_cves" script in the root dir of the tree)
[00:31] <Fujitsu> I would explore, but I fear the working copy in ~pitti is woefully out of date.
[00:31] <keescook> it basically display information about the CVE, and then prompts for package name, etc, then spawns and editor after populating the new CVE file
[00:31] <Fujitsu> Aha.
[00:32] <keescook> Fujitsu: the bzr tree is okay, so a local "bzr branch" of it should be fine.
[00:32] <Fujitsu> keescook: Right, I'm doing that now; it just takes a while.
[00:32] <keescook> true.  The "README" in the root dir is good too.
[00:32] <Fujitsu> (and -intel being really unstable and occasionally hard-locking at the moment doesn't help)
[00:32] <keescook> (let me go see if I can convince the working tree to update...)
[00:33] <Fujitsu> A bzr up in ~pitti/bzr/ubuntu-cve should do it.
[00:33] <Fujitsu> Hm, maybe a co.
[00:33] <Fujitsu> If rookery even has a recent enough bzr, that is...
[00:34] <keescook> woo, it worked.
[00:34] <Fujitsu> Aha, thanks.
[00:36] <keescook> if people want to start helping with the tracking, I'll likely move it to a bzr tree on LP
[00:38] <Fujitsu> I'll definitely be going through it regularly and filing bugs for universe stuff, and hopefully getting some if it fixed.
[00:39] <keescook> Fujitsu: cool; one of the other script I was hoping to write was an auto-LP-bug-opener
[00:42] <Fujitsu> keescook: That would be good.
[00:42] <Fujitsu> Yay, checkout finished.
[00:42] <keescook> I figure it'd look up the CVE, check for the pkg, and if it's not there, open a new bug.  with python-launchpad-bugs it should be pretty straight forward.
[00:42] <keescook> heh
[00:45] <Fujitsu> keescook: I presume you would know this if anybody did: is there a way to apt-get source something like `sourcepackage/release'?
[00:46] <keescook> Fujitsu: if there is, I haven't found it.  I tend to use sbuild+LVM and do the apt-get sources inside the chroots
[00:46] <keescook> schroot -c dapper "apt-get source ...."
[00:46] <Fujitsu> Ah.
[00:46] <Fujitsu> Yep.
[00:50] <Fujitsu> keescook: DNE is for stuff that just isn't packaged, NOT FOR US is stuff that will never be?
[00:51] <keescook> Fujitsu: there is a bit of confusion there, but basically, yes.
[00:52] <keescook> jdstrand was making the distinction, but I haven't tended to.
[00:52] <keescook> NFU would be for totally alien things (cisco, microsoft, etc), DNE for random php CMSs, etc
[00:52] <Fujitsu> I can see it might be useful at times.
[00:52] <Fujitsu> Yep.
[00:52] <Fujitsu> That's what I thought.
[00:55] <keescook> Fujitsu: I've updated the README a bit to clarify
[00:56] <keescook> (haven't pushed yet)
[00:56] <Fujitsu> keescook: Thanks.
[00:57] <emgent> heya keescook ^^
[00:57] <keescook> hi emgent !
[00:57] <emgent> all good ? :)
[00:58] <keescook> emgent: I need another 10 hours a day.  I'll have to move to Jupiter or something.  :)
[00:58] <emgent> ehhehe
[00:58] <lamont> keescook: net connectivity will be very laggy from there.
[00:59] <Fujitsu> lamont: Just a bit.
[00:59] <keescook> lamont: crap, good point.  radiation I can deal with.  latency, though.... no way.
[01:00] <Fujitsu> keescook: Are we manually tracking things synced into Hardy at the moment?
[01:00] <keescook> Fujitsu: yeah, there's nothing automatic in the CVE tracker at this point.
[01:00] <lamont> keescook: someone was talking in church a few years back about "what's important" based on his getting a job offer to an island off the coast of south america.  My singular question when he started the discussion (to myself, not out loud) was "How fat is the pipe???"
[01:01] <Fujitsu> keescook: And autosyncs aren't logged anywhere. Joy.
[01:01] <keescook> lamont: hehe. when I was comparing climates when moving away from Chicago, "is there any technology?" was the first question after climate.  Pago Pago was right out.  :)
[01:04] <lamont> exactly
[01:13] <Fujitsu> keescook: What's the correct status if a release already has the fix? (not in SECURITY, but RELEASE)
[01:14] <keescook> Fujitsu: if it's in hardy, it's the "devel" release, in which case I tend to mark things as "not-affected" if they were okay when I got there, or "release ($VERSION)" if I had to apply fixes
[01:15] <keescook> if it's an earlier release and the CVE is just out of date or wrong, I would mark it not-affected
[01:15]  * desrt allows google to convince him that "kees" is a valid nickname for people named cornelius
[01:15] <Fujitsu> keescook: OK. (there's very little documentation on what the statuses are for...)
[01:15] <keescook> heh
[01:16] <keescook> Fujitsu: valid point, I can add a section for that.
[01:16] <slangasek> desrt: even though neither google translate nor babelfish substantiates the claim that "kees" is a Dutch word for "horn"? :)
[01:17]  * keescook is confused now
[01:17]  * desrt too
[01:17] <Fujitsu> keescook: Is the upstream_blah field meant to contain the fixed version?
[01:18] <keescook> Fujitsu: yeah, look in the retired/ tree for recent CVEs.
[01:18] <Fujitsu> Good point.
[01:18] <slangasek> keescook: by me, or by something security-ish?
[01:19] <keescook> slangasek: by you.  where is the "horn" claim from?
[01:20] <slangasek> keescook: one of the google hits I found when I was looking for it said that etymologically, "kees" is a nickname for "Cornelius" because it's a Dutch word meaning horn (where "cornelius" < Lat. CORNUS, horn (of an animal))
[01:21] <slangasek> but then I couldn't find anyone that agreed this is what "Kees" meant in Dutch :)
[01:21] <keescook> slangasek: bizarre.
[01:22] <keescook> google of "kees cornelius" shows all sorts of people with stuff in ()'s.  :P
[01:22] <keescook> http://en.wikipedia.org/wiki/Dutch_name
[01:23] <slangasek> yes, but all that proves is that you've compromised google. and wikipedia.
[01:23] <keescook> slangasek: *rofl* if only.
[01:24] <keescook> (is there a "blame" view in wikipedia?)
[01:24] <slangasek> not AFAIK :)
[01:25] <keescook> sweet.  then you'll never find n0tk33s's strategic edits!
[01:25] <Fujitsu> Heh.
[01:26] <BBHoss> anybody here know how to get ObjC code to compile on 7.10?
[01:26] <BBHoss> i keep getting an error that cc1obj cant be found
[01:28] <minghua> BBHoss: Do you have gobjc package installed?
[01:28]  * Hobbsee waves
[01:28] <keescook> heya Hobbsee
[01:28] <BBHoss> lemme check
[01:28] <Hobbsee> keescook!
[01:29] <BBHoss> apparently not :)
[01:29] <BBHoss> cool thank minghua
[01:30] <jdstrand> Fujitsu, kees: wrt NFU and DNE, I have basically said that NFU is for something that will/cannot be used in/on Ubuntu (eg Cisco IOS), but DNE is something that could actually run on Ubuntu (ie php apps), but isn't in the archive
[01:30] <jdstrand> but like kees said, it's really pretty loose and means the same thing in the end
[01:30] <Fujitsu> jdstrand: That makes sense.
[01:31] <slangasek> not-for-exist
[01:32] <keescook> jdstrand: I'm add a section on "status"
[01:32] <jdstrand> keescook: cool
[01:34] <jdstrand> Fujitsu, keescook: I have on my TODO list to somehow check upstream_pkg against devel, and warn if it looks like it is fixed in devel (kinda like we do with retired)
[01:34] <jdstrand> it'd slow things down though, so would likely need to be a separate script or option
[01:35] <jdstrand> (I haven't worked out much beyond getting it on my todo list ;)
[01:35] <keescook> jdstrand: ooh, yeah, that's another good way to find stuff.  frequently the changelog for such things will just say "New upstream release" without mentioning CVEs.
[01:36]  * keescook adds a TODO file
[01:36] <Fujitsu> jdstrand: That sounds good.
[01:36]  * jdstrand hopes keescook doesn't get too crazy with that TODO file
[01:38] <slangasek> cjwatson: did we have specific text to include for the update-grub ucf template?  this wasn't preserved in the gobby session
[01:39] <slangasek> keescook: or maybe you remember?
[01:39] <keescook> slangasek: oh... did we specify something like that?
[01:40] <slangasek> keescook: well, there was some reason we didn't want to use the standard ucf text, but perhaps the replacement text wasn't fully specified :)
[01:40] <keescook> slangasek: I don't think it came up, but since I'm not familiar with ucf, not everything made sense
[01:43] <emgent> keescook, do you have tomcat ?
[01:43] <keescook> emgent: "have", as in, installed?  I don't, no.
[01:43] <emgent> uhm ok. np.
[01:43] <keescook> but there is tomcat5 and tomcat5.5 in the archive.
[01:43] <emgent> yes i saw
[01:44] <emgent> but i found bug in tomcat 6.0
[01:44] <keescook> ah, cool.  Yeah, that software has a lot of CVEs against it.
[01:45] <emgent> I think in earlier versions too.
[01:45] <emgent> it's a stupid XSS
[01:46] <keescook> I think the other CVEs are mostly XSS too: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=tomcat
[01:47] <emgent> yes i'm in :P
[01:49] <emgent> oh it's old uhm..
[01:49] <emgent> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2449
[01:49] <ubotu> Multiple cross-site scripting (XSS) vulnerabilities in certain JSP files in the examples web application in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.36, 5.0.0 through 5.0.30, 5.5.0 through 5.5.24, and 6.0.0 through 6.0.13 allow remote attackers to inject arbitrary web script or HTML via the portion of the URI after the ';' character, as demonstrated by a URI containing a "snp/snoop.jsp;" sequence. (http://cve.mitre.org/cgi-bin/cvename.cgi?
[01:50] <emgent> poor tomcat :)
[01:50] <keescook> heh
[02:08] <Hobbsee> Mez: unfortunately, only by name at the moment.
[03:22] <tonyyarusso> siretart: Under "Outstanding issues" on https://wiki.ubuntu.com/EncryptedFilesystems, would it make sense to have passphrase/key management available from multiple places?  For instance, it relates to partitions, so you should be able to do it in GParted, but it's also a password/encryption key management task, so it would seem to also make sense to have stuff in Seahorse.
[03:22] <flake> using glade, how do i resize a button or other control on the window 'form' ?
[03:39] <flake> oh i guess I add panes to the window and place/resize controls in there?
[03:40]  * Hobbsee notes this is not a gtk help channel.
[03:41] <flake> otay then..  where is it
[03:42] <flake> and then.. how do you develop, what tools?  Qt?
[03:43] <Hobbsee> for the kde stuff, yes.
[03:43] <Hobbsee> for the gnome stuff, it's gtk.
[03:43] <flake> i can see the panes in this Konversation app
[03:44] <flake> ok
[03:47] <flake> gnome apps work on kde, can kde apps work on gnome?
[03:47] <LaserJock> sure
[03:47] <LaserJock> why wouldn't they?
[03:47] <Hobbsee> works fine here.
[03:51] <Chipzz> flake: there are a number of gtk+ help channels on irc.gimp.org; among which #gtk+ and #pygtk
[05:48] <pabs3> where can I find out about the magical juice that makes Ubuntu JeOS good for VMWare appliances?
[06:48] <warp10> Hi all!
[08:03] <_jm> Anybody who could run a quick GTK+ test program for me real quick? I'm experiencing a very weird bug, but it's so severe I want to ensure it's not a problem with my system.
[08:04] <_jm> For some reason, using the U+FF5E character causes many CJK characters to stop displaying in GTK+. C version at http://pastebin.ca/778083 , Python version at http://pastebin.ca/778084
[08:05] <_jm> Figured it was best to ask somebody to confirm this, rather than posting a bug and getting lots of "works for me".
[08:06] <pasic> hi guys
[08:07] <pasic> i tryed to access samba packages to upgrade/install but them cannot readable at security.ubuntu.comn
[08:07] <pasic> -n
[08:07] <pasic> is it normal, or mistake?
 samba security update is broken and deliberately 403
[08:08] <_jm> They found a problem with it after it was pushed out, so marked it forbidden to stop people from downloading it
[08:08] <pasic> ok:) thx
[08:08] <pasic> what time about when accessible again?
[08:09] <_jm> Likely when the problem is fixed, and a new version pushed out.
[08:09] <pasic> LOL just seen up line :P
[08:09] <pasic> ok, thx ...
[08:53] <jjones> security.ubuntu.com repository files inaccessible.. who do we tell?
[08:54] <jjones> files at  http://security.ubuntu.com/ubuntu/pool/main/s/samba/ with "Last Modified" dates of 16-Nov-2007 have permissions set wrong
[08:54] <lamont> jjones: see http://bugs.launchpad.net/bugs/163116
[08:54] <ubotu> Launchpad bug 163116 in samba "libsmbclient: upgrade fails with error 403" [Undecided,In progress]
[08:54]  * lamont sleeps
[08:56] <jjones> ahhh.. wish I had spotted that on my own, thanks lamont. I'll pass the info along to others on Kubuntu IRC.
[08:56] <lamont> jjones: generally speaking, if the file is 403, you _REALLY_ don't want it.  it has been totally intentional both times I've seen it.
[08:57] <lamont> (as in it's bad enough that it's better to have all these questions than to let people download it...)
[09:02] <jjones> The kubuntu irc seems to be more aware of it now too..  7 hours ago I got nothing.
[10:47] <mdke> mjg59: around by any chance?
[10:58]  * Hobbsee waves
[11:01] <mdke> hi Hobbsee
[11:17] <Kmos> * There's a session about how to properly read Stack traces in #ubuntu-classroom *
[11:50] <\sh> moins
[11:51] <\sh> slangasek, thx for taking care of xclass...
[12:58] <jpatrick> doesn't the ubuntu font has accents?
[12:58] <Chipzz> jpatrick: there is no such thing as the ubuntu font?
[12:59] <jpatrick> ubuntu title font
[12:59] <Chipzz> what on earth are you referring to? :P
[13:00] <jpatrick> ttf-ubuntu-title
[13:03] <Chipzz> heh
[13:04] <Chipzz> anyway, you could probably take a look using something like gucharmap or something
[13:04] <Chipzz> although I believe it does substitution for missing characters
[13:04] <Chipzz> wow
[13:04] <Chipzz> that font does look pretty small
[13:04] <Chipzz> Get:1 http://archive.ubuntu.com gutsy/universe ttf-ubuntu-title 0.1-1 [9858B]
[13:05] <Chipzz> very much possible it in fact does not have accents
[13:15] <ogra> it doesnt have accents ....
[13:16] <ogra> it was done by an australian (who doesnt use accents) focused on the ubuntu string (which doesnt have accents either)
[13:16] <ogra> feel free to submit patches for accents ;)
[13:17] <Hobbsee> bah.  who needs accents, anyway... </australian>
[13:17] <jpatrick> ogra: and how could I do that?
[13:17] <ogra> jpatrick, modify it, file a bug, attach a diff for the modifications you do to the source
[13:24] <jpatrick> ogra: there appears to be a ttf-ubuntu at http://wiki.ubuntu.com/CatalanTeam/Grafisme with accents
[13:24] <ogra> that should be included then
[16:16] <ogra> jpatrick, hey, thanks :)
[16:17] <jpatrick> ogra: don't mention it
[16:18] <ogra> anything wrong ?
[16:18] <jpatrick> nope
[16:18] <ogra> :)
[16:19] <jpatrick> just saying "bitte" :)
[16:19] <ogra> ah :) gut
[16:19] <ogra> hab ich falsch verstanden :)
[17:46] <Skiessi> why nvidia-glx doesn't get updated to work with xserver-xorg-core?
[17:47] <Skiessi> http://packages.debian.org/sid/nvidia-glx they have it already in debian :o
[17:48] <Skiessi> or should I go talk about hardy in #ubuntu?
[17:49] <Skiessi> oh they've restarted #ubuntu+1, I'll ask there
[18:12] <cjwatson> slangasek: I haven't gone through all my notes yet, but I'm not sure we specified text
[18:12] <cjwatson> I often tend to leave that up to the implementor in specs anyway ...
[18:34] <kaleh> hello. how to set the path for a particular forlder, so as to run binaries from it?
[18:34] <kaleh> do i have to use the setenv command?
[18:37] <cjwatson> kaleh: please use #ubuntu or https://answers.launchpad.net/ubuntu
[18:43] <kaleh> sure
[19:30] <IntuitiveNipple> cjwatson: Am I correct that you're a bit of an installer wiz?
[19:31] <jdong> IntuitiveNipple: that's an understatement :)
[19:32] <IntuitiveNipple> hehehe... just I have a quick question. I'm creating automated scripts to build  Ubuntu User Mode Linux file systems and wondering if mkaing use of the installer logics might be a good way to go. Curerntly I'm doing deboostrap followed by a bunch of manual writes to various config files.
[19:33] <Chipzz> IntuitiveNipple: depending on what you need to do you could also use debconf preseeding
[19:33] <IntuitiveNipple> I was wondering if I could customize the server/alternate CD installer scripts or if that would be overkill!
[19:34] <IntuitiveNipple> Chipzz: yeah, that's what I've been looking at. I'm trying to make it create an image that is identical to what the installers might create, to make prevent support issues because of differences in initial configuration
[19:36] <cjwatson> IntuitiveNipple: it ought to be possible, although getting the right kernel in place could be a little tricky
[19:37] <cjwatson> but you can do arbitrary stuff in preseed/late_command scripts, so ...
[19:37] <cjwatson> an automated d-i install is certainly where I'd start
[19:39] <IntuitiveNipple> I'm wanting to not put the kernel in, obviously. I just want to take it from the deboostrap packages point
[19:40] <IntuitiveNipple> The UML kernel is a binary on the host, and once the script has built it, and deboostrap has run, it copies the kernel modules into place.
[19:41] <IntuitiveNipple> OK, from what has been said it sounds like the way to go.
[19:41] <cjwatson> IntuitiveNipple: try preseeding base-installer/kernel/image to 'none' for that, although you'll probably also have to go to a bit of effort to avoid installing a bootloader
[19:41] <cjwatson> but it should all be possible
[19:42] <cjwatson> (it's "debootstrap" BTW)
[19:42] <IntuitiveNipple> lol... no it's 'spulling mistaks'
[19:43] <jdong> deboostrap is used on Oct 31.
[20:40] <attunix> How do I make my own X Windowing System?
[20:43] <Chipzz> attunix: 1) please read the topic; this question is off-topic here; 2) your question is poorly formulated (ambiguous) and 3) supposing you think X itself is crap and you want to write something from scratch; don't. You're most likely looking at the output of top, thinking "OMG X eats a lot of memory! That must be inefficient!" and be terribly wrong about it
[20:45] <attunix> Chipzz: 1) I know this is not an application development room, and it is on-topic, since I would like to attempt to implement this on an Ubuntu system. 2) I'll try to restate my question 3) I don't want to redesign X. GNOME runs on X. KDE runs on X. I want a windowing system like those two (more examples: XFCE, blackbox, etc.) and not make my own x-like thing.
[20:45] <attunix> I mean windowing manager
[20:46] <Chipzz> the fact that you want to implement it on an ubuntu topic still doesn't make your question on-topic ;)
[20:46] <cjwatson> if you wanted to write your own window manager, you would need to start by reading the ICCCM specification
[20:46] <Chipzz> s/ topic//
[20:46] <attunix> ok
[20:46] <cjwatson> but it is NOT for the faint of heart or for anyone who needs to ask questions along the way ...
[20:46]  * Chipzz agrees
[20:47] <Mez> why is it so damned hard to find someone to sponsor a package to debian (It's not like it's even a new package, it's just an update to a current package that I've mainained for about a year now!)
[20:48] <Chipzz> attunix: btw, are you sure you want to implement a wm, or do you want to implement a desktop environment?
[20:48] <attunix> Chipzz: what's the difference?
[20:49] <Chipzz> a wm just draws the borders around windows. a DE consists of a wm plus other things (like a file manager and a panel)
[20:49] <attunix> Chipzz: a windowing manager.
[20:49] <Chipzz> you could argue that both the file manager and the panel are optional, and use something like gdeskltes instead
[20:49] <Chipzz> *gdesklets
[20:50] <slangasek> Mez: because your package has "nonfree" in the name ;)
[20:50] <Mez> slangasek, true ;)
[20:50] <Chipzz> attunix: btw, there are already a lot of wm's out there; have you tried all of them? a good place to start would be freshmeat (let me look up the link for you)
[20:51] <attunix> ok, thanks :)
[20:51] <Chipzz> attunix: http://freshmeat.net/browse/56/ may be a good place to start
[20:52] <Mez> slangasek, *sighs* why I decided to maintain rar I don't know
[20:52] <Chipzz> 153 projects found :P
[20:52] <Mithrandir> Mez: then give it away?
[20:53]  * Chipzz frowns; why does freshmeat consider cedega a wm? :P
[20:53] <Mez> Mithrandir, I'm happy to do it, but not being a DD is a PITA
[20:53] <Mez> cause finding sponsors is a Pain
[20:54]  * Nafallo looks back and forth on Mez and Mithrandir a couple of times
[20:54] <Nafallo> seems hard ;-)
[20:55] <Mithrandir> Nafallo: no, I'm not going to sponsor random packages in Debian.
[20:55] <Nafallo> :-)
[20:55] <Mez> Mithrandir, I was assuming that you wont sponsor unless you've worked with me from the start with it
[20:55] <Mez> however, I've had 2 sponsors dissapear on me so far - so need a new one
[20:56] <Mez> (infinity was one of them!)
[20:56] <Mithrandir> Mez: in this case, it's more that I'm spending little enough time on Debian that pretending to be your sponsor isn't something I want to do.
[20:57] <Mez> Mithrandir, It's no problem, I know that you have a lot of things to do... hence why I didn't ask
[20:57] <Mez> I know quite a few DDs in here, but a lot of them are either too busy, dont want to sponsor a non-free package, or wouldnt go for something that they havent walked through from the start with
[20:58]  * Mithrandir nods.
[20:58] <Mez> that's at least the reason why infinity stopped sponsoring me (the time issues)
[20:59] <Mez> though it'd be nice if I could get NM sponsorship based on rar - make my life easier :D
[20:59] <jdong> hmm can a driver evaluate bug #157867 for SRU?
[20:59] <ubotu> Launchpad bug 157867 in pbuilder "pdebuild-internal broken when XSBC-Orig-Maintainer used because of faulty sed command" [Undecided,Fix released] https://launchpad.net/bugs/157867
[20:59] <jdong> the patch is trivial
[20:59] <jdong> and the debdiff I attached to the bug is already in SRU-ish format
[21:22] <gnomefreak> when the ubuntu installer asks to import settings that doesnt include bookmarks and such right?
[22:15] <Viper550> just wondering, is it possible to make a text-based install which is as fast as the graphical install?
[22:44] <LaserJock> Viper550: depending on the hardware that's already done :-)
[22:45] <Viper550> I mean, using the different method the live CD uses, I know for a fact that it doesn't use debian-installer in the Live CD installer.
[22:45] <LaserJock> yeah sure
[22:45] <LaserJock> I was just teasing
[22:45] <LaserJock> I had an old computer that I tried a LiveCD install on
[22:45] <LaserJock> and it was slower than the Alt disk
[22:46] <LaserJock> it's certainly possible to make a text-based installer use a squashfs system like the LiveCD does
[22:46] <Viper550> yeah
[22:47] <Viper550> They truly need to do that, debian-installer is slow.
[22:47] <Viper550> Think I should blueprint that idea?
[22:48] <wasabi> Eh. I like d-i
[22:48] <wasabi> I really dislike the livecd method of installing. =)
[22:48] <LaserJock> Viper550: I would think a blueprint has already be created to cover that
[22:49] <wasabi> d-i can be done over the network, etc.
[22:49] <wasabi> since it uses apt to retrieve packages
[22:49] <Viper550> I mean, have it "emulate" the process and UI of the installer, but make it use the Squashfs style system
[22:49] <wasabi> Yeah. Discard the best parts? Psssh.
[22:50] <LaserJock> a quite common request is to have the LiveCD have an option that installs without booting into the live system first
[22:50] <Viper550> that'll add ANOTHER CD to the batch, we'd have Live CD, Alternate installer, and then the "advanced installer"
[22:50] <Viper550> also
[22:50] <wasabi> I really like how it is now.
[22:50] <wasabi> LiveCD for UIish desktop people, d-i for people who want something more low level/customizable.
[22:50] <Viper550> On Sabayon, if you're wondering how they handle launching the installer without the full desktop, they just load the installer through Fluxbox.
[22:51] <wasabi> I wouldn't mind having a d-i frontend that used X.
[22:51] <wasabi> But I must have d-i. ;)
[22:51] <Viper550> they do have a d-i frontend with X
[22:52] <LaserJock> Viper550: I think people have thrown around the idea of going lighter than fluxbox
[22:52] <Viper550> openbox?
[22:52] <LaserJock> no WM at all
[22:52] <wasabi> We have a d-i X frontend that WORKS?
[22:52] <Viper550> yeah.
[22:52] <wasabi> News to me. I remember that being the original idea.
[22:52] <wasabi> But nobody ever finishing it
[22:52] <Viper550> http://www.cyberciti.biz/tips/wp-content/uploads/2006/08/debian-testing-gui-installer-paritition-disks-2.png final version uses a Clearlooks theme though
[22:53] <Viper550> It's not default on Etch though, you have to type "guiinstall" at the boot prompt to use it
[22:53] <wasabi> Oh, neato.
[22:53] <Viper550> I have been wanting Ubuntu to maybe add that though
[22:54] <Viper550> http://alioth.debian.org/~fjp-guest/tmp/g-i_new_banner_progress.png here's another shot but with the theme
[22:54] <wasabi> I really like d-i. There's some rough parts of it, sure... but I like how easy it is to customize.
[22:54] <wasabi> I have in a few instances added my own content to it.
[22:55] <wasabi> The hackyness involved in using debconf for complex UI layout sucks.
[22:56] <Viper550> What I wanted was maybe a text-based d-i "clone", emulates it exactly (maybe even using debconf), but copies files instead of installing packages.
[22:58] <wasabi> why?
[22:58] <wasabi> instaling packages is little more than copying fies.
[22:59] <wasabi> And any other overhead should actually just be fixable.
[22:59] <Viper550> but with debian-installer, it's gotta go through this "complex ritual" of configuring them and all that too.
[22:59] <wasabi> It's not done on the LiveCD because you can't boot into packages/ ANd with a full desktop you can't fit a package of everything.
[22:59] <Viper550> compress it?
[22:59] <wasabi> It's already out of psace.
[22:59] <wasabi> Lots of packages have postinst scripts that do nothing. Thouse should be fixed.
[23:00] <wasabi> Lots of them that do things repeatidly, we have dpkg triggers now
[23:01] <wasabi> THere's the slight CPU overhead of decompressing the files.
[23:01] <wasabi> BUt you do sort of have that with the LiveCD too, since it's squashed
[23:02] <wasabi> Hmm. In fact, makes me wonder if it's really the case that the d-i shouldn't be possibly made FASTER than the LiveCD. Reading a single .deb from a CD is no doubt faster than reading thousands of files individual.
[23:02] <wasabi> seeking on a CD is not good.
[23:08] <luk__> s/guiinstall/installgui/
[23:09] <jdong> wasabi: the livecd is compressed way harder than .deb packages...
[23:09] <jdong> AFAIK squashfs uses gzip level 9 basically
[23:09] <wasabi> ahh
[23:09] <wasabi> WHy can't data.tar.gz be done that way?
[23:10] <jdong> the main overhead with ubiquity is that of the live environment to begin with
[23:10] <jdong> unpackaging .debs definitely is more IO intensive than what ubiquity does.
[23:10] <wasabi> Mind explaining how?
[23:10] <jdong> there are still postinsts that do real work
[23:10] <wasabi> Sure.
[23:10] <jdong> while that would be "cached" on a liveinstall
[23:10] <jdong> because the results of the postinst scripts would be saved essentially.
[23:11] <wasabi> Of course.
[23:11] <jdong> not to mention temp files are written, dpkg databases are written, dependencies are resolved, and so on in a dpkg based install
[23:11] <wasabi> Heh. okay. ;)
[23:11] <jdong> I don't think d-i can ever become faster than a copy-the-files based install method... it can probably get very close though