Oleksandr Moskalenko schrieb:
I cannot confirm
this report on the current 1.2.1+cvs. Please update your package and test for
this again. If you don't mind you could get the latest package from one of the
two repositories I maintain upstream as there is an unfortunate slowdown in
getting an updated package into Unstable at the moment. Add the following
source lines to you /etc/apt/sources.list:
deb http://debian.scribus.net/debian/ unstable/
deb-src http://debian.scribus.net/debian/ unstable/
deb http://debian.tagancha.org/scribus unstable/
deb-src http://debian.tagancha.org/scribus unstable/
Run the usual "apt-get update; apt-get install scribus". As I see that you
have a stable system. Since Testing/Unstable has libgcc1 at 4.0.0 now, if you
really don't want to install anything from Testing you'll have to rebuild the
package. It's not hard. See my message to the Scribus mailing list at
http://irc.altmuehlnet.de/pipermail/scribus/2005-June/011710.html. By the way
- new 1.3cvs series is pretty usable already. You can install scribus-cvs
package from the upstream repository in parallel with the official scribus
package and try it. Some people already use it for production.
Thank you for your attention to this bug.
As you supposed, I do not want to install from unstable at this time.
Thanks also for your detailed work instruction detailed via the supplied
URL.
It will certainly take me some time to do this, since I first want to
understand what the instructions do. The other day, another debian
developer asked me to add an entry to the apt sources list, and then
pushed some packet not-from-stable on my machine without telling me
beforehand what happend, which -- while it solved the problem at hand --
I did not appreciate. So I have to be careful before adventuring around
with commands I don't understand yet. Reading und understanding all the
man-pages and other doc's takes much time, which I cannot supply in a
short time frame. I'm not a developer in the debian sense so far, still
having blanks in my understanding of the system. I hope you understand
this. Maybe it is possible to verify the bug with the stable version?
Apparently, filing a bug -- as valued as it seems to be -- is the easy
part, as opposed to dealing with the required fallout...
Regards,
Peer
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
