[suggest] Version 4.0.8 of lftp is out

[Nico Kadel-Garcia]

Good morning!

lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine. Should I send a .spec
file with the one line change and a forged updated '%changelog', or
can I ask you wonderful folks upstream to get that into play, please?

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine.

4.0.8 SPEC has already been committed to the SVN yesterday. This is
exactly the reason why we are asking to check the SVN out first, instead
of ripping the SPECs out of SRPMs.

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64

I think it should have hit the mirrors yesterday already.

[Nico Kadel-Garcia]

Post by Dag Wieers

Post by Yury V. Zaytsev

Should I send a .spec file with the one line change ?and a forged
?updated '%changelog', or can I ask you wonderful folks upstream to get
?that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64
I think it should have hit the mirrors yesterday already.

Thanks, I was checking a mirror. Boy, you guys are fast.

[Nico Kadel-Garcia]

Post by Dag Wieers

Post by Yury V. Zaytsev

Should I send a .spec file with the one line change ?and a forged
?updated '%changelog', or can I ask you wonderful folks upstream to get
?that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64
I think it should have hit the mirrors yesterday already.

Thanks, I was checking a mirror. Boy, you guys are fast.

[Nico Kadel-Garcia]

Post by Dag Wieers

Post by Yury V. Zaytsev

Should I send a .spec file with the one line change ?and a forged
?updated '%changelog', or can I ask you wonderful folks upstream to get
?that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64
I think it should have hit the mirrors yesterday already.

Thanks, I was checking a mirror. Boy, you guys are fast.

[Nico Kadel-Garcia]

Post by Dag Wieers

Post by Yury V. Zaytsev

Should I send a .spec file with the one line change ?and a forged
?updated '%changelog', or can I ask you wonderful folks upstream to get
?that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64
I think it should have hit the mirrors yesterday already.

Thanks, I was checking a mirror. Boy, you guys are fast.

[Nico Kadel-Garcia]

Post by Dag Wieers

Post by Yury V. Zaytsev

Should I send a .spec file with the one line change ?and a forged
?updated '%changelog', or can I ask you wonderful folks upstream to get
?that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64
I think it should have hit the mirrors yesterday already.

Thanks, I was checking a mirror. Boy, you guys are fast.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64

I think it should have hit the mirrors yesterday already.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64

I think it should have hit the mirrors yesterday already.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64

I think it should have hit the mirrors yesterday already.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[dag at moria ~]# rpm -q lftp
lftp-4.0.8-1.el5.rf.x86_64

I think it should have hit the mirrors yesterday already.

[Nico Kadel-Garcia]

Good morning!

lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine. Should I send a .spec
file with the one line change and a forged updated '%changelog', or
can I ask you wonderful folks upstream to get that into play, please?

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine.

4.0.8 SPEC has already been committed to the SVN yesterday. This is
exactly the reason why we are asking to check the SVN out first, instead
of ripping the SPECs out of SRPMs.

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[Nico Kadel-Garcia]

Good morning!

lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine. Should I send a .spec
file with the one line change and a forged updated '%changelog', or
can I ask you wonderful folks upstream to get that into play, please?

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine.

4.0.8 SPEC has already been committed to the SVN yesterday. This is
exactly the reason why we are asking to check the SVN out first, instead
of ripping the SPECs out of SRPMs.

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[Nico Kadel-Garcia]

Good morning!

lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine. Should I send a .spec
file with the one line change and a forged updated '%changelog', or
can I ask you wonderful folks upstream to get that into play, please?

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine.

4.0.8 SPEC has already been committed to the SVN yesterday. This is
exactly the reason why we are asking to check the SVN out first, instead
of ripping the SPECs out of SRPMs.

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.

[Nico Kadel-Garcia]

Good morning!

lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine. Should I send a .spec
file with the one line change and a forged updated '%changelog', or
can I ask you wonderful folks upstream to get that into play, please?

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
lftp has an update published to version 4.0.8 with some minor
bugfixes. I just tested the existing 4.0.7 spec file from RPMforge,
updated to the 4.0.8 release, and it works fine.

4.0.8 SPEC has already been committed to the SVN yesterday. This is
exactly the reason why we are asking to check the SVN out first, instead
of ripping the SPECs out of SRPMs.

Post by Nico Kadel-Garcia
Should I send a .spec file with the one line change and a forged
updated '%changelog', or can I ask you wonderful folks upstream to get
that into play, please?

I think asking the wonderful folk of Dag to rebuild will do, but since
his is the person who has committed the SPEC I assume he already has it
on his mind, so you should just wait until the next rebuild happens.