Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #3519 [ All Revisions ] [ Back to Issue ]
Summary 0003519: dpkg-shlibdeps warning: libwadseeker.so.1.2 links against useless dependency libpthread.so.0
Revision 2018-09-24 23:48 by WubTheCaptain
Steps To Reproduce While issue 0003246 is unresolved, one unfortunately needs to put in a bit more effort to create an effective Debian package the Debian way. Something like this:

  1. Install debuild and dh_make on Debian: apt install devscripts dh-make # as superuser
  2. Retrieve a Mercurial snapshot of Doomseeker code, at (currently) latest commit a9995252fabcdd532cddcb763dc6c0931510e056 (or earlier). (hg clone'https://bitbucket.org/doomseeker/doomseeker [^]' && hg checkout a9995252fabcdd532cddcb763dc6c0931510e056) # URL must be all lowercase, else Bitbucket may throw HTTPS errors from command line use. wtf?
  3. Make a tarball release: (cd releasescripts/ && sh ./makesourcepackages.sh --no-sign) # yes, it's silly and requires to change directory first because it looks for ../src/*
  4. Extract the new source package somewhere: mkdir -p /tmp/doomseeker-debian && tar xfvJ doomseeker-1.2.tar.xz -C /tmp/doomseeker-debian # GNU TAR
  5. Change directory: cd /tmp/doomseeker-debian/doomseeker-1.2/
  6. Create stub Debian packaging files for the next step (accepting single package and any details): dh_make -f ../doomseeker-1.2.tar.xz
  7. Run debuild: debuild -us -uc
  8. Wait. Eventually debuild warns about dpkg-shlibdeps near the end of compilation, before lintian warnings/errors. (Perhaps ignore lintian for now, using dh_make without changes generates lots of warnings.)
Revision 2018-09-24 23:48 by WubTheCaptain
Steps To Reproduce While issue 0003246 is unresolved, one unfortunately needs to put in a bit more effort to create an effective Debian package the Debian way. Something like this:

  1. Install debuild and dh_make on Debian: apt install devscripts dh-make # as superuser
  2. Retrieve a Mercurial snapshot of Doomseeker code, at (currently) latest commit a9995252fabcdd532cddcb763dc6c0931510e056 (or earlier). (hg clone'https://bitbucket.org/doomseeker/doomseeker [^]' && hg checkout a9995252fabcdd532cddcb763dc6c0931510e056) # URL must be all lowercase, else Bitbucket may throw HTTPS errors from command line use. wtf?
  3. Make a tarball release: (cd releasescripts/ && sh ./makesourcepackages.sh --no-sign) # yes, it's silly and requires to change directory first because it looks for ../src/*
  4. Extract the new source package somewhere: mkdir -p /tmp/doomseeker-debian && tar xfvJ doomseeker-1.2.tar.xz -C /tmp/doomseeker-debian # GNU TAR
  5. Change directory: /tmp/doomseeker-debian/doomseeker-1.2/
  6. Create stub Debian packaging files for the next step (accepting single package and any details): dh_make -f ../doomseeker-1.2.tar.xz
  7. Run debuild: debuild -us -uc
  8. Wait. Eventually debuild warns about dpkg-shlibdeps near the end of compilation, before lintian warnings/errors. (Perhaps ignore lintian for now, using dh_make without changes generates lots of warnings.)
