[users] RPMFORGE URL for Mrepo

[Camron W. Fox]

Alle,

When have had the following configuration in our mrepo configuration
since installation for the rpmforge rsync URL:

rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/

However, when I was checking for the updated clamav packages today, I
found that the directory doesn't exist:

lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>

Is this still the correct pathname to use for rsync?

Best Regards,
Camron

[Dag Wieers]

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>
Is this still the correct pathname to use for rsync?

Hi Camron,

There was a cleanup of the directory structure on mirrors. And as you can
see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.

We also stopped providing native apt-repository support for newer RHEL
releases because apt-rpm supports createrepo repositories natively since 4
years or so... Regenerating the whole tree/repositories now takes less
than an hour, allowing us to push important fixes. (Although the main
mirror doesn't update that often)

I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

[Dave Miller]

Post by Dag Wieers

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I

There was a cleanup of the directory structure on mirrors. And as you
can see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.
I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

Yeah, I just discovered this the hard way myself a couple days ago,
ironically for the same reason (trying to figure out why we weren't
getting clamav updates).

Of course, mrepo had been kindly sending us email every day saying it
was getting an error on rpmforge that nobody saw buried with all the
rest of the cron mail from our hundreds of servers. :O (been an ongoing
problem, we recently had a person start spending most of their time
fixing cron jobs so we only get email on stuff that actually needs
action, but that's another story for another list)

The URL we're using now is:

rpmforge =
rsync://apt.sw.be/freshrpms/pub/dag/redhat/el$release/en/$arch/rpmforge/RPMS/

[Dave Miller]

Post by Dag Wieers

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I

There was a cleanup of the directory structure on mirrors. And as you
can see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.
I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

Yeah, I just discovered this the hard way myself a couple days ago,
ironically for the same reason (trying to figure out why we weren't
getting clamav updates).

Of course, mrepo had been kindly sending us email every day saying it
was getting an error on rpmforge that nobody saw buried with all the
rest of the cron mail from our hundreds of servers. :O (been an ongoing
problem, we recently had a person start spending most of their time
fixing cron jobs so we only get email on stuff that actually needs
action, but that's another story for another list)

The URL we're using now is:

rpmforge =
rsync://apt.sw.be/freshrpms/pub/dag/redhat/el$release/en/$arch/rpmforge/RPMS/

[Dave Miller]

Post by Dag Wieers

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I

There was a cleanup of the directory structure on mirrors. And as you
can see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.
I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

Yeah, I just discovered this the hard way myself a couple days ago,
ironically for the same reason (trying to figure out why we weren't
getting clamav updates).

Of course, mrepo had been kindly sending us email every day saying it
was getting an error on rpmforge that nobody saw buried with all the
rest of the cron mail from our hundreds of servers. :O (been an ongoing
problem, we recently had a person start spending most of their time
fixing cron jobs so we only get email on stuff that actually needs
action, but that's another story for another list)

The URL we're using now is:

rpmforge =
rsync://apt.sw.be/freshrpms/pub/dag/redhat/el$release/en/$arch/rpmforge/RPMS/

[Dave Miller]

Post by Dag Wieers

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I

There was a cleanup of the directory structure on mirrors. And as you
can see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.
I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

Yeah, I just discovered this the hard way myself a couple days ago,
ironically for the same reason (trying to figure out why we weren't
getting clamav updates).

Of course, mrepo had been kindly sending us email every day saying it
was getting an error on rpmforge that nobody saw buried with all the
rest of the cron mail from our hundreds of servers. :O (been an ongoing
problem, we recently had a person start spending most of their time
fixing cron jobs so we only get email on stuff that actually needs
action, but that's another story for another list)

The URL we're using now is:

rpmforge =
rsync://apt.sw.be/freshrpms/pub/dag/redhat/el$release/en/$arch/rpmforge/RPMS/

[Dave Miller]

Post by Dag Wieers

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I

There was a cleanup of the directory structure on mirrors. And as you
can see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.
I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

Yeah, I just discovered this the hard way myself a couple days ago,
ironically for the same reason (trying to figure out why we weren't
getting clamav updates).

Of course, mrepo had been kindly sending us email every day saying it
was getting an error on rpmforge that nobody saw buried with all the
rest of the cron mail from our hundreds of servers. :O (been an ongoing
problem, we recently had a person start spending most of their time
fixing cron jobs so we only get email on stuff that actually needs
action, but that's another story for another list)

The URL we're using now is:

rpmforge =
rsync://apt.sw.be/freshrpms/pub/dag/redhat/el$release/en/$arch/rpmforge/RPMS/

[Camron W. Fox]

Alle,

When have had the following configuration in our mrepo configuration
since installation for the rpmforge rsync URL:

rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/

However, when I was checking for the updated clamav packages today, I
found that the directory doesn't exist:

lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>

Is this still the correct pathname to use for rsync?

Best Regards,
Camron

[Dag Wieers]

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>
Is this still the correct pathname to use for rsync?

Hi Camron,

There was a cleanup of the directory structure on mirrors. And as you can
see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.

We also stopped providing native apt-repository support for newer RHEL
releases because apt-rpm supports createrepo repositories natively since 4
years or so... Regenerating the whole tree/repositories now takes less
than an hour, allowing us to push important fixes. (Although the main
mirror doesn't update that often)

I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

[Camron W. Fox]

Alle,

When have had the following configuration in our mrepo configuration
since installation for the rpmforge rsync URL:

rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/

However, when I was checking for the updated clamav packages today, I
found that the directory doesn't exist:

lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>

Is this still the correct pathname to use for rsync?

Best Regards,
Camron

[Dag Wieers]

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>
Is this still the correct pathname to use for rsync?

Hi Camron,

There was a cleanup of the directory structure on mirrors. And as you can
see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.

We also stopped providing native apt-repository support for newer RHEL
releases because apt-rpm supports createrepo repositories natively since 4
years or so... Regenerating the whole tree/repositories now takes less
than an hour, allowing us to push important fixes. (Although the main
mirror doesn't update that often)

I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

[Camron W. Fox]

Alle,

When have had the following configuration in our mrepo configuration
since installation for the rpmforge rsync URL:

rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/

However, when I was checking for the updated clamav packages today, I
found that the directory doesn't exist:

lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>

Is this still the correct pathname to use for rsync?

Best Regards,
Camron

[Dag Wieers]

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>
Is this still the correct pathname to use for rsync?

Hi Camron,

There was a cleanup of the directory structure on mirrors. And as you can
see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.

We also stopped providing native apt-repository support for newer RHEL
releases because apt-rpm supports createrepo repositories natively since 4
years or so... Regenerating the whole tree/repositories now takes less
than an hour, allowing us to push important fixes. (Although the main
mirror doesn't update that often)

I was surprised nobody complained the first days, so I think the
reorganization was useful :-)

[Camron W. Fox]

Alle,

When have had the following configuration in our mrepo configuration
since installation for the rpmforge rsync URL:

rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/

However, when I was checking for the updated clamav packages today, I
found that the directory doesn't exist:

lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>

Is this still the correct pathname to use for rsync?

Best Regards,
Camron

[Dag Wieers]

Post by Camron W. Fox
When have had the following configuration in our mrepo configuration
rpmforge =
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el5/en/$arch/RPMS.dag/
However, when I was checking for the updated clamav packages today, I
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64> ls -l
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 buildtools
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:50 dag
lrwxrwxrwx 1 ftp ftp 3 Aug 26 02:33 rpmforge -> dag
drwxrwxr-x 4 ftp ftp 48 Aug 26 02:33 testing
lftp apt.sw.be:/pub/freshrpms/pub/dag/redhat/el5/en/x86_64>
Is this still the correct pathname to use for rsync?

Hi Camron,

There was a cleanup of the directory structure on mirrors. And as you can
see it's better to either use 'dag/' or 'rpmforge/' rather than
'RPMS.dag/'.

We also stopped providing native apt-repository support for newer RHEL
releases because apt-rpm supports createrepo repositories natively since 4
years or so... Regenerating the whole tree/repositories now takes less
than an hour, allowing us to push important fixes. (Although the main
mirror doesn't update that often)

I was surprised nobody complained the first days, so I think the
reorganization was useful :-)