Mirror not updating

[darose]

Anyone have contact info for the rit.edu mirror?  It doesn't appear to
have been updated since June 30.

Thanks,

DR

[Gerhard Brauer]

Am Donnerstag, den 09.07.2009, 09:27 -0400 schrieb David Rosenstrauch:
> Anyone have contact info for the rit.edu mirror?  It doesn't appear to
> have been updated since June 30.

I have contacted on Tuesday all mirror admin from the affected US/CA/EU
mirrors, which are not synced and have all the same lastsync time.

Only CA mirror http://mirror.twilightlair.net/arch is synced again from
this block.
I'll write a mail tomorrow again i nothing happens.

>
> Thanks,
>
> DR

Gerhard "gerbra"

[Lee R. Burton]

Sorry, just saw this email, RIT mirror is now syncing, ... seems a lockfile got stuck.
Feel free to give me a call next time for a more rapid response to it.
Thanks,
Lee Burton
lburton@...
301 910 0246

----- Original Message -----
From: "Gerhard Brauer" <gerhard.brauer@...>
To: arch-general@...
Sent: Thursday, July 9, 2009 10:00:00 AM GMT -05:00 US/Canada Eastern
Subject: Re: [arch-general] Mirror not updating

Am Donnerstag, den 09.07.2009, 09:27 -0400 schrieb David Rosenstrauch:
> Anyone have contact info for the rit.edu mirror?  It doesn't appear to
> have been updated since June 30.

I have contacted on Tuesday all mirror admin from the affected US/CA/EU
mirrors, which are not synced and have all the same lastsync time.

Only CA mirror http://mirror.twilightlair.net/arch is synced again from
this block.
I'll write a mail tomorrow again i nothing happens.

>
> Thanks,
>
> DR

Gerhard "gerbra"

[Allan McRae-3]

David Rosenstrauch wrote:

> Gerhard Brauer wrote:
>> Am Donnerstag, den 09.07.2009, 09:27 -0400 schrieb David Rosenstrauch:
>>> Anyone have contact info for the rit.edu mirror?  It doesn't appear
>>> to have been updated since June 30.
>>
>> I have contacted on Tuesday all mirror admin from the affected US/CA/EU
>> mirrors, which are not synced and have all the same lastsync time.
>>
>> Only CA mirror http://mirror.twilightlair.net/arch is synced again from
>> this block.
>> I'll write a mail tomorrow again i nothing happens.
>>
>>> Thanks,
>>>
>>> DR
>>
>> Gerhard "gerbra"
>
> Thanks much for the update!
>
> Just wondering:  any way we could post status on a web page somewhere
> on the last time each mirror has synched?  (And, for bonus points,
> maybe a 1-line status comment for each, where someone could post a
> message indicating what the status is of any issues that mirror is
> having.)

Such as http://users.archlinux.de/~gerbra/mirrorcheck.html

[darose]

Gerhard Brauer wrote:

> Am Donnerstag, den 09.07.2009, 09:27 -0400 schrieb David Rosenstrauch:
>> Anyone have contact info for the rit.edu mirror?  It doesn't appear to
>> have been updated since June 30.
>
> I have contacted on Tuesday all mirror admin from the affected US/CA/EU
> mirrors, which are not synced and have all the same lastsync time.
>
> Only CA mirror http://mirror.twilightlair.net/arch is synced again from
> this block.
> I'll write a mail tomorrow again i nothing happens.
>
>> Thanks,
>>
>> DR
>
> Gerhard "gerbra"

Thanks much for the update!

Just wondering:  any way we could post status on a web page somewhere on
the last time each mirror has synched?  (And, for bonus points, maybe a
1-line status comment for each, where someone could post a message
indicating what the status is of any issues that mirror is having.)

Thanks again,

DR

[darose]

Cool.  Thanks much, Lee.

Your mirror is great, btw.  Nice and fast for us US Easterners!

DR

Lee R. Burton wrote:

> Sorry, just saw this email, RIT mirror is now syncing, ... seems a lockfile got stuck.
> Feel free to give me a call next time for a more rapid response to it.
> Thanks,
> Lee Burton
> lburton@...
> 301 910 0246
>
> ----- Original Message -----
> From: "Gerhard Brauer" <gerhard.brauer@...>
> To: arch-general@...
> Sent: Thursday, July 9, 2009 10:00:00 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [arch-general] Mirror not updating
>
> Am Donnerstag, den 09.07.2009, 09:27 -0400 schrieb David Rosenstrauch:
>> Anyone have contact info for the rit.edu mirror?  It doesn't appear to
>> have been updated since June 30.
>
> I have contacted on Tuesday all mirror admin from the affected US/CA/EU
> mirrors, which are not synced and have all the same lastsync time.
>
> Only CA mirror http://mirror.twilightlair.net/arch is synced again from
> this block.
> I'll write a mail tomorrow again i nothing happens.
>
>> Thanks,
>>
>> DR
>
> Gerhard "gerbra"

[darose]

