Getting Scribus on Ubuntu/Kubuntu up and running: Difference between revisions
No edit summary |
|||
Line 7: | Line 7: | ||
Scribus is packaged for Debian GNU/Linux by Oleksandr (Alex) Moskalenko <malex@tagancha.org>. Please contact me at that email if you have questions that do not belong to the Debian or Scribus BTS (Bug Tracking System) or for comments about this page. | Scribus is packaged for Debian GNU/Linux by Oleksandr (Alex) Moskalenko <malex@tagancha.org>. Please contact me at that email if you have questions that do not belong to the Debian or Scribus BTS (Bug Tracking System) or for comments about this page. | ||
If you'd like to stay on the leading edge of Scribus development please use upstream repositories as I have to upload scribus into Debian through a sponsor and it usually takes weeks to get an upload in. Because of that the official packages are usually well-behind what is available in the upstream repositories. Please try a package from an upstream directory to test the bug you discovered as it might have already been fixed and new package is available. This is called "the Scribus magic (TM)". | If you'd like to stay on the leading edge of Scribus development please use upstream repositories as I have to upload scribus into Debian through a sponsor and it usually takes weeks to get an upload in. Because of that the official packages are usually well-behind what is available in the upstream repositories. Please try a package from an upstream directory to test the bug you discovered as it might have already been fixed and new package is available. This is called "the Scribus magic (TM)". Please note that the repositories listed below are IDENTICAL in order to provide a backup and additional bandwidth if needed. The contain packages for Debian stable,testing,unstable and Ubuntu hoary,breezy distributions. | ||
<p> | <p> | ||
To use | To use our upstream repositories: | ||
Add the appropriate lines from the following list to your /etc/apt/sources.list file: | |||
<pre> | <pre> | ||
deb http://debian.scribus.net/debian/ unstable/ | # debian.scribus.net - Primary repository | ||
deb-src http://debian.scribus.net/debian/ unstable/ | # Debian stable | ||
deb http://debian.scribus.net/debian/ stable main non-free contrib | |||
deb-src http://debian.scribus.net/debian/ stable main non-free contrib | |||
# Debian testing | |||
deb http://debian.scribus.net/debian/ testing main non-free contrib | |||
deb-src http://debian.scribus.net/debian/ testing main non-free contrib | |||
# Debian unstable | |||
deb http://debian.scribus.net/debian/ unstable main non-free contrib | |||
deb-src http://debian.scribus.net/debian/ unstable main non-free contrib | |||
# Ubuntu hoary | |||
deb http://debian.scribus.net/debian/ hoary main restricted | |||
deb-src http://debian.scribus.net/debian/ hoary main restricted | |||
# Ubuntu breezy | |||
deb http://debian.scribus.net/debian/ breezy main restricted | |||
deb-src http://debian.scribus.net/debian/ breezy main restricted | |||
deb http://debian.tagancha.org/ | # debian.tagancha.org - Backup repository | ||
deb-src http://debian.tagancha.org/ | # Debian stable | ||
</pre | deb http://debian.tagancha.org/debian/ stable main non-free contrib | ||
deb-src http://debian.tagancha.org/debian/ stable main non-free contrib | |||
# Debian testing | |||
deb http://debian.tagancha.org/debian/ testing main non-free contrib | |||
deb-src http://debian.tagancha.org/debian/ testing main non-free contrib | |||
# Debian unstable | |||
deb http://debian.tagancha.org/debian/ unstable main non-free contrib | |||
deb-src http://debian.tagancha.org/debian/ unstable main non-free contrib | |||
# Ubuntu hoary | |||
deb http://debian.tagancha.org/debian/ hoary main restricted | |||
deb-src http://debian.tagancha.org/debian/ hoary main restricted | |||
# Ubuntu breezy | |||
deb http://debian.tagancha.org/debian/ breezy main restricted | |||
deb-src http://debian.tagancha.org/debian/ breezy main restricted | |||
</pre | |||
Once you added the sources lines you can run | Once you added the sources lines you can run | ||
<pre> | <pre> | ||
aptitude install scribus | aptitude install scribus scribus-cvs | ||
</pre> | </pre> | ||
Substituted aptitude for apt-get if you wish. "scribus" package is for 1.2.xcvs stable series. You can or even should also install "scribus-cvs" package to try the new 1.3cvs series, which is pretty stable and much more featureful than 1.2. scribus-cvs package installs into /usr/local hierarchy and can be installed in parallel with the scribus package, so you can have both and even run them at the same time. However, DO NOT file bug reports about the 1.3 scribus-cvs package or any packages in the upstream repository that are newer then what is in Debian proper in the Debian BTS. Only use Debian BTS for the packages that are in Debian. If you have a Scribus issue, which is not related to Debian packaging then it is much more preferable if you use scribus BTS for reporting bugs. Go to http://bugs.scribus.net and have fun. | Substituted aptitude for apt-get if you wish. "scribus" package is for 1.2.xcvs stable series. You can or even should also install "scribus-cvs" package to try the new 1.3cvs series, which is pretty stable and much more featureful than 1.2. scribus-cvs package installs into /usr/local hierarchy and can be installed in parallel with the scribus package, so you can have both and even run them at the same time. However, DO NOT file bug reports about the 1.3 scribus-cvs package or any packages in the upstream repository that are newer then what is in Debian proper in the Debian BTS. Only use Debian BTS for the packages that are in Debian. If you have a Scribus issue, which is not related to Debian packaging then it is much more preferable if you use scribus BTS for reporting bugs. Go to http://bugs.scribus.net and have fun. | ||
=== Other branches === | === Other branches === | ||
'''EVERYTHING BELOW HAS BEEN RENDERED OBSOLETE BY THE NEW REPOSITORIES''' | |||
I have built packages for every branch of Debian proper (sid/etch/sarge) and for Ubuntu (breezy/hoary). These packages are currently located at http://debian.tagancha.org/scribus/other. I am in the process of setting up a complete automatic repository that can be used for apt-pinning and whatever else is possible with the official repositories. Stay tuned. [[User:Malex|Malex]] 18:06, 7 Jul 2005 (UTC) | I have built packages for every branch of Debian proper (sid/etch/sarge) and for Ubuntu (breezy/hoary). These packages are currently located at http://debian.tagancha.org/scribus/other. I am in the process of setting up a complete automatic repository that can be used for apt-pinning and whatever else is possible with the official repositories. Stay tuned. [[User:Malex|Malex]] 18:06, 7 Jul 2005 (UTC) |
Revision as of 21:44, 7 July 2005
Installation • Usage • PDF issues • Imposition • Other |
"Debian" name here encompasses Debian proper (unstable/testing/stable or sid/etch/sarge) and Ubuntu breezy/hoary.
Installation
Scribus is packaged for Debian GNU/Linux by Oleksandr (Alex) Moskalenko <malex@tagancha.org>. Please contact me at that email if you have questions that do not belong to the Debian or Scribus BTS (Bug Tracking System) or for comments about this page.
If you'd like to stay on the leading edge of Scribus development please use upstream repositories as I have to upload scribus into Debian through a sponsor and it usually takes weeks to get an upload in. Because of that the official packages are usually well-behind what is available in the upstream repositories. Please try a package from an upstream directory to test the bug you discovered as it might have already been fixed and new package is available. This is called "the Scribus magic (TM)". Please note that the repositories listed below are IDENTICAL in order to provide a backup and additional bandwidth if needed. The contain packages for Debian stable,testing,unstable and Ubuntu hoary,breezy distributions.
To use our upstream repositories: Add the appropriate lines from the following list to your /etc/apt/sources.list file:
# debian.scribus.net - Primary repository # Debian stable deb http://debian.scribus.net/debian/ stable main non-free contrib deb-src http://debian.scribus.net/debian/ stable main non-free contrib # Debian testing deb http://debian.scribus.net/debian/ testing main non-free contrib deb-src http://debian.scribus.net/debian/ testing main non-free contrib # Debian unstable deb http://debian.scribus.net/debian/ unstable main non-free contrib deb-src http://debian.scribus.net/debian/ unstable main non-free contrib # Ubuntu hoary deb http://debian.scribus.net/debian/ hoary main restricted deb-src http://debian.scribus.net/debian/ hoary main restricted # Ubuntu breezy deb http://debian.scribus.net/debian/ breezy main restricted deb-src http://debian.scribus.net/debian/ breezy main restricted # debian.tagancha.org - Backup repository # Debian stable deb http://debian.tagancha.org/debian/ stable main non-free contrib deb-src http://debian.tagancha.org/debian/ stable main non-free contrib # Debian testing deb http://debian.tagancha.org/debian/ testing main non-free contrib deb-src http://debian.tagancha.org/debian/ testing main non-free contrib # Debian unstable deb http://debian.tagancha.org/debian/ unstable main non-free contrib deb-src http://debian.tagancha.org/debian/ unstable main non-free contrib # Ubuntu hoary deb http://debian.tagancha.org/debian/ hoary main restricted deb-src http://debian.tagancha.org/debian/ hoary main restricted # Ubuntu breezy deb http://debian.tagancha.org/debian/ breezy main restricted deb-src http://debian.tagancha.org/debian/ breezy main restricted </pre Once you added the sources lines you can run <pre> aptitude install scribus scribus-cvs
Substituted aptitude for apt-get if you wish. "scribus" package is for 1.2.xcvs stable series. You can or even should also install "scribus-cvs" package to try the new 1.3cvs series, which is pretty stable and much more featureful than 1.2. scribus-cvs package installs into /usr/local hierarchy and can be installed in parallel with the scribus package, so you can have both and even run them at the same time. However, DO NOT file bug reports about the 1.3 scribus-cvs package or any packages in the upstream repository that are newer then what is in Debian proper in the Debian BTS. Only use Debian BTS for the packages that are in Debian. If you have a Scribus issue, which is not related to Debian packaging then it is much more preferable if you use scribus BTS for reporting bugs. Go to http://bugs.scribus.net and have fun.
Other branches
EVERYTHING BELOW HAS BEEN RENDERED OBSOLETE BY THE NEW REPOSITORIES
I have built packages for every branch of Debian proper (sid/etch/sarge) and for Ubuntu (breezy/hoary). These packages are currently located at http://debian.tagancha.org/scribus/other. I am in the process of setting up a complete automatic repository that can be used for apt-pinning and whatever else is possible with the official repositories. Stay tuned. Malex 18:06, 7 Jul 2005 (UTC)
Sarge-specific issues
The latest gcc packages in sarge are at 3.4.3 version and the current unstable/testing have already diverged. Fortunately, as of early July 2005 sarge is not that far behind and you can get my package to work on your system by a simple package rebuild. Make sure that you have the deb-src lines for scribus repositories uncommented and run the following commands:
The cool way (TM) - as root or set up sudo for yourself as a user:
apt-get install apt-build
Answer questions about your CPU and stuff - see an excellent document at http://julien.danjou.info/article-apt-build.html)
apt-build update apt-build install scribus (or scribus-cvs)
Without apt-build - as root:
apt-get build-dep scribus-cvs (or scribus)
apt-get source -b scribus scribus-cvs
Anoter way - as root:
apt-get install devscripts build-essential fakeroot
Note: This creates a minimal build environment.
apt-get source scribus-cvs (or "scribus" instead of "scribus-cvs")
apt-get build-dep scribus-cvs (or scribus)
cd scribus.... or scribus-cvs...
At this moment these are scribus-1.2.1+cvs20050620 and scribus-cvs-1.3+cvs20050629), but it's just an example. Use the actual directory names.
debuild -us -uc
cd ..
dpkg -i scribus_.... or scribus-cvs_....
At the moment these are scribus_1.2.1+cvs20050620-2_i386.deb and scribus-cvs_1.3+cvs20050629-1_i386.deb, but use the actual file names.
Voila - you have a scribus (1.2) or scribus-cvs (1.3) package built and optimized for your Sarge (Debian 3.1 a.k.a. stable) system.
Other Debian-based distributions
Please post your experiences about the Scribus availability on other Debian-based distributions. If you just want to get the latest package on one of them - follow the source package rebuild procedure above.
Ubuntu Linux Hoary (5.04)
Using the 1.3 CVS and the 1.2.2 CVS from the Debian CVS builds and rebuilding from source works fine for me. Originally I just tried to install the these packages using just apt-get install scribus but with Ubuntu had some major dependency errors with gcc etc.
With the help of the scribus list, I now use (admittedly a slight variant of the building from source for Debian) notes, ie, as root, or with sudo:-
apt-get source -b scribus-cvs
This alerted me to many dev libraries that were missing. Ubuntu doesn't (not surprisingly) have many dev libs installed on the std build. This command does the actual complie. If you use 'scribus-cvs' you will currently get the v1.3 dev series build, whereas if you use just 'scribus' you will get the stabile 1.2.2 release ie the 1.2 CVS series builds.
Once these were all installed, I did :-
apt-get build-dep scribus-cvs
This builds the scribus-cvs package for you from source. It took around half an hour, and spews out a lot of messages. Eventually, you should find a scribus-cvs deb in the directory that you are working in.
Then just do
apt-get install scribus-cvs
& Bingo !
As I said before, I'm not a Debian/Ubuntu expert and I'm sure there may be betters ways of doing this. The scribus packages do however work fine on Ubuntu when building from source. I have had NO errors part from std occasional crashes of the CVS package.
NOTE
It seems from experimentation that you should stick with either the official install method as mentioned above, or the method I use, BUT NOT BOTH !