Re: KDE 4.1.4 (try #1) uploaded

On Tue, Jan 6, 2009 at 11:01 PM, Dirk Mueller muel...@kde.org wrote: Hi, I just finished uploading the initial set of KDE 4.1.4 tarballs. Please let me know of any issues. Planned announcement is next week Tuesday. kdelibs' content: documentation eu is it mr README regards, Harald

Re: KGoldrunner silenced in KDE 4.6 RC1

in touch with anyone who could help? If you post some additional information to the kde-mm list I am sure we can get to the bottom of this and fix the problem :) regards -- Harald Sitter Phonon Developer ___ release-team mailing list release-team@kde.org

Re: No more release schedules.

On Friday 10 June 2011 01:22:00 Kevin Kofler wrote: On Friday 10 June 2011, Scott Kitterman wrote: Kevin Kofler kevin.kof...@chello.at wrote: OK, since a lot of context apparently got lost during the message passing, let me just state my (personal) position clearly: What I think is

Re: RFC: Release Management Going Forward

On Friday 10 June 2011 09:23:43 Aaron J. Seigo wrote: On Friday, June 10, 2011 03:49:21 Harald Sitter wrote: More frequent releases does not translate to more frequent adoption though, so I doubt it would have much affect for distros and 3rd party developers i agree that this is the case

Re: Missing french documentation for kstars in 4.8.3/4.8.4

On Tue, Jun 5, 2012 at 1:16 AM, Albert Astals Cid aa...@kde.org wrote: Yes, I understand that what you suggest would be the desired thing, but unfortunately due to how our docbook generation system works it's not easy/trivial to do so. Wouldn't it simply be an svn revert? HS

Re: ALERT: KDElibs (at least) 4.8.4 is actually 4.8.80+

On Sun, Jun 10, 2012 at 8:49 PM, Wulf C. Krueger philant...@exherbo.org wrote: No, you don't. You just told me you expect *us* to do *your* QA, your *testing* and, ideally, sort *your* stuff out (including, according to some, informing individual project leads). Disrespectful. *us* and *you*

Re: Moving strigi-multimedia to unmaintained

On Sun, Jun 17, 2012 at 11:05 PM, Albert Astals Cid aa...@kde.org wrote: Code doesn't compile (it's protected by a cmake check) Hasn't had any meaningful commit since 2007 Anyone against the move? Nope. Then again I am not even sure what it is supposed to do, nor if it ever did anything ...

Re: polkit-kde-kcmmodules editing /usr

On Thu, Oct 25, 2012 at 9:47 AM, Andrea Scarpino and...@archlinux.org wrote: But on Arch Linux we have the same kind of issue with KDM; it stores the configs in /usr/share/config/kdm. How do you handle that? http://goo.gl/WEHqD ___ release-team

Re: Patch needed in phonon-backend-gstreamer for fixing a bug in Dolphin and other players

On Thu, Nov 29, 2012 at 3:32 PM, Rex Dieter rdie...@math.unl.edu wrote: On 11/28/2012 06:01 PM, Manuel Tortosa Moreno wrote: This patch: https://projects.kde.org/**projects/kdesupport/phonon/**phonon-https://projects.kde.org/projects/kdesupport/phonon/phonon-

KDE's opinion on SC 4.13 for Kubuntu 14.04

Alohas, Kubuntu could pick up 4.13 for the 14.04 release (due April 17th). However there are some concerns because of how the respective release schedules line up [1]. - to land 4.13.0 we'd have to upload to Kubuntu as soon as the tarballs become available as we are going into release freeze on

Re: KDE's opinion on SC 4.13 for Kubuntu 14.04

On Mon, Jan 20, 2014 at 1:42 PM, Sebastian Kügler se...@kde.org wrote: So I'd go with 4.13. ^ That. Thanks for the input. Most comments on the Kubuntu side also were in favor of it. We will go with 4.13 \o/ (assuming nothing goes wrong) HS ___

kde-l10n-* pre-releases rolled from wrong l10n branch

Aloha It was brought to my attention that both czech and slovenian language tars apparently do not result in a fully translated plasmas for 4.12.95 (e.g. [1]). Looking at the cs tar I see no launcher po but a kickoff po: ~/tmp/kde-l10n-cs-4.12.95/messages/kde-workspace  ls *kickoff*

Re: kde-l10n-* pre-releases rolled from wrong l10n branch

