Re: d-i repo at dillon

[Cyril Brulebois]

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 with 'origin/master'.
| Changes not staged for commit:
|   modified:   ../../scripts/etc/cron/crontab
| 
| no changes added to commit
| Username for 'https://salsa.debian.org': ^C

Let's look at ~/.gitconfig:
| [url "git://git.debian.org/d-i/"]
| insteadOf = git+ssh://git.debian.org/git/d-i/
| [url "git+ssh://git.debian.org/git/d-i/"]
| pushInsteadOf = git+ssh://git.debian.org/git/d-i/

→ git.debian.org is gone, so removed.

| [user]
| name = D-I role
| email = debian-boot@lists.debian.org
| [http]
| sslcapath=/etc/ssl/ca-debian
| sslcainfo=/etc/ssl/ca-debian/ca-certificates.crt
| [push]
| default = matching
| [url "g...@salsa.debian.org:"]
| pushInsteadOf = https://salsa.debian.org/

→ Duplicated in a different way below, so removed.

| [url "https://salsa.debian.org/installer-team/;]
| insteadOf = g...@salsa.debian.org:installer-team/

→ This one seems responsible for the SSH→HTTPS replacement when trying
  to git push…

| [url "g...@salsa.debian.org:installer-team/"]
| pushInsteadOf = https://salsa.debian.org/installer-team/



Interactively, I'm seeing the same issue anyway:
| d-i@dillon:~/trunk$ git push -n
| Username for 'https://salsa.debian.org': ^C

Commenting out the insteadOf bit leads to:
| d-i@dillon:~/trunk$ vi ~/.gitconfig 
| d-i@dillon:~/trunk$ GIT_TRACE=1 git push -n
| 21:09:37.847733 git.c:371   trace: built-in: git 'push' '-n'
| 21:09:37.851080 run-command.c:350   trace: run_command: 'ssh' 
'g...@salsa.debian.org' 'git-receive-pack '\''installer-team/d-i.git'\'''
| ^C

Not exactly sure how to best fix this…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: d-i repo at dillon

[Holger Wansing]

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 always did it exactly this way.

> Check both .gitconfig and .ssh/config, as I've set up a specific key
> for salsa. Maybe latest changes to .gitconfig (ISTR you tweaked the
> git-setup script lately) interfer with the ssh configuration?

No, I did not touch some of those files.
And looks fine to me.


Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Cyril Brulebois]

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 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

Check both .gitconfig and .ssh/config, as I've set up a specific key
for salsa. Maybe latest changes to .gitconfig (ISTR you tweaked the
git-setup script lately) interfer with the ssh configuration?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: How to make git push quiet? [ Re: d-i repo at dillon ]

[Henrique de Moraes Holschuh]

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 present
> Error in a GIT operation at packages/po dir, please investigate
> d-i@dillon:~/trunk$

Add files that are to *always* be untracked to a .gitignore file,
perhaps?

-- 
  Henrique Holschuh

Re: d-i repo at dillon

[Holger Wansing]

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 ; else 
> > clean ; fi
> 
> Thank you for your very detailed explanation!
> 
> First I will try to get it running with above (minimalist) variant.

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.

Remaining points are:
- authentication does not work non-interactively (?)
- script currently does not check for git errors


Holger

