I just updated to 4.0.82 inlcuding some packaging improvements. (no i686
packages this time; I don't use them anyway)
On Tue, 2008-06-03 at 08:40 +0200, Pierre Schmitz wrote:
> Thanks for the hint. I'll add replaces=(gnome) and conflicts=(gnome)
> to kde
> packages.
>
> Just kidding; I'll talk to Jan what could be done to avoid those
> conflicts; of
> course those files are different.
/etc/ggz.modules looks li
Am Dienstag 03 Juni 2008 06:25:20 schrieb Eric Belanger:
> I went to try out the i686 packages but there are file conflicts:
>
> error: could not prepare transaction
> error: failed to commit transaction (conflicting files)
> kdelibs: /etc/xdg/menus/applications.menu exists in filesystem
> kdegames
On Sat, 31 May 2008, Pierre Schmitz wrote:
On Thursday 29 May 2008 22:43:22 Pierre Schmitz wrote:
Let's create a kde-repo on top of our testing repo and
see how we can package it and manage the transition from kde3.
OK, this was quite some work. I have moved the repo to other/kde-testing. Thi
Am Sonntag 01 Juni 2008 00:38:42 schrieb Aaron Griffin:
> It could have been easier if you used the dbscripts to do this. Like
> Thomas suggested, you could do all the work in
> repos/kde-testing-i686/, commit everything, scp to
> ~staging/kde-testing/add/ (see Dan's repopkg patch for a helper
> sc
On Sat, May 31, 2008 at 2:16 PM, Pierre Schmitz <[EMAIL PROTECTED]> wrote:
> On Thursday 29 May 2008 22:43:22 Pierre Schmitz wrote:
>> Let's create a kde-repo on top of our testing repo and
>> see how we can package it and manage the transition from kde3.
>
> OK, this was quite some work. I have mo
On Thursday 29 May 2008 22:43:22 Pierre Schmitz wrote:
> Let's create a kde-repo on top of our testing repo and
> see how we can package it and manage the transition from kde3.
OK, this was quite some work. I have moved the repo to other/kde-testing. This
way it should be found on some mirrors so
Pierre Schmitz schrieb:
On Thursday 29 May 2008 22:57:06 Aaron Griffin wrote:
And the db-scripts are made to do just this!
But this depends on the svn tree, right? ATM I don't wont to mess up with the
repo. Think about a new KDE3 release before KDE4 is ready to use.
What about using a git r
On Thursday 29 May 2008 22:57:06 Aaron Griffin wrote:
> And the db-scripts are made to do just this!
But this depends on the svn tree, right? ATM I don't wont to mess up with the
repo. Think about a new KDE3 release before KDE4 is ready to use.
What about using a git repo for this and put the re
On Thu, May 29, 2008 at 4:03 PM, Dan McGee <[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 3:57 PM, Aaron Griffin <[EMAIL PROTECTED]> wrote:
>> On Thu, May 29, 2008 at 3:43 PM, Pierre Schmitz <[EMAIL PROTECTED]> wrote:
>>> My suggestion would be: Let's create a kde-repo on top of our testing r
On Thu, May 29, 2008 at 3:57 PM, Aaron Griffin <[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 3:43 PM, Pierre Schmitz <[EMAIL PROTECTED]> wrote:
>> My suggestion would be: Let's create a kde-repo on top of our testing repo
>> and
>> see how we can package it and manage the transition from kd
On Thu, May 29, 2008 at 3:43 PM, Pierre Schmitz <[EMAIL PROTECTED]> wrote:
> My suggestion would be: Let's create a kde-repo on top of our testing repo and
> see how we can package it and manage the transition from kde3. I have setup
> such a repo as an example:
And the db-scripts are made to do j
Hey guys,
I have made some packages of the first beta release of KDE 4.1. I had to
update some dependencies and put them into [testing]. I also cleaned up the
QT package. Due to a file conflict with kdelibs-4 I disabled phonon.
The PKGBUILDs are built from scratch and I tried to keep it as simp
13 matches
Mail list logo
