Re: Python3.4 / CVE-2016-5636

2019-01-13 Thread Brian May
I saeem to be having problems building the latest Jessie version
3.4.2-1+deb8u1 on Jessie.

[1/1] test_httplib
test test_httplib failed -- multiple errors occurred; run in verbose mode for 
details
1 test failed:
test_httplib
[1/1] test_httpservers


It seems to hang at this point. At first I though I broke something with
my fix for CVE-2016-5699.patch, which makes changes to httplib, but I
reverted all my changes and get exactly the same messages followed by
the same hang.

When I accidentally built the package on a sid schroot, I didn't get the
test failure, but I got the hang still. So suspect the failure is not
related to the hang.
-- 
Brian May 



Re: Assistance with building symfony for jessie

2019-01-13 Thread Roberto C . Sánchez
On Mon, Jan 14, 2019 at 09:40:33AM +1300, David Prévot wrote:
> Hi,
> 
> Le 14/01/2019 à 03:23, Roberto C. Sánchez a écrit :
> > On Sun, Jan 13, 2019 at 12:21:16PM +0530, Abhijith PA wrote:
> >> On Sunday 13 January 2019 06:26 AM, Roberto C. Sánchez wrote:
> 
> > Do you think you could try your build again, but for the
> > 2.3.21+dfsg-4+deb8u3 package in jessie?
> 
> I don’t use Jessie anymore (and am not interested in installing it
> again), sorry.
> 
That's understandable.  We will get it figured out.  Thank you for your
earlier assistance.

Regards,

-Roberto

-- 
Roberto C. Sánchez



Re: Assistance with building symfony for jessie

2019-01-13 Thread David Prévot
Hi,

Le 14/01/2019 à 03:23, Roberto C. Sánchez a écrit :
> On Sun, Jan 13, 2019 at 12:21:16PM +0530, Abhijith PA wrote:
>> On Sunday 13 January 2019 06:26 AM, Roberto C. Sánchez wrote:

> Do you think you could try your build again, but for the
> 2.3.21+dfsg-4+deb8u3 package in jessie?

I don’t use Jessie anymore (and am not interested in installing it
again), sorry.

Regards

David



signature.asc
Description: OpenPGP digital signature


Re: gzip not working properly

2019-01-13 Thread Matus UHLAR - fantomas

On Fri, Jan 11, 2019 at 10:59:00AM +, xia boles wrote:
>Hi, gzip is not working correctly, because when I install linux-images, it
>reports with gzip: stdout: no space left on device when I have a lot of
>space left. Can you fix it?



On Fri, 2019-01-11 at 08:02 -0500, Roberto C. Sánchez wrote:

That does not seem like a gzip problem.  It seems like your filesystem
does not have enough free space.  If /boot is a separate partition on
your system, try removing some kernel packages you no longer use.


On 13.01.19 15:21, Ben Hutchings wrote:

Right.  The error from gzip likely relates to creation of the initramfs
image, which has to go in /boot.

If there isn't even room for 2 versions of the kernel and initramfs in
/boot, another option would be to reduce the size of the initramfs by
setting MODULES=dep (see initramfs.conf(5)).


I think it uses /tmp as well. Do you have enough of space on /tmp?


--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"To Boot or not to Boot, that's the question." [WD1270 Caviar]



Re: gzip not working properly

2019-01-13 Thread Ben Hutchings
On Fri, 2019-01-11 at 08:02 -0500, Roberto C. Sánchez wrote:
> On Fri, Jan 11, 2019 at 10:59:00AM +, xia boles wrote:
> >Hi, gzip is not working correctly, because when I install linux-images, 
> > it
> >reports with gzip: stdout: no space left on device when I have a lot of
> >space left. Can you fix it?
> 
> That does not seem like a gzip problem.  It seems like your filesystem
> does not have enough free space.  If /boot is a separate partition on
> your system, try removing some kernel packages you no longer use.

Right.  The error from gzip likely relates to creation of the initramfs
image, which has to go in /boot.

If there isn't even room for 2 versions of the kernel and initramfs in
/boot, another option would be to reduce the size of the initramfs by
setting MODULES=dep (see initramfs.conf(5)).

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.




signature.asc
Description: This is a digitally signed message part


Re: Assistance with building symfony for jessie

2019-01-13 Thread Chris Lamb
Roberto C. Sánchez wrote:


> Since symfony is arch:all, there are no buildd logs to consult.  As a
> result, it would be helpful if one or two others out there could attempt
> to build symfony 2.3.21+dfsg-4+deb8u3 and report on the result.

Fails here too; log attached. Hope that helps.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


symfony_2.3.21+dfsg-4+deb8u3_amd64.build.xz
Description: application/xz


Re: Assistance with building symfony for jessie

2019-01-13 Thread Roberto C . Sánchez
On Sun, Jan 13, 2019 at 12:21:16PM +0530, Abhijith PA wrote:
> Hi Roberto
> 
> On Sunday 13 January 2019 06:26 AM, Roberto C. Sánchez wrote:
> > Hello all,
> > 
> > I have been working on the LTS update for symfony and while I completed
> > the backports of all of the patches several weeks ago I have not managed
> > to get the package to build on jessie.  In particular, the build fails
> > because of the unit tests.
> > 
> > To determine if any of my changes had anything to do with the unit test
> > failures I attempted to build the current version in jessie,
> > 2.3.21+dfsg-4+deb8u3.  That build attempt also failed.
> > 
> > I tried several different approaches to building the package (version
> > 2.3.21+dfsg-4+deb8u3) using different versions of dependencies to see
> > some dependency update along the way triggered new failures.  Here are
> > the build attempts I made:
> > 
> > - build in an updated jessie cowbuilder with gbp (FAIL)
> > - build in a jessie chroot using dpkg-buildpackage with dependencies at
> >   versions as they existed when version 2.3.21+dfsg-4+deb8u3 was
> >   uploaded on 10 May 2016 (FAIL)
> > - build in a jessie chroot using dpkg-buildpackage with dependencies at
> >   versions as they existed at the initial release of jessie (FAIL)
> > - build in a wheezy cowbuilder with gbp (FAIL, some dependencies do not
> >   exist in wheezy)
> > - build in a stretch cowbuilder with gbp (FAIL, some dependencies do not
> >   exist in stretch)
> > 
> > Since symfony is arch:all, there are no buildd logs to consult.  As a
> > result, it would be helpful if one or two others out there could attempt
> > to build symfony 2.3.21+dfsg-4+deb8u3 and report on the result.  If the
> > build is successful, I would appreciate a copy of the build log.  Or,
> > perhaps, if you are able/willing to finish the update and perform the
> > upload, I can provide my patches.
> 
> My build is also failing with around 20 unit test failures.
> 
> --a
> 

I was afraid of that.

I wonder what the best course of action is.  I had earlier communicated
with the maintainer about this.  That was several weeks ago.  At that
time he was travelling and had poor Internet access, but managed to run
a build...of the version in stretch.  I did want to further bother
someone who was travelling and without good Internet access, but since
it has been a few weeks, I have not been able to sort it out, and there
is now confirmation from someone else that the package does not build,
it seems time to ping the maintainer again.

I have copied him on this message.

David,

Do you think you could try your build again, but for the
2.3.21+dfsg-4+deb8u3 package in jessie?  I would very migh like to
resolve the build problem, get the package uploaded, and the advisory
published.

Regards,

-Roberto

-- 
Roberto C. Sánchez