-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Holger Wansing]

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 `foo` does produce output
> then the shell will attempt to execute that and use the resulting exit
> code.
> 
> These just run true or false and take the output:
> 
>$ dash -c 'if true ; then echo YES ; else echo NO ; fi'
>YES
>$ dash -c 'if false ; then echo YES ; else echo NO ; fi'
>NO
> 
> These run true or false, see the output is "" and so use the exit code:
> 
>$ dash -c 'if $(true) ; then echo YES ; else echo NO ; fi'
>YES
>$ dash -c 'if $(false) ; then echo YES ; else echo NO ; fi'
>NO
> 
> These run `echo` (which always succeeds) then runs the resulting "true"
> or "false" and uses the exit code:
> 
>$ dash -c 'if $(echo true) ; then echo YES ; else echo NO ; fi'
>YES
>$ dash -c 'if $(echo false) ; then echo YES ; else echo NO ; fi'
>NO
> 
> This runs `echo` (which always succeeds) then tries to run the
> resulting "foo" and fails because that isn't a command:
> 
>$ dash -c 'if $(echo bar) ; then echo YES ; else echo NO ; fi'
>dash: 1: bar: not found
>NO
> 
> `git status` outputs nothing when the tree is clean, and I think the
> `$($git status -s -uno $DI_COPY/packages/po)` case uses that to succeed
> on a clean tree, however if the tree was dirty you'd get the "not
> found" stuff for something relating to the output.
> 
>$ git status -s -uno build/Makefile
>$ echo $?
>0
>$ dash -c 'if $(git status -s -uno build/Makefile ) ; then echo CLEAN ; 
> else echo DIRTY ; fi'
>CLEAN
>$ echo "FOO" >> build/Makefile
>$ git status -s -uno build/Makefile
>M build/Makefile
>$ echo $?
>0
>$ dash -c 'if $(git status -s -uno build/Makefile ) ; then echo CLEAN ; 
> else echo DIRTY ; fi'
>dash: 1: M: not found
>DIRTY
> 
> Notice that the original svn version had a `| grep -q ^C` which was
> checking if any line started with a "C" (for Changed I suppose),
> produced no output (`-q`) but exited with an error code reflecting the
> presence of any lines. You could do something similar but you'd need to
> check for more than M (modified) since git status has a variety of
> error codes, including (A)dded, (D)eleted, (R)enamed etc.
> 
> `git status` doesn't seem to have an option which makes the error code
> reflect the dirtiness. In the past I've used:
> 
># Update cache, otherwise files which have an updated
># timestamp but no actual changes are marked as changes
># because `git diff-index` only uses the `lstat` result and
># not the actual file contents. Running `git update-index
># --refresh` updates the cache.
>git update-index -q --refresh
>if git diff-index --quiet HEAD -- path/to/something ; then clean ;
>else dirty ; fi
> 
> (--quiet enable --exit-code which makes the exit status meaningful).
> 
> 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 ; else 
> clean ; fi

Thank you for your very detailed explanation!

First I will try to get it running with above (minimalist) variant.


Holger

-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Ian Campbell]

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 $git foo bar; then … fi
> > 
> > However, with this simplified variant it fails. So I left it as is
> for now.
> 
> 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 `foo` does produce
> output
> then the shell will attempt to execute that and use the resulting
> exit
> code.
> 
> These just run true or false and take the output:

Should be "These just run true or false and use the exit code".

BTW, it's worth mentioning that `true` and `false` here are actually
`/bin/{true,false}` i.e. literal commands which return the appropriate
exit code that the shell `fork`s and `exec`s. There's no shell syntax
magic[*] going on here where `true` and `false` are somehow parsed
specially.

Ian.

