On Thu, Mar 29, 2018 at 07:04:06PM +0200, Andreas Tille wrote:
> Could you please add something.
>
> To enable the migration even if either amd64 or i386 architecture
> is missing for one of the dependencies please
>
> [ ] file a bug against release.debian.org
> [ ] send an e-mail t
Hi Niels,
On Thu, Mar 29, 2018 at 04:27:00PM +, Niels Thykier wrote:
> >
> > That would be a Britney bug, therefore file it against relase.debian.org
> > and usertag it with 'britney'.
> >
> > In that case, I'd rather keep listing all the broken architectures, but
> > explicitly mark those a
Mattia Rizzolo:
> On Thu, Mar 29, 2018 at 03:37:10PM +0100, Ian Jackson wrote:
>> But, Andreas linked to the excuses page (his [1], above) which mention
>> a lot of other architectures, where installability of the dependencies
>> is not relevant. Eg
>> paleomix/s390x unsatisfiable Depends: pytho
or testing
> migration ? I guess maybe not.
No. Bwa and bowtie2 were explicitly designed for amd64 (not even 64 bit
in general since it contains assembly code). These packages are
Architecture: amd64 kfreebsd-amd64
So getting bcftools tests fixed would be nice but has no influence on
pa
On Thu, Mar 29, 2018 at 03:37:10PM +0100, Ian Jackson wrote:
> But, Andreas linked to the excuses page (his [1], above) which mention
> a lot of other architectures, where installability of the dependencies
> is not relevant. Eg
> paleomix/s390x unsatisfiable Depends: python-pysam
>
> I can see
Andreas Tille writes ("How to enable testing migration for packages
Architecture: all but depending from Architecture: any packages"):
> [1] https://qa.debian.org/excuses.php?package=paleomix
Mattia Rizzolo writes ("Re: How to enable testing migration for packages
Arc
Hi Mattia,
On Thu, Mar 29, 2018 at 10:53:26AM +0200, Mattia Rizzolo wrote:
> On Thu, Mar 29, 2018 at 10:19:25AM +0200, Andreas Tille wrote:
> > its not the first time that I'm running into that problem: A package
> > that is Architecture: all depends from packages Architecture: any.
> > These dep
Hi,
[...]
>> While simply setting the Architecture: all package to any that
>> intervention would not be necessary but that's simply wrong.
>> Unfortunately I currently see no better solution and wanted to bring
>> this topic up here.
>>
> Make sure your arch:any package builds on at least amd64 a
On Thu, Mar 29, 2018 at 10:19:25AM +0200, Andreas Tille wrote:
> its not the first time that I'm running into that problem: A package
> that is Architecture: all depends from packages Architecture: any.
> These dependencies are not available on all architectures and thus the
> package does not mig
On 03/29/2018 10:19 AM, Andreas Tille wrote:
> Hi,
>
> its not the first time that I'm running into that problem: A package
> that is Architecture: all depends from packages Architecture: any.
> These dependencies are not available on all architectures and thus the
> package does not migrate to t
Hi,
its not the first time that I'm running into that problem: A package
that is Architecture: all depends from packages Architecture: any.
These dependencies are not available on all architectures and thus the
package does not migrate to testing. The package paleomix is an example
for this[1].
11 matches
Mail list logo
