Re: Preventing a broken release arch from blocking testing migration
Hi Andrey, On Fri, Jun 17, 2022 at 05:51:36PM +0500, Andrey Rahmatullin wrote: > On Fri, Jun 17, 2022 at 02:01:42PM +0200, Daniel Gröber wrote: > > my package yosys has a test failure on mips64el that I can't figure out and > > consequently got removed from testing. I'm wondering how to deal with this? > > > > From reading the policy it seems I can use the Architecture field to list > > all arches except mips64el. Is that the right thing to do here? > Well, ideally you should fix the test or the software. If that's > impossible then yeah. Ideally yes, but I just don't see anyone wanting to build/test FPGA bitstreams on a wee little embedded mips router thingies ;) so it's just not worth spending time on IMO. > > I also wonder if there is a way to specify "everything except mips64el" > > instead of listing all arches explicitly? > Unfortunately no. Alright as long as I'm not missing something obvious :) Thanks, --Daniel signature.asc Description: PGP signature
Re: Preventing a broken release arch from blocking testing migration
On Fri, Jun 17, 2022 at 02:01:42PM +0200, Daniel Gröber wrote: > my package yosys has a test failure on mips64el that I can't figure out and > consequently got removed from testing. I'm wondering how to deal with this? > > From reading the policy it seems I can use the Architecture field to list > all arches except mips64el. Is that the right thing to do here? Well, ideally you should fix the test or the software. If that's impossible then yeah. > I also wonder if there is a way to specify "everything except mips64el" > instead of listing all arches explicitly? Unfortunately no. -- WBR, wRAR signature.asc Description: PGP signature
Re: Preventing a broken release arch from blocking testing migration
Le ven. 17 juin 2022 à 14:31, Daniel Gröber a écrit : > Hi Mentors, > > my package yosys has a test failure on mips64el that I can't figure out and > consequently got removed from testing. I'm wondering how to deal with this? > > From reading the policy it seems I can use the Architecture field to list > all arches except mips64el. Is that the right thing to do here? > > I also wonder if there is a way to specify "everything except mips64el" > instead of listing all arches explicitly? > https://wiki.debian.org/ftpmaster_Removals#Removals_from_testing.2C_stable_and_oldstable Jérémy
Preventing a broken release arch from blocking testing migration
Hi Mentors, my package yosys has a test failure on mips64el that I can't figure out and consequently got removed from testing. I'm wondering how to deal with this? From reading the policy it seems I can use the Architecture field to list all arches except mips64el. Is that the right thing to do here? I also wonder if there is a way to specify "everything except mips64el" instead of listing all arches explicitly? Thanks, --Daniel signature.asc Description: PGP signature
Testing Migration
Dear All I found that my package (http://packages.qa.debian.org/a/acsccid.html) cannot migrate to testing. The build log (kfreebsd-amd64) is Ok but it didn't set the status to Installed. Do you know why? Regards Godfrey -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/B26B0B185A294D448CB08AF85CF7BDB8@PC104
Re: Testing Migration
On 2014-05-23 18:16:46, Godfrey Chung wrote: Dear All I found that my package (http://packages.qa.debian.org/a/acsccid.html) cannot migrate to testing. The build log (kfreebsd-amd64) is Ok but it didn't set the status to Installed. Do you know why? Looking at https://buildd.debian.org/status/package.php?p=acsccid the kfreebsd-amd64 is Uploaded for 27 days. This might indicated that there went something wrong with the upload from the buildd to the archive. I'd contact the buildd admins to find out what's wrong. You can reach them at kfreebsd-am...@buildd.debian.org. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Re: Testing Migration
Godfrey Chung godfrey.ch...@acs.com.hk writes:
I found that my package (http://packages.qa.debian.org/a/acsccid.html)
cannot migrate to testing. The build log (kfreebsd-amd64) is Ok but it
didn't set the status to Installed.
Do you know why?
You'll in general ask the buildd maintainers for that by sending a mail
to ${arch}@buildd.debian.org -- in that case
kfreebsd-am...@buildd.debian.org.
Now I would be the one receiving that mail and I have already reuploaded
the package from the buildd. Let's see
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87zji8lj3r@anonymous.siccegge.de
