[L2Ork-dev] [PD] pd-l2ork 20121115 rc1 now available including deb -- please test and provide feedback
Jonathan Wilkes
jancsika at yahoo.com
Thu Dec 6 23:36:42 UTC 2012
Sounds good, I'll try again with the git version...
-Jonathan
----- Original Message -----
> From: Ivica Ico Bukvic <ico at vt.edu>
> To: Jonathan Wilkes <jancsika at yahoo.com>
> Cc: "An open mailing list for a world-wide network of aspiring L2Orkists, L2Ork developers, contributors, and supporters." <l2ork-dev at disis.music.vt.edu>
> Sent: Thursday, December 6, 2012 6:12 PM
> Subject: Re: [PD] pd-l2ork 20121115 rc1 now available including deb -- please test and provide feedback
>
>T his was fixed in the latest control file on git. I by mistake (read:
> lack of experience with debs) did not vet the control file. All should
> be well now.
>
> On 12/06/2012 05:32 PM, Jonathan Wilkes wrote:
>> Ok, turns out I just needs the devscripts and now it builds the deb
> correctly.
>>
>> Debian Wheezy can't satisfy libglew1.5 because it has libglew1.6. I
> just changed the
>> DEPENDS stuff in order to get past that.
>>
>> It installed successfully using Gdebi Package Manager and runs
> successfully.
>>
>>
>> But after the successful installation it shows this error in red:
>> Error: Breaks existing package 'pd-l2ork'
>> conflict pd-l2ork ()
>>
>>
>> I don't have another pd-l2ork deb package that I can find, either in
> that directory
>> or searching the repositories.
>>
>> -Jonathan
>>
>>
>> ----- Original Message -----
>>> From: Ivica Ico Bukvic <ico at vt.edu>
>>> To: Jonathan Wilkes <jancsika at yahoo.com>
>>> Cc: "An open mailing list for a world-wide network of aspiring
> L2Orkists, L2Ork developers, contributors, and supporters."
> <l2ork-dev at disis.music.vt.edu>
>>> Sent: Friday, November 30, 2012 1:04 AM
>>> Subject: Re: [PD] pd-l2ork 20121115 rc1 now available including deb --
> please test and provide feedback
>>>
>>> Your architecture descriptor in the control file is empty, which
> suggests Debian
>>> either has a fundamentally different version of dpkg-architecture
> (unlikely) or
>>> you don't have this tool installed (it might be that Debian has it
> as part
>>> of a separate optional package that has to be installed independently
> from other
>>> deb building tools).
>>>
>>> The following is command that is used by Makefile to detect your
> architecture
>>> and populate this field:
>>>
>>> dpkg-architecture
>>>
>>> Run it first by itself and see if you even have it. The output should
> be
>>> something like:
>>>
>>> DEB_BUILD_ARCH=amd64
>>> DEB_BUILD_ARCH_OS=linux
>>> DEB_BUILD_ARCH_CPU=amd64
>>> DEB_BUILD_ARCH_BITS=64
>>> DEB_BUILD_ARCH_ENDIAN=little
>>> DEB_BUILD_GNU_CPU=x86_64
>>> DEB_BUILD_GNU_SYSTEM=linux-gnu
>>> DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
>>> DEB_BUILD_MULTIARCH=x86_64-linux-gnu
>>> DEB_HOST_ARCH=amd64
>>> DEB_HOST_ARCH_OS=linux
>>> DEB_HOST_ARCH_CPU=amd64
>>> DEB_HOST_ARCH_BITS=64
>>> DEB_HOST_ARCH_ENDIAN=little
>>> DEB_HOST_GNU_CPU=x86_64
>>> DEB_HOST_GNU_SYSTEM=linux-gnu
>>> DEB_HOST_GNU_TYPE=x86_64-linux-gnu
>>> DEB_HOST_MULTIARCH=x86_64-linux-gnu
>>>
>>> If that goes well, try the actual command ran by Makefile:
>>>
>>> dpkg-architecture -qDEB_BUILD_ARCH
>>>
>>> The output should be your architecture, in my case:
>>>
>>> amd64
>>>
>>> Naturally, if you don't have the tool, install it. When trying to
> rebuild
>>> the deb you can use lowercase -b option which is an incremental install
>>> (provided your immediate previous attempt was to build a deb rather
> than a
>>> script-based installer) that completes a lot quicker.
>>>
>>> Hope this helps!
>>>
>>>
>>>
>>>
>>> On 11/29/2012 02:16 AM, Jonathan Wilkes wrote:
>>>>> ________________________________
>>>>> From: Ivica Bukvic <ico at vt.edu>
>>>>> To: Jonathan Wilkes <jancsika at yahoo.com>
>>>>> Cc: "An open mailing list for a world-wide network of
> aspiring
>>> L2Orkists, L2Ork developers, contributors, and supporters."
>>> <l2ork-dev at disis.music.vt.edu>
>>>>> Sent: Monday, November 19, 2012 11:51 PM
>>>>> Subject: Re: [PD] pd-l2ork 20121115 rc1 now available
> including deb --
>>> please test and provide feedback
>>>>>
>>>>> Also if you can, please send me the entire output of the
> terminal
>>> during build? Don't forget to compress it. If it proves too large
> for
>>> emailing, can you post it in a dropbox?
>>>>> Thanks!
>>>> Here is the control. How do I capture the terminal output?
>>>>
>>>> -Jonathan
>>>
>>> -- Ivica Ico Bukvic, D.M.A
>>> Composition, Music Technology
>>> Director, DISIS Interactive Sound & Intermedia Studio
>>> Director, L2Ork Linux Laptop Orchestra
>>> Head, ICAT IMPACT Studio
>>> Virginia Tech
>>> Department of Music
>>> Blacksburg, VA 24061-0240
>>> (540) 231-6139
>>> (540) 231-5034 (fax)
>>> disis.music.vt.edu
>>> l2ork.music.vt.edu
>>> ico.bukvic.net
>>>
>
>
> --
> Ivica Ico Bukvic, D.M.A
> Composition, Music Technology
> Director, DISIS Interactive Sound & Intermedia Studio
> Director, L2Ork Linux Laptop Orchestra
> Head, ICAT IMPACT Studio
> Virginia Tech
> Department of Music
> Blacksburg, VA 24061-0240
> (540) 231-6139
> (540) 231-5034 (fax)
> disis.music.vt.edu
> l2ork.music.vt.edu
> ico.bukvic.net
>
More information about the L2Ork-dev
mailing list