Building complex packages,conversions and alien

jupiter:~# alien --scripts --to-deb MySQL-server-5.0.18-0.glibc23.ppc.rpm Package build failed. Here's the log: dh_testdir dh_testdir dh_testroot dh_clean -k -d dh_installdirs dh_installdocs dh_installchangelogs find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \ xargs -0 -r -i cp

Comfortable with Debian,but 4 points...

After some months with Debian(3.1PowerPC)I´m generally comfortable with it: -compiling software,and dealing with the different aspects of the package management system(good stuff!) -Connections to the Internet. -Printing system: my 70 dollars inkjet prints documents,photos with quality

Practical problems faced by new Debian user

I have Debian 3.1Sarge(testing) from early May2005,since then I have downloaded binary packages from testing(latest May) and 3.1stable (early June) and with dpkg -install package_x.deb I usually get: dpkg: dependency problems prevent configuration of package_x: package_x depends on libc6 (=

termcap in Debian:difficulties building programs

In Debian there is a termcap-compat package for i386 systems,I run a Sarge PowerPC system,so I needed to get a SuSE source,build it in Debian,and with alien create a .deb binary.It installs without problem,but I tried to build MySQL-4.1.12(from MySQL AB servers in Sweden) and the configure script

Is Debian Print Cartridge Refilling friendly?

I´m not exactly willing to pay 50 times to Hewlett Packard my inkjet printer,with this pick pocket business model of selling printers with a low price and print cartridges with a very high price,so I decided to refill my cartridges.I know that in Windows,Mac OS, Mac OS X the drivers and

debian sources to deb binaries.Risk of corrupting the file system?

When we build a binary debian .deb package from debian sources,for example with the debuild command of the devscripts package,is there the danger of change in the file system?For example with rpm there is a BuildRoot situated in /var/tmp where rpm temporarily installs all files of the binary

Crypto File System: Necessary patches

I got the following warning trying to create a crypto file system in hda10 partition of my hard disk: I did - modprobe cryptoloop modprobe aes losetup -e aes-256 /dev/loop0 /dev/hda10 Password: ioctl: LOOP_SET_STATUS: Invalid argument I have a PowerPC kernel 2.6.8,util-linux 2.12,and

Surprise upgrading Debian packages!

I have a background with several Linux distributions,and when I want to upgrade one package,I download the source package (or binary,if compatible) through a web browser html/ftp interface in a mirror. I see all packages listed and I pick what I want.Now,I have Debian and when I want to download