Hi,
I was recently looking at the tracker page for e2fsprogs, and I
noticed that there was the VFS watch error: "Failed to analyze the VCS
repository. Please troubleshoot and fix the issue."
Looking at this this page [1] the complaint seems to be: "Repository
size 537583616 exceeds 500 MiB, block
On Wed, Apr 02, 2014 at 09:54:08AM -0400, Phillip Susi wrote:
> I had prepared an updated package that just discarded the existing git
> tree and imported the current debian/ directory onto the new upstream
> after giving up trying to sort out what of the 1000+ commits in the
> debian fork are stil
On Thu, Jan 02, 2014 at 05:13:02PM +, Adam D. Barratt wrote:
> Urgencies are "sticky", meaning that for any given migration the
> effective urgency used is the highest of all uploads with version
> numbers higher than the package in testing - i.e. if 1.0-1 is
> uploaded at "high", and -2 at "me
Thanks for the explanation. (BTW, it was a typo in my original
message; I had meant to say that the version in _sid_ was 0.9.1-3.)
On Thu, Jan 02, 2014 at 04:58:12PM +, Adam D. Barratt wrote:
> Urgencies for new packages are ignored iff they are "higher" than
> the default urgency configured
Hi,
For the debian.qa.debian.org page[1], it states:
excuses:
Too young, only 0 of 5 days old
Ignoring high urgency setting for NEW package
Not considered
[1] http://packages.qa.debian.org/x/xzgv.html
What's confusing me is there is no "high" urgency setting in the Debian
changelog for
http://piuparts.debian.org/sid/fail/comerr-dev_2.1-1.42~WIP-2011-07-02-1.log
This looks like a missing sid.tar.gz file, which is not a problem with
the package, but some kind of configuration problem? Will piuparts
automatically retry the test at some point?
6 matches
Mail list logo
