I tried downloading and installing the rpm today but still no go. I am reading where some people are running .42 but I can't get anything to happen. .41 still installs and runs fine. Any word?
Thanks
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
On Fri, Jul 29, 2005 at 07:39:12AM -0700, les kraut wrote:
I tried downloading and installing the rpm today but still no go. I am reading where some people are running .42 but I can't get anything to happen. .41 still installs and runs fine. Any word?
I can confirm this issue. A user here at work on SuSE9.2 installed the static rpm version but ran into the same error that other SuSE and Fedora users have encountered. The autopackage version also failed to install (there was an error with starting the graphical installer).
Presumably the 0.42.1 release will solve this issue, however given how many people run Fedora and SuSE, I'm a little concerned about the number of people that may be experiencing this problem.
Meanwhile, if you're anxious to get it installed, you could try installing from source, or else keep an eye on the bug tracker, as that's where I expect the fix will first be found.
Bryce
On Fri, 29 Jul 2005 13:07:17 -0700, Bryce Harrington wrote:
I can confirm this issue. A user here at work on SuSE9.2 installed the static rpm version but ran into the same error that other SuSE and Fedora users have encountered. The autopackage version also failed to install (there was an error with starting the graphical installer).
Bryce, can you give me more details about how autopackage failed to start? We should fix this.
thanks -mike
On Sat, Jul 30, 2005 at 10:47:48PM +0100, Mike Hearn wrote:
On Fri, 29 Jul 2005 13:07:17 -0700, Bryce Harrington wrote:
I can confirm this issue. A user here at work on SuSE9.2 installed the static rpm version but ran into the same error that other SuSE and Fedora users have encountered. The autopackage version also failed to install (there was an error with starting the graphical installer).
Bryce, can you give me more details about how autopackage failed to start? We should fix this.
it seemed to go very well, but then suddenly failed on starting up the autopackage interface. I don't remember the exact error mesage, but we were able to assure ourselves it was within the autopackage procedure, not Inkscape.
This was on a fairly stock SuSE 9.2 distro. The same guy that we've gotten suse/autopackage/inkscape testing issues from before.
Bryce
participants (4)
-
Alexandre Prokoudine -
Bryce Harrington -
les kraut -
Mike Hearn