[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887060: marked as done (testing migration happened despite FTBFS on arch:all buildd)

Your message dated Tue, 19 Mar 2024 20:26:23 +0100
with message-id <a22054e0-8b8f-41d9-a3cb-cb603903c08b@debian.org>
and subject line Re: testing migration happened despite FTBFS on arch:all buildd
has caused the Debian Bug report #887060,
regarding testing migration happened despite FTBFS on arch:all buildd
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
887060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887060
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: britney

Hi,

Package src:octave-interval creates two binaries:
- octave-interval (arch:any)
- octave-interval-doc (arch:all)

Version 3.1.0-3 was uploaded on 2018-01-07 as source-only:

 https://tracker.debian.org/news/899881

Compilation went fine on the arch:any buildds, but failed on the arch:all one:

 https://buildd.debian.org/status/fetch.php?pkg=octave-interval&arch=all&ver=3.1.0-3&stamp=1515343715&raw=0

Still, testing migration occurred on 2018-01-13:

 https://tracker.debian.org/news/901166

As of 2018-01-13, the dak status is the following:

$ ssh coccia dak ls octave-interval octave-interval-doc
octave-interval     | 2.1.0-2       | stable         | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
octave-interval     | 2.1.0-2       | unstable       | source
octave-interval     | 2.1.0-2       | unstable-debug | source
octave-interval     | 2.1.0-2+b1    | unstable       | kfreebsd-amd64, kfreebsd-i386
octave-interval     | 3.1.0-3       | testing        | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
octave-interval     | 3.1.0-3       | unstable       | source, amd64, arm64, armel, armhf, hurd-i386, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
octave-interval     | 3.1.0-3       | unstable-debug | source
octave-interval-doc | 2.1.0-2       | stable         | all
octave-interval-doc | 2.1.0-2       | unstable       | all
octave-interval-doc | 3.1.0-2       | unstable       | all

i.e. octave-interval is present in testing but octave-interval-doc is not.

(I will probably request soon a give-back for octave-interval-doc, so this
state will not persist for long).

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi,
On Sat, 13 Jan 2018 10:07:24 +0100 =?iso-8859-1?Q?S=E9bastien?= Villemot <sebastien@debian.org> wrote: 
Package src:octave-interval creates two binaries:
- octave-interval (arch:any)
- octave-interval-doc (arch:all)

Version 3.1.0-3 was uploaded on 2018-01-07 as source-only:

 https://tracker.debian.org/news/899881

Compilation went fine on the arch:any buildds, but failed on the arch:all one:

 https://buildd.debian.org/status/fetch.php?pkg=octave-interval&arch=all&ver=3.1.0-3&stamp=1515343715&raw=0

Still, testing migration occurred on 2018-01-13:
I have just deployed a change to britney2 that will prevent this from happening in the future: 
https://salsa.debian.org/release-team/britney2/-/merge_requests/95

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: