[arch-dev-public] [signoff] abs 2.0-2

newer
[arch-dev-public] [signoff] lvm2...

older
[arch-dev-public] TrueCrypt and...

Travis Willard

14 Apr 2008 14 Apr '08

1:26 a.m.

Same as 2.0-1, except: rsync server configurable rsyncd.conf.abs moved to /usr/share/abs

Show replies by date

Dan McGee

14 Apr 14 Apr

3:26 a.m.

On Sun, Apr 13, 2008 at 8:26 PM, Travis Willard wrote:

...

Same as 2.0-1, except:

rsync server configurable rsyncd.conf.abs moved to /usr/share/abs

Tried out 2.0-1 and it looked great, so if this is all that changed, then I'll signoff on functionality. One thought- what happens if you upgrade and don't immediately merge the pacnew, and try to run abs? Is the error message helpful? Otherwise we may want a note on upgrade (for only the first time you go to >=2.0) saying the conf file syntax has changed. -Dan

Pierre Schmitz

6:06 a.m.

Am Montag, 14. April 2008 03:26:01 schrieb Travis Willard:

...

Same as 2.0-1, except:

it does not work for me on x86_64: ==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2] -- archlinux.de

eliott

6:47 a.m.

On 4/13/08, Pierre Schmitz wrote:

...

Am Montag, 14. April 2008 03:26:01 schrieb Travis Willard:

...
Same as 2.0-1, except:

it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

Pierre Schmitz

9:15 a.m.

Am Montag, 14. April 2008 08:47:52 schrieb eliott:

...

...
it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

No, I did not replace abs.conf by abs.conf.pacnew; so there was no rsync-server set. Sorry, my fault. Works now on i686 and x86_64. -- archlinux.de

Travis Willard

15 Apr 15 Apr

3:29 p.m.

On Mon, Apr 14, 2008 at 5:15 AM, Pierre Schmitz wrote:

...

Am Montag, 14. April 2008 08:47:52 schrieb eliott:

...
...
it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

No, I did not replace abs.conf by abs.conf.pacnew; so there was no rsync-server set. Sorry, my fault. Works now on i686 and x86_64.

Hm - I think I'll push this to core tonight, with a nice brief, but descriptive install message explaining the change and urging people to mv abs.conf.pacnew to abs.conf Actually... since abs.conf is the only config file, can I move it straight into /etc, and avoid the issue altogether?

eliott

4:16 p.m.

On 4/15/08, Travis Willard wrote:

...

On Mon, Apr 14, 2008 at 5:15 AM, Pierre Schmitz wrote:

...
Am Montag, 14. April 2008 08:47:52 schrieb eliott:

...
...
it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

No, I did not replace abs.conf by abs.conf.pacnew; so there was no rsync-server set. Sorry, my fault. Works now on i686 and x86_64.

Hm - I think I'll push this to core tonight, with a nice brief, but descriptive install message explaining the change and urging people to mv abs.conf.pacnew to abs.conf

Actually... since abs.conf is the only config file, can I move it straight into /etc, and avoid the issue altogether?

probably just emit a message. People may want to clean up the supfiles too.

Dan McGee

4:27 p.m.

On Tue, Apr 15, 2008 at 11:16 AM, eliott wrote:

...

On 4/15/08, Travis Willard wrote:

...
On Mon, Apr 14, 2008 at 5:15 AM, Pierre Schmitz wrote:

...
Am Montag, 14. April 2008 08:47:52 schrieb eliott:

...
...
it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

No, I did not replace abs.conf by abs.conf.pacnew; so there was no rsync-server set. Sorry, my fault. Works now on i686 and x86_64.

Hm - I think I'll push this to core tonight, with a nice brief, but descriptive install message explaining the change and urging people to mv abs.conf.pacnew to abs.conf

Actually... since abs.conf is the only config file, can I move it straight into /etc, and avoid the issue altogether?

probably just emit a message. People may want to clean up the supfiles too.

Killing a subdir in /etc sounds good to me (seems dumb if we only have one file in it). Of course, don't do this if there is any chance of needing that subdir again. -Dan

eliott

4:46 p.m.

On 4/15/08, Dan McGee wrote:

...

On Tue, Apr 15, 2008 at 11:16 AM, eliott wrote:

...
On 4/15/08, Travis Willard wrote:

...
On Mon, Apr 14, 2008 at 5:15 AM, Pierre Schmitz wrote:

...
Am Montag, 14. April 2008 08:47:52 schrieb eliott:

...
...
it does not work for me on x86_64:

==> Starting ABS sync... rsync: getaddrinfo: 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.2]

looks like you are having dns issues on that box.

No, I did not replace abs.conf by abs.conf.pacnew; so there was no rsync-server set. Sorry, my fault. Works now on i686 and x86_64.

Hm - I think I'll push this to core tonight, with a nice brief, but descriptive install message explaining the change and urging people to mv abs.conf.pacnew to abs.conf

Actually... since abs.conf is the only config file, can I move it straight into /etc, and avoid the issue altogether?

probably just emit a message. People may want to clean up the supfiles too.

Killing a subdir in /etc sounds good to me (seems dumb if we only have one file in it). Of course, don't do this if there is any chance of needing that subdir again.

oh! I thought he meant just clobber the file itself. yeah, if there is only one config file, then I agree it should move to /etc

5865

Age (days ago)

5866

Last active (days ago)

List overview

Download

8 comments

4 participants

participants (4)

Dan McGee
eliott
Pierre Schmitz
Travis Willard