SVN commit 1296353 by kossebau:
Move kdesdk/kdeaccounts-plugin to tags/unmaintained/4
This old KABC-based plugin creating a read-only addressbook resource has been
replaced by the new Akonadi-based plugin in kdepim-runtime/resources/kdeaccounts
but this one was forgotten to be removed before.
Mo
On Wednesday, May 23, 2012 19:40:52 Allen Winter wrote:
> This whole thread is confusing me.
>
> Maybe a command line would help?
>
> Is this correct?
> % tar cvf kdefoo-x.y.z.tar
> % xz kdefoo-xy.z.tar
> => resulting in kdefoo-x.y.z.tar.xz
That's fine.
> if not, please tell us what a command
On Wednesday 23 May 2012 1:28:04 PM Wulf C. Krueger wrote:
> Hello Albert et al,
>
> On 23.05.2012 18:58, Albert Astals Cid wrote:
> > The machine i'm generating the tarballs doesn't have pixz so i'll
> > use xz.
>
> Even though it's somewhat coincidental ;): Thank you.
>
> Personally, I think i
On Wednesday, May 23, 2012 18:59:58 Albert Astals Cid wrote:
> Unless someone disagrees i'll give kde-base-artwork it's own tarball, since
> well, it's a toplevel module.
I think it makes sense for its sheer size.
Please do keep in mind that changes in tarball layout cause additional work
for p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Albert et al,
On 23.05.2012 18:58, Albert Astals Cid wrote:
> The machine i'm generating the tarballs doesn't have pixz so i'll
> use xz.
Even though it's somewhat coincidental ;): Thank you.
Personally, I think it would be an excellent idea t
Unless someone disagrees i'll give kde-base-artwork it's own tarball, since
well, it's a toplevel module.
Cheers,
Albert
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
El Dimarts, 22 de maig de 2012, a les 23:48:25, Michael Pyne va escriure:
> Hi all,
>
> I noticed something while we were on the topic of tagging the beta tomorrow
> that I wanted to bring up, which is a concern with tarball generation.
> Specifically, the various parallizeable tarball generators
Sebastian
Change of plans. As per recent discussions with tsdgeos and kde_pepo on
#kde-devel -
They would like to avoid too many new repositories. So, if it's okay with
you we'll keep the nepomuk-kde-config and nepomuk-kde-kio code in
kde-runtime, while the rest can be removed as it is there in n
Does anyone have suggestions on where nepomuk-kde-kio and
nepomuk-kde-config should be placed?
I was thinking under kde-baseaps, but that might not be correct. Any
suggestions?
On Fri, May 18, 2012 at 1:45 AM, Kevin Krammer wrote:
> On Thursday, 2012-05-17, Sebastian Trüg wrote:
> > I think we
