~alpine/infra

2 2

Fw: Alpine aport iperf has been flagged out of date

Natanael Copa <ncopa@alpinelinux.org>
Details
Message ID
<20170307170047.1996b37b@ncopa-desktop.copa.dup.pw>
Sender timestamp
1488902447
DKIM signature
missing
Download raw message
Hi,

I wonder if we can include an url to the project in Anitya that
triggered the flag?

https://release-monitoring.org/projects/search/?pattern=iperf

In this case it seems like it was
https://release-monitoring.org/project/1389/

-nc

Begin forwarded message:

Date: Tue, 07 Mar 2017 12:15:31 -0000
From: Alpine Package DB <pkgs@alpinelinux.org>
To: ncopa@alpinelinux.org
Subject: Alpine aport iperf has been flagged out of date


Dear Natanael Copa

This is an automatic message send from pkgs.alpinelinux.org
You are receiving this message because you are the maintainer of aport:

iperf

abump iperf-3.1.7

The following message is send by: Alpine Package DB <pkgs@alpinelinux.org>

This package has been flagged automatically on the basis of notification from
Anitya <https://release-monitoring.org/>.

Please note that integration with Anitya is in experimental phase.
If the provided information is incorrect, please let us know on IRC
or alpine-infra@alpinelinux.org. Thanks!

Re: Alpine aport iperf has been flagged out of date

Jakub Jirutka <jakub@jirutka.cz>
Details
Message ID
<A7CF26AF-2EAB-4EB4-8543-00205FDEF2F1@jirutka.cz>
In-Reply-To
<20170307170047.1996b37b@ncopa-desktop.copa.dup.pw> (view parent)
Sender timestamp
1488920519
DKIM signature
missing
Download raw message
Hi,

yes, that would be probably useful.

I’ve fixed name of the mapped package on Anitya to iperf3. However, why we still have an old 2.x version as “iperf” and the current one as “iperf3”?

Jakub

> On 7. Mar 2017, at 17:00, Natanael Copa <ncopa@alpinelinux.org> wrote:
> 
> Hi,
> 
> I wonder if we can include an url to the project in Anitya that
> triggered the flag?
> 
> https://release-monitoring.org/projects/search/?pattern=iperf
> 
> In this case it seems like it was
> https://release-monitoring.org/project/1389/
> 
> -nc
> 
> Begin forwarded message:
> 
> Date: Tue, 07 Mar 2017 12:15:31 -0000
> From: Alpine Package DB <pkgs@alpinelinux.org>
> To: ncopa@alpinelinux.org
> Subject: Alpine aport iperf has been flagged out of date
> 
> 
> Dear Natanael Copa
> 
> This is an automatic message send from pkgs.alpinelinux.org
> You are receiving this message because you are the maintainer of aport:
> 
> iperf
> 
> abump iperf-3.1.7
> 
> The following message is send by: Alpine Package DB <pkgs@alpinelinux.org>
> 
> This package has been flagged automatically on the basis of notification from
> Anitya <https://release-monitoring.org/>.
> 
> Please note that integration with Anitya is in experimental phase.
> If the provided information is incorrect, please let us know on IRC
> or alpine-infra@alpinelinux.org. Thanks!
> 
> 
> 

Re: Alpine aport iperf has been flagged out of date

Natanael Copa <ncopa@alpinelinux.org>
Details
Message ID
<20170308104038.3a58bb94@ncopa-desktop.copa.dup.pw>
In-Reply-To
<A7CF26AF-2EAB-4EB4-8543-00205FDEF2F1@jirutka.cz> (view parent)
Sender timestamp
1488966038
DKIM signature
missing
Download raw message
On Tue, 7 Mar 2017 22:01:59 +0100
Jakub Jirutka <jakub@jirutka.cz> wrote:

> Hi,
> 
> yes, that would be probably useful.
> 
> I*ve fixed name of the mapped package on Anitya to iperf3. However,
> why we still have an old 2.x version as *iperf* and the current one
> as *iperf3*?

Looks like it is two different things.

"This code is a continuation based from the no longer maintained iperf
2.0.5 code base. . . . In summary, the Iperf2 code here attempts to
maintain the iperf 2.0.5 feature set and backward compatibility. . .

Iperf 2 vs iperf 3 major differences: Iperf 3 is a rewrite which does
not support interoperability with iperf 2."

https://sourceforge.net/projects/iperf2/

-nc

> 
> Jakub
> 
> > On 7. Mar 2017, at 17:00, Natanael Copa <ncopa@alpinelinux.org>
> > wrote:
> > 
> > Hi,
> > 
> > I wonder if we can include an url to the project in Anitya that
> > triggered the flag?
> > 
> > https://release-monitoring.org/projects/search/?pattern=iperf
> > 
> > In this case it seems like it was
> > https://release-monitoring.org/project/1389/
> > 
> > -nc
> > 
> > Begin forwarded message:
> > 
> > Date: Tue, 07 Mar 2017 12:15:31 -0000
> > From: Alpine Package DB <pkgs@alpinelinux.org>
> > To: ncopa@alpinelinux.org
> > Subject: Alpine aport iperf has been flagged out of date
> > 
> > 
> > Dear Natanael Copa
> > 
> > This is an automatic message send from pkgs.alpinelinux.org
> > You are receiving this message because you are the maintainer of
> > aport:
> > 
> > iperf
> > 
> > abump iperf-3.1.7
> > 
> > The following message is send by: Alpine Package DB
> > <pkgs@alpinelinux.org>
> > 
> > This package has been flagged automatically on the basis of
> > notification from Anitya <https://release-monitoring.org/>.
> > 
> > Please note that integration with Anitya is in experimental phase.
> > If the provided information is incorrect, please let us know on IRC
> > or alpine-infra@alpinelinux.org. Thanks!
> > 
> > 
> >   
> 
> 
Reply to thread Export thread (mbox)