On Thu, Dec 10, 2020 at 6:00 PM Volker Krause wrote:
>
> The most notable feature gap compared to the official specification is
> probably school holidays, we lack a collection of international data for that
> so far. That only occurs in about 2k out of the 1.8M opening hours expressions
> in the
of completeness. Covering them all would give you the basic building
block for a GUI for systemd more generally.
Additionally, if the "all the wrappers included" approach is taken it
might eventually also be worth considering systemd-homed (portable
user directories backed by encrypted sto
On Mon, Aug 3, 2020 at 11:50 PM Albert Astals Cid wrote:
>
> El dimecres, 29 de juliol de 2020, a les 14:01:07 CEST, Bhushan Shah va
> escriure:
> > At plasma, we are experimenting with new workflow regarding how bugfixes
> > are put on the stable branch [1].
> >
> > # Current workflow
> >
> > -
On Sun, May 10, 2020 at 9:49 AM Ben Cooksley wrote:
>
> Following lengthy discussion in the original thread, it was agreed
> that the original sysadmin proposal of various categories would be
> implemented, with repositories organised according to that structure.
>
> You can find this documented
On Fri, May 1, 2020 at 6:38 AM Nate Graham wrote:
>
> On 4/30/20 5:59 PM, Aleix Pol wrote:
> > El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid
> >> Am I the only person that just has all the repos on the same folder? I
> >> thought it was the common thing to do :?
> >
> > I do too
>
On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk wrote:
>
> >
> > We may need to do on-the-fly conversion of the kde: repo paths if they
> > won't be expressible as 'kde:foo' in the future, but we should have the
> > information needed to do this in kdesrc-build to make
On Sun, Apr 12, 2020 at 1:06 AM Ben Cooksley wrote:
>
> On Sun, Apr 12, 2020 at 11:04 AM Johan Ouwerkerk
> wrote:
> >
> > On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk
> > wrote:
> > >
> > > Yes the only reason why a cleanup script migh
On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk wrote:
>
> Yes the only reason why a cleanup script might be needed is if the
> logical path used to express the repo in dependency information
> changes at the same time. E.g. suppose a `frameworks/kf5foo` gets
> remapped to `fra
On Sat, Apr 11, 2020 at 11:03 PM Michael Pyne wrote:
>
> On Sat, Apr 11, 2020 at 09:25:11PM +0200, Johan Ouwerkerk wrote:
>
> >
> > A cleanup script could be handy. I think kdesrc-build will
> > automatically pick up new repo paths from metadata and that should
> >
On Sat, Apr 11, 2020 at 9:01 PM Nicolás Alvarez
wrote:
>
> How would it work during the "grace period"? Keeping an outdated read-only
> mirror on the old URL? I have done some research into redirecting or
> remapping from the old URL to the new one so we can keep it working for a
> longer
On Sat, Apr 11, 2020 at 8:39 PM Ben Cooksley wrote:
>
> Yes, the hostname git.kde.org will be fully retired as part of this
> transition.
>
> From my understanding kdesrc-build will automatically pick this up
> once we update sysadmin/repo-metadata to show the new repository
> paths.
> This is
On Sat, Apr 11, 2020 at 11:36 AM Ben Cooksley wrote:
>
> Should anyone have any questions on the above, please let us know.
>
Does the migration also mean that `git.kde.org` push URL will be
retired and would need to be remapped to `invent.kde.org`?
In that case, it would be good to have a
On Sat, Apr 11, 2020 at 11:36 AM Ben Cooksley wrote:
>
> To help assist with this, it would be appreciated if all holders of a
> KDE Developer account could please login on our Gitlab instance (at
> https://invent.kde.org/) and ensure they are listed as a 'Developer'
> of the KDE group. You can
On Sun, Mar 22, 2020 at 3:20 AM Ben Cooksley wrote:
>
> We already do have a repository of artifacts :)
> You can find the public view of this at
> https://build-artifacts.kde.org/production/
>
>
> We already use Virtual Machines for both FreeBSD and Windows.
>
> The main problem here is that
On Sat, Mar 21, 2020 at 10:27 PM Ben Cooksley wrote:
>
> On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk
> wrote:
> >
> > On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
> > >
> > > Comments welcome. Please note that simply fixing the dependency
&g
On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
>
> Comments welcome. Please note that simply fixing the dependency
> breakage in this case is not enough to resolve this - there are
> underlying issues which need to be addressed here.
>
> Regards,
> Ben Cooksley
> KDE Sysadmin
I cannot
On Wed, Feb 19, 2020 at 2:09 PM Friedrich W. H. Kossebau
wrote:
>
> Personally I am still unsure what the actual issue is. Why are redirects
> needed at all. Why all the address changes all the time?
>
It is part of the HTTP spec for servers to be able to inform clients
that resource /foo/bar
On Mon, Feb 3, 2020 at 11:27 AM laurent Montel wrote:
>
> Le lundi 3 février 2020, 10:49:10 CET David Edmundson a écrit :
> > I updated:
> >
> > https://community.kde.org/Policies/API_to_Avoid
> >
> > Which had no mention of this.
> >
> > David
>
> I think that you made an error
>
>
in KDE review for over three weeks, so unless there
is urgent new feedback that leaves the question: what is next?
Thanks again for all your help and feedback making Keysmith much better!
Regards,
-Johan Ouwerkerk
On Wed, Dec 18, 2019 at 3:51 PM Bhushan Shah wrote:
>
> Hello everyone!
>
&
On Sat, Dec 28, 2019 at 6:38 PM Friedrich W. H. Kossebau
wrote:
>
> That one is a blocker though to pass kdereview, for what I understand from
> https://community.kde.org/ReleasingSoftware#Sanity_Checklist as linked from
> https://community.kde.org/Policies/Application_Lifecycle#kdereview
>
> At
First of all sorry for the duplicate reply Friedrich. I messed up with
the send button earlier.
Here goes the second try:
>
> Did some usual-nitpick-CMake-code cleanup commit already (things which also
> apply to other new Plasma repos, someone might want to brush over their
> CMakeLists.txt as
First of all: sorry for the duplicate reply Albert. There was a mixup
with the reply button on my end, unfortunately.
Here goes attempt #2:
> I think it'd be good if you used a QVarLengthArray instead of "char
> code[m_pinLength];"
>
Yes that is a known wart. There are a few issues/MRs that
Just one question here: what is the impact on projects in the KDE/
namespace which have only a single maintainer/contributor?
Are we then essentially going to accept that users merge in their own
MRs? And also, how then does that tie in with the expressed preference
for fast-forward only merges
23 matches
Mail list logo
