On Fri 2017-10-06 10:00:27 +0100, Chris Lamb wrote:
> If it were hardcoded into the filenames, one wouldn't need to do
> anything onerous, eg.
>
> -rw-r--r-- 1 0 Oct 6 09:56
> helloworld.adc83b19e793491b1c6ea0fd8b46cd9f32e592fc.class
> -rw-r--r-- 1 0 Oct 6 09:56
>
Source: koji
Version: 1.10.0-1
Severity: wishlist
Ohai,
https://pagure.io/koji/releases lists 1.14.0 as latest koji release,
please update the packaging :)
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'),
Source: koji
Severity: wishlist
please update d/control, d/copyright and d/watch accordignly :)
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign
Hi dkg,
> And there are more questions too: what if multiple source files
> contributed to the creation of the compiled artifact (e.g. "include"
> directives)?
Hm, that's an excellent point.
> You can also imagine a compilation regime that detects changes to a file
> (e.g. via inotify) and
Hi,
> test_progress regression with WoLpH/python-progressbar 3.34.3
< anthraxx > lamby: h01ger: can anyone give me the output of
print(err) in def test_progress() in tests/test_progress.py
would help me creating a patch that works with both versions
Sure. Starting with
