[aur-general] Quick Access Plasmoid appears more than once in AUR

2009-03-27 Thread Bram Schoenmakers
Hello,

The Quick Access Plasmoid appears more than once in AUR. [1] is orphaned but 
has more votes. [2] still has a maintainer. So I would suggest to remove [1] 
from AUR.

Kind regards,

[1] http://aur.archlinux.org/packages.php?ID=18854
[2] http://aur.archlinux.org/packages.php?ID=18893

-- 
Bram Schoenmakers

What is mind? No matter. What is matter? Never mind.
(Punch, 1855)


Re: [aur-general] Quick Access Plasmoid appears more than once in AUR

2009-03-27 Thread Daenyth Blank
On Fri, Mar 27, 2009 at 07:03, Bram Schoenmakers
li...@bramschoenmakers.nl wrote:
 Hello,

 The Quick Access Plasmoid appears more than once in AUR. [1] is orphaned but
 has more votes. [2] still has a maintainer. So I would suggest to remove [1]
 from AUR.

 Kind regards,

 [1] http://aur.archlinux.org/packages.php?ID=18854
 [2] http://aur.archlinux.org/packages.php?ID=18893

 --
 Bram Schoenmakers

 What is mind? No matter. What is matter? Never mind.
 (Punch, 1855)


kdeplasma-quickaccess deleted as it doesn't match the common naming conventions.


Re: [aur-general] Arch's Vim Failings Solution Suggestions

2009-03-27 Thread Kessia 'even' Pinheiro
Hi!

On Fri, Mar 20, 2009 at 12:19 PM, Tobias Kieslich tob...@justdreams.de wrote:
 Hi,

        I was reaaly busy lately so I wasn't able to push tha changes I made
 locally.
 I got rid of gvimrc in etc, I still wonder thought why they would
 have such a file upstream. Also virc is gone. Since we won't ship a vim
 based vi package anymore.

Why not?

 vi will be besad on nvi. that has lot's of advantages:
 - smaller for the iso
 - no waiting on testing that stalls vim and gvim
 - vi and vim are separated

Why base vi on nvi? nvi aren't updated (on website) since 4/14/01. The
last version of vi was based on vim and its a bit different for
compiling options only. I think this is fine for most of users. I
think in vi like a vim without X improvements, so, why not still with
vi based on vim? Maybe you can provide nvi in a different package,
which can provide vi, i dont know.

 I was not aware of the double loading, a testbuild showed me that it is
 easy to build both packages (vim/gvim) without the path specified. The
 idea behind specifying was that gvim and vim use the same runtime but
 only one package ships it. So being explicit instead of implicit seemed
 like a good idea to me. Anyway, that will be gone as well in the new
 layout.

I understand the python idea here about explicit is better than
explicit, but vim dont need that, really.

 Hopefully tonight I can push them to testing. For the update people will
 be forced to remove the /usr/bin/vim and I think the /usr/bin/rview
 symlink manually. I tried to find a way around that, but no dice.

        -T


We are waiting until that...

