Bug#821347: libsecret porting for s390x

2016-08-28 Thread Aurelien Jarno
On 2016-08-28 18:55, Aurelien Jarno wrote: > control: tag -1 + patch > control: tag -1 + upstream > control: tag -1 + fixed-upstream > > On 2016-08-25 14:16, Aurelien Jarno wrote: > > I am therefore cloning this bug and reassigning the clone to pygobject. > > I don't simply reassigning it as the

Processed: Re: Bug#821347: libsecret porting for s390x

2016-08-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #821347 [src:libsecret] FTBFS on mipsel and s390x: test suite failures Added tag(s) patch. > tag -1 + upstream Bug #821347 [src:libsecret] FTBFS on mipsel and s390x: test suite failures Added tag(s) upstream. > tag -1 + fixed-upstream Bug #821347

Bug#821347: libsecret porting for s390x

2016-08-28 Thread Aurelien Jarno
control: tag -1 + patch control: tag -1 + upstream control: tag -1 + fixed-upstream On 2016-08-25 14:16, Aurelien Jarno wrote: > I am therefore cloning this bug and reassigning the clone to pygobject. > I don't simply reassigning it as the /collection/delete-sync test is > also failing, though it

Processed: Re: Bug#821347: libsecret porting for s390x

2016-08-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 821347 -1 Bug #821347 [src:libsecret] FTBFS on mipsel and s390x: test suite failures Bug 821347 cloned as bug 835413 > reassign -1 pygobject Bug #835413 [src:libsecret] FTBFS on mipsel and s390x: test suite failures Bug reassigned from

Bug#821347: libsecret porting for s390x

2016-08-25 Thread Aurelien Jarno
clone 821347 -1 reassign -1 pygobject retitle -1 pygobject: wrong enum to hash conversion on 64-bit big endian affects -1 libsecret block 821347 by -1 thanks On 2016-08-25 09:15, Aurelien Jarno wrote: > On 2016-07-27 14:23, Emilio Pozuelo Monfort wrote: > > On 27/07/16 14:16, Aurelien Jarno

Bug#821347: libsecret porting for s390x

2016-08-25 Thread Aurelien Jarno
On 2016-07-27 14:23, Emilio Pozuelo Monfort wrote: > On 27/07/16 14:16, Aurelien Jarno wrote: > > On 2016-07-10 21:24, Andreas Henriksson wrote: > >> Hello Bastian Blank. > >> > >> On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: > >>> On Sun, Jun 26, 2016 at 10:12:31PM +0200,

Bug#821347: libsecret porting for s390x

2016-07-27 Thread Emilio Pozuelo Monfort
On 27/07/16 14:16, Aurelien Jarno wrote: > On 2016-07-10 21:24, Andreas Henriksson wrote: >> Hello Bastian Blank. >> >> On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: >>> On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: I'd like to ask for your help with

Bug#821347: libsecret porting for s390x

2016-07-27 Thread Aurelien Jarno
On 2016-07-10 21:24, Andreas Henriksson wrote: > Hello Bastian Blank. > > On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: > > On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: > > > I'd like to ask for your help with looking at the problems building > > >

Bug#821347: libsecret porting for s390x

2016-07-10 Thread Andreas Henriksson
Hello Bastian Blank. On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: > On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: > > I'd like to ask for your help with looking at the problems building > > libsecret on s390x. It's currently the only (release-)architecture

Bug#821347: libsecret porting for s390x

2016-07-10 Thread Bastian Blank
On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: > I'd like to ask for your help with looking at the problems building > libsecret on s390x. It's currently the only (release-)architecture > not building and blocking testing migration for a long time. :( What was the result of

Bug#821347: libsecret porting for s390x

2016-06-26 Thread Andreas Henriksson
Hello Debian s390x porters! I'd like to ask for your help with looking at the problems building libsecret on s390x. It's currently the only (release-)architecture not building and blocking testing migration for a long time. :( It seems the testsuite somehow gets stuck on your arch/buildd