Package Details: teams

Git Clone URL: (read-only, click to copy)
Package Base: teams
Description: Microsoft Teams for Linux is your chat-centered workspace in Office 365
Upstream URL:
Licenses: custom
Conflicts: ms-teams
Replaces: ms-teams
Submitter: ogarcia
Maintainer: ogarcia (jvybihal)
Last Packager: ogarcia
Votes: 151
Popularity: 19.08
First Submitted: 2019-12-10 18:41
Last Updated: 2020-10-05 16:56

Latest Comments

« First ‹ Previous ... 9 10 11 12 13 14 15 Next › Last »

Muflone commented on 2019-12-11 15:26

thank you @jvybihal and @ogarcia for settling the things so easily.

I'm therefore deleting the ms-teams package, now useless.

jvybihal commented on 2019-12-11 15:23

@Muflone ok :)

Also, I think teams-for-linux-official-bin by @dennisoehme should merge too, I saw he put some nice work into PGP validation and it is always nice to have.

ogarcia commented on 2019-12-11 15:23

@muflone, the package that is a duplicate of ms-teams is that is a different version of teams only for insider users. This package is the open one, I think that both packages must exist since are differents versions.

I added @jvybihal as co-maintainer in both packages, this and

@jvybihal I think that names must be teams and teams-insiders as original ones. People find this package before ms-teams because enter teams word in search box and suggest this one.

Muflone commented on 2019-12-11 15:18

@jvybihal I think the teams name suits better. You could co-maintain it along with @ogarcia

Then we can delete the ms-teams package

jvybihal commented on 2019-12-11 15:03

I agree that the duplicates need to merge into one. I contacted @ogarcia about a month ago with PRQ#16712. He suggested keeping name teams-insiders - which kind of makes sense, because it's the naming MS uses, but I (as some others) like ms-teams much better. So I decided not to argue and let it be, without reply - I knew my package was not originally aimed for the insiders version, I just wanted to create the ground for official release once it came out. And now it did, and I switched my package to it.

It is beyond my understanding why we have 3 packages of the same thing now, and what is the reasoning behind it.

Anyway, I like ms-teams name, but I don't care too much about it, so merging everything into 'teams' is fine with me, if others like it better. I can co-maintain it, but I do not insist on it.

wizard32 commented on 2019-12-11 14:57

Works fine to me. The only issue that I have so far is the auto-correction and the spell check is not working any more. Any other here with the same issue?

Muflone commented on 2019-12-11 14:38

@ogarcia this package is a duplicate of which was created 3 months ago, while this package was created yesterday

we have to make a choice here:

1- this package will be removed and ms-teams will keep the previous name

2- you let the ms-team package to take this package and we can merge ms-teams into teams

davidhaller commented on 2019-12-11 08:50

Chrome installs certificates user-wide (I believe the location was ~/.pki), this might be the reason Teams can see your company certificate.

ogghi commented on 2019-12-11 07:41

I don't think so, as I don't have any chrome/chromium installed in my laptop since I re-installed with Arch... Also nothing written here in the dependencies?

je-vv commented on 2019-12-11 05:20

Does "teams" on gnu+linux depends on chromium/chrome, or at least reads chromium/chrome settings somehow? If a dependency, should it be included as such?

See, I authenticated for the company account, and it rejected me since I don't have double authentication, but after adding my personal company certificate to chromium, it just worked. Which makes me suspect whether teams is using chromium/chrome to authenticate, or it uses its setting given it's sort of based on chromium/chrome...