Re: Package not migrating although status says 'Will attempt migration'

Hi Sebastiaan, On 2020-04-16 09:46, Sebastiaan Couwenberg wrote: > The excuses for rdkit show that it's blocked by gcc-10: > > https://qa.debian.org/excuses.php?package=rdkit > > And the excuses for gcc-10 show autopkgtest regressions: > > https://qa.debian.org/excuses.php?package=gcc-10

Re: Package not migrating although status says 'Will attempt migration'

On 4/16/20 8:34 AM, mer...@debian.org wrote: > schroedinger-coordgenlibs is not migrated although the delay is over > [1]. Is there something I can do about it? This package prevents > migration of other packages. The britney update_output shows: trying: schroedinger-coordgenlibs skipped:

Package not migrating although status says 'Will attempt migration'

Hello, schroedinger-coordgenlibs is not migrated although the delay is over [1]. Is there something I can do about it? This package prevents migration of other packages. Best, Andrius [1] https://qa.debian.org/excuses.php?package=schroedinger-coordgenlibs

Re: Package not migrating due to missing build on i386, but i386 is excluded

On Fri, 20 Dec 2019, 12:30 Andrey Rahmatullin, wrote: > Thet testing package is built on i386. If you are no longer building it on > that arch, you need to file a bug to remove the i386 binary from testing. > Thanks for explanation! Best, Andrius

Re: Package not migrating due to missing build on i386, but i386 is excluded

On Fri, Dec 20, 2019 at 11:37:48AM +0200, Andrius Merkys wrote: > stringtie [1] is not migrating due to missing build on i386, although this > arch is excluded from the arch list for the package. The delay is over. Is > this transient, or is there a problem? Thet testing package is built on i386.

Package not migrating due to missing build on i386, but i386 is excluded

Hello, stringtie [1] is not migrating due to missing build on i386, although this arch is excluded from the arch list for the package. The delay is over. Is this transient, or is there a problem? Cheers, Andrius [1] https://tracker.debian.org/pkg/stringtie

Re: Package not migrating

Ole Streicher: > Hi Nils, > Hi, > Niels Thykier writes: >> Ole Streicher: >>> Andrey Rahmatullin writes: On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote: >> The package is affected by the same issue that chocolate-doom was in the >>

Re: Package not migrating

Hi Nils, Niels Thykier writes: > Ole Streicher: >> Andrey Rahmatullin writes: >>> On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote: > The package is affected by the same issue that chocolate-doom was in the > referenced bug (#824169). The

Re: Package not migrating

Ole Streicher: > Andrey Rahmatullin writes: >> On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote: >>> * Not touching package due to block request by adsb (check >>> https://release.debian.org/testing/freeze_policy.html if update is >>> needed) >>

Re: Package not migrating

Andrey Rahmatullin writes: > On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote: >> * Not touching package due to block request by adsb (check >> https://release.debian.org/testing/freeze_policy.html if update is >> needed) >

Re: Package not migrating

On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote: > * Not touching package due to block request by adsb (check > https://release.debian.org/testing/freeze_policy.html if update is > needed) https://release.debian.org/britney/hints/adsb: # 20170720 # in both main and contrib,

Re: Package not migrating

Hi, On 17/08/17 19:42, Ole Streicher wrote: > I have a package (cpl) that did not migrate since 38 days, but I don't > see a reason: > > Excuse for cpl > > * Migration status: BLOCKED: Needs an approval (either due to a freeze > or due to the source suite) > * 38 days old (needed 10 days) >

Package not migrating

Hi, I have a package (cpl) that did not migrate since 38 days, but I don't see a reason: Excuse for cpl * Migration status: BLOCKED: Needs an approval (either due to a freeze or due to the source suite) * 38 days old (needed 10 days) * Not touching package due to block request by adsb (check

Re: Package not migrating

Hello, >https://release.debian.org/britney/update_output.txt OTOH says: > >trying: sunpy >skipped: sunpy (0, 0, 255) >got: 36+0: a-3:i-23:a-0:a-0:a-0:m-0:m-7:m-0:p-0:s-3 >* s390x: python-sunpy, python3-sunpy this usually means (if I'm correct) that the new sunpy makes python-sunpy

Re: Package not migrating

Andrey Rahmatullin writes: > On Thu, Jan 12, 2017 at 10:33:58AM +0100, Ole Streicher wrote: >> Hi, >> >> I still do not completely understand all causes why a package does not >> migrate: >> >> sinpy is a valida candidate but doesn't migrate. None of the pages shows >> a

Re: Package not migrating

On Thu, Jan 12, 2017 at 10:33:58AM +0100, Ole Streicher wrote: > Hi, > > I still do not completely understand all causes why a package does not > migrate: > > sinpy is a valida candidate but doesn't migrate. None of the pages shows > a reason: > > https://qa.debian.org/excuses.php?package=sunpy

Package not migrating

Hi, I still do not completely understand all causes why a package does not migrate: sinpy is a valida candidate but doesn't migrate. None of the pages shows a reason: https://qa.debian.org/excuses.php?package=sunpy https://release.debian.org/britney/update_excuses.html#sunpy At the same time,

Re: Package not migrating

On Wed, Nov 30, 2016 at 04:35:34PM +0100, Ole Streicher wrote: > I have a package (casacore-data-tai-utc), that doesn't migrate to > testing, even if it is marked as "valid candidate": > > excuses: > * 12 days old (needed 10 days) > * casacore-data-tai-utc/i386 unsatisfiable Depends:

Package not migrating

Hi, I have a package (casacore-data-tai-utc), that doesn't migrate to testing, even if it is marked as "valid candidate": excuses: * 12 days old (needed 10 days) * casacore-data-tai-utc/i386 unsatisfiable Depends: python3-casacore * Valid candidate The second item comes from the fact, that