[00:14] <jose> Hello, I'm hoping you guys can help me. I followed Daniel Holbach's videocast for setting up the tools. When I type in "pbuilder-dist natty create" I get an error, but when I type in "pbuilder-dist lucid create" it works. Is this because I'm running on Lucid?
[00:15] <jose> Oops, sorry didn't realize the message above was partly cut off. I followed Daniel Holbach's videocast, and now I'm having the problem mentioned above.
[00:20] <Bachstelze> jose: please pastebin the exact error
[00:20] <Bachstelze> !pastebin| jose
[00:22] <jose> http://paste.ubuntu.com/549182/
[00:24] <jose> Any ideas?
[00:24] <Bachstelze> hmm, I'm using pbuilder directly, not with pbuilder-dist, so I don't know how you're supposed to get that script
[00:25] <maxb> is it in ubuntu-dev-tools ?
[00:25] <Bachstelze> it's in the package debootstrap in natty, you should be able to download it from packages.ubuntu.com and install it, but that's a bit ugly
[00:26] <jose> So, what do you recommend?
[00:27] <stgraber> jose: debootstrap doesn't seem to know natty. Maybe there's a backport of debootstrap for lucid that adds support for natty or you can workaround it with: sudo ln -sf gutsy /usr/share/deboostrap/scripts/natty
[00:27] <Bachstelze> I would recommend not using pbuilder-dist :p I'm not sure what it does but I'm doing fine without it
[00:27] <jose> If I run "sudo pbuilder --create natty" it seems to work fine. Any problems with doing so?
[00:28] <Bachstelze> you'll have a problem if you want to run several pbuilders (for different releases or architectures), the wiki has a nice .pbuilderrc that lets you do that with pbuilder
[00:29] <Bachstelze> !pbuilder
[00:29] <Bachstelze> jose: look in section 13
[00:31] <cjwatson> there should be a working debootstrap for everything up to natty in lucid-backports
[00:32] <cjwatson> yeah, there is, I just checked
[00:33] <jose> Okay, so what you guys are trying to say is if I do what I mentioned above, I'll only be able to work on natty?
[00:33] <jose> cjwatson, so do I have to update something?
[00:33] <cjwatson> yes, upgrade your debootstrap package to the version in lucid-backports and the error you showed will go away
[00:34] <Bachstelze> jose: http://packages.ubuntu.com/lucid-backports/debootstrap you can get it from here, or enable the backports in your package manager
[00:37] <jose> Okay, let's see if that works.
[00:39] <jose> Thank you, that fixed it. Where is all that data landing?
[00:53] <hakermania> happy new year
[01:57] <dnivra> hello. I am packaging openteacher and would like to know which template to use to create manpage- manpage.1.ex, manpage.sgml.ex or manpage.xml.ex? is there some preference given to either of them? also how can i watch a bazaar branch? is it possible?
[02:05] <maxb> my suggestion for manpages would be to use whichever formatting language tou are familiar with
[02:05] <maxb> it's not clear what you mean by watching a bazaar branch
[02:06] <dnivra> i'm writing man pages for first time and have not really worked with sgml/xml. what would you suggest?
[02:06] <dnivra> "watch" in the sense check upstream for changes using 'uscan'.
[02:07] <maxb> ah, no, you can't watch a branch with uscan
[02:08] <dnivra> so no way of adding it. great!
[02:09] <dnivra> maxb, any suggestions/advice on man pages? i'm totally new to packaging :).
[02:10] <dnivra> i read that having man pages is a plus and makes it easier to get it into debian and hence to ubuntu as well :). so just wanted a few opinions :).
[12:29] <c_korn> Happy new year!
[12:30] <TheNumb> Hey guys. Any tips about curing alcohol poisoning?
[16:34] <bdrung> kklimonda: around?
[17:43] <kklimonda> bdrung: yes
[17:43] <bdrung> kklimonda:  what do you suggest as name for dprintf?
[17:44] <kklimonda> bdrung: I'd suggest simple debug
[17:44] <kklimonda> or debug_print
[17:45] <bdrung> debug is better
[17:45] <bdrung> kklimonda: are you interested in reviewing it?
[17:47] <kklimonda> bdrung: sure, but not today :)
[17:47] <ari-tczew> hey, what does mean last column on page http://qa.ubuntuwire.org/debcheck/debcheck.py?dist=natty&list=ALL ?
[17:48] <bdrung> kklimonda: what do you think about the function names?
[17:50] <ari-tczew> who is reponsible for debcheck/ubuntuwire?
[17:51] <kklimonda> bdrung: what happens if kibi_init isn't called before other kibi functions?
[17:51]  * tumbleweed prods bdrung with a code review reminder
[17:52] <bdrung> kklimonda: it uses the packers default config
[17:52] <kklimonda> bdrung: mhm, great
[17:53] <bdrung> we have three levels of configuration: user, system, and packager
[17:53] <kklimonda> bdrung: but kibi_init do have a warning that it should be called before any other kibi function.
[17:54] <kklimonda> bdrung: I'm asking because later there is a #define g_format_size_for display kibi_format_size...
[17:54] <kklimonda> bdrung: if other people are like myself someone will forget to add kibi_init call at some point ;)
[17:55] <bdrung> kklimonda: the warning is there because the user and system configuration is ignore if you don't run kibi_init
[17:56] <bdrung> kklimonda: there is an alternative: check in every function call if libkibi is initialized (one if(foo == NULL)) and drop kibi_init
[18:00] <kklimonda> bdrung: I wonder.. it makes sense, most _init functions, at least in the "G" world,  are there because you pass some arguments to them. g_type_init is the only exception I can think of right now
[18:00] <cdbs> ari-tczew: There are some people who maintain ubuntuwire, such as wgrant and ajmitch (I may be wrong)
[18:01] <kklimonda> (also, an additional condition check is a performance penatly of sort - even when you use UNLIKELY macro)
[18:01] <bdrung> kklimonda: it's a trade of. what do you prefer?
[18:08] <kklimonda> bdrung: I guess it depends on how often the functions are going to be called - with correcly used UNLIKELY macro the overhead of the if check should be negligible..
[18:10] <bdrung> kklimonda: what do you mean with "unlikely macro"?
[18:13] <kklimonda> bdrung: gcc has __builtin_expect which is, by kernel and by glib, wrapped in LIKELY/UNLIKELY macros - when you use one you inform the compiler that the wrapped condtional is unlikely/likely to evaluate to something - gcc uses it for optimalization
[18:14] <bdrung> kklimonda: can you give me an example?
[18:14] <bdrung> or point me to one?
[18:32] <kklimonda> bdrung: there are quite a lot of examples in glib/gobject sources (sorry for the delay, got a call)
[21:25] <bcurtiswx_> im using bzr bd and it required a version of gsettings-desktop-schemas, so i build that and used dpkg to install it.. (both the regular and -dev) so the version on my system were right.. but it still fails at the dep check.  idk why
[21:27] <ari-tczew> what do you think about merge package devscripts into ubuntu-dev-tools?
[21:31] <dapal> maybe the contrary ;) -- but a bad idea, introducing an unnecessary delta between Debian and Ubuntu
[21:32] <bcurtiswx_> why doesn't bzr bd notice my package version changes ?
[21:38] <bcurtiswx_> http://paste.ubuntu.com/549372/
[22:29] <bcurtiswx_> http://paste.ubuntu.com/549372/ i still can't figure out why its not recognizing the correct version.. any ideas?
[22:57] <em> Hi everyone.
[22:58] <em> I was here quite a long time ago asking about the Racket package for Ubuntu. I was told that Ubuntu cannot make packages and it leaves that to Debian.
[22:58] <em> I was told I should file a bug with Debian, and I did, here -- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592688
[22:59] <em> That was on August 12, 2010, can Racket be in Natty now?
[23:00] <maxb> em: That bug report has not yet resulted in a finished package in Debian
[23:01] <em> That's incredible.
[23:01] <maxb> huh?
[23:01] <em> I filed that bug on August 12, 2010.  They are doing it.
[23:03] <em> Yeah Im not complaining. Im just disappointed.
[23:15] <bdrung> em: the only way to ensure that the software is package is either to do it yourself or to pay someone for it.
[23:16] <em> bdrung: okay how much would that cost?
[23:16] <paultag> bdrung: has anyone ever paid you?
[23:16] <paultag> because that would be sweet.
[23:16] <bdrung> paultag: no
[23:16] <em> how much?
[23:16] <paultag> em: might want to pay someone @debian.org
[23:16] <bdrung> em: you need to find someone.
[23:17] <paultag> bdrung: I s'pose most @canonical get that deal
[23:18] <bdrung> em: the problem you will have if you pay someone for packaging it, you won't have someone who maintains it
[23:18] <em> there is already someone who maintains it. It makes no sense to me.
[23:18] <bdrung> i found this: http://git.debian.org/?p=collab-maint/racket.git
[23:18] <em> look at this -- http://git.debian.org/?p=collab-maint/racket.git;a=commit;h=86f39a16c0caf051cf9800b25858a156bd29b26d
[23:19] <bdrung> it's in NEW -> http://ftp-master.debian.org/new.html
[23:20] <em> what needs to happen so that it is in position so that Ubuntu can have a package for Racket?
[23:20] <paultag> em: we pull every six months from Debian. If it's in Debian, it's most likely it will migrate the next sync
[23:21] <paultag> unless there's a block, but I doubt that muchly.
[23:21] <bdrung> em: a debian ftp-master has to accept the package. then someone needs to request a sync.
[23:21] <bdrung> paultag: it targets experimental. so it won't get synced automatically
[23:23] <paultag> bdrung: roger.
[23:23] <paultag> I did not even look at it
[23:53] <bdrung> kklimonda: the performance loss with removing the kibi_init function would be 1.3 %


[16:01]  * slangasek waves
[16:01] <infinity> o/
[16:02]  * stgraber waves
[16:02] <slangasek> #startmeeting
[16:02] <meetingology> Meeting started Wed Dec 12 16:02:08 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:02] <slangasek> [TOPIC] lightning round
[16:04] <slangasek> $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra cjwatson xnox stokachu)
[16:04] <slangasek> barry cjwatson ev stgraber stokachu xnox ogra doko slangasek bdmurray jodh
[16:04] <barry> win!
[16:04] <barry> bug 1061149 (more debugging, seems related to landscape). bug 1077076 (oneconf ported to py3 landed in trunk, bug 1088536 m-p for packaging). bug 1088535.  patch piloting (status sent to mlist).  done.
[16:04] <infinity> Isn't ogra on holidays?
[16:04] <slangasek> yes, as is jodh
[16:05] <slangasek> and stokachu is also not making the meeting today
[16:05] <cjwatson> Knocked out for part of this week by persistent cough/cold.
[16:05] <cjwatson> Further progress on 12.04 SB backport.  Seems to be mostly done now.
[16:05] <cjwatson> Fixed some embarrassingly old debconf regressions from work I did on dpkg-reconfigure earlier this year.
[16:05] <cjwatson> Half a dozen more cross-building fixes.
[16:05] <cjwatson> debmirror patch to limit mirroring to arbitrary field names by package.
[16:05] <cjwatson> Started work on publishing package set information in archive index files.
[16:05] <cjwatson> Followed up to Jean-Baptiste's autopkgtest integration mail with a few questions; should be able to start proposed-migration work after getting those answers.
[16:05] <cjwatson> Helped out with Upstart 1.6.1 release.
[16:05] <cjwatson> ..
[16:06] <ev> This is going to be a long one. Maybe go fetch yourself a nice hot kwahfee ☕
[16:06] <ev> Week of December 6th
[16:06] <ev> - Ubuntu Error Tracker sprint. Wrap up email forthcoming.
[16:06] <ev>   - Managed to get through most of the sprint agenda:
[16:06] <ev>     https://docs.google.com/a/canonical.com/document/d/1BWOIRdJvUueJa4cWV68UEY3nlmHgAVJY6aNGo6YSCQg/edit?pli=1#
[16:06] <ev>   - We came up with an implementation plan for stopping phased updates:
[16:06] <ev>     https://wiki.ubuntu.com/ErrorTracker/PhasedUpdates
[16:06] <ev>   - And server-side hooks. This will let you request that additional
[16:06] <ev>     information be sent for a package or problem (bucket ID) automatically, or
[16:06] <ev>     request that a user file a bug in Launchpad with a link back to the error
[16:06] <ev>     tracker, so that you have someone to converse with:
[16:06] <ev>     https://wiki.ubuntu.com/ErrorTracker/ServerSideHooks
[16:06] <ev>   - Thanks to Martin, we now have end-to-end system tests up and running on
[16:06] <ev>     canonistack \o/:
[16:06] <ev>     https://wiki.ubuntu.com/ErrorTracker/Deployment
[16:06] <ev>   - Did code review for Brian and Martin, and countless pastebin discussions
[16:06] <ev>     over IRC.
[16:06] <ev>     - We're going to be setting up Tarmac on canonistack to drive the end to
[16:06] <ev>       end system testing on each new merge proposal. This is blocked on us
[16:06] <ev>       getting canonistack credentials for the Tarmac instance, so that it can
[16:06] <ev>       drive juju to spin up the nodes for testing (RT 57881).
[16:06] <ev>   - We also did some pair programming (crowded around my laptop - damn you
[16:06] <ev>     tmux) to create a mapping between bugs and crash signatures:
[16:06] <ev>     lp:~ev/errors/bug-to-crash-signature
[16:06] <ev>   - We're moving the retracers to prodstack (RT 58019) after doing some
[16:06] <ev>     investigations around a copy on write backend using LVM or overlayfs. This
[16:06] <ev>     will fix the disk space problems we've been encountering, according to
[16:06] <ev>     James.
[16:06] <ev>   - Worked on improving error handling around open ID logins. I've also
[16:06] <ev>     restricted access to the full stack traces to just
[16:06] <ev>     ~canonical-ubuntu-engineering, per James' request (bug 1087361). In a later
[16:06] <ev>     change, which I'm working on, we'll provide sanitised stack traces and
[16:06] <ev>     instance pages for anyone in ~ubuntu-bugcontrol to view.
[16:07] <ev>   - Worked through the implementation plan for a view of all the errors that
[16:07] <ev>     your team is responsible for with Brian.
[16:07] <ev>   - Came up with a plan to handle statistical noise from more developers using
[16:07] <ev>     a particular error type or a bug fix causing more reports of a particular
[16:07] <ev>     error type.
[16:07] <ev>   - Worked with Ivanka to come up with more friendly messaging and started to
[16:07] <ev>     build a persona for communicating errors to the user (think of the Google
[16:07] <ev>     Chrome robot).
[16:07] <ev>   - Call with Rick to fill him in on the sprint's progress.
[16:07] <ev>   - Came up with a plan for receiving crashes from unpackaged software (like
[16:07] <ev>     Steam games).
[16:07] <ev>   - Came up with a plan to clean up the chain of bug duplicates as it relates
[16:07] <ev>     to errors.ubuntu.com (this will provide steady footing for the 'prompting
[16:07] <ev>     for software updates for the crashes they fix' functionality):
[16:07] <ev>     https://bugs.launchpad.net/errors/+bug/1086754
[16:07] <ev>   - We decided there's no programmatic way of untangling errors from libraries
[16:07] <ev>     and the applications that consume them, but will surface likely library
[16:07] <ev>     issues using map/reduce jobs:
[16:07] <ev>     https://bugs.launchpad.net/errors/+bug/1072854
[16:07] <ev>   - Talked through the security implications of allowing users to see their
[16:07] <ev>     crashes given just the system UUID. We could technically blacklist any IP
[16:07] <ev>     with multiple 404s against the system page (brute force SHA512 guessing),
[16:07] <ev>     but we'll likely just let users see a table of basic information about each
[16:07] <ev>     crash. Providing further access would imply also letting them delete the
[16:07] <ev>     data, which has the same trust problem of not absolutely knowing the person
[16:07] <ev>     viewing the data is the owner.
[16:07] <ev>   - Came up with a really nice solution with James (RT 55518) for providing a
[16:07] <ev>     secondary/analytics cluster and a development cluster using sstableloader
[16:07] <ev>     and single beefy machines to represent each additional cluster. This
[16:07] <ev>     creates one directional pipes of the data from the core Cassandra cluster
[16:07] <ev>     to each additional cluster. So it means we cannot use the analytics cluster
[16:07] <ev>     to do back population. We'll therefore still install Hadoop on the core
[16:07] <ev>     cluster as well, and just use it for the back population map/reduce jobs
[16:07] <ev>     (putting all other M/R jobs on the analytics cluster).
[16:08] <ev>   - We came up with several actionable items for getting more teams using
[16:08] <ev>     errors.ubuntu.com. If you have any ideas on this, do let me know! I really
[16:08] <ev>     want to ensure everyone has at least considered making it part of their
[16:08] <ev>     daily routine and know what the blockers are to people using it more.
[16:08] <ev> - Attended a Cassandra London meetup on moving from MongoDB to Cassandra.
[16:08] <ev>   - Full report forthcoming, but here are my notes (there may also be a video
[16:08] <ev>     at some point):
[16:08] <ev>     http://paste.ubuntu.com/1427650/
[16:08] <ev>   - Met a few guys from Meta Broadcast after their talk. They seem well suited
[16:08] <ev>     for juju, so I've sent them along to Jorge. They also want to work with us
[16:08] <ev>     on bringing multimedia to the dash and TV, so I set up their CEO with John
[16:08] <ev>     L.
[16:08] <ev>   - From talking to some other Hadoop users at the meetup, I learned that the
[16:08] <ev>     released version of Pig has a number of thorny issues that can be avoided
[16:08] <ev>     by building from trunk.
[16:08] <ev>   - No one has a better idea of how to recreate a Column Family with the
[16:08] <ev>     correct comparators other than just pointing all requests at both the old
[16:08] <ev>     and the new CF while siphoning off data from the old into the new as a
[16:08] <ev>     background task.
[16:08] <ev> - Started fleshing out tasks to complete at the end and beginning of each
[16:08] <ev>   release:
[16:08] <ev>   https://wiki.ubuntu.com/ErrorTracker/UbuntuReleasePreparation
[16:08] <ev> - Chased down getting http://graphite.engineering.ubuntu.com up and running,
[16:08] <ev>   which is now is! Filed RT 57837 for a graph of column family sizes, per
[16:08] <ev>   James' request. Filed RT 58016 for getting a statsd instances feeding
[16:08] <ev>   Cassandra timeouts and errors.ubuntu.com access data into graphite.
[16:08] <ev> - Moved packages from my personal PPA to the new daisy-pluckers daisy-seeds
[16:08] <ev>   PPA, pulling in changes from raring where possible.
[16:08] <ev> - Tested and pushed out a new pycassa to the retracers. This will hopefully
[16:08] <ev>   help us understand why we're seeing only a single retry on Cassandra
[16:08] <ev>   connection attempts when we have it explicitly set to 5.
[16:08] <ev> - Countless other things. It's been a very busy two weeks and I'm still trying
[16:08] <ev>   to get everything codified on the wiki, in bugs, in RT tickets, and in a big
[16:09] <ev>   writeup of all the progress we've made. The sprint was one of the most
[16:09] <ev>   productive weeks of my time at Canonical and I was elated to hear that Rick
[16:09] <ev>   made a point of keeping money in the budget for small-group sprints in 2013.
[16:09] <ev>   A massive thanks to Steve, Rick, and Pete for approving this and Brian,
[16:09] <ev>   Martin, Dmitrijs, Ivanka, and James for lending their time.
[16:09] <ev> done \o/
[16:09] <stgraber>  - Upstart
[16:09] <stgraber>   - Some cleanup of the prctl branch, sent an e-mail to upstart-devel and ted about it, waiting for final review.
[16:09] <stgraber>   - Dug into the libnih dbus code generator and fixed the 'as' type issue, sent MP, reviewd and accepted by James, still needs uploading.
[16:09] <stgraber>   - Merged gdbus port of the dconf bridge, cleaned up the code a bit after that.
[16:09] <stgraber>  - Container
[16:09] <stgraber>   - Quite a lot of code review for patches being sent upstream.
[16:09] <stgraber>   - Did a lot of code cleanup, dropped any hardcoded path in the code, using autoconf everywhere.
[16:09] <stgraber>   - Updated the upstream documentation for the new contribution workflow.
[16:09] <stgraber>   - Improved locking in lxc-create to allow for concurent creation of containers using different templates.
[16:10] <stgraber>   - Update python bindings for the new set/get_cgroup_item API, rebased some of the code on the new API.
[16:10] <stgraber>   - Discussed the release plan upstream and sent the 0.9~alpha1 pull request to Daniel.
[16:10] <stgraber>   - Finished porting arkose to python3, released 1.6 and uploaded to the archive.
[16:10] <stgraber>  - Release
[16:10] <stgraber>   - Released alpha-1 for Edubuntu and Kubuntu.
[16:10] <stgraber>   - Fixed a few bugs in the QA Tracker related to images auto-publishing based on manifest.
[16:10] <stgraber>   - Extended the manifest in the tracker to support an active/disabled flag so entries can remain on the manifest even when not planned for release in the current milestone.
[16:10] <stgraber>  - Networking
[16:10] <stgraber>   - Wrote patch to make bridge-utils work with any init system (well, at least sysvinit and upstart)
[16:10] <stgraber>   - Uploaded a new ifenslave-2.6 fixing all the remaining bugs on Launchpad.
[16:10] <stgraber>   - Uploaded a new ifupdown fixing a bunch of bugs in ifupdown and the upstart jobs, changes forwarded to Debian.
[16:10] <stgraber>   - Went through bridge-utils and vlan bugs.
[16:10] <stgraber>   - Reviewed redhat's fiberchannel patchset for isc-dhcp, will need quite a lot of changes to apply.
[16:10] <stgraber>  - Other
[16:10] <stgraber>   - Did some more precise UEFI secureboot testing for Colin, it actually works now!
[16:10] <stgraber>  - TODO
[16:10] <stgraber>   - Upload new libnih.
[16:10] <stgraber>   - Add test for Restarted event to the dbus-events upstart branch and propose for merging.
[16:10] <stgraber>   - Go through the isc-dhcp and resolvconf bugs.
[16:10] <stgraber>   - Try to apply redhat's fiberchannel patchset to our isc-dhcp.
[16:10] <stgraber>   - Figure out how to build the shim locally and sign it with a local key, then work with slangasek to figure out what's the exact bug I'm having.
[16:11] <stgraber>  - Travel/Sprint/...
[16:11] <stgraber>   - I'll have a slightly weird work schedule on Friday as I'll be traveling to Montreal, will still be working as usual and be available on IRC.
[16:11] <stgraber>   - I'm arriving in Europe on Saturday (15th) and will be back in Canada on the 2nd of January.
[16:11] <stgraber>   - Monday through Wednesday next week, we'll have an upstart sprint on European time.
[16:11] <stgraber>   - Thursday I'll be working as usual but on European time.
[16:11] <stgraber>   - Then I'll be off from Friday (21st) until I'm back in Canada on the 2nd of January.
[16:11] <stgraber>   - So if you need anything non-upstart related from me this year, make sure to talk to me this week or Thursday next week.
[16:11] <stgraber> (DONE)
[16:12] <slangasek> ev: why are we damning tmux?
[16:12] <ev> slangasek: because setting up multiuser tmux was eating up way too much time
[16:12] <slangasek> ev: ah, so tmux isn't actually better than screen :)
[16:12] <ev> slangasek: it has a real fun time trying to negotiate the screen size
[16:12] <xnox> slangasek: and /me killing the group session by accident did not help either.
[16:12] <ev> slangasek: if anyone exits tmux, EVERYONE DIES
[16:12] <slangasek> ev: +1 on retracers moving to prodstack - very cool
[16:12] <ev> slangasek: yup! We're moving the whole stack minus cassandra, actually
[16:13] <ev> just talked through it with Tom
[16:13] <xnox> * Fix UTAH ISO smoke testing:
[16:13] <xnox>   - correct bind mounts for DHCP (bug 1061242)
[16:13] <xnox>   - re-enable wubi test (lp:~xnox/utah/wubi-still-exists)
[16:13] <xnox>   - pep8 fixes (lp:~xnox/utah/new-pep8)
[16:13] <xnox> * Requesting separate & more comprehensive static ISO image validation
[16:13] <xnox>   in UTAH without blocking other tests (bug 1088444)
[16:13] <xnox> * Fix racy upstart test for dep8, but a different one failed in
[16:13] <xnox>   jenkins =( (bug 1089159)
[16:13] <xnox> * Upload new procenv and identify cause for upstart test suite failure
[16:14] <xnox>   in debian on amd64/xfs
[16:14] <xnox> * Fix above with a libnih merge proposal (bug 672643)
[16:14] <xnox> * Verify ubiquity SRUs (bug 792652) (bug 887879) (bug 1027648)
[16:14] <xnox>   (bug 1055967) (bug 1070427)
[16:14] <xnox> * Add quantal/raring to manpages.ubuntu.com and file RT#57985 for
[16:14] <xnox>   deployment
[16:14] <xnox> * Made merge proposal to avoid partman hanging in the reuse/replace
[16:14] <xnox>   recipes. (bug 1085991)
[16:14] <xnox> * Upstart continuing to add support in upstart to parse and load
[16:14] <xnox>   config sources for user sessions.
[16:14] <xnox> done.
[16:16] <xnox> ogra is off, doko?
[16:16] <doko> - getting gcc-4.7 cross built (just needed two upstream fixes)
[16:16] <doko> - trying to understand cross build setups
[16:16] <doko> - modifying the armhf cross compiler to install into a different location than t
[16:16] <doko> he armhf native compiler
[16:16] <doko> - more gcc-4.7 packaging changes, fallout from the libxxx-4.7-dev splits, that s
[16:16] <doko> hould be all for now
[16:16] <doko> - moving the gcc-4.7 changes to gcc-4.8
[16:16] <doko> - python m-a same/allowed changes
[16:16] <doko> - gcc-linaro merge
[16:16] <doko> (done)
[16:22] <slangasek>  * Processing SRU backlog for precise; the X backport stack is now in
[16:22] <slangasek>  * Ongoing discussions about the UEFI Samsung bricking bug.  Possibly an issue with the samsung-laptop module.
[16:22] <slangasek>  * Helped get upstart 1.6.1 ready for raring
[16:22] <slangasek>  * TODO:
[16:22] <slangasek>   * updating shim for: MOK support, fixing noisiness on boot, trying to debug stgraber's unsigned kernel boot bug
[16:22] <slangasek>   * looking at getting edk2 (ovmf) packaged for raring
[16:23] <slangasek> (done)
[16:23] <stgraber> slangasek: do you already have a branch of the new shim that I could build+sign here and try to boot?
[16:23] <slangasek> stgraber: no, will try to do that today
[16:23] <bdmurray> crashdb sprint (lots of discussions there)
[16:23] <bdmurray> wrote pycassa code to query cassandra crashdb over an ssh tunnel
[16:23] <bdmurray> pushed new version of whoopsie fixing bug 1084311
[16:23] <bdmurray> worked on fixing bug 1078801 and sorting of package versions on buckets page
[16:23] <bdmurray> updated bug 1088587 (apport/errors) with research
[16:23] <bdmurray> reported and fixed bug 1089083 regarding version ordering on buckets page of errors
[16:24] <bdmurray> pushed errors branch fixing html title on buckets page - bug 1086796
[16:24] <bdmurray> pushed daisy branch fixing UnicodeEncodeError regarding DupeSig
[16:24] <bdmurray> pushed errors branch to view bucketids with unicode in them
[16:24] <bdmurray> tested a new rollout of errors and daisy with thedac
[16:24] <bdmurray> updated bug bot on cranberry to comment on ubiquity bug reports
[16:24] <bdmurray> discovered an issue with the SRU for bug 1084296
[16:24] <bdmurray> SRU verification of bug 1084296 and bug 1084996
[16:24] <bdmurray> SRU verification of bug 1048059
[16:24] <bdmurray> with slangasek clean-up of the old unverified SRUs
[16:24] <bdmurray> merging and testing fix for bug 1071388
[16:24] <ev> ow, my highlight
[16:24] <bdmurray> ⁂ done⁂
[16:25] <slangasek> any questions over the above?
[16:26] <xnox> bdmurray: what did ubiquity bug commenter bot learned to do?
[16:27] <bdmurray> xnox: set crashes to high, tag bugs with the release and ubiquity version, mark hardware errors as invalid, tell oneiric installers to try precise
[16:27] <bdmurray> xnox: probably some more stuff too
[16:27] <bdmurray> xnox: it had be accidentally disabled for a bit :-(
[16:28] <slangasek> [TOPIC] Bugs
[16:28] <xnox> bdmurray: i see. thanks.
[16:29] <slangasek> bdmurray: any bugs we should be worrying about?
[16:29] <bdmurray> xnox: we can talk about it more later if you'd like
[16:30] <bdmurray> slangasek: not specifically however generally where does bug 1087630 belong?
[16:30] <infinity> ubuntu-meta, but assigned to the server team.
[16:30] <slangasek> bdmurray: right, what infinity said
[16:30] <bdmurray> okay, thanks
[16:30] <bdmurray> it actually looks like an issue with the qa team setup from what I can tell
[16:31] <xnox> bdmurray: and I think jamespage was looking into that. E.g. the testing framework makes the minimal install bloated, not the installation itself.
[16:31] <bdmurray> this is interesting but I'll dig into it
[16:31] <bdmurray> https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fsoftware-properties-gtk%3ASystemError%3A%3Cmodule%3E%3A__init__%3A__init__%3Aopen
[16:32]  * xnox ponders if d-i can report total used space after tasksel but before late-commands.... or somehow subtract testing overlay size.
[16:34] <slangasek> bdmurray: interesting indeed; I've got nothing, will leave you to dig into it :)
[16:34] <slangasek> anything else?
[16:34] <bdmurray> the Problem with MergeList issue shouldn't happen in 12.10 iirc
[16:35] <slangasek> well, this one looks at least superficially different from the ones we had before
[16:35] <slangasek> claiming that a record in the file is invalid
[16:36] <xnox> en%5fUS is interesting ending of the filename. why is it processing translations?
[16:36] <infinity> That's just straight up stream/file corruption, isn't it?
[16:37] <infinity> Not that apt/libapt/python-apt shouldn't deal with that tons better than it currently does, but...
[16:37] <slangasek> xnox: because the translations should also be merged into the database that you see with 'apt-cache show' etc?
[16:37] <slangasek> infinity: it's a bit surprising for that to happen so frequently with that one URL
[16:37] <slangasek> er, assuming it's all that one url
[16:37] <xnox> slangasek: and I don't see any en_US translations present for quantal multiverse here http://archive.ubuntu.com/ubuntu/dists/quantal/multiverse/i18n/
[16:38] <infinity> Oh, indeed.
[16:38] <infinity> Those signatures aren't all the same at all.
[16:38] <infinity> https://errors.ubuntu.com/oops/013c3eee-3284-11e2-b1c9-2c768aafd08c
[16:39] <infinity> It's just taking the traceback, not the error.
[16:39] <slangasek> ok
[16:39] <slangasek> anyway, let's not try to dissect this here
[16:40] <slangasek> take it to #ubuntu-devel afterwards if you want to kibitz bdmurray's investigation ;)
[16:40] <slangasek> bdmurray: any other bugs?
[16:41] <bdmurray> slangasek: nope
[16:41] <slangasek> ok, cool
[16:41] <slangasek> thanks
[16:41] <xnox> ev: mis-bucketing ^^^^^ stuff is bucketed by traceback instead of error message.
[16:41] <slangasek> [TOPIC] AOB
[16:42] <slangasek> anything else?
[16:42] <infinity> So, in the AOB realm for me, my last day of the year is today.  I'll be "around" here and there, if someone needs me for Ubuntuy or Debiany things, but don't expect responses before Jan 02.
[16:43] <xnox> infinity: so with you & ogra gone #ubuntu-arm will be almost unresponsive =))))
[16:43] <slangasek> well, I guess the rest of us will have to pitch in there :)
[16:44] <slangasek> #endmeeting
[16:44] <meetingology> Meeting ended Wed Dec 12 16:44:20 2012 UTC.
[16:44] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-12-16.02.moin.txt
[16:44] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-12-16.02.html
[16:44] <slangasek> thanks everyone!
[16:44] <xnox> cheers.
[16:44] <infinity> \o
[16:48] <stgraber> thanks!
[18:39] <zakuan> hello


[00:26] <aboSamoor> I was using google code,for my personal code. Some homeworks and shared work. but it seems that my account in google code is having a bug. I am asking if it is legal to use launchpad for such thing ?
[00:26] <mthaddon> aboSamoor, does your code use one of the approved open source licenses?
[00:27] <aboSamoor> mthaddon, it was under GPLv3 in code.google
[00:27] <mthaddon> aboSamoor, in that case, absolutely
[00:29] <aboSamoor> mthaddon, I want to be sure that I am not violating any policy. Because collabnet hosting has a policy to support only large and not personal code
[00:30] <mthaddon> aboSamoor, I don't believe there's any such distinction in Launchpad - that said, it's designed for project based setup, so if you have lots of different bits that you want to have in different source trees, it might not work quite as nicely as it could
[00:30] <lifeless> aboSamoor: we like users
[00:30] <aboSamoor> mthaddon, any idea about how to start ?
[00:31] <mthaddon> aboSamoor, https://launchpad.net/+tour
[00:32] <aboSamoor> Is there a possibility to transfer my code from svn to bzr ?
[00:33] <mthaddon> aboSamoor, absolutely - there's a bzr-svn plugin that will help
[00:33] <mthaddon> http://bazaar-vcs.org/BzrForeignBranches/Subversion
[00:33] <persia> aboSamoor, Unless you have a special reason to do otherwise, I'd recommend putting that sort of thing in a personal +junk project on an launchpad account, rather than creating a project.
[00:34] <persia> Once something grows large enough to need bug tracking, collaboration, etc. then it might make sense to have a project.
[00:34] <lifeless> aboSamoor: the same conditions for hosting apply, but it doesn't show as a formal project
[00:35] <aboSamoor> persia, Yes this is better for me. I don't want a project just code hosting is enough. However, what do you mean by personal + junk ?
[00:36] <aboSamoor> persia, I already have launchpad account
[00:36] <persia> You can push bzr branches to the special +junk project, which shows them in your personal branch list, but doesn't associate them with any project.  There's surely some docs at help.launchpad.net about it.
[00:38] <lifeless> aboSamoor: e.g. lp:~aboSammor/+junk/study
[00:38] <aboSamoor> persia, lifeless, I found this https://help.launchpad.net/Code/PersonalBranches
[00:39] <persia> That's precisely it.
[01:00] <aboSamoor> while I am trying to add svn folders to bzr using 'bzr add', I got this message "bzr: ERROR: Permission denied: ".": PROPFIND request failed on '/svn/trunk'"
[01:02] <aboSamoor> should I have to delete .svn folders or use a different command to make my first commit to bzr branch ?
[01:03] <persia> You probably don't want .svn to be .bzr managed.
[01:03] <lifeless> persia: you're confused :P
[01:03] <persia> #bzr might be a better resource to understand how to migrate (although a number of those people are here)
[01:03] <lifeless> aboSamoor: bzr is trying to talk to your svn server
[01:03] <persia> lifeless, Always.
[01:03] <lifeless> aboSamoor: because bzr supports svn
[01:04] <lifeless> aboSamoor: but google code's svn servers are not full svn servers
[01:04] <lifeless> aboSamoor: two suggestions:
[01:04] <lifeless> 1) use bzr branch svn://code.google.com/<whatever> my-bzr-branch
[01:05] <lifeless> 2) use svn export to export your tree, then add it to bzr
[01:05] <lifeless> choose one of these:)
[01:05] <wgrant> There's no easy way to use cscvs oneself, is there?
[01:05] <lifeless> fsvo easy
[01:12] <aboSamoor> is there anyway to replace my accounts in ubuntu forums, brainstorm.ubuntu by launchpad openID ?
[01:13] <persia> Not currently.  brainstorm will probably happen before the forums.
[01:41] <aboSamoor> lifeless, I got this description in my new branch  	Repository format: Packs containing knits without subtree support
[01:42] <aboSamoor> is there any problem ?
[01:42] <maco> using https://bugs.edge.launchpad.net/ubuntu/+source/hal/+filebug i can't file a bug.  the "continue" button doesn't do anything.  anyone else noticed that?
[01:47] <aboSamoor> I think I made it correctly. lifeless, persia, mthaddon I appreciate your help. Thank you very much
[01:52] <wgrant> maco: Works for me. Does it not even reload the page?
[02:47] <lifeless> abentley: thats fine
[02:47] <lifeless> abentley: sorry, wrong nick
[08:21] <Aron_> I wonder how to use ppa on lanchpad,could someone help me?
[08:26] <Aron_> ziroday: here I am
[10:37] <Hobbsee> Aron_: would help if you asked a question, though
[10:37] <Aron_> I want to know how to use launchpad ppa
[10:38] <Aron_> I have created a ppa in my account on the web page
[10:58] <Hobbsee> !ppa
[10:58] <Hobbsee> Aron_: did you see ^
[10:58] <Aron_> sorry,leaved just now and back here
[11:02] <Aron_> Hobbsee: I have read it before
[11:02] <Aron_> but still something fuzzy
[11:04] <Aron_> Hobbsee: should I put the files in a particular directory?
[11:04] <Hobbsee> Aron_: which files?
[11:04] <Aron_> .changes,.dsc,.diff.gz and orig.tar.gz
[11:05] <Hobbsee> all except the last will get generated for you, from your directory with the source in it
[11:05] <Hobbsee> the .orig.tar.gz should be in the directory above the unpacked source
[11:05] <Hobbsee> apart from that, it doesn't matter.
[11:05] <Hobbsee> (the others will appear in the directory above the unpacked source)
[11:29] <Aron_> Hobbsee: got it ,big thanks to you
[11:30] <Hobbsee> Aron_: you're welcome!
[14:36] <joumetal> Would it be nice to remove obsolete tags from launchpad. For example edgyeft tag is not very useful anymore.
[15:11] <cody-somerville> If I was to add support to dput to have a special URI for PPAs, would folks prefer lp:<ppa-id> or ppa:<ppa-id>?
[16:36] <andrea-bs> Can non-team members post to mailing lists?
[18:06] <BoomShaka> Hi, can someone explain where i upload my SSH key in launchpad?
[18:07] <BoomShaka> nvm, found it :)
[18:11] <BoomShaka> arrgh. it keeps telling me i am using an invalid public key...
[18:11] <BoomShaka> anyone know what could be wrong?
[18:19] <LarstiQ> BoomShaka: formatting?
[18:30] <BoomShaka> LarstiQ, no worries, I figured it out. thanks
[18:44] <jfcgauss_> how do i add packages to my PPA? how do i set my PPA (for instance i want to target hardy but i see
[18:44] <jfcgauss_> apt sources.list entries:
[18:44] <jfcgauss_> deb http://ppa.launchpad.net/jfcgauss/ubuntu jaunty main
[18:44] <jfcgauss_> under my PPA.
[19:43] <Peng_> No 300,000 bug sweepstakes? :(
[19:44] <LarstiQ> Peng_: you already claimed it? :)
[20:13] <Andre_Gondim> how can i send e-mail in launchpad, always i don't have permision
[20:25] <Ursinha> Andre_Gondim, what do you mean?
[20:26] <Andre_Gondim> Ursinha, mandar mail para uma pessoa que tem o mail como escondido no launchpad
[20:26] <Ursinha> Andre_Gondim, deixa ver se é um bug
[20:27] <Andre_Gondim> Ursinha, tá
[20:27] <Andre_Gondim> Ursinha, quer exemplo?
[20:27] <Ursinha> manda
[20:27] <Andre_Gondim> Ursinha, preciso entrar em contato com https://edge.launchpad.net/~smoking-dog/+contactuser
[20:31] <Ursinha> Andre_Gondim, achei
[20:31] <Ursinha> bug 286410
[20:31]  * Ursinha hugs ubottu
[20:31] <Ursinha> Andre_Gondim, está sendo corrigido
[20:32] <Andre_Gondim> Ursinha, tá, é que eu preciso muito disso, pois tem muita gente que tá com maiil escondido e eu preciso contactar para melhorar as traduções ;)
[20:32] <Andre_Gondim> Ursinha, valeu
[20:32] <Ursinha> Andre_Gondim, beleza, faz um comentário no bug lá
[20:32] <Andre_Gondim> Ursinha, blz
[22:54] <javaJake> Is there any way to add someone to my personal repository without requesting a group?
[23:04] <intellectronica> javaJake: no, you'll have to use a team if you want to collaborate on repositories
[23:04] <javaJake> intellectronica: OK. :(
[23:04] <intellectronica> javaJake: why is that a problem?
[23:05] <javaJake> Well, I have to wait for two days to get it set up.
[23:05] <intellectronica> javaJake: oh, you mean a ppa?
[23:06] <javaJake> No, a repository with a team
[23:06] <intellectronica> javaJake: a bzr repository?
[23:06] <javaJake> https://code.launchpad.net/~fun2program8/+junk/gentoo-arm-pandora <-- I'm using it to collaborate with others on this project.
[23:06] <javaJake> intellectronica: yes
[23:06] <javaJake> But I don't know if it'll be permanent
[23:06] <javaJake> And so I'd rather not make a "mess" on Launchpad.
[23:07] <intellectronica> javaJake: so why do you have to wait two days? you can go ahead and create a team
[23:07] <javaJake> How!? o0
[23:07] <javaJake> I thought an administrator had to do it?
[23:08] <javaJake> I'd rather not bother them for such a trifle.
[23:10] <intellectronica> javaJake: https://edge.launchpad.net/people/+newteam
[23:10] <javaJake> intellectronica: nice! That's unbelievably conveniant
[23:10] <intellectronica> javaJake: i think that you're yet another victim of bug #102361 :-/
[23:11] <javaJake> intellectronica: hehehe
[23:11] <intellectronica> javaJake: why don't you go and mark yourself as affected by this bug ;)
[23:11] <javaJake> Good idea :D


[08:08] <luna> new podcast later today?
[11:57] <amurray> luna: hey - podcast just went live :)
[11:59] <luna> amurray: thanks will listen when helping with some 23.04 Alpha testing then :)
[12:03] <luna> and doing QA of my Swedish for ubuntu-desktop-installer
[15:55] <Guest6198700> Hello, I am seeing only fixable CVEs (USNs) in the Ubuntu Oval data. Is it not including unfixable CVEs? Is there anywhere we can get unfixable CVEs except for the git lunchpad data? Thank you!
[16:28] <hank> this is also relevant to my interests
[17:13] <ebarretto> Guest6198700, hank USN OVAL data only contains data based on USN, which means CVEs we fixed. If you want a CVE based OVAL you can download, just alter the name file from 'usn' to 'cve', e.g.: com.ubuntu.bionic.cve.oval.xml.bz2. CVE OVAL will show you a lot of vulnerabilities as it has the entirety of CVEs that affect us and that might not been fixed yet or never will
[17:16] <Guest6198700> Thank you! That's very helpful!
[17:18] <hank> are the "never" advisories called out?
[17:19] <hank> that is to say, can I tell the difference between "unfixed" and "unplanned"
[17:20] <ebarretto> hank, probably not, some CVEs will continue to have a needs-triage until upstream decides to fix it, if upstream is dead, that CVE will continue living until the package is dropped from debian/ubuntu
[17:21] <ebarretto> or if we decide to ignore them all, then you won't see it anymore in OVAL
[17:23] <hank> so there's no way to tell that an in-support package is planned to be updated, but hasn't yet?
[17:35] <ebarretto> not in oval
[17:35] <ebarretto> you could try to get more info the cve pages
[17:36] <hank> is there a way to get that in a machine format that's not the git repo?
[17:38] <ebarretto> not that I know of, the page does provide a json for each cve, but then you will need to query a bunch of them
[17:38] <ebarretto> also tbh our git repo doesn't exactly show if it is planned or not
[17:40] <hank> alright


