Initial import for public release...

Special Note
  Prior to git import, approx 90% of the code was done by Judd Vinet. Thanks Judd!

Author: eliott

.gitignore

@@ -0,0 +1,4 @@
+*.pyc
+*.swp
+local_settings.py
+

AUTHORS

@@ -0,0 +1,6 @@
+# AUTHORS
+Judd Vinet <[email protected]>
+Simo Leone <[email protected]>
+eliott <[email protected]>
+
+

LICENSE

@@ -0,0 +1,14 @@
+# License
+ See LICENSE file.
+
+# Authors
+ See AUTHORS file.
+
+# Installation
+
+## Dependencies
+ - python
+ - mysql-python
+ - Django >= 0.95
+
+

README

@@ -0,0 +1,50 @@
+from django.db import models
+from django.contrib.auth.models import User
+
+class Mirror(models.Model):
+    id = models.AutoField(primary_key=True)
+    domain = models.CharField(maxlength=255)
+    country = models.CharField(maxlength=255)
+    url = models.CharField(maxlength=255)
+    protocol_list = models.CharField(maxlength=255, null=True, blank=True)
+    admin_email = models.CharField(maxlength=255, null=True, blank=True)
+    def __str__(self):
+        return self.domain
+    class Admin:
+        list_display = ('domain', 'country')
+        list_filter = ('country',)
+        ordering = ['domain']
+        search_fields = ('domain')
+        pass
+
+class Donator(models.Model):
+    id = models.AutoField(primary_key=True)
+    name = models.CharField(maxlength=255)
+    def __str__(self):
+        return self.name
+    class Admin:
+        ordering = ['name']
+        search_fields = ('name')
+        pass
+
+class UserProfile(models.Model):
+    id = models.AutoField(primary_key=True) # not technically needed
+    notify = models.BooleanField("Send notifications", default=True, help_text="When enabled, user will recieve 'flag out of date' notifications")
+    alias = models.CharField(core=True, maxlength=50, help_text="Required field")
+    public_email = models.CharField(core=True, maxlength=50, help_text="Required field")
+    other_contact = models.CharField(maxlength=100, null=True, blank=True)
+    website = models.URLField(null=True, blank=True)
+    yob = models.IntegerField(null=True, blank=True)
+    location = models.CharField(maxlength=50, null=True, blank=True)
+    languages = models.CharField(maxlength=50, null=True, blank=True)
+    interests = models.CharField(maxlength=255, null=True, blank=True)
+    occupation = models.CharField(maxlength=50, null=True, blank=True)
+    roles = models.CharField(maxlength=255, null=True, blank=True)
+    favorite_distros = models.CharField(maxlength=255, null=True, blank=True)
+    picture = models.FileField(upload_to='devs', default='devs/silhouette.png')
+    user = models.ForeignKey(User, edit_inline=models.STACKED, num_in_admin=1, min_num_in_admin=1, max_num_in_admin=1, num_extra_on_change=0, unique=True)
+    class Meta:
+        db_table = 'user_profiles'
+        verbose_name = 'Additional Profile Data'
+        verbose_name_plural = 'Additional Profile Data'
+

__init__.py

@@ -0,0 +1,12 @@
+from django import template
+
+register = template.Library()
+
+@register.inclusion_tag('errors.html')
+def print_errors(errors):
+	errs = []
+	for e,msg in errors.iteritems():
+		errmsg = str(msg[0])
+		# hack -- I'm a python idiot
+		errs.append( (e, errmsg[2:-2]) )
+	return {'errors': errs}

common/__init__.py

