Hi,
please orphan the package
[http://aur.archlinux.org/packages.php?ID=18241].
The maintainer hasn't respond to any comment. I also sent him an email
a few days ago, but he hasn't answered.
Cheers
Francesco Groccia wrote:
Hi,
please orphan the package
[http://aur.archlinux.org/packages.php?ID=18241].
The maintainer hasn't respond to any comment. I also sent him an email
a few days ago, but he hasn't answered.
Cheers
Done
Hello all,
It is also time for me to resign as a Trusted User. I've been here for
two years already, and it's been quite enjoyable. But now my time
schedule is getting too demanding, and I prefer to leave the field for
new TUs. Of course, I will continue to contribute to the Arch community
as a d
2009/4/10 Firmicus :
> pdfedit
adopted
--
Andrea `BaSh` Scarpino
Arch Linux Developer
According to
http://wiki.archlinux.org/index.php/Gnome_package_guidelines#GTK_Icon_cache
packages which install icons in /usr/share/icons/hicolor should depend on
hicolor-icon-theme and invoke gtk-update-icon-cache.
I've made a namcap module [1] which checks for the existence of the
/usr/share/ic
Please delete this package, it's included in extra for a while now:
http://aur.archlinux.org/packages.php?ID=16498
On Fri, Apr 10, 2009 at 3:05 PM, Jan de Groot wrote:
> Please delete this package, it's included in extra for a while now:
> http://aur.archlinux.org/packages.php?ID=16498
>
done
On Fri, 2009-04-10 at 20:24 +0530, Abhishek Dasgupta wrote:
> According to
> http://wiki.archlinux.org/index.php/Gnome_package_guidelines#GTK_Icon_cache
>
> packages which install icons in /usr/share/icons/hicolor should depend on
> hicolor-icon-theme and invoke gtk-update-icon-cache.
>
> I've ma
Hi,
What is the current policy for out date packages in the community
repo. Iirc there were ten or so such packages that fall into this
zone. Now while this isnt many, there packages have no hope of being
updated, unless a kindly TU takes pity on them. Could they please be
moved back to the aur wh
2009/4/10 Laurie Clark-Michalek :
> What is the current policy for out date packages in the community
> repo. Iirc there were ten or so such packages that fall into this
> zone. Now while this isnt many, there packages have no hope of being
> updated, unless a kindly TU takes pity on them. Could th
=
= Integrity Check i686 of community =
=
Performing integrity checks...
==> parsing pkgbuilds
==> checking mismatches
==> checking archs
==> checking dependencies
==> checking makedepends
==> checking for circular dependenci
===
= Integrity Check x86_64 of community =
===
Performing integrity checks...
==> parsing pkgbuilds
==> checking mismatches
==> checking archs
==> checking dependencies
==> checking makedepends
==> checking for circular depe
Hi,
I'll be taking over Nexuiz from Swiergot and I'm working on tidying up
and updating the PKGBUILD right now.
(related issue: http://bbs.archlinux.org/viewtopic.php?id=69617)
Is there any way to build the package on the community upload server?
There is a single PKGBUILD for both architectures
> Actually, I'll probably just submit a feature request for a "--config"
> option.
Done: http://bugs.archlinux.org/task/14178
Xyne wrote:
Actually, I'll probably just submit a feature request for a "--config"
option.
Done: http://bugs.archlinux.org/task/14178
That option is available in git.
Also, have a look at this:
http://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot
Allan
2009/4/11 Jan de Groot :
> Looks great, and really saves me doing some work (or bugs sneaking in
> new versions of packages).
>
> This dependency check on hicolor-icon-theme, does it traverse down the
> dependency tree, or does it only look at what is in depends=()?
It just looks at depends() righ
17 matches
Mail list logo
