Christian Perrier <bubulle@debian.org> (2014-09-09):
> Le 09/09/2014 11:19, Debian FTP Masters a écrit :
> >
> >
> >Processing raised an exception: disabled is not a valid architecture name or wildcard.
> >Traceback (most recent call last):
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 914, in check
> > final_suites = self._final_suites()
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 808, in _final_suites
> > if self._check_new(overridesuite):
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 773, in _check_new
> > if self._check_new_binary_overrides(suite):
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 748, in _check_new_binary_overrides
> > packages = source.package_list.packages_for_suite(suite)
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/packagelist.py", line 128, in packages_for_suite
> > built = entry.built_in_suite(suite)
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/packagelist.py", line 58, in built_in_suite
> > built_on_arch = self.built_on_architecture(arch.arch_string)
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/packagelist.py", line 49, in built_on_architecture
> > if match_architecture(architecture, arch):
> > File "/srv/ftp-master.debian.org/dak/dak/daklib/architecture.py", line 94, in match_architecture
> > raise InvalidArchitecture('{0} is not a valid architecture name or wildcard'.format(wildcard))
> >InvalidArchitecture: disabled is not a valid architecture name or wildcard
>
>
> Anyone understanding what's happening?
See the cdebconf-slang-udeb stanza in debian/control.
I suppose some dak changes triggered the reject. I'm not sure the
exception is expected though, so cc-ing ftpmaster@.
Mraw,
KiBi.
Attachment:
signature.asc
Description: Digital signature