On Thu, Mar 27, 2014 at 10:46 AM, Albert Astals Cid aa...@kde.org wrote: That is known and will be fixed for the final release of 4.13 Cheers, Albert P.S: I thought noone would realize, good work :D lol :P ___ release-team mailing list

Re: KDE Frameworks Release Cycle

ahoy, quick question that just when we discussed this in kubuntu: On Sun, Apr 27, 2014 at 3:15 PM, David Faure fa...@kde.org wrote: * Everything is developed in master, so each release will contain a few new features and bugfixes; Of course, going with this type of cycle comes with some

Re: Fwd: Re: Fwd: KDE Frameworks Release Cycle

On Wed, Apr 30, 2014 at 6:19 PM, Raymond Wooninck tittiatc...@gmail.com wrote: So with frameworks I think we can compromise with something like last 5 releases and turn off auto reporting for anything older than that (this is just an example). So in other words, this means that you are

Re: Fwd: Re: Fwd: KDE Frameworks Release Cycle

On Thu, May 1, 2014 at 1:33 AM, Michael Pyne mp...@kde.org wrote: Also ideally, we should break with this tendency of upstream/downstream and you should become upstream, I would love to see opensuse (and others) keeping the release you picked maintained in a branch. I think this is wishful

Re: Fwd: Re: Fwd: KDE Frameworks Release Cycle

, yes, a fork) On Thu, May 1, 2014 at 8:27 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Harald Sitter wrote: On Thu, May 1, 2014 at 1:33 AM, Michael Pyne mp...@kde.org wrote: Also ideally, we should break with this tendency of upstream/downstream and you should become upstream

Re: bugzilla verion numbers

On Fri, Jul 11, 2014 at 12:06 PM, Jonathan Riddell j...@jriddell.org wrote: Hola, I'm wondering how version numbers get updated in bugs.kde.org for KDE SC releases and Frameworks etc. Are they really added manually or is there a scriptable way to add them? I'm looking to add 5.0.0 version

Re: Review Request 119915: Plasma release scripts to use Ki18n's PO installation macro

doesn't pass for me: 1) Failure: TestL10n#test_get_po [./ts_l10n.rb:87]: Failed assertion, no message given. It appears that the test needs updating since we don't create a million cmakelists.txt anymore. - Harald Sitter On Aug. 24, 2014, 8:52 p.m., Chusslove Illich wrote

Re: Review Request 119915: Plasma release scripts to use Ki18n's PO installation macro

On Aug. 25, 2014, 7:02 a.m., Harald Sitter wrote: lib/kdel10n.rb, line 242 https://git.reviewboard.kde.org/r/119915/diff/1/?file=307343#file307343line242 random nitpicking: could use @languages.empty? instead of a new var Chusslove Illich wrote: The check should depend

Re: Review Request 119915: Plasma release scripts to use Ki18n's PO installation macro

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119915/#review65628 --- Ship it! - Harald Sitter On Aug. 30, 2014, 6:50 p.m

Re: KF 5.3.0

On Mon, Oct 6, 2014 at 7:52 AM, David Faure fa...@kde.org wrote: On Saturday 04 October 2014 23:16:35 Nicolás Alvarez wrote: 2014-10-04 18:41 GMT-03:00 David Faure fa...@kde.org: After some compilation fixes (related to .po files and the new kf5_entry.desktop files in kconfigwidgets), I

Fwd: DrKonqi backtrace generation broken with gdb 7.8

FYI, apparently it silent bounced... -- Forwarded message -- From: Bhushan Shah bhus...@gmail.com Date: Fri, Oct 10, 2014 at 11:46 AM Subject: Fwd: DrKonqi backtrace generation broken with gdb 7.8 To: sit...@kde.org -- Forwarded message -- From: Bhushan Shah

Re: DrKonqi backtrace generation broken with gdb 7.8

On Fri, Oct 10, 2014 at 11:47 AM, Harald Sitter sit...@kde.org wrote: FYI, apparently it silent bounced... -- Forwarded message -- From: Bhushan Shah bhus...@gmail.com Date: Fri, Oct 10, 2014 at 11:46 AM Subject: Fwd: DrKonqi backtrace generation broken with gdb 7.8 To: sit

Re: Plasma 5.1 beta tars

