Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

Flavien Bridault <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.general,gmane.linux.debian.ports.s390,gmane.linux.debian.ports.sparc,gmane.linux.debian.ports.powerpc
Message-ID <[email protected]>
Okay thanks a lot for your quick answer !

Maybe I misunderstood the excuses
https://qa.debian.org/excuses.php?package=camp, but the build failure on
s390x looks very similar at the endianess issue we have on sparc64, so
this should also solves that. If not I will contact s390x folks.


Le 06/04/2018 à 14:28, John Paul Adrian Glaubitz a écrit :
> Hi Flavien!
>
> On 04/06/2018 02:24 PM, Flavien Bridault wrote:
>> I already posted the information but it seems no one got it.
>>
>> My GPG key has been signed by a Debian Developer, would it be
>> possible to
>> gain access to the sparc64 porterbox now ?
> Yes, we can create an account for you on the sparc64 porterbox.
>
>> camp has been removed from testing because of this bug and this
>> prevents fw4spl
>> from being updated, I would like to fix this asap.
>
> A package failing to build from source on sparc64 does not have
> any influence on testing migration. In fact, the package builds
> fine on sparc64 at the moment so I'm not sure a sparc64 porterbox
> would help you.
>
> We can still give you access to the sparc64 porterbox if the problem
> is big-endian-specific, but I guess access to an s390x machine would be
> better. Although for that you would have to contact the s390x folk.
>
> Adrian
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.