Holger Wansing (2018-06-16):
> Remaining points are:
> - authentication does not work non-interactively (?)
> - script currently does not check for git errors
Running the script manually, I'm seeing:
| Commit all general PO/POT files to GIT... done.
| On branch master
| Your branch is up-to-date
Hi,
Cyril Brulebois wrote:
> Holger Wansing (2018-06-16):
> > Remaining points are:
> > - authentication does not work non-interactively (?)
> > - script currently does not check for git errors
>
> You probably want to check what happens with a shell started as d-i:
>
> $ sudo -u d-i -s
I
Holger Wansing (2018-06-16):
> It works this way.
>
> I have also replaced $git by git.
>
> And I did some tests, if the l10n-sync script works as it should:
> everything looks fine AFAICS.
Thanks!
> Remaining points are:
> - authentication does not work non-interactively (?)
> - script curre
On Sat, 16 Jun 2018, Holger Wansing wrote:
> Untracked files:
> ../../.l10n.lock
> ../../l10n-sync.log
> ../../scripts/dose.tmp/
> ../../scripts/testing-summary/age-policy-dates
> ../../scripts/testing-summary/hints/
>
> nothing added to commit but untracked files pre
Hi,
Holger Wansing wrote:
> Ian Campbell wrote:
> > For perhaps less git magic you could also just write it as:
> >if [ -z "$(git status -s -uno path/to/something)" ] ; then clean ; else
> > dirty ; fi
> > or inversely:
> >if [ -n "$(git status -s -uno path/to/something)" ] ; then dirty
Hi Ian,
Ian Campbell wrote:
> It seems there is an interesting (and new to me, or at least I'd never
> fully appreciated the behaviour) corner case of the `if $(foo); then`
> syntax, which is that if `foo` exits producing no output then its exit
> code is apparently used for the condition. If `fo
On Sat, 2018-06-16 at 10:17 +0100, Ian Campbell wrote:
> On Sat, 2018-06-16 at 08:36 +0200, Holger Wansing wrote:
> > > The original/final lines are a bit strange, though, instead of
> having:
> > >
> > > if $($git foo bar); then … fi
> > >
> > > I suppose it should only be:
> > >
> > > if $
On Sat, 2018-06-16 at 08:36 +0200, Holger Wansing wrote:
> > The original/final lines are a bit strange, though, instead of having:
> >
> > if $($git foo bar); then … fi
> >
> > I suppose it should only be:
> >
> > if $git foo bar; then … fi
>
> However, with this simplified variant it fail
Hi,
Holger Wansing wrote:
> Holger Wansing wrote:
> > > This morning, I performed a l10n-sync run with my latest modifications,
> > > and
> > > it went through so far. But when committing, I had to give username and
>
> My first run this morning was ok, because there were two files to commit.
Hi,
Holger Wansing wrote:
> Hi,
>
> Holger Wansing wrote:
> >
> > This morning, I performed a l10n-sync run with my latest modifications, and
> > it went through so far. But when committing, I had to give username and
My first run this morning was ok, because there were two files to commit.
Hi,
Holger Wansing wrote:
>
> This morning, I performed a l10n-sync run with my latest modifications, and
> it went through so far. But when committing, I had to give username and
> password to commit. What's the way to make it non-interactive?
> (I am somewhat confused: I gave "holgerw" as use
Hi,
Cyril Brulebois wrote:
> Hey,
>
> Holger Wansing (2018-06-15):
> > Some cron jobs still fail. Until the reasons have been investigated, I
> > have disabled those (3) jobs for now.
> >
> > Then I started to test the l10n-sync script.
> > And it turns out, that there is some changed behaviou
(/me still reading this thread in case I can help at some point)
Quoting Cyril Brulebois (k...@debian.org):
> Also wondering if it makes sense to keep $git a variable instead of just
> using git everywhere. Maybe we used to require a specific $svn, but I
> won't be doing any archeology tonight.
Hey,
Holger Wansing (2018-06-15):
> Some cron jobs still fail. Until the reasons have been investigated, I
> have disabled those (3) jobs for now.
>
> Then I started to test the l10n-sync script.
> And it turns out, that there is some changed behaviour, when comparing
> the old "svn st" lines ag
Hi,
Cyril Brulebois wrote:
> Hi,
>
> Holger Wansing (2018-06-14):
> > > I also changed some lines from svn to git (./daily-build-aggregator
> > > and ./daily-build-manager and ./daily-build-overview)
> >
> > They fail, because on dillon, there is still a checkout of the svn
> > repo. So dillo
Hi,
Holger Wansing (2018-06-14):
> > I also changed some lines from svn to git (./daily-build-aggregator
> > and ./daily-build-manager and ./daily-build-overview)
>
> They fail, because on dillon, there is still a checkout of the svn
> repo. So dillon needs an git checkout there.
>
> Ok for me
Hi,
Holger Wansing wrote:
> > > 2.
> > > Above you mention "re-enable cron entries". However, I cannot find any
> > > such
> > > disabled entries.
> > > I assume the l10n-sync process is currently enabled, or am I missing
> > > something?
> > > (I'm planning to test the modified script via some
17 matches
Mail list logo