Allan McRae wrote:
> Such as http://users.archlinux.de/~gerbra/mirrorcheck.html

Yes - exactly such as that!  :-)

Thanks much!  Didn't even know that page existed.

DR

[Dieter Plaetinck]

On Thu, 09 Jul 2009 11:54:43 -0400
David Rosenstrauch <darose@...> wrote:

> Allan McRae wrote:
> > Such as http://users.archlinux.de/~gerbra/mirrorcheck.html
>
> Yes - exactly such as that!  :-)
>
> Thanks much!  Didn't even know that page existed.
>
> DR

Maybe we should link to it from the main page or host it on
archlinux.org if it's not too much work to migrate it (on the long term
i want mirrorbrain)

Dieter

[Pierre Schmitz-2]

On Thursday 09 July 2009 17:50:50 David Rosenstrauch wrote:
> any way we could post status on a web page somewhere on
> the last time each mirror has synched

There is https://www.archlinux.de/?page=MirrorStatus You can sort the list by
last sync time etc.. There is also a list with current problems at the bottom.

Its updated every hour and the average stats take the last two weeks into
accout.

--

Pierre Schmitz, http://users.archlinux.de/~pierre

[Gerhard Brauer]

Am Donnerstag, den 09.07.2009, 11:54 -0400 schrieb David Rosenstrauch:
> Allan McRae wrote:
> > Such as http://users.archlinux.de/~gerbra/mirrorcheck.html
>
> Yes - exactly such as that!  :-)
>
> Thanks much!  Didn't even know that page existed.

You also could easy check a mirror with this script:
---------------
#!/bin/sh
#
# Test Arch Linux Mirror status
# Parameter: URL to test (full path to Arch Linux dir on mirror)
# 2008/06/10 Gerhard Brauer <gerbra@...>
#
ARCHES="i686 x86_64"
REPOS="core extra community"

echo
echo "Mirror-URL: $1"
echo "Last timestamp from rsync.archlinux.org (updated each hour)"
echo "------------------------------------------------------------"
for arch in ${ARCHES}; do
    for repo in ${REPOS}; do
        echo -e -n "$arch-$repo:\t"
        date +"%x %X" -u -d @$(wget -q -O - $1/$repo/os/$arch/lastsync)
    done
done
---------------

ex.: sh /tmp/mt.sh ftp://mirror.rit.edu/archlinux
shows you (in UTC) the lastsync time. Means: this mirror has last synced
to his upstream between the displayed timestap  and displayed timestamp
+ 1 hour.
To see the time according to your timezone, remove the -u parameter on
date call.

> DR

Gerhard "gerbra"

[Gerhard Brauer]

Am Donnerstag, den 09.07.2009, 19:17 +0200 schrieb Gerhard Brauer:

> You also could easy check a mirror with this script:

Got an idea (hehe!)....
Could we add such a check into pacman?
So pacman could warn if current used mirror was outdated, or a
commandline option to check the user prefered mirror.

Gerhard "gerbra"

[Daenyth Blank]

On Thu, Jul 9, 2009 at 13:44, Gerhard Brauer<gerhard.brauer@...> wrote:
> Am Donnerstag, den 09.07.2009, 19:17 +0200 schrieb Gerhard Brauer:
>> You also could easy check a mirror with this script:
> Could we add such a check into pacman?

I don't think that's really needed. We shouldn't have any consistantly
outdated mirrors, and if we do, they should be either marked as such
or removed from the mirrorlist.

[Lee R. Burton]

Perhaps not needed, but could be useful, more folks complaining generally = faster action on the part of a mirror admin (like yours truely)... although, if someone comes back from vacation to an inbox full of 300 "YOUR MIRROR IS OUTDATED" messages, they might be understandably unhappy.  
Might be nice to know as an end-user since one could switch off the mirror for a while.. mhm that part could even be made automagic.
Cheers,
Lee Burton
lburton@...
301 910 0246

----- Original Message -----
From: "Daenyth Blank" <daenyth+arch@...>
To: "General Discusson about Arch Linux" <arch-general@...>
Sent: Thursday, July 9, 2009 1:59:09 PM GMT -05:00 US/Canada Eastern
Subject: Re: [arch-general] Mirror not updating

On Thu, Jul 9, 2009 at 13:44, Gerhard Brauer<gerhard.brauer@...> wrote:
> Am Donnerstag, den 09.07.2009, 19:17 +0200 schrieb Gerhard Brauer:
>> You also could easy check a mirror with this script:
> Could we add such a check into pacman?

I don't think that's really needed. We shouldn't have any consistantly
outdated mirrors, and if we do, they should be either marked as such
or removed from the mirrorlist.

[Square]

I noticed this in my typical routine when installing AUR packages. 'makepkg -sic' is the typical command I use, and most of the time if dependencies are installed before building sudo doesn't time out before the install - meaning I do not have to re-enter a password for installing the package itself. This leaves a window where any time during the build process a command could have been executed with sudo and it would have went through without my knowledge.

