On 14/07/14 23:17, Niko Tyni wrote:
> I've just uploaded perl_5.18.2-7 providing only perlapi-5.18.2d on s390x
> and closing this bug (#753444).
FWIW, this had some trouble migrating because there were a few packages that
were still depending on perlapi-5.18.2 on testing, and the rebuilds were not
On 14/07/14 23:17, Niko Tyni wrote:
> On Mon, Jul 14, 2014 at 09:34:35AM +0200, Emilio Pozuelo Monfort wrote:
>> On 14/07/14 09:05, Niko Tyni wrote:
>
>>> So can I go ahead with dropping perlapi-5.18.2 or do we need to dig in
>>> the libimager-perl/libpng problem first?
>>
>> If you're ok with rem
On Mon, Jul 14, 2014 at 09:34:35AM +0200, Emilio Pozuelo Monfort wrote:
> On 14/07/14 09:05, Niko Tyni wrote:
> > So can I go ahead with dropping perlapi-5.18.2 or do we need to dig in
> > the libimager-perl/libpng problem first?
>
> If you're ok with removing libimager-perl, libimager-qrcode-per
On Mon, 14 Jul 2014 21:40:42 +0200, Emilio Pozuelo Monfort wrote:
> On 13/07/14 20:12, Aurelien Jarno wrote:
> > On Sun, Jul 13, 2014 at 03:19:51PM +0200, gregor herrmann wrote:
> >> - libsereal-* FTBFS on various architectures and are perfect removal
> >> candidates from testing (#742409 and #7
On 13/07/14 20:12, Aurelien Jarno wrote:
> On Sun, Jul 13, 2014 at 03:19:51PM +0200, gregor herrmann wrote:
>> - libsereal-* FTBFS on various architectures and are perfect removal
>> candidates from testing (#742409 and #750770).
>> hm, except that libsession-storage-secure-perl depends on them
On 14/07/14 09:05, Niko Tyni wrote:
> On Sun, Jul 13, 2014 at 01:27:37PM +0200, Emilio Pozuelo Monfort wrote:
>> On 13/07/14 13:04, Julien Cristau wrote:
>>> On Sat, Jul 5, 2014 at 11:45:16 +0200, Emilio Pozuelo Monfort wrote:
>>>
I have thought a bit more about this. I was hesitant as there
On Sun, Jul 13, 2014 at 01:27:37PM +0200, Emilio Pozuelo Monfort wrote:
> On 13/07/14 13:04, Julien Cristau wrote:
> > On Sat, Jul 5, 2014 at 11:45:16 +0200, Emilio Pozuelo Monfort wrote:
> >
> >> I have thought a bit more about this. I was hesitant as there are lots of
> >> packages involved, bu
On Sun, Jul 13, 2014 at 03:19:51PM +0200, gregor herrmann wrote:
> On Sun, 13 Jul 2014 13:27:37 +0200, Emilio Pozuelo Monfort wrote:
>
> > > perl 5.18.2-6 is now in jessie, so AFAICT it should be fine to drop the
> > > old Provides on s390x at this point.
> > Yes, but the seven packages that haven
On Sun, 13 Jul 2014 13:27:37 +0200, Emilio Pozuelo Monfort wrote:
> > perl 5.18.2-6 is now in jessie, so AFAICT it should be fine to drop the
> > old Provides on s390x at this point.
> Yes, but the seven packages that haven't been rebuilt will be a problem,
> unless
> we can drop them from testin
On 13/07/14 13:04, Julien Cristau wrote:
> On Sat, Jul 5, 2014 at 11:45:16 +0200, Emilio Pozuelo Monfort wrote:
>
>> I have thought a bit more about this. I was hesitant as there are lots of
>> packages involved, but thinking more about it, this should be pretty smooth.
>> You
>> add perlapi-5.1
On Sat, Jul 5, 2014 at 11:45:16 +0200, Emilio Pozuelo Monfort wrote:
> I have thought a bit more about this. I was hesitant as there are lots of
> packages involved, but thinking more about it, this should be pretty smooth.
> You
> add perlapi-5.18.2d to perl-base's Provides, but you won't remov
On Tue, Jul 08, 2014 at 09:43:14AM +0200, Emilio Pozuelo Monfort wrote:
> https://release.debian.org/transitions/html/perlapi-5.18.2d-s390x.html
>
> However the main blocker right now is the perl/mips FTBFS.
For the record, I'm aware of this but it's currently difficult to find
the time. The qu
On 07/07/14 10:49, Emilio Pozuelo Monfort wrote:
> On 07/07/14 09:31, Aurelien Jarno wrote:
>> On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
>>> That said, feel free to upload perl now.
>>
>> It has been uploaded, and is now installed on all s390x buildds.
>
> Thanks. I h
On 07/07/14 09:31, Aurelien Jarno wrote:
> On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
>> That said, feel free to upload perl now.
>
> It has been uploaded, and is now installed on all s390x buildds.
Thanks. I have scheduled a bunch of binNMUs.
Emilio
--
To UNSUBSC
On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
> That said, feel free to upload perl now.
It has been uploaded, and is now installed on all s390x buildds.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http:/
On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
> On 05/07/14 18:31, Niko Tyni wrote:
> > On Sat, Jul 05, 2014 at 11:45:16AM +0200, Emilio Pozuelo Monfort wrote:
> >> I have thought a bit more about this. I was hesitant as there are lots of
> >> packages involved, but think
Processing commands for cont...@bugs.debian.org:
> forwarded 753444
> https://release.debian.org/transitions/html/perlapi-5.18.2d-s390x.html
Bug #753444 [perl-base,release.debian.org] perl-base - Segfaults in
libperl.so.5.18
Bug #753592 [perl-base,release.debian.org] interruption code 0x4003B in
Processing control commands:
> reassign -1 perl-base,release.debian.org
Bug #753542 [libc6] perl-base - Segfaults in libperl.so.5.18
Bug reassigned from package 'libc6' to 'perl-base,release.debian.org'.
No longer marked as found in versions eglibc/2.19-1 and glibc/2.19-4.
Ignoring request to alte
Control: reassign -1 perl-base,release.debian.org
Control: user release.debian@packages.debian.org
Control: usertags -1 transition
On 05/07/14 18:31, Niko Tyni wrote:
> On Sat, Jul 05, 2014 at 11:45:16AM +0200, Emilio Pozuelo Monfort wrote:
>> On 05/07/14 08:48, Niko Tyni wrote:
>
>> I have t
Processing control commands:
> reassign -1 perl-base,release.debian.org
Bug #753444 [perl-base] perl-base - Segfaults in libperl.so.5.18
Bug #753592 [perl-base] interruption code 0x4003B in
libperl.so.5.18.2[3fffcfff000+1d]
Bug reassigned from package 'perl-base' to 'perl-base,release.debian.
On Sat, Jul 05, 2014 at 11:45:16AM +0200, Emilio Pozuelo Monfort wrote:
> On 05/07/14 08:48, Niko Tyni wrote:
> I have thought a bit more about this. I was hesitant as there are lots of
> packages involved, but thinking more about it, this should be pretty smooth.
> You
> add perlapi-5.18.2d to p
On 05/07/14 08:48, Niko Tyni wrote:
> On Sat, Jul 05, 2014 at 02:27:02AM +0200, Emilio Pozuelo Monfort wrote:
>> Although I would prefer to wait a bit and do 5.20 directly, I'm not affected
>> by
>> this breakage as I don't have any s390x machines. So if you think this is
>> important enough, we c
On Sat, Jul 05, 2014 at 02:27:02AM +0200, Emilio Pozuelo Monfort wrote:
> On 03/07/14 19:50, Aurelien Jarno wrote:
> > On Thu, Jul 03, 2014 at 07:43:57PM +0300, Niko Tyni wrote:
> >> I could make a sourceful perl upload incrementing perlapi-5.18.2 to
> >> for instance perlapi-5.18.2d (and removing
On 03/07/14 19:50, Aurelien Jarno wrote:
> On Thu, Jul 03, 2014 at 07:43:57PM +0300, Niko Tyni wrote:
>> On Thu, Jul 03, 2014 at 08:48:37AM +0200, Aurelien Jarno wrote:
>>> On Wed, Jul 02, 2014 at 11:29:58PM +0200, Bastian Blank wrote:
>>
The problem is a missmatch between the jmp_buf size in
On Thu, Jul 03, 2014 at 07:43:57PM +0300, Niko Tyni wrote:
> On Thu, Jul 03, 2014 at 08:48:37AM +0200, Aurelien Jarno wrote:
> > On Wed, Jul 02, 2014 at 11:29:58PM +0200, Bastian Blank wrote:
>
> > > The problem is a missmatch between the jmp_buf size in perl vs. modules.
> > > Aka the build again
On Thu, Jul 03, 2014 at 08:48:37AM +0200, Aurelien Jarno wrote:
> On Wed, Jul 02, 2014 at 11:29:58PM +0200, Bastian Blank wrote:
> > The problem is a missmatch between the jmp_buf size in perl vs. modules.
> > Aka the build against glibc 2.19 changed the public ABI of perl.
>
> Yes, jmp_buf had t
26 matches
Mail list logo