@@ -0,0 +1,164 @@
+=============================================================================
+            THE QUICK AND DIRTY ON HOW TO BE A PACKAGE MAINTAINER
+=============================================================================
+                                             questions to [email protected]
+
+1. Follow Package Guidelines
+
+   Package guidelines can be found in the Arch Linux documentation.
+   Please follow them closely.
+
+2. How To Use CVS
+
+   The example commands below assume the module 'extra'.
+
+   2.1  Make sure your CVSROOT environment variable is set properly.  If the
+        CVS repository is on the same box:
+          # export CVSROOT=/home/cvs-extra
+
+        If you want to access the repository from the different box via SSH:
+          # export CVS_RSH=ssh
+          # export CVSROOT=:ext:[email protected]:/home/cvs-extra
+
+   2.2  Checkout the repository.  This will download the entire repository to
+        your local machine:
+          # cvs co extra
+
+   2.3  Updating the repository.  This syncs your local repository with the
+        master.  You should do this often, especially if other people could be
+        working on the same repository.
+          # cd extra
+          # cvs -q update -d
+
+   2.4  Adding files/directories to the repository.  When you want to add a new
+        package you should create a directory under the respective category and
+        place the new PKGBUILD in it.  For example, to add fvwm to the repo:
+          # cd extra/x11
+          # mkdir fvwm
+          # cd fvwm
+          # cp /var/abs/PKGBUILD.proto ./PKGBUILD
+          <edit, test, build, etc>
+          # cd ..
+          # cvs add fvwm
+          # cvs add fvwm/PKGBUILD
+
+   2.5  Committing changes. Files are not written to the master repository until
+        you commit.  Never forget to commit!
+          # cd extra
+          # cvs commit
+ 
+        This will find all modified files, then throw you into vi where you can
+        add a log message describing your changes.  Save and exit from vi when
+        you're done and cvs will update the files in the master repository.
+
+   2.6  Removing files.  If you need to remove a file (eg, an old patch that
+        isn't needed anymore), you can do the following:
+          # cd extra/x11/fvwm
+          # rm old.patch
+          # cvs remove old.patch
+          # cvs commit -m "removed old.patch" old.patch
+        also remove the CURRENT/STABLE tags from the file so it does not appear
+        in ABS any more:
+          # cvs tag -d CURRENT old.patch
+ 
+        Don't forget to commit afterwards!  Remember that no changes are made
+        to the master until you commit.
+
+   2.7  Removing directories cannot be done easily.  If you really need to
+        remove a directory, email the sysadmin (Judd) and I'll help you out.
+
+   2.8  Tagging files.  Every file in CVS has tags associated with it, which
+        allows us to select certain versions of scripts.  The db generation
+        scripts will only look at files that are tagged as CURRENT, so you need
+        to tag all files after you commit them:
+          # cd extra/x11/fvwm
+          # cvs tag -c -F -R CURRENT
+
+        NOTE: When tagging, you should be sure to ONLY tag the updated files,
+        not the entire repository.  Otherwise, if parts of your checkout are
+        out-of-date, you may actually be tagging an OLDER version of a file,
+        reversing someone else's tag procedure.
+
+3. The Process
+
+   3.1  Checkout/update your local repository from cvs.archlinux.org
+   3.2  Make any changes you need to
+   3.3  Put your new packages in your local staging directory on archlinux.org.
+        Suggested syntax is: 
+          scp name-ver-rel.pkg.tar.gz [email protected]:staging/extra/add
+   3.4  Commit your changes (section 2.5)
+   3.5  Update the CURRENT tags to new revisions (section 2.8)
+   3.6  Log in to archlinux.org and run the /arch/db-extra script, which
+        will re-generate the sync db and place it in /home/ftp/extra, then
+        move the new/updated packages from your staging directory to the
+        FTP tree.
+   3.7  Remove any older versions of packages from /home/ftp/extra to
+        save diskspace, they should be noted when the db generation script
+        finishes.
+
+   Make sure you do things in this order, mixing them up can break things
+   temporarily.  For example, if you remove older versions from the ftp
+   tree before you update the database or update the database before 
+   uploading new packages, arch users trying to download the package at 
+   that time will get "file not found" errors.
+
+4. Staging Directories
+
+   As mentioned in Section 3, packages need to be uploaded to the proper
+   staging directory before running a db generation script.  The staging
+   area (located in your home dir) looks like so:
+
+    staging
+    |-- arch
+    |   |-- add
+    |   `-- del
+    |-- extra
+    |   |-- add
+    |   `-- del
+    |-- testing
+    |   |-- add
+    |   `-- del
+    `-- unstable
+        |-- add
+        `-- del
+
+   As you can see, each repository has two staging directories: "add" and
+   "del".  When you want to add or update a package, you'll place it in the
+   "add" directory for the repository you're working in.  Then run the db-gen
+   script.
+   
+   When you want to remove a package, you will move the package OUT OF the FTP
+   directory (eg, /home/ftp/extra/os/i686/) and INTO the "del" directory for
+   the repository you're working in.  Once moved, you can run the db-gen
+   script -- it will see that the file has left the FTP tree and will remove
+   it from the package database.
+
+5. Miscellaneous Stuff
+
+   5.1  If you are creating a daemon you need to include an rc.d startup
+        script for it.  Look at /var/abs/daemons/esd for a simple example.
+   5.2  Please include a line that says '# $Id: pkgmaint_guide.txt,v 1.3 2006/10/05 20:52:01 judd Exp $' at the top of each
+        PKGBUILD.  This will be parsed by cvs during a commit, and replaced
+        with user/timestamp data.
+   5.3  Please do some rudimentary checks of the package before making it
+        'live'.  Try installing it and see if there are any file conflicts.
+        Check for dependencies by running 'ldd' against the binaries and
+        looking through the .so files it requires.  For example,
+        'ldd /usr/bin/gvim' returns a big list of libs, one of which is
+        libgtk-x11-2.0.so.0, so gtk2 should be one of the dependencies for
+        gvim.  Also, namcap is available in the extra repository.  Running it 
+        against a package will print dependancy warnings as well as possible
+        configuration problems.  Namcap is not the final word, if ldd or
+        runtime show otherwise, believe them instead.
+   5.4  When creating a package description for a package, do not include
+        the package name in a self-referencing way, as it is redundant.
+        For example, "Nedit is a text editor for X11" could be simplified to
+        "A text editor for X11".  Also try to keep the descriptions to ~80
+        characters or less.
+   5.5  When entering cvs log messages for new/upgraded packages, please use
+        these tags so they can be easily parsed for changelog generation:
+          if the package is upgrade use: 'upgpkg: pkgname newpkgver'
+          if the package is new use:     'newpkg: pkgname newpkgver'
+
+
+$Id: pkgmaint_guide.txt,v 1.3 2006/10/05 20:52:01 judd Exp $

common/models.py

@@ -0,0 +1,67 @@
+from django.http import HttpResponse, HttpResponseRedirect
+from django.contrib.auth.decorators import login_required
+from django.contrib.auth.models import User
+from django.core import validators
+from archlinux.utils import render_template
+from archlinux.packages.models import Package
+from archlinux.todolists.models import Todolist, TodolistPkg
+from archlinux.settings import DATA_DIR
+from archlinux.utils import validate
+from archlinux.common.models import UserProfile
+
+@login_required
+def index(request):
+	try:
+		thismaint = User.objects.get(username=request.user.username)
+	except User.DoesNotExist:
+		# weird, we don't have a maintainer record for this logged-in user
+		thismaint = None
+
+	# get a list of incomplete package todo lists
+	todos = Todolist.objects.get_incomplete()
+	# get flagged-package stats for all maintainers
+	stats = Package.objects.get_flag_stats()
+	if thismaint:
+		# get list of flagged packages for this maintainer
+		pkgs = Package.objects.filter(maintainer=thismaint.id).filter(needupdate=True).order_by('repo', 'pkgname')
+	else:
+		pkgs = None
+
+	return render_template('devel/index.html', request,
+		{'stats':stats, 'pkgs':pkgs, 'todos':todos, 'maint':thismaint})
+
+@login_required
+#@is_maintainer
+def change_notify(request):
+	maint = User.objects.get(username=request.user.username)
+	notify = request.POST.get('notify', 'no')
+	try:
+		maint.get_profile().notify = notify == 'yes'
+	except UserProfile.DoesNotExist:
+		UserProfile(user_id=maint.id ,notify=notify == 'yes').save()
+	maint.get_profile().save()
+	return HttpResponseRedirect('/devel/')
+
+@login_required
+def change_profile(request):
+	errors = {}
+	if request.POST:
+		passwd1, passwd2 = request.POST['passwd'], request.POST['passwd2']
+		email = request.POST['email']
+		# validate
+		if passwd1 != passwd2:
+			errors['password'] = ['  Passwords do not match.  ']
+		validate(errors, 'Email', email, validators.isValidEmail, False, request)
+		# apply changes
+		if not errors:
+			request.user.email = email
+			if passwd1:
+				request.user.set_password(passwd1)
+			request.user.save()
+			return HttpResponseRedirect('/devel/')
+	return render_template('devel/profile.html', request, {'errors':errors,'email':request.user.email})
+
+@login_required
+def guide(request):
+	return HttpResponse(file(DATA_DIR + '/pkgmaint_guide.txt').read(),
+			mimetype='text/plain')

common/templatetags/__init__.py

@@ -0,0 +1,29 @@
+from django.contrib.syndication.feeds import Feed
+from archlinux.packages.models import Package
+from archlinux.news.models import News
+#from datetime import datetime
+
+class PackageFeed(Feed):
+	title       = 'Recent Package Updates'
+	link       = '/packages/'
+	description = 'Recent Package Updates'
+
+	def items(self):
+		return Package.objects.order_by('-last_update')[:10]
+
+	def item_pubdate(self, item):
+		return item.last_update
+
+	def item_categories(self, item):
+		return (item.repo.name,item.category.category)
+
+class NewsFeed(Feed):
+	title       = 'Recent News Updates'
+	link       = '/news/'
+	description = 'Recent News Updates'
+
+	def items(self):
+		return News.objects.order_by('-postdate', '-id')[:10]
+
+	def item_pubdate(self, item):
+		return item.postdate