The ietf/patches directory doesn't work out as intended, and causes some confusion with the /a/www/ietf-datatracker/patches/ directory on the production server.

- Legacy-Id: 7546
This commit is contained in:
Henrik Levkowetz 2014-03-26 14:27:36 +00:00
parent 5ff7ddcc5a
commit 521b42436d
2 changed files with 0 additions and 38 deletions

View file

@ -1,10 +0,0 @@
#!/usr/bin/env python
print """
This file was a run-once script to back-fill reference information for
documents which were already in the database. Once it had been run,
there's no particular further use for it, so in order to avoid handling
40 extra Megabytes in for instance grep and lint (pyflakes) operations,
the content has been removed. It is still available in earlier repository
revisions, though.
"""

View file

@ -1,28 +0,0 @@
#!/usr/bin/env python
from ietf import settings
from django.core import management
management.setup_environ(settings)
from ietf.doc.models import RelatedDocument,State,DocEvent
from ietf.person.models import Person
relevant_relations = RelatedDocument.objects.filter(relationship__slug='replaces',
target__document__type__slug='draft',
target__document__states__type='draft',
target__document__states__slug__in=['active','expired'])
affected_docs = set([x.target.document for x in relevant_relations])
replaced_state = State.objects.get(type='draft',slug='repl')
system_user = Person.objects.get(name="(System)")
for d in affected_docs:
d.set_state(replaced_state)
DocEvent.objects.create(type="added_comment",
doc=d,
by=system_user,
desc='Draft state administratively corrected to Replaced',
)