These are instructions for building a ‘testing’ package on a ‘stable’ system.
When running the stable distribution of debian occasionally you
want to install non-stable packages, because they don’t appear in
stable, or features or revisions are not up to what we need on our
system. To do this we have to simply compile the upstream packages in
the traditional debian style.
We have on our system the pre-requisite packages to build .deb files,
namely: dpkg-dev and fakeroot. Our /etc/apt/sources.list file contains
the following “deb-src” lines which are duplicates of normal “deb”
lines, with deb-src in front instead:
deb-src http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free
note: it is possible to add lines similar to this for unstable, but it
would be better to add them when you are sure you want package source from
unstable instead of accidentally getting something from unstable.
The process to install a package from something other than stable is:
- apt-get update
- apt-get source – this will download the orig.tar.gz,
diff.gz and .dsc source files for your package, unpack them and patch
the source code in a new source directory underneath the one you are
- Look in the .dsc file for the “Build-Depends” list, verify all of
those packages are currently installed on the system. Also, make sure
no packages listed in the “Build-Conflicts” (if it exists) are installed.
- cd to the source directory and type (as root) “debian/rules
binary”, or if you are not root, type: “fakeroot debian/rules binary”
This will automatically go through all of the steps necessary to
build your package.
- Install the .deb file that was created in the parent directory:
“dpkg -i ../__.dev” – for example, if you
built the smartmontools package, you would see in the parent directory
the .deb file smartmontools_5.1.4-2_i386.deb, so you would do: “dpkg -i ../smartmontools_5.1.4-2_i386.deb”
I’m delighted to have read your entertaining essay, Continue to post excellent posts like this one
What practices and tools can be effective in striving to improve product quality when we combine manual testing performed by humans and automated testing performed using special tools and scripts?
The combination of manual and automated testing improves product quality by making optimal use of each approach. Enhancing Quality Through Manual Testing and Test Automation provides a deeper, more contextual analysis of functionality, which is especially important for new features or product changes. Test automation allows you to quickly and repeatedly check the stability and performance of a product, which is especially useful in continuous integration and delivery environments. An intelligent combination of both methods, as well as careful planning, collaboration, and analysis of the results, improves the quality and speeds up the development process.
I followed the instructions, and I successfully installed the pokedoku non-stable package on my stable Debian system.
Automating test automation makes it possible to rapidly and often assess a product’s performance and snow rider 3d stability, which is particularly helpful in situations that include continuous integration and delivery.