[00:06] <guiverc> thanks Eickmeyer
 @kc2bez thats Erich's fault.  his nextcloud is rejecting the embed.
 as stated in that error message
[00:37] <Eickmeyer> @teward001 The sane thing to do would've been to put the picture in the discord post itself.
 correct
 because then it goes on s3 storage
[00:37] <Eickmeyer> My nextcloud can't handle the embed.
 i know thats why i am blaming you :P
 not on my ability to fix non lubuntu infra xD
[00:38] <Eickmeyer> It was intended for one-time use and download, not for this. It's only a 10Mbps connection. 😂
 Honestly, let's blame wxl for failing to place the image instead of embedding it. 😁
 define large cause the upload limit is pretty large by default
 5 TB
 *shots fired*
 1.1MB in this case. 💀
 uhhh it doesn't show who sent that?
[03:20] <Eickmeyer> *confused noises*
[03:22] <Eickmeyer> I can definitively confirm it is 1,041KB. Definitely not 4MB or even bigger.
[03:22] <Eickmeyer> And that's full-size.
[03:26] <guiverc> i just modified wxl's post and added a smaller version  (lower quality & half-res)
[03:27] <Eickmeyer> I was just about to make a .jpg of it.
[03:29] <Eickmeyer> guiverc: If you wouldn't mind, modify it to remove the embed of mine and the link to my nextcloud share. The bandwidth usage will kill me.
[03:30] <guiverc> ack.
[03:30] <Eickmeyer> And, fwiw, I have no idea how that white line got there.
[03:32] <guiverc> done Eickmeyer (I did not hide the history though, so viewers can click post history & find it still)
[03:33] <Eickmeyer> guiverc: Right. I'm talking about the image he originally posted, which is an embedded version of the file on my site.
[03:33] <Eickmeyer> I mean, additionally.
[03:36] <guiverc> okay... sorry I misunderstood request... will fix
[03:38] <guiverc> post now only shows the one I shrank/compressed
[03:40] <guiverc> wxl, if you have any issues with ^, just ping/request, or edit it yourself as appropriate


