[Freeswitch-users] debian build-all freezing at "Building sid-amd64 debs"

[Michael Jerris]

If we are talking about "best" then I would say Debian 7 is the preferred platform as that is what we do the most testing and development on.

> On Nov 17, 2014, at 6:36 PM, Steven Ayre <steveayre at gmail.com> wrote:
> 
> Ah ok. Not sure what I was thinking then actually as we're on 14.04 not 12.04. So Bruce my original comment stands, best to use the latest LTS 'Trusty'
> 
> On 17 November 2014 14:25, Michael Jerris <mike at jerris.com <mailto:mike at jerris.com>> wrote:
> Random crashes.  We have traced a number of them down to changes/patches pulled in to system libs, but stopped bothering, its not worth the time as the new LTS works fine.
> 
> 
>> On Nov 17, 2014, at 9:01 AM, Steven Ayre <steveayre at gmail.com <mailto:steveayre at gmail.com>> wrote:
>> 
>> That being said, we have had a string of well known very bad behaviors due to bugs in 12.04
>> 
>> Can you elaborate Michael? (The company I work for runs FS exclusively on servers running 12.04, although my personal preference would be Debian).
>> 
>> On 17 November 2014 13:46, Michael Jerris <mike at jerris.com <mailto:mike at jerris.com>> wrote:
>> Build on 12.04 generally works if you fix all the dependency issues (there are several).  That being said, we have had a string of well known very bad behaviors due to bugs in 12.04.  We strongly recommend against using it.  You will have random crashes and we will not spend any time trying to fix them due to these known issues.
>> 
>> 
>>> On Nov 15, 2014, at 5:58 AM, Steven Ayre <steveayre at gmail.com <mailto:steveayre at gmail.com>> wrote:
>>> 
>>> I believe 12.04 is too old to be supported by FreeSWITCH, it might be worth upgrading to 14.04 Trusty (which is also a LTS release) and which I know FS builds fine on on.
>>> 
>>> On 14 November 2014 21:47, Bruce Lefko <blefko5361 at gmail.com <mailto:blefko5361 at gmail.com>> wrote:
>>> So I ran those two exports you gave me and added "-c precise" to my utils call, but it still seems to be running into that pbuilder bug.  Here's the output or log/precise-amd64:
>>> 
>>> pbuilder/build//cow.20008 cow-shell 
>>> W: /root/.pbuilderrc does not exist
>>> I: Running in no-targz mode
>>> I: Upgrading for distribution precise
>>> I: copying local configuration
>>> cp: cannot create regular file `/var/cache/pbuilder/build/cow.20008/etc/hosts': No such file or directory
>>> pbuilder update failed
>>> E: could not update with cowdancer, try --no-cowdancer-update option
>>>   forking: rm -rf /var/cache/pbuilder/build//cow.20008 
>>>  -> Copying COW directory
>>>   forking: rm -rf /var/cache/pbuilder/build//cow.22359 
>>>   forking: cp -al /var/cache/pbuilder/base-precise-amd64.cow /var/cache/pbuilder/build//cow.22359 
>>> I: unlink for ilistfile /var/cache/pbuilder/build//cow.22359/.ilist failed, it didn't exist?
>>>  -> Invoking pbuilder
>>>   forking: pbuilder update --override-config --buildplace /var/cache/pbuilder/build//cow.22359 --mirror http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ <http://us-west-2.ec2.archive.ubuntu.com/ubuntu/> --distribution precise --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.22359 cow-shell 
>>> W: /root/.pbuilderrc does not exist
>>> I: Running in no-targz mode
>>> I: Upgrading for distribution precise
>>> I: copying local configuration
>>> cp: cannot create regular file `/var/cache/pbuilder/build/cow.22359/etc/hosts': No such file or directory
>>> pbuilder update failed
>>> E: could not update with cowdancer, try --no-cowdancer-update option
>>>   forking: rm -rf /var/cache/pbuilder/build//cow.22359 
>>> cannot canonicalize filename /var/cache/pbuilder/base-precise-amd64.cow, does not exist
>>> 
>>> Thanks!
>>> 
>>> 
>>> 
>>> On Thu, Nov 13, 2014 at 7:47 PM, Bruce Lefko <blefko5361 at gmail.com <mailto:blefko5361 at gmail.com>> wrote:
>>> Yeah, so it looks like in log/sid-amd64 I see the following over and over again:
>>> 
>>>   forking: rm -rf /var/cache/pbuilder/base-sid-amd64.cow 
>>>  -> Invoking pbuilder
>>>   forking: pbuilder create --buildplace /var/cache/pbuilder/base-sid-amd64.cow --mirror http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ <http://us-west-2.ec2.archive.ubuntu.com/ubuntu/> --architecture amd64 --distribution sid --no-targz --extrapackages cowdancer 
>>> W: /root/.pbuilderrc does not exist
>>> I: Running in no-targz mode
>>> I: Distribution is sid.
>>> I: Building the build environment
>>> I: running debootstrap
>>> /usr/sbin/debootstrap
>>> I: Retrieving Release
>>> E: Failed getting release file http://us-west-2.ec2.archive.ubuntu.com/ubuntu/dists/sid/Release <http://us-west-2.ec2.archive.ubuntu.com/ubuntu/dists/sid/Release>
>>> E: debootstrap failed
>>> W: Aborting with an error
>>> pbuilder create failed
>>> 
>>> 
>>> 
>>> On Thu, Nov 13, 2014 at 1:11 PM, Bruce Lefko <blefko5361 at gmail.com <mailto:blefko5361 at gmail.com>> wrote:
>>> I am trying to tweak mod_spandsp in master and deb package the code for use in my application.
>>> 
>>> I'm running "./debian/util.sh build-all -ibn -z9 -f /tmp/modules.conf" but it consistently gets stuck at "Building sid-amd64 debs.." 
>>> 
>>> First off, I'm not sure if this is the correct way to package custom changes, but also why is the debian build stuck at this step?
>>> 
>>> Thanks!
>>> 
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20141117/0d07d843/attachment-0001.html