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

Bug#746792: marked as done (release.debian.org: hint lazarus: not migrating because an arch all was made arch any)

Your message dated Fri, 16 May 2014 08:18:07 +0200
with message-id <5375AD9F.5080500@debian.org>
and subject line Re: Bug#746792: release.debian.org: hint lazarus: not migrating because an arch all was made arch any
has caused the Debian Bug report #746792,
regarding release.debian.org: hint lazarus: not migrating because an arch all was made arch any
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.)


-- 
746792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746792
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi RT,

It seems to me that lazarus needs some help to migrate to testing.
We moved a package from arch all to arch any and now migration is
blocked because some architectures are not able to build the package.

See: https://release.debian.org/migration/testing.pl?package=lazarus-ide-qt4-1.2

Or did I miss something and should I do something on my side?

Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJTZQrVAAoJEJxcmesFvXUK6iAIAKbuCl+wWF4LYZ69dRjwsamq
G0S4mMoXkE7jTej5Ig2oqSPp4gECZ41ydLmNCsvZ9mgMveiuwp7lDnmJ3zDAxpNW
mnSkd8gzG5GqU5ye93oNN6Gb6Bv/ApYMG8uHAisz/SUDYKtfSTh0tZFkvEKEm1tX
4NVc+Cz+pGgSm6m9INdKHWc1x6v3jDwoEnPpIrh8gv0A3bWIMk+MVyx5qamGfH9e
SUHMiml+jUiTrFURa7/hyiZl19Ef5iwAuK4IjCg9EaBWsfb26yGBfi7vhujZkc7k
AxWWXPhI9IlwKkDS6evAqkCrLw7riZcKs2IacqQ2OLcjqix3JBPsYQI6VklyxvU=
=unKY
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 03-05-14 17:50, Paul Gevers wrote:
> Actually, it should be waiting on fpc to migrate now I think of it, via
> depends on fpc-abi-2.6.4. Is this maybe just not shown?

There was a brief moment that it showed why the migration was blocked,
but the last couple of days it didn't really show that is was blocked by
dependency chain. I am not sure if I can really propose an improvement
in code, but it seems to me the information to the maintainers could be
more explaining.

> And while
> investigating, I notice that amd64 and powerpc have been built, but not
> installed yet.
> 
> So for now, it is probably best to wait a couple of days, let me come
> back to you (unless you already have insights for me).

All migrated now on their own, so nothing to do here anymore. It seems
like the dependency chain is working properly.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: