Re: Adding salsa to our food^w workflow

¡Hola Sandro! El 2017-12-31 a las 15:02 +0100, Sandro Knauß escribió: On Mittwoch, 27. Dezember 2017 14:14:32 CET Lisandro Damián Nicanor Pérez Meyer wrote: El martes, 26 de diciembre de 2017 12:54:22 -03 Boris Pek escribió: Ah! Well, I would like to have some input on the other members of the

Re: Recent changes & dhmk

¡Hola Pino! El 2017-12-29 a las 12:41 +0100, Pino Toscano escribió: I would like to know why you are switching all the packages away from dhmk to "pure debhelper". Sadly, the commit messages do not explain it at all (and they are even hidden from changelog, "Gbp-Dch: Ignore"), and I do not

Re: Fwd: KGlobalAccel regression in latest frameworks release

On September 13, 2017 10:47:18 PM GMT+02:00, "Sandro Knauß" wrote: >Hey, > >i think we also should look at this issue. > >sandro > >-- Forwarded Message -- > >Subject: KGlobalAccel regression in latest frameworks release >Date: Mittwoch, 13. September 2017,

Re: k3b as part of applications

On Monday, 4 September 2017 15:44:18 CEST Maximiliano Curia wrote: > k3b is now part of KDE applications, and as such I think that it would be > better to have the package repository under the same tree as the other KDE > applications. That means migrating the history from svn to git, an

kde4libs and libssl-dev

Hi, With the upload of qt4-x11 4:4.8.7+dfsg-12 (experimental) qt4 now builds against libssl-dev, instead of libssl1.0-dev. Lisandro pinged me by irc to upload a newer kde4libs built against libssl-dev (and the newer qt4 version) in order to test this, but looking at the latests commits, it's

Re: Use of CMAKE_BUILD_TYPE=Debian

¡Hola Jonathan! El 2016-12-12 a las 14:41 +, Jonathan Riddell escribió: I'm wondering if there's still a need for CMAKE_BUILD_TYPE=Debian which gets set on builds which use /usr/share/pkg-kde-tools/lib/kf5_flags It's used by /usr/share/pkg-kde-tools/cmake/DebianABIManager.cmake and

Re: syntax-highlighting repo

¡Hola Harald! El 2016-11-21 a las 09:25 +0100, Harald Sitter escribió: but the repo names follow upstream naming not source naming (attica vs. attica-kf5 etc.) :/ Upstream also mentioned that they were going to rename it, but then they only renamed the content of the tarball. When I renamed

Re: gpgme 1.7.0~ alpha or beta to debian experimental?

(resending on list) Qt and KDE libs are built with -fPIC, which, afaik, is stronger and incompatible with -fPIE, would it be an option to use -fPIC for gpgme? On October 7, 2016 3:48:39 AM GMT+02:00, Daniel Kahn Gillmor wrote: > On Thu 2016-10-06 19:51:57 -0400, Sandro

kmail CVEs and patches

Hi, About: https://www.kde.org/info/security/advisory-20161006-1.txt I tried to backport the CVE-2016-7966 fix commit to kf 5.26 and it didn't apply cleanly, it would be nice if the advisory includes the list of the commits to backport, or maybe a new 5.26.1 kcoreaddons bugfix release.

SDDM in tty1 by default

Hi, I've used sddm in tty1 for a while to test it out (this was sometime ago, things could have changed since). And there were a couple of things that bothered me. - If you start a second session it tries to use tty2. This might slowly eat all your vts, but more importantly is that

Team coordination for kde-extras

On 02/02/16 16:16, Lisandro Damián Nicanor Pérez Meyer wrote: > I won't remove it for now until we clear up this then. I've pinged Kubuntu developers via irc to participate in this discussion, I've changed the subject to reflect the topic of the discussion. > - The shared repos where for the

Re: no time for calligra anymore

On 07/02/16 11:43, Dmitry Shachnev wrote: > On Sun, Feb 07, 2016 at 11:05:53AM +0100, Adrien Grellier wrote: > > Sadly I have not anymore time to dedicate to calligra. The package is not in > > a very good state since a couple of months, I am sorry about that. > > > If someone want to take care of

Re: kgamma - kgamma5

¡Hola Lisandro! El 2015-08-07 a las 12:15 -0300, Lisandro Damián Nicanor Pérez Meyer escribió: On Friday 07 August 2015 13:54:33 Jonathan Riddell wrote: Upstream (me) renamed kgamma tar to kgamma5 because it now has a lower Plasma version number, so I've moved the git repository in debian git

Re: Reg. packaging pam-kwallet for Debian

¡Hola Rahul! El 2014-10-23 a las 05:09 +0530, Rahul Amaram escribió: Totally understand and appreciate this. I didn't think that a package in Ubuntu mainstream would need so much review. Yeah, well, it happens, we are more picky/we aim to have higher quality software (I guess a bit of both).

Re: Reg. packaging pam-kwallet for Debian

¡Hola Rahul! El 2014-10-23 a las 11:44 +0200, Maximiliano Curia escribió: I'm not sure about the socket file in /tmp. The file name is predictable and it's even logged before use... oh, it's never used, mmh. No, it's used in kde-workspace-bin's startkde, to set the session environment

Re: Reg. packaging pam-kwallet for Debian

¡Hola Rahul! El 2014-10-21 a las 01:26 +0530, Rahul Amaram escribió: Apologies for the delay. Had been caught up with some work. Kindly review and upload to Debian. The review process involves checking and fixing the packaging, and checking upstream code for possible errors/incompatibilities

Re: RFC: Moving kubuntu packaging branches to pkg-kde git

¡Hola Philip! El 2014-08-12 a las 21:47 +0200, Philip Muskovac escribió: They don't get ignored, but if one build-dep breaks another the build will just FTBFS instead of dep-wait on the new version. And even scripted retrying of hundreds of builds is not really fun so we dumped

Re: RFC: Moving kubuntu packaging branches to pkg-kde git

¡Hola Rohan! El 2014-07-29 a las 16:10 +0200, Rohan Garg escribió: - master: has the shared packaging and targets the latest upstream (beta?) release (which should really be everything as long as something doesn't cause a problem for the other team) - series (e.g. unstable, utopic):

Re: RFC: Moving kubuntu packaging branches to pkg-kde git

¡Hola Philip! El 2014-08-07 a las 10:39 +0200, Philip Muskovac escribió: Wasn't the whole point of the maintainer change that debian maintainers were grumpy about getting mails from issues in derivatives? Afaik it was for reports reported to the Debian maintainers that were unaware or not