Well, for not be so long, I made some packages for vi/vim/gvim with
ruby1.9, for that I made a patch for vim (sent for vim_dev today) and
uploaded for ArchLinux-BR repository [repo.archlinux-br.org]. I
uploaded the packages with the PKGBUILD's on my home
[http://even.archlinux-br.org/things/arch/packages]. For that I solve
some bugs from flyspray[#13937 and #12440] and also the questions in
the main of this thread. If you have any doubts, please reply me.

-- 
Kessia Pinheiro
Computer Science Student - Brazil, UFBa
Linux System Administrator
Arch Linux Trusted User
Linux User #389695
http://even.archlinux-br.org
---
X Fórum Internacional Software Livre - fisl10
24 a 27 de junho de 2009
PUCRS - Porto Alegre - Brasil


[aur-general] Integrity Check community i686 27-03-2009

2009-03-27 Thread repomaint

=
= Integrity Check i686 of community =
=

Performing integrity checks...
== parsing pkgbuilds
== checking mismatches
== checking archs
== checking dependencies
== checking makedepends
== checking for circular dependencies

Missing PKGBUILDs
---
/srv/abs/rsync/i686//community/CVS
/srv/abs/rsync/i686//community/daemons/CVS
/srv/abs/rsync/i686//community/devel/CVS
/srv/abs/rsync/i686//community/editors/CVS
/srv/abs/rsync/i686//community/emulators/CVS
/srv/abs/rsync/i686//community/games/CVS
/srv/abs/rsync/i686//community/gnome/CVS
/srv/abs/rsync/i686//community/i18n/CVS
/srv/abs/rsync/i686//community/kde/CVS
/srv/abs/rsync/i686//community/lib/CVS
/srv/abs/rsync/i686//community/modules/CVS
/srv/abs/rsync/i686//community/multimedia/CVS
/srv/abs/rsync/i686//community/multimedia/libflashsupport-oss/CVS
/srv/abs/rsync/i686//community/network/CVS
/srv/abs/rsync/i686//community/office/CVS
/srv/abs/rsync/i686//community/science/CVS
/srv/abs/rsync/i686//community/system/CVS
/srv/abs/rsync/i686//community/x11/CVS
/srv/abs/rsync/i686//community/xfce/CVS

Missing Dependencies
--
flumotion -- 'twisted-web'
open-vm-tools-modules -- 'kernel262.6.28'
eclipse-ve -- 'eclipse3.3'
cdfs -- 'kernel262.6.28'
virtualbox-ose-additions-modules -- 'kernel262.6.28'

Missing Makedepends
-
splix -- 'jbigkit'

Summary
-
Missing PKGBUILDs: 19
Invalid PKGBUILDs: 0
Mismatching PKGBUILD names:0
Duplicate PKGBUILDs:   0
Invalid archs: 0
Missing (make)dependencies:6
Repo hierarchy problems:   0
Circular dependencies: 0


[aur-general] Integrity Check community x86_64 27-03-2009

2009-03-27 Thread repomaint

===
= Integrity Check x86_64 of community =
===

Performing integrity checks...
== parsing pkgbuilds
== checking mismatches
== checking archs
== checking dependencies
== checking makedepends
== checking for circular dependencies

Missing PKGBUILDs
---
/srv/abs/rsync/x86_64//community/CVS
/srv/abs/rsync/x86_64//community/daemons/CVS
/srv/abs/rsync/x86_64//community/devel/CVS
/srv/abs/rsync/x86_64//community/editors/CVS
/srv/abs/rsync/x86_64//community/emulators/CVS
/srv/abs/rsync/x86_64//community/games/CVS
/srv/abs/rsync/x86_64//community/gnome/CVS
/srv/abs/rsync/x86_64//community/i18n/CVS
/srv/abs/rsync/x86_64//community/kde/CVS
/srv/abs/rsync/x86_64//community/lib/CVS
/srv/abs/rsync/x86_64//community/lib32/CVS
/srv/abs/rsync/x86_64//community/modules/CVS
/srv/abs/rsync/x86_64//community/multimedia/CVS
/srv/abs/rsync/x86_64//community/network/CVS
/srv/abs/rsync/x86_64//community/office/CVS
/srv/abs/rsync/x86_64//community/science/CVS
/srv/abs/rsync/x86_64//community/system/CVS
/srv/abs/rsync/x86_64//community/x11/CVS
/srv/abs/rsync/x86_64//community/xfce/CVS

Missing Dependencies
--
eclipse-ve -- 'eclipse3.3'
flumotion -- 'twisted-web'
gg2 -- 'arts'
perl-ldap -- 'perl-xml-sax-writer'
thunderbird-spell-pl -- 'thunderbird=2.0.0.19'
cdfs -- 'kernel262.6.28'

Missing Makedepends
-
splix -- 'jbigkit'

Summary
-
Missing PKGBUILDs: 19
Invalid PKGBUILDs: 0
Mismatching PKGBUILD names:0
Duplicate PKGBUILDs:   0
Invalid archs: 0
Missing (make)dependencies:7
Repo hierarchy problems:   0
Circular dependencies: 0


Re: [aur-general] Arch's Vim Failings Solution Suggestions

2009-03-27 Thread Tobias Kieslich
On Fri, 27 Mar 2009, Kessia 'even' Pinheiro wrote:

 Hi!
 
 On Fri, Mar 20, 2009 at 12:19 PM, Tobias Kieslich tob...@justdreams.de 
 wrote:
  Hi,
 
         I was reaaly busy lately so I wasn't able to push tha changes I made
  locally.
  I got rid of gvimrc in etc, I still wonder thought why they would
  have such a file upstream. Also virc is gone. Since we won't ship a vim
  based vi package anymore.
 
 Why not?
becuase it is obviously missleading and a fair sourcve of confusion.
 
  vi will be besad on nvi. that has lot's of advantages:
  - smaller for the iso
  - no waiting on testing that stalls vim and gvim
  - vi and vim are separated
 
 Why base vi on nvi? nvi aren't updated (on website) since 4/14/01. The
 last version of vi was based on vim and its a bit different for
 compiling options only. I think this is fine for most of users. I
 think in vi like a vim without X improvements, so, why not still with
 vi based on vim? Maybe you can provide nvi in a different package,
 which can provide vi, i dont know.
We will base that on the devel version from 2007, whic is stable and
works fine. Many other distros do the same. The advantages are listed
above and there is a long thread on the bugtracker. The main advantage
is that nvi is samller and as such much better suited for the base/core
stuff. And if we move vi to extra there is hardly any point for having a
vi over a vim package becuase the saving in space is marginal. Leaving
KISS alone ...

 
  I was not aware of the double loading, a testbuild showed me that it is
  easy to build both packages (vim/gvim) without the path specified. The
  idea behind specifying was that gvim and vim use the same runtime but
  only one package ships it. So being explicit instead of implicit seemed
  like a good idea to me. Anyway, that will be gone as well in the new
  layout.
 
 I understand the python idea here about explicit is better than
 explicit, but vim dont need that, really.
Well that iss the whole assumption theory. We 'assume' that the pathes
are the same, but then the beginning of every catastrophy is a bloody
assumption :P

 
  Hopefully tonight I can push them to testing. For the update people will
  be forced to remove the /usr/bin/vim and I think the /usr/bin/rview
  symlink manually. I tried to find a way around that, but no dice.
 
         -T
 
 
 We are waiting until that...
Yeah, there was a little issue called food poising, not pretty but well
it happened.

 
 Well, for not be so long, I made some packages for vi/vim/gvim with
 ruby1.9, for that I made a patch for vim (sent for vim_dev today) and
 uploaded for ArchLinux-BR repository [repo.archlinux-br.org]. I
I hope that will hit the vim upstream soon as it would help to keep the
package clean. Thanks for the work.

-T


Re: [aur-general] Integrity Check community i686 27-03-2009

2009-03-27 Thread Eric Bélanger
On Fri, Mar 27, 2009 at 4:10 PM,  repoma...@archlinux.org wrote:

 =
 = Integrity Check i686 of community =
 =

 Performing integrity checks...
 == parsing pkgbuilds
 == checking mismatches
 == checking archs
 == checking dependencies
 == checking makedepends
 == checking for circular dependencies

 Missing PKGBUILDs
 ---
 /srv/abs/rsync/i686//community/CVS
 /srv/abs/rsync/i686//community/daemons/CVS
 /srv/abs/rsync/i686//community/devel/CVS
 /srv/abs/rsync/i686//community/editors/CVS
 /srv/abs/rsync/i686//community/emulators/CVS
 /srv/abs/rsync/i686//community/games/CVS
 /srv/abs/rsync/i686//community/gnome/CVS
 /srv/abs/rsync/i686//community/i18n/CVS
 /srv/abs/rsync/i686//community/kde/CVS
 /srv/abs/rsync/i686//community/lib/CVS
 /srv/abs/rsync/i686//community/modules/CVS
 /srv/abs/rsync/i686//community/multimedia/CVS
 /srv/abs/rsync/i686//community/multimedia/libflashsupport-oss/CVS

fixed



 /srv/abs/rsync/i686//community/network/CVS
 /srv/abs/rsync/i686//community/office/CVS
 /srv/abs/rsync/i686//community/science/CVS
 /srv/abs/rsync/i686//community/system/CVS
 /srv/abs/rsync/i686//community/x11/CVS
 /srv/abs/rsync/i686//community/xfce/CVS

 Missing Dependencies
 --
 flumotion -- 'twisted-web'
 open-vm-tools-modules -- 'kernel262.6.28'
 eclipse-ve -- 'eclipse3.3'
 cdfs -- 'kernel262.6.28'
 virtualbox-ose-additions-modules -- 'kernel262.6.28'

 Missing Makedepends
 -
 splix -- 'jbigkit'

 Summary
 -
 Missing PKGBUILDs:                     19
 Invalid PKGBUILDs:                     0
 Mismatching PKGBUILD names:            0
 Duplicate PKGBUILDs:                   0
 Invalid archs:                         0
 Missing (make)dependencies:            6
 Repo hierarchy problems:               0
 Circular dependencies:                 0



Re: [aur-general] Voting period: Chris Brannon

2009-03-27 Thread Allan McRae

Allan McRae wrote:

Hi TUs,

It is time to vote so head to the AUR voting interface.  You can 
refresh your memory here: 
http://www.archlinux.org/pipermail/aur-general/2009-March/004104.html




Bump!

There is two days voting left and we have not reached quorum.  Go there 
now and vote!


Allan