Signed-off-by: Eric Bélanger
---
cron-jobs/sourceballs |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/cron-jobs/sourceballs b/cron-jobs/sourceballs
index 6553327..0486c48 100755
--- a/cron-jobs/sourceballs
+++ b/cron-jobs/sourceballs
@@ -79,8 +79,13 @@ for repo i
On Tuesday 14 December 2010 03:43:16 Eric Bélanger wrote:
> Signed-off-by: Eric Bélanger
> ---
> cron-jobs/sourceballs |9 +++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/cron-jobs/sourceballs b/cron-jobs/sourceballs
> index 6553327..0486c48 100755
> --- a/cron-
On Tue, 14 Dec 2010 09:55:22 +0100, Andrea Scarpino
wrote:
> Well, I didn't know that I can patch our scripts to enable [kde-unstable]
> support officially. Or better, I didn't think that I can explicitly
> add a [kde-
> unstable] case in that way because we should add a gnome-unstable and a foo-
On Tue, Dec 14, 2010 at 4:32 AM, Pierre Schmitz wrote:
> On Tue, 14 Dec 2010 09:55:22 +0100, Andrea Scarpino
> wrote:
>> Well, I didn't know that I can patch our scripts to enable [kde-unstable]
>> support officially. Or better, I didn't think that I can explicitly
>> add a [kde-
>> unstable] cas
Am 14.12.2010 11:22, schrieb Eric Bélanger:
>> I wont add any hack for a specific repo to the dbscripts. Every repos
>> has to have the repos/$repo-$arch structure.
>>
>
> Andrea: If you don't want to mess up the trunk directory with the kde
> unstable stuff, you could at least have the files in t
On Tuesday 14 December 2010 12:01:14 Thomas Bächler wrote:
> You can create a "trunk-unstable" directory, commit there and still use
> archrelease kde-unstable-{i686,x86_64,any} as usual - afaik the
> directory "trunk" is not hardcoded anywhere.
Unfortunately trunk is hardcoded in archrelease, see:
Am 14.12.2010 13:59, schrieb Andrea Scarpino:
> On Tuesday 14 December 2010 12:01:14 Thomas Bächler wrote:
>> You can create a "trunk-unstable" directory, commit there and still use
>> archrelease kde-unstable-{i686,x86_64,any} as usual - afaik the
>> directory "trunk" is not hardcoded anywhere.
>
On Tue, 14 Dec 2010 14:13:58 +0100, Thomas Bächler
wrote:
> Am 14.12.2010 13:59, schrieb Andrea Scarpino:
>> On Tuesday 14 December 2010 12:01:14 Thomas Bächler wrote:
>>> You can create a "trunk-unstable" directory, commit there and still use
>>> archrelease kde-unstable-{i686,x86_64,any} as usua
- Original message -
> Afaik its old and I thought I had removed it some time ago. Try this:
> http://projects.archlinux.org/devtools.git/commit/?id=5815d639f38ebd8a5622706a18bbfe64f747fd32
Thanks, looks ok. When I back home I'll fix the kde-unstable packages path to
use trunk-unstable.
-
On Tuesday 14 December 2010 15:36:47 Andrea Scarpino wrote:
> Thanks, looks ok. When I back home I'll fix the kde-unstable packages path
> to use trunk-unstable.
Ehm I meant kde-unstable. Anyway everything committed (with archrelease) in
repos/kde-unstable-$arch. And finally I can use db-update no
10 matches
Mail list logo
