Hi Andreas, in order to build a backport for KiCad 4.0.1, I must at least wait until the package enters debian/sid: it it currently inside the NEW queue, due to the activation of two new binary packages, kicad-doc-es and kicad-doc-de. See https://qa.debian.org/developer.php?login=georg...@debian.org#kicad and https://ftp-master.debian.org/new/kicad_4.0.1-2.html
When this package will be accepted, I shall fork it into a new backport. Best regards, Georges. Andreas Krüger a écrit : > Package: kicad > Severity: wishlist > > Dear Maintainer, > > I managed to home-brew (fumble) Jessie backports > kicad-common_4.0.1-0~bpo8+1_all.deb and > kicad_4.0.1-0~bpo8+1_amd64.deb, and they installed and seem to work at > first glance (I'm new at kicad). But I would very much appreciate an > official version in Jessie-Backports. > > If that helps, here are some key points of what I found myself doing > (full details as a script below): > > I replaced the libglew1.13 dependency with libglew1.10. > > I used > https://launchpad.net/kicad/4.0/4.0.1/+download/kicad-4.0.1.tar.xz as > my source of upstream sources and had to change > debian/patches/20-noAvhttp.patch and > debian/patches/desktop-files.patch, as the upstream sources used ^M > line endings for all files in those patches. > > I failed to build the 4.0.1 documentation packages. There was a > possibly related note in README.source that I didn't understand: > > > The script get-kicad is run once, then debian patches are applied, and > > a build is done in the directory <packaging folder>/doc to generate > > PDF, HTML, EPUB files. Sourceless PDF files are erased, and the > > source package is compressed again. > > Is that something I should have done manually, or is this a mere > description of things that happen during the build? I compared the > content of the official kicad_4.0.0~rc1a.orig.tar.xz and my home-grown > kicad_4.0.1.orig.tar.xz, found quite a few differences of course, > but nothing that stroke me as glaring. > > Regards, and thank you for providing fine software, > > Andreas > > My full workaround script for home-brewing those two is attached. > As far as downloads is concerned, the script caches the results. > Build is done anew from scratch each time. > > The script contains a few ^M line endings which need to be preserved > for it to properly function: > > $ sha256sum -b run-build.sh > afe257af7624da4b7c884453219f80ae6ffa0c8200d2e9d0fb3957aaa9524c46 *run-build.sh > > The following system information pertains to my home-brew-result installed: > > -- System Information: > Debian Release: 8.2 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages kicad depends on: > ii kicad-common 4.0.1-0~bpo8+1 > ii libboost-context1.55.0 1.55.0+dfsg-3 > ii libboost-date-time1.55.0 1.55.0+dfsg-3 > ii libboost-filesystem1.55.0 1.55.0+dfsg-3 > ii libboost-iostreams1.55.0 1.55.0+dfsg-3 > ii libboost-locale1.55.0 1.55.0+dfsg-3 > ii libboost-program-options1.55.0 1.55.0+dfsg-3 > ii libboost-regex1.55.0 1.55.0+dfsg-3 > ii libboost-system1.55.0 1.55.0+dfsg-3 > ii libboost-thread1.55.0 1.55.0+dfsg-3 > ii libc6 2.19-18+deb8u1 > ii libgcc1 1:4.9.2-10 > ii libgl1-mesa-glx [libgl1] 10.3.2-1+deb8u1 > ii libglew1.10 1.10.0-3 > ii libglu1-mesa [libglu1] 9.0.0-2 > ii libgomp1 4.9.2-10 > ii libice6 2:1.0.9-1+b1 > ii libsm6 2:1.2.2-1+b1 > ii libstdc++6 4.9.2-10 > ii libwxbase3.0-0 3.0.2-1+b1 > ii libwxgtk3.0-0 3.0.2-1+b1 > ii libx11-6 2:1.6.2-3 > ii libxext6 2:1.3.3-1 > > kicad recommends no packages. > > Versions of packages kicad suggests: > ii extra-xdg-menus 1.0-4 > ii kicad-doc-en 4.0.0~rc1a-3 > > -- no debconf information > -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
