[01:37]  shirish_ (~quassel@117.195.119.10) left irc: Read error: Connection reset by peer
 [02:37]  shirish (~quassel@117.195.118.18) joined #hamara.
 [02:47]  shirish_ (~quassel@117.222.3.11) joined #hamara.
 [02:53]  shirish (~quassel@0001358e.user.oftc.net) left irc: Ping timeout: 480 seconds
 [03:40]  kamaldeep (~kamal@210.7.64.8) joined #hamara.
 [04:04]  shirish_ (~quassel@117.222.3.11) left irc: Quit: No Ping reply in 180 seconds.
 [04:05]  shirish (~quassel@117.222.3.11) joined #hamara.
 [04:21]  shirish_ (~quassel@117.195.115.130) joined #hamara.
 [04:29]  shirish (~quassel@0001358e.user.oftc.net) left irc: Ping timeout: 480 seconds
 [05:23]  shirish (~quassel@117.214.126.128) joined #hamara.
 [05:29]  shirish_ (~quassel@117.195.115.130) left irc: Ping timeout: 480 seconds
 [05:32]  shirish_ (~quassel@117.222.5.4) joined #hamara.
 [05:38]  shirish (~quassel@0001358e.user.oftc.net) left irc: Ping timeout: 480 seconds
 [08:22]  gurvinder (~gurvinder@210.7.64.6) joined #hamara.
 [08:22]  gurvinder (gurvinder@210.7.64.6) left #hamara.
 [08:46]  shantanu1 (~shantanu@210.7.64.5) joined #hamara.
 [08:46]  shantanu1 (shantanu@210.7.64.5) left #hamara.
 [09:08]  anant (~anant@210.7.64.52) joined #hamara.
 [09:27]  vikas (~vik@2a02:17d8:1010:1:94ab:51e4:3e52:1e45) joined #hamara.
 [09:35]  anant (~anant@210.7.64.52) left irc: Remote host closed the connection
 [09:38]  anant (~anant@210.7.64.52) joined #hamara.
 [09:57]  anant (~anant@210.7.64.52) left irc: Remote host closed the connection
 [12:33]  kamaldeep (~kamal@210.7.64.8) left irc: Quit: Leaving.
 [13:12]  vikas (vik@2a02:17d8:1010:1:94ab:51e4:3e52:1e45) left #hamara.
 [14:08]  MANGESH_ (~quassel@106.209.31.15) joined #hamara.
 [14:17]  MANGESH_ (~quassel@106.209.31.15) left irc: Remote host closed the connection
 [14:36]  vikas (~vik@2a02:17d8:1010:1:94ab:51e4:3e52:1e45) joined #hamara.
 [14:50] <shirish_>  good evening people.
 [14:50] <vikas>  hi shirish
 [14:51] <shirish_>  vikas: hi
 [14:51] <shirish_>  just putting up an email to the list.
 [14:53] <vikas>  i wrote a blog post about kodi today - but wordpress lost my draft :(
 [14:53] <vikas>  will try and rewrite it!
 [14:59] <shirish_>  that is strange, that should never happen.
 [15:00] <shirish_>  vikas: did you raise a bug-report for it ?
 [15:00] <vikas>  i think the session expired midway and when I logged back in, the draft was gone
 [15:01] <vikas>  so i guess it's not a bug as such
 [15:01] <shirish_>  umm.... did you save it before session expiry ?
 [15:01] <vikas>  no
 [15:01] <vikas>  hence I think it was my fault
 [15:01] <shirish_>  that explains it.
 [15:02] <shirish_>  right, right.
 [15:02] <vikas>  i guess it doesn't have an autosave feature for a draft
 [15:02] <shirish_>  I think we might also have to tune wordpress a bit.
 [15:02] <shirish_>  it has, I'm guessing it's not turned on or something
 [15:02] <shirish_>  also the session bit might be tunable.
 [15:03] <shirish_>  vikas: do you know what version of wordpress did anant install ?
 [15:03] <vikas>  no - don't
 [15:03] <vikas>  would expect it to be latest though
 [15:04] <shirish_>  umm.... ok. It would be better if he the version numbers did show up on wordpress install, makes it easier to find support and whatever else that is needed.
 [15:04] <shirish_>  it also has a pretty good plugin and themeing community.
 [15:08] <vikas>  btw - jessie sync is finished
 [15:09] <vikas>  I have started work on building a sugam iso using debian packages
 [15:09] <vikas>  :q
 [15:14] <shirish_>  don't quit now :)
 [15:14] <shirish_>  just sent that mail, it looks like mailman 3 is good for us.
 [15:16] <shirish_>  vikas: I had been waiting for this for last 7 odd years, to see it finally being released today, am a bit overcome.
 [15:16] <shirish_>  I do hope mailing lists have a resurgence because of it as forums had a slightly bigger hand all these years.
 [15:26] <vikas>  shirish: i need to take a close look at mailman
 [15:26] <shirish_>  vikas: sure, go ahead.
 [15:26] <vikas>  if ti can give us google groups type functionality - then I would favour dropping the forum altogether
 [15:27] <vikas>  mainly we need to know if a user can use it just via the web interface
 [15:27] <shirish_>  the feature lists says it does, that is what I recommended too, let's take it for a spin, give it some sort of domain (I hope we do have some reserve domains parked for such usage)
 [15:27] <shirish_>  let it mirror our existing mail infrastructure and then let all of us test out the various bits and pieces
 [15:28] <vikas>  i wonder if we can find a demo install somewhere
 [15:28] <shirish_>  the UI, posting, backup etc. If we find it to be superior than our current methods than let it take over.
 [15:29] <vikas>  agree
 [15:29] <shirish_>  umm... I *think* I did share that the some of the fedora 21 lists uses the new mailman 3 interface.
 [15:29] <vikas>  ok
 [15:29] <vikas>  let me have a look around too
 [15:30] <shirish_>  I am in the middle of filing a mailman 3 wishlist bug, gonna take a break for sometime and then will be back.
 [15:30] <vikas>  ok
 [16:03]  amardeep (~amardeep@210.7.64.3) joined #hamara.
 [16:24]  shahper (~shahper@210.7.64.2) joined #hamara.
 [16:25]  aparna (~aparna@210.7.64.2) joined #hamara.
 [16:26] <aparna>  Hi all
 [16:29] <aparna>  I was working on bug no 69 and found that there is no configuration file in /etc/nginx/sites-enabled/ folder
 [16:30] <aparna>  How shall I proceed
 [16:31] <aparna>  Do you want me to contact diaspora guys for configuration file and then recreate debian package
 [16:33] <shirish_>  aparna, have you synced to the latest release of diaspora ?
 [16:35] <shirish_>  the bug is confusing also, do you mean to say there is no configuration file or the configuration file is not the right place.
 [16:36] <shirish_>  the configuration file you shared for review, where did you get it ?
 [16:36] <shirish_>  aparna ^
 [16:37] <aparna>  I have installed version
 [16:37] <aparna>  http://in.devel.hamaralinux.org/hamara/pool/main/d/diaspora-installer/diaspora-common_0.2+1.0hamara_all.deb
 [16:38] <aparna>  configuration file which already there is only for nginx, however not for specific site, in this case diaspora
 [16:39] <shirish_>  umm... so there are two things that can be done.
 [16:40] <shirish_>  a. rename the bug heading so we know what the issue is, it's confusing there.
 [16:40] <shirish_>  b. ask the diaspora people for a sample for some $sample site and on the basis of that make one for hamaralinux
 [16:41] <shirish_>  aparna: what do you think ? ^
 [16:41] <aparna>  I guess thats what we need to do :)
 [16:41] <shirish_>  this could also be put up as a sort of bug in their bug-tracker so that there is a sample site already done.
 [16:42] <shirish_>  would make it easier for the next person who comes along and wants to do it for some $random site.
 [16:42] <shirish_>  vikas: filed bugs.debian.org/783732
 [16:42] <shirish_>  http://bugs.debian.org/783732
 [16:43] <shirish_>  sorry it took so long, I had to manually pull in all the dependencies and see they were doing alright and try to show it was a genuine mailman installation.
 [16:43] <vikas>  am in a meeting at the moment - but just saw this discussion
 [16:43] <vikas>  I think the diaspora installer maintainer did fix this bug upstream - but I don't think we have rebuilt the package
 [16:44] <shirish_>  the maintainers do like that if you have the package installed and all the pre-requisites as well as suggests installed too, makes for better response also.
 [16:45] <vikas>  https://wiki.debian.org/Diaspora
 [16:45] <shirish_>  vikas: the mailman 3 live demo did you see ? http://lists-dev.cloud.fedoraproject.org/archives/
 [16:48] <vikas>  ok
 [16:48] <vikas>  shirish: that looks great
 [16:48] <vikas>  shirish: solves our purpose
 [16:49] <vikas>  let me take a look at how to install it
 [16:50] <vikas>  aparna: my suggestion would be to have a look at the diaspora git repo and see if there are any commits that fix this issue
 [16:51] <vikas>  aparna: if you cannot find it, then the author is quite helpful. We have given their organisation hosting for http://diasp.in - so I expect they will help you out
 [16:51] <aparna>  ok I will check
 [16:51] <vikas>  aparna: the author is praveen@debian.org
 [16:52] <vikas>  aparna: I suggest you check git and also try building a new package to verify if this bug is still there before contacting praveen
 [16:54] <aparna>  vikas: I guess this is where i should check about latest commits
 [16:54] <aparna>  https://gitlab.com/groups/debian-diaspora
 [16:55] <vikas>  aparna: yes - that's the place
 [16:55]  shirish_ (~quassel@117.222.5.4) left irc: Ping timeout: 480 seconds
 [16:56] <aparna>  I have'nt build any debian package so I will check with amar or shantanu for further steps.
 [16:57] <vikas>  aparna: you can find it on our jenkins install
 [16:58] <vikas>  aparna: ask Amardeep to show you?
 [16:58] <aparna>  okk :)
 [17:00]  shahper (shahper@210.7.64.2) left #hamara.
 [17:01]  aparna (~aparna@210.7.64.2) left irc: Quit: Leaving.
 [17:01]  shirish (~quassel@59.88.96.98) joined #hamara.
 [17:02] <shirish>  sorry, net quit on me :(
 [17:02] <shirish>  but now back :)
 [17:03] <vikas>  tbs guys just left for the day
 [17:04]  amardeep (~amardeep@210.7.64.3) left irc: Quit: Leaving.
 [17:04] <shirish>  tbs - to be sad ?
 [17:05] <shirish>  or you wanted to say tbh - to be honest
 [17:05] <shirish>  vikas: ^
 [17:05] <shirish>  vikas: did you see bug #132 http://bugs.hamaralinux.org/show_bug.cgi?id=132
 [17:07]  shirish_ (~quassel@59.97.97.69) joined #hamara.
 [17:08]  shirish__ (~quassel@117.195.127.176) joined #hamara.
 [17:13] <shirish__>  vikas: let me know when your meeting ends, then we can talk a bit.
 [17:13] <vikas>  shirish: short of time, have got abt 15 mins now
 [17:13] <vikas>  am out of mtg
 [17:14]  shirish (~quassel@0001358e.user.oftc.net) left irc: Ping timeout: 480 seconds
 [17:14] <shirish__>  vikas: ok, have you thought of setting up a partial mirror for debian ?
 [17:14] <shirish__>  has that been discussed ?
 [17:15] <vikas>  shirish: no it hasn't
 [17:15]  shirish_ (~quassel@59.97.97.69) left irc: Ping timeout: 480 seconds
 [17:16] <shirish__>  ohk.... so probably will need to put it in a thread.
 [17:17] <vikas>  yeah :)
 [17:17] <shirish__>  because we will need to discuss which architectures to support, and when to sync
 [17:17] <vikas>  I am not sure we have extra bandwidth though
 [17:17] <shirish__>  because believe it or not, debian is updated 4 times in a day,
 [17:17] <vikas>  and debian does have a lot of mirrors already
 [17:18] <vikas>  shirish: do you think we should be a debian mirror?
 [17:18] <shirish__>  then are we just going to provide a snapshot service ?
 [17:18] <vikas>  shirish: we are not building a copy of debia
 [17:18] <vikas>  *debian
 [17:18] <shirish__>  true, but most packages would be based on debian.
 [17:18] <vikas>  so our repo won't be the same
 [17:19] <shirish__>  so are we go to be using a different version of compiler, different version of kernel etc. ?
 [17:19] <vikas>  shirish: kernel is something we quite possibly will want to build
 [17:19] <vikas>  also a number of other packages have to be build - like firefox or virt-manager
 [17:20] <vikas>  this list will likely expand
 [17:20] <shirish__>  but why?
 [17:20] <vikas>  but there are currently > 50 packages that we do not take from ubuntu
 [17:20] <shirish__>  aha, is that list put up somewhere.
 [17:20] <vikas>  i need to get you access to the build system
 [17:21] <vikas>  but you can see the list in git
 [17:21] <shirish__>  right.
 [17:21] <vikas>  agree we should have it on the wiki though
 [17:21] <shirish__>  what is the git repo. address ?
 [17:21] <vikas>  git.hamaralinux.org
 [17:22] <shirish__>  and is it browseable through a browser or do I need to do a clone of it ?
 [17:22] <vikas>  running gitlab
 [17:22] <vikas>  ah, i think you need credentials for it
 [17:22] <shirish__>  right, right.
 [17:23] <shirish__>  yup, it is asking for credentials to sign in.
 [17:23] <shirish__>  why have you made the repo. private ?
 [17:23] <vikas>  https://git.hamaralinux.org/hamara-developers/hamara-packages/tree/development/hamara-packages/1.0
 [17:23] <shirish__>  do we have any non-free packages therein ?
 [17:24] <vikas>  I need to go through the build process with you - but am short of time
 [17:25] <vikas>  the url I have just shared is the hamara packages repo
 [17:25] <vikas>  we also have helper script repo which is not currently public
 [17:25] <vikas>  that contains scripts that take upstream source, make branding changes and build new debs
 [17:26] <vikas>  we also use helpers to patch packages
 [17:26] <shirish__>  ok cool. that is understood.
 [17:26] <shirish__>  I do understand the need for branding and making those changes in hamara
 [17:26] <vikas>  an example is - our helper script for gnome-shell disables the location service - which upstream enable by default
 [17:27] <shirish__>  actually that is also what is being in debian as well, they also have disabled it
 [17:27] <shirish__>  that is why I was saying it would be good to be in sync with them, because apart from branding changes there is lot we could re-use from there.
 [17:28] <vikas>  yes - that's exactly what we are doing atm with ubuntu upstream
 [17:28] <shirish__>  and also we should try to contribute back, simply because we would be getting more testers therein than here.
 [17:28] <vikas>  we sync each day from upstream
 [17:28] <vikas>  but we do not sync any packages that we are building ourselves
 [17:29] <vikas>  agree - anything that should be pushed upstream, will be
 [17:29] <vikas>  but so far that changes have not been bug fixes
 [17:29] <vikas>  another example is our virt-manager patch
 [17:30] <vikas>  it simply adds Hamara Linux as a linux distro type in virt-manager
 [17:30] <shirish__>  vikas: that is precisely what I am asking that we do, the branding changes could be put in a sort of patch series that is to be applied whenever a new version comes in.
 [17:30] <shirish__>  let the bug-fixes flow from debian to us and then let us generate the .deb again with our branding.
 [17:30] <shirish__>  in that we don't lose any bug-fixes which are applied by debian and we profit from our branding.
 [17:31] <vikas>  we can configure the existing set up to do exactly that
 [17:31] <shirish__>  and in case something breaks, we can always file a bug in the debian BTS that hey, this got broke while we were trying to do so and so.
 [17:31] <vikas>  the only small change on our side is to monitor upstream for new versions of packages that we build
 [17:31] <vikas>  and then trigger our build instead of pulling the package from upstream
 [17:31] <shirish__>  that + bug-fixes.
 [17:32] <shirish__>  because debian does do quite a bit of that, so if somebody else is doing the hard-work then why should we duplicate it.
 [17:32] <vikas>  i'll set up my debian/sugam build on that basis