Bug#687211: IPv6 recommends should be the preferred alternative

2012-09-11 Thread gregor herrmann
On Mon, 10 Sep 2012 22:53:41 +0200, Matthias Klose wrote: the alternatives for the build dependencies default to the ipv6 variants, while the recommends default to ipv4. this looks inconsistent. should the recommends default to ipv6 too? I guess (there are several alternatives with ipv6

Bug#687211: IPv6 recommends should be the preferred alternative

2012-09-11 Thread Salvatore Bonaccorso
Hi Gregor, Hi Matthias On Tue, Sep 11, 2012 at 06:30:23PM +0200, gregor herrmann wrote: On Mon, 10 Sep 2012 22:53:41 +0200, Matthias Klose wrote: the alternatives for the build dependencies default to the ipv6 variants, while the recommends default to ipv4. this looks inconsistent.

Bug#687211: IPv6 recommends should be the preferred alternative

2012-09-11 Thread gregor herrmann
On Tue, 11 Sep 2012 20:57:20 +0200, Salvatore Bonaccorso wrote: In my understanding, libio-socket-ip-perl is newer, preferred by upstream, and supports both IPv4 and IPv6. So the Recommends makes more sense to me than the B-D-I. Yes upstream has the following order in IO:Socket::SSL:

Bug#687211: IPv6 recommends should be the preferred alternative

2012-09-10 Thread Matthias Klose
Package: libio-socket-ssl-perl Version: 1.76-1 the alternatives for the build dependencies default to the ipv6 variants, while the recommends default to ipv4. this looks inconsistent. should the recommends default to ipv6 too? -- To UNSUBSCRIBE, email to