[*] technically `true` and `false` might be shell builtins for
performance reasons (and it looks like with `dash` `true` is but
`false` isn't). However logically they can be treated as external
commands without special handling. To be unambiguous you could rerun
all the examples using the explicit /bin/true etc versions directly.

>$ dash -c 'if true ; then echo YES ; else echo NO ; fi'
>YES
>$ dash -c 'if false ; then echo YES ; else echo NO ; fi'
>NO

Ian.

Re: d-i repo at dillon

[Ian Campbell]

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 fails. So I left it as is for now.

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 `foo` does produce output
then the shell will attempt to execute that and use the resulting exit
code.

These just run true or false and take the output:

   $ dash -c 'if true ; then echo YES ; else echo NO ; fi'
   YES
   $ dash -c 'if false ; then echo YES ; else echo NO ; fi'
   NO

These run true or false, see the output is "" and so use the exit code:

   $ dash -c 'if $(true) ; then echo YES ; else echo NO ; fi'
   YES
   $ dash -c 'if $(false) ; then echo YES ; else echo NO ; fi'
   NO

These run `echo` (which always succeeds) then runs the resulting "true"
or "false" and uses the exit code:

   $ dash -c 'if $(echo true) ; then echo YES ; else echo NO ; fi'
   YES
   $ dash -c 'if $(echo false) ; then echo YES ; else echo NO ; fi'
   NO

This runs `echo` (which always succeeds) then tries to run the
resulting "foo" and fails because that isn't a command:

   $ dash -c 'if $(echo bar) ; then echo YES ; else echo NO ; fi'
   dash: 1: bar: not found
   NO

`git status` outputs nothing when the tree is clean, and I think the
`$($git status -s -uno $DI_COPY/packages/po)` case uses that to succeed
on a clean tree, however if the tree was dirty you'd get the "not
found" stuff for something relating to the output.

   $ git status -s -uno build/Makefile
   $ echo $?
   0
   $ dash -c 'if $(git status -s -uno build/Makefile ) ; then echo CLEAN ; else 
echo DIRTY ; fi'
   CLEAN
   $ echo "FOO" >> build/Makefile
   $ git status -s -uno build/Makefile
   M build/Makefile
   $ echo $?
   0
   $ dash -c 'if $(git status -s -uno build/Makefile ) ; then echo CLEAN ; else 
echo DIRTY ; fi'
   dash: 1: M: not found
   DIRTY

Notice that the original svn version had a `| grep -q ^C` which was
checking if any line started with a "C" (for Changed I suppose),
produced no output (`-q`) but exited with an error code reflecting the
presence of any lines. You could do something similar but you'd need to
check for more than M (modified) since git status has a variety of
error codes, including (A)dded, (D)eleted, (R)enamed etc.

`git status` doesn't seem to have an option which makes the error code
reflect the dirtiness. In the past I've used:

   # Update cache, otherwise files which have an updated
   # timestamp but no actual changes are marked as changes
   # because `git diff-index` only uses the `lstat` result and
   # not the actual file contents. Running `git update-index
   # --refresh` updates the cache.
   git update-index -q --refresh
   if git diff-index --quiet HEAD -- path/to/something ; then clean ;
   else dirty ; fi

(--quiet enable --exit-code which makes the exit status meaningful).

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 ; else 
clean ; fi

These explicitly check whether the output of the status command was
empty (the -z check, meaning clean) or non-empty (the -n check, meaning
dirty).

Ian.

Re: How to make git push quiet? [ Re: d-i repo at dillon ]

[Holger Wansing]

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.
> 
> However, when I run it agagin now, it fails on GIT error, because there is
> nothing to commit, and GIT seems to not return cleanly because of some
> untracked files (like .l10n-sync.log).
> 
> I tried to make "git push" quiet with -q, but the error persists.
> 
> 
> What can be done about this?

Some output, how it fails:

[...]
- zh_CN
  - Merge sublevel PO files into master PO file and update...
  - Merge with template.pot for sublevel 1...
.. done.
  - Merge with template.pot for sublevel 2...
.. done.
  - Merge with template.pot for sublevel 3...
 
done.
  - Merge with template.pot for sublevel 4...
. done.
  - Merge with template.pot for sublevel 5...
... done.
- zh_TW
  - Merge sublevel PO files into master PO file and update...
  - Merge with template.pot for sublevel 1...
.. done.
  - Merge with template.pot for sublevel 2...
.. done.
  - Merge with template.pot for sublevel 3...
... 
done.
  - Merge with template.pot for sublevel 4...
. done.
  - Merge with template.pot for sublevel 5...
.. done.
Commit all general PO/POT files to GIT... done.
On branch master
Your branch is up-to-date with 'origin/master'.
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 present
Error in a GIT operation at packages/po dir, please investigate
d-i@dillon:~/trunk$


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

How to make git push quiet? [ Re: d-i repo at dillon ]

[Holger Wansing]

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.

However, when I run it agagin now, it fails on GIT error, because there is
nothing to commit, and GIT seems to not return cleanly because of some
untracked files (like .l10n-sync.log).

I tried to make "git push" quiet with -q, but the error persists.


What can be done about this?

Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Holger Wansing]

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 username and my password, but
> in the git log, it now reports username "D-I role". ???)

Ah, wait: will it just work, when the script is fired up by cron?
(Today, I started it manually via "sudo -u d-i".)


Holger

-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Holger Wansing]

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 behaviour, when comparing
> > the old "svn st" lines against the new "git status -s -uno" lines.
> > The relevant diff is this:
> > 
> > 
> >   # Do not accept working on an unclean copy
> > - if $(svn st $DI_COPY/packages/po | grep -q "^C") ; then
> > -   error "$DI_COPY seems to contain some SVN conflict files"
> > + if $($git status -s -uno $DI_COPY/packages/po) ; then
> > +   error "$DI_COPY seems to contain some GIT conflict files"
> > +   error "in packages/po."
> > error "Please fix this before launching the script again"
> > exit 1
> > 
> > 
> > As it seems, the svn st line returns 0, if there _are_ changes in the
> > ../po dir while the new git status line returns 0, if there _are_no_
> > changes.
> > 
> > So I tried to change "if" into "if !" and that seems to work so far,
> > however I would like to receive a short confirmation from coding
> > people for this (/me having no coding skills so far).  It seems to
> > work at least.
> 
> That's exactly what's needed to reverse the check! :)
> 
> 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 fails. So I left it as is for now.


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 username and my password, but
in the git log, it now reports username "D-I role". ???)

