>> - Does anybody really uses dragonplayer? Shouldn't we recommend vlc
>> instead?
>
> I personally like smplayer a lot
+1
--
Boris
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
>>> Could anyone with enough access permissions import git repo [1] to
>>> subgroup
>>> KDE extras [2] and git repo [3] to subgroup Qt extras [4] and give me
>>> Master level of access to these new repos?
>>>
>>> [1] https://anonscm.debian.org/git/pkg-kde/kde-extras/qtcurve.git
>>> [2]
Hi team,
Could anyone with enough access permissions import git repo [1] to subgroup
KDE extras [2] and git repo [3] to subgroup Qt extras [4] and give me Master
level of access to these new repos?
[1] https://anonscm.debian.org/git/pkg-kde/kde-extras/qtcurve.git
[2]
Hi,
>> Ok. In this case I may suggest you to use workflow similar to one in Debian
>> Perl Group [1]. They do not add extra members to the main group [2], but
>> allow members joining to specific sub-groups (for example, [3]). Though
>> it is only in plans; they have not done the migration
Hi,
>> I think that package maintainers should have a Master level of access
>> to be able to create or to import git repos in the group [1].
>> Al least DDs. See Debian Science Team group [2] at Salsa as example.
>
> Yesterday we decided that, at least for now, only admins will be able to
>
Hi,
> I was wondering if Verdigris would be suitable for this team.
> Here's RFP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886514
>
> It has just reached 1.0,
> and I am thinking about Debian packaging.
> Your team and sponsorship would be very helpful.
I have seen this article [1] long
Hi,
I think that package maintainers should have a Master level of access
to be able to create or to import git repos in the group [1].
Al least DDs. See Debian Science Team group [2] at Salsa as example.
As a side note: could you add small description for the main Debian Qt
and KDE Team group
> We had no replies, so let's keep saturday 13 UTC except someone chimes in.
Do you have a list of questions to discuss?
--
Boris
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
>> This is not mutually exclusive, see [1] as example.
>>
>> [1] https://salsa.debian.org/salsa/support/issues/1
>
> As I understand here is either qa or qa-team, but not both (and this is what
> I had in mind when I wrote the previous mail)
I mean: we could create "qt-kde-team" group ourself and
Hi Lisandro,
> Today I talked with David and wanted to update kdeconnect. But found out that
> we have two separate repos for it.
Thank you for working on this! Bug #794499 is quite annoying despite of
available workaround.
> The original had the source code in it, which is normal considering
Hi everyone,
> So basically we need a way to ensure the Qt 5 stack gets tied together. I can
> think in two possible ways of doing it:
>
> a) Suggested by Adam Majer and improved by Felix Geyer: if package A gets
> built against any qtbase x.y.z lib make it depend upon the version used to get
>
11 matches
Mail list logo