I do realize that it should be up to the user to validate all of the
content, i.e. make sure everything is 'clean', but I thought I might
bring it up for discussion.

[Aaron Griffin]

On Thu, Jul 9, 2009 at 1:55 PM, Square<toolman33@...> wrote:
> I noticed this in my typical routine when installing AUR packages. 'makepkg -sic' is the typical command I use, and most of the time if dependencies are installed before building sudo doesn't time out before the install - meaning I do not have to re-enter a password for installing the package itself. This leaves a window where any time during the build process a command could have been executed with sudo and it would have went through without my knowledge.
>
> I do realize that it should be up to the user to validate all of the
> content, i.e. make sure everything is 'clean', but I thought I might
> bring it up for discussion.

This is up to you to control. You can change the timeout in
/etc/sudoers by using the "password_timeout" (or is it
"passwd_timeout"?) option.

[Thomas Bächler-2]

Aaron Griffin schrieb:

> On Thu, Jul 9, 2009 at 1:55 PM, Square<toolman33@...> wrote:
>> I noticed this in my typical routine when installing AUR packages. 'makepkg -sic' is the typical command I use, and most of the time if dependencies are installed before building sudo doesn't time out before the install - meaning I do not have to re-enter a password for installing the package itself. This leaves a window where any time during the build process a command could have been executed with sudo and it would have went through without my knowledge.
>>
>> I do realize that it should be up to the user to validate all of the
>> content, i.e. make sure everything is 'clean', but I thought I might
>> bring it up for discussion.
>
> This is up to you to control. You can change the timeout in
> /etc/sudoers by using the "password_timeout" (or is it
> "passwd_timeout"?) option.

I agree. The question is not about makepkg security, but about sudo
security. And frankly, sudo is a security desaster in its default
configuration.

[Aaron Griffin]

On Thu, Jul 9, 2009 at 3:37 PM, Thomas Bächler<thomas@...> wrote:

> Aaron Griffin schrieb:
>>
>> On Thu, Jul 9, 2009 at 1:55 PM, Square<toolman33@...> wrote:
>>>
>>> I noticed this in my typical routine when installing AUR packages.
>>> 'makepkg -sic' is the typical command I use, and most of the time if
>>> dependencies are installed before building sudo doesn't time out before the
>>> install - meaning I do not have to re-enter a password for installing the
>>> package itself. This leaves a window where any time during the build process
>>> a command could have been executed with sudo and it would have went through
>>> without my knowledge.
>>>
>>> I do realize that it should be up to the user to validate all of the
>>> content, i.e. make sure everything is 'clean', but I thought I might
>>> bring it up for discussion.
>>
>> This is up to you to control. You can change the timeout in
>> /etc/sudoers by using the "password_timeout" (or is it
>> "passwd_timeout"?) option.
>
> I agree. The question is not about makepkg security, but about sudo
> security. And frankly, sudo is a security desaster in its default
> configuration.

Any suggestions for changing / shipping a better default config file?
I know little about the security implications of this, but I think we
should ship a decent default if possible.

[Daenyth Blank]

On Thu, Jul 9, 2009 at 14:28, Lee R. Burton<lburton@...> wrote:
> Perhaps not needed, but could be useful, more folks complaining generally = faster action on the part of a mirror admin (like yours truely)... although, if someone comes back from vacation to an inbox full of 300 "YOUR MIRROR IS OUTDATED" messages, they might be understandably unhappy.
> Might be nice to know as an end-user since one could switch off the mirror for a while.. mhm that part could even be made automagic.

I still disagree. pacman is a package manager, not a mirror
maintenance tool. An external script, or perhaps yaourt would be a
better home for it.

[Alessandro Doro]

On Thu, Jul 09, 2009 at 03:00:49PM -0500, Aaron Griffin wrote:

> On Thu, Jul 9, 2009 at 1:55 PM, Square<toolman33@...> wrote:
> > I noticed this in my typical routine when installing AUR packages.
> > 'makepkg -sic' is the typical command I use, and most of the time if
> > dependencies are installed before building sudo doesn't time out
> > before the install - meaning I do not have to re-enter a password
> > for installing the package itself. This leaves a window where any
> > time during the build process a command could have been executed
> > with sudo and it would have went through without my knowledge.
> >
> > I do realize that it should be up to the user to validate all of the
> > content, i.e. make sure everything is 'clean', but I thought I might
> > bring it up for discussion.
>
> This is up to you to control. You can change the timeout in
> /etc/sudoers by using the "password_timeout" (or is it
> "passwd_timeout"?) option.

A simple workaround could be a "sudo  -k" after each sudo invocation in
the makepkg script.

[Daenyth Blank]

On Thu, Jul 9, 2009 at 20:25, Alessandro Doro<ordo.ad@...> wrote:
> A simple workaround could be a "sudo  -k" after each sudo invocation in
> the makepkg script.
>

I don't think there should be any such behavior added. All we do is
follow the settings the user has established -- no more and no less.
Let's not have our tools start second-guessing the users. We should
always start with the assumption that the user is competant.