Bug#817008: unfulfilled dependencies

[Mattia Rizzolo]

On Fri, Mar 11, 2016 at 07:13:46PM +0800, 殷啟聰 wrote:
> I don't really know too much about the transition process, do you mean
> it will block the transition of src:android-sdk-meta itself?

yes: a RC (such a severity:serious) bug which affects the version in
unstable but not the one in testing will block the migration.  That
said, also the tags play a role in this; if I'm right wrt the tagging
this evening (~22:30 UTC) the bug status should be checked again and
this https://release.debian.org/britney/update_excuses.html will be
refreshed, after some time (don't know after how much) also the view in
https://tracker.debian.org/pkg/android-sdk-meta will be refreshed and
it'll stop saying there is that new bug.

The point, without android-sdk-meta nothing will migrate, we don't want
this (probably fixed) bug to block the migration.

> And of course I will wait and see what will happen to my packages.
> From 
> 
> we can see "Invalidated by dependency", so I don't really know if they
> will get into testing :(

That "Invalidated by dependency" just tells you that it won't try to
migrate the package, since some its dependency aren't ready to migrate
themselves.  It will stay there until android-platform-system-extras
will be able to migrate, which in turns need -core...

They will get into testing, I can see how such a entanglement may be
hard to grasp and follow :)  Just hold on!


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#817008: unfulfilled dependencies

[殷啟聰]

I don't really know too much about the transition process, do you mean
it will block the transition of src:android-sdk-meta itself?

And of course I will wait and see what will happen to my packages.
>From 
>
we can see "Invalidated by dependency", so I don't really know if they
will get into testing :(

Bug#817008: unfulfilled dependencies

[Mattia Rizzolo]

control: tag -1 - stretch

On Fri, Mar 11, 2016 at 12:38:31PM +0800, 殷啟聰 wrote:
> I am confident that 24.3.3+2 solved the bug, but I prefer to wait for
> the package getting accepted. Just want to be cautious :)

uh, ok :)

Though, this very bug would block the migration, so you would see just
nothing.  I'm confident that in this case removing the tag stretch is
enough to have britney to try to migrate it, but whatever I'm going to
keep an eye on this stack, as I'd love to see it migrate and stop
bothering me ;))

Anyway, now that you uploaded android-platform-system-core we need to
wait other 5/6 days before seeing any of this; can you please try to
hold on other uploads non-critical for the testing migration, so we all
of the stack reaches the migration age of 5 days and it migrates?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#817008: unfulfilled dependencies

[殷啟聰]

I am confident that 24.3.3+2 solved the bug, but I prefer to wait for
the package getting accepted. Just want to be cautious :)

Bug#817008: unfulfilled dependencies

[Mattia Rizzolo]

On Mon, Mar 07, 2016 at 10:27:09PM +0800, 殷啟聰 wrote:
> I have fixed it but not yet uploaded it.

So, is this by any chance fixed by 24.3.3+2?

If so, can you please close this bug with a fixed version set?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#817008: unfulfilled dependencies

[殷啟聰]

Thank you for reporting the bug. Actually the reason to this is that I
used ${source:Version} for "android-sdk-platform-tools" and
"android-sdk-build-tools", which is substituted to the version of the
source package rather than their own. I have fixed it but not yet
uploaded it.

The reason of setting the version differently is simple: They have
different versions :(

Bug#817008: unfulfilled dependencies

[Matthias Klose]

Package: src:android-sdk-meta
Version: 24.3.3+1
Severity: serious
Tags: sid stretch

Looking at https://tracker.debian.org/pkg/android-sdk-meta

excuses:
11 days old (needed 5 days)
android-sdk-build-tools/amd64 unsatisfiable Depends: 
android-sdk-build-tools-common (= 24.3.3+1)
android-sdk-platform-tools/amd64 unsatisfiable Depends: 
android-sdk-platform-tools-common (= 24.3.3+1)
android-sdk-build-tools/i386 unsatisfiable Depends: 
android-sdk-build-tools-common (= 24.3.3+1)
android-sdk-platform-tools/i386 unsatisfiable Depends: 
android-sdk-platform-tools-common (= 24.3.3+1)

Invalidated by dependency
Not considered
Depends: android-sdk-meta android-platform-dalvik (not considered)
Depends: android-sdk-meta android-platform-development
Depends: android-sdk-meta android-platform-frameworks-base (not considered)
Depends: android-sdk-meta android-platform-system-core (not considered)

looks like the debian/rules file didn't update

export BUILD_TOOLS_VERSION = 23.0.2
PLATFORM_TOOLS_VERSION = 23.0.0
[...]
override_dh_gencontrol:
dh_gencontrol
dh_gencontrol -pandroid-sdk-platform-tools -- 
-v$(PLATFORM_TOOLS_VERSION)+1
dh_gencontrol -pandroid-sdk-platform-tools-common -- 
-v$(PLATFORM_TOOLS_VERSION)+1

dh_gencontrol -pandroid-sdk-build-tools -- -v$(BUILD_TOOLS_VERSION)+1
dh_gencontrol -pandroid-sdk-build-tools-common -- 
-v$(BUILD_TOOLS_VERSION)+1



On the other hand, I don't see what people are trying to achieve with this 
different version setup.