[arch-dev-public] [signoff] abs-2.0-1
In testing for signoff. Moved to rsync. Yay!
On 4/12/08, Travis Willard <travis@archlinux.org> wrote:
In testing for signoff. Moved to rsync. Yay!
Should /etc/abs/rsyncd.conf.abs be in the packages etc directory? Seems like that should be in /usr/share or something, as it is an example, and not a runtime required configuration file (nor is it an example file that is copied in the same dir).
On 4/12/08, eliott <eliott@cactuswax.net> wrote:
On 4/12/08, Travis Willard <travis@archlinux.org> wrote:
In testing for signoff. Moved to rsync. Yay!
Should /etc/abs/rsyncd.conf.abs be in the packages etc directory?
Seems like that should be in /usr/share or something, as it is an example, and not a runtime required configuration file (nor is it an example file that is copied in the same dir).
upgrading from a csup abs config to the new rsync config involved: 1. mv /etc/abs/abs.conf.pacnew /etc/abs/abs.conf 2. rm -f /etc/abs/supfile* (not required..just cleanup) 3. abs rsync even cleanedup the abs dir for me. :) Nice work Travis. *functionality signoff on i686*
eliott schrieb:
upgrading from a csup abs config to the new rsync config involved: 1. mv /etc/abs/abs.conf.pacnew /etc/abs/abs.conf 2. rm -f /etc/abs/supfile* (not required..just cleanup) 3. abs
rsync even cleanedup the abs dir for me. :)
Nice work Travis.
*functionality signoff on i686*
Careful: Some people have stuff in /var/abs/local, will that be gone? If yes, they should be warned.
On 4/12/08, Thomas Bächler <thomas@archlinux.org> wrote:
eliott schrieb:
upgrading from a csup abs config to the new rsync config involved: 1. mv /etc/abs/abs.conf.pacnew /etc/abs/abs.conf 2. rm -f /etc/abs/supfile* (not required..just cleanup) 3. abs
rsync even cleanedup the abs dir for me. :)
Nice work Travis.
*functionality signoff on i686*
Careful: Some people have stuff in /var/abs/local, will that be gone? If yes, they should be warned.
Nope. I tested that. I also tested the ! syntax in the abs.conf. That worked as expected for the testing repo at least.
On Sat, Apr 12, 2008 at 4:41 PM, Thomas Bächler <thomas@archlinux.org> wrote:
eliott schrieb:
upgrading from a csup abs config to the new rsync config involved: 1. mv /etc/abs/abs.conf.pacnew /etc/abs/abs.conf 2. rm -f /etc/abs/supfile* (not required..just cleanup) 3. abs
rsync even cleanedup the abs dir for me. :)
Nice work Travis.
*functionality signoff on i686*
Careful: Some people have stuff in /var/abs/local, will that be gone? If yes, they should be warned.
It purposefully keeps /var/abs/local and /var/abs/README (installed by the ABS package) - anything else inside of /var/abs will get nuked when you run abs tho
On Sat, Apr 12, 2008 at 4:20 PM, eliott <eliott@cactuswax.net> wrote:
On 4/12/08, Travis Willard <travis@archlinux.org> wrote:
In testing for signoff. Moved to rsync. Yay!
Should /etc/abs/rsyncd.conf.abs be in the packages etc directory?
Seems like that should be in /usr/share or something, as it is an example, and not a runtime required configuration file (nor is it an example file that is copied in the same dir).
Hm.... good call on that. /usr/share/abs might be a better place for it.
On Sat, 12 Apr 2008, Travis Willard wrote:
In testing for signoff. Moved to rsync. Yay!
Now that abs depends on rsync, should rsync be moved to core? Rsync is currently out-of-date so I (or someone else) could do the update/move at the same time. And what about csup? Will it be moved to extra or removed completely? We should wait after abs gets moved to core before doing that. And it looks good on x86_64. I just ran abs and it seems to work fine. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
participants (4)
-
eliott
-
Eric Belanger
-
Thomas Bächler
-
Travis Willard