[00:57] <GamersCorp> Hi there. I've been having an issue that I've been trying to troubleshoot for about nine hours now. I created a thread on Reddit with more information: http://www.reddit.com/r/techsupport/comments/1f1yew/booting_ubuntu_from_a_usb/
[02:05] <holstein> lol
[11:05] <alphabravo> hello
[11:06] <alphabravo> i had a doubt regarding wifi


[17:39] <mhall119> bobweaver: were you ever able to get Unity trunk compiling?
[17:40] <bobweaver> yup
[17:40] <mhall119> bobweaver: great
[17:41] <bobweaver> but I am spending more time fixing unity then I am making new code :/
[17:41] <mhall119> bobweaver: are you working form the unity trunk, or the branch of it I made for TV?
[17:41] <bobweaver> I am using the bzr lp:unity
[17:41] <bobweaver> on raring
[17:41] <mhall119> ok, I'm going to update the TV branch with the latest from there
[17:41] <bobweaver> ok
[17:42] <bobweaver> mhall119,  it was just that stagging has many different libs that I do not think are going to make it into main I could be wrong
[17:42] <bobweaver> mhall119,  you know of anyone to talk to about lightdm remote login ?
[17:42] <bobweaver> like how it works ?
[17:43] <mhall119> bobweaver: david barcth is heading that one up
[17:43] <mhall119> barth
[17:43] <bobweaver> thanks mhall119
[17:43] <mhall119> is there something you need to know about it?
[19:26] <bobweaver> bzr: ERROR: [Errno 28] No space left on device     :: time to clean house
[19:37] <mhall119> bobweaver: I hate it when that happens
[19:39] <bobweaver> rm all the stuff on desktop alone (old builds ect) got me 26 gigs back
[19:54] <bobweaver> ermm http://paste.ubuntu.com/1380291/
[19:56] <mhall119> bobweaver: hmm, maybe it's using /tmp/ while it creates the branch?
[19:57]  * mhall119 doesn't know what overflow fstype is
[20:02] <bobweaver> no deals for the wicked ;/ I am going to try a different branch and look at .bzr log
[22:10] <bobweaver> mhall119,  do you know where I can find all the properties for namespace unity and dash ?
[22:11] <bobweaver> like that api thingy that you where making ? maybe
[22:27] <mhall119> bobweaver: the API website?  that only worked with the GObject exported data
[22:28] <mhall119> bobweaver: but if that's what you need, the static version is here: http://developer.ubuntu.com/api/ubuntu-12.10/c/Unity-6.0.html
[22:39] <bobweaver> thanks
[22:48] <bobweaver> http://unity.ubuntu.com/nux/d7/dde/namespaceunity_1_1dash.html#a40054a3e5c131dca40af497fb872aecb   << that is 100% what I was looking for
[22:50] <mhall119> ah, nux


[14:30] <FIRDOUSBHAT[m]> Hi Guys, need a help for Lubuntu. I've Internet plan of 100 MBPS but I'm getting only few MBs of speed. please help.
 "Hi Guys, need a help for Lubuntu..." <- Hello, this is Ubuntu Studio support room, not Lubuntu.
[14:43] <MauroGaspari[m]> Having said that, usually ISP rate download speed in Megabits Mbps. 100Megabits = 12.5 MegaBytes. remove a bit of overhead and if you get between 10 and 12 MBytes per second you are in the correct speed range.
[15:43] <rgh> If you're on a laptop and on battrru, your wifi adapter might be in power save mode.
[15:43] <rgh> *battery


[06:06] <didrocks> good morning
[06:15] <duflu> Morning didrocks
[06:19] <didrocks> hey duflu
[06:19] <duflu> I made a great discovery yesterday. But so far am being met with skepticism and criticism. Maybe more people should test it: https://gitlab.gnome.org/GNOME/mutter/merge_requests/168
[06:20] <gitlab-bot> GNOME issue (Merge request) 168 in mutter "clutter: Remove input lag and cursor stutter [performance]" (comments: 4) [Opened]
[06:27] <seb128> good morning desktopers
[06:33] <didrocks> hey seb128
[06:35] <duflu> Morning seb128
[06:35] <seb128> hey didrocks, duflu
[06:35] <seb128> how are you today?
[06:36] <duflu> seb128, not great. Awake since 5am for some reason. You?
[06:37] <seb128> I'm good, up at 6:10 today but I don't feel too tired
[06:38] <seb128> it's somewhat nice, I already clear my emails backlog, dropped the kid to childcare, had coffee and it's only 8:30
[06:38] <duflu> seb128, yeah days like today I appreciate having time for pilates
[06:38] <duflu> and not just rushing to my desk
[06:39] <seb128> you do pilates in the morning?
[06:39] <duflu> seb128, only when I have time. Not often mid week any more
[06:39]  * seb128 is not a morning person, I've difficulties doing any sort of exercice in the first hour after I wake up
[06:39] <duflu> Stretching doesn't raise the heartrate
[06:40] <duflu> Unless you're in fear of over stretching
[06:44] <seb128> I've not really flexible, even less in the morning :p
[06:44] <seb128> like I would be able to touch my knee with my hand, maybe my ankle but not my foot
[06:46] <duflu> seb128, yeah I was the same a few years ago. Still not great only doing it once or twice a week. But daily seemed to cause more problems than it solved
[07:30] <oSoMoN> good morning desktoppers
[07:31] <oSoMoN> didrocks, can you add me to the team so that I can assign myself communitheme bugs? see https://github.com/ubuntu/communitheme/issues/350#issuecomment-406173316
[07:31] <gitlab-bot> ubuntu issue 350 in communitheme "libreoffice not opening properly on communitheme.snap" (comments: 18) [Snap, Closed]
[07:31] <oSoMoN> unless this is a restricted team for active contributors to the theme only
[07:33] <didrocks> oSoMoN: done!
[07:33] <didrocks> et salut ;)
[07:36] <duflu> Hi oSoMoN
[07:39] <Trevinho> morning
[07:39] <duflu> Hi Trevinho
[07:41] <didrocks> hey Trevinho
[07:42] <seb128> Trevinho, Buongiorno
[07:52] <oSoMoN> merci didrocks
[07:52] <didrocks> de rien ;)
[07:52] <oSoMoN> hey duflu, Trevinho, seb128
[07:52] <seb128> lut oSoMoN, en forme ?
[07:53] <seb128> (and brb, changing location)
[08:00] <Trevinho> seb128, didrocks Bonjour
[08:01] <Trevinho> Et oSoMoN
[08:01] <Trevinho> Hi duflu
[08:01] <Laney> vatz up
[08:02] <didrocks> hey Laney
[08:03] <duflu> Hi Laney
[08:03] <duflu> i tink datz all vatz up
[08:18] <seb128> hoi
[08:18] <seb128> I guess Laney arrived while I was moving, hey Laney :)
[08:18] <Laney> hey seb128 (didrocks & duflu)
[10:06] <didrocks> hum, new meson doesn't like the symlinks on g-i-s.desktop: https://launchpadlibrarian.net/379093344/buildlog_ubuntu-cosmic-amd64.ubuntu-settings_18.10_BUILDING.txt.gz
[10:11] <didrocks> confirming it's 0.47 introducing this regression
[10:23] <doko> could somebody look at https://launchpadlibrarian.net/379210467/buildlog_ubuntu-cosmic-i386.goffice_0.10.41-1_BUILDING.txt.gz ? blocks a few packages
[10:23] <Trevinho> Laney: ciao amico!
[10:24] <didrocks> https://github.com/mesonbuild/meson/issues/3914
[10:24] <gitlab-bot> mesonbuild issue 3914 in meson "Symlinks can't be copied by install_subdir() since 0.47.0" (comments: 0) [Open]
[10:24] <doko> same on debian
[10:26] <Trevinho> Laney: as for the upstream tags thing I was asking few days ago... I think csoriano might make a release for nautilus today... if he does, that would be a case where if I import the orig in ubuntu first (and then debian does), would cause some troubles, no? Well, in this case probably it's just better to ask you to merge my PR for the pristine-tar in debian and then going with ubuntu, but well... what would be better? :)
[10:26] <didrocks> ahah, the code has a "# FIXME: what about symlinks?"
[10:26] <didrocks> for meson
[10:26] <didrocks> yeah, "thx" ;)
[10:27] <Laney> Trevinho: just propose the upstream stuff to salsa
[10:27] <Trevinho> that's fine, I only need to have you around :)
[10:27] <Laney> one day you can get access there
[10:28] <Trevinho> if it involves bureaucracy probably not :-D
[10:28] <Laney> less than getting gnome commit rights
[10:29] <Laney> doko: not sure what that has to do with this channel?
[10:31] <Trevinho> Laney: for me that one was really easy... I said can I have push access? Done. :D
[10:31] <Laney> O_O
[10:31] <Laney> well then it's the same
[10:32] <Trevinho> good new point releases for mutter and shell ready...
[10:32]  * Trevinho prepares branches
[10:32] <Laney> these people skipping the process
[10:32] <Laney> RULES
[10:32] <Laney> I LOVE RULES
[10:33] <Trevinho> Cages you love cages!
[10:33] <Trevinho> I put rules, I don't respect them though... Classic italian way :-D
[10:34] <Laney> (ERROR: ERROR:../../../../../testsuite/gtk/defaultvalue.c:45:check_property: Property GtkFontChooserWidget.tweak-action: NULL != ((GSimpleAction*) 0x5619ca8c6800)
[10:34] <Laney> now what is this trying to tell me
[11:06]  * Laney finds the commit that fixes that
[11:28] <Trevinho> Laney: https://salsa.debian.org/gnome-team/mutter/merge_requests/3 and https://salsa.debian.org/gnome-team/gnome-shell/merge_requests/2
[11:28] <gitlab-bot> GNOME issue (Merge request) 3 in mutter "New upstream release 3.28.3" (comments: 0) [Opened]
[11:28] <gitlab-bot> GNOME issue (Merge request) 2 in gnome-shell "New upstream release 3.28.3" (comments: 0) [Opened]
[11:28] <Laney> yeah, it emails me
[11:28] <Laney> are you going to do the debian/master bits too?
[11:29] <Trevinho> since I was there... altough... I'm seeing something weird in the diffs :o
[11:31] <Trevinho> Laney: as updating pristine-tar only would involve passing an upstream/x.y.z tag or i could use the actual x.y.z tag from upstream only?
[11:33] <Trevinho> I mean gitlab shows also debian/* files which I didn't touch as changes, while local git diff salsa/debian/master doesnt
[11:35]  * Trevinho updates ubuntu too (time to create a branch for mutter ubuntu/bionic I guess, as I wanted that anyway)
[11:36] <Laney> what changes are needed there over cosmic?
[11:40] <Trevinho> Laney: nothing, but to track at least the changelog and stuff... And not to have to deal with debdiffs :-P
[11:40] <Trevinho> and we eventually we'll need one anyway, so...
[11:40] <Trevinho> technically we've already forked (as if just for changelog)
[11:45] <Trevinho> in any case, in this scenario without having g-s on salsa to have the upstream/foo tag udpating also ubuntu g-s would be problematic I guess, as if debian wouldn't want to update (for example) we'd ended up in redefining a new upstream/version tag which then debian will overwrite... If cases like this would happen (hypotetically now), wouldn't be just better to use a different upstream tagging option? (like upstream-ubuntu/version)
[11:45] <Laney> I'd rather we stop coming up with problems that don't exist yet
[11:49] <seb128> what's the issue? us updating before Debian?
[11:50] <seb128> there is no reason the pristine-tar/gnome content should be different even if we do update on our side and they do it later on their right? like merging should just work, and the tags are different since the versions are different?
[11:51] <Trevinho> seb128: yes, that case...
[11:51] <Trevinho> the upstream tags will be different
[11:52] <Laney> I can't be bothered to fight over these details every day
[11:52] <Laney> so I just go with whatever you propose
[11:52] <Trevinho> so when you import the origin, as per our gbp.conf we get upstream/x.y.z tag, while debian might have the same later
[11:52] <seb128> ah
[11:52] <seb128> what do you propose to do for those cases?
[11:52] <Trevinho> 😂 win for stressing :-D
[11:53] <Trevinho> Well, I though that in such cases we could change the debian/gbp.conf to use something like upstream-ubuntu/x.y.z tagging then, when we merge back get it back to upstream/foo
[11:54] <Trevinho> not that is a solution I like, but it's the only one that comes up to my mind not to have to have clashing tags
[11:54] <Trevinho> anyway Laney in this case just merge and I'm happy :-P
[11:55] <Trevinho> but there will be cases, I know, when we can't proceed this way
[11:56] <seb128> Trevinho, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931 has been fixed in g-s 3.28.3 if you want to list it in the changelog
[11:56] <Trevinho> seb128: yeah, also others thanks... but I've not prepared the g-s for ubuntu yet as I'm not sure if I can reuse the tag I just done for upstream until it gets merged to debian
[11:57] <Trevinho> (to merge with that)
[12:01] <seb128> k, well that discussion is a bit over me and I feel like it's a sensitive topic for Laney and I don't want to piss off anyone so I'm going to step out and let you guys deal with it
[12:01] <seb128> just "we can't update because Debian didn't update yet" isn't an answer, how we get the update I don't care about
[12:02] <seb128> either by doing ourself in Debian, doing it first and dealing with tags issues or whatever you guys prefer
[12:02] <Trevinho> I've not actually any strong opinion in how
[12:02] <Trevinho> I only want to know how...
[12:02] <seb128> just pick one and go with it then
[12:02] <seb128> seems nobody is going to tell you that
[12:03] <seb128> both Laney and I bailed out from replying to that question
[12:03] <Trevinho> eh, but I don't want to go back later, so I ask
[12:03] <seb128> so do what you think makes sense
[12:03] <Laney> what is the actual problem that happens rather than a theoretical concern?
[12:03] <seb128> and if someone disagrees with what you did we can discuss
[12:03] <seb128> Laney, from what I understood Trevinho thinks we are going to have the upstream/3.28.3 tag on a different commit than Debian
[12:04] <seb128> unsure if that's a problem?
[12:04] <Laney> I understand that
[12:04] <Laney> I don't understand what the real problem that happens as a result is
[12:04] <Trevinho> Well, now might not be the case, as I've prepared the branches
[12:04] <Laney> seems like guessing / assumption to me
[12:04] <seb128> I don't understand git enough
[12:04] <seb128> can the same tag be defined twice?
[12:04] <seb128> or can we diverge?
[12:04] <Laney> no, but does it even matter?
[12:04] <seb128> or what tags mean
[12:04] <Laney> you merge the commit into the packaging branch
[12:04] <Laney> then it has multiple parents
[12:04] <Trevinho> but.... imagine we want to switch to any package first than debian... as for some reaason they want to stick to older version
[12:04] <Laney> even if one of them isn't named as a tagged revision
[12:05] <Laney> so does it really actually matter if you don't have the tags at all?
[12:05] <Laney> I think this is guesswork and nobody has actually tried it to see what the problem is
[12:05] <seb128> k, as I said I don't understand git enough to understand what consequences a mismatch is the tagging has
[12:06] <Trevinho> I can merge with actual upstream branch and that's fine...
[12:06] <Laney> I'm happy to talk about *real* problems
[12:06] <seb128> but yeah, I'm fine ignoring the issue until it creates a problem in practice, then we can fix if needed
[12:06] <Laney> that have *actually* happened
[12:06] <Laney> but discussing abstract things, not so much
[12:06] <Trevinho> but the fact is that if you don't have the upstream-tag set, gbp complains no?
[12:06] <seb128> Trevinho, import-orig would tag upstream no?
[12:06] <Trevinho> Laney: I need you more philosopher :)
[12:07] <Trevinho> seb128: eh, yes... but we can't do that or that tag will be on debian too later.. .so
[12:07] <seb128> Laney, fine, but if we *know* that we are doing something stupid that is going to blow up we might as well discuss how to fix it before it bites us ... which from the backlog I now understand it doesn"t seem to be the case there and we don't know if it would create any problem
[12:07] <Trevinho> this is the case where instead of using import-orig, you actually git merge with origin / branch
[12:07] <seb128> so yeah, let's stop arguing and just do the work then
[12:07] <Laney> seb128: yes, so if you think there's a problem
[12:07] <Laney> then demonstrate that it exists
[12:08] <seb128> agreed
[12:08] <Trevinho> Laney: I think we already had a clashing tag issue...
[12:08] <seb128> Trevinho, ^ let's get the tag first and see what it leads to when debian does the update
[12:08] <seb128> Trevinho, what was the impact?
[12:08] <seb128> if that's "none visible" let's not care?
[12:08] <Laney> you still have a reference to the commit, even if you don't have the tag by name
[12:09] <Laney> so the problem would only be if gbp is trying to use it by name and it ends up being different and that breaks
[12:09] <Trevinho> yeah, that's fine... but we'll have 2 new upstream release tag.. and at that point we've to --delete our tag, and keep debian?
[12:09] <seb128> or we don't care
[12:09] <seb128> that tag exists twice
[12:09] <seb128> and?
[12:09] <Trevinho> in our repo will be different than salsa
[12:09] <seb128> and?
[12:09] <Trevinho> or we just at that point --force push the new tag
[12:09] <Trevinho> to point to debian
[12:10] <Laney> if that happens we'll have a diverged upstream branch anyway
[12:11] <Trevinho> that's ok, nothing really hurting to me, but since I thought we didn't want to play with force or anything, I thought it was just saner to use our upstream tagging if we do upstream code before or different from debian, and then go back when we merge again
[12:11] <Laney> what I really want to avoid is making this thing really complicated
[12:12] <Laney> so I'm pushing back against adding more weird steps
[12:12] <Laney> now if something breaks, fine, we can't avoid it
[12:12] <Laney> but if it's no problem in reality then I would rather not make it harder
[12:12] <Trevinho> I see the point, I just expect that simplifying this could make things harder to fix
[12:13] <Trevinho> but I like to think in advance
[12:13] <Laney> that's fine
[12:13] <Trevinho> (only in computer stuff, not really in life :D)
[12:13] <Laney> but you can go experiment if you want to and find out what actually happens
[12:14] <Laney> go gbp import something in two repositories and play with merging between them
[12:14] <Trevinho> Laney: if would be possible to only push the upstream/{latest,foo} branches in salsa in case, is just enough though
[12:14] <Trevinho> as they will anyway need those
[12:14] <Laney> it is fine
[12:14] <Laney> it's always fine to push upstream and pristine-tar
[12:14] <Trevinho> and then they just merge when needed instead of using import-orig
[12:14] <Laney> those are objective things
[12:15] <Trevinho> ok, so let's define this rule... Propose any changes to `upstream/xxxx` branches and to `pristine-tar` always mandatory to be proposed to salsa too
[12:15] <Trevinho> not sure it simplifies (for who has no salsa write access) but at least, does the job
[12:16] <Trevinho> speaking of which Laney please pull there my ones for mutter and shell 💋
[12:16] <Trevinho> (debian/master are done too, but... I can wait)
[12:16] <Laney> I will, don't stress
[12:17] <Laney> trying to get a build of gtk 3.23
[12:18] <seb128> Trevinho, the less work is to do the update in Debian and just sync/merge from them, that systems is working for Laney's goal to have us doing the work there :)
[12:18] <Trevinho> ahaha, yeah... :)
[12:18] <Laney> 😎
[12:18] <Trevinho> well, that's fine for me, and I agree in doing it. Well `debian/master` is another thing, so not sure I'll always do that :-D
[12:19] <seb128> I'm fine doing the work in Debian, I'm unsure how I feel about pushing/uploading things without testing them on the target distro though
[12:19] <seb128> but I guess we can push without the tagging/upload that's most of the work
[12:19] <Trevinho> well, if you only push upstream and pristine-tar branches you don't affect them
[12:19] <seb128> right
[12:19] <Trevinho> and that's safe
[12:19] <seb128> but I mean for quite some package we have no diff
[12:19] <seb128> so it would make sense to update in Debian and direct sync
[12:19] <Trevinho> ah, sure
[12:20] <Trevinho> like we do for mutter right now
[12:20] <seb128> but then do you test that build on cosmic and assume it's working on Debian?
[12:20] <seb128> I don't like much assuming it's fine
[12:20] <Trevinho> ah, indeed
[12:20] <Laney> no I run the things
[12:20] <seb128> but I don't have enough installs to be using Debian
[12:20] <seb128> already having Ubuntu current, current stable, LTS
[12:20] <Trevinho> yeah, it's quite a lot of chroots
[12:20] <seb128> you can fire a VM and do a "log in, it works, ship"
[12:20] <seb128> it's a bit of work and not proper testing though
[12:21] <Laney> what do you do for testing for cosmic?
[12:21] <seb128> I usually boot the version of Ubuntu I'm currently working on
[12:21] <Trevinho> it's fine to break debian.... It's the purpose of "sid" :)
[12:21] <seb128> e.g the days I do cosmic update I boot that
[12:22] <seb128> the days I work on SRUs I boot my bionic disk/partition
[12:22] <seb128> but I already reboot too much to my taste
[12:22] <Laney> but it's probably mostly testing along those same lines?
[12:22] <seb128> I don't want a 3rd Debian install
[12:22] <Laney> install it, play a bit, ship it
[12:22] <seb128> well I'm usually doing full days
[12:22] <seb128> so I dput mid-day after having used a bit the session
[12:23] <seb128> but yeah, no perfect system
[12:23] <seb128> it's just more complicated to target several distributions/series
[12:23] <seb128> and the more you add the more complex it gets
[12:23] <Trevinho> well, in any case I'm quite sure if there are not huge packaging changes if it works in cosmic, works in debian
[12:23] <seb128> no magical way around it sadly
[12:23] <Laney> ok, well, as you wish
[12:23] <Laney> there's no new argument here
[12:24] <Laney> either you want to do some work to make it happen in debian, and then nobody has to duplicate the packaging work
[12:24] <Trevinho> In any case, I'm fine to work on debian as much we can...
[12:24] <Laney> or not, and someone does, but maybe a higher chance someone catches a bug
[12:24] <seb128> Trevinho, yeah, that makes sense
[12:24] <seb128> for apps I'm confident enough
[12:25] <Trevinho> In fact... for gnome-shell I already had some sync-with-debian work done that I should prepare for cosmic
[12:25] <seb128> not likely to behave differently between distros and not the end of the world if there is an issue in the image viewer
[12:25] <seb128> but the shell is a bit trickier
[12:25] <Trevinho> although we still have our patches, but at least rebase on that
[12:26] <Trevinho> for mutter is fine, although I'd like some more freedom, but normally we add to it only stuff that is anyway proposed to upstream, so even debian guys are fine normally
[12:27] <Laney> people can do what they think is best
[12:27] <Trevinho> that said, I'm going to update g-s on ubuntu... Using my tag. :)
[12:27] <Laney> it's been this way for years with only a couple of us doing the updates on the debian side
[12:27] <Laney> not going to destabilise anything if this doesn't change
[12:28] <Trevinho> I like to propose things there, I just don't want to slow down even more the work... as you know, I already I've to pass through the desktop sponsor, later will be debian sponsor + sync. I'm ok to do it, but indeed slows things down a bit (especially if you have to reiterate)
[12:29] <Trevinho> but since all this git thing happened, working with both debian and ubuntu and upstream is a looooooot more easier and productive
[12:29] <Trevinho> so happy to put more bits at the very source
[12:31] <Trevinho> seb128: for nautilus.. our MPs are approved, let me know if you want to wait a bit more (i'd say eod) for rebase this on next upstream release if Carlos can do it, or we can proceed with these
[12:34] <Trevinho> seb128: ah, also for bionic maybe I should use different different versioning?
[12:34] <Trevinho> like 0ubuntu0?
[12:35] <fossfreedom__> Hi all - I have a patch/SRU request outstanding for the last couple of months - anyone got a bit of time to sponsor it? https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799
[12:37] <Trevinho> fossfreedom__: can you propose a MP against https://code.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-menus/+git/gnome-menus ? :)
[12:39] <fossfreedom__> Trevinho: sure ... any instructions available on how this is now done with the new launchpad git system?
[12:39] <Trevinho> fossfreedom__: https://wiki.ubuntu.com/DesktopTeam/git
[12:40] <seb128> Trevinho, right, nautilus is on my todo for today, morning was a bit busy but I do that in a bit
[12:41] <Trevinho> so gbp clone that repo, gbp pq import add your patch (in this case you can use git apply probably), then, gbp pq export, edit changelog, stage changes (avoid committing index updates, if not in a different commit)
[12:41] <seb128> Trevinho, versioning, https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
[12:41] <Trevinho> oh, that's the wiki I was looking for, thanks
[12:42] <seb128> fossfreedom__, sorry about this one, I though jbicha would handle it/I wanted to talk to him since he's the one who introduced the bug, but I was busy and he vanished then
[12:43] <Trevinho> seb128: as for version for SRU (before you review it), should be <IP_ADDRESS>-0ubuntu<IP_ADDRESS> then
[12:43] <seb128> fossfreedom__, I've already too much on my todo for today and I'm having a day off tomorrow but I have a look next week for sure if nobody beats me, if you get a git mr up by then it should be all good :)
[12:43] <Trevinho> while for mutter we used the ~ubuntu18.04.1 way
[12:43] <Trevinho> (i like that more I think :P)
[12:43] <Trevinho> not sure then
[12:44] <seb128> Trevinho, sounds like it ... I had a case of where I used ~18.04 recently which was rejected and reupload by the SRU team with another version, depends who is reviewing it
[12:44] <Trevinho> k
[12:44] <seb128> but yeah, ~serie is right as well
[12:52] <fossfreedom__> seb128: ta.  Will try to get my head around this.  I'm used to the github fork and graphical merge process - this launchpad method looks nothing like that.
[12:53] <seb128> fossfreedom__, well, it's basically "push to git, click on the submit merge request button" similar to what you did with bzr in launchpad
[12:53] <seb128> just the vcs commands changing and the url in launchpad to get/push/browse
[12:54] <fossfreedom__> ah - in that case, more happy
[13:10] <Trevinho> seb128: things for loving git even more https://stackoverflow.com/a/44754855/210151 :-D
[13:10] <Trevinho> I was trying with `git show --theirs` but, noooo...
[13:11] <seb128> lol
[13:12] <Trevinho> 1, 2, 3... easy :)
[13:12]  * Trevinho wonders how to alias these
[13:13] <Laney> I was just having a git rage that it was telling me my branch was up to date when trying to merge with debian
[13:14] <Laney> ...I was typing the wrong branch name
[13:14] <Laney> 😭
[13:29] <willcooke> sigh
[13:29]  * willcooke needs new glasses
[13:29] <willcooke> I shouldnt have got a laptop with a 1080 13" screen
[13:30]  * willcooke <-- old
[13:39]  * Laney nelson laugh
[13:48] <Trevinho> Laney: I love raging laney :-D
[13:49] <Laney> ;_;
[13:54] <Laney> ahhhhhhhhhhhhhhhhhhhhh
[13:54] <Laney> a new gtk 3.23 release just as I was about to do the other one
[13:54] <Laney> new release, new testsuite failures /o\
[13:58]  * didrocks reboots with gdm debug log on
[13:58] <didrocks> gdm doesn't find a session in /usr/local
[14:13]  * czajkowski passes Laney a 99 to cool on down :)
[14:13] <Laney> yessss
[14:13] <Laney> 🍦
[14:13] <Laney> that would be good actually, this room is currently 27.7C
[14:18] <didrocks> ok, so:
[14:18] <didrocks> 1. GDM doesn't have /usr/local in its env var, that's why I think it's not picking up things in /usr/local
[14:19] <didrocks> 2. GNOME Shell doesn't like mode names with upper letters
[14:19]  * didrocks will file moar bugs today
[14:23] <Trevinho> didrocks, Laney, seb128: I've updated this section https://wiki.ubuntu.com/DesktopTeam/git#Merge_a_new_upstream_version including the thing we discussed earlier about push-back to salsa the pristine-tar/upstream branches changes, how to proceed if the tag is already there and how to deal with rebasing patches
[14:24] <Trevinho> didrocks: you can pass XDG env to gdm now, not in 3.28 though
[14:24] <Trevinho> I fixed that as I needed it to get gdm working from jhbuild
[14:27] <didrocks> Trevinho: yeah, my issue is bionic
[14:27] <Trevinho> didrocks: eh, there's a patch to cherry-pick if you want
[14:27] <Trevinho> :)
[14:28] <didrocks> Trevinho: unsure it worthes it right now, but we'll see. At least, no need to open a bug on that one :)
[14:33] <didrocks> a last reboot, hopefully :)
[14:42] <Trevinho> mh, when gnome-shell was pushed to ~ubuntu-desktop, the tags where not pushed...
[14:43] <Trevinho> also the release is missing a tag...
[14:45] <Trevinho> while ubuntu/3.28.2-0ubuntu1 is wrong...
[15:00] <Trevinho> didrocks: we miss tags on gnome-shell, could you push and pull them from my remote?
[15:00] <Trevinho> err pull and push  :-P
[15:04] <Trevinho> and actually before pushing fix ubuntu/3.28.2-0ubuntu1 as that should be for 65d8e54e48028903b626117d6f19a4aab42353fa (current git head)
[15:04] <didrocks> Trevinho: who did push your g-s word and why did we miss tags?
[15:04] <Trevinho> cause tags were not pushed I guess
[15:04] <didrocks> I don't remember, is it me transforming the branch?
[15:05] <Trevinho> might be, if you didn't just changed ownership from lp ui that might have happened
[15:05] <didrocks> Trevinho: ah, you did the transform
[15:05] <Trevinho> not an issue, although I think I deleted the ~canonical-deskop-team branch so... let me seee
[15:05] <didrocks> Trevinho: and I confirm I don't have the tags locally, so you didn't push them in your script :p
[15:05] <Trevinho> no, no I pushed... they are in my remote
[15:05] <didrocks> well, remote from when? ;)
[15:06] <Trevinho> and same in the all the other canonical remotes, so... should be there
[15:06] <didrocks> can you give me the remote url so that I don't have to search for it and just push the tags?
[15:06] <Trevinho> lp:~3v1n0/ubuntu/+source/gnome-shell
[15:06] <didrocks> thx!
[15:06] <Trevinho> let me check though as that should be a bit different now, but just try to get tags from that and see if they apply
[15:07] <Trevinho> plus you nee to git tag the desktop-team heaad with ubuntu/3.28.2-0ubuntu1
[15:07] <didrocks> Already up to date.
[15:07] <didrocks> hum, how do we fetch the tags only?
[15:08] <Trevinho> git fetch --tags
[15:08] <didrocks> argh, missing s :/
[15:08] <Trevinho> but actually these two branches might be a bit different, so let see if they apply, otherwise I need to go manual way
[15:08] <didrocks> actually, the tag ubuntu/3.28.2-0ubuntu1 already exits
[15:08] <didrocks> but on a commit you unreferenced
[15:08] <Trevinho> yeah, but it's wrong
[15:09] <Trevinho> yep
[15:09] <didrocks> why would it be different, you changed it again? :/
[15:10] <Trevinho> no, I think we messed up things, as it was in the ~canonical-desktop-team and I removed the repo probably, while you imported from lp:~3v1n0 so they were different I think
[15:10] <didrocks> anyway, I just retag tip with ubuntu/3.28.2-0ubuntu1, deleting the old one
[15:10] <Trevinho> yeah, need to do that
[15:10] <didrocks> and yeah, I can't push because of tag conflicts
[15:11] <didrocks> so -f? :/
[15:11] <Trevinho> also a36941c3b739d907eeaf8a17bd73e7dca5988ab7 should be ubuntu/3.28.1-0ubuntu2-bzr to match old behavior
[15:11] <Trevinho> you can push -f on tag or
[15:11] <didrocks> it's 65d8e54e48028903b626117d6f19a4aab42353fa
[15:11] <Trevinho> push --delete tag and then push again
[15:11] <didrocks> which is tip
[15:11] <didrocks> yeah, but people already having the branch would have conflicts
[15:11] <didrocks> anyway… I'll tell them to talk to you, I don't want to waste more time on this :p
[15:12] <didrocks> the other tags were already on the remote
[15:12] <didrocks> it's only the commit you tweaked which wasn't
[15:13] <seb128> andyrock, hey, I uploaded bug #1781996 to cosmic and bionic, unsure if you have a better testcase than watching error reports, if you do please update the bug info :)
[15:13] <didrocks> Trevinho: so, everything should be pushed
[15:13] <seb128> Trevinho, I'm sorry but I didn't manage to look at nautilus today and I need to call it a day early, going to France for the w.E and having tomorrow off
[15:13] <Trevinho> didrocks: tags aren't here https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/refs/
[15:13] <seb128> but I might do an hour or so in the morning tomorrow and look at it then
[15:14] <didrocks> ubuntu/3.28.1-0ubuntu2
[15:14] <didrocks> ubuntu/3.28.2-0ubuntu<IP_ADDRESS>
[15:14] <Trevinho> seb128: mh, ok... carlos will do a release soon though, so i'll rebase on it
[15:14] <didrocks> ubuntu/3.28.2-0ubuntu1
[15:14] <didrocks> $ git push --tags
[15:14] <didrocks> Everything up-to-date
[15:14] <Trevinho> didrocks: the old ones I mean
[15:14] <Trevinho> mhmhmh
[15:14] <Trevinho> ah, wait I've them locally
[15:14] <didrocks> :/
[15:14] <didrocks> seriously…
[15:14] <Trevinho> not sure, I pulled them from remote before
[15:14] <Trevinho> https://www.irccloud.com/pastebin/CBzR5rhA/
[15:15] <Trevinho> So they should be no remote
[15:15] <Trevinho> didrocks: ahhhhhhhhhhh
[15:15] <Trevinho> need to od this
[15:15] <Trevinho> what git tag -l 'ubuntu/*' points to you?
[15:15] <seb128> Trevinho, well, let's see tomorrow
[15:16] <seb128> maybe the delay is helping in that regard :)
[15:16] <Trevinho> seb128: I'll prepare everything tonight if he gets it ready
[15:16] <seb128> thx
[15:16] <didrocks> Trevinho: the 3 commits I gave ^ that's what I wrote
[15:18] <Trevinho> didrocks: this is weird... why when I fetched from my remote I had the tags there, while you didn't? :o
[15:19] <didrocks> Trevinho: I just refetched again from your repo, and this time I got 50Mg + the tags… :/
[15:19] <Trevinho> mh and I didn't push nothing
[15:19] <didrocks> launchpad snaffu?
[15:19] <didrocks> I'm repushing your tags and content
[15:20] <Trevinho> only tags
[15:20] <didrocks> well, git push --tags do both
[15:20] <Trevinho> mhmhm wait then :)
[15:20] <didrocks> too late
[15:20] <didrocks> but errored out
[15:20] <didrocks> because of tag conflicts
[15:21] <Trevinho> soooo... this
[15:21] <Trevinho> git tag | grep -E '^ubuntu/|^debian/|^upstream/' | xargs --no-run-if-empty  git push origin --force
[15:21] <Trevinho> this will only push tags
[15:22] <didrocks> Everything up-to-date
[15:22] <Trevinho> ack
[15:22] <Trevinho> as for content, good that it didn't update
[15:22] <didrocks> it did
[15:22] <didrocks> I think it only errored out on the tip tag
[15:22] <didrocks> which isn't part of the transaction
[15:22] <didrocks> so your 60M or so are now in the ~ubuntu-desktop branch
[15:23] <Trevinho> lovely data
[15:23] <Trevinho> well I would have only pushed the tags as before, reducing a bit the things, but...
[15:23] <didrocks> ok, so I need to fix manually the tip tag
[15:23] <Trevinho> could you tag also a36941c3b739d907eeaf8a17bd73e7dca5988ab7 as ubuntu/3.28.1-0ubuntu2-bzr for consistency
[15:23] <Trevinho> ?
[15:24] <Trevinho> gnome-shell wasn't done with the script, so... it's different from others. Or well was scripted, but later :)
[15:24]  * didrocks would love to not spend time on this and has real work to do :/
[15:24] <didrocks> let me fix those 2 tags
[15:24] <didrocks> I hope it's the last time we complexify something this way
[15:24] <Trevinho> I know, it's only few minutes, then I'll bother you only for pulling new upstream version :-D
[15:25] <didrocks> check with others maybe? ;)
[15:25] <Trevinho> eh, basically I made laney already crazy enough, I need to go back to you a bit :-D
[15:26] <seb128> or to stop making people crazy?
[15:26] <seb128> that is way more discussions and issues that it should have been :/
[15:26] <seb128> #fail
[15:27] <didrocks>  * [new tag]             ubuntu/3.28.1-0ubuntu1 -> ubuntu/3.28.1-0ubuntu1
[15:27] <didrocks>  * [new tag]             ubuntu/3.28.1-0ubuntu2-bzr -> ubuntu/3.28.1-0ubuntu2-bzr
[15:27] <didrocks> done
[15:27] <Trevinho> seb128: not possible, since I've not push rights in nor salsa or our git...
[15:34] <Trevinho> didrocks: thanks, I should be able to proceed with new push now
[15:35] <didrocks> yw!
[15:37] <Trevinho> and... When you've time maybe you can pull push again without interruptions, please :)
[15:38] <didrocks> git fetch -> nothing to do…
[15:38] <didrocks> from your repo
[15:39] <didrocks> ah --tags
[15:39] <didrocks> please be explicit
[15:39] <didrocks> again on ubuntu/3.28.2-0ubuntu1?
[15:39] <didrocks> ok, git push -f --tags and done
[15:44] <Trevinho> mh it was still pushing, weird since most of things should be already there but it takes a bit, I'll write when is finishing for real -_-
[15:47] <Trevinho> ok it's done... I've not finalized the relase though, as someone should sponsor that anyway... let me know if i can do that
[15:52] <didrocks> Trevinho: pushed, and yes, please wait for things to be pushed before pinging
[15:58] <didrocks> Trevinho: you only pushed ubuntu/master
[15:58] <didrocks> not pristine-tar
[15:58] <didrocks> nor upstream/latest
[15:59] <didrocks> please follow the wiki :/
[15:59] <didrocks> it does say it explicitely when upgrading a new release
[15:59] <Trevinho> didrocks: these are to be taken from salsa, which is not ready yet...
[16:00] <Laney> just push them, it's going to be the same
[16:00] <Trevinho> indeed i know that, that's why I've updated the wiki also for that
[16:00] <didrocks> Trevinho: hum, we told we would do it ourself and merge from salsa
[16:00] <didrocks> that's what we discussed with Laney
[16:00] <Trevinho> ok
[16:00] <didrocks> Trevinho: please don't, revert to what it was
[16:00] <Laney> I'll push those now in a minute if you want
[16:00] <Trevinho> Laney: I think I've to redo the gnome-shell debian/master I think though
[16:00] <didrocks> I'll let Laney goes on from now :)
[16:01] <didrocks> but please don't decide on workflow changes yourself
[16:01] <didrocks> so, revert the wiki as it was, with what we agreed upon
[16:01] <Trevinho> didrocks: no, I didn't change things, we said here before... plus seb said just do... so it's hard what is a democracy and what a doacracy
[16:02] <didrocks> Trevinho: well, we said before with Laney that we would do it and merge back
[16:02] <Laney> no I'll just push to salsa
[16:02] <Trevinho> didrocks: check what I also changed, there are things which need to be that way (like importing orig)
[16:02] <Laney> don't know about this other stuff, I'm not getting involved with that right now
[16:02] <didrocks> Trevinho: I'm a little bit tired to check again and again random changes
[16:02] <didrocks> so no, I won't check, if it doesn't work and we see it yourself, you will fix them I guess
[16:02] <didrocks> which is fine
[16:02] <didrocks> but I'm out of that update for now
[16:03] <Trevinho> ok, I can handle changes when they will needed
[16:03] <didrocks> sounds like everyone is going to use a different workflow
[16:03] <didrocks> going to be create something interesting and messy, but we'll see
[16:03] <Trevinho> didrocks: nope... it's all the same, just we can't use import-orig for example when orig hsa alrady the tag
[16:04] <Trevinho> so, that needed to be changed
[16:04] <didrocks> that's was one of the point, indeed, but I hope that you didn't chagne for the case the tag wasn't here
[16:04] <Trevinho> Nope, I only mentioned that
[16:04] <didrocks> k
[16:05] <didrocks> anyway, enough for today, get someone to sponsor it now :)
[16:05] <Trevinho> and updated to mention that if the pristine-tar and upstream/* branches are updated, they need to be proposed to salsa
[16:05] <Laney> those are pushed now, no chance of diverging any more
[16:06] <didrocks> eoding, see you tomorrow guys for those who are around tomorrow :)
[16:06] <didrocks> friday is git-workflow-less discussion \o/
[16:06] <Laney> bye didrocks!
[16:06] <didrocks> enjoy your long week-end Laney ;)
[16:31] <Trevinho> Laney: now debian/master for g-s is fine
[16:31] <Trevinho> not sure what happened, like the patch-queue branch went into master :o
[16:34] <Laney> sí, looking good
[16:34] <Laney> at least it fast forwarded this time
[16:46] <Trevinho> Laney: good, as for g-s on ubuntu, not sure you've time to sponsor... in case I can finalise the changelog, and i've already pushed in my local a new changelog entry
[16:47] <Laney> I'm on the train, probably not but I'll see
[16:47] <Laney> trying to build debian now
[16:48] <Laney> made me notice you got some comments from Florian on gnome-shell !4
[16:48] <Laney> 😜
[16:50] <Trevinho> yes, I didn't address them yet since there were some bigger bits he probably wanted to change, so these where only styling related
[16:50] <Trevinho> Laney: where are you heading to?
[16:51] <Laney> south coast
[16:51] <Laney> need some more sea swimming
[16:52] <Trevinho> right, enjoy then
[16:52] <Trevinho> I've been swimming in awesome sea these days, so back to a city (Granada) since last night
[16:52] <Trevinho> git log
[16:52] <Trevinho> no, this is not terminal, marco!
[16:52] <Laney> commit d3adb33f
[16:53] <Laney> Author: Santa Claus
[17:06] <Trevinho> :)
[17:07] <Trevinho> I've prepared also the gnome-shell upstream branches
[17:07] <Trevinho> errrrrrr
[17:07] <Trevinho> gnome-shell bionic branches
[17:07]  * Trevinho need to stop :)
[17:42] <Laney> oh god git rerere just saved my life
[19:15] <Laney> Trevinho: if you merge gnome-shell with debian/3.28.3-1 tag it'll make me happy (ubuntu/master)
[19:16] <Laney> and then make the changelog a merge changelog (remaining changes: stuff)
[19:19] <Laney> we now have new gtk 3.23 in cosmic-proposed but glib's going to have to wait because there's no tarball just yet
[19:20] <Laney> hope it doesn't break stuff
[19:20]  * Laney is going OFFLINE until tuesday
[19:20] <Laney> BYE!!!!
[19:22] <willcooke> See ya Laney, have a good one
[19:36] <Trevinho> Laney: yeah I already had a branch for that, need to do it... Although for now better to wait next major, because otherwise all the merges with Ubuntu/bionic would be harder
[19:39] <oSoMoN> enjoy the time off Laney !


[18:34] <studio-user834> Where is the best place to find help with keeping pulse audio working on Studio? Everytime it gets messed up it takes me forever to get sound back again.
[20:10] <studio-user777> ello my friends
[22:01] <JDA2> I have a ubuntustudio newbie question, if anyone is active on this channel
[22:27] <JDA2> I have a ubuntustudio newbie question, if anyone is active on this channel
[22:32] <krytarik> JDA2: You know, just ask it.. :)
[22:33] <JDA2> Sorry for the "noise" post.  :-)   I am trying to find a Linux distro that will support video capture from my Hauppauge WinTV card.  But I don't know if naitve ubuntustudio will do that, or whether I have to customize it with drivers for my TV card.
[22:36] <krytarik> Well, I'm using one myself, and I don't remember having done anything extra on my current install to make it work.. :D
[22:38] <JDA2> Sounds encouraging.  As a real newbie, I tried opening Kdenlive, and in the configuration window, it seems to acknowledge that there is a Hauppauge card there.  That sounded good.   But I don't see what to click to see if it can view the TV.
[22:39] <JDA2> Should I be using some other program?
[22:39] <krytarik> I'm just using plain MPlayer for it myself. >_>
[22:48] <JDA2> OK thanks.  As a real video+linux newbie, I was not familiar with mplayer.  Looks like it has LOTS of options!  Could you tell me what parameters you use to access your TV card?
[22:55] <krytarik> Are we talking digital or analog here anyway?  I got the latter.
[22:56] <JDA2> Analog.  I hope to hook VCR to the coax jack and import old home movies.
[23:10] <krytarik> JDA2: Ok, so I got 1.) in my config: tv = driver=v4l2:chanlist=europe-west:norm=PAL:buffersize=150:device=/dev/video0:input=0:width=720:height=576:adevice=hw.1,0:amode=1:alsa=1:audiorate=32000:immediatemode=0 -- heartbeat-cmd = "nice xscreensaver-command -deactivate > /dev/null" -- plus the channels, and 2.) in a custom shell script I called "tv": mplayer -aspect 4:3 -vf-add pp -autoq 6 ...
[23:10] <krytarik> ... -vf-add eq=0:0,pp=hb:c/vb:c/dr:c/lb:c/tn -af volume=6:0 -framedrop "${@:2}" tv://$1
[23:15] <JDA2> OK, thanks krytarik.  I will give those a try.   (I am not on that computer right now, unfortunately)   I appreciate your help!