Holger




-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Christian PERRIER]

(/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.

Yes, that was the point. We had to use a different version of SVN,
than the one on the machine, in the old days, as l10n-sync was not
always running on a Debian stable machine (it ran on my own machine
for quite some time).

I agree thaat this is probably not so useful nowadays.





signature.asc
Description: PGP signature

Re: d-i repo at dillon

[Cyril Brulebois]

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 against the new "git status -s -uno" lines.
> The relevant diff is this:
> 
> 
>   # Do not accept working on an unclean copy
> - if $(svn st $DI_COPY/packages/po | grep -q "^C") ; then
> - error "$DI_COPY seems to contain some SVN conflict files"
> + if $($git status -s -uno $DI_COPY/packages/po) ; then
> + error "$DI_COPY seems to contain some GIT conflict files"
> + error "in packages/po."
> error "Please fix this before launching the script again"
> exit 1
> 
> 
> As it seems, the svn st line returns 0, if there _are_ changes in the
> ../po dir while the new git status line returns 0, if there _are_no_
> changes.
> 
> So I tried to change "if" into "if !" and that seems to work so far,
> however I would like to receive a short confirmation from coding
> people for this (/me having no coding skills so far).  It seems to
> work at least.

That's exactly what's needed to reverse the check! :)

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

Since $() is used to introduce a command substitution…

(e.g. echo "I'm working on $(hostname)")


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.

> > Don't bother regarding the daily-build-logs.git repository (or
> > whatever it's called), it has gotten corrupted at some point, which
> > I've never found time to investigate, fix, or nuke. It might make
> > sense to re-init it to an empty repository at some point, so that
> > further logs can be injected in it. Just mentioning that so that you
> > don't wonder too much, not trying to put it in your plate.
> 
> I cannot find such repo on salsa.
> Does this need to be created?

I'll handle this (repo+relevant jobs) when I have some spare time, don't
worry about those.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: d-i repo at dillon

[Holger Wansing]

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 dillon needs an git checkout there.
> > 
> > Ok for me to do that?
> 
> Sure thing, and thanks!

Done.
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 against the new "git status -s -uno" lines.
The relevant diff is this:


  # Do not accept working on an unclean copy
- if $(svn st $DI_COPY/packages/po | grep -q "^C") ; then
-   error "$DI_COPY seems to contain some SVN conflict files"
+ if $($git status -s -uno $DI_COPY/packages/po) ; then
+   error "$DI_COPY seems to contain some GIT conflict files"
+   error "in packages/po."
error "Please fix this before launching the script again"
exit 1


As it seems, the svn st line returns 0, if there _are_ changes in the ../po dir
while the new git status line returns 0, if there _are_no_ changes.

So I tried to change "if" into "if !" and that seems to work so far, however
I would like to receive a short confirmation from coding people for this
(/me having no coding skills so far). 
It seems to work at least.

> Don't bother regarding the daily-build-logs.git repository (or whatever
> it's called), it has gotten corrupted at some point, which I've never
> found time to investigate, fix, or nuke. It might make sense to re-init
> it to an empty repository at some point, so that further logs can be
> injected in it. Just mentioning that so that you don't wonder too much,
> not trying to put it in your plate.

I cannot find such repo on salsa.
Does this need to be created?


Holger

-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: d-i repo at dillon

[Cyril Brulebois]

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 to do that?

Sure thing, and thanks!

Don't bother regarding the daily-build-logs.git repository (or whatever
it's called), it has gotten corrupted at some point, which I've never
found time to investigate, fix, or nuke. It might make sense to re-init
it to an empty repository at some point, so that further logs can be
injected in it. Just mentioning that so that you don't wonder too much,
not trying to put it in your plate.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

d-i repo at dillon

[Holger Wansing]

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 weblate commits, that's
> > > why.)
> 
> 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 to do that?


Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/