[12:20: 1] MANGESHDIVTelegram[m] (~telegr_36@2001:470:1af1:101::164d) joined #hamara.
[12:20: 3] <MANGESHDIVTelegram[m]> Welcome pankaj
[13:47: 8] PankajJadhavTelegram[m] (~telegr_36@2001:470:1af1:101::164e) joined #hamara.
[13:47: 0] <PankajJadhavTelegram[m]> Thank you mangesh 🙏
[13:48: 3] <vik[m]> welcome to both of you
[13:48: 7] <vik[m]> are you hamara linux users?
[13:50: 1] <MANGESHDIVTelegram[m]> @Vikas Pankaj is not yet using hamara but he wants to start contributing. He is complete beginner
[13:51: 5] <vik[m]> ok, that's great! we're just finalising the hamara sugam release
[13:51: 5] <MANGESHDIVTelegram[m]> Studying for RHCE
[13:52: 2] <vik[m]> last bugs being squashed
[13:52: 2] <vik[m]> https://wiki.hamaralinux.org/wiki/index.php/Hamara_Sugam_2.0_Final_release
[13:53: 8] <PankajJadhavTelegram[m]> I would love keeping to contribute to hamara Linux
[13:53: 2] <vik[m]> Pankaj Jadhav (Telegram): thanks - testing the next build would be very helpful
[13:53: 5] <vik[m]> Pankaj Jadhav (Telegram): i mean testing the bugs that are marked resolved in the above list
[13:54: 3] <vik[m]> rajudev: shall we upload a new iso so people can test?
[13:56: 1] <PankajJadhavTelegram[m]> Ok once uploaded I will test.
[13:56: 4] <vik[m]> Pankaj Jadhav (Telegram): latest iso is here but I think we will push a new one out today http://devel.hamaralinux.org/iso/testing/hamara-sugam/amd64/
[13:56: 8] <vik[m]> will update here once it's available
[13:57: 4] <vik[m]> rajudev: I can go ahead and do this - or do you want to?
[14:04: 8] <libregeekingkid[m]> I'll do it. We made a new buid just yesterday.
[14:04: 2] <vik[m]> "First they ignore you, then they laugh at you, then they fight you, then you win."
[14:05: 4] <vik[m]> http://www.thisisinsider.com/microsoft-azure-sphere-is-powered-by-linux-2018-4
[14:05: 4] <libregeekingkid[m]> Resolving some bugs with that build
[14:05: 6] <vik[m]> 😆
[14:05: 1] <vik[m]> rajudev: ok, ETA?
[14:05: 6] <libregeekingkid[m]> a few minutes from now
[14:06: 3] <vik[m]> awesome
[14:20: 9] <libregeekingkid[m]> hey Pankaj Jadhav (Telegram) Vik you can download a latest test build from https://www.hamaralinux.org/download/ or from http://devel.hamaralinux.org/iso/testing/hamara-sugam/amd64/current/
[14:21: 8] <libregeekingkid[m]> Vik: this build resolves #387,
[14:22: 3] <libregeekingkid[m]> #397 has been resolved as well. It it needs to be tested in a new build.
[14:55: 3] <dhanesh95[m]> I'll spin it up on VM tonight. Will update my findings here
[15:42: 7] libregeekingkid (~rajudev@111.93.193.54) joined #hamara.
[15:53: 7] <vik[m]> Dhanesh: 👍
[16:58: 9] <dhanesh95[m]> rajudev: Above link does not give me anything. Request simply times out.
[17:08: 1] <libregeekingkid[m]> Dhanesh: Could you try downloading from the website link?
[17:32: 4] <libregeekingkid[m]> Looks like it is not accessible. Making an alternative link available in a few minutes.
[17:41: 9] <libregeekingkid[m]> Dhanesh: try now with this.
[17:41: 2] <libregeekingkid[m]> http://in.devel.hamaralinux.org/iso/testing/amd64/current/
[17:49: 0] <dhanesh95[m]> rajudev: That link works
[17:49: 9] <dhanesh95[m]> But extremely slow speed.
[17:52: 9] <libregeekingkid[m]> Meanwhile I am breaking your downloads for now.
[17:52: 9] <libregeekingkid[m]> link will change
[17:53: 8] <libregeekingkid[m]> again
[17:55: 2] <libregeekingkid[m]> now the link on the website works as well.
[18:03: 3] <vik[m]> rajudev: shall we agree upgrade to firefox 59 as the fix for https://bugs.hamaralinux.org/show_bug.cgi?id=396
[18:03: 3] <vik[m]> I think that's probably the easiest way to resolve that issue
[18:08: 0] <libregeekingkid[m]> Vik: I'll start work on this, in a couple of hours or more. Also as I said, this time for firefox, should we go with the approach as discussed in #401 https://bugs.hamaralinux.org/show_bug.cgi?id=401
[18:39: 1] <vik[m]> rajudev: just to be clear on #401 and let's take firefox here as an example
[18:40: 1] <vik[m]> your proposing we keep the deb source or the firefox source?
[18:43: 9] <vik[m]> deb source plus patching is the way other debian based distros (like ubuntu) operate
[18:44: 0] <libregeekingkid[m]> as of now we used to build firefox using the helper, which used to take the upstream package, add our changes. and push to our repos. We used to do this with each build.
[18:44: 0] <libregeekingkid[m]> as per #401, we take the upstream source once, add our changes. and build.
[18:44: 1] <libregeekingkid[m]> so even when upstream changes, after some time, our builds won't break
[18:45: 2] <libregeekingkid[m]> as used to happen with the helper
[18:45: 0] isaagar (~isaagar@111.93.193.54) joined #hamara.
[18:45: 4] <libregeekingkid[m]> about the other distros. Most distros use the approach mentioned in #401
[18:45: 4] <vik[m]> from debian?
[18:45: 1] <libregeekingkid[m]> except trisquel
[18:45: 7] <libregeekingkid[m]> yes.
[18:47: 4] <vik[m]> yeah - we took the trisquel approach originally as we based on ubuntu
[18:48: 3] <vik[m]> do you propose that we link our repo with upstream?
[18:48: 8] <libregeekingkid> `link our repo with upstream` ?
[18:49: 8] <vik[m]> also, with regard to our changes, I believe they should be held in patches - but I think you have another view
[18:49: 4] <vik[m]> but this is how it's done elsewhere
[18:49: 5] <vik[m]> https://bazaar.launchpad.net/~mozillateam/firefox/firefox-trunk.head/files/head:/debian/patches/
[18:49: 9] <vik[m]> I mean should we be a remote fork of the package from debian
[18:50: 8] <vik[m]> we can watch for release tags upstream and push our package updates accordingly
[18:52: (null)
[18:52: 8] <libregeekingkid> I am fine with the helpers/patches approach. The only problem here is that the helper's or patches will fail if the upstream changes there source a lot.
[18:53: 1] <vik[m]> libregeekingkid: it is a similar approach, but it's the approach the people generally use when creating debs that are from an upstream deb src
[18:53: 9] <vik[m]> if you see the packaging guidelines - if we're creating packages we should do so from the original application source- but if we're creating downstream debs from another distro - we should probably add patches
[18:54: 6] <vik[m]> libregeekingkid: i think that's fine - otherwise I worry that we will end up not updating our packages frequently enough
[18:54: 9] <libregeekingkid> for example, if in our helper/patch we are adding changes to line #34 in a file xyz. Our patch will work. But if the line changes in upstream. or if a name or pattern changes in upstream our patches/scripts will break.
[18:55: 0] <vik[m]> yeah - i think that's fine though as we do need to regularly update our packages
[18:55: 9] <libregeekingkid[m]> Vik: there are distros using both the approaches.
[18:56: 6] <vik[m]> so updating our patches is not that much different if we're updating the package regularly
[18:56: 2] <vik[m]> we should be aiming to release package updates as regularly as upstream
[18:56: 4] <vik[m]> from a security perspective I think that's essential
[19:01: 0] <libregeekingkid> well, both approaches have there pros and con;s
[19:01: 7] <vik[m]> we would be releasing updates to packages frequently so importing and making the changes each time seems like more effort
[19:02: 6] <vik[m]> whereas using the patch approach - you only have to do something if the patch gets broken due to upstream change
[19:02: 3] <vik[m]> if you need to import every time - you have to make the same changes even if upstream source changes have not effected our change
[19:03: 2] <vik[m]> that doesn't make sense from an efficiency perspective
[19:03: 8] libregeekingkid (~rajudev@111.93.193.54) left irc: Remote host closed the connection
[19:04: 8] <isaagar[m]> libregeekingkid: Vik lets try with new approach for firefox
[19:04: 1] <isaagar[m]> and see the difference in maintaining that
[19:05: 1] isaagar (~isaagar@111.93.193.54) left irc: Ping timeout: 480 seconds
[19:05: 9] <vik[m]> i know after maintaining the firefox package previously that I was able to release firefox updates easily and that the helper/patch did not break frequently
[19:06: 9] <vik[m]> I prefer fork package and add patch as a resolution to #401
[19:07: 1] <vik[m]> we can have multiple patches too which would reduce the likelihood of them breaking
[19:07: 8] libregeekingkid (~rajudev@111.93.193.54) joined #hamara.
[19:13: (null)
[19:14: 0] <libregeekingkid[m]> or may be we can resolve this difference in opinions about the approach with trying to maintain firefox
[19:14: 8] <libregeekingkid[m]> as isaagar suggested..
[19:25: 4] <vik[m]> rajudev: The upstream dependency problem only happened because we based on a frozen version and we wanted newer firefox versions - as we rebased to testing we should not face that issue (with dependancies) in the future
[19:25: 4] <vik[m]> I was maintaining firefox for a couple of years before that and I think maybe broke once or twice
[19:34: 6] <libregeekingkid> vik[m]: our patches/changes that we'll do might break at the time when we'll be changing them. But we will make sure that our builds won't break or the packages in the repository won't break
[19:42: 5] <vik[m]> but that's easily achieved by having the production builds made against a tag and the dev builds against a different commit position
[19:42: 6] <vik[m]> again I don't see a strong reason for moving away from patches
[19:42: 7] <vik[m]> but i see less work in keeping patches
[21:19: 9] <dhanesh95[m]> rajudev: I still can't download the ISO. :(
[21:31: 1] <libregeekingkid[m]> some changes done on the infra side for providing faster downloads. Figuring out the download links
[21:34: 1] <libregeekingkid[m]> Dhanesh: apologies for the trouble. The link works from the outside now.
[21:36: 4] <libregeekingkid[m]> Dhanesh: the download link works now, and the downloads should be faster as well.
[21:37: 8] libregeekingkid (~rajudev@111.93.193.54) left irc: Quit: Leaving.
[21:37: 2] <libregeekingkid[m]> apologies for the trouble before and thanks for reporting the issuehere.
[22:27: 0] <dhanesh95[m]> Yes. It works. Just finished downloading the ISO
[22:55: 3] Action: dhanesh95[m] uploaded an image: Screenshot from 2018-04-18 22-53-36.png (603KB) <https://matrix.org/_matrix/media/v1/download/disroot.org/kLVDhxjbmawAHbKBmvCSCFYp>
[22:56: 8] <dhanesh95[m]> I like the Calamares installer. But I think there's too much text for an average Joe.
[23:05: 6] libregeekingkid (~rajudev@157.119.218.217) joined #hamara.
[23:05: 1] libregeekingkid (~rajudev@157.119.218.217) left irc:
[23:11: 4] dhanesh95 (~Dhanesh@117.195.24.168) joined #hamara.
[23:23: 5] <vik[m]> Dhanesh: I think we could improve that before release, won't take long
[23:23: 0] <vik[m]> Dhanesh: raise a bug?
[23:33: 5] <dhanesh95[m]> Vik: Wil raise a bug
[23:54: 7] <vik[m]> Dhanesh: thanks
[00:00: 0] --- Thu Apr 19 2018