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

Bug#733411: marked as done (migrate only packages built on at least two architectures)

Your message dated Thu, 19 Mar 2020 14:05:02 +0100
with message-id <efa92508-a9f1-0609-7a05-f0fd3a824046@debian.org>
and subject line Re: migrate only packages built on at least two architectures
has caused the Debian Bug report #733411,
regarding migrate only packages built on at least two architectures
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.)


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

Hi,

as just discussed on IRC, it would be nice if britney would only
migrate packages to testing which are available on at least two
architectures (so that we know it had been autobuilt at least once).
(For the few exceptions which are only relevant for a single
architecture, there would need to be a hint like "singlearch package",
and also an initial cleanup before activating it sounds a good idea.)

Reasoning behind is that as of now britney doesn't get aware if
brand new packages FTBFS everywhere e.g. because of broken build
dependencies, but would happly migrate such a package to testing
(which then couldn't been built in a clean chroot), because the
package is current on all architectures it was ever built on. Forcing
human work to file RC bugs fast enough doesn't seem reliable,
especially if we could automatically detect it.



Thanks,
Andi

--- End Message ---
--- Begin Message --- 
Hi Andreas,

On Sat, 28 Dec 2013 20:32:31 +0100 Andreas Barth <aba@ayous.org> wrote:
> as just discussed on IRC, it would be nice if britney would only
> migrate packages to testing which are available on at least two
> architectures (so that we know it had been autobuilt at least once).
>> (For the few exceptions which are only relevant for a single
> architecture, there would need to be a hint like "singlearch package",
> and also an initial cleanup before activating it sounds a good idea.)
> 
> Reasoning behind is that as of now britney doesn't get aware if
> brand new packages FTBFS everywhere e.g. because of broken build
> dependencies, but would happly migrate such a package to testing
> (which then couldn't been built in a clean chroot), because the
> package is current on all architectures it was ever built on. Forcing
> human work to file RC bugs fast enough doesn't seem reliable,
> especially if we could automatically detect it.

We now explicitly only allow migration of packages that have been built
on a buildd. So I think this bug can be closed because that is what you
wanted to achieve.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: