Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

Also start moving some p-u checks into daklib
Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

This is a first pass and likely to break
Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

security wants us to check their origs also in their upload/embargo queies. so lets do that
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

modified process-new and all related stuff so NEW can now also be processed
during (most of) dinstall. The lock where NEW is forbidden is then down to
some 15 til 20 minutes, instead of 2 hours.

For that process-new moves files into a "staging" directory, from which
cron.unchecked will move them into the accepted queue. As c.u only runs when
it is safe to do so this is fine.

The small part where we still are forbidden to do NEW is between the point where
we run process-accepted and right before we start generating Packages files. As
that is exactly the area daily.lock exists for, process-new now locks on that and
simply refuses to do work then.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

notes now have a timestamp column.
do not allow to edit old notes, only add new ones
hand over existing notes (if any) to the reject message (unless we get called with -m)
hand over existing notes (if any) to the prod message
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

remove the legacy support
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

more docstrings, even if some are empty/not written yet. Any help would be nice :)
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

doc strings, dont we love em?
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

This is so that we have an idea of where we need what.

Lots of these should be changed to be opaque functions,
not exposing that they're internally regexes at all.
Signed-off-by: NMark Hymers <mhy@debian.org>

Rather than scatter regexes all over the place (for things
which should probably be functions hiding the implementation
detail anyways such as "is this a valid package version"),
move them into daklib.regexes.

I'm not convinced this is an immediate win, but I think it's
one step on a long road...

Oh, and it's untested
Signed-off-by: NMark Hymers <mhy@debian.org>

"0644" != 0644. damn you, string and int.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

who would have thought, os.fdopen really wants an fd, not a filename.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

remove a few trailing ;
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

shut up more of pychecker.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

use the new "style" for the temp_filename function, and if applicable
also use os.fdopen.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

2008-12-09  Philipp Kern  <pkern@debian.org>

        * daklib/queue.py (cross_suite_version_check): add an additional
        parameter to specify if an upload is sourceful or not; do not reject
        uploads that do not satisfy the "must be newer than" criteria and
        are binary-only
        * daklib/queue.py (check_source_against_db, check_binary_against_db):
        invoke cross_suite_version_check as above

OLD bug.
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

2008-10-21  Philipp Kern  <pkern@debian.org>

        * daklib/queue.py: reintroduce James' check for EPERM after
          the chmod'ing of dak files and ignore it; just fubar if the file is
          world writable, which should really never happen
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

2008-09-13  Philipp Kern  <pkern@debian.org>

        * dak/queue.py (dump_vars): make .dak u,g=rw,o=r; James'
        assumption (as stated in 2002-05-18's ChangeLog entry)
        was that people will use the information therein albeit
        it is "just" a duplication of information present in
        other control files; people should still not use it
        as source of information but access to those files makes
        dak debugging easier and there is no leak of sensitive
        information involved
Signed-off-by: NPhilipp Kern <pkern@debian.org>

This reverts commit 536cb00b.

Signed-off-by: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

This really does not have to be quite this unreadable Signed-off-by: Stephen Gran <steve@lobefin.net>