Revision 2018-09-24 22:46 by WubTheCaptain
Steps To Reproduce While issue 0003246 is unresolved, one unfortunately needs to put in a bit more effort to create an effective Debian package the Debian way. Something like this:

  1. Install debuild and dh_make on Debian: apt install devscripts dh-make # as superuser
  2. Retrieve a Mercurial snapshot of Doomseeker code, at (currently) latest commit a9995252fabcdd532cddcb763dc6c0931510e056 (or earlier). (hg clone'https://bitbucket.org/doomseeker/doomseeker [^]' && hg checkout a9995252fabcdd532cddcb763dc6c0931510e056) # URL must be all lowercase, else Bitbucket may throw HTTPS errors from command line use. wtf?
  3. Make a tarball release: (cd releasescripts/ && sh ./makesourcepackages.sh --no-sign) # yes, it's silly and requires to change directory first because it looks for ../src/*
  4. Extract the new source package somewhere: mkdir -p /tmp/doomseeker-debian && tar xfvJ doomseeker-1.2.tar.xz -C /tmp/doomseeker-debian # GNU TAR
  5. Change directory: /tmp/doomseeker-debian
  6. Create stub Debian packaging files for the next step (accepting single package and any details): dh_make -f ../doomseeker-1.2.tar.xz
  7. Run debuild: debuild -us -uc
  8. Wait. Eventually debuild warns about dpkg-shlibdeps near the end of compilation, before lintian warnings/errors. (Perhaps ignore lintian for now, using dh_make without changes generates lots of warnings.)
Revision 2018-09-24 22:18 by WubTheCaptain
Steps To Reproduce While issue 0003246 is unresolved, one unfortunately needs to put in a bit more effort to create an effective Debian package the Debian way. Something like this:

  1. Install debuild and dh_make on Debian: apt install devscripts dh-make # as superuser
  2. Retrieve a Mercurial snapshot of Doomseeker code, at (currently) latest commit a9995252fabcdd532cddcb763dc6c0931510e056 (or earlier). (hg clone'https://bitbucket.org/doomseeker/doomseeker [^]' && hg checkout a9995252fabcdd532cddcb763dc6c0931510e056) # URL must be all lowercase, else Bitbucket may throw HTTPS errors from command line use. wtf?
  3. Make a tarball release: (cd releasescripts/ && sh ./makesourcepackages.sh --no-sign) # yes, it's silly and requires to change directory first because it looks for ../src/*
  4. Extract the new source package somewhere: mkdir -p /tmp/doomseeker-debian && tar xfvJ doomseeker-1.2.tar.xz -C /tmp/doomseeker-debian # GNU TAR
  5. Change directory: /tmp/doomseeker-debian
  6. Create stub Debian packaging files for the next step (accepting single package and any details): dh_make -f ../doomseeker-1.2.tar.xz
  7. Run debuild: debuild -us -uc
  8. Wait. Eventually debuild warns about dpkg-shlibdeps near the end of compilation, before lintian warnings/errors. (Perhaps lintian for now, using dh_make without changes generates lots of warnings.)
Revision 2018-09-24 22:16 by WubTheCaptain
Steps To Reproduce While issue 0003246 is unresolved, one unfortunately needs to put in a bit more effort to create an effective Debian package the Debian way. Something like this:

  1. Install debuild and dh_make on Debian: apt install devscripts dh-make # as superuser
  2. Retrieve a Mercurial snapshot of Doomseeker code, at (currently) latest commit a9995252fabcdd532cddcb763dc6c0931510e056 (or earlier). (hg clone'https://bitbucket.org/doomseeker/doomseeker [^]' && hg checkout a9995252fabcdd532cddcb763dc6c0931510e056) # URL must be all lowercase, else Bitbucket may throw HTTPS errors from command line use. wtf?
  3. Make a tarball release: (cd releasescripts/ && sh ./makesourcepackages.sh) # yes, it's silly and requires to change directory first because it looks for ../src/*
  4. Extract the new source package somewhere: mkdir -p /tmp/doomseeker-debian && tar xfvJ doomseeker-1.2.tar.xz -C /tmp/doomseeker-debian # GNU TAR
  5. Change directory: /tmp/doomseeker-debian
  6. Create stub Debian packaging files for the next step (accepting single package and any details): dh_make -f ../doomseeker-1.2.tar.xz
  7. Run debuild: debuild -us -uc
  8. Wait. Eventually debuild warns about dpkg-shlibdeps near the end of compilation, before lintian warnings/errors. (Perhaps lintian for now, using dh_make without changes generates lots of warnings.)




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker