Installing V11 on Debian Testing

Keith Frost
Keith Frost
in Linux

I had previously had V11 running on Debian stable(squeeze), but my hard drive on my workstation died yesterday.

it took out both my windows and linux.

I'm still looking for my XP disks to reinstall, so in the mean time i'm working on Debian linux.

i had decided to install testing(wheezy).

i had to go back and add stable to my sources.list to pick up the libglew1.5.

apt-get didn't seem to have a problem with both 1.5 and 1.6 installed side by side.

but when i go to install bricscad i get:

dpkg: error processing /home/phrostie/Downloads/Bricscad-V11.3.16-2-en_US.deb (--install):
 parsing file '/var/lib/dpkg/tmp.ci/control' near line 187 package 'bricscadv11':
 blank line in value of field 'Description'
Errors were encountered while processing:
 /home/phrostie/Downloads/Bricscad-V11.3.16-2-en_US.deb

 

 

Comments

  • Philippe LAURENT
    Philippe LAURENT

    Hello

     

    I've already done a support request about it. There is a problem between dpkg 1.16 and Bricscad. Here is the answer from Tijs Vermeulen :

    Tijs Vermeulen 2011-10-06 15:35 UTC

    Hello,

    The debian policy manual explaining the syntax of the description field indeed mentions:
    "[...]a single space followed by a single full stop character. These are rendered as blank lines. This is the only way to get a blank line."
    http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description

    I never noticed this restriction before. So far, in the description field of the Bricscad deb installer blank lines were expressed by a line containing a single space only - not followed by a single full stop character.

    Debian bugreport #308082 seems to confirm that this restriction is enforced starting from 1.16.
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308082

    I have adapted our description field generation. The lines with a single space are now properly replaced by a single space followed by a single full stop.

    While the fix of the generation process was easy, regenerating all installers is a bit more work, since all translations need to be generated as well. I will discuss this with my colleague responsible for guiding our translators.

    Thanks for reporting this.

    Kind Regards
    Tijs Vermeulen

     

  • Philippe LAURENT
    Philippe LAURENT

    NB : you can bypass this problem by modifying the deb file.
    Here's a solution that is certainly not the best :

    • Create a directory with the deb file.

     

    • Start a console in the newly created directory.

     

    • Extract the file control.tar.gz from the deb file :

    ar x Bricscad-[version].deb control.tar.gz

     

    • Extract the control file from control.tar.gz :

    tar xf control.tar.gz

     

    • Edit the control file with vim, gedit or other ...

    Delete the blank line ( before last line, just before homepage ).

     

    • Recreate control.tar.gr :

    tar cfz control.tar.gz ./control ./postinst ./postrm

     

    • Replace control.tar.gz in the deb file :

    ar r Bricscad-[version].deb control.tar.gz



    Now you can install Bricscad again.

    I hope this will help you ...

  • Keith Frost
    Keith Frost

    sounds better than anything i'd thought of.

     

    I'll try it when i get back to my linux side.

     

    thanks

This discussion has been closed.