Package Details: scribus-svn 25998-1

Git Clone URL: https://aur.archlinux.org/scribus-svn.git (read-only, click to copy)
Package Base: scribus-svn
Description: A desktop publishing program - Version from SVN
Upstream URL: http://www.scribus.net
Licenses: GPL, LGPL
Conflicts: scribus
Provides: scribus
Submitter: None
Maintainer: migrev
Last Packager: migrev
Votes: 49
Popularity: 0.085374
First Submitted: 2008-04-27 21:07 (UTC)
Last Updated: 2024-01-19 08:41 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »

helldrak commented on 2018-08-23 09:28 (UTC)

Hi everyone, First of all, thanks for your tremendous work – it’s always a pleasure to rely effortlessly on AUR packages ;). Just to signal that the latest upgrade of Arch now provides libicuuc.so.62 (https://www.archlinux.org/packages/multilib/x86_64/lib32-icu/files/) and thus that scribus-svn can no longer be launched :

scribus: error while loading shared libraries: libicuuc.so.61: cannot open shared object file: No such file or directory

All the best,

haawda commented on 2018-05-03 00:29 (UTC)

bm456, it builds fine here (revision 22517), and your past is too short to see what is happening on your side.

bm456 commented on 2018-05-02 00:03 (UTC)

https://p.teknik.io/Qa6Gv

Kunda commented on 2018-04-02 10:54 (UTC)

Thanks again @haawada

haawda commented on 2018-03-31 21:38 (UTC)

Upstream bug, which is already reported. https://bugs.scribus.net/view.php?id=15236

I will try the suggested fix.

bm456 commented on 2018-03-30 21:38 (UTC) (edited on 2018-03-30 21:39 (UTC) by bm456)

i got this https://p.teknik.io/7hyTu

svn snaps: 22460

icu: 61.1 hardbuzz-icu: 1.7.6

haawda commented on 2018-03-17 12:59 (UTC)

makepkg will automatically bump to the latest svn version.

Kunda commented on 2018-03-16 20:38 (UTC)

@haawada how can I update PKGBUILD on my local system and bump the latest svn version ?

haawda commented on 2018-02-14 21:07 (UTC) (edited on 2018-02-14 21:09 (UTC) by haawda)

Cite from the guidelines:

Note: VCS packages are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you. AUR maintainers should not commit mere pkgver bumps.

If it is forbidden, it is also forbidden once a month. See also the comment of eschwarz on the AUR page of dunst-git.

And I agree the rule is ridiculous, but it is a rule. That said, I run the bot privately almost daily, so I most probably will detect build failures.

severach commented on 2018-02-14 20:39 (UTC)

Would once a month work? I update most of my git packages every version to ensure the git packages are updated no less often than the non git packages.

The problem with updating every commit is that non developers don't need it and developers are already doing it. The constant stream of commit update notifications from AUR doesn't add any value.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »