Re: [newbie] rpm install failures
SNIP Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John John If there is a problem with the gimpprint driver for your printer type why not mention it on the printer forum at Mandrake Club? http://www.mandrakeclub.com/modules.php?name=Splatt_Forum You do not need a membership, and printer questions are often answered by Till Klampetter Mandrake's printer guru. derek Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
On Wed, 2002-12-04 at 19:37, Derek Jennings wrote: SNIP Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John John If there is a problem with the gimpprint driver for your printer type why not mention it on the printer forum at Mandrake Club? http://www.mandrakeclub.com/modules.php?name=Splatt_Forum You do not need a membership, and printer questions are often answered by Till Klampetter Mandrake's printer guru. derek What about completely removing the printer drivers from John's distro, then re-installing them via the MCC Package Management? Wouldn't this be so much easier than mucking around with RPM's that will break his box? ...and I rather forgot what exactly was the reasoning behind installing new drivers in the first place... -- Wed Dec 4 20:05:00 EST 2002 .o0 linux user:267497 0o. |____ | kühn media australia | / \ /| |'-. | http://kma.0catch.com | .\__/ || | | | | _ / `._ \|_|_.-' | stephen kühn | | / \__.`=._) (_ | email: [EMAIL PROTECTED] | |/ ._/ || | email: [EMAIL PROTECTED] | |'. `\ | | |icq: 5483808 | ;/ / | | | | smk ) /_/| |.---.| | mobile: 0410-728-389 | ' `-`' | Berkeley, New South Wales, AU Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn Mulder: how big can this thing get? Scully: Mulder, I.. (smiles) sorry, for a second there it felt like old times. The X-Files: The Host Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
Derek Jennings wrote: SNIP Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John John If there is a problem with the gimpprint driver for your printer type why not mention it on the printer forum at Mandrake Club? http://www.mandrakeclub.com/modules.php?name=Splatt_Forum You do not need a membership, and printer questions are often answered by Till Klampetter Mandrake's printer guru. derek Yes, the fault is known, someone has been tinkering with the gimpprint/libgimpprint, the one is the gui to the backend driver of the other, and crosswired red and blue, so that the colour rendering is reversed. I've been busy backdating the same files , Till, took me so far, then no further,and it didn't quite work, the hope has to be that a new fixed set of gimp drivers will emerge, there is a tar ball, but I'm loatherd to mix tarballs with an otherwise rpm ghostscript/foomatic/cups printer setup. I suppose I might try building an rpm of the tarball but I know sod all about how to. I suppose the proper attitude is to say , well this is my chance to learn. It really wants someone with the knowledge to fix the fault and post new gimpprint / libgimpprint rpms asap. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
Stephen Kuhn wrote: On Wed, 2002-12-04 at 19:37, Derek Jennings wrote: SNIP Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John John If there is a problem with the gimpprint driver for your printer type why not mention it on the printer forum at Mandrake Club? http://www.mandrakeclub.com/modules.php?name=Splatt_Forum You do not need a membership, and printer questions are often answered by Till Klampetter Mandrake's printer guru. derek What about completely removing the printer drivers from John's distro, then re-installing them via the MCC Package Management? Wouldn't this be so much easier than mucking around with RPM's that will break his box? ...and I rather forgot what exactly was the reasoning behind installing new drivers in the first place... As I say, the M9.0 version of gimpprint/libgimpprint the one is a gui for the backend driver, is broken, it worked up till M8.2 quite well, but someone tinkered with it and now it's broken,I'm basically waiting on a bugfix update,which is really why I went for the cooker variety, not knowing the risks. There is a tarball but I am loathed to mix rpm's and tarballs, remember gimpprint is a ghostscript pluggin and has to work with it and I don't want something installed I cannot take off again. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
On Tuesday December 3 2002 07:09 pm, John Richard Smith wrote: That only leaves the cookers, How risky is it going to be, I mean , what other choice left to me is there. What have I got to loose, a buggered up printer maybe, a sodded up oS, well if the worse comes to the worse I can put that back, and well a printer , not very likely to do any lasting damage to the hardware other than the printer itself ? First I doubt if newer rpms are gonna fix your problem. BUT if you're bound and determined, get the cooker src.rpms and see if they'll rebuild on your system. If you get missing deps, use the ones for your mandrake version whenever possible. I highly doubt you'll be succesful in this on anything but Mdk 9.0. If the src.rpm won't build, then it's almost certain installing the cooker binary rpms you need will fsck up your system. You won't hurt your hardware tho. ftp://sunsite.uio.no/pub/unix/Linux/Mandrake/Mandrake-devel/cooker/SRPMS -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] rpm install failures
I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
On Tuesday December 3 2002 02:28 pm, Stephen Kuhn wrote: What about using: rpm -Uivh --force --no-deps ...as the command instead? Usually a _very_ bad idea. --force is useful if you're installing an rpm over an rpm of the same version because you screwed it up. --nodeps is useful if you're completely confident that all deps are met, and it's only a packaging problem. Both switches together is most often a receipe for disaster. As always, anything you do as root, and it's repercussions, are your own fault. As is software choice. There's almost always very good reasons that deps and conflicts are reported when tryin to install some packages, specially if you've tainted your system http://www.tux.org/lkml/#export-tainted -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
Derek Jennings wrote: On Tuesday 03 Dec 2002 6:57 pm, John Richard Smith wrote: I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John I assume you realise that these are Cooker packages, and --forcing them to install will very likely break your system? No. I take it that this is why the install was refused then. If you really really want to use gimpprint-4.2.3-5mdk.i586.rpm instead of gimpprint-4.2.3-3.2mdk as available in the latest Mandrake 9.0 Updates, Then how does one know which packages to download. then the safest way of doing it is to download the .src.rpm and recompile it for your system with rpm --rebuild gimpprint-4.2.3-5mdk.src.rpm I couldn't find any src.rpm versions, rpmfind didn't come up with any. Then, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm are these also cooker jobs. because these libgimpprint are the actual drivers, gimpprint is just a graphical front end and it's the libgimpprint driver files that are broken in M9.0 standard install versions. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
On Tuesday 03 Dec 2002 10:54 pm, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 6:57 pm, John Richard Smith wrote: I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John I assume you realise that these are Cooker packages, and --forcing them to install will very likely break your system? No. I take it that this is why the install was refused then. If you really really want to use gimpprint-4.2.3-5mdk.i586.rpm instead of gimpprint-4.2.3-3.2mdk as available in the latest Mandrake 9.0 Updates, Then how does one know which packages to download. then the safest way of doing it is to download the .src.rpm and recompile it for your system with rpm --rebuild gimpprint-4.2.3-5mdk.src.rpm I couldn't find any src.rpm versions, rpmfind didn't come up with any. Then, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm are these also cooker jobs. because these libgimpprint are the actual drivers, gimpprint is just a graphical front end and it's the libgimpprint driver files that are broken in M9.0 standard install versions. John If you want the latest drivers all you have to do is run Mandrake Update (assuming you have an update source defined) Or from the command line urpmi.update -a to update your source lists then urpmi --update --auto-select to install any available updates (I recommend using the command line. You will learn a lot more about how urpmi works in the process) However now that you have deleted the original RPMs Mandrake Update will not know you are interested in these RPMS so now you have to do urpmi.update -a urpmi gimpprint (The other RPMS will be installed automatically since they depend on gimpprint) As Tom Brinkman's post pointed out. Anytime rpm fails with a dependency, there is usually a very good reason. I learned from (bitter) experience not to use --force or --no-deps without good reason. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
Derek Jennings wrote: On Tuesday 03 Dec 2002 10:54 pm, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 6:57 pm, John Richard Smith wrote: I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John I assume you realise that these are Cooker packages, and --forcing them to install will very likely break your system? No. I take it that this is why the install was refused then. If you really really want to use gimpprint-4.2.3-5mdk.i586.rpm instead of gimpprint-4.2.3-3.2mdk as available in the latest Mandrake 9.0 Updates, Then how does one know which packages to download. then the safest way of doing it is to download the .src.rpm and recompile it for your system with rpm --rebuild gimpprint-4.2.3-5mdk.src.rpm I couldn't find any src.rpm versions, rpmfind didn't come up with any. Then, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm are these also cooker jobs. because these libgimpprint are the actual drivers, gimpprint is just a graphical front end and it's the libgimpprint driver files that are broken in M9.0 standard install versions. John If you want the latest drivers all you have to do is run Mandrake Update (assuming you have an update source defined) Or from the command line urpmi.update -a to update your source lists then urpmi --update --auto-select to install any available updates (I recommend using the command line. You will learn a lot more about how urpmi works in the process) However now that you have deleted the original RPMs Mandrake Update will not know you are interested in these RPMS so now you have to do urpmi.update -a urpmi gimpprint (The other RPMS will be installed automatically since they depend on gimpprint) As Tom Brinkman's post pointed out. Anytime rpm fails with a dependency, there is usually a very good reason. I learned from (bitter) experience not to use --force or --no-deps without good reason. Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
On Wednesday 04 Dec 2002 12:33 am, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 10:54 pm, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 6:57 pm, John Richard Smith wrote: I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John I assume you realise that these are Cooker packages, and --forcing them to install will very likely break your system? No. I take it that this is why the install was refused then. If you really really want to use gimpprint-4.2.3-5mdk.i586.rpm instead of gimpprint-4.2.3-3.2mdk as available in the latest Mandrake 9.0 Updates, Then how does one know which packages to download. then the safest way of doing it is to download the .src.rpm and recompile it for your system with rpm --rebuild gimpprint-4.2.3-5mdk.src.rpm I couldn't find any src.rpm versions, rpmfind didn't come up with any. Then, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm are these also cooker jobs. because these libgimpprint are the actual drivers, gimpprint is just a graphical front end and it's the libgimpprint driver files that are broken in M9.0 standard install versions. John If you want the latest drivers all you have to do is run Mandrake Update (assuming you have an update source defined) Or from the command line urpmi.update -a to update your source lists then urpmi --update --auto-select to install any available updates (I recommend using the command line. You will learn a lot more about how urpmi works in the process) However now that you have deleted the original RPMs Mandrake Update will not know you are interested in these RPMS so now you have to do urpmi.update -a urpmi gimpprint (The other RPMS will be installed automatically since they depend on gimpprint) As Tom Brinkman's post pointed out. Anytime rpm fails with a dependency, there is usually a very good reason. I learned from (bitter) experience not to use --force or --no-deps without good reason. Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John If you were not offered updates, then maybe you do not have an update source defined. This command will give you one urpmi.addmedia --update Updates ftp://ftp.gwdg.de/pub/linux/mandrake/updates/9.0/RPMS with ../base/hdlist.cz (That command is all one line) Or alternatively you can look at the RPMs in the download source directly ftp://ftp.gwdg.de/pub/linux/mandrake/updates/9.0/RPMS derek Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] rpm install failures
Derek Jennings wrote: On Wednesday 04 Dec 2002 12:33 am, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 10:54 pm, John Richard Smith wrote: Derek Jennings wrote: On Tuesday 03 Dec 2002 6:57 pm, John Richard Smith wrote: I am trying to update a printer driver, having removed the old ones. [root@localhost root]# rpm -i --force /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm /mnt/ext2-vol6/downloads2/libgimpprint1-4.2.3-5mdk.i586.rpm: read manifest failed: Success [root@localhost root]# why won't it install the package ? I have to install 3 packages, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm gimpprint-4.2.3-5mdk.i586.rpm in this order, I think. John I assume you realise that these are Cooker packages, and --forcing them to install will very likely break your system? No. I take it that this is why the install was refused then. If you really really want to use gimpprint-4.2.3-5mdk.i586.rpm instead of gimpprint-4.2.3-3.2mdk as available in the latest Mandrake 9.0 Updates, Then how does one know which packages to download. then the safest way of doing it is to download the .src.rpm and recompile it for your system with rpm --rebuild gimpprint-4.2.3-5mdk.src.rpm I couldn't find any src.rpm versions, rpmfind didn't come up with any. Then, libgimpprint1-4.2.3-5mdk.i586.rpm libgimpprint1-devel-4.2.3-5mdk.i586.rpm are these also cooker jobs. because these libgimpprint are the actual drivers, gimpprint is just a graphical front end and it's the libgimpprint driver files that are broken in M9.0 standard install versions. John If you want the latest drivers all you have to do is run Mandrake Update (assuming you have an update source defined) Or from the command line urpmi.update -a to update your source lists then urpmi --update --auto-select to install any available updates (I recommend using the command line. You will learn a lot more about how urpmi works in the process) However now that you have deleted the original RPMs Mandrake Update will not know you are interested in these RPMS so now you have to do urpmi.update -a urpmi gimpprint (The other RPMS will be installed automatically since they depend on gimpprint) As Tom Brinkman's post pointed out. Anytime rpm fails with a dependency, there is usually a very good reason. I learned from (bitter) experience not to use --force or --no-deps without good reason. Thanks everyone for the advice, I achieved the result, unfortunately no update was offered. I only got the standard M9.0 install, which are broken. I was connected to the net. I guess I'm down to forcing cooker installs, as an OS with a broken printer driver is useless, so I'm going to have to take the risk. John If you were not offered updates, then maybe you do not have an update source defined. This command will give you one urpmi.addmedia --update Updates ftp://ftp.gwdg.de/pub/linux/mandrake/updates/9.0/RPMS with ../base/hdlist.cz (That command is all one line) Or alternatively you can look at the RPMs in the download source directly ftp://ftp.gwdg.de/pub/linux/mandrake/updates/9.0/RPMS derek OK, been there downloaded and installed, gimpprint-4.2.3-3.2mdk.i586.rpm lingimpprint1-4.2.3-3.2mdk.i586.rpm libgimpprint1-devel-4.2.3-3.2mdk.i586.rpm which are all mandrake , not cooker rpms, but bad luck, these are just as broken and M9.0's choices. That only leaves the cookers, How risky is it going to be, I mean , what other choice left to me is there. What have I got to loose, a buggered up printer maybe, a sodded up oS, well if the worse comes to the worse I can put that back, and well a printer , not very likely to do any lasting damage to the hardware other than the printer itself ? John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
