- 18 5月, 2016 5 次提交
-
-
由 Julien Cristau 提交于
Instead of doing two queries per filename and per hash function, store a set of known hashfiles up front and group the UPDATEs in a single query. Suggested by Colin Watson. Signed-off-by: NJulien Cristau <jcristau@debian.org>
-
由 Julien Cristau 提交于
When setting suite.byhash to false, the suite's existing hashfiles need to be marked as unreferenced so they can be cleaned up. Signed-off-by: NJulien Cristau <jcristau@debian.org>
-
由 Julien Cristau 提交于
This way we only touch the filesystem after the db is updated. Signed-off-by: NJulien Cristau <jcristau@debian.org>
-
由 Julien Cristau 提交于
Group knowledge of hash function and corresponding name in our db and in Release files in a class instead of playing clever but unreadable tricks. Suggested by Colin Watson. Signed-off-by: NJulien Cristau <jcristau@debian.org>
-
由 Ansgar Burchardt 提交于
This makes sure the Release files are synced last, after all Packages indices (and their correspondig by-hash files).
-
- 17 5月, 2016 6 次提交
-
-
由 Ansgar Burchardt 提交于
These seem to no longer be used as of c91ff0bd
-
由 Ansgar Burchardt 提交于
This is controlled via the database, however fcfcdcc1 left the setting in config/debian/dak.conf.
-
由 Ansgar Burchardt 提交于
It doesn't seem to be used anywhere.
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
-
- 16 5月, 2016 1 次提交
-
-
由 Julien Cristau 提交于
Add a per-suite boolean to enable by-hash; store the by-hash files in the db, and record when they stopped being referenced, so that clean-suites can delete them after the archive's stayofexecution time. In generate-release, where we have checksums for all the things, hardlink files to the by-hash dir for each of the suite's configured hash methods. Signed-off-by: NJulien Cristau <jcristau@debian.org> --- changes in v2: - use archive.stayofexecution as delay before removing files from by-hash - don't assume any particular ordering for suite.checksums changes in v3: - rebase on latest master, update115 is now update116 - handle missing files in clean_byhash changes in v4: - use hardlinks instead of symlinks - don't initialize `unreferenced` to its default value - in clean_byhash, remove useless fetchall, and handle ENOENT from unlink instead of checking for existence beforehand
-
- 10 5月, 2016 1 次提交
-
-
由 Luke Faraone 提交于
Needed to run the test suite: ====================================================================== ERROR: test_importing_rm (test_imports.ImportTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/srv/daksrc/tests/test_imports.py", line 15, in test_fn __import__('dak', fromlist=[cmd]) File "/srv/daksrc/dak/rm.py", line 54, in <module> from daklib.rm import remove File "/srv/daksrc/dak/daklib/rm.py", line 52, in <module> import debianbts as bts ImportError: No module named debianbts Signed-off-by: NLuke Faraone <lfaraone@debian.org>
-
- 04 5月, 2016 1 次提交
-
-
由 Ansgar Burchardt 提交于
Before Debian LTS started to use the security archive, all uploads that would trigger buildds would be sourceful uploads to a policy queue. So new packages entering the build queues and pushing the public mirrors would likely not happen in the same cron.unchecked run. With Debian LTS, uploads would go to both the build queues and trigger a public mirror push. If the mirror push takes more than three minutes, cron.buildd would however not notify w-b of changes. This patch moves the w-b notification right behind the update of the build queues and before the mirror push to avoid the problem. Ideally we would not rely on anything happening within the last three minutes though.
-
- 02 5月, 2016 1 次提交
-
-
由 Julien Cristau 提交于
Let the python interpreter handle it and actually exit with the right status, otherwise when a sub-command calls sys.exit(1) we end up exiting 0 instead, which is confusing if not dangerous. Signed-off-by: NJulien Cristau <jcristau@debian.org>
-
- 01 5月, 2016 3 次提交
-
-
由 Ansgar Burchardt 提交于
With "wheezy" being used for Debian LTS, the archive needs to be published not only when policy queue uploads are accepted, but also when direct uploads to "wheezy" arrive. The same applies to uploads to "jessie-kfreebsd".
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
Newer SQLAlchemy versions seem to track the `binary` attribute of `BinaryMetadata`. This means the association proxy in `DBBinary` would first create a `BinaryMetadata` with `binary` set to `None`, flush this to the database and then set the actual value of `binary` we want. However the flush fails, as `NULL` is not allowed for the `binary_id` column. The problem can be avoided by not setting `binary` to `None`. This is treated as an "undefined value" by SQLAlchemy and changing it later means the database row never sees `NULL`. The same applies to the `source` attribute of `SourceMetadata`.
-
- 25 4月, 2016 1 次提交
-
-
由 Guillem Jover 提交于
The orig tarball regexes match also the orig tarball detached signatures because they are not anchored at the end, and the loop short-circuits on first match. So we have to move them before their more general counterparts. Fixes commit 84f230b6.
-
- 15 4月, 2016 2 次提交
-
-
由 Ansgar Burchardt 提交于
Calling `f.read()` would read the entire file at once which is wasteful. It's also not intended given the read loop. Also replace a use of `readline()` with `read(65536)` as well where we want to read the entire file and not only single lines.
-
由 Ansgar Burchardt 提交于
-
- 12 4月, 2016 4 次提交
-
-
由 Guillem Jover 提交于
We should only allow upstream tarballs with detached signatures, but not native tarballs, «<source>_<version>.orig.asc» or «<source>_<version>.asc» filenames. We also need to allow this on all relevant regexes. This commit fixes and refactors the regexes to implement the above, and to make it easier to modify a single place in the future. Fixes commit 4911282c. Closes: #759401
-
由 Guillem Jover 提交于
When there's an unknown file in a source package, the function spits this: ,--- Processing raised an exception: global name 'reject' is not defined. Traceback (most recent call last): File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 966, in check chk().check(self) File "/srv/ftp-master.debian.org/dak/dak/daklib/checks.py", line 497, in check rejects = utils.check_dsc_files(dsc_fn, control, source.files.keys()) File "/srv/ftp-master.debian.org/dak/dak/daklib/utils.py", line 343, in check_dsc_files reject("%s: unexpected source file '%s'" % (dsc_filename, f)) NameError: global name 'reject' is not defined `--- Just set the reject message and break from the loop.
-
由 Guillem Jover 提交于
-
由 Guillem Jover 提交于
-
- 02 4月, 2016 7 次提交
-
-
由 Joerg Jaspert 提交于
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
-
由 Joerg Jaspert 提交于
-
由 Joerg Jaspert 提交于
-
由 Joerg Jaspert 提交于
-
由 Ansgar Burchardt 提交于
-
- 01 4月, 2016 3 次提交
-
-
由 Ansgar Burchardt 提交于
We used the remaining parameters before which is somewhat confusing.
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
-
- 31 3月, 2016 4 次提交
-
-
由 Ansgar Burchardt 提交于
This reverts commit 196b3433.
-
由 Ansgar Burchardt 提交于
This should prevent changes to the {src,bin}_contents tables and result in all helper processes seeing the same data.
-
由 Ansgar Burchardt 提交于
-
由 Ansgar Burchardt 提交于
This makes it less error-prone to switch compression methods: the files that are no longer generated are automatically removed. Before they had to be removed manually.
-
- 16 3月, 2016 1 次提交
-
-
由 Joerg Jaspert 提交于
which is helpful when there are no .gz/.bz2 ones around to look at.
-