On Fri, Oct 10, 2014 at 12:50 PM, Jonathan Riddell j...@jriddell.org wrote: On Fri, Sep 26, 2014 at 12:56:03AM +0200, šumski wrote: On Friday 26 of September 2014 00:28:46 Jonathan Riddell wrote: Plasma 5.1 Beta tars are up at http://starsky.19inch.net/~jr/tmp/plasma-5.0.95/ and coming

Phonon 4.8.1

Ahoy, We've just released the first patch release for Phonon 4.8. It fixes a potential crash on failing to load a backend which could crash the configuration UIs on load and prevent changing to a working backend. For a detailed changelog and download information please head to our releases page:

Re: KDE Applications 14.12.2 ready for packagers

On Mon, Feb 2, 2015 at 4:13 PM, Eric Hameleers al...@slackware.com wrote: On Fri, 30 Jan 2015, Albert Astals Cid wrote: Usual location, I'm at FOSDEM this weekend so it may happen that if you guys find some issue (hopefully not) it'll have to wait until monday for me to act on it. Cheers,

Re: 5.2.1 tars for packagers

On Thu, Feb 19, 2015 at 11:16 PM, Heiko Becker heire...@exherbo.org wrote: Hi Jonathan, On 19.02.2015 18:00, Jonathan Riddell wrote: 5.2.1 tars are up on depot for packagers Harald has been lovely and done a lot of work on releaseme which makes the tars, please check over for regressions.

[okteta] [Bug 345010] kasten soversion got lowered in Apps 15.04 and master

https://bugs.kde.org/show_bug.cgi?id=345010 Harald Sitter sit...@kde.org changed: What|Removed |Added CC||release-team@kde.org -- You

Re: Wrong prefix in KPeople libraries

On Wed, Mar 11, 2015 at 4:31 PM, Aleix Pol aleix...@kde.org wrote: I've just been pointed out by kubuntu packagers that we're missing the KF5 prefix (i.e. the library is called libKPeople.so instead of libKF5People.so). This patch [1] addresses that but it's obviously a BIC. I see these

Re: Re: Re: 5.2.1 tars for packagers

On Tue, Feb 24, 2015 at 2:46 PM, Anke Boersma d...@kaosx.us wrote: FWIW, no such regressions here with Plasma 5.2.1 Krunner/Alt-F2 works as should, focus of opened apps with krunner is correct. The hotkey issue could totally be a missing kglobalaccel daemon actually. What with it having moved

Re: KDE Applications 15.04 Beta 1 is out

On Thu, Mar 5, 2015 at 8:13 PM, Albert Astals Cid aa...@kde.org wrote: If anyone starts filling in https://community.kde.org/Applications/15.04_Release_Notes in a similar note as https://community.kde.org/Applications/14.12_Release_Notes great, otherwise i'll try to do it tomorrow evening or

Re: Future frameworks releases

On Sun, Jun 7, 2015 at 4:28 PM, David Faure fa...@kde.org wrote: Hello packagers, The thread Versioning of Frameworks on kde-frameworks-devel has led to the idea that some future frameworks (coming from the kdepim world) would not be part of every Frameworks release, and would have their own

Re: kopete and kdepimlibs in apps 15.08

On Tue, Aug 18, 2015 at 10:33 AM, Pali Rohár pali.ro...@gmail.com wrote: CCing R.Harish Navnit, GSoC student who porting kopete to KF5. I think you forgot that ;) On Tuesday 18 August 2015 09:53:44 Harald Sitter wrote: Now looking at the source kdepimlibs is used for two things in kopete: 1

kopete and kdepimlibs in apps 15.08

Hellos, So, I just noticed that kopete has: CMakeLists.txt:find_package(KdepimLibs REQUIRED) we do however not have a kdepimlibs (qt4) in Applications 15.08 so that requirement cannot really be met anymore. What's worse: kdepimlibs (qt4) in fact has file overlap with kdepimlibs (qt5); namely

kpart plugins kdelibs vs. frameworks WAS: Re: dolphin branches

I literally have no clue how this thread ended up on kde-multimedia so I am ditching it again from CC Oo On Tue, Aug 11, 2015 at 3:31 PM, Martin Koller kol...@aon.at wrote: On Monday 10 August 2015 19:16:46 Emmanuel Pescosta wrote: So there's no way to get the latest qt4 based version of both

Re: Kamoso 3.0 Release

On Fri, Jul 17, 2015 at 12:01 AM, Jonathan Riddell j...@jriddell.org wrote: Why not version purpose using frameworks style version numbers? Presumably purpose will get moved into frameworks at some point? I am not sure adding to the confusion of what is a framework and isn't is a good idea.

Re: Kamoso 3.0 Release

On Thu, Jul 16, 2015 at 8:46 PM, Aleix Pol aleix...@kde.org wrote: Hi, I'd like to proceed and release Kamoso 3.0 (and Purpose), I came up with this little release schedule. https://userbase.kde.org/Kamoso/3.0#Release_schedule Can somebody +1 it? I just branched 3.0 (1.0 for purpose) and

Re: What's up with dolphin?

On Sun, Jul 19, 2015 at 11:10 PM, Luca Beltrame lbeltr...@kde.org wrote: Il Sun, 19 Jul 2015 21:17:42 +0200, Albert Astals Cid ha scritto: Can anyone confirm that was an oversight and that dolphin.git should be released with KDE Applications 15.08? AFAICS, this was an oversight. Dolphin was

Re: Noto font for Plasma 5.5

On Fri, Oct 16, 2015 at 8:38 PM, Eric Hameleers wrote: > On Fri, 16 Oct 2015, Jonathan Riddell wrote: > >> On Fri, Oct 16, 2015 at 10:38:58AM -0700, Eric Hameleers wrote: >>> >>> On Fri, 16 Oct 2015, Jonathan Riddell wrote: >>> The Plasma team plan to switch to Noto for

Re: how to release oxygen-icons

On Wed, Oct 7, 2015 at 3:20 PM, Rex Dieter wrote: > On 10/07/2015 08:14 AM, Jonathan Riddell wrote: >> >> Oxygen icons is back and updated and due to be part of Plasma 5.5 > > ... >> >> So how to release it now? > > > Silly question, why does it have to be part of plasma

oxygen-icons & plasma-workspace-wallpapers moved to git

As requested by the VDG all artworky bits moved out of svn and into git because git is awesome and all that... # oxygen-icons moved from kdesupport svn to git. Newly available at kde:oxygen-icons. Also going to be in plasma release scope for 5.5 as the VDG wants to continue maintaining the

Re: oxygen-icons & plasma-workspace-wallpapers moved to git

On Wed, Sep 16, 2015 at 1:32 PM, kainz.a wrote: > about the wallpapers. The standard Wallpaper is in kde:breeze should we move > them into plasma-workspace-wallpapers? the question is that the > plasma-workspace-wallpapers are an additional package and the standard > wallpaper

breeze repo to be split into breeze and breeze-icons come plasma 5.5

Some time between now and plasma 5.5 branching we will split the breeze icon theme from the breeze repo to its own breeze-icons repo. HS ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

[frameworks-kio] [Bug 351699] Whereis Share Folder

https://bugs.kde.org/show_bug.cgi?id=351699 Harald Sitter <sit...@kde.org> changed: What|Removed |Added CC||sit...@kde.org --- Comm

Re: tarball signing

On Tue, Jun 7, 2016 at 2:09 PM, Albert Astals Cid wrote: > El dilluns, 6 de juny de 2016, a les 11:39:25 CEST, Sandro Knauß va escriure: >> Hey, >> >> > Well, Albert and I use (the same user on) the same server to make >> > releases. >> > So the private key will have to be on that

reducing amount of bundled kemoticon themes

Hola! I have been talking to Andreas Kainz and we kind of concluded that out of the four kemoticon themes we ship by default two should be kicked out of the framework as they are not needed for operation, increase disk foot print, and litter the emoticon kcm with excess default options. So, we

tarball signing

--verify -q phonon-4.9.0.tar.xz.sig phonon-4.9.0.tar.xz; echo $? gpg: Signature made Don 02 Jun 2016 13:34:35 CEST using DSA key ID 72F23991 gpg: Good signature from "Harald Sitter <apachelog...@ubuntu.com>" [ultimate] Now then. In the grand scheme of things we'd only ship tarballs wit

git tag signing

Hola. It was brought to my attention that at least one linux distribution developer likes to have git tags signed as to have authoritative tags for releases. IIRC this was mostly as a nice-to-have sort of thing, so this isn't terribly important I'd say. Nevertheless, if you are in the business of

Re: reducing amount of bundled kemoticon themes

It just occured to Riddell that maybe we should move them to kde-apps. Which seems like a swell idea, seeing as putting them in a repo with tarball doesn't really have value of any sort. On Sun, May 29, 2016 at 11:21 AM, Harald Sitter <sit...@kde.org> wrote: > Hola! > > I ha

Re: Fwd: KActivities repository split

On Thu, Feb 18, 2016 at 10:19 PM, Sune Vuorela wrote: > On 2016-02-18, Ivan Čukić wrote: >> The transition period: >> - >> >> The situation with kde:kactivitymanagerd is clear, when making 5.20 >> packages of kde:kactivities,

Re: KDE Frameworks 5.21.0

There was a bug in oxygen-icons5 which will need a new tarball please https://quickgit.kde.org/?p=oxygen-icons5.git=commit=25a83b55f6b2439470bcc5d0963fd2ffa5c086ee On Mon, Apr 4, 2016 at 1:58 PM, David Faure wrote: > On Monday 04 April 2016 08:12:20 David Faure wrote: >> Dear

Re: Hotfix for KWallet in the Frameworks 5.22.0 Release

On Sun, May 8, 2016 at 11:29 PM, Allen Winter wrote: > Howdy, > > Unfortunately my commit b3a95ba0540e01a9bb10db53fc449cc49ce9a9e8 for > the blowfish backend in kwallet broke things. > > See https://bugs.kde.org/show_bug.cgi?id=362805 > > A patch can be found attached to that bug,

Re: New appstream path

the way this change is done still breaks backwards compatibility of ECM. same as when the change was first committed On Mon, Jul 18, 2016 at 12:40 PM, Jonathan Riddell wrote: > I've updated the appstream path from /usr/share/appdata to > /usr/share/metainfo (or your prefix of

Re: tarball signing

On Sun, Aug 7, 2016 at 9:01 PM, David Faure wrote: > On mercredi 15 juin 2016 12:53:23 CEST Andre Heinecke wrote: >> I'm using agent-forwarding through socat for that reason: >> >> Here is an example how I connect to . The last command is >> executed after ssh on the server. >> >>

Re: Plasma 5.7.0 tars

On Thu, Jun 30, 2016 at 4:45 PM, David Edmundson wrote: > *sigh* seems so. Yet plasma-workspace is from the right branch and it's done > by an automated script(!) Haven't we fixed that for beta already? ___ release-team

Re: Plasma 5.7.0 tars

On Mon, Jul 4, 2016 at 2:29 PM, David Edmundson <da...@davidedmundson.co.uk> wrote: > > > On Mon, Jul 4, 2016 at 1:20 PM, Sebastian Kügler <se...@kde.org> wrote: >> >> On Thursday, June 30, 2016 11:06:46 PM CEST Harald Sitter wrote: >> > On Thu

Re: Moving LibKGAPI do KDE Applications

On Sun, Feb 5, 2017 at 9:24 PM, Daniel Vrátil wrote: > Any objections? Elevation from playground requires going through kdereview. HS

excess paperwork when releasing crap?

Aloha, Not sure this is intentional paperwork. But why exactly can I, as maintainer of a project, not change i18n branches of said project without having to file a sysadmin ticket? I mean, it literally says I am a Mister Bossman in that repo [1] ``` $ git push FATAL: W any

Re: excess paperwork when releasing crap?

On Wed, Jan 25, 2017 at 12:45 AM, Ben Cooksley <bcooks...@kde.org> wrote: > On Tue, Jan 24, 2017 at 8:19 PM, Harald Sitter <sit...@kde.org> wrote: >> Aloha, > > Hi Harald, > >> >> Not sure this is intentional paperwork. But why exactly can I, as >> m

Phonon 4.9.1 released

Phonon bugfix release 4.9.1 resolves an issue when building against Qt 5.8.0, which removed a header. Additionally the tarball is now GPG signed. You may find the signature file by appending `.sig` to the tarball URL. The signing key fingerprint is: CB93 8752 1E1E E012 7DA8 0484 3FDB B550 84CC

phonon vlc 0.9.1

Newly released phonon-vlc 0.9.1 fixes some issues on OS X as well as build time compatibility with both older Phonon and newer VLC versions. Also the tarball is now GPG signed. Grab it while it's hot! Signed by same GPG key as phonon tarballs (see phonon 4.9.1 mail)

qca forkery undone

Ahoy ahoy, It was suggested that it may not have been obvious enough when I released QCA 2.1 in 2015. The "new" "regular" QCA tarballs are a replacement for the temporary qca-qt5 fork we had in early 2015. Since we merged the qt5 branch into master (as discussed on frameworks-devel in September

Re: tarball signing

On Sat, Sep 10, 2016 at 1:26 PM, David Faure <fa...@kde.org> wrote: > On lundi 8 août 2016 17:07:41 CEST Harald Sitter wrote: >> 1. Move release tarballing from rosetta to a server/container with >> gpg2.1 > > So, now we are trying this. > > Partial success, s

Re: tarball signing

quick guide https://gist.github.com/apachelogger/4aa69ad0637feedb330b3fadc7adea3a with openssh 6.7 and gpg 2.1 it really is this simple (do note that gpg2.1 needs to be on server and client!) On Mon, Sep 12, 2016 at 12:33 PM, Harald Sitter <sit...@kde.org> wrote: > On Sat, Sep 10, 201

Re: KDE Frameworks 5.27.0

no signatures? :( On Sun, Oct 2, 2016 at 1:29 PM, David Faure wrote: > Dear packagers, > > KDE Frameworks 5.27.0 has been uploaded to the usual place. > > New frameworks: none this time. >syntax-highlighter and prison have been postponed to next month. > > Public release next

Re: KDE Frameworks 5.27.0

On Thu, Oct 6, 2016 at 10:43 PM, David Faure <fa...@kde.org> wrote: > On mardi 4 octobre 2016 12:45:48 CEST Harald Sitter wrote: >> no signatures? :( > > Ah yes I forgot :-) > > Uploaded now, does it look OK ? looking good. thank you :)

Re: Missing Kirigami tarball?

http://download.kde.org/stable/kirigami/ NB: at least discover actually needs a newer kirigami than is available. Marco knows about it and I should hope he does a release soon :) On Wed, Sep 21, 2016 at 5:03 PM, Daniel Vrátil wrote: > Hi, > > trying to build Plasma 5.7.95 for

Re: New kholidays tarball - was - Re: kholidays-16.12.3 depfreeze broken

next time please make that .1 (e.g. kholidays-16.12.3.1.tar.xz) On Thu, Mar 16, 2017 at 12:26 AM, Albert Astals Cid wrote: > El divendres, 10 de març de 2017, a les 14:19:04 CET, > andreas.sturmlech...@gmail.com va escriure: >> master was merged twice into Applications/16.12

Re: KDE Applications 17.04.0 packages available for packagers

to the marble list though. It doesn't really impact the release team. On Mon, Apr 17, 2017 at 10:39 AM, Heinz Wiesinger <ppr...@slackware.com> wrote: > On Monday, 17 April 2017 10:01:29 CEST Harald Sitter wrote: >> On Sun, Apr 16, 2017 at 5:44 PM, Eric Hameleers <al...@slackware.com&g

Re: KDE Applications 17.04.0 packages available for packagers

marble does not maintain their ABIs as such they increase their soversions every feature release. On Sun, Apr 16, 2017 at 5:44 PM, Eric Hameleers wrote: > On Fri, 14 Apr 2017, Albert Astals Cid wrote: > >> At the usual location. >> >> Haven't had time to compile yet, will

releaseme now relying on kdoctools for documentation installation

Hola! As per [1] the release management suite releaseme creates tarballs which rely on kdoctools to process a directory with docbooks inside. Previously releaseme manually constructed CMakeLists suitable for the documentation lineup at hand. This required an excessive amount of fairly poorly

Re: behaviour change in download.kde.org - was - Re: KDE Frameworks 5.36.0

On Tue, Jul 11, 2017 at 12:05 PM, David Faure <fa...@kde.org> wrote: > On mardi 11 juillet 2017 11:52:19 CEST Harald Sitter wrote: >> Seems most likely the directory wasn't actually 750. > > I always create it with > mkdir $dest > chmod o-rx $dest > >

Re: behaviour change in download.kde.org - was - Re: KDE Frameworks 5.36.0

On Mon, Jul 10, 2017 at 11:17 PM, Albert Astals Cid wrote: > El dilluns, 10 de juliol de 2017, a les 11:32:41 CEST, David Faure va > escriure: >> On vendredi 7 juillet 2017 15:51:41 CEST Maximiliano Curia wrote: >> > ¡Hola David! >> > >> > El 2017-07-03 a las 02:18 +0200, David

Re: libkdeaccessibilityclient

Client side api wrapper. I.e. the thing that allows you to access entities exposed via a11y apis. In qt is the "server" side. I.e. exposing entities via a11y apis. On Jul 23, 2017 10:04, "Albert Astals Cid" wrote: > El dissabte, 22 de juliol de 2017, a les 16:57:14 CEST,

Re: Clarification on requirements for a release

On Tue, Jul 4, 2017 at 2:49 AM, Ben Cooksley wrote: > I was the one who made that decision Cool You are not my supervisor.

Re: Clarification on requirements for a release

On Tue, Jul 4, 2017 at 9:41 AM, Ben Cooksley <bcooks...@kde.org> wrote: > On Tue, Jul 4, 2017 at 7:20 PM, Harald Sitter <sit...@kde.org> wrote: >> On Tue, Jul 4, 2017 at 2:49 AM, Ben Cooksley <bcooks...@kde.org> wrote: >>> I was the one who made that deci

Re: Clarification on requirements for a release

On Tue, Jul 4, 2017 at 12:01 PM, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > On Tuesday, 4 July 2017 11:55:24 CEST Harald Sitter wrote: >> On Tue, Jul 4, 2017 at 9:41 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> > On Tue, Jul 4, 2017 at 7:20 PM, Harald

Re: Clarification on requirements for a release

On Tue, Jul 4, 2017 at 1:45 PM, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > On Tuesday, 4 July 2017 12:29:14 CEST Harald Sitter wrote: >> On Tue, Jul 4, 2017 at 12:01 PM, Luigi Toscano <luigi.tosc...@tiscali.it> > wrote: >> > On Tuesday, 4 July 2017

Re: Clarification on requirements for a release

the phab task is marked private. on a general note I do not think this was ever discussed or agreed upon and makes no sense (how the heck is a playground project meant to evolve if it can't do bloody pre releases...). making production releases from playground is not advisable because a)

releaseme new requirement: non-conflicting files on case-insensitive FS/OS

Guten Abend Everyone! To aid with use of our tarballs on Windows and case-insensitive file systems, releaseme now makes sure [1] that the tarballs it generates are safe to use in such contexts. As this is a major problem for pretty much every source tarball as it prevents people from doing

Re: Help kioslave from KF 5.51.0 always crashes

On Sat, Oct 13, 2018 at 9:33 PM David Faure wrote: > > On samedi 13 octobre 2018 20:00:08 CEST Heiko Becker wrote: > > On Samstag, 13. Oktober 2018 19:36:39 CEST, Albert Astals Cid wrote: > > >> with kio-5.51.0 the help kioslave always crashes here, doesn't > > >> matter if I > > >> use it via

Re: qca forkery undone

Guess I'll do a 2.2.0 release unless someone has objections. On Sun, Feb 24, 2019 at 12:23 AM Aleix Pol wrote: > > On Fri, Feb 17, 2017 at 12:58 PM Harald Sitter wrote: > > > > Ahoy ahoy, > > > > It was suggested that it may not have been obvious enough when

Re: KDE Applications rename to KDE Apps Bundle

+1 to what Paul said. On Fri, May 10, 2019 at 8:38 AM Paul Brown wrote: > > On viernes, 10 de mayo de 2019 1:13:49 (CEST) Jonathan Riddell wrote: > > I'd like to propose renaming KDE Applications to KDE Apps Bundle. > > > > We've had discussion on it here https://phabricator.kde.org/T10812 > > >

tar names vs. repo names

Yo! What's our stance on tar names different from the repo names? For simplicity's sake I would argue it should not ever happen, but are there practical reasons where we simply have to have it (other than for legacy naming reasons)? And if we do have a need for this, should we maybe encode the

Source Signing

At akademy we had a poorly attended bof about release artifact signing. Jonathan raised the concern that while we generally sign our stuff we do not actually verify the signatures properly so coverage and reliability is dodgy at best. This largely factors into what Friedrich raised a while ago in

Re: Elisa Music Player and KDE Applications Bundle

On Fri, Sep 27, 2019 at 2:37 PM Nate Graham wrote: > > On 9/27/19 4:55 AM, Harald Sitter wrote:> If there's no objections I'll > move Elisa to kde/multimedia next week. > > Next release would then be 18.12 > +1! 19.12 though? :) Ah yes, indeed it's 2019 already ;)

Re: Elisa Music Player and KDE Applications Bundle

ubation process described > at the link above. That would mean the only 'permission' needed would be > the module coordinator for the module you'd want to join > (kde-multimedia, here). > > So the question is "who's the coordinator"... and I'm not entirely sure! > I think

[sysadmin/repo-metadata] projects/kde/kdemultimedia/elisa: move elisa from extragear to kdemultimedia

Git commit aa82b36fa41524db4b7c50622ed46ccdd322a6c5 by Harald Sitter. Committed on 30/09/2019 at 08:26. Pushed by sitter into branch 'master'. move elisa from extragear to kdemultimedia as agreed upon on the release, mm and elisa mailing lists. @i18n: Please move translations accordingly

anyone using releaseme module releasing

Quick question: anyone using releaseme to release all repos of a module? https://bugs.kde.org/show_bug.cgi?id=420501 e.g. ./tarme.rb --version 1 --origin trunk kde/workspace The feature was originally intended to batch release plasma, but because repos can move between modules it quickly turned

Re: anyone using releaseme module releasing

On Fri, Apr 24, 2020 at 11:46 AM Jonathan Riddell wrote: > > I'm not using it. > > And it would be worth querying if the modules in repo-metadata are useful at > all beyond playground, kdereview, stuff-we-care-about and unmaintained. > Currently there's several modules in the

Re: Plasma 5.20 tars

On 08.10.20 18:59, Jonathan Riddell wrote: > Tars are up for Plasma 5.20 for packages to package. Release due on Tuesday > > Jonathan > Please respin plasma-disks up to cab4513c3886e62ced9079cd1159ab89f52ba7a6 Merci HS

Re: Merge tags in master branch?

Hej On 23.11.20 16:11, Bhushan Shah wrote: > Hello, > > So I have one question regarding the how we do the framework versioning. > Namely the tags, > > So currently some packages have a versioned tags on their master branch, > > i.e > > karchive: > > ➜ git describe > v5.76.0-1-g7304c28 > >

Re: KDE Gear 21.04.2 packages available for packagers

On Tue, Jun 8, 2021 at 2:57 PM Luigi Toscano wrote: > > Heiko Becker ha scritto: > > On Tuesday, 8 June 2021 13:27:08 CEST, Antonio Rojas wrote: > >> kturtle fails to build here: > >> > >> file:///usr/share/kf5/kdoctools/customization/entities/l10n.entities:530: > >> warning: failed to load

Re: Including LayerShellQt in Plasma in time for 5.22

- I'm like a broken record at this point: some of the cmake files and the json file lack licensing details. please run `reuse lint` to check the list. it's incredibly close to being fully licensed - you include KDEClangFormat but don't actually seem to enable it - along a similar note: the code

Re: The KIPI fate

On Fri, Apr 15, 2022 at 12:22 PM Albert Astals Cid wrote: > > In December KIPI support was removed from gwenview and spectacle with this > commit message > > > > Drop KIPI support > > KIPI offers export functionality for various external services > > However it has been

Re: The KIPI fate

On Sun, Apr 17, 2022 at 12:46 PM Albert Astals Cid wrote: > > El divendres, 15 d’abril de 2022, a les 13:42:43 (CEST), Harald Sitter va > escriure: > > On Fri, Apr 15, 2022 at 12:22 PM Albert Astals Cid wrote: > > > * "severly lacks UI polish" *SO WHAT* &

Re: Old versions of our software in Bugzilla

On Tue, Sep 6, 2022 at 11:41 PM Nate Graham wrote: > In the medium term, I would like to extend the bugzilla bot to post a > comment on bug reports filed against old unsupported versions > recommending that the reporter instead ask their distro for support. Needs a blurb for starters :) Code

Re: KDE Frameworks 5.98.0

Hey David, It'd be lovely if you could respin kio to include https://invent.kde.org/frameworks/kio/-/commit/a9c3fc3caf8ff5e57f0dec81265911529f7c8b50 It works around a fairly aggressive crasher with the http worker. Thanks HS

Re: releases driven through invent?

On Fri, Oct 21, 2022 at 10:52 AM Antonio Rojas wrote: > > Hi, > > > - new releaseme program; run with `--version 1.0.0 --ref master > > plasma-workspace` > > - tells invent to make a release with tag v1.0.0.0 (the terminal zero > > is managed by the program? through inspecting existing tags) > >

  1   2   >