Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-21 Thread Sandro Tosi
Hello, On Wed, Apr 21, 2010 at 07:41, Rick Thomas rbtho...@pobox.com wrote: On Apr 20, 2010, at 2:30 AM, Jimmy Johnson wrote: If I was you I would start by finding out why python-twisted-core is not getting upgraded to the latest version that's in the repos and so on, with a little

Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-21 Thread Tristan Seligmann
On Wed, Apr 21, 2010 at 7:41 AM, Rick Thomas rbtho...@pobox.com wrote: The reason seems to be that python-twisted-core version 10.0.0-3 is available on amd64 Sid, but on i386 Sid it's only available at version 10.0.0-2 . Maybe it needs to be rebuilt for i386 ? python-twisted-core is an Arch:

Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-21 Thread Kurt Roeckx
On Wed, Apr 21, 2010 at 08:58:53AM +0200, Sandro Tosi wrote: On Wed, Apr 21, 2010 at 07:41, Rick Thomas rbtho...@pobox.com wrote: The reason seems to be that python-twisted-core version 10.0.0-3 is available on amd64 Sid, but on i386 Sid it's only available at version 10.0.0-2 . Maybe

Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-21 Thread Rick Thomas
On Apr 21, 2010, at 11:41 AM, Tristan Seligmann wrote: On Wed, Apr 21, 2010 at 7:41 AM, Rick Thomas rbtho...@pobox.com wrote: The reason seems to be that python-twisted-core version 10.0.0-3 is available on amd64 Sid, but on i386 Sid it's only available at version 10.0.0-2 . Maybe it

Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-21 Thread Cyril Brulebois
Hi. Rick Thomas rbtho...@pobox.com (21/04/2010): I don't know how this can happen, but it definitely did happen. Enjoy! The list of Arch: all packages merged into the Packages list for a given architecture depends (!) on the build status of the related Arch: